Android 4.2.2 adb can't find devices

Question

With the new update to 4.2.2 to my Galaxy Nexus and Nexus 7, I can\'t find both my devices under adb.

These are the steps I took:

• Updated to 4

Answer 1

For me the best solution was:

Update the Android SDK via the SDK-Manager. Removing the '.android' folder in my usr directory ( Windows 7 ) and re-plugging the device back in. Worked flawlessly due to the ADB RSA key issue. I had an older version of ADB that I stashed into c:\windows\system32\ due to not wanting to install an entire freakin SDK when all I wanted was a command prompt. Good ol' Google, the new Microsoft.

Answer 2

adb wait-for-device

works for me. Just unplug your usb device, run this command, and while it's waiting, plug your device in, then it will just work. :)

Answer 3

going to Developer Options and checking USB Debugging solved it for me

Answer 4

I tried everything mentioned here and in other posts. It wasn't the cable, the USB port, rebooting the PC or Nexus 7, killing and starting adb or enabling/disabling USB Debugging.

It was due to the 4.2.2 OTA update, I simply replaced the \platform-tools\ folder, as described here: Android ADB device offline, can't issue commands

Download the updated platform-tools: http://dl.google.com/android/repository/platform-tools_r16.0.1-windows.zip

Answer 5

In case it helps someone else arriving here, I had this problem with a ZTE phone.

I tried installing the driver based on the offical list here but in Device Manager the driver was marked as not installed correctly.

In the end I found the way to make this work was:

1. Press Menu Button
2. Choose "Connect to PC"
3. Choose "Default connect type"
4. Choose "Install Driver"
5. Plug in phone and on PC select option to install the driver
6. Then change "Default connect type" to "PC software"

After doing this I was able to do:

adb kill-server
adb start-server
adb devices

and view my device.

Answer 6

From the adb docs

When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer. This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog. This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher

So, unplug, wait, replug in the cable, and hit ok (on modal dialog that appears on your device)

If you hit cancel, the device will show up as offline via adb devices