Database Info

[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...

My OnePlus 6 a6000 is crashing and rebooting

My oneplus 6 A6000 is always crashing when something new is opened. Random apps make the phone freeze and it randomly reboots from boot animation and in splash screen. I cant update my software via local it always fails. I cant update my software via OTA it is says signature failure at 95%
my phone was recently bricked with a RED warning "your phone is corrupted...." I fixed the warning with MSM downloader tool. I am out of options.
I tried to flash a custom ROM but I Am stuck in step 1 that to flash OOS it says error 28
Updated via MSM tool Tried to go to 10.3.0 it crashes from Welcome Logo
via MSM tool Tried to go to 9.0.8 it crashes too
I also notice some lines in the screen. I had a chance to take a screenshot of it and it shows in the screenshot. it means its not an LCD problem.
please help me developers

Ok, so feels like you have some unofficial oos or firmware installed...can you tell me more about your situation?
What OOS you are using?
Are your bootloader unlocked?
Do you have root?
What firmware installed with MSM tool?
When in MSM tool you wiped everything or only data?
What twrp you are using?...
Please provide some info...and if you can, upload that screenshots so we can see that lines....maybe you phones battery is dead or maybe something with hardware i guess...

It all started when I updated to 9.0.9 pie it is stable version. I flashed oxygen os 5.1.5 via msm tool to remove the red warning. The only twrp I tried is for Android Q ( I updated my system to 10.3.0 via MSM tool). Yes I tried to unlock bootloader and try to flash a ROM I got stuck in a step where I need to flash an OOS the version is right. I dont know what causes the error. Pls ignore the 2nd error in screenshot I accidentally pressed that. Thank you I will get back to you for the screen DIAGONAL lines it is small I also notice if something new appear to the screen the phone freezes and restart.

Ok, what twrp version you are using?...and pls...try to format data withing twrp and then enable mtp and flash latest oxygen again...but your zip is not the latest one...it should be Oneplus6oxygen os 042...but format everything when it says type yes...try this and talk back...
And feels like it is hardware problem...

Here is the screenshot of lines appearing randomly.
I tried that nothing happend. Still that warning yes it is 042 and i am using EvolutionX rom it reboots but Not too much

Twrp is 3.3.1-17 Q

Did you try to format your phone?
PecanTastic said:
My oneplus 6 A6000 is always crashing when something new is opened. Random apps make the phone freeze and it randomly reboots from boot animation and in splash screen. I cant update my software via local it always fails. I cant update my software via OTA it is says signature failure at 95%
my phone was recently bricked with a RED warning "your phone is corrupted...." I fixed the warning with MSM downloader tool. I am out of options.
I tried to flash a custom ROM but I Am stuck in step 1 that to flash OOS it says error 28
Updated via MSM tool Tried to go to 10.3.0 it crashes from Welcome Logo
via MSM tool Tried to go to 9.0.8 it crashes too
I also notice some lines in the screen. I had a chance to take a screenshot of it and it shows in the screenshot. it means its not an LCD problem.
please help me developers
Click to expand...
Click to collapse
Sometimes issues like that occur when I change some things in mine and don´t wipe the data [Mine is an A6003]

Yes I did try to format data. I tried to install TWRP in. 8.1 oreo OOS 5.1.11 Blu spark twrp 3.2.3-x. "fastboot boot twrp.img" and it completes but stuck in oneplus logo fast boot mode.
I had only access to twrp in Q 10.3.0 twrp version 3.3.1-17-Q ( this is the only Custom recovery worked )
I tried pie 9.0.8 flash twrp "fastboot boot twrp.img" it is also stuck in oneplus logo fastboot mode

Maybe this will help? The package box of my phone
Problem started after Pie OTA update. Black screen and random reboots
it was sold with OxygenOS installed

Bump

Read and write speed
My read and write speed is 749mbps(read)
0mbps(write) any way to fix this? Maybe this is the problem

If those problems are purely software-related, and I think there's a good chance they are, I'd say one of the more critical partitions on your phone got corrupted at some point, somehow. Using MSMDownloadTool to fix this is a bit of an overkill imo, and the method below has always worked for me when I messed something up while switching between OOS and custom ROMs so I reckon it's pretty good. Also, full-proof. Essentially just do as follows:
0. Make a backup. Always!
1. Download the newest OOS version from this thread (direct link to 10.3.1)
2. Unpack the zip to whichever location on your PC suits you best.
3. One of the files inside will be an archive (also .zip if I recall correctly) with all the partition images. Unpack all its contents to the main directory where the rest of the files are.
4. There will also be a folder with different .bat files corresponding to what partitions you'd like to flash (as per the flasher advanced guide section in the thread from point 1) - grab the one named flash-all-partitions.bat and copy it to the main folder as well.
5. Boot the phone into fastboot mode and connect it to PC, and finally
6. Launch the script from point 4, agree to the data wipe, and wait. Flashing the whole thing will take a while, but hopefully it'll solve your problems

Hello, I followed all the steps still no luck. Random apps cause the phone to crash systemUi. Which leads to boot from bootanimation Anyone please help me too sad oneplus has no emergency download tool

PecanTastic said:
Hello, I followed all the steps still no luck. Random apps cause the phone to crash systemUi. Which leads to boot from bootanimation Anyone please help me too sad oneplus has no emergency download tool
Click to expand...
Click to collapse
MSMDownloadTool is the emergency download tool. Anyway, what you did is you literally just reflashed all of your phone's partitions, on both slots, so either the issue is hardware, or...I don't know. What happens when you boot your phone in safe mode (hold the reboot, err, icon that appears after holding the power button for a few seconds, until a popup with info about safe mode appears)? Do apps still crash?
Oh, one more thing (blind guess really, but yeah) - are you, by any chance, a beta tester for the Android System WebView app or Google Play Services? If you are, switch back to stable channel via Play Store and update the respective apps. Tell me, if that changed anything. (Also, if you could check the WebView implementation version in the settings, that would be great (just use search)).
Edit: out of curiosity, what happens when you try to update the phone via the local update function (to 10.3.1, just download the full OTA zip this time instead of the fastboot-compatible one)? Does it work without issues or not really?

One thing I noticed is writing speed is instant e.g. sending
OKAY [19.294]
Write[0.000]
Sometimes it is [-0.000]
i need a tool to reset internal partition or anything main slot for boot is "b"
It does not update via local.
I will try that playstore thing but I doubt it

McAwesomePL said:
MSMDownloadTool is the emergency download tool. Anyway, what you did is you literally just reflashed all of your phone's partitions, on both slots, so either the issue is hardware, or...I don't know. What happens when you boot your phone in safe mode (hold the reboot, err, icon that appears after holding the power button for a few seconds, until a popup with info about safe mode appears)? Do apps still crash?
Oh, one more thing (blind guess really, but yeah) - are you, by any chance, a beta tester for the Android System WebView app or Google Play Services? If you are, switch back to stable channel via Play Store and update the respective apps. Tell me, if that changed anything. (Also, if you could check the WebView implementation version in the settings, that would be great (just use search)).
Edit: out of curiosity, what happens when you try to update the phone via the local update function (to 10.3.1, just download the full OTA zip this time instead of the fastboot-compatible one)? Does it work without issues or not really?
Click to expand...
Click to collapse
Apps don't crash when Im in safe mode but i can only access system apps. Thank you for helping dude.

Maybe this will explain something?

PecanTastic said:
One thing I noticed is writing speed is instant e.g. sending
OKAY [19.294]
Write[0.000]
Sometimes it is [-0.000]
i need a tool to reset internal partition or anything main slot for boot is "b"
It does not update via local.
I will try that playstore thing but I doubt it
Click to expand...
Click to collapse
Some partitions are fairly small, so they should be transferred to the device pretty much instantly, although I'm not sure if the time should show null ([-0.000]).
If OTA still doesn't work however, then the problem seems to be somewhere else entirely, so the Playstore thing probably won't help, yes.
PecanTastic said:
Apps don't crash when Im in safe mode but i can only access system apps. Thank you for helping dude.
Click to expand...
Click to collapse
Heeeey, we're getting somewhere!
-------------------------------------------
Edit: wait, are the user apps the only ones crashing (when not in safe mode)? Or are system apps crashing too?
-------------------------------------------
The safe mode is designed in such a way that no services other than system ones can run while using it - it's mostly for troubleshooting, same as e.g. in Windows. Not sure where that leads us, but there is a chance one of your apps/widgets/whatever might be causing this issue in that case, although I'm not sure how an app would impact the OTA functionality. Regardless, what you can check is whether you're able to perform a local update while in safe mode. You can also download the OTA zip again just to be sure it's not corrupted and that if the installation fails, it's not the update package's fault (and remember to use the full 1.something GB zip, not just the delta package!).
One other thing to try if the above fails is to reflash the critical partitions using the fastboot-compatible update zip and an appropriate script from within it. No idea if that's going to help, especially considering the fact those partitions should have been reflashed along with the rest using the script I mentioned a few posts earlier, but I reckon it's worth a try if everything else fails - troubleshooting is a trial-and-error process, all in all.
...also, np - hope you manage to fix your phone's issues eventually!
---------- Post added at 02:26 PM ---------- Previous post was at 01:59 PM ----------
PecanTastic said:
Maybe this will explain something?
Click to expand...
Click to collapse
Not really, no, unfortunately - if I understand the information from the photo correctly, the only reasons for your device powering off were holding the power button [1] and using the keypad [3] (tapping the power off icon from the power menu?), which is, well, a normal way to turn a device off.

Pls just use MSMDownload tool insted....i can give you a link if you want but you can just google it

James Blode said:
Pls just use MSMDownload tool insted....i can give you a link if you want but you can just google it
Click to expand...
Click to collapse
He used it actually, as mentioned in the OP, but to no avail.

Android 11 Upgrade by mistake - can I downgrade to 10 without losing data?

Topic says it all. I REALLY didn't want to upgrade. I think it downloaded on its own and I had system update on reboot checked.
Can I reflash the factory image for Android 10 without losing all of my data or am I screwed and stuck with 11?

Yeah I just got forcefully upgraded to Android 11.
I turn my phone off every night and when I turned it on this morning it took a lot longer than normal and then I had Android 11. Very annoying

I'm not happy about it and didn't know that Google actively pushes OTA updates as background downloads. I had the update services that I know of disabled and it stealth updated anyway.
I had to flash factory reset and wipe all data to get back. Now I'll be paranoid every time I have to reboot.

The new screenshot system is weird. I used to screenshot from the menu by holding down the power key but you can't do that anymore.

Android 11 is better than 10.
The new way it handles notifications.
Media controls.
The Google Pay, and home shortcuts on the power button.
Android 11 is one of the reasons I bought the Pixel 4a

WAusJackBauer said:
The new screenshot system is weird. I used to screenshot from the menu by holding down the power key but you can't do that anymore.
Click to expand...
Click to collapse
Just delete .nomedia folder in Files and you can take screenshot again.

digger16309 said:
I'm not happy about it and didn't know that Google actively pushes OTA updates as background downloads. I had the update services that I know of disabled and it stealth updated anyway.
I had to flash factory reset and wipe all data to get back. Now I'll be paranoid every time I have to reboot.
Click to expand...
Click to collapse
Oy - if you prefer stagnation pixel devices are clearly a poor choice

a121232 said:
Just delete .nomedia folder in Files and you can take screenshot again.
Click to expand...
Click to collapse
That sounds a bit odd, are you sure?

AstroDigital said:
Android 11 is better than 10.
The new way it handles notifications.
Media controls.
The Google Pay, and home shortcuts on the power button.
Android 11 is one of the reasons I bought the Pixel 4a
Click to expand...
Click to collapse
Ugh. This isn't a debate thread. There are perfectly valid reasons to stay on A10. I will not engage in the debate though.

Can we downgrade to 10?mine shipped with Android 11 from fi
But there's no twrp for Android 11 or roms

TheUndertaker21 said:
Can we downgrade to 10?mine shipped with Android 11 from fi
But there's no twrp for Android 11 or roms
Click to expand...
Click to collapse
You could flash the A10 factory image through the Google flash tool if you don't mind also wiping data.

TheUndertaker21 said:
Can we downgrade to 10?mine shipped with Android 11 from fi
But there's no twrp for Android 11 or roms
Click to expand...
Click to collapse
You can unlock your bootloader and flash-all the last a10 factory image.
I'm on superior os and it's android 11. Give it a try before you roll back.

This is in no way a deal breaker but man the Pixel 4a has issues with firmware updates.
I shutdown my phone every night and upon every boot up it checks for newer firmware but despite this, I didn't get a notification for the November security update. I had heard it was out but kept waiting and then I manually searched for firmware updates and it was there....
Get it together Google.

WAusJackBauer said:
This is in no way a deal breaker but man the Pixel 4a has issues with firmware updates.
I shutdown my phone every night and upon every boot up it checks for newer firmware but despite this, I didn't get a notification for the November security update. I had heard it was out but kept waiting and then I manually searched for firmware updates and it was there....
Get it together Google.
Click to expand...
Click to collapse
You can go under developer options and disable automatic system updates and it won't install updates.

If your phone is not the google store version with unlockable bootloader than you CAN NOT flash images and go back to previous versions. If you are able to unlock bootloader, than you can go back but you can't save your data. It will result in phone being stuck at animation screen if you do. You can however, use swift backup like I do, and backup your apps and data with rooted phone, and restore them later. Titanium Backup hasn't been updated in so long that I don't recommend that.

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.

Android 12 Beta

I'm thinking of trying out Android 12 Beta soon. Anybody try it out? Any bad bugs?

better wait , my phone is stuck in setup process "keep date from old phone" > "enter pin" > keep data from..." blabla

Seems great to me. No issues whatsoever!

I cleaned flashed to it from DP3 yesterday. Loving it so far! And I wasn't sure about some of the UI changes from the leaked photos.
The bugs I'm getting are:
Bubbles work, but there's a messages 'screen' that opens for each one that you see in recents.
The new conversation widgets still only shows the person. No message or anything. It does launch either messages or whatever bubble.
There's still a pill on the top of the screen when it's locked. Looks like the navigation pill. It started for me on DP3.
That's all I've seen so far. No crashes. Root works but safety net fails, Viper4Android works, GPay works.
Go get it!

Beta 1 works well so far. There were some minor issues that disappeared, so not even sure if it was the Beta causing it.
Magisk/root works
EdExposed doesn't work yet -- or at least, I couldn't get it to work

So far it's been perfect. No issues whatsoever. Been using it since yesterday when it released. I did perform a factory reset as always. It's really nice I think.

gettinwicked said:
I cleaned flashed to it from DP3 yesterday. Loving it so far! And I wasn't sure about some of the UI changes from the leaked photos.
The bugs I'm getting are:
Bubbles work, but there's a messages 'screen' that opens for each one that you see in recents.
The new conversation widgets still only shows the person. No message or anything. It does launch either messages or whatever bubble.
There's still a pill on the top of the screen when it's locked. Looks like the navigation pill. It started for me on DP3.
That's all I've seen so far. No crashes. Root works but safety net fails, Viper4Android works, GPay works.
Go get it!
Click to expand...
Click to collapse
I've had the same issue (having the pill on the lock screen) since android 11... Otherwise, seems to be relatively usable

Anyone able to get safetynet passing?

emkay5775 said:
I've had the same issue (having the pill on the lock screen) since android 11... Otherwise, seems to be relatively usable
Click to expand...
Click to collapse
With A11? Weird! It only started doing it for me on DP3. I even reset my phone on it to try to fix that and a couple other issues. Clean flashed into beta 1 and it's still there...

Go for it. But be sure about how you follow the installation instructions. Don't forget, the Android 12 beta is still a beta release with some known issues and can brick your device. Be cautious.

sw6n21 said:
Anyone able to get safetynet passing?
Click to expand...
Click to collapse
As far as Google pay working? It works for me

I'm keen to install but does anybody know if Barclays and Natwest apps work with 12 Beta?

StrangerWeather said:
I'm keen to install but does anybody know if Barclays and Natwest apps work with 12 Beta?
Click to expand...
Click to collapse
Replying to my own question: yes, they work.

is there anyway to swap backbutton? tried magisk modules that worked with android 11. but bootloops

I'm currently using beta, some bug available, it's ok for me using for daily driver. I don't care bug

I'm currently using beta, some bug available, it's ok for me using for daily driver. I don't care bug

Well, just flashed Android 12 beta today and I'm love it so far. I'm really like the Samsung style AOD clock.

I have installed Android 12 beta. After booting into Recovery mode and performing Hard Reset after rebooting, the system hangs at verify pattern. I mark the correct pattern I have used previously, the system accepts it and then comes back a step back. I cannot enter the system, I cannot upload an older version of the system. Phone locked, bootloader locked, I can't start debugging mode because the system won't let me go any further after verifying the correct pattern or PIN.
Someone help?

I have installed Android 12 beta. After booting into Recovery mode and performing Hard Reset after rebooting, the system hangs at verify pattern. I mark the correct pattern I have used previously, the system accepts it and then comes back a step back. I cannot enter the system, I cannot upload an older version of the system. Phone locked, bootloader locked, I can't start debugging mode because the system won't let me go any further after verifying the correct pattern or PIN.
Someone help?

Chris PL said:
I have installed Android 12 beta. After booting into Recovery mode and performing Hard Reset after rebooting, the system hangs at verify pattern. I mark the correct pattern I have used previously, the system accepts it and then comes back a step back. I cannot enter the system, I cannot upload an older version of the system. Phone locked, bootloader locked, I can't start debugging mode because the system won't let me go any further after verifying the correct pattern or PIN.
Someone help?
Click to expand...
Click to collapse
You need to unlock it and flash again.