WM6 Rom Kitchen - JAMin, XDA Neo, S200 ROM Development

The use of the Rom Kitchen is at your own risk!
Note: This is NOT for beginners, you need to have a good understanding of flashing G3/G4 prophets
This is NOT for answering or asking basic info, use the wiki/search for that.
Rom Kitchen Installation:
Download and install MS .NET framework 2 first
Extract the file ‘Prophet_WM6_RK_S-Core.rar’ anywhere.
The Folder structure will look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Extract ‘FlashOS.zip’ and ‘rgu-hv.zip’ anywhere.
Using the Rom Kitchen in Steps:
STEP (0): Making an OEM Package:(optional, more later)
This step is not necessary at beginning, unless you want to include new OEM Package in the OEM dir of Kitchen.
STEP(1): Run BuildOS.exe:
it will look like this:
Here you can select / de-select any packages you require.
Make sure you don't select too many or it will overflow the rom and you will get any error in the CreateRom.bat step.
Click the green button when you are done and it will create the OS dump.
If you get errors during this, it is probably due to duplicate files/modules in SYS and OEM dirs or due to bad registry entries.
If they occur, it has to be fixed by deleting duplicate files/modules (make sure you know what you are deleting) and correcting the registry (its hard to track registry errors, only change one package at a time).
If there are no errors BuildOS.exe will finish and prompt ‘Done’.
The temp dir will have dump,boot.hv,boot.rgu and log.txt
Do not delete any content at this point.
STEP(2) (a): Editing default/User .hv files:
This can be skipped, but all depends upon need.
This is needed for example when you need to ‘remove’ some reg entries.
For example see:
The base rom used in this kitchen is from the wizard, so we probably need this type of removal again.
To do it , copy default.hv and user.hv( user may not need both) files from dump created above to rgu-hv folder.
Run respective batch file to convert them in *.rgu files and rename *.rgu files to *.txt
edit *.txt files in notepad.
Remember these points:
--------(i)Turn off Word Wrap in notepad
--------(ii)1st line is blank line, type “REGEDIT4”(without quotes)on this line
--------(iii)Make sure last line is blank line
--------(iv)Files should be saved as Unicode not ANSI after editing
--------(v)HKCR & HKLM falls in default.rgu
--------(vi)HKCU and HKU falls in user.rgu
When saving *.txt files in notepad,
--------Select Encoding as Unicode
--------Select file type ‘all’
--------Rename as *.rgu
Now run respective batch file to convert *.rgu file back to *.hv files. Original *.hv files present in rgu-hv dir will be replaced by newly edited *.hv files.
Move new *.hv files back to dump folder in temp dir.
STEP(2) (b): Editing main initflashfiles.dat, why ? (Coming soon)
STEP(3): Run CreateRom.bat:
This batch file uses the dump dir., boot.hv and boot.rgu files to create the OS.nb file.
If there are no errors, the newly created OS.nb is placed in the temp dir.
STEP(4): Flashing the OS:
- Downgrade to AKU 2.2 first (wm5)
- Move your new OS.nb from the temp dir to the FlashOS dir and run UpgradeRom.bat
Screenshots:
Downloads:
PROPHET_WM6_RK_S-CORE
View attachment FlashOS.zip
View attachment rgu-hv.zip
View attachment Guide.zip
Updates:
#1 - 10/06/2007 Reduce imgfs size and put in more OEM/Files
(1)View attachment TOOLS+CreateROM.zip
Extract Zip and replace TOOLS dir and CreateROM.bat with old one in RK.
Modified File/TOOLS are optional, one can continue to work with old ones.
Info on Update #1
- Modified File/Tools repack imgfs block and hence OS.nb to reduced size!!
- Standard size of Shiped OS/Old cutom cook OS is 58368 KB(59,768,832 Byte)
- With the modified File/Tools new OS.nb can be less then 50 MB!!
- Hence its possible to include more OEM Packs and files untill the limit of 58368 KB
- Less imgfs blocks will not increase Storage.
- If OEM Packs/Files are deleted, initflashfile.dat must be edited, if not it will not boot properly
- Flashing reduced size OS.nb with FlashOS, may not prompt completion, so one has to wait as long as to approx 30 min or above to make it complete in hidden mode.
- If you add too many OEM/Files to the OS.nb greater than standard size without any error, but avoid such OS and dont risk ur device by flashing over size OS.nb
- experience with reduced size OS.nb - device switches off frequently after waking up, no other issue found yet.
Credits:
Mamaich,bepe and faria for base framework
Anichillus for base rom Core 2.n
Double_ofour for linux support
Zeusin/Smart1 for explaning ModelID
itsme and Tadzio for his tools
funman for the manual
And many others.........

