Hi,
My fiancé was very happy with her Xiaomi Mi A2 until last week when it was basically bricked by the bootloop bug after an update.
We got our money back from the retailer so now we are in the market again for a new phone. However, she doesn't like any other phone.
What are the chances that a new Mi A2 will be bricked again by a future update? Is it safe to order a new one? Or should I convince her to buy something else?
Thanks for your reply,
Kind regards,
QD
Did you have the 4/64 or 6/128 version that bricked?
Ulver said:
Did you have the 4/64 or 6/128 version that bricked?
Click to expand...
Click to collapse
I had the 4/64 version.
which update exactly ?
Not sure about the exact build number but it was a security update in march, after the PIE update.
I had the bootloop issue, too. Update from stock Android 8 to Android 9 worked well, but second update to April 2019 security update failed and ended in a bootloop. Thank's to A/B update, see https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/, the phone managed to boot the old firmware after some failed retries. Finally a manually initiated update worked.
My perception is, that updating immediately after a previous update might cause a race condition in the update. After the first boot in the new firmware some post boot processes are running (cleanup?) - running an update in parallel might cause the issue.
Xiaomi support suggested a hard reset; power + volume-up, main menu, wipe data
Luckily this wasn't necessary.
Related
Hi,
I just switched from Apple to Android two days ago and don't know a whole lot about Android yet. I just got my brand new Huawei P20 Pro all set up yesterday and this morning when it went out of battery for the first time I naturally plugged it in to the charger. When I started it back up it went to the Huawei EMUI erecovery screen where it told me that something went wrong and I had a few options:
- Factory reset (recommended)
- Download new version and recovery
- Reboot
- Shutdown
I tried "Download new version and recovery" first and the package was successfully downloaded but when the phone had to restart it went back to the previously mentioned screen. I tried this a couple of times with the same result. After that I tried Reboot and Shutdown (trying to avoid having to factory reset) but it went back to the same screen again. Eventually I gave in and factory reset everything and it seems to have solved the issue but my phone still wants me to update EMUI and now I am afraid that it will do the exact same again. Does anyone in here know anything about this? Is it the new update or am I doing something wrong? How can I update without running into the same problem again?
My current EMUI version is 8.1.0
Thank you for your help.
8.1.0 is the latest emui, as far as I know. If it tries to update emui, you probably should do it because the Android 9 has already been released for P20 pro. If it's not Android and emui it is trying to update, probably it's a new build number. The latest is 156 c432 patch 03 with gpu turbo. Either way, you should update.
azahtoth said:
8.1.0 is the latest emui, as far as I know. If it tries to update emui, you probably should do it because the Android 9 has already been released for P20 pro. If it's not Android and emui it is trying to update, probably it's a new build number. The latest is 156 c432 patch 03 with gpu turbo. Either way, you should update.
Click to expand...
Click to collapse
I tried to update it and it went through fine so it's all good now. I still don't know what happened the first time but I am hoping it won't happen again. Thank you for your reply.
Hi
so i recently bought mi a2 , which i updated on same day and it got stuck on Android logo. multiple users faced this issue.
i called Amazon and they sent ne replacement.
this time, I disabled auto update through Developer option. however phone still downloaded this march 2019 update. now its just waiting on restart, while i am making sure that i dont restart.
screenshot attached.
how to get out of this situation. I do not want want to replace again since there is no point
build number
is there a way to know build number of this upcoming upstate before installing
Before restarting the phone, eject the sim card and then hit restart
One person has the same issue. phone not able to switch off and not able to restart the device.
Yesterday afternoon I received a 2.3 GB update, which turned out to be the security patch for April. It installed normally but immediately started causing system and app failure. The problem arises when scrolling, as if the update time on the screen is reduced. It is a continuous stutter. I have restored the factory settings and the problem persists. Did something similar happen to them? Solutions? The truth is, I don't know what to do anymore. Will it be hardware? The phone has 3 months of use and prior to the update it worked perfectly.
Sorry if my post violates any forum rules, I'm new to this.
You could try going in to the system update again. Then click the menu top right and download latest package and try flashing it again
Hi,
I couldnt update my Mi A2, so googled a bit and found that i should Clear Cach of Google Services Frames. So i did, and after a reboot still unable / or the same message no updates were found.
"Cannot check on updates / Update aint available atm. Try again later"
So i did a factory reset. And now it started updating, till the security patch 5th may 2019. And now im stuck again, with the same message again.
Is there anyone with an idea on what to do now? Ive read that mi a2 had a update to android 10, its just weird mine is stuck at updates from 2019.
Or could anyone please advise me what guide to follow on how to install a custom / or official rom for the mi A2.
Best regards,
I need dire help . I just downloaded the new MIUI 13 update and rebooted to install it but it went into a bootloop instead.. It's not rebooting into fastboot either.
Never download MIUI updates right after they get released. My Redmi Note 9 (EEA) also got bricked, but on the 12.5 release. I had to send a complaint to the shop where I bought it from and they have reflashed my whole phone, thus losing all my data like authenticator codes and 80 GB of photos and videos with my family. And this is a Mediatek chipset which is very common to get the phone bricked on. Always wait for at least the first patch before updating anything, or just don't update and stick with the already buggy environment.