0

When I try to start adb using the "adb start-server" command, the command line doesn't respond, and adb shows up for a second in the task manager, but then disappears. I've tried re installing, and a fresh copy of the SDK has the problem. When I type in "adb devices", the output is: "error: protocol fault (no status)" Any ideas on how I can fix this?

Also, when I update the SDK, I get this code: Starting ADB server failed (code -1).

enter image description here

6
  • Try asking on the android google group. You are more likely to get help there.
    – d3dave
    Commented Apr 26, 2014 at 19:59
  • Where is that located? Commented Apr 26, 2014 at 19:59
  • Are you sure that you are writing the adb commands at android sdk's adb installation path?
    – Devrim
    Commented Apr 26, 2014 at 20:01
  • Yeah, I'm pretty sure. I attached a screenshot. Commented Apr 26, 2014 at 20:02
  • @ElectronicGeek: Here: groups.google.com/forum/#!forum/android-developers
    – d3dave
    Commented Apr 26, 2014 at 20:06

2 Answers 2

1

Try running adb kill-server and then adb start-server again.

After that, adb devices should work correctly.

4
  • Ive done that. When i do adb kill-server it says that adb was never running. Commented Apr 26, 2014 at 21:30
  • I found this on xda-developers: forum.xda-developers.com/showthread.php?t=1011355. Perhaps give that a try? I've had problems with ADB on Windows too, where I'd have to restart it
    – user3514956
    Commented Apr 26, 2014 at 21:37
  • The problem for me is that adb doesn't even start. Commented Apr 26, 2014 at 21:49
  • Nevermind, I found out it was a problem with a parental controls software disallowing adb from running. Commented Apr 27, 2014 at 13:03
1

The problem was that my parental control software was interfering with adb.

1
  • Can you give an explained solution how to fix it, because I am also getting the same problem of yours. Commented Dec 1, 2021 at 20:07

Not the answer you're looking for? Browse other questions tagged or ask your own question.