Thursday, 13 October 2011

iOS5 and the 3200 error

I've had some fun with technology the last few days. Firstly I switch on my netbook on Monday evening and the screen is screwed up, green lines, flashing pixels like green snow, colour scheme that would make Windows 95 look classy, to say I wasn't impressed wouldn't exactly be an understatement. After some brief internet searching, I discovered the area around the side of the screen was somehow coming apart, so I clicked that back in, still the same.

Then I closed the netbook in annoyance and noticed the battery bit thing wasn't straight, somehow something there had come loose too. Out came the battery, and a quick repair later and I had one netbook looking like nothing had ever happened to it.

So I thought right, that's my weekly machine break down, it's all good. Then last night I decided to try n get a bit of iOS5 action going on for my little soon to be out of date little iPhone. I was expecting slowness having the drawn out process of going os3 - os4 still in my memory, but thought fuck it lets go.

The first part was more a lesson than anything, don't ignore iTunes updates, as I think I had to do about 150 updates to that first (that may be an exaggeration... may be). But then I was ready to go. I began the download, all ok and done in about 30 mins, much better than I was expecting, iTunes then backed up the creatively titled 'Andrews iPhone' (imagination pumps from every pore on times), it was time.

Time? Yeah! Time to friggin crash!

I was greeted with the soon to be infamous 3200 error, iTunes didn't know what it was or if it did it didn't want to tell me. The update stopped and the phone reverted to its previous state. OK, no big deal, no harm done. Let's try again. Same thing happened.

"To google!" I exclaimed (in my head) and started a search for this problem. Of course the Internet was instantly filled with know-it-alls who were making it their business to tell everyone how to fix it as they knew cos they were clever. They varied from restarting PCs to restarting phones to reinstalling iTunes itself. Nice one assholes, I've heard people talk shit before and I spotted it a mile off, so ignored them. However there was one, reasonable sounding post saying to just keep trying eventually it worked and they thought 3200 was some kind of server issue due to traffic.

This all made sense, it was doubtless busy at the moment, so I soldiered on. Numberous times I was thwarted at the metaphorical gates of Mordor by this 3200 error, but I battled back, only to be pushed back again. Then finally... it connected, the installation started, this was it... iOS5 would be mine.

Boom in comes a 3004 error and stops it dead, only this time no revert, I'm stuck in restore mode. I have no idea how to get out of restore mode. I stomp off for 5, phoneless...

A bit of research tells me how to reset the phone using the buttons, I do so and try again. 3200 kicks my ass all over again. Twitter is alight with part 'yay os5' tweets and part '3200 gumble grumble' ones. With a side helping of smug Android users (easy to be consistent if you never try anything new). One more item I think, just one more time...

Battle of Los Angeles (that's battle of, not Battle: Los Angeles) had been playing in the background thanks to Syfy+1 and was about to finish (and may I say what a piece of dog turd that film is. I know it's one of the Asylum low budget cash in films, but Jesus Christ, how do you make films this bad??) so I knew it was late.

I hit restore one last time and bingo, it worked, iOS5 was mine took seemingly an age to update and then it was done. To be honest, looks a bit prettier in places but so far not noticing a ton of changes, but I have used it for about 15 minutes to date. But improvements are the subject for another day. This was about my battle against 3200 and how I won!

Go me...

No comments:

Post a Comment