[LG V20 Questions & Answers] runningnak3d:
EDIT: I still need the partition listing, and there is still hope. I have a lead on the firehose_8996.mbn used to fix this very problem with the QFIL tool.

If I can get it, then I will need the partition layout in order to make the rawprogram0.xml file.

I am going to leave the post below because it WAS a good idea, and it does work on SD800, 801 and 808 chips. However ,this is no longer possible on 820 and above Snapdragon chips.

I decided to do some research on WHY there would be sda devices instead of mmcblk. sda is a DISK device, and mmcblk is a FLASH device. eMMC is flash. This is what I found...

From ehem's github:

The problem here is that you can't make an SDcard look like multiple whole disk block devices: sda, sdb, sdc, sdd, etc. or even mmcblk0, mmcblk1, etc. Without being able to do that, there is no way to create an image on an SDcard that the 820 chip will ever boot from.

I am not giving up hope. I know that the qfil files are out there (8996.mbn, recovery.xml and patch0.xml). Even if they are for another device, the XML files can be modified with information we can gain from a working V20.

Original post:

I am starting a new thread because I couldn't change the title of the last one, and there was a lot of "static".

So, I need someone with an H915 to run a couple of commands with the end result being that we will end up with an image that can be "burned" onto an SDcard, and recover from 9008 error bricks.

You will know you have a 9008 if your phone suddenly won't turn on, and nothing lights up when hooked to a PC. Another good indication (if you have Windows) is that it will say something like

qdloader / something / 9008 in device manager when the phone is connected (sorry, I use GNU/Linux, so I have no clue what the exact listing in device manager is).

This procedure will work on ANY Qualcomm Snapdragon based phone that has an SDcard slot, and I have successfully tested it on an LG G4, and an LG V10.

I was in the process of testing it on my V20, but my image was corrupt, and I ended up with a brick -- so now I turn to you.

This is for both the H915 and H910, but the reason I need an H915 is because there is a KDZ for the H915. The H910 and H915 are identical hardware.

So what are the risks to you? None as far as there being a risk to your phone, however, I could unintentionally have you send me sensitive data. For example, there is the EFS partition.

This contains your IMEI ... you don't want that out there. Also, there is the DATA partition. I think that one speaks for itself. However, I would never intentionally ask you to send me something,

but more importantly, if I did get something, it would be nulled. I will always list the risk of any command. For example: "Warning: This could contain the EFS partition!".

You can then decide if that is a risk you want to take.

The easiest thing by far would be for someone to just send me an entire dump of their eMMC, but as stated above, that would definitely contain sensitive info.

However, if there is a trusting soul out there that doesn't want to go through the pain below, please send me a PM ;)

So with that disclaimer in mind, I need to start with the partition layout since I don't currently have a working V20.

There is ZERO risk involved with this. It is just a list of the partitions that are on ALL H915 phones.

First need to get into recovery.

adb reboot recovery

Once the phone is sitting in TWRP you can get the partition listing. The thing is I am not sure of the device name. It is dependent on the kernel you are using.

It could be either mmcblk0 or sda OR something else.

To find out you can run:

adb shell
ls /dev/block

You will see a bunch of entries, but we need the "whole disk" block device (you can ignore single entries, loop* and ram*). So, if you see a bunch of mmcblk0pXX then you know it is mmcblk0.

If you see a bunch of sdaXX, then you know it is sda. Once you find out, you will execute (replacing mmcblk0 with the appropriate device if needed):

fdisk -l /dev/block/mmcblk0

or

fdisk -l /dev/block/sda

Once that is done, please copy and paste the output into a post here. To give you an idea if you are close, this is what it looks like on an LG V10:

[dev01:~/h901] $ adb reboot recovery
[dev01:~/h901] $ adb shell
~ # fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT

Disk /dev/block/mmcblk0: 122142720 sectors, 2296M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 56 entries
First usable sector is 34, last usable sector is 122142686

Number Start (sector) End (sector) Size Code Name
1 16384 192511 86.0M 0700 modem
2 192512 196607 2048K 0700 spare1
3 196608 197631 512K 0700 pmic
4 197632 199679 1024K 0700 sbl1
5 199680 201727 1024K 0700 tz
6 201728 202751 512K 0700 sdi
7 202752 203775 512K 0700 hyp
8 203776 204799 512K 0700 rpm
9 204800 208895 2048K 0700 aboot
10 208896 210943 1024K 0700 sbl1bak
11 210944 211967 512K 0700 pmicbak
12 211968 212991 512K 0700 hypbak
13 212992 215039 1024K 0700 tzbak
14 215040 216063 512K 0700 rpmbak
15 216064 220159 2048K 0700 abootbak
16 220160 221183 512K 0700 sdibak
17 221184 222207 512K 0700 limits
18 222208 223231 512K 0700 apdp
19 223232 224255 512K 0700 msadp
20 224256 225279 512K 0700 dpo
21 225280 229375 2048K 0700 spare2
22 229376 230399 512K 0700 persistent
23 230400 232447 1024K 0700 devinfo
24 232448 245759 6656K 0700 spare3
25 245760 278527 16.0M 0700 misc
26 278528 344063 32.0M 0700 persist
27 344064 347135 1536K 0700 modemst1
28 347136 350207 1536K 0700 modemst2
29 350208 353279 1536K 0700 fsg
30 353280 354303 512K 0700 fsc
31 354304 355327 512K 0700 ssd
32 355328 356351 512K 0700 keystore
33 356352 360447 2048K 0700 DDR
34 360448 361471 512K 0700 sec
35 361472 362495 512K 0700 encrypt
36 362496 363519 512K 0700 eksst
37 363520 364543 512K 0700 rct
38 364544 376831 6144K 0700 spare4
39 376832 475135 48.0M 0700 laf
40 475136 557055 40.0M 0700 boot
41 557056 638975 40.0M 0700 recovery
42 638976 659455 10.0M 0700 drm
43 659456 671743 6144K 0700 sns
44 671744 737279 32.0M 0700 mpt
45 737280 745471 4096K 0700 raw_resources
46 745472 753663 4096K 0700 raw_resourcesbak
47 753664 847871 46.0M 0700 factory
48 847872 851967 2048K 0700 spare5
49 851968 872447 10.0M 0700 fota
50 872448 901119 14.0M 0700 fau
51 901120 9674751 4284M 0700 system
52 9674752 12197887 1232M 0700 cache
53 12197888 122140671 52.4G 0700 userdata
54 122140672 122142686 1007K 0700 grow