Android adb stop working

Question

Until yesterday everything was working perfect until today that I connected my phone (just updated to Jelly Bean) and adb.exe stop working. If I execute adb.exe I can see the help but when I want to use any command it just run forever and no message is shown.

I tried with "kill-server" and "devices" and it runs forever, no message at all is displayed and I must terminate the process to close it.

I just connect the same phone to other PC that was fully functional and also adb.exe stop working. The strange thing is that adb.exe will not work any more even If I disconnect the phone and/or I connect my tablet. Adb.exe just got useless.

I was using the same phone yesterday (android 4.0), with my tablet (android 4.2) and adb.exe was working.

Adb.exe is not corrupted as I checked it MD5 and it is the same as in working pc (5787e5df1a68e7afea82d58e5f0d6549 *adb.exe).

I have Android Debug Bridge version 1.0.31 and Android SDK tools 22. I uninstalled android sdk tools and Installed again but when is near to finish it hangs because it launches adb.exe and again it will run forever.

Please any suggestion or help?

Answer 1

Try rebooting. Sometimes the USB drivers lock up. I work HEAVILY with ADB in my project at http://android-casual.googlecode.com and I find it to be one of three things when ADB locks up.. 1. USB drivers, or 2. adb_usb.ini needs an update, or 3. on new devices you have to "pair" them so that ADB can perform any action.

To pair, you can disconnect, reconnect and run "adb devies" to display the pairing on the device.

Answer 2

Not sure if you're still facing this issue, but for what it's worth I had the same kind of issue with adb.exe, and came across this post while trying to troubleshoot it. In my case, I wasn't using any physical Android devices, only the Emulator. Everything had been working fine and then suddenly adb.exe would no longer respond (couldn't get any output from any adb command - it just appeared to hang).

In the end, my issue turned out to be another application I had installed on my development machine. It was starting as a service, and was listening on the exact same port that the adb server runs on (5037), which appeared to be confusing it. Once I changed the application to use a different port, adb started working again and everything was fine.

Answer 3

Run command

where adb

I had such kind of situation.

In my case

where adb

gave output

C:\\Windows\\adb.exe D:\\AndroidSDK\\adt-bundle-windows-x86_64-20131030\\sdk\\platform-tools\\adb.exe

I tried to run adb from disk C, when Eclipse used second adb from AndroidSDK (from disk D).

I removed adb from strange path C:\\Windows\\adb.exe , and this solved this problem.

Answer 4

I got the same problem,my solution is going to cmd and paste adb.exe path,and then click enter button.

For example

D:\Android\Android\platform-tools\adb.exe