Related
I haven't used my nexus in a couple months, turned it on today and there's a PIN lock.
I don't remember ever setting this up, I tried my usual PINs and none work.
I keep trying but I never get a forgot password log in with google option. I always get 5 wrong entries, wait 30 secs.
I'm at 35 incorrect PINs so far.
-I've also tried going to device manager but my device is always unavailable so I can't send a lock screen to it.
-I can't do a factory reset because my recovery is broken and I can't get into it to erase my data.
-I can't flash a new recovery because my computer isn't a trusted device to access it and I can't allow it because I can't log in.
I'm not sure what else to do.
I have a secondary user on it but I can't turn on the developer options for it because it's not the primary account.
Any ideas what I can do?
If you can get your driver issues figured out, so that the Fast Boot driver works, you can just reflash images from the Bootloader. You do not need to get into Recovery, or get passed the pin lock to reflash. To make it easy, you can use something like Wug's NRT and use the "Bricked Device" option to flash images from the bootloader screen.
I just rebooted my phone, get the "password required after restart" message, enter my password, and it immediately jumps back to the lockscreen and gives me the same message. If I deliberately enter the wrong password, it gives me a wrong password message, so in the first case it is recognizing my password as correct, just not unlocking.
It seems to be the same problem described here:
https://productforums.google.com/forum/#!topic/nexus/yMUh6a2SVLs;context-place=forum/nexus
I've tried rebooting, tried booting into recovery and wiping cache to no avail, tried booting into safe mode, hoping to avoid having to do a factory reset.
I can still receive phone calls and can activate the camera by swiping, so phone is running fine, just can't get past the lockscreen.
Thoughts?
So if it is not the boot up screen to unlock the encrypted partition but the Android start screen, go into recovery, delete the password db file and you are done
in TWRP, go to Advanced > File Manager and navigate to /data/system.
to me this happened after restoring a twrp backup
I have a metropcs Oneplus nord n100 I'm trying to access the the bootloader but oem option in developer mode is greyed out. Also i don't own a pc is there any way i can unlock.bootloader without a pc?
There are a few devices on which the bootloader can be unlocked without the need of a PC and fastboot command sets. For example, many Samsung devices can be bootloader unlocked by going to device Settings>About Phone and tapping Build Number 7 times until Developer Options is enabled. In Developer Options, enabling the OEM Unlock option will unlock the bootloader, thus disabling the layer of protection which restricts flashing of certain device partitions. Other than Samsung, there are some device OEMs and models which also allow bootloader unlocking in this manner. However, on most devices, in addition to enabling OEM Unlock, fastboot mode must be initiated, device and PC synced with a cable, and a command line or command set must be executed.
If your device oem unlock is greyed out, you can try unlocking it using fastboot and recovery mode with the help of a pc.
LegendSayantan said:
There are a few devices on which the bootloader can be unlocked without the need of a PC and fastboot command sets. For example, many Samsung devices can be bootloader unlocked by going to device Settings>About Phone and tapping Build Number 7 times until Developer Options is enabled. In Developer Options, enabling the OEM Unlock option will unlock the bootloader, thus disabling the layer of protection which restricts flashing of certain device partitions. Other than Samsung, there are some device OEMs and models which also allow bootloader unlocking in this manner. However, on most devices, in addition to enabling OEM Unlock, fastboot mode must be initiated, device and PC synced with a cable, and a command line or command set must be executed.
If your device oem unlock is greyed out, you can try unlocking it using fastboot and recovery mode with the help of a pc.
Click to expand...
Click to collapse
Thanks i will do further research and once again thank you for taking the time to reply
Carrier-locked devices generally do not have unlockable bootloaders, or at the very least until 6 months has passed for a SIM unlock in the case with Metro going by how T-Mobile handled bootloader unlocking with the OnePlus 6T. However, that's unconfirmed and I could not find any information on either carrier-locked models for the N100 regarding this matter. So for now, it's a dead end.
yes I'm having the same issue here with the be2015 metropcs variant. They're saying 180 days (6months) till able to unlock this phone. I've been searching for some sort of way around it but no lock as of yet. Please everyone keep us all updated just in case.
when i do
Code:
fastboot oem unlock
I get FAILED (remote: 'Flashing Unlock is not allowed.
I've been trying to follow this guide here with Shizuku but I'm also running into issues. any help here please? Thanks yall
Yeah, that tuturial in the other post that the mod locked, he also deleted the commands. I'm guessing there's an issue that xda doesn't want to be involved in, kinda like writing new imei's. So I guess we're kinda screwed.
I bought this phone cheap, €117 at a discount. And Its EU version, where I can unlock the oem bootloader on this phone.
You can enable OEM unlock in Debug menu with debloat until from girhub, but you cannot unlock bootloader in metro phones.
Even if you have got unlock token, OnePlus says that's imei failed.
So is there any way to unlock this phone from carrier?
meowmee said:
So is there any way to unlock this phone from carrier?
Click to expand...
Click to collapse
if it's metro, it has the unlock app on it; still have to be paid up and 180 days in on your account, though
CandymanCA said:
I have a metropcs Oneplus nord n100 I'm trying to access the the bootloader but oem option in developer mode is greyed out. Also i don't own a pc is there any way i can unlock.bootloader without a pc?
Click to expand...
Click to collapse
Just for the record everyone:
Bugjaeger Premium - Apps on Google Play
Debugging and maintenance tool for Android devices
play.google.com
Bugjaeger Premium actually allows you to use an OTG Connection, (Android-->Android), that enables A Real connection via ADB/Fastboot.
So for all those that have no PC, but have two devices, it is possible to use one to run the ADB or Fastboot consoles and run authentic commands. I use it all the time since a desktop isn't so portable.
It takes a little thinking when it comes to the directories used, but I've easily ran Fastboot oem unlock and flashing commands before on the go
ways2 said:
yes I'm having the same issue here with the be2015 metropcs variant. They're saying 180 days (6months) till able to unlock this phone. I've been searching for some sort of way around it but no lock as of yet. Please everyone keep us all updated just in case.
when i do
Code:
fastboot oem unlock
I get FAILED (remote: 'Flashing Unlock is not allowed.
I've been trying to follow this guide here with Shizuku but I'm also running into issues. any help here please? Thanks yall
Click to expand...
Click to collapse
Tell you the truth, I was in the process of switching out SD Cards in the BE2015 and while I had the SIM/Tray out I saw that the developer options allowed the OEM Unlock toggle to be switched....
The option greyed itself back out once the sim was reinserted, but, I was able to toggle the switch ON before it did all that.
And even greyed out the option remains switched ON now.
For the record.
here your solution
One+_TooL with Grayed out Oem_Unlock (Bootloader Unlock)enabler & Engineer Decrypt
Here is my latest version of My Oneplus Tool . This tool can do almost everything for you. I have added a method to switch the Oem_Unlock switch on Sim locked devices. It will ungray the switch so you can flip it and bootloader unlock. It still...
forum.xda-developers.com
I vaguely remember a speedbump when unlocking my G7P a couple years back, but cannot recall what it was.
Search gives me many, many, many results that omit anything but a happy ending, are dated platforms and have differing procedures/results.
Procedure I followed:
Fresh XT2025-1 fresh out of the box this morning.
Disabled Google Play Protect & enabled Developer Options + ADB Debugging.
Restarted into Bootloader.
I submitted my fastboot oem get_unlock_code results, clicked the blue button & confirmed scary warranty-now-void pop-up.
Received email from Moto w/ the code. Did it a 2nd time & received same code.
Ran fastboot oem unlock UNIQUE_KEY(w/ 20 digit key that motorola emailed me).
Result: WARNING: This command erases all user data. Please re-run this command to continue. Total time: 0.008s.
Ran fastboot oem unlock UNIQUE_KEY again.
Result: Check 'Allow OEM Unlock' in Android Settings > Developer Options. Total time: 0.007s.
Rebooted & OEM Unlock is still greyed out. Still says oem_locked on Bootloader screen. Boot logo is still generic Moto.
Phone has been on wifi for an hour or so, do not have a SIM @ this time. EDIT: Was on wifi for hours before, as well.
Anyone have any ideas?
PS: I paid full price @ BB w/ no subsidies, just so I can unlock now. Using latest ADB/platform-tools_r31.0.2.
After ~15 minutes & my multi-edits to my post, the unlock toggle became available. Was just impatient.
Mods, please delete post unless you think it may be useful for reference.
googleverifysux said:
After ~15 minutes & my multi-edits to my post, the unlock toggle became available. Was just impatient.
Mods, please delete post unless you think it may be useful for reference.
Click to expand...
Click to collapse
In my case, it became available soon after I connected to wifi.
I tried many things, but I couldn't get the option active without wifi connection.
I don't know if having SIM card influence this, because I tried everything without SIM, as well.
With moto e6, I had the option without wifi (and without SIM).
PROBLEM:Under certain scenarios, enabling Quick Unlock on the OnePlus 9 Pro with Android 12 causes semi-bricked phone: the phone will vibrate OVER and OVER again and it is impossible to log in!
If your phone is in this state, here's three possible fixes:
Spoiler: Possible Solution #1
POSSIBLE SOLUTION #1:
Thanks to Caligastia's post, here's another option to resolve.... (quoting from his post)[/B]
Just use the adb command...
Code:
locksettings clear --old [PASSWORD]
And that should do the trick.. Make sure to untoggle the quick unlock option if you set a new password
Click to expand...
Click to collapse
Spoiler: Possible Solution #2
POSSIBLE SOLUTION #2:
Revert to settings_system.xml.fallback file. Do not follow this guide UNLESS your phone is in this vibrate over and over / impossible to login state.
Note: This only works if you have USB debugging enabled on your computer with root enabled. This will not work if you haven't performed adb shell as root before ( com.android.shell ). Doesn't hurt to try!
Boot up phone to system/normal mode.
Type the following in command prompt:
Code:
adb shell
su
ls /data/system/users/0/settings_system.xml
If it says:
Code:
/data/system/users/0/settings_system.xml
Then this fix should work! Otherwise, this probably won't work.
Finally, type...
Code:
mv /data/system/users/0/settings_system.xml /data/system/users/0/settings_system.xml.old
cp /data/system/users/0/settings_system.xml.fallback /data/system/users/0/settings_system.xml
reboot
Your phone will reboot and the issue should be fixed!
By applying this method you may lose a few recently changed system settings, but nothing major.
Spoiler: Possible Solution #3
POSSIBLE SOLUTION #3:
Go to bootloader/fastboot mode on your phone.
Type
Code:
fastboot --set-active=a
fastboot reboot
if it doesn't boot right still, go back to bootloader/fastboot and type
Code:
fastboot --set-active=b
fastboot reboot
There are no settings on the 9Pro A12 called quick unlock. What are you referring to?
I'm referring to the setting called Quick Unlock.
Password and Security > Lock Screen Password.
But what this option do ? ( Quick unlock )
asheroto said:
PROBLEM:Enabling Quick Unlock on the OnePlus 9 Pro with Android 12 causes semi-bricked phone: the phone will vibrate OVER and OVER again and it is impossible to log in!
DO NOT ENABLE QUICK UNLOCK!
Click to expand...
Click to collapse
On my LE2123 OnePlus 9 Pro I do not face this issue with quick unlock. I made a test now once and no issue. Just FYI. I an not rooted.
K1nsey6 said:
There are no settings on the 9Pro A12 called quick unlock. What are you referring to?
Click to expand...
Click to collapse
This option appears if you select Alphanumeric password, using the regular keyboard instead of number pad. Quick unlock will unlock your phone immediately once you enter the password without having to press the enter key.
Interesting, I have the LE2125 with alphanumeric enabled.
I edited the original post to say "Under certain scenarios".
I just updated to Android 12 on my OnePlus 8 and tried out this setting. Now it is impossible to log in to my phone and it constantly vibrates, just like described above.
I cannot connect through ADB (shows as unauthorized) so I cannot complete the steps outlined above. Any ideas what I could do?
blxyy said:
I just updated to Android 12 on my OnePlus 8 and tried out this setting. Now it is impossible to log in to my phone and it constantly vibrates, just like described above.
I cannot connect through ADB (shows as unauthorized) so I cannot complete the steps outlined above. Any ideas what I could do?
Click to expand...
Click to collapse
Unfortunately you have to allow the host (your computer), but you can't do that unless you can tap on the popup.
Can you get in with TWRP or anything else? If so you could edit the file that way. Otherwise, try booting to the other slot.
How to check the current slot:
How to Check if You're on Partition Slot A or Slot B? - KrispiTech
Android phones can now have an A and a B partition system for the OS and we can use this fastboot command to check and see which slot is currently active.
krispitech.com
How to change the active slot:
adbcommand.com - adbcommand Resources and Information.
adbcommand.com is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, adbcommand.com has it all. We hope you find what you are searching for!
adbcommand.com
I cannot connect through ADB (shows as unauthorized) so I cannot complete the steps outlined above. Any ideas what I could do?
Click to expand...
Click to collapse
@bixyy
Just saw this, hope i'm not too late to help.
If adb shows "unauthorized" it just means that usb debugging permission was revoked between your phone and computer. here's what to do: (assuming you're on windows)
-Unplug your phone from pc. Disable Usb debugging and turn off "disable timeout"
-on your pc, go to C:/users/<username>/.android (it's a hidden folder) and delete adbkey.
-reboot both phone and pc to make sure it takes effect.
-plug your phone again, turn on usb debugging and you should get a new prompt to allow authorization.
adb devices should return your serial number now.
Added possible alternate solution
I ran into the same issue, OP was very helpful.
A bit more info here:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Finally fixed it! Very simple solution it turns out. Since the setting is only for alpha numeric passwords once you erase the pass the phone stops acting up.
Just use the adb command
locksettings clear --old [PASSWORD]
And that should do the trick.. Make sure to untoggle the quick unlock option if you set a new password
Caligastia said:
Finally fixed it! Very simple solution it turns out. Since the setting is only for alpha numeric passwords once you erase the pass the phone stops acting up.
Just use the adb command
locksettings clear --old [PASSWORD]
And that should do the trick.. Make sure to untoggle the quick unlock option if you set a new password
Click to expand...
Click to collapse
Thanks for that man! I updated the original post to include your solution and linked to your post for credits!
I had the same issue on my OnePlus Nord, and finally managed to fix it too!
Thanks to @asheroto for your initial guide and @Caligastia for your last comment that gave me the idea of trying with digits only!
Here is how I did it:
After rebooting my phone in recovery mode to activate the USB debugging, I connected to it using adb shell
The locksettings clear --old [PASSWORD] command wasn't allowed on my phone.
==> I'm guessing it was due to some security settings enforced by the enterprise work profile I had installed on my device.
So instead of trying to clear the password, I tried to change it to a PIN code using the command:
locksettings set-pin --old [PASSWORD] [PIN_CODE_HERE]
The command succeeded and after a few seconds of waiting, a digit keyboard finally shown up on my previously bugged lock screen, allowing me to unlock my phone!
I then disabled in the system settings the "Quick Lock" feature and restore my previous password.
_147 said:
I had the same issue on my OnePlus Nord, and finally managed to fix it too!
Thanks to @asheroto for your initial guide and @Caligastia for your last comment that gave me the idea of trying with digits only!
Here is how I did it:
After rebooting my phone in recovery mode to activate the USB debugging, I connected to it using adb shell
The locksettings clear --old [PASSWORD] command wasn't allowed on my phone.
==> I'm guessing it was due to some security settings enforced by the enterprise work profile I had installed on my device.
So instead of trying to clear the password, I tried to change it to a PIN code using the command:
locksettings set-pin --old [PASSWORD] [PIN_CODE_HERE]
The command succeeded and after a few seconds of waiting, a digit keyboard finally shown up on my previously bugged lock screen, allowing me to unlock my phone!
I then disabled in the system settings the "Quick Lock" feature and restore my previous password.
Click to expand...
Click to collapse
can you help me i cant seem to get adb to recognize my phone
Hi,
Is there any possible solution for us who don't have USB-Debugging enabled?
The goal is to not have to wipe the whole phone and loose all data.
Possible solution #1 fails: Wont work because USB debugging is disabled which prevents us from getting adb-shell and run the "
locksettings clear --old [PASSWORD]" command. When trying to figure out how to enable USB debugging from remote it seems to require some fastboot option which would wipe the phone.
Possible solution #2: Same - requires shell, and we cant enable usb debugging because of the bug
Possible solution #3: I can access fastboot but not run the specific commands:
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.000s
fastboot --set-active=a
Setting current slot to 'a'
FAILED (remote: 'Slot Change is not allowed in Lock State')
fastboot: error: Command failed
Unlocking boot to install TWRP and enable debugging to use ADB shell would wipe the phone as I understand it.
Any suggestions please?
Is your phone locked when you're doing that?
asheroto said:
Is your phone locked when you're doing that?
Click to expand...
Click to collapse
Developer options enabled
OEM bootloader unlock enabled
USB debugging enabled
Default USB Configuration file transfer
Non-TMO variant = boot to bootloader, then fastboot OEM unlock...wipes device. No other way. Unlock bootloader will wipe device period.