yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] byteXpression:
If you unlock the bootloader via the OEM unlock option in the stock recovery, you have to be on the internet at least once, so that the OEM unlock will be recognized. If you connect your device to the internet, go to developer option and check if the unlock boot option is enabled and greyed out. If this is the case, you are OK.

In order to boot to the bootloader (downloader) you will have to hold volume down (not volume up) and bixby and connect your USB cable.

Once you are in the bootloader (downloader) long press volume up to allow the bootloader accept other software.

Next time you reboot to the bootloader you will get a warning that your device is unlocked and you have to acknowledge it with the power button.

Back in the bootloader press volume down to proceed with flashing.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] superlutin:
Thank you byteXpression! Very sorry to bug everybody with such a simple problem, again. But this is my scenario:

1 fresh phone S10E - reset, reboot. No Google og Samsung account. I am connected, I can browse, i can check for phone update.

2 in Dev. opt. I go OEM unlocking, while connected

(2a reboot to check for greyed out OEM setting - never saw that)

3 adb to download mode

4 pressing volume up for maaaaany seconds. Nothing happens. Never. Topjohnwu writes: This will wipe your data and automatically reboot

5 reboot - normal, no warnings

6 OEM settings are not greyed out, setting is still turned on with blue switch active

I do not feel comfortable to go further Apparently there must be something basically wrong? I got my phone second hand. My sim is accepted and everything works normally. Can this still have to do with provider locking? Would a total reinstall of everything with Odin do some good?

byteXpression, you say: 'unlock the bootloader via the OEM unlock option

in the stock recovery

' I guess this is a typo?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] exocetdj:
Nice to see this ironed out

Too tired to try after airsoft but got something to do this weekend

??
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Geekser:
if i am currently on 3.3.1 (that you originally made before getting official status) do I need to flash the new "Official" version or are they essentially the same version?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
They are functionally the same: just built on different hosts by different people.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Carotix:
hi Ian,

i can't flash anything from recovery ...

can you take a look at this log?

recovery.log

thanks
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
The installer is trying to use Busybox, but TWRP for Android 9.0 no longer includes Busybox.

The installer should be rewritten to test for the presence of Busybox and Toybox and use whichever is available. Or, better yet, just call the applet by name and don't be concerned with which binary it links back to.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] TheUndertaker21:
hope we are able to flash img soon

specially to update twrp
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Carotix:
thanks ;)

but can i flash an app for example ? or better , how can i use this recovery , to flash what in this moment?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
You can flash an .img file. Just select the file, tell TWRP where to flash it and away you go.

The same applies to a TWRP image. It's no different in that regard.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] TheUndertaker21:
i meant as in

for future twrp update: root it with magisk and flash the img in twrp
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
You can do that. Flashing an .img to recovery is basic TWRP functionality.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] shorza:
Once we have TWRP, are we able to flash other Samsung firmware versions without wiping data?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] vegetaleb:
I don't understand, if this is twrp why some people say there are no twrp on s10/s10+? And no roms?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] drago122:
When it comes time to update your device's firmware, please follow John Wu's excellent instructions for patching the firmware's AP file. After using Odin to update the device with the patched AP file, reboot back to download mode and immediately reflash your rooted TWRP image. Alternatively, you may replace recovery.img in the patched AP file with your rooted TWRP image, thereby completing the upgrade in a single flash.

Hi Ian,

could you explain to me how to flash the twrp.img with odin since the files img are not loaded on odin ?? and if possible could you describe the steps to replace the rooted twrp image file in the ap patched file to make a single flash ?? you know I am not very experienced and I would not do damage.

thanks a lot
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] planck0815:
I do not understand that, too.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] aussiesausage:
I read somewhere that there was issues with custom roms booting due to the way something installs to a certain partition or something like that, I can't remember 100% but it was a long those lines.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] shorza:
Thanks for the help.

Just to be certain, i don't need to factory reset afterwards?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] tiho5:
No, but:

make sure you use you region FW and select HOME CSC when flashing it.

you must also go straight from download mode to TWRP after the FW was flashed and flash the multi disabler zip

then you can boot to system (by selecting boot to recovery in TWRP to boot to rooted system)
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
It's right there in the OP:

Also explained in the OP. Replace recovery.img.

If you're not comfortable tarring files and manipulating archives, you might want to hold off on rooting/TWRP until you have gained more experience. Otherwise, if anything goes wrong, you may find it hard to recover.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] tiho5:
I decrypted cscfeature.xml for my CSC and edited it to activate the "Caller ID and Spam Protection" feature as it is not available for my region. Then I made a flashable zip to flash this to my wife's S10+ and mounting /product was not working until I read this and indeed found toybox in /sbin.

