Develop Bugs

Easier Way To OEM Unlock Via Fastboot?

This is potentially a MUCH easier way to OEM Unlock the S9.
I bought my S9 and waited the 7 days,did the unlock and accidentally let it wipe and reboot, so I had to wait the 7 days again. I tried the date manipulation trick and it never worked. Flashing a new bootloader wouldn't work.
Then I saw that Fastboot had an OEM unlock command, so I tried that, but it said it failed.
But then today, the 7 days were up again, and oem unlock finally appeared in my dev options again, and behold, OEM Unlock was already true!
I'm going to try flashing twrp and rooting later today, but I thought someone who may not want to wait 7 days could try this and see if even though it "fails" the bootloader may unlock anyway!
Assuming you have Fastboot and the proper USB drivers etc. Also assuming the device is not modified from its factory state etc.
Steps to attempt:
1. Turn off the phone.
2. Hold vol up, bixby, and power (to go into Fastboot)
3. From a command prompt enter: fastboot oem unlock
4. It will say it failed.
5. Attempt flashing the recovery of your choice via: fastboot flash recovery <recovery file>
Let people know in the comments whether this works!

Did this method work for your....

LysolPionex said:
This is potentially a MUCH easier way to OEM Unlock the S9.
I bought my S9 and waited the 7 days,did the unlock and accidentally let it wipe and reboot, so I had to wait the 7 days again. I tried the date manipulation trick and it never worked. Flashing a new bootloader wouldn't work.
Then I saw that Fastboot had an OEM unlock command, so I tried that, but it said it failed.
But then today, the 7 days were up again, and oem unlock finally appeared in my dev options again, and behold, OEM Unlock was already true!
I'm going to try flashing twrp and rooting later today, but I thought someone who may not want to wait 7 days could try this and see if even though it "fails" the bootloader may unlock anyway!
Assuming you have Fastboot and the proper USB drivers etc. Also assuming the device is not modified from its factory state etc.
Steps to attempt:
1. Turn off the phone.
2. Hold vol up, bixby, and power (to go into Fastboot)
3. From a command prompt enter: fastboot oem unlock
4. It will say it failed.
5. Attempt flashing the recovery of your choice via: fastboot flash recovery <recovery file>
Let people know in the comments whether this works!
Click to expand...
Click to collapse
which variant you use?

angel8502 said:
which variant you use?
Click to expand...
Click to collapse
SM-960F/DS.
But I just got the "Only Official released binaries are allowed to be flashed" message, so I might get to try this method again myself, lol.

How exactly are you able to run fastboot commands when this is a samsung?? Odin is fastboot replacement and there is no way to make it recognize Fastboot. Please enlighten

beatbreakee said:
How exactly are you able to run fastboot commands when this is a samsung?? Odin is fastboot replacement and there is no way to make it recognize Fastboot. Please enlighten
Click to expand...
Click to collapse
Well, I just got the lock screen freeze and had to force a reboot, and when I did, I couldn't flash anything recovery or rom via Odin, so I tried using fastboot again to oem unlock, and it fastboot didn't even see it connected, so what you're saying makes sense.
Is it possible I used ADB instead? Does ADB have an oem unlock command as well? Or maybe the factory reset after the first toggle didn't set OEM lock like it normally does?
I'm not sure what I did, but OEM unlock was definitely toggled on once the option appeared. I'm going to play around with it a bit more.
On a side note, when I go into download mode, it still says OEM LOCK: off, but still won't let me flash unofficial bins. Would the RMM Prenormal have something to do with that?

LysolPionex said:
Well, I just got the lock screen freeze and had to force a reboot, and when I did, I couldn't flash anything recovery or rom via Odin, so I tried using fastboot again to oem unlock, and it fastboot didn't even see it connected, so what you're saying makes sense.
Is it possible I used ADB instead? Does ADB have an oem unlock command as well? Or maybe the factory reset after the first toggle didn't set OEM lock like it normally does?
I'm not sure what I did, but OEM unlock was definitely toggled on once the option appeared. I'm going to play around with it a bit more.
On a side note, when I go into download mode, it still says OEM LOCK: off, but still won't let me flash unofficial bins. Would the RMM Prenormal have something to do with that?
Click to expand...
Click to collapse
take a pic n post it of download mode

