yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] overhaulengines:
update my new rom

hello Alex, thanks for this tutorial, i went through all the steps and got to part G. final step Flashing, well i chickened out, but only for a moment, i closed the window, but now im ready.

questions

1. is my new rom saved and all i have to do is click on KaiserCustomRUU?

2. when i got to step D Build Rom, after this it says"in the Save Build Rom File window, enter in a name for your Rom and Click Save" question, can i name it as i choose? i ask this because i notice after i named it that in the black window it said to name it RUU_signed.nbh. do i just rename it or can i just leave it with the current name?

3. In the readmefirst text file, it says in the 4th paragraph that "when you need to update your ROM with latest mods you made in OEM, SYS, and ROm folders just click on cook.cmd script to insert all changes, question, where is this cook.cmd? is this (c) cook a rom in kaiser kitchen? i made the first rom per your instructions, now how do i pull it up to see it and then add changes to it. i know major noob questions, lead me to the slaughter. :o

thank you in advance

Lupe
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
It should be saved as the name you saved it as in HTCRT by DarkSimpson in \kaiserkitchen. You can skip straight to 'flash ROM' through the menu. If KaiserCustomRUU is in the \kaiserkitchen directory, you can click on that too...

Any name is fine. Be aware that when flashing, you only want *ONE* ROM in the \kaiserkitchen directory, or the flashing application will get confused and choose the first ROM in alphabetical order in the directory, which could cause some very confusing results. Move or delete old ROMs before flashing.

Readmefirst.txt was created by jcespi2005 when he created the original set of scripts. I've included this text file for additional information, even though it may no longer be current. You are correct in guessing cook.cmd is now (c) cook a ROM.

The only way to see what you've cooked is to flash it. If you have problems with flashing, you can put your phone in bootloader mode by holding down the camera button while pressing reset, allowing you to bypass your brick and flash any other ROM.

No worries, we all had questions the first time around. Glad to see that people continue to be interested in creating their own ROMs!

Hope this helps!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] overhaulengines:
mms

hello Alex, thanks for your last reply, with your help, i have now cook my 5th rom, little by little it coming out the way i like it, fast and stable, again thanks, donation on the way.

question, how do i get mms, i guess that multi media, all i have in options is email and text messages, i looked in the packages but i could not find it or might be overlooking it. is there a cab? thanks again, :):D:):D

to all you noobies, read carefully, check off the steps 1 by 1, read the post carefully, then ask questions,

you can do it.

thanks

Lupe
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Alemaker:
MMS

ArcSoft MMS is one of the packages, under Misc. WM6_by Alex i think.

Have it cooked into my rom and can send mms.

Alemaker
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Glad to hear you're up and running. MMS is in the "KAIS__Other_ArcsoftMMS__4_0_31_28" folder, in the 'Kaiser.Other.Alex' group within BuildOS. As mentioned in another thread, I'll be including Arcsoft MMS 4.2 in the next version.

Thanks for the donation. Hope this helps!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Megavvolt:
Changing registry?

I'd like to change some stuff in the registry (Owner Information, etc.) so that the cooked ROM would have all these changes incorporated. How do I do that?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] JohanDC:
Hi Alex

Love your kitchen, I have been using it for some time now.

I still have a couple of questions, and I was wondering if you could help me out here?

btw, I have been searching xda-developers for days now without any luck. :(

Can you give me soms pointers on how to build an hybrid ROM? Let's say I want to use a Polaris ROM on my Kaiser, I know that most HW is the same, except for the FM radio & HW keyboard, so how will I be able to add the keyboard support for example?

Also when I find a newer WM OS/build, how would I be able to incorporate that into a base Kaiser ROM?

Thanks in advance if you could give me some advice! :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] odyseus:
ArcsoftMMS v 4.2.8.1

Hi All

If anyone wants a package for ArcsoftMMS v 4.2.8.1 then I have done one and it can be downloaded from here..

http://rapidshare.com/files/88611443/ArcsoftMMS4_2_8_1.zip

Cheers

Ody
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] odyseus:
Other packages

Hi again,

I have uploaded some more packages to my rapidshare folder..

http://rapidshare.com/users/B96KLZ password piggy1

Hopefully, they might be usefull..

Cheers

Ody :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] avengerpenguin:
Dont suppose anyone has a 6.1 base yet to work with? I have tried to extract schaps 6.1 but I get and error when trying to cook it in both versions of buildOS.

The error is a string parameter error if I recall correctly
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] JohanDC:
Tried this as well, but re-cooking a cooked ROM is most of the time not possible.

schaps did something to his ROM to prevent us noobs from reusing it, when you extract it, the SYS folder is not repopulated, there is only a folder called BETA, create your own ROM

So I am pretty sure he does not want us to reuse his work. ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] avengerpenguin:
This thought did cross my mind, if that is the case then fair enough and we should respect his wishes.

So the hunt for a 6.1 base continues, Dutty's will not work either I dont think as he removes files to gain storage
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] overhaulengines:
cab creator

hello Alex, been loving my custom roms, now im loving game rom V5, :)question. in your kitchen you have a way to convert cabs to packages, is there a way to make a cab from a package? i need a cab creator. i searched for cab makers and cab creators, but no luck, :confused:thanks again.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] odyseus:
More packages uploaded

I have added Home Customiser and Vista Cube packages....

Cheers

Ody
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laubscherc:
Hmmm....

I have been sitting in the sideline way too long. I have flashed my Universal so many times I have lost count. Now after flashing my Tytn II a cou;le of times, and with all the hype surround9ing WM6.1, I thought maybe I should start building my own ROM's. So I will be asking a lot of questions!

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] overhaulengines:
New Kitchen out

hello Alex, been waiting for this new kitchen, thanks a bunch, i will let you know how it goes, also using your v5 game rom, i love it, its fast, battery life is AWESOME, usually by 5PM i'm down to 50%, right now i'm at 74%. very nice.:D

great your goodies here

http://xdaforums.com/showthread.php?t=349354

good luck new chefs;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] akosiryan:
InitRegistry FAILED in file ".\Registry\2566cd4b-37b8-4103-af02-81b7013b3505.rgu" within a few lines of line 4.

ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\2566cd4b-37b8-4103-af02-81b7013b3505.rgu"

wmain: (RGUComp) !ERROR failed building DEFAULT hives

Creating registry Error...

i get this error while cooking... what do i do?.. im new at this.. so im not sure how everything goes... the wiki doesnt anything about this...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] akosiryan:
i solved the problem.. it seems that i get an error when i include my home made package for google maps.. my bad
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] THEQUARTZGUY:
Awesome Kaiser Kitchen, Alex!!!

WOW ALEX, WHAT A GREAT JOB! I HAVE CREATED DOZENS OF NICE KAISER ROMS NOW, AND I AM ALMOST GOOD ENOUGH TO START POSTING THEM ON XDA'S SITE FOR OTHERS TO SHARE! GREAT JOB TO ALEX AND ALL CONTRIUTORS!!!:D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pandaedward:
Hi Alex,

I have cooked my own ROM by following your tutorial instruction, base ROM is HTC1.81, radio 1.27.12.17.

I have a problem on the Connection Setup wizard, the operator list does not have New Zealand configuration. Vodafone NZ is my service provider.

Is there a way that I can add my own operator configuration before I cook the ROM so that it will have New Zealand operators?

All other things in my own cooked ROM are working just fine.

Thx Alex
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] akosiryan:
i finally gave up on cooking...

i did trial and error for my tilt rom but i couldnt figure out why the camera was missing. i tried extracting the tilt rom so that the camera would be installed but when i run it, it doesnt capture images. it only displays a black screen with the camera options. align screen was also messed up. thats all i could think of at the top of my head.. but yea.. i gave up cooking. so much for my perfect rom :(
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
The camera is in an OEM package. Sorry to hear you've given up so easily, many other people are very satisfied...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
I believe someone has posted a South East Asian operators (including NZ), so you can search for that. Alternatively, you can create a OEM package containing your operator information.

Hope this helps!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] cushcalc:
2-26-08 v5.1 OEM packages, cooking, questions . . .

