Develop Bugs

Help getting S9 back to stock.

Hi all,
I've searched and searched but haven't been able to find anyone else with the same issue I have with my S9, so i'm hoping somebody might be able to help me out!
Basically i installed twrp and then installed Lineageos with Odin. But after a while decided i wanted to go back to stock (there were a few things i was missing, dolby atmos, the stock camera, wi-fi calling and google pay.)
I downloaded a stock firmware from updato and installed with Odin. I used the BTU version, although my phone would have come with the XEU version as standard. I used the HOME_CSC (not sure if that is important?)
So now my phone has stock firmware and got an OTA update yesterday. But when i go into dev settings OEM unlock is greyed out and says 'Bootloader is already unlocked' and my phone is also uncertified in the play store and failed safetynet.
So i'm hoping to be able to get my phone back to the boot loader locked state and to get it certified and passing safetynet. I've waited 7 days as some people have suggested, phone was up for 170 hours but OEM unlock is the same and phone is still uncertified. My next thought is to install the XEU firmware and see if that makes any difference, but i'm not convinced it will.
Does anyone have any idea on how i can fix this please??

evjohns said:
Hi all,
I've searched and searched but haven't been able to find anyone else with the same issue I have with my S9, so i'm hoping somebody might be able to help me out!
Basically i installed twrp and then installed Lineageos with Odin. But after a while decided i wanted to go back to stock (there were a few things i was missing, dolby atmos, the stock camera, wi-fi calling and google pay.)
I downloaded a stock firmware from updato and installed with Odin. I used the BTU version, although my phone would have come with the XEU version as standard. I used the HOME_CSC (not sure if that is important?)
So now my phone has stock firmware and got an OTA update yesterday. But when i go into dev settings OEM unlock is greyed out and says 'Bootloader is already unlocked' and my phone is also uncertified in the play store and failed safetynet.
So i'm hoping to be able to get my phone back to the boot loader locked state and to get it certified and passing safetynet. I've waited 7 days as some people have suggested, phone was up for 170 hours but OEM unlock is the same and phone is still uncertified. My next thought is to install the XEU firmware and see if that makes any difference, but i'm not convinced it will.
Does anyone have any idea on how i can fix this please??
Click to expand...
Click to collapse
HOME_CSC does not reset the device, CSC does, chances are some of the root stuff / system modified files are still present causing these problems
Factory reset, if that doesn't work, flash again but use CSC this time

*Detection* said:
HOME_CSC does not reset the device, CSC does, chances are some of the root stuff / system modified files are still present causing these problems
Factory reset, if that doesn't work, flash again but use CSC this time
Click to expand...
Click to collapse
Thanks, I'll try that again later. Any idea whether it matters if i use the XEU or BTU firmware?

evjohns said:
Thanks, I'll try that again later. Any idea whether it matters if i use the XEU or BTU firmware?
Click to expand...
Click to collapse
Probably won't be able to switch to BTU if you were originally on XEU, BTU is multiCSC and contains XEU so the phone will default to it's original CSC
The firmware will flash fine, but if you check the CSC it will likely still be on XEU unless you managed to change it when you were custom

*Detection* said:
Probably won't be able to switch to BTU if you were originally on XEU, BTU is multiCSC and contains XEU so the phone will default to it's original CSC
The firmware will flash fine, but if you check the CSC it will likely still be on XEU unless you managed to change it when you were custom
Click to expand...
Click to collapse
Yep you're right, it's still XEU. I'll try a factory reset. I'm hoping the OTA update may have fixed a few things.

Can you lock the bootloader back?

parnunu said:
Can you lock the bootloader back?
Click to expand...
Click to collapse
I did a factory reset, then flashed the stock ROM again and used CSC, but the boot loader is still unlocked. I don't have the option to re-lock it, so seems like maybe you can't

Just in case this helps anyone else, I did a complete reset of the stock ROM using @rifek4 instructions from https://forum.xda-developers.com/galaxy-s7/how-to/guide-onelatest-stock-fw-csc-root-t3702963
But i'm still not able to re-lock the boot loader. So going to leave it now and hope the option comes back after 7 days.

rifek4 said:
https://forum.xda-developers.com/showpost.php?p=76388485&postcount=51
Click to expand...
Click to collapse
Thanks for replying. Do you think that method would help me to re-lock the boot loader?
When I go to the settings the OEM unlock says "boot loader is already unlocked"
Basically all I want to do is get safety net to pass again, and it seems that having an unlocked boot loader makes it fail.

Just in case this helps anyone else.
I downloaded magisk 16.7 beta, 16.6 caused my OS (lineage 15.1) to crash, but 16.7 was fine. I installed universal safety net fix for magisk, beta version. Installation said it failed, but when I rebooted it had worked!
Safety net now passes, device is certified in play store and Google pay is working fine. As @rifek4 said, bootloader lock has nothing to do with safety net (although I've seen a lot of people claiming it does).

I waited 7 days then disabled oem unlock in the developer option.
DONE.
None of skip wait time method work for me.

J600G RMM State prenormal

Hello everyone,
I have an SM-J600G device which I am actually using in a country that doesn't sell it, so there is no stock ROM for this country.
I have already OEM unlocked, but the issue is that my RMM state is always prenormal even after waiting several 7 days.
I think it's because I'm using a different stock ROM than my SIM network (But i'm obligated to do since there is no stock rom for the country i'm living in right now). If it is really the case is there like any solution to root my phone?
Thank you,

Up

Up

no solution ..
stuck on recovery and no other method to remove rmm state prenormal

I've tried another country's firmware to test out the reach of rmm. I got rmm removed completely, so yours would be a hardware problem, maybe. It's hard to say

ShaDisNX255 said:
I've tried another country's firmware to test out the reach of rmm. I got rmm removed completely, so yours would be a hardware problem, maybe. It's hard to say
Click to expand...
Click to collapse
Thanks for the reply. For my case, the phone is Malaysian and I use Malaysian stock ROM along with Moroccan SIM card. In download mode I got that "CARRIER_ID" flag that has "XME" value which is the Samsung code for Malaysia.
Do you think this is maybe the problem?

Up

Well I have installed a stock Pie ROM with bootloader and modem from Oreo Rom to get rid of this RMM flag. But it didn't work. It seems as @ShaDisNX255 said, it's a hardware problem.

I finally managed to remove this cursed flag using this method.

S9 Exynos - Rooting issue - only official released binaries are allowed to be flashed

Hi All,
Happy new year. I had been struggling to root the S9 and getting the following error
"only official released binaries are allowed to be flashed(recovery)" while ODIN flashing of TWRP 3.2.1.1.tar
I tried a few methods mentioned in the forum - Wipe/factory reset->Flash Official firmware-> again TWRP using odin
Also tried OEM unlock option. Still cannot succeed in rooting the phone.
Kindly help me with the files and procedure to root and install stock rom. Thank you all in advance.
Regards,
Raghav

Need to have both rmm normal and oem unlocked

amakuramio said:
Need to have both rmm normal and oem unlocked
Click to expand...
Click to collapse
So do I need to flash rmm before twrp flashing?

amakuramio said:
Need to have both rmm normal and oem unlocked
Click to expand...
Click to collapse
I know there are lists of threads dealing with this topic, but I would request for your help in the procedure to root the phone successfully. Thanks in advance

amakuramio said:
Need to have both rmm normal and oem unlocked
Click to expand...
Click to collapse
How to make rmm normal?? How long to wait 7 days or 14 days after OEM unlock. Also need to put the sim on the phone or can just leave it ON with wifi connection?

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

[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.