Alternatively, dump the GPT:
For the CHM-U01, the scatter file typically contains 20–30 regions, from the Anti-Rollback (ARB) partition to the userdata area. A typical line from the CHM-U01 scatter looks like this: Chm-u01 Firmware Scatter
On the CHM-U01, the proinfo partition (containing factory SN) sits between seccfg and nvram . If you shift offsets even by 1 byte, the eMMC’s GPT and the scatter will mismatch, leading to S_FTHND_FILE_IS_NOT_LOADED_YET or STATUS_EXT_RAM_EXCEPTION errors. You don’t always need the original firmware package. On a rooted CHM-U01: Alternatively, dump the GPT: For the CHM-U01, the
Let’s dissect the CHM-U01’s scatter file not as a simple partition table, but as a low-level hardware blueprint. In the world of MediaTek (MTK) chipsets—which power the CHM-U01 (MT6735P)—a scatter file describes how the eMMC (embedded MultiMediaCard) flash memory is partitioned in physical address space . Unlike high-level block devices ( /dev/block/mmcblk0pX ), the scatter file works at the pre-bootloader level. SP Flash Tool, the standard flashing utility for MTK devices, uses this file to write raw data to exact physical offsets. You don’t always need the original firmware package
adb shell su cat /proc/dumchar_info This MTK-specific proc node outputs the exact scatter layout used by the kernel. Compare it to your XML — if mismatched, the device has been repartitioned.