I have a Moto G 2015 installed the ROM CyanogenMod 12.1 it. I went back to the original, made all commands after restarted the device did not call more. I can not even access the Fastboot Flash Mod screen. The computer recognizes the phone driver as Qualcomm HS-USB qdloader 9008. Help me please!
This happened to me with moto g 1st Gen. Did u restore thru a nandroid backup? The solution for me was to reinstall the oem firmware thru the bootloader. But if I understand u correctly, u can't even get the bootloader screen, right?
I would recommend you to go back to cm12.1, make sure debugging is on and try and see if your computer is able to recognize the phone. If that happens then reinstall the oem firmware.
Sent from my MotoG3 using Tapatalk
LucasAway said:
I have a Moto G 2015 installed the ROM CyanogenMod 12.1 it. I went back to the original, made all commands after restarted the device did not call more. I can not even access the Fastboot Flash Mod screen. The computer recognizes the phone driver as Qualcomm HS-USB qdloader 9008. Help me please!
Click to expand...
Click to collapse
Also try removing the Qualcomm device in the computers device manager, replug the phone and see if it will reinstall the phone driver correctly.
Sent from my GT-P5210 using Tapatalk
Related
Solved: See post below.
So I decided to go back to Kitkat from Lollipop. To do this I went into TWRP and restored a 38R backup I made when I first got the phone in November. TWRP did its thing and booted back into 11S 38R and it seemed to work. What then happened was that I was prompted to update to 44S so I did and the phone rebooted into TWRP. TWRP came up with some sort of screen, I can't remember what it said but the last line said something about an MD5 check not beeing needed. It then turned off and I haven't been able to get it back on. I've tried holding down the power button on its own and after around 5 seconds it vibrates but nothing happens. Also when I plug it into my PC or charger the charging light doesn't turn on.
I've tried to get into recovery and fastboot mode by holding power button+up/down volume but nothing happens on screen but I still get a vibration. However when I press volume button up+power button it seems to be recognised in Windows and it brings up the device as "QHSUSB_BULK" but that is it.
Does anyone know how to fix this?
P.S: I've got a nandroid backup + modem backup from when I first got the phone available if that helps.
I was able to fix the issue using the Oneplus Recovery tool. The issue was that the phone was not being recognised by my PC despite installing the drivers included in the recovery tool. This post in the recovery tool thread had the answers:
"I also deactivate unsigned driver installation but still same fail... I found a Qualcomm HS-USB QDLoader 9008 2.1.0.5 for Windows 7 that I used. I opened the Device Manager, I found my device named QHSUSB_BULK with an yellow triangle. I pressed udate drivers , choose from computer and installed that Qualcomm HS-USB QDLoader 9008 2.1.0.5 I donwloaded. AFTER THAT the tool found my phone and I was manage to flash ROM took me half a day. I cant have done wrong , somethnig must be wrong with the drivers in the tool for w7 64bit or something . this was the first time I have hard bricked a phone EVER and I have flashed a lot . But im glad it worked out with that Qualcomm HS-USB QDLoader 9008 driver since that guy also had same problem as me and later got it to work with that driver. Qualcomm HS-USB Drivers"
http://forum.xda-developers.com/showpost.php?p=58074662&postcount=40
So that was how I fixed it.
Why it broke in the first place is a mystery but I'm just glad to be back on Kitkat 44S.
I used the LG Flash Tool 2014 for my device to try to recover from a bricked phone. And I think i made it worse after using the kdz file and it completed 100%. I took the battery out and unplugged the phone when it was done. It wont even show anything on the screen now or go into recovery mode. But I do show RELINK HS-USB QDLoader 9008 (COM5) under the device options in my device manager when I connect the phone to the computer. Also it does make the device connected sound when I plug it in the computer. What can I do to get out of this mess? Thanks in the advance for any help that I can get.
Any help will be appreciated. THanks.
i downgraded my moto x xt1052 from 5.1 to stock rom after that without knowing installed ota update for 4.4...that totally bricked my phone on installing update..on conneccting with pc it recognize and shows green light but the qualcom husb loader not listed in my device manager also tried installing qualcom driver stil not listed in other deives list too..without that driver cant able to debrick my phone..
is there any way to debrick my phone??
also tried http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 this method and also tried this wire moethod too http://forum.xda-developers.com/moto-x/moto-x-qa/how-to-unbricked-hard-bricked-phone-t3146036
still my lap(using win 10 64bit) doesnt shows qusb loader..
is there any way to debrick my phone ???
why the qualcom port is not installed in device manager
I am on windows 7 and device manager detects moto g xt1032 as usb input device. I downloaded usbdeview and uninstalled every driver for every device ever on my laptop and plugged the moto g back in same result. Downloaded moto g usb drivers from xda and tried updating the drivers, it says windows has determined it already has the best drivers.
I couldn't find any other drivers and oddly the filename of the drivers package downloaded from xda says Moto_winxp_drivers.zip, but it seems to have a bunch of driver files.
Yesterday it was detecting the moto g as 'xt1032' in device manager and I messed around with drivers and it is now back to usb input device. I don't think there is a problem with the laptop, might be some sort of software issue, but not sure what.
I should mention that this moto g is not operable as it is stuck in a boot loop with the occassional android robot laying down and red exclamation point. So there is that but I am trying to sort this out and get it to show on adb and then install something on it.
I also installed motorola device manager, no help. Seems the problem might be usb drivers since the package I downloaded from xda is from 2013 and I couldn't find an updated package.. so if anyone knows feel free to post a link. thx
Drivers from 2013 should be fine, considering that the device is also from that year.
Can you boot into fastboot? Which bootloader is installed?
There is an unbrick post in this forum. You can try going through that, it includes installing unsigned drivers under windows.
Can someone provied me blank flash file for motorola g6. I hard bricked my devices while updating it. There was an OTA update in my device and i was so excited that i didint notice battery percentage and started my update process. While updating my devices ran out of juice and now it is dead. It means not responding at all (not booting regularly or in recovery). When i connect it in my pc it is detected as Qualcomm HS-USB QLoader 9008. Please help me. I didnt find any blank flash file for my motorola g6. :crying::crying: