When I type in "adb devices", the output is "error: protocol fault (no status)". The adb functionality is broken in both Android Studio and Eclipse, so it's a problem with the connection, I believe. I tried to kill adb.exe from the Task Manager, but it's not listed in the processes. Any tips?
asked Apr 24, 2014 at 15:23
Add a comment
|
4 Answers
Try to open the this directory :
adt-bundle-windows-x86_64-20130917\sdk\platform-tools
Hold shift + right mouse click. Select open command prompt here.
After that,
in the command window type
adb kill-server
and then
adb start-server
then,
adb devices
See if the adb is started and if your device is visible on eclipse or android studio.
answered Apr 24, 2014 at 15:28
-
Thanks for the reply, but the problem still persists. The kill-server command returns: * server not running * Commented Apr 24, 2014 at 15:30
-
Try doing just adb start-server and see if it shows, deamon started Commented Apr 24, 2014 at 15:50
-
I tried that, it doesn't show anything, it just goes to the next input. Commented Apr 24, 2014 at 15:51
-
The output should come like this : * daemon not running. starting it now on port 5037 * * daemon started successfully * Commented Apr 24, 2014 at 15:52
-
Yeah, I think that's why it's not showing up in the process list. Any ideas on how to fix it? Commented Apr 24, 2014 at 15:52
My problem was my parental controls software. The adb.exe works fine with it disabled.
answered Apr 30, 2014 at 19:20
Same problem i faced in past, the solution worked for me is: Navigate to the plateform-tools(it is under SDK) and execute following commands on cmd.
C:\Android\android-sdk\platform-tools>set ADB_TRACE=1
C:\Android\android-sdk\platform-tools>adb start-server
I hope it will help you
Change your USB cable then it will resolve the issue.
answered May 14, 2016 at 12:51
