Repair Services

Using our detailed step by step tutorials, you could repair and recover your smartphones including iPhone, Android, BlackBerry, Windows and Nokia smartphones.


Either your device is built on Qualcomm or MTK Chipset, SPD or Apple's As chipsets, all you have to do is find the right tutorials within our phones' repair guides.

How to Create msimage.mbn File Flashable Via QFIL, MiFlash, Other Qualcomm Tools

How to Create msimage.mbn Flashable Via QFIL, MiFlash, Other Qualcomm Tools MSIMAGE.mbn which is usually in the formats 8660_msimage.mbn, 8210_msimage.mbn, 8974_msimage.mbn etcetera are Qualcomm image files required by some Qualcomm flash and unbrick tools such QFIL, MiFlash, Tool Studio, GNQC, HW-OneKey amongst others.

Each of these Qualcomm flash and unbrick tools uses this msimage.mbn file to identify and map correctly, the specific Qualcomm device whose firmware is to be loaded or flashed.

This msimage.mbn file is created from the stock firmware file partitions of a particular Qualcomm device and named accroding to the Qualcomm device SoC. E.g an LG D325 that is powered by a Qualcomm MSM8210 chipset will have 8210_msimage.mbn as its boot image/msimage file name.
Create XXXX_msimage.mbn file for your Qualcomm Device

Now, since most Qualcomm devices stock firmware are not distributed with these XXXX_msimage.mbn file in the, how can you create one specific for your Qualcomm device? This is the focus of these tutorial. Here, I discuss how to build XXXX_msimage specific your Qualcomm android device.

How to Build, Create or Make XXXX_msimage (e.g 8660_msimage) for Qualcomm Device

1. Download and install QPST 2.7.366 or higher version on your PC. You can download All QPST Versions from here.
2. Make a new empty folder on your PC then, copy and paste sbl1/sbl2/sbl3/rpm/tz images to the newly created folder.
3. copy the emmcswdownload.exe which can be loacted in:
C:\Program Files\Qualcomm\QPST\bin

to this newly created folder.
4. Prepare partition_boot.xml using NotePAD++. In the partition_boot.xml file, contain this info:
DO NOT ALTER THIS CODE AT ALL!

http://www.aryk.space/Jr -Mega Download Link
http://www.aryk.space/Js -Mediafire Link

!For one reason or another, the XML could not be displayed on the major browsers, so, I created one, uploaded it and those are the download links above.

5. Save the partition_boot.xml file you just created then, copy and paste it into the same folder you created in the step 2 above.
6. Now, Run the emmcswdownload.exe in terminal/Command Prompt using the command below:
emmcswdownload.exe -f 8660_msimage.mbn -x partition_boot.xml -s 1G -g 4M

7. On successfull run, the XXXX_msimage.mbn will be generated in the folder. You may then move the file to the appropriate folder where it is needed.

Do You Get it Right?
Donate. Please, consider a donation if I have helped you.
Get Premium. Do you still have issues? Become a premium follower to get persionalized assistance.
Get ABC Package. Do you practice phone software repairs, you need ABC Package.

Recommended:

91 comments:

  1. Replies
    1. What's the response you received? Check the previous page where you commented. I have responded to your comment.

      Delete
  2. this tells me that the image tag is no longer supported

    ReplyDelete
    Replies
    1. Yes. It will always throw that error if you use very recent QPST versions. You should use any QPST between 2.7.3X (where X equals any figures).

      Delete
  3. how to create partition_boot.xml with partition_boot you have upload

    ReplyDelete
    Replies
    1. Just follow the step by step instructions as prescribed therein.

      Delete
  4. Where do you get the SBL1 SBL2 SBL3 RPM & TZ images? I'm using Nexus 6P and was able to find .img files for ABOOT CMNLIB HYP KEYMASTER PMIC RPM SBL1 SDI TZ RADIO VENDOR which is rare because Google distributes software via flashable files from fastboot. Is this where to get those files or another location?

    ReplyDelete
    Replies
    1. Since there are different CPUs/Chipset, looking for exactly the same file(s) is not necessary, what is, however, is getting equivalent files. If I have your IMEI, I might get your official stock ROM and work on it myself and then, test it.

      Delete
    2. I tagged you in a post on Google+. Send me an email and I'll reply with IMEI.

      Delete
  5. im not able to download xml file can you provide another link the links r not working

    ReplyDelete
  6. CExParsePartition
    -x : error parsing partition description file: Document error on element type "root" and name/value " tag no longer supported"

    How can i solve this?

    ReplyDelete
  7. http://www.aryk.space/Jr paste this in the browser to download

    ReplyDelete
  8. http://www.aryk.space/Jr paste this in the browser to download

    ReplyDelete
  9. C:\Program Files (x86)\Qualcomm\QPST\bin>-f = 8210_msimage.mbn
    -x = partition_boot.xml
    -s = 1073741824
    -t =
    -f : Beginning image build...
    -x : Parsing partition description file...
    CExParsePartition
    -x : error parsing partition description file: Document error on element type "root" and name/value " tag no longer supported"

    ReplyDelete
  10. Buenas amigo necesito una factory firmware para qpst LG K371, se me murio uno egradando con z3x y quedo en QSloader 8008... por favor amigo +584126891627 y correo lfcs04012011@gmail.com

    ReplyDelete
  11. I'm having HTC one m8 sprint
    Can you get me the files please

    ReplyDelete
  12. Hi:

    I am trying to generate an .MBN file from the stock Marshmallow .KDZ file for the LG G4 H812, so thanks for creating this tutorial. Unfortunately, I find your instructions somewhat confusing.

    1) Step 1 says "Download and install QPST 2.7.366 or higher ...". Please note that some recent versions of QPST, including QPST v2.7.460, fail to work for this method. These versions yield the error:

    x : error parsing partition description file: Document error on element type "root" and name/value " tag no longer supported"

    However, the error is avoided when using QPST v2.7.366. For details, see: http://kernel-develop.blogspot.ca/2012/05/qpst-emergency-download-support.html

    2) Step 2 says "Make a new empty folder on your PC then, copy and paste sbl1/sbl2/sbl3/rpm/tz images to the newly created folder." Do you mean: copy the image files sbl1.img, etc. that have been extracted from the .KDZ file? If so, this generates an error when the emmcswdownload.exe command is run, displayed in the following lines:

    Writing file "sbl1.mbn" to file partition at 0x0000000000000200
    Failed to open input file. [sb1.mbn]

    The source of the error can be traced to the lines in partition_boot.xml, which refers to .mbn files, not .img files, e.g.:

    file name="sbl1.mbn" offset="0"

    Changing the extensions of the .img files to .mbn avoids this error, but generates a further error for me:

    Writing file "sbl1.mbn" to file partition at 0x0000000000000200
    File sbl1.mbn too large for 512000 byte partition

    For the Marshmallow .KDZ file for the LG G4 H812, the size of sbl1.img is 1024 KB, which as the error indicates, is too large for the specified partition size. Is sbl1.img the correct file to use? Is it simply to be renamed sbl1.mbn? If not, does sbl1.img need to be converted somehow to sbl1.mbn first? In addition, do the partition sizes specified in partition_boot.xml need to be increased to accommodate the size of the .img files?

    3) The partition_boot.xml file refers to 2 secondary bootloader image files that are not present in my .KDZ file. Specifically, my .KDZ file contains only sbl1.img, but not sbl2.img or sbl3.img. Should reference to these files be removed from partition_boot.xml? Or should sbl1.img be copied to create these missing files?

    Thanks for your help.

    John

    ReplyDelete
    Replies
    1. Hello John,
      First, I'd love to say a big thank you for your observation and such a detailed comment.

      Q1 Answer:
      The support for this method of creating the partition.xml file had been dropped from QPST v2.7.366 and higher. Therefore, using this method with them will always yield various errors.

      Q2 Answer:
      1. All sbl.img files have to be converted to .mbn file first.
      2. .img and .mbn formats have different conversion levels hence, the difference in size. Converting your file(s) to the appropriate format will avoid all sizes related errors.
      3. Adjusting (increasing or decreasing) the partition file size in partition...xml file will avoid the errors and let you flash your device but will end up having a SUPER BRICK device hence, this is not an option.

      Q3 Answer:
      Other (excess) sbl file in the partition...xml file can be safely ignored.

      I hope I have answered your questions. If you require further assistance, do not hesitate to comment again.

      Delete
  13. Hi:

    Here's a quick addendum to my previous post, providing a bit more information, in case you or other readers are interested.

    The LG G4 H812 is the Canadian variant of the LG G4 (with a locked bootloader) and is using the Qualcomm MSM8992 board with chipset P1.

    The .KDZ file I'm using is H81220x_00_1122.kdz, which is Marshmallow (6.0) for the carrier Bell Mobility/Virgin Mobile, software version H81220x.

    I extracted the .IMG image files from the .KDZ file using WindowsLGFirmwareExtract Release 1.2.5.0.

    I was able to generate an .MBN file with your method using emmcswdownload.exe from QPST v2.7.366, by modifying the partition_boot.xml file you provided, and renaming the .IMG files to extension .MBN. As I explained previously, only 1 of the 3 secondary bootloader files that you specify are contained in the .KDZ file: sbl1.img. I modified your original partition_boot.xml file by removing references to the additional partitions for sbl2 and sbl3, and then increasing the sizes specified for the partitions.

    The partition sizes specified in the partition_boot.xml file depend, among other things, on the sizes of the input files to be written to the .MBN file. The relevant image files I extracted, sbl1.img, rpm.img, and tz.img have sizes 1024 KB, 512 KB, and 1024 KB respectively. I note that about the last half of each file is zero-filled, so the actual data occupies far less space than the file size indicates. This is the modified partition_boot.xml file that I used to create my output file 8992_msimage.mbn:

    <?xml version="1.0"?>
    <image>
    <physical_partition number="0">
    <primary order="1" type="4d" bootable="true" label="SBL1" size="2048" readonly="false">
    <file name="sbl1.mbn" offset="0"/>
    </primary>
    <primary order="2" type="5" bootable="false" label="EXT" size="3072">
    <extended order="1" type="47" label="RPM" size="1024" readonly="false">
    <file name="rpm.mbn" offset="0"/>
    </extended>
    <extended order="2" type="46" label="TZ" size="2048" readonly="false">
    <file name="tz.mbn" offset="0"/>
    </extended>
    </primary>
    </physical_partition>
    </image>

    Of course, whether the file I produced in this manner is actually useful in unbricking an LG G4 H812 is another question entirely. I note that it is substantially different than the file prog_emmc_firehose_8992_lite_lge.mbn which I recently examined.

    John

    ReplyDelete
    Replies
    1. The reason for the difference(s) have been given in your previous comment. Please check it.

      Delete
  14. Hi,
    I'm a little new on this but I am trying to create the msimage for my leeco lepro 3 elite (x722) as I couldn't find any qfil for this phone yet.
    I downloaded the stock rom from the official Le Eco site and tried to follow your instructions but I was not able to find the sbl1/sbl2/sbl3 images.
    I also didn't find any .KDZ file so I'm a bit lost here.
    I have a recovery rom for x720 which is almost the same phone but with a different chipset (821 instead of 820)
    I really appreciate some kind of hint or idea you can give me.
    Cheers
    Santi

    ReplyDelete
    Replies
    1. .KDZ file is an extension for LG stock ROM firmwares therefore, this tutorial cannot work for your LeeCo devices. However, you may report your phone case on our facebook page at http://facebook.com/aryktech maybe a dedicated page maybe made for your device here on ArykTECH

      Delete
    2. Thanks a lot for your reply!

      Delete
  15. Hi, how are you, I've seen your tutorial and I find it excellent.
    Tenog A lgh635c and good is dead, but when I connect it comes Qualcomm HS-USB QDLoader 9008 good try everything but this method is good but I do not know if you will have a method for this device Thanks.

    ReplyDelete
  16. Buenas tardes. primero darte gracias x l tutorial... pero no puedo crear la imagen msimage.mbn para mi lg d390ar. serias tan gentil de proporcinarme la imagen? la pc solo me lo reconoce como QUALCOMM HS-USB QDLOADER 9008. o quizas los archivos para uarlos en QFIL? desde ya muchas gracias x todo.

    ReplyDelete
    Replies
    1. Realmente no entiendo su comentario, pero aquí está QFIL Tutorial: Flash with QPST QFIL

      Delete
    2. Hola buenas noches Gracias x responder mi comentario... tratare de explicarme mejor.
      Tengo un LG modelo(d390ar) el cual no da señal de vida, la pc solo me lo
      reconoce como (Qualcomm hs-usb qdloader 9008)
      Tengo entendido que QFIL usa 3 archivos de extencion XML, los cuales
      no puedo encontrar los adecuados para mi modelo en la red.
      prog_emmc_firehosexxxx.mbn,rawprogram0.xml y patch0.xml...
      Si fueras tan amable de facilitarme estos 3 archivos para mi modelo de lg.
      O indicarme como crearlos. estaria muy agradecido con usted.

      Delete
    3. Gracias por la explicación. He dado las guías paso a paso sobre cómo crear el archivo .mbn específico para su dispositivo en este tutorial. ¿Puede señalar el aspecto específico del tutorial con el que tiene problemas?
      En cuanto a los archivos firehose_emmc, marque aquí:eMMC ufs Firehose Files

      Delete
  17. I cant create .mbn file for lg v10 h960A with that methode chipset is m8992 to have the rawprogram0.xml and path please can someone help me please

    ReplyDelete
    Replies
    1. See LG V10 specific unbrick guide on our Unbrick section from the navigation menu.

      Delete
  18. hi sir can u make it for samsung galaxy grand prime sm 530h/ds thank you...

    ReplyDelete
    Replies
    1. Alright. Will be made and added to ArykTECH shortly.

      Delete
    2. Hi can u provide me the link for the files, I also have grandprime w/c needs to be fixed w these method, pls

      Delete
  19. Hi can you make it for lg g pad 10.1 thanks

    ReplyDelete
  20. Hi can anyone help me with vizio tablet xr6m10 mm8916 snapdragon 410soc .mbn ?

    ReplyDelete
    Replies
    1. The information you have provided is not correct. Please review it.

      Delete
  21. i get this error,how do i solve thiss :unable to open primary document entity..

    ReplyDelete
  22. Hey,

    I'm trying to build 8996_msimage.mbn for a google pixel but I don't have sbl1-3 in the factory images.
    Is it possible they are named differently for me?
    aboot, apdp, boot, bootloader-sailfish-8996-012001-1706221457, bootlocker, cmnlib32, cmnlib64, devcfg, hosd, hyp, keymaster, modem, pmic, radio-sailfish-8996-013053-1706271859, rpm, system, system_other, tz, vendor and xbl are .img files I have in the factory image folder.


    Thank you.

    ReplyDelete
    Replies
    1. This method is not supported by your device. You need to read directly from the device to get an accurate file map.

      Delete
  23. Hi sir, I have bricked my Huawei KIW-L21. its in state 9008(Takes only drivers of these).I have tried to make file as per instruction . its created but still can not flash and its incomplete file. Need help Please need its qfil file to make alive my phone.

    8936_msimage

    partition_boot

    RPM

    SBL1

    TZ

    I only get these files and missing much. need help.




    Thanks
    Br, Raja

    ReplyDelete
  24. Hi sir,
    This is error while file making.
    C:\Users\Ali\Desktop\Qfil file\New folder>-f = 8636_msimage.mbn
    -x = partition_boot.xml
    -s = 1073741824
    -g = 4194304
    -f : Beginning image build...
    -f : XML parse complete
    -f : writing output file
    Begin MBR at 0x0000000000000000
    prtn 0 at 0x00000000000001be: bootable 0x80, type 0x4d, 1st sect 0x00000001, siz
    e 0x00000146
    prtn 1 at 0x00000000000001ce: bootable 0x00, type 0x05, 1st sect 0x00000147, siz
    e 0x001ffeb9
    MBR disk signature 0xfffffffe, signature bytes 0x55 0xaa
    Writing file "sbl1.mbn" to file partition at 0x0000000000000200
    Failed to open input file
    -f : operation completed

    Please need help

    Thanks
    Br, Raja

    ReplyDelete
    Replies
    1. Hi,
      I think that you have to rename the 3 files extensions from .img to .mbn

      Delete
  25. Hi,

    I have an H818P G4 model (with Qualcomm MSM8994)

    After following this tutorial,
    I noticed that the output file size of 8994_msimage.mbn is 9.00 Mo is it normal ?

    I'm planning for weeks to use QFil, but i need the two more files :
    - patch0.xml
    - rawprogram0.xml

    How can i get them ?

    Please Help me

    Thanks

    ReplyDelete
    Replies
    1. Yes. The output files size is normal. As for the other 2 files, visit our Facebook page.

      Delete
    2. Hi
      I can't find them
      Upload them please

      Delete
  26. This comment has been removed by the author.

    ReplyDelete
    Replies
    1. It appears this is a repetition of your message on our facebook page to which a response have been given.

      Delete
  27. hi sir can u make it for samsung galaxy grand prime sm 530h/ds thank you...

    ReplyDelete
  28. This comment has been removed by the author.

    ReplyDelete
  29. -x = partition_boot.xml
    -s = 1073741824
    -t =
    -f : Beginning image build...
    -x : Parsing partition description file...
    CExParsePartition
    -x : error parsing partition description file: Xerces parse error: fatal error, line 1, col 1, "invalid document structure"
    me da este errror cual sera la solucion

    ReplyDelete
  30. I managed to brick my LG V20 (H910). I have a H91510e_00_VTR_CA_OP_1205.kdz but am not sure how to generate the needed files for the QFIL tool. Can you please advise? Thanks.

    ReplyDelete
    Replies
    1. For the step by step instructions on how to convert kdz files to QFIL flash files, see here: How to Convert KDZ Files to MBN or BIN Files

      Delete
  31. Hi.... This tutorial works for LG LS676????? I've one of this device in hard bricked mode, and i'm trying to repair it.....

    ReplyDelete
  32. Hello Sir. I got the LG G4 H815p that is bricked because of bad flash. i tried to create the mbn file for it but i get some error that the program can't start because xerces-c_3_1.dll is missing from your computer. Try installing the program to fix this problem. I don't seem to know the problem is coming from. Please is there any generated mbn file for the LG H815p available??? Thanks in advance and cheers for your great work. I love aryk.tech

    ReplyDelete
  33. Okay thanks for the quick reply. I will follow the link and the instructions. i have open the loader.img page that needs purchase but i can't seem to find the LG H815p. Is it contained inside the "ALL OTHERS" folder? i just wanna be sure its inside before purchase.

    ReplyDelete
  34. And in you reply comment above would the files for the H815 work for the H815p too??

    ReplyDelete
  35. i need the two more files :
    - patch0.xml
    - rawprogram0.xml

    How can i get them ?

    ReplyDelete
  36. i have samsung galaxy note edge(scl24) its going into Qloader 9008 how i can get those rawpatch.xml , firehose.mbn etc..
    please help

    ReplyDelete
    Replies
    1. Can you provide additional details? Or, you could also visit our facebook page for straight responses.

      Delete
  37. My LG V20 got 9008. And I tried to extracted bin files from dz but got 7 of PrimaryGPT_[0-7].bin and BackupGPT too. and these PrimaryGPT_* cant use with premium tool 2.4 from your. So I dont know what to do!! Please help

    ReplyDelete
  38. C:\Firehose>C:\Firehose>emmcswdownload.exe -f 8952_msimage.mbn -x partition_boot.xml -s 1G -g 4M
    DNS server not authoritative for zone.

    C:\Firehose>
    C:\Firehose>C:\Firehose>-f = 8952_msimage.mbn
    DNS server not authoritative for zone.

    C:\Firehose>-x = partition_boot.xml
    DNS server not authoritative for zone.

    C:\Firehose>-s = 1073741824
    DNS server not authoritative for zone.

    C:\Firehose>-t =
    DNS server not authoritative for zone.

    C:\Firehose>-f : Beginning image build...
    DNS server not authoritative for zone.

    C:\Firehose>-x : Parsing partition description file...
    DNS server not authoritative for zone.

    C:\Firehose>CExParsePartition
    DNS server not authoritative for zone.

    C:\Firehose>-x : error parsing partition description file: Document error on element type "root" and name/value " tag no longer supported"
    DNS server not authoritative for zone.

    ReplyDelete
  39. Hy, do you have somehow the files for an HTC 10?

    ReplyDelete
  40. Hello, can I re-mark the flash memory to restore the possibility of its firmware? There is a device with a defective flash, all attempts to fill the firmware are not crowned with success. I somewhere read that somehow you can perezmetkit memory to restore its performance, is it true?

    ReplyDelete
    Replies
    1. Honestly, your comment is not understood. Could you rephrase it?

      Delete
  41. Hi sir,
    This is error while file making.
    E:\ZTE\zte>-f = 8960_msimage.mbn
    -x = partition_boot.xml
    -s = 1073741824
    -t =
    -f : Beginning image build...
    -x : Parsing partition description file...
    CExParsePartition
    -x : error parsing partition description file: Document error on element type "root" and name/value " tag no longer supported"

    ReplyDelete
  42. can you created rawprogram0.xml and patch0.xml. for MSM8940 snapdragon 435 Zte nubia m2Play?

    ReplyDelete
  43. i cant find prog_emmc_firehose_8940 in google,please help me

    ReplyDelete
  44. Please provide the Samsung Galaxy core .mbn file
    And also provide rawprogram_unsparse_without_qcn.xml
    Patch0.xml
    Provide ASAP thanks

    ReplyDelete
  45. Tell me how to convert .md5 file to .mbn

    ReplyDelete
  46. MOTO E4 XT 1765 MSM 8917 QCOM
    i have unlock boot loader working fine on stock
    firmware version 7.1.1
    NCQ 26.69.46_cid22_subsidy-MPCS_regulatory. but not rooted working charm, after few day i have connected on wifi server suddenly i have received pop up OTA new security patch ready for install i have just installed this patch and my mobile going installing, then erasing after that now not showing anything i have hard brick my own phone with my little negligence.
    when i connected to pc just tray icon show HS_USB_Qdloader 9008 and only detected by flash.bat and Qualcomm Snapdragon Flash Tool

    plz help me out this headache

    Give me a correct blankflash file or Qfile please

    ReplyDelete
    Replies
    1. Hi,
      I am sorry but we do not currently have an unbrick project opened for the Moto E4. You may make a custom request on our facebook page though.

      Delete

Web Services
Web Design Services

For individuals willing to earning a living through blogging. For small businesses aiming to expand their customer base via the internet. For schools...


Whichever your course and your needs for a website or blog, we will give you the best you deserve.

Build Blogs

Be it on Blogspot or WordPress, we help you build the best and professionally looking blogs in no time!

Pull Traffic

Relying on the best SEO practices, we help you build the most traffic to your blogs and websites within a reasonable time frame.

Design Websites

For individuals, personal or small businesses, we have working solutions that'll certainly help your course.

We Re-design

Already have a blog or website you wish to re-design? We are always ready to attend your demand! Just visit our office or call us!

Unbrick Services
Phone Repairs

Access to the right files is the soul of phones software repairs. But we do not provide you files only. We also provide you the right tutorials to use the files.

At a very reasonable cost, you may gain access your device unbrick files in our archives.