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.
Related
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.
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
Hey, Ive tried to install xiaomi.eu rom but didnt realize that i needed the chinese rom and that the global didnt work for this, after ive installed using TWRP the rom, ive rebooted and it just went black, not recovery, not fastboot.
BT was unlocked.
I also see my phone as qualcomm...qloader 9008 when connecting to my pc
Any help?
after having a few heartattacks, ive installed a good Miflsah and a good fastboot rom, and managed to restore my phone to its former glory
no need for further help, but i have a few advices
dont be stupid like me, and listen to directions like theyre the word of god, when they say change from chinese rom to a non official rom, YOU NEED CHINESE, global wont work
and if you're having problems with miflash giving errors, try a bunch of downloads, old, new, everything.
Hi, yet another brick here!
I had an AOSP ROM but I had problems with it. I entered TWRP, downloaded a MIUI official ROM for recovery, wiped the phone from TWRP and decrypting it (there was an option for that). Then I did try to flash the ROM and... black screen. No signs of life.
However, when I connect it to the computer it detects it as the famous Qualcom xxx 9008 (COM10) device. But fastboot is not working, when I type "fastboot devices" it doesn't return anything. ADB doesn't recognize the phone either. Everywhere I saw that I should use MiFlash to recover it, but I took a look at the scripts and are using fastboot to perform the process. But since fastboot doesn't recognize the device, it won't work. I get stuck all the time at "Failed to receive the hello packet".
Fastboot doesn't detect my phone either on Linux or Windows. I tried Linux, virtual Windows 10 (x64) and at last I'm trying on a Windows 10 (x64) computer (no virtualization). No matter what I do, it always stays at the same point. I also used several MiFlash versions (from old builds from last year to the most up-to-date version of XiaomiMiFlash). But since fastboot is not detecting the phone I think there's no point in switching MiFlash versions.
So... what can I do? Should I use the pin short-circuit /deepflash cable method? As of I understand, that is what you use to get into EDL, but if my device is showing 9008 in device manager doesn't it mean that I'm already in EDL? I'm not really sure because all the threads I saw in several forums are a bit messy.
I'll appreciate any help. I don't have phone since 3 days ago and I can survive without it but I need it for my work.
Thank you in advance!
EDIT:
Forgot to say, if I try to power off and power on it doesn't do anything BUT when I plug and unplug from the charger it does show a battery icon with the charged percentage. That's the only sign of life from the phone, aside from being recognized as a 9008 device, but that actually happens when I try to (blindly) get in fastboot mode.
FIXED!!! After four hours testing out several options I found the solution: Open up the phone, unplug the battery cable, plug it again, and voilà. The phone automatically got recognized (again) as Qualcomm 9008 device but this time the flash went on flawlessly. It took less than 5 minutes, once succeeded I powered on the device and it ran into MIUI 8 in less than 5 minutes.
So, if you find issues with the command "fastboot devices", unplug the battery and try it again before troubling yourself with deepcables or shortcircuits ;-D
NOTE: Taking out the back cover is very easy, search on youtube, I bought the thing you need for 1$ at the store next to my home (sorry I don't know what it's called).
Hello all,
A friend of mine said he was careless and installed an A2 Lite ROM to his A2. All I know is he can't fix the phone no matter what he tried.
Can we do something about this? Or is the phone permanently bricked?
lelele5 said:
Hello all,
A friend of mine said he was careless and installed an A2 Lite ROM to his A2. All I know is he can't fix the phone no matter what he tried.
Can we do something about this? Or is the phone permanently bricked?
Click to expand...
Click to collapse
try flashing stock rom
Thank you for the reply. Will get back to you as soon as I get an answer from him.
Okay, I got some more info: From what my friend said:
He installed the ROM but after selecting "restart device" it didn't boot up.
Pressing button combinations has no effect either.
When the device is connected to PC Windows recognizes it as "Qualcomm HS-USB QDLoader 9008(COM3)".
He also tried different versions of MiFlash but he is getting "The Write timed out" and "cannot read hello packets" (???) errors.
Since the device isn't reacting to button presses he can't activate fastboot.
This was translated from another language. Hope I didn't make any mistakes.
EDIT: He tried edl before, it didn't work.
Now he is getting "Error loading type library/DLL".
Your friend need to do Flash Point
Ask him to google "How to flash a qualcomm soc with qpst via com port". I'm sure he'd find a lot of videos on youtube guiding through the entire process. Also tell him to keep the stock fastboot rom downloaded, coz he'll be needing that.
Flashing a wrong rom destroyed the partition table of his device. If he cant fix it himself, tell him to visit a nearby service centre. He'll get the device back in a few days or so.
lelele5 said:
Okay, I got some more info: From what my friend said:
He installed the ROM but after selecting "restart device" it didn't boot up.
Pressing button combinations has no effect either.
When the device is connected to PC Windows recognizes it as "Qualcomm HS-USB QDLoader 9008(COM3)".
He also tried different versions of MiFlash but he is getting "The Write timed out" and "cannot read hello packets" (???) errors.
Since the device isn't reacting to button presses he can't activate fastboot.
This was translated from another language. Hope I didn't make any mistakes.
EDIT: He tried edl before, it didn't work.
Now he is getting "Error loading type library/DLL".
Click to expand...
Click to collapse
all is fine ...
he can flash it in miflash in edl mode
if computer can see the 9008 com port he is already in edl
the error with hello packets is because he waits too long to start flashing ..he needs to unplug phone then when he plugs it in he must have everything prepared then press flash quickly
he can wait for battery to run out of charge ...then prepare miflash ...then plug in phome ...the EXACt moment it wakes press flash
then it will work
Thanks a lot for your time and help everyone. He got frustrated and sent it to a service center. I couldn't convince him. It works fine now, though.
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