Two comments/notes (and wondering if anyone else is experiencing these phenomenae):

1) The Wiki instructions state:

Uncompress kaiserkitchen_01-20-08.rar to \kaiserkitchen.

It is highly recommended you extract this and all additional applications to folders on your C: drive, e.g., c:\kaiserkitchen. It is not necessary for this tutorial, however it will be necessary to use Ervius Package Creator in the OEM Package Tutorial.

You'll notice that there is a file called !!!readmefirst!!!.txt within the uncompressed files. This file contains additional information on how to cook and I suggest reading it after you complete this tutorial as it contains valuable information about cooking, but some steps will conflict with the steps found here.

You should have \kaiserkitchen and

two subfolders, ?BaseROM and Tools.

NB: I have never, in multiple fresh installations of all this stuff, had subfolder 'BaseROM' automatically created. I

always

have had to just create it myself, hoping that is the right thing to do, and left it empty; and cooking has proceeded O.K.

2) Using the 2-26-08 "Alex.v5.1.OEM.Packages.fixed.again" parts 1,2, and 3, and all the other ingredients, and installing fresh into empty C:\kaiserkitchen - cooking process crashes with multiple errors, among them: "buildos+package_tools-2.7.exe has encountered a problem and needs to close."

I will wipe everything out, reinstall, and try again, but just wanted to put up an early post of a possible problem in the packages. Hope I'm wrong and it's just me . . .

Thank you again _Alex_ for the brilliant work that you've done - I can hardly imagine how much time and effort you've put into this, and it has kept me (and countless others I'm pretty sure) very excited about this great device, which, like a great person, has tremendous attributes and potential, and yet, a few flaws, which we must learn to forgive and work around.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Having no BaseROM folder is fine, if you never extract a ROM and just use the ROM folders I've provided.

As for your folder layout, regardless of how the RAR files extract it's contents, try to make your folders look exactly as the pictures in the wiki, e.g.,

The folders found in packages will be different than the ones below because this is a screenshot from v3 OEM packages or earlier.

BTW, I recommend for all of those who have already setup their 1.62 kitchens and have them working to avoid updating to the new OEM packages, as there is only one change...

Hope this helps!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] akosiryan:
ok.. so now, im going back to cooking cuz i think i might get lucky this time... i tried extracting an OEM att rom (the new one...) but when i build, at some point i get this error....

file yet present: C:\Documents and Settings\Ryan\Desktop\rom cook\newkaiserkitchen\SYS\NetCF -> cgacutil.exe! Skipped!
file yet present: C:\Documents and Settings\Ryan\Desktop\rom cook\newkaiserkitchen\SYS\NetCF -> mscoree.dll! Skipped!
file yet present: C:\Documents and Settings\Ryan\Desktop\rom cook\newkaiserkitchen\OEM\OEMDrivers -> HTCCamera1.dll! Skipped!

i keep on getting that error for an oem att rom.. and when i look at the folders, i can find the skipped files.. idk why the OS builder skips it....

edit: when i flashed the alex's rom, without adding packages, i still somehow have a program called batti (and another program.. i forgot the name..) which i found annoying..... thats why i wanted to extract my own

editII: before, when i first tried flashing it.. (and ignored the skipped camera) the camera app didnt work...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Learn to walk before you run. Please follow the tutorial step by step. :D

There are many things wrong with what you're posting.

You should have uncompressed your kitchen to c:\kaiserkitchen, not your desktop. I'm surprised you're not running into path character limitations just yet.

Secondly, a shipped ROM isn't stripped. Therefore, putting more applications and registry settings onto it may have mixed results and conflict with existing applications that have not been removed.

Skipped files just means there are duplicates in the OEM package and the base ROM. This isn't a problem in itself.

Finally, as mentioned in many other posts, move the packages you don't want out of the packages directory. This is to prevent applications you do not want from appearing.

In summary:

Start from scratch.

Follow instructions and don't deviate from the instructions until you really know what you're doing.

If you don't want something installed, move it out of the packages directory.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] akosiryan:
well.. i kinda memorized the steps already.. but yea.. now.. i get it.. i posted here last night before i flashed my phone... so yea.., everything

seems to be fine now.. im doing trial and error again but not as frustrating as before... i think ill be flashing 2-3 more times to get it right but yea.. i already figured out the programs that i want.. :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pdagenius:
Reconstructing Polaris ROM

I have successfully reconstructed a Polaris ROM using the Kaiser ROM Kitchen. This was suggested in the Polaris forum. Thank you for the good tutorial and the excellent tools and associated files. :)

My queries relates to the OEM packages which you helpfully provide.

Background....When reconstructing the ROM I did not put any of the OEM Package files that you list as ingredients from your V5 Cooking Kits into the Packages folder. Therefore the Ervius Package Tools main window was blank. However clicking on Show Editor revealed all the dumped files that would be reconstructed. Anyway the build completed as it should which was great.

My question is if I had loaded your OEM packages into the Packages folder am I correct in thinking that many of these are relevant to the Polaris and therefore it will allow me to customise / cook the ROM as it is reconstructed. Presumably any of the packages which are already present in the dumped files will show up in the Ervius Package window as ticked?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
You will find OEM folders after extracting a ROM. Packages aren't created when extracting a ROM. Packages are created by people after they've extracted a ROM :D

Hope this helps!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] The.Grunt:
ahh

im tryna learn how to cook a rom and wen i get to the step where load a rom on the ervius package tool i click kaiserkitchen and then it says im missing OS.NB or sumthin im new to this so yea lol help plz
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Follow the advice in this post or watch Doctajay's excellent videos, specifically the one for preparing your kitchen, which is a simplified version of what you need to do in these tutorials.

Hope this helps!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] The.Grunt:
hey alex i jus wanted to say thanks man i learned to cook in 2 days (im new so i got stuck at a couple things as simple as they were) the tutorial is perfect. jus one qustion tho were else can i get packages to include in my rom?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
The FAQ at the end of the tutorial has your answer.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] cushcalc:
I'm about to pull my hair out!

My folders look

exactly

like the above. I have successfully cooked about 2 dozen ROM variations using your kitchen, in the past 2 months, but since downloading the newest files in your cooking kits:

Alex.v5.ATT.1.82.parts1-2-3, Alex.v5.1.OEM.Packages.fixed.again.parts1&2, 01-20-2008 KaiserKitchen Updater, I now get the error shown below every time I attempt to cook.

I have deleted the entire folder C:\kaiserkitchen and reinstalled the whole shebang, there are no temp files, there is no extra .nbh file lurking about, I am running Windows XP Home SP2 (NOT Vista) on Dell Inspiron 8600 laptop, I have also tried this on my desktop running Windows XP Pro, with same result.

There's got to be something obvious that I'm missing, but it certainly eludes me. I have tried the suggested fixes in this thread, but they seem to be directed towards Vista users, and they didn't help me.

Would appreciate your help. Thanks.

Edit: Further Info: It's buildos+package_tools-2.7.exe that won't fire up, and causes the Initialization Error - I have tried executing this from the root of C:\ and from C:\kaiserkitchen, with and without all the folders installed. I have downloaded and reinstalled this several times, on three different computers, and kept getting this error. So I tried executing BuildOS.exe, and it says it needs .net framework! I don't know I can NOT have .net framework on any of 3 computers - I have never explicitly installed it, things just worked - but anyway, I installed the latest .net CF 3.5, and now buildos+package_tools-2.7.exe starts up without error. [this post was up for 3 days, and no one responded, so I wonder if no one knew the reason or no one noticed?)

Anyway, problem solved.

Nothing to see here . . . go on about your business . . .
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] semitral:
Packages...

Alex,

1st excellent tutorial on cooking and your packages are amazing! Fine Work!

I have been using your base ROM ATT 1.62 and v5 packages but cannot find the packages for your most recent ROM update for the nicely colored

- comm manager

- quick list

- contact manager

- and action screen.

I did try searching but could not find these versions in the same form as your ROM. I did note many other versions in you packages file but not these most recent versions which were in your most recent ROM. Thanks in advance.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ecltech:
I can answer for the Comm Manager and the same probably holds true for the other packages. These are v5.2 of his OEM packages, which to my knowledge hasn't been released as yet.

For the Comm Manager, try this link: http://xdaforums.com/showthread.php?t=376051. It's a cab file but convert it to an OEM and cook into your ROM. I've done it and it works great.

Hope that helps.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] semitral:
Ok thanks for the update. Alex, are you planning on releasing v5.2? Now that Ive started cooking I cant get enough! Thanks.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Sorry, installing the latest .NET versions and updates was mentioned a couple of times in the cooking kit thread as a solution to problems with XP installs. Meant to reference the other article (as I usually do) but it must of slipped my mind.

Glad to hear you're back up and running :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kjb86:
Cooking

Hello Alex,

I have followed your steps 1 by 1 and I've also looked into the video's provided as well.

All is well, no error's or anything, but I noticed a couple of things

1) No buttons are mapped on the device

2) I'm missing some important info out of my system (e.g.: Device Information)

3) The Menu *stickies* on the start menu don't appear when flashed as well.

Is there something that is missing during my cooking process?

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Hey _Alex_,

I'm looking for some info/advice on cooking here. I have gone through all the tutorials, but I don't really

understand

how everything works even though I can do it. I would like a little bit more explanation.

I'll start with the premise that I want to take a shipped ROM and strip out all the OEM bloat:

- So, when I "e"xtract a ROM into the \ROM \SYS and \OEM directories, what actually is in each of these and what can be messed with?

It looks to me like you don't really want to touch what is in \ROM under any circumstances (unless you are modifying os.nib for pagepool).

- The \SYS appears to be everything that makes up the basic OS...although I have to think that there are some tweaks in here between carriers as well (as opposed to just different OS builds)?

- Then, what is in \OEM would appear to be all the additional software that gets installed. Is everything in \OEM what runs during the "customization" phase? Meaning, if I interrupt the "customization in 3 seconds" prompt, would everything in my OEM directory not get installed, or is this a different process?

- Should it be possible to extract a ROM, and NOT add any packages (uncheck everything) and then just cook it again to get the exact same ROM that you extracted? In other words, when you extract a ROM, do you loose anything from it that must be added back or can you extract and then recook to get the same thing?

- If you can...then by that rationale can you strip things out of the \SYS and \OEM directories to remove unneeded apps before the recook?

My trials so far have not been too successful, so I am curious as to what is being lost when a ROM is extracted that doesn't get cooked back in.

- Also, how does this process differ with an already cooked ROM? Say i liked someone's cooked ROM, but I wanted to update some program they cooked in with a newer version? What would be the process to extract their ROM, update it, and re-cook it? Would i need access to all their original packages or is the extracted ROM enough?

And finally, some slightly more specific questions:

- All my radio files are .nbh format, but the ROM Builder app is looking for .nb files. Are these the same? I have had several issues that when I cook in a radio file, the flashing process hangs (usually at 22%). If I don't choose a radio file then the image flashes without an issue (and I then can flash the radio separately).

- Is the pagepool changer that comes with the kitchen the true pagepool changer? It appears to be searching for and changing an offset, much like what Dutty mentions in his tutorial, but I heard some people mention a pagepool technique that doesn't really change the pagepool. It did look like the pagepool changer in the kitchen accurately changes the available RAM, so it appears to be a true one. If so however, I am wondering what the big fuss was about in Dutty's tutorial, as it looks like this program does it all automatically.

Thanks for any guidance.