yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Coldieee:
Hello,

I have a G973F running rooted OS (PDA = G973FXXS3BSL4 & CSC = G973FOXM3BSKO).

Which unofficial TWRP version should I use? In the changelog I can't see a G97[035]F build for BSL4.

OS releases for G973F went BSKO -> BSL4 -> BTA8, so I think it should be one of:

v3.3.1-101 for G97[035]F - BSKO

v3.3.1-102 for G97[035]F - BTA8

Thanks!
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] cameronkelley28:
101 (BSKO) should work fine.

Usually if the TWRP builds skip a release, it means the previous kernel (AKA TWRP) is compatible with the builds before the next TWRP update.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] goodflood:
I have been everywhere and have been told to post here:

Phone: S10e; https://en.wikipedia.org/wiki/Samsung_Galaxy_S10

Stock: https://www.sammobile.com/samsung/galaxy-s10e/firmware/SM-G970F/XEU/download/G970FXXU4BTA8/316635/

LOS: 17.1

ROM Thread: https://xdaforums.com/galaxy-s10/sa...exynos/rom-lineageos-17-0-s10-exynos-t4006917

The problem I am running into:

On flashing stock firmware (BTA8), I have 107 GB of space.

When I flash magisk patched_AP file (with the rest of the firmware), after renaming Ivan's recovery and including it in the AP file, followed by TWRP and rebooting to recovery, I have 15.7 GB.

I had previously flashed a tarred file (not magiskpatched_AP) to the AP partition by itself. Does this mean that my data partition has shrunk?

On asking for help, someone said that flashing stock firmware will reverse everything. It did. But, when I follow the steps above, I get a smaller data space. I do not have re-partition enabled in Odin. I am not sure what is going on or how to fix it. Can anyone help?

Thanks!
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] tiho5:
It's almost impossible to brick this device. You are anyway wiping data. So even if something goes wrong, you can always flash a FW package and go back to stock.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Philnicolls89:
What do you mean you tried in terminal but something went wrong?? No part of the wiping or root process requires you to open terminal. It's all done through recovery.

Also I hope this isn't a troll post but that twrp link goes to some stupid add website!
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] fil3s:
You a bully trying to Bully are ya:D

Edit: added to ignore list.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] veryape:
the mirrow "twrp-beyond0lte-3.3.1-102_ianmacd.img" is not working!!
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] veryape:
Help needed.

So I have my s10e rooted, how can I create a .tar file? I have the latest twrp .img file I patch the image on magisk and from the created file how can I turn that in to .tar???
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Keule-Tm:
https://lmgtfy.com/?q=img+to+tar+odin&s=d

Edit: Not mobile-friendly, go desktop mode.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Philnicolls89:
Correct, every time you want to upgrade or change firmware you will need to patch the AP file again. There is a guide in the first post of this thread.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] DaReDeViL:
For those who want to update to april firmware, be advised that the actual twrp doesn't work correctly with it. Follow OP instructions to boot with new stock patched recovery.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Philnicolls89:
Good to see that you have done your research before posting so thank you. A few things to consider,

After patching the AP file with magisk, you do not NEED to use adb push/pull to transfer the file to your computer but can if you wish.

You can also install twrp and magisk simultaneously, just download the correct twrp for your firmware(yes there are specific versions of twrp for most of the different firmware version), patch it with magisk, rename the file to 'recovery', open your patched AP file with 7zip and remove the stock recovery file and put the new file inside instead. You can then flash your AP file with twrp inside through Odin, along with the other files (BL, CP, CSC)

After doing the factory reset through recovery, it is important not to let phone boot up properly until you have flashed multi disabler.

It may be possible to install twrp without magisk which would allow you to perform a full back up of your device, but It would be a lot easier to just back up your apps etc to an SD card. Once you are rooted with twrp you can then do a full nandroid backup.

Also it is very rare to hard brick this device, most problems will be fixed by reflashing stock firmware and starting the process over again from scratch if you stuff something up.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] cgirerd:
I followed this tutorial, install TWRP using the official app, but cannot start TWRP using Power + Bixby Button + Volume Up... I tried to flash the patched version from Magisk as well, with either Odin or Heimdall with no autoreboot so that I can switch the device off using Volume Down + Power and then Power + Bixby Button + Volume Up to enter TWRP, but I get a bootloop for all my attempts. Don't really know what to do at this point :eek:
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] putti71:
One question, I am on latest stock rom (CTC9 for DBT) and I am rooted with magisk. Can I just flash this TWRP with TWRP app, without doing the data wipe?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Pogromonolith:
Thanks a lot for the response [MENTION=10006231]Philnicolls89[/MENTION]!

This is one thing I haven't understood - which firmware should I download (and which TWRP)?

The phone is brand new and shipped with an Android 9.0, Build Number G975FXXS3ASJG (UK based).

Should I download the same firmware the phone came with (which is the latest Android 9.0 for that carrier)?

Or is it better to download a newer Android 10.0 firmware?

I'm planning to install Lineage 17.1 (Android 10.0 based) after.

So from what I gather from your post, the Magisk root and TWRP flash could be done together, just need to add the following steps after step 6 in Root with Magisk (and scrap the Install TWRP section I wrote before):

7) Download TWRP to phone from ianmacd thread (?).

8) Enter Magisk Manager → Install → Install → Select and Patch a File.

Select the TWRP img file.

9) Copy patched TWRP file to PC and rename to "recovery.img"

10) On PC, extract magisk_patched.tar (patched firmware) using 7-zip.

11) Delete recovery.img.lz4 file from the extracted folder.

12) Copy the renamed downloaded TWRP "recovery.img" to the extracted folder.

13) How do I wrap the extracted AP folder back into a tar.md5 file? I can archive format through 7-zip, but then I get a tar.tar file instead of a tar.md5

Two issues I've encountered when testing:

When I try to extract the AP file (done a test on the unpatched firmware), I get the following warning in 7-zip:

Warnings:

There are some data after the end of the payload data

Second issue, is that after extracting the AP file, the recovery file inside is "recovery.img.lz4", whilist the TWRP recovery is "recovery.img".

That sounds like a mismatch (again, tested it on the unpatched AP file).

Many thanks for your help!
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] hanspampel:
No, you still have to format data. But twrp dont work on ctc9. Still waiting on fresh samsung sources. No sources, no working twrp on ctc9.;)
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] cgirerd:
My mistake, forgot to rename the patched TWRP img to recovery.img before making the .tar file. Thank you all!
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Philnicolls89:
You do not need to download the software version that came with your phone, you can download any firmware version you like so long as you get the right twrp to go along with it.

It's worth noting that the latest update (April I think) doesn't yet have a twrp that will work with it.

Also some roms need a specific or minimum software version before you can install the rom so you should check the lineage thread for that.

some updates also have new bootloaders which means when you update to a certain version you will not be able to downgrade to previous versions. For example if you flashed an Android 10 firmware then you won't be able to restore a backup of ASJG as the bootloader will have changed.

You also do not need to extract the downloaded AP file, just open it. The process would be:

Download firmware zip

Unzip files (ap, bl, csc etc)

Download and patch twrp

OPEN ap file with 7zip and replace stock recovery file with twrp (make sure you rename twrp to 'recovery'.)

Patch the AP file that now has twrp in it. (After patching ap file you may end up with a zip file, this is fine you can flash the zip through Odin in the AP slot)

As for the recovery file inside your firmware being named 'recovery.img.iz4' I have never come across this issue before sorry!
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] hanspampel:
The ctc9 sources are up now.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Pogromonolith:
Thank you [MENTION=10006231]Philnicolls89[/MENTION]!

I think you've cleared most of my confusions.

Do I need to patch the TWRP file as well? Or just use it as is?

Also is it important to also flash vbmeta_disabler after TWRP is up, before flashing the multidisabler?

(Extracting vbmeta_disabler.zip to vbmeta.img, tar it with 7-Zip to vbmeta_disabler.tar, use Odin to flash the vbmeta_disabler.tar via the AP slot, unchecking Auto Reboot in Odin).

The one thing that is weird is that I can't replace the recovery.img file using 7-zip (or am I missing something very trivial here?).

When I open the AP file using 7-zip, and drag the recovery.img file inside, that's what I get:

[IMG="Dragging recovery.img into 7-zip AP file"]https://pictshare.net/exmbqi.jpg[/IMG]

[IMG="Error after dragging recovery.img into 7-zip AP file"]https://pictshare.net/t4oi0r.jpg[/IMG]

Anyone ever encountered this or know how to resolve?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Philnicolls89:
You need to patch the twrp recovery file with magisk aswell yes, (before placing it inside the AP file). Ians multi disabler includes the vbmeta disabler along with other things, and yes, make sure that you flash it once your in twrp(After the full wipe of course;).

As for the 7-zip issue, I can't say I have come across that error before. What 7-zip are you using? And could it just be because you need to delete the original recovery file first? Then drag and drop the new one?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] amakuramio:
Confusing, geitis nemesis kernel and twrp have magisk included and dont need weird button combination, plus the rom is rooted easily, just flash twrp, then nemesis kernel and disabler.

Why would anyone choose Ians twrp and do so many steps?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
A few reasons to use this version of TWRP and continue to root one's device in recovery are:

Rooting in recovery is the only officially supported method on these devices by John Wu, creator of Magisk.

The vast majority of users do not (wish to) run the Nemesis ROM.

TWRP can be configured and built in many ways. The builds available via this thread comply with TeamWin's guidelines for Android 9+ devices.

Holding down a couple of keys when booting really isn't the hardship that some make it out to be. You get used to it.

Other users will probably have additional reasons.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
Version 3.3.1-103_ianmacd released for G97[035]F.

There are many changes to the kernel source code in the CTC9 firmware, so if you are running the latest firmware on your device and you want to leave TWRP in-place and boot Android from its kernel, you will want to upgrade to this new version of TWRP at your earliest convenience.

Changelog

v3.3.1-103_ianmacd for G97[035]F [inc. CTC9 kernel] (2020-03-31)

Rebase kernel on Samsung's CTC9 source code.

This version is intended for use only with Android 10.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Pogromonolith:
Thanks again [MENTION=10006231]Philnicolls89[/MENTION]!

I believe it's an issue with 7-zip on my system.

I get the "not implemented" error with any change I try to make within 7-zip (therefore I can't delete files withing the archive as well).

Also, when I extract the AP archive, 7-zip shows the following warning:

"There are some data after the end of the payload data".

What I managed is to extract the AP archive using UniExtractRC2 instead of 7-zip, then I can replace the recovery file and re-archive using 7-zip into .tar.

The original AP file is .tar.md5.

With this method I end up with a .tar file.

Should that be safe to continue and flash using Odin?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Philnicolls89:
Yes, I believe the .md5 extension is just a sort of security verification used by Odin but it's not necessary.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] matury:
Hi all, so I been trying to install TWRP in the S10 for a while now with no success.. and I need some help. I was able to root with Magisk, but when trying to install TWRP I am unable to boot (button combination) to TWRP, it just keeps on bootlooping. I tried 5 time with no success.

So a little more info:

I am able to install Magisk no problem.

S10 AP_G973FXXU2ASF3_CL16247232_QB24321558_REV01_user_low_ship_meta_OS9.tar

My question is " Do I need Version v3.3.1-4_ianmacd for G97[035]F [inc. ASF3 kernel] ??? or may I use v3.3.1-13_ianmacd for G97[035]F [inc. ASJG kernel] ???
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] cameronkelley28:
The issue is that you're trying to inject the TWRP recovery.img into the original, un-patched AP file.

1. Patch the AP file (xxx.tar.md5) with magisk and you'll end up with the magisk_patched.tar file.

2. Patch the TWRP image with magisk and you'll end up with a magisk_patched.img

