Android ADB server didn’t ACK * failed to start d

Programmer algorithm practice must read, common Java API skills to share>>>

The problem of ADB server didn’t ack will annoy many novice friends. I have encountered this problem when I first started Android, but I don’t know how to solve it with Baidu or Google. Many novice friends in the group will ask this problem. To be honest, I don’t have an ultimate solution to this problem, Ha ha), I didn’t meet him and didn’t take him seriously. Today, even today, I opened eclipse, connected my mobile phone and prepared to debug the program. The following information appeared


Then I do it according to his requirements, restart eclipse and ADB, and then confirm whether the path of ADB is correct. When I run the program again, it still can’t work. Then I started Baidu. A friend said to run ADB kill server under DOS first (you must configure your ADB path in the environment variable or enter the directory of adb.exe), Then in the ADB start server, when I run the ADB start server, DOS will display the following information


Then I still couldn’t run the program, and I couldn’t do it again and again. Some friends said that they found adb.exe in the task manager, then shut it down and restart eclipse. I opened the task manager and found that there was no adb.exe at all. At this time, my face was full of tears, and then I calmed down, I know that some friends encounter this error because Peapod software occupies the port of adb.exe. Peapod is not installed in my computer at all. Then I want to see who occupies the port of ADB. I found out from the Internet that the port of adb.exe is 5037. Next, I will introduce the solution to you

check who has occupied port 5037, start — run — CMD to the command prompt, enter netstat – AON | findstr “5037”, as shown in figure

we can’t see who is occupying port 5037 from the above. We need to find the application occupying the port according to the following PID (2748), and enter tasklist | findstr “2748”, As shown in the figure below, note: port 5037 here is correctly occupied by adb.exe. If it’s you, it’s other applications

end the process, enter taskkill/F/T/im your process name, such as adb.exe, as shown in the figure below. When reconnecting the mobile phone, you will find that the program is running

Although this problem is not a big problem, it is also a thorny problem for novices, so I will record my own method to solve this problem here, hoping to give a little help to people who encounter this problem. If I write an article to help you, please help me with the article, thank you

Similar Posts: