Database Users

[Oct 05] Polaris Kitchen v1.4 Multilang - WM6.1 (Build 19965.1.2.3)

How to:
1. Extract Polaris_Kitchen and put it in C:\ , so we will be C:\Polaris_Kitchen
2. In Polaris_Kitchen\TOOLS\Polaris.htcrtproj set:
VersionId
LanguageId
3. Put your packages inside OEM
4. Execute BuildOS and select/deselect packages that want to include in your ROM then start it and at the end of his work close it.
5. Execute Build ROM.bat
6. Please Wait
7. That's all, inside FLASH directory will be a RUU_signed.nbh ready to flash!
General information:
OEM: HTC Polaris 3.13.405.0
SYS: HTC Polaris WWE 3.13.405.0 - (Build 19965.1.2.3)
Useful Links
Polaris Hard SPL v2
Polaris CustomRUU
Custom Splash Screen
Thanks to:
bepe for his BuildOS
Dark Simpson for his HTC ROM Tool
misar for G'Reloc
Olipro for his Hard-SPL
tadzio for ImgFS Tools
Changelog:
Code:
What's new in v1.4?
[+] Updated the kitchen to Official HTC ROM
[+] Updated OS CE 5.2.19965 (Build 19965.1.2.3)
What's new in v1.3?
[+] Updated OS CE 5.2.19214 (Build 19214.1.0.4)
What's new in v1.2?
[+] Updated OS CE 5.2.19209 (Build 19209.1.0.2)
[+] Updated OEM part - Polaris CHT 1.52.753.3
[!] Fixed Ringtone Settings problem
[!] Fixed USB to PC, now it's in Connections
[!] XIP rebuild
What's new in v1.1?
[+] New SYS part from AT&T Kaiser ROM (Build 19209.1.0.2)
[+] Updated to .NET 3.5 Compact Framework
[+] Voice Command 1.6.19209
[!] Fixed small issue in the Kitchen
Download:
Polaris Kitchen v1.4
Password: Polaris_Kitchen_v1.4
Download Improved "Build Rom.bat":
Build ROM.zip (thanks to worstenbrood)
Note: I improved "Build Rom.bat" a bit so you can use the kitchen from ANY directory, not only C:\Polaris_Kitchen, adjust the 2 environment variables at the beginning (set version_id=... and set language_id=...) to your needs and execute buildos.exe, then "Build Rom.bat".
Download base ROM in other languages:
FRA
GER
NLD
ITA
NOR
PTG
SPA
RUS

How to extract and reconstruct OEM and SYS parts:
P.S.: OEM part must be an Polaris OEM, not from other devices!
1. To extract .nbh files you need NBHextract.
Put your .nbh file and nbhextract.exe into a directory
From prompt commands: nbhextract file_name.nbh
Delete all extracted files except xx_OS.nb
Rename xx_OS.nb in OS.nb
2. To extract OS.nb files you need ImgFS Tools (v2.1rc2)
Extract all files inside the zip into the same OS.nb directory and from prompt commands:
nbsplit -kaiser OS.nb
imgfsfromnb OS.nb.payload imgfs.bin
imgfstodump imgfs.bin
We have dumped the ROM and than we need reconstruct OEM and SYS parts, to make this need PKG Tool.
This step it's very simple, open the dump directory with PKG Tool than Tools -> Build Packages
Ok now we have OEM and SYS parts.
!! Remember, use only OEM part from Polaris ROM don't use from other device or your ROM don't boot. !!
How to create a package from a .cab
There is a very very powerful tool to do this, Ervius Package Creator (EPC).
1. Download latest version of EPC from his thread.
2. Select your ROM Language.
3. Select Package's group.
4. Click on Open Cab File than select your cab.
5. Copy the directory created inside your OEM directory.
5. Done!
Thanks to my friend Ervius for this awesome tool

hi friend, I'm happy to see that works go on, and with a fantistik kitchen....
I think so, people will be able to eat somethings good!!!!!

Thanks for all work i'll try it for the next flash

Hi UDK, I always attend to taste your rom on my polaris

Yes thanks man a good explanation to cook a rom i was waiting for this

Hi Udk i'ts to make wwe version?

Do you also have an tutorial for how to make WM 6.1 Translate to Dutch or any other language ?

HTC Touch Dual Dialer for Touch Cruise
Hello,
the touch cruise dialer satisfy me not. I saw the dialer in Youch dual and it's much better.
Can I replace mine for touch dual dialer? What should I do to replace?
PS: I thought there is a .cab with dialer, I should just luanch it and it will remove the previous one himself, but I cannot find such a .cab. Help.
Another question, if I finally replace my dialer with another one - will the view of "Calls list" be replaced with the new one? I wish it will.

infido said:
Hi Udk i'ts to make wwe version?
Click to expand...
Click to collapse
Yes it's WWE.
lexi1986 said:
Do you also have an tutorial for how to make WM 6.1 Translate to Dutch or any other language ?
Click to expand...
Click to collapse
Need only to change OEM (Polaris OEM) and SYS (Kaiser SYS) from a Dutch ROM.

Can you explain me What i must do to get the KAISER NLD SYS en what the POLARIS OEM is ?? I have download the WM 6.1 Dutch but it's an .NBH file for the Kaiser. I hope you can help.

lexi1986 said:
Can you explain me What i must do to get the KAISER NLD SYS en what the POLARIS OEM is ?? I have download the WM 6.1 Dutch but it's an .NBH file for the Kaiser. I hope you can help.
Click to expand...
Click to collapse
First all you need an Official Polaris Dutch ROM (find it here) to extract OEM part only.
To extract .nbh files you need NBHextract.
To extract OS.nb files you need ImgFS Tools
nbsplit -kaiser OS.nb
imgfsfromnb OS.nb.payload imgfs.bin
imgfstodump imgfs.bin
To reconstruct OEM and SYS parts you need PKG Tool
Remember, OEM from Polaris and SYS from Kaiser, don't mix them!
Then put your OEM and SYS in C:\Polaris_Kitchen (delete existing).
Open ROM\XIP\boot.rgu and change:
[HKEY_LOCAL_MACHINE\MUI]
"SysLang"=dword:409
[HKEY_CURRENT_USER\MUI]
"CurLang"=dword:409
to
[HKEY_LOCAL_MACHINE\MUI]
"SysLang"=dword:413
[HKEY_CURRENT_USER\MUI]
"CurLang"=dword:413
save and exit.
That's all.

Thanks i will try youre great.
DONE: now i have to wait for the Polaris Kitchen youre great i hope this work. The Download link is availible tonight ?
Edit: Nevermind there are online great work

Cant download Part1 or 2 "This file is currently set to private. This error has been forwarded to MediaFire's development team" came up

lexi1986 said:
Thanks i will try youre great.
Click to expand...
Click to collapse
Try, it's not difficult

omaga said:
Cant download Part1 or 2 "This file is currently set to private. This error has been forwarded to MediaFire's development team" came up
Click to expand...
Click to collapse
part1 and part2 are now online!
Have fun

Thank you UdK!

very fantastic UDK
moderator... Sticky thread???

I get an Error: The File temp\packages\75bcd9fa-30b9-8705-5d86-11acd2e2c1b1.dsm already exists
after that the BuildOS stops.
Edit: After closing BuildOS the file Buildrom.bat is busy with things maybe it's going to be ok.
I have got a .nbh file now i going to flash and look if it is working.
Edit: Flashing has worked but my phone is hanging on boot any idea ???

If BuildOS returns error close it and then close prompt commands, don't flash the .nbh.
I will fix this, If buildos returns error automatically stops all others tools.

EasyPortOven V2.2 [Updated May 11 2008]

This is a release for my ROM porting kitchen. It ports both XIP's and SYS folders. It currently supports the following:
Herald
Wizard
Prophet
Kaiser
Elf/Elfin
Hermes
Zinc
Athena
http://www.darthnet40.com/xda/ivanmmj/Kitchens/
(You will need 7-Zip to open the file.)
This is compatible with Bepe's extended kitchen, but I don't believe he ever released one for every device out there. It requires a ROM folder with an extracted XIP folder within it. Just download the Herald's and you'll see what I mean. The ONLY tested section has been the Herald section as that's the only device that I have.
If your device is compatible with Bepe's kitchen or my kitchen, it will automatically launch the kitchen right after.
Instructions:
Delete your old SYS folder
Place the SYS file you wish to port into Working_Folder
Place your xip.bin that you wish to port into the Prepare folder
*Note: Close the XIPPort program after pressing "Make Packages." The script will take over after that.
You should not have a Working_Folder with an OEM, SYS and XIP folder (and a Tools folder if you have Bepe's kitchen, even more if you have my kitchen.)
Double click on the RunMe file and choose your device.
For those who have a kitchen:
Place bepe's kitchen in the Working_Folder (so that OEM/SYS/ROM and other folders are right within Working_Folder.) Alternatively, you can place also place all the files into EasyBakeOven's folder. Allow the Working_Folder to override EasyBakeOven's Working_Folder. You will not loose any data but will bypass a few "info" scripts. This will not cause any problems.
Obligatory Warning Label:
Use this at your own RISK. I cannot be held liable for any damage caused to your device by your own mistakes or by my mistakes in the instructions.
If you wish to know how to do this manually, head over to my HowTo thread.
Thank you's go to:
Bepe for his Extended kitchen and Herald/Atlas files
ababrekar for the elfin files
l3v5y and xvx45 for the Prophet files
character and ginminded for the Wizard files
Script for the Kaiser files
tjkhattak61 for the Atom Exec files
cruzzmz for the Zinc files
caxio for the Hermes files
irus for the Athena files
Changelog
V2.2
Added Athena Compatibility
V2.1
Added Prophet Compatibility
Added Elfin/Elf Compatibility
Added Hermes Compatibility
Added Kaiser Compatibility
Added Zinc Compatibility
Added Atom Compatibility
V2
Added Wizard Compatibility
Rewrote script to add expandability
V1.5
XIP porting complete
V1
SYS porting complete

Woo! I've failed to find a link for this up till now, but now I can cook some new ROMS!!
One thing, the read me doesn't include some of the more reason compatibility improvements...
Welcome to EasyBakeOven!
Devices supported:
Herald/Atlas
Wizard
Note: Make sure that the XIP in your recieving folder has been extracted already (You should have a ROM folder with a XIP folder inside it.) This is not an issue if you're using Bepe's Extended 6.1 kitchen or my own JustClean EasyBakeOven.
Thank you's go to:
Bepe for his Extended kitchen and Herald/Atlas files
ababrekar for the elfin files
l3v5y and xvx45 for the Prophet files
character and ginminded for the Wizard files
Script for the Kaiser files
tjkhattak61 for the Atom Exec files
cruzzmz for the Zinc files
caxio for the Hermes files
irus for the Athena files
Click to expand...
Click to collapse

l3v5y said:
Woo! I've failed to find a link for this up till now, but now I can cook some new ROMS!!
One thing, the read me doesn't include some of the more reason compatibility improvements...
Click to expand...
Click to collapse
Noted. Thank you!

Has anyone found this even remotely useful? If not, I will not pursue adding more devices.

Has anyone found this even remotely useful? If not, I will not pursue adding more devices.
Click to expand...
Click to collapse
I have! I've ported a Kaiser XIP and a Touch one to the Prophet! Problem is I couldn't find the latest builds so they where slightly out of date...

l3v5y said:
I have! I've ported a Kaiser XIP and a Touch one to the Prophet! Problem is I couldn't find the latest builds so they where slightly out of date...
Click to expand...
Click to collapse
Just for being nice to me, here you go!
That's the newest official build. Be careful of anything "newer," they're fakes.
It's the one labeled 19213.7z
You'll need 7Zip to open the file. In it as the xip.bin and the SYS folders.

Yay!!!
Porting time!

I have one feature request!
Would it be possible to build a feature in that cleans out the folders before porting?

I think I'll test later cause actually I'm in exam but I think it work, I'm on the same device as l3v5y so I'll make my test and maybe take to you Artemis files (my other phone)
Thank for your hard work

Great tool ivanmmj.... I have a few questions. I guess I don't fully understand the process.
I've been able to get the XIP folder, os.nb.payload and romhdr.bin files from a KAISER rom... plus I used the .VM and WinCENLS_WWE folders from a working HERMES rom, but I can't seem to get past the second boot screen. A question I had is... do we use the os.nb.payload and romhdr.bin we got from the KAISER? or do we use those from a working hermes rom? and the XIP directory, do we need to change anything in there? or is just extracting it out, enough to work?
Thanks in advance.

Awesome tool, looks like a dummy can me even port ROM's will try it out sometime. Thanks bunches!

l3v5y said:
I have one feature request!
Would it be possible to build a feature in that cleans out the folders before porting?
Click to expand...
Click to collapse
Already ahead of you. Today I noticed that I tend to leave a mess behind. lol I'll have it remove the files before replacing them, then I'll have it delete the extra files created during the process when it's done. (This part is already ready but I just haven't uploaded it. The removing the files before replacing them, I haven't done so, yet. Although this might not really be needed. Only the cleaning after part.)
...Maybe I don't know what you're talking about. lol
Explain it to me.

AssassinsLament said:
Great tool ivanmmj.... I have a few questions. I guess I don't fully understand the process.
I've been able to get the XIP folder, os.nb.payload and romhdr.bin files from a KAISER rom... plus I used the .VM and WinCENLS_WWE folders from a working HERMES rom, but I can't seem to get past the second boot screen. A question I had is... do we use the os.nb.payload and romhdr.bin we got from the KAISER? or do we use those from a working hermes rom? and the XIP directory, do we need to change anything in there? or is just extracting it out, enough to work?
Thanks in advance.
Click to expand...
Click to collapse
You need the XIP folder, os.nb.payload and romhdr.bin of YOUR device and the xip.bin and SYS folder of the rom you want to port INTO your device. Which device do you have? Tell me and I'll "draw" a map of what goes where.

xvx45 said:
I think I'll test later cause actually I'm in exam but I think it work, I'm on the same device as l3v5y so I'll make my test and maybe take to you Artemis files (my other phone)
Thank for your hard work
Click to expand...
Click to collapse
That would be more than welcomed especially since I'm gonna use my Herald cooking class and modify it to teach Artemis users, also.
ai6908 said:
Awesome tool, looks like a dummy can me even port ROM's will try it out sometime. Thanks bunches!
Click to expand...
Click to collapse
My hope is that it will allow just about anyone to port a ROM. ^_^

ivanmmj said:
You need the XIP folder, os.nb.payload and romhdr.bin of YOUR device and the xip.bin and SYS folder of the rom you want to port INTO your device. Which device do you have? Tell me and I'll "draw" a map of what goes where.
Click to expand...
Click to collapse
Thanks for replying ivanmmj... I have a hermes, and I've been doing exactly that... my problem is when I go to build it, I get "An unhandled win32 exception occurred in buildxip.exe [2276]"
If I put in my older XIP build, buildxip works fine... so I'm lost now. Oh, and I'm trying to port the 19213 official att kaiser rom XIP.

AssassinsLament said:
Thanks for replying ivanmmj... I have a hermes, and I've been doing exactly that... my problem is when I go to build it, I get "An unhandled win32 exception occurred in buildxip.exe [2276]"
If I put in my older XIP build, buildxip works fine... so I'm lost now. Oh, and I'm trying to port the 19213 official att kaiser rom XIP.
Click to expand...
Click to collapse
You'll need:
OEM: hermes
ROM folder: Hermes (uncluding the XIP folder and all the other files)
SYS folder from kaiser (look for and remove MSkernel from this folder... I'm not 100% on that folder yet and future versions may handle that folder automatically)
Place the xip.bin from the kaiser into the prepare folder.
Now run the RunMe

ivanmmj said:
You'll need:
OEM: hermes
ROM folder: Hermes (uncluding the XIP folder and all the other files)
SYS folder from kaiser (look for and remove MSkernel from this folder... I'm not 100% on that folder yet and future versions may handle that folder automatically)
Place the xip.bin from the kaiser into the prepare folder.
Now run the RunMe
Click to expand...
Click to collapse
I really appreciate your help ivanmmj, same thing again. It chokes up on BuildXIP.exe ...I have BuildXIP version 0.53 if that makes any difference. I tried with two XIP versions... 19209 and 19900. I'm about to give up.
Oh and I have Visual Studio 2008 installed, so I don't think it would be the runtimes... would it?

AssassinsLament said:
I really appreciate your help ivanmmj, same thing again. It chokes up on BuildXIP.exe ...I have BuildXIP version 0.53 if that makes any difference. I tried with two XIP versions... 19209 and 19900. I'm about to give up.
Oh and I have Visual Studio 2008 installed, so I don't think it would be the runtimes... would it?
Click to expand...
Click to collapse
It might be.... I'll have to do some research...

Ok, I even installed the vs2008 runtimes, same thing.. I found buildxip v.54, same thing... then i moved the whole ROM folder (new XIP) out and put in the old 19209 one and it ran... so maybe there's something wrong with 19213 with hermes? ok, I give up. Thanks for your help!!

19213 porting to elfin
i'm trying to port the 19213 to my elfin, and after porting when i use bepe's kitchen, it gets stuck at this screenshot. anybody help!!!

XIP 20721 for Polaris.

XIP 20721 for Polaris.

SHAYDER said:
XIP 20721 for Polaris.
Click to expand...
Click to collapse
Call me stupid.... what's XIP?

XIP is kernel of OS.
You can see a version of XIP: Start->Settings->System->About
OS CE 5.2.20721 is current XIP.
To build ROM with new XIP you must: put "MSXIPKernel" folder to "SYS" folder. Then build you new ROM with new XIP.
For Example you can use Polaris Kitchen v1.3 - WM6.1 (Build 19214.1.0.4)
http://forum.xda-developers.com/showthread.php?t=379559
for build ROM.

thanks....
20721 seems have Microsoft touch function
and 20721 XIP seems good , too.
now trying ^^

Brilliant cooked in and working fine
I am a total n00b so took a risk flashing but it went in and reports as 5.2.20721

Shayder,
no more need for your imgfs.bin and os.nb.payload like in the
XIP 20296 you posted?
Olioaglio

German ROM to dump available?
Anyone has a recent (202..) GERMAN Polaris ROM which
is able to recook (with dsm, rgu correct header etc)?
Unfortunately all ROMs I tried (Glass 0.4, UDK R7 GER, bepe) which
are available cannot be dumped and/or repackaged
It's a real pity! Seems the only way is using WWE for getting
the advantages of the new builds....
ANY HELP IS APPRECIATED!!!
Olioaglio

My imgfs.bin and os.nb.payload needed to replace any XIP on any ROM.(It is templates)
My Kichen.
http://rapidshare.com/files/140893825/Kichen.zip.html
To build ROM:
1) Put "OEM" and "SYS" folders to "Build" folder. (dont delete any existing files)
2) Run Rom.bat Then put "1" then "8" then "0"
3) When running "BuildOS" Put 'Play' button.
To Extract ROM:
1) Put "RUU_Signed.nbh" to "Extract" Folder
2) Run Rom.bat Then put "2"
3) When running "Package Tool", File->Open and put way "...\Extract\dump"

