yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] yuweng:
:fingers-crossed:

When the tool detect SELinux then it'll abort . . . :D Its quite a complicated process restoring as i have no KitKat device to test so i disable it . . . :cowboy:

However, you can try the manual unpack/ repack, manually add sepolicy, seapp_contexts, property_contexts, file_contexts from VIbe UI ROM to the root of rmdisk . . .

Repack it then try backup/ restore & see if it works . . . :fingers-crossed: Fyi, KitKat ROM doesn't use old update-binary . . . :cowboy:
[Miscellaneous Android Development] SammaelAkuma:
CTR port for Alcatel OT 5020 and variants

Well, since I didn't feel like creating a new thread just to post a working port, touch controls and all, that I did next to nothing to get working properly. I figured I'd post it here (And here's to hoping yuweng doesn't mind that I do so).

Many of the Alcatel OT 5020(and variant) owners lack one major thing...the ability to make a FULL(Meaning custpack partition too) CWM compatible backup. Many have resorted to using MTKDroidTools to make a SPFlashTool compatible package. Well, here I am to save you the hassle of running to your computer every time something goes haywire and you need to restore to a working state.

Well, I'm only here with the result. yuweng and carliv are the masterminds behind the tool and the recovery.

As far as I know, this resulting recovery should work on ALL Alcatel One Touch 5020 variants. However, I only have an Alcatel One Touch 5020W to test on, but since I was able to boot a CWM port for an Alcatel OT 5020X on my phone, I can safely assume that it'd work on the X variant as well.

I will attempt to keep this as updated as I can with the release of each edition of the Carliv Touch Recovery and the AIO Porting tool with keeping the prior versions available as an archive of sorts, again, only if yuweng consents to it.

Sorry if this seems like thread hijacking. I don't intend it to be. Just sharing my working recovery to get more userbase for CTR and the tool.
[Miscellaneous Android Development] yuweng:
Thank you so much my friend for the feedback that it works for Alcatel devices . . . :good:

However, the proper place to share a working device list is actually here . . . :o
[Miscellaneous Android Development] razkal1:
Will this work on a huawei y530 it as a msm 8610 board... Could i port this recovery to it?

Thanks
[Miscellaneous Android Development] irfanjunaid:
Master, as per your request CTR has been successfully ported to Xolo Q900... Thanks for all your effort! I definitely owe you one...
[Miscellaneous Android Development] kuldeepraj:
This tool (ctrv2.4)is not working under Windows xp. Any solution.
[Miscellaneous Android Development] yuweng:
No <- As the title of this thread says . . . Yes <- You can compile it with the changes here accordingly to your device layout & delete this . . . :cowboy:

Refer to my BBQLinux thread & DIY or beg my Master Shifu Carliv & see if he will help compile one for your device . . . :fingers-crossed: :laugh:

Whoops, i've just shorten the codes from two lines to one, miss out the double-quote " " & it loops on XP, i didn't test it earlier . . . :o

Use this fix . . . :cool: Just replace it & it'll work . . . :cowboy:
[Miscellaneous Android Development] yao85930101:
Thanks for sharing your hard
[Miscellaneous Android Development] Kalpesh Sharma:
Tool to Port TWRP

Can u plz make a tool to port twrp 2.7.1.0 ?
[Miscellaneous Android Development] hanuma:
Yes, It would be nice a tool for Port TWRP 2.7.1.0 MT6582/92/95 , ZOPO ZP998 TWRP 2.7.1.0 http://xdaforums.com/showpost.php?p=53220610&postcount=755
[Miscellaneous Android Development] ptrVoid:
Hello, I tried to port the recovery for Jiayu F1 but the screen is upside down. Can you add an option to flip screen? Thanks.
[Miscellaneous Android Development] yuweng:
It has been mentioned few times on this thread, it won't work on your intermediate MTK device, don't believe me then try this . . .

After giving some thoughts to it & since TWRP all branch can be compile with jellybean source & it only takes 3 minutes to compile one & it'll work for all MTK device, fyi, i'm half-way working on it . . . :cowboy:

Again, this has been mentioned at the OP, porting tools problems report here & recovery features/ bugs report here . . . :rolleyes:

Fyi, it has to be compile with this flag & it takes 40 minutes to compile one for each resolutions on cm10.1, total 15 res multiple by ubifs multiple by custpack multiple by ext4 multiple by new lun path for latest MTK equivalent to . . .

40min x 15res x 3 type of filesystems(ubifs, custpack, ext4) x 2 lun path ≃ 3600 minutes ! ≃ 60 hours ! ≃ 2.5 days ! x 2 (normal & if add Flip screen) ≃ 5 days non stop !
[Miscellaneous Android Development] bovirus:
[MENTION=4478781]yuweng[/MENTION]

What do you mean for " intermediate MTK device"?

PhilZ recovery is OK for MTK device s with a recovery partition bigger than 6MB.

Is not so good for fevice with recovery partition max 6MB.
[Miscellaneous Android Development] yuweng:
meaning of intermediate . . . :cowboy:

In simple terms, PhilZ Touch & TWRP will only work on old MTK such as MT6573, 75, 77 b'cos its kernel is small & it'll just fits to its 6Mb recovery partition . . . :cowboy:

It'll also works on latest MT6582, 88, 92, 95 b'cos these devices has more than 8Mb of recovery partition . . . :cool:

While Intermediate MTK devices such as MT6589, 72 won't work & ported recovery will be oversize & when force install, some causes it to loose the IMEI & might lead to brick . . .

Conclusion : Use CTR that will work on all MTK . . . :laugh:
[Miscellaneous Android Development] bovirus:
I will post in the approporiate forum.

I tssetd your CTR recovery but didn't work in many Star/sesonn MTK6589/MTK6582 devices.

I tested both compiled version and I compiled it my self.

Star N9500 MTK6589 = lunpath1 (checked)

Tested Recovery 1.4 non touch (different font) - 1.4 touch.720x1280 - 2.4 1280x720result = not work

Installation via fastboot or MobileUncle

result= didn't work. The device seems boto in recovery bit after a blach diplay restar in normal mode

Star N9500 MTK6582 = lunpath2 (checked)

Tested Recovery 1.4 non touch (different font) - 1.4 touch.720x1280 - 2.4 1280x720result = not work

Installation via fastboot or MobileUncle

result= didn't work. The device seems boto in recovery bit after a blach diplay restar in normal mode

For bot phones I tried to compile myself the recovery.

Result= not possible why ro.secure=1

I tried also using MTK Droid and leave it open during CTR use.

The phoen is full rooted (MTK Droid green indicator).

I asked also to the MTK Droid autor to implement ro.secure=0 in default.prop.

Other users in italian forum made the same test with the same results.
[Miscellaneous Android Development] yuweng:
As mentioned a few times before, even its the same MTK SoC some porting works out-of-the-box while some require some tinkering . . . :cowboy:

Have you tried this . . . :cowboy:
[Miscellaneous Android Development] bovirus:
Already tested.

ls /system

app

bin

build.prop

build.prop.bak

data

etc

fonts

framework

lib

lost+found

media

mobile_toolkit

operation.log

res

secro

tts

usr

vendor

xbin

ls /system/etc

NOTICE.html.gz

ProjectConfig.mk

agps_profiles_conf.xml

apns-conf.xml

application

audio_effects.conf

audio_policy.conf

bluetooth

custom.conf

dbus.conf

dhcpcd

disableapplist.txt

drm_chmod

epo_conf.xml

event-log-tags

factory.ini

fallback_fonts.xml

firmware

fmr

geocoding.db

gps.conf

hosts

init.goldfish.sh

mddb

media_codecs.xml

mkshrc

mtk_omx_core.cfg

mtklog-config.prop

permissions

player.cfg

ppp

radvd

recovery-resource.dat

resmonwhitelist.txt

resolv.conf

ril

security

spn-conf.xml

system_fonts.xml

theme

throttle.sh

time

virtual-spn-conf-by-efpnn.xml

virtual-spn-conf-by-efspn.xml

virtual-spn-conf-by-imsi.xml

voicecommand

vold.fstab

vold.fstab.nand

wide-dhcpv6

wifi

xlog-filter-default

xlog-filter-tags

I made also all tries (also leaving open MTK Droid).

It's quite strange becaiuse other device withs ame chispet (MTK6582/89) works fine.

And also iot's quite strange that appear in the same way with the recovery compield.

If reloaded the old CWM 5.5.0.4 (without other changes) it worked.
[Miscellaneous Android Development] Kalpesh Sharma:
I have MT6582 Device

I have MT6582 Device with 480x854 resolution...

And I want to port TWRP 2.7.0.1...

Can u plz make a tool to port twrp or plz tell me how to port twrp 2.7.0.1 to my device manually ?
[Miscellaneous Android Development] farhantahir:
Hello [MENTION=4478781]yuweng[/MENTION] I have successfully ported carliv recovery v2.4 for coolpad 7295 (mtk 6589) but touch is not working again as it was also not working on v2.2. Is it device specific as I have tried different pcs for that.
[Miscellaneous Android Development] waulliano:
Guys, can anyone help me?

So guys am with this problem. The recovery in my Blu Studio 5.0E mtk6572 is upside down. Anyone know how to fix this problem? I appreciate all your help. Thank you! :good:
[Miscellaneous Android Development] bobo9900:
[MENTION=4478781]yuweng[/MENTION] , can you modify this tool to create recovery without the need to connect the device? is it possible?

I try mtkdroidtool, it was able to create cwm with boot.img and recovery.img from stock rom. It will easier for us to create custom recovery without owning the device. Thanks.
[Miscellaneous Android Development] m0han:
seeking help regarding twrp on ctr thread? have a heart! :D

request here after doing a full search. you might get twrp v2.7.1.0 even.

read this also.
[Miscellaneous Android Development] Kalpesh Sharma:
TWRP

[MENTION=4478781]yuweng[/MENTION] I have MT6582 Device with 480x854 resolution...

And I want to port TWRP 2.7.0.1...

Can u plz make a tool to port twrp or plz tell me

how to port twrp 2.7.0.1 to my device manually ?
[Miscellaneous Android Development] ptrVoid:
I asked because in the older version CTR v2.2 there was an option to flip screen and this worked for the Jiayu F1, but now the new version doesn't have an option.

Also, is there any tutorial for including the flag and building from source? I would like to try.
[Miscellaneous Android Development] yuweng:
Why there is a sudden surge of annoying n00bs & newbies at the development thread . . .

Guys, please brush up your knowledge first as most of your questions are already answered . . . :rolleyes:

i've just answered here & you ask twice & in spite of mohan telling you, you are at the wrong thread asking for TWRP, this is the CTR thread . . .:rolleyes:

Use the search & learn from Master Shifu Carliv, he has spent alot of time preparing it . . .

Again, already mentioned here <- CLICK TO SHOW CONTENT & you ask again . . . Fyi, many MTK device Touch is not working while at recovery . . .

Mentioned at the OP to read at least 5 pages from the back to know the latest news, again just mentioned here . . .

Why would anyone wanna create custom recovery for device they don't owned . . . Any users can just download the porting tool & DIY . . .

Fyi, its not so simple as you think, the porting tool uses adb to identify what you have on your device either ubifs, ext4, mtd, custpack detect what resolutions on your device & much much more . . .

What you need is learn is how to manual port, refer to here . . .

Refer to here & here & here . . . :cool:
[Miscellaneous Android Development] hadiyalkishan:
Hello sir, I have a mtk 6589t xolo q3000 with 4.4.2 kitkat os.

My stock recovery.imgs size is 6Mb and my stock boot.imgs size is also 6mb.

Is it possible to port ctr 2.4 in my device ?

Will my mobile support your recovery ?
[Miscellaneous Android Development] AndroTech:
Hi [MENTION=4478781]yuweng[/MENTION],