3. Rename magisk_patched.img to recovery.img and inject it into the magisk_patched.tar with 7zip.

4. Flash the magisk_patched.tar (with replaced recovery.img) in ODIN as the AP, along with the CP, BL, and HOME_CSC (or just the CSC if you want to fully wipe your device - HOME_CSC retains your data and doesn't wipe the device)
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] MarkMR73:
I flashed the current TWRP (103) onto my G975F with BTB3 today. Everything went as usual until I wanted to scan a QR code.

I only noticed that the Samsung camera app no ​​longer works.

So I flashed the TWRP (102), but unfortunately the phone reboots when I try to enter the PIN.

So back to TWRP (103) with the camera app not working ...

Can I do anything to make the camera app work again or do I have to go up to CTC9?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] cgirerd:
Which ROM are you using? I know that there is a combination of TWRP version + ROM version that works. For instance, BeyondROM v6.6 (based on BTB3) works with twrp 102, and when flashing the update v6.7 based on CTC9, TWRP as to be updated to 103. BTB3 would not work with 103, and equivalently CTC9 would not work with 102. Any bad combination leads to issues like the camera not working, as reported by users yesterday in the BeyondROM thread after updating to CTC9. Also, TWRP has be patched by magisk as usually before it is flashed. Don't know if it is possible to roll back to a previous version though, but I would guess that it is possible.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] MarkMR73:
I use the Carotix rom. Who is still working on the CTC9. Unfortunately I had noticed too late that TWRP 103 is not backwards compatible.

Since I don't feel like a double full wipe, I wait for the CTC9 and do without the camera.

Maybe it would work with the 102 if I then flash the BTB3 dirty again.

But I also lack the motivation to do so. It's just the camera ...
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Philnicolls89:
I have just downloaded version 102 of twrp from the link in #2nd post of this thread, but I do not know how to compile the files downloaded from the github device tree into a disk image file??

The instructions are very vague for the uneducated :silly:

Or I would be very grateful if someone could upload version 102 here for me!
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] cgirerd:
Here you go: https://androidfilehost.com/?fid=4349826312261719164. You could have found it by following the link of the latest twrp, going in the developer's profile, and navigating between his folders to reach the previous versions that are still online :)
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Philnicolls89:
Thank you, and thanks for the tip. I did not think to go into the developers profile and look for older versions. :good:
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] DJBhardwaj:
Hi, when flashing the patched TWRP image (renamed to TAR properly as per the instructions in OP) via Odin, do we also have to flash the other firmware files like BL, CSC, and CP along with it?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] hanspampel:
No. If you only want to flash the recovery, its enough. If you want flash the patched fw (ap), you have to flash all other stuff too. Otherwise it would shrink your storage.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Keule-Tm:
You would probably know that, but for the protocol: it's not renaming, but packing. You need to do it via eg 7zip.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] 3lastic:
Samsung S10e with latest magisk and this TWRP my camera doesn't work, tried everything..sometimes it works in Lockscreen mode.. any ideas?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] alecxs:
"tried everything" does neither tell us what exactly tried already nor leaves room for any possible "untried" answers. furthermore "trying" in general can be part of the cause

check if your problem is related to encryption, for example broken fstab. the recommended multidisabler will change the encryption type from FBE into FDE which is a common bug. magisk has exchanged this bug with another bug half a year ago, now magisk breaks encryption completely (versions >7.3.5)
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] royhanks3:
Hey Ian, would it be possible for you to update the kernel for G997B ( S10 5G)?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] angiotell:
Hi. I've versione 3.3.1-0

How can I update to v3.3.1-103_ianmacd for G97[035]F [inc. CTC9 kernel] (2020-03-31)?

Thanks
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Faulkner33:
ok so ive got magisk installed now how do i flash twrp and do i flash .img or tar
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] p@to:
Rooted device..

From OP

Do this

# f=/storage/emulated/0/Download/magisk_patched.img; dd if=$f of=/dev/block/sda15 bs=$(stat -c%s $f).

