How to manually port Carliv Touch Recovery for Mediatek KitKat
How to manually port Carliv Touch Recovery for Mediatek KitKat
21-02-2015, 02:14 PM
This guide will explain how to manually port Carliv touch recovery to a Mediatek (MTK) Android device.
Features ; Version 2.7 update (11-dec-2014)
- Rebuilt from base (cwm 6.0.3.7) and add improvements on top.
- Reintegrated bottom virtual navigation keys, to compensate the non-function of swipe in some phones
- Better compressed backups integration - pigz support from cm-11
- New "nvram backup/restore" menu functionality: the nvram partition will be backed up in clockworkmod/backup/.nvram/nvram-xxxxx folder as nvram.img. This will help if you lose IMEI and other communication features. It will work only if you have the nvram partition defined in recovery.fstab. If the nvram partition is damaged (as in flashing an oversized recovery) this will not help you, and you need SPFlashTools to reflash with format your phone official firmware, and after that flash this recovery, boot in recovery and restore nvram.
- The recovery has now an increased stability, many issues are solved
- The content of the backup folder will contain only what an usual clockworkmod backup contain, and that will make it easy to restore backups made with older versions.
- New GUI images, very light (the difference between non-touch modded cwm and this one is only 14 Kb, for 720x1280 resolution)
- Some other changes.
Requirement
- PC
- Download ALL phones Boot & Recovery repack Util for WINDOWS v2
- Stock Boot and Recovery images (see this guide for how to backup)
Procedure
1. Download Carliv Touch Recovery Image
For your screen resolution (to check your device's screen resolution, visit http://www.whatismyscreenresolution.com )
- Install ROM ToolBox Lite or any root browser
- Launch the root browser and navigate to /sys/devices/platform/mt_usb/ to determine your Lunfile path
- If you have a gadget folder directly inside the mt_usb folder then yours is old, download yours @ https://www.androidfilehost.com/?w=files&flid=22386
- If in the mt_usb folder, you have musb-hdrc.0/gadget instead then yours is new download yours @ https://www.androidfilehost.com/?w=files&flid=22387
2. Unpack the images
- Unpack the ALL phones Boot & Recovery repack Util for WINDOWS v2 zip file and open the folder. You should have a bin folder, MTK_pack, MTK_unpack, STD_pack and STD_unpack.
- Copy the phone's boot image, recovery image and the carliv touch recovery image downloaded into the above folder
- Drag the three images one at a time and drop them over MTK_unpack . The tool will automatically unpack them into folders
- You should now have three additional folders: boot image folder, recovery image folder and carliv recovery folder
3. Replace carliv kernel and kernel_header
- Open the boot image folder and copy kernel and kernel_header. Paste them into the carliv folder. When prompted,go ahead with replacing the existing files in the carliv folder
4. Edit Carliv recovery.fstab
- Using Notepad++, open recovery.fstab in the phone's recovery folder and also carliv folder (recovery.fstab is located in folder/rmdisk/etc)
- Recovery.fstab contains the mount points. Using the phone recovery.fstab as a guide , edit the carliv recovery.fstab so that its mount points correspond to that in the phone's recovery.fstab then save the modified carliv recovery.fstab
5. Edit carliv recovery fstab (could be named fstab.mt65xx)
- Using Notepad++ , open fstab in the boot image folder and also carliv folder (fstab is located in folder/rmdisk)
- Edit the content of the carliv fstab file so that it matches with that from the boot image fstab (you can get the correct mount points from phone's recovery.fstab) then save
6. Edit carliv default.prop
- Open both phone recovery and carliv's default.prop using Notepad++ (default.prop is located in folder/rmdisk)
- Replace the values for the following parameters in carliv's default.prop with the corresponding ones in the phone's default.prop
Code:ro.product.model ro.product.brand ro.product.name ro.product.device ro.product.board ro.product.manufacturer ro.build.product ro.product.platform ro.product.ota.model ro.cm.device
- Look for patterns like these and replace new with the appropriate values
Code:ro.build.display.id=cm_new-eng 4.4.4 KTU84Q 347d7427a4 test-keys ro.build.description=cm_new-eng 4.4.4 KTU84Q 347d7427a4 test-keys ro.build.fingerprint=mtk/cm_new/new:4.4.4/KTU84Q/347d7427a4:eng/test-keys ro.cm.version=11-20141209-UNOFFICIAL-new ro.modversion=11-20141209-UNOFFICIAL-new ro.cm.display.version=11-20141209-UNOFFICIAL-new
7. Edit carliv init.rc
- Using Notepad++, open the meta.init.rc, init.usb.rc and init.
- .ssd.rc in the boot ramdisk folder then init.rc in the carliv ramdisk folder
- Using the .rc files from the boot ramdisk folder as a guide, edit the following values in the init.rc file in the carliv ramdisk folder then save
- To get vendor and product id check init.usb.rc. in init.usb.rc , look for
xxxx is your idVendorCode:setprop sys.usb.vid xxxx
yyyy is your idProductCode:#5.mass_storage,adb write /sys/class/android_usb/android0/idProduct yyyy
- Edit the following values in the init.rc file in the carliv ramdisk folder then save
Code:export EXTERNAL_STORAGE /storage/sdcard0 export SECONDARY_STORAGE /storage/sdcard1 mkdir /mnt/media_rw/sdcard0 0700 media_rw media_rw mkdir /mnt/media_rw/sdcard1 0700 media_rw media_rw mkdir /storage/sdcard0 0700 root root mkdir /storage/sdcard1 0700 root root symlink /storage/sdcard0 /sdcard symlink /storage/sdcard0 /mnt/sdcard symlink /storage/sdcard1 /sdcard2 symlink /storage/sdcard1 /mnt/sdcard2 write /sys/class/android_usb/android0/idVendor 0BB4 write /sys/class/android_usb/android0/idProduct 0C03 write /sys/class/android_usb/android0/functions mass_storage,adb # virtual sdcard daemon running as media_rw (1023) service fuse_sdcard0 /system/bin/sdcard -u 1023 -g 1023 -w 1023 -d /mnt/media_rw/sdcard0 /storage/sdcard0 class late_start disabled # virtual sdcard daemon running as media_rw (1023) service fuse_sdcard1 /system/bin/sdcard -u 1023 -g 1023 -d /mnt/media_rw/sdcard1 /storage/sdcard1 class late_start disabled write /sys/class/android_usb/android0/idProduct 0C03 write /sys/class/android_usb/android0/functions mass_storage,adb write /sys/class/android_usb/android0/idProduct 0C01 write /sys/class/android_usb/android0/functions adb
8. Repack ported carliv
- Drag the modified carliv folder and drop over MTK_pack
- Once complete, you'll see a file named new_image. Thats your ported Carliv Touch recovery
Credits
Carliv, Bgcngm & Michfood
This post was last modified: 11-06-2018, 05:43 PM by hovatek.
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
17-10-2015, 09:17 PM
(17-10-2015, 05:22 PM)mboy13 Cnt port_CarlivTouch-recovery for my device resolution. 360x640. Any option
which device?
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
18-10-2015, 10:50 AM
(17-10-2015, 11:08 PM)mboy13 I mean to say i cnt find my fone resolution. hot note
use a resolution close to it
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
18-10-2015, 02:37 PM
(18-10-2015, 01:23 PM)mbo y13 So whick will suite?
port_CarlivTouch-recovery-2_7-320x480.img
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
19-10-2015, 09:57 AM
the screenshot attached, could it be an error of not successfully extracted?
This post was last modified: 19-10-2015, 10:17 AM by mboy13.
Attached Files
19-10-2015, 10:40 AM
This post was last modified: 19-10-2015, 10:48 AM by mboy13.
Attached Files
Users browsing this thread:
2 Guest(s)
2 Guest(s)
Users browsing this thread:
2 Guest(s)
2 Guest(s)
