Menu
My ADB stopped working recently. All commands results in error: protocol fault (no status).
Follow trace.
adb devices
system/core/adb/adb.c::main():Handling commandline()
system/core/adb/adb_client.c::adb_query():adb_query: host:devices
system/core/adb/adb_client.c::_adb_connect():_adb_connect: host:version
system/core/adb/sysdeps_win32.c::socket_loopback_client():socket_loopback_client
: could not connect to tcp:5037
system/core/adb/adb_client.c::adb_connect():adb_connect: service host:devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
system/core/adb/adb_client.c::_adb_connect():_adb_connect: host:devices
system/core/adb/sysdeps_win32.c::socket_loopback_client():socket_loopback_client
: port 5037 type tcp => fd 101
system/core/adb/transport.c::writex():writex: fd=101 len=4: 30303063 000c
system/core/adb/transport.c::writex():writex: fd=101 len=12: 686f73743a646576696
36573 host:devices
system/core/adb/transport.c::readx():readx: fd=101 wanted=4
system/core/adb/sysdeps_win32.c::_socket_set_errno():_socket_set_errno: unhandle
d value 10054
system/core/adb/transport.c::readx():readx: fd=101 error 22: Invalid argument
system/core/adb/sysdeps_win32.c::adb_close():adb_close: 101(lo-client:5037)
system/core/adb/adb_client.c::adb_connect():adb_connect: return fd -1
error: protocol fault (no status)
429
How to Answer This doesn't always work, it sometimes gives out a "error: failed to read response from server" if such think happens, rebooting is required. Just Restart PC and everything mean Android Studio and your android Device its working for me As you may found in source code of ADB, something raised up this error:
This typically means, that your ADB service or your driver is outdated. I recently got the same error, after installing a driver for the Moto X. I previously had the ADB and Fastboot quick install. I installed the driver, saw that the Moto X still wasn't registered, so uninstalled the driver again. Ten I got this error message.
Then you have to disable the ADB integration via "Tools -> Android" (uncheck). After that, restart you adb server by using adb kill-server or simply restart your computer. Show activity on this post.
Click the "End process" menu item; Open a command prompt and type adb start-server and it will start the adb again. This is not a solution, even if it might work in some cases. It does not fix the cause why the issue occurs in the first place.
I had the same issue and found the problem: Android Studio.
Open the Android Studio menu Tools -> Android and uncheck Enable ADB integration.
adb devices should work (you might need adb kill-server first).
Then you can re-enable ADB integration in Studio.
81
This typically means, that your ADB service or your driver is outdated.
Since the drivers aren't updated most of the time, make sure you've installed the latest version of your Android SDK Platform-tools via the SDK Manager:
45
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