---

Hi Nandlal,
Finally after a long wait... Am downloading it now, and will try it out asap. it looks grt and easy to use from what i can see. Thanks a lot for this, and hopefully we will have more custom stable roms coming out based on this RK
PS: SMART1 helped in figuring out the model ID.....so thanks to him

---

dmc3 said:
can this be use with smart1's???
Click to expand...
Click to collapse
its complete kitchen, u dont need any other rom to use with.
Kitchen uses anichillus's Core 2.n as base rom.
If u just use kitchen with all steps u will get a rom which looks as in post.

---

P4k1t0 said:
i forget to install it... i have formated my pc 2days ago
xD
Thankx for this pack nandlal_mk
It was good if it was more options to cook our proprly rom
Click to expand...
Click to collapse
Im still on improvement work, especially option to choose Language Packs via OEM packahe and more on registry changes, but the limitation is of time. I have free access to my PC only in night for 2Hrs

---

I answered my question by myself: it's explained in the PDF-File!
But I got another question:
Can I switch the Core-ROM? I'm customizing at the moment PDAViet 4.0.0.0.3 but I think it's not all to replace the OS.nb inside the Kitchen! Explain it please!

---

animelover said:
I answered my question by myself: it's explained in the PDF-File!
But I got another question:
Can I switch the Core-ROM? I'm customizing at the moment PDAViet 4.0.0.0.3 but I think it's not all to replace the OS.nb inside the Kitchen! Explain it please!
Click to expand...
Click to collapse
Hi animelover,
Nice to see u.
I have been out for some work and will complete remaining tutorial on first page.
Well, choice for Core rom just arises cuz i liked its speed and performence even when there is not much registry changes, i changed very little few reg to work with prophet, as it was consuming time of my work hour.
And its absolutely possible to port any custem rom to kitchen, that was my search which ends in a shape of this kitchen.
But as i stated in 1st post we should have a official WM6 for prophet then only the kitchen based on that will be perfect.
There is some inbuilt behaviour of BuildOS.exe, that it does not construct registry based on custom rom that has been ported to kitchen, rather it construct registry from deployed SYS/OEM structure.
Thats why when a custom rom ( say Smart1 v3 or any) ported in kitchen vanishes its customized registries on running BuildOS.exe, and newly created rom will have totally different registries than original one.
However original registries of custom rom r placed in SYS/Metadata but they r ignored during BuildOS.exe (Mods, please correct my findings if im wrong)
If there is a better chioce for a rom that should be ported, please mention, that will be ported in RK, but u know what i wrote above.
One has to make registry changes after BuildOS.exe to make rom more performative.

---

it looks promising,
when will tut on post#5 complete ?

---

Reduce imgfs size and put more OEM/Files
Extract Zip and replace TOOLS dir and CreateROM.bat with old one in RK.
Modified File/TOOLS are optional, one can continue to work with old ones.
Benefits & Facts of Enhancement #(1)
.....(1) Modified File/Tools repack imgfs block and hence OS.nb to reduced size!!
....(2) Standard size of Shiped OS/Old cutom cook OS is 58368 KB(59,768,832 Byte)
....(3)With modified File/Tools new OS.nb can be as less to 50 MB!!
....(4)Hence its possible to include more OEM Packs and files untill the limit of 58368 KB
....(5)Decrease in imgfs block does not grow Storage on flashed device.
....(6)If OEM Packs/Files r deleted, initflashfile.dat must be edited, if not then device could not be booted properly
....(7)Flashing reduced size OS.nb with FlashOS, may not prompt completion, so one has to wait as long as to approx 30 min or above to make it complete in hidden mode.
....(8)If too many OEM/Files included than these tools make OS.nb greater than standard size without any error, but avoid such OS and dont risk ur device by flashing over size OS.nb
....(9)My 2 days experience with reduce size OS.nb--- device switches off frequently after waking up, no other issue found yet.

---

Brakelseboer said:
This ROM is great. Beautifull bootscreen and finally sound for every tap, even the Start Menu.
One Problem:
When I change the backlight setting (everything off) and I switch off and on my device the backlight is gone. The only solution is to hard reset my device and set it up again. Is there a solution for?
Click to expand...
Click to collapse
there is no such problem on my device, but its possible different devices shows little variation in performence.
try using without backlight off setting or power offsetting for some time, i think it may help or remake-reflash in freash way.
im still on enhancement work, but with slow pace. However there is not much to change as base rom provided by anichillus is already superb.
But still i will post some more enhancement before reviving whole kitchen with any new good base rom.

---

Thread move to WM6 section, will update and clean later
Good work nandlal_mk

---

thanx for sticky
Jesterz said:
Thread move to WM6 section, will update and clean later
Good work nandlal_mk
Click to expand...
Click to collapse
Thanx Jesterz.
Its nice to see you again after a long time ( last activity 20-3-07 , i was eying/waiting to change it), really missing u all prophet forum user.
I need ur assistence, may i PM u later?

---

nandlal_mk said:
Thanx Jesterz.
Its nice to see you again after a long time ( last activity 20-3-07 , i was eying/waiting to change it), really missing u all prophet forum user.
I need ur assistence, may i PM u later?
Click to expand...
Click to collapse
Thanks ! and sure, give me a PM whenever
C ya

---

2 questions...
1. can i use this tool to cook ipaq rom?
2. if the pda has no phone function, how can i remove the phone module?
sorry i am newbie, pls bear with me if i asked silly questions

---

Anyone have the problem on the status battary?

---

nandlal_mk said:
Im still on improvement work, especially option to choose Language Packs via OEM packahe and more on registry changes, but the limitation is of time. I have free access to my PC only in night for 2Hrs
Click to expand...
Click to collapse
Please let me know if you need help for multiple lingual packs as I know japanese, korean and chinese. I still have the problem of doing a korean/japanese language rom. Tks!

---

Is there a way to convert OEM Packages into cabfiles that I can install like any other program?

---

OEM to cab
Infestor said:
Is there a way to convert OEM Packages into cabfiles that I can install like any other program?
Click to expand...
Click to collapse
I use this program for making cab files
Installation Creator
It's got everything you need
Just place the files in the right folder and edit the registry and go to build and your done

---

new core rom
I realy like to get a new core rom the one inside this kitchen is buging me.. as is restarts the prophet rapidly

---

Thanks gullum!
I only have some remaining questions:
First, is it correct, that the registry entries from the OEM-package are in the *strange-hex-code*.rgu? Do I need to enter this code anywhere? Is there a way to import this file directly into the Installation Creator or do I have to add the settings manually by editing the registry sections?
Second, how can I find out if there are any self registering or setup dll files that I have to specify during the setup process?
Sorry to bother you, if there is a thread or tutorial where this has been discussed before, just tell me which one it is.
I just downloaded the OEM.zip from the Wizard Forum and want to try some of the programs out.
Thanks again for your help!
PS: And yes, I have the same problems with the core here...my Prophet restarts every 10 inutes or so .

---

Help me
gullum; said:
I use this program for making cab files
Installation Creator
It's got everything you need
Just place the files in the right folder and edit the registry and go to build and your done[/QUOTE
Bro, thanks for the link but i dont really understand how to create cab file using this intallation creator tool but eager to try. I'm quite blur. Can you help me on this?
Click to expand...
Click to collapse