[Full Guide Thread] TNT.Kitchen for Wizard, Auto XIP Porting and Modules Relocating - 8125, K-JAM, P4300, MDA Vario ROM Development

hi,
As promissed, this is my special Kitchen for Wizard users and chefs. This kitchen is based on Bepe kitchens with some edits on nb file and batches to work well with our Wizard devices.
With this kitchen and guide, all beginners can going very fast to be an expert, so this is suitable for all (experts and beginners).
===============================================
Change Log:
5-Aug Update: 5.2.20273 build 5.2.20273.1.3.3 SYS and XIP (check 2nd post).
13-May Update: 5.2.19213 build 5.2.19213.1.0.4 SYS and XIP (check 2nd post).
29-Apr Update2: 19202 buid added in downloads post as SYS and xip.bin.
29-Apr Update1: another CreateROM.bat to cancel combining all packages to one.
28-Apr Update: date of creating this thread.
===============================================
Kitchen Advantages:
- Real porting for xip in auto mode (no need for write addresses or whatever)
- Auto Relocating for modules (no need to edit .VM folder in SYS)
- All dsm will be combined in one dsm (so, windows folder has only one dsm, no overloading, and this will save more than 1 MB from the Kitchen)
- All RGU will be auto encrypted.
- The kitchen will give you a notice that your packages are overload (no need to flash to test).
===============================================
Requirements:
- you have to download: Microsoft Visual C++ 2008 Redistributable Package.
- Wizard Device.
- SYS folder from the build you want to use.
- OEM folder which contains Drivers and your packages.
- XIP modules from the build you want to port.
- Give some credits if you plan to share your releases.
===============================================
How to start cooking:
1- Extract TNT_Kitchen_for_Wizard to C: dirctory on your PC.
2- Copy SYS folder you want to use to the Kitchen.
3- Add your OEM packages to OEM folder.
4- Run BuildNB.bat.
5- wait until BuildNB.bat shows "press any key to continue".
6- go to nbf folder.
7- run nb2nbf.exe.
8- in Language, choose WWE.
9- tick File #1 and then choose your 80040000-OS.nb file.
10- go to Image Name and choose OS.
11- on the right top corner, choose Translate.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
12- open nbf folder and run Vista_ROMUpdateUtility.exe if you have vista operating system, or XP_ROMUpdateUtility.exe if you have XP operating system.
===============================================
Some Hints:
- How to know that your packages is larger than what you have to load??
- if you see this msg, so you have to remove some packages:
- How to minmize SYS folder Size??
- there are many of useless packages located on SYS folder, try to see what you don't need and remove.
===============================================
How to port XIP from any new build:
- extract xip.bin from the build you want to port from.
- Download Bepe xip port
- extract xipport to any folder
- the folder should contain XIPPort.exe, pkgcommon.dll, and xip.bin you want to prot. (i will put xip.bin from different new builds)
- run XIPProt.exe
- press Dump xip.bin
- you will have OUT Folder
- press Make Pkgs
- now, open OUT folder, you will have Files and Modules.
- for each folder (Files and Modules) copy MSXIPKernel and MSXIPKernelLTK contents (Note: without .txt files) and paste them to /ROM/XIP folder and replace.
- now, if you cook, you will have the new build with real port.
===============================================
How to port SYS from any new build:
Just extract SYS folder from the new rom you want to use its SYS folder, and paste the new SYS to the kitchen (you have to see the suitable extracting kitchen from the device you want to get SYS folder from it, and also i will upload SYS folder from any new build to direct use)
===============================================
Which OEM Drivers and Apps can you use:
you can search for this yourself, and there are many of them, you can use boy_de_ghet from Here, or use double_ofour OEM which can be found here, also Faria thread contains good OEM (but maybe old). on these packages, you can use Drivers and apps with no problems for Wizard ( OEM_Lang_0409, OEMAPPS, OEMDrivers, OEMMISC, OEMOPERATORS, WinCENLS_WWE...)
from other devices, you can use OEM packages from mattk_r packages (without using the drivers located on that OEM Folder, because they are for Hermes only) the thread can be found here, also maybe they are a little bit old, but you should find something intersted. (you cannot use
OEM_Lang_0409, OEMAPPS, OEMDrivers, OEMMISC, OEMOPERATORS, WinCENLS_WWE.. which are for Hermes Device, just get the other packages)
===============================================
Some Packages should be located in OEM to make your rom bootable:
your OEM should contains: OEM_Lang_0409, OEMAPPS, OEMDrivers, OEMMISC, OEMOPERATORS, WinCENLS_WWE (maybe this will be in SYS) and SecurityOff. also, maybe LangDB and Default packages.
All mentioned above are suggestions (maybe experts know about that more than beginners)
===============================================
How to make new packages for your own:
you can learn that yourself by searching and learning, it is very simple but needs nice relax from you, i suggest to read Faria thread to learn how to create your own packages. another very useful thread by double_ofour can be found here

Downloads:
========================
TNT_Kitchen_for_Wizard: contains the base kitchen without SYS and OEM. the orioginal XIP in this kitchen is 5.2.19209
Rapidshare
========================
5.2.19209 SYS Folder: contains SYS folder extracted from Kaiser, just copy SYS to the kitchen
Rapidshare
=======================
29/Apr update1
CreateRom without combining all packages to one: all you need to do is to download this file and put CreateROM.bat in TOOLS folder and replace.
=======================
29/Apr update2
XIP.bin from 19202 build: as mentioned before, use xipport.exe to extract this xip and read guide to know where to extract and what to extract
Download
SYS from 19202 build: just copy SYS to the kitchen
Rapidshare
=======================
13/May update
XIP.bin from 19213 build: as mentioned before, use xipport.exe to extract this xip and read guide to know where to extract and what to extract
Download
XIP Folder from 19213 build: this is the whole folder of XIP which should be located in Rom folder, so just remove the older one and paste this one.
Download
SYS from 19213 build: just copy SYS to the kitchen
Rapidshare
=======================
5/Aug update
XIP Folder from 20273 build: this is the whole folder of XIP which should be located in Rom folder, so just remove the older one and paste this one.
RapidShare
SYS from 20273 build: just copy SYS to the kitchen
RapidShare

Notes:
- you have to unlock your device before flashing, for more details in flashing notes visit this thread.
- i'm not responsible for any damage on your device.
========================================
Important Links:
- How to determine if your Wizard is a G3 or a G4
- CID Unlock your G3 Wizard (Only for Wizards with less than AKU2)
- Easy guide to CID unlock G3 Wizard
- Solution for CID Unlocking G3 Wizard with AKU2 or higher
- CID Unlock your G4 Wizard Hard-SPL
- CID Unlock your G4 Wizard Soft-SPL
- Unlocking and Upgrading G3 Wizards
- Howto flash a Wizard... a little tutorial!
- How to SIM unlock the Wizard
- HOW To Change the Pagepool (WM5)
- HOW To Change the Pagepool (WM6)
- XDA-Wiki for Wizard which contains huge informations needed.
Credits:
- ofcourse first one is Bepe for his great tools
- tom_condon for helping me on so many things in cooking
- misar for his tools in relocating modules
- all the nick names i used in this thread (faria, double_ofour, boy_de_ghet, mattk_r, and vippie)
- for jwzg for the good arrangement in our forums.
================================
i hope you get some useful tools and informations to learn and improve your cooking.
Good Luck and have a nice cooking .
================================
if you don't have the time for cooking, you can download any rom, feel free to see my sign. and click on the latest wizard rom mentioned there.

Perhaps I should build my own. This should be interesting.
Thanks man, you always do a great job.

Please creat kitchen buit 19701 new !!!!
OS 5.2.19701
Vesion clean !

Done.
i will update the thread with the suitable informations and links to keep our working better.
if you think that there are some of useful threads just let me know to edit my posts .
good luck guys .

amsatnetg said:
Perhaps I should build my own. This should be interesting.
Thanks man, you always do a great job.
Click to expand...
Click to collapse
ofcourse you have to build your own (if you have the time)

c28langthang2010 said:
Please creat kitchen buit 19701 new !!!!
OS 5.2.19701
Vesion clean !
Click to expand...
Click to collapse
where is this??
point me and let me do it for you .

well done it's right, i am going to see if i can cook using your kitchen. I was completely clueless when it came to porting a "real" rom from one device from another so i can now see the light. This definately deserves to be a sticky!! thanks again

newbie1221 said:
well done it's right, i am going to see if i can cook using your kitchen. I was completely clueless when it came to porting a "real" rom from one device from another so i can now see the light. This definately deserves to be a sticky!! thanks again
Click to expand...
Click to collapse
you will use it with no problem at all, and i'm sure you will increase your packages size (in case of dealing with 19209 SYS by removing the useless packages from it).
Good luck bro .

Nice Kitchen! I ported 19701 and it works greats! But now the SYS folder... The 19701 from PDAVIET is protected. Can someone provide it or knows how to extract it?

j.vd.spank said:
Nice Kitchen! I ported 19701 and it works greats! But now the SYS folder... The 19701 from PDAVIET is protected. Can someone provide it or knows how to extract it?
Click to expand...
Click to collapse
is it difficult?
about the protuction, no one can open it.
any rom will be cooked using the kitchen here can't be extracted, PDAVIET used the same tools included on this kitchen

its right said:
is it difficult?
about the protuction, no one can open it.
any rom will be cooked using the kitchen here can't be extracted, PDAVIET used the same tools included on this kitchen
Click to expand...
Click to collapse
Not difficult... I can share if someone is interested, but without SYS folder its 'useless'. So we have to wait when someone releases a kitchen

j.vd.spank said:
Not difficult... I can share if someone is interested, but without SYS folder its 'useless'. So we have to wait when someone releases a kitchen
Click to expand...
Click to collapse
i don't prefer the builds that not provided by microsoft, many of builds are hacked like 19400 and yours, so i don't think you will find SYS folder simply.

Very well done wise man!
I'm going to start on my own and report the results later
Thanks a lot for sharing

epimazzo said:
Very well done wise man!
I'm going to start on my own and report the results later
Thanks a lot for sharing
Click to expand...
Click to collapse
you are welcome, have a nice cook man .

its right said:
Downloads:
========================
TNT_Kitchen_for_Wizard: contains the base kitchen without SYS and OEM. the orioginal XIP in this kitchen is 5.2.19209
Rapidshare
========================
5.2.19209 SYS Folder: contains SYS folder extracted from Kaiser, just copy SYS to the kitchen
Rapidshare
=======================
Click to expand...
Click to collapse
The two links are to the same file.....
Andy

nice job =D
i'll try it myself

ADB100 said:
The two links are to the same file.....
Andy
Click to expand...
Click to collapse
no they are different
but after editing , thanks for that.

Itsright,
Got little confused...
During cooking process, only DUMP is created together with log.txt. That's all found inside temp folder. Shouldn't expect boot.rgu and nb file? I added my own stuff like OEM and SYS parts. no issues here.
XIP is also already in but didn't got your point related to OS.NB.PAyload.
What actually does it mean?
Maybe I should review something left behind...
I appreciate other comments too...
Rgs

Related

[KITCHEN][04/Jan/11]ELF(in) Kitchen(s)[ONLINE]

INTRO
I started trying to make a kitchen for our Elves based on bepe's Extended Kitchen and Elf(in) Hybrid Kitchen was "born".
Since then, bepe released his famous PlatformReBuilder(PRB) and I followed him, creating B2 Kitchen (page41 and on).
The Hybrid Kitchen is discontinued but I will keep it posted here for anyone who wants to play with it.
B2_Kitchen has started as an Elf(in) kitchen, but became a multidevice kitchen.
B2_Kitchen has started as a simple batch-file kitchen, but became a multifunctional kitchen.
At the end it is a GUI based on command-line tools just like some other visual kitchens.
The main applications are PlatformReBuilder and ImgfsTools.
So I don't actually feel that I made something new...
I take no credit!
CREDITS TO
bepe for the kitchens and other tools,
pof for the USPL, cmonex for the HSPL,
itsme , mamaich & tadzio for the brilliant but simple tools,
ervius for the great tools,
Noonski for the cooking class [This is how newbies gain the knowledge to cook] and for the inspiration,
Ababrekar for guideness in porting OS from another device,
Aman for sharing his knowledge&helping me make any fixes&upgrades
and many more members/developers of this forum which I consider as a free on line school whose tools and guides made this possible!
These kitchens are free to use or edit but at your own risk, I take no responsibility for any damage caused to your phone!​
B2 Kitchen
B2 Kitchen GUI (LATEST VERSION 2.0.0.0)
Supported Devices:
Elfin
Leo
Diamond
? (Testers Needed for other devices)
INSTALLATION:
Prerequisites:
Microsoft .NET Framework 3.5 (Windows Vista / Windows 7 have it pre-installed)
If you're using Windows Vista / Windows 7, make sure USER ACCESS CONTROL is turned OFF!
DO NOT change the structure of the kitchen!
If you don't want to use ImDisk Driver, you should get another 3rd party software able to create a RamDisk in order to use the relevant feature.
Installation:
Once you download the kitchen, install it following on screen instructions.
When you launch the kitchen for first time you'll get the chance to install ImDisk Driver if it isn't already installed.
(RECOMMENDED if you don't have another 3rd party software for Virtual Drive Management)
To get started, you should import a device by using an official_shipped_ruu.exe as a source.
Otherwise you could place your files manually.
(Be careful to put them in the correct way, respecting the kitchen's structure)
Download links:
Mediafire(For ALL users)
XDA(For XDA members)
********************************************************************************************************************
DESCRIPTION:(Video)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Dump any source you want in almost any known format:
RUU_Device_HTC_Version_Signed_Ship.exe
RUU_Signed.nbh
Flash.dio
OS.nbf
OS.nb.payload
OS.nb
nk.fat
Imgfs.bin
xip.bin
Part01.raw and Part02.raw
Import a new device by dumping the device's OFFICIAL Rom RUU_Device_HTC_Version_Signed_Ship.exe.
The kitchen will even create a CustomRUU.exe AND a Task29.exe for the imported device.
Import any new leaked build just with one click.
When you dump a rom / import a new device the kitchen is able to:
Remove any empty packages if you select -EmptyPkgs.
Sort each registry file from your dump to make it more readable if you select SortRegistry.
Sort all Packages into the required style.
Sort all manila localization files by lcid.
Build your rom according to your taste:
Set which packages will be included from the "Packages Selection" area.
Set Rom version, language, ModelID and CountryID that are required for generating the final flashable *.nbh. The Rom date will always be automatically set to current date.
Select among various builds and lcids which one to use for building your Rom.
Select whether to use a real 6.5 nk (if your device has a 6.5 nk) or not in your generated Rom by selecting 6.5nk.
Select whether to use ShaDrac's driver - Extendir - or not by selecting Extendir, without messing up (adding/removing Extendir.dll - editing boot.rgu) your XIP each time.
Select whether to reduce/remove ULDR or not at your generated Rom by selecting -uldr.
Select whether to increase the Storage Memory of your Rom or not by selecting -imgstart.
Choose your Rom's PagePool Size (0-20).
Select compression (XPR-LZX-None) method for building your Rom.
Add Radio and Splashscreen to your final flashable *.nbh.
Set the kitchen to take care the "SLOT 0 overfloating" issue when building a 6.5 Rom while your nk.exe is not a real 6.5 nk.exe by selecting Rec.Mod SYS
If you have used the above option and have recmodded some modules inside SYS/Shared in order to fix the "SLOT 0 overfloating" issue when no real 6.5 nk.exe is available, but now you want to use the same Build (= the same SYS/Shared) for building a new Rom for a device that has a real 6.5 nk.exe you can reversmode the same files by selecting Rev.Mod SYS.
Set the kitchen to search and find any duplicate items in your compilation that would cause crashing issues to PRB before starting the real building process by selecting DuplicateCheck.
Each time you build a rom a log file is created which you can easily see by clicking the "Process" Label.
Search for files or file's content (i.e. Search for a certain registry entry among *.reg files) using the search engine of the kitchen.
Access fast and easy certain files that are commonly used inside a Rom.
You can see lists of *.txt, *.mscr , *.xml , *.provxml , *.cpr & *_manila inside your kitchen by simply clicking the relevant button.
If you click on any file you see in those lists you open it for editing.
Flash any ROM you selected from a list of your created Roms to your device.
You'll get the chance to perform task29 on your PDA - THEN manualy enter Bootloader and FINALLY update the ROM if you have that special CustomRUU inside the kitchen.
Use a RamDisk (ImDisk Driver comes with this kitchen) for the building and dumping processes in order to gain speed and decrease hard disk fragmentation.
Cfc manila files and convert any normal Manila_package to a compressed one just with one click.
Exploit the possibilities of MortScript even during building your Rom:
Forget about app.dat - app.mscr is introduced in this kitchen.
Don't cook in hundreds of files that get copied to various locations but at the same time stay in your "Windows" directory slowing down your device - Create just one archive (app.xdaz) which extracts the files to the correct locations during boot leaving in "Windows" directory only one file with an unknown extension.
Convert cabs--->EXT Packages just with one drag n' drop on a button.
Convert files<-->modules just with one drag n' drop on a button.
Convert rgu files<-->hives just with one drag n' drop on a button.
Convert provxml files<-->reg files just with one drag n' drop on a button.
Convert bmp<-->nb just with one drag n' drop on a button.
Install any cab file to your pda just with one drag n' drop on a button.
Manipulate each package from the "Packages Selection" area just with one click:
Double click on the package to open its folder
Right click on the package to:
Edit directly the package's app.reg.
Edit directly the package's app.dat.
Edit directly the package's app.mscr.
UPX one/all package's executable(s).
Optimize package's png(s).
Optimize package's bmp(s).
Repack package's *.mui files.
Recmod one/all package's module(s).
NosplitMod one/all package's module(s).
Revmod one/all package's file(s).
Install the package to your pda.
Edit directly the initflashfiles.dat of the selected language just by right clicking inside the "Locale" box in the "Configuration" area.
Edit directly the boot.rgu of the selected build just by right clicking inside the "Build" box in the "Configuration" area.
If you want to edit directly the boot.rgu for the Extendir driver just right click the Extendir checkbox.
Read/Write directly the packages.cif and packages.sof of the selected build just by right clicking inside the "Build" box in the "Configuration" area.
Optimize XIP & SYS of the selected build just by right clicking inside the "build" box.
Build 3 different editions of your rom just by selecting an "Edition" (Premium, Basic, Lite) in the "Configuration" area.
This is optional, so if you leave "Edition" blank, then the "P" , "B" , "L" selection in the "Packages Selection" area doesn't matter!
Keep the kitchen accessible at all time. When you close the kitchen, it minimizes to tray from where you can access many functions and browse the kitchen's folders. By double clicking the tray icon you restore the kitchen's window.
If you want to really exit the kitchen while it is visible press F1!
Easily uninstall the kitchen from your system.
Easily save/load your project:
If you double click the "Save" icon then you'll save your current project (its name will be the Edition.build.locale.date&time of saving).
If you click the "Save" icon then you can select from a list of your projects which one to load.
Easily access all the tools that come with the kitchen. Even assign your own favorites to ALL the bottom buttons.
Check existing registry files for errors before building your Rom by right clicking the "Packages Selection" Label.
The time of this operation depends from the number of registry files, so you either give it enough time to finish if you have a lot of packages in your compilation or you click the Stop button to abort it.
Control your pda from inside the kitchen:
Restart your connected pda without even touching it.
Enter BootLoader.
Watch a list of processes currently running on your device.
View/edit/dump your device's registry.
********************************************************************************************************************
BASIC USAGE:
***Valid for any device - Just consider your device's name instead of the Elfin***
Packages Selection:
You can see all the SYS Packages from the BUILD & LOCALE you've chosen.
You can see all the EXT Packages you have in the kitchen's directories.
You can make sub-directories(limitation:up to 16!) to organize them better(i.e. EXT\Elfin\Tweaks , EXT\Elfin\TodayItems , EXT\Elfin\Apps , EXT\Elfin\Utilities , etc) and place your packages inside each sub-directory.
You can select which packages to include in your ROM by ticking the checkbox in front of the package's name. If you have it unticked then the package will be skipped.
If you double click inside the selection cell but not on the checkbox then you can select/deselect ALL packages.
You can see in the "Packages Selection" area that there are 3 columns "P" , "B" , "L" following the Package's name.
These will have an effect ONLY IF you select an Edition under "Configuration" area!
Code:
If you want "Package1" to be [COLOR="YellowGreen"]included[/COLOR]/[COLOR="Red"]excluded[/COLOR] in your [B]P[/B]remium edition then you must have the checkbox under "[B]P[/B]" [COLOR="YellowGreen"]ticked[/COLOR]/[COLOR="Red"]unticked[/COLOR].
If you want "Package1" to be [COLOR="YellowGreen"]included[/COLOR]/[COLOR="Red"]excluded[/COLOR] in your [B]B[/B]asic edition then you must have the checkbox under "[B]B[/B]" [COLOR="YellowGreen"]ticked[/COLOR]/[COLOR="Red"]unticked[/COLOR].
If you want "Package1" to be [COLOR="YellowGreen"]included[/COLOR]/[COLOR="Red"]excluded[/COLOR] in your [B]L[/B]ite edition then you must have the checkbox under "[B]L[/B]" [COLOR="YellowGreen"]ticked[/COLOR]/[COLOR="Red"]unticked[/COLOR].
There is also a ZIP Column. That Column is used to "mark" which EXT Packages you wish to convert to "Mscr_Packages" when you click "ExtToMscr" option.
Code:
If checkbox = unticked then nothing will change.
If checkbox = ticked then Selected Package will be converted to a Mscr Package (this is useful ONLY for applications that get installed to Program Files)
If checkbox = greyed then Selected Package will be converted to an Extendir Package (this is useful ONLY for applications that get installed to Windows and you're cooking Extendir in your Rom)
When you click the "ExtToMscr" the kitchen creates an archive (with the extension *.xdaz) from the Package's files and writes the necessary "app.mscr" (something like the equivalent of "app.dat").
For this it needs the "app.dat" inside the EXT Package so that it translates it to "app.mscr".
(This operation doesn't take place each time you hit the build button)
Your (original) EXT Packages will be copied to TOOLS\pkg\EXT.bak as a backup and only the (converted) Mscr Packages will be kept inside EXT[folder].
These new packages will be used ONLY IF you select "mscr" for ARType( = AutoRun Type) in the "Configuration" area.
Of course MortScript MUST be included in your Rom AND you must have the ARMS.mscr (script with #INSERTLINE switch) inside Autorun.mscr\Elfin folder.
Click to expand...
Click to collapse
Main Functions:
Obligatory routine:
Select device.
Select build.
Select locale.
Clicking the "Dump" button presupposes that you have placed a Rom file inside BaseROM folder.
When the process finishes you'll get a full dump of that Rom.
Drag n' drop a Rom file on this button works the same way!
Right Click on "Dump" button will show you two options:
Import New Device
meaning use another device's official rom to dump&prepare everything that is required by the kitchen to operate.
When everything is completed you'll be asked whether to auto move files or not!
Import New Build
meaning use any archive with the new leaked build to import the included SYS and XIP packages to the kitchen.
Next to the "Dump" button is 1 icon :
The folder-icon is a menu that includes shortcuts to various kitchen's folders.
Clicking the "Build" button starts the building process.
Next to the "Build" button are 3 icons :
The first one is a menu that includes :
ImDiskGui
ExtToMscr
RomTools
RePackOEM
CFCManila
The second one opens the below window. From there you can turn on/off the RamDisk feature, uninstall the kitchen, set your custom (build) commands, etc.!
The third one opens the Search utility of the kitchen.
Clicking the "Stop" button you stop the process you've started.
Clicking the "Phone-icon" button you have the options to:
Select from a list with your created Roms which rom to flash.
Restart your connected pda without even touching it.
Enter BootLoader.
Watch a list of processes currently running on your device.
Launch CeRegEdit
Double clicking the "Phone-icon" button you access the RELEASE\Elfin folder.
Clicking the "Flash" button you minimize the kitchen and start the CustomRUU (ElfinCustomRUU) in order to flash the ROM you selected to your device.
Right Click on "Flash" button will show you the option to Format&Flash, meaning that you'll get the chance to FIRST perform task29 on your PDA (ElfinTask29) - THEN manualy enter Bootloader and FINALLY update the ROM.
Right Click on "Configuration" label will show you the Advanced PRB Settings panel.
Clicking on "Radio" label opens the radio sub-folder.
Clicking on "Splash" label opens the splash sub-folder.
Addons:
You can easily access all the extra tools that come with the kitchen. - Drag n' Drop works for every dark-GRAY button.
You can assign your favorite links to ALL the buttons you see at the bottom!
Those links can be applications, folders, batch files or urls.
In order to set your own you should edit the file myaddons.ini under TOOLS\addons\ keeping the format addon#|Name|Path :
(Just right click on the button you want to change)
Code:
addon1|CFF Explorer|C:\Program Files (x86)\Explorer Suite\CFF Explorer.exe
addon2|Tiny Hexer|C:\Program Files (x86)\mirkes.de\Tiny Hexer\mpth.exe
addon3|Icon Editor|C:\Program Files (x86)\Icon Editor\IcoFX.exe
addon4|Manila Kitchen|C:\Program Files (x86)\Manila_Kitchen
.
.
.
********************************************************************************************************************
TO DO:
Any suggestions are welcomed!
Any bug reports are appreciated!
B2 Kitchen's Structure
This is the structure of the kitchen after importing a device and you shouldn't try to change it because you will have errors!
The build 23545 you'll see in the below pictures is an example in order to help you understand the kitchen's structure.​
Autorun.mscr is the folder where you can put your mortscript file that runs at first boot(named ARMS.mscr).
This mscr must include a line "#INSERTPOINT" !!! This line is required so that all "app.mscr" will be added at that exact point of your script!
The ARMS.mscr must be placed inside the subfolder named after your device.
BaseRom is the folder where you can put any rom you want to dump.
EXT is the folder where you store all your EXT Packages that you want to try in your ROM.
Here you can put any application,utility,todayitem,etc. and choose whether to include it or not, having in mind if it is or not essential for the windows to work!
Those Packages must be placed inside the subfolder named after your device.
OEM is the folder where you have OEMApps, OEMDrivers and other OEMFolders (Device Specific). Check out trueg's posts for more information about these folders.
Those OEMFolders must be placed inside the subfolder named after your device.
If you are cooking a rom in a different language than WWE, then create that subfolder.
For example if I want to cook a greek rom I'll create a subfolder 0408 along with 0409 and place my local.files in 0408.
If you are using the kitchen in OEM mode you can put inside the "Pkgs" subfolder your old-style packages (with *.dsm , *.rgu , etc.). You'll be able to choose whether to include or not each of those from the kitchen's packages selection!
RELEASE is the folder where your custom ROM (i.e.Yourdevice_ROM_Lang_0409_Build_21056.nbh) will be placed after cooking in order to flash it to your device using your CustomRUU.
You must have a subfolder named after your device under RELEASE and be careful with the names of the included *.exes (YourdeviceCustomRUU.exe & Task29\YourdeviceTask29.exe).
ROM is the folder where the XIP is placed.
If you enter this folder you'll see :
Like it is shown above, you must have all the XIP elements, except MSXIPKernel, inside the subfolder named after your device.
If your device has WinCENLS_Lang_0*** as part of XIP leave it there, otherwise an adviced location to store it is OEM\Yourdevice\0***\.
SYS is the folder where all the OS Packages (Not device Specific , but I'd say Screen Resolution Specific) are stored categorized by build number. Check out trueg's and Da_G's posts for more information about these Packages.
You must place those OS Packages inside the subfolders SHARED, dpi_96 , dpi_96_resh_240_resv_320 , etc. like it is shown below.
TOOLS is obviously the kitchen's "engine".
(Each time you build a rom you should find in there a log file from the building process which you can access by clicking on the Process label of the main application)
Inside CORE\Saved folder you must have a subfolder named after your device.
Inside CORE\Devices.list(file) you must have the settings for your device.
$DEV=YourDevice'sName
<1 for device that has only wm6.1kernel , 2 for device that has wm6.1kernel AND wm6.5kernel , 3 for device that has only wm6.5kernel>
KERNEL=3
dpi=192
resh=480
resv=800
ModelID=PB8110000
CID=11111111
chunksize=64
GSMHeaderType=0x301
<" -s" Switch if device's Splash.nb requires smartphone signature , leave blank if device's Splash.nb DOESN'T require smartphone signature>
SplashSwitch=
SplashHeaderType=0x600
<Size of device's Splash.nb>
SplashSize=786432
<" -t 0" for 0x00 or " -t 255" for 0xFF>
SplashPaddingType= -t 255
OSHeaderType=0x400
<hermes for Sectorsize=0x208 , kaiser for Sectorsize=0x808 , titan for Sectorsize=0x800 , leave blank for Sectorsize=0x200>
NBMerge=kaiser
<reduce for device that ULDR can ONLY be reduced , remove for device that ULDR can be totaly removed>
ULDR=reduce
Click to expand...
Click to collapse
Inside Radios folder (see below) you can store any %radio%_0x30$.nb in order to use in your Rom:
You must place those Radios inside the subfolder named after your device.
You can find all Elf(in) Radios here.
Inside splash folder (see below) you can store any
%##splash%_0x60$.nb in order to use in your Rom.
%##splash%_0x60$.bmp is required for previewing!
You must place those Splashscreens inside the subfolder named after your device.
You can find more SplashScreens here or you could make your own with the kitchen tools.
B2_Kitchen_GUI is the GUI that combines all the command line tools. Screenshots here.
Elfin Hybrid Kitchen
ELF(in) Hybrid Kitchen (DISCONTINUED - NEWER KITCHEN @ 2nd POST)
INSTALLATION:
1. Install on your pc Microsoft Visual C++ 2008 Redistributable Package and Microsoft .NET Framework 3.5!
2. Remove any previous version(if any)of the kitchen(shortcuts too) before "installing" the newer!
3. The archive should be extracted directly to the Drive where Windows are installed (most cases C:\) , otherwise nothing will work!
4. Once you do that, go into C:\ELF(in)_Hybrid_Kitchen and double-click "First_Run_For_ELF(in)_Hybrid_Kitchen.bat"!
5. IF you're using Windows Vista, make sure USER ACCESS CONTROL is turned OFF!
Download through: Mediafire
********************************************************************************************************************
DESCRIPTION:
(Be patient and keep your eyes on the DOS window for additional help&instructions while using this kitchen)
Main Functions:
[a] Dump any ROM from Kaiser, Polaris, Diamond, Xperia, Raphael, Elf(in)...
You may use these formats:
****.nbh (eg: RUU_Signed.nbh, Blue_Elves.nbh, etc) ,
****OS.nb (eg: New-OS.nb, 19588-OS.nb, etc) or ***windows.nb (eg:Mobile_windows.nb, New_windows.nb, etc) ,
****imgfs.bin (eg: imgfs.bin, new_imgfs.bin, etc) .
****.payload (eg: OS.nb.payload, 20270_OS.nb.payload, etc) . <- NOT FOR ELF(in) !
****.raw(only Part01.raw & Part02.raw) .
You get new OEM, SYS and xip.bin(unless you used *imgfs.bin) into C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\Temp .
If you used an ELF(in) ROM then you'll get a full dump, OEM, SYS and XIP, that you could move to C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19XXX\ and use it as a cooking base .
[b] Port any XIP from Kaiser, Polaris, Diamond, Xperia... You need xip.bin .
It requires:
NOT to change Ref_XIP folder inside C:\ELF(in)_Hybrid_Kitchen\Prepare_XIP and
If you have any problems in XIP Porting you have all the needed tools inside C:\ELF(in)_Hybrid_Kitchen\Prepare_XIP to try manually port the xip .
[c] Build your OS.nb (using the Ervius PkgToolsBuildos which can autofix & autorelocate SYS) .
You'll get the option to make a dumpable ROM using PkgToolsBuildos (by keeping unticked the box next to "All packages in one:") .
NOTE1: Inside ..\Build_ROM the OEM , SYS and ROM\XIP folders are empty . You may "fill" them with the required files .
NOTE2: Because Ervius PkgToolsBuildos is included in the kitchen, you could always use the functions that it provides apart from those described here .
NOTE3: If your xip_out.bin or out.bin is smaller than 2,49MB you could use the attached os.nb.payload (where imgfs start @ 0x280000)
[d] Flash any ROM to your device .
If you have a CID Locked device you have the option to flash a ROM using SoftSPL & your device remains CID Locked with the same SPL !
Additional Functions:
[1] Convert any cab to an OEM Package using Ervius Package Creator .
[2] Create a cab using IABovine's QuickCab 2.0 .
[3] Convert a bitmap to a Splash.nb (& reverse) using pof's nbimg .
[4] Convert files to modules & reverse using RecMod and reversmode . Not all files can be converted to modules.
[5] Convert 24 bit .bmp to .brn and reverse (for editing Cube gfx) .
[6] Compress executable files using UPX 3.03 .
Panel:
Easy access for many tools .
BASIC USAGE:
(Check out ayyu3m's great [PICTORIAL] COOKING YOUR 6.1 ROMS USING ELF(in) HYBRID KITCHEN)
1. Lets say you want to use a SHIPPED or DUMPED (NOT a COOKED!) ELF(IN) ROM as a Base.
--1.1.Double click the desktop-shortcut "Main Menu"
--1.2.Press [a]
--1.3.A window pops up beside the DOS screen. Place in there the RUU_Signed.nbh and close the window!
--1.4.Press [1]
--1.5.When the process is completed (& pressing any key returns you to main menu), you get another window opened with the files you want:
Packages(OEM&SYS)
XIP(folder)
xip.bin
--1.6.Keep that window open and double click the desktop-shortcut "Kitchen"
--1.7.Copy OEM and SYS to C:\ELF(in)_Hybrid_Kitchen\Build_ROM\
--1.8.Copy the XIP(folder) to C:\ELF(in)_Hybrid_Kitchen\Build_ROM\ROM\
2. The Base for cooking your ROM is set! Either clean up the OEM folder from things you wish to be removed or just (re)build the ROM.
--2.1.Double click the desktop-shortcut "Main Menu" (if you closed the main menu window)
--2.2.Press [c]
--2.3.PkgToolsBuildos starts
--2.4.Go to BuildOS Tab and click Load Rom.Select which Packages to include and press the green play button[Go]
--2.5.When this process is completed you'll have your OS.nb inside the "temp" folder and the (final product) RUU_Signed.nbh is generated in two places,
(i)..\CustomRUU\ <= For flashing CID Unlocked phones
&
(ii)..\RUU\ <= For flashing CID Locked phones using SoftSPL
NOTES:
A) Ref_XIP folder inside Prepare_XIP is the latest 3.10ROM's XIP, but modified as follows:
-removed modules:
cachefilt.dll, hd.dll, mencfilt.dll, osaxst0.dll
-removed files:
boot_ms.rgu, bmui.nb0
-edited files:
boot.hv, boot.rgu,
Code:
REMOVED ENTRIES:
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Filters\CacheFilt]
"Dll"="CacheFilt.dll"
"Order"=dword:2
[-HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Filters\CacheFilt]
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Index"=dword:00000001
"Prefix"="DRM"
"Dll"="lsomacore.dll"
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\LsFilter]
"Order"=dword:00000001
"Dll"="LSFILTER.dll"
[HKEY_LOCAL_MACHINE\Init]
"Launch98"="TimeWizard.exe"
-edited modules:
nk.exe
Code:
RTC is enabled
-ALL MSXIPKernel modules are relocated to achieve better XIPPorting
**If you include LockStreamDRM PACKAGE in your ROM and you use the Ref_XIP as your \ROM\XIP(folder), ADD the removed (from boot.rgu) entries
Code:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Index"=dword:00000001
"Prefix"="DRM"
"Dll"="lsomacore.dll"
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\LsFilter]
"Order"=dword:00000001
"Dll"="LSFILTER.dll"
[HKEY_LOCAL_MACHINE\Init]
"Launch98"="TimeWizard.exe"
in the PACKAGE's *.rgu.
B) Building your ROM
When you are building your ROM you need:
ROM\XIP(ALL FILES and MODULES) ,
ROM\romhdr.bin and
ROM\OS.nb.payload
This option builds the out.bin(buildxip.exe is used)from the XIP(folder).
C) PP Patching is included in the kitchen operation!
You just set your favorite pp size at the beginning(installing) and each Rom you build is already patched!
If you make the following hex change in nk.exe's S000
Aman said:
i've another method for u guys to change the PP. search the 03 15 A0 03 02 15 A0 13 00 10 83 E5 62 C2 FF EB in yours S000 of nk.exe and change the string marked in Red color to 00 00 A0 E1. from there onwards u can simply use the old Multi-platform PP changer.exe (that is also found in kaiser kitchen) to change ur PP on the OS.nb. this should make the kitchen even simpler
PS: this method works regardless of the device
Click to expand...
Click to collapse
then the kitchen's PP Patching doesn't work!
You should use the suggested by Aman Multi-platform PP changer v2.21 which is included in the kitchen's panel!
NOTE: I don't have an ELF to test, but after the above change then I think that the pp size is the same for both ELF&ELFIN(not dynamic).
Nice job Kokotas.
great job bro
i would like to test ur kitchen.
Repository:
ElfinCustomRUU.exe
ElfinTask29.exe
Task29&CustomRUU
B2_Kitchen_GUI_Setup
B2_Kitchen_GUI.exe
kokotas said:
Thanks man, but it will be great only if it works for everybody!
I'll pm you the password for the download link.
Regards!
Click to expand...
Click to collapse
TOGETHER we all can MAKE SURE that it works for everybody
how can I obtain pass? I will translate ebglish rom to Turkish and I need that tool..
Nice work.
Not going to switch right away at the moment.
But this looks very good.
I'm on the lookout for a cheep Touch so this will come in handy if I get my hands on a touch....
gullum said:
I'm on the lookout for a cheep Touch so this will come in handy if I get my hands on a touch....
Click to expand...
Click to collapse
gullum I have touch and I can't wait to cook a new room for touch
ill have a go i got a rom on my phone that that is needed in the upgrade rom list but i have been able to remove it
Project for work
i need to lock down some features of my works PDAs and would love to try your kitchen to attempt this.
can i have a password?
Got a Touch tonight for under 200$ used of cause so now I want a kitchen to make roms
kokotas said:
Sit taken
Click to expand...
Click to collapse
Well deserved!
Gr8 job, Ill keep an eye.
This is fantastic and I'd like to try it. I'd like to cook my rom using this kitchen. Would you pls. give me a password.
Removed password protection!The download link is open for everyone!
Read 1st post before starting to play with it!Get used to it and read carefully!
Some features are NOT tested yet!
Hope to hear some good news!
Even better...hope to hear that someone makes it better!
I'm done!Back to my readings and to Solid State Physics(I hate that lesson)
Best Regards!
This is on it's way to my pc now thanks in advance
I've already changed Bepe's kitchen to fit my cooking but this one seams more advanced so thanks again
kokotas said:
Removed password protection!The download link is open for everyone!
Read 1st post before starting to play with it!Get used to it and read carefully!
Some features are NOT tested yet!
Hope to hear some good news!
Even better...hope to hear that someone makes it better!
I'm done!Back to my readings and to Solid State Physics(I hate that lesson)
Best Regards!
Click to expand...
Click to collapse
u need to modify the Create_ROM_for_ELF.bat file used for Ervius' buildOS tool. its not working right now, pls check it

Tutorial: How to Dump, Extract and Build a Rom for Windows Mobile

CREDIT GOES TO anichillus for his Tutorial and kitchen. I just modified the tutorial with some pics and steps. Thanks to its right, S.V.I, CRACING and kitchen tools developers. Hope it helps…
Note: I wrote this tutorial on my Blog too. So consider this post as a copy of that post. Plz let me know if i have mistake in the tutorial. Thanks....
1. Some ROMS are password protected. So those ROMS will not dump.
At First you need to download a good Kitchen and a good ROM for windows mobile. All the kitchens are good. For me HyperCore Kitchen is the best choice so download the kitchen from here :
Kitchen source: HyperCore Kitchen
Latest Kitchen Download: Download
You can Use this kitchen for Wizard, Hermes, Artemis, Herald, Universal, Trinity and Prophet. Then Download a Rom for your device. You can find a lots of coustomized ROM for windowsmoble devices on Xda Developers. Before Downloading a windows Mobile Rom you need to know what kind of Windows Mobile Device you Have . And You need a CID Unlocked Device. I know that my MDA is a Wizard and it’s a G3 Device. To know about your device please read Smartphone / PDA Nick Names And Unlocking. I added some Unlocking tools source for different Device. After downloading and Unlocking Your Device You can update your Rom. To coustomize your downloaded ROM follow this steps:
1. Extract The kitchen to your C: Drive otherwise it will not work properly. It should be C:\Core\ on you PC. First of all you need to edit the file named “Device.txt” located on the “C:\Core\ACK\” folder located on systemdrive. You will see set device= . If you have a Wizard then edit the test like this set device=Wizard. Then Go to your downloaded rom directory ans copy the nk.nbf or the .nbf file to Desktop\HyperCore\Panel\Extract\source Folder. Make sure that .nbf file is named as nk.nbf.
Take a look at the bottom picture :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. The Navigate to Desktop\HyperCore\Panel\Extract folder and Start DumpRom and hit Enter to Dump / Extract the ROM from nk.nbf file. You will see its working.. After few seconds..minutes, depending on your PC and the ROM you are extracting you will be prompted with a Status and with some questions. Here you can start PKG Tool and you can move the OS.nb to ROM folder. Type In 2 and hit Enter to copy Os.nb. Now Type in 1 and hit [ENTER] to start Package Tool. Read the window and Hit [ENTER] to countinue…
Bulding Packages
3. You will see some options On the status window. Choose Number 3 manual Option. So type in 3 and hit [ENTER].. Package tool will start. Click on Package tool and go to file > Open then select the folder Desktop\HyperCore\Extract\dump. It will show you Rom Information. After that click on Tools > Build Packages on the package Tool program. It will take some time to bulid the package. It will show you some status afet building packages.Look for [Missing Files] to find info about their Directory. To copy the missing file go to Desktop\HyperCore\Extract\dump directory and Copy the missing files / folders from there to where it shows. After you placed all files where they should be, you must then rename the “dump” folder into “Packages” and only then you can exit the PackageTool. . When you will do that, the batch program will get you to another Status window. Here you can see “Move SYS and OEM to Kitchen. So, select “4” and press [ENTER] but be sure that you renamed the “Dump” folder first into “Packages”. Then type Y and press [ENTER] again. It will move the SYS and OEM folders into HyperCore \Build for later building. Then Exit or Press [ENTER] to Exit the status window.
Dumping XIP from ROM
4. The Only thing you miss now is the XIP section and you’ll have your first OEM and SYS Kitchen after dumping the XIP from the ROM. Go to Desktop \HyperCore\Panel\Extract and start DUMP XIP it will open a folder asking you to place OS.nb on that folder. We already moved the OS.nb to this folder. So Close that folder and hit [ENTER]. This will work to generate the XIP. Read the status window and continue. Type in 1 and press [ENTER] to move the XIP. Press any key to continue and Exit the Status window.
BuilDing ROM from Kitchen
5. If you are on this step, you made your own first kitchen for your windows mobile device. Before building any windows mobile rom you must remember that your ROM size should be 56.9 MB. Now go to Desktop \HyperCore\Build and add / delete your OEM Pcakages from OEM Folder. If you want to know about how to make OEM package for Windows Mobile please read details about Making Windows Mobile OEM Here. Add remove packages from OEM and SYS folder to adjust the nk.nbf size. After adding an deleting packages go to Desktop\HyperCore\Panel\Build and start BuildOS. Look at the picture below to see this status window.
6. This will prompt you with couple of choices. It’s pretty easy. Select “1” and this will start the actual BuildOS program. Select the Packages from there and click on little green arrow and wait until finish. Note that, If you have duplicate file on the packages you will get error message saying file exist.. delete duplicate files from SYS and OEM then click on green button again. When done close the build os on the status window to make OS.nb file by choosing option 2. Type in 2 and press [ENTER] to create OS.nb file.
7. After finishing you will see the status window again. Now type in 3 and it will start nb2nbf tool. Now follow this instruction carefully.
Select Wizard on model ID field.
Then select File#1 and browse Os.nb file from Desktop \ HyperCore \Tools\Convert\ .
Then select OS from drop down list.
Click on Start Address field to get the Start address.
Click on Translate to buld nk.nbf file. Here is a picture of nb2nbf tool with this steps .
how to remove programs from sys folder
i want to remove some applications from the sys folder (like bluetooth ftp,ps shutxp) which i never use.can i simply delete the folder from sys or i have to edit rgu or initflash or dsm file .or anyone knows how to edit xml file so that i can select or deslect program from the buildos tool.thanks in advance
confident said:
i want to remove some applications from the sys folder (like bluetooth ftp,ps shutxp) which i never use.can i simply delete the folder from sys or i have to edit rgu or initflash or dsm file .or anyone knows how to edit xml file so that i can select or deslect program from the buildos tool.thanks in advance
Click to expand...
Click to collapse
Deleting the folders worked fine for me.
Which dose the samsung onima go under?
Wizard, Hermes, Artemis, Herald, Universal, Trinity or Prophet?
thanks
Hello,
MoonBlazer said:
Wizard, Hermes, Artemis, Herald, Universal, Trinity or Prophet?
thanks
Click to expand...
Click to collapse
No, hypercore or any kitchen found in this website will not work for samsung onima and also the device is not developed by HTC so you might not get any info in this website for cooking ROM's for samsung onima.
SO DO NOT TAKE ANY RISK.
confident said:
i want to remove some applications from the sys folder (like bluetooth ftp,ps shutxp) which i never use.can i simply delete the folder from sys or i have to edit rgu or initflash or dsm file .or anyone knows how to edit xml file so that i can select or deslect program from the buildos tool.thanks in advance
Click to expand...
Click to collapse
* If you are deleting any OEM folders which contains lnk. Simply delete the OEM and also clear the command line in the initflashfiles.dat file which relates to the lnk file inside the deleted OEM. You can ignore this one but I think it will slow down the speed of booting at the first time.
* If you are deleting any OEM folder which does not contain any lnk file then simply delete it.
* When ever you deleted the OEM, Rgu file might be the important to boot the device so confirm the keys inside the rgu and then delete the OEM.
* After build the nk.nbf, The file should be less then 56.9 MB if not its overcooked and it will defiantly crash while flashing.
* Make sure you device is flashed to hardspl before testing your cooked ROM.
I think these tips will help a little, Thanks
Best regards
thanks
CRACING said:
Hello,
No, hypercore or any kitchen found in this website will not work for samsung onima and also the device is not developed by HTC so I might not get any info in this website for cooking ROM's for samsung onima.
SO DO NOT TAKE ANY RISK.
* If you are deleting any OEM folders which contains lnk. Simply delete the OEM and also clear the command line in the initflashfiles.dat file which relates to the lnk file inside the deleted OEM. You can ignore this one but I think it will slow down the speed of booting at the first time.
* If you are deleting any OEM folder which does not contain any lnk file then simply delete it.
* When ever you deleted the OEM, Rgu file might be the important to boot the device so confirm the keys inside the rgu and then delete the OEM.
* After build the nk.nbf, The file should be less then 56.9 MB if not its overcooked and it will defiantly crash while flashing.
* Make sure you device is flashed to hardspl before testing your cooked ROM.
I think these tips will help a little, Thanks
Best regards
Click to expand...
Click to collapse
ok, thanks
Thanks Cracing.Your Touch HD is the best rom i ever used.
* Make sure you device is flashed to hardspl before testing your cooked ROM.
Click to expand...
Click to collapse
I think Hspl is only needed if you have a G4 Device!
ather90 said:
I think Hspl is only needed if you have a G4 Device!
Click to expand...
Click to collapse
O" thats right man. I was not knowing about it.
Why did the htc developerd two edition of htc wizard, I mean G3 and G4.
Regards
nada1
CRACING
ı am not spaek english soryy ı am eng. speak very little
Rom edit Video description pls
Correct English :
Can any one please make a screencast/video of the steps explained above ?
5. If you are on this step, you made your own first kitchen for your windows mobile device. Before building any windows mobile rom you must remember that your ROM size should be 57 MB. Now go to Desktop \HyperCore\Build and add / delete your OEM Pcakages from OEM Folder. If you want to know about how to make OEM package for Windows Mobile please read details about Making Windows Mobile OEM Here. Add remove packages from OEM and SYS folder to adjust the nk.nbf size. After adding an deleting packages go to Desktop\HyperCore\Panel\Build and start BuildOS. Look at the picture below to see this status window.
Can any one please make a screencast/video of the steps explained above ?
ferfecir said:
5. If you are on this step, you made your own first kitchen for your windows mobile device. Before building any windows mobile rom you must remember that your ROM size should be 57 MB. Now go to Desktop \HyperCore\Build and add / delete your OEM Pcakages from OEM Folder. If you want to know about how to make OEM package for Windows Mobile please read details about Making Windows Mobile OEM Here. Add remove packages from OEM and SYS folder to adjust the nk.nbf size. After adding an deleting packages go to Desktop\HyperCore\Panel\Build and start BuildOS. Look at the picture below to see this status window.
Can any one please make a screencast/video of the steps explained above ?
Click to expand...
Click to collapse
in this step go to Desktop \HyperCore\Build and add / delete your OEM Pcakages from OEM Folder in that directory. Create or download your OEM packages from here. Then follow the tutorial
Tried this a couple times from the beginning and I can't get past the BuildOS. Seen people have this before with other ROM's but they never post how it was fixed. It's the old "External component has thrown and exception." when it's creating initflashfiles.dat....
Any help with past experience would be much appreciated.
DurKNesS said:
Tried this a couple times from the beginning and I can't get past the BuildOS. Seen people have this before with other ROM's but they never post how it was fixed. It's the old "External component has thrown and exception." when it's creating initflashfiles.dat....
Any help with past experience would be much appreciated.
Click to expand...
Click to collapse
Please explain more. I will try my best to fix your problem.
Thanks CRACING,
I think it has everything to do with I don't know what i'm doing...lol
I have a lot of respect for all of the peeps cooking roms for us. Don't even know where to start when I'm looking at the sys folder. Thanks for offering to help but I'm staying far away from trying to cook a rom to my liking.
DurKNesS said:
Thanks CRACING,
I think it has everything to do with I don't know what i'm doing...lol
I have a lot of respect for all of the peeps cooking roms for us. Don't even know where to start when I'm looking at the sys folder. Thanks for offering to help but I'm staying far away from trying to cook a rom to my liking.
Click to expand...
Click to collapse
Only few weeks ago I was also not in knowing how to cook. I readed may posts and threads on this website but did not went in head. So after many studies and hard works day/night, Now I am able to cooking the ROM's for the wizard. Everyone think that cooking is not so easy but after learning, we can cook ROM's easily.
Now I am insearch in cooking ROM's for HTC Touch HD but the only problem for me is that, I have do not have device to test.
Anyway, Do some research in this good website. You will get many guides for cooking ROM's and threads/post for fixing problems.
Best regards
the path
Desktop\HyperCore\Panel\Extract\source
is on new version not correctly the path are
\Desktop\HyperCore\Extract\Source
gabberjool said:
the path
Desktop\HyperCore\Panel\Extract\source
is on new version not correctly the path are
\Desktop\HyperCore\Extract\Source
Click to expand...
Click to collapse
But mine shows.. Desktop\HyperCore\Panel\Extract\source i am confused
delete your OEM Pcakages
Can any one please make a screencast/video of the steps explained above !
Touch 3G - Jade
Hi,
Can I use this tutorial to create a Rom for my Jade ,or Touch 3 G.Please note that I am not a computer geek.
Regards,
Thomas

[ CRBuilder™ 2 ] [ FOR A COMPLETE AND SMARTER COOK ]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Version 2​
Hello Brothers and Sisters,
I'm pleasure to provide you my first kitchen for HTC Wizard, based on Bepe's Platform Rebuilder and other tools. This kitchen is so powerfull and professional, that gives you all the needs to build a prefect ROM's. ROM Builder, XIP Dumper, Splash S Builder, File Editor Suite, and more. Also supports for building multiple languages and editions of a ROM with a single kitchen ( Version 1 Only ). As usual the description is below, Please read it before downloading and using.
Features :
Easy XIP porting.
Super faster ROM building.
EXT packages (Extended packages)
Change Page Pool Size while cooking.
Support for building multiple languages and editions of a ROM with a single Kitchen
.ROM and .VM are not needed in SYS anymore, PRB will create it's own .ROM now
No need to reloc the modules using G'Reloc or WMReloc.
Easy to build 1st and/or 2nd splash screens using Splash S Builder.
And lot more.
Versions :
CRBuilder 2
Platform Rebuilder v2.1
XIP Dumper v2.0
Splash S Builder v2.0
DSM Patcher v1.6
DSMAnalyzer v1.4
Package Creator v2.7
RGU to XML v1.0
SYSVersion 1.2
NB2NBF v2.02
PagePool Changer v2.21
Log Report : Version 2
Deeply modified to look smarter and user friendly.
Replace bat files to exe's.
Placed error msgs
Added page pool changing feature while building ROM.
Modified Splash S Builder.
Modified XIP Dumper.
Installation Notes : CRBuilder
Run CRBuilder 2.exe
Enter the password and install/extract.
The kitchen is ready to use.
Installation Notes : XIP Builder
Drag and drop xip.bin or os.nb.payload or cooked ROM ( OS.nb ) or file which contains XIP, into DUMP XIP.exe.
Wait for processing.
You will get XIP dir and romhdr.bin in root
Go inside XIP; Drag and drop all the dsm files ( One-By-One ) into Package Builder.exe ( Xtra Tools ) using another window.
Now inside the XIP dir you will get : MSXIPKernel, MSXIPKernelLTK and OEMXIPKERNEL.
If your are porting XIP from other device, then you should remove OEMXIPKERNEL and place your devices OEMXIPKERNEL.
Move XIP dir and romhdr.bin to root of the ROM dir of your kitchen.
XIP porting is done.
Paths and Patterns : Single or Multi Language/Edition
OEM - Place all your packages including OEM_Lang_0409, OEMAPPS, OEMDrivers, OEMMISC, OEMOPERATORS.
SYS - I think you all might know this.
ROM - Use your base ROM. i.e OS.NB but rename the file to OS.NB.payload; romhdr.bin.
ROM\XIP - MSXIPKernel, MSXIPKernelLTK, and OEMXIPKERNEL.
EXT - Use this, if you have EXT packages. Use OEM to EXT.exe if you want to convert OEM to EXT packages. Exampe : EXT\LEO\AdobePDF 2_5_1_0_395886_06H
Installation Notes : Single Language/Edition
Build your kitchen, as said in Paths and Patterns above.​
Installation Notes : Multi Language/Edition
Build your kitchen, as said in Paths and Patterns above and also do the following :​
'Skip' and 'Only' Files:
Use 'skip' and/or only files to make multi language or edition ROM's. You can place these 'skip' and/or 'only' files inside SYS and/or OEM packages.
In Config.txt, you will find this line :
set LOCALE=XXXX
LOCALE should be set to the language you want to build the ROM for. i.e 0409, 0804, 0804 or etc
set BUILD=XXXX
BUILD is some custom value like Premium/Basic/Lite.​
File Name/s :
_skip
This package will be skipped always.
_skip_0409
This package will not be included to the ROM if you set LOCALE to 0409 in Config.txt.
_skip_Premium or _skip_Basic or _skip_Lite
This package will not be included to the ROM if you set BUILD to Premium/Basic/Lite in Config.txt.
_only_0409
This package will only be included to the ROM if you set LOCALE to 0409 in Config.txt.
_only_Premium or _only_Basic or _only_Lite
This package will only be included to the ROM if you set BUILD to Premium/Basic/Lite in Config.txt.​
Example:
OEM\Package 1\_skip_0409
OEM\Package 1\_skip_0407
OEM\Package 2\_skip_Lite
OEM\Package 2\_skip_Premium
OEM\Package 3\_only_Premium
OEM\Package 4\_only_0409​
Package 1: Will only be included if you are building a 0409 rom.
Package 2: Will only be included if you are building a Basic rom.
Package 3: Will only be included to a Premium build.
Package 4: Will only be included if you are building a 0409 rom.​
As you can see there can be more than one skip or only files in one package.
A skip or only file is just a file (like an empty text file) that is renamed to "_skip_xxx" or "_Only_xxx", important is that this file MUST not have an extension, only filename!
Video Guide :
Link
Warning Notes :
CRBuilder is only for building ROM(s) so you need all the source to do so. Like OEM's, XIP, SYS, OS Payload and Device base files/modules/packages. To get those, You need to extract any stock or custom ROM/s ( i.e Using hypercore ) but the ROM should not be protected.
Microsoft Visual C++ 2008 Redistributable is must
Supports all type of Windows platforms.
Download :
Link
Password : 02111989
Thank you for using our developments..........
Source​
Wizard's OS Payload : Link
Wizard's Metadata : Link
( Use this when porting non Wizard's SYS )
Wizard's WinCENLS WWE : Link
( Use this when porting non Wizard's SYS )
Wizard's XIP base kernel : Link
( Use this when porting non Wizard's XIP )
Recommend to use Metadata and WinCENLS WWE which comes with SYS source. These are just for reference.
Kitchen Builder Open Source​
Its not the builder, it contains bat files. The source of exe's.
Click here to download.
Empty Post 1
Empty Post 2
My Special Thanks To :​
- AMD, ASUS and NVidia
- XDA-Developers
- Bepe - DONATE
- Ervius - DONATE
- Laurentius26 - DONATE
- Ameet - DONATE
- Cornelha
- Also thanks to the ROM testers, feedbacks, and donations........
hey was about to test this out but says the password is incorrect
mysticgoku said:
hey was about to test this out but says the password is incorrect
Click to expand...
Click to collapse
Sorry, Pass is 02111989
CRACING said:
Sorry, Pass is 02111989
Click to expand...
Click to collapse
lol thanks will test it out now and give feedback
Very Interesting indeed!
Stickied
great work!
excellent thanks!
how do I use your kitchen from a file nk.nbf
Italiano
ottimo grazie!
come posso utilizzare la tua cucina partendo da un file nk.nbf
ippoglosso said:
excellent thanks!
how do I use your kitchen from a file nk.nbf
Italiano
ottimo grazie!
come posso utilizzare la tua cucina partendo da un file nk.nbf
Click to expand...
Click to collapse
This is only the ROM builder. First you need to extract the ( unprotected )ROM using hypercore, then only you can use this ROM builder.
Thanks and regards
Installation Notes : XIP Builder
* Drag and drop xip.bin or os.nb.payload or file which contains XIP, into DUMP XIP.bat.
* Press any key to start; Wait to dump and again press any key to exit.
* You will get XIP dir and romhdr.bin in root
* Go inside XIP; Drag and drop all the dsm files into Package Builder.exe ( Xtra Tools ) using another window.
* Now inside the XIP dir you will get : MSXIPKernel, MSXIPKernelLTK and OEMXIPKERNEL.
* If your are porting XIP from other device, then you should remove OEMXIPKERNEL and place your devices OEMXIPKERNEL.
* Move XIP dir and romhdr.bin to root of the ROM dir of your kitchen.
* XIP porting is done.
Click to expand...
Click to collapse
gives error in this step
usage : dumpxip (os.nb payload)
Click to expand...
Click to collapse
ather90 said:
gives error in this step
Click to expand...
Click to collapse
Have you drag and droped xip.bin or os.nb?
i have put xip.bin
ather90 said:
i have put xip.bin
Click to expand...
Click to collapse
It must work because I have tried xip.bin and os.nb and works fine.
Can you attach here or pm me that xip.bin?
well i went in to folder :
C:\Documents and Settings\Ather Akber\Desktop\CRBuilder\Xtra Tools\XIP Dumper 1.0
Click to expand...
Click to collapse
there i pasted my xip.bin, there was a folder called bin and a batch file called "DUMP XIP"
but now i tried manually from CMD "dumpxip xip.bin" and it worked
ather90 said:
well i went in to folder :
there i pasted my xip.bin, there was a folder called bin and a batch file called "DUMP XIP"
but now i tried manually from CMD "dumpxip xip.bin" and it worked
Click to expand...
Click to collapse
You should drag and drop the xip.bin on DUMP XIP.bat and it will extract the XIP.
Anyway, glad to know that you have extracted xip.
ok, that done, now when i drag the dsms on Package Builder.exe, should i be looking for some files or just the dsms?
cracing this builder works with wm 6.5? or is only for the others windows?

[29nd Oct] osKitchen Kaiser (fe~ROM kitchen) - easy kitchen with GUI [ver 1.4.test8!]

TEST version 1.4 goes public
1.4.test8http://forum.xda-developers.com/showpost.php?p=4836277&postcount=997 - new style SYS tree + COMPLETE 23081 0409 ALL-DPI ALL-RES package! - DELETE msvcr71.dll IN TOOLS FOLDER!
1.4.test7 - only few bugfixes, somewhere lost around pages 95 - 100?
1.4.test6 - Fixed all not-working devices. UPDATE TO .test5 AND IMPLANTXIP FIRST!
1.4.test5 - OVERWRITE YOUR TOOLS FOLDER! + implantxip from this post, otherwise XIP won't implement and ROM woudln't boot!! SELECT DEVICE ONLY KAISER, ALL OTHER WILL CRASH!!
1.4.test4 - OVERWRITE YOUR TOOLS FOLDER!
1.4.test3
1.4.test2
1.4.test (always crashes, don't use it for cooking!)
osKitchen (aka fe~ROM kitchen)
Hello ladies,
I’m too lazy to do many things manually so I build a new kitchen for us. I must thank to TPC for using his .bat (hardcoded into kitchen) and ervius for idea.
It is much simplier than Erviuse’s kitchen. I use external tools from TPC’s kitchen so if crashes any of these tools, it’s not my fault, I just cooked with it and flashed and it works fine if you don’t create crash fault manually. I’ve been writing this first release few hours and it has about 1000 lines of code lol.
Save & Load works as expected, saves everything (you shouldn't modify saved file by yourself).
If you don't know what something does in "More tweaks" menu, just don't touch it and leave it as was default!
What you need: patience and .NET Framework 3.5.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
Kitchen with 23009 SYS&XIP and TPC's EXT, ver 1.0.3b My Server [CZE] | 4Shared
Kitchen without SYS XIP EXT and OEM, but with all tools My Server [CZE] | 4Shared
Current updates:
I usually do updates WITH Tools and Kitchen folders to ensure you have it complete so update it too!
1.0.3b -> 1.0.8 My Server [CZE] | 4Shared
1.0.8 -> 1.0.9 My Server [CZE] - Only new .exe, make sure you have updated to 1.0.8 first!
!! THERE WILL BE NO MORE UPDATES TO 1.0.x VERSION, I'M NOW FOCUSING ON 1.4 FINAL!!
SYS&XIP updates:
23016 WWE (0409) - SYS&XIP
23028 WWE (0409) - SYS&XIP - not 100% done, but pretty usable
23034 WWE (0409) - SYS&XIP - nice new UI changes (Start moved down etc), FAST, smooth
All SYS&XIP updates unpack into Sources folder
OLD updates: only for history purpose
4Shared | my server [CZE]
Kitchen with 23009 SYS&XIP: 4Shared | my server [CZE]
Updates (rollup, so you just only download latest .exe and overwrite the old one):
1.0.1 4Shared
1.0.2 My Server testing build
1.0.3 4Shared also testing build
1.0.4 4Shared
1.0.5 4Shared | My Server [CZE]
1.0.6 4Shared | My Server [CZE]
1.0.7 My Server [CZE]
WORKS ONLY ON 1.0.x RELEASES ONLY AND 1.4.test TILL 1.4.test8! Watch 1.4.test8 version post for details about NEW tree structure.
Tree structure:
I wanted to have main kitchen root as clean as possible so I moved all things to Source directory.
- In Source directory, there is few folders. The ones starting with _ you don’t have to pay attention on them, or better, don’t touch them at all unless you know what you are doing!
- In folder EXT are four folders: Apps, Fixes, Settings and SYSpkgs. What’s the difference between them? Actually none. In all of them you put EXT packages as you’re used from TPC’s kitchen (app.dat, app.reg and files folder). The only difference is that they show themselves in different tabs in kitchen so you don’t mess different settings with applications etc.
- In folder MSXIPKernel always create numbered folder with XIP version, like 23009 and copy all folders and files from MSXIPKernel you get (busenum.dll etc).
- Into OEM you put your OEM folder with folders like OEM_Drivers
- ROM folder you don’t have to touch on it unless you know what you’re doing – it’s already preset by TPC’s kitchen.
- And into SYS you put, just like in MSXIPKernel folder, numbered folder with build # and inside you place all SYS packages (Base, ConfettiCore, etc)
In the main root are also folders Projects that you can save your projects into, Tools which contains all tools needed to cook so don’t touch it too. Folder „build“ should remove itself after finished cooking. If it doesn’t (like crash etc) you can delete it manually. In FLASH folder (that creates only after cooking) should be only CustomKaisRUU.exe and RUU_Signed.nbh, or you can delete it too – RUU is copied from Source directory and NBH is cooked.
There also might be some other folders, "working" directory is for extracting NBH file (you can delete it if is not kitchen running) or Kitchen folder (new since 1.0.7) - it contains support things to kitchen like tutorials, icons and other material. You shouldn't touch it too.
Examples:
EXT apps directory:
MSXIPKernel:
OEM folder:
SYS folder:
Questions & Answers:
Q: What’s the difference in Device between Kaiser and Tilt?
A: When selected Tilt, keyboard patch is automatically added.
Q: LZX or XPR?
A: LZX saves space, but takes longer to build.
Q: UPX on EXT?
A: Saves space by compressing all EXE files in EXT directory with UPX compression.
Q: SuperRAM?
A: Only switches between nk.exe’s with 79M/85M/101M (and automatically adds MEMFIX).
TIP: You don’t have to manually change always in OEM\OEMVERSION that one .provxml, if you fill it in kitchen it gets created automatically.
Tutorials & Tips
Moved to kitchen Tutorials!
User tips and tutorials:
witschey - Adding HTC StartUp animation with system backup
witschey - Fixing HTC Startup sound
OndraSter - Porting new SYS and XIP to kitchen (valid for version till 1.4.test6)
Changelog
Kitchen 1.4.test2
- Added X button to selecting splash and welcomehead to clean it
- Added option to cook-in radio
- Now you can change cook button name to anything you want in Kitchen\settings.dat (if it doesn't exist, it is created)
- Dropped autoupdate function (I wasn't generating it for download anyway)
- Fixed that public release didn't had Tools update (I'm not allowed yet to publish it) so it crashed when copying Tools
- Now when copying files application doesn't look frozen, you can even select and copy text in cooking log
Kitchen 1.4.test
- Instead of opening windows, everything goes to logs
- No windows will open when cooking (except HTC Rom Tool and XVI since they're not console-only)
- Added new tab with cooking log
- Many more minor changes
- first preparations for more devices support
Kitchen 1.0.9 - last one before new minor build
- Now able to cook for different LOCALEs than 0409 (make sure you swap all folders with your LOCALE ones)
- Platformrebuilder does output to log.txt file in root of the kitchen, but still has opened black window, just ignore it
- Some anticrash fixes
- Etc...
Kitchen 1.0.8
- Added option (into More Tweaks menu) to insert welcomehead and splash images
- Fixed sometimes failing to copy htcrtproj file, or any other file into FLASH folder
Kitchen 1.0.7
- Added new feature - Tutorials section. Who has any tips what I should write about, write me PM or here to this thread.
- I've written few FAQs I've seen around
- Also disabled DEBUG mode in extracting nbh
- Added update option to update kitchen itself from internet
Kitchen 1.0.6
- Fixed after extracting RUU_Signed deleting "working" directory
- Now you must first close all menu's till able to do anything in main window (just for causion)
- Fixed "relly" to "really" when closing main window (exitting program) by ESC key
Kitchen 1.0.5
- Now you can convert complete OEM folder from different QVGA device (like HTC MEGA) to your EXT by one click, converts all PACKAGE* folders
- I forgot to update version, sorry for that
Kitchen 1.0.4
- Now you can export RUU_Signed.nbh into OEM, SYS and ROM folders - it doesn't work with cooked NBH's, only shipped ones
Kitchen 1.0.3b
- Only graphical changes, fixed last ESC/Enter keys action
- When clicked Quit, you must confirm it
Kitchen 1.0.3 - test build
- Improved stability when trying to overwrite files/folders that already exists
- Added scrollbars to selecting tabs (they we're out of display)
- Fixed crashing when OS.nb building has failed
- Added "Convert SYS to SYSpkg" for easy removing (I like having few SYS folders converted to EXT so I can easily find them)
- Removed unescessary buttons from dialogs
- Disabled resization, add ESC key actions in menus
- When upgrading, update Tools folder with enclosed recmod!
Kitchen 1.0.2 - test build
- Some fixes
- Added new "Convert OEM to EXT and place it" feature
Kitchen 1.0.1
- Added advanced tweaks (AKU, IdentName & IdentDesc, Calibration Data, Enable/disable welcome screen, Hide "Beam", ...)
- Changed COOK button
- Fixed "XDA Thread" link in About menu
Requests awaiting to be done: (my TODO)
- Could add the option to view files in the folders duplicates kitchen before you start the process of cooking the rom? To correct any error overwriting files before the cooking process.
- Add tab for adding easy registry stuff
- "When disabled Base package, disable DPI etc folders too" - done in latest .test8 version
- Extendir integration support
- Change a bit "Disable Customer Feedback" function detail
Donators:
Twopumpchump - $20
Witschey - $20
af974 - $20
aaraya1516 - $5
luiggi - $10
wbrown5 - $20
swiss240 - $10
Thank you all, every dollar counts!
Looks like its inbetween ervius and bepe kitchen. Will give it a whirl. Thanks bud.
Edit...
Runs ok, I tried to change EXT folders name, and it didnt like it. I prefer to have my own folder names, so that I know what I have in them!
In vista, it keeps poping up should kitchen run imgfs files! It doesnt do that in ervius for joshs kitchen in vista. So I am thinking there is a security thing maybe!?
All in all, good work, I always love GUI stuff!
OndraSter said:
fe~ROM kitchen
**** ME
Click to expand...
Click to collapse
Joking aside, this seems like a good kitchen. Thank you.
Quetzecotyl said:
Click to expand...
Click to collapse
Yea I dont like that "**** Me" too! LOL
**** ME will be added as Option. (and more things I will add like AKU and such).
This kitchen doesn't want to be like Erviuse's one - I want to make this directly for Kaiser and integrate different predefined tweaks etc. Only get them together will take some time.
OndraSter said:
**** ME will be added as Option. (and more things I will add like AKU and such).
This kitchen doesn't want to be like Erviuse's one - I want to make this directly for Kaiser and integrate different predefined tweaks etc. Only get them together will take some time.
Click to expand...
Click to collapse
I love the GUI. So good work there.
nice work brother, will download and try it out, i did bookmark this thread so i hope that you will keep interest with this and keep it up to date (as needed)
I've been working on some new features and I thought "Hey, I might integrate few tweaks I use".
What about this? More comming.
Also I was thinking of easy "buttons" changer (hold voice button/press voice button etc).
PS: I know that it doesn't support resizing/maximizing window, I will disable both of it.
PPS: **** ME! no more, back to COOK IT
OndraSter said:
I've been working on some new features and I thought "Hey, I might integrate few tweaks I use".
What about this? More comming.
Also I was thinking of easy "buttons" changer (hold voice button/press voice button etc).
PS: I know that it doesn't support resizing/maximizing window, I will disable both of it.
PPS: **** ME! no more, back to COOK IT
Click to expand...
Click to collapse
lol i just got the old one downloaded, but VERY nice brother
I nearly wet myself when I saw the **** ME button... LOL
Latest tweaks update till I release it:
+ it asks after ROM build whether you want to run KaiserCustomRUU.exe and flash it immediatily.
I'll upload it in the morning with clear head, now I'm gonna go sleep. Gnight ladies.
OndraSter said:
Latest tweaks update till I release it:
+ it asks after ROM build whether you want to run KaiserCustomRUU.exe and flash it immediatily.
I'll upload it in the morning with clear head, now I'm gonna go sleep. Gnight ladies.
Click to expand...
Click to collapse
lmao nite mommy
Looks good! Just dont make it too complicated!
OK, here we go: http://www.4shared.com/file/120731385/d9575efd/osKitchen_101.html
Replace the original .exe with this one, saved sessions are compatible (and always will be) on both ways.
is there anyway of using this in vista?

Vox Rose Kitchen 2.0 [WM 6.0 + 6.1 + 6.5] UPDATED to 2.0

Vox Rose Kitchen 2.0 [WM 6.0 + 6.1 + 6.5]
I present to you my new Vox Rose Kitchen v2.0.
​
It now supports the Vox and the Rose.
The downloads here will be Vox specific only. All the ROM, SYS and OEM folders will only work with the Vox.
For the Rose version go here!​
For all things you can do with the kitchen, please look at the thumbnail!
​
Requirements:
dotNET Framework (at least 2.0)
Microsoft Visual C++ 2008 Redistributable
Windows XP or higher is recommended (SplashMaker doesn't work under 64-bit operating systems)
Kitchen has to be located like this: %systemdrive%\Vox Kitchen\... -- So in the "Vox Kitchen"-folder should be the exe and all the folders (OEM,SYS,ROM,TOOLS)!
Downloads:
The download comes in two parts!
First is the TOOLS folder and the "Vox Rose Kitchen 2.0.exe".
The second part are the ROM, SYS and OEM folders.
General Downloads (always needed):
Download exe, bat and TOOLS folder
just click on install and it will unpack it to your system drive\Vox Rose Kitchen
Downloads for WM 6.0:
Download ROM + OEM + SYS for WM 6.0
Downloads for WM 6.1 (should be20282.1.3.6):
Download ROM + OEM + SYS for WM6.1 (Rose folders)
Neo-Package (replace the SYS packages)
WM 6.1 Languages
Downloads for WM 6.5:
Download ROM + OEM + SYS (21854.5.0.80 "Official" files)
Download ROM + OEM + SYS (23017.5.3.0)
Changelog:
v1.2 -> v2.0
updated the whole kitchen to be compatible with the Rose (S740)
made extracting a lot easier (therefore I removed the wizards), also gives you the XIP of the ROM
automatically implants xip when you place a xip.bin in the ROM folder (therefore I removed the XIP wizard, but it's still in the tools folder)
updated the build wizard accordingly
some new graphics
If you want to use the batch version, you'll have to use the old v1.2 where it's still included, but without the benefits of automatic xip implantation -> download 1.2
And of course Thanks to Dr. G!!!
The Building Process
Fire up "Vox Rose Kitchen.exe" in the normal kitchen folder ("C:\Vox Rose Kitchen") and go to the build tab. It'll look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The first step is to start G'Reloc and check if the values are right for the Vox (look at the picture) and click on "Do it"!
If you are cooking with WM 6.5 you might get errors, because G'Reloc isn't ready for Wm 6.5. In this case you click OK and then "Do it!" again and it'll tell you which module is producing the error. You can now either go to that folder and use Unlocker to unlock the "tmp"-file and delete it and then click "Do it!" again to keep going or you use recmod to make a file out of the module (better if you are cooking more then once). I recommend the recmod path it's easier and faster once you've eliminated all "bad" modules!
The WM 6.5 package I supply has all modules already fixed, so you don't need to worry!
When G'Rleoc is done (it might look like it hangs and then unexpectedly is done), you can close it and continue on with BuildOS. Here you can choose what to include and what not to include (only OEM packages, if you don't want certain languages (all the xxx_LANG_0XXX folders) or SYS packages you'll have to delete them manually! Please do not remove the package I have marked in the picture, unless you are re-integrating customer service (but why would you ).
Click on the green play button once you have selected everything you want! It'll say done at the bottom once it's done!
When it's done you can close it and click on "Create Vox ROM".
This will automatically insert a xip into the new ROM if there is one present in the ROM folder (xip.bin). You don't need a new XIP for 6.1 and I integrated the right one in my WM 6.5 package. So basically you don't have to worry about XIPs.
​
The cmd window will do everything on it's own and it's done when the window closes itself. You now have a OS.nb in the temp folder.
Now open then "Start HTC ROM Tool" and click on "Build!":
Under "Device" choose Excalibur.
Change the "Version" to what ever you want and leave the rest alone.
Then select a OS and choose the OS.nb in the temp folder.
Then click on "Build" and save the ROM in TOOLS\VoxFLASH and you are done with cooking!
​
Welcome back!
May you indicate the SYS-XIP included for every WM?
Thank you very much, frauhottelmann! Very long waited kitchen under WM6.5. Great work!
I added the build numbers, but I don't remember WM 6.0 build...
I have been waiting for WM6.5 kitchen for a long time. Great minds will come to work again.
cooking 6.5 will be fun.
Thanks!!
Thank FMs..did you have a good time in scotland?
I just ahd a quick look at this and...I got no chance lol
Thanks fh, was waiting for it, hope you had fun on your vacation
Hello, guys...
I´m completely new to Vox world, I´m coming from Excalibur, and I want to know if I´ll be able to backup my current rom with this tool. Also, I want to know if it´ll be possible to restore this backup if something goes wrong with a WM6.5 upgrade, for example.
I´m currently using WM6.0 Stock ROM. My vox never saw another rom in it´s life.
Also, is there a step-by-step guide to do this backup/restore procedure? I found some articles (using the search tool), but they seem to be incomplete or outdated. I´m really afraid of bricking my expensive device.
Thanks in advance.
Regards.
I uploaded the folders from my "Official" WM 6.5 ROM.
Updated to version 2.0 check first and second post for details!
Spoiler: automatic xip integration and new tutorial on cooking!
hi frauhottelmann
can i build a wm6.1 vox spanish rom with all the files available in the 1st post?
Also, where could I get a spanish language for building the rom?
thanks,
WM6.5 Offical V1 built and my phone hangs in bootloader splash for infinite time (I tried waiting for more than half an hour then gave up installing original HTC WM6 update)
I tried disabling the options for third party software (first 4 in the list) but still it hangs in startup screen.
From official word it seemed to me that it has stock WM6.5 icons form microsoft but later seeing "Clean" rom screenshots i became sure that the "official" will much look the same.
Regards
Moeen
kabeza said:
hi frauhottelmann
can i build a wm6.1 vox spanish rom with all the files available in the 1st post?
Also, where could I get a spanish language for building the rom?
thanks,
Click to expand...
Click to collapse
No, there are no Spanish files, I don't have them all.
dark_prince said:
WM6.5 Offical V1 built and my phone hangs in bootloader splash for infinite time (I tried waiting for more than half an hour then gave up installing original HTC WM6 update)
I tried disabling the options for third party software (first 4 in the list) but still it hangs in startup screen.
From official word it seemed to me that it has stock WM6.5 icons form microsoft but later seeing "Clean" rom screenshots i became sure that the "official" will much look the same.
Regards
Moeen
Click to expand...
Click to collapse
Don't know, what you're doing wrong, but I didn't change anything from my ROM to the kitchen, so it should boot (and nobody complained yet).
Otherwise please try v1.2 (download) and build the ROM with that version. I haven't tried v2.0 with the Vox, but it should work.
What do you want to tell about the icons?
frauhottelmann said:
No, there are no Spanish files, I don't have them all.
Click to expand...
Click to collapse
Any way to get plain files for translating into spanish? or most are built without source
frauhottelmann said:
No, there are no Spanish files, I don't have them all.
Don't know, what you're doing wrong, but I didn't change anything from my ROM to the kitchen, so it should boot (and nobody complained yet).
Otherwise please try v1.2 (download) and build the ROM with that version. I haven't tried v2.0 with the Vox, but it should work.
What do you want to tell about the icons?
Click to expand...
Click to collapse
I just installed clean v3.0 of WM6.5 and it has the original icons so my problem is solved in that regard.
Any way to get plain files for translating into spanish? or most are built without source
Click to expand...
Click to collapse
I have French, Czech, Italian, Greek and Polski/Polish localisations but unfortunately i dont have spanish localisation for Windows Mobile standard
Any fix to change sliding panel to default HTC one rather using Titanium (its slower than HTC's Sliding panel)
Could you please upload the WM 6.0 ROMs and OEM + SYS, but now using a *.zip or *.rar format, because the installer that you're using is crashing on my Windows Vista.
nathanpc said:
Could you please upload the WM 6.0 ROMs and OEM + SYS, but now using a *.zip or *.rar format, because the installer that you're using is crashing on my Windows Vista.
Click to expand...
Click to collapse
You can unpack the exe files with 7zip instead of the installer.
When I tried what I got was this:
Code:
Can not open file 'C:\Program Files\Vox Kitchen\oem_sys.exe' as archive
And the same for the rom.exe
That sounds like a corrupted archive then. Try re-downloading. I couldn't upload right now anyway!

Categories

Resources