Database Info

Announcement: Wizard Rom-Packer Kitchen V2.0

Welcome to the Wizard Rom-Packer Kitchen V2.0, with "Squeezer" technology!
Please read all the way through before starting, even if you've used a previous version.
USE AT YOUR OWN RISK!
This kitchen is easy to use, but is really meant for those with some previous work with other kitchens,like faria's or 004's or Molski's. (If I've left someone out, I'm sorry about that.) This kitchen is based on Bepe's Hermes kitchen, which has incorporated tadzio's reworking of maimach's imgfs tools. This allows the rom to be packed more efficiently, and thus more packages and files to be burned into the rom. The savings is not trivial, a few megabytes at least.
In addition, I have added a new Squeezer module, based on open-source UPX technology, which actually compresses Office .exe files, freeing even more room in the rom (a few more meg), and actually decreasing load times!
Although the Wizard Rom is not quite as malleable as the Hermes in that the extra space is not translated into additional user storage memory, at least the additional freeware, shareware, themes, etc. which can be burned to the rom do not have to reduce the user storage space.
I hope over time to enhance this further, as new innovations become available, (maybe someone will figure out a way to repartition the Wizard Rom?). Also, perhaps adding some way of automatically generating the xip directory. If you have suggestions feel free to let me know about them.
Error checking is not extensive, so be sure to keep your old rom available to fall back to! Check the size of the generated .nbf file. If its around 59 mb you are close to the limit. Be ready to re-flash in bootloader mode (after paring some packages or files) if the program exits before the 100% mark.
How to use:
Download your favorite base rom, at this point one from another kitchen, which has already been broken down to SYS, OEM, and ROM directories. Delete the SYS, OEM, and ROM directories from my kitchen, and copy the ones from the other kitchen in there instead.
Make a copy of the SYS\OFFICE directory in case of later problems (not likely).
An additional caution/strong recommendation is to delete the /autoupdate package from your roms. This currently does nothing anyway, so you won't miss it, and in any case would likely only create havoc with a custom rom. But additionally the repacking method used in this kitchen removes the extra space in the rom which was to be used for that anyway, and so autoupdate will definitely be useless in a rom built with this method.
Run the SqueezeOffice.bat program. (This compresses your main Office .exe's)
Make sure there is an 80040000-os.nb file in the ROM directory. (It may be called something else and have to be renamed. It'll be around 50mb in size.)
Now click on Start.bat, and away you go...
(Optional) If you want to later go back to using another kitchen, run the PrepareNewNB.bat file. After it completes, there will be a new, compacted 80040000-OS.nb file created in the ROM directory which you can move back to your original kitchen. (Also copy the Office directory back) You will loose some packing efficiency by building in another kitchen, but you will still gain lots of space from having visited here!
Depending on the kitchen you were using, either you will see selectable packages or not during the running of BuildOS. Use whatever method you were using previously to add new packages or to remove the ones you don't want. In general, everything should work about the same way it did before, except you will be able to fit more packages in than previously! (Those who are importing faria's kitchen will have to rename his BuildOS.exe to BOS.exe and bring it into this kitchen. Also, rename his Flash file in the ROM directory to 80040000-OS.nb.)
You will be given the opportunity to go all the way to flashing the rom, similar to the way faria's kitchen is set up. Hold down the Control and "C" keys during one of the pauses provided if you do not want to go to the next step for some reason. (You have a G4, unlocked G3, want postpone flashing for later, etc.) Then press the "Y" key to abort when prompted.
If you'd like, check out the ZSqueezer directory, and the readme there. There you can compress your other programs for even more space (and speed!).
Thanks to all those who have helped me in the past, and especially those who created the tools and roms we all use and enjoy.
Version History:
Initial Unlabeled: Worked fine
V1.1: Added "pre-packing", had a bug in Start.bat
V1.2: Worked fine
V1.3: Deletion of .rgu files from the dump.
V2.0: Removed .rgu deletion (instability), and introduced "squeezer" compression.
Download Link: V2.0
http://rapidshare.com/files/33616241/Wizard_ROM-Packer_Kitchen_V2.0.rar

Standalone Squeezer Module
For those interested in having the "squeezer" technology for their own programs, but aren't comfortable cooking their own roms, I have created a standalone module for that. (Already included in the latest Rom-Packer Kitchen V2.0). I've also started a separate thread for that as well in the Upgrading section. Of course, feel free to leave comments and suggestions in either thread.
Here's the link: http://forum.xda-developers.com/showthread.php?p=1283338#post1283338
Have fun!

More space for later use.

thanks. i'll give it a go later tonight

I just tried these tools and didn't have much sucess....
I used the latest mUn base ROM, added some OEM stuff that I have been using without issues when creating ROM's with mUn's previous ROM. All this went OK. It got to the point of installing the ROM on the device but the ROMUpdateUtility just exited at 98% and left the Wizard in limbo. I have had put it in bootloader and re-intall a previous ROM
There was no message, it just got to 98% on the PC and the Wizard and then the ROMUpdateUtility just exited. I tried manually using the nb2nbf application and copying the resulting nk.nbf to another RUU folder and the same thing happened.
Any idea's?
Andy

ADB100 said:
I just tried these tools and didn't have much sucess....
I used the latest mUn base ROM, added some OEM stuff that I have been using without issues when creating ROM's with mUn's previous ROM. All this went OK. It got to the point of installing the ROM on the device but the ROMUpdateUtility just exited at 98% and left the Wizard in limbo. I have had put it in bootloader and re-intall a previous ROM
There was no message, it just got to 98% on the PC and the Wizard and then the ROMUpdateUtility just exited. I tried manually using the nb2nbf application and copying the resulting nk.nbf to another RUU folder and the same thing happened.
Any idea's?
Andy
Click to expand...
Click to collapse
Can't really say. I've also flashed mUn's latest, and it seemed to go ok. Did you create your own xip directory? If not, use the version in 004's kitchen as a base.

edhaas said:
Can't really say. I've also flashed mUn's latest, and it seemed to go ok. Did you create your own xip directory? If not, use the version in 004's kitchen as a base.
Click to expand...
Click to collapse
I had the XIP directory from the original ROM kitchen (in dOUbleOfour_Wiz_Dev_5.2.1413WWE.rar). I think I might try without any OEM stuff and build it up and see where it fails. In your original post you mentioned the error checking is not extensive, does it log any errors anywhere? (apart ffrom the log.txt file that looks OK).
Andy

ADB100 said:
I had the XIP directory from the original ROM kitchen (in dOUbleOfour_Wiz_Dev_5.2.1413WWE.rar). I think I might try without any OEM stuff and build it up and see where it fails. In your original post you mentioned the error checking is not extensive, does it log any errors anywhere? (apart ffrom the log.txt file that looks OK).
Andy
Click to expand...
Click to collapse
You put too many files, that's why it existed. I presume that because it exited at 98% , meaning that almoust fit, but it didn't . Try leaving out a package ...something about 1MB or so..mabe less

anichillus said:
You put too many files, that's why it existed. I presume that because it exited at 98% , meaning that almoust fit, but it didn't . Try leaving out a package ...something about 1MB or so..mabe less
Click to expand...
Click to collapse
Yep, I think that's what the issue is
When I tried cooking with this as the Base ROM previously I ran into size limitations so I was hoping that these new kitchen tools would solve this -
This allows the rom to be packed more efficiently, and thus more packages and files to be burned into the rom. The savings is not trivial, several megabytes at least.
Click to expand...
Click to collapse
Obviously not enough
I'll play around a bit more and see where I get....
Andy

I'm very sorry, but I left out a very important preparation step in my original posting. Please redownload the package to get the corrected version. (V1.1) I think you will find the results to be much more satisfying! Keep the bug reports coming..

the new start batch file doesn't have the correct paths in it. its trying to work in the root folder not temp.
the original one works good though. too late to flash tonight, but i'll give it a go tomorrow and let you know how it works

I tried to correct the start batch file to use temp but now get errors about not finding initflashfiles.dat in the temp\dump area. I don't have time to debug this right now.
I also noticed that the nb2nbf.exe is a Typhoon Smartphone version (so not sure that is correct for the Wizard).
I will say that the pre processor that does the packing is cool. The Faria Vanilla 80040000.nb (in Faria's kitchen its actually called FLASH.nb0, so I just renamed it) was 58.3MB in size. After running the PrepareNewNB.bat it was then 57.1MB, so a full meg smaller. I'll see about moving this over to the Faria kitchen and using it to rebuild my rom later and see how that changes things when its actually flashed to the phone.

i'll post the working one in a little bit.
edit... here's the one that works for me

notyourdaddy said:
i'll post the working one in a little bit.
edit... here's the one that works for me
Click to expand...
Click to collapse
Thanks, I was bleary eyed last night with trying to figure out what was going on that it wasn't working for you guys, and I ended up "fixing" some things that weren't broken I guess.
Just be sure to delete the old dump file in the temp directory after you run the preparenewnb.bat file.
Has the compression been working for you?
I appreciate your help. I'm juggling lots of things with "real life" and am sorry for the slip-ups.
I am updating the first postings.

notyourdaddy said:
i'll post the working one in a little bit.
edit... here's the one that works for me
Click to expand...
Click to collapse
Maybe its an issue with the Faria RK base rom and compatibility with this kitchen, but even with this updated file (thanks for that) I still get the following error when running the build os step:
Code:
Could not find file "temp\dump\initflashfiles.dat".
The other question is, is it ok to use the Typhoon Smartphone nb2nbf.exe that comes with this?

mfrazzz said:
Maybe its an issue with the Faria RK base rom and compatibility with this kitchen, but even with this updated file (thanks for that) I still get the following error when running the build os step:
Code:
Could not find file "temp\dump\initflashfiles.dat".
The other question is, is it ok to use the Typhoon Smartphone nb2nbf.exe that comes with this?
Click to expand...
Click to collapse
Yeah, I was just running through the faria kitchen and had the same issue. The workaround is to copy the initflashes.dat file in the OS folder and then paste it into the dump directory after buildos has deleted the previous dump and before it is processing the sys\os directory. (Watch the process messages at the bottom of the buildos screen.) This worked for me.
Yes the typhoon version works fine. I think they are mostly all relabeled versions of the same original tools. (Except the imgf tools which are recently updated by tadzio.)
Hope this helps.

weird. intiflashfiles.dat copied over for me using 004's kitchen

I just finished doing a build with faria's kitchen as a base, and was somewhat disappointed that I was unable to flash the entire kitchen at once. I had to leave out enterprise and voip (which is fine for me, but some may want them). I'd be interested in hearing how much extra space people are finding. I felt like I was able to cram a lot more into double_ofour's mUn release, but perhaps that's because it was more stripped down to start? Maybe "the kitchen sink" was a bit optimistic.

Re Faria kitchen
mfrazzz, The easy fix for the faria kitchen is to use faria's buildos.exe instead of the generic one I included. That one runs fine with his kitchen. Just rename it to bos.exe. (or edit the start.bat appropriately.) I don't think this will affect the packing of the files.

Update
OK, Things seem stable now. I've updated the first posting with additional information gleaned from everyone's input, and updated the version. The old start.bat that notyourdaddy posted should not be necessary.
FYI, I got feedback from one user that they got about 2.5 meg additional space from these tools vs the old tools. Not as earth shattering as I'd hoped, but helpful. Roms with more small files, as opposed to those with larger files will likely benefit more, as the savings are in the "padding" between them.
Feel free to incorporate this into your own kitchens.
Regards,

[UPD beta3] Microwave oven: TRANSLATE YOUR ROM - (for wizard only)

Hi ppl,
I've collected all the tools I use to translate roms from our chefs (God bless them). I don't want to steal anyone's work so the most of the credit should go to the creator of the tools I've packed, so all but Muiver, 2bytecut, Go.bat that were made by me.
It should be easy for everyone to make a translation following these steps (it's easier to do than to read ...):
1) Download and install windows PROFESSIONAL image in your language (source language) from here
2) Download your preferred foreign language (destination language) ROM (i.e. TNT or OCATIVOI or whatever ... )
3) copy the images over microwave dir, go to the command prompt and run GO "your language image file" "foreign language nbf file":
4) Let it run ... When Muiver opens up, set the right languages, pick your preferred options and hit GO.
MuiVer automatically looks for the right directories in the MS dump and copies it over the image that needs to be translated, modifying some files and making things you don't have to care about. At this stage you only have to choose, based on your (future) experience, what you want to copy and what not. The options are : Mui directories (OS), Other Mui files (OEMapplications), Other non MUI files (other language related files like staticdict); The more you copy, the most will be translated, more problem you may experience (missing texts, or applications that goes blank screen).
I suggest to always copy the MUI directories and experiment with other options.
5) You're nearly done only have to edit initflashfiles.dat according to your language. This file contains the localized name of some system directories and especially the start menu and start menu items names.
When wincmp opens up you will see two child windows: the left one is the file you have to edit, The right pane c0ntains the initflashfiles localized for your language. Edit the left one, according to what you can see in the right one and then "save source" from File menu. Take big care to the name of the "startup" dir (i.e. in italian it must be changed in "Esecuzione automatica") otherwise your rom won't start the customization (no screen alignment, no initial settings .. etc etc..). I suggest not to change the name of the links in the appbutton section however.
6) When nb2nbf opens up, set everything like always (look at the picture) and hit "translate" button
Flash your new translated rom (tools included)
It's a beta, just test .. I am quite happy with it. I'll update the script to run with other devices.
DOWNLOAD links beta3:
Rapidshare Download link
Mediafire Download link
Fixed beta3:
- Added a new tool to speed up initflashfiles.dat editing
Fixed beta2:
- Before flashing move or delete manually the file nk-old.nbf or the Updater could reflash that one in place of the translated one

it is good post, even in microwave oven cooked!

I think it doesn't work with ROMs that is >= 5.2.1620 because the shellresapps.dll.xxx.mui is incompatible with older versions?

Would someone be kind enough to translate TauRho3i to English.
http://forum.xda-developers.com/showthread.php?t=332663
Anyone want to try?
-McMex

starkwong said:
I think it doesn't work with ROMs that is >= 5.2.1620 because the shellresapps.dll.xxx.mui is incompatible with older versions?
Click to expand...
Click to collapse
If it's true, then remove the directory from dump.src dir before hitting "go" on muiver ... I'll check for it and handle the case in next version.
Would someone be kind enough to translate TauRho3i to English.
http://forum.xda-developers.com/showthread.php?t=332663
Anyone want to try?
Click to expand...
Click to collapse
Come on man ... you'have the tools now, why don't you try by yourself :|

can someone up load this tool to another host ? Ex: mediafire.com plz!
I'm having probs in downloading files from rapidshare

i'll try
mcmexican said:
Would someone be kind enough to translate TauRho3i to English.
http://forum.xda-developers.com/showthread.php?t=332663
Anyone want to try?
-McMex
Click to expand...
Click to collapse
i'll try
...but i'm waiting for my touchscreen

New tests shows that a very little number of .mui files (out of .mui dirs) are compatible with our WM6 releases ... for safe translations, do not copy them at all (MuiVer->File->options->Other Mui Files -> ignore all)
Hint: Take a look to the initFlashfiles.dat in the dump.src dir before editing the new one.
medkid said:
can someone up load this tool to another host ? Ex: mediafire.com plz!
I'm having probs in downloading files from rapidshare
Click to expand...
Click to collapse
Done
@Taurho: Take a look at the ROMUpdateUtility.exe

