Reasons for ADB startup failure and modification of ADB port number

When we use Android Studio, there are times when the ADB fails to open or starts.

ADB startup failure Reason: There are other programs that occupy the ADB default boot port number (like I have encountered, every time as long as the early start of the cool dog music, ADB will start failure ~ This is to let us concentrate on writing code, do not listen to the song side of the 0.0)

The solution to the problem is to open the terminal terminal of Android Studio

Use the following command:

Close ADB Service

Re-start the ADB service

ADB start-server

Result: (the terminal outputs the following code to indicate that the boot was successful)

ADB port (5037 for ADB default port) was modified to 5037

If it is occupied, the system will automatically match you to a port

* Daemon not running. Starting it now on port 5037 * * Daemon started successfully *

Reasons for ADB startup failure and modification of ADB port number