ADB not connected, adb server didn ' t ack problem, resolution

ADB is not connected to a virtual machine, even if the adb kill-server command is executed?

If your error message is that ADB server didn ' t ack this way, the 5037 port is occupied.

Just find the process that occupies the port and kill it.

The following are the specific practices:

Address below: http://104zz.iteye.com/blog/1681183

The following conditions occur

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

Workaround:

Method One:

(1) View Task Manager, close all Adb.exe, or run->cmd, enter ADB kill-server in the command window

(2) Restart Eclipse

Method Two,:

If the method is not, you can check whether your computer has started such as: 91 mobile phone assistant, 360 mobile phone pea pod, etc. first shut him down, reconnect try, and then uninstall these software should be able to solve. Because these software may occupy the ports of Android phone and Eclipse connection start adb

Method Three:

5037 ports are occupied, you will also see the following prompt ...

So, it's like finding a lifeline. In the command line, first enter the following instructions to see 5037 this port is now occupied by who:

Netstat-a-O 5037

And then get a result like this, and it's really taken up, OH:

What is this 4792 on my machine, exactly what is the process, OK, then enter the following command to find out the real killer:

Tasklist/fi "pid eq 4792"

Then, the amount ... I was depressed ... It's the famous Pea pod:

ADB not connected, adb server didn ' t ack problem, resolution