Update!! So, I went to work after having to give up on the service call, not because the tech was no help or we had exhausted all possibilities but because I had run out of time. I got to work and, on a hunch (or out of desperation or boredom I suppose), I decided to try once more, on my work computer (Dell Optiplex running Windows XP Pro). Downloaded the package, installed the libusb file, and followed all instructions carefully...and HALLELUJAH!!! IT'S WORKING!! What's even better is that I have a backup of my phone on this computer from September, so an old one (and from a previous iPhone) but better than nothing until I get home and fidget with it some more...it's restoring right now, hopefully that goes off without any further trouble...only time will tell of course. SO, in summary, I have learned a few things from this nightmare that I hope will help others with a similiar problem:
- mrangelo is a god among men for laying out clear, easy-to-follow instructions for using iRecovery with Windows, because the ones on the download page are too smart for me
- It seems like trying to run iRecovery on 7 was the cause of my further problems trying to get my computer to recognize the device, probably because the libusb file is designed for XP SP 2, and even installing the file with compatibility settings for that OS didn't seem to help, SO, do yourself a favor and don't bother running this utility unless you're on a computer running XP, it's just waaaaayyy easier and you will save yourself a headache...it literally took me like, five minutes start-to-finish with XP, compared with 2 hours of useless fighting with 7
- Uninstall the libusb file after you're finished, to make sure there are no lasting changes to your registry or anything...I don't know why, but installing the file on my 7 computer caused the wireless drivers to malfunction (see previous post), so its just safer that way...the file comes with an uninstall function so you should be able to remove it completely, a nice thing since I did this on my work computer
- According to the tech I spoke with this morning, Apple is giving them a set of several steps to try (i.e. uninstalling iTunes completely and reinstalling, attempting to restore from a new User profile, etc.) before doing any real repair work because they are unhappy with the number of phones being sent in and replaced due to this error (my response? Hmmm...maaaybe they should fix it then?!) All the steps the tech mentioned either failed me or failed someone else in this thread, so I would recommend one of two things before you waste your time: take it to an Apple store (not AT&T, Apple) so they can attempt fixing it, fail, and replace your phone, or run iRecovery. It works and makes no lasting changes to your phone, so will not void the warranty, though I wouldn't recommend telling the store you tried it if you did and it failed, unless you want to risk further headache and a scolding at the Genius Bar.
- These appear to be the only, or at least the easiest, options for this error, until Apple gets around to coming up with a real fix, which they do NOT have as of this morning, even though my tech was very nice and eager to help me
Thanks again for all your help mrangelo, if I knew you I would send you cookies. Restore is done and I have most of my contacts at least, and a working phone. Whew...good luck to everyone else having this issue...