yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9+ Guides, News, & Discussion] exocetdj:
Does rebooting with a custom recovery if you have not activated developer options cause the FRP error? Had that last night and had to restore to stock etc.

Could installing busybox to system/xbin (for v4a) also cause this?
[Samsung Galaxy S9+ Guides, News, & Discussion] :
Hi everybody. Today i flashed TWRP official to my device and rooted it with SuperSU, but this loads very long and i can't answer supersu requests. So it seems useless to me.

Any idea guys?
[Samsung Galaxy S9+ Guides, News, & Discussion] jcplus:
After exactly followed the instruction, the restart fell into infinite loop of the white Samsung logo.
[Samsung Galaxy S9+ Guides, News, & Discussion] DevilStyle:
Thanks, any news for work this? Thanks
[Samsung Galaxy S9+ Guides, News, & Discussion] Onikuro:
Same for me, tried 3 times, no root. Even tried after flashing the original ROM with Odin, no other zip installed (Odin Flash -> TWRP -> OEM Fix +root )
[Samsung Galaxy S9+ Guides, News, & Discussion] skivnit:
I had mine available when I bought the phone 2 weeks ago but now it disappeared lol
[Samsung Galaxy S9+ Guides, News, & Discussion] MSH2000FF:
I checked my developer options but I did not find OEM unlock as usual.

What to do ?

finished 7 day's.. not active
[Samsung Galaxy S9+ Guides, News, & Discussion] :
You don't have to post in every thread you can find...
[Samsung Galaxy S9+ Guides, News, & Discussion] joe535:
Ohh, so many different attitudes here... While reading one post, I assume there is defenitely no way to bypass the wait-time. Other posts make me assume that I just need to flash some files via odin, regardless of oem unlock...

So I wonder what is finally true...

And IF we have to wait, I also found several posts, saying that the uptime must be without shutdown. Others say you may switch off the phone, e.g. overnight when you dont need it...

hmm... So what is the worst case? If I flash TWRP while OEM-unlock is not visible, I will probably have to reflash a valid stock-ROM and wait again.. So any tries to workaround should be done at the very beginning of the waiting-period..

Does anybody know, how exactly this "feature" works? Are there parts of code in Bootloader and other parts in the kernel and they have dependencies ??
[Samsung Galaxy S9+ Guides, News, & Discussion] gaww:
If you can Odin TWRP successfully, you are home free. If you are still locked and/or prenormal is there - it won't let you install TWRP. The key is always check both in download mode.

7 days are triggered by factory reset or Odin of stock ROM. You can use the phone while you ar waiting - turning on/off doesn't matter.
[Samsung Galaxy S9+ Guides, News, & Discussion] LysolPionex:
I did both a factory reset and flashed stock, 203 hours ago. Any idea what could be preventing RMM normal?
[Samsung Galaxy S9+ Guides, News, & Discussion] GalaxyV1:
I always check Dr. Ketan's thread about rooting Samsung Galaxy S9+

I successfully rooted my device, it is actually simple just follow Dr. Ketans guide.

Thnks for the tutorial. :good::good: <3

After the 1st boot please check if you have OEM Unlock, before rebooting

I don't know how to attach image but here are my phone's bootloader ver / security

Build No. - R16NW.G965FXXS2BRI1

Bootloader - G965FXXS2BRI1

Security Patch Level - 2018-09-01

