Easy Magic TWRP Installer for all MediaTek Devices ONLY (Developers ONLY)

Status
Not open for further replies.
Search This thread
By:
Advanced…
M

miskiab

Senior Member
May 9, 2012
58
5
I need this informations roms!

Screen : 540x960
BB Chip : MT6577
Ms Board : Glaxy S3
IMEI1 : XXXXXX
IMEI2: XXXXXX
Modem Ver. : MAUI.11AMD.W11.50.SP.V12. 2012/09/20 18:56
Bar code : 030801050804260123456788.81_20390210
Build Time : 2012 10 17 15:02:47 CST
UBoot Ver. : 2010.06
Kernel Ver. : 4.1.1
SW Ver. : ALPS.ICS.MP.V2.6
Custom Build Verno. : 005121017

hi, a have same phone and is it possible update new rom? Why? Because thşs rom very stable but one except, google contacts cant sync.
And i m trying cwm install with MTKdroid tools its runing but ONLY ONE TAKE. After the reboot in CWM menu coming orginal factory recovery(yellow simple screen and only have test etc. menus) why? ((
Again im trying install twrp with mobileuncles, installing normal, no error but open the recovery mode no twrp. again im trying easytwrp, ctr 2.4 etc. tools but they are cant see my phone as MTK device. How do i can? thanks
 
A

aimnl.hkim

New member
May 12, 2016
3
1
I used the manual install and after following all the procedure accordingly and it says :

Aborting, ported recovery is too large & causes region overlap
Click to expand...
Click to collapse

In the log.txt it says:

20170226143619 Manual-mode
--------------
20170226143716 ro.secure : 1
--------------
20170226143717 MTK partition info :
/system/bin/sh: cat: /proc/dumchar_info: No such file or directory
dev: size erasesize name
--------------
20170226143717 MTK CPU Info : Processor : ARMv7 Processor rev 2 (v7l)
processor : 0
BogoMIPS : 28.60
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 2

Hardware : MT6752
Revision : 0000
Serial : 0000000000000000
--------------
20170226143717 build.prop Info :
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KTU84P
ro.build.display.id=P1_MY_9B18D_P632A10V1.0.3
ro.build.version.incremental=eng.dongxiaoyong.20160428.091636
ro.custom.build.version=B02
ro.build.inner.version=B02
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.4
ro.build.version.security_patch=2015-12-01
ro.build.version.base_os=
ro.build.date=Thu Apr 28 09:18:59 CST 2016
ro.build.date.utc=1461806339
ro.build.type=user
ro.build.user=dongxiaoyong
ro.build.host=dongxiaoyong-desktop
ro.build.tags=release-keys
ro.product.model=ZTE Blade Q Lux
ro.product.brand=ZTE
ro.product.name=P632A10
ro.product.device=P632A10
ro.product.board=aeon6752_lwt_nj_cu
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=ZTE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=aeon6752_lwt_nj_cu
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=aeon6752_lwt_nj_cu-user 4.4.4 KTU84P eng.dongxiaoyong.20160428.091636 release-keys
ro.build.fingerprint=ZTE/P632A10/P632A10:4.4.4/KTU84P/20160428.091636:user/release-keys
ro.build.flavor=
ro.build.characteristics=default
# end build properties

# begin mediatek build properties
ro.mediatek.version.release=P1_MY_9B18D_P632A10V1.0.3
ro.mediatek.platform=MT6752
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK2.MP13
ro.mediatek.version.sdk=3
# end mediatek build properties
#
# from out/target/product/aeon6752_lwt_nj_cu/obj/CUSTGEN/config/system.prop
#
#
# system.prop for generic sdk
#

rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0


# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }

# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}

# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}


#
wifi.tethering.interface=ap0
#

ro.opengles.version=196608

wifi.direct.interface=p2p0
# dalvik.vm.heapgrowthlimit=256m
# dalvik.vm.heapsize=512m

# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0

# Power off opt in IPO
sys.ipo.pwrdncap=2

# Switching Menu of Mass storage and MTP
ro.sys.usb.storage.type=mtp,mass_storage

# USB BICR function
ro.sys.usb.bicr=yes

# USB Charge only function
ro.sys.usb.charging.only=yes

persist.uartconsole.enable=1

# audio
ro.camera.sound.forced=0
ro.audio.silent=0

ro.zygote.preload.enable=0
persist.sys.timezone=Asia/Kuala_Lumpur

#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=0
ro.gemini.sim_switch_policy=1
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=0
ril.current.share_modem=2
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
persist.radio.fd.on.only.r8.network=0
drm.service.enabled=true
drm.forwardlock.only=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=CONSYS_MT6752
mediatek.wlan.module.postfix=_consys_mt6752
ril.radiooff.poweroffMD=0
ro.config.notification_sound=Glow.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=The_party.ogg
persist.mtk.wcn.combo.chipid=-1
ro.fota.oem=MTK_KK
ro.fota.platform=MTK_KK
ro.fota.type=phone
ter.service.enable=0
mediatek.extmd.usbport=0
ro.lte.dc.support=0
ril.active.md=0
ro.setupwizard.mode=ENABLED
ro.com.google.gmsversion=4.4_r7
ro.com.google.clientidbase=android-zte
ro.com.google.clientidbase.ms=android-zte
ro.com.google.clientidbase.am=android-zte
ro.com.google.clientidbase.gmm=android-zte
ro.com.google.clientidbase.yt=android-zte
wfd.dummy.enable=1
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
qemu.hw.mainkeys=0
--------------
20170226143728 MTK screen res : 480x854
--------------
20170226143742 Manual data/media
--------------
20170226143745 KitKat ROM
--------------
20170226143748 recovery.fstab :
# mount point fstype device [device2]

/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/uboot emmc /dev/uboot flags=display="uboot";backup=1
/nvram emmc /dev/nvram flags=display="nvram";backup=1
/cache ext4 /[email protected]
/data ext4 /[email protected]
/system ext4 /[email protected]
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
--------------
20170226143810 Ported recovery size : 9355264/ Stock recovery size :
--------------
Click to expand...
Click to collapse

Help?
 
  • Like
Reactions: Ranjanlal Nishad
LiquidXed

LiquidXed

Senior Member
Jul 10, 2010
423
41
any way to use this tool with WIFI USB instead of through USB? i cant enable USB debugging with this device, only can adb through WIFI.
MT8127 head unit
1024*600
 
S

Sharashchandra

Senior Member
Mar 8, 2016
116
18
LiquidXed said:
any way to use this tool with WIFI USB instead of through USB? i cant enable USB debugging with this device, only can adb through WIFI.
MT8127 head unit
1024*600
Click to expand...
Click to collapse

I dont know which device you are using ,
If its OS is above 4.3 then you have to manually
Enable the usb debugging in your device in the developer option
If you dont have developer option in your device
Then goto aboutdevice and tap on buildno seventimes
It will enable developer option in your device
Install adb driver in your PC
Iam using 15sec adb imstaller v1.4.3
All the best
Get usb debugging on your device
 
LiquidXed

LiquidXed

Senior Member
Jul 10, 2010
423
41
Sharashchandra said:
I dont know which device you are using ,
If its OS is above 4.3 then you have to manually
Enable the usb debugging in your device in the developer option
If you dont have developer option in your device
Then goto aboutdevice and tap on buildno seventimes
It will enable developer option in your device
Install adb driver in your PC
Iam using 15sec adb imstaller v1.4.3
All the best
Get usb debugging on your device
Click to expand...
Click to collapse
Yes i know how to enable usb debugging. Its a Chinese head unit, and usb debugging doesn't work. I managed to root it and enable wifi adb
 
LiquidXed

LiquidXed

Senior Member
Jul 10, 2010
423
41
One more question.. If i flash this recovery that i tryed to port. If its not right, will it cause the os not to boot?
My bootloader is locked and have no way to unlock, dnt want to brick it.
 
XN Logos

XN Logos

Senior Member
Sep 27, 2016
316
309
indore
ya i know this is not compatible For MT67XX but i mean can Someone update it For MT67XXX, Devices, bcz there is non update Available for MTK tools So many user face a A Custom Recovery Issue on Low budget Devices, and up to more than 80% Devices Come with Mtk chipset,
 
K

KHARKOVSKIY30

New member
Aug 16, 2014
2
0
KHARKOV
Hello.
Help with TWRP recovery on Т311 clone Samsung galaxy Tab 9" mt6577 width 600; height 1024
here in detail the data sources of talc in Russian:

---------- Post added at 12:05 PM ---------- Previous post was at 12:02 PM ----------

Links are not inserted, in personal correspondence probably will be able to show link((
 
SubwayChamp

SubwayChamp

Senior Member
Aug 6, 2016
3,826
4
1,563
dise.666 said:
will it work on HTC 526G DS powered MTK6582
Click to expand...
Click to collapse

It worked with a Blu Dash 5.5 with same mtk6582, just take a backup of your recovery with rashr. I think that this app can´t cause a brick, I tried with newer processors, no results but just this app closes access to recovery partition temporarily untill flashing backup again.
 
Status
Not open for further replies.

Similar threads

bucefal82
Cyanogenmod for mediatek devices
Replies
7K
Views
2M
K
kalwardin
lokeshsaini94
  • Sticky
[GUIDE] [how to] CREATE OWN ROM [FOR ANY ANDROID DEVICE] [FOR N00B] [EASIEST METHODS]
Replies
1K
Views
1M
J
Justnaggy
S
Intel Android Devices Root / Temp Recovery Session
Replies
1K
Views
926K
T
triangles
D
Amazing Temp Root for MediaTek ARMv8 [2020-08-24]
Replies
2K
Views
671K
carlosyoan99
carlosyoan99
yuweng
[PORT] [TOOL] Carliv Touch Recovery for MediaTek devices
Replies
919
Views
509K
B
bovirus

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 183
    yuweng
    yuweng
    Credits
    TWRP Lead Developer Dees_Troy for continuously developing, improving & maintaining TWRP, TeamWin team & numerous developers that has contributed to TWRP & many doesn't know its Igor Sorocean initially submitted MrJavum codes so that TWRP officially supports MediaTek devices & most importantly MrJavum for discovering TWRP works on MediaTek devices & written codes to support proper backup formatting for MTK device . . .
    bo_zps0904409a.gif


    This tool uses EnJens for repack based on the original Unpack/ Repack concept by Russian Master Shifu Michfood . . .
    salute_zps09342dc6.gif


    Not forgetting my Master Shifu Carliv who has taught me how to compile & continuously guiding me to the right direction, dhinesh77 for sharing his super simple technique to patch ubifs for TWRP, awaaas for sharing his tips & findings for building TWRP from source for MTK devices ( Updates ), cyberangel22k for beta-testing custpack backup/restore on MTK Alcatel, yazidkucrit for discovering that TWRP also works on MT6573 & all MTK Developers that has contributed to the MTK platform . . . :highfive:
    Screenshot
    1_zps692eac36.png
    2_zpsccf36d6c.png
    3_zps5e2df19f.png
    4_zps1db3a616.png
    Video Preview

    Installation How-to

    Double-click TWRP Setup.exe & read the on-screen instructions

    Where is the Downloads . . .
    Down_zps5d0e5d6c.jpg

    Known problems on MTK devices

    • Mostly older intermediate MediaTek devices such as MT6589, MT6572 that comes with only 6Mb recovery partition, most probably won't work. However, it works on my legacy MT6573, MT6577 because its kernel is much smaller. There has been feedback from fellow xda members that some latter MediaTek devices comes with 7Mb & 8Mb. Latest MT6592 has a recovery partition of more than 8Mb.

    • In the past, there has been reports that Touch doesn't work at recovery on some MTK devices, try using different releases of kernels from your device. Recovery is independent so GB, ICS or JB kernel will work provided they are from your device. If you don't have different kernels from your device manufacturer either live without Touch or try porting other recovery, it might work.

    • This TWRP was compiled from source without adding any sauce or spice & it works for most MTK devices. However, if the mount USB doesn't work then refer to a.marduk solution . . . :good:

    • # Even though the MTK SoC is designed by MediaTek but the one that produces it is hundreds if not thousands of factories so some might use other combinations to boot up the recovery. It is a known problem that some MTK doesn't wanna boot up recovery the normal way so try Popey900 technique. Standard procedure : Take out the battery, wait a while, put it back, hold Volume Up or Down, don't let go then press the Power button until it boots up #
    WARNING

    DO NOT USE IT ON LOCKED BOOTLOADER MTK DEVICES SUCH AS ASUS, HTC, LG, SONY, MOTOROLA & OTHERS <- Click Here. IT WILL BRICK IT, refer to here for more info . . .

    Even though wrong installation of custom recovery normally will bricks the recovery only however it is better to be safe than sorry.

    TWRP is packed with many features so typically it will work on MTK devices with above 6Mb recovery partition however you can try your luck.

    Tested working perfectly on my legacy MTK device, MT6573 & MT6577.
    • Make a Factory ROM backup first with MTK Droid Tools. My old guide here.
    • Install Flashify & make another backup of your current recovery first & also the boot.img too
    • Extract downloaded files to your Desktop, disable UAC & restart PC, double-click TWRP.exe & follow the on-screen for instructions.
    YOUR TOOL DOESN'T WORK . . .

    i've seen this at many threads & also mentioned this many times at my other threads, most frequent reply is it doesn't work, you have given nothing at all to figure out what went wrong . . .
    alamak_zps2e31ed77.gif


    Please list out as many info as possible then it'll be easier to trouble-shoot & read EVERYTHING before hands-on . . .
    1. What OS you are using on the PC & your MTK...
    2. Did you disable UAC & Anti-Virus
    3. Did you execute the porting tool at C: drive if you're using XP else then at your Desktop
    4. Did you try Run as Administrator
    5. Could it be some other software that you installed that interfere with the porting tool then uninstall it
    6. Did you try it on other PC with other version OS or even different USB port
    7. Try uninstall all previous adb driver -> Device Manager -> View -> Show hidden devices -> uninstall all ADB Interface/ Android device -> reboot -> re-install
      adb.jpg
    8. Did you try latest google ADB driver while for XP try this one
    9. Attach both log.txt from porting tool & recovery.log from TWRP, attach also stock recovery.img/ boot.img & ported TWRP recovery.img too so that i can compare it to see where it went wrong

    Please bear in mind that this tool has been PROVEN to work & many has ported it to their MTK device so try to do you own trouble-shooting first & when you found the solution then you are most welcome to post it here . . . :good:

    And if you do found a bug on this porting tool, please do report it here too so that i can fix it . . . :eek:
    And pls do not quote the whole OP when replying . . .

    Updates 03 July 2014
    Great news, TWRP ubifs patch has been officially submitted to omni for review . . .

    Attention all MTK ubifs users,

    Guys, please hit the thanks button for dhinesh77 to show your gratitude & appreciation, he has taken all the trouble to get ubifs officially supported on TWRP even though he uses a Samsung nowadays . . .

    Thanks bro for doing all this & going thru the hassle for the whole MTK ubifs community, you're the best . . . :highfive:
    i've released AIO Compile TWRP script for MediaTek devices on BBQLinux so that you can build it on your own since i don't use MTK nowadays... :cool:

    Changelog

    XDA:DevDB Information
    Easy Magic TWRP Installer for MediaTek Devices ONLY (Developers ONLY), Tool/Utility for all devices (see above for details)

    Contributors
    yuweng
    Source Code: https://github.com/omnirom/android_bootable_recovery


    Version Information
    Status: Stable
    Current Stable Version: 2.8.2.0
    Stable Release Date: 2014-12-07

    Created 2014-06-28
    Last Updated 2016-03-27
    View
    50
    yuweng
    yuweng
    Features

    Auto mode
    - You don't need to know a thing & it'll port a working TWRP for your MTK & that is why it is called Magic . . .
    brows_zpsda58f2fa.gif


    Manual mode
    - Let you choose either to use your boot.img or recovery.img for porting.
    - Let you manually choose your device res, data/media device, flipped screen & uses all files from your stock recovery. Refer to here for more info . . .
    - device resolutions
    - data/media
    - flipped screen

    UnPack/ RePack mode
    - Let you mod whatever you want with option to install it right away to your MTK

    Requirement
    - Requires Root
    - Install adb driver
    - Enable USB debugging
    - Disable UAC
    - Disable driver signature
    - Compatibility with KitKat
    - No need ro.secure=0 to run
    recovery.fstab How-to

    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

    TW_INTERNAL_STORAGE_PATH := "/data/media"
    TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
    TW_EXTERNAL_STORAGE_PATH := "/sdcard"
    TW_EXTERNAL_STORAGE_MOUNT_POINT := "sdcard"

    TW_INTERNAL_STORAGE_PATH := "/emmc"
    TW_INTERNAL_STORAGE_MOUNT_POINT := "emmc"
    TW_EXTERNAL_STORAGE_PATH := "/sdcard"
    TW_EXTERNAL_STORAGE_MOUNT_POINT := "sdcard"

    SP1_NAME := "uboot"
    SP1_DISPLAY_NAME := "uboot"
    SP1_BACKUP_METHOD := image
    SP1_MOUNTABLE := 0
    SP2_NAME := "nvram"
    SP2_DISPLAY_NAME := "nvram"
    SP2_BACKUP_METHOD := image
    SP2_MOUNTABLE := 0
    SP3_NAME := "custpack"
    SP3_DISPLAY_NAME := "custpack"
    SP3_BACKUP_METHOD := image
    SP3_MOUNTABLE := 0
    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 mmcblk0p6 for system & some uses mmcblk0p3 while [email protected] 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"][email protected][/COLOR]
/data           ext4      /[COLOR="blue"][email protected][/COLOR]
/system         ext4      /[COLOR="blue"][email protected][/COLOR]
/emmc           vfat      /[COLOR="blue"][email protected][/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 [email protected] 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            /[email protected]
/data           ext4            /[email protected]
/misc           emmc            /dev/misc
/recovery       emmc            /dev/recovery
/system         ext4            /[email protected]
[COLOR="blue"]/preload[/COLOR]        ext4            /[COLOR="blue"][email protected][/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		/[email protected]
/data		ext4		/[email protected]
/misc		emmc		/dev/misc
/recovery	emmc		/dev/recovery
/emmc		vfat		/[email protected]		flags=display="Internal SD-card";storage;wipeingui;backup=1
/system		ext4		/[email protected]
/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    /[email protected]             flags=display="cache"
/data        ext4    /[email protected]           flags=display="data"
[COLOR="Blue"]/cust[/COLOR]        ext4    /[COLOR="blue"][email protected][/COLOR]              flags=display="[COLOR="blue"]cust[/COLOR]";backup=1
/system      ext4    /[email protected]           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	/[email protected]
/data		ext4	/[email protected]
/system		ext4	/[email protected]
/emmc		vfat	/[email protected]
[COLOR="Blue"]/custpack[/COLOR]	ext4	/[email protected]		flags=display=[COLOR="blue"]custpack[/COLOR];backup=1
[COLOR="blue"]/mobile_info[/COLOR]	ext4	/[email protected]_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:
    Ported recovery.img is too large & causes region overlap !

    This tool is AIO so use the UnPack/ RePack feature to remove below known files that are safe to be deleted to save a few Kb. ( rmdisk/sbin folder ) Below list starts with less critical to critical
    1. Use awaaas technique to use basic theme
    2. Parted
    3. All *exfat*
    4. erase_image, dump_image
    5. flash_image <- You will not be able to flash modded EBR, MBR
    6. rmdisk/supersu folder <- You will not be able to Root via TWRP
    7. adbd <- No adb shell & mount USB storage but you still can use MTP
    In fact in the past i have tested, there are quite a few more binary that you can safely remove from rmdisk/sbin folder. Of course you'll loose a few features but at least you can still use TWRP for basic backup & restore.

    Delete one file at a time at rmdisk/sbin folder, repack it, until it let you auto-install it.

    Updates
    Found out that you can also zip the whole content of res folder, move it to /sdcard/TWRP/theme/ui.zip, delete whole res folder & that will work too but no splash screen . . . :cowboy:

    if you want then remain res/images/curtain.jpg then splash screen will work . . .
    TWRP Materialised Theme

    Huge Credits to z31s1g, TWRP has never look so elegant & sophisticated ever before . . . :good:

    As mentioned many times, this tool is AIO so unpack the ported recovery.img, download the various custom splash screen that you like, resize it to your device res, copy & paste it to res/images/curtain.jpg, Credits to PünchUp . . . :good:

    i have ported to 480x854 res Dark Theme & Light Theme, credits to thewisenerd & Modding.MyMind & don't forget to hit the Thanks button for them . . . :good:

    Dark & Light Theme porting to MTK
    If you're using other themes other than 480x854 which is ported by me then Dark & Light Theme will not work properly on MTK . . . :cowboy:

    Solution to Change Color on Dark & Light Themes to work on MTK
    1. Open ui.zip -> ui.xml & change all /sdcard/TWRP to /emmc/TWRP EXCEPTIONAL for two -> tw_filename=/sdcard/TWRP/aromafm/aromafm.zip & save it first.

      Tips : Use the search function -> Ctrl + f to search for above keyword & if you're a Windows users then use Notepad++ for editing . . .

    2. There are two occurrence -> ./zip -0 -r -u "/emmc/TWRP/theme/ui.zip" *; <- You'll need to delete both the -u.
      Code: 
      mkdir "/cache/twrp";
if [ -f "/emmc/TWRP/theme/ui.zip" ];
then unzip -o "/emmc/TWRP/theme/ui.zip" -d "/cache/twrp";
chmod 777 "/cache/twrp/zip";
cp -r /cache/twrp/%tw_folder%/* "/cache/twrp/images";
busybox mv "/cache/twrp/ui.xml" "/cache/twrp/ui_temp.xml";
busybox sed "s/%text_highlight%/#%tw_text_color_highlight%/g" "/cache/twrp/ui_temp.xml" > "/cache/twrp/ui_temp2.xml";
rm -f "/cache/twrp/ui_temp.xml";
busybox sed "s/%text_actionbar%/#%tw_text_actionbar%/g" "/cache/twrp/ui_temp2.xml" > "/cache/twrp/ui.xml";
rm -f "/cache/twrp/ui_temp2.xml";
cd "/cache/twrp";
[COLOR="blue"]./zip -0 -r "/emmc/TWRP/theme/ui.zip" *;[/COLOR]
cd /;
rm -r "/cache/twrp"
else
    Updates
    /data/media device refer to here . . . :good:
    Solution to Install Image on Dark & Light Themes to work on MTK

    WARNING : Does not check whether the boot.img or recovery.img you're about to flash is oversize & that might brick your MTK if you have only 6Mb partition, you have been fore-warned . . .

    When you select Install -> Top Menu Install Zip -> Install Zip or Install Image
    • Open ui.zip -> flashify -> META-INF -> com -> google -> android -> update-binary & edit as below . . .

      Replace Line 41 to 53 with below & save it first.
      Code: 
      # Modded to work on MediaTek devices only
case $image in
  boot*)
    imgtype="boot.img";;
  *recovery*)
    imgtype="recovery.img";;
  *)
    ui_print "No image file found to flash.";
    abort;;
esac;
      Now at Line 66 to 74 replace with below, save it & now flashing MTK boot.img or recovery.img will work on Dark & Light Theme.
      Code: 
      # Modded to work on MediaTek devices only
  if [ "$imgtype" == "boot.img" ]; then
    block=/dev/bootimg;
  elif [ "$imgtype" == "recovery.img" ]; then
    block=/dev/recovery;
  fi;
    Aroma File Manager
    It is a known problem that aromafm will not to work properly on flip-screen, this is not a TWRP problem as it has never been updated for almost a year.

    Flip Touch on Flip Screen

    It is a known problem that MTK manufacturer uses non-standard design & uses different Flip Screen/ Non-Flip LCD with different combinations of Flip/ Non-Flip Touch Screen on various Portrait & especially Landscape Android devices.

    There is absolutely no way that the porting tool could detect whether your MTK's Touch is FlipX or FlipY or SwapXY so i build all possible combinations here -> View attachment 3039567, read the How-to use it. Built-in to porting tool -> Manual-mode
    Bug report <- No support if you don't attach it to your post, pls refer to post #1 YOUR TOOL DOESN'T WORK . . .

    Refer to here on how to submit a proper bug report . . . :good:

    Please always attach recovery.log & log.txt from the porting tool or i'll be giving the wrong advice based on assumption & that might brick your device !

    How to obtain recovery log
    1. adb pull /tmp/recovery.log -> Attach to your post
    2. At TWRP -> BackUp -> After Backup go to Advanced -> Copy Log to SDCard

      Typically you will find the recovery.log at

      Typical Internal SdCard
      /emmc/TWRP/BACKUPS/ [Your Device Name] / [Backup date] [ro.mediatek.version.release]

      or

      Typical External SdCard
      /sdcard/TWRP/BACKUPS/ [Your Device Name] / [Backup date] [ro.mediatek.version.release]

      Attach it to your post.
    3. At TWRP console (Square button at button) -> You can view the log
    if you don't see me replying means either the answer is already at this thread so start reading every page, its not like there are 100 over pages, as of 10 Jan 2014, there are only 24 pages . . .

    The 2nd reason you don't see me replying is i donno the answer then head up to the TWRP IRC channel to get help, refer to here for more info . . . :cowboy:
    TWRP FAQ
    View
    11
    yuweng
    yuweng
    Haha, you are most welcome, my friend . . . :highfive:

    Any feedbacks on ubifs & if everything is working well then i'll contact Master Shifu Dees_Troy to submit dhinesh77 patch to have ubifs officially supported by TWRP . . .
    brows_zpsda58f2fa.gif
    View
    10
    yuweng
    yuweng
    Be warned, there hasn't been active feedbacks on ubifs here, refer to here for more info . . . Previously, dhinesh77 has shared with me that he had a hard time unbricking his ubifs in spite of having SP Flash Tool Factory ROM from vendor. Having said that, daoodshah has reported 2.7.1.0 working perfectly so you may wanna try that first . . .

    As for the recovery.fstab, try the below . . .
    Code: 
    # mount point	fstype		device			[device2]

/boot          mtd    boot
/recovery      mtd    recovery
/uboot         mtd    uboot                 flags=display="uboot";backup=1
/nvram         mtd    nvram                 flags=display="nvram";backup=1
/cache         ubifs  cache
/data          ubifs  userdata
/system        ubifs  system
/sdcard        [COLOR="blue"]auto[/COLOR]   fat                   flags=display="[COLOR="blue"]Internal Storage[/COLOR]";settingsstorage
/external_sd   [COLOR="Blue"]auto[/COLOR]   /dev/block/mmcblk0p1  flags=display="[COLOR="Blue"]External Storage[/COLOR]";storage;removable
/sd-ext        auto   /dev/block/mmcblk0p2
    If it doesn't work then change the above auto to vfat
    Code: 
        mkdir /boot
    mkdir /recovery
    mkdir /system
    mkdir /data
    mkdir /cache
    [COLOR="Blue"]mkdir /external_sd[/COLOR] [COLOR="red"]<- Add this to your existing [COLOR="blue"]init.rc[/COLOR][/COLOR]
    mount tmpfs tmpfs /tmp
    Attn to All
    Guys, from now on please attach recovery.log & log.txt from the porting tool or i'll be giving the wrong advice. Eg. Previous post, advice given assuming is ext4 filesystem but actual is ubifs which is completely different & that might brick your device . . . Refer to post #2 (Bug report) on how to obtain recovery.log . . .
    View
    9
    G
    Gauraav
    @yuweng Simply Awesome.... :)
    View

New posts