Database Develop

SOFT BRICK using tool Xiaomi Mi A2

Hi guys, i need some help pleeease!
I was with the November security patch on my cell phone, I unlock the bootloader and went to use the friend tool (https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585) to activate the camera2api.
But it gave problem and the cell phone did not turn on, it was locked in the screen of android one.
So I downloaded the patched_boot.img from the version I was in and put it via fastboot. did not work.
Now, my phone is in this situation: I tried to use MiFlash (three versison: 2018528, 2017720 and 20151028) and they fail in the middle of the process, accusing "FAILED (command write failed (Unknown error))".
And: when I try to connect the cell phone normally, it shows the unlocked bootloader warning and goes straight to the fastboot, even without my request. This is strange. Perhaps because the system is damaged by the miflash unfinished
Obs: bootloader are unlocked and i can access twrp
If anyone can help me I will be very grateful and happy

What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...

AsItLies said:
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
Click to expand...
Click to collapse
Hi.
The tool (her topic link is up there) promised to activate camera2api without root my device (allowing OTAs in the future).
I believe she did a "temporary root" with a "temporary" boot.img just to activate the camera2api, and when it rebooted, it would return to normal boot.img without root. I do not know if I could explain it well.
The current issue is that it seems that the system is currently "destroyed or corrupted". Can not I reinstall the entire system through TWRP? Or something like this

Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work

AsItLies said:
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
Click to expand...
Click to collapse
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?

erickxd said:
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
Click to expand...
Click to collapse
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.

AsItLies said:
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
Click to expand...
Click to collapse
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:

erickxd said:
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
Click to expand...
Click to collapse
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.

AsItLies said:
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
Click to expand...
Click to collapse
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me

erickxd said:
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
Click to expand...
Click to collapse
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers

AsItLies said:
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
Click to expand...
Click to collapse
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?

erickxd said:
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
Click to expand...
Click to collapse
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.

Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861

ckpv5 said:
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
Click to expand...
Click to collapse
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:

AsItLies said:
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Click to expand...
Click to collapse
I can access twrp when I flash ''fastboot boot twrp.img" in powershell, so until the next reboot I have access to twrp

erickxd said:
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
Click to expand...
Click to collapse
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.

ckpv5 said:
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
Click to expand...
Click to collapse
Hmm thanks for the answer!
Even when the operation fails after transfer a couple of archives before the system.img??? (on the Miflash)
If my phone was locked, Miflash could transfer these couple of archives before the operation fails?? Or if bootloader is locked, zero files can be passed by Miflash, and the error is apresented at the beginning of the operation?

Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.

prokaryotic cell said:
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
Click to expand...
Click to collapse
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?

erickxd said:
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
Click to expand...
Click to collapse
Before someone can explain that, why don't you answer the question asked .. in fact at least 3 people was asking/telling ...
"Have you successfully unlocked critical partitions?"
Without the proper answer from you, not easy to help.

Question regarding bootloop

Hi all,
First of let me start by saying I have a Mi 9T and I know that it has its own forum, but I didn't find a solution to my problem there, so I thought I'd ask in this forum as well, since the devices look a lot like each other but here are more people.
So my problem is I got stuck in a bootloop which I can't seem to get out of. I can boot into fastboot mode and adb fastboot AND Miflash recognize my device, so I'm able to flash things, but the bootloop still stays.
I started on global rom, and then installed twrp. Then I flashed the latest 9.7.25 ROM from mi-globe for MI 9T. It booted up fine, but my TWRP was removed and I couldn't install it anymore like the first time. For some reason I did a factory reset then. And tried to flash a new ROM by using MiFlash. It said it was succesfull, but it only took 1 second and it didn't automatically boot (it stayed in fastboot mode). I tried again and it said anti-rollback error.
So that didn't work, so I tried flashing boot.img, recovery.img and system,img seperately by using adb fastboot. That worked and it booted normally. I went through the startup configuration like selecting wifi network and gmail,etc. But after trying to set a fingerprint, the screen went completely black but the phone was still on. I could reboot it normally, but when the lockscreen came up or I tried to use fingerprint scanner it went black completeley every time.
I was desperate, so I used 'fastboot erase system -w' in adb fastboot, which is a factory reset apparently. Then I flashed the 3 .img files like I did before, but this time it didn't boot, but went into bootloop.
I also tried 'fastboot boot twrp.img' which also didn't get me into twrp, it just goes to bootloop again.
So to summarize: I CAN get into fastboot and adb fastboot and miflash DO recognize my device, but I can't get out of bootloop no matter what I flash.
Does anyone know a solution for this problem? I would be very thankful.
I also don't understand why flashing or booting TWRP doesn't work, while it worked the first time. I also don't understand why flashing the 3 .img files doesn't work this time, like it used to work the first time.
Btw my anti getvar is 1.

Are you using windows 10? Had same issue with MiFlash and had to use a laptop with earlier version of Windows to get it working

DaveHTC200 said:
Are you using windows 10? Had same issue with MiFlash and had to use a laptop with earlier version of Windows to get it working
Click to expand...
Click to collapse
I do, but I don't have anything else than that. Are you sure that was the problem and not something else?

Rapydax said:
I do, but I don't have anything else than that. Are you sure that was the problem and not something else?
Click to expand...
Click to collapse
I've not had your issue but that was causing the flash tool to just carry out the task in 1 second, which isn't possible

i have the same situation here. did your issue solve?

can't boot into twrp

im really stupid, i was installing twrp, i did a advanced wipe to afterwards install a custom rom, and when my phone was done wiping i accidentally pushed the power button and turned of my phone. now it is stuck in fastboot mode. i tried reinstalling twrp but i can't boot into twrp, it keeps turning on in fastboot mode
thanks in advance

Reflash miui with miflash, be sure yo untick the lock thing onnthe bottom sonyoubdont lock bootloader, then try again.
Sounds like partition is fked

Rikkertbiemans said:
im really stupid, i was installing twrp, i did a advanced wipe to afterwards install a custom rom, and when my phone was done wiping i accidentally pushed the power button and turned of my phone. now it is stuck in fastboot mode. i tried reinstalling twrp but i can't boot into twrp, it keeps turning on in fastboot mode
thanks in advance
Click to expand...
Click to collapse
After flashing TWRP and still in fastboot, hold power and vol+. Keep both held while it reboots, it takes a few seconds. When the Redmi logo appears and the phone vibrates release the power button. Keep holding the vol+ button until it boots into TWRP.

Robbo.5000 said:
After flashing TWRP and still in fastboot, hold power and vol+. Keep both held while it reboots, it takes a few seconds. When the Redmi logo appears and the phone vibrates release the power button. Keep holding the vol+ button until it boots into TWRP.
Click to expand...
Click to collapse
this was the first thing i tried, but it keeps rebooting to fastboot, if i hold it longer it wil just reboot again. i've tried miflash, but miflash can't find a flash all.bat and when i go into explorer i can't find it either.

problem solved, i installed another version of twrp, deleted it and reinstalled the first one. thanks for all answers, it really helped along

Hey glad to hear you solved the issue. What version of TWRP did you end up flashing and what tool did you use to flash it? I'm facing a similar issue.
Thanks

kh805794 said:
Hey glad to hear you solved the issue. What version of TWRP did you end up flashing and what tool did you use to flash it? I'm facing a similar issue.
Thanks
Click to expand...
Click to collapse
I can't answer for OP, but he looks to have abandoned the thread.
What I can recommend from personal experience is that using latest version of TWRP - I think it's 4.3.3 (can't tell you exactly, as I'm writing this without checking my laptop on which I have the TWRP and ROM files) - will resolve all your problems.

Thanks for your reply I actually just managed to get root/TWRP/Magisk to work. A lot of the TWRP recovery images that I encountered just caused the phone to boot loop or get stuck on fastboot mode.
The TWRP that worked for me was twrp-3.3.1-15-raphael-mauronofrio.img
following:
fastboot flash recovery twrp-3.3.1-15-raphael-mauronofrio.img
For reference I have the global Mi 9T Pro

Rikkertbiemans said:
problem solved, i installed another version of twrp, deleted it and reinstalled the first one. thanks for all answers, it really helped along
Click to expand...
Click to collapse
I am also having this issue, after doing the exact same thing you did...
Would you be able to post the download link you got your TWRP version from? And maybe go into a little more detail about the reinstalling order (if that is important)?
Also the "mauronofrio" version didn't work (I have the Mi 9T), are there any other options out there?
Many thanks for any responses

camelCaseOnly said:
I am also having this issue, after doing the exact same thing you did...
Would you be able to post the download link you got your TWRP version from? And maybe go into a little more detail about the reinstalling order (if that is important)?
Also the "mauronofrio" version didn't work (I have the Mi 9T), are there any other options out there?
Many thanks for any responses
Click to expand...
Click to collapse
Did you ever get this solved? I'm in a similar situation after what I thought was a normal ROM flashing.
EDIT: Nevermind. Got it fixed using MiFlash.

theCroh said:
Did you ever get this solved? I'm in a similar situation after what I thought was a normal ROM flashing.
EDIT: Nevermind. Got it fixed using MiFlash.
Click to expand...
Click to collapse
Hey sorry didn't see your reply... I haven't had time in the last month to look at it so I'm still stuck. How did you fix it using MiFlash? Did you make it force load TWRP onto the phone or something?
I think there is definitely something wrong with the partition, as when I plug it into the computer it no longer comes up in "my computer" - although I do have the MIUI recovery working again.
Cheers

Rikkertbiemans said:
im really stupid, i was installing twrp, i did a advanced wipe to afterwards install a custom rom, and when my phone was done wiping i accidentally pushed the power button and turned of my phone. now it is stuck in fastboot mode. i tried reinstalling twrp but i can't boot into twrp, it keeps turning on in fastboot mode
thanks in advance
Click to expand...
Click to collapse
Flash images manually mr

camelCaseOnly said:
Hey sorry didn't see your reply... I haven't had time in the last month to look at it so I'm still stuck. How did you fix it using MiFlash? Did you make it force load TWRP onto the phone or something?
I think there is definitely something wrong with the partition, as when I plug it into the computer it no longer comes up in "my computer" - although I do have the MIUI recovery working again.
Cheers
Click to expand...
Click to collapse
I just flashed a full fastboot MIUI ROM in fastboot using the MiFlash portable tool. No need to do anything in recovery.
Edit: You can find fastboot ROMs from the OP of this thread https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647/ (labeled as ...fastboot)

EpickBroVlad said:
Flash images manually mr
Click to expand...
Click to collapse
Where can I find the right commands for flashing

theCroh said:
I just flashed a full fastboot MIUI ROM in fastboot using the MiFlash portable tool. No need to do anything in recovery.
Edit: You can find fastboot ROMs from the OP of this thread https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647/ (labeled as ...fastboot)
Click to expand...
Click to collapse
I'm still not able to get TWRP working... I think all of my problems will be solved as soon as I can get into it, but each time I load the recovery image on (using command prompt) it says it completes, but when I try to reboot it into recovery mode it never works (if I use command prompt to reboot into recovery it just shuts down but if I hold the button combination it either reboots back into fastboot or the original MIUI recovery mode - and yes, I am using the right button combinations).
I've tried every version of TWRP I could find, so I'm certain its not a problem with the recovery image itself... Have you or anyone else had this happen before? It's so infuriating that it just doesn't work, but I don't know why...
BTW the commands I'm using are
Code:
fastboot flash recovery "recovery.img"
(which works) and then
Code:
fastboot boot "recovery.img"
(which gives 2 OKs, but the phone just turns off).
(this all after setting the directory to my adb folder)

camelCaseOnly said:
I'm still not able to get TWRP working... I think all of my problems will be solved as soon as I can get into it, but each time I load the recovery image on (using command prompt) it says it completes, but when I try to reboot it into recovery mode it never works (if I use command prompt to reboot into recovery it just shuts down but if I hold the button combination it either reboots back into fastboot or the original MIUI recovery mode - and yes, I am using the right button combinations).
I've tried every version of TWRP I could find, so I'm certain its not a problem with the recovery image itself... Have you or anyone else had this happen before? It's so infuriating that it just doesn't work, but I don't know why...
BTW the commands I'm using are
Code:
fastboot flash recovery "recovery.img"
(which works) and then
Code:
fastboot boot "recovery.img"
(which gives 2 OKs, but the phone just turns off).
(this all after setting the directory to my adb folder)
Click to expand...
Click to collapse
This worked
https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
now shall I keep read only or allow modifications?

claudioita said:
This worked
https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
now shall I keep read only or allow modifications?
Click to expand...
Click to collapse
Unfortunately I wasn't able to access that link for some reason, but I did FINALLY manage to get it to work using another version from this thread; specifically the 4PDA 3.3.1-3 build and instructions referenced in the original post (I was using MIUI 11.0.1.0 at the time).

solution
you need the version for youre board if you open aida64 on youre phone is says davinci on my xiaomy mi 9t so download the twrp for davinci and it works i had the same problem too stuck in fast boot , im new to this this is my frist time im trying to install a new beta for miui

camelCaseOnly said:
Unfortunately I wasn't able to access that link for some reason, but I did FINALLY manage to get it to work using another version from this thread; specifically the 4PDA 3.3.1-3 build and instructions referenced in the original post (I was using MIUI 11.0.1.0 at the time).
Click to expand...
Click to collapse
Yy

help!
my honor 9 lite bootloader is unlocked and i have installed an unknown kernel and now when i want boot into twrp it will boot into stock recovery and when i flash twrp and boot it will boot into stock
i tried all of twrp versions :|
wtf should i do?
plz help me

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

Mi 11T not booting (no help needed anymore)

A little Background: I installed a module that broke my g-apps, so I tried to update my rom from 14.0.1.0 to 14.0.2.0 (EEA).​​The problem: I flashed the fastboot rom through Mi Flash. Now my phone is stuck in a loading animation when booting (I can access adb commands, but still can't access my files).​​I tried everything I could think of, but it just won't boot... I didn't make a backup and I don't want to lose my files if there's any way to avoid that.​​A very weird thing though: It gets really close to booting: it even applies reading mode and connects to adb, but the loading screen doesn't disappear.​when I do "adb reboot" the system clock flashes for a second. When I touch the fingerprint sensor it vibrates.​​THERE IS NO TWRP FOR MY DEVICE​​Thank you so much for your help!​​

Did you try safe boot?

surajpai524 said:
Did you try safe boot?
Click to expand...
Click to collapse
Yes, unfortunately it didn't help

The flashing script has a line saying "fastboot %* erase expdb".
There is no image named expdb in the images folder.
Does this mean this partition was uninstalled but not installed afterwards?
Could this be the issue?
Where do I get an expdb.img from so I can flash it again?

Try posting this in MI11T forums instead of Magisk.

I accepted my faith and did a full reset.
My files are gone now, but at least my phone is alive.
Thanks for helping!
surajpai524 said:
Did you try safe boot?
Click to expand...
Click to collapse