Olioaglio said:
Anyone has a recent (202..) GERMAN Polaris ROM which
is able to recook (with dsm, rgu correct header etc)?
Unfortunately all ROMs I tried (Glass 0.4, UDK R7 GER, bepe) which
are available cannot be dumped and/or repackaged
It's a real pity! Seems the only way is using WWE for getting
the advantages of the new builds....
ANY HELP IS APPRECIATED!!!
Olioaglio
Click to expand...
Click to collapse
I cant help you. ((Glass 0.4, UDK R7 GER, bepe) they Specially so have made) You must find needed files in internet.

Good work my friend. Indeed a good help.
kindly post the os.nb.payload as you have posted in the other XIP.
....regards
...c_shekhar

"imgfs.bin" and "os.nb.payload"

First off let me say thankyou for putting this package together.
I have cooked a rom and it boots up fine so I have started to customize it. Run into a few problems that I am hoping someone will be able to fix.
Here goes
I have used the package creator to insert some cabs into the installation. 3 of my cabs went in fine the rest create errors when building the registry.
So I am looking for a way to auto run the cabs. When the OS loads it seems to run a UC application from 2 places.
config_operator.txt
config_PT.txt
These point to cabs in the \windows directory and are installed upon first running of the rom. Brilliant I though. I copied the cabs i wanted into the OEMAPPS folder. Now when the rom is flashed my cabs are 100% copied OK into the windows folder as I can see them and run them.
So I edited the config_operator.txt
CAB: \WINDOWS\googlemaps.cab
CAB: \WINDOWS\coreplayer.cab
CAB: \WINDOWS\3iepatch.cab
CAB: \WINDOWS\opera1938.cab
CAB: \WINDOWS\advancedconfig.cab
CAB: \WINDOWS\keyboard.CAB
EXEC:\WINDOWS\cusTSK.exe \WINDOWS\Htc.tsk
XML: \WINDOWS\Menu_Operation.xml
CAB: \WINDOWS\PP_AKv33-Defau
Now when I re-flashed and the OS boots and I can see it in the install run my cabs and it looks like they are installing. The last one restorepie.cab then resets the device.
Upone reset my cabs have not been installed even though it looked like they were. Why is this?
Also is there a switch I can put to delete the cab after install? something like
CAB: \WINDOWS\opera1938.cab -d
Thanks in advance.

I dont know. I cant help you with this. But i can help you with errors when building the registry.
in "*.rgu"
Usually errors such:
@=""Windows\\cecmd.exe" "%1""
You must correct to
@="Windows\\cecmd.exe %1"
errors in ""
Good luck

SHAYDER said:
I dont know. I cant help you with this. But i can help you with errors when building the registry.
in "*.rgu"
Usually errors such:
@=""Windows\\cecmd.exe" "%1""
You must correct to
@="Windows\\cecmd.exe %1"
errors in ""
Good luck
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU THANK YOU!!!!
I went through the rgu for my opera package and did as you said. Now build perfectly no errors.
Time to get some more cooking done!!

Shayder,
Trying to use your kitchen but got stuck on how to change the automatically splash screen already setup in the BAT file? I was looking for NB file so I could just change the path but didn't understand those files named polarishtcrtproj.....
Thanks a lot and also for sharing this stuff!
SHAYDER said:
My imgfs.bin and os.nb.payload needed to replace any XIP on any ROM.(It is templates)
My Kichen.
http://rapidshare.com/files/140893825/Kichen.zip.html
To build ROM:
1) Put "OEM" and "SYS" folders to "Build" folder. (dont delete any existing files)
2) Run Rom.bat Then put "1" then "8" then "0"
3) When running "BuildOS" Put 'Play' button.
To Extract ROM:
1) Put "RUU_Signed.nbh" to "Extract" Folder
2) Run Rom.bat Then put "2"
3) When running "Package Tool", File->Open and put way "...\Extract\dump"
Click to expand...
Click to collapse

To change main splash screen you must:
1) run ROM.bat
2) put 3
3) in ".nb Image Tool" put "load..."
4) "save .nb" (save as "mainsplash.nb")
5) replace "mainsplash.nb" in "Build" folder to you "mainsplash.nb".
6) in ROM.bat put 1 then 8 then 0
Good luck

Thanks Man!
Cooked already but is showing CE OS 20721 and Build 20275
Things happens
SHAYDER said:
To change main splash screen you must:
1) run ROM.bat
2) put 3
3) in ".nb Image Tool" put "load..."
4) "save .nb" (save as "mainsplash.nb")
5) replace "mainsplash.nb" in "Build" folder to you "mainsplash.nb".
6) in ROM.bat put 1 then 8 then 0
Good luck
Click to expand...
Click to collapse

version of build Depends from "SYS" (not XIP)
XIP is CE OS 5.2.20721

Yep...agreed
I have used Niki's SYS but got stuck on splash screen all the time
SHAYDER said:
version of build Depends from "SYS" (not XIP)
XIP is CE OS 5.2.20721
Click to expand...
Click to collapse

I can help? Just whot do you do?

[Kitchen][May 5 23563 WWE]Kitchen Tool for Ipaq 61x/91x

I finally found a way to overcome space issue that cause BuildIMGFS throw error when you put too many files in the ROM using captaintrip's kitchen
The repack used imgfsfromdump instead of buildimgfs which avoid the size issue and in additon can reduce the final size of flash.dio
The usage are the same with captaintrip's kitchen, I only rename the bat to "iPAQ61x_91x flex kitchen" since this works for both 61x and 91x
You will need to rename flash.dio to TEMPLATE.ROM and put it under ROM folder, when you run iPAQ61x_91x flex kitchen.bat it will also prompt you,follow instruction
keep in mind if you use flex kitchen to build your rom won't be able to extract it properly, anyone want to edit your room will need your kitchen instead. If you don't have buildimgfs issue you may want to stick with the old way of building rom
use iPAQ614c Rom Kitchen.bat if you want to build your rom in old way
Updated July 7th: attached new cecompr_nt.dll that fixed memory leak, necessary for LZX compression, replace the one under TOOLS folder
Download (v0.3):
mediafire
Updated: Dec 9th ,09
v4 Beta:
-improve ability to decompose ROM, however the packages in SYS and OEM portion is usually mix up so you have to manually move them to correct folder after extraction
Download:
21501 kitchen
21215 kitchen
Rom folder for w version for 21215 (Rename it to ROM if you want to build w version)
21232 kitchen
21234 kitchen
21725 kitchen - removed due to too many issue, use 21728 kitchen instead
21728 WWE Kitchen
21728 ITA Kitchen
21728 GER Kitchen
21728 FRA Kitchen
21812 WWE Kitchen
21815 WWE Kitchen
23001 WWE Kitchen
23001 CHT Kitchen
23004 WWE Kitchen
21921 WWE Kitchen
23009 Hybrid WWE Kitchen
23016 18.1 WWE Kitchen
21854 WWE Kitchen
23047 WWE Kitchen
23052 WWE Kitchen
21867 WWE Manila 24M2 Kitchen
21869 WWE Kitchen
21869 WWE Manila 25M Kitchen
23088 WWE Kitchen
28002 WWE Kitchen
28011 WWE Kitchen Beta 29
28011 WWE Beta 29_2 Kitchen - kitchen of Beta 29.2
note: you can replace WinCENLS_Lang_0404 with WinNLS_WWE (from other rom kitchen) to save ROM space
-arcsoft streaming player & codec can be removed if you don't need them
23515 xip (use with 23518 SYS)
23518 CHT Kitchen (LZX)
23518 WWE kitchen
21888 WWE Kitchen
23529 WWE Kitchen
28230 WWE Kitchen
23544 WWE Kitchen
23563 WWE Kitchen
91x 28011 WWE Kitchen -not tested since i don't own 91x device so use as your own risk, use dnw in the worst case
91x 23518(23515)/21888 untested xip
Official WM 6.5 Tookit/SDK/Emulator: here

