Mi A2 stuck after an OTA update - Xiaomi Mi A2 / 6X Questions & Answers

Hi
Today I performed an OTA update of my Xiaomi A2. After that I restarted my phone and I am not able to boot it anymore.
I got the screen from below. I tried to use "Try again", but it's now working. I have bootloader unlocked and updated OTA on daily basis. I can enter fastboot. I did some research on the internet, but I didn't find the solution.
What can I do to fix it? How can I upload system files only without erasing the data?
Please help.
Screen:
Android Recovery
Xiaomi/jasmine/jasmine_sprout
10/QKQ1.190910.002/V11.0.15.0.QDIMIXM
user/release-keys
Use volume up/down and power.
Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data store on this device.
- Try again
- Factory data reset

I've shared a small guide here: https://forum.xda-developers.com/showpost.php?p=83816925&postcount=31

Related

Trying To Recover Data After XT1096 5.1 Black Screen Bug

Trying to recover data after XT1096 5.1 black screen bug
So I encountered this bug about 2 days ago. It's basically a bug that results in an un-responsive black screen for no apparent reason. I tried all the standard support protocols to save my data (i.e. copy files to pc via USB, and using Cellebrite to pull them off) but without MTP or USB Debugging enabled none of these options worked. Both Verizon and Motorolla tech support advised me to factory reset my phone. However being that a reset will wipe all my data, I've refused to go down that path (yet). So after doing some of my own research I came up with the following ideas, which so far have not been successful.
Idea 1 - use adb to sideload an OTA update with a fresh image that will hopefully resolve the black screen bug but not wipe my data. I followed this thread with partial luck. I got about 47% through the sideload process before it crashed complaining about an invalid full image check
Idea 2 - use fastboot to flash all the images except user data (again with the hopes of resolving the black screen bug without losing data) - But I can't seem to find a compatible set of stock images that will play nicely with my unrooted and locked bootloader phone.
Idea 3 - root my phone, load a custom rom (with no black screen bug) and preserve my user data - unfortunately mofo doesn't support an XT1096 root since I've already accepted the 5.1 OTA.
So my question are:
1 - Are there a set of verizon stock digitally signed images anywhere out there that will work with my XT1096 with 5.1 already installed?
if not
2 - Is there any way to root my phone or unlock the bootloader so that I can accept non-factory images without the use of Mofo?
Any help with this is greatly appreciated.
rushramia said:
So I encountered this bug about 2 days ago. It's basically a bug that results in an un-responsive black screen for no apparent reason. I tried all the standard support protocols to save my data (i.e. copy files to pc via USB, and using Cellebrite to pull them off) but without MTP or USB Debugging enabled none of these options worked. Both Verizon and Motorolla tech support advised me to factory reset my phone. However being that a reset will wipe all my data, I've refused to go down that path (yet). So after doing some of my own research I came up with the following ideas, which so far have not been successful.
Idea 1 - use adb to sideload an OTA update with a fresh image that will hopefully resolve the black screen bug but not wipe my data. I followed this thread with partial luck. I got about 47% through the sideload process before it crashed complaining about an invalid full image check
Idea 2 - use fastboot to flash all the images except user data (again with the hopes of resolving the black screen bug without losing data) - But I can't seem to find a compatible set of stock images that will play nicely with my unrooted and locked bootloader phone.
Idea 3 - root my phone, load a custom rom (with no black screen bug) and preserve my user data - unfortunately mofo doesn't support an XT1096 root since I've already accepted the 5.1 OTA.
So my question are:
1 - Are there a set of verizon stock digitally signed images anywhere out there that will work with my XT1096 with 5.1 already installed?
if not
2 - Is there any way to root my phone or unlock the bootloader so that I can accept non-factory images without the use of Mofo?
Any help with this is greatly appreciated.
Click to expand...
Click to collapse
1) Yes there are stock signed images for the xt1096. They won't fix your problem. The problem is the data partition is corrupt. Flashing a stock image does not change nor fix the data partition, so it won't help.
2) No, there is no other way.
I am sorry to say, but there is only one solution, which is factory reset. The reason factory reset works is because it will erase the corrupted data partition. Sorry, but you will lose your data, there is no way to recover now. Since you have 5.1 installed, it is also impossible to use mofo and sunshine, so no root and no bootloader unlock neither.
I'm in the same boat except I'm on vacation with out my computer. Can I factory reset from fastboot?
Yes you can. Once you are in fastboot select recovery. Once you are in recovery and see the dead android press power and volume down to open the menu, then select factory reset.
Sent from my XT1095 using Tapatalk
AGISCI said:
1) Yes there are stock signed images for the xt1096. They won't fix your problem. The problem is the data partition is corrupt. Flashing a stock image does not change nor fix the data partition, so it won't help.
2) No, there is no other way.
I am sorry to say, but there is only one solution, which is factory reset. The reason factory reset works is because it will erase the corrupted data partition. Sorry, but you will lose your data, there is no way to recover now. Since you have 5.1 installed, it is also impossible to use mofo and sunshine, so no root and no bootloader unlock neither.
Click to expand...
Click to collapse
Thanks Chris,
I appreciate the response. Do you know where I might find the stock signed images for xt1096? I've somehow hosed my system img so now I can't even get into recovery to do a factory reset (keeps complaining 'failed to validate system image'). I'm hoping to re-flash the stock system.img to fix this problem. Let me know.
Thanks!
Sure here it is:
download
Sent from my XT1095 using Tapatalk
AGISCI said:
Sure here it is:
Click to expand...
Click to collapse
Thanks!
That got me back to where I started. System is no longer 'invalid' and my phone boots up to a black screen. The notifications still work and I can boot into fastboot or recovery modes. I guess my only option now is to bite the bullet and factory reset now (and loose my data). :crying:
Thanks again for all your help!
AGISCI said:
Yes you can. Once you are in fastboot select recovery. Once you are in recovery and see the dead android press power and volume down to open the menu, then select factory reset.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
weird. I go into fastboot and got the options: normal boot, recovery, factory and some others and i can cycle through with vol down. vol up is select but no matter what i select it just boots normally (still have black screen)
do i need to unlock something?
I need some more info. Are you on stock rom? What version(4.4.4, 5.0, or 5.1)? Have you unlocked your bootloader with sunshine? Have you rooted woth mofo or kingroot?
Sent from my XT1095 using Tapatalk

Failed downgrade from Nougat to MM bricked my EVA-L09

Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did
Code:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.
i2ectcf said:
Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.
Click to expand...
Click to collapse
did you wiped data, cache, dalvik?
snapdesign said:
did you wiped data, cache, dalvik?
Click to expand...
Click to collapse
Hi! I'm not sure how to wipe data, cache or dalvik, because when I upgraded to Nougat this apparently removed TWRP.
Also I'm wondering if trying to use srktool to reinstall TWRP for 6.0 might have corrupted my 7.0 phone?
Is there any way to wipe data, cache, and/or dalvik now? Or are there other things I could try to unbrick?
Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow. Here's an outline:
1. Google "Huawei Bricked phone repair guide with DC Phoenix", go to the first result and look at the instructions (I can't post URLs yet).
I used Method 1. But note! The newer versions of DC Phoenix are missing a feature that the instructions make clear you have to use. To get the original version used in their guide, you have to download the latest version of DC Phoenix, open it on your PC, then click "Enter Support Area" which logs you in to a download section. Find "DC Unlocker Softwares", "DC_Phoenix", then download DC_Phoenix_v14.rar and run that instead. Whether it's Method 1 or 2 make sure you complete it - i.e. the fastboot flash step AND a step they call "flashing in upgrade mode."
(Also note that for DC Phoenix you want to feed it the oldest version of firmware available for your phone, in my case b152. This is because themes and icons won't be fixed until it receives the next version of firmware as an update.)
2. Once I did the fastboot and upgrade flash, I did a system reset from the Settings app trying to get themes and current icons again. (This didn't work but doesn't do any harm or might have helped somehow further down the line).
3. I used hajuuk's Firmware Updater and HiSuite to upgrade to the next version of firmware available (in my case b168).
3. All fine and your phone is back to stock - icons look nice again and local themes are back. To get the original icons layout, go to Recents, hold down on the Trash Icon, show system apps, and Clear Data for Huawei Home.
i2ectcf said:
Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow.
Click to expand...
Click to collapse
Thanks for sharing! You saved me!

[Issue] Is memory on my g2 dead?

Hi there,
I have a Moto G 2 (2014) that I use as a secondary phone and yesterday my phones started to act weird so I decided to reboot it, upon rebooting phone is completely unusable. There is no way to browse through apps or do anything at all as every single app crashes almost immediately. Even the system apps crash constantly.
I thought that factory reset will solve the issue but I can't access it through phone so I tried to use recovery option to reset it to the factory settings without any luck. Bootloader is unlocked with status 3, but there is no way to flash anything, custom rom or recovery. I have followed the steps to flash the recovery from HERE without any luck. Booting the recovery through fastboot gets me through to TWRP or CWM but I can't perform any operation as any wipe command results in error 5.
Erasing through fastboot doesn't do anything either, although shows that operation has succeed when I boot I am greeted with same state I left the phone in, with exact apps I left open etc.
I have even unplugged the battery and left it for few hours to drain the energy from the board without any luck!
Now I was wondering whether it is some sort of memory issue? I never had any issues with the phone it was working well until one day it just sort of died.
Short version
Phone boots - Every app crashes (even system apps)
Unlocked Bootloader
No way to flash or wipe anything
Can boot to custom recovery through fastboot but that's about it (can't perform any operation, constant Error 5)
When wiping through fastboot device still has the old data even the apps that I had open when it crashed.
Sounds like data/internal storage partition is corrupted. Can you access internal storage via mtp on PC?
Many phones were saved by flashing stock ROM, especially partition table/gpt.bin.
Try flashing whole stock ROM, step by step. You can find files and Howto here on xda.
This will reset your phone! Good luck!

Question My Realme x7 max 5G stuck in recovery loop after uninstalling bloatare like glance, finshell pay, hot apps

like the title says I uninstalled the mentioned apps using adb and all of a sudden my camera stopped working so I decided for a simple restart and the device stuck in the loop ever since.
it restarts several times and open realme UI recovery and when I choose language it says " KINDLY REMINDER : system error, after select language, please select Online update(keep data) to recovery system, thanks! " .
So I did what the message said and I connect the wifi but instead of updating it says no updates found.
I also tried to wipe data but I got asked whether to retain contacts/media or format data.
I obviously tried the first one because I need the data but as expected it didn't work.
I am skeptical to clean format because I feel that I can still fix it with retaining the data.
I tried all the key combinations but only the realme UI recovery comes up . Please help me!
thank you
I don't think you'll be able to fix this without a full reflashing of the ROM using SP Tools and a format of the data partition from Recovery. You probably don't have access to full ADB now, if at all, and Fastboot won't help you recover anything. However, you should be able to rescue important files before you do this, as long as you have unlocked your bootloader.
Follow the steps here to install TWRP custom recovery. Once done, you can boot into it from fastboot by running `fastboot reboot recovery`. Once you're in TWRP, you can mount partitions so you can access them over USB from your PC.
Once you've got your important files transferred to your PC, take a full backup to be safe, then flash the stock ROM. This thread can help you do both of those things. Note that flashing the stock ROM using SP Tools will also restore the stock recovery. Once the process is done, boot right into fastboot and use it to reboot back into the stock recovery before letting it actually boot the ROM. Format your data partition (yes the whole thing). Now you can restart, and it should go through first time setup just fine.
I was going to uninstall these apps, but was too lazy. Guess lazyness is not too bad after all.
@Ricodey have you got the solution for this thing beacause i am also experiencing same issue
e_v_i_l_x_ said:
@Ricodey have you got the solution for this thing beacause i am also experiencing same issue
Click to expand...
Click to collapse
Unfortunately I had to go for the latter option of complete reset with the loss of data to get my device boot up . It seems the option to recover the device with data seems too complicated and not to mention the fact that this process is not without it's own risks. If you want an easy out from this issue I suggest that you complete format the device and have your important data backed up from now.
And Obviously I had data not backed up which I wanted on my device during this issue but it wasn't too important and I could let go of it cuz rest of my data was backed up.. but being the nerd I am, I tried to recover that data too.. but as I said it wasn't worth the time and risk for me so I chose the latter option.
Hope this helps! Do reply if you need further assistance !
Ricodey said:
Unfortunately I had to go for the latter option of complete reset with the loss of data to get my device boot up . It seems the option to recover the device with data seems too complicated and not to mention the fact that this process is not without it's own risks. If you want an easy out from this issue I suggest that you complete format the device and have your important data backed up from now.
And Obviously I had data not backed up which I wanted on my device during this issue but it wasn't too important and I could let go of it cuz rest of my data was backed up.. but being the nerd I am, I tried to recover that data too.. but as I said it wasn't worth the time and risk for me so I chose the latter option.
Hope this helps! Do reply if you need further assistance
Click to expand...
Click to collapse
for me the issue was like i just downgraded my device to the a.15 firmware after setting up i uninstalled the bloatware apps and some google apps which were not needed obviously and restarted my device and it got a bootloop, the issue of bootloop wasn't new to me i previoulsy had the same issue when i have downgraded to a.19 firmware. there is a simple fix, if you want to get rid of the bloatware apps now also you can use the disable command like.
(pm uninstall-user --user 0 ----package name---) this will not give any bootloop and can enjoy a part of RAM....
THIS WILL HELP
get in touch if need anything else

The system does not boot after automatic update

Hi
I have a very strange case with my P20 PRO 128GB Single Sim. About a week or two ago, I got a message that my phone found a new system update. I was very happy because I was still stuck on 9.1.0.311 because my phone never got the update to 10.
What was my surprise when it turned out that the update has exactly the same number that I have now uploaded to my phone.
I found that I did not have time to install the update yet, so I kept delaying it.
I was also supposed to do a data backup, unfortunately I didn't have time.
Last night my phone was updated. Unfortunately, it did not start normally after this update.
Constantly stops on the screen:
Your device has loaded a different operating system.
To learn more, visit:
http://zh.ui.vmall.com/emotiondownload.php?mod=restore
....
Your device is booting now ...
Then it goes to eRecovery.
I tried to do Update and recover system in this eRecovery, unfortunately after connecting to Wifi and trying to find information, I get the information Get package info failed
The Emergency backup option does nothing. The phone restarts and goes to the first screen Your device has loaded ...
I wanted to repair my phone via Fastboot & Rescue mode and HiSuite, unfortunately I get the information that "System restore is not supported on this device"
If I hold Volume Up + Power on the turned off phone, I enter the menu where I have the option Update mode and Clear data. In Clear data, I chose Wipe cache partition and then Safe mode, but it didn't help.
I wonder if by Update mode and, for example, through Memory card / OTG update mode or USB update mode, I would be able to restore the system and recover the data.
What do you think about it? Is there any chance to recover data (mainly photos and videos) or accept the loss and try to do Factory reset?

Categories

Resources