Well, my Apple Support contact called me today. He tells me that the researchers have decided I definitely have a "hardware problem" and need a new phone. Since my old phone is out of warranty, that means I have to pay for a new one myself.
I protested that my 2 yr old phone never had a single problem until I downloaded the Apple update, so why did he think it was a hardware issue? He explained that the "logs" from my computer indicated a hardware problem. This reference to the "logs" is like a car mechanic's reference to the faulty "manifold" or "timing belt"---he knows I have no expertise in "logs" so I have to take his word for it. But I gather the crucial evidence is that I got this [-1] error which means a hardware issue.
The reason it took Apple so long to figure out that I had a hardware problem, despite my having told the tech about getting the [-1] error the first time I spoke to him, is that before the IOS5 update, no one at Apple knew anything about this error. Why? Because it was so rare. It was not even included on Apple's standard list of errors (used by techs). But now, suddenly, all the Apple techs are getting to know it REALLY well, because in the wake of the IOS5 update, this error is turning up all over the place. But make no mistake---the sudden prevalence of a heretofore unknown error does NOT mean the IOS5 update is responsible---oh, no no no no!!! It's just that, coincidentally, we all happen to have acquired a mysterious hardware problem recently---a problem that never manifested itself in any way, shape, or form until we downloaded the update.
I asked the support guy if he had any PROOF that this hardware problem existed in my phone before the IOS5 update---I mean, I see evidence that suggests that it didn't exist before the update (the phone worked)----what evidence is there that it did exist before the update? Once again; "logs" and the [-1] error. Nothing more specific. At this point, it dawned on me that the tech guy was just repeating to me what the researchers had told him. He didn't get it either.
When I asked why no previous updates had triggered this problem if it was lurking, he said the glitch must have developed after the last update (as usual, no hint of how he would know that---I think he just threw it out there so I would not suggest the glitch had been lurking since the phone was brand new). When I ask for specific evidence that would lead him to think that, he could only offer: logs & [-1] error code.
I reiterated once more that my phone (and the phones of lots of other people on the Apple support site) worked perfectly before the update, and that all our phones were identically disabled (stuck in restore loop with -1 error) by the update. Didn't that seem odd? He said that actually there were all kinds of different hardware problems that could elicit that [-1], so the other people complaining on the site actually had different problems. I asked, "With the exact same symptoms, occuring in the same way, during the same update process??" Yup.
Why should I believe this tale of mulitfarious latent hardware problems? When I finally asked the tech guy EXACTLY what my hardware problem was, he said that the only way I could find that out was to send in the phone for a diagnostic & repair, which would probably cost more than getting a new phone. That answer spells out my situation: I am screwed and have no options. Apple's update broke my phone, and Apple is not going to take responsibility.
As it happens, I recently learned that I can get a free iphone 3GS (like mine but less capacious) from ATT right now. Or, I can get a castoff next-to-new iphone 3gs from someone I know who is upgrading. But I am feeling so annoyed at Apple for disabling my iphone with their latest update that all I want to do is run around telling as many people as possible about how irresponsible Apple is. Good luck to the rest of you.