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

Search This thread

AmINoS007

Senior Member
Apr 19, 2014
370
65
i have done all the steps with replacing recovery and res etc from CTR 2.5 to 2.5 and repacked succesfully
but when i nstall the recovey when the phone reboot i find its 2.4 CTR and not 2.5 .. what could be the mistake and any suggestions pls :confused:
 

Mahesh90901

Member
Sep 20, 2012
29
10
Vashi
Please tell me how can i fix the problem when i try to mount or enable touch it says Cant mount sd card my mobile does not have external sd card it used internal storage
 

dockers

Member
Nov 29, 2006
19
0
The buttons and points of touch are misaligned on Karbonn TA-FONE 37

The buttons and points of touch are misaligned on

Hardware : MT6577
Model : Karbonn TA-FONE A37
Build number : ALPS.JB.MP.V1.16
Display: 480*800


See the attached picture.
Any ideas to fix this?
 

Attachments

  • device-2014-08-06-110505.png
    device-2014-08-06-110505.png
    46.7 KB · Views: 216

dhampire

Senior Member
Jan 26, 2013
201
58
Thailand
Normal CWM

Master, Thank you for your great jobs.
Can you arrange this Carliv Touch Recovery for MediaTek devices to "make normal CWM" ?
If we do it, how to ? Please advice us.
 
Last edited:
  • Like
Reactions: yuweng

yuweng

Senior Member
Feb 5, 2012
1,172
4,221
Fyi, no DEV has worked on the latest CWM sources to make it compatible with MTKs & furthermore koush has left cm team . . .
ids_emoticon_wilted_zps9728bd64.gif


Why "make normal CWM" when CTR is PROVEN to be better for MTK devices . . . :cowboy:

If you want then use this but its not compatible for older devices as it uses the latest lun path for CWM . . .
 

grungemann

Senior Member
Dec 18, 2012
174
48
Alor Setar
Fyi, no DEV has worked on the latest CWM sources to make it compatible with MTKs & furthermore koush has left cm team . . .
ids_emoticon_wilted_zps9728bd64.gif


Why "make normal CWM" when CTR is PROVEN to be better for MTK devices . . . :cowboy:

If you want then use this but its not compatible for older devices as it uses the latest lun path for CWM . . .

My phone is running on 4.4.2. Can I build a carliv backup with it?
 

neodrift

Member
Jul 31, 2010
17
1
Can somebody please help me with this Flip Screen issue? Although everything works fine im having problem flashing rom, when i flash new rom its also Flip like my recovery. Attached is my recovery.
 

Attachments

  • recovery.img
    6 MB · Views: 34

KunalKene1797

Senior Member
Dec 4, 2013
435
1,042
24
Nagpur
Can somebody please help me with this Flip Screen issue? Although everything works fine im having problem flashing rom, when i flash new rom its also Flip like my recovery. Attached is my recovery.

Its not anyone's issue!:silly: the screen of your phone was put upside down and code in the ROM was used to make it straight...so what you can do is Compile the Recovery on your OWN! and Install the Stock ROM!:silly:
 
  • Like
Reactions: Jupp011

Q9Nap

Senior Member
Feb 13, 2009
1,019
1,890
I'll play with it but I'm more ROM side and have only been able to mount/extract the system image but not recovery. This is also my first time playing with MTK based devices so I'm having to get used to no fastboot and with a smartwatch that lacks volume buttons.

Which one? ;)
Right now I have an EC309 (MT6577) from Vapirius which they resell as the AX-2 Comet which the gave me for development. I am being shipped the TrueSmart Engineering Prototype (MT6572) as well as backing the TrueSmart Oct Dev Edition which will ship in December.

so how do you unpack system.img?

i successfully unpacked the mzf using mtk, but none of the tools that work for most moto system images work to extract the system image.

i've tried imgextractor, simg2img, and unyaffs2.

*edit*
as for unpacking/repacking boot.img and recovery.img, Android-Kitchen works great: https://github.com/dsixda/Android-Kitchen
 
Last edited:

yuweng

Senior Member
Feb 5, 2012
1,172
4,221
As mentioned here, MTK Motorola is the worse of all or shall i say the best of all at ensuring that it stays as stock ROM at all time, once you mod it then it'll brick & you have to use RSDLite to download back the original Factory ROM then only it'll boot . . . :cowboy:

i don't see the point for you to move forward unless you have found a way for custom recovery to work on your MTK Motorola . . . :cool:
Code:
adb shell su -c "tar -cf /mnt/sdcard1/system.ext4.tar /system"
OR
Code:
adb shell su -c "tar -cf /mnt/sdcard2/system.ext4.tar /system"

Refer to here onwards for MTK Motorola custom recovery progress . . . :cool:
 

Q9Nap

Senior Member
Feb 13, 2009
1,019
1,890
As mentioned here, MTK Motorola is the worse of all or shall i say the best of all at ensuring that it stays as stock ROM at all time, once you mod it then it'll brick & you have to use RSDLite to download back the original Factory ROM then only it'll boot . . . :cowboy:

i don't see the point for you to move forward unless you have found a way for custom recovery to work on your MTK Motorola . . . :cool:
Code:
adb shell su -c "tar -cf /mnt/sdcard1/system.ext4.tar /system"
OR
Code:
adb shell su -c "tar -cf /mnt/sdcard2/system.ext4.tar /system"

Refer to here onwards for MTK Motorola custom recovery progress . . . :cool:

Thanks for the reply! The above method requires having the device to pull the system; there are many ways to do that.
"adb pull system" is probably the easiest
You can also use the on-device make_ext4fs binary to make a nice sparsed system.img

I want to know how to dump the system.img created by opening the *.mzf file with mtk.
The recovery.fstab specifies that it is ext4, but linux will not mount it.
It is in some proprietary format I think, and different from other moto system.img files, because the standard extraction tools don't work...
 
Last edited:

yuweng

Senior Member
Feb 5, 2012
1,172
4,221
As mentioned & AFAICR, existing tools available doesn't work on MTK Motorola & nobody wants to work on it & nobody ever share the solutions . . . :rolleyes:
(fyi, i don't own a MTK Motorola yet i download RSDLite & tried porting recovery for it . . . )

If you have read the previous link, the progress stops at using SP Flash Tool instead of RSDLite . . .
 

derkvol

Member
Oct 5, 2008
30
2
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 !

Is it right in step2 CTRv.2.4 or must be CTRv2.5?
 

yuweng

Senior Member
Feb 5, 2012
1,172
4,221
its so obvious & still you don't get it . . . :cowboy:

Step 1 - Download compatible CTRv2.5 according to your MTK filesystems
Step 2 - Unpack Step 1 & copy out the res folder & recovery binary
Step 3 - Unpack the working CTRv2.4 that you ported earlier & follow below Step 3

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 !

 

derkvol

Member
Oct 5, 2008
30
2
its so obvious & still you don't get it . . . :cowboy:

Step 1 - Download compatible CTRv2.5 according to your MTK filesystems
Step 2 - Unpack Step 1 & copy out the res folder & recovery binary
Step 3 - Unpack the working CTRv2.4 that you ported earlier & follow below Step 3

I did it 2 days ago, but , i think, in step 2: line 2 and line 3 is wrong (must be CTRv2.5). It's mistake. Pls, change it for someone else:D
 
Last edited:

yuweng

Senior Member
Feb 5, 2012
1,172
4,221
There is absolutely no error, this shows that your English Reading and Writing skill definately got problem . . . :cowboy: i have already mentioned clearly at that post that i won't be making CTRv2.5 Porting Tool b'cos i can't keep up & its so easy for existing users to upgrade it themselves . . . :cool:

My advice for Non-native English speaker, pls read & continue reading it a few times then you'll understand or use google translate . . .

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 <- You are using CTRv2.4 Porting Tool to UnPack CTRv2.5 recovery.img
  2. Goto CTRv2.4\UnpackRepack\recovery\rmdisk & copy whole res folder out <- You are using CTRv2.4 Porting Tool here
  3. Goto CTRv2.4\UnpackRepack\recovery\rmdisk\sbin & copy the binary file named recovery out <- You are using CTRv2.4 Porting Tool here
 

bovirus

Senior Member
Oct 7, 2007
2,154
789
@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?
 

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: