Develop Bugs

Beta: WM5 ROM editing tool

I've made a set of tools that can assist in cooking your own WM5 ROMs. These tools were tested only on BlueAngel devices. They should also work on Himalaya. Universal and Wizard support is also present, but it is untested, so the tools may crash or turn your device into brick. But it is possible to extract files from universal/wizard ROMs and use them on other devices.
I've attached 2 archives - make_hv.rar, a tool from Platform Builder that can be used to recreate .HV files (they contain default and boot registry), and imgfs_tools.rar - these tools should be used to edit WM5 IMGFS partition.
With these tools and http://forum.xda-developers.com/viewtopic.php?t=33321 (it can edit WM5 boot XIP partition) it is possible to replace/add/delete any file in WM5 ROM.
Usage:
Code:
prepare_imgfs.exe
Splits nk.nba into imgfs_raw_data.bin and imgfs_removed_data.bin.
imgfs_raw_data.bin - contains raw IMGFS data
imgfs_removed_data.bin - contains extra data (something like FAT table).
Usage:
prepare_imgfs.exe nk.nba [-nosplit] [-mpx200] [-acer]
Use "-nosplit" for HTC Wizard and Universal ROMs that don't contain extra
blocks of data. In this case imgfs_removed_data.bin would be empty.
make_imgfs.exe
Reverse of prepare_imgfs. Combines imgfs_raw_data.bin and imgfs_removed_data.bin
into nk.nba file. Use -nosplit if it was specified for prepare_imgfs.exe.
Usage:
make_imgfs.exe nk.nba [-nosplit]
The nk.nba file would be used as a template, its contents would be overwritten.
viewimgfs.exe
Dumps the contents of imgfs_raw_data.bin to "dump" subdirectory. Files are
dumped as is, modules as directories. File time and attributes are preserved.
If RecMod.exe is present in the current directory, all modules are
reconstructed as working DLLs/EXEs and placed in the corresponding subdirectory.
Tool creates dump_MemoryMap.txt with address ranges occupied by modules.
Usage:
viewimgfs.exe imgfs_raw_data.bin
RecMod.exe
Reconstructs a module dumped as directory to a working state. Rebuilds
relocations information, and tries to guess section names.
Usage:
RecMod.exe [path to module directory]
BuildImgfs.exe
Reverse of viewimgfs. Reconstructs imgfs_raw_data.bin and imgfs_removed_data.bin
from files in "dump" directory. Overwrites contents of imgfs_raw_data.bin/imgfs_removed_data.bin
files. Does not check for errors or end of free space. Approximate free space
left is displayed when program is finished. In case of error contents of bin
files is undefined.
Usage:
BuildImgfs.exe
It would overwrite imgfs_raw_data.bin/imgfs_removed_data.bin in current directory.
DelFile.exe
Deletes one file or module from imgfs_raw_data.bin. Wildcards are not supported.
Usage:
DelFile.exe filename.ext
Uses imgfs_raw_data.bin from current directory. Does not check for errors.
AddFile.exe
Adds one file to imgfs_raw_data.bin. Would reuse space freed by DelFile.
Usage:
AddFile.exe filename.ext
Uses imgfs_raw_data.bin from current directory. Does not check for errors.
The typical process should be:
prepare_imgfs.exe nk.nba
viewimgfs.exe imgfs_raw_data.bin
...modify "dump" directory as you need...
BuildImgfs.exe
make_imgfs.exe nk.nba
or
prepare_imgfs.exe nk.nba
DelFile.exe filename.ext
AddFile.exe filename.ext
...you may add/delete as many files as you need...
make_imgfs.exe nk.nba
Of cause you'll need a tool to convert NBF<->NBA files. SD-card images can be also used instead of NK.NBA file, but this was not tested!
Troubleshooting.
In case of invalid ROM the tools would crash without saying anything. In this case they may destroy the contents of input files.
Use these tools at your own risk! They may make your device completely unusable! Always make an SD-card backup of your ROM and Extrom!
The worst case I had during tests was complete destroying of DOC partition on my device. I had to flash WM2003 OS, repartition DOC from there and this fixed the device. Of cause this method cannot be used on Wizard or Universal.
I've published these tools so that someone could integrate BA patches into a ROM or play with cooking own ROMs.
edited 12.12.2005. AddFile/BuildImgfs should work on Universal/Wizard ROMS (i.e. roms with empty imgfs_removed_data.bin file).
edited 15.01.2005. Fixed a major bug found by TofClock. Short name of files with filename length 24 chars or longer (like "instmsgrresources.96.dll") was incorrectly generated and in some cases they were inaccessible by OS.
edited 05.02.2005. Added several checks so that viewimgfs.exe does not crash on incorrectly patched ROMs (MPX200). Don't use buildimgfs.exe on such ROMs.
edited 30.03.2006. Added RecMod tool that reconstructs modules dumped as directories to a working DLL. So reusing modules from other ROMs is now much easier. Added updated prepare_imgfs.exe with support of ACER N300 ROM (thanks to Tuatara).
edited 12.07.2006. Added source code of prepare_imgfs/make_imgfs tools, so anyone can add the support of new devices.
edited 25.10.2006. Published the source code on my site. The code is ugly and is not commented at all. Don't ask me how to compile or use it!
I've stopped working on this project. There would be no updates.
Complete source code is available on my site.

mamaich,
can this be done on Alpine device??? Alpine that known as faster Himalaya also should be running WM5.....
thanks

Looks nice
Some questions:
1. AddFile:
Can I add single file like
Code:
AddFile something.exe
or have I use 'modules as directories' [like directories dumped with ViewImgfs]
2. AddFile:
Is it possible to add files into directories not in \Windows? For example: "\Program Files\Something\something.exe"
3. Is it possible to modify the kernel? Can I extract and replace \Windows\fatfsd.dll?
Thanks in advance.

mamaich, would for example replacing the internet explorer exe be enough to get it to render gifs correctly? Or are extra dll needed? Also is it necessary to use the other tool you linked to as it appears your tool can add and delete files itself? thanks
Edit: Forgot to add, thanks for your hard work.

mamaiiiiichhhhh I was waiting those tools gr8 work mate, can you upload the modified rom that you already customized for testing it?