Thnks ^^
[Samsung Galaxy S9+ Guides, News, & Discussion] gaww:
Exactly what does download mode show with respect to the locks and prenormal (if it's still there)?
[Samsung Galaxy S9+ Guides, News, & Discussion] LysolPionex:
I wish I could just screenshot this, lol:

ODIN MODE

DOWNLOAD SPEED: FAST

PRODUCT NAME: SM-G960F

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Official

RMM STATE: Prenormal

FRP LOCK: OFF

OEM LOCK: OFF

Secure Download : Enabled

CCIC = MAX77705 hw: 3 main:27

WARRANTY VOID: 1 (0x030c)

--more stuff--

edit: I did a factory reset as well, to see if it will make a difference in 7 more days. All totaled, it's going on 3 weeks since I first cleared OEM and got the Only Official Binaries... message and had to reflash stock.
[Samsung Galaxy S9+ Guides, News, & Discussion] jonathan_moreno91:
Are you sure you have 203 hours already? Coz we have the same bootloader and august security patch. Mine got oem unlock visible after uptime: 168 hours/7days... Be sure to not turn off your phone. Leave it in idle mode, screen off doesnt matter just do not turn off/shutdown much worst do not factory reset it will go back to 0...
[Samsung Galaxy S9+ Guides, News, & Discussion] LysolPionex:
Positive. We'll see if a factory reset makes a difference. I'll do like you say and not turn it off.
[Samsung Galaxy S9+ Guides, News, & Discussion] gaww:
Your not paying attention - good luck
[Samsung Galaxy S9+ Guides, News, & Discussion] LysolPionex:
203 hours in, not sure what else I could have done. Thanks
[Samsung Galaxy S9+ Guides, News, & Discussion] jonathan_moreno91:
If you really did factory reset right now, then might as well flash again the stock rom since it doesnt matter you will have to wait another 7 days anyway. If you did not factory reset though, just be patient it will come out the next 48 hours..
[Samsung Galaxy S9+ Guides, News, & Discussion] jerryspring:
On aroma installer there is a CSC choice page. I'm on att network. Which CSC should I chose then? There are quite a few choices. Thanks.
[Samsung Galaxy S9+ Guides, News, & Discussion] gaww:
If on at&t us, they don't include it. I use detonator on us tmo, but not sure if they have done one for at&t yet.
[Samsung Galaxy S9+ Guides, News, & Discussion] vidit82:
Worked successfully

Thank you dr.ketan worked successfully with September patch!

:good::fingers-crossed:
[Samsung Galaxy S9+ Guides, News, & Discussion] Zer0Sense:
After OEM unlock appeared I flashed twrp and then after reboot to recovery dm verity encryption remover. After reboot to the recovery again OEM unlock for magisk chose multitool and the oem patch. Rebooted to system with no problems and made the first steps (added gmail account etc) and had working root (used titanium) I still gоt "only official binaries" after reboot. Do I need to open developer options and tick oem unlock again before I turn off the phone or why this happens 2. time already.
[Samsung Galaxy S9+ Guides, News, & Discussion] joe535:
Could anybody please be so kind and write a small table about the states and waiting-times to change these ?

E.G.

1. A new phone is always in State "xyz"

2. If you enable developer options, the state changes to "abc" and will remein for xxx hours (do never switch off phone)

3. You may enable now OEM unlock and the phone is in state vvvvvv. Now you can reboot to download-mode and proceed with the

steps as described in post number #nnnn

3. once you rooted your phone and/or flashed a new kernel, the state will be "ssss" and you will (always, never, after another xxxx hours) see the oem unlock options...

Thanks a lot in advance
[Samsung Galaxy S9+ Guides, News, & Discussion] jonathan_moreno91:
1-2. New phone , you can immediately enable developer option... then you have to wait for 7days without turning off until oem unlock appears.

3. Turning on oem unlock will require phone to format to factory settings therefore you have to wait another 7 days..

4. After you root the phone, if you did not see the oem unlock in developer option, DO NOT RESTART OR SHUTDOWN... wait 7 days or more till you see the oem unlock...

---------- Post added at 01:09 PM ---------- Previous post was at 01:03 PM ----------

You are not reading the comment section especially the tutorial instruction.. after rooting usually most of the case, oem unlock does not appear.. you have to wait 7 days or more till u see it.. So it's better to avoid installing app that requires reboot.
[Samsung Galaxy S9+ Guides, News, & Discussion] gaww:
Unbelievable after all this time beginning in April that so many people don't have it right.

On 3 above, no problem but unnecessary to wait another 7 days if you do it right. In this thread and a few others it is explained - search and read.

Number 4 is wrong - period.

After unlocking there is no reason to go to development options except to screw things up. This is why several developers eliminate it in their roms.

You should ONLY go to download mode to check on locks and also prenormal. During the waiting period you can use it and turn it off. Only resetting or ODINing stock ROMs will trigger the 7 days.
[Samsung Galaxy S9+ Guides, News, & Discussion] jonathan_moreno91:
Wow I have notice you before you always bash someone's post as if you are Dr. KETAN. Dude you have no right to say I am wrong on number 4, it is like saying DR. Ketan is wrong. He said in the last instruction that in settings check in developer option if you did not see the oem unlock option then it is not safe to reboot. Apps like viper fx, from magisk module, it requires reboot to activate.. so if you did that even though you did not see the oem unlock in developer option right after rooting then you are screwed "ONLY OFFFICIAL BINARIES ETC"

Also number 3, new phone 1st time oem unlock appears. If you turned it on, it is a must to wait 7 days coz after factory settign you cannot flash anything yet

You said since april right? Well lucky for you if you did not experience official binaries if you restart after root. Because as of August security patch bootloader xxu2, oem unlock does not appear after root.
[Samsung Galaxy S9+ Guides, News, & Discussion] dr.ketan:
Let me make it clear here

- I said in this thread to not to restart device if you don't have OEM unlock option - THIS IS CORRECT

Because person who following this guide are coming from stock ROM

Some developers saying you don't need to worry about missing option of OEM unlock is because

1.Either their ROM have made is hidden to prevent accidental off

2.They have patched kernel to remove this fully to prevent official binary error

But If someone with above two condition might using already rooted ROM and why they need to follow my guide?

So we can't ask users to reboot to download mode and check for prenormal as if he/she attempt to do this, it will end with official binary error when reboot to system after testing it in case it have prenormal condition
[Samsung Galaxy S9+ Guides, News, & Discussion] dr.ketan:
I am planning to add one more security to patch the kernel to remove OEM stuff fully.
[Samsung Galaxy S9+ Guides, News, & Discussion] jonathan_moreno91:
Exactly sir.. we are here coz some of us here are using s9+ stock rom xxu2 august patch above. That guy is the reason why some still dont get it, they still reboot after rooting. Thus ended up getting official binaries.. I think 3 days ago was my 7th day after rooting coz Oem appeared. As of now, no more only official binaries allowed no matter how many times restarted /shutdown no problem at all. Thanks
[Samsung Galaxy S9+ Guides, News, & Discussion] dr.ketan:
This OEM option managed remotely with three stuff

1.Rlc apk - That tool provided here can remove it

2.With vaultkeeper value - That this tool fix but again, flashing vendor reset original value

3.CSC - As samsung have introduced encrypted csc, it's bit difficult to edit specific changes because for that we need first decrypted CSC

Users who are getting this issue because of this tool can't block this third way.

What we can do next

I believe, if we patch the kernel while flashing root, we can prevent OEM stuff completely. That may leand to no OEM option at all but still device should be safe to reboot.
[Samsung Galaxy S9+ Guides, News, & Discussion] dr.ketan:
Guys do one favor

If you have stock ROM for S9+ then please extract boot.img.lz4 file and post here so I can try to edit tool and that may patch kernel to remove this OEM stuff fully.

After this there shouldn't anymore official binary error there.
[Samsung Galaxy S9+ Guides, News, & Discussion] LysolPionex:
My oem toggle finally appeared!

Can I apply the September update and then root? Or would I have to wait again?

Or can I apply the update after I root?
[Samsung Galaxy S9+ Guides, News, & Discussion] Zer0Sense:
Tried to root again. Did everything with the instruction and booted with root rights. Oem was not there and I entered a google account credits and put a phone onto the shelf to wait for I week so I can finally start using it.

Yet it freezed on uptime 30 mins and I have to start 2 week circle yet again. Week is a really long time for a phone to be up. You nearly don't want to use it so nothing goes wrong and causes device to restart. It probably did some google play updates.

Considering reseting device each time and all of this mess every time you decide to upgrade to newer firmwares it's VERY questionable whether it makes sense to buy or own theese newer Samsung devices.
[Samsung Galaxy S9+ Guides, News, & Discussion] joe535:
Hopefully someone from Samsung will also read all those and see that they loose customers this way...
[Samsung Galaxy S9+ Guides, News, & Discussion] gaww:
They could care less - they never supported unlocking.

---------- Post added at 03:23 PM ---------- Previous post was at 03:19 PM ----------

If you can, list step by step what you have done - you should not be having all this trouble.

NOTE - the order on the OP is a bit off. Do NOT OEM unlock until you are ready to ODIN TWRP and everything else is ready. You want to go straight from there to TWRP.
[Samsung Galaxy S9+ Guides, News, & Discussion] Zer0Sense:
Oem unlock appears after a week as "on" in developer options

I flash twrp and boot into recovery set it as read only and format

Reboot into recovery and flash dm verity

Reboot into recovery and flash oem unlock, choose multitool ... oem unlock ... magisk, not patching kernel after installation is complete I boot into system

Reboot into android inserting google or samsung account magisk is installed I have root rights. Prenormal mode so no oem unlock in developer options. Need to keep device up a week so I can restart it.

if device fails or freezes I eventually return to official binary.

The whole rooting process is 2 week process where no single mistake is allowed.
[Samsung Galaxy S9+ Guides, News, & Discussion] mrwan74:
i have linked the boot image file from stock rom G965FXXU2BRGA_G965FOXM2BRG8_ILO in my profile because im unable to post links due to restricstions here on xda

"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"

the link starts with "filebin"

im still having trouble rooting after the august 1 security patch , my phone freezes.

after flashing twrp 3.2.3.0 ,wiping storage,flashing no verity opt encrypt 6.0-star ,flashing RMM State bypass Mesa v2 , and finally magisk .after booting the phone just freezes up

i have tried everything every 7 days with no success , different version of magisk ( latest one ,then going down a version) , supersu

i am thinking the problem is with the no verity encrypt ,maybe the update broke it somehow
[Samsung Galaxy S9+ Guides, News, & Discussion] Zer0Sense:
Both from Emirates firmwares:

G965FXXU2BRGA:

https://www.upload.ee/files/9041054/boot.img.lz4.html

G965FXXU2BRI3 (Galaxy S9+ SM-G965F with product code XSG from United Arab Emirates. This firmware has version number PDA G965FXXU2BRI3 and CSC G965FOXM2BRHA. The operating system of this firmware is Android 8.0.0 , with build date Mon, 03 Sep 2018 09:54:45 +0000. Security patch date is 2018-09-01, with changelist 14049503)

https://www.upload.ee/files/9041971/boot.img.lz4.html
[Samsung Galaxy S9+ Guides, News, & Discussion] Zer0Sense:
No mean to hurry but is there any ETA ?
[Samsung Galaxy S9+ Guides, News, & Discussion] jonathan_moreno91:
You sir really need to get off this thread you are making people confuse. Not long ago you said it is okay to restart or turn off after rooting which is wrong. Now you are claiming that Dr. Ketan order is wrong LOL... you are wrong!! Even if you are ready even if you download all etc.. if you did not oem unlock you cant do anything!!!! s9+ out of the box don't have oem option after 7 days it appears turn it on and wait another 7 days for it to re appear before you can flash twrp through odin.

---------- Post added 10th October 2018 at 12:18 AM ---------- Previous post was 9th October 2018 at 11:54 PM ----------

Bro you sure that flash dm verity andfash oem unlock is from this tutorial? Maybe you got it from other tutorial..

Coz in this tutorial there is only 1 zip to flash and that is N9_S9_Root_for_OEM_issue_devices_V3.zip. in that file I applied oem fix then magisk then reboot to system.. that's it nothing else.. try to discard everything you downloaded from other tutorial.. I am too using bootloader with august patch.

Again bro to make it simple:

1. Flash N9_S9_Root_for_OEM_issue_devices_V3.zip

2. Apply oem fix

3. Skip kernel

4. Select magisk

5. Reboot and done wait for 7 days no restart no shutdown.

---------- Post added at 12:33 AM ---------- Previous post was at 12:18 AM ----------

Bro why do you want to upgrade to september? Just stick to august. Right now I don't have any problem at all... be sure to discard everything from other tutorial coz I notice some people are flashing dm verity flashing rmm and flashing oem unlock.. You only need 1 file to flash N9_S9_Root_for_OEM_issue_devices_V3.zip.. thats it.

---------- Post added at 12:37 AM ---------- Previous post was at 12:33 AM ----------

Same with zer0sense bro, you are flashing other files... maybe thats the reason.. you dont need all of that rmm, oem, or verity.. you only needed to flash N9_S9_Root_for_OEM_issue_devices_V3.zip.
[Samsung Galaxy S9+ Guides, News, & Discussion] dr.ketan:
I uploaded V4 now which have option to flash RMM stat patched kernel for S9+ user

Any S9+ users want to try this option, Download V4 (Link in OP) From TWRP flash V4 - select OEM patch + Select Patched kernel for S9+ + select magisk (must else device won't boot)

Here some confusion there as there may not be OEM available because of kernel patch but should be safe to reboot. (No guarantee!)
[Samsung Galaxy S9+ Guides, News, & Discussion] gaww:
Many are using RMM patching with no OEM available without issues - including this S9+ (prenormal is the biggest pain..), so I would give it a try.
[Samsung Galaxy S9+ Guides, News, & Discussion] mrwan74:
Updated files

hi dr.ketan ,thanks for your work we really do appreciate it.

i'll try it out next week when im out of the 7 day OEM jail period,i have a couple of questions

did you update the files in your zip file? e.g

RMM state bypass by mesa -- there's a version 2 of the file .

found here on the forums https://xdaforums.com/samsung-a-series-2017/how-to/how-to-root-january-security-patch-sm-t3739225/post75360965#post75360965 . i spoke with him personally on facebook,he's called Mesa Labs

no-verity-opt-encrypt-6.0-star -- this is the latest according to my research

Stable Magisk Version: v17.1 - v17.2 is currently beta --

topjohnwu added a couple of important stuff

a script "

Enable KEEPVERITY when the device is using system_root_image

" and

Script "

Add hex patch to remove Samsung defex in new Oreo kernels

"

im having trouble with my device rooting,after the first boot my device freezes up and wont respond.

it seems that samsung patched some of the vulnerabilities used by the bypasses to achieve root,

after the august update. the device is unable to sustain the NO Verity OPT encrypt , the device seems to re-encrypt it self after the first boot

should i try running the magisk DM verity enabled echo command in the TWRP terminal before flashing the file?

echo KEEPVERITY=true>>/data/.magisk

its documented in Magisk Troubleshoot Wiki (huge thanks to [MENTION=4667597]Didgeridoohan[/MENTION]!)

https://www.didgeridoohan.com/magisk/HomePage

last question ,what is the kernel patch you added.what does it do exactly ? is it related to this problem

sorry for the confusion im not trying to tell you how to do anything you are great ,im just trying to contribute to the best of my ability

thanks alot again man

Galaxy S9+ SM-G965F

This firmware version number PDA G965FXXU2BRGA and CSC G965FOXM2BRG8. The operating system of this firmware is Android 8.0.0 , with build date Thu, 26 Jul 2018 02:10:34 +0000. Security patch date is 2018-08-01, with changelist 14049503.

https://filebin.net/n9ibrff7tvvi3lkw

---------- Post added at 06:49 PM ---------- Previous post was at 06:43 PM ----------

hi man thanks for your reply,i wasn't very clear last time i'll try to explain as best of i can this time.

dr.ketan script consists of the files i used to flash manually.

no verity opt encrypt remove the encryption of the device

RMM State bypass by mesa - this here bypass the RMM/OEM lock after reboot

rooting methods : SuperSU or Magisk file

i tried those after trying the previous version of dr.ketan's scripts and failed to boot
[Samsung Galaxy S9+ Guides, News, & Discussion] mrwan74:
[MENTION=4899305]ashyx[/MENTION] said that i need a patched custom kernel to bypass the encryption and dm-verity, no_verity_opt_encrypt won't work on Oreo.

is it possible that he's wrong?

his profile

https://xdaforums.com/member.php?u=4899305

posted on Magisk General Support / Discussion by topjohnwu https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post77843692#post77843692
[Samsung Galaxy S9+ Guides, News, & Discussion] kusumuck:
I just tried V4 last night. Everything worked. I used all of the options in the tool kit: OEM, RMM, and Magisk.

A few things though:

1.) I have root.

2.) The OEM setting is visible but currently in the "off" position. I can toggle it, but it wants to do a factory reset so I left if off.

