Samsung Reactivation Lock - Galaxy S 5 Q&A, Help & Troubleshooting

Recently I installed a Rom from here with the latest Lollipop, I will refrain from saying which one but I found it very buggy and unusable so I went to put back on my old Fav Omega..... thing is my phone now tells me the reactivation lock is enabled with any use of Odin a flash fails, now when I go into the security to "deactivate the lock" its already unticked, if I tick it it opens a screen to enter my Sammy password which I do, then it just goes back to the screen with the box still unticked for the reactivation, this is telling me its "stuck on" and I am unable to turn it off? any suggestions?

No ideas?

Related

phone bricked! frp lock.... solved!

so your phone doesnt boot and you have the s6 edge plus logo flashing your face with some red text in the upper corner saying fap lock something something
first things first. your phone does charge while in download mode, so get your ass into download mode by holding the power button, menu and down at the same time
1. plug your phone to charging stuff while you wait
figured that out my self after accedentally disabling the oem thingy and restarting with about 10% left of battery
what you absolutly need to do is to calm down and head over to sammobile and
2. get the correct stock rom for your phone
3. after downloading you need to unzip the file and flash it through the ap section of the odin software, once thats done you are good to go, the phone should start up as usual and you will have all your apps and stuff waiting for you, just with stock rom, stock bootloader and stock recovery, after that you should head over to the developer section and enable oem unlock
when thats done feel free to flash a custom recovery, rom etc...
just remember, never ever ever ever ever disable the oem unlock in developer mode if you have a custom binary
you could also use the smart switch software from samsung, fiy the serial number is on the back on your phone and is pritty hard to read and your model number can be found in the download mode

To start Android, enter your password

For some reason, this screen showed up asking for my password. The phone booted automatically because I set the clock, but it didn't ring and this screen showed up, causing me to be late for work. Any idea what it is? I don't even have a password set on this device.
did you install twrp?
No, I'm still waiting for an official bootloader unlock

Accidentally disabled OEM Unlocking on custom rom?

I was on android device manager and i clicked the button that said "enable lock and erase". After about a second, the buttons were enabled. Now, when i go into developer settings on the phone, OEM unlocking is turned off. Should I worry? I am running Pure Nexus (0802 build). The phone is still on and fully functional, and I have not rebooted it since. I have tried multiple times to re-enable oem unlocking in developer settings, it asks for my pin and after i put it in it stays off. Maybe my custom rom doesn't even have the code in it to mess with anything like that because it knows it is running on an unlocked bootloader? I went into google settings on the phone and unchecked the box that says enable erase and lock and now i am back to not being able to do it in android device manager.
That has nothing to do with it... with your bootloader unlocked that setting is disabled, that's normal. If you bootloader is unlocked, why would you need to enable "OEM Unlocking", it has no function now.

SM-T580 Boot looping with 'Custom Binary Blocked by FRP Lock'

So, put my son's SM-T580 on the charger last night, it was fine (he's been using it for months), woke up this morning to it boot looping. It will not get past the initial boot screen and has that annoying red text 'Custom Binary Blocked by FRP Lock' in the upper left corner. It will not boot recovery. I can only boot to the bootloader. Of course, I can't flash anything using ODIN because of the FRP lock. I'm thinking the only options I have is to try flash a stock ROM / Recovery back onto it and start over but I was wondering if anyone else has ever seen or heard of anything like this before I do that. Thanks.
UnZoner said:
So, put my son's SM-T580 on the charger last night, it was fine (he's been using it for months), woke up this morning to it boot looping. It will not get past the initial boot screen and has that annoying red text 'Custom Binary Blocked by FRP Lock' in the upper left corner. It will not boot recovery. I can only boot to the bootloader. Of course, I can't flash anything using ODIN because of the FRP lock. I'm thinking the only options I have is to try flash a stock ROM / Recovery back onto it and start over but I was wondering if anyone else has ever seen or heard of anything like this before I do that. Thanks.
Click to expand...
Click to collapse
The only thing that I can think of is that someone, somehow disabled the OEM Enable setting in /Developer options. This is what trigger the FRP lock.
You will need to hold Vol-, Home and Power buttons to boot to download mode and use Odin to flash a stock ROM. Then you will need your the Google Login and Password that is registered to the tablet. If you don't know those, you're in a heap of trouble.
As soon as you get stock up and running, the first thing to do is enable the developer options and make sure that OEM is enabled. After that you can flash TWRP and custom ROMS.
If you don't know the Google info, the tablet CAN be salvaged, but it is a complicated process.
lewmur said:
The only thing that I can think of is that someone, somehow disabled the OEM Enable setting in /Developer options. This is what trigger the FRP lock.
You will need to hold Vol-, Home and Power buttons to boot to download mode and use Odin to flash a stock ROM. Then you will need your the Google Login and Password that is registered to the tablet. If you don't know those, you're in a heap of trouble.
As soon as you get stock up and running, the first thing to do is enable the developer options and make sure that OEM is enabled. After that you can flash TWRP and custom ROMS.
If you don't know the Google info, the tablet CAN be salvaged, but it is a complicated process.
Click to expand...
Click to collapse
This is what I was afraid of. It is my sons tablet so I have all his Google info. I would not be surprised if he somehow reset the developer options. He'll lose some of his game progress but that's nothing compared to losing the whole tablet. Thanks for the reply. Off to download a stock rom and start over.

"Custom binary blocked by FRP Lock" when rebooting after flashing custom rom

So I've been trying to flash Ivan_Meler's LineageOS 19 zip with NikGApps Stock on my Galaxy S8+, and the setup went smoothly, however, when I restart the phone I am greeted with the "Galaxy S8 Powered by Android" splash screen along with red text at the top saying "Custom binary blocked by FRP Lock". The phone then powers off. When I turn the phone on, the same message appears, then turns the phone off. I can't access the system or the recovery, so I did some research, only to find that the only way was to reflash stock firmware through download mode, so I did.
I tried doing some more research, but I didn't find any resources on how to prevent this error from occurring in the first place (other than signing out of Google and deleting any screen locks on the stock firmware, which I already did). I've tried flashing the same rom three times, all with the same result.
Another detail I noticed: When I reboot the phone during the setup before I sign into my Google account, it works fine. Unfortunately, I need to sign into my Google account for personal use, so skipping signing in is not an option here.
What I'm asking is - is there any way to flash a custom rom with a Google account without that "Custom binary blocked by FRP Lock" error appearing on reboot?
Edit 1: I've done some more digging and it seems a possible reason for this error is that the OEM Unlock option has been disabled somehow. I will try tomorrow to verify that the OEM Unlock has been turned on after flashing.
Edit 2: Well the OEM Unlock option isn't there in the LineageOS developer tools. Figures since they probably assume your bootloader is already unlocked. I also tried using Zillinium's FRP Destroyer, but to no avail.
Edit 3: SOLUTION: Turns out using BitGApps instead of NikGApps Stock solves the problem.
Hy, I have got the same problem.
Which is the mistake?
Thanks for all

Categories

Resources