The error "The connection to adb is down, and a severe error has occured." occurs when The adb startup problem occurs in Android development or The application is not successfully deployed. adbconnectionerror

The error "The connection to adb is down, and a severe error has occured." occurs when The adb startup problem occurs in Android development or The application is not successfully deployed. adbconnectionerror

First, I want to test the application today. If there is no problem, I will proceed with the next step,

The connection to adb is down, and a severe error has occured.

 

Some solutions on the Internet:

 

1. In Eclipse, select "help-> Check for update" and select "update ADT. After completing the preceding operations, restart Eclipse!

2. Enter the root directory of adb in cmd, type adb kill-server, type adb-startserver, and restart Eclipse.

3. Kill the adb.exe process in the task manager and restart Eclipse. If adb.exe cannot be killed, check whether the pod is running. Disable the pod and try again.

4. In the SDK folder that you have installed, see adb.exe in the platform-toolsfolder. If not, create a new folder, platform-tools, and copy all the files in tools to platform-tools.

5. After installing the mobile phone driver, close the wrist bean folder and restart eclipse. Similar programs such as wrist bean clips should not be opened at the same time as eclipse! You can also turn off the process of pods in task management.

6. The simulator is sometimes unstable. Sometimes you have to configure the development environment again, or you have to delete the simulator and create a new simulator.

7. The default port may be occupied. In cmd, enter netstat to view the port, disable the conflicting program, or set a new port.

8. Add the platform-tools directory and tools directory to the Path environment variable.

9. Switch Eclipse to DDMS mode, and restart ADB and Eclipse.

10. Open the SDK and download the API, android SDK Tools, and android SDK platform-tools before configuring Eclipse.

11. Enable usb debugging.

12. Restart your computer.

13. Shut down the cool dog, restartADB, and restart eclipse.

14. If the previous method still fails, we recommend that you reinstall a new system. You 'd better change the system.