yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] gls9:
When I use the scripts for TWRP-V2.3.2.3 on windows this gives some problems.

It failed with a message access denied. I end up with a directory rmdisk in recovery dir which cannot be removed anymore in a normal way. Only when taking recursive ownership I can delete it.

When debugging I see the following:

F:\download\michfood-TWRP-V2.3.2.3\recovery>F:\download\michfood-TWRP-V2.3.2.3\bin\chmod og=xr rmdisk

F:\download\michfood-TWRP-V2.3.2.3\recovery>cd rmdisk

Access denied.

So it looks like something going wrong with rights after chmod.

I'am using windows 7 64 bit.

Edit: it is working when starting with cmd box as administrator and call the bat file from commandline. When dragging in explorer it won't work here.
[Miscellaneous Android Development] yuweng:
Haha, never did test it on x64...

Thank you so much for sharing this info...

Updated with 320x480 support, ported over from other devices... ;)
[Miscellaneous Android Development] sihag:
Moving to the original thread.
[Miscellaneous Android Development] yuweng:
Yeoh bro, i have said this many times, please give very detail specific explanation as this mod has evolve alot since Rev 1 & i don't even know which mod you are talking about... There is Android Kitchen plugins for cygwin version, ubuntu version, standalone ubuntu script, lately Master Shifu Michfood version & you're not even mentioning if its for MT6573 or MT6575/ 77, cwmr or TWRP...

However, from your feedback above, that is not even from this thread, its from here...

i have already spend alot of time doing all those tuts/ guides by screen capturing it step by step as though i was setting up it for the first time, there is no way it fails unless you didn't read all those pdfs files...
[Miscellaneous Android Development] balamu96m:
Yuweng bro, I just ported ClockWorkMod Recovery Touch v6.0.1.1 to our Spice Mi-350n !! Could be the first ever for MTK6573?? !! :good::good:

Screen Shot:

Video:

[YOUTUBE]UxL0oZOvCbA[/YOUTUBE]

Currently testing it...Will upload soon !!
[Miscellaneous Android Development] yuweng:
Yeoh Bala bro,

Actually, ported that one from builder.clockworkmod.com awhile back ago, guess you didn't checkout my thread here... :o

Unfortunately, builder now uses JB sources so latest build doesn't work correctly on our device anymore & it doesn't even work on latest HTC too...
[Miscellaneous Android Development] balamu96m:
Oh...by bad..i didn't see... :eek: :confused:
[Miscellaneous Android Development] darkangel1016:
I had the same problem win 7 x64. The tool creates a folder whose security is not same as the one who starts the batch file. so the tool fails to create a recovery.img file at the end as the access to the intermediate folder is denied. the folder cannot be deleted untill the security is reset using the folder security options. i had to use another machine to run the batch file successfully to get the recovery. yet to test the file.
[Miscellaneous Android Development] Mawe79:
hi yuweng

first thx for you work.

i have tried to get CWM to my MTK6577 with this Method:

http://www.mediafire.com/view/?ue1rctqb66foz6k

it seems to work, but......

first what have i done:

i copy my (stock) recovery into the bat file....process is running...type "2" for 6577, done!

A new folder named "revocery" appears. In this folder there is a "recovery.img" and some other files.

seems to work..

flash recovery (which found in new createt folder) with sp into phone, tried to open CWM....but there is no CWM...

hmmm....

do i need something else or did i something wrong? patched boot?
[Miscellaneous Android Development] yuweng:
Many has tried & reported back that they manage to port it successfully so my best guess is that you have earlier Drag & Drop before & you didn't delete the recovery.img at michfood folder then ported recovery.img will not boot... :o

And the ported recovery.img should be at michfood folder & NOT at recovery folder... :p

Are you using my earlier mod as those doesn't auto clean-up extracted files & folders... :D So you need to manually delete recovery.img & recovery folder before Drag & Drop again...

i only found out that bug after discovering that TWRP does work on MT6575/ 77 so i only fix it on TWRP mod... :o
[Miscellaneous Android Development] Mawe79:
ok again....in extended Version xD

