Develop Bugs

[Q] Pattern Lock problem

HTC Wildifire S
Pattern lock attempts are over.
Asking for google account.
I know my correct username/pass.
But my wifi and data services are off.
As i read you do not need internet for this. but still when i enter correct details it just comes back to sign in screen.
USB Debugging is off , so can i use file manager in recover mode to delete gesture.key.
To install filemanager in recovery mode i need CWM ? how do i install when usb debug is off.
How do i get the pattern lock bypassed ?

These I do not answer, because there is a possibility of the phone not being yours, sorry.

Forgot the PIN - any possibility to retrieve the data from my redmi note 5 pro?

I have my device with me, and someone has changed the PIN to my phone and I'm now locked out. I did not link my device to the MI cloud and don't have google's sync enabled. Is there any way i can retrieve just the pictures from the device?
The bootloader is locked, and the phone doesn't have adb enabled.
Will a factory reset, and then deep data recovery using some tools work? I need the pictures alone.

Unlock greyed oem option help

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

How To Guide [GUIDE] How to fix Quick Unlock bug on Android 12 (constant vibrate at lock screen, impossible to log in)

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.

[Xiaomi Mi 10T Lite (gauguin)] need help for firehose file patching

My mi11 bricked.The screen only shows errors: system ui isn't responding,I entered recovery mode and then upgraded to the latest system now.but nothing changed.I also restored the factory settings, but the problem has not been resolved.
Miflash error: Flashing is not allowed in Bootloader Lock State​so,i need help for the firehose file patched to skip the EDL authentication for flash rom (gauguin_images_V13.0.11.0.SJSEUXM)
Many thanks for your help .

It will be you are hard to find. Weather try in developer options to unlock bootloader wait 7 days and flash again

its bricked.Unable to enter settings, unable to open developer options

I bought a second-hand mobile phone to restore, because the display was broken, the seller said that there were no associated accounts, as the display did not show an image and only sound, I deduced that everything was going well, when I tried I found that I had an MI account associated. the seller don't know also the mi account information, now I can't use it at all, I didn't want to spend more money on the phone so I tried everything that is within reach on the internet. The mobile has:
1. My account (I don't have the information)
2. Impossible to unlock the bootloader (I can't access the mobile phone)
3. Impossible to enable debug mode (I can't access the mobile phone)
4. I can connect in fastbook
5. I can connect in adb sideload
6. I can connect in EDL mode (Qualcomm 9008)
I tried QPST, QFIL, but it always gives an error, maybe because of the firehose.
As the bootloader is blocked, I have no more chances for free, the last hope was to try Firehose in Auth for this model, but I can't find it anywhere.
The cell phone does not detect the Touch, and every time I turn it off it restarts automatically. However I can use a mouse in OTG.
I thought if I did a flash it would solve it too.
The last solution is to pay someone who can do the job and guarantee that it will work without restrictions, for that you would also have to find someone you can trust.