Related
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,
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...
I've started trying my hand at cooking some of my own ROMs over the past couple of days and have gotten confused on some stuff. I've been following the both the Wiki's and the threads on cooking but none of them seem to point it out so here goes.
1) I'm trying to use a base ROM such as this one or this one and have been successful in both dumping them and cooking them using Alex's latest revision of KaiserKitchen and his apps. When I am including the os.nbh file during the cooking process, should it be the one that comes up in the main KaiserKitchen folder or the one that is located in the BASEROM folder? Is either of those files just the OS part of the ROM without all the applications and such?
2) After cooking and successfully flashing either of the two before mentioned ROMs I will always get the auto-installer which occurs on a default ROM. The problem is is that none of the defined packages that I've chosen in the cooking process will be installed when the ROM is flashed. Why is this? Is there something that I should be doing that I'm not doing now that will allow this?
I would greatly appreciate any help in this as I want to become an avid chef but want to learn the ropes first. I've been toying around with it and wanted to get a decent collection of base ROMs and understand them before I start customizing them and such. Again, any help would be thoroughly appreciative and love what you guys are doing here.
HEdwards2008 said:
I've started trying my hand at cooking some of my own ROMs over the past couple of days and have gotten confused on some stuff. I've been following the both the Wiki's and the threads on cooking but none of them seem to point it out so here goes.
1) I'm trying to use a base ROM such as this one or this one and have been successful in both dumping them and cooking them using Alex's latest revision of KaiserKitchen and his apps. When I am including the os.nbh file during the cooking process, should it be the one that comes up in the main KaiserKitchen folder or the one that is located in the BASEROM folder? Is either of those files just the OS part of the ROM without all the applications and such?
2) After cooking and successfully flashing either of the two before mentioned ROMs I will always get the auto-installer which occurs on a default ROM. The problem is is that none of the defined packages that I've chosen in the cooking process will be installed when the ROM is flashed. Why is this? Is there something that I should be doing that I'm not doing now that will allow this?
I would greatly appreciate any help in this as I want to become an avid chef but want to learn the ropes first. I've been toying around with it and wanted to get a decent collection of base ROMs and understand them before I start customizing them and such. Again, any help would be thoroughly appreciative and love what you guys are doing here.
Click to expand...
Click to collapse
os.nb should be in base rom with RUU_signed.nbh(once youve extracted) The File that is generated during ervius package tools is OS-new.nb-this is your new os. Kaiser Wiki has all info.
yardie.spike said:
os.nb should be in base rom with RUU_signed.nbh(once youve extracted) The File that is generated during ervius package tools is OS-new.nb-this is your new os. Kaiser Wiki has all info.
Click to expand...
Click to collapse
I've been searching the Wiki like crazy and I guess I am just confused on it. So OS-new.nb is the OS ROM with all of the packages, Which one would be just the OS itself? The os.nb file in the BASEROM folder?
HEdwards2008 said:
I've been searching the Wiki like crazy and I guess I am just confused on it. So OS-new.nb is the OS ROM with all of the packages, Which one would be just the OS itself? The os.nb file in the BASEROM folder?
Click to expand...
Click to collapse
Yeah, but dont worry about os.nb in base rom folder, unless you dont want to mod the rom and just add your fave radio/splash/spl. If thats all you want to do then recomplile using htcrt.exe in tools folder. OS .nb is what is extracted into OEM SYS and ROM folders in the kaiserkitchen. To add Packages put a folder called Packages in your kaiserkitchen and put your OEM Packages in it, then run KAISERKITCHEN.CMD chose option c then b. When Ervius build os +package tool opens,click the right tab and add rom(Add your kaiserkitchen folder,but make sure its on your desktop). You will then get a list of packages in the premade folder, just tick the ones you want to add to your rom. Once happy click build rom. Once done exit and KAISERKITCHEN.CMD should crack on by itself....then bring up a couple more apps(Rom Tool and Pagepool)just do what they say . every time you exit these apps KAISERKITCHEN.CMD will take you to the next step.
yardie.spike said:
Yeah, but dont worry about os.nb in base rom folder, unless you dont want to mod the rom and just add your fave radio/splash/spl. If thats all you want to do then recomplile using htcrt.exe in tools folder.
Click to expand...
Click to collapse
speaking of the htc rom tool, does anyone have a mirror for the latest version (1.1.1). it's not working on his site, and I 'm really interested in the command line support
mbarvian said:
speaking of the htc rom tool, does anyone have a mirror for the latest version (1.1.1). it's not working on his site, and I 'm really interested in the command line support
Click to expand...
Click to collapse
Theres a new ROM tool????Anyone tried??
NEW IS GOOD!!!
Thank you so much for the clarification. I've also been trying to find a decent kitchen setup and the one made by Alex is the best one I've encountered so far but haven't really steered too far from his build. I have to agree that a new version of the HTC Rom Tool would be cool.
HEdwards2008 said:
Thank you so much for the clarification. I've also been trying to find a decent kitchen setup and the one made by Alex is the best one I've encountered so far but haven't really steered too far from his build.
Click to expand...
Click to collapse
I just put up a Kaiser 20270 kitchen from PPCKitchen.org and AstainHellbring. Try it, let me know what you think. Feedback thread is here.
yardie.spike said:
Yeah, but dont worry about os.nb in base rom folder, unless you dont want to mod the rom and just add your fave radio/splash/spl. If thats all you want to do then recomplile using htcrt.exe in tools folder. OS .nb is what is extracted into OEM SYS and ROM folders in the kaiserkitchen. To add Packages put a folder called Packages in your kaiserkitchen and put your OEM Packages in it, then run KAISERKITCHEN.CMD chose option c then b. When Ervius build os +package tool opens,click the right tab and add rom(Add your kaiserkitchen folder,but make sure its on your desktop). You will then get a list of packages in the premade folder, just tick the ones you want to add to your rom. Once happy click build rom. Once done exit and KAISERKITCHEN.CMD should crack on by itself....then bring up a couple more apps(Rom Tool and Pagepool)just do what they say . every time you exit these apps KAISERKITCHEN.CMD will take you to the next step.
Click to expand...
Click to collapse
So if I'm understanding this correctly....in order to achieve a completely clean ROM without all the extra fixings I would simply need to use the os.nb file and not the os-new.nb file when cooking correct?
No, the only way to get a completely clean base is to use one someone made, or to manually remove extra oems from an uncorrupted rom (which usually means stock). os.nb is the donor imgfs, os-new.nb is the donor imgfs with your added pkgs.
The PPCkitchen.org kaiser kitchen is clean, and is way simpler to use. If you're trying to get to a clean base, do yourself a favor and just use it.
so... does this mean that if I use for say OEM HTC ROM, and put the os.nb in the base folder, when I build it using the tool, whatever packages I selected are simply added to whatever is on the OS.NB? I thought it would use the baserom as base and whatever apps installed on it are ignored. I guess I totally got it wrong then... So how do you strip out all the programs that have been installed in the baserom? Does this mean you have to dump the image?
maximumbs said:
so... does this mean that if I use for say OEM HTC ROM, and put the os.nb in the base folder, when I build it using the tool, whatever packages I selected are simply added to whatever is on the OS.NB? I thought it would use the baserom as base and whatever apps installed on it are ignored. I guess I totally got it wrong then... So how do you strip out all the programs that have been installed in the baserom? Does this mean you have to dump the image?
Click to expand...
Click to collapse
I do know that in order to get the base OEM packages out of the main build you have to go through and remove and edit certain files to get it done right, which there is information in the Wiki about but haven't really had time to focus on it much. As for the PPCKitchen.org version of the Kitchen, I'm going to try it when I get home tonight because I'm at work currently. Gguruusa, you have to understand that some of us are new to the cooking community and want to be able to get our feet wet slowly and make sure we do stuff right instead of damaging our device. I've only got one Tilt and I don't want to completely destroy it. I would love to cook but need to be able to start off with a simple clean base rom with no extra ingredients and then go from there.
maximumbs said:
so... does this mean that if I use for say OEM HTC ROM, and put the os.nb in the base folder, when I build it using the tool, whatever packages I selected are simply added to whatever is on the OS.NB? I thought it would use the baserom as base and whatever apps installed on it are ignored. I guess I totally got it wrong then... So how do you strip out all the programs that have been installed in the baserom? Does this mean you have to dump the image?
Click to expand...
Click to collapse
No dont put os.nb in the base rom put the RUU_unsigned and extract using KAISERKITCHEN.cmd.....read my previous posts.
gguruusa said:
No, the only way to get a completely clean base is to use one someone made, or to manually remove extra oems from an uncorrupted rom (which usually means stock). os.nb is the donor imgfs, os-new.nb is the donor imgfs with your added pkgs.
The PPCkitchen.org kaiser kitchen is clean, and is way simpler to use. If you're trying to get to a clean base, do yourself a favor and just use it.
Click to expand...
Click to collapse
This looks very promising, downloading it now. Thanks for this! Hope they update it 20273 soon
HEdwards2008 said:
As for the PPCKitchen.org version of the Kitchen, I'm going to try it when I get home tonight because I'm at work currently. Gguruusa, you have to understand that some of us are new to the cooking community and want to be able to get our feet wet slowly and make sure we do stuff right instead of damaging our device. I've only got one Tilt and I don't want to completely destroy it. I would love to cook but need to be able to start off with a simple clean base rom with no extra ingredients and then go from there.
Click to expand...
Click to collapse
That's why ppckitchen.org was born. With ppckitchen.org, it's a point and click thing to build a rom. The mysterious part (making a kitchen base) is done for you. All you have to focus on is what packages you want to add.
You still have to unlock your device and install radios outside the kitchen, which is where people generaly brick their devices.
gguruusa said:
That's why ppckitchen.org was born. With ppckitchen.org, it's a point and click thing to build a rom. The mysterious part (making a kitchen base) is done for you. All you have to focus on is what packages you want to add.
You still have to unlock your device and install radios outside the kitchen, which is where people generaly brick their devices.
Click to expand...
Click to collapse
I shouldn't have any problems then seeing as to how I know that you need to have HardSPL installed and also to be sure to flash the radio AFTER the ROM in order to prevent bricking.
But that takes the whole fun out of cooking a rom when the base is already made for you...!!!
I will have to say my most challenging part is trying to get the base rom the way I like it in order to add whatever I want.
For example....
In my current kitchen I have deleted all of the OEMAPPS folders except the dsm file. I have then rebuilt all of my programs like the way a Diamond and Raphael ROM is....
In essence, If I was to just build my ROM without any packages it would be a clean rom without any software like camera, mms, phoneskins ect....
Its taken awhile thats why I have not published my newest rom yet...
ryncppr said:
But that takes the whole fun out of cooking a rom when the base is already made for you...!!!
I will have to say my most challenging part is trying to get the base rom the way I like it in order to add whatever I want.
For example....
In my current kitchen I have deleted all of the OEMAPPS folders except the dsm file. I have then rebuilt all of my programs like the way a Diamond and Raphael ROM is....
In essence, If I was to just build my ROM without any packages it would be a clean rom without any software like camera, mms, phoneskins ect....
Its taken awhile thats why I have not published my newest rom yet...
Click to expand...
Click to collapse
I totally agree my favourite build was one that went wrong and nearly bricked my phone....sounds sick, but it was going back over what i had done and fixing that was the fun part. That ROM turned out to be possibly my most stable (Yardie 2.1.240) Ha ha i love cooking!!!
ryncppr said:
But that takes the whole fun out of cooking a rom when the base is already made for you...!!!
Click to expand...
Click to collapse
Bah. The fun of cooking is getting a ROM to look and feel like you want. Making a kitchen is entertaining when you haven't done it before, but it's really 99% repetition and 1% art.
NATF: the Kitchen
Please Read The Entire Thread Before Posting A Question.
This kitchen is based around the original KaiserKitchen. All the ingredients used in the v5 Final versions of my Kaiser ROM series are included.
Step 1: Download which build you want to work with.
KaiserKitchen - AT&T 3.57 OEM with 20755 ROM and SYS
KaiserKitchen - HTC 3.28 OEM with 20755 ROM and SYS
Step 2: CAB Files
NATF's CAB Collection
(NOTE: I did NOT create these CAB files. The original author information remains intact, but they have been edited to create shortcuts inline with the layout of my ROMs)
Step 3: OEM Packages
NATF's Customized OEM Packages
(NOTE: I created most of these packages myself from CAB files found all over XDA and the internet)
If this is your first foray into ROM cooking, please visit Alex's Cooking Wiki and take advantage of the numerous tutorials available.
Reserved...
i can't get the packages to load properly. the only ones that i am using are the ones that you uploaded in post #1.
An item with the same key has already been added
Click to expand...
Click to collapse
internetadam4657 said:
i can't get the packages to load properly. the only ones that i am using are the ones that you uploaded in post #1.
Click to expand...
Click to collapse
There are some duplicate packages in the archive (some are for the HTC build, and some are for the AT&T build). Make sure that you are not selecting any duplicates.
mirror please...
i'm not, its just attempting to load the packages so that i can select them. when i click ok on the error message it shows some of the packages but its not even half of them. i'm not sure what i did wrong. i've attempted cooking before and i looked at alex's tutorial and it shows that you put the OEM packages into a folder simply called packages which is what i did.
edit: i just tried to select my packages again, and it only loaded 14 of the 38 packages.
Todd, thank you for this great contribution to the community. Your work here will truly be missed when you move on to the Fuze!
internetadam4657 said:
i'm not, its just attempting to load the packages so that i can select them. when i click ok on the error message it shows some of the packages but its not even half of them. i'm not sure what i did wrong. i've attempted cooking before and i looked at alex's tutorial and it shows that you put the OEM packages into a folder simply called packages which is what i did.
edit: i just tried to select my packages again, and it only loaded 14 of the 38 packages.
Click to expand...
Click to collapse
Make sure you are running G'reloc immediately prior to launching the KaiserKitchen.cmd file. You do not need to change any values, just click Do It, and wait about 15 seconds.
You are correct that all you need is a folder named Packages in the same location as OEM, ROM, and SYS. Which packages are you trying to cook in? Maybe a list will help narrow down the problem.
Alternatively, you can bring up the search box when inside the Packages folder, and search for "*.rgu". Then sort them by name, and make sure they all have unique names. If they do, then search for all "option.xml" files, and open them up. Check that the GUID IDs inside them are all unique.
If you have to go to the XML step, I recommend downloading and installing Notepad++. It is a freeware Notepad replacement that allows you to open RGU, XML, and PROVXML files in 1 tabbed window.
Is it already xmas time?
That's really a nice gift.
Thank you very much indeed.
Nice work NATF!!!
I love seeing people open up their kitchens & allowing others to improve or add to them as they see fit! It the sharing of knowledge that makes the XDA community possible & improves it.
I commend you on your open roms & making them easy to moddify & disassemble. We would be much further along in dicovering the ultimate potential of WM devices if more people approached the developmental & hacking tasks as you do. You are a definite asset to our community!
Nice to see more updated kitchens popping up with more & more options!
ok i figured out the problem, on my own even! there were 4 packages that were conflicting.
Package - HTC Home 2.1.1005.722 (ATT - Disabled by Default)
and
Package - HTC Home 2.1.1005.722 (ATT - Enabled by Default)
Package - NATF Reg Tweaks (ATT)
and
Package - NATF Reg Tweaks (HTC)
Somehow those 2 sets of conflicting packages were causing several other packages to fail loading as well.
internetadam4657 said:
ok i figured out the problem, on my own even
there were 4 packages that were conflicting.
Package - HTC Home 2.1.1005.722 (ATT - Disabled by Default)
and
Package - HTC Home 2.1.1005.722 (ATT - Enabled by Default)
Package - NATF Reg Tweaks (ATT)
and
Package - NATF Reg Tweaks (HTC)
Somehow those 2 sets of conflicting packages were causing several other packages to fail loading as well.
Click to expand...
Click to collapse
That's what I mean by multiple packages with identical GUIDs. Because I would never use 2 HTC Home packages in the same ROM, I mirrored the folder and then modified the RGU files as needed. As you can tell from the names, the first package was used for ROMs that contained HTC Home, but did not enable it by default.
As for the Reg Tweaks, the only difference between the two is that the AT&T one has the keys needed to remap the Tilt's keyboard.
ohhhhh!!!! ok! i gotcha now!
by the way, i forgot to say thanks for the release! i loved using the roms, and once i get this cooking thing figured out, i'm sure i'll really enjoy this too! by the way, is there a certain radio that you can recommend to use with this kitchen and any rom that might come out of it?
internetadam4657 said:
ohhhhh!!!! ok! i gotcha now!
by the way, i forgot to say thanks for the release! i loved using the roms, and once i get this cooking thing figured out, i'm sure i'll really enjoy this too! by the way, is there a certain radio that you can recommend to use with this kitchen and any rom that might come out of it?
Click to expand...
Click to collapse
I never distributed my ROMs with a radio. Since reception can vary so dramatically from location to location, I just pointed people to AllTheWay's Ultimate Radio Thread.
On a personal note, I was using Neon 1.58.25.17 from the day it was posted, and never had a reason to dislike it.
TreoFan! You are a god.
I am glad that we have chefs willing to share their builds. This community is about sharing not gross profit!
Not sure what I'm doing wrong here - I've read the tutorials and watched the screencasts, but i'm having problems. I put all my packages in a folder named packages, ran G'Reloc before running KaiserKitchen, and I'm getting errors. The error says "Double package or .DSM found! copying only from packages folder." Could it be because I used Cab2OEM to create some of my oem packages? I went through and made sure all the RGU's hade unique names and that the options.xml had the same GUID in it. What am I doing wrong?
riot1031 said:
Not sure what I'm doing wrong here - I've read the tutorials and watched the screencasts, but i'm having problems. I put all my packages in a folder named packages, ran G'Reloc before running KaiserKitchen, and I'm getting errors. The error says "Double package or .DSM found! copying only from packages folder." Could it be because I used Cab2OEM to create some of my oem packages? I went through and made sure all the RGU's hade unique names and that the options.xml had the same GUID in it. What am I doing wrong?
Click to expand...
Click to collapse
Make sure that you only put the packages you want to cook in the Packages folder.
If you are using any of my packages, then make sure you don't have any duplicates. For example, I have several HTC Home packages, but since I only ever use one, I did not give each of them a unique GUID or RGU.
NotATreoFan said:
Make sure that you only put the packages you want to cook in the Packages folder.
If you are using any of my packages, then make sure you don't have any duplicates. For example, I have several HTC Home packages, but since I only ever use one, I did not give each of them a unique GUID or RGU.
Click to expand...
Click to collapse
I only put about 10 packages in the Packages folder, and made sure each was unique. Could it be anything else?
riot1031 said:
I only put about 10 packages in the Packages folder, and made sure each was unique. Could it be anything else?
Click to expand...
Click to collapse
I'm having the same problems with packages not showing (only listing about 30 out of 50+).
Nice work on the kitchens. Thought i'd give them a whirl and used both for my personal ROM.
I experienced some weird issues with the ATT ROM: the backlight wouldn't work, sporadic freezing right after a reset (which i suspect could be from M2D), and screen freezes (which i'm aware that is usually caused by spl, however don't think it's the case right now).
I then decided to switch over to the HTC one and check that out and had the same problems. The freezing after soft resets (which causes yet another soft reset) and sporadic freezes have led me to think that it could be because of M2D possibly? I'm running SPL v3.28 which should run great on HTC ROMs (as i've used it in the past on my own ROMs). Any ideas or thoughts would be appreciated.
I am learning how to cook a Kaiser 6.5 Rom using osKitchen and just wanted confirmation that I am doing this right.
Any help / advice / redirection will be appreciated.
Thanks for reading.
---------------------------
Using htcRIE_0.5.0.12, I have dumped the XIP from WM 6.1 Rom (RUU_Kaiser_O2_UK_3.29.206.0) and get the following output:
XIP
-OEM
--LangDB
--OEMXIPKernel
-SYS
--MSXIPKernel
--MSXIPKernelLTK
--WinCENLS_WWE
1) LangDB is an empty folder with only a dsm file inside. Hence I have excluded this folder from my kitchen.
2) In OEMXIPKernel I have replaced cecompr.dll with the contained in Post 9 of this thread (http://forum.xda-developers.com/showthread.php?t=438676) that supports LZX compression. I have also deleted nk.exe folder to use the one contained in osKitchen (modified to work with 6.5 kernel). Should all other files / folders in OEMXIPKernel including boot.hv and boot.rgu be left untouched or is there scope for modification / tweaking?
3) MSXIPKernel - Deleted this folder and simply replaced with the one contained in 6.5 SYS package (build 28205). I have deleted mem card encription mencfilt.dll since I read that it is safe to do so.
(a) do I need to edit the dsm file to remove reference to mencfilt.dll or does Bepe's package rebuilder automatically create new dsm files?
(b) since the file size of modules in donor and source MSXIPKernel are different, do I need to manually reallocate the addresses of each module or is that automatically done during the cooking process?
4) MSXIPKernelLTK - Same again. Deleted this folder and simply replaced with the one contained in 6.5 SYS package (build 28205). This folder only contains a dsm file so I guess no reallocation is required.
5) WinCENLS_WWE - With this one I am not sure. Initially I thought of deleting this as well since it is contained in 6.5 SYS package. But elsewhere it was suggesting that this is not allowed since the Rom may not boot. OndraSter suggested that I transfer the wince.nls file into OEMXIPKernel and delete the WinCENLS_WWE folder. If i did this then
(a) do I need to edit the dsm file in OEMXIPKernel folder to add reference to wince.nls?
(b) should I delete the WinCENLS_WWE folder from 6.5 SYS folder to avoid duplication (although file sizes are different)?
Anyone willing to spare some time to help please?
Not sure why you are using ROM Editor to do this; it would be so much easier just to use osKitchen or Ervius and dump that ROM, then all you'd have to do is copy/paste. I'm also learning, but I'll answer what I know.
1)I do the same. Almost all chefs delete almost all the .dsm/package.ini files in their kitchen folder before cooking with osKitchen or Ervius's VK. I don't know why it is possible to cook without them, but it's easier then maintaining them and saves a tiny bit of space. It is also why almost all cooked ROMs are not able to be dumped as per OEM ROMs--the file associations and shadows are gone (which is what the .dsm/package.ini files provide).
2)Let me preface by saying that ideally, you shouldn't be touching anything in the OEM/MS kernel. 1st q: If you are using osKitchen, why are you doing this? It can compress with XPR or LZK out-of-box . 2nd q: The nk.exe is modified to use more RAM, not to work with WM 6.5. Kaiser doesn't have a native WM 6.5 nk.exe, so chefs use an older 6.1 nk.exe from a released ROM and patch it to use more memory if they want.
3)I've never deleted that, but this is otherwise correct. (a) You could use DSM editor and remove that one file association yourself. (b) Automatic, as I've never reallocated anything in the kernel and my ROMs cook perfectly.
4)This is correct.
Last one I don't know. I've never done any of that and my ROMs cook/work fine. If I did what OndraSter recommended, I still wouldn't do either (a) or (b) because I don't think it matters to the kitchen script--he would have probably told you to do that as well.
Thanks for responding to the distress signal.
Quetzecotyl said:
Not sure why you are using ROM Editor to do this; it would be so much easier just to use osKitchen or Ervius and dump that ROM, then all you'd have to do is copy/paste. I'm also learning, but I'll answer what I know.
Click to expand...
Click to collapse
I use the ROM editor since I get an error whilst using osKitchen to extract RUU_signed. Infact there is also a warning that pops-up explaining that this utility in osKitchen is awaiting a rewrite and to expect failures.
Quetzecotyl said:
1)I do the same. Almost all chefs delete almost all the .dsm/package.ini files in their kitchen folder before cooking with osKitchen or Ervius's VK. I don't know why it is possible to cook without them, but it's easier then maintaining them and saves a tiny bit of space. It is also why almost all cooked ROMs are not able to be dumped as per OEM ROMs--the file associations and shadows are gone (which is what the .dsm/package.ini files provide).
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
2)Let me preface by saying that ideally, you shouldn't be touching anything in the OEM/MS kernel. 1st q: If you are using osKitchen, why are you doing this? It can compress with XPR or LZK out-of-box .
Click to expand...
Click to collapse
I was getting errors with osKitchen when using the original 6.1 cecompr.dll. It is only when I replaced it with the version in the referenced post that the errors disappeared.
Quetzecotyl said:
2nd q: The nk.exe is modified to use more RAM, not to work with WM 6.5. Kaiser doesn't have a native WM 6.5 nk.exe, so chefs use an older 6.1 nk.exe from a released ROM and patch it to use more memory if they want.
Click to expand...
Click to collapse
Thanks for the clarification .
Quetzecotyl said:
3)I've never deleted that, but this is otherwise correct. (a) You could use DSM editor and remove that one file association yourself. (b) Automatic, as I've never reallocated anything in the kernel and my ROMs cook perfectly.
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
4)This is correct.
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
Last one I don't know. I've never done any of that and my ROMs cook/work fine. If I did what OndraSter recommended, I still wouldn't do either (a) or (b) because I don't think it matters to the kitchen script--he would have probably told you to do that as well.
Click to expand...
Click to collapse
When I dump the 6.1 ROM, wince is part of the XIP. The recent 6.5 releases (28008 and 28205) contain wince as a SYS package in folder WinCENLS_WWE. This is what confuses me - is wince device specific or is it build specific .
If I place the wince from 6.1 ROM in OEMXIPKernel and also select the one in 28205 SYS as an ingredient, then either I am duplicating (and possibly creating a conflict since the file sizes are different) or the kitchen script is smart enough to ignore one of these?
This has also been discussed at http://www.everythingdiamond.info/showthread.php?t=444&page=46 but without any strong conclusion.
Has anyone else experimented with wince?
OK, about WinCE--I wanted to make sure, but skimming through my build logs for a time, I don't think I've ever had that in my SYS. WinCE must be device specific because it is part of the OEMXipKernel, and I've used the same one (ie, OEMXipKernel) maybe 30+ times and can not recall ever seeing a wince.nls in my SYS updates. I've only cooked the 21xxx and 23xxx WM6.5 COM branches, but I can't help but think that the WinCE in your SYS update comes from the device the SYS dumpers used. If I were you, my first go around I would exclude it and use the one from your OEMXip. If for some reason your ROM doesn't boot (it could be so many other things), try replacing your wince.nls with the one from your SYS update (highly doubt this).
BTW, I recommend using Ervius for dumping, as it has never given me any issues.
I think what you say seems logical. I will give it a try and feedback how it went. Thanks once again.
If you dump it via my kitchen and put name Kaiser, it should autogenerate all Sources folder with OEM, original SYS and put NK and XIP on right places actually. (I tried it on newer version of Kaiser's ROM when I was making this dumper so it should work fine.)
And if you restart kitchen, it will load all things automatically (or I hope so, I haven't tried the new UI yet, I'm still at the old one since I actually prefer it...)
I get an error when dumping using your kitchen. I have posted the exception text in your thread.
ps: This is sorted. My RUU_Signed.nbh was not in root of osKitchen dir but a different dir where I place my ROMs.