Custom binary (Recovery) blocked by FRP when flashing custom recovery - Galaxy Grand Prime Q&A, Help & Troubleshooting

Hi everybody, I'm new here and I wanted to ask you a problem:
Few days ago I rooted my Samsung Galaxy Grand Prime SM-g53f with a pre-rooted ROM (It was the only way) and I wanted to install xposed framework, but for lollipop is needed a custom recovery, but trying to flash it by odin it says:"Custom binary (Recovery) blocked by FRP". I've been looking on a lot of forums, but I get no answer. I tried with the TWRP app but it says that an error happens.

Delete your google account first. Then flash twrp

Don't do what @aamnahid said, go to the developer options (Tap 8 times in build number), and check OEM Unlock. Then reboot your phone normally then you can try and flash it.

fabiossilva21 said:
Don't do what @aamnahid said, go to the developer options (Tap 8 times in build number), and check OEM Unlock. Then reboot your phone normally then you can try and flash it.
Click to expand...
Click to collapse
Fabio, what else we can do if OEM lock is grayed out (not able to enable/disable)?

Related

"custom binary blocked by frp lock"

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?

Custom Binary Blocked By FRP Lock

I was trying to root my phone
odin failed and my phone showed "Custom Binary (Recovery): Blocked By FRP Lock"
I was following this video
https://www.youtube.com/watch?v=M8ji0yjf7IY
What went wrong ?
johngr77 said:
Probably you forgot to enable OEM unlock in developer options menu
Click to expand...
Click to collapse
I did that and I successfully installed the twrp file
Then the phone rebooted and now it is stuck in the Samsung logo !!
What should I do ?
look through this forum - i only put the answer on here yesterday
JUST FLASH with latest stock firmware.. 1st of all to get phone into main screen/ activation lock screeen
asadnow2k said:
JUST FLASH with latest stock firmware.. 1st of all to get phone into main screen/ activation lock screeen
Click to expand...
Click to collapse
I did that and its working again
But How can I root it now ?
I tried rooting it again the same way but it got stuck on logo screen again !
is there any alternative way to root it ?
HussainJH said:
I did that and its working again
But How can I root it now ?
I tried rooting it again the same way but it got stuck on logo screen again !
is there any alternative way to root it ?
Click to expand...
Click to collapse
you just install frimware latest one and activate it with ur google account. than oem unlock than flash with root via odin
Im having this issue with my phone i accidently ticked off the oem unlock in development settings I put the phone in download mode because thats the only mode i can get into (recovery and regular boot does not work) when I connect to pc now it shows up as usb serial device in ports or it shows up as samsung modem and odin wont flash the firmware
I never had any issue. You get a single recovery.IMG and flash it. The s6e+ is tricky. You should have a custom ROM or what you want to flash ready and just flash twrp, boot immediately into it. Backup phone via twrp then wipe it and flash custom ROM. This will ensure you don't get any real issues or fpr blocked. Also use XDA tuts or get help here, YouTube can go good or bad. Recovery images are device specific. If you have f and flash t it won't work. You have to really look at what you are flashing and match model information. I'm seeing a lot of people fpr blocked and in trouble. I might go make a little walkthrough

unlock bootloader SM-G901F DTM

I am looking for a way to unlock the bootloader on my Samsung Galaxy S5 Plus (Sm-g901f, kccat6) with German t-Mobile branding (DTM) in order to flash Lineageos on it.
Is there a known way (executable for a newbie in Android flashing)?
Unfortunately my handset does not have a "OEM unlock" button in the developer options.
Is it possible to verify if the bootloader is locked apart from flashing a custom recovery and checking if it has been installed persistently?
i think you just have to flash twrp. if i remmeber correctly i had the same message that my bootloader was locked with my s4 i9506 back then
k2828 said:
i think you just have to flash twrp. if i remmeber correctly i had the same message that my bootloader was locked with my s4 i9506 back then
Click to expand...
Click to collapse
Even though my answer was posted a month ago, I want to present my solution:
As I said above, flashing TWRP did not worked on the way that all installation guides told me. But not because my bootloader was locked, the reason seems to be a bug (or is it a feature ) in TWRP.
The problem was, that the Stock OS is overwriting the bootloader on the first normal start.
What you have to do in order to prevent this mechanism:
1. Uncheck Auto-Reboot in Odin.
2. After Odin shows "PASS" shut your phone down and reboot it manually to the recovery.
3. In TWRP select Reboot and then System.
4. Done.
Now I am a lucky user of a LineageOS powered phone.
ooo yes thats a common odin bug for some phones..
dial25and said:
Even though my answer was posted a month ago, I want to present my solution:
As I said above, flashing TWRP did not worked on the way that all installation guides told me. But not because my bootloader was locked, the reason seems to be a bug (or is it a feature ) in TWRP.
The problem was, that the Stock OS is overwriting the bootloader on the first normal start.
What you have to do in order to prevent this mechanism:
1. Uncheck Auto-Reboot in Odin.
2. After Odin shows "PASS" shut your phone down and reboot it manually to the recovery.
3. In TWRP select Reboot and then System.
4. Done.
Now I am a lucky user of a LineageOS powered phone.
Click to expand...
Click to collapse
Why to shut down ?
When Odin passed !
Press download mode command keys
When screen goes black
Immediately press recovery commands !
And if u failed to reboot to recovery,flash firmware with nand erase all option !
As i experienced this issue!

Samsung A3 2016 won't boot, OEM unlocked > disabled

Hi,
So I rooted this device successfully but with my dumb head I apparently disabled OEM unlock.
Now my device is not booting. It only shows the samsung logo. I can go to download mode and android recovery.
I already tried:
- Wipe data
- Install stock firmware using Odin
- Install TWRP using Odin
None of this worked. It gives errows like "Custom binary blocked by FRP"
How can I possibly turn on the OEM while Im unable to go into Android?
Michelium said:
Hi,
So I rooted this device successfully but with my dumb head I apparently disabled OEM unlock.
Now my device is not booting. It only shows the samsung logo. I can go to download mode and android recovery.
I already tried:
- Wipe data
- Install stock firmware using Odin
- Install TWRP using Odin
None of this worked. It gives errows like "Custom binary blocked by FRP"
How can I possibly turn on the OEM while Im unable to go into Android?
Click to expand...
Click to collapse
I've found the solution for this problem. Thanks anyways.
Michelium said:
I've found the solution for this problem. Thanks anyways.
Click to expand...
Click to collapse
What was the solution?
i have the exactly same problem.

Is there anyway to Root a Galaxy S7 (SM-G930P) that has 8.0 on it?

I normally do the research myself and finally after a week i give up and can't find any sure way to do it. I've tried some stuff on Odin but get a fail message. I've rooted other phones before using Odin years ago, but this phone has been giving me lots of trouble. I have a Galaxy S7 with boost mobile. IT's a SM-G930P and awhile ago i updated it to 8.0 when it came out. Is there any way i can get TWRP on it or just anything at all?
Have you made sure FRP lock is disabled by ensuring enable OEM unlock is enabled in developer options in the phone settings? That will block flashing custom binaries (files) to the phone via ODIN download mode.
Steps below require factory resetting your phone so backup your data if you need to in advance.
I root most Samsungs with the following steps:
- Tap Build Number 7 times in settings > about phone > software info > build number to unhide developer options
- Enable OEM unlocking
- Reboot to download mode
- Flash TWRP custom recovery via ODIN that is compatible with your device and Nougat / Oreo
- Boot custom recovery, flash no-verity-opt-encrypt-6.0.zip, factory reset phone (optionally format data partition)
- Install / flash the SuperSU (version SR3 for example) via TWRP recovery to root your phone.
- Reboot phone and wait.
benjamen50 said:
Have you made sure FRP lock is disabled by ensuring enable OEM unlock is enabled in developer options in the phone settings? That will block flashing custom binaries (files) to the phone via ODIN download mode.
Steps below require factory resetting your phone so backup your data if you need to in advance.
I root most Samsungs with the following steps:
- Tap Build Number 7 times in settings > about phone > software info > build number to unhide developer options
- Enable OEM unlocking
- Reboot to download mode
- Flash TWRP custom recovery via ODIN that is compatible with your device and Nougat / Oreo
- Boot custom recovery, flash no-verity-opt-encrypt-6.0.zip, factory reset phone (optionally format data partition)
- Install / flash the SuperSU (version SR3 for example) via TWRP recovery to root your phone.
- Reboot phone and wait.
Click to expand...
Click to collapse
Thanks for the response. I think the issue from what i read is that TWRP can't be put on the SM-G930P, something about the bootloader being locked. I tried another method on here and had to end up wiping my phone since it bricked. It looks like my type of phone can't be rooted from the methods i've seen on here.

Categories

Resources