Develop Bugs

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

[Released Translation TUTORIAL] - HOW to translate ANY ROM

Hi!
After a long time of trying to cook custom roms in greek language I am ready to post a small tutorial on how to translate your Rom to your Language using kitchens with a quick and dirty way .
Attention there is a better way to do so but this is what I Do to make my Greek ROMS
Step 1)
a)Download your language emulator Files from
http://www.microsoft.com/downloads/details.aspx?FamilyID=38c46aa8-1dd7-426f-a913-4f370a65a582&DisplayLang=en#filelist
(b) extract the files in a new folder.
Slumpolo 's suggestion:
-----
to extract files from the emulation rom follow this direction:
- Download Tadzio's imgfs excelent tools in: http://forum.xda-developers.com/showthread.php?t=298327
- Unzip the tools along with the image in any folder.
- Rename the image to A.BIN (to make the next commands easier to type).
- Open a D.O.S. command window and perform these commands:
Code:
> NBSPLIT -emu A.BIN
(it generates two files: A.BIN.EXTRA and A.BIN.PAYLOAD)
> IMGFSFROMNB A.BIN.PAYLOAD IMGFS.BIN
(it generates the file IMGFS.BIN)
> IMGFSTODUMP IMGFS.BINAnd that's all. Files are dumped in /Dump directory
-----
Click to expand...
Click to collapse
(c) Rename ALL the 4xx files to 409 (e.g. 0408.mui -> 0.409.mui) Apply this to all files and folders (an eyasier way to do that is to search from windows for all *408* files and then rename them)
Slumpolo's suggestion
----
For step 1c) during the translation of italian rom for the mui files that resides in directory I edited also a file (simply with Supered) that has a line that pointed to the 0410 files (ea. italian) and changed this to 409.
----
Click to expand...
Click to collapse
Step 2)
Find your BASE ROM.
Step 3)
Download your Kitchen. I prefered Anichillus kitchen due to the fact that supports ROM dumping in an easy way
Step 4)
Dump ROM ( If you use Anichullus Kitchen , follow the manual but Stop BEFORE using Bepe's Package TOOL !
Step 5)
Go to DUMP folder ,(eg C:\core\extract\dump) and paste ALL the language files you have renamed from step 1c . ATTENTION you have to copy and paste ALL files from your language folder AFTER you have renamed them to 409 . REPLACE duplicate files
Step 6)
Continue with kitchen steps . For instance if you were to use Bepe's Package TOOL , go on and build the packages.
Step 7)
Edit Initflashes.dat file . Information on how to do that are in every cooking tutorial. In Intflashes.dat file you will have to translate all the links and directories according to your language files. CAUTION if you make mistakes in translation your WM6 will be crappy and programs may not start
->In order to make a good translation check your original rom, or try the WM6 emulator wth your language files and check the directory names (eg
folder Programs in Greek have to be Προγράμματα)
Step 8)
Save Initflashes.dat in unicode and remove first two bytes with a hex editor
Step 9)
Choose your OEM packages.
For GREEK USERS : If you need a greek software keyboard like the original one I have made an OEM package that allows you to do so
Slumpolo's suggestion
------
For step 9) / 10) about keyboard, you must add with a oem package also:
- dictionary in your language
- settings for your language
- t9 dictionary for your language
- for keyboard layout make this registry mod:
Code:
Registry Editor:
HKCU >> ControlPanel >> Keybd
Create a string "Locale" with "0410" vale. Everything without "Where 0410 is your country value.
------
Click to expand...
Click to collapse
Step 10)
build your rom according to your kitchen manual
I hope this helps
Good luck with your tries

