Hello guys, i had requests to teach how-to cook successfully ROMs for the HTC Wizard, so i decided to start this thread and tell you guys how to cook using Video Tutorials
INDEX
POST#2 Basic Terms
POST#3 Basic Things
POST#4 Cooking using Cornelha’s Kitchen
POST#5 Cooking using CRBuilder
POST#6 Porting ROMs (Coming Soon...)
POST#7 Extras (OEM Packs, Ported SYS and XIPs, etc.) (Coming Soon)
NOTE: I would keep on editing this thread as i remember of more things.... Cooking is a large complicated process
Basic Terms:
Basic Terms:
Base ROM:
Base ROM is a ROM used as a base of your Cooked (Customized) ROM, or the ROM to which you’ll be making changes while cooking.
Cooking & Cook:
Cooking means preparing or building a ROM (i.e. adding software, changing registries and settings, changing images/graphics, etc.), and the one who does it is known as the cook.
Extended ROM (ExtROM):
Wizard has a ExtROM of about 10MB, this ROM can also be utilized while cooking but must be kept in mind it is also a read only mind, well it can be used to store *.CAB or other files, for use after ur Customized ROM has been flashed
OEM:
OEM (Original Equipment Manufacturer) is typically a company that uses a component made by a second company in its own product, or sells the product of the second company under its own brand. The specific meaning of the term varies in different contexts.
The OEMs used in ROM Kitchens are extracted form .CAB files. They are program files of software (i.e. .exe, .dll, .lnk, etc). They contain the information that where the files would be copied when a ROM is flashed and what are the registry keys of that software, some types of files you will find in OEMs are:
initflashfiles.txt – these files have the information that where the files are to be copied once the ROM has been flashed. They are not present in every OEM, but are in most of them.
*.rgu - these files have the registry keys of the OEM (Software), they must start with “REGEDIT4” and have a black line at the end, else they won’t work. They are not present in every OEM, but are in most of them.
*.dsm – just leave them, they aren’t of any use to us.
*.provxml - these files can do the work of both *.rgu and initflashfiles.txt files, they contain the information of files to be moved after flashing and registry keys to be enterd, but the diference between them and *.rgu and *.initflashfiles.txt is that .provxml files are executed when the ROM is ran first time, so they change any of the registry keys, applied by *.rgu files and remove/change any changes made by the initflashfiles.txt. They are not present in every OEM, but are in only some of them.
Program Files – these files are files of the software and are necessary to run it, these may include files of any of the following types e.g. .exe, .dll, .rar., .lnk, .brn, .swf, .html, etc.
Porting:
Porting means that, a ROM is designed for another device and you make it compatible for your device, so that it can run on your device, without any problems (except minor bugs caused during cooking).
ROM Kitchen:
ROM Kitchen is a kitchen used to cook ROMs for the Windows Mobile Device. They
are of different types by different cooks/programmers.
Basic Things:
Basic Things:
Creating a Shortcut (*.lnk file):
It’s very easy, create a New *.txt file. Open it in Notepad and write the following in it.
#”\source path\source file.exe”
And rename that file to *.lnk
EXAMPLE:
I have a file called ABC.lnk, it has the following written inside it:
#”\Windows\ABC.exe”
Editing Initflashfiles.txt:
This is very important file, when the Wizard gets a hard-rest or flashed it builds directory structures, copies files to (as example) the Program Files directory.
These are some examples from initflashfiles.txt:
Directory("\Program Files"):-Directory("ABC")
Directory("\Program Files\ABC"):-File("ABC.exe","\Windows\ABC.exe")
As you can see, not as tough as it looks, I am going to explain to you these two lines to tell you what do they mean.
-Directory("\Program Files"):-Directory("ABC")
(In this line “\Program Files” is the directory where a new directory "ABC")
-Directory("\Program Files\ABC"):-File("CBA.exe","\Windows\ABC.exe")
(In this line the file “ABC.exe” in the directory “\Windows” gets copied to directory “\Program Files\ABC” and gets renamed to “CBA.exe”
Very Easy, isn’t it?
So if u make a “initflashfiles.txt” file yourself or edit one, make sure that the last line of the files is empty.
Editing *.rgu files:
When editing *.rgu there are 4 things very important:
1. Turn off Word Wrap in Note Pad
2. On the first line should be REGEDIT4 and nothing else
3. The last line of the file should be blank
4. The files should be save in Unicode, not any other format.
The Windows Mobile Registry has 4 keys:
[HKEY_CLASSES_ROOT]
[HKEY_LOCAL_MACHINE]
[HKEY_CURRENT_USER]
[HKEY_USERS]
Make sure that every registry is in the *.rgu file or a *.provxml file else your respective program might not work!!
Making an OEM:
Making an OEM is easy, use this software to convert *.cab files into OEMs
Cooking using Cornelha’s Kitchen
Cooking using Cornelha’s KitchenHello, now I’ll show you how-to cook a Custom ROM for HTC Wizard using Cornelha's Kitchen. We’ll be using XIP and SYS from WM6.1 Build 20931(already ported for HTC Wizard). Please download this file.
1. Extract the “WM6.1 Build 20931 (cornelha's Kitchen).rar” file you downloaded and open the extracted folder.
2. Now you'll find here 4 folders of your use, OEM, Packages (sometimes needs to be manually created), ROM and SYS - OEM & Packages folders have the OEMs of the Software you want to add to your Cooked ROM, ROM folder has the XIP of your ROM and SYS has the basic Windows Mobile OS files.
3. Now let’s add OEMs to our Packages Folder, but b4 lets have a look in the OEM folder. The four folder you saw in the OEM folder are basic files/drivers needed for ever WM ROM to run, and can be used to cook any WM ROM.
4. Lets add OEMs to our Packages Folder.
5. Now go to the root of kitchen and run Kitchen.exe and go to Build OS tab and press on LOAD ROM button.
6. Under the title Packages to build into the ROM, check the apps you want in your ROM and uncheck those which you don’t want to.
7. Once done so, press “go” and wait...
8. The All packages into one option allows your ROM to be extraction protected, no one else can re-modify it after that
9. Now as it’s done, press the OK button in this newly opened window to convert the ROM into OS.nb file
10. Now as our OS.nb has been created to flash it we need it to be in nk.nbf format so let’s convert.
11. Go to Compile Tools folder and run the “Tools NK.nbf_wizard.exe” file.
12. Set language to WWE
13. In the first field select your OS.nb to be converted and in Image Name select OS and it’ll automatically fill in the text box on its left side.
14. Now you done, it’s time to flash let me show u how.
15. Cut/Copy the nk.nbf file to the TOOLs folder and then run the ROMUpdateUtility.exe and flash as you normally would
That’s it, your tutorials ends, you can enjoy cooking still if you have any problems, ask on the THREAD u found this video from and for more information on OEMs and etc search the thread
DOWNLOADS:
*Quick Start Kitchen: Download Link
It has:
1. Cornelha’s Kitchen
2. Ported XIP & SYS (WM6.1 Build 20931)
3. All setup and ready to use
*Video Tutorial: Download Link
NOTE: Sorry Guys! i forgot a file in the "Quick Start Kitchen" download the "touch.zip" file and extract the "touch.dll" file and copy it to OEM\OEMDrivers Folder (it is the driver of the Touch Screen )
Cooking using CRBuilder
1.Download the Quick Setup Kitchen from my thread and extract the .rar file and open the folder created.
2.Here only 3 folder are usefull to you, OEM, ROM & SYS - OEM folder has all the OEM packages of the softwares u want to add to ur Custom ROM, ROM folder has the XIP of the ROM ur going to cook and SYS folder has the basic files of ROM u'll be cooking
3.Lets have a look inside the OEM folder. These three folder starting with OEM are the basic folders and your ROM without them wont function correctly, they have drivers, base application, etc.
4.Now add all the OEMs of the softwares you want to cook into our ROM.
5.Now goto the root of the CRBuilder and run Build_ROM.bat amd wait until it compeletes. (See now its cooking so just wait
6.the OS.nb file has been created now its time to convert it into nk.nbf so press any key/Enter.
7.In language select WWE, check the File#1 checkbox then select the file and ImageName to OS click in the textbox next to it(on left) its value will be automatically entered
8.Press Translate.
9.As the nk.nbf file has been created, use it with any of the RUU u have, or download the RUU from the Thread u downloaded this video.
10.That's all, Enjoy!! Cooking
DOWNLOADS:
*Quick Start Kitchen: Download Link
It has:
1. CRBuilder Kitchen
2. Ported XIP & SYS (WM6.1 Build 21028)
3. All setup and ready to use
*Video Tutorial: Download Link
NOTE: Sorry Guys! i forgot a file in the "Quick Start Kitchen" download the "touch.zip" file and extract the "touch.dll" file and copy it to OEM\OEMDrivers Folder (it is the driver of the Touch Screen )
Empty Post 6
Extras (OEMs, Ported XIP & SYS)
Extras
XDA2'S OEM PACK
This OEM Pack contains the following programs and can be downloaded from here
Code:
Directory of XDA2'S OEM PACK
04/09/2009 07:40 AM <DIR> .
04/09/2009 07:40 AM <DIR> ..
03/13/2009 12:08 PM <DIR> Advanced_Configuration_Tool_v3
03/13/2009 12:03 PM <DIR> ArcSoft MMS 4
04/09/2009 07:40 AM <DIR> ASync Fix
03/13/2009 12:05 PM <DIR> ASyncFix_v2
03/13/2009 12:03 PM <DIR> BtCrawler
03/13/2009 12:10 PM <DIR> Calculator
03/13/2009 12:11 PM <DIR> Camera
03/13/2009 12:11 PM <DIR> camera+streamer
04/09/2009 07:36 AM <DIR> Commanager 2.0.8.0
03/13/2009 12:11 PM <DIR> Commanager 2.7.1.8
03/13/2009 12:06 PM <DIR> Contact Fixer 1
03/13/2009 12:08 PM <DIR> Cyberon - VoiceSpeedDial 1
03/13/2009 12:11 PM <DIR> Dialer - Opal PhoneCanvas
04/09/2009 07:36 AM <DIR> Diamond Vouge Dialer
04/09/2009 07:36 AM <DIR> Diamond WM skin By poorlyduck
04/09/2009 07:15 AM <DIR> dotFred Task Manager
03/12/2009 10:48 AM <DIR> EzInput Keyboards
03/13/2009 12:06 PM <DIR> File Explorer Extension
03/13/2009 12:11 PM <DIR> greatbal_M2D_grey_HTC_Opal_CommManager_2_7_1_8
04/09/2009 07:36 AM <DIR> HTC Calc Skin
04/09/2009 07:36 AM <DIR> HTC Camera
04/09/2009 07:36 AM <DIR> HTC Diamond CommManager 6 Button
04/09/2009 07:36 AM <DIR> HTC Diamond OutlookEnhancement 1.0.33540.3
04/09/2009 07:36 AM <DIR> HTC Diamond SmartTouch 1.0.31096.0
03/13/2009 12:09 PM <DIR> HTC Duo Album
04/09/2009 07:36 AM <DIR> HTC GIFAnimation
04/09/2009 07:15 AM <DIR> HTC Random Access_4_0_1009721_0
04/09/2009 07:36 AM <DIR> HTCAlbum
04/09/2009 07:36 AM <DIR> HTCAudioManager
03/13/2009 12:04 PM <DIR> HTC_Album
03/13/2009 12:11 PM <DIR> HTC_Album_2_0_1818_3829_4
03/13/2009 12:09 PM <DIR> HTC_Audio_Manager
04/09/2009 07:36 AM <DIR> HTC_Diamond_only_english
04/09/2009 07:36 AM <DIR> HTC_X Button 2_x
03/13/2009 12:04 PM <DIR> Keyboard Skin
03/13/2009 12:09 PM <DIR> Kin3tikSettings
SERVER ERROR: IT CORRUPTED MY LIST, SO DOWNLOAD TO SEE NOW
[CODE]
[SIZE=3][U][B] Cooking ROM in other Language:[/B][/U] [URL="http://rapidshare.com/files/280310930/Video_On_Demand.rar"]Link[/URL][/SIZE]
[B][I][SIZE=1][COLOR=Red]Note: This is an example how-to cook a dutch ROM, but other languages are cooked same like Dutch if u have the required files, i haven't included OEM_LANG_XXXX in the Packages, you have to search for it yourselves and place it OEM folder, its different for every device and language e.g for ENGLISH = OEM_LANG_0407, Have Fun![/COLOR][/SIZE][/I][/B]
[FONT=Verdana][SIZE=3][U][B] Editing a DLL:[/B][/U] [URL="http://rapidshare.com/files/283989157/DLL_Editing.rar"]Link[/URL][/SIZE][/FONT]
This is a tutorial to add something into the WM About, e.g "Provided by X2H", etc.
hi haseeb...
i am doing this what u describe ... and then lot question i will ask from u
salooo said:
hi haseeb...
i am doing this what u describe ... and then lot question i will ask from u
Click to expand...
Click to collapse
You can ask as much questions as much you want, if you want my cell no. you can PM
yupp..i need ur cell no...
and brother where i get master oem folder ..where there are lot of applications as shown in ur awsome video..
salooo said:
yupp..i need ur cell no...
and brother where i get master oem folder ..where there are lot of applications as shown in ur awsome video..
Click to expand...
Click to collapse
i'm uploading everything, but it'll take me some time
ok ..thanks buddy... u r much help full than all of the cookers...
salooo said:
ok ..thanks buddy... u r much help full than all of the cookers...
Click to expand...
Click to collapse
Maybe thts y you gave my ROMs a "one start" rating in my thread
ha ha ha ha.... actually i dont like the theme and ur 6.5 stucks in thretd sms mode..thats why ..but u gave themes pack now its 4 star
salooo said:
ha ha ha ha.... actually i dont like the theme and ur 6.5 stucks in thretd sms mode..thats why ..but u gave themes pack now its 4 star
Click to expand...
Click to collapse
Who uses threaded SMS mode?? i guess no body, ur the only one i have found using it i guess only 10% ppl might be using it
owwww ...thats why some times my wizard ... becomes slow while typing msges ..
so now again i am flashing ur rom..hehehe
one more question... my bateer drains fast as compare to normal.. is there any solution..and please give me your cell no
salooo said:
owwww ...thats why some times my wizard ... becomes slow while typing msges ..
so now again i am flashing ur rom..hehehe
Click to expand...
Click to collapse
Feel glad to hear that your flashing my ROM and Threaded SMS takes too much of RAM too i guess, i used it once and it screwed me after tht i have used the normal mode, its way better and faster
salooo said:
one more question... my bateer drains fast as compare to normal.. is there any solution..and please give me your cell no
Click to expand...
Click to collapse
So your battery drains fast... well there can be many reasons some of them are the following:
1.ROM u have flashed
2.Radio ROM ur using
3.Today plugins like TouchCommander, etc.
yayy thanks for this guide! I really need one but i don't know how to find OEMs and other stuff like language files..i hope you will help us
lapy said:
yayy thanks for this guide! I really need one but i don't know how to find OEMs and other stuff like language files..i hope you will help us
Click to expand...
Click to collapse
I posted a spcly made tutorial for you guys, didnt i? then y wuldnt i help u, further? and pl zbe patient im making a OEM pack for all of u a BIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIG ONE!!
UPDATE: Check the post#7 for OEMs and etc. i promised it and its there
Related
Hello Friends,
I have managed the new WM6 kitchen based on Ivan's new (17913.0.3.0) build. This is a clean vanilla kitchen, you can add your own flavor and the way you want it.
I've uploaded the kitchen to the following url and hope that you will like it.
http://www.siemens-bd.net/files/000000
Files have been splited into 10 parts (5MB each) because of my unstable internet connection here. Uploading a 50MB file for me is simply a nightmare! Please download all of them and unrar.
You will find two cmd files (1. BuildKitchen.cmd and 2. CreateROM.cmd) inside the ROM_DEV folder after the unrar.
Step-1: Run the BuildKitchen.cmd (first time only), it will dump the rom and prepare the kitchen for you.
[Additionally, you may use it to dump other WM6 rom and prepare the kitchen. In that case, decode the rom, copy (or overwrite) the nk.nba file to the ROM folder and run this cmd to build the kitchen.]
Step-2: Run the CreateROM.cmd to build the rom...as usual.
You will find a Ranju_OEM folder under the ROM_DEV folder. Some of the oem packages have been added if anyone is interested to use. Just copy your desired packages to the OEM folder and build the rom.
And finally, all credit goes to Ivan. Special thanx to Helmi, Midget, Bepe and Tuatara for their tools and support.
By the way, I've a limited bandwidth to this server, it will be great if someone mirror it somewhere.
Best regards,
Ranju
ranju said:
By the way, I've a limited bandwidth to this server, it will be great if someone mirror it somewhere.
Click to expand...
Click to collapse
Mirrored:
http://vidmes.com/Uni/Kitchens/ranju/ROM_DEV.rar
(btw My mirror has a Bandwidth limit of 3Tb per month...)
TehPenguin said:
Mirrored:
http://vidmes.com/Uni/Kitchens/ranju/ROM_DEV.rar
(btw My mirror has a Bandwidth limit of 3Tb per month...)
Click to expand...
Click to collapse
Hi TehPenguin, thank you very much.
Thanks to ranju and thanks to tehpenguin!
ranju said:
I have managed the new WM6 kitchen based on Ivan's new (17913.0.3.0) build. This is a clean vanilla kitchen, you can add your own flavor and the way you want it.
Click to expand...
Click to collapse
Thx for the new kitchen. Based on V3, correct?
Could you please clarify the 1st post?
Clean Vanilla: What did you remove from the ROM?
Cheers
Download
Extract
BuildKitchen
CreateRom
BuildOS stops on error: the file 'temp\dump\Thumbs.db' already exists
I've just checked the OEM folder.
Very good Job: just like i was thinking. Probably I don't need any other apps for OEM.
THX!!!
tailazoom said:
Download
Extract
BuildKitchen
CreateRom
BuildOS stops on error: the file 'temp\dump\Thumbs.db' already exists
Click to expand...
Click to collapse
Did you modify any cmd file?
If not, then delete the temp folder. Do a search on SYS & OEM for "Thumbs.db" and delete them if found any. Run the CreateROM.cmd.
I suppose "Thumbs.db" have been created by your picture browser apps.
"Thumbs.db" is a file that Windows XP (and Vista) create if you preview a picture or movie. Its not important at all (although Windows will complain that it is a "System File")
(Nifty fact: Windows XP can create the "thumbs.db" file in a read-only network share!)
Thanks for the info, i'll try deleting and recompile.
Deleted, compiled and flashed: every essential function i tested is working. The kitchen is very clean! Many thanks ranju!
Little update of the kitchen
This is a little update of the kitchen:
* Due to the slow response of the phone, dialing/ending tone have been removed
* Update for HTC Task Manager 1.5 (Exclusive apps can be added now)
Please download the zip and copy/replace to the associated folder.
Update: HTC Task Manager cab attached.
http://forum.xda-developers.com/attachment.php?attachmentid=40327&d=1180503183
ranju said:
This is a little update of the kitchen:
* Due to the slow response of the phone, dialing/ending tone have been removed
* Update for HTC Task Manager 1.5 (Exclusive apps can be added now)
Please download the zip and copy/replace to the associated folder.
Click to expand...
Click to collapse
Can you please make a cab of it so that we can install. Dont want to go through re in stalling rom. Appreciate
Or if you can advice the registry entries for both above issues please.
Phone.cab
A cab file for the file in phone.zip is not that difficult since it's just a couple of registry entries.
The other one is more difficult since it also includes files.
So just to help a little, a cab file for the registry stuff in the phone.zip
Actually not that difficult
When comparing the old and new files, I noticed that just the RGU file is different.
Since this is the file with registry settings, I made a quick cab for it.
So not to replace the previous HTC Manager install or anything like that, just to corrent the registry entries.
ps. This and the previous file are not made/reviewed/anything by Ranju, but I've just given them him (her?) name to avoid confusion.
aniel1 said:
Can you please make a cab of it so that we can install. Dont want to go through re in stalling rom. Appreciate
Or if you can advice the registry entries for both above issues please.
Click to expand...
Click to collapse
[HKEY_CURRENT_USER\ControlPanel\Sounds\Dialing]
"Sound"="dpadctl.mid"
"Script"="p"
"Category"="InCallFeedback"
[HKEY_CURRENT_USER\ControlPanel\Sounds\Ending]
"Sound"="dpadctl.mid"
"Script"="p"
"Category"="InCallFeedback"
[HKEY_CURRENT_USER\ControlPanel\Sounds\DialPadCtlKey]
"Sound"="dpadctl.mid"
"Script"="p"
"Category"="InCallFeedback"
Remove the line in bold above ("Sound"="dpadctl.mid") in the registry and it should like this:
[HKEY_CURRENT_USER\ControlPanel\Sounds\Dialing]
"Script"="p"
"Category"="InCallFeedback"
Set the value of "Script" to "apr" and it should like this. It will remove 3s ring delay.
[HKEY_CURRENT_USER\ControlPanel\Sounds\RingTone0]
"Script"="apr"
Press the power button (off) after the changes and wait for 10 sec, switch on again and soft reset your device to take the changes in action...
GerardNL said:
When comparing the old and new files, I noticed that just the RGU file is different.
Since this is the file with registry settings, I made a quick cab for it.
So not to replace the previous HTC Manager install or anything like that, just to corrent the registry entries.
ps. This and the previous file are not made/reviewed/anything by Ranju, but I've just given them him (her?) name to avoid confusion.
Click to expand...
Click to collapse
I tried but looks like the cab does not stick the enteries in the registry.Can you give me the registry entries so that i can try to insert them manually. thank you
ranju said:
[HKEY_CURRENT_USER\ControlPanel\Sounds\Dialing]
"Sound"="dpadctl.mid"
"Script"="p"
"Category"="InCallFeedback"
[HKEY_CURRENT_USER\ControlPanel\Sounds\Ending]
"Sound"="dpadctl.mid"
"Script"="p"
"Category"="InCallFeedback"
[HKEY_CURRENT_USER\ControlPanel\Sounds\DialPadCtlKey]
"Sound"="dpadctl.mid"
"Script"="p"
"Category"="InCallFeedback"
Remove the line in bold above ("Sound"="dpadctl.mid") in the registry and it should like this:
[HKEY_CURRENT_USER\ControlPanel\Sounds\Dialing]
"Script"="p"
"Category"="InCallFeedback"
Set the value of "Script" to "apr" and it should like this. It will remove 3s ring delay.
[HKEY_CURRENT_USER\ControlPanel\Sounds\RingTone0]
"Script"="apr"
Press the power button (off) after the changes and wait for 10 sec, switch on again and soft reset your device to take the changes in action...
Click to expand...
Click to collapse
thank you ranju. CAn you provide the registry entry for tak manager too, somehow the cab posted above doesnot stick in the registry and i still dont see exclusive/activate please
Third day of use (calls with bt headset/sms/excel) without any problem. Thanks again ranju!
ranju said:
.....
Remove the line in bold above ("Sound"="dpadctl.mid") in the registry and it should like this:
....
Click to expand...
Click to collapse
Mmmm. Removing items from the registry.... Didn't think about that one. So that means that the 2 cabinet files I made will not work.
Back to the drawingboard...
Build my first Rom
I've this ROM kitchen few days back from one of my friends and was simply amazed when I build my first rom.
This is as easy!
Thanks ranju, keep up good work!
Hi guys,
I wanted to start cooking my own ROM and was wondering which kitchens are available that i can use. The only ones i know of are:
1) Hypercore kitchen by anichillus (http://forum.xda-developers.com/showthread.php?t=324682)
2) Beasty and Leo's Kitchen (only saw the snapshot in one of their posts, dont know where i can get it from)
What other options do i have when it comes to ROM Kitchens? And what exactly are the pro's and con's associated with each of the kitchens you mention!
A quick reference to some tutorials and how-to's would be awesome too I've already got some reading material but, the more the better!
I'd really appreciate any help i can get.
Thanks!!!
really, noone?!?
thingonaspring is offering a kitchen from his 3.2 rom, he added a cooking tutorial.
http://forum.xda-developers.com/showthread.php?t=332737
best kithen its kithen which you create by yourself .and for your own... mine for example
2 bat files ... pack and unpack
unpack
1. extracts nbf file
2. extracts nb file content
3. creates packages ...
4. extracts xip.bin and xip contents to folders near sys and oem
5.. system metafiles ( old reg ... initflash files .. and others ) place near sys as meta folder
6. all rgu files from packages hey copy near sys and oem folder as reg folder .. with mark of priority while assembling
after all
sys folder
oem folder
xip folder
xip extended folder with xip.bin and other xip related extracted stuff
reg folder with rgus
meta folder
pack.bat
1. promt .. what rgus use for assembling .. placed in packages or placed in reg folder
2. creating dump folder
3. calculate rom space .. if they exeed standart process brakes
4. injecting xip_out.bin in nb file
5. creating nb.new file
6. assembling nbf file
quadxeon said:
thingonaspring is offering a kitchen from his 3.2 rom, he added a cooking tutorial.
http://forum.xda-developers.com/showthread.php?t=332737
Click to expand...
Click to collapse
I've downloaded thingonaspring's kitchen. Will look into it as soon as i get free from work!
mo3ulla said:
best kithen its kithen which you create by yourself .and for your own... mine for example
2 bat files ... pack and unpack
unpack
1. extracts nbf file
2. extracts nb file content
3. creates packages ...
4. extracts xip.bin and xip contents to folders near sys and oem
5.. system metafiles ( old reg ... initflash files .. and others ) place near sys as meta folder
6. all rgu files from packages hey copy near sys and oem folder as reg folder .. with mark of priority while assembling
after all
sys folder
oem folder
xip folder
xip extended folder with xip.bin and other xip related extracted stuff
reg folder with rgus
meta folder
pack.bat
1. promt .. what rgus use for assembling .. placed in packages or placed in reg folder
2. creating dump folder
3. calculate rom space .. if they exeed standart process brakes
4. injecting xip_out.bin in nb file
5. creating nb.new file
6. assembling nbf file
Click to expand...
Click to collapse
Do your Pack.bat and Unpack.bat files work for ANY NBF files or only for the kitchen you use?? If they work for all NBF files, is there any chance you could provide me with those batch files?
1. any nbf file placed in source folder may be unppacked
2. its not only bat files .. primary its a complex of unreleased progs
3.. no chance .. becose this kithen i made with cooperation with 1 mad programer .. who not like freeware licence
mo3ulla said:
1. any nbf file placed in source folder may be unppacked
2. its not only bat files .. primary its a complex of unreleased progs
3.. no chance .. becose this kithen i made with cooperation with 1 mad programer .. who not like freeware licence
Click to expand...
Click to collapse
perfectly understandable ... any chance you could help me build my own kitchen? i've got over 6 years of programming experience in over a dozen languages. you'll just have to provide me with guidelines. possible??
SYS PORTING GUIDE
Special thanks goes to Monsterfly for helpful guidance on porting SYS to a new build
Inventory:
Tools you will need for porting the SYS
BuildOS+Package Tool by Ervius
G’Reloc Tool by Misar
Procedure:
Use BuildOS+Package tool to dump ORIGINAL ROM and build packages
Copy G'Reloc to the folder where you have original SYS folder
Run it and write down numbers under slot 0, slot 1 and size of rom
Use BuildOS+Package tool again to dump DONOR ROM and build packages
Replace your original SYS folder with Donor's SYS
Run G'Reloc again
Notice that this time numbers under slot 0, slot 1 and size of rom may be different
Just replace them with numbers you got in the firt step
Click »Doit!« and wait till it shows "Done" in the status bar
Use the OEM folder in which you have added ingredients and the XIP fodler that you ported
Info: In some cases you will need to copy WinCENLS_WWE folder to SYS folder (if not present in Donor's SYS) from your original ElfIn SYS otherwise your device will not boot
Build OS in the kitchen of your choice and flash the new build ROM to your device and HAPPY COOKING
Timebomb solution and the boxed closed / ok button solution found here by HTCTouchp
[POLL][REF]*XIP & SYS Porting Guide*[ONLINE]
XIP Porting Guide (Based on Bepe's Buildxip.exe tool)
More detailed Porting guide on manual XIP Porting can be found here
I have added pictorials in .pdf format at the end of this post. Too many pictures so the .pdf file
Special thanks goes to Ervius for a lot of helpful guidance on porting XIP to a new build
Inventory:
Tools you will need for porting the XIP
BuildOS+Package Tool by Ervius
XIPPort Tool by Bepe
M’Reloc Tool by Misar
Procedure:
To make life more simple, I am attaching the XIP.bin extracted from Kaiser 19209 build ROM by Ervius. Dump the XIP.bin file with XIPPort tool and choose to make packages. Download from here (Rapidshare Folder)
In the OUT folder, ignore or delete all the text files (.txt) These files are created by XIPPort tool only to know the physical addresses and are not required for porting
In files and modules folders, delete all folders except “MSXIPKernel” and “MSXIPKernelTLK” The modules and files from these folders are the only items which are to be ported to make a new build. DO NOT copy or replace any files and modules from OEMXIPKernel, as these are device specific
Now open the BuildOS+Package tool and on packaging page click open with option to choose dump folder. Select your original ElfIn XIP folder (OS 19199) and on right you will see the XIP in its directory structure. Don’t click on build packages (you can’t do it anyways, as package.sof file is not present in the XIP folder) Instead click on “OEMXIPKernel” and then right click to select export package. Choose to save on different location, like your desktop. This is only temporary requirement, just to be on safe side that you still don’t replace any files or modules seen in that folder
Now you copy and replace the files and modules seen in the “MSXIPKernel” and “MSXIPKernelTLK” from the new XIP in your original XIP folder, you need to copy and replace only those items found in your original folders, do not add anything new. Now compare each and every .rgu file from your new XIP with your original XIP and check if they are similar (NOT the .rgu files in “OEMXIPKernel”)
After all the files and modules are replaced and .rgu files checked, run the M’Reloc tool and check the modules addresses from your original XIP with your new XIP (Don’t do anything to the modules located in “OEMXIPKernel”) The addresses have to be similar to your original modules from your original “MSXIPKernel” and “MSXIPKernelTLK” folders
Changing of addresses through M’Reloc is not required if you are using the BuildOS+Package tool for cooking ROMs as Ervius has already included the address relocation system into his tool with BuildXIP
In a nutshell you need to follow the following copying & replacement structure and everything will work:
Original XIP (19199): OEMXIPKernel
Donor XIP (19209): MSXIPKernel and MSXIPKernelTLK
Replace this new XIP folder in ROM in Bepe's WM6.1 Elfin kitchen and cook to get 19209 Build XIP, HAPPY COOKING
I have managed to put together a clean Base WM6.1 ROM for Elfin (Touch XL - 128/256) with almost everything removed except the most essential system packages
Please take note, this is a base rom for cooking and not to be directly flashed on the device as it may be unusable. You need to populate the ROM with your choice of packages and the essentials to bring it up to the 50MB limit for making it usable
Link to download the dumped Removed packages: Here
Special thanks to
Bepe for his wonderful kitchen
Noonski for his valuable comments and suggestion all the way
Kokotas for his help in getting rid of the cube
Download Bepe's WM6.1 Kitchen for ElfIn and replace the OEM and SYS folders with yours and cook the OS.nb file
The archived OEM package (dumped and packaged) can be downloaded here
DOWNLOAD HERE (V1)
UPDATE
DOWNLOAD HERE (V2) (Further stripped down OEMApps & OEM_Lang_0409)
20296 MSXIPKERNEL. Mix this with OEMXIPKERNEL and you are ready to cook. Do M'relocing if necessary
Download here: View attachment 108115
SYS archieve
A. The archived SYS package 19199 buid. DOWNLOAD HERE
Stripped to down basic required
B. SYS ported from 19209 Build. DOWNLOAD HERE (Rapidshare Folder) This archieve is from my new ROM (XIP and SYS Ported to new build) Removed packages as per above ist
C. 19588 Build ROM Dump (OEM, SYS & XIP) DOWNLOAD HERE. Thanks to Koko for sharing this archieve (SYS, OEM & XIP)
Hi Abrabekar,
You really came in the right time! I'm about to remove all the unnecessary apps inside Elfin original ROM and now you came with WM6.1
You really save my time, many thanks to you!
Cheers,
Vibranze
Deleted! Double post.
well im just waiting for another version wm6.1 ROM for elfin~at least after swiftblade and couldyfa's~ any updated wm6.1 ROM for elfin is welcome! `cheers~
JohnQ said:
well im just waiting for another version wm6.1 ROM for elfin~at least after swiftblade and couldyfa's~ any updated wm6.1 ROM for elfin is welcome! `cheers~
Click to expand...
Click to collapse
@JohnQ.. this is not an upgrade to swiftblade's or cloudyfa's wonderful roms but just a clean base rom for everyone to cook have more personalised options
Hi Ababrekar,
Yeah, but how I supposed to populate the SYS and OEM folder? Or to be precised, how should I continue from your OS.nb file?
Cheers,
Vibranze
ababrekar said:
@JohnQ.. this is not an upgrade to swiftblade's or cloudyfa's wonderful roms but just a clean base rom for everyone to cook have more personalised options
Click to expand...
Click to collapse
vibranze said:
Hi Ababrekar,
Yeah, but how I supposed to populate the SYS and OEM folder? Or to be precised, how should I continue from your OS.nb file?
Cheers,
Vibranze
Click to expand...
Click to collapse
you need to populate the rom by adding your choice of packages. the essentials out the removed list would be phone dialer, commanager, bluetooth, netcf, audio manager. also you need to add files so the final cooked os.nb file is above 50mb limit
Don't Mind Vibranze he allready is running his own Rom...
Noonski said:
Don't Mind Vibranze he allready is running his own Rom...
Click to expand...
Click to collapse
i was answering his questions coz no question should go unanswered in my thread
I think it would be a good idea to post which kitchen you advice to cook the nb in.
I was wondering if there is a WM 6.1 Rom with nothing extra added. Just like an original HTC ROM? Like with no accessories folder, or HTC Action screen etc. I really don't like any of that stuff. I really only wanted WM 6.1 for the threaded sms.
Thanks in advance
canadian student said:
I was wondering if there is a WM 6.1 Rom with nothing extra added. Just like an original HTC ROM? Like with no accessories folder, or HTC Action screen etc. I really don't like any of that stuff. I really only wanted WM 6.1 for the threaded sms.
Thanks in advance
Click to expand...
Click to collapse
as i said, this is a bare naked base rom with all the packages removed for maximum user customisation. the packages removed are listed in my first post here
Noonski said:
I think it would be a good idea to post which kitchen you advice to cook the nb in.
Click to expand...
Click to collapse
good suggestion, like always brother i have updated the first post at the last line guiding to bepe's kitchen for cooking the nb file
(although i need bepe's or your guidance on how to get the exact same contents of his ROM folder from my ROM which can help everyone in achieving more customisation)
Well i've been working a month on SuperCore now but it now contains Packages for almost everything you have removed.
Looked up most of the registry settings for removed items to.
Generated new .dsm files and made option.xml for each.
And i still need to make registry keys to make removed controlpanel items work from SD.
So now i can wait another month before uploading new SuperProCore.
Now if somone could tell me how to make a os.nb.payload for ELF only with 4MB pp poeple would really be happy.
Noonski said:
Well i've been working a month on SuperCore now but it now contains Packages for almost everything you have removed.
Looked up most of the registry settings for removed items to.
Generated new .dsm files and made option.xml for each.
And i still need to make registry keys to make removed controlpanel items work from SD.
So now i can wait another month before uploading new SuperProCore.
Now if somone could tell me how to make a os.nb.payload for ELF only with 4MB pp poeple would really be happy.
Click to expand...
Click to collapse
even i'm looking for a way to get the exact contents of ROM folder what Bepe has in his kitchen for ElfIn. It contains XIP with a lot of other files. I wonder if having the os.nb.payload from my own rom would help rather than using bepe's file still waiting for a guidance
i am attaching the default.hv & user.hv files with the reg entries deleted as per the removed packages list. see if you can check and comment on it, it will be great
eagerly waiting for SuProCore
Most of the keys are double ussually.
So you'll find the same keys also in SYS and OEm .rgu files as in hives files.
Noonski said:
Most of the keys are double ussually.
So you'll find the same keys also in SYS and OEm .rgu files as in hives files.
Click to expand...
Click to collapse
oh ok. so to completely remove the removed package list from the rom, i will have to also edit the .rgu files found in oem & sys?
ababrekar said:
oh ok. so to completely remove the removed package list from the rom, i will have to also edit the .rgu files found in oem & sys?
Click to expand...
Click to collapse
Naah you really don't need to.
Those left behind registry settings ussually don't do any harm without the files present.
Obligatory Warning Label:
Use this at your own RISK. I cannot be held liable for any damage caused to your device by your own mistakes or by my mistakes in the instructions.
How to port a XIP:
Extract xip.bin from the build you want to port from
Download Bepe's XIPPort
Extract XIPPort to any folder
The folder should contain XIPPort.exe, pkgcommon.dll, and xip.bin you want to port.
Run XIPProt.exe
Press "Dump xip.bin" - This will create an OUT folder
Press "Make Pkgs"
Open the OUT folder and you will find two folders: Files and Modules
Copy the contents of MSXIPKernel and MSXIPKernelLTK with each folder (Files and Modules) and paste them to /ROM/XIP folder and replace. (Note: Don't worry about copying the .txt files, they are not needed.)
Source
How to port a SYS folder
Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell
Source
Q&A
Q: What is the XIP?
A: It's the kernel of the ROM.
Q: What is the SYS folder?
A: It's where all the new apps included in each Windows Mobile release are stored.
Q: I did all this and I bricked my phone, help!!!
A: First, rest assured. Your phone is not bricked. See THIS thread on how to unbrick your phone. Secondly, refer to Q&A #4.
Q: This is too complicated... but I still want to port my own ROM. What should I do?
A: Easy. Use my EasyPortOven and the process will be automated.
Q: Where do I get the latest SYS folders? XIP's?
A: I don't know... Your guess is as good as mine. I just download Kaiser ROM's that have them since they tend to have the latest and greatest first. Do NOT PM me asking me where to find them.
well done ,thanks.
ivan i love you...lol just kidding silly goose but thanks a million
Ivan:
Can XIP or SYS folders be ported over different language ROMS?
Say... I have my spanish HTC WM6 ROM, can I port an english WM6.1 over it to obtain an unofficial spanish WM6.1?
I assume the XIP folder could be ported but porting the SYS folder would end with a spanish ROM and multiple applications in WWE (without even starting to think about localization codes troubles)
Thanks.
le_hades said:
Ivan:
Can XIP or SYS folders be ported over different language ROMS?
Say... I have my spanish HTC WM6 ROM, can I port an english WM6.1 over it to obtain an unofficial spanish WM6.1?
I assume the XIP folder could be ported but porting the SYS folder would end with a spanish ROM and multiple applications in WWE (without even starting to think about localization codes troubles)
Thanks.
Click to expand...
Click to collapse
You'd have to go through every file in the OEM folder and find every misdirected link (because of the different language) as well as replace every MUI. So in short, no it's not possible unless you have a LOT of time and want to work really hard. What I would do is just use any of the readily available Spanish Herald ROMs to obtain your OEM files.
mm this is a "fast" and dirty way:
If you use in.ex a 19199 build (0409 wwe)
you need to extract all mui files from 04xx (your langauge from another build, if you use wm6.1 you need to use mui from another wm6.1 build)
rename them from 04xx to 0409, replace all in you 19199 build with the new renamed ones
this can be done both in OEM and SYS
The thing is that i'd like to make a herald spanish 6.1 ROM but I can't find none to port on kaiser forums etc, so i was thinkong about alternatives
ivanmmj said:
Obligatory Warning Label:
Use this at your own RISK. I cannot be held liable for any damage caused to your device by your own mistakes or by my mistakes in the instructions.
How to port a XIP:
Extract xip.bin from the build you want to port from
Download Bepe's XIPPort
Extract XIPPort to any folder
The folder should contain XIPPort.exe, pkgcommon.dll, and xip.bin you want to port.
Run XIPProt.exe
Press "Dump xip.bin" - This will create an OUT folder
Press "Make Pkgs"
Open the OUT folder and you will find two folders: Files and Modules
Copy the contents of MSXIPKernel and MSXIPKernelLTK with each folder (Files and Modules) and paste them to /ROM/XIP folder and replace. (Note: Don't worry about copying the .txt files, they are not needed.)
Source
How to port a SYS folder
Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell
Source
Q&A
Q: What is the XIP?
A: It's the kernel of the ROM.
Q: What is the SYS folder?
A: It's where all the new apps included in each Windows Mobile release are stored.
Q: I did all this and I bricked my phone, help!!!
A: First, rest assured. Your phone is not bricked. See THIS thread on how to unbrick your phone. Secondly, refer to Q&A #4.
Q: This is too complicated... but I still want to port my own ROM. What should I do?
A: Easy. Use my EasyPortOven and the process will be automated.
Q: Where do I get the latest SYS folders? XIP's?
A: I don't know... Your guess is as good as mine. I just download Kaiser ROM's that have them since they tend to have the latest and greatest first. Do NOT PM me asking me where to find them.
Click to expand...
Click to collapse
Great job bro,
ivan you rock!!
I learn so much from reading your threads.
I think im almost ready to cook a rom.
I was wondering if you could be my mentor??
It works and works very well, however, I have ported from Hermes XIP CE OS 19949 & build 19949.1.1.1
to Atom from orginal XIP and I have CE OS 5.2.1921 & build 19949.1.1.1 (WM6.1) how to gain CE of 19949? thank you very much for sharing.
homer285 said:
It works and works very well, however, I have ported from Hermes XIP CE OS 19949 & build 19949.1.1.1
to Atom from orginal XIP and I have CE OS 1921 & build 19949.1.1.1 (WM6.1) how to gain CE of 19949? thank you very much for sharing.
Click to expand...
Click to collapse
You ported the XIP AND the SYS folder?
Thanks for your reply, yes I did.
homer285 said:
Thanks for your reply, yes I did.
Click to expand...
Click to collapse
Are you using the imgfs.bin/os.nb from the Atom? The only time I've seen that is when you're using the imgfs.bin/os.nb from another device. It "lines up" enough for the ROM to work but somethings like the version numbers don't "line up." I'd need more information to find out what happened. Also, did you change the DPI of the ROM for any reason? or the DPI files?
ivanmmj said:
Are you using the imgfs.bin/os.nb from the Atom? The only time I've seen that is when you're using the imgfs.bin/os.nb from another device. It "lines up" enough for the ROM to work but somethings like the version numbers don't "line up." I'd need more information to find out what happened. Also, did you change the DPI of the ROM for any reason? or the DPI files?
Click to expand...
Click to collapse
yes Im using the Diskimage_Ver.nb0 from Atom in Rom folder, tried by hand and EasyPortOven same result, only build is porting not CE OS info. Perhaps I need a new XIP to try, anyway thanks for this great tool it really makes porting easy, seriously.
Edit: So the trick for me was the Atom needed porting directly, all modules must have address changed and then ported to diskimage_Ver via XIPPORT, drop into Kitchen/ROM folder along with everything mentioned here .
can anyone confirm if this works for the kaiser, and if it doesn't, what to use for the kaiser?
thanks in advance
I've heard that Keeping your original Device MetaData hive files isn't that important as the Hive Files get created.
But just to be on the Sure side.
When you put the Hive files from MetaData folder into the New Build from the Ported Sys.
Won't that make hive files with unneeded Reg entries?
instead of sticking with your original device Hive Files?
€dit: Wrong thread, sorry!
Drivers?
What about the drivers and files specific to the device?
Is it included in the .VM folder? Is it not necessary to copy the .ROM folder too?
So, in essence, I have to just copy the folders you have specified to the new SYS and XIP folders and use BuildOS. To cook a light and clean ROM, only these two folders are enough, right?
BTW, what is the OEM folder for? In the kitchens, I have used, they contain a few folders like OEMAPPS, OEMDRIVERS, etc, which in some kitchens are placed in the SYS folder instead.
I don't know where to place those folders. Is the location of those folders irrelevant? I am kinda noob to cooking. I've played with it a lot of times with mixed results. I am building it for Tornado btw.
rajathvsm said:
What about the drivers and files specific to the device?
Is it included in the .VM folder? Is it not necessary to copy the .ROM folder too?
So, in essence, I have to just copy the folders you have specified to the new SYS and XIP folders and use BuildOS. To cook a light and clean ROM, only these two folders are enough, right?
BTW, what is the OEM folder for? In the kitchens, I have used, they contain a few folders like OEMAPPS, OEMDRIVERS, etc, which in some kitchens are placed in the SYS folder instead.
I don't know where to place those folders. Is the location of those folders irrelevant? I am kinda noob to cooking. I've played with it a lot of times with mixed results. I am building it for Tornado btw.
Click to expand...
Click to collapse
Things have changed a lot since I wrote this... but:
The drivers are in the OEM folder (as well as most of the device specific stuff.)
You need the OEM, SYS and XIP in order to make ANY ROM.
You can move your OEM into your SYS but it makes it harder to port newer builds to your ROM later on.
You only need the .VM folder, not the .ROM folder. The kitchen will autoadjust itself.
Yep its been a long time... but is useful on old kitchens
I gues i have an hybrid
cause the process i use is like EXT packages + OEM packages + SYS + XIP
Something about a platform rebuilder + oldschool buildOS hahaha
Maybe you can help me Ivan using your process to port the xip i DID it! it works the sys too but....
I port the SYS from xbeta.cn hermes WWE, changing the .VM and shellres you know... and the xip usin xipport everything goes fine I port the Xip from Kaiser... but
But now everything i install says certificates untrested... i instal sdkcerts and nothing happends
do you think i port the sys or xip wrong?
thanks in advance I dont have an Herald, I had an hermes... but i think the process is the same...
wm6.5 build 21812
This is a release for my ROM porting kitchen. It ports both XIP's and SYS folders [currently for the herald/atlas/wing and Wizard only].
http://www.darthnet40.com/xda/ivanmmj/Kitchens/
It is compatible with Bepe's extended kitchen, but I don't believe he ever released one for the Wizard. It requires a ROM folder with an extracted XIP folder within it. Just download the Herald's and you'll see what I mean. Hopefully someone will make something like it for your devices. The Wizard part is untested, as I no longer have a wizard.
Normally, I'd say:
Place bepe's kitchen in the Working_Folder (so that OEM/SYS/ROM and other folders are right within Working_Folder.) Alternatively, you can place also place all the files into EasyBakeOven's folder. Allow the Working_Folder to override EasyBakeOven's Working_Folder. You will not loose any data.
Place the SYS file you wish to port into Working_Folder (and delete your old SYS folder.) Place your xip.bin that you wish to port into the Prepare folder.
Obligatory Warning Label:
Use this at your own RISK. I cannot be held liable for any damage caused to your device by your own mistakes or by my mistakes in the instructions.
If you wish to know how to do this manually, head over to my HowTo thread.
Thanks go to:
ababrekar for the elfin files
l3v5y and xvx45 for the Prophet files
character and ginminded for the wizard files
bepe for his wonderful kitchen and for the herald files taken from his kitchen
Coming soon: V2.1
Added support for:
Elfin/elf
Prophet
DUDE! I downloaded your "Just Clean kitchen" and have been using the **** out of it! thanx for that post and for this one!