Database Info

How to Cook a Rom

Okay after reading through a few threads on XDA I thought I might take a stab at writing a Simple tutorial of the knowledge I know of cooking a rom
Step 1: Download a kitchen of your choice I think the Kitchens from Matt are the best to use only my recommendion
Step 2: Download the OEM packages you'll need..Leave them in a different folder then the Kitchen right now..
Step 3: Make a OEM folder in the kitchen folder if theres not one already and place it in the kitchen folder
Step 4: Take the OEM packages from the desktop and drag the ones needed for your rom
Step 5: Click Build OS check the files your going to have in your ROM to be built..if it errors look at where it errored and check the OEM package to see if it meets the standered below
Step 6: Now add any thing you need to edit in the dump or replace files (EX: Welcome Screen, themes, initflashfiles.dat file ect)
Step 7: Now run the CreateROM.bat once finished you'll have a new file in the temp folder
Step 8: In the kitchen there will be a nb2nbf_wizard.exe if not search the forums..open that model ID will say Wizard.. change the language to WWE then on the bottom you'll see empty fields..those are self explanatory pick OS for the ROM then locate the file in the TEMP folder of the Kitchen
Step 9: Now once its finished translating where ever the output direction was it will be your file to flash, now move that to the RUU and flash and say Hello to your own Cooked rom
PS Steps will varies from Kitchen to kitchen but this covers the jist of basic ones
nows for the complex parts how to make an OEM package...Information from double_ofour
Step 1: Vist http://www.famkruithof.net/uuid/uuidgen the Create UUIDs of another type should be set to Version 4: random then a code like this "6bfb7458-6a83-450a-9da5-b5feabba8335" will be made
Step 2: make the code the name of the 2 text files you have in the OEM package folder, Change one Text file extension to RGU and the other DSM
Step 3: now the RGU is where the Reg hacks are the first line MUST be REGEDIT4 then you list your Reg hacks.. in the formate like this
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\MASD]
"TaskManager"="1_5_29968_1"
Step 4: Leave a space after the last reg hack and save as UNICODE
Step 5: add any files to the OEM package Folder they will be put in the /Windows directory
to make an extension into the programs folder you should edit the initflashfiles.dat
How to edit the initflashfiles- Should be done between useing the Build OS and Create Rom
Step 1: open the file with note pad
Step 2: remove any lines that aren't needed..sometimes you'll see likes to create a folder for a shortcut when your not using the program
Step 3: add a line to create a shortcut for a program from your own OEM package...Most packages here already do it for you
sigh I'm tired of typing but theres a basic out line of what cooking a rom consists of..feel free to add anything I might of missed
Just thought I'd help out anyone looking to cook a rom and needs a little guide
Please don't ask for help here..I'm not text support..I think there shoul dbe one thread for all cooking questions..you guys could even use the thread when i asked for help
PS again thanks to all the people here at XDA that made cooking simple easy even ifs making a OEM pack or a fix or even a kitchen thank you all

thanks ANTC!!!

thanks dude! can we have pictures too? (what the heck - had to ask )

thanks this is EXACTLY what I was looking for

mattk_r said:
thanks dude! can we have pictures too? (what the heck - had to ask )
Click to expand...
Click to collapse
sigh..sure once i can release my full touch rom using your kitchen

so no deal matt...lol not like you need a tut how to make a rom...maybe you could help with the cam issue to for my rom

everytime I click buildos.exe I get an error. No matter what folder I try it in, it just wont work.

How do I dump an official rom?

maybe some one can help you with the dump question its hard for me to put into words since core does it by it self
and th build os problem is something to take up with the maker of ur kitchen try doing a windows update you may need sp2 or net framework

I suggest making this thread sticky, removing all unnecessary posts, including this one and transform it into an How To thread. Where everybody can post tutorials on different aspects of rom cooking.
dferreira said:
How do I dump an official rom?
Click to expand...
Click to collapse
Same you do with an unofficial one lol The difference is that you won't find any missing files and that means less work for you.

anichillus said:
I suggest making this thread sticky, removing all unnecessary posts, including this one and transform it into an How To thread. Where everybody can post tutorials on different aspects of rom cooking.
Same you do with an unofficial one lol The difference is that you won't find any missing files and that means less work for you.
Click to expand...
Click to collapse
It won't dump using your kitchen... Try the last oficial RUU Prodigy of WM5 and you'll see that it seems to be protected, since it can't extract the 8004000 :s

