Hello everyone!
As the title states, my Xiaomi mi 9 is stuck in fastboot mode, after i tried installing the latest unofficial port of Lineageos 17.1 for the Mi 9.
I can not exactly remember how it happened but i guess i must have wiped the phone after installing the custom rom. Silly me...
I tried the following things to try to unbrick my phone:
1. Using the Mi Flash Tool in order to flash the official Xiaomi firmware onto my device. I flashed these versions: 11.05 global fastboot, 11.08 EEA fastboot, 11.06 global fastboot. None of them worked. My phone would show up on the flash tool and the flashing itself was always marked as successfull but sadly my phone would not boot into MIUI and just stay frozen in fastboot mode. Restarting the device did not help.
2. Flashing twrp and trying to boot into it. Sadly, this also did not work out for me. Every time after i would successfully flash the .img file and reboot my device, the damn fastboot screen appeared.
So is there anything i can do? No matter what i try, my device goes into fastboot mode. I tried searching for the answer myself but those who had the similar issue did either not receive any useful answers or the Mi Flash Tool magically worked for them after a few attempts.
Thank you in advance!
Hello,
As long as you have access to fastboot mode, am sure you can recover your device.
You need to download the official ROM that corresponds to your specific devices. If it is global version, download the global version.
Also, before flashing, make sure you unlock the bootloader.
jaybirdxyz said:
Hello everyone!
As the title states, my Xiaomi mi 9 is stuck in fastboot mode, after i tried installing the latest unofficial port of Lineageos 17.1 for the Mi 9.
I can not exactly remember how it happened but i guess i must have wiped the phone after installing the custom rom. Silly me...
I tried the following things to try to unbrick my phone:
1. Using the Mi Flash Tool in order to flash the official Xiaomi firmware onto my device. I flashed these versions: 11.05 global fastboot, 11.08 EEA fastboot, 11.06 global fastboot. None of them worked. My phone would show up on the flash tool and the flashing itself was always marked as successfull but sadly my phone would not boot into MIUI and just stay frozen in fastboot mode. Restarting the device did not help.
2. Flashing twrp and trying to boot into it. Sadly, this also did not work out for me. Every time after i would successfully flash the .img file and reboot my device, the damn fastboot screen appeared.
So is there anything i can do? No matter what i try, my device goes into fastboot mode. I tried searching for the answer myself but those who had the similar issue did either not receive any useful answers or the Mi Flash Tool magically worked for them after a few attempts.
Thank you in advance!
Click to expand...
Click to collapse
fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
this temporarily boots you into TWRP so you can reflash TWRP again. with this method the TWRP will be deleted once you reboot si you need to reflash TWRP in TWRP. then dont reboot, flash a Good working rom.
Similar problem here.
The line fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
brings up
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
ai5g said:
Similar problem here.
The line fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
brings up
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
Click to expand...
Click to collapse
try other TWRP images? or your boot partition fried?
fastboot flash boot twrp.img and see What happens
Related
Solved !!!
I was able to flash global miui 9.5.
Hi ,
So after finally the bootloader is unlocked I tried to flash the global rom via mi flash tool.
Update failed and an error message is update crc list failed !
I tried flashing back the chinse rom and I get the same error.
I can boot the device to recovery mode, but its mi recovery 3.0, I have 3 options:
1.wipe data
2. boot to system
3. connect via pc suite
tried with pc suite but it says my device isn't supported.
The computer recognizes the device via MiFlash tool but in adb via cmd when I type adb devices I get blank row and its unable to find the device.
how can I make my phone usable again please?
I have tried many things I found on google but nothing worked.
Thank you all
Hi
Is fastboot mode able?
Try to unlock again.
what do you mean able?
the phone is recognized via Mi Flash tool but in adb via cmd it is not recognized.
I waited 700 hours for the unlock and the phone is unlocked.
can you explain please what is fastboot able and what do you mean to try to unlock again?
thx
Hi
Could you start the phone in fastboot mode?
StupiduserHH said:
Hi
Could you start the phone in fastboot mode?
Click to expand...
Click to collapse
yes the phone is in fastboot mode, and I cant back to normal mode for regular use.
I tried to unlock again like you said it the program said the device is already unlocked.
Have you tried the first option, wipe data?
Don't panick, since you have fastboot mode it's not bricked. Let's start by booting into TWRP.
Download TWRP and put it in the same directory with your FASTBOOT.exe file.
Open a windows dos prompt and get to the same directory as your FASTBOOT file.
Reboot your phone into FASTBOOT mode.
in your DOS prompt type "Fastboot boot yourrecoveryfilename.img" (change the yourrecoveryfilename.img to the TWRP recovery image file you downloaded)
your phone should reboot into TWRP if there wasn't an error. TWRP won't be permanent (if you reboot out of TWRP it won't retain it), but will allow you to flash ROM.
I've only ever flashed all my ROMs through TWRP, never used anything else since i unlocked the phone.
Let me know how this goes.
fastboot .exe file,where can i get it
_katho_ said:
Have you tried the first option, wipe data?
Click to expand...
Click to collapse
wherecan i download this fastboot file
Hello all.
Big screw up, I think. So I've had my MI 8 for a while now, no issues, until today I decided to install official lineage on it. The bootloader was unlocked. I flashed TWRP, but every time I rebooted the phone, it would go back to stock recovery, not TWRP. So here the issue started:
- Via Mi flash tool, I reflashed global MIUI 10 back to stock. I didn't realize I had relocked the bootloader...
- I tried reflashing TWRP without realizing I had relocked the bootloader.
- Thinking that the TWRP flash was done incorrectly again, I simply wanted to go back to stock, and attempted to use the mi flash tool to reflash, once again, the global stock MIUI 10. the flash tool said it was a success. (I still didn't realize I was on a locked bootloader)
- I am now on a bootloop. I can't get past the stock recovery screen, but I can go into fastboot. The recovery screen has a warning that the ROM cannot be used on the phone.
- I tried re unlocking the bootloader with the unlock tool, but because my Mi account credentials are not input on the phone (the phone was wiped clean), I cannot re unlock it.
What can I do? How can I get out of the bootloop, and hopefully re unlock and flash global rom clean again?
dancarriv said:
Hello all.
Big screw up, I think. So I've had my MI 8 for a while now, no issues, until today I decided to install official lineage on it. The bootloader was unlocked. I flashed TWRP, but every time I rebooted the phone, it would go back to stock recovery, not TWRP. So here the issue started:
- Via Mi flash tool, I reflashed global MIUI 10 back to stock. I didn't realize I had relocked the bootloader...
- I tried reflashing TWRP without realizing I had relocked the bootloader.
- Thinking that the TWRP flash was done incorrectly again, I simply wanted to go back to stock, and attempted to use the mi flash tool to reflash, once again, the global stock MIUI 10. the flash tool said it was a success. (I still didn't realize I was on a locked bootloader)
- I am now on a bootloop. I can't get past the stock recovery screen, but I can go into fastboot. The recovery screen has a warning that the ROM cannot be used on the phone.
- I tried re unlocking the bootloader with the unlock tool, but because my Mi account credentials are not input on the phone (the phone was wiped clean), I cannot re unlock it.
What can I do? How can I get out of the bootloop, and hopefully re unlock and flash global rom clean again?
Click to expand...
Click to collapse
Here I made this thread for you : https://forum.xda-developers.com/mi-8/how-to/how-to-install-roms-resolve-issues-t3911611
tsongming said:
Here I made this thread for you : https://forum.xda-developers.com/mi-8/how-to/how-to-install-roms-resolve-issues-t3911611
Click to expand...
Click to collapse
I finally got around fixing this. It turns out my phone was China, with Global ROM. So I did an EDL test point method and paid someone with an authorized account to access my laptop remotely to Flash the latest China ROM. I waited the required period for bootloader unlocking, and it's back alive!
I'm running official lineage 16, and I'm pretty happy with the results. I'm Using it as a daily driver instead of my all stock pixel 2 XL. No issues.
dancarriv said:
I finally got around fixing this. It turns out my phone was China, with Global ROM. So I did an EDL test point method and paid someone with an authorized account to access my laptop remotely to Flash the latest China ROM. I waited the required period for bootloader unlocking, and it's back alive!
I'm running official lineage 16, and I'm pretty happy with the results. I'm Using it as a daily driver instead of my all stock pixel 2 XL. No issues.
Click to expand...
Click to collapse
That's great news! It sucks that you were tricked into thinking your that phone is a global version. But at least you able to get things permanently sorted.
Sent from my Xiaomi MI 8 using XDA Labs
Agimax said:
Don't panick, since you have fastboot mode it's not bricked. Let's start by booting into TWRP.
Download TWRP and put it in the same directory with your FASTBOOT.exe file.
Open a windows dos prompt and get to the same directory as your FASTBOOT file.
Reboot your phone into FASTBOOT mode.
in your DOS prompt type "Fastboot boot yourrecoveryfilename.img" (change the yourrecoveryfilename.img to the TWRP recovery image file you downloaded)
your phone should reboot into TWRP if there wasn't an error. TWRP won't be permanent (if you reboot out of TWRP it won't retain it), but will allow you to flash ROM.
I've only ever flashed all my ROMs through TWRP, never used anything else since i unlocked the phone.
Let me know how this goes.
Click to expand...
Click to collapse
Hey, so I don't want to spam you, but seems like you really know about this and I desperately need some help...
Could you please take a look at my thread? https://forum.xda-developers.com/xi...nt/help-bricked-mi-mix-2s-installing-t4131269
Thank you
Hello, i have a Mi8 global version, unlocked and actually i'm on latest xiaomi.eu dev (9.1.24), but i have some problems with twrp and custom kernels.
I don't know why, but almost every recovery won't boot.
Actually i'm on TWRP 3.2.2-0711 (the only one that works) and managed to flash xiaomi.eu rom as written before.
But every other recovery on the forum won't boot, tried to flash and boot from cmd, only boot from cmd, flash with some tools, flash and with apps from playstore, restart from cmd with vol up, disconnect phone and use keys combination, but same result: only 3.2.2 works.
Every other recovery i try to flash does nothing, it just reboots normally without enter in twrp.
I have similar problem with custom kernel: only francoKernel_r4 boots fine. With every other miui compatible kernel i have bootloop.
I've tried to reflash fastboot rom with XiaomiFlash but still have same results.
Can anyone help me please? I have no more ideas what to do
IronJacob said:
Hello, i have a Mi8 global version, unlocked and actually i'm on latest xiaomi.eu dev (9.1.24), but i have some problems with twrp and custom kernels.
I don't know why, but almost every recovery won't boot.
Actually i'm on TWRP 3.2.2-0711 (the only one that works) and managed to flash xiaomi.eu rom as written before.
But every other recovery on the forum won't boot, tried to flash and boot from cmd, only boot from cmd, flash with some tools, flash and with apps from playstore, restart from cmd with vol up, disconnect phone and use keys combination, but same result: only 3.2.2 works.
Every other recovery i try to flash does nothing, it just reboots normally without enter in twrp.
I have similar problem with custom kernel: only francoKernel_r4 boots fine. With every other miui compatible kernel i have bootloop.
I've tried to reflash fastboot rom with XiaomiFlash but still have same results.
Can anyone help me please? I have no more ideas what to do
Click to expand...
Click to collapse
Did you know this thread?
https://xiaomi.eu/community/threads...neage-compatible-global-rom-compatible.48432/
lolo9393 said:
Did you know this thread?
https://xiaomi.eu/community/threads...neage-compatible-global-rom-compatible.48432/
Click to expand...
Click to collapse
No i did know. Just tried but both twrp don't work.
Btw i'll try to write in that thread too.
Thank you
Fastboot flash the recovery img, then fastboot boot the recovery img.
Then reflash recovery zip file from within twrp you just fastboot booted
https://forum.xda-developers.com/showpost.php?p=78693530&postcount=71
Use TWRP 3.2.3-1208 version from OP in this link
Stoffl_ said:
Fastboot flash the recovery img, then fastboot boot the recovery img.
Then reflash recovery zip file from within twrp you just fastboot booted
https://forum.xda-developers.com/showpost.php?p=78693530&postcount=71
Use TWRP 3.2.3-1208 version from OP in this link
Click to expand...
Click to collapse
As written on eu forum, the only recovery working is the 3.2.2.
Every other recovery, 1208 too give me:
Mi logo (unlocked) - black screen - Mi logo (unlocked) - system. But no recovery.
Tried to flash a custom rom different to xiaomi.eu but got bootloop, same with kernel flashable zips on xda. Only bootlooo...
I really don't know what to do anymore...
Yeah weird, I've literally guided a friend through the process just yesterday with that method.
Zero issues
Hi guys,
I flash Havoc-OS on Mi9T Pro Global PFKMIXM 10.3.1 by TWRP, after reboot do not start system and not enter on TWRP again.
I try this commands on fastboot below.
Code:
adb devices
fastboot flash recovery recovery.img
fastboot boot recovery.img
fastboot reboot recovery
Can anyone give me a help?
Thanks.
fastboot devices
fastboot flash recovery recovery.img
> now just push volume up + power to boot to twrp. (those boot and reboot not working some reason always)
... i tried use same custom rom, but fail also. Then i test LineageOS, that boot normally. I used EUxxx ROM before and after. I just got enought to test custom roms so far.
S3miniFin said:
fastboot devices
fastboot flash recovery recovery.img
> now just push volume up + power to boot to twrp. (those boot and reboot not working some reason always)
... i tried use same custom rom, but fail also. Then i test LineageOS, that boot normally. I used EUxxx ROM before and after. I just got enought to test custom roms so far.
Click to expand...
Click to collapse
Hi friend, mainly thanks for helping.
I tried your suggestion, but it doesn't work.
I restored with Mi Flash Tolls, the only alternative. Now it works well.
You will now try the Flash I Rom and waiting for new updates and then flash any custom rom.
After I want share stuff tools and congratulations.
Have nice guys!
I have the same stuck in fastboot No recovery img, no rom loaded so cant use XiaoMiTool
I booted into TWRP but it didnt ask me for my dycrpt password or somehow i wasnt paying attention and when in with cancel.
I was preparing to flash a new ROM so i wiped all but user data then went to flash my ROM and found i was in the wrong partition
so i rebooted TWRP back into recovery but it booted to fastboot
once i realised i had no recovery i tried flashing again it says it passes but doesnt boot to recovery?
any ideas please.
E:\Downloads\Mobile Phone\ADB>fastboot flash recovery twrp-3.3.1-13-raphael-mauronofrio.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.400s]
writing 'recovery'...
OKAY [ 0.332s]
finished. total time: 1.732s
E:\Downloads\Mobile Phone\ADB>
Click to expand...
Click to collapse
Madaz2 said:
I have the same stuck in fastboot No recovery img, no rom loaded so cant use XiaoMiTool
I booted into TWRP but it didnt ask me for my dycrpt password or somehow i wasnt paying attention and when in with cancel.
I was preparing to flash a new ROM so i wiped all but user data then went to flash my ROM and found i was in the wrong partition
so i rebooted TWRP back into recovery but it booted to fastboot
once i realised i had no recovery i tried flashing again it says it passes but doesnt boot to recovery?
any ideas please.
Click to expand...
Click to collapse
Yes, that's what happened to me.
The only solution I found was to install the new rom via fastboot.
For this you will need to perform the following steps:
1 - Install Mi Flash + drivers (this is boring, if you have Windows 7, it will be easier). In this link you will find some downloads and more details.
2 - Download the Sotck Rom (for fastboot important) from your device, in my case it was PFKMIXM 10.3.1 for Mi9T Pro. You need to extract zip then before.
3 - Flash the new rom via fastboot (approximately 10 minutes).
After that, your device will start with the new rom, then you can flash TWRP again and everything will work. The Magisk installation may cause error 1, but only flash boot.img through TWRP.
Be quick, because if the battery drain, you won't be able to start it in fastboot again.
If you need any links, ask me. I didn't have time to share everything.
Have a nice and good luck!!
Madaz2 said:
I have the same stuck in fastboot No recovery img, no rom loaded so cant use XiaoMiTool
I booted into TWRP but it didnt ask me for my dycrpt password or somehow i wasnt paying attention and when in with cancel.
I was preparing to flash a new ROM so i wiped all but user data then went to flash my ROM and found i was in the wrong partition
so i rebooted TWRP back into recovery but it booted to fastboot
once i realised i had no recovery i tried flashing again it says it passes but doesnt boot to recovery?
any ideas please.
Click to expand...
Click to collapse
To boot to recovery After fastboot flash recovery , you will need also a system...
As you wiped all, you dont have anymore. I made the same mistake when decrypting After unlocking.
Extract system.img from stock fastboot rom and fastboot flash system system.img.
Then again (why not lol) fastboot flash again reco and reboot to recovery with buttons.
If it dont work , miflashtool will recover it ( DONT SELECT CLEAN_LOCK)
rodolphe06 said:
To boot to recovery After fastboot flash recovery , you will need also a system...
As you wiped all, you dont have anymore. I made the same mistake when decrypting After unlocking.
Extract system.img from stock fastboot rom and fastboot flash system system.img.
Then again (why not lol) fastboot flash again reco and reboot to recovery with buttons.
If it dont work , miflashtool will recover it ( DONT SELECT CLEAN_LOCK)
Click to expand...
Click to collapse
Yes, very important.
In Mi Flash, check only "Clean All" dont clean and lock.
Thanks.
thanks, hopefully i didnt break it further as i accidently flashed a global indian ROM when i should have flashed CN
now my only option might be EDL via testpoint, i have a mate who can help i will try and find the right version CN rom tonight and go slower
Madaz2 said:
thanks, hopefully i didnt break it further as i accidently flashed a global indian ROM when i should have flashed CN
now my only option might be EDL via testpoint, i have a mate who can help i will try and find the right version CN rom tonight and go slower
Click to expand...
Click to collapse
Thank you for sharing your experiences.
Too bad you couldn't recover. I hope you can do it again.
Today I had to flash twice, once because I flashed Kernel Quax and couldn't rollback and once for trying Rom Syberian. I hope that in the future we will have a firmware balanced with the customs kernel and roms.
Good luck.
Thanks I dont think it will work
i bought a Deep flash cable to see if i can get it into EDL mode without opening.
Madaz2 said:
Thanks I dont think it will work
i bought a Deep flash cable to see if i can get it into EDL mode without opening.
Click to expand...
Click to collapse
With flash cable or have you open?
Hot-Proton said:
With flash cable or have you open?
Click to expand...
Click to collapse
with flash cable, have to wait for it to arrive now.
if that doesn't work i will have to open and do EDL
Madaz2 said:
with flash cable, have to wait for it to arrive now.
if that doesn't work i will have to open and do EDL
Click to expand...
Click to collapse
I think works, for me it was like this.
Have nice.
is there any reason why flashing twrps via ADB would send z5 pro gt into boot loop into bootloader unable to access the custom recovry or phone needing to do emergency flashing via qfil to stock firmware i did previously use trwps on device to flash files and to sign boot to always boot twrps recovery when trying to access recovery mode . (before bootlooping)
affter bootlooping and fixing via qfil i have been unable to successful install trwps if i do it bootloop to bootloader.
whats the difference between "meta" / "flat" options in qfil
tried locked and unlocked bootloader on both 10.5.304 and 11.1.021 also tried to go straight to recovery mode affter twrps flashing on both firmware same thing lead me bootloop needing to qfill to 10.5.30
another question can i qfil flash to 11.1.021 straight away without having having to qfil 10.5.30 then ota updating to 11.1.021..
thanks in advance
leerh said:
is there any reason why flashing twrps via ADB would send z5 pro gt into boot loop into bootloader unable to access the custom recovry or phone needing to do emergency flashing via qfil to stock firmware i did previously use trwps on device to flash files and to sign boot to always boot twrps recovery when trying to access recovery mode . (before bootlooping)
affter bootlooping and fixing via qfil i have been unable to successful install trwps if i do it bootloop to bootloader.
whats the difference between "meta" / "flat" options in qfil
tried locked and unlocked bootloader on both 10.5.304 and 11.1.021 also tried to go straight to recovery mode affter twrps flashing on both firmware same thing lead me bootloop needing to qfill to 10.5.30
another question can i qfil flash to 11.1.021 straight away without having having to qfil 10.5.30 then ota updating to 11.1.021..
thanks in advance
Click to expand...
Click to collapse
Okay ?
The point is ? I must unlock , install twrp and flashing via ota ?
Flash via qfil done and isn't working
My touchscreen still have thats issue
IamRdw said:
Okay
The point is ? I must unlock , install twrp and flashing via ota ?
Flash via qfil done and isn't working
My touchscreen still have thats issue
Click to expand...
Click to collapse
if you want OTA(over the air) updates you need to lock bootloader. otherwise the updater will say something like phone has been rooted and they cant provide you an update
https://forum.xda-developers.com/z5-pro-gt/how-to/installing-ota-update-11-5-141-via-twrp-t4050027
http://anago.2ch.sc/test/read.cgi/sm...ne/1577014188/ theres a lot of information on this link here are some highlights for me
_____________________________________
>> Crash dump loop of 113 ROM burnt Z5PROGT can be restored by burning CNROM for the time being,
Even if I tried it again, it was useless, so if I look at the syntax at the time of batch execution, it seems that vbmeta.img is not burned.
It says unrecognised option `--disable-verification '.
This time, the boot loader loop only started, and TWRP couldn't start.
This time it may be packed
__________________________________________
>> 117
I'm sorry I want to confirm.
Where did you use the fastboot command?
①fastboot --disable-verification flash vbmeta vbmeta.img
②fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
It is ① that I instructed, but it looks like there are two kinds when I check it on the net.
He seemed to have hit it without knowing it.
Excuse me, can you hit both again?
________________________________________
>> 150
>> I burned 113 ZUI11 version Gro ROM.
I re-added TWRP, but when I started it, it was usable normally, so I could add Magisk,
After that, it only seems to be unavoidable that it only starts up in normal recovery mode.
It is troublesome to do it every time you want to use TWRP, but it can't be helped.
__________________________________________________ _______
this helped Solved
Hello!
So I wanted to flash Evolution X 5.7, because I had problems with the new version, now it's stuck in the boot logo and it also wiped the recovery?! I'm stuck in fastboot. I tried flashing Orangefox using fastboot flash recovery recovery.img it returns success, no error. Then, fastboot reboot recovery. It reboots, but into the system. After that, I did a hard reset into the recovery with the upper vol. button and it got me back into fastboot. Now I'm clueless...
Thanks for reading.
Additional information:
I wiped the data and the system partition before flashing the ROM.
I'm using Artix Linux as my OS (I also have Windows 10 x86_64 but fastboot didn't see my phone, even after installing Qualcomm drivers and android_winusb.inf so I stayed with Linux)
All commands are ran under superuser privileges (with the su command)
Slymi4n said:
Hello!
So I wanted to flash Evolution X 5.7, because I had problems with the new version, now it's stuck in the boot logo and it also wiped the recovery?! I'm stuck in fastboot. I tried flashing Orangefox using fastboot flash recovery recovery.img it returns success, no error. Then, fastboot reboot recovery. It reboots, but into the system. After that, I did a hard reset into the recovery with the upper vol. button and it got me back into fastboot. Now I'm clueless...
Thanks for reading.
Additional information:
I wiped the data and the system partition before flashing the ROM.
I'm using Artix Linux as my OS (I also have Windows 10 x86_64 but fastboot didn't see my phone, even after installing Qualcomm drivers and android_winusb.inf so I stayed with Linux)
All commands are ran under superuser privileges (with the su command)
Click to expand...
Click to collapse
Search/read about Mi Flash and flashing the stock fastboot/tgz firmwares (general method for all Xiaomi phones, hence guides are not specific to this or that phone and can be found elswhere)
This is the only proper way how you should always return to the stock firmware (it means it will also install back the stock recovery, etc)
Hopefully, you didn't hard brick your phone in which case you would need to look for the paid support from someone with an authorized EDL account
zgfg said:
Search/read about Mi Flash and flashing the stock fastboot/tgz firmwares (general method for all Xiaomi phones, hence guides are not specific to this or that phone and can be found elswhere)
This is the only proper way how you should always return to the stock firmware (it means it will also install back the stock recovery, etc)
Hopefully, you didn't hard brick your phone in which case you would need to look for the paid support from someone with an authorized EDL account
Click to expand...
Click to collapse
YES!! IT WORKED!!! Thank you so much