baniaczek said:
1. AddFile:
Can I add single file like
Code:
AddFile something.exe
Click to expand...
Click to collapse
You can use both methods, but subdirs can be used only if you are really know what you are doing (i.e. you know all addresses of each section and 100% sure that they don't overlap some other modules and you've edited .VM and .ROM files). In most cases you should add EXE/DLL files as normal files.
Is it possible to add files into directories not in \Windows? For example: "\Program Files\Something\something.exe"
Click to expand...
Click to collapse
All files are placed into \windows dir and then moved by coldinit to subdirs according to instructions in initflashfiles.dat. Of cause you can modify that file as you like.
3. Is it possible to modify the kernel? Can I extract and replace \Windows\fatfsd.dll?
Click to expand...
Click to collapse
Boot part can be edited with http://forum.xda-developers.com/viewtopic.php?t=33321
ramram
There is no ROM I can release for public testing. I would not integrate my patches into the ROM, I'm working on adopting Wizard's ROM for our devices. But everything is on too early stage, I have to combine registry settings, ROM files, find and patch drivers for ROMs to work, etc. And Wizard's ROM is larger than ours, some files should be removed.

efjay said:
mamaich, would for example replacing the internet explorer exe be enough to get it to render gifs correctly? ...
Click to expand...
Click to collapse
I don't have any problems with IE.

Ic
mamaich,
I'll wait you then until you finish the wizard rom adoptation, I'll be glad trying it on the BA if you don't mind, consider my device for development purpose and beta testing if needed.
Concernig the IE, I have the same problems as Efjay mentioned earlier.
Thank you

@mamaich
Thank you for the answer. And thank you for your hard work [sinze Siemens SL45i].

mamaich said:
efjay said:
mamaich, would for example replacing the internet explorer exe be enough to get it to render gifs correctly? ...
Click to expand...
Click to collapse
I don't have any problems with IE.
Click to expand...
Click to collapse
mamaich, the problem is with viewing gif files. On this site using PIE i cannot see the quote button and other buttons below a post. Even manually opening a gif file on the BA opens PIE with a blank page.

go mamaich!!!
;o)))
buzz

buzz_lightyear said:
go mamaich!!!
;o)))
buzz
Click to expand...
Click to collapse
And GooO BuzZ

how about buzz if you can with your know how get a bare minimum rom version of universal not having alot of crap like the various silly tsk files and other pictures and videos that serve as demos on the rom and not do anyting else..im sure alot of us use our own file explorers (resco,tc) so that can be removed aswell.. what do you think...??/

can you use nk.nbf? how can i convert nk.nbf into nk.nba????

zohaer21 said:
can you use nk.nbf? how can i convert nk.nbf into nk.nba????
Click to expand...
Click to collapse
you can use this tool xda3nbftool.exe download from ftp for BA or Xda2nbftool.exe for Himalaya.
@Maimach
All the module files are Directory ??? How can I use these for my purpose ? But it Great work Maimach , go on!!!!!!

I tried to use this tool to add two modules and then flash the finished nbf file but i get an error file is corrupt if i use BaUpgradeUt.exe. If i use MaUpgradeUt_noID.exe it seems to initialise but no rom info is shown on the upgrade screen. Continuing the rom upgrade nothing then happens then a message comes up that the upgrade is finished. Soft reset and back to normal. I followed mamaichs instructions and everything seemed to go ok. Any idea why it didnt work for me?

Yeah, go Mamaich, you rock. After the Wizard ROM on the BA, the next step could be a complete ROMkitchen (á lá Wallaby...).

Stupid question, where can I find the NBF<->NBA converter? (Yes, i did search the forums)

ftp://xda:[email protected]/BlueAngel/Tools/UpgradeTools.rar
and this page for info
http://wiki.xda-developers.com/index.php?pagename=BA_GettingStarted

@efjay
did you use the -sd -sl -so and the -c -u options in xda3nbftool? Thats where i went wrong first time.

Cooking ETEN Romz

Hi
can anybody please help with decomiling ETEN Romz so that we can customise it and tweak it like HTC romz.
reo

Try this attach
Usage:
prepare_imgfs_eten.exe temp.dat
then mamaich viewimgfs

Hi
thanks i have this file, and yes it does work to disassemble rom. but i had a problem reassembling.
i am still testing this, i will fill everyone in.
regards
reo

OK, continue
...modify "dump" directory as you need...
BuildImgfs.exe
make_imgfs_eten.exe temp.dat

hi
thanks, but my problem was actually this part. i should have been more clear. when i done a recompile with build the OS did not come out correct. it seems that it got damamged and when i loaded it to my phone it froze up on boot logo.
is there a limit on the amount of changes u can make in the OS part ? mayb it must not go higher than a certain file size ?
i however have successfully changed the startup logo, and extrom and created a new ROM. only the OS part has been a problem.
regards
reo

How Can I extract the ROM from Eten?

reo
These tools were tested on M500, M600, G500.
If you disassemble temp.dat to dump folder, and then built temp.dat without any changes in the dump folder, the resulting file temp.dat is working?

I tested this, but unfortunately after i reassemble it does not recombile identically. so when i compare there are differences.
however, i have noticed that if you do not have the PPM from itsme repository then you will get 652 files extracted, when you should actually recieve 1117 files
regards
reo

prepare and make imgfs works. when i open reassembled temp.dat again with prepareimgfs - viewimgfs extracts files normally (About 102mb). But comparing with hex editor, first 51,880,508 byte is ok then it changes. After every 513 bytes there is extra 7 bytes in orginal rom. I think Eten made some protection. For example in rom ver.230 bootscreen image (JPG) is located at first lines of rom. But every 512bytes of image there is FFFF FFFF. So i removed FFs and i got bootscreen image
uas, could you give me prepare_imgfs_eten source? i want to see how it works. i am not a programmer but i made a little perl code which adds FFFF every 512bytes of a file. For making bootimages for putting into rom.
Reo i couldn't start bootloader anymore after i made a modification on rom. Could you give me any suggesttions? Forgive my english if there is sth wrong....

All perl scripts for eten roms are in the Russian forum
http://forum.wce.by/viewtopic.php?p=78923#78923
(Registration required)

thanks very much..

can someone make a Eten G500 rom with a bigger page pool ?

UAS,
Thanks a lot for your tools. It works perfectly on my M600 and I am going to write up an tutorial how to customize the rom in detail

jackleung said:
UAS,
Thanks a lot for your tools. It works perfectly on my M600 and I am going to write up an tutorial how to customize the rom in detail
Click to expand...
Click to collapse
oh, please do.......i have been eagerly waiting for someone who are able to explain the extraction of eten rom in details, please jackleung.

sfliu said:
oh, please do.......i have been eagerly waiting for someone who are able to explain the extraction of eten rom in details, please jackleung.
Click to expand...
Click to collapse
My draft (not finished yet)
http://www5.discuss.com.hk/viewthread.php?tid=4127717&extra=page=1

jackleung said:
My draft (not finished yet)
http://www5.discuss.com.hk/viewthread.php?tid=4127717&extra=page=1
Click to expand...
Click to collapse
thank you very much for your effort, this really make my daylooking forward to your complete tutorial.

initflashfiles.dat you can get from the windows folder on your device.
It must be in Unicode but without the first two bytes FFFE Unicode sign.
Localized names must be like as:
Directory("\Windows"):-Directory("\x0428\x0440\x0438\x0444\x0442\x044B")

uas said:
initflashfiles.dat you can get from the windows folder on your device.
It must be in Unicode but without the first two bytes FFFE Unicode sign.
Localized names must be like as:
Directory("\Windows"):-Directory("\x0428\x0440\x0438\x0444\x0442\x044B")
Click to expand...
Click to collapse
But seem like Eten's PDA doesn't come w/ one. Use initflashfiles.dat from other as template and make one from scratch is quite time consuming and error prone (especially w/ Chinese rom w/ chinese file name and directory). For me, I just manually move the files and directories once. Do a SPB backup and use the backup files for initialization after ROM update.

