Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Bricked iPhone with 3.0

h.21 said:
Hey, you were right! Thank you so much for helping me with this. I was really worried that I had screwed up big time. After I provisioned my device it did recognize in iTunes and I'm restoring from a backup now. Thanks again!! :D
Click to expand...
No problem! Glad I was able to help ... :)
 
Apple needs to outline this procedure much more clearly. It is as confusing as heck when you first get going.
 
WTF Invalid SIM

I am a paid dev. and upgraded through xcode now have an invalid SIM error?? cant activate???
 
thyland said:
I am a paid dev. and upgraded through xcode now have an invalid SIM error?? cant activate???
Click to expand...

Yeah i have the same problem. Tried with 2 sim cards (2 different carriers in belgium) and neither worked. So I'm using my SonyEricsson t68 now :p
 
Whew! Glad I read this first. I'll wait until the final release is available. Enjoy my jailbreak for a couple more months.
 
Installed the OS 3 beta on mine last night. Mine was jailbroken and the install went without a hitch.

By the way System Profiler gets you the Iphone UDID also
 
jav6454 said:
You are stuck there. You cannot downgrade back down to 2.2.1 goodness. Sorry, but the Dev Team and pretty much everyone who has been in the iPhone scene since last Spring warned people, not to update unless you are really comited to developing.

Sorry if I sounded like an a$$ hole, but its the God honest truth and this way we can have fewer "help me, 3.0 beta bricked me!" threads.

3.0 Beta - Lesson to be learned, casual users be warned, once you update you are on your own!
Click to expand...

Thanks for reading the thread? The guy already had his problem fixed by the time you replied.
 
MistaBungle said:
Thanks for reading the thread? The guy already had his problem fixed by the time you replied.
Click to expand...

I think his point is still valid. 3.0 beta is for developers to test on if they want to start developing for the latest APIs, not for public consumption. It may not always brick your iPhone but from what I've read there are lots of kinks to work out and its not yet compatible with all 3rd party accessories. You can (for free) download the 3.0 SDK and play with it on the simulator all you want though, risk free.
 
sage

jav6454 said:
You are stuck there. You cannot downgrade back down to 2.2.1 goodness. Sorry, but the Dev Team and pretty much everyone who has been in the iPhone scene since last Spring warned people, not to update unless you are really comited to developing.

Sorry if I sounded like an a$$ hole, but its the God honest truth and this way we can have fewer "help me, 3.0 beta bricked me!" threads.

3.0 Beta - Lesson to be learned, casual users be warned, once you update you are on your own!
Click to expand...

Thanks for your encouraging post, but I got everything working fine. I knew there was no downgrading from the 3.0 Beta, but I didn't know about the process of provisioning devices.

That doesn't matter though, because it's pretty obvious you didn't fully read my first post. I never said anything about *wanting* 3.0 off my device.


ptsube said:
Apple needs to outline this procedure much more clearly. It is as confusing as heck when you first get going.
Click to expand...

I agree with you. It is a bit confusing if you are completely new to the program and haven't researched it previously.


DavidLeblond said:
I think his point is still valid. 3.0 beta is for developers to test on if they want to start developing for the latest APIs, not for public consumption. It may not always brick your iPhone but from what I've read there are lots of kinks to work out and its not yet compatible with all 3rd party accessories. You can (for free) download the 3.0 SDK and play with it on the simulator all you want though, risk free.
Click to expand...

We all have to start somewhere, eh? Just because I'm not familiar with Apple's unique scheme for implementing this does not mean I am stupid. That being said, their scheme has been a pleasure to work with so far, even taking this into account. ;):apple:
 
fjk said:
why would apple brick every developers' phones once the beta is completed???
Click to expand...

Apple has bricked every developers phone at least once IIRC when the next beta OS wasn't ready before the previous beta expired. Fortunately it was only a temporary bricking for a couple days.
 
Master Chief said:
Sure, but not the "UDID" (which might be the same, but I'm not sure).
Click to expand...

Edit: The "Serial number:" displayed in System Profiler is the same as when I click on the serial number in iTunes (click to toggle the Serial Number/UDID on the Summary tab) so it does display it, but with the wrong text in front of it.
 
How to downgrade from 3.0

So my brother and his company are a part of the developer program and I wanted to 'tag along' since I've started to learn how to develop (but I didn't want to pay $100 :( ). I went ahead and upgraded to 3.0 because he said he would put my iphone on his list - well turns out he's not going to be able to do that... at least not now (but that's beside the point).

So last night I was stuck with an iphone (not part of the developer program) in 3.0, and I couldn't downgrade - I had a brick.

After a while of tinkering I've got the phone working again and running on 2.2.1!

To do this, I downloaded PwnageTool and created a custom .ipsw from 2.2 and it installed pretty well (however, it did take 2-3 tries for some reason...). Then, since I didn't want it jailbroken, I figured I would just update up to 2.2.1 and I would have a fresh legitimate updated firmware. iTunes erred again and now I'm starting the process over.

However, this time I made a custom .ipsw from 2.2.1. That went ok, and I had a working, jailbroken iPhone on 2.2.1 - again, though, I don't want it jailbroken (but if it's the only way for now, I'll keep it).

I just updated the carrier settings and I am currently restoring the phone to 2.2.1 - so that it will not be jailbroken.

--- Ugh ---

Well while typing that I got an error again from iTunes while I was attempting to restore from a jailbroken 2.2.1 to a fresh 2.2.1 - iTunes error 1013.

I am now going BACK to the jailbroken 2.2.1 since it atleast lets me use my phone. If I discover anything else, I'll post.

If anyone is able to fully bring it back to 2.2.1, please email me or PM me!
 
Updated to OS 3.0 only to get error 1013

So yesterday i got excited to update my iphone to the 3.0 firmware...
After waiting hours for it to back up and actually install, i got greeted with "unable to restore, error 1013" or something like that.

I've tried so many different ways to restore using the DFU and recovery modes, but nothing. The closest i got was another error message "restore needed, please restore using itunes" but then got something about my SIM pin stopping it from activating!

Please can someone help me out here, i have just about lost all patience with Apple and it' products!!
 
Tr17aV said:
So yesterday i got excited to update my iphone to the 3.0 firmware...
After waiting hours for it to back up and actually install, i got greeted with "unable to restore, error 1013" or something like that.

I've tried so many different ways to restore using the DFU and recovery modes, but nothing. The closest i got was another error message "restore needed, please restore using itunes" but then got something about my SIM pin stopping it from activating!

Please can someone help me out here, i have just about lost all patience with Apple and it' products!!
Click to expand...

My problems are exactly the same... I have another thread on here about it but I'm getting the same thing. I've spent hours on this and nothing :(
 
Kyeris said:
My problems are exactly the same... I have another thread on here about it but I'm getting the same thing. I've spent hours on this and nothing :(
Click to expand...

Yeah same here for me too. Done everything that the Apple support article suggests (using a differnent USB port, different computer, restarting machine etc.) and still got no where.

I've restored back to 2.2.1 a few times and tried "upgrading" to 3.0 but I get the same problem everytime. As im easily able to restore back to 2.2.1 it makes me think there must be something wrong with the 3.0 update?
 
I can't even get down to 2.2.1, I get an error 1600 downgrading, and can't downgrade out of recovery or DFU mode because I get a sim error when out of those two modes.
 
Kyeris said:
I can't even get down to 2.2.1, I get an error 1600 downgrading, and can't downgrade out of recovery or DFU mode because I get a sim error when out of those two modes.
Click to expand...

Yeah same here! I can't even revert back to the previous version!
What the hell is going on?
 
Tr17aV said:
Yeah same here! I can't even revert back to the previous version!
What the hell is going on?
Click to expand...

Yeah no kidding. I was trying to downgrade to 2.2.1 and jailbreak so I can get access and then restore to 3.0 and hoped that work, but I can't even get to 2.2.1, after it unpackages the .ipsw I get a 1600 error.

Edit: Tried it on my MacBook, Windows 7 x64 on my MacBook, Windows 7 x64 on my PC, and now Windows XP on another PC, seems like I'm getting some progress, I'll update when it's finished.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back