yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] vampirefo:
[MENTION=5186178]carliv[/MENTION]

Thanks for the kitkat update, I have a question about this version, I know it's designed for MTK devices, will this recovery work on non MTK devices? I am thinking about compiling it for x86 Dell venue 8.

I have no ideal if this recovery will work on my Dell, time will tell, just curious if this recovery is able to work on non mtk devices.

Update:

I went ahead and downloaded the source, I am compiling now, so will know shortly if it works on my dell venue 8 Intel x86 or not.

Update:

OK, recovery compiled and works on my Dell venue 8, currently doing a backup with recovery.

I left the name of recovery the same, added x86 after KitKat.
[Miscellaneous Android Development] :
:laugh: Well, that's good, because it doesn't build in lollipop, and for an upgrade I have to rewrite completely the source. Good that you find it can work with a lollipop kernel :good:

Ah, yes at first was designed for MTK devices, but for latest versions I isolated all MTK modifications and activated by BoardConfig flag, so if that is not set it will work as a CWM 6.0.5.1, but with touch screen (in most devices). For building and using with x86 platforms it's the same as regular CWM.

Glad you figured out how to build it. And thanks for respecting my request about name (I didn't refer to version, only the name Carliv Touch Recovery).
[Miscellaneous Android Development] Shreps:
Very nice ?

That means Carliv Touch for Acer Intel Tabs maybe soon

Envoyé de mon One+
[Miscellaneous Android Development] vampirefo:
Yes, I should release Dell version soon, [MENTION=1829889]vache[/MENTION] should be able to port to Acer.
[Miscellaneous Android Development] Maximus1a:
after testing the new CTR3 i can give an OK for using.

thanks Carliv

Elephone G6 CTR3.0 Download:

http://www.needrom.com/download/carliv-touch-recovery-3-0-kk-lolli-ready/
[Miscellaneous Android Development] flux1000:
Support fo MTK 8752\6752...

First os all thanks for the enormous wok you are doing.. t's a clear guide for everyone of us,..those who barely understand how it really works...:good:

I've been reading and reading before daring to post here. As I haven't seen anywhere stated if this method could work with the new MTK 6752\8752 (the same but for tablets), I'd like to ask it here. Do you think it 'll work?

It's because I have a wondefrul Teclast T98 Kit KAt 4.4.4 MTK8752 powered, and although is rooted, I looking for a working method (MTKDroid failes to do the trick as you know) to elaborate a CMW myself,..with your help/advice, of course.

Thanks in advance. :)

P.S. I already have a SP Flash tool complete rom from the Teclast Tool Pad download system ( model C6R2),...
[Miscellaneous Android Development] :
The porting method doesn't work for new MTK platforms, and zopo zp999 was the first and the last phone I worked without having it in my hands. It's a very hard task to do this "in blind". So, either you learn how to build the recovery by yourself, or wait for an experienced dev to get the device and to do some work for it.

Sorry, but to work on a device I can't see it's time consuming and frustating. I'm thankfull for Zopo zp999 users support during and after the job, but I won't do that again.

If you want to build the recovery, in my threads (find link in signature) I posted a guide for that.
[MENTION=2244756]flux1000[/MENTION]

LE: Maybe I've spoken too soon. Aparently it works if the recovery to port it is built for a phone with a new platform. So head over the thread of Elephone P6000 and do what they did there. :good:

You will find in that thread few posts of mine with hints for solving some issues.

You can try just like bigrammy did it.
[Miscellaneous Android Development] ocoot:
-deleted-
[Miscellaneous Android Development] ramzidjoudi:
deleted
[Miscellaneous Android Development] aki_007:
[MENTION=5186178]carliv[/MENTION]

Just a request ...

1)can you restore that preflash wipe option which we had earlier

2)can you also provide an option to select multiple zip files to flash at once (it saves time and errors too.)

Thanks very much
[Miscellaneous Android Development] :
Sorry, but no.

The preflash option gave me a lot of troubles. Most users are not very experimented or they are just ignorant and I received too many messages about "help I can't start my phone after using that menu". They don't read the menu command, or don't know how to use it. Now if someone wants to wipe system, it can be done in format menu with format system, but from my experience almost any ROM updater script has a "format system" command.

About multiple zips, maybe, but not now. Now I'm working when I have time to change the touch code and some other functions.
[Miscellaneous Android Development] aki_007:
yeah you are right I also saw those user comments but you can place them in mount options ... like format preflash

I always put those formattins lines in updater script , So it's cool.

This one I need very much...
[Miscellaneous Android Development] exodius48:
[MENTION=5186178]carliv[/MENTION] I want to ask, I was compiled it yesterday to my device, but navigation keys menu did not work.

