ADB server didn ' t ACK * failed to start daemon *

Problem Description: An error occurred in Eclipse Logcat

[2014-01-08 14:00:07-ADB] ADB server didn ' t ack[2014-01-08 14:00:07-adb] * Failed to start daemon *[2014-01-08 14:07:24-adb] adb server didn ' t A ck[2014-01-08 14:07:24-ADB] * Failed to start daemon *

Workaround: First find out if the ADB service is bound port problems, if there is a problem with the binding port, find out which process the port is occupied, and then kill the process.

1. Start the ADB service with CMD first. This time will prompt the startup to fail. E:\ANDROID-SDK-4.2\ANDROID-SDK\PLATFORM-TOOLS>ADB START-SERVERADB Server is an out of date.  Killing ... ADB server didn ' t ack* failed to start daemon. There are many reasons why a service fails to start, but it is generally a port binding failure. Let's take a look at the port binding information. , there is really a problem with the port binding. E:\ANDROID-SDK-4.2\ANDROID-SDK\PLATFORM-TOOLS>ADB Nodaemon servercannot bind ' tcp:5037 ' 3. Let's see which service takes up this port. There are 2 processes that occupy this port. E:\android-sdk-4.2\android-sdk\platform-tools>netstat-ano | Findstr "5037"  tcp    127.0.0.1:5037         0.0.0.0:0              LISTENING       5456  tcp    127.0.0.1:5037         127.0.0.1:1221         time_wait       0  TCP    127.0.0.1:5037         127.0.0.1:1222         time_wait       0

Kill the process of listening on port 5456 under the console

E:\android-sdk-4.2\android-sdk\platform-tools>taskkill/pid 5456 Error: Unable to terminate the process with PID 5456. Cause: This process can only be forcibly terminated (with/F option). E:\android-sdk-4.2\android-sdk\platform-tools>taskkill/pid 5456/f succeeded: The process of PID 5456 has been terminated.

Kill the process that caused the problem, and then execute the preceding command

E:\android-sdk-4.2\android-sdk\platform-tools>netstat-ano | Findstr "5037" e:\android-sdk-4.2\android-sdk\platform-tools>adb Nodaemon server

The results show that this issue is resolved!

ADB server didn ' t ACK * failed to start daemon *