Database Users

Reactivation lock wont turn on

Hello,
i just got my note 4 yesterday and i have rooted the device using chainfire. when i try to turn on the Reactivation Lock, the checkbox does not checked
any help would be appreciated

If you have flash custom recovery Reactivation Lock not work!

i have flashed custom kernel which is cf auto root. i still have stock recovery but getting "dm-verity verification failed...."
EDIT: after reboot. i can enable reactivation lock. really strange.

I also had rooted my device and knox was not working anymore...
I updated with Samsung kies on my computer (to latest firmware)and now it's working again and stock again.
I wait for android 5.0 because i rooted for my sd card and es explorer.
And annoying advertise
Sent from my SM-N910C using XDA Free mobile app

Personally I wouldn't enable reactivation lock as I think it would make it much harder to recover your phone should it get bricked (you can't flash in ODIN mode until it is disabled afaik).
Also, if you install a custom recovery, reactivation lock is useless, as the recovery can be used to bypass it.

Help - Custom Binary Block By Reactivation Lock

I recently flashed the Xtresolite S5 ROM and I didn't realise that Reactivation Lock was turned on, now I clicked restart and then clicked recovery, but now every time I try to start my phone it shows "Custom Binary Block By Reactivation Lock" and "SECURE FAIL: RECOVERY". How can I fix this? Model: Samsung Galaxy S5 SM-G900F.
EDIT: I managed to get out of the error that wouldn't let me boot into my phone, but how do I remove reactivation lock as I've tried, but it does not show up in security. My Baseband version is G900FXXU1BOI3. I don't know if its changed when I flashed the ROM. Please note that the network I am using is Tesco Mobile and that the phone is unlocked.

Flash a stock KitKat ROM, log into all accounts, disable Reactivation lock, then flash whatever you want after that

*Detection* said:
Flash a stock KitKat ROM, log into all accounts, disable Reactivation lock, then flash whatever you want after that
Click to expand...
Click to collapse
I flashed the original lollipop touch wiz, but now my root is gone and I cant disable the reactivation lock. Furthermore my stock ROM do you mean a stock touch wiz ROM?

Also Odin fails to root my phone and flash a recovery, am I ****ed?

I highlighted the word KitKat for a reason

*Detection* said:
I highlighted the word KitKat for a reason
Click to expand...
Click to collapse
Flash a stock Samsung KitKat ROM and it is stuck in boot loop.

How long did you wait for first boot? It can take a long time
Flash it again, boot to recovery, factory reset and clear caches, reboot
---------- Post added at 09:30 ---------- Previous post was at 09:01 ----------
If it boot loops again after trying the above, flash the PIT file at the same time as the ROM, add it to the PIT section in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091

That helps?
https://www.youtube.com/watch?v=OCZpUcnp6Cc
-
https://www.youtube.com/watch?v=UdH56pUZAY8
-
http://myandroid.nl/reactivation-lock-solution-for-galaxy-s5/

REACTIVATION LOCK(KK): ON and Galaxy S5 is stuck on boot screen. How can I flash now?

Hi guys,
I rooted my S5 (SM-G900F) then afterwards I enabled my KNOX security on. Later I had to restart my phone and it got stuck in boot screen. Therefore, I thought to re-flash the device again but since "REACTIVATION LOCK(KK): ON" is preventing me to flash anything to the device. Any developer or knowledgeable person can help me with this situation?
Thank you in advance.

You have to flash KK rom then disable reactivation lock.
tapatalked

rajman said:
You have to flash KK rom then disable reactivation lock.
tapatalked
Click to expand...
Click to collapse
Thanks for the suggestion.
What I did to get my phone working was flash the stock ROM through Samsung Kies > Tools > Firmware Upgrade and Initialization option. It seems that when reactivation lock is enabled then only Samsung Stock ROM/s can be flashed only to the device.

custom binary blocked by reactivation lock

I have a Samsung Galaxy S5 SM-G900F when installing a new custom ROM I accepted the reactivation lock. The problem is that when trying to disable the lock reactivation occurs FC settings. And unfortunately I can not access the account Samsung on phone because is not installed
I can not go into recovery mode as the following message appears custom binary blocked by reactivation lock. Secure Fail: Recovery
I've read several threads here the forums but none solved the problem. It only remains to try for odin installing a stock rom Kit Kat I'm downloading it but very slow ...
If anyone can help me solve this problem ... And I apologize for bad English

Stock KK ROM is the only way

*Detection* said:
Stock KK ROM is the only way
Click to expand...
Click to collapse
Thank you. The download is almost over and then test. After confirm whether resulted or if I need some more help

[Fixed] [T580] Custom binary blocked by frp lock

Update:
For anyone who got the same problem as me:
Flash the exact same stock rom with odin (bl, ap, csc not csc_home).
---------------------------------------------------------
Hello,
So i made a mistake to turn off the developer options and i think by that also oem unlock, and on a restart i got Custom binary blocked by frp lock.
What are my options now in 2022 also is it possible to complety remove the Custom binary blocked by frp lock so i wont happen again in the future?
I still got the stock recovery because twrp wont mount anything but i think that is because i needed to flash the dm_verify zip to make that happen so i stayed with stock recovery and patched it with magisk.
I can boot in to the stock recovery and i can boot into downloader mode.
Hope someone can help me with this.
Info:
Samsung Galaxy Tab A 2016 (SM-T580)
Rom: T580XXS5CTK1_T580PHN5CTK1
Android: 8.1.0 Stock samsung rom
Recovery: Stock
Magisk and Busybox installed

Let me see if I've got this right. Your post says you have a stock ROM and recovery but with Magisk installed. With full stock and no Magisk, all the FRP lock should do is require you to enter the Google Account login and password on first boot. So have you tried a factory reset in recovery to get rid of Magisk? Then once booted, you can turn Dev mode and OEM enable back on and go from there.

Hello, thank you for the reply
But it was a Custom binary blocked by frp lock so no google account frp lock.
But i got it fixed by just flashing the complete stock rom with odin and then flashed twrp 3.6.2 with dm_verify 6.1 zip.
So this thread can be closed.

Nixz89 said:
So this thread can be closed.
Click to expand...
Click to collapse
Thread closed.