Updates
This porting tool is build on
jellybean repo so that it can support
three generation of
MTK SoC with non-device specific build flags to maintain compatibility. Below specific build flags are not use & it seem that the
2.8.1.0 porting tool doesn't work across
MTK device. However, fyi, it works fine on mine
So pls refer to
here <-
*RECOVERY.FSTAB* to use the different flags to properly support your
MTK device.
With non-device specific build flags, compatibility can be maintained across
MTK SoC, you only need to mod the
recovery.fstab. Having said that, i need users feedback so that i can incorporate those changes or this porting tool will remain as it is on every new release.
It seems that you need to label Sdcard as
Internal Storage or
External Storage to properly support proper BackUp/ Restore function. Refer to
here for more info . . .
TTF font is also disable to maintain compatibility across
MTK SoC.
-------------------------------------------
Preface
As mentioned few times, i don't own all the
MTK devices available on the market so a few things might not work on your
MTK. So use the
UnPack/ RePack mode to edit necessary files typically the
init.rc &
recovery.fstab.
UnPack other
MTK TWRP by other
DEVs & see how they did it.
google your device info & search
github & see how they did it, Eg.
here for
USB-OTG Thanks to
hehua2008 the only one that published/ i can find for
MTK TWRP.
As mentioned few times, the porting tool now is
AIO so go ahead & play with it.
Intro
What is
recovery.fstab
The actual require backup partition for
MTKs or any android devices are actually ONLY just the
boot,
cache,
data &
system partition.
When you encounter any problems such as doesn't boot/ bootloop issues after a new app installation or anything at all, a
Wipe Data/ Factory Reset or
Restore with ONLY the
system &
data partition & you'll be able to revert to previous working state in a short while. Thats why its very important to make a backup before modding anything at all !
For bootloop issues with new firmware installation (update.zip) then its best to restore everything. Having said that, if you flash
preloader using
SP Flash Tool then
TWRP restore would not be able to restore it, thats why it is important to backup your
Factory ROM with
MTK Droid Root & Tools first.
How to identify MTK partition
WARNING : Might corrupt or brick your
MTK when you specify the wrong partition at
recovery.fstab ! You have been fore-warned . . .
adb shell cat /proc/dumchar_info OR
adb shell cat /proc/mtd
Below are typical
MTK partition layout
Code:
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000004000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000008000 2 /dev/block/mmcblk0
[COLOR="Blue"]nvram[/COLOR] 0x0000000000500000 0x0000000000408000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000908000 2 /dev/block/mmcblk0
[COLOR="blue"]uboot[/COLOR] 0x0000000000060000 0x0000000000928000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000000988000 2 /dev/block/mmcblk0
recovery 0x0000000000800000 0x0000000000f88000 2 /dev/block/mmcblk0
sec_ro 0x0000000000400000 0x0000000001788000 2 /dev/block/mmcblk0p2
misc 0x0000000000060000 0x0000000001b88000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001be8000 2 /dev/block/mmcblk0
expdb 0x0000000000200000 0x0000000001ee8000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x00000000020e8000 2 /dev/block/mmcblk0p[COLOR="blue"]3[/COLOR]
cache 0x0000000020100000 0x00000000221e8000 2 /dev/block/mmcblk0p[COLOR="blue"]4[/COLOR]
usrdata 0x0000000020100000 0x00000000422e8000 2 /dev/block/mmcblk0p[COLOR="blue"]5[/COLOR]
fat 0x0000000085338000 0x00000000623e8000 2 /dev/block/mmcblk0p[COLOR="blue"]6[/COLOR]
bmtpool 0x0000000001500000 0x00000000ff9f00a8 2 /dev/block/mmcblk0
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate
Standard TWRP
recovery.fstab for
MTK devices
Code:
# mount point fstype device [device2]
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/system ext4 /dev/block/mmcblk0p[COLOR="Blue"]3[/COLOR]
/cache ext4 /dev/block/mmcblk0p[COLOR="blue"]4[/COLOR]
/data ext4 /dev/block/mmcblk0p[COLOR="blue"]5[/COLOR]
/emmc vfat /dev/block/mmcblk0p[COLOR="blue"]6[/COLOR]
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
/nvram emmc /dev/nvram flags=display="[COLOR="blue"]Nvram[/COLOR]";backup=1
/uboot emmc /dev/uboot flags=display="[COLOR="blue"]Uboot[/COLOR]";backup=1
Thanks to
MrJavum who discover that we can also backup
Nvram &
Uboot for
MTK devices . . . :good:
MTK Uboot also consist of camera driver & this feature is extremely useful when you upgrade your device firmware, typically it will replace the
Uboot & your camera doesn't work after that. A simple restore & you'll have your camera working again in no time.
MTK Nvram consist of your
IMEI & this feature is extremely useful when you have corrupted it, a simple restore & you'll have your phone in working state again.
Below format was discovered by
bgcngm & it has saved me a few lines of codes as
MTK manufacturer tends to use different partition no. from each other. Eg. Some might be using mmcblk0p
6 for system & some uses mmcblk0p
3 while
emmc@android will work on all
MTK devices.
Code:
# mount point fstype device [device2]
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery flags=display="recovery";backup=1
/uboot emmc /dev/uboot flags=display="uboot";backup=1
/nvram emmc /dev/nvram flags=display="nvram";backup=1
/cache ext4 /[COLOR="blue"]emmc@cache[/COLOR]
/data ext4 /[COLOR="blue"]emmc@usrdata[/COLOR]
/system ext4 /[COLOR="blue"]emmc@android[/COLOR]
/emmc vfat /[COLOR="blue"]emmc@fat[/COLOR]
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
Having said that, few has reported back that its not compatible for their
MTK then you'll need to unpack it & use the device block path
/dev/block/mmcblk0pX instead of this soft-link
emmc@android format. Use
Notepad++ for editing.
Updates : Porting tool now uses direct device block path.
Below examples are some of
MrJavum TWRP
recovery.fstab for
MTKs
Code:
# mount point fstype device [device2]
/boot emmc /dev/bootimg
/cache ext4 /emmc@cache
/data ext4 /emmc@usrdata
/misc emmc /dev/misc
/recovery emmc /dev/recovery
/system ext4 /emmc@android
[COLOR="blue"]/preload[/COLOR] ext4 /[COLOR="blue"]emmc@preload[/COLOR] flags=display="[COLOR="blue"]Preload[/COLOR]";backup=1;wipeingui
/external_sd vfat /dev/block/mmcblk1p1 flags=display="External SD-card";storage;wipeingui;removable
/nvram emmc /dev/nvram flags=display="Nvram";backup=1
/uboot emmc /dev/uboot flags=display="Uboot";backup=1
/logo emmc /dev/logo flags=display="Boot Logo";backup=1
#mt6582/recovery_emmc.fstab
To support
preload partition you'll need to specify it at
init.rc too.
Code:
[COLOR="Blue"]mkdir /preload[/COLOR]
mkdir /external_sd
mkdir /system
mkdir /data
mkdir /cache
mount /tmp /tmp tmpfs
Code:
/boot emmc /dev/bootimg
/cache ext4 /emmc@cache
/data ext4 /emmc@usrdata
/misc emmc /dev/misc
/recovery emmc /dev/recovery
/emmc vfat /emmc@fat flags=display="Internal SD-card";storage;wipeingui;backup=1
/system ext4 /emmc@android
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="External SD-card";storage;wipeingui;removable
/nvram emmc /dev/nvram flags=display="Nvram";backup=1
/uboot emmc /dev/uboot flags=display="Uboot";backup=1
/[COLOR="blue"]logo[/COLOR] emmc [COLOR="blue"]/dev/logo[/COLOR] flags=display="[COLOR="blue"]Boot Logo[/COLOR]";backup=1
Awaaas is so kind to shared with me his findings. He got help from
bigbiff on the
IRC & now
TWRP can also backup
EBR1 & SECRO. Refer to
updates here.
CodeLover has added
cust partition for his Huawei.
Code:
# mount point fstype device [device2]
/boot emmc /dev/bootimg flags=display="boot"
/misc emmc /dev/misc
/recovery emmc /dev/recovery flags=display="recovery";backup=1
/uboot emmc /dev/uboot flags=display="uboot";backup=1
/nvram emmc /dev/nvram flags=display="nvram";backup=1
/cache ext4 /emmc@cache flags=display="cache"
/data ext4 /emmc@usrdata flags=display="data"
[COLOR="Blue"]/cust[/COLOR] ext4 /[COLOR="blue"]emmc@cust[/COLOR] flags=display="[COLOR="blue"]cust[/COLOR]";backup=1
/system ext4 /emmc@android flags=display="system"
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
init.rc with
cust partition support.
Code:
mkdir /boot
mkdir /recovery
mkdir /system
mkdir /data
[COLOR="blue"]mkdir /cust[/COLOR]
mkdir /cache
mkdir /sdcard
mount tmpfs tmpfs /tmp
So its entirely up to you to specify what you want
TWRP to backup on your
MTK no need to compile a new one, just mod the
recovery.fstab
For further info refer to the main thread
here . . . :good:
For
MTK Alcatel devices, besides
/custpack there is also
/mobile_info partition, again its entirely up to you whether you would wanna backup it too, credits to
MrJavum for compiling the first
TWRP version for it . . .
Code:
# mount point fstype device [device2]
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/cache ext4 /emmc@cache
/data ext4 /emmc@usrdata
/system ext4 /emmc@android
/emmc vfat /emmc@fat
[COLOR="Blue"]/custpack[/COLOR] ext4 /emmc@custpack flags=display=[COLOR="blue"]custpack[/COLOR];backup=1
[COLOR="blue"]/mobile_info[/COLOR] ext4 /emmc@mobile_info flags=display=[COLOR="blue"]mobile_info[/COLOR];backup=1
/nvram emmc /dev/nvram flags=display=Nvram;backup=1
/uboot emmc /dev/uboot flags=display=Uboot;backup=1
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
Code:
mkdir /boot
mkdir /recovery
mkdir /system
mkdir /data
mkdir /cache
[COLOR="blue"] mkdir /custpack
mkdir /mobile_info[/COLOR]
mkdir /sdcard
mount tmpfs tmpfs /tmp
As mentioned many times, i don't own all
MTK devices out there so some features might not work. To fix it & to learn more about modding recovery refer to my Master Shifu thread
here &
here . . . :good:
