Hey,
I want to cab packages and reg files so they can install.Is there a way to do this.Im trying to make addons pack for lite versions of roms and make some kind of salad bar for users to choose from when they flash a rom.Im doing this in conjunction with an addins installer made for extended roms but tweaking it to read cabs from microdrive/storage card.Any help and tips appreciated.
Have a look at Wince Cab Manager; it can do what you're looking for and a lot more.
it's kinda wa I need but does'nt do much for oem packages.Any more suggestions?
If you want for OEMs, get a program on here called Cabs2oem or simply use the tool from _Alex_'s kitchen.
I went on the wiki to get alex's rom kitchen, which tool converts oems to cabs, I've seen a cab extractor to oem tho?
thanks for your help.
It's called "packages creator 5.4."
Related
Ok I need a few opinions.
I am wanting to find out who has the easy and the best Kitchen.
I want to take a "nk.nbf" and edit it.
I want to remove packages that are in there and add others.
I have "TNT.1933_Professional___HTC_Home_Wizard" Rom I have tryed to use "HyperCore Kitchen" but could not get the rom to work.
I took the original ron, extracted it and then re made it (With out changing anything) to see if I was doing it the correct way, but after I loaded the rom it locks up after it posts the ver screen.
Is this the rom I am using or the way I am using it. Or is it the kitchen.
I really want to learn to make my own. So if some one has time to walk me though it I would be ever so greatfull.
I have searched and search the site and most walkthroughs apply to old vers of kitchens. I still tryed to follow them but cant get a rom to work. I know I must be missing something somewhere.
- Albert
I don't think you have the .rgu's
If the chef deletes the .rgu files you can't rebuild his rom the easy way. You should either seek a rom that has all the files or ask the maker to share them.
Ok thank you
Yep, a lot of the roms have the .rgu files removed. You can use my cooking pack or I recall that there was a Lite version of TNT that was meant for cooking that would still ahve the .rgu files (but then you'll have to get the packages to put in it what you want). Then of course there is theloon's kitchen stuff which has tons of packages and all.
XDA Mobile 6 Release 5 Cooking Pack
Build your own flavor of XM6r5
By popular demand, I'm releasing the XDA Mobile 6 Release 5 (XM6r5) Cooking Pack. Basically, this is just a the ROM / SYS / OEM folders that I used to build XM6r4. Those so inclined, can download this and build their own flavor of XM6r5 and customize it to their heart's content. If you are looking for the already cooked XM6r5 then go to this thread.
NOTE: This is NOT a Kitchen, but is "guts" of the kitchen. I personally used anichillus' HyperCore Kitchen to build XM6r5, and recommend this kitchen. But since most all of the Wizard kitchens I've seen are almost all alike, these folders will probably work in the majority with only minor changes.
How to Use the Cooking Pack
First you need to download a kitchen and install it per the instructions for that kitchen. NOTE: This thread is NOT for supporting kitchens, and is NOT for general questions on cooking. It will be for the usage of this Kitchen pack.
After you get your kitchen setup, then download the XM6r5 Cooking Pack. Unzip the file and place the ROM, SYS, and OEM folders under the kitchen directory where it belongs (for HyperCore, these folders will go under the Build folder).
At this point you are basically ready to cook.
Where are the options.xml files???
In XM6r5, I only have options.xml files in the OEM packages that are optional between the Full and the Lite versions of XM6r5. By doing it this way, I was easily able to build a full version, then go back and build a Lite version but just unchecking everything. For me, rather than having a BuildOS that is loaded with lots of options, I personally prefer to have an OEM directory which (in most cases) is what is going into the rom, and another directory for things that won't go into the rom (OEM-Hold or somesuch. Call it what you want). Then all I do is take OEM packages I don't want in the ROM from the OEM folder and move them to the OEM-Hold folder. By doing this, they won't be part of the rom (and you don't have to deal with checking and unchecking things in BuildOS). If you don't like this style, then feel free to create options.xml files for each of the OEM packages and you can then check and uncheck to your heart's content.
If you want to add things to the rom, you'll need to create the OEM packages and drop those in the OEM folder. But thats beyond the scope of this thread. Please see Cooking and Kitchen threads on how to build packages.
Extras Folder
Also included in this Cooking Pack is an Extras folder. In here I've placed the OEM package for SuperDoku, and I've placed the NETCF 2.0 SP2 folder. To build SuperDoku into your rom, just drop that folder into the OEM folder. To build with NETCF 2.0 SP2 instead of the 3.5 thats in XM6r5, first copy the NETCF folder out of the SYS folder and put it in the Extras folder (rename it to NETCF3.5 or something). Then copy the NETCF folder in the Extras area into the SYS folder. NOTE: The only reason to do this is if you have an app that won't work with NETCF 3.5 (Pocket eSword is one example). But since NETCF 3.5 is the direction Microsoft is going, for future compatibility you should stick with 3.5 in most cases.
Splash Screens
Attached to this post are the BMP and PNG files used for the splash screens on XM6r5. While the graphics are not mine originally (I've found them here in the forums but asked permission for their use) some modifications are by me. If you are using HyperCore, there are tools for building splash screens in that kitchen.
NOTE: For me, the first splash screen (the so called HTC Logo, which I used the Cylon image for) tends to be the trickiest one. If the file size and complexity of the graphic isn't just right, the screen will not show up properly. If you are trying to build your own htc logo splash screen and having problems, use a graphic editor to convert it from BMP to GIF. Then close the image completely (important) and then reopen it, and then convert the GIF back to BMP. This will sometimes work. If not, then convert the image to a jpg and increase the compression level to be below 50% (the image will start to get grainy and not look as good so you'll have to play around with this). Then close the image and then reopen the jpg then convert it back to a BMP and try again.
Final Notes
This is an exact copy of the folders I used in building XM6r5. I have not upgraded or changed anything (so the same bugs and features in the built version will be in this cooking pack). A lot of the pieces originated from mattk_r and theloon's kitchen work for the 318 ROM. Then I've made changes to those bases to create the XM6 series. Most OEM folders found in theloon's kitchen will probably work with this cooking pack (but no guarantees).
Official Download Sites for XM6r5 Cooking Pack
12-Feb-2009: New Download links (Same file, just new places to pull it since the old location went away)
FileFactory.com
FileDropper.com
FileSavr.com
Happy Cooking!
.
Reserved for future use
Reserving 1 more...
I've been waiting for this since you let us know it was coming. I'm gonna use this as my base to teach myself how to cook
Your ROMS are always great, but there are usually a few things I don't use so I want to try taking them out.
THanks again.
Thanks a lot Mfrazz i rely on you enough to trust you have a good base.
I've been so busy Working on the ELF thread i never got to cook my own Wizard Ro.
This way you are saving me a lot of headaches finding a nice Base.
Only important thing is that AD2P is working, but i'll know that in ten minutes instead of reading your whole ROM thread.
Cheerz.
Download link is not working. I know, link can't be active forever, and I shouldn't be so slow and conservative (still on XM6r2). Can you upload this file somewhere else or mailed to me?
Thanks,
Another one - download link not working for me either; please reupload!!
Thanks...
I need this
The download link isn't working. Can anyone re-upload or send me it? Thanks!
I'll try to look for backups of this and see about uploading it to a new location... Didn't realize the links had died. Sorry about that.
[EDIT] I found the file in my backups. I'm uploading to a couple of file sharing services now. Will update the first post and put a reply in here when its complete.
Uploaded the original file to 3 new locations. First post has been updated. Please note: This is the original cooking pack. I have not updated anything in it (and don't plan on updating it... Sorry). But I hope this helps those that have asked for this to be reuploaded...
My new brilliant idea since I am having trouble getting any of my cooked roms to work; is there a painless method to create .cabs from the packages contained in the kaiser kitchen?
Most, if not all packages are readily available in CAB format.
get WinCE Cab Manager..
it's pretty easy.
Nerdgurl said:
My new brilliant idea since I am having trouble getting any of my cooked roms to work; is there a painless method to create .cabs from the packages contained in the kaiser kitchen?
Click to expand...
Click to collapse
Get them here, [url="http://www.cinetsystems.com/xda/index.php?path=Kaiser+Cab+Collections/" the largest cabs collections from Dutty.
If you still can find what you want, let me know.
HELLO ALL AT XDA....
I HAVE RECENTLY BEEN WORKING ON SOME KAISER ROMS USING ALEXS COOKING KIT AND OEM PACKAGES. I HAVE READ ALL OF THE FORUMS I COULD FIND ON ANYTHING RELEVANT TO KAISER ROM COOKNIG, BUT WHHENEVER I USE AN OEM PKG FROM ALEXS KIT, OR I HAVE CREATED LOTS OF MY OWN AS WELL, I CANNOT GET THEM TO INSTALL TO THE SPECIFIED DIRECTORY/START MENU FOLDERS!
I HAVE FIGURED OUT HOW TO CHANGE THE LOCATION OF THE PKGS IN THE PKG SELECTOR IN THE ROM BUILDER BY EDITING THE XML FILE (OPTION.
xml), BUT OF COURSE THIS IS ONLY FOR THE "GROUP" THAT THE PKG SHOWS UP IN ON THE PKG SELECTOR. WHEN I CREATE A PKG FROM A .CAB FILE OR OPEN AND MODIFY ONE OF ALEXS PKGS, I SPECIFY THE FOLDER I WANT THE EXE ICON IN, AND APPLY THE SEETINGS (IN THE INITFLASHES BOX), AND IT SHOWS IT AS BEING THERE, BUT NO GO WHEN I COOK THE PKG INTO MY ROM. WHEN I FLASH IT AND GO TO FIND THE APP, ALL OF THE START MENU FOLDERS ARE THERE THAT I SPECIFIED, BUT ALL THE APPS/EXE'S SHOW UP IN THE /WINDOWS DIR, AND THEY WORK IF YOU SELECT THEM FROM THERE....
ANY IDEAS OR SUGGESTIONS? I AM VERY FAMILIAR WITH FLASHING AND SOME MODERATE MODDING, BUT AS FOR ROM COOKING I AM PRETTY NEW AT IT. ALL OF MY ROMS SO FAR HAVE BEE VERY NICE AND STABLE, BUT THIS IS PROBABLY MY BIGGEST ISSUE.
ANY HELP WOULD BE APPRECIATED!!! THANKS IN ADVANCE.
BTW, IF ANYONE NEEDS ANY FURTHER DETAILS OR SCREEN SHOTS ETC... I WOULD BE GLAD TO PROVIDE ANY EXTRA INFO IF ANYONE HAS THE TIME TO HELP ME....
Hello,
I dumped the factory ROM of my Kaiser (part00.raw, part01.raw... ).
I would want to extract from it some applications that are useful for me, and reinstall them on my new ROM (Schap 4.31).
So, is there a tutorial about a method to do CAB file ?
I don't want to use ROM cooking for now.
Sorry of my questions, I'm a novice !
;-)
Thanks in advance.
Pascal
What you have is simply raw data. The eaiser thing to do wold have been to pull the cabs out of windows FIRST, then just install them. If you want to make cabs out of the OEM's just using raw data, I hope you have a lot of time on your hands, particularly if you've never done this.
The first step for constructing cabs out of OEM raw data is to reconstruct the rom. I suggest starting with this excelent guide by jcespi2005. SEE HERE: http://forum.xda-developers.com/showthread.php?t=337066
Once you've recontructed the data you'll need to pull out all the OEM data including the .rgu & .dsm files. You'll then need to create an initiaflash file with the location references for the contents of the program.
Once you've done all that you can think about making the OEM into a cab.
It' much easier (if the proggies your looking for were part of cutomization & were originally cab files) to find the cab or ask people with that original rom to post the cab.
If they did indeed start as cab files you can find them in windows already as cabs. If you're trying to cook your own rom & want the programs as an OEM package or if they were already an OEM package, you'll need to reconstruct, extract, & then compile for a cab.
If you tell me what proggie you want I can most likely point you to it as a cab already.
Visual Studio has a template for it.