I rooted my s7, latest version of 8.0 United Kingdom (g930fxxu4esae build r16nw.g930fxxs5esf6). I used TWRP and magisk.
All was well until I rebooted, then got the dreaded "custom binary blocked by frp lock". I was able to take the stock rom and install the AP file, and now it's working again except that of course root is gone. I suspect that if I attempt to root again, I will run into the same error on a reboot.
I've done some googling but haven't found anything really reliable sounding about getting around this problem.
EDIT: UPDATE: I've flashed the latest version of BTU on phones 1 and 2. I've successfully rooted phone 1 and it seems to be sticking. Phone 2 I'm still working on, it doesn't have to be rooted though as it's more of a backup for gaming. Thanks again to everyone in this thread for all the good advice and info.
You are going to have to re flash you current firmware unrooted and before you root, enable OEM unlocking in developer options AFTER setting up your google account(you have to use the same google account as you did before), unfortunately there is no way of force enabling OEM unlock with a flashable zip on the s7, well least to my knowledge. FRP lock is googles factory reset protection, which stops people from factory resetting a phone and then just use their google account instead of the one they don't know the password too, and it stops custom binaries like trwp from booting and even a stock binary that has been rooted from booting because it thinks you could be trying to bypass FRP.
Enabling OEM unlocking with disable FRP lock on the device, allowing you to use custom binary and boot normally without the checks.
Viper4060 said:
You are going to have to re flash you current firmware unrooted and before you root, enable OEM unlocking in developer options AFTER setting up your google account(you have to use the same google account as you did before), unfortunately there is no way of force enabling OEM unlock with a flashable zip on the s7, well least to my knowledge. FRP lock is googles factory reset protection, which stops people from factory resetting a phone and then just use their google account instead of the one they don't know the password too, and it stops custom binaries like trwp from booting and even a stock binary that has been rooted from booting because it thinks you could be trying to bypass FRP.
Enabling OEM unlocking with disable FRP lock on the device, allowing you to use custom binary and boot normally without the checks.
Click to expand...
Click to collapse
Correct basically turn FRP lock off it's a pain in the ass.
Also @kettir this is the final release of BTU not the one you have in your post 》》https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/BTU/download/G930FXXU5ESD2/270504
cooltt said:
Correct basically turn FRP lock off it's a pain in the ass.
Also @kettir this is the final release of BTU not the one you have in your post 》》https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/BTU/download/G930FXXU5ESD2/270504
Click to expand...
Click to collapse
Thanks for more great advice and info. It appears that now the requirements are:
Download the latest BTU as per your note because I like it better
Flash it to attain a "stock" system.
Go through the minimum setup after reboot and get developer options.
Set up google account
Enable OEM unlocking (and USB debugging of course)
flash TWRP
go into recovery immediately
Use TWRP to flash magisk
go back into download mode immediately
flash only the AP from the stock firmware
And this might, possibly, achieve root with magisk, while keeping the stock bootloader. That is, if I understand what TWRP and magisk are actually doing to the system. I.e., TWRP replaces the system part that handles recovery, while magisk roots the phone without changing the system, so that TWRP is the problem for FRP.
Related
Running: Galaxy S7 with SupermanRom 2.3
Yeah, I did it... Disabled all USB debugging and OEM unlock due to some testing and forgot about it during a subsequent reboot.. Now stuck with bootloop "Custom binary blocked by FRP lock"
Is there any way to fix this without a full recover to stock ROM?
If not, can the data at least be recovered some way?
Very thankful for any help!
do Flash with stock firmware latest than let me know status.
In short, no there isn't really flash via odin and start again
I already unlocked the bootloader, happens anything if I turn off oem unlock in developer settings or will the bootloader relock?
Maik_ said:
I already unlocked the bootloader, happens anything if I turn off oem unlock in developer settings or will the bootloader relock?
Click to expand...
Click to collapse
Turned it off once by accident but turned on again.. Nothing changed
I don't think anything changes unless u relock it via fastboot, which at that point as long as u can boot back into the OS, u can always unlock it again, relocking bootloader will format ur data and u will no long be rooted or have twrp installed
locking your bootloader with root etc installed can cause major problems so before doing that you should flash a stock firmware otherwise you will be locked out
Why would you want to do this? There is no benefit to it if you plan to stay rooted.
Need to find something to do. You bored
iElvis said:
Why would you want to do this? There is no benefit to it if you plan to stay rooted.
Click to expand...
Click to collapse
I want to disable developer options, but if I do that OEM-Unlock automatically turns off and I don't want to reboot because I dont want that I lock myself out.
Your cat will get knock up..........again!
Maik_ said:
I want to disable developer options, but if I do that OEM-Unlock automatically turns off and I don't want to reboot because I dont want that I lock myself out.
Click to expand...
Click to collapse
Just turning off Developer Options won't relock your bootloader. You can only do that manually in fastboot. But you'll also lose USB debugging, which means adb won't work anymore in case something goes wrong. (But leaving USB debugging on all the time isn't the best idea anyway.)
Hello everyone
I think I did that mistake
I have twrp installed on my phone Samsung SM-G532F . my phone was working just fine but I have locked the oem for no reason .
now when I turn off the device and tried to turn it on it shows { Custom binary blocked by FRP. (boot. img) }
and when I open recovery mode it shows { Custom binary blocked by FRP. (recovery. img) }
the download mode is working and shows that the FRP lock is on .
I tried to flash the stock recovery with odin but since the FRP is locked it failed .
the adb is not working because the device cannot boot , even the battery symbol when I plug my phone with a charger is not displayed and shows the error { Custom binary blocked by FRP. (boot. img) }
any ideas will help a lot .
omer123137 said:
Hello everyone
I think I did that mistake
I have twrp installed on my phone Samsung SM-G532F . my phone was working just fine but I have locked the oem for no reason .
now when I turn off the device and tried to turn it on it shows { Custom binary blocked by FRP. (boot. img) }
and when I open recovery mode it shows { Custom binary blocked by FRP. (recovery. img) }
the download mode is working and shows that the FRP lock is on .
I tried to flash the stock recovery with odin but since the FRP is locked it failed .
the adb is not working because the device cannot boot , even the battery symbol when I plug my phone with a charger is not displayed and shows the error { Custom binary blocked by FRP. (boot. img) }
any ideas will help a lot .
Click to expand...
Click to collapse
You cannot boot with a custom recovery and a locked bootloader. As to how to fix this, you need to ask in the Samsung forums. This is for OnePlus 6.
If you have a oneplus look in the forum for msmdownloadtool and follow the steps, you can revive your phone.
If your phone its a samsung, search in samsung forums for a tool to unbrick your phone.
iElvis said:
You cannot boot with a custom recovery and a locked bootloader. As to how to fix this, you need to ask in the Samsung forums. This is for OnePlus 6.
Click to expand...
Click to collapse
I was finally able to solve this issue with flashing the official firmware with odin . now I will never touch the oem unlock button ever again :laugh: . but thank you for your reply .
---------- Post added at 07:27 PM ---------- Previous post was at 07:22 PM ----------
Toni Moon said:
If you have a oneplus look in the forum for msmdownloadtool and follow the steps, you can revive your phone.
If your phone its a samsung, search in samsung forums for a tool to unbrick your phone.
Click to expand...
Click to collapse
I downloaded and flashed the official firmware with odin and it worked . thanks for the reply
I did this once on my OnePlus X, disabled oem unlocking in developer options. phone and recovery worked fine. I did a backup. Flashed a new rom to test it. The rom had AOSP recovery in the zip, overwriting twrp (opx has separate recovery partition). I flashed gapps affter the rom and the setup wizard was crashing so I could not boot in the home screen. Tried TWRP, its gone. Tried to boot to twrp via fastboot, oem locked. Had to do hard brick reset. Backup and data, gone.
TLDR, you should leave it on, unless you are on stock firmware.
After flash a rom you must flash twrp recovery again, restart in recovery and flash gapps and magisk
First of all you have to flash combination file associated with your device model through ap slot of odin.
Then your phone will turn on and you can access settings through which you can turn on oem unlock.
Then you can install your desired rom into your device
Sinankhan.official said:
First of all you have to flash combination file associated with your device model through ap slot of odin.
Then your phone will turn on and you can access settings through which you can turn on oem unlock.
Then you can install your desired rom into your device
Click to expand...
Click to collapse
This isn't a Samsung device.
Maik_ said:
I already unlocked the bootloader, happens anything if I turn off oem unlock in developer settings or will the bootloader relock?
Click to expand...
Click to collapse
I also accidentally turned off oem in rooted phone , Does my bootloader locked or I can safely reboot
I restored the stock firmware using Odin, but now I see that the bootloader is still unlocked.
When try to lock it again the system says: "If OEM unlock is turned off, your phone will be reset to factory default settings after restart. This will erase all of your data... " etc.
My question is: will the firmware be still in place? I don't mind everything being wiped, because most of it will be restored anyway when I login to Google and Samsung again.
SamarSS123 said:
I also accidentally turned off oem in rooted phone , Does my bootloader locked or I can safely reboot
Click to expand...
Click to collapse
No
Guys, I tried to flash TWRP recovery on my A7, build number xxu1asa4.
I unlocked OEM first, then booted into download mode to install system and suddenly disconnected my phone from PC:
"Custom binary blocked by FRP lock"
I have locked OEM now, no recovery access, and there is a soft brick in my smartphone. :crying:
Does anyone know how to fix that issue?
NickDeveloper said:
Guys, I tried to flash TWRP recovery on my A7, build number xxu1asa4.
I unlocked OEM first, then booted into download mode to install system and suddenly disconnected my phone from PC:
"Custom binary blocked by FRP lock"
I have locked OEM now, no recovery access, and there is a soft brick in my smartphone. :crying:
Does anyone know how to fix that issue?
Click to expand...
Click to collapse
I am also experiencing this problem, the solution is to take in a technician or authorized Samsung.
NickDeveloper said:
Guys, I tried to flash TWRP recovery on my A7, build number xxu1asa4.
I unlocked OEM first, then booted into download mode to install system and suddenly disconnected my phone from PC:
"Custom binary blocked by FRP lock"
I have locked OEM now, no recovery access, and there is a soft brick in my smartphone. :crying:
Does anyone know how to fix that issue?
Click to expand...
Click to collapse
You should've not unlocked the OEM, but also disable the FRP Lock. Initiating a factory reset from Settings (which will force you to enter your Samsung Account password) would've done the trick.
To get your Phone running again, reflash Stock ROM and just repeat the process.
Phone will not boot because of "Custom binary blocked by FRP Lock" What do i do?
So I installed TWRP then Magisk then some modules and I reboot to install the modules and like a complete idiot I turned OEM Unlock off so FRP has tripped and I have no idea how to unlock it. I can't get in my phone but I can get in download mode. Odin3 v3.13 will see my phone and can interact with it. What do I do?
SM-G930F
Oreo
Latest Update
Just Dan said:
So I installed TWRP then Magisk then some modules and I reboot to install the modules and like a complete idiot I turned OEM Unlock off so FRP has tripped and I have no idea how to unlock it. I can't get in my phone but I can get in download mode. Odin3 v3.13 will see my phone and can interact with it. What do I do?
SM-G930F
Oreo
Latest Update
Click to expand...
Click to collapse
You need to flash it back to stock firmware then enter the google account info after reboot to release the FRP lock. It's only a problem if you don't know it.
cooltt said:
You need to flash it back to stock firmware then enter the google account info after reboot to release the FRP lock. It's only a problem if you don't know it.
Click to expand...
Click to collapse
Thanks for the help.
Hey
Is there new 2023 methods to get rid of phone is locked screen? I enabled adb and removed kg lock. Upon disabling systemUI, the screen is blank, How can I manage to get rid of that lock by unistalling system app, or installing new systemUI and getting rid of the original one which is locked.
BARMASAI said:
Hey
Is there new 2023 methods to get rid of phone is locked screen? I enabled adb and removed kg lock. Upon disabling systemUI, the screen is blank, How can I manage to get rid of that lock by unistalling system app, or installing new systemUI and getting rid of the original one which is locked.
Click to expand...
Click to collapse
Install Odin on your camputeur and reinstall your whole system with it.
the A125F system firmware is at this link : https://samfw.com/firmware/SM-A125F
To get to re install the system is not that easy. First no option to factory reset at recovery mode, then locked bootloader. If you can assist on the same, it will really help
give it back jamal
clarify
BARMASAI said:
To get to re install the system is not that easy. First no option to factory reset at recovery mode, then locked bootloader. If you can assist on the same, it will really help
Click to expand...
Click to collapse
If the bootloader is locked, then connect the phone at your pc and press volume + and volum - until the phone starting in download mod and there re install system with odin.
BARMASAI said:
Hey
Is there new 2023 methods to get rid of phone is locked screen? I enabled adb and removed kg lock. Upon disabling systemUI, the screen is blank, How can I manage to get rid of that lock by unistalling system app, or installing new systemUI and getting rid of the original one which is locked.
Click to expand...
Click to collapse
get into BROM Mode, use SP Flash Tool to flash normal firmware, then use FRP Bypass to bypass setup, then turn on OEM Unlocking, reboot to download, enable oem unlocking, reboot to download again, and flash TWRP, from TWRP flash a GSI or a custom ROM.
TheWorldYT said:
get into BROM Mode, use SP Flash Tool to flash normal firmware, then use FRP Bypass to bypass setup, then turn on OEM Unlocking, reboot to download, enable oem unlocking, reboot to download again, and flash TWRP, from TWRP flash a GSI or a custom ROM.
Click to expand...
Click to collapse
This may or may not work too, I have never tried this method before, but it looks fine for the removal of that screen. or in SAMFW Tool I think there is a MDM Bypass, if not then you can use SAMFW tool to bypass the FRP on that phone.