extract the file "michfood.7z"

it appears folder in the createt folder a folder names bin, and two files, "cwmr6015.bat + MTK_pack.bat"

- drag stock recovery into "cwmr6015.bat"

- cmd prompt appears and skript runs; than type "2" for MTK6577

- a folder named "recovery" appears...inside this folder there is a file named recovery.bin and some other files

inside first folder "milchfood" is no other file!!

and i flashed the recovery,bin which i found in the new folder, but you say that this was wrong, so i think it doesn't work for me....uses Windows 7 x86
[Miscellaneous Android Development] Mawe79:
i me agai. I tried now TWRP (http://www.mediafire.com/view/?ixb8v2438mnofay)

and nearly same failure as using CWM

when both datas (recovery and folder) are on partition c: the programm starts, than it's interrupt with message that he can't find xxxx

when i do same thing on other partition for example d: the programms runs completly (CMW press 2 for MTK6577, done ; TWRP press 3 for MTK6577 and than 4 for qhd, done)

both times i get message done, but no recovery.img file appears in folder?!?

I know you have sent me file and thx :) , but want that this will work too? Any idea?
[Miscellaneous Android Development] falcaobr:
e1909c_v77_jbl_9p017_6628

Gentlemen, could someone let me know which CWM and installation method for this MT6577: e1909c_v77_jbl_9p017_6628

Thank you.
[Miscellaneous Android Development] abhishek 9650:
hey i want to how you did it and will it also work on my mtk6572 device with android 4.2
[Miscellaneous Android Development] lopestom:
I sent you a PM...
[Miscellaneous Android Development] abhishek 9650:
plz help me

my device is spice mi436 which have mtk 6572 processor . and jb 4.2 please tell me to install recovery on my device plz suggest me a safest way i have bricked my phone 2 times
[Miscellaneous Android Development] cyberangel22k:
sorry for this very noob question [MENTION=4478781]yuweng[/MENTION] my friend. The list of the recoveries fro philz, doesn't include armv7. is it not supported yet? I wanna try to port it.:p

BTW, I haven't share all the ports i did for several devices. I wanna share it in master [MENTION=5186178]carliv[/MENTION]'s thread but found out it's already closed. Too bad.:eek:

Anyway, I will just post may public dev host link here. Users can find the TWRP, CTR with custpack, and all the roms for Alcatel One Touch S'Pop/Glory 2 4030E. Some reports it works in some other variants like 4030A,D, and X. but some report white screen. For those who get, white screen, You can PM me and send the stock recovery so I can fix it.:D

Big thanks to Master [MENTION=4478781]yuweng[/MENTION], Master [MENTION=5186178]carliv[/MENTION], and Master [MENTION=5119815]rua1[/MENTION] for teaching me a lot of stuff.:good:

EDIT: found out, armv7 is cortex A9. :))
[Miscellaneous Android Development] farhantahir:
REQ] Philz for spice mi 515 /CoolPad 7295.

Hello could you please port philz for spice mi 515 as it has every spec similar to a116 except resolution. I could provide you the stock, cwm v5 and ctr 2.2

If not please upload your one as it will be very easy for me to port philz then.

I'm somewhat noob at these things so please teach me. I will be very thankful to you.
[Miscellaneous Android Development] farhantahir:
Guide for philz recovery.

Hello [MENTION=4478781]yuweng[/MENTION] I think you should create a small guide to port philz recovery not step by step but a small guideso every matter could be found in one place instead of saerching the posts for an error. Please.
[Miscellaneous Android Development] cyrillem28410:
Hello

Thanx for this useful tool.

It seems to works for my iOcean but is a file has been created ? I would like to share this recovery but didn't find if a file has been created

Thanks
[Miscellaneous Android Development] yuweng:
Its already stated at the OP & you seems not to understand it then you'll have to brush up your knowledge first . . . :cowboy:

Fyi, this is a development thread & i got few pms too, confirming ported PhilZ Touch is working on various MTK devices . . . :cool:

Again, all info is stated at the OP you just gotta read it all, my friend . . . :cool:
[Miscellaneous Android Development] EnerJon:
i Successfully Ported PhilZ Recovery To My Qmobile-A900 (Elife-E3 Clone) Same Device As Yours...

1) i Removed "adbd" - "fb2png" - "mount.exfat" - "parted"

2) i Compressed PNGs Using tinypng.com This is An Amazing Online PNG Compression Site, Visual Loss is ZERO, But The Output File Size is EXTREMELY SMALL...

3) i Moded Sir [MENTION=2117836]michfood[/MENTION]'s Boot/Recovery UnPacker/RePacker Tool To increase Compression Ratio (instead Of GZIP Commandline Tool i Used 7zip Commandline Tool in GZIP Mode)

Open "MTK_pack.bat" in Sir Michfood's UnPacker/RePacker Tool Using Text Editor... And

Replace This Line

%~dp0bin\gzip -n -f ../ram_disk

With This

%~dp0bin\7z a -tgzip -mx=9 ../ram_disk.gz ../ram_disk

Now Your Newly Repacked Recovery.img/Boot.img Will Be More Than 100KB Smaller Compared To Previously RePacked Boot/Recovery... Try it (Y)

Hello [MENTION=4478781]yuweng[/MENTION] Brother, First of All, i Would Like To Thank You For Compiling PhilZ Touch Recovery For MTK Devices, i Started Learning Android From Your Threads... i Can Tell You PhilZ Recovery is Working Perfectly Fine in My Qmobile-A900 (MT6589) But Just a Small issue... First Time i Saw This Problem in TWRP-2.6.x & TWRP-2.7.x Compiled By Sir [MENTION=912474]Dees_Troy[/MENTION] For OPPO-R819 And Now in PhilZ Touch Recovery 6.27.x By Sir [MENTION=4666971]Phil3759[/MENTION]

The Problem is, Whenever i Make/Restore Backup in TWRP-2.6.x & TWRP-2.7.x Or Whenever i Enable "TWRP Mode" in Nandroid Backup Settings Of PhilZ Touch Recovery And Goto Make/Restore Backup, it Tries To Make/Restore Backup From a Folder With This Name "0000000000000000"

After Checking Recovery.log, i Saw This...

I:Checking cmdline for serialno...

I:Checking cpuinfo...

I:=> hardware id from cpuinfo: 'MT6589'

I:=> Using cpuinfo serialno: '0000000000000000'

I:Checking needed space for backup '/storage/sdcard0/TWRP/BACKUPS/0000000000000000/2014-05-02.00.16.22_SV1.0'

And Then i Used This Command (cat /proc/cpuinfo) in Terminal... And This is What i Saw...

shell@android:/ $ cat /proc/cpuinfo

cat /proc/cpuinfo

Processor : ARMv7 Processor rev 2 (v7l)

processor : 0

BogoMIPS : 2439.94

Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt

CPU implementer : 0x41

CPU architecture: 7

CPU variant : 0x0

CPU part : 0xc07

CPU revision : 2

Hardware : MT6589

Revision : 0000

Serial : 0000000000000000

shell@android:/ $

So, This "0000000000000000" Should Be The Serial Number Of My Device... But Don't Know Whats Happening Here... Any Clue? :confused:

i Never Faced This issue With TWRP-2.5.x

Maybe Because it Uses "ro.product.model_ro.hardware" (For Exapmle sdcard0/TWRP/BACKUPS/ZTEv970_MT6577/)

instead Of "ro.serialno" (For Example sdcard0/TWRP/BACKUPS/123456789ABCDE/)

i Even Tried Setting This Property "ro.serialno=123456789ABCDE" in default.prop inside Rmdisk, it Still Shows 0000000000000000 in Recovery Mode...
[Miscellaneous Android Development] agismaniax:
interesting steps. could you share your recovery.img in here? my previous attempt is not booted up, but the size is 6118KB.
[Miscellaneous Android Development] yuweng:
You seems to know alot about TWRP my friend . . . :laugh: It has to be compiled with this flag then only it'll work if not then it'll show all zero . . . :cowboy:

PhilZ Touch has this flag too but i never tried it until you brought it up . . . :cowboy: Refer to here for further updates . . . :cool:
[Miscellaneous Android Development] KopiJahe:
[MENTION=5694739]EnerJon[/MENTION]

The easiest way (IMHO) to change your serial no in TWRP is by editing you init.rc from this:

write /sys/class/android_usb/android0/iSerial ${ro.serialno}

to this:

write /sys/class/android_usb/android0/iSerial "My Serial No"

for example:
write /sys/class/android_usb/android0/iSerial "N986"

btw, I used this additional build flags to compile TWRP for several MTK-based phones that uses 6MB recovery partition:

TW_USE_TOOLBOX := true
TW_EXCLUDE_SUPERSU := true
BOARD_HAS_NO_REAL_SDCARD := true
TW_NO_EXFAT_FUSE := true
TW_NO_EXFAT := true
TW_INCLUDE_CRYPTO := false

And after compressing (and sometimes redrawing and changing) the images, I stayed below 6144 KB limit

You can also -but not recommended- use separated ui.zip to remove res folder from recovery.img, just compress res folder's contents, rename it to ui.zip, and place it in <your internal memory>/TWRP/theme/ui.zip (But remember not to wipe your internal storage, or you won't able to enter TWRP)

you can see the result here. This phones uses the new "datamedia" partiiton layout, so it may not 100% compatible with normal MTK devices that uses 2 separate internal partitions.
[Miscellaneous Android Development] EnerJon:
Here You Go... Qmobile A900 (Elife E3 Clone) PhilZ Touch Recovery 6.27.4 Download Link

Thanks Brother, But i Don't Know How To Compile Recovery... i Have MTK Kernel Compilation Experience But Never Tried Recovery Compilation... i Just Checked That Commit And if i Recall Correctly, That TWRP-2.5.x Was Compiled By [MENTION=3339772]Javu[/MENTION]m... So This is Why We Never Saw This issue in TWRP-2.5.x... But Don't Know Why Sir [MENTION=912474]Dees_Troy[/MENTION] Didn't Set This Flag (TW_USE_MODEL_HARDWARE_ID_FOR_DEVICE_ID) To True While Compiling TWRP For OPPO-R819...

BTW Thanks For Compiling And Fixing This issue in Latest PhilZ Recovery 6.40.x :o

Thanks Brother, i Have Already Tried it in PhilZ Touch Recovery, But it Didn't Worked...

First i Changed This in init.rc

]write /sys/class/android_usb/android0/iSerial "12345ABCD"

And Then Executed This Command in Terminal To Verify cat /sys/class/android_usb/android0/iSerial

it Showed Me This "12345ABCD" Which Means it Worked, But When i Tried To Make/Restore Backup, it Was Stil Looking For Backup in "0000000000000000" Directory :rolleyes:

i Even Tried This (setprop ro.serialno 12345ABCD) in init.rc But it Didn't Worked Either...

BTW Thanks For Sharing Additional Build Flags To Compile TWRP For Devices Having Small Size Recovery Partition :o
[Miscellaneous Android Development] yuweng:
AFAIK, Dees_Troy don't even own a R819 & out of presumably 10K unit of R819 sold (should be more than that), 0.1% = 10 person is a DEV BUT not even one committed this flag here, thats the android community today . . . :rolleyes:

As for my case i don't even own a MT6592 & i'm sorry to say, nowadays i couldn't even be bother to drop by those thread to offer my help, got ignored completely & totally unappreciated . . . :rolleyes: Fyi, to compile PhilZ Touch from source for a new device, it took 45 minutes to complete, better for me to spend my time else where . . . :rolleyes:

Thats what Phil3759 says, to maintain compatibility with Philz Touch & TWRP on MTK it will show all zero BUT most importantly it works when you rename it to all zero with the correct device folder name as PhilZ Touch . . . :laugh:
[Miscellaneous Android Development] EnerJon:
Thanks For Taking Your Time To Reply Me Brother :) We Really Appreciate Your Hard Work... Your Threads Are The First Place From Where i Started Learning Android Stuff... Without Your Efforts We Might Not Be Able To See Latest PhilZ Recovery 6.x in Our MTK Devices... Keep Up The Good Work ^_^
[Miscellaneous Android Development] betaman69:
HTM H10

Hi,

I have a HTM H10 mtk6572 ubifs phone.

When I try to run ctr2.2 for ubifs I get the message "error detected.cannot unpack recovery.img"

I also tried manual option with a recovery.img that I have obtained using MTK droid tools backup but the message remains the same.

I am correctly rooted (link2sd and root explorer works perfectly) and bussy box is installed.

Can anyone help?

P.S. When I use the MTK_unpack.bat from Unpack_tools the unpacking is successful.
[Miscellaneous Android Development] farhantahir:
During manual porting use your stock recovery not modified cwm by mtk Droid tools.

It would be better if you use a pc running Windows 7 or earlier not windows 8/8.1 as it has changed permission policies.
[Miscellaneous Android Development] betaman69:
I got the recovery.img using the backup function of the MTK droid tools. Is there another way to do it? I'm using windows 7 x64
[Miscellaneous Android Development] farhantahir:
Which recovery is currently flashed.

Since you are backing up using mtk Droid tool it will also backup the cwm flashed in your phone. I said to use stock one as mentioned in op. So google for your phone's stock recovery.
[Miscellaneous Android Development] betaman69:
I never installed a CWM on the phone I'm still with 3e and also I can't find a stock rom for my phone anywhere.
[Miscellaneous Android Development] TechBurner:
I have a chinese s4 clone with mtk 6575 . Whenever i run the tool it says that you can only port this on mtk chipset.

Is there any way i can do it?
[Miscellaneous Android Development] farhantahir:
Most important you are not running a mtk based phone and that is what that dialog box says to you. Learn more about your phone.
[Miscellaneous Android Development] TechBurner:
I know everything about my phone it is running mtk 6575 . if you don't have the answer plz don't mess around
[Miscellaneous Android Development] gatgat23:
Got a S4 Mini Clone. I used the tool but after rebooting to recovery, recovery ain't loading.

Just a black screen. Nothing shows up.

Tried auto and manual port which both used stock recovery.

It's SoC is MTK6572 (real) but most of the programs/apps detect it as MTK6589 which is fake in default .prop files.

Any help will be appreciated as I also need to flash gapps because Google Play services ain't working.

Thanks.

EDIT: UBIFS filesystem. :)
[Miscellaneous Android Development] yao85930101:
Carliv Touch Recovery v2.4 came out of a wish to free tools:good:
[Miscellaneous Android Development] ladalgigi:
Port tool update

Hi Yuweng

I just wanna know if you're going to update your tool with new CTR v2.4 ?

thank in advance

ladalgigi :confused:
[Miscellaneous Android Development] farhantahir:
It's already been updated you should read the op. It's just a typo by yuweng that he has by mistake written 1.4
[Miscellaneous Android Development] iZLeeP:
Have you used the porting tool? It's not typo error. Version 1.4 is actually 1.4 (non-touch module) carliv recovery which is different from the 2.4 version which is full touch.
[Miscellaneous Android Development] prynxx003:
hi, please is there anyone who can help me port CTR manually? I have stock boot.img and recovery.img but I dont have the phone in hand. It's mt6572 ext4. I hope there's someone who can help me.
[Miscellaneous Android Development] iZLeeP:
Check the OP, thread is now updated with the tool to port automatically CTR v2.4
[Miscellaneous Android Development] anandisrocking007:
Hi i have an Auxus Nuclea X Cell from Iberry and it has the following specs in the picture posted below its an octacore and has an mtk 6592 processor can the twp recovery be created by the following tool.......i am slightly of a noob in recovery creation and would like to be double sure before doing anything hope you can help:mad:
[Miscellaneous Android Development] irfanjunaid:
Master, will you please create one for Xolo Q900....! It's a mt6589 device....
[Miscellaneous Android Development] surfturtle:
720x1280 Resolution is Missing in CTR-v2.4

