Develop Bugs

[Q] Forgot Pattern Lock

Hi there,
I owned a Galaxy Nexus running Jelly Bean 4.2.1 version, yakjuxw (Not rooted), GSM. I activated the Pattern Lock to prevent the kids at my relatives house messing my phone. Unfortunately, I forgot the pattern and the phone stays locked out. I have tried the pattern combinations for days but failed.
I have tried to key in my Gmail account username/password but since my phone is wifi/data switched off, I cant sign in. Moreover, I am not sure whether the USB Debugging is enabled.
I have tried some 'hole' methods recommended at some forums, but it didnt work on my phone.I hope to get access to my messages/images/some files and transfer them to my pc before reset the phone to factory setting. Please help! :-|

yu_buffon said:
Hi there,
I owned a Galaxy Nexus running Jelly Bean 4.2.1 version, yakjuxw (Not rooted), GSM. I activated the Pattern Lock to prevent the kids at my relatives house messing my phone. Unfortunately, I forgot the pattern and the phone stays locked out. I have tried the pattern combinations for days but failed.
I have tried to key in my Gmail account username/password but since my phone is wifi/data switched off, I cant sign in. Moreover, I am not sure whether the USB Debugging is enabled.
I have tried some 'hole' methods recommended at some forums, but it didnt work on my phone.I hope to get access to my messages/images/some files and transfer them to my pc before reset the phone to factory setting. Please help! :-|
Click to expand...
Click to collapse
You can reset the phone to Factory settings.
1. Turn off your phone.
2. Press vol up+vol down+power buttons till it vibrates. Now you see a dead android.
3. Navigate with your volume buttons to "Recovery Mode" and select it with the power button.
4. When its booted you should see a soort of menu.
5. Select "wipe data" (or something like that). THIS WIPES YOUR DATA AND YOUR INTERNAL STORAGE (music, pictures etc..)
6. Select reboot system now.
7. Done.
Sent from my Galaxy Nexus using XDA Premium HD app

Without wiping out the data
mrgnex said:
You can reset the phone to Factory settings.
1. Turn off your phone.
2. Press vol up+vol down+power buttons till it vibrates. Now you see a dead android.
3. Navigate with your volume buttons to "Recovery Mode" and select it with the power button.
4. When its booted you should see a soort of menu.
5. Select "wipe data" (or something like that). THIS WIPES YOUR DATA AND YOUR INTERNAL STORAGE (music, pictures etc..)
6. Select reboot system now.
7. Done.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thank you for the reply. But, I wish to get access to my files in order to transfer them to a save location before reset the phone to Factory settings. Is there a way to hack into the device without wiping out the data?

Try this out.
http://en.miui.com/thread-5684-1-1.html

ATTACK said:
Try this out.
http://en.miui.com/thread-5684-1-1.html
Click to expand...
Click to collapse
Call yourself from another phone and answer, after that your phone will probably get unlocked.

