Then tried to install TWRP using your method.
I get stuck at this part of the instructions.
If red error messages show up, your phone is probably encypted but TWRP can’t decrypt the /data partition (it’s a common issue on Samsung phones).
To solve that problem, go to Wipe > Advanced wipe, select “data”, click on “Repair or Change File System”, then on “Change filesystem”. Select exFAT (or another one if it doesn’t work, it doesn’t matter), then swipe from the left to the right. Redo the manipulation but this time select ext4 (which is the original file system) then slide from the left to the right. Go to the 8)A)1. part of the howto.
I choose to format
On the screen it says
formatting data using mkexfat
done
but it keeps showing the blue moving bar and at the top of the screen at says formatting.
I am stuck in this screen now. Shut down phone and reinstalled TWRP. Now TWRP gets stuck at the starting screen.
Which version of TWRP did you use? Did you install with ODIN?. By “starting screen” do you mean the screen before the starting screen (that is a “Splash screen” which is expected to be transient as TWRP loads) ?
Were you sure to remove all accounts from the phone before starting /e/OS install ?
TWRP 3.7.0_9-1
Yes installed with Odin. Everything went fine. Rebooted in TWRP. Did the advanced wipe as mentioned in the link. During the formatting process something seems to have gone wrong. Now I am stuck in the teamwin screen with the blue circle with the arrows. So yes the splash screen.
So you are in the situation where this job is incomplete.
Tbh I do not know if this can influence failure of TWRP to load, but I would try Odin to flash perhaps an earlier version of TWRP, then the most recent (again) in order to get back and finish the formatting job.
A detail you mention is
On the screen it says
formatting data using mkexfat
done
…
but it keeps showing the blue moving bar
I would believe “done”, the persisting animation I would be less concerned about.
Just a thought, should you find yourself in that situation again, be sure to use the “Back” buttons under the TWRP screen.
Thank you for the advise. I did not see a back button. Guess I had to use back button on the phone but was not familiar with this phone. Found out later the touch buttons ;-). Was stuck although it said formatting done.
@piero I use Windows. I gave up in June, now I want to try again but in the meantime the S5 Neo dissappeared from the devices list: https://doc.e.foundation/devices . so I will have to try installing another OS now?
@make-nz darf ich fragen wo Du wohnst und ob Du mir persönlich helfen kannst oder zufällig jemanden kennst?
It is just masqued by default has it has been dropped like all devices stucked on android “Q”.
You must enable " legacy devices" (at the bottom) in the search options :
Samsung Note 10+ has a problem. supposedly newer Samsung phones have this problem.
I don’t know the details, but I found the fix.
After flashing TWRP onto the phone with ODIN, the phone will restart in a potentially fake download mode, and display the error "“error validating footer (0)” and “invalid vbmeta header (6)”
The solution is to enter download mode again, restart and press the button combo for it with the cable attached. This is to get out of the potentially fake download mode into the real download mode.
Then you can do this here, or you could have seen this post ahead of time so that you can do this the first time.
in addition to putting the TWRP.tar in the ‘AP’ location, you also need vbmeta.tar in the ‘CP’ location. This can be found here under “Odin (Windows)” Instructions. (I didn’t find it on the TWRP website. It’s not on the pages I found the TWRP.tar on)
This is “avb disabled vbmeta”. I don’t know any details as to what this does or why it’s needed, but it works and is needed.
I successfully installed eOS on my Samsung Galaxy S9. I ran into some smaller issues, though:
No “OEM unlock” - the option never showed up, until I registred my phone with a Google account (and had waited 7 days before, hoping it would show up).
During step C/3, I got an error message that a /media folder couldn’t be swiped. I tried a couple of things, none of which made a difference. The folder just wasn’t there. So I decided to ignore the error message. That worked.
Thanks for your post. I amhappy to announce that I finally manage to install/update to the latest 3.2 Murena version. My phone was since 2022 without any update.
I am happy i have still phone for 1 or 2 years or more.
The process took me 4 hours, reading the article, verifying everything, downloading files and checking that were the right files.
It was a little bit tough as Iused TWRP for the first time, trying how to get there many times..
I have to say that I wouldn’t like to repeat this process again. But it´s nice to know i have a “new phone” and it´s working properly. I was about to give up and at some points i thought i didn’t have phone anylonger, as i couldn’t leave the Samsung S8 welcome screen (no rebooting and without changes from the TWRP).
Differences from your process:
In my case, as I have already had a Murena OS, i didn’t have to do the step 3.
Also, my recommendation is that you put the ROM or zip with the OS in the internal storage before starting the process; because in my case i had many problems in transferring when i was in the middle of the process.
Testing everyting, everything works excepto for 2 banks apps that i´ve downloaded from Aurora, they open, but i cannot login.
so you already had a custom recovery, no need of TWRP, you just had to boot into the recovery-e and install /e/ from internal storage, SDcard or adb sideload (only step 8 was required)…
