I've switch on the Reactivation Lock. My phone is rooted and in the reboot options I've selected reboot to recovery.
Now the phone is in a loop trying to enter in recovery and giving the activation lock warning.
I think that the problem is that the reboot to recovery option is always forcing to enter in recovery and the Reactivation Lock don't allow this.
Does anybody know a way to force to boot in the system to disable the reactivation lock? I can't believe that nobody had reboot to recovery by mistake without disabling Reactivation Lock previously.
JmJ17 said:
I've switch on the Reactivation Lock. My phone is rooted and in the reboot options I've selected reboot to recovery.
Now the phone is in a loop trying to enter in recovery and giving the activation lock warning.
I think that the problem is that the reboot to recovery option is always forcing to enter in recovery and the Reactivation Lock don't allow this.
Does anybody know a way to force to boot in the system to disable the reactivation lock? I can't believe that nobody had reboot to recovery by mistake without disabling Reactivation Lock previously.
Click to expand...
Click to collapse
I reply myself. I've found a solution, perhaps could be usefult for other user:
I've tried to flash a recovery with Odin. Obviously it fails because the Reactivation Lock, but when you reboot the phone, it boots to system and now it's possible to deactivate it.
The option Reactivation is useful but it's importan to take care.
JmJ17 said:
I reply myself. I've found a solution, perhaps could be usefult for other user:
I've tried to flash a recovery with Odin. Obviously it fails because the Reactivation Lock, but when you reboot the phone, it boots to system and now it's possible to deactivate it.
The option Reactivation is useful but it's importan to take care.
Click to expand...
Click to collapse
Great stuff man, big thanks, thought I'd screwed my phone. but this worked for me too
Related
Ok, this is my first dev device and I don't want to screw it up.
But, now I screwed up. I was SO comfortable running a new ROM that I messed around and checked on Reactivation Lock.
But then, I got a wild hair to try the TouchWiz 4x5 launcher instead of Nova and booted into Recovery to flash it in.
Now, I get "Custom binary blocked by Reactivation Lock"
Crap Crap Crap....
I've looked at several threads about how to boot or flash to fix, but the solutions seem ambiguous at best.
My biggest fear is that I am running a dev device and I don't want to get the wrong firmware and end up flashing in a retail bootloader or something.
Please Help!
I've tried pulling the battery, booting in download mode but neither of those work.
Rickinsav said:
Ok, this is my first dev device and I don't want to screw it up.
But, now I screwed up. I was SO comfortable running a new ROM that I messed around and checked on Reactivation Lock.
But then, I got a wild hair to try the TouchWiz 4x5 launcher instead of Nova and booted into Recovery to flash it in.
Now, I get "Custom binary blocked by Reactivation Lock"
Crap Crap Crap....
I've looked at several threads about how to boot or flash to fix, but the solutions seem ambiguous at best.
My biggest fear is that I am running a dev device and I don't want to get the wrong firmware and end up flashing in a retail bootloader or something.
Please Help!
I've tried pulling the battery, booting in download mode but neither of those work.
Click to expand...
Click to collapse
I've got reactivation lock enabled and haven't had any issues.
Ok..
When did you get the "Custom Binary blocked......" message? After booting into recovery? After flashing the file? What recovery?
When does the message appear? After the Samsung splash screen? After the boot animation? After the device boots completely?
MrHyde03 said:
I've got reactivation lock enabled and haven't had any issues.
Ok..
When did you get the "Custom Binary blocked......" message? After booting into recovery? After flashing the file? What recovery?
When does the message appear? After the Samsung splash screen? After the boot animation? After the device boots completely?
Click to expand...
Click to collapse
Sorry, I could have been more detailed to save this.
The S5 has TWRP for recovery (2.7.0 I think). I downloaded TouchWiz4x5.zip and restarted into recovery via QuickBoot app.
When the phone starts, I get the familiar Samsung logo, S5 Custom Android screen, not boot animation. It displays for about 2 seconds and then up in the top left it reads:
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Then displays:
Custom binary blocked by Reactivation Lock
SECURE FAIL: RECOVERY
...and goes no further. This whole boot process takes like three or four seconds from power on to yellow triangle ( I call it the ROMuda triangle lol)
I was thinking if I could force the boot loader to boot normally instead of into recovery all would be fine. It's getting hung on TWRP recovery. Then I could turn RL off. Some of the threads with similar errors have SECURE FAIL: KERNEL, which is not what I'm dealing with. The kernel and firmware are fine.
If I do have to return to stock, then I need to make damn sure that I'm flashing a dev edition so I don't end up with a retail version and locked boot loader.
Rickinsav said:
Sorry, I could have been more detailed to save this.
The S5 has TWRP for recovery (2.7.0 I think). I downloaded TouchWiz4x5.zip and restarted into recovery via QuickBoot app.
When the phone starts, I get the familiar Samsung logo, S5 Custom Android screen, not boot animation. It displays for about 2 seconds and then up in the top left it reads:
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Then displays:
Custom binary blocked by Reactivation Lock
SECURE FAIL: RECOVERY
...and goes no further. This whole boot process takes like three or four seconds from power on to yellow triangle ( I call it the ROMuda triangle lol)
I was thinking if I could force the boot loader to boot normally instead of into recovery all would be fine. It's getting hung on TWRP recovery. Then I could turn RL off. Some of the threads with similar errors have SECURE FAIL: KERNEL, which is not what I'm dealing with. The kernel and firmware are fine.
If I do have to return to stock, then I need to make damn sure that I'm flashing a dev edition so I don't end up with a retail version and locked boot loader.
Click to expand...
Click to collapse
Sounds like reactivation lock flagged your custom recovery. Can you get into Download mode? Start your phone like your trying to load Download mode. When you get the screen for Vol UP or Vol Down for continue or reboot, select reboot and see if it lets you boot up. If it does, then disable reactivation lock.
If it still won't boot, you should try flashing your stock recovery via ODIN. Hopefully you've made backup copies as there are no official firmware packages for the DevEd. Alternatively, you could ask another DevEd user to give you a copy of their recovery.
Have a look at this thread: [ODIN-RESTORE] [GS5-DEV Edition] Flashable Rescue package
MrHyde03 said:
Sounds like reactivation lock flagged your custom recovery. Can you get into Download mode? Start your phone like your trying to load Download mode. When you get the screen for Vol UP or Vol Down for continue or reboot, select reboot and see if it lets you boot up. If it does, then disable reactivation lock.
If it still won't boot, you should try flashing your stock recovery via ODIN. Hopefully you've made backup copies as there are no official firmware packages for the DevEd. Alternatively, you could ask another DevEd user to give you a copy of their recovery.
Have a look at this thread: [ODIN-RESTORE] [GS5-DEV Edition] Flashable Rescue package
Click to expand...
Click to collapse
Hyde, the link for the rescue package is dead. I did make a full backup with TWRP but don't know how to use it to flash via Odin.
TWRP doesn't backup the recovery. You may need to send a PM to one of the other users who have DevEd.
FIXED!!!
Just wanted to follow up to let everyone know that I have fixed the "Custom binary blocked by Reactivation Lock" error that had bricked my device.
I downloaded the recovery file (I'll update with a link to this file)
I flashed with Odin 3.0.7 (PDA)
It FAILED. (I expected this)
I unplugged USB, pulled the battery out
I put it back in, booted into stock recovery with Power + vol down.
Selected Normal Boot
Everything Fine!
Went to settings and turned off RL. LOL
Restarted Phone with normal Power Off menu - still fine
After reboot, opened SuperSU, still showed QuickBoot with root access
Opened QuickBoot, tapped on Recovery
It booted into TWRP (I'm on 2.7.0.0) - no problems
Rebooted again. No more error when booting to custom recovery
Profit!!!
** the battery pull trick after Odin flash fail I picked up from the Note 3 forums **
** If you have SECURE FAIL: KERNEL, you may need to perform a factory reset during the first boot after battery pull! **
A big thanks to all those who helped me via the forums and PM!
Hi,
Please help.
Samsung Galaxy S 5 SM900F
After installing new ROM all was well. Decided to try new ROM. Used power button to reboot to recovery.
At this point I see notification that recovery mode is locked by Reactivation Lock. When I press power button it restarts back to recovery mode with Reactivation Lock information again.
At the moment I'm in a loop. I cant turn the phone on because it always goes to recovery mode. I can still go to Download Mode but as Reactivation Lock is ON I cant do anything.
I would like either boot to normal system or install different ROM or use backup stored on SD card.
Is it bricked?
Thank you
Urgent.
Smartphone is protected by pattern. How to disable reactivation lock without erasing data?!
Normally I flash TWRP recovery and I delete gesture.key but this time Reactivation Lock is ON.
Need help.
ok brother
daxx75 said:
Urgent.
Smartphone is protected by pattern. How to disable reactivation lock without erasing data?!
Normally I flash TWRP recovery and I delete gesture.key but this time Reactivation Lock is ON.
Need help.
Click to expand...
Click to collapse
gave me pic abut your problem
i am trying to flash twrp 3.0 on a samsung j500fn in odin, but when i press start, i get a msg on the phone:
custom recovery blocked by frp lock
At this time i havent anabled OEM unlock yet, is that the problem?
What can i do? I read stories of people flashing twrp and after that it won't boot anymore, with the same message?
sander815 said:
i am trying to flash twrp 3.0 on a samsung j500fn in odin, but when i press start, i get a msg on the phone:
custom recovery blocked by frp lock
At this time i havent anabled OEM unlock yet, is that the problem?
What can i do? I read stories of people flashing twrp and after that it won't boot anymore, with the same message?
Click to expand...
Click to collapse
You forgot to enable OEM unlock, now you have to flash stock rom using odin, and do it again, this time don't forget to enable OEM unlock, how are you going to mess around with your system, when you forgot to unlock bootloader when rooting?
no, i am still in download mode on the samsung. Flashing twrp just didn't work. Phone is still working ok. I am just getting this msg when i am trying to flash twrp with Odin.
/
You need to enable OEM unlock and than reflash TWRP in Odin disable auto rebot in option after finishing insert your baterry.
Hey. I tried to root my phone with CF Auto Root but it stuck with the Samsung Logo (no bootloop, just stuck there). I managed to restart it. But when I went to the Download Mode I saw a blue screen with a "!" in a yellow warning sign and the line "no command". Then I am in the stock recovery mode.
The system dont allow OTA because I modified the system. I dont have a problem with that, but I need to get into the download mode to flash TWRP.
p.s.: When I am in the stock recovery mode I tried to "boot into bootloader", but it didnt work.
Ok, I give up on android. I just tried it two more times and suddenly all worked fine. DAFUQ?!?!!?
Edit: Ok, I always get the message "Custom Binary blocked by FAP Lock".
What does this mean? It blocks my acces to TWRP. Also I cant flash things with download mode.
Rookie1919 said:
Ok, I give up on android. I just tried it two more times and suddenly all worked fine. DAFUQ?!?!!?
Edit: Ok, I always get the message "Custom Binary blocked by FAP Lock".
What does this mean? It blocks my acces to TWRP. Also I cant flash things with download mode.
Click to expand...
Click to collapse
I usually heard about an FPR lock message but FAP lock is the first time (samsung really needs to rename that one :laugh: ) anyway , FRP lock happens if you forgot to enable OEM unlock in dev option before trying anything on your phone so if you can access download mode reflash stock firmware and do all the process again otherwise you'll need someone more experienced of me but I'm afraid that if you can't access download mode you're in a bad situation..
If you want to be helped in a better way provide more info about your phone for example wich model you have got, wich firmware were you on before all of this happened and so on
Hope you'll find a solution!
Ok, I managed to reset it. I use the G935F with Exynos. But now I have another problem: The CF-autoroot AND the TWRP make my phone stuck in the Samsung Boot Logo (no bootloop, just stuck). DAFUQ? Why?
Rookie1919 said:
Ok, I managed to reset it. I use the G935F with Exynos. But now I have another problem: The CF-autoroot AND the TWRP make my phone stuck in the Samsung Boot Logo (no bootloop, just stuck). DAFUQ? Why?
Click to expand...
Click to collapse
It might be necessary to wipe data maybe? In TWRP --> wipe --> format data --> type yes and reboot but be carefull, I didn't use this autoroot since I prefer the "standard way" so make sure you have a backup! Ah, and leave it at least 5 mins at boot logo.. mine takes that much to boot after every flash
Thx, Format Data worked. Now I´m fine.