elliwigy said:
take a pic n post it of download mode
Click to expand...
Click to collapse
Just a close up, nothing else relevant in the screen.

LysolPionex said:
Just a close up, nothing else relevant in the screen.
Click to expand...
Click to collapse
most likely is the rmm state

elliwigy said:
most likely is the rmm state
Click to expand...
Click to collapse
That makes sense with what I found last night in another thread. I think I used an old version of the rmm Mesa bypass too, so we'll see what happens. In another 5 days...

This will not work. The large majority of Samsung devices (exceptions being the Galaxy Nexus and Nexus S) don't support Fastboot and there isn't any way to unlock the device using ADB.
The reason why your "OEM unlock" switch was already toggled was because, even after the data wipe, it doesn't reset. Your device stays OEM unlocked, but isn't RMM unlocked until the 7 day timer has passed -- so your bootloader stays locked until the RMM timer passes.
Fun fact: you can flash the "combination" firmware to your device and immediately enable OEM unlock, but you'll have to flash the normal firmware back and let the RMM lock timer pass still. You won't have to wipe your device that way.

tomiga said:
This will not work. The large majority of Samsung devices (exceptions being the Galaxy Nexus and Nexus S) don't support Fastboot and there isn't any way to unlock the device using ADB.
The reason why your "OEM unlock" switch was already toggled was because, even after the data wipe, it doesn't reset. Your device stays OEM unlocked, but isn't RMM unlocked until the 7 day timer has passed -- so your bootloader stays locked until the RMM timer passes.
Fun fact: you can flash the "combination" firmware to your device and immediately enable OEM unlock, but you'll have to flash the normal firmware back and let the RMM lock timer pass still. You won't have to wipe your device that way.
Click to expand...
Click to collapse
This is the first time I've seen a clear explanation off all of this. Thank you for that!

What do I need to flash a combination firmware? Anda what is this combination?
Ps: sorry my english I am Brasilian. He...he..

Regikitten said:
What do I need to flash a combination firmware? Anda what is this combination?
Ps: sorry my english I am Brasilian. He...he..
Click to expand...
Click to collapse
I'm not familiar with it, but I assume he's talking about this: https://forum.xda-developers.com/ga...ollection-combination-rom-samsung-s9-t3782737
There are a couple other threads about it in the S9 forum.

tomiga said:
This will not work. The large majority of Samsung devices (exceptions being the Galaxy Nexus and Nexus S) don't support Fastboot and there isn't any way to unlock the device using ADB.
The reason why your "OEM unlock" switch was already toggled was because, even after the data wipe, it doesn't reset. Your device stays OEM unlocked, but isn't RMM unlocked until the 7 day timer has passed -- so your bootloader stays locked until the RMM timer passes.
Fun fact: you can flash the "combination" firmware to your device and immediately enable OEM unlock, but you'll have to flash the normal firmware back and let the RMM lock timer pass still. You won't have to wipe your device that way.
Click to expand...
Click to collapse
So I kept the device on for 155 hours, and the oem option appeared again, so I booted into download mode: RMM prenormal (oem lock off still). When I started it back up, the oem option was gone again (still is). Does the 7 day period have to be without turning the device off?

LysolPionex said:
So I kept the device on for 155 hours, and the oem option appeared again, so I booted into download mode: RMM prenormal (oem lock off still). When I started it back up, the oem option was gone again (still is). Does the 7 day period have to be without turning the device off?
Click to expand...
Click to collapse
to my understanding yes lol.. theres many threads with specific instructions.. if u miss one lil step u start over waiting period and all

elliwigy said:
to my understanding yes lol.. theres many threads with specific instructions.. if u miss one lil step u start over waiting period and all
Click to expand...
Click to collapse
Lol, so I'm at 182 hours uptime, but the OEM option isn't in dev options...do I risk going to download mode to see RMM status?

tomiga said:
This will not work. The large majority of Samsung devices (exceptions being the Galaxy Nexus and Nexus S) don't support Fastboot and there isn't any way to unlock the device using ADB.
The reason why your "OEM unlock" switch was already toggled was because, even after the data wipe, it doesn't reset. Your device stays OEM unlocked, but isn't RMM unlocked until the 7 day timer has passed -- so your bootloader stays locked until the RMM timer passes.
Fun fact: you can flash the "combination" firmware to your device and immediately enable OEM unlock, but you'll have to flash the normal firmware back and let the RMM lock timer pass still. You won't have to wipe your device that way.
Click to expand...
Click to collapse
The above information was clear and helpful, but one query with respect to my case.
I have an Samsung S7 edge (SM-G935FD), i have flashed custom ROM successfully, but due to some reason I need to go back to my Stock ROM and I was able to do successfully.
The question is, seems still my OEM is unlocked even after stock ROM, will the OEM lock will happen automatically after 7 days, or is there any way to lock back manually.
Thanks in Advance

Samsung doesn´t have fastboot , it uses some kind of own mode only accessible via Odin. I prefer this way.
Also you have Prenormal state , this is some kind of security blocking by Knox, happened to me and had to wait 7 days.
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
askader said:
The above information was clear and helpful, but one query with respect to my case.
I have an Samsung S7 edge (SM-G935FD), i have flashed custom ROM successfully, but due to some reason I need to go back to my Stock ROM and I was able to do successfully.
The question is, seems still my OEM is unlocked even after stock ROM, will the OEM lock will happen automatically after 7 days, or is there any way to lock back manually.
Thanks in Advance
Click to expand...
Click to collapse
Will appear within 5-7 days since you flashed stock ROM.

ZoiraP said:
Samsung doesn´t have fastboot , it uses some kind of own mode only accessible via Odin. I prefer this way.
Also you have Prenormal state , this is some kind of security blocking by Knox, happened to me and had to wait 7 days.
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
Will appear within 5-7 days since you flashed stock ROM.
Click to expand...
Click to collapse
Did it solved after 7 days?

Can't install TWRP due to KG status Prenormal

So as the title says, I am on pie SF4 version, in my download mode it says my RMM status: Prenormal
and KG status: Prenormal. and so when i try to flash anything it says 'only official binaries can be flashed'. How do i solve this? Please I desperately need help. I just don't like using my device without any root/magisk and without twrp i'm stuck.

caspianprince said:
So as the title says, I am on pie SF4 version, in my download mode it says my RMM status: Prenormal
and KG status: Prenormal. and so when i try to flash anything it says 'only official binaries can be flashed'. How do i solve this? Please I desperately need help. I just don't like using my device without any root/magisk and without twrp i'm stuck.
Click to expand...
Click to collapse
You need use smart switch then use this link to root and twrp --> https://forum.xda-developers.com/showpost.php?p=79378123&postcount=142

N1NJATH3ORY said:
You need use smart switch then use this link to root and twrp --> https://forum.xda-developers.com/showpost.php?p=79378123&postcount=142
Click to expand...
Click to collapse
What will i do with smart switch? Using smart switch will reset the KG status?

Did you finish setting up the tablet after you factory reset? During setup KG Status will stay prenormal.

last1youlove said:
Did you finish setting up the tablet after you factory reset? During setup KG Status will stay prenormal.
Click to expand...
Click to collapse
After setting up, my KG state went to 'Checking' but my RMM is still 'Prenormal'. How do i reset that? I can't flash with RMM 'prenormal' right?

No you can't
RMM should go to normal after 7 days. You're probably just gonna have to wait.
Do you have the LTE version?

last1youlove said:
No you can't
RMM should go to normal after 7 days. You're probably just gonna have to wait.
Do you have the LTE version?
Click to expand...
Click to collapse
No the Wifi version T830. So it's okay if KG status is 'Checking'? now i just need to wait for 7 days?

caspianprince said:
No the Wifi version T830. So it's okay if KG status is 'Checking'? now i just need to wait for 7 days?
Click to expand...
Click to collapse
Huh that's strange I have a T830 as well but no RMM State.
After setting up Did you connect to the internet, enable developer options and make sure OEM Unlocking is visible and enabled?
If it doesn't show at first leave and reenter developer options a few times if that doesn't work try restarting. And yes KG Status is supposed to be Checking

last1youlove said:
Huh that's strange I have a T830 as well but no RMM State.
After setting up Did you connect to the internet and enable developer options and make sure OEM Unlocking is visible and enabled?
If it doesn't show at first leave and reenter developer options a few times if that doesn't work try restarting. And yes KG Status is supposed to be Checking
Click to expand...
Click to collapse
I have OEM unlocking enabled but I also have RMM 'prenormal'. Normally, as far as i know from reading the forums, in oreo if RMM was 'prenormal' then OEM unlock option didn't even appear in developer settings, but in pie even if RMM is 'prenormal' OEM unlock still appears but still you can't flash anything unless it returns to 'Normal'.

Thats really strange For me I have no RMM State however OEM Unlocking didn't appear for me until I connected to the internet and restarted. Sorry but I got no idea at this point. You may have to just wait the week out.

S9 SM-G960F Root Issue On android pie one UI

Hello, I tried following the tutorial that seems to work for everyone
(
) LINK to tutorial.
But my basic problem is that when i try to flash twrp it says " only official binaries can be flashed"
It happened after i enabled OEM unlocking and the phone restarted then i went to download mode before allowing it to restart, thats where it gave me that issue., I want to root my phone.
I am sharing current state of my phone. If somebody can guide me i would be thankful.

ibrahimqureshae said:
Hello, I tried following the tutorial that seems to work for everyone
(
) LINK to tutorial.
But my basic problem is that when i try to flash twrp it says " only official binaries can be flashed"
It happened after i enabled OEM unlocking and the phone restarted then i went to download mode before allowing it to restart, thats where it gave me that issue.
I am sharing current state of my phone. If somebody can guide me i would be thankful.
Click to expand...
Click to collapse
Leave your phone the way it is with stock
Sent from my SM-J327P using Tapatalk

PoochyX said:
Leave your phone the way it is with stock
Click to expand...
Click to collapse
Ok... But i want to root it? How will i be able to do that? Any solutions to overcome the problem while flashing twrp?

ibrahimqureshae said:
Hello, I tried following the tutorial that seems to work for everyone
But my basic problem is that when i try to flash twrp it says " only official binaries can be flashed"
It happened after i enabled OEM unlocking and the phone restarted then i went to download mode before allowing it to restart, thats where it gave me that issue., I want to root my phone.
I am sharing current state of my phone. If somebody can guide me i would be thankful.
Click to expand...
Click to collapse
your bootloader state is prenormal, still locked. Unlock it and you should be good. There are some files you can flash it keep the prenormal at bay once you get it removed
PoochyX said:
Leave your phone the way it is with stock
Sent from my SM-J327P using Tapatalk
Click to expand...
Click to collapse
orrrrrrrrrrr, he can do whatever he wants with it..... smmfh....
---------- Post added at 09:20 AM ---------- Previous post was at 09:14 AM ----------
ibrahimqureshae said:
Ok... But i want to root it? How will i be able to do that? Any solutions to overcome the problem while flashing twrp?
Click to expand...
Click to collapse
bootloader is still locked. the "prenormal" in download mode is the thing thats preventing you.

