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

android eclipse adb
pengwang picture pengwang · Apr 18, 2011 · Viewed 132.6k times · Source

After updating the SDK, Eclipse shows this error:

ADB server didn't ACK, failed to start daemon.

When I run an Android application, it gives me the following:

Please ensure that adb is correctly located at 'D:\android-sdk-windows\platform-tools\adb.exe' and can be executed.

How can I fix this problem?

Answer

Horrorgoogle picture Horrorgoogle · Aug 7, 2011

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.

Related questions

Android Device Chooser -- device not showing up

I'm using Eclipse + ADT, and my physical device (listed below) is unlisted on Android Device Chooser. I have updated Eclipse and all of the Android packages. My phone is running Android OS 1.6, which corresponds to the target version listed in …

Read More
How to resolve "Waiting for Debugger" message?

I have HTC Comet connected to Eclipse with SDK 2.2. I do a debug build - the application does not run; though it does get installed on the device. On the device I get this message box on the Comet screen …

Read More
The connection to adb is down, and a severe error has occurred

Possible Duplicate: The connection to adb is down, and a severe error has occured I am currently trying to develop an application for Android in the latest release of Eclipse. When I try to build and run, the following comes …

Read More