Did it came from my ROM / carliv / my mistake?

Can you explain me? Thanks in advance
[Miscellaneous Android Development] :
I can't because I'm not a psychic. I don't know what device you have, how you did setup your device tree, if your kernel supports touch in recovery...

There are thousands mtk devices out there; how could I possibly know everything about every one of them?

I don't understand though, if you say you've "compiled" this, why are you posting your question on the porting thread?
[Miscellaneous Android Development] exodius48:
Sorry, I mean i have ported it, but touch function did not work. I used michfood's tool to unpack. I'll try once again with your image kitchen. Hope touch function will work on my device. :)

Edit

Already ported it, but touch function not working on my device.

My device is support touch function, FYI.
[Miscellaneous Android Development] superdragonpt:
I can ensure you it works on the new elephone p7000, w/ MTK's Lollipop OS

MTK6752 64bit

@carliv, you can add this SoC as supported

Xeers
[Miscellaneous Android Development] :
Yes, I know. I already built recoveries for mt6595, mt6732 and a friend built for mt6752. All works with kernel 3.10 but they need my custom graphic file (the ones I did for zp999).

And like I said, for porting it has to be used a recovery built for same platform (or for a new one at least), so none of the recoveries from OP will work on these phones.

Regards,
[Miscellaneous Android Development] superdragonpt:
Hi

Yes...

Also working on Elephone p8000 :)

Only tested The non-touch one

and yes im talking about source built ones ( @ others )

Xeers
[Miscellaneous Android Development] killfrenzy05:
Rom may flash stock recovery on boot.Fix? THIS CANNOT BE UNDONE?

Sir Successfully ported in my skk lynx kitkat 4.4.2 with chipset mt6592 but when I tried to reboot this messages show "Rom may flash stock recovery on boot.Fix? THIS CANNOT BE UNDONE?" then there's two option click No and Yes-Disable recovery flash.. how can I fix it? tia
[Miscellaneous Android Development] superdragonpt:
Press "NO" ...

...

Xeers
[Miscellaneous Android Development] bovirus:
Is there an option/configuration file to avoid this message about the fix?
[Miscellaneous Android Development] killfrenzy05:
Yeah I mean sir.. How to avoid that message. If there's a way how to fix it?
[Miscellaneous Android Development] :
guys. how does one determine which file system his phone has? I mean weahter it's normal, custpack or ubifs? Thanks in advance.
[Miscellaneous Android Development] Call_Me_Hudson:
No Custom Recovery was made for my phone right?

damn my phone is real sh*t

Blue Life Play Mini KitKat 4.4.2 L190u MT6572

updated the version from BLU_L190_V08_GENERIC

to version BLU_L190_V13_GENERIC

with "Wireless Update" found in About Phone.

I can't even root it.

trying to do this forever

MTK Droid tools doesn't automatically create the CWM Recovery because

--- ERROR :No find KernelGZ

--- ERROR :No Split Boot Image

I seriously don't know what to do because iRoot, Kingo ROOT, Kingroot, SRS root etc doesn't work.

and I can't even port a custom recovery because i'm getting this error when i use MTK Droid tools.

ATTENTION! File /system/recovery-from-boot.p which restore factory recovery in case of phone switching on in a normal mode Is Found!

I already ported and backed up my full ROM but I can't do nothing else

I really want to root this phone. Hardest thing on earth.

If you could try and help, please do.﻿
[Miscellaneous Android Development] :
MTK Droid Tools was very good for mtk phones up to mt6592 and jellybean. Even if there are some phones with kitkat that works with it, on the russian forum where the tool is originated, they say very clear that is not kitkat ready, and probably it will never be since the developer stoped to update the aplication.

So, you have to port a recovery for your phone. My guide is easy to follow to do that, but if you're not confident you can do it, try to ask [MENTION=4939713]lopestom[/MENTION] to help you, if he has time, since he already did it for several Blu phones.
[Miscellaneous Android Development] Call_Me_Hudson:
So may I start tutorials on youtube on how to port my own custom recovery?

I wsh it was easier but this is my only choice and I'm a newb programmer
[Miscellaneous Android Development] :
Really?! You didn't even bother to read the OP?
[Miscellaneous Android Development] Call_Me_Hudson:
I'm going to read it now

Here's my boot and recovery.img can you check to see if caliv recovery can be made for my phone?

https://www.dropbox.com/s/sl2nzsc83ur8908/BLU_LIFE_PLAY_MINI_L190_KK_unmodified_Recovery.img?dl=0

^^ recovery.img above