anichillus said:
I suggest making this thread sticky, removing all unnecessary posts, including this one and transform it into an How To thread. Where everybody can post tutorials on different aspects of rom cooking.
Same you do with an unofficial one lol The difference is that you won't find any missing files and that means less work for you.
Click to expand...
Click to collapse
Coming from you thats a huge compliment..

what can i do if i want to add programs like TNT, i have few apps compared to mfrazz's build or TNT and now if i add 1 more program in my kitchen it crashes the buildimgfs.exe, anything i can do to add more? i am using faria's kitchen tool

nycelitemaster said:
what can i do if i want to add programs like TNT, i have few apps compared to mfrazz's build or TNT and now if i add 1 more program in my kitchen it crashes the buildimgfs.exe, anything i can do to add more? i am using faria's kitchen tool
Click to expand...
Click to collapse
Try using Core kitchen that should do the trick

hopefully as a newbie I can make my own rom with this
and please do help me if i encounter any problems
thanks in advance

Personally, I would suggest doing a topic like this in the Wiki. Then have a topic here that is stickied to point to the Wiki entry.
Here's a page I started for the Faria Kitchen last May. http://wiki.xda-developers.com/index.php?pagename=FPRK_Cooking_Instructions
You could take what ANTC posted and merge with the info I provided and come up with a nice generic page for cooking )most of the kitchens work the same since they all use basically the same set of tools).
Here's a page on making OEM packages that da_jojo added on:
http://wiki.xda-developers.com/index.php?pagename=FPRK_Creating_ROM_Packages
BTW: If you do the instructions in the Wiki then any / all of us can help maintain it (where posts here can only be maintained by the original poster).

i think this is good for those who already know how to cook, but too brief for beginners who know little about cooking a rom.

My problem when building the rom is when it is finished this error comes up
"c:\DocumentsandSetting\M541378\ApplicationData\hIqInc\PPC-BuildOS\9.05.3.0Temp\ROM\XIP"
so in my ROM folder there is no XIP, I create the folder, and I re-create, it and then the XIP folder erases. I have no idea why this happens? Can anyone please help....

Updating rom image USING FARSTONE DRIVE CLONE
Hi all i'm new at the forum, i would like to know if i can create an image with farstone drive clone of all the programs i have and configurations and then upload it to the phone?? I would like that even if i have to perform a hard-reset on the device it would still have all the progs and configurations created on the image uploaded.
Any suggestions are welcomed!!!!!

hi, I am a newbbiess... i am totally not understand what do u mean by kitchen... but i am intrested in generate a ROM myself.. please advice..

ROM Kitchen registry problem

I have been currently making another ROM kitchen to use but I have gotten stuck. When trying to use BuildOS create the new dump, I always get an error creating registry with a dialog that says "The system cannot find the file specified."
I dumped the ROM with Tadzio's revised IMGFS tools and used PackageTool to create the OEM and SYS folders.
Where are the default.hv and user.hv files located?
Any suggestions?

ND4SPD said:
I have been currently making another ROM kitchen to use but I have gotten stuck. When trying to use BuildOS create the new dump, I always get an error creating registry with a dialog that says "The system cannot find the file specified."
Click to expand...
Click to collapse
Does the error say anything else? Usually this indicates an error in one of your packages (possibly a syntax error in a .rgu file). Try disabling some packages in the OEM folder (either uncheck them in buildos.exe or move them out of the OEM folder to some holding folder) and see if it will run to completion. If it does, then move them back one at a time to find the offending package. Then go look at the .rgu file.
Also verify the files are saved in Unicode (.rgu, initflashfiles.txt) as that can cause issues too.

OK. I tried to fix this by unchecking all of the OEM packages. I still got the error. It shows the same error. On the status bar it says, "Error, last status: "Creating Registry..."". I then get the dialog mentioned before. When I do the same thing through Anichillus's kitchen, it works perfectly with the same OEM and SYS folders.
Is there something wrong that I'm doing in the dump procedure that could affect this?
Thanks

ND4SPD said:
OK. I tried to fix this by unchecking all of the OEM packages. I still got the error. It shows the same error. On the status bar it says, "Error, last status: "Creating Registry..."". I then get the dialog mentioned before. When I do the same thing through Anichillus's kitchen, it works perfectly with the same OEM and SYS folders.
Click to expand...
Click to collapse
Ahhh... I had a similar issue with the Faria Kitchen rom and trying to move it to other kitchens. There seems to be slight variations in buildos.exe. Never figured out exactly what it was... You can just take the buildos.exe from Core Kitchen and move it to the one you are using now (that gets the errors) and it will work. I think it has to do with where it expects to find certain files, but from what I could tell they all work exactly the same.

Just tried that too. Got the same error. I don't remember, but I think I had already gotten the BuildOS from the Core Kitchen. Sorry, but do you know of any other versions that work? Or if it isn't to much trouble, do you think you could attach the version you are using?
Could you tell me if this process is correct or if there is something in this that is causing the problem?
1. Split the Rom with typho5
2. Split the nb with ImgfsFromNb or prepare_imgfs
3. Dump from bin using ImgfsToDump or viewimgfs
4. Use PKGTool and make packages
5. After adding/removing packages, use BuildOS to recreate ROM
6. use BuildImgfs to recreate the bin file
7. use make_imgfs to recreate OS file
Thanks for your time

ND4SPD said:
Just tried that too. Got the same error. I don't remember, but I think I had already gotten the BuildOS from the Core Kitchen. Sorry, but do you know of any other versions that work? Or if it isn't to much trouble, do you think you could attach the version you are using?
Click to expand...
Click to collapse
I use the Core Kitchen and the scripts in the Extract and Panel folders there to break apart and build roms (its basically all setup and scripted that way).
Try extracting and rebuilding with Core Kitchen and see if that works (I know you said the build works with Core Kitchen). Is there a reason for this other kitchen tools you are trying to use (something newer/better)? Just curious.
While most of the kitchen tools are basically the same, there are some slight variations, and aparently something with this rom or kitchen doesn't quite mesh up...

OK. I will try that. Thank you for the suggestions. If it doesn't work, I'll let you know
Try extracting and rebuilding with Core Kitchen and see if that works (I know you said the build works with Core Kitchen). Is there a reason for this other kitchen tools you are trying to use (something newer/better)? Just curious.
Click to expand...
Click to collapse
I'm not too sure what you mean by this question, but if you are asking why I'm making another kitchen, it is so that cookers can build their own roms from a GUI without having to worry about putting things in certain folders.
Here is a screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The only thing not working right now is the rebuilding of the OS.

Nice and well done! Interested to see this in action...
I will say that while I like most everything about Core Kitchen, one thing I don't care for is the scripts all assume everything is on your SystemFolder drive (C:\) and assume top level folder names. I'm going to look at modifying this so its generic (like most other kitchens) just haven't had the time to do it yet.
So I guess what I'm saying is, if you build this project, don't hardcode the location of the kitchen

BuildOS needs some files in same folder with it in order to work if i remember corectly. Maybe you missed that.
I wonder though...Are you sure you completely understand the big scheme ?
I mean ... you are trying to build a kitchen not knowing all the steps necessary to do that. Maybe you should collaborate with someone. I don't want to have a wave of bricked wizards around here. Again...your choice...and...btw i wanted to do that for some time also so you would save me the work.
The Wizard ROM doesn't use the SPLIT option. If you use typhoon decode.
Don't worry mfrazzz , i will redo my kitchen. Today was my last exam, and as i promised i will get on with it

Sorry it took me some time to reply, I was busy with something else
@anichillus:
i guess it would be a VERY good idea to collaborate on this. I have been trying to build a kitchen based on the way yours and Molski's works. Or, I could give you the source code if you want. It's in VB, but I haven't put a single comment in the whole thing.
So I guess what I'm saying is, if you build this project, don't hardcode the location of the kitchen
Click to expand...
Click to collapse
Oops! I probably should change that then. Right now, it's all hardcoded to a folder "C:\Autosculpt"
Btw I named it Autosculpt from the customization of a car's parts in the game Need For Speed Carbon. Just thought you would like to know.
Also, with the progress bars, don't take any notice of them, they are time based and automatically go to 100% when the certain task is done.
I have attached the current build of my program and kitchen. See what problems you can find. I have been doing this from a computer on which typho5 doesn't work so I have only tested it twice on a different computer.
Also, don't worry about the splash screen tool makers. They don't do anything just yet as I haven't added code for them.
Make sure that the directory of the Kitchen is C:\Autosculpt!
Once again, please tell me if you want the source code. If you want to use it, you will need Microsoft Visual Basic 2005 Express Edition which you can get as a free download from microsoft. If you can turn this into something successful, you don't need to give me credit for the original. I just did because I was bored and I had to anyways learn a few programming languages so for a class I will be taking.

