yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] AlienSexGod:
YES! Follow the instructions on the first page to the letter making sure you do NOT let a system boot happen until you have all the patches loaded via multiple reboots into recovery. Only then will it all work. Sometimes you need to reflash root in Odin Twice to get it stable. I wouldn't be going Magisk for a which till it's fully sorted. If you aren't much of an instruction reader then this youtube is pretty clear just ignore his sound effects! I recommend Alexdr's rom for now.... Very stable, has excellent cleanup routines on install (saved me after FLash kernel gave me boot loops when I tried other peoples roms) and dirty flash is supported for updates after the initial wipe before rom install. Good Luck :highfive:

https://www.youtube.com/watch?v=g3IppGISkP0
[Samsung Galaxy S9 & S9+ Cross Device Development] metal450:
...This step was not listed in the instructions.
[Samsung Galaxy S9 & S9+ Cross Device Development] exocetdj:
magisk working perfect on soldiers rom - although alex's work is excellent!!!

currently enjoying V4A!
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
One more time - when I first set up my phone, I used a guide that linked "ROOT S9+(Exynos) + OEM fix + EFS Backup Tool" by dr.ketan"

In following the OP's instructions here - is that redundant now?

---------- Post added at 02:53 PM ---------- Previous post was at 02:39 PM ----------

careful - the youtube guide above uses the old no-verity and RMM zips - not the newer one in the OP here.
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
7 days over, and OEM unlock popped up - with the notation that it was already unlocked (as I had seen in Download mod). I went to download to see if RMM Prenormal was gone and it was.

Odin'd TWRP and back in business.
[Samsung Galaxy S9 & S9+ Cross Device Development] fkofilee:
Can i just confirm. After flashing TWRP & the fix - Wiping data etc.

When i boot back to the System - It shows OEM Unlock as off (Not switched on) But Download mode says OEM Lock is off?

IS it off though? :/

I only ask because my device was fine recently until it rebooted and then suddenly got the " Official Binaries" Blah Blah...

Luckily my device is H3G and the OEM unlock is always there.
[Samsung Galaxy S9 & S9+ Cross Device Development] NEMES|S:
This: "Luckily my device is H3G and the OEM unlock is always there" is amazing...

Can you please post the exact firmware you are using? About->Software (screenshot please)

Thank you!
[Samsung Galaxy S9 & S9+ Cross Device Development] fkofilee:
Yes Sir - I used to flash the BTU ODin files however - since they merged the CSCs - I dont bother but i did to restore my device this evening.

However as you can see - Its reverted to XEU / H3G

Hope that helps... Now back to my query.

Im guessing the toggle should be showing blue? HAs anyone had an issue where they had FRP OFF then suddenly it came on randomly?
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
its off, and with the special no-verity... zip here - it should stay that way.
[Samsung Galaxy S9 & S9+ Cross Device Development] fkofilee:
Awesome... Thanks very much
[Samsung Galaxy S9 & S9+ Cross Device Development] AlienSexGod:
Yeah I meant follow instructions plus stay in recovery till all patches are done...

Ok good to know! Magisk was better on my S7Edge. Since the fix is very new for S9+ I am a little reticent to give it a go atm. Working well for you? Soldiers rom couldn't install for me after I tried Flash kernel i got continual boot loops. Alex's ROM with his cleanup routines saved me there hence my loyalty.

Yeah well while I am pretty sure the old patches still work to break encryption and root I did intend the video just for people having issues and using teh latest patches if they have them :)
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
[MENTION=6371894]jesec[/MENTION]

After reading this in your installation instructions "TL;DR: Flash custom kernel before root or be screwed", I flashed a ROM that had a custom kernel plus the fixed Magisk, so root was done with one flash - but would the above happen or does it need a kernel flash separately first?
[Samsung Galaxy S9 & S9+ Cross Device Development] bigmaster:
Unlock the bootloader of American and Canadian Edition

We need a talented DEV to bypass S9+ Snapdragon's bootloader as well.
[Samsung Galaxy S9 & S9+ Cross Device Development] exocetdj:
Hi, I flashed a new splash via TWRP and after flashing, TWRP shut down and I now cannot reboot

I just get a black screen when trying to reboot into recovery and normal boot

