yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Veraster:
I'm having a lot of trouble getting this working. If I flash this after patching the stock firmware with magisk, it will boot to TWRP and not android. After flashing LineageOS, I cannot get into TWRP using the buttons. The only way to get in to TWRP is to do something that makes android not boot such as flash something to the AP.

Any ideas? I've already retried the process of installing stock firmware in odin, patching with magisk, flashing that with odin, seeing it boot, flashing TWRP then flashing LineageOS about 4 times. Note that while LineageOS actually boots, I can't get magisk working. While I can flash magisk via Odin's AP button by renaming it boot.img and putting it in the same tar as recovery.img and vbmeta.img, and while magisk manager claims magisk is installed, I can't install any modules. I get an error message of

! is not installed
! Please install Riru from Magisk Manager
***********************************
! Installation failed

I'm using vbmeta-disabled as instructed, extracting twrp-3.5.2_9-beyond2lte-v1.img.xz and renaming it to recovery, renaming vbmeta-disabled.img to vbmeta.img, using 7zip to put that into a .tar file and then flashing the resulting tar file to AP with Odin.

what am I doing wrong?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] perxeus:
Similar situation - i cannot get any TWRP version with FBE support to work.

That were the prerequisits:

* happens for a newly acquired S10 (not the S10+ mentioned in the signature)

* coming from latest stock rom

* Official TWRP 3.5.2_9_3 installed and working (I was unaware of this version of TWRP)

* fresh latest official lineageos 18.1 beyond1lte 2021-08-20 installed and working

* magisk installed and working

* build the recovery.img tar and vbmeta.img tar with 7Zip

* flashed in download mode with Odin 3.14.1

-> result: S10 will not start ("could not do normal boot - kernel length invalid!")

no possibilty to boot system or recovery and boot loops when hooking it to the USB cable

the only way out was pressing Vol-Down and Bixby and then connecting to USB to start DL mode. and reinstall official TWRP - this again works.

Same also happens with version 3.4 of this TWRP version

What happens - how can I get this TWRP to work???

I hope the are is someone who can help.

Thanks

Perxeus
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] diegol 007:
same!!! please help!!!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] gsausalito:
Hi:

Is there any difference with official TWRP and this version?

I was unable (with this version and official version) to make a backup from twrp because or reading errors.

I'm not using any pin/fingerprint to lock the phone but it seems locked or encrypted because twrp can't read data partition.

Thanks for your time
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Scarecrow_66:
Could you please add a MODPUNK TWRP for SM-G977B (Galaxy S10 5G)?? Appreciate it
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Wobbo-Q:
Can I get the official LineageOS beyond0lte on a beyond0lteeea? I keep getting nervous with IDs like this. Is it important that the first part is the same and everything after is not important? If my smartphone gives number like G970FXXUEGVA2 then I have a G970F?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] zogoibi:
Will it also work for G970FXXSGHVI1? That's S10e model, Android 12, One UI 4.1, the very latest firmware as of today.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] danii26:
¿Todavía funciona hoy? 2023 Además, tengo Android 12 y uso un SM-G973F
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
You have to ask [MENTION=4063475]derf elot[/MENTION] :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lupin57:
Hi Modpunk ;)

Just for information ^^

Little mistake on ur OP "This project provides the TWRP recovery for the Samsung Galaxy S10e (SM-G970F, beyond0lte), S10 (SM-G973F, beyond1lte) and S10+ (SM-G974F, beyond2lte)"

SM-G975F instead of SM-G974F :D
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
Im not confirm with twrp building. But in the last time twrps would build with stock kernel sources. It seems youll find a different way with lineage?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Fixed, thanks.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] derf elot:
I'll see what I can do about it in the near future. I am currently triggered again a little by the CTC9 kernel source release from Samsung. It's not the quality I'm used to from Sony :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ramnkc:
Do this twrp required to boot with key combo during boot up to have magisk root?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
This is just a recovery which supports FBE decryption for AOSP based ROMs. We are doing a LineageOS bringup for S10e|S10|S10+ right now. We have most of the stuff working already.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] angela5246:
What FBE modes did you try? I can see that stock rom comes with fileencryption=ICE. Does your TWRP also work if encryption is set to fileencryption=aes-256-xts or fileencryption=aes-256-xts:aes-256-cts:inlinecrypt_optimized?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] jean_michmich:
I successfully flashed RECOVERY and VBMETA.

It was impossible to start the STOCK ROM....and all the time coming back to TWRP.

The data partition was showing some empty folders with hashes (even after several Wipes of DATA partition)

I was also unable to push through ADB the zip of lineage OS in the folder /sdcard. The error message was : "remote couldn't create file: Required key not available"

So it seems i was well bothered by encryption.

Then I installed LOS17 through TWRP...and it works well.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
As stated in the first post TWRP doesn't support Samsung ODE, it only support the AOSP way of encryption.

Well, it is encrypted so you can't write on it. You have to put it on the the external SD card.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] angela5246:
I see. So if one would like to use AOSP's FBE the fstab needs the right entries. How would that fstab look like to have AOSP's FBE on /data partition?

In other words, could you post a file fstab where FBE is enabled?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
ICE means it is a vendor specific implementation, what is Samsung using?

The device does clearly not support inlinecrypt, you checked the kernel options, right?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] jean_michmich:
You are right.

I fully format the Data partition. It removed the encryption.

So I well confirm the version of TWRP and the VBMETA images provided in this first post well work (flashed in command lines with heimdall)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] angela5246:
Thank you for getting back to my questions. No, i did not check the kernel options. I am not sure if I would understand them anyways.

So if inlinecrypt is not supported, how would the fstab need to look like?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Not that TWRP only decrypts data it doesn't setup the encryption nor update the keys. The encryption is always set up by the ROM and keys are updated by it too!

For the recovery we need fileencryption=aes-256-xts:ice, then we can decrypt both variants.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] catormeme:
so does this work with BTA8?

---------- Post added at 11:29 AM ---------- Previous post was at 11:25 AM ----------

jk im stupid
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] brambles1234:
Can somebody please re upload the vbmeta disable file I get a 404 missing file from link on first page
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Sorry, I've uploaded it again.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
I've uploaded new recovery images, they are userdebug builds. This means adb only works if there is a valid authentication available.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] p@to:
Hi.

can i flash this recovery on a stock rom?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Yes, why not. However a stock ROM needs a special boot.img (kernel). It has several things implemented to prevent flashing custom stuff.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] p@to:
Sorry I'm new on this phone. Where I can find this special boot.img?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] WalterCool:
Deleted by myself
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] WalterCool:
Question, installing this TWRP and just formatted device, doesn't allow you to use any ADB (normal/sideload) at S10, tested with twrp-3.3.1-0-android-10.0-beyond1lte-3.img. Normal ADB gave you an unauthorized, sideload doesn't work.

Is that a normal behavior?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
This is a user build which means you need authorized keys in /data to allow usb access. This makes the recovery at least a bit more secure. For flashing the first time, you need to put the ROM on the sdcard. Once you have set up the ROM and turned on USB Debugging, adb will work in TWRP.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] p@to:
I can flash it directly from another twrp recovery?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] AndrOdin:
VBMETA instructions wanted

How do I flash VBMETA disabled?

I first tried to use fastboot, under platform tools, but this doesn't seam to work with S10e.

I then tried to pack vbmeta-disabled.img as vbmeta-disabled.img.tar using CMD, so the file is recognized by Odin, but when flashing, it just get stuck at flashing vbmeta.img.

If I just flash a patched TWRP, provided by OP, i get stuck on splash screen.

I have previously flashed ianmcd TWRP without problems...

Can you please provide the procedure on how to flash vbmeta-disabled.img?

What should be flashed first, recovery.img or vbmeta-disabled.img?

Step by step would be apreciated.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] trancinguy:
There is no fastboot with Samsung, reboot to download mode Tar: recovery.img plus vbmeta.img together and then Odin and make sure auto reboot is off, and then exit download mode and make the key combo to recovery, format data, then multi disable if you want stock, or wipe dalvik, cache and system if you want Roms.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] AndrOdin:
Thanks for the reply, and I was a bit confused by some mentioning fastboot as download mode, but that is cleared up.

I have figured out, that the reason I was stuck at flashing vbmeta.img, was because I named vbmeta.img as vbmeta-disabled.img in the compresed vbmeta-disabled.img.tar file I made.

After renaming vbmeta-disabled.img to vbmeta.img, and making a new vbmeta-disabled.img.tar, I was able to flash with Odin.

The problem might have been that "-" is unrecognized charachter or the name having to be named as originaly provided by Samsung, but maybe someone can confirm?

That aside, I then:

1) Opened Odin

2) Flashed recovery.img, packed as twrp-3.3.1-0-android-10.0-beyond0lte-5.img.tar

3) Restartet Download mode

4) Flashed vbmeta.img (vbmeta-disabled), packed as vbmeta-disabled.img.tar

5) Restarted phone and pressed the combo to enter Recovery (Bixby, VolumeUp, Power), and released everything accept VolumeUp

I was though unable to boot to recovery, and just got stuck on splash screen.

How do I flash recovery.img and vbmeta-disabled.img together?

I thought I was suposed to flash both in AP in Odin, one after the other?

Do I need to pack them together?

As of now, I only know how to pack one file as tarbal, but not multiple together, if that is needed?

Do I need to flash vbmeta-disabled.img in BL?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] trancinguy:
You can do them separately or together, both images should not be tar, rename the Q-twrp img to recovery.img, and then tar the two together in one tar file, then key combo and keep holding until you boot to recovery, then format. 7 zip is a good program that can do it.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] jibon89096:
Problem with restore

