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

Apple screwed the pooch on this one. It released everything on the same day for iOS 5 and Lion 10.7.1. The servers are jammed so relax already.
 
For me, it's trying to verify the restore twice, once before the iPad restarts; and if that succeeds it verifies it again after it restarts, which always fails.

Grrrrr.... for a second there I thought I was getting somewhere. Think I might just leave it until tomorrow.
 
I'm stuck in recovery mode. When I try and restore it fails.
Is there any way to get it out of recovery mode?
 
Went through some of the problems listed here, but after the restore, all is fine and iOS5 is installed with no problems.
All apps, contacts, cal events and even voice mail msgs were restored just fine.
I have a 3GS, BTW
 
it's simple

It's quite simple, but it took me a while to figure it out. Just reset your iDevice to factory defaults from iTunes (the button under 'update', not sure what's written there, I'm too lazy to connect my iPad now) and it will also offer you to update your device (...it's nice to have a backup before you do so). Click yes / ok on all dialog boxes that might appear and it should do the trick. After iOS 5 is installed, after initial setup it will ask you if you want to restore it's previous settings from iTunes. Click yes / ok and enjoy your new iOS 5 :)

I tested this with my iPad 2, but I think it should work for all iDevices that support iOS 5.
 
Last edited:
I'm stuck in recovery mode. When I try and restore it fails.
Is there any way to get it out of recovery mode?

Be patient... don't unplug.

I restarted, actually shut down my mac, and restarted the restore process. Worked fine.
 
Phone is hosed now, in a loop of a useless phone and trying to put the update on.

Complete fail, Apple.

They should have released OSX 7.2 earlier in the week and then put this out.

Not happy. :mad:
 
Error 3200

Initially my iPad kept showing the 3200 error. It did this quite a few times. I finally got mad and pulled the USB from my monitor and plugged it directly into my laptop. All of the sudden it started working. I am not sure if it was that or just servers being overloaded but I am running iOS 5 now.
 
Error 3014 first time. Error 1004 second time. I tried to follow some troubleshooting by deleting a .plist file and reboot the system. I'm going for the third attempt.

PS: Mission Accomplished :)
 
I was getting this problem and realized I was still using the iTunes beta, downloaded the latest public release and everything is fine.
 
I got error 3004 twice, iTunes forced me to restore, then got 3014 twice. Worked after I entered this in the terminal:
Code:
dscacheutil -flushcache
 
Phone is hosed now, in a loop of a useless phone and trying to put the update on.

Complete fail, Apple.

They should have released OSX 7.2 earlier in the week and then put this out.

Not happy. :mad:

What error did you get? Have you tried check the troubleshooting?
 
How many employers are getting screwed today because people are trying to do this update at work and NOT doing their job?

Or how many people started the update before they went to work, had these issues and decided to call in sick or take the day off work.

For me, all this time has cost me MORE than if I would have just waited until the 14th and went in and bought a brand new iPhone. Wait, this will be my last Apple product. I've never been an Apple fan, but I decided to get an iPhone and iPad. Not 100% happy with either of them. And it's not because of this issue of updating, just don't care for the Apple crap.

Going into the 7th hour and my iPhone and iPad are still not updated. Apple, your way of doing business totally sucks! IT JUST DOESN'T WORK!
 
This is because Apple's servers are slammed. If you get this error, take a break and try again in a few hours or tomorrow and it will work.
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_5 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8L1 Safari/6533.18.5)

Apple's servers just ***** exploded
 
How many employers are getting screwed today because people are trying to do this update at work and NOT doing their job?

Or how many people started the update before they went to work, had these issues and decided to call in sick or take the day off work.

For me, all this time has cost me MORE than if I would have just waited until the 14th and went in and bought a brand new iPhone. Wait, this will be my last Apple product. I've never been an Apple fan, but I decided to get an iPhone and iPad. Not 100% happy with either of them. And it's not because of this issue of updating, just don't care for the Apple crap.

Going into the 7th hour and my iPhone and iPad are still not updated. Apple, your way of doing business totally sucks! IT JUST DOESN'T WORK!

So you don't like Apple's devices, but not because of this updates issues? Yet, you brag only about the update issue?
People calling sick at work to update the phone 'issue' is just plain stupidity.
 
yeah i had the 3200 error code, i kept trying it and it came up about 5-6 times then it went through, so the best thing to do is just keep trying because there i so many people trying to update. IT WILL WORK EVENTUALLY
 
Wirelessly posted (Mozilla/5.0 (iPod; U; CPU iPhone OS 4_3_5 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8L1 Safari/6533.18.5)

I was thinking about updating my iPod Touch (3rd Gen), but now I'm not sure. Maybe I should wait a few days. Then again...
 
Image

Omg so ****** off by this!! They had 16 months to test this! Apple iCloud has no QOS for the updaters? Is there maybe a wrong timeout value somewhere??

There's only like a billion people trying to do it all at the same time. Have some patience. :D
 
i keep getting error 3004 after restoring to almost 70% :mad: :( , tried like 20 times ,, my friend updated his just now ,, bt i cnt :confused:
 
This is because Apple's servers are slammed. If you get this error, take a break and try again in a few hours or tomorrow and it will work.

If Apple knew what they were doing, this wouldn't have happened in the first place. And yeah, it is Apple's fault.
 
This is because Apple's servers are slammed. If you get this error, take a break and try again in a few hours or tomorrow and it will work.

:p Exactly! None of the solutions here work. It's down to Apple's servers and blind luck in timing whether or not the install works. After about 30 attempts, mine is finally progressing. Nothing changed on my part, apart from a few more grey hairs....
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.