good work,
im interested in sorce code if u dont mind.

Please wait till about 12:30. I have summer school and can't upload it now

Here is the link:
ftp://xdaupload:[email protected]/Upload/testapp.zip
Place the folder testapp projects folder in the Visual Studio 2005 folder in My Documents. Then you can just open up the project file from Microsoft Visual Basic Express Edition.
Be warned: I haven't placed a single comment in the program. If you want I can send one with the comments later today. I can't do it immediately as I have to go and practice tennis with my friend.
Also, as mentioned before, I haven't put the code to activate the splash tools yet. I asked the-equinoxe about them yesterday and will be implementing them later today.

Now have gotten a little further with this. I still haven't made any effort to fix the registry problem.
Changes to kitchen:
Added Splash editing support
Added G4 flashing support (not that this will do any good until I fix the registry problem)
Note: progress bar has not been binded to any running of an application at this time. Instead, you will get a dialog box telling you when a certain process is done.
If anyone has looked at the kitchen, do you think you can figure out what is going wrong with the registry.
Updated source code is posted on ftp server at the same link
Here is the link to the updated kitchen: ftp://xdaupload:[email protected]\Upload\Autosculpt.rar

make "temp" folder in kitchen folder.....if i understood your prob correctly....

also having problems
hi,
i'm trying to cook a rom using buildOS i get this error message:
'error building defaul.hv and user.hv'
anyone got a clue how to fix this??

ND4SPD said:
I have been currently making another ROM kitchen to use but I have gotten stuck... I always get an error creating registry with a dialog that says "The system cannot find the file specified."
Click to expand...
Click to collapse
In my case it was lacking the rgucomp.exe utility in the tools folder.

Learning to cook. Need a little help

I'm using alex's kitchen and am trying to create a cooked wm6.1 rom from the CE OS 5.2.19170 (BUILD 19170.1.0.0).
I've extracted the rom loads of times and can create a flashable RUU_signed.nbh with additional apps from packages (and some packages i made myself) but if i try to add the new polaris camera or anything that the rom may have a previous version of it errors out and can't create the default hives.
It says for a lot of the added packages they do not contain rgu's.
Anyone fancy trying to mentor me a bit?

read the wiki on how to make oem packages bro im in the midst of making my own custom rom right now based off of dcs1.1

Cheers for the reply.
I've done that and made some working packages but it seems thats not the problem. i think i need to remove all the older stuff from oemapps first but i don't know how to do that and can't find any pointers.
I know i could start deleting stuff but thats probably not wise.

ive been lerning myself the past 3 days non stop just testing n testing new stuff seeing what goes well, trying to take pkgs from roms and merge to other etc takes some time but ull get it if u keep at it, i really recommend the packages creator 5.4 util for making ur pkgs

i just wish i cood find the pkgs for dutties beautiful red phone dialer and call history etc. i tried removing it but its a bit too advanced for me atm

I've been using the package creator in the kitchen (ervius' one).
I'm on nightshifts at work and i think the sleep deprivation is making me miss the obvious.
I'll stick at it for a bit though and then have a proper go when i get a day off.
I'll have a bash with the rom your using as its got the camera in already but i'd still like to know how to do it myself.
Now where'd i put that cup of coffee?

oh and i find with the pkg tool i have to delete the rgu files to avoid the hv registry errors in buildos hope that helps

It says they are missing for most of them anyway.

Please watch this.

to get my pkgs to work i found that i had to uncheck prefix files and leave all others checked, then after creating the pkgs i delete the rgu files

_Alex_ said:
Please watch this.
Click to expand...
Click to collapse
Now that's funny.
Now i know it's the wrong thread and all but i don't want to start a new one just to thank you for your kitchen and tutorials. So ta very much.

xzon said:
to get my pkgs to work i found that i had to uncheck prefix files and leave all others checked, then after creating the pkgs i delete the rgu files
Click to expand...
Click to collapse
Cheers for the advice xzon.
I'm gonna call it a day for now but will definitely check out what you've said.

_Alex_ said:
Please watch this.
Click to expand...
Click to collapse
Thanks Alex

Confused on some things when cooking!!

I've started trying my hand at cooking some of my own ROMs over the past couple of days and have gotten confused on some stuff. I've been following the both the Wiki's and the threads on cooking but none of them seem to point it out so here goes.
1) I'm trying to use a base ROM such as this one or this one and have been successful in both dumping them and cooking them using Alex's latest revision of KaiserKitchen and his apps. When I am including the os.nbh file during the cooking process, should it be the one that comes up in the main KaiserKitchen folder or the one that is located in the BASEROM folder? Is either of those files just the OS part of the ROM without all the applications and such?
2) After cooking and successfully flashing either of the two before mentioned ROMs I will always get the auto-installer which occurs on a default ROM. The problem is is that none of the defined packages that I've chosen in the cooking process will be installed when the ROM is flashed. Why is this? Is there something that I should be doing that I'm not doing now that will allow this?
I would greatly appreciate any help in this as I want to become an avid chef but want to learn the ropes first. I've been toying around with it and wanted to get a decent collection of base ROMs and understand them before I start customizing them and such. Again, any help would be thoroughly appreciative and love what you guys are doing here.

HEdwards2008 said:
I've started trying my hand at cooking some of my own ROMs over the past couple of days and have gotten confused on some stuff. I've been following the both the Wiki's and the threads on cooking but none of them seem to point it out so here goes.
1) I'm trying to use a base ROM such as this one or this one and have been successful in both dumping them and cooking them using Alex's latest revision of KaiserKitchen and his apps. When I am including the os.nbh file during the cooking process, should it be the one that comes up in the main KaiserKitchen folder or the one that is located in the BASEROM folder? Is either of those files just the OS part of the ROM without all the applications and such?
2) After cooking and successfully flashing either of the two before mentioned ROMs I will always get the auto-installer which occurs on a default ROM. The problem is is that none of the defined packages that I've chosen in the cooking process will be installed when the ROM is flashed. Why is this? Is there something that I should be doing that I'm not doing now that will allow this?
I would greatly appreciate any help in this as I want to become an avid chef but want to learn the ropes first. I've been toying around with it and wanted to get a decent collection of base ROMs and understand them before I start customizing them and such. Again, any help would be thoroughly appreciative and love what you guys are doing here.
Click to expand...
Click to collapse
os.nb should be in base rom with RUU_signed.nbh(once youve extracted) The File that is generated during ervius package tools is OS-new.nb-this is your new os. Kaiser Wiki has all info.

yardie.spike said:
os.nb should be in base rom with RUU_signed.nbh(once youve extracted) The File that is generated during ervius package tools is OS-new.nb-this is your new os. Kaiser Wiki has all info.
Click to expand...
Click to collapse
I've been searching the Wiki like crazy and I guess I am just confused on it. So OS-new.nb is the OS ROM with all of the packages, Which one would be just the OS itself? The os.nb file in the BASEROM folder?

HEdwards2008 said:
I've been searching the Wiki like crazy and I guess I am just confused on it. So OS-new.nb is the OS ROM with all of the packages, Which one would be just the OS itself? The os.nb file in the BASEROM folder?
Click to expand...
Click to collapse
Yeah, but dont worry about os.nb in base rom folder, unless you dont want to mod the rom and just add your fave radio/splash/spl. If thats all you want to do then recomplile using htcrt.exe in tools folder. OS .nb is what is extracted into OEM SYS and ROM folders in the kaiserkitchen. To add Packages put a folder called Packages in your kaiserkitchen and put your OEM Packages in it, then run KAISERKITCHEN.CMD chose option c then b. When Ervius build os +package tool opens,click the right tab and add rom(Add your kaiserkitchen folder,but make sure its on your desktop). You will then get a list of packages in the premade folder, just tick the ones you want to add to your rom. Once happy click build rom. Once done exit and KAISERKITCHEN.CMD should crack on by itself....then bring up a couple more apps(Rom Tool and Pagepool)just do what they say . every time you exit these apps KAISERKITCHEN.CMD will take you to the next step.

yardie.spike said:
Yeah, but dont worry about os.nb in base rom folder, unless you dont want to mod the rom and just add your fave radio/splash/spl. If thats all you want to do then recomplile using htcrt.exe in tools folder.
Click to expand...
Click to collapse
speaking of the htc rom tool, does anyone have a mirror for the latest version (1.1.1). it's not working on his site, and I 'm really interested in the command line support

mbarvian said:
speaking of the htc rom tool, does anyone have a mirror for the latest version (1.1.1). it's not working on his site, and I 'm really interested in the command line support
Click to expand...
Click to collapse
Theres a new ROM tool????Anyone tried??
NEW IS GOOD!!!

Thank you so much for the clarification. I've also been trying to find a decent kitchen setup and the one made by Alex is the best one I've encountered so far but haven't really steered too far from his build. I have to agree that a new version of the HTC Rom Tool would be cool.

HEdwards2008 said:
Thank you so much for the clarification. I've also been trying to find a decent kitchen setup and the one made by Alex is the best one I've encountered so far but haven't really steered too far from his build.
Click to expand...
Click to collapse
I just put up a Kaiser 20270 kitchen from PPCKitchen.org and AstainHellbring. Try it, let me know what you think. Feedback thread is here.

yardie.spike said:
Yeah, but dont worry about os.nb in base rom folder, unless you dont want to mod the rom and just add your fave radio/splash/spl. If thats all you want to do then recomplile using htcrt.exe in tools folder. OS .nb is what is extracted into OEM SYS and ROM folders in the kaiserkitchen. To add Packages put a folder called Packages in your kaiserkitchen and put your OEM Packages in it, then run KAISERKITCHEN.CMD chose option c then b. When Ervius build os +package tool opens,click the right tab and add rom(Add your kaiserkitchen folder,but make sure its on your desktop). You will then get a list of packages in the premade folder, just tick the ones you want to add to your rom. Once happy click build rom. Once done exit and KAISERKITCHEN.CMD should crack on by itself....then bring up a couple more apps(Rom Tool and Pagepool)just do what they say . every time you exit these apps KAISERKITCHEN.CMD will take you to the next step.
Click to expand...
Click to collapse
So if I'm understanding this correctly....in order to achieve a completely clean ROM without all the extra fixings I would simply need to use the os.nb file and not the os-new.nb file when cooking correct?

No, the only way to get a completely clean base is to use one someone made, or to manually remove extra oems from an uncorrupted rom (which usually means stock). os.nb is the donor imgfs, os-new.nb is the donor imgfs with your added pkgs.
The PPCkitchen.org kaiser kitchen is clean, and is way simpler to use. If you're trying to get to a clean base, do yourself a favor and just use it.

so... does this mean that if I use for say OEM HTC ROM, and put the os.nb in the base folder, when I build it using the tool, whatever packages I selected are simply added to whatever is on the OS.NB? I thought it would use the baserom as base and whatever apps installed on it are ignored. I guess I totally got it wrong then... So how do you strip out all the programs that have been installed in the baserom? Does this mean you have to dump the image?

maximumbs said:
so... does this mean that if I use for say OEM HTC ROM, and put the os.nb in the base folder, when I build it using the tool, whatever packages I selected are simply added to whatever is on the OS.NB? I thought it would use the baserom as base and whatever apps installed on it are ignored. I guess I totally got it wrong then... So how do you strip out all the programs that have been installed in the baserom? Does this mean you have to dump the image?
Click to expand...
Click to collapse
I do know that in order to get the base OEM packages out of the main build you have to go through and remove and edit certain files to get it done right, which there is information in the Wiki about but haven't really had time to focus on it much. As for the PPCKitchen.org version of the Kitchen, I'm going to try it when I get home tonight because I'm at work currently. Gguruusa, you have to understand that some of us are new to the cooking community and want to be able to get our feet wet slowly and make sure we do stuff right instead of damaging our device. I've only got one Tilt and I don't want to completely destroy it. I would love to cook but need to be able to start off with a simple clean base rom with no extra ingredients and then go from there.

maximumbs said:
so... does this mean that if I use for say OEM HTC ROM, and put the os.nb in the base folder, when I build it using the tool, whatever packages I selected are simply added to whatever is on the OS.NB? I thought it would use the baserom as base and whatever apps installed on it are ignored. I guess I totally got it wrong then... So how do you strip out all the programs that have been installed in the baserom? Does this mean you have to dump the image?
Click to expand...
Click to collapse
No dont put os.nb in the base rom put the RUU_unsigned and extract using KAISERKITCHEN.cmd.....read my previous posts.

