Phone is a n975f. Factory data reset it. Put in a Google account. Enabled developer mode. Has been 8 days. Why is OEM unlock still greyed out?
hello,
I had similar situation.. since you have already did factory reset, you might wanna try the following. Factory reset again, Do not add any account or connect to wifi.. set the date.. and then connect to Wifi.. Try going to the about and see if you can toggle the OEM unlocking
Good luck
Related
After trying too many unlock patterns i was locked out.I am now unable to use my google username and password since i cant access the wifi settings...Any pointers???????
it can because of security reasons try rebooting or factory reset will do the trick
androidisfuture said:
it can because of security reasons try rebooting or factory reset will do the trick
Click to expand...
Click to collapse
+1
Settings/Backup & reset/Factory data reset - not wipe data in bootloader!
How do I reset the passcode on a nexus 5 without doing a reset? I've tried logging into the google acconut, and I can use the "find" option in the device manager to locate the device, but if i press the "lock" button and try to enter a new password, for a split second it says "We have sent a lock request to the device", but then it says "Since Google has verified that a screen lock is already set, the password you entered won't be needed." Wtf is going on? Is there another way to reset the password?
I have not tried this and I do not know if it's updated for Lollipop, so use with caution.
This thread discusses how this can be accomplished if you have custom recovery installed or if USB debugging is enabled. If neither of those are true, you'll have to do a factory reset, there are no other options.
[the final word in the title should be the word "removed"].
My phone is a Rook G from EE (UK), which I understand to be just a carrier-branded ZTE Blade 3 A410. I need to wipe the phone and do a Factory Reset . But the phone has Factory Reset Protection, so I must remove this in order to proceed. I do this by removing all google accounts from the device. As a result, I can perform the factory reset from within the "Backup & Reset" section of "Settings".
However, if I boot into recovery (By holding Vol+ and Power simultaneously), then when I choose "Wipe data/Factory reset", the following line appears at the bottom of the screen:
"Frp have not wipe, factory reset failed".
And it doesn't seem that the device is factory reset. So my first question is: WHAT do I do to enable the Wipe data/factory reset feature from recovery?
[If you are wondering why I need to Factory Reset from Recovery, the answer is that I'm trying to unlock the bootloader. Now we know that the last step in unloking the boottloader is that the device is wiped back to Factory Reset state. I presume that this is accomplished by code which runs in the regular recovery partition.
What worries me substantially, therefore, is that if there is some problem which prevents Recovery from wiping the device clean, then it will not be possible to unlock the bootloader. I'm sorry to say that indeed I am not able right now to unlock the bootloader -- at the crucial moment when I would use the Volume key to confirm that I want to unlock, there seems to bea problem with what is happening: the phone screen stops responding, and in the end the procedure for unlocking the bootloader fails.
If anyone can confirm to me that it must be possible to do a factory reset of your device from within Recovery for there to ever be a procdure to unlock the bottloader.
And last but not at all least -- if someone can help me to end the appearance of that crazily ungrammatical error ("Frp not have wipe, factory reset failed"), I'd be very grateful. Because I'm hopeful that this is the key to unlocking my bootloader.
--scott
Developer options>Allow OEM unlocking
thanks, but of course I have both Allow OEM unlocking checked and also USB debugging checked. Perhaps it's a clue that the "OM unlocking" toggle seems to be not perfectly sticky. It sometimes/often happens that I check the value and it's gone abck to "off". At this point, i check that value before I do anything that might unlock the bootloader.
But thanks for the suggestion.
BTW -- please note that THIS question here is about how to get Factory Reset to work from Recovery on a phone which has no google account set up. To do THAT surely doesn't require the OEM Unlocking toggle to be set.
Whenever I factory reset my phone reasons maybe because of root or going back to stock I notice that the FRP is now disabled and I can skip past the google account with the skip button. Does the OEM unlock have to do with this? My phone is a factory unlocked model of the Pixel 7 pro.
I'm a bit confused with your question... If you initiate a factory reset from the settings menu, you effectively remove the FRP link to your account. FRP is designed to prevent other methods of factory reset (like from the recovery or bootloader) when an account has already been added to the device.
UltimateGamer83 said:
Whenever I factory reset my phone reasons maybe because of root or going back to stock I notice that the FRP is now disabled and I can skip past the google account with the skip button. Does the OEM unlock have to do with this? My phone is a factory unlocked model of the Pixel 7 pro.
Click to expand...
Click to collapse
Yes FRP is disabled when OEM unlocking is enabled.
Hello, my wifes stock S21+ crashed and rebooted. It now boots up, accepts SIM card pin code but UI crashes to black screen and reloads when you enter the pattern to unlock the phone. Phone is still locked and it asks for the pattern again. I can't activate developer mode/USB debugging because of this. I can call the phone and answer the call so the phone works, it just doesn't want to unlock.
Is there any way to get the data out? We do have backups but unfortunately yesterdays sons christmas event didn't get yet uploaded to the cloud. The phone has warranty but support said they will wipe the phone. I don't care about keeping phone under warranty, all I want is yesterdays data.
Safe mode has the same problem. I already tried flashing current and older stock firmware with Odin but same problem persists. Is there any other thing I could try?