FORUMS
Remove All Ads from XDA

[Q&A] [PORT] [TOOL] Carliv Touch Recovery for MediaTek devices

n/a posts
Thanks Meter: 0
 
By QA Bot, Guest on 20th November 2014, 09:37 PM
Post Reply Email Thread
Q&A for [PORT] [TOOL] Carliv Touch Recovery for MediaTek devices

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [PORT] [TOOL] Carliv Touch Recovery for MediaTek devices. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy!
 
 
20th November 2014, 09:37 PM |#2  
Member
Thanks Meter: 3
 
More
i have a mt6582 4.4.2 kitkat with build ALPS.KK1.MP1.v2.10 kernel HTSVR8 #1 v3.4.67 (busybox checker app tells something about kot49h).
my question is. can i use this tool to flash custom recovery for my device. i already bricked it . once and i dont have a functional recovery image on this device
i searched a bit in this thread nothing found.
4th March 2015, 06:30 PM |#3  
Junior Member
Thanks Meter: 0
 
More
Yeah it worked for my qmobile a34 ubifs :)
May god bless you all who have made this cwm or ctr whatever it is
love u guys , thankyou alot ! yeah i mean it
bty did it manually by puting stock recovery as told by ctr v2.2 :P
17th March 2015, 05:27 PM |#4  
Junior Member
Thanks Meter: 0
 
More
Recovery not functional for MTK8127 and Mali450
Hi @carliv; @yuweng; @r0c0; @FeyoMx
I have the Cube U25GT C4W with MTK8127 Quad Core processor and Mali-450.
I tried to flash different recovery with negative results for all of them, none is 100% functional for this tablet. (The tablet does not have physical volume keys)
Yesterday, on the recommendation @FeyoMx, I pass through here and tried to CTRv2.5 by SP Flash Tool Tools with negative results, the tablet does not start in recovery mode and it does is boot normally.

PD. Again I returned to flash the original recovery with SPFT and if you boot into recovery mode, only that is not functional in the absence of volume keys.

I can be wrong? or no functional recovery for MTK8127 and Mali 450 ??
3rd June 2015, 02:29 AM |#5  
Junior Member
Thanks Meter: 0
 
More
successfully booted to CTR v2.2 ubifs, but, there bug messages in CTR menu.
after using carliv touch recovery port tool from windows i booted to my CTR v2.2 ubifs, but, in the menu screen below, there are bug messages, like, "E: cannot mount mtd14E" and other not mounted messages? im a oplus usa 8.33 user mt6572 ubifs, how can i fix this please help?
16th July 2015, 06:45 PM |#6  
Junior Member
Thanks Meter: 4
 
More
downloads gave me virus
thanks bro

next time try use a decent download site
17th July 2015, 09:21 AM |#7  
rzdz's Avatar
Junior Member
Flag .
Thanks Meter: 0
 
More
Question CTR 2.4 and Alcatel Pop C7 (7041D / MT6582)?
Hi,
thank you for this great tool!

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 (link removed)


I tried to port for Alcatel Pop C7 (7041D / MT6582)., but I'm not sure it is the correct version I used.
.recovery_version : Carliv Touch Recovery v2.4 "CGen82"


I'm searching the web since 5 weeks for a working custom recovery for this phone and for information to port a recovery, but I cannot get to the point (sorry, you can call me a noob )...

So please can somebody help me?

This is the backup folder I generated by this recovery:
Code:
 Verzeichnis von D:\Backups\test

17.07.2015  08:41    <DIR>          .
17.07.2015  08:41    <DIR>          ..
16.07.2015  23:10                 0 .android_secure.vfat.tar
16.07.2015  23:10             1.536 .android_secure.vfat.tar.a
17.07.2015  01:19                35 .recovery_version
16.07.2015  23:05         6.291.456 boot.img
16.07.2015  23:10                 0 cache.ext4.tar
16.07.2015  23:10            14.848 cache.ext4.tar.a
16.07.2015  23:09       642.777.088 custpack.img
16.07.2015  23:09                 0 data.ext4.tar
16.07.2015  23:10       234.831.360 data.ext4.tar.a
16.07.2015  23:11               557 nandroid.md5
16.07.2015  23:05         6.291.456 recovery.img
17.07.2015  01:19             6.570 recovery.log
16.07.2015  23:05                 0 system.ext4.tar
16.07.2015  23:07       405.637.120 system.ext4.tar.a
17.07.2015  08:41               353 version.txt
              15 Datei(en),  1.295.852.379 Bytes
               2 Verzeichnis(se), 820.864.557.056 Bytes frei
Is this a complete backup I can use for the case I bricked my phone?

This is the recovery.log:
Code:
Starting recovery on Thu Jul 16 22:56:22 2015
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 854)
Carliv Touch Recovery v2.4
recovery filesystem table
=========================
  0 /tmp ramdisk (null) (null) 0
  1 /boot emmc /dev/bootimg (null) 0
  2 /recovery emmc /dev/recovery (null) 0
  3 /uboot emmc /dev/uboot (null) 0
  4 /custpack emmc /emmc@custpack (null) 0
  5 /cache ext4 /emmc@cache (null) 0
  6 /data ext4 /emmc@usrdata (null) 0
  7 /system ext4 /emmc@android (null) 0
  8 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
  9 /sd-ext auto /dev/block/mmcblk1p2 (null) 0

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!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
Warning: No file_contexts
I:Warning:  No file_contexts
I:device_recovery_start()
Command: "/sbin/recovery"

ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=mt6582
ro.revision=0
ro.emmc=0
ro.boot.emmc=0
ro.factorytest=0
ro.secure=0
ro.allow.mock.location=1
persist.mtk.aee.aed=on
ro.debuggable=1
persist.service.acm.enable=0
persist.sys.usb.config=mass_storage,adb
ro.mount.fs=EXT4
ro.build.id=JDQ39
ro.build.display.id=ALPS.JB5.MP.V1.5
ro.build.version.incremental=eng.zmchivin2.1398734395
ro.custom.build.version=1398734395
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Sun May 11 12:44:49 EEST 2014
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=carliv
ro.build.host=max
ro.build.tags=test-keys
ro.product.model=ALCATEL ONE TOUCH 7041D
ro.product.brand=SESONN
ro.product.name=htt82_wet_jb5
ro.product.device=YARISXL
ro.product.chivinproduct=N9700
ro.product.chivinversion=0502K069_20140428
ro.product.customversion=0502K069_20140428
ro.product.usbname=N9700
ro.product.board=htt82_wet_jb5
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
ro.build.product=htt82_wet_jb5
ro.build.description=htt82_wet_jb5-user 4.2.2 JDQ39 eng.zmchivin2.1398734395 test-keys
ro.build.fingerprint=HTT:4.2.2/JDQ39/1398734395:user/test-keys
ro.build.flavor=
ro.build.characteristics=default
ro.mediatek.version.release=ALPS.JB5.MP.V1.5
ro.mediatek.platform=MT6582
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=ALPS.JB5.MP
ro.mediatek.version.sdk=1
rild.libpath=/system/lib/mtk-ril.sorild.libargs=-d /dev/ttyC0
wifi.interface=wlan0

ro.mediatek.wlan.wsc=1
ro.mediatek.wlan.p2p=1
mediatek.wlan.ctia=0
wifi.tethering.interface=ap0
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
ro.sys.usb.mtp.whql.enable=0
sys.ipo.pwrdncap=2
ro.sys.usb.storage.type=mtp,mass_storage
ro.sys.usb.bicr=yes
ro.sys.usb.charging.only=yes
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
ro.setupwizard.mode=DISABLED
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
persist.sys.timezone=Europe/Berlin
ro.chivin.secure=9527
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=1
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.sf.hwrotation=0
ril.current.share_modem=2
launcherplus.allappsgrid=2d
launcher2.allappsgrid=3d_20
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
persist.mtk.wcn.combo.chipid=-1
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=1
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=MT6620
mediatek.wlan.module.postfix=_mt6620
ril.radiooff.poweroffMD=0
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=Backroad.ogg
ro.config.sound_fx_volume=-10
ter.service.enable=0
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...

-- Installing: /sdcard/clockworkmod/.aromafm/aromafm.zip
Finding update package...
I:Update location: /sdcard/clockworkmod/.aromafm/aromafm.zip
Opening update package...
Installing update...
aroma/s: Initializing
aroma/s: Saving Arguments

AROMA Filemanager version 1.80
(c) 2012 by amarullz xda-developers

aroma/s: Open Archive
aroma/s: Initializing Resource

DEVICE NAME: mtk-kpd - /sys/board_properties/virtualkeys.mtk-kpd
EV ST: minX: 0  maxX: 0  minY: 0  maxY: 0
EV MT: minX: 0  maxX: 0  minY: 0  maxY: 0

DEVICE NAME: mtk-tpd-kpd - /sys/board_properties/virtualkeys.mtk-tpd-kpd
EV ST: minX: 0  maxX: 0  minY: 0  maxY: 0
EV MT: minX: 0  maxX: 0  minY: 0  maxY: 0

DEVICE NAME: mtk-tpd - /sys/board_properties/virtualkeys.mtk-tpd
EV ST: minX: 0  maxX: 480  minY: 0  maxY: 854
EV MT: minX: 0  maxX: 480  minY: 0  maxY: 854

DEVICE NAME: hwmdata - /sys/board_properties/virtualkeys.hwmdata
EV ST: minX: 0  maxX: 0  minY: 0  maxY: 0
EV MT: minX: 0  maxX: 0  minY: 0  maxY: 0

DEVICE NAME: ACCDET - /sys/board_properties/virtualkeys.ACCDET
EV ST: minX: 0  maxX: 0  minY: 0  maxY: 0
EV MT: minX: 0  maxX: 0  minY: 0  maxY: 0
aroma/s: Input Initialized
aroma/s: Opening Freetype
aroma/s: Graph Initialized
aroma/s: Mute Parent
aroma/s: Starting Interface
aroma/s: (1) Freetype fonts loaded as Font Family
aroma/s: (1) Freetype fonts loaded as Font Family
aroma/s: (1) Freetype fonts loaded as Font Family
Load Font: DroidSans.ttf - dir: assets/fonts/Droid Sans/
aroma/s: Change Folder /
aroma/s: (1) Freetype fonts loaded as Font Family
aroma/s: (1) Freetype fonts loaded as Font Family
aroma/s: (1) Freetype fonts loaded as Font Family
aroma/s: (1) Freetype fonts loaded as Font Family
Load Font: DroidSans.ttf - dir: assets/fonts/Droid Sans/
RESHOW PATH [/]
aroma/s: Close Graph Thread
aroma/s: Unmute Parent

AROMA Filemanager Finished...
aroma/s: Starting Release
aroma/s: Font Released
aroma/s: Input Released
aroma/s: Archive Released
aroma/s: Closing Freetype
aroma/s: Graph Released
aroma/s: Cleanup Temporary
aroma/s: Closing Recovery Pipe

Install from sdcard complete.
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
If someone need dumchar_info
Code:
cat proc/dumchar_info

Part_Name	 Size	              StartAddr	         Type	MapTo
preloader    0x0000000001000000   0x0000000000000000   2   /dev/misc-sd
mbr          0x0000000000080000   0x0000000000000000   2   /dev/block/mmcblk0
ebr1         0x0000000000080000   0x0000000000080000   2   /dev/block/mmcblk0p1
pro_info     0x0000000000300000   0x0000000000100000   2   /dev/block/mmcblk0
nvram        0x0000000000500000   0x0000000000400000   2   /dev/block/mmcblk0
protect_f    0x0000000000a00000   0x0000000000900000   2   /dev/block/mmcblk0p2
protect_s    0x0000000000a00000   0x0000000001300000   2   /dev/block/mmcblk0p3
seccfg       0x0000000000020000   0x0000000001d00000   2   /dev/block/mmcblk0
uboot        0x0000000000060000   0x0000000001d20000   2   /dev/block/mmcblk0
bootimg      0x0000000000600000   0x0000000001d80000   2   /dev/block/mmcblk0
recovery     0x0000000000600000   0x0000000002380000   2   /dev/block/mmcblk0
sec_ro       0x0000000000600000   0x0000000002980000   2   /dev/block/mmcblk0p4
misc         0x0000000000080000   0x0000000002f80000   2   /dev/block/mmcblk0
logo         0x0000000000300000   0x0000000003000000   2   /dev/block/mmcblk0
ebr2         0x0000000000080000   0x0000000003300000   2   /dev/block/mmcblk0
custpack     0x0000000026500000   0x0000000003380000   2   /dev/block/mmcblk0p5
mobile_info  0x0000000000800000   0x0000000029880000   2   /dev/block/mmcblk0p6
expdb        0x0000000000a00000   0x000000002a080000   2   /dev/block/mmcblk0
android      0x0000000026500000   0x000000002aa80000   2   /dev/block/mmcblk0p7
cache        0x0000000013900000   0x0000000050f80000   2   /dev/block/mmcblk0p8
usrdata      0x0000000082c00000   0x0000000064880000   2   /dev/block/mmcblk0p9
otp          0x0000000004000000   0x00000000feff0200   2   /dev/block/mmcblk0
bmtpool      0x0000000001500000   0x00000000feff00a8   2   /dev/block/mmcblk0
While the phone is booted to recovery, MTK DroidTooll reports this:

" --- BadFstab = Recovery doesn't suit this phone! "

This is not OK, is it?
Please help me...
Post Reply Subscribe to Thread

Tags
auto-qa

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes