yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] praderj:
Here you go...

http://www.mediafire.com/view/?7humxw5eb99404u

Make a complete backup before doing this.. and don't restore the old backups after doing this.. read it and do the steps carefully...

Sent from my Celkon A97i
[Miscellaneous Android Development] superdragonpt:
Why dont you just cut the picture sizes ?
[Miscellaneous Android Development] praderj:
Actually I ported the recovery for him.. I tried to reduce the size but it didn't come to 6 mb.. that's why I uploaded the ported recovery without any changes to images...

Sent from my Celkon A97i
[Miscellaneous Android Development] xhxx:
Brothers, I have ported my sec_ro in the scatter at 7 MB, tomorrow try the scatter with the COT recovery, now I go to sleep sorry brothers. :) Thanks again for the support. :D
[Miscellaneous Android Development] :
The recovery for Cubot A890, Canvas4 Micromax A210, Gionee Elife E6, UMI X2, Jiayu G4 Standard and Jiayu G4 Advanced.
[Miscellaneous Android Development] :
I don't know where you do wrong, I just follow my instructions from first post and made some shrink optimize tasks for png images (I have experience with this from making websites where the size is very important).
[Miscellaneous Android Development] praderj:
Master he provided me a wrong recovery. He didn't provide his stock recovery and the provided recovery is something else. And i confirmed with [MENTION=4259703]wahuka[/MENTION]
[Miscellaneous Android Development] wahuka:
Yes, i confirn than i provide to [MENTION=5325910]praderj[/MENTION] taiwan101 recovery
[Miscellaneous Android Development] :
And I used that to correct fstab. The stock fstab has different mount points, for example for system /dev/block/mmcblk1p3 and in custom recovery is /dev/block/mmcblk1p5. Why the difference? Because stock recovery, and also stock ROM, use protected entry protect_s which have /dev/block/mmcblk1p3 mount point, but the system is installed actually on /dev/block/mmcblk1p5. Custom recovery and custom ROM just get the shortcut, bypassing protected entry.

But in addition I've downloaded your stock ROM for stock boot and recovery img.

Exactly what I did for [MENTION=5307007]xhxx[/MENTION] too.
[Miscellaneous Android Development] praderj:
Bro.. I've a problem with the ported recovery.. adb sideload is not working.. I tried your cwm also.. but no adb sideload.. how to make it to work brother... help me...

Sent from my Celkon A97i
[Miscellaneous Android Development] xhxx:
Thanks!

Thanks [MENTION=5186178]carliv[/MENTION] the recovery works perfectly, thanks for having relieved, I have not installed anything from recovery but I think it's fine, you can also put the recovery at the second post in the thread.

Thanks again guys, you are magnificent, carliv with permission I can post in the italian thread (of italian android fourm) of Cubot M6589/A890 this recovery,Thanks let me know!

PS: I thanked both Carliv and also praderj! :)
[Miscellaneous Android Development] praderj:
you are welcome friend...

Sent from my Celkon A97i
[Miscellaneous Android Development] rictec:
porting to note II mkt6577

i did the manual porting but had some problems

boot.img or stock recovery has no fstab to replace

it boots but freeze on calibration second boot shows the menu

it complains about misc dir not found

will try again later anyone with this kind of errors?

device is

Hardware : MT6577

Model : GT-N7100

Build number : GT_N7100_Dualcore1.4_1GRAM

Build date UTC : 20121023-030012

Android v : 4.1.1

Baseband v: MAUI.11AMD.W12.22.SP.V8, 2012/08/22 20:06

Kernel v : 3.0.13 (linux-server-build0@linux-server-build0-desktop) (gcc version 4.4.3 (GCC) ) #1 SMP Tue Oct 23 10:58:34 CST 2012

Uboot build v : MAIN2.2.ubt.2934

LCD Driver IC : 1-OTM8009A_rgb_6575

thank you
[Miscellaneous Android Development] :
You have to make chages in init.rc and to change recovery.fstab according to your device. If you don't have a misc partition or has a different mountpoint you get those errors... I wrote in guide that if you can't find one of those files in stock recovery or stock boot ramdisk, delete the file from COT ramdisk.

I guess you didn't follow carefully my guide. Try yuweng's automated port tool.
[Miscellaneous Android Development] rictec:
i will retry doing it again today

i have a recovery.fstab on etc but not a fstab on root so i deleted it on COT

i had to use my kernel they are both of the same size but only the one on my device boots up also replaced the kernel module with my sec.ko make sense since i replaced the kernel had to replace it also on init.rc

