yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] gsser:
i will try to use date and time trick with july update, hope it fixes oem so that i can try again
[Samsung Galaxy S9 & S9+ Cross Device Development] Kocai:
I'm thinking of flashing TWRP on my G960F/DS so that I can install a custom kernel since I can't stand the atrocious battery life. My question is if I succesfully follow the guides provided on the first page and have TWRP fully functional, can I immediately just flash a custom kernel and root and then the phone will boot into stock ROM that's rooted and running on the custom kernel of my choice? Is there a step that I should take before flashing a custom kernel?
[Samsung Galaxy S9 & S9+ Cross Device Development] marquelito:
And?? Think youre the silly one. If there was problems with other devices what makes you think that s9 cant have other problems? Love s9+, but its not perfect. Neither you mate. Greetings
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
is it safe to update twrp 3.2.1.1 to 3.2.3.0 with the app from google store ?
[Samsung Galaxy S9 & S9+ Cross Device Development] rodrigoaguilera:
TWRP fails to decrypt the data partition, always reporting as "wrong password". LineageOS 15.1, the firmware used to encrypt said partition, decrypts it fine using the same passphrase.

Doubt it's relevant since they're entirely different ring levels, but my device passphrase (the one used to e.g. unlock the screen) is different from my disk encryption passphrase.

I Think it should be stated in the first post at least so the expectations are clear.

Seems related to

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1333

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1336
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
Yes that's a known problem and already reported here and on github. I hope it's getting fixed but it seems to be tricky with Samsung devices.
[Samsung Galaxy S9 & S9+ Cross Device Development] rodrigoaguilera:
Just out of curiosity: why is the device brand involved? as a user I would expect the firmware (LineageOS) to take care of the encryption and be similar accross devices.

Thanks for paying attention :)
[Samsung Galaxy S9 & S9+ Cross Device Development] batpoil:
I can't for the life of me try to flash this thing. I've been trying for the past 2 months on and off.

I have the OEM Unlock set to on in developer settings. I try to flash TWRP in download mode (OEM LOCK: OFF) and it says only official binaries can be loaded or something like that.

I go back stock thinking I would have another week to wait but the OEM is there, but ticked off. So I enable is, asks that it will have to reset to which I say ok, and as soon as I see the Samsung logo I send it to download mode, right? Well then I have the prenomal state, but OEM LOCK: OFF and I still can't load because of the official binaries error.

Please can someone help I'm about to throw this garbage of a locked phone in the trash

EDIT:

CURRENT BINARIES: Samsung Official

RMM STATE: Prenormal

KG STATE: Checking

FRP LOCK: OFF

OEM LOCK: OFF

Secure Download : Enabled

...

Only official released binaries are allowed to be flashed(RECOVERY)

I am trying in Odin, should I try with sideload ADB?
[Samsung Galaxy S9 & S9+ Cross Device Development] gsser:
Dont waste your time in Pie Firmware to get rmm state normal. it wont. If it will, you have to wait for pie compatible recovery which we dont have yet.

i can see that you are using pie beta firm because of KG STATE: Checking. I have waited 7 days for oem unlock, did a mistake by not going into download mode as i pressed factory reset. i wish i have read the replies as people explain those step better. when i was in pie, oem unlock will show whatever you do. BUT it will not revert back to RMM STATE normal. i have waited 7 days more to see if it will work, sadly didnt. so if i were you, i would flash latest oreo fw from odin and wait 7 days. im rocking at 47 hours uptime. ( dont ota update if you recieve.) for my experience; KG STATE is preventing rmm state to go normal. if you use oreo firmware you will not see kg state in download mode.

mine has oem and frp off with rmm state prenormal and secure download enabled only. i keep my developer settings enabled. when i reach 168hours uptime, i will look at it and if i dont see oem unlock, i will wait 1 more day and disable-enable developer settings.

so long story short: it takes minimum 2 weeks to get twrp. as i see many people having this issue, maybe guide is outdated and latest oreo firmwares patched that exploit of not waiting 7 days more....
[Samsung Galaxy S9 & S9+ Cross Device Development] batpoil:
Thanks for this! Unfortunately, I did the waiting thing on oreo before and like you, didn't go to download prior it doing a full reboot. Anyways, what I will do is trade this POS for something else that will let me unlock my bootloader as I see fit, not play their retard waiting game 7 days at a time.

Thanks for the help and good luck all.
[Samsung Galaxy S9 & S9+ Cross Device Development] gsser:
im also looking for alternatives... i have unlocked my bootloader in pie, if it wont work in oreo(rmm state) i will go back to pie, relock. then go back to oreo and wait for oem unlock toggle.
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
This here was mentioned:

https://twrp.me/faq/encryptionsupport.html
[Samsung Galaxy S9 & S9+ Cross Device Development] Retenor:
Hey there, reporting back!

So far, using this and magisk seemed to work, but today I stumbled across a weird issue.

Whenever the screen goes off by the auto timeout, it won't turn back on, even if I press the power button. Also happens when I turn of the screen for more than 10 seconds. This doesn't occur when the always on display is active tho.

I'm assuming the firmware is crashing somewhere, but I'll somehow have to fix that.

Haven't flashed a custom kernel but am now thinking about it.

Would like to go for the endurance Kernel (xdaforums.com/galaxy-s9/samsung-galaxy-s9--s9-cross-device-development/kernel-endurance-kernel-v1-0-t3849434), is it compatible?

What would be the steps for me now? Do I need to reset the device otherwise? A normally initiated android reset didn't quite do anything.

For now I'll restore a backup I made before really doing anything besides installing TWRP iirc, and see if that helps.

Also I don't know if it's a TWRP related issue, I also had XPosed installed at some point.

Any further suggestions? Thanks for help in advance :)

EDIT: Restoring a Backup did (as I expected) not help.
[Samsung Galaxy S9 & S9+ Cross Device Development] NoYbee81:
Hi All,

Would you be so kind to help? For some reason my camera has stopped working after rooting the S9 (SM-G960F).

Any ideas?

I used:

Odin3 3.13.1

twrp-3.2.3-0-starlte (for Galaxy S9)

no-verity-opt-encrypt-samsung-1.0

elementalx-s9-1.14

Magisk-v18.0.zip

Thank you!

N
[Samsung Galaxy S9 & S9+ Cross Device Development] batpoil:
Can someone confirm the correct way to install TWRP on this phone please? I have latest Pie firmware. I should:

Flash back BRJ6 Oreo.

Lock bootloader.

Wait 7 days.

Unlock bootloader, format, cancel midway, reboot download and flash TWRP with Odin?

Thanks!
[Samsung Galaxy S9 & S9+ Cross Device Development] ASMstudent:
I'm trying to flash the twrp recovery, but I keep getting "only official binaries are allowed....." error. Knowing that I have oem unlock enabled with RMM state as pre normal and waiting for 7 days didn't help as it never changed from pre normal from day 1 I bought the device till today regardless of how many days I waited , what firmware I'm on or wiping everything down.

Any help?
[Samsung Galaxy S9 & S9+ Cross Device Development] ratsalad:
It might not help with your situation but you're using an old version of TWRP there

Get latest one from here -> https://eu.dl.twrp.me/star2lte/
[Samsung Galaxy S9 & S9+ Cross Device Development] Yandvoiris:
had this issue

flash stock

leave oem unlocked

wait a week

flash twrp
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
You have unlocks done, so you should just have to wait on prenormal.
[Samsung Galaxy S9 & S9+ Cross Device Development] gsser:
Keep your phone on for 7 days and you will be ok.
[Samsung Galaxy S9 & S9+ Cross Device Development] ASMstudent:
I already kept my phone up for a week with OEM unlock toggle enabled and nothing changed. Using latest twrp didn't help nor did using miracle box to remove RMM state lock.

I have this phone for months and Prenormal state never changef for once.
[Samsung Galaxy S9 & S9+ Cross Device Development] Yandvoiris:
as i said before you must flash stock android 8 and then wait
[Samsung Galaxy S9 & S9+ Cross Device Development] batpoil:
I had the same and like the other user said, you need to flash stock oreo, relock bootloader, wait 7 days, then unlock and properly flash twrp. At least that's what I'm doing.
[Samsung Galaxy S9 & S9+ Cross Device Development] Yandvoiris:
no need to relock

i unlocked my while in the beta

flashed oreo back and waited a week
[Samsung Galaxy S9 & S9+ Cross Device Development] ASMstudent:
I already took your advice and clean installed a complete stock Oreo firmware yesterday. OEM unlock is gone, but I'll wait and see what will happen in 7 days.
[Samsung Galaxy S9 & S9+ Cross Device Development] Yandvoiris:
in my case the unlock option didn't showed up but the prenormal status was gone

since the bootloader was already unlocked i just flashed twrp
[Samsung Galaxy S9 & S9+ Cross Device Development] Vapochilled:
Im doomed! lol

I did the format .. and know im on boot loop.

The format failed several partitions :|
[Samsung Galaxy S9 & S9+ Cross Device Development] Matce:
Hey guys,

is there any update on what works with PIE already?

I'm currently still on Oreo - unlocked, rooted with Magisk.

Just downloaded Pie, ready to flash with Odin but will TWRP+Magisk work? Which version? How to flash it?

Previously I had the following procedure:

Flash update files through ODIN with Autoboot OFF

Immediately after the flash, go back into download-mode and flash TWRP with Autoboot OFF

Immediately after go into TWRP and install patched boot and Magisk

Reboot - and voila.

Will this still work after Pie?
[Samsung Galaxy S9 & S9+ Cross Device Development] grandwizard:
I had no success to install TWRP (3.2.1. and 3.2.3.) after upgrade to Pie on S9+ (SM-G965F/DS).

Odin (3.13.1) failed, nothing happened.
[Samsung Galaxy S9 & S9+ Cross Device Development] aeroman:
Start again and install first Samsung USB Driver for PC

Flash latest Firmware with Odin on your S9+ with Odin

Restart Phone and go Developer Settings "Allowed unlock Bootloader/OEM"

Restart Phone Download Mode, connect device Usb, start odin with admin

Odin Settings: untick Autoreboot! After complete flash Twrp v3.2.3

press following buttons for restart phone manually (volume down + power button for 7sec)

press following buttons immediately after restart (bixby + volume up + power button for 7sec)

(If the Twrp Recovery does not start, you were too slow! Repeat Twrp Flash)

On this way I was able to get Twrp v3.2.3 running on the S9 + Pie, :good:
[Samsung Galaxy S9 & S9+ Cross Device Development] grandwizard:
Thank you for your reply!

With Oreo rooting was painless, but after the odin upgrade to Pie, there are no OEM unlock in developer settings. Maybe 168 hrs later...
[Samsung Galaxy S9 & S9+ Cross Device Development] mackentosh:
Still keeps failing
[Samsung Galaxy S9 & S9+ Cross Device Development] Drizzt321:
I'm having the same issue, can't decrypt the data partition from TWRP. I recall when twrp-3.2.1-2 came out shortly after I first installed TWRP and LineageOS, I could decrypt with a pattern, but after updating to the current twrp 3.2.3-0 I can't. I just tried changing to using a password, and it still doesn't work to decrypt.
[Samsung Galaxy S9 & S9+ Cross Device Development] Tachi91:
OTG detection is random. Sometimes it works, sometimes it doesn't. Different USB drives, sizes, and file system, Samsung OTG, Anker OTG, Offbrand OTG. All behave the same way. Sometimes it loads, sometimes it doesn't. Reflashed TWRP several times and reboots.
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
That's a known problem. Right now unfortunately there's no solution to that. You can find more infos in this thread or at github.
[Samsung Galaxy S9 & S9+ Cross Device Development] ASMstudent:
Unfortunately it didn't go away. OEM lock was off as you said, but RMM state prenormal is still there. I lost hope and flashed oneui waiting for someone to find a solution to people in my situation.
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
I'm struggling with this issue too: When I'm trying to perform a backup at external SD card it always fails with backing up system.

Do I really have to wipe everything?

Unfortunately I can't attach the log file with XDA labs.

But i think this is the relevant point:

"I:Error writing destination fd (Operation not permitted)"

Now i'm asking myself: Why should the Operation not be permitted?

Thanks for help!

BTW: Backing up at internal storage works like a charm.
[Samsung Galaxy S9 & S9+ Cross Device Development] AlbertoS9:
Working on S9 with Sual Sim + MicroSD hack? Happy to donate if so.

Dear All,

I am currently on LightRom /Exynos/Team ExyKings, and it finally works again with my dual Sim and MicroSD hack, that Samsung Ass*oles blocked in June last year.

I was wondering if this Rom also works with the dual sim + MicroSD hack, if so I would install it on my S9 and make a donation as this really solves lots of issues!!!

Many thanks,

AL
[Samsung Galaxy S9 & S9+ Cross Device Development] mackentosh:
Twrp still a no go on Pie?
[Samsung Galaxy S9 & S9+ Cross Device Development] dari-woka:
answer:
[Samsung Galaxy S9 & S9+ Cross Device Development] dratif:
If anyone succeeds with this method please report
[Samsung Galaxy S9 & S9+ Cross Device Development] StarLte:
Escaped from the 7 day jail

Hi everyone,

I want to share my process of getting TWRP installed on a new Galaxy S9 (SM-G960F/DS) in case it helps someone.

