Database Develop

Need tapres.dll from a Windows Mobile 2003 SE Device

Hi i have the problem that i cannot copy the tapres.dll of my MDA Compact to my PC for modify. This has the "pressed" Buttons inside i have found tapres.dll for WM 2003 but i need the one with landscape graphic inside (WM2003 SE).
Can somebody help me to show me a way to copy this file to pc ... when i modify the registry for example tapres2.dll i can't copy the tapres.dll too!
Thx for your help
Snappy

here u go 8)

hmm, think this is not the same one like the one on my device, there is not the image inside like the tapres.dll from a wm2003 device ... perhaps you can show me a way to copy the tapres.dll from my device to my pc i need it in german too.
Thx for your help
Snappy

Snappy said:
hmm, think this is not the same one like the one on my device, there is not the image inside like the tapres.dll from a wm2003 device ... perhaps you can show me a way to copy the tapres.dll from my device to my pc i need it in german too.
Thx for your help
Snappy
Click to expand...
Click to collapse
You cannot copy/move/rename the ROM dlls. What you can do is to go to the ftp.xda-developers.com site, and perform a dumprom from the ROM images available on the site. To download dumprom and FAQ, goto wiki-xda-developers.com site and search for dumprom.
Bear in mind that if you then copy the new tapres.dll into the /Windows folder of your device, it exists as a run-time copy that the device manager will use instead of the original one in your ROM.
However, the new DLL cannot survive a hard-reset, and you must copy it back to the /Windows folder after a hardreset.
Last time, I think some of the drivers for Compact/Mini/JAM are customised for the hardware only. I'm not sure about taperes.dll, but you can try porting and see if it works. Good luck!
Anyway, here the tapres DLLs from a GERMAN ROM.

Thx alot for your help, i have found the graphic in the tapres.96.dll but i have only heard about a way to change the graphic by change the registry to a other dll...

Ok here an information for anybody who wants to create own skins for dialer on MDA3 and MDA Compact with Key Pressed graphic.
- modify the normal graphics with any graphic program
- extract the .ico files from the tapres.96.dll for example with "PE Explorer"
(Icon_Entry: 1 is for Standard and 2 is for Landscape graphic (3 is sqre))
- modify the .ico for example with "axialis icon workshop"
- replace the icon files with "PE Explorer" and save the .dll to a new name like tapres.97.dll
- modify the Registry Key HKEY_CURRENT_USER\ControlPanel\Phone\IcoFil to your filename "tapres.97.dll (original its tapres.dll)
- softreset
Thats all ;-)
Hav fun Snappy

TMO Extended Rom CAB List

Can someone point me to a link of the TMO extended rom cab file list with descriptions for each. i searched i swear
Also, If I updated my rom and wanted to load all these cabs back on to the device can i just copy the whole backup folder to /windows/ and then the autorun will run it on reset?
thanks

search better . . .its on the wiki

the one in the wiki is dutch, is there a USA one?
what about the second part?

1. I know its based on dutch tmo rom, but most of the US cabs are much alike (based on their name)
2. autorun makes use of a registry setting (dont know out of my head, but plz do another search on config.txt and autorun) to load the correct config.txt file.
If you change that you canb use your backup and install from there.

TO: c_shekhar

1. You must be seeing a folder \ExtROM here which has few cabs and tsk files. Place this folder on \Storage Card of your device.
2. You can add the files which you wish to autoinstall after hard reset to this folder. But, dont forget to modify the \Storage Card\ExtROM\Config.txt accordingly.
3. Mark all cab files as read only.
You now have the Extended ROM back on your device but on the storage card this time.... Enjoy.
4. Install PPCPimbackup utility by Dotfred on your existing ROM and backup your SMS using that. And then flash the new ROM.The utility is available in this folder also.
C_shekhar
Click to expand...
Click to collapse
Hi C_shekhar,
I have two questions in upgrading your ROM and the ExtROM
1) How to do this step ->Mark all cab files as read only
2) Can i flash the ROM first, the copy all ExtROM files to the SD card, and then do a Hardreset -> i have done this but seems not work.
Thank you.

you can mark the files read only using a file explorer utility like resco explorer. and as long as u add the appropriate entries to config.txt whenever u hard reset the cabs will get installed.
n btw im sorry im not c_shekhar but i think the answers correct

xPreSiDenT said:
you can mark the files read only using a file explorer utility like resco explorer. and as long as u add the appropriate entries to config.txt whenever u hard reset the cabs will get installed.
n btw im sorry im not c_shekhar but i think the answers correct
Click to expand...
Click to collapse
thank you very much for your quick reply.
now i have reflashed the ROM and the ExtROM works now.
I am wondering why we have to hide the files in the ExtROM folder, as i found all CAB files still there after the installing.
another question: can we hide teh ExtROM folder not the files inside?
Thanks.

yeah sure again that could be done with resco file explorer or something similar... although i dont think hiding is one of the requirements. the only thing required is marking them readonly.

Shift rom kitchen + liberated rom

Hi,
let's keep the rom development topic in here. Here is my romkitchen, from kaiserkitchen 0.3. There is no flash utility, but you can use customruu for that.
The included rom is a base for localisation, or customisation. Click on first step (prepare), make your changes, then click on step 2 (cook). You have a Signed_RUU ready for flashing.
In my experience, it is best to delete the RUU_Signed before creating a new one
Also, the custom ruu will not flash the new rom if you do not change the folder between each flashing on vista. I use a name identation (folder1 then folder2, etc...)
Happy cooking. Please use this to help finding stuff about drivers
Warning: you cannot add or remove from sys folder without doing a greloc. DO it before doing anything. Notge the value, then relaunch it when you added or removed something. Put back previous value then click on go!
http://rapidshare.com/files/142122071/shiftkitchen.rar.html

thank you.
thaihugo said:
Hi,
let's keep the rom development topic in here. Here is my romkitchen, from kaiserkitchen 0.3. There is no flash utility, but you can use customruu for that.
The included rom is a base for localisation, or customisation. Click on first step (prepare), make your changes, then click on step 2 (cook). You have a Signed_RUU ready for flashing.
In my experience, it is best to delete the RUU_Signed before creating a new one
Also, the custom ruu will not flash the new rom if you do not change the folder between each flashing on vista. I use a name identation (folder1 then folder2, etc...)
Happy cooking. Please use this to help finding stuff about drivers
Warning: you cannot add or remove from sys folder without doing a greloc. DO it before doing anything. Notge the value, then relaunch it when you added or removed something. Put back previous value then click on go!
http://rapidshare.com/files/142122071/shiftkitchen.rar.html
Click to expand...
Click to collapse
Hi
Thank you very much.
Ram

Thank you for your hard work and dedication we put it. Best regards

thaihugo said:
Warning: you cannot add or remove from sys folder without doing a greloc. DO it before doing anything. Notge the value, then relaunch it when you added or removed something. Put back previous value then click on go!
http://rapidshare.com/files/142122071/shiftkitchen.rar.html
Click to expand...
Click to collapse
you mean that we have to extract sys folder from RUU_Signed.nbh file... then execute greloc and take note of the value... then copy files in the sys folder like OEMAPPS and OEMDrivers... and when we finish adding files in the sys folder... before we execute cook process and NBHutils we have to run the greloc again and reinsert the previous values... then click doit! in the greloc?

davidgreen said:
you mean that we have to extract sys folder from RUU_Signed.nbh file... then execute greloc and take note of the value... then copy files in the sys folder like OEMAPPS and OEMDrivers... and when we finish adding files in the sys folder... before we execute cook process and NBHutils we have to run the greloc again and reinsert the previous values... then click doit! in the greloc?
Click to expand...
Click to collapse
Make sure you keep your langugage specific folders intact.
Thanks
Ram

G'Reloc Situation
thaihugo said:
Hi,
Warning: you cannot add or remove from sys folder without doing a greloc. DO it before doing anything. Notge the value, then relaunch it when you added or removed something. Put back previous value then click on go!
http://rapidshare.com/files/142122071/shiftkitchen.rar.html
Click to expand...
Click to collapse
Hi thaihugo
My G'Reloc posts the same numbers always before and after, and strangely they are same for kaiser and SnapVUE. Am I doing anything wrong there?
Slot 0: 01F90000
Slot 1: 03DD0000
Size of ROM: 83400000
Unknown: 00000000
These are the numbers I have seen in ImageInfo.txt under .VM folder in SYS
Thanks
Ram

