Like most everyone who was let down by Apple’s announcement on October 4, 2011 that there would not be a truly new iPhone 5 being released, we did take a little bit of comfort in the fact that iOS5 was to be released today, October 12, 2011.
It was a good day for me for the release – I didn’t have any client meetings, I’m not up against any massive deadlines, not much to do except eagerly await the announcement that iOS5 was ready to be loaded onto my iPhone 4 and my iPad – not to mention the two new iPhones that are somewhere in transit.
A little bit after 2pm Eastern US Time, my constant clicking of the “Check for Update” button was rewarded with the dialog box that iOS5 was now available. I could feel a little flutter in my belly as I clicked the “Continue” button. I acknowledged that some items had not been transferred to iTunes – everything had been as I had backed up my phone several times throughout the morning – and started the process.
First time, it crashed with an Error #3002 – An unknown error has occurred. Great, not even the great Apple knows what the error code being thrown means. Quick – Bing to the rescue…
Only thing I could find was some early beta developers encountering this error and were able to load the software from a specific location while performing a ‘Restore’ instead of an ‘Update’. Unfortunately for me on my Windows7 box, I could not replicate the steps detailed in their posts.
But, I’m stubborn – figured I’d try it again. Clicked the mighty ‘Update’ button and eventually received the same Error #3002. Now, in this dialog box, there is a ‘More Information’ button. My experience with these on my Windows machines, is the ‘More Information’ takes you to something that could be considered “more information” – but if you don’t read Hex, and weren’t part of the original product dev team, it’s completely useless information.
Kudos to Apple, though…the ‘More Information’ that was provided included a small link to “advanced troubleshooting” tips for specific errors, including the 3002 error I’d been encountering.
Two pieces of advice stuck out at me – 1) Restart the computer. Ok, I can do that.
Piece #2 was “disconnect all other USB devices”. Ok, considering that my keyboard/mouse are USB devices, that’s not completely practical. However, it did occur to me – I had my iCord plugged in to a USB hub. Even though it’s a powered hub, it just might not be up to the task, so I plugged the iCord in to an “installed” USB port (after the restart) and gave the update another shot.
Well, the first time through, it threw the #3002 back into my face. Mocking me. As I said earlier, I’m pretty stubborn, so I tried it again.
Apparently, my stubbornness has paid off…I’m about 5 seconds away from a completed restore from backup after installing iOS5!
I’m going to verify this with the iPad next, but if you run in to this iOS5 Error #3002, my advice would be to:
a) Restart your computer, and
b) Make sure you’ve got your iCord plugged in to an installed USB port.
It may not be a fool-proof solution, but it did work on the iPhone 4…I’m happily looking at iOS5 reporting that it’s been successfully installed.