Restore needed every time there's an update?

[atlaz]

I have an iPhone 3G in the UK on O2. So far, I've updated it twice and each time it's been out of action for over an hour because I've needed to restore. Obviously this can't be normal, anyone have any idea what I can do about it?

 

[mkrishnan]

Obviously this can't be normal, anyone have any idea what I can do about it?

Do you mean that the restore action (i.e. returning your settings, SMS, Notes, etc, to your phone from backup after the firmware has been updated) itself took an hour, or do you mean that it took you an hour to update your phone to the new firmware, reboot it, resync it, and restore it?

If you mean the latter, you're doing pretty well compared to most users, and the only real advice is to pass on minor updates. Like if you got 2.0.1 and no one even knows what 2.0.2 fixes, and the next 2.0.x is probably going to come in a couple of weeks, just don't bother with 2.0.2 at all.

If you mean the former, then that does seem somewhat atypical... From what I remember, the "restore" itself did not take very long. In fact the longest step was re-syncing all the music....

Now if Apple could just make it so that the firmware could be upgraded without re-syncing the music.... syncing music on USB2 is so painfully slow!

 

[atlaz]

Well for 2.0.2 I'm now on my second restore as iTunes didn't like the iPhone. I had two restores for 2.0.1 as well so I'm starting to wonder what the hell is up with the Apple upgrade/restore process.

 

[atlaz]

And now it still doesn't recognise it despite 3 restores. I think I'll give up and just pretend it's a new one.