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)

Need some help from the community.

Im looking for a cab file with only the files and registry entries for ArcSoft MMS 3_5_1_17. Also I keep getting the Customer Feedback thing launching. Where all do i need to remove the ceipui.exe. I delete the exe and the entries in default.hv. I have also removed them from 1f1aca24-d942-464a-9281-10567741499c.rgu
I would also like to know if someone can help me out with a cab for the latest Midlet manager out there.
Thanks ahead of time.

For midlet manager try with this cab: http://forum.xda-developers.com/showthread.php?t=286604
Ciao

Ok, so i am building this rom. how can i make sure that it runs my provxml files and rgu files upon flashing?

Hi, Have you made an oem package for Midlet Manager?
Eventually can you share it?
Thanks,
Slump

slumpolo said:
Hi, Have you made an oem package for Midlet Manager?
Eventually can you share it?
Thanks,
Slump
Click to expand...
Click to collapse
I've got an OEM for it in the kitchen, check my sig.

nottoosmart said:
Ok, so i am building this rom. how can i make sure that it runs my provxml files and rgu files upon flashing?
Click to expand...
Click to collapse
.rgu is pretty much guarenteed if it's in the SYS or OEM folder, as long as there's no options.xls file in the folder with it ( and there's a .dsm file with it with the same guid).
As for the provxml, I haven't figured out what fires it off...

so im not the only one having trouble with this new bild and MMS..I think the last MuN rom is better more stable

Porting T-Mobile Shadow's Chome plugin to other devices.

Hello.
I'v trying this for a couple of hours without effects.
Dumped rom, builded modules with PKGTool. Files are in OEM/Oemdrivers and SYS/Chome. It does't run by just copying. Need some way to regsvr dll files. Because Chome plugin is accesing partial plugins by GUID.
Anyone have idea?

I did the exact same thing. I haven't had any time to try anything else because I have finals next week. I'll let you know if I get anything

To all helpfull shadow users
Can some T-Mobile Shadow user backup those registry keys?
all those are in HKEY_CLASSES_ROOT\CLSID\
Code:
{D7B35490-A4B2-4ef4-BF8D-332C4979F14E}
{892B90CB-9806-427e-8BED-F45C6A9E576B}
{E98FBDCC-6664-4c5b-BB62-20932ED37762}
{C5A51777-B837-447d-8947-FAF3FF9D570B}
{3FD3C828-753F-48f9-BEA9-6201F64B5F58}
{06BC7E69-CE13-4028-9454-C27A32F56197}
{4F612B1A-E470-4b31-9386-AC396AEDAAF9}
{1DE8DD6B-D74D-4d2e-A8C3-72439F2B8402}
{D3303B00-DB12-4bbb-A0CD-D5DAD41E2DFC}
{634CA962-22D8-4671-BBC7-BAC47148A4B6}
{D51A48AA-1F22-4aee-A4D1-B215C504550D}
{74D7FEB8-0DA7-485a-AB4F-4D12E6338758}
{4B998C14-3801-4a8e-9B20-5DFE58B19C39}
{7B4E69B9-C032-4134-81BE-D6F360B30576}
or better just backup HKEY_CLASSES_ROOT\CLSID\ and send me PM - I'll sent my mail.
You can use Registry Workshop to do this.
Those keys don't contains any personal information or settings so it's safe- don't worry.
//////////////////////////Edit////////////////////////////////
I've recieved all CLSID from [email protected]://allshadow.com forums but still no luck...

I'll be getting my own Shadow in a couple of days. I can do the backup then. Once again, I don't have much time to do anything else because of school and a robotics team I'm on.
Nice job finding those keys!
When I tried flashing my first rom with all of the CHome plugin stuff in it, the ROM flash to the wizard stopped at 78%...

I uploaded all the plugins and .png + reg entries that seems to be used with the chome home screen. all files are here:
http://www.esnips.com/doc/14b31b95-2c8f-4ae9-a6c9-1453df7d05e6/shadow
copy all the files in Windows to Windows folder. Add all the registry entries and copy T-mobile_basic_blue to Application Data\home\ folder.

Once I've tried to put all the files to my phone, I even got all the regedits (or maybe I've missed something) and I just got a white space on my homescreen.

how do i add the registry's to my phone?? do i add them with a reg edit app??

kingroach said:
I uploaded all the plugins and .png + reg entries that seems to be used with the chome home screen. all files are here:
http://www.esnips.com/doc/14b31b95-2c8f-4ae9-a6c9-1453df7d05e6/shadow
copy all the files in Windows to Windows folder. Add all the registry entries and copy T-mobile_basic_blue to Application Data\home\ folder.
Click to expand...
Click to collapse
could you post this on the ftp site? for some reason, the captcha phrase on esnips is having problems and i can't create an account. Thanks!

rafyvitto said:
how do i add the registry's to my phone?? do i add them with a reg edit app??
Click to expand...
Click to collapse
You cannot normally import .reg files on smartphones. However Resco Explorer from resco.net can do that.

kingroach said:
I uploaded all the plugins and .png + reg entries that seems to be used with the chome home screen. all files are here:
http://www.esnips.com/doc/14b31b95-2c8f-4ae9-a6c9-1453df7d05e6/shadow
copy all the files in Windows to Windows folder. Add all the registry entries and copy T-mobile_basic_blue to Application Data\home\ folder.
Click to expand...
Click to collapse
Have You manage to run this plugin on non shadow device?
Files are easy to extract but make it work does not.

I tried on qtek 8500. It doesn't run and after reset the device stucks. Need a hard reset to factory defaults to work again. fortunately I had a backup.

I just got my own T-Mobile Shadow and I found out that you need to have a .scheme/.home XML file that sets the plugin. I think it's called cmhome.home. Also, you need cmhomeres.dll.0409. I'm going to try adding these in to the rom...
...unless they are already there and I haven't noticed

any update.. can i have a copy of the rom u builded thx

ND4SPD said:
I just got my own T-Mobile Shadow and I found out that you need to have a .scheme/.home XML file that sets the plugin. I think it's called cmhome.home. Also, you need cmhomeres.dll.0409. I'm going to try adding these in to the rom...
...unless they are already there and I haven't noticed
Click to expand...
Click to collapse
Yes we actually know that chome is part of theme, about that MUI and other many many files too.
Can You just post orginal Shadow rom.

melgurth said:
Yes we actually know that chome is part of theme, about that MUI and other many many files too.
Can You just post orginal Shadow rom.
Click to expand...
Click to collapse
i got it u need it?
here u go http://rs81.rapidshare.com/files/73516772/S730_ROM_Dump__PKGTool_.rar

Can somebody upload new Shadow update to rapidshare?

I'll post it as soon as I get home. School's proxy blocks FTP upload/download and exe files.

Rom link: http://www.megaupload.com/?d=5GART6H6. Sorry I forgot to upload before

Thanks for posting the new ROM!
I had some success with the old one here:
http://s2.photobucket.com/albums/y15/GnatGoSplat/3125Shadow/
It was a complete ROM port though. I'll see about making a CAB when I have some free time.

cant wait wanted it since shadow came out...i have s620 will it work with landscape

[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

Uni ROM Kitchen v2.0 by Tomal: Next generation Kitchen for Universal

Guy's,
This is my 2nd attempt to build a useful kitchen for Uni lovers. It uses a new set of tools and technology and you can customize/cook the rom exactly the way you like it. Porting or building XIP was a real pain but the kitchen builds the XIP and IMGFS together and importantly without manual intervention.
I believe this is the easiest kitchen ever built for Uni and you'll simply enjoy it.
The OS has been included in the kitchen is a fresh new Core - CE OS 5.2.21014.
OK, let's go for working part -
Unrar the kitchen in any of the drive in your PC (but must be in root) and it should look like - D:\TML_UNI_KITCHEN.
You'll find a command script "build_rom.cmd" under the TML_UNI_KITCHEN directory. Now, make a coffee, then just hit on this script and reluxe. Your ROM will be cooked within couple of minutes. Well, a little dialog box will pop-up at the asking what to do, select Encode to encode the rom and then exit.
You can follow the encoding steps like:
>>Encode>>Browse>>open nk.prj>>Encode>OK>>OK>>Exit.
Now, got to RELEASE directory, open ROMUpgradeUt.exe and flash the ROM to your device.
Advance part -
You can modify few parameters under the build_rom.cmd to make your custom rom.
set BUILD_TYPE=Regular
This is the type of your ROM to be cooked. The value "Regular" has an association with the directory \TML_UNI_KITCHEN\EXT\Regular. Put all the packages here, those you want to include in Regular build.
set BUILD_TYPE=Vanila
The value "Vanila" has an association with the directory \TML_UNI_KITCHEN\EXT\Vanila. Put all the packages here, those you want to include only in Vanila build.
PLease note, packages under the Regular directory will not be included in Vanila build and vise versa. There is also a Common directory inside the \TML_UNI_KITCHEN\EXT. You can put the packages here, those you want to include in Regular and Vanila both the builds.
set BUILD_NO=21014
This is the build number of the rom. The value "21014" has an association with the directory \TML_UNI_KITCHEN\21014. Actually you can put any value you want but whatever value you put must be associated with the same directory. Importantly SYS and XIP must be located under this BUILD_NO directory, i.e. \TML_UNI_KITCHEN\21014\SYS, \TML_UNI_KITCHEN\21014\XIP.
ROM template located under the \TML_UNI_KITCHEN\ROM directory.
OEM drivers located under the \TML_UNI_KITCHEN\OEM directory.
ROM will be transfered to \TML_UNI_KITCHEN\RELEASE directory after the successful build.
Directory Structure:
\TML_UNI_KITCHEN\21014
\TML_UNI_KITCHEN\21014\SYS
\TML_UNI_KITCHEN\21014\XIP
\TML_UNI_KITCHEN\21014\romhdr.bin
\TML_UNI_KITCHEN\EXT
\TML_UNI_KITCHEN\EXT\Common
\TML_UNI_KITCHEN\EXT\Regular
\TML_UNI_KITCHEN\EXT\Vanila
\TML_UNI_KITCHEN\OEM
\TML_UNI_KITCHEN\RELEASE
\TML_UNI_KITCHEN\ROM
\TML_UNI_KITCHEN\ROM\nk.nba
\TML_UNI_KITCHEN\TOOLS
\TML_UNI_KITCHEN\build_rom.cmd
Please note the kitchen is still in beta so you may notice some unwanted thing which I haven't noticed earlier. Also, the XIP inject part has not been finished yet. But it's not a big deal and not necessary for the current build.
You can easily inject it using Bepe's Xiptool if you want. Just pick the xip.bin from "temp" directory after the build, rename it to xip_out.bin and write to nk.nba.
There is also some other secret thing which I forgot to mention and love to forget.
Acknowledgment:
Major credit goes to Bepe as it was not possible to built this kitchen without his great tools.
Uni Kitchen v2.0 (beta):
http://vidmes.com/xda/Uni/ROMs/Tomal/TML_UNI_Kitchen_2.0_Beta.rar
http://vidmes.com/xda/Uni/ROMs/Tomal/TML_UNI_Kitchen_OEM.rar
Cheers!!!

Gr8 news Tomal.
Thx 4 you hard work.

Good job!Thanks!

Hm, i tried to start kitchen, but unfortunately getting error:
Code:
PLATFORMREBUILDER Copyright (c) 2008-2009 bepe Jan 4
Build: Regular
Locale: 0409
Preparing release structure...
... done!
Collecting standard packages and initializing hives...
XIP: 3 packages
IMG: 71 packages
Error: 0x8000000a
'initflashfiles.dat' does not exist in the specified paths!
ERROR! (errorlevel: 1)
Press any key to EXIT

I get the same initflashfiles error. It occurs in this command line:
.\tools\platformrebuilder.exe
in .\tools\buildOS.cmd

Same error here.. :/ If there is a fix it looks pretty good! Well done, Tomal

opppppsss...my mistake!
I forgot to include the OEM pack. Don't worry, I'll upload it asap.
Update:
OEM part has been uploaded (in 1st post). Extract it under \TML_UNI_KITCHEN directory.
regards

tomal said:
[...]
There is also some other secret thing which I forgot to mention and love to forget. [...]
Click to expand...
Click to collapse
LOL how nasty
gonna try and study it...
thx a lot for your work! hope my little donation was appreciated more than simple words

Wonderful!!!! Thank You
And with VInit help we can add flashdisk until he gets a way to make combined storage work for G4.

this could be the start of something new for uni lovers, many tnx tomal

Thanks a lot Tomal!
Hopefully on my vacations I can get into it!
Cheers,

Great work, Tomal I have just one question. I started build_rom.cmd and after some time a window pop-uped asking for HTC64 EXT rom... and there were 3 options : Encode, Decode and Exit. Afraid of doing something wrong I clicked Exit. Can you give some instructions how to continue the process and if there are any additional settings to make.
Thanks in advance .

simeonfilipov said:
Great work, Tomal I have just one question. I started build_rom.cmd and after some time a window pop-uped asking for HTC64 EXT rom... and there were 3 options : Encode, Decode and Exit. Afraid of doing something wrong I clicked Exit. Can you give some instructions how to continue the process and if there are any additional settings to make.
Thanks in advance .
Click to expand...
Click to collapse
Select Encode>>browse (to open the project file)>>open nk.prj>>Encode>OK>>OK>>Exit.
Cheers

Thank you! I just flashed with the Vanila ROM and it seems to be very good - it's fast, after soft reset there is ~28 mb free RAM. Again - thanks for your hard work .

it's possible to do a multilanguage/region kitchen? almost for common applications and configuration applets.
thx.

tomal said:
Please note the kitchen is still in beta so you may notice some unwanted thing which I haven't noticed earlier. Also, the XIP inject part has not been finished yet. But it's not a big deal and not necessary for the current build.
You can easily inject it using Bepe's Xiptool if you want. Just pick the xip.bin from "temp" directory after the build, rename it to xip_out.bin and write to nk.nba.
There is also some other secret thing which I forgot to mention and love to forget.
Click to expand...
Click to collapse
I tested it, and its working fine 100%, 1000 thanks Tomal for the great work!!!! I also used the optimize tool from HyperCore kitchen and the final nb.nbf is only 44M, but what about the XIP is it in my new rom or is it not and if not how do I inject it? I tried the implantxip tool from the TOOLS directory but I seam to not getting it how it works. Please help!!!

With the OEM directory in place, this kitchen produces great ROM's!
Thanks Tomal!

Thanks Tomal !
May i know how to use your kitchen to dump other ROM ?
Very appreciated your reply !!!
Thanks & Regards,

Upload This ROM
Can you guys help in uploading a ROM produced by this kitchen new Core - CE OS 5.2.21014
I would like to try it out.
Appricated ...

Vanilla nk.nbf
Here you are Fast and stable :]