RMM state: prenormal after OEM unlock on Android 9.0 - Samsung Galaxy Note 9 Questions & Answers

Hello!
Got a strange situation: set up new Note9, updated it to Pie, connected to Wi-Fi and did OEM unlock instantly rebooting to Odin mode to flash TWRP, but instead of this I got RMM state: prenormal message (should be RMM state: checking in Pie) and KG state : checking. Booted back in OS, set it up and see OEM unlock active in Development options. Unlocked lots of samsung devices - but they are all always got me RMM checking and let flash TWRP instantly in PIE. Is this some new security feature or its because I updated to PIE from Oreo and still have to wait 7 days for unlock?

+1 waitting

Narkozzz said:
Hello!
Got a strange situation: set up new Note9, updated it to Pie, connected to Wi-Fi and did OEM unlock instantly rebooting to Odin mode to flash TWRP, but instead of this I got RMM state: prenormal message (should be RMM state: checking in Pie) and KG state : checking. Booted back in OS, set it up and see OEM unlock active in Development options. Unlocked lots of samsung devices - but they are all always got me RMM checking and let flash TWRP instantly in PIE. Is this some new security feature or its because I updated to PIE from Oreo and still have to wait 7 days for unlock?
Click to expand...
Click to collapse
the waiting periode is not the issue. if oem unlock is there then no wait was needed.
the real problem was not reading the guides section attentively. check for dr.ketans guide and follow it through.
you should be using method 1 in the guide.
and again follow it from a to z.
now flash back stock firmware and start the procedure again.

bober10113 said:
the waiting periode is not the issue. if oem unlock is there then no wait was needed.
the real problem was not reading the guides section attentively. check for dr.ketans guide and follow it through.
you should be using method 1 in the guide.
and again follow it from a to z.
now flash back stock firmware and start the procedure again.
Click to expand...
Click to collapse
The problem is RMM prenormal state even after clean flash of stock rom and oem unlock enabled. I cant flash anything non-signed. With all respect to dr.ketan I have mine experience that never failed before - RMM checking always appear after unlock on Pie. So I asking people who could have same issue - will it change from prenormal to checking in 7 days or I better flash Oreo and wait 168 hours?

Narkozzz said:
The problem is RMM prenormal state even after clean flash of stock rom and oem unlock enabled. I cant flash anything non-signed. With all respect to dr.ketan I have mine experience that never failed before - RMM checking always appear after unlock on Pie. So I asking people who could have same issue - will it change from prenormal to checking in 7 days or I better flash Oreo and wait 168 hours?
Click to expand...
Click to collapse
fine dont read and follow the guide to flash his root oem fix root v5
sheesh
here are some more details since you are new to note 9.
here an other zip that does partially what ketans does:
https://1drv.ms/u/s!AhXVLDDj8g3AgrxVEeICKZil9BIAUA?e=kpfiM9
it has no kernel nor magisk.
ketan has a kernel and magisk AND rmm state fix that should make device be able to boot while on custom recovery as the kernel needs to be patched in order to boot.

bober10113 said:
the waiting periode is not the issue. if oem unlock is there then no wait was needed.
the real problem was not reading the guides section attentively. check for dr.ketans guide and follow it through.
you should be using method 1 in the guide.
and again follow it from a to z.
now flash back stock firmware and start the procedure again.
Click to expand...
Click to collapse
bober10113 said:
fine dont read and follow the guide to flash his root oem fix root v5
sheesh
here are some more details since you are new to note 9.
here an other zip that does partially what ketans does:
https://1drv.ms/u/s!AhXVLDDj8g3AgrxVEeICKZil9BIAUA?e=kpfiM9
it has no kernel nor magisk.
ketan has a kernel and magisk AND rmm state fix that should make device be able to boot while on custom recovery as the kernel needs to be patched in order to boot.
Click to expand...
Click to collapse
Thank you for trying to help me, friend. But you misses the core thing - to flash anything mentioned in dr.ketan's guide I have to flash TWRP first. But I cant flash TWRP since I have RMM state prenormal mode alongside with unlocked bootloader. Even after reflash of stock rom. So the only question in my situation is: will RMM state change after 168 hours wait on Pie, or I need to flash Oreo rom first and wait. I am not new neither to Note9 unlocking, not to Samsung devices and have all needed tools to fix OEM and RMM issue AFTER I will get a chance to flash TWRP.

Narkozzz said:
Thank you for trying to help me, friend. But you misses the core thing - to flash anything mentioned in dr.ketan's guide I have to flash TWRP first. But I cant flash TWRP since I have RMM state prenormal mode alongside with unlocked bootloader. Even after reflash of stock rom. So the only question in my situation is: will RMM state change after 168 hours wait on Pie, or I need to flash Oreo rom first and wait. I am not new neither to Note9 unlocking, not to Samsung devices and have all needed tools to fix OEM and RMM issue AFTER I will get a chance to flash TWRP.
Click to expand...
Click to collapse
flash stock. boot to home screen make it check for updates in the software menu once. check dev tool if OEM unlock is there. if it is a unlocked flash twrp. and boot directly to recovery after odin finishes. in recovery format data in wipe menu and type yes. go to reboot menu and choose reboot to recovery. flash ketans oem root fix v5 in aroma setup choose to flash kernel and magisk.
ive had your issue before. its not complicated. just do what i said if your oem unlock is there and unlocked. if its vanished and want it to appear then there are guides to make it appear instead of waiting.
also do you want oreo or pie? ketan has both. just read..

You are not listening: I flashed stock; I connected to WiFi; I do see OEM unlock enabled in Development Options; Still I have RMM state prenormal in Odin mode and cant flash TWRP.

Narkozzz said:
You are not listening: I flashed stock; I connected to WiFi; I do see OEM unlock enabled in Development Options; Still I have RMM state prenormal in Odin mode and cant flash TWRP.
Click to expand...
Click to collapse
well if you dont try as i said of course youll never know.
again, i had your issue and alot of people as well. please use xda search feature and read. if not then dont post for help if you dont want help.

Narkozzz said:
You are not listening: I flashed stock; I connected to WiFi; I do see OEM unlock enabled in Development Options; Still I have RMM state prenormal in Odin mode and cant flash TWRP.
Click to expand...
Click to collapse
I also have the problem, but with the S10.
OEM activation active, even reactivated in download mode, so OEM activation is gray. Even the trick with the 8 days did not help - it remains prenormal.

bober10113 said:
the waiting periode is not the issue. if oem unlock is there then no wait was needed.
you should be using method 1 in the guide.
Click to expand...
Click to collapse
Hello, do you have a link for the manual?
Have been looking for a long time and geffen nothing.
Maybe I will continue with the instructions to get the "prenormal" away

bininga59 said:
Hello, do you have a link for the manual?
Have been looking for a long time and geffen nothing.
Maybe I will continue with the instructions to get the "prenormal" away
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143

I am in the same situation, the rmm state prenormal still continues
even when I have the OEM unlocked, in fact I tried to do it through the chimera
program, but for having the June android security patch (CSF2)
the chimera friends commented to me that for that reason I could not do the
unlocking of rmm through their program, they told me that they worked on a
solution for it, but they did not give me an estimate of time, I guess we will
have to wait for a solution from them, since searching and reading most of the post,
none worked for me, I'm stuck in not being able to flash TRWP, so I can't really do anything.
I hope someone finds a solution or that through the chimera program, we can correct that problem.

I'm facing same problem on sm-a730f, the rmm state prenormal still active
even when I have the OEM unlocked

Same problem here, i'm using a brazilian Samsung galaxy Note 9 N9600 retail version

Same situation here i have galaxy s9 exynos

RMM state prenormal fix for non-US phones
@bober10113 et al, specially non-US folks
I guess these guys are suffering the same as me, it is exactly like what @Narkozzz said. RMM state prenormal (even with OEM already unlocked!!!) won't allow for flashing one single thing other than official binaries e.g. TWRP without which we can do nothing (the fixes are only prevention, not remedying).
Skimming through Samsung international forums abroad and other websites I saw the solution consists in installing the SIM card, flashing stock with Odin again, and then keeping the cellphone, the simcard and the mobile data turned on constantly. Eventually after 7 days, on in some cases more than a month, that state will reset back and we will then be able to flash TWRP and the RMM bypass, plus noverity etc. etc.
Ketan also mentioned that in the comments in his topic, although he did not mention specifically about keeping the simcard together with mobile data enabled during all the time
I'm about to flash mine now and wait with everything enabled, following that solution.
Will report back in here after a while
Cheers!

active usb debugging and active oem, the same happens in note 9, waiting for your experience

For what it's worth, I'm going to share what I've done; since it seems like I've somehow just stumbled through the same issue on my note 9, without having to wait any substantial amount of time. Hopefully it's of some use to someone.
I originally had N960FXXU3CSF9 (rooted with TWRP installed) on my Exynos Note 9; flashed stock N960FXXS3CSG5 using Odin, got about half way through the new device setting up process then black screen with "Only official released binaries are allowed to be flashed" message.
Me rambling about my fails
After the initial 30 minutes of panic and swearing, got the phone to download mode (Volume Down + Bixby, plug in USB from PC), then various combinations of trying to flash the same stock N960FXXS3CSG5 rom, TWRP, trying to install no-verity-opt-encrypt and Magisk-v18.0. The only change I noticed was RMM state sometimes seems to be stuck on "checking" instead of "Prenormal" while in download mode sometimes; either way, all ends with the same "Only official released binaries are allowed to be flashed" brick.
Last ditch attempt that worked for me:
(from RMM msg brick)
- Volume Down + Bixby, plug in USB from PC to Download mode
- Flashed the old N960FXXU3CSF9 stock rom with Odin;
- Turned phone off after 1st reboot after ^;
- Volume Down + Bixby, plug in USB from PC to Download mode
- Flashed twrp-3.2.3-0-crownlte_UNOFFICIAL.tar.md5
- Held down Volume Up + Bixby + Power before reboot from ^, to boot straight to TWRP recovery
- Transferred N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip & Magisk-v18.0.zip from PC to external SD card
- From TWRP, Wipe - Format Data - "yes"; after format is done, press back to first TWRP page
- Install N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip
- Install Magisk-v18.0.zip
- Wipe Dalvik Cache
- Reboot to System
More rambling
it then took a few minutes with boot img before "optimizing apps" (I assume this is code for Samsung black magic and murdering imaginary orphans?) then eventually I got to enter my details through the new device set up process... for the 10th time today. So far it's been about 6hrs since I've put all my apps back, in developer options OEM unlocking is off, but
I have root access back, and everything seems to be fine.
Sorry that I kept jumping between tenses and waffled on a bit there; it's been a long 20 hrs of reading forums, articles, hand cramps death gripping phone buttons and bashing head against desks. Hope this is useful to someone, I'm off to find 2 tin cans and some string.

Need help for n9... Prenormal

Related

Bypassed OEM Unlock wait time, yet RMM is stil prenormal. TWRP Can't be installed.

So I've used CRHA for weeks, yet OEM unlock never appeared. I found this post to bypass the wait time, so I've flashed the rom again with a full wipe, followed the how-to and got the Oem Unlock option. Yay!
Installed TWRP and I found that data wasn't being detected, so I've flashed the Dm_verity and encryption disabler, rebooted prompted me to wipe the data and right after the device got into a boot loop with the Logo splash screen and a little legend saying that "Only official binaries are allowed". Reflashing stock is the only fix I found so far. I've also noticed that even after the device is OEM Unlocked, the RMM State is still "prenormal"
TLDR: I'm able to bypass the OEM Unlock wait time, I can install TWRP, I can flash the dm-verity fix, yet I'm unable to wipe my phone because of this problem.
Does anyone have a suggestion? What am I doing wrong?
galaxynote2 said:
So I've used CRHA for weeks, yet OEM unlock never appeared. I found this post to bypass the wait time, so I've flashed the rom again with a full wipe, followed the how-to and got the Oem Unlock option. Yay!
Installed TWRP and I found that data wasn't being detected, so I've flashed the Dm_verity and encryption disabler, rebooted prompted me to wipe the data and right after the device got into a boot loop with the Logo splash screen and a little legend saying that "Only official binaries are allowed". Reflashing stock is the only fix I found so far. I've also noticed that even after the device is OEM Unlocked, the RMM State is still "prenormal"
TLDR: I'm able to bypass the OEM Unlock wait time, I can install TWRP, I can flash the dm-verity fix, yet I'm unable to wipe my phone because of this problem.
Does anyone have a suggestion? What am I doing wrong?
Click to expand...
Click to collapse
What post shows you how to bypass? Please link it and I will help. I've never seen such a post despite countless searches and watching the boards.
But regardless, if you are getting the only official binaries screen, your haven't fully bypassed rmm. It sounds like whatever you did is letting you have custom recovery but not custom boot, as the dmv fix modifies there boot image, despite it not being needed on these devices. If what I'm saying is true, I can probably fix it, but I need this bypass guide to test

Note 9 bricked ? N960F DS

Hello samsung gurus! I think I've bricked my phone
A few days ago I tried flashing a custom rom (didn't even get to that part but that was my goal).
I was on DBT XXU2CSA2 with XXU2CRTL so I tried flashing other stock roms (only XXU2) via download mode with Odin 3.13.1 and it didn't work it said something like Custom binaries are not allowed to be flashed due to KG locked (BOOTLOADER).
Then I entered recovery and made a factory reset and selected reboot to bootloader and when I tried to flash a rom (stock XEU XXU2ARJ1) it worked ... now I went and enabled the developer mode ... checked OEM Unlock which restarted my phone ... enabled usb debugging because I was preparing for flashing twrp.
Put the phone in recovery and choose reboot to bootloader after that I flashed twrp and then it booted into it.
I was going to flash Dr.Ketan rom and after I downloaded the files I saw that there was a file BL_N960FXXU2CSA2_CP_N960FXXU2CRLT_extract_this_first.zip so I thought that I need to flash that first so I rebooted my phone from twrp pressed vol down + bixby which got me directly into download mode and flashed the bl and cp from odin and this is where all ended it didn't work as it said :
All binaries are not allowed to be flashed due to KG Locked. (RADIO)
And when I restarted my phone the only thing that appears on the screen is: Custom binary blocked due to remaining installment balance. Even when I plug the charger in I get this message and no charger animation So now I can't boot intro recovery because I flashed twrp .. and when I boot in download mode anything that I try to flash ends with the message:
All binaries are not allowed to be flashed due to KG Locked.
When I boot in download mode I get the following details:
PRODUCT NAME: SM-N960F
CURRENT BINARY: Custom
KG STATE: LOCKED
FRP LOCK: OFF
OEM LOCK: OFF
Secure Download: Enabled
CCIC = MAX77705 hw: 3 main: 30
WARRANTY VOID: 1 (0x030c)
AP SWREV: B:2 K:2 S:2
and a bunch of other info (DID, LOT_ID, CHIP_ID, nAsv_TABLE, nAsv_CPUCL0, nAsv_CPUCL1, nAsv_G3D, nAsv_MIF, nAsv_INT, nAsv_CAM_DISP, nAsv_CP, nAsv_PMIC, nAsv_PMIC_CP, nAsv_FSYS, product_line, asb_version, ids_big, ids_g3d, PMIC_ID, LPDDR4 manufacturer, LPDDR4 process ver, LPDDR3 size)
and anything I try to flash (i tried all files from DBT XXU2, also individual files like just BL/AP/CP/CSC and even individual imgs like sboot, boot, recovery, system, cache) and always the same message All binaries are not allowed to be flashed due to KG Locked.
Is my phone really bricked ? Anybody have any tips on what should I do ? I searched for 2 days for any solution and didn't find anything specific for N960F and solutions for other models didn't work, also nothing comes up on searches on KG STATE :crying:
Have you tried Smart Switch?
moromindful said:
Hello samsung gurus! I think I've bricked my phone
A few days ago I tried flashing a custom rom (didn't even get to that part but that was my goal).
I was on DBT XXU2CSA2 with XXU2CRTL so I tried flashing other stock roms (only XXU2) via download mode with Odin 3.13.1 and it didn't work it said something like Custom binaries are not allowed to be flashed due to KG locked (BOOTLOADER).
Then I entered recovery and made a factory reset and selected reboot to bootloader and when I tried to flash a rom (stock XEU XXU2ARJ1) it worked ... now I went and enabled the developer mode ... checked OEM Unlock which restarted my phone ... enabled usb debugging because I was preparing for flashing twrp.
Put the phone in recovery and choose reboot to bootloader after that I flashed twrp and then it booted into it.
I was going to flash Dr.Ketan rom and after I downloaded the files I saw that there was a file BL_N960FXXU2CSA2_CP_N960FXXU2CRLT_extract_this_first.zip so I thought that I need to flash that first so I rebooted my phone from twrp pressed vol down + bixby which got me directly into download mode and flashed the bl and cp from odin and this is where all ended it didn't work as it said :
All binaries are not allowed to be flashed due to KG Locked. (RADIO)
And when I restarted my phone the only thing that appears on the screen is: Custom binary blocked due to remaining installment balance. Even when I plug the charger in I get this message and no charger animation So now I can't boot intro recovery because I flashed twrp .. and when I boot in download mode anything that I try to flash ends with the message:
All binaries are not allowed to be flashed due to KG Locked.
When I boot in download mode I get the following details:
PRODUCT NAME: SM-N960F
CURRENT BINARY: Custom
KG STATE: LOCKED
FRP LOCK: OFF
OEM LOCK: OFF
Secure Download: Enabled
CCIC = MAX77705 hw: 3 main: 30
WARRANTY VOID: 1 (0x030c)
AP SWREV: B:2 K:2 S:2
and a bunch of other info (DID, LOT_ID, CHIP_ID, nAsv_TABLE, nAsv_CPUCL0, nAsv_CPUCL1, nAsv_G3D, nAsv_MIF, nAsv_INT, nAsv_CAM_DISP, nAsv_CP, nAsv_PMIC, nAsv_PMIC_CP, nAsv_FSYS, product_line, asb_version, ids_big, ids_g3d, PMIC_ID, LPDDR4 manufacturer, LPDDR4 process ver, LPDDR3 size)
and anything I try to flash (i tried all files from DBT XXU2, also individual files like just BL/AP/CP/CSC and even individual imgs like sboot, boot, recovery, system, cache) and always the same message All binaries are not allowed to be flashed due to KG Locked.
Is my phone really bricked ? Anybody have any tips on what should I do ? I searched for 2 days for any solution and didn't find anything specific for N960F and solutions for other models didn't work, also nothing comes up on searches on KG STATE :crying:
Click to expand...
Click to collapse
first time I've herd of KG state.
get samsung smart switch and go to the emergency recovery menu incase that works.
Rosli59564 said:
Have you tried Smart Switch?
Click to expand...
Click to collapse
i tried smart switch latest version and while in download mode it says unrecognized phone ... i also downloaded a version where the device initialization is available .... entered the s/n from the back of the phone and it says n960f doesn't support initialization ... so no luck with smart switch either
I'm on pie and I found in developers options the 6st option down in the row is to unlock bootloader. This is the first time that I've sean something like that and I don't know what's it for but maybe it's your case.
EDIT: sorry, I realized that you already used it.
moromindful said:
i tried smart switch latest version and while in download mode it says unrecognized phone ... i also downloaded a version where the device initialization is available .... entered the s/n from the back of the phone and it says n960f doesn't support initialization ... so no luck with smart switch either
Click to expand...
Click to collapse
check your xda pm for solution
gsmfixer said:
check your xda pm for solution
Click to expand...
Click to collapse
This is still not resolved.
I tryed flashing combination files still the same message in download mode: All binaries are not allowed to be flashed due to KG Locked.
When booting recovery: Custom binary blocked by remaining installment balance
When normal boot same message as in recovery
So if anyone have any ideea what should I try please chip in ...
I will gladly pay for any service related to unbricking my phone or at least guiding me to unbricking it if this is possible.
I added some photos. Still no solution yet
Did you try to flash lastest stock android pie rom
malucthuyquai said:
Did you try to flash lastest stock android pie rom
Click to expand...
Click to collapse
I tried to flash stock rom. full files, partial files ... all give me the same error All binaries are not allowed to be flashed due to KG locked.
moromindful said:
Hello samsung gurus! I think I've bricked my phone
A few days ago I tried flashing a custom rom (didn't even get to that part but that was my goal).
I was on DBT XXU2CSA2 with XXU2CRTL so I tried flashing other stock roms (only XXU2) via download mode with Odin 3.13.1 and it didn't work it said something like Custom binaries are not allowed to be flashed due to KG locked (BOOTLOADER).
Then I entered recovery and made a factory reset and selected reboot to bootloader and when I tried to flash a rom (stock XEU XXU2ARJ1) it worked ... now I went and enabled the developer mode ... checked OEM Unlock which restarted my phone ... enabled usb debugging because I was preparing for flashing twrp.
Put the phone in recovery and choose reboot to bootloader after that I flashed twrp and then it booted into it.
I was going to flash Dr.Ketan rom and after I downloaded the files I saw that there was a file BL_N960FXXU2CSA2_CP_N960FXXU2CRLT_extract_this_first.zip so I thought that I need to flash that first so I rebooted my phone from twrp pressed vol down + bixby which got me directly into download mode and flashed the bl and cp from odin and this is where all ended it didn't work as it said :
All binaries are not allowed to be flashed due to KG Locked. (RADIO)
And when I restarted my phone the only thing that appears on the screen is: Custom binary blocked due to remaining installment balance. Even when I plug the charger in I get this message and no charger animation So now I can't boot intro recovery because I flashed twrp .. and when I boot in download mode anything that I try to flash ends with the message:
All binaries are not allowed to be flashed due to KG Locked.
When I boot in download mode I get the following details:
PRODUCT NAME: SM-N960F
CURRENT BINARY: Custom
KG STATE: LOCKED
FRP LOCK: OFF
OEM LOCK: OFF
Secure Download: Enabled
CCIC = MAX77705 hw: 3 main: 30
WARRANTY VOID: 1 (0x030c)
AP SWREV: B:2 K:2 S:2
and a bunch of other info (DID, LOT_ID, CHIP_ID, nAsv_TABLE, nAsv_CPUCL0, nAsv_CPUCL1, nAsv_G3D, nAsv_MIF, nAsv_INT, nAsv_CAM_DISP, nAsv_CP, nAsv_PMIC, nAsv_PMIC_CP, nAsv_FSYS, product_line, asb_version, ids_big, ids_g3d, PMIC_ID, LPDDR4 manufacturer, LPDDR4 process ver, LPDDR3 size)
and anything I try to flash (i tried all files from DBT XXU2, also individual files like just BL/AP/CP/CSC and even individual imgs like sboot, boot, recovery, system, cache) and always the same message All binaries are not allowed to be flashed due to KG Locked.
Is my phone really bricked ? Anybody have any tips on what should I do ? I searched for 2 days for any solution and didn't find anything specific for N960F and solutions for other models didn't work, also nothing comes up on searches on KG STATE :crying:
Click to expand...
Click to collapse
Hello moromindful,
did you ever find any solution to your problem?
besmirgogu said:
Hello moromindful,
did you ever find any solution to your problem?
Click to expand...
Click to collapse
unfortunately no do you know a solution ? or are you in the same situation ?
moromindful said:
unfortunately no do you know a solution ? or are you in the same situation ?
Click to expand...
Click to collapse
same situation :/
besmirgogu said:
same situation :/
Click to expand...
Click to collapse
Maybe someone who has a solution will see this post now that it is bumped up.
I tried a whole lot of different things all ended in the same problem. All binaries are not allowed to be flashed due to KG Locked.
moromindful said:
Hello samsung gurus! I think I've bricked my phone
A few days ago I tried flashing a custom rom (didn't even get to that part but that was my goal).
I was on DBT XXU2CSA2 with XXU2CRTL so I tried flashing other stock roms (only XXU2) via download mode with Odin 3.13.1 and it didn't work it said something like Custom binaries are not allowed to be flashed due to KG locked (BOOTLOADER).
Then I entered recovery and made a factory reset and selected reboot to bootloader and when I tried to flash a rom (stock XEU XXU2ARJ1) it worked ... now I went and enabled the developer mode ... checked OEM Unlock which restarted my phone ... enabled usb debugging because I was preparing for flashing twrp.
Put the phone in recovery and choose reboot to bootloader after that I flashed twrp and then it booted into it.
I was going to flash Dr.Ketan rom and after I downloaded the files I saw that there was a file BL_N960FXXU2CSA2_CP_N960FXXU2CRLT_extract_this_first.zip so I thought that I need to flash that first so I rebooted my phone from twrp pressed vol down + bixby which got me directly into download mode and flashed the bl and cp from odin and this is where all ended it didn't work as it said :
All binaries are not allowed to be flashed due to KG Locked. (RADIO)
And when I restarted my phone the only thing that appears on the screen is: Custom binary blocked due to remaining installment balance. Even when I plug the charger in I get this message and no charger animation So now I can't boot intro recovery because I flashed twrp .. and when I boot in download mode anything that I try to flash ends with the message:
All binaries are not allowed to be flashed due to KG Locked.
When I boot in download mode I get the following details:
PRODUCT NAME: SM-N960F
CURRENT BINARY: Custom
KG STATE: LOCKED
FRP LOCK: OFF
OEM LOCK: OFF
Secure Download: Enabled
CCIC = MAX77705 hw: 3 main: 30
WARRANTY VOID: 1 (0x030c)
AP SWREV: B:2 K:2 S:2
and a bunch of other info (DID, LOT_ID, CHIP_ID, nAsv_TABLE, nAsv_CPUCL0, nAsv_CPUCL1, nAsv_G3D, nAsv_MIF, nAsv_INT, nAsv_CAM_DISP, nAsv_CP, nAsv_PMIC, nAsv_PMIC_CP, nAsv_FSYS, product_line, asb_version, ids_big, ids_g3d, PMIC_ID, LPDDR4 manufacturer, LPDDR4 process ver, LPDDR3 size)
and anything I try to flash (i tried all files from DBT XXU2, also individual files like just BL/AP/CP/CSC and even individual imgs like sboot, boot, recovery, system, cache) and always the same message All binaries are not allowed to be flashed due to KG Locked.
Is my phone really bricked ? Anybody have any tips on what should I do ? I searched for 2 days for any solution and didn't find anything specific for N960F and solutions for other models didn't work, also nothing comes up on searches on KG STATE :crying:
Click to expand...
Click to collapse
Just for my understatement : You flashed a custom ROM via Odin ?
Are you german (because DBT)?
amorosa said:
Just for my understatement : You flashed a custom ROM via Odin ?
Are you german (because DBT)?
Click to expand...
Click to collapse
I am not german. I bought the phone from a friend who lives in Germany.
I flashed via Odin.
besmirgogu said:
same situation :/
Click to expand...
Click to collapse
Did you find a solution ? I have found that the only way would be to change the mother board :|
moromindful said:
Did you find a solution ? I have found that the only way would be to change the mother board :|
Click to expand...
Click to collapse
unfortunately I was told the same thing. I simply gave up...
I have a phone, same your phone: KG STATE: LOCKED My phone is A205F . Can you help me, any one?
https://techshali.com/unbrick-galaxy-note-9/

KG State prenormal OEM is unlocked

Hello have a problem on my Note 8 N950 my oem is unlocked switches switch is present and visible. KG State will be used in the download Modus prenormal Displayed. Can't flash twrp odin there are errors. I've waited 8 days. Manuel Update search has already been done. I'm connected to wi-fi and mobile data on the Internet. If you have a tip please for help.
Can't help me.. Please is very important.?
akin03 said:
Hello have a problem on my Note 8 N950 my oem is unlocked switches switch is present and visible. KG State will be used in the download Modus prenormal Displayed. Can't flash twrp odin there are errors. I've waited 8 days. Manuel Update search has already been done. I'm connected to wi-fi and mobile data on the Internet. If you have a tip please for help.
Click to expand...
Click to collapse
I had that same problem, i dont know what exactly solved it for me because i did many things, here's what i did in order:
1- flash latest stock rom for your model, mine is N950F exynos so i'm not sure if it's possible to get twrp on Snapdragon models.
2- boot and do the android setup
3- toggle oem unlock off then on
4- reboot into recovery and wipe data/factory reset
5- boot again and do the android setup, repeat step 3
6- boot to download mode and check if KG state changed, if not reflash the rom again, boot, toggle oem unlock again, enter recovery and when it loads (finishes the update/no command screen) do nothing and reboot the phone, then reboot again to download mode.
That's how it worked for me I hope this helps.
Follow this if it worked it's a must https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
AiRMaX-360 said:
I had that same problem, i dont know what exactly solved it for me because i did many things, here's what i did in order:
1- flash latest stock rom for your model, mine is N950F exynos so i'm not sure if it's possible to get twrp on Snapdragon models.
2- boot and do the android setup
3- toggle oem unlock off then on
4- reboot into recovery and wipe data/factory reset
5- boot again and do the android setup, repeat step 3
6- boot to download mode and check if KG state changed, if not reflash the rom again, boot, toggle oem unlock again, enter recovery and when it loads (finishes the update/no command screen) do nothing and reboot the phone, then reboot again to download mode.
That's how it worked for me I hope this helps.
Follow this if it worked it's a must https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Click to expand...
Click to collapse
Hi thank you for the effort and help. I also have an Exynos device. However, as soon as I get into recovery I have bootloop.. Recovery Displays some errors. Therefore, this process is unfortunately no longer possible. Hi thank you for the effort and help. I also have an Exynos device. However, as soon as I get into recovery I have bootloop.. Recovery Displays some errors. Therefore, this process is unfortunately no longer possible. What a pity
AiRMaX-360 said:
I had that same problem, i dont know what exactly solved it for me because i did many things, here's what i did in order:
1- flash latest stock rom for your model, mine is N950F exynos so i'm not sure if it's possible to get twrp on Snapdragon models.
2- boot and do the android setup
3- toggle oem unlock off then on
4- reboot into recovery and wipe data/factory reset
5- boot again and do the android setup, repeat step 3
6- boot to download mode and check if KG state changed, if not reflash the rom again, boot, toggle oem unlock again, enter recovery and when it loads (finishes the update/no command screen) do nothing and reboot the phone, then reboot again to download mode.
That's how it worked for me I hope this helps.
Follow this if it worked it's a must https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Click to expand...
Click to collapse
not working
Did anyone solve this problem??

Note 9 soft bricked?

Hi! I've tried following dr.ketan's post on rooting a Note 9 with the first method ("(Guide)Root +Busybox + OEM Fix + EFS backup Note 9 N960F/FD/N Exynos only").
After that I've flashed RomAur via TWRP, booted up and while setting up my account the screen became black with the message "only official released binaries are allowed" . I've then tried to flash the stock firmware via Odin but on the screen of my phone I get a "SW REV CHECK FAIL (BOOTLOADER) DEVICE 4 BINARY 1" error.
Odin seemed stuck so I unplugged my phone and then got a screen saying "An error has occured updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
My phone's a N960F/DS
After further research I've come to the conclusion that:
1) SW REV CHECK FAIL (BOOTLOADER) DEVICE 4 BINARY 1 means the firmware I was trying to flash was too old and Samsung decided that downgrading isn't an option anymore.
2) I'm unable to flash anything else besides Samsung official firmware for a 7 or more days because of a Knox Guard (RMM/KG state prenormal). So reinstalling any custom recovery to then flash a new Rom can't be done since there's no way to bypass this time period on Pie.
I did end up flashing stock but I can't mod my phone until the kg state goes back to normal or checking
I've tried waiting for 168 hours twice since the last post. KG State won't change from prenormal. I should mention that my OEM unlock option is available but I can't flash anything besides Samsung binaries. Last week I've flashed TWRP despite the KG State not changing and I got the same "only official released binaries are allowed" error followed by a red fail box in ODIN. At this point I have no idea how to fix it. Does anyone have any suggestion?
I've downloaded the latest stock (N960FXXU4DSLB) and installed it. After that it looks like the prenormal state went away. Immediately I've toggled the OEM Unlock option, waited for the factory reset to be done and checked to see if the toggle was still there. The OEM unlock option works just like before BUT I've successfully installed geiti94's latest TWRP (3.2.3 ATM). Flashing RMM-State_Bypass_Mesa_v2.zip no-verity-opt-encrypt-6.0.zip and Magisk 20.2 seem to be able to get root working but there are some weird bugs:
- can't set up any security measure such as a pin, patter or biometrics
- if I try to log into my Samsung account I get a "processing failed" pop up
- restarting my phone causes it to bootloop

CAN'T INSTALL TWRP

I'm using a Samsung galaxy note 8, I used it with android 8. I had to install android 9 because there was no OEM option in the developer settings. I updated it to 9 and now I can turn it on. After I turned it on. In bootloader mode it was doing:
RRM STATUS : Prenormal
KG STATUS: Checking
OEM LOCK: OFF
FRP LOCK: OFF
as you can see OEM is unlocked but when I try to install TWRP the bootloader shows me that "Only official binaries are allowed to be flashed(recovery)"
I think it is because of RRM Status, but how to turn RRM of, I have no idea.
---------------------------ANY HELP WILL BE HELPFUL-----------------------------
Ragromir said:
I'm using a Samsung galaxy note 8, I used it with android 8. I had to install android 9 because there was no OEM option in the developer settings. I updated it to 9 and now I can turn it on. After I turned it on. In bootloader mode it was doing:
RRM STATUS : Prenormal
KG STATUS: Checking
OEM LOCK: OFF
FRP LOCK: OFF
as you can see OEM is unlocked but when I try to install TWRP the bootloader shows me that "Only official binaries are allowed to be flashed(recovery)"
I think it is because of RRM Status, but how to turn RRM of, I have no idea.
---------------------------ANY HELP WILL BE HELPFUL-----------------------------
Click to expand...
Click to collapse
Notice how it says KG Status: Checking?
After unlocking the bootloader, Knox Guard is still active and has not quite unleashed the bootloader.
Here's what you have to do:
Boot into the OEM system (if you haven't yet, you'll need to reflash in Odin)
Skip through the initial setup and connect to the Internet
Enable Developer Options and check to see if the OEM Unlocking toggle is visible
If it isn't, go to System Update and force a check for firmware update (don't actually update if one is available)
After checking for an update, check again to see if OEM Unlocking is visible (should be grayed out, "Bootloader is already unlocked")
If toggle is visible, reboot to download mode. KG STATUS should say COMPLETED, I forget if RMM STATUS changes or disappears.
If they're still the same as they initially were, boot into system again, and set the clock ahead 2 weeks, then check again.
Once you've fixed KG and RMM status, flash TWRP in Odin. Make sure you force the phone to boot into TWRP after flashing, do NOT let it boot into system - this will overwrite TWRP with the stock recovery
Once you're in TWRP, format (not wipe) data. If you intend to continue to use the OEM firmware, make sure you flash Multidisabler. If you intend to install a custom ROM, make sure you reformat /system.
V0latyle said:
Boot into the OEM system (if you haven't yet, you'll need to reflash in Odin)
Skip through the initial setup and connect to the Internet
Enable Developer Options and check to see if the OEM Unlocking toggle is visible
If it isn't, go to System Update and force a check for firmware update (don't actually update if one is available)
After checking for an update, check again to see if OEM Unlocking is visible (should be grayed out, "Bootloader is already unlocked")'ve done this steps
Click to expand...
Click to collapse
I've done these steps.
Ragromir said:
OEM LOCK: OFF
Click to expand...
Click to collapse
As I said my OEM is unlocked, I unlocked it when I installed android 9.0
And for me, I think I need only to do this step to fix RMM and KG:
V0latyle said:
If they're still the same as they initially were, boot into system again, and set the clock ahead 2 weeks, then check again.
Click to expand...
Click to collapse
But It didn't work
Ragromir said:
I've done these steps.
As I said my OEM is unlocked, I unlocked it when I installed android 9.0
And for me, I think I need only to do this step to fix RMM and KG:
But It didn't work
Click to expand...
Click to collapse
I'm not telling you to unlock your bootloader, I understand you already did that.
Is the OEM Unlocking toggle visible in Developer Options? Yes or no.
The RMM: PRENORMAL is what's preventing TWRP from booting.
V0latyle said:
Is the OEM Unlocking toggle visible in Developer Options? Yes or no.
Click to expand...
Click to collapse
It's visible
Ragromir said:
It's visible
Click to expand...
Click to collapse
Ok. KG STATUS is still Checking and RMM STATUS is still PRENORMAL?
V0latyle said:
KG STATUS is still Checking and RMM STATUS is still PRENORMAL?
Click to expand...
Click to collapse
Yes, still same
Ragromir said:
Yes, still same
Click to expand...
Click to collapse
Damn.
It's entirely possible that a newer bootloader version is preventing custom images. This is the case on a few other devices out there because for whatever reason Samsung continues to obstinately try to actively block custom software, including root. Maybe see if you can roll back to a previous version and try again?
I also found this thread, see if anything there helps you
Btw thanks

Categories

Resources