gguruusa said:
No, the only way to get a completely clean base is to use one someone made, or to manually remove extra oems from an uncorrupted rom (which usually means stock). os.nb is the donor imgfs, os-new.nb is the donor imgfs with your added pkgs.
The PPCkitchen.org kaiser kitchen is clean, and is way simpler to use. If you're trying to get to a clean base, do yourself a favor and just use it.
Click to expand...
Click to collapse
This looks very promising, downloading it now. Thanks for this! Hope they update it 20273 soon

HEdwards2008 said:
As for the PPCKitchen.org version of the Kitchen, I'm going to try it when I get home tonight because I'm at work currently. Gguruusa, you have to understand that some of us are new to the cooking community and want to be able to get our feet wet slowly and make sure we do stuff right instead of damaging our device. I've only got one Tilt and I don't want to completely destroy it. I would love to cook but need to be able to start off with a simple clean base rom with no extra ingredients and then go from there.
Click to expand...
Click to collapse
That's why ppckitchen.org was born. With ppckitchen.org, it's a point and click thing to build a rom. The mysterious part (making a kitchen base) is done for you. All you have to focus on is what packages you want to add.
You still have to unlock your device and install radios outside the kitchen, which is where people generaly brick their devices.

gguruusa said:
That's why ppckitchen.org was born. With ppckitchen.org, it's a point and click thing to build a rom. The mysterious part (making a kitchen base) is done for you. All you have to focus on is what packages you want to add.
You still have to unlock your device and install radios outside the kitchen, which is where people generaly brick their devices.
Click to expand...
Click to collapse
I shouldn't have any problems then seeing as to how I know that you need to have HardSPL installed and also to be sure to flash the radio AFTER the ROM in order to prevent bricking.

But that takes the whole fun out of cooking a rom when the base is already made for you...!!!
I will have to say my most challenging part is trying to get the base rom the way I like it in order to add whatever I want.
For example....
In my current kitchen I have deleted all of the OEMAPPS folders except the dsm file. I have then rebuilt all of my programs like the way a Diamond and Raphael ROM is....
In essence, If I was to just build my ROM without any packages it would be a clean rom without any software like camera, mms, phoneskins ect....
Its taken awhile thats why I have not published my newest rom yet...

ryncppr said:
But that takes the whole fun out of cooking a rom when the base is already made for you...!!!
I will have to say my most challenging part is trying to get the base rom the way I like it in order to add whatever I want.
For example....
In my current kitchen I have deleted all of the OEMAPPS folders except the dsm file. I have then rebuilt all of my programs like the way a Diamond and Raphael ROM is....
In essence, If I was to just build my ROM without any packages it would be a clean rom without any software like camera, mms, phoneskins ect....
Its taken awhile thats why I have not published my newest rom yet...
Click to expand...
Click to collapse
I totally agree my favourite build was one that went wrong and nearly bricked my phone....sounds sick, but it was going back over what i had done and fixing that was the fun part. That ROM turned out to be possibly my most stable (Yardie 2.1.240) Ha ha i love cooking!!!

ryncppr said:
But that takes the whole fun out of cooking a rom when the base is already made for you...!!!
Click to expand...
Click to collapse
Bah. The fun of cooking is getting a ROM to look and feel like you want. Making a kitchen is entertaining when you haven't done it before, but it's really 99% repetition and 1% art.

[WM Kitchen] Wizard Kitchen

This is a kitchen based on Cracing's CRBuilder2 that I have been using for some time now.
Many thanks to him, S.V.I and the many others that have made this kitchen possible.
This is not a visual kitchen, I have not managed to do that. Instead it is a drag and drop kitchen. You create you ROM batch and then drop it into the OVEN to cook.
Please avoid spaces in file name, it will help avoid problems that may arise.
The ROM batch folder arrangement is that of platformrebuilder.
Code:
_ROM_Batch
EXT
Wizard
Extended Packages
OEM
OEM Packages
ROM
XIP
MSXIPKernel
MSXIPKernelLTK
OEMXIPKERNEL
SYS
SYS Packages
I put the _ in front of my ROM_Batch folders to find them easier.
I have as many error checks as I can think of, but they may not catch everything. Since I drag and drop pieces in and out of my ROM batch, I sometimes drop them in the wrong place. Most of these errors should get caught. This saves having to go through the cooking process to find you have a module in another module's folder.
I also have a Configurator option in my kitchen. This will merge all config.txt files in you ROM batch into one file. This is useful if you are using AutoRun, but have some packages from a RunCC version ROM. You will want to remove any CFG: lines to avoid running a config.txt twice. Also, this is how I do something similar to add2config.txt I have seen in other kitchens. For example, if you create an EXT package that has a config.txt file with some commands you want to add to the main config.txt like EXEC:\windows\myprogram.exe these lines will get added to the new Config.txt. Configurator also adds and CAB files you do not already have listed in the Config.txt files.
Here it is Wizard_Kitchen.7z
It includes Cracing's CR96 Touch HD ROM batch he recently posted.
If you drag and drop the Extended_ROM folder into the OVEN you can build an Extended ROM by itself.

For future use

For future use

For future use

For future use

Thanks! I'll have to switch over to this. I grabbed the RC6 kitchen, and I've started cooking. So far, I've just updated the Google Maps app, as a sanity test. It worked as expected so I'm ready to try something more wild. I'll DL this kitchen tonight, compare it with CRACING's kitchen for the same version, then see if I can figure out how to plug the RC6 parts into it. I know that you've done that already, but I want to learn.
I think your ExtROM magic is going to be helpful in increasing available internal storage, but I don't see it helping the main deficiency of a 6.5 ROM on the Wizard, which is available RAM.

I downloaded this kitchen, extracted it to c:/WizardKitchen, and dragged _Cracing_Latest into OVEN.exe, then answered all the questions with the defaults. The resulting OS was too big.

n2rjt said:
Thanks! I'll have to switch over to this. I grabbed the RC6 kitchen, and I've started cooking. So far, I've just updated the Google Maps app, as a sanity test. It worked as expected so I'm ready to try something more wild. I'll DL this kitchen tonight, compare it with CRACING's kitchen for the same version, then see if I can figure out how to plug the RC6 parts into it. I know that you've done that already, but I want to learn.
I think your ExtROM magic is going to be helpful in increasing available internal storage, but I don't see it helping the main deficiency of a 6.5 ROM on the Wizard, which is available RAM.
Click to expand...
Click to collapse
Didyou mean CR96 Touch HD™ RC5 Reloaded w/ M2D Build 21882 Cracing recently posted? For my kitchen you can do this. Copy the sample folder under Wizard_Kitchen and rename the copy to something like _CR96_RC5 or any other name that works for you. Best to have no spaces. Then copy EXT, OEM, ROM and SYS folders from Cracing's kitchen you downloaded to your new folder _CR96_RC5. Then drag and drop the _CR96_RC5 folder on to the OVEN.exe file and the kitchen will start making your ROM.
Cracing's ROM is clean you so can answer no to the Configurator as he already has a complete Config.txt file in his kitchen. Also, you can answer no to the include an Ext_ROM question or pick yes and copy the empty extended ROM I included in the kitchen. There are a few other questions to answer and yo can try it different ways to see what you like best.
You are correct. The extended ROM only lets us add more stuff into our phone during a flash. I am still watching ShaDrac as he works on Extendir.

n2rjt said:
I downloaded this kitchen, extracted it to c:/WizardKitchen, and dragged _Cracing_Latest into OVEN.exe, then answered all the questions with the defaults. The resulting OS was too big.
Click to expand...
Click to collapse
Use LZX compression. That is how I manage to fit more stuff. I do it by default now asa matter of habit.
If that alone does not help. I typically choose 0, Try Reducing, 4MB pp and include -no cert for the other question group

Thanks, much closer now. Compression was the key to making it fit.
Yes I am trying both _Cracing_Latest and _Cracing_RC6 which I copied from CRACING's recently released kitchen. I am focusing on RC6 but using your _Cracing_Latest as a sanity check.
They both build successfully now. I have not yet burned _Cracing_Latest, but when I burned RC6 it doesn't boot. I've tried twice: it gets stuck at the second screen. I will try same with _Cracing_Latest since I assume it works.

n2rjt said:
Thanks, much closer now. Compression was the key to making it fit.
Yes I am trying both _Cracing_Latest and _Cracing_RC6 which I copied from CRACING's recently released kitchen. I am focusing on RC6 but using your _Cracing_Latest as a sanity check.
They both build successfully now. I have not yet burned _Cracing_Latest, but when I burned RC6 it doesn't boot. I've tried twice: it gets stuck at the second screen. I will try same with _Cracing_Latest since I assume it works.
Click to expand...
Click to collapse
Both of his versions booted for me. Hmmm, I'll try to think of what it could be.