Related
Hello everyone.
I need your help.
My Device: LG G3 D855 32GB
The device does not turn on, the only thing that appears is because when I connect the device to a PC, I see a driver installed:
RELINK HS-USB QDLoader 9008
I read guides on site here, and I'm trying to order
I downloaded the software BoardDiag 2.9
I downloaded the files to the appropriate TOT
I extracted the files by instructors on site.
I opened the program and I followed the guide and it seems to me an error
Download mode is enabled Mode,
I quickly disconnects from the computer and reconnect the computer and then the moment I am unable to do a test and the results are:
AP CHECK START = PASS
EMMC TEST START
FAILED TO OPEN PARTITION FROM EMMC
TEST ABORTED !!
I tried a lot of tutorials but I can not, it always seems the device is in Download Mode
What can I do more?
Please your help,
Eliran
If you go that way, you will need bunch of other stuff. Here is the link
http://open-freax.fr/guide-unbrick-your-lg-g3/
It is a good thing that your PC recognises phone like that.
But first be sure that You can not enter download mode or recovery or even fastboot.
And please say what did you do to make it like that? Wrong flash?
If you CAN enter download mode than you can flash kdz or tot files from there. Easiest way is to use LGUP but you must be careful if you want to try.
The phone fell
Navuhodonosor said:
If you go that way, you will need bunch of other stuff. Here is the link
It is a good thing that your PC recognises phone like that.
But first be sure that You can not enter download mode or recovery or even fastboot.
And please say what did you do to make it like that? Wrong flash?
If you CAN enter download mode than you can flash kdz or tot files from there. Easiest way is to use LGUP but you must be careful if you want to try.
Click to expand...
Click to collapse
Thanks for the comment
The phone fell into the vehicle.
I know the phone is always in Download Mode
The software does not let me do anything and making phone download mode
I did not try to install KDZ.
And I can not open a setup KDZ because the device does not rise and there is no open port.
I only have the port I did above.
Thanks for the help, I worked in the guide and I could not ...
Navuhodonosor said:
If you go that way, you will need bunch of other stuff. Here is the link
It is a good thing that your PC recognises phone like that.
But first be sure that You can not enter download mode or recovery or even fastboot.
And please say what did you do to make it like that? Wrong flash?
If you CAN enter download mode than you can flash kdz or tot files from there. Easiest way is to use LGUP but you must be careful if you want to try.
Click to expand...
Click to collapse
Thanks for the help, I worked in the guide and I could not ...
I went through all the steps I found at:
Now, let’s get the party started
I set up the software the guide and I got an error:
FAIL on the EMMC test
I changed the parameter Read / Write »to« Erase
And again I got the error:
FAIL on the EMMC test
Then I try again, click Start, open a window and write in English and Chinese
Device DLOAD mode
device was not found in dload trying flash peogrammer
I click OK, the window closes and then when I press Start again, the window reappears.
Only when I disconnect the USB cable from the computer and the author briefly again then I’m able to do the test, but he failed.
FAIL on the EMMC test
The device always is in Download Mode and appears port:
RELINK HS-USB QDLoader 9008
My component can not be right at all and it always is in Download Mode?
I did not do short the guide, because the computer also detected me.
It has always seemed stuck in a download mode.
There is another option? Short elsewhere as will enable progress?
Thank you very much for your help,
Eliran
I need help please. What can i do
zarfati66 said:
Thanks for the help, I worked in the guide and I could not ...
I went through all the steps I found at:
Now, let’s get the party started
I set up the software the guide and I got an error:
FAIL on the EMMC test
I changed the parameter Read / Write »to« Erase
And again I got the error:
FAIL on the EMMC test
Then I try again, click Start, open a window and write in English and Chinese
Device DLOAD mode
device was not found in dload trying flash peogrammer
I click OK, the window closes and then when I press Start again, the window reappears.
Only when I disconnect the USB cable from the computer and the author briefly again then I’m able to do the test, but he failed.
FAIL on the EMMC test
The device always is in Download Mode and appears port:
RELINK HS-USB QDLoader 9008
My component can not be right at all and it always is in Download Mode?
I did not do short the guide, because the computer also detected me.
It has always seemed stuck in a download mode.
There is another option? Short elsewhere as will enable progress?
Thank you very much for your help,
Eliran
Click to expand...
Click to collapse
I need help please. What can i do
The phone woke for a moment ...
zarfati66 said:
I need help please. What can i do
Click to expand...
Click to collapse
Hello everyone
Today I tried again to connect the device to your computer, the screen comes on suddenly.
And see the state of battery with a question mark inside a yellow triangle.
I did not realize also saw installed driver
LGE AndroidNet USB Serial Port
I tried to re-install.
Now again became a black screen and the next thing happens:
When the device without a battery connected to a computer costing me
RELINK HS-USB QDLoader 9008
When I'm with a battery, it registers an unknown device.
When the device without a battery test again tried to do this EMMC component fails.
help please
Eliran
relink hs-USB Qdloader 9008
ZARFATI6 said:
Hello everyone
Today I tried again to connect the device to your computer, the screen comes on suddenly.
And see the state of battery with a question mark inside a yellow triangle.
I did not realize also saw installed driver
LGE AndroidNet USB Serial Port
I tried to re-install.
Now again became a black screen and the next thing happens:
When the device without a battery connected to a computer costing me
RELINK HS-USB QDLoader 9008
When I'm with a battery, it registers an unknown device.
When the device without a battery test again tried to do this EMMC component fails.
help please
Eliran
Click to expand...
Click to collapse
I am exactly in the same situation. Have you found any solution so far???? My phone suddenly stopped working and didn't boot up at all first and then I used the LG Flashtool to install original TOT file and all went well. I forgot to close LG Flashtool and it started flashing again. LG Flash tool restarts the phone at about 80% and then it failed at that point and since then I am having this issue.................
Any solution???????
apur32 said:
I am exactly in the same situation. Have you found any solution so far???? My phone suddenly stopped working and didn't boot up at all first and then I used the LG Flashtool to install original TOT file and all went well. I forgot to close LG Flashtool and it started flashing again. LG Flash tool restarts the phone at about 80% and then it failed at that point and since then I am having this issue.................
Any solution???????
Click to expand...
Click to collapse
Same situation too, solutions yet?
Hey I have the same problem .
If any of you found the solution please post it here or pm me, I am stuck
I wanted to port MIUI on the Robin, found Xiaomi mi4c, which were good enough to port miui from. downloaded, edited boot, and pushed to phone. then i flashed it, clicked "reboot to system" and then it turnes off. It is not reacting on buttons or that sort of thing. When i connected to pc i had qhsusb.. but after flashing drivers it is qualcomm hs-usb dloader 9008 (COM9). I found nothing about unbricking, not found needed files for QFIL unbrick? Please help with smth
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
So,
Now I got the issue that was the main culprit of the error happening while flashing in EDL mode through mi flash tool .. .
Current status of my phone- Nothings working no buttons working
Black screen
When I connect to PC blue led flashes. Without battery red led flashes only one time
Phone detects as Qualcomm HS USB qdloader 9008 port
And after that when I try to flash it .. the port kepps refreshing and the phone connects and disconnects...
On the device manager it seems that the qdloader 9008 converts into diagonastics 9006 then reverts back to 9008. And in the disk management the Qualcomm mmc storage do the same just connects and 2 or 3 second later disconnects. Then reconects and disconnects..
And at that point the flash tool gives the error....
Changing usb wire and changing pc gives the same result .
Now please suggest me a way to get rid out of it.
The thread is very long sorry for that ....
Please help me out .
Windows driver issue maybe?
Are you sure that this is not a driver problem in Windows?
I have never tried flashing in Download Mode, but I'm just making a (possibly silly) guess.
Enable Test-signing in Windows and try again :-
Put this command in an elevated command prompt and restart the computer to enable test signing:-
Code:
bcdedit /set testsigning on
Good luck!
First trying with disable driver signature enforcement from boot option and now tried with cmd ran the code but same result. Is this my windows 7 problem?
I haven't tried it on windows 10....
Hi all
well in a nutshell a friend's good old pixel 2 xl finally had the issue of black screen and only qbulk being detected by the PC.
After a bit of googling i found a Qualcomm loader and some firehose files from github.
However it fails on with error sahara protocol cannot establish connection.
I read that maybe i needed to short pins on the board to go into edl test mode, but dont know which ones i have attached a picture
Any suggestions would help
Can't help you with the pins. I can however tell you that based upon my experiences with my Lenovo tablet, using Xiaomi's MiFlash software proved a lot more reliable than Qualcomm's tools when trying to restore the firmware through the low level interface.
Strephon Alkhalikoi said:
Can't help you with the pins. I can however tell you that based upon my experiences with my Lenovo tablet, using Xiaomi's MiFlash software proved a lot more reliable than Qualcomm's tools when trying to restore the firmware through the low level interface.
Click to expand...
Click to collapse
i will give it a try thank you, is it the same way for xiaomi to short pins in order to get to edl test mode ?
I don't know.
Well, there has to be a reason that the phone ended up in this state.
My guess is a hardware fault, and if that's the case, you'll need to replace the motherboard.
Some phones can end up this way if you do something stupid while flashing a rom, but I've never heard about that on a Pixel.
code777 said:
Hi all
well in a nutshell a friend's good old pixel 2 xl finally had the issue of black screen and only qbulk being detected by the PC.
After a bit of googling i found a Qualcomm loader and some firehose files from github.
However it fails on with error sahara protocol cannot establish connection.
I read that maybe i needed to short pins on the board to go into edl test mode, but dont know which ones i have attached a picture
Any suggestions would help
Click to expand...
Click to collapse
If your device is not properly detected, because it is not properly in EDL mode, then, there's not a tool that can detect it or work with.
When the kernel refuses to start because of a failed upgrade or something, then the device enters automatically to Qualcomm/EDL mode, but the first you'll see, it is detected in device manager as QBulk or Qualcomm HS-UB-Diagnostics 900E, then you have to update the drivers to Qualcomm HS-USB QDloader 9008 to get it.
This is an example of my other device, by fortune my P2XL is working fine besides the bootloader can't be unlocked.
SubwayChamp said:
If your device is not properly detected, because it is not properly in EDL mode, then, there's not a tool that can detect it or work with.
When the kernel refuses to start because of a failed upgrade or something, then the device enters automatically to Qualcomm/EDL mode, but the first you'll see, it is detected in device manager as QBulk or Qualcomm HS-UB-Diagnostics 900E, then you have to update the drivers to Qualcomm HS-USB QDloader 9008 to get it.
This is an example of my other device, by fortune my P2XL is working fine besides the bootloader can't be unlocked.
Click to expand...
Click to collapse
Hello, i think i installed it correctly tried on two different computers with one "unsigned" driver with the windows drive signature turned off and then with a driver from Microsoft's own website which is signed i still gate the same issue.
Tired with couple of version of QPST with the latest i found being QPST_2.7.496, tried with a couple of firehose files there is a github repo with most of them 8916 often pops up in google 2xl topics and one zip which was named 2XL had in it prog_ufs_firehose_8998_ddr.elf not sure if its the correct one :
ERROR: function: rx_data:246 Error occurred while reading from COM port
ERROR: function: sahara_main:982 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
So i am stuck to this point now , ANY suggestions will be appreciated
code777 said:
Hello, i think i installed it correctly tried on two different computers with one "unsigned" driver with the windows drive signature turned off and then with a driver from Microsoft's own website which is signed i still gate the same issue.
Tired with couple of version of QPST with the latest i found being QPST_2.7.496, tried with a couple of firehose files there is a github repo with most of them 8916 often pops up in google 2xl topics and one zip which was named 2XL had in it prog_ufs_firehose_8998_ddr.elf not sure if its the correct one :
ERROR: function: rx_data:246 Error occurred while reading from COM port
ERROR: function: sahara_main:982 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
So i am stuck to this point now , ANY suggestions will be appreciated
Click to expand...
Click to collapse
To start with, the correct installation of these drivers is mandatory, otherwise, you can't advance further, if you have a message of success, then it's done, if not, you may redo the steps.
Microsoft doesn't own any of the needed drivers here. All relies on Qualcomm, it contains the lot of variants, from all of them, one is all you need.
If the issue is with QPST, I saw a QPST thread in XDA, just search for it.