It came with Android 8 Oreo installed. I used the rewind time and update trick to make the OEM unlock toggle appear in the Developer Tools. An Oreo update was installed, then an update to Android 9 Pie was installed. The trick worked, OEM unlock toggle appeared and after toggling it, asked to factory reset and reboot. This was probably when the Remote Mobile Manager (RMM) changed from normal to prenormal. I made the mistake of allowing the phone to reboot back into the OS, instead of entering download mode and flashing TWRP as the guide in post 3 of this thread instructs.

So now in download mode the phone showed that the OEM LOCK and the FRP LOCK were both OFF, but RMM STATE was prenormal, and so attempting to flash TWRP would give an error message saying: “Only official released binaries are allowed to be flashed (RECOVERY)”.

Next via Odin I flashed stock Android 8 with a CSC of Australia XSA. This was probably unneccesary. I then inserted a Sim card and triggered an update. This registered the device and I believe this is the moment when the 7 day timer starts – on Samsung’s server. I didn’t restart the phone, I checked for an update manually once per day and after 168 hours the OEM lock toggle appeared in the Developer Tools with a message that the phone was already OEM unlocked.

I rebooted into download mode and via Odin flashed TWRP and the patch to freeze RMM, FRP and the OEM lock state & installed a fork of LineageOS currently called /e/.

I don’t think flashing a different stock Android, inserting a SIM card, or keeping the phone on is necessary as I’ve since read reports of people keeping the OS it came with, not inserting a SIM and rebooting the phone multiple times and still having the OEM unlock toggle appear after 7 days. Also I never used a Samsung or Google account on the phone (I don’t even have accounts with them). One more thing to mention is that because I OEM unlocked the phone within an hour of getting it, 7 days later, when the OEM unlock toggle appeared again, there was no need toggle the OEM lock state and do a factory reset. I simply turned off the phone, rebooted into download mode and flashed TWRP.
[Samsung Galaxy S9 & S9+ Cross Device Development] :
can i install TWRP on Android pie?
[Samsung Galaxy S9 & S9+ Cross Device Development] petrevirgil:
Yes... I done this yesterday after update to pie... Same process...
[Samsung Galaxy S9 & S9+ Cross Device Development] :
thanks

i done it too with ElementalX...!
[Samsung Galaxy S9 & S9+ Cross Device Development] mackentosh:
Can you share how you did it cause the install continues to fail in Odin
[Samsung Galaxy S9 & S9+ Cross Device Development] dratif:
Need to flash it on Pie... anyone willing to help? Above mentioned methods to cumbersome
[Samsung Galaxy S9 & S9+ Cross Device Development] EagleSoldier:
See three posts above u
[Samsung Galaxy S9 & S9+ Cross Device Development] dratif:
Same process means? Same as for android oreo?
[Samsung Galaxy S9 & S9+ Cross Device Development] mahmoudnashat:
Hello all. I'm one One UI CSA2, and I've tried installing TWRP and then the patch as per the guide, and have an issue where I'm unable to use any biometrics on my phone. Even using a PIN code, I can enable it, but then when I enter the PIN code, I get an error that says the PIN code is incorrect. Anyone has this problem or knows how to fix it? Any help is highly appreciated. Thanks in advance!

Edit: adding to the above, I am also unable to log into my Samsung account. Once I restore to stock binaries, all the above issues are fixed. However, secure folder/internet browser secret mode (and possibly Samsung pay) do not work anymore, and it says that my bootloader is already unlocked in developer options (that's probably why the aforementioned apps don't work anymore).
[Samsung Galaxy S9 & S9+ Cross Device Development] Haphim:
Others have asked this question, but I haven't seen anyone answer it:

The instructions say that for the initialization of TWRP, you are supposed to NOT allow TWRP to modify your system.

The question is - after TWRP has been fully installed and initialized, how are you supposed to answer this question for future boots into recovery?

Should you allow TWRP to modify the system? Continue to not allow it? Does it no longer matter if you have a custom ROM, such as Lineage installed?
[Samsung Galaxy S9 & S9+ Cross Device Development] bdwilk:
Well I have read that too and saw it in videos as well but I allowed modifications and everything has been just fine. I don't know the reasoning behind not allowing so maybe someone smarter than me can answer that but from experience, on my device (s9+), allowing modification works fine. I've flashed many ROMs many times since then without problems.
[Samsung Galaxy S9 & S9+ Cross Device Development] Haphim:
Thank you, that's good to know. I didn't want to get everything set up just to screw the pooch the next time I went into TWRP and chose poorly. :)
[Samsung Galaxy S9 & S9+ Cross Device Development] bdwilk:
What worked for me might not work for you (you're welcome for the vote of confidence, haha) but I don't see any reason it wouldn't be alright.
[Samsung Galaxy S9 & S9+ Cross Device Development] Haphim:
Fair enough. :)
[Samsung Galaxy S9 & S9+ Cross Device Development] Kamikaze01:
Is it right, that i have to loos all data and apps when flashing TWRP?

