I bricked my iPhone attempting to upgrade from 1.1.2 to 1.1.3. Last night I tried iJailbreak Mobile twice, but I mysteriously dropped off my wifi at 93% and then 94%, and that wiped me out. So I used iJailbreak, but it requires the “Soft Upgrade” package from the Installer repo, which has since been removed, which left me with 300+ megabytes of trash littered all over my iPhone. So I ran the “Official 1.1.3 Installer” and it worked! But then it rebooted and gave me the dreaded “Your phone is damaged, please bring it back to Apple” nonsense.
Luckily, you can put your iPhone into restore mode – aka “dfu” mode – by holding down the home key and plugging it into your computer. I restored to 1.1.2, and then upgraded to 1.1.3. So I am on 1.1.3, and thankfully, my phone works, so that’s good. But I’m no longer jailbroken, and that really sucks.
Here’s hoping the SDK is not as lame as some fear it might be.
I am still on 1.1.1 because I need the phone to be unlocked, and the 1.1.2 and 1.1.3 versions are either not unlocked or non-reversable, which makes it difficult to upgrade in the future. So I leave it at 1.1.1 and hope that a better way will appear when the SDK firmware version comes out.
Er, that’s not bricked.
Bricked is when the device is as useful as… a brick, and the only thing you can do is send it back to Apple.
You could put an older OS revision on there, so that’s nothing like bricking.
What next? “Help! My PC is a brick because of Mandriva 2008! But no worries, I’ve gone back to Mandriva 2007”
See why it makes no sense? 🙂
@Blah:
My understanding is that prior to this version of iTunes, a restore in this manner was not possible, so it was bricked, but now, it’s restorable. Either way, it’s fixed, so it’s mostly a moot point.
The motivation behind the post is that upgrading the jailbroken phone destroyed the software on the unit and required a complete flash.