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,

[Main-OUTDATED] The Development Chronicles... [Day 4 - 08/25/08]

These are the development chronicles. They will chronicles the creation of Just, my next ROM. I will keep track of everything I do here. Please do not post anything on this thread. I will create a second sister thread where you can ask questions. Please keep the threads clean of anything that is not related to the subject. I am not a mod, so I cannot delete posts, so I will rely on your honor.
Note: Since I work full time (actually, about 46 hours...), am a student and I'm getting married soon, my time is a little on the limited side. This will not be updated daily. Ivan's Class will not be cancelled, but will be placed on hold for the mean time. I will probably copy and paste lessons from there to here to save time, though. Since this is going to be my next rom, let's hope that I will keep at it until we have a working ROM.)

Day 1: Our OEM
Today we'll be getting our OEM. To do so, we will follow the following:
Welcome to Lesson 2. Today, we will learn how to decompile a ROM using Hypercore. This will serve us in two ways.
1. You'll understand how to decompile a ROM and obtain files from it.
2. You'll be able to get started building your own OEM folder. This OEM folder will be the basis for every ROM that we will be building in these lessons.
To begin:
Go here and download the Hypercore.7z file. You'll need 7Zip in order to open the file. Uncompress the hypercore folder into your desktop. Uncompress the Core folder into your main drive (C for MOST people.) These are my personal folders so you'll get more tools, fixed batches, correct settings for the Herald... and probably some random junk.
Here is where the fun starts. Start by grabbing a base ROM. You can use either Tmobile's Wing ROM or HTC's Herald ROM. I'm sure you can find a copy somewhere...
If you've downloaded 7zip, you should be able to right click on the RUU file and extract it somewhere. You'll notice that one of the files is named RUU_signed.nbh. This is a ROM in its NBH format.
Extracting the files in your NBH.
Go to your newly created HyperCore folder, open up Tools, then NBH_Tools_v1.1.
On the first tab, you will notice one and only one button... Press it.
Search for your RUU_signed.nbh file and click Open.
Save the files somewhere.
As you can see... this isn't rocket science.... yet.
Blind Date with HyperCore
Just to tell you a few things about HyperCore:
You will be working with the HyperCore folder. The Core folder includes all the things that are done in the background. Don't touch it.
The Panel folder holds most if not all the batch files that make the kitchen possible.
The Build Folder is where you'll find your OEM folder once we're done with the next step.
Extracting your files
Find Windows.nb in the folder you just extracted everything to.
Rename this file to os.nb
Copy the os.nb file to your HyperCore/Extract/Source folder.
Go to HyperCore\Panel\Extract and launch DumpRom.
Press Enter and wait...
With any luck, you'll see:
{
"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"
}
Press 1 then Enter to Start the Package Tool. Press Enter again. Then 3 and Enter to do it manually.
Go to File, Open, open your HyperCore\Extract\Dump folder.
Click on Tools, then Build Packages but do not close that window.
Rename the Dump folder into Packages and then close the Package Tool.
Press 4 to move your OEM and SYS folders. Press N to bypass making a backup.
That's it. Now you have your very own OEM folder to play with. You can discard the SYS and ROM folders, as we will not be using them in this class. The next lesson will teach you about the OEM folder, what it does, how to clean it up, etc. Then we will be downloading our other kitchen. Bepe's kitchen... or maybe my own EasyBakeOven... anyhow, it's late and the only reason I'm still up is because I promised you guys a lesson. It might not be pretty, but it will get the job done. Maybe I'll fix it up and rewrite it later when I'm fully awake. lol
Click to expand...
Click to collapse
Source: My Cooking Class: Lesson 2
The XIP and SYS will be extracted next. I will be using the XIP from Bepe's kitchen as a base to port other XIP's over. The SYS will come from somewhere else... I haven't decided which SYS to use.

Day 2:
OK, so we have the OEM folder which is where most of my ROM is going to come out off. Now it's time to plan out my goals so we know what we're building.
Goals:
80mb free of storage for LZX version
30+mb of RAM
A dark red and black theme
Raw speed
Stability above all else
Starting from scratch with a new core, instead of working with my previews cores like I did with Just2Clean and JustMe.
umm.... All my ROMs are the same aren't they? lol
So we have to familiarize ourselves with the OEM folder.
Lesson 3: Getting Personal with Your OEM
In today's lesson we are going to learn what the OEM folder is, what it does, how it does it, and why it is so important to you personally as a cook. This will be your signature and where most of what makes the ROM yours will take place...
The very first thing we will do, though, is make sure that you have your computer set to show all hidden and system files.
Open up the folder that holds the OEM folder, go to Tools, Folder Options, click on View, make sure Show Hidden Files and Folders is checked, hide extensions for known types in NOT checked and Hide Protected Operating System Files is NOT checked. Please do not go around deleting files in your computer after this and then PMing me that your PC will no longer boot up.
File Structure
The file structure of a STOCK OEM folder is as follows:
LangDB
OEMAPPS
OEMDrivers
OEMMISC
OEMOPERATORS
OEMVERSION
OEM_DPI_96
OEM_Lang_0409
OEM.cer
What does this mean? - We will not be getting into all of them, only the ones important to today's lesson.
OEMAPPS - This is where all the OEM apps are stored. This means all the apps that are not originally part of the OS and were placed in by the phone manufacturer. These apps include the camera utility, a java manager (usually a crappy crippled old one, too...) etc. This folder is usually full of random useless things but has no real order within it. You'll see files for things like an FTP-Bluetooth utility and other things you might not need. Cleaning this OEM folder will be the meat of our cleaning process (although not the only place.)
OEMDrivers - This is where the drivers of the device are stored. You'll also notice that a few ringtones and such should be listed in here. These will be part of the cleanup process, too. The only driver here which you can touch will be the touch.dll (no pun intended.) This driver will be replaced later on to allow for BioTouch (the ability to touch the middle of the screen to scroll instead of the side bars.)
OEMOPERATORS - This is where a lot of the junk that your OEM puts in goes to. This is also where you can set your preferred theme and setup your UC compatibility. Unless you're me... and you use a separate package... more on this later.)
OEM_Lang_0409 - You will see a lot of MUI's here. MUI's store the wording on programs and thus the language of your device. More on this later. This is also part of the cleaning process.
So now you have a VERY basic overview on the OEM folder. We will get more indepth as we go through this class.
Click to expand...
Click to collapse
Source: My Cooking Class: Lesson 3

The Clean...
Day 2: Part 2:
OK, cleaning an OEM folder is the funnest/least fun part of making a ROM, depending on how you see it. To me, it's a fun investigation game.
I'm going to just list the folders in the OEM one by one and post exactly what I've done with them.
We have a couple of ways of cleaning out files we don't want. We have the research way, which means we will research to see what the files do. This one we do AFTER we get rid of the bulk of useless files. The second way, which is actually a short cut I made up... is to find packages of programs that you do not want and copying and pasting those files into my OEM folders. By default, windows will leave those files highlighted when the copy is done. All the files, even if they overwrote the files you had in there that you don't want anyways. Then, you just delete those files. If this sounds confusing, that's how everything in my head it... lol
So....., in practice:
Open oem package of program you don't want.
Copy all the files.
Paste them into the first OEM folder.
Delete the files.
Paste them into the next folder.
Delete the files.
etc.
It's a cheap trick, but it does its job well.
So how do we know which programs are in that we don't want? Install the stock RUU and write down what you want to get rid off. Or look through the files and research to find out what they are.
If you really want to be extra picky, you can also search for all the registry keys that the RGU has in that package as well.

Hey Ivan. Nice informative thread you got here. Long time, how you been. Congrats on your wedding
There, I posted a junk post But me being a Mod, can delete useless posts from here to keep it clean (including mine) Just let me know when you wish to get this one cleaned up

lol. You're forgiven this time.
Thanks on the wedding congratulation!

Day 3: OK, So I went through all the packages for the easy cleaning process. I also looked through all the RGU's and deleted any and all references to the stuff deleted. Now I have to go file by file and find out what to keep and what not to keep. One thing to notice, PROVXML files also include a lot of info that has to be edited. Think of them as a making of an XML file and a RGU file.

Day 4: I had an idea. I'm going to use the extROM for storage of certain system files that do not require a read directory... That might give me the push I need to reach 80MB free.

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!

(6-16-09)TPC & Joshkoss Collaborative 6.1 and 6.5 Kitchens for Noobs-updated builds!

(6-16-09)TPC & Joshkoss Collaborative 6.1 and 6.5 Kitchens for Noobs-updated builds!
Not too long ago, i started trying to learn how to cook roms and i was fortunate enough to have some people on here help me get started...so i thought i would try to do the same for other people who want to learn how to cook. One of the people who helped me the most was Joshkoss, we have spent alot of time testing different things and trying to make our kitchen as good as possible and its turned out pretty good Since i like to cook wm 6.1 and Josh likes to cook 6.5, we thought we would kinda share this thread..Josh doing 6.5 and me doing 6.1. We are including our base kitchens of our latest ROMS, and with our instuctions you guys will be able to customize your ROMS however you want None of the main tools in the kitchen were created by us, we just put them all together with a few batch files...all credits to creators of tools without them we would have no kitchen. We do plan on writing tutorials, but you guys will have to be patient because this is a work in progress we will try to update as much as we can. Here is a list of what will be included in the kitchen.
--choice of either LZX or XPR ROM compression(thanks ivanmj)
--option to compress all .exe's in EXT folder with UPX
--automatically hides all files in dump folder for smoother running ROM
--includes MainSplash.nb
--includes 101 RAM tweak(thanks ervius, anryl)
--includes toolset to create packages from cabs for your rom
--tool to batch compress .exe's with UPX any folders,subfolders you choose
--latest official wm 6.1 and (unofficial) 6.5 builds(thanks anryl)
all updated resources in 4th post
Download kitchens on 2nd(6.5) and 3rd(6.1) posts
{
"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"
}
thanks to these people for tools and helping with kitchen
Bepe, ervius, anryl, dark simpson, tadzio, ivanmj, upx team, abusalza, medkid, DA_G, conflipper,mbarvarian, OndraSter ??? let me know if you helped or i missed someone will update

Josh's 6.5 Kitchen for Kaiser
Hello Everyone,
TPC And I came up with a sweet idea to have a collaborative kitchen thread since him and I have done allot of work on these kitchens. Since we both love doing this and both were noobs at this not too long ago, we figured it would be cool to help out and contribute learning more peeps on becoming chefs.
Step 1: Download kitchen:
21232 6.5 Light build HERE
Step 2: Extract it
You will see the rom structure:
EXT is were all your extra packages and app you want to add will go.
OEM is essential usually device specific items are.
ROM is your xip structure
SYS is your Windows build core items are.
"go ahead and poke around "
More to come soon.

