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.
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 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
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
I have managed to brick my Asus rog 3 phone, I have followed all steps outlined here https://forum.xda-developers.com/t/...bricked-asus-rog-phone-3-23-nov-2021.4151443/ to unbrick but none worked, tried different WW versions even cn, it appears that my PC doesn't recognise the device updated Qualcomm drivers PC still shows android device connected, phone stuck in recovery mode every time when started just shows fast boot mode , while following steps everything went smooth until I went to the last bit about installing latest ww version, this gave the result I have now.
Where exactly is the device stuck, i.e what screen does the device land on when you power on? What exactly is the device recognized as on your PC when connected while in bootloader mode? Can you successfully send Fastboot commands to the device? Sounds like you're just soft bricked/bootlooped. Shouldn't need Qualcomm drivers unless you have to mess with EDL which should be the last option.
cutetiger said:
I have managed to brick my Asus rog 3 phone, I have followed all steps outlined here https://forum.xda-developers.com/t/...bricked-asus-rog-phone-3-23-nov-2021.4151443/ to unbrick but none worked, tried different WW versions even cn, it appears that my PC doesn't recognise the device updated Qualcomm drivers PC still shows android device connected, phone stuck in recovery mode every time when started just shows fast boot mode , while following steps everything went smooth until I went to the last bit about installing latest ww version, this gave the result I have now.
Click to expand...
Click to collapse
Hello
I used to have a similar problem with Asus Rog 2.
The solution turned out to be:
- changing the cable to a different one
- complete uninstallation of drivers and reinstallation (not update)
- flashing on a computer that is not overclocked
I also recommend https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/
If you can, please send some pics or log from fastboot. Maybe the phone can be saved.
Regards