Skip to Content

Mt3367 Android Scatter.txt File

Introduction to MT3367 and Scatter.txt

The MT3367 is a processor chip developed by MediaTek, a company known for producing chipsets for various electronic devices, including smartphones and tablets. MediaTek chipsets are widely used in Android devices due to their cost-effectiveness and performance.

A "scatter.txt" file is a crucial component when dealing with MediaTek devices. This text file contains information about the layout of the firmware, specifying where different components of the firmware should be written on the device's flash memory. Essentially, it's a map that guides the flashing tool on how to properly distribute and write the firmware components onto the device.

Story: The Challenges of Finding the Right Scatter.txt for MT3367

John had been an Android enthusiast for years. He loved experimenting with different ROMs and firmware on his devices. Recently, he acquired an older smartphone based on the MediaTek MT3367 chipset. His goal was to breathe new life into this device by installing a custom ROM.

However, John quickly encountered a significant hurdle. The device wasn't recognized properly by the SP Flash Tool, and he couldn't find a compatible "scatter.txt" file for his specific device model. Without this file, he couldn't proceed with flashing any firmware.

Determined, John started his search online, scouring through forums and websites dedicated to Android development and MediaTek devices. He encountered several threads discussing the challenges of finding the correct scatter files for various devices but found nothing specific to his model. mt3367 android scatter.txt

Conclusion

The MT3367 Android Scatter.txt is a deceptively simple text file that holds the keys to the device's operating system. It is the bridge between the software binaries on a PC and the physical memory chips inside the hardware. Whether for repairing a car's infotainment system or developing custom firmware for industrial tablets, respecting and understanding the scatter file is the first rule of engagement.

6. Important Warnings for MT3367

Mastering the MT3367 Android Scatter.txt: The Blueprint for Firmware Flashing

Key Partition Definitions for MT3367

  1. PRELOADER – The primary bootloader. Corrupt this, and the device is hard-bricked (requires JTAG or EMMC programmer). On MT3367, it is tiny (0x40000 bytes).
  2. PGPT – Primary GPT (GUID Partition Table). Modern MTK chips, including MT3367, use GPT instead of MBR for larger storage.
  3. NVRAM – Stores device-specific data: IMEI, WiFi MAC address, Bluetooth address. Never flash a generic NVRAM from another device; it will kill your radio functions.
  4. UBOOT – U-Boot bootloader; initializes RAM and display. On head units, this controls LCD timing and touch panel init.
  5. BOOT_IMG (or boot) – Contains the kernel and a small ramdisk. For MT3367, this often includes CAN bus drivers for car integration.
  6. ANDROID – The system partition (super partition in newer builds). This is where /system, /product, and /vendor live in a logical volume.
  7. USRDATA – User data partition (factory reset wipes this). Address 0xffffffff indicates it extends to the end of free space.

================================================ scatter_version:2.0 platform: MT3367 partition_index: SYS0 androidboot.hardware: mt3367 board_id: mt3367_board

partition_name: PRELOADER file_name: preloader.bin is_download: true type: PRIMARY_ROM linear_start_addr: 0x00000000 physical_start_addr: 0x00000000 partition_size: 0x00040000 region: EMMC_BOOT_1 storage_space: EMMC

partition_name: MBR file_name: MBR is_download: true type: PRIMARY_ROM linear_start_addr: 0x00040000 physical_start_addr: 0x00040000 partition_size: 0x00040000 region: EMMC_USER storage_space: EMMC

partition_name: EBR1 file_name: EBR1 is_download: true type: PRIMARY_ROM linear_start_addr: 0x00080000 physical_start_addr: 0x00080000 partition_size: 0x00040000 region: EMMC_USER storage_space: EMMC Introduction to MT3367 and Scatter

partition_name: UBOOT file_name: u-boot.bin is_download: true type: PRIMARY_ROM linear_start_addr: 0x00100000 physical_start_addr: 0x00100000 partition_size: 0x00080000 region: EMMC_USER storage_space: EMMC

partition_name: RECOVERY file_name: recovery.img is_download: true type: PRIMARY_ROM linear_start_addr: 0x00180000 physical_start_addr: 0x00180000 partition_size: 0x00400000 region: EMMC_USER storage_space: EMMC

partition_name: SEC_RO file_name: secro.img is_download: true type: PRIMARY_ROM linear_start_addr: 0x00580000 physical_start_addr: 0x00580000 partition_size: 0x00100000 region: EMMC_USER storage_space: EMMC

partition_name: LOGO file_name: logo.bin is_download: true type: PRIMARY_ROM linear_start_addr: 0x00680000 physical_start_addr: 0x00680000 partition_size: 0x00100000 region: EMMC_USER storage_space: EMMC Do NOT flash a scatter from a different screen resolution

partition_name: ANDROID file_name: system.img is_download: true type: PRIMARY_ROM linear_start_addr: 0x00780000 physical_start_addr: 0x00780000 partition_size: 0x0A000000 region: EMMC_USER storage_space: EMMC

partition_name: CACHE file_name: cache.img is_download: true type: PRIMARY_ROM linear_start_addr: 0x0AF80000 physical_start_addr: 0x0AF80000 partition_size: 0x02000000 region: EMMC_USER storage_space: EMMC

partition_name: USRDATA file_name: userdata.img is_download: true type: PRIMARY_ROM linear_start_addr: 0x0CF80000 physical_start_addr: 0x0CF80000 partition_size: 0x15000000 region: EMMC_USER storage_space: EMMC

partition_name: FAT file_name: fat.img is_download: true type: PRIMARY_ROM linear_start_addr: 0x21F80000 physical_start_addr: 0x21F80000 partition_size: 0x00500000 region: EMMC_USER storage_space: EMMC

partition_name: MD1DATA file_name: md1img.img is_download: false type: PRIMARY_ROM linear_start_addr: 0x22480000 physical_start_addr: 0x22480000 partition_size: 0x01000000 region: EMMC_USER storage_space: EMMC

What it is and why it matters

================================================ End of example scatter