ADB not responding. You can wait more,or kill “adb

Question

I have installed Android Studio. Then I have updated the Android SDK. Now when I start Android Studio, this message pops up:

ADB not responding. You can wait more,or kill "adb.exe" process manually and click 'Restart'

The dialog has 3 options: Wait more, Restart and Cancel. But all of them gives me the same result, i.e. a message Waiting for ADB appears and I can't do anything with Android Studio.

I have to kill the program using windows task manager! I'm using windows 7.

Can anyone help me on this?

Answer 1

For me, on Windows 7, killing the ADB server and restarting it via command line did not help. It would not start up successfully.

>adb kill-server

>adb start-server
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *

So killing the adb.exe process via Task Manager was actually the easiest solution that case.

Answer 2

I ran into this problem and tried a number of solutions on my Mac without any success. I finally got to work with the commands below:

$ rm -rf ~/.android
$ killall adb
$ adb devices

Note that rm -rf ~/.android will remove any AVDs that you have configured, so don't take this step lightly. Personally I had to though and I'm not sure why. Hopefully this helps someone.

Answer 3

I had this problem and solved it by this way... I had a app in my pc that used adb... I tried to disable it but still my android studio's adb had problem after unistall that application and problem solved.

Answer 4

None of the above helped me completely. Although Oventoaster made me think. I had a couple of adb on my system. Removed them almost all.

I am running android studio on ubuntu 14.04 64 bit.

So I checked manually /home/xxxxx/Android/Sdk/platform-tools/adb

where xxxxx was my linux username

this gave

/home/xxxxx/Android/Sdk/platform-tools/adb: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

https://stackoverflow.com/a/27415749/4453157

solved it for me.

Answer 5

I run netstat -nao | findstr 5037 in cmd.

As you see there is a process with id 3888. I kill it with taskkill /f /pid 3888 if you have more than one, kill all.

after that run adb with adb start-server, my adb run sucessfully.

Answer 6

I had this problem on Windows 7. My situation is this through SDK Manager. I only download API 19 but I had not downloaded related Android SDK build-tools. So it occur this problem.

I went through SDK Manager download build-tools 19 to fix it. Hope to give you help.