| Tool | Purpose | Key Scatter Requirement |
|------|---------|--------------------------|
| SP Flash Tool v5.x / v6.x | Flashing, readback, format | Scatter file mandatory |
| MTK Client | Bypass brom auth, read partitions without preloader | Scatter optional but useful for region calc |
| Wwr MTK + MTK Extractor | Generate scatter from a full ROM dump | Uses partition table discovery |
| Python – mtk-scatter | Parse/extract addresses programmatically | python mtk-scatter.py --info scatter.txt |
A typical MT6768 scatter file contains multiple partition entries. Below are critical ones you will encounter during real work:
| Partition Name | Typical Start Address (Hex) | Typical Size | Purpose |
|----------------|----------------------------|--------------|---------|
| preloader | 0x0 | 256KB–512KB | First-stage bootloader (hardware init, DRAM init) |
| pgpt | 0x0 (sector 0) | 1 sector | Primary GPT (if using GPT partitioning) |
| proinfo | 0x80000 | 3MB | Production info (IMEI, MAC, calibration) |
| lk | 0x200000 | 1MB | Little Kernel bootloader (fastboot, display init) |
| boot | 0x2800000 | 32–64MB | Kernel + ramdisk (boot image) |
| recovery | 0x2A00000 (example) | 32–64MB | Recovery image (if separate) |
| system | 0x4C00000 | 3–4GB | Android system image |
| vendor | dynamic (after system) | 1–2GB | Vendor-specific blobs |
| userdata | last logical partition | remaining | User data + internal storage |
| tee1 / tee2| varies | 2–5MB each | Trusted Execution Environment (OP-TEE) | mt6768 scatter file work
Note: Actual addresses vary per OEM build. Always use the scatter file extracted from your exact firmware package.
| Error | Fix |
|-------|-----|
| STATUS_EXT_RAM_EXCEPTION | Wrong scatter or DA mismatch |
| STATUS_BROM_CMD_SEND_DA_FAIL | Preloader version mismatch |
| S_BROM_CMD_STARTCMD_FAIL | Driver/connection issue, try another USB port |
| ERROR : Not match scatter | Scatter doesn’t match device’s GPT – extract from same firmware |
| Partition size mismatch | Edit scatter to match readback or real partition size from /proc/partitions | | Tool | Purpose | Key Scatter Requirement
Even with the correct scatter file, things can go wrong. Here are the most common issues and how to resolve them:
To work safely and effectively with an MT6768 scatter file, you need the right toolkit: Note: Actual addresses vary per OEM build
When you hit "Download" in SP Flash Tool, the scatter file helps the DA (Download Agent)—a small piece of code running on the MT6768’s internal SRAM—negotiate the correct protocol. The DA uses the scatter file’s block_size and page_size parameters to manage NAND writes efficiently.
| Error Message | Likely Cause | Fix |
|---------------|--------------|-----|
| STATUS_SCATTER_FILE_INVALID | Missing [PROGRAM] section or bad format | Validate with Notepad++ / compare to known working file |
| ERROR: S_FTHND_NO_SCATTER_FILE | No scatter selected | Load one before any operation |
| STATUS_DEVICE_CTRL_EXCEPTION | Preloader mismatch – wrong scatter for this device’s partition count | Extract scatter from device’s own ROM using readback + MTK Extractor |
| Partition [tee2] not found | Scatter defines more partitions than hardware | Comment out or delete missing partition entry |