I have a general TWRP problem, hope someone can help me solve, regarding the different backup options in TWRP.

I'm running TWRP on a Galaxy S10+.

In the first backup I've made (after rooting and flashing ROM), I've included all options my phone have: Baseband, Boot, Cache, Data (excl. storage), EFS, Product, Product Image, System, System Image, Vendor, Vendor Image.

In later backups I've only included: Boot, Data, System.

I was jumping between backups and restored the first backup in full (meaning I restored everything that was backed up - not only Boot, Data & System).

Since then, the phone is stuck on Samsung's boot screen.

I've returned to TWRP to restore a later backup (only Boot, Data & System), but am still stuck on boot screen.

Can anyone help please?

A million thanks to whoever can help me get back to normal.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] AndrOdin:
Have you tried to wipe dalvik cache?

---------- Post added at 12:45 PM ---------- Previous post was at 12:30 PM ----------

I have now tried to go back to full stock firmware, and then:

1) Re-downloaded twrp-3.3.1-0-android-10.0-beyond0lte-5.img.xz and vbmeta-disabled.img.

2) Extracted twrp-3.3.1-0-android-10.0-beyond0lte-5.img from twrp-3.3.1-0-android-10.0-beyond0lte-5.img.xz.

3) Patched twrp-3.3.1-0-android-10.0-beyond0lte-5.img with magisk, and transfered the output file to computer (magisk_patched.img).

4) Renamed magisk_patched.img to recovery.img.

5) Renamed vbmeta-disabled.img to vbmeta.img.

6) Packed recovery.img and vbmeta.img as QTWRP.tar with 7Zip.

7) Opened Odin and unselected "Auto reboot".

8) Flashed QTWRP.tar as AP in Odin.

9) After flash succces, i restarted S10e, and held recovery combo right away (Bixby, VolumeUp, Power).

After 10 min of holding the recovery combo, phone is still stuck at splash screen...

What am I doing wrong?

Have I missed a step somewhere?

I have tried to repeat process several times, and I have also tried to flash prepatched stock firmware in AP, before continuing above process, and with ianmcd TWRP there is no problems, but with this recovery I just can't boot, and I have to reflash stock firmware, to be able to proceed again.

PS. I'm currently on Magisk patched stock firmware (2020-04-05_G970FXXU4CTC9_G970FOXM4CTC5_NEE), with unlocked bootloader.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] jibon89096:
Yes.

Before every restore I wipe: Dalvik, Cache & Data.

When I usually restore it's all fine, but now that I've restored all these options (Baseband, Boot, Cache, Data (excl. storage), EFS, Product, Product Image, System, System Image, Vendor, Vendor Image) - I'm stuck on the boot screen.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] AndrOdin:
You need to do the wipe Dalvik, Cache & Data, after restoration, and regarding the backup, if you have backed up on an SD card, I would then go to stock, and restore you app data with Titanium backup.

It would really be apreciated if we could get the right procedure how to flash this TWRP used for LineageOS, in detail.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] jibon89096:
Do you mean to flash stock firmware using Odin - starting up from scratch?

I'll PM you with details on how I installed TWRP and LineageOS 17.1.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] AndrOdin:
Yes, I was thinking that the easiest thing would be to start from scratch, if you have a backup on the SD card.

I know it can be a pain, but that is what I would have done, I have also done that about 7 times today, when trying to flash TWRP for LineageOS, and without success.

I don't tnink it's good to use ianmcd TWRP, when this TWRP by OP is recomended.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] jibon89096:
Thanks [MENTION=10599663]AndrOdin[/MENTION]

Anyone might be able to save me, helping to restore one of the backups without reverting back to stock?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] trancinguy:
I think your mistake was patching the twrp with magisk, only rename the twrp img to recovery.img
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] AndrOdin:
But how do I install Magisk afterwards?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] trancinguy:
You flash a magisk boot img to the boot partition in twrp recovery.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] jibon89096:
Would really appreciate if someone can help with that!

Couldn't go pass boot screen for several days now :crying:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] p@to:
Try to restore first buckup without any image backup

---------- Post added at 12:44 AM ---------- Previous post was at 12:30 AM ----------

Try to restore first buckup without any image backup
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] jibon89096:
Thank you!

Thought that would be more complicated, but that actually did sort it :highfive:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] AndrOdin:
THANK you very much, as patching with Magisk seam to cause problmes, and by avoiding this, I was able to both flash TWRP, and instal LineageOS.

How do I actually do this?

Can I pack the magisk_boot_ctc9_beta1.img as zip with 7zip, and flash through TWRP?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] trancinguy:
You need the boot-magisk-img developed by Ivan Meler, reboot to the actual twrp recovery using the key combo or the advanced reboot menu, install, change from install zip to install Image, navigate to the boot partition, install to the boot partition, reboot.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] AndrOdin:
Found boot image for S10e here: boot-magisk-img developed by Ivan Meler
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] p@to:
Hello!

Could you edit your post and detail how you flashed twrp and vbmeta?

Thanks a lot.

I still find it confusing
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] p@to:
Thank you very much!!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] AndrOdin:
Turns out I got modpunk's boot image working on my device, and all I did different, was not wiping ART cache.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] martindar:
Hi I'm having the same problems on s10e I must have had to restore to stock and then reboot 8 times and still getting bootloop at the end of the process!! I've currently given up for a min as I need my phone working m! really not sure whats going on but just frustrated that I cannot get the process to work give me back my nexus 4!!

---------- Post added at 07:19 PM ---------- Previous post was at 06:57 PM ----------

I have tried flashing twrp for the last three days and not been getting anywhere, had to go back through the rooting and booloader stuff time and time again! looked at all the threads on xda, Ian, geits etc and not got anywhere , will this work with an s10e running latest stock rooted rom and magisk, upto now all I end up with is a booting up screen repeating I gave tried terminal stuff and stuff and still no luck - give me back my nexus 4!! many thanks for your post and really just wanted assurance on the above cheers, Martin.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] AndrOdin:
If you are on stock, and just want TWRP, I would follow this guide here (Edit after clicking to "the custom droid(dot)com" without spaces), which gave me Ianmacd's TWRP and root, you have to follow it to the minute, and it's more profund then mine, and can be cut down to this:

1) Patched stock

2) Patched TWRP

3) Magisk installation

If that is what you want, follow the link above to the minute...

Ianmacd's TWRP thread is very important reading, and if you aren't sure, read it again. While using Ianmacd's TWRP, it's imprtant to use multidisabler and flash it every time after doing system wide operations.

If you want to have LinageOS, then folow the instructions laid out by me, but nothing is guarantied, like said in the disclaimer.

If you want help, you can send a PM, and I will do my best when I have time.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Muatyola:
GREAT WORK MATE. It's possible to flash this version of TWRP TO S10 PLUS EXYNOS , FROM STOCK ROM AND UNROOT DEVICES WITHOUT INSTALL MAGISK FIRST ,

I TRIED TO INSTALL MAGISK FIRST TO ROOT MY DEVICE BUT ITS DIDNT WAORK. PLEASEE HELP AND THANK YOU IN ADVANCE
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] f.silva:
Unable to Install TWRP

Hello everyone. I have some questions. Recently purchased a new unlocked S10e CTC9. I can successfully flash stock but have zero luck getting TWRP installed using the above instructions, or any other instructions found here on XDA. Have successfully rooted and installed ROMs on 3 previous Samsungs and a Moto so have some experience. That being said, these latest models have changed. Maybe I'm missing something here.

My questions:

_Does the sim card have to be present in order to install TWRP? Could that prevent custom flashing? Does the phone have to be activated with the carrier first? (This is my first time attempting to do it without a sim card).

_Is the OEM bootloader option supposed to be both checked AND grayed out? Some instructions say it needs to be checked and grayed out to satisfy Vaultkeeper however I can reflash stock no problem. Everything else fails or freezes along the way (using Odin 3.13.1). :(

Feels like I'm so close to getting this however am a bit discouraged after 3 days of attempting it. Any suggestions or ideas are greatly appreciated! Ask away as well if you need any specifics.

Thanks and have a great day everyone :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] AndrOdin:
The sim card doesn't need to be pressent, but you need to register the phone online, after a new purchase, factory resset or stock firmware flashing, just like described here.

Bare in mind though, that ticking "OEM unlocking" only allows you to unlock bootlader, and it isn't unlocked before you go into Download mode, and follow the instruction to unlock the bootlader, provided by the instruction the S10e Download mode screen, which means:

1) Entering download mode warning screen, just before entering Download mode.

2) You shoud be pressented with 3 option

* a) Volume up: Continue

* b) Long presseing Volume up: Device unlock mode

* c) Volume down: Cancel (Restart phone)

Insted of pressing a single time on volume up, to enter download mode splash screen, you have to hold volume up to enter device unlock mode.

If you haven't done as described above, your bootloader is probably still locked.

OEM bootloader option should only be togglable, while bootloader is locked. When you unlock the bootloader, the toggle should be greyed out, until you relock bootloader.

If you can flash stock firmwre though Odin, then there shouldn't be annything wrong with your USB drivers, and just make sure the bootloader is unlocked.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] f.silva:
Thanks for the help! I'm able to get into download mode using those same instructions above so have to assume it's failing because the phone is not registered yet. Will get that done tomorrow or Monday and start from scratch. Will post an update afterwards :)