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

Question

I am unable to connect to my phone using adb. I am getting the following error:

D:\softwares\Development\Android\android-sdk-windows\platform-tools>adb devices -l
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: protocol fault (couldn't read status): Invalid argument

http://s18.postimg.org/7fdc8w9dl/screenshot_97.png

Previously i am getting this error in windows 8.1 then i have installed windows 10 and error resolved but now again i am unable to connect my cellphone with adb :(.

I am getting this error even if no device is connected.

Eclipse error:

[2015-10-24 13:25:02 - ddms] Failed to initialize Monitor Thread: Unable to establish loopback connection
[2015-10-24 13:25:02 - adb] error: protocol fault (couldn't read status): Invalid argument
[2015-10-24 13:25:02 - ddms] 'D:\softwares\Development\Android\android-sdk-windows\platform-tools\adb.exe,start-server' failed -- run manually if necessary

Update: Even adb tcp is also not working so i think this is not a driver issue.

ADB traces http://s24.postimg.org/mtfdwf3id/screenshot_99.png

reinstall your device drivers correctly. That may resolve this problem. — Pragnesh Ghoda シ, Oct 24 '15 at 08:18
see this:http://stackoverflow.com/questions/21049253/adb-devices-return-error-protocol-fault-no-status — KishuDroid, Oct 24 '15 at 08:21
I am getting this error even if no device is connected I don't think its a driver issue — H4SN, Oct 24 '15 at 08:22
try running the emulator and run the command, if its the same then its not the device, its is either your software or something else — Muyide Ibukun, Oct 24 '15 at 08:27
I have also tried to download fresh adb but still result is same — H4SN, Oct 24 '15 at 08:38
You can see this issue for help. https://code.google.com/p/android/issues/detail?id=219085 — DysaniazzZ, Dec 12 '16 at 03:39

score 5 · Accepted Answer · answered Jul 19 '17 at 07:19

5

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

answered Jul 19 '17 at 07:19

H4SN

1,392
3
22
43

score 5 · Answer 2 · answered Nov 30 '18 at 23:04

5

In my case:

adb kill-server
adb start-server

:)

answered Nov 30 '18 at 23:04

Mauricio Porto

51
1
2

9

Welcome to Stack Overflow. While these commands may answer the question, providing additional context regarding why and/or how this code answers the question improves its long-term value.[How to Answer](https://stackoverflow.com/help/how-to-answer) – Elletlar Nov 30 '18 at 23:39
This is good enough for me, great job and welcome :) – Eman Nov 19 '20 at 19:32
1

This doesn't always work, it sometimes gives out a "error: failed to read response from server" if such think happens, rebooting is required. – Chepech Feb 24 '22 at 00:52

score 4 · Answer 3 · answered Jun 08 '17 at 10:06

4

Just Restart PC and everything mean Android Studio and your android Device its working for me

answered Jun 08 '17 at 10:06

Muhammad Natiq

203
4
14

score 2 · Answer 4 · answered Oct 27 '15 at 07:08

2

As you may found in source code of ADB, something raised up this error:

     if (!ReadFdExactly(fd, buf, 4)) {
         *error = perror_str("protocol fault (couldn't read status)");
         return false;
     }

Try to export export ADB_TRACE=all

And rerun adb devices

With this env variable you will see much more info

answered Oct 27 '15 at 07:08

Laser

6,291
7
49
78

1

How to export ADB_TRACE ? I am using windows – H4SN Oct 27 '15 at 13:37
@H4SN `set ADB_TRACE=all` – Laser Oct 27 '15 at 13:52
where i need to set ADB_TRACE-all ? – H4SN Oct 27 '15 at 14:09
@H4SN in `cmd` (console) before running `adb` – Laser Oct 27 '15 at 14:15
You have to type '=' instead of minus – Laser Oct 27 '15 at 15:18
Let us [continue this discussion in chat](http://chat.stackoverflow.com/rooms/93561/discussion-between-h4sn-and-arseniy). – H4SN Oct 28 '15 at 06:55
@ Arseniy Same problem with as admin – H4SN Oct 28 '15 at 14:42
Finally i ended up with resetting my Windows 10 and everything works fine. – H4SN Feb 15 '16 at 06:42

score 2 · Answer 5 · edited Dec 18 '20 at 14:11

2

I was also getting this error so here's how I solved it. I killed the adb process and start again.

Steps:

Open the Task manager (Windows);
- You can press Ctrl+Shift+Esc and task manager will be opened.
Find adb.exe and right click on it. Click the "End process" menu item;
Open a command prompt and type adb start-server and it will start the adb again.

edited Dec 18 '20 at 14:11

Kroltan

4,812
5
34
56

answered Dec 01 '19 at 02:26

Sampat Sharma

46
1
2

Excelente, funcionó de maravilla, nada de reiniciar PC, Gracias – Adonys Jan 05 '22 at 15:23
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. It is just a simple retry. – arkascha Jan 28 '22 at 13:20
IT IS a solution because explain why this is happening . Another adb process is running in zombie mode and needs to be killed – Delcasda May 12 '22 at 18:52

score 2 · Answer 6 · answered Jan 14 '20 at 09:56

2

In your task manager, find adb.exe > right click and End Process.

solved this way for me..

answered Jan 14 '20 at 09:56

Mustafa Al Ajmi

33
1
4

score 2 · Answer 7 · answered Feb 17 '21 at 11:11

Although not exactly the same error as the OP, I was getting a similar error in Windows:

❯ adb.exe start-server
error: protocol fault (couldn't read status): No error

This error was related to my port proxy. It seems I had setup some rules that resulted in the adb client/server not being able to communicate with each other.

I was able to solve this by resetting my portproxy settings:

netsh interface portproxy reset

And now I can start the adb server:

❯ adb.exe start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully

score 1 · Answer 8 · answered Dec 27 '21 at 00:28

1

See my answer here, for me adb port 5037 was in use, killing the process using the port resolve the issue.

answered Dec 27 '21 at 00:28

piouson

1,580
1
15
24

score 0 · Answer 9 · answered May 27 '19 at 19:20

0

Simple fix, restart your computer and re-try :)

answered May 27 '19 at 19:20

Josh O'Connor

4,570
6
52
89

score 0 · Answer 10 · answered Dec 15 '20 at 11:03

You can get more info with:

export ADB_TRACE=all

This gave me the full log when connecting:

adb D 12-15 11:48:11  1014 18521 adb_trace.cpp:187] Android Debug Bridge version 1.0.41
adb D 12-15 11:48:11  1014 18521 adb_trace.cpp:187] Version 30.0.2-6538114
adb D 12-15 11:48:11  1013 18519 adb_client.cpp:155] _adb_connect: host:connect:192.168.1.109
adb D 12-15 11:48:11  1013 18519 adb_io.cpp:107] writex: fd=3 len=30 30303161686f73743a636f6e6e656374 001ahost:connect [truncated]
adb D 12-15 11:48:11  1013 18519 adb_io.cpp:81] readx: fd=3 wanted=4
adb D 12-15 11:48:11  1013 18519 adb_io.cpp:97] readx: fd=3 wanted=4 got=4 4f4b4159 OKAY
adb D 12-15 11:48:11  1013 18519 adb_client.cpp:189] _adb_connect: return fd 3
adb D 12-15 11:48:11  1013 18519 adb_client.cpp:364] adb_connect: return fd 3
adb D 12-15 11:48:11  1013 18519 adb_io.cpp:81] readx: fd=3 wanted=4
adb D 12-15 11:48:11  1013 18519 adb_io.cpp:91] readx: fd=3 disconnected
error: protocol fault (couldn't read status length): Undefined error: 0

I resolved the issue by updating my Platform Tools from the SDK Manager in Android Studio.

$ adb --version
Android Debug Bridge version 1.0.41
Version 30.0.5-6877874

score 0 · Answer 11 · answered Nov 16 '21 at 16:23

Uninstall and re-install ADB from Android Studio and check your path to make sure you aren't pointing to any other ADB installations.

I had no other installations but for some reason the ADB instance I had was corrupted (v 1.0.41).

I went to Preferences >> Android SDK >> Unchecked the installed version >> Clicked next to uninstall.

Then I went back and re-checked the box to install it again and it worked. Still version 1.0.41

Muhamed Riyas M · Answer 12 · 2022-04-12T14:52:57.870

0

I had a similar issue after updating android studio.

None of the above solutions are worked.

https://developer.android.com/studio/releases/platform-tools

I solved it by downloading platform-tools from the above link. And replaced the contents of my android SDK's platform-tools with downloaded one

edited Apr 12 '22 at 14:52

answered Apr 12 '22 at 14:20

Muhamed Riyas M

4,861
3
27
30

score -1 · Answer 13 · answered Jun 01 '19 at 07:44

-1

run the adb.exe and then again try with this command i got same issue with my asus max pro m1 device after doing that

answered Jun 01 '19 at 07:44

Mizan Hosen

1
3

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

13 Answers13

Steps:

Linked