Problem installing /e/ on Galaxy S10 (SM-G973F dual-sim)

Yes, it says OEM LOCK ON(UI).

Is there a way to unlock oem lock?

I do not have them available ATM, but the OEM unlock instructions should be on the install instructions. If they are missing or unclear a search will find them.

Gr8, thank you so much for your help :slight_smile:
I will find them.

This seems to be a deeper problem. There’s no OEM unlock option in the developer options for this model of S10, apparently the models with Exynos chips have it, but Snapdragon chips don’t. I tried with the generic instructions - also using the command line option - from the /e/ documentation, but it didn’t work. I guess I’m stuck here :cry:

So it appears that your device is not supportable, IF it is not a beyond1lte

Possibly, although the samsung original recovery ROM is named something like samsung/beyond1ltexx/beyond111/…G973FXXSEFUL1…
so it looks like it is beyond1lte yet I can’t find a way to turn off the OEM lock.

What is the reason you mentioned Qualcomm? What is the reason you originally described it as SM -G973F? Please be specific! Any further info on the Odin mode screen?

The device is as I originally said, SM-G973F/dual-sim, at least that’s what it says in Settings > About phone. The phone simply doesn’t want to allow OEM unlock no matter what I try. Odin mode screen says the same: OEM LOCK ON(UI)

Does not allow it, or does not have it on the menu? The preinstall instructions are very specific about the role of the USB cable. Does the word Prenormal appear on the Odin screen?

Device specific: Install /e/ on a Samsung Galaxy S10 - “beyond1lte”

Finally success :sunglasses:

It all boiled down to finding how to enable the OEM unlocking. The installation document fails to explain how to enable OEM unlocking, when this item is missing from the menu. I got it there by removing the automatic date & time setting and then selecting a date 8 days back.

Anyways, thanks for all the tips and support :slight_smile:

When you point to perceived gaps in the documentation (especially in the case of a relatively “new to /e/” device it is always nice to leave the best information for the next person who finds this situation.

Is there any improvement that can be provided to this article (is it up to date?) and/or how do we make it more findable. OEM Unlock - toggle now missing. Or there is Documentation Suggestions. Thanks.

The only distro I have successfully installed with this procedure is the latest Lineage “lineage-19.1-20221230-nightly-beyond1lte-signed”. I was unable to install any /e/OS distro (e-1.6-s-20221130239247-dev-beyond1lte) nor - for testing - Lineage OS 18. In these last two cases, the installation is fine from the Recovery but the Samsung does not boot anymore. I started from a ROM-STOCK G973F_XEF (android 12).
Do you have any idea how to install /e/OS on this Galaxy S10 (Exynos)?

I then tried to install an earlier stock rom with Odin and I saw the message “SW REV. CHECK FAIL (BOOTLOADER) DEVICE:16 BINARY:14” displayed on the smartphone. I think it was the same anti-rollback problem with Heimdall, but without message. Does anyone know a way to extract the Rollback index from an /e/OS distro (.zip) ?

Extracting the Rollback index would be a nice idea ! But unknown to me.

As Odin is a Samsung tool it will not cooperate in doing a downgrade.

You started from a ROM-STOCK G973F_XEF Android 12 == S == Lineage 19.

The only distro I have successfully installed with this procedure is the latest Lineage “lineage-19.1-20221230-nightly-beyond1lte-signed”.


I was unable to install any /e/OS distro (e-1.6-s-20221130239247-dev-beyond1lte)

I notice that there is a 1 month degrade of timestamp there – did you try /e/OS first ?

nor - for testing - Lineage OS 18.

Would be explained by Rollback.

We have to cope (it seems increasingly) with Android security patch level (SPL) where devices may resist degrade of SPL as well as Android version.

From Release notes we learn the SPL of e-1.6-x-xxx is October 2022.

Generally, perhaps, before attempting install one may need to check Settings > About phone > Android version > Android security patch level.

In this case, if you have a pre-existing SPL in advance of October one might expect resistance.

If one experiences resistance maybe one has to wait for an /e/OS version in advance of that date, but I am not absolutely certain.


Yes, /e/OS was the first open system I attempted to install, but without success.

Thanks for the info, very useful for next time.
When I do this on the S10 (now running LineageOS 19), I have the following dates: Android Security Update: 5/Dec/2022 and Vendor Security Patch Level: 1/May/2022. As I understand it, it’s the second date that matters and we would have to wait for a /e/OS version with later SPL ?
Thanks a lot

So in this case we do not now know the relative SPL between your stock ROM and e-1.6-x-xxx.

The Android SPL updates every month and the vendor at random intervals as I understand.

My guess would be that e-1.6-s-xxx would share the Vendor Security Patch Level: 1/May/2022 with the contemporary lineage-19.1-20221230… but it will lag in Android SPL.

Edited twice It is the monthly published date of the Android security patch level which points to SPL while Vendor Security Patch Level points to the Manufacture’s software revision aka “SW Rev” which may also be referenced when searching for a stock ROM.

If you were to revert to your stock ROM – maybe now e-1.7-s will be in advance of it ?

Thanks a lot for your time and your explanations aidb.

Please bear in mind that I am uncertain if SPL is indeed the primary consideration.

There also exists this workaround Update firmware on beyond0lte | LineageOS Wiki which I found linked here Samsung - Galaxy S10e - beyond0lte - Documentation Suggestions - #15 by ImG.

1 Like

I finally got there by rolling back through the SM-G973FXXSGHVI4 STOCK ROM and then I installed /e/OS 1.620221130xxx. I got the message “only official released binaries etc…” with no OEM unlock option. I applied this solution; which worked, /e/OS 1.6 was installed.
I then upgraded to /e/OS 1.7.
Thanks to all the contributors for their indications.

1 Like

Same error (Signature verification failed) and it took me a few hours of trial/error and reading to understand and get past this.
In fact the problem comes from the reboot after the installation of /e/OS Recovery.
It says: 7. Manually reboot into recovery:
This reboot is difficult. If you miss it the recovery you downloaded is deleted and the next step cannot be validated.
I found the way to reboot correctly by reading the Lineage OS installation procedure => Install LineageOS on beyond1lte | LineageOS Wiki
IMHO it would be nice to specify this point in the e/OS installation instructions =>
When rebooting after downloading the recovery you will see a different screen with the e/OS logo.
Attached a screenshot of the OS installation. (Not necessary to wipe data twice.)

Of course you have to be sure to have the right model SM-G973F (or SM-G973F/DS). SM-G973U is not good (no OEM unlock).