Database Info

Recovered from boot loop but constant crashes with older ROM

I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?

I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine

Jst flash a newer modem in recovery

mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.

PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.

Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine

KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.

Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.

Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.

mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.

Rooting LG Lucky (LGL16C)

Can anyone verify that the method posted by Unjustified Dev in this thread will work the the indicated phone model?

Rooted LG Lucky
I rooted using kingroot version 4.8.0 I could use the stock Rom have no download if anyone could help thanks. Its a straight talk lg lucky running 4.4.2 kitkat I'm no computer whiz and I couldn't figure out how or what I needed phone works fine . now I just want to be able to do a factory reset safely if need be only deleted stock apps that I don't use nothing important I hope.

boct1584 said:
Can anyone verify that the method posted by Unjustified Dev in this thread will work the the indicated phone model?
Click to expand...
Click to collapse
I have obtained root on the device today. Ive read that some were able to do it with kingroot on the older versions but all have had no luck on the version with software version L16CV11a and build number KOT49I.L16CV11a. Well i managed to root it today with a certain methid...will post up a guide later after ive written it out...may see if i can further the progress now that ive rooted it.

STOCK firmware??
i got an lg lucky and its stuck in bootloop does anyone know how i could get stock firmware to flash? it goes to factory reset menu but freezes as soon as it starts to do its thing... maybe not fixable??

bonnis.phone said:
i got an lg lucky and its stuck in bootloop does anyone know how i could get stock firmware to flash? it goes to factory reset menu but freezes as soon as it starts to do its thing... maybe not fixable??
Click to expand...
Click to collapse
Depends on if yourlucky was rooted and if you deleted files you should have
Sent from my Nexus 6 using Tapatalk

REV3NT3CH said:
I have obtained root on the device today. Ive read that some were able to do it with kingroot on the older versions but all have had no luck on the version with software version L16CV11a and build number KOT49I.L16CV11a. Well i managed to root it today with a certain methid...will post up a guide later after ive written it out...may see if i can further the progress now that ive rooted it.
Click to expand...
Click to collapse
I have the newer Model LGL16C/4.4.2/Baseband version M8610B-AAAANAZM-1.0.6060/Kernel version 3.4.0+/Build KOT49I.L16CV11a/Software version L16CV11a/"Lucky". Service provider is Tracfone, aka Crapfone. Attempts to root with Kingroot as well as Kingoroot failed, including several apps which claim to root your phone. I paid less than $10 US dollars for this phone and rooting it isn't high on my priority list, however rooting the damn thing has presented a bit of a challenge.
A working guide to rooting this phone would be great.

2k73 said:
I have the newer Model LGL16C/4.4.2/Baseband version M8610B-AAAANAZM-1.0.6060/Kernel version 3.4.0+/Build KOT49I.L16CV11a/Software version L16CV11a/"Lucky". Service provider is Tracfone, aka Crapfone. Attempts to root with Kingroot as well as Kingoroot failed, including several apps which claim to root your phone. I paid less than $10 US dollars for this phone and rooting it isn't high on my priority list, however rooting the damn thing has presented a bit of a challenge.
A working guide to rooting this phone would be great.
Click to expand...
Click to collapse
Give me a few days to write it out...basically if you have the knowledge...what I did was run kingroot while plugged into PC...was a tad tricky but I'll get further into it later...took a few tries
Sent from my Nexus 6 using Tapatalk

REV3NT3CH said:
Give me a few days to write it out...basically if you have the knowledge...what I did was run kingroot while plugged into PC...was a tad tricky but I'll get further into it later...took a few tries
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hey mate,
I hate to be like a noodge, but would you be able to explain how you rooted? Would be so much appreciated.

REV3NT3CH said:
Give me a few days to write it out...basically if you have the knowledge...what I did was run kingroot while plugged into PC...was a tad tricky but I'll get further into it later...took a few tries
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
PizzaMaster said:
Hey mate,
I hate to be like a noodge, but would you be able to explain how you rooted? Would be so much appreciated.
Click to expand...
Click to collapse
Hey so i spent forever trying ro find a root that would work on this. Or a custom ROM anything really. Try going into McAfee Security, setting up an account, go to settings and disable the lock down device option. That was the problem for me at least McAfee was blocking any root from installing. From there i rooted my lucky with kingroot one click root. Hope this helps!

The Easiest Way To Root Your LG Lucky Without a PC
Easy way to install SuperSU on your LG Lucky
Just follow directions
Use KingRoot 4.5.0 app - google KingRoot apk all versions. Download and install apk.
Google replace kingroot with supersu. There will be a few sites popup, Mediafire is where the original .zip file is hosted. You can even search "how to replace/remove kingroot with supersu" here on XDA for more info.
Once you have downloaded the .zip file be sure to extract it to your INTERNAL sd, the script in the zip will not work from your external sd.
Open the extracted file and copy the mrw file to the internal storage, the path should look like /storage/emulated/0/mrw.
Now go to the play store, download and install Terminal Emulator. I use the one by Jack Palevich as it is only 551kb and easy to use.
Open the terminal emulator and type "su" in order to grant super user permission to the emulator,
On the next line type "/system/bin/sh - /storage/emulated/0/mrw/root.sh" and press enter.
Now the script will run and open up SuperSU automatically. Install binary when prompted with the "normal" option. Choose yes when it asks if you want to delete other superuser apps. (this removes kingroot).
Before rebooting phone, go into the settings of SuperSU and enable pro mode, change icon if you wish, enable survival mode, enable su during boot. I think you have to restart app at this point, can't remember as I did this months ago. Then restart the SuperSU app, go back into settings to Install SuperSU into system. Reboot phone,
When phone reboots, this is when Kingroot is finally uninstalled. Your phone will still be rooted with SuperSU. At this point you may wish to update SuperSU as this is version 2.46 and the newest version is 2.71 Beta. You can get the newest version of SuperSU from the thread here on XDA.
(thanks MrWolf for the script to make the change and thank you Chainfire for SuperSU, FlashFire, CF.lumen, etc...)

LGL-16C successfully (so far) rooted using Kingoroot.exe (latest version). Had to change from mtp to camera on USB then was recognized. Have SuperSU 2.72, SuperSU Pro, BusyBox Pro, and Xposed installed with Xblast and Lucky Patcher running. No custom recovery or roms available and I have searched hi and lo. Was a Net10 $15 phone with nothing to lose, so...will try more stuff out another day and post again.

mikemc63 said:
LGL-16C successfully (so far) rooted using Kingoroot.exe (latest version). Had to change from mtp to camera on USB then was recognized. Have SuperSU 2.72, SuperSU Pro, BusyBox Pro, and Xposed installed with Xblast and Lucky Patcher running. No custom recovery or roms available and I have searched hi and lo. Was a Net10 $15 phone with nothing to lose, so...will try more stuff out another day and post again.
Click to expand...
Click to collapse
Until any source is made there will be no recovery or ROM and tbh I don't have the time to dig into it currently.. The positive with rooting though is removing the bloat
Sent from my Nexus 6 using Tapatalk

REV3NT3CH said:
Until any source is made there will be no recovery or ROM and tbh I don't have the time to dig into it currently.. The positive with rooting though is removing the bloat
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hi. Could you tell me how you installed supersu after rooting with kingroot? Thanks

Well I have root and supersu installed but it won't update binary. Any help out there? Thanks

Hey everybody. I did it!! Just root with kingroot 4.5 and replace kinguser with super sume. Worked great. All kingroot stuff is gone!! Ive rebooted 3 times to make sure and all is good.

Well if anyone is interested in looking at the source code, lg support has downloads available for nearly every phone they've ever made.
http://opensource.lge.com/osList/list?m=Mc001&s=Sc002
The file for the LGL16C is on page 2. Every thing seems to be listed alphabetically so it's easy to locate.
I still have my lucky and actually use it often although I no longer have it activated.

@ cecnwv,
Thanks for the link. Using Ares 11 and got "IP banned for 6 hours,try again later" after dbl tppng yellow icon. I did something wrong. Not at my PC. (unfortunately)
Thanks for any enlightenment,
michaeltheclyde
Two 10a LGL16C Tracfones, one free (recon from Tf) and one new $14.95 @ eBay from Best Buy, rooted with everything that has Google in the name frozen (TB) but no image to restore. (twrp)

Has anyone made a complete backup of their system apps using Titanium Backup? Being that one can't use fastboot/download mode (this phone has it locked out and a special USB cable is required) so my backup options were limited. I thought I did a full backup with Titanium Backup, but apparently lost it as I only found a small partial one on my PC.
Issue is I had uninstalled some bloatware and integrated updates for a few apps. But after factory resetting the phone it is behaving a bit odd. The notification bar doesn't really work anymore (apps still able to use sound/vibration to make a notification, but nothing appears in the notification bar) and I am unable to call the phone because it never rings and it immediately goes to voice mail. So the phone app is borked too.
Plus soft button to the right of the home button (I forget what it's called) doesn't bring up the app history anymore so I can't close background apps. (the volume buttons also don't really do anything anymore. Normally using them causes the volume bar for ringtone to appear and if using a media app, the volume bar for media audio comes up instead. But now nothing happens).
The phone is in a pretty broken state and even doing app updates from Play Store doesn't work anymore. Was gonna try and look around if someone has some app/data backup of the system apps installed. This is a TracFone branded phone and is currently running Android 4.4.2 (Kernel version 3.4.0+). Which is the last Android update they made for this phone.
Perhaps there's a single service/app that is responsible for notifications/volume bar that is borked. But I have no idea which system app is broken so a full app restore is my next best option.
The first thing wrong I noticed after resetting it was that the intial setup screen would return everytime I rebooted the phone. (only way i could get that to stop was freezing it in Titanium Backup). So maybe related to that app somehow. I don't recall ever uninstalling/merging update data for that perticular app though so it's probably a side effect of a different app going haywire.
EDIT:
Ok looks like I resolved the issue. I just removed the LGStartupWizard.apk then did a factory reset via Volume Down+Power button combo. It boots straight to home menu now and everything works. I guess the LG setup wizard thing got borked somehow. No more setup wizard but verious things like google account and whatnot can be configured manually via settings so no real loss.
All the missing things like the app history button, lock screen, notification bar, etc are now working as a result of resetting after removing LGSetupWizard.apk.

Apache Thunder said:
Has anyone made a complete backup of their system apps using Titanium Backup? Being that one can't use fastboot/download mode (this phone has it locked out and a special USB cable is required) so my backup options were limited. I thought I did a full backup with Titanium Backup, but apparently lost it as I only found a small partial one on my PC.
Issue is I had uninstalled some bloatware and integrated updates for a few apps. But after factory resetting the phone it is behaving a bit odd. The notification bar doesn't really work anymore (apps still able to use sound/vibration to make a notification, but nothing appears in the notification bar) and I am unable to call the phone because it never rings and it immediately goes to voice mail. So the phone app is borked too.
Plus soft button to the right of the home button (I forget what it's called) doesn't bring up the app history anymore so I can't close background apps. (the volume buttons also don't really do anything anymore. Normally using them causes the volume bar for ringtone to appear and if using a media app, the volume bar for media audio comes up instead. But now nothing happens).
The phone is in a pretty broken state and even doing app updates from Play Store doesn't work anymore. Was gonna try and look around if someone has some app/data backup of the system apps installed. This is a TracFone branded phone and is currently running Android 4.4.2 (Kernel version 3.4.0+). Which is the last Android update they made for this phone.
Perhaps there's a single service/app that is responsible for notifications/volume bar that is borked. But I have no idea which system app is broken so a full app restore is my next best option.
The first thing wrong I noticed after resetting it was that the intial setup screen would return everytime I rebooted the phone. (only way i could get that to stop was freezing it in Titanium Backup). So maybe related to that app somehow. I don't recall ever uninstalling/merging update data for that perticular app though so it's probably a side effect of a different app going haywire.
EDIT:
Ok looks like I resolved the issue. I just removed the LGStartupWizard.apk then did a factory reset via Volume Down+Power button combo. It boots straight to home menu now and everything works. I guess the LG setup wizard thing got borked somehow. No more setup wizard but verious things like google account and whatnot can be configured manually via settings so no real loss.
All the missing things like the app history button, lock screen, notification bar, etc are now working as a result of resetting after removing LGSetupWizard.apk.
Click to expand...
Click to collapse
Awesome, this worked for me too, though the issue wasn't exactly the same. When I got the phone it had already been rooted with Kingo at some point and I noticed after resetting it that I had similar problems (it may have had the issues before the factory reset too, I just didn't notice one way or the other). Anyway, I was getting slightly different misbehavior. No recents key, yes, but also no response from the Home key. Pull-down notifications bar was mostly working, but with no visible notifications and I couldn't press the Setup "gear" in top right. My volume buttons and Play Store were fine, though, but I'd noticed that when I tried further factory resets (from the menu, not via hard reset) that it wasn't "really" resetting, as any downloaded files/etc. remained on the phone. I'd tried freezing LGSetupWizard already, but as you noted, that doesn't fix it for whatever reason. Deleting altogether does. Yay. I do wonder what the hell is happening during the root or reset that triggers this problem, though. It behaves as if Setup Wizard was just never completed, so you remain "locked out" of most of the same functions that are unavailable during setup normally. Oh well.
Anyway, as old ten-dollars-or-less type phones go, this isn't the worst I've ever used by a long shot. Heck, it's arguably better than a few other slightly bigger/newer/pricier crap-phones out there! (Looking at you, ZTE Legacy/Quest...) FWIW, I had "ripped" all of the APKs from /system/app and /priv-app for some reason back when I first got this thing, so if they'd be of use to anyone I'll be happy to upload all or individual files. Hell, if anyone can tell me how to do a full ROM dump I'd be happy to do that too, because there's definitely still no official stock image available online that I could find a trace of. (Granted, I don't know if there'd be any way to utilize a non-official backup image anyway or turn it into a flashable KDZ, but that's not my point...)