3.) The phone was running really slow for about 6 hours. I downloaded 'System Monitor' and resource usage was low, but still running slow. About 12 hours later, it is running faster, but still doesn't seem like it is at 100% all of the time.

Is this how it should be? I can deal with the reduced speed for a week, if after that time I can I restart the phone and maintain my root status. This is my 5th attempt at root.
[Samsung Galaxy S9+ Guides, News, & Discussion] gaww:
If you toggle it, let it start into factory reset, but then go straight into download mode before it completes and see if locks are off an no prenormal. This is where TWRP would normally be ODIN'd but I am guessing you have it so just reboot.
[Samsung Galaxy S9+ Guides, News, & Discussion] dr.ketan:
Check for OEM toggle, if there then nothing to worry
[Samsung Galaxy S9+ Guides, News, & Discussion] mrwan74:
hey [MENTION=3931450]dr.ketan[/MENTION] , have you read my previous two posts above ? would appreciate any help :confused:
[Samsung Galaxy S9+ Guides, News, & Discussion] ashyx:
Since Oreo Dm-verity flags are no longer in the Ramdisk. The flags are dtb based.

If the dtb isnt patched or dm-verity disabled in the kernel source then rooting will likely cause a boot loop.

Same goes for disabling forced encryption, the flags are no longer in the Ramdisk fstab, but usually located in the Vendor partition.

Magisk attempts to hex patch the kernel, but when Samsung update the firmware the hex patch offsets change and patching fails.
[Samsung Galaxy S9+ Guides, News, & Discussion] mrwan74:
[MENTION=4899305]ashyx[/MENTION]

wow man you are a genius kudos to you!! I’m eternally grateful to you. thanks!! :good::o:o

a completely unrelated question to the matter at hand

Im currently learning computer science at college to get bachelor's degree,first year here .

how can i become like you guys ,to understand what you understand. is there something specific i should learn to understand these matters? these stuff are complicated and not covered in computer science

any tips would be helpful.and thank you again I’m so grateful for your help
[Samsung Galaxy S9+ Guides, News, & Discussion] Kellykell559:
Kellyscharton@gmail.com