Root [INFO]CWM Flashable.zip

[mavrikmeercat]

It seems we need a CWM flashable.zip for the Transform Ultra so, I decided to make a thread so we can all bring info to one place in order to give the whole community a place to learn. I’ve done quite a bit of research on this and have found bits a pieces on how this works. Please post back whatever you find? Links, files, info, or whatever..

Note: I am not just giving info on this. I am also seeking info. I am attempting to request a community wide effort to gather info so it's available for everyone so please help us out and post some useful info, testing, and discussion on the subject. I will update everything relevant or proven in the OP as it becomes available and give credit where it's due.

Here is what I’ve got so far…

CWM.zip FILE STRUCTURE:

The System and Data Folders must go in the root of the ROM_name.zip and are pretty self-explanatory as to their target on the device. /system and /data.

The META.INF folder is where CWM looks to validate if the .zip is in the proper format, if it’s signed, and how to push/write the above files to their intended places on the device through a binary-script language written for CWM.

Updater-script, located in META.INF/com/google/android is not to be confused with update-script. There are two different versions of this language. The original binary called Amend, uses the update-script language and was created for Clockworkmod versions prior to version 3. The upgraded binary called Edify, uses the updater-script language. It is based on the original binary but is more advanced and allows for more options when flashing the .zip. Edify was created for Clockworkmod versions 3 and above.

I have found a few useful guides on the updater-script commands:
http://www.synfulgeek.com/main/index.php/articles/76-scratchpad-documenting-edify-commands-for-android-updater-scritps-based-off-of-kernel-source-code

[TUT]Edify Installation Script Syntax's - xda-developers

http://www.freeyourandroid.com/guide/introdution_to_edify

If you’re running Windows, you cannot use notepad or wordpad to edit/create the scripts. They won’t work. I’m sure there are lots of others that do this but it seems the most common one is notepad++

If you are running Ubuntu, then the built-in gedit will do perfectly…

CERT.RSA, CERT.SF, and MANIFEST.MF are files related to security and test keys for the validation of the CWM.zip and are created when you create the .zip and go through the signing process. It’s best just to leave them alone unless you want to edit that for some more advanced reason. I’m not going to cover that in this thread.

I did find a pretty useful tool that lets you create the .zip by browsing for files and directories to add to the CWM.zips System and Data folders, lets you add your custom updater-script, and lets you specify what type of binary you would like to use and creates the update-binary for you. Once you have created the zip it will then sign the zip for you.

Thread:
http://forum.xda-developers.com/showthread.php?t=1274736
Windows Installer:
http://dl.dropbox.com/u/32209684/UpdatezipCreator/UpdatezipCreator_setup.exe
Be sure to thank JordanElliot for creating this

 

[mavrikmeercat]

The updater-script and update-binary is what takes all the know-how.

Thanks to some info from Davegrow, depending on what generates your update-binary (Updatezip Creator, UOTK, Android Kitchen) may all have different versions of the EDIFY binary and that directly affects what syntax you can use for your mount points to /system, /data, /cache, /sd-ext, and such.

So, say you want to format /system before installing a ROM. The base language for the Transform Ultra would be:

format("ext4", "EMMC", "dev/block/mmcblk0p15", "/system");

But might not be the way it is for your binary. it may be a variation of those arguments.

arguments are the things inside ( ).
ext4= type of file system for the TU
EMMC= Type of Partition for the TU
dev/block/mmcblk0p15= mount point for /system in the TU
/system=name of the partition

Some binaries only call for two arguments to format like this:

format("system", "/system");

Or

format("ext4", "/system");

And some might call for three like this:

format("ext4", "EMMC", "/system");

Or

format("ext4", "EMMC", "dev/block/mmcblk0p15");

Also from what I gather, if your binary calls for say two arguments then the mount command calls for three.. (always one more for mount) but I could be wrong on this. not much to go on. Bits and pieces of info only

(More info required from the community)

 

[Lordvincent 90]

i tried this using win7 64 and got this:

Access to path 'C:\ProgramFiles(x86)\
UpdatezipCreator\Logfile.txt' is denied. 
Please contact the developer

any ideas?

derp. ran as admin all is well now

 

[mavrikmeercat]

i tried this using win7 64 and got this:

Access to path 'C:\ProgramFiles(x86)\
UpdatezipCreator\Logfile.txt' is denied. 
Please contact the developer

any ideas?

derp. ran as admin all is well now

make it permanent by right clicking/properties/check run as admin

 

[Lordvincent 90]

make it permanent by right clicking/properties/check run as admin

lol, yup, i did that. thx

 

[mavrikmeercat]

lol, yup, i did that. thx

it's a pretty good program script huh?

 

[Lordvincent 90]

makes life WAAAAYYYY easier... im working on the warp for my rm...
1.make cwm flashable version of stock rom
2.deoded stock rom
3.replicate CTMOD-like rom
4.???
5.PROFIT?

 

[mavrikmeercat]

makes life WAAAAYYYY easier... im working on the warp for my rm...
1.make cwm flashable version of stock rom
2.deoded stock rom
3.replicate CTMOD-like rom
4.???
5.PROFIT?

just go for the big!!! CTMOD like but give blood cred for it
that warp would be BADASS with CTMOD

 

[Lordvincent 90]

thats the plan.... now, i just hope it (the rom, not the cred, lol) goes as smoothly in real life as it does inside my head lol

ps, those are ALL goals, just the order of operations to get to the end product- PERFORMANCE. it didnt come with CIQ so that saves me a hard, time consuming, project... i dont so much plan to port it as replicate its tweaks. ground up approach...