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 — Ibukun Muyide, 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 7 · Answer 1 · answered Nov 30 '18 at 23:04

7

In my case:

adb kill-server
adb start-server

:)

answered Nov 30 '18 at 23:04

Mauricio Porto

71
1
2

3

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 6 · Answer 2 · 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 5 · Answer 3 · answered Jun 08 '17 at 10:06

5

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

213
5
14

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,482
3
24
43

score 3 · Answer 5 · answered Oct 27 '15 at 07:08

3

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,652
8
54
85

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 3 · Answer 6 · edited Dec 18 '20 at 14:11

3

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

This company is turning evil.

5,021
5
34
58

answered Dec 01 '19 at 02:26

Sampat Sharma

71
1
3

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 7 · 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

63
1
1
5

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

3,328
3
29
29

score 0 · Answer 9 · 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 10 · 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 11 · 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

5,055
3
30
31

Greg Porceng · Answer 12 · 2023-01-11T00:11:34.120

0

If ADB is not recognized

If you can't get your 'adb' to recognize in Windows follow this guide to edit your path variables. Scroll to answer by Linh.

'adb' is not recognized as an internal or external command, operable program or batch file

Then follow above. And restart Android studio after the process is done. That worked for me.

edited Jan 11 '23 at 00:11

answered Jan 11 '23 at 00:11

Greg Porceng

1
2

score 0 · Answer 13 · answered Mar 27 '23 at 09:18

0

Just find where the adb is installed, just change the name of adb to something else and try again with adb devices. It will work

answered Mar 27 '23 at 09:18

Aakash V

43
7

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Apr 02 '23 at 21:49

score 0 · Answer 14 · answered Jun 09 '23 at 20:30

If you're getting this error:

rhradec@server.local ~/android/platform-tools $ ADB_TRACE=all ./adb devices
adb D 06-09 13:25:17 1229295 1229295 adb_trace.cpp:187] Android Debug Bridge version 1.0.41
adb D 06-09 13:25:17 1229295 1229295 adb_trace.cpp:187] Version 34.0.3-10161052
adb D 06-09 13:25:17 1229295 1229295 adb_trace.cpp:187] Installed as /RAID/atomo/home/rhradec/android/platform-tools/adb
adb D 06-09 13:25:17 1229295 1229295 adb_trace.cpp:187] Running on Linux 5.9.14-zen1-1-zen (x86_64)
adb D 06-09 13:25:17 1229295 1229295 adb_trace.cpp:187] 
adb D 06-09 13:25:17 1229295 1229295 adb_client.cpp:160] _adb_connect: host:version
adb D 06-09 13:25:17 1229295 1229295 adb_io.cpp:107] writex: fd=3 len=16 30303063686f73743a76657273696f6e 000chost:version
adb D 06-09 13:25:17 1229295 1229295 adb_io.cpp:81] readx: fd=3 wanted=4
adb D 06-09 13:25:17 1229295 1229295 adb_io.cpp:88] readx: fd=3 error 104: Connection reset by peer
adb: failed to check server version: protocol fault (couldn't read status): Connection reset by peer

It means the default port for adb server is being allocated for a process that is not responding.

That would probably be another adb server frozen and hanging around, but if you have no adb process running and you don't know what's locked port 5037, a quick workaround is to use adb with a different port, like:

adb -P 5038 devices

in my case, this worked perfectly for the Connection reset by peer error I was getting.

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

14 Answers14

Steps:

If ADB is not recognized

Linked