How to custom build Eten Rom
Let me thanks UAS for the tools first
I put all require programs, and user.txt and default.txt (registry for *** Traditional Chiniese Rom ***) into a signle package. Here http://rapidshare.com/files/30073907/eten_rom_cook_package.zip.html
Steps
******************
U will find the steps are very similar to cooking Asus P525 here http://www5.discuss.com.hk/viewthread.php?tid=3788644&extra=page%3D2
***** Section 1: obtain the imgfs_raw_data.bin from the rom *****
1. Download my Rom edit and update package (addfile.exe, buildimgfs.exe .... etc.)
2. In File Explorer, put "%temp%" as address and it should bring you system temp directory probably "C:\Documents and Settings\<yr winodows user id>\Local Settings\Temp", U may want to do some clean up if lots of files there.
3. Run the Eten Rom update program (e.g.: EUU_M600_CHT_R22_101_0230HK_WinXP.exe)
4. No need to connect yr M600. Follow the update instructions step by step and you will eventually see a files: temp.dat (~73mb). Copy the Rom file (Temp.dat) to other folder and extract my package there.
5. create the imgfs_raw_data.bin file by "prepare_imgfs_eten.exe" ONLY
***** Section 2a (Modify Rom content by Add/Remove files) ******
This method is very easy and relative low risk
1. Remove files in the Rom by "Delfile.exe <file name in the rom>"
2. Add files to the Rom by "Addfile.exe <file in yr computer>" (If the program crash, the rom is probably full)
***** Section 2b (Modify Rom content by extract and re-package) *****
More complicate and BuildImgfs.exe take a long time to build a package. But this method ismore flexable and manageable.
1. extract the content by "viewimgfs.exe imgfs_raw_data.bin"
2. add/replace/remove files in the dump directory
3. package the content by back to imgfs_raw_data.bin by "BuildImgfs.exe" (take a shower then come back )
****** Section 3 (optional: Modify the registy content of the Rom file) ******
1. Get the default.hv and user.hv from 2b.1
2. do the following in DOS to convert the registry to readable format :
REM ****************************
SET _FLATRELEASEDIR=.
rgucomp -o default.hv -nologo > wwedefault.txt
rgucomp -o user.hv -nologo > wweuser.txt
REM ****************************
(note: If you are modifing Chinese Rom, rgucomp does not support Chinese Ouput and you need to manually fix the output file (or use mine in the package as yr template)
3. Add "REGEDIT4" in the beginning of the files, leave a blank line atthe end of the file and save the file as UTF-16 or Unicode format. (Ultra-Edit is very good editor for this)
4. Edit the files for registry setting
5. Do the following to replace the registy file w/ yr modification
REM *** Registry ****
Delfile.exe default.hv
Delfile.exe user.hv
attrib -h -s -r *.hv
SET _FLATRELEASEDIR=.
copy /y wwedefault.txt boot.rgu
RGUCOMP -b
copy /y boot.hv default.hv
Addfile.exe default.hv
copy /y wweuser.txt boot.rgu
RGUCOMP -b
copy /y boot.hv user.hv
Addfile.exe user.hv
REM *** Registry ****
******** Section 4 (Optional: Create Folders or copy files from \Windows to other directory)
1. initflashfiles.dat not present in Eten rom, U can create one and put it in the rom. But I can't make my M600 to boot properly w/ this
******* Section 5 Convert imgfs_raw_data.bin temp.dat***************
1. make_imgfs_eten.exe
******* Section 6 Update yr M600 w/ the modified rom***************
1. Copy the temp.dat and RUU.exe (from my package) back to %temp% directory
2. Connect yr M600 and wait for MS Activesync to connect first
3. Run RUU.exe and follow the instruction.

My customized M600 Hong Kong Rom
Don't ask me for M600+ rom since I don't have M600+, and I will not have time to customize build for others. So, take it or leave it (but I might do bug fix and update if there's any). Please feel free to give comment.
*** ROM based on Hong Kong 230 ROM (EUU_M600_CHT_R22_101_0230HK_WinXP.exe) ***
What's get removed from my customized rom:
1. Eten phone firewall (replaced by CALL SMS Blocker)
2. MSN & Msn messenger (replaced by MSN Live and Live Messenger)
3. Eten phone profile manager (Replaced by Pocketmax Phone alarm)
4. Calculator (replaced by Omega 1-Calc)
5. Pocket Excel (Install Softmaker Office if you need a REAL excel program)
6. Pocket Powerpoint
7. Mandarin Voice Command (replaced by Cantonese)
8. Error Reporting and Irda driver
9. Eten backup problem (Replaced by SMS backup Genius and SPB Backup)
10. Quick Link
11. Lots of other junks
What's buildin: (all the tricks I mentioned here: http://www5.discuss.com.hk/viewthread.php?tid=2505945&extra=page=1)
1. USB Host
2. Eten backup battery patch
3. Eten Skype Setting, and Skype
4. SPB Safe Mode and AltTab
5. AE Button Plus
6. Resco Audio Recoarder
7. Resco File Exploer 5.42
8. MemEmpty
9. Multipad.exe
10. No Plugins Today
11. TCPMP Player
12. Pocket Alarm
13. Resco Photo Viewer and screen capture
14. Task Manager
15. Celedial and CeleTask
16. WM5NewMenu
17. Wisbar Lite
(Not all the apps are registed or some of them registered under my name, you may need to look for the SN yrself)
To Install:
1. Follow instruction 6 on my previous post to load the rom
2. put the exe file on yr PDA and run it to have the needed files in place
Dowload link: http://rapidshare.com/files/30225309/eten.rar.html

Rom Cooking Related Question: Bugs and Problems

I'm facing a rather tricky problem.
Adobe Flash LE has a file called searchtext.bmp, same goes for the taskmanager that i'm using....BuildOS says there is redundant files (already exists)...what can I do to avoid this conflict?
Same thing happened to audio manager and audio booster. I first installed audio manager, then I installed audio booster. They happen to be using the same file name for some apps, and as a result, audio manager's skin was messed up because audio booster's skin file overwritten it

cook one in and use a cab for the other!

one thing you can do, is that you cook the bitmap file as a different name, say, package A has a file called myfile.bmp, and package B as well. what you need to do is cook the file in B as myfile_.bmp and an initflashfiles.txt with the entry such as:
Directory("\Program Files\ProgramB"):-File("myfile.bmp","\windows\myfile_.bmp")
that should work.
** this means that, program A and B would be in \program files\ instead of \windows\.

allan1 said:
cook one in and use a cab for the other!
Click to expand...
Click to collapse
Allan, that will not work as I mentioned in my thread that it will overwrite the file with the same name.
@kazuni
That sounds like a plan, seperating them into different folders. I'm gonna try and see if it works

What about same DLL?
Another questions I have is about same DLL. For example, Comm manager uses a dll called phcanOverbmp.dll. I noticed that the "White battery Icon" fix also uses the same DLL, but they are of different size with Comm manager's version @ 500+kb, while the battery fix version @ at smaller size.
Which DLL should I keep?
Can I keep the one that is larger and apply the registry settings found in the battery fix?

kin0kin said:
Another questions I have is about same DLL. For example, Comm manager uses a dll called phcanOverbmp.dll. I noticed that the "White battery Icon" fix also uses the same DLL, but they are of different size with Comm manager's version @ 500+kb, while the battery fix version @ at smaller size.
Which DLL should I keep?
Can I keep the one that is larger and apply the registry settings found in the battery fix?
Click to expand...
Click to collapse
as long as your program isnt hard coded to use \windows\phcanOverbmp.dll then you can make the OEM package for Comm Manager to reside in another folder and use its own phcnaOverbmp.dll
if not, then you will have to try and see if you do not apply the battery fix at rom cooking, then manually copy the file over into your pda after bootup, and see. that way, you are trying both original commanager and batteryfix's phcanOverbmp.dll and see if they can coexist.
remember, you cannot use file explorer to copy over a file that already existed in rom from another location. you would have to copy it as a different name, and then put it inside \windows\ and then rename the file as the original file name.
see if that helps?

actually, I don't think I even need to replace the phcanOverbmp.dll
the "fix" pretty much just sets the parameter "BatteryIconIdStart" to integer: 1001
Looking at the fix in Schap's thread, the Integer was set to 1000....does anybody know what difference does it make?

The .bmp in the taskmanager isn't needed.
The phcanoverbmp in the comm manager is a stock version. Remove it from the package if your going to install a custom one from somewhere else. The larger one probably has Schaps battery indicator.
Typically, duplicate files are caused from re-introducting a file that isn't needed - typically from to packages that were compiled and one inadvertently getting an unnecessary file.
You're on the right track with asking what the difference is, but sometimes I'll grab a cab for the package I'm trying to install and compare the files. In many cases, that's solved the mystery.
Another suggestion is if you're customizing your own kitchen, you might put everything into the OEMApps folder. Thay way you're not adding additional .dsm/.rgu files into your rom unnecessarily. Just copy the files over and paste the .rgu contents (following the guildelines for doing so) to the OEMApps folder .rgu.

Matt,
Actually most of the time I'd take the cab, decommission it, and compare it to some of the premade packages to see what the differences are, then i'd use my own discretion to recreate my own package.
Another suggestion is if you're customizing your own kitchen, you might put everything into the OEMApps folder. Thay way you're not adding additional .dsm/.rgu files into your rom unnecessarily. Just copy the files over and paste the .rgu contents
Click to expand...
Click to collapse
You mean I could just go into the packages, take out all the content and copy them into OEMApps, along with the respective .rgu?
What happens to the initflashfiles.txt then? Do I combine all the initflashfiles into one big initflashfiles for all the apps and put it in there as well?
And the benefit of doing this is saving some spaces from the all the .dsm files?

yeah, you would also need to put in the appropriate entries for the initflashfiles.txt
one little advice, i have had a lot of problem with his is that,
option.xml is in UTF format;
initflashfiles.txt is in UTF format;
anything.rgu is in UTF format as well;
but shortcuts are all in ANSI stardard format.
have fun

lol, yeah most of them are in unicode. When I just started getting into cooking, I wasn't even sure if .dsm is suppose to be in unicode or ansi since most of the guides only say to create rgu in unicode, none said anything about whether dsm should also be in unicode or ansi. But anyway, for those who are looking for the answer, .dsm is in ansi
Problem #1
I've still got a few tiny bugs I need to fix for my rom. When I create the "accessories" and "system tools" folder with the line:
Code:
Directory("\Windows\Start Menu\Programs"):-Directory("Accessories")
Directory("\Windows\Start Menu\Programs\Accessories"):-File("W5torage.lnk","\Windows\W5torage.lnk")
The first line should create the folder for accessories. However, the folder that it created is just the generic folder.
How can I get windows to create the accessories folder like the one in the picture below?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Should I be be using the code:
Code:
Directory("\Windows\Start Menu\Programs"):-[B][COLOR="Red"]PermDir[/COLOR][/B]("Accessories")
??
Same goes for the system folder.
Problem #2
Another thing I'm having problem with is getting autoconfig to run. I've created the following:
Folder name: Preconfig
With the following content:
-preautorun.exe
-preautorun.lnk
-HTC_Default.tsk
-Preconfig.txt
Code:
LOCK:Enabled
EXEC:\Windows\SetHSDPA.exe /Enable
EXEC:\Windows\cusTSK.exe \Windows\HTC_Default.tsk
LOCK:Disabled
RST: Reset
I then created a dsm file and populated it with buildDSM. I toss it into the OEM folder and ran buildOS....it didn't work Am I missing something?
BTW, kazuni & matt, thanks for helping me out, you guys have been really helpful
Edit: Problem two solution
I'm an idiot, it's missing the provxml
Question
What is the App_Service.dll for? I was examining the pandora kitchen's OEM package for Pre-settings and in both ATT preconfig were the App_Service.dll, but it wasnt there in the Orange_UK's presettings..

kin0kin said:
lol, yeah most of them are in unicode. When I just started getting into cooking, I wasn't even sure if .dsm is suppose to be in unicode or ansi since most of the guides only say to create rgu in unicode, none said anything about whether dsm should also be in unicode or ansi. But anyway, for those who are looking for the answer, .dsm is in ansi
Problem #1
I've still got a few tiny bugs I need to fix for my rom. When I create the "accessories" and "system tools" folder with the line:
Code:
Directory("\Windows\Start Menu\Programs"):-Directory("Accessories")
Directory("\Windows\Start Menu\Programs\Accessories"):-File("W5torage.lnk","\Windows\W5torage.lnk")
The first line should create the folder for accessories. However, the folder that it created is just the generic folder.
How can I get windows to create the accessories folder like the one in the picture below?
Should I be be using the code:
Code:
Directory("\Windows\Start Menu\Programs"):-[B][COLOR="Red"]PermDir[/COLOR][/B]("Accessories")
??
Same goes for the system folder.
Problem #2
Another thing I'm having problem with is getting autoconfig to run. I've created the following:
Folder name: Preconfig
With the following content:
-preautorun.exe
-preautorun.lnk
-HTC_Default.tsk
-Preconfig.txt
Code:
LOCK:Enabled
EXEC:\Windows\SetHSDPA.exe /Enable
EXEC:\Windows\cusTSK.exe \Windows\HTC_Default.tsk
LOCK:Disabled
RST: Reset
I then created a dsm file and populated it with buildDSM. I toss it into the OEM folder and ran buildOS....it didn't work Am I missing something?
BTW, kazuni & matt, thanks for helping me out, you guys have been really helpful
Edit: Problem two solution
I'm an idiot, it's missing the provxml
Question
What is the App_Service.dll for? I was examining the pandora kitchen's OEM package for Pre-settings and in both ATT preconfig were the App_Service.dll, but it wasnt there in the Orange_UK's presettings..
Click to expand...
Click to collapse
The only way you can make them is specifying an icon file. if you take a look and unhide the folder there, there is an icon.ico or a dll there.

Actually, I found the solution after looking at the initflashfiles.dat from another rom which has the folders and here's what I found:
Code:
Directory("\Windows\Start Menu\Programs"):-Directory("Accessories")
Directory("\Windows\Start Menu\Programs\Accessories"):-File("icon.lnk","\Windows\accessoriesico.lnk")
Directory("\Windows\Start Menu\Programs"):-Directory("System Tools")
Directory("\Windows\Start Menu\Programs\System Tools"):-File("icon.lnk","\Windows\systemtoolsico.lnk")
That's one less problem!
New Problem
One other odd problem I'm having is with the theme. For some reasons windows wont apply the theme properly for the first time with my rom, the theme is only partially applied with some "leftovers" from the windows default theme...like some parts being blue and etc. Sometimes I need to reapply the theme several times to get it applied properly. Does anybody know what's causing the problem. I've had the same problem last time and somehow it just disappeared in one of my test roms but it is now back.

[KITCHEN-WWE-NL-DE] O.R.D.E. v2.04.00.01[118.51|61.26][VACATION]

Open.Rom.Diamond.Edition​
​
The First ever MultiLanguage Support NOOB Kitchen.
Now It Cooks you either a German, English or A Dutch Rom without the need of knowing what goes on underneath the cooking hood.
Just Start Cooking Select your Language then Disable or enable the applications you want in the rom and Flash.
For the more experienced Cooks, Package Updates or extra packages are always welcome to be submitted. Place the name into the Package like "PACKAGE_DSIXDA_Mortscript_Screen_Rotate_Simple_0000". You can PM me about it or post directly into the thread.
The Kitchen is Hybrid and i have given no attention to the Build Numbers that you SEE in device information. I only Update Incrementally and only what is needed as long as it's stable i don't care about version numbers Shown, trust me i know what i'm talking about, stop the paranoia.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
Make It Like You Want To And Help Making It Better​
Version 1.97.162.6 WWE+DE+NL BETA|132.66|14.15|118.51||115.03|53.77|61.26|​
The last stage of Development before it leaves Beta has now been reached. The Selectable Options will all be put into the correct groups. A few more options will be added, Bugs will be found and the mort installation script will be optimized.​
IPMORTANT Cooking Instructions​
Contents & Options​
Blauwe Tand Me Up Scotty.​
OLD SKOOL XDA Respect, to Brothers "The Great" Faria and the "Kitchen Classic" Anichillus​
This Project could not have been Possible without, Bepe, Bram_smulders, cmonex, dark simpson, panosha, Anichillus, itsme, jcespi2005, joubertvasc, jugglerlkr, mamaich, Mort, OliPro, pfcsabre, pof, sushilange, Paul at Modace for Apptodate, Nadavi, Snailslug, tadzio, theblasphemer, AlphaZero, SwTos, MRHawaii, Mondilv, Tom Codon, Tuspidin for sharing the Blackstone ROM, udk and Many More.
Direct Contributors, Noonski, Ameet, DSIXDA, NFSFAN, mccune, aruppenthal, bbobeckyj (for teaching me the Mort Regread and If else commands, for even more optimized packages), Bl0w, mst46, Kokotas, stief (without him i would not have a Diamond to Cook and work with in the first place), Pkoper, Piranha1, Mossi, comec, (The German Team). TheDizzAR, Aarge (For their Appreciative Donation)
If i have forgotten to add credit to you, i'm sorry for my slip up. Feel free to PM me about it so i can correct it.
Please Report Your **** Ups (Combination's of Selections that don't work together)​
If you like what we're doing and would like to motivate me into making it WWE (Almost Done) and bringing the kitchen over to Touch Pro to, you can show us some love.​
​
Packages are Allowed to be used for Personal Roms only.
And if you manage to use the heavily MortScript Dependable Packages in a Public ROM respect to you for understanding Why it is being used.
Give a Holler, but most importantly help making it better.
Or Do as most do Send a PM and most of the Time the Answer will be Yes.​

O.R.D.E. German
ORDE German version available.
Current version:
22.12.2008 1.97.162.2
Please leave your comments here or in german here.
22.12.2008 v1.97.162.4DE

Temporary Placeholder for ORDE WWE Messages.

Extra Packages
Added into Next Update (1.97.162.7).
PACKAGE_McCune_Quickmark_0000
PACKAGE_McCune_Stopwatch_0000
Upgrade Packages
PACKAGE_McCune_Quickmark_0000 & Install Script
PACKAGE_McCune_Stopwatch_0000 & Install Script
The contents of the INstall scripts need to be added manually to the SPC.mscr in the OEMOPERATORS folder if your upgrading before version 1.97.162.7

PACKAGE_AltTab_0000:
Adds "Alt-Tab" functionality (program switching) under the Start menu.
PACKAGE_Opera_Mini_4_2_0000:
Installs Opera Mini 4.2 on your Diamond and also creates a shortcut on the Start menu. It is recommended that the Esmertec Jbed 20080912 package is selected or else the shortcut may not work (see the next package).
PACKAGE_VGA_Esmertec_Jbed_20080912_5_1_0000:
Thanks to trueg for pointing this version out to me. It is one of the first versions of Jbed that allows you to resize the tiny fonts in Opera Mini, among other things.
PACKAGE_TouchHD_EnglishOnly_Keyboard_0000:
Touch HD Keyboard, English only. Similar to Diamond keyboard but with left/right/up/down soft keys below the keyboard. Files are based on the multi-language CAB by sblop at this link; I simply took out the appropriate files and registry keys, reducing the size significantly.
.

Screenshots
Some Screenshots:
More To Come​

Instructions
Instructions
1. Be Sure you have Developers HardSPL Flashed to your Phone before you start Cooking.
In the Folder "Tools\SPL's" you will find three versions of these.
2. The Kitchen is not set up to use a specific Radio nor do i Advice any as Radio performance can differ from Operator To Operator
A Collection of Radio's can be found in the folder "Tools\Radio's"
3. The Kitchen does not include the OS.NB anymore because it was getting to big. Fortunatly Modilv has the LEGO Kitchen Thread Kitchen Thread Where He Provides two OS.NB versions in his Rapidshare Folder.
Download either the 8MB Pagepool version or the 12MB Pagepool version and then drop the OS.NB into the "\Rom\" folder.
4. The Kitchen has three Language Options to choose from when it Begins.
1 for English (not working yet) 2 for German & 3 For Dutch (Not Working Yet).
5. After Choosing your language Disable or Enable extra options in the BUILDOS screen and then Press Play. If you get errors during this process please post them in this thread. After BUILDOS is finished Close the Build OS window and it will continue do to it's job until the Flash to you phone Screen comes up, so Flash it.
6. Flashing Roms to your phone is always risky, no matter how much precautions i have taken, everything that goes wrong is also your responsibility. If your not that familiar with the process the advice is to not tick OF more then the already preselected options.
If you want the kitchen to keep using your preferred packages you have to edit the Corresponding language file in the Options folder.
If your making an English Rom edit the EN.xml file in notepad.
Look up the option you want preselected in BuildOS (The Kitchen) and change the value from False to True (or the other way around).
Don't forget to also to put True into the correspondant Language Option.
0407 for German 0409 for English 0413 for Dutch.
For German edit the DE.xml and for Dutch NL.xml

Content and Default Options
[X]= Default set to ON
[0]= Default set to OFF
If no other MUI Locale Code Present, the Package does not need it.
[X] PACKAGE_francarl_FingerMenu_0000_1_10 [AppToDateSupport]
[X] PACKAGE_joubertvasc_RemoteTracker_0000_0_3_2-0 [AppToDateSupport]
[X] PACKAGE_sushilange_Diamond_TF3D_Config_0000_0_6_7 [AppToDateSupport] [0407] [0409] [0413]

Downloads
​O.R.D.E. NL Kitchen (No ROM download but a Full and Easy Do it Yourself Kitchen)​ SYS: 52.19965 & 5.20954
XIP: 52.20954
OEM: 1.93.404.5, 1.96, 1.97 & 2.00
|Storage|Total|In Use|Free||Program Memory|Total|In Use|Free|
Version 1.0
Version 1.93.404.2 |115.30|17.63|97.66||111.02|56.98|54.04|
Version 1.95.404.7|127.04|19.81|108.47||111.02|55.33|55.69|
Version 1.95.405.1|114.80|24.44|90.36||111.02|49.80|61.22|
Version 1.95.405.3|120.80|20.38|100.04||111.02|48.12|62.90|
Version 1.96.405.5 |122.54|19.20|103.34||111.02|47.07|63.32|
Version 1.97.161.9 |129.16|18.18|110.35||115.03|48.56|66.47|493
Version 1.97.162.5 DE+NL |134.41|12.07|122.34||115.03|56.87|58.16|
Version 1.97.162.6 WWE+DE+NL BETA|132.66|14.15|118.51||115.03|53.77|61.26|
Version 1.97.162.7 WWE+DE+NL|132.66|14.15|118.51||115.03|53.77|61.26|
(Measured after a second boot and killing Active Sync)
Then above numbers are by using the default Ultra Clean preconfigured settings. (not as Clean as it should be yet)
If you change these, the numbers will also change.
This is so easy it can't go wrong (if you Meet the requirements below and don't mess with the settings)
XP SP2 or Vista with MS .NET Framework required to use it.
Also Developers HardSPL is recommended
(Also required is Microsoft Visual C++ 2008 Redistributable Package added to Package)
Any Changes To Kitchen Are at Own Risk!​
Updated Packages (All in the Next Kitchen upload)
(ORDE Packages have no Unneeded Files like Package.Provxml, Initflashfiles.txt, Help, .LNK or other files that are not needed to make the app working. Because Mort Takes Care of most of that)

Changelog
>>=IN <<=OUT
​
Build from Original Dutch HTC Build and numbering goes up from there.
>> (Version 1.97.162.8) Updated Stop Watch with newer version from McCune's Post.
>> (Version 2.04.00.01) Switched to 2.03 OEM/SYS/Restarted Cleanup.
>> (Version 2.04.00.01) Patched and updated PACKAGE_ORDE_ConnectionSetup_0000_1_5_35852_1 Icon removed CPL Item (using MyCPL to get Conn Setup in Control Panel) and Made Modules.
>> (Version 2.04.00.01) Patched PACKAGE_Snailslug_TouchResponse_0000_v03_2 Icon and Updated Package Made Module for the DLL and it now supports AppToDate in Rom to.
>> (Version 2.04.00.01) Updated Taskmanager to PACKAGE_ORDE_TaskManager_0000_2_1_35603_1 Made Modules, removed CPL item and replaces WM taskmanager in Control Panel, Reduced Graphics to 8 Bits.
>> (Version 2.04.00.01) Reduced PACKAGE_pfcsabre_SocialNetworksEngine_0000_1_0_1819_3528 by 0.5 MB by optimizing Graphics to VGA and 8 bits where possible (Graphics without Transparancy), Made Modules.
>> (Version 2.04.00.01) Updated RemoteTracker to PACKAGE_joubertvasc_RemoteTracker_0000_0_3_4-1
>> (Version 2.04.00.01) Added
PACKAGE_KDKobes_FootPrints_0000_1_11_33557_0, Plus the 4 options for different Navigational Soft ware, TomTom, NaviTel, PapaGo & Copilot.
>> (Version 2.04.00.01) Updated Album to PACKAGE_ORDE_Album_HTC_0000_2_5_1820_4127
>> (Version 2.04.00.01) removed CPL item from PACKAGE_Schaps_Network_Plugin_0000_1_0_30468_1
>> (Version 2.04.00.01) Updated Butler to PACKAGE_Siggie1970_Butler_0000__1_2, It's now made into a mort install Package

Q & A
Q: I tried the 'connectionSetupAuto' package and it did nothing - is this package meant to be
used in conjunction with the 'connectionSetup' package? Connection Setup on its own
works fine.
A: PACKAGE_OREE_ConnectionSetup_0000_1_5_34564_2_Auto & PACKAGE_OREE_ConnectionSetup_0000_1_5_34564_2 Need to be installed together to get the Auto part working (sort of)
PACKAGE_OREE_ConnectionSetup_0000_1_5_34564_2
Causes connection setup to run only once after reboot (60 seconds)
PACKAGE_OREE_ConnectionSetup_0000_1_5_34564_2_Auto
Sets it as an Autostart Item that is being run by The Taskmanager and runs whenever you switch the SIM card.
If once is enough, only use the PACKAGE_OREE_ConnectionSetup_0000_1_5_34564_2
(or you can start it manually)
If you switch a lot of Sim Cards and don't mind the extra memory being used at start up leave in the Auto version

Request
Who can help me create a MortScript that reads specific Registry values.
SOLVED thanks to bbobeckyj
Something like these
Code:
[HKEY_LOCAL_MACHINE\Software\MortInstaller\LNK\Reader.lnk]
"SourcePath"="\Windows\AdobeReaderLE.exe"
"TargetPath"="\Windows\Startmenu\Office Mobile\"
[HKEY_LOCAL_MACHINE\Software\MortInstaller\LNK\Calculator.lnk]
"SourcePath"="\Windows\MobileCalculator.exe"
"TargetPath"="\Windows\Startmenu\Office Mobile\"
It then Creates and Executes the Parts below.
Code:
CreateShortcut("\Windows\Startmenu\Office Mobile\Adobe Reader.lnk","\Windows\AdobeReaderLE.exe")
CreateShortcut("\Windows\Startmenu\Office Mobile\Calculator.lnk","\Windows\MobileCalculator.exe")
It's an AutoShortcut/ProvXML/Removeatribute.exe/initflashfiles.dat/Excessive .LNK files in Windows, replacement.
At the moment i put all commands into one start up script, but that makes separate and COMPLETE OEM packages impossible. As disabling one Package in the Kitchen, still leaves the Command in the start up mortscript to create the shortcut.
This is not just for my own convenience, but for building a kitchen that can be used by every NOOB, that contains optimized and clean Packages.
This way i can put the creation of .lnk files into that package it's RGU file.
If it could also unzip and Change attributes through this script using registry values it would even be better.
I know there's someone out there that can cook this one up.
Thanks for the attention at least.
Update:
Script has been adjusted.
It now reacts to if a file is present in Rom and then reacts to that taking into account the MUI localization.
Code:
if (FileExists( "\Windows\RotateScreen.mscr" ))
WriteFile( SystemPath("StartMenu") \ "Rotate Screen.lnk", "99#""\Windows\RotateScreen.mscr""?shellres.192.dll.0413.mui,-8259")
Else
EndIf

Package Submittal
If there's an app or package that you think would be a good one to include in the kitchen you can always submit it.
Here's what you need to take into account.
1. If the package does not need an RGU, you don't need to include it.
2. The RGU and DSM files need to be hand made.
Make a blank .txt file. Go to http://www.famkruithof.net/uuid/uuidgen get a new UID, Rename the text file and extension with the UID number and .dsm extension.
(Ervius Packages sometimes don't work correctly)
Make a blank text file again and rename it to the new UID name and .rgu extension. Make sure you resave the RGU file as Unicode. (that is only if you need the RGU file.
3. When the package is complete. Drop the Package Folder onto the BuildDSM.exe in the tools folder. (be sure that Initflashfiles and option.xml are temporary removed from package when you do this)
Some more explanations about Mortscript installation.
As we try to Use as few as possible files in the rom and also make accommodate with the three language.
The way to create a link to a program has a little trick to it so it installs into the correct directory for the language.
Beneath is an example:
Code:
if (FileExists( "\Windows\StopWatch.exe" ))
if (FileExists( "\Windows\shellres.dll.0413.mui" ))
MkDir(SystemPath("ProgramsMenu") \ "Applicaties")
CreateShortcut(SystemPath("ProgramsMenu") \ "Applicaties\StopWatchk.lnk","\Windows\StopWatch.exe")
Else
EndIf
Else
EndIf
This way it checks for two conditions before it creates a link
As shellres.dll.0413.mui only exists in a Dutch rom this particular shortcut will only be created in a Dutch rom.
Also when a directory does not exist, MORT will not install a link into it.
So i added the MakeDir command first.
Two other variables of the script are needed so it supports German and English.
Now if the file did not need to go into the sub dir Applicaties
One script would do:
Code:
if (FileExists( "\Windows\StopWatch.exe" ))
CreateShortcut(SystemPath("ProgramsMenu") \ "StopWatchk.lnk","\Windows\StopWatch.exe")
Else
EndIf
And only one version of the script would do.
Or the link creation could be more dynamic:
Code:
if (FileExists( "\Windows\YouTube.exe" ))
if (DirExists(SystemPath("ProgramsMenu") \ "MultiMedia" ))
CreateShortcut(SystemPath("ProgramsMenu") \ "MultiMedia\YouTube.lnk","\Windows\YouTube.exe")
Else
CreateShortcut(SystemPath("ProgramsMenu") \ "YouTube.lnk","\Windows\YouTube.exe")
EndIf
Else
EndIf
So if the Folder "MultiMedia" does not exist the shortcut will be made in the main programs folder.

ToDo
1. Check Manila Options (Checked)
2. Check Remote Desktop
3. Fix and put put back main ringtones.
4. Fix Dutch Missed Calls Issue.
5. Fix FullScreen Player. (Checked)
6. Add more configuration scripts.
8. Put back rtps reg values to streaming media and the file itself.

you kitchen is birrliant how i can make wwe rom?
what i need to change ?

yes2000 said:
you kitchen is birrliant how i can make wwe rom?
what i need to change ?
Click to expand...
Click to collapse
Either use the Full Kitchen
http://forum.xda-developers.com/showpost.php?p=2392286&postcount=3
To extract the OEM/SYS/ROM from an Official Rom.
Then Replace the OEM/SYS/ROM folders in ORDE Kitchen.
Then Compare the differences
The Brilliance of the Kitchen is because of all those other People that have worked on it, i just made it a bit more Noob Proof with some very amateuristic adjustments of the batch files.

Your calculations are correct...

pkoper said:
Your calculations are correct...
Click to expand...
Click to collapse
Well it's better then making a WWE Dutch or German ROM.
All the OS parts can be ported from newer WWE builds instead of Porting Localization to a newer WWE build.

Hey for all the people who make this kitchen ..i thank you.
Geat work but now i have to find a way to cook my own favorite programs in the rom.

UC Autorun + The Power of MortScript PreCooked.
Want to Change or add some stuff Through UC Autorun?
Here's a way for the advanced user to do even more.
Code:
CPY1:\Intern geheugen\Cabs\MyMort.mscr
CPY2:\Temp\MyMort.mscr
EXEC:\Temp\MyMort.mscr
Inside the script you can do anything you can do with Mortscript.
For instance copying over a complete Directory to Phone Storage.
Code:
UnzipAll( "\Intern geheugen\Cabs\ExtraTemplates.zip", "\Mijn Documenten\Templates" )
Code:
CreateShortcut("\Windows\Startmenu\Programma's\TomTom.lnk","\Intern geheugen\Program Files\Navigator\TomTom Navigator.exe")
As long as you don't forget to delete the script.
Code:
Delete( "\Temp\MyMort.mscr" )

[PC][TOOL] Manila Source Kitchen - in development

UPDATE: For example of dump, go to Post #3!
Thanks to Co0kieMonster, Chainfire and other people I use their tools (LuaConv, LuaC, LuaDec, CFC, Mode9Decode and some other).
Hello,
[OT]
I am planning on totally remaking Manila into something totally different.
[/OT]
Anyway, back to the topic.
I decided to use Manila, because it has builtin OpenGLES animations that can be decoded to XML, also it uses LUA scripts which are really easy to write, plus manila provides me access to all what I need - audio library, messaging, ...
But this requires A LOT of effort. That's why I decided to create something like Manila kitchen, that would build whole manila from source .lua, .png, .mode9 and .xml files and all the rest I just forgot, to the asd123qwer_manila files.
Advantage of this is, that when some lua script has does require something like messaging\messaging.luac, it really is there, so you don't have to via manilahash.exe search for that file, disassemble, edit etc. Kitchen will do all of this itself
As of now, I have done part, which will grab folder filled with those _manila files, disassemble the lua files, it can delete unneeded langs in xml (afterall, all will be deleted for my purpose), those disassembled .lua files renames by the list (thanks to Co0kieMonster and others who helped him to fill it) it has, creates virtual original file structure. And from this structure, it again rebuilds into output directory. (And yes, it takes that base is \windows\htc, it just seemed useless to have there, since all scripts have that base name)
Example:
from:
C:\ManilaSourceKitchen\Dump\08c9c9cc_manila
C:\ManilaSourceKitchen\Dump\575c2a6d_manila
happens
C:\ManilaSourceKitchen\Source\scripts\activesyncdetect.luac
C:\ManilaSourceKitchen\Source\scripts\audio\music_property.luac
etc.
(Testing and developing is on TF3D 2.1, but will be Sense 2.1/2.5 compatible too.)
Current progress
-- LUA:
- Disassemble
- Move to Source folder with propriate name
- Compile back to _manila file
-- XML:
- Delete languages you don't want
- Move to Source folder with propriate name
- Compile (copy) back to _manila file
-- MODE9:
- Decompile from binary to XML
- Move to Source folder with propriate name
- Compile back to _manila file
-- QTC:
- Revert to PNG from QTC
- Move to Source folder with propriate name
- Compile back to _manila file
-- Kitchen:
- UI
Who's interested?
PS: The "new" Manila, simple picture (MSPaint, mouse, 2 minutes):

Sounds very interesting. It will be great to see what you come up with.

I've been working another hour and half and I made another progress. Now is being decmopiled what can be:
LUA -> luac source code
MODE9 -> XML (editable view of binary mode9)
QTC -> PNG
proper file naming from names.txt -- still needs updating. For TF3D there is about 160 files without name. But with this it is easy to find out what is missing, because when some scripts asks for \Windows\HTC\Assets\Images\someimage.qtc, I can easily check, if that file is there. If not, I simply check it's hash and then find propriate file, add it to names.txt and voila .
To show you how does it look atm, I enclose ZIPped TF3D dump from my ROM.
All files in Sand\*_manila are those without proper records in names.txt which has to be discovered their original name.

Hello all,
Am using this opportunity to introduce myself to the community.My name is Calvin and I,m the new kid on the bloc hoping to find my way around your community to meet some nice and interesting people with fresh ideas.Hope we find a common path to tread.
Calvin
web design,web development, cms websites, Joomla Development, cms based websites, website design and development

Sounds like an interesting project, I know the manila/sense guys in the TouchFLO/Manila/SenseUI social group are keen to move on from the Manila Command Line Kitchen (excellent though it is).
Shall look forward to seeing what comes of this.
Welcome aboard Calvin123.

The "Decompiling" part is a bit of problem, because lua decompiler isn't 100% accurate, so recompile "what you just dumped" doesn't work on all files. Images yes, XML yes, mode9 yes, not not lua scripts.
Anyway, those remaining _manila files are now being bruteforced. Couldn't find link to them in require("somescript"), nor mode9 files . It goes quite fast, hope to get results till 2 hours from now (counting max 30 filename length + .luac name). Bruteforce to find original filenames will be enclosed too, IMHO best way to find original filename, if you can't find it manually by checking dependencies in mode9 and luac