Database Users

[Q] Custom binary blocked by reactivation lock

Hi,
i've just finished the "root" into my Galaxy S5. I've tried to install a custom recovery through Kies but it fails.
Now, when trying to access the recovery, i get the following message:
Custom binary blocked by reactivation lock
Secure Fail: Recovery
Any idea/help?

SOLVED:
Just go to settings, Security and deactivate Reactivation!
SilvioMarco said:
Hi,
i've just finished the "root" into my Galaxy S5. I've tried to install a custom recovery through Kies but it fails.
Now, when trying to access the recovery, i get the following message:
Custom binary blocked by reactivation lock
Secure Fail: Recovery
Any idea/help?
Click to expand...
Click to collapse

how did u get past the error screen?
Im stuck on it right now

Glad you figured it out.
This isn't news though. Anyone who reads the forum a bit or did a search for reactivation lock would quickly find that it needs to be disabled before you can flash firmware. For anyone else who encounters this message, simply disable reactivation lock in the settings menu.
.

Custom binary blocked by reactivation lock.
This is the message I am getting after installing if I go to the TRWP boot (volume up, home and on/off button).
The phone is working normally 900F wit stock kernel, Cf root and TWRP recovery, I want to install some of the aroma package but I can't install right now.
I have no reactivation in the security menu?
Thanks and greetings,
Erik.

It's called the reactivation lock. To getvthee go to - Settings - System - Security.You have to scroll down the security menu to find it.
I flashed the twrp recovery using flashify from android itself. Flashify is in the play store.
Your lucky aftrr I tried flashing twrp my phone would not even go past the error seen.
---------- Post added at 11:36 PM ---------- Previous post was at 11:34 PM ----------
When I first tried flashing twrp using the twrp app. It worked first time on flashify.

How do you get it to boot? Mine won't go past the error screen

Flash stock KitKat > Log into all accounts > disable reactivation lock

I wasn't able to do anything including flash anything, but i took it to sprint and they fixed it. Now to reroot it. .

worse boat
whbisondtr said:
I wasn't able to do anything including flash anything, but i took it to sprint and they fixed it. Now to reroot it. .
Click to expand...
Click to collapse
i m in worse boat thn u i root n intalled xtroolite rom thn whn i want to go to recovery mod i m stuck in binary screen same as u m still finding my answer but cant get help

Juzer zoaib said:
i m in worse boat thn u i root n intalled xtroolite rom thn whn i want to go to recovery mod i m stuck in binary screen same as u m still finding my answer but cant get help
Click to expand...
Click to collapse
I think you can Odin the og1 tar file to fix it but it depends on the model. My suggestion is to take it to sprint. They didn't charge me anything either.

Juzer zoaib said:
i m in worse boat thn u i root n intalled xtroolite rom thn whn i want to go to recovery mod i m stuck in binary screen same as u m still finding my answer but cant get help
Click to expand...
Click to collapse
Already explained, boot to DOWNLOAD MODE (Not recovery)
Flash a KitKat Stock ROM with ODIN
Log into all accounts
Disable Reactivation lock

process stop
*Detection* said:
Already explained, boot to DOWNLOAD MODE (Not recovery)
Flash a KitKat Stock ROM with ODIN
Log into all accounts
Disable Reactivation lock
Click to expand...
Click to collapse
yes brother i did same but it is not working. now problem is the process is not working same thing coming again n again process stop everytime i donno.
i m trying.
i got some update doing it thn see what happens.

Juzer zoaib said:
yes brother i did same but it is not working. now problem is the process is not working same thing coming again n again process stop everytime i donno.
i m trying.
i got some update doing it thn see what happens.
Click to expand...
Click to collapse
After flashing the Stock KK ROM, boot into recovery and factory reset, then try and boot

[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 .

SM-G900F: Reactivation lock recovery

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

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/

Need help unbricking.

Yesterday I tried root my S8 (SM-G950FD) and I made the mistake of not allowing system modifications before flashing because I misinterpreted a guide. I flashed the no-verity zip and Magisk. The phone booted successfully and magisk was installed. Then I went to reboot into recovery to change some TWRP settings IE: Brightness. Then my phone said "Only officially released binaries are allowed to be flashed." That left me unable to boot my phone and also made it unable to boot into recovery. The only thing I can boot my phone into is download mode. I've tried flashing some stock roms that are 7.0 to remove the prenormal lock but they failed. I happened to make a TWRP backup before flashing but I can't use TWRP because of the official binary stuff. I'm wondering if I use the nand erase all option if that will let me flash the 7.0 stock roms then boot into TWRP and restore my backup or if they is way to convert the backup into something that Odin can flash. Does anybody know any confirmed methods to solve my problem?

Unbrick-me said:
Yesterday I tried root my S8 (SM-G950FD) and I made the mistake of not allowing system modifications before flashing because I misinterpreted a guide. I flashed the no-verity zip and Magisk. The phone booted successfully and magisk was installed. Then I went to reboot into recovery to change some TWRP settings IE: Brightness. Then my phone said "Only officially released binaries are allowed to be flashed." That left me unable to boot my phone and also made it unable to boot into recovery. The only thing I can boot my phone into is download mode. I've tried flashing some stock roms that are 7.0 to remove the prenormal lock but they failed. I happened to make a TWRP backup before flashing but I can't use TWRP because of the official binary stuff. I'm wondering if I use the nand erase all option if that will let me flash the 7.0 stock roms then boot into TWRP and restore my backup or if they is way to convert the backup into something that Odin can flash. Does anybody know any confirmed methods to solve my problem?
Click to expand...
Click to collapse
You will need to flash the same or higher version of Android to fix official binary error. Use default settings in Odin.
You cannot.flash earlier versions of Android if your bootloader is lower than what is on your phone ( 5th number from right of firmware name ). If in doubt flash the latest version.

Then I went to reboot
Click to expand...
Click to collapse
And i same problems "Only officially released binaries are allowed to be flashed"
---------- Post added at 10:31 PM ---------- Previous post was at 10:30 PM ----------
Then I went to reboot
Click to expand...
Click to collapse
And i same problems "Only officially released binaries are allowed to be flashed"

spawnlives said:
You will need to flash the same or higher version of Android to fix official binary error. Use default settings in Odin.
You cannot.flash earlier versions of Android if your bootloader is lower than what is on your phone ( 5th number from right of firmware name ). If in doubt flash the latest version.
Click to expand...
Click to collapse
Ok so in few minutes from now the rom will be finished downloading. When that is done what version of Odin should I use and what files should place in Odin. I know this may seem stupid to ask but I'm not going to let myself make anymore stupid decisions after not installing the rmm bypass.

Quick Update, the rom finished downloading. I wasn't able to flash it. It gave me the error that the Bootloader had: 4 and the binary had 3... I was able to flash cp by itself tho and that set the system status to samsung official but the binary status is still custom. That made it so my phone only booted into a "Update failed screen use smart switch" screen ( I've tried smart switch before it doesn't detect my device). I can still get it back into recovery and flash old cps to get it to turn off without bootlooping into the smart switch screen. I'm wondering if I flash csc to factory reset if that will help at all. Guys what do I do??

Excuse my language but I ****ING DID IT!!! I don't know this worked but I am going to roughly call my process. So flashing the stock rom initially failed. I flashed then CP which for some reason always works and then AP which began but failed. This set the binary text to "Samsung Official", system status was still ****ed as custom. So I restored the cp and ap(?) from the crgb oreo files posted here. Then I flashed cp that passed, then csc which passed and then tried AP. After some time... It passed. The phone rebooted. The official binary bull**** was gone from the bootscreen and the phone booted into recovery. It installed some sys update stuff up to 30$ then erased some things which took awhile. Then the phone booted into initial setup and I now have ACCESS TO MY PHONE AGAIN!!!
For anyone interested in what FW I flashed PM me.