Thank you, I got my lucky rooted! I'm wondering if anyone ever found any custom ROMs or recoveries for this device. It seems like this was never popular for any of that, but thought I'd ask. Thanks.

SafetyNet fails although the phone is completely stock

Hey guys,
I'm in weird situation. I was debating with myself for a long time whether to unlock the BL or not (Verizon) and decided not to - because I want things to just work.
So I left the system as is and funny as it sound - Android Pay is not working, although I didn't change anything with the phone. It's completely stock, no BL unlock, no flashing no nothing. The only thing I did do was to flash an OTA.
Any thought? Any idea how to fix?
SafetyNet Helper shows "CTS profile match: false".
Another weird issues I'm having that might be related:
ֿIf I clear Data for Android Pay I get "MTP Host has stopped" message (force close message). Then - I can't charge the phone and I need to restart it.
After restarting though - The system goes back to the previous version (October patch)! That's the one that was before the OTA. Then I get the android upgrade notification (for November, the version I was on when it all started).
SUPER WEIRD!

don_alberto said:
Hey guys,
I'm in weird situation. I was debating with myself for a long time whether to unlock the BL or not (Verizon) and decided not to - because I want things to just work.
So I left the system as is and funny as it sound - Android Pay is not working, although I didn't change anything with the phone. It's completely stock, no BL unlock, no flashing no nothing. The only thing I did do was to flash an OTA.
Any thought? Any idea how to fix?
SafetyNet Helper shows "CTS profile match: false".
Another weird issues I'm having that might be related:
ֿIf I clear Data for Android Pay I get "MTP Host has stopped" message (force close message). Then - I can't charge the phone and I need to restart it.
After restarting though - The system goes back to the previous version (October patch)! That's the one that was before the OTA. Then I get the android upgrade notification (for November, the version I was on when it all started).
SUPER WEIRD!
Click to expand...
Click to collapse
What if you uninstall the AP app and reinstall?

quangtran1 said:
What if you uninstall the AP app and reinstall?
Click to expand...
Click to collapse
Tried that. Also deleting data. It's unrelated because the SafetyNet doesn't work.
Anyway, I flashed a factory image and It works now.

i have a pixel 2 on Android P

So I have a Google Pixel 2 and I installed the android P preview via sideload but I had my bootloader locked now I can try to toggle OEM unlock and put in my pattern but after I put my password in it still says it's off idk what to do I haven't tried to flash the 8.1 factory image or unlocking yet but idk if I'll be able too there's I'm almost 100,% sure it's not a Verizon model I don't have any Verizon apps and on 8.1 I could toggle this on and it's not greyed out

I am also not able to change this in the preview, maybe you could install the 8.1 OTA (afterwards a factory reset)to go back. Flashing a factory image will not work with a locked bootloaded, OTA also works with locked BL.

EnormoDerClown said:
I am also not able to change this in the preview, maybe you could install the 8.1 OTA (afterwards a factory reset)to go back. Flashing a factory image will not work with a locked bootloaded, OTA also works with locked BL.
Click to expand...
Click to collapse
That wouldn't brick my phone?

