yashsingh1/xdaforums huggingface dataset:
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] KevinBaker:
If you read the instructions and did some research you'd know that you don't have to worry about your bootloader, as XDA Live and 1.35.00.11 Radio both use the modified RUU updater which pushes SSPL to the phone, so it doesn't matter what bootloader you're using.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] epicurean:
Thanks. Believe it or not, I have spent hours reading the threads but with so many changes and so much information, it can get rather confusing.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] wpbear:
Can not use the Ext ROM in the WM6 Roms you would still have to execute each cab from the ext rom manually.
[Miscellaneous Android Development] :
Tap on menu tile to access the listed function:

In long menu lists (as in select zip from sdcard), to go back, or to scroll up:

<<<<<<<<<<< SWIPE TO LEFT ON SCREEN <<<<<<<<<<<

just under the last menu tile visible.

To scroll down:

>>>>>>>>>>> SWIPE TO RIGHT ON SCREEN >>>>>>>>>>

If the swipe feature doesn't work, you can use volume buttons to navigate down or up, one by one, through menu tiles.

Other solution is to use bottom virtual keys:

First is for Go Back, and it does just that (go back to precedent menu):

Second is for navigate down through menu items, but if you reach the end of menu in long list menus, it will take you back to first position on top:

Third is for navigate up through menu items, and if you are already at the top position it will bring you to the end of menu (in long list menus):

And last position is for select menu - it does same thing as tap on menu tile - access that function:

I did removed those virtual keys in previous releases, but because many phones can't get swipe to work, I integrated them back. The reason to remove was to reduce the size of recovery, but now I redesigned all images and shrinked so much that now all images, with virtual keys included, are smaller in size than the old release images without virtual keys.
[Miscellaneous Android Development] :
List of working recoveries for MTK phones.

Micromax Unite 2 A106

Lenovo P780 - [4Gb/CN/2013 version]

BLU Life Play X L102

BLU Life Play L100

Jiayu G4 Standard

ZOPO ZP999

Acer Liquid E2 (V370/C11)

Acer Liquid Z500

XOLO Q3000

MyPhone Agua Rio v2(kitkat)

Gionee M2

Mode LifeOne

Lenovo S860 ROW

Elephone G6

Elephone P6000

AcerLiquid E3 (E380)

Ulephone Be Pro

Acer Iconia A1-811

Acer Liquid Z500

If you need an image with logo on your thread, take this one attached here.
[Miscellaneous Android Development] superdragonpt:
Awesome .

I i

Only had time to test , The 960x540 res version.

Só far everything seems OK

Thumbs up
[Miscellaneous Android Development] freedgt:
hi my recovery size is 6Mb stock ,my device mtk6589 star N9500, test recovery file 1280x720 not work have idea?

unpack this is recovery https://www.androidfilehost.com/?fid=95851939534733629

in to rmdisk is fstab.mt6582

Please do not quite understand the English language

help me thanks

thank you
[Miscellaneous Android Development] :
Actually I think this one is: https://www.androidfilehost.com/?fid=95851939534733625

But if you flash it as it is in your phone clearly won't work. That is only for porting, the kernel is not a real one, is just a bunch of blank bytes. I even put this message in that dummy kernel too:

So, you have to port it to your device first (follow my guide) and then it will work. One other thing is if your new kitkat kernel is bigger than 4 Mb, it won't work again because the recovery will exceede the 6 Mb size of partition.

Cheers!

PS: I'm sorry I don't know Italian. I'm doing my best here in English even if it's not my language too.
[Miscellaneous Android Development] Swapnil Solanki:
Thanks. I'll be Porting it soon to Android One Devices. :)
[Miscellaneous Android Development] lopestom:
Update done!

http://xdaforums.com/showthread.php?p=57506400

[ROM][ROOT][CWMv6CTRv3.0\TWRPv2.8.0.0][MT6589T-16GB - KK 4.4.2] BLU Life Play X L102

http://xdaforums.com/showthread.php?p=57506762

[ROM][ROOT][CWMv6CTRv3.0/TWRPv2.8.0.0][MT6589 - 4GB - KK 4.4.2] BLU Life Play L100

_____________________________

[MENTION=5278745]freedgt[/MENTION]

Maybe you download this CTRv3.0 because is same resolution of the your device and trying to port with your stock kernel and recovery.fstab, others files....

If you not have knowledge for create your custom recovery is need read and following instructions by Master [MENTION=5186178]carliv[/MENTION] on the another thread.

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

[GUIDE] How to port custom CWM-based (Carliv Touch) recovery to other MTK phones
[Miscellaneous Android Development] binded2:
do you think that you could port for the life play 2 "l170a'
[Miscellaneous Android Development] lopestom:
I did some testing files (No v3.0). But this is V14 the kernel has the size of 4.8MB. It would be better if the kernel had a size of 3.4MB or maximum 4.2Mb.

I'll leave the files to an experienced user and if all is well, the file will be free to all users BLP2_L170.
[Miscellaneous Android Development] binded2:
thanks let me know
[Miscellaneous Android Development] freedgt:
I can not do

difficult for me to understand

sorry

thank you mater carliv and all
[Miscellaneous Android Development] :
If you want, I'll try to port it for you these days, but I need your stock boot.img, stock recovery img and the dumchar_info file (get it with adb from your phone, and if you don't know how ask one of your friend from Italian forums to tell you - I have that written in my guide but since you can't understand...).

Cheers!
[Miscellaneous Android Development] ygorigor:
CTR 3 for Jiayu G4 Standard

I ported Carliv Touch Recovery 3 to Jiayu G4 Standard
[Miscellaneous Android Development] mirrr46:
Hi,

It is possible that you can do Carliv Touch Recovery for ZOPO ZP780?

Please :D
[Miscellaneous Android Development] :
Yes, but I need a stock boot image, stock recovery and a dumchar_info file from your phone.
[Miscellaneous Android Development] Shreps:
Thanks for your work Carliv

I ported your reco for the Acer Liquid E2 (V370/C11) : http://forum.frandroid.com/topic/211788-recovery-carliv-touch-recovery-30-v370c11e2/
[Miscellaneous Android Development] :
Very well. I hope the Acer users to enjoy using it. I'll post a link on the working list. Thanks for notifying me!
[Miscellaneous Android Development] napo7:
Hi

You should modify the "delete from sdcard0" : it is a bit too long, and it's truncated : you can't see if the buttons refer to sdcard0 or sdcard1.

Perhaps "del from sdcard0" or "delete from sd0" would be better ?
[Miscellaneous Android Development] freedgt:
no problem for boot.img stock, problem for dumchar_info how to extract?

my boot stock

https://mega.co.nz/#!kBoDgC5B!vArF04FCPMsK5J9MDkUbXKHMXIfAd0fllZkfbCZCwxg

recovery stock

https://mega.co.nz/#!AAR3DAya!Y4oeo_yBGSE8rtERUse4fyYY8We48ASr78ZPkaBk5SM

thank you master carliv :good:
[Miscellaneous Android Development] :
With adb. Connect the phone with USB Debuging activated to PC and type this in terminal:

adb shell cat /proc/dumchar_info

Then copy the result from terminal screen and save it in a text file.
[Miscellaneous Android Development] bovirus:
with adb shell cat /proc/dumchar_info > dumchair_info.txt

will create the dumcjair_info.txt file with all info.

I made it as standard to maintain all info.

To have a text file with unsefull ewline I replaced all CR/LF (unsefull) with nothing (delete all CR/LF) and replace all CR with CR/LF to read it on Windows/Unix.

Otherwise you can catch via prompt MSDOS the list with right clic -> Mark the select teh text region to copy, then press NETR.

The text now it's in the Clipboard. You can past into a text editor.

---------- Post added at 04:58 PM ---------- Previous post was at 04:28 PM ----------

@Carliv

Could you help me with teh recovery. I attached the archive with boot.img/recovery.img/dumchar_info.txt.

http://www62.zippyshare.com/v/53412629/file.html

Thanks.

Question about other phone (no related to the phone that I attached the file..); If I have a device with stock recovery /3e) not working (small green robot fall down) and with red esclamation amrk, is it possible to create fullrecovery (i
[Miscellaneous Android Development] avi3230:
Nice work as always Sir:good::good:

Recovery ported and fully working - XOLO Q3000 - MTK6589T

recovery thread

ported recovery.

Thanks a lot again Sir.:good::good:
[Miscellaneous Android Development] freedgt:
C:\Users\free\Desktop\mtk6577tool\MtkDroidTools\MtkDroidTools>adb shell cat /pro

c/dumchar_info

Part_Name Size StartAddr Type MapTo

preloader 0x0000000000600000 0x0000000000000000 2 /dev/misc-sd

mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0

ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1

pmt 0x0000000000400000 0x0000000000100000 2 /dev/block/mmcblk0

pro_info 0x0000000000300000 0x0000000000500000 2 /dev/block/mmcblk0

nvram 0x0000000000500000 0x0000000000800000 2 /dev/block/mmcblk0

protect_f 0x0000000000a00000 0x0000000000d00000 2 /dev/block/mmcblk0p2

protect_s 0x0000000000a00000 0x0000000001700000 2 /dev/block/mmcblk0p3

seccfg 0x0000000000020000 0x0000000002100000 2 /dev/block/mmcblk0

uboot 0x0000000000060000 0x0000000002120000 2 /dev/block/mmcblk0

bootimg 0x0000000000600000 0x0000000002180000 2 /dev/block/mmcblk0

recovery 0x0000000000600000 0x0000000002780000 2 /dev/block/mmcblk0

sec_ro 0x0000000000600000 0x0000000002d80000 2 /dev/block/mmcblk0p4

misc 0x0000000000080000 0x0000000003380000 2 /dev/block/mmcblk0

logo 0x0000000000300000 0x0000000003400000 2 /dev/block/mmcblk0

ebr2 0x0000000000080000 0x0000000003700000 2 /dev/block/mmcblk0

expdb 0x0000000000a00000 0x0000000003780000 2 /dev/block/mmcblk0

android 0x0000000028a00000 0x0000000004180000 2 /dev/block/mmcblk0p5

cache 0x0000000007e00000 0x000000002cb80000 2 /dev/block/mmcblk0p6

usrdata 0x0000000040000000 0x0000000034980000 2 /dev/block/mmcblk0p7

fat 0x000000006cba0000 0x0000000074980000 2 /dev/block/mmcblk0p8

bmtpool 0x0000000001500000 0x00000000ff9f00a8 2 /dev/block/mmcblk0

Part_Name:Partition name you should open;

Size:size of partition

StartAddr:Start Address of partition;

Type:Type of partition(MTD=1,EMMC=2)

MapTo:actual device you operate

my log
[Miscellaneous Android Development] :
I asked for stock boot and recovery. The boot image may be stock, but the recovery you posted here is made with rua1's MtkDroidTools. If you want me to help you please do what I ask. So take a boot.img and recovery.img from official kitkat ROM and post them here.

Same as above, that is not a stock recovery. And you don't say why you need my help, what you tried and doesn't work.

About that stock recovery... If the kernel is ok and you have a working boot.img you can do it.
[Miscellaneous Android Development] freedgt:
dont have recovery and boot kitkat

I want to bring recovery

to install kitkat

boot does not exist in rom zip

thank you
[Miscellaneous Android Development] :
If you don't have a stock boot and recovery with kitkat kernel I can't "make" a kitkat recovery for your phone. Those have to exists otherwise it won't work. A

Sorry but I can't help you in this case.
[Miscellaneous Android Development] bovirus:
[MENTION=5186178]carliv[/MENTION]

Could you help me creating the recovery?

I posted the archive with boot.img/recovery,.img stock and dumchar_info.txt some post ago.
[Miscellaneous Android Development] :
And few post after I told you that the posted recovery is not the stock one (unless phone manufacturers have a deal with my friend yuweng to build recoveries for them). Also, you forgot to tell what phone is that and what resolution has.
[Miscellaneous Android Development] bovirus:
Probably there was a misunderstanding

The file that I posted was stock boot/recovery about Mode LifeOne (alias MPAI 809T) KK diplay 1280x720 MT6592.

http://www.modeitalia.it/life_one.html

The file that I posted was stock files.

Then I told that I have another phone (N9500 MT6582) that I was investiganting about a problem on not workingg stock recovery.

The phone has stock boot/recovery but pressing POWER + VOL+ stock recovery didn't work.

And I posted if in this case the CWM recovery could be work.

But it's a problem less important because I recieved a new firmware for this N9500 MT6582 to test.

The original request was about LifeOne phoen and the file are stock.

Please help me with Lifeone file.
[Miscellaneous Android Development] :
About that LifeOne recovery I was talking. Here is the default.prop:

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JZO54K
ro.build.display.id=cm_MediaTek-eng 4.1.2 JZO54K eng.yuweng.20140906.190548 test-keys
ro.build.version.incremental=eng.yuweng.20140906.190548
ro.build.version.sdk=[COLOR="Red"]16[/COLOR]
ro.build.version.codename=REL
ro.build.version.release=[COLOR="Red"]4.1.2[/COLOR]
ro.build.date=Sat Sep 6 19:06:05 MYT 2014
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=[COLOR="Red"]yuweng[/COLOR]
ro.build.host=[COLOR="Red"]BBQLinux[/COLOR]
ro.build.tags=test-keys
ro.product.model=LIFE ONE
ro.product.brand=MediaTek
ro.product.name=cm_MediaTek
ro.product.device=719v92_hydy_mode
ro.product.board=MediaTek
ro.product.cpu.abi=armeabi
ro.product.manufacturer=MediaTek
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=MTK
# ro.build.product is obsolete; use ro.product.device
ro.build.product=MediaTek
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=cm_MediaTek-eng 4.1.2 JZO54K eng.yuweng.20140906.190548 test-keys
ro.build.fingerprint=MediaTek/cm_MediaTek/MediaTek:4.1.2/JZO54K/eng.yuweng.20140906.190548:eng/test-keys
ro.build.characteristics=default
ro.cm.device=MediaTek
# end build properties
#
# system.prop for MediaTek
#

#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.kernel.android.checkjni=1
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

As you can see is not a stock recovery default.prop. The recovery is a ported twrp, probably created with my friend's tool.
[Miscellaneous Android Development] bovirus:
Yoiu are right.

I made an errore creating the zip from the wrong folder. I will check and I will re-post the,.

I'm very sorry.
[Miscellaneous Android Development] cleverior.ipul:
[MENTION=5186178]carliv[/MENTION] : whether carliv recovery v2.7 dont have touch support ? cz i've managed to compile it from source with cm10.1 source but when i test it, i can touch menu. I should use volume to navigate it.
[Miscellaneous Android Development] :
Yes it does. Probably your phone is one from exceptions (from my OP screenshot):
[Miscellaneous Android Development] cleverior.ipul:
Hmm.. or there is additional config that should i add to boardconfig to make touch work ?

bcz i try TWRP and the touch function is work. but im confuse why in carliv recovery is doesnt work.
[Miscellaneous Android Development] :
Different touch code. Every touch recovery has it's own touch code and that is not working the same in all phones.
[Miscellaneous Android Development] //.dax:
Hi [MENTION=5186178]carliv[/MENTION]

First, thanks for recovery for my Acer Z500, it is better than auto-made one I have been using before. Keep up in good work ;)

Can I ask you something? I cannot find "Fix permissions" ability, anywhere. It is implemented or not?

Sorry for such a noobish question, it is my first time using cwm (twrp on desire x before)

Thanks for response
[Miscellaneous Android Development] :
Actually the recovery for your Acer was made/ported by Shreps using my resources, but you can thank both :)

The "fix permissions" feature was removed by cwm people long ago (6.0.3.4). Read about that here and here. They said at that time that people will continue to ask about this long after, as they did after removing "delete battery stats". Well, "fix permissions" in twrp is different than the same from cwm, and for newer versions could do more bad than good.
[Miscellaneous Android Development] aki_007:
Sir can you please port the Carliv recovery to my device as I am unable to port it ...

BOOt img and recovery image are in attachment alongwith dumchar_info.txt.

I know its rude to ask you to do it but it would be great if you could help.

my device res-480x854
[Miscellaneous Android Development] bovirus:
Hi Carliv.

i contacted the manufacturer that for safe resend me the stock firmware and and I'm sorry but I ddidn0't make a wrong backup (as I believed). The stock recovery image is a TWRP 2.8.0.

Is it possible to create your recovery starting from a stock recovery that it's a TWRP 2.8.0?

If you can please use my file that I posted before.

http://www62.zippyshare.com/v/53412629/file.html

Thanks.
[Miscellaneous Android Development] :
[MENTION=637263]bovirus[/MENTION] your recovery is here

, [MENTION=5648292]aki_007[/MENTION] your recovery is here

, [MENTION=6168512]Kyzrael[/MENTION] your recovery is here
[Miscellaneous Android Development] bovirus:
Thanks Carlv. I will test it.
[Miscellaneous Android Development] aki_007:
Thanks .

Just one request : Could please add options for selcting multiple files in the recovery as it saves much time and error during installing multiple files and when there is a sequence for installing files required.

Thanks again for your awesome work
[Miscellaneous Android Development] bovirus:
For who make a procedure to extract dumchair_info and create a text file can sue adb tools and fart (find and replace text) to create a simple bat (ex- dumchar_extract.bat)

[MENTION=279333]ECHO[/MENTION] off

CLS

echo ** Getting dumchar_info from Android device

adb shell cat /proc/dumchar_info > dumchar_info.txt

rem killing adb server (to avoid it running)

echo ** Killing adb server

adb kill-server

if not exist dumchar_info.txt goto exit

echo ** Processing dumchair_info.txt

rem delete CRLF standalone (not needed)

fart -q --remove dumchar_info.txt -C \r\n

rem convert CR into CR-LF

fart -q dumchar_info.txt -C \r \r\n

:exit

echo. && echo.

---------- Post added at 04:41 PM ---------- Previous post was at 04:09 PM ----------

@Carliv

Could create the recovery with theese files?

http://www36.zippyshare.com/v/xzacAeXV/file.html

Are about N9500 MTK6582 - Resolution 1280 x720.

Thanks.
[Miscellaneous Android Development] hanuma:
Why do not you collect yourself, where everything is written in detail How to port custom CWM-based (Carliv Touch)
[Miscellaneous Android Development] bovirus:
Because I already tried but I have some problem on sd mapping...
[Miscellaneous Android Development] :
Well, I did it once, and before I worked countless hours to provide all info and resources necessary to DIY, so I can't do it again, everytime one of you ask. I want to do other things too, not just to port recoveries for other people.

If you tried and failed, take a look on my ported recovery and see what's different than yours, then read again the porting guide. This is how you can start to learn.
[Miscellaneous Android Development] bovirus:
The problem is that the original stock has probably some problems regarding SD that is mapped as media_rw/sdcard1 and MTKDroid cannot backup ROM.

This is because I need your help about it.
[Miscellaneous Android Development] mustatir:
Sir carliv. Please port it for me.

Boot.img https://www.dropbox.com/s/47na4j3vlw38kgs/boot.img?dl=0

Recovery.img https://www.dropbox.com/s/crce7tnzr6ynl66/recovery.img?dl=0

