
What gives?!Įdit, 16:41 GMT: An update to Platform-tools 16.0.2 was just released. He didn't install from the bundle he installed ADT into Eclipse, the old-fashioned way, but I doubt that would make a difference. I even copied his adb.exe and dll's and tried that and it still wouldn't work on mine. Weird thing is, my colleague can get the popup to show on those same devices without any trouble. I even completely re-installed the SDK from the ADT bundle. I'm using the standard 'Android ADB Interface' drivers from the SDK, but have also tried the 'Android Composite ADB Interface' and 'Samsung Composite ADB Interface' drivers too. Have tried using different USB ports and cables.


The Nexus One, being <4.2.2, works just fine with adb, but all the 4.2.2 devices show as 'offline' in adb, and I have NEVER seen the RSA security dialog pop up on the devices, even after several restarts of ADB (using I have four 4.2.2 devices to test with, a Galaxy Nexus with unlocked bootloader but not rooted, and Nexuses One, 4, 7 & 10, all stock. My development machine is running Windows 7, 圆4. I updated SDK Tools to 21.1 and Platform-tools to 16.0.1. I hope my answer saves your from the traumatic experience I went through while troubleshooting magical ADB for an entire day! :)Įdit: Fixed! Looks like there are very many possible causes for this. (2.0.0.1), where a race condition issue has been fixed! : Please prefer this ADB kit (exe and dll files), compared to 's ADB kit (2.0.0.0), since it has an updated version of (Please backup the same folder before, just in case.) Go ahead and replace the following 3 files in yourĬ:\Users\\AppData\Local\Android\Sdk\platform-tools Tried a different USB cable (and USB port)Īnd even uninstalled and re-installed Android studio!įile downloaded by the official SDK tool manager was corrupted! So I used to get windows error code 0xc0000142 on launching adb.exe from command prompt! :(įor future readers (and victims xD) of the above ADB problem, please do the following:ĭirectory into the system path environment variable. Installed various unnecessary C++ re-distributables Turn off and turn on USB debugging on phone multiple timesĮxperimented with "MTP", "PTP", "Midi" and "Charging" modes to see if ADB detects something.Ĭhecked my anti-virus software to see if adding exceptions to the adb directory works.

I had tried all these (from different SO answers) and no devices showed up when phone was connected to PC. On Android Studio while trying to "run" the app onto the phone. "Unable to detect adb version, adb output:" Preface: Although my answer focuses on Android Studio's perspective of ADB errors, I'm sure it is helpful for Windows ADB debugging in 's answer helped me look in the right direction.
