LG D605 HARD BRICK (How to build eMMC flash programmer MPRGXXXX.hex and msimage.mbn) - LG Optimus L3 II, L5 II, L7 II, L9 II

We need a developer who has a working lg l9 ii to create these files, i think...
How to generate the 8660_msimage.mbn
8660_msimage.mbn is released in SW by default, actually, it includes the all the boot images and partition table there. MPRG8660.hex will download this image and reset to mass-storage mode. If customers have different HW settings, such as GPIO/DDR, the default 8660_msimage.mbn may not work for them, so customers need build their own 8660_msimage.mbn by themselves with following ways.
1. Have the QPST 2.7.366 or higher version installed.
2. Make a local folder, copy sbl1/sbl2/sbl3/rpm/tz images to this folder.
3. copy the emmcswdownload.exe from C:\Program Files\Qualcomm\QPST\bin to this folder.
4. Prepare the partition_boot.xml as below and copy the partition_boot.xml to the same folder as above.
<?xml version="1.0"?>
<image>
<physical_partition number="0">
<primary order="1" type="4d" bootable="true" label="SBL1" size="1000" readonly="false">
<file name="sbl1.mbn" offset="0"/>
</primary>
<primary order="2" type="51" bootable="false" label="SBL2" size="3000" readonly="false">
<file name="sbl2.mbn" offset="0"/>
</primary>
<primary order="3" type="45" bootable="false" label="SBL3" size="1500" readonly="false">
<file name="sbl3.mbn" offset="0"/>
</primary>
<primary order="4" type="5" bootable="false" label="EXT" size="1000000">
<extended order="1" type="47" label="RPM" size="1000" readonly="false">
<file name="rpm.mbn" offset="0"/>
</extended>
<extended order="2" type="46" label="TZ" size="1000" readonly="false">
<file name="tz.mbn" offset="0"/>
</extended>
</primary>
</physical_partition>
</image>
5. Run the emmcswdownload.exe tool to create OEM boot image with a command below.
emmcswdownload.exe -f 8660_msimage.mbn -x partition_boot.xml -s 1G -g 4M
6. The 8660_msimage.mbn will be generated in the folder.
OR:
How to build eMMC flash programmer MPRGXXXX.hex and msimage.mbn?
1. Please check if the SConscript is provided in "modem_proc/core p/tools/emmcbld/bulid". If not, you cannot build it with this release.
2. set build environment by executing RVCTXX.bat in build/ms folder
3. go to "modem_proc/core/bsp/build"
4. execute "build emmcbld BUILD_ID=xxxxxxxx"
5. The generated image is located in modem_proc/build/ms/bin/EMMCBLD/
6. MPRGXXXX.hex is eMMC programmer used to communicate with QPST to download msimage.mbn into eMMC.
7. msimage.mbn is used to enumerate the device as a USB mass storage device for all the image updates.
Please refer to modem_proc/core/bsp/tools/emmcbld/bulid/SConscript for how emmcbld and msimage are built and generated.
Using command line to creat 7x30_msimage.mbn
The eMMC Software Download Tool can also be used in Command Line mode for factory automation and creating boot images.
First find the location of your QPST install, normally under C:\Program Files(x86)\Qualcomm\ 5 QPST\bin, that contains your emmcswdownload.exe file. You can either map this location to your 6 path or refer to it directly from the cmd window.
The following command line options are supported for emmcswdownload.exe:
-f <filename> : direct output to <filename> instead of selected device
-s <size enum> : mass storage device size = { “1G”, “2G”, “4G”, etc }
-g <size enum> : write protect group size = { “4M”, “8M”, “16M”, etc }
-x <filename> : partition description file
-p <directory> : search path = path1;path2;…. Etc
-L <filename> : list all connected mass storage drives to <filename>
-i <filename> : image file to write to mass storage device
-w <drive> : mass storage drive to write image file to
In this command line:
 –s and –g options are required, even if no sections are marked as read only
 –s size is only used to set the size of the last partition; it does not affect the size of the output image
 –g is the write-protect size for partitions marked as read only; if there are multiple read-only partitions, only the first and last partitions will be aligned on a protect size boundary
 –L only dumps to the output file, not to stdout
emmcswdownload -f \tmp\7x30_msimage.mbn -x E:\emmc\partition_boot.xml -s 1G -g 64M -p E:\emmc\;
Original Post: http://4pda.ru/forum/index.php?s=&showtopic=643084&view=findpost&p=43253768

---

This does not help at all

---

neutrondev said:
This does not help at all
Click to expand...
Click to collapse
Why? To revive the smartphone lacks only these two files

---

JackPOtaTo said:
Why? To revive the smartphone lacks only these two files
Click to expand...
Click to collapse
Ok try then. You can't make the files like that but try if you want. I just told you .

---

neutrondev said:
Ok try then. You can't make the files like that but try if you want. I just told you .
Click to expand...
Click to collapse
I wrote that we need a developer who has a working l9 II to build these files:cyclops:

---

JackPOtaTo said:
I wrote that we need a developer who has a working l9 II to build these files:cyclops:
Click to expand...
Click to collapse
You can't build it like that, I tell you again. No device with your socket was unbricked. If it was that easy someone would of made them. Don't trust everything you read on the internet.

---

neutrondev said:
You can't build it like that, I tell you again. No device with your socket was unbricked. If it was that easy someone would of made them. Don't trust everything you read on the internet.
Click to expand...
Click to collapse
Hi , I have Coolpad devce "Qiku Terra" MSM8992 and the device is hard bricked. I do not have the required files such as MPRG8992.mbn, 8992_msimage.mbn etc. Can you suggest some ways to unbrick it???.
As per a post on xda of Coolpad device if emmc image of working phone (same model) is written on a sd card using HDD Raw copy then the phone can boot in fastboot mode. You think this would work??
Can you also help me with the right code to get the emmc image's initial partitions?? I would appreciate your response.

---

No even emergency/download mode?

---

JackPOtaTo said:
<?xml version="1.0"?>
<image>
<physical_partition number="0">
<primary order="1" type="4d" bootable="true" label="SBL1" size="1000" readonly="false">
<file name="sbl1.mbn" offset="0"/>
</primary>
<primary order="2" type="51" bootable="false" label="SBL2" size="3000" readonly="false">
<file name="sbl2.mbn" offset="0"/>
</primary>
<primary order="3" type="45" bootable="false" label="SBL3" size="1500" readonly="false">
<file name="sbl3.mbn" offset="0"/>
</primary>
<primary order="4" type="5" bootable="false" label="EXT" size="1000000">
<extended order="1" type="47" label="RPM" size="1000" readonly="false">
<file name="rpm.mbn" offset="0"/>
</extended>
<extended order="2" type="46" label="TZ" size="1000" readonly="false">
<file name="tz.mbn" offset="0"/>
</extended>
</primary>
</physical_partition>
</image>
Click to expand...
Click to collapse
Can you give me more details? I have a bricked Huawei Y6 (SCL-L21) that has Qualcomm cpu and I have the original firmaware in UPDATE.APP format (huawei default) but I can extract almost every partition inside that file, so looking at your xml, I have sbl1, rpm and tz partition, so do I need to delete sbl2 and sbl3 entries? and one more thing... Do I have to change the size attribute?
Waiting for your reply, thanks

---

Hi, I have a rooted working d605. I can help if you give me instructions.

---

So the people in Japan using this method are wrong ?
The code is not exactly correct but the theory seems correct.

---

Just for info.
I found out that to build a msimage.mbn for your phone, That you have to use a older version of QPST, The newest version does not work.
I built a 8960_msimage.mbn that matches my phone using the old version, QPST 2.7.366
For some reason newer versions of emmcswdownload.exe fails when trying to build a image.
New versions are not always better versions... Look at Windows 10.