I went with run_program("/sbin/toybox", "mount", "/product"); and things are alright.

So thank you
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
You're very welcome.

Note that script writers will do better to directly call the applets they need and ignore whether they link back to Toybox or Busybox:

For example, in your case:

run_program("/sbin/mount", "/product");
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Philnicolls89:
Not sure what you are doing wrong, once you enable oem unlocking in settings, turn off your phone. Then go into download mode using the button press and connect cable to your computer. You should then be able to unlock bootloader. Check out this video. If this doesnt work maybe try factory reset first?:confused:

https://youtu.be/s2Xp-lQg1xs
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Halim61:
Hi I have S10 Exynos on Security Patch for November. On Germany we have the security patch for December since a few days, it´s with Android 10.

Can I install the upgrade with twrp, and all works normally after update??
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] zabhi:
bootloop:crying:

dont do this wait for unofficial or official android 10 TWRP
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] hanspampel:
No kernel sources up for q, so no twrp with android 10. You have to wait till samsung releases there sources.;)
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] daphun:
Now they did :)

Mobile Phone

SM-G973F

G973FXXU3BSKO

SM-G973F_QQ_Opensource.zip
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] BSroot:
backup

I installed twrp and when I attempted to make a system backup, i noticed multiple new partitions im not familiar with

like baseband, efs, product, etc and im unsure what I need to back up to ensure I can successfully restore my phone from total damnation

if anyone can help it would be greatly appreciated
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] hanspampel:
Ill saw it. Up for all devices.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Philnicolls89:
For a full system back up just make sure all the boxes are ticked. There are 1 or 2 that may not be necessary but I do them all just to be safe.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
Version 3.3.1-12_ianmacd for the G97[035]F released.

Changelog

v3.3.1-12_ianmacd for G97[035]F [inc. ASJG kernel] (2019-12-03)

Rebase kernel on Samsung's ASJG source code.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] 1jkan:
Is there somewhere on the forum TWRP that works on Android 10 (BSKO) ?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Halim61:
Is this version android 10 compatible on s10?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] hanspampel:
ASJG is only Pie Version. BSKO ist the Q FW.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
Android 10-compatible test images were posted by me in this project's Telegram group today. Please try them out and report your findings.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] robbo1947:
Android 10

Now successfully updated my Magisk rooted S10+ to Android 10, firmware KSK0, and all is looking brilliant.

Have reverted (possibly only temporarily) to stock Recovery as couldn't get working with latest TWRP 3.3.1-12_ianmacd.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] tiho5:
It doesn't work in system but what if you flash TWRP and boot to it? Can you boot to TWRP? Make backup, restore or flash a zip?

Then change recovery to stock and boot back to system?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] mazzie66:
Any luck already?

Mazzie
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] jumpers:
hi guys,

i need a bit of help, because i'm totally lost,

someone from the CarHDMod sends me here for TWRP, and on that guide to root my device : https://topjohnwu.github.io/Magisk/install.html

my device is now rooted and Magisk is working fine, but, i still not have TWRP, and this topic totally lost me, i really dont know what to do next to have both TWRP and Magisk.

i tryed to download the IMG provided in the First Post, and patching it with Magisk Manager, Manager seems to have patched it, but after reboot, no TWRP, still stock recovery.

any tips for me ? because this working method is totally new for me, and i'm not understanding everything. (my semi-bad english doesn't help.)

thanks for helping me.

edit : i think i found why the image whas not flashin correctly tought Odin, the img whas not correctly renamed. TWRP is booting now.

i'm not able to make a backup, but i'm trying to check why.

edit2 : cannot backup with TWRP, it says "can not create '/data/media/0/twrp' folder (required key not available), can't figure out why.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] shatteredsight:
Guys I'm having the weirdest problems flashing Magisk & TWRP with my S10+.

I'm following Wu's instructions and [MENTION=2022726]PiCkLeS[/MENTION]'s instructions at post #9, bootloader is unlocked and OEM Unlock is greyed out.

I'm using "MagiskManager-v7.3.5-2019092201-ianmacd.apk" & "twrp-beyond2lte-3.3.1-12_ianmacd.img", so both versions kindly provided by [MENTION=7187684]ianmacd[/MENTION].

I already patched stock image AP file and TWRP image file with Magisk Manager (logs attached) with Recovery Mode option on (is this correct?),

un-tarred magisk_patched.tar, replaced recovery.img with the freshly patched TWRP image (properly renamed in recovery.img) and re-tarred everything back.

But after flashing everything with Odin it seems that no patching happend whatsoever to the files:

rebooting in recovery right after ODIN I have no TRWP but stock recovery and there is no Magisk installed in the system.

I noticed that during the first reboot after flashing the image I see briefly an Android animation with the two turning round arrows and the text "Erasing",

then it reboots and I can enter stock recovery and perform wipe data/factory reset.

What am I doing wrong? Should I not use ianmacd Magisk Manager?

I attached logs and images with flashing information and Magisk Manager showing ianmacd version.

Thanks
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] robbo1947:
Android 10

Nope, tried flashing TWRP but will not boot to TWRP.

Just get Bootloader unlocked warning screen then S10 logo screen then reboot loop. The same result as I got when I tried merging the patched TWRP image into the magisk_patched.tar.

So be warned folks this new firmware upgrade to Android 10 does NOT like TWRP 3.3.1-12
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Nextasy:
Can somebody please tell me how to get our samsung s10+ "triangle up + exclamation mark" inside error mode? Odin FW flashing failed.

Smart switch PC doesnt not recognize the device, by the way..

Thx

---

SOLVED!!!!
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ninestarkoko:
That is very interesting, thanks for sharing.

Did you get other information about this issue? Was it repeatable?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] tiho5:
Don't worry about it. At that time file based backup was having a problem. It's been fixed.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] shatteredsight:
Just an update:

first of all, I'm an idiot... I was compressing in the tar file the whole directory instead of all the single files, so Odin was skipping completely the image.

Now I'm at the point that I have a working rooted system with Magisk but no matter the version of Magisk Manager I use, no matter the method

I use to patch TWRP (with MM inside the magisk_patched.tar file, with MM separately or with ODIN), I always end up with a bootloop with a long

black screen between reboots and no TWRP or stock recovery either. And unlike the stock rom, the OEM Unlock is NOT greyed out.

What am I doing wrong? Any insight? [MENTION=7187684]ianmacd[/MENTION] do you have any ideas? Sorry to bother you guys.

Thanks
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] |||||:
Is there any hope? Dispite Factory Reset? Any Way to flash twrp with odin or something?

https://xdaforums.com/galaxy-s10/help/how-to-restore-internal-sd-data-twrp-t4015235
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Philnicolls89:
Couldn't you just flash stock rooted firmware again using the home csc file to keep your data? Once the Odin flash is done don't let the phone boot up properly and just force pass through to twrp. Then you would be able to restore the backup??
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] |||||:
This is what I tried basically... problem is, I flashed new version of TWRP with TWRP to recovery, wich somehow wasn't accepted, so TWRP, wich I counted on, was gone as well...

So if there is any way to flash a twrp pre-enabled stockflash, this would be legendary and probably the easiest way to go for it...

I hope there is a solution...
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] |||||:
I found the solution!! ;)

IT was to flash patched TWRP (just rename it into recovery.img and put it inside a .tar archieve and flash it with Odin & and after flashing go right inside TWRP by holding VOLup + Bixby + POWER right on restart after flashing! ;)

See my Signature for more Insights :highfive:
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Chris4evernoob:
This still doesn't work for my S10+. I downloaded the lastest Android 10 firmware for XEF using Frija. I've patched the AP and twrp-beyond2lte-3.3.1-12_ianmacd.img. Then i've tried replacing the recovery.img inside the patched tar and also like you said, separately flashing the recovery inside it's own .tar.

Any time I flash something with the patched recovery, it doesn't work. If I just flash the patched AP, I can access the stock recovery. But if I flash the patched AP with replaced recovery.img, or patched AP and then patched recovery.img inside a .tar, I cannot access any recovery, and the phone just boot loops on the bootloader warning screen.

Any ideas ? Or does the recovery just need to be updated for the new android version, and I should just wait ?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] gitlygit:
Join Telegram. There are new builds there, more experimental but work on 10 (Q).
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
Version 3.3.1-100_ianmacd released for G970F, G973F and G975F.

This release of TWRP targets devices that have been upgraded to Android 10.

After installing this, you must ensure that you use the latest version of the multi-disabler, currently v2.1. Do not use earlier versions with Android 10.

Changelog

v3.3.1-100_ianmacd for G97[035]F [inc. BSKO kernel] (2019-12-07)

Rebase kernel on Samsung's BSKO source code.

This version is intended for use only with Android 10.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Chris4evernoob:
Thank you so much for your work.

I'm sorry I didn't realize the previous versions were only for android 9. I just got the phone yesterday and I thought the android 10 rollout had been going on for a while.

In any case, everything works perfectly fine now ! :good:
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Magendanz:
[MENTION=7187684]ianmacd[/MENTION], could you update your device trees on GitHub with these changes? I'm curious what has changed so that I can mirror them for the SM-T510.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
I updated them at the same time I announced the new release. However, you won't find much of interest there. The significant changes are in the kernel.

TWRP itself also requires a patch to prevent linker problems in cases such as this. Unfortunately, I can't submit this patch upstream at present, due to a privilege configuration error on Omni's Gerrit server that is preventing the submission.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Magendanz:
I'm actually building the kernel for SM-T510 right now because Samsung posted kernel source for the November 2019 Security Update last night. Is there a change you've made to some setting in the defconfig that breaks Android Pie support? I'd prefer not to have to make separate TWRP releases for 9.0 and 10.0.

Thanks for the heads up on this patch! I'll make the change locally before I build today.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
My kernel sources are linked from the OP.

Samsung's default config for Android 10 has quite a few changes from Pie. For one thing, the version of the kernel has leapt forward from 4.14.85 to 4.14.113.

So, I took the logical approach of making a diff between Samsung's default Pie config and my custom Pie config (yielding the changes necessary to allow root to work without issue on Pie), and I applied this as a patch against Samsung's default config for Android 10. The end result is an Android 10 config that allows root to work without issue.

You can try using this latter config to boot Android 9, but you're in uncharted waters there.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Magendanz:
Ah, that explains it. We haven't gotten an Android 10 build from Samsung for the SM-T510 yet, but now I'll know what to expect. Thanks, [MENTION=7187684]ianmacd[/MENTION]!
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Olli2k:
Hey, anyone managed to upgrade to BSKO already? With previous relases I did updates the following way:

- Download new Firmaware

- Extract it and copy AP file and current release of TWRP from this thread to my device

- Patching Magisk to both files via Magsik Manager

- Download to PC again, renamed patched magisk.img to recovery.img and replaced it in the patched AP tar.

- Flashing with odin (autoreboot off) with CP, Bl and home_csc from original firmware and special patched AP file

- Manual reboot while hitting recovery buttons (2 times, because first time TWRP installs something and reboots automatically) and flashed multidiabler (2.1 for android 10)

Voila and I was done. Mostly first boot time with new firmaware was like regular one.

With BSKO this seems not to work. Device seems to be freezed at SAMSUNG logo.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] rafalubo:
hello how are you I had the same problems and I solved it by putting the original rom then I installed Magisk and patched ap and recovery I put it by odin as always and it worked
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Olli2k:
Hey, thanks for this idea. Completley forget aubout this option :)
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] shatteredsight:
I think I found the problem:

back in march when I first rooted the S10+ I used TWRP 3.3.1-2 version, so I tried again with that version instead of 3.3.1-12 and it works!

Could it be because my phone is still with ASCA build version?
[MENTION=7187684]ianmacd[/MENTION] when you write in your changelogs "inc. XXXX Kernel" or "rebased on XXXX kernel", does it mean that any previous version won't work anymore

and the device must be updated or is it intended to be backward compatible?

Thanks
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
No, they are very often not backwards-compatible and there's no way to make them so. If you are using the kernel from the TWRP to dual-boot into Android, you should ideally use the build of TWRP that was compiled for your firmware version.

If you flash TWRP only on demand and replace it with stock recovery again before rebooting to Android, this is less of a factor, but there are still circumstances (e.g. an incompatible bootloader upgrade) that can make it impossible even to boot into TWRP. The 3.3.1-6 release and -10 releases were both watershed moments, as is -100, obviously, as that version targets Android 10.

See the first couple of posts in this thread for details of which builds of TWRP work with which versions of the firmware.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] tiho5:
TWRP on demand. That's what I'm always doing.

Therefore I want to ask if it's possible to please make a small announcement here when a new FW is out if the current TWRP can boot on it only. If it is possible.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] shani908:
s10+ android 10

gives this error .. I rooted by devices . works fine ..XEF-G975FXXU3BSKO_G975FOXM3BSKO-20191127..

but when i replace recovery.img after untar . and try to flash it, it gives this error

<ID:0/003> Odin engine v(ID:3.1301)..

<ID:0/003> File analysis..

<ID:0/003> Total Binary size: 7105 M

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> NAND Write Start!!

<ID:0/003> SingleDownload.

<ID:0/003> magisk_patched/

<ID:0/003> Unassigned file

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] vantjnh1991:
Hello Ian. Please support twrp for S10 5G. G977*.

Thanks you very much!!!
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
If someone upgrades his firmware and notices that there are issues with the current TWRP, that's likely to get reported here. In such cases, which don't occur very often, it's often an option to remain on the previous bootloader and keep using TWRP.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
I do have a TWRP image for this device, but it is not officially supported and not up to date. See the links at the top of this thread.

There has been very little interest in TWRP for this device. I have offered to update the current image, but every time I have asked the requester to send me the latest recovery.img from their firmware, it hasn't materialised.