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,

ROM Kitchen Features ?

I Am Currently In The Process Of Developing A ROM Kitchen For The Universal.
My Work So Far Is Going Good.
The Purpose Of This Thread Is To Gather Information On What Users/Developers Want In A Kitchen.
The Kitchen Is A Windows GUI That Controls The Usual Tools. (Not Batch Scripted And Could Be Ran From Removable Storage)
It Should Work On Any Version Of Windows Without Complications.
I Am Trying To Make This GUI Easy To Use So That A Complete N00B (Or Trained Monkey) Could Use It,
But It Also Includes Complete Control Over The Entire Cooking Process Which Gives Experienced Developers/Cookers More Control Without All The Command Line Workings.
Please Feel Free To Post Your Ideas/Requirements And I Will Try To Include It Into The Kitchen.
PS. This Kitchen Is For The Universal Only.
Regards,
OllieD

Would certainly like it to be able to create flash drive on Universal - I have found this a very useful feature in Tomal's ROMs.

uMP2k said:
Would certainly like it to be able to create flash drive on Universal - I have found this a very useful feature in Tomal's ROMs.
Click to expand...
Click to collapse
One Of The Features I Will Be Including (Hopefully) Is The Automation Of Converting Left Over ROM Space Into A Flash Disk.
Regards,
OllieD

OllieD said:
One Of The Features I Will Be Including (Hopefully) Is The Automation Of Converting Left Over ROM Space Into A Flash Disk.
Regards,
OllieD
Click to expand...
Click to collapse
Hi,
I started a GUI based Kitchen a while back, almost completed too, but abandoned due to time.
What language are you writing it in, and what tools are you basing it on (HyperCore or Mamaich/Helmi/Ivan tools)
I'll post some picks of my GUI (If I can find it again)
Would also be useful to have it portable for other devices, doesn't require that much extra code to do it.
I'll see if I can dig out my design docs too to assist you with functionality/features.
Cheers,
Beasty

Thanks Beasty.
Its Coded In VB.Net So Any Windows With .Net Should Run It.
I Appreciate The Idea Of Opening The Kitchen To Other Devices.
The Problem Is This Kitchen Is Already Quite Customised For The Universal.
It Relies On Alot Of Other Tools But The Idea Is To Fully Automate Everything I Can. (The Less User Interaction Required For N00Bs The Easier They Will Find It To Use.)
In Its Current State It Can...
Decode An NBF File To An NBA And Split The Header.
Extract The IMGFS Partition To A File
Dump The Contents Of The IMGFS Partition
Sort The Dump Folder Into Packages ( Just About To Code This One)
Planned Universal Specific Features Include...
Automatic Injection Of Flash Disk.
Splash Screen Replacement ( Need To Figure Out How To Convert BMP/JPG/GIF To RSB )
Regards,
OllieD

Although I don't have a Uni, this seems a great idea, and if I have the time I'm going to do something similar for the Prophet...
One question though, with your splash screen conversion, can the image be in the *.nb format and then converted to *.nbf along with the OS? If so, pof has a tool! http://pof.eslack.org/blog/
For me, one of the most important features would be some way of having XIP porting (like ivanmmj's EasyPortOven).

OllieD said:
Splash Screen Replacement ( Need To Figure Out How To Convert BMP/JPG/GIF To RSB )
Click to expand...
Click to collapse
This is a aplication for Convert to rsb.

Extraction Side Complete.
l3v5y said:
One question though, with your splash screen conversion, can the image be in the *.nb format and then converted to *.nbf along with the OS? If so, pof has a tool! http://pof.eslack.org/blog/
Click to expand...
Click to collapse
Thank You l3v5y.
Pof's Tool Does Generate The Required Output If Ran With The Correct Parameters.
So The Current Feature List Of The Kitchen At The Current State Is...
Decode An NBF File To An NBA And Split The Header.
Extract The IMGFS Partition To A File
Dump The Contents Of The IMGFS Partition
Sort The Dump Folder Into Packages
Extract XIP Contents
Create Compatible Splash Images.
I Think Thats About It For The Extraction Side Of Things.
Now To Code The Build Process.
Regards,
OllieD

Great to hear
How about a quick way to edit the ROM name / version & date
Similarly for setting pagepool.
I think including HEXEDITOR inside will help in case the above 2 are not possible.
It's great to see "Oli-n-Family" together over here

rdosti said:
Great to hear
How about a quick way to edit the ROM name / version & date
Similarly for setting pagepool.
I think including HEXEDITOR inside will help in case the above 2 are not possible.
It's great to see "Oli-n-Family" together over here
Click to expand...
Click to collapse
That sounds useful!
Now, probably a slightly cheeky question, but is there anyway this could be modified to suite the Prophet, or alternatively, some form of code released to allow for alterations?
Oh, and BTW I'm called Oli as well! Time for some epic confusion!

Hi Ollie,
great idea, and I really hope you get it working. It'll be a godsend!
Some things I'd like to see for the edit/build phase:
1) A UUID generator.
2) A DSM builder like BuildDSM, but able to rebuild ALL DSMs within a given 'tree'. I use a CMD script to do this, but it's a bit of a pain having to hit 'enter' after every package!
3) A .provxml editor (for Diamond packages & any others that use Autoshortcut).
Thanks and good luck!
-PJC

pjc007 said:
Hi Ollie,
great idea, and I really hope you get it working. It'll be a godsend!
Some things I'd like to see for the edit/build phase:
1) A UUID generator.
2) A DSM builder like BuildDSM, but able to rebuild ALL DSMs within a given 'tree'. I use a CMD script to do this, but it's a bit of a pain having to hit 'enter' after every package!
3) A .provxml editor (for Diamond packages & any others that use Autoshortcut).
Thanks and good luck!
-PJC
Click to expand...
Click to collapse
The buildDSM could be automated relatively easily in C#, and I've seen a UUID generator demonstrated on MSDN.
For ProvXML editing, notepad can do it, so that shouldn't be too hard I think...
I might make myself a DSM builder program, and I can post the code if so desired...
One thing that I made my self and that helps for ROMs with lots of OEM packs is a tool that goes through the OEM folder, and adds the name of each pack to a text file so you can easily list all the packs/programs. I can post that code too if wanted!
Still, all of these tools in one program would be awesome!

Just wondering...
...how this is progressing?
I'm sure I'm not the only one that would love to see this out & working!
-PJC

Rom Files

Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.
my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.
i am frustreated man and really need help.

Tambuyeye said:
Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.
my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.
i am frustreated man and really need help.
Click to expand...
Click to collapse
When creating packages with Package tool it creates the following folders:
SYS
OEM
Missing <-- Thats what you are looking for.
I suggest that if this is your 1st attempt and you are building based on a custom rom, use HyperCore Kitchen. Its very easy to use and does the extraction much quicker and easier than doing it by hand. Once you have the hang of it then just move your stuff to another kitchen. Nice part about HyperCore you can dump just about any rom if you set it for that specific device. Just a note: some cookers protect their roms and you end up with almost everything in Missing. You can dump WizFlo from 6.1.1.3 upwards easily

When you have run the PkgTool - Build Packages option, don't mistaken the Missing Manifests for the same thing as Missing Files or Missing Packages. The missing "dsm" manifest files the Pkg Tool refers to are contained in the XIP files (which you will be doing next, i.e., extract XIP). So, you can just ignore the Missing Manifest message and continue on, however be aware that you must use compatible XIP that contains these "missing" dsm manifest files when you go to re-build your rom.
If there are indeed missing packages or missing files, it will tell you exactly what they are and where (what folder) they are supposed to go into. These missing packages/files will be in the dump folder along side the OEM and SYS folders after you run the Build Packages option in the PkgTool app.
This took me a while to realize as it was not explained (or at least I did not see it anywhere) in the various forums/threads on rom building.
If I am wrong on any of this someone please correct me as I too am relatively newbie to this and still learning.
Good Luck!

[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

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