How to resolve the "ADB server didn't ACK" error? [duplicate]

I am trying to install my project on 5 AVD's at the same time, but I constantly get this error, I am executing it on Windows 8.1

"* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon"

I have tried reading all possible posts on stackoverflow concerning this error, and all of them just mention that try to kill the adb process and restart eclipse and then all will be fine. I have tried the method mentioned in the posts and along with that I have also turned off my security and firewall, so that there is no obstruction on the port 5037. Somebody please help me as I need to execute my project and I am not able to do so :(. For your reference I can provide the output of the following command "netstat -ano | findstr "5037""

 TCP    127.0.0.1:5037         0.0.0.0:0              LISTENING       7144
 TCP    127.0.0.1:5037         127.0.0.1:57410        ESTABLISHED     7144
 TCP    127.0.0.1:5037         127.0.0.1:57411        ESTABLISHED     7144
 TCP    127.0.0.1:5037         127.0.0.1:57414        ESTABLISHED     7144
 TCP    127.0.0.1:5037         127.0.0.1:57415        ESTABLISHED     7144
 ...

Somebody please suggest a workaround this problem, what might be the cause of this. Also you can take a look at the following image to infer what might be happening.


Solution 1:

Try the following:

  1. Close Eclipse.
  2. Restart your phone.
  3. End adb.exe process in Task Manager (Windows). In Mac, force close in Activity Monitor.
  4. Issue kill and start command in <sdk_folder>\platform-tools\
    • C:\sdk\platform-tools>adb kill-server
    • C:\sdk\platform-tools>adb start-server
  5. If it says something like 'started successfully', you are good.

Solution 2:

For anyone using OSX (I'm aware OP isn't): What worked for me in the end was removing the android settings folder in the home directory.

rm -Rf ~/.android

Solution 3:

For me it didn't work , it was related to a path problem happened after android studio 2.0 preview 1, I needed to update genymotion and virtual box, and apparently they tried to use same port for adb.

Solution is explained here link! Basically you just need to:

1) open genymotion settings

2) specify sdk path for the adb manually

3) adb kill-server

4) adb start-server