yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] ^^rac:
Hi guys,

Thanks for this, can you please help me? Did i do something wrong.

I followes the steps to where i had to flash twrp, but got the custom binary error. I rebooted the devices, it told me it has to erase for it to be unlocked, and it did.

Rebooted and is all fine now. When i go to DEV Options i do see OEM Unlocked (It says your OEM is unlocked already) But i still cant flash TWRP? Or am i now in the 7 day period? Not sure as it looks fine.......
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Check Download mode. If you see prenormal, you will have to wait until it's gone.
[Samsung Galaxy S9 & S9+ Cross Device Development] ^^rac:
Thanks alot, will do, can i use the device as normal until its gone? :D
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
I did mine.
[Samsung Galaxy S9 & S9+ Cross Device Development] mackentosh:
You gotta wait 7 days, you can turn the phone off or it can go dead just do not factory reset your device or your 7 day count will reset and you'll have to wait another 7 days
[Samsung Galaxy S9 & S9+ Cross Device Development] wackowizzard:
Tnx! Nice work! :D
[Samsung Galaxy S9 & S9+ Cross Device Development] ettore88:
Hi guys.Id like to root my new phone S9 + with the latest fw android pie.My fear is to get the 7 Days OEM unlock!Does it still happen?In case it happens, the phone can not be used?Id like to root my phone with Magisk.Could you explain to me what the current situation is about 7 Days OEM unlock?Why does it happen?How can you avoid it?THX in advance.;)
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Do some more reading. First, go to download mode and see if the locks are on or off and if prenormal shows up. If locks are off and no prenormal, you are set to go with no 7 days but read - especially around April where all this was getting worked out.
[Samsung Galaxy S9 & S9+ Cross Device Development] ettore88:
Ok.I have read, but I did not understand what causes this block of 7 days. Can the phone be used during the 7-day block?
[Samsung Galaxy S9 & S9+ Cross Device Development] bdwilk:
The block comes from Samsung. It's a security measure. There's no way around it (publicly) and yes you can use your phone. The 7 day timer only gets reset if you factory reset your device. This has been mentioned 1000 times in this thread and it's very good practice to search and read a lot before attempting to modify anything.
[Samsung Galaxy S9 & S9+ Cross Device Development] bdwilk:
[MENTION=8152197]RE910177[/MENTION] you should read the guide in post 3 of this thread as well as the rooting guide. This might pertain to you

3. Go to Settings -> Developer options and enable OEM Unlock option.

Notice: This is "state transition" mentioned eailier.

NOTE: You will be asked to do a factory reset, that's normal.

BUT DO NOT LET IT COMPLETE THE WHOLE RESET PROCESS.

You should take a look at the whole guide and be prepared to use reboots as chances to flash or reboot into TWRP.

https://xdaforums.com/galaxy-s9/sam...development/twrp-exynos-t3763464/post75893923
[Samsung Galaxy S9 & S9+ Cross Device Development] RE910177:
@bdwilk yes i did but it doesnt work after seeing in dev options oem button still unchecked and also KG status its still "checking" so i decided to go back to oreo and so far so good.. still no luck with pie :(
[Samsung Galaxy S9 & S9+ Cross Device Development] bdwilk:
Well do like most of us and just use one of the stock ROMs that can be flashed in twrp. Devbase, lightrom, and my personal favorite ultimate ROM.
[Samsung Galaxy S9 & S9+ Cross Device Development] RE910177:
[MENTION=7478074]bdwilk[/MENTION] are you on android P?
[Samsung Galaxy S9 & S9+ Cross Device Development] bdwilk:
Yes. I'm on Ultimate ROM CSA2. It's stock OneUI with some custom features built-in.
[Samsung Galaxy S9 & S9+ Cross Device Development] RE910177:
[MENTION=7478074]bdwilk[/MENTION] looks pretty awesome :) guess i might stay with oreo a little bit because im still on the process of testing how well this work stock rom + ex kernel
[Samsung Galaxy S9 & S9+ Cross Device Development] Mietschein:
In the guide, it says:

But then it asks again whether you want to allow modifications a second time. Should I allow them the second time it asks ? Or do I need to keep rejecting ?
[Samsung Galaxy S9 & S9+ Cross Device Development] R-iel:
I'm gonna install TWRP on untouched S9+ with Pie on board, does it change anything to the whole process described in the guide?
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
It shouldn't
[Samsung Galaxy S9 & S9+ Cross Device Development] ettore88:
Done. Everything went ok.I have a root on my S9+.

I ask you for information.When there will be an update of the stock fw...I ll do a FULL WIPE from TWRP.(Dalvik/ART Cache,SYSTEM,Data,Internal Storage and cache.)Consequently via ODIN...flash the new vs of the stock fw.MY QUESTION IS:I will have to redo the Enable OEM Unlock from developer option?Or do I directly flash the TWRP?[emoji6]
[Samsung Galaxy S9 & S9+ Cross Device Development] daviddema:
I am on stock Pie, coming from stock Oreo, just upgraded 2 days ago via OTA. In Oreo, I never managed to get the OEM unlock toggle to appear or RMM prenormal to clear. Now in Pie, OEM unlock toggle showed up, I switched it on and factory reset the phone upon being prompted. In download mode, I see:

OEM lock off

FRP lock off

RMM state prenormal

KG state checking

Can I install TWRP or not? Or should I wait to see if the RMM and KG states will clear after a week?
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
If you had read more, you would have seen that when you selected factory reset, you should have gone immediately to download mode and ODIN'ed TWRP. Now you have to wait 7 days for prenormal to disappear.
[Samsung Galaxy S9 & S9+ Cross Device Development] daviddema:
Thanks for the reply gaww.

I have read a lot and I DID go straight to download mode after selecting factory reset (after toggling oem unlock). But I found RMM state prenormal and KG state checking, so I did not dare attempting to install TWRP and risk messing up my warranty. Then I just decided that it would be safer to just reboot to system and wait another 7 days to see if they might eventually clear.

When I was on Oreo, my OEM toggle never appeared and my RMM state remained prenormal after waiting several one week periods... Can't figure out why... During my reading I've seen several people for whom it was the case also ( [MENTION=6909327]ASMstudent[/MENTION] in this thread is one of them), but I have never seen a satisfying explanation of WHY the toggle would not appear for some and would for (most?) others.

After the Pie OTA update, the OEM toggle appeared immediately, so I thought that was the end of my woes. But before toggling it, I rebooted to download mode and found RMM prenormal and KG checking. Then I rebooted to system, toggled OEM unlock, selected factory reset and went straight to download mode without letting the system reboot. Again, found RMM prenormal and KG checking...

Don't know what to do now anymore... I can wait another 6 days, but if it doesn't clear it looks to me I am stuffed... and I will try to return the phone to Samsung. After all, this is supposed to be an anti-theft feature, and I didn't steal my phone. Because of their software "malfunctioning" or tagging me as a thief when I am not one, I have a crippled device over which I do not have full control. That is not acceptable to me.
[Samsung Galaxy S9 & S9+ Cross Device Development] ASMstudent:
Your warranty won't be void because Knox won't be tripped as it simply won't allow you to. You'll just get" only official binaries ......" Error.

I've tried tens of times and I always get same result ; warranty void still 0X0.

Samsung apps sometimes would tell me that my device is rooted and won't work, but I don't know if it was related.
[Samsung Galaxy S9 & S9+ Cross Device Development] bdwilk:
I believe that's because your bootloader is unlocked.
[Samsung Galaxy S9 & S9+ Cross Device Development] daviddema:
My fear was that it would maybe let me flash TWRP because of "OEM lock off" (tripping Knox in the process) but end up with errors in TWRP as some users have reported elsewhere, making me unable to flash anything else. In which case I would end up still unrooted, back to stock recovery AND without warranty. Maybe misguided fear, but I'd rather wait a few more days (50 wasted days are behind me already anyway) than take even a small chance.

So with Pie it got even more confusing... OEM lock off seems to mean the bootloader is unlocked, but RMM state prenormal and KG state checking (wtf does KG stand for??) mean it's still locked!? There does not seem to be any real in depth explanation of how it really works (or why it seems to fail to work as intended in some cases)... I've searched and searched and still no clue of why I - and others - cannot clear this limbo state... If it's anti-theft and we are somehow false positives, then we should be able to request Samsung to clear it upon presenting our proof of purchase...
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Odd. When going straight to download mode, locks were off and prenormal was not there. Prenormal keeps you from ODINing something like TWRP.

Trying will not hurt- it just won't work as long as prenormal is there.
[Samsung Galaxy S9 & S9+ Cross Device Development] ettore88:
Hi guys.Im sorry,but I don t understand a thing.I ve rooted my s9+.If for example tomorrow I would be a full wipe from TWRP..and I wanted to reinstall the stock fw through Odin ...to proceed to the root again I have to redo the Enable OEM Unlock from developer option?Or do I directly flash the TWRP?I wanted to know only this.I hope someone can answer me.Thx in advance.
[Samsung Galaxy S9 & S9+ Cross Device Development] bdwilk:
Yup. I agree. All I can tell you is pie enables OEM toggle no matter the RMM state and the KG state is only a pie thing. If you were to go back to Oreo right now then KG state would be gone (one less thing to worry about) and it's possible that the KG could have a longer waiting period as I was told. We all got errors in TWRP when we first flashed it but formatting data partition fixes that.

I skipped all of this using a method a guy showed me on telegram, which I will not share here because it was very long and intensive and doesn't seem to work for everyone as [MENTION=6909327]ASMstudent[/MENTION] tried it unsuccessfully.

My advice is to return the device and see if a new one will work better. Better to do it now as you'll have to wait for the states to clear on the new one anyways also.
[Samsung Galaxy S9 & S9+ Cross Device Development] vijaygopalbalasa:
Actually, the guide you posted was very short. So, I followed the following guide which I found on the web. Source Then, I have successfully installed TWRP and Rooted my Galaxy S9+ device. Thanks for everything.
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
There's no news about encryption, right?
[Samsung Galaxy S9 & S9+ Cross Device Development] wackowizzard:
Hey,

I have a problem. I have downloaded the latest TWRP version and installed it by the TWRP application. I wanted to boot recovery, to check if TWRP was installed, but I can not do anything with my phone. If I want to turn on my phone, my screen will remain black, with at the top left the text in red colour : "could not do normal boot, invalid KERNEL LENGTH!" Recovery does not work either. I can still boot in downloading mode. What went wrong?
[Samsung Galaxy S9 & S9+ Cross Device Development] wackowizzard:
Solved! I flashed TWRP with odin.
[Samsung Galaxy S9 & S9+ Cross Device Development] Drizzt321:
Bumpity bump this a thousand times. Just some reply, even "nope, haven't gotten to it" would be nice. Ideally a "working on it, giving us trouble" or "nearly done", but I'll take what I can get.
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
search and read. There is a ROM thread in this group that provides for encryption.
[Samsung Galaxy S9 & S9+ Cross Device Development] jstsmblaz:
hi guys, just to be on the safe side:

i have a rooted S9 running Soldier PIE Rom + Magisk with TWRP 3.2.1-1 and i want to upgrade to TWRP 3.2.3.

as i don't remember if i flashed dm-verity and force encryption disabler when i was initializing TWRP my questions are:

1. how do i know if i did flash dm-verity

2. what happens if i flash it again

3. so the correct steps to upgrade would be: 1. flash dm verity, 2.boot to system, 3. boot to recovery, 4.flash twrp img file (instal, image, recovery)

did i miss something?
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
I upgraded TWRP awhile back with their app and did nothing else - no problems.
[Samsung Galaxy S9 & S9+ Cross Device Development] jstsmblaz:
thx.

anybody else?
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
I upgraded by flashing in TWRP without any problems
[Samsung Galaxy S9 & S9+ Cross Device Development] jstsmblaz:
and you didn't flash dm verity? not now, not ever?
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
I believe I did that once at the beginning
[Samsung Galaxy S9 & S9+ Cross Device Development] santhy:
This change would seem to enable encryption options in TWRP, but I have flashed latest version (3.2.3-0) on a starlte and flashed LineageOS with MicroG nightly of 2019-02-27 (https://download.lineage.microg.org/starlte/lineage-15.1-20190227-microG-starlte.zip) but after enabling encryption on the OS I cannot get TWRP to decrypt the partition.

I suppose that since I am using an AOSP-based ROM this should be using Stock Android's encryption methods, and not the Samsung's proprietary ones. I am testing the encryption with a PIN, so I think the PIN number should be the encryption key, and it does not work (and it does not work either with default_password, although TWRP should also test for that automatically).

So, if there is a technical issue that needs solving for this to work, I can even try to give a hand here.
[Samsung Galaxy S9 & S9+ Cross Device Development] Mr. A:
Thank you for the wonderful work with TWRP.

Today I successfully rooted my S9. But the OEM is not unlocked. I guess we need to unlock OEM to flash Custom Rom, but OEM unlocking requires a factory reset.

So my main question is, should we unlock OEM after rooting the device, is it necessary for anything? And Will the root go if I enable OEM and factory reset the device?

Someone, please help me.
[Samsung Galaxy S9 & S9+ Cross Device Development] Drizzt321:
Post #3, https://xdaforums.com/showpost.php?p=75893923&postcount=3, has all the instructions. However, there's generally a 7-day delay from last reset to when OEM Unlock becomes available. Once you enable Developer Options (Step #1), if you don't see OEM Unlock as an option, you'll have to wait. Keep checking back daily. Once you have it available, start from step #2. Ensure you read through ALL steps before doing anything, and you have all downloads/etc you need.

After it starts to reboot to do it's reset, hold [VOLUME DOWN] + [BIXBY] + [POWER] as it restarts. It may take some time, or it may be very quick. The full details are in step #7, but you'll need the rest of the downloads/computer drivers in the previous steps as well.

Like I said, read through EVERYTHING before you do anything so you know what you'll have to do as a next step, as some things you only get 1 good chance to get right without having to start over.
[Samsung Galaxy S9 & S9+ Cross Device Development] bdwilk:
If you were able to flash TWRP then your bootloader is unlocked. Otherwise you wouldn't have been able to. Once you flash TWRP then you shouldn't ever think about the OEM toggle again. If you're still not convinced then check in download mode and see if OEM LOCK is off. That means it's not locked.
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
I assume the problem is still the same.

https://twrp.me/faq/encryptionsupport.html

It would be great if there would be some kind of progress.
[Samsung Galaxy S9 & S9+ Cross Device Development] net37:
Special Patch

Hi All

It's not immediately clear to me if I need to flash the special patch "dm-verity and force encryption disabler" if I intend to install a custom ROM (Lineageos) pretty much straight after TWRP?

Or is the patch still required to stop "stupid" behavior even with a Custom ROM?

Thanks for any help
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Probably should, as those ROMs don't have added mods to fix these. Flashing a modified stock rom would.
[Samsung Galaxy S9 & S9+ Cross Device Development] :
Hello, sorry if it's a dumb question but I'm new to modding on the S9. Through decrypting by using the Force Encrypt patch the phone is much easier to hack (at least that's what I could find out about it) but safety is important to me, so is there any possibility to encrypt the device again after flashing a GSI (f.e. Phh-Treble 9.0 without root) through TWRP? Or is there any other possibility to flash a ROM/GSI with TWRP without losing so much security?

Thanks in advance.
[Samsung Galaxy S9 & S9+ Cross Device Development] LavaSnake54:
If you want to root, you will have to sacrifice Knox. And yes the security that Knox provides when you're not rooted is pretty good.
[Samsung Galaxy S9 & S9+ Cross Device Development] :
I thought that flashing TWRP already triggers Knox, not only root?? :confused:

And even though Knox is a good security feature, I don't think I would be able to use it if I flashed a stock rom that isn't based on OneUI.
[Samsung Galaxy S9 & S9+ Cross Device Development] pasbec:
Waht about DevBase ROM?

Its close to stock without Knox crap and you can use encryption - however without access from TWRP.
[Samsung Galaxy S9 & S9+ Cross Device Development] :
Thanks for the recommendation, sounds really interesting. But the only rom/GSI I want to flash is an AOSP rom. That's the only reason why I want to use TWRP.
[Samsung Galaxy S9 & S9+ Cross Device Development] kgr:
Hi I am unable to flash TWRP with Odin for some reason. In Dev Options, my phone shows OEM unlocked - see pic - but I get an official binaries message when trying to flash. I've tried Odin v 3.11.1, 3.12.3, 3.13.1. Glad if anyone could point me to the problem. Thanks!
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
If you had read a little more, you would know about prenormal - look it up.
[Samsung Galaxy S9 & S9+ Cross Device Development] NotATechnician:
Sorry - I haven't seen anything that says don't - but I want to ask anyway, before doing something stupid..

I have just purchased the device. OEM unlock is ready, Odin running, TWRP downloaded, etc. The device currently has this build-number:

PPR1.180610.011.G960FXXU2CSB3

Patch level is Feb 2019

The device wants to do an update, which I would quite like to do, but want to be sure this process will work before I allow that.
[Samsung Galaxy S9 & S9+ Cross Device Development] NotATechnician:
I did all of this and now I am stuck with the Samsung Galaxy 9+ logo... I can get into download mode or back in TWRP, but system will not boot at all.

I cannot find a stock rom to flash and LOS seems like a bit of a gamble at the moment.

Does anyone have any advice?

Should I suck it up an go the LOS route? Should I keep looking for a stock? I'd happily wait another 7 days if there's a way to get my phone to reboot...

Thanks.
[Samsung Galaxy S9 & S9+ Cross Device Development] revtech101:
You have successfully installed TWRP if you are able to boot into TWRP.

Find Dr. Ketans instructions. It has some history regarding flashing additional files especially for stock rooted roms.

Wore case scenario, find your firmware here and do an Odin install with home_csc to keep your data:

https://www.sammobile.com/firmwares/galaxy-s9-plus/SM-G965F/

This will bring you back to stock. Your knox count is 0x1 now nonetheless.

Hope this helps
[Samsung Galaxy S9 & S9+ Cross Device Development] dedq:
Hey guys, just a quick quick question regarding TWRP theme I am using.

Whenever I restart the recovery I have to reflash the theme in oder to use it.

What could be the possible solution?
[Samsung Galaxy S9 & S9+ Cross Device Development] LavaSnake54:
Which theme did you use?
[Samsung Galaxy S9 & S9+ Cross Device Development] dedq:
This one:

https://1drv.ms/u/s!AmMjr4LSLfWfoBdhtVLSnhE_rLpI
[Samsung Galaxy S9 & S9+ Cross Device Development] tomhtg90:
is it safe to flash twrp when KG State is checking?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Yes.
[Samsung Galaxy S9 & S9+ Cross Device Development] :
New TWRP is out
[Samsung Galaxy S9 & S9+ Cross Device Development] leap_ahead:
anyone test it ?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
It actually offers very little new of interest to S9(+) users.
[Samsung Galaxy S9 & S9+ Cross Device Development] leap_ahead:
how to update twrp ?

and if u can help me with this two : .

https://xdaforums.com/galaxy-s9/help/to-backup-twrp-t3921968

https://xdaforums.com/galaxy-s9/help/how-to-update-firmware-twrp-custom-t3921966
[Samsung Galaxy S9 & S9+ Cross Device Development] davidk21770:
To update, I downloaded to my phone and used flashify. You can also use odin.

The 2nd link implies you're new to this. Did you read the beginning of this thread? Do you have specific questions about the process?

The 1st post - again - have you done any research? But... Everything except cache and preload. System image depends on what kind of restore you want and what you're backing up...
[Samsung Galaxy S9 & S9+ Cross Device Development] :
Why so complicated? Download the image (img) file and flash it with twrp.

Go to install and hit image
[Samsung Galaxy S9 & S9+ Cross Device Development] davidk21770:
Although I've done that, I don't like overwriting memory that I'm currently executing...

(With that said, in desperation, I've even used dd from a broken twrp to install a new version of twrp and the tablet survived to live another day ? - it had major partition corruption issues that I was working through).
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
So encryption still doesn't work?
[Samsung Galaxy S9 & S9+ Cross Device Development] Mr. A:
Hello everyone, I wanted to flash a custom ROM on my device (s9 Exynos) but before that, I want to back up my whole device first using TWRP. I have TWRP(3.2.3.0) installed but I am confused what items should we include in the backup. On other devices, there were only fewer items to backup but this one has so many. Anyone can help me with this?

​

What are the files that I should include in my backup just for the system, my apps data and other imp stuff?

If I select all and backup, its gonna be very very huge. Is there anything that I can exclude on backup? Please help. :confused:

Edit: is it necessary to update TWRP for s9 or the current version (3.2.3.0) works well with flashing custom ROMs?
[Samsung Galaxy S9 & S9+ Cross Device Development] leap_ahead:
For first time backup all except system img and vendor img

You can update twrp
[Samsung Galaxy S9 & S9+ Cross Device Development] blixer:
You should backup everything except 'System-Image', 'Cache' and 'Preload'.
[Samsung Galaxy S9 & S9+ Cross Device Development] Mr. A:
wow, that was quick. Thanks a lot.

But what if I have to make another backup for 2nd and 3rd time on a different date? Should I again add all in the backup or still I can exclude some more?
[Samsung Galaxy S9 & S9+ Cross Device Development] leap_ahead:
You can choose anything

But for first time i mean its good to have efs backup ...