Eclipse error "ADB server didn't ACK, failed to start daemon"

Solution 1:

Thanks, @jowett, I have solved my same problem, doing these steps

Step 1: CTRL+Shift+Esc to open the task manager, which has adb.exe process and end (kill) that process

Step 2: Now, close the eclipse, which is currently running on my computer.

Step 3: Again, restart eclipse then solved that problem.

For those using OS X

killall adb

For those using Windows

adb kill-server

should do the trick.

Solution 2:

I met same problem, though I didn't what caused this. Whatever, i find some clues and fixed finally.

When I open SDK and AVD manager, but find the AVD version(2.3.3) is not same with android lib version(2.3). So I create a new AVD with 2.3.

I fixed it by the following steps: 1. Open windows task manager and kill adb.exe process. 2. Close eclipse and restart it. Then it works.

Hope it helps.

Solution 3:

Command prompt (cmd.exe):

netstat -aon | findstr 5037

Find the process id of 0.0.0.0:

Make sure it's adb.exe:

tasklist | findstr 1980

Kill this process:

taskkill /f /t /im adb.exe

Get ADB back to normal:

Credit: blog post *Android ADB server didn't ACK failed to start daemon*

Solution 4:

These symptoms occur if you are using the Genymotion emulator (on Windows or Linux) at the same time as Android Studio:

adb server is out of date.  killing...
ADB server didn't ACK
* failed to start daemon *

Genymotion includes its own copy of adb, which interferes with the one bundled in the Android SDK.

The easiest way to fix seems to be to update your Genymotion Settings so it uses the same ADB as your Android SDK:

Just check the "Use custom Android SDK tools" option and enter your desired location.

Solution 5:

ADB will often fail if there is a newline in adb_usb.ini. Remove it, restart it, and that will often solve the problem (at least for me anyway).