Dumchar.info https://www.dropbox.com/s/i9y5m97k1f4z8lg/dumchar_info.txt?dl=0
[Miscellaneous Android Development] bovirus:
[MENTION=5186178]carliv[/MENTION]

The CWM for LifeOne is working fine.

Are the font used for the menu ixed point or scalable?

I found some problem regarding some string that make a wrong automatic wrap.

Is it possible to fix it? If the answer is yes can I post teh screenshot of this screens?
[Miscellaneous Android Development] :
The backup made with MTKDroid Tools has nothing to do with recovery. You need to learn to do the port "manually" following my guide. Many guys did it, so it is a working

method.

I just said few posts above yours that I won't do that anymore. Learn to use my guide or maybe some of the other users want's to do it in their spare time. I already shared all necessary information for anyone with a brain to do it.

I'm surprised you don't know yet that CWM fonts can't be modified in any way after it is built. If you want a different font you have to build it with that flag on BoardConfig.

If the recovery is working, compare this with your port and learn to do it by yourself.

Guys, all of you, with my threads (porting guide and both for porting recoveries) I teach you how to fish. Why then, you keep asking me to throw you a fish from time to time?
[Miscellaneous Android Development] bovirus:
Sorry but It's quite clear that don't want another font.

Infact I askied how you handle text strings and font.. I ddin'tr request a new font.

The scope of my question is to understand if it's variable font sieze font /(that depoend by display resolution) or fixed one.

Then if the automatic text wrap on the text string can depend also by display resolution.

I made an example from "Install zip menu" (based on LifeOne recovery)

------------------------------------------

choose zip from /s

torage/sdcard0

------------------------------------------

choose zip from /s

torage/sdcard1

------------------------------------------

installò zip from l

ast folder

------------------------------------------

installò zip from s

ideload

------------------------------------------

Toogle sihnature V

erification

------------------------------------------

Please take not about automatic wrap in the middle of the word.

The right one should be

------------------------------------------

choose zip from

/storage/sdcard0

------------------------------------------

choose zip from

/storage/sdcard1

------------------------------------------

install zip from

last folder

------------------------------------------

install zip from

sideload

------------------------------------------

Toogle sihnature

Verification

------------------------------------------

And if your are intersted there are situation like this in other menui
[Miscellaneous Android Development] :
I know what are you talking about and I answered you accordingly, but you don't understand what I'm talking about.

This is how cwm recovery fonts look like:

Every "font" means a size. When you compile the recovery you choose a size to fit the screen resolution. That can't be modified after build.

The truncate menu items is made by a calculation as you see here in my code:

#define ALLOWED_CHAR (int)([COLOR="Red"]resX*0.47[/COLOR])/CHAR_WIDTH
int ui_start_menu(const char** headers, char** items, int initial_selection) {
.....
strncpy(submenu[i], items[i-menu_top] + ALLOWED_CHAR - MENU_ITEM_HEADER_LENGTH, [COLOR="Red"]ALLOWED_CHAR-3[/COLOR]);
....

That operation is done automatically and I can't choose what to put on first line and what in second.

If there are other recoveries UI that do that I strongly advise you to start using those recoveries. In CWM based recoveries always you will see sometimes menu items incomplete because didn't fit in alocated space.
[Miscellaneous Android Development] Nihal @A-JAX:
Thanks for version 3.0 . Here is CTR v3.0 for LAVA Iris 310s !! But touch doesn't work . Well It may be due to cheap hardware.

http://xdaforums.com/general/general/v3-0-carliv-touch-recovery-lava-iris310s-t3010077
[Miscellaneous Android Development] :
Maybe, or could be because if the touch code, which is kind of old. I'm working on a new one, but it takes time.
[Miscellaneous Android Development] superdragonpt:
Works on Lollipop

Hi there, i Know LL is not supported...

After repacking this new CTR w/ New LL Kernel, + Small changes on init ... it's working in most functions ;)

(Using my own LL Rom, on dev. stage)

Awesome.

Thanks Again ;)

Regards