tell me where they are and i used universal adb and fastboot drivers when I went to unlock bootloader adb was working pretty well with the drivers however fastboot wasn't cuz it didn't show my device in fastboot device even if it was plugged to the pc
Attached
mr.onegin said:
Attached
Click to expand...
Click to collapse
but is it really safe i dont want my pc destroyed
succaBYLTA said:
but is it really safe i dont want my pc destroyed
Click to expand...
Click to collapse
Drivers are safe but flashing or unblocking anything never was
Actually there is a thread on XDA all ready official-tool-windows-adb-fastboot-and-drivers-15-seconds-adb-installer but drivers I presented are from another forum exactly for this device.
mr.onegin said:
Drivers are safe but flashing or unblocking anything never was
Actually there is a thread on XDA all ready official-tool-windows-adb-fastboot-and-drivers-15-seconds-adb-installer but drivers I presented are from another forum exactly for this device.
Click to expand...
Click to collapse
Well also is QDLoader setup 64-bit safe cuz when i opened QDloader setup for 64-bit It opened alot of cmds and that was sus for me so is It safe
mr.onegin said:
Drivers are safe but flashing or unblocking anything never was
Actually there is a thread on XDA all ready official-tool-windows-adb-fastboot-and-drivers-15-seconds-adb-installer but drivers I presented are from another forum exactly for this device.
Click to expand...
Click to collapse
And also What does QDLoader even does? I AM pretty New to this
succaBYLTA said:
And also What does QDLoader even does? I AM pretty New to this
Click to expand...
Click to collapse
First Google result...
QDLoader
This package (Qualcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip) contains Qualcomm HS-USB QDLoader 9008 Drivers for Windows 10/7/8/8.1 64-Bit OS. This Qualcomm QDLoader Driver helps in detecting the device when it is connected to PC in EDL Mode or Download Mode.
This Qualcomm HS-USB Driver package is for 64-bit OS, you can download the 32-bit version of the driver here. If you would like to install the drivers manually, download these Qualcomm Drivers.
I installed all of them but still I cannot flash anything from fastboot. What can I do?
Related
after flashing the wrong rom to my nexus5x,it seemed turn to brick.plug to coputer and shows QUALCOMM HS-USB QHLOADER.
I tried QPST ,innos but they all stuck on XML file?
got no solution right now
Need more information
hopesrequiem said:
Need more information
Click to expand...
Click to collapse
connect to pc and shows Qualcomm HS-USB QDLoader 9008,
QPST Configuration state progress bar not moving,
eMMC software download needs XML files.
any solutions?
johnagg said:
any solutions?
Click to expand...
Click to collapse
You flashed a ROM. That mean you had installed twrp?
Hey guys i how are you doing?!!!
I have a htc desire d820n that was soft bricked and can boot only to fastboot when I tried to install a stock rom via sdcard it said that the zip file is to big and didnt install the rom then my phone was hard bricked and didn't turn on at all (not even to htc logo) and I downloaded 2 stock roms which were in a zip file and when i try to open them on my computer it says that the archive is corrupted (an unexpected end of archive) the good thing is that when i connect it to the pc it install a qualcomm driver (Qualcomm HS-USB QDLoader 9008 (COM5)) please help me.
thanks in advance.
George_Samy said:
Hey guys i how are you doing?!!!
I have a htc desire d820n that was soft bricked and can boot only to fastboot when I tried to install a stock rom via sdcard it said that the zip file is to big and didnt install the rom then my phone was hard bricked and didn't turn on at all (not even to htc logo) and I downloaded 2 stock roms which were in a zip file and when i try to open them on my computer it says that the archive is corrupted (an unexpected end of archive) the good thing is that when i connect it to the pc it install a qualcomm driver (Qualcomm HS-USB QDLoader 9008 (COM5)) please help me.
thanks in advance.
Click to expand...
Click to collapse
Carefully read it can help you with https://forum.xda-developers.com/de...n-restarts-continuously-t3548182#post71073715
My case is almost the same, but mine isn't detected for Windows (neither adb nor loader).
I had disconnected the battery, but without any results.
Any idea?
Clamp all 3 buttons and hold 1 minute. What happens?
vuk1963 said:
Clamp all 3 buttons and hold 1 minute. What happens?
Click to expand...
Click to collapse
n
Unfortunately, nothing
How did it all start? how did it all turn out? Read more.Are the drivers of the НTС installed?
---------- Post added at 07:11 PM ---------- Previous post was at 06:58 PM ----------
Android ADB driver https://yadi.sk/d/TVkbNcXv3KP7mQ Connect the phone to the computer in the task manager on the computer to choose the interface adb to install the driver, specify in the manual on the desktop. 2.Also install USB_driver_QCOM https://yadi.sk/d/mrmvZKrk3MSggY
vuk1963 said:
How did it all start? how did it all turn out? Read more.Are the drivers of the НTС installed?
---------- Post added at 07:11 PM ---------- Previous post was at 06:58 PM ----------
All started when the phone isn't capable to install the official update to 6.0.
I decided to try other ROM's, opening the boot loader and installing the TWRP recovery. All goes well, but the ROM that are working better (Tomal - Discovery 2.00) had problems with my LTE networks.
Reading one of your post, I started to try to install the official 6.0, but I forgot to wipe the system before relock the bootloader.
After trying flash different RUU files through fastboot I used one from easy firmware: (0PFJIMG_A51_UL_K44_DESIRE_SENSE60_Orange_ES_1.28.75.5_Radio_01.01.010_U10305041_08.01.41222_2__combined_signed.zip) that belong to my CID (Orange Spain)
Then the phone don't respond to anything...
I will uninstall all drivers and programs and restart according your instructions...
Click to expand...
Click to collapse
vuk1963 said:
lcarrasc said:
Yes, sadly, you need to restore the bootloader,and it's very difficult to do it yourself http://4pda.ru/forum/index.php?showtopic=643084&st=7060
Click to expand...
Click to collapse
Thanks. I understand that my phone is lost
I tried to use QFIL (romkingz.net/2016/07/how-to-use-qualcomm-flash-image-loader) but the computer hasn't recognised the phone...
Click to expand...
Click to collapse
Solution: I will buy a used 820 with broken screen and then change the bricked motherboard myself. The price here is around 40 eur.
lcarrasc said:
Solution: I will buy a used 820 with broken screen and then change the bricked motherboard myself. The price here is around 40 eur.
Click to expand...
Click to collapse
Did you do this ?: 1.Android ADB driver https://yadi.sk/d/TVkbNcXv3KP7mQ Connect the phone to the computer in the Device Manager on the computer to choose the interface adb to install the driver specify in the manual on the desktop. 2.Also install USB_driver_QCOM https://yadi.sk/d/mrmvZKrk3MSggY 3.Connect your phone to your computer,оn the computer in Device Manager, click the tab ports (СОМ and LPT).What is written there?
vuk1963 said:
Did you do this ?: 1.Android ADB driver https://yadi.sk/d/TVkbNcXv3KP7mQ Connect the phone to the computer in the Device Manager on the computer to choose the interface adb to install the driver specify in the manual on the desktop. 2.Also install USB_driver_QCOM https://yadi.sk/d/mrmvZKrk3MSggY 3.Connect your phone to your computer,оn the computer in Device Manager, click the tab ports (СОМ and LPT).What is written there?
Click to expand...
Click to collapse
Yes. I did it.
I'm running Windows 10. As you know this OS not showing Ports (COM and LTE) in Device Manager. I added manually a COM port, (COM3 in this case), but appears only the yellow signal (!) related to errors.
lcarrasc said:
Yes. I did it.
I'm running Windows 10. As you know this OS not showing Ports (COM and LTE) in Device Manager. I added manually a COM port, (COM3 in this case), but appears only the yellow signal (!) related to errors.
Click to expand...
Click to collapse
I also run Windows 10 х86 and in Device Manager has a ports (COM and LРТ)
What it's expected to find in the com ports?
lcarrasc said:
What it's expected to find in the com ports?
Click to expand...
Click to collapse
Something like: Qualcomm HS-USB QDLoader 9008 port com
The phone seems fully dead...
Only a red led blinking when the usb cable is connected to PC or a charger.
lcarrasc said:
The phone seems fully dead...
Only a red led blinking when the usb cable is connected to PC or a charger.
Click to expand...
Click to collapse
Clamp all 3 buttons and hold 1 minute,and try different variants combinations with holding the volume buttons + and - and the power button,with the connection of the phone to the computer and to the power unit
I tried all possible combinations of buttons, and nothing...
Any idea?
I attempted to flash Dirty Unicorn from they're site, which appeared to go well, then I proceeded to flash the TWRPinstaller.zip that was suggested from the maintainer for our device. when I tried to reboot from recovery I got a no OS message. I ignored the message and attempted to reboot. Now the phone doesn't normally power on or off(which may change once the battery dies), no boot animation, no recovery, no fastboot recognition. The computer recognizes the phone as Qualcomm HS-USB QDLoader 9008. I googled for hours last night trying to fix to no avail. Has any of our great devs found a way to atleast recover the bootloader screen. I think I can handle it myself from there with adb.
Solved: Use the first blank flash from the link to get back to bootloader screenhttps://firmware.center/firmware/Motorola/Moto%20Z2%20Force/Blankflash/
From bootloaderscreen put your ADB skills to work. I'm not too good with guides but this just saved me $175
mookiexl said:
I attempted to flash Dirty Unicorn from they're site, which appeared to go well, then I proceeded to flash the TWRPinstaller.zip that was suggested from the maintainer for our device. when I tried to reboot from recovery I got a no OS message. I ignored the message and attempted to reboot. Now the phone doesn't normally power on or off(which may change once the battery dies), no boot animation, no recovery, no fastboot recognition. The computer recognizes the phone as Qualcomm HS-USB QDLoader 9008. I googled for hours last night trying to fix to no avail. Has any of our great devs found a way to atleast recover the bootloader screen. I think I can handle it myself from there with adb.
Click to expand...
Click to collapse
I did the same, got the same. Can't confirm the Qualcomm HS-USB QDLoader 9008 device will be there.
No charge, no screen, does not turn on/off, no vibration. Worst: no bootloader... Again, could be different if the battery dies.
mookiexl said:
Solved: Use the first blank flash to from the link to get back to bootloader screenhttps://firmware.center/firmware/Motorola/Moto%20Z2%20Force/Blankflash/
From bootloaderscreen put your ADB skills to work. I'm not too good with guides but this just saved me $175
Click to expand...
Click to collapse
Three questions:
1. File there is NDX26.183-15_17. Is it the same for OPXS27.109-34-10 on which I'm now? I suppose I need to use the "Oreo" version (2nd file in the list).
2. Which tool/software did you use to flash it? Is there a step by step tutorial?
3. You say "from bootloader screen". What about if we do not have a bootloader screen but a black brick in our hands?
Technical said:
I did the same, got the same. Can't confirm the Qualcomm HS-USB QDLoader 9008 device will be there.
No charge, no screen, does not turn on/off, no vibration. Worst: no bootloader... Again, could be different if the battery dies.
Three questions:
1. File there is NDX26.183-15_17. Is it the same for OPXS27.109-34-10 on which I'm now? I suppose I need to use the "Oreo" version (2nd file in the list).
2. Which tool/software did you use to flash it? Is there a step by step tutorial?
3. You say "from bootloader screen". What about if we do not have a bootloader screen but a black brick in our hands?
Click to expand...
Click to collapse
Answers
1.NDX26.183-15_17 (All it does is get your boatloader screen back
2. If you go to the device menu on your computer and your phone reads as Qualcomm HS-USB QDLoader 9008, all you have to do is click on the Blank flash all file and from the extracted folder and command prompt will do the rest. If the device is not recognized QDLoader 9008 then you will need to download qualcomm drivers to your computer
3.That is exactly what the file is for. Getting your black brick to at least the bootloader screen. From there you can adb recovery or stock rom.
What I ended up doing was adb push the bootable TWRP from the this thread https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932.
Flash the TWRP the official for our device from they're site(the bootable TWRP will give you access to extsd and thats where I had the official TWRP )
Rebooted back to bootloader and adb the firmware files for my device from the AOISP thread and rebooted my phone and I was booting DU.
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Dany XP said:
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Click to expand...
Click to collapse
Before connecting the phone, start the blankflash program. Maybe you have to repeat it a couple of times. Also try different cables, ports and computers.
Dany XP said:
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
mookiexl said:
Answers
1.NDX26.183-15_17 (All it does is get your boatloader screen back
2. If you go to the device menu on your computer and your phone reads as Qualcomm HS-USB QDLoader 9008, all you have to do is click on the Blank flash all file and from the extracted folder and command prompt will do the rest. If the device is not recognized QDLoader 9008 then you will need to download qualcomm drivers to your computer
3.That is exactly what the file is for. Getting your black brick to at least the bootloader screen. From there you can adb recovery or stock rom.
What I ended up doing was adb push the bootable TWRP from the this thread https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932.
Flash the TWRP the official for our device from they're site(the bootable TWRP will give you access to extsd and thats where I had the official TWRP )
Rebooted back to bootloader and adb the firmware files for my device from the AOISP thread and rebooted my phone and I was booting DU.
Click to expand...
Click to collapse
Can somebody please help me, my laptop isn't even detecting my device as QDLoader 9008, can you please tell me which windows os version did you use, also did you use the usb cable came in the box and did you use usb 2.0 port or 3.0?
LØNEWØLF said:
Can somebody please help me, my laptop isn't even detecting my device as QDLoader 9008, can you please tell me which windows os version did you use, also did you use the usb cable came in the box and did you use usb 2.0 port or 3.0?
Click to expand...
Click to collapse
Well, you need of course, Qualcomm loader driver, to at least having your device recognized as 9008. There u go: https://www.androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/
After that, go ahead with blankall and stuff...
P.s. and yes ..stay away from USB 3.0! ???
Dany XP said:
Well, you need of course, Qualcomm loader driver, to at least having your device recognized as 9008. There u go:
After that, go ahead with blankall and stuff...
P.s. and yes ..stay away from USB 3.0!
Click to expand...
Click to collapse
Thanks for the reply bro....but I have that driver installed...I installed before connecting it....still not detecting... I'm gonna try this once more in my friend's pc... let's see what happens
LØNEWØLF said:
Thanks for the reply bro....but I have that driver installed...I installed before connecting it....still not detecting... I'm gonna try this once more in my friend's pc... let's see what happens
Click to expand...
Click to collapse
I know it's a long shot but...do u have any other Qualcomm device to try?
U can enter EDL mode with adb command "adb reboot edl". Yes, it's that simple. ?
Dany XP said:
I know it's a long shot but...do u have any other Qualcomm device to try?
U can enter EDL mode with adb command "adb reboot edl". Yes, it's that simple. ?
Click to expand...
Click to collapse
OK I'll try...but how would I get back from edl to Normal without doing anything in the edl?
LØNEWØLF said:
OK I'll try...but how would I get back from edl to Normal without doing anything in the edl?
Click to expand...
Click to collapse
Uh...good question
I am trying to use the EDL methods that require qualcomm hs-usb qdloader 9008 drivers.
I had 0 luck so far to get the device show up as qualcomm hs-usb qdloader 9008.
I tried several versions of the driver install package I could find, tinkered with LG, xiaomi and others.
My device is Windows x64, 1903.
It's an UEFI device, so secure boot is enabled
Some instructions require you to disable driver signing - which doesn't work with secure boot, I disabled it...
I disabled driver signing...
I installed the certificate...
still nothing.
When booting the device shows up under "Universal Serial Bus devices" as "QUSB_BULK"... when trying to update the drivers, I get "The best drivers for your device are already installed" - Care Suite Emergency Connectivity, which is a Microsoft driver. Uninstalling that one also results in nothing really.
Are there no qdloader drivers for a current OS? Which steps do you take to get the driver working?
My phones do not even seem show up when in EDL mode a this point.
Any help is appreciated.
My first "thing" is to do is to reflash the Alcatel Idol 4s open market properly as the WDRT tool only would allow the T-Mobile firmware to be flashed.
What I eventually would want is a European language supporting firmware with a US based modem/cellular configuration.
My first step is however to be able to flash things at all.
Any guidance is appreciated.
unstall all nokia/microsoft software,driver on pc and install qcom driver again
I'm a newbie here I have all the drivers installed it's showing the correct Qualcomm QD loader 9008 under device manager however device manager is showing the yellow triangle with an exclamation point. I have twrp installed however when I go to twrp I can't do anything like flash root I need someone to hold my hand here and really help me thank you
Did you choose the corect region version for youre phone?
Did you follow the guide how to flash MSM ? By the letter.
If you have the QD loader 9008 in Device Manager you should be good to go.
this.guy.lol said:
I'm a newbie here I have all the drivers installed it's showing the correct Qualcomm QD loader 9008 under device manager however device manager is showing the yellow triangle with an exclamation point. I have twrp installed however when I go to twrp I can't do anything like flash root I need someone to hold my hand here and really help me thank you
Click to expand...
Click to collapse
If the device manager is showing the triangle then the drivers are not installed correctly.
The qualcomm drivers are here :
Qualcomm drivers.7z | by djsubterrain for OnePlus 9 Pro
This is the driver you will need to use any MSM tool. Please ensure you have driver signature enforcement disabled in Windows 10 first, you can do so by running this in a command window : bcdedit.exe /set nointegritychecks on To enable signature enforcement again, toggle the flag back off with...
androidfilehost.com
You haven't said what OS you're on but If it's not installing them properly, then try disabling driver signatures although I think they are signed.
As with all drivers, install them before connecting the device.
If you still have a problem, right click the device in the device manager and uninstall, then restart and try again.