ADB cannot bind ' tcp:5037 ' adb server didn ' t ACK

When we use several different sources of ADB in the system, it is particularly easy to come up with the error described in the title:

ADB server is an out of date.  

The reason for this error is that the port that our ADB is bound to is occupied by other services, or that there are multiple services that occupy 5037 of ports, which prevents each other from working properly.

To confirm the above guess, you can use the following command:

[Email protected]:~$ adb nodaemon servercannot bind ' tcp:5037 '

The following is a look at those services that take up 5037 ports, find those services, and kill them using the KILL command.

To view port usage status, use the Netstart command:

To view the service ports that are already connected:

Netstart-a

View all services, using:

Netstart-ap

When used, it can be used with the grep command. For example, we want to see the service for Port 5037, so:

Netstat-ap|grep "5037"

Enter as follows:

(Not all processes can be detected, all non-user process information will not be displayed, if you want to see all the information, you must switch to the root user) TCP        0      0 localhost:5037          *:*                     LISTEN      25255/ADB       TCP        0      0 localhost:51695         localhost:5037          established 23836/adb       TCP        0      0 localhost:5037          localhost:51695         established 25255/ADB       

As we can see, there are multiple ADB services that take up 5037 ports and cause them to not work properly. Use the KILL command to kill all ADB processes and re-use ADB start-server to restart ADB.

[Email protected]:~/tools/adt-bundle-linux-x86_64-20140702/sdk/tools$ kill 23836[email protected]:~/tools/ Adt-bundle-linux-x86_64-20140702/sdk/tools$ Kill 25255

The above is the Ubuntu System processing method, window similar.

ADB cannot bind ' tcp:5037 ' adb server didn ' t ACK