youdoofus said:
your bootloader state is prenormal, still locked. Unlock it and you should be good. There are some files you can flash it keep the prenormal at bay once you get it removed
orrrrrrrrrrr, he can do whatever he wants with it..... smmfh....
---------- Post added at 09:20 AM ---------- Previous post was at 09:14 AM ----------
bootloader is still locked. the "prenormal" in download mode is the thing thats preventing you.
Click to expand...
Click to collapse
And how would i do that?

ibrahimqureshae said:
And how would i do that?
Click to expand...
Click to collapse
the prevailing theory is that you have to leave the phone on for 168 hours, after a fresh install, enable dev options, then uncheck the box. The FRP lock will re-enable it self even if you have the OEM unlock toggle switched to off. Reflash your stock firmware in Odin, set the phone up for as much as youd need in 168 hours worth of usage, then do the oem unlock. Then immediately boot to DL mode and flash twrp

youdoofus said:
the prevailing theory is that you have to leave the phone on for 168 hours, after a fresh install, enable dev options, then uncheck the box. The FRP lock will re-enable it self even if you have the OEM unlock toggle switched to off. Reflash your stock firmware in Odin, set the phone up for as much as youd need in 168 hours worth of usage, then do the oem unlock. Then immediately boot to DL mode and flash twrp
Click to expand...
Click to collapse
ok now i flashed stock firmware on my phone and it has oem unlock toggled on and it says bootloader is already unlocked, i tried flashing twrp and it still gives me the same error! i have no idea what to do now!

ibrahimqureshae said:
ok now i flashed stock firmware on my phone and it has oem unlock toggled on and it says bootloader is already unlocked, i tried flashing twrp and it still gives me the same error! i have no idea what to do now!
Click to expand...
Click to collapse
there is also another zip file to flash when dealing with the oem unlock to make sure it doesnt lock again. ill have to look for it, but i came across it originally in the Galaxy A8 forum. You might also have to wait 168 hours and then try the toggle again. This 168 hour thing can be a real bugger.

youdoofus said:
there is also another zip file to flash when dealing with the oem unlock to make sure it doesnt lock again. ill have to look for it, but i came across it originally in the Galaxy A8 forum. You might also have to wait 168 hours and then try the toggle again. This 168 hour thing can be a real bugger.
Click to expand...
Click to collapse
No, the thing is that my OEM UNLOCK is toggled On, which means my bootloader is unlocked.
That should mean that my rmm state should not be prenormal,
But its not like that.
Despite flashing new rom and having oem unlock already toggled on which means unlocking the bootloader,
I am still unable to flash twrp.
What else can i do? Any solution ?

ibrahimqureshae said:
No, the thing is that my OEM UNLOCK is toggled On, which means my bootloader is unlocked.
That should mean that my rmm state should not be prenormal,
But its not like that.
Despite flashing new rom and having oem unlock already toggled on which means unlocking the bootloader,
I am still unable to flash twrp.
What else can i do? Any solution ?
Click to expand...
Click to collapse
i know the toggle is on, but that doesnt ensure that your bootloader is unlocked. If your rmm state is anything other than prenormal, then its definitely not unlocked.
rmm prenormal has been a bane of the samsung xda corner of the internet for a while now, read this
im betting its the 168 hour issue. dont reboot your phone for 168 hours and toggle it off then back on

youdoofus said:
i know the toggle is on, but that doesnt ensure that your bootloader is unlocked. If your rmm state is anything other than prenormal, then its definitely not unlocked.
rmm prenormal has been a bane of the samsung xda corner of the internet for a while now, read this
im betting its the 168 hour issue. dont reboot your phone for 168 hours and toggle it off then back on
Click to expand...
Click to collapse
are you sure? if i turn it off and then on it would work?

ibrahimqureshae said:
are you sure? if i turn it off and then on it would work?
Click to expand...
Click to collapse
no, im not sure. but the worst thing that could happen is the phone making you wait another 168 hours if you toggle it once and it makes you wait for the second toggle again.

