[ACCEPTED]-Error "The connection to adb is down, and a severe error has occurred.-adb

Accepted answer
Score: 533

Try the below steps:

  1. Close Eclipse if running
  2. Go to the Android SDK platform-tools directory in the command prompt
  3. Type adb kill-server (Eclipse should be closed before issuing these commands)
  4. Then type adb start-server
  5. No error message is thrown while starting the ADB server, then ADB is started successfully.
  6. Now you can start Eclipse again.

It worked for me this 1 way.

Restart your phone as well!

Score: 106


Open Task Manager → Processes → adb.exe 3 → End Process → restart Eclipse

This worked 2 for me.


Open Task Manager → Processes 1 → eclipse.exe → End Process → restart Eclipse

Score: 24

Open up the Windows task manager, kill the 2 process named adb.exe, and re-launch your 1 program.

Score: 12

[2012-07-04 11:24:25 - The connection to 11 adb is down, and a severe error has occurred.
[2012-07-04 10 11:24:25 - You must restart adb and Eclipse.
[2012-07-04 9 11:24:25 - Please ensure that adb is correctly 8 located at '/home/ASDK/platform-tools/adb' and 7 can be executed

I realized the folder of 6 the project in Eclipse was closed. I expanded 5 the directory and the project launched. I 4 know this may sound like a "no-brainer". I 3 had the .java files open on the workspace, and 2 that was enough to make me think the project 1 was open.

Score: 10

I tried this using Eclipse Juno and it worked 4 fine:

  • From the dropdown of the Run icon, select option Run Configuration.
  • Make sure your project is selected
  • Go to tab Android
  • Under section Launch Action, select Launch Select the package name and voila! try running your application.

UPDATE: It also helps to kill the process 3 adb.exe from the task manager and restart 2 it. adb.exe can be found here: Android\android-sdk\platform-tools.

Good 1 luck

Score: 7

Update your Eclipse Android development 1 tools. It worked for me.

Score: 6

Make sure it's not running in the task-manager 3 processes. If so, end the process and then 2 start it from a command prompt as in a previous 1 answer. This worked for me.

Score: 4

I know this question has already been answered, but 13 thought I might add that I found the problem 12 to be folder permissions on my android-sdk directory.

I 11 tested it out by granting Full Control to 10 Everyone (dodgy, I know...), and the problem 9 went away. I am not sure yet what the specific 8 mix of permissions might be that it was 7 looking for, but I assume some or other 6 service in Eclipse didn't have execute permissions 5 on adb.exe. That said, I'm a complete noob 4 to this - just wanted to put it out there 3 in case someone else had some insights into 2 this.

I am running Windows 7, 64-bit, 4.2.0 1 Eclipse, and 20.0.0v201206242043 ADT.

Score: 4

In my situation: I have the same warning: The connection to adb is down, and a severe error has occured

I 3 have found the solution:

The adb.exe was 2 moved from: android-sdk-windows\tools\adb.exe to android-sdk-windows\platform-tool\adb.exe.

Only 1 thing. Move file adb.exe to \tools. And restart Eclipse.

Score: 4
  1. Go to the folder platform-tools in cmd folder platform tools 3 available in the Android folder where you 2 have Android backup files.

  2. Type the following

    adb kill-server


    adb start-server

    then 1 type

    adb devices
    adb kill-server

You can now see your device.

Score: 3

This problem has been plaguing me for days 20 until I finally figured out what was causing 19 it. It got so bad I couldn't even update 18 my apps even after trying all the above 17 suggestions.

HTC Sync also runs a process 16 called adb.exe. HTC Sync is an optional 15 program available when installing the HTC 14 USB driver. I had recently updated my installation 13 of the HTC bundle and apparently hadn't 12 installed HTC Sync before. Checking properties 11 on adb.exe in the Task Manager showed it 10 to belong to HTC Sync, not Android.

As soon 9 as I uninstalled HTC Sync from the control 8 panel the problem disappeared! (It's listed 7 separately from the USB driver so that can 6 stay.) I never saw more than one instance 5 of adb.exe running. I'm curious to know 4 if people having to kill the process from 3 Task Manager, check to see if it's actually 2 the Android process you are killing?

Please 1 read user comments (I too have a HTC Thunderbolt): http://www.file.net/process/adb.exe.html

Score: 2

Simply go in Task Manager (windows users) and kill the 8 abd.exe (it is remaining active somehow). After 7 that start Eclipse.

The error

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

happened 5 after installing plugin for Android of Netbeans. After 4 closing Netbeans the process abd.exe remained active. When 3 you want to start again Eclipse ... you will get 2 the error.

You have to manually kill the 1 adb.exe and then start Eclipse.

It worked for me.

Score: 2

I had the same problems, and it turned out 4 that my antivirus program (Comodo) sandboxed 3 the adb.exe, and that is why it didn't work. I 2 closed the antivirus, and it worked just 1 fine. Consider that.

Score: 1

My problem was that my firewall was preventing 1 ADB from binding to the port it wanted to.

Score: 1

I had a similar problem. I found out that 11 there was another adb.exe running which 10 was started from BirdieSync (Sync Tool for 9 Thunderbird). I found out with Process Explorer from Sysinternals, that 8 Windows was running another incompatible 7 adb.exe. Just put the mouse cursor above 6 the process (in Process Explorer), and 5 you'll see which adb.exe is started.

I had 4 to kill the BirdieSync process as well, because 3 it started the wrong adb.exe again.

Then 2 I could start the right adb.exe, and it 1 worked fine.

Score: 1

The killing of the mysteriously running 14 abd.exe worked. This sudden roadblock stopped 13 me for a long time. I was doing all sorts 12 of command line stuff and removed the lock 11 icon from my user folder, but nothing worked 10 until your simple suggestion of looking 9 for the abd in the running processes of 8 the task manager and killing it.

Another 7 newbie roadblock I discovered an answer 6 to: don't run Eclipse when any file other 5 than the main .java file is active. If you 4 run it when, for example, the main.xml file 3 is active, you will get unhelpful error 2 messages, an odd file created like main.xml.out, and 1 it wont run.

Score: 1

I had the same problem

  1. I entered Task manager -> find adb.exe -> end process
  2. Go to the Android SDK tools directory in Command Prompt double click adb.exe

That's all


Score: 1

If you are using the Genymotion emulator:

Make 4 sure that the SDK path used for Genymotion 3 is also the same path used for the Eclipse.

This 2 error also occurs if those two paths are 1 different.

Score: 1

I am running Eclipse Neon2. on Mac OS 10.12.4 24 and I experienced this issue after recently 23 upgrading my Android SDK to the latest "SDK 22 Tools" (v 25.2.5), "Platform tools" (v 21 26) and "Build Tools" (v 26) and 20 moving one of my development projects to 19 Android Studio.

Unfortunately none of the 18 many answers here worked for me.

What did work 17 was to create a separate copy of the Android SDK 16 in a different folder and then point Eclipse 15 to it via "Preferences --> Android". You 14 will have to use an older version of the 13 SDK as indicated in this SO answer.

Once you've downloaded 12 the separate version of the SDK and put 11 it in a different folder than your main 10 Android SDK, launch the SDK Manager (via 9 <separate-sdk>/tools/android) and install the required "Platform 8 tools", "Build-tools" and 7 Android versions. There are two important 6 things to observe here though:

  1. Make sure 5 that you do not upgrade your "SDK Tools" beyond 4 the version that's already installed!

  2. Make 3 sure that you install a version of the "Build 2 tools" that is less than 26!

Otherwise you may 1 run into this issue.

Score: 1

I found the path of the SDK (Preferences* → AndroidSDK Location) was 4 the cause. My SDK path was the following:

C:\Program Files (x86)\Android\android-sdk

The 3 spaces in the path is the problem. To get 2 it to work, you must change Program Files (x86) to Progra~2

The complete 1 right path is C:\Progra~2\Android\android-sdk.

Now it should work.

Score: 1
  1. Go to the tools folder of your Android SDK
  2. Run emulator.exe -avd <your avd>. It will take some time for the emulator to run.
  3. Once you see the homescreen on your emulator, open Eclipse and run your program again...


Score: 1

The previous solutions will probably work. I 8 solved it downloading the latest ADT (Android 7 Developer Tools) and overwriting all files 6 in the SDK folder.


Once you overwrite it, Eclipse 5 may give a warning saying that the path 4 for SDK hasn't been found, go to Preferences and change 3 the path to another folder (C:), click Apply, and 2 then change it again and set the SDK path 1 and click Apply again.

Score: 1

Close Eclipse

Use this in the terminal:

sudo killall -9 adb

Run 1 Eclipse.

Score: 0

maydenec is correct (in my case...). The 3 file was moved.

I even found this file:

C:\Program Files (x86)\Android\android-sdk\tools\adb_has_moved.txt

Which 2 explained this issue.

Suggestions in this 1 file:

  1. Install "Android SDK Platform-tools".
  2. Please also update your PATH environment variable to include the "platform-tools/" directory.
Score: 0

It worked for me to start my AVD emulator 4 first (from the AVD manager), and then to 3 run my program. The other stuff mentioned 2 here.

(Restarting the ADB server didn't work 1 though.)

Score: 0

I've deleted all my tasks from HTC task 1 manager and now it's working.

Score: 0

AndroidSDK → Platform ToolsKill did not work.

But after 1 restarting my computer, it worked.

Score: 0

Add android-sdks/platform-tools to the Windows PATH environment variable.


Score: 0

For Ubuntu users, you can run the following 1 command:

sudo apt-get install ia32-libs
Score: 0

Eclipse → preferencesAndroidNDK

Check the "NDK Location" path 2 is set correctly, and use the browse button 1 to set it.

Score: 0

Here is a script I run to restart adb (Android 1 Debug Bridge) server:

#!/usr/bin/env bash

## Summary: restart adb (Android Debug Brdige) server.

## adb binary full path

if pgrep adb >/dev/null 2>&1
    echo "adb is running"
    echo "terminating adb ..."
    $ADB_BIN kill-server
    if pgrep adb >/dev/null 2>&1
        echo "did not work"
        echo "kill adb processes by killall"
        killall -9 adb
        echo "terminated"
    echo "adb is not running"

echo "starting adb ..."

$ADB_BIN start-server

echo "adb process:"

echo `pgrep adb`

echo "done"

Score: 0

Devices window → toolbar more menu → Reset 2 adb

For displaying the devices window: Menu 1 WindowShow viewOtherAndroidDevices

Score: 0

Another error cause would be the fact you 2 might have set up adb.exe to run with administrator 1 privileges.

Score: 0

Nothing worked for me, even restarting a 4 computer. I couldn't install an app on my 3 device. But I solved this problem by myself:

Go 2 to DDMS and choose connected device. Now 1 try again!

Score: 0

Last time I faced this problem, was solved 6 with adb restart. If you have tried adb kill-server and 5 adb start-server with no luck you might want to try this. When 4 again I faced the same issue I tried all 3 the above answers, with no luck, and this 2 was the last option to try. It did work 1 like a charm.

Goto Android SDK Manager >> Install the essential packages.

Score: 0

I have tried "adb kill-server" and restarted 4 Eclipse too many times. I even rebooted 3 my computer. They don't work.

Finally, I 2 turned off test mode of my phone and turned 1 on again. Then everything looked fine.

Score: 0

I've tried the above methods, end the adb 3 process through task manager and all, it 2 didn't work. But when I ran the adb.exe 1 file as admin it worked fine.

Score: 0

Check if your firewall didn't add a rule 4 and blocked the connection to adb server. It 3 uses newdev.dll and your network. It just 2 happened here, I removed the blocking rule 1 from the firewall, and now it is fine.

Score: 0

I got the same error. My resolution is to 3 set the directory platform-tools to the system path and 2 then restart the OS.

Or in a DOS cmd prompt:

set path=%path%;c:\xxx\platform-tools

It 1 works for me.

More Related questions