Database Info

Share your OEM Packages for Faria ROM Kitchen

Hey all,
So that we don't all have to reinvent the wheel, is it possible where we could share OEM Package setup info to be used in the Faria ROM Kitchen. I know a number of your are adding your own packages, and this could save a lot of work for those of us just starting to look at customizing this tool. Use ftp://ftp.xda-developers.com/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf to read up on how to create OEM packages and how they work.
What I'm thinking is that this thread could be a repository for packages (not for requests, but for packages people want to share). Bascially you would reply to this thread with what the package is for, and any special information and setup (or things people may want to look at and change), and then attach a zip file (or pointer to the package file) that people can then download and put into their devwiz folder. If its for a commercial (non-free) program, leave out the commercial program / dlls but just to have the other files setup and instructions on what to put into the folder could be very useful for people.
When you provide the packages, try to provide it with the original package.rgu and/or package.dsm filenames (not with the GUID that was generated for you). People will then be able to just run the buildos.exe and the GUID will get created for them without changing filenames. Then just edit the options.xml file to use the newly generated GUID.

so screenshot + cab + short info + status: freeware/shareware/etc. would be fine?

mfrazzz said:
Hey all,
So that we don't all have to reinvent the wheel, is it possible where we could share OEM Package setup info to be used in the Faria ROM Kitchen. I know a number of your are adding your own packages, and this could save a lot of work for those of us just starting to look at customizing this tool.
What I'm thinking is that this thread could be a repository for packages (not for requests, but for packages people want to share). Bascially you would reply to this thread with what the package is for, and any special information and setup (or things people may want to look at and change), and then attach a zip file (or pointer to the package file) that people can then download and put into their devwiz folder. If its for a commercial (non-free) program, leave out the commercial program / dlls but just to have the other files setup and instructions on what to put into the folder could be very useful for people.
The only tricky thing here would be the guid for the files. I'm still new to this, so if someone has an idea how to handle that (maybe the person does the package.rgu and runs the program where it generates the guide, then unzips the files and modifies the guid to the new one in the right places).
Click to expand...
Click to collapse
The GUID is so simple, if you to use a package, just go to http://www.famkruithof.net/uuid/uuidgen . Then you just get a new GUID and paste it in all the different palces in the package, then you dont have to chnage file names then have them chnaged again by buildOS
I thik this is a good idea, would be good to share and also good for problem finding, cus i have one that i cant for the life of me get the today plugin to work how it is meant to!!!

GSFinder Package
[... This package has been updated and can now be found in post 23 of this thread ...]
This is a package for GSFinder. This is a freeware file manager (like TotalCommander).
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.

MoDaCo NoData
[... This package has been updated and can now be found in post 23 of this thread ...]
This is a package for MoDaCo NoData. This is a freeware program that allows you to turn off and on what data sources will work on your device (so if you don't have a GPRS plan, you can turn off GPRS so your phone will not use it).
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.

mUn Keyboard Skin
This is a package for the mUn keyboard skin. This is a freeware skin file to modify the look of the on screen keyboard to be like what is in the mUn aRTM WM6 rom.
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
NOTE: If you have other keyboard skin files in your OEM directory, you may get an error when you build this initially (or if more than one is selected). You can only have one of the keyboard skins selected.

XPlore Keyboard Skin
This is a package for the XPlore keyboard skin. This is a freeware skin file to modify the look of the on screen keyboard to be like what is provided for the XPlore 2.0 WM6 rom.
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
NOTE: If you have other keyboard skin files in your OEM directory, you may get an error when you build this initially (or if more than one is selected). You can only have one of the keyboard skins selected.

mfrazzz said:
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
Click to expand...
Click to collapse
Thanks for putting this together!
I tried building via your instructions, but got an error (buildos.exe crashed). I deleted the options.xml file and then re-ran the build and it worked. Then copied back in an options.xml file and edited the GUID and it ran fine.
I'd noticed this when I was building another package. In my experience, I have to do a build without the options file, let the [GUID].dsm file get built, then create the options.xml file with the correct GUID in it and then rerun.

saeba said:
Thanks for putting this together!
I tried building via your instructions, but got an error (buildos.exe crashed). I deleted the options.xml file and then re-ran the build and it worked. Then copied back in an options.xml file and edited the GUID and it ran fine.
Click to expand...
Click to collapse
Yep I figured this out an hour ago. The options.xml should be renamed until the first run of builos.exe completes, then rename it back and change the guid inside the file.
I'll redo the packages tomorrow and update the instructions on them.

mfrazzz said:
Yep I figured this out an hour ago. The options.xml should be renamed until the first run of builos.exe completes, then rename it back and change the guid inside the file.
I'll redo the packages tomorrow and update the instructions on them.
Click to expand...
Click to collapse
Can i jst say that the chnace of the same number being used again in you kitchen is really high, so you should not have to chnage it!!! Try run the buildOs without chnaging anything!

Has anyone figured out how to move files yet?

RickoT said:
Has anyone figured out how to move files yet?
Click to expand...
Click to collapse
The initflashfiles.txt moves the files (doesn't just make duplicates). So you just have to put a line in for everyfile to "move" it to a different location. The next post will be for BatteryStatus and you can look at that one as thats what it does. All the graphic images are moved into a directory it creates.

Battery Status Package
[... This package has been updated and can now be found in post 23 of this thread ...]
Here is the package for Battery Status. I initially put this together but had some errors in how I did things. Thanks to ADB100 for cleaning it up! This is the same one he reposted for me in the Faria Rom Kitchen thread.
ALso going with Funman's point that its unlikely to hit a duplicate GUID, so I'm leaving the GUID alone. So just extract to the OEM directory and you are ready to go.
This package contains Battery Status 1.04.202 Beta 3 Build 0195 (latest version at the time of this posting).
Reposting with generic Registry Entries (removing ADB100's custom settings he mentions in his post below)

WM5torage Package
[... This package has been updated and can now be found in post 23 of this thread ...]
Package for WM5torage (version 1.73). Just unzip in your OEM folder.
Note, the package puts a shortcut in the \Windows\Start Menu\Accessories folder for WM5torage. Edit the initflashfiles.txt if you want the shortcut to be located someplace else.

mfrazzz said:
Here is the package for Battery Status. I initially put this together but had some errors in how I did things. Thanks to ADB100 for cleaning it up! This is the same one he reposted for me in the Faria Rom Kitchen thread.
ALso going with Funman's point that its unlikely to hit a duplicate GUID, so I'm leaving the GUID alone. So just extract to the OEM directory and you are ready to go.
This package contains Battery Status 1.04.202 Beta 3 Build 0195 (latest version at the time of this posting).
Click to expand...
Click to collapse
I should note that it is pre-configured with the following options:
General Tab - Show CpuSpeed, Show Mobile Operator
Indicator Tab - Show more Indicators, Use Small Fontsize, Show Powerdrain, Show Temperature
Tools Tab - DeviceLock on Wakeup, Lock if Display..., Backlight fix - 30-seconds
Omap Tab - Overclock to 247Mhz, Overclock on Wakeup, Remember last CpuSpeed, Overclock after reboot
Traylaunch Tab - All disabled
Not sure this will suit everybody so be warned...
Andy

Adobe Reader LE
[... This package has been updated and can now be found in post 23 of this thread ...]
Package for Adobe Reader LE. This is the "faria Adobe Reader" cab thats been posted, but then I've altered the .rgu to fix the registry entry for opening docs that have spaces in the name (Thanks ADB100 for pointing that fix out), and made a couple of fixes to the initflashfiles.txt (it had moves for files that didn't exist and I've added where it moves a shortcut into \Windows\Start Menu\Programs\Accessories
Just unzip into your OEM directory.

ADB100 said:
I should note that it is pre-configured with the following options
[... snip ...]
Not sure this will suit everybody so be warned...
Click to expand...
Click to collapse
I've reloaded the zip file in my post above for Battery Status and put the registry entries back to generic like a fresh install. If you want specific settings, then install BS, tweak it to your heart's content, then dump out the registry entries and replace them in the .rgu file.

mfrazzz said:
Package for WM5torage (version 1.73). Just unzip in your OEM folder.
Note, the package puts a shortcut in the \Windows\Start Menu\Accessories folder for WM5torage. Edit the initflashfiles.txt if you want the shortcut to be located someplace else.
Click to expand...
Click to collapse
Sorry mate but your package is not right! The .rgu was not setup right!

funman said:
Sorry mate but your package is not right! The .rgu was not setup right!
Click to expand...
Click to collapse
Arrrgh! Sorry about that. I was putting that one together and got interupted with a concall at work, and some other things. I went back to working on it, and I guess I didn't edit and fix what I thought I had done... Sheesh...
Thanks...

mfrazzz said:
The initflashfiles.txt moves the files (doesn't just make duplicates). So you just have to put a line in for everyfile to "move" it to a different location. The next post will be for BatteryStatus and you can look at that one as thats what it does. All the graphic images are moved into a directory it creates.
Click to expand...
Click to collapse
Are you sure, because I think I read in faria's rom thread that it copies the files, not moves them, (Unless im utterly retareded and misread it, which is very possible)

How to Cook a Rom

Okay after reading through a few threads on XDA I thought I might take a stab at writing a Simple tutorial of the knowledge I know of cooking a rom
Step 1: Download a kitchen of your choice I think the Kitchens from Matt are the best to use only my recommendion
Step 2: Download the OEM packages you'll need..Leave them in a different folder then the Kitchen right now..
Step 3: Make a OEM folder in the kitchen folder if theres not one already and place it in the kitchen folder
Step 4: Take the OEM packages from the desktop and drag the ones needed for your rom
Step 5: Click Build OS check the files your going to have in your ROM to be built..if it errors look at where it errored and check the OEM package to see if it meets the standered below
Step 6: Now add any thing you need to edit in the dump or replace files (EX: Welcome Screen, themes, initflashfiles.dat file ect)
Step 7: Now run the CreateROM.bat once finished you'll have a new file in the temp folder
Step 8: In the kitchen there will be a nb2nbf_wizard.exe if not search the forums..open that model ID will say Wizard.. change the language to WWE then on the bottom you'll see empty fields..those are self explanatory pick OS for the ROM then locate the file in the TEMP folder of the Kitchen
Step 9: Now once its finished translating where ever the output direction was it will be your file to flash, now move that to the RUU and flash and say Hello to your own Cooked rom
PS Steps will varies from Kitchen to kitchen but this covers the jist of basic ones
nows for the complex parts how to make an OEM package...Information from double_ofour
Step 1: Vist http://www.famkruithof.net/uuid/uuidgen the Create UUIDs of another type should be set to Version 4: random then a code like this "6bfb7458-6a83-450a-9da5-b5feabba8335" will be made
Step 2: make the code the name of the 2 text files you have in the OEM package folder, Change one Text file extension to RGU and the other DSM
Step 3: now the RGU is where the Reg hacks are the first line MUST be REGEDIT4 then you list your Reg hacks.. in the formate like this
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\MASD]
"TaskManager"="1_5_29968_1"
Step 4: Leave a space after the last reg hack and save as UNICODE
Step 5: add any files to the OEM package Folder they will be put in the /Windows directory
to make an extension into the programs folder you should edit the initflashfiles.dat
How to edit the initflashfiles- Should be done between useing the Build OS and Create Rom
Step 1: open the file with note pad
Step 2: remove any lines that aren't needed..sometimes you'll see likes to create a folder for a shortcut when your not using the program
Step 3: add a line to create a shortcut for a program from your own OEM package...Most packages here already do it for you
sigh I'm tired of typing but theres a basic out line of what cooking a rom consists of..feel free to add anything I might of missed
Just thought I'd help out anyone looking to cook a rom and needs a little guide
Please don't ask for help here..I'm not text support..I think there shoul dbe one thread for all cooking questions..you guys could even use the thread when i asked for help
PS again thanks to all the people here at XDA that made cooking simple easy even ifs making a OEM pack or a fix or even a kitchen thank you all

thanks ANTC!!!

thanks dude! can we have pictures too? (what the heck - had to ask )

thanks this is EXACTLY what I was looking for

mattk_r said:
thanks dude! can we have pictures too? (what the heck - had to ask )
Click to expand...
Click to collapse
sigh..sure once i can release my full touch rom using your kitchen

so no deal matt...lol not like you need a tut how to make a rom...maybe you could help with the cam issue to for my rom

everytime I click buildos.exe I get an error. No matter what folder I try it in, it just wont work.

How do I dump an official rom?

maybe some one can help you with the dump question its hard for me to put into words since core does it by it self
and th build os problem is something to take up with the maker of ur kitchen try doing a windows update you may need sp2 or net framework

I suggest making this thread sticky, removing all unnecessary posts, including this one and transform it into an How To thread. Where everybody can post tutorials on different aspects of rom cooking.
dferreira said:
How do I dump an official rom?
Click to expand...
Click to collapse
Same you do with an unofficial one lol The difference is that you won't find any missing files and that means less work for you.

anichillus said:
I suggest making this thread sticky, removing all unnecessary posts, including this one and transform it into an How To thread. Where everybody can post tutorials on different aspects of rom cooking.
Same you do with an unofficial one lol The difference is that you won't find any missing files and that means less work for you.
Click to expand...
Click to collapse
It won't dump using your kitchen... Try the last oficial RUU Prodigy of WM5 and you'll see that it seems to be protected, since it can't extract the 8004000 :s

anichillus said:
I suggest making this thread sticky, removing all unnecessary posts, including this one and transform it into an How To thread. Where everybody can post tutorials on different aspects of rom cooking.
Same you do with an unofficial one lol The difference is that you won't find any missing files and that means less work for you.
Click to expand...
Click to collapse
Coming from you thats a huge compliment..

what can i do if i want to add programs like TNT, i have few apps compared to mfrazz's build or TNT and now if i add 1 more program in my kitchen it crashes the buildimgfs.exe, anything i can do to add more? i am using faria's kitchen tool

nycelitemaster said:
what can i do if i want to add programs like TNT, i have few apps compared to mfrazz's build or TNT and now if i add 1 more program in my kitchen it crashes the buildimgfs.exe, anything i can do to add more? i am using faria's kitchen tool
Click to expand...
Click to collapse
Try using Core kitchen that should do the trick

hopefully as a newbie I can make my own rom with this
and please do help me if i encounter any problems
thanks in advance

Personally, I would suggest doing a topic like this in the Wiki. Then have a topic here that is stickied to point to the Wiki entry.
Here's a page I started for the Faria Kitchen last May. http://wiki.xda-developers.com/index.php?pagename=FPRK_Cooking_Instructions
You could take what ANTC posted and merge with the info I provided and come up with a nice generic page for cooking )most of the kitchens work the same since they all use basically the same set of tools).
Here's a page on making OEM packages that da_jojo added on:
http://wiki.xda-developers.com/index.php?pagename=FPRK_Creating_ROM_Packages
BTW: If you do the instructions in the Wiki then any / all of us can help maintain it (where posts here can only be maintained by the original poster).

i think this is good for those who already know how to cook, but too brief for beginners who know little about cooking a rom.

My problem when building the rom is when it is finished this error comes up
"c:\DocumentsandSetting\M541378\ApplicationData\hIqInc\PPC-BuildOS\9.05.3.0Temp\ROM\XIP"
so in my ROM folder there is no XIP, I create the folder, and I re-create, it and then the XIP folder erases. I have no idea why this happens? Can anyone please help....

Updating rom image USING FARSTONE DRIVE CLONE
Hi all i'm new at the forum, i would like to know if i can create an image with farstone drive clone of all the programs i have and configurations and then upload it to the phone?? I would like that even if i have to perform a hard-reset on the device it would still have all the progs and configurations created on the image uploaded.
Any suggestions are welcomed!!!!!

hi, I am a newbbiess... i am totally not understand what do u mean by kitchen... but i am intrested in generate a ROM myself.. please advice..

[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

[Kitchen] [Nov 6th, 2008] NATF the Kitchen: AT&T and HTC Editions

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.

Adding some Apps to a ROM ?

Hi!
After a lot of flashing and reading I became sure, that there are a lot of great ROMS out there, but not the excatly one I would like to get
Well so I tried the JustMe kitchen and everything works well. Now I came to the point to add own applications to the ROM, so I created some OEm folders with Packagescreator, just like explained in the wiki.
now comes my problem: Most of them don't work...
When I want to use them in BuilOS form JustMe kitchen, I get different errors:
e.g. "the setup.dll is already at temp\dump\ and the process stops.
Now I want to learn what can I do if I have some files needed for more than one application? Would be great to hear from someone who would like to help a new "cook" (well, it's just editing a rom) with this problem!
Thanks
ruebyi

You can just delete the extra setup.dll files in the OEM folder.

Hi! Thanks ivan!
So all files I have too often I can delete from one of the OEM packages? that helps a lot!
But now I get the next error:
The target File \temp\dump\gx.dll is not a file but a folder (translated from the German error warning)
What means that? It is a *.dll file in the OEM folder of MortPlayer AND there is a folder called gx.dll in the temp\dump\
Any chance to "fix" this?
I uploaded the OEM folder I want to integrate in JustMe
ruebyi

ruebyi said:
Hi! Thanks ivan!
So all files I have too often I can delete from one of the OEM packages? that helps a lot!
But now I get the next error:
The target File \temp\dump\gx.dll is not a file but a folder (translated from the German error warning)
What means that? It is a *.dll file in the OEM folder of MortPlayer AND there is a folder called gx.dll in the temp\dump\
Any chance to "fix" this?
I uploaded the OEM folder I want to integrate in JustMe
ruebyi
Click to expand...
Click to collapse
It is one of the duplicate error you have earlier. One of them is in package format and the other is in binary format. You can delete the one in your OEM.
To comment on your original post. All the packages converted by oem package converter works. Only you need to look at the files that will be processed after the installation. For example, when installed, some files will be copied into /Program Files/my_program folder. In order to do this in OEM package, try to find out what files need to be moved manually and copy them using initflashfiles.txt in your OEM package. Hope this help and enjoy cooking!

live4nothing said:
It is one of the duplicate error you have earlier. One of them is in package format and the other is in binary format. You can delete the one in your OEM.
To comment on your original post. All the packages converted by oem package converter works. Only you need to look at the files that will be processed after the installation. For example, when installed, some files will be copied into /Program Files/my_program folder. In order to do this in OEM package, try to find out what files need to be moved manually and copy them using initflashfiles.txt in your OEM package. Hope this help and enjoy cooking!
Click to expand...
Click to collapse
A great Thanks!
Now I was able to build the *.nbh, but after flashing the Mortplayer can't find it's MotImg.dll. this *dll is not located in the OEM folder and is not listed in the initflashfiles.txt I'm really confused at the moment!
I didn't find a tutorial on this kind of problem! Was I to stupid to search, or is there none? Would really like to see one, so I don't have to bother you for every little probelm
ruebyi

ruebyi said:
A great Thanks!
Now I was able to build the *.nbh, but after flashing the Mortplayer can't find it's MotImg.dll. this *dll is not located in the OEM folder and is not listed in the initflashfiles.txt I'm really confused at the moment!
I didn't find a tutorial on this kind of problem! Was I to stupid to search, or is there none? Would really like to see one, so I don't have to bother you for every little probelm
ruebyi
Click to expand...
Click to collapse
Were you able to install and run successfully with the original .exe in the same rom? What I usually do in converting to OEM packages is that check the rgu generated by OEM converter, then look at all the references, either change all the pathes to /windows/ or fix them in the initflashfiles.txt. Maybe if you can attach the original, I can take a look. I am kind of busy to search around for the apps you a trying to convert.

live4nothing said:
It is one of the duplicate error you have earlier. One of them is in package format and the other is in binary format. You can delete the one in your OEM.
To comment on your original post. All the packages converted by oem package converter works. Only you need to look at the files that will be processed after the installation. For example, when installed, some files will be copied into /Program Files/my_program folder. In order to do this in OEM package, try to find out what files need to be moved manually and copy them using initflashfiles.txt in your OEM package. Hope this help and enjoy cooking!
Click to expand...
Click to collapse
Thanks that you care about that issue at all!
I managed to do it with TCPMP 8.1, HomeScreen++, Nodata, Minimal dialer
What I "need"/want to add:
MortPlayer
MortScript
After that I would like to integrate my own skins for some of these apps, but this, I hope, will be easier...
I was not able to upload the files, don't know why, so I give you here the Links:
MortScript
MortPlayer
THANKS a lot!
ruebyi