While OEMs may customize layouts, a typical MT8163 scatter file includes these key partitions:
| Partition Name | Description | Typical Size | Volatility | |----------------|-------------|--------------|-------------| | preloader | First-stage bootloader; initializes DRAM. | ~256-512 KB | Critical | | pgpt | Primary GPT (GUID Partition Table). | 17 sectors | Critical | | proinfo | Contains factory data (serial, MAC, calibration). | 2-4 MB | Unique per device | | lk | Little Kernel – second-stage bootloader (fastboot). | 1-2 MB | Important | | boot | Linux kernel + ramdisk (boot image). | 16-32 MB | Modifiable | | recovery | Recovery environment (ADB, factory reset). | 16-32 MB | Modifiable | | secro | Secure data (DRM keys, widevine). | 2-8 MB | Critical | | system | Android OS (read-only). | 1-3 GB | Modifiable | | vendor | Vendor-specific blobs (if AOSP/treble). | 200-800 MB | Modifiable | | cache | Temporary system cache. | 256-512 MB | Wipeable | | userdata | User apps, settings, internal storage. | Remaining space | Wipeable | | tee1 / tees | Trusted Execution Environment (OP-TEE). | 4-8 MB | Critical |
A scatter file (usually named MT8163_Android_scatter.txt) is a partition layout table. It describes: mt8163 scatter file
Without this file, tools like SP Flash Tool or fastboot wouldn't know where to flash boot.img, recovery.img, or system.img.
Use SP Flash Tool’s “Read Back” with the scatter’s nvram partition address range (e.g., start 0x2a800000, size 0x500000). Save the raw file as nvram.bin. While OEMs may customize layouts, a typical MT8163
Finding the precise scatter file for your tablet or board can be frustrating. Here are the reliable methods:
Unlike Qualcomm processors that use MBN or rawprogram0.xml files, MediaTek relies exclusively on the scatter format. The MT8163 has several unique characteristics that make its scatter file distinct: Without this file, tools like SP Flash Tool
Using a scatter file from a different device (e.g., an MT8167) or a different firmware version can result in a hard brick—a state where the preloader is corrupted, and the device won't even power on.
1. Scatter File Version Mismatch: Attempting to flash a scatter file from one device variant (e.g., a 16GB storage model) onto a different variant (e.g., an 8GB model) will cause errors. The SP Flash Tool will typically throw an error: "Partition offset exceeds storage capacity."
2. BROM Error (4032):
This is often caused by the scatter file attempting to write to a "Protect" partition (like protect1 or protect2) which has been locked by the manufacturer. In the scatter file, setting is_download: false for these partitions resolves the issue.
3. Missing scatter.txt:
Users often download firmware in "Backup" format (individual folders). Without the text scatter file, the flashing tool cannot interpret the raw binaries. Tools exist to generate a scatter file manually, but they require precise knowledge of block sizes and offsets.