youdoofus said:
no, im not sure. but the worst thing that could happen is the phone making you wait another 168 hours if you toggle it once and it makes you wait for the second toggle again.
Click to expand...
Click to collapse
how about i just try to go into download mode after 168 hours and see if the rmm state isnt pre normal anymore

ibrahimqureshae said:
how about i just try to go into download mode after 168 hours and see if the rmm state isnt pre normal anymore
Click to expand...
Click to collapse
only issue that could cause, if it was even going to cause an issue, is reset the time since previous reboot, in which case all that would happen is having to wait 168 hours again if that doesnt work

оin raz o umenya proizasla takaya problema na samsunge s8 ya nasol ofisialniy rom postavil i ya moq zdelat polniy root .nu saas u menya s9 samiy posledniy obnovleniya ni moqu zdelat root kg status prenormal piset kak mne delat
Translation: Once about the skill there was such a problem on the samsung S8. I put the office rum on and I could make a root. I have the latest update I can not make a root. kg status prenormal write how do i do?

nikoh8756 said:
оin raz o umenya proizasla takaya problema na samsunge s8 ya nasol ofisialniy rom postavil i ya moq zdelat polniy root .nu saas u menya s9 samiy posledniy obnovleniya ni moqu zdelat root kg status prenormal piset kak mne delat
Translation: Once about the skill there was such a problem on the samsung S8. I put the office rum on and I could make a root. I have the latest update I can not make a root. kg status prenormal write how do i do?
Click to expand...
Click to collapse
1. Welcome to XDA. We hope you enjoy your stay.
2. Please post in English as per XDA Rule #4.
3. Thank you for your cooperation.
-Regards: Badger50

[help me please] a505gn missing oem unlock

So dang first of all this situation sucks I have the phone(A505GN) now for over a year.. and I'm having a hard time unlocking the boot loader so here's the method that I tried using.
1. I tried the method where you change date and update etc didn't work
2. Tried waiting for 168 hours didn't work
It's getting hopeless I can't flash anything except official rom dang it I hope someone can save me from this dreadful situation I freaking won't get any other samsung phone
I attached a picture of my download mode I can turn the frp lock off but can't turn off oem lock so this sucks HELP me please

@Lynjun002
IIRC an Android user can not unlock the bootloader without OEM unlocking, because without this process the device will not accept the bootloader unlocking command.

jwoegerbauer said:
@Lynjun002
IIRC an Android user can not unlock the bootloader without OEM unlocking, because without this process the device will not accept the bootloader unlocking command.
Click to expand...
Click to collapse
Yes i fully understand dang so i think this is it im helpless

Lynjun002 said:
So dang first of all this situation sucks I have the phone(A505GN) now for over a year.. and I'm having a hard time unlocking the boot loader so here's the method that I tried using.
1. I tried the method where you change date and update etc didn't work
2. Tried waiting for 168 hours didn't work
It's getting hopeless I can't flash anything except official rom dang it I hope someone can save me from this dreadful situation I freaking won't get any other samsung phone
I attached a picture of my download mode I can turn the frp lock off but can't turn off oem lock so this sucks HELP me please
Click to expand...
Click to collapse
Do you have rmm status prenormal?

Alijjasghar said:
Do you have rmm status prenormal?
Click to expand...
Click to collapse
my download mode doesnt say anything about RMM i only have the line that says KG STATE : NORMAL

So there is no problem with rmm lock
And your phone is not the US varient
Actually you need to use your phone for 168 hours with internet connection on and no reboots. Did I do the same?

Alijjasghar said:
So there is no problem with rmm lock
And your phone is not the US varient
Actually you need to use your phone for 168 hours with internet connection on and no reboots. Did I do the same?
Click to expand...
Click to collapse
Right it is not US variant do i need to do factory reset or can i reboot phone and start waiting for 168 hours without turning of data?

