ADB processing universal solution
adb action device not found
Pre-operation is best done
Pre-operation, unplug the mobile phone cable, close Android Studio, mobile assistants and other programs that may start the adb process.
1. The most common solution is to find the program that occupies the ADB port first, then kill and restart the service.
1) Find the port that occupies the program (the port number followed by ADB defaults to 5037)
netstat -ano | findstr 5037
The following may appear as follows 4512 is the pid of the process
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 4512
2) Kill the process according to the displayed process pid
taskkill /f /pid 4512（占有5037端口号的id）
will show
成功: 已终止 PID 为 15644 的进程。
3) Enter adb start-server
adb start-server
If it returns Successful, it means that the successful return program can be enabled
adb start-server2. However, sometimes there will be no response after calling and other commands.
Only display the content below has been no feedback
* daemon not running; starting now at tcp:5037
_
At this time, there are the following steps
: 1) Restart the computer, let the computer actively enable the adb service
2) Repeat the above operation, first ensure that the adb process is killed, and then call adb nodaemon server, this command will take a while
When the loaded new key... may appear after the input
adb nodaemon server, the adb is already enabled at this time. When you perform the operation of connecting the cable, the command window also changes, indicating that the daemon process may be attached to the cmd window. At this time Do not close the command window, once closed, the adb guardian service will also be shut down
adb_auth_init...
loaded new key from 'C:\Users\{用户名}\.android\adbkey' with fingerprint {
密钥}
When this appears, you can actually connect the device by plugging and unplugging the device.
Sometimes it will always be in the state of adb_auth-init. At this time, you may need to restart the computer