Android 4.2.2 adb can't find devices-ThrowExceptions

Exception or error:

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.2.2
  • Updated ADT and SDK through the SDK Manager
  • Checked ADB version, it’s at 1.0.31
  • Restarted PC and Tablet and Phone numerous times

When I run adb devices, it’s just blank. I have the same issue on Windows 8 and on Ubuntu 12.10, but on Ubuntu it shows my device and it says offline.

Are there any other steps I can take?

How to solve:

Try pre-installing the drivers for your devices. Make sure, under Windows, that your device is recognized in the System control panel first.

I use Windows 7 and my Galaxy Nexus wouldn’t be recognized by the system until I installed the device drivers before plugging them in. From the comments, this works on Windows 8 as well.

Galaxy Nexus drivers

Nexus 7


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


Just though Id share my experience, I had –

  • Unplugged and re plugged in the device
  • Installed the correct platform tools
  • Installed the correct Android bridge Turned USB debugging on and off
    and on and off an…
  • Tried WiFi but it said it was offline
  • etc. etc.

What fixed it for me was changing the device connection from Mass Storage to MTP. To do so, with the phone unplugged you go into –

“Settings” -> “Storage” -> Click the menu Button -> “USB computer
connection” -> “Media device (MTP)”

Hope this helps some one from going crazy!




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:


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. 🙂


Here is what I did (Galaxy S4 4.2.2):

  • go to Settings => about this device => click several times on “Version number”, that is to say something like “JDQ39.I9505XXBHYTGKDD” (not android version or anything else) ; here you will see that Google or Samsung have a lot of humour as you have to click until multiple times until having a toast displaying “You are at few clicks from being a developer” ; after something like 10 clicks, you have a toast “You are a developer”

  • Go “Development options” (in the “More” tab (rigjt tab of settings menu)) ; be sure that “USB debugging” is checked.

And it works ! Eclipse can see your S4(or any other device) 4.2.2 !


I had this problem today and fixed it by rebooting the Tab2 while leaving it plugged into the laptop/eclipse


Check if you have installed android-adb-tools in Ubuntu. If you do, the adb tool may be old. Uninstall and make an alias to the latest adb tool you download with the ADB plugin. To check the adb version do “adb version” if it’s 1.0.29 is the old, the latest and working for Android 4.2.2 is 1.0.31.

I made a lot of stuff until i realized this.


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


My solution used on cm10.1 nightly build on droid bionic, was after updating the newest usb drivers, using the Mass storage option (instead of the MTP option for USB computer connection), then unchecking and rechecking in developer options, “ADB over network” option. Then it did the RSA pop up dialog.


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.


You may use an old version of adb.exe. Update platform-tools.
You may have to set a new path to adb.exe as well.


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.


It’s working on windows 8 using Android 4.4.2

Reset your phone,

  • go to setting->about phone-> seven time click on build number.
  • go to back and go to developer options check USB debugging.
  • go to windows 8 start menu click on profile picture and click change profile picture.

Select devices and on Download over metered connections.
Connect your phone via cable your PC and wait.

Leave a Reply

Your email address will not be published. Required fields are marked *