| ... | ... | @@ -100,7 +100,7 @@ mmcblk0p33: 8e4ffc 000000 "emmc" |
|
|
|
<br /><br />
|
|
|
|
|
|
|
|
### MTK Based Devices
|
|
|
|
On devices based on MTK (MediaTek) chips, a file at `/proc/dumchar_info` is populated with the partition layout, by the linux kernel. This file, however is not similar to `/proc/mtd`, `/proc/emmc` and partition layout files used by Online Nandroid. Since MTK devices use the uboot mechanism, partitions including boor and recovery, are not revealed as separate partitions, but rather accessed sequencially by size and start parameters. The dumchar_info file has this size and start parameters specified in it. This file has some other major differences in partition naming such as the boot partition is named `bootimg` instead of `boot`, data partition is named `usrdata` instead of `userdata` system partition is named `android` instead of `system` and internal sd card is named `fat` instead `emmc`.
|
|
|
|
On devices based on MTK (MediaTek) chipsets, a file at `/proc/dumchar_info` is populated with the partition layout, by the linux kernel. This file, however is not similar to `/proc/mtd`, `/proc/emmc` and partition layout files used by Online Nandroid. Since MTK devices use the uboot mechanism, partitions including boot and recovery, are not revealed as separate partitions, but rather accessed sequencially by size and start parameters. The dumchar_info file has this size and start parameters specified in it. This file has some other major differences in partition naming such as the boot partition is named `bootimg` instead of `boot`, data partition is named `usrdata` instead of `userdata` system partition is named `android` instead of `system` and internal sd card is named `fat` instead `emmc`.
|
|
|
|
Online Nandroid (since v8.0) has built-in support for MTK based devices, thus does not require separate partition layout files on MTK based devices.
|
|
|
|
|
|
|
|
Example (`/proc/dumchar_info` on a Star N9770 Dual Core - MT6577):
|
| ... | ... | |