https://www.dropbox.com/s/k1zk9qruqq3ugyu/BLU_LIFE_PLAY_MINI_L190_KK_unmodified_boot.img?dl=0

^^ boot.img above

my resolution is 480x800
[Miscellaneous Android Development] killfrenzy05:
I successfully ported in mt6592 kitkat but one problem can't mount in sdcard1 but can mount in sdcard0 and also backup and restore works only in sdcard0.. How can I fix it sir carliv?

in recovery.fstab

# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>

/emmc@android /system ext4 ro,noatime wait
/emmc@cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait
/emmc@usrdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer

# vold-managed volumes
/devices/platform/mtk-msdc.0/mmc_host/mmc0 auto auto defaults voldmanaged=sdcard1:8,
/devices/platform/mtk-msdc.1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard0:auto

/dev/bootimg /boot emmc defaults defaults
/dev/nvram /nvram emmc defaults defaults
/dev/recovery /recovery emmc defaults defaults
/dev/uboot /uboot emmc defaults defaults
/dev/misc /misc emmc defaults defaults

in fstab.mt6592

# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>

/emmc@android /system ext4 ro,noatime wait
/emmc@cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait
/emmc@usrdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer
/emmc@protect_f /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check
/emmc@protect_s /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check

# vold-managed volumes
/devices/platform/mtk-msdc.0/mmc_host/mmc0 auto auto defaults voldmanaged=sdcard0:8
/devices/platform/mtk-msdc.1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto

/devices/platform/mt_usb/sda/sda1 auto auto defaults voldmanaged=usbotg:auto

/dev/bootimg /boot emmc defaults defaults
/dev/nvram /nvram emmc defaults defaults
/dev/recovery /recovery emmc defaults defaults
/dev/uboot /uboot emmc defaults defaults
/dev/misc /misc emmc defaults defaults

I tried to change sdcard1:8 to auto but still can't mount..

/devices/platform/mtk-msdc.0/mmc_host/mmc0 auto auto defaults voldmanaged=sdcard1:auto,

thanks sir for your help..
[Miscellaneous Android Development] :
So, you didn't read my porting guide carefully....

Your device has a fat partition? That fat partition has mmcblk0p8 number? If not, there's your answer! You left unchanged the defines for my phone (a lenovo with mt6589 used as template), and you expect it to work!?

Read the porting guide again.
[Miscellaneous Android Development] killfrenzy05:
Sorry Sir.. My problem is now fixed. I understand and It work's well both in my internal and sdcard back up and restore..

Here's the link

http://internetcribs.blogspot.com/2015/03/updated-ctr-30-skk-lynx.html

BTW Thank you very much sir Carliv..
[Miscellaneous Android Development] vetfactor:
capacitive touch screen IPS

480*854

5.0 inches

Multitouch Yes (2 Finger)

Loudspeaker Yes

3.5mm jack Yes

ROM 8GB Internal storage (0 .89GB) Phone storage 4.97GB

Card slot Micro SD, up to 32 GB

RAM 1 GB

GPRS Yes

EDGE Yes

Speed HSPA/TD-SCDMA modem, WCDMA& EDGE 2.75G

WLAN Yes

Bluetooth Yes

NFC N/A

Infrared port N/A

USB Yes

GPS Yes, with A-GPS

Camera

Primary 5 MP, Flash

Secondary 2 MP

Android OS, v4.4.2 (Kit Kat)

Chipset MTK6582

CPU Quad-core 1.3GHz Cortex-A7 ARmv7 (VFPv4,NEON)/ Mali-400 MP

Sensors Accelerometer, proximity

Messaging SMS(threaded view), MMS, Email

those are my device Hardware configuration,

its KK 4.4.2 with no data about update.

did your recovery works well with?

and how to detect that the above configs are real?

thanks in advance!
[Miscellaneous Android Development] navneetasnavi:
Ported for XOLO a600

hi master . Thanks Again

Ported it for my XOLO A600

here it is
[Miscellaneous Android Development] ThePeacedog:
How generic are the recoveries? I'm wondering if this recovery will work for a Blu Studio 7?

port_CarlivTouch-recovery-3_0-600x1024.img

Thanks for any input.
[Miscellaneous Android Development] :
Pretty much will work for any MTK SOC prior to mt6595, and I believe your device has mt6572 or the equivalent for tablets (mt8312). So, it should work if you will port it (it won't work as it is - those are only builds for porting).
[Miscellaneous Android Development] :
Update (last).

Version 3.3 update (21-apr-2015):

This is the last batch of builds for porting. I won't do that anymore.

- many fixes in code;

- cleaned up the source code;

- reset battery stats option;

- wipe all - preflash option;

- removed nvram backup/restore because it can corrupt the bootloader;

-full track of changes here.

Check the OP.
[Miscellaneous Android Development] Nihal @A-JAX:
This is the port for LAVA Iris X8 by me,

http://xdaforums.com/general/general/v3-3-carliv-touch-recovery-lava-iris-x8-t3098269

Thanks Carliv

Everthing is working fine except sd card not mounting and both sdcards are not mounting in PC. How to fix it ??
[Miscellaneous Android Development] :
Are you sure you port it right? I saw in your ported image you didn't changed anything in recovery.fstab and fstab.mt6592, and if that device doesn't have same blocks numbers as my lenovo P780 (mt6589) - used by me as example, of course it won't work.

/dev/block/mmcblk0p[COLOR="Red"]5[/COLOR] /system ext4 ro,noatime wait
/dev/block/mmcblk0p[COLOR="Red"]6[/COLOR] /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait
/dev/block/mmcblk0p[COLOR="Red"]7[/COLOR] /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer

# Here, you can put some extra paths (not used in recovery.fstab), like protect_f,
# protect_s, info, custom, etc
# also, if your device has a custpack partition (Alcatel or TCL), here is the
# place to define it.
#
#/dev/block/mmcblk0px /custpack ext4 noatime,nosuid,nodev,noauto_da_alloc wait
#

# vold-managed volumes. Check the paths for sdcards in /devices/platform....
# if your device has emulated internal sdcard (data/media or data/media/0) don't
# use the next line, and don't define at all the internal sdcard in fstabs for
# recovery!
#
/devices/platform/mtk-msdc.0/mmc_host/mmc0 auto auto defaults voldmanaged=sdcard0:[COLOR="Red"]8[/COLOR],nonremovable,noemulatedsd

# if your device has an external sdcard, define it as in following line!
#
/devices/platform/mtk-msdc.1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto,noemulatedsd

Anyway, soon I will upload again all images, because there are some issues with some fonts and resolutions. I will try to make few other changes to help minivold to mount sdcards to PC.
[Miscellaneous Android Development] Nihal @A-JAX:
yes I did whatever you said in your guide and block numbers are same too. Is there anything else i have to do ??

I think the problem is with vold or something which manages sdcard mount points. how to check whether it is nonemulated or emulated ?? In x8 both sdcards were in storage i.e /storage/sdcardx

Here is dumpchar from x8,
[Miscellaneous Android Development] :
Ok, then that's the problem. As you see in dumchar, there is no "fat" partition, which means the internal sdcard is emulated (/data/media/0 probably). You used my definition voldmanaged block 8, but my device has a fat partition (separate partition for internal sdcard) on mmcblk0p8.

Just delete that definition for internal and don't put anything instead and it'll work.
[Miscellaneous Android Development] Nihal @A-JAX:
Thanks.I have to make changes in init.rc also right ??
[Miscellaneous Android Development] t-minik:
!!! does this mean Carliv touch recovery is really dead ? or you just stop these batch of porting generic files ?

really sad if you stop CTR development. that was my best recovery ever.
[Miscellaneous Android Development] :
Actually both. Yes, CTR is ended and I won't build recoveries for porting anymore. But I developed a new project Carliv CWM*T Recovery which I will focus on from now on. I've built it only for my phone.
[Miscellaneous Android Development] t-minik:
I hope your new CWM*T will be as goog as CTR was. ;)
[Miscellaneous Android Development] :
I think it's even better:

- touch;

- Multizip flash from sdcard (select how many zips you want and they will be flashed one by one) – credits to PhilZ @ xda-developers;

- Toggle vibrate on touch;

- Display battery state, and charging in recovery mode;

- Separate Wipe Menu:

Wipe Data – Factory reset

Wipe Cache

Wipe Dalvik-cache

Wipe All – including System – for preparing to flash a new ROM or to restore a clean backup

- A new menu for advanced backup and restore, with separate menus for advanced backup and advanced restore;

- USB Mass Storage mounting both sdcards (internal and external to PC);

- Working partition Sdcard in advanced menu;

- Use the fstab version 1 which is much easier to configure and you can define lun files paths in it;

- A Carliv menu with few extra menus:

Aroma File Manager access menu

Toggle Rainbow Mode for GUI

Reset battery stats (wipe)

Special MTK partitions menu: with backup and restore for uboot, logo, nvram and secro

* A fully working IMEI fix by restoring nvram and secro in special mtk menu: the nvram backup will do the /data/nvram folder as well; in order to be able to restore the IMEI and communications with this, you have to make first a backup with phone in good state, then whenever you need, restore secro and nvram and that’s it, the IMEI is restored (no other steps needed);

- Separate power menu (like in CTR):

Reboot Recovery

Reboot to download

Power Off

- Disable flash stock recovery on boot after stock ROM update or install (working);

- Root the phone if it’s not rooted, with Chainfire Supersu binary.

- It will have a new GUI design (working on it).
[Miscellaneous Android Development] t-minik:
It sounds awesome!
[Miscellaneous Android Development] charansai:
My phone boot&recovery.img

https://drive.google.com/file/d/0B7Ba--KwVLt1Tm5uSFJ2UDNjQjg/view?pli=1

Dumchar_info

https://docs.google.com/file/d/0B7Ba--KwVLt1cXhCaF82UXNFYU0/edit?pli=1

Mtk6582

Screen resolution 480x854

Ruining on 5.0

Plss port for me
[Miscellaneous Android Development] :
This recovery works with kitkat kernels, as I stated in OP. Some people ported it to lollipop, but in most cases doesn't work. It is based on CWM and CWM stoped at kitkat version.

And, also as I said before, I don't do porting jobs anymore.

Stop being so annoying: two PMs and two posts it is too much, and I won't do something because you flood me with your requests.
[Miscellaneous Android Development] nitin.chobhe:
This seems awesome.

Are you planning to extend this recovery to work with mtk devices working on lollipop?
[Miscellaneous Android Development] haimmalka:
How do I install it for p3000s mtk6752?
[Miscellaneous Android Development] vampirefo:
Looking forward to new recovery, I have just downloaded, carliv_touch_recovery, version 3.3, need to build a recovery for Blu Studio 5.0 C, this is a cheap Walmart phone, my other phone broke so I got this from Walmart seems to work well.

Also downloaded your CarlivScreenshot just now, Thanks for that tool also works great.
[Miscellaneous Android Development] :
I'm glad you find my screenshot tool useful. I couldn't find anything for linux, so I made it!

The new recovery is under development, but I don't have much time lately.... Maybe in a month or two I'll finish it. I'll try to port it to lollipop or higher too.
[Miscellaneous Android Development] kirito9:
You are just so awesome [MENTION=5186178]carliv[/MENTION] I can't wait to see this new recovery and i hope there will be base recoveries to port from ;).

I know this project is discontinued but some people still want this recovery for Kitkat. Here is my port [RECOVERY] Carliv Touch Recovery v3.3 [Kitkat] Alcatel Pop D3:)
[Miscellaneous Android Development] kirito9:
Transfer speed between PC and Sdcard

My question is does anything that i have to edit like say the init.usb.rc affect the transfer speeds? :confused: I got a complaint from a user for my ported recovery and this is what he said.

I would like to know if anything can be done to fix that. Thanks :good:
[Miscellaneous Android Development] Kiranveer Singh:
A big thanks to u for ur touch recovery.

I solute to u :)
[Miscellaneous Android Development] Nihal @A-JAX:
external sdcard not mounting to PC

Hi Carliv , I successfully ported 3.3 CTR for my KK MT6589 device. Everthing's working fine but when I mount usb storage to PC only internal storage get mounted. I get error message as:

E:sdcard1 un-shared state=1

What may be the issue ? How to fix it ?
[Miscellaneous Android Development] redlum:
UBIFS problem ?

Hello [MENTION=5186178]carliv[/MENTION] and other forum members

First of all thank you for your efforts in building this tool and releasing it to the public.

I have a phone based on MT6571 running Android 4.4.2 that I am desperately trying to root and I figured that by flashing CWM and booting into recovery mode I could then install superSU and finally get this st*pid phone rooted since all other rooting methods i tried failed.

So I followed your guide to port the recovery image onto my phone, flashed it, booted into recovery but then:

- I can't mount any of the system/data/cache folders (e.g. Error mounting /system!)

- I can't access the sdcard (Can't mount /storage/sdcard0)

I was able to sideload the superSU app using adb sideload and it apparently executed successfully but when I rebooted the phone still wasn't rooted.

I am wondering if I did something wrong in the process or if this could be the result of the file system on my phone being UBIFS.

Can you please help me out ?
[Miscellaneous Android Development] vampirefo:
Yes, it's because of UBIFS.
[Miscellaneous Android Development] redlum:
Can you suggest any other mean to get this phone rooted ? I already tried all of the framaroot, root genius, and so on. Or is there any way to convert UBIFS into another file system ?

Thanks
[Miscellaneous Android Development] killfrenzy05:
UBIF's is sucks..lol find your mount points using adb command to be able to mount.