Database Info

[MOD] MT6577 2GB Data Repartition/ SdCard Swap [HACK], INT2EXT (data2ext)

All MT6577 android phones are 'STILL' plagued by low internal memory issue...
{
"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"
}
Credits to X-Dron from russia, now you'll have 2GB of internal storage instead of 512MB with this mod ! :good:
I've included a google direct translated version for the help file, some sentence doesn't make sense but i'm sure you'll figure it out on how to use it...
X-Dron claim his mod is universal & it can be use on all MT6577... :good:
You can follow the original thread here...
Added on Oct 04, 2012 - SdCard Swap
What the f... , you have use up your 2GB Internal Memory & you can't install any more apps...
Credits to EMF, he found this hack & it is working well on my MT6577... :good:
Originally, this hack by 神族-bpok which install .smssecurity to app folder which is meant for V970 so attach copy here, i've deleted it so that it can be use on any MT6577 via cwmr...
Having said that, it is best that you copy your original vold.fstab before installing this hack so that, if anything were to go wrong, you can still revert it back to original state... Just open revert2ori.zip with 7zip but don't extract it, drag & drop your original vold.fstab into it & flash via cwmr... :good:
What this hack did is that it swap the mount points at vold.fstab...
Original
Code:
dev_mount sdcard /mnt/sdcard [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.0/mmc_host
dev_mount sdcard /mnt/sdcard[COLOR="blue"]2[/COLOR] auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-sd.1/mmc_host
Hack
Code:
dev_mount sdcard /mnt/sdcard[COLOR="blue"]2[/COLOR] [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.0/mmc_host
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-sd.1/mmc_host
It is also possible to manual edit vold.fstab as confirmed working by other thread...if it doesn't then power off, take out the battery, wait few sec then put it back & reboot...
If it still doesn't work, you can try manual edit & add 2 to vold.fstab.nand
Original
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.1/mmc_host
Hack
Code:
dev_mount sdcard[COLOR="Blue"]2[/COLOR] /mnt/sdcard[COLOR="Blue"][B]2[/B][/COLOR] auto /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.1/mmc_host
Some report that this works well with 32GB SdCard too ! But make sure to use minimum Class 4 & above...
Bravo to the original developer/ hacker...
--------------------------------------
Added on Oct 17, 2012 WARNING : MEDIATEK SMART PHONE FLASH TOOL
i've seen far too many times that fellow xda member make this same mistake over & over again, including myself...
So pls pls people, don't use SP Flash Tool & download ROM not meant for your phone, it will brick it & there is no way to revive it back ! After you have download wrong PRELOADER, your phone will be completely dead, cannot power on, no charging, no recovery, no USB vcom detection & you can say
to it...
Here is the WARNING again :
NEVER DOWNLOAD ROM NOT MEANT FOR YOUR PHONE. IT WILL BRICK IT !
--------------------------------------
Added on Dec 02, 2012 - INT2EXT on MT6575 / 77 for the extreme gamers !
Finally found a way to install 200 over games on my MT6577 & i'm sure it will work on MT6575 too... :fingers-crossed:
So here is the updated tut to do that... Works on ext 2, 3 or 4... :good:
As usual the credits, without these Master Shifu's sharing, this mod would not be here...
croniccorey
mastermind1024
KarmaToBurn
--------------------------------------
Added on Jan 03, 2013 - Data Repartition APK for MT6577
Full credits to jaydvn, he has found it, translated it & share with us this super easy to use app...
Refer to this post here onwards...
--------------------------------------
Added on Feb 25, 2013 - Operation to Support & Reward our MTK SoC Developers
Head up to here & show your support...
--------------------------------------
Added on June 26, 2013 - How to use your 64GB Micro SDXC for Android-powered smartphone that supports only up to 32GB
Found an interesting article here but i haven't try it b'cos i don't have a 64GB Micro SDXC...
Its in Russian so use Google Chrome built-in translations, it makes more sense... :laugh:
Its for people who already had a 64GB SDXC to try out, anyone care enough to report back whether it works... :fingers-crossed:
--------------------------------------
Added on Dec 12, 2013 - MT6589 MBR, EBR1, EBR2 explained
MT6589 MBR, EBR1, EBR2 are the least explained thanks to Master Shifu nightcraw for the detail explanations, i'm a complete zero when it comes to Hex calculations...
Original idea by JohnnyInBriz i've requested Master Shifu nightcraw to edit it so here it is, all formula already setup so you can resize cache, android system, usrdata, fat & it will let you know what to edit to the MBR & EBR....
Hopefully it will be useful to those DYI'er who wants to resize partition themselves & mod at your own risk... :laugh:
--------------------------------------
Added on Dec 25, 2013 - MoreApp.apk
This mod was shared at another forum but under constant spamming...
Not to waste a good mod by Master Shifu Michfood here is the link... :good:
WARNING : Make a backup first. This mod will shift all apps to sdcard ./android_secure & therefore freeing all internal space & CWMR/ TWRP does backup it too...

Wow another great guide here. I'll try and report back once it finish.

Hi yuweng
Nice trick, though not new to me. The reason I did not describe this in my thread is because in Settings->Storage, you can simply choose which SD card is used, internal or external. (internal one is called USB). No hacking of fstab needed
But I see soo many people doing this, or other tricks, I start to wonder: Maybe the settings->storage choice is only on Lenovo? Do you not have this on other MT657x phones? Or are people just looking passed the build in selection?
PS: your other tutorial, on retrieving a scatter file and recovery image from a phone, is really good. I will use that if I ever get a phone for which there is no ROM yet.

Wow,
Master Shifu cybermaus dropping by to my thread, really honor to have you here...
Haha, i'm one of those who like to keep all my games all at the phone & this is where this hack comes in... :good: So far that i've tried, even it is set to SD card, the internal memory will keep on decreasing, while with this sdswap hack, preferred install location set to Phone Storage(its swap now), i've installed more than 2GB games & internal storage stay the same size... :laugh: Kudos to the developers of android games, Wow, those recent games graphics are really amazing & some are really addictive too...
Learn that trick from Master Shifu bgcngm blogspot, discovered it can be use on MT6577 too, however its start address is offset for MT6577...

It's work!
I managed to successfully root my EASTCOM W5500 One X with this tutorial. But, 7z.exe needed to be updated to latest version (for my case, Windows 7 64bit). Other run well. Superuser reported working well. Adfree works as expected. So, I deleted all Chinese apps and make it feel stock.
Next step: create a custom rom for my device :fingers-crossed:
update (22/10/2012) : Error flashing zip file, back to kitchen..

But, 7z.exe needed to be updated to latest version (for my case, Windows 7 64bit).
update (22/10/2012) : Error flashing zip file, back to kitchen..
Click to expand...
Click to collapse
haha, been using x86 earlier b'cos of driver compatibility issue but now also lazy to upgrade...
Yeoh bro, for Android Kitchen to work on MT6577, you'll need 'curi ayam' patching...
There are so many MT6577 out there, to update edify_defs for all model is crazy...
After extraction at AK, go to ADVANCED OPTIONS -> Convert update-script or updater-script -> Convert update-script to updater-script (Edify)
Then go to AK -> tools\update_files folder, copy emmc-update-binary to WORKING folder \META-INF\com\google\android, delete existing copy & rename emmc-update-binary to update-binary
Open updater-script with Notepad++ & delete the 2nd & 3rd line & add the following to the 2nd line & save it...
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p3");
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
Build ROM from working folder & Voila, you'll have Android Kitchen working on MT6577 & i believe it will work on MT6575 too... :fingers-crossed:
If you need to add apps/ games to WORKING folder /data/app then you will need the below...
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p5");
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/data");
package_extract_dir("data", "/data");
set_perm_recursive(0, 0, 0777, 0777, "/data");
format("ext4", "EMMC", "/dev/block/mmcblk0p3");
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
AK will works with either system.img or system.ext4.tar but *.tar will take a longer time to decode symlink...
As usual, wipe data/ factory reset first before installing ur newly created update.zip...
Actually you don't need to format statement also at updater-script since you already manually done it...

Thanks for the guide but still got no time to continue the custom rom. Will update once I got time
Sent from my W5500 using xda premium
---------- Post added at 10:29 PM ---------- Previous post was at 09:48 PM ----------
cybermaus said:
Hi yuweng
Nice trick, though not new to me. The reason I did not describe this in my thread is because in Settings->Storage, you can simply choose which SD card is used, internal or external. (internal one is called USB). No hacking of fstab needed
But I see soo many people doing this, or other tricks, I start to wonder: Maybe the settings->storage choice is only on Lenovo? Do you not have this on other MT657x phones? Or are people just looking passed the build in selection?
PS: your other tutorial, on retrieving a scatter file and recovery image from a phone, is really good. I will use that if I ever get a phone for which there is no ROM yet.
Click to expand...
Click to collapse
I can confirm that this option is not working on my MTK6577 One X. tried few time, but still store on phone storage instead of sd card

yuweng said:
All MT6577 android phones are 'STILL' plagued by low internal memory issue...
Credits to X-Dron from russia, now you'll have 2GB of internal storage instead of 512MB with this mod ! :good:
I've included a google direct translated version for the help file, some sentence doesn't make sense but i'm sure you'll figure it out on how to use it...
X-Dron claim his mod is universal & it can be use on all MT6577... :good:
You can follow the original thread here...
Added on Oct 04, 2012 - SdCard Swap
What the f... , you have use up your 2GB Internal Memory & you can't install any more apps...
Credits to EMF, he found this hack & it is working well on my MT6577... :good:
Originally, this hack by 神族-bpok which install .smssecurity to app folder which is meant for V970 so attach copy here, i've deleted it so that it can be use on any MT6577 via cwmr...
Having said that, it is best that you copy your original vold.fstab before installing this hack so that, if anything were to go wrong, you can still revert it back to original state... Just open revert2ori.zip with 7zip but don't extract it, drag & drop your original vold.fstab into it & flash via cwmr... :good:
What this hack did is that it swap the mount points at vold.fstab...
Original
Code:
dev_mount sdcard /mnt/sdcard [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.0/mmc_host
dev_mount sdcard /mnt/sdcard[COLOR="blue"]2[/COLOR] auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-sd.1/mmc_host
Hack
Code:
dev_mount sdcard /mnt/sdcard[COLOR="blue"]2[/COLOR] [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.0/mmc_host
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-sd.1/mmc_host
It is also possible to manual edit vold.fstab as confirmed working by other thread...if it doesn't then power off, take out the battery, wait few sec then put it back & reboot...
If it still doesn't work, you can try manual edit & add 2 to vold.fstab.nand
Original
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.1/mmc_host
Hack
Code:
dev_mount sdcard[COLOR="Blue"]2[/COLOR] /mnt/sdcard[COLOR="Blue"][B]2[/B][/COLOR] auto /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.1/mmc_host
Some report that this works well with 32GB SdCard too ! But make sure to use minimum Class 4 & above...
Bravo to the original developer/ hacker...
--------------------------------------
Added on Oct 17, 2012 WARNING : MEDIATEK SMART PHONE FLASH TOOL
i've seen far too many times that fellow xda member make this same mistake over & over again, including myself...
So pls pls people, don't use SP Flash Tool & download ROM not meant for your phone, it will brick it & there is no way to revive it back ! After you have download wrong PRELOADER, your phone will be completely dead, cannot power on, no charging, no recovery, no USB vcom detection & you can say
to it...
Here is the WARNING again :
NEVER DOWNLOAD ROM NOT MEANT FOR YOUR PHONE. IT WILL BRICK IT !
Click to expand...
Click to collapse
awesome, i was looking for this tutorial, to repartition my umi x1 mtk6577 , thanks, but i don't want the sdcard swap, only want to delete emmc partition
so its only the first file needed to flash using cmw right? or i can edit the vold.fstab on my own rom

yuweng said:
So pls pls people, don't use SP Flash Tool & download ROM not meant for your phone, it will brick it & there is no way to revive it back ! After you have download wrong PRELOADER, your phone will be completely dead, cannot power on, no charging, no recovery, no USB vcom detection & you can say
to it...
Here is the WARNING again :
NEVER DOWNLOAD ROM NOT MEANT FOR YOUR PHONE. IT WILL BRICK IT !
Click to expand...
Click to collapse
Just to let you know...
I have a GooPhone Y5 .. and I have actually tried to flash my phone with the Zopo Z100 or Z200 (I don't remember) ..
The phone went dead.. BUT.. After installing the preloader driver for the Zopo device (just like a did for the GooPhone before first use of FlashTool) I was able to use FlashTool again.. and back on GooPhone ROM

@androidnyubi
Yes, just use the MTK6577_Data_Repartition.7z by X-Dron. However, found out lately, most users doesn't have factory ROM & they started modding this & that which is very dangerous... Use MTK Droid Tool by russian Master Shifu rua1 to backup your whole ROM with it... :good: There is an option there to create scatter.txt so you can revert it back when needed... :good:
@whitetigerdk
Wow, this is a good find... :good: it means MT6575/ 77 is 'unbrickable' after all...

thanks yuweng, this umi x1 actualy my 1st mtk based android, confusing which hack compatible with this chip hehe..
Sent from my HTC Desire V using xda app-developers app

Repartition APP for MT657x (Need root)
This app helps you have up to 3GB internal storage (Data Partition) <DOWNLOAD>
*Phone must me rooted.
*Run the app > Choose the size of data partition you want (I choosed 3GB ("Bộ nhớ 3GB, bỏ thẻ SD trong" in app's menu) because after swap sdcard, i feel internal SDcard is useless).
*Then Reboot to Recovery ("Khởi động máy vào Recovery" in menu).
*Once rebooted to Recovery> wipe data/factory reset.
*After reboot, you will have the size of data partition you want.
-Good luck!
-Sorry for my bad English!
-App's language is in Vietnamese

Yeoh bro, i've unpack it & notice it is actually replacing the EBR1 & MBR...
i suggest that you get Sir.nguyenhaiduongbk or phi.long to translate it to English first before sharing it here as no one else will benefit from it... :laugh:
And please include an English Readme.txt on how to use it too...

yuweng said:
Yeoh bro, i've unpack it & notice it is actually replacing the EBR1 & MBR...
i suggest that you get Sir.nguyenhaiduongbk or phi.long to translate it to English first before sharing it here as no one else will benefit from it... :laugh:
And please include an English Readme.txt on how to use it too...
Click to expand...
Click to collapse
Ok bro, i think this app does the same way with yours, just replace ebr1, i'll ask them to translate it to english then share after.
---------- Post added at 11:14 AM ---------- Previous post was at 11:09 AM ----------
yuweng said:
Yeoh bro, i've unpack it & notice it is actually replacing the EBR1 & MBR...
i suggest that you get Sir.nguyenhaiduongbk or phi.long to translate it to English first before sharing it here as no one else will benefit from it... :laugh:
And please include an English Readme.txt on how to use it too...
Click to expand...
Click to collapse
Can i ask you one more question, i use android kitchen to make update.zip of rom, but after flash the zip file, my wifi can't be turned on, do you know it because of boot.img or updater-script?

Translated Repartition APP
I've translated Data Repartition Tool to English <DOWNLOAD>
Hope you enjoy it!

Yeoh Bro, did a full test & it is working great, thank you so much for sharing...
[Original Size] [500MB] [1GB] [2GB] [2.5GB] [3GB]
However, Factory Reset at TWRP show error but it works after reboot. CWMR Wipe Data/ Factory Reset no error...
jaydvn said:
Can i ask you one more question, i use android kitchen to make update.zip of rom, but after flash the zip file, my wifi can't be turned on, do you know it because of boot.img or updater-script?
Click to expand...
Click to collapse
That problem was solved by Master Shifu dsixda since version 2.14 b'cos of symlink problem, refer to Release Notes here...

Success bro thanks..

yuweng said:
[Added on Oct 17, 2012 WARNING : MEDIATEK SMART PHONE FLASH TOOL
i've seen far too many times that fellow xda member make this same mistake over & over again, including myself...
So pls pls people, don't use SP Flash Tool & download ROM not meant for your phone, it will brick it & there is no way to revive it back ! After you have download wrong PRELOADER, your phone will be completely dead, cannot power on, no charging, no recovery, no USB vcom detection & you can say
to it...
Here is the WARNING again :
NEVER DOWNLOAD ROM NOT MEANT FOR YOUR PHONE. IT WILL BRICK IT !
Click to expand...
Click to collapse
Does this mean that if I want to try a new ROM it is better to leave the original PRELOADER in its place or am I saying something stupid now....
I tried to find what exactly is the function of each part of the firmware but cannot find an easy to understand description.
I guess some of the parts of a ROM are very machine dependent and others are more general.
It would be nice if somebody could describe relations and dependencies of the different parts.
Luit

yuweng said:
Yeoh Bro, did a full test & it is working great, thank you so much for sharing...
[Original Size] [500MB] [1GB] [2GB] [2.5GB] [3GB]
However, Factory Reset at TWRP show error but it works after reboot. CWMR Wipe Data/ Factory Reset no error...
That problem was solved by Master Shifu dsixda since version 2.14 b'cos of symlink problem, refer to Release Notes here...
Click to expand...
Click to collapse
I've already updated kitchen to 2.18 but still no wifi after flash update.zip. my device's board is 'signal77_ics2', maybe I'll try to rename some files in edify_defs folder to make kitchen define my device. Thanks.

it doesnt sink in to me yet
could someone explain further.
i have
1gb rom internal mem
16gb internal sd
2gb external micro sd (the removable one)
what will happen to them?
i cannot figure out a way to open the phone to replace the external sd.
thank you!:good:

[PATCH] Enable native USB-OTG access on Nexus 7 (grouper) (02/12/12)

Hello,
i found a description for enable the native USB-OTG access on this Website. You don't need any app, e.g. StickMount, for the USB access. This is a flashable patch for your Nexus 7 (grouper) device.
Requirements:
- customize recovery
- root access
- USB-OTG cable
Note:
Use Kernel 3.1.10-g830e42f from CM10-Stable (Only changed entries in boot.img-ramdisk.gz).
Tested with:
JB 4.1.2: CM10-ROM, SmoothROM v4.1 and Stock-ROM
JB 4.2.1: CleanROM v3.0 and StockROM.
Thanks:
- CyanogenMod-Team
- Google for Android
MD5:
for JB 4.1.2: f6adbf30518e7d7985430ef277ac5519
for JB 4.2.1: 7a16565c9034ad32920b3466fb81834f

Don't work on my nexus7

@nikdevil
Wich ROM and android version use you?

Cleanrom 2.5, JB 4.2

michaelm_007 said:
Hello,
i found a description for enable the native USB-OTG access on the AOSP-Developer-Website. You don't need any app, e.g. StickMount, for the USB access. This is a flashable patch for your Nexus 7 device.
Requirements:
- customize recovery
- root access
- USB-OTG cable
Tested on Nexus 7 (grouper) with JB 4.1.2 CM10- and Stock-ROM.
MD5: c10d57a8d00072ba29bcb7b33daf6061
Click to expand...
Click to collapse
Can you provide link to where you found this? What versions will it work with 4.2.1, 4.2 or 4.1.2, all versions?

michaelm_007 said:
Hello,
i found a description for enable the native USB-OTG access on the AOSP-Developer-Website. You don't need any app, e.g. StickMount, for the USB access. This is a flashable patch for your Nexus 7 device.
Requirements:
- customize recovery
- root access
- USB-OTG cable
Tested on Nexus 7 (grouper) with JB 4.1.2 CM10- and Stock-ROM.
MD5: c10d57a8d00072ba29bcb7b33daf6061
Click to expand...
Click to collapse
I have to try the patch. It is an elegant solution!
The MODE = 600, I might be wrong but, why not using 666 instead, so that every users can access the data ... might help for >= 4.2.
Interestingly, I have almost the same file in my Ubuntu (with only one line and MODE=666).

alfeuss said:
Can you provide link to where you found this? What versions will it work with 4.2.1, 4.2 or 4.1.2, all versions?
Click to expand...
Click to collapse
link here: http://source.android.com/source/initializing.html under "Configuring USB Access" (i don't know if this is true, because i think it is for the pc, not the nexus. This is the same reason why i think it will not work on the nexus. The zip includes the same code)

@all
Updated ZIP-file

is this work for 4.2.1 ?

michaelm_007 said:
@all
Updated ZIP-file
Click to expand...
Click to collapse
Does not seem to work on my 4.2.1 stock rooted (stickmount is uninstalled).
I have rebooted, patched the v3 in CWM. When back in android, nothing appends when I plug a usb memory stick: it should be mounted automatically in /storage/usbdisk when the usb stick is pluged ? does /storage/usbdisk have to be manally created ?

Doesnt work on AOKP ROM Milestone 1 JB 4.2.

@all
Sorry, i have it tested on JB 4.2.1 and it will not work at the moment. The kernel is the problem and at the moment i can it only offer for JB 4.1.2 :crying:

michaelm_007 said:
@all
Sorry, i have it tested on JB 4.2.1 and it will not work at the moment. The kernel is the problem and at the moment i can it only offer for JB 4.1.2 :crying:
Click to expand...
Click to collapse
Ah too bad! Too nice and simple to be true!
How to remove the patch: just deleting /system/etc/vold.fstab and /system/etc/udev ?

i got to looking into making this work for 4.2 now im no dev or anything and this is just fumbling around with files in a texteditor and or looking at the system files but could it be as easy a fix for 4.2 as this
Code:
## Vold 2.0 fstab for cardhu
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# Mounts the first usable partition of the specified device
dev_mount usbdisk /storage/usbdisk auto /devices/platform/tegra-otg

NicoGa said:
Ah too bad! Too nice and simple to be true!
How to remove the patch: just deleting /system/etc/vold.fstab and /system/etc/udev ?
Click to expand...
Click to collapse
Yes, it should be that. I was bored, so i edited the zip so it will remove the files for you: http://ubuntuone.com/40OkIet0BHFnUhbkMx4Dwf

mid-kid said:
Yes, it should be that. I was bored, so i edited the zip so it will remove the files for you: http://ubuntuone.com/40OkIet0BHFnUhbkMx4Dwf
Click to expand...
Click to collapse
Thanks!
but in fact there may be a typo in your files:
In the zip used to flash the patch the file is named : vold.fstab
While in the zip to remove the patch it is named: void.fstab
Shouldn't it be void.fstab everywhere ?
Also I wonder why you have included a patch with the boot ? (curiosity of a newby)
Finally, where could it be possible to find more information on the mounting process in JB >=4.2 ?

@all
Updated files, now it is compatible with JB 4.1.2 and JB 4.3.1 :laugh:

Will it work on paranoid 2.54 (jb 4.1.2) and M- Kernel a11 ?

@doublin
I think: yes, but my patch use the kernel of CM10 and not the M-Kernel.

Well,I'll do a nandroid and try it myself.
I'll be back in few minutes with feedback.
EDIT:
OK,I just flashed it and plugged in flash drive with some the walking dead episodes.
I can see what's on the flash drive using ES Explorer and Nexus Media Importer.
Problem is i can't open the files. I tried playing the movies using stock movie player and MX Player with no success. Something opens and right after closed back without seeing anything.
Any idea?
EDIT 2:
After a few tests with 2 flash drives ( one NTFS and one FAT16 ) and an external HDD NTFS I noticed that:
The HDD works just fine
The NTFS flash plays only two out of nine episodes.
The FAT16 flash plays two out of four episodes.
Streaming this videos was possible only trough MX Player. Stock video player and ES Explorer's integrated video player didn't work.
I'll keep trying to see what's going on, but anyway this is better than nothing. I was with no USB OTG support with my from and kernel.

[ROM]Adoli v1 | Monster M7 Tablet | Pre-Rooted | 4.1.1

In 2021 This thread and device are pretty much defunct; links in OP are updated though as I've been seeing a few requests lately.
Many thanks to all of the following. This small project would not be possible without their work/research.
Sergio Poverony
BSDgeek_Jake
raishiro
Koush
Garner
Basian Mile
rovo89
Prevailious
arctablet.com
This is a customized version of the most recent stock firmware (v4) for the Monster M7 tablet designed to make your tablet bloat free and easily rooted. Otherwise known as a custom ROM. The android version is 4.1.1.
In order to fully enjoy all the features of this ROM it needs to be flashed via some type of flashing tool through your computer, such as the Rk Batch Tool. Please see the instructions in the second post for setting up this tool properly.
Note that you can simply rename the .img file to update.img and flash it through your phone's recovery, but you'll be missing 3GB of storage in addition to having the manufacturer default allocation for app storage. Everything else should work correctly should you decide to use such a method.
Features:
Pre-Rooted (Koush SuperUser)
Very slim
xPosed framework
Modified Hosts file. Blocks large amount of advertising.
App storage increased to 3GB
All Monster bloatware removed.
DPI set at 160. (you can change this with an app.)
4.4 E-mail and News&Weather Apps.
4.2 Clock App.
Stock Browser with Adobe Flash 11
Added ArcTools for easy CWM installation.
ro.secure=0
ADB debug enabled by default.
Download​
Let me know if there are things you would like to see added. Higher android version at this point is beyond me, and I'm not even sure if it's possible as there is no source code yet available for this particular device. (Let me know if you somehow acquire source code for this device though )

Instructions for setting up the RK Batch Tool and drivers. Thanks to sab99
Shutdown the M7 tablet
Run the RK Batch Tool, Open Device Manager
Connect the USB cable to the PC, while pressing the volume down button on the side of the M7. You will see nothing on the screen, but at this point, Windows should be alerting you to a USB device insertion. At this point my Win 8.1 x64 box kept detecting the device and popping up a failed device message - the Win 7 x64 detected the device and left it as unknown (which is expected).
Go into the device manager, find the unknown device, and update its driver with the Rk Batch Tool driver for your bitness and os.
Now the RK Batch Tool should show green for your tablet.
Load the ROM and press the Recover button.
Have a beer while it flashes.

reserved

reserved

reserved

Open.

Could you please provide a correct drivers for Monster M7? Drivers from Rk Batch Tool you've provided are not working. I've tried on Win8/Win7, 32/64, driver can't start and always shows error 10. I also tried to install on the "Android-free" PC (Win7, 32), no android usb drivers are previously installed - no luck.
P.S. And of course I've tried different USB ports and cables (what is really stupid 'cause my Nexus 7 2013 and all WinPhones are using these cables without problems)

sensboston said:
Could you please provide a correct drivers for Monster M7? Drivers from Rk Batch Tool you've provided are not working. I've tried on Win8/Win7, 32/64, driver can't start and always shows error 10. I also tried to install on the "Android-free" PC (Win7, 32), no android usb drivers are previously installed - no luck.
Click to expand...
Click to collapse
I had an issue with my Windows 8.1 x64 machine, but it worked on a Win 7 x64 machine. The steps to use the RK Batch tool with the M7 are:
Shutdown the M7 tablet
Run the RK Batch Tool, Open Device Manager
Connect the USB cable to the PC, while pressing the volume down button on the side of the M7. You will see nothing on the screen, but at this point, Windows should be alerting you to a USB device insertion. At this point my Win 8.1 x64 box kept detecting the device and popping up a failed device message - the Win 7 x64 detected the device and left it as unknown (which is expected).
Go into the device manager, find the unknown device, and update its driver with the Rk Batch Tool driver for your bitness and os.
Now the RK Batch Tool should show green for your tablet.
Load the ROM and press the Recover button.
Have a beer while it flashes.
Thanks for the cleanups on this ROM, kaiserII101. 3GB, no crapware, and all source code is the way everything should be shipped. At least you fixed 2 of the 3. When you start looking at these 'value' tablets they are all pretty much the same. If you REALLY wanted to sell a ton of your hardware, releasing the source would encourage the modding community here and be worth more advertising dollars than your razor thin margins could ever support.

sab99, thanks for the help but yesterday I figured out by myself (it costs me a few hours of sleep but fortunately it's a weekend )
But definitely TS should add your instructions to the first post! Also, #3 is very important - it's absolutely unclear from TS post and another discussion (someone referred to the bootloader mode as a "flashing mode" that is confusing).
Also, using topic starter's image and RK29xxImageTools, I've increased userdata (internal memory) up to 8GB. Here is parameters for partitioning (I also attached my parameter file):
Code:
CMDLINE: console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:[email protected](misc),[email protected](kernel),[email protected](boot),[email protected](recovery),[email protected](backup),[email protected](cache),[email protected](userdata),[email protected](kpanic),[email protected](system),[email protected](user)
I'm curious: is it possible to completely get rid of "user" (aka "internal sdcard") partition? This "monster" works perfectly with 32GB microsd, so we don't need to waste important nand space...
Also, could we change mtdparts order, to simplify calculations? I mean something like this (showing just the end of CMDLINE string):
Code:
... [email protected](cache),[email protected](kpanic),[email protected](system),[email protected](userdata)
I can't try now: my daughter (3.5 yo) just grabbed the tablet and started installing and reinstalling her favorite games (actually, I've bought this "monster" 'cause her old Gtab 7'' just broke - probably, LCD screen connection problem - but I can't fix it, need a special screwdriver to disassemble. BTW, this Galaxy Tab is a great product - very old but still working).
sab99, could you try "user"-less partitioning (i.e. without "internal sdcard")? Actually it will be great, and this option (if works of course) will significantly improve tablet value.
P.S. Seems like to be able to do this, we also need to comment that line in \system\etc\vold.fstab and repack system.img. Probably, TS can help us...
Code:
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
## Example of a standard sdcard mount for the emulator / Dream
# Mounts the first usable partition of the specified device
#dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
### dev_mount flash /mnt/sdcard auto /dev/block/mtd/by-name/user <-- we need to comment this line (in case we don't want to have "internal sdcard"
dev_mount sdcard /mnt/external_sd auto /devices/platform/rk29_sdmmc.0/mmc_host/mmc0
dev_mount udisk /mnt/usb_storage auto /devices/platform/usb20_otg/usb1
## Example of a dual card setup
# dev_mount left_sdcard /sdcard1 auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# dev_mount right_sdcard /sdcard2 auto /devices/platform/goldfish_mmc.1 /devices/platform/msm_sdcc.3/mmc_host/mmc1
## Example of specifying a specific partition for mounts
# dev_mount sdcard /sdcard 2 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1

Added the instructions for setting up the RK Batch Tool in the second post.
Possible bug with velvet.apk (search) force quitting.. May need to revert to an older version as soon as I can start building again.
As far as eliminating the user partition, I would say, yes it is probably possible. Personally though, I'm not sure I want to do that. Will certainly try experimenting with it though.
Also, please everyone feel free to take the ROM, modify it, and post a link to your modified version (preferably list the changes you made). In order to modify update.img contents easily and repack them into flashable form you can use Sergio Poverony's tools. http://forum.xda-developers.com/showthread.php?t=2445406
I will be travelling to Russia wednesday for 5 months, and so I probably will be out of action here for a week at least I imagine. I will have internet access there eventually, as I'll be getting a sim-card, but important thing is to get settled in there first.

Thanks for your tip but I suggest a better link for the Sergio Poverony's tools
Unfortunately I can't experiment with Monster M7: a little Alice completely occupied a new toy Probably, some guys (also this Monster currently on sale for $75 at Walmart) can do some experiments.
P.S. For us, my "mod" (if I can say) is enough; 8GB + 4GB "internal sd" fits well my daughter's "play pattern" - she has (and download new stuff every day ) a lot of relatively small children games, so these games has all assets packed into .apk.
P.P.S. Here is the link to the "8GB" image: https://www.dropbox.com/sh/3bj2thbf9sfshz8/M_RCCWtsek

Hey congrats on this! Hope you can make many more improvements for a lot of people out there.
Would it be possible to perform an update the regular way after modifying the storage space parameters?

Prevailious said:
Would it be possible to perform an update the regular way after modifying the storage space parameters?
Click to expand...
Click to collapse
I don't think so. But it's not a big problem - we always can do this trick again; the main problem is about update; I don't think the manufacturer will release any major update (like KitKat) for this device
P.S. BTW, we've got exactly what we paid for... What are you expecting for $75 device?

Awesome!
i wasn't expecting much from this tablet, but daaaang, good job guys. i was expecting to have to try Kingo or Framaroot to get a root on this. you guys have it rooted AND the user partition expanded!! too cool. +1000!

Zzz73 said:
i wasn't expecting much from this tablet, but daaaang, good job guys. i was expecting to have to try Kingo or Framaroot to get a root on this. you guys have it rooted AND the user partition expanded!! too cool. +1000!
Click to expand...
Click to collapse
Same here.

The link to the RK Batch Tool in the OP doesn't work. Will this version work?
http://www.freaktab.com/showthread.php?5173-New-Rockchip-Batch-Tool-v1-7-Plus-v3-5-Drivers
Just picked up two of these tablets for my kids and would like to remove the extra crap and increase the size of the internal storage partition.
---------- Post added at 10:30 PM ---------- Previous post was at 09:40 PM ----------
OK, so what am I doing wrong? I'm trying to follow the instructions in POwer #2
I powered off the M7 by holding down the power button and choosing to Shut Down. When I plug in the usb cable, nothing happens. Windows doesn't detect anything at all.
Was I just supposed to turn off the screen but not shut down the entire tablet? I don't get any Device Connected messages, nothing shows up in Device Manager, etc.

OK, well. No idea why the heck it didn't work last night but it worked fine just now. Whole process took like 3 minutes. Wasn't even enough time to go get a beer.
Update:
Well, looks like I spoke too soon. It boot sup to the Monster screen and then just stops. It never continues on. Anyone have any suggestions?
Update2:
I flashed it again and this time it gave me the sphere after the update and then came up. One thing I notice is that some of the fonts seem hard to read in the Play Store. Not sure if that's because of the DPI setting change or what. Nice to see such a small list of apps when I view the All Apps page.

Anyone use the image in the OP and have trouble using the Clear Notifications button when you swipe up the notification bar? It takes me like 1o tries to tap it because most of the time it just registers that I'm tapping the whole bar and toggles between notifications and whatever the other screen is.
I'm guessing it's just my fat fingers but thought I'd see if I'm really going insane or not...

kelemvor33 said:
Anyone use the image in the OP and have trouble using the Clear Notifications button when you swipe up the notification bar? It takes me like 1o tries to tap it because most of the time it just registers that I'm tapping the whole bar and toggles between notifications and whatever the other screen is.
I'm guessing it's just my fat fingers but thought I'd see if I'm really going insane or not...
Click to expand...
Click to collapse
it's not just you. I have noticed the touchscreen not being very responsive. drives me nuts. also the touch accuracy is a little off... no big deal, still a decent tablet for what I paid.
Sent from my Optimus G using Tapatalk

So I got an update prompt for SuperUser today. I tried the "Install" button and instantly got an error. So I then tried the Recovery Install option and the tablet has been sitting there for 10+ minutes and I don't know if it's doing anything.
Anyone know if this should eventually work or what's going on?
Thanks.

Easy Magic PhilZ Touch Installer for MediaTek Devices ONLY (Developers ONLY)

* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 6 Recovery
CWM Advanced Edition 6.x
* * * * * * * * * * * * * * * * * * * * * * * * *
​
PhilZ Touch CWM Advanced Edition is developed by XDA Recognized Developer Phil3759 now fully supports MediaTek devices . . .
{
"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"
}
Supports Five generations of MediaTek SoC in One-Porting-Tool.
Arm11
Cortex-A9
Cortex-A7
big.LITTLE
Cortex-A53
Video Preview
For full features & functions, refer to Main Thread here . . . :good:
Credits
Phil3759
Michfood
suhas.holla
shoxxy
Last but not least, my Master Shifu Carliv who has taught me how to compile & continuously guiding me to the right direction & also many DEVs that shared & published their findings on the World Wide Web on various subject . . . . . .
Updated Credits - Added support for MTK big.LITTLE & Cortex-A53
Huge Credits to . . .
Russian Master Shifu Javum
Master Shifu Carliv
Huge Thanks to Xpeca1 for confirming all the porting tool features & functions is working correctly on his Cortex-A53 & not forgetting NiksSkersts too . . . :highfive:
This updates has the most beta-tester, never the less, thanks for all their contributions too . . .
XDA:DevDB Information
Easy Magic PhilZ Touch Installer for MediaTek Devices ONLY (Developers ONLY), Tool/Utility for all devices (see above for details)
Contributors
yuweng
Source Code: https://github.com/PhilZ-cwm6/philz_touch_cwm6
Version Information
Status: Stable
Current Stable Version: Final Release 6.59.0
Stable Release Date: 2015-03-09
Created 2014-05-11
Last Updated 2015-04-09

Terms & Conditions of Use
codeworkx said:
DEAR KANGERS
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't meant Out-of-Respect!!!
Thanks to all contributors!!!
Click to expand...
Click to collapse
As Master Shifu codeworkx says, the same applies here . . .
All i'm asking is for you to give proper credits to me & the DEVs that i mentioned on the porting tool, without them sharing, this porting tool wouldn't have exists !
i have seen many that took my work, got a ported working PhilZ Touch on their MTKs & shared it directly even here on XDA ! while some at other forum threads BUT not a single word mentioning this thread, me or the porting tool or the DEVs that has contributed to this project . . .
Many just make a new thread with the ported PhilZ Touch & shared it with their followers, fooling their followers by not mentioning credits so that their followers thinking that the ported PhilZ Touch is built from source & is their own work, collected all the Thanks & that will make them look cool while some even solicit for Donations !
Anyone can just download this porting tool, run the exe & they will get a ported PhilZ Touch on their MTK, what is so cool about that . . .
Do you know how many hours i have put into this, not mentioned is the time studying & building PhilZ Touch from source, PC hardware upgrading, broadband fee, electricity fee, time to study & building this porting tool exe & i'm sharing this all for FOC & i don't solicit for Donations or Thanks in return, i don't even post my Donate button . . .
If you wanna start a new thread to support specific MTK devices with the ported PhilZ Touch, i have absolutely no problem with that, it will be your responsibility to response & provide support to your followers but pls give proper credits . . .
If you think this porting tool is too complicated & you would wanna start a new thread/ guide/ video or whatever either here or else where, again i have absolutely no problem with that BUT pls pls don't mirror the porting tool. i'm sure you have seen this all the time at XDA here by other DEVs, the logic is very simple, when you mirror the files, there is no way of tracking which version has bugs. Most importantly, i need direct feedback from users & when you mirror the files, your followers will download that version from your link & they complain & feedback to you but you won't be able to fix it so pls put a link direct to this thread so that i can improve on this porting tool.
If you wanna post this porting tool on your blog, website or anything at all, again i have absolutely no problem with that BUT again post a link directly to this thread so that users can always post a bug report here & they will always get the new, bug free porting tool as i will fix it when i receive bug report.
Credits mentioning & redirecting link to original threads won't make you low standard, in fact your followers will be thanking you for sharing with them a great new tool that you found. Credits mentioning & redirecting link to original threads also means that you give respect & honor the original DEVs of the tool, this would also enable feedbacks on new ideas, new features & improvement of that particular tool too.
If you are a company then pls get my permission first or the least you can do is Donate to Phil3759 for a job well done & if you are an end user, you are also encourage to do so too, fyi, i did . . .
Features
Auto mode
- You don't need to know a thing & it'll port a working PhilZ Touch 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, MTK fixes, Flip screen/ Flip Touch, different font size & uses all files from your stock recovery when using recovery.img. For boot.img porting, this tool will only use its kernel only. Refer to here for more info . . .
- device resolutions
- 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
- Works from Gingerbread to Lollipop but NOT on encrypted data partition on Lollipop but why you enable it back ?
- No need ro.secure=0 to run
recovery.fstab How-to
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 PhilZ Touch by other DEVs & see how they did it.
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 PhilZ Touch restore would not be able to restore it or for that matter, your device wouldn't even be able to boot at all (brick), thats why it is important to backup your Factory ROM with MTK Droid Root & Tools first.
For latest MTK armv8
Since the latest MTK armv8 is using direct device path, below is possible as i've seen it on msm devices but personally i think it is unnecessary to have those partition backed up as it will take alot of space & typically you only brick the system or data partition but then again, that is entirely up to you on what you wanna backup. Below example is taken from Master Shifu Carliv github, added all various armv8 devices direct device path partition for reference. To find out the actual MTK armv8 partition info on your device, use the command adb shell cat /proc/partinfo & adb shell ls -al /dev/block/platform/mtk-msdc.0/by-name
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#<src> <mnt_point> <type><mnt_flags and options><fs_mgr_flags>
/dev/block/platform/mtk-msdc.0/by-name/boot /boot emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/nvram /nvram emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/flashinfo /flashinfo emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/expdb /expdb emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/secro /secro ext4 relatime wait,check
/dev/block/platform/mtk-msdc.0/by-name/seccfg /seccfg emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/proinfo /proinfo emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/para /para emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/logo /logo emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/tee1 /tee1 emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/tee2 /tee2 emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/otp /otp emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/lk /lk emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro,noatime wait
/dev/block/platform/mtk-msdc.0/by-name/preload /preload ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=/dev/block/platform/mtk-msdc.0/by-name/metadata
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/persist /persist ext4 relatime wait,check
/dev/block/platform/mtk-msdc.0/by-name/custom /custom ext4 relatime wait,check
/devices/mtk-msdc.0/11240000.MSDC1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto
To manually make a SP Flash Tool backup of your MTK armv8 Factory ROM then refer to here & you can also use the following empty cache secro userdata since a Factory Reset/ Wipe Data will wipe data partition anyway.
Updates
Refer to here & here for custom partition backup/ restore on armv8 Thanks to Katinatez . . . :good:
Refer to this the only lead shared by BachMinuetInG . . . :good:
Aroma File Manager
It is a known problem that aromafm will not to work properly on flip-screen, this is not a PhilZ Touch problem as it has never been updated for almost a year.
Flip Screen/ Flip Touch/ Font size
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 into the porting tool -> Manual-mode -> Try all combinations one at a time until one that works for your device.
Typical Flip Screen device then choose either Flip Screen Only or Flip Screen FlipX-FlipY. For Landscape devices (tabs), typically is SwapXY FlipY.
As said, i don't own all MTK devices so i donno which font size is suitable for your device so again, you'll need to play around with the different selection. Below are available fonts as demonstrated on my 480x854 res . . .
Bug report <- No support if you don't attach it to your post.
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 PhilZ Touch -> Advanced Functions -> Report Error -> Copy log from /sdcard/clockworkmod/philz_recovery.log -> Attach to your post
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 18 March 2015, there are only 14 pages . . .
The 2nd reason you don't see me replying is i donno the answer then head up to PhilZ Touch development thread & get help from Phil3759 directly . . .
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
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 !
To check your bootloader
Code:
adb reboot-bootloader [COLOR="Blue"]or[/COLOR] adb reboot bootloader [COLOR="blue"]or[/COLOR] adb reboot fastboot
fastboot getvar all
Code:
(bootloader) unlocked: NO
To unlock it, use below command.
Code:
fastboot oem unlock
Source
As explained BRANDED at the OP, UNBRANDED MTKs are generally MTKs directly from China, have unlock bootloaders.
Updates
MTK armv7/ armv8 LP refer to this workaround, make sure to unlock your bootloader first !
List of supported MTK devices . . .

Installation
Installation How-to
Where is the Downloads . . .
WARNING
Even though wrong installation of custom recovery normally will bricks the recovery only however it is better to be safe than sorry.
PhilZ Touch 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, double-click PhilZ Setup & 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, fyi, tested working on XP to Win10 Technical Preview . . .
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. Refer to screenshot -> View attachment 3018860
Did you try latest google ADB driver while for XP try this one

Known problems on MTK devices
Known problems on MTK devices
E: failed to mount /cache
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.
PhilZ Touch does not support ubifs
PhilZ Touch does not support MTK Alcatel devices with /custpack partition. Added support at beta version
Haven't identify latest voldmanaged mount points for Internal SD that uses /storage/usbdisk voldmanaged=usbdisk:auto so it won't mount Internal SD on such layouts. Thanks to adhamamar for sharing the solution. :good:
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.
Thanks to shoxxy for the tip, flip screen works on PhilZ Touch with added Flip screen flag. However, it has a small glitches that is the screen will flashes & flip upside down when using the virtual keys. Since Touch is fully working either don't use the virtual keys or just disable it permanently. PhilZ Settings -> GUI Preferences -> Toggle Virtual Keys
Updates
Fixed flip screen flickering, Thanks to Teamwin updated flip screen codes . . . :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 PhilZ Touch 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 PhilZ Touch #
Do not try this on lock bootloader MTK devices as there has been confirmed cases that it will brick it, refer to here for more info.
---------------------------------------
This tool will auto-install Aroma FileManager & it is a known problem on some MTK devices that Aroma FileManager refuses to start & complains about E:Can't make /tmp/update_binary -> Installation aborted . . .
On Flip screen MTK device, Aromafm will always be flipped & the answer is here
Work around - Built-in to porting tool
Use the Auto mode first & it will auto make a backup of your current recovery.
Pull out the USB cable & use the Manual mode, copy recovery.img from BackUp-MTK-Recovery folder to Stock & it will ask you to plug-in the USB to PC.
Now open Stock/recovery/rmdisk/init.rc with Notepad++ & add the line as below & save it.
Plug-in USB cable to PC, press OK, select your device res & it'll auto install it.
Code:
mkdir /emmc
mkdir /system
mkdir /data
mkdir /cache
[COLOR="blue"][B]mkdir /tmp[/B][/COLOR] [COLOR="Red"]<- add this line to init.rc[/COLOR]
mount tmpfs tmpfs /tmp
chown root shell /tmp
chmod 0775 /tmp
Aroma FileManager shall work now.
---------------------------------------
On my friend's old ICS 4.0.4 MT6577 with 480x854 res, ported PhilZ Touch doesn't boot & later i found out its something to do with the kernel not supporting PhilZ res more than 320x480.
Work around - Built-in to porting tool
At Windows Explorer -> Show Hidden Files & Folders -> MTK_PhilZ -> bin -> extract out 240x320_bg.png from res.7z, rename it to stitch.png
Plug-in the USB cable & use the manual mode, select your device res & it will ask whether you have flipped screen.
Copy & paste extracted 240x320 stitch.png to Stock/recovery/rmdisk/res/images folder to replace it & answer the flipped screen question
At PhilZ Settings -> GUI Preferences -> Change Background -> Reset Koush Background

Trouble-shooting
Trouble-shooting the mount USB storage
Huge credits to suhas.holla, the fstab v2 AKA unified fstab has been demystified for MTK devices & mount both sdcard at PhilZ Touch is working perfecty now. . . :laugh:
i don't own every MediaTek devices out there so most probably some will not mount USB storage for both of the storage while at recovery b'cos of different voldmanaged path.
Updates - Built-in to porting tool
Refer to below on how to identify it & correct this problem.
Open a new Notepad & save the below to MTK_PhilZ folder for unpack/ repack of ported PhilZ Touch recovery.img.
MTK_unpack.bat
Code:
@echo off
cd %~dp0
chcp 1251
if (%1)==() (
echo Select image
goto end
)
setlocal enabledelayedexpansion
COLOR 0A
mode con:cols=65 lines=31
bin\sfk166.exe hexfind %1 -pat -bin /88168858/ -case >bin\offset.txt
bin\sfk166.exe hexfind %1 -pat -bin /FFFFFFFF1F8B08/ -case >>bin\offset.txt
bin\sfk166.exe find bin\offset.txt -pat offset>bin\off2.txt
bin\sfk166.exe replace bin\off2.txt -binary /20/0A/ -yes
if exist %~N1 rd /s /q %~N1 >nul
set /A N=0
:loop
FOR /F %%G IN (bin\off2.txt) DO (
if !N!==1 (
set /A ofs1=%%G
set /A N+=1
)
if !N!==3 (
set /A ofs2=%%G
set /A N+=1
)
if !N!==5 (
set /A ofs3=%%G+4
set /A N+=1
)
if `%%G` EQU `offset` (
set /A N+=1
)
)
FOR %%i IN (%1) DO ( set /A boot_size=%%~Zi )
echo.
echo - size of %1 %boot_size% byte
echo - kernel offset - %ofs1%
echo - ram_header offset - %ofs2%
echo - ram_disk offset - %ofs3%
echo.
del bin\offset.txt
del bin\off2.txt
md %~N1
echo - extracting kernel_header...
bin\sfk166.exe partcopy %1 -fromto 0x0 %ofs1% %~N1\kernel_header -yes
echo - extracting kernel...
bin\sfk166.exe partcopy %1 -fromto %ofs1% %ofs2% %~N1\kernel -yes
echo - extracting ram_header...
bin\sfk166.exe partcopy %1 -fromto %ofs2% %ofs3% %~N1\ram_header -yes
echo - extracting ram_disk...
bin\sfk166.exe partcopy %1 -fromto %ofs3% %boot_size% %~N1\ram_disk.gz -yes
echo - unpack ram_disk.gz...
bin\7za.exe -tgzip x -y %~N1\ram_disk.gz -o%~N1 >nul
echo - unpack ram_disk.cpio...
md %~N1\rmdisk
cd %~N1
cd rmdisk
%~dp0bin\cpio.exe -i <../ram_disk
cd ..
cd ..
copy %1 %~N1
echo.
echo - Done ^^!
echo.
pause
:end
MTK_pack.bat
Code:
@echo off
cd %~dp0
chcp 1251
if (%1)==() (
echo Select folder
goto end
)
setlocal enabledelayedexpansion
COLOR 0A
mode con:cols=60 lines=39
set pt=%~N1%~X1
echo %pt%
copy %pt%\ram_header %~N1\new_ram_with_header >nul
cd %pt%
%~dp0bin\chmod og=xr rmdisk
cd rmdisk
echo - pack rmdisk to cpio...
%~dp0bin\find . | %~dp0bin\cpio.exe -o -H newc -F ../new_ram_disk.cpio >nul
move ..\ram_disk ..\ram_disk_old >nul
copy ..\new_ram_disk.cpio ..\ram_disk
echo - pack rmdisk to gzip...
%~dp0bin\gzip -n -f ../ram_disk
echo - add header...
%~dp0bin\dd if=../ram_disk.gz >> ../new_ram_with_header
FOR %%i IN (../ram_disk.gz) DO ( set /A size=%%~Zi )
echo - new ramdisk %size% byte
%~dp0bin\sfk166 hex %size% -digits=8 >../../size.txt
FOR %%i IN (../../size.txt) DO ( set /A size=%%~Zi )
%~dp0bin\sfk166 split 1 ../../size.txt ../../1 >nul
FOR /F %%i IN (../../1.part7) DO (set a1=%%i)
FOR /F %%i IN (../../1.part8) DO (set a2=%%i)
FOR /F %%i IN (../../1.part5) DO (set a3=%%i)
FOR /F %%i IN (../../1.part6) DO (set a4=%%i)
FOR /F %%i IN (../../1.part3) DO (set a5=%%i)
FOR /F %%i IN (../../1.part4) DO (set a6=%%i)
FOR /F %%i IN (../../1.part1) DO (set a7=%%i)
FOR /F %%i IN (../../1.part2) DO (set a8=%%i)
echo %a7%%a8%>size.txt
echo %a5%%a6%>>size.txt
echo %a3%%a4%>>size.txt
echo %a1%%a2%>>size.txt
echo - add new size in header 0x%a1%%a2% 0x%a3%%a4% 0x%a5%%a6% 0x%a7%%a8%
%~dp0bin\sfk166.exe echo %a1%%a2% %a3%%a4% %a5%%a6% %a7%%a8% +hextobin ../../tmp1.dat
%~dp0bin\sfk166.exe partcopy ../../tmp1.dat 0 4 ../new_ram_with_header 4 -yes>nul
echo - make image...
%~dp0bin\mkbootimg.exe --kernel ../kernel --ramdisk ../new_ram_with_header -o ../new_image.img
del size.txt >nul
copy ..\new_image.img %~dp0\new_image.img
move ..\ram_disk_old ..\ram_disk >nul
cd ..
cd ..
del size.txt >nul
del tmp1.dat>nul
del 1.part*>nul
echo.
echo - Done ^^!
echo.
pause
:end
Just Drag&Drop ported PhilZ Touch recovery.img to MTK_unpack.bat to unpack it & Drag&Drop unpack recovery folder to MTK_pack.bat to repack it back. Disable UAC first.
Or you can also download the original Boot/Recovery repack utils for WINDOWS to unpack/ repack the ported PhilZ Touch recovery. Basically it operates exactly the same except for this porting tool, it is using the standalone 7za.exe instead of 7z.exe that requires the 7z.dll to operate.
Huge Credits to Russian Master Shifu Michfood for sharing his unpack/ repack MTK boot/ recovery algorithm or this porting tool would not have exists & you will have do all this on a NIX box . . . :laugh:
recovery.fstab for MT65xx
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/bootimg /bootimg emmc defaults defaults
/dev/recovery /recovery emmc defaults defaults
/dev/uboot /uboot emmc defaults defaults
/[email protected] /system ext4 ro,noatime wait
/[email protected] /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait
/[email protected] /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer
# For MT6577
/devices/platform/mtk-sd.0/mmc_host/mmc0 auto auto defaults voldmanaged=sdcard0:[COLOR="blue"][B][SIZE="4"]6[/SIZE][/B][/COLOR]
/devices/platform/mtk-sd.1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto
Code:
# For MT65[B]xx[/B]
[COLOR="Blue"]/devices/platform/mtk-msdc.0/mmc_host/mmc0[/COLOR] auto auto defaults voldmanaged=sdcard0:[COLOR="blue"][B][SIZE="4"]6[/SIZE][/B][/COLOR]
[COLOR="blue"]/devices/platform/mtk-msdc.1/mmc_host/mmc1[/COLOR] auto auto defaults voldmanaged=sdcard1:auto
To identify your MTK voldmanaged path for sdcard -> adb shell find /sys -name mmc0. You don't need to include the first path /sys so it should start with /devices
To identify your internal sdcard partition no. -> adb shell cat /proc/dumchar_info & look at fat partition block /dev/block/mmcblk0p6 & update it accordingly . . .
Update it to fstab.${ro.hardware} too.
The correct way to check ${ro.hardware} -> adb shell getprop ro.hardware -> mt6577 then it should be rename to fstab.mt6577
------------------------------------------------
Updates - Built-in to porting tool
Some MTK don't use fat mount points for Internal sdcard then this tool will fail to identify it & ported PhilZ Touch will not boot/ bootloop . . .
Code:
/devices/platform/mtk-msdc.0/mmc_host/mmc0 auto auto defaults voldmanaged=sdcard0: [COLOR="Red"]<- Empty[/COLOR]
/devices/platform/mtk-msdc.1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto
Solution - Put a # at the beginning of that line or just delete it & it'll boot . . .
Code:
[B][SIZE="3"][COLOR="Blue"]#[/COLOR][/SIZE][/B]/devices/platform/mtk-msdc.0/mmc_host/mmc0 auto auto defaults voldmanaged=sdcard0: [COLOR="Red"]<- Empty[/COLOR]
/devices/platform/mtk-msdc.1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto
------------------------------------------------
To identify USB voldmanaged mount points for Internal SD -> adb shell su -c "ls -R" > c:\users\YOUR USER NAME\desktop\usb.txt
Look for anything usb in it & try it at the fstab.${ro.hardware} & also update it to recovery.fstab too. Both must be identical or it will not work.
An example below, confirmed by shoxxy that can be view at PhilZ Touch -> Install Zip but doesn't mount it at mount USB storage.
Code:
/devices/platform/mt_usb/usb1 auto auto defaults voldmanaged=usbdisk:auto
Also look for various example here on voldmanaged for USB storage & hopefully someone will get it working one day.
if yours is a /data/media device then it would not work . . .
Refer to here credits to RD chrmhoffmann
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:
When everything fails then try your hands on building one yourself with the optional build flags here for your MTK . . .

This is awesome man....

Yeah...Finally a support thread of philz touch for mediatek devices ...Great initiative by master @yuweng for bringing simple tool to install philz touch on many mediatek devices
Sent from my A250 using Tapatalk

Hi there. Does it work with the Jiayu G5S ?
Is there a simple guide?
Gesendet von meinem JY-G5S mit Tapatalk

Bro, everything is already stated clearly at post #1 to 5, make backup x3, double-click PhilZ.exe & follow on-screen instructions, that's the guide . . .

manual porting ?
SIR Thanks a lot for creating the tool :good:
BTW I tried on my mt6577 in both the ways but it says recovery.img is too large and it is aborting
my question is How to do manual porting for this recovery as we did for carliv touch recovery ( i tried to merge the A9,7z with my ramdisk but it didnt worked)
so pls assist me Sir :crying:

Updates - Built-in to porting tool
Temporary work around is to use the same technique at post #3 most bottom . . . When ask whether you have flipped screen, that is the time to delete the files. Binary files at Stock/recovery/rmdisk/sbin as listed below are safe to be deleted to save some space. List below starts with less critical to critical & i have absolutely no idea what will happened in the long run but definitely it'll boots.
Most of them are utilities for formatting the sdcard while at recovery. Try one at a time starting with Item 1, if still it complains about oversize then delete 1+2 , 1+2+3 & so on until it auto-install . . . :fingers-crossed:
Parted
sdparted
fb2png
mount.exfat
adbd
e2fsck & tune2fs
Updates
You can also try tinypng.com the tips from EnerJon to resize all images at Stock\recovery\rmdisk\res\images to a much smaller size that might just be enough for it to boot PhilZ Touch on your MTK . . . :fingers-crossed:
--------------------------------
Refer to updates of the updates here . . . :good:

hi Bro
thanks for sharing this TUT
but, i can't see download ling of Philz.exe
can give me Download Link ?
thanks ...

Little problem
Hi
First, thank you for porting Philz cwm recovery to our mediatek devices.
I have a zte blade q mini rooted with framaroot but when i want to use your tool, it says ro.secure=1 so no way to port recovery for me.
Any idea or workaround ?
Thank you
ladalgigi
---------- Post added at 02:59 PM ---------- Previous post was at 02:58 PM ----------
You have to go on the top of OP, you can see Discussion and Download tab...

Update info . . .
i3ooter said:
but, i can't see download ling of Philz.exe . . . can give me Download Link ?
Click to expand...
Click to collapse
ladalgigi said:
ro.secure=1 so no way to port recovery for me. Any idea or workaround ?
---------- Post added at 02:59 PM ---------- Previous post was at 02:58 PM ----------
You have to go on the top of OP, you can see Discussion and Download tab...
Click to expand...
Click to collapse
i donno why so many cannot see the Downloads, updated info here . . .
For ro.secure=1 solution is also at the same post & since you already gain root, refer to here . . . :good:
My experience is that you'll have to EXIT MTK Droid Tools first then start the PhilZ.exe or both will be conflicting using the adb shell at the same time . . .
Updates
To others facing the same problem & still you cannot make ro.secure=0 then follow the guide here on how to upload your boot.img & let MTK Droid Tools automatically make the boot.img to ro.secure=0 for you . . . :good: You can also let MTK Droid Tools automatically make & install CWM for you first then use PhilZ.exe to updates it to PhilZ Touch . . . :laugh:
WARNING
Be careful, wrong steps & you'll end up with a soft-brick MTK . . . Make a Factory ROM backup first, read & continue reading then only hands on !

Hi yuweng,
I have root shell right.
but the program says I need root shell.
what can I do?
see my attached file

Then i guess you have no choice but to upload your boot.img & make it ro.secure=0 then . . . :laugh: Or try the manual mode if you have your stock recovery.img with you . . . :fingers-crossed:

Hi !
I tried the manual mode an put my recovery.img in the right folder.
But it gets the same error.
How i can make my boot.img to ro.secure=0 ?

Hi all.
Now i have a Boot.img with ro.secure=0 (Thank you to hanuma)
Now i have the next Problem.
After installing, (Congratulation now you have PhilZ.... Boot into recovery? Yes or No)
And he cant't boot into the recovery.
Only Bootlogo.

Phil's CWM, supports MTK for some time now, i got some issues last time i checked (source built)
Can you please check, if the backup / Restore of boot.img / system are done correctly ?
Regards

Popey900 said:
And he cant't boot into the recovery.
Click to expand...
Click to collapse
In the past, users feedback the same for my other porting tool & then they manually installed it & it works . . . Ported recovery.img is at PhilZ folder.
If still it doesn't boot then upload your stock recovery.img here & i'll have a look at it . . . :fingers-crossed:
superdragonpt said:
Can you please check, if the backup / Restore of boot.img / system are done correctly ?
Click to expand...
Click to collapse
Hey, and i though you followed the news back at the CTR thread then you would've know this . . . :laugh:
CWM/ PhilZ Touch never boots on MTK since last year on the release of cm10.2 & cm11 b'cos we are not using fstab v2 . . .
And just got PhilZ Touch fully supported on MTK devices, Phil3759 just a few days ago announces retirement & releases all the close source to the world . . .

[Completed] Manually Swap External SD to Internal SD, 5.1.1 Lollipop After Root?

Alcatel OneTouch Elevate
Hardware : Qualcomm
Model : 5017B
Build number : Android L
Build date UTC : 20150725-065328
Android v : 5.1.1
file being modified: vold.fstab
code to be modified:
dev_mount sdcard /storage/sdcard1 auto /devices/msm_sdcc.2/mmc_host
#MTP
#dev_mount sdcard2 /mnt/sdcard/external_sd auto /devices/platform/msm_sdcc.3/mmc_host
Should I swap out the highlighted red text in each line, or perhaps it is another section of each line? Or is storage mount embedded in the ROM, which would require opening the ROM and editing it then repacking it (which no one can do right now, no means of backing up full ROM)?
Is it even possible to modify these lines in Lollipop 5.1.1 without bricking an Alcatel OT Elevate that's rooted? there is no recovery possible for this device at present. No custom ROMs, and no custom recovery to flash with. This phone is mysterious, has a hidden fastboot partition, looks like.

mU$!c said:
Alcatel OneTouch Elevate
Hardware : Qualcomm
Model : 5017B
Build number : Android L
Build date UTC : 20150725-065328
Android v : 5.1.1
file being modified: vold.fstab
code to be modified:
dev_mount sdcard /storage/sdcard1 auto /devices/msm_sdcc.2/mmc_host
#MTP
#dev_mount sdcard2 /mnt/sdcard/external_sd auto /devices/platform/msm_sdcc.3/mmc_host
Should I swap out the highlighted red text in each line, or perhaps it is another section of each line? Or is storage mount embedded in the ROM, which would require opening the ROM and editing it then repacking it (which no one can do right now, no means of backing up full ROM)?
Is it even possible to modify these lines in Lollipop 5.1.1 without bricking an Alcatel OT Elevate that's rooted? there is no recovery possible for this device at present. No custom ROMs, and no custom recovery to flash with. This phone is mysterious, has a hidden fastboot partition, looks like.
Click to expand...
Click to collapse
Hello,
Please try posting your query in Android Q&A Forum with all relevant details, the experts there maybe able to assist you.
Regards
Vatsal,
Forum Moderator.