I was just installing a few apps and then rebooted and now getting the messaging "Blocked by FRP Lock". I had turned on the OEM option when I first rooted the phone so I am guessing it somehow turned off.
I have the N920CD, so what are my next steps?
Related
"Custom binary blocked by FRP lock" error message appear on my Galaxy Note 5 SM-N920R6 and I can't fix it. I've tried literally everything, searched the entire internet, but I don't seem to find the right stock firmware for this model nor any other way to unroot it or fix this. Someone please help!
Mr.niceguy09 said:
"Custom binary blocked by FRP lock" error message appear on my Galaxy Note 5 SM-N920R6 and I can't fix it. I've tried literally everything, searched the entire internet, but I don't seem to find the right stock firmware for this model nor any other way to unroot it or fix this. Someone please help!
Click to expand...
Click to collapse
HI
copy bypass google apk file in otg
conect to your phone and go to setting
2. go to about and active developer option
3. active OEM unlock
4. and reset factory
afshin.noorani said:
HI
copy bypass google apk file in otg
conect to your phone and go to setting
2. go to about and active developer option
3. active OEM unlock
4. and reset factory
Click to expand...
Click to collapse
I know this method but my phone won't turn on. It says "Custom binary blocked by FRP lock" on the start up screen and turns back off.
Mr.niceguy09 said:
I know this method but my phone won't turn on. It says "Custom binary blocked by FRP lock" on the start up screen and turns back off.
Click to expand...
Click to collapse
I had to odin back the whole phone to factory rom
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
I was trying to install Camera2 on it. Unlocked it with developer options ->Unlock OEM
After try some things I reset factory the cellphone and decide to forget camera2 things...
So I went to developer options and LOCKED OEM.
After that I reboot in fastboot mode and did fastboot oem lock
Now the cellphone is locked in a bootloop saying that my deveice loaded a differente operational system and a screen to visit miui.com/unlock.
The unlock aplication doesn't work. Says that I can't unlock the device.
So that means I lost my crazy brand new phone? THere's any solution? The Test Point solution will work? Is that the only solution???
Thiank you for any response.
foxdanger said:
I was trying to install Camera2 on it. Unlocked it with developer options ->Unlock OEM
After try some things I reset factory the cellphone and decide to forget camera2 things...
So I went to developer options and LOCKED OEM.
After that I reboot in fastboot mode and did fastboot oem lock
Now the cellphone is locked in a bootloop saying that my deveice loaded a differente operational system and a screen to visit miui.com/unlock.
The unlock aplication doesn't work. Says that I can't unlock the device.
So that means I lost my crazy brand new phone? THere's any solution? The Test Point solution will work? Is that the only solution???
Thiank you for any response.
Click to expand...
Click to collapse
"So I went to developer option and LOCKED OEM" can you be a little more clear. Because unlocking the bootloader locks the OEM unlock option in the developer settings.
Possible cause of your bootloop is the change in your build.prop file.
I did a similar mistake as well. My phone was stuck in a bootloop. My mistake was that I installed Magisk and forgot to uninstall it through the Magisk manager before locking the bootloader and so the system were not in their stock state.
What I did was, I just booted my phone into fastboot.
Unlocked the bootloader again by using "fastboot OEM unlock". Went into fastboot again. Checked the current active slot by "fastboot getvar current-slot" and flashed the stock boot image from the stock pie rom found on Mi website.
Njaiker said:
"So I went to developer option and LOCKED OEM" can you be a little more clear. Because unlocking the bootloader locks the OEM unlock option in the developer settings.
Possible cause of your bootloop is the change in your build.prop file.
I did a similar mistake as well. My phone was stuck in a bootloop. My mistake was that I installed Magisk and forgot to uninstall it through the Magisk manager before locking the bootloader and so the system were not in their stock state.
What I did was, I just booted my phone into fastboot.
Unlocked the bootloader again by using "fastboot OEM unlock". Went into fastboot again. Checked the current active slot by "fastboot getvar current-slot" and flashed the stock boot image from the stock pie rom found on Mi website.
Click to expand...
Click to collapse
What I did was with the phone working I entered on configuration, developer, and turned of the oem lock option.
Than I reboot in fastboot and did fastboot oem lock.
This made the cellphone unbootable. Bootloop saying that I'm trying to start a different operational system.
And I can't make fastboot unlock because I turned off the option in the system, so I can't send fastboot commands like oem edl, unlock, unlock-critical and etc...
I can't do nothing :/
I don't know how the option was working, but was... I know it should be locked, but this time wasn't. Was after I factory reset the cellphone
Your fault that you locked bootloader on a modified system. Do a research next time
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
I've unlocked my device some weeks ago, but I recently reinstalled the stock ROM and it doesn't accept magisk without give me a bootloop, so I decided to keep it originally locking the bootloader using stock ROM. But when I type
Code:
fastboot oem lock
, it says that I got to enable "OEM unlocking", and I can't do it, the button still in gray and it says "bootloader is already unlocked".
How can I fix it???