i think you forgot to include 720x1280 Res

could you please update the tool?
[Miscellaneous Android Development] bovirus:
Carliv Recovery already compiled

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

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

http://xdaforums.com/showthread.php?t=2471479
[Miscellaneous Android Development] yuweng:
This tool will port Carliv Touch Recovery only . . .

Download & DIY thats why i created it at the first place . . .

Workaround : Use Manual mode & select 720x1024 . . .
[Miscellaneous Android Development] AndroTech:
Master [MENTION=4478781]yuweng[/MENTION],

Your tool is awesome. I used it to port 2.4 for my device. I have one question - Can I set the font size of the recovery in manual port?
[Miscellaneous Android Development] bovirus:
[MENTION=538497]yuwen[/MENTION]

For a clean asistance of the user on the first update please add also standard resolution 1280x720.

Until you will add resolution 1280x720 please add in teh first post the workaround about 1280x720 resolution.

Thanks.
[Miscellaneous Android Development] yuweng:
Unfortunately no, it has to be compile with this . . . And there are math for defining this corresponding to the selected font size & screen size, its not so simple my friend & i almost forgotten what my Master Shifu Carliv has taught me, i hate math . . . :laugh:

However, you can try manual mode & choose other resolutions, it might suit your needs . . . :fingers-crossed:
[Miscellaneous Android Development] AlexZap:
I am having an issue with my backup. I don't know if it is an issue with the way it was created, or if it is my phone. I used master yuweng's auto port tool to port to my phone, a star n9002 note 3 clone. Chipset is mt6582, screen is 786x1024. The port was successfully, and installed and runs fine (I LOOOOOVE having the aroma file manager access). But when I run a backup, everything succeeds without an issue, but when I look at the files, all the .tar files are 0.0 bytes, and empty. Then there are files like "system.tar.a" that look correct, and are fine tar files. I don't know if I could successfully restore one of these, and luckily I haven't had to try. But when I use the "online nandroid backup" app, all the .tar files are fine, and there are no .tar.a files (are they temp files?) Maybe I'm just being stupid, but I want to make sure the backups are correct.
[Miscellaneous Android Development] yuweng:
Fyi, CTR has been PROVEN to work on many MTK devices BUT as usual make a backup x3 and this has been mentioned many times at this development thread . . . :cool:

My old tut for ref here . . . :cowboy: Better to be safe than sorry . . . :fingers-crossed:

This version i've intergrated all ubifs, ext4, yaffs, custpack, old lun & new lun AIO so there might be bugs, idk . . . :fingers-crossed: Again, as mentioned at the OP, try the unpack/ repack & check the recovery.fstab if its the correct format for your device . . . :fingers-crossed:

On my device, backup system.ext4.tar is 0Kb while system.ext4.tar.a is 324,724Kb & backup/ restore works fine . . . :cowboy:

Any CTR related issue report here while porting tool here but many do it the other way round . . . :silly:
[Miscellaneous Android Development] djixon:
Hello good.

I'm trying to carry carliv Elephone P8 is mtk6592

I have proven with the stock recovery.img but I installed the stock recovery.

I have proven to version 2.4 making it with the file from your computer, unpack and repackage since from the mobile do not **** me (weird because if flashtools and other programs).

As carliv could carry this phone?

Thanks in advance!
[Miscellaneous Android Development] surfturtle:
Support for KitKat ROMs like Lenovo VibeUI / VibeROM

Your CTR tool has been working great with all MTK phones except the ones running KitKat. I tried on Lenovo P780 with VibeUI ROM v1.5 and the CTR tool said that it does not support KitKat roms.

Futhermore I downgraded to JellyBean and created recovery through CTR and then upgraded to KitKat but the recovery created under JellyBean is not compatible once the phone is upgraded to KitKat. The recovery boots fine but when I try to install gapps it gives an error that there is Insufficient Storage on system partition. The partition has about 1.5GB free so the error must be due to something else.