Mt6761 Scatter File New < FRESH × REPORT >

File name: MT6761_Android_scatter_new.txt
Target device: [e.g., Device Model Name]
Flash type: eMMC / NAND (specify)
Page size: 0x200 (512 bytes)
Block size: 0x20000 (128 KiB)

Assuming you have your mt6761 scatter file new and stock ROM images, follow these steps:

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:


Below is a simplified example. Note: This example is for educational purposes. Always use the correct and updated scatter file specific to your device model. File name:   MT6761_Android_scatter_new
version: 1.1
meminfo
0x80000000,0x40000000
partitions
name = preloader;     offset = 0;         size = 0x60000;
    name = bootloader;    offset = 0x60000;   size = 0x20000;
    name = vboot;         offset = 0x80000;   size = 0x20000;
    name = trustzone;     offset = 0xa0000;   size = 0x40000;
    name = lk;            offset = 0xe0000;   size = 0x40000;
    name = boot;          offset = 0x120000;  size = 0x80000;
    name = recovery;     offset = 0x200000; size = 0x100000;
    name = system;        offset = 0x300000; size = 0x800000;
    name = cache;         offset = 0xb00000; size = 0x400000;
    name = userdata;      offset = 0xf00000; size = 0x4000000;
    name = metadata;      offset = 0x4f00000; size = 0x10000;

Using an outdated or incorrect scatter file can lead to:

A new scatter file often comes directly from the latest stock ROM. These files include updated parameters for Mediatek’s newer security protocols, such as: Key indicators of a "new" scatter file:


Pro Tip: Do not use a scatter file from a device running Android 8.1 (Oreo) on a device updated to Android 10 (Q). Always source the scatter file from the exact same firmware build number.