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.

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.

mi5 hard bricked

hey guys i have a hardbricked mi5 no fast boot or charging if i connect to the computer it says unknown usb device.how to fix my device any ideas.

Try to find and install drivers for qualcomm hs-usb qdloader 9008.

if you hardbrick your pc prob detect your phone as Qualcomm hs-usb qloader 9008 . Just install any MIUI rom use MiFlashTool . you can find tutorial in MIUI forum . Because i got hardbrick last week . and my phone work again after install MIUI rom .

How to solve it
gowtham300 said:
hey guys i have a hardbricked mi5 no fast boot or charging if i connect to the computer it says unknown usb device.how to fix my device any ideas.
Click to expand...
Click to collapse
I know it's been a long while since you had this problem, but as I have to face it myself without any clue how to solve it I thought it was a good idea to recover this thread.
First of all, let me say it happened to me with a Xiaomi mi5s. I had already installed adb & fastboot, as well as Xiaomi drivers from the Xiaomi Unlock Tool.
The problem arose when I made a partial firmware upgrade through fastboot in order to install LOS 14.1 via TWRP. I could not geet into fastboot mode, the screen went completely black and no charging LED. Curiously my laptop (Win10) made a tiny nose everytime I pluged or unplugged it (the same one it does everytime you plug a new device) and saw that it recognised it as a 'Qualcomm HS-USB qloader 9008'. More curiously, Xiaomi Flash Tool (BTW, it was the beta version although I guess the latest version would have worked as well) recognised the device although everytime I tried to flash an official firmware I got a message error: 'cannot receive hello packet'.
Well, after some research I was scared because I didn't want to open the phone to unplug the battery or anything. But I read somewhere that someone had the same problem as me and that he tried Xiaomi Flash Tool until it worked.
That was it, that was the clue. Xiaomi Flash Tool ready, having initially recognised my mi5s, the phone connected to the laptop, I made the combination to get into fastboot (holding volume - & power button) until my laptop made a tiny nose (the same one I explained at the beginning). As soon as I heard it I left the phone and clicked on the flash button on Xiaomi Flash Tool. Yes, it worked out. I installed latest development chinese MIUI rom. From there, I got into fastboot, flashed a new recovery... Well that's another history, the fact is that the mi5s is working again and I must say I feel really relived.
If anyone encounters the same problem I had I hope this post is of any help to him/her.

21prods said:
I know it's been a long while since you had this problem, but as I have to face it myself without any clue how to solve it I thought it was a good idea to recover this thread.
First of all, let me say it happened to me with a Xiaomi mi5s. I had already installed adb & fastboot, as well as Xiaomi drivers from the Xiaomi Unlock Tool.
The problem arose when I made a partial firmware upgrade through fastboot in order to install LOS 14.1 via TWRP. I could not geet into fastboot mode, the screen went completely black and no charging LED. Curiously my laptop (Win10) made a tiny nose everytime I pluged or unplugged it (the same one it does everytime you plug a new device) and saw that it recognised it as a 'Qualcomm HS-USB qloader 9008'. More curiously, Xiaomi Flash Tool (BTW, it was the beta version although I guess the latest version would have worked as well) recognised the device although everytime I tried to flash an official firmware I got a message error: 'cannot receive hello packet'.
Well, after some research I was scared because I didn't want to open the phone to unplug the battery or anything. But I read somewhere that someone had the same problem as me and that he tried Xiaomi Flash Tool until it worked.
That was it, that was the clue. Xiaomi Flash Tool ready, having initially recognised my mi5s, the phone connected to the laptop, I made the combination to get into fastboot (holding volume - & power button) until my laptop made a tiny nose (the same one I explained at the beginning). As soon as I heard it I left the phone and clicked on the flash button on Xiaomi Flash Tool. Yes, it worked out. I installed latest development chinese MIUI rom. From there, I got into fastboot, flashed a new recovery... Well that's another history, the fact is that the mi5s is working again and I must say I feel really relived.
If anyone encounters the same problem I had I hope this post is of any help to him/her.
Click to expand...
Click to collapse
fixed long time ago , but i appreciate your help and you taking time to do this for me

You are welcome. I was afraid I wouldn't be of much help to you but I thought that it was a good idea anyway to leave my experience just in case at some point it proves helpful to someone.

My Z2 Pro dead .. help me ..!!

i did something Stupid and my Z2 Pro dead
there is no fast-boot and no recovery .. only black screen and when i press power button there is a short and long vibration just that and the LED there is flash yellow for 0.1 second

aljthab said:
i did something Stupid and my Z2 Pro dead
there is no fast-boot and no recovery .. only black screen and when i press power button there is a short and long vibration just that and the LED there is flash yellow for 0.1 second[/QUOTE try connecting it to the PC, if it doesn't show anything on PC then just hand it over to the lenovo service center and blame it on the device that it stopped booting :silly:. I thought i had bricked my device but they did something and gave it to me in 3 to 4 days and that was done under the warranty no extra charge and don't confess that I had rooted ur device , If u tell them that they will try to extort money from u :crying:
Click to expand...
Click to collapse

aljthab said:
i did something Stupid and my Z2 Pro dead
e LED there is flash yellow for 0.1 second
Click to expand...
Click to collapse
I have exactly the same, what to do? I installed the dev 44, the rate of established but after 15 minutes, logo is stalled, not waiting until the end of excess freewheeling dev 300, it is not fully established and bug crawled, I rebooted the machine and an endless vibration with green LED :crying:
1 Charging can be a little warm
2. can not be detected pc
3. can not access the fastboot mode
4. when charging, the notification light dies
5. deep flash cable has not helped
sorry my bad english

kerei said:
I have exactly the same, what to do? I installed the dev 44, the rate of established but after 15 minutes, logo is stalled, not waiting until the end of excess freewheeling dev 300, it is not fully established and bug crawled, I rebooted the machine and an endless vibration with green LED :crying:
1 Charging can be a little warm
2. can not be detected pc
3. can not access the fastboot mode
4. when charging, the notification light dies
5. deep flash cable has not helped
sorry my bad english
Click to expand...
Click to collapse
Refer to this http://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ and this http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/

same issue with zuk z2
adriano1593 said:
Refer to this http://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ and this http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
Click to expand...
Click to collapse
Hello there... Any solution you found? I am stuck with my zuk z2 in same situation ?? any help ?

I have a similar problem.
What caused the black screen? -
History:
I booted to test mode at 2.5.033 ST, the phone got stucked at this menue there was no way to get out. TWRP Restore to Nandroid bougt only black screen after 2nd vibration and ZUK logo.
I fixed the Test mode bug, by flashing the ZUI 1.9.104 ST Stock ROM via QPST.
After the phone was "repaired" I unlocked the bootloader, installed TWRP, made a nandroid backup of fully stock ROM and restored a nandroid backup from before the test mode problem.
The nandroid restore was successful, I rebooted the phone and it was "dead". Black screen, only rebooting (perioldy vibrating) there was no end, until the battery was empty.
I got no luck to reach any mode with tricky button pressing (vol+ pwr; vol- pwr; vol+ vol- pwr; usb in vol-) nor Windows detecting the phone. That's why I decided to remove the back glass cover, to got access to the battery.
Now I'm able to get the phone detected by my PC.
What I did: disconnect the battery, connect the phone to my computer, pressed the vol- button and connect the battery.
This made my PC able to detect the phone, but no I have an other problem. Windows only detects the phone as "unknown usb device (device descriptor request failed)". I don't know any way to install the driver....
Maybe anyone is able to help me or has any tip?
Thanks!
Cheers,
m_atze

m_atze said:
I have a similar problem.
What caused the black screen? -
History:
I booted to test mode at 2.5.033 ST, the phone got stucked at this menue there was no way to get out. TWRP Restore to Nandroid bougt only black screen after 2nd vibration and ZUK logo.
I fixed the Test mode bug, by flashing the ZUI 1.9.104 ST Stock ROM via QPST.
After the phone was "repaired" I unlocked the bootloader, installed TWRP, made a nandroid backup of fully stock ROM and restored a nandroid backup from before the test mode problem.
The nandroid restore was successful, I rebooted the phone and it was "dead". Black screen, only rebooting (perioldy vibrating) there was no end, until the battery was empty.
I got no luck to reach any mode with tricky button pressing (vol+ pwr; vol- pwr; vol+ vol- pwr; usb in vol-) nor Windows detecting the phone. That's why I decided to remove the back glass cover, to got access to the battery.
Now I'm able to get the phone detected by my PC.
What I did: disconnect the battery, connect the phone to my computer, pressed the vol- button and connect the battery.
This made my PC able to detect the phone, but no I have an other problem. Windows only detects the phone as "unknown usb device (device descriptor request failed)". I don't know any way to install the driver....
Maybe anyone is able to help me or has any tip?
Thanks!
Cheers,
m_atze
Click to expand...
Click to collapse
What id shown in unknown device.
Like ven_9102&dev_1234
Maybe with editing quallcom drivers for your device id, you can still install it.
and if luck qpst can recognize it as qualcomm debug mod
Sent from my ZUK Z2121 using Tapatalk

eryenakgun said:
What id shown in unknown device.
Like ven_9102&dev_1234
Maybe with editing quallcom drivers for your device id, you can still install it.
and if luck qpst can recognize it as qualcomm debug mod
Sent from my ZUK Z2121 using Tapatalk
Click to expand...
Click to collapse
Hi,
Thanks for your quick response.
The Hardware ID: USB\DEVICE_DESCRIPTOR_FAILURE
"Error Message": This device has been stopped because it has reported errors. (Code 43)
An error occurred while requesting the USB device descriptor.

m_atze said:
I have a similar problem.
What caused the black screen? -
History:
I booted to test mode at 2.5.033 ST, the phone got stucked at this menue there was no way to get out. TWRP Restore to Nandroid bougt only black screen after 2nd vibration and ZUK logo.
I fixed the Test mode bug, by flashing the ZUI 1.9.104 ST Stock ROM via QPST.
After the phone was "repaired" I unlocked the bootloader, installed TWRP, made a nandroid backup of fully stock ROM and restored a nandroid backup from before the test mode problem.
The nandroid restore was successful, I rebooted the phone and it was "dead". Black screen, only rebooting (perioldy vibrating) there was no end, until the battery was empty.
I got no luck to reach any mode with tricky button pressing (vol+ pwr; vol- pwr; vol+ vol- pwr; usb in vol-) nor Windows detecting the phone. That's why I decided to remove the back glass cover, to got access to the battery.
Now I'm able to get the phone detected by my PC.
What I did: disconnect the battery, connect the phone to my computer, pressed the vol- button and connect the battery.
This made my PC able to detect the phone, but no I have an other problem. Windows only detects the phone as "unknown usb device (device descriptor request failed)". I don't know any way to install the driver....
Maybe anyone is able to help me or has any tip?
Thanks!
Cheers,
m_atze
Click to expand...
Click to collapse
Alright bro, there is one method you can try.
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
I assume your phone is a brick now. The only method you can use is the 9008 unbrick mode. (AKA QBST)
There are a few things you need to prepare before you save ur phone. U need to download the require application that the website provided above, after you set everything up,
make sure you download the latest 2.5 QBST rom,
http://bbs.lenovomobile.cn/z2pro/t554654/
Because ur phone wont be able to enter 9008 through software, thus u need to do the following.
1. Load the content XML fille,
2.Turn off your phone. After it's fully shutdown
3. press and hold the volume up button for 3 seconds
4. press power button while hold the volume up (press it for 0.5second and keep holding it)
5. after 0.5 seconds, plug in the usb right away
6. the QFIL tool should appear the Qualcomm usb QD loader
7. the download button should turn blue
8. flash it and wait for reboot

OtakuLi said:
Alright bro, there is one method you can try.
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
I assume your phone is a brick now. The only method you can use is the 9008 unbrick mode. (AKA QBST)
There are a few things you need to prepare before you save ur phone. U need to download the require application that the website provided above, after you set everything up,
make sure you download the latest 2.5 QBST rom,
http://bbs.lenovomobile.cn/z2pro/t554654/
Because ur phone wont be able to enter 9008 through software, thus u need to do the following.
1. Load the content XML fille,
2.Turn off your phone. After it's fully shutdown
3. press and hold the volume up button for 3 seconds
4. press power button while hold the volume up (press it for 0.5second and keep holding it)
5. after 0.5 seconds, plug in the usb right away
6. the QFIL tool should appear the Qualcomm usb QD loader
7. the download button should turn blue
8. flash it and wait for reboot
Click to expand...
Click to collapse
Thanks for your tip.
I followed your described procedure, but the phone will not be recocnized by the PC.
1st: I loaded QFIL XML file. (By the way this tut is made by me)
2nd: I disconnected the battery (The phone can't be turned off normally!)
3rd, 4th, 5th
6th: nothing happend!
7th: "-"
8th: "-"
The only way the phone will detected by the PC:
1st: disconnect battery
2nd: plug in USB (PC and Phone)
3rd: press VOL+ or VOL- or PWR button (doesn't matter which one)
4th: connect battery
5th: detected as "unknown usb device (device descriptor request failed)"

m_atze said:
Thanks for your tip.
I followed your described procedure, but the phone will not be recocnized by the PC.
1st: I loaded QFIL XML file. (By the way this tut is made by me)
2nd: I disconnected the battery (The phone can't be turned off normally!)
3rd, 4th, 5th
6th: nothing happend!
7th: "-"
8th: "-"
The only way the phone will detected by the PC:
1st: disconnect battery
2nd: plug in USB (PC and Phone)
3rd: press VOL+ or VOL- or PWR button (doesn't matter which one)
4th: connect battery
5th: detected as "unknown usb device (device descriptor request failed)"
Click to expand...
Click to collapse
Make sure you have to plug in the usb right away as soon as you u press power, and keep holding them

OtakuLi said:
Make sure you have to plug in the usb right away as soon as you u press power, and keep holding them
Click to expand...
Click to collapse
Yes, I did exactly you described. Sorry but this isn't working.
I don't know what I should do. Even a repair shop couldn't fix it.
Maybe I need to do this:
http://bbs.lenovomobile.cn/z2/t121791/?highlight=900e
But I don't want to destroy my PC (3000 bugs)

m_atze said:
Yes, I did exactly you described. Sorry but this isn't working.
I don't know what I should do. Even a repair shop couldn't fix it.
Maybe I need to do this:
http://bbs.lenovomobile.cn/z2/t121791/?highlight=900e
But I won't destroy my PC (3000 bugs)
Click to expand...
Click to collapse
oh well, good luck

OtakuLi said:
oh well, good luck
Click to expand...
Click to collapse
I will report the result.

OK. I made the deepflash cable.
After using it there is no difference between pressing one of the button combinations I recently mentioned (VOL+ or VOL- or PWR).
The phone will be detected as Unknown device. After intalling my modified driver to match the unknown ID, QFIL don't detect the COM Port.

Hello had the same problem, only with the difference that my battery was not completely discharged.
What has helped:
1 Start QFIL Tool
2 Press the volume +
3 Connect the original cable to the PC
4 QFIL Tool recognized the phone and I could play an original Rome.
Mfg
Ps. Is now the battery cover (glass) broken?

No, I used a hairdryer, a razorblade, plastic tool and a suction cup to lift the backcover glass.
The glass is fully intact no damages.

You have good nerves. I would not have expected that.
But in the end, it does not matter if it does not start anymore.
Thank you again for your great instructions for playing and rooting the mobile phone.
I hope you get your phone back.
Mfg

Good and bad news
The guy unbricked the phone successfully, I received it today.
Now I have an other problem:
The phone is very very slow and laggy now.
The problem occurs everywere, Recovery, boot (the bootlogo laggs), booted System, also the test mode laggs now
Furthermore the sceen flickers sometimes and at the right side the sceen is mirrored sometimes.
Did anyone has an idea?
What I did today:
reflash through qfil
1.9.104_ST
2.3.044_ST
ZUI_2.5.335_ST

Hi m_atze, I am exactly in the same situation as You. After using deep flash cable method, I got "unknown usb device (device descriptor request failed)". Could You tell me what was the solution to unbrick the phone?

Question Help needed. I think I bricked my phone...

I installed android 12 beta on my Mi 11 ultra. Did not like it and wanted to install global. Installed TWRP, wiped data and instead of rebooting in twrp, I tried to enter fastboot mode via adb. The phone screen turned black. Now it is not showing in ADB, not detected by Mi flash tool, not enetering fastboot mode and not entering recovery. When I connect it to computer, there is this connecting sound but soon it is followed by disconnecting sound. Not even getting the charging screen. In the device manager on Windows, there is this Qualcum HS-USB QDLoader 9008 (COM9) when the phone is connected via USB cable to PC.
Anyway to restore any firmware on it? It is a CN version, star, has bootloadder unlocked.
EDL time? Or even worse? Is it paperweight now?

EDL time I think.

Sathelp said:
EDL time I think.
Click to expand...
Click to collapse
Believe me, this is reassuring. I'm happy to settle on EDL instead of paperweight... For EDL does the phone need to be opened, back cover removed and then that magic short circuit or is there a way to get it done without opening the phone?

hellodrsoul said:
Believe me, this is reassuring. I'm happy to settle on EDL instead of paperweight... For EDL does the phone need to be opened, back cover removed and then that magic short circuit or is there a way to get it done without opening the phone?
Click to expand...
Click to collapse
Don't worry. When mine was EDL flashed the guy asked me to download a specific miflash version that he had the link for and the ROM of choice to be flashed. I connected the phone to the PC, he connected, asked me to put it in to EDL mode ( he will explain if your not sure) and done his stuff using TeamViewer with control of my desktop. Once finished, just rebooted when asked, all done.

need mi auth to flash

How do you put the phone in EDL mode?

can you get your phone on fastboot?

xNAPx said:
How do you put the phone in EDL mode?
Click to expand...
Click to collapse
Hold both vol up and down while powering up or adb, adb reboot edl or fastboot, fastboot oem edl . You will see edl drivers load on your PC.

Thank you guys for your replies. I got it fixed and now it is rocking again. If anybody faces the same issue, please see details below.
Diagnosis: EDL mode
Signs and problems: Completely dead phone. Black screen. None of the buttons or their combinations work. Volume down plus power, volume up plus power, Both volume buttons, All three buttons. None of these worked in this EDL mode. In fact, the only sign that this phone was "alive" was the Qualcomm driver showing in the device manager when the phone was connected to a PC. There was this yellow sign even on the Qualcomm driver and the official Xiaomi flash tool failed to detect the phone due to the Qualcomm driver malfunction. Got the Qualcomm driver working (the yellow sign on the driver name icon in device manager) by disabling windows driver signature check. After this the phone was detected by the official Xiaomi flash tool. When I tried to flash the official and stock CN ROM, it did not allow me and gave the error "you are not authorized to download". Took the phone to Xiaomi service, they refused as the phone was of another region. They did not know any unofficial paid solution. Took it to local technicians. They tried but failed (ultimate multi-tool, some other tool they called as "aqua" did not work.
Treatment: Searched online and found a YouTube channel (
). Paid USD 35 and got it flashed via TeamViewer. I just sat anxiously (praying that he must not be a scammer...). He did some magic and successfully flashed the phone with the original CN ROM with the boot loader unlocked. I then was able to install the global version via fastboot as usual.
Thanks again for the free support I got here. Obliged and stay blessed

hellodrsoul said:
Thank you guys for your replies. I got it fixed and now it is rocking again. If anybody faces the same issue, please see details below.
Diagnosis: EDL mode
Signs and problems: Completely dead phone. Black screen. None of the buttons or their combinations work. Volume down plus power, volume up plus power, Both volume buttons, All three buttons. None of these worked in this EDL mode. In fact, the only sign that this phone was "alive" was the Qualcomm driver showing in the device manager when the phone was connected to a PC. There was this yellow sign even on the Qualcomm driver and the official Xiaomi flash tool failed to detect the phone due to the Qualcomm driver malfunction. Got the Qualcomm driver working (the yellow sign on the driver name icon in device manager) by disabling windows driver signature check. After this the phone was detected by the official Xiaomi flash tool. When I tried to flash the official and stock CN ROM, it did not allow me and gave the error "you are not authorized to download". Took the phone to Xiaomi service, they refused as the phone was of another region. They did not know any unofficial paid solution. Took it to local technicians. They tried but failed (ultimate multi-tool, some other tool they called as "aqua" did not work.
Treatment: Searched online and found a YouTube channel (
). Paid USD 35 and got it flashed via TeamViewer. I just sat anxiously (praying that he must not be a scammer...). He did some magic and successfully flashed the phone with the original CN ROM with the boot loader unlocked. I then was able to install the global version via fastboot as usual.
Thanks again for the free support I got here. Obliged and stay blessed
Click to expand...
Click to collapse
I tried this method today and it wasn't successful. It appeared he flashed it with his auth code, but it still doesn't power on. I'm so bummed because DHL won't touch the phone for less than $151 (risk of it being sent back) because seller wants me to lie and say it's a gamepad when DHL has precautions on phones being sent back, etc. requiring importer certificates.
My phone was acting strange on 3rd day: wasn't detecting charging USB cable overnight, would only charge wirelessly. I manually rebooted a bunch of times, then it detected the USB charging and would charge. About that time I updated to Miui 13 OTA update (Chinese /EN Rom) and noticed it was rebooting randomly in my pocket asking for PIN (not getting notifications) . Again got no USB charging through cable.
I was doing a bunch of vol up/down and Power and rebooted into safe mood. Rebooted again after things were 'ok' and little while later, the phone was OFF and never came back on again.
Did I put it into EDL and brick it this way? I Never flashed anything through USB until I tried the 35eur paid service dude.

Happy to see that is being fixed.

Wish it had fixed mine. Unfortunately, it didn't . Was refunded