Hard bricked device detected by computer as QComm HS-USB Diag 9091 - Xiaomi Redmi 4X Questions & Answers

My redmi 4x, running the official build of AOSP Extended, suddenly shutdown during normal usage.
The device is now unresponsive to all button presses, and all keypress combinations do not work.
When connected to the original charger, the device heats up, just as per normal charging, although the display remains dark and the LED does not light up.
However, when plugged into my computer, the device is detected as 'Qualcomm HS-USB Diagnostics 9091 (COM3)'. All my searches have returned solutions that work for other 90__ codes, but none for 9091.
Does anyone have a possible solution to this? Thanks in advance for your assistance!
Some other information that may be of assistance:
The device was running the AOSP Extended 20180510 official build.
TWRP is installed and the device is rooted.
The device does not boot AT ALL. Not to system, not to recovery, and not to fastboot.

Related

Softbricked Phone Battery Too Low for RSD Lite, Won't Charge

I have searched around for a couple days, but there doesn't seem to be anyone who has posted about this issue with a Droid 4. So here is what I have.
I rooted my Droid 4 using the RazrBlade method without incident. Afterwards I wanted to flash Cyanogenmod onto it, but did not have a custom recovery like ClockworkMod or TWRP set up yet. So, looking around led me to download the latest safestrap .apk so I would have a recovery capable of flashing Cyanogenmod. The latest version of safestrap would not work for me because of a parsing error, I looked around and found that some people were having the same issue and fixed it by downloading an earlier version of safestrap to their Droid 4. So, I found a safestrap 2.x.x version, downloaded that and followed the directions accordingly. I now had a functional (to my knowledge) recovery that would allow me to flash CyanogenMod. So I downloaded the .zip file from the CyanogenMod website for Droid 4, and attempted to flash it using the recovery that safestrap 2.x.x set up.
Everything looked okay for the install, no errors were reported, phone was at least at 80% battery, but once the phone rebooted, after the Motorola spash screen, there was a blank screen. The phone is on, evidenced by the backlight being visibly seen, but otherwise there is no evidence that it is trying to boot up any ROM. There is no loop whatsoever, just a blank screen.
First, I thought it was a bad install, afterall, it wouldn't be the first time. But when I turned it off (only possible via PWR&Vol.- button combo) it did not give the option to go into the safestrap recovery mode upon booting back up.
But I am not without a working knowledge of how to pull a phone out of a softbrick state, so I quickly connected my phone to a computer set up to take adb commands and tried to reboot my phone into the recovery mode. I connected my phone to my PC, left it on the blank screen mode and typed the adb command [adb devices] to confirm that it was acknowledged by my computer, it was, and attempted to reboot it into the recovery mode with the command [fastboot reboot-recovery]. It responded by rebooting, but led back to the backlit blank screen. I thought that this might be an issue with the wires or drivers or something to that effect, so I reattempted with a usb cord that was supplied by Motorola, and reinstalled all the appropriate drivers. Nothing worked, so I moved everything to a new computer freshly set up to take adb commands. I connected my phone and it was immediately recognized by the new computer, but it still would not respond to any adb commands. Attempting to reboot into recovery yields a blank screen still.
By this point I do not care if my phone is rooted or if I have to restore it to factory settings. So I look up solutions that flash it back to the stock 4.1.2 ROM. I find one that does this, but it requires that I am in AP Fastboot Flash Mode. I put it in the aforementioned mode, but it is not recognized by the adb terminal. It is listed as an adb device if it is in "blank screen mode" but not while in AP Fastboot Flash Mode. Shortly after this the battery is too low to program anyway, so I turn it off and set it to charge. But instead of a "battery charging" screen, I am greeted with the Motorola splash screen for as long as the phone is connected to the charger. Every time the phone is removed from the charger it, immediately and without pause, loses power and cannot be powered on until placed back on a charger.
Looking around some more, because I am increasingly desperate to solve this problem, I find something called RSD Lite, which will reflash the stock firmware to the phone and it will behave as if it was reset to factory settings. I plug the phone up to the computer, it powers on, I boot it up to the AP Fastboot Flash Mode and RSD Lite sees the phone as a fastboot device, and is ready and willing to fix it, but the battery is too low to program.
The battery is incapable of being charged by a wall outlet by any means that I have tried (will list below), BUT... If I connect my phone to a computer, and after the phone is connected, turn the phone off, a little green LED light appears at the top left and stays for at least 15 minutes until the Motorola splash logo appears and my phone connects to the computer. The phone recieves power in this mode evidenced by the fact that it does not instantly power down after it is disconnected from the power source. But at this point in time, the battery does not charge enough to cause a change in the AP Fastboot Flash Mode to allow it to be OK to Program.
Here is some misc info that might be needed:
Modes that I have access to
1.) Motorola Splash Screen + "Blank Screen Mode": This mode connects to the computer and is registered by the device number XT894. After the Moto Splash Screen there is a backlit blank screen I call "Blank Screen Mode". This mode is recognized by adb commands but not by RSD Lite. Any time an adb command is used apart from rebooting, command prompt says <waiting for device> and the device does not respond.
2.) Motorola Splash Screen Only: This mode is only accessible by connecting the phone to a wall outlet. This mode does not charge the phone and if the phone does not have any power otherwise, will power down without warning upon being disconnected from the power source.
3.) Boot Mode Selection Menu: This mode provides various options that appear to do nothing. The "Recovery" option that is supposed to bring me to the default android recovery mode instead brings me to the Motorola Boot Logo and then to a green android laying down with a red triangle over it (with an exclamation point). I am able to access AP Fastboot Flash Mode from here.
4.) AP Fastboot Flash Mode: In this mode, the device is recognized by the computer as an adb fastboot device (not as an XT894 device). It does not respond to adb commands, and the adb terminal does not acknowledge the phone in this mode. RSD Lite does acknowledge the phone in this mode, but trying to begin the process to reflash the stock firmware causes the "Low Battery/ No Program" text on the phone to flicker and result in a failure in the RSD Lite program. It lists the reason as: Phone return(ed) Fail.
5.) Computer Charging Mode: When connected to a computer, and immidiately powered off, a green LED light turns on. After leaving the phone for some time, the phone can be disconnected and stands on it's own power without needing to be connected to a power source to remain on. In this mode, the screen is not on, and the phone is not recognized by the computer at all.
Methods I Have Attempted to Use to Charge Phone
1.) Plugging Moto Stock USB charging cable to computer and leaving it: This causes the 1st mode listed above to occur, and no charge is held. After 10 minutes of "charging" upon disconnecting cable, phone shuts off abruptly, and without any warning.
2.) Plugging Moto Stock USB into USB to Wall Outlet Plug: This causes 2nd Mode listed with similar results to above.
3.) Plugging Motorola Wall Outlet Charging Cable to Phone: See above
4.) ALL Above Methods + Boot Mode Selection Menu BD Tools Mode: I read that if you were to connect your phone to a wall outlet after booting it up into the Boot Mode Selection Menu, and selecting BD Tools, the phone would boot up to the Motorola Boot Logo screen, then show a battery charging similarly to how one does if you charge your phone after it shuts down from having 0% Battery. This was not the result I received. Similar results to #1
I apologize if there is some blatant simple answer here, but I have looked everywhere to find a solution to no avail. I included everything that occured between then and now so as to facilitate this process, and hope that I am not stepping on any toes with the wall of text I just posted.
Thanks in advance, if more info is needed (or if the post needs to be formatted in an easier to read way) just say so.
Sounds like you will need a motorola factory cable. I think that's what they are called. It provides power directly to the phone allowing you to fastboot. I know you can find them on ebay. I believe team black hat also sells an adapter to turn your regular OEM cable into a factory cable.
Your other alternative would be to sacrafice a usb cable and attach to the battery terminals directly to charge the battery. If you google it you should be able to find directions for how to do this. I believe someone posted a how to on youtube for the razr which should give you a good idea of what you would be getting into.
Good luck!
Droid 4 - Avatar
Fixed It
Thanks for the help.
I didn't feel like paying $12 dollars and waiting several days to purchase one of those special factory cables, so I ended up taking a non-USB charger, spicing it, and hooking it directly to the battery terminals like you said. After I did that, it automatically said that it was "OK to Program".
The only problem I had was that RSD Lite wasn't able to fix it, I had to download some other app that ran things through command prompt while the device was in AP Fastboot mode. But the end result was the same.
I found out that the problem that caused all this was me not flashing the CyanogenMod firmware into ROM Slot-1 while in the safestrap recovery mode. I flashed it to the "Stock" ROM Slot instead.
Thanks again for the help, I learned a lot, and I am glad I didn't have to shell out money for a new phone. :laugh:

Phone won't turn on after update

I accidentally deleted my phone OS using TWRP.
So, I fixed this and installed stock android firmware for my device and locked the bootloader.
It was all set up nicely. Then, I decided to update to the latest android version and now it showed the updating logo and everything and the screen suddenly went black and it won't show anything.
I have tried holding power and volume down for 2 minutes but have had no luck.
I have tried charging with many USB cables.
When I plug a USB cable into my phone and computer, I get the error message "USB Device Not Recognized".
Please help me fix this error and help me to get my phone working again, thank you in advance.
You broke the bootloader, this can be solved if Moto releases the blankflash files, however motorola has no idea in releasing those files. get some other mobile, no other alternatives as of now.
Jon_6 said:
I accidentally deleted my phone OS using TWRP.
So, I fixed this and installed stock android firmware for my device and locked the bootloader.
It was all set up nicely. Then, I decided to update to the latest android version and now it showed the updating logo and everything and the screen suddenly went black and it won't show anything.
I have tried holding power and volume down for 2 minutes but have had no luck.
I have tried charging with many USB cables.
When I plug a USB cable into my phone and computer, I get the error message "USB Device Not Recognized".
Please help me fix this error and help me to get my phone working again, thank you in advance.
Click to expand...
Click to collapse
Sorry Bro, you've completely bricked your phone. Even if Motorola releases blank flash files for Moto G 2 Titan, your mobile should be detected as "Qualcomm HS-USB Qdloader 9008". But as you mentioned that when you connect your phone with PC, it shows USB DEVICE NOT RECOGNISED, so there is nothing you can do now. Try giving it to service centre see if they can help
pkdon123 said:
Sorry Bro, you've completely bricked your phone. Even if Motorola releases blank flash files for Moto G 2 Titan, your mobile should be detected as "Qualcomm HS-USB Qdloader 9008". But as you mentioned that when you connect your phone with PC, it shows USB DEVICE NOT RECOGNISED, so there is nothing you can do now. Try giving it to service centre see if they can help
Click to expand...
Click to collapse
Thank you for your reply. I tried plugging my phone into my PC again after leaving it for a while and charging it for a few hours. Now, it shows as Qualcomm HS-USB Qdloader 9008 as you said. For some reason, it wasn't recognised last time I connected my phone to my computer.
Karthik_pm said:
You broke the bootloader, this can be solved if Moto releases the blankflash files, however motorola has no idea in releasing those files. get some other mobile, no other alternatives as of now.
Click to expand...
Click to collapse
Thank you for your answer, in the meantime, I'll just buy a cheap SIM-free phone that is in my Moto G.
I may as well use that and when my contract is finished, buy a new phone.
Jon_6 said:
Thank you for your reply. I tried plugging my phone into my PC again after leaving it for a while and charging it for a few hours. Now, it shows as Qualcomm HS-USB Qdloader 9008 as you said. For some reason, it wasn't recognised last time I connected my phone to my computer.
Click to expand...
Click to collapse
Well That's A Good News But I've Tried Searching Blank Flash Files on Google, Unfortunately I'm Unable To Find The Files For TITAN, The Files Available Online Are for Moto G FALCON, Which Wont Work Here..

Bricked Xiaomi MI5

Hello everyone.
Yesterday while i was trying to install a new rom in my MI5 I bricked my phone.
I wiped the system, data, cache and kernel cache, then, as a mistake I rebooted my phone and all of a sudden it turned black and I couldn't go to the recovery or fastboot.
Now the phone is just black, no response trying to boot or go to recovery\fastboot. When I put to charger theres no LED LIGHT.
So I installed the adb drivers, installed MiFlash, and the computer recognized the phone as QualComm HS-USB QDLoader 9008 COM4.
Then I installed a fastboot rom into the phone using MiFlash, it said flash done and successful.
But, it keeps freezed in a black screen.
Should I just wait for a miracle or theres another option?
My PC still recognizes the phone as QualComm HS USB QDLoader 9008 COM 4.
Thanks in advance.
// EDIT (SOLVED)
Ok so now it booted with the fastboot ROM I flashed.
As I see, after the flash it takes hours to boot. I just went home, dropped the phone in the bed, then I pressed Vol up+Vol down and power button at the same time for two minutes and worked.

MIPAD 4 Plus BRICKED

Hi everyone, I have a problem with my MIPAD 4 Plus, without any reason it stopped working, I can't turn it on, the charging screen or the LED does not appear, it was with the original Chinese firmware and without a custom recovery, when connecting to the PC it detects it as ''Qualcomm HS-USB QDLoader 9008'', so I think it is a system problem.
I was looking for information and only found that maybe the bootloader is damaged.
Could anyone help me please?

HTC One m7_UL Hard brick or battery change?

The device does not turn on, by connecting to the current it starts charging as in the picture, with the red LED flashing, then it turns off. If I try to turn it on (always under charge), it gets to the HTC logo then it turns off, if I press power + vol- the bootloader starts, but selecting any option remains blocked.
I connected it to the computer with windows 10 and it detects QHSUSB_DLOAD. I searched the forum and found this:
[UNBRICK][BETA] HTC Unbricking Project
OP status: [WIP] This will fix devices which were bricked due to firmware incompatibility. This can be caused with the way HTC handles the firmware updates in it's m7's OTAs. If you've been flashing from a 3.x firmware to a 5.x firmware via OTA...
forum.xda-developers.com
so i tried to use ubuntu 12.04.05, but it gave as result: 9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
My question is: can the battery be completely discharged, (I have been using it for 6 years) and then replace it, or is it another problem?
Looking at the bootloader O.S disappeared, why?
Thanks for your attention and sorry for the English.

Categories

Resources