Samsung - Galaxy S10e - beyond0lte - Documentation Suggestions

…Enter suggestions to improve documentation in this category. Do not raise bugs or issues here…

Just got an update from the LOS maintainer for the device that TWRP could create a problem …specifically it will cause issues on these devices and eventually even force users to wipe in order to boot up again after an OTA (this is due to TWRP messing with FBE encryption)
The suggested method by the maintainer is to avoid TWRP and instead use the Lineage recovery .

Checking with the team if the lineage recovery will work with the /e/ build and also if the /e/ recovery will be updated to accommodate these changes

Will also check how to add this to the documentation for the S10 devices

Hi @Manoj,

I plan to install /e/ on an S10e.
Do yo have any news on what is be the best recovery to use in order to install /e/ on Samsung S10e (I saw that there still some references to TWRP in the install doc).


PS: I hope it’s the right section to post this kind of question.

You can use the erecovery …download it from the same location where you get the s10e image

The documentation with an updates guide is ready but awaiting review for sometime now. Will try to get it published ASAP.


Hi I finally succeed to install /e/ on the S10e thanks to community support !

it was and “orange” ( french carrier ) device before

What we should change :

  • if the KG or RMM is “locked” the user has to boot once and change the date to seven days earlier ( we still need to clarify that ) otherwise we will get some kind of

only official release can be flashed

when trying to flash recovery , I also inserted a french ( Free mobile) sim card , I don’t now if this made the KG to “checking” mode

  • After the recovery is flashed , we have to tell to poweroff using BIX+VOLDOWN+ PWR and right after go in recovery with BIX+VOLUP+PWR , otherwise the recovery will be erased and the samsung recovery will be booted.
1 Like

I installed /e/ on Galaxy s10e Beyond0lte Exynos from a windows machine today. I would like to sugest an easyer method for people not fit for code.


  • /e/ build and recovery
  • TWRP
  • avb disabled vbmeta .tar and odin from here

Pre install instructions stay same.


  • power off phone
  • aktivate download mode
  • open odin (phone should be shown as “added”)
  • put TWRP.tar file as AP
  • put vbmeta.tar file in CP
  • start flash and immediately press Vol-Up+home+power
  • TWRP should start
  • swipe right for write mode
  • transfer /e/ recovery and /e/OS on phone or SD-card
  • go to install/Install Image
  • choose /e/ recovery file
  • hit reboot into recovery (/e/ recovery is booting)

From here it is the same steps than in the existing description.
Steps to install /e/OS from recovery

For me this was much easier than handling heimdal.


Thanks but we can only give instructions with open source tools , you have the graphical heimdall that could replace the CLI if you prefer


There is a warning saying “Do not install /e/OS on top of a higher version of stock OS.”

The documentation does not say what one should do if his S10e is running Android 12 “S” version, when the latest available /e/ version is R.

Hi @Cobus, welcome to this forum !

I clearly understand that you have 2 options :

  • Downgrade the device Stock OS
  • or Wait for an upgrade of /e/OS

Luckily there is one HowTo for your device series :
/How to/ install /e/ R on a samsung galaxy s10e already running android 12

Thank you for your quick reply, @piero !

I saw (and read) this thread about downgrading, but My CSC shows an “F” binary.
Sammobile has no frmware downgrade to Android 11 for CSCs with “F” binaries.

Looks like I have to wait for an upgrade of /e/OS…

It is a common warning, if you like playing, you could try, as it seems not to have big difference betwen android 11 and 12 device and system trees, that there were betwen 7 and 8

In case of problems, Odin can restore your device to his original state (note your firmware version code number included CSC to download it from sfirmware faster than sammobile or from database of your choice)

Thanks for your advice !
I may give it a try and post the results in another thread (it would be off topic here).

Anyway, I had the right advice (from you @piero), but other readers of the docuentation may need it too.
I think that a table with “What Android version do you run” entries and "what should you do to run /e/ version Q, /e/ version R, etc. outputs would make things clear.

Hello, Just a small glitch but with important consequences for new users/installers :

The documentation for installation of /e/os on Samsung s10 s10e s10+ is not using the last Heimdall link from lineage doc. The heimdall version linked in the /e/ os doc is not working. The Heimdall offered in Lineage OS doc is working.

The instructions of other samsung devices should also be checked for this.

1 Like


I’ve just installed the 1.6-s build on s10e using Ubuntu. There are also other successes for this phone with this build (here, there…)

NB : I used the heimdall I took previously from the LineageOS install page.

The documentation and install documentation must be updated:

  • my model is SM-G970F/DS (dual sim), documentation can add this model (as LineageOS has)
  • my model was running G971FXXSGHVI1 (Android 12) before flashing the ROM

Many thanks for all people making this build and documentation available.

Sometimes when you flash a custom ROM through Recovery on S10e you ended up stuck on boot screen logo. This happens because the firmware needed to be upgraded, there is a tutorial maded by LineageOS team teaching how to do that and it works perfect with e/os too. This happens on my phone and i fixed by upgrading the firmware.

Here is the link if anyone get stuck on the process:

1 Like

I had the problem during the installation that I got an error message when sideloading at the 47% point and the installation was aborted.
The message that was displayed:
"E:failed to verify whole-file signature
Update package verification took 57.6 s (result 1).
E:Signature verification failed
E:error: 21

Install from ADB completed with status 2.
Installation aborted."

It helped me to switch on ADB via the recovery screen: “Advanced >> Enable adb”.

After that, the installation worked without any problems.

1 Like

We managed to flash a Samsung S10e at or flash-party, but it has been hard.

First, it was “RMM” locked. So flashing with heimdall ended up with this error on the command-line

Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...

And a red message on the device, saying:

Only official released binaries are allowed to be flashed(RECOVERY)

The solution of this first issue was simply to start the device once, and connect it to the Internet (WiFi or mobile data)

But it was still ignoring the /e/ recovery, and rebooting on Android.

The solution, found on, was to flash both the recovery and the vbmeta.img (downloaded from, with this command-line:

heimdall flash --RECOVERY recovery.img --VBMETA vbmeta.img --no-reboot

I think it’s necessary to add this information in the official documentation.

Finally, as @freechelmi said 2 years ago in Samsung - Galaxy S10e - beyond0lte - Documentation Suggestions - #5 by freechelmi, the buttons usage should be more explicit after recovery flashing

1 Like

Thanks! That did the trick for me! I could not get into /e/ recovery before. Tried several times but doing it this way worked immediately. =)

1 Like

Hello, I am running into the very same problem than you, but I don’t understand how you fixed it. What do you mean by «switch on ADB via the recovery screen: “Advanced >> Enable adb”.« ?

1 Like

If you already have access to /e/OS recovery then you may simply go in the sideload/adb menu to activate sideload mode and then from your PC send the terminal command sideload … to send and install the OS image.

If you do not have access to /e/OS recovery, then it is probably because the Samsung recovery erased automatically the /e/OS during first startup after loading the /e/recovery in fstboot/download mode.
As explained in previous posts, the key combination is tricky and the change from volume down to volume down must be very fast as soon as the phone switches off, while always pressing the two other keys. It might require several trials.