[PORT] [TOOL] Carliv Touch Recovery for MediaTek devices

Search This thread

yuweng

Senior Member
Feb 5, 2012
1,172
4,221
@yuwen

I experimented some problems using Carliv tools and your TWRP tool in some pc's (of my friends) with different configuration (Windows7/Windows8/XP) with different antivirus (AVG, Avira, Avast, etc -always disabled).

No error but the recovery didn't work (didn't start).

On other pc with the same software it worked fine (my pc).
It's too complicate make a proof test to understand wht was happend.

For this I asked if it's possible to have the instruction how to port manually TWRP on mediatek device.

Carliv made a detailed Guide how merge his archive of recovery wiyth specific device recovery.

Could you do that?
Bro, in spite of me explaining it here & here & now you come to this thread asking for the same thing, this is Auto-Port CTR thread NOT manual-port TWRP . . .
ids_emoticon_wilted_zps9728bd64.gif


You have problems with manual porting try discussion thread here or here . . .

Since you didn't get the message, i'm going to speak very frankly to you now, it tooks me almost two years to learn all about the three generations of MTK SoC, each of the porting tool consist of close to 3000 lines of codes which is automating the manual porting process, now why do i need to share what i learn from scratch, nobody teach me all these, all self-taught, nights after nights of codings the software, experience gain from trial & error, trouble-shooting, reading & continue reading threads here at XDA & elsewhere, learn to compile recovery from source, i have to compile six times with all the optional build flags to make TWRP porting tool & fyi, i pm'ed more than eight DEVs asking for advice compiling from source, guess what only my Master Shifu Carliv guided me all the way & fyi, the Thanks meter that you see now, almost half of it is from him, i should be thanking him but instead he thank me back . . .

Now as mentioned previously, there are too many things & its too complicated to explain, learn to compile TWRP look at the source code then you'll know how it works & thats all the pointers that i can give to you . . .

If you have trouble setting up the BE then refer to this thread . . .

Good Luck . . . :cool:
 

bovirus

Senior Member
Oct 7, 2007
2,154
789
@yuwen+
Sorry for the mistake. I believe to be in your thread (TWRP installer).
I believe that is enough that who compile an old version of TWRP for a device post the Boadconfig.
 

iZLeeP

Senior Member
Jan 23, 2014
528
151
Manila
@yuweng

You said here
Master Shifu Carliv guided me all the way
shouldn't you be doing the same to others? It's true that you have shared all these applications, instructions and information to simplify the processes esp. for users who don't even bother to read and understand what they're reading. But there are things that just won't work no matter what they do. You can debunk me if I say that most users here in XDA do not have a linux machine nor can they run linux on a virtual machine, much more understand what the source code is. More so, that users are your average individual who know nothing of programming (or anything related to it) and only wants to improve their android experience. So they're only option is to do it the manual way just like Carliv mentioned.

Furthermore,
reading & continue reading threads here at XDA & elsewhere
if these threads were not started by their respective OPs, would you be able to make those awesome stuff that you post? The OPs shared their knowledge knowing that many would benefit from it. This is XDA my friend, a place of learning and sharing the knowledge you gained. Isn't that the meaning behind what open source is?

Just a thought. Peace brother!
 

yuweng

Senior Member
Feb 5, 2012
1,172
4,221
its a figure of speech, most of the things i learn it on my own. The short & simple answer is stay away & use the phone as it is as what Carliv has said here . . .

Threads that i started are Auto-Port if they can't get my tools to work then they are most welcome to ask . . .

Manual-porting is completely off-topic, it has absolutely nothing to do with my tools . . .

Talking about contributions, here are my contributions back to the XDA community, what have your good self done so far . . .

Now i tell you No offence, Bro does that make you feel any better, of course not !

So pls re-evaluate yourself first before making such remarks or are you in the position to make such remarks !

You can always get me on pm if you're not happy with what i'm doing, this type of public bashing is totally unexceptable . . .
 
Last edited:

bluefirebird

Senior Member
Mar 23, 2013
1,027
5,029
carliv.eu
I know this is not my thread, but as my friend Yuweng said, things are getting out of the way. So, first read the word "PORT" or "PORTING" in title. It's not about compiling. And this very thread is for my friend's amazing tool for automate porting. He spent many hours to develop it and has wrote everything you need to use it. The main problem here and on my threads is that people don't want to or they can't read. As you all can see, there are only few users that can't get it and keep asking again and again same questions. XDA is not a college or a school. Yes it's a place to learn, but learn by yourself: there are no teachers here. The help that we offer here is the same help we get from other experienced users and developers: a hint, a link or just "you should read deeper, the answer is there". Everyone has to do the work by himself, nobody is at anyone disposal or service. We wrote all needed info in our threads, and the proof is the huge number of people who use these things and get a successfull result. Of course the majority of them didn't botter to hit that thanks button or to make a donation, but if you are looking over the internet you can see hundred of Carliv Touch Recovery ports, and most of them are made with Yuweng's tool.

@yuwen+
Sorry for the mistake. I believe to be in your thread (TWRP installer).
I believe that is enough that who compile an old version of TWRP for a device post the Boadconfig.

If you look on device folders on github, in my account or other people account you can find that Boardconfig file.

@yuweng

You said here shouldn't you be doing the same to others? It's true that you have shared all these applications, instructions and information to simplify the processes esp. for users who don't even bother to read and understand what they're reading. But there are things that just won't work no matter what they do. You can debunk me if I say that most users here in XDA do not have a linux machine nor can they run linux on a virtual machine, much more understand what the source code is. More so, that users are your average individual who know nothing of programming (or anything related to it) and only wants to improve their android experience. So they're only option is to do it the manual way just like Carliv mentioned.
Furthermore, if these threads were not started by their respective OPs, would you be able to make those awesome stuff that you post? The OPs shared their knowledge knowing that many would benefit from it. This is XDA my friend, a place of learning and sharing the knowledge you gained. Isn't that the meaning behind what open source is?

Just a thought. Peace brother!

I think you was a little bit harsh. I respect you because you are one of a few people who respect other's work, but here you are not right. What I did show to Yuweng was something that he couldn't find somewhere else and that only after he has searched for that unsuccessfull. There are few minor things that you can find only by yourself if you try enough. But he learned to set up a BE and to use a linux distro by himself, and not only from XDA. That was what I did also, but for me it was a little bit easier because I've had previous experience in coding in php and javascript.
If someone wants to learn to build something in linux there are plenty of guides here on xda and in other places all over the internet. Of course that needs hard work and many hours from day to day time. Nobody can't make a magical thing, that you install on a computer, make few clicks and tada: you are a developer!

Now, I think it's time to close this discussion here. Everything a user needs to know is there in OP, and in few other posts. Use them wisely and you will get the result.
 

iZLeeP

Senior Member
Jan 23, 2014
528
151
Manila
I meant no disrespect with my post. It was just my point of view. If it was offensive, then my bad. You may report me to moderators and I'll gladly accept any punishment they mete out.

One thing to clarify, I'm no developer nor do I know have any knowledge about programming. That's why I don't have any contributions whatsoever. As a long time Apple user, Android is something that brings delight with all the customizations that you could do to it.

In any case, do forgive this fool if my criticism was harsh.
 
  • Like
Reactions: yuweng

m3ni

Senior Member
Aug 11, 2013
58
16
m3ni.ir
hello y2yu,

Glad you find it informative... :D

According to this site, there will be another 2 new cpu after MT6575/ MT6577... (use google chrome for translation)

This means MT6573 is 5 generation behind MT6588 & it is still unexploit with all info/ tools scattered all over the web...

Thats where i decided to compile all these info & put it here... :good:

Now that i check, i've bought my first mediatek back in 2008...( never knew it until i check it just now ) :silly: It has serve me well for almost 2 years in spite of dropping, a few times from 8 feet height when i was on a ladder & it still works ! It was the last drop that spoilt the mic & render it unuseful. It can still make & receive call to date but the other side can't hear what i say... :eek:

At that time, made in china phone was famous for its extra loud speaker/ ringtone but doesn't support android back then...

