Error: “Adb connection Error:An existing connection was forcibly closed by the remote host”

Question

When I tried to reset my adb the following error occurs:

[2011-09-14 09:34:06 - DeviceMonitor]Adb connection Error:An existing connection was fo         


        

Answer 1

Window->Show View->device (if not found ->Other->Device) in right most side, there is arrow, click that, you will see reset adb, just click and enjoy!! It worked for me.

Answer 2

Looks like the installed driver was in bad state. Here is what I did to make it work:

1. Delete the device from Device Manager.
2. Rescan for hardware changes.
3. "Slate 21" will show up with "Unknown driver" status.
4. Click on "Update Driver" and select /extras/google/usb_driver
5. Device Manager will find the driver and warn you about installing it. Select "Yes."

This time the device got installed properly.

Note that I didn't have to modify winusb.inf file or update any other driver.

Hope this helps.

Answer 3

In my case, resetting ADB didn't make a difference. I also needed to delete my existing virtual devices, which were pretty old, and create new ones.

Answer 4

Well, its not compulsory to restart the emulator you can also reset adb from eclipse itself.

1.) Go to DDMS and there is a reset adb option, please see the image below.

2.) You can restart adb manually from command prompt

  run->cmd->your_android_sdk_path->platform-tools>

Then write the below commands.

adb kill-server - To kill the server forcefully

adb start-server - To start the server

UPDATED:

F:\android-sdk-windows latest\platform-tools>adb kill-server

F:\android-sdk-windows latest\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

Answer 5

Change to another USB port works for me. I tried reset ADB, but problem still there.

Answer 6

In my case, which none of the answers above stated. If your device is using the miniUsb connector, make sure you are using a cable that is not charge-only. I became accustom to using developing with a newer Usb-C device and could not fathom a charge-only cable got mixed with my pack especially since there is no visible way to tell the difference.

Before you uninstall and go through a nightmare of driver reinstall and android menu options. Try a different cable first.