Develop Bugs

HELP! Fully Bricked LG G3 D855 Blank Screen

Hi,
I think I mistakenly flashing the Fastboot partition with all wrong version of Boot, Recovey and the rest of other partition.
Now phone is only turn with BLANK BLACK SCREEN, but USB Connection still active with COM assigned at port 41 (saw under device manager).
Anyone have idea how to flash it back to work, please .....
mKHMER

mkhmer said:
Hi,
I think I mistakenly flashing the Fastboot partition with all wrong version of Boot, Recovey and the rest of other partition.
Now phone is only turn with BLANK BLACK SCREEN, but USB Connection still active with COM assigned at port 41 (saw under device manager).
Anyone have idea how to flash it back to work, please .....
mKHMER
Click to expand...
Click to collapse
Search for latest stock rom 29 at the end of version number download an unzip to desktop.
Flash in Flashtool,at first take battery out and and flash only the bootloader uncheck everithing else !!!,when finisht disconect phone ,put battery in ,now in flashtool flash whole rom

Does your PC recognize your phone as Qualcomm HS-USB QDLoader 9008 or something else?

ludoke said:
Search for latest stock rom 29 at the end of version number download an unzip to desktop.
Flash in Flashtool,at first take battery out and and flash only the bootloader uncheck everithing else !!!,when finisht disconect phone ,put battery in ,now in flashtool flash whole rom
Click to expand...
Click to collapse
It dosn't recognize my USB driver, is there any driver needed to manually install? but if we put the battery it does [LGE AndroidNET COMx]

mkhmer said:
It dosn't recognize my USB driver, is there any driver needed to manually install? but if we put the battery it does [LGE AndroidNET COMx]
Click to expand...
Click to collapse
If PC doesn't recognize your device as Qualcomm HS-USB QDLoader 9008, you need to JTAG your device, or short pin.
Information about short pin;
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359

That look like we need to work direct on mainboard of the phone? anyway withou touching inside the phone?

mkhmer said:
That look like we need to work direct on mainboard of the phone? anyway withou touching inside the phone?
Click to expand...
Click to collapse
You have to disassembly your device.

My LG G3 is not recognised as stated above but as Android device LGE MOBILE ADB INTERFACE and i have no issues on Win 10.
The phone is also imidiatly detected by LG Pc Suite

ludoke said:
My LG G3 is not recognised as stated above but as Android device LGE MOBILE ADB INTERFACE and i have no issues on Win 10.
The phone is also imidiatly detected by LG Pc Suite
Click to expand...
Click to collapse
But when I remove the back cover, I see another stainless steel cover on those chip/board, how to remove it? Too risky!

http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359/page8#post63750296
Here is a brioef guide i am also facing that issue from alst five days.. hope some master help to solve that situation

HELP!
Soooo... I have LG G3 D855 32GB, i think i installed wrong version of TWRP recovery (for another phone). Phone is not charging, so battery is dead. NO boot, NO recovery and NO download mode. PC does not recognize phone with LG drivers and QDLoader USB driver installed. I already do a "short pin" and nothing changes at all. I am out of solutions, please help me.
I already tried:
https://www.reddit.com/r/LGG3/comments/41wbo3/how_to_unhardbrick_your_lg_g3_jtag/
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
http://forum.xda-developers.com/sprint-lg-g3/general/guide-how-to-restore-sprint-lg-g3-ls990-t2852042

ExtremeD722 said:
Soooo... I have LG G3 D855 32GB, i think i installed wrong version of TWRP recovery (for another phone). Phone is not charging, so battery is dead. NO boot, NO recovery and NO download mode. PC does not recognize phone with LG drivers and QDLoader USB driver installed. I already do a "short pin" and nothing changes at all. I am out of solutions, please help me.
I already tried:
https://www.reddit.com/r/LGG3/comments/41wbo3/how_to_unhardbrick_your_lg_g3_jtag/
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
Click to expand...
Click to collapse
Your computer recognize any serial port when you connect g3

[email protected] said:
Your computer recognize any serial port when you connect g3
Click to expand...
Click to collapse
Computer doesn't recognize anything... I tried all 4 ports (2 ports 3.0, 2 ports 2.0), with original cable and non-original(Sony) cable.

ExtremeD722 said:
I tried all 4 ports (2 ports 3.0, 2 ports 2.0), with original cable and non-original(Sony) cable.
Click to expand...
Click to collapse
I mean any responce in pc device manager when u connect ur mbl

[email protected] said:
I mean any responce in pc device manager when u connect ur mbl
Click to expand...
Click to collapse
No, device manager detects nothing. I have windows 10 (i tried in normal mode and test mode). And if I connect my G3 Beat computer crashes because of LG driver.( I tried different versions of LG drivers and always the same crash(error)).

ExtremeD722 said:
No, device manager detects nothing. I have windows 10 (i tried in normal mode and test mode). And if I connect my G3 Beat computer crashes because of LG driver.( I tried different versions of LG drivers and always the same crash(error)).
Click to expand...
Click to collapse
I think crashing driver due to window .Try to connect ur device at window 7 .Hope device manager show serial port or qhbulk.I was have same problem my g3 but i resolve by short wire method.Good luck
---------- Post added at 03:01 PM ---------- Previous post was at 02:53 PM ----------
ExtremeD722 said:
Soooo... I have LG G3 D855 32GB, i think i installed wrong version of TWRP recovery (for another phone). Phone is not charging, so battery is dead. NO boot, NO recovery and NO download mode. PC does not recognize phone with LG drivers and QDLoader USB driver installed. I already do a "short pin" and nothing changes at all. I am out of solutions, please help me.
I already tried:
https://www.reddit.com/r/LGG3/comments/41wbo3/how_to_unhardbrick_your_lg_g3_jtag/
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
http://forum.xda-developers.com/sprint-lg-g3/general/guide-how-to-restore-sprint-lg-g3-ls990-t2852042
Click to expand...
Click to collapse
Bro firt change ur window then install ur variant driver and qhbulk driver.After that if device manager show qhsub bulk port or something like then all problem will solve.If ur device manager show only lge serial port then use short wire method.:good:

[email protected] said:
I think crashing driver due to window .Try to connect ur device at window 7 .Hope device manager show serial port or qhbulk.I was have same problem my g3 but i resolve by short wire method.Good luck
Click to expand...
Click to collapse
I will try with other computers, but i have on all 3 computers win10...
Thx for respond !

ExtremeD722 said:
I will try with other computers, but i have on all 3 computers win10...
Thx for respond !
Click to expand...
Click to collapse
Then u should install window 7 because qhsub bulk will not dect on window 10.
---------- Post added at 04:11 PM ---------- Previous post was at 04:07 PM ----------
Bro when u install window 7 reply me if u get any issue.Be careful when u use short wire method because due to this method my g3 baseband and imei are unknow

[email protected] said:
Then u should install window 7 because qhsub bulk will not dect on window 10.
---------- Post added at 04:11 PM ---------- Previous post was at 04:07 PM ----------
Bro when u install window 7 reply me if u get any issue.Be careful when u use short wire method because due to this method my g3 baseband and imei are unknow
Click to expand...
Click to collapse
I will reply u soon. Why do u even need baseband and imei ?

Because my baseband. Unknown and imei is null

lg g3 bricked shows qdloaderboard diag says ap check failed device not in dwnld mode

i rooted my lg g3 d 855 lollipop and tried to install TWRP
but it was not a success i lost recovery + download mode but it boots perfectly into android system and can use it normally
to install twrp again i tried to flash it again and again but no success
then i flash aboot.img and it all went blank not booting not rrecovery etc
i tried board diag method to unbrick it shows up in my system as qcomm hs usb 9008
but when using board diag it says DEVICE NOT FOUND IN DLOAD MODE
plz help this is my first android phone after months of hardwork
i dont think i have enough money to replace the mobo or buy a new one:crying:

Hello,
it's recoverable, but you need to read and some knowledge...
Refer to this thread. Proceed point by point and use willcracker boarddiag.

halekhonza said:
Hello,
it's recoverable, but you need to read and some knowledge...
Refer to this thread. Proceed point by point and use willcracker boarddiag.
Click to expand...
Click to collapse
brother i used board diag method it is succesfully able to show my device as qcomm hs usb 9008
and im able extract the files with program
but when i click start after some time it says ap check failed ,device not found in dload mode
i desperately need ur help IM NEW TO XDA FORUMS I HOPE ANYONE WOULD BE ABLE TO SOLVE PROBLEM
tnx in advanc

adilismail62 said:
brother i used board diag method it is succesfully able to show my device as qcomm hs usb 9008
and im able extract the files with program
but when i click start after some time it says ap check failed ,device not found in dload mode
i desperately need ur help IM NEW TO XDA FORUMS I HOPE ANYONE WOULD BE ABLE TO SOLVE PROBLEM
tnx in advanc
Click to expand...
Click to collapse
I understand. I'm just asking if you really using right boarddiag (thread that I mentioned - willcracker.rar)
Also be sure that you have a phone connected to right port (check it in device manager)

halekhonza said:
I understand. I'm just asking if you really using right boarddiag (thread that I mentioned - willcracker.rar)
Also be sure that you have a phone connected to right port (check it in device manager)
Click to expand...
Click to collapse
halekhonza said:
I understand. I'm just asking if you really using right boarddiag (thread that I mentioned - willcracker.rar)
Also be sure that you have a phone connected to right port (check it in device manager)
Click to expand...
Click to collapse
yes im using the r8 port it shows in device manager and in board daig also i gave port 14
before my phone was going to get bricked its battery was low
is it affecting the procedure i think my battery is not charging
when i remove battery and connect to pc phone shows battery not inserted sign when i insert the batery it disappear and no sign of charging
i thought this might help:good:

You have to use the original LG usb cable. Dont try with fake china cables because its a lot possible to have troubles with them.

I've got bricked phone now i need help.....

Hello...
i've got a bricked phone from a friend of mine because he's out of options to put it back to fully function.
he told me that he had flashed the phone while it was in 9008 usbbulk whith a recovery thats not suitable for this
phone. now the only thing the phone is doing is turn backlight on when connect to pc ... it will not be recognized. all drivers are installed .... windows runs on test mode with no verfication for drivers or else ... is it possible to rescue the phone or is it good white brick ?
Phone Data:
LG K10 (420N)
16 GB

TheRazcall said:
Hello...
i've got a bricked phone from a friend of mine because he's out of options to put it back to fully function.
he told me that he had flashed the phone while it was in 9008 usbbulk whith a recovery thats not suitable for this
phone. now the only thing the phone is doing is turn backlight on when connect to pc ... it will not be recognized. all drivers are installed .... windows runs on test mode with no verfication for drivers or else ... is it possible to rescue the phone or is it good white brick ?
Phone Data:
LG K10 (420N)
16 GB
Click to expand...
Click to collapse
Do you see anything in device manager?

No... device manager shows nothing and there is no satisfaing "da ding" noise after plug in the USB to my PC...

{Solved}I gotta super slim brick !!!!

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 need blank Flash for Moto g5s please

Hello I need a blank flash for me Motorola G5S please, I tried everything to turn it on, only flashes the led blank notifications, it is recognized by the laptop as Qualcomm HS-USB QDLoader 9008. Please I am anguished.

Have you tried SD card method to boot?
Most of the users got their devices fixed using sd card boot

newinnov said:
Have you tried SD card method to boot?
Most of the users got their devices fixed using sd card boot
Click to expand...
Click to collapse
yes I tried using Rufus, but it did not work. I read that it is not compatible with 16GB models :crying:

Thomas0922 said:
yes I tried using Rufus, but it did not work. I read that it is not compatible with 16GB models :crying:
Click to expand...
Click to collapse
It will not work on windows!
Why can't you follow instructions? Windows 10 dd does not work with Linux images, Genius!

Thomas0922 said:
Hello I need a blank flash for me Motorola G5S please, I tried everything to turn it on, only flashes the led blank notifications, it is recognized by the laptop as Qualcomm HS-USB QDLoader 9008. Please I am anguished.
Click to expand...
Click to collapse
Try This
https://hardbrickfixmotog5s.blogspot.com/