Hi, after installing a custom rom, i just edited the Build number via Kenel Auditor to SM-G925I(as it was my actual model name) from SM-G925F . Before i enabled Reactivation Lock in settings menu.
After that i tried to restart the phone, now its showing "Custom Binary Blocked by Reactivation Lock" over the top of the logo, i can't enter recovery, only Bootloader Download mode is accessible, can't flash anything via Odin, it gives me error, what can i do now?
Help plz ! TIA :angel:
You can't use reactivation lock even with root.
You need to flash a fresh stock ROM.
Related
hello all
i have stock rom
just i root my device without recovery
super user need to update
i choose to update by recovery ( wrong choose )
then device just restart to samsung logo with this attention in the left upper corner
( recovery is not seandroid enforcing custom binary blocked by frp lock )
i cant do recovery
how can i fix without flash new rom
if i must flash new rom
plz give me stock and fast download to flash it via odin plz
thx all
my galaxy s5 sm-g900f is rooted and I have TWRP recovery mode. When I install rom manager(from play store) for bacukup rom(all settings in rom manager was ok) it reboot my phone into recovery mode and shows a message with alert icon........
custom binary blocked by reactivation lock
secure fail: recovery
I tried to fix this by removing battery but it still stuck on my phone whenever I power on my phone.... :crying:
NOTE THAT: USB DEBUGGING IS DISABLED
Please help me to fix this
miraz4300 said:
my galaxy s5 sm-g900f is rooted and I have TWRP recovery mode. When I install rom manager(from play store) for bacukup rom(all settings in rom manager was ok) it reboot my phone into recovery mode and shows a message with alert icon........
custom binary blocked by reactivation lock
secure fail: recovery
I tried to fix this by removing battery but it still stuck on my phone whenever I power on my phone.... :crying:
NOTE THAT: USB DEBUGGING IS DISABLED
Please help me to fix this
Click to expand...
Click to collapse
Greetings and welcome to assist. I'm not sure why you needed rom manager to back up your rom when twrp can do this ? Anyway it souns like you are being blocked by frp lock, you should be able to fix this by using kies to go back to stock then reinstall twrp
Good Luck
Sawdoctor
My phone is stuck on either download mode or custom binary blocked by frp can someone please help me ive been looking alot and have not have any succes at all my model number is SM-G530T1
I had the same issue few days before I didn't know what happened wrong but while restarting my phone after changing SIM it showed that custom binary is blocked by frp lock ,it even couldn't be charged. so what all I have to do was to download the official stock ROM for it and flash the stock ROM by Odin hope you had backup of your data, otherwise you will not get your data , so flash the correct ROM and it will be OK
my phone is stuck on the boot menu for three days it says custom binary blocked by frp lock . i tried downloading firmware from sammobile.com but it says error .
please help me. i am stuck bad.
I have rooted my phone J7 2015 India (J700F) with TWRP and SuperSU.
Literally followed the following tutorial: androidinfotech .com/2016/07/root-samsung-galaxy-j7-sm-j700f-601.html
But I locked custom ROM in Developer Option and forget to turn it off and switched off my phone.
Now, it is not booting and turn off in a few second displaying:
Custom binary blocked by frp lock
Click to expand...
Click to collapse
When I tried to boot TWRP recovery. It says:
Recovery is not seandroid enforcing
Custom binary blocked by frp lock
Click to expand...
Click to collapse
What should I do? Is there any easy option to fix this or Do i have to flash ROM?
Please consider me android noob.
Thanks in advance.
Hello,
I have fixed the issue by installing stock ROM downloaded from sammobile.com/firmwares/galaxy-j7/SM-J700F/
Using ODIN from https://odindownloader.com I reflashed the phone.
PS: As far as personal data is concerned it was intact as I had only rooted the phone and probably had the same OS before.