Android ADB device offline, can't issue commands

android adb android-2.2-froyo
Brian picture Brian · Feb 21, 2013 · Viewed 734.5k times · Source

I can't connect to my device anymore using ADB through the command line or in Eclipse.

Running the command

adb devices

returns the device name, but it says it's offline.

Things I've tried.

  1. Toggled Android debugging mode
  2. Reinstalled the Google USB driver
  3. Restored the OS to a previously working backup (CyanogenMod)
  4. Swapped the USB cord
  5. Rebooted the phone/computer multiple times
  6. Updated the Android SDK

I really don't have any clue what's going on. Anything else you think I can try, I'm all ears.

To be clear, if you're having this same issue the problem is probably an out-of-date SDK. As of 4.2.2 there is a security feature that requires you to confirm the RSA fingerprint of the connecting device. Open the SDK manager and update the tools! Then reboot.

Answer

Thomas Economous picture Thomas Economous · Mar 12, 2013

Try running adb devices after running adb kill-server. Security question pops up after that. Worked for me.

Related questions

ADB Shell giving bad mode when executing chmod (under su)

I'm having an issue related to the Android ADB Shell. When I try to execute the command chmod he gives me a "Bad Mode". I don't get it why. I'm sure I'm executing under "su", as represented by the '#…

Read More
How can I connect to Android with ADB over TCP?

I am attempting to debug an application on a Motorola Droid, but I am having some difficulty connecting to the device via USB. My development server is a Windows 7 64-bit VM running in Hyper-V, and so I cannot connect directly …

Read More
Android Studio doesn't see device

The AVD Manager in Android Studio doesn't show my device but adb devices does show it. Am I missing something obvious here?

Read More