Database Develop

[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5

How to flash a factory image | Return to stock | Unroot your Nexus 5​
Hello Nexus 5 Users!
I see many users that don't know how to restore their Nexus 5 to stock. It may come in handy, either when you want to RMA your phone, or you want to fix your mistakes.
This process consists of wiping and flashing every partition on your phone.​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING!!!
This process will wipe your phone completely. Backup your storage before you continue.
I am also not responsible if anything goes wrong.
You can backup apps and data using this app before you unlock the bootloader. No root required.
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
DO NOT USE TOOLKITS!!!
They have a high probability of something going wrong if you don't know how to use them (which, if you managed to ruin your phone, probably is true).
I don't mean to offend toolkit creators. They did a great job. But don't risk bricking your phone just because you're lazy.
FOLLOW EVERY SINGLE STEP
or you will end up in a bootloop, or with a bricked phone, and we don't want that
Let's get started!!
Setting up​
For this process, you will need to:
★Install adb and fastboot drivers. To do this, use this simple program:
http://forum.xda-developers.com/showthread.php?t=2588979
For MAC users:
http://forum.xda-developers.com/showthread.php?t=1917237
*Note: MAC users will have to write "./" before every command in this thread. For example : "./fastboot flash recovery recovery.img"
Linux users should know their stuff
http://forum.xda-developers.com/showthread.php?t=921169
★Download the latest factory images from here:
https://developers.google.com/android/nexus/images#hammerhead
★Extract the archive you downloaded (Use WinRAR). It should look like this:
★Unlock your bootloader (In case you haven't already)
http://forum.xda-developers.com/showthread.php?t=2507905
Flashing the factory images​
There is more than one way to flash these images. Each give the same results, but the first is for lazy users
Method 1. Easy method.
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Execute the flash-all.bat script (for Windows) or flash-all.sh(for MAC and LINUX) in the folder where you extracted the factory images.
**!!** For MAC: You'll have to edit the flash-all.sh, and add "./" before every fastboot command.
★Wait for everything to flash.
★After everything finished, select "Recovery" using the volume buttons.
★When a small dead Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock. :good:
Method 2. Long method (Same thing actually, but I'll mention it, just in case)
★Extract the image-hammerhead-krt16m.zip somewhere easy to access (On C:\image-hammerhead-krt16m for example). You will have the following files:
★In the same folder, from the original archive, extract "bootloader-hammerhead-XXXXXX.img" (rename it to bootloader.img) and "radio-hammerhead-XXXXXX.img" (rename it to radio.img)
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Open a CMD window.
★Type the following commands, in this order (If you have a different folder, change the path)
Code:
fastboot flash bootloader C:\image-hammerhead-krt16m\bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:\image-hammerhead-krt16m\radio.img
fastboot reboot-bootloader
fastboot flash system C:\image-hammerhead-krt16m\system.img
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
[B](Note: this command will wipe your device (including \sdcard), EVEN if your bootloader is already unlocked.)[/B]
fastboot flash boot C:\image-hammerhead-krt16m\boot.img
fastboot flash recovery C:\image-hammerhead-krt16m\recovery.img
fastboot erase cache
fastboot flash cache C:\androidimage\cache.img
★After everything finished, select "Recovery" using the volume buttons.
★When a small Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock. :good:
For both methods:
Optional, but necessary for warranty purposes - Locking your bootloader+ Resetting the tamper flag
The Nexus 5 has a thing implemented in the bootloader called a tamper flag. This shows if the bootloader was ever unlocked, kind of like the flash counter with Samsung devices. You can check it out by using this command
Code:
fastboot oem device-info
. If the tamper flag value is "true", then you'll have to reset it. The following steps will reset this flag, and lock your bootloader.
•So, first, go here: http://forum.xda-developers.com/showthread.php?t=2239421 (Thanks @osm0sis for the wonderful script)
Under "Flashable Zips", you will find the Nexus BootUnlocker script. Download it.
•Put the zip on your internal storage.
•Download the latest TWRP recovery image for the Nexus 5 from here: http://techerrata.com/browse/twrp2/hammerhead. Rename it to TWRP.img.
Now boot it. You do this by booting your phone in fastboot, and typing the following command:
Code:
fastboot boot path\to\TWRP.img
*Replace path\to\TWRP.img with the path to where you placed the TWRP.img. For example: C:\Users\X\Desktop\TWRP.img
TWRP recovery should boot.
•When TWRP finished booting, select "Install", then navigate to the Nexus Bootunlocker zip, select and install it. After it finished, use the back arrow at the bottom of the screen to go back, and reboot.
Now your bootloader should be locked, and your tamper flag should show "false".
And now you have a brand new Nexus 5 (software wise, at least)​​
Video Guides​
Thanks @techfanatic9.
For Windows:
For Mac:
Another easy and fast tutorial made by @iTzGavin96
These don't contain the tamper flag reset step. Follow the steps above to reset your tamper flag value to "False" for warranty purposes.
If you now have 12 GB of storage instead of 28 GB, go to post #2​

32 GB phone now shows 16GB?​
This is a common problem with Nexus devices. Minor error, don't panic. Here is how to fix it
★Boot into STOCK RECOVERY (If you are running a custom recovery you must flash to stock)
★Clear cache
★Factory reset
If that didn't work, proceed with doing this:
Open a CMD window, boot your phone is fastboot, and write the following commands, in this order (Considering that you have extracted the images in C:\image-hammerhead-krt16m\)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader C:\image-hammerhead-krt16m\bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:\image-hammerhead-krt16m\radio.img
fastboot reboot-bootloader
fastboot flash system C:\image-hammerhead-krt16m\system.img
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
(Note: this command will wipe your device (including \sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:\image-hammerhead-krt16m\boot.img
fastboot flash recovery C:\image-hammerhead-krt16m\recovery.img

Credits and Thanks:
@efrant
For his thread in the N4 section (http://forum.xda-developers.com/showthread.php?t=2010312)
@osm0sis
For contributing a lot with the tamper flag part
@dombera
For inspiring me to make this guide
@Chromium_
For not replying to my Hangouts messages
@jd1639
For helping me out with this thread.
@Prodeje79
For pointing problems out.
​

abaaaabbbb63 said:
Chromium_
For not replying to my Hangouts messages
Click to expand...
Click to collapse
I do my best
Jk, my school has WiFi jammers in some of the classes.
Sent using xda-developers app

Chromium_ said:
I do my best
Jk, my school has WiFi jammers in some of the classes.
Sent using xda-developers app
Click to expand...
Click to collapse
Really? That's..... evil!!

abaaaabbbb63 said:
Really? That's..... evil!!
Click to expand...
Click to collapse
Evil...more like illegal.

Bleah.. The Dotted divider looks horrible on Tapatalk....
Meh

Because I don't know better, why do you consider method 2 safer?

Is there an easier "hide root" or any way to unroot where AirwatchMDM or other MDM corporate software control crap is hidden?
I'm wanting to try register on airwatch then lock down airwatch and see if I could still use touchdown.

jd1639 said:
Because I don't know better, why do you consider method 2 safer?
Click to expand...
Click to collapse
Well, safer in the sense that you are more in control, and can only flash certain images, not all. I'll delete de safe part.
fintheman said:
Is there an easier "hide root" or any way to unroot where AirwatchMDM or other MDM corporate software control crap is hidden?
I'm wanting to try register on airwatch then lock down airwatch and see if I could still use touchdown.
Click to expand...
Click to collapse
If you have root through the "SuperSU" app, it has an unroot option.

My keeps boot looping

sergiox209 said:
My keeps boot looping
Click to expand...
Click to collapse
Did you factory reset from the Stock Recovery?

abaaaabbbb63 said:
Did you factory reset from the Stock Recovery?
Click to expand...
Click to collapse
not the stock one a Rom

sergiox209 said:
not the stock one a Rom
Click to expand...
Click to collapse
Wait, what exactly did you do?

abaaaabbbb63 said:
Wait, what exactly did you do?
Click to expand...
Click to collapse
honestly i forgot but it keeps telling me in CMW error mounting /data if i try to wipe data

sergiox209 said:
honestly i forgot but it keeps telling me in CMW error mounting /data if i try to wipe data
Click to expand...
Click to collapse
You flashed CWM without booting in the stock ROM?
Please, follow the guide accordingly.
Try keeping it stock for the first boot. Then, you may install a custom recovery.

abaaaabbbb63 said:
You flashed CWM without booting in the stock ROM?
Please, follow the guide accordingly.
Try keeping it stock for the first boot. Then, you may install a custom recovery.
Click to expand...
Click to collapse
yes thats what im trying to do but it keeps boot looping. if there a way i can fix?

sergiox209 said:
yes thats what im trying to do but it keeps boot looping. if there a way i can fix?
Click to expand...
Click to collapse
The bootloop is most probably caused by you not factory resetting. Do you have the stock recovery right now?

abaaaabbbb63 said:
The bootloop is most probably caused by you not factory resetting. Do you have the stock recovery right now?
Click to expand...
Click to collapse
the file that you provide i have that download.

sergiox209 said:
the file that you provide i have that download.
Click to expand...
Click to collapse
Ok, so you installed using the flash-all.bat? Then you have stock recovery.
In bootloader, select "Recovery". When the small Android comes up, press Power Button + Volume UP. From the menu, select "wipe data/factory reset"

Soft-Brick HTC One M7

Hi all,
first time poster - looonnng time lurker. Hoping you can help me with my One M7 brick.
Phone had been running slow and sluggish for a few weeks. Yesterday morning, it was particularly slow with apps randomly closing/crashing. Decided to reboot. The phone didn't reboot though; it came back with a white screen and "** TAMPERED *** *** LOCKED****" coming up - a fastboot screen I believe.
I can't get it to boot at all and I've tried accessing it via adb but it isn't detected. 'adb devices' shows nothing however 'fastboot devices' does list the phone. Windroid seems to detect it.
Ordinarily, I would just do a factory reset to see if this helps but my problem is this - I have SMS messages and photos/videos on the phone of my daughter that I really, really, really don't want to lose. They are very precious to me. If it was a case of breaking up the phone then I'd do it in a heartbeat to recover this data.
I've attached some images that I hope may help. A friend has mentioned that some of the lines indicate a problem with encryption on the card which means the data is lost completely - I'm desperately hoping this isn't the case and some kind soul can help.
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

need help to flash factory ruu zip
recently i installed recovery and accidentally deleted system partition..then it wont boot up..
OS- 7. 21 .980. 35
hboot -1.61
can not s-off
mid-PN0714000
cid- HTC__039
there are no ruu zip matches i found..
can anyone suggest me something to back to normal.. thanks..

namal.007 said:
recently i installed recovery and accidentally deleted system partition..then it wont boot up..
OS- 7. 21 .980. 35
hboot -1.61
can not s-off
mid-PN0714000
cid- HTC__039
there are no ruu zip matches i found..
can anyone suggest me something to back to normal.. thanks..
Click to expand...
Click to collapse
flash the 7.19.980.5 RUU, see post #2 of this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
---------- Post added at 09:24 AM ---------- Previous post was at 09:20 AM ----------
MPDi said:
Hi all,
first time poster - looonnng time lurker. Hoping you can help me with my One M7 brick.
Phone had been running slow and sluggish for a few weeks. Yesterday morning, it was particularly slow with apps randomly closing/crashing. Decided to reboot. The phone didn't reboot though; it came back with a white screen and "** TAMPERED *** *** LOCKED****" coming up - a fastboot screen I believe.
I can't get it to boot at all and I've tried accessing it via adb but it isn't detected. 'adb devices' shows nothing however 'fastboot devices' does list the phone. Windroid seems to detect it.
Ordinarily, I would just do a factory reset to see if this helps but my problem is this - I have SMS messages and photos/videos on the phone of my daughter that I really, really, really don't want to lose. They are very precious to me. If it was a case of breaking up the phone then I'd do it in a heartbeat to recover this data.
I've attached some images that I hope may help. A friend has mentioned that some of the lines indicate a problem with encryption on the card which means the data is lost completely - I'm desperately hoping this isn't the case and some kind soul can help.
Thanks
Click to expand...
Click to collapse
If the phone was encrypted then the only way to recover the phone is a factory reset using the stock recovery which will obviously delete all your files. Any other method that could fix the phone will wipe it: unlock the bootloader to flash a new rom will wipe the phone, flashing a ruu will also wipe it. Thats probably either an encryption problem or a failed emmc chip. I don't think there anything to do to recover your data, especially if the phone was encrypted. Sorry at least the phone might be recoverable...

alray said:
flash the 7.19.980.5 RUU, see post #2 of this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
---------- Post added at 09:24 AM ---------- Previous post was at 09:20 AM ----------
If the phone was encrypted then the only way to recover the phone is a factory reset using the stock recovery which will obviously delete all your files. Any other method that could fix the phone will wipe it: unlock the bootloader to flash a new rom will wipe the phone, flashing a ruu will also wipe it. Thats probably either an encryption problem or a failed emmc chip. I don't think there anything to do to recover your data, especially if the phone was encrypted. Sorry at least the phone might be recoverable...
Click to expand...
Click to collapse
Well, after asking a company who said they could do it and then said they'd have to wipe it, I've taken it back.
It seems there's nothing I can do about it; I've even tried using guides on here and elsewhere to return it completely to stock but because I can't get adb working, it's a no go. Factory reset does nothing. Trying to use tools and fastboot to change recovery images and all sorts doesn't work either. Seems to be something relating to 'S-ON' as when it's in RUU boot, if I disconnect and reconnect the USB cable, the screen briefly changes from the HTC screen to the white screen showing "Security Failed!" after trying to flash a new image on.
At a bit of a loss!

MPDi said:
It seems there's nothing I can do about it; I've even tried using guides on here and elsewhere to return it completely to stock but because I can't get adb working, it's a no go.
Click to expand...
Click to collapse
adb commands only works from a booted rom + USB debugging enabled from the developer option menu or from a custom recovery. So there is no problem here.
Factory reset does nothing.
Click to expand...
Click to collapse
What is it doing exactly? You select "factory reset and it boot to the HTC splash sceen? It reboot in bootloader mode? It freeze the phone?
Trying to use tools and fastboot to change recovery images and all sorts doesn't work either.
Click to expand...
Click to collapse
Again you need to be more precise, what doesn't work exactly? There is no fastboot connectivity or there is but the recovery won't flash? Did you unlocked the bootloader?
Seems to be something relating to 'S-ON'
Click to expand...
Click to collapse
No, Its not related to S-ON.
as when it's in RUU boot, if I disconnect and reconnect the USB cable, the screen briefly changes from the HTC screen to the white screen showing "Security Failed!" after trying to flash a new image on.
Click to expand...
Click to collapse
What image exactly and how did you tried to flash it?

alray said:
adb commands only works from a booted rom + USB debugging enabled from the developer option menu or from a custom recovery. So there is no problem here.
What is it doing exactly? You select "factory reset and it boot to the HTC splash sceen? It reboot in bootloader mode? It freeze the phone?
Again you need to be more precise, what doesn't work exactly? There is no fastboot connectivity or there is but the recovery won't flash? Did you unlocked the bootloader?
No, Its not related to S-ON.
What image exactly and how did you tried to flash it?
Click to expand...
Click to collapse
I've taken it back to another shop this morning to have it reset/flashed back to stock. Will just have to try data recovery once I've got it back and see if I can recover anything.

Stock HTC One M7, Unrooted, locked bootloader, stuck in boot loop

Good evening:
My sister in law has an HTC One M7 that has a LOCKED bootloader, is running STOCK, and is S-On. She was using the phone perfectly fine one day, and then all of a sudden it went into this infinite bootloop. This is the Verizon variant of this phone.
The main thing I am trying to accomplish is to save some pictures that she has on her phone of her newborn son (not automatically backed up). After that, I will flash an RUU to get it where it hopefully needs to be.
The info is as follows:
*** Locked***
M7_WLV PVT Ship S-On RH
HBoot-1.61.0000
Radio-1.13.41.1209
OpenDSP-v35.120.274.0718
OS-6.22.605.6
eMMC-boot 2048mb
Nov 30 2015
I have tried the following things from other threads:
1. "Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader."
2. "Try and shut it down and restart it again by holding the power button down for 12 - 15 seconds and see whether that clears it."
3. "Hold down power, volume up and volume down for at least 10 seconds. That should force a clean reboot."
How can I mount the phone to get the pictures or how can I get it to restart just long enough to receive them? Thank you for all your help.

poda13 said:
Good evening:
My sister in law has an HTC One M7 that has a LOCKED bootloader, is running STOCK, and is S-On. She was using the phone perfectly fine one day, and then all of a sudden it went into this infinite bootloop. This is the Verizon variant of this phone.
The main thing I am trying to accomplish is to save some pictures that she has on her phone of her newborn son (not automatically backed up). After that, I will flash an RUU to get it where it hopefully needs to be.
The info is as follows:
*** Locked***
M7_WLV PVT Ship S-On RH
HBoot-1.61.0000
Radio-1.13.41.1209
OpenDSP-v35.120.274.0718
OS-6.22.605.6
eMMC-boot 2048mb
Nov 30 2015
I have tried the following things from other threads:
1. "Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader."
2. "Try and shut it down and restart it again by holding the power button down for 12 - 15 seconds and see whether that clears it."
3. "Hold down power, volume up and volume down for at least 10 seconds. That should force a clean reboot."
How can I mount the phone to get the pictures or how can I get it to restart just long enough to receive them? Thank you for all your help.
Click to expand...
Click to collapse
You could try to go in recovery mode a wipe cache (do not factory reset). Then if the phone is still in a bootloop there is absolutely nothing you can do to backup any file from it. There are only 2 possibility to backup files from your phone, 1st one requires to be booted in the OS which is not possible, 2nd one requires to boot a custom recovery (the bootloader is locked, unlocking it to flash a custom recovery will wipe the phone)
Here is the RUU you'll need: https://www.androidfilehost.com/?fid=24341993505161705
Flash it using htc_fastboot.exe like explained in the RUU collection thread from the general section.

alray said:
You could try to go in recovery mode a wipe cache (do not factory reset). Then if the phone is still in a bootloop there is absolutely nothing you can do to backup any file from it. There are only 2 possibility to backup files from your phone, 1st one requires to be booted in the OS which is not possible, 2nd one requires to boot a custom recovery (the bootloader is locked, unlocking it to flash a custom recovery will wipe the phone)
Here is the RUU you'll need: https://www.androidfilehost.com/?fid=24341993505161705
Flash it using htc_fastboot.exe like explained in the RUU collection thread from the general section.
Click to expand...
Click to collapse
Hi Alray,
Thank you for your ideas on this. When I boot into the bootloader and select to go into recovery, it just takes me back to the bootloader screen. For some reason, I can not get to the screen with the red triangle to get into stock recovery. I was able to figure out the command prompt and fastboot, so I tried "fastboot erase cache", but it said there was an error.
Two key point that I think are good to know, developer options were not enabled on the phone so USB debugging is not on. Also, the fastboot option under settings >> power was still checked. Since i cant get into the system, i can not change those.
So, I cant erase cache via fastboot and I can not get into recovery for some reason. Any other suggestions on how to get into recovery or anything else?
Thanks for your time!

poda13 said:
Hi Alray,
Thank you for your ideas on this. When I boot into the bootloader and select to go into recovery, it just takes me back to the bootloader screen. For some reason, I can not get to the screen with the red triangle to get into stock recovery. I was able to figure out the command prompt and fastboot, so I tried "fastboot erase cache", but it said there was an error.
Two key point that I think are good to know, developer options were not enabled on the phone so USB debugging is not on. Also, the fastboot option under settings >> power was still checked. Since i cant get into the system, i can not change those.
So, I cant erase cache via fastboot and I can not get into recovery for some reason. Any other suggestions on how to get into recovery or anything else?
Thanks for your time!
Click to expand...
Click to collapse
USB debugging status (on/off) doesn't matter when in bootloader and recovery, its only needed to use ADB commands when booted in the OS.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There is nothing else you can try without loosing data on the phone.,,
what was the error when trying fastboot erase cache?

alray said:
USB debugging status (on/off) doesn't matter when in bootloader and recovery, its only needed to use ADB commands when booted in the OS.
There is nothing else you can try without loosing data on the phone.,,
what was the error when trying fastboot erase cache?
Click to expand...
Click to collapse
There was not a specific error given from what I remember, just said that there was an error. I am heading to work so I will try again tonight and will post the specific script that was shown.

alray said:
USB debugging status (on/off) doesn't matter when in bootloader and recovery, its only needed to use ADB commands when booted in the OS.
There is nothing else you can try without loosing data on the phone.,,
what was the error when trying fastboot erase cache?
Click to expand...
Click to collapse
Here is the info that I get when I try to do the fastboot clear cache:
C:\Users\The Goat>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.017s
Any thoughts?

poda13 said:
Any thoughts?
Click to expand...
Click to collapse
Its time to try the RUU I guess

Mi A2 - Failed to boot - after system update

Hello everyone, yesterday morning, Sunday 12/15/19, the system message "restart the device to make the system update effective".
So I do as I have always been.
The phone, an Mi A2, goes into bootloop and then a white screen appears on a black background with the title:
"<!> Failed to boot"
"Press the Volume keys to select then the Power button to continue.
RETRY
POWER OFF "
Choosing "RETRY" verifies bootloop 3 or 4 times and then the recovery mode screen appears which says:
"Can't Load Android system. Your data may be corrupted. You should get the message you need to perform at factory data reset and erase all user data stored on this device."
It gives me the choice between:
-Try again
-Factory data reset
Choosing "Try again" returns the same routine as when "RETRY" is selected In the previous black background screen, bootloop and then the black background white screen described at the beginning.
I MUST ACCESS AND SAVE THE VERY IMPORTANT CONTENT. :crying:
I have all the photos and videos of my newborn daughter. I usually backup but this inconvenience suddenly caught me.
I surfed and I saw that many people found this problem after an update .. but I never found any solutions. I called the Xiaomi center in Novara indicated by the site but they told me that they only serve as a collection center to send to the assistance in the company Xiaomi, saying that the assistance resets the phone to restore its functioning and does not save the data. I tried to start the fastboot, the device is recognized by the PC and shows the locked bootloader. The program MiFlash asks me to start to install a set of drivers and then immediately generate an unhandled exception and crash.
Attached the images.
Can you help me? I do not know what to do..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".

Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.

Aerobatic said:
Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.
Click to expand...
Click to collapse
Thank you, can you explain me better what I should try to do?

HTCDevil said:
You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".
Click to expand...
Click to collapse
Is there any guide to do that?

pedrix82 said:
Is there any guide to do that?
Click to expand...
Click to collapse
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.

pedrix82 said:
Thank you, can you explain me better what I should try to do?
Click to expand...
Click to collapse
First you can try to search this forum and read dozens of discussions of the same issue. Meanwhile you can plug in power adapter and reboot several times with pauses, probably sometimes switching to stock recovery and to fastboot mode, and then leave phone powered for a night.

HTCDevil said:
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.
Click to expand...
Click to collapse
Thanks....I will try, I don't remember if I enabled the usb debugging mode, for sure I saw with fastboot that I have the bootloader Locked.

nothing to do...i tried ADB mode, but it is not enabled, only fastboot mode where i can do nothing because the bootloader is locked.
I also tried to install the Xiaomi tool, but it doesnt recognize the device.
i dont know what to do....

Did you try the factory data reset?

1N4148 said:
Did you try the factory data reset?
Click to expand...
Click to collapse
Hello...ehm...not, the aim is to recover all the data, photos and documents that are stored inside...

Same thing happened to me. You should manually switch the active partition in fastboot.

Zedsdeadbaby said:
Same thing happened to me. You should manually switch the active partition in fastboot.
Click to expand...
Click to collapse
Hi, I already tried to do what you suggest, but it is not possible with the bootloader Locked.
Anyway, can you tell me what I have to do to change the active partition? Maybe I don't do it as I should....

@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.

Aerobatic said:
@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.
Click to expand...
Click to collapse
Thanks,
It's really long time that I'm rebooting the mobile since it happened...
But cyclically and alternate I got the two image attached to the main post....

try a "fastboot continue" in adb

hello everyone, update.
unfortunately I was unable to recover anything and proceeded with the factory reset.
The phone has reset and everything is working.
So I thought to try to do a file recovery as you do for deleted files.
for the various recovery applications I need to root the device.
For this phone should be really simple but I'm still stuck in.
I followed one guide, then another, and then another .... all with the same procedures.
the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone.
but from this recovery, even if I install Magisk, with a successful results from the recovery, I do not root the device. I verified root with Magisk manager and rootchecker.
Help.... thanks

pedrix82 said:
... So I thought to try to do a file recovery as you do for deleted files.
Click to expand...
Click to collapse
I do no believe you'll be able to undelete files after factory reset.
pedrix82 said:
... for the various recovery applications I need to root the device. ... I followed one guide, then another, and then another .... all with the same procedures.
Click to expand...
Click to collapse
This guide works for everybody, except that
(1) there is obsolete "fastboot oem unlock" command stated which should better be changed to "fastboot flashing unlock", and
(2) guide does not mention that each unlock step is to be approved on phone, and
(3) guide skips step of patching stock boot.img in phone with MagiskManager, - while exactly this step creates archived copy of stock boot image in /data root, thus allowing to restore images (actually restoring stock boot image) before downloading next OTA, and
(4) only 1st variant - that is booting into patched boot image and then making "Direct Install" is safe - it allows to check that patched boot image is suitable for ROM.
pedrix82 said:
...the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone....
Click to expand...
Click to collapse
IMHO that just means that you did not do your homework (I mean you have not read guides and discussions and Google info with links I provided) well enough to understand that with A/B slots partitions structure there is no separate /recovery partition in phone (instead, recovery is embedded into /boot image), and thus we cannot just "flash TWRP" into MiA2.
Instead, TWRP can only be embedded into boot image (patching previously flashed suitable boot image), which is made by installing TWRP.zip in temporarily booted TWRP.img. Thus, if you want to have both root and permanent TWRP (I still do not see why anybody needs permanent TWRP with rooted stock), first get root with patched boot image, and then install TWRP patching this Magisk-patched boot image once more.
And I do think that "TWRP 4pda edition" is working better than so called "official TWRP".

Found the solution,
First u need to get to the recovery menu by pressing vol up + power, tap it multiple times after retry boot...you have to be quick...and eventually will get to the android robot pic with "no command"....keep pressing till you get to the full recovery menu. (this might take multiple tries)
Then go to update using adb. (you need all the files for adb, usb drivers, latest mi a2 update zip, you can find tutorials in youtube/google )
after updating it should boot up fine with all data intact.
If latest update versions dont boot, try repeating will older version.
Make sure you backup everthing afterwards! and enable oem unlocking &usb debugging for potential future issues.
Hope this helps!

Phone stuck at black Mi logo

Hello, I never experienced this before so here I am trying to find some explanation, hopefully it's the right place... I have a Xiaomi Mi 5 Pro, few years old, sometimes slow but otherwise perfect, I changed the battery couple times.
Today I noticed it was at around 20% charge, I plug it to the wall, and leave it on the bed (turned on). After a few hours I go back to check on it and found the 100% indicator, but the phone was turned off.
I obviously try to turn it back on, but it gets stuck at the Mi logo (black screen with "unlocked" text below). I have installed a MIUI.eu rom ver. 11, twrp 3.2.3-0 recovery, and everything has been fine for years. I tried several times, still Mi logo (it's not bootloop, it's just stuck).
Suprised, I try to boot into recovery, and there I noticed that all the partitions are marked empty 0 bytes. I tried several things like backup, switching file format, restoring file system, etc., but it just won't work. It's like it has all been wiped and can't be mounted again.
I connected it to my desktop, MTP enabled from twrp, device recognized, storage completely empty. I remember I could see files there just the other day...
I tried all possible wipes, they won't work, either can't mount the partitions or other errors.
I already asked for suggestions elsewhere, which pointed me to fastboot flash using the adb/fastboot tools on Windows.
Well it says "Looking for devices...", the fastboot screen on the phone stays there for about 30 seconds, then it goes to the black Mi logo and then it shuts down.
Also if I boot in recovery, I can see it detected in the adb/fastboot tools screen, the scary part is that there it says "Bootloader: locked" (but it has been unlocked for years, and it even says unlocked in the black Mi screen!)
I'm lost, I never had anything like this, any suggestions to save the device? I would be really grateful

ZexDC said:
Well it says "Looking for devices...", the fastboot screen on the phone stays there for about 30 seconds, then it goes to the black Mi logo and then it shuts down.
Click to expand...
Click to collapse
You probably don't have proper drivers for Mi 5 installed, download MIFLASH UNLOCK 3.5.1108.44 from here https://xiaomifirmware.com/downloads/download-mi-unlock-3-5-1108-44/
Double click on MiUsbDriver and install fastboot driver. Then phone will stay in fastboot mode when connected to PC, so you can try to install some original fastboot rom. I don't know what is the problem.

Indie Zex said:
You probably don't have proper drivers for Mi 5 installed, download MIFLASH UNLOCK 3.5.1108.44 from here https://xiaomifirmware.com/downloads/download-mi-unlock-3-5-1108-44/
Double click on MiUsbDriver and install fastboot driver. Then phone will stay in fastboot mode when connected to PC, so you can try to install some original fastboot rom. I don't know what is the problem.
Click to expand...
Click to collapse
Thanks it was the driver stopping the fastboot.
Now I still cannot flash anything though, I get the following error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried different roms, different MiFlash, from terminal, but same error.
From recovery I still see empty not mounted partitions.
Any other suggestions?

Well I don't know. Have you tried to format data in TWRP? Go into Wipe/Format Data/type yes (this will wipe EVERYTHING on phone) then from main menu reboot into recovery again and see if things changed.

Indie Zex said:
Well I don't know. Have you tried to format data in TWRP? Go into Wipe/Format Data/type yes (this will wipe EVERYTHING on phone) then from main menu reboot into recovery again and see if things changed.
Click to expand...
Click to collapse
Yes that was the first thing I tried unfortunately that's where I found out something was off... I can't wipe any partition, I can't mount any partition, I tried to switch filesystem but no luck.
I was reading in the forums here about "sudden death" and it kinda feels that's what happened. Phone fine one day, dead the next with no real explanation...

ZexDC said:
I was reading in the forums here about "sudden death" and it kinda feels that's what happened. Phone fine one day, dead the next with no real explanation...
Click to expand...
Click to collapse
That's a bummer. I don't think that phone is dead, but it looks that it somehow locked itself. According to this guide https://flash-er.com/xiaomi-mi-5-flash-file/ you can flash fastboot roms only on unlocked devices. But you can't unlock it now in this state...

Indie Zex said:
That's a bummer. I don't think that phone is dead, but it looks that it somehow locked itself. According to this guide https://flash-er.com/xiaomi-mi-5-flash-file/ you can flash fastboot roms only on unlocked devices. But you can't unlock it now in this state...
Click to expand...
Click to collapse
It's very weird, I've been flashing lots of stuff in the past but I've never been locked out like this.
And the joke is that the black Mi logo screen still says "unlocked" as it should be... no idea, maybe it is programmed to just give up after some years.

Could be that your TWRP recovery is corrupted. You can install new one from a fastboot mode:
1. Copy latest twrp-3.5.2_9-0-gemini.img to your fastboot tools location on PC
2. Put the phone in fastboot mode (power + volume down) and connect it to the computer
3. Enter these commands in cmd prompt:
fastboot flash recovery twrp-3.5.2_9-0-gemini.img
fastboot boot twrp-3.5.2_9-0-gemini.img
Then the phone will boot into new TWRP so you can check if it's ok.

Indie Zex said:
Could be that your TWRP recovery is corrupted. You can install new one from a fastboot mode:
1. Copy latest twrp-3.5.2_9-0-gemini.img to your fastboot tools location on PC
2. Put the phone in fastboot mode (power + volume down) and connect it to the computer
3. Enter these commands in cmd prompt:
fastboot flash recovery twrp-3.5.2_9-0-gemini.img
fastboot boot twrp-3.5.2_9-0-gemini.img
Then the phone will boot into new TWRP so you can check if it's ok.
Click to expand...
Click to collapse
I tried that, it gives the following error:
I noticed that even from MiFlash the device id sometimes disappears, not sure if that's the no link error

I really don't know what's going on. Maybe you can try this tutorial (it is for Mi 9, but can be applied to all Mi phones)

Indie Zex said:
I really don't know what's going on. Maybe you can try this tutorial (it is for Mi 9, but can be applied to all Mi phones)
Click to expand...
Click to collapse
Thanks for trying I really appreciate. I did follow the tutorial, same error.
It's like the internal storage got fried or something? I have no clue