the touch is strange touch buttons get highlited but they don’t do anything and touch calibration just freeze an escape key would be nice there

unfornatly the yuweng tool is for windows i only have LInux machines near if i fail again i will get a windows VM to try

thank you for the reply and for the nice recovery port to MKT :D
[Miscellaneous Android Development] rictec:
thank you for this

so my stock recovery was to blame about mount points fixed that

the rest is working no more bugs found

i posted on XDA in case you want to see it or ad to your collection ;)

http://xdaforums.com/showthread.php?p=46317760#post46317760

thank you

Rictec
[Miscellaneous Android Development] velikimeda:
Alcatel phones have two system partition system and custpack. Recovery backup only system partition can you fix that?
[Miscellaneous Android Development] :
I will look into this, I don't know yet.
[Miscellaneous Android Development] velikimeda:
Thanks. I attached factory and my working TWRP recovery.fstab.
[Miscellaneous Android Development] :
I need boot stock img, recovery stock img and a custom working recovery img, not only fstab, and also your screen resolution. And might not work - I will make a try, but after I studied this problem it must need an adjustment in source code before build. We'll see.
[Miscellaneous Android Development] Sblood86:
Should be fairly easy actually, let me know if you need help [MENTION=5186178]carliv[/MENTION].
[Miscellaneous Android Development] :
Thanks man, I was thinking to add custpack info in recovery.fstab and init.rc, and if that is not working, in source code. Do you have anything else in mind?

I saw someone add this partition instead of sd-ext, but I think I can add it along with.
[Miscellaneous Android Development] Sblood86:
Yep, it would require that and a change in the source code (specifically in nandroid):

If you take a look at the nandroid_backup (and the nandroid_advanced_backup) methods you'll see that the partitions are called by name during nandroid. I would recommend using a board define when compiling to add the requirement.

I went ahead and wrote it for you (sort of :p) nandroid_backup(/custpack)

Advanced backup will be a little bit more tricky (just sort of), add that in and test it, if it works open a pull request and I'll look into advanced backup when I merge it.
[Miscellaneous Android Development] velikimeda:
You must make changes in source code. No options for custpack in Advanced backup menu.
[Miscellaneous Android Development] :
Yes, exactly that I was thinking, but I want to write it with existence condition, just like sd-ext, to make it work with other devices too:

vol = volume_for_path("/custpack");
if (vol == NULL || 0 != stat(vol->device, &s))
{
LOGI("No custpack found. Skipping backup of custpack.\n");
}
else
{
if (0 != ensure_path_mounted("/custpack"))
LOGI("Could not mount custpack. custpack backup may not be supported on this device. Skipping backup of custpack.\n");
else if (0 != (ret = nandroid_backup_partition(backup_path, "/custpack")))
return ret;
}

And, of course related modifications to restore. I'll let you know if these will work. Thanks again!
[Miscellaneous Android Development] Sblood86:
Aye, that would work as well; I'll accept either as a pull request if you prove it works.

Edit: and yeah sorry I thought restore was implied :p
[Miscellaneous Android Development] Yash98:
I am not able to Manual/Auto port this recovery.

Device: Canvas 4 (Micromax)

RAM: 1GB

Internal memory: 8GB

Processor: Quad Core MT6589 SoC Cortex A7

Stock 4.2.1 Canvas 4 Firmware: http://www.tusfiles.net/agbdwr69sc8s
[Miscellaneous Android Development] :
Please test attached recovery (already ported) and tell me if it works.
[Miscellaneous Android Development] Yash98:
Thanks, I'll test it later but I want to learn how you made this recovery, I followed all of your steps? :confused:

Thanks

EDIT: Flash_Tool shows failed loading ROM Recovey
[Miscellaneous Android Development] :
What is your recovery partition size? I shrinked a little the recovery. Attached here now. If this works, unpack it with michfood's tool and look inside to see what's different. That way you can understand how I did it.
[Miscellaneous Android Development] Yash98:
This one works thanks a lot but i am not able to tap the red dot (touchscreen in recovery not working)
[Miscellaneous Android Development] :
You're welcome.

Some MTK phones have a weird way to initialize touch, so you don't need to touch the red square. Instead touch on the edge of the screen - top, bottom... try untill you get response on log - this is a fix suggested by yuweng.
[Miscellaneous Android Development] wahuka:
Hello [MENTION=5186178]carliv[/MENTION], i am wahuka, that of B6000.

when trying to install some file from the recovery and file this under line 28 on the screen, the recovery shows no more than 28 lines.

Can you repair this bug?

another request that is making me many people is whether it could be done with a font size a little bigger.

Thanks for your time.

regards
[Miscellaneous Android Development] Sblood86:
The line issue I believe is related to the max rows and will require the recovery to be recompiled, some screens are little obnoxious about the display rows, will probably need to lower it (like we did for the ls670), something like the following thrown into the board config might work.

BOARD_TS_MAX_ROWS := 22

Font size is also going to require recompiling with a different font, I believe Carliv has this info already.

Edit: btw the default max rows is 30, hence I said lower it if it's stopping at 28, should force it to scroll.
[Miscellaneous Android Development] :
Yes, I know, I've told that to wahuka too, but is not only from max rows - somehow the scroll is not working only with that.

I did solve it, only I didn't have time yet to recompile again all resolutions (it takes me two days).

Beside lowering max rows number, I added in source a fix for scroll menu. I will make a pull request for that because I have tested it and it works very well.
[Miscellaneous Android Development] Sblood86:
Cool, I need to look at the new swipe touch that wasn't recently merged to CWM but really there are a few other things I need to catch up with CWM on first lol. But yeah, always down for pull requests of any sort.
[Miscellaneous Android Development] wahuka:
Yes, it works perfect now.
[Miscellaneous Android Development] vevs:
Please, correct the link to FHD image (error 404). And many thanks for your work! :)
[Miscellaneous Android Development] elsorroct:
if possible for w8s ???
[Miscellaneous Android Development] captain_nemo:
Hello Master Carliv,

I have ported Cannibal Open Touch Recovery 2.1.3 to Micromax A110. Though SuperDroid-Bond ported it earlier, I noticed slight new changes in your current build, so I ported your latest COT recovery build.

http://xdaforums.com/showthread.php?p=47445506#post47445506

Thanks.
[Miscellaneous Android Development] BigBison420:
OP - Hello.

This may seem a bit silly but i ask anyway...

I am currently modding an MTK smart watch (s5 or zgpax it's called).... good specs: 512Mb Ram, 4GB Rom, camera, dual core ICS 4.0.4 - Very fast. Already rooted and did many things via Rom Toolbox. I am looking for alternate recovery to back up Rom before i start getting ballsy with these mods. The screen res is 240x240 - Any idea if that could be done for a smart watch?

The current recovery is a bit like CWM with failry large text and it's actually easy to use, but lacking basic backup features. Also i have only 2 buttons... power and back button on the side

Attached a pic for your viewing pleasure
[Miscellaneous Android Development] :
If someone will port it.

In theory it will be possible, but must be compiled from source, because of that peculiar resolution. Although, it might not work the touch feature... And one inportant thing: how big is your recovery partition?
[Miscellaneous Android Development] hamsam:
I ported it using tools but the recovery size is bigger than my device recovery partition how to compress it more...my device partition is about 5.6 mb and recovery is 6.9 mb
[Miscellaneous Android Development] iTalisman:
Can you make one for Gionoee Elife E5? I can't find one :(
[Miscellaneous Android Development] hamsam:
Download and port easily through autoport cot tools for mtk...
[Miscellaneous Android Development] chauhanjayc:
Xperia C

hi

could you guide me or provide me any link for Xperia C customer recovery

aside below is the link for boot.image and recovery.img

if any one wants to create a customer recovery for the same

boot.img : http://d-h.st/YUK

recovery.img : http://d-h.st/Gpv
[Miscellaneous Android Development] petesimon:
COT for Jiayu G4A works

Thanks Mr. Carliv! Works fine for my Jiayu G4 Advanced. I like to use the Jiayu.es app to do some flash on my phone. So I simply zipped the one recovery-cot-Jiayu-G4-advanced.img file and put the zip file into /mnt/sdcard/JIAYUES/RECOVERY folder and opened my Jiayu.es app and flashed the zip file, and the app reboots into recovery successfully. Huh, some kinda magic! Same procedure works for CWM and Carliv touch recoveries.

Jiayu.es apk file

http://ge.tt/api/1/files/4kklvs81/5/blob?download

Cannibal recovery zip for G4A (contains only one .img file)

put this file into /mnt/sdcard/JIAYUES/RECOVERY folder

http://ge.tt/api/1/files/4kklvs81/01/blob?download

also Carliv recovery zip for G4A. use same way as the above file.

http://ge.tt/api/1/files/4kklvs81/11/blob?download

-----

By the way, the Carliv recovery is soooo colorful. :silly: I was hoping for a unicorn or pink pony to run across the screen any minute. :fingers-crossed: Does COTR also show the colors?
[Miscellaneous Android Development] fonehacker:
I Ported it to Micromax A117 Canvas Magnus MT6589T (v2)

thread link:

http://xdaforums.com/showthread.php?t=2600467

thank you very much.
[Miscellaneous Android Development] iZLeeP:
Hi [MENTION=5186178]carliv[/MENTION],

I successfully ported this to my Lenovo P700i using the autoport tool and it is working great. I don't have a thread but I uploaded the recovery image to dev-host site. If you want I can give you the link.

Thanks for the great work!
[Miscellaneous Android Development] DjSylvester:
E-boda Sunny V35

If i can provide the img files needed to port the recovery , can someone help me get the port for it ? I am not sure wich CWM works for it so that`s why i ask for help. My device has a 320x480 resolution screen with an ALPS MTK 6572M dual core 1.2 Ghz, PowerVR SGX531 GPU, IPS touch screen. I have backup all my internal phone system files, so i can provide them to port a recovery for it. Device is called E-boda Sunny V35.
[Miscellaneous Android Development] BenDroid1:
This if for u to read to help me please ... [MENTION=5186178]carliv[/MENTION] Ok this is a dream come true to know that people actually consider developing for mtk phones A big thnx for THAT! but anyways i have a problem. i have an mtk6572 rooted phone and its a my saga c3 and in the instruction its says am suppose to get my recovery and boot.img but it didnt tell me where and also get a cwm for your phone what is that suppose to mean i came to this thread to get a custom recovery cause i couldn't find any? So where it is and how to get it. if anyone is familiar with the phone my saga c3 what file system is it its a jellybean phone too i bought it from chinavasion. please help oh and can i get bricked by messing around with the recovery like what if it fails
[Miscellaneous Android Development] FunSucker:
work with mtk6577 (480x800) , auto-installer . when installed, i must use power button (selection) , volume (+) and volume (-) OR setting button and home button (up and down) . touch and swipe doesn't work for me, sir.

how should i do to make this recovery work with touch on my mtk6577 , sir ?
[Miscellaneous Android Development] pugsang:
Cannibal Open Touch recovery ZOPO ZP700 MTK6582

Tested and working

https://mega.co.nz/#!4w0A0ByI!27gs7oU3ph4kVdtWG5LmQIbbTapLv4DhEp9G8FSoC_0
[Miscellaneous Android Development] lohanbarth:
@ carliv

cot recovery work custpack with it, thank you in advance
[Miscellaneous Android Development] superdragonpt:
Sorry whrong thread ......
[Miscellaneous Android Development] lohanbarth:
COT for alcatel 5036x pop C5

@ CARLIV

COT_5036x_pop_C5 alcatel without custpack:highfive:

THANK YOU for your work
[Miscellaneous Android Development] Jeffrianz:
Anyone known this recovery working on mtk mt8382
[Miscellaneous Android Development] Upo_hu:
I've ported COT 2.1.3 manually to Doogee Collo3 DG-110, it works but upside-down (batman style). Touch is upside-down too so it is usable but is it possible to make it the right direction?
[Miscellaneous Android Development] navneetasnavi:
Ported For XOLO A600 Successfully ! THANKS

So i successfully ported Cannibal open touch recovery today for my mt6572 device with emmc partition i.e, XOLO A600 .

Here Is The Download Link

Thanx again :)
[Miscellaneous Android Development] nightwalker:
Hello @carliv sir.I ported COT to Xolo A500s.Thanks to you.

Here is link:- Click here to open
[Miscellaneous Android Development] navneetasnavi:
Port :)

I ported This cot recovery for my XOLO A600 successfully. Please add this in the successful ported for device list [MENTION=230200]master[/MENTION] Shifu Carliv Sir :)

Here is the link to thread
[Miscellaneous Android Development] @dARKdROID:
Awesome Work Dude.. :good:
[Miscellaneous Android Development] janmae:
Success manually ported to Lenovo S939

Here Is COT Recovery Download Link

[IMG="cot_recovery_s939"][/IMG]
[Miscellaneous Android Development] lols21.10:
[MENTION=5186178]carliv[/MENTION]

i need your help your both recovery this one and the carliv one did not worked for with tool(auto- manual mode) and without tool.Well drop that i have cm11 source so i thought of making it from source but you local manifest for cm11 branch is outdated : https://github.com/projectopencannibal/android_bootable_recovery/tree/cm11

Any you write a guide about how to build from source ?
[Miscellaneous Android Development] Vishesh:
Can someone port this recovery for canvas HD plus a190 device.. Pls if pos..
[Miscellaneous Android Development] nophyan:
Can you help me port to my qualcomm?
[Miscellaneous Android Development] Sblood86:
Speaking for Project Open Cannibal here I can tell you that we have more or less abandoned the old recovery repo you have linked here. The new repo is still in alpha status, https://github.com/ProjectOpenCannibal/android_bootable_recovery-cm, this is forked from the yet unreleased CM recovery (an AOSP fork rather than CWM). It doesn't have the MTK changes that [MENTION=5186178]carliv[/MENTION] made to his fork of our old repo but building for device is significantly easier (so long as the device isn't landscape) with the exception of some older devices don't work right with the touch code. Frankly I don't know if the old repo will work right for you or not but if you did want to build it you could very easily sync CM11 from their own manifest and just replace the bootable/recovery with ours (you will need to make the appropriate device changes as well, none of which are required with that new repo).
[Miscellaneous Android Development] :
I had no time lately to do any work for these projects. To be honest, when I started my projects on recoveries, was because there wasn't any working touch recovery to fit a small partition (6Mb), as in MTK phones. Now, I saw they changed that size in new mt6592 and up powered phones, but in old ones it remained the same - even after kitkat upgrade. So, maybe if I will have time, I will try to continue what I started.
[Miscellaneous Android Development] d3m3:
Cant make it for Allview AX4 Nano ALPS clone :(

Hey guys, im having trouble building CWM or TWRP for my frypan. I want a touch or nontouch version of one of the 2 .

This is my phablet:

ATTENTION! Fake Hardware in kernel or firmware doesn't correspond to phone!
Hardware : MT6582 (MT8312 is Fake!)
Model : AX4Nano
Display : 480 x 800
Build number : AX4Nano_KK_SV7.0
Android v : 4.4.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V35.P4, 2014/06/27 14:22
Kernel v : 3.4.67 (weiw@pnserver-66) (gcc version 4.7 (GCC) ) #1 SMP Mon Aug 25 16:11:20 CST 2014
My device is a ext4 with 800 x 480 pixel display emmc partition.

Full specs HERE.

Tryed using CTR but failed . PIC, Tryed MTKDT but that failed too saying: --- ERROR :Recovery doesn't match by the size !

Tryed making it manualy using boot from phone and your ports (Carliv) and that failed also( COT, touch and nontouch vers).

After reading some more, i manualy unpacked my boot.img and recovery.img and in default.prop i see secure flags are on.

ro.secure=1
ro.allow.mock.location=0
persist.mtk.aee.aed=on
ro.debuggable=0
persist.service.adb.enable=1
ro.adb.secure=1

So i tryed seting them to 0 and debugging to 1 repacked and when flashed i get different size and bootloop. Also when i try making it manualy with MTKDT.

Im out of solutions and i ask for your help and guidance.

Here is my stock Boot+Recovery.

Firmware blocks

Scatter File

=== EDIT ===

After unpack stock and port recovery.img files copyed meta_init.project.rc meta_init.rc ueventd.rc meta_init.modem.rc and fstab from original ramdisk to port ramdisk, fstab from ramdisc/etc to same path port folder and kernel and kernel_header to port then repacked and size is 6.14 M and maximum admited is 6.

Found a smaller cwm template for MTK DT and managed to make autocwm wich is verry buggy and unstable ... now struggling to set kernel secure flags to 0.

Thanks in advance !
[Miscellaneous Android Development] silver_619:
how Can I use my custpack partition in alcatel
[Miscellaneous Android Development] franzyroy:
One or two question please,

Android Image Kitchen[/URL] (another tool to unpack/ pack) the img can also do it? I ask because, I've no issue with it when I make custom TWRP!

Your tuto,

Can it work for Samsung Galaxy S4 (GT-I9505 - Qualcomm)?
[Miscellaneous Android Development] :
Well, you didn't pay attention to the title of this thread. What you see here is for MTK powered phones, not Qualcomm... I don't think you can port recoveries for qualcomm.

And, that being said, no Android kitchen doesn't work, because these images have MTK header, which Android Kitchen doesn't recognize.
[Miscellaneous Android Development] joni2012:
Hello good news, porting htc m8?
[Miscellaneous Android Development] Swapnil Solanki:
Ported Cannibal successfully for Android one add to list

http://xdaforums.com/crossdevice-dev/android-one-general/port-sprout-cannibal-recovery-cot-t2967260
[Miscellaneous Android Development] manojkumar8552:
IS there any guide for samsung device ???
[Miscellaneous Android Development] :
Sorry but the porting "thing" only works for MTK platform, for the other platforms (qualcomm, exynos, etc.) the recovery have to be built from source. At least that's what I know.