Database Develop

Stuck in fastboot

Hey folks,
I need your help;
After a forced shutdown due to a depleted batterie, my device only boots into Fastboot.
My Nexus 6 is unrooted and has stock Android 6.
If I try start, recovery mode, or factory reset, I only get the following error;
"failed to validate boot image: ret=-1"
Connecting it to a PC does not help, as the pc does not recognise the device (so I can not install the usb drivers).
I managed to boot the device once, but all the google aps crashed, and finally android itself crashed.
Now on around every 30th try (in starting android in normal mode), I'll get the follwing message:
"Decryption Unsuccessful, The password you entered is correct, but unfortunately your data is corrupt"
What can I do?

Olikay said:
Hey folks,
I need your help;
After a forced shutdown due to a depleted batterie, my device only boots into Fastboot.
My Nexus 6 is unrooted and has stock Android 6.
If I try start, recovery mode, or factory reset, I only get the following error;
"failed to validate boot image: ret=-1"
Connecting it to a PC does not help, as the pc does not recognise the device (so I can not install the usb drivers).
I managed to boot the device once, but all the google aps crashed, and finally android itself crashed.
Now on around every 30th try (in starting android in normal mode), I'll get the follwing message:
"Decryption Unsuccessful, The password you entered is correct, but unfortunately your data is corrupt"
What can I do?
Click to expand...
Click to collapse
sounds like you should flash a factory image.
ok, heres the problem. to flash a factory image, you need to unlock your bootloader. to unlock your bootloader, you have to enable to oem unlock setting in developer options. which means, you need to try to boot again, 40 times if need be. when you boot up, you need to go into settings, about phone, the press build number 3 times in a row. that will enable the developer options. go back one page, scroll up, and youll see it. go in there and enable oem unlock. now you can flash a factory image.

Yea dude, that doesn't look good at all. Have you ever installed any mod of any kind on the device before? Or was this just random and happened while 100% stock? Your best bet as Simms said, would be to try and get into your developer settings and turn on "allow oem unlocking" and "USB debugging". Then flashing a stock image.
Sent from my Nexus 6

There is no modification to the rom.
Unfortunately, I don't think I so get it booted anymore, the only think that might happen is that it brings me to decryption unsuccessful window and from there on reboot is the only option (also after waiting more than 10 seconds or hitting the power button to try and dismiss the message). Even if I did get into the OS which I succeed once close to the beginning of the problem, I would get so many popups of crashed Google apps that you could do nothing before it would crash the OS completely.

Olikay said:
There is no modification to the rom.
Unfortunately, I don't think I so get it booted anymore, the only think that might happen is that it brings me to decryption unsuccessful window and from there on reboot is the only option (also after waiting more than 10 seconds or hitting the power button to try and dismiss the message). Even if I did get into the OS which I succeed once close to the beginning of the problem, I would get so many popups of crashed Google apps that you could do nothing before it would crash the OS completely.
Click to expand...
Click to collapse
Damn, that's awful dude, I wanna say your Nexus isn't recoverable. Might have to send it in for repair to Google. If there was no modification to it at all, bring that up! You might get it fixed cheaper or free!
Sent from my Nexus 6

It's really sad, and it makes me think why the USB debugging mode is not enabled on default on every device for this very reason.
I did not root the device yet, as I did not wanted to risk to lose the warenty which it still should be under. So I guess I have no choice than to send it in.
I will try one last thing, and that is to hook it up to a Ubuntu powered computer, let's see if I can mount the phone' s drive with it.
I'll keep you folks updated.
UPDATE: negative on the Ubuntu idea, there is nothing mountable (Disk utility)

It works again! At least it seams for now...
This worked for me video ID: 0nDLvy8F5qk on youtube "Nexus 6 Hard Factory Reset Fastboot Bootloader Recovery Mode" from Jamie Wagner (I am not allowed to post links yet)
But I needed 20 tries to boot into factory reset.

if ya know your going to mod it at some point...maybe unlock it so if it does happen...you can fix it. thats my main reason for running an unlocked device. if you know what hits the fan...you can always fix it yourself. just a suggestion though.

Yourgodtim said:
if ya know your going to mod it at some point...maybe unlock it so if it does happen...you can fix it. thats my main reason for running an unlocked device. if you know what hits the fan...you can always fix it yourself. just a suggestion though.
Click to expand...
Click to collapse
Definitely! I would highly recommend just unlocking your bootloader and leaving it unlocked, with USB debugging on! This does not affect OTA updates at all and really, it's a last resort form of protection! My opinion of course!
Sent from my Nexus 6

unlock tbe bootoader
that the best thing youll do for your device, just in case. you dont have to modify anything, and itll still be unmodified.

Xiaomi Mi 9 stuck in a bootloop, now with no OS. Help needed

Yeah, I'm not feeling very smart right now.
Short story:
Accidentally wiped OS in TWRP, now only seem to have access to fastboot. Can I fix this? Flash another ROM? Anything? Bootloader is unlocked, can't seem to get into TWRP anymore. Power + Volume up only takes me to fastboot again.
Long story:
Magisk module caused a bootloop. Wanting to try and avoid a factory reset, I tried sideloading Magisk for TWRP which didn't work, ultimately gave up and wanted to perform a factory reset via TWRP, but I've been working late and ticked the wrong box without thinking. Bad idea, I know. Wiped system, yes.
Aside from feeling exceptionally stupid, can this situation be salvaged? The phone doesn't switch off, it just sits in fastboot. I have Minimal ADB and Fastboot on my PC. Any help will be greatly appreciated, really.

Just in case anyone else ends up with a similar problem, the resolution was fortunately rather straightforward - I needed to grab the Mi Flash tool (as it turns out, this version worked best), stock firmware for my version, go into fastboot (which was no issue as that was the only thing my phone would do) and then open the Mi Flash tool and flashing the firmware was pretty straightforward from there. I even managed to get a BSOD during the process, but it's not like it could get any worse, anyway. Rebooted, restarted the process and about 10-15 minutes later, my phone was happily booting again.

divided by zero said:
Just in case anyone else ends up with a similar problem, the resolution was fortunately rather straightforward - I needed to grab the Mi Flash tool (as it turns out, this version worked best), stock firmware for my version, go into fastboot (which was no issue as that was the only thing my phone would do) and then open the Mi Flash tool and flashing the firmware was pretty straightforward from there. I even managed to get a BSOD during the process, but it's not like it could get any worse, anyway. Rebooted, restarted the process and about 10-15 minutes later, my phone was happily booting again.
Click to expand...
Click to collapse
With Fastboot mode and Mi flash as fail safes , we can flash to our hears content with no worries !
Also a more automated tool is a custom mi flash tool by a developer called XiaimiToolV2 ,which has a dedicated mode for bricked phones or downloads the latest fastboot roms for you.

crs951 said:
With Fastboot mode and Mi flash as fail safes , we can flash to our hears content with no worries !
Also a more automated tool is a custom mi flash tool by a developer called XiaimiToolV2 ,which has a dedicated mode for bricked phones or downloads the latest fastboot roms for you.
Click to expand...
Click to collapse
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?

mstaglicic said:
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
Click to expand...
Click to collapse
I had excaxtly that witha my mi5 , completely dead .
Leave it on the charger for a little bit,mine after an unsuccessful flash with mi flash (catastrophic error message) it turned back on.
IF not download XiaomiTool V2 and try the option for bricked phones.

I tried that yesterday but that option is still in development. Only the modifications one is supported currently. As for the issue mentioned, maybe it's really just a matter of charging the phone first. Can't hurt either way.

mstaglicic said:
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
Click to expand...
Click to collapse
Try to use the EDL mode

How to force it to EDL by key combination or maybe deep flash cable ?
My Mi account is authorized for EDL flash but I cant get Mi9 into EDL mode on my PC ( Windows10 )

No OS, but working TWRP
Hi,
I have a similar problem with my mi 9.
I followed a really bad description for the update xiaomi.eu from MIUI10 to MIUI11.
https://www.chinahandys.net/xiaomi-eu-rom-update/
It recomended to wipe alvik / Art Cache, Cache AND System :crying:
So I do not have no OS any more. However, TRWP is still working.
I have a Backup but it did not work :crying:
Is there a better option than the Mi Flash tool?
Please help me!

Since you already have TWRP, download the latest Xiaomi.eu custom ROM available for the Mi 9, which is 9.11.7 to your computer.
Also download the latest TWRP by Mauronofrio from XDA which is 3.3.1-42.
Then use adb to transfer both the ROM and TWRP to your Mi 9.
In TWRP, install TWRP first and manually reboot to twrp using the vol up + power button.
In TWRP, install the ROM, do a factory reset, then finally reboot.
Sent from my MI 9 (Cepheus) using Tapatalk

sangbuana said:
Since you already have TWRP, download the latest Xiaomi.eu custom ROM available for the Mi 9, which is 9.11.7 to your computer.
Also download the latest TWRP by Mauronofrio from XDA which is 3.3.1-42.
Then use adb to transfer both the ROM and TWRP to your Mi 9.
In TWRP, install TWRP first and manually reboot to twrp using the vol up + power button.
In TWRP, install the ROM, do a factory reset, then finally reboot.
Sent from my MI 9 (Cepheus) using Tapatalk
Click to expand...
Click to collapse
Thank you very much for your reply.
When I tried to make my TWRP backup work I had several problems.
First was "vendor read only". So I went in TWRP to "mount" and unticked the "mount vendor partition read-only" (sounds easy, took me some time to find out)
Then I was able to do the restore without error message. However just boot loop and only the possibility to access TWRP.
After some while I realized that this restored the wiped system partition.
So I flashed the aktual MIUI 11 9.11.7 again and rebooted.
And it worked perfectly! :victory:
I did no Factory reset all the time, it seems that everything is perfect!
No lags, no problems with the camera, no issues with auto rotation.
Tom

Xiaomi MI A2 Bricked, Bootloop. Can't get recognized in fastboot and EDL mode

Hello guys, so, today i was trying to install miui 9 in my mi a2, then later going to update to miui 10. I was trying to install by flash mode (XiaoMiFlash) Everything was going fine, until my windows accidently turned off for updates (RIP). When my pc turned on, i was desperately opening miflash as fast that i could, but then when i try to install again it was saying "cannot recieve hello packet". I tried to restart it thinking that would fix it, but its just stuck in a MI logo with mi.com screen(Bootloop). I was trying to unplug usb cable and then putting again trying to fix it, clicking refresh to see if it appears, but it doesn't. Same with fastboot mode, doesn't get recognized. I really need help to fix it and sorry if i wrote something wrong, english is not my native language.

Same problem happened with me today. Any Solution?

Are you able to boot into fastboot?

Something similar happened to me once with the A2.
I somehow too managed to interrupt some update process and got stuck in the same scenario.
I could resolve it by getting one of these now superseded fastboot stock files with some installer scripts in them.
The scripts also wouldn't work, but I could install the firmware files one by one manually, following the script's content.
First off though, you could try to get into fastboot mode (as mentioned before), boot the official twrp img and flash the latest firmware zip file from here
Then you could go ahead and flash miui for the A2 like any other custom ROM (or did you just post in the wrong section and actually got an 6X? - seeing that you used miflash, it really seems like it..
Just in case here is the right thread for downloading miui for the A2: A2 miui port)

Yaroray said:
Are you able to boot into fastboot?
Click to expand...
Click to collapse
Hey, sorry for not awnsering for a long time. Yes, i can enter in fastboot, but the problem is that my MI A2 doesn't get recognized. (nothing happens if i try to flash it in fastboot mode).

i same that trouble, i can try to bootloader but when i connect usb to my pc it not recognized, i don't run anycommand from my PC,
I think if i change to second slot i will boot my phone, and i want to change slot without command "fastboot set active-slot "

I can't install twrp, make a hard reset, update by OTA, nothing O.o

SOLVED
Hi there.
I had my couple's mobile rooted with Magisk and MIUI Global 10.3. Once wanted to update twrp and the issues began. Actually the mobile isn't rooted but with unlocked bootloader, apparently.
I list the issues down below:
1) Trying to install twrp with fastboot by CMD, pressing enter after the command the cursor just blinks and nothing happens. At first it showed "waiting for device", so I installed adb drivers and the mobile appeared in Device Manager. It run once up to "sending 'recovery'" but not farther. The mobile was connected in fastboot mode indeed as well as in usb debugging but couldn't activate oem unlock as it stated it as unlocked and the option was dimmed.
2) Tried to unlock the mobile with Miflash_unlock and the phone was recognized, but the tool checked the device up to 50% and then showed that it Couldn't verify the device.
3) Then I tried to make a backup of the user data and doing a Hard Reset from settings. It went forward up to reboot, so I did, then it entered in fastboot mode for a few seconds and it powered off. Rebooted the phone and it was up and running as if nothing happened. So I cannot make a hard reset.
4) I can't enter the recovery too. If pressing volume - and power on it enters in fastboot mode. With volume + and power on it does the same With recovery enter tools isn't possible either. It seems as it's been corrupted.
5) I've just tried to flash the Global_8.0 rom with MiFlash 2019.12.6.0 and on the progress line it says "echo Mismatching image and device" How? I'm sure its a Mi Mix 2 'chiron' Rom, so... Anyway, I start to flash and the tool seems to progress but it never ends. So I disconnect the phone, reboot, and it keeps untouched running as before, OMG
6) On top of that I can't update android by OTA, as it gets downloaded, then reboot, then enters fastboot mode and after few seconds it powers off as before, and powering it on afterwards shows that it couldn't be updated
So I don't know what to do next. However, the mobile runs apparently ok.
May someone lend me a hand, please?
Thank you.

SOLVED: The Xiaomi Mi MIX 2 is up and running with the last firmware installed. The issue was that, as I build a new PC lately, I connected the phone in fastboot mode to the front USB ports, which are 3.0 version, and you need a 2.0 USB port at most, causing errors in MiUnlock and MiFlash.

Stuck with havoc OS and TWRP

Hello to everyone. I have problem with Mi Max 2, what i gave my mom last year. Device was bootloader unlocked and flashed with custom rom HAVOC , idk right version, some build of 2019. It worked for year without problem, but last night my mom was playing some games on phone, and it freeze. She didnt know what to do, so she left phone frozen untill battery drains and shut down. Then this morning she come to me with bootlop on phone, it comes to the havoc logo and just stay there. So i thought it isnt big deal, but when i try to boot in recovery mode, twrp does same thing. It freeze on startup logo and just stays there. TWRP is 3.2.3-0 version.
There comes more issues. I connect phone to PC, it doesnt see him. Nor in bootlop, fastboot, only in frozen recovery, and sees him only like universal USB in Device Manager, still dont shows anything in My PC.
I downloaded a lot of usb drivers for mi max 2, even installed them manually but there is no changes. In cmd, it recongnizes phone only when it is in bootlop in recovery mode, and only in that situation it shows on command /adb devices - the phone, when i try to to type command /adb reboot fastboot, cmd freezes and do nothing, phone isnt booting in fastboot. When i go in fastboot manually, power + vol down, it doesnt recongnises the phone, on command /adb devices now there is nothing, and even over that if i try to /adb flash recovery, it just says waiting for any device.
So theres my problem - i cant boot in system, i cant boot in twrp recovery, pc and platform tool doesnt sees my phone when it is in fastboot so i cant flash other twrp image. Is there any solution? can anyone tell me what to do, i rooted phones since like S2 in 2012 and flashed so many roms, but this situation i never had. I can understand that OS crashed down, but why TWRP trolls and cant be booted in...
Any solutions are welcome, phone is unusable like this.
P.S. phone didnt have any hardware damages, ever.

I don't have a solution and I only wish the best for you and your mom. How cool to have a mom running Havoc! I sure don't know everything so I could be wrong, but sometimes, rarely, phones break. I hope that's not the case here and don't give up yet, but I've been doing this a long time too (since S5) and what you've got there sounds bad. Your mom sounds badass and if her phone is broken, please get her something nice. A Moto G Stylus might be perfect. We've got havoc, and a flawless RR Q. She certainly deserves something nice and, if you're in America, Metro is giving them away free if you bring your number and switch. Best phone I ever had. Even better than oneplus 5. Good luck, Sir.

Press power off + volume down mean go to fastboot.
download orange fox recovery.zip and extract .img file
now connect your phone to pc and use command
fastboot boot extract_boot_image_name.img.
wait to boot
now flashed orange fox recovery.zip from recovery.
Okay done.
Download any rom for mi max 2 in xda rom section android 9 and android 10 based and
simply install rom...