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 forcibly closed by the remote host
[2011-09-14 09:34:07 - DeviceMonitor]Connection attempts: 1

I am just making a simple "hello world" program.

Answer 1

I faced that after upgrading to Android Studio Bumblebee; and the cause that the adb server doesn't get started automatically, and required to start it manually.

Even I couldn't start it from Android Studio terminal as it blinks and loses the focus while typing.

So, did that instead from the operating system CLI/terminal by using adb start-server. Make sure to call that from AndroidSDK\sdk\platform-tools directory.

If the adb already started, you can try to kill it, then restart it:

adb kill-server
adb start-server

Prepend that with sudo for Unix based Operating systems.

Answer 2

Solution that worked for me on: Ubuntu 20.04, adb 33.0.1, Android Studio Bumblebee 2021.1.1:

1. Android Studio > Settings > Build, Execution, Deployment > Debugger: Set "Use existing manually managed server" with port 5038.

2. Close Android Studio
3. path-to-android-sdk/platform-tools/adb kill-server
4. path-to-android-sdk/platform-tools/adb start-server
5. Start Android Studio

Event Log shows that it cannot reach ADB server which is fine. When you run with command in point 3. and 4. adb starts on port 5037. If Studio connected to manually started adb, it'd kill it. That's why 5038 (instead 5037) has to be set in Studio settings.

After next reboot you should just execute 4. and 5.

Answer 3

It seems this issue has no exact solution, because the cause of this issue is not same for everyone. However, if you have faced this issue recently in Android Studio Bumblebee (2021.1.1) and later, then the problem might have happened due to adb mDNS for wireless debugging.

To solve this issue, disable mDNS for wireless debugging from here:

Android Studio > Settings > Build, Execution, Deployment > Debugger > Untick "Enable adb mDNS for wireless debugging"

Update (19th March, 2022):

As mentioned in the issue tracker, this issue has been fixed in adb version 33.0.1

Answer 4

Latest version of android studio broke this for me.. adb connected just fine after reinstalling 2020.3.1.26, then I tried to upgrade it again just to see.. and yeah.. busted again. Going to version 2020.3.1.26 works for me now.

Answer 5

For me, it wasn't my antivirus or firewall. I had somehow created a bunch of unnecessary virtual network adapters that were interfering with ADB. If this is the case with you, go to Device Manager -> Network Adapter, right-click the virtual network adapters, and uninstall them. You can always easily recreate them.

This answer is what helped me:

How to remove extra host only network interfaces created by vagrant on windows 10?

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.

Answer 7

I know I'm 4 years late but my answer is for anyone who may not have figured it out. I'm using a Samsung Galaxy S6, what worked for me was:

1. Disable USB debugging

2. Disable Developer mode

3. Unplug the device from the USB cable

4. Re-enable Developer mode

5. Re-enable USB debugging

6. Reconnect the USB cable to your device

It is important you do it in this order as it didn't work until it was done in this order.

Answer 8

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

Answer 9

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 10

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 11

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 12

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 *