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

Search This thread

steadfasterX

Recognized Developer
Nov 13, 2013
5,666
14,994
263
Do you know if lglaf could be used? I was hoping it could be used to install a twrp to my mtk8+ plus as it connects but so far i get fails on every command.

Has any one had any luck getting it to work on a nougat device. If one had made a copy of the start sectors and end sectors of thier partitions its seems that one could flash the back ups made from salt and restore a device.

Its really driving me crazy that i have collected every firehose and sahara file needed to use qfil and or qdl but so far i cant get anything to work.
depends on the LAF protocol version (open SALT, find it in the main menu). everything higher then 3 might not work or at least need more work in the lglaf backend.

What if we had to or could build the prog_emmc_firehose.mbn files ourselves.
well. the thing here is not the programmer itself. it is more that it must be signed with a certificate accepted by the PBL. which you do not have (as long as you do not get private key leaked).

anyways that kind of developer discussions is not at the right place here. this thread is about a guide for users unbricking without any QFIL stuff. I would like to see that other discussion in a separate thread, thanks.

.-
 

ryu_hayabusa

Member
May 29, 2012
22
8
0
Calicut
After i completed the process plugin the Card and turned it on,
there is only boot loop at this time phone (LG logo comes shows message "secure boot error 1006")
doesn't get detected in USB(nothing in dmesg, nothing in windows also)
If you keep pressing "vol up" recovery mode logo comes with a "secure boot error 1006" message, nothing gets detected in USB at this time also.
Tried with Sandisk 32 GB (29.7) and Samsung (29.8) Cards.
If i don't put the sd card it will get detected in USB as 9008 mode. (no display)
https://ibb.co/qRJTzKZ
https://ibb.co/DVdFPJc

Also i dint get any KDZ files for v21 AT&T, therefore i downloaded the TOT file for v21 and extracted it using lg extract tool. Then followed rest of this tutorial, like using dd to flash gpt , sbl etc

Any solutions ?


A bit of flashback
This was AT&T locked phone
Somebody flashed a rom (probably V10 and phone was probably v21) bam :crying: 9008 mode no display.
Was trying QFIL method previously, it would stop on error after sending firehorse programmer.
Device g4(h810)
 
Last edited:

UsualNoise

Senior Member
Jan 20, 2013
50
6
0
I picked up a bricked LG G4 from eBay (VS986) and I was wondering what you suggest I try to install for the firmware since I can't check the current ARB number. Or is there a way to check when in 9008 mode? It doesn't show up in SALT as a connected device.
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,666
14,994
263
I picked up a bricked LG G4 from eBay (VS986) and I was wondering what you suggest I try to install for the firmware since I can't check the current ARB number. Or is there a way to check when in 9008 mode? It doesn't show up in SALT as a connected device.
No ARB check possible in 9008 mode



Sent from my OnePlus 6T using XDA Labs
 

UsualNoise

Senior Member
Jan 20, 2013
50
6
0
Question on the instructions in the OP. It states that the SD card files have to match the ARB value of the installed firmware on the phone and if the ARB of the phone is higher than the SD card it won't work. My question is: will it / should it work if the ARB value on the SD card is higher than the the phone?

I'm trying to determine if I need to try a different firmware set or if the phone is just dead beyond repair. I attempted the SD card using bootloader files from an ARB 02 firmware and it did not work. Should I try an ARB 01 set next? Or should it have worked if the ARB of the phone was lower? Thanks for any input.
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,666
14,994
263
Question on the instructions in the OP. It states that the SD card files have to match the ARB value of the installed firmware on the phone and if the ARB of the phone is higher than the SD card it won't work. My question is: will it / should it work if the ARB value on the SD card is higher than the the phone?

I'm trying to determine if I need to try a different firmware set or if the phone is just dead beyond repair. I attempted the SD card using bootloader files from an ARB 02 firmware and it did not work. Should I try an ARB 01 set next? Or should it have worked if the ARB of the phone was lower? Thanks for any input.

ARB means physical fuses get blown just by booting. It does not matter when booting from flash or sdcard. Fuses get blown in either way.

Next: you cannot boot a lower ARB then the current / last booted one.

If the method does not work it can have several reasons not just ARB . The very first thing is that the gpt is not flashed correctly, or the sdcard is too small sized , or you haven't flashed the full bootloader stack. Then ofc ARB is important as described above but sometimes trying just another firmware helps. Frankenstein devices are also something which can cause a lot of trouble (i.e. refurbished and swapped mainboards) ... And well there is more..



Sent from my OnePlus 6T using XDA Labs
 

UsualNoise

Senior Member
Jan 20, 2013
50
6
0
ARB means physical fuses get blown just by booting. It does not matter when booting from flash or sdcard. Fuses get blown in either way.

Next: you cannot boot a lower ARB then the current / last booted one.

If the method does not work it can have several reasons not just ARB . The very first thing is that the gpt is not flashed correctly, or the sdcard is too small sized , or you haven't flashed the full bootloader stack. Then ofc ARB is important as described above but sometimes trying just another firmware helps. Frankenstein devices are also something which can cause a lot of trouble (i.e. refurbished and swapped mainboards) ... And well there is more..

Thank you, that was very helpful. I'm confident I performed the SD card stuff correctly as I previously resurrected a LG G4 VS986 last year doing the same procedure (and same bootloader files). I used a 64 GB SD card and a 32 GB SD card (in that order) just to make sure the card was working. I also tried stock bootloader (first) and UsU variation (second). I know it's going to the SD card slot because when connected to a PC it does not show up in 9008 mode. When I take out the SD card and connect then 9008 shows up again.

Bottom line, I'm pretty sure something is simply broken / fried on the phone beyond a normal hard brick. Thanks for your feedback and all the great tools you provide!
 

summy1977

Member
Feb 5, 2019
14
0
0
Si I'm newbie help me please.

How to unbrick by sdcard from 9008 without QFIL

This method works ONLY for qualcomm devices (ANY non-UFS!!) which are in QDL/EDL/9008 mode!

This method does *not* work for UFS devices (so not for the G5 or later). Details:


If your device is not detected like that when connected the external sdcard method will NOT work for you.
You could force the sdcard mode by following post #2

Hint --> If you have no sdcard and own a H815 device (only then) you can make use of these validated QFIL process here

Requirements

  • 1) Ok first of all what you need is Linux. I highly recommend FWUL ( https://bit.do/FWULatXDA ) but any Linux is sufficient if you can handle it.

  • 2) LG models only: you need the latest SALT version ( https://bit.do/SALTatXDA ) which is already included since FWUL v2.5 (one of the reasons why I recommend FWUL).
    If you decide to use FWUL and start SALT it should prompt you when an updated SALT version is available. To be sure: just click the Update button in SALT once started.

  • 3) you need an external sdcard which is (to be sure) bigger then your internal storage (the sdcard must have the same size of your internal storage! so in theory a 32GB card should work fine but some cards are sold as 32GB but the real size is less , i.e. 29 GB). Thats the most critical part here as the GPT will be invalid if it does not fit with the sdcard. you can't edit the GPT though as then internal checksum may fail and so it will not work to boot from the sdcard. so ensure you have a bigger sized sdcard to workaround any issues related to this.

  • 4) Another important requirement for that external sdcard is: speed! If you want to ensure that you do not struggle ensure it is at least a class 10 card with UHS. It MIGHT work without UHS and it MIGHT work even on slower cards down to class 4 but when the storage is too slow the device rejects to boot from it as it ran into timeouts and so marking the sdcard as "not good enough" to boot from it.
    Of course you can first try a lower speed sdcard but if you encounter issues here then it is likely related to the speed of the sdcard.

  • 5) you need a 100% matching firmware (e.g a KDZ on LG's) for your device model - and very important: with a matching ARB of your current installed firmware!
    If your current installed firmware has a higher ARB then the one you flash on the sdcard it will NOT work!
    Find out what ARB means here https://bit.do/antirollg4



Steps

  • 1. Boot FWUL (or ur personal Linux)

  • 2. Start SALT - ensure that it is v3.5 or higher

  • 3. Extract the firmware file (e.g KDZ) but usually not all partitions are needed - just the bootloader stack
    (depends on your device - the following is for any LG G4 model):
    • Primary GPT
    • sbl1
    • aboot
    • pmic
    • rpm
    • tz
    • laf
    • sdi
    • hyp

    If you have not all or any of these (first check the note about UFS above) then you must identify your bootloader stack first.
    A good start for this is here: https://lineageos.org/engineering/Qualcomm-Firmware but you may have to just try and error here.
    For a quick & dirty try: flash every partition which is smaller then 150 MB (i.e. leave out system, cache, userdata and such).

  • 4. Clean dmesg by opening a terminal and type:
    Code:
    sudo dmesg -c >> /dev/null

  • 5. Connect your external sdcard to FWUL

  • 6. Type this in the terminal:
    Code:
    dmesg
    and find the connect messages there pointing to the device name. usually you see something like "mmcblk0" but sometimes it's different named like sdc or sdd or similar.
    We do not need the pXX here. So if you see mmcblk0p1 we need only mmcblk0. If you see a sdc1 or sdd1 we just need sdc or sdd without the number.

  • 7. The device name is needed now! Ensure it has the correct size by typing this in the terminal:
    Code:
    sudo fdisk -l /dev/mmcblk0
    (replace mmcblk0 if you your device is named different in step 6).
    This is important because the next step will erase your sdcard completely!
    All your data get lost!
    So if you choose the wrong one you may overwrite your PC storage in worst case! So double check this before proceeding.
    You can do so by disconnecting the sdcard and if the command in this step gives a message about the device cannot be found - connect device again and re-do the above command. if it shows then again your device all is fine

  • 8. Now flash the GPT (partition table) to your device in a terminal:

    Change into the folder where you extracted the backup. If you leaved the default on SALT it's /tmp/extracteddz:

    Code:
    cd /tmp/extracteddz 
    sudo -s 
    dd if=PrimaryGPT.gpt of=/dev/mmcblk0 (replace mmcblk0 if you your device is named different in step 6)
    sync
    hint: do not close the terminal

  • 9. Disconnect the sdcard and connect it again

  • 10. Now flash the rest in a terminal:

    First check if the GPT has been flashed fine:
    Code:
    ls -la /dev/disk/by-partlabel/

    if you get nothing as a result or an error message something went wrong. Go back to step 4!

    Move to the folder where you extracted the backup. If you leaved the default on SALT it's /tmp/extracteddz:

    Code:
    cd /tmp/extracteddz

    LG G4 - ONLY - Flashing instructions for locked or official unlocked phone (If you UsU'd your device skip this!)
    Code:
    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
    
    [B][COLOR="Red"][SIZE="4"]sync[/SIZE][/COLOR][/B] 
    
    Do [B][U]not forget[/U][/B] that last ("sync") command!! Otherwise it will very likely not work!

    LG G4 - ONLY - Flashing instructions for an UsU'd device
    Besides the KDZ extract you also need to grab the UsU unlock zip of your device model first then do this:
    Code:
    dd if=sbl1.bin of=/dev/disk/by-partlabel/sbl1 
    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=sdi.bin of=/dev/disk/by-partlabel/sdi
    dd if=laf_UsU.img of=/dev/disk/by-partlabel/laf
    dd if=aboot_UsU.img of=/dev/disk/by-partlabel/aboot 
    dd if=rawres_UsU.img of=/dev/disk/by-partlabel/raw_resources 
    
    [B][COLOR="Red"][SIZE="4"]sync[/SIZE][/COLOR][/B]
    
    Do [B][U]not forget[/U][/B] that last  ("sync") command!! Otherwise it will very likely not work!

  • 11. Now everything is prepared. Take out your sdcard. Take out the battery and disconnect cable. Plugin the external sdcard. Put battery back.
    Start the device in fastboot mode and use fastboot flash partition imagename.img

    If there is no fastboot possible open the download mode.

    For example on the LG G4:
    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 e.g. LGup (or for Samsung, ODIN etc) for unbricking by flashing a regular firmware on it (beware of the ARB again).


Have fun! :highfive:

Support / IRC Channel
IRC means Internet Relay Chat and you will get best support there only.
Personally I'm online there from Mondays to Fridays only but there are maybe others (maybe YOU too) who can help as well.

Choose how to get in:
  • FWUL v3.1 or later: just click the IRC hexchat icon on the desktop
  • PC (HexChat and Pidgin are only 2 of them! This list is not complete!)
  • Android (Yaaic, AndChat, HoloIRC, AndroIRC are only a few of them! This list is not complete!)
  • Web (KiwiIRC-Web,Freenode-Webchat])
  • When you have to choose a channel it is: #carbonfusion-user
  • When you be asked for a server network choose: freenode
  • It wouldn't hurt to read this as well when you are new to IRC: beginners guide (for a quick one read just: "Etiquette")
    Simplified said: be polite, don't ask to ask, be patient(!), respect the timezones, help others.

,-

ARB means physical fuses get blown just by booting. It does not matter when booting from flash or sdcard. Fuses get blown in either way.

Next: you cannot boot a lower ARB then the current / last booted one.

If the method does not work it can have several reasons not just ARB . The very first thing is that the gpt is not flashed correctly, or the sdcard is too small sized , or you haven't flashed the full bootloader stack. Then ofc ARB is important as described above but sometimes trying just another firmware helps. Frankenstein devices are also something which can cause a lot of trouble (i.e. refurbished and swapped mainboards) ... And well there is more..



Sent from my OnePlus 6T using XDA Labs

I have f500l korean version. Pc detected 9008 please help me recover. Maybe you have QFIL file because this sdcard method is very difficult for me :crying:
 

skorpien

Member
Dec 14, 2006
7
0
0
Would this method work for a Samsung SM-T350? It seems like it should work as it is in QDL 9008 mode, but I get stuck at creating the GPT on the SD card (my firmware files don't contain a PrimaryGPT.gpt file).

I do have a partitions.xml file for my tablet. Is there any way to use this to create the GPT on the SD card?
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,666
14,994
263
Would this method work for a Samsung SM-T350? It seems like it should work as it is in QDL 9008 mode, but I get stuck at creating the GPT on the SD card (my firmware files don't contain a PrimaryGPT.gpt file).

I do have a partitions.xml file for my tablet. Is there any way to use this to create the GPT on the SD card?
No Samsung seems to be different in many ways. In general the principal is identical as you can recover by sdcard but you need to search for

sboot sdcard unbrick
(sboot is the important part here)

Gl



Sent from my OnePlus 7T Pro using XDA Labs
 

alvinprimo

Senior Member
May 30, 2010
161
12
48
No Samsung seems to be different in many ways. In general the principal is identical as you can recover by sdcard but you need to search for

sboot sdcard unbrick
(sboot is the important part here)

Gl



Sent from my OnePlus 7T Pro using XDA Labs
Possible for LG G5 v987 stuck on 9008 mode? No download mode, no recovery, no fastboot
 

anton vier

New member
Feb 14, 2021
3
0
1
hi SteadfasterX, thanks for the work and patience

does this method work with xiaomi Redmi note 5a (codename Ugg)?

thanks in advance and sorry for my lazy english. :)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 23
    How to unbrick by sdcard from 9008 without QFIL

    This method works ONLY for qualcomm devices (ANY non-UFS!!) which are already in QDL/EDL/9008 mode!

    This method does *not* work for:
    • Samsung devices in general.
      Details:
      Samsung is doing things completely different while ofc a qcom based Samsung works with the same principal as "normal" devices. Just the process of building an hnbrick sdcard is different as you can get the pit (partition list) by heimdall but not a flashable gpt. Instead search for "sboot sdcard unbrick" or "sboot sdcard <your model>" . The important part here is "sboot" as that one will be loaded by the iROM when flashed properly (+other stuff).

    • UFS devices (so not for the G5 or later).
      Details:
      9008 bricks are not fixable on UFS NAND devices by booting from an SD card. The boot path is stored in QFPROM (on the CPU) and it is something like /dev/block/sdb or /dev/block/sde. On eMMC devices, the boot path is /dev/block/mmcblk0. If you have a 9008 brick, the SD card is seen as /dev/block/mmcblk0 so the phone will boot from it on an eMMC device since that IS the boot path. There is no way to make the SD card appear as /dev/block/sdX. And there is no way to change the boot path once you have a 9008 brick without a firehose. If you have a signed firehose, then you can fix your phone without needing an SD card As for cross flashing. I checked the RSA signature for the H930, H932, H933, and US998 and they are all different. If you flash any of the signed firmware (xbl, abl, hyp, modem, etc) from one of those devices, then you have a 9008 brick and no way to fix it yourself.I didn't bother checking the Verizon or Sprint models since they are even more locked down than the H932 is, but it appears from reading this thread that they have the same key as the US998 (I am not going to waste my time checking).-- Brian

    If your device is connected and not detected like that the external sdcard method will NOT work for you.
    On the LG G4 you can force the sdcard mode by following post #2 . I guess every device has a way to force that mode so google is your friend.

    Hint --> If you have no sdcard and own a H815 device (only then) you can make use of these validated QFIL process here

    Requirements

    • 1) Ok first of all what you need is Linux. I highly recommend FWUL ( https://bit.do/FWULatXDA ) but any Linux is sufficient if you can handle it.

    • 2) LG models only: you need the latest SALT version ( https://bit.do/SALTatXDA ) which is already included since FWUL v2.5 (one of the reasons why I recommend FWUL).
      If you decide to use FWUL and start SALT it should prompt you when an updated SALT version is available. To be sure: just click the Update button in SALT once started.

    • 3) you need an external sdcard which is (to be sure) bigger then your internal storage (the sdcard must have the same size of your internal storage! so in theory a 32GB card should work fine but some cards are sold as 32GB but the real size is less , i.e. 29 GB). Thats the most critical part here as the GPT will be invalid if it does not fit with the sdcard. you can't edit the GPT though as then internal checksum may fail and so it will not work to boot from the sdcard. so ensure you have a bigger sized sdcard to workaround any issues related to this.

    • 4) Another important requirement for that external sdcard is: speed! If you want to ensure that you do not struggle ensure it is at least a class 10 card with UHS. It MIGHT work without UHS and it MIGHT work even on slower cards down to class 4 but when the storage is too slow the device rejects to boot from it as it ran into timeouts and so marking the sdcard as "not good enough" to boot from it.
      Of course you can first try a lower speed sdcard but if you encounter issues here then it is likely related to the speed of the sdcard.

    • 5) you need a 100% matching firmware (e.g a KDZ on LG's) for your device model - and very important: with a matching ARB of your current installed firmware!
      If your current installed firmware has a higher ARB then the one you flash on the sdcard it will NOT work!
      Find out what ARB means here https://bit.do/antirollg4



    Steps

    • 1. Boot FWUL (or ur personal Linux)

    • 2. LG models only: Start SALT - ensure that it is v3.5 or higher

    • 3. Extract the firmware file (e.g KDZ) but usually not all partitions are needed - just the bootloader stack
      (depends on your device - the following is for any LG G4 model):
      • Primary GPT
      • sbl1
      • aboot
      • pmic
      • rpm
      • tz
      • laf
      • sdi
      • hyp

      If you have not all or any of these (first check the note about UFS above) then you must identify your bootloader stack first.
      A good start for this is here: https://lineageos.org/engineering/Qualcomm-Firmware but you may have to just try and error here.
      For a quick & dirty try: flash every partition which is smaller then 150 MB (i.e. leave out system, cache, userdata and such).

    • 4. Clean dmesg by opening a terminal and type:
      Code:
      sudo dmesg -c >> /dev/null

    • 5. Connect your external sdcard to FWUL

    • 6. Type this in the terminal:
      Code:
      dmesg
      and find the connect messages there pointing to the device name. usually you see something like "mmcblk0" but sometimes it's different named like sdc or sdd or similar.
      We do not need the pXX here. So if you see mmcblk0p1 we need only mmcblk0. If you see a sdc1 or sdd1 we just need sdc or sdd without the number.

    • 7. The device name is needed now! Ensure it has the correct size by typing this in the terminal:
      Code:
      sudo fdisk -l /dev/mmcblk0
      (replace mmcblk0 if you your device is named different in step 6).
      This is important because the next step will erase your sdcard completely!
      All your data get lost!
      So if you choose the wrong one you may overwrite your PC storage in worst case! So double check this before proceeding.
      You can do so by disconnecting the sdcard and if the command in this step gives a message about the device cannot be found - connect device again and re-do the above command. if it shows then again your device all is fine

    • 8. Now flash the GPT (partition table) to your device in a terminal:

      Change into the folder where you extracted the backup. If you leaved the default on SALT it's /tmp/extracteddz:

      Code:
      cd /tmp/extracteddz 
      sudo -s 
      dd if=PrimaryGPT.gpt of=/dev/mmcblk0 (replace mmcblk0 if you your device is named different in step 6)
      sync
      hint: do not close the terminal

    • 9. Disconnect the sdcard and connect it again

    • 10. Now flash the rest in a terminal:

      First check if the GPT has been flashed fine:
      Code:
      ls -la /dev/disk/by-partlabel/

      if you get nothing as a result or an error message something went wrong. Go back to step 4!

      Move to the folder where you extracted the backup. If you leaved the default on SALT it's /tmp/extracteddz:

      Code:
      cd /tmp/extracteddz

      LG G4 - ONLY - Flashing instructions for locked or official unlocked phone (If you UsU'd your device skip this!)
      Code:
      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
      
      [B][COLOR="Red"][SIZE="4"]sync[/SIZE][/COLOR][/B] 
      
      Do [B][U]not forget[/U][/B] that last ("sync") command!! Otherwise it will very likely not work!

      LG G4 - ONLY - Flashing instructions for an UsU'd device
      Besides the KDZ extract you also need to grab the UsU unlock zip of your device model first then do this:
      Code:
      dd if=sbl1.bin of=/dev/disk/by-partlabel/sbl1 
      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=sdi.bin of=/dev/disk/by-partlabel/sdi
      dd if=laf_UsU.img of=/dev/disk/by-partlabel/laf
      dd if=aboot_UsU.img of=/dev/disk/by-partlabel/aboot 
      dd if=rawres_UsU.img of=/dev/disk/by-partlabel/raw_resources 
      
      [B][COLOR="Red"][SIZE="4"]sync[/SIZE][/COLOR][/B]
      
      Do [B][U]not forget[/U][/B] that last  ("sync") command!! Otherwise it will very likely not work!

    • 11. Now everything is prepared. Take out your sdcard. Take out the battery and disconnect cable. Plugin the external sdcard. Put battery back.
      Start the device in fastboot mode and use fastboot flash partition imagename.img

      If there is no fastboot possible open the download mode.

      For example on the LG G4:
      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 e.g. LGup (or for Samsung, ODIN etc) for unbricking by flashing a regular firmware on it (beware of the ARB again).


    Have fun! :highfive:

    Support / TG group

    Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here.

    Note:
    be polite, don't ask to ask, be patient(!), respect the timezones, help others.


    ,-
    8
    Force SDCARD boot

    How-To force booting from sdcard (LG G4 only) (e.g. when the device is NOT in 9008 / QDL mode)

    You may know the 2-pin-bridge method which can enforce the 9008/QDL mode (on the back of the main board which is shown when disassembling the back cover).
    Now you may think: you can enforce that mode by bridging these pins and then you could boot from sdcard as this guide here says 9008 mode is a requirement.

    The answer is: NO. This will NOT work!

    But there seems to be a way (which I personally never have tested!) to force that sdcard boot by doing the following.

    Be aware: You do this on your own risk! Do not cry if something is failing/destroyed/whatever. Its totally up to you to proceed or not but its on your own risk like always when following guides.

    • prepare the sdcard as described in the above guide
    • insert the sdcard in the device
    • remove battery of the device
    • unplug usb cable
    • disassemble the back cover by loosen all screws
    • disassembling the mainboard like described here: fixit guide
    • on the FRONT of the mainboard find 5 (DAT0) and 6 (GND) as shown in the picture:
      ground_pin-5-and-6.jpeg
    • bridge these both and while bridging plugin the usb cable - WITHOUT TOUCHING anything with your fingers/body/soul on the mainboard!!!!
    • Keep thumbs pressed.. it may work if you flashed the correct files, with a matching ARB, in a correct way and [fill-on-on-whoever-u-believe-in] is with you
    3
    https://bpaste.net/show/eebc27d1975e
    it's happens with all sd, they are 16gb and 32gb class 10 extreme kingstone, i also created with gparted a partition and i made the process but nothing happens
    Keep in mind that there is a thanks button. Anyways you are using a 16GB SD card which I explained will not work please read the OP again

    Sent from my LG-H815 using XDA Labs
    3
    it seems either ubuntu 17.10 messes something up or salt 3.6-6 stable can't find partitions and i've downloaded two different h812 kdz.

    This is happening to me too?

    upload the log after extracting a KDZ:
    advanced menu -> Logfile -> upload button -> share the link
    2
    marzsalim said:
    5. Connect sdcard with mobile ? Or sdcard just connect to pc? Please reply to me

    Like I wrote to FWUL so yes to your PC where FWUL is running





    Sent from my LG-H815 using XDA Labs
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone