Database Users

Bricked Mi A1 - Qualcom HS-USB Diagnostics 900E

Hi guys
At first - I tried a method given on this forum: https://forum.xda-developers.com/mi-a1/help/phone-goes-to-qualcomm-hs-usb-qdloader-t3757867
This method doesn't work for me, because after disconnect my PC doesn't recognize my phone.
Phone is in Qualcom HS-USB Diagnostics 900E mode after OTA update (Mi A1 April Update) - strange
So guys... I know there are some magicians who can do almost everything.. Any ideas what to do?

Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,

To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screwdriver.
I did NOT have success with deep flash cable myself, I had to use testpoint method (and sadly broke my LCD in the process). The deep flash issue might of been because I was in Windows 10 x64 or on a USB3 port. If you do go that route and can't get it working, try with a Windows 7 x86 VM and USB2 passthrough mode before last resort of taking device apart.

Hold power button for 20 sec then volume down and fastboot will apear

1. install all necessary drivers (adb, qualcomm's HS-USB Diagnostics 900E, xiaomi flash tool)
2. use test point method as suggested by @CosmicDan - lots of tutorial on web on how to do this. Carefully read this before actually attempting it.
3. When you successfully do the test point method you will hear the device recognized sound on your computer
4. when you hear it, open miflashtool and your device should show up in it.
5. if not, reboot your PC. You should reboot your PC after installing all the drivers. See #1. (reboot required)
6. Once you successfully see your device on miflashtool, you can flash the fastboot rom of your choice.
7. (you might get stuck on "Can't receive hello packet" dialogue which will prevent your device from flashing), in that case change the USB port, possibly to USB 2.0 and try the test point flash method again to get detected and try flashing again.
8. Test point method should be done everytime you disconnect the USB from your phone and computer, hopefully you only need to do it twice.
9. Sadly for me, I am still unable to flash stock roms with this method, my problem is kind of unique, after flashing it shows me "Your phone is destroyed, press power to turn off" dialogue. lmao
10. if you get the same message then you dun goof'd. Hopefully yours will successfully flash.
Oh and only one version of fastboot ROM actually revives the phone, other fastboot roms actually puts it to coma (vibrating every one second, no display, no nothing). Only one fastboot ROM allows me to go to fastboot and flash recoveries. But if I flash any ROM (stock or custom) it kills the phone again and I have to repeat the given method and try again with another rom. I think the phone is effectively dead. What a **** phone! lol

udaan said:
1. install all necessary drivers (adb, qualcomm's HS-USB Diagnostics 900E, xiaomi flash tool)
2. use test point method as suggested by @CosmicDan - lots of tutorial on web on how to do this. Carefully read this before actually attempting it.
3. When you successfully do the test point method you will hear the device recognized sound on your computer
4. when you hear it, open miflashtool and your device should show up in it.
5. if not, reboot your PC. You should reboot your PC after installing all the drivers. See #1. (reboot required)
6. Once you successfully see your device on miflashtool, you can flash the fastboot rom of your choice.
7. (you might get stuck on "Can't receive hello packet" dialogue which will prevent your device from flashing), in that case change the USB port, possibly to USB 2.0 and try the test point flash method again to get detected and try flashing again.
8. Test point method should be done everytime you disconnect the USB from your phone and computer, hopefully you only need to do it twice.
9. Sadly for me, I am still unable to flash stock roms with this method, my problem is kind of unique, after flashing it shows me "Your phone is destroyed, press power to turn off" dialogue. lmao
10. if you get the same message then you dun goof'd. Hopefully yours will successfully flash.
Oh and only one version of fastboot ROM actually revives the phone, other fastboot roms actually puts it to coma (vibrating every one second, no display, no nothing). Only one fastboot ROM allows me to go to fastboot and flash recoveries. But if I flash any ROM (stock or custom) it kills the phone again and I have to repeat the given method and try again with another rom. I think the phone is effectively dead. What a **** phone! lol
Click to expand...
Click to collapse
Did you do factory flash mode? That's the only one that can recovery it, the other scripts won't flash everything.
Note that because you didn't backup partitions you will also wipe the IMEI, or so I've read (I backed up my whole device via emmcdl before brick so I was able to recover fine without miflash)

CosmicDan said:
Did you do factory flash mode? That's the only one that can recovery it, the other scripts won't flash everything.
Note that because you didn't backup partitions you will also wipe the IMEI, or so I've read (I backed up my whole device via emmcdl before brick so I was able to recover fine without miflash)
Click to expand...
Click to collapse
Actually I think I got scammed. It is Mi5x sold as MiA1. ****ing chinks! Anyway, I managed to install (Tiffany) on it and now it is booting to boot logo and bootlooping. I can get to fastboot and default (MIUI's) recovery by pressing button combos. But OEM is locked now so I cannot flash TWRP or other ROMs in it. I will have to EDL flash back to that MIA1 ROM to get it unlocked from fastboot. Otherwise MIUI unlocker asks me to link my miui account to this phone by going to settings, which I can't do because it is not booting up.
funny situation.

Bruce666 said:
Hi guys
At first - I tried a method given on this forum: https://forum.xda-developers.com/mi-a1/help/phone-goes-to-qualcomm-hs-usb-qdloader-t3757867
This method doesn't work for me, because after disconnect my PC doesn't recognize my phone.
Phone is in Qualcom HS-USB Diagnostics 900E mode after OTA update (Mi A1 April Update) - strange
So guys... I know there are some magicians who can do almost everything.. Any ideas what to do?
Click to expand...
Click to collapse
Facing The same Issue
---------- Post added at 10:42 AM ---------- Previous post was at 10:35 AM ----------
Phone Showing Charging Only
Can't Even Transfer Data
Not Detected on Pc

udaan said:
1. install all necessary drivers (adb, qualcomm's HS-USB Diagnostics 900E, xiaomi flash tool)
2. use test point method as suggested by @CosmicDan - lots of tutorial on web on how to do this. Carefully read this before actually attempting it.
3. When you successfully do the test point method you will hear the device recognized sound on your computer
4. when you hear it, open miflashtool and your device should show up in it.
5. if not, reboot your PC. You should reboot your PC after installing all the drivers. See #1. (reboot required)
6. Once you successfully see your device on miflashtool, you can flash the fastboot rom of your choice.
7. (you might get stuck on "Can't receive hello packet" dialogue which will prevent your device from flashing), in that case change the USB port, possibly to USB 2.0 and try the test point flash method again to get detected and try flashing again.
8. Test point method should be done everytime you disconnect the USB from your phone and computer, hopefully you only need to do it twice.
9. Sadly for me, I am still unable to flash stock roms with this method, my problem is kind of unique, after flashing it shows me "Your phone is destroyed, press power to turn off" dialogue. lmao
10. if you get the same message then you dun goof'd. Hopefully yours will successfully flash.
Oh and only one version of fastboot ROM actually revives the phone, other fastboot roms actually puts it to coma (vibrating every one second, no display, no nothing). Only one fastboot ROM allows me to go to fastboot and flash recoveries. But if I flash any ROM (stock or custom) it kills the phone again and I have to repeat the given method and try again with another rom. I think the phone is effectively dead. What a **** phone! lol
Click to expand...
Click to collapse
Im sorry, exactly with which ROM did you get to the fastboot?

Press power button for 15 sec
If you feel vibration then you are so lucky

boshell said:
Im sorry, exactly with which ROM did you get to the fastboot?
Click to expand...
Click to collapse
Fastboot rom for Mi5x because the phone is Mi5x.

Stuck in rescue mode after tried flashing stock firmware

Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.

Did you managed to fix this?

Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!

ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).

Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.

Bricked phone, won't turn on/fastboot/recovery

So yeah, I screw up by a lot, but let's see if someone can help me/
I tried to update twrp on my phone and it got bricked, ADB was not seeing the device but Mi FlashTool was with a code but not COM, tried changing the phone drivers brom 900E to QL8000 and it got registered by MiFlashtool as COM and another code, the phone was still showing there even if I could not make the phone go to fastboot mode, just blackscreen; I tried to reinstall stock rom with it but got stuck at "flashing", disconnected the phone, the phone was still bricked in a black screen, when trying to reconnect the phone again to the pc, Win10 now displays an error
https://imgur.com/a/VS1yh6t
,
https://imgur.com/a/4PxUD7E
, I already tried uninstalling the device, deleting and reinstalling the drivers (unable because for some reason they won't appear now, but already tried installing the from their 1st party and prom MiFlashTool), so the phone won't turn on, display anything, go into recovery/fastboot, and I don't know what to do now, is the phone lost? I hope you can help me with this issue.

Hello Bro. Try install latest Mi Flash Tool latest version and then install the drivers. For my it's works in windows 10.

Bricked Lenovo Tab M10 fhd plus while trying to downgrade, any advice?

Hi,
I'm not sure I'm posting in the right section but, I had a really bad experience upgrading to android 10. Really sluggish and slow... so I tried to downgrade to android 9 by using Lenovo's Rescue and Smart Assistant.
What I did, is to find the stock ROM for my model, and replace the files downloaded by the Rescue Assistant (which downloaded the latest firmware). The process went through, but now the device wont power on.
When I plug in the USB, windows makes a sound, the charging light comes on, but The rescue Assistant nor SP flash tool is able to flash the latest firmware.
Is it bricked for good?
Model : TB-XF606F
Hardware number : 60

Maybe your computer doesn't recognize your tablet. Did you ever try using sp flash tool with your tablet before? You can try reinstall or install a driver for your table if you haven't done it yet.

Well the tablet is recognized as the "mtk vcom..." in device manager. I guess it is the driver that the lenovo rescue app installed.
I have never used sp flash tool with my tablet, just the lenovo rescue.
I tried on 2 different pc and it is the same thing. I think the problem is that I can't turn off the tablet properly, even though, all I can see is a black screen.
I will try to drain the battery by keeping the power button pressed with some scotch tape. I don't know what I can do else.
Edit: I tried a few other times with flash tool using different setting for the connection (with battery and full speed) and nothnig happened. But now windows says it does not recognize my tablet.

did the same thing exactly. . bricked lenovo m10 fhd plus x600v after i flashed a downgrade version. dont try to downgrade this thing. i had already flashed it with 3 or 4 versions the same way , but when i chose to flash the oldest version available with the model , this tab got completly unresponsive , no feedback when try to boot into recovery, fastboot, or system . neither does it gets recognised in windows or anything - device manager dowsnt recognise this usb device ( in device manager properties comments it reads- USB\DEVICE_DESCRIPTOR_FAILURE). if you find a way to reflash the device please let us know. good luck .

Bricked mine after being completely running smoothly on Lineage, then was messing around trying to get gapps installed and jacked up the partitions. TWRP said no OS. Kept messing around and mistakenly locked the bootloader again with apparently an unverified boot partition. . I couldn't get SP Flash tool to work ever either. Pretty sure it's a door stop now.

[solved]Bricked my OP6t on A11 while tinkering, stuck in boot loop (?hard bricked), windows 7 doesn’t detect Device as Qualcomm device

I was on A11.1.1.1 , when I decided to root my device. Tried to install Twrp but failed, then unlocked boot loader and flashed magisk using Adb from my windows 7 desktop. Phone restarted, went into bootloop, then restarted naturally - however I couldn’t turn on Wi-Fi. Downloaded SuperSU, which showed device was rooted. In an attempt to revert back to stock os, I flashed another boot image, and phone went into continuous boot loop. So I searched the web and downloaded Qualcomm hs-usb QDloader 9008, and MsmDownload tool v 4.0 in an attemp to unbrick my device and installed them. However, my desktop doesn’t recognise my phone as Qhusb_bulk or as Qualcomm qhusb qdloader9008 in devicemanager. So I m unable to use the MSM tool to un brick my phone. Tried reinstalling the drivers on desktop , but the phone doesnt show up on device manager still. Only shows up as “pci simple communications controller” under other devices.
When i turn on my phone, it shows the OP logo going round and round for 5mins, then the screen goes blank. If I keep the power off button pressed for quite sometime, phone restarts into boot loop again. Can’t get into boot loader, nor does adb on my desktop recognise the device.
i m at my wits end as to how I m gonna unbrick my phone, as this is my primary phone. Kindly guide me step by step as to how to unbrick my OP6t. Any help is appreciated.

Jeet77 said:
I was on A11.1.1.1 , when I decided to root my device. Tried to install Twrp but failed, then unlocked boot loader and flashed magisk using Adb from my windows 7 desktop. Phone restarted, went into bootloop, then restarted naturally - however I couldn’t turn on Wi-Fi. Downloaded SuperSU, which showed device was rooted. In an attempt to revert back to stock os, I flashed another boot image, and phone went into continuous boot loop. So I searched the web and downloaded Qualcomm hs-usb QDloader 9008, and MsmDownload tool v 4.0 in an attemp to unbrick my device and installed them. However, my desktop doesn’t recognise my phone as Qhusb_bulk or as Qualcomm qhusb qdloader9008 in devicemanager. So I m unable to use the MSM tool to un brick my phone. Tried reinstalling the drivers on desktop , but the phone doesnt show up on device manager still. Only shows up as “pci simple communications controller” under other devices.
When i turn on my phone, it shows the OP logo going round and round for 5mins, then the screen goes blank. If I keep the power off button pressed for quite sometime, phone restarts into boot loop again. Can’t get into boot loader, nor does adb on my desktop recognise the device.
i m at my wits end as to how I m gonna unbrick my phone, as this is my primary phone. Kindly guide me step by step as to how to unbrick my OP6t. Any help is appreciated.
Click to expand...
Click to collapse
When you get it to reboot did you try holding volume down as it starts? Should get you into recovery then bootloader.

Also get magisk to root rather than SuperSU. You can install twrp from magisk in oos with the correct installer but first you have to root correctly with modded boot.img. Can make your own or get from the one post in here. I'd suggest getting the newest oos also.

Brettroth said:
When you get it to reboot did you try holding volume down as it starts? Should get you into recovery then bootloader.
Click to expand...
Click to collapse
Probably need to flash a stock boot of 11.1.1.1 to unbrick. You can try booting to the newest twrp from fastboot I'm not sure if it works anymore.

Brettroth said:
Probably need to flash a stock boot of 11.1.1.1 to unbrick. You can try booting to the newest twrp from fastboot I'm not sure if it works anymore.
Click to expand...
Click to collapse
Couldn’t fastboot into twrp, since device got corrupted while trying to flash multiple things. Thankfully while tinkering, my desktop recognised my device as qhusb qloader 9008, and all I had to do was boot my device into edl mode (which was also a pain tbh!). After trying numerous key combinations and timing it perfectly, device booted into edl and I could use the msm download tool to unbrick my device. Now device has rebooted into iOS 10.3.5 (same version as msm tool version) and I have somehow breathed a huge sigh of relief that my device could be resuscitated. Will be updating to 11.1.1.1 now (I see the latest is 11.1.2.2) and setting up my device now.
Thank you a lot for looking into my issue and suggesting solutions. In my younger years, I was a technology enthusiast and often rooted/flashed, but have pursued medicine since then. Now am out of touch completely to the tech scene and it was a grave blunder on my part to have used my primary driver to try and root/flash again.
Have a great day, my friend and please know that it means a lot to me to have received help from the community.

Jeet77 said:
I was on A11.1.1.1 , when I decided to root my device. Tried to install Twrp but failed, then unlocked boot loader and flashed magisk using Adb from my windows 7 desktop. Phone restarted, went into bootloop, then restarted naturally - however I couldn’t turn on Wi-Fi. Downloaded SuperSU, which showed device was rooted. In an attempt to revert back to stock os, I flashed another boot image, and phone went into continuous boot loop. So I searched the web and downloaded Qualcomm hs-usb QDloader 9008, and MsmDownload tool v 4.0 in an attemp to unbrick my device and installed them. However, my desktop doesn’t recognise my phone as Qhusb_bulk or as Qualcomm qhusb qdloader9008 in devicemanager. So I m unable to use the MSM tool to un brick my phone. Tried reinstalling the drivers on desktop , but the phone doesnt show up on device manager still. Only shows up as “pci simple communications controller” under other devices.
When i turn on my phone, it shows the OP logo going round and round for 5mins, then the screen goes blank. If I keep the power off button pressed for quite sometime, phone restarts into boot loop again. Can’t get into boot loader, nor does adb on my desktop recognise the device.
i m at my wits end as to how I m gonna unbrick my phone, as this is my primary phone. Kindly guide me step by step as to how to unbrick my OP6t. Any help is appreciated.
Click to expand...
Click to collapse
This happen to me several times and the first time it happened I thought my phone would not be unbricked after numerous attempts with the msm tool!
My issue was that my phone was a renewed amazon phone and amazon listed it as a unlocked international but it actually was a t-mobile variant and when i downloaded the correct msm tool with firmware it worked!
You need to get the phone into edl mode. For edl, when phone off press both volume buttons and plug in the usb while connected to your pc and the qualcom driver should pop up in device manager. After that finding the right msm firmware will be your next issue but with enough searching you should find it!
Let me know your progress with the driver and I can try and post some links to different msm firmware for the oneplus 6t!