Hi, I need help.
I can't boot into my phone because the custom binary has been blocked by Reactivation lock.
I know i need some kind of firmware or something, but I don't understand what it is i need specifically and how i fix this problem.
Thanks
So I bought a new phone. Thanks for all the help anyway. Takes long enough. Someone can lock this. I don't care.
Related
Hi everyone.
I wanted to root my device and it didn't work, allways got Auth fail recovery on odin and device, until I unchecked the reactivation lock, then it rooted flawlessly.
(I know my google account and password)
I was curious is it safe to stay with reactivation lock checked in case this happens:
Lets say the soft bricks into a boot loop who knows why but recovery still works.. so if I want to factory reset from custom recovery(philz recovery, with Nandroid and efs backed up), I think it is the best to unroot before factory reset(hope I'm wrong), witch will be imposible if the root didn't worked because of the reactivation lock, the unroot won't work too?
I gues before trying any flashing etc is good to uncheck reactivation lock, but I can allways make a mistake and forget it on.
So let me make that short, is it safe to activate ractivation lock when rooted in case something bad happens with the boot start?
I want to activate it for safety but this safety could block me too?
Do you guys keep it on after rooting?
I hope the readers will understand my question and don't get any headakes, sometimes I gould it hard to express myself in english, sorry about that.
alexpu1u said:
So let me make that short, is it safe to activate ractivation lock when rooted in case something bad happens with the boot start?
Click to expand...
Click to collapse
Well reactivation lock is an anti-theft feature. Theft deterrents are good although they only have significant value when they are well implemented. Which is arguable in this case. It's hardly undefeatable. 2 strikes. And can be as annoying as hell in not liking your custom kernel. Strike thr ...
Bottom line, if you are good at making backups and believe in theft deterrents, then enable it. It makes it slightly more likely that a lost phone would make it back to you. Or at least ruin the thief's day. There should always be a way to restore your device if you have a backup and your credentials.
However if you are forgetful, bad with backups or simply have no patience for having to search XDA threads or enter something on a command line to disable reactivation lock and recover from a bootloop, etc.. then obviously don't use it. It could cause you some exasperation if you are in an unbootable state and it is interferring with an Odin flash.
Pick one. And either way try not to lose your phone.
.
That's what I wanted to hear, so it's safe to keep it on if I'm backedup and pacient in case of a problem.
Thank you for your time. I activated it .
alexpu1u said:
That's what I wanted to hear, so it's safe to keep it on if I'm backedup and pacient in case of a problem.
Thank you for your time. I activated it .
Click to expand...
Click to collapse
Well, I'm not concerned with being locked out of my phone permanently. Nor convinced that RA would really stop a stolen phone from being reactivated. But it's plausible that it would delay some thieves from using Odin to obliterate your tracking software.
So a longer window in which it might be possible to pin down your phone's location. Or perhaps spur someone to return your phone in the case of a lost, rather than stolen phone.
Whether to use RA depends mostly on your willingness to put up with some temporary frustration should your phone somehow end up unbootable and you have to jump through a few hoops to disable the reactivation lock.
.
alexpu1u said:
Hi everyone.
I wanted to root my device and it didn't work, allways got Auth fail recovery on odin and device, until I unchecked the reactivation lock, then it rooted flawlessly...
Click to expand...
Click to collapse
But you can't enable this option after root, it does not work!
knox 0x1 (2)
jgfernog said:
But you can't enable this option after root, it does not work!
Click to expand...
Click to collapse
interesting finding from me:
even if you are not root, with samsung knox 0x1 (2) the option is automatically enabled but you won't see it ticked. You can factory reset your phone when you have knox 0x1 (2) and see it will ask for reactivation account in order to by pass the phone. There is no solution. Samsung knox is funny.
MaXi32 said:
interesting finding from me:
even if you are not root, with samsung knox 0x1 (2) the option is automatically enabled but you won't see it ticked. You can factory reset your phone when you have knox 0x1 (2) and see it will ask for reactivation account in order to by pass the phone. There is no solution. Samsung knox is funny.
Click to expand...
Click to collapse
Yeah! There are some problems with it. I saw people saying that their devices had KNOX enabled even with the option unchecked in settings.
I wouldn't bother with reactivation lock for any scenario
1. Easy to bypass
2. Only causes problems for yourself if you forget to disable it before flashing
3. Anyone who knows how to flash a new ROM, which is what it's designed to prevent, can bypass it flashing a KitKat ROM anyway
4. You've lost your phone anyway, they're not gonna give it back because they can't use it
Hi all,
I was wondering if I'd still be able to use the reactivation lock after rooting my note 4?
As in: If the phone is rooted (using stock recovery) and a factory reset is preformed from bootloader, will the OS prompt to enter the Samsung Account credentials?
Found the following topic, but it did not make things clear:
http://forum.xda-developers.com/note-4/help/reactivation-lock-root-t3004321
The model that I'm using: SM-N910F.
Kind regards, Stefan.
Anyone?
Thaevil0ne said:
Anyone?
Click to expand...
Click to collapse
Bump.
Thaevil0ne said:
Hi all,
I was wondering if I'd still be able to use the reactivation lock after rooting my note 4?
As in: If the phone is rooted (using stock recovery) and a factory reset is preformed from bootloader, will the OS prompt to enter the Samsung Account credentials?
Found the following topic, but it did not make things clear:
http://forum.xda-developers.com/note-4/help/reactivation-lock-root-t3004321
The model that I'm using: SM-N910F.
Kind regards, Stefan.
Click to expand...
Click to collapse
I m not sure but it's like this, u can't root if your phone reactivation is on & once u root without reactivation, u can't activate reactivation.
jdomadia said:
I m not sure but it's like this, u can't root if your phone reactivation is on & once u root without reactivation, u can't activate reactivation.
Click to expand...
Click to collapse
Thanks for your reply, I will not be rooting this phone then.
I would mainly be rooting to be able to use the Moga universal driver for my controller.
But the reactivation lock is really a neat feature that I would not want to lose.
Kind regards, Stefan.
Reactivation Lock
I can confirm (at least with your request having been put in layman's terms!!) that no, the reactivation lock does........NOT work after rooting!
dang. I could swear that after rooting my Note 4 n910G, reactivation lock still works. im positive about it. I did it a few times, checking n unchecking it. But i got sick of Odin errors because of having Reactivation Lock on that i just left it unchecked for then on & havent touched it since. I donr even know how important a feature it is.
Hi to everyone. I have a problem with my phone
When I try to open my phone, Writing custom binary blocked by fap and don't opening. Closing by it self. My problem is not FRP lock is FAP lock.
I didn't root my phone, I didn't do nothing illegal. My battery finished and when I put to charge It's did like that.
How I can fix it guys? I can't open my phone
My phone is: Samsung Galaxy S6 Edge Plus - SM-G928C
I solved it. I flashed a rom and FRP lock unlocked but now I have this problem
dm-verity verification failed.
Need to check DRK first...
Really I'm tired about it. Some one can help me?
No one help me?
kaderimse_24 said:
No one help me?
Click to expand...
Click to collapse
i did mine stuck in a loop, used smart switch
zmaczac said:
i did mine stuck in a loop, used smart switch
Click to expand...
Click to collapse
I used that. But I can not use Emergency Recovery because I don't have a recovery code. And my phone don't coming in the list below.
I used Software Update and Restart but the same problem.
Hi all,
Don't know if I'm in the correct place for this question, but here goes. I've been lurking for a while now and have become interested in the bootloader exploit that has recently been discovered for our phones. I read that reactivation lock needs to be disabled before you follow the unlock procedure. When I try to disable my reactivation lock in settings / security, I get an "Unfortunately, Settings has stopped" dialogue. I'm on CVertigo 1's BS_FREE_Lollopop_5.0 which has Samsung account info removed. Would I need to flash a different 5.0 rom that has Samsung account info, and then disable reactivation lock prior to following the bootloader unlock guide?
Thanks for all you do.
yes
Hello, I have a Galaxy S5 G900F, updated to Marshmallow 6.0.1, being using it for a year now and it seems that I had the reactivation lock on for so long, but the samsung account associated with it was deleted by me a couple months ago.
A few days ago, a friend just as a stupid prank went into recovery mode and wiped my phone, and now i can't get it to work because of the reactivation lock. I cant sign in with my account because it no longer exists and I tried taking it in for service as it is still in warranty and the Knox is 0x0 and everything but they said that it says specifically on the device that before taking the device in for service you have to disable the reactivation lock. So they said that the only way i can get it to work is pay $200 for them to replace my motherboard. And i am not going to do that.
Can you please tell me if I can do something to force bypass or install another ROM or ANYTHING at all in order to get past the lock? I would greatly appreciate it. I don't care if i flag the Knox system, i just want my phone to work. I only have a medium level knowledge of installing custom ROMS, rooting and using ODIN i've been doing it on my old samsung S3 for a long time. Can you please please give me a tutorial or something i can do doesn't matter if it takes long or if it's complicated or risky as I have nothing to lose. Thank you so much!
Flash a stock KITKAT ROM
Boot into recovery, factory reset, see if you can get back in
Or Create that Samsung account with the same email address again, if it's been deleted, it should let you create it again, log back in with that