Five situations and solutions that caused adb to fail to start
- 2020-06-19 11:41:33
- OfStack
1, adb server out date...
Solution: Various reboots (computer, eclipse)
2, check whether the port is occupied: enter the command adb nodaemon server
3. Find the process occupying the port: netstat-ano | findstr "5037" or netstat-a-o 5037
4. Kill the process tasklist /fi "pid eq ****" or use the task manager to kill the process
5. Generally, it is caused by qq, Pea pod, 91 and other mobile phone assistants. It can be closed