SM-G900F: Reactivation lock recovery - Galaxy S 5 Q&A, Help & Troubleshooting

Hi,
Tried to upgrade my S5 with latest Alliance rom from 5.1 to 5.5 version.
Followed all steps thrue ROM Customizer than this damn thing happened before the phone even got to recovery:
Custom binary blocked by Reactivation lock.
Secure fail: recovery
Tried searching but none of the solutions found are for this exact problem.
Can someone point in the right direction before things go wrong way?

Will flashing stock recovery from unified androit toolkit help?
Or it must be true Odin 3.09?

No solution worked for you? Try this...

You must have activated Reactivation Lock in the security section. Go there and un check it. It should ask for your reactivation password. Once you enter it, you should be good.
Swordfish - R750A Gear S, SM-G900W8 S5

Related

[Q] [Solved] Custom binary blocked by Reactivation Lock

Will / Can "Custom binary blocked by Reactivation Lock" be solved by:
1 flashing a Stock firmware by Odin?
or
2 flashing a PIT-file?
eRPeeX said:
Will / Can "Custom binary blocked by Reactivation Lock" be solved by:
1 flashing a Stock firmware by Odin?
or
2 flashing a PIT-file?
Click to expand...
Click to collapse
Try turning off Reactivation Lock.
sarbe said:
Try turning off Reactivation Lock.
Click to expand...
Click to collapse
If it was that simple I wouldn't have asked.
But I've downloaded stock firmware
Flashed it by Odin (got in a bootloop)
In recovery wiped data
Booted
Reinstalling all my apk's
Unticked reactivation Lock
And than up to NeatRom 2.2!
When you get stuck in a boot loop saying "Custom binary blocked by Reactivation Lock" you can solve this by trying to flash e.g. CFAutoRoot with Odin. This will fail. Then you take of the battery and after this you should be able to reboot normally without this message.
I found this solution here.
eRPeeX said:
If it was that simple I wouldn't have asked.
But I've downloaded stock firmware
Flashed it by Odin (got in a bootloop)
In recovery wiped data
Booted
Reinstalling all my apk's
Unticked reactivation Lock
And than up to NeatRom 2.2!
Click to expand...
Click to collapse
If you gave a more detailed question you would get a more detailed answer. There is no rom info, what you've tried etc. You will not get spoonfed here.
sarbe said:
If you gave a more detailed question you would get a more detailed answer. There is no rom info, what you've tried etc. You will not get spoonfed here.
Click to expand...
Click to collapse
I've got a problem. Had my phone since release, rooted + custom recovery.. haven't changed rom since. Must have activated the reactivation lock at some point, but forgotten all about it. The other day i was installing a mod in xposed and ended up in bootloop upon restarting my phone. Now i got the error in the op when i try to go into recovery, and well phone is in bootloop.. So im kinda in a limbo here, cant fix it since i cant get into recovery, and i cant deactivate since all i get is the samsung logo.
Any help would be greatly appreciated
jee82 said:
I've got a problem. Had my phone since release, rooted + custom recovery.. haven't changed rom since. Must have activated the reactivation lock at some point, but forgotten all about it. The other day i was installing a mod in xposed and ended up in bootloop upon restarting my phone. Now i got the error in the op when i try to go into recovery, and well phone is in bootloop.. So im kinda in a limbo here, cant fix it since i cant get into recovery, and i cant deactivate since all i get is the samsung logo.
Any help would be greatly appreciated
Click to expand...
Click to collapse
Nevermind figured it out. Used odin to flash stock firmware, booted up and deactivated that darned reactivation lock. Just glad I remembered the login and pass .

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.

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.

Categories

Resources