Most of the time, greloc sees the same numbers, but is needed for the few DLL's you have added. So even if you (as me) get the same number everytime, just run it to make sure everything is in place.
If you put say a full sys from another device, you will get slightly different numbers. You will have to put back the value you posted here in that case.
Morality: If you add any dll folder or exe folder in the SYS folder (not a simple dll or exe), do a preventive g'reloc before cooking.

thaihugo said:
Most of the time, greloc sees the same numbers, but is needed for the few DLL's you have added. So even if you (as me) get the same number everytime, just run it to make sure everything is in place.
If you put say a full sys from another device, you will get slightly different numbers. You will have to put back the value you posted here in that case.
Morality: If you add any dll folder or exe folder in the SYS folder (not a simple dll or exe), do a preventive g'reloc before cooking.
Click to expand...
Click to collapse
oh. Thank you
Ram

Help needed...
After all...i decided to cook my own rom...
Read alot , did everything i have read...
"cab oem" ing
"initflashfiles.dat" modification
but when it came to the end , buildos gives an error such as
The target file "temp\dump\mstscax.dll is a directory not a file"
Mind do wake me up for what i am missing ?
Safak

Help #2 for the noob
I have found out the problem about the previous tab... It was about wrong configuration of Remote Desktop...
I have overcome it but came a new one which is
Buildos gives this error
"Error building default.hv and user.hv"
and now , what ?
Help this poor lamer :-(

eh...
I ignored the latest error and have my own rom...and i m now flashing it to my Shift...
Will let yo know whn done...to be honest i m a little nervous about the result...

Urgent Help
I m in deep trouble...
I messed everything and now i m dead...Winmo side does not even boot...tell me what to do...tell me if there is a way to go back ?!?

how about flashing working rom to it?

omg
Recovered....thanks alot for your patience...

Average Joe
Hi guys,
I recently bought a HTC shift which SnapVue came out to be in Chinese, i really need to change the language and liberate it ASAP. I 've read so many replies on many different threads that i'm just completely confused right now. I barely understand all the technical words used out here. I need help please. Thank you.

What is the max size the rom can be?
I'm getting my Shift this week and I'm prepering for it with a cooked rom
EDIT: I saw that UDK's rom was 64mb in size so I know I'm safe if I'm within that limit

gullum said:
What is the max size the rom can be?
I'm getting my Shift this week and I'm prepering for it with a cooked rom
EDIT: I saw that UDK's rom was 64mb in size so I know I'm safe if I'm within that limit
Click to expand...
Click to collapse
Welcome Gullum.
64mb is the limit IMHO. Some NBH files over 50 mb have problems, and I have to reduce them.

thaihugo said:
Welcome Gullum.
64mb is the limit IMHO. Some NBH files over 50 mb have problems, and I have to reduce them.
Click to expand...
Click to collapse
ok first problem now ... I made my first atempt to flash a rom and now snap vue only gives a black screen what to do now?
edit maybe it should be added to first post that to recover from bad cooked flash then just flast the included rom

I now have a working own cooked rom on my shift just need to do some finetuning and I'll upload a rom for everyone to try... next step is to port a newer build.
i'm typing this on my snapvue side of my **** with opera mini
I have added some apps from blakstone and opal
google maps, rsshub, streaming media, calculator skined, thumbcal and some more

gullum said:
I now have a working own cooked rom on my shift just need to do some finetuning and I'll upload a rom for everyone to try... next step is to port a newer build.
i'm typing this on my snapvue side of my **** with opera mini
I have added some apps from blakstone and opal
google maps, rsshub, streaming media, calculator skined, thumbcal and some more
Click to expand...
Click to collapse
Hi
Can't wait. Could you check whether you are able to attach to audio to notes etc.
Thanks
Ram

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