Cleanse, Tone, Defrag: iOS 5 Error 3200 aka Hold Your Horses
Don’t call it a comeback because it’s not. Well, it might be. Just a bit, perhaps blue-moony, but at any rate let me apologise for essentially just dumping this column without a head’s up. After the last entry, things got hectic and my muse decided that enough was enough and ran off into the night, screaming and casting her bra that once held her bosoms of inspiration asunder.
Or, rather, my plate was full and I didn’t know what to write about.
Then last night happened. You all know what last night was, right? Of course you do. It was the iOS 5 general release. Even if you’re a BlackBerry or Android user, chances are you knew about it from all the tweets and status updates and the general rubbing in that Apple’s answer to BBM, iMessage, was live and working, unlike the aforementioned.
Perhaps it was our snarky comments – mine included, I’ll admit – that might have pushed our luck, or at least some of our collected, go with me here, “iLuck”.
After the laborious download of the new update, many iPhone, iPad and iPod users found themselves with an error message during the final stages of installation, telling them that their mandatory backups could not be restored. Turning to Twitter, as I you do in times like these, I think it was safe to say that there was a somewhat collective sigh of relief at finding others with the exact same problem, and not exclusive to just one device either. Not before long, #error3200 was trending along with plenty of moaning tweets from iOS users. Of course the BlackBerry lot also took advantage of the hashtag to dig their knife in and make with the Nelsons’. And for those who tweeted “Apple and BlackBerry crumble”? Bra-very-o.
So what was/is Error 3200?
A verification error. Nothing malicious, that is unless you count the time you’ve spent in front of your computer, tirelessly waiting for the process to go through because you just know that the minute you move you’d be needed to press ‘Confirm’ or something. The error is returned to users when the verification is denied or cannot be achieved due to Apple’s servers being battered by the literal millions trying to update their shinies. Your backup and data is fine (for the vast majority), the hour-long-plus software download isn’t corrupted; if you got the error then you were just simply unlucky that your verification was denied. There’s no need to restore to factory settings (even though some did and to no avail), call a Genius or likeminded tech-friend. Just be patient and wait it out. I’m aware that’s very rich coming from me considering my last tweet of the night, but… shut-up.
Your best bet if you’ve been unsuccessful so far is to either just wait or scheme to get the update complete when no one else is about. My personal advice is to get up a bit earlier in the morning, ideally the majestic twilight and or FU period of between 6-7am, and you’ll be up-to-date before most peoples’ alarms go off. Worked a charm for me this morning.
Affiliates
