WM6 ROM Cook Guide for Novice[EN] - HTC Tornado

Translated from Chinese, any questions please refer
http://www.koxo.cn/bbs/thread-7146-1-1.html.
You can down here.
91files
rapidshare
All tools and pics contained on the zip.
________________________________________________
TXT Preview
WM6 ROM Cook Guide for Novice
Cook a ROM is easier than you thought.
By challhsu
2007.08.03
Translated from Chinese
Take my WM6.EN.Build.AnniversaryofP.L.A.Special.SP for example.
All tools needed prepared, except the copyright protection software.
Copyright Tools needed:
EmEditor
UltraEdit
And this may help you advanced:
WinCE CAB Manager
Steps:
ONE Decompress the ROM
1.Put the file nk.nbf to the folder where this guide in.
2.Run the TyphoonNbfTool.exe on the folder T。Like this pic,click the文件 (File).
3.click 打开NBF…(open NBF…),find nk.nbf.
4.select nk.nbf,and click打开(Open).
5.right-click on the OS,choose Dump decrypted.
CAUTION:
Not all the ROMs only have OS, still have others like IPL SPL GSM Splash Screen,this guide这only have how to cook the OS.
6.just click 保存(S)(save(s)).
7.If it successed, you will see:
8.back to the folder where nk.nbf is, and you will find a new file OS.n_d.
8.rename OS.n_d to OS.nb。
9.run decompress.bat,to decompress the ROM. You will see a cmd windows,just wait for the windos disappear. And then, you will find a new folder and 6 new files. OK, the ROM is decompressed.
Dump this folder contain all files of the ROM, If you just want to add or delete some files, now you can.
default.reg and user.reg formed the registry of the ROM.
initflashfiles.dat we called文件发行表,
we do not need to edit the other 3 files dump_MemoryMap.txt imgfs_raw_data.bin imgfs_removed_data.bin.
TWE Edit the ROM:
10.Add or Delete files:
Enter the folder dump,you can see many folders and files. Folders contains modules(模块) while files means files of ROM.
If you do not choose the Hide System Files(隐藏受保护的系统文件),you can find more hide folders and files. They are all system files, do not edit them unless you know what you do.
Example:If we want to cancel the STK_UISP’s English support, we can find the file STK_UISP.exe.0409.mui on the forlder dump, and delete it.
Similarly, you can also add or delete other functions by add or delete the right folders and files. But advanced functions may need several files and need to edit the reg and initflashfiles.dat(对于高级功能,往往需要删除多个文件,并且需要同时对注册表和文件发行表进行操作。
Be sure you know what you are doing.
11.Edit the registry:
At this step, you need EmEditor UltraEdit and Notepad2.exe.You can also take other tools to instead them.
Back to the folder where default.reg is.
(1)code fo .reg(注册表编码):
Open the default.reg by EmEditor, and choose file(文件)—save as(另存为), you can see a window like the pic below. chooseUTF-16LE 添加Unicode签名(BOM) 无更改, and save.
After save, the size of the fils approximately twice that before.
Take the user.reg to UTF-16LE too.
(2)Edit the registry:
Open default.reg and user.reg by Notepad2.exe.
Notepad2.exe can use more eye-catching to see all keys, it is not easy to confuse.使用Notepad2.exe可以比较醒目的看到各个键值,不容易混淆。
And then, you can edit the reg.
Strongly recommends the novice take some simple operate for test.
There list some simple keys can be used for pracise:
Bluetooth name:
HKEY_LOCAL_MACHINE\Ident\Name
Automatic check time(自动对时)
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL下NITZEnable 0 means close while 1 means opern
Change the operator name:
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\RIL\OPERATORNAMES
中国移动的网络号"46000",value data随便填你要显示的字符,联通的网络号为46001
12.edit initflashfiles.dat文件发行表的修改:
文件发行表名称为initflashfiles.dat,open it by Notepad2.exe or other. And add or remove what you want.
Example:
root:-Directory(“My Documents”) means MD My Documents
Directory(“My Documents”):-Directory(“My Ringtons”) means MD a folder My Ringtons on folder My Documents.
Directory("\Windows\Start Menu"):-File("Speed Dial.lnk","\Windows\scut.lnk") means copy the scut.lnk on \windows to \windows\start menu, and rename it to speed dial.lnk
Three compress the ROM:
13run compress.bat,when you see press any key to continue… ,do it,until the cmd windows disappeared. If no error, you will take the new OS.nb.
But if you find error, you must check and fix it.
@ECHO off
set _FLATRELEASEDIR=.
copy default.reg boot.rgu /y
t\rgucomp.exe -b
pause——this is the first press any key to continue…,if you see error before there, it means there must be some errors on default.reg
copy boot.hv default.hv /y
copy user.reg boot.rgu /y
pause——this is the second press any key to continue…,if you see error before there, it means there must be some errors on user.reg
t\rgucomp.exe -b
pause
copy boot.hv user.hv /y
del boot.rgu
del boot.hv
copy default.hv dump /y
copy user.hv dump /y
copy initflashfiles.dat dump /y
pause
t\buildimgfs
pause
t\make_imgfs os.nb –nosplit
Example:
Though the text, we know, this error appears before the first press any key to continue…so,we know there must be some error on default.reg.
Go on, within a few lines of 3.means the error is on the 3 line of default.reg
Open default.reg by UltraEdit-32,you will see”***DOS**?”,click”N”.
Then, you can see a test like the pic below.
[HKEY_CLASSES_ROOT\.pkg]
@=“package”——there should [email protected]=”package” 这里和其他对比可知,引号应为半角,这里错用全角。应为@=”package”
Fixed the error, and run compress.bat again, till no errors appeared. And you can take the new OS.nb.
14enter the folder T, and run nb2nbf_tornado.exe.
Steps:
1.Model ID;
2.Language;
3.CID;
4.Output file;
5.Click;
6.Find the OS.nb;
7.Choose OS;
8.Click at here, it will take a number, it’s important, be sure don’t change it;
9.click Translate, build the new nk.nbf。
You will see:

``╭⌒╮ ..',', ',',','
╱◥██◣''o┈┄o.'',,',.
︱口︱ 月 | '',,',.o┈-┄o
╬╬╬╬╬╬╬╬╬╬╬╬╬-

支持一下,不过兄弟忽略了一点,你用的rom定制工具都是中文版的,在老外的电脑上未必能正常显示,例如“打开”,“文件”等菜单很可能都是显示"??",其实这些工具都是国人汉化得来的,让老外们用原版好了,可以免不少麻烦!

bluehanson said:
支持一下,不过兄弟忽略了一点,你用的rom定制工具都是中文版的,在老外的电脑上未必能正常显示,例如“打开”,“文件”等菜单很可能都是显示"??",其实这些工具都是国人汉化得来的,让老外们用原版好了,可以免不少麻烦!
Click to expand...
Click to collapse
但是有图片啊,位置总看得见吧。。。。。这个教程是从我的中文教程翻译过来的。。
we talked about that EN users may can't understand it. And I said,"They can follow the pics.'

challhsu said:
但是有图片啊,位置总看得见吧。。。。。这个教程是从我的中文教程翻译过来的。。
Click to expand...
Click to collapse
no offense, but might i ask that we keep this thread, and maybe this entire forum readable and understandable by other people also?

bogdi1988 said:
no offense, but might i ask that we keep this thread, and maybe this entire forum readable and understandable by other people also?
Click to expand...
Click to collapse
Yeah, at least TRY to also translate your q's / posts into English. No problem if you aren't a native English speaker and make mistakes.

wm6 bin
What if you a wm6.bin file to start with?
How can we get the nbf file from there. I assumed that nbf file maybe in the wm6.bin But I can not explore the bin file (tried virtual drives, creating a cue file and mounting it, even tried to convert it to ISO..nothing seems to work).
directly: how do we go from wm6.bin to os.nbf
thanks for any advice

Menneisyys said:
Yeah, at least TRY to also translate your q's / posts into English. No problem if you aren't a native English speaker and make mistakes.
Click to expand...
Click to collapse
Can they also post the chinese version of their question, in addition to the Englishm so chinese speakers can help when their English doesn't work?
Some things don't always translate well, so it could save some frustration.

When using the tools, Chinese becomes gibberish even if I enable non-unicode support for it.

challhsu said:
但是有图片啊,位置总看得见吧。。。。。这个教程是从我的中文教程翻译过来的。。
we talked about that EN users may can't understand it. And I said,"They can follow the pics.'
Click to expand...
Click to collapse
不要乱发废帖, your englsh is misleading !!!! please respect XDA-developer site and do not copy others!!!!!!!!!!!!!!!!!!!!!!!!thank you and wellcome to the site!!!!!!!!!!!!!!!!!!!!!!!!!!!

Related

Share your OEM Packages for Faria ROM Kitchen

Hey all,
So that we don't all have to reinvent the wheel, is it possible where we could share OEM Package setup info to be used in the Faria ROM Kitchen. I know a number of your are adding your own packages, and this could save a lot of work for those of us just starting to look at customizing this tool. Use ftp://ftp.xda-developers.com/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf to read up on how to create OEM packages and how they work.
What I'm thinking is that this thread could be a repository for packages (not for requests, but for packages people want to share). Bascially you would reply to this thread with what the package is for, and any special information and setup (or things people may want to look at and change), and then attach a zip file (or pointer to the package file) that people can then download and put into their devwiz folder. If its for a commercial (non-free) program, leave out the commercial program / dlls but just to have the other files setup and instructions on what to put into the folder could be very useful for people.
When you provide the packages, try to provide it with the original package.rgu and/or package.dsm filenames (not with the GUID that was generated for you). People will then be able to just run the buildos.exe and the GUID will get created for them without changing filenames. Then just edit the options.xml file to use the newly generated GUID.
so screenshot + cab + short info + status: freeware/shareware/etc. would be fine?
mfrazzz said:
Hey all,
So that we don't all have to reinvent the wheel, is it possible where we could share OEM Package setup info to be used in the Faria ROM Kitchen. I know a number of your are adding your own packages, and this could save a lot of work for those of us just starting to look at customizing this tool.
What I'm thinking is that this thread could be a repository for packages (not for requests, but for packages people want to share). Bascially you would reply to this thread with what the package is for, and any special information and setup (or things people may want to look at and change), and then attach a zip file (or pointer to the package file) that people can then download and put into their devwiz folder. If its for a commercial (non-free) program, leave out the commercial program / dlls but just to have the other files setup and instructions on what to put into the folder could be very useful for people.
The only tricky thing here would be the guid for the files. I'm still new to this, so if someone has an idea how to handle that (maybe the person does the package.rgu and runs the program where it generates the guide, then unzips the files and modifies the guid to the new one in the right places).
Click to expand...
Click to collapse
The GUID is so simple, if you to use a package, just go to http://www.famkruithof.net/uuid/uuidgen . Then you just get a new GUID and paste it in all the different palces in the package, then you dont have to chnage file names then have them chnaged again by buildOS
I thik this is a good idea, would be good to share and also good for problem finding, cus i have one that i cant for the life of me get the today plugin to work how it is meant to!!!
GSFinder Package
[... This package has been updated and can now be found in post 23 of this thread ...]
This is a package for GSFinder. This is a freeware file manager (like TotalCommander).
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
MoDaCo NoData
[... This package has been updated and can now be found in post 23 of this thread ...]
This is a package for MoDaCo NoData. This is a freeware program that allows you to turn off and on what data sources will work on your device (so if you don't have a GPRS plan, you can turn off GPRS so your phone will not use it).
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
mUn Keyboard Skin
This is a package for the mUn keyboard skin. This is a freeware skin file to modify the look of the on screen keyboard to be like what is in the mUn aRTM WM6 rom.
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
NOTE: If you have other keyboard skin files in your OEM directory, you may get an error when you build this initially (or if more than one is selected). You can only have one of the keyboard skins selected.
XPlore Keyboard Skin
This is a package for the XPlore keyboard skin. This is a freeware skin file to modify the look of the on screen keyboard to be like what is provided for the XPlore 2.0 WM6 rom.
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
NOTE: If you have other keyboard skin files in your OEM directory, you may get an error when you build this initially (or if more than one is selected). You can only have one of the keyboard skins selected.
mfrazzz said:
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
Click to expand...
Click to collapse
Thanks for putting this together!
I tried building via your instructions, but got an error (buildos.exe crashed). I deleted the options.xml file and then re-ran the build and it worked. Then copied back in an options.xml file and edited the GUID and it ran fine.
I'd noticed this when I was building another package. In my experience, I have to do a build without the options file, let the [GUID].dsm file get built, then create the options.xml file with the correct GUID in it and then rerun.
saeba said:
Thanks for putting this together!
I tried building via your instructions, but got an error (buildos.exe crashed). I deleted the options.xml file and then re-ran the build and it worked. Then copied back in an options.xml file and edited the GUID and it ran fine.
Click to expand...
Click to collapse
Yep I figured this out an hour ago. The options.xml should be renamed until the first run of builos.exe completes, then rename it back and change the guid inside the file.
I'll redo the packages tomorrow and update the instructions on them.
mfrazzz said:
Yep I figured this out an hour ago. The options.xml should be renamed until the first run of builos.exe completes, then rename it back and change the guid inside the file.
I'll redo the packages tomorrow and update the instructions on them.
Click to expand...
Click to collapse
Can i jst say that the chnace of the same number being used again in you kitchen is really high, so you should not have to chnage it!!! Try run the buildOs without chnaging anything!
Has anyone figured out how to move files yet?
RickoT said:
Has anyone figured out how to move files yet?
Click to expand...
Click to collapse
The initflashfiles.txt moves the files (doesn't just make duplicates). So you just have to put a line in for everyfile to "move" it to a different location. The next post will be for BatteryStatus and you can look at that one as thats what it does. All the graphic images are moved into a directory it creates.
Battery Status Package
[... This package has been updated and can now be found in post 23 of this thread ...]
Here is the package for Battery Status. I initially put this together but had some errors in how I did things. Thanks to ADB100 for cleaning it up! This is the same one he reposted for me in the Faria Rom Kitchen thread.
ALso going with Funman's point that its unlikely to hit a duplicate GUID, so I'm leaving the GUID alone. So just extract to the OEM directory and you are ready to go.
This package contains Battery Status 1.04.202 Beta 3 Build 0195 (latest version at the time of this posting).
Reposting with generic Registry Entries (removing ADB100's custom settings he mentions in his post below)
WM5torage Package
[... This package has been updated and can now be found in post 23 of this thread ...]
Package for WM5torage (version 1.73). Just unzip in your OEM folder.
Note, the package puts a shortcut in the \Windows\Start Menu\Accessories folder for WM5torage. Edit the initflashfiles.txt if you want the shortcut to be located someplace else.
mfrazzz said:
Here is the package for Battery Status. I initially put this together but had some errors in how I did things. Thanks to ADB100 for cleaning it up! This is the same one he reposted for me in the Faria Rom Kitchen thread.
ALso going with Funman's point that its unlikely to hit a duplicate GUID, so I'm leaving the GUID alone. So just extract to the OEM directory and you are ready to go.
This package contains Battery Status 1.04.202 Beta 3 Build 0195 (latest version at the time of this posting).
Click to expand...
Click to collapse
I should note that it is pre-configured with the following options:
General Tab - Show CpuSpeed, Show Mobile Operator
Indicator Tab - Show more Indicators, Use Small Fontsize, Show Powerdrain, Show Temperature
Tools Tab - DeviceLock on Wakeup, Lock if Display..., Backlight fix - 30-seconds
Omap Tab - Overclock to 247Mhz, Overclock on Wakeup, Remember last CpuSpeed, Overclock after reboot
Traylaunch Tab - All disabled
Not sure this will suit everybody so be warned...
Andy
Adobe Reader LE
[... This package has been updated and can now be found in post 23 of this thread ...]
Package for Adobe Reader LE. This is the "faria Adobe Reader" cab thats been posted, but then I've altered the .rgu to fix the registry entry for opening docs that have spaces in the name (Thanks ADB100 for pointing that fix out), and made a couple of fixes to the initflashfiles.txt (it had moves for files that didn't exist and I've added where it moves a shortcut into \Windows\Start Menu\Programs\Accessories
Just unzip into your OEM directory.
ADB100 said:
I should note that it is pre-configured with the following options
[... snip ...]
Not sure this will suit everybody so be warned...
Click to expand...
Click to collapse
I've reloaded the zip file in my post above for Battery Status and put the registry entries back to generic like a fresh install. If you want specific settings, then install BS, tweak it to your heart's content, then dump out the registry entries and replace them in the .rgu file.
mfrazzz said:
Package for WM5torage (version 1.73). Just unzip in your OEM folder.
Note, the package puts a shortcut in the \Windows\Start Menu\Accessories folder for WM5torage. Edit the initflashfiles.txt if you want the shortcut to be located someplace else.
Click to expand...
Click to collapse
Sorry mate but your package is not right! The .rgu was not setup right!
funman said:
Sorry mate but your package is not right! The .rgu was not setup right!
Click to expand...
Click to collapse
Arrrgh! Sorry about that. I was putting that one together and got interupted with a concall at work, and some other things. I went back to working on it, and I guess I didn't edit and fix what I thought I had done... Sheesh...
Thanks...
mfrazzz said:
The initflashfiles.txt moves the files (doesn't just make duplicates). So you just have to put a line in for everyfile to "move" it to a different location. The next post will be for BatteryStatus and you can look at that one as thats what it does. All the graphic images are moved into a directory it creates.
Click to expand...
Click to collapse
Are you sure, because I think I read in faria's rom thread that it copies the files, not moves them, (Unless im utterly retareded and misread it, which is very possible)

[RELEASE]{02/08/2007}MODIFIED Molski Devpack Kitchen for HTC Tornado [by Duke]

Hello ALL!
Here is the long awaited HTC Tornado ROM kitchen
This Kitchen is in actual fact the Molski DEVPACK kitchen but its been MODIFIED by myself, Duke_Stix in order to be compatible with the HTC tornado and to make rom editing and cooking easier for EVERYONE!
Please note, before anybody starts pointing fingers, FULL permission was obtained from molski himself before any modifications were made and full permission was obtained in order for me to release this kitchen as the initial kitchen was of course, by MOLSKI!
This was the first kitchen that i learnt to use so it was the first kitchen i modified!
There will also be a modified CORE kitchen released soon too once i can iron out any and all bugs.
Anyway:
Pretty simple to run really. heres a few instructions to get you all started:
Download the attached file: Molskis_Devpack_modified_for_tornado_by_duke_stix.exe
READ THE PDF FILE THAT IS IN C:\DEVPACK\tools\batch\readme
Here are steps:
1) RUN the executable file, you should end up with TWO folders, DEVPACK and Molski.biz Devpack. MOVE the 'DEVPACK' folder to the ROOT of your C: drive.
2) Place ANY nk.nbf that you wish to 'unpack' into the source folder of the DEVPACK folder. so.....
' C:\DEVPACK\source ' Contains your NK.NBF file
3) Go to your desktop and into the 'molski.biz devpack' folder, this has lots of little shortcuts in it.
4) first of all, click the 'dump rom' script.
5) Let it do its thing
6) in the C:\DEVPACK folder there should now be a new folder called......ROMDUMP! (<-- guess whats in here?!)
7) Edit as much as you wish, dont forget to get rid of the first two bytes in the initflashfiles.dat file before you build rom again
8) once you've clicked the 'build rom' script go back into c:\devpack\tools and in there should be nb2nbf_tornado.exe
9) open that, dont touch anything atthe top apart fro the output field, here, I would suggest selecting your desktop and you MUST issue the file name as 'nb.nbf'
10) below that click the tick box next to 'File #1:' it will allow you to select 'file #1' point it to c:\DEVPACK\ROMDUMP and to the file called 82040000-OS.nb
11) back in the nb2nbf program select 'OS' under image name
click translate
go to your desktop, move the nk.nbf file there into C:\DEVPACK\tools\RUU_2001
run the 'ROMUpdateUtility.exe'
and away you go! should start flashing
IT IS IMPORTANT THAT YOU READ THE README FILE! i will also attach it to the post
also, anyone willing to donate can send any paypal donations to [email protected] and reference them 'duke'! very much appreciated!lol
MIRROR:
http://www.megaupload.com/?d=VWCLXM6Z
ENJOY!
post any questions here
AND DO NOT FORGET TO READ THE README FILE!!!!!
ALSO READ: http:\\www.molski.biz
HAPPY COOKING!
duke_stix said:
How to use this Rom Cooking Pack:
I tried to make everything as simple as possible, still you definitely need to know what you are doing!
Step 1:
Extract the nk.nbf file from a Rom archive (all Rom archives can be opened with tools like WinRAR) into the X:\DEVPACK\source directory.
Step 2:
Execute the DUMP_ROM script when the script is finished a ROMDUMP folder is created in X:\DEVPACK, with all the .nb files found in the nk.nbf file, the 80040000-OS.nb file will be splitted into 2 template (.bin) files and the contents of the OS templates is placed in the “dump” folder.
Step 3:
When the script is finished you can start adding and deleting (watch out what you delete!) files in the dump folder.
Step 4:
Editing the initflashfiles.dat file!
Execute the EDIT_INITFLASHFILES script so the file gets copied to the ROMDUMP directory, a backup of this file is placed in the Backup folder inside the ROMDUMP directory!
This is a very important file, when the Wizard gets a hard-reset or is flashed to another Rom, this file builds the directory structure, copys files from Windows to (as example) the Program Files directory.
These are some examples from the initflashfiles.dat file:
root:-Directory("My Documents")
Directory("My Documents"):-Directory("My Pictures")
Directory("\Windows\Start Menu")ermDir("Programs")
Directory("\Windows\Start Menu")ermDir("Settings")
Directory("\Windows\Start Menu"):-File("Messaging.lnk","\Windows\tmail.lnk")
Directory("\Windows\Start Menu\Programs"):-File("File Explorer.lnk","\Windows\fexplore.lnk")
Directory("\My Documents\Templates"):-File("love.gif","\Windows\love.gif")
As you can see, not so tough as it looks, I am not going to explain every single line of this file, but will give you one example….just to make things a little bit easier to understand!
All files from the “dump” folder are basically placed in \Windows and get copied to other directories from this point, so when a shortcut is copied from \Windows to \Windows\Start Menu\Programs you will have a shortcut in both directories (but that’s not a big deal!).
I am going to explain this line, to let you know what this line actually does
Directory("\Windows\Start Menu\Programs"):-File("File Explorer.lnk","\Windows\fexplore.lnk")
The shortcut fexplore.lnk in \Windows gets copied to the \Windows\Start Menu\Programs directory and gets renamed to File Explorer.lnk
Very easy….isn’t it? J
So…after adding all files to the “dump” directory, adding the lines of the added files (IF needed) to the initflashfiles.dat file you can save this file, make sure the last line in this file is a blank line (otherwise your device will be stuck at the second Splash Screen)!!
Example:
When you want to add a program named ABC.exe to \Start Menu\Programs, just copy the ABC.exe file to to the “dump” folder and place a shortcut named ABC.lnk in the “dump” folder and add a line for ABC.lnk into the initflashfiles.dat file.
To create a shortcut for ABC.exe, simply open Notepad, create a line like this:
24#"\Windows\ABC.exe"
(the number can be different), save it as ABC.lnk and add this to the initflashfiles.dat file:
Directory("\Windows\Start Menu\Programs"):-File("Alphabet.lnk","\Windows\ABC.lnk")
In this example the shortcut ABC.lnk, that points to ABC.exe gets placed in Programs with the name Alphabet.
After saving the initflashfiles.dat file, open the file in WinHex and remove the first 2 bytes (FF FE)!
If you don’t remove these 2 bytes your device will also be stuck at the second Splash Screen!!
After removing the 2 bytes and saving the file you can copy it to the “dump” folder (overwrite the original initflashfiles.dat file….don’t worry, you still got the backup of the original file in the Backup folder)!
Step 5:
Editing the HV Files!
Okay, let’s say that the application used in the example (ABC.exe) has a few Registry Values and will not work without it, therefore we will need to edit the default.hv and/or user.hv files.
Execute the script CREATE_RGU_FILES, this will copy the default.hv and user.hv files from the “dump” folder into a directory called HV Files in the Romdump directory and convert the 2 .hv files into .rgu files so we can edit them with notepad.
When editing .rgu files there are 4 things that are very important!
Turn off Word Wrap in Notepad
The 1st line is a blank line, type “REGEDIT4” (without quotes) on this line
Make sure the last line of the file is a blank line
Make sure the files are saved in Unicode and not in ANSI
The Windows Mobile Registry has 4 keys:
[HKEY_CLASSES_ROOT] à These Registry keys gets insert in the default.rgu file
[HKEY_LOCAL_MACHINE] à These Registry keys gets insert in the default.rgu file
[HKEY_CURRENT_USER] à These Registry keys gets insert in the user.rgu file
[HKEY_USERS] à These Registry keys gets insert in the user.rgu file
When you are finished editing the .rgu files, execute the CREATE_HV_FILES, watch properly of the files get converted without errors, if everything went okay, copy the default.hv files from the HV Files directory to the “dump” folder (overwite the original files….don’t worry, you still got the backup of the original file in the Backup folder)!
Step 6:
Okay, by now we have extracted and dumped the nk.nbf file, added and/or removed files from the “dump” folder, edited the initflashfiles.dat file, added registry values in default.hv & user.hv and copied the 3 edited files to the “dump” folder.
Now we are (finally…) ready to build the Rom!
Execute the script BUILD_ROM and wait till it’s finished (will take a couple of minutes depending on the speed of the computer).
This script will add the modified “dump” folder to the OS template files (.bin files) and when that is done it will build the 8004000-OS.nb file from the OS template file.
[\QUOTE]
Click to expand...
Click to collapse
Click to expand...
Click to collapse
reserved yet again
Thanks a lot for this tool i'll look that when i will go at home.
Thanks for all your job
can't get to megaupload.
can you upload it to rapidshare? thanks for your work.
ericjm said:
can't get to megaupload.
can you upload it to rapidshare? thanks for your work.
Click to expand...
Click to collapse
http://rapidshare.com/files/46589256/Molskis_Devpack_modified_for_tornado_by_duke_stix.exe.html
burkay said:
http://rapidshare.com/files/46589256/Molskis_Devpack_modified_for_tornado_by_duke_stix.exe.html
Click to expand...
Click to collapse
thanks dude!
anyone tried this yet then?!
\
im awaiting feedback!
When I tried to dump rom, I get this
Splitting 80040000-OS.nb into .bin files....
Unable to open source image [80040000-OS.nb]
Creating Dump directory....
Dumping Rom content into dump directory....
Please wait a couple of minutes, depending of the speed of your computer!
Dump folder is ready in ROMDUMP directory!
Press any key to continue . . .
Why is it that I am unable to open source image ?
Looks like duke stix forgot to add a rename command in the batch file.
The wizard NBF WDATA start address for the OS is 80040000 and the tornado WDATA start address is 82040000, so rename 82040000-OS.nb to 80040000-OS.nb and it should work.
Phil
jm012a9749 said:
Looks like duke stix forgot to add a rename command in the batch file.
The wizard NBF WDATA start address for the OS is 80040000 and the tornado WDATA start address is 82040000, so rename 82040000-OS.nb to 80040000-OS.nb and it should work.
Phil
Click to expand...
Click to collapse
Actually im dumping using Mozbi Devpack for Wizard, thought it is the same, it works now.
Thanks
oioi
I'll get to changing that right now. didnt notice that!
Good tools and good explanations.
I dumped I rebuilt a Qtek ROM today for my wizard, and the advices of this thread were the biggest help.
Thanks and well done.
Customized ROM hanging in spash screen
Hello Duke,
I am currently in the process of customizing my own ROMs from other user builds thanks to the tools you provided. I am having problems though...I have used multiple nk.nbf (different os) files and dumped then rebuilded without modification just to make sure I have the technique correct. That is without modifying initflash or hv files and going right to rebuilding after dumping and I am hanging on the first screen. I then need to manually go to bootloader for reinstall.
I then checked with my modified ROMs following pdf religiously (ie deleting first 2 bytes and leaving last empty line-initflash...and adding REGEDIT4 and leaving last line saving as unicode-rgu...following instructions provided) and yet I continue to hang on the first screen.
Do you have any suggestions??
Thanks again,
vjgrace

[UPD beta3] Microwave oven: TRANSLATE YOUR ROM - (for wizard only)

Hi ppl,
I've collected all the tools I use to translate roms from our chefs (God bless them). I don't want to steal anyone's work so the most of the credit should go to the creator of the tools I've packed, so all but Muiver, 2bytecut, Go.bat that were made by me.
It should be easy for everyone to make a translation following these steps (it's easier to do than to read ...):
1) Download and install windows PROFESSIONAL image in your language (source language) from here
2) Download your preferred foreign language (destination language) ROM (i.e. TNT or OCATIVOI or whatever ... )
3) copy the images over microwave dir, go to the command prompt and run GO "your language image file" "foreign language nbf file":
4) Let it run ... When Muiver opens up, set the right languages, pick your preferred options and hit GO.
MuiVer automatically looks for the right directories in the MS dump and copies it over the image that needs to be translated, modifying some files and making things you don't have to care about. At this stage you only have to choose, based on your (future) experience, what you want to copy and what not. The options are : Mui directories (OS), Other Mui files (OEMapplications), Other non MUI files (other language related files like staticdict); The more you copy, the most will be translated, more problem you may experience (missing texts, or applications that goes blank screen).
I suggest to always copy the MUI directories and experiment with other options.
5) You're nearly done only have to edit initflashfiles.dat according to your language. This file contains the localized name of some system directories and especially the start menu and start menu items names.
When wincmp opens up you will see two child windows: the left one is the file you have to edit, The right pane c0ntains the initflashfiles localized for your language. Edit the left one, according to what you can see in the right one and then "save source" from File menu. Take big care to the name of the "startup" dir (i.e. in italian it must be changed in "Esecuzione automatica") otherwise your rom won't start the customization (no screen alignment, no initial settings .. etc etc..). I suggest not to change the name of the links in the appbutton section however.
6) When nb2nbf opens up, set everything like always (look at the picture) and hit "translate" button
Flash your new translated rom (tools included)
It's a beta, just test .. I am quite happy with it. I'll update the script to run with other devices.
DOWNLOAD links beta3:
Rapidshare Download link
Mediafire Download link
Fixed beta3:
- Added a new tool to speed up initflashfiles.dat editing
Fixed beta2:
- Before flashing move or delete manually the file nk-old.nbf or the Updater could reflash that one in place of the translated one
it is good post, even in microwave oven cooked!
I think it doesn't work with ROMs that is >= 5.2.1620 because the shellresapps.dll.xxx.mui is incompatible with older versions?
Would someone be kind enough to translate TauRho3i to English.
http://forum.xda-developers.com/showthread.php?t=332663
Anyone want to try?
-McMex
starkwong said:
I think it doesn't work with ROMs that is >= 5.2.1620 because the shellresapps.dll.xxx.mui is incompatible with older versions?
Click to expand...
Click to collapse
If it's true, then remove the directory from dump.src dir before hitting "go" on muiver ... I'll check for it and handle the case in next version.
Would someone be kind enough to translate TauRho3i to English.
http://forum.xda-developers.com/showthread.php?t=332663
Anyone want to try?
Click to expand...
Click to collapse
Come on man ... you'have the tools now, why don't you try by yourself :|
can someone up load this tool to another host ? Ex: mediafire.com plz!
I'm having probs in downloading files from rapidshare
i'll try
mcmexican said:
Would someone be kind enough to translate TauRho3i to English.
http://forum.xda-developers.com/showthread.php?t=332663
Anyone want to try?
-McMex
Click to expand...
Click to collapse
i'll try
...but i'm waiting for my touchscreen
New tests shows that a very little number of .mui files (out of .mui dirs) are compatible with our WM6 releases ... for safe translations, do not copy them at all (MuiVer->File->options->Other Mui Files -> ignore all)
Hint: Take a look to the initFlashfiles.dat in the dump.src dir before editing the new one.
medkid said:
can someone up load this tool to another host ? Ex: mediafire.com plz!
I'm having probs in downloading files from rapidshare
Click to expand...
Click to collapse
Done
@Taurho: Take a look at the ROMUpdateUtility.exe
TauRho said:
i'll try
...but i'm waiting for my touchscreen
Click to expand...
Click to collapse
If I would have known I have a bricked 8125 sitting on my desk. But thank you.
-McMex
Working on TauRho3 WWE
mcmexican said:
If I would have known I have a bricked 8125 sitting on my desk. But thank you.
-McMex
Click to expand...
Click to collapse
one colleague of mine... and my first beta-tester has lent me his WIZ (only for weekend, of course)!
so....I take back the development!!!
and TauRho4 WWE is arriving
...hummmm sunday morning! (italy time)
Great job! I am so expecting tools like this, thanks.
One quick question - Does it translate all content of the ROM, incl. OS and OEM applications? Or only OS, not for other applications in the ROM? Thanks?
it doesnt work with me i have downloaded all image file's from microsoft and when i instald it i get a pocket pc dir a tools dir a Images License txt file and a Images Readme file so i placed it all including the nbf file in the microwave dir and pressed go and a msdos screen flashes for about i mili second and then it does nothing did i do somthing wrong??
or can someone please explain me better
thanx
Danny
Can you explain a little more point number 5 and 6 plz?
I'm transalating from wwe to spanish thx.
It's my first attemp to do something with kitchens, etc...
Nice release pal.
Maybe I'm doing something wrong but is not working for me... That's what i did:
Downloaded from MS my localized image and installed it (I don't have the emulator installed, just the image).
Already downloaded my english ROM (in my case, TNT 5.0)
Did the GO stuff in this way "GO <localized-Image> <TNT5-ROM>
Then flashed the resultant ROM and it is still in English...
... What I did wrong?
Could you please post a detailed explanation (if it is possible with printscreens) about this process?
Sorry but I'm a little dumb using this one...
Regards and keep on doing this great job!
@com_reg
Does it translate all content of the ROM, incl. OS and OEM applications?
Click to expand...
Click to collapse
It basically translate the OS and some HTC applications, but due to the high number of versions around, it is safe to only transalte the OS part. I've experienced problems with some HTC applications not displaying properly after translations. So you better make some tests excluding or not some files / dir from Muiver. I'll try to release a more flexible Muiver soon
@danny de w
Open a DOS prompt and type "GO <name of the MS image>.bin nk.nbf"
@cesarr4
Did you move your old nk.nbf in a different place ? The script renames it in nk-old.nbf but this is sometimes not enough: the update utility will still pick the old one in place of the new one. The easiest solution is to move the nk-old.nbf away from the microwave dir.
@JouSePo and ALL
I am at work right now and can't take pictures, I will do a better explanation with images when I'll be at home later. By now I can try to explaint it better by words:
During the process some applications will pop-up asking you to do something:
- the first one is the MuiVer, that automatically looks for the right directories in the MS dump and copies it over the image that needs to be translated, modifying some files and making thinghs you don't have to care about. At this stage you only have to choose, based on your (future) experience, what you want to copy and what not. The more you copy, the most will be translated, but you may experience more problem (missing texts, or applications that goes blank screen).
- The second application is a notepad instance, opened on your initFlashfiles.dat. This file contains the localized name of some system directories and especially the start menu. I suggest you to take a look to the initflashfiles present in the microwave\dump.src dir that is the localized version for your language and change the one in the notepad accordingly. The only part that REALLY NEED to be changed is the name of the "startup" dir (i.e. in italian it must be changed in "Esecuzione automatica") otherwise your rom won't start the customization (no screen alignment, no initial settings .. etc etc..)
- At this point the script will have built the nk.nb file that must be translated in a nk.nbf file in order to be flashed. This is done with the last program that opens up : nb2nbf. You will find a set of row in the middle of the screen, check the first checkbox in the first line and in the box on the right pick the nk.nb file from the microwave dir. On the same line choose OS in the combobox on the right and then just click on the text box on the left. A number will appear, it is all ok. Now click on translate and you're done.
Nice printscreens smogdragon!
Thanks!
I have a question:
Which .BIN file should I use? The installed file from Microsoft extracted the following .BIN files:
PPC_ESN.BIN
PPC_ESN_GSM_QVGA_VR.BIN
PPC_ESN_GSM_SQUARE_VR.BIN
PPC_ESN_GSM_VGA_SQUARE_VR.BIN
PPC_ESN_GSM_VGA_VR.BIN
PPC_ESN_GSM_VR.BIN
All of them with same size... Which one should I use for my QTEK A9100 (Wizard)???
Thanks in advance!
In addition to my previous post, I'm getting the following error message when click on "GO" button at MUIVER program (see attachment).
What is going on? It doesn't happens when using Beta2 release.
@cesarr4
PPC_ESN_GSM_QVGA_VR.BIN is the best match with wizard's hardware.
As for the error, I've never seen that But I can see on the command prompt that you had a previous error "acces is denied". I would try to start clean, deleting dump and dump.src directories. Ah, be sure to have administration rights. Let me know
thanks for your prompt responses and your help.
I flashed the resultant rom to my Wizard and it is working fine but some issues arised with built-in apps. By example, the phone app doesn't start and built in software keyboard doesn't show up...
I was wondering if it is possible to extract the OS part from the MS image and pack it into a nk.nbf file and flash it (I mean, do not transkate a existing rom but using the OS inside the .bin file and flash it to the device)...
it is possible? what can be the side-effects doing that?
hello smogdragon
i tried using cmd and it work t for a little bit when i deed everything you said it say that it cant find this file cant find that file it cant find muiver nothing get recognized by cmd
but its all in the same dir and the image file too

Rom Cooking? (Help from the Pros!)

I have been messing around with cooking roms for a few weeks now. I have cooked up a rom (New Att Rom) that has these numbers.
Total Storage: 166.16mb (Free 164.27mb)
Total Program: 101.38mb (Free 75.28mb)
I am trying to make this Att rom as clean as possible. I have removed abosultly everything that I can. I have a few questions though as Im being kind of a perfectionist. When I load up my rom and go into the registry I can find traces of old programs that were removed from the rom (for example transcriber or sim manager registry keys) I have edited the proxml files and they are not the curlprit. I have checked the .RGU files and there is only two in the whole rom (one is boot.rgu and the other one has only one entry in it) I have also checked the initflashfiles.dat file and edited it but it doesnt have the registry keys I am looking for either. Where is the main part of the registry in these roms?
Another question I have is why the dsm files (when opened in a text editor) show other programs or files in them. I would like to delete the microphone, clear storage and key lock app or the TTY icon in the settings screen. I have found these files in the DSM files but they cant be deleted. Is there a way to edit the dsm files or are they updated when other changes are made?
Lets say I load the stock att rom on my phone and make changes to the registry (add or remove registry settings). Then if I dump the rom, will the registry changes be saved when I use the dumped rom in cooking a new rom?
Has anyone figured out a way to get the memory back when a memory card is placed into the phone? I would be around 79mb free program memory (before speed tweaks) if someone figures this out!
I will have a few more questions probably but I cant remember them right now. The rom I have made is working very well and is stable. I just want to make sure all of the trace files in the registry and other places are gone. Thanks for the help
All of the pros must be working on their own roms, look at how many have been updated! Someone must know the answer to a few of these questions. I dont mind doing the work I just need a few hints!
hollywood said:
When I load up my rom and go into the registry I can find traces of old programs that were removed from the rom
Click to expand...
Click to collapse
Default.hv and User.hv are the default and user registries where you will find the entries.
hollywood said:
Is there a way to edit the dsm files or are they updated when other changes are made?
Click to expand...
Click to collapse
There's a app that does it in the general section under hacking IIRC search for build dsm that should bring it up.
hollywood said:
Lets say I load the stock att rom on my phone and make changes to the registry (add or remove registry settings). Then if I dump the rom, will the registry changes be saved when I use the dumped rom in cooking a new rom?
Click to expand...
Click to collapse
Yes.
hollywood said:
Lets say I load the stock att rom on my phone and make changes to the registry (add or remove registry settings). Then if I dump the rom, will the registry changes be saved when I use the dumped rom in cooking a new rom?
Click to expand...
Click to collapse
I beleave the answer to this is no... the dump you get is the unmodiffied ROM you have after flash it... all changes after this are not dumped.
Cheers.
Great info thanks guys
What program do you use to edit the default.hv and user.hv? Thanks again
hollywood said:
What program do you use to edit the default.hv and user.hv? Thanks again
Click to expand...
Click to collapse
You can not edit directly, you must convert from .HV format to REG (text) format using RGUCOMP.EXE (included in KaiserKitchen) to edit, and once edited, convert back to .HV with the same tool.
Code:
dump default.hv:
1. SET _FLATRELEASEDIR=.
2. RGUCOMP -o default.hv -nologo > default.txt
3. Add 'REGEDIT4' (first line)
4. Last line MUST be empty
5. Save as UNICODE
... edit the txt file ...
build default.hv:
1. rename default.txt to boot.rgu (same folder as RGUCOMP.exe)
2. SET _FLATRELEASEDIR=.
3. RGUCOMP -b
4. rename boot.hv to default.hv
Cheers.
Great info. I have cooked up a rom and I am having a hard time figuring out what is causing the screen delay in my registry settings. Does anyone know what setting is causing like the three second delay in the screen going from landscape to portrait? Thanks
SO if I understand you correctly.
I can open the files, edit in all of my reg edits (particularry the ones I can not export) and recompress it with RGUCOMP.EXE and cook my edits into my rom ?
Ok I tried this and finally figuted I have to do it from a command line.
WHen I do
1. SET _FLATRELEASEDIR=.
2. RGUCOMP -o default.hv -nologo > default.txt
I get fronm the txt file:
dump default.hv:
1. SET _FLATRELEASEDIR=.
2. RGUCOMP -o default.hv -nologo > default.txt
3. Add 'REGEDIT4' (first line)
4. Last line MUST be empty
5. Save as UNICODE
... edit the txt file ...
build default.hv:
1. rename default.txt to boot.rgu (same folder as RGUCOMP.exe)
2. SET _FLATRELEASEDIR=.
3. RGUCOMP -b
4. rename boot.hv to default.hv
obviously I am doing something wrong, but I have no idea what.

[REF] Greek Document tab + Howto find manila file names for all language

Hi all
I am not a manila guru.. and this is my first dive in to the manila naming ocean...
I started this thread when some person that i asked for the filenames to have Greek language
in the documents tab he refuse to tell me EVEN the filenames.
So when i figure out how it works i deside to put together this Howto for other people.
This is a tutorial, a howto find the manila file names for the varius language,apps and tabs.
You will need
a) ManilaHASH.exe
b) Manilafiles.txt
Files are provided in the end of this post.
In his tutorial we will try to find the manila files and filenames to have the document tab in
Greek Language.
The same way works for any tab and any language...
So lets start.
The manila files that holds all the strings are the xml ones...
1. Open the manilafiles.txt in a text editor you will see lines like this one
5bb3a45f_manila \windows\htc\album\assets\images\btn_camera_press.qtc
The first part its the actual filename.(You will find that file in the windows folder)
The second one its a virtual path that refers to that filename.
(I dont know how and why they just are linked and the manilahash app use this to produce the
actual filenames.)
Lets find now the filenames for the document tab.
2. Search the Manilafiles.txt file for the string 'document' and when you find the first instance
scrool down to find the lines with the xml files
in our case the lines are :
35bfc9f0_manila \windows\htc\docexplorer\locales\en-us\docicons.en-us.xml
4e4ebb4e_manila \windows\htc\docexplorer\locales\en-us\documentexplorer.en-us.xml
43326f20_manila \windows\htc\docexplorer\locales\en-us\documentexplorerbrowse.en-us.xml
4db93f9f_manila \windows\htc\docexplorer\locales\en-us\documentexplorersettings.en-us.xml
1a93e5c6_manila \windows\htc\docexplorer\locales\en-us\expandeddocument.en-us.xml
The first part of those lines is the actual filename.
Those are the files that we need to find them in the \windows folder of the device and copy
them for editing. So find them and copy them from the device to your pc.
Before go to the next step, lest do a test now just to see how the manilahash.exe and the manila
naming works.
3. Open the manilahash.exe and copy and paste the "\windows\htc\docexplorer\locales\en-us\docicons.en-us.xml"
to the manila file path textbox.
Then press the "get manila" button ... you will get the 35bfc9f0_manila witch is refered in our text file.
The same goes for the others files... just check them.
4. Now lets go for the other language - the greek
In the filepath for the first file "\windows\htc\docexplorer\locales\en-us\docicons.en-us.xml" change
the language code from en-us to el-gr the greek language code, and now the path string its like this :
"\windows\htc\docexplorer\locales\el-gr\docicons.el-gr.xml".
(Here you can find all the language codes to letters for each of the 2 parts, the Primary language and Sublanguage)
http://msdn.microsoft.com/en-us/library/ms776294.aspx
5. Copy this to the manila file path textbox of manilahash.exe app and press getmanila to get the name
of the file for the greek language witch is this: 7139AFEE_manila.
So now copy the file 35bfc9f0_manila and rename it to 7139AFEE_manila.
Follow the same procedure for all the files.
The open the all files with a text editor and change the first line the string en-us to el-gr and save.
Transfer all the files to \windows folder of your device and after a softreset you will have greek (or any other lang
in the document tab.
The procedure is generaly the same for any other set of files or tabs... and for any language...
I dont now if the text file with the names covers all the manila files... i did some try and find attemps
and all the files where there.
If i can help you with your search just post the question here.
Thanks to metlwater, he was the first that answer my question about manila file names in the facebook tab
greek translation.
colossus
Greek files for Document tab
Those are the greek file name dor the document tab .
Unrar them and copy to \windows folder ....
Allways keep a copy of the originals ....
ps: the translation is not finish but i put the files here for anyone who wants to use them.
Many thanks...
thanks for sharing...actually the guy who didn't helped you did you a favor, now you are a manila guru.
Χαιρετώ
myfoka said:
thanks for sharing...actually the guy who didn't helped you did you a favor, now you are a manila guru.
Χαιρετώ
Click to expand...
Click to collapse
LOL Thanks alot (Ευχαριστώ)
I just read this today, very useful! Any idea how this works for custom tabs?
Cheers for any pointers.
Hola Colossus ;-)
I know this thread isn´t "warm" anymore, but doing some research for "FullThemSwitch" witch CHTS (or manually ) I stumbled across this one
Guess we both encountered the same "attitude" when asking "certain" people for information , guess not everybody is into sharing knowledge - since information is power At last let me also congratulate you, because you actually "practice what you preach" Love your signature
I'd all but forgotten about this thread and there was no thankyou meter last time I posted. So, your thankyou meter just went up by one.
Without you I wouldn't have been able to find out which manila files to have translated, for those wanting other localisations of my ROM series.
Cheers again!
THX great work (ευχαριστω)
colossus_r said:
Those are the greek file name dor the document tab .
Unrar them and copy to \windows folder ....
Allways keep a copy of the originals ....
ps: the translation is not finish but i put the files here for anyone who wants to use them.
Click to expand...
Click to collapse
Thanks a lot my friend. May i ask you something - My documents tab <bar> at the top of the screen is empty without writing <Documents> (from the begining). Do you know perhaps how or what file makes it appears again? I have an HD2 with the latest Greek Rom.
Interesting informations, I think you are a manila guru!!

Categories

Resources