Will the current port tool work for CTR ver 2.5 or need some rework to support ver 2.5?
[Miscellaneous Android Development] yao85930101:
Carliv been updated Carliv Touch Recovery v2.5 hope [MENTION=4478781]yuweng[/MENTION] brothers look to follow up thank you very much

Version 2.5 update (29.06.2014):

- cleaned up the source code

- removed "wipe all" option from wipe menu (too many users wiped their system and blamed me); if you need to wipe system, use "format system" from "mounts/storage"

- rearanged menu order in root menu to restore CWM order

- added a "nvram backup/restore" menu in "carliv" section: the nvram partition will be backed up in clockworkmod/backup 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 of size 0x500000 (check your scatter) and if you have the nvram defined as /dev/nvram path 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.

- some other small changes.
[Miscellaneous Android Development] yuweng:
Guys, i can't keep up with all the different porting tools i've made, pls DIY if you want CTRv2.5. . .

The porting tool has everything & already given you all the info you need . . .

Step 1

If yours is emmc/ mtd refer to here & download your device res

If yours is custpack refer to here & download your device res

If yours is ubifs refer to here & download your device res

Step 2

Use the Unpack/ Repack recovery.img -> Unpack recovery.img, copy downloaded CTRv2.5 Eg: port_CarlivTouch-recovery-2_5-480x854.img & rename it to recovery.img & press OK

Goto CTRv2.4\UnpackRepack\recovery\rmdisk & copy whole res folder out

Goto CTRv2.4\UnpackRepack\recovery\rmdisk\sbin & copy the binary file named recovery out

Step 3

Use the Unpack/ Repack recovery.img -> Unpack recovery.img again to unpack the earlier working CTRv2.4 recovery.img for your device

Delete res folder & replace it with res from CTRv2.5

Replace recovery from CTRv2.5 to sbin

Manual edit CTRv2.4\UnpackRepack\recovery\rmdisk\etc\recovery.fstab with Notepad++ & add the below accordingly

/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/uboot emmc /dev/uboot
/nvram [COLOR="red"]emmc[/COLOR] /dev/nvram[COLOR="Red"] <- Add this new line[/COLOR]

[B][COLOR="Blue"]OR[/COLOR][/B]

/nvram [COLOR="Red"]mtd[/COLOR] nvram

Use the Repack recovery.img & let it auto-install the new CTRv2.5 to your device, thats it !
[Miscellaneous Android Development] AndroTech:
Followed the steps but the created recovery didn't work.
[Miscellaneous Android Development] iZLeeP:
Thanks for another way of manually updating carliv recovery. However, in my case, I do it the other way around. I just copy the necessary files from my working CTRv2.4 to CTRv2.5 (e.g., recovery.fstab, default.prop, ueventd.rc, kernel image, etc.) and repack the latter.
[Miscellaneous Android Development] CODE_WORKX:
Master recovery was successfully created and also it was flashed perfectly

The Recovery booted and also everything was fine...

Just a thing that when flashing something the updater script lines are exceeding the resolution which was not before

other than its perfect :good::D
[Miscellaneous Android Development] Exaxoid:
upside down

I bought a like the samsung galaxy sg5 mtk6572 and installed recovery image but it boots upside down can someone help me please
[Miscellaneous Android Development] droiddeb:
I am also facing the same issue. It happens in mt6572 devices, I guess.
[Miscellaneous Android Development] bovirus:
[MENTION=538497]yuwen[/MENTION]

Could you fix the 1280x720 resolution (use automatic mode) with anew version?
[Miscellaneous Android Development] yuweng:
You already know how to manually port it why would you want the porting tool anymore . . . :cowboy:

If you have read 5 pages from the back then you would've know the latest story, it's here & its also hightlighted at the OP too
[Miscellaneous Android Development] vfan3388:
MTK 6595 device

