Cannot restore/update iPhone. Internal error iOS5

same here =/

The same thing happened with my iPhone 4 and iPad 2. Updated Mac OS X and iTunes but nothing has changed after 4 attempts.

Same problem - I disabled my firewall and everything on the IPhone updated... Then enable after update...

Same here -- nothing I do seems to make any difference. I'm considering a factory wipe of my phone, and doing the upgrade from the fresh device...

Add me to the list. Same error as everyone else. Looks like Apple have succeeded in making a total mess of the iOS5 update...

😢

no it's not the update servers. When you get to the point of the backup for your iPhone the software iOS image is already downloaded and on your computer. From there it's usually a wipe, upgrade and restore.

So are you saying updating with no firewall allowed the update to succeed and you are now running iOS5 with all your apps restored?

Yes, I'm having the same problem with a 3GS. Tried it twice, but just get the error message.

Bob.

I can confirm it has nothing to do with firewalls.

me too 😟 an i need my iphone until tomorrow ... thanks apple... i always get a connect to ituens logo and can+t get out of recovery

I am afraid i am having the same problem and had the same issue with the ipad too... have tried different USB ports... and now clearing all the data from my phone just incase but not having much luck... fingers crossed we find an answer

iPhone 3GS running 4.3.5 here and Snow Leopard. I can confirm that disabling my firewall enabled the restore process to go through. Previously I received the internal error message 5 times in a row.

I am retired IT and its was the firewall... I am now running IOS5...

I am retired IT and its was the firewall... I am now running IOS5...

I was having the same problem as well. I updated iTunes to 10.5 and OS X to 10.7.2. After getting this error twice I decided to try to do a normal sync since I hadn't done that after updating iTunes and OS X. The sync worked correctly, so I tried the iOS update again and it seems to be working (still installing, but I didn't get the error this time).