Database Develop

[Q] File recovery after soft-brick

I have an HTC One M7 on T-Mobile, v4.4.3, with a locked bootloader and no root access (never got around to rooting). So the phone is basically completely untouched from a developer standpoint. I had previously accessed the developer options and I'm pretty sure I left USB debugging checked although not 100% positive.
The past few days my phone has been randomly rebooting, and then today I randomly found it in a state of apparent upgrading even though there are no new OTA updates (I checked yesterday). Then it was "optimizing apps" and going through all of them. Then it rebooted and ever since that point it has been stuck on the HTC ONE logo and will not boot to the home screen. I'm able to access the bootloader (HBOOT 1.57). I'm also able to access the stock recovery, from which I wiped the partition cache and rebooted with no success.
I have a ton of pics and videos from the first year of my son's life on the phone and stupidly did not back them up. I really want to avoid doing a factory reset if possible. Is there any way to recover these files?
I installed minimal ADB and fastboot. From within fastboot on the phone, I can see my device when typing "fastboot devices" in the command prompt. However, it does not list any devices when I enter "adb devices" in the command prompt, regardless of whether my phone is in the bootloader, fastboot, recovery, or stuck on the logo screen. I reinstalled updated HTC drivers and also tried with a universal ADB driver. I've tried multiple usb cables and all USB 2.0 ports, using Windows 7. While in fastboot, when I connect my phone to PC via usb cable, the computer makes the typical sound that it does when a USB device is connected and unconnected, however no drive/mount shows up.
All I want to do is find my device somehow on the PC and extract my photos and videos. I was hoping to use "adb pull" to do this but it just won't find my device. At this point, unlocking the bootloader and installing a custom recovery will wipe all data anyway, correct? Is there any way that I can recover my data in this situation?
Any help would be greatly appreciated since I'm at a complete loss and losing this data would be terrible. Thanks so much in advance!

mac12383 said:
I have an HTC One M7 on T-Mobile, v4.4.3, with a locked bootloader and no root access (never got around to rooting). So the phone is basically completely untouched from a developer standpoint. I had previously accessed the developer options and I'm pretty sure I left USB debugging checked although not 100% positive.
The past few days my phone has been randomly rebooting, and then today I randomly found it in a state of apparent upgrading even though there are no new OTA updates (I checked yesterday). Then it was "optimizing apps" and going through all of them. Then it rebooted and ever since that point it has been stuck on the HTC ONE logo and will not boot to the home screen. I'm able to access the bootloader (HBOOT 1.57). I'm also able to access the stock recovery, from which I wiped the partition cache and rebooted with no success.
I have a ton of pics and videos from the first year of my son's life on the phone and stupidly did not back them up. I really want to avoid doing a factory reset if possible. Is there any way to recover these files?
I installed minimal ADB and fastboot. From within fastboot on the phone, I can see my device when typing "fastboot devices" in the command prompt. However, it does not list any devices when I enter "adb devices" in the command prompt, regardless of whether my phone is in the bootloader, fastboot, recovery, or stuck on the logo screen. I reinstalled updated HTC drivers and also tried with a universal ADB driver. I've tried multiple usb cables and all USB 2.0 ports, using Windows 7. While in fastboot, when I connect my phone to PC via usb cable, the computer makes the typical sound that it does when a USB device is connected and unconnected, however no drive/mount shows up.
All I want to do is find my device somehow on the PC and extract my photos and videos. I was hoping to use "adb pull" to do this but it just won't find my device. At this point, unlocking the bootloader and installing a custom recovery will wipe all data anyway, correct? Is there any way that I can recover my data in this situation?
Any help would be greatly appreciated since I'm at a complete loss and losing this data would be terrible. Thanks so much in advance!
Click to expand...
Click to collapse
unfortunately, you need a booted rom or a custom recovery to use adb commands, so you can't pull your files from the bootloader or from the stock recovery. You already wiped cache and tried to reboot... Not much you can do except maybe to try reflashing the firmware and see if your phone can boot. Can you post the output of "fastboot getvar all" except imei and serialno?

