Sorry if a similar thread exists elsewhere in here. I did search first, but like all large forums, this one has a search engine that is decidedly cumbersome to use. I did try. Anyway, onward:
I plugged in my 16GB 3G around 10 PM last night to get the 3.0 update. As of this morning, I've plugged the phone into 3 different computers (all PCs), to try and get it working again. I've followed all advice on Apple support pages concerning uninstalling and reinstalling iTunes, DFU mode, checking USB ports, everything. My phone is bricked. The update process runs fine through preparing the iPhone, then installing software, then verifying software and restore, but gets to "restoring iPhone firmware" and quits with "This iPhone cannot be restored. Unexpected error (6)." I have an appointment at a Genius Bar this afternoon. If anyone can offer any suggestions as to something I could try before I'm forced to go there, I'd appreciate it.
UPDATE: Genius Bar gave me a refurb, commenting that "the flash memory was probably messed up". That it happened at the same moment as the 3.0 update was a coincidence. I'm glad to see that I'm the only one who had this issue. The Genius said of all the 3G models he'd seen, this was a first for him, too.
I plugged in my 16GB 3G around 10 PM last night to get the 3.0 update. As of this morning, I've plugged the phone into 3 different computers (all PCs), to try and get it working again. I've followed all advice on Apple support pages concerning uninstalling and reinstalling iTunes, DFU mode, checking USB ports, everything. My phone is bricked. The update process runs fine through preparing the iPhone, then installing software, then verifying software and restore, but gets to "restoring iPhone firmware" and quits with "This iPhone cannot be restored. Unexpected error (6)." I have an appointment at a Genius Bar this afternoon. If anyone can offer any suggestions as to something I could try before I'm forced to go there, I'd appreciate it.
UPDATE: Genius Bar gave me a refurb, commenting that "the flash memory was probably messed up". That it happened at the same moment as the 3.0 update was a coincidence. I'm glad to see that I'm the only one who had this issue. The Genius said of all the 3G models he'd seen, this was a first for him, too.