FORUMS
Remove All Ads from XDA

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

4,966 posts
Thanks Meter: 13,309
 
By steadfasterX, Recognized Developer on 13th February 2018, 11:38 AM
Post Reply Email Thread
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:
Quote:

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 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/sbl1
    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
    Flashing instructions for any 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
    
    sync 
    
    Do not forget that last ("sync") command!! Otherwise it will very likely not work!


    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 
    
    sync
    
    Do not forget 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!

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.

,-
The Following 18 Users Say Thank You to steadfasterX For This Useful Post: [ View ]
13th February 2018, 11:39 AM |#2  
steadfasterX's Avatar
OP Recognized Developer
Thanks Meter: 13,309
 
Donate to Me
More
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:
    Click image for larger version

Name:	ground_pin-5-and-6.jpeg
Views:	2384
Size:	178.5 KB
ID:	4454585
  • 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
The Following 8 Users Say Thank You to steadfasterX For This Useful Post: [ View ]
15th February 2018, 07:35 AM |#3  
steadfasterX's Avatar
OP Recognized Developer
Thanks Meter: 13,309
 
Donate to Me
More
Quote:
Originally Posted by marzsalim

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
The Following 2 Users Say Thank You to steadfasterX For This Useful Post: [ View ]
18th February 2018, 05:18 PM |#4  
commandervadeo's Avatar
Member
Flag Ottawa
Thanks Meter: 13
 
More
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.
The Following User Says Thank You to commandervadeo For This Useful Post: [ View ] Gift commandervadeo Ad-Free
23rd February 2018, 04:41 AM |#5  
Member
Thanks Meter: 29
 
More
Quote:
Originally Posted by commandervadeo

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?
The Following User Says Thank You to Shepxda For This Useful Post: [ View ] Gift Shepxda Ad-Free
23rd February 2018, 08:18 AM |#6  
steadfasterX's Avatar
OP Recognized Developer
Thanks Meter: 13,309
 
Donate to Me
More
Quote:
Originally Posted by commandervadeo

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.

Quote:
Originally Posted by Shepxda

This is happening to me too?

upload the log after extracting a KDZ:
advanced menu -> Logfile -> upload button -> share the link
The Following 3 Users Say Thank You to steadfasterX For This Useful Post: [ View ]
24th February 2018, 12:18 AM |#7  
Member
Thanks Meter: 29
 
More
Quote:
Originally Posted by steadfasterX

upload the log after extracting a KDZ:
advanced menu -> Logfile -> upload button -> share the link

No, you see, when you select the KDZ and the location to extract to, no partitions are available to choose from. It's just a blank page
24th February 2018, 08:24 AM |#8  
steadfasterX's Avatar
OP Recognized Developer
Thanks Meter: 13,309
 
Donate to Me
More
Quote:
Originally Posted by Shepxda

No, you see, when you select the KDZ and the location to extract to, no partitions are available to choose from. It's just a blank page

Yes. After this do what I said above. Give me the log.



Sent from my LG-H815 using XDA Labs
The Following User Says Thank You to steadfasterX For This Useful Post: [ View ]
5th March 2018, 11:00 PM |#9  
Member
Thanks Meter: 3
 
More
Hi, I have an H811 bricked this way, as it is bricked, I cannot check antirollback on phone's android.

On the rear label (the one with serial number near to battery) I can see model (H811) and it says H/W 1.0, S/W V10d

I search and saw that there is not V10d kdz for H811, is that data useful? Which kdz will be the best choice to use?
6th March 2018, 07:39 AM |#10  
steadfasterX's Avatar
OP Recognized Developer
Thanks Meter: 13,309
 
Donate to Me
More
Quote:
Originally Posted by birry

Hi, I have an H811 bricked this way, as it is bricked, I cannot check antirollback on phone's android.

On the rear label (the one with serial number near to battery) I can see model (H811) and it says H/W 1.0, S/W V10d

I search and saw that there is not V10d kdz for H811, is that data useful? Which kdz will be the best choice to use?

do you remember at least if you had installed Android marshmallow or lollipop? Any chance that you have made a TWRP backup in the past? Or did you never unlocked your device?

Sent from my LG-H815 using XDA Labs
6th March 2018, 09:23 AM |#11  
Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by steadfasterX

do you remember at least if you had installed Android marshmallow or lollipop? Any chance that you have made a TWRP backup in the past? Or did you never unlocked your device?

Sent from my LG-H815 using XDA Labs

Never upgraded Android, I guess it was lollipop. No backups or unlock also, it just bootlooped and I bricked it trying to install a H812 image with lgup (I know which image I tried if it is useful, I remember editing a value because lgup was refusing to install h812 image on the h811, I didn't find h811 image for lgup bootloop flashing fix).

This was my reference when I destroyed the phone

https://www.reddit.com/r/lgg4/commen...le_tool_guide/
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes