Database Develop

xiaomi mi3 hard brick cold dead?

Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?

Shamoth said:
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Click to expand...
Click to collapse
Try mi flash tool

Main problem is that I have tried all 3 miflash I could found 2.11.6 20131108 20140509 and none of them recognizes device and I can't even initiate flashing process ;/

it sounds like a driver issue. just download all the drivers you can find for your phone.

Shamoth said:
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Click to expand...
Click to collapse
Same problem here, waiting for someone give the solution

if the device is not getting detected in any of the mi flash tools,i feel its a clear sign of driver issues ,

ZenR2 said:
if the device is not getting detected in any of the mi flash tools,i feel its a clear sign of driver issues ,
Click to expand...
Click to collapse
r u following correct procedure for using MI flash tool ?
is ur Phone able to boot to FLash mode ( turn phone off > Press volume + Key then Press Power on - it will show flash mode )
Now Open MI Flash tool > Press Refesh > it will show phone now ( a number will b shown instead of name Xiamo Mi3)
Now Extract Fastboot rom to C Drive ( it should look like this C:\ROM (Location should not cointain space)
Now click Browse > advance > select C:\ROM\Folder\ select bat file

Its not drivers issue since its get detected as QUALCOMM HS-USB QDLoader 9008 or QUALCOMM HS-USB Diagnostic 9006 depending of its state.
In QDLoader it is recognized by miflash as COM20 device and I can upload by miflash or qpst boot image, then it switches to diagnostic that is recognized by some sort of string and I can upload/proceed with rest of rom flashing that includes creating partitions and writing data to them.
Main problem is that when its successfully flashed it is still cold dark, while PC can see it and all partitions like 28 of them...
And I think its related to the fact that qpst reports phone as in download mode.
Any idea how to exit that mode, like in Mi2 that was forced to enter "service" by shortening some pins to put it download mode to flash cold dead ones?

agdag said:
magdag from en.miui.com forum seems to be able to hekp ..or try [email protected] , jason provide paid service
Click to expand...
Click to collapse
You were already looking at it
Kinda wasted a lot of Mine and Yours time and some of my money
If You got any other ideas since that time how to resurrect it just let me know.

Any solution?
Is there any solution to this problem? My phone has been cold brick for 3 days now. Doesnt boot up or charge up. Detected on connecting to PC with a sound, but Shows as Com 10 or 20 on Miflash and thus cannot be flashed.
Cannot boot into fastboot as well.
Anyone anything?

androidy88 said:
Is there any solution to this problem? My phone has been cold brick for 3 days now. Doesnt boot up or charge up. Detected on connecting to PC with a sound, but Shows as Com 10 or 20 on Miflash and thus cannot be flashed.
Cannot boot into fastboot as well.
Anyone anything?
Click to expand...
Click to collapse
You can check the steps I took for recovering from a similar problem here: http://en.miui.com/forum.php?mod=viewthread&tid=22811
If you have any other questions, tag me on your reply and i'll try my best to help.

Xperia SP Hard Bricked , Possible Solution ?

HI everyone
i have hard bricked my xperia sp , my xperia sp is c5302 i have falshed c5303 ftf its hard bricked
Led not working when put in charge and when connected with pc
power button not working
hard reset button not working (back on the phone)
display not working
fastboot and flashmode not working
but when connected with pc qhsusb_dload driver instalation started and windows cant find drivers , i updated the drivers manually
and treid testoint method but its not working
log:
20-03-2015 15:57:45 will use DLOAD protocol ...
20-03-2015 15:57:45 0808010600900000
20-03-2015 15:57:45 0D0F50424C5F446C6F6164564552322E30
20-03-2015 15:57:45 162001000100
20-03-2015 15:57:45 17004001000100E1108800
20-03-2015 15:57:45 1801000F43240892D02F0DC96313C81351B40FD5029ED98FF9EC7074DDAE8B05CDC8E1
20-03-2015 15:57:46 PHONE NOT SUPPORTED IN THIS MODE
20-03-2015 15:57:46 Elapsed:19 secs.
but i havent opened the device and used metal with testpoint
because there is no successfull report on working on xperia sp in the forum
Is there any one sucessfully unbricked using test point method or any other method to unbrick
And im willing to donate for the solution
regards
david

Hi,
First of all : There is no hard brick for Xperia SP. Either you have a soft brick or your phone has a hardware default.
Now there are two common cases of soft brick from which you can recover:
The first is some kind of early bootloop. It seems like the phone is off but your phone is bootlooping. This happens if you flash a non working kernel (and can probably also happen with a corrupt kernel).
To recover from this: plug your phone to pc, press volume up and without releasing it, press the reset button on the back. You should keep all the three (volume up, usb and reset) until you see the green led. This mean you are in flashmod and from then just follow the guides !
The second kind generally comes from the first one. It's an empty battery with non working software. It happens if for example you have a bootloop which drains your battery totally.
To recover from this: plug your phone to wall charger (not on computer) and wait for some hours (you will probably need at least 3. Maybe even 5-6 hours) and then try the solution for the first kind of brick.
I don't think I have seen any harder brick than these two and I believe hard brick cannot happen unless you mess with the bootloader (like editing it).
The problem could also be a hardware default. In this case, just send your phone for repair if you still have warranty or buy a new one.

ty
thank you pec0ra for the reply
i can confirm that its not soft brick (bootloop , sony logo,display on) and there is no hardware defect , bootloader is unlocked and i havent played with bootloaders ,never relocked or other things
tried by connecting hard reset button + volume down +volume up to enter flashmode but no it isnt
what happenedd is i have flashed wrong ftf (charge level 50+ percentage) and falshtool succesfully flashed c5303 ftf and removed usb and tried to turn on but power isnt responding phone doesnt turned on and back hardreset button also failed to reboot the phone , when i coonected with pc it tried to install qualcomm drivers (qhsusb_dload)
i dont know what will happen after flashing wrong ftf technically
can you say about that little more that would be helpfull
thank you

uh oh said:
thank you pec0ra for the reply
i can confirm that its not soft brick (bootloop , sony logo,display on) and there is no hardware defect , bootloader is unlocked and i havent played with bootloaders ,never relocked or other things
tried by connecting hard reset button + volume down +volume up to enter flashmode but no it isnt
what happenedd is i have flashed wrong ftf (charge level 50+ percentage) and falshtool succesfully flashed c5303 ftf and removed usb and tried to turn on but power isnt responding phone doesnt turned on and back hardreset button also failed to reboot the phone , when i coonected with pc it tried to install qualcomm drivers (qhsusb_dload)
i dont know what will happen after flashing wrong ftf technically
can you say about that little more that would be helpfull
thank you
Click to expand...
Click to collapse
I'm not sure about this, but I think flashing a c5305 firmware on a c5302 shouldn't brick your phone but only your wireless connectivity.
The bootloop I talked about is a bootloop that happens before the sony logo displays. Booting android happens approximately so :
Reset signal sent to cpu
Load kernel (I'm not sure but this should be done by some hardware procedures and the bootloader) and initialize devices
Load ramdisk and display splash logo (sony)
Launch android and display boot animation
If you have a bootloop at 4 (after the boot animation has appeared), it means your kernel is working but your rom has a problem (for example it is not compatible with the kernel)
If you have a bootloop at 3 (after the splash logo has appeared), it means you have a problem in the ramdisk
If your CPU is totally broken, you might never arrive at 2
Now the interesting part is if your kernel is broken (for example not compatible with your hardware or there is an error in the code or the binaries are corrupted). If an error happens in the kernel, an interrupt signal will be sent to your CPU and you will start again at 1. This will lead in a loop in 1 and 2. Your screen will stay off but your CPU will run at max speed doing the early initialization again and again. This often drains the battery before you find it out.
This kind of hidden bootloop only happened to me when I modified a kernel and made some errors, but I can easily imagine that this can also happen with something going wrong in firmware flashing or corrupted firmware.
I have seen this kind of problem a few times, mainly on my phone, but I've also seen other users report similar problem. My guess is your phone only has this problem and I recommend you to let it charge a few hours and then try to connect it in flashmod.
If the problem isn't the one I mentioned (and this is of course possible), then I can unfortunately not help you further and you should wait for others to reply.
Good luck !

uh oh said:
HI everyone
i have hard bricked my xperia sp , my xperia sp is c5302 i have falshed c5303 ftf its hard bricked
Led not working when put in charge and when connected with pc
power button not working
hard reset button not working (back on the phone)
display not working
fastboot and flashmode not working
but when connected with pc qhsusb_dload driver instalation started and windows cant find drivers , i updated the drivers manually
and treid testoint method but its not working
log:
20-03-2015 15:57:45 will use DLOAD protocol ...
20-03-2015 15:57:45 0808010600900000
20-03-2015 15:57:45 0D0F50424C5F446C6F6164564552322E30
20-03-2015 15:57:45 162001000100
20-03-2015 15:57:45 17004001000100E1108800
20-03-2015 15:57:45 1801000F43240892D02F0DC96313C81351B40FD5029ED98FF9EC7074DDAE8B05CDC8E1
20-03-2015 15:57:46 PHONE NOT SUPPORTED IN THIS MODE
20-03-2015 15:57:46 Elapsed:19 secs.
but i havent opened the device and used metal with testpoint
because there is no successfull report on working on xperia sp in the forum
Is there any one sucessfully unbricked using test point method or any other method to unbrick
And im willing to donate for the solution
regards
david
Click to expand...
Click to collapse
Did you select s1 Emergency mode? Do you have s1boot version wich support SP? Which driver did you use? You have to use Gordons Gate drivers.

pec0ra said:
I'm not sure about this, but I think flashing a c5305 firmware on a c5302 shouldn't brick your phone but only your wireless connectivity.
The bootloop I talked about is a bootloop that happens before the sony logo displays. Booting android happens approximately so :
Reset signal sent to cpu
Load kernel (I'm not sure but this should be done by some hardware procedures and the bootloader) and initialize devices
Load ramdisk and display splash logo (sony)
Launch android and display boot animation
If you have a bootloop at 4 (after the boot animation has appeared), it means your kernel is working but your rom has a problem (for example it is not compatible with the kernel)
If you have a bootloop at 3 (after the splash logo has appeared), it means you have a problem in the ramdisk
If your CPU is totally broken, you might never arrive at 2
Now the interesting part is if your kernel is broken (for example not compatible with your hardware or there is an error in the code or the binaries are corrupted). If an error happens in the kernel, an interrupt signal will be sent to your CPU and you will start again at 1. This will lead in a loop in 1 and 2. Your screen will stay off but your CPU will run at max speed doing the early initialization again and again. This often drains the battery before you find it out.
This kind of hidden bootloop only happened to me when I modified a kernel and made some errors, but I can easily imagine that this can also happen with something going wrong in firmware flashing or corrupted firmware.
I have seen this kind of problem a few times, mainly on my phone, but I've also seen other users report similar problem. My guess is your phone only has this problem and I recommend you to let it charge a few hours and then try to connect it in flashmod.
If the problem isn't the one I mentioned (and this is of course possible), then I can unfortunately not help you further and you should wait for others to reply.
Good luck !
Click to expand...
Click to collapse
pec0ra after charging my phone for 6 hours (leds off all time) and connected to the pc red led glows in device and windows started searching for drivers and device named as unrecognized and after some time device disconnected from pc
and i treid to boot in flashmode volume down + power , power +volumedown+hard reset button but the led is red and turns off after 3 or 4 sec
i cant boot to flashmode or fastboot ,
2 : kernel is broken or not there to load or wrong kernel , and what might be the cause for not booting up in flashmode or fastboot is that kernel problem.
thank you pec0ra

smogf said:
Did you select s1 Emergency mode? Do you have s1boot version wich support SP? Which driver did you use? You have to use Gordons Gate drivers.
Click to expand...
Click to collapse
s1 emergency mode: yes
s1boot version for sp : yes from the other forum
gordon gate drivers :yes
thank you smogf

uh oh said:
pec0ra after charging my phone for 6 hours (leds off all time) and connected to the pc red led glows in device and windows started searching for drivers and device named as unrecognized and after some time device disconnected from pc
and i treid to boot in flashmode volume down + power , power +volumedown+hard reset button but the led is red and turns off after 3 or 4 sec
i cant boot to flashmode or fastboot ,
2 : kernel is broken or not there to load or wrong kernel , and what might be the cause for not booting up in flashmode or fastboot is that kernel problem.
thank you pec0ra
Click to expand...
Click to collapse
Flashmode is independent from the kernel.
The right combo is volume up + hard reset. Keep them at least 10-15 seconds while connected to usb.

pec0ra said:
Flashmode is independent from the kernel.
The right combo is volume up + hard reset. Keep them at least 10-15 seconds while connected to usb.
Click to expand...
Click to collapse
volume up+hard reset : not working
volume down +hard reset : not working
volume up/down+power , volume up/down + hard reset: red led for 3 or 4 sec then turned off device disconnected
when ever i connect with power button + other button red led for 3 or 4 sec is that when power button is pressed the device try turn on ?
and when connecting with wall charger with pressing power button red led blink (a flash) is that device is in low battery
and one big question should i drain the battery completly and tried to connect in flashmode or charge the device fully overnight and try to boot in flashtool
really thank you pec0ra for the patience , help

try installing another kernel and flash any rom?

Marília de Oliveira said:
try installing another kernel and flash any rom?
Click to expand...
Click to collapse
cant boot to flashmode or fastboot
@noahvt can you help with this thank you

uh oh said:
cant boot to flashmode or fastboot
@NovaHt can you help with this thank you
Click to expand...
Click to collapse
Try to install the drives in FlashTool

Marília de Oliveira said:
Try to install the drives in FlashTool
Click to expand...
Click to collapse
installed drivers from flastool/drivers
commom flashmode
common fastboot
and viskan board

uh oh said:
volume up+hard reset : not working
volume down +hard reset : not working
volume up/down+power , volume up/down + hard reset: red led for 3 or 4 sec then turned off device disconnected
when ever i connect with power button + other button red led for 3 or 4 sec is that when power button is pressed the device try turn on ?
and when connecting with wall charger with pressing power button red led blink (a flash) is that device is in low battery
and one big question should i drain the battery completly and tried to connect in flashmode or charge the device fully overnight and try to boot in flashtool
really thank you pec0ra for the patience , help
Click to expand...
Click to collapse
I'd say the red blink is a good sign but unfortunately I have no further knowledge to help you. If I find the time I'll make some tests.
In the mean time, you should try your computer with another phone to see if usb works and/or try with another computer.

pec0ra said:
I'd say the red blink is a good sign but unfortunately I have no further knowledge to help you. If I find the time I'll make some tests.
In the mean time, you should try your computer with another phone to see if usb works and/or try with another computer.
Click to expand...
Click to collapse
thank you pec0ra hope it would be fixed , and one last ques where i can download zeus flash drivers
:highfive:

uh oh said:
thank you pec0ra hope it would be fixed , and one last ques where i can download zeus flash drivers
:highfive:
Click to expand...
Click to collapse
Zeus Flash Driver is in Gordon Gates package. But U have to select this driver manually. Default is SEMC Flash Device.

smogf said:
Zeus Flash Driver is in Gordon Gates package. But U have to select this driver manually. Default is SEMC Flash Device.
Click to expand...
Click to collapse
after bricking phone is not recognised as semc flash device, now my device is connecting only in qhsusb_dload
and in drivers its qhsusb_dload qualcom hs-usb QDloader 9008(com13)
thank you for clearing zeus flash

uh oh said:
after bricking phone is not recognised as semc flash device, now my device is connecting only in qhsusb_dload
and in drivers its qhsusb_dload qualcom hs-usb QDloader 9008(com13)
thank you for clearing zeus flash
Click to expand...
Click to collapse
Of course is recognized as qhsusb_dload. Thats why U have to install Gordons Gate drivers.

smogf said:
Of course is recognized as qhsusb_dload. Thats why U have to install Gordons Gate drivers.
Click to expand...
Click to collapse
sorry for wrong info, device connected as zeus flash device(with power button pressed , normally device is not recognized) , disconnects after a minute

uh oh said:
sorry for wrong info, device connected as zeus flash device(with power button pressed , normally device is not recognized) , disconnects after a minute
Click to expand...
Click to collapse
Do you have any LED light? Below example from my hardbricked Xperia S.
When I've connected Xperia S to computer, red light show up. After a little while LED turn off, and device is recognized as qhsusb_dload (SEMC Flash Device, Zeus flash device, or which driver I have installed or I havent.) No matter. The thing is, that my phone is recognize after RED led turn off. Dont know how about SP, but I suppose that can be similar.
In the end. Launch s1boot, select sin_file_set wich you have to flash (theres a Thread with proper file to recover boot) click on Testpoint Ready and connect the phone to usb. I suppose not, but can work without disassembling device and attaching testpoint. You have to try.

Is there anything I can do? Brick help

My Xiaomi mi5 does not turn on.
No lights, fastboot is not accessible, resetting it does not do anything.
Basically for any combination of buttons that I press, nothing happens and the screen stays black - it is completely dead.
However, when I plug it into my pc, the devices shows up as qualcomm hs-usb qdloader 9008 (COM3) which is the only sign of life from the phone.
What I want to know is if it is possible for me to unbrick the phone from this situation. I understand that I need to get into fastboot in order to flash the ROM, but is there a way to get to fastboot using my pc? Or even turn the phone on with commands? At the moment ADB and Fastboot does not recognise my phone, is there a way to make it detect it from the state it is in?
Thanks

sivd said:
My Xiaomi mi5 does not turn on.
No lights, fastboot is not accessible, resetting it does not do anything.
Basically for any combination of buttons that I press, nothing happens and the screen stays black - it is completely dead.
However, when I plug it into my pc, the devices shows up as qualcomm hs-usb qdloader 9008 (COM3) which is the only sign of life from the phone.
What I want to know is if it is possible for me to unbrick the phone from this situation. I understand that I need to get into fastboot in order to flash the ROM, but is there a way to get to fastboot using my pc? Or even turn the phone on with commands? At the moment ADB and Fastboot does not recognise my phone, is there a way to make it detect it from the state it is in?
Thanks
Click to expand...
Click to collapse
Do you have all the necessary driver installed? I think yes and that is why you are seeing in (COM3) port. You can do one thing, Unplug the phone from PC and Press and Hold Vol Down (-) and plug in again. If not works then you can also Press and HOLD Vol Down and Press and HOLD Power button until you see Fast boot menu. If don't work then try the same thing with Vol UP button. Then you suppose to see a MI phone logo with a USB cable.

"qualcomm hs-usb qdloader 9008" Is a signal of Hard Brick for QCOM devices (Like for LG G2);
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
As you can see here, for fix it you need all partition files, all system files, and a programm
But i dont know if it will works also on SD820, you might need all files for Mi5
Just a question: How did you bricked your phone?
EDIT:
I had an idea: maybe inside fastboot rom you can find all files you need, it might be worth a try, at least you can send it to your shop where you bought it

sivd said:
However, when I plug it into my pc, the devices shows up as qualcomm hs-usb qdloader 9008 (COM3) which is the only sign of life from the phone.
What I want to know is if it is possible for me to unbrick the phone from this situation. I understand that I need to get into fas,tboot in order to flash the ROM
Click to expand...
Click to collapse
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here: https://www.androidfilehost.com/?fid=24521665358595574
3: download the latest dev rom from here: http://update.miui.com/updates/v1/fullromdownload.php?d=gemini&b=X&r=cn&n=
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.

adwinp said:
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here: https://www.androidfilehost.com/?fid=24521665358595574
3: download the latest dev rom from here: http://update.miui.com/updates/v1/fullromdownload.php?d=gemini&b=X&r=cn&n=
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
Click to expand...
Click to collapse
I also had the same issue with black screen and no responses from vol. & power buttons. But when I notice that in device manger it showed the qcom driver, then I new that there was hope to recover the phone. I can confirm that this will unbrick your phone. I MiFlash'd the China Rom (non-dev), unlocked the bootloader, MiFlash'd MiFlash_xiaomi.eu_gemini_V7.2.13.0.MAACNDB_6.0 rom, sideload lastest stable EU rom, TRWP and SuperSU.

adwinp said:
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here:
3: download the latest dev rom from here:
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
Click to expand...
Click to collapse
Thank you so much, this has worked perfectly and saved me a lot of money! I really appreciate your help, thank you again!

sivd said:
Thank you so much, this has worked perfectly and saved me a lot of money! I really appreciate your help, thank you again!
Click to expand...
Click to collapse
Glad you could salvage your device.
Now remember - from great flashing power comes great responsibility ;]

adwinp said:
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here: https://www.androidfilehost.com/?fid=24521665358595574
3: download the latest dev rom from here: http://update.miui.com/updates/v1/fullromdownload.php?d=gemini&b=X&r=cn&n=
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
Click to expand...
Click to collapse
Thanks for the guide, 1 q tho: what to do when i get the "missed hello packets, try to recover" message?, wait or restart the process?
Ok, solved by disabling driver sign (press F8 during boot)

Hello , i got the same problem as described at this topic and here is my problems :
I can't turn on my phone and i can't put it in fastboot mode ( tryed a lot of buttons combinations)
But when i plug it into my pc - it recognizes as Android
I have tryed to install drivers but windows shows mistake and can't install that
When my device connected to pc and i press volume + and power buttons - in few minutes system(WIN 10) recognizes it as ADB interface(can't install drivers too) and i have acess to mi5 internal storage ( i can download photos and so on )
But mi flash doesn't see phone in any mode and i feel that my device is still alive and i can recover it but don't know how....
I will be grateful for any help !

Isteran said:
Hello , i got the same problem as described at this topic and here is my problems :
I can't turn on my phone and i can't put it in fastboot mode ( tryed a lot of buttons combinations)
But when i plug it into my pc - it recognizes as Android
I have tryed to install drivers but windows shows mistake and can't install that
When my device connected to pc and i press volume + and power buttons - in few minutes system(WIN 10) recognizes it as ADB interface(can't install drivers too) and i have acess to mi5 internal storage ( i can download photos and so on )
But mi flash doesn't see phone in any mode and i feel that my device is still alive and i can recover it but don't know how....
I will be grateful for any help !
Click to expand...
Click to collapse
If you can see it in adb, you might be able to see it in fastboot.
Try go in to fastboot (even though you can't see it on screen.)
And try fastboot oem device-info see if you can get anything. Then we go from there.

DrBubblewrap said:
If you can see it in adb, you might be able to see it in fastboot.
Try go in to fastboot (even though you can't see it on screen.)
And try fastboot oem device-info see if you can get anything. Then we go from there.
Click to expand...
Click to collapse
tryed a lot of time to go to fastboot , but nothing happened...

same issue
I've been having the same problem with my MI5, 128gb running MIUI8 6.6.23CN, unlocked bootloader
It started when I did an OTA from 6.6.16, then OTA failed, I tried again this time it downloaded full rom and went into my twrp but installation started automatically. Then it rebooted but the system stayed in black screen. I forced-rebooted it, then everything was fine and I was on 6.6.23. I was using the phone normally for a few hours, then around 6hr later after I upgraded, I took phone out of my bag and it was bricked. I tried everything, no fastboot, no adb, no recovery, no led, nothing on screen. MiFlash reconizes (cuz of the 9008 status) but flash fails. I event opened it up, disconnected the 3 cables from the battery and hold onto power buttons for few seconds to try to drain whatever power it has left in system. Reconnected battery but no change.
I gave up, put phone back in case and was going to ask friend to take it back to send to china for repair the next day, but then I too it out an hour before I go meet my friend and suddenly, phone led flashed red and I see on screen out-of-battery icon. I plugged it in to charge then LED flickered quickly in red for a bit then turn solid red, then turned orange. I let it charged for 10min or so, and pressed power+Vol_Down for few seconds. Lo and behold, I got the bunny on screen and went into fastboot. I was able to re-flash 6.6.23 and phone was good to go again. (but why did removing battery cables do the same thing? Maybe I didn’t leave it disconnected long enough?)
Good story until this part… then 2 days later, I wanted to test MI Talk with friend, I click on it, and phone froze. Both touch sensor light stayed on. I waited about 15 second and forced reboot. Phone vibrates once and then went into hard brick again. Exactly same situation, nothing works.
Now I am waitng for phone to discharge by itself. God knows how many days it will take. It was 96% charged. (1st time I had about 45% and too a day to discharge)
Only if I can get back into fastboot......

tkrave said:
I've been having the same problem with my MI5, 128gb running MIUI8 6.6.23CN, unlocked bootloader
It started when I did an OTA from 6.6.16, then OTA failed, I tried again this time it downloaded full rom and went into my twrp but installation started automatically. Then it rebooted but the system stayed in black screen. I forced-rebooted it, then everything was fine and I was on 6.6.23. I was using the phone normally for a few hours, then around 6hr later after I upgraded, I took phone out of my bag and it was bricked. I tried everything, no fastboot, no adb, no recovery, no led, nothing on screen. MiFlash reconizes (cuz of the 9008 status) but flash fails. I event opened it up, disconnected the 3 cables from the battery and hold onto power buttons for few seconds to try to drain whatever power it has left in system. Reconnected battery but no change.
I gave up, put phone back in case and was going to ask friend to take it back to send to china for repair the next day, but then I too it out an hour before I go meet my friend and suddenly, phone led flashed red and I see on screen out-of-battery icon. I plugged it in to charge then LED flickered quickly in red for a bit then turn solid red, then turned orange. I let it charged for 10min or so, and pressed power+Vol_Down for few seconds. Lo and behold, I got the bunny on screen and went into fastboot. I was able to re-flash 6.6.23 and phone was good to go again. (but why did removing battery cables do the same thing? Maybe I didn’t leave it disconnected long enough?)
Good story until this part… then 2 days later, I wanted to test MI Talk with friend, I click on it, and phone froze. Both touch sensor light stayed on. I waited about 15 second and forced reboot. Phone vibrates once and then went into hard brick again. Exactly same situation, nothing works.
Now I am waitng for phone to discharge by itself. God knows how many days it will take. It was 96% charged. (1st time I had about 45% and too a day to discharge)
Only if I can get back into fastboot......
Click to expand...
Click to collapse
You don't have to go into fastboot to use miflash if you have stock recovery
Sent from my MI 5 using Tapatalk

vf1 said:
You don't have to go into fastboot to use miflash if you have stock recovery
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
how do you flash stock recovery if you dont need to go into fastboot? now I am unable to go into recovery or fastboot as the phone does not boot at all. connecting it to PC reconizes the phone as the infamous "Qualcomm HS-USB QDLoader 9008" device.
Its been 4 days and the damn battery hasnt run out yet as I can still plug into pc and get qualcom 9008 to come up. I think I am going to send to china to get it fixed properly if I still cannot get the red flicker of low battery power to come up by tomorrow.

It has happened to me 3-4 times already. It didnt want to boot. No signs of life either. I even sent a message to the shop for sending it back..the only thing that was telling me it wasn't completely dead, was the qualcomm driver ,while on USB connection with the PC, which you are referring to as well
Here is what you could try doing. Try pressing the power button for about 30 seconds at first. If it does not boot, try bending the phone real gently back and forth (don't break it!!). Preferably, hit it gently with your palm while holding it in your other hand.( -- I know it might sound weird --) I noticed that it's shutting down while i have it in my pocket and doing some work which squeezes the phone a bit against my leg.
I came to the conclusion that some connection must become loose when some pressure is being applied to it.. Unfortunately it has to be a design flaw of the phone. Nothing random with yours or mine , in my opinion. // I have a case and tempered glass installed as well since the first minute I got it in my hands..
Sent from my MI 5 using XDA-Developers mobile app

Thanks for the tips Takkaros. I tried what you said but nothing changed (though I was a bit scared to bend it too hard). 1st time it happened to me, I had around 40-50% battery and somehow battery completely drained 24hr later so I got the red blinking low of battery light and was able to charge the phone up and go back into fastboot, which solved everything. this time it happened when I had 96% battery(which I knew cuz I was using the phone, then clicked MI Talk and phone froze, then bricked). I wish there is a way for me to force a battery drain without opening it up. I did opened it up once(on the 1st brick) and disconnected the 3 battery cables, but it was still in brick state when I put everything back.
The qualcomm 9008 driver detection was also my concern about sending back the phone. Chances are by the time my phone reaches the repair shop, battery is completely dead and they simply charge the battery then flash a stable rom and send it back to me without changing out the motherboard or whatever. Which in such case it will be faster for me to just wait a week or two and do myself, instead of shipping it to china and wasting shipping cost and probably will take 4-6 weeks.

I am not sure whats wrong with this phone. Sometimes it turns off while i have in on charge at night, with the Green led lighting. I can get into recovery mode but all the partitions are missing. I cant wipe anything and all my files are not there. If I restart the recovery 2-3 times everything comes back to normal. Maybe there is something wrong with the flash drive. If honorbuy replied to my messages i'd sent it back to them asap. This is not a reliable phone for daily use
Sent from my MI 5 using XDA-Developers mobile app

Try using mi flash. Follow the instruction
Sent from my MI 5 using Tapatalk

I am sending back the phone to china to have them "fix" it. Not sure what they will do, hopefully they either swap me a new phone or swap out the motherboard or something. I just hope they dont just boot into fastboot (after battery completely drained and system resets) and flash new rom and send it back to me.
Probably will take a month or so. Good thing i still have my old phone.

tkrave said:
I am sending back the phone to china to have them "fix" it. Not sure what they will do, hopefully they either swap me a new phone or swap out the motherboard or something. I just hope they dont just boot into fastboot (after battery completely drained and system resets) and flash new rom and send it back to me.
Probably will take a month or so. Good thing i still have my old phone.
Click to expand...
Click to collapse
This happened to me recently. I used mi flash and the global 7.2.4 stable fastboot rom to get it going again. Wouldn't work for me with with with newer versions. Think edl has been disabled on them.

Problem after miflash

Hey guys, I need your help, I bricked my phone yesterday, and trying to solve it I used miflash, but now that the process finished my phone only vibrate and show a green light and then start a loop , and my pc wont recognizes my phone, somebody can help me please?
sorry for my bad english

Could you give more info? Which phone, what bricked the phone, bootloader locked/unlocked, what do you see in device manager on your PC?
Are you able to go into fastboot?
There's another user dealing with a bricked phone currently here, see if anything there helps you out. Link: https://forum.xda-developers.com/zuk-z2-pro/help/zuk-z2-booting-anymore-restore-t3539804

Uivalf39 said:
Could you give more info? Which phone, what bricked the phone, bootloader locked/unlocked, what do you see in device manager on your PC?
Are you able to go into fastboot?
There's another user dealing with a bricked phone currently here, see if anything there helps you out. Link: https://forum.xda-developers.com/zuk-z2-pro/help/zuk-z2-booting-anymore-restore-t3539804
Click to expand...
Click to collapse
So in the last days I bricked my z2 pro by closing the bootloader with a custom installed, and to solve the problem I put it in EDL mode and I used the flash mi, but now when I press the power button it just vibrates and flashes a green Led, but it does not turn on, I already tried several combinations of buttons to get into fastboot and nothing, and when I plugged the usb into the pc it shows nothing

Help with Xiaomi mi5

Hi I just recived my mi5 and was wanting to put a stock android rom on it that is stable, I see a couple of ROMs on here but not sure what to use or where to start if anyone can give me a guide and correct ROM to use, I'm in UK Scotland
Sent from my HTC One using Tapatalk

Please help me my phone is in EDL mode and i can't flash anything on it. It does not turn on no led no light no display no response. Just Qualacomm QDLoader 9008
Everytime i flash it gives me an error.
Max buffer sector is 256.
Errors and so on.....
How to fix please
I have reinstalled all drivers and programs , tried a lot of miflash versions , fastboot roms like 6-8. Many pc restarts

casuk said:
Hi I just recived my mi5 and was wanting to put a stock android rom on it that is stable, I see a couple of ROMs on here but not sure what to use or where to start if anyone can give me a guide and correct ROM to use, I'm in UK Scotland
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
If I were you I would definitely flash Lineage OS, its really solid, fast and has a good battery life.
Check this post for instructions. And give him a big thank

Spevky said:
Please help me my phone is in EDL mode and i can't flash anything on it. It does not turn on no led no light no display no response. Just Qualacomm QDLoader 9008
Everytime i flash it gives me an error.
Max buffer sector is 256.
Errors and so on.....
How to fix please
I have reinstalled all drivers and programs , tried a lot of miflash versions , fastboot roms like 6-8. Many pc restarts
Click to expand...
Click to collapse
I had the exact same problem, it happened randomly after a normal reboot. I was considering taking it apart to disconnect the battery, try a deepflash cable and EDL but then I solved it.
The problem is your Windows driver. That's why you can't flash anything. Read up on Xiaomi forums about the problem. I can't remember exactly how I solved it, but I think I uninstalled the driver, plugged the phone back in, wait for the automatic install on Device Manager, then for it to update, do a roll back and then flash it via MiFlash.

xdadevet said:
I had the exact same problem, it happened randomly after a normal reboot. I was considering taking it apart to disconnect the battery, try a deepflash cable and EDL but then I solved it.
The problem is your Windows driver. That's why you can't flash anything. Read up on Xiaomi forums about the problem. I can't remember exactly how I solved it, but I think I uninstalled the driver, plugged the phone back in, wait for the automatic install on Device Manager, then for it to update, do a roll back and then flash it via MiFlash.
Click to expand...
Click to collapse
Thanks. THat must be the problem. But i tried on my friends pc too and it did not work. Maybe Windows 7 is the problem? Im installing Windows 10.
Which OS do you have?

Spevky said:
Thanks. THat must be the problem. But i tried on my friends pc too and it did not work. Maybe Windows 7 is the problem? Im installing Windows 10.
Which OS do you have?
Click to expand...
Click to collapse
I don't think Windows 7 is the problem, but I've been using Windows 10 for 3 years (as Beta user) so I can't tell. Boot into EDL (Phone must be powered off, then hold both "Volume UP" and "Volume Down" as you plug it into the computer, only then do you let go) and tell me what driver your phone is seen as in Device Manager.

xdadevet said:
I don't think Windows 7 is the problem, but I've been using Windows 10 for 3 years (as Beta user) so I can't tell. Boot into EDL (Phone must be powered off, then hold both "Volume UP" and "Volume Down" as you plug it into the computer, only then do you let go) and tell me what driver your phone is seen as in Device Manager.
Click to expand...
Click to collapse
It is detected as QDLoader 9008 version of QDLoader 9008

im trying to follow the guides but im not understanding what to do I have downloaded adb and fastboot I extracted the files to a folder and im now stuck, whats this mean
•Append ;%USERPROFILE%\adb-fastboot\platform-tools to the end of the existing Path definition (the semi-colon separates each path entry)
that's were im am so far and im basically lost and need so help if anyone is kind enough to go through the steps with me
thanks
Ok I've unlocked the phone but i can seem to be able to root it