Database Info

ROM Kitchen - SYS and OEM interchangeable?

Sorry if this is another noobish question, but since I've been experimenting with cooking in the CORE Kitchen lately, I was wondering, are the files in the SYS and OEM parts of the kitchen interchangeable? I've been recently trying to use the ingenetic's rom to install the basic options that I would like (I don't use bt, so most of those features aren't needed), and noticed that some information appears to be in the SYS folder by default when dumping the rom.
an example would be something like the comm manager, which appears to already have some files in the SYS folder, but there was an htc option to click off on build os, since i think the oem package had it listed (part of the oem package download in the same thread as the kitchen). also the files for office appear to be pre-existing in the sys folder, so was wondering if the build os checkbox meant anything...
I've tried cooking roms with the options checked off and on and haven't noticed any differences, because the roms usually ended up being built and flashable, but the roms always came out screwed up. (office shortcuts would not appear, although they could be run from the \windows directory or an option to put the date information on 1 line didn't work).
I'll probably try to figure out how to use faria's kitchen and try to make the same mods, since it looks like the cookers themselves seem to have been using that kitchen for their original builds...

One thing you will find out is all the kitchens (at the lowest levels) are basically the same since they all use the same set of tools. Where the differences come is just layouts (and even then, they are still all pretty close. Core Kitchen is probably the one that is the most different, and thats just because its been laid out very logically (and not just hacked together IMO) and scripts and shortcuts setup to make it all look and feel like a nice organized set of tools. I've been using Core Kitchen mainly since Crossbow Reloaded 1.7 and I really like the layout and all. But definetly try other kitchens so you can see how they all came from the same roots (and you start to realize how this all fits together).
As for OEM and SYS... Well SYS is supposed to be what the base rom is. And OEM is the add on packages. But different cookers do things differently. I'll admit that I get sloppy sometimes and will drag stuff out of SYS and into OEM if I'm completely changing it, or sometime I edit stuff directly in SYS and maybe make rgu or initflashfile stuff for it over in OEM (so yeah, anyone dumping my roms may find some odd things in odd places. Sorry, it makes sense for me at the time I worked on it, and some of it is tricks / techniques that I've seen in Faria's stuff).
So yeah, I guess you could say OEM and SYS are interchangable. In my ROM Windows LIve stuff is in OEM since it was brought from elsewhere (but then Office was brought from elsewhere but I left it in SYS as I had issues when I tried to move it).
Good luck!

lol...coincidentally the base roms i was using look like they were from you...both your tweaked version of the base wm6 from ingenetics and xm6. maybe that's what causing all these error messages to popup when i try to buildos. says it already has files here and there.
if you have experience with core kitchen, would you know if i can still flash the file that is created, even if the error message pops up? the error that i usually get in buildos is that the file already exist elsewhere (though i need to play with a bit more to figure why, since i can't find the file in more than one location when i do a search). not sure if buildos finishes its build or it just stops (the included tutorial says to try to fix the error and not continue flashing...but just curious).
anyway, it looks like there was another version of the base ingenetics rom in the forum posting, so I'm gonna try tossing that into the core kitchen to see if i get the same errors in trying to cook it.
thx for the comments.

First of all, i want to say thanks mfrazzz for the nice words...i apreciate it !
Second ...if it gives you any error then the product is corrupted, that is very easy to understand...Because when Build OS encountered an error it stopped and won't go trough with the whole process. So if any errors, abort and check the log and fix what can be fixed.

monkey_knight said:
lol...coincidentally the base roms i was using look like they were from you...both your tweaked version of the base wm6 from ingenetics and xm6. maybe that's what causing all these error messages to popup when i try to buildos. says it already has files here and there.
Click to expand...
Click to collapse
Yeah, if it says that the file is already there, then you have to stop and find out where the duplicates are. Most likely there are files in OEM and in SYS with the same name. You then have to figure out which you want and remove the other (or rename it and then in initflashfile.txt change the name back to what you want when you move it to a different directory).
But if you get errors, (duplicate files, hive not created) or the like, you have to stop! You can't move on as things didn't complete.
If you want a clean version, then use the Ingenetics base and the packages that matt put together. Thats all made to work together. If you start with my base, then you have to keep moving forward from there, and I threw XM6 and the first version of Ingenetics together in a matter of hours so they are not laid out very well. Part of what I want to do with this next XM6 is take my time and do this one right (but I was trying to get that base out to the masses and get a better working Crossbow Reloaded 1.7 type rom on it, and wasn't thinking of people using it to start their own cooking with either of them ).

Deleted

i've deleted this, because there is another thread which give you full informations and include this thread, check: http://forum.xda-developers.com/showthread.php?t=388666
please admin delete this thread

great share its right much appreciated here

rocking! thanx! I might just use this thing afterall. one question: is the size of the nb0 the same as the original 5.1 for the wizard? I found that using the 57mb nbo didn't allow me to have as much room, while not increasing storage space. I believe the original nb0 is 58.+ mb. which allows for almost 2mb more for things like live and MSVC.
Thanx for porting and posting the kitchen. if I use it for the next one the creds will for sure be yours.

Thansk a lot!
You rock Itsright!
Finally what we were expecting from your hands!
Thanks for sharing your [email protected]!
Now, let's play!
Take care!

Awesome.
Once I get to play with and test this I will consider posting my "latest and greatest"

its right said:
hi guys,
many of users asked me before to release my kitchen, then i said i will release for own using not for public, so i decided to remove all my stuff (to save my work) and share what i did for xip ported (especially) and driver modules are relocated all of these at the best ways (no hacking at all).
you will find xip folder in ROM, all of these are useless, what ever you change will not effect , so just play with OEM and SYS.
if all happy with this thing, i will continue porting and sharing.
Download: http://rapidshare.com/files/110524485/19209_Kitchen_wizard.rar
please if you want to use, give some credits.
enjoy.
Click to expand...
Click to collapse
It's Right,
Great Job!!
Now this definitely deserves a sticky guys! I will try your newest rom out and then I will look into using this for my own special brand.
Thank you so much,

Damn!
This thing is FREAKING HUGE!
I had a whole bunch of stuff that I got into the 19199 port I've been using as a base, but I got in IMMEDIATE trouble with this one as soon as I started cooking.
The 64MB wall is made out of granite, and you just can't get beyond it. Well, I've got a problem trying to stay under it now.
What accounts for these huge changes? Were the '199 version's components compressed or something where this one is not?
I don't know why the difference is so large, but it is......

Ok, I'll update that comment - There has to be some sort of duplication of files and space consumed in this one.
I stripped damn near everything I usually stick in the ROM - I mean everything - and I still wound up with a file that was too big and wouldn't flash!
I even went so far as to go back and "squeeze" things that hadn't been squeezed in the base ROM in an attempt to make it fit, and still no-go.
To give you an idea of what's in there that fails, I literally have the Kaiser Comm MAnager, a little BT utility (about 20kb), Total Commander, MMS, 1 Calc and a couple of other small apps in the ROM. It builds far too big and won't flash.
If this is the base that you're using for the TNT series there's no way in hell you could possibly get that set of apps in there unless there's just a huge amount of cruft being left in the kitchen.
Would love to work with it but can't with this as a base.... almost nothing will fit

what is the nb0 size? I use a 19209=with what used to be 57mb then used a 59mb from Faria's kitchen... i kept getting the imfg error if I added too much stuff, so I got rid of WML to make room for stuff. You can also upx the entertainmet (games) and you can change the graphics in photoshop so they take up less space.
I also had errors when I was screwing around with some reg settings... so maybe that could be an issue with some packages.
try to add one package at a time to see which package is screwing things up..
I haven't downloaded it yet. ;aybe when I get home.

I'm in a middle of flashing my first real tentative...
I was playing around and after adding my stuff, I got 61MB which is really big
I do not know about duplication but with a OS near to 60mb, maybe it's coming with most stuff inside!
I'm now trying with much less apps. Just what I consider essential. Let's see...
I also tried to dump and then repack a new NB but didn't have luck...
still on the road....
cheers

Can anybody post a mirror for this kitchen? Rapidshare being gay today.....

so I downloaded it, and have to say I don't have much use for it. maybe backup sys files in case I screw something up. the NB0 is 57mb which meand you can not cram much stuff in it. it will build, but not flash well. I would recomend using the original nb0 or Faria's 318 which is about 2 mb bigger.

S.V.I said:
so I downloaded it, and have to say I don't have much use for it. maybe backup sys files in case I screw something up. the NB0 is 57mb which meand you can not cram much stuff in it. it will build, but not flash well. I would recomend using the original nb0 or Faria's 318 which is about 2 mb bigger.
Click to expand...
Click to collapse
amm... i think the tools chefs are using are not suitable for the nb file.
amm... i will think again to release the whole kitchen i used, the nb file i edited to give the advantages of bepe tools for porting xip and locating modules without any action by the chef, just copy and past then cook with no worries about locating and porting.
if i decided to release that, i need some time to give a good guide for the chefs .

Wise man....
By doing this way, chances to have good final results increases!
Take your time!
its right said:
amm... i think the tools chefs are using are not suitable for the nb file.
amm... i will think again to release the whole kitchen i used, the nb file i edited to give the advantages of bepe tools for porting xip and locating modules without any action by the chef, just copy and past then cook with no worries about locating and porting.
if i decided to release that, i need some time to give a good guide for the chefs .
Click to expand...
Click to collapse

i will open new thread to give all details with the kitchen i'm using, but i need some time .

Some cooking questions

I have a few questions about this cooking stuff. Yes I searched and watched the videos. Maybe I can't find the proper wording for the search to work for me. But if I'm in the clear in that department, then maybe I can get some help.
1. If I have a radio that is an NBH file, the BuildOs wants an NB file. How do I convert?
2. How would I get someone else'e rom, say the Hyperdragon roms, and get it to the oem, sys and rom folder. I already did the dump and I end up with the temp directory that has some stuff like what is in the oem, sys, and rom folders. Am I missing something?
3. Is there any easy way to find one of the Packages after doing a dump? Say i am looking for the registry entries in the Hyperdragon roms, where would those be and how would I get them?
I have the basic idea of how to do this stuff, just need some assistance in the stuff that I feel was not covered very well. I already made a few roms with Manilla and without and some with HTC home. They all work with some bugs here and there. I have never been much of a person on reading on how to do stuff, just tell the "simple" explanation and I experiment from there.
Any help, please!

Hi there I don't know if this thread really belongs here (mods will tell ) but here are some answers to your question:
1/ use the search function... ok, not SO funny
1 bis/ use NBH extract http://forum.xda-developers.com/showthread.php?t=289830
2/ Download a good Kaiser kitchen (Alex's or the one on PPCKitchen) and follow the first steps that will extract your OEM/SYS folders
3/ Registry entries can be found all the place, under varied forms: basically, .rgu files, initflashfile.dat, and .provxml files. You'll have to take some (like in a lot) time to figure out which modifies a given reg key
Hope this shed some light
Best regards

Ok, I was missing the Extraction tool for the NBH files.
I thought I was right on the reg files but I was thinking, maybe even hoping, for an easier route but I guess not.
I have everything I could find on the kitchen stuff and have tons of packages and cabs. Now, like you said, time to spend a lot of time experimenting.
But again, where do I get a radio*.nb file from?

whitehooptie said:
Ok, I was missing the Extraction tool for the NBH files.
I thought I was right on the reg files but I was thinking, maybe even hoping, for an easier route but I guess not.
I have everything I could find on the kitchen stuff and have tons of packages and cabs. Now, like you said, time to spend a lot of time experimenting.
But again, where do I get a radio*.nb file from?
Click to expand...
Click to collapse
You have download the radio you want, and extract it using nbh tool.

You'd better not include the radio ROM into your final .nbh package: it will be easier to later test different radio roms without having to reflash the radio in case you flash the main (OS) rom again, and will make your packaged ROM lighter. If you later want to share it, you can still zip your OS and Rasio roms together for people to flash separately...
Remember that the efficiency of a radio ROM is more or less closely tied to your phone service provider, location, Kaiser build, color of your socks and so on... People most often have a prefered radio ROM they'll tend to stick to.
When I cook roms I want to share, I get 3 .nbh ready: one for OS, one for radio, and one for splash, so people can choose to flash whatever they want.

So NBHextract works on everything. Who would've thought. I think maybe I am reading too hard in this. My biggest deal on the radio was I want to make one for myself where I can put my phone back to how it is exactly. If I try a cooked one and need to change a few things then I can load my stuff back on without spening 30 minutes doing it.
Thanks for the answers guys, I appreciate it.

Another question. Is there any other way than flashing to your phone to test these roms? I know microsoft has that "emulator" to try out WM6. Any way to change those files?

Decompile ROM to find out what's inside?

Some ROM chefs post a list of what they have cooked into their roms, some don't. But if I like a certain application/software cooked in and I don't know the name, like for example a battery meter that looks cool, how do I find out what it's called to get a cab of it on my own? This brings me to a point, is there a way to decompile a ROM and get a list of pre-installed/cooked applications, and then from there either find a cab for that particular application or make your own from the ROM you just decompiled? Just wondering, sorry if this has been posted already. Thanks.

Reverse engineering is what we do here in XDA LOL. Anyhow, if you like something, go to explorer and look for file name u think it might be! Its a WAG, but it works, and then go to the link in my sign and search! Good luck.

Yeah well I tried searching for it via explorer, no luck finding it lol. Thanks however. Plus I would want the version number on the app too. Is it possible to decompile a rom and get a list of installed apps? Like the chefs post when they release?

Short answer is yes, as a ROM contains a collection of various packages. Grab any one of the kitchens and give it whirl.

What happens if the rom I want to decompile doesn't have its kitchen released?

Use dumprom, however I think youre best shot is to use the ROM tread and ask there.

kickindrummerkid said:
What happens if the rom I want to decompile doesn't have its kitchen released?
Click to expand...
Click to collapse
No worries, most any kitchen can dump a ROM. ImgfsTools is actually what you seek, but the kitchens paint a bigger picture if you're not already familiar with the cooking process.

Ok so I dumped the rom however, how do I tell out of all the dll's and exe's in "dump_imgfs" folder which one is the battery icon OEM. Also, how do I make a cab out of it?

There isn't going to be a big, flashy "This is the battery monitory" sign.
Your first step would be to guess, based on the names of the files. Something that includes "Bat" and "Mon" is a great candidate. Put your guesses in google and see what you find.
If that doesn't work, you're gonna have to guess based on some other criteria. For example, MS will often set the operating system DLLs to the same date. If that date was preserved when the ROM was cooked, you can eliminate all the OS ones and google the rest.
Now, there's 2 methods that may be a lot easier and get you a faster response:
1. PM/email the author of the ROM and ask. Be polite and thankful, and let them know you appreciate their work.
2. Google "Windows CE Battery Monitor" and look through the results.

I found out by looking up an OEM package for another battery and found out the registry settings for it and went to my registry on my ROM and found out what DLL it pointed to. Then I created a CAB and flashed a new ROM and then installed the CAB and it worked . However, is there any way to edit the DLL and change how it looks? I tried hex editing but that's no luck for a picture.

kickindrummerkid said:
Ok so I dumped the rom however, how do I tell out of all the dll's and exe's in "dump_imgfs" folder which one is the battery icon OEM. Also, how do I make a cab out of it?
Click to expand...
Click to collapse
Now that you have figured out the details. Can you please write step-by-step procedure how new ones in this arena can accomplish this?

convert visual SYS files to work with old style

How do you use sys files that are designed for visual kitchens with the non visual buildos? I tried moving all the folders into one directory and buildos finishes but the rom doesn't boot... anyone? thanks!

I dunno, but you'll need all of the dsm's to begin with. If you don't have them, you might as well not even try. There's a folder in the visual kitchens with dependencies; maybe those are the dsm's that are removed from the original packages. It's just a guess.
Why not just use the newer kitchens? Or, wait until Da_G finishes with all of his kitchen tools. I bet he'll have everything figured out.
Edit: Or, check this post. It will probably help you out.

Thanks for the info! Perhaps I should have also asked what the differences were! I will check that post. About newer kitchens.. I guess I am old-fashioned. I will have to convert one day but it's like I am with cars, I require a standard transmission - one day I will have to give in a drive automatic ...

raidzero said:
Thanks for the info! Perhaps I should have also asked what the differences were! I will check that post. About newer kitchens.. I guess I am old-fashioned. I will have to convert one day but it's like I am with cars, I require a standard transmission - one day I will have to give in a drive automatic ...
Click to expand...
Click to collapse
Automatic sucks, don't go there, lol.
I started out with the older style kitchens and was reluctant to change, but it's really not that hard. You'll need to convert your packages, but there's a simple tool for doing it put together by Kraize. The kitchen itself works better; I used to have the older style one crash all the time. Just suck it up and do it.

more and more kitchens are showing up as visual. I have groove rom 5 kitchen but just could not figure it out, my rom would not boot. maybe I will swap my question around and learn to convert old style kitchens to new. I do kinda like the no duplicate file error... and the nbh's they produce do seem to be smaller. not sure though as I have never made a rom that will boot!