If I want to resize partitions or restore a backup later, how do I make sure that
/proc/dumchar_info reflects the changes?
As far as I can tell,
dumchar_info is not related to the MBR and EBRs, since it has more info.
Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. It only takes a minute to sign up.Sign up to join this community
I cant find a dumchar_info file on my device, but usually using
proc/partinfo gives you the physical start locations and lengths of each partition, not including the preloader partition. Hypothetically if you resized the DATA partition to an extra 1 Gig, you would need to adjust the entire partition scheme after the new ending length position, you could readjust the size of only the next partition if you leave enough space for it to actually be used.
You would need to update any changes to the scatter file, the new starting positions of each partition and the new sizes.
Backup and restore, you can just backup the entire emmc and restore it again using SP Flash Tool.
/proc/dumchar_info is provided by the
dumchar driver, which reads the partitioning info from a header file generated during the build process and compiled in when the kernel is built. This header file is also used by other components, like the preloader, possibly bootloader, and both regular and recovery kernels. This means unless you can rebuild said components with a new header file, the partitioning is quite literally hard-coded.
A scatter file is related, in that it's generated from the same source. You can use the information from
/proc/dumchar_info (together with some assumptions) to generate a scatter file.
For more information on partitioning on MediaTek devices that don't use GPT, see here.