In ADB or some other way to access the file system in Recovery Mode
navigate to /data/system and
delete password.key and/or gesture.key
- reboot.
Password/Gesture Lock gone.
You can use AROMA File Manager in Recovery (would have to sideload it if you didn't pre-install it)
http://forum.xda-developers.com/showthread.php?t=1646108
Good luck. Post back with your solution.

Trying...
ATTACK said:
Try this out.
Click to expand...
Click to collapse
Thank you for the link. I am downloading the Cygwin on my Windows Vista machine. Slow broadband speed has actually delayed my work.

Sideload
jpinsl said:
In ADB or some other way to access the file system in Recovery Mode
navigate to /data/system and
delete password.key and/or gesture.key
- reboot.
Password/Gesture Lock gone.
You can use AROMA File Manager in Recovery (would have to sideload it if you didn't pre-install it)
http://forum.xda-developers.com/showthread.php?t=1646108
Good luck. Post back with your solution.
Click to expand...
Click to collapse
Thank you for the help. What do you mean by sideload? I am using a Galaxy Nexus which has no SD slot.

yu_buffon said:
Thank you for the help. What do you mean by sideload? I am using a Galaxy Nexus which has no SD slot.
Click to expand...
Click to collapse
Please use the search function:
http://forum.xda-developers.com/sitesearch.php?q=sideload

adb method failed
ATTACK said:
Try this out.
/QUOTE]
Hi, I have used the Mint Live session instead. When I type <adb shell>, it returns <error no device found>. What should I do? Please help.
Click to expand...
Click to collapse

I am a noob
jpinsl said:
Please use the search function:
Click to expand...
Click to collapse
Hi, I have searched about sideload. I have never rooted my phone before and having difficulties in understanding the android features. Can you provide me a walk-through on how can I install the recovery on my locked out phone and access my files please.
FYI, I tried the adb method listed above, but the terminal returns <error no device found>. I tried the method on Mint (linux) live session.

I managed to get access to my data. Messages are the only thing I am losing out. Thank you XDA guys.

Rooting the LG Exalt LTE from Verizon (LG VN220) - Request for Advice

TL.DR; Trying to root new Verizon Android flip-phone with Marshmallow 6.0.1, ARMv7. Firmware version: VN22010B. Seems to to be locked down.
Click to expand...
Click to collapse
I'm trying to root the LG Exalt LTE, or LG VN220, from Verizon. Initially, I've attempted the common rooting kits, such as KingoRoot as well as the tools described around XDA. However all failed. I suspect the cause to be the restrictive permissions of /data/local/tmp, which prevents execution of binaries. I believe any kit using this location will likely fail to achieve anything.
As such, I've been looking to achieve the same using manual techniques. The first step, as in most rooting activity is to put the device into USB debugging mode. To do this on the VN220, first compose ##7764726220. When asked for a service code, use 000000 to access a special menu. Select the Developer Options > USB Debugging and select On. There is an additional menu below named Select USB configuration, from which you can select Media Transfer Protocol or RNDIS among other options.
With that done, you can verify that you can now communicate with the device via ADB. To do so, download the Minimal ADB and Fastboot bundle. While I was successful in querying the device with ADB with
Code:
adb devices
Trying to use fastboot simply outputs "< waiting for device >" indefinitively. It is also possible to open a shell using ADB, however attempting ADB with root will fail. I don't think this is caused by having wrong drivers, as all the other tools could detect the phone (see below), but rather a permission issue.
From there, I've try to boot in different modes, which are accessible by turning off the phone, and then powering up the device while holding the Volume Down button. This will boot into a white screen with some options, including the "Safe Mode" option which I attempted. The second mode is the "Firmware Upgrade" mode which is accessible by again, powering down the phone and powering it up again, but this time holding the Volume Up for 3 seconds.
Attempting to run the following fails:
Code:
fastboot oem unlock
That being said, I later found out that LG does provides a legitimate way to unlock the bootloader via their LG developer portal. Unfortunately the VN220 is not in the list of supported devices, nor does the procedure given applies to this phone. Additionally, it requires the device ID which fails also since it requires fastboot:
Code:
fastboot oem device-id
The other attempt I've tried is using the LG Mobile Support Too l and while it was useful to obtain the KDZ file from their website, it also failed to apply the update. LGUP didn't recognise the model. (Note that both requires the USB mode to be RNDIS to detect the phone)
Trying to run apps from the internal storage such as su or even using the chmod command only results in "Operation not permitted" messages. So even temporary root seems rather difficult.
At this point, I'd like to know if anyone has any advice on additional things I could try to root the phone, or even have temporary root.
Thanks in advance
@cyberrecce

Why?
First of all thank you, I've been looking for that service code to enable developer settings / adb since I discovered the phone secretly runs Android. But I don't see why we would need root, I've been using adb to side load apps since I can't get to a menu that allows it

jfn0802 said:
First of all thank you, I've been looking for that service code to enable developer settings / adb since I discovered the phone secretly runs Android. But I don't see why we would need root, I've been using adb to side load apps since I can't get to a menu that allows it
Click to expand...
Click to collapse
1. Why? To install a custom ROM.
2. Did you get any issue with certificates when side-loading apps? I keep getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES. Can't seem to find the "Install from Unknown Sources" option.

Same problem
InfectedPackets said:
1. Why? To install a custom ROM.
2. Did you get any issue with certificates when side-loading apps? I keep getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES. Can't seem to find the "Install from Unknown Sources" option.
Click to expand...
Click to collapse
i get the same error. did you find a solution? i would really appreciate it

InfectedPackets said:
1. Why? To install a custom ROM.
2. Did you get any issue with certificates when side-loading apps? I keep getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES. Can't seem to find the "Install from Unknown Sources" option.
Click to expand...
Click to collapse
MendilR said:
i get the same error. did you find a solution? i would really appreciate it
Click to expand...
Click to collapse
re: the certificate error for side loading apps...
Code:
adb shell settings put secure install_non_market_apps 1
turns off the unknown source block, but I'm still getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
Could the apk itself I'm trying to use have a bad certificate? Or is there another solution?

InfectedPackets said:
I'm trying to root the LG Exalt LTE, or LG VN220, from Verizon. Initially, I've attempted the common rooting kits, such as KingoRoot as well as the tools described around XDA. However all failed. I suspect the cause to be the restrictive permissions of /data/local/tmp, which prevents execution of binaries. I believe any kit using this location will likely fail to achieve anything.
As such, I've been looking to achieve the same using manual techniques. The first step, as in most rooting activity is to put the device into USB debugging mode. To do this on the VN220, first compose ##7764726220. When asked for a service code, use 000000 to access a special menu. Select the Developer Options > USB Debugging and select On. There is an additional menu below named Select USB configuration, from which you can select Media Transfer Protocol or RNDIS among other options.
With that done, you can verify that you can now communicate with the device via ADB. To do so, download the Minimal ADB and Fastboot bundle. While I was successful in querying the device with ADB with
Code:
adb devices
Trying to use fastboot simply outputs "< waiting for device >" indefinitively. It is also possible to open a shell using ADB, however attempting ADB with root will fail. I don't think this is caused by having wrong drivers, as all the other tools could detect the phone (see below), but rather a permission issue.
From there, I've try to boot in different modes, which are accessible by turning off the phone, and then powering up the device while holding the Volume Down button. This will boot into a white screen with some options, including the "Safe Mode" option which I attempted. The second mode is the "Firmware Upgrade" mode which is accessible by again, powering down the phone and powering it up again, but this time holding the Volume Up for 3 seconds.
Attempting to run the following fails:
Code:
fastboot oem unlock
That being said, I later found out that LG does provides a legitimate way to unlock the bootloader via their LG developer portal. Unfortunately the VN220 is not in the list of supported devices, nor does the procedure given applies to this phone. Additionally, it requires the device ID which fails also since it requires fastboot:
Code:
fastboot oem device-id
The other attempt I've tried is using the LG Mobile Support Too l and while it was useful to obtain the KDZ file from their website, it also failed to apply the update. LGUP didn't recognise the model. (Note that both requires the USB mode to be RNDIS to detect the phone)
Trying to run apps from the internal storage such as su or even using the chmod command only results in "Operation not permitted" messages. So even temporary root seems rather difficult.
At this point, I'd like to know if anyone has any advice on additional things I could try to root the phone, or even have temporary root.
Thanks in advance
@cyberrecce
Click to expand...
Click to collapse
Just curious - any success or updates. I can't seem to get past " INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES"

For installing apps I'm still not getting past INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
I even tried pulling an apk from my LG G4 that successfully installed on that device and tried installing it on the Exalt, but same error.
The biggest reason I've seen for the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES is apks that are signed poorly. When I check the apks I'm using for their signatures with the JDK it says one or more of their signatures lack a timestamp which can cause problems.
Also, downloading the apk from the Exalt's browser and trying to install from either
settings > phone settings > storage > phone > explore > downloads > open > install
or
tools > file manager > internal storage > downloads > open > install
has been coming up with "app not installed" after it tries to install the apk.
I'm not really giving up though, I just don't really know where to go from here.

effulgent.unicorn said:
For installing apps I'm still not getting past INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
I even tried pulling an apk from my LG G4 that successfully installed on that device and tried installing it on the Exalt, but same error.
The biggest reason I've seen for the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES is apks that are signed poorly. When I check the apks I'm using for their signatures with the JDK it says one or more of their signatures lack a timestamp which can cause problems.
Also, downloading the apk from the Exalt's browser and trying to install from either
settings > phone settings > storage > phone > explore > downloads > open > install
or
tools > file manager > internal storage > downloads > open > install
has been coming up with "app not installed" after it tries to install the apk.
I'm not really giving up though, I just don't really know where to go from here.
Click to expand...
Click to collapse
Any ideas on how to get past - "INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES"?

PAULC91316 said:
Any ideas on how to get past - "INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES"?
Click to expand...
Click to collapse
I'm still at the same place I was the other day when I posted this.
effulgent.unicorn said:
For installing apps I'm still not getting past INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
I even tried pulling an apk from my LG G4 that successfully installed on that device and tried installing it on the Exalt, but same error.
The biggest reason I've seen for the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES is apks that are signed poorly. When I check the apks I'm using for their signatures with the JDK it says one or more of their signatures lack a timestamp which can cause problems.
Also, downloading the apk from the Exalt's browser and trying to install from either
settings > phone settings > storage > phone > explore > downloads > open > install
or
tools > file manager > internal storage > downloads > open > install
has been coming up with "app not installed" after it tries to install the apk.
I'm not really giving up though, I just don't really know where to go from
here.
Click to expand...
Click to collapse

InfectedPackets said:
The other attempt I've tried is using the LG Mobile Support Too l and while it was useful to obtain the KDZ file from their website, it also failed to apply the update. LGUP didn't recognise the model. (Note that both requires the USB mode to be RNDIS to detect the phone)
Click to expand...
Click to collapse
Can you please share with us the KDZ file?
Thanks!

anyone?

You will need to:
- unlock it’s Bootloader. If the “fastboot oem unlock” command will not work (and I’m quite sure it will not, since we’re talking about a USA LG device), you can stop here and throw the phone out the window.
- if by some any miracle you will be able to unlock the bootloader, you have two ways of rooting it:
1. Using TWRP and a superuser zip file (magisk or the now Chinese owned supersu). The main problem with this is that you will need to compile TWRP yourself, since I doubt anyone will bother for such an obscure device.
2. Using a prerooted boot image. You will need the stock boot image, install the latest magisk manager, let it root it and then flash it via fastboot. This is particularly difficult because you will need to decrypt the kdz file (if any available) in order to get the boot.img
Even if by a greater miracle you will be able to get 1 or 2 working, there still is a huge chance that the fastboot flash command will be disabled.
Forget about solutions like king/kingoroot. Best case scenario they will fail. Worst case scenario they will softbrick the phone by gaining temporary root and then modifying /system. That will in turn trigger dm-verity which will cause the soft brick.
Forget about the scams like oneclickroot. Their so called techs will try the aforementioned and fail and you will waste your $40.
Sorry To deliver the bad news, but there’s no way out of it.

Thanks for taking your time, to help me.
I will check if I can unlock the bootloader.
Thanks alot

r3w1NNNd said:
You will need to:
- unlock it’s Bootloader. If the “fastboot oem unlock” command will not work (and I’m quite sure it will not, since we’re talking about a USA LG device), you can stop here and throw the phone out the window.
- if by some any miracle you will be able to unlock the bootloader, you have two ways of rooting it:
1. Using TWRP and a superuser zip file (magisk or the now Chinese owned supersu). The main problem with this is that you will need to compile TWRP yourself, since I doubt anyone will bother for such an obscure device.
2. Using a prerooted boot image. You will need the stock boot image, install the latest magisk manager, let it root it and then flash it via fastboot. This is particularly difficult because you will need to decrypt the kdz file (if any available) in order to get the boot.img
Even if by a greater miracle you will be able to get 1 or 2 working, there still is a huge chance that the fastboot flash command will be disabled.
Forget about solutions like king/kingoroot. Best case scenario they will fail. Worst case scenario they will softbrick the phone by gaining temporary root and then modifying /system. That will in turn trigger dm-verity which will cause the soft brick.
Forget about the scams like oneclickroot. Their so called techs will try the aforementioned and fail and you will waste your $40.
Sorry To deliver the bad news, but there’s no way out of it.
Click to expand...
Click to collapse
Any sage advice on the [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] issue when sideloading apps?
 @jfn0802 said they had success with sideloading, but haven't been online in ages, and none of the rest of us seem to have had the same success. Minimum, that's what I would like to accomplish.
[side note, has anyone switched from Verizon with this phone? I'm looking to, but I'm wondering a couple of things like, does verizon have the mobile hotspot function restricted from use on other carriers? & etc & just wondering how it's doing off-verizon for anyone.]

effulgent.unicorn said:
Any sage advice on the [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] issue when sideloading apps?
@jfn0802 said they had success with sideloading, but haven't been online in ages, and none of the rest of us seem to have had the same success. Minimum, that's what I would like to accomplish.
[side note, has anyone switched from Verizon with this phone? I'm looking to, but I'm wondering a couple of things like, does verizon have the mobile hotspot function restricted from use on other carriers? & etc & just wondering how it's doing off-verizon for anyone.]
Click to expand...
Click to collapse
my freinds are using it in Canada with videotron and everything works, without unlocking

Just to add a clue what to look at, I think these devices are from Verizon and they are blocking anonymous apps from being installed

GenTech Solution said:
Just to add a clue what to look at, I think these devices are from Verizon and they are blocking anonymous apps from being installed
Click to expand...
Click to collapse
Yes right, but how can I go around it?
Ps. I was able to uninstall apps (I removed my Verizon)
With adb shell, as the user 0, but with adb normal uninstall didn't work, but when I try to install with adb shell, it gave the same certificate erorr

GenTech Solution said:
Just to add a clue what to look at, I think these devices are from Verizon and they are blocking anonymous apps from being installed
Click to expand...
Click to collapse
Isn't that what turning on the "install from unknown sources" option should do? I still get the Install Parse Failed after switching it on with ADB.
@98jbsz I've tried to uninstall without success. What way did you do it? And does it just leave a blank space in the menu screen?
[Less on topic, sorry again, but has anyone seen the LG Wine LTE? http://www.lg.com/us/cell-phones/lg-UN220-lg-wine
It's strikingly similar to our friend the Exalt LTE here, but it seems less carrier branded/available at US Cellular, so I'm wondering if that would make a difference?
Major differences Wine LTE has more 4G bands (2/4/5/12/25) versus Exalt (4/5/13), which kind of has me kicking myself, because travel and 4G was one of the reasons I bought the Exalt. Both have quadband GSM and WCDMA, but interestingly the Wine also has CDMA.
Beyond that, there are some more smaller differences I scavenged from their LG pages, Exalt has more bluetooth profiles, supports more music formats, has more GPS capabilities, wifi calling, and 1 more ringtone. Wine has more supported video formats, and an FM radio.
I'm curious about what/if the Wine would have for sms messaging (I doubt it'd have Verizon's message+) and instead of my Verizon app...]

98jbsz said:
Yes right, but how can I go around it?
Ps. I was able to uninstall apps (I removed my Verizon)
With adb shell, as the user 0, but with adb normal uninstall didn't work, but when I try to install with adb shell, it gave the same certificate erorr
Click to expand...
Click to collapse
Alright, I also managed to uninstall my verizon and verizon's cloud app using
Code:
adb shell and the pm uninstall -k --user 0
But the Verizon apps folder on the menu screen remains, although it's empty. Any ideas on how to remove it?
Then I tried to install an apk using
Code:
pm install
and it came back with [INSTALL_FAILED_INVALID_URI] which...is a different than [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES], but not better.

right, but when you first copy the APK to the phone, and then you install it, you will see the [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] error. still not a solution

Mi A2 Lite Bluetooth Audio Problems? Back To Oreo?

Hi There,
Just bought my GF a Mi A2 Lite a few weeks ago and she is loving it compared to her old iPhone 5s but one major issue atm is that her bluetooth headphones seem to be giving her issues!
The audio stutters a LOT even when right next to the phone. Tried resetting the Bluetooth connection but to no avail.
I had a quick scan through the forums and seen that people recommend going back to Oreo to solve the issues.
Is there any clear guides or links on how to do this? I know my way around tech so should have any issues following a guide.
Thanks in advance!

Yes, it's a very annoying bug.... I have it too, but didn't find a solution
That's the reason why I downgraded to Oreo!
If you want to downgrade,
1. you must unlock the bootloader, but this will erase all of your data. So, don't forget to make a backup of your internal storage. https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-unlock-bootloader-official-t3885578
2. Install MiFlash and ADB on your computer: https://www.xiaomiflash.com/download/ https://forum.xda-developers.com/showthread.php?t=2317790
3. Download an oreo stock rom and unzip it: https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
4. Boot your phone into bootloader
-> Connect your phone with your computer and enable ADB in developer settings
-> Shutdown your phone and hold Volume Down and Power-Button to boot your phone into fastboot/bootloader
5. Open the MiFlash-Tool on your computer and select the Oreo-Stock-Rom which you want to install.
6. At the bottom of the MiFlash window you must choose clean all, this will erase all of your data!
7. If your phone gets recognized from your computer and the programm, then you can hit the button flash on the top of the window
8. This procedure takes a while, so be patient.
9. If everything works, it will reboot your phone automatically.
10. Maybe you will have the bug of swapped SIMs. You must install TWRP: https://forum.xda-developers.com/mi-a2-lite/development/official-twrp-daisy-t3855396
and flash this file to fix it: https://forum.xda-developers.com/attachment.php?attachmentid=4704476&stc=1&d=1550012435
11. Perfect! You downgraded to Oreo!
I hope this little guide could help you, and sorry if it's a bit complicated

If it's any consolation, I had this issue on Oreo and Pie!
I'm now upgrading to a Pixel 3a, but keeping this phone for development. Might try porting Ubuntu Touch some time. ?

iforgotmylogin said:
If it's any consolation, I had this issue on Oreo and Pie!
I'm now upgrading to a Pixel 3a, but keeping this phone for development. Might try porting Ubuntu Touch some time. ?
Click to expand...
Click to collapse
Okay, that's weird ?
Maybe there was a problem with your Bluetooth headset?

00norman00 said:
Okay, that's weird ?
Maybe there was a problem with your Bluetooth headset?
Click to expand...
Click to collapse
If so, it was a problem with every one I tried!
I tried on a generic Bluetooth speaker, two different generations of Echo Dot, and on a current gen regular Echo.

It is channels problem. Bluetooth and WiFi are on 2.4GHz. Some frequencies are busy and it stutters. Turn off WiFi and Bluetooth. Turn Bluetooth on and connect your Bluetooth device. Wait 10 seconds and turn on WiFi. After this WiFi will avoid frequency where is Bluetooth device and use free frequencies.

LotR656 said:
It is channels problem. Bluetooth and WiFi are on 2.4GHz. Some frequencies are busy and it stutters. Turn off WiFi and Bluetooth. Turn Bluetooth on and connect your Bluetooth device. Wait 10 seconds and turn on WiFi. After this WiFi will avoid frequency where is Bluetooth device and use free frequencies.
Click to expand...
Click to collapse
Interesting... sounds like a pain in the ass, but I'll try this next time I get chance.
Thanks!

LotR656 said:
It is channels problem. Bluetooth and WiFi are on 2.4GHz. Some frequencies are busy and it stutters. Turn off WiFi and Bluetooth. Turn Bluetooth on and connect your Bluetooth device. Wait 10 seconds and turn on WiFi. After this WiFi will avoid frequency where is Bluetooth device and use free frequencies.
Click to expand...
Click to collapse
But it stutters also when wifi is offline. And on Android 8 I don't have this frequency-problem

00norman00 said:
But it stutters also when wifi is offline. And on Android 8 I don't have this frequency-problem
Click to expand...
Click to collapse
You can solve by adding the the missing codecs, all the routes are still there, xiaomi removed licensed codecs

Downgrade helped as of 30.05.2019
Mi A2 lite
Bought Galaxy Buds. Stuttered and eventually lost connection.
NOTE:What comes ahead is my personal experience (with some software errors that doesnt seem to have effect on our goal) downgrading my MI A2 lite to Oreo.
Downloaded Android Oreo 9.6.11 , ADB and Fastboot, Miflash(latest from site) from links in the beginning of the thread.
Very few proper video tutorials (Indian mostlyXD).
Enabled developer options on my phone (tapping 7 times on build number). In developer options enabled allow OEM unlock and turned on usb debug mode.
Turned off phone and launched it it fastboot mode (hold "volume down" and power button simultaneously). Connect phone to PC via usb.
Open folder on PC where you installed ADB and fastboot software. Launch cmd.exe or smth. In black window type "fastboot oem unlock" Enter. The phone reboots (takes a lot of time dont be alert) and wipes data from your phone. You will see a scary message/warning (disappear s after few sec) that asks you to lock bootloader back.
NOTE: somehow my device did not ask for any confirmations for enabling unlocked bootloader.
NOTE 2: I was trying to do this whole process by video and text guides. Some ppl type commands in cmd "fastboot flashing unlock" and then "fastboot flashing unlock_critical" BUT for some reason this commands did nothing. So all I did is oem unlock command.
After OEM unlock command rebooted phone skip all phone setups and open developer mode again (if it is locked) and in dev options check if "allow oem unlock" and usb debug mode is turned on. Turn off your phone and load it in fastboot mode (volume down+power).
On PC unpack Android Oreo files. It should look like a long name folder with some .bat files and folder (avoid unpacking in place with strange name paths).
Launch MiFlash tool. NOTE: it gave me a prompt for installing drivers and after i pressed it gave an error. It is fixed by creating inside MiFlash tool folder a new folder and naming it "log". Then launch the tool again and press install drivers.
Once you are in MiFlash program there is a ling space where you can insert a file path. You need to copy a file path that leads to your unpacked Android Oreo files (the path should lead inside where the .bat files located). Paste this copied path into MiFlash path bar and press refresh button. If there is no error you can proceed by pressing in the bottom right corner a "clear all" option and in the top right "flash" button. This will install Android Oreo on your mi a2 lite.
After the process is done i had an error in MiFlash program BUT the phone reboots on its own with downgraded Android version. Turn the phone off, load it in fastboot mode, connect via usb and run in ADB folder CMD.exe and run "fastboot oem lock" command. The phone reboots, takes a while.
!!!
After it reboots immediately skip all phone setup menus especially wifi and account options and go straight in settings to unlock developer mode. In developer options TURN OFF AUTOMATIC SYSTEM UPDATES! After it you can finish phone setup process ,accounts, networks and everything else.
An Android message "update available" can pop up. To get rid of it for good simply swipe it slowly A BIT (not all the way) till you see a cog sign (options icon) and there turn of this notification.
Now you can go smoke a cigar. Android 8.1.0 Oreo installed AND it wont update automaticlly to PIE. You can use your bluetooth devices properly (or whatever problems you had).
Have a nice day. Gonna probably go buy Samsung A30. This **** is unacceptable. Pie update rolled out long time ago (Android Q is releasing in 3 months from now) and this stuff is still not fixed. Wtf

Solution
I did a simple step to fix pair
Reboot into safe mode, pair the select device, after pair reboot out the safe mode and you see the device paired.
Cheers
---------- Post added at 10:15 PM ---------- Previous post was at 10:14 PM ----------
I did a simple step to fix pair
Reboot into safe mode, pair the select device, after pair reboot out the safe mode and you see the device paired.
Cheers

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.