Read OP for better explanation
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] WaningGibbous:
I'm having some trouble getting this to work.... I'm here from the LOS 17 thread, and plan on using Ivan's magisk patch, so I am not worried about doing anything with Magisk for now.

I am just looking to flash regular, non rooted TWPR and continue on with Ivan's directions. I've had this working in the past with LOS16 but wanted to do a clean install.

I flashed stock CTC9 with no problem in Odin (v3.14.4) . Now when I try to flash vbmeta it fails and give me the error on my device "only official binaries are allowed to be flashed VBMETA". It still boots to stock without issue. Same thing when i tried flashing my .tar of the recovery.img (3.3.1-103, yes the correct file for my device, 0). Sometimes Odin will hang on the "making connection" step, and other times it will just crash as soon as I hit flash. None of these things are happening when I try to flash stock FW.

What exactly is going on here? Do I need to be flashing something in CSC at the same time as AP?

To make the .tar files I am just right clicking them and choosing 7-zip>add to archive... Then selecting "archive format">tar . I've tried renaming them to "vbmeta" and "Recovery" both with the .img.tar and just .tar.

When I try with heimdall i just get this.... i have adb installed, and am not sure if there's something else i need for it to work. Heimdall detects my device, when i tried to print the PIT file just to see what would happen, i get the same error. I am running these commands as SU, by the way.

Claiming interface...
Setting up interface...
libusb: error [op_set_interface] setintf failed error -1 errno 110
ERROR: Setting up interface failed!
Releasing device interface...

sometimes it gives me this error

libusb: error [op_set_interface] setintf failed error -1 errno 71

i have been trying with differet cables, ports, and computers
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] jmch83:
Hi. First of all I feel sorry for my English. I use google translate.

I have a problem. My galaxy s10 stays in bootloop. It only lets me enter donwload mode but my problem is that odin doesn't recognize it on the pc. I have the option to relock the bootloader in download mode but I don't dare because I don't know if it's convenient.

I wanted to install LOS 17.1 and enter recovery mode, erase data, system ... the usual thing. I installed the latest TWRP from ianmcd to be able to install LOS 17.1 and there came the bootloop.

I have tried on several pc, on several usb ports, I have installed samsung usb drivers, kies, adb fastboot ... and still do not recognize odin. I have also used several versions of odin and nothing at all.

I use windows 10 ltsc in case it is of any use. I'm desperate already ...
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] giorgospav:
The link for S10E on the front page does not work. Maybe someone can fix it?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] bruram:
[MENTION=9230880]giorgospav[/MENTION]

try this

https://www.androidfilehost.com/?fid=4349826312261758026

this is the link in OP within the square [. .] and without "
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Jimmy Mossiba Floyd:
Hello every body! thanks to the OP for the hard work! I'm have recently bought an S10e Exynos and I've already rooted it with magisk with all being stock (the firmware I mean). now I want to flash TWRP without wiping data (if it's possible). Do I have to flash it from the TWRP official app and put the latest file I've downloaded here on xda (not from the app). Will I have access to the /data partition from twrp?

Another question: is flashing "multipledisabler.zip" mandatory or I can flash twrp without the need to flash it?

EDIT: Tried flashing TWRP through it's Official App and it went well without locking the /data partition. Now I'm gonna try multiple-disabler.zip
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] jibon89096:
This method is not advised if you'd want to flash LOS17.1 later.

Follow [MENTION=8518487]byteXpression[/MENTION] guide in LOS17.1 thread.

That should clarify everything.

---------- Post added at 01:05 PM ---------- Previous post was at 12:55 PM ----------

Hi everyone,

I have a problem I hope someone here can help me sort.

I've successfully installed [MENTION=7187684]ianmacd[/MENTION] 's TWRP on a Galaxy S10+, later rooting and flashing LineageOS 17.1.

Everything worked perfectly.

In the first backup I've made (right after flashing the ROM), I've included everything: 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.

Anyone can give an insight how to get back to normal?

Thanks in advance!