Database Develop

Modded Cappackage.pxp Files

So I thought it would be worthwhile to create a thread focusing on modified "cappackage.pxp" files. These are the files which control the default carrier specific configurations. In my case, I am running the Aussie "Three" WM6 OS, however I wanted some, but not all, of the ATT customizations. For example, I wanted the proxy tool, the logos and the certs . . . Attached is a modified version of the ATT cappackage.pxp file. I had difficulty configuring WindowsMobileLive.cab and the HTC task manager to automatically install as part of this new file so I will post those cab files as well for convenience (for those who may want it).
If you have a customized cappackage.pxp, please post it in this thread and describe how it has been modified so everyone can decide which they may want to use.
Here are the changes I made to the cappackage.pxp file. Note, all of these .cab files should be possible to install directly simply by extracting from original ATT WM6 cappackage.pxp in case you happen to need one of them:
delete getgood.cab
delete getmail.cab
delete realplayer.cab
delete getmobitv.cab
delete cmradio.cab
delete attmallandmusic.cab
delete musicid.cab
delete jarguarrm.cab
delete gettelenav.cab
alter "Att_Settings.prov.xml" to remove messaging and Windows Mobile Live registry customizations
add install of new devstate.dll (exists in 3AUS cappackage.pxp and also in ROW 2.23 cappackage.pxp)
ABS
EDITED 12-30-2007: Note - this altered cappackage.pxp file is based off the "leaked" ATT WM6 ROM.

abs99 said:
So I thought it would be worthwhile to create a thread focusing on modified "cappackage.pxp" files. These are the files which control the default carrier specific configurations. In my case, I am running the Aussie "Three" WM6 OS, however I wanted some, but not all, of the ATT customizations. For example, I wanted the proxy tool, the logos and the certs . . . Attached is a modified version of the ATT cappackage.pxp file. I had difficulty configuring WindowsMobileLive.cab and the HTC task manager to automatically install as part of this new file so I will post those cab files as well for convenience (for those who may want it).
If you have a customized cappackage.pxp, please post it in this thread and describe how it has been modified so everyone can decide which they may want to use.
Here are the changes I made to the cappackage.pxp file. Note, all of these .cab files should be possible to install directly simply by extracting from original ATT WM6 cappackage.pxp in case you happen to need one of them:
delete getgood.cab
delete getmail.cab
delete realplayer.cab
delete getmobitv.cab
delete cmradio.cab
delete attmallandmusic.cab
delete musicid.cab
delete jarguarrm.cab
delete gettelenav.cab
alter "Att_Settings.prov.xml" to remove messaging and Windows Mobile Live registry customizations
add install of new devstate.dll (exists in 3AUS cappackage.pxp and also in ROW 2.23 cappackage.pxp)
ABS
Click to expand...
Click to collapse
Thanks, any idea if we can add another carrier in the carrier_db file that isn't there?

john_99 said:
Thanks, any idea if we can add another carrier in the carrier_db file that isn't there?
Click to expand...
Click to collapse
I honestly do not know. Sorry. You might ask Olipro as he seems to be very knowledgeable.

abs99, what tool did you use to repackage your PXP file. I've tried several archive tools to .ZIP and rename, but no joy. I've looked, but can't find any info on PXP file creation. Surely, I'm missing something simple here.
TIA

I found that "winrar" can handle the files without a problem. I had also noticed that the date stamps were the same for all the files in the original package, so I also use a tool called "stamp it" to set all the dates on all the files in the new package to the same original date.

thanks. I found that 7-zip is working too.
Now, the next step, I'm trying to mod the capdata.xml file and for whatever reason the device will not recognize it after my mods.
Here's my version of an ATT config file:
Code:
<?xml version="1.0" encoding="utf-8" ?>
- <Varnish xmlns="http://www.ephox.com/product/editliveforxml/document/Untitled20062026011007629">
<Version />
<Notes />
<UpgradePath>always|</UpgradePath>
- <PolA>
- <Certificates>
<File>CingularCert.prov.xml</File>
</Certificates>
- <Certificates>
<File>Class3_PCA_G2_v2.xml</File>
</Certificates>
- <Certificates>
<File>entrust_gssl_ca.prov.xml</File>
</Certificates>
- <Certificates>
<File>RSA1024RootCA.prov.xml</File>
</Certificates>
- <Certificates>
<File>RSA2048RootCA.prov.xml</File>
</Certificates>
- <Certificates>
<File>VeriSign_C3_PCA_G3v2.prov.xml</File>
</Certificates>
- <Ringtone>
<File>AT&T Tone.wav</File>
</Ringtone>
- <ProvXML>
<File>ATT_Settings.prov.xml</File>
</ProvXML>
- <ProvXML>
<File>MSFPHeartbeat.prov.xml</File>
</ProvXML>
- <ProvXML>
<File>ResetRequired.prov.xml</File>
</ProvXML>
- <InstallApp>
<File>WindowsLive.CAB</File>
</InstallApp>
- <InstallApp>
<File>ATT_Theme.CAB</File>
</InstallApp>
- <InstallApp>
<File>ProxyManager.CAB</File>
</InstallApp>
- <InstallApp>
<File>ATT_Content.cab</File>
</InstallApp>
- <ExtractZip>
<From>DevState.zip</From>
<To>\Windows</To>
</ExtractZip>
</PolA>
- <Welcome>
<WaitImage>E_PolishImage.bmp</WaitImage>
</Welcome>
- <Sweatshop>
<AccountName>GEN</AccountName>
<VarnishName>ENG</VarnishName>
<BuildName>005</BuildName>
<User>[email protected]</User>
<Environment>Sweatshop QA Staging</Environment>
<CoreVersion>1.9.9</CoreVersion>
<Treo750Version>3.0.0</Treo750Version>
<DateStamp>Wed Aug 22 6:10:15 PDT 2007</DateStamp>
</Sweatshop>
</Varnish>
Any thoughts? This is just a basic mod and plan to get more detailed configs in there once I figure out what I'm doing wrong.
TIA

The issue with this file may be that editor you are using is adding "white space". I found that some editors caused this to occur. I ended up the file in notepad to avoid the problem as it was a real mess to deal with any other way. You should open the original unedited file and your new edited file in notepad and compare both. For whatever reason, the OS does not like to deal with a properly formatted .xml file!

Thanks mate, the white space and file size were the culprit. Was trying to cheat and use MS xmlnotepad - very easy to use, but it added the whitespace as it made it pretty to look at. I also was trying to cram too much into my archive; the extracted archives need to fit in the 8.4mb along with the archive itself.
Attached is a custom CapPackage.PXP with the following (based from ATT 2.25 ROW, CapPackage.PXP):
ATT Theme
Regional Settings: US, - 5 EST
ExtROM mount and rename
Custom ringtone
Custom Sounds Settings
Delete poutlook.lnk from startup
Set Hello to ATT
Disable CAB security policy
Removed all ATT applications (CV, real, win live, etc)
TODO: Incorporate RegHacks of additional settings customization and tweaks (lots of typing...), right now I install and merge the apps I want after initial setup completes.
Cheers

HOW TO
***always a good idea to backup existing files before attempting any modification***
1. mount your extended rom (search for the cabs and instructions on this site)
2. copy the CapPackage.PXP from ExtendedROM\Partition to your PC
3. extract the contents to a folder named CapPackage on your PC (any ZIP compliant archive tool will do)
4. remove/add the *signed* cab files your desire (unsigned cab files simply get passed over)
5. open capdata.xml in epcEDIT or notepad.
6. add/remove the configuration information as desired - this is where some trial and error comes in trying to determine what commands control what function.
7. ZIP (no other archive format seems to work) the CapPackage folder to CapPackage.PXP (or rename .zip to .pxp).
8. copy to ExtendedROM and hardreset.
TODO:
-Hope to be able to post a list of commands for the XML to enable configure of most if not all device "settings"
-Hope to figure out a way to get unsigned cabs to install (present workaround is a zip extract and registry commands if the app isn't too complex (e.g. lots and lots of typing required)
--Not sure yet if reg hack setting "HKLM\Security\Policies\Policies' valuename '0000101a' to dword:1" will resolve this during initial setup

Okay, after getting my questions about how this all works and saves the space on the phone, I took the plunge and upgraded from 2.23ROW to 2.25ATT. Went smooth as butter, and I have a "decrapified" phone with the official, supported ATT release (just in case I have any problems and need support).
Of course, being a hacker, now I'm totally intrigued by this cappackage customization, and want to play with it myself. So, Tim et. al., two questions:
Does the capdata.xml file have to match the contents of the archive? Or, if something's missing, it's just ignored? I'd like to be able to delete some more stuff and remake the PXP file without having to hassle with the XML file and run into the problems you have (workable, but I just don't want to waste time on whitespace issues if I don't have to).
Does the carrierDB file need to stay in the extended ROM for any reason after install and setup? I'd like to archive it on my PC, and delete it from the extrom so I can use that space for general storage.

microsoft word has a wonderful xml file editor. rather than try and keep everything straight in that jumbled up mess you get out of notepad or some other editor, word indents all the xml, and makes it look like it should. it was a snap to edit. I used Winrar and opened the PXP file. I never extracted the contents. Just the capdata file. I edited it, and then put the edited version back into winrar. using winrar I deleted the files I didn't want. saved the archive and moved it back to the device.

dwallersv said:
Does the capdata.xml file have to match the contents of the archive? Or, if something's missing, it's just ignored? I'd like to be able to delete some more stuff and remake the PXP file without having to hassle with the XML file and run into the problems you have (workable, but I just don't want to waste time on whitespace issues if I don't have to).
Does the carrierDB file need to stay in the extended ROM for any reason after install and setup? I'd like to archive it on my PC, and delete it from the extrom so I can use that space for general storage.
Click to expand...
Click to collapse
1. The XML will bypass anything it can't actually do.
2. I have tried it both ways and feel like I've had no issues, but I have seen some reports of strange behavior without it. I currently have it in my ExtROM since I hard reset my device often as I test apps and config settings. If you don't hard reset very often then once the device is hard reset you may delete and gain an additional 1.45mb.
The thing I intend to work on next is creating a provisioning XML to call an external XML (outside of the cappackage). I'm hoping this way I will be able to strip even more out of the cappackage (literally everything but the capdata.xml) and hav an on the fly configuration capability and call installations and configuration from the SD card. Haven't had much time to play with it though.

Can someone help point me in the right direction to get start loading the cappackage. I can't seem to find how to mount the extended ROM. I did a search for it and everything that came up didn't explain it (or at least I didn't understand it if it did).

Hmm, I can't seem to find the original thread either. Really just registry entries, but the cab's make it easier.
See attached...
Run each in order, then soft reset
Cheers
FYI: You can use my cappackage (see pg 1) as a starting/reference point for building the extROM mount into the initial config process after hard reset...

Try this. ...............
sodak said:
Can someone help point me in the right direction to get start loading the cappackage. I can't seem to find how to mount the extended ROM. I did a search for it and everything that came up didn't explain it (or at least I didn't understand it if it did).
Click to expand...
Click to collapse

Thanks to both of you for the quick response

I don't know whether it is because of this or because of something else. But I started modding this CapPackage file, and all of a sudden my treo just started acting weird. I had to hard reset it several times throughout the day. Then I upgraded to the 2.25 WM6. And that is where **** really hit the fan (I upgraded and put my own CapPackage version in it). And after that I've had nothing but trouble. Soft resets didn't work anymore, it just crashed on the boot screen. Hard resets work, but really slow, takes about 20min. So now I'm re-upgrading to 2.25 and just leaving that CapPackage file alone for now .
The tale away message: Don mess with this unless you know what you're doing, which isn't me
-Robert

Run SD Cab with autorun.exe

hello
i need to add a username into the registies for a number of devices i'm flashing. Unfortunatly the usernames all need to be different i.e. PDA001, PDA002 and so on...
I've created a number of different cab files each for a different device that will add the username in.
So is it possible to run the cab file off the storage card as part of the hard reset process. i've updated the SD card with the file Username.cab which is the name of all the cab file, then added "CAB: \Storage Card\Extended_ROM\Username.cab" in to config.txt which is in the Extended ROM. i tested it but it didn't work.
Has anyone got any ideas
Or may be have a shortcut to the cab file added into start up. Would that work?

I'd suggest that you instead edit an existing (or relatively insignificant) CAB file (that you'd probably have no use for anyway) with the registry entries/additions so that its guaranteed to be included when you do the Extended ROM customization.
Did you ensure that you copied all the files from an original extended ROM correctly (before making your modifications)?

The thing is I have around 250+ device which need flashing with the same image and as all the devices will require a different Username adding into the registies I 'll need to run an external cab file, a cab file which will be different for all the devices and it's best to run it from the SD card.
I tried to adding a cab file into the Extended ROM which will install a shortcut into the startup folder the shortcut is to the cab file on the storage card. But for some reason it didn't run.
I have a couple of SD cards with an image of my Extended rom on so if anything goes wrong i have the backups.

Whats wrong with having the 'end-user' maually execute the .CAB file?
Why don't you simply customise one PDA (the way you wan't with your preconfigured settings) (minus the user/device name), then do an entire backup using SPB BACKUP (onto a SD Card). You can then restore this image on all 250+ devices (sounds time-consuming,but it really isn't).
All the end user had to do, is to manually execute your .CAB file when they are issued the units.

This is your true answer (in my opinion):
http://www.spbsoftwarehouse.com/products/backup/?en

RE: Whats wrong with having the 'end-user' maually execute the .CAB file?
Basically the devices are used by Market research interviewers who work for us, most of whom are not familier with the devices and are not computer litterate. I'm responsible for a small support team and also the development of the devices. The software we use is already extremley simple and all they need to do is click a buttom "Connect" if the username is not already inserted they get a box "Logon Failed, please check the following details are correct." and a username and password box is displayed and they simply need to type in the id number from the sticker on the back of the pda (like PDA001).
We have just had a large project in feild and over the period we have around 200+ user. Around 50% of the call we took, at some point they had problems entering the username. As much as SPB backup would be of use, if they can't already do a simply thing like type in PDA123, asking them to do this seem like asking alot and would probabily cause more issues.
We already have all the other information in the registries for this application and the username is the only thing which isn't consistant through out.
Do you know if it would be possible to prompt them to run the cab from the sd card which enters the username into the registires on startup?

Nunwood PDA said:
Do you know if it would be possible to prompt them to run the cab from the sd card which enters the username into the registires on startup?
Click to expand...
Click to collapse
Sure it is possible. Did you already try placing a shortcut to the .CAB in "Windows\StartUp" ?. Likewise, you can easily create another script that deletes that shortcut (to ensure that its only used once).
Please keep us posted, on your developments.

Nokia 3650 said:
Sure it is possible. Did you already try placing a shortcut to the .CAB in "Windows\StartUp" ?.
Click to expand...
Click to collapse
Yeah, it didn't do anything. I had a cab file in the extended ROM which placed the shortcut in the dir. \Windows\startup\. For some reason nothing happened, but when I navigate to the .cab file it ran without any problems.
When you say create another scipt, how would I go about doing that? If i had an .exe it could act as a link to the cab on the SD card. i'm not familier with this kind of method. But I think that would solve the problem.
The location of the .cab is: \Storage Card\Help\UserName.cab

Thanks for the exact location. I'm just compiling something for you in visio Studio 2005, that will execute the .CAB file when run at automatically from startup (it'll do this only once).

Simple WM6.1 ROM kitchen

For those of you who want to customize wm6.1, here it a simple ROM kitchen to do so. Beginners, please wait for my GUI release. It is much simpler to use. This isn't that hard, but it takes a little bit of time on your side.
The basics:
All software and regedits are contained in folders called OEM packages. These are in the OEM folder.
All operating system stuff is in the SYS folder. I've also moved the shadow drivers here so you don't have to mess with them.
To make OEM packages:
Download ervius's package creator 5.4 from XDA-developers. Use this to open the cab file to convert into a package.
Copy the OEM package to the OEM folder.
Do NOT delete the OEM packages you don't want. You will choose them later in a different way.
NOTE: You can always download premade OEM packages from XDA-Develoers. There are tons of options.
If you want to make a regedit.
Create a new folder in the OEM folder and convert it into a package using Package Creator 5.4.
Open the RGU file inside with notepad
Edit like following. Note that this isn't the way to comment in regedit files:
Code:
REGEDIT4 <-----Make sure this is always the first line
------Leave one line blank here-------
[HKEY_LOCAL_MACHINE\Software\Example Software\Example Key] <----- Navigate to keys like this
"Example String" = "test" <-------- Write values with quotes. Strings are given with quote after the equal sign.
"Example Directory" = "Windows\\test.jpg" <------ Use \\ to indicate a \ between directories. Otherwise, the ROM build will not work.
"Example Number" = dword: 5000 <----- use dword: to indicate a number or hex value.
<----- You can add more reg entries after the first one. Make sure to specify a different key when needed
-----leave 2 lines at the end of file------
For Sliding Panels:
Leave ROM as it is.
For Neo interface:
Replace Chome folders and bronze folders in SYS folder with the ones attached below.
Select Neo Interface in the buildos step.
Build ROM:
start buildos.bat
when it opens packagetools+buildos, click on the buildos tab.
Click load rom and navigate and select the kitchen folder
Select which oem packages you want and then click Go.
Once it is done, close out.
Sit back and relax for a while so the batch file can build the ROM.
Self-explanatory from here.
Post any questions/problems here.
link: http://www.sendspace.com/file/ap9n8w
NOTES: The inlcuded T-Mobile Edition Package is my beta version. Feel free to build on it. You might also notice the empty placeholder folder for my N33D4SP33D Edition rom that I haven't worked on yet.

To make OEM packages:
Download ervius's package creator 5.4 from XDA-developers. Use this to open the cab file to convert into a package.
Click to expand...
Click to collapse
I found the program but get many errors when I start it up on my computer.. Im currently running Vista Ultimate. I went into control panel and changed the enviroment to emulate WinXP when the program runs and still get many errors..
Is there a vista friendly program out there or alternative available?

I'm running Vista Ultimate too and it works perfectly for me.
Attached is the version I have.

ND4SPD said:
I'm running Vista Ultimate too and it works perfectly for me.
Attached is the version I have.
Click to expand...
Click to collapse
Great! yours works thanks alot now to get my feet wet in all this lol

I got this error
'Error building default.hv and user.hv! (see imto "BuildOsX-log.Txt")
i can't see anything in there. What now. Thanks

Do you mean there's nothing in the BuildOsX-lot.txt? There should be. A few lines from the last, or the last line, there should be the registry file that messed up and on which line it messed up on. The file is given by the GUID, or that long string of numbers and letters that you see.

no, there is nothing what tell me what to do. so what should i do with that error.

i will make stick this thread.Hope next times will see some roms with this kitchen

Thanks tom. I'll make sure to post my GUI kitchen soon to let more people create ROMs a lot easier.

kormanb1123 said:
no, there is nothing what tell me what to do. so what should i do with that error.
Click to expand...
Click to collapse
what kind of things did you modify or add? Maybe I can help based on that.

I get the same error for the following:
InitRegistry FAILED in file ".\Registry\fcbf420c-04fd-478f-bd29-e4ab55973337.rgu" within a few lines of line 359.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\fcbf420c-04fd-478f-bd29-e4ab55973337.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives
Looked through each App in the OEM folder until I found the matching rgu number, which in my case is the HTC DirectShow. Took that out of my ROM build, ran again and it states that it completed.

I think there is a problem with the directshow package. I'll check the registry entries. Until then, I think you might need to go without that.

This may sound like a stupid question, but hear me out. I have used BuildOS in the past for an Apache from PPCGeeks\PPCKitchens. Once the ROM is finished creating in that version it auto prompts to update your device.
After the ROM is done in your version, I then selected the Package Tool tab and pointed it to the "temp" directory and it did it's thing. Now I am at a loss for what to do next. I see a .nb file temp\dump\ROM directory but i don't see a .nbh file. Do I use the NBHTool even though PHOEB is not listed?

ND4SPD said:
I think there is a problem with the directshow package. I'll check the registry entries. Until then, I think you might need to go without that.
Click to expand...
Click to collapse
I'm not too worried about the directshow, I just that maybe the other guy was getting the error for the same reason so figured I would pass on my resolution.

Sorry, I guess I didn't completely read you post. For the HTC Rom Tool, use the exacalibur settings. Those are the exact same as the Juno.

all I have is o4_osxip.nb.exe in the temp folder no nbh is this the right nb. file I use with
htc tool I put exacalibur settings but don't no what to put in firmware contents
do I put o4_osxip.nb.exe in system and none in the ipl spl and splash and 0x800 radio

ok i did this
Build ROM:
start buildos.bat
when it opens packagetools+buildos, click on the buildos tab.
Click load rom and navigate and select the kitchen folder
Select which oem packages you want and then click Go.
Once it is done, close out.
Sit back and relax for a while so the batch file can build the ROM.
ok where is the rom all i have is o4_osxip.nb.exe in the temp

i have no file imgfs-new.bin in the temp all i have is 04_OSXIP.nb.exe and cecompr_nt.dll and CECompressv4.dll
and where would i look for the batch file

Thank you for your works, ND4SPD
but i can not download your kitchen, it says reached the 4G limit.
because i want to know is there any wrong method i used.
My issue is :
when buildimgfs, the total sections can not bigger than 1B200.
when i put too many files into the imgfs file, the buildimgfs will quit without any info.
but the 71M imgfs.bin have about 22000 sections.
do you have issue too ?
Is it because my PC have only 1G RAM, not enough to do the building?

@Hikey: I have that same problem too. It's the way t-mobile packaged the rom. I'm going to try using the dopod rom for the base next. It might be the PC too. I only have 1GB of RAM, maybe it isn't enough.
@kron2:
run buildos
download this zip: http://www.sendspace.com/file/xuhlc5
copy the files from the zip archive to the temp directory.
open up the cmd that's now in the temp directory.
type the following:
Code:
ImgfsFromDump imgfs-old.bin imgfs-new.bin
Sit back and relax. If this finishes without crashing like Hikey said, do this:
Code:
ImgfsToNb imgfs-new.bin 04_OSXIPN.nb os.nb -conservative
Now you can run the htccert program in the main directory of the kitchen to build the rom. When you are done making the nbh, copy it to the RUU folder and run the update utility.

Device Lock still grayed out after following other procedures

Hi!
As I were trying to link up my X1 to my works exchange-server, I was forced to check the "Prompt if device is unused" checkbox. As I was growing more and more irritaded over having to enter the code every time I use the phone, I wanted to get rid of it.
As I was finding posts telling me that this was becaus of the exchange server forcing this checkbox, I deleted the connection to exchange.
But the checkbox is still grayed out. Is there any way without having to hard reset the phone I could fix this?

There is a way to "circumvent" the Exchange policy - albeit temporarily
Similar questions have been asked before, so I managed to locate this solution - in theory, if you're no longer talking to the Exchange server, the undoing of the policy settings should stick (and you'll get your checkbox back)
OK, read THIS post and may all your troubles be little ones....
Hope that helps,
Mark.

There is another one, very similar program which resets the registry key once in a while, so it doesnt bug you anymore.
Stay Unlock 2
If your device doesnt have an english OS, then the prog wont run out of the box, you have to tweak it (the path \Program Files is hardcoded unfortunately). Instructions:
Create the folder "\Program Files"
Go to the program folder on your device (\Programme, \Programmes, \Programmi, ...) and make a copy of the "Zenyee" folder in your newly created "\Program Files" folder
Now go and run the config utility, it will work
What it should look like:
Code:
\
\Application Data
\Documents and Settings
\My Documents
\Programme
\Zenyee (<- original folder)
\Program Files
\Zenyee (<- copied folder, duplicate)
\Windows
etc etc

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