TPC-Joshkoss WM 6.1 21046 complete kitchen with instructions
Part One---COOKING YOUR BASIC ROM
1--Download TPC-Joshkoss 6.1 21046 kitchen HERE
2--extract kitchen to your root drive(ex. C:/kitchen)
3--inside you will see some folders and some .bat files...will look like this
notice the folders highlighted in yellow...those are where all your ROM files are located
SYS= all your main system files, microsolft office, welcome center, etc.
ROM= your xip structure
OEM= some apps inside but mostly device specific drivers ect.
EXT= folder where pretty much all of your applications, utilities, games, manilla, etc. will be stored in ext rom pkgs
4--some advice on editing these folders....leave your SYS and ROM folder alone unless you are an advance user(noobs do not touch). you may add packages to your OEM folder(not this time later) but do not delete any of the files that are in there now. you may also add or delete packages in EXT folder as well, but in both cases files must be in correct format(another lesson)
5--notice the file build_rom.bat in kitchen folder....this is the file you will run to create you rom this is a batch file that tells the other tools in kitchen what to do. if you are using windows vista(maybe even xp) you need to run this file from command line. the easiest way to do this is to go to main kitchen folder in room kitchen(ex. c:/kitchen), hold down the "shift" key and right click on it....you will see the option "open command window here". click on that and a black box will pop up with this text in it... C:/TPC_KITCHEN_6.120146. after this you need to enter this text build_rom.bat this tells windows to open your kitchen(see pic)
6--so whatta ya say we go ahead and cook our first rom so you have completed the above steps, now press enter...kitchen screen will pop up and will say press any key continue, do that and you will see this
for now we will just worry about one of two options....LZX or XPR compression. we will save UPX for a later lesson as all base files in EXT folder are already compressed. if you press option "1" your ROM will be compressed with LZX algorithm, which will give you 10-15% more free storage but takes longer to cook and is optional. if you press option "2" your rom will be compressed with XPR compression, this is the default compression most ROMS are cooked with. choose whichever option you want and press enter.....YOUR ROM IS NOW COOKING
7--let kitchen cook untill all steps are completed then open your kitchen folder and go to the FLASH folder and open it up.....you will see this
CONGRATULATIONS.....YOU HAVE JUST COOKED YOUR FIRST ROM!
hopefully you have flashed a rom before you are trying to cook one so you know what to do from here....click on KaiserCustomRUU.exe and follow instructions to flash your new rom.
Part Two--CUSTOMIZING YOUR BASIC ROM WITH EXT PKGS
note--there are two ways you can add pkgs to your rom, either use some that are already made or you can create your own with tools...this section is for using EXT pkgs that have already been made.
1--go to THIS link and you will see some files i have uploaded for the EXT packages, download both packages and save on your pc/extract where ever is convient for you. we will use iolite ext packages folder for example in this lesson.
2--open iolite_external_packages folder and you will see another folder inside named the same thing, click on that folder and you will see a huge list of files...these are all EXT packages from iolite dump will look like this
3--now go to your kitchen folder and click on EXT folder....you will see one folder inside...BASE, open this folder and it will look like this(see pic)....this is where your new EXT pkgs from iolite dump will be placed
note--i like to set folders side by side on my desktop and compare what packages i have in my current kitchen folder with new packages in iolite folder and decide which ones i want to replace/delete(see pic)
4--now for the fun part after you have decided which packages you want to add to your rom from the iolite folder, right click on one and click on "copy". now go to your kitchen "base" folder and right click and then click "paste"....its that simple! you have now added a new pkg to your ROM
5--THIS IS VERY IMPORTANT...if you try this and your kitchen crashes when trying to cook, then the structures of your files are wrong. ALL FILES IN EXT FOLDER MUST HAVE THIS STRUCTURE.....EXT/BASE/YOUREXTPKGS ....OR YOUR KITCHEN WILL CRASH.
6--now cook your rom again and experiment with different pkgs/configurations till you find the one that fits you the best....then start enjoying your new ROM!

SYS_XIP Ports
SYS XIP ports:
21051_SYS_XIP 6.1 ported by TPC
21275_SYS_XIP
21728_SYS_XIP
RTM_EMulator Dump for 6.5 "unedited"
RTM_21234_SYS_XIP
21806_SYS_XIP
21812_SYS_XIP
21820_SYS_XIP
from TPC:
21815_sys_xip
21820_sys_xip
23001_sys_xip
23003_sys_xip
23004_sys_xip
21921_sys_xip
21925_sys_xip
23007_Public_Kitchen
23008_Public_Kitchen
23009_Public_Kitchen
Click to expand...
Click to collapse

wm 6.1 sys-xip ports
21051_sys_xip

and 6 is mine
Cuz i'm fat and greedy

haha awesome guys. I hope u were done reserving posts
can't wait for the kitchen thread

yeah i think ive been screwing around with roms long enuff that i should probly learn how to cook em...i think i know what makes a good rom, and now with tpc doing it (even with the cheese factored in) i'm kinda inspired...time is my x factor, but since most of my work time is wasted on the computer anyway, i guess i could use it to chef it up...

thedrizzle said:
yeah i think ive been screwing around with roms long enuff that i should probly learn how to cook em...i think i know what makes a good rom, and now with tpc doing it (even with the cheese factored in) i'm kinda inspired...time is my x factor, but since most of my work time is wasted on the computer anyway, i guess i could use it to chef it up...
Click to expand...
Click to collapse
yeah i work from home office so i get to squeeze in a rom or two every now n then you should give it a try driz, just takes some hard work and alot of patience. with this kitchen you will have it alot easier than i did in the respect that all the kitchens that i had to work with were good kitchens, just based on older builds and outdated tools. the kitchen i posted is base to my v4 and v5, just need to add some apps and tweak on it a lil.

I appreciate all you have done. I would like to cook a rom by myself. Now it is simple to follow your action. Thanks very much. I hope to explain more ditail to help all newer to do this. Thanks......

Cool thanks guys.
If I use one of the other great roms here and just remove a couple of programs (i.e. windows live or messenger), what are the chances that I screw up the rom?
I just don't want to flash a bad rom and brick my phone.

tilt4life2 said:
Cool thanks guys.
If I use one of the other great roms here and just remove a couple of programs (i.e. windows live or messenger), what are the chances that I screw up the rom?
I just don't want to flash a bad rom and brick my phone.
Click to expand...
Click to collapse
i dont think you have to worry about bricking your phone, worst that can happen is that it wont boot and you have to put in bootloader mode to reflash with good rom. as far as windows live and windows messenger, they are already removed so you dont have to worry with those i am going to write tutorial in the morning for next step customization and will go in detail about things to add/delete. the roms are pretty naked so gather you up some cabs that you want to put in your rom and tomorrow you can learn how to put them in your new rom

twopumpchump said:
i dont think you have to worry about bricking your phone, worst that can happen is that it wont boot and you have to put in bootloader mode to reflash with good rom. as far as windows live and windows messenger, they are already removed so you dont have to worry with those i am going to write tutorial in the morning for next step customization and will go in detail about things to add/delete. the roms are pretty naked so gather you up some cabs that you want to put in your rom and tomorrow you can learn how to put them in your new rom
Click to expand...
Click to collapse
Well, first thing I have to do is flash your new rom and give that monster a run.
I will keep reading this thread in my free time to learn more, but I won't be able to start cooking until Tuesday once I get this paper for my journal competition mailed out. I hate law school. The work never ends even after finals.

Awesome Guys!!!
With this toolset, even a noob like me, can cook.
I can't help but notice a sudden urge comin' up.
Will definately play around with this and I'm looking forward to your customization part.
Josh and TPC - Thx for your great contribution - makes me remember what I was doin' here

looks like learning easy way to cook ...subscribing to this thread thanks to TPC and Josh

suppose we want to cook registry edits into the rom(like cleartype on landscape, etc), how would we go about doing that?

himalayasplaya said:
suppose we want to cook registry edits into the rom(like cleartype on landscape, etc), how would we go about doing that?
Click to expand...
Click to collapse
I have an entire "Device" in EXT dedicated to registry tweaks, so if I need to add one, for example, I'd just make a folder called ClearType, then app.reg in that, and put the registry in it
actually, I have one of those folders, it's attached

mbarvian said:
I have an entire "Device" in EXT dedicated to registry tweaks, so if I need to add one, for example, I'd just make a folder called ClearType, then app.reg in that, and put the registry in it
actually, I have one of those folders, it's attached
Click to expand...
Click to collapse
thanks mb yeah i plan on explaining how to do this in detail in next lesson...i just now woke up need to clear my head a lil before i get started lol. there is also a program called oemizer that i think would be easy way for noobs to make pkgs for reg entries will put link in my tools folder on server later.

twopumpchump said:
thanks mb yeah i plan on explaining how to do this in detail in next lesson...i just now woke up need to clear my head a lil before i get started lol. there is also a program called oemizer that i think would be easy way for noobs to make pkgs for reg entries will put link in my tools folder on server later.
Click to expand...
Click to collapse
no prob man, looking forward to the next lesson
yes, but then wouldn't they have to convert the package after that?
which might not work with oem2ext and oemizer, I don't know if the two are compatible

mbarvian said:
no prob man, looking forward to the next lesson
yes, but then wouldn't they have to convert the package after that?
which might not work with oem2ext and oemizer, I don't know if the two are compatible
Click to expand...
Click to collapse
when i started out i used oemizer with extpackagebuilder all the time with success great way to customize your rom! can also choose from alot of built in tweaks in oemizer as well. if anybody wants to go ahead and try it, HERE is the link

[APP] Subversion

All,
Please find the attached native Windows RT binaries for Subversion 1.8.0
Also feel free to give the binaries a try by checking out the following:
svn checkout http://windowsrtdev.googlecode.com/svn/trunk/ windowsrtdev-read-only
I'll try to keep the SVN repo up to date. I'm happy to take suggestions for a layout/tree structure to keep things easy to manage for my fellow XDA members!
Cheers!
EDIT: fixed missing binaries... sorry! please re-download 'rel2'.

That would be an incredibly useful tool to a software developer on RT. Nice one :good:

SixSixSevenSeven said:
That would be an incredibly useful tool to a software developer on RT. Nice one :good:
Click to expand...
Click to collapse
I'm hoping it can be more than that.
It would be nice to get to a point where we can maybe leverage svn as a software repo and provide easy access to app ports, libs, etc. Also would make getting updates much easier. If we could wrap this and the jailbreak with some batch/perl scripts we could have a completely functioning "app store" (so to speak) to help improve the access to Windows RT desktop apps.
Cheers!

Yeah I can definitely see svn contributing towards a "homebrew" store.

Hello, thanks for the port! We use subversion for several things at work, so this could be very useful. I haven't been able to get it to run though.
I extracted the archive (using Ark on linux instead of 7zip), and copied the files to C:\Bin\subversion_1.8.0_arm\
Running svnversion.exe I get an error "the program can't start because libapr-1.dll is missing...". So I renamed libapr.dll to libapr-1.dll. I then get a similar message "libaprutil-1.dll is missing...". Renamed libaptutil.dll to libaprutil-1.dll. Then I got a message that libapr.dll is missing, so I made a copy of the renamed libapr-1.dll back to libapr.dll. Then I get a very different message:
"The procedure entry point apt_atomic_xchgptr could not be located in the dynamic link library C:\Bin\subversion_1.8.0_arm\libsvn_subr-1.dll." This dll does exist in this location.
svn.exe gives an error "The procedure entry point apr_array_clear could not be located in the dynamic link library C:\Bin\subversion_1.8.0_arm\libsvn_fs-1.dll".
Other exes give other similar errors which I can copy down if it'd help. I figured svnversion.exe and svn.exe would be good examples.
I'm not sure what I'm doing wrong. I thought it'd be fairly straightforward, but maybe I'm missing something obvious.
Thanks!

domboy said:
Hello, thanks for the port! We use subversion for several things at work, so this could be very useful. I haven't been able to get it to run though.
I extracted the archive (using Ark on linux instead of 7zip), and copied the files to C:\Bin\subversion_1.8.0_arm\
Running svnversion.exe I get an error "the program can't start because libapr-1.dll is missing...". So I renamed libapr.dll to libapr-1.dll. I then get a similar message "libaprutil-1.dll is missing...". Renamed libaptutil.dll to libaprutil-1.dll. Then I got a message that libapr.dll is missing, so I made a copy of the renamed libapr-1.dll back to libapr.dll. Then I get a very different message:
"The procedure entry point apt_atomic_xchgptr could not be located in the dynamic link library C:\Bin\subversion_1.8.0_arm\libsvn_subr-1.dll." This dll does exist in this location.
svn.exe gives an error "The procedure entry point apr_array_clear could not be located in the dynamic link library C:\Bin\subversion_1.8.0_arm\libsvn_fs-1.dll".
Other exes give other similar errors which I can copy down if it'd help. I figured svnversion.exe and svn.exe would be good examples.
I'm not sure what I'm doing wrong. I thought it'd be fairly straightforward, but maybe I'm missing something obvious.
Thanks!
Click to expand...
Click to collapse
My bad. Download rel2.. should be fixed.

bfosterjr said:
My bad. Download rel2.. should be fixed.
Click to expand...
Click to collapse
Awesome, thanks for fixing it so quickly!