First of all I would like to thank Ervius and Bepe for bringing a revolution here on XDA by Providing us with this Rom building tool called Ervius Visual Kitchen. Long gone old days where we used to build our roms with dos prompts. EVK has a GUI built on very strong tools to build a Rom for any device. This tutorial will make u aware of all the possible functions of this Tool and how to properly use it.
!!Starting on!!
Inspecting the Facility
To start with just download this Base Kitchen of mine through which I’ll explain you all the structure of EVK. You can Download it from here http://rapidshare.com/files/253466344/XDA.rar. Just open the rar file and copy the XDA folder to the root of C: drive. This is the kitchen root preview: as we can see in c:\XDA The reason to create the kitchen in the root of your drive is to avoid large Path name issues.
—————————————————————————– EXT Folder
The External packages (EXT) folder is divided into Device Specific folders and a Shared folder. You can get more information about the EXT Structure in our Tutorial on Understanding the OEM/EXT Application Packages and Adding new Applications
In Brief the Device Specific folders are typically used for files (packages) that should only be applied to a specific type of the device. Each Device Specific folder is further divided into Operating System Build Version Specific folders and a Common folder.
- Operating System Build Version Specific folders are typically used for files (packages) that should only be applied to a specific build (version) of Operating System.
- The Common folder is typically used for files (packages) that can be installed on any Operating System build version.
———————————————————————————-
OEM Folder
The OEM folder can contain multiple Device Specific folders. You can get more information on the OEM Stucture in out Tutorial on Porting new ROM Release and Exploring the OEM Main Folders of your Kitchen and Scanning the Important/Un-Important Packages
- Device Specific folders are typically used for files (packages) that should only be applied to a specific type of the device. Each Device Specific folder is further divided into Locale Specific folders and a Common folder.
- The Common folder is typically used for files (packages) that can be installed in any locale – not specific to a language.
- Locale Specific folders are typically used for files (packages) that should only be applied to a specific locale.
—————————————————————————————-
ROM Folder
The ROM folder is divided into Device Specific folders and a Shared folder. You can get more information on the ROM structure in our Tutorial Understanding the Rom Structure, MsXipKernel and OemXipKernel
- The Shared folder is typically used for kernel system files that are compatible amongst devices. (MSXIPKERNEL folder).
The Shared folder is further divided into Operating System Build Version Specific folders.
- Operating System Build Version Specific folders are typically used for kernel system files that should only be applied to a specific build (version) of Operating System.
- Device Specific folders are typically used for kernel system files that should only be applied to a specific type of the device. (OEMXIPKERNEL folder).
Each Device Specific folder is further divided into Operating System Build Version Specific folders.
- Operating System Build Version Specific folders are typically used for kernel system files that should only be applied to a specific build (version) of Operating System.
—————————————————————————–
SYS Folder
The SYS Folder contains all the system base files, or the Operating System files and drivers from Microsoft. The Build Version Specific folders will often contain files (packages) specific to the device DPI (Dot Per Inch) and Horizontal/Vertical display size. You can get more information on the SYS structure in our Tutorial on Porting new OS Build and Exploring the SYS Folder of your Kitchen and Scanning the Important/Un-Important Packages
The system (SYS) folder is divided into Operating System Build Version Specific folders.
- Each Operating System Build Version Specific folder is further divided into a ROM DPI, ROM Resolution, and Shared folder, providing a significant amount of flexibility during ROM compilation. The ROM DPI, ROM Resolution, and Shared folders are further divided into Locale Specific folders and a Common folder.
- The Common folder is typically used for system files (packages) that can be installed in any locale – not specific to a language.
- Locale Specific folders are typically used for system files (packages) that should only be applied to a specific locale,
for example, 0409 (English).
——————————————————————————–
!!!!!Setting up the ROM and SYS!!!!!
Now we must know that these days we currently at latest have 3 Operating System versions provided with us, the well known Wm 6.1, the recently released Wm 6.5 and the soon coming or developing Wm 6.5.x. All are based on WinCE 5.2 and all have different set of Native Kernels. Wm 6.1 have the Old set of Kernels with just 2 Open Slots of virtual memory. Whereas the New Kernels for Wm 6.5 and Wm 6.5.x open 2 more slots making more space for the virtual Memory. You can read more and understand everything about Vitual Memory and download latest available Native Kernels out HERE. Now this for 21815 build but as we must know: OEMXIPKERNEL is the Kernel part that is device specific designed for… so we just gonna use this folder and of course… the “Romhdr.bin” and “os.nb.payload”
6
(so with this info we have the part of the kernel for every build we think to make) keep this files safe cause we gonna use it always. the xip.bin is not needed cause is not the meaning of this tutorial to port the XIP… so the kitchen wil ask for the file, instead that we dont want to port, so use the xip.bin that is on the build 23001 check the pic bellow.
The MSXIPKERNEL is the build OS specific kernel part… so…
The kitchen will takes the OEMXIPKERNEL (the native NK by Utak3r) and the MSXIPKERNEL for the build to be compiled, and we could have the kernel complete.
The MSXIPKERNELLTK folder (Logo Tool Kit) Is not needed, it has just a .DSM that allows the carrier to make important fixes and upgrades to thir ROMs (But even they didnt use it) so we dont need it anymore. Well… we gonna set the kitchen with the BUILD
Unrar it to a different folder cause we need to set this as a base… I will use my kitchen as a base to reference… but first i will show you all the folders in SYS that has the 23001… so lets see what we got!
And we need too the MSXIPKERNEL from this build check it on the pic
At this point we must to have this things
1.- Native OEMXIPKERNEL 2.- Native os.nb.payload file 3.- Native romhdr.bin file 4.- MSXIPKERNEL folder 5.- Xip.bin file from 6.- SYS folders from 7.- Ervius kitchen from my RS upload on first post
—————————————————————————————————————————————-
WHERE TO PLACE WHAT???!!!!
Pay attention on the place you put folders the name of the tree folder will gives you the correct place, so in the pics bellow i set at “”LEFT”" how it should be at finish and in the “”RIGHT”" the tree only for reference.
NOTE: if you see a folder on the original build ported address that you have miss to organize please ask or read again and see the pictures again. (I dont know what does the folders are for, well… maybe lots of them i knew, some others i dont…)
FIRST!!!! ROM Set romhdr.bin, os.nb.payload and xip.bin 
Set OEMXIPKERNEL 
Set MSXIPKERNEL 
Second SYS!!!!!! check the tree always you dont need to create folders I already did it!!! just paste the folders on that folders… questions at the end please
Note!!!!! In Newer Kitchens… 1.7 to date, the .VM folder must be set on the following address: “”"C:\<YourkitchenNAme>\OEM\<YourdeviceNAME>”" “” i dont know why newer kitchens cant found the .VM folder inside the common shared sys folder… So keep it in mind!!! Third EXT!!!!!!!!!!!!! 
Fourth OEM!!!!!!!!!! 
Certainly, the kitchen ask for the OEM_LANG_0409 package and i think all the others so… paste the whole OEM to this kitchen from the josh’s kitchen., or your favorite chef’s kitchen.
(NOTE: For other devices…. That folders OEMDRIVERS OEMoperatorspkg,OEM LANG, can get that folders if you dump a stcok rom that is the most recommended if not… you can download a kitchen for your device that kitchen must have this folders)
Setting the .bat file for Hermes device!!!!!!! Or others!!!
If you make an update from the kitchen i posted(10.4) so you must to edit the .bat file as follow…
Lemme introduce y’all the quote of the guy who make this posible… (pp change) you can get from this quote the lines.
Quote:
| BY Utak3r: For all those who can’t get pp right: Edit your TOOLS\kitchen_build_rom.bat and find the line with implantxip and replace it with those two lines: ..\TOOLS\osnbtool -ap xip.bin %pp%MB -y ..\TOOLS\implantxip -xip xip.bin -payload OS.nb.payload -imgstart %imgstart% -%uldr% -%nocert% Of course you have to have osnbtool.exe in your tools directory |
To end this process lets copy the osnbtoll.exe to tools as follow
And we are good to go!!!!
WHOOO HOOOO!!!!!!!!!!!! we finish!!!!!!!!! its already set! so this is the kitchen UI, if everything was ok the kitchen launch without troubles if you saw an error check the folders it says (SVN folders don cause troubles at starting the build proces) SO just set the device, XIP, SYS EXT and OEM and select the apps to be installed or not clickng double. HAPPY COOKING GUYS!!!!
BTW i edit the build_rom.bat in the tools folder to make it for Hermes there is an option to set the ULDR but i cant figured out how to use it on hermes… the UI may change on every update so…
try it at your OWN risk I’m not responsible for damages to your device
If you dont know what are you doing first ask your querry by writing a comment below and then move forward. We’ll assist you as soon as we can.
