LG G6 TestPoints for EDL Mode (9008) - LG G6 Guides, News, & Discussion

Simple af. Just short them.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For incase that doesn't work;

---

One question can we make lg g6 go to edl mode using edl cable? I don't want to open the device and make a mess

---

Ashley david said:
One question can we make lg g6 go to edl mode using edl cable? I don't want to open the device and make a mess
Click to expand...
Click to collapse
I tried it (shorting GND with DATA -) not working.

---

badmaan said:
Simple af. Just short them.
For incase that doesn't work;
Click to expand...
Click to collapse
It works! My phone was 100% dead and now I am in Qualcomm 9008 mode! (using the test points under the flash)
unfortunately it seems to be another dead path with this phone. No firehose and no xml to flash with QFIL

---

I have hoses but i don't think any are the proper ones. I can get my software/hardware to load some but not perform any operations with one hose and the other nothing at all.

---

try using the firehose from here. https://forum.xda-developers.com/t/lg-g6-unbrick-new-method.3935924/
i had been given a dead G6 no partitions (fried) and none of the tools work for reflashing. found a bunch of tools to use in Linux since the drivers/windows kept reseting the connection every time i plugged in and was getting no response so it always ended up in failure. (Note if really is dead bricked as mine was you literally have to pull the pins and get back to edl using the test points every time for each operation as it resets and stops responding after each)
Managed to create proper rawprogram0-6.xml using https://github.com/ANEP-ET/kdztools
unkdz -f myfile.kdz -x
undz -f kdzextracted/myfile.dz -c
undz -f kdzextracted/myfile.dz -r
(creates rawprogram xml files for each primary_gpt file you likely have)
cp rawprogram*.xml dzextracted/
make sure to edit all the separate rawprogram files and edit the files to match the letters associated with the extracted files in dzextracted.
for example in rawprogram1.xml prefix all the files listed in there with B.
for rawprogram2.xml prefix all the files listed in there with C.
and so on. BUT do not rename the first file, rawprogram0.xml does not need to append A. to it as the first one did not get created as such.
tried this tool where it was getting the phone was getting detected properly and the programmer file was uploaded but it was iffy to get it to do anything but cool tool and lots of programmer files with it https://github.com/bkerler/edl
what finally worked with my newly created rawprogam files and the programm was using Qualcoms qdl tool (requires compiling it in Linux, port on github) from here https://github.com/andersson/qdl
by doing
qdl --storage ufs prog_ufs_firehose_lge_g6.elf rawprogram0.xml
and repeat for all the rawprogram files 0 through 6 (or however many there was autogenerated) you generated from above making sure to pull the battery and force it back into edl mode if its reseting the connection afterward like it did for me. Note the name for the firehose there might be something else for you just replace the name with the right file.

---

Oh i forgot that you probably need to patch the kdztools from https://github.com/ANEP-ET/kdztools because it may fail on newer files the PR for the patch is on the patch already on there a PR #1 @ https://github.com/ANEP-ET/kdztools/pull/1

---

Lastly before i forget this as well run qdl from within the dzextracted directory so i can find all the bin/image files enumerated in the rawprogram xml files that you copied over into and flash them properly.

---

draekko said:
try using the firehose from here. https://forum.xda-developers.com/t/lg-g6-unbrick-new-method.3935924/
i had been given a dead G6 no partitions (fried) and none of the tools work for reflashing. found a bunch of tools to use in Linux since the drivers/windows kept reseting the connection every time i plugged in and was getting no response so it always ended up in failure. (Note if really is dead bricked as mine was you literally have to pull the pins and get back to edl using the test points every time for each operation as it resets and stops responding after each)
Managed to create proper rawprogram0-6.xml using https://github.com/ANEP-ET/kdztools
unkdz -f myfile.kdz -x
undz -f kdzextracted/myfile.dz -c
undz -f kdzextracted/myfile.dz -r
(creates rawprogram xml files for each primary_gpt file you likely have)
cp rawprogram*.xml dzextracted/
make sure to edit all the separate rawprogram files and edit the files to match the letters associated with the extracted files in dzextracted.
for example in rawprogram1.xml prefix all the files listed in there with B.
for rawprogram2.xml prefix all the files listed in there with C.
and so on. BUT do not rename the first file, rawprogram0.xml does not need to append A. to it as the first one did not get created as such.
tried this tool where it was getting the phone was getting detected properly and the programmer file was uploaded but it was iffy to get it to do anything but cool tool and lots of programmer files with it https://github.com/bkerler/edl
what finally worked with my newly created rawprogam files and the programm was using Qualcoms qdl tool (requires compiling it in Linux, port on github) from here https://github.com/andersson/qdl
by doing
qdl --storage ufs prog_ufs_firehose_lge_g6.elf rawprogram0.xml
and repeat for all the rawprogram files 0 through 6 (or however many there was autogenerated) you generated from above making sure to pull the battery and force it back into edl mode if its reseting the connection afterward like it did for me. Note the name for the firehose there might be something else for you just replace the name with the right file.
Click to expand...
Click to collapse
Good to hear that there is some hope, i bricked my G6 (h870) 2 months ago while in download mode the laptop turn off. I tried the new unbricked method but got same issue of connection reset. Will try this and update. Also can you share rawprogram xmls please.

---

kurogami555 said:
Good to hear that there is some hope, i bricked my G6 (h870) 2 months ago while in download mode the laptop turn off. I tried the new unbricked method but got same issue of connection reset. Will try this and update. Also can you share rawprogram xmls please.
Click to expand...
Click to collapse
Nope it was an H873 canadian model. You can make your own using the kdz for your model as i described though.

---

draekko said:
try using the firehose from here. https://forum.xda-developers.com/t/lg-g6-unbrick-new-method.3935924/
i had been given a dead G6 no partitions (fried) and none of the tools work for reflashing. found a bunch of tools to use in Linux since the drivers/windows kept reseting the connection every time i plugged in and was getting no response so it always ended up in failure. (Note if really is dead bricked as mine was you literally have to pull the pins and get back to edl using the test points every time for each operation as it resets and stops responding after each)
Managed to create proper rawprogram0-6.xml using https://github.com/ANEP-ET/kdztools
unkdz -f myfile.kdz -x
undz -f kdzextracted/myfile.dz -c
undz -f kdzextracted/myfile.dz -r
(creates rawprogram xml files for each primary_gpt file you likely have)
cp rawprogram*.xml dzextracted/
make sure to edit all the separate rawprogram files and edit the files to match the letters associated with the extracted files in dzextracted.
for example in rawprogram1.xml prefix all the files listed in there with B.
for rawprogram2.xml prefix all the files listed in there with C.
and so on. BUT do not rename the first file, rawprogram0.xml does not need to append A. to it as the first one did not get created as such.
tried this tool where it was getting the phone was getting detected properly and the programmer file was uploaded but it was iffy to get it to do anything but cool tool and lots of programmer files with it https://github.com/bkerler/edl
what finally worked with my newly created rawprogam files and the programm was using Qualcoms qdl tool (requires compiling it in Linux, port on github) from here https://github.com/andersson/qdl
by doing
qdl --storage ufs prog_ufs_firehose_lge_g6.elf rawprogram0.xml
and repeat for all the rawprogram files 0 through 6 (or however many there was autogenerated) you generated from above making sure to pull the battery and force it back into edl mode if its reseting the connection afterward like it did for me. Note the name for the firehose there might be something else for you just replace the name with the right file.
Click to expand...
Click to collapse
Good solid info. Thanks

---

draekko said:
try using the firehose from here. https://forum.xda-developers.com/t/lg-g6-unbrick-new-method.3935924/
i had been given a dead G6 no partitions (fried) and none of the tools work for reflashing. found a bunch of tools to use in Linux since the drivers/windows kept reseting the connection every time i plugged in and was getting no response so it always ended up in failure. (Note if really is dead bricked as mine was you literally have to pull the pins and get back to edl using the test points every time for each operation as it resets and stops responding after each)
Managed to create proper rawprogram0-6.xml using https://github.com/ANEP-ET/kdztools
unkdz -f myfile.kdz -x
undz -f kdzextracted/myfile.dz -c
undz -f kdzextracted/myfile.dz -r
(creates rawprogram xml files for each primary_gpt file you likely have)
cp rawprogram*.xml dzextracted/
make sure to edit all the separate rawprogram files and edit the files to match the letters associated with the extracted files in dzextracted.
for example in rawprogram1.xml prefix all the files listed in there with B.
for rawprogram2.xml prefix all the files listed in there with C.
and so on. BUT do not rename the first file, rawprogram0.xml does not need to append A. to it as the first one did not get created as such.
tried this tool where it was getting the phone was getting detected properly and the programmer file was uploaded but it was iffy to get it to do anything but cool tool and lots of programmer files with it https://github.com/bkerler/edl
what finally worked with my newly created rawprogam files and the programm was using Qualcoms qdl tool (requires compiling it in Linux, port on github) from here https://github.com/andersson/qdl
by doing
qdl --storage ufs prog_ufs_firehose_lge_g6.elf rawprogram0.xml
and repeat for all the rawprogram files 0 through 6 (or however many there was autogenerated) you generated from above making sure to pull the battery and force it back into edl mode if its reseting the connection afterward like it did for me. Note the name for the firehose there might be something else for you just replace the name with the right file.
Click to expand...
Click to collapse
Ok, so i tried this method in Ubuntu but Qdl just waits for EDL device nothing happens. I check the attached usb devices there it shows that Qualcomm 9008 is connected but Qdl script doesn't detect it. Some help please.

---

kurogami555 said:
Ok, so i tried this method in Ubuntu but Qdl just waits for EDL device nothing happens. I check the attached usb devices there it shows that Qualcomm 9008 is connected but Qdl script doesn't detect it. Some help please.
Click to expand...
Click to collapse
did you reset the device by pulling the battery and putting it back into edl mode for each time you ran qdl? if you don't it won't work as the connect resets every time and will stop communicating after each command sent. Also make sure you have the right programmer file.

---

draekko said:
did you reset the device by pulling the battery and putting it back into edl mode for each time you ran qdl? if you don't it won't work as the connect resets every time and will stop communicating after each command sent. Also make sure you have the right programmer file.
Click to expand...
Click to collapse
yes, i removed battery again and again short circuited the edl pin the device immediately gets detected as Qualcomm 9008 in usb list but the Qdl script still shows waiting for Edl device.

---

If you use the programmer file with this tool at https://github.com/bkerler/edl does it show the cpu/serialnumbers/other info when trying to get a partitions list or other commands? If not either the programmer file is wrong or the device is too dead to respond.

---

draekko said:
If you use the programmer file with this tool at https://github.com/bkerler/edl does it show the cpu/serialnumbers/other info when trying to get a partitions list or other commands? If not either the programmer file is wrong or the device is too dead to respond.
Click to expand...
Click to collapse
what command should i run to check if the firehose is good or not ?

---

kurogami555 said:
what command should i run to check if the firehose is good or not ?
Click to expand...
Click to collapse
try anything that reads data, try printpgt for example. If it doesn't list the cpu type and serial number it means you have the wrong programmer file for your device. Note that it may fail to actually print any data as it failed on mine but will show the SN/cpu information with the right one.

---

draekko said:
try anything that reads data, try printpgt for example. If it doesn't list the cpu type and serial number it means you have the wrong programmer file for your device. Note that it may fail to actually print any data as it failed on mine but will show the SN/cpu information with the right one.
Click to expand...
Click to collapse
Sorry for this but i don't get how to use this edl script it's too complicated. Can you please check whether the firehose i attached is good or not. Please.

---

kurogami555 said:
Sorry for this but i don't get how to use this edl script it's too complicated. Can you please check whether the firehose i attached is good or not. Please.
Click to expand...
Click to collapse
I can't do that the phone is sealed up now and can't be thrown back into edl mode.
Try the loaders github repo for edl, 0005f0e100310000_2cf7619a278d2607_fhprg_peek.bin should theoretically be the right one. https://github.com/bkerler/Loaders
If you install the edl tool per instructions it should include that file as well.
If that fails might be totally bricked or require one of the boxes to revive it.

---

draekko said:
I can't do that the phone is sealed up now and can't be thrown back into edl mode.
Try the loaders github repo for edl, 0005f0e100310000_2cf7619a278d2607_fhprg_peek.bin should theoretically be the right one. https://github.com/bkerler/Loaders
If you install the edl tool per instructions it should include that file as well.
If that fails might be totally bricked or require one of the boxes to revive it.
Click to expand...
Click to collapse
What I do not understand is that how to use firehose in that EDl script. After I connect the phone in edl mode than what ?