Database Develop

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.

Can't get OTG to work or show up.

So I put this phone away for quite a while, I recently took it out to use with my USB c earpiece from Xiaomi, but it wasn't connecting. So I tried plugging in a USB C Otg thumbdriver, it too did not show up.
I was running Pixel Experience when it had treble support. But given I thought it might be at play for why it's not detected, I wiped and reinstslled miui through TWRP. However after doing that it still didn't work. So I tried to see if TWRP could detect a USB C thumbdriver, it too didn't detect. I resorted to using Mi Flash tool to Flash the stock firmware of Mi Max 2, but still doesn't work.
Anyone know what I could possibly do to get it to work? Thanks

I have a similar issue not same. Similarly my phone stopped detecting usb flash disk on otg. Below is what i did,
To understand if your usb port is malfunctioning, connect your phone to PC and try to communicate through ADB interface. If it goes well than your configuration somewhere deep there sucks (which is my case) or else you have a hardware problem.

kirpi_e said:
I have a similar issue not same. Similarly my phone stopped detecting usb flash disk on otg. Below is what i did,
To understand if your usb port is malfunctioning, connect your phone to PC and try to communicate through ADB interface. If it goes well than your configuration somewhere deep there sucks (which is my case) or else you have a hardware problem.
Click to expand...
Click to collapse
Ah it's okay, I sent it to Xiaomi and got it repaired. Thanks!

kirpi_e said:
I have a similar issue not same. Similarly my phone stopped detecting usb flash disk on otg. Below is what i did,
To understand if your usb port is malfunctioning, connect your phone to PC and try to communicate through ADB interface. If it goes well than your configuration somewhere deep there sucks (which is my case) or else you have a hardware problem.
Click to expand...
Click to collapse
Please advise how did u fix this
Have installed pixel experience oreo rom on mi max 2 and then I noticed org was not working
Please advise

fastboot doesn't react when connect to computer / no device shown

Hello all, I have a strange problem on my xiaomi 8 phone.
Every thing works fine, the phone is BL unlocked, with global rom installed and can be OTA-updated.
Now I want to re-lock the Bl (because of google pay), so I booted to fastboot and the strange thing happens. When I connect to the usb port of my win10 pc, nothing happens, the device manager also show no new device or unknown device. And I als connected to my ubuntu server, dmesg show nothing, and lsusb also show nothing new.
So the issue is, in fastboot mode, my phone seems not be responsed the usb connection. This is boring, because I also accidently replaced the twrp with stock recovery, now I can do nothing on my phone without the fastboot connection.
Any one has an idea or simillar issue and have a solution for it? Thanks in advance.

Zhifu_Yu said:
Hello all, I have a strange problem on my xiaomi 8 phone.
Every thing works fine, the phone is BL unlocked, with global rom installed and can be OTA-updated.
Now I want to re-lock the Bl (because of google pay), so I booted to fastboot and the strange thing happens. When I connect to the usb port of my win10 pc, nothing happens, the device manager also show no new device or unknown device. And I als connected to my ubuntu server, dmesg show nothing, and lsusb also show nothing new.
So the issue is, in fastboot mode, my phone seems not be responsed the usb connection. This is boring, because I also accidently replaced the twrp with stock recovery, now I can do nothing on my phone without the fastboot connection.
Any one has an idea or simillar issue and have a solution for it? Thanks in advance.
Click to expand...
Click to collapse
It sounds like you accidentally relocked the bootloader.
If so you will need to repair the phone in EDL mode by using QPST. There are plenty of how to guides available. You can buy a EDL cable from Amazon
https://www.amazon.com/Baosity-Flas...ds=edl+cable&qid=1552775105&s=gateway&sr=8-11

ADB can't find phone

Greetings,
Yesterday i tried to flash twrp + havoc os, like on my previous phone, but i got stuck right on the begining when ADB says the device wasn't found, I have the phone unlocked, usb debugging allowed, and i can access phones internal storage from windows just fine, entered fastboot and still nothing.
Weird thing is after i entered fastboot the Device Manager changed the name of phone to just "Android"
and driver failed to install, then i tried to search the driver with windows built in driver search, and driver was sucesfully installed, but the phone still can't be found by ADB. Really don't know which can be the cause. I have win 7 by the way. Hope somebody can help me with my problem, i appreciate any tips.
Thanks and have a great weekend

ElectroYume said:
Greetings,
Yesterday i tried to flash twrp + havoc os, like on my previous phone, but i got stuck right on the begining when ADB says the device wasn't found, I have the phone unlocked, usb debugging allowed, and i can access phones internal storage from windows just fine, entered fastboot and still nothing.
Weird thing is after i entered fastboot the Device Manager changed the name of phone to just "Android"
and driver failed to install, then i tried to search the driver with windows built in driver search, and driver was sucesfully installed, but the phone still can't be found by ADB. Really don't know which can be the cause. I have win 7 by the way. Hope somebody can help me with my problem, i appreciate any tips.
Thanks and have a great weekend
Click to expand...
Click to collapse
Sounds like the fastboot drivers are missing. I'm sure you can find the drivers if you google it or just download the mi flash tool and install the drivers from there. Test the type c as well maybe the cable has the problem (try to use the official one), test it from a different usb, or an other PC or laptop if you have any.
I had similar issues before using mi flash tool, I tried on my other laptop and was working fine.

Thank you for your advice, it was due to drivers, but now im struggling with some very weird problem, i managed to flash twrp, and installed havoc (later tried lineage) succesfully, but when i boot the phone, it boots into fastboot instead of android for some reason, i tried installing the rom several times, everytime succesfully, deleted dalvik cache and so on.. Its just booting to fastboot for some reason.

Mi 5 stuck on black Mi screen

Hello everybody,
To explain things a bit better than just this title. I have a Mi 5 that was working smoothly for quite a long time. Had a modified MIUI ROM flashed on it with many specific apps such as xposed, Magisk and also TWRP. However, my GPS has turned completely dead for some months. Couldn't use it anymore. After some researches, I found out it could be software related. So I decided to flash a new ROM (AOSP Extended) to see if that could fix the GPS issue.
First I backed up the whole system via adb on my laptop and then wiped the whole system. It turns out after trying to flash the AOSP ROM, I came across a message saying I should have MIUI 8.1.30 or older. Or something like that... Can't remember exactly. Just read that I was supposed to update my ROM to a newer stock ROM to be able to flash AOSP in a second time. I did a lot of different operations and I can't remember them all but it turns out one moment, adb started to flash a ROM because the adb command line was saying it. But it failed. Aftert that moment, my phone definitely got bricked. I have no clue what exactly happened, it's kind of confused...
Currently, the phone is always displaying dark screen with mi logo and "unlocked" mention below. Power and volume up will just reboot it to the same state (meaning twrp is not longer installed or accessible). In this dark screen mode, plug the phone to a computer will do nothing, it's not even detected in devices manager. On the other side, power and volume down will boot the phone into fastboot mode, the computer beeps when I plug the USB cable and I can briefly see the Android device with a yellow warning in the dev manager. But after something like 20 seconds, fastboot mode goes off and phone restarts on black MIUI screen.
I've tried to install Google drivers, Qualcomm drivers and did numerous actions but the phone isn't detected anymore. Also, tried to type command "adb devices" in the short time when the phone is detected by computer in fastboot but it shows an empty list. I'm pretty desperate, seems I've tried anything and I've no ideas now... Just saw there is possibly a hardware fix which requires to dismount the back of the phone. Not sure what it does but I'll try it out if no other solution shows up...
Any idea is welcome ! Thanks

Well, looks like my thread wasn't so popular Finally found a workaround after nearly 8 hours searching for a fix. Thought that might help anybody else having the same struggle as mine. What I can tell is that it's not related to the computer used since I've made the same operations on 3 different computers, same problem for each of them. In fact, there were two problems :
First the bootloader not remaining more than 30 seconds. To stop this, I had to open the devices manager and as soon as the Android device would appear after turning it into Fastboot, I would right click on the visible device (appearing with an exclamation mark) and update manually the driver following the process that is described in many topics (locate the Google Android devices USB drivers that I downloaded right before). The time is quite short so you have to be pretty fast, otherwise, the MI 5 would disappear, forcing you to do the fastboot mode operation again. I have to say that doing it without the device being recognized is not working. So if you install with the legacy driver option, it's not going to be associated directly to the device. At least, not in my case.
Once I had done this, the Fastboot mode would remain on. I found my way pretty fast until that moment but the problem was adb wouldn't detect my device. Typing "adb devices" command would return no result, no matter what I did. Strangely, installing an old version of MiFlash (last ones gave me error) would help the computer to detect the device. I don't know why, possibly because the drivers are better ? Anyway, MiFlash helped me to access the phone and Flash a new ROM. Usually, I was just using adb and it would do the job but this time not.
Hope it can help !