Mt6833 Scatter File Work

In the world of Android firmware and low-level system recovery, the scatter file is arguably the most critical component after the firmware itself. For devices powered by the MediaTek MT6833 chipset—commonly known as the Dimensity 700—understanding how the scatter file works is not optional; it is essential.

Whether you are unbricking a device, porting a custom ROM, or performing a factory firmware restoration using tools like SP Flash Tool, the MT6833_Android_scatter.txt file dictates every byte written to the eMMC or UFS storage.

This article provides a deep dive into the MT6833 scatter file work—what it is, how it is structured, how partition addressing works on the Dimensity 700, and how to troubleshoot common errors.

After two nights of trial and error, here’s what finally got my MT6833 scatter file to flash correctly: mt6833 scatter file work

Analysis of a standard MT6833 scatter file reveals the following critical partitions:

| Partition Name | Typical Function | File Reference | Required for Boot? | | :--- | :--- | :--- | :--- | | preloader | Low-level bootloader (initializes DRAM) | preloader_mt6833.bin | Yes | | pgpt | Primary GPT (partition table) | pgpt.img | Yes | | proinfo | Production info (IMEI, MAC, serial) | proinfo.bin | No (but critical) | | lk | Little Kernel (2nd stage bootloader) | lk.bin | Yes | | boot | Linux kernel + ramdisk | boot.img | Yes | | vendor_boot | Vendor-specific boot image | vendor_boot.img | Yes | | super | Dynamic partition (system, product, vendor) | super.img | Yes | | userdata | User data partition (size varies) | userdata.img | No | | md_udc | Modem firmware (5G/4G baseband) | md1rom.img | Yes (for telephony) | | scp | Sensor Core Processor firmware | scp.img | No | | sspm | Secure System Power Management | sspm.img | Yes |

Example snippet from a scatter file:

- partition_index: 5
  partition_name: boot
  file_name: boot.img
  is_download: true
  type: NORMAL
  linear_start_addr: 0x5000000
  physical_start_addr: 0x5000000
  partition_size: 0x2000000

A scatter file is a plain-text configuration file that describes the partition layout of a device’s flash memory. It tells the flashing tool exactly where to write each image: the starting address (linear address), the partition size, the file name, and the region.

Why focus on MT6833? The MediaTek MT6833 (Dimensity 700) is a 7nm 5G chipset featuring:

Unlike older MediaTek chips (MT67xx, MT81xx), the MT6833 follows a modern Android 10/11/12 partition scheme, including dynamic partitions (super), vbmeta for Verified Boot, and gz or lz4 compressed images. Therefore, an MT6833 scatter file is more complex than legacy ones. To resize userdata :

A scatter file (usually named MT6833_Android_scatter.txt) is a partition layout table written in a simple, human-readable format. For the MT6833, it maps out all the logical partitions—from preloader and bootloader to userdata and super—assigning each a linear memory address range.

Why is this necessary? Unlike Qualcomm’s partition XML or Samsung’s PIT files, MediaTek’s proprietary SP Flash Tool relies on scatter files to perform low-level read/write operations on the eMMC or UFS storage. Without a correctly matched scatter file, the tool cannot locate the boot image, recovery, or even the basic preloader code.

Cause: The Download Agent (DA) stored in the scatter file’s _da region does not match the device’s boot ROM version. Fix: Use the Auth Bypass DA specifically for MT6833 or use a newer SP Flash Tool version extracted from the manufacturer’s OTA. Save the file with Unix line endings (LF, not CRLF)

Before you touch a scatter file, pull a full readback from your MT6833 device.
One wrong address in linear_start_addr and your IMEI, nvram, or nvdata is gone forever.