ok im updating phone I was hoping you said that
Ok I found that with your great help
[Galaxy S9+] star2lte
Now onto the next step.
Ive run the process a couple of times via Odin and it fails. I got a green bar then the RED fail came up.
I downloaded samsung drivers again but its still failing.
If you think there is any possibility that it is a drivers issue, sometimes an upgrade in driver is needed to cope with change of booting mode, please thy this.
Open a device manager window. You will know you are looking for a yellow warning triangle if there is a driver missing. Now run Odin with the device manager open alongside. Check that a device warning does not appear, if necessary do the Windows update right then, while the phone and PC are still in the failing state.
Secondly, are you fully watching for any flags for user participation! Like something happens on the PC now you have to do something on the device, be sure to turn up the device screen timeout to 30 minutes and watch both screens.
Perhaps check out this Know your hardware - Samsung # First boot into TWRP
and thirdly did you do a factory reset/remove accounts before you started post 91 (although the detail there applies to a more complicated USA case)
If Driver is already installed on the windows PC, in device manager, you have to change the Samsung composite interface, no ?
From what I’ve read, you can’t downgrade the android version. If you have Android 10, you’re going to have to wait until an /e/ version 10 comes out for your phone.
On star2lte I could not downgrade any ROM once I had stock Android 9 or above installed. Likely due to regional lock (I’m in USA). RMM was locked “Prenormal”. This only happened if the stock ROM was upgraded to Android 9 or above before the bootloader was unlocked. If someone is in the USA my advice is use non Samsung hardware to flash yourself or buy direct from /e/ if you want star2lte.
These instructions are brilliant and helped me trouble shoot my problem with my phone not using mobile data with the eOS easy-installer version.
Thank you so much, I doubt I could have done it without you.
Thank you very much for your detailed and excellent tutorial for installing the /e/OS using the ODIN tool.
Following its instructions I have managed to install /e/OS in my Samsung Galaxy S9 and found it is a lot more easy than doing it in Windows with Heimdall and having to compile this program with complex tools.
Without your tutorial, I would have to do the installation in Linux which is a lot more complex, following all those commands and instructions.
Before trying your tutorial, I have tried to install the /e/OS with the Easy Install but I became stuck in the TWRP transfer to the smartphone.
Thank you again for your help.
After a few tries it worked as a charm. Thank you very much for this spendid tutorial.
A great thread with lots of useful information.
Hello! I am stuck at point 5. Though Odin3 is recognizing my Samsung Galaxy S10, I receive a FAIL. Any ideas what I could do?/What I am doing wrong?
Help would be highly appreciated. Muchas gracias!
S10 is another story,
you need Odin 3.14
first unlock bootloader and flash the vbmeta.img.tar And the twrp.img.tar
Hola Leontin and welcome.
I have got a samsung s10e, and I have the same issue as you do… “Fail error” in Odin while trying to flash TWRP.
I tried to do what piero recommands flashing vbmeta.img.tar, but it didn’t work either.
If you succeed to do it, I would really appreciate if you could give a feedback
Just have a look ! Good luck
I was FINALLY able to get the OEM unlock to work and ran Odin to install TWRP. Odin says “PASS”, but my device - a Samsung Galaxy Tab S6 LTE, says this on a blue debug screen:
ODIN MODE (AVB Fail)
recovery: Error validating footer. (0)
recovery: Error verifying vbmeta image: invalid vbmeta header (0)
VBMETA P610XXU2DUK1, 45668820A
nothing i try will power the device off or get away from this screen. I can push PWR + VOL DWN but i get a momentary flash of the device page like it is going to boot, and then right back here. Can’t even power it off. Any suggestions???
I have the very same issue with my Galaxy Tab S6 Lite… I have not found a solution yet. It was pretty easy to get everything to work with my Xiaomi Mi10T, so this was a bummer.
Anyone with the know-how who could help PFCDroid and me?
EDIT: found this, but I am not experienced enough to test it:
For custom rom or recovery modifications u need to Flash null vbmeta or disable it. If not it will throw AVB fail
Where to get the files and what to do?
Thread ‘[HOWTO] Flash a blank vbmeta’ [HOWTO] Flash a blank vbmeta | XDA Forums
@PFCDroid The problem is that the TWRP is discontinued for Samsung S6 Lite, meaning that the developer will not update it and that the current version is unfinished, resulting in errors </3 I am trying to find a good solution.
@Anonyme I think it would be wise to mention early that TWRP is no longer an option for a lot of Samsung devices because devs do not update it anymore. Would have saved me a lot of hassle. I should have researched more myself before going ahead, but I am thinking about everyone else
BEFORE INSTALLING TWRP: make sure that TWRP for your model is properly maintained and up to date. If not, you will encounter an error and will need to run a recovery.
Anyone here with the proper knowledge on how to run a recovery if one is stuck in an Odin loop?
Please confirm is this Install /e/ on a Samsung Galaxy Tab S6 Lite (Wi-Fi) - “gta4xlwifi”. Please can you tell us what happens now if you try to install /e/ Recovery?