In yesterday’s post, I chronicled some of the issues I was having with updating my iPhone 4 to Apple’s shiny new iOS5.
I was certainly not suffering in solitude yesterday. Twitter was going crazy with people experiencing not only the same Error #3002 that I was seeing, but many other errors as well. As far as I know, Apple has not released any official cause for these issues, but rumors continue to swirl that all errors that people were seeing were a result of the demand for the new operating system.
I’m not totally convinced, however, that the #3002 error I was receiving was just a matter of overloaded servers. Of course, I’ve got no way to confirm my suspicions, so I’ll just move on and take away the lesson of “don’t try to upgrade on the first day.”
Unfortunately, that pesky #3002 error was not the only problem I had yesterday.
When I tried to update my iPad to iOS5, the first problem I encountered was the download time for the update package. That one I’m happy to attribute to overloaded servers. But once the download completed, that’s where the real fun began.
I had backed up both of my devices prior to performing the update process. Always a good thing to do, if possible, and it’s highly encouraged by Apple.
The update process itself, albeit slowly, completed without any issue including the restoration of the device…so I was led to believe by iTunes.
When I powered on the device after the update, the only thing greeting me was the basic app suite included with iOS5. None of my previous apps had been restored after all. Not a problem, I tried to do a restore. No such luck, even though there was a valid backup available from just prior to starting down the update path.
Fortunately, all is not last as some might think. I was able to access the “purchased” tab in the AppStore and view a list of apps that had been previously installed on the device. While it a was a minor pain having to reinstall each and every app, I did get all of them back on to the iPad.
Same thing was true with iBooks. I went into the store and clicked on purchased which allowed me to bring my purchased books back down.
The only casualties of the iPad upgrade to iOS5 were the loss of some .pdf books/papers I had installed in iBooks, a few movies I had copied to the iPad, and the music that I had copied to it. Over all, not too bad.
Today, I had the opportunity to update two brand new Verizon iPhone 4 handsets. Why didn’t I get the i4s you might ask? Well, price was the big factor, but secondarily, I wanted to voice my displeasure with Apple not releasing a new phone to go with the new iOS. Believe me, had they offered an i5, I would’ve been all over it as I’ve been waiting to upgrade two Blackberrys for a very, very long time.
Biggest thing I needed was a replacement for Blackberry Messenger (the security aspect) and iOS5 does the trick for me with iMessage.
Fortunately, updating these two phones went off without any problems whatsoever. Not a single Error #3002 was raised, nor were the download times appearing to be extraordinarily long. Maybe Apple did something on their end to increase capacity, or perhaps demand has dropped enough which I tend to doubt given the number of devices in the wild that can be updated to iOS5. Whatever the case, I happy things went smoothly.
Now I can get back to my regularly scheduled programming already in progress.