Database Info

Announcement: Wizard Rom-Packer Kitchen V2.0

Welcome to the Wizard Rom-Packer Kitchen V2.0, with "Squeezer" technology!
Please read all the way through before starting, even if you've used a previous version.
USE AT YOUR OWN RISK!
This kitchen is easy to use, but is really meant for those with some previous work with other kitchens,like faria's or 004's or Molski's. (If I've left someone out, I'm sorry about that.) This kitchen is based on Bepe's Hermes kitchen, which has incorporated tadzio's reworking of maimach's imgfs tools. This allows the rom to be packed more efficiently, and thus more packages and files to be burned into the rom. The savings is not trivial, a few megabytes at least.
In addition, I have added a new Squeezer module, based on open-source UPX technology, which actually compresses Office .exe files, freeing even more room in the rom (a few more meg), and actually decreasing load times!
Although the Wizard Rom is not quite as malleable as the Hermes in that the extra space is not translated into additional user storage memory, at least the additional freeware, shareware, themes, etc. which can be burned to the rom do not have to reduce the user storage space.
I hope over time to enhance this further, as new innovations become available, (maybe someone will figure out a way to repartition the Wizard Rom?). Also, perhaps adding some way of automatically generating the xip directory. If you have suggestions feel free to let me know about them.
Error checking is not extensive, so be sure to keep your old rom available to fall back to! Check the size of the generated .nbf file. If its around 59 mb you are close to the limit. Be ready to re-flash in bootloader mode (after paring some packages or files) if the program exits before the 100% mark.
How to use:
Download your favorite base rom, at this point one from another kitchen, which has already been broken down to SYS, OEM, and ROM directories. Delete the SYS, OEM, and ROM directories from my kitchen, and copy the ones from the other kitchen in there instead.
Make a copy of the SYS\OFFICE directory in case of later problems (not likely).
An additional caution/strong recommendation is to delete the /autoupdate package from your roms. This currently does nothing anyway, so you won't miss it, and in any case would likely only create havoc with a custom rom. But additionally the repacking method used in this kitchen removes the extra space in the rom which was to be used for that anyway, and so autoupdate will definitely be useless in a rom built with this method.
Run the SqueezeOffice.bat program. (This compresses your main Office .exe's)
Make sure there is an 80040000-os.nb file in the ROM directory. (It may be called something else and have to be renamed. It'll be around 50mb in size.)
Now click on Start.bat, and away you go...
(Optional) If you want to later go back to using another kitchen, run the PrepareNewNB.bat file. After it completes, there will be a new, compacted 80040000-OS.nb file created in the ROM directory which you can move back to your original kitchen. (Also copy the Office directory back) You will loose some packing efficiency by building in another kitchen, but you will still gain lots of space from having visited here!
Depending on the kitchen you were using, either you will see selectable packages or not during the running of BuildOS. Use whatever method you were using previously to add new packages or to remove the ones you don't want. In general, everything should work about the same way it did before, except you will be able to fit more packages in than previously! (Those who are importing faria's kitchen will have to rename his BuildOS.exe to BOS.exe and bring it into this kitchen. Also, rename his Flash file in the ROM directory to 80040000-OS.nb.)
You will be given the opportunity to go all the way to flashing the rom, similar to the way faria's kitchen is set up. Hold down the Control and "C" keys during one of the pauses provided if you do not want to go to the next step for some reason. (You have a G4, unlocked G3, want postpone flashing for later, etc.) Then press the "Y" key to abort when prompted.
If you'd like, check out the ZSqueezer directory, and the readme there. There you can compress your other programs for even more space (and speed!).
Thanks to all those who have helped me in the past, and especially those who created the tools and roms we all use and enjoy.
Version History:
Initial Unlabeled: Worked fine
V1.1: Added "pre-packing", had a bug in Start.bat
V1.2: Worked fine
V1.3: Deletion of .rgu files from the dump.
V2.0: Removed .rgu deletion (instability), and introduced "squeezer" compression.
Download Link: V2.0
http://rapidshare.com/files/33616241/Wizard_ROM-Packer_Kitchen_V2.0.rar

Standalone Squeezer Module
For those interested in having the "squeezer" technology for their own programs, but aren't comfortable cooking their own roms, I have created a standalone module for that. (Already included in the latest Rom-Packer Kitchen V2.0). I've also started a separate thread for that as well in the Upgrading section. Of course, feel free to leave comments and suggestions in either thread.
Here's the link: http://forum.xda-developers.com/showthread.php?p=1283338#post1283338
Have fun!

More space for later use.

thanks. i'll give it a go later tonight

I just tried these tools and didn't have much sucess....
I used the latest mUn base ROM, added some OEM stuff that I have been using without issues when creating ROM's with mUn's previous ROM. All this went OK. It got to the point of installing the ROM on the device but the ROMUpdateUtility just exited at 98% and left the Wizard in limbo. I have had put it in bootloader and re-intall a previous ROM
There was no message, it just got to 98% on the PC and the Wizard and then the ROMUpdateUtility just exited. I tried manually using the nb2nbf application and copying the resulting nk.nbf to another RUU folder and the same thing happened.
Any idea's?
Andy

ADB100 said:
I just tried these tools and didn't have much sucess....
I used the latest mUn base ROM, added some OEM stuff that I have been using without issues when creating ROM's with mUn's previous ROM. All this went OK. It got to the point of installing the ROM on the device but the ROMUpdateUtility just exited at 98% and left the Wizard in limbo. I have had put it in bootloader and re-intall a previous ROM
There was no message, it just got to 98% on the PC and the Wizard and then the ROMUpdateUtility just exited. I tried manually using the nb2nbf application and copying the resulting nk.nbf to another RUU folder and the same thing happened.
Any idea's?
Andy
Click to expand...
Click to collapse
Can't really say. I've also flashed mUn's latest, and it seemed to go ok. Did you create your own xip directory? If not, use the version in 004's kitchen as a base.

edhaas said:
Can't really say. I've also flashed mUn's latest, and it seemed to go ok. Did you create your own xip directory? If not, use the version in 004's kitchen as a base.
Click to expand...
Click to collapse
I had the XIP directory from the original ROM kitchen (in dOUbleOfour_Wiz_Dev_5.2.1413WWE.rar). I think I might try without any OEM stuff and build it up and see where it fails. In your original post you mentioned the error checking is not extensive, does it log any errors anywhere? (apart ffrom the log.txt file that looks OK).
Andy

ADB100 said:
I had the XIP directory from the original ROM kitchen (in dOUbleOfour_Wiz_Dev_5.2.1413WWE.rar). I think I might try without any OEM stuff and build it up and see where it fails. In your original post you mentioned the error checking is not extensive, does it log any errors anywhere? (apart ffrom the log.txt file that looks OK).
Andy
Click to expand...
Click to collapse
You put too many files, that's why it existed. I presume that because it exited at 98% , meaning that almoust fit, but it didn't . Try leaving out a package ...something about 1MB or so..mabe less

anichillus said:
You put too many files, that's why it existed. I presume that because it exited at 98% , meaning that almoust fit, but it didn't . Try leaving out a package ...something about 1MB or so..mabe less
Click to expand...
Click to collapse
Yep, I think that's what the issue is
When I tried cooking with this as the Base ROM previously I ran into size limitations so I was hoping that these new kitchen tools would solve this -
This allows the rom to be packed more efficiently, and thus more packages and files to be burned into the rom. The savings is not trivial, several megabytes at least.
Click to expand...
Click to collapse
Obviously not enough
I'll play around a bit more and see where I get....
Andy

I'm very sorry, but I left out a very important preparation step in my original posting. Please redownload the package to get the corrected version. (V1.1) I think you will find the results to be much more satisfying! Keep the bug reports coming..

the new start batch file doesn't have the correct paths in it. its trying to work in the root folder not temp.
the original one works good though. too late to flash tonight, but i'll give it a go tomorrow and let you know how it works

I tried to correct the start batch file to use temp but now get errors about not finding initflashfiles.dat in the temp\dump area. I don't have time to debug this right now.
I also noticed that the nb2nbf.exe is a Typhoon Smartphone version (so not sure that is correct for the Wizard).
I will say that the pre processor that does the packing is cool. The Faria Vanilla 80040000.nb (in Faria's kitchen its actually called FLASH.nb0, so I just renamed it) was 58.3MB in size. After running the PrepareNewNB.bat it was then 57.1MB, so a full meg smaller. I'll see about moving this over to the Faria kitchen and using it to rebuild my rom later and see how that changes things when its actually flashed to the phone.

i'll post the working one in a little bit.
edit... here's the one that works for me

notyourdaddy said:
i'll post the working one in a little bit.
edit... here's the one that works for me
Click to expand...
Click to collapse
Thanks, I was bleary eyed last night with trying to figure out what was going on that it wasn't working for you guys, and I ended up "fixing" some things that weren't broken I guess.
Just be sure to delete the old dump file in the temp directory after you run the preparenewnb.bat file.
Has the compression been working for you?
I appreciate your help. I'm juggling lots of things with "real life" and am sorry for the slip-ups.
I am updating the first postings.

notyourdaddy said:
i'll post the working one in a little bit.
edit... here's the one that works for me
Click to expand...
Click to collapse
Maybe its an issue with the Faria RK base rom and compatibility with this kitchen, but even with this updated file (thanks for that) I still get the following error when running the build os step:
Code:
Could not find file "temp\dump\initflashfiles.dat".
The other question is, is it ok to use the Typhoon Smartphone nb2nbf.exe that comes with this?

mfrazzz said:
Maybe its an issue with the Faria RK base rom and compatibility with this kitchen, but even with this updated file (thanks for that) I still get the following error when running the build os step:
Code:
Could not find file "temp\dump\initflashfiles.dat".
The other question is, is it ok to use the Typhoon Smartphone nb2nbf.exe that comes with this?
Click to expand...
Click to collapse
Yeah, I was just running through the faria kitchen and had the same issue. The workaround is to copy the initflashes.dat file in the OS folder and then paste it into the dump directory after buildos has deleted the previous dump and before it is processing the sys\os directory. (Watch the process messages at the bottom of the buildos screen.) This worked for me.
Yes the typhoon version works fine. I think they are mostly all relabeled versions of the same original tools. (Except the imgf tools which are recently updated by tadzio.)
Hope this helps.

weird. intiflashfiles.dat copied over for me using 004's kitchen

I just finished doing a build with faria's kitchen as a base, and was somewhat disappointed that I was unable to flash the entire kitchen at once. I had to leave out enterprise and voip (which is fine for me, but some may want them). I'd be interested in hearing how much extra space people are finding. I felt like I was able to cram a lot more into double_ofour's mUn release, but perhaps that's because it was more stripped down to start? Maybe "the kitchen sink" was a bit optimistic.

Re Faria kitchen
mfrazzz, The easy fix for the faria kitchen is to use faria's buildos.exe instead of the generic one I included. That one runs fine with his kitchen. Just rename it to bos.exe. (or edit the start.bat appropriately.) I don't think this will affect the packing of the files.

Update
OK, Things seem stable now. I've updated the first posting with additional information gleaned from everyone's input, and updated the version. The old start.bat that notyourdaddy posted should not be necessary.
FYI, I got feedback from one user that they got about 2.5 meg additional space from these tools vs the old tools. Not as earth shattering as I'd hoped, but helpful. Roms with more small files, as opposed to those with larger files will likely benefit more, as the savings are in the "padding" between them.
Feel free to incorporate this into your own kitchens.
Regards,

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..

[20931 SYS/ XIP Ported]Improved PackageTools and BuildOS now for Wizard [29/11/2008]

I have been using many kitchens over the past year. Cooking horrible roms, decent ones and now a pretty good one. My problem was always the various tools lying all over my hard drive. Luckily I came across this litte gem by Ervius
Package Tools and BuildOS rolled into one. I also noticed that it handles rgu files much better than the previous BuildOS, it choked on an incorrect rgu file. Which in turn allowed me to get Video working in HTC Album 2
I have modified the batch files for our Wizards and have been cooking and im loving it
PackageTools+BuildOS (Latest combined version)
rgu-2-xml : Convert .rgu to provxml files
SYSVersion : Generates a version list of your SYS Folder
All the usual build tools :G'Reloc, M'Reloc, ImgFS Tools
AllPackagesToOne - Protect your rom from being ripped apart and the whole world being able to share in your utter cooking brilliance, via a tickbox ofcourse
Automatic Find and Fix duplicate file errors during BuildOS process
More features which I am either too lazy to list or dont use at all
Just add SYS,ROM and OEM folders. It also have a nice feature which allows you to select OEM Packages and save it as a preconfigured rom. Extra OEM packages can be placed in a Packages folder. BuildOS will load those files also (No more OEM's all over your hard drive).
BuildOS also runs G'Reloc during the dump process, but for good measure I also included it in the batch file.
Also added -conservative to the Imgfs Tools portion of the script to protect against overcook
BuildOS generates pretty log files which shows where stuff went wrong
Extract the zip file. Run Kitchen.exe and watch the magic at work.
Note
For some reason the output window text is black on a black background, but at the top is a nice running status. If not sure just hilight the output window.
If you start up and It complains about folders just create them
Download
Ported 20931 SYS/XIP without PIE 6 download
Microsoft Visual C++ 2008 Redistributable Package (x86) is need to be installed in your PC
[URL="http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&DisplayLang=en]Get it here[/URL]

Hi,
Nice kitchen.
But its little bit difficult compare to hypecore.
Thanks for great kitchen.

Nice release ..i think im gonna start cooking too

Does it also have my favourite tool "Alpackagestoone" to remove and merge DSM and RGU files from Rom?

Noonski said:
Does it also have my favourite tool "Alpackagestoone" to remove and merge DSM and RGU files from Rom?
Click to expand...
Click to collapse
It does, in the prettiest little tick box you have ever seen, just below the Output Window. One of the really cool features of this version of BuildOS is the ability to scan for and fix duplicate files

sounds really impressive! downloading...
I'll recook my rom with it and let you know how it went

where should I extract this kitchen?
Error: pkgdll is missing
Never mind. copied it to the same folder as the kitchen.exe

I cant cook... .net problems
Many problems with the kitchens... why I cant install .net frameworks more than 2.0 that i have why... cause It said on every reinstalation missing file the installer will be quit! GOD DAmn... I think I need to reformat my PC and almost backup 40 GB info or... does anybody has an utiliti that erase all of anay program that stucks on uninstall or repair or install? i need to kill those .Net frameworks.

+ Que PPC said:
Many problems with the kitchens... why I cant install .net frameworks more than 2.0 that i have why... cause It said on every reinstalation missing file the installer will be quit! GOD DAmn... I think I need to reformat my PC and almost backup 40 GB info or... does anybody has an utiliti that erase all of anay program that stucks on uninstall or repair or install? i need to kill those .Net frameworks.
Click to expand...
Click to collapse
What OS are you running on your pc ? .net 2.0 and higher really like XP Sp2. Do a google search for CCleaner and "Uninstall Utility" this might help before you format dude.

Errors I am facing:
can not find \ROM folder
Windows can not open this file: OS.NB.Payload
Windows can not open this file: OS.NB.extra
BuildOS: Error, can not find ROM Folder!!!
Where are these files supposed to go? can you provide a tree map?
Can you also tell me what exe opens what file?
I'm almost having to pour cold water over my self
The main issue is not knowing where the ROM folder is supposed to go.
Also, not being able to see what the thing is doing (black on black) is really frustrating me also.
When you get a chance, let me (us) know how to use this cooker. it looks like it can do a lot more than I'm used to... but at the moment I am finding it useless.

S.V.I said:
Errors I am facing:
can not find \ROM folder
Windows can not open this file: OS.NB.Payload
Windows can not open this file: OS.NB.extra
BuildOS: Error, can not find ROM Folder!!!
Where are these files supposed to go? can you provide a tree map?
Can you also tell me what exe opens what file?
I'm almost having to pour cold water over my self
The main issue is not knowing where the ROM folder is supposed to go.
Also, not being able to see what the thing is doing (black on black) is really frustrating me also.
When you get a chance, let me (us) know how to use this cooker. it looks like it can do a lot more than I'm used to... but at the moment I am finding it useless.
Click to expand...
Click to collapse
I really wish I could decompile and just fix the black on black issue. Coz it is a simple case of just changing the font. Unfortunatly it is not written in .net like the previous BuildOS, so no luck there
This should be your default layout:
Base Folder-
->Compile Tools (OS.nd encoding tools)
->Flash (Created by Batch file, your new OS.nd ends up here)
->OEM (I like to put the BASE OEM Folders in here OEMAPPS etc)
->Packages (This is where I drop my custom OEM folders)
->ROM (OS.nb XIP,romhdr.bin lives here)
->SYS (Yeah well we know this one)
The error you are getting is when you try and extract a rom with Package Tools in the kitchen. Here is the procedure:
Create a base folder, I normally use Base_Buildnumber_Device
Select your Dump Type in the bottom check boxes, either a folder where you have already dumped a rom or an *.nb,*.nbf type file
Start your kitchen and select Open on the Package Tools tab.
Browse to the folder you have just created select the folder of rom file based on the above selection
Package tools will now extract the rom and create OEM and SYS Folders if possible
In case of cooking which I believe you are after:
Create the above folder structure with all files in place
Select BuildOS tab
Click Load Rom
Edit OEM's etc and just press Go

thank god u placed this tut, i thought i was the only one with theis prob oO
I'm almost having to pour cold water over my self
Click to expand...
Click to collapse
you were "almost" but i already did several times, what more do you expect if your working on Core,Improved Pakagetools, Molski Devpack,tnt kitchen and Porting :S

ather90 said:
thank god u placed this tut, i thought i was the only one with theis prob oO
you were "almost" but i already did several times, what more do you expect if your working on Core,Improved Pakagetools, Molski Devpack,tnt kitchen and Porting :S
Click to expand...
Click to collapse
Dude I battled to get the whole thing running as the tut's where for Kaiser and the tools were abandoned by the looks of it. But once i started using the cool right click and import package features I was sold.

Sorry. double post.

->ROM (OS.nb XIP,romhdr.bin lives here)
That may be what I am missing. how do I extract that?
I Have OS.nb; XIP.bin XIPfolder

@S.V.I Here is the romhdr.bin : http://forum.xda-developers.com/attachment.php?attachmentid=131286&d=1227164342
@cornelha i think u need a break lol you attached te file in the siff thread

->ROM (OS.nb XIP,romhdr.bin lives here)
Click to expand...
Click to collapse
should the XIP be in the bin extension or in a folder the one which Hyper Core Generates) ?

ather90 said:
@S.V.I Here is the romhdr.bin : http://forum.xda-developers.com/attachment.php?attachmentid=131286&d=1227164342
@cornelha i think u need a break lol you attached te file in the siff thread
Click to expand...
Click to collapse
OMFG dude I think you are right. Dev by day ... cook by night ... hey wtf is my gf ?!?!?

how to use this kitchen??
i run Kitchen.exe from desktop, but error(installation error)
any help me??

fachry said:
how to use this kitchen??
i run Kitchen.exe from desktop, but error(installation error)
any help me??
Click to expand...
Click to collapse
Yeah I realised now that when I zipped up the Kitchen I left pkgcommon.dll in the Tools folder, this should be copied to the same folder as Kitchen.exe.
Your error however comes from me not stating the .net Framework 2.0 or highers is required. I take these for granted since I have Visual Studio installed on my machine anyway

Uni ROM Kitchen v2.0 by Tomal: Next generation Kitchen for Universal

Guy's,
This is my 2nd attempt to build a useful kitchen for Uni lovers. It uses a new set of tools and technology and you can customize/cook the rom exactly the way you like it. Porting or building XIP was a real pain but the kitchen builds the XIP and IMGFS together and importantly without manual intervention.
I believe this is the easiest kitchen ever built for Uni and you'll simply enjoy it.
The OS has been included in the kitchen is a fresh new Core - CE OS 5.2.21014.
OK, let's go for working part -
Unrar the kitchen in any of the drive in your PC (but must be in root) and it should look like - D:\TML_UNI_KITCHEN.
You'll find a command script "build_rom.cmd" under the TML_UNI_KITCHEN directory. Now, make a coffee, then just hit on this script and reluxe. Your ROM will be cooked within couple of minutes. Well, a little dialog box will pop-up at the asking what to do, select Encode to encode the rom and then exit.
You can follow the encoding steps like:
>>Encode>>Browse>>open nk.prj>>Encode>OK>>OK>>Exit.
Now, got to RELEASE directory, open ROMUpgradeUt.exe and flash the ROM to your device.
Advance part -
You can modify few parameters under the build_rom.cmd to make your custom rom.
set BUILD_TYPE=Regular
This is the type of your ROM to be cooked. The value "Regular" has an association with the directory \TML_UNI_KITCHEN\EXT\Regular. Put all the packages here, those you want to include in Regular build.
set BUILD_TYPE=Vanila
The value "Vanila" has an association with the directory \TML_UNI_KITCHEN\EXT\Vanila. Put all the packages here, those you want to include only in Vanila build.
PLease note, packages under the Regular directory will not be included in Vanila build and vise versa. There is also a Common directory inside the \TML_UNI_KITCHEN\EXT. You can put the packages here, those you want to include in Regular and Vanila both the builds.
set BUILD_NO=21014
This is the build number of the rom. The value "21014" has an association with the directory \TML_UNI_KITCHEN\21014. Actually you can put any value you want but whatever value you put must be associated with the same directory. Importantly SYS and XIP must be located under this BUILD_NO directory, i.e. \TML_UNI_KITCHEN\21014\SYS, \TML_UNI_KITCHEN\21014\XIP.
ROM template located under the \TML_UNI_KITCHEN\ROM directory.
OEM drivers located under the \TML_UNI_KITCHEN\OEM directory.
ROM will be transfered to \TML_UNI_KITCHEN\RELEASE directory after the successful build.
Directory Structure:
\TML_UNI_KITCHEN\21014
\TML_UNI_KITCHEN\21014\SYS
\TML_UNI_KITCHEN\21014\XIP
\TML_UNI_KITCHEN\21014\romhdr.bin
\TML_UNI_KITCHEN\EXT
\TML_UNI_KITCHEN\EXT\Common
\TML_UNI_KITCHEN\EXT\Regular
\TML_UNI_KITCHEN\EXT\Vanila
\TML_UNI_KITCHEN\OEM
\TML_UNI_KITCHEN\RELEASE
\TML_UNI_KITCHEN\ROM
\TML_UNI_KITCHEN\ROM\nk.nba
\TML_UNI_KITCHEN\TOOLS
\TML_UNI_KITCHEN\build_rom.cmd
Please note the kitchen is still in beta so you may notice some unwanted thing which I haven't noticed earlier. Also, the XIP inject part has not been finished yet. But it's not a big deal and not necessary for the current build.
You can easily inject it using Bepe's Xiptool if you want. Just pick the xip.bin from "temp" directory after the build, rename it to xip_out.bin and write to nk.nba.
There is also some other secret thing which I forgot to mention and love to forget.
Acknowledgment:
Major credit goes to Bepe as it was not possible to built this kitchen without his great tools.
Uni Kitchen v2.0 (beta):
http://vidmes.com/xda/Uni/ROMs/Tomal/TML_UNI_Kitchen_2.0_Beta.rar
http://vidmes.com/xda/Uni/ROMs/Tomal/TML_UNI_Kitchen_OEM.rar
Cheers!!!

Gr8 news Tomal.
Thx 4 you hard work.

Good job!Thanks!

Hm, i tried to start kitchen, but unfortunately getting error:
Code:
PLATFORMREBUILDER Copyright (c) 2008-2009 bepe Jan 4
Build: Regular
Locale: 0409
Preparing release structure...
... done!
Collecting standard packages and initializing hives...
XIP: 3 packages
IMG: 71 packages
Error: 0x8000000a
'initflashfiles.dat' does not exist in the specified paths!
ERROR! (errorlevel: 1)
Press any key to EXIT

I get the same initflashfiles error. It occurs in this command line:
.\tools\platformrebuilder.exe
in .\tools\buildOS.cmd

Same error here.. :/ If there is a fix it looks pretty good! Well done, Tomal

opppppsss...my mistake!
I forgot to include the OEM pack. Don't worry, I'll upload it asap.
Update:
OEM part has been uploaded (in 1st post). Extract it under \TML_UNI_KITCHEN directory.
regards

tomal said:
[...]
There is also some other secret thing which I forgot to mention and love to forget. [...]
Click to expand...
Click to collapse
LOL how nasty
gonna try and study it...
thx a lot for your work! hope my little donation was appreciated more than simple words

Wonderful!!!! Thank You
And with VInit help we can add flashdisk until he gets a way to make combined storage work for G4.

this could be the start of something new for uni lovers, many tnx tomal

Thanks a lot Tomal!
Hopefully on my vacations I can get into it!
Cheers,

Great work, Tomal I have just one question. I started build_rom.cmd and after some time a window pop-uped asking for HTC64 EXT rom... and there were 3 options : Encode, Decode and Exit. Afraid of doing something wrong I clicked Exit. Can you give some instructions how to continue the process and if there are any additional settings to make.
Thanks in advance .

simeonfilipov said:
Great work, Tomal I have just one question. I started build_rom.cmd and after some time a window pop-uped asking for HTC64 EXT rom... and there were 3 options : Encode, Decode and Exit. Afraid of doing something wrong I clicked Exit. Can you give some instructions how to continue the process and if there are any additional settings to make.
Thanks in advance .
Click to expand...
Click to collapse
Select Encode>>browse (to open the project file)>>open nk.prj>>Encode>OK>>OK>>Exit.
Cheers

Thank you! I just flashed with the Vanila ROM and it seems to be very good - it's fast, after soft reset there is ~28 mb free RAM. Again - thanks for your hard work .

it's possible to do a multilanguage/region kitchen? almost for common applications and configuration applets.
thx.

tomal said:
Please note the kitchen is still in beta so you may notice some unwanted thing which I haven't noticed earlier. Also, the XIP inject part has not been finished yet. But it's not a big deal and not necessary for the current build.
You can easily inject it using Bepe's Xiptool if you want. Just pick the xip.bin from "temp" directory after the build, rename it to xip_out.bin and write to nk.nba.
There is also some other secret thing which I forgot to mention and love to forget.
Click to expand...
Click to collapse
I tested it, and its working fine 100%, 1000 thanks Tomal for the great work!!!! I also used the optimize tool from HyperCore kitchen and the final nb.nbf is only 44M, but what about the XIP is it in my new rom or is it not and if not how do I inject it? I tried the implantxip tool from the TOOLS directory but I seam to not getting it how it works. Please help!!!

With the OEM directory in place, this kitchen produces great ROM's!
Thanks Tomal!

Thanks Tomal !
May i know how to use your kitchen to dump other ROM ?
Very appreciated your reply !!!
Thanks & Regards,

Upload This ROM
Can you guys help in uploading a ROM produced by this kitchen new Core - CE OS 5.2.21014
I would like to try it out.
Appricated ...

Vanilla nk.nbf
Here you are Fast and stable :]

[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.