Hi I just bought a mobile name Q1, it is MTK6592+MTK6595 .It does not work on your pool tool. just fyi, still working on install recovery.
[Miscellaneous Android Development] SkandaH:
[MENTION=4478781]yuweng[/MENTION]

Thanks for making this wonderful piece of code! Works perfectly on Micromax Bolt A46.

Here is mirror of the ported & stock recoveries: https://mega.nz/#!YlQEwRoK!WmXU6C2KrJ6DLbMnQzFUfzpKicm0kwXFymqmAjPxCNU
[Miscellaneous Android Development] AmINoS007:
i have done all the steps with replacing recovery and res etc from CTR 2.5 to 2.5 and repacked succesfully

but when i nstall the recovey when the phone reboot i find its 2.4 CTR and not 2.5 .. what could be the mistake and any suggestions pls :confused:
[Miscellaneous Android Development] Mahesh90901:
Please tell me how can i fix the problem when i try to mount or enable touch it says Cant mount sd card my mobile does not have external sd card it used internal storage
[Miscellaneous Android Development] syon.piyush:
Spice mi-436 strange problem

GO TO THIS LINK TO SEE MY PROBLEM

http://xdaforums.com/general/help/help-spice-mi-436-boot-loops-t2838098
[Miscellaneous Android Development] dockers:
The buttons and points of touch are misaligned on Karbonn TA-FONE 37

The buttons and points of touch are misaligned on

Hardware : MT6577

Model : Karbonn TA-FONE A37

Build number : ALPS.JB.MP.V1.16

Display: 480*800

See the attached picture.

Any ideas to fix this?
[Miscellaneous Android Development] dhampire:
Normal CWM

Master, Thank you for your great jobs.

Can you arrange this Carliv Touch Recovery for MediaTek devices to "make normal CWM" ?

If we do it, how to ? Please advice us.
[Miscellaneous Android Development] yuweng:
Fyi, no DEV has worked on the latest CWM sources to make it compatible with MTKs & furthermore koush has left cm team . . .

Why "make normal CWM" when CTR is PROVEN to be better for MTK devices . . . :cowboy:

If you want then use this but its not compatible for older devices as it uses the latest lun path for CWM . . .
[Miscellaneous Android Development] grungemann:
My phone is running on 4.4.2. Can I build a carliv backup with it?
[Miscellaneous Android Development] m0han:
if you meant carliv recovery backup, ctr is for "devices with kernels up to Android 4.3. It won't work for kitkat." more here in large red letters.
[Miscellaneous Android Development] neodrift:
Can somebody please help me with this Flip Screen issue? Although everything works fine im having problem flashing rom, when i flash new rom its also Flip like my recovery. Attached is my recovery.
[Miscellaneous Android Development] KunalKene1797:
<<<RECOVERY PARTITION IS ONLY 6MB HEAD OVER HERE >>>​

MT6572​

http://xdaforums.com/showpost.php?p=55160827&postcount=100
[Miscellaneous Android Development] KunalKene1797:
Its not anyone's issue!:silly: the screen of your phone was put upside down and code in the ROM was used to make it straight...so what you can do is Compile the Recovery on your OWN! and Install the Stock ROM!:silly:
[Miscellaneous Android Development] Q9Nap:
so how do you unpack system.img?

i successfully unpacked the mzf using mtk, but none of the tools that work for most moto system images work to extract the system image.

i've tried imgextractor, simg2img, and unyaffs2.

*edit*

as for unpacking/repacking boot.img and recovery.img, Android-Kitchen works great: https://github.com/dsixda/Android-Kitchen
[Miscellaneous Android Development] yuweng:
As mentioned here, MTK Motorola is the worse of all or shall i say the best of all at ensuring that it stays as stock ROM at all time, once you mod it then it'll brick & you have to use RSDLite to download back the original Factory ROM then only it'll boot . . . :cowboy:

i don't see the point for you to move forward unless you have found a way for custom recovery to work on your MTK Motorola . . . :cool:

adb shell su -c "tar -cf /mnt/sdcard1/system.ext4.tar /system"

OR