TauRho said:
i'll try
...but i'm waiting for my touchscreen
Click to expand...
Click to collapse
If I would have known I have a bricked 8125 sitting on my desk. But thank you.
-McMex

Working on TauRho3 WWE
mcmexican said:
If I would have known I have a bricked 8125 sitting on my desk. But thank you.
-McMex
Click to expand...
Click to collapse
one colleague of mine... and my first beta-tester has lent me his WIZ (only for weekend, of course)!
so....I take back the development!!!
and TauRho4 WWE is arriving
...hummmm sunday morning! (italy time)

Great job! I am so expecting tools like this, thanks.
One quick question - Does it translate all content of the ROM, incl. OS and OEM applications? Or only OS, not for other applications in the ROM? Thanks?

it doesnt work with me i have downloaded all image file's from microsoft and when i instald it i get a pocket pc dir a tools dir a Images License txt file and a Images Readme file so i placed it all including the nbf file in the microwave dir and pressed go and a msdos screen flashes for about i mili second and then it does nothing did i do somthing wrong??
or can someone please explain me better
thanx
Danny

Can you explain a little more point number 5 and 6 plz?
I'm transalating from wwe to spanish thx.
It's my first attemp to do something with kitchens, etc...

Nice release pal.
Maybe I'm doing something wrong but is not working for me... That's what i did:
Downloaded from MS my localized image and installed it (I don't have the emulator installed, just the image).
Already downloaded my english ROM (in my case, TNT 5.0)
Did the GO stuff in this way "GO <localized-Image> <TNT5-ROM>
Then flashed the resultant ROM and it is still in English...
... What I did wrong?
Could you please post a detailed explanation (if it is possible with printscreens) about this process?
Sorry but I'm a little dumb using this one...
Regards and keep on doing this great job!

@com_reg
Does it translate all content of the ROM, incl. OS and OEM applications?
Click to expand...
Click to collapse
It basically translate the OS and some HTC applications, but due to the high number of versions around, it is safe to only transalte the OS part. I've experienced problems with some HTC applications not displaying properly after translations. So you better make some tests excluding or not some files / dir from Muiver. I'll try to release a more flexible Muiver soon
@danny de w
Open a DOS prompt and type "GO <name of the MS image>.bin nk.nbf"
@cesarr4
Did you move your old nk.nbf in a different place ? The script renames it in nk-old.nbf but this is sometimes not enough: the update utility will still pick the old one in place of the new one. The easiest solution is to move the nk-old.nbf away from the microwave dir.
@JouSePo and ALL
I am at work right now and can't take pictures, I will do a better explanation with images when I'll be at home later. By now I can try to explaint it better by words:
During the process some applications will pop-up asking you to do something:
- the first one is the MuiVer, that automatically looks for the right directories in the MS dump and copies it over the image that needs to be translated, modifying some files and making thinghs you don't have to care about. At this stage you only have to choose, based on your (future) experience, what you want to copy and what not. The more you copy, the most will be translated, but you may experience more problem (missing texts, or applications that goes blank screen).
- The second application is a notepad instance, opened on your initFlashfiles.dat. This file contains the localized name of some system directories and especially the start menu. I suggest you to take a look to the initflashfiles present in the microwave\dump.src dir that is the localized version for your language and change the one in the notepad accordingly. The only part that REALLY NEED to be changed is the name of the "startup" dir (i.e. in italian it must be changed in "Esecuzione automatica") otherwise your rom won't start the customization (no screen alignment, no initial settings .. etc etc..)
- At this point the script will have built the nk.nb file that must be translated in a nk.nbf file in order to be flashed. This is done with the last program that opens up : nb2nbf. You will find a set of row in the middle of the screen, check the first checkbox in the first line and in the box on the right pick the nk.nb file from the microwave dir. On the same line choose OS in the combobox on the right and then just click on the text box on the left. A number will appear, it is all ok. Now click on translate and you're done.

Nice printscreens smogdragon!
Thanks!
I have a question:
Which .BIN file should I use? The installed file from Microsoft extracted the following .BIN files:
PPC_ESN.BIN
PPC_ESN_GSM_QVGA_VR.BIN
PPC_ESN_GSM_SQUARE_VR.BIN
PPC_ESN_GSM_VGA_SQUARE_VR.BIN
PPC_ESN_GSM_VGA_VR.BIN
PPC_ESN_GSM_VR.BIN
All of them with same size... Which one should I use for my QTEK A9100 (Wizard)???
Thanks in advance!

In addition to my previous post, I'm getting the following error message when click on "GO" button at MUIVER program (see attachment).
What is going on? It doesn't happens when using Beta2 release.

@cesarr4
PPC_ESN_GSM_QVGA_VR.BIN is the best match with wizard's hardware.
As for the error, I've never seen that But I can see on the command prompt that you had a previous error "acces is denied". I would try to start clean, deleting dump and dump.src directories. Ah, be sure to have administration rights. Let me know

thanks for your prompt responses and your help.
I flashed the resultant rom to my Wizard and it is working fine but some issues arised with built-in apps. By example, the phone app doesn't start and built in software keyboard doesn't show up...
I was wondering if it is possible to extract the OS part from the MS image and pack it into a nk.nbf file and flash it (I mean, do not transkate a existing rom but using the OS inside the .bin file and flash it to the device)...
it is possible? what can be the side-effects doing that?

hello smogdragon
i tried using cmd and it work t for a little bit when i deed everything you said it say that it cant find this file cant find that file it cant find muiver nothing get recognized by cmd
but its all in the same dir and the image file too

1st try at the kitchen, and I can only fry some eggs....

Hi guys....
I've been a member of this comunity for 2 years now, but posted very litle, because I would be mostly spamming, re-interating what others have said, with" wow, this is fast...nice job"...and such..so i only post when I realy have to.
I downloaded the hypercore kitchen, and after some reading of the contained links and txt files, decided to have a go at it...
I would like to target Tomal's v8 but although very fast, it seems to have a significant number of com bugs...So maybe I'll go with v7.7...
I copied the nk.nbf file to the correct directory, and ran the decoder, but it errors on the next step saying that there is no OS.nb file...
Should this file be extrated from the nk.nbf?
Is this a problem with the nk.nbf file I'm using?
I would apreciate some help on this, as I'm looking for a full flavored cake, but to my taste...see I'm "diabetic" so I have to be extremly caution with what I cook...

When you decoding nk.nbf, decode it to OS.nb (change second line) instead nk.nba.

Something else to be aware of with Tomal's ROMs is that he ships all his RGUs in a single RGU.cab file.
You'll need to extract the contents of this file into the dump directory AFTER the imgfstodump and BEFORE the pkgtool step.
-PJC

Thanks for the quick answers, guys...
Something pop-up as a doubt...can I cook from an usb stick?(installing the kitchen, and workind directly trought the usb stick)???

I'm getting starved.....I can't even turn on the oven...
I have nstaledthekitchen over and ove again.
Changed the settings so it reads "Universal", copied the nk.nbf of my choice to the Extract/source folder, and whent to the Panel/extract and runned "DumpRom"...So far so good....
The DOS windows warns me that the file must be in the correct folder, so I double check....I press return...HTC Extender Rom Tool starts and prmpts me what I want to do and were is the extended rom...I thought it was embeeded in the nk file, but since Tomal provided with and empty extenden Rom, I downloade it and poited to it...Hit decode...
A big window opens with some file paths, so I check them to know were the files are going to...and using the above tip, change the name of the fat file to OS.nb, Hit decode...I'm happy, the window says "Decode sucessfull", so I hit "OK"...
I am agin at the Htc Extended Rom tool, so I hit exit(? done it right ?)...
The Dos window now tells me that it cannot find the ON.nb(? Didnt I just created it?)....
So I'm stuck....
The constructions workers haven't yet finished furnishing my kitchen, so I have no ingredients to work with....
Any chef willing to help me make a simple meal?????

psapg said:
I'm getting starved.....I can't even turn on the oven...
I have nstaledthekitchen over and ove again.
Changed the settings so it reads "Universal", copied the nk.nbf of my choice to the Extract/source folder, and whent to the Panel/extract and runned "DumpRom"...So far so good....
The DOS windows warns me that the file must be in the correct folder, so I double check....I press return...HTC Extender Rom Tool starts and prmpts me what I want to do and were is the extended rom...I thought it was embeeded in the nk file, but since Tomal provided with and empty extenden Rom, I downloade it and poited to it...Hit decode...
A big window opens with some file paths, so I check them to know were the files are going to...and using the above tip, change the name of the fat file to OS.nb, Hit decode...I'm happy, the window says "Decode sucessfull", so I hit "OK"...
I am agin at the Htc Extended Rom tool, so I hit exit(? done it right ?)...
The Dos window now tells me that it cannot find the ON.nb(? Didnt I just created it?)....
So I'm stuck....
The constructions workers haven't yet finished furnishing my kitchen, so I have no ingredients to work with....
Any chef willing to help me make a simple meal?????
Click to expand...
Click to collapse
With HTC Extender Rom Tool you must extract nk.nbf not ext_rom, and when extracting name it OS.nb (i thing it is 2nd line in tool)

Perhaps the would-be chef should read a cookery book?
There's a very, very good guide in this forum, which is what I started off with and had no problems whatsoever, but I can't for the life of me remember if it was beasty or thingonaspring who wrote it (apologies to the real author if I missed them out!). It also includes some fixes for the batch files.
Remember - the wiki and search are your best friends...
PJC

Hi Again...
The construction workers finaly had done some real work, so now my kitchen is properly furnished with all the CABinets i need...so now to try to cook me a simple meal, and try to learn from it....

Can't rebuild Ranju 7.7
Hi all.
I gave it a go and tried to rebuild Ranju 7.7.
I could decode it, dump it (yes, I extracted the contents of RGU.CAB to the dump directory), convert the dump to packages etc. So far, so good.
But when I tried to rebuild it, the ImgfsToNb tool gave this error message:
"Partition with file system 0x01 found after IMGFS partition. It's safer to abort here, sorry."
What should I do now?

jandevries12 said:
Hi all.
I gave it a go and tried to rebuild Ranju 7.7.
I could decode it, dump it (yes, I extracted the contents of RGU.CAB to the dump directory), convert the dump to packages etc. So far, so good.
But when I tried to rebuild it, the ImgfsToNb tool gave this error message:
"Partition with file system 0x01 found after IMGFS partition. It's safer to abort here, sorry."
What should I do now?
Click to expand...
Click to collapse
imgfstonb doesn't seem to support the FLASH disk that's in Tomal's ROMs. I don't know what he uses, but when I've based things on his work, I use a different 'donor' OS.nb for the imgfstonb stage. Obviously, I lose the FLASH disk, but as I don't use it anyway, that's not an issue for me.

^^ yup, exactly, it is due flash disk.

Ok, I understand.
But what is the "donor" os.nb used for?
I've extracted the OEM, SYS en XIP parts. Isn't that enough to compose a new ROM?
What parts are re-used from the original os.nb? And must an alternative donor os.nb be of the same version/build?

jandevries12 said:
Ok, I understand.
But what is the "donor" os.nb used for?
I've extracted the OEM, SYS en XIP parts. Isn't that enough to compose a new ROM?
What parts are re-used from the original os.nb? And must an alternative donor os.nb be of the same version/build?
Click to expand...
Click to collapse
As I understand it (and I'm sure someone can correct me if I'm wrong), the donor OS.nb is used as a 'template' for storing the IMGFS into an NB structure. As far as I've been able to tell, pretty much *any* OS.nb from *any* ROM can be used as the template.
Basically, imgfstonb takes 3 arguments - the imgfs file itself, a 'donor' OS.nb, and the 'target' OS.nb final output. This is all hidden by the scripting, but is what I've found by playing with the underlying utilities.
The only restriction I've found is that ROMs that contain Flash disk can't be used as the donor OS.nb.
PJC

Could one of the senior members of this forum please comment on pjc007's statements above?
Is it correct that the donor os.nb is only used to determine the right structure for the ROM?
(I'm asking because I got the impression from other posts on this excellent site that the donor os.nb is used as source for the XIP part, but I don't know for sure)

Well, I have the same matter now, I really want to cook sth to use the way I want a rom to be and share with others as I feel really bad just to download, I hope to upload my own rom and share but I read the instructions again and again , look for sth on the internet, download all the things to my PC that will be used to cook, still not certain what I'm going to do.
My question is if I cook a bad rom, then I up it to my EXEC, Is there any chances for it to die ? Or simply just install another well-known rom to rescue it if my rom jail to boot?

Rom Files

Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.
my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.
i am frustreated man and really need help.

Tambuyeye said:
Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.
my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.
i am frustreated man and really need help.
Click to expand...
Click to collapse
When creating packages with Package tool it creates the following folders:
SYS
OEM
Missing <-- Thats what you are looking for.
I suggest that if this is your 1st attempt and you are building based on a custom rom, use HyperCore Kitchen. Its very easy to use and does the extraction much quicker and easier than doing it by hand. Once you have the hang of it then just move your stuff to another kitchen. Nice part about HyperCore you can dump just about any rom if you set it for that specific device. Just a note: some cookers protect their roms and you end up with almost everything in Missing. You can dump WizFlo from 6.1.1.3 upwards easily

When you have run the PkgTool - Build Packages option, don't mistaken the Missing Manifests for the same thing as Missing Files or Missing Packages. The missing "dsm" manifest files the Pkg Tool refers to are contained in the XIP files (which you will be doing next, i.e., extract XIP). So, you can just ignore the Missing Manifest message and continue on, however be aware that you must use compatible XIP that contains these "missing" dsm manifest files when you go to re-build your rom.
If there are indeed missing packages or missing files, it will tell you exactly what they are and where (what folder) they are supposed to go into. These missing packages/files will be in the dump folder along side the OEM and SYS folders after you run the Build Packages option in the PkgTool app.
This took me a while to realize as it was not explained (or at least I did not see it anywhere) in the various forums/threads on rom building.
If I am wrong on any of this someone please correct me as I too am relatively newbie to this and still learning.
Good Luck!

µkitchen to add custom files into protected rom

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?