Troubleshooting of android_adb.exe

Android_adb troubleshooting

 

 

1. The connection to ADB is down, and a severe error has occured. Or ADB server is out of date. Killing

Some people on the Internet say that the process of the pods is disabled, but I did not open the pods process. After thinking about it, I will provide you with a more general method.

Zookeeper does not occupy the adb.exe port. Find the occupied process and use the Process Manager to stop the occupied process. The specific steps are as follows:

1. Disable eclipse

2.disable adb.exe

Procedure:

Enter cmd in search, and then enter ADB kill-server on that DOS Interface

If Adb is not an internal command, add the path to the environment variable.

3.reactivate adb.exe

Procedure:

Enter ADB start-server on that DOS Interface

A. If you get the information daemon started successfully, congratulations, you have succeeded. You can start eclipse to continue your programming...

B. If the obtained information is ADB server is out of date. Killing...Verify that the endpoint is used, and the adb.exe must be enabled after the end is stopped.

Specific solution:

1.we know that the adb.exe port is 5037.

2. Enter netstat-Aon | findstr on the DOS interface."5037" press enter to see the result. We can see which process number is occupied. In this example, it is assumed that the process with process no. "4012" occupies port 503.7

3. Continue to execute the following command: tasklist | findstr"4012" press enter to see the process name. Then we can open the Process Manager and end the process. Then we can re-Execute step 3.