adb shell su -c "tar -cf /mnt/sdcard2/system.ext4.tar /system"

Refer to here onwards for MTK Motorola custom recovery progress . . . :cool:
[Miscellaneous Android Development] Q9Nap:
Thanks for the reply! The above method requires having the device to pull the system; there are many ways to do that.

"adb pull system" is probably the easiest

You can also use the on-device make_ext4fs binary to make a nice sparsed system.img

I want to know how to dump the system.img created by opening the *.mzf file with mtk.

The recovery.fstab specifies that it is ext4, but linux will not mount it.

It is in some proprietary format I think, and different from other moto system.img files, because the standard extraction tools don't work...
[Miscellaneous Android Development] yuweng:
As mentioned & AFAICR, existing tools available doesn't work on MTK Motorola & nobody wants to work on it & nobody ever share the solutions . . . :rolleyes:

(fyi, i don't own a MTK Motorola yet i download RSDLite & tried porting recovery for it . . . )

If you have read the previous link, the progress stops at using SP Flash Tool instead of RSDLite . . .
[Miscellaneous Android Development] derkvol:
Is it right in step2 CTRv.2.4 or must be CTRv2.5?
[Miscellaneous Android Development] yuweng:
its so obvious & still you don't get it . . . :cowboy:

Step 1 - Download compatible CTRv2.5 according to your MTK filesystems

Step 2 - Unpack Step 1 & copy out the res folder & recovery binary

Step 3 - Unpack the working CTRv2.4 that you ported earlier & follow below Step 3
[Miscellaneous Android Development] derkvol:
I did it 2 days ago, but , i think, in step 2: line 2 and line 3 is wrong (must be CTRv2.5). It's mistake. Pls, change it for someone else:D
[Miscellaneous Android Development] yuweng:
There is absolutely no error, this shows that your English Reading and Writing skill definately got problem . . . :cowboy: i have already mentioned clearly at that post that i won't be making CTRv2.5 Porting Tool b'cos i can't keep up & its so easy for existing users to upgrade it themselves . . . :cool:

My advice for Non-native English speaker, pls read & continue reading it a few times then you'll understand or use google translate . . .
[Miscellaneous Android Development] bovirus:
[MENTION=538497]yuwen[/MENTION]

I experimented some problems using Carliv tools and your TWRP tool in some pc's (of my friends) with different configuration (Windows7/Windows8/XP) with different antivirus (AVG, Avira, Avast, etc -always disabled).

No error but the recovery didn't work (didn't start).

On other pc with the same software it worked fine (my pc).

It's too complicate make a proof test to understand wht was happend.

For this I asked if it's possible to have the instruction how to port manually TWRP on mediatek device.

Carliv made a detailed Guide how merge his archive of recovery wiyth specific device recovery.

Could you do that?
[Miscellaneous Android Development] yuweng:
Bro, in spite of me explaining it here & here & now you come to this thread asking for the same thing, this is Auto-Port CTR thread NOT manual-port TWRP . . .

You have problems with manual porting try discussion thread here or here . . .

Since you didn't get the message, i'm going to speak very frankly to you now, it tooks me almost two years to learn all about the three generations of MTK SoC, each of the porting tool consist of close to 3000 lines of codes which is automating the manual porting process, now why do i need to share what i learn from scratch, nobody teach me all these, all self-taught, nights after nights of codings the software, experience gain from trial & error, trouble-shooting, reading & continue reading threads here at XDA & elsewhere, learn to compile recovery from source, i have to compile six times with all the optional build flags to make TWRP porting tool & fyi, i pm'ed more than eight DEVs asking for advice compiling from source, guess what only my Master Shifu Carliv guided me all the way & fyi, the Thanks meter that you see now, almost half of it is from him, i should be thanking him but instead he thank me back . . .

Now as mentioned previously, there are too many things & its too complicated to explain, learn to compile TWRP look at the source code then you'll know how it works & thats all the pointers that i can give to you . . .

If you have trouble setting up the BE then refer to this thread . . .

Good Luck . . . :cool: