Android doc inside ADB connection problem solving method

The first is to ensure that there are nets on both sides of the connection

The second is often said on the Internet 1, adb kill-server

2. ADB start-server

3. ADB remount

However, when running adb remount It is possible to prompt

C:\USERS\A123>ADB server is an out of date. Killing
ADB server didn ' t ACK
Could not start server this error

3. Workaround:

In the cmd window:
C:\users\lizy>adb Nodaemon Server
Cannot bind ' TCP:5037‘


C:\users\lizy>Netstat-ano | findstr "5037"
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING8516
TCP 127.0.0.1:5037 127.0.0.1:59163 time_wait 0
TCP 127.0.0.1:5037 127.0.0.1:59164 time_wait 0
TCP 127.0.0.1:5037 127.0.0.1:59167 time_wait 0
......
C:\users\lizy>tasklist | findstr "8516"
Sjk_daemon8516 Console 1 3,071 K

Oh, it turns out that the Sjk_daemon process accounted for the ADB port.

C:\users\lizy>tasklist




Image name PID Session Name session# Mem Usage
========================= ======== ================ =========== ============
System Idle Process 0 Services 0 K
System 4 Services 0 1,128 K
Sjk_daemon 963Console 1 3,071 K
Tasklist.exe 1260 Console 1 5,856 K


To kill this process:
C:\users\lizy>taskkill/f/pid 963

If this command prompts for no permission, then you can go toWindows Task Manager, "Process" window, find this process and kill it.


Run the ADB devices again, there is no problem.
C:\USERS\LIZY>ADB devices
4df7f482396a301d Device

Android doc inside ADB connection problem solving method