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

103,250

Solution 1

I just got the same problem and to fix it, I opened the task manager and killed the adb.exe process, then I restarted Eclipse.

Solution 2

Reinstall everything??? no way! just add the path to SDK tools and platform tools in your classpath from Environment Variables. Then restart Eclipse.

other way go to Devices -> Reset adb, or simply open the task manager and kill the adb.exe process.

Solution 3

I restarted eclipse and did the Project -> Clean -> select your project One of them fixed my problem with adb

[2011-12-31 10:50:45 - HelloAndroid] Android Launch!                      good

[2011-12-31 10:50:45 - HelloAndroid] adb is running normally.             good

[2011-12-31 10:50:45 - HelloAndroid] Could not find HelloAndroid.apk!     bad

Thanks for the help. On to the next problem (sigh)

Solution 4

Sounds a bit familiar with my problem: aapt not found under the right path

I needed to clean all open projects to get it working again...

Solution 5

I had exactly the same problem with you. And after two days wondering why this occurs to me, I finally got through this by moving the adb.exe from the unreliable software list of the COMODO anti-virus to its reliable software list. At that time, I had tried at least 5 kinds of measures to make the adb work, including all above...

Share:
103,250
ariets
Author by

ariets

I am a Tech Lead at Disney Streaming Services working on the Disney+ Android application.

Updated on February 01, 2020

Comments

  • ariets
    ariets over 4 years

    Possible Duplicate:
    The connection to adb is down, and a severe error has occured

    I am currently trying to develop an application for Android in the latest release of Eclipse. When I try to build and run, the following comes up:

    [2011-02-17 17:08:03 - <ProgramName>] The connection to adb is down, and a severe error has occured.
    [2011-02-17 17:08:03 - <ProgramName>] You must restart adb and Eclipse.
    [2011-02-17 17:08:03 - <ProgramName>] Please ensure that adb is correctly located at 'C:\<sdk-directory>s\platform-tools\adb.exe' and can be executed.
    

    Now, I have updated the ADT plugin, I have the latest version of the Android SDK; adb.exe is, in fact, in the platform-tools directory and can be executed. I've tried everything I found on Google:

    • I tried adb kill-server and adb start-server
    • I tried to run it with an without an emulator started
    • I have the given directory in my PATH (I tried with just the platform-tools in the path and I tried with having both platform-tools and tools in my PATH).

    Notes: I am running Windows 7. Also, I have previously tested apps in Eclipse. This error is new to me since upgrading the SDK.

  • ariets
    ariets about 13 years
    Okay, so I shut down Eclipse and then ran it as administrator. I uninstalled the ADT, and then re-installed it. Still getting the same problem.
  • ariets
    ariets about 13 years
    By clean, do you mean right clicking on the project, going to "Source" and clicking "Clean up..."?
  • ariets
    ariets about 13 years
    The SDK location is pointing to the root of my SDK on my device. I tried to edit it to see if setting it to the platform-tools location would work, but it would not allow me (as I expected). However, the error message stated: "Could not find folder 'tools' inside...[directory]" Is it suppose to say tools? Or something else? Thanks!
  • WarrenFaith
    WarrenFaith about 13 years
    no, I mean Project -> Clean -> select your project
  • Adeem Maqsood Basraa
    Adeem Maqsood Basraa about 13 years
    solve the problem for me stackoverflow.com/questions/4072706/…
  • IgorGanapolsky
    IgorGanapolsky over 12 years
    @NickT: Eclipse does not have issues finding the android SDK if you point it to the right directory.
  • Radu
    Radu over 11 years
    Did it without even restarting Eclipse, just unplugged the phone and plugged it back in.
  • Jim In Texas
    Jim In Texas over 11 years
    I tried everything until I saw this answer. Just cleaning fixed the problem. I'd give you a hundred upvotes if I could. thanks!
  • Hardik Joshi
    Hardik Joshi about 11 years
    its worked for me.. thanks.
  • Arthur Kushman
    Arthur Kushman about 11 years
    For those who can't run, even after restarting and cleaning. go to the /sdk/platform-tool/ via terminal, to make adb tool executable write sudo chmod 777 adb. It`s helped me, good luck.
  • Admin
    Admin over 10 years
    Thanks for the COMODO tip. What worked for me was from COMODO -> Defence+ -> ViewActiveProcessList right click on adb.exe and emulator-arm.exe and select "Add to Trusted Files". Then kill those processes and restart eclipse.
  • Mahdi
    Mahdi about 10 years
    I dont have that service runned on my system. why? :(
  • Muneeb Mirza
    Muneeb Mirza over 8 years
    That worked for me too!