Programmer algorithm practice must read, common Java API skills to share>>>
1. Sometimes when you use the ADB tool to connect to an Android device or simulator, you will be prompted with such a prompt as ADB Server Version (31) doesn’t match this client (41). As shown in the picture
The literal meaning of the prompt is that the current client version 41 does not match the server version. The current version is too high. Note that the client here is the version of the ADB program that has been installed on your computer, and the server, your server, is the device that will be connected
It’s said on the Internet that if there is such a mismatch, just download the corresponding version of ADB and replace the one you installed before. The corresponding Android studio path is the adb.exe program in the platform tools folder of your Android SDK directory
In fact, it’s not about solving problems. This is because my computer is installed with 360 mobile phone assistant, which occupies the port of ADB. Because of the uniqueness of socket (a socket can only be uniquely determined by protocol/network address/port number), a computer can only have one program associated with the corresponding port, and the corresponding port for ADB is 5037
In order to verify whether port 5037 is occupied, you can use netstat – ano | findstr “5037” to find the process ID of the port number corresponding to 5037, that is, PID
Sure enough, there is a corresponding process on port 5037. We try to find the corresponding process name and use tasklist | findstr “13656” to delete it
Through searching in the process, it is found that the 360 mobile assistant can only be unloaded
run again after uninstall: ADB devices succeeded
Of course, the premise is to ensure that the mobile phone is connected to the computer normally, and the USB of the mobile phone is in the debugging state
Similar Posts:
- The ADB command installs APK, and the installation problem is solved by daemon not running. Starting it now on port 5037
- How to connect Android mobile phone with ADB & reasons and solutions of unable to connect to 192.168.1.100:5555
- How to Solve React Native Error: Could not get BatchedBridge
- [Solved] Android ADB server didn’t ACK * failed to start daemon *
- Android ADB server didn’t ACK * failed to start d
- Android studio can’t find the emulator and can’t connect to the mobile phone. Prompt adb.exe start server ‘failed — run manually if necessary
- [Android test] solution to error closed after ADB shell carriage return
- How to Solve Android wireless debug Error
- adb server is out of date. killing [How to Solve]
- [Solved] Error: listen EADDRINUSE: address already in use 127.0.0.1:3000