yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] rebajz:
2.2. version...

if i go from CTR to aroma file manager, i cannot go for example to Menu, or select all button, etc. I can only swipe up and down.

Previous version 2.1 working correctly.

I use auto port option (Lenovo p780, 6589, 720x1280).

CTR working good. Error is only in aroma file manager.
[Miscellaneous Android Development] iZLeeP:
Thanks yuweng for the auto port tool. Manage to port CTR 2.2 to my Lenovo A60+ (MT6575).

One thing though, I used the Auto function and it did port automatically except for the part of rebooting to CTR recovery. Instead, it rebooted to the old CWM recovery. Nonetheless, I flashed the ported CTR image at Ported-CTR folder via mobileuncle and CTR recovery is working properly.
[Miscellaneous Android Development] Napst3r88:
Now my phone g-tide e77 MT6572 support ubifs .. What should I use ?? V 2.1 or v 2.2 sir
[Miscellaneous Android Development] bovirus:
Please read the first post before to post...

2.1 = UBIFS

2.2 = NON UBIFS
[Miscellaneous Android Development] BenDroid1:
Thanks but a little help

Thank you for considering us with the ubifs file system ...I have AN mtk6572 phone(my saga c3) if u know the phone....Its a ubifs so just to clarify how to use your porting tool. All i have to do is make sure the drivers for my phone are there and working , plug in my android device (4.2.2), run in admin,turn or pause antivirus, turn on usb debugging and be rooted ...right? ...thats all but what is this i hear about make sure your phone isnt ro secure something like that.....is that all? :) :) Oh ANd just a question too is there any way to either change the file system of my phone and is it possible to change your button combination to access recovery on your mtk device ..PLEASE HELP AND ANSWER ALL MY QUESTIONS PLEASE ><?/:D:cowboy::laugh: :rolleyes: :cyclops:
[Miscellaneous Android Development] :
Super working!

perfectly working on my MT6572! Thank you sooo much!
[Miscellaneous Android Development] wertzPH:
thanks for the tool sadly, my touchscreen down move to the selections. im still using volume keys and power to navigate.

capacitive touch button does move selection down, back button does what it should, go back last page. on aroma touch does work, and so are the menus on it i can activate.

MT6572 here, ext4
[Miscellaneous Android Development] htctouch2t3333:
alps gt-i9500 mtk6572

thank you for this tool -

autoport crt 2.1 for ubifs work good but the screen of recovery is up side down - is not a big problem but will be better with normal screen - there is something that i can do for it ?
[Miscellaneous Android Development] Napst3r88:
sir .. now i ported cwm to my mtk5672 with ext4 ... when it asked me ( do you have flipped pages) _ Yes

when it finished it transfer me to Mediafire link about 7mb recovery ... Now i will flash produced cwm with mobile uncle ...

any problem or that is ok ?

update

it is ok .. Now i have carliv touch recovery .. but with manual method not auto

thanks to you and sir.carliv
[Miscellaneous Android Development] genesisalgor:
I've tried all ways to port this recovery but can't, the auto-tool says my phone is not a Mediatek Device, so i can't use it. My phone is a Note 3 Clone, okay, but have MTK6589. And trying port manual with Carliv Tutorial all i can make is a phone freeze on Boot, sadly this recovery is amazing, but i can't hav it.
[Miscellaneous Android Development] bovirus:
Before to make any changes you should made a backup with MTKDroid.

Now if you don't have any backup you cannot do anything.
[Miscellaneous Android Development] genesisalgor:
I've already ported a CWM for my device, but it's 6.0.2.8 by Bruno using Michfood tool, made a complete backup with MTKDroid and a Nandroid Backup too, Also a backup of my CWM recovery and Stock. I can handle with these bricks on my phone. Also in my port of Carliv, the phone freeze when i try to go to recovery, but boot normally in a simple boot. I can say i have experience with MTKs but the port of CTR is being hard for my device. :(
[Miscellaneous Android Development] bovirus:
The discusiione about CTR here should be OT.

Please takje care that you are not alone about freeze of CTR recovery (but normally boot).

It's a known problem about CTR kit with many phones.

I'm using the standard CWM (5.5.0.4) created by MTKdroid.
[Miscellaneous Android Development] genesisalgor:
I'm just think i've done something wrong with the port, but you saying this makes sense.

If only my phone could use this tool, but accuse in to be not a Mediatek Device i can have sure.
[Miscellaneous Android Development] bovirus:
I tested CTR on five different hardware models of Mediatek phone. CTR worked fine (no errors).

But when I reboot the phones (with all 5 different hardware models) the recovey created by CTR didn't work (go in loop).

But teh phone booted normally in non recovery mode.
[Miscellaneous Android Development] yuweng:
As said, i've put in alot of error checking, sometimes it wouldn't work properly on some PC... :o Did you read the OP -> Notice to annoying n00bs & newbies...

If all five doesn't work then i can definitely say something is wrong with your PC, did you try it on other PC or laptops with different OS.... :cowboy:
[Miscellaneous Android Development] genesisalgor:
Thanks for the reply master yuweng, i've sucessful manually ported CTR now from the CTR Thread guide, everything working great now.
[Miscellaneous Android Development] bovirus:
[MENTION=4478781]yuweng[/MENTION]

I tested it on 4 different pc with different OS (Windows7 32bit/64bit - Windows 8.1 32/64bit).

Some pc is just installed. The issue is always the same.

CTR unpacked on root of C: drive. Adb driver instaleld and phone recognixed right.

I ran it, check different steps, no error.

But the recovery didn't work. Go in loop.

I tested also the trick of MTKDroid lave open. No changes.

I tested 5 differnt hardware Star phoen (with Mediatek chip)

But the phone boot up normally (not in recovery).

I used Master Shifu's Repack Utils to make changes to boot.img but generate a lot of error during unpack/repack (with stock file).

.
[Miscellaneous Android Development] yuweng:
​

As said many times & also mentioned at the OP, the porting tool uses Master Shifu Michfood Repack Utils & from Win7 onwards, MS has introduce permission & ownership so the porting tool or the Repack Utils won't work properly when UAC is enable & it must be executed at the Desktop to have the correct ownership with read/ write/ execute permission.... :cowboy:

So disable UAC & also your Anti-Virus too as many feedback that it also interfere with the porting process...

Reboot the PC, extract & execute the porting tool or the Repack Utils at your Windows Desktop then it'll work properly.... :cool:

-----------------------

Refer to this old youtube video by xda friend rnovino concept is the same... :good:

[YOUTUBE]thN2OXheByU[/YOUTUBE]
[Miscellaneous Android Development] bovirus:
The UAC is disabled on all W7/W8 pc's. Antivirus is not installed (fresh pc installation).

I will try to use CTR on Desktop

I tesetd the same tool on tw home pc (was teh first test) that has XP 32bit.

Same result (CTR didn't report error but the recovery.img file created didn't boot right).
[Miscellaneous Android Development] KopiJahe:
I've encountered the same problem in the past, but with qualcomm-based phone, in the end, I managed to boot it up by using another phone's kernel (and got the display upside-down :D )
[Miscellaneous Android Development] praderj:
Bro [MENTION=4478781]yuweng[/MENTION].. thanks for the tool.. I successfully ported like before and its working like a charm... your tool never showed error in my lap.. thank you master [MENTION=5186178]carliv[/MENTION] for such a wonderful recovery..
[Miscellaneous Android Development] johnny523:
error while portig to A269i

carliv's recovery ver 2.1 boots but touch screen doesn't work normally, I have to use the physical buttons to access the menus, this is ok but I got a bunch of errors, then I checked the recovery log and found out that the following errors occur:

can't open /dev/tty0: no such file or directory

.

.

.

w: unable to get recovery.fstab info for /datadata during fstab generation!

w: unable to get recovery.fstab info for /emmc during fstab generation!

w: unable to get recovery.fstab info for /external_sd during fstab generation!

and a bunch of other errors. I have tried to rebuild the recovery several times with same errors
[Miscellaneous Android Development] rnovino:
Carliv Finally Booted up!

I posted also a fix for some devices particularly MT6582 and MT6572 that are having bootloop like mine feel free to check it out here http://xdaforums.com/showpost.php?p=50934291&postcount=15 simply hit the thanks buttons if it helps :)

as always thanks to [MENTION=4478781]yuweng[/MENTION] [MENTION=5186178]carliv[/MENTION] [MENTION=5119815]rua1[/MENTION] and all the devs who always create great stuffs here :)
[Miscellaneous Android Development] bovirus:
Could the CTR author make directly theese changes to the CTR project?
[Miscellaneous Android Development] rnovino:
I think this will be optional just in case because not all MT65XX have this issues
[Miscellaneous Android Development] flufytendo:
Hi I use this tool to port a recovery. Works without touch, any idea?

Enviado desde mi H30-U10 mediante Tapatalk
[Miscellaneous Android Development] BHARDIK:
try to port it again, make sure you port it correctly :)
[Miscellaneous Android Development] dedi.stwn:
Are this work on lg g pro lite?
[Miscellaneous Android Development] KopiJahe:
LG may lock your bootloader, don't proceed unless you actually sure it doesn't or you unlocked it.
[Miscellaneous Android Development] dedi.stwn:
Mtk6577 have a bootloader?
[Miscellaneous Android Development] KopiJahe:
Every phone has a bootloader, wheter it unlocked or locked one.
[Miscellaneous Android Development] dedi.stwn:
Are u know to unlock bootlaoder lg g pro lite?
[Miscellaneous Android Development] joshatt:
Thanks so much!!! Works like a charm ----- on my Philips w736, android4.0.4, mtk6577A.

Only the manual of how to scroll/page down is hidden in that menu, a little tricky.
[Miscellaneous Android Development] CyberianIce:
Can somebody explain me what is C suffix in block size option for DD because i see no logic in using it and no description on man pages:

I heard only for following: w, b, k, M, G, ... but there is no "S" :/
[Miscellaneous Android Development] lopestom:
CTRv2.2 for BLU Life Play X - MT6589T

Thanks for master shifu [MENTION=4478781]yuweng[/MENTION] and [MENTION=5186178]carliv[/MENTION] for this CTRv2.2 - CWMv6.0.4.4.

Now my device BLU Life Play X - MT6589T have backup...:cool:

------------------------------

Update 30-03-14

After tests this okay.

CWMv6.0.4.4 v2.2 TOUCH for BLP X

Device with ROOT!! Use apk mobileuncletools to Recovery Update CWM (recovery.img).

Dowload: recoveryOriginal BLPx-lopestom.zip http://d-h.st/iRF

recoveryCTRv6.0.4.4v2.2-BLPx-lopestom.zip http://d-h.st/pjM

Or see: https://plus.google.com/115816992326284478418/posts/NSzh9RdtpLx
[Miscellaneous Android Development] iZLeeP:
Wrong thread buddy! Kindly post on your device's specific thread (or related if none).
[Miscellaneous Android Development] arnabgharay:
Gionee m2 ctr not working

sir, this is a awsm tool thanks for it , its working on old mtk6589 chipset fine , but my new gionee m2 which is based on mtk6582 , the porting method working fine , but the recovery is not booting up , plz help me sir :confused: , i try both method (auto and manual ) not working , i uploaded my file in dropbox
[Miscellaneous Android Development] abhinav2hd:
Help!!

[MENTION=4478781]yuweng[/MENTION] I have Ported CTR v2.2 for Hcl Y3 tab MT6575 which has Resolution of 1024*600. the problemis that touch Not Working Properly. It works As if Recovery is Portrait but Recovery is in Landscape. Getting Same Problem With COT and TWRP too, Please help Sir.
[Miscellaneous Android Development] iZLeeP:
Cool! [MENTION=4478781]yuweng[/MENTION] working on Philz Touch Recovery for porting to MTK devices. Gonna try porting the one on the OP.
[Miscellaneous Android Development] suhas.holla:
After Hours of Research ...Finally I fixed USB Mount storage option in Philz recovery by [MENTION=4478781]yuweng[/MENTION]

Credits to Master [MENTION=4478781]yuweng[/MENTION] for his base recovery.

.I have Added init.usb.rc file and add the line "import /init.usb.rc" in init.rc

i have not checked external sdcard as my device does not have it but internal storage works fine
[Miscellaneous Android Development] minahasa:
Hello, I'm struggling to find a compatible recovery for Indonesian release Mito A68 -a physical variant of Cherry Mobile Fuze & Micromax A96- It has MT6582 Quad-Core SoC (@1.3GHz) but with 512 Ram. Can you help? Thank You
[Miscellaneous Android Development] agismaniax:
I try to port your Cortex-A7 version. I unpack, replace the kernel, edit the recovery.fstab, delete some files from sbin, replace background and virtual_keys, compress some PNGs, repack and the result is still oversize (6558KB). :confused:
[Miscellaneous Android Development] yuweng:
if your recovery partition is 6291456 Byte AKA 6Mb then it won't work, as simply as that . . . :laugh:

Even awaaas is having problem resizing Philz Touch to his ZTE986 that comes with 7Mb recovery partition from the factory . . . :cowboy:

Unless you wanna revisit my 7Mb mod & you have been fore-warned by Master Shifu carliv about the consequences . . . :cool:
[Miscellaneous Android Development] KopiJahe:
Yes, in my previous build, it's bigger than 7 MB

But I don't know why, after sync-ing repo yesterday and build it, it become 6.9 MB

But I still prefer using TWRP :)

I'm now succeeded with building TWRP for several 6MB MTK devices (ZTE N986D and Hisense EG680) without placing res folder outside recovery.img anymore ;) (some newbies bootloop-ed their phone, and installed TWRP without ui.zip (res folder's content), so they even have bootloop in recovery mode :eek: but not anymore :D )
[Miscellaneous Android Development] superdragonpt:
I've built (from sources) the new TWRP for my ZTE v970...

Of course it doesn't fits my Recovery Partition...

BUT... since i've built my own kernel for this device, its easy to overcome this issue:

Compiled the zImage with LZMA compression... so the recovery was 7.xx Mb and now its 4.1x Mb :)

Fits just fine now....

So, what i want to say is:

IF you have your kernel sourcecode; Changing the kernel compression is your solution ;)

Also (since we are talking about recovery) you can also stripped down your kernel source (remove drivers; etc) not needed for recovery.

Hope it helps...

B.Regards
[Miscellaneous Android Development] yuweng:
Unfortunately, most MTK vendors doesn't provide kernel source & i'm a complete n00b at it . . . :o

i've seen at the TWRP thread that someone mentioned we can also use XZ compression too, supposedly to be better, idk . . .:D

Hmm, i've been wanting to ask & i've mentioned this i think at the porting thread, on SP_MDT there are only 5 camera selection & 7 LCD for my old MT6577 . . .

n00b Question

:o

if you include supposedly all source available for the above to your MT6577 kernel source then i could get mine booted up with the correct settings . . . :confused: :D

Why i think MediaTek not keen on releasing kernel source like HTC

Found this & they have the latest 4.4.2 on an old '09 product that was originally a Windows Phone . . . :eek: :laugh:
[Miscellaneous Android Development] btiu:
Help on MTK6517

Um hi,

I have an oddball MTK6517. It says it's a Kingwill P606. Running 2.3.5 Gingerbread, rooted. mtd system. i have gotten boot.img from mtd9 and recovery.img from mtd10. Now, I have setup adb to work on my zorin 8 lite(based on Lubuntu) so i tested it and it works. Adb can detect my phone and i can pull and push stuff.

I tried auto porting. First it says "you hav Soc..". Then it says that my phone is not mtk device. Maybe this happened because I haven't checked yet if my device's ro.secure=0 already. so I tried manual porting.

I tried manual porting, so I copied my stock recovery.img to Stock folder but it also says sorry this porting tool is for mtk devices only. Can someone tell me what could have went wrong with the manual porting?

PS I tried both CTR2.2 and CTR2.2 ubifs. Both did not work. My 3e recovery image is actually 10MB. weird. not sure if normal.

PSS Also when I use MTK droid tools, it says UNKNOWN ROM STRUCTURE. so that's probably one indicator, which I don't know how to solve yet. I also tried using MTK Droid tools (2 ways) to make cwmr, but both failed too.

Thanks in advance
[Miscellaneous Android Development] yuweng:
When you said MTK Droid Tools also said UNKNOWN ROM STRUCTURE then its confirmed it may not be a MTK device . . . :cool:

Try adb shell cat /proc/cpuinfo & see what the HARDWARE says . . . :cowboy:

Update

Hmm, it seems what oscarblue48 said is true . . . Refer to here & see the title thread . . . :D
[Miscellaneous Android Development] superdragonpt:
I Know, but this is Mediatek's fault, Mediatek CHARGES MONEY to give the sources to their Vendors, not to mention the NDA Agreements...

What Mediatek usually do is giving the kernel already pre-compiled to their Vendors (without the sources), if 1 Vendor request their own device kernel source (like WIKO) they have to PAY .

Just like you, my ZTE device NEVER had kernel sources.

So i started working on an Custom kernel for my device, using the available MT6577 known kernel sources:

- The sources ARE NOT the same on kernel common (/kernel) some have more MTK patches and /kernel patches than others

- You will need to work on your device Configs / ProjectConfigs and Drivers (And you may need to modify the drivers to work on your device)

--> i.e: My device uses GT818B touchScreen, BUT the available GT818B touchScreen drivers NEVER worked on my device, so it was modified (the calibration matrix) ...

- And there's an ton of other things you will need to work on / test , took me +6months to made it, and of course with some help from other guys (lingfude for example was the one that fixed the touchscreen driver... )

Yeah it should work also, XY haves an nice compression rate; but for my personal use and my device specifics i prefered the LZMA compression (about 33% LESS space).

AFAIK, MTK's Camera configs (on ProjectConfig.mk) is an big Headache...

Not only you need to config your camera, but also your image sensors/ backup lens/ sub-lens / etc, etc

And no, we can't just put all the MT6577 camera and sensors in one single project, and expect it to work ...

Regards ;)
[Miscellaneous Android Development] btiu:
rua1 maker of mtk droid tools confirms mine is a fake. Hahaha :) I will also try that proc/cpuinfo to see for myself

Thanks for the heads up yuweng! so even spreadtrum cpus take on the name of MTKs everywhere!! :P The person in the post you linked to, seems like we have same cpu but his is named differently LOL

here's cpuinfo.

free upload
[Miscellaneous Android Development] keanu_ritz:
hi , I've followed your instructions for philztouch recovery and got the recovery to boot on MMX A116 (MT6589).

but the problem is that it doesn't mount any sdcard (internal /external).

check the attached image

when i tried to take logcat it gives this error "/sbin/sh: exec: line 1: logcat: not found "
[Miscellaneous Android Development] yuweng:
i've just updated the OP yesterday, the mount USB storage is dependent on the fstab.${ro.hardware}

The correct way to check ${ro.hardware} -> adb shell getprop ro.hardware -> mt6589 then it should be rename to fstab.mt6589 not MT6589 . . . :o
[Miscellaneous Android Development] keanu_ritz:
My bad , didn't notice that!!

changed it and now it mounts both sdcards!!!!!!!!

Thanks master shifu [MENTION=4478781]yuweng[/MENTION]
[Miscellaneous Android Development] superdragonpt:
Also, there's been cases where if you unsecured the kernel ramdisk+remove the MTK debugger from init.rc PATH$ you will loose your USB connection from recovery.

So just use the stock ramdisk without modifications for testing USB purposes .

Regards
[Miscellaneous Android Development] yuweng:
Tested Philz on 3# MT6577 2# mine working fine, 1# friend's unit had this USB loose connection problem while copying a 420Mb ROM while at recovery . . . :cowboy:

While only my A789 has a working Aroma File Manager the other 2# need to add mkdir /tmp to init.rc then only it'll work . . .

As said at the OP, no extra sauce or spice added & if a certain function doesn't work then you'll have to figure it out yourself by trial & error . . . :laugh:

Philz Touch mount USB storage even works on my old MT6573 . . . :D

Update

For Philz Touch first boot testing, use the existing recovery.img 320x480 res as i've experience only this res will boot on my friend's unit . . . :cool:
[Miscellaneous Android Development] KopiJahe:
Just some info to whoever lost their IMEI due to flashing recovery larger than their partition size, there's a way to obtain your IMEI back, as long as you don't do anything else:

1. Search for secro.img / nodl_secro.bin for your phone (or use yuweng's universal one -no tested-)

2. Flash this partition in SP Flash Tool:

RECOVERY [COLOR="Blue"]-> use [B]stock recovery[/B][/COLOR]
SEC_RO [B][COLOR="Blue"]-> use secro.img / nodl_secro.bin[/COLOR][/B]

3. Go check your IMEI, if it still invalid, do a factory reset

Hopefully, your NVRAM partition still intact, if it corrupted or empty (for example, you formatted your phone in SP Flash Tool), it will not come back, except you have the backup.

Good luck ;)
[Miscellaneous Android Development] abhishek 9650:
will it install recovery to mtk6572

hi man

i am new to mtk platform and recovery

will it install a recovery on my spice mi-436 mtk 6572 device

i have bricked my phone 2 times .

plz do me a favor plz how to do it
[Miscellaneous Android Development] Sonic1SVK:
Ported to Xiaomi REDMI WCDMA (older revision Hongmi)

https://mega.co.nz/#!IoE1mZiZ!lb0t14_ndeRaGnCw6QcNesoYzlqZWIfyZfgxQaj2iig
[Miscellaneous Android Development] paulpax:
I have recovery.img

good day, i have managed to find a recovery.img for my device i-mobile Q2 duo which is the same as my Starmobile Astra which is MTK6577. Can you please REPACK this with TWRP and CMR recoveries please? I find the TUT hard to follow. Forgive me.
[Miscellaneous Android Development] wassgha:
Is there any method to install ClockworkMod recovery on HDC One X Clone (512 Gb of RAM, 4.5" Screen, MTK6577) Also PLEASE IF ANYBODY HAS THE SAME PHONE, PLEASE GIVE ME THE build.prop file for it, I need it very much.
[Miscellaneous Android Development] tm.bax:
hi

hi friend

yuweng i have mtk6575 (cpu) phone...

i want root and install recovery but i dont know use which link?:(

help me

i want rooting at first time...

than i want install recovery...

rooting 6573 in first page. working for me?

help me:(:(:(:(

please:(:(:(:(:(
[Miscellaneous Android Development] tm.bax:
rooted my phone

hi friend:fingers-crossed:

I rooted my phone with SuperOneClick v2.3.3 :good::good::good:

thanks a lot yuweng :good:
[Miscellaneous Android Development] fauntelroy:
can you add 320x480 resolution to TWRP?
[Miscellaneous Android Development] yuweng:
Huh, you mean there are still MT6575/ 77 with 320x480... :confused:

If 320x480 is available, i would have included it to the updated mod... :o

Unfortunately, i'm not good at compiling from kernel sources, only simple makefile...

However, you can take a look at here as Russian Master Shifu Javum spell out everything you need to know about compiling TWRP from sources... :good:

Use google chrome as its built-in translator makes more sense compare to others... :D

Good Luck...
[Miscellaneous Android Development] fauntelroy:
yes there are, the phone is lenovo a60+, mt6575 with 320x480 resolution

i'm no good with compiling either, hope you can help me, i have hard time with this device