[GUIDE][9008][EDL|QDL][QUALCOMM ONLY] Unbrick via external sdcard (no QFIL!)

[steadfasterX]

Yes. when I connect it to the pc with or without battery and without the sd card, the phone appears as Quectel QDLoader 9008

well Quectel is not Qualcomm so this will not work for you I guess.

 

[trqzhangkai]

Now flash:

dd if=sbl1.bin of=/dev/disk/by-partlabel/sbl1 
dd if=aboot.bin of=/dev/disk/by-partlabel/aboot 
dd if=hyp.bin of=/dev/disk/by-partlabel/hyp
dd if=pmic.bin of=/dev/disk/by-partlabel/pmic 
dd if=rpm.bin of=/dev/disk/by-partlabel/rpm 
dd if=tz.bin of=/dev/disk/by-partlabel/tz 
dd if=laf.bin of=/dev/disk/by-partlabel/laf 
dd if=sdi.bin of=/dev/disk/by-partlabel/sdi

sync

[*]11. Now everything is prepared. Take out your sdcard. Take out the battery and disconnect cable. Plugin the external sdcard. Put battery back.
Press volume up (only this) and keep it pressed.
Then connect USB cable while still keep the pressure on volume up for 20 seconds.
The download mode should come up. Congrats you can now use lgup to completely unbrick.
[/LIST]

Have fun! :highfive:

thank you giving us so nice guide,i have some qusetions to consult

1. I extracted my KDZ file by SALT 3.13 and the file's extension is ".image" not ".bin",i don't know if it is right.
2. i unlocked my phone by UsU, should i replace the code "dd if=aboot.bin of=/dev/disk/by-partlabel/aboot" by "dd if=aboot_UsU.img of=/dev/disk/by-partlabel/aboot"?
3. what's the next step if i flashed all the files and in download mode? as my understanding i can not use LGup tool to flash a KDZ rom.

 

[steadfasterX]

thank you giving us so nice guide,i have some qusetions to consult

1. I extracted my KDZ file by SALT 3.13 and the file's extension is ".image" not ".bin",i don't know if it is right.
2. i unlocked my phone by UsU, should i replace the code "dd if=aboot.bin of=/dev/disk/by-partlabel/aboot" by "dd if=aboot_UsU.img of=/dev/disk/by-partlabel/aboot"?
3. what's the next step if i flashed all the files and in download mode? as my understanding i can not use LGup tool to flash a KDZ rom.

yes this process differs when you have flashed UsU as you already found out/know.

reg. 1) nothing you need to care about. its just a file extension without any special meaning
reg. 2) correct. same goes for laf and raw_resources in the next step
reg 3) I would try to boot into fastboot instead of download mode and flash whats needed (e.g. system + boot + bootloader stack)
what exactly depends on what you have done to brick your phone. SALT v4 will support flashing KDZ files but up to then i guess fastboot is your best option.

EDIT:
I have updated the OP (step 10) so it should be more clear now

.

 

[trqzhangkai]

yes this process differs when you have flashed UsU as you already found out/know.

reg. 1) nothing you need to care about. its just a file extension without any special meaning
reg. 2) correct. same goes for laf and raw_resources in the next step
reg 3) I would try to boot into fastboot instead of download mode and flash whats needed (e.g. system + boot + bootloader stack)
what exactly depends on what you have done to brick your phone. SALT v4 will support flashing KDZ files but up to then i guess fastboot is your best option.

EDIT:
I have updated the OP (step 10) so it should be more clear now

.

thank you !

 

[christian2628]

Hi @steadfasterX
I installed [ROM][N][H811] DESPACITO-N-ROM v1.0[FULL STOCK] on my LG G4 H811 successfully but unfortunately it is currently in brick condition as "Qualcomm HS-USB QDLoader 9008"
I dismantled it and has my surprise grade on the motherboard it is marked that it is the model H810 instead of H811,whereas in the settings it was marked H811 with The T-MOBILE bootlogo when it turned on.
Can you help me solve my problem and make my LG work again ?

 

[steadfasterX]

Hi @steadfasterX
I installed [ROM][N][H811] DESPACITO-N-ROM v1.0[FULL STOCK] on my LG G4 H811 successfully but unfortunately it is currently in brick condition as "Qualcomm HS-USB QDLoader 9008"
I dismantled it and has my surprise grade on the motherboard it is marked that it is the model H810 instead of H811,whereas in the settings it was marked H811 with The T-MOBILE bootlogo when it turned on.
Can you help me solve my problem and make my LG work again ?

omg why setting the size of your whole text to ultra big?

You have a Frankenstein: check FAQ #21 here

So actually what wins is H810 as that is printed on your mainboard. but....
As you already found out: you CAN install a H811 system partition even on a H810. ...and even if not.. Its just a little text property which displays the model in Android settings. So what you see there means nothing at all. It can be tricked easily.

to make it even more complicated the H810 itself is a special model. There are users reported to be able to install a full h811 bootloader stack on it without bricking. So MAYBE you have really a bootloader stack of a h811 currently installed.

Regardless of the above the thing is: you need to know the ARB of your current bootloader stack. That means: what exact firmware was installed BEFORE you bricked it?
If you know the firmware version you can identify here (click) what ARB it has.

Most important I need to know:
- did you unlocked the device by UsU or by the fastboot oem unlock command?
- what have you done to get into the current 9008 state?

-

 

[christian2628]

omg why setting the size of your whole text to ultra big?

You have a Frankenstein: check FAQ #21 here

So actually what wins is H810 as that is printed on your mainboard. but....
As you already found out: you CAN install a H811 system partition even on a H810. ...and even if not.. Its just a little text property which displays the model in Android settings. So what you see there means nothing at all. It can be tricked easily.

to make it even more complicated the H810 itself is a special model. There are users reported to be able to install a full h811 bootloader stack on it without bricking. So MAYBE you have really a bootloader stack of a h811 currently installed.

Regardless of the above the thing is: you need to know the ARB of your current bootloader stack. That means: what exact firmware was installed BEFORE you bricked it?
If you know the firmware version you can identify here (click) what ARB it has.

Most important I need to know:
- did you unlocked the device by UsU or by the fastboot oem unlock command?
- what have you done to get into the current 9008 state?

-

Hi @steadfasterX, thanks for your answer
Before installing the rom and putting it in brick condition it had version 20R or 20V.
I unlocked the bootloader via the "fastboot oem unlock" command.
And for the "Qualcomm HS-USB QDLoader 9008" mode it comes on its own when connected to a computer, with or without the battery in it.
Strangely enough, one day I managed to turn it on for a few seconds in download mode and LGUP detected it as "H81130b", probably the rom I had installed and which put it in brick condition.
Also before installing the rom I made a backup via twrp, if that can help and here is what I could see in the build.prop that I extracted

ro.lge.swversion_arb=ARB03
ro.lge.swversion=H81120v
ro.lge.swversion_short=V20v
ro.lge.swversion_rev=0
ro.lge.factoryversion=LGH811AT-00-V20v-TMO-US-APR-25-2017-ARB03+0

Thank you. I hope I've shed more light on my problem.

 

[steadfasterX]

Hi @steadfasterX, thanks for your answer
Before installing the rom and putting it in brick condition it had version 20R or 20V.
I unlocked the bootloader via the "fastboot oem unlock" command.
And for the "Qualcomm HS-USB QDLoader 9008" mode it comes on its own when connected to a computer, with or without the battery in it.
Strangely enough, one day I managed to turn it on for a few seconds in download mode and LGUP detected it as "H81130b", probably the rom I had installed and which put it in brick condition.
Also before installing the rom I made a backup via twrp, if that can help and here is what I could see in the build.prop that I extracted

ro.lge.swversion_arb=ARB03
ro.lge.swversion=H81120v
ro.lge.swversion_short=V20v
ro.lge.swversion_rev=0
ro.lge.factoryversion=LGH811AT-00-V20v-TMO-US-APR-25-2017-ARB03+0

Thank you. I hope I've shed more light on my problem.

Great thx for your detailed answer that helps a lot!

Just to make it clear: the last thing you did were to flash that ROM right? Directly afterwards it was bricked or did it boot once (at least up to the LG logo)?


Sent from my LG-H815 using XDA Labs

 

[christian2628]

Great thx for your detailed answer that helps a lot!

Just to make it clear: the last thing you did were to flash that ROM right? Directly afterwards it was bricked or did it boot once (at least up to the LG logo)?


Sent from my LG-H815 using XDA Labs

Hello @steadfasterX
The rom had successfully installed and the phone turned on correctly, I could manipulate it for a few moments and then a message appeared to say that an application stopped working and went off to start only in qualcomm mode.

 

[steadfasterX]

Hello @steadfasterX
The rom had successfully installed and the phone turned on correctly, I could manipulate it for a few moments and then a message appeared to say that an application stopped working and went off to start only in qualcomm mode.

well that's what I feared.

the chance is about 90% that you got catched by the ilapo. sorry.
Read this FAQ here:
14) I have unlocked with UsU and all went fine. I flashed a ROM and it bootloops and now my phone died!! What have you done with my device? It never had this issue before in the last years!?

this FAQ is about UsU but its true for any model, unlocked officially or by UsU.

You CAN try to boot using this method described in this OP here and do the whole process with a h811 KDZ of 20V plus using a modified boot image as described here in the X cores guide
good luck

.

 

[christian2628]

well that's what I feared.

the chance is about 90% that you got catched by the ilapo. sorry.
Read this FAQ here:
14) I have unlocked with UsU and all went fine. I flashed a ROM and it bootloops and now my phone died!! What have you done with my device? It never had this issue before in the last years!?

this FAQ is about UsU but its true for any model, unlocked officially or by UsU.

You CAN try to boot using this method described in this OP here and do the whole process with a h811 KDZ of 20V plus using a modified boot image as described here in the X cores guide
good luck

.

Hi @steadfasterX, thanks for answering me
Is a motherboard change possible with an H818 ?

 

[steadfasterX]

Hi @steadfasterX, thanks for answering me
Is a motherboard change possible with an H818 ?

in theory yes. keep in mind that h818 cant be unlocked (neither officially nor by UsU).

 

[christian2628]

in theory yes. keep in mind that h818 cant be unlocked (neither officially nor by UsU).

Would that mean I couldn't install a custom rom on it ?

 

[steadfasterX]

Would that mean I couldn't install a custom rom on it ?

if you mean: TWRP, AOSCP, LOS, .. exactly. This will NOT work.

 

[christian2628]

if you mean: TWRP, AOSCP, LOS, .. exactly. This will NOT work.

Hi @steadfasterX Unfortunately the motherboard change with an H818P does not work.
The phone starts well but the screen remains completely black.
I used the method with Qfil and the different files that go with it but still the same but the H811 gave life sign after a long time with a missing battery screen that flashes again and again as on the pictures .
Any ideas?

 

[steadfasterX]

Hi @steadfasterX Unfortunately the motherboard change with an H818P does not work.
The phone starts well but the screen remains completely black.
I used the method with Qfil and the different files that go with it but still the same but the H811 gave life sign after a long time with a missing battery screen that flashes again and again as on the pictures .
Any ideas?

this is totally OT pls open an own thread for questions not matching to an existing topic

follow up here:
https://forum.xda-developers.com/g4...device-usu-t3760451/post76290181#post76290181

 

[itsme.Ronjie]

Sir this can fix deadboot? Newbie here

 

[Cisuwek]

[[email protected] aaa]$ sudo dmesg -c >> /dev/null
[sudo] password for android:
[[email protected] aaa]$ dmesg
[ 1098.146011] usb 1-1.3: new full-speed USB device number 12 using ehci-pci
[ 1098.507009] usb 1-1.3: new high-speed USB device number 13 using ehci-pci
[ 1098.586482] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[ 1098.587152] scsi host5: usb-storage 1-1.3:1.0
[ 1099.616258] scsi 5:0:0:0: Direct-Access Mass Storage Device PQ: 0 ANSI: 0 CCS
[ 1099.617946] sd 5:0:0:0: [sdc] 15728640 512-byte logical blocks: (8.05 GB/7.50 GiB)
[ 1099.618558] sd 5:0:0:0: [sdc] Write Protect is off
[ 1099.618560] sd 5:0:0:0: [sdc] Mode Sense: 03 00 00 00
[ 1099.619181] sd 5:0:0:0: [sdc] No Caching mode page found
[ 1099.619183] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[ 1099.625696] sd 5:0:0:0: [sdc] Attached SCSI removable disk
[[email protected] aaa]$ sudo fdisk -l /dev/sdc
Disk /dev/sdc: 7.5 GiB, 8053063680 bytes, 15728640 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device Boot Start End Sectors Size Id Type
/dev/sdc1 1 4294967295 4294967295 2T ee GPT
[[email protected] aaa]$ sudo -s
[fwul aaa]# dd if=PrimaryGPT.bin of=/dev/sdc
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0.149222 s, 3.5 MB/s
[fwul aaa]# sync
[fwul aaa]# dd if=hyp.bin of=/dev/disk/by-partlabel/hyp
dd: failed to open '/dev/disk/by-partlabel/hyp': No such file or directory

What am I doing wrong. I spend lot of time try to figure out, but know nothing
Tried with usu image too.

 

[steadfasterX]

[[email protected] aaa]
What am I doing wrong. I spend lot of time try to figure out, but know nothing
Tried with usu image too.

have you done this after flashing the GPT and doing the sync command?

9. Disconnect the sdcard and connect it again

if yes do this :

find /dev/ -name sbl1

maybe the path is different for you

 

[aliarslan007]

Thank you. Just need some further help.

I have followed the complete guide, and when everything else had failed (and I mean every other method mentioned on the internet), your method has woken my G4 H810. So first of all, thank you so much. You are a genius.

The problem I am facing is that my phone is not entering Download mode where I could use LgUp. My phone is stuck in Fastboot mode. And none of the fastboot commands are working except fastboot devices which shows that the device is attached.

Please help.