| Partition Name | Linear Start Addr | Size (Hex) | Size (MB) | Mount Point | Read-Only | Description |
|----------------|-------------------|------------|-----------|-------------|-----------|-------------|
| preloader | 0x0 | 0x40000 | 0.25 | - | Yes | First-stage bootloader – never flash unless recovering from dead boot |
| pgpt | 0x0 | 0x200000 | 2 | - | Yes | Primary GPT table |
| proinfo | 0x200000 | 0x300000 | 3 | - | Yes | Factory IMEI, MAC, serial (unique per device) |
| lk | 0x500000 | 0x200000 | 2 | - | Yes | Little Kernel (ABOOT) – bootloader UI, fastboot |
| boot | 0x700000 | 0x2000000 | 32 | /boot | Yes | Kernel + ramdisk (Android 12+ uses boot for GKI) |
| recovery | 0x2700000 | 0x2000000 | 32 | /recovery | Yes | Standalone recovery (A/B devices may omit) |
| dtbo | 0x4700000 | 0x800000 | 8 | - | Yes | Device Tree Blob Overlay |
| vbmeta | 0x4F00000 | 0x1000000 | 16 | - | Yes | AVB verification data |
| logo | 0x5F00000 | 0x1000000 | 16 | - | No | Boot logo (splash screen) |
| tee | 0x6F00000 | 0x500000 | 5 | - | Yes | Trusted Execution Environment (OP-TEE) |
| metadata | 0x7400000 | 0x2000000 | 32 | /metadata | No | Encrypt key, rollback protection |
| nvdata | 0x9400000 | 0x5000000 | 80 | /nvdata | Yes | Modem calibration, nvram |
| nvram | 0xE400000 | 0x500000 | 5 | - | Yes | WiFi/BT MAC, factory config |
| protect1 | 0xE900000 | 0xA00000 | 10 | - | Yes | Keystore, DRM (part1) |
| protect2 | 0xF300000 | 0xA00000 | 10 | - | Yes | Keystore, DRM (part2) |
| seccfg | 0xFD00000 | 0x200000 | 2 | - | Yes | Secure config (bootloader unlock flag) |
| expdb | 0xFF00000 | 0x400000 | 4 | - | No | Engineering exception database |
| vendor (via super) | dynamic | dynamic | varies | /vendor | Yes | Vendor HALs, blobs (logical in super) |
| product (via super) | dynamic | dynamic | varies | /product | Yes | Pixel-like product partition |
| system (via super) | dynamic | dynamic | varies | /system | Yes | Android framework |
| userdata | 0x2C000000 | 0x3A8000000 | ~14912 | /data | No | User apps, internal storage |
Note on dynamic partitions: Many MT6768 devices running Android 10+ use
super(logical volume). In such cases,system,vendor, andproductare not listed as physical partitions – onlysuperappears.
The MT6768 chip has a bottleneck: it initializes storage at 0x0 (preloader) then jumps to 0x80000 (pgpt). If your scatter file has gaps (e.g., 0x1a000 then 0x1d0000), the flash tool will waste milliseconds seeking—which adds up over 30 partitions. mt6768androidscattertxt better
How to make it better: Use contiguous addressing or align to 0x10000 boundaries. A well-optimized scatter file for MT6768 should look like this:
| Partition | Start Address | End Address | | :--- | :--- | :--- | | preloader | 0x0 | 0x40000 | | pgpt | 0x80000 | 0x84000 | | proinfo | 0x100000 | 0x108000 | | nvram | 0x180000 | 0x1f0000 | | Partition Name | Linear Start Addr |
Pro tip: Use the --align flag in MTK Droid Tools (if it worked for MT6768) or calculate using partition_size = next_start - current_start.
MT6768 has preloader, md1img, spmfw, scp, tee. A good scatter protects these by: Note on dynamic partitions : Many MT6768 devices
When users search for a "better" scatter file, they are usually trying to solve one of three problems: compatibility, partition size errors, or device bricking. Here is what distinguishes a mediocre scatter file from a superior one:
Let’s move from theory to action. Here are five specific modifications to upgrade your scatter file from "works sometimes" to "bulletproof."