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/
Related
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
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 .
Hello,
I recently flashed CWM for my device but had Reactivation lock on so I cannot boot my device because the binary counter is custom. I think if I flashed the stock recovery.img (NK7 build) I should be fine and wont lose any of my info on my phone. Is this the case and if so anyone know of any faster downloads than sam mobile?
I though Knox counter was only for guarranty purposes, didnt know it could block your device
Sent from my Galaxy NOTE 4
Well lesson learned, DONT KEEP reactivation lock set to on. I was only able to find a MD5 file for the whole restore, though I may be able to break it up.
Was able to fix it by extracting the tar.md5 file, but my device is trying to boot into recovery and that wont work because there is something wrong with chainfire's root method. My recovery will never load and at this point I dont think I can flash a custom one, full restore is only option. If that works...fingers crossed.
final fix was just doing full odin restore....weird I kept all of my data?
zhable said:
Well lesson learned, DONT KEEP reactivation lock set to on. I was only able to find a MD5 file for the whole restore, though I may be able to break it up.
Click to expand...
Click to collapse
Where is the reactivation lock?
Ita under settings -> security -> reactivation lock. Note i was able to flash the stock recovery.img but due to something with chainfires root method it messes up stock recovery. So i was stuck in a recovery bootloop.
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
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.