Beecause no OTA is possible, i have to flash every Update via ODIN... is there a way just to flash the update files, or do i have to flash full rom?

Than i loos my root and have to flash TWRP (and loos all data and apps) every update?!

Please tell me, that there is a simple way and i am wrong !!!
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
You will lose all data only the first time you ODIN TWRP, as you have to format data partition to access it. After that you flash only the Roms and root if you want also.

You can still ODIN all of it but use Home CSC which doesn't wipe data, but I would stay with just Dev's Roms if you can.
[Samsung Galaxy S9 & S9+ Cross Device Development] dratif:
The guide says " when you enable OEM unlocking, the phone will ask for a factory reset. But DO NOT let it complete the reboot" how do I stop this from rebooting?? Means when there's startup screen displaying Samsung logo I press the power+Bixby+volume down button to go into download mode?
[Samsung Galaxy S9 & S9+ Cross Device Development] Kamikaze01:
Thank u very much for the answer.

In other threats, they told me to flash Android 9 only via ODIN (and Home_CSC). So I still have my apps and data. Only all permissions and my own ringtones are gone...

AND: lost root !!!

Now I have no TWRP anymore and have to loose all apps and settings to get TWRP and root again...

Did I made something wrong? Would it have been possible to flash Pie via TWRP (instead ODIN)

How to update and keep TWRP, Root and all apps and settings?

I like the stock Samsung Firmware very much. But which dev Rom can u advice me? (And where to download it)....?

Thank u very much in advance.
[Samsung Galaxy S9 & S9+ Cross Device Development] dari-woka:
once you install a rom through recovery, you have to flash magisk (before the first boot)
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Yes. I then ODIN'd TWRP from there.
[Samsung Galaxy S9 & S9+ Cross Device Development] mahmoudnashat:
Thanks a lot for your reply. I'm not actually looking to install a custom ROM. I just want to install a custom kernel, but stay on stock Samsung firmware (custom recovery + custom kernel + stock firmware). From reading different threads, it seems that is completely possible to do, but I can't seem to get it working without facing all the biometric authentication issues. Is there something I'm missing here?
[Samsung Galaxy S9 & S9+ Cross Device Development] Kamikaze01:
What about this thread?

https://xdaforums.com/galaxy-s9/help/root-galaxy-s9-exynos-9-0-android-pie-t3884267/page4
[Samsung Galaxy S9 & S9+ Cross Device Development] mahmoudnashat:
At the time of flashing, I tried the advise in this thread as well, and still had issues. To be fair, it seems the person who got this working fine is on CRLI, and I'm on CSA2. Not sure if there is an issue there. There's a few more comments, though, that suggest using a different kernel that has been built in CSA2's kernel (I initially wanted to use ElementalX). I guess I'll try that once I'm out of my 7 day RMM lock period.

Thanks a lot for your advise and for the link! If you happen to know any more information that could help with this, I would appreciate it if you let me know. Once again, thanks!
[Samsung Galaxy S9 & S9+ Cross Device Development] Kamikaze01:
No problem...

I am also on SM-G965F with G965FXXU2CSA2 and lost my root after update to Android Pie.

Now I am afraid of flashing TWRP or a custom kernel.

I like the stock Samsung FW and just want to get root again... But after Updating to Android 9 (flash G965FXXU2CSA2 via ODIN), my TWRP is gone.

And to flash TWRP again I will loose all apps and data :(

I am afraid I have to flash and loos root every single update :(
[Samsung Galaxy S9 & S9+ Cross Device Development] bdwilk:
This is precisely the reason most people who want twrp and root just use a stock based ROM like devsbase or lightrom. It's updated within a day or so of release by Samsung and you can just flash it in twrp with magisk and never have to worry about the things you are talking about.
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Agree.

It amazes me that with all real issues having been addressed back in April, all this thrashing around keeps going on and on. Yes they are new users, but they have access to tools and procedures that weren't there as we were working them out.
[Samsung Galaxy S9 & S9+ Cross Device Development] mackentosh:
You have to wait 7 days to get out of the "Prenormal" mode cause it will fail Everytime. Do not factory reset the phone before the 7 days, don't worry you can turn the phone off and it can go dead just don't factory reset it or the 7 day count will start over. Once your 7 days are up only then will you be able to flash twrp.