no FRP error either

do you know what may have caused this?

I can access download though. hoping a TWRP flash will sort it but don't want to loose the setup I had if I have to return to stock (I do have a nand however)

reposted here as well as splash screen thread as may be TWRP relevant
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
I installed the latest TWRP an

d noticed an expanded list of modules that can be saved, including system image. I tried that but it failed after backing it up for several minutes. The regular system backup worked - but what

would the backed up system image be for ?
[Samsung Galaxy S9 & S9+ Cross Device Development] rfburen:
In post 3 I see the link to the no-verity-opt-encrypt.zip but I can't find any rmm.zip file. Where is it then ?
[Samsung Galaxy S9 & S9+ Cross Device Development] metal450:
...Umm, again, the step right before installing dm-verity explicitly says to reboot. Thus, no, you're not just staying in recovery, you're rebooting back into it and thus have to make a selection.

4: Go to "Reboot" menu and Press "Recovery" to reboot TWRP.

**(then when TWRP starts you have to either keep /system RO or allow modification. The question was "which?").**

5. Download dm-verity...
[Samsung Galaxy S9 & S9+ Cross Device Development] rm501:
I have enquired regarding this as well with no response.

However I have successfully installed TWRP and rooted so hopefully can provide some clarity to those who are confused as I was.

Basically after installing TWRP you only require the no verity patch as provided in OP. Then TWRP is done and installed and the op work is done.

Now if u want root, THEN you need the superSU zip and RMM and the other patch from the video. (or Magisk)

These packages are usually included in custom roms so you don't need to bother with them in that case.

If I am wrong, please correct me.

Thank you
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
The new special no verity zip here includes the RMM. The video had the a separate one and a RMM from the S8 I believe. I did the old ones earlier, and after having problems latter, used this now. Also, a few of the ROMs have this built in but I would still use it first, as that damn RMM is real easy to get activated and its back to jail then.
[Samsung Galaxy S9 & S9+ Cross Device Development] ingalaxyz:
Hello guys.

I want to share my experience because this is getting really confusing.

I bought a branded Galaxy S9 (not carrier locked) here in Australia.

The first day I enabled developer options, OEM unlock was there.

Flashed TWRP, and then proceeded with flashing DM-verity encryption patch etc.

Then SuperSU but after every reboot I lost root.

Then I flashed Elemental Kernel, everything was working fine (including SuperSU) but after I rebooted the phone I got FRP lock.

Couldn't go into TWRP recovery, only download mode.

In download mode FRP and OEM lock were "On" and RMM status "prenormal"

At the time being the Australian firmware wasn't available so I flashed through Odin the unbranded ARC5 using the HOME_CSC file so I don't lose my data and apps.

The phone booted normally but OEM unlock was gone.

I left the phone on for 7 to 8 days (168 hours on time), but OEM unlock still didn't show up in developer options.

Then I flashed the unbranded Australian firmware (ARCC) using the CSC file instead of HOME_CSC to begin from scratch.

OEM unlock still not there.

Is there any chance that I'll be able to flash TWRP and root the phone?

Would it be possible to enable OEM unlock through ADB or I need to wait 7 days?

Last time I flashed stock European firmware after 8 days nothing showed up
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
You can't use ADB fastboot now as the boatloader is locked.

One longshot - go to settings and search "unlock" as one poster said he got in early that way.
[Samsung Galaxy S9 & S9+ Cross Device Development] jesec:
Changelog - Apr 18, 2018 (twrp-3.2.1-2):

Refactor USB configurations (fixes ADB)

Remove /cpefs from filesystem table (fixes /cpefs warning/error)

Rebase Kernel to ARCC. (fixes I/O performance issues)

Use correct OTG mount path

Enable software encryption support (general AOSP only, Samsung method remain unsupported)

I recommend everyone to update to this build.

Note that for some reasons starlte (G960*) build does not show up on twrp website yet.

Please download the build via this link: http://build.twrp.me/twrp-3.2.1-2-starlte.img.tar
[Samsung Galaxy S9 & S9+ Cross Device Development] ingalaxyz:
Saw that post while searching the forum, unfortunately nothing shows up in the general settings search.

I just wonder if OEM unlock will eventually show in the Dev settings after 7 days, the last time I flashed the stock rom it didn't show up after that period of time.

I also wonder how I got FRP lock after rooting successfully and installing a custom kernel.

The only thing I can think is that I flashed HOME_CSC instead of SCS, maybe the unlock OEM counter needs the CSC file so it can wipe all data and begin from scratch, which I flashed the second time going back to stock
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
I think you are right on the HomeCSC - saves data but can cause issues. Which custom kernel ?
[Samsung Galaxy S9 & S9+ Cross Device Development] ingalaxyz:
When I bought the phone OEM unlock was in the Dev options straight out of the box.

Then I installed TWRP, the DM verity patch and the OEM unlock for all devices fix.

Then I installed flash kernel but the Bluetooth and Mobile hotspot didn't work.

And after every reboot lost root and had to install SuperSU again.

Then I flashed Elemental Kernel, root stayed, everything worked fine but when I rebooted the phone I got FRP lock.

At the time being the Australian firmware wasn't available for download so I flashed the European ARC5 with the home CSC. Waited 7 days without rebooting the phone and OEM unlock didn't show up in Dev options.

So I flashed the Australian firware that was available at the time, ARCC, using the normal CSC file and when the phone started I got the message that I need to connect the Google account that was setup in the beginning.

Which means that FRP lock is on, even after a clean stock flash wiping everything.

So now obviously I need to wait for 7 days again but I don't think that OEM unlock will show up again.

Tripped the Knox from rooting, I was thinking was kind of excuse to find to replace the device with the carrier.

An Android phone without root is sort of pointless
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
You're not the only one who is confused.

I received my S9+ this afternoon. It's the 256 Gb model, unlocked and unbranded for the Dutch (PHN) market.

I charged it, turned it on, and then skipped all the installation stages that I could until it successfully booted into Android.

Next, I updated the firmware over wi-fi to G965FXXU1ARCC/G965FOXM1ARCA/G965FXXU1ARCC.

After the phone had restarted, I turned on Developer Options, and lo and behold, OEM Unlock was immediately available.

I toggled it on, accepted the option to reset the phone, and let it wipe itself.

Now the phone has restarted and is awaiting installation again, but I'm currently too nervous to proceed with installing TWRP and rooting the device after reading about your experience.

I'm afraid I'll have the same FRP problems if I proceed, and possibly lose OEM Unlock for a week (or longer) in the process. Since I'm lucky enough to be able to OEM unlock the phone on day 1, I'd rather not lose that advantage by proceeding without fully understanding all of the variables here.

Can anyone here offer any advice on the best way to proceed? And out of curiosity, does anyone have an inkling why some people have OEM Unlock available from day 1? I had only heard unconfirmed reports of this until today, but now my very own device turns out to be one of the lucky ones.

Anyway, any advice would be gratefully received.
[Samsung Galaxy S9 & S9+ Cross Device Development] ingalaxyz:
As I've been reading from other threats it's all about the RMM state, if you go into download mode and see RMM state "prenormal" then you must wait 7 days to change to "normal" or else if you even successfully flash TWRP when you try to flash the RMM patch you may get the "not allowed to flash custom binaries" error message. Looks like RMM is linked with FRP and OEM lock like a multiple layer security lock
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
I'm no longer at home now, but I'll check the RMM state this evening.

I don't intend to run a custom kernel. I just want root. Even TWRP I could theoretically live without, if CF Auto Root is working reliably. I'm not sure whether that affects your advice in my particular case.

There are too many contradictory and incomplete reports about this device at the moment, and it seems that different devices really are behaving differently straight out of the box. Hard to know what to do for the best.
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Mine was available right out of the box as imported to the US. Was also lucky I did not have region lock to deal with. After some ROM and kernel flashes, everything blew up and took 2 7 day sessions to get back up.

I would not be afraid to TWRP with the instructions here, then pick a ROM (am on Soldier due to good working Magisk), but after there it gets iffy. I had my initial crash after installing a kernel, and my second after attempting Xposed installed through Magisk. On the latter one I did not loose TWRP, so was able to recover with nandroids, but even then there were some issues.

I appreciate the work here and with the other dev's - but really pissed at Samsung, who has made things really difficult since the S7"s.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
OK, I've just rebooted the phone into download mode. There I see the following:

SYSTEM STATUS: Official

FRP LOCK: OFF

OEM LOCK: OFF

No mention of RMM state at all.

I've seen screenshots of the Note 8 where there's a line for RMM state between the system status and FRP lock lines, so I'm assuming that's where it would be on the S9+, too.

Does this really mean I can go straight ahead and install TWRP and SuperSU? I'm almost too nervous to try.

And do I really need to run a custom kernel/firmware, or can I get by with stock as long as I properly disable all of Samsung's booby traps?
[Samsung Galaxy S9 & S9+ Cross Device Development] ingalaxyz:
By the sound of it you can safely flash TWRP, both OEM and FRP are off, as long though you've got the OEM switch in dev options.

Very strange you haven't got RRM state, if u flash the fix from blackmesa you should be fine.

You don't need a custom rom or Kernel though as I've read Alex's Rom runs perfectly and it's just stock cleaned up plus including all patches and fixes for these annoying security locks
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Link for lineage doesn't work.
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Original idea of blackmesa's fix is great but, unfortunately, it does not work as intended here (@ S9 / S9+). I suppose that at least a few "failures" here happened because of thinking that you are protected by this fix.

Blackmesa's fix is trying to find "vaultkeeper.feature=1" string in /system/build.prop and replace it with "vaultkeeper.feature=0" string. In result "ro.security.vaultkeeper.feature=1" line (if exists in /system/build.prop) is changed to "ro.security.vaultkeeper.feature=0".

Unfortunately, in case of S9 / S9+, there is no "ro.security.vaultkeeper.feature" line in /system/build.prop AT ALL, it is placed in /vendor/build.prop and after flashing blackmesa's fix it remains untouched. The only successful action done by this fix is to delete Rlc.apk (seems like it is not enough).

EDIT: I have updated Blackmesa123's fix to work with S9/S9+ and contacted him to replace it in his post :cool: It will avoid future "failures" if somebody prefer his RMM fix habitually:

https://xdaforums.com/showpost.php?p=75360965

Yes, it also cares about ro.security.vaultkeeper.feature line placed in /vendor/build.prop :)

BTW:

[MENTION=6371894]jesec[/MENTION] - I just noticed your new no-verity-* patcher which contain also alternative security fix related to RMM prenormal state prevention. Really interesting idea with placing overrides in /efs/factory.prop, but are you really sure about it? I'm not asking if property is overrided successfully or not (we can easy check by "getprop ro.security.vaultkeeper.feature"). I'm asking if you are sure that property is overrided early enough at boot to be effective (e.g. post-fs or at least before Rlc.apk checks this property), you know what I mean..
[Samsung Galaxy S9 & S9+ Cross Device Development] highaltitude:
I got all the way through things and into TWRP. Then tried to reboot to recovery again, and now stuck at the "only official released binaries..." I boot into download mode. It says "prenormal" and that OEM lock is off etc. From what I'm reading, I am screwed again into having to wait 7 days again?
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Yes, unfortunately..

Have you flashed EXACT BELOW version of dm-verity-* patcher, which contains also RMM fix?

https://androidfilehost.com/?fid=962187416754474353 (it is also linked in post #3)
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Well, I've successfully installed TWRP on the device, including flashing the dm-verity and force encryption disabler zip.

Now I just need to get root on it. I want to stick with the stock firmware.

Is it enough to flash the SuperSU 2.82 SR5 zip? The OP here makes reference to needing a custom kernel with some extra Samsung badness disabled, but I believe the SuperSU ZIP disables the same stuff in the stock kernel. Am I correct about this?

An alternative route is the Dr. Ketan method detailed here:

https://xdaforums.com/galaxy-s9-plus/how-to/guide-root-s9-oem-fix-t3763974

But I'm not sure if the details in that thread are still current. People seem to have mixed results.

Any advice?
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
You need RMM also or you will be heading to jail.

I had used that, plus the S8 RMM fix discussed above - which resulted in loosing TWRP and Prenormal popping up. Also, OEM and FRP locks went to on.

I am on the new fix zip above and everything working good right now.
[Samsung Galaxy S9 & S9+ Cross Device Development] ingalaxyz:
I assume you flashed the new zip above after 7 days when the OEM unlock appeared again?

Because with status "Prenormal" and OEM and FRP locks on obviously that option should be missing from the developer options?

Could you please share what exactly you did to get the OEM unlock switch to show again in the developer options?

And which stock firmware you flashed ? Normal CSC or HOME_CSC?

Personally re-flashing stock (first time I flashed ARC5), the OEM unlock didn't show up, maybe because I rebooted the phone or disabled the data now and then?

Now I've flashed ARCC and waiting again.

I think if there's a solid solution to make OEM unlock re appear again then everything can be sorted
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
The RMM patch is now part of the no DM and no encryption zip. From the OP:

So I already have TWRP installed and RMM disabled.

Now I just want root, ideally on top of the already installed stock ROM. Is flashing SuperSU 2.82SR5 enough, or will that not take care of the "Real-time Kernel Protection (RKP)" and "RKP Control Flow Protection" mentioned in the OP of this thread?
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
It sounds like SuperSU won't, based on the specific warning.

I wonder if the slightly modded stock kernel by Soldier would work...

Update- bluetooth may not work with it, has to be used with his ROM. Nice if he modded the kernel with the fix also.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Funny you should say that. I'm looking at Soldier's ROM right now, which is basically stock, with a very limited number of enhancements, and a couple of things removed.

I'm going to read through its full XDA thread, but I may well end up installing that.
[Samsung Galaxy S9 & S9+ Cross Device Development] Denis Meissner1990:
For me in the Download Mode it shows

OEM lock: ON

FRP lock: ON

I have no line with RMM

In Developer Options the toggle is visible

I have read the whole thread, yes all 23 pages,every post, but I absolutely can't get clear with that all

I'm so confused now, like I was with the first phone I've ever rooted: HTC Desire S

That's a long time ago, so I'm absolutely not a newbie

Until the S8 I rooted nearly all Samsung's

S8 was a bit tricky the first time but then no problem

And now I understood nothing, and that after more than 200 posts

WOW

Samsung you made it ?

Congrats
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Damn XDA website - just wrote an extensive guide and it dropped it when i tried to preview the post. That has happened before, and should have posted it as-is and then edited if necessary !!

I will try to do it again latter - too pissed right now.

Ok - had a beer and cussed out a scammer on a call that got thru Hiya, so ready to go:

If you are still at the above, and have not gone beyond it and run into a dead end with RMM Prenormal, then start this way:

1. Toggle OEM lock off, and see what happens. If you only get the popup warning about unlocking, you are lucky - just do it. Then go into Download and see if both locks are off and no RMM Prenormal. Then you are ready to go per the OP"s instructions here.

2. If you get the dreaded popup saying you have to do a factory reset and you do that (like I did unfortunately), you trigger a 7 day jail term. At the end, you would see the toggle again, but you should not have to do it - check Download mode and see if locks are off and not Prenormal. If so, you are ready to go like 1. above.

3. I you don't do the reset after toggling OEM off, then you might want to try something i didn't think of. Go straight to Download Mode after toggling and see if the two locks are off and if there is no RMM Prenormal. Then you could go straight to ODINing TWRP like above. If not, then you probably will have to do the reset, which gets you the 7 day wait.

4. You should probably select a ROM first that you want to install, and put it on your ExtSD.

Then after OINing TWRP and flashing the no- verity.. 1.0 from this thread, I would flash the ROM, as if you choose one with a Root option in aroma, you do it that way. The OP recommends flashing a custom kernel do disable more Samsung junk, so if you Flash a ROM with a custom kernel and root, you get it all done also.

Note - if you are using your phone and want to preserve apps and data (as you will have to format data which wipes all but the ExtSD, I would use Samsung Smart Switch to backup as much as you can, and if more on your internal SD, manually copy that also.

Anyway, give it a go if you are still where you were when you wrote this post.
[Samsung Galaxy S9 & S9+ Cross Device Development] Denis Meissner1990:
Oh Sh** :(

Okay, big thanks to you

I absolutely won't root until I understood that Sammy Sh**

Because I won't do anything wrong