Before you attempt anything extreme, I suggest factory reset your phone and do the minimal setup to get into the settings and try toggling

I did still no luck

To be fair: i can not guarantee that, but i can just imagine 3 scenarios:
1. Update fails, OTA install fails
2. OTA installs but a lot of FC´s with apps (factory reset afterwards shoudl get rid of that)
3. Everything installs and is functional without doing anything (i don´t think so).
i would expect, that option 2 would occure

Installation failed, called Google to see if they could do anything they only referred me to the Android beta website, guess I'm stuck till DP2 comes out

AaronGavin said:
Installation failed, called Google to see if they could do anything they only referred me to the Android beta website, guess I'm stuck till DP2 comes out
Click to expand...
Click to collapse
This is a long shot, but try disabling your lock screen security PIN if you have one, then check the setting again. If still greyed out, try setting a PIN, then check again. This typically prompts for your PIN, maybe somehow something got messed up in the sideload.

March update could just be to old, April update could work because of newer data. OTA checks whether the update is older/newer.

quakeaz said:
This is a long shot, but try disabling your lock screen security PIN if you have one, then check the setting again. If still greyed out, try setting a PIN, then check again. This typically prompts for your PIN, maybe somehow something got messed up in the sideload.
Click to expand...
Click to collapse
That actually worked xD thank you

AaronGavin said:
That actually worked xD thank you
Click to expand...
Click to collapse
Glad to hear. Did it become un-greyed without lock screen security, or after it was re-enabled? I have seen similar behavior before, so I thought it might be the same thing in P.

quakeaz said:
Glad to hear. Did it become un-greyed without lock screen security, or after it was re-enabled? I have seen similar behavior before, so I thought it might be the same thing in P.
Click to expand...
Click to collapse
It was never greyed out just after I put my password in it wouldn't turn on the slider and at first I just thought maybe it is on but bugged out but after I removed my password it just turned on properly I'm about to test it as soon as the factory image downloads again

quakeaz said:
Glad to hear. Did it become un-greyed without lock screen security, or after it was re-enabled? I have seen similar behavior before, so I thought it might be the same thing in P.
Click to expand...
Click to collapse
Back on 8.1 ?

Where can I download A2020U stock Android 9 image?

After upgrade to Android 10, GPS is having issues. It takes long time to fix a location. Tried all kind of solutions suggested on forums. Tried many apps for clearing, updating AGPS data. Nothing worked permanently.
Did anyone else faced similar issues on A2020U pro?
Also, sometimes notifications from app stopped showing. After I turn off Wifi and when data switches to LTE, I see all older notifications pop up.
I believe it's issue with Android 10. Is there possibility of rollback to its stock Android 9. I saw another thread where OP mentioned that it can be rolled back using the system update, but for that I need to have stock image on sdcard.
For rollback from stock 10 to stock 9, do I need to root/unlock bootloader/or install TWRP?

ccraze said:
After upgrade to Android 10, GPS is having issues. It takes long time to fix a location. Tried all kind of solutions suggested on forums. Tried many apps for clearing, updating AGPS data. Nothing worked permanently.
Did anyone else faced similar issues on A2020U pro?
Also, sometimes notifications from app stopped showing. After I turn off Wifi and when data switches to LTE, I see all older notifications pop up.
I believe it's issue with Android 10. Is there possibility of rollback to its stock Android 9. I saw another thread where OP mentioned that it can be rolled back using the system update, but for that I need to have stock image on sdcard.
For rollback from stock 10 to stock 9, do I need to root/unlock bootloader/or install TWRP?
Click to expand...
Click to collapse
I had a minor issue with my wifi after updating to A10, was fighting with my router. Googled it and basically A10 in general has issues... some people said they were resolved by clearing the dalvik cache. I never got around to trying it and over time the issue seems to have gone away.
Anyhow, the best way to downgrade currently is the EDL tool and firmware package I put together (for exactly this reason). You don't need to root/unlock.
Here's the tools: https://forum.xda-developers.com/t/...ded-edl-tools-new-fixes-general-tips.4174667/
And here's the Android 9 firmware: https://forum.xda-developers.com/t/rom-stock-stock-firmware-packages-for-expanded-edl-tools.4194045/
Make sure you do a full backup of your phone, then install the firmware (to make it easy, just install it to both A and B partitions). More detailed instructions are on the tools thread, ask if you have any questions.