FCC Information for 610c
FCC information for 910c
----------------------------------
Structure Overview
XIP is the kernel, this is also what you see those 2xxxx build mean, the whole term is called "Execute in Place", i.e execute files in rom directly without copying to ram, this is for boot process, anything wrong mean you will stuck in clean boot
OEM is for device/manufacturer specific program/drivers
SYS is for Windows Mobile system files
A package is a folder with at least a dsm file,all other files are extra
-rgu file is just reg file which you can use notepad to edit
-default all files goto Windows directory (obviously exclude rgu file)
-initflashfiles.dat/txt is a text file with instruction to move files to different directory
Files vs Modules
Modules are folder with ".dll" in their names. Inside the folder there is imageinfo.bin, S00X where x is a digit. When they are cooked into ROM they will become dll with proper relocation (done by WMReloc/G'Reloc). Supposedly being modules would make them load faster(because no need to relocate at runtime?) and some dlls must be in modules or else some program will not work properly. However there are also cases that modules must be converted to files.
Technically you can put everything in SYS since at the end buildOS will merge everything together but it is easier to manage if you follow the OEM/SYS structure
Common Issues TroubleShooting
hang on 1st boot screen (HP Logo)
-XIP porting issue, .rom , .vm file not correct .etc
hang on 2nd boot screen (WM splash screen)
-module did not relocate properly (did you run WMReloc or GReloc?)
-XIP (lower possibility, i don't think it affect..just in case you should keep in mind)
hang/crash on today screen
-software conflict/missing .etc , check your SYS/OEM files
Endless HP update/customization engine
-happens because of different model uses different customization engine, using one from other model/region will cause it to rerun every boot time, the only solution seem to prevent it to run from start by removing it from initflashfiles.dat. Convert all the fix into packages and integrate to the rom instead
installed SIP(virtual keyboard) cannot be switched
-use recmod (under tools folder) to convert all modules into files in browsingie folder
cannot compose new sms/email .etc
-replace redist_lang_[lang_code] folder with one that worked before
wifi cannot turn off after boot
-set HKLM/Comm/SDIO86861/Wireless to 1
XIP
To insert ported xip, run this command: osnbtool -c TEMPLATE.ROM 1 xip_out.bin
where xip_out.bin is your new XIP file
xip porting tutorial can be found all over the place in xda/ppcgeek .etc
Also make sure in ROM folder, the boot.rgu is from your device xip (the kitchen I provided only contains 61x xip so to cook for 91x you need to put 91x boot.rgu instead)
Phone Radio
rilgsm.dll is needed but usually it is in OEM folder
PagePool
Overview: xda wiki
edit using pagepool_by_wlodixon under flash folder, copy your flash.dio and run the appropriate cmd
The only exception is if the rom set pagepool to 0 (Dynamic PagePool), it won't able to recognize and you have to hex edit
hex edit the xip.bin at 0x000A75E4, change all 4 bytes to your desired value (all 0 for dynamic pagepool)
Convert cab to OEM
get package creator here
use it to open cab, then wince cab analyzer opened, choose extract folder icon, after close wince cab analyzer, you will be present with shortcut screen, do you things and hit done, finally hit complete package unless you want to change some option
Create simple cab for file/reg changes
get QuickCab
Xt9
corresponding lang files in OEMApp/OEMLang_#### where #### is the 4 digits lang ID
-[2letter langs code]hpd.ldb
-[2letter langs code]lbUN_xt9s/lsUn/.etc].kdb
-et9.SQR.[Language].bmp [Optional, some language like Polish/Portuguese just point to english bmp in registry]
-[a bunch of number/digit known as GUID].rgu (if you open it up you will find there is registry on xt9)
also under OEM\OEM_Lang_[Lang number]
-initflashfiles.dat (actually you can use notepad to open it and seacrh for ldb/kbd/bmp to see which lang files )
cooking different language
-you will need your language OEM folders from original HP rom
-your language wince.nls
-replace all language mui (e.g 0409=English) with your language mui
-some languages may added extra folders, be sure to copy them into SYS too
-sometime the hp customization/update will end up endless run in every start, in this case you will need to prevent it from running and integrate all updates into the ROM
OptionXML Addon
I have written this small .Net 3.5 App to generate option.xml for SYS packages which will allow you to select the common package and different language more easily without moving folders all the time, just unzip the zip to kitchen which will overwrite the existing batch file and put the exe under TOOLS folder.
To select/UnSelect a category in BuildOS, you can click on the Category group (e.g click on 0409 will select all 0409 packages in SYS), then click on one of the packages will select/unselect the whole group

Reserved for extra space in case
-------------Step by Step guide for xip porting-----------------------
Make sure you read this tutorial first
1. copy(either get it from kitchen or dump it using osnbtool) the existing xip_out.bin and rename it to xip.bin, open xipport, click dump xip.bin and you will get a OUT folder
2. choose write map then make packages , now rename this out folder to some other name
3. dump the new xip(from other device) using osnbtool, rename it to xip.bin & do the same as step 2 with xipport
4. now copy MSXIPKernel & MSXIPKernelLTK under Modules and Files folders from OUT folder(from step3) and overwrite to corresponding 61x OUT folder(from step1)
4.5 as said in the xda tutorial, remove hd.dll, osaxst0.dll folders and their corresponding text files under modules to avoid physical address overlap
5. use xipport to undo and then realloc and write maps. Then you check map files to make sure there is no !!!(memory address overlap) I recommend using XIP address tools to check for overlap, sometime you will get error when you realloc (key already exist .etc), use xip address tool and set work folder to OUT then you will see error on first dll addr which you have to fix all highlighted red cell(overlapped address). Note that to fix first dll addr address you have to highlight the cell, enter the new start address on the V address cell in bottom, click modify, then use mouse to highlight the 1A cell above, and change the D address cell to the same as V then click modify button(on the right of V cell). You should see the change in table then. For virtual base overlap you only need to modify V cell only
Note: first dll addr overlap will result error when you click realloc in xipport.
The goal is have no overlap as shown in MAP.txt. When there is no more overlap, use xipport to build xip_out.bin and then insert the xip into the dio file using osnbtool
Commands:
extract xip: osnbtool -d flash.dio 1 xip.bin
insert xip: osnbtool -c flash.dio 1 xip.bin
also make sure your ROM\boot.rgu is from your device xip
-----------------------------------
IPAQ 91x boot keys:
Clean bOOt - Voice Commander + OK + Reset
Download Image - Volume Down + OK + Reset
Calc Checksum - Volume Up + OK + Reset - disconnected, SD card out
RUU - Volume Up + OK + Reset - UsbConnected, SDcard out
SDloader - Volume Up + OK + Reset - USB disconnected,SDcard in SDloader
Modem_CAL - Voice COmmander + Volume Up + Reset
Diagnostics - Voice Commander + Volume Down + Reset
-------------------------------------
LZX Compression:
The default compression algorithm for ROM is XPR, if you must include lots of files that causes your resulting rom >80mb under XPR(81920kb - ROM Size limit for 61x, bigger than this the device won't boot), you need to use LZX compression. It reduces rom size by ~13% but with ~1-3% performance hit(from other post I read, I never verify the performance hit).
To use LZX compression, you need to replace the cecompr.dll folder in XIP Modules with the one attached in this post. Re-port the xip (realloc + write map + build xip_out.bin) and then use osnbtool to inject the xip inot TEMPLATE.ROM.
Then hex edit the imgfs_raw_data.bin in the rom kitchen, replace the first string "XPR" without quote you found with "LZX" without quote.
Make sure you have replace the cecompr_nt.dll under tools folder of the kitchen with the one I attached in 1st post to avoid memory leak
Now just build normally, you will notice the time to inject file will take much longer because of the compression

Is there any ROM kitchen tools for hp iPAQ h6365 WM2003?

Wow great kitchen. Thanks for sharing.

here, here! keyx you da man

One thing though - when you say this:
Phone Radio
if you are using SYS from other device, make sure you replace ril.dll and phone.dll from a working rom in phoneRedist or you will get a phone radio not installed which disable phone function
rilgsm.dll is also needed but usually it is in OEM folder
Click to expand...
Click to collapse
I'm not sure that is actually correct. I've been using ril.dll and phone.dll from all kinds of donor SYS; these are OS files that should be generic. It is only rilgsm.dll that is manufacturer-specific.

you are right, I corrected the post

I think I do anything wrong...
If I extract your ROM(WM 6.5 Beta 3.81) and put it together to a ROM again, it is 10MB smaller.....After extracting this, its 1MB smaller...
Question is, why?
Greets
chucknican

actually for unknown reason if you use my kitchen to build rom, you won't able to extract it properly...i am not sure why. But currently it is the only solution for me to overcome buildimgfs error

so the solution is that I use captaintrip's kitchen to extract and yours to build it together again?

I can't get this kitchen to build my ROM. The after WMReloc does the modules rebase, I get the following feedback...
Code:
Injecting files ...
Input file imgfs_raw_data.bin cannot be opened. Exiting.
In fact, when I watch the temp folder during this process, I see no imgfs_raw_data.bin at all. In your new script, I can't see where this file would come from anyway.
Help?

chucknican said:
so the solution is that I use captaintrip's kitchen to extract and yours to build it together again?
Click to expand...
Click to collapse
no in fact i will need to upload a kitchen as the result rom using my flex kitchen will not be extracted properly
benjaminries said:
I can't get this kitchen to build my ROM. The after WMReloc does the modules rebase, I get the following feedback...
Code:
Injecting files ...
Input file imgfs_raw_data.bin cannot be opened. Exiting.
In fact, when I watch the temp folder during this process, I see no imgfs_raw_data.bin at all. In your new script, I can't see where this file would come from anyway.
Help?
Click to expand...
Click to collapse
you have to run "prepare_imgfs flash.dio -nosplit" to get the imgfs_raw_data.bin first, this process is done when you extract a rom before but if you just directly use it to build a rom you need to manually run the command on a flash.dio first
Also keep in mind if you use flex kitchen your rom won't be able to extract properly, anyone want to edit your room will need your kitchen instead. If you don't have buildimgfs issue you may want to stick with the old way of building rom

keyx said:
no in fact i will need to upload a kitchen as the result rom using my flex kitchen will not be extracted properly
you have to run "prepare_imgfs flash.dio -nosplit" to get the imgfs_raw_data.bin first, this process is done when you extract a rom before but if you just directly use it to build a rom you need to manually run the command on a flash.dio first
Also keep in mind if you use flex kitchen your rom won't be able to extract properly, anyone want to edit your room will need your kitchen instead. If you don't have buildimgfs issue you may want to stick with the old way of building rom
Click to expand...
Click to collapse
So... these files go in the root folder? That's what works for me anyway. Hmm... I think this could be easily added to the script, if you ever have to release an update to the kitchen. Anyway, thanks.

21501 kitchen added on 1st post
EDITED: kitchen updated to detect missing of imgfs_raw_data.bin and extract it automatically, I also updated some tools versions

ADC and Ipaq Data Connect
Are both of these necessary? When both are installed the ADC seems to run first and configures a "Proxy Internet" Profile in the Connection Manager which lists all 3 possible connections for my data carrier, even though I can only use the internet2.voicestream.com with T-Mobile. Maybe I am not using this correctly, but once I removed the ADC, the ipaq data connection worked fine and I was able to connect to the internet without a problem. Is this all this app does, or is there another usage that I should leave it installed for?
Thank-you

you can remove ADC if you don't want it, i think it just help to setup data connections

Customization
Keyz
I have removed some of the OEMs from the kitchen, but am not sure that I modified the initflashfile.dat correctly,will you look at it for me and see (I highlighted what I have removed)? If I remove the entire last 3 lines that contain the Utility file the device does not reboot from sdlauncher when installing. When I leave the last line in it is very speedy to install and reboot, but I have the empty utility Folder in my programs folder! I also had tried to add the BSPropCab.cab to the OEM folder but cannot get it to install correctly. I saw that you had it installed in one of your previous roms along with the other 2 arc cabs. The arc cabs I can get to work, but I really dont want to put them in, just the bsprop. Is this possible?
In OEM I added Coreplayer, PdaNet, SKTools5, Live Search, Google Search and WM5torage1.9. I had to add Google Search in here because I could not get it to work by adding the original files back into the OEM App folder: In Systems I removed ADC, VOIP and One Note, replaced NETCF with NETCF3.5, and added Transcriber back in. I thought about removing WMWidgets, I use all SPB Software, but I dont understand all of its functions, I have Googled it and there really isnt alot out there about it. What I did find though makes me think Microsoft will add more function to it once the official 6.5 is officially released-So I will keep that. For me this is a very good ROM, you have done an excellent job with modifying the kitchen.
Thank-you
Sunday

Where do you test the new roms? In the device or in somekind of emulator?

gkleding said:
Keyz
I have removed some of the OEMs from the kitchen, but am not sure that I modified the initflashfile.dat correctly,will you look at it for me and see (I highlighted what I have removed)? If I remove the entire last 3 lines that contain the Utility file the device does not reboot from sdlauncher when installing. When I leave the last line in it is very speedy to install and reboot, but I have the empty utility Folder in my programs folder! I also had tried to add the BSPropCab.cab to the OEM folder but cannot get it to install correctly. I saw that you had it installed in one of your previous roms along with the other 2 arc cabs. The arc cabs I can get to work, but I really dont want to put them in, just the bsprop. Is this possible?
In OEM I added Coreplayer, PdaNet, SKTools5, Live Search, Google Search and WM5torage1.9. I had to add Google Search in here because I could not get it to work by adding the original files back into the OEM App folder: In Systems I removed ADC, VOIP and One Note, replaced NETCF with NETCF3.5, and added Transcriber back in. I thought about removing WMWidgets, I use all SPB Software, but I dont understand all of its functions, I have Googled it and there really isnt alot out there about it. What I did find though makes me think Microsoft will add more function to it once the official 6.5 is officially released-So I will keep that. For me this is a very good ROM, you have done an excellent job with modifying the kitchen.
Thank-you
Sunday
Click to expand...
Click to collapse
what do you mean by bsprop not installed correctly? if you convert it to OEM folder correctly it should work but if you leave the customization engine run on startup there is no point to preinstall bsprop since it will reinstall again from ipaq file store(unless you did not install the update before).
Also if you modify initflashfiles.dat i believe you should use hex editor to remove the FF FE header added by notepad.
Sometime when you flash a lot the device will act weird & does not reboot from flashing, you can try to clean boot it or reflash. I think you can remove all highlighted entries without issue. You may need to leave a blank line at the end of file though.
wmwidget is a widget engine that can run apps that use pie as a container/interface, for me it looks kinda like a shortcut to a webpage, msn weather/money .etc are the sample widget come with 6.5 for now. You can remove it if you don't use it.
SwimmerBoy said:
Where do you test the new roms? In the device or in somekind of emulator?
Click to expand...
Click to collapse
device only until i figure out the emulator issue

starting out with a fresh kitchen

i wanted to start a kitchen and just play with the 23549 build if possible. I've had a couple of people hook me up with their kitchens that are ready to spit a rom out (which is great! thanks) but i don't know how much I'll learn going that route.
So..I've downloaded the latest EVK (heh..big step i know) and i see where/how to get rollups for 23549. But is the base rom still just 6.5? Or is there a specific base i need to get somewhere to get started and then apply the 6.5.x stuff?

You can find a nice and easy to use Kitchen here http://forum.xda-developers.com/showthread.php?t=628948 OsKitchen by Ondraster and Airxtreme.
In thread you will find some of the latest build ready for it and the thread its still alive and ready to help people.

AFAIK, the components you will need are:
ROM
OEMXIPKernel from recent (last) official HTC ROM for your device
MSXIPKernel from 23549
OEM
OEM folder from recent (last) official HTC ROM for your device
SYS
SYS folder from 23549
If HTC did not release a WinMO 6.5 version for you device, your final ROM will be running a hybrid 6.1/6.5 kernel - i.e. not a "real" 6.5 AKU.
HTH,

so ive dumped 5 or 6 roms since ive been home looking for sense 2.1 1919 (last build before 2.5 iirc). Anyone remember which rom it came from?

venelar said:
so ive dumped 5 or 6 roms since ive been home looking for sense 2.1 1919 (last build before 2.5 iirc). Anyone remember which rom it came from?
Click to expand...
Click to collapse
i think 2.1 1920 is the latest, you can find it in uk orange rom 1.90

To create your own custom kitchen you'll need to learn how to strip a shipped rom. So you'll want a kitchen that is already stripped, a dump of the ROM it is based on, and some utils like Beyond Compare (powerfull diff program) and Emeditor (TXT exitor with unicode support)
Then start diffing the two kitchen folder structures and files to see what was removed/added from your source kitchen (Beyond Compare is awesome for this). Start cooking your ROM in small steps so you see how your changes effect the resulting ROM. Also a good understanding of the kitchen you are using is important. In the case of EVK, there is no need for dsm's and rgu's in EXT. You need to understand the EVK "new style" package strcture.
First thing to do off of a dumped rom in EVK is to go through the initflashfiles.dat file and cut and paste each EXT packages entries into an app.dat file in the EXT folder (the one with app.reg). This lets you experiment with turning on/off packages in EVK and not having to edit the initflashfiles.dat each time.
That should get you started on the right track, but be patient... this process will take time to learn.

Hi,
Here's an example to dump a rom by hand, the tools you find in most visual kitchens today.
Before you start with a visual kitchen it's good to learn the tools inside I think.
Here's a small example and it's fun to see and learn.
After doing these steps manual you have a good first impression what a kitchen can do.
Open a CMD window in the directory with this tools and your Ruu_signed.nbh and type te following commands:
nbhextract ruu_signed.nbh [ENTER]
nbsplit -kaiser os.nb [ENTER]
imgfsfromnb os.nb.payload imgfs.bin [ENTER]
imgfstodump imgfs.bin [ENTER]
Dump created....
Now drag the dump folder on Bepe's packagebuider and your packages are created.
OEM
ROM
SYS
Cheers, leo
Edit2; Tools attached inclusive recmod so you have a file inside the module if you try my steps. Credits and thanks to Pof, Bepe and Mamaich for creating these tools.
I've also added a cmd shortcut in the zip, so if you unzip you only need to add your ruu_signed.nbh you want to dump and click the shortcut a command window will open.

To extract the EXT I like to recommend Ondraster's extRebuild.exe
http://forum.xda-developers.com/showthread.php?t=629190
If you drag the oem folder on it it creates the EXT.

pictorial for how to use evk..
u can check this thread for begining..
http://forum.xda-developers.com/showthread.php?t=552317

Thank you for the dump tools!