In the latest SP Flash Tool v6, the traditional .txt scatter file has been replaced by a more structured flash.xml file. This change allows the tool to handle more complex partition layouts and security requirements for modern MediaTek (MTK) chipsets. Core Structure of a V6 XML File
The flash.xml file is a configuration manifest that tells the tool what to flash and where. A typical structure includes:
Section: Contains global device info like the chip name (e.g., MT6765), storage type (NAND/EMMC/UFS), and the path to the Download Agent (DA).
: Lists every partition to be flashed. Each entry (ROM) includes: index: The partition ID.
enable: A true/false toggle for whether to flash that specific part. sp flash tool v6 xml file
file path: The location of the actual image file (e.g., boot.img, system.img).
Section: Defines pre-flash actions, such as auto-formatting flags (e.g., FormatAll or FormatNVRAM). How to Use the XML File
Preparation: Ensure you have the MTK VCOM Drivers installed so your PC can communicate with the device in BROM mode.
Load the XML: Open SP Flash Tool v6. Instead of "Scatter-loading," look for the "Download XML file" field and click "Choose" to select your flash.xml. In the latest SP Flash Tool v6 , the traditional
Configure: The tool will automatically populate the partition list based on the XML. Ensure "Download Only" is selected unless you are performing a full firmware upgrade.
Execute: Click "Download", power off your device, and connect it via USB. The progress bar will turn yellow as the files transfer. Key Differences from V5 SP Flash Tool v5 SP Flash Tool v6 Config File MTxxxx_Android_scatter.txt flash.xml Flexibility Rigid text-based format Dynamic XML structure Support Older MTK devices Modern 64-bit MTK chipsets Linux Support Often buggy/unstable Improved stability in v6
Note: You cannot simply rename a .txt scatter file to .xml. They are formatted differently. If your firmware only has a .txt scatter file, you must use SP Flash Tool v5.
SP Flash Tool v6 utilizes a flash.xml file to define firmware partitions, replacing the .txt scatter file format required by older v5 versions for newer MediaTek (MTK) chipsets. This XML structure is mandatory for handling complex partitioning and secure boot requirements (SLA/DAA) in modern devices, and it requires specific loading via the "Download-XML" field, rather than scatter-loading. Learn more about this process at Hovatek. A standard scatter XML file (e
A standard scatter XML file (e.g., scatter.xml) begins with a declaration and contains several key sections.
Check/uncheck partitions in GUI – tool reads XML and allows per-partition selection.
Most stock ROMs (in PAC, OZIP, or ZIP format) contain a scatter.xml file. Look inside the extracted firmware folder.
| Feature | Old .txt Scatter | XML Scatter (v6) | |--------|----------------|------------------| | Structure | Key-value pairs | Hierarchical XML | | Partition count | Limited | Extended (dynamic) | | 64-bit support | ❌ No | ✅ Yes | | Extra attributes | Basic | Full (region, type, flags) | | Validation | None | Schema-based | | Human readability | Moderate | Good (structured) | | Tool compatibility | Legacy SPFT | SPFT v6+ |
A typical MediaTek Android 11+ firmware folder:
firmware/
├── MT6785_Android_scatter.xml <-- Main XML scatter file
├── preloader.bin
├── boot.img
├── dtbo.img
├── vbmeta.img
├── super.img <-- Contains system, product, vendor
├── userdata.img
├── cache.img
└── ...