bobthenormal said:
I had a minor issue with my wifi after updating to A10, was fighting with my router. Googled it and basically A10 in general has issues... some people said they were resolved by clearing the dalvik cache. I never got around to trying it and over time the issue seems to have gone away.
Anyhow, the best way to downgrade currently is the EDL tool and firmware package I put together (for exactly this reason). You don't need to root/unlock.
Here's the tools: https://forum.xda-developers.com/t/...ded-edl-tools-new-fixes-general-tips.4174667/
And here's the Android 9 firmware: https://forum.xda-developers.com/t/rom-stock-stock-firmware-packages-for-expanded-edl-tools.4194045/
Make sure you do a full backup of your phone, then install the firmware (to make it easy, just install it to both A and B partitions). More detailed instructions are on the tools thread, ask if you have any questions.
Click to expand...
Click to collapse
I tried clearing the dalvik cache after resetting all apps settings. That also didn't work.
Thanks for the links. I will give it a try to downgrade to previous release and will post how it goes.

Thanks @bobthenormal for the image and EDL tool. I finally tried to flash with EDL and A9 image. I could see the GPS working perfectly fine. Also tested various OTA updates, GPS problem actually starts with 1.13 A9 last security update and not with A10 (2.09). Then I reflashed again to the A9 image and have GPS working.
Now, I am having issues with sensors.
Fingerprint sensor is working but other sensors like Acclerometer, Magnetic, Gyro, Light etc are not working.
If I do the Sensor Test in EMODE with code *983*0# I could see All sensors shows "CTS Fail". Is there any mod or any patch that I can use to get sensors working?

ccraze said:
Thanks @bobthenormal for the image and EDL tool. I finally tried to flash with EDL and A9 image. I could see the GPS working perfectly fine. Also tested various OTA updates, GPS problem actually starts with 1.13 A9 last security update and not with A10 (2.09). Then I reflashed again to the A9 image and have GPS working.
Now, I am having issues with sensors.
Fingerprint sensor is working but other sensors like Acclerometer, Magnetic, Gyro, Light etc are not working.
If I do the Sensor Test in EMODE with code *983*0# I could see All sensors shows "CTS Fail". Is there any mod or any patch that I can use to get sensors working?
Click to expand...
Click to collapse
I think you're past what I know... I can only guess. Do you have a backup of your phone before installing any ROMs/firmware changes?
The other thing I would try is flashing the stock bootloader (you'll get that annoying warning on boot is the only downside). A pretty desperate leap of an idea, but I did have a problem that was only resolved by doing this. Sorry I can't be of more help!

Thanks for getting back. I am able to recover. After updating to v1.11 and v1.13 via OTA, sensors started working. But after sometime GPS again started giving issue. So I had to reflash again. Strange thing noticed that when I flash first to Partition B and then A, I see the issue of sensors not working. If I flash B later then it is working. I had to disable auto update otherwise it was updating automatically via OTA to A10. Because of that I re-flashed almost 3-4 times.
To disable auto update I had to stop all networks otherwise it downloads OTA and does not show settings menu. Sometimes it went into boot loop, but setting the correct bootable partition using your tool helped. Finally I am on A9 v1.10 and managed to disable auto update and everything is working fine. GPS is locking in 3-5 secs and no issues with notifications getting stuck when on Wifi. I have kept a backup_all after things are setup, in case required in future.
Your tool is amazing, thank you for sharing and providing detailed steps.

@ccraze I just ran into the same issue with the sensors myself. The last time I re-flashed, I only flashed partition B, because - from earlier experiences = I learned that partition B is the one that matters. So I skipped writing to partition A.
Just to be clear, what you did was this:
1. Run Load Programmer.ps1 - phone should now be connected
2. Ran Write Firmware v1.1.0 to A.ps1 <-- THIS
3. Ran Write Firmware v1.1.0 to B.ps1
4. Ran Set Bootable Partition0 Slot B.ps1
Is that right?

karlovac said:
@ccraze I just ran into the same issue with the sensors myself. The last time I re-flashed, I only flashed partition B, because - from earlier experiences = I learned that partition B is the one that matters. So I skipped writing to partition A.
Just to be clear, what you did was this:
1. Run Load Programmer.ps1 - phone should now be connected
2. Ran Write Firmware v1.1.0 to A.ps1 <-- THIS
3. Ran Write Firmware v1.1.0 to B.ps1
4. Ran Set Bootable Partition0 Slot B.ps1
Is that right?
Click to expand...
Click to collapse
@karlovac The sequence you mentioned is correct. But later I noticed that there is no set sequence which can cause this issue and no specific sequence which can fix it. After my previous post, I tried installing OTA and sensors worked. Then I reflashed it and it worked again. Later by mistake I took the OTA again and saw GPS issues. So reflashed, and then ran into sensor issue again. Again reflashing worked and AFAIK it was not in the sequence mentioned above in your post.
I would say just a matter of luck, I couldn't find exact sequence which can cause this issue. Just try flashing again, most probably you will not see sensor issues. If you still see sensor issues then try installing all OTA till your system is back to A10, meanwhile checking if the sensors are back after every OTA. If you see sensors working, then no need to install all OTAs and reflash with this image to go back to A9 and disable auto updates. Good Luck!

Thanks @ccraze . I already did *one* OTA system update to see if that fixed it but it didn't. My build number is now GEN_NA_A2020U_PROV.1.11
The way I'm testing the sensors is:
1. Open dialer
2. Enter *983*673636# -> this enables EMODE
3. Enter *983*0# -> this opens the testing app
4. Go to sensor test
They all say CTS Fail. (I got that from this thread BTW).
Do you happen to know how many OTA updates there were before you get to the "bad" A10 one? I know the bad build is GEN_NA_A2020U_PROV2.09.

@ccraze success! I did the following:
1. Wiped the cache partition. See this video. It did *NOT* fix the sensors. But apparently it's a good thing to do.
2. Did an OTA update to the next A9 build . My build number is now GEN_NA_A2020U_PROV1.13
After that, my sensors worked again. Thanks for the tips.

karlovac said:
Thanks @ccraze . I already did *one* OTA system update to see if that fixed it but it didn't. My build number is now GEN_NA_A2020U_PROV.1.11
The way I'm testing the sensors is:
1. Open dialer
2. Enter *983*673636# -> this enables EMODE
3. Enter *983*0# -> this opens the testing app
4. Go to sensor test
They all say CTS Fail. (I got that from this thread BTW).
Do you happen to know how many OTA updates there were before you get to the "bad" A10 one? I know the bad build is GEN_NA_A2020U_PROV2.09.
Click to expand...
Click to collapse
Even that is not consistent. Once, I have seen it worked fine till I got all A9 updates. But in one run GPS went bad in first OTA itself. Definitely A10 is bad, but there something else wrong with the A9 OTAs also which mess up the drivers. I would recommend to not take any OTA after flashing with this image.

karlovac said:
@ccraze success! I did the following:
1. Wiped the cache partition. See this video. It did *NOT* fix the sensors. But apparently it's a good thing to do.
2. Did an OTA update to the next A9 build . My build number is now GEN_NA_A2020U_PROV1.13
After that, my sensors worked again. Thanks for the tips.
Click to expand...
Click to collapse
Great! just make sure that OTA is not messing up GPS again. otherwise you might need to reflash and disable auto updates immediately after booting.

@ccraze how did you disable OTA updates exactly? My phone was fine for the last few days, but then it installed the A10 update last night again! I haven't restarted it yet, but it's definitely the A10 one.
I really don't know what else to do. I disabled "automatic system updates" in developer options, *and* I removed the permissions from the system update app.
Is there a different place you disabled OTA updates?

karlovac said:
@ccraze how did you disable OTA updates exactly? My phone was fine for the last few days, but then it installed the A10 update last night again! I haven't restarted it yet, but it's definitely the A10 one.
I really don't know what else to do. I disabled "automatic system updates" in developer options, *and* I removed the permissions from the system update app.
Is there a different place you disabled OTA updates?
Click to expand...
Click to collapse
After you flash the OS, immediately turn off all data (Mobile + Wifi). Then go to Settings->System->System Update->Click 3dots on the top right -> Settings -> Disable all options.
Its easy to see those options if you have all data sources turned off. It will download and will show that update is ready to install but will not install automatically.

I think I did what you're describing, right after I flashed:
However, the update still downloaded, and it sounds like if I reboot the phone, it will automatically install:
I'm afraid to reboot now since I can't afford to lose GPS reliability now.

karlovac said:
I think I did what you're describing, right after I flashed:
View attachment 5338875
However, the update still downloaded, and it sounds like if I reboot the phone, it will automatically install:
View attachment 5338877
I'm afraid to reboot now since I can't afford to lose GPS reliability now.
Click to expand...
Click to collapse
You are not following the menu items that I mentioned before. You should see following screens. Developer options system update is different setting.

Oh man, that's confusing that there are *two different* places to disable auto updates. Very frustrating!
Unfortunately now that the update is downloaded, I can't go into the System Update settings any more. The System Update app is in a state where I can't get to the ... menu. I haven't restarted my phone for 2+ weeks, since I've been traveling, and I couldn't afford for GPS to break.
Do you know if there's a way I can delete the downloaded update, so it doesn't install, using the tools?

karlovac said:
Oh man, that's confusing that there are *two different* places to disable auto updates. Very frustrating!
Unfortunately now that the update is downloaded, I can't go into the System Update settings any more. The System Update app is in a state where I can't get to the ... menu. I haven't restarted my phone for 2+ weeks, since I've been traveling, and I couldn't afford for GPS to break.
Do you know if there's a way I can delete the downloaded update, so it doesn't install, using the tools?
Click to expand...
Click to collapse
Your phone seems to have A/B partition.
So the update is written into the inactive slot.
Check which slot it's using and which slot is inactive.
Then purposely corrupt the inactive slot which contains the update. Make backup of what you change though in case you targeted the wrong stuff.
So the update will fail and the update in the inactive slot will not boot.
Then it will return back to the previous active slot with the old system.
Risk it yourself though. I never had an A/B slot, so can't make sure if it works.

pl1992aw said:
Check which slot it's using and which slot is inactive.
Then purposely corrupt the inactive slot which contains the update. Make backup of what you change though in case you targeted the wrong stuff.
Click to expand...
Click to collapse
Thanks for the feedback! When you say "purposely corrupt the inactive slot", I take it you mean that I should manually corrupt a ROM and then flash it to the inactive partition, right? I've been using the tools here to flash, so there are two scripts - one to write to partition A and one to write to partition B. Do you have any specific suggestions on what I should do to corrupt it - specific file(s) I should delete perhaps, that would guarantee it fails?
Also, to check which slot is inactive, according to this doc, it seems I should run:
fastboot getvar all | grep “current-slot”
Do I have to put my phone in EDL mode to do that, or can I run fastboot without EDL mode. I'm worried that if I put my phone in EDL mode, when I exit out of it, it will reboot. So I'll be past the point of no return.

karlovac said:
Thanks for the feedback! When you say "purposely corrupt the inactive slot", I take it you mean that I should manually corrupt a ROM and then flash it to the inactive partition, right? I've been using the tools here to flash, so there are two scripts - one to write to partition A and one to write to partition B. Do you have any specific suggestions on what I should do to corrupt it - specific file(s) I should delete perhaps, that would guarantee it fails?
Also, to check which slot is inactive, according to this doc, it seems I should run:
fastboot getvar all | grep “current-slot”
Do I have to put my phone in EDL mode to do that, or can I run fastboot without EDL mode. I'm worried that if I put my phone in EDL mode, when I exit out of it, it will reboot. So I'll be past the point of no return.
Click to expand...
Click to collapse
I never had ZTE phones, so can't really be sure about the flashing process.
You don't need to corrupt the whole ROM, you can rather just corrupt the boot partition of the inactive slot with update. Or even just flash a wrong version of boot partition into that inactive slot can corrupt it as well.
Either
Code:
fastboot flash boot_a wrong_boot_file.img
Or
Code:
fastboot flash boot_b wrong_boot_file.img
The corrupt can be done with root or in fastboot, EDL should be not needed.
About which slot is inactive, since your case is complicated that it's going to do an update, the fastboot command to check inactive slot is hard to distinguish.
You may need to use rather command
Code:
fastboot getvar all
It will show like this:
With this, you will be able to see the system version.
eg. ro.build.version (find the correct one yourself, I don't know this phone.)
Before power off, you first find out your current version, so then in fastboot, you check if it's the same as read from fastboot.