Database Develop

initflashfiles.dat -- Help Needed

So I've been playing around for a little while with the intention of creating my own custom ROM. I think I've got everything all figured out - however I'm having a problem that I think is related to the initflashfiles.dat file. Basically, after flashing my new OS ROM, my 8125 hangs at the splash screen with the version numbers on it. As a test, I redid my modified ROM, except I used the original initflashfiles.dat - this worked just fine. Tried it again by building the ROM with my modified initflashfiles.dat - same problem.
Here are the steps I'm going through.
1. Parse out the nk.nbf file using typhoonnbfdecode -x
2. prepare_imgfs 80040000-OS.nb -nosplit
3. viewimgfs imgfs_raw_data.bin
4. Modify contents of dump directory. Basically I've deleted files I don't need and added new ones.
5. Modifiy initflashfiles.dat (which I've attached). After modifying the file I open it in a hex editor and remove the first two bytes - making the first byte 3B (";"). I save it and mark it as read-only.
6. buildimgfs
7. make_imgfs 80040000-OS.nb -nosplit
8. Run nb2nbf_tornado.exe. I do run this correctly, using the correct memory address for the OS .nb file.
9. Put the new nk.nbf into an existing RUU self-extracting archive and run it.
It really seems like it's the initflashfiles.dat file - as I've successfully loaded this ROM with the original file (its really not the original, it's from a summiter ROM that I'm basing mine off).
Any thoughts?

I'm going to bump this once just in case people missed it originally.
I've messed around a bit more, and have pretty much isolated that this is my problem - but for the life of me I can't figure out what I'm doing wrong.

CameronJ said:
I'm going to bump this once just in case people missed it originally.
I've messed around a bit more, and have pretty much isolated that this is my problem - but for the life of me I can't figure out what I'm doing wrong.
Click to expand...
Click to collapse
Hi,
i see that the file you've attached isn't actually a .DAT file. It is a .dat.TXT that's the same that saying it's a TXT file!!!
If the file you're putting inside your ROM is this very same file (.dat.txt) then you've found your problem: you need a .DAT and NOT a .dat.txt file!!!
Try following this procedure on your PC (i suppose you're using XP or 2003 server):
- open a folder (whichever folder you like, it's not important)
- on the Tools menu click Folder Options.
- click the View tab.
- clear the Hide extensions for known file types check box.
- press OK
PS: Here is an illustrated guide on how to show file extensions
Now go to the place where your initflashfiles.dat is. If the file is named 'initflashfiles.dat.TXT' (like the file you uploaded in this forum) then:
- select the file
- press F2 (or right click and choose 'Rename')
- remove the tailing .txt from the name
Finally:
- let us know if it worked
Bye bye

risidoro said:
i see that the file you've attached isn't actually a .DAT file. It is a .dat.TXT that's the same that saying it's a TXT file!!!
Click to expand...
Click to collapse
:lol: Thanks for the reply.
I had to add the .txt extension otherwise the forum wouldn't let me upload the file (.dat files are not on the list of available file types for upload).
When I loaded the file I meant to put that explanation in there but forgot before I finished the post.

Hi. I don't know if you're still working on this, but I'd like to share with you my experience last night. I examined your initflashfiles.dat, and it is perfectly ok.
As I see in your initflashfiles.dat, there are a lot of folder customization like:
Directory("\Program Files\Task Manager"):-File("taskmanager.exe","\Windows\taskmanager.exe")
There is nothing wrong with this as we need the file to be in the right location. BTW, THIS FORMAT WORKED FOR ME. Just a thought, you might be editing the default.hv and user.hv (hives) to put in the registry keys of some applications?
My device (Himalaya) did not start out correctly and did not execute the initflashfiles.dat, BUT when I connected my Hima through active sync, you can actually explore the contents. SO, in this non-working state, I experimented in tracing the culprit, by restoring a couple of the original files I edited. I found out that it has something to do with the way I edited the hives.
Steps I made in experimenting:
1. I sync my Hima to my PC.
2. Copied the original default.hv to \windows directory
3. Hard Reset Hima, BUT answer NO to all three boot options
4. My Hima started normally and executed initflashfiles.dat to the detail.
Discovery from experiment:
1. The files were only copied to the directory were we wanted it, BUT the original file is still in the \windows directory. Therefore, we did not save storage memory.
2. We only benefitted from an already installed app built into the ROM.
Hope this gives you some insight.

Trouble with ROM cooking

(First post and not really good english)
One week after i bought my phone (HTC P4350, unbranded) i discovered this site/forum. A very usefull site, i learned much.
Now i am going to try to build my own rom. Based on this howto. (not Vista, but XP Professional)
(WM6: All WM6/WM6.1 ROMS --> All Official HTC Roms --> WWE version)
first i followed the howto without modifications to SYS and OEM to test if everything was working. result: as expected, a working phone.
next step was to remove some folder from SYS.
first try: remove 'windows update' (AUTOUPDATE, Autoupdate_Lang_0409)
flashed to phone, result: Start->Settings->Tab System->Windows Update fully functional, so it is not removed at al,
second try:
restored AUTOUPDATE, Autoupdate_Lang_0409
removed INTERNETSHARING
flashed to phone, result: Start->Programs->Internet Sharing, functional for so far i could test (no internet on phone, sim in other phone), but IntShrUI.exe was available in \Windows
Troubleshooting/Guesses about what went wrong
- Am i deleting stuf in the right directory (C:\Core\Hypercore\Build\SYS)
- Can i continue working in the kitchen after i flashed one time, or should i delete c:\core and start al over again by every modification?
after some houres searching on google and this site i did not found the solution or anyone with a problem like this.
i am doing something wrong, but do not know what.
'Met vriendelijke groet' (Greetings)
Robin

You're doing fine. Not sure why you would still have functioning parts after removing them... you took them off the SYS folder and place them where? (Somewhere NOT in the build folder.)

no, not in the build folder, i put a 'backup'/'copy' in a subfolder of 'my documents'
so i don't think that is the problem
edit:
i carefully read the howto for x time again and know i am wondering if (as below, quote) also goes for SYS folder, find everything with 'intshrui.exe', 'internet sharing', 'autoupdate', 'autoupdate.exe', etc
Add the oem packages into the oem folder. Total commander and networkwzard don’t require removal off default files from the oem folder, but comm. Manager do, and so do htc home. The way I use to find duplicate files, is before I add the oem packages, I open in.ex the new package with comm manager, and I highlight the OEM folder and rightclick and choose searchtab. Search for files, type in search “comm.” And all files containing the word “comm.” Will be displayed, dele them (make sure they belong to comm manager, that the names matches the one in your package)
When you have searched for all files in your package, and deleted them from the OEM folder, you can add you package.
Follow same steps for all packages you add, that can have duplicate files, if you don’t you will get error when building the rom, and the build process will terminate, tell you what file is duplicate. You must then find the file, and remove it (don’t remove the one in your new package)
Click to expand...
Click to collapse

You did it correctly... I wonder if it's really building the ROM or just flashing what's already in there...
I would offer that you use my kitchen, but I think you would definitively keep trying at the HyperCore because it sounds like you might be one of the next generation of cooks. My kitchen is more for the average person who doesn't want to or have the time to learn how to cook but wants their own custom ROM.

what i want for now i a rom with the software i 'need' of like.
i will give your kitchen a try, this link right?
but i don't give up with HyperCore because it should work. if other can do it, i can do it (i think)

r.g.j.jansman said:
what i want for now i a rom with the software i 'need' of like.
i will give your kitchen a try, this link right?
but i don't give up with HyperCore because it should work. if other can do it, i can do it (i think)
Click to expand...
Click to collapse
I'll be uploading Beta 2 soon with a LOT of fixes, you might want to wait until then. Any packages that you'd like to see there before I start uploading?

most packages that i need are in the list.
Basis apps like Office, audio manager are there, same goes for tools.
Your kitchen works easy. Nice work.
With the current release (downloaded at +/- 20:00 GMT+1) has some errors while building. Such as 'the file 'temp\dump\winlive.htm' already exists'.
i think i can handle those error my self, isn't it?
Greeting
Robin

r.g.j.jansman said:
most packages that i need are in the list.
Basis apps like Office, audio manager are there, same goes for tools.
Your kitchen works easy. Nice work.
With the current release (downloaded at +/- 20:00 GMT+1) has some errors while building. Such as 'the file 'temp\dump\winlive.htm' already exists'.
i think i can handle those error my self, isn't it?
Greeting
Robin
Click to expand...
Click to collapse
the double in \tem\ is not important... but there msut be a double in one of the sys or oem folders. try to search them and delete one of them....

Exactly. Do a search for the OEM and SYS folder for the files in question and delete the duplicate. All these errors have been fixed in the Beta 2, but I haven't had time to upload them, yet. (Tried last night but the connection went out half way through it.)
On a brighter note, I'm slowly buying all the parts I need this week to finally rebuild my computer!! (For those that have been here long enough to know my PC fried and I've been working off my ancient laptop for a while.)

when you have uploaded beta2 i will give it a try
good luck with (re)building your pc

i think i know what went wrong..
When starting Hypercore\Panel\Build\BuildOS there are for me 3 options
1. Start "Build OS"
2. Create OS.nb from Sys and OEM
4. Flash
The first time (without changes to SYS and OEM) i copied OS.nb to HyperCore\Tools\RUU for flashing my phone.
By the second test with changes to SYS and OEM i started BuilOS, followed all 3 steps but did not copy OS.nb to HyperCore\Tools\RUU so the first ROM is flashed again, and not my modified ROM
I will now give it another try and will let know the result. But i'm pretty sure this was the problem.
Thanks already for trying to help me.

That would DEFINITIVELY be a problem. lol
After you run 1, then 2, the os.nb will be at the build folder after.

Still some trouble
here i am again.
i don't know if i should start a new thread or go further with this one.
After i removed some software, i am now trying to add software (oem packages). As source i have some cab files. They have to be converted to an oem package, (i read, found on this forum). So i tried to.
Reading and applying this one, and this one BuildOS make trouble.
An messagebox appears with 'Data Exception' and in the bottom (status) is says
[ Error, Last status: "Processing: OEM\OEMAPPS... Searching for dsm file" ]
I tried also with an OEM Package (PocketRAR) downloaded from here.
It keeps saying the same error.
Who can help me?
if you need more information you can ask me for it.

X1 ROM optimization with Kovsky kitchen

**********************************************************************************************************************
IMPORTANT: Use my guide as your own risk. I am not responsible for anything if you device is bricked. Please flash only if you have hardspl installed.
**********************************************************************************************************************
XPERIA ROCKS​**********************************************************************************************************************
I have been using Xperia's cooked roms from Jack and ITJE and they are good. However, there are some problems with working that and not working this. and also I found that either the roms are too light or too heavy.
My goal is making Xperia rom as light as possible and only using xperia original stuffs so that I don't have problems with bluetooth and other things.
And I found a way to taking out junks from Xperia X1 and increased X1's storage space to around 360 MB by using Kovsky Kitchen and working everything normal.
I found that X1i_GENERIC_UK_CDF1215-1832_R2AA010 is the best for me and I stripped out SE's junks from the rom using Kovsky Kitchen. You can do to any original rom for your need.
Preperation:
1. Download Kovsky Kitchen here http://forum.xda-developers.com/showthread.php?t=477801 .
2. Download X1i_GENERIC_UK_CDF1215-1832_R2AA010 .
Start Cooking your own rom:
Step 1: Preperation
1. Extract Kovsky Kitchen to any where you want. (Preferrably C:\Kovsky Kitchen)
2. Rename APP_SW_X1i_GENERIC_UK_CDF1215-1832_KOV_R2AA010.image to RUU_Signed.nbh and copy to Kovsky kitchen's BaseRom folder.
Step 2: Extracting
1. Run KovskyKitchen.CMD
2. Type "e" to extract the original X1 R2AA010 rom
3. Type "a" to start extracting. (It will take around 2 or 3 minutes)
4. Wait until you see "Press Any Key to continue...."
5. Leave the CMD windows open...
Now Kovsky Kitchen is ready to cook...
Step 3: Cooking
1. Go to a newly created folder called " OEM" in the kitchen that where you do stripping out SE's Junks.
2. Go to "ConfigAP" folder. You will see config_AP.txt. Make file writable by changing read only attribute. And delete all links to CAB files that you want to delete. I delete them all as I don't want any of them.
CAB: \WINDOWS\bejeweled2SX1.PPC_2577.WM5_signed.CAB
CAB: \WINDOWS\FM-Radio_Panel_MR1_R19_32318_signed.CAB
CAB: \WINDOWS\GoogleMaps-ms-sonyericsson_emb.cab
CAB: \WINDOWS\GooglePanel_UK_MR1_R19_32195_signed.CAB
CAB: \WINDOWS\GoogleSearch_SEMC_1.1.40_RC3_signed.CAB
CAB: \WINDOWS\MxP_R19_MR1_RC2_32367_signed.CAB
CAB: \WINDOWS\WM6.1_PPC_dawn_Opera_2532_signed.cab
CAB: \WINDOWS\sudokuSX1.PPC_2577.WM5.CAB
Leave only "CFG: \WINDOWS\config_end.txt" line . I don't want any junk in the rom. I will install them later by UC config or manually install them.
And put the file back "Read Only"
3. Delete folders that you don't want in the OEM folder whatever start with "PACKAGE_". For example:
PACKAGE_Kovsky_Bejeweled2
PACKAGE_Kovsky_Bejeweled2_0409
PACKAGE_Kovsky_FMRadioPanel
PACKAGE_Kovsky_FMRadioPanel_0409
PACKAGE_Kovsky_GoogleMap
PACKAGE_Kovsky_GoogleMap_0409
PACKAGE_Kovsky_Googlepanel
PACKAGE_Kovsky_Googlepanel_0409
PACKAGE_Kovsky_GoogleSearch
PACKAGE_Kovsky_GoogleSearch_0409
PACKAGE_Kovsky_HandangoInHand
PACKAGE_Kovsky_HandangoInHand_0409
PACKAGE_Kovsky_MxP
PACKAGE_Kovsky_MxP_0409
PACKAGE_Kovsky_Opera_Browser
PACKAGE_Kovsky_Opera_Browser_0409
PACKAGE_Kovsky_Sudoku
PACKAGE_Kovsky_Sudoku_0409
4. Deleting files from ExtendedPkg (Musics and Movies)
Make config.txt writable and delete
"XML: \WINDOWS\fileoperations.xml" line and Make the file read only again.
Delete all files that are larger than 22 KB except "Xperia Black.tsk", because i like Xperia black theme.
You can delete other files if you want to but for me I leave them alone as they are small enough.
5. Deleting files from SYS folder (These are original WM stuffs)
Delete "AUTOUPDATE" folder
Delete "NetCF" folder (You can install NetCF 3.0 later)
Delete "SampleMusic" folder
Delete "WelcomeCenter" folder
Delete "WelcomeCenter_Lang_0409" folder
You can delete OneNote, Office, or WindowsLive if you would like to. But I leave them alone.
Now.. our rom has no more unwanted stuffs..
Step 4: Building OS
1. Go back to CMD window and
2. Type "C" cook a rom.
3. Type "A" if you want to use the old BuildOS.exe (I can't figure out the second one)
4. BuildOS windows will appear.
5. Just click on green "Play" icon and It will start building our rom. Wait until it finishs and closes the "Build OS" window.
6. Go back to CMD windows again and wait until you see "press any key to contine".. press any key..
7. It will do some stuffs and you will see os-new.nb in the kitchen folder.
8. htc rom tool windows will appear.
Go to Rom Builder TAB. Choose Kovsky * in device. It will fill all the infomation in other fields. Just change the version to anything you like.
9. Choose "os-new.nb" in the OS field. and click on "Build" button.
10. Save it as "RUU_Signed.nbh" in the kitchen folder. A new window appear and it will quit itself.
11. Now. you will see "RUU_Signed.nbh" in the kitchen folder.
12. An Hexa Editor windows will appear. Just close it.
13. You can close CMD window now.
Step 5: Flashing
Now you are ready to flash your own cooked rom. You can flash your rom with RUU Update Utility or just change "RUU_Signed.nbh" to "KOVSIMG.nbh" and put is in SD card and flash it.
For information on how to flash using SD card here .
You can get my sample rom here.
*********************************************************************************************************************
FOR THOSE WHO WANT TO PUT CAB FILES IN THE ROM.
*********************************************************************************************************************
Step1:
Put the line in Config_AP.txt the line "CAB: \WINDOWS\FM-Radio_Panel_MR1_R19_32318_signed.CAB" . It has to be exactly as the cab file name that you are going to put in the OEM folder.
Step2:
Make 2 folders "PACKAGE_Kovsky_FMRadioPanel" and "PACKAGE_Kovsky_FMRadioPanel_0409" in the OEM folder. Put your cab file in the first folder.
And now you are good to go.
Step3:
Open KovskyKitchen.CMD and start the procedures "Step 4: Building OS "from my guide.
************************************************** ********
Step 4: Building OS
1. Go back to CMD window and
2. Type "C" cook a rom.
3. Type "A" if you want to use the old BuildOS.exe (I can't figure out the second one)
4. BuildOS windows will appear.
5. Just click on green "Play" icon and It will start building our rom. Wait until it finishs and closes the "Build OS" window.
6. Go back to CMD windows again and wait until you see "press any key to contine".. press any key..
7. It will do some stuffs and you will see os-new.nb in the kitchen folder.
8. htc rom tool windows will appear.
Go to Rom Builder TAB. Choose Kovsky * in device. It will fill all the infomation in other fields. Just change the version to anything you like.
9. Choose "os-new.nb" in the OS field. and click on "Build" button.
10. Save it as "RUU_Signed.nbh" in the kitchen folder. A new window appear and it will quit itself.
11. Now. you will see "RUU_Signed.nbh" in the kitchen folder.
12. An Hexa Editor windows will appear. Just close it.
13. You can close CMD window now.
************************************************** ************************************************** *****************
FOR THOSE WHO WANT TO PUT OTHER HTC DEVICE'S STUFFS IN THE ROM. (For example "Blackstone" HTC Touch HD)
************************************************** ************************************************** *****************
Step 1: Exact other device's ROM the same procedure as X1 rom.
Step 2: Simply copy folders from Blackstone kitchen's OEM folder to X1 kitchen's OEM folder. For example:
PACKAGE_Blackstone_AudioBooster
PACKAGE_Blackstone_AudioBooster_0409
Step 3: Follow the step 4: Building OS from the guide.
Working Stuffs:
Album
AudioBooster
AudioManagerEngine
Enlarge Startmenu
MP3 Trimmer
FMRadio
Manila
JetCet Print
LargeTitalbar
Volume Control
AdvancedNetwork
Not Working Stuffs: (May need shared files from other folders or tweakings)
Camera (I simply use X1 camera application . Copy \Program Files\CameraRunner.exe to \Windows and rename it to "Camera.exe".)
Youtube (You can simply install Youtube program that has been modified)
CyberonVoice Commander

Nice work!! Downloading at the moment, and see what your guide brings me

wow,that's what i'm looking for!
thanks for the work

How to cook rom 101.. This is what i've been looking for.. Thanks TS.

Brilliant, someone should sticky this.
Been wanting to try cooking my own rom for a while but didn't know where to start. Your example is pretty much exactly what i've been looking for in a cooked rom, strip out all the media junk but not mess with anything else.
What do I have to do to get UC working, is it just a case of having SDConfig.txt on my storage card or do I need to add something to the rom?
Any chance of a part 2 for how to add cab's to the rom? I would like to add a few light weight essentials such as blackstone dialer, fm radio & volume control to mine.

Nice Thread...I will try it later after work...
"Make config.txt writable and delete
"XML: \WINDOWS\fileoperations.xml" line and Make the file read only again.
Delete all files that are larger than 22 KB except "Xperia Black.tsk", because i like Xperia black theme."
One question...what do you mean "make config.txt writable?"

MykeChester said:
One question...what do you mean "make config.txt writable?"
Click to expand...
Click to collapse
In file properties, untick "read-only"
Q

a good guide.Thanks!

thank you very much

Actually, I have never tried to use UC yet. I just install whatever I want manually. Using UC should be quicker to install things. Great chefs like ITJE and Jack should know better. Please search their threads for UC stuffs.
For putting the cab files should be relatively easy. We can do reverse exactly how we stripped them out.
For example , you can do the following if you want to put FM Radio panel back or any other cabs you wanted to include in the rom.
But for me, I want the rom as light as possible and to get the largest storage space, I don't bother to put them in the rom. If I want them, I just install them manually.
Step1:
Put the line in Config_AP.txt the line "CAB: \WINDOWS\FM-Radio_Panel_MR1_R19_32318_signed.CAB" . It has to be exactly as the cab file name that you are going to put in the OEM folder.
Step2:
Make 2 folders "PACKAGE_Kovsky_FMRadioPanel" and "PACKAGE_Kovsky_FMRadioPanel_0409" in the OEM folder. Put your cab file in the first folder.
And now you are good to go.
Step3:
Open KovskyKitchen.CMD and start the procedures "Step 4: Building OS "from my guide.
**********************************************************
Step 4: Building OS
1. Go back to CMD window and
2. Type "C" cook a rom.
3. Type "A" if you want to use the old BuildOS.exe (I can't figure out the second one)
4. BuildOS windows will appear.
5. Just click on green "Play" icon and It will start building our rom. Wait until it finishs and closes the "Build OS" window.
6. Go back to CMD windows again and wait until you see "press any key to contine".. press any key..
7. It will do some stuffs and you will see os-new.nb in the kitchen folder.
8. htc rom tool windows will appear.
Go to Rom Builder TAB. Choose Kovsky * in device. It will fill all the infomation in other fields. Just change the version to anything you like.
9. Choose "os-new.nb" in the OS field. and click on "Build" button.
10. Save it as "RUU_Signed.nbh" in the kitchen folder. A new window appear and it will quit itself.
11. Now. you will see "RUU_Signed.nbh" in the kitchen folder.
12. An Hexa Editor windows will appear. Just close it.
13. You can close CMD window now.
**********************************************************
Hope this help.
i_am_jon said:
Brilliant, someone should sticky this.
Been wanting to try cooking my own rom for a while but didn't know where to start. Your example is pretty much exactly what i've been looking for in a cooked rom, strip out all the media junk but not mess with anything else.
What do I have to do to get UC working, is it just a case of having SDConfig.txt on my storage card or do I need to add something to the rom?
Any chance of a part 2 for how to add cab's to the rom? I would like to add a few light weight essentials such as blackstone dialer, fm radio & volume control to mine.
Click to expand...
Click to collapse

@htainlin
Thank you greatly for these posts - they are very clear and concise.
Most of all, they are explicit and very helpful. Trying to obtain a "road map" of ROM cookery is very frustrating - it's all a "big secret", where you are advised to read and read etc, but the multifarious references are truncated, incomplete, chaotic and contradictory. You've helped enormously in cleaning up this mess.
Straightforward now - generic RA3 versions will turn up sometime.
Re UC:
I use this to re-install most apps after a new ROM flash (see Jack Leung's thread for my posts). The only real hassle for UC are those apps that splatter files on installation to both the SD card and Storage. There is a huge thread on UC with most questions answered in one fashion or another, but it takes patience to sort through it. Having done it once, you need only update your sdconfig.txt as you add/remove apps over time.

Nice post!
However if you really want to make a streamlined rom use Ervius Visual Mulitlang Kitchen
http://forum.xda-developers.com/showthread.php?p=3147148#post3147148,
The GUI is pretty neat, and it uses Bepe's new kitchen system to get rid of extra gumpf in the roms (such as dsm files).
this then optimizes it a bit as /windows has less files in it. Ergo it does things faster.
this will also work with the newer format roms coming I think.

ianl8888 said:
@htainlin
Thank you greatly for these posts - they are very clear and concise.
Most of all, they are explicit and very helpful. Trying to obtain a "road map" of ROM cookery is very frustrating - it's all a "big secret", where you are advised to read and read etc, but the multifarious references are truncated, incomplete, chaotic and contradictory. You've helped enormously in cleaning up this mess.
Click to expand...
Click to collapse
There's no "big secret" the reasons you've stated are the reasons people tell you to read. If there was one post to point people to then don't you think people would have done it?
It takes a lot of time to do the work that htainlin did, which is why most people dont get around to doing it all.
htainlin stick it in the WIKI.

Very rom cooking guide for beginner
Nice work. I did something similar for Asus P525 long time back and I know it's takes a lot of effort to bring everything together, and explain the subject clearly for beginner.
This is a very good starter "re-cooking" document for beginner. There is no "big secret" for rom cooking. All you still need to do is research and read a lot more to do some hardcore stuff for the next level. e.g. remove unnecessary driver/service/registry Welcome center / Customer Satisfactory ...etc, replace driver w/ other device to get more functionality. Then XIP/Sys port .....etc

Thanks guys. I am not really into cooking.
My goal is to take the "Unwanted Stuffs" out from the rom so that the storage will be larger and just a small guide to everyone who wants to make their rom lighter. Everyone should be able to do it themselves for their likings to any future rom versions.
There is "NO BIG SECRET" for rom cooking. But for beginners, it is really hard to figure out how to use "Kovsky Kitchen". Once you are experienced, it's quite easy.
But for advanced stuffs as Jack mentioned.. we need more research and skills. I might write a detailed guide later, how to edit registry and replacing better dlls and applications.
Everyone has his/her own preferences and I just want to show them even a beginner could do themselves.
Windows mobile is the best ever mobile os for me so far and you can modify anyway you like. Thanks to many developers who created kitchen and make things easy for us.

how to's...
here are some of the how to's i stumbled on ppc geeks. hope this enlighten some in modding/customizing roms:
1. how to's for developing
2. adding registry entries (rgu method)

twisted said:
here are some of the how to's i stumbled on ppc geeks. hope this enlighten some in modding/customizing roms:
1. how to's for developing
2. adding registry entries (rgu method)
Click to expand...
Click to collapse
Thanks for the links. Very good.

There is no need to do such a hard job - to extract & rebuild all the ROM file.
Just take HTC Rom Editor, open your ROM there, clear all useless stuff and correct files
config.txt
config_AP.txt
config_operatior.txt
config_SP.txt (if exist)
fileoperations.xml
runlua.cc
Then save your rom and flash it. Easy way.
PS: My custom rom with cleared "stuff" (even SE Dialer) and some features is about 65MB, and makes about 360+MB free memory.

Great job! Big help to us new to WM and ROM cooking. Thanks, mate!
+1 to make this thread sticky

great write up. got a couple questions tho.
what effect does deleting the \windows\fileoperations.xml have on:
ringtones? will you have to maually load your ringtone, like for my alarm, notifications (mail, sms)
internet explorer start page?
startup animation?
panels? will i still have the se1 and 2 panels? how about the today panel?
thanks,
claudio

[REF|TUT] My first Rhodium ROM - Completed

I’ve started cooking my own ROM’s only a week ago. I wanted to share my experiences here as it’s not as easy as it seems Well, with the right settings, tools, references, etc it makes it easier though. So this is my sharing back to the community, my tutorial/reference guide on how to cook a ROM.
The result of my days of hard work is named DaxyROM and can be found here.
If you want to start cooking, be prepared to read a lot and spent a lot of time trying your home cooked meals. But when it boots and works as expected, you’ll enjoy all the time spent.
There are 3 steps I’d like to discuss in the following 3 posts:
1) Basic ROM extraction and cooking
2) Adding / Removing programs
3) Upgrading your XIP/SYS (aka install new OS version)
First of all get to know what you’re dealing with. Understand what SYS/EXT/OEM/ROM/XIP is ‘cause at the end of the week you can’t think of anything else. Good source here.
1 Basic ROM extraction and cooking
I’ll be using the Ervius Visual Kitchen and the official WM6.5 ROM from HTC to start with.
* Download Ervius Visual Kitchen. Always use the latest version.
* Download WM6.5 ROM’s from HTC
* Download CustomRUU.exe
Preparing the kitchen:
Extract Visual Kitchen (VK) to C:\Kitchen (will be refered to as Kitchen now)
Create a directory in the Kitchen named RomDump
Open the WM6.5 HTC ROM .exe file with Winzip
Extract the file named RUU_signed.nbh to the RomDump directory
Now open the Kitchen (erviuskitchen.exe). Ignore the warning messages
Click on the bottom left button named “Dump nbh/nb/payload”
Open the RUU_signed.nbh file and wait till it’s completed.
Enter the Kitchen\RomDump\dump directory
Move all files to Kitchen directory
There seems to be an issue with kitchen_build_rom.bat while building your ROM.
Modify your kitchen_build_rom.bat file from this:
Code:
set DSM_TEMPLATE=%dsm%
set DSM_INCLUDES=*
REM **************** TOOLS\platformrebuilder.exe
if not "%errorlevel%"=="0" goto error
To this:
Code:
set DSM_TEMPLATE=%dsm%
set DSM_INCLUDES=*
REM **************** TOOLS\platformrebuilder.exe
REM **************** if not "%errorlevel%"=="0" goto error
You’re now ready to go.
Built your first ROM – The Visual Kitchen Basics:
Click on the pull-down menu next to RHODIUM and select RHODIUM
Ignore the messages. You’ll see the screen building now
Fill in the name of your ROM at the ROM ver. Field
Check the “Real WM 6.5 AKU” field
Click on the “Other” button
Change the –PP value from 6 to 18 and click on the Close button
Save the settings: hit the “Save ROM” button. Filename must end with extension .erv.
You’re ready to hit the Create ROM button
Wait till it finishes
Now open the Kitchen\RELEASE_Rhodium directory
Copy the CustomRUU.exe to this directory and run it
You’re now running the HTC WM 6.5 ROM rebuilded by yourself
Right now your kitchen is ready to use and you can modify it as much as you like.

Part 2: Adding / Removing programs
Right now we know that the kitchen works. We have rebuiled the official version and it boots up fine. Make sure to test your extracted ROM works otherwise you will loose a lot of time. Now it's time to make changes. Keep in mind that the following is what I've teached myself and that there might be better methods in adding/removing packages.
The easiest is removing packages. Just double-click on the package and it won't be included. If you want it back, just double-click again and it's back in. Easy as that.
Keep in mind that you can't remove OEM packages and that if you're removing packages from the SYS you have to be carefull as you might run the risk you remove a core application and that Windows won't boot anymore. You can however safely remove packages like LiveSearch, MSTag, OneNote, etc without any problems.
The EXT directory is where all packages reside. This directory is devided in 2 sub-directories. One for Rhodium specific packages and one for Shared platforms. By default all applications are in the Rhodium directory but you might want to change this manually to Shared if you're planning on building for multiple platforms. For now we'll keep them in the Rhodium directory.
You need to either find EXT packages online, or you need to convert CAB files to EXT packages. That is basically it.
I've found a lot of new EXT files here: http://www.everythingdiamond.info/showthread.php?t=94. You can download new EXT folders and copy them into the VK\EXT\Rhodium\<built>\Rhodium_External_Packages directory. Now load VK and Load your previous saved config. Scroll down the list and you will see your new package. This package is not yet included in the Kitchen. This is useful if you're upgrading packages so you'll know which one is new and which one is old.
If you're upgrading packages, keep in mind that some do depend on each other. For example Manila heavily depends on all kinds of other packages. When you're upgrading one, upgrade the others as well unless you're certain there are no dependances. You'll find out when your upgrading. Make sure to safe your work very often so you can always revert back to your previous situation.
As I mentioned you can also convert CAB's to EXT. This can be done using the package-creator from Ervius. TotalFire Package Converter does the job as well, but I haven't used it yet.
Download your application as cab file. Open the package converter, open the cab file and it converts to an EXT directory. This EXT directory can be copied into the kitchen again.
Adding your own EXT is more complicated. For example if you want to create a package which holds all your registry tweaks.
You can either download this file and change the .reg file, or you can take the hard way and learn by using this tutorial: http://www.mediafire.com/file/j15nqfzkwz5/CreatingOEM.zip
Both are written by user kwbr. See here for more info: http://forum.xda-developers.com/showthread.php?t=480714.
I believe this concludes this section. You should be able to add and remove packages right now. Next stop, installing a different Windows build.
Please sent me feedback on how to improve my posts.

Part 3: Upgrading your XIP/SYS (aka install new OS version)
It's time for the last part of my Tutorial. This time I will explain how to upgrade your XIP/SYS.
First you need to find your new XIP/SYS. I get mine WM 6.5.1 at http://forum.xda-developers.com/showthread.php?t=544445 but there are probably more sources.
First you need to know what to get. If I'm taking the above URL as example, there are several files.
The first one you need is the XIP/SYS one. This however is the OS for a screen resolution of 480x600 (The Touch Pro2 has a screen resolution of 480x800). You still need this file as it the the base OS combined with the (wrong) resolution files. That's why you need the 2nd file named "0409 USA English United States (Includes COMMON DPI, required for others)" as well. This is the english version for all resolutions.
The first file you can just extract in your SYS directory. It will create a new directory with the new build number and a directory named Shared.
The Shared directory you need to move to your ROM directory. This means you end up with a new build number in the Shared directory.
Now we just need to make sure the resolution files are copied. This means you need to copy a list of directories. At first create a directory named SYS\<build>\dpi_192_resh_480_resv_800. Just extract the complete 0409 Language file into a temp directory and the create the following directory structure by moving directories:
Code:
SYS\<build>\dpi_192_resh_480_resv_800\0409\Base_Lang_0409_DPI_192_RESH_480_RESV_800
SYS\<build>\dpi_192_resh_480_resv_800\0409\Themes_Lang_0409_DPI_192_RESH_480_RESV_800
SYS\<build>\dpi_192_resh_480_resv_800\COMMON\base_dpi_192_resh_480_resv_800
SYS\<build>\dpi_192_resh_480_resv_800\COMMON\MediaOS_dpi_192_resh_480_resv_800
SYS\<build>\dpi_192_resh_480_resv_800\COMMON\Phone_dpi_192_resh_480_resv_800
SYS\<build>\dpi_192_resh_480_resv_800\COMMON\Redist_dpi_192_resh_480_resv_800
This concludes the SYS, now the XIP.
The zip file you downloaded also contains a directory named "MSXIPKernel".
Extract this directory to your ROM\Shared\<build> directory.
Now go into the directory ROM\Rhodium.
Inside the builds you can find the OEMXipKernel which are basically the device specific drivers.
Usually these drivers don't change, unless you are upgrading the OEMXipKernel using a newly released ROM from HTC.
For now you have to copy the original build directory over to the new directory and you're done.
Right now your OS is ready to cook:
Open your Kitchen
Open your saved configuration file
Change the XIP and SYS versions (top right) to the new build version
Hit the Create ROM button
You're all set
After creating your new SYS, I suggest changing some default values. For example changing Unsigned Themes/CAB Policies:
Open the file named OEM\Rhodium\0409\Operator Pkg\mxipupdate_oemoperators_100.provxml
Find the section <!--337.01_SecurityPolicy-->
Add the following lines:
Code:
<parm name="4101" value="8" />
<parm name="4102" value="1" />
<parm name="4122" value="1" />
<parm name="4103" value="16" />
<parm name="4097" value="1" />
Save the file
Cook your ROM
Basically this means:
ID 4101: Unsigned CABS Policy = 8
ID 4102: Unsigned Applications Policy = 1
ID 4122: Unsigned Prompt Policy = 1
ID 4103: Unsigned CABS Policy = 16
ID 4097: Unsigned Prompt Policy = 1
Now you won't get warnings if you install unsigned applications etc.
One last thing to keep in mind. Don't forget to grab a new version of the OEM directory once it gets released by HTC.
I've ran into a situation where ActiveSync ran out of memory and a new OEM fixed this.
Thanks
Ervius: Big thanks to Ervius for his great Kitchen and Package creator: http://forum.xda-developers.com/showthread.php?t=469420
Da_G: For providing the latest WM builds: http://forum.xda-developers.com/showthread.php?t=544445
hilaireg: For providing his tuturial which was my starting point: http://forum.xda-developers.com/showthread.php?t=521632
kwbr: For his tutorial on creating applications: http://forum.xda-developers.com/showthread.php?t=480714
Everyone I forgot to add. Make yourself known and I'll add you of course!
This concludes my Tutorial. I hope you find it useful. Please feel free to provide feedback so I can adjust the tutorial or provide answers.

Eventually I may try cooking my own ROM.
Not because I can't find any good roms out there.
But just for the simple fact that I want to learn how to do it.
Thanks for taking the time to write this all up.

Just what I was looking for. I have been searching and reading and searching and reading but not getting anywhere. After following your post I've dissasembled a ROM, renamed it, and then reassembled it.
Now I was just following a recipe and didn't understand everything that happened (what is the -PP value and why am I changing it?) but I'm finally making some progress. Looking forward to your upcoming posts.
BTW, I just used the official TMo US 6.1 ROM that CDGuider dumped and made available. It'll do while I'm learning but I'm really waiting for the Official TMo US 6.5 to be released so I can use it as the main ingredient.
S

sleonard said:
Just what I was looking for. I have been searching and reading and searching and reading but not getting anywhere. After following your post I've dissasembled a ROM, renamed it, and then reassembled it.
Now I was just following a recipe and didn't understand everything that happened (what is the -PP value and why am I changing it?) but I'm finally making some progress. Looking forward to your upcoming posts.
BTW, I just used the official TMo US 6.1 ROM that CDGuider dumped and made available. It'll do while I'm learning but I'm really waiting for the Official TMo US 6.5 to be released so I can use it as the main ingredient.
S
Click to expand...
Click to collapse
Let me know if I missed something. I had to do it from the top of my head so if I forgot to add an action, let me know and I'll add it.
PS, the -PP allows you to change the PagePool size (sort of swapfile for WM).
Some people set it to 0, some to 12-18. I found 18 to be working fine. I must admit that I have too little knowledge to truly understand the PP stuff to come to a clear correct value (I believe it's questionable, the values).
If anyone disagrees, let me know

This is a great post.
I've subscribed because I'm really interested in learning and once I've ran through it myself will reference it on my site for all to use.
Well done you, supply and demand.

Daxy, On Tuesday I get my Pro2 and begin to try. Thanks for a great post!!!!!!!!!!!!!

I download the files of 23069, for example, where should I hold?
Xip and sys...

Awesome Information!! Thanks a lot and I appriciate it because rarely people share knowledge!

Thanks for the clear tutorial! Looking forward to future updates!

really excited to start making my own roms...
thank you for taking the time and making this
hopefully in the future ill be able to contribute to the community...
my touch pro2 could use some of my own flavor lol

thanx for the effort ...
gonna read thru it when i am more awake ... lol ... this seem to be what i am looking for ... wanna cook my own rom but proper info is few and far between for the rhodium ... unless i waslooking in the wrong places ... hehehe

I have used this tool to dump official rom, it works. But when i dump others' customized roms, it always says 'lost XIP'. why?

Thanks all for your kind words.
I've updated Post 2: Adding / Removing programs
Hope you like it. Please let me know if anything is missing.
Next post will be regarding using a new version of Windows, where to place files etc. This one should be up in a couple of days.

eddy16112 said:
I have used this tool to dump official rom, it works. But when i dump others' customized roms, it always says 'lost XIP'. why?
Click to expand...
Click to collapse
Customized ROMs are protected. You cant dump them. You can only dump official ROMs.

eddy16112 said:
I have used this tool to dump official rom, it works. But when i dump others' customized roms, it always says 'lost XIP'. why?
Click to expand...
Click to collapse
ai6908 said:
Customized ROMs are protected. You cant dump them. You can only dump official ROMs.
Click to expand...
Click to collapse
Correct! even if the customized rom was unprotected you still would not be able to rebuild a rom off of it because of the loss of rgu's and dsm's in the origional building process. would be very difficult.. best thing to do is ask for the kitchen files from the chef and hope they can share.
edit: one thing you can do is use an app called rom imaged editor and open the nbh with that, you can grab individual files out, even protected roms you can.. then you can add things on your own.

I've changed the topic to My first Rhodium ROM. Though it would sound better.

joshkoss said:
edit: one thing you can do is use an app called rom imaged editor and open the nbh with that, you can grab individual files out, even protected roms you can.. then you can add things on your own.
Click to expand...
Click to collapse
I have extracted files from kooked roms no biggie. saves time from flashing for sure...
I have tried to extract all files from kooked rom too, and it seems to work. but might be able to use some dll files.

Everytime I build the ROM (rebuilding the stock rom, not config changes) towards the end the kitchen gives me a runtime error, I have tried on a 64-bit vista and 32-bit XP.
After reviewing the log it appears that the problem is:
Executing: kitchen_build_rom.bat.....
ERROR! (errorlevel: 1)
ERROR executing: kitchen_build_rom.bat
ERROR!!!
Wait some seconds...
No ''SVN'' folders present...

how to extract cabs from NBH file

im trying to extract some cabs from a NHB file...can anyone guide me in the direction on how to do this

I'd say the best way to do that is to extract the ROM into regular files.
You need to download a bunch of EXE files: NBHextract.exe, NBSplit.exe, ImgfsToDump.exe, and ImgfsFromNB.exe
You need to extract the NBH with NBHextract.exe. This will yield a .nb file
You need to use NBSplit (use the "-kaiser" parameter) to split the .nb into a .nb.payload file and a .nb.extra file
You then need to use ImgfsFromNB on the .nb.payload file, which will create a file called imgfs.bin
Use ImgfsToDump on imgfs.bin, which will create a folder called "Dump". When it finishes, All of the ROM's files will be there. You will probably want to search the folder for .cab files, since there are thousands of files in the average ROM dump.
That should do the job for you.

Or just use Visual Kitchen to Dump the ROM, and then rebuild the OEMs to CABs.
Dave

could u walk me through the visual kitchen program?

Hmmm look for htcRIE_0.4.0.47 and extract what you want.

im trying to extrct the streaming media player cab...the one thats in most of the 6.5 roms that has a look a like HTC ablum look to it, but i cant find a cab using "htcRIE_0.4.0.47"

little help will might ...
You do not search for it at you WM ROM,
Search at the site...
Anyway i have been find it for you !
A newer version of htcRIE, enjoy!
michealmyers said:
im trying to extrct the streaming media player cab...the one thats in most of the 6.5 roms that has a look a like HTC ablum look to it, but i cant find a cab using "htcRIE_0.4.0.47"
Click to expand...
Click to collapse

i have that program, but im unsure on how to properly use it to get the cab files.....can u help me?

michealmyers said:
i have that program, but im unsure on how to properly use it to get the cab files.....can u help me?
Click to expand...
Click to collapse
With Visual Kitchen, just click on the Dump button at the bottom - and then browse to the NBH file .
Dave

i guess all nbh files dont have cabs because in the dump folder it creates...its only a couple of cabs and whole lot of systems files

michealmyers said:
i guess all nbh files dont have cabs because in the dump folder it creates...its only a couple of cabs and whole lot of systems files
Click to expand...
Click to collapse
Yeah, you have to rebuild the EXT packages to CAB's I don't know if there is a tool for that actually. Might be better dumping it the Dave (TyTNII) way, that will give you OEM's. There are tools for OEM 2 CAB.
Jason8 is working on a tool to convert all 3 all ways IIRC.
Dave

the nbh extract file launches for a quick second...it doesnt stay on the screen, as well as a lot of other files such as nbh split....do i need to update something in order to have these programs run properly?

michealmyers said:
the nbh extract file launches for a quick second...it doesnt stay on the screen, as well as a lot of other files such as nbh split....do i need to update something in order to have these programs run properly?
Click to expand...
Click to collapse
You have to run them from the windows command line (CMD.exe). If you really want me to, I'll upload a batch file I made which automates most of this. You just put the NBH and tools in certain folders and run the batch file and it does the rest.

DaveTheTytnIIGuy said:
You have to run them from the windows command line (CMD.exe). If you really want me to, I'll upload a batch file I made which automates most of this. You just put the NBH and tools in certain folders and run the batch file and it does the rest.
Click to expand...
Click to collapse
that would be so helpful

Alright, I fixed all the bugs in it (it was still in progress) and added some new features I had meant to add for a while, such as renaming the processed files by date processed (though you probably won't need them if you're only extracting one ROM). Hit [WINDOWS KEY] and R on your keyboard at the same time to open the Windows Run dialog, and type "%USERPROFILE%" without the quotes. Simply unzip the file and drag the folder called "Flashing" in the user folder (it's vital to have the Flashing folder in the correct spot. Otherwise, the entire script will fail). Place the NBH file you want to extract in the NBHDUMP folder (in the Rhodium folder, which is in the Flashing folder), and go to the IMGFS folder (in the Rhodium folder, which is in the Flashing folder). Now, run RhodiumRomDump.bat and the dump should commence, and a folder with your dump should appear in the same directory.
If anything should go wrong, please tell me so I can try to fix it.
EDIT: Please redownload, all issues I could find are fixed in this version. If you get errors about needing MSVCr71.DLL with this version, google is your friend.

maybe im not doing something right, ive been at it for days now...i put the "flashing folder" in C:\Documents and Settings\Sean (sean's my name..haha), put the nbh file in the NBH folder, ran "DumpRhodiumRom", i got 2 folders named "and" and "Setings"....when i run "dumpRhodiumRom", its just stays on the screen for half a second

ive extracted the rom before using visual kitchen...im trying to get some of the programs into cabs...the problem is that in the dump file, i see the programs i want, but they arent in cabs, so i cant just take its "exe" file and put it into another phone (well at least that didnt work for me)

michealmyers said:
maybe im not doing something right, ive been at it for days now...i put the "flashing folder" in C:\Documents and Settings\Sean (sean's my name..haha), put the nbh file in the NBH folder, ran "DumpRhodiumRom", i got 2 folders named "and" and "Setings"....when i run "dumpRhodiumRom", its just stays on the screen for half a second
Click to expand...
Click to collapse
That's odd. Can you tell me two things?
Where do these folders ("Settings" and "And") show up?
Hit [Windows Key] + R and type "CMD" (without quotes), then hit okay, then type "cd %USERPROFILE%\Flashing\Rhodium\IMGFS" (without quotes). Now, type "DumpRhodiumRom" (without quotes), and tell me exactly what is says (you don't actually have to include all the formatting and everything). Also, if you could tell me what color it's in, that would help.
I'm going to test it in a virtual Windows XP environment and see if it's compatiblity with XP that's the problem.
EDIT: So the problem seems to be the fact that it doesn't like the spaces in the folder name "Documents and Settings", hence the creation of the "and" and "settings" folders. Unfortunately, it's an important folder, so renaming isn't really possible. However, I think I know a simple fix to the original script, so I'll test that and post it shortly.

michealmyers said:
ive extracted the rom before using visual kitchen...im trying to get some of the programs into cabs...the problem is that in the dump file, i see the programs i want, but they arent in cabs, so i cant just take its "exe" file and put it into another phone (well at least that didnt work for me)
Click to expand...
Click to collapse
Try downloading cabtools V 0.3 and use pkg2cab to build the package back into a .cab file. I've never done it myself, but this looks like what you want.

DaveTheTytnIIGuy said:
That's odd. Can you tell me two things?
Where do these folders ("Settings" and "And") show up?
Hit [Windows Key] + R and type "CMD" (without quotes), then hit okay, then type "cd %USERPROFILE%\Flashing\Rhodium\IMGFS" (without quotes). Now, type "DumpRhodiumRom" (without quotes), and tell me exactly what is says (you don't actually have to include all the formatting and everything). Also, if you could tell me what color it's in, that would help.
I'm going to test it in a virtual Windows XP environment and see if it's compatiblity with XP that's the problem.
EDIT: So the problem seems to be the fact that it doesn't like the spaces in the folder name "Documents and Settings", hence the creation of the "and" and "settings" folders. Unfortunately, it's an important folder, so renaming isn't really possible. However, I think I know a simple fix to the original script, so I'll test that and post it shortly.
Click to expand...
Click to collapse
This is What i got....where the "and" and "settings" folder apear is "untitled2.zip"