Two nights ago I was trying to adb in to my phone but "adb devices" said that the phone was there, but "offline". I updated ADK and went to bed.
Last night the phone charges fine but now it will not show up as a device at all. The PC does not even look for the software and show up as a bad device. I think this is hardware, because this is what I have tried after digging around in the forums:
adb over WiFi works, and I guess I could FTP files to the phone, but it is all a bit mysterious. The phone has not been dropped, not have I done anything different with it. USB debugging used to toggle an insertion event on the PC but not any more. The only "different" thing I did that night was try adb over wifi to see if I could get in to the phone. I have since uninstalled that widget.
Frustrating. I wonder if there is any simple setting that might have ticked itself.
Last night the phone charges fine but now it will not show up as a device at all. The PC does not even look for the software and show up as a bad device. I think this is hardware, because this is what I have tried after digging around in the forums:
- different cables - my phone bad, wife's Desire S is fine
- different PCs - my phone bad, wife's Desire S is fine
- different ROMs with full wipe - IceColdSandwich and Android Revolution draw a blank. Revolution detected the USB insertion and said that it was going in to USB hard disk mode, but that PC did nothing.
- cleaned out the port with an air jet and a pin (there was nothing to pull out).
- rebooted in fastboot, "fastboot getvar all" did nothing other than "< waiting for device>"
adb over WiFi works, and I guess I could FTP files to the phone, but it is all a bit mysterious. The phone has not been dropped, not have I done anything different with it. USB debugging used to toggle an insertion event on the PC but not any more. The only "different" thing I did that night was try adb over wifi to see if I could get in to the phone. I have since uninstalled that widget.
Frustrating. I wonder if there is any simple setting that might have ticked itself.