Adb Error (Error: Protocol Fault (Couldn't Read Status): Invalid Argument)

adb error (error: protocol fault (couldn't read status): Invalid argument)

None of mentioned solutions work, seems like something wrong with windows, finally i ended up with resetting my windows 10 and issue resolved.

android - error: protocol fault (couldn't read status): connection reset

I simply did a System Restore to a time before I started port forwarding to TCP 5554, and started adding new firewall rules. ADB daemon started at TCP port 5037 and that was it.

8:18 AM * daemon not running; starting now at tcp:5037

8:18 AM * daemon started successfully

Android studio build application error: protocol fault (couldn't read status)

Surprinsingly, creating a script which contains the following code and executes each time my computer start solved the problem :

adb kill-server
adb start-server

I added the script here : C:\Users[name]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs and it runs at each start (before I can open Android Studio)

adb devices return error: protocol fault (no status)

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.

adb error: protocol fault (status 48 54 54 50?!)

The status XX XX XX XX part of the adb's protocol fault error message is not really a "status". It is just a hex encoded content of the first 4 bytes of the response that adb got back when it tried to connect to a port (which it most likely assumed belonged to an emulator instance). Your reads 'HTTP' which suggests that you have a web server running on a non-standard (for a web server) port.

Use netstat -b command to find what it is and kill it.

Related Topics

Leave a reply