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
Related
Hello, this is my first post here.
I know the same title was used in so many posts, but I think my case is different.
I have this g610f which had frp lock and was on 7.0, so I downloaded and flashed the combination rom(I do not have the box), made sure usb debugging was on and tried to go back to stock(worked for me with s8 and a310).
Although this time if I flash only AP it says "custome binary(boot) blocked by frp lock" and if I try to flash the BL with AP it says "secure check boot failed".
Also tried to flash TWRP, recovery was blocked by frp lock
whitymighty said:
Hello, this is my first post here.
I know the same title was used in so many posts, but I think my case is different.
I have this g610f which had frp lock and was on 7.0, so I downloaded and flashed the combination rom(I do not have the box), made sure usb debugging was on and tried to go back to stock(worked for me with s8 and a310).
Although this time if I flash only AP it says "custome binary(boot) blocked by frp lock" and if I try to flash the BL with AP it says "secure check boot failed".
Also tried to flash TWRP, recovery was blocked by frp lock
Click to expand...
Click to collapse
did you unlock the OEM in the developer option?
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.
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.
Hello,
I had a problem with my samsung j7 prime (SM-G610M) biometric reader and now the only way to access the phone is through the password I can't remember anymore.
I tried installing a custom recovery (TWRP) with Odin, then removing the password file and recovering my photos. When I try to install TWRP I get the message "custom binary blocked by FRP lock".
USB debug is not enabled.
Is there any possibility of circumventing this protection?
This should be easily resolved by flashing latest firmware for your device in Odin. Just make sure you choose CSC and not Hone CSC. You will lose all your data and internal memory but will have your phone back. Doesn't matter if you have not enabled USB debugging as you will be on download mode. I assume that you did not unlocked bootloader, reason why you are frp locked.