Lynjun002 said:
Right it is not US variant do i need to do factory reset or can i reboot phone and start waiting for 168 hours without turning of data?
Click to expand...
Click to collapse
No need to factory reset. Reboot and start 168 hours with data ON and see if it helps. You can see your uptime somewhere in About phone. When it reaches 168 hours then check for updates and see if OEM lock appears

Alijjasghar said:
No need to factory reset. Reboot and start 168 hours with data ON and see if it helps. You can see your uptime somewhere in About phone. When it reaches 168 hours then check for updates and see if OEM lock appears
Click to expand...
Click to collapse
Ok bro im at 40hrs now

Lynjun002 said:
Ok bro im at 40hrs now
Click to expand...
Click to collapse
May I ask what this time trick your trying to make OEM show up? I'm having the same issue can you break down the time trick and what I do after? Please

Didnt work till now i havent unlock my phone

mattshann34 said:
May I ask what this time trick your trying to make OEM show up? I'm having the same issue can you break down the time trick and what I do after? Please
Click to expand...
Click to collapse
i failed and gave up man it didnt work

[Q] RMM State check/bypass

Hi i've got a question. I recently purchased the A5 2017 (A520F) secondhand and i want to put a custom rom on it. I have unlocked and flashed tons of phones and tablets in the past so i'm far from a newbee.
My phone has "Bootloader OEM unlock" in dev options.
When i go into odin download mode (vol-, home+power) i dont get any message regarding "RMM state: Prenormal". FRP is unlocked.
Does this mean i'm all set to flash anything without the RMM.zip?
I'm having the latest security patch Jan2020 and Oreo bootloader. Knox is 0x0. Are there any other ways to check RMM state?

JMailuhu said:
Hi i've got a question. I recently purchased the A5 2017 (A520F) secondhand and i want to put a custom rom on it. I have unlocked and flashed tons of phones and tablets in the past so i'm far from a newbee.
My phone has "Bootloader OEM unlock" in dev options.
When i go into odin download mode (vol-, home+power) i dont get any message regarding "RMM state: Prenormal". FRP is unlocked.
Does this mean i'm all set to flash anything without the RMM.zip?
I'm having the latest security patch Jan2020 and Oreo bootloader. Knox is 0x0. Are there any other ways to check RMM state?
Click to expand...
Click to collapse
Reboot device just to check that OEM unlock is still enabled.

Yes, Bootloader OEM unlock switch is still activated.

JMailuhu said:
Yes, Bootloader OEM unlock switch is still activated.
Click to expand...
Click to collapse
Then read a guide like this, there are other workarounds though https://forum.xda-developers.com/t/...e-prenormal-on-oneui-android-pie-9-0.3911862/ but don't flash custom binaries while you don't bypass RMM prenormal status.

Yeah this requires a linux distro so i guess for that method i have to run linux in a VM or dualboot on another partition.
However, it still doesn't explain why i don't have a RMM message. Maybe RMM is gone altogether (not sure if thats possible tho).
Anyway thanks for your replies.

JMailuhu said:
However, it still doesn't explain why i don't have a RMM message. Maybe RMM is gone altogether (not sure if thats possible tho).
Click to expand...
Click to collapse
What do you mean with? You said RMM appears like prenormal.

SubwayChamp said:
What do you mean with? You said RMM appears like prenormal.
Click to expand...
Click to collapse
No i said i did NOT have any message regarding RMM state in download mode

JMailuhu said:
No i said i did NOT have any message regarding RMM state in download mode
Click to expand...
Click to collapse
Oh, sorry, I read bad, and nothing about KG?
It means you don't have remote restrictions, even with FRP.
In this case, you are able to flash custom binaries.

No problem bud, happens to the best of us. Nope nothing about KG either. I wil try and flash twrp etc. Worst case i'll flash back official firmware. Thanks for the help!

Solved: There was no RMM/KG on the device at all so i went and flashed TWRP and Rise-Q OneUI 2.5. Everything went smooth as butter.

Good, if it is not present in download screen, then in this device, either RMM/KG are not implemented.