ADB disconnects during sideloading

/e/OS Devices Samsung
,
1

Hello,

I’m trying to upgrade to /e/OS on my Samsung S21. I’m nearing the end of the tutorial, switching from “Recovery mode” to “Apply update.” When I try to “sideload,” I get the error: “protocol fault (no status).” The phone is disconnected. However, the phone was connected just before. I’ve tried many things: adb kill-server / adb start-server / killing adb.exe in the task manager, etc.

I’d really appreciate some help; I’m so close to finishing!

Thanks!

image
image775×377 11.1 KB

2

When you say upgrade do you mean that you are attempting Upgrade of Android Version?

If yes it is likely expected that you should first update the recovery … so that the recovery matches the ROM you sideload.

For clarity maybe best to confirm “from what” you hope to change.

3

I’m trying to switch from Android to /e/OS.

My Android version is already up to date.

I’m trying to load the last community version : e-3.5-a15-20260214581400-community-a21s

Thanks for your help!

4

So have you definitely seen the colourful e-Recovery as opposed to the regular Android recovery you had before you started?

A clue for this case Your first boot into the custom recovery

1 Like
6

Yes, I’ve got the /e/ Recovery.
I get to apply update and ADB Sideload into it.

Thanks for the advice about power-shell et command-prompt. I tried both unsuccessfully.

7

What is the response to

adb version

So this is Android 12?

This article covers the error ADB Sideload Error: Protocol Fault (no status)

8

Thank you for your help. The problem was the ADB version (it’s wa 1.0.31 version).
I am sorry to disturb.

/e/OS on my phone. One more step to say goodbye to and old toxic friend.

Have a nice day!

2 Likes