alray said:
unfortunately, you need a booted rom or a custom recovery to use adb commands, so you can't pull your files from the bootloader or from the stock recovery. You already wiped cache and tried to reboot... Not much you can do except maybe to try reflashing the firmware and see if your phone can boot. Can you post the output of "fastboot getvar all" except imei and serialno?
Click to expand...
Click to collapse
Thanks for the quick reply. Here's the info.
Would reflashing firmware require the bootloader to be unlocked? It wouldn't wipe my data?

mac12383 said:
Thanks for the quick reply. Here's the info.
Would reflashing firmware require the bootloader to be unlocked? It wouldn't wipe my data?
Click to expand...
Click to collapse
no with s-on, bootloader must be locked to flash firmware.
What you could try is to download the 6.10.531.9 RUU and extract the firmware.zip and flash it to your phone.
Firmware.zip must be in the same folder where adb and fastboot are then open a command prompt (minimal adb/fastboot):
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fasboot reboot
If this doesn't work I think theres nothing we can do (to access your files) At least you can restore your phone using the complete RUU

alray said:
no with s-on, bootloader must be locked to flash firmware.
What you could try is to download the 6.10.531.9 RUU and extract the firmware.zip and flash it to your phone.
Firmware.zip must be in the same folder where adb and fastboot are then open a command prompt (minimal adb/fastboot):
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fasboot reboot
If this doesn't work I think theres nothing we can do (to access your files) At least you can restore your phone using the complete RUU
Click to expand...
Click to collapse
Thanks, I'll give that a try soon, probably tomorrow, and let you know how it goes. Appreciate the help

mac12383 said:
Thanks, I'll give that a try soon, probably tomorrow, and let you know how it goes. Appreciate the help
Click to expand...
Click to collapse
I flashed it successfully, but unfortunately the phone still did not boot to the home screen. I'll hold off on wiping everything for a little longer in case anyone has any other ideas. Thanks for the help!

HTC and T-Mobile were of no help, as suspected. I guess I just find it strange that there's NO WAY to recover data from a soft bricked phone. If I was some big-time criminal who was arrested by the FBI and my phone was seized in this condition, their analysts would have no way of getting into my phone and recovering the data? Maybe I just watch too many crime shows, I don't know...but that seems a bit unbelievable. Is there no way to (carefully) take it apart and access the hard drive in some other way? I'm desperate...

mac12383 said:
HTC and T-Mobile were of no help, as suspected. I guess I just find it strange that there's NO WAY to recover data from a soft bricked phone. If I was some big-time criminal who was arrested by the FBI and my phone was seized in this condition, their analysts would have no way of getting into my phone and recovering the data?
Click to expand...
Click to collapse
Yes they would disassemble the phone, de-solder the emmc chip and extract its data which is not an easy task...
Maybe I just watch too many crime shows, I don't know...but that seems a bit unbelievable. Is there no way to (carefully) take it apart and access the hard drive in some other way? I'm desperate...
Click to expand...
Click to collapse
There is no hard drive in your phone, its a memory chip (emmc). It is soldered to the main board and can't be removed by the user.
see the chip highlighted in orange? This is where your data is stored.
If you can't boot to the OS, your bootloader is still locked, and you have already tried to erase cache and reflashed the firmware, afaik, there's nothing more you can try

alray said:
Yes they would disassemble the phone, de-solder the emmc chip and extract its data which is not an easy task...
There is no hard drive in your phone, its a memory chip (emmc). It is soldered to the main board and can't be removed by the user.
see the chip highlighted in orange? This is where your data is stored.
If you can't boot to the OS, your bootloader is still locked, and you have already tried to erase cache and reflashed the firmware, afaik, there's nothing more you can try
Click to expand...
Click to collapse
I was afraid of that. Thanks for all your help though

Locked bootloader and can't boot into ROM or Recovery. (Fixed!)

Well, I really did it this time. In my efforts of messing with the M Preview build and trying to eliminate the "verification failed" startup message I made the mistake of locking the bootloader. Now the phone will not boot into Android or into Recovery. I'm stuck in Bootloader and it won't let me "fastboot OEM unlock" the device because in order to do this you need to boot into Android and tick the box to allow OEM unlocking (which I also unticked before getting into this mess, like an idiot).
EDIT: Got it resolved!
In order to get into Recovery I had to use the following commands in the bootloader:
fastboot format cache
fastboot format userdata
After doing this I was able to boot into recovery. However, recovery showed 0MB available storage and wouldn't mount /data, which prevented me from installing anything. It also wouldn't allow me to copy anything to the SD card using Android File Transfer or ADB sideloading.
To solve this I went into "Wipe" while in recovery and did a full format (the one that requires you to type "yes" before proceeding"
After doing this and booting back into recovery, I had full storage space back and recovery was able to mount /data. At this point I just copy/pasted the 5.1.1 ROM onto the sdcard with Android File Transfer. Once installed, I flashed the ROM and it booted right up.
I then skipped through the setup to get to settings and in developer settings I ticked the box to allow OEM unlocking. After doing that, I booted back into the bootloader and used the fastboot command "fastboot oem unlock" to unlock the bootloader again.
Once that was done I was able to use fastboot commands to flash the M preview all over again.
Hopefully you don't find yourself in this mess, but if you do, I'm hoping the above solution works for you.

sn0warmy said:
Well, I really did it this time. In my efforts of messing the the M Preview build and trying to eliminate the verification failed startup message I really locked up the phone. I locked the bootloader and now the phone will not boot into either recovery or the ROM. It won't let me "fastboot OEM unlock" the device either because it requires me to go into settings and check the allow OEM unlock. However, since I can't boot into the ROM, I cannot do that.
I'm really stuck here. Any ideas?
Click to expand...
Click to collapse
Hope you can RMA it

akellar said:
Hope you can RMA it
Click to expand...
Click to collapse
Well.... s**t.

sn0warmy said:
Well.... s**t.
Click to expand...
Click to collapse
Is TWRP installed?

WAIT!!
I did the following:
- fastboot format cache
- fastboot format userdata
And the phone now boots into TWRP. It won't boot fully but it will boot into recovery. I'm trying to sideload a ROM now but I can't access the storage.
Edit: enabled ADB sideload so I can ADB push a ROM to the SD card to flash. Does anyone know the exact root folder name for the sd card to pusht he ROM to? Is it /data/media/?

I did something similar this past weekend while trying to do the 5.1.1 upgrade with the OTA files before the Factory images were available.
Try and use the WugFresh tool to wipe the cache and such, and try some of the other obvious settings in the tool.
It was late and I'm not 100% sure what I did but I do remember reflashing the LRX22C from the factory image using the tool. Everything I did was from the tool minus the 5.1 OTA that came through once I was able to get back into the device. From there I was able to unlock the bootloader again.
I was worried myself that I might have to send the phone back but I just kept trying, don't give up just yet. I've been told many times it's almost impossible to brick an android device now a days.
Good luck!

sn0warmy said:
WAIT!!
I did the following:
- fastboot format cache
- fastboot format userdata
And the phone now boots into TWRP. It won't boot fully but it will boot into recovery. I'm trying to sideload a ROM now but I can't access the storage.
Edit: enabled ADB sideload so I can ADB push a ROM to the SD card to flash. Does anyone know the exact root folder name for the sd card to pusht he ROM to? Is it /data/media/?
Click to expand...
Click to collapse
Enable MTP in TWRP then drag n drop.

rootSU said:
Enable MTP in TWRP then drag n drop.
Click to expand...
Click to collapse
Can't access device storage.
However, I was able to ADB push the ROM to the SDcard. But when I try and install the ROM it gives me a bunch of errors saying "unable to mount '/data'" and "unable to mount storage"
Ideas?

sn0warmy said:
Can't access device storage.
However, I was able to ADB push the ROM to the SDcard. But when I try and install the ROM it gives me a bunch of errors saying "unable to mount '/data'" and "unable to mount storage"
Ideas?
Click to expand...
Click to collapse
Assuming you tried ticking data in twrp mounts...
In twrp, try and format data again. If that fails, try to format it as another file system such as f2fs before formatting it back to ext4

rootSU said:
Assuming you tried ticking data in twrp mounts...
In twrp, try and format data again. If that fails, try to format it as another file system such as f2fs before formatting it back to ext4
Click to expand...
Click to collapse
Success!
TWRP was also reporting 0mb available storage. I went into Wipe and performed a full format. Booted back into recovery and storage was showingt he full amount again. I was then able to plug the phone in and enable MTP and drag/drop the 5.1.1 ROM onto the SD card. Just flashed it and it booted right up!
I'm going to update the OP with all this info just in case someone else runs into the issue and needs help.
Thanks for your help!

sn0warmy said:
Well, I really did it this time. In my efforts of messing with the M Preview build and trying to eliminate the "verification failed" startup message I made the mistake of locking the bootloader. Now the phone will not boot into Android or into Recovery. I'm stuck in Bootloader and it won't let me "fastboot OEM unlock" the device because in order to do this you need to boot into Android and tick the box to allow OEM unlocking (which I also unticked before getting into this mess, like an idiot).
Click to expand...
Click to collapse
Hi,
I faced the same condition like you experienced, with some differences:
- the phone stuck in "Google" logo
- stock recovery is accessible from bootloader
- I am unable to mount sdcard or install rom from sd card, but could conduct adb sideload
However, am stuck with verifying update package showing :
E: footer is wrong
E: signature verification failed
any ideas what to do next?
================ edited- add below info on how I got stuck
So my N6 was still on 5.0 (has not been updated to 5.1). I decided to try the M preview. I downloaded the preview, and began the process as follows:
1. reboot into bootloader
2. fastboot oem unlock
3. flash-all (success on loading the bootloader and radio, but error on updating the image)
4. hence i followed to flash individually:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
5. and comes the stupid thing ! --> fastboot oem lock (really really regret why I did this)
6. and then once reboot, it stuck in Google logo forever
However, I am still able to access:
- bootloader (fastboot recognize the device, but wouldn't allow me to fastboot oem unlock)
- able to go to stock recovery, and as mentioned above:
I am unable to mount sdcard or install rom from sd card, but could conduct adb sideload
However, am stuck with verifying update package showing :
E: footer is wrong
E: signature verification failed
I tried to adb sideload the M preview image and 5.1 LMY47I but both showing the above error....
hope you can shed some light on this...

Please does anyone have a solution to this? please help me

Iambenqazy said:
Please does anyone have a solution to this? please help me
Click to expand...
Click to collapse
A solution to what? Keep in mind your problem may be different from the OP's issue, so if you want people to help you it's necessary to provide plenty of information, such as what you were trying to do, how you tried to do it, and any other information that you believe may be useful.

Strephon Alkhalikoi said:
A solution to what? Keep in mind your problem may be different from the OP's issue, so if you want people to help you it's necessary to provide plenty of information, such as what you were trying to do, how you tried to do it, and any other information that you believe may be useful.
Click to expand...
Click to collapse
.
OK What i was trying to do was to flash a stock recovery, i start it by running the flash-it all.bat file in the factory image zip, it changed the user interface of the bootloader after first reboot and and had an error for "archive: recovery.sig not found" (something like). the phone status shows Software Version: Modified and fastboot oem unlock dont give the confirmation.
and
now my phone wont even boot to the bootloader, everything turned black. please hellp!!!!:crying::crying:

If you can't even get into the bootloader (volume down and power) you may have to have the device serviced. Do you get a response when you type "adb devices"?

Iambenqazy said:
.
now my phone wont even boot to the bootloader, everything turned black. please hellp!!!!:crying::crying:
Click to expand...
Click to collapse
Maybe it just crashed at a black screen? Does a very long press of the power button (over 10 secs) cause it to react?
Or maybe the battery is empty? Try connecting the power supply for some time.

i did that but no response.

Iambenqazy said:
i did that but no response.
Click to expand...
Click to collapse
The very dead battery is a real possibility. The thing is, using the charger that came with the phone isn't going to help. If you think the battery being dead is a possibility, you would need to plug the phone into a USB port on a PC, that is a very slow charge. Leave it on there overnight then unplug and replug. If the led at the top of the screen lights or the battery icon shows on the screen, you have hope. At this point using the original charger should get the battery going again. In this case, plan on replacing the battery.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Sprint htc m8 stuck at udating partition details

Stock Rom kitkat 4.4.2 rooted, unlocked, s-off. Was in recovery and accidentally hit the "middle button". Been stuck on "updating partition details" for 12 hours. I've searched and can't find the answer, but I'm relatively new so maybe I'm not looking for the right thing. Please be somewhat specific as the jargon is also something I am learning. I know nothing about partitions so I have no idea what my phone is even doing. Thanks guys. Love ya all and would be lost without you!!

kseawright76 said:
Stock Rom kitkat 4.4.2 rooted, unlocked, s-off. Was in recovery and accidentally hit the "middle button". Been stuck on "updating partition details" for 12 hours. I've searched and can't find the answer, but I'm relatively new so maybe I'm not looking for the right thing. Please be somewhat specific as the jargon is also something I am learning. I know nothing about partitions so I have no idea what my phone is even doing. Thanks guys. Love ya all and would be lost without you!!
Click to expand...
Click to collapse
What were you doing in recovery?
Have you tried holding the power button + volume up button to reboot the phone?

kseawright76 said:
Stock Rom kitkat 4.4.2 rooted, unlocked, s-off. Was in recovery and accidentally hit the "middle button". Been stuck on "updating partition details" for 12 hours. I've searched and can't find the answer, but I'm relatively new so maybe I'm not looking for the right thing. Please be somewhat specific as the jargon is also something I am learning. I know nothing about partitions so I have no idea what my phone is even doing. Thanks guys. Love ya all and would be lost without you!!
Click to expand...
Click to collapse
Hello,
I just tried the same thing in twrp...I had to press the Home button a few(maybe 10) times to get back to the main screen.
Phone booted normally afterwards.

Help..,.what if my phone dies!!!
Sloth said:
Hello,
I just tried the same thing in twrp...I had to press the Home button a few(maybe 10) times to get back to the main screen.
Phone booted normally afterwards.
Click to expand...
Click to collapse
Was trying to update firmware to Lolipop using FUU tool. 45 minutes later it still hadnt done anything so I ended task. Now HTC toolkit cant find device at all!!! Where do I start? What do I need to install/flash and where?? Is my device charging while connected to my pc or is it going to die and brick?????

kseawright76 said:
Was trying to update firmware to Lolipop using FUU tool. 45 minutes later it still hadnt done anything so I ended task. Now HTC toolkit cant find device at all!!! Where do I start? What do I need to install/flash and where?? Is my device charging while connected to my pc or is it going to die and brick?????
Click to expand...
Click to collapse
You were trying to update firmware using twrp?

First, I would suggest plugging your phone into a wall outlet and charging it until it's fully charged. You can get to the bootloader with the phone off by pressing power + volume down. Afterwards, I suggest running the latest RUU, not simply a FUU. This is done from the bootloader, not TWRP.

NO
sloth said:
you were trying to update firmware using twrp?
Click to expand...
Click to collapse
used generic fuu tool

Generic FUU
Magnum_Enforcer said:
First, I would suggest plugging your phone into a wall outlet and charging it until it's fully charged. You can get to the bootloader with the phone off by pressing power + volume down. Afterwards, I suggest running the latest RUU, not simply a FUU. This is done from the bootloader, not TWRP.
Click to expand...
Click to collapse
4.25.651.18 Full Firmware from RUU (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347796613
Generic Firmware Update Utility (FUU)
These are what I used. Put phone in fastboot manually...maybe I flashed straight from bootloader and not fastboot? or am I being stupid and its the same?
ADB No Device Found
Recovery No Device Found (there was a recovery at first but I lost it after I tried to flash another image)
Fastboot No Device Found
Ok Cleaned up my computer and got someything out of fastboot:
List of devices attached
adb reboot bootloader
error: device not found
fastboot reboot bootloader
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
umm,.....huh? is it telling me what to do?

Firmware, boot image, or recovery
what do I do first?

Dont unplug
FUU utility told me if update fails not to unplug or it will brick but my battery is going to die...I'm panicking

Have Fastboot
Ok I have fastboot but no adb...now what? Im using htc toolkit...not sure if its up to date...

kseawright76 said:
Ok I have fastboot but no adb...now what? Im using htc toolkit...not sure if its up to date...
Click to expand...
Click to collapse
Run the latest RUU from bootloader.
For future reference adb works while booted to recovery or OS/rom
Fastboot works in bootloader/fastbootusb

RUU
Stock or updated firmware? My phone still runs 4.4.2... I tried everything I could think of...still no recovery or adb...Im not sure which ruu to use...please be a little more specific and thank you so much for responding. I was up until 3:30 am trying to figure this out...Im super tired, frustrated, and heartbroken.

How do i run it? Flash to where? Where should my sdk and adb be on my computer? Is there a more recent version of the tool kit? Do i want to flash from oem ruu? I used to have a bunch of different utilities on my computer and erased what I could fine but there is adb all over the place...I have a few phones...unfortunately. Do i need to relock bootloader? What about recovery? Can I create another account on my pc and avoid the other programs? Can I or do I need to sideload or push anything? I cant even tell if I still have drivers or good ones...phone is just sitting on black screen with silver htc on it

kseawright76 said:
How do i run it? Flash to where? Where should my sdk and adb be on my computer? Is there a more recent version of the tool kit? Do i want to flash from oem ruu? I used to have a bunch of different utilities on my computer and erased what I could fine but there is adb all over the place...I have a few phones...unfortunately. Do i need to relock bootloader? What about recovery? Can I create another account on my pc and avoid the other programs? Can I or do I need to sideload or push anything? I cant even tell if I still have drivers or good ones...phone is just sitting on black screen with silver htc on it
Click to expand...
Click to collapse
Was going through my sd card...i have twrp backups and Titanium backups but i dont know what to do with them. When boot into fastboot on the htc toolkit a number and "fastboot" come up on screen. That number is the folder my twrp backups are in.

Still stuck
Please help. I have tried flashing I dont know how many times and its not working. Im not sure what to flash or how. Tried in toolkit, command prompt, and fuu. Command prompt keeps telling me cant load file. I dont care what I lose or dont lose I just want my phone to work again. Still have fastboot and phone still says everything it should while booted into fastboot USB. I was on my computer all day yesterday until 4am today and had to be up to get kids to school. Im sooo tired and frustrated. PLEASE SOMEONE TAKE THE TIME TO HELP ME FIND THE RIGHT FILE AND TELL ME HOW AND WHERE TO FLASH IT. IM SORRY BUT IM STILL LEARNING

Troubles with my HTC One Mini 2

Hey,
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
S-ON, no-debugging usb, Bootloader locked and can't unlock him... I already tried with htc-dev, everything works but nothing appair on my screen to confirm the unlocking.
I'm really stuck, searched lot of things on google, ....
I used fastboot, and ADB, the first one recognize my device, but the last one not. I can't boot on RUU mode neither.
Any ideas?

AzweL said:
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
Click to expand...
Click to collapse
The very first thing I recommend you to do, is to download the right recovery and install it via command
Code:
fastboot flash recovery recovery.zip
Let me know if you run into any further troubles.

AzweL said:
Hey,
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
S-ON, no-debugging usb, Bootloader locked and can't unlock him... I already tried with htc-dev, everything works but nothing appair on my screen to confirm the unlocking.
I'm really stuck, searched lot of things on google, ....
I used fastboot, and ADB, the first one recognize my device, but the last one not. I can't boot on RUU mode neither.
Any ideas?
Click to expand...
Click to collapse
Hi,
Frist in boot loader check your OS version it should be something like 2.19.401.2 or lower than this.
NB: ALWAYS TRY WITH MORE THAN 75% BATTERY, AND THAT FOR ANY CODE TO WORK PROPERLY, MAKE SURE TO SELECT FASTBOOT BY POWER KEY IN BOOTLOADER
Anyway, if you can enter fastboot, then you have some chance of recovering your device and because you have S-Off it is going to be a bit difficult.
First download this stock boot file : https://mega.nz/#!lEAVwRSL!wrP2hi6GEYLeJaPf2ssZo9wCtSi7E4yfyUHgh3Q3XSs
Then place this file in the ADB folder, then run command :
To flash boot file command is:
Code:
- Fastboot Devices (this command is important to know if the device is connected and accepting and responding commands)
- fastboot flash boot boot_signed.mg (assuming this is the name you saved the file with)
- fastboot reboot bootloader
Also download Stock Recovery: https://mega.nz/#!gVJE1Bxa!6SwXStAD8p-XlnQiPkRcdNo_ITFD1ykn-tN6wIBVi1I
Place this in ADB folder and run command:
Code:
fastboot flash recovery stockrec.img // (assuming that is the name you have saved the file with), only after flashing this you will know if the device has any OS, if OS exists it will boot up.
fastboot erase cache
Attempt and let us know how it went...Good Luck

Bootloop after October security update on rooted device.

Hello, I have some problems on my Mi A2. I rooted the device in August to enable Camera2API (getting stuck in the security update of the same month.). I installed Magisk and everything was going well. Then came a notification regarding the October update. I clicked to upgrade and by the time it was done, the device was working perfectly until the moment it completely discharged its battery. After that it gets into Bootloop on the Android One boot screen. I would like some suggestions for the solution. Thanks.

until the moment it completely discharged its battery
Click to expand...
Click to collapse
same here! I am not rooted and not unlocked.

Exactly the same here...

fly23 said:
same here! I am not rooted and not unlocked.
Click to expand...
Click to collapse
This was 2 days ago. It worked again after about 150 reboots. Or i pushed a special button combination, I don't know.
In betweet I did one "fastboot reboot".
Now I have the same problem again after empty battery. Bootloop.
This is the worst android phone I ever bought after HTC desire, Galaxy Nexus, Nexus 5, 5X. I will never again buy a budget phone or a xiaomi.

I did a factory reset this morning, and itgot stuck on an Android One screen. I am trying to figure out how to reflash it, but it doesn't seem to like the firmware. Not sure if I have to unlock the bootloader? I am not family with any of this stuff. I was supposed to ship the phone to the buyer today, but I guess I may have to kill the deal and refund them. This may be the last Xiaomi I buy.
https://imgur.com/a/5J51w3D

for me helped that thing
1. boot manually into fastboot mode
2. Change slot, reboot to fastboot
3. Change slot again.
4. After that reboot to system completed succesfully
but that sh*t came back again in a week for me

[email protected] said:
for me helped that thing
1. boot manually into fastboot mode
2. Change slot, reboot to fastboot
3. Change slot again.
4. After that reboot to system completed succesfully
but that sh*t came back again in a week for me
Click to expand...
Click to collapse
How do you change slot? The fastboot screen does not have any options/menu for me. It is just a picture.

clocks11 said:
How do you change slot? The fastboot screen does not have any options/menu for me. It is just a picture.
Click to expand...
Click to collapse
Yeah, I wonder that as well.
The arrow down + power button combination just keeps the phone frozen on a fancy picture with "fast boot" written at the bottom of the screen.

clocks11 said:
How do you change slot? The fastboot screen does not have any options/menu for me. It is just a picture.
Click to expand...
Click to collapse
You need PC for that
Boot into fastboot (vol - + PWR)
Then use fasboot from terminal
First look which slot is active by typing
fastboot getvar current-slot
Then we can change active slot using this commands
fastboot --set-active=a
or:
fastboot --set-active=b

Unfortunately, to be able to switch booting slot one needs fully unlocked phone (bootloader and critical partitions in our case).
Being fully unlocked, one can boot device in fastboot into TWRP, and from there:
- change slots
- wipe Dalvik/Art cache (and other Cache partition if present) - which in turn very often helps to recover from OTA-generated bootloop

Aerobatic said:
Unfortunately, to be able to switch booting slot one needs fully unlocked phone (bootloader and critical partitions in our case).
Being fully unlocked, one can boot device in fastboot into TWRP, and from there:
- change slots
- wipe Dalvik/Art cache (and other Cache partition if present) - which in turn very often helps to recover from OTA-generated bootloop
Click to expand...
Click to collapse
I think this is why my phone is completely bricked. It does not have an unlocked bootloader, so it seems I can't flash firmware on it. I will likely never buy Xiaomi again after this. I just was doing a factory reset since I had sold the phone.

[email protected] said:
for me helped that thing
1. boot manually into fastboot mode
2. Change slot, reboot to fastboot
3. Change slot again.
4. After that reboot to system completed succesfully
but that sh*t came back again in a week for me
Click to expand...
Click to collapse
this method works perfectly to me :good: ! my Mi A2 update to Oct 5 2019 patch okk. but i want to restart my phone. after restart, my phone is bootloop then luckily i found this usefull guide. thanks you very much again! Android One on Xiaomi is really sh*t.

ngohoainam said:
this method works perfectly to me :good: ! my Mi A2 update to Oct 5 2019 patch okk. but i want to restart my phone. after restart, my phone is bootloop then luckily i found this usefull guide. thanks you very much again! Android One on Xiaomi is really sh*t.
Click to expand...
Click to collapse
I'm still not clear how to change slot. Does the the phone have to be unlocked for this? Is special PC software needed? My A2 has been a brick for almost a week now.

clocks11 said:
I'm still not clear how to change slot. Does the the phone have to be unlocked for this? Is special PC software needed? My A2 has been a brick for almost a week now.
Click to expand...
Click to collapse
yes. you need your phone to be unlocked Bootloader and Critical Partition to use fastboot. more info here ( read Prerequisites carefully )
after you unlocked your phone and unlock Critical Partition. turn off you phone and after that press both Power and volumn down button at the same time. then your phone is booted to fastboot mode.
in fastboot mode. type fastboot getvar current-slot . after that the system will return your current slot. example: b
then you type fastboot --set-active=a
then you disconnect your phone to PC and then reboot again.
then you turn off your phone again and turn your phone to fastboot mode. then you type this command again: fastboot --set-active=b
then you disconnect your phone and boot your phone normally. after that your phone is fixed from bootloop.
ps: remember to download the driver and minimal fastboot so that your pc recognize your phone is connected to your pc

ngohoainam said:
yes. you need your phone to be unlocked Bootloader and Critical Partition to use fastboot. more info here ( read Prerequisites carefully )
after you unlocked your phone and unlock Critical Partition. turn off you phone and after that press both Power and volumn down button at the same time. then your phone is booted to fastboot mode.
in fastboot mode. type fastboot getvar current-slot . after that the system will return your current slot. example: b
then you type fastboot --set-active=a
then you disconnect your phone to PC and then reboot again.
then you turn off your phone again and turn your phone to fastboot mode. then you type this command again: fastboot --set-active=b
then you disconnect your phone and boot your phone normally. after that your phone is fixed from bootloop.
ps: remember to download the driver and minimal fastboot so that your pc recognize your phone is connected to your pc
Click to expand...
Click to collapse
Unfortunately, I think I am screwed, as the phone was not unlocked prior to my boot issue. So I am not sure there is anything I can do. I can get to fastboot though.