Xml File For Sp Flash Tool Direct

Below is a real example of an XML scatter file for a MediaTek device (e.g., MT6765):

<?xml version="1.0" encoding="UTF-8"?>
<MTK_ROM_INFO>
  <PHYSICAL_DEVICE>EMMC</PHYSICAL_DEVICE>
  <PARTITION_SIZE>0x1C2000000</PARTITION_SIZE>
</MTK_ROM_INFO>

<PARTITION_CONFIG>
<PARTITION>
<NAME>preloader</NAME>
<ADDR>0x0</ADDR>
<SIZE>0x400000</SIZE>
<FILE>preloader_mt6765.bin</FILE>
<IS_DOWNLOAD>true</IS_DOWNLOAD>
<TYPE>BOOT_1</TYPE>
</PARTITION>


<PARTITION>
<NAME>pgpt</NAME>
<ADDR>0x0</ADDR>
<SIZE>0x200000</SIZE>
<FILE>pgpt.bin</FILE>
<IS_DOWNLOAD>true</IS_DOWNLOAD>
<TYPE>NORMAL</TYPE>
</PARTITION>


<PARTITION>
<NAME>boot_para</NAME>
<ADDR>0x3a00000</ADDR>
<SIZE>0x100000</SIZE>
<IS_DOWNLOAD>false</IS_DOWNLOAD>
<TYPE>NORMAL</TYPE>
</PARTITION> xml file for sp flash tool


<!-- Common partitions -->
<PARTITION>
<NAME>boot</NAME>
<ADDR>0x4a00000</ADDR>
<SIZE>0x2000000</SIZE>
<FILE>boot.img</FILE>
<IS_DOWNLOAD>true</IS_DOWNLOAD>
<TYPE>NORMAL</TYPE>
</PARTITION>


<PARTITION>
<NAME>system</NAME>
<ADDR>0x6a00000</ADDR>
<SIZE>0x100000000</SIZE>
<FILE>system.img</FILE>
<IS_DOWNLOAD>true</IS_DOWNLOAD>
<TYPE>NORMAL</TYPE>
</PARTITION>


<PARTITION>
<NAME>userdata</NAME>
<ADDR>0x106a00000</ADDR>
<SIZE>0x80000000</SIZE>
<FILE>userdata.img</FILE>
<IS_DOWNLOAD>true</IS_DOWNLOAD>
<TYPE>NORMAL</TYPE>
</PARTITION>
</PARTITION_CONFIG>
 Below is a real example of an XML

| Tool | File Type | Purpose | |------|-----------|---------| | SP Flash Tool | .txt / .xml (scatter) | MediaTek devices | | Odin (Samsung) | .pit + .tar.md5 | Exynos/Qualcomm Samsung | | MiFlash (Xiaomi) | .bat + flash_all.sh | Qualcomm Xiaomi | | Fastboot | No config (manual commands) | All semi-modern Android devices |

Unlike Odin’s binary PIT format, SP Flash Tool’s XML scatter file is plain text. This makes it more flexible but also easier to corrupt accidentally. | Tool | File Type | Purpose |

<?xml version="1.0" encoding="UTF-8"?>
<SPFlashToolConfig>
    <ScatterVersion>1.0</ScatterVersion>
    <Platform>MT6765</Platform>
    <Target>alps</Target>
    <Partitions>
        <Partition>
            <Name>preloader</Name>
            <FileName>preloader.bin</FileName>
            <Address>0x0</Address>
            <Region>boot1</Region>
        </Partition>
        <Partition>
            <Name>lk</Name>
            <FileName>lk.bin</FileName>
            <Address>0x400000</Address>
            <Region>emmc_user</Region>
        </Partition>
        <Partition>
            <Name>boot</Name>
            <FileName>boot.img</FileName>
            <Address>0x800000</Address>
            <Region>emmc_user</Region>
        </Partition>
        <Partition>
            <Name>system</Name>
            <FileName>system.img</FileName>
            <Address>0x2000000</Address>
            <Region>emmc_user</Region>
        </Partition>
        <Partition>
            <Name>userdata</Name>
            <FileName>userdata.img</FileName>
            <Address>0x10000000</Address>
            <Region>emmc_user</Region>
        </Partition>
    </Partitions>
</SPFlashToolConfig>

Note: Real scatter files are usually in a plain text format with PARTITION sections, not XML. SP Flash Tool mainly uses scatter.txt files. XML is rare — only certain OEMs or versions support it. Let me know if you actually need the standard scatter file format.

To prevent SP Flash Tool from flashing a partition (e.g., nvram), change its <type> from NORMAL to BYPASS:

<partition type="BYPASS" id="nvram" name="nvram">

The tool will ignore it during download.

The scatter file is a configuration file (written in XML or a structured text format) that tells SP Flash Tool how to flash firmware (ROM) onto a MediaTek (MTK) Android device. It describes the partition layout of the device's flash memory (eMMC / UFS).

Note: Older versions used a .txt scatter file. Newer SP Flash Tool versions (V5.x+) use an XML-based scatter file (e.g., MTxxxx_Android_scatter.xml).

Back
Top