Hello,
Recently I have rooted my samsung galaxy J5 SM-J500F phone. Next I opened OEM and enabled USB debugging, and then flashed TWRP with Odin. All went well, made a full backup (i.e. all the options were selected). I have stored the files on my PC, and then foolishly closed the OEM and USB debugging. Some time after I restarted my phone and I was met with the "Custom Binary blocked by FRP" screen. I could not boot into recovery, the only screen accessible was the download screen. I have hunted for a few firmware files, tried to flash them all to no avail. They are either being blocked by the FRP, or the "secure check fail" error (when trying to flash the PIT). I would like to
a) Repair the phone (my personal files can be deleted, no need for me to keep anything)
b) Prevent this issue for recurring (perhaps by disabling this FRP permanently in some way if possible)
Thanks in advance.
Kaizen-85 said:
Hello,
Recently I have rooted my samsung galaxy J5 SM-J500F phone. Next I opened OEM and enabled USB debugging, and then flashed TWRP with Odin. All went well, made a full backup (i.e. all the options were selected). I have stored the files on my PC, and then foolishly closed the OEM and USB debugging. Some time after I restarted my phone and I was met with the "Custom Binary blocked by FRP" screen. I could not boot into recovery, the only screen accessible was the download screen. I have hunted for a few firmware files, tried to flash them all to no avail. They are either being blocked by the FRP, or the "secure check fail" error (when trying to flash the PIT). I would like to
a) Repair the phone (my personal files can be deleted, no need for me to keep anything)
b) Prevent this issue for recurring (perhaps by disabling this FRP permanently in some way if possible)
Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572 That might be worth trying the OEM unlock needs to be left alone when it is unlocked and never touched again.
Related
Edit: No one replied with a good answer so i reinstalled stock recovery while keeping root and turned off OEM Unblock and it bricked my device with "custom binary blocked by frp lock" and i am currently fixing it with Smart Switch initialization. Moral of the story: Never disable OEM Unlock
(A5 2016)
Does this happen after you turn off OEM Unlock because the recovery is not stock (TWRP is installed) or because the device is rooted or both?
If after rooting with https://forum.xda-developers.com/sa...overy-samsung-sm-a510f-fd-exynos7580-t3314399 i flash stock recovery and turn off OEM Unlock will i still get this message?
Thanks!
Please note that i had the "custom binary blocked by frp lock" error but i fixed it with Smart Switch initialization. I want to turn off OEM Unlock for security reasons
just flash previous firmware version which u have in your phone before frp lock.
nothing to worry its not bricked.
only ensure version u are going to flash is same as before , flash via odin and enjoy
I already did it, my question is that if i remove TWRP and install the stock recovery while keeping root, will disabling "OEM Unlock" show "custom binary blocked by frp lock"
Help
I am going through a similar enigma. I have S7 Edge. If I log in with Google and then turn down unlock on will I get custom binary error? Any help would be greatly appreciated.
@CrystalGTX
This is an old thread, but I am having the same problem; (stupidly) unchecked OEM Unlock. Reboot, and now I have "Custom binary blocked by FRP lock".
When you say "fixed it with Smart Switch initialization", does that essentially mean reflashing firmware?
And as a result, erasing all data?
I've read that flashing stock firmware can save the hardware, but I'm much more concerned about the data; I need my contacts, photos, txts, etc.
EDIT: Err, shoot. I see now this was posted by a Guest, so I doubt the OP is going to give me a response. Anyone else help?
Hello people, I'm just going to get straight into it... FRP blocked my custom binary on my Samsung Galaxy On5. I am new to FRP and I wasn't being careful when restoring a backup via TWRP. Now I can only boot into download mode and OEM Unlock is disabled from what i can tell. I've tried Odin i can kinda flash the AP file it doesn't work obviously but it does mark my system as official for some reason so FRP isn't triggered but then it tells me to use smart switch to restore it via emergency restore. I can also flash the CSC and CC back to get to square one. I've tried Smart Switch but i don't know my serial number to do the initialization i have an idea of what it might be since i do have a TWRP backup of my phone on my PC so shouldn't my serial be there? Any idea to fix my phone or is it fully bricked?
Hi community,
I tried to flash TWRP and LOS via Odin, but anytime it failed in download mode. On the download screen was a message blocked by "FRP Lock" . I read anywhere this FRP is to avoid that e.g. stolen phone can be flashed - just owner can do. So i did a factory reset (so removed my personal "connection" to the phone) and it worked . I flashed TWRP, flashed LOS 16 - super ! All worked fine - no problems.
BUT after I switched of the phone and I wanted to switch on the phone again it stopped in bootloader (or first black screen) with message "Custom binary blocked by FRP". I was not able to start into TWRP (power+home+volume up), just into download mode. So I tried to flash again TWRP -> blocked by FRP! But now I could not do as in very first beginning a factory reset to avoid FRP block, because phone didn't boot.
I downloaded original firmware latest version (german unbranded version - its a german unbranded phone), but flashing in Odin works only in BL, AP, CSC, but in CP it failed (I tried first all, and then step by step). So phone does not boot. It has boot loop with samsung logo.
Because it seemed that in each status the phone does not charged I opened phone and removed battery to avoid that I can't test anything because of empty battery. I don't have any idea what to do now. Is my phone bricked or is there a chance to switch of FRP if I am not able to boot the phone normally?
Regards Odiad
SOLVED: I found a good explanation in a german Forum, and in addition (one of my problems) I could get SamFirm to run (I had trouble with MS C++ 2008), so with new/other ROM I was able to flash without problems and now mobile works fine again...
Regards Odiad
Hi there,
I got an old man's S7 Edge (SM-G935F) and I'd like to help him rescuing his photos (he doesn't have a periodic backup but he learned from this now).
The phone did stuck at the boot screen. He didn't try to modify anything.
FRP Lock on unfortunately. Should be the latest Android.
I can enter the download mode (not the recovery) but no chance for TWRP b/c of FRP. Same error for an engineering recovery I found online.
AP SUREV: B:8 K:B S:7
So I got me two OEM firmware packages with Frija and try to reflash but it always stuck at flashing "boot.img" endlessly.
Also it got me to the "An error has occurred while updating the device software, Use the Emergency recovery function in the Smart Switch PC software." screen now.
(I have no code for Smart Switch recovery but I still can get into download mode using FRP Hijacker.)
Is the NAND most likely roasted and the only hope may be chipoff? Tried on different PCs with different cables.
Thanks,
Nico
Edit: I don't need a working device, decrypted dump would be enough.
Edit 2: When I skip the AP package (containing the "boot.img.lz4"), it stucks at flashing "RADIO" after a few percent.
BUJ1 fw. I had previously rooted the device and it was working fine, then x days later found it wouldnt boot (teal screen with 'enrolled knox guard prevent flashing factory binary (vbmeta)' displayed) so I reflashed the stock binary. Now when I go into dev options, I cant get OEM unlock to appear (tried the date forward/back.. didnt work). Anyone know how I can fis that?
Additionally, in download mode the tab shows 'oem lock off (u)' and 'kg status normal', but when I try to flash the magisk modified ap file to root it, it fails almost at the end of the odin process with the 'enrolled knox guard prevent flashing factory binary (vbmeta)' error displayed on the download screen. Rebooting then boots back into the stock android. Is this likely to be linked to the owm unlock being unavailable in dev options even tho the device is showing oem lock is off?