Database Info

Stuck on lockscreen - androidui has stopped

Moto G 16GB, bought off Amazon.co.uk. Rooted and flashed 4.4.2 before it was pushed to the device (I think it was an image off US version, found it in these forums back when I got the phone). I've been getting a prompt to install some Motorola US update for a few weeks, it pops up every now and then, has gone away when I tapped "No, thanks" option. All was fine until this morning...this is a really weird problem.
I don't know if the phone updated itself overnight, but when I dismissed the alarm this morning I couldn't get past the lockscreen. I put in my lock code and the phone had the stock wallpaper, then cycled to black background, then back to stock wallpaper and then I got a pop up saying "Unfortunately, the process com.android.systemui has stopped." and I was bumped back to the PIN lockscreen. Tried again, same thing. Now it doesn't even say anything about androidui, just cycles between black background and stock wallpaper and kicks me out.
Tried hooking it up to a PC and Mac, but neither recognized it and the phone appeared to be just charging. Power cycled it a dozen times by holding down the power button for about 6 seconds and I always end up with the same problem of not getting past the lockscreen. Every time I boot the phone now it says "Android is upgrading... Optimizing app 1 of 1". This is why I thought maybe I was pushed some incompatible US update?
Underneath it all the phone works fine, got the alarm this morning, received an SMS, answered a phone call. I can even get to the camera from the lockscreen. Is there any other options besides complete wipe and starting from the beginning again?
Probably OT, but I've always had trouble with the launcher quitting, no matter what launcher I'm using, on Moto G and the previous GNex.
Any help is appreciated, I'm bummed.

Hi,
i've today the same, exactly the same problem. It's strange, because i can't reset my phone to factory default, i went to the recovery menu, then "factory", but it only rebooted...
My "solution":
I reinstalled the original firmware:
http://forum.xda-developers.com/showthread.php?t=2542219
Then all works fine.. No matter why this error occurs.. an automatic firmware update? ..i don't know...

the exact same thing happened to me today out of nowhere and i'm about to leave on a trip, i'm so angry!

Jeez...well, looks like I'm not the only one. WTF happened? I left on a weekend trip too and I'm P.O.'d. I haven't been too religious with my backups either, that's why I was trying to find a way to back things up before wiping it all, but it looks like I'm out of luck. Guess a full wipe is in order.

hmmm i'm a complete dufus when it requires ADB, i've followed the procedures at the link but everytime i try to enter an input cmd says "mfastboot is not a recognized command"
electrictimes said:
Jeez...well, looks like I'm not the only one. WTF happened? I left on a weekend trip too and I'm P.O.'d. I haven't been too religious with my backups either, that's why I was trying to find a way to back things up before wiping it all, but it looks like I'm out of luck. Guess a full wipe is in order.
Click to expand...
Click to collapse
my phone wasn't even rooted, pure stock kitkat, i'm taking my heavy ass old notebook with me and will spend my days off trying to fix this **** it seems

a.monteiro said:
hmmm i'm a complete dufus when it requires ADB, i've followed the procedures at the link but everytime i try to enter an input cmd says "mfastboot is not a recognized command"
Click to expand...
Click to collapse
Take a look:
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot mfastboot-v2.zip (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.

I'm debating if I should go ahead and restore the firmware OR wait for Motorola to right their wrongs!

a.monteiro said:
the exact same thing happened to me today out of nowhere and i'm about to leave on a trip, i'm so angry!
Click to expand...
Click to collapse
Same situation....

ifishy said:
Take a look:
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot mfastboot-v2.zip (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.
Click to expand...
Click to collapse
I... did that, but obviously not the correct way, i'm downloading the files on my note and will try again. Maybe I should unpack the firmware files at some specific place? The instructions said nothing about this so I did nothing.
zofari said:
I'm debating if I should go ahead and restore the firmware OR wait for Motorola to right their wrongs!
Click to expand...
Click to collapse
Just reminded me that my phone is still within warranty, doing this restore may void it?

a.monteiro said:
I... did that, but obviously not the correct way, i'm downloading the files on my note and will try again. Maybe I should unpack the firmware files at some specific place? The instructions said nothing about this so I did nothing.
Just reminded me that my phone is still within warranty, doing this restore may void it?
Click to expand...
Click to collapse
My phone is back working..at the cost of wiping out all my data.

zofari said:
My phone is back working..at the cost of wiping out all my data.
Click to expand...
Click to collapse
Guess this is the only way out of this, then. What a mystery... I wonder if this is the "Welcome to Lenovo" update 1.0 lol.

i'm getting a "missing AdbWinApi.dll" although i've installed all the applications required, any help?
edit: guess i also need the android sdk, right?
edit2: got it, just copy the dlls from the minimal adb directory into the firmware directory and it's good to go, just configuring my newly restored device, thanks all

I wonder why this happened? I was using google play store at the moment, updating the flipboard app...

a.monteiro said:
I wonder why this happened? I was using google play store at the moment, updating the flipboard app...
Click to expand...
Click to collapse
I guess It's the problem of flipboard app!

My father's phone is also experiencing this issue, I can't even reset the phone to factory settings.
This occurred when I was also updating the flipboard app... seriously I'll have to RMA this...
----------------------
So I also have an issue where when you unlock the screen, it just locks back up (no android dialogue saying that com.android.systemui has crashed, but the same result).
I'm also unable to go into bootloader -> Recovery to factory reset the phone.
I stupidly tried to uninstall the flipboard app and reinstall it and it killed the phone... it's now stuck and quite annoying.
I'm 99% sure it's Flipboard.

Looks like others are having issues with Flipboard too
http://forums.androidcentral.com/moto-g/391289-something-seriously-wrong-my-moto-g.html
----------------
I solved the issue by following the instructions here:
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050

how could a flipboard update screw android so badly? what a strange day
edit: they seemed to have pulled the update back or fixed it though, during my restore flipboard installed without issues

Holy S*** I'm in the same situation. It's definitely the Flipboard update that caused everything. Support just acknowledged me but never gave me any solution. I'm running ART and I think that was contributing the problem. It's terrifying knowing how a single app can completely ruin your phone!!
Anyway guys, is there anyway I can save my pics and stuff before I wipe my data?

Good detective work, I now remember updating the Flipboard app w/ bunch of others as well when things were still all good. Could this be remedied if Flipboard would manage to push a working update? I really don't wanna wipe everything, and I'm not sure I can.

Word from Flipboard (via Twitter):
"Flipboard does not support the experimental OS ART at this time."

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.

Any ideas?! because im out of ideas

1. I can only get into phone manager or permission manager when phone is in airplane mode? Strange lol Otherwise it will open for .5 second and close. No toast notification though
2. My memory usage. Normal? Screenshot should be added.

Sorry. 6x rooted L24 model ? using a p9 lite theme

tre717 said:
1. I can only get into phone manager or permission manager when phone is in airplane mode? Strange lol Otherwise it will open for .5 second and close. No toast notification though
2. My memory usage. Normal? Screenshot should be added.
Click to expand...
Click to collapse
Try clearing the app data for phone manager and see.

tre717 said:
1. I can only get into phone manager or permission manager when phone is in airplane mode? Strange lol Otherwise it will open for .5 second and close. No toast notification though
2. My memory usage. Normal? Screenshot should be added.
Click to expand...
Click to collapse
Yes. Memory usage is fine. See mine

shashank1320 said:
Try clearing the app data for phone manager and see.
Click to expand...
Click to collapse
Yes this works, too. But what would make it mess up again? Seems like something is corrupt or something

tre717 said:
Yes this works, too. But what would make it mess up again? Seems like something is corrupt or something
Click to expand...
Click to collapse
These things happen sometimes...so dont worry buddy

Update: On my Phone Manager force closing by its self. Airplane Mode- Works perfectly. Data on Wifi on- force closes.. Data on Wifi-OFF-- works perfectly. Weird? With wifi on it will not work. Also, my wifi is called WLAN?

tre717 said:
Update: On my Phone Manager force closing by its self. Airplane Mode- Works perfectly. Data on Wifi on- force closes.. Data on Wifi-OFF-- works perfectly. Weird? With wifi on it will not work. Also, my wifi is called WLAN?
Click to expand...
Click to collapse
Do you have a phone which is a China varaiant? Because I konw only in China, Wifi is called WLAN due to local regulations...

Since you're rooted I assume you have either a custom ROM, or at the very least, a custom recovery. My personal preference is TWRP.
1. In <insert your custom recovery name here, such as TWRP>, do a full NAND / System backup. (This is a long process but bear with me)
2. Look here on the forums for a "stock" rom in flashable .zip form (NOTE: You will want it to be in .zip as opposed to some sanctioned Huawei/Honor package as that will remove your root). When found , download it and stick it on your MicroSD card somewhere
3. Flash the "stock" rom.
4. Wipe Cache / Davlik / system partitions (Usually this is recommended, but in this case I'd argue it's required)
5. Boot into your stock software
6. Now see if the same exact issue persists. If it does, then you know at least its not hardware or software related and its something in the Honor ROMs. If the issue is gone, then it's "something" in your setup. Once you've at least identified this, you now know what to do next.
7. Boot back into <insert your custom recovery name here, such as TWRP>, and restore the backup you snapped in step 1 (This will bring you back nicely to where you were)
Purpose of this exercise: To determine if your issue exists stock-software in a "factory reset" condition, or if it's something funky with how you setup our phone / software / apps / etc.
I know this is long-winded, but it should clarify a few things for you.
"I'm just here so I won't get fined.....errr so I can 'participate' in the Honor 6x sweepstakes"

jerryhou85 said:
Do you have a phone which is a China varaiant? Because I konw only in China, Wifi is called WLAN due to local regulations...
Click to expand...
Click to collapse
Here is the thing.
Phone, boot looped first time unlocking it. So I downloaded a update zip and extracted the update.app and flashed the stock.img
Then I did the same with the firmware for my model L24 (because it wasn't out there at first)
So it seems something didn't get "wiped" when I flashed the image from the L24?

tre717 said:
Here is the thing.
Phone, boot looped first time unlocking it. So I downloaded a update zip and extracted the update.app and flashed the stock.img
Then I did the same with the firmware for my model L24 (because it wasn't out there at first)
So it seems something didn't get "wiped" when I flashed the image from the L24?
Click to expand...
Click to collapse
...That's too complex...maybe you should try to get your phone to flash all the files from a same ROM

So I went back and downloaded the L24C900B110 from the honor.ru site. And still it shows WLAN?
Another thing I noticed. Using Zooper widget, the location is India?? Maybe that firmware isn't for the bln-l24? But I thought that was the US version, not the India version.

[FIRMWARE-ONLY][MI MIX][LITHIUM] Developer ROM Firmware

News :
Starting today, i'll just upload the firmware if it has a change in it.
So you know there's no need to update the firmware if there's no change in it, save the hassle.
Tips :
* I've added checksum file for each firmware-only files in google drive, so you guys can see what's changed on every firmware-only release.
* If you experience sim card not detected after flashing firmware, don't worry, it's normal. do this, plug out and plug in your sim card tray, and restart your device.
[FIRMWARE-ONLY]
Recommended : 9.2.21
Latest : 9.2.21
https://drive.google.com/drive/folders/1PGmzEcmgG0XhRB7110CDDTgMwmw4N3MM
[ROMS - CHINA]
http://www.miui.com/download-323.html
[ROMS - GLOBAL]
http://en.miui.com/download-317.html

yep i believe the Miui10 is in Alpha and currently being tested by a closed group of users. we should see public Beta releases towards the end of June.
Im just curious if there is any difference in battery consumption to previous version of MIUI.

I've tried it a couple of days ago. There are some visual changes like new notifications panel UI, recents UI, In-call UI etc. A bit more IOS-ish as some say.
First of all, if you consider flashing it;
- You need the Raupe/Blunden twrp to flash it, other recoveries end up with error 7.
- After flashing this build; twrp will ask for a decrypt password and no password will be correct. So your internal storage won't be mounted on twrp no way to fix it at the moment.
- Magisk 16.4 is able to root it, don't know about previous ones.
- If you consider flashing other roms, you have to do factory reset(format data) to get your internal be able to mount on twrp again.
- It doesn't have google apps as it's China specific, so you need to install google apps manually by Google installer apk or there are zip files for miui 10 ported gapps which give force closes randomly.
- Can be a daily driver since all is working.
- Xposed won't work.
Other than these hick ups, it's good initial build. Fast and smooth, can't tell about battery life since I haven't used it for a long time. There are secondary releases(8.6.5) for some devices so can be around for Mix too. Cheers.
Sent from my Xiaomi Mi Mix using XDA Labs

Konstantine34 said:
I've tried it a couple of days ago. There are some visual changes like new notifications panel UI, recents UI, In-call UI etc. A bit more IOS-ish as some say.
First of all, if you consider flashing it;
- You need the Raupe/Blunden twrp to flash it, other recoveries end up with error 7.
- After flashing this build; twrp will ask for a decrypt password and no password will be correct. So your internal storage won't be mounted on twrp no way to fix it at the moment.
- Magisk 16.4 is able to root it, don't know about previous ones.
- If you consider flashing other roms, you have to do factory reset(format data) to get your internal be able to mount on twrp again.
- It doesn't have google apps as it's China specific, so you need to install google apps manually by Google installer apk or there are zip files for miui 10 ported gapps which give force closes randomly.
- Can be a daily driver since all is working.
- Xposed won't work.
Other than these hick ups, it's good initial build. Fast and smooth, can't tell about battery life since I haven't used it for a long time. There are secondary releases(8.6.5) for some devices so can be around for Mix too. Cheers.
Click to expand...
Click to collapse
I'm willing to give this a shot, thanks for the input ??

Ok trying it now and everything seems to be working good. A little laggy at the moment so I'm just letting it set in. I was hoping the camera would've gotten updated but same old crappy camera software from previous MIUI firmware. Hopefully when they do release the final version we'll get a updated camera but all in all this is a keeper till we get updated version on here, hopefully...

juggaknot77 said:
Ok trying it now and everything seems to be working good. A little laggy at the moment so I'm just letting it set in. I was hoping the camera would've gotten updated but same old crappy camera software from previous MIUI firmware. Hopefully when they do release the final version we'll get a updated camera but all in all this is a keeper till we get updated version on here, hopefully...
Click to expand...
Click to collapse
Have face unlock maybe?

zrzatore said:
Have face unlock maybe?
Click to expand...
Click to collapse
Haven't tried that but I'll look into it today and report back.
---------- Post added at 04:27 PM ---------- Previous post was at 03:36 PM ----------
Ok going through settings and as far as I can tell I don't see face unlock feature. I highly doubt the mix will get seeing as how old it is now, I never use it anyway on other devices so it's not a big deal to me. Everything is running very smooth and fast, I'm liking the Android P style look a lot, more than how it looks on the pixel but that's just me.

How did you go past decrypt after flashing via TWRP?

Wmateria said:
How did you go past decrypt after flashing via TWRP?
Click to expand...
Click to collapse
You just cancel it and internal storage will be unable to use on twrp. If you flash other things, you need to do it by an OTG.
Sent from my Xiaomi Mi Mix using XDA Labs

Konstantine34 said:
You just cancel it and internal storage will be unable to use on twrp. If you flash other things, you need to do it by an OTG.
Click to expand...
Click to collapse
Oh yes yes, I always use OTG just in case. Thanks for the info.

I installed it, but I keep loosing the recovery, when I reboot it goes to the Miui recovery.
Is there a way to disable the factory recovery overwriting the twrp.
Appreciate any help.
Thanks.

Konstantine34 said:
You just cancel it and internal storage will be unable to use on twrp. If you flash other things, you need to do it by an OTG.
Sent from my Xiaomi Mi Mix using XDA Labs
Click to expand...
Click to collapse
doesn't it will be solved just by formatting data?

fatouraee said:
I installed it, but I keep loosing the recovery, when I reboot it goes to the Miui recovery.
Is there a way to disable the factory recovery overwriting the twrp.
Appreciate any help.
Thanks.
Click to expand...
Click to collapse
i think you should flash this file in twrp :
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
after that the recovery shouldn't get replaced anymore.

That's weird I don't have any issues seeing my storage in TWRP, everything works.

juggaknot77 said:
That's weird I don't have any issues seeing my storage in TWRP, everything works.
Click to expand...
Click to collapse
really? can you show us the screenshot of the storage in twrp? what twrp version did you use? what other procedure did you perform in order not to encrypt storage? thanks

Thanks. That seems to have worked.

fatouraee said:
I installed it, but I keep loosing the recovery, when I reboot it goes to the Miui recovery.
Is there a way to disable the factory recovery overwriting the twrp.
Appreciate any help.
Thanks.
Click to expand...
Click to collapse
You need to delete
- system/etc/recovery-resource.dat
- system/bin/install-recovery.sh
- system/recovery-from-boot.p

rhong said:
really? can you show us the screenshot of the storage in twrp? what twrp version did you use? what other procedure did you perform in order not to encrypt storage? thanks
Click to expand...
Click to collapse
Honestly I didn't do anything different, followed the instructions on the 1st post, everything works on my end.

juggaknot77 said:
Honestly I didn't do anything different, followed the instructions on the 1st post, everything works on my end.
Click to expand...
Click to collapse
i think he should need to format his Data and Internal Storage.
i can't remember the detail, but i once encountered this too, and i read that something about F2FS not supported or whatsoever.

heindrix said:
i think he should need to format his Data and Internal Storage.
i can't remember the detail, but i once encountered this too, and i read that something about F2FS not supported or whatsoever.
Click to expand...
Click to collapse
It's weird I didn't format anything, just updated twrp, backed up my rom, wiped everything, installed new miui 10, installed magisk, wiped cache and dalvik and everything works perfectly...

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.