ADB Server didn ' t ACK, failed to Start Daemon workaround (device not shown in Eclipse, device offline)

1. Turn off eclipse.
2. Turn Adb.exe off in Task Manager
3. Enter the ADB directory and then execute the ADB start-server to successfully execute the problem resolution

　　

The problem should be solved, but if adb start-server start up!

Finally, the reason for the port occupancy is found.

Here's how to fix it:

1.adb nodaemon server

To view the reasons that cannot be performed, output:

Cannot bind ' tcp:5037 '

2. Fixed a problem with the port! Yes, Port 5037 is occupied!

3.netstat -ano | findstr 5037

Find out who is taking up 5037 of the process and get the process PID.

4. Kill the process.

You can kill in Task Manager, or use the command: Taskkill/pid port number-F

The last discovery is Tfadb.exe This program takes up the port. Query signature Discovery This is the popular client!!

Really matchless pit father Ah, installed the popular students really have to pay attention to.

Note: This workaround comes from the network, thanks for sharing

ADB Server didn ' t ACK, failed to Start Daemon workaround (device not shown in Eclipse, device offline)