I have used the same method for the italian version but you must translate also some parts of .hv files and .rgu or you must pay more attention during the translation of initflashfiles.dat because not all links and directories can be translated without .hv and .rgu editing.
My suggestion? Edit only initflashfiles.dat
Some add for your excellent tutorial:
----
For step 1b) to extract files from the emulation rom follow this direction:
- Download Tadzio's imgfs excelent tools in: http://forum.xda-developers.com/showthread.php?t=298327
- Unzip the tools along with the image in any folder.
- Rename the image to A.BIN (to make the next commands easier to type).
- Open a D.O.S. command window and perform these commands:
Code:
> NBSPLIT -emu A.BIN
(it generates two files: A.BIN.EXTRA and A.BIN.PAYLOAD)
> IMGFSFROMNB A.BIN.PAYLOAD IMGFS.BIN
(it generates the file IMGFS.BIN)
> IMGFSTODUMP IMGFS.BIN
And that's all. Files are dumped in /Dump directory
----
For step 1c) during the translation of italian rom for the mui files that resides in directory I edited also a file (simply with Supered) that has a line that pointed to the 0410 files (ea. italian) and changed this to 409.
----
For step 9) / 10) about keyboard, you must add with a oem package also:
- dictionary in your language
- settings for your language
- t9 dictionary for your language
- for keyboard layout make this registry mod:
Code:
Registry Editor:
HKCU >> ControlPanel >> Keybd
Create a string "Locale" with "0410" vale. Everything without "
Where 0410 is your country value.
Next days I'll try to release an
Ciao

At last
Very good..now i can direct all people who ask this question here.
Great initiative

Thanks
Slumpolo
Updated

Tna said:
Thanks
slumpolo can you post info about the which parts of hv files you edit?
Click to expand...
Click to collapse
I'll post everything next week. All my files are in office
Ciao

btw. as far as i know only certain wm6 builds can be translated using EMU mui files. i dont remember build no's.

Why is that ? What are the restrictions?

does it work for Universal to ?

thats what i wrote above, as far as i know(consulted with bepe) 17913 build its not supported(latest uni) it must be build ???? i remember there is 4 in build no. cannot fint irc log with that conv. with bepe

Hi and thanks for your tutorial. I try to go a different way and want to port over a hermes mui cab to get german wm6. i have some trouble of getting it done.
- the file explorer draws no softkeybar, so it is not usable. does anyone know what files i need therefore?
- the free space when installing a cab isn't displayed correctly
what have i done?
- i took the cab from asukal and removed hermes specific things
- afterwards i copy the files from the emulator image to get newest versions of the files.
if somebody want to test it - here you go:
http://www.gsm-multifund.de/holg/Making_German_Wizard.cab
i would appreciate every help.
best greetings
holg

answer from midget about builds that can be translated:
Code:
the changes from 17740-5 are not language related so the mui's work for all of them

i tried a newer rom and also got no luck with the file explorer. does anybody know what file is responsible for translating the file explorer?

No i don't... since file explorer is the least used program i didn't really care about it ...
so sorry but i can't help in that ... why don't you leave it as it is ?

i think filesys.exe.0409.mui

I think that he has found the file. The problem is about the softkey .
Try using reshack tool (it can be found in most kitchens) and open the mui file. search for the softkey
But yet I am not sure ...

yeah thanks for the suggestions
i personally like the build in filexplorer, cause it is fast and has softkey control, it's good if you just browse and open a file.
filesys.exe.0407.mui is already inserted in windows directory, so i will test with reshack,but at the moment i am a little busy.

Doubt about Files
Hi people
About the translation... i have one question.
After doing the "IMGFSTODUMP IMGFS.BIN" command, and all files are in the Dump Directory... besides the files with 4xx names, there are also some folders with 4xx names... and inside those folders are some files also with 4xx names.
Do i have to rename the folders and the files inside those folders, or just the files... or just the folders.
And one thing more... for example the folder "bbcbres.dll.0816.mui" inside these folder, one of the files called "imageinfo.txt".. inside this txt there's something written on the first line : " Module name: bbcbres.dll.0816.mui" if i have to change the name of the file inside the folder called "bbcbres.dll.0816.mui".... do i have to change this line also inside the txt ???
Thanks

how about the hardware keyboard? because I am on a German MDA Vario, Wizard of course, since we are using QWERTZ instead of QWERTY?
Will this be fixed automatically as well?
Cheers.

PauloBarreiros said:
Hi people
About the translation... i have one question.
After doing the "IMGFSTODUMP IMGFS.BIN" command, and all files are in the Dump Directory... besides the files with 4xx names, there are also some folders with 4xx names... and inside those folders are some files also with 4xx names.
Do i have to rename the folders and the files inside those folders, or just the files... or just the folders.
And one thing more... for example the folder "bbcbres.dll.0816.mui" inside these folder, one of the files called "imageinfo.txt".. inside this txt there's something written on the first line : " Module name: bbcbres.dll.0816.mui" if i have to change the name of the file inside the folder called "bbcbres.dll.0816.mui".... do i have to change this line also inside the txt ???
Thanks
Click to expand...
Click to collapse
You have to change all the *0816*. There is no need to change the folders al long as you rename the *.816* files that are included in those folders. There is no need to change the imageinfo since your are not going to replace the original one.
After renaming All the files (including the language files inside the folders) then you shoud copy only THESE files to your dumped ROM .

4irm said:
how about the hardware keyboard? because I am on a German MDA Vario, Wizard of course, since we are using QWERTZ instead of QWERTY?
Will this be fixed automatically as well?
Cheers.
Click to expand...
Click to collapse
no ... look for hades language pack to fix that, too

[Tutorial][+QueKitchen FULL Available]ErviusVisualKitchen for HERMES[Stopped]

Maybe a mod can make me a Favor and add more post to this thread if needed that will be great appreciated.
I will apreciate all the support from every people that use this kitchen in hermes to allow people get the info as clearly that a noob can install this wonderfull kitchen.
!!!!!!!!!!!!!!!!English is not my native lang, so grammar could be wrong!!!!!!!!!!!!!!!
First of all...
You will need to upgrade your .net to the latest 3.5 version and install Microsoft Visual 2008 redist DL it here
Refeer to this threads to get more info.
Thanks to Hilaireg that allows me to use his tuto as base: Dude you're da man!
http://forum.xda-developers.com/showthread.php?t=521632&page=1
Thanks to Da_G to teach me on this new location of the ervius kitchen and many more important info: Man you rules!
http://forum.xda-developers.com/showthread.php?t=474406
You can get the kitchen that works for me here...
http://rapidshare.com/files/252095433/new_visualkitchen_v_1_4_only_exe___Tools_folder_dsm_editor.rar
And the Updates can be found here:
http://forum.xda-developers.com/showthread.php?t=469420
Thanks Ervius you brings a revolution here on XDA (new 10.6 allow pkg update!!! OMG this is incredible!!! no more flash NOR and NAND unlocked to store and change SYS and XIP!!!)
thanks to BEPE too, to get this to work... This three guys maybe gonna rules the world!!!
!!Starting on!!​
Inspecting the Facility
This is the kitchen root preview: as we can saw in c:\XDA
Yes unrar it on C: and call it XDA to avoid the large name issues at CMD!
{
"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"
}
-----------------------------------------------------------------------------
EXT Folder
The External packages (EXT) folder is divided into Device Specific folders and a Shared folder.
*Device Specific folders are typically used for files (packages) that should only be applied to a specific type of the device.
-Each Device Specific folder is further divided into Operating System Build Version Specific folders and a Common folder.
ººOperating System Build Version Specific folders are typically used for files (packages) that should only be applied to a specific build (version) of Operating System
ººThe Common folder is typically used for files (packages) that can be installed on any Operating System build version.
-----------------------------------------------------------------------------
OEM Folder
The OEM folder can contain multiple Device Specific folders.
*Device Specific folders are typically used for files (packages) that should only be applied to a specific type of the device.
-Each Device Specific folder is further divided into Locale Specific folders and a Common folder.
ººThe Common folder is typically used for files (packages) that can be installed in any locale – not specific to a language.
ººLocale Specific folders are typically used for files (packages) that should only be applied to a specific locale.
-----------------------------------------------------------------------------
ROM Folder
The ROM folder is divided into Device Specific folders and a Shared folder.
*The Shared folder is typically used for kernel system files that are compatible amongst devices. (MSXIPKERNEL folder)
*Device Specific folders are typically used for kernel system files that should only be applied to a specific type of the device. (OEMXIPKERNEL folder)
-The Shared folder is further divided into Operating System Build Version Specific folders.
ººOperating System Build Version Specific folders are typically used for kernel system files that should only be applied to a specific build (version) of Operating System.
-Each Device Specific folder is further divided into Operating System Build Version Specific folders.
ººOperating System Build Version Specific folders are typically used for kernel system files that should only be applied to a specific build (version) of Operating System.
-----------------------------------------------------------------------------
SYS Folder
The system (SYS) folder is divided into Operating System Build Version Specific folders.
*The Build Version Specific folders will often contain files (packages) specific to the device DPI (Dot Per Inch) and Horizontal/Vertical display size.
-Each Operating System Build Version Specific folder is further divided into a ROM DPI, ROM Resolution, and Shared folder – providing a significant amount of flexibility during ROM compilation.
ººThe ROM DPI, ROM Resolution, and Shared folders are further divided into Locale Specific folders and a Common folder.
···The Common folder is typically used for system files (packages) that can be installed in any locale – not specific to a language.
···Locale Specific folders are typically used for system files (packages) that should only be applied to a specific locale – for example, 0409 (English).

Continue...
!!!!!Setting up the ROM and SYS!!!!!​
First of all:
As we most know there is a NATIVE NK from Da_G but even if I try to get it working as is... i cant... so Utak3r has been edited the OEMXIPKERNEL and its so good. Thanks man this is Great!!!
get it here http://forum.xda-developers.com/showthread.php?t=527454&page=4
This is just the XIP port... for 21815 build but as we must know:
OEMXIPKERNEL is the Kernel part that is device specific designed for... so we just gonna use this folder and of course... the "Romhdr.bin" and "os.nb.payload"
(so with this info we have the part of the kernel for every build we think to make) keep this files safe cause we gonna use it always. the xip.bin is not needed cause is not the meaning of this tutorial to port the XIP... so the kitchen wil ask for the file, instead that we dont want to port, so use the xip.bin that is on the build 23001 check the pic bellow.
The MSXIPKERNEL is the build OS specific kernel part... so...
The kitchen will takes the OEMXIPKERNEL (the native NK by Utak3r) and the MSXIPKERNEL for the build to be compiled, and we could have the kernel complete.
The MSXIPKERNELLTK folder (Logo Tool Kit) Is not needed, it has just a .DSM that allows the carrier to make important fixes and upgrades to thir ROMs (But even they didnt use it) so we dont need it anymore.
Well... we gonna set the kitchen with the BUILD 23001 so download the Port from TAI_Sw thanks a lot man! it was a great suport you had to all of us here!!
http://forum.xda-developers.com/showthread.php?t=531819
Unrar ir to a diferent folder cause we need to set this as a base...
I will use my kitchen as a base to reference... but first i will show you all the folders in SYS that has the 23001... so lets see what we got!
Folder missing!
get it here post #14: http://forum.xda-developers.com/showthread.php?t=531819&page=2
BTW: the adobeflash_Lang_0804 is not our lang so delet it too and replace it with the match lang.
And we need too the MSXIPKERNEL from this build check it on the pic
At this point we must to have this things
1.- Native OEMXIPKERNEL folder from Utak3er
2.- Native os.nb.payload file from Utak3er
3.- Native romhdr.bin file from Utak3er
4.- MSXIPKERNEL folder from Tai's 23001
5.- Xip.bin file from Tai's 23001
6.- SYS folders from Tai's 23001
7.- Ervius kitchen from my RS upload on first post
WHERE TO PLACE WHAT???!!!!​
Pay attention on the place you put folders the name of the tree folder will gives you the correct place, so in the pics bellow i set at ""LEFT"" how it should be at finish and in the ""RIGHT"" the tree only for reference.
NOTE: if you see a folder on the original build ported address that you have miss to organize please ask or read again and see the pictures again. (I dont know what does the folders are for, well... maybe lots of them i knew, some others i dont...)
FIRST!!!! ROM
Set romhdr.bin, os.nb.payload and xip.bin
Set OEMXIPKERNEL
Set MSXIPKERNEL
Time to sleep tomorrow this continue...

Continue...
Second SYS!!!!!!
check the tree always you dont need to create folders I already did it!!! just paste the folders on that folders... questions at the end please
Note!!!!! In Newer Kitchens... 1.7 to date, the .VM folder must be set on the following address: """C:\<YourkitchenNAme>\OEM\<YourdeviceNAME>"""" i dont know why newer kitchens cant found the .VM folder inside the common shared sys folder... Kepp it in mind!!!
Continue... next post

Continue...
Third EXT!!!!!!!!!!!!!
Fourth OEM!!!!!!!!!!
Certainly, the kitchen ask for the OEM_LANG_0409 package and i thing all the others so... paste the whole OEM to this kitchen from the josh's kitchen.
(NOTE: For other devices.... That folders OEMDRIVERS OEMoperatorspkg,OEM LANG, can get that folders if you dump a stcok rom that is the most recommended if not... you can download a kitchen for your device that kitchen must have this folders)
Setting the .bat file for Hermes device!!!!!!!​
If you make an update from the kitchen i posted(10.4) so you must to edit the .bat file as follow...
Lemme introduce y'all the quote of the guy who make this posible... (pp change) you can get from this quote the lines.
BY Utak3r:
For all those who can't get pp right:
Edit your TOOLS\kitchen_build_rom.bat and find the line with implantxip and replace it with those two lines:
..\TOOLS\osnbtool -ap xip.bin %pp%MB -y
..\TOOLS\implantxip -xip xip.bin -payload OS.nb.payload -imgstart %imgstart% -%uldr% -%nocert%
Of course you have to have osnbtool.exe in your tools directory
Click to expand...
Click to collapse
To end this process lets copy the osnbtoll.exe to tools as follow
And we are good to go!!!!
WHOOO HOOOO!!!!!!!!!!!! we finish!!!!!!!!! its already set! so this is the kitchen UI, if everything was ok the kitchen launch without troubles if you saw an error check the folders it says (SVN folders don cause troubles at starting the build proces) SO just set the device, XIP, SYS EXT and OEM and select the apps to be installed or not clickng double. HAPPY COOKING GUYS!!!!
BTW i edit the build_rom.bat in the tools folder to make it for Hermes there is an option to set the ULDR but i cant figured out how to use it on hermes... the UI may change on every update so...
try it at your OWN risk IM not responsible for damages to your device​
If you dont know what are you doing first ask to the bigger senior members that creates this before do anything... with this changes i made everything works fine.
If you cant even reading to understand this download the complete kitchen here:
http://rapidshare.com/files/253466344/XDA.rar
YOUR NOOB CHEF + QUE PPC
Want to donate for some pills? I will be very thankfull cause this headache is killing me.

BUILDS ported for this kitchen
"""WELL THIS IS THE POST FOR MY PORTED BUILDS"""
WM6.5​
My Complete Kitchen 1.4
.23001 Kitchen
My Complete Kitchen 1.6
.23004 Kitchen
Mirror 2share
Thanks to TWOPUMPCHUMP at Kaiser
.23004 SYS MSXIPKernel
.21921 SYS MSXIPKernel
Thanks to Cofeelb for the Resize fix
.21925 SYS MSXIPKernel (Please test the rom is beta buggy hopes this works fine)
Thanks to Da_G
.23008 SYS MSXIPKernel
21828 From TOPAZ Cingular thread.
.21828 SYS MSXIPKERNEL
WM6.5.X​
My Full Kitchen 1.6 Mirion B1 (the ext pkg for WOWHD is corrupted, delete it)
23034 Mirion_B1 at Rapidshare
23034 Mirion_B1 at Megaupload
Mirror 2Share
Mirror 4Share
My Full Kitchen 1.6 Mirion B4 (It has many more tools on the folder Mytools check it out!!! ready to mke a MirionB4 just load the ROM)
23053 build - Rapidshare
Ported builds Thanks to the xda-devs, xbeta, and htcpedia teams
23022 for EVK
23028 for EVK
23064 For hermes EVKMsxipkernel-23064
Inside the txt is the real link
COM5 .23504 SYS WWE+ESN+MSXIPKernel
"""Mirrors thanks to nurkamol"""
Im calling all who knows how this works to make it update constantly
Im calling to all members to read first very well ask so much more and try this paciently before do anything or ask things described above.
Thanks to all.
Last Full Kitchen 1.8.2 21609 6.5.1
Thanks to all for upgrade my ROMS

WORKING!!!! Package Repository EXT or OEM
!!!!!!!!!THE PACKAGE REPOSITORY POST!!!!!!!!!​
Many Times we can xpend hours searching for EXT or OEM packages for QVGA that works with WM6.5 or 6.1, Well this post is to fill it with them just to get them fast enough to have time for sleep
If you want to share some packages... please you can post your package with a simple screenshot of the app, OS Compatible, and a lil description, I cant post warez so... if you think it is... dont even post it its better you pm me and investigate the source, I would like to post only the thested and working packages for QVGA and works for Hermes.
Thanks Guys, this space is for all of us and to offer a source even if many people has their own hosting accounts, are places where the google cant reach easily.
Keep it up!!!!

Thanks to Josh the Mod to add this!
This is the latest +Que Kitchen it has two builds from HTC Branch
Part1
Part2
Part3
play safe

Nice1
Excellent work Amigo
Now that I'm going down the road of trying to cook my own ROMS this will be invaluable.
Anything special we need to do to Maximize Program memory?

MystaMagoo said:
Anything special we need to do to Maximize Program memory?
Click to expand...
Click to collapse
Reedit resources in dlls and muis, turn off unused drivers and services, reedit all the pngs and bmps, lots of work in rgus, remove honeycomb... that's in short

utak3r said:
Reedit resources in dlls and muis, turn off unused drivers and services, reedit all the pngs and bmps, lots of work in rgus, remove honeycomb... that's in short
Click to expand...
Click to collapse

MystaMagoo said:
Click to expand...
Click to collapse
hahahahaha^^

wow Thanx QuePPC this is a GREAT job

Even if I red all the info on that threads
i cant understand the way to set this kitchen to work! hahaha so hopefully all the chefs here turns to this awsome to get this thing working! its naked! but i will continue this...! keep in touch!!!
Its truth we must to edit the images on the wm6.5 to a simplest img... when I edit them to a high def or prettier the ram decrease considerably.
BTW wich modules and dlls can deleted.. processes and so much more it could be great to know... in devices with large RAM and ROM the WM6.5 is simply awsome. 128/256.

good job with this. i seem to have everything set up properly now other than the SYS. a little more info on what goes where would be handy. my first thoughts on this kitchen are that its too complicated to set up but im still looking forward to trying this out. i got some good ideas for my next rom and i intend to do it with this dispite having my current kitchen set up perfectly just for the challenge

very good man,thank u very much,this is really helpful!

Yes FCW i will do it right now so stay on touch!
@fcw
I will set the ROM and the sys and from OEM and EXT i took josh's kitchen packages to make it easier.
@ thanks coffee i will do my best here.

UPDATE post #2 stay on touch...!!!

what does no SVN folders present mean? i think i have the kitchen set up properly, it shows all my packages in the ext rom oem and sys folders but when i try to create the rom it comes up with that

No problem with that...
I dont know what are the svn folders for but i think they gonna surprise us with something about it... cause the new 10.6 is ready for PKG update!
But your rom finish or not?

Finished
More little things to go but with this all did... you can experiment so more! ah dont change the ULDR cause this kitchen version and our os.nb.payload is not ready to do it... or it is? ask before do it please.
BTW the kitchen makes XIP PORTS and thake the OEMXIPKERNEL ported and MSXIPKERNEL PORTED to the right place just make your new folders for new builds!
Happy cooking guys!!!!
If some links or images goes down pm me or ask here for the fix...

[PC-APP] RecModFolder - fast module to file conversion

01/04/2010 update - program can read list of modules from text file.
download link: http://www.4shared.com/file/255038195/c2b5de9b/RecModFolder_04.html
mirror: http://narod.ru/disk/19297102000/RecModFolder_04.zip.html
how to use
1. create text file RecModFolder.txt,
2. write list of modules to this file, for example:
SYS\MediaOS\wmpocx.dll
SYS\OS\dw.exe
SYS\OS\dwui.dll
SYS\OS\DwXfer.dll
3. pass RecModFolder.txt as a parameter:
RecModFolder.exe RecModFolder.txt
that's it.
and, of course, you can convert all modules in folder like this
RecModFolder.exe SYS\AdobeFlash
RecModFolder.exe SYS\AdobeFlashCodecs
there are sample RecModFolder.txt and cmd file that I use with OSBuilder
cmd file is executed from the root of my kitchen, program is in the tools\RecMod subfolder
====================================================
old post:
I developed small tool which helps me to update my kitchen with new OS build.
My device has wm6.1 kernel and I get tired with "too many modules" problem.
I know I can use RecMod to convert modules to files, but it's so slow and inconvenient:
find folder with module,
drop it on recmod.exe,
get new file out of this folder,
delete folder,
move file back,
find, drop, get, delete, move...
find, drop, get, delete, move...
GRRR!!!! =)
My tool will do all these steps for me.
I just select parameters:
1. Folder - folder with modules, for example SYS\21872,
2. Mask (optional) - any mask that is valid in windows is acceptable,
(common masks are *.dll, *.cpl, *.exe, *.mui), no mask means "*".
3. Count (optional) - how many modules to convert, no count means "convert all".
[new in v0.3] If Count is 0, program will only display all modules matching the mask,
and do not change your files.
=======================================
Example 1:
>RecModFolder.exe c:\xda\v1\SYS\21054
means - RecMod all modules in c:\xda\v1\SYS\21054 recursive
=======================================
Example 2:
>RecModFolder.exe c:\xda\v1\SYS\21054 *.exe
means - RecMod all exe modules in c:\xda\v1\SYS\21054 recursive
=======================================
Example 3:
>RecModFolder.exe c:\xda\v1\SYS\21054 *.dll 10
means - RecMod first 10 dll modules in c:\xda\v1\SYS\21054 recursive
=======================================
Algorithm
Code:
read parameters from command line
find all modules in given folder (recursive) using given mask
for each module folder
{
call RecMod
create temporary unique file name (GUID for safety reason)
move new file to parent folder and assign it temporary name
delete module folder (with all files)
rename new file, give it real module name
if (count >= requested count)
{
stop
}
}
=======================================
Installation
make sure you can run RecMod from console, add its folder to PATH or drop RecModFolder.exe to the same folder.
That's it.
=======================================
Tips
You can create shortcut to RecModFolder and drop folders on it from explorer or Total Commander. RecModFolder will convert all modules in that folder to files.
Backup your files. This tool doesn't ask any questions,
it just informs you in case of error and stops immediately.
Save log file and check it for errors.
This is console application - you can use it in bat files.
You can save output of this program to text file - add >fileName.txt to your command line.
example:
RecModFolder.exe c:\xda\v1\SYS\21054 *.dll 10 >log.txt
this command will call RecMod first 10 dll modules in c:\xda\v1\SYS\21054 recursive
and save its output to log.txt.
Do not open folders you want to delete (replace with files) in explorer (or Total Commander, FAR, etc.) while this program works.

very nice, but there is already a similar app which does it from right click menu..
see here -> recmod by OndraSter
you probably have more options on the whole process, but the other tool might be more convenient.. anyways i will try

serfer222, you know that you may be responsible for whole lots of nab made VERY bad rom releases now, lol?
hheh, thanks for that tool anyway.

nosedive said:
very nice, but there is already a similar app which does it from right click menu..
see here -> recmod by OndraSter
you probably have more options on the whole process, but the other tool might be more convenient.. anyways i will try
Click to expand...
Click to collapse
I can explain what is the main difference:
If I choose one module folder, for example
Code:
SYS\21055\SHARED\COMMON\BROWSING\browser.dll\
and select osRecmod "Recmod this folder" it will work.
but if I select parent folder
Code:
SYS\21055\SHARED\COMMON\BROWSING\
osRecmod will just delete this folder and create empty file BROWSING
in the SYS\21055\SHARED\COMMON\
So, you see, it doesn't work for me.
I want to convert all modules inside folder
Code:
SYS\21055\SHARED\COMMON\BROWSING\
in one step. I drag this folder on my tool and all modules are converted to files. That's what I want =)

pupakota said:
serfer222, you know that you may be responsible for whole lots of nab made VERY bad rom releases now, lol?
Click to expand...
Click to collapse
You know, there are a lot of such rom developers already here.
This tool will just save their time and maybe they will find out whole new world outside computer and then will quit rom development... =)

Thank you serfer222 for this application, which complements my kitchen.
By

New version - v0.3.
new option is added - if you set Count to 0 program will just display list of matching modules.
Example: I want to see a list of *.mui module folders that can be converted to files.
Command: >RecModFolder.exe d:\mega2\SYS\21874\ *.mui 0
Output:
Code:
d:\mega2\SYS\21874\SHARED\0409\AdobeFlash_LANG_0409\flashresource.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Autoupdate_Lang_0409\AutoUpdateRes_wpc.exe.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\commctrl.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\commdlg.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\coredll.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\coreres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\crypt32.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\fatutil.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\filesys.exe.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\gwes.exe.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\ieceext.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\jscript.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\miscres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\netmui.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\notify.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\OutlookLiveUpdaterResources.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\outres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\quartz.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\shellres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\shellresapps.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\syncres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\tapres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\tshres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\unimodem.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\waveapi.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\wsp.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Browsing_Lang_0409\browsres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Browsing_Lang_0409\mlang.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Browsing_Lang_0409\shdoclc.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Browsing_Lang_0409\shlwapi.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Browsing_Lang_0409\urlmon.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Browsing_Lang_0409\wininet.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\CHome_Lang_0409\cmhomeres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Entertainment_Lang_0409\bbcbres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Fwupdate_Lang_0409\MdsRes_wpc.exe.0409.mui
d:\mega2\SYS\21874\SHARED\0409\IPSECVPN_Lang_0409\ipsecvpnres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Skybox_Lang_0409\MyPhoneConsole.exe.0409.mui
d:\mega2\SYS\21874\SHARED\0409\WMWidgets_LANG_0409\riahostres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\WMWidgets_LANG_0409\wmwidgetinstallerres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0419\AdobeFlash_LANG_0419\flashresource.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Autoupdate_Lang_0419\AutoUpdateRes_wpc.exe.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\commctrl.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\commdlg.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\coredll.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\coreres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\crypt32.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\fatutil.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\filesys.exe.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\gwes.exe.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\ieceext.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\jscript.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\miscres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\netmui.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\notify.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\OutlookLiveUpdaterResources.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\outres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\quartz.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\riresdll.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\shellres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\shellresapps.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\syncres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\tapres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\tshres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\unimodem.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\waveapi.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\wsp.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Browsing_Lang_0419\browsres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Browsing_Lang_0419\mlang.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Browsing_Lang_0419\msscript.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Browsing_Lang_0419\shdoclc.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Browsing_Lang_0419\shlwapi.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Browsing_Lang_0419\urlmon.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Browsing_Lang_0419\wininet.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\CHome_Lang_0419\cmhomeres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Entertainment_Lang_0419\bbcbres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Fwupdate_Lang_0419\MdsRes_wpc.exe.0419.mui
d:\mega2\SYS\21874\SHARED\0419\IPSECVPN_Lang_0419\ipsecvpnres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\MediaOS_Lang_0419\wmploc.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\RemoteDesktopMobile_Lang_0419\wpctsc.exe.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Skybox_Lang_0419\MyPhoneConsole.exe.0419.mui
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMContactsResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMDeckResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMHSContainerResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMHSMailResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMHSMeResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMHSMessengerResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMHSSearchBarResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMHSSplashResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMHSSyncResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMMailResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMMessengerResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMServiceResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMSharedResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMSpacesResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMSyncResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WMWidgets_LANG_0419\riahostres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\WMWidgets_LANG_0419\wmwidgetinstallerres.dll.0419.mui
97 modules found.
download it from the first post.
have fun =)

keep on
good job man

I have an idea for next update.
Now I'm using 21874 with my wm6.1 kernel and just simple update it to 21876 is a headache. This tool helps me to convert modules fast, but I still must choose what should be converted. I'm lazyyyy. I did it for 21874 and want to REUSE my old work.
Idea is:
1. run application and choose good existing build AS TEMPLATE.
2. select new build folder and drink a cup of coffee.
3. my app will do the job - take old working build as template and prepare new build exactly the same way.
What do you think? Is there a program that already implement this feature or
I need to create it? (lazy question)
=)

When I start doing recmod the recmodefolder.exe shows this message "Do you have RecMod.exe in PATH?" and then stops.
What happens?

program is updated, list-mode added,
first post is updated

hi, friends, it seems an excerllent apps, but how can i download it? when i visit that link, it seems a Russian web, i even don't know one letter!
can you upload it rapishare ?

www.4shared.com link in the first post

useful App ,, Thanks
when selecting or specifying 1 module folder, it doesen't work for me.
It shows "RecMod 0 modules completed"
It works only using multiple (eg: *.mui).
Maybe the first prob. will be replaced by osrecmod, & ur tool for multiple files ,, LoL
------------
ANY idea of converting back file to module?
-Yasser-

[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