Related
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)
Hello Friends,
I have managed the new WM6 kitchen based on Ivan's new (17913.0.3.0) build. This is a clean vanilla kitchen, you can add your own flavor and the way you want it.
I've uploaded the kitchen to the following url and hope that you will like it.
http://www.siemens-bd.net/files/000000
Files have been splited into 10 parts (5MB each) because of my unstable internet connection here. Uploading a 50MB file for me is simply a nightmare! Please download all of them and unrar.
You will find two cmd files (1. BuildKitchen.cmd and 2. CreateROM.cmd) inside the ROM_DEV folder after the unrar.
Step-1: Run the BuildKitchen.cmd (first time only), it will dump the rom and prepare the kitchen for you.
[Additionally, you may use it to dump other WM6 rom and prepare the kitchen. In that case, decode the rom, copy (or overwrite) the nk.nba file to the ROM folder and run this cmd to build the kitchen.]
Step-2: Run the CreateROM.cmd to build the rom...as usual.
You will find a Ranju_OEM folder under the ROM_DEV folder. Some of the oem packages have been added if anyone is interested to use. Just copy your desired packages to the OEM folder and build the rom.
And finally, all credit goes to Ivan. Special thanx to Helmi, Midget, Bepe and Tuatara for their tools and support.
By the way, I've a limited bandwidth to this server, it will be great if someone mirror it somewhere.
Best regards,
Ranju
ranju said:
By the way, I've a limited bandwidth to this server, it will be great if someone mirror it somewhere.
Click to expand...
Click to collapse
Mirrored:
http://vidmes.com/Uni/Kitchens/ranju/ROM_DEV.rar
(btw My mirror has a Bandwidth limit of 3Tb per month...)
TehPenguin said:
Mirrored:
http://vidmes.com/Uni/Kitchens/ranju/ROM_DEV.rar
(btw My mirror has a Bandwidth limit of 3Tb per month...)
Click to expand...
Click to collapse
Hi TehPenguin, thank you very much.
Thanks to ranju and thanks to tehpenguin!
ranju said:
I have managed the new WM6 kitchen based on Ivan's new (17913.0.3.0) build. This is a clean vanilla kitchen, you can add your own flavor and the way you want it.
Click to expand...
Click to collapse
Thx for the new kitchen. Based on V3, correct?
Could you please clarify the 1st post?
Clean Vanilla: What did you remove from the ROM?
Cheers
Download
Extract
BuildKitchen
CreateRom
BuildOS stops on error: the file 'temp\dump\Thumbs.db' already exists
I've just checked the OEM folder.
Very good Job: just like i was thinking. Probably I don't need any other apps for OEM.
THX!!!
tailazoom said:
Download
Extract
BuildKitchen
CreateRom
BuildOS stops on error: the file 'temp\dump\Thumbs.db' already exists
Click to expand...
Click to collapse
Did you modify any cmd file?
If not, then delete the temp folder. Do a search on SYS & OEM for "Thumbs.db" and delete them if found any. Run the CreateROM.cmd.
I suppose "Thumbs.db" have been created by your picture browser apps.
"Thumbs.db" is a file that Windows XP (and Vista) create if you preview a picture or movie. Its not important at all (although Windows will complain that it is a "System File")
(Nifty fact: Windows XP can create the "thumbs.db" file in a read-only network share!)
Thanks for the info, i'll try deleting and recompile.
Deleted, compiled and flashed: every essential function i tested is working. The kitchen is very clean! Many thanks ranju!
Little update of the kitchen
This is a little update of the kitchen:
* Due to the slow response of the phone, dialing/ending tone have been removed
* Update for HTC Task Manager 1.5 (Exclusive apps can be added now)
Please download the zip and copy/replace to the associated folder.
Update: HTC Task Manager cab attached.
http://forum.xda-developers.com/attachment.php?attachmentid=40327&d=1180503183
ranju said:
This is a little update of the kitchen:
* Due to the slow response of the phone, dialing/ending tone have been removed
* Update for HTC Task Manager 1.5 (Exclusive apps can be added now)
Please download the zip and copy/replace to the associated folder.
Click to expand...
Click to collapse
Can you please make a cab of it so that we can install. Dont want to go through re in stalling rom. Appreciate
Or if you can advice the registry entries for both above issues please.
Phone.cab
A cab file for the file in phone.zip is not that difficult since it's just a couple of registry entries.
The other one is more difficult since it also includes files.
So just to help a little, a cab file for the registry stuff in the phone.zip
Actually not that difficult
When comparing the old and new files, I noticed that just the RGU file is different.
Since this is the file with registry settings, I made a quick cab for it.
So not to replace the previous HTC Manager install or anything like that, just to corrent the registry entries.
ps. This and the previous file are not made/reviewed/anything by Ranju, but I've just given them him (her?) name to avoid confusion.
aniel1 said:
Can you please make a cab of it so that we can install. Dont want to go through re in stalling rom. Appreciate
Or if you can advice the registry entries for both above issues please.
Click to expand...
Click to collapse
[HKEY_CURRENT_USER\ControlPanel\Sounds\Dialing]
"Sound"="dpadctl.mid"
"Script"="p"
"Category"="InCallFeedback"
[HKEY_CURRENT_USER\ControlPanel\Sounds\Ending]
"Sound"="dpadctl.mid"
"Script"="p"
"Category"="InCallFeedback"
[HKEY_CURRENT_USER\ControlPanel\Sounds\DialPadCtlKey]
"Sound"="dpadctl.mid"
"Script"="p"
"Category"="InCallFeedback"
Remove the line in bold above ("Sound"="dpadctl.mid") in the registry and it should like this:
[HKEY_CURRENT_USER\ControlPanel\Sounds\Dialing]
"Script"="p"
"Category"="InCallFeedback"
Set the value of "Script" to "apr" and it should like this. It will remove 3s ring delay.
[HKEY_CURRENT_USER\ControlPanel\Sounds\RingTone0]
"Script"="apr"
Press the power button (off) after the changes and wait for 10 sec, switch on again and soft reset your device to take the changes in action...
GerardNL said:
When comparing the old and new files, I noticed that just the RGU file is different.
Since this is the file with registry settings, I made a quick cab for it.
So not to replace the previous HTC Manager install or anything like that, just to corrent the registry entries.
ps. This and the previous file are not made/reviewed/anything by Ranju, but I've just given them him (her?) name to avoid confusion.
Click to expand...
Click to collapse
I tried but looks like the cab does not stick the enteries in the registry.Can you give me the registry entries so that i can try to insert them manually. thank you
ranju said:
[HKEY_CURRENT_USER\ControlPanel\Sounds\Dialing]
"Sound"="dpadctl.mid"
"Script"="p"
"Category"="InCallFeedback"
[HKEY_CURRENT_USER\ControlPanel\Sounds\Ending]
"Sound"="dpadctl.mid"
"Script"="p"
"Category"="InCallFeedback"
[HKEY_CURRENT_USER\ControlPanel\Sounds\DialPadCtlKey]
"Sound"="dpadctl.mid"
"Script"="p"
"Category"="InCallFeedback"
Remove the line in bold above ("Sound"="dpadctl.mid") in the registry and it should like this:
[HKEY_CURRENT_USER\ControlPanel\Sounds\Dialing]
"Script"="p"
"Category"="InCallFeedback"
Set the value of "Script" to "apr" and it should like this. It will remove 3s ring delay.
[HKEY_CURRENT_USER\ControlPanel\Sounds\RingTone0]
"Script"="apr"
Press the power button (off) after the changes and wait for 10 sec, switch on again and soft reset your device to take the changes in action...
Click to expand...
Click to collapse
thank you ranju. CAn you provide the registry entry for tak manager too, somehow the cab posted above doesnot stick in the registry and i still dont see exclusive/activate please
Third day of use (calls with bt headset/sms/excel) without any problem. Thanks again ranju!
ranju said:
.....
Remove the line in bold above ("Sound"="dpadctl.mid") in the registry and it should like this:
....
Click to expand...
Click to collapse
Mmmm. Removing items from the registry.... Didn't think about that one. So that means that the 2 cabinet files I made will not work.
Back to the drawingboard...
Build my first Rom
I've this ROM kitchen few days back from one of my friends and was simply amazed when I build my first rom.
This is as easy!
Thanks ranju, keep up good work!
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
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!!!!!!!!!!!!!!!!!!!!!!!!!!!
Ok, I am going absolutely crazy here...I am no noob to cooking but I am having a horrible time for some reason. First let me set up the ROM for you...
I am running CE OS 707 WWE ported with Build 19965 (Raphael) and it is working fine. I have always made a provxml file to make my necessary registry changes instead of going through all the rgu's.
I have named this provxml file mxipupdate_oemoperators_108.provxml which I have attached for reference... This file is placed into the OperatorPKG folder and should, I say should run along with the other mxiupdate files...
Please look at this file and please explain why it is not happening. THe only thing I am thinking is that the ported SYS folder is causing some errors???
THanks in advance.
The file was made using rgutoXML in Unicode with wordwrap turned off
I have also tried running the file, converted to a xml file in my user customizations when it starts but still a no go...
Check youre sys if you got coldinit.lnk/coldinit.exe present.
My config_operator.txt
Code:
LOCK:Enabled
XML: \WINDOWS\mxipupdate_dialer_runback.provxml
TSK: \WINDOWS\IBI.tsk
XML: \WINDOWS\Menu_Operation.xml
CAB: \WINDOWS\PP_AKv33-DefaultPage_WWE-0409.CAB
XML: \WINDOWS\xml_reg.provxml
CAB: \WINDOWS\Raiisak`s IBI visual.cab
CFG: \Windows\config_PT.txt
config_operator.txt & xml.reg.provxml in C:\kaiserkitchen\OEM\OperatorPKG
xml.reg.provxml is where I have some of my reg stuff.
Yeah both those files are present in the SYS\Shell folder...
See whats confusing me about the whole thing is that the other ProvXML files in the OperatorPKG are working???? So I am assuming it might be something to do with the file.???
ryncppr said:
Yeah both those files are present in the SYS\Shell folder...
See whats confusing me about the whole thing is that the other ProvXML files in the OperatorPKG are working???? So I am assuming it might be something to do with the file.???
Click to expand...
Click to collapse
Wel, I poped it open to see if you had "Registry" present twice wich would make a error but it seemed good to me so its something that makes it not run. Try to set it up like I did above and give it a spin. Letme know if it worked.
Well that was a NO go so I am going to see if it has too do with the SYS files.... possible causing the error , I am not too sure...Very dumbfounded right now
Just for additional info.
To make *.provxml to be loaded on cold-boot, the said file must exist is any *.dsm.
Hope this help
And please check ur file, there were some errors in it & will be bypassed during cold-boot
Here some hints:
-check ur header
-remove semicolon or use html code
-check ur HKLM & "HKEY_LOCAL_MACHINE"
hang.tuah said:
And please check ur file, there was some error in it
Click to expand...
Click to collapse
Ah, yes. Didnt think of that.... Yet look for it ..
Ok I'm dying over here...what is the error please???? And by placing the *.provxml file into the OperatorPKG file isn't a DSM file attached to it???
I made sure any settings were not duplicated on a newer version...and by the way I tried to change the Coldinit files back to the original but no go either...I am trying a different SYS now
i think u missed my previous edited post
What do you mean by "Check my header"....
It says version="1.0" encoding="utf-8" I know.... do you mean I have to change the source file (text file) to unicode to get rid of this???
Basically if I open the file, click on View Source it opens in a notepad format...Should I save the file as *.provxml in Unicode??? because when I look at all the files that ATT puts out, once I change these files it makes them have the same header....
I also looked at raiisak xml.reg.provxml file and it too has the same header???
Ok I have attached my newest version of the Provxml...the header is gone as I changed the file type to Unicode and saved....
Also I have removed all the different HKLM files to the same and got rid of the ";" but it appears it is still not working???
I have the file named mxipupdate_oemoperators_108.provxml and it is set to run in the OperatorPKG file which has all the files the same up to 107....
ryncppr said:
I also looked at raiisak xml.reg.provxml file and it too has the same header???
Click to expand...
Click to collapse
For one time I prolly didnt use XML Notepad And I saw in EditPad
_ . _
so can someone please help me here....I am just asking what I am doing wrong...I have search the file, looked a hundreds of provxml files and still can not understand why this is not working???
ryn, for me, the header is not mandatory, it is ok, but will give error if u use some xml compiler.
here my attached edited file & u can compare with yours.
Hope this helps
hang.tuah said:
Here some hints:
-check ur header
-remove semicolon or use html code
-check ur HKLM & "HKEY_LOCAL_MACHINE"
Click to expand...
Click to collapse
Code:
translation="filesystem">
Code:
<characteristic type="HKLM\Software\OEM\RIL ; HSDPA indicator">
Code:
<characteristic type="HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts">
This is what hang tried to explain.
I already changed the HKLM and the ";" problems...the translation=filesystem I did not change.....what would it be changed too???
have u compared ur with mine mate
and please test it can work or not | sorry i cant test it
I have compared yours with mine...
I am seeing you took out the translation section which I had done before...I am going to try and load yours in a rom...just trying to find a program that I can use instead of burning the rom completely over..
i dont think having translation section is problem. i'm also using a provxml that i created for myself, it has the provxml section in it and it does work properly. what i suspect is integer" value="0.0 sec". if it is integer, shouldn't it be integer" value="0" ?