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

[AmINoS007]

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

 

[Mahesh90901]

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

 

[syon.piyush]

Spice mi-436 strange problem

GO TO THIS LINK TO SEE MY PROBLEM
http://forum.xda-developers.com/general/help/help-spice-mi-436-boot-loops-t2838098

 

[dockers]

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?

 

[dhampire]

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.

 

[yuweng]

Fyi, no DEV has worked on the latest CWM sources to make it compatible with MTKs & furthermore koush has left cm team . . .

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

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

 

[grungemann]

Fyi, no DEV has worked on the latest CWM sources to make it compatible with MTKs & furthermore koush has left cm team . . .

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

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?

 

[m0han]

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

if you meant carliv recovery backup, ctr is for "devices with kernels up to Android 4.3. It won't work for kitkat." more here in large red letters.

 

[neodrift]

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.

 

[KunalKene1797]

<<<RECOVERY PARTITION IS ONLY 6MB HEAD OVER HERE >>>​

MT6572​

http://forum.xda-developers.com/showpost.php?p=55160827&postcount=100

 

[KunalKene1797]

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:

 

[Q9Nap]

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

 

[yuweng]

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 . . .

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 . . .

adb shell su -c "tar -cf /mnt/sdcard1/system.ext4.tar /system"

OR

adb shell su -c "tar -cf /mnt/sdcard2/system.ext4.tar /system"

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

 

[Q9Nap]

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 . . .

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 . . .

adb shell su -c "tar -cf /mnt/sdcard1/system.ext4.tar /system"

OR

adb shell su -c "tar -cf /mnt/sdcard2/system.ext4.tar /system"

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

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...

 

[yuweng]

As mentioned & AFAICR, existing tools available doesn't work on MTK Motorola & nobody wants to work on it & nobody ever share the solutions . . .
(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]

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
   

   /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]

its so obvious & still you don't get it . . .

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
   

   /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]

its so obvious & still you don't get it . . .

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

 

[yuweng]

There is absolutely no error, this shows that your English Reading and Writing skill definately got problem . . . 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 . . .

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]

@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?