Struggling with a Samsung s10e

/e/OS Devices Samsung
1

Hello! I am trying to install e/0s/ on a (second hand) Galaxy s10e, which is definitely on the supported list.

I have found the following thread (Downgrading android 12 to 11 on a samsung galaxy s10e and installing /e/ - #4 by piero). My French isn’t good enought to follow. And tried to follow the default ODIN instructions but have not been able to get the TWRP flash to install.

image
image996×675 34.9 KB

Every time I try to use ODIN I get the following message:

<ID:0/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 53 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!! 
<ID:0/009> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> vbmeta.img
<ID:0/009> RQT_CLOSE !!
<ID:0/009> 
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Does anyone have recent experience of installing to s10e? Has anyone encountered this issue?

Cheers
struggling

2

Hello @struggling, Welcome to the /e/ forum.

Please share a photo of the screen in download mode

3

1000005969
10000059691920×3677 239 KB

the top left appears to say -N MODE (by param) \n ause:

4

Did you notice that @Marine did a review in English /How to/ install /e/ R on a samsung galaxy s10e already running android 12 which I commented on post 2 apropos Prenormal.

I remember it was observed that Prenormal was an issue not shown of this device’s Download mode screen (?? poor memory) but you might consider what he reports he had to do to overcome this “unknown” first. He had to persevere for a long time although perfectly familiar with the routine on earlier Samsung.

Part of the original thread is in English or French and English in the area (re Prenormal) of Downgrading android 12 to 11 on a samsung galaxy s10e and installing /e/ - #78 by aibd.

5

Note that downgrading is no more necessairy as /e/is now based on a higher android level,
But “RRM” could be bypassed by connecting the device to the internet throught the Stock OS

2 Likes
6

I tried the section you pointed out, unfortunately with no luck, even with the vbmeta.tar suggested. Do you think the phone I got might be locked in some way we’re not guessing? I don’t really understand why it’s saying ‘custom binary blocked by OEM lock’ when I’ve unlocked OEM. :weary:

Maybe I will give up the dream of a Google free life :cry:, unless anyone knows of other things I can try, or can make any sense of what I’m seeing here.

I any case, thanks for your help though!

7

This I would associate with Prenormal … I thought I had done a rather overkill with the many links (or follow my links) to the Prenormal situation there.

Very loosely speaking Samsung would, on one hand, allow you to unlock and apply an official binary (first part of marine’s story) – but a Custom binary requires a further level of unlocking which is unavailable in the Prenormal state (his second hurdle).

That was way back in early 2022, different Android versions and I guess different install page now. It is mainly covered in the Pre-install instructions, Install /e/OS on a Samsung Galaxy S10e - “beyond0lte” perhaps tell us where you are at with reference to that ??

1 Like
8

Sure!
So basically I ran through all the pre-install sections, excpt this one - it seems the bootloader was already unlocked

  1. Power off the device, and boot it into download mode:
  • hold Volume Down + Bixby and connect USB cable to PC
  • Now, click the button that the onscreen instructions correlate to “Continue” and/or “Unlock Bootloader”.

But - I have now discovered that although I found different ways to enter download mode - this is the special way that allows you to enter download mode in a way that unlocks bootloader.

Thank you for making me look more closely again. I will report back if I get stuck!

9

Great.

If you get a screenshot which demonstrates the “critical change” in Download mode and whether the KG or RMM state now shows on your Download mode screen or elsewhere it might help others.

10

Ahh I’ve gone past that but I could write about it - the short version it that it seems you have to follow the exact instructions -

hold Volume Down + Bixby and connect USB cable to PC

to enter download mode - using ADB or the boot menu won’t work.

But! I have progressed to a new problem - in TWRP I am unable to install the e/os/ zip: TWRP is saying

The current recovery does not seem to support dynamic partitions, please update.

Before I try to sort out doing via heimdall in WSL just checking if anyone has ODIN experience to suggest what might be the issue I’m facing via ODIN?

This is the only thing I can find about the same issue

11

TWRP is not working well with recent devices and recent android.

In Odin, put the recovery-e.tar into the AP slot,
and the vbmeta.tar in any other slot…

(“7zip” is your friend)

12

Do you mean I should use 7zip to put - /e/OS community beyond0lte download recovery-e-2.8-a14-20250220470208-community-beyond0lte.img into a tar?

this did not work so I guess you meant something else

1 Like
13

!! Only if coming from full stock firmware

  • In TWRP home screen press wipe - format data - yes
  • Download and flash multidisabler-samsung-3.* zip to disable security and encryption.

Ahah, I have found something - perhaps this is what I need to do https://xdaforums.com/t/recovery-official-3-6-1-x-twrp-for-galaxy-s10-e-5g-exynos.4180287/

but it’s not clear to me how to use it. Do I ‘install’ it using TWRP?

14

TWRP is not mentioned on the install page, except they do divert some users to the “old” HOWTO written before e-Recovery was invented.

So if you have to use the old HOWTO can you just substitute all TWRP for e-Recovery?

Or if using the “Corsicanu” method I do not follow where you are stuck.

There is also no attribution to your quote.

15

The quote is from the link beneath it, sorry I didn’t make that clear.

So I 'm trying to understand what this post https://xdaforums.com/t/recovery-official-3-6-1-x-twrp-for-galaxy-s10-e-5g-exynos.4180287/ means by

Download and flash multidisabler-samsung-3.* zip to disable security and encryption.

I’m wondering if this might help with the TWRP issue.

On the other hand, I don’t know Piero is suggesting about recovery-e.tar. What is recovery-e.tar? I found the recovery-e.img for my phone but not sure what Piero is referring to. Do you mean just to make my own tar containing the .img? I tried this and ODIN crashes :sweat_smile:

In any case - I have succesfully reached a booted TWRP, but cannot get it to install eos. I can try from scratch to use heimdall in WSL rather than odin next.

16

You can use your working TWRP to install the “recovery-e.img”

2 Likes
17

Please describe the problem. You would just pick up at

8) Install /e/ with TWRP

Where does it go wrong?

Advanced stuff

You could read the purpose of multidisabler here https://xdaforums.com/t/pie-10-11-system-as-root-multidisabler-disables-encryption-vaultkeeper-auto-flash-of-stock-recovery-proca-wsm-cass-etc.3919714/.

TWRP is also advanced, e-Recovery is more simple.

Edit. What TWRP version are you using? TWRP 3.7 was for Android 11 and 12, TWRP 3.6 one down. You are planning to install /e/OS at Android 14.

18

You can use your working TWRP to install the “recovery-e.img”

Ahah - which partition should I flash to?

  • Boot
  • Recovery
  • System Image
  • Vendor Image
  • Product Image
    ?

Thanks for your patience!

Where does it go wrong?

Sorry, I could’ve been clearer. It fails at C) 4: rather than a successful install I get

The current recovery does not seem to support dynamic partitions, please update.

I am trying to install
e-2.8-a14-20250220470208-community-beyond0lte.zip using twrp-3.7.0_9-2-beyond0lte.img.tar. Maybe the answer is I need an older version of eos?

19

Sorry …

Edit … but an incompetent TWRP … but that is why I have been saying don’t use TWRP; is what I meant by “substitiute e-Recovery”.

In using that old HOWTO, every instance of TWRP read as e-Recovery.

This TWRP cannot handle a14. e-Recovery is expected to be fine.

20

with a recovery partition image…