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
Related
Universal WM6 ROM Kitchen
Finally I'm able to steal some time to upload this Kitchen, the intention is to get everybody involved and understand and maybe help with the development of wm6 for universal, and also everyone can built their own personalize universal WM6 ROM, hopefuly user or any rom modder sending some patch or registry modification or some part update to the kitchen...
Big Thanks to MAMAICH and also my friend Bepe, the two Genius on the forum I know...
Most of this Guide is taken from bepe's, and also some of the dev tool are taken from Bepe's, and ofcourse MAMAICH so credits goes to them also for his great method and tools!
lets start,
helmi
----------
ROM Kitchen is a tool to cook your personal Universal Windows Mobile 6 ROM by the packages you need.
Your Computer must have .NET Framework v2.0 installed!
THE KITCHEN:
Someone might need to mirror it somewhere?
ftp://xda:[email protected]/Uploads/Universal/helmi_c/helmi_uni_wm6_kitchen_r0.rar
OEM Pack Included in R0 Kitchen (Most of it part are newer then currently available rom):
Camera&MMS=3.5.1.5
CommManager=1.3.7.0
mHub=6.29.061106.I0
PicturesExt.dll=1.20.911.610
PowerService.dll=2.15.1.0
WirelessMgr_Service.dll=2.21.0.0
NETCF2_SP2= .NET Compact Framework 2 SP2
JAVA
SIM_Mgr=5.30
STK_Service.dll=4.47
StreamingMedia=2_10_1025621
Zip=1_20_25226_1
ps: the kithen is ready to build vanilla version, just
1. Click createos.exe
2. Click start button (createos.exe dialog) wait till its finish.
3. Click CreateROM.BAT, click encode, browse nk.prj, set operator
4. flash....Done.
OEM PACK:
I'm just too lazy to link them one by one...
BTFtp=1_1_27419_1
BTSapProfile.v1.45
CambridgeMSBTPlug-In
HtcWmpPlugin
Indialler_Phonepad_15_Language
MS.VoiceCommand=1.6_UNIVERSAL
OneNoteMobile=12.0.4518.1010
Pocket_MSN
PocketXPDF=0.50
Resco_Explorer 5.42
SDDaemon_UNIVERSAL
StowawayBTMouseKeyboard
SymbolPad=1_0_24075_1
Szilamer_BubbleFix
Szilamer_WordSuggestionFix
TaskManager=1_0_27407
USB_HDD
VGAMode
VOIP
WinliveVGA
WM5torage 1.7.3
WM6_CustomerFeedBack
NETCF2_SP2
JAVA
Zip=1_20_25226_1.rar
more will be added by others maybe? TOMTOM? SPB PLUS?, wiki page might be ideal for this...
How-To build a ROM:
1. Extract the kitchen pack to the c:\DEV folder (create the folder if u dont hv it)
2. Extract OEM Packages you need to OEM folder
3. Run CreateOS.exe and click the button
4. Run CreateROM.bat, proccesing....
5. HTC64_Extended_ROM_Tool.exe will start, click encode, then browse for C:\Dev\Helmi_UNI_WM6_Kitchen_R0\Temp\nk.prj then click next.
6. Set ur operator in operator name text field, default is set for 02 (02__01) u might change this to TMOB, MDL, etc then click encode when u finish to convert nk.nba to nk.nbf, the nk.nbf (ROM) will locate at C:\Dev\Helmi_UNI_WM6_Kitchen_R0\Temp folder.
{
"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"
}
7. ROMUpgradeUt.exe will start to update the rom to ur device or u might cancel if u planning to update latter.
Done! U Just create ur personal Universal WM6 ROM!
How-To build ur own OEM Package:
An OEM Package is just a simple folder containing files and registry settings for the ROM
First of all you'll need a GUID number for your Package.
Go to http://www.famkruithof.net/uuid/uuidgen to get one.
In my case:
283b9db7-cb03-4c1b-820e-ca49b2c3b5db
Necessary steps:
1. Create a new folder:
Dev/OEM/[Your package name]/
2. Create a empty text file:
Dev/OEM/[Your package name]/283b9db7-cb03-4c1b-820e-ca49b2c3b5db.dsm
(CreateOS.exe will finish this file for you)
If needed:
3. Create an UNICODE text file:
Dev/OEM/[Your package name]/283b9db7-cb03-4c1b-820e-ca49b2c3b5db.rgu
This file could be used to add registry entries to the ROM
First line is:
REGEDIT4
...
and there MUST be a empty line at the end!!
4. Create an UNICODE text file:
Dev/OEM/[Your package name]/initflashfiles.txt
This file could be used to create folders or copy files, shortcut on the ROM.
For Example/ Ilustration: Open or read Dev/LOC/initflashfiles.dat using a text editor or any premake initflashfiles.txt at one of the OEM folder.
and there MUST be a empty line at the end of iniflashfiles.txt also!!
Copy all files you need to Dev/OEM/[Your package name]/
How to change Universal paging pool SIZE:
Open nk.nba with hex editor and search for hex 64B00000640000002E2E2E2E00002E00 with 2E as a joker string and the last 2E00 is ur paging pool size. or just goto offset 51A502 and start mod ur paging pool see ilustration bellow:
the picture show us 4.8mb(48) paging pool (standart) change to 60 (6mb), 70(7mb), or any size u like.
How to fake ur CE version and OS Built
(only if u kinda person who like to fake stuff, not recommended thought)
How to fake ur CE version:
open nk.nba/nk.fat with any hex editor and go search unicode string 2.00.02 (the real version) or goto address 477C and 31437C and modify to any version u like, 2.99.99 or 2.00.99 or 2.01.06 or 2.01.08 or maybe 9.99.99? if u like... but still, its a fake, well its up to you...
Ilustration picture:
How to fake ur OS Build:
convert shellres.dll.0409.mui module (dir) to file and edit string 918 at resource ID 14683 and 14684 to any OS version u like, u'll have OS build 10.10 (Build 99999) OS if u like...but still, its a fake, well its up to you...
Ilustration picture (u'll hv OS 10.50.9999 (Build 99999) isn't amazing? more update then ms one...:
How to cook ur Extended_ROM
I'll update someday, running out of time...
Well, the kitchen and also some instruction (hopes u guys understand) are here now, so? why dont you guys built ur own personalize WM6 ROM...??
I hope more people will understand and gettin more involved and helpful with rom making stuff after this, and more people will support each others with bugs and updates... lets work togather guys... next would be AKU3.3 and AKU3.5 kitchen if I hv time...
hopes that i'm not forgot about something...lol...
regard,
Helmi
EDIT:
Added wiki page by my old buddy GerardNL, Thanks GerardNL, my friend...
Kitchen WIKI:
http://wiki.xda-developers.com/index.php?pagename=HTC_Universal_WM6_Kitchen_Helmi
the link doesnot work.
what a great guide, but can't download the kitchen..
ftp://xda:[email protected]/Uploads/Universal/helmi_c/helmi_uni_wm6_kitchen_r0.rar
Link above is working, file download ok for me. File not corrupt.
Helmi
What a great gift ! It makes a little bit easier to understand how to make something face our particular needs. a way to make everyone happy with the parameters and applications he likes. by default.
Thank you !
WoOoOoW. CoOoOoL.
Will download, learn and try.
You have disappear for too long. Beside this kitchen, any new ROMs with Video Call Working?
Very Very thanks from Italy.
helmi_c said:
Most of this Guide is taken from bepe's, and also some of the dev tool are taken from Bepe's, and ofcourse MAMAICH so credits goes to them also for his great method and tools!
http://buzzdev.net/index.php?option=com_simpleboard&Itemid=59&func=view&id=23392&catid=64
Click to expand...
Click to collapse
One matter.
This link doesn't work.
One Question.
One Wizard to translate the roms is it possible?
2nd problem.
I try this:
ps: the kithen is ready to build vanilla version, just
1. Click createos.exe
2. Click start button (createos.exe dialog) wait till its finish.
3. Click CreateROM.BAT, click encode, browse nk.prj, set operator
4. flash....Done.
Click to expand...
Click to collapse
At 3th point after I Browse nk.prj I click Encode and I've this error:
Hi Helmi_C
The link is working for me.
Thank you for the kitchen, great work!
Greetings, Leo
Broken FAQ link
http://buzzdev.net/index.php?option=com_simpleboard&Itemid=59&func=view&id=23392&catid=64
Is the page you Link to Helmi.. I cant call it up either!
cicciocant said:
2nd problem.
I try this:
At 3th point after I Browse nk.prj I click Encode and I've this error:
Click to expand...
Click to collapse
I get the same error code as well!
thx .............
Great Job , Thanks
cicciocant said:
2nd problem.
I try this:
At 3th point after I Browse nk.prj I click Encode and I've this error:
Click to expand...
Click to collapse
Juggles said:
I get the same error code as well!
Click to expand...
Click to collapse
did u guys extract the kitchen to c:\dev ? so the end result should be C:\Dev\Helmi_UNI_WM6_Kitchen_R0, the error is because the nk.nba cant be found... the nk.nba should locate here C:\Dev\Helmi_UNI_WM6_Kitchen_R0\Temp\Nk.nba
cicciocant said:
Very Very thanks from Italy.
One matter.
This link doesn't work.
One Question.
One Wizard to translate the roms is it possible?
Click to expand...
Click to collapse
yes, the link to buzz is dead, I'll erase it...
if you hv another LOC (Localization MUI) it should possible, btw darkforce hv post a rom with many language? u can take its MUI and HTM help file with another language. just replace the loc folder with foreign LOC.
helmi_c said:
yes, the link to buzz is dead, I'll erase it...
if you hv another LOC (Localization MUI) it should possible, btw darkforce hv post a rom with many language? u can take its MUI and HTM help file with another language. just replace the loc folder with foreign LOC.
Click to expand...
Click to collapse
the mui and htm only can replace by OEM folder , in LOC not enough for that,special for IMU very difficult to replace,also need to edit reg key
helmi_c said:
yes, the link to buzz is dead, I'll erase it...
if you hv another LOC (Localization MUI) it should possible, btw darkforce hv post a rom with many language? u can take its MUI and HTM help file with another language. just replace the loc folder with foreign LOC.
Click to expand...
Click to collapse
Thx. I Solved.
TO translate Can I Take the .mui file from Wm5 Aku 3.5 Italian ROM by fly?
It's very difficult?
Ufone Operator ID
Hello Helmi thanks for the Kitchen and love you for the 1.1 Rom.
Can you tell me how to set Operator ID for Ufone in pakistan because I have never been able to successfully change the code that I get "41003" in the phone app even after editing the nbf in WM5 Himalaya Roms as well.
Do I write Ufone_41003 in the Operator Id line or what?
Here is what I get from running CreateOS.exe with extra included (see attached).
Running CreateROM.bat prompts for missing default.hv, boot.rgu which I copy from somewhere in the kitchen. But prompts for Boot.hv which is no where to be found. (Can find in my PPC).
What did I do wrong?
But still able to continue to get nk.nbf. Can flash this? Is this same as Helmi-WM6-v1.1?
i don't know how you guys do it, but thanks very much all of you!!!!
Wow......Great job!
I had been waiting for it for a long time.
http://forum.xda-developers.com/showthread.php?p=1159759#post1159759
Thanks......
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
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
My Guide to cooking requested by a few of my ROM users.
- IMPORTANT -
Make sure you have Visual C++ 2008 and M$ .Net Framework and it's Service Pack.
- NOTE TO COOK -
These Sys and Xip files are for 96 dpi devices only or commonly known as QVGA. So Please if you want to cook for your device using my guide, please make sure your device is as such.
- THE PREP _ Gathering Your Ingredients-
You can download my kitchen.
(Extract my kitchen to the C:\ directory (the root of your harddrive))
-OR-
Download the kitchen files below and create your own kitchen.
Create a directory C:\kitchens\
(Go into the C: drive and right click in an open area. Hover over 'New' and the select 'New Folder' and name it kitchens.)
Then download these kitchen files:
Link 1
Link 2
Link 3
Link 4
Link 5
Link 6
Link 7
(These links were brought to you by JustKitchen.info)
These links are archived with 7-zip.
When you have all these files downloaded, and you have 7-zip installed, Select all of the files you've downloaded. Then right click on one of the highlighted files and hover over 7zip in your dropdown menu and then click on 'Extract Here.'
{
"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"
}
This will create a directory that looks similar to this:
As you also see in that picture (The 'Working_Folder' archive) you'll need my Sys & Xip files. And as you know me, I will always try to keep this folder updated so that when a new build comes out you guys can cook with it too, Which you guys can find HERE or any of my ROM threads. Right now I have all the newest builds. So you guys are set
_If you downloaded my kitchen instead, then it will have come with build 23545 & build 23563 only (Which are Windows Mobile 6.5.5 - the latest Windows Mobile Builds)._
After you download my Working_Folder.7z then just extract the files as shown (Just right click on the file and hover over 7zip and you can click on 'Extract Here.'
And yes, lol, my computer is names Muff - PC because me and my wife's pet names are Muffin, lol.
Now, click 'Yes' when it prompts you asking if you want to Merge the folders and then also click 'Yes' to Overwrite the files there if necessary.
Once you have the kitchen setup the way you want it, (you'll also notice the PagePool Changer I have in there) then go up one level in the folder to where you see Working_Folder and send a shortcut to the desktop as you see below:
Here is where you'll need to make changes to your files (Because my files have my background image and watermarks and all of my GUI changes..etc..).
Navigate to C:\kitchens\SuperJustKitchen\Working_Folder\SYS\23563\dpi_96\COMMON\Base_DPI_96
You can download this Base_DPI_96 folder here if you want the original files..
Just drag and drop over the Base_DPI_96 folder in the C:\kitchens\SuperJustKitchen\Working_Folder\SYS\23563\dpi_96\COMMON directory.
After you're all set in making your GUI changes then navigate to
C:\kitchens\SuperJustKitchen1\Working_Folder\EXT\SHARED\THEMES_QVGA
This is where you are going to change your background images. The most important part about making these images is the fact you need to keep them perfectly proportioned to your device. If you have a qvga, like my Wing/Herald, then its going to be 240 x 320 (portrait) and 320 x 240 (landscape).
When you're done making your images make sure to rename them respectively.
Now navigate to C:\kitchens\SuperJustKitchen1\Working_Folder\EXT\SHARED\Control Panel\HTCAnimation_1_3_5_0\files
This is where you'll change the splash screens. And Please do ^>^ because we each should have our own unique style of cooking, lol.
Just find an animated .gif image - Also 320 (tall) x 240 (width) - and just rename it Animation2.gif
Then Find a still image of whatever you'd like and rename it welcomehead.96.png
Just take mine out and dispose of them..
- End of Prep -
Part two below.
- PART TWO _ More Prep -
Okay. First thing is navigate to your Working_Folder, which should be on your desktop continuing from the last post. Open the ErviusKitchen.exe
Let it load, then click on the drop down menu in the picture and land it on Herald. It will go crazy for a second, but, that is normal.
Next, click on the dropdown menu for the XIP and SYS and land them on the build you're using. I am using, the included, 28223 build.
Next, you're going to add your ROM version number. In the picture is how I normally label mine.
Should look like this:
Using LZX Compression is useful when you notice your ROM is too big. The Max size a ROM can be is about 80MB or so. If you plan on not flashing by SDCard then the minimum size of the ROM should be 50.1MB. When you are ready to cook, you'll see the size in bytes. So, in bytes, 50.1MB is 52,567,531
- - -
Next, click on Show Editor.
This will bring up all the .rgu files that are located in the kitchen. Scroll down to where you see the .rgu file located in the Shell.
Double click on it and it will open up the editor. Locate line 419. This is where you can 'brand' your ROM. All my ROMs I create usually have the branding '- Trib.' Put anything you want after the '- ' (and you also have to leave space right after the '- '). Then make sure to save. Then close out of the editor. Then go back to the main kitchen window.
- - -
Next, click on Extra Buttons.
This will bring up a menu with large buttons. Click on the CABtoEXT button.
That will bring up a command prompt window as shown:
Minimize all the other windows. Then hit the Enter key. This will open up a large window.
Then navigate to any of the cab files that you might want that are not listed in the kitchen. Select and Right-Click on the cab files that you want then click on Copy.
Then Right-Click and Paste the cab files into the window that popped up.
When all the cab files have been placed go back to the other command prompt window and then press Enter where you see Press any key to continue . . .(and make sure to only put up to four at a time.. for some reason it doesn't work right).
A prompt will follow asking if it will be used for 96dpi devices. Make sure you select the respective digit for 96dpi then hit enter. Another message will prompt you to select what devices can use the programs. Make sure to select All devices.
Your cabs you import into the kitchen will be located in the 0096 Category in the list
- - -
Now head back to the kitchen's main window. Next we are going to Save the ROM so far. Make sure you save with a version number (sometimes if I save before I put a version number I'll forget to put one all together. Basically a ROM won't flash without one.
Now Close out of the kitchen all together then re-open it. Reason being is because the cab files you've just installed won't show up until you do. Then Load your previously saved ROM.
Now it's time to make your selections of what is going to go into your ROM. Double click on each file/module to toggle the enabling/disabling of packages.
These are my selections:
Once you've made your selections make sure to save once more.
- End of Part Two_ More Prep-
Cheers,
Trib
- PART THREE _ Cooking -
Now you are ready to cook. Press the Create ROM button.
You will see more craziness:
This process can take up to an hour depending on how many cores your computer has - it's a logical based kitchen ^>^
Once the process is complete, navigate to C:\kitchens\SuperJustKitchen\Working_Folder\RELEASE_HERALD and click on the ROM Update Utility. Or you can use the PagePool Changer to change the pagepool to something other than the default, which is 6MB. Changing it to 3MB will give you about 5MB more Ram. But it also has a trade-off of slowing your ROM down a bit.
Put your device into the bootloader by soft-reseting it (by pressing in, with your stylus, the little hole on the left side of your device) and also holding down the camera button. You will then be in a, what we call a tri-colored, screen.
Then check off the check box and press next. Do this again. Then it will pause. Then the utility will pop up again and click on next twice and then UPDATE.
Once you flash the ROM to your device, upload it with RGhost.Net
Then post the link in this thread. I would like nothing more than to see the fruits of yours and my own labour.
Cheers,
Trib.
-End Part Three _ Cooking -
An excellent and to the point start!
Let me be the first to congratulate you! This tutorial is going to help people like me tremendously!
Hm. i just realized I forgot to mention that these Sys and Xip files are for 96 dpi devices only or commonly known as QVGA. So Please if you want to cook for your device using my guide, please make sure your device is as such.
Long time viewer, first time poster.
I am also looking very forward to this tutorial. I've been messing around in the "kitchen", just getting the feel of it.
Looking forward to a better understanding.
Thanx for all the hard work.
Thank you for this!! I will try to.
Your welcome. I can't wait to see what your ROMs will be like.
WOW! Nice tutorial!!
If I mess it up now, it could only be due to my own un-geekness.
Just one question: Would it be too much trouble to outline just the files needed to create a "bare-bones" rom; i.e. a rom that will work (duh), but have as little "fluff" as possible?
Excellent work!! Donation is on the way!
Thank you for your kindness.
And that is exactly what I did - If you select the selections i've made you'll come out with a barebones system with all the necessary files.
nothing
not appear
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]...
img: http://cwmobile.webcindario.com/nothing.PNG
what is the error?
thanks in advance..
Hm. Didn't realize that it wasn't in there. You can manually enter it in there. But I'll include it for you... Just redownload
Tribulattifather said:
Thank you for your kindness.
And that is exactly what I did - If you select the selections i've made you'll come out with a barebones system with all the necessary files.
Click to expand...
Click to collapse
Ah, OK, excellent.
Please pardon my noobness.
I'm at work right now. I'll hit that PayPal button when I get home (I don't want to be typing logins/passwords on this PC, for obvious reasons).
It can't be said often enough: Thank you for your work.
I surrender, thanks for try help me...
Don't surrender, lol. I'm uploading the files you'll need right now.
I'll post back here when its uploaded.
UPDATE: Added the correct files to the SYS folder; you will now be able to 'brand' your ROM now.
Tribulattifather said:
Thank you for your kindness.
And that is exactly what I did - If you select the selections i've made you'll come out with a barebones system with all the necessary files.
Click to expand...
Click to collapse
i have to disagree with you there. You have included many unneeded things for the average user.
To name a few unneeded:
ADC, Adobeflash/codecs, DRM, Entertanment, ipsecvpn, SQLCEMobile, Transcriber, Voicecommand, HTC animation, SIM_Tkit, Net CF.
Just my 2 cents
Granted your roms are more geared towards everyone. Many know mine were not
Oh yeah, I know what you mean. I only meant that this was a barebones ROM that I would make. I guess one could construe that I meant barebones for an average user. My apologies :1
But best thing one can do is cook , cook , cook and cook some more until you get the ROM you want, lol.
thanks, but if I yield to truth, and you can not download the files because they are heavy and my internet is 256 and download speed is + / - 30 kbs.
thanks... thanks... and thanks...
What build would you like me to upload separately for you? I think you said you needed 28223.
This file is only 30MB and contains only 28223 with the updated Shell folder:
http://rghost.net/download/980604/6a9cbd59a9d861179da20ac3f06349b222d8cfda/Working_Folder.7z
Cellomancer said:
Ah, OK, excellent.
Please pardon my noobness.
I'm at work right now. I'll hit that PayPal button when I get home (I don't want to be typing logins/passwords on this PC, for obvious reasons).
It can't be said often enough: Thank you for your work.
Click to expand...
Click to collapse
Thank you so much Cell for your kindness. I will prioritize your needs if you do need anything.
Work in progress..
Now the purpose of this guide is only one, to guide you through “cooking” your own stock flashable ROM from a shipped ROM… That’s it. It’s not hard but it does help you start the journey of the real dev work. There are to many "Devs" around that just do something like this guide and copy files from other ROMs to theres, And this DOES NOT make you a Developer so please dont go posting stock deodexed ROMs everywhere and call yourself a Developer
Before starting I’m going to assume you have setup the correct ADB Drivers for your device although not really needed to make a ROM, it does make it easier in the long run.
Once you run through this guide you will have a stock ROM with ROOT permissions, DeoDexed, Zipaligned, Busybox and init.d support. From there you can modify your ROM to your hearts content, all this is doing is making your base. The real Dev work is .smali editing, modifying .xmls making your own apps, etc... This guide will just help you to not rely on other members to release "Stock deodexed ROMs"
Wording:
ROM = An Android Operating system
Cooking = Making your own ROM
Shipped ROM = A Stock ROM for your device, e.g. a RUU.exe etc…
Kitchen = The Dsixda’s ROM Kitchen
ADB = Android De-Bugging
CWM = Clockwork Mod Custom Recovery
zImage = Kernel controls CPU, Battery etc.
Modem/Radio = Controls cell signal, internet etc.
ROOT = ROOT Permissions, access to the ROOT or / of your device, kind of like the Windows folder on your computer.
DeoDexed = Removing the .odex files from a ROM to allow for .apk customizing e.g. Theming etc..
.apk = Android application file
Init.d = Allows the running of scripts such as Memory tweaks and SD-Card tweaks etc.
SU = Superuser
CMD = Windows Command Prompt
MOD = Modification
Click to expand...
Click to collapse
ADB Short codes that may be helpful later:
Type these directly into your CMD window with your device plugged in.
adb reboot recovery = Reboots your phone straight into recovery mode
adb reboot = Reboots your phone
adb push = use this to push files to your phone, make sure you are in the folder with the file you want to push in CMD (Example, adb push c:\android\SystemUI.apk /system/app)
adb logcat = Tells you what your phone is doing.
adb remount = Remounts the partition specified (Example, adb remount /system)
Note 1:
When making a ROM the overall concept is the same for every device that runs CWM or any other custom recovery. The only main difference is extracting the files you need from the Shipped ROM
Note 2:
It makes it easier to have a shortcut to your kitchen folder and any others you need in your favourites or dektop
Part 1. Setting up the “Kitchen”
Go to THIS FAQ and choose the method you prefer to install on. If you are running Windows I recommend the Cygwin way. It’s easier and you don’t need to keep booting between Linux and Windows, You don’t even need Linux if you do it the Cygwin way. And please do get the pictorial guide HERE, it helps A LOT for “noobs” and don’t forget to install the Java JDK if you do Windows Option 1. Keep in mind that doing it on Ubuntu IS much faster.
NOW IF Cygwin is to difficult for you, just download Ubuntu and install it next to windows.
Part 2. Extracting the files you need.
There are a few different ways you can do this, the main ones are:
For HTC Devices
Get a RUU.exe from the internet for HTC Devices and extract the system.img and boot.img
Download the RUU and run it on Windows, proceed until you get to the screen with the picture of the phone, see bellow. – (No you don’t need to plug your phone in)
{
"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"
}
Open your Start Menu on Windows
In the Windows 7 search bar type %temp% and hit enter
In the folder that opens click in the search box in the top right corner and search ROM.zip
Drag ROM.zip to your desktop, open and extract system.img and boot.img to your desktop.
________________________________________________
For ANY Android Device (Or if you cant get them any other way)
Using a backup of a stock ROM, This way gives you the ability to make a ROM from pretty much any device that has CWM installed.
Taking the system.img and boot.img from the backup folder
________________________________________________
For Samsung Devices:
Extracting the following from a Samsung Shipped ROM
factoryfs.img (and optionally: cache.img, zImage, modem.bin)
TAR file containing factoryfs.img (optional: cache.img, zImage, modem.bin)
ZIP file containing factoryfs.img (optional: cache.img, zImage, modem.bin)
Any of these above methods can be used and the extracted files placed in the ORIGINAL_UPDATE folder of the kitchen in the next step. If your device is not compatible with these methods check the device list in this THREAD for more guides.
Part 3. Setting up the working folder.
Now we have the files needed to make our ROM let’s get to it!
Go to your kitchen folder then the original_update folder and place your files in It
Start the kitchen by starting Cygwin and typing cd kitchen then ./menu
Hit option “1. Setup working folder from ROM” press enter again
Select the option you want from the list e.g. “(1) system.img and boot.img”
Rename the folder if you wish but it doesn’t matter, hit enter
If you are working from system.img and boot.img you need to run through the extraction process in next step. Most new ROMs use an EXT4 file system so if you are unsure just hit option “2 – Run Ext2Explore (EXT3/EXT4)” and follow the instructions in the Cygwin window (If you are just using a .zip or .tar etc. you don’t need to do this step.)
When that’s finished hit “3 – I’m finished unpacking / abort”
Finally hit Y to see you working folder details once its run through the process.
Part 4. Add the options you want to add
A good thing to do now is, keep it simple. The kitchen is best to use only for making your ROM base, once you have the .zip file most customizing can be done from there unless you need to edit the boot.img etc. but we are not going to get into that in this guide.
Now, we are going to make a simple ROM base optimized for speed and functionality. Follow the next steps and by the end you will be ready to build the ROM.
The most obvious of all, we will add “ROOT Permissions”. So choose option 2.
Always stick with Chains method so hit option F, this won’t take long at all, wait for it to finish the press enter to continue.
Next add Busybox with option 3, hit Y to continue and enter when finished.
Most people disable boot sounds (option 4), I usually just do it later if I choose to.
Don’t worry about Zipaligning because we will do it when we build the ROM.
Next choose option 0 for advanced options.
If you ROM isn’t already DeoDexed choose option 11
If you wish you can backup both folders but I usually don’t bother.
Then select option B to Deodex BOTH folders, this one will take some time, on an HP Laptop core2duo with 4gig of RAM takes about 15 minutes.
Now add /data/app functionality so choose option 13 and select Y to continue, This allows you to move apps from the system folder to your /data/app folder before the install, which in turn allows the end user to uninstall the apps if they wish. This can ONLY be done with certain apps, like apps you get from the market.. YouTube, Google Maps, Twitter etc. DO NOT put dependent apps like SystemUI.apk etc in the /data/app folder.
Next add the Nano text editor on option 14
Next add Command Shell or “Bash” with option 15
Next add init.d support with option 17 to allow the running of init.d scripts, sometimes you may have to manually add the init.d folder to your ROM at the end or before build, either way it doesn’t matter.
Now we are ready to build the ROM and flash it. Understand that all these are optional, if you want to you can just deodex the ROM and go straight to option 99 and build the .zip file. This is just what I recommend you do
Next go to option 99 when you’re ready to build your ROM.
For now you will choose option 1 “Interactive Mode”
When it asks you to Zipalign your .apk’s you can now choose Y and it will quickly run through and Zipalign all the .apk’s in your build.
Once finished, it will start building you ROM.zip file this may take about 5-10 mins on a slow computer or if your CPU is busy already.
When that’s finished it will ask you to either continue with the updater-script or not, this is always a YES for you guys, so hit Y and move on.
Now we need to Sign our ROM, this is always a YES also
The final step is to either rename your ROM or not, it doesn’t matter if you do it now or just rename the .zip file later, so do what you wish and hit enter.
Congratulations you have made your first ROM! You can now backup your current setup in CWM and flash it from your SD-Card, be sure to do a full wipe if it’s the first time and install it.
Note 1:
Sometimes you may get an error and CWM wont flash it, USUALLY this is because the kitchen has screwed up the updater-script but this doesn’t often happen. If it does take one from another ROM on the SAME DEVICE (<< IMPORTANT) and add it to your ROM.
Part 5. Further Mods and tweaks:
Resources:
Last one..
Well be the first one to reply this is amazing for a person like me who is in the learning process.
Mr.Oug said:
Well be the first one to reply this is amazing for a person like me who is in the learning process.
Click to expand...
Click to collapse
That's the idea
Sent from my Nexus S using xda premium
Awesome work! I'll be following this interesting thread. Thanks bro!
Sent from my GT-S5660 using XDA Premium App
Thank you very much. I've tried and passed from your guide and do I expect further intermediate and advance guide ?
Can't wait to start on this tonight.
I changed my ics lockscreen on my one with help from someone.
Now i finaly can learn to mod a rom on my own.
THX for the tutorial.
Time to learn more from my android
This tutorial worked like a charm.
Nice to see that everything worked and that i learned a lot from it.
Can wait to see how to mod it all.
Keep updating and i will follow the threats.
730000229 said:
Thank you very much. I've tried and passed from your guide and do I expect further intermediate and advance guide ?
Click to expand...
Click to collapse
Coming soon guys
Sent from my Nexus S using xda premium
A good tutorial for those with HTC devices, the tablets such as those from Samsung do not follow the file structure as before and will require a correct Edify definition file to create an update script that will work.
lorinkundert said:
A good tutorial for those with HTC devices, the tablets such as those from Samsung do not follow the file structure as before and will require a correct Edify definition file to create an update script that will work.
Click to expand...
Click to collapse
The kitchen should still sort it out. I've not had a Samsung tablet but its not going to be that different and if the updater isn't formatted properly compare it to a pre made ROM and see what's different
Sent from my Nexus S using xda premium
hi i have i9100G and i used the guide as written from top to bottm but for my i9100g it ask to change the framework.i tried the guide twice and both times i get stuck at the boot...
manishdev said:
hi i have i9100G and i used the guide as written from top to bottm but for my i9100g it ask to change the framework.i tried the guide twice and both times i get stuck at the boot...
Click to expand...
Click to collapse
What do you mean it asked to change the framework. More details mate. Make sure you have the right base ROM for your device
Sent from my Nexus S using xda premium
I'm definitely gonna try this out. Thanks for the instruction!
I want to follow this but i see no specifics on how to set up the kitchen on an Ubuntu machine, i purposely took one of my older dell latitude d420 and completely removed windows and installed the latest version of ubuntu, which is 11.10. would you please if possible, post some specifics on how to go about setting up the kitchen for an ubuntu machine, the faq links are pretty much windows specific. you said that using ubuntu would be much easier to go about this adventure, and i am dying to try it out, but im stuck, I know i have the java files and i have the android sdk all installed and stuff (or so i think). Any kind of enlightenment would be much appreciated,,,,,,,im refreshing this thread like every 2 minutes.....i really wanna dive into this
kevace1 said:
I want to follow this but i see no specifics on how to set up the kitchen on an Ubuntu machine, i purposely took one of my older dell latitude d420 and completely removed windows and installed the latest version of ubuntu, which is 11.10. would you please if possible, post some specifics on how to go about setting up the kitchen for an ubuntu machine, the faq links are pretty much windows specific. you said that using ubuntu would be much easier to go about this adventure, and i am dying to try it out, but im stuck, I know i have the java files and i have the android sdk all installed and stuff (or so i think). Any kind of enlightenment would be much appreciated,,,,,,,im refreshing this thread like every 2 minutes.....i really wanna dive into this
Click to expand...
Click to collapse
Just skip everything cywgin. Cywgin basically runs Linux commands on Windows
Sent from my ARCHOS 80G9 using xda premium
Everything will be heaps faster if you run it on ubuntu
Sent from my Nexus S using xda premium
so basically just do all comands written and just omit any refeernce to cywgin? when i extract the zip from the kitchen file, i get 3 folders and a "menu" file, and a readme text. what command do i have to use on terminal to start the kitchen?