haha, enough of history, have you manage to port CWMR to your MT6573 ? In fact, i have manage to create a plugin for dsixda's Android Kitchen which can port CWMR to any MT6573 with a few copy & paste features just like Android Kitchen... :good:

Still testing it, may be you would like to be the first beta tester... :confused:

dude u have android in that phone? :eek: i had one of those... it didn't even had java |:
 

mi-425

Senior Member
Jun 25, 2012
216
24
Please guide me which ctr version is suitable for this device.....required cwm recovery.....
07b9b83f098782f3cc3219e56ab3be65.jpg


Sent from my iball4.5d Quadro
 

bovirus

Senior Member
Oct 7, 2007
2,154
789
Please dodn't ask a guide.
Please read instead carefully the first posts. You have here all info.
 

AlexZap

Senior Member
Feb 15, 2014
477
319
Waterbury
Please guide me which ctr version is suitable for this device.....required cwm recovery.....
07b9b83f098782f3cc3219e56ab3be65.jpg


Sent from my iball4.5d Quadro

Your device says alps.kk1.whatever.... this means that your phone runs kitkat and has been previously discussed all over the thread, ctr is not suitable. It may work in some instances, but it is based off of jellybean source, and shouldn't be used with kitkat devices. Try the twrp auto port tool instead.

Sent from my KFTHWI using XDA Premium 4 mobile app
 
  • Like
Reactions: yuweng and mi-425

yuweng

Senior Member
Feb 5, 2012
1,172
4,221

sudhansu7

Member
Oct 12, 2014
48
39
cuttack
great work...but 2.5 has some bugs...i have ubifs device ,mt6572...restore is not working...cant mout ubi system 0....but 2.2 works fine...
 
  • Like
Reactions: yuweng

raveeshwadhawan

Senior Member
Dec 9, 2014
71
42
faridabad
Old Tool
Added on Mar 05, 2014
Updated CTR v2.2 for MTK devices with ubifs ONLY
And Thanks to dhinesh77 for countless beta-testing & most importantly, Master Shifu carliv for looking into those ubifs source code to make it work on MTK devices....
salute_zps09342dc6.gif


Download link here...

Solution to cannot see whole sdcard is here by Master Shifu himself, it is actually a new feature/ function... :laugh:
----------------------------------------------------------
Added on Jan 27, 2014
Updated CTR v2.2 Recovery for MT6575,15, 77, 17, 89, 82, 88, 92
MT6572 (ext4 only, ubifs not supported)


Pls support by donation or at least drop your thanks here to encourage Master Shifu for further development...
rclxms_zps452ba9d3.gif


Download link here

----------------------------------------------------------
Added on June 02, 2014
New Porting Tool CTRv-1.4 for ext4 devices ONLY. . .

Known problems : Touch not working on some MTK devices . . . :cowboy:

Any bugs report here . . . :cool:
----------------------------------------------------------
Added on June 10, 2014
New AIO Porting Tool Easy Magic CTR v2.4 Installer for MTK for ALL MTK Cortex-A9/ A7 devices ONLY with either mtd, emmc, ubifs or custpack partition . . . :cowboy:

Any bugs report here . . . :cool:

Updates
Thanks to surfturtle for reporting . . . :eek:

Workaround : Use Manual mode & select 720x1024 that is the screen res for 720x1280 . . .

This is an AIO porting tool so go ahead & try the differrent res at Manual mode, the unpack/ repack feature, play around with it & you'll learn what is needed for porting custom recoveries . . . :cool:
----------------------------------------------------------
Added on June 17, 2014
Users using XP & 720x1280 MTK devices use this fix . . . :eek:
----------------------------------------------------------
Added on July 01, 2014
CTRv2.5 refer to here . . . :cowboy:
----------------------------------------------------------
Notice to annoying n00bs & newbies

Most of your questions are already answered on this thread so pls read it...
alamak_zps2e31ed77.gif


1) Either your MTK is still ro.secure=1 then use this method here then EXIT/ CLOSE it first then re-start the porting tool...

2) i've already put in alot of error checking to make sure this porting tool works, either the Auto or Manual port, it will leave behind Ported-CTR folder then manually install it via SPFT when it fail to auto install.... Most probably why it fail to install is b'cos you use SuperSu did you bother to look at your MTK device & grant access to Root Shell... There has been cases where the stock recovery is already corrupted then this tool will also port a corrupted CTR too. Re-install your stock 3e recovery.img & make sure you can boot into it then only use the porting tool again or just use the manual port... The differences is Auto will upload whatever recovery already at your device be it older CWM or TWRP & it will repack it with CTR ramdisk. While Manual will use whatever at your stock 3e -> factory_init.project.rc, meta_init.modem.rc, ueventd.rc & etc... Refer to this by Master Shifu carliv... :good: This tool has no log b'cos it is actually a simple copy & paste program, thats what it actually do.... :laugh:

3) Pls bear in mind that this porting tool has been downloaded by many & confirmed working BUT i can't guarantee that it will work flawlessly on your MTK device so continue trying & report back the solution if you found one... :cowboy:

4) This has been mentioned many times on this thread, if you really can't get it to work then don't just say your porting tool doesn't work...
alamak_zps2e31ed77.gif


Instead list out everything then it'll be easier to trouble-shoot
a) What OS you are using on the PC & your MTK...
b) Did you disable UAC & Anti-Virus on your PC
c) Did you execute the porting tool at C:\ drive if you're using XP else then at your Desktop READ what the porting tool says & it will ask you to wait then wait for it to continue without pressing the OK button...

As said many times, this porting tool uses Russian Master Shifu Michfood Repack Utils Huge Credits to him, it is actually DOS program with cygwin dll working at the back so all DOS limitation still applies such as it will ONLY operate properly when it is executed at the Desktop on latest OS... Tested working on XP to 8.1

As much info as possible then it'll be easy to identify where it goes wrong & did you bother to read 5 to 10 pages from the back then you would have know what is the latest story... :rolleyes:

Last but not least, i didn't compile CTR so any features not working / bugs found pls report it here BUT again, read the whole thread first as most already answered at that thread...

Q&A

1) Touch not working, refer to here...
2) MTK Alcatel devices refer to here & here... Supported on CTRv2.4
3) All MTK devices supported except this...
4) Inverted screen solutions -> Compile your own
5) CTRv2.5

i am in shock that a big platform xda cannot give a single example for porting or compiling recover for qualcomm snapdragon
 

bovirus

Senior Member
Oct 7, 2007
2,154
789
x raveeshwadhawan
Please remove the quote of first post. It's completly unseful.
Please post just your comment.
If you read carefully the first posts you have the instrcution how to porting the recovery for your device.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 262
    Old Tool
    Added on Mar 05, 2014
    Updated CTR v2.2 for MTK devices with ubifs ONLY
    And Thanks to dhinesh77 for countless beta-testing & most importantly, Master Shifu carliv for looking into those ubifs source code to make it work on MTK devices....
    salute_zps09342dc6.gif


    Download link here...

    Solution to cannot see whole sdcard is here by Master Shifu himself, it is actually a new feature/ function... :laugh:
    ----------------------------------------------------------
    Added on Jan 27, 2014
    Updated CTR v2.2 Recovery for MT6575,15, 77, 17, 89, 82, 88, 92
    MT6572 (ext4 only, ubifs not supported)


    Pls support by donation or at least drop your thanks here to encourage Master Shifu for further development...
    rclxms_zps452ba9d3.gif


    Download link here

    ----------------------------------------------------------
    Added on June 02, 2014
    New Porting Tool CTRv-1.4 for ext4 devices ONLY. . .

    Known problems : Touch not working on some MTK devices . . . :cowboy:

    Any bugs report here . . . :cool:
    ----------------------------------------------------------
    Added on June 10, 2014
    New AIO Porting Tool Easy Magic CTR v2.4 Installer for MTK for ALL MTK Cortex-A9/ A7 devices ONLY with either mtd, emmc, ubifs or custpack partition . . . :cowboy:

    Any bugs report here . . . :cool:

    Updates
    Thanks to surfturtle for reporting . . . :eek:

    Workaround : Use Manual mode & select 720x1024 that is the screen res for 720x1280 . . .

    This is an AIO porting tool so go ahead & try the differrent res at Manual mode, the unpack/ repack feature, play around with it & you'll learn what is needed for porting custom recoveries . . . :cool:
    ----------------------------------------------------------
    Added on June 17, 2014
    Users using XP & 720x1280 MTK devices use this fix . . . :eek:
    ----------------------------------------------------------
    Added on July 01, 2014
    CTRv2.5 refer to here . . . :cowboy:
    ----------------------------------------------------------
    Notice to annoying n00bs & newbies

    Most of your questions are already answered on this thread so pls read it...
    alamak_zps2e31ed77.gif


    1) Either your MTK is still ro.secure=1 then use this method here then EXIT/ CLOSE it first then re-start the porting tool...

    2) i've already put in alot of error checking to make sure this porting tool works, either the Auto or Manual port, it will leave behind Ported-CTR folder then manually install it via SPFT when it fail to auto install.... Most probably why it fail to install is b'cos you use SuperSu did you bother to look at your MTK device & grant access to Root Shell... There has been cases where the stock recovery is already corrupted then this tool will also port a corrupted CTR too. Re-install your stock 3e recovery.img & make sure you can boot into it then only use the porting tool again or just use the manual port... The differences is Auto will upload whatever recovery already at your device be it older CWM or TWRP & it will repack it with CTR ramdisk. While Manual will use whatever at your stock 3e -> factory_init.project.rc, meta_init.modem.rc, ueventd.rc & etc... Refer to this by Master Shifu carliv... :good: This tool has no log b'cos it is actually a simple copy & paste program, thats what it actually do.... :laugh:

    3) Pls bear in mind that this porting tool has been downloaded by many & confirmed working BUT i can't guarantee that it will work flawlessly on your MTK device so continue trying & report back the solution if you found one... :cowboy:

    4) This has been mentioned many times on this thread, if you really can't get it to work then don't just say your porting tool doesn't work...
    alamak_zps2e31ed77.gif


    Instead list out everything then it'll be easier to trouble-shoot
    a) What OS you are using on the PC & your MTK...
    b) Did you disable UAC & Anti-Virus on your PC
    c) Did you execute the porting tool at C:\ drive if you're using XP else then at your Desktop READ what the porting tool says & it will ask you to wait then wait for it to continue without pressing the OK button...

    As said many times, this porting tool uses Russian Master Shifu Michfood Repack Utils Huge Credits to him, it is actually DOS program with cygwin dll working at the back so all DOS limitation still applies such as it will ONLY operate properly when it is executed at the Desktop on latest OS... Tested working on XP to 8.1

    As much info as possible then it'll be easy to identify where it goes wrong & did you bother to read 5 to 10 pages from the back then you would have know what is the latest story... :rolleyes:

    Last but not least, i didn't compile CTR so any features not working / bugs found pls report it here BUT again, read the whole thread first as most already answered at that thread...

    Q&A

    1) Touch not working, refer to here...
    2) MTK Alcatel devices refer to here & here... Supported on CTRv2.4
    3) All MTK devices supported except this...
    4) Inverted screen solutions -> Compile your own
    5) CTRv2.5
    24
    Guys, i can't keep up with all the different porting tools i've made, pls DIY if you want CTRv2.5. . .

    The porting tool has everything & already given you all the info you need . . .

    Step 1
    • If yours is emmc/ mtd refer to here & download your device res
    • If yours is custpack refer to here & download your device res
    • If yours is ubifs refer to here & download your device res

    Step 2
    1. Use the Unpack/ Repack recovery.img -> Unpack recovery.img, copy downloaded CTRv2.5 Eg: port_CarlivTouch-recovery-2_5-480x854.img & rename it to recovery.img & press OK
    2. Goto CTRv2.4\UnpackRepack\recovery\rmdisk & copy whole res folder out
    3. Goto CTRv2.4\UnpackRepack\recovery\rmdisk\sbin & copy the binary file named recovery out

    Step 3
    1. Use the Unpack/ Repack recovery.img -> Unpack recovery.img again to unpack the earlier working CTRv2.4 recovery.img for your device
    2. Delete res folder & replace it with res from CTRv2.5
    3. Replace recovery from CTRv2.5 to sbin
    4. Manual edit CTRv2.4\UnpackRepack\recovery\rmdisk\etc\recovery.fstab with Notepad++ & add the below accordingly
      Code:
      /boot        emmc    /dev/bootimg
      /recovery    emmc    /dev/recovery
      /uboot       emmc    /dev/uboot
      /nvram       [COLOR="red"]emmc[/COLOR]    /dev/nvram[COLOR="Red"] <- Add this new line[/COLOR]
      
      [B][COLOR="Blue"]OR[/COLOR][/B]
      
      /nvram       [COLOR="Red"]mtd[/COLOR]      nvram
    5. Use the Repack recovery.img & let it auto-install the new CTRv2.5 to your device, thats it !

    14
    Yo, Bala bro, been quite busy with work, until now only manage to finish this tut... :eek:

    Yeah, i was thinking about that too, to mod dsixda's android kitchen just for MT6573 platform that includes Bruno Martins's unpack/ repack boot.img, unpack/ repack recovery & port it to CWMR like this tut, replace a2sd with data2ext or ad2sdx; only this two mod stable on MT6573 platform so far that i have tested...

    actually did try but give up half way as my scripting skill is still at novice level... :eek:

    did read it on some other forum that someone is actually doing that too but i never see it got release though...:p

    Well i guess we need dsixda expertise to be able to do that but he is retired now...
    ids_emoticon_wilted.gif


    Added on Sept 04, 2012 Info Update
    Dark Tremor's a2sd/ Apps2sd works well on MT6573 platform after all... :eek:

    i was using the last version 2.7.5.3 Beta 04 all this while & i always use a2sd datasd all the time & it FC all apps after a few weeks of using/ sometimes a few days even after a fresh install...

    After all, DT_a2sd/ apps2sd is actually apps to sd & i always push it as data2sd... :eek:

    Only until recently that i play with Android Kitchen, use it to extract my system.img & update it with its built-in Darktremor Apps2SD version 2.7.5.2, it works extremely well because 2.7.5.2 doesn't support a2sd datasd feature...

    So guys, if you are using DT_a2sd beta 4, don't use the command a2sd data2sd instead use a2sd cachesd...

    You can checkout my other post here
    12
    Okay, here's CWM recovery v6.0.2.8 (ramdisk only) for anyone that wants to port it to MT65xx based devices. Please note that this ramdisk contains my Huawei U8836D specific files and properties, but it should at least be portable for the majority of MT6577 phones out there. Important note is that init.usb.rc (only needed for MT6577 devices) is device specific and while porting the original must be taken from stock boot.img.

    Other than that, nandroid backup is fully working for devices with eMMC partitions, unlike other recoveries that get stuck while backing up boot partition.

    Happy porting (and don't forget to hit "Thanks" button)! :D
    11
    hello y2yu,

    Glad you find it informative... :D

    According to this site, there will be another 2 new cpu after MT6575/ MT6577... (use google chrome for translation)

    This means MT6573 is 5 generation behind MT6588 & it is still unexploit with all info/ tools scattered all over the web...

    Thats where i decided to compile all these info & put it here... :good:

    Now that i check, i've bought my first mediatek back in 2008...( never knew it until i check it just now ) :silly: It has serve me well for almost 2 years in spite of dropping, a few times from 8 feet height when i was on a ladder & it still works ! It was the last drop that spoilt the mic & render it unuseful. It can still make & receive call to date but the other side can't hear what i say... :eek:

    At that time, made in china phone was famous for its extra loud speaker/ ringtone but doesn't support android back then...

    haha, enough of history, have you manage to port CWMR to your MT6573 ? In fact, i have manage to create a plugin for dsixda's Android Kitchen which can port CWMR to any MT6573 with a few copy & paste features just like Android Kitchen... :good:

    Still testing it, may be you would like to be the first beta tester... :confused: