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 . . .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This tool uses EnJens for repack based on the original Unpack/ Repack concept by Russian Master Shifu Michfood . . .
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
Video Preview
Installation How-to
Double-click TWRP Setup.exe & read the on-screen instructions
Where is the Downloads . . .
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 . . .
Please list out as many info as possible then it'll be easier to trouble-shoot & read EVERYTHING before hands-on . . .
What OS you are using on the PC & your MTK...
Did you disable UAC & Anti-Virus
Did you execute the porting tool at C: drive if you're using XP else then at your Desktop
Did you try Run as Administrator
Could it be some other software that you installed that interfere with the porting tool then uninstall it
Did you try it on other PC with other version OS or even different USB port
Try uninstall all previous adb driver -> Device Manager -> View -> Show hidden devices -> uninstall all ADB Interface/ Android device -> reboot -> re-install
Did you try latest google ADB driver while for XP try this one
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 . . .
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...
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
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 . . .
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 /e[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
Use awaaas technique to use basic theme
Parted
All *exfat*
erase_image, dump_image
flash_image <- You will not be able to flash modded EBR, MBR
rmdisk/supersu folder <- You will not be able to Root via TWRP
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 . . .
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 . . .
Solution to Change Color on Dark & Light Themes to work on MTK
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 . . .
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
adb pull /tmp/recovery.log -> Attach to your post
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.
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 . . .
TWRP FAQ
Questions & Answers
Q : Your tool doesn't work.
A : Its already explained at the OP, pls read EVERYTHING at Page 1 !
Q : I can't get adb to work on my PC.
A : Then get one of your device forum DEV to look at this porting tool.
Q : I have a MTK model xxx SoC YYY, does your porting tool support it.
A : The title already said it, for all MediaTek Devices ONLY except latest big.LITTLE/ Cortex-A53 use PhilZ Touch
Q : I have a MTK but i'm afraid the porting tool would brick my device.
A : Then don't use it ! Its for Developers ONLY !
Q : OP said DO NOT USE IT ON LOCKED BOOTLOADER but the link doesn't say much for MTK devices.
A : There isn't any guide to identify locked bootloader on MTKs, generally you'll have to flash the recovery.img to find out whether it bricks ! However, farenheith has confirmed by flashing back the original stock 3e recovery.img & his locked bootloader MTK Motorola boots back !
As explained BRANDED at the OP, UNBRANDED MTKs are generally MTKs directly from China, have unlock bootloaders.
List of supported MTK devices . . .
@yuweng Simply Awesome....
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 . . .
Amazing work!
It's been a while since i googled about MTK Devices. I've already compiled TWRP for Oppo Find Muse, which has the MTK6572. It's really pleasure to see that you've made a good job! :laugh::good:
Keep up the good work!
I'm not able to update my TWRP recovery coz my device already given to my mom :crying:
But i'm still browsing about the MTK Devices :laugh:
It says that my recovery partition its to small(6291456) and that i can lose my IMEI. How can i make the partition recovery bigger?
As mentioned at the OP, it will most probably works on the latest MTK devices with above 6Mb, Eg : The latest MT6582, MT6592 or the obsolete MT6573, MT6575, MT6577 b'cos the kernel is so much smaller in size on these legacy devices . . .
i've published my findings on how to increase MTK recovery partition to 7Mb or 8Mb last year but many couldn't get it to work on their MT6589 . . .
Those that got it to work never shared it . . . Hunt for key work 7Mb_TWRP.pdf. WARNING : You might brick your device in doing so . . .
yuweng said:
As mentioned at the OP, it will most probably works on the latest MTK devices with above 6Mb, Eg : The latest MT6582, MT6592 or the obsolete MT6573, MT6575, MT6577 b'cos the kernel is so much smaller in size on these legacy devices . . .
i've published my findings on how to increase MTK recovery partition to 7Mb or 8Mb last year but many couldn't get it to work on their MT6589 . . .
Those that got it to work never shared it . . . Hunt for key work 7Mb_TWRP.pdf. WARNING : You might brick your device in doing so . . .
Click to expand...
Click to collapse
:good:
I prefer not to test it
Works with MT6572? :/
Great Work Bro!! :highfive:
Hello sir, I have a "mtk 6589t xolo q3000 with 4.4.2 kitkat os.
My stock recovery.imgs size is 6Mb and my stock boot.imgs size is also 6mb.
Is it possible to port twrp in my device ?
Will my mobile support your tool?
Sent from my Q3000 using XDA Premium 4 mobile app
Please upload it to some file sharing site rather than torrent..no seeds and leechers..
Sent from my Micromax A58 using xda app-developers app
daoodshah said:
....no seeds and leechers....
Click to expand...
Click to collapse
if you wanna download, do it the simple way. see the part "Where is the Downloads . . . " in the op.
"click to show content". can't get any simpler/better than that.
Dwnload is nt getting any speed..thats the problem..as there are no seeds..
Sent from my Micromax A58 using xda app-developers app
daoodshah said:
Dwnload is nt getting any speed....as there are no seeds..
Click to expand...
Click to collapse
no seeds required. click direct download. don't you see the pic and the circled icon? just do a 1-2-3.
Working perfectly for UBIFS..just tested right now..
Sent from my Micromax A58 using xda app-developers app
Wanna try this
which can delete files from folder "sbin"? Turned to run on 6589, but still works incorrectly.
Is there a way to increase size of recovery partition. I have 6mb partition, ported recovery is 6.4mb
Hi
I've cm-11-20150607-NIGHTLY-i9100 on my Samsung Galaxy SII i9100
It has gapps-kk-20140105-signed (as far as I remember).
I do have cwm 6.0.5.1
Two days ago, there was some update (haven't seen what exactly).
Now, while booting the phone hangs on the boot screen.
When I lunch into cwm-recovery I do see:
CWM-based Revocery v6.0.5.1
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open/cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open/cache/recovery/last_log
The show log says:
mount: mounting /dev/block/mmcblk0p7 on /cache failed: Invalid argument
W: failed to mount /dev/block/mmcblk0p7 (File exist)
E:Can't mount /cache/recovery/log
(and more like this)
...
I do have MTP enabled, and debugging USB disabled- this is a big problem since i can not access adb...
I would like to backup data, but how can I enable adb from cwm?
I did try to wipe dalvik (I think it did work) /format cache - It does not work - it hangs.
I did try to "reboot to receovery (or reboot to bootloader): from the cwm- it hangs
I did try to mount /storage/sdcard0 - it hangs
I did try to create a backup from phone memory to scracd1 - it hangs
I can boot into fastboot.
It looks like some error on partition, or problem with internal phone memory.
Anything that try to access internal sdcard0 hangs
How can I backup the phone (or at lest photo - not all were synced yet).
What would be the next step?
Any idea howto enable USB debugging?
I've seen this tutorial
(can add a link so google "enable usb debbuging through clockworkmod with adb")
but it is for the Nexus, not for the i9100...
I do have Ubuntu, with
adb version 1.0.31
I can switch to Windows if it would help...
Ok,
For the moment, I made the wrong assumption.
I can access adb.
The solution was to install latest android SDK (cm11 is some like Android 4.4.4) to get newest adb
(developer.android com/sdk/installing/index.html?pkg=studio )
To be clear, if you're having this same issue the problem is probably an out-of-date SDK. As of 4.2.2 there is a security feature that requires you to confirm the RSA fingerprint of the connecting device. Open the SDK manager and update the tools! Then reboot. - quote from stackoverflow com/questions/14993855/android-adb-device-offline-cant-issue-command
Click to expand...
Click to collapse
stackoverflow com/questions/14993855/android-adb-device-offline-cant-issue-commands
and
having Enabled ADB Integration via Tools > Android > Enable ADB Integration
stackoverflow com/questions/26079838/android-studio-adb-error-device-unauthorized-please-check-the-confirmat
Now I can access
adb shell (while booting into cwm recovery - Power+volUp+Home)
Code:
# parted /dev/block/mmcblk0 print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 159MB 105MB CACHE
8 159MB 176MB 16.8MB MODEM
9 176MB 713MB 537MB FACTORYFS
10 713MB 2861MB 2147MB DATAFS
11 2861MB 15.2GB 12.4GB UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
~ # cat /etc/fstab
/dev/block/mmcblk0p7 /cache ext4 rw
/dev/block/mmcblk0p10 /data ext4 rw
/dev/block/mmcblk0p9 /system ext4 rw
~ # mount -o ro -t ext4 /dev/block/mmcblk0p10 /data
mount: mounting /dev/block/mmcblk0p10 on /data failed: Invalid argument
The problem is - I can not backup the data nor mount the /data partition
Sir,
This forum is for helping new users to help members navigate the site, not for support.
I see you've found your device section and already know how things work on XDA.
So please note the sticky from the top of the Assist section and ask directly in this thread for I9100:
[Q&A][SGS2][Newbies][Experienced Users][RCs] New members friendly Q&A thread
Good luck
Could a genius with some time on there hands make TWRP for this device, its driving me insane, everything provided below.
Android 8.1
2GB RAM
Snapdragon 210
MSM8909
GPU Adreno 304
Times like these i wish i could follow a tutorial correctly.
Thanks in advance!
I had to archive the recovery as the IMG was over 8MB.
frankieuk said:
Could a genius with some time on there hands make TWRP for this device, its driving me insane, everything provided below.
Android 8.1
2GB RAM
Snapdragon 210
MSM8909
GPU Adreno 304
Times like these i wish i could follow a tutorial correctly.
Thanks in advance!
I had to archive the recovery as the IMG was over 8MB.
Click to expand...
Click to collapse
I know this reply is a little late... but have you tried twrp builder app? Search xda... got a working recovery for an obscure UMX budget phone... I have this tablet but I haven't bothered trying to do anything with it.
i have ported the Lenovo Tab 10 TB-X103F twrp to {TB-X104F}
tdawgg777 said:
I know this reply is a little late... but have you tried twrp builder app? Search xda... got a working recovery for an obscure UMX budget phone... I have this tablet but I haven't bothered trying to do anything with it.
Click to expand...
Click to collapse
i have ported the Lenovo Tab 10 TB-X103F twrp to {TB-X104F}but.... i having problems with partitions when i boot into it
i think my problems has to do with recovery.FSTAB file
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
heres my current recovery.fstab for twrp
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
#device mount point fstype [device2] [length=]
/boot emmc /dev/block/bootdevice/by-name/boot flags=display="Boot";backup=1
/recovery emmc /dev/block/bootdevice/by-name/recovery flags=display="Recovery";backup=1
/system ext4 /dev/block/bootdevice/by-name/system flags=display="System";backup=1;wipeingui
/misc emmc /dev/block/bootdevice/by-name/misc flags=display="Misc";backup=0
/cache ext4 /dev/block/bootdevice/by-name/cache flags=display="Cache";backup=1;wipeingui;wipeduringfactoryreset
/data ext4 /dev/block/bootdevice/by-name/userdata flags=display="Data";backup=1;wipeingui;wipeduringfactoryreset;length=-16384
/sdcard0 vfat /dev/block/mmcblk1p1 flags=display="Micro SDCard";storage;wipeingui;removable;backup=0
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
______________________________________________________________________________________________________________________
heres he stock recovery.fstab
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
#device mount point fstype [device2] [length=]
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1 wait
/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered wait,check
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc wait,check,encryptable=footer
/dev/block/mmcblk1p1 /sdcard vfat nosuid,nodev wait
/dev/block/bootdevice/by-name/boot /boot emmc defaults defaults
/dev/block/bootdevice/by-name/recovery /recovery emmc defaults defaults
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
none of the partitions show up except (microsd card)
what am i doing wrong
Interested in recovery for this tablet also. Any luck?
Sent from my SM-N960U using Tapatalk
Hello Good People,
Is there a working TWRP for this tablet?
T.I.A.
Hello again,
Is there any working recovery for this tablet.
Its very very difficult to find a custom ROM.
Are people using LineageOS ?
T.I.A.
Hi to all, I hope to be posting in the right section...otherwise...punish me plz
It's a long story, so i hope that someone has time and want to put some effort to help me understand what i'm doing wrong.
By the way i work in IT field and have some knowledge about linux (let's say 5 on 10) but not so many on how android really works, but i'm confortable with custom recovery and roms, i'm still using an s4 mini (GT-I9195) with mine android 9 custom rom and i'm super happy with it.
Now that presentation are done , here is the matter.
I've found an old zp980 32GB (NOT the "plus one") that some years ago i've rooted it flashed with recovery and custom rom. all was working, but at some point i started playing with fdisk and parted and i messed up things.
Honestly i don't remember what exactly i was doing, but now the status of the phone is:
System not booting
I can enter into Recovery (custom TWRP by dezmen3 v2.4.4.0)
I can connect to adb into recovery
I cannot flash rom trough recovery due the actual system partition (589 MB)
I cannot flash the original rom trough SP flash tool due "SFT enable dram failed (4032)" error
The partitions actually are (what i can see from recovery):
System (589 MB)
Data (54MB)
Boot (6 MB)
Recovery (6MB)
Cache (4 MB)
uboot(0 MB)
nvram (5 MB)
Free space: 27412 MB
Actually, I've tried to reformat the memory using SP flah tool, but i got the same error "SFT enable dram failed (4032)", all drivers are ok, i can see COM port in deivce manager tried win 10 and even win 7.
SP tool ver. used v5 1720 more updated version tells me that the brick i'm tringo to flash in not supported anymore xD
Here a dump of fdisk -ul /dev/block/mmcblk0 from adb shell
Bash:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1024 1022 2147483647+ 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 26624 47103 10240 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 47104 67583 10240 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 93184 105471 6144 83 Linux
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 134144 1465343 665600 83 Linux
/dev/block/mmcblk0p6 4869120 1022 2145049599+ 83 Linux
if i make a print from parted (pushed with adb) I get:
Error: Can't have a partition outside the disk!
Before i was also having an error saying that there was an extended partition into a logical one (don't ask me how I do it), but i removed it
So, now....what to to to rescue this device?
by the way honestly except for the instinct of "recover things that doesn't work" my main purpose is understand:
What I've messed on the partitions
Why sp flash tool can't reformat/flash the memory (i haven't tried to manually modify it again)
no brave person hat want to help me to brick it in a bad way?
EDIT NEW INFO
i've understtod that the problem was caused by
/dev/block/mmcblk0p1
and
/dev/block/mmcblk0p6
start and end were inverted , them were overflowing.
Now i used fdisk to remove part 1 (the extended), so i've lost also 5 and 6 (system and cache) and i have recreated them using 1 GB for each and using correct sector order.
now SD and try to flash a ....random compatible rom....see u later for info.
Cross your finger for me xD
flash failed it cant mount system and emmc.....
and now
~ # cat /etc/fstab
/cache ext4 rw
/data ext4 rw
/emmc vfat rw
/system ext4 rw
/sdcard vfat rw
/sd-ext auto rw
if someone has a zp980/c2 working can please post me the result of
cat /etc/fstab
from adb shell??
and a fdisk -ul?