I let the battery drain all the way, and it won't charge, neither the screen nor the LED charging indicator light turn on. I've tried holding Volume Down + Power, even holding it for over 2 minutes. When I plug it into my Windows 10 PC, it makes the device connected sound, and it shows up both in Device Manager and Devices and Printers as "Qualcomm HS-USB QDLoader 9008 (COM4)".
I tried googling it and tried following the threads I found, including trying fastboot_edl, but no devices showed when I tried the command fastboot_edl devices. I tried the official Lenovo recovery software, and it never detected the phone.
I also tried what was suggested here, but the blank flash bat file just keeps saying waiting for device. I got the blank flash file here. This was the only download I could find for it, as the link mentioned here seems to have been deleted from the person's google drive.
My phone was running Android 9.0, September 2019 security patch, with Magisk. Any suggestions for next steps? Thank you.
Update: I finally found a fix, using Blank Flash. I couldn't find the file anywhere, until, by chance, I found a reddit post, from over a year ago, and messaged a user who had posted about Blank Flash. I asked them if they knew where to find the Blank Flash files, and they referred me to a Telegram group where they had the files. Said files, Blank Flash files for Moto X4, have been attached to this post. The Telegram group is called @MotoX4_dev.
Related
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..
Hey, Ive tried to install xiaomi.eu rom but didnt realize that i needed the chinese rom and that the global didnt work for this, after ive installed using TWRP the rom, ive rebooted and it just went black, not recovery, not fastboot.
BT was unlocked.
I also see my phone as qualcomm...qloader 9008 when connecting to my pc
Any help?
after having a few heartattacks, ive installed a good Miflsah and a good fastboot rom, and managed to restore my phone to its former glory
no need for further help, but i have a few advices
dont be stupid like me, and listen to directions like theyre the word of god, when they say change from chinese rom to a non official rom, YOU NEED CHINESE, global wont work
and if you're having problems with miflash giving errors, try a bunch of downloads, old, new, everything.
Hi, yet another brick here!
I had an AOSP ROM but I had problems with it. I entered TWRP, downloaded a MIUI official ROM for recovery, wiped the phone from TWRP and decrypting it (there was an option for that). Then I did try to flash the ROM and... black screen. No signs of life.
However, when I connect it to the computer it detects it as the famous Qualcom xxx 9008 (COM10) device. But fastboot is not working, when I type "fastboot devices" it doesn't return anything. ADB doesn't recognize the phone either. Everywhere I saw that I should use MiFlash to recover it, but I took a look at the scripts and are using fastboot to perform the process. But since fastboot doesn't recognize the device, it won't work. I get stuck all the time at "Failed to receive the hello packet".
Fastboot doesn't detect my phone either on Linux or Windows. I tried Linux, virtual Windows 10 (x64) and at last I'm trying on a Windows 10 (x64) computer (no virtualization). No matter what I do, it always stays at the same point. I also used several MiFlash versions (from old builds from last year to the most up-to-date version of XiaomiMiFlash). But since fastboot is not detecting the phone I think there's no point in switching MiFlash versions.
So... what can I do? Should I use the pin short-circuit /deepflash cable method? As of I understand, that is what you use to get into EDL, but if my device is showing 9008 in device manager doesn't it mean that I'm already in EDL? I'm not really sure because all the threads I saw in several forums are a bit messy.
I'll appreciate any help. I don't have phone since 3 days ago and I can survive without it but I need it for my work.
Thank you in advance!
EDIT:
Forgot to say, if I try to power off and power on it doesn't do anything BUT when I plug and unplug from the charger it does show a battery icon with the charged percentage. That's the only sign of life from the phone, aside from being recognized as a 9008 device, but that actually happens when I try to (blindly) get in fastboot mode.
FIXED!!! After four hours testing out several options I found the solution: Open up the phone, unplug the battery cable, plug it again, and voilà. The phone automatically got recognized (again) as Qualcomm 9008 device but this time the flash went on flawlessly. It took less than 5 minutes, once succeeded I powered on the device and it ran into MIUI 8 in less than 5 minutes.
So, if you find issues with the command "fastboot devices", unplug the battery and try it again before troubling yourself with deepcables or shortcircuits ;-D
NOTE: Taking out the back cover is very easy, search on youtube, I bought the thing you need for 1$ at the store next to my home (sorry I don't know what it's called).
So here's my story. I have a Moto X4 phone that I recently rooted and installed LineageOS 15.1 on from this page:
https://download.lineageos.org/payton
I followed the linked installation instructions and everything worked great for a couple days. This morning the 10/23 update came through and I went ahead and installed it. It seemed to take a long time and I had to go to work, but on my way to work I noticed it gave the prompt to reboot which I did. Once at work I found it was completely dead. No lights. Nothing when attempting to charge. Buttons don't do anything. Nothing. I tried plugging into my laptop at home tonight to try adb and nothing there either.
Any ideas on what could have happened to it? I'd think it'd at least light up or show some kind of intro screen. The only thing I can think of is that the thumbprint/pattern protection was on (my work requires it for email access) before installing the update. I know TWRP seems to have issues with this when booting into recovery.
After installing the LineageOS ROM, I also installed GAPPS and the arm64 LineageOS su add-on.
How easy is it to try disconnecting the reconnecting the battery? Or is that not worth a try at this point?
Thanks.
Plug in your laptop, go to device manager in windows and verify if was a "qualcomm device" in the list
I do see a "Qualcomm HS-USB QDLoader 9008 (COM3)" on the list under ports. Is that it?
I was able to download some stuff (some of which I already had installed on my laptop) with the help of this guide:
https://forum.xda-developers.com/showpost.php?p=77905869&postcount=635
That got me a more sound USB connection to my phone, although I still couldn't do anything with my phone at all when plugged in. I then found this:
https://forum.xda-developers.com/showpost.php?p=76942904&postcount=30
This was the magic ticket to blank flash via the linked zip download. I ran the .bat file and it booted right to the bootloader which I then selected recovery. It jumped to the LineageOS recovery screen. I then just chose to start LineageOS and it came right up as normal.
I definitely won't make the mistake of updating LineageOS again though. This version's here to stay now.
SO i feel like a real doofus. I managed to accidentally uninstall the 9008 driver on device manager. I have no access to my device since its stuck in EDL mode and I cant figure out how to get it out of it. I managed find a Qualcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip online but it doesnt work or more likely i am doing something wrong. Ive tried manually selecting the qcser.inf file in the driver selection like some tutorials said but it spat out an incompatibility error at me. I tried using the exe file to install the drivers for me but when i went into select the driver it just wasnt there or it had no affect. Im losing hope. Feel free to ask questions.
UPDATE: Completely draining the battery seems to have taken the phone out of EDL mode. Its charging fine and everything now. The way I drained the phone (relatively) quickly was to place it under a pillow. This kills the phone. No news about the drivers yet.
Hi there, thanks for standing by.
Fast forward. Once installed the image with platform tools and rebooted the device I get the message Qualcomm CrashDump Mode.
Now in Qualcomm Crashdump Mode, it has been listed as " QUSB_BULK_SN: E8AC606F " in the driver manager.
After that, I installed QDLoader HS-USB Driver_64bit and restarted my desktop.
Now in the " device manager " COM and LPT is listed as Qualcomm HS-USB QDLoader 9008 (COM10) the phone is switched off, caption.
Last but not least what I wanted is to unbrick my phone to EU_OxygenOS_10.5.11 through MSM Download Toolv4.0, so I'm doing that and the device is now shut down and can be recognized in the device manager as I mentioned.
Opened MSM, chose Other, and now I'm able to see COM10 on index 1 Connected, selected EU, Sha 256 check, Auto reboot check, and Started. On the first attempt, I get a "Firehose Communication Handshake failed". Was confused and I thought I'm going to unbrick it with no problem, I got mad at this point, and I opened MSM again, after starting it I get "Open Serial Device" and a few moments after that Sahara Communication failed - Waiting for device. After disconnecting the cable and reconnecting it, the device is not shown in MSM nor in COM and LPT ports.
What is missing I'm not sure since I've tried a lot of that.
Any expert tech assistance would be great and appreciate it.
lukegonewild said:
Hi there, thanks for standing by.
Fast forward. Once installed the image with platform tools and rebooted the device I get the message Qualcomm CrashDump Mode.
Now in Qualcomm Crashdump Mode, it has been listed as " QUSB_BULK_SN: E8AC606F " in the driver manager.
After that, I installed QDLoader HS-USB Driver_64bit and restarted my desktop.
Now in the " device manager " COM and LPT is listed as Qualcomm HS-USB QDLoader 9008 (COM10) the phone is switched off, caption.
Last but not least what I wanted is to unbrick my phone to EU_OxygenOS_10.5.11 through MSM Download Toolv4.0, so I'm doing that and the device is now shut down and can be recognized in the device manager as I mentioned.
Opened MSM, chose Other, and now I'm able to see COM10 on index 1 Connected, selected EU, Sha 256 check, Auto reboot check, and Started. On the first attempt, I get a "Firehose Communication Handshake failed". Was confused and I thought I'm going to unbrick it with no problem, I got mad at this point, and I opened MSM again, after starting it I get "Open Serial Device" and a few moments after that Sahara Communication failed - Waiting for device. After disconnecting the cable and reconnecting it, the device is not shown in MSM nor in COM and LPT ports.
What is missing I'm not sure since I've tried a lot of that.
Any expert tech assistance would be great and appreciate it.
Click to expand...
Click to collapse
It sounds like you've corrupted your bootloader. Have you already used this guide? I suggest asking for support there.
I fixed it already, it works with 11.9.9.
@lukegonewild
I have the same error as you -> "Firehose Communication Handshake Failed"
I have tried my main Windows 11 PC and also a Windows 10 machine. It makes no difference.
That's strange, because I remember using the same tool 2 years ago
Can you please tell me how you fixed it?
marcelhdhd said:
@lukegonewild
I have the same error as you -> "Firehose Communication Handshake Failed"
I have tried my main Windows 11 PC and also a Windows 10 machine. It makes no difference.
That's strange, because I remember using the same tool 2 years ago
Can you please tell me how you fixed it?
Click to expand...
Click to collapse
Hi 🖐️
Make sure you install the right drivers for Qualcomm, also you must know that you cannot go for Oxygen 10.5.11, only 11 , you pick which image you would like your phone running from Oxygen 11 releases just remember that you can't go for lower software image like 10.5.11 cause it's not the system settings software. In theory OnePlus is not letting you install earlier releases that are 10 or lower. Respond which image file you're flashing in next reply, if it's the 11.9.9 I'll explain it in the comments section, it's not that complicated.
lukegonewild said:
Hi 🖐️
Make sure you install the right drivers for Qualcomm, also you must know that you cannot go for Oxygen 10.5.11, only 11 , you pick which image you would like your phone running from Oxygen 11 releases just remember that you can't go for lower software image like 10.5.11 cause it's not the system settings software. In theory OnePlus is not letting you install earlier releases that are 10 or lower. Respond which image file you're flashing in next reply, if it's the 11.9.9 I'll explain it in the comments section, it's not that complicated.
Click to expand...
Click to collapse
Thanks for your reply, but I managed to find the problem a few hours later. It was a bad USB-C cable.
Head -> Table