Adb server is out of date. killing...

From: http://blog.csdn.net/id19870510/article/details/8489486

1: A strange problem found during android debugging today

[Html]View plaincopy

1. C: \ Users \ xxxx> adb start-server
2. Adb server is out of date. killing...
3. ADB server didn't ACK
4. * Failed to start daemon *

Adb reports an error no matter whether shell devices or logcat is executed.

[Html]View plaincopy

1. Adb server is out of date. killing...

The source is that the adb server is not started.

Go to stackoverflow and check the analysis as follows:

[Html]View plaincopy

1. C: \ Users \ xxxx> adb nodaemon server
2. Cannot bind 'tcp: 8080'

Failed to bind the adb server port

Continue to check which port is occupied

[Html]View plaincopy

1. C: \ Users \ xxxxxx> netstat-ano | findstr" 5037"
2. TCP 127.0.0.1: 5037 0.0.0.0: 0 LISTENING 4236
3. TCP 127.0.0.1: 5037 127.0.0.1: 49422 ESTABLISHED 4236
4. TCP 127.0.0.1: 49422 127.0.0.1: 5037 ESTABLISHED 3840

Open the task manager and kill the 4236 process. OK

Now the problem has been solved.