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.
Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
If you can flash/boot into TWRP, then probably nothing is lost. While in TWRP, if you connect your phone with PC, what happens? Do you hear the usual USB connection sound? If yes, what appears in the device manager?
Even if it doesn't appear in device manager, don't worry.
Boot into TWRP, go to storage, DISABLE MTP and enable it again. I know it sounds dumb, but just try it. It will be recognized as long as you have the proper drivers installed.
After that copy the zip of an OxygenOS based ROM like FreedomOS and flash it. Don't wipe anything. It will boot fine. I've done that a few times, never had a problem.
Thanks for the advice guys - no, no sound, nothing - as I said, I only get the charging (+) icon in twpr next to the battery percentage.
I did disable and enable MTP before - although not plugged in a pc during the process - will try if I have the chance.
One more thing that might ring a bell for someone - I tried the key combo for hard reset today(power + vol down) for a couple second and moments later I got a fuzzy (random colored pixels) screen and a red led. Weird, if you ask me.
P.S.: Today I tried to chat with OP a bit - 230 Eur for a new MB (64GB) and 255 Eur for my 128GB version - I just wanted to know, I'm still not admitting failure though. But as a student, these numbers from the support literally hurt me when reading...
grello said:
Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
Click to expand...
Click to collapse
1) try to update the twrp to the official 3.1.1.0. Then flash the latest modem firmware for your device and try to flash a custom rom like lineage os (a 7.x rom)
If you connect the phone to PC in TWRP and your phone is not recognized, chances are good that either your phone's USB or the cable (or the USB port on the computer) is not working. You can try to download the adb driver installer from here, just to check if your phone is listed by the installer: http://adbdriver.com/downloads/
Update - tried the MTP Enable/disable option in TWRP (in the Mount menu) while plugged into the PC, with no luck
IvanPrince - have you actually read the description of my problem? I have the 3.1.1-0 and even if not, how should I actually flash another version of twrp? The problem here is I cannot seem to find a WAY how to flash ANYTHING on the device.
I'll see about the adb drivers and update.
Thanks all,
Does the phone show up as anything on the PC when you boot to fastboot? I re-read but didn't see anything about it.
Nope - nothing. By now, I believe it is a hardware problem as the phone indeed got wet before my mistake with the advanced wipe. It appears to work just fine though, apart from the connectivity issue, so I believe the MB should be ok as everything else, including the screen is.
I just have one, perhaps a little courageous thing I'd like to ask from someone kind enough. Anyone with a Oneplus 3 or 3T who's not afraid to open the phone for a couplne minutes and has a multimeter alongside with a USB cable should be able to help me. :angel:
Could you, my awesome stranger, check where the 4 USB pins (on the side where you plug them into the PC) lead (make contact/'BEEP' on the multimeter) with the actual phone motherboard? It would REALLY help me in troubleshooting and perhaps saving 250 Eur. So far, I have this: (same color means contact) at that point. See picture.
BLACK - GND (all the heatsinks are connected to GROUND as well)
GREEN - DATA +
YELLOW - DATA -
RED - VCC
If anyone decides to open up their phone and help out a fellow xda guy, it will be greatly appriciated. :angel:
Hey Bro I was curious to know if you tried this method of recovering from a hard brick... When I first got my 3t something similar happened to me. I can't remember all the details of my hard brick but I thought I was f***ed. Please try this if you have not already.
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Might be a dumb question, but you did remember to mount the USB when you connected the otg right?
If the bootloader is unlocked, you can save it.
I would flash the stock recovery and the latest factory image (4.1.7)
Download them both from here:
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/
After flashing the stock recovery using fastboot, boot to stock recovery and sideload through ADB the stock factory image.
Reboot and after checking that everything is working fine, feel free to relock the bootloader if you wish to stay 100% stock.
If the computer doesn't recognize it at all then it's a driver problem, not the phone... at least that's what I think.
try to use the program to fix my oneplus 3t it said download complete. try to restart
try to use the program to fix my oneplus 3t it said download complete. try to restart it and can press the screen and it keep rebooting it like the screen is frozen
please help me out
Hi, I have a new redmi 9c NFC, it has an Mediatek chip, so I can instant unlock bootloader, I installed a MIUI 12.5 Port for this phone "https://forum.xda-developers.com/t/...dmi-9c-nfc-angelica-angelican-stable.4383125/"
I didn't had enough space for GApps I saw a tutorial on YouTube for expand system partition "
"
I deleted partitions, (super, recovery and cache). I accidentally rebooted my phone, and now i'ts on a black screen, no recovery, not fasboot, no vibrations, the only signal of life that I have is when I connect the phone to my computer, It appears like this: "Dispositivo serie USB (COM4)" (It's on spanish because I'm spanish, and sorry for my bad English) I can't use Mi flash or something. PLZ HELP, I'M DESESPERATED
AvZPablo4 said:
Hi, I have a new redmi 9c NFC, it has an Mediatek chip, so I can instant unlock bootloader, I installed a MIUI 12.5 Port for this phone "https://forum.xda-developers.com/t/...dmi-9c-nfc-angelica-angelican-stable.4383125/"
I didn't had enough space for GApps I saw a tutorial on YouTube for expand system partition "
"
I deleted partitions, (super, recovery and cache). I accidentally rebooted my phone, and now i'ts on a black screen, no recovery, not fasboot, no vibrations, the only signal of life that I have is when I connect the phone to my computer, It appears like this: "Dispositivo serie USB (COM4)" (It's on spanish because I'm spanish, and sorry for my bad English) I can't use Mi flash or something. PLZ HELP, I'M DESESPERATED
Click to expand...
Click to collapse
You can use instead SPFT.
I used SP Flash Tool. I watched a YouTube tutorial:
I didn't had luck, It said me : PTM changed from the ROM; It must be downloader. Please select "Formato Allí + Download" scene and try again
It didn't work on Format All . It grave me this error: ERROR : STATUS_UNKNOWN_STORAGE_SECTION_TYPE (0xC003000C). [HINT]:
I tried to search solutions but nothing.
Well, it is very risky to use this function, it may format the calibration data, and your IMEI, within other things, so you shouldn't have to try this option, before to take a backup and even be sure, that this backup will, really, restore the things.
Try flashing only the preloader first, then go for the rest of partitions. You also have this tool to back up every thing that is not corrupted, https://github.com/bkerler/mtkclient
SubwayChamp said:
Well, it is very risky to use this function, it may format the calibration data, and your IMEI, within other things, so you shouldn't have to try this option, before to take a backup and even be sure, that this backup will, really, restore the things.
Try flashing only the preloader first, then go for the rest of partitions. You also have this tool to back up every thing that is not corrupted, https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
Ok, I have a problem, I think that my phone is bricked forever. I watched a tutorial
It's a bad quality tutorial
It surprisely worked!! I obviously used Redmi 9c NFC files.
When the phone were flashing, my cat passed trough the cable and he desconnected it. It only flashed bootloader, but still no fastboot or something else Now, if I connect the mobile to the computer it says: The usb device is not recognized.
In the device manager it appears as: Unknown USB device (Device descriptor request error).
It has error code 43
I'm going to press the power button or something and try it again
AvZPablo4 said:
Ok, I have a problem, I think that my phone is bricked forever. I watched a tutorial
It's a bad quality tutorial
It surprisely worked!! I obviously used Redmi 9c NFC files.
When the phone were flashing, my cat passed trough the cable and he desconnected it. It only flashed bootloader, but still no fastboot or something else Now, if I connect the mobile to the computer it says: The usb device is not recognized.
In the device manager it appears as: Unknown USB device (Device descriptor request error).
It has error code 43
I'm going to press the power button or something and try it again
Click to expand...
Click to collapse
Well, what the guy is doing, is basically, installing the LibUSB dev filters, to get device recognized, and can bypass the DA/SLAA authentication, then it is flashing a firmware using SPFT, this usually, even in a serious bricking state, is not that hard, BUT, your main issue now, is that you repartitioned some essential images onto your device, so the safe way to keep it trying will be flashing once by once, every partition to detect exactly, which of them were altered (I guess super and data), flash first the preloader, and then proceed one by one.
For sure the option format all will fix your device but unfortunately, this will erase the calibration data and your IMEI, mainly, you have the option that you can back up all your partitions, no matter super nor recovery nor userdata, but the others, using the CLI tool I provided the link, after that you should perform a format all, and then restore them.
SubwayChamp said:
Well, what the guy is doing, is basically, installing the LibUSB dev filters, to get device recognized, and can bypass the DA/SLAA authentication, then it is flashing a firmware using SPFT, this usually, even in a serious bricking state, is not that hard, BUT, your main issue now, is that you repartitioned some essential images onto your device, so the safe way to keep it trying will be flashing once by once, every partition to detect exactly, which of them were altered (I guess super and data), flash first the preloader, and then proceed one by one.
For sure the option format all will fix your device but unfortunately, this will erase the calibration data and your IMEI, mainly, you have the option that you can back up all your partitions, no matter super nor recovery nor userdata, but the others, using the CLI tool I provided the link, after that you should perform a format all, and then restore them.
Click to expand...
Click to collapse
Thanks for the reply!!
I can't backup, Flash or something, my pc down't detect my phone, it's unrecognised, by device manager or in lib usb, I changed the usb cable and port but nothing, I can't connect the phone to the pc.
If I get the possibility of connect the phone to the pc successfully, I would try that! ( I reset PC but nothing)
I sent a (tablet quality) video reporting the problem a bit.
AvZPablo4 said:
Thanks for the reply!!
I can't backup, Flash or something, my pc down't detect my phone, it's unrecognised, by device manager or in lib usb, I changed the usb cable and port but nothing, I can't connect the phone to the pc.
If I get the possibility of connect the phone to the pc successfully, I would try that! ( I reset PC but nothing)
I sent a (tablet quality) video reporting the problem a bit.
Click to expand...
Click to collapse
Windows not recognizing is normal in this state because your device is trying to boot to system, then Windows can't detect it as MTP BUT to have the device detected properly for preloader mode, you firstly have to install all the proper MediaTek drivers, then, from LibUSB entries listed choose one from all, i.e. Dispositivo Compuesto USB, it doesn't matter that it is the right entry, but this entry, if it is succesfully changed, would serve to recognize it, always that the VCom, and preloader drivers are properly installed.
I installed all LibUSB entries, install mtk drivers but nothing, it says (the same as before):
USB device not recognized
The last USB device you connected to this computer did not work properly, and Windows did not recognize it.
Remember that I flashed bootloader (I don't know what it is for you, but in case it causes a conflict with the IMEI or I don't know)
AvZPablo4 said:
I installed all LibUSB entries, install mtk drivers but nothing, it says (the same as before):
USB device not recognized
The last USB device you connected to this computer did not work properly, and Windows did not recognize it.
Remember that I flashed bootloader (I don't know what it is for you, but in case it causes a conflict with the IMEI or I don't know)
Click to expand...
Click to collapse
You have to keep pressed the buttons, even while the device is connected to the PC, your device will pass through various states, then quickly you have to release your fingers.
Well, preloader is a kind of bootloader, in MediaTek.
Use this tool, to bypass, https://androidfilehost.com/?fid=17825722713688275528 when you have success from the tool, then just run SPFT, uncheck the options LIB USB DA match storage and Storage Life Cycle, also check USB full speed.
I'm going to try it right now. Im' going to edit this for give the results
1st edit: I didn't start yet to bypass that, but, it has password
2nd edit: I pressed power button for 15 seconds and pw button + vol up for 10 seconds but nothing, with all drivers and all, still at: unknown usb device
AvZPablo4 said:
I'm going to try it right now. Im' going to edit this for give the results
1st edit: I didn't start yet to bypass that, but, it has password
2nd edit: I pressed power button for 15 seconds and pw button + vol up for 10 seconds but nothing, with all drivers and all, still at: unknown usb device
Click to expand...
Click to collapse
The tool is mirrored from other sites though https://gsmatoztool.com/mtk-auth-bypass-tool-v26-new-update-latest-tool/
Press the three buttons, but pay attention to the sound of PC and to device manager when something change.
Also download the UsbDk 64-Bit installer from the site I linked, with mtk-client tool you also can do some things.
SubwayChamp said:
Press the three buttons, but pay attention to the sound of PC and to device manager when something change.
Click to expand...
Click to collapse
I pressed the 3 buttons at the same time by 5 minutes but nothing, no sound, no changes on device manager
AvZPablo4 said:
I pressed the 3 buttons at the same time by 5 minutes but nothing, no sound, no changes on device manager
Click to expand...
Click to collapse
The way to use the tool I linked is, clicking on bypass and pressing the two volume buttons, but probably you have to get your device listed in LibUSB, and quickly, install it, otherwise you won't be able to use SPFT.
This is the guide to get the things working, read carefully every step, if it's needed, then uninstall all the drivers and reinstall them, just what you need. https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/
SubwayChamp said:
The way to use the tool I linked is, clicking on bypass and pressing the two volume buttons, but probably you have to get your device listed in LibUSB, and quickly, install it, otherwise you won't be able to use SPFT.
This is the guide to get the things working, read carefully every step, if it's needed, then uninstall all the drivers and reinstall them, just what you need. https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/
Click to expand...
Click to collapse
Nope, I installed all, but when I connect it (vol up + vol down) the same, usb not recognized. This is a redmi 9C NFC, that realme has the same mtk chip, but it might change on this xiaomi
AvZPablo4 said:
Nope, I installed all, but when I connect it (vol up + vol down) the same, usb not recognized. This is a redmi 9C NFC, that realme has the same mtk chip, but it might change on this xiaomi
Click to expand...
Click to collapse
This is a generic guide that applies for any MediaTek device, I had Realme and Xiaomi. Try combining other hardware buttons, pay attention to this: you should keep pressing (even blindly because of no sign of life) assuming that your device is either on or off, and interchanging the buttons.
SubwayChamp said:
This is a generic guide that applies for any MediaTek device, I had Realme and Xiaomi. Try combining other hardware buttons, pay attention to this: you should keep pressing (even blindly because of no sign of life) assuming that your device is either on or off.
Click to expand...
Click to collapse
I kept pressing vol up + vol down for like 10 min, but, nothing
AvZPablo4 said:
I kept pressing vol up + vol down for like 10 min, but, nothing
Click to expand...
Click to collapse
It's not a matter of time, if after 15 seconds or around, you don't hear something either from your PC or your device, then clearly, it's not working.
What I'm trying to say is, that you have to press all the modes available, PWR + vol. down, PWR + vol. up, both volume buttons, three buttons, all that doing it blindly because you can't see something onto your display, so no sign of life.
To better understand what I'm trying to say, suppose that your device is on, then make the combination keys, to quickly power off your device, and pressing rapidly the combination keys to enter to preloader mode, but again, you have to do it BLINDLY, just assuming that your device is on, and after, if no results, the other way around, assuming that your device is off, just do the combination keys, if your device is off, then pressing the three buttons around 10 seconds, then your device can tend to power on, in this short time you have to press, only the two volume buttons and release the PWR button, do you understand? I have bricked my Redmi Note 9 some year ago, and I have really, really bricked my Realme 7, and I recovered this way.
SubwayChamp said:
It's not a matter of time, if after 15 seconds or around, you don't hear something either from your PC or your device, then clearly, it's not working.
What I'm trying to say is, that you have to press all the modes available, PWR + vol. down, PWR + vol. up, both volume buttons, three buttons, all that doing it blindly because you can't see something onto your display, so no sign of life.
To better understand what I'm trying to say, suppose that your device is on, then make the combination keys, to quickly power off your device, and pressing rapidly the combination keys to enter to preloader mode, but again, you have to do it BLINDLY, just assuming that your device is on, and after, if no results, the other way around, assuming that your device is off, just do the combination keys, if your device is off, then pressing the three buttons around 10 seconds, then your device can tend to power on, in this short time you have to press, only the two volume buttons and release the PWR button, do you understand? I have bricked my Redmi Note 9 some year ago, and I have really, really bricked my Realme 7, and I recovered this way.
Click to expand...
Click to collapse
No, i didn't get something, I'm desesperated, you can teamviwer me or something or... I DON'T KNOW
AvZPablo4 said:
No, i didn't get something, I'm desesperated, you can teamviwer me or something or... I DON'T KNOW
Click to expand...
Click to collapse
Not much I can do. I recommended all the best to bypass this. If you have taken it in consideration, then you should sort it out.
- Uninstall all the drivers, reinstall exactly only what you need.
- Be sure that LibUSB is properly installed.
- Install the UsbDK 64 bits installer from the site I linked and try also the mtk-client tool.
- The option Format all except bootloader in SPFT may help, but consider that it may erase your calibration data and IMEI, mainly.