Develop Bugs

[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

[Updated 10/9/07 v1.0]Pandora's Kitchen Utility - Works on any BuildOS based kitchen

Pandora's Kitchen Option Utility
This utility will allow you to quickly save or recover your settings when customizing the options to your taste.
You will no longer have to go through BuildOS and check all your favorite programs every time you rebuild your image or install a new kitchen set.
Simply define your settings once, and from then on it's but a few clicks away
Troubleshooting:
If you receive an error when clicking "Load Kitchen":
1. The error message will display the path to the file. Check that it is formatted properly. See further down troubleshooting for more info.
2. Under the menu option File is the selection Log File. Click this to open the current log file for the kitchen you attempted to use. The last few lines should point to the option.xml file that caused the error.
3. Try running BuildOS. If it won't open, don't expect this to work. Try to isolate the trouble package and compare to other working ones.
Option.xml file formatting issues:
The file must be saved as Unicode
The file must follow the following format - noting that the entry for Tip is optional and the indention spacing is not displaying properly:
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<Items>
<Item name="Time Sync Tab" group="Registry Tweaks" checked="false">
<Tip>Add time sync Tab to Phone Settings</Tip>
<Guid type="p">2f1ae013-04e8-11dc-8314-0800200c9a66</Guid>
</Item>
</Items>
Can't load Saved Configuration:
Your configuration file may have corrupted. Retrieve a backup or recreate it.
Known MAJOR Issues:
No known
Known Deficiencies:
List sorted by in alphabetical order
Future build will integrate BuildOS functionality - single user interface for both
once updated, option.xml files no longer use <cr> for readability. No effect on performance or function.
v1.0 Beta 1 does not read / edit the SYS folder option.xml file(s).
Downloads:
Installer:
Public Beta coming soon... target release of 10/10/07
.NET Framework 2.0 Redistributable (required if you don't already have it on your PC)
RapidShare Link
Revision History:
v1.00 Beta 1: Initial limited beta release
How-to video:
RapidShare Link (updated 10/9/07)
Suggestions:
Word to the wise - BACK UP YOUR KITCHEN!! It will save you much headache should something go wrong.

I can only rub my hands in glee - really look forward to using this as it allows for formal comparative testing between builds for me ;-)

Looks great Matt,
one question, how east is it to update the OEM packages. Same as before,just put them into the kitchen folder?

allan1 said:
Looks great Matt,
one question, how east is it to update the OEM packages. Same as before,just put them into the kitchen folder?
Click to expand...
Click to collapse
Very, then run this utility to set your options to true/false as you desire, then backup the settings so you can easily re-set them if you download a whole new setup.
Super easy and super quick. Just have a few XML formatting issues to resolve before I can get this out

News?
It sounds so good....

i'm getting excited

You're a good egg, you!

are we any closer to a beta yet?

[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-

NBHImageTool 1.2 (An NBH handling tool) (new WP7 NBH support)

usage:
NBHImageTool -build|-dump param1 param2 param3
What is NBHImageTool?
NBHImageTool is a command line application to handle dumping and re-creation of .NBH files, which are data containers designed by HTC to be read by their SPL. The .nbh file contains a number of data partitions identified by their ItemID. NBHImageTool uses just a small subset of libnb, which is a library designed to handle Windows Mobile firmware images, and is in development. New! Support for WP7 unsigned NBH dumping and rebuilding
How do I use NBHImageTool?
Included in the archive are 2 batch files which demonstrate the usage of NBHImageTool, one will dump the .nbh to its .nb components, and an xml configuration file which defines the parameters to rebuild it. The other will build an .nbh from its .nb components and an .xml. Note that ImageHash.exe and TEST.pvk must be in the same folder as libnb.dll or it will fail to sign the output NBH. These files are not required if your output NBH is not signed.
What is the output from NBHImageTool?
It will generate an RUU_Unsigned.nbh and an RUU_Signed.nbh. The RUU_Signed.nbh is signed with the TEST.pvk certificate contained in the archive, and the RUU_Unsigned.nbh is unsigned.
What are the .nb files generated with unknown in the name?
These are some binary data that i'm not sure about. If you know what they are (and optionally how to manipulate them) let me know!
What can I change in the xml configuration and still obtain a valid .nbh to flash to my device?
Code:
Defaults for the following parameters are all generated by the dump function.
<NBHFile>
The Signed attribute tells NBHImageTool if it should sign your output .NBH with TEST.pvk.
The ModelID attribute must match your device ModelID. An asterisk (*) can be used to match any character.
The CID attribute must match your device CID if you are running the stock bootloader. If you are running HardSPL the CID can be any value.
The Version attribute can be any value.
The Language attribute can be any value.
The DataChunkSize attribute should match the original dumped value from your .NBH. This value defines the maximum size of data to be allocated inbetween signature chunks written by ImageHash.exe.
<Item>
The IncludedInNBH attribute determines if the program should look for this item in the input folder. The remaining attributes will be skipped if this is not set to 1.
The ItemID attribute defines the Item's type. 0x400 defines an os.nb, which contains most of the relevant Windows Mobile files. This is the only ItemID which defaults to be included in the final NBH. ItemID and FileName will only be read if IncludedInNBH is set to 1.
The FileName attribute defines the filename for NBHImageTool to grab from the input directory ([b]param1[/b]). ItemID and FileName will only be read if IncludedInNBH is set to 1.
Are there any other things I can do with NBHImageTool?
RUU_Signed.nbh and RUU_Unsigned.nbh are both generated in the output folder. You could change "TEST.pvk" in the .\tools folder to a .pvk of your choosing to sign the resulting .nbh with that certificate. Or you could use the RUU_Unsigned.nbh raw image to be processed in some other way (signed using a 3rd party tool, etc.)
What are the "unknown" .nb files generated by NBHImageTool?
These are data partitions that unknown to me! If you know what one is, please drop me a PM and let me know, I will update the library with this information.
What's this "param1", "param2" nonsense?
The parameters take different values, depending if you are running -dump or -build. The values are:
-dump:
param1: Path to the .nbh to dump. This Path must end in the filename (eg. RUU_Signed.nbh)
param2: Path to the folder to extract to. This Path must end in a folder name (eg. C:\Kitchen\dumpfolder)
param3: Path to an .xml to create with configuration data to rebuild the .nbh. This path must end in an .xml file name (eg. C:\Kitchen\xml\raphael.xml)
-build:
param1: Path to the folder to take .nb files from to build resulting .nbh. This path must end in a folder name (eg. C:\Kitchen\dumpfolder)
param2: Path to the folder to build the .nbh files in. This path must end in a folder name (eg. C:\Kitchen\buildfolder)
param3: Path to an .xml to read with configuration data to rebuild the .nbh. This path must end in an .xml file name (eg. C:\Kitchen\xml\raphael.xml)
I've run into some bug with NBHImageTool, or found an .nbh that causes odd behavior!
Please drop me a PM to let me know, I will look into it ASAP!
I'm a programmer, and libnb sounds like a .dll I might be interested in.
Please contact me via PM! I'd like to support libnb.dll and all its functions for anyone interested in using it for their own program (not for commercial use)
This program is written in VS2010/C++ Native Code.
The Visual C++ 2010 (x86 or x64, depending which version you use) Runtime is required to run it.
Thanks to everyone who helped me to understand the .NBH format, the SPL, and what parameters it finds tasteful. Cmonex, Olipro, Bepe, and Ervius and many others!
Release History:
v1.0: Initial release
v1.1: Fixed a bug when the last NBH Item is smaller than DataChunkSize resulting in a crash on dumping, changed help text and error output to reflect the need for ImageHash.exe and TEST.pvk in launch folder
v1.2: Optimizations, x64 version added, WP7 Unsigned NBH format now supported for dumping, new "Signed" variable added to XML. Path issues with imagehash.exe addressed (keep it and test.pvk in the same folder with libnb.dll)

This should be good enough, But everyone knows that if there are any errors b00n can find them, No idea how they come up wiht half the stuff they do.
This is a decent tool, that will do a lot more for everyone.
Spent the afternoon, trying everything I could think of to try and make it crash, and most of the issues have been fixed, I could not get anything else to go wrong with it, so we will have to see how it all works in the end.

Thanks Da_G - but I get an error on my Windows 7 x64 system - what am I missing??
{
"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"
}
I installed the x64 runtime files from here
DT
edit: had to install the x86 version

Hi d_train!
Sorry, I put that in my post, but it's pretty small. I'll make it bigger, to be more clear! VS2010 is a recent release and so these files are installed on almost no machines right now

Well done Da_G,
This is a great tool and here is my report of using it.
Original used NBH : Raphael O2 UK 5.12.206.1 ROM
First I tried to dump it via "1dump_nbh" and it worked without any errors and in ~1 second. 4 NB files created successfully: OS, Radio, SPL, Splash.
Here is the output XML:
Code:
<?xml version="1.0" encoding="utf-16"?>
<!--This document describes the contents of your NBH file. The IncludedInNBH attribute can be used to include (1) or exclude (0) that item from your final NBH-->
<NBHFile ModelID="RAPH12000" CID="O2___001" Version="5.12.206.1" Language="USA" DataChunkSize="64">
<ItemList>
<Item IncludedInNBH="0" ItemID="0x301" FileName="radio.nb" />
<Item IncludedInNBH="0" ItemID="0x200" FileName="spl.nb" />
<Item IncludedInNBH="0" ItemID="0x600" FileName="splash.nb" />
<Item IncludedInNBH="1" ItemID="0x400" FileName="os.nb" />
</ItemList>
</NBHFile>
Then, I tried to rebuild them via "2build_nbh". Yes, It worked great again and 2 NBH files are created in ~4 seconds. (included OS.NB only). And finally, I tried to edit XML to include all NB files and process completed successfully in ~10 seconds. (writing NBH and signing took ~3-4 seconds).
Tested in Windows 7 x86 (32bit) without installing any libraries and runtimes. (I'm using VS2010 and I think they were installed before.)
Regards

Da_G said:
Hi d_train!
Sorry, I put that in my post, but it's pretty small. I'll make it bigger, to be more clear! VS2010 is a recent release and so these files are installed on almost no machines right now
Click to expand...
Click to collapse
lol now I see it
thanks for this great tool
DT

Here is the XML from a Leo ROM
Code:
<?xml version="1.0" encoding="utf-16"?>
<!--This document describes the contents of your NBH file. The IncludedInNBH attribute can be used to include (1) or exclude (0) that item from your final NBH-->
<NBHFile ModelID="PB8110000" CID="CSL__001" Version="1.72.831.1" Language="USA" DataChunkSize="64">
<ItemList>
<Item IncludedInNBH="0" ItemID="0x301" FileName="radio.nb" />
<Item IncludedInNBH="0" ItemID="0x380" FileName="radiocust.nb" />
<Item IncludedInNBH="0" ItemID="0x200" FileName="spl.nb" />
<Item IncludedInNBH="0" ItemID="0x600" FileName="splash.nb" />
<Item IncludedInNBH="1" ItemID="0x400" FileName="os.nb" />
<Item IncludedInNBH="0" ItemID="0x920" FileName="conf.nb" />
<Item IncludedInNBH="0" ItemID="0x900" FileName="extrom.nb" />
<Item IncludedInNBH="0" ItemID="0x610" FileName="unknownsplash1.nb" />
<Item IncludedInNBH="0" ItemID="0x611" FileName="unknownsplash2.nb" />
</ItemList>
</NBHFile>
So do I assume that if I wanted to replace the splash screens I enable 0x600, 0x610 and 0x611?
Is there a utility that allows me to view and or convert WVGA splashscreen nb files?
Thanks again Da_G
DT

Yes, if you wanted to replace the splash screens you would enable the IncludedInNBH attribute for those items.
You would need to dump these .nb splash files to an editable format (such as .bmp) to work with them, and then re-create the .nb file to feed into the build function, in order to replace them in the final .nbh.
I will soon look at incorporating an automatic .nb HTC Splash Image Converter, to aid with replacing these splash images easily. I think the tool "nbimg" by pof may be able to work with them, for the time being. It accepts manual parameters for the width and height of the image. If it doesn't work, please let me know if you find or know of a tool that does, and I will update the first post until I can program a function for this tool to handle it. Thanks

Da_G said:
Yes, if you wanted to replace the splash screens you would enable the IncludedInNBH attribute for those items.
You would need to dump these .nb splash files to an editable format (such as .bmp) to work with them, and then re-create the .nb file to feed into the build function, in order to replace them in the final .nbh.
I will soon look at incorporating an automatic .nb HTC Splash Image Converter, to aid with replacing these splash images easily. I think the tool "nbimg" by pof may be able to work with them, for the time being. It accepts manual parameters for the width and height of the image. If it doesn't work, please let me know if you find or know of a tool that does, and I will update the first post until I can program a function for this tool to handle it. Thanks
Click to expand...
Click to collapse
Thanks Da_G - found the nbimg tool and it was able to convert the splash.nb file to bmp, but not the unknownsplash1.nb and unknownsplash2.nb files
Thanks again for your ongoing contribution to these forums
DT

Hi Da_G
Maybe you create Tool for file *.tsw - You build good and faster tools!
Thanks

Great
Great tool Da_G, will be testing it in a bit. looking forward to developers incorporating this into new Kitchens

Thanks Da_G, works like a charm on my XP Pro machine.
I send you some beer money so you can order La Chouffe from Holland.
Congrats

nbimg tool for Leo
nbimg tool by pof for splash works for my Leo but needs recalculating of the padding.Works with the following parameters:
nbimg -p 18400 -w 480 -h 800 -F nameofphoto.bmp -T 0x601 -S 64 -D PB8110000
http://forum.xda-developers.com/showthread.php?t=668862
Would be very nice if you could automate the process.
Congrats for your perfect tool!!

Hi,
Which are the advantages os this utility compared to nbhutil from olipro?
Thanks

good job Da_G! gonna try it later.
thanks

mac_es said:
Hi,
Which are the advantages os this utility compared to nbhutil from olipro?
Thanks
Click to expand...
Click to collapse
NBHUtil and HTCRT need configuration files provided by other users that often lack support for new devices and are incomplete/inaccurate. This utility instead can make its own building configuration file from the NBH itself so you can rebuild any NBH without having to desperately search for the correct configuration file that supports your device.

Thank you for this Da_g your work is always appreciated
Excellent tool works flawlessly
Transaction ID: 5LV66560PR5951831

@mac_es:
As airxtreme already stated, one of the bigger drawbacks of previous tools is that you had to come up with a configuration file somewhere. This one will automatically generate one from any ROM for your device. This has the advantage of picking up on any ItemIDs that we hadn't previously seen in a ROM or didn't exist until recently (like radiocust, radioconf)
I'm working with l3v5y to add another nice feature, automatic dumping of a splash screen .nb to .bmp, and then automatic rebuilding of the splash screen .nb from the .bmp (i'll probably add a flag to the xml for that auto rebuild from bmp) - this way you can work directly on the .bmp and avoid unneccessary conversions every time you make an edit to it.
I'm looking at making a routine to pull the radio.nb version out too, and store it in the xml, just for informational purposes.

Very nice work Da_G. Really appreciate the time and effort you put into doing this stuff for us.
Just one question, now that we have this tool for getting the .nbh, what is a good option for us at the moment to get the packages extracted from the .nbh?

xidump from Bepe is a fine tool for this, it can work directly with the os.nb, and output directly from it.
Unfortunately it has no build support yet, that is my next target, to replace NBImageTool with a new version that handles dumping and building

RecMod (Module to File) By denominator77

Thanks to denominator77 we now know how to recmod some modules
denominator77 said:
1. FixRecMod.exe your_dll_folder
2. LordPE -> PE Editor -> choose the recmoded dll -> get ImageBase value -> add the value to BaseOfCode and BaseOfData -> Save&OK
Sometimes ImageBase is not properly restored by FixRecMod.exe. If IDA has not identified any imported function, then try the following steps to fix the addresses:
1. Go to .pdata segment
2. There will be a list of "Function start" and "Function end" definitions
3. Take the first "DCD 0xNNNNZZZZ ; Function start"
4. In the most cases ImageBase will be 0xNNNN0000
5. Run LordPE and update ImageBase, BaseOfCode, and BaseOfData
download to fixrecmod
View attachment 487836
Click to expand...
Click to collapse
Link to LordPE
http://www.woodmann.com/collaborative/tools/index.php/LordPE
to get you all starting I did some modules .
http://dl.dropbox.com/u/5011238/Data/SecurityCore.7z
http://dl.dropbox.com/u/5011238/Data/MSXIPKERNEL.7z
http://dl.dropbox.com/u/5011238/Data/Phone.7z
http://dl.dropbox.com/u/5011238/Data/Start.7z
http://dl.dropbox.com/u/5011238/Data/APPPLATFORM.7z
if a file isn't working then use the above steps (quoted)
edit: updated the DL links.

I'm sorry to bumb such an old thread, but please could you try recmodding the SystemInfo exes and dlls from the ShellDogfood package? They are really old, but there is a possibility that they could run on current version of WP. And if they don't run, is there a way to debug them?