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,
Hello,
I extracted Schap's ROM 4.31, no problems until that.
But when I want to reconstruct it with Ervius package tools + Build OS, without adding any package (so no cooking if I can tell that...), there are some problems when it come to the last process, the "Registry file processor and hive builder.". It tell me that : 'InitRegistry FAILED in file ".\Registry\1dc3da02-499f-4547-9fd2-78cddfda9c62.rgu" within a few lines of line 1.'
So, I looked at this RGU file, and indeed, the file is empty ! And there are many other RGU in the same way !
So, what is the problem ? Bad extraction ?
Thanks in advance.
Ok,
Nobody wants to help me ?
Why ?
up!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
It's been posted in the ROM kitchen thread and the reconstructing ROMs thread many MANY times. You can't re-cook certain chef's ROMs, because they don't include .RGU files.
Hope this helps!
Thanks you very much Alex, I read the Kitchen thread, but may me be not wholly...
So, is there a possibility to include the missing rgu's from other rom ?
Just another question,
during the past weeks I reconstructed my factory ROM, there wasn't all the RGU files too, but however, this has worked... Why ?
Thanks a lot for your great patience...
Pascal06 said:
Thanks you very much Alex, I read the Kitchen thread, but may me be not wholly...
So, is there a possibility to include the missing rgu's from other rom ?
Just another question,
during the past weeks I reconstructed my factory ROM, there wasn't all the RGU files too, but however, this has worked... Why ?
Thanks a lot for your great patience...
Click to expand...
Click to collapse
Some directories just won't have RGU files, which is ok. This is what you've encountered with your factory ROM.
RGU files are important because they contain registry information. Taking them from another ROM is going to be a very painful process, and that's also where 75% of the customization takes place, so losing the important registry information from the original ROM will make it less than useful.
For more information about RGU files, read my OEM Primer from my OEM Package Tutorial...
Hope this helps!
Thanks you Alex,
I already read your OEM primer tutorial.
In fact, if I wanted to cook the Schap's ROM, it's because the included Arcsoft MMS program doesn't work. So, I wanted to include yours (the last version 5 cab), and others app, eg. MS voice command and Transcriber.
I'm very ashamed...
Pascal06 said:
Thanks you Alex,
I already read your OEM primer tutorial.
In fact, if I wanted to cook the Schap's ROM, it's because the included Arcsoft MMS program doesn't work. So, I wanted to include yours (the last version 5 cab), and others app, eg. MS voice command and Transcriber.
I'm very ashamed...
Click to expand...
Click to collapse
Why be ashamed? It's good that you tried something new and even if it didn't work as expected, it was a learning experience.
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.
Hey guys,
I am working on my first rom. After going through many readings from other sub-forum (hermes and kaiser) as well as Ivan's cooking class, I made my first rom using the Wing stock rom. After deleting un-used packages and files, I can sucessfully build the os.nb and converted it to .nbh file. But when I tried to flash it back to the wing, I got a error saying my RUU cannot used to flash the device, but I have been using this same RUU for many roms. I attached the screenshot, please take a look and help me debug it. It's my first rom Many thanks
go and try when you buld .nbh to set device "herald" but in section "version" write "test" not the numbers that are there by default.....
hope that helps.
Yep, looks like you didn't set it to Herald when you built it.
Thanks. You guys are right. I can flash my rom now. However, it stuck in the primary splash and does not response to the stylus. Any idea how to fix? Again, really appriciate any help.
live4nothing said:
Thanks. You guys are right. I can flash my rom now. However, it stuck in the primary splash and does not response to the stylus. Any idea how to fix? Again, really appriciate any help.
Click to expand...
Click to collapse
This is part of the fun of being a cook, figuring out what mistakes we made.
There could have been 1 million different things you could have done that made it not boot up. It could have been something you removed or something you added. What kitchen are you cooking with? (It could also be that you didn't relocate all the modules if you're using something like hypercore.)
ivanmmj said:
This is part of the fun of being a cook, figuring out what mistakes we made.
There could have been 1 million different things you could have done that made it not boot up. It could have been something you removed or something you added. What kitchen are you cooking with? (It could also be that you didn't relocate all the modules if you're using something like hypercore.)
Click to expand...
Click to collapse
I am using hypercore. Can you point me to a reference to use hypercore or maybe an better kitchen for new cooks?
Either use G'Reloc for hypercore, or use Bepe's Extended Kitchen for the Herald. The latter option would be the best.
After re-doing the delete packages part, I got the rom flashed into my wing, booted, but nothing working. I mean windows started, top and bottom bars also loaded, but radio not working, nothing reponses. One thing, the screen seem to flicker a little bit. I notice the boot speed is super fast (really really fast) as in none of the hardware drivers is initialized at all. I am clueless as of this point. Any more help?
@Ivan:
Thanks man. Since I started with hypercore and kind of familiar with it already, I would like to stick with it. Can you show me how to use G'Reloc? Thanks
Just drop the file into your build folder and run it. (Assuming you're using a SYS folder that belongs to your phone.) Bepe's kitchen is great because it does a lot of fixing up for you automatically. It's not a competitor's kitchen, it's a MUCH newer kitchen. I use both. I use Hypercore to take Herald ROMs appart and for different tools in it and Bepe's kitchen to put my ROMs together (and a kaiser kitchen to take appart kaiser, diamond and other ROMs) and I also use my own kitchens which are mostly based out of Bepe's kitchens.
The whole boot speed and nothing working means that you deleted things packages you shouldn't have.
I run G'Reloc, but it ask for slot 1, slot 2, ... Do you mind explain them to me? I tried to just click "do it" with the default values, and it showed that it relocated 265 out of 368. I built the rom and flashed it to my wing, but it stuck in the boot splash now. Thank for the help
Those are taken from a folder in your SYS folder. It sounds to me like you deleted a lot of packages that are essential to WM6/6.1. You can't delete everything that SOUNDS like you don't use. Also, the SYS folder HAS to be from a Herald UNLESS you ported it. If you didn't port it, then the values on slot 1 and slot 2 will be wrong.
I followed your guide to take the SYS from the Kaiser's rom. Here's what I did. I run buildOS.exe, then I run G'reloc, then I run createROM.bat. Did I do it right?
live4nothing said:
I followed your guide to take the SYS from the Kaiser's rom. Here's what I did. I run buildOS.exe, then I run G'reloc, then I run createROM.bat. Did I do it right?
Click to expand...
Click to collapse
Which guide? My guide? You run G'Reloc first and THEN buildOS, or else you're building the OS BEFORE fixing the files that you need to BUILD the OS.
The sequence part, I guess on my own. I meant I follow your guide on porting the SYS and XIP on lesson 4 and 5. I did not even try G'Reloc in the first place because I did not know I have to do it. Btw, thank again man, you're such a big help to me.
The reason why the guide was failing and I hadn't mentioned G'Reloc in the walkthrough is because the walkthrough was made for Bepe's Extended Kitchen. No problem with the help. I remember when I was learning, no one answered, so I figured I'd give something back.
working with OEM
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
live4nothing said:
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
Click to expand...
Click to collapse
This is great news, we have a new herald cook on the way.
I'm very glad to see this since I will be not be cooking any more after my current release is done.
Keep it up bro,
live4nothing said:
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
Click to expand...
Click to collapse
Your missing the SQM package (or at the very least the patched file that you use to bypass it.) http://forum.xda-developers.com/showthread.php?t=393997
ivanmmj said:
Your missing the SQM package (or at the very least the patched file that you use to bypass it.) http://forum.xda-developers.com/showthread.php?t=393997
Click to expand...
Click to collapse
Dude Ivan, you are awsome. I sucessfully created a ROM using my ported SYS, XIP and my own OEM. Again, thank you very much for guiding me through the whole process. I am thinking release it as a lite rom so everyone here can enjoy the newest build if they wish to. Before I can do it, I want to do some tweaks to it. So can you so me how to cook registry entries into the ROM? Thanks
live4nothing said:
Dude Ivan, you are awsome. I sucessfully created a ROM using my ported SYS, XIP and my own OEM. Again, thank you very much for guiding me through the whole process. I am thinking release it as a lite rom so everyone here can enjoy the newest build if they wish to. Before I can do it, I want to do some tweaks to it. So can you so me how to cook registry entries into the ROM? Thanks
Click to expand...
Click to collapse
You've got two options. RGU's and PROVXML's. You're better off setting up a package with an RGU that has all your registry keys. RGU's are nothing more than reg files. ^_^ And I'm glad it worked.
Hello all ,
I ran into the problem of liking a rom that was protected..
no problem , only thing i want to add was remote tracker.
the rest i do with uc.
So with the help of da_g i striped a kitchen to unpack and repack protected roms.
to add a package , just unpack..put your cab in the dump dir and add it to config????.txt
and repack.
that way i get the use the protected rom with my own package build in.
thought i would post it.
grtx , arnold
hi arnoldl,
i want to thank you and everyone have helped you to create and publish this. i was searching something like this since many time ago, finally i found your thread and i was able to add RT to the rom i use!
i think this will be useful to many other people
i have changed something and it works perfectly with my blackstone!
thank you thank you.
bye
What is the difference in extracting ngh file, adding cab file to dump folder, updataing config.txt and recooking compared to installing the cab file using UC?
Can we add visual kitchen packages to this dump folder? If we can add do we need to just copy all the files in all the folders of the package to dump folder?
eg: in the package there are some files in 0409 and some in files folder , _skip, app.reg, all these goes to dump folder?
Thanks
@DarkRenegade
No problem , happy that i helped...
@kk0813
If i would buy a phone of the street , i would do the folowing.
- check if there are funny things on it
- format the card
- hardreset the phone
and gone is your remote tracker protection..
If i cook rt in, with my personal settings for it.
after a hard-reset it's installed again , so i can still gps find my stolen phone after a complete format.
only next step i want to take is to re-hard spl , to prevent reflashing if posible.
but these days with new 6.5 images coming out so quick i flash so often i will wait with that one
but all other things i install by uc or later shashimi
Don't know if you can add kitchen files.
never tried it.....
btw attached a new version.
remade it to work with the new envirus kitchen the newer 6.5 roms are using..
arnoldl said:
@DarkRenegade
No problem , happy that i helped...
@kk0813
If i would buy a phone of the street , i would do the folowing.
- check if there are funny things on it
- format the card
- hardreset the phone
and gone is your remote tracker protection..
If i cook rt in, with my personal settings for it.
after a hard-reset it's installed again , so i can still gps find my stolen phone after a complete format.
only next step i want to take is to re-hard spl , to prevent reflashing if http://forum.xda-developers.com/showthread.php?t=503112posible.
but these days with new 6.5 images coming out so quick i flash so often i will wait with that one
but all other things i install by uc or later shashimi
Don't know if you can add kitchen files.
never tried it.....
btw attached a new version.
remade it to work with the new envirus kitchen the newer 6.5 roms are using..
Click to expand...
Click to collapse
Thats a nice idea. Thanks for the updated version.
DarkRenegade said:
hi arnoldl,
i want to thank you and everyone have helped you to create and publish this. i was searching something like this since many time ago, finally i found your thread and i was able to add RT to the rom i use!
i think this will be useful to many other people
i have changed something and it works perfectly with my blackstone!
thank you thank you.
bye
Click to expand...
Click to collapse
Thanks again
works very well
arnoldl said:
Hello all ,
I ran into the problem of liking a rom that was protected..
no problem , only thing i want to add was remote tracker.
the rest i do with uc.
So with the help of da_g i striped a kitchen to unpack and repack protected roms.
to add a package , just unpack..put your cab in the dump dir and add it to config????.txt
and repack.
that way i get the use the protected rom with my own package build in.
thought i would post it.
grtx , arnold
Click to expand...
Click to collapse
You have a Trojan horse in first post!!!
All this to add a couple of cabs to a ROM ? Isn't it a whole of a lot easier to just... you know... install them after ? Or maybe even UC them to make it even lazier ?
Does this work with other roms from other devices? Or just Raphael roms?
I tried this but it extracts os.nb and os.nb.payload and also os.nb.extra but when it starts to create dump it fails
this is the log
ImgfsToDump 2.1rc2
Cannot map file imgfs.bin
what to do help
jagan2 said:
I tried this but it extracts os.nb and os.nb.payload and also os.nb.extra but when it starts to create dump it fails
this is the log
ImgfsToDump 2.1rc2
Cannot map file imgfs.bin
what to do help
Click to expand...
Click to collapse
Use the latest version of extractor, place the .nbh file in BaseROM, rename it to RUU_signed.nbh and run the extractor.
That worked for me.
A little late reading this, but I downloaded it to rip a rom from a little known site & guess what... Theres a trojan in that 1st post, virus software just riped it out of 2 kitchens recently downloaded as well as that 1st post file.
file namned Win32/Delfsnif.dx
I used your extractor but when i use old (1,2mb) i have problem with rom (sense 2.5 crash , windows menu crash), when i use new extractor (1,9mb) i don;t have a bootable rom (.nbh is very small 15mb-100mb) Is there any solution?
Sorry for my english I hope you can understand me.
I think there are more usefull tools that could help you.
Let's have a look here : http://forum.xda-developers.com/showthread.php?t=411915
And I believe that this tool is used by most roms makers.
Sorry but this tool is traying to rebuild protected rom into kitchen (with folders - ext, rom, sys etc.) but this is impossible.
Worked Great ! !
It worked great for me!
Moving to general section
You should just move this to the cooking forum. People are always asking if you can modify cooked roms. Then others are always answering that you can't dump and modify a protected rom, which clearly isn't true. So this would work ok in the Cooking forum (can't even remember the name of the forum, even though I'm a mod there, lol).
If this works, than this is pretty kick ass! I was recently trying to simplify the process as you did but your work looks flawless to me! I'll post as soon as I can confirm it works putting the rom back on an HTC rose (htc s743).
After the rom is dumped, what says what files go in what directories? In the dump directory ALL files are in the dump directory and not in the folder structure they would be after the ROM is flashed to the phone. Where would I find what determines the folder structure?