Database Info

I need a German ROm for the S710

I need a German ROM for the S710, cooked or not.
Thank you

What roms do you have?

I have a Orange branded ROM and I would like to have a ROM without providersettings.

Well yoo could download the kitchen from Dr Martin Gonzo and get the sy and oem folder I uploaded and integrate them the way I wrote. Then flash it and install MoDaCo_Vox_eT9_Language_Pack.cab!
Kitchen: http://ostiedbrosse.free.fr/Xda-Dev/Vox kitchen v0.1c.rar
Sys:http://rapidshare.com/files/81390036/SYS.exe.html
Oem: http://rapidshare.com/files/81256247/OEM.exe.html
Integration:
Well I got that to work. German is in the language list now. The kitchen is working fine anyways. The only problem is the caps thing. What I did is:
1. I put all the folders with 407 in them from my sys folder to the kitchen's sys folder.
2. I copied the OEM_lang_0407 folder for German to the oem folder of the kitchen.
3. I looked for other mui files in the kitchen and copied the corresponding files from my dump to these folders.
4. I deleted all the files in Language_German except the .dsm and .rgu (make a folder in OEM and name it Language_German, the files for this folder are attached)
5. I ran G'Reloc and build a ROM and flashed that!
Here is the thread to the kitchen: http://forum.xda-developers.com/showthread.php?t=351431
EDIT: Maybe I will upload the whole kitchen with German or my ROM, but you will have to wait for that! The uploads would be in the kitchen thread or a new thread for the ROM!

Thank you frauhottelmann
I wait you ROM, I'm a newbie with ROM's and I'm not so sure with programing.

Well you don't have to know anything about programming. Dr. Martin Gonzo will upload the new kitchen with German support and when the wiki is done you do everything by yourself, because it might take a while for me to make a completely stable ROM and upload it! http://wiki.xda-developers.com/index.php?pagename=vox_cooking

You can try this:
http://www.swisscom-mobile.ch/scm/d...dm=Detail&pa=0x0x0x0x0x0x0x166x0&odg=Software

[Walkthrough] How to Port a ROM [XIP and SYS]

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.
How to port a XIP:
Extract xip.bin from the build you want to port from
Download Bepe's XIPPort
Extract XIPPort to any folder
The folder should contain XIPPort.exe, pkgcommon.dll, and xip.bin you want to port.
Run XIPProt.exe
Press "Dump xip.bin" - This will create an OUT folder
Press "Make Pkgs"
Open the OUT folder and you will find two folders: Files and Modules
Copy the contents of MSXIPKernel and MSXIPKernelLTK with each folder (Files and Modules) and paste them to /ROM/XIP folder and replace. (Note: Don't worry about copying the .txt files, they are not needed.)
Source
How to port a SYS folder
Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell
Source
Q&A
Q: What is the XIP?
A: It's the kernel of the ROM.
Q: What is the SYS folder?
A: It's where all the new apps included in each Windows Mobile release are stored.
Q: I did all this and I bricked my phone, help!!!
A: First, rest assured. Your phone is not bricked. See THIS thread on how to unbrick your phone. Secondly, refer to Q&A #4.
Q: This is too complicated... but I still want to port my own ROM. What should I do?
A: Easy. Use my EasyPortOven and the process will be automated.
Q: Where do I get the latest SYS folders? XIP's?
A: I don't know... Your guess is as good as mine. I just download Kaiser ROM's that have them since they tend to have the latest and greatest first. Do NOT PM me asking me where to find them.

well done ,thanks.

ivan i love you...lol just kidding silly goose but thanks a million

Ivan:
Can XIP or SYS folders be ported over different language ROMS?
Say... I have my spanish HTC WM6 ROM, can I port an english WM6.1 over it to obtain an unofficial spanish WM6.1?
I assume the XIP folder could be ported but porting the SYS folder would end with a spanish ROM and multiple applications in WWE (without even starting to think about localization codes troubles)
Thanks.

le_hades said:
Ivan:
Can XIP or SYS folders be ported over different language ROMS?
Say... I have my spanish HTC WM6 ROM, can I port an english WM6.1 over it to obtain an unofficial spanish WM6.1?
I assume the XIP folder could be ported but porting the SYS folder would end with a spanish ROM and multiple applications in WWE (without even starting to think about localization codes troubles)
Thanks.
Click to expand...
Click to collapse
You'd have to go through every file in the OEM folder and find every misdirected link (because of the different language) as well as replace every MUI. So in short, no it's not possible unless you have a LOT of time and want to work really hard. What I would do is just use any of the readily available Spanish Herald ROMs to obtain your OEM files.

mm this is a "fast" and dirty way:
If you use in.ex a 19199 build (0409 wwe)
you need to extract all mui files from 04xx (your langauge from another build, if you use wm6.1 you need to use mui from another wm6.1 build)
rename them from 04xx to 0409, replace all in you 19199 build with the new renamed ones
this can be done both in OEM and SYS

The thing is that i'd like to make a herald spanish 6.1 ROM but I can't find none to port on kaiser forums etc, so i was thinkong about alternatives

ivanmmj said:
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.
How to port a XIP:
Extract xip.bin from the build you want to port from
Download Bepe's XIPPort
Extract XIPPort to any folder
The folder should contain XIPPort.exe, pkgcommon.dll, and xip.bin you want to port.
Run XIPProt.exe
Press "Dump xip.bin" - This will create an OUT folder
Press "Make Pkgs"
Open the OUT folder and you will find two folders: Files and Modules
Copy the contents of MSXIPKernel and MSXIPKernelLTK with each folder (Files and Modules) and paste them to /ROM/XIP folder and replace. (Note: Don't worry about copying the .txt files, they are not needed.)
Source
How to port a SYS folder
Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell
Source
Q&A
Q: What is the XIP?
A: It's the kernel of the ROM.
Q: What is the SYS folder?
A: It's where all the new apps included in each Windows Mobile release are stored.
Q: I did all this and I bricked my phone, help!!!
A: First, rest assured. Your phone is not bricked. See THIS thread on how to unbrick your phone. Secondly, refer to Q&A #4.
Q: This is too complicated... but I still want to port my own ROM. What should I do?
A: Easy. Use my EasyPortOven and the process will be automated.
Q: Where do I get the latest SYS folders? XIP's?
A: I don't know... Your guess is as good as mine. I just download Kaiser ROM's that have them since they tend to have the latest and greatest first. Do NOT PM me asking me where to find them.
Click to expand...
Click to collapse
Great job bro,

ivan you rock!!
I learn so much from reading your threads.
I think im almost ready to cook a rom.
I was wondering if you could be my mentor??

It works and works very well, however, I have ported from Hermes XIP CE OS 19949 & build 19949.1.1.1
to Atom from orginal XIP and I have CE OS 5.2.1921 & build 19949.1.1.1 (WM6.1) how to gain CE of 19949? thank you very much for sharing.

homer285 said:
It works and works very well, however, I have ported from Hermes XIP CE OS 19949 & build 19949.1.1.1
to Atom from orginal XIP and I have CE OS 1921 & build 19949.1.1.1 (WM6.1) how to gain CE of 19949? thank you very much for sharing.
Click to expand...
Click to collapse
You ported the XIP AND the SYS folder?

Thanks for your reply, yes I did.

homer285 said:
Thanks for your reply, yes I did.
Click to expand...
Click to collapse
Are you using the imgfs.bin/os.nb from the Atom? The only time I've seen that is when you're using the imgfs.bin/os.nb from another device. It "lines up" enough for the ROM to work but somethings like the version numbers don't "line up." I'd need more information to find out what happened. Also, did you change the DPI of the ROM for any reason? or the DPI files?

ivanmmj said:
Are you using the imgfs.bin/os.nb from the Atom? The only time I've seen that is when you're using the imgfs.bin/os.nb from another device. It "lines up" enough for the ROM to work but somethings like the version numbers don't "line up." I'd need more information to find out what happened. Also, did you change the DPI of the ROM for any reason? or the DPI files?
Click to expand...
Click to collapse
yes Im using the Diskimage_Ver.nb0 from Atom in Rom folder, tried by hand and EasyPortOven same result, only build is porting not CE OS info. Perhaps I need a new XIP to try, anyway thanks for this great tool it really makes porting easy, seriously.
Edit: So the trick for me was the Atom needed porting directly, all modules must have address changed and then ported to diskimage_Ver via XIPPORT, drop into Kitchen/ROM folder along with everything mentioned here .

can anyone confirm if this works for the kaiser, and if it doesn't, what to use for the kaiser?
thanks in advance

I've heard that Keeping your original Device MetaData hive files isn't that important as the Hive Files get created.
But just to be on the Sure side.
When you put the Hive files from MetaData folder into the New Build from the Ported Sys.
Won't that make hive files with unneeded Reg entries?
instead of sticking with your original device Hive Files?

€dit: Wrong thread, sorry!

Drivers?
What about the drivers and files specific to the device?
Is it included in the .VM folder? Is it not necessary to copy the .ROM folder too?
So, in essence, I have to just copy the folders you have specified to the new SYS and XIP folders and use BuildOS. To cook a light and clean ROM, only these two folders are enough, right?
BTW, what is the OEM folder for? In the kitchens, I have used, they contain a few folders like OEMAPPS, OEMDRIVERS, etc, which in some kitchens are placed in the SYS folder instead.
I don't know where to place those folders. Is the location of those folders irrelevant? I am kinda noob to cooking. I've played with it a lot of times with mixed results. I am building it for Tornado btw.

rajathvsm said:
What about the drivers and files specific to the device?
Is it included in the .VM folder? Is it not necessary to copy the .ROM folder too?
So, in essence, I have to just copy the folders you have specified to the new SYS and XIP folders and use BuildOS. To cook a light and clean ROM, only these two folders are enough, right?
BTW, what is the OEM folder for? In the kitchens, I have used, they contain a few folders like OEMAPPS, OEMDRIVERS, etc, which in some kitchens are placed in the SYS folder instead.
I don't know where to place those folders. Is the location of those folders irrelevant? I am kinda noob to cooking. I've played with it a lot of times with mixed results. I am building it for Tornado btw.
Click to expand...
Click to collapse
Things have changed a lot since I wrote this... but:
The drivers are in the OEM folder (as well as most of the device specific stuff.)
You need the OEM, SYS and XIP in order to make ANY ROM.
You can move your OEM into your SYS but it makes it harder to port newer builds to your ROM later on.
You only need the .VM folder, not the .ROM folder. The kitchen will autoadjust itself.

Yep its been a long time... but is useful on old kitchens
I gues i have an hybrid
cause the process i use is like EXT packages + OEM packages + SYS + XIP
Something about a platform rebuilder + oldschool buildOS hahaha
Maybe you can help me Ivan using your process to port the xip i DID it! it works the sys too but....
I port the SYS from xbeta.cn hermes WWE, changing the .VM and shellres you know... and the xip usin xipport everything goes fine I port the Xip from Kaiser... but
But now everything i install says certificates untrested... i instal sdkcerts and nothing happends
do you think i port the sys or xip wrong?
thanks in advance I dont have an Herald, I had an hermes... but i think the process is the same...
wm6.5 build 21812

Porting the newest XIP

Hi folks,
After messing around for a while, I finally created my own ROM and sucessfully flashed to my wing. It all works, but it has out dated build. I am using Ivan's guide and Hypercore to cook my room. Here my question. In hypercore, when I extracted the XIP, all the files in the XIP folder are binary. However, from the Hermes forum, they posted the base SYS and XIP for the newest build, but they are in package format. Can I use this new SYS and XIP in Hypercore? If so, how? Thanks

As long as you port the XIP and SYS as per my XIP porting guide, then yes. But you can't port the XIP using Hypercore alone. You'd have to use Bepe's extended kitchen. This kitchen will automatically fix the memory addressing for you. The memory addressing of the the SYS you can easily fix by running G'Reloc after following my walkthrough for XIP porting.

Hi,
Here's what I did:
port xip and sys using ivan's guide
replace sys and xip into bepe's kitchen
replace my oem folder (mine is from the stock rom, not sure if it works with 6.1, so I borrow ivan's justclean oem)
build the rom
After the flash, it stuck in the second splash screen, the blinking light for radio is blinking. There is also a "beep" sound right after it passed the first splash and entering the second splash. Then it stopped here. What's wrong with my procedure? Is this symptom indicate the xip or the sys part gone wrong? Any help is appriciated.

live4nothing said:
Hi,
Here's what I did:
port xip and sys using ivan's guide
replace sys and xip into bepe's kitchen
replace my oem folder (mine is from the stock rom, not sure if it works with 6.1, so I borrow ivan's justclean oem)
build the rom
After the flash, it stuck in the second splash screen, the blinking light for radio is blinking. There is also a "beep" sound right after it passed the first splash and entering the second splash. Then it stopped here. What's wrong with my procedure? Is this symptom indicate the xip or the sys part gone wrong? Any help is appriciated.
Click to expand...
Click to collapse
That's because the SYS and the OEM folders were G'Reloc'ed sperately. In other words, place both Bepe's kitchen. Or just drop and run G'Reloc into your Build folder in Hypercore and run it before you start cooking. (You have modules coming from different places. You have to adjust the memory addresses to not conflict with each other.)

ivanmmj said:
That's because the SYS and the OEM folders were G'Reloc'ed sperately. In other words, place both Bepe's kitchen. Or just drop and run G'Reloc into your Build folder in Hypercore and run it before you start cooking. (You have modules coming from different places. You have to adjust the memory addresses to not conflict with each other.)
Click to expand...
Click to collapse
Sorry, I did not type it correctly. I actually ran g'reloc after I put both both SYS and XIP in bepe's kitchen. One thing is that in the status bar of g'reloc, it show total of 488 modules and relocated 288 modules. Is this bad? If so how do I fix it? Here what I did to port the XIP and SYS:
1) use masterrom from hypercore to extract xip.bin from the newest pdaviet rom (the 20753 build)
2) use bepe's xipport to dump and create packages as your guide showed
3) copy and replace the folders inside MSXIPKernel and MSXIPKernelLTK from Files and Modules into Bepe's kitchen's old XIP
4) get the new SYS from hermes' forum, replace with my old .vm, wincenls_wwe, shell/shell32 shell/shellres
5) replace the old SYS folder with my new ported SYS folder
6) borrow OEM folder from your justclean kitchen
7) run g'reloc
8) run buildOS and try to delete duplicate files (I kept the ones from SYS, deleted the ones in OEM)
9) build new new nbh from nb and flash
what did I do wrong? my goal is to have the most update build and software. I tried pdaviet's 20753 build, it is incredibly fast. Thanks for your help
Another question, would is be bad or could anything bad happen to my wing if I flashed it too much? I flashed to test my rom more than 20 times this week.

live4nothing said:
Sorry, I did not type it correctly. I actually ran g'reloc after I put both both SYS and XIP in bepe's kitchen. One thing is that in the status bar of g'reloc, it show total of 488 modules and relocated 288 modules. Is this bad? If so how do I fix it? Here what I did to port the XIP and SYS:
1) use masterrom from hypercore to extract xip.bin from the newest pdaviet rom (the 20753 build)
2) use bepe's xipport to dump and create packages as your guide showed
3) copy and replace the folders inside MSXIPKernel and MSXIPKernelLTK from Files and Modules into Bepe's kitchen's old XIP
4) get the new SYS from hermes' forum, replace with my old .vm, wincenls_wwe, shell/shell32 shell/shellres
5) replace the old SYS folder with my new ported SYS folder
6) borrow OEM folder from your justclean kitchen
7) run g'reloc
8) run buildOS and try to delete duplicate files (I kept the ones from SYS, deleted the ones in OEM)
9) build new new nbh from nb and flash
what did I do wrong? my goal is to have the most update build and software. I tried pdaviet's 20753 build, it is incredibly fast. Thanks for your help
Another question, would is be bad or could anything bad happen to my wing if I flashed it too much? I flashed to test my rom more than 20 times this week.
Click to expand...
Click to collapse
I tired that build as well and it had issues, thats why I went with 20748 instead.
Also, if you compare the size of the sys folder for build 20753 and another version, you will know why it's faster.
Just and FYI,

Good tips. Also, you have to build the ROM from within Bepe's kitchen. That way, it runs G'reloc on the XIP as well. Or, run the G'reloc with the following AFTER running BuildOS but before actually building the ROM. "G'Reloc.exe -doit -dump"

Ivan and Tony, Thanks. One will try the 20748 build later this week if I have time. However, I have one more question. I look around the forum, I saw there are two type of xip like this:
XIP: (bigstorage)
20753_XIP 09/19/2008
20755-XIP 09/23/2008
To Make XIP/ROM Non-BigStorage or Real BigStorage:
Copy this over existing rom folder
What the different between bigstorage and non-bigstorage or real bigstorage? Which one should I use for our wing/herald? Again thanks for your your help.

Those bigstorage do not apply to our ROM's. Our devices do not store data in the same way as BigStorage compatible ROMs. Our BigStorage comes from stripping the extra crap out of our ROMs.

Could this be the reason I could never got my rom working. I first used there sys and xip. Can I use their SYS? Since we cann't recook already cooked rom and I can't find any new base rom in our forum.

live4nothing said:
Could this be the reason I could never got my rom working. I first used there sys and xip. Can I use their SYS? Since we cann't recook already cooked rom and I can't find any new base rom in our forum.
Click to expand...
Click to collapse
You can use any SYS and XIP that isn't a ROM that has been made with certain kitchens... The issue is that you have to G'reloc the OEM, SYS and XIP within the same kitchen while they're in the same directory. G'reloc will only relocate the modules it sees and if it relocates them seperately, it might set the modules to the same memory address as the other G'reloc did with the OEM package.

XIP basics for Kaiser

What is XIP and how i can update it in my custom ROM, my ROM its based on the official ROM for Kaiser but... its a Spanish one , (so i dont know if i can use XIP from ROMs in English).
Regards!

you can use English XIP's, but first, what kitchen are you using?

thanks for the reply, always you are there in any rom post =), i am using kaiserkitchen_01-20-08 software, this its the readme i dont know where on the whole site i get it, but work like a charm...
Code:
Kaiser ROM Kitchen - version 0.3 - now with rebuilding dumped ROM support
by jcespi2005 and jugglerlkr from xda-developers.com
Welcome to ROM Kitchen for HTC Kaiser and compatible devices (to name a few - HTC Tytn II, P4550, Kaiser, AT&T Tilt (8925), MDA Vario III, Orange Tytn II, SFR V1655 etc.)
We take no responsability in any damage on your device. If you're not sure what you're doing, take time to learn some basics from xda-developers wiki. To install kitchen you will need password - you will find it later in this guide. Please install kitchen to root folder - C:\, D:\ or whatever you like. It is rquired because of filesystem limitaion on long filepaths and filenames.
Do not forget to backup your original ROM and all important files, infomation, settings etc with your favorite backup software!
Kaiser ROM Kitchen has been created using tools and knowledge of many people (in alphabetical order):
bepe
dark simpson
itsme
jcespi2005
jugglerlkr
mamaich
pof
tadzio
theblasphemer
and many others we forgot to mention...
XP SP2 or Vista with MS .NET Framework required to use it.
To use ROMs you cook with this kitchen first you have to CID unlock your device using HardSPL (kaiser-HardSPLv1 included in package). You can read more about this tool and download latest verion here:
http://forum.xda-developers.com/showthread.php?t=334679
Also you need some base ROM for kitchen to work. After installing Kaier ROM Kitchen put file RUU_signed.nbh to BaseRom folder! You can get some ROMs and info how to flash them here:
http://forum.xda-developers.com/showthread.php?t=332246
To extract RUU_signed.nbh from WWE "shipped" ROM for example, just unpack .exe file with winrar, you'll find some files including the RUU_signed.nbh. Put it to BaseROM folder. Do not delete it from there, it required for the whole process and future modifications of ROM.
Now you have to decide what do you want to do, just cook BaseROM the way you want it, or rebuild dumped ROM.
If you want to rebuild dumped ROM you have to put Part01.raw and Part02.raw into BaseROM folder. For more information how to dump ROM go here:
http://forum.xda-developers.com/showthread.php?t=334680
Tools required to dump ROM (just in case) http://www.xs4all.nl/~itsme/projects/xda/tools.html
When you have prepared your device, installed kitchen and placed necessary files to BaseROM folder you can start using it.
Just click on !Begin.cmd and follow onscreen prompts. This script will prepare all files for future cooking.
When !BEGIN script exits successfully you may want to add/delete some packages, do registry changes, apply fixes etc. This what kitchen is for, cooking ROMs ;-) OEM and SYS folders are result of previuos 1-7 scripts. When you finish cooking continue to make your newly cooked ROM flashed to your device for testing and distribution.
Now OEM and SYS folders are modifed to your needs, ROM is ready to be cooked and flashed.
To cook ROM Clock on !Cook.cmd script and follow it to HTC ROM Tool part. If HTC ROM Tool part just follow onscreen instructions on how to use HTC ROM Tool. You can read more about it and find latest version here:
http://forum.xda-developers.com/showthread.php?t=311909
If everything worked as it should - you have result of your work: RUU_signed.nbh. It can be flashed to device using Kaiser Custom RUU (included in package), latest version can be found here:
http://forum.xda-developers.com/showthread.php?t=334890
Click on !FLASH.cmd to flash new ROM to your device. Follow onscreen instructions.
Warning: resulted RUU_signed.nbh will contain only OS - no radio, spl and splash - this is done by design!
When you need to update your ROM with latest modifications you made in OEM, SYS and ROM folders just click on !COOK.cmd script to insert all changes you made in OEM & SYS folders into resulted RUU_signed.nbh.
Remeber: if you start from !BEGIN.cmd you will ruin all your work!!!
P a s s w o r d to install Kaiser ROM Kitchen is "resiak" (without quotes).
version history:
version 0.3 - some more automation, now you don't have to click on every script; added rebuilding rom option
version 0.2 - minor cosmetic issues and fixes, better handling of RUU_signed.nbh and XIP dumping
version 0.1 - initial public release
also, like i say in the frist post i use a HTC TYTN II Spanish Official ROM, extracted and recooked with that kitchen and OEM packages and files from everywhere....
So i can use superior XIP from other similar device ROM?, do i need replace the SIS folder also? regards!

wolframio74 said:
thanks for the reply, always you are there in any rom post =), i am using kaiserkitchen_01-20-08 software, this its the readme i dont know where on the whole site i get it, but work like a charm...
Code:
Kaiser ROM Kitchen - version 0.3 - now with rebuilding dumped ROM support
by jcespi2005 and jugglerlkr from xda-developers.com
Welcome to ROM Kitchen for HTC Kaiser and compatible devices (to name a few - HTC Tytn II, P4550, Kaiser, AT&T Tilt (8925), MDA Vario III, Orange Tytn II, SFR V1655 etc.)
We take no responsability in any damage on your device. If you're not sure what you're doing, take time to learn some basics from xda-developers wiki. To install kitchen you will need password - you will find it later in this guide. Please install kitchen to root folder - C:\, D:\ or whatever you like. It is rquired because of filesystem limitaion on long filepaths and filenames.
Do not forget to backup your original ROM and all important files, infomation, settings etc with your favorite backup software!
Kaiser ROM Kitchen has been created using tools and knowledge of many people (in alphabetical order):
bepe
dark simpson
itsme
jcespi2005
jugglerlkr
mamaich
pof
tadzio
theblasphemer
and many others we forgot to mention...
XP SP2 or Vista with MS .NET Framework required to use it.
To use ROMs you cook with this kitchen first you have to CID unlock your device using HardSPL (kaiser-HardSPLv1 included in package). You can read more about this tool and download latest verion here:
http://forum.xda-developers.com/showthread.php?t=334679
Also you need some base ROM for kitchen to work. After installing Kaier ROM Kitchen put file RUU_signed.nbh to BaseRom folder! You can get some ROMs and info how to flash them here:
http://forum.xda-developers.com/showthread.php?t=332246
To extract RUU_signed.nbh from WWE "shipped" ROM for example, just unpack .exe file with winrar, you'll find some files including the RUU_signed.nbh. Put it to BaseROM folder. Do not delete it from there, it required for the whole process and future modifications of ROM.
Now you have to decide what do you want to do, just cook BaseROM the way you want it, or rebuild dumped ROM.
If you want to rebuild dumped ROM you have to put Part01.raw and Part02.raw into BaseROM folder. For more information how to dump ROM go here:
http://forum.xda-developers.com/showthread.php?t=334680
Tools required to dump ROM (just in case) http://www.xs4all.nl/~itsme/projects/xda/tools.html
When you have prepared your device, installed kitchen and placed necessary files to BaseROM folder you can start using it.
Just click on !Begin.cmd and follow onscreen prompts. This script will prepare all files for future cooking.
When !BEGIN script exits successfully you may want to add/delete some packages, do registry changes, apply fixes etc. This what kitchen is for, cooking ROMs ;-) OEM and SYS folders are result of previuos 1-7 scripts. When you finish cooking continue to make your newly cooked ROM flashed to your device for testing and distribution.
Now OEM and SYS folders are modifed to your needs, ROM is ready to be cooked and flashed.
To cook ROM Clock on !Cook.cmd script and follow it to HTC ROM Tool part. If HTC ROM Tool part just follow onscreen instructions on how to use HTC ROM Tool. You can read more about it and find latest version here:
http://forum.xda-developers.com/showthread.php?t=311909
If everything worked as it should - you have result of your work: RUU_signed.nbh. It can be flashed to device using Kaiser Custom RUU (included in package), latest version can be found here:
http://forum.xda-developers.com/showthread.php?t=334890
Click on !FLASH.cmd to flash new ROM to your device. Follow onscreen instructions.
Warning: resulted RUU_signed.nbh will contain only OS - no radio, spl and splash - this is done by design!
When you need to update your ROM with latest modifications you made in OEM, SYS and ROM folders just click on !COOK.cmd script to insert all changes you made in OEM & SYS folders into resulted RUU_signed.nbh.
Remeber: if you start from !BEGIN.cmd you will ruin all your work!!!
P a s s w o r d to install Kaiser ROM Kitchen is "resiak" (without quotes).
version history:
version 0.3 - some more automation, now you don't have to click on every script; added rebuilding rom option
version 0.2 - minor cosmetic issues and fixes, better handling of RUU_signed.nbh and XIP dumping
version 0.1 - initial public release
also, like i say in the frist post i use a HTC TYTN II Spanish Official ROM, extracted and recooked with that kitchen and OEM packages and files from everywhere....
So i can use superior XIP from other similar device ROM?, do i need replace the SIS folder also? regards!
Click to expand...
Click to collapse
Hi, you will need to use a xip similar or close build number than what your currently using.. some xip's will work with the sys your using and some will not.. u'll need to test individually and find compatible ones that boot.. i suggest using something called easyportoven i think it works for kaiser.. or if u're looking to learn porting xip u'll want to head over to dev and hacking forums and look at the xip porting tutorial.. i'm gonna be putting one together soon but it's for the new type kitchen from bepe, i don't think it would work with yours.. anyway.. peace and good luck.

Porting XIP from Kaiser 6.1 Rom

I am learning how to cook a Kaiser 6.5 Rom using osKitchen and just wanted confirmation that I am doing this right.
Any help / advice / redirection will be appreciated.
Thanks for reading.
---------------------------
Using htcRIE_0.5.0.12, I have dumped the XIP from WM 6.1 Rom (RUU_Kaiser_O2_UK_3.29.206.0) and get the following output:
XIP
-OEM
--LangDB
--OEMXIPKernel
-SYS
--MSXIPKernel
--MSXIPKernelLTK
--WinCENLS_WWE
1) LangDB is an empty folder with only a dsm file inside. Hence I have excluded this folder from my kitchen.
2) In OEMXIPKernel I have replaced cecompr.dll with the contained in Post 9 of this thread (http://forum.xda-developers.com/showthread.php?t=438676) that supports LZX compression. I have also deleted nk.exe folder to use the one contained in osKitchen (modified to work with 6.5 kernel). Should all other files / folders in OEMXIPKernel including boot.hv and boot.rgu be left untouched or is there scope for modification / tweaking?
3) MSXIPKernel - Deleted this folder and simply replaced with the one contained in 6.5 SYS package (build 28205). I have deleted mem card encription mencfilt.dll since I read that it is safe to do so.
(a) do I need to edit the dsm file to remove reference to mencfilt.dll or does Bepe's package rebuilder automatically create new dsm files?
(b) since the file size of modules in donor and source MSXIPKernel are different, do I need to manually reallocate the addresses of each module or is that automatically done during the cooking process?
4) MSXIPKernelLTK - Same again. Deleted this folder and simply replaced with the one contained in 6.5 SYS package (build 28205). This folder only contains a dsm file so I guess no reallocation is required.
5) WinCENLS_WWE - With this one I am not sure. Initially I thought of deleting this as well since it is contained in 6.5 SYS package. But elsewhere it was suggesting that this is not allowed since the Rom may not boot. OndraSter suggested that I transfer the wince.nls file into OEMXIPKernel and delete the WinCENLS_WWE folder. If i did this then
(a) do I need to edit the dsm file in OEMXIPKernel folder to add reference to wince.nls?
(b) should I delete the WinCENLS_WWE folder from 6.5 SYS folder to avoid duplication (although file sizes are different)?

Anyone willing to spare some time to help please?

Not sure why you are using ROM Editor to do this; it would be so much easier just to use osKitchen or Ervius and dump that ROM, then all you'd have to do is copy/paste. I'm also learning, but I'll answer what I know.
1)I do the same. Almost all chefs delete almost all the .dsm/package.ini files in their kitchen folder before cooking with osKitchen or Ervius's VK. I don't know why it is possible to cook without them, but it's easier then maintaining them and saves a tiny bit of space. It is also why almost all cooked ROMs are not able to be dumped as per OEM ROMs--the file associations and shadows are gone (which is what the .dsm/package.ini files provide).
2)Let me preface by saying that ideally, you shouldn't be touching anything in the OEM/MS kernel. 1st q: If you are using osKitchen, why are you doing this? It can compress with XPR or LZK out-of-box . 2nd q: The nk.exe is modified to use more RAM, not to work with WM 6.5. Kaiser doesn't have a native WM 6.5 nk.exe, so chefs use an older 6.1 nk.exe from a released ROM and patch it to use more memory if they want.
3)I've never deleted that, but this is otherwise correct. (a) You could use DSM editor and remove that one file association yourself. (b) Automatic, as I've never reallocated anything in the kernel and my ROMs cook perfectly.
4)This is correct.
Last one I don't know. I've never done any of that and my ROMs cook/work fine. If I did what OndraSter recommended, I still wouldn't do either (a) or (b) because I don't think it matters to the kitchen script--he would have probably told you to do that as well.

Thanks for responding to the distress signal.
Quetzecotyl said:
Not sure why you are using ROM Editor to do this; it would be so much easier just to use osKitchen or Ervius and dump that ROM, then all you'd have to do is copy/paste. I'm also learning, but I'll answer what I know.
Click to expand...
Click to collapse
I use the ROM editor since I get an error whilst using osKitchen to extract RUU_signed. Infact there is also a warning that pops-up explaining that this utility in osKitchen is awaiting a rewrite and to expect failures.
Quetzecotyl said:
1)I do the same. Almost all chefs delete almost all the .dsm/package.ini files in their kitchen folder before cooking with osKitchen or Ervius's VK. I don't know why it is possible to cook without them, but it's easier then maintaining them and saves a tiny bit of space. It is also why almost all cooked ROMs are not able to be dumped as per OEM ROMs--the file associations and shadows are gone (which is what the .dsm/package.ini files provide).
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
2)Let me preface by saying that ideally, you shouldn't be touching anything in the OEM/MS kernel. 1st q: If you are using osKitchen, why are you doing this? It can compress with XPR or LZK out-of-box .
Click to expand...
Click to collapse
I was getting errors with osKitchen when using the original 6.1 cecompr.dll. It is only when I replaced it with the version in the referenced post that the errors disappeared.
Quetzecotyl said:
2nd q: The nk.exe is modified to use more RAM, not to work with WM 6.5. Kaiser doesn't have a native WM 6.5 nk.exe, so chefs use an older 6.1 nk.exe from a released ROM and patch it to use more memory if they want.
Click to expand...
Click to collapse
Thanks for the clarification .
Quetzecotyl said:
3)I've never deleted that, but this is otherwise correct. (a) You could use DSM editor and remove that one file association yourself. (b) Automatic, as I've never reallocated anything in the kernel and my ROMs cook perfectly.
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
4)This is correct.
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
Last one I don't know. I've never done any of that and my ROMs cook/work fine. If I did what OndraSter recommended, I still wouldn't do either (a) or (b) because I don't think it matters to the kitchen script--he would have probably told you to do that as well.
Click to expand...
Click to collapse
When I dump the 6.1 ROM, wince is part of the XIP. The recent 6.5 releases (28008 and 28205) contain wince as a SYS package in folder WinCENLS_WWE. This is what confuses me - is wince device specific or is it build specific .
If I place the wince from 6.1 ROM in OEMXIPKernel and also select the one in 28205 SYS as an ingredient, then either I am duplicating (and possibly creating a conflict since the file sizes are different) or the kitchen script is smart enough to ignore one of these?
This has also been discussed at http://www.everythingdiamond.info/showthread.php?t=444&page=46 but without any strong conclusion.
Has anyone else experimented with wince?

OK, about WinCE--I wanted to make sure, but skimming through my build logs for a time, I don't think I've ever had that in my SYS. WinCE must be device specific because it is part of the OEMXipKernel, and I've used the same one (ie, OEMXipKernel) maybe 30+ times and can not recall ever seeing a wince.nls in my SYS updates. I've only cooked the 21xxx and 23xxx WM6.5 COM branches, but I can't help but think that the WinCE in your SYS update comes from the device the SYS dumpers used. If I were you, my first go around I would exclude it and use the one from your OEMXip. If for some reason your ROM doesn't boot (it could be so many other things), try replacing your wince.nls with the one from your SYS update (highly doubt this).
BTW, I recommend using Ervius for dumping, as it has never given me any issues.

I think what you say seems logical. I will give it a try and feedback how it went. Thanks once again.

If you dump it via my kitchen and put name Kaiser, it should autogenerate all Sources folder with OEM, original SYS and put NK and XIP on right places actually. (I tried it on newer version of Kaiser's ROM when I was making this dumper so it should work fine.)
And if you restart kitchen, it will load all things automatically (or I hope so, I haven't tried the new UI yet, I'm still at the old one since I actually prefer it...)

I get an error when dumping using your kitchen. I have posted the exception text in your thread.
ps: This is sorted. My RUU_Signed.nbh was not in root of osKitchen dir but a different dir where I place my ROMs.