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

User · Answer

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

User · Answer

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    Disable USB debugging Disable Developer mode Unplug the device from the USB cable Re-enable Developer mode Re-enable USB debugging 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

User · Answer

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

User · Answer

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- gt cmd- gt your android sdk path- gt platform-tools gt    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 gt adb kill-server  F  android-sdk-windows latest platform-tools gt adb start-server   daemon not running  starting it now on port 5037     daemon started successfully

User · Answer

Looks like the installed driver was in bad state  Here is what I did to make it work    Delete the device from Device Manager  Rescan for hardware changes   Slate 21  will show up with  Unknown driver  status  Click on  Update Driver  and select  extras google usb driver 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

User · Answer

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

User · Answer

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

[android] Error: "Adb connection Error:An existing connection was forcibly closed by the remote host"

Examples related to android

Examples related to eclipse