Device offline in ADB

diver47591

Senior Member
Feb 24, 2011
90
5
0
After following info on XDA and everything I could find elsewhere on the web to no avail, ADB still showed "error; device offline" . I believe I must install new rom in order to start over with computer/device recognition. After "Revoke USB Authorizations" in Settings>Developer Options>USB Debugging, believe that is a permanent revocation until computer is presented with a new system.img, (rom). But I am just noob, please correct me if I'm wrong. So if I'm correct I guess I'll Have to do Factory Reset, lose root, and go through the whole process again
 

alin919

Senior Member
Oct 25, 2013
365
72
0
Raleigh
After following info on XDA and everything I could find elsewhere on the web to no avail, ADB still showed "error; device offline" . I believe I must install new rom in order to start over with computer/device recognition. After "Revoke USB Authorizations" in Settings>Developer Options>USB Debugging, believe that is a permanent revocation until computer is presented with a new system.img, (rom). But I am just noob, please correct me if I'm wrong. So if I'm correct I guess I'll Have to do Factory Reset, lose root, and go through the whole process again
If you do a manual factory reset , never gonna lose the root.
 
  • Like
Reactions: diver47591

alaneddy

Senior Member
Jun 2, 2013
148
71
0
Dothan
After following info on XDA and everything I could find elsewhere on the web to no avail, ADB still showed "error; device offline" . I believe I must install new rom in order to start over with computer/device recognition. After "Revoke USB Authorizations" in Settings>Developer Options>USB Debugging, believe that is a permanent revocation until computer is presented with a new system.img, (rom). But I am just noob, please correct me if I'm wrong. So if I'm correct I guess I'll Have to do Factory Reset, lose root, and go through the whole process again
When you "Revoke USB Authorizations" it just clears the current saved devices. Try this, unplug device, use a USB port on back of the computer (sometimes it matters), make sure Developer Options is enabled, USB Debugging enabled, Verify apps via USB unchecked, revoke USB authorizations, then start ADB, plug phone in and wait for it to be recognized by windows, then enter the command "adb devices". The phone should ask if you want to authorize this PC.

If that fails, try a different cable.
 
  • Like
Reactions: diver47591

diver47591

Senior Member
Feb 24, 2011
90
5
0
When you "Revoke USB Authorizations" it just clears the current saved devices. Try this, unplug device, use a USB port on back of the computer (sometimes it matters), make sure Developer Options is enabled, USB Debugging enabled, Verify apps via USB unchecked, revoke USB authorizations, then start ADB, plug phone in and wait for it to be recognized by windows, then enter the command "adb devices". The phone should ask if you want to authorize this PC.

If that fails, try a different cable.
I was way off! I found a suggestion on another site that recommended updating sdk. Determined my sdk was version 1.0.29, updated to 1.0.30, and voila returned "device name device" good to go. Thanks so much for the help.
 
  • Like
Reactions: alaneddy