Printable View
1) launchctl, ok
2) ienew, lost wi-fi, continued on mobileterminal
4) iunew, ok
5) bbupdater -v, failed
6) tried various firmwares, all said no-wifi, sim missing
7) did a stupid mistake and restored to 1.1.3
8) now i get fast scrolling text during boot, but iphone never starts and keeps rebooting
9) i have tried all firmwares, but it either fails to restore or finishes with error and fast scrolling text stays
Can anyone confirm that this iphone now should be called ibrick?
What version were you running when you ran ienew/iunew ?
I would put it on DFU, restore to 1.1.2, them put again in DFU and restore to 1.1.1, jailbreak, and check "bbupdater -v"
If you sucesfully downgraded the bootloader to 3.9 you can erase the 1.1.3 baseband with the 1.1.3-secpack. But if you didn't, you're doomed for the time being :)
I ran ienew/iunew from 1.1.1.
Problem is that I can't even restore in DFU mode.
I have tried all version and I iTunes 7.3 starts restore only for 1.0.0 and 1.0.2.
For version 1.1.1, 1.1.2 & 1.1.3 it justs extracts firmware and then spits unknown error.
Just out of curiosity, what week is your unit?
week 45, if I had bought just day earlier then I would have these problems.
I have not seen this error before, but I would perhaps try with a newer version of iTunes?
Messing with the commboard/baseband should not disable the main OS FW like you are describing. I am hopefull your iPhone can be saved.
Good luck.
Turns out, this was caused because I wasn't patient enough when ibrickr jailbreaking process. I put iphone in restore mode and after running AppTap I was back to activation screen.
Then I restored to 1.0.2 and followed this jailbreak guide - http://www.hackint0sh.org/forum/showthread.php?t=24122
It still said no wi-fi and repair needed, so I was trying this guide: http://www.hackint0sh.org/forum/showthread.php?t=13255
But I did not succeed:
1) ieraser stays at "Waiting for data..."
2) bbupder after trying 10 times spits out error "Error: Baseband bootloader is too old. update to 1.8 or later and try again."
So, does this mean that 1.1.3 screwed everything and now I have to wait for 1.1.4?