Hello,
I've rooted my S8+ using TWRP + RMM Bypass + no-verify-opt + magisk + odin.
I've done it once, and i disabled the OEM Unlock, then i reconnected, and it boot looped with the message : "Custom binary is locked by FRP lock".
Now, i've rooted my s8+ one more time, i still have OEM unlock, can i restart the phone without that CUSTOM BINARY message ?
Thank you.
Reaxtive said:
Hello,
I've rooted my S8+ using TWRP + RMM Bypass + no-verify-opt + magisk + odin.
I've done it once, and i disabled the OEM Unlock, then i reconnected, and it boot looped with the message : "Custom binary is locked by FRP lock".
Now, i've rooted my s8+ one more time, i still have OEM unlock, can i restart the phone without that CUSTOM BINARY message ?
Thank you.
Click to expand...
Click to collapse
Yes you can.
Once modification is done to your phone turning off OEM lock ( re-locking bootloader ) will cause you issues.
Is there any way to get around those issues?
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
Well I'm having a strange issue.
I've unlocked bootloader then flashed twrp. It didn't work then. When i boot my phone to recovery, a screen appears with a security warning and nothing happens. Then somehow my frp is triggered. Now i can't flash anything and my recovery is messed up . My phone boots normally though.
Is there any way to unlock the FRP? :/
Anyone? ?
Rommco05 said:
In developer options is OEM setting which need be enabled for FRP unlocked. Probably with unlocked bootloader u cant change this option, so need relock bootloader and enable OEM and again unlock bl
Click to expand...
Click to collapse
I know that brother. I've tried dload method for full firmware restore. Sadly after 5% it shows error . Now I'm left with no options at all.
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.