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)

OEM Package Tutorial [Updated 2008-01-31 - New wiki layout]

Hello!
I thought I'd contribute back to the Kaiser community by starting a wiki page with what I've discovered about packages while cooking and cleaning my own ROM.
12-07-07 Update: Major overhaul with more content! Great read for all cooks and chefs...
OEM Package Tutorial​
If you have any comments or questions about this tutorial, please reply to this thread. Thanks!

Nice, thanks!

_Alex_ said:
Hello!
I thought I'd contribute back to the Kaiser community by starting a wiki page with what I've discovered about packages while cooking and cleaning my own ROM.
Most of the material I've read is outdated and scattered, so hopefully this will save time for novice chefs.
Please note that this is the first draft / rough outline. More content to follow...
Kaiser OEM Package Tutorial
Click to expand...
Click to collapse
Great
Really good contribution... I'll add a link in the KaiserKitchen second post...
Cheers.

Nice Work...
Its always nice to see some of the newer members active and contributing. The write-up is good and I think it will help a lot of Rom "Sous" Chefs as they start experimenting with their own creations.
BTW, thanks for the kudos. The best pay-off is seeing that my efforts have inspired others to strike-out on their own. I also want to say good work on adding a Wiki page instead of just leaving the info in a thread somewhere.

Great guide.
Makes me want to try it.​

Just go to my signature, i have wrote it too,.

Garmin, that's a great tutorial for the manual process for converting OEM packages to cabs.
Just wanted to make sure you're aware that Ervius package creator automatically converts cabs into the following, which makes things alot easier:
initflashfiles.txt from file structure found in cab
links found in .inf and/or setup.xml
randomly generated UUID
rgu from setup.xml or .inf
option.xml
Hope this helps.

_Alex_ said:
Garmin, that's a great tutorial for the manual process for converting OEM packages to cabs.
Just wanted to make sure you're aware that Ervius package creator automatically converts cabs into the following, which makes things alot easier:
initflashfiles.txt from file structure found in cab
links found in .inf and/or setup.xml
randomly generated UUID
rgu from setup.xml or .inf
option.xml
Hope this helps.
Click to expand...
Click to collapse
hehehe,.
thanks buddy,.
but many people dont understand it like you did,.

yeah agree nice one mate, Great idea.

True, i do build upon existing works to inform folks of the most efficient way to build an OEM package...
I've added your tutorial into the wiki page as a 'primer', should anyone not understand my text.
Maybe I'll find the time to write my own primer, or someone else could take up the challenge?

Folks, all in good intention but the Tutorial is fairly steep.
I don't consider myself is all thumbs but plowing through them is going to be not just a week effort and at the end it is still in monkey see, monkey do level.
To put it in a simple way, (I will stand for correction). Most people who strode around this forum is only expected to spent "Basic" level in stead of "C++" level programing effort to get what they want or solve their problem. Most will only have the ability to play with a few different ROM's but not to cook them. I really like Palm, it is much simpler and much faster machine for given same horse power. But its founders just grabbed the money and went fishing and left it to rot and we have to entertain M$.

My intent was not to write a tutorial understandable by all, as clearly stated within the preface. The tutorial is geared towards intermediates who have already dabbled.
The tutorial that's missing is the ROM kitchen one. In the ROM Kitchen thread, jcespi2005 says he has one in the works, so I didn't want to step on his toes. When that comes out, I would hope for it to be alot easier to understand than my intermediate OEM package tutorial.

I've done a major overhaul to this tutorial, knowing that more people will be reading it with the release of the Kaiser ROM Kitchen tutorial...
It should prove to be a good read for all interested in building OEM packages.

Need help for not able to convert .cab to Package
I was trying to convert some .cab files into Packages using Ervius Package Creator. Following the instruction 1. Click on "Open CAB file" and select a cab file to convert.
Then I just pick a .cab file (tried different ones but same error message)
Before I could go to the 2nd step of "Extract CAB files with original names in a folder", I got the error message:
x Erreur d"insertion de ligne RichEdit
I can't read Italian ?!
What went wrong?

jychan28 said:
I was trying to convert some .cab files into Packages using Ervius Package Creator. Following the instruction 1. Click on "Open CAB file" and select a cab file to convert.
Then I just pick a .cab file (tried different ones but same error message)
Before I could go to the 2nd step of "Extract CAB files with original names in a folder", I got the error message:
x Erreur d"insertion de ligne RichEdit
I can't read Italian ?!
What went wrong?
Click to expand...
Click to collapse
Hi... I went to google translate and translated the french error message from MSCEINF which means 'Error of insertion line RichEdit'. This doesn't mean much to me either
If you run MSCEINF.exe, click on the first icon cab with the caption 'Choose a CE installation file', open the cab and click on the icon with the caption 'Extract CAB Files with original names in a folder', does the same thing happen? If so, you may need to ask the original author. His thread is here: http://forum.xda-developers.com/showthread.php?t=347397&highlight=msceinf
Hope this helps...

Alex, I downloaded all you files and setup all the file directories as described. I downloaded more packages.
I want to add a few more .cab and needed to convert them into packages.
It was frustrating for hours. I have re-download the MSCEinf.exe file a few times.
I Unziped it and renamed it to MSCEinfen.exe as instructed.
Then click on packages creator 5.4.exe, check the boxes as instructed.
Click on Open cab file, select a .cab file in one of the directory, then it automatically execute MSCEinfen.exe and the error message poped
I even tried to execute packages creator 5.4.exe in a DOS black box. Same problem and same result.
Click on anything else will eventually cancel the procedure and back to square zero.
What could be the problem?

I Got The Same Problem.
I'm confidence that I strictly follow the instruction of converting cab to OEM package, and got the same error message like you do.
I try to translate the message with google, looks the language is French translated to English as "Error inserting line RichEdit".

Good News, I just solved this problem in my machine.
I changed the "Language for non-Unicode Program" to "English (United State)", the error message gone, and my MSCEInfEn works well now. I not sure it works for everybody, welcome to post with your result, maybe in other language. Thanks.

Anyone getting an Unhandled exception error after clicking on "Go"? I've done the following:
1) DL and Extract kaiserkitchen
2) Extract the build/package tools (3 files) to the folder where I installed kaiserkitchen
3) DL and Extracted AT&T Ultraclean ROM folders (3 folders) to the kaiserkitchen folder
4) DL and extracted AT&T OEM packages
When I start up the program I can select the AT&T OEM Packages. I left at default and hit Go but get the unhandled exception error.
Also, it doesn't seem like the AT&T OEM Packages contains any Registry Tweaks. Is there a separate package to dl that contains the registry tweaks? A few days ago I know there was an AT&T OEM package that had the registry tweaks.
I'm attaching a capture of the error. Appreciate any feedback.
Thanks.
Update:
I tried doing this again with ROM Folders and AT&T OEM Package I downloaded on 12/8/07 and it works fine. No error when building as outlined above.
-Mike

ecltech said:
Anyone getting an Unhandled exception error after clicking on "Go"? I've done the following:
1) DL and Extract kaiserkitchen
2) Extract the build/package tools (3 files) to the folder where I installed kaiserkitchen
3) DL and Extracted AT&T Ultraclean ROM folders (3 folders) to the kaiserkitchen folder
4) DL and extracted AT&T OEM packages
When I start up the program I can select the AT&T OEM Packages. I left at default and hit Go but get the unhandled exception error.
Also, it doesn't seem like the AT&T OEM Packages contains any Registry Tweaks. Is there a separate package to dl that contains the registry tweaks? A few days ago I know there was an AT&T OEM package that had the registry tweaks.
I'm attaching a capture of the error. Appreciate any feedback.
Thanks.
Update:
I tried doing this again with ROM Folders and AT&T OEM Package I downloaded on 12/8/07 and it works fine. No error when building as outlined above.
-Mike
Click to expand...
Click to collapse
See these posts: http://forum.xda-developers.com/showpost.php?p=1745239&postcount=105, http://forum.xda-developers.com/showpost.php?p=1747265&postcount=117 & http://forum.xda-developers.com/showpost.php?p=1747298&postcount=119. Alot more info can be found in that thread, so you might want to read up there...
Hope this helps...

Create OEM Packages

Hey guys I would love to make some OEM packages from Cabs, but when I try InitFlashFiles Generator it just exits and doesn't work. So how do I create initflash and .rgu s ?
Important is how do I create the .rgu names? Just random? The initflash is not a problem!
Problem solved: http://www.famkruithof.net/uuid/uuidgen

you could try ervius package creator

Yeah I tried that before, but it exits with an error! It's ok now, I just create the initflash manually!

I would love to use it, but when I extracted the cab with MSCEInfen.exe and close it, I get an error and the initflashfiles tab doesn't open when I click continue and I can't open it manually! It looks like the same error you get when you open it! Any ideas?? It is a pain to create all by yourself!

http://forum.xda-developers.com/showpost.php?p=1761005&postcount=405
try that link, i think it might be his latest creator judging by the date
so here is what i do to use the program
i run the creator in its folder or by a link
i place my cabs in a different folder
click on open cab
browse for the cab
click on extract cab (zip icon without any extras on it)
click ok
click msce icon (running green man icon)
change options or click done
change options or click complete package
and that should be it hopefully

Thank you very much, this one works very good. With the last version I had an error with this one it works!

Question about language package

I have extract language 0804 from China Mobile ROM and sort it into OEM and SYS, however, there is no "Language_Simplified Chinese" folder under OEM, hence, when I try to cook my own ROM, I can't find Chinese options.
Can any one let me know how to build the the folder "Language_Simplified Chinese" and make the options visible?
Thanks in advance!

There is no such folder in the original ROMs, you have to create one. Look at the other language packs (are you using the language kitchen for new guava or the vox kitchen 0.3??). There you should find a .dsm and a .rgu (rgu s are hidden) and a option.xml. Just copy them to your "Language_Simplified Chinese" folder and then rename the dsm and rgu to ce2bca2e-da07-4123-9e20-87dc3dcf032c.dsm and ce2bca2e-da07-4123-9e20-87dc3dcf032c.rgu Then go into the option xml, there you will find a line with the former name of the rgu change it to ce2bca2e-da07-4123-9e20-87dc3dcf032c . Also change the line for the name to Chinese.. Then you have to go into the rgu (with editor) there you have to change all the language codes to the code for Chinese, but only change the codes for the former language, because English has to stay in, English is either 0409 or 0809!

Many thanks.
Yes, I am using kitchen to cook the rom. However, when I try to build the rom, it reports an error that "temp\dump\mixpcold_smartphon_1.provxml" already exist.
Then what can I do?

Search for the file, it should be in the ROM twice somewhere in the sys or oem folder, delete one, if it is in an oem package delete that not the one in sys.

Thanks again.
I have successfully build the rom and flash to the Vox, but the display just squares, neither Chinese nor English.
Can you please tell?

Hm, can you upload all your language files, just zip and attach them, I'll see what I can do!

Great appreciate your help.
I've uploaded file in /Smartphone/Vox/Vox Kitchen 0.3/languages/
Please check it.

Do you have a Chinese keyboard layout or is it a normal English qwerty? Maybe I have found your mistake! I'll upload once you have told me about the keyboard!

It is normal English Keyboard.

OK I am uploading, wait 5 minutes and it's done! Again I don't know if it'll work at all, because it is not from the same ROM version!

It's done!

frauhottelmann said:
OK I am uploading, wait 5 minutes and it's done! Again I don't know if it'll work at all, because it is not from the same ROM version!
Click to expand...
Click to collapse
Any way, more than thanks.
One more question.
I have dumped the original rom into three raw files. Can I flash this files back? If so, How?

I am sorry I don't know. Nobody here has tried it and reported back, but people keep asking it. It should (!) work when you just extract it to OEM and SYS folder, place that in the kitchen and run it, but as I said I don't know if it works!

I think a raw file (or was it a bin ?) can also be directly flashed with pdocwrite.exe but I have never tried that. Search for it on the forum or with google and be cautious with it.
Please report here if you are succesfull

Yeah, because if it works we could write a Wiki article. Did the new language pack work?

Unfortunately, it is not work.

Any more ways to help me out?
What I guess it because of wince.nls file. It it Chinese support file. I can find it after flash, but I can't find in folders before I cook them. Do you have any idea?

[20931 SYS/ XIP Ported]Improved PackageTools and BuildOS now for Wizard [29/11/2008]

I have been using many kitchens over the past year. Cooking horrible roms, decent ones and now a pretty good one. My problem was always the various tools lying all over my hard drive. Luckily I came across this litte gem by Ervius
Package Tools and BuildOS rolled into one. I also noticed that it handles rgu files much better than the previous BuildOS, it choked on an incorrect rgu file. Which in turn allowed me to get Video working in HTC Album 2
I have modified the batch files for our Wizards and have been cooking and im loving it
PackageTools+BuildOS (Latest combined version)
rgu-2-xml : Convert .rgu to provxml files
SYSVersion : Generates a version list of your SYS Folder
All the usual build tools :G'Reloc, M'Reloc, ImgFS Tools
AllPackagesToOne - Protect your rom from being ripped apart and the whole world being able to share in your utter cooking brilliance, via a tickbox ofcourse
Automatic Find and Fix duplicate file errors during BuildOS process
More features which I am either too lazy to list or dont use at all
Just add SYS,ROM and OEM folders. It also have a nice feature which allows you to select OEM Packages and save it as a preconfigured rom. Extra OEM packages can be placed in a Packages folder. BuildOS will load those files also (No more OEM's all over your hard drive).
BuildOS also runs G'Reloc during the dump process, but for good measure I also included it in the batch file.
Also added -conservative to the Imgfs Tools portion of the script to protect against overcook
BuildOS generates pretty log files which shows where stuff went wrong
Extract the zip file. Run Kitchen.exe and watch the magic at work.
Note
For some reason the output window text is black on a black background, but at the top is a nice running status. If not sure just hilight the output window.
If you start up and It complains about folders just create them
Download
Ported 20931 SYS/XIP without PIE 6 download
Microsoft Visual C++ 2008 Redistributable Package (x86) is need to be installed in your PC
[URL="http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&DisplayLang=en]Get it here[/URL]

Hi,
Nice kitchen.
But its little bit difficult compare to hypecore.
Thanks for great kitchen.

Nice release ..i think im gonna start cooking too

Does it also have my favourite tool "Alpackagestoone" to remove and merge DSM and RGU files from Rom?

Noonski said:
Does it also have my favourite tool "Alpackagestoone" to remove and merge DSM and RGU files from Rom?
Click to expand...
Click to collapse
It does, in the prettiest little tick box you have ever seen, just below the Output Window. One of the really cool features of this version of BuildOS is the ability to scan for and fix duplicate files

sounds really impressive! downloading...
I'll recook my rom with it and let you know how it went

where should I extract this kitchen?
Error: pkgdll is missing
Never mind. copied it to the same folder as the kitchen.exe

I cant cook... .net problems
Many problems with the kitchens... why I cant install .net frameworks more than 2.0 that i have why... cause It said on every reinstalation missing file the installer will be quit! GOD DAmn... I think I need to reformat my PC and almost backup 40 GB info or... does anybody has an utiliti that erase all of anay program that stucks on uninstall or repair or install? i need to kill those .Net frameworks.

+ Que PPC said:
Many problems with the kitchens... why I cant install .net frameworks more than 2.0 that i have why... cause It said on every reinstalation missing file the installer will be quit! GOD DAmn... I think I need to reformat my PC and almost backup 40 GB info or... does anybody has an utiliti that erase all of anay program that stucks on uninstall or repair or install? i need to kill those .Net frameworks.
Click to expand...
Click to collapse
What OS are you running on your pc ? .net 2.0 and higher really like XP Sp2. Do a google search for CCleaner and "Uninstall Utility" this might help before you format dude.

Errors I am facing:
can not find \ROM folder
Windows can not open this file: OS.NB.Payload
Windows can not open this file: OS.NB.extra
BuildOS: Error, can not find ROM Folder!!!
Where are these files supposed to go? can you provide a tree map?
Can you also tell me what exe opens what file?
I'm almost having to pour cold water over my self
The main issue is not knowing where the ROM folder is supposed to go.
Also, not being able to see what the thing is doing (black on black) is really frustrating me also.
When you get a chance, let me (us) know how to use this cooker. it looks like it can do a lot more than I'm used to... but at the moment I am finding it useless.

S.V.I said:
Errors I am facing:
can not find \ROM folder
Windows can not open this file: OS.NB.Payload
Windows can not open this file: OS.NB.extra
BuildOS: Error, can not find ROM Folder!!!
Where are these files supposed to go? can you provide a tree map?
Can you also tell me what exe opens what file?
I'm almost having to pour cold water over my self
The main issue is not knowing where the ROM folder is supposed to go.
Also, not being able to see what the thing is doing (black on black) is really frustrating me also.
When you get a chance, let me (us) know how to use this cooker. it looks like it can do a lot more than I'm used to... but at the moment I am finding it useless.
Click to expand...
Click to collapse
I really wish I could decompile and just fix the black on black issue. Coz it is a simple case of just changing the font. Unfortunatly it is not written in .net like the previous BuildOS, so no luck there
This should be your default layout:
Base Folder-
->Compile Tools (OS.nd encoding tools)
->Flash (Created by Batch file, your new OS.nd ends up here)
->OEM (I like to put the BASE OEM Folders in here OEMAPPS etc)
->Packages (This is where I drop my custom OEM folders)
->ROM (OS.nb XIP,romhdr.bin lives here)
->SYS (Yeah well we know this one)
The error you are getting is when you try and extract a rom with Package Tools in the kitchen. Here is the procedure:
Create a base folder, I normally use Base_Buildnumber_Device
Select your Dump Type in the bottom check boxes, either a folder where you have already dumped a rom or an *.nb,*.nbf type file
Start your kitchen and select Open on the Package Tools tab.
Browse to the folder you have just created select the folder of rom file based on the above selection
Package tools will now extract the rom and create OEM and SYS Folders if possible
In case of cooking which I believe you are after:
Create the above folder structure with all files in place
Select BuildOS tab
Click Load Rom
Edit OEM's etc and just press Go

thank god u placed this tut, i thought i was the only one with theis prob oO
I'm almost having to pour cold water over my self
Click to expand...
Click to collapse
you were "almost" but i already did several times, what more do you expect if your working on Core,Improved Pakagetools, Molski Devpack,tnt kitchen and Porting :S

ather90 said:
thank god u placed this tut, i thought i was the only one with theis prob oO
you were "almost" but i already did several times, what more do you expect if your working on Core,Improved Pakagetools, Molski Devpack,tnt kitchen and Porting :S
Click to expand...
Click to collapse
Dude I battled to get the whole thing running as the tut's where for Kaiser and the tools were abandoned by the looks of it. But once i started using the cool right click and import package features I was sold.

Sorry. double post.

->ROM (OS.nb XIP,romhdr.bin lives here)
That may be what I am missing. how do I extract that?
I Have OS.nb; XIP.bin XIPfolder

@S.V.I Here is the romhdr.bin : http://forum.xda-developers.com/attachment.php?attachmentid=131286&d=1227164342
@cornelha i think u need a break lol you attached te file in the siff thread

->ROM (OS.nb XIP,romhdr.bin lives here)
Click to expand...
Click to collapse
should the XIP be in the bin extension or in a folder the one which Hyper Core Generates) ?

ather90 said:
@S.V.I Here is the romhdr.bin : http://forum.xda-developers.com/attachment.php?attachmentid=131286&d=1227164342
@cornelha i think u need a break lol you attached te file in the siff thread
Click to expand...
Click to collapse
OMFG dude I think you are right. Dev by day ... cook by night ... hey wtf is my gf ?!?!?

how to use this kitchen??
i run Kitchen.exe from desktop, but error(installation error)
any help me??

fachry said:
how to use this kitchen??
i run Kitchen.exe from desktop, but error(installation error)
any help me??
Click to expand...
Click to collapse
Yeah I realised now that when I zipped up the Kitchen I left pkgcommon.dll in the Tools folder, this should be copied to the same folder as Kitchen.exe.
Your error however comes from me not stating the .net Framework 2.0 or highers is required. I take these for granted since I have Visual Studio installed on my machine anyway