The MT6761 scatter file typically organizes partitions into groups based on their function. Below is a typical layout analysis.
A correct, modern MT6761 scatter file should look like this (excerpt): mt6761 scatter file new
############################################################################################################
# General Setting
############################################################################################################
- general: MTK_PLATFORM_CFG
info:
platform: MT6761
partition_name: PRELOADER
file_name: preloader_mt6761.bin
is_download: true
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x400000
region: EMMC_BOOT_1
storage: HP
boundary_check: true
is_reserved: false
operation_type: BOOTLOADERS
reserve: 0x00
...
- partition_index: 4
partition_name: SECCFG
file_name: seccfg.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1400000
physical_start_addr: 0x1400000
partition_size: 0x800000
region: EMMC_USER
storage: HP
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
Key indicators of a "new" scatter file:
| Partition | Linear Start | Length | Flags |
|----------------|--------------|------------|---------------------|
| preloader | 0x0 | 0x40000 | protected |
| pgpt | 0x0 | 0x80000 | required, protect |
| proinfo | 0x80000 | 0x300000 | visible, nvram |
| nvram | 0x380000 | 0x500000 | visible, nvram |
| lk | 0x880000 | 0x200000 | required |
| boot | 0xA80000 | 0x2000000 | required |
| recovery | 0x2A80000 | 0x2000000 | required |
| para | 0x4A80000 | 0x100000 | required |
| logo | 0x4B80000 | 0x800000 | required |
| expdb | 0x5380000 | 0x1400000 | required |
| tee1 | 0x6780000 | 0x500000 | required, trustzone |
| tee2 | 0x6C80000 | 0x500000 | required, trustzone |
| metadata | 0x7180000 | 0x2000000 | visible |
| userdata | 0x9180000 | 0xFFFFFFFF (rest) | visible, userdata | The MT6761 scatter file typically organizes partitions into
Note: Actual addresses and sizes depend on total eMMC size (e.g., 16GB, 32GB). Adjust userdata length accordingly. Key indicators of a "new" scatter file:
This is the most critical section. If the Preloader is corrupted, the device enters a "Hard Brick" state (requiance on BROM exploits for revival).