Database Develop

Personalising ROM's... without Ext_ROM

Okay, there a couple of CAB files I install no matter what ROM I use (Total Commander, Today Screen Speed Dial, MortRing [by .exe], Morphy's Call Filter etc), now that I'm getting to grips with the whole ROM building thing I have a question:
How can I add a program installed via a CAB into a ROM so that it is installed into ROM, I've searched on the forum and can't find much. I know it can be done as ROM's such a TuMa's, Logout's and Ivan's have apps in ROM which aren't there by default...
EDIT: In addition, I overwrite some of the default ROM stuff once I've installed (ETEN M600 Dialler in particular), so again, how can I get the 'bits' out the cab and overwrite the default contents of the ROM, this would make my life much easier...
If this has been posted previously then please point me in the right direction

First extract files, shortcuts and registry entries from the .cab using wince cab manager or similar http://www.ocpsoftware.com/, take note on what directory each file/shortcut is in. (often more reg entries will be stored as a file called 'platformxxx.reg' use these too)
Normal rom edit way: add the contents of the exported .reg files to default.rgu, making sure that you leave a blank line on the end, copy all the files to the \dump directory and edit initflashfiles.dat to copy them to the right directory on first boot. (remeber to remove the first two bytes - ff fe with a hex editor). then build your rom!
Bepe's rom edit way: create a folder '[your software name]' in the oem folder and get yourself a guid from here http://kruithof.xs4all.nl/uuid/uuidgen. create a blank file called '[yourguid].dsm and a blank text file called '[yourguid].rgu'. add the contents of the exported .reg files to '[yourguid].rgu' and make sure you save as unicode. then copy all the other files to the folder and create a blank unicode txt file called 'initflashfiles.txt' and use it like initflashfiles.dat in the first method except there is no need to hex edit out the first two bytes. then build your rom!

midget, you're a star, I thought it may be something simple... I'm off out with the family now for the day, but I'll work on this later, cheers!

ROM Editing...Is this correct?? Please READ!!!

I am trying to modify a ROM for my BA with the use of imgfs tools I downloaded from buzzdev.. This is what I did... (hope someone here could comment if this is correct) I have not tried flashing any of my modified ROM coz i dont still have my BA with me, mabe this 3rd week of sept I will have it in my hands!!! LOL
Here's how:
1.) I tried helmi v1.3 (I converted nk.nbf to nk.nba with the use of nba converter)
2.) Prepare_imgfs nk.nba
3.) viewimgfs imgfs_raw_data.bin
4.) modified the dump directory (added the wm5torage, pocketrar, taskmanager v1.4.4)
5.) edit the initflasfiles.dat with the use Notepad (deleted the 2byte signature with the use of ULtraEdit)
6.) I also edit the default.hv with the use of rgucomp (I dont know if i made it correctly) to include the registry entries of WM5torage) (Well I succesfully convert it to rgu, edit it with the use of UltraEdit save it as unicode and I managed to convert it to .hv file successfully without any errors)
7.) Buildimgfs
8.) make_imgfs nk.nba
Is this a correct way of modifying the ROM? If not, how? I read alot of posts here (xda and buzzdev) on how to modify a ROM with use of imgfs tools and this is how I understood it... hehehe
Is the rom i made workable? Thanks hope soomeone here could help me!!! by the way here is the attached rgu and hv file i modified!!

I might suggest trying the Bepe ROM Kitchen.. quite a bit easier

Yeah its easier>>!!
I tried the method you said..But for me this is simplier... So based on your own understanding, is that correct? I know you have done modifying a lot of roms already....
Thanks
So anybody here could give some more opinions>>>Pls

Anyone?
Anyone???

It seems OK the way you did.
I did the same way as you when I used XdaII or Himalaya.
I edited BA ROM this way too.
One thing to tell you is that you will not know that it works or not until you flash it in your device.
The file you add may overload the space if you don't delete some files you don't use.
I delete transcriber because I don't use it and will have about 500 KB for adding some files I want.
Flash it and you will know the answer yourself.
8)

Thanks
Thank vivi.. Yeah I did, i deleted some of the files in the rom (which I donot use at all) to have some space for my additional files... btw, I read about boot.hv (like on the other method) do I need it also in this method? Or is it included in the default.hv?

I left boot.hv in dump folder and didn't touch it.
I edited only default.hv and initflashfiles.dat.
But it is a long time not doing.I nearly forget the steps to do.
I think Helmi ROM is OK and I use it as it is.

OOOH
I dont see any boot.hv in the dump directory? Did i mess somthing?
Yup It seems that Helmi ROMs are great..Thanks again

Autorun.exe Help Required

Can anybody help me with a problem
I want to autoinstall some cab files on a wm5 wizard. (Like tomtom does under wm2003)
Problem WM5 don't want to install!!!
I have used the 2577 folder and the autorun from tomtom, renamed my cabs to the tomtom names (ttn.cab, gps.cab etc) this works fine under wm2003 but will not install on wm5
Does Anybody have a hacked autorun.exe that installs cabs on wm5 or
a Hacked extended rom autorun.exe that reads the config from the storage card instead of the extended rom.
The second option would be better as then all i have to do is re-write the config for different sd-cards
Please Please Please help me all you programmers/hackers/reverse-engineers or whatever you would lke to be known as.
Many thanks in advance

Autorun reads the ini from the /ExtendedRom/ location and that is hardcoded..
I can't be changed because it will render the certificate invallid.
However you can use:
PocketPC Installer ( http://www.pocketpctoolkit.com/index.htm )
It will make an autorun.exe for you (to install cabs registry keys etc etc..)

the-equinoxe said:
Autorun reads the ini from the /ExtendedRom/ location and that is hardcoded..
I can't be changed because it will render the certificate invallid.
However you can use:
PocketPC Installer ( http://www.pocketpctoolkit.com/index.htm )
It will make an autorun.exe for you (to install cabs registry keys etc etc..)
Click to expand...
Click to collapse
Doesn't Autoconfig.exe just reads the Config.txt file from the same directory?
Just change the Config.txt so it fits your needs and I think you will be done.
Only problem is that every app will be installed to Main Storage.
I actually have to know this, but cannot try it right now, my device is flashing one of my test Roms
Molski

molski said:
Doesn't Autoconfig.exe just reads the Config.txt file from the same directory?
Just change the Config.txt so it fits your needs and I think you will be done.
Only problem is that every app will be installed to Main Storage.
I actually have to know this, but cannot try it right now, my device is flashing one of my test Roms
Molski
Click to expand...
Click to collapse
The one from orange (NLD) doesn't. It reads the one in the extended rom.
Have disassebled it with IDA-pro, there I saw the strings pointing to the extended rom.
After patching it I got a certificate error when I tried to run it..

Cooking a rom...

Hi, I followed the thread: "How to reconstruct a dumped ROM"... (obviously I had, before, did a rom dump!). Now I have a directory named "dump" with several subdirs.
In the step 3) there is written: "After this step you can optionally edit the OS files with the proper tools"... now the question is: what are these proper tools? I searched in the forum, in the other threads but I didn't find anything... My needs are: to delete some programs that are in the rom (for example Pocket Word, Pocket Excel, other..) in order to obtain more space, but to install other tools at the free space.
Thanks in advance for your help....

Great question ! i can't help you , but i wait for answers ....

I asked the same thing the other day, and got an answer(thx again to him).
Actually, I'm doing it right now, as a test I've successfuly dumped and rebuilt lsvw's rom using enhanced imgfs tools batch files, nbdump.bat nbname.nb & nbbuild nbname.nb, now I'm removing files from the rom and maybe add some other, like that quick gps thingy, latest msn(optimized for trinity, removed vga resources), phone pad, and some other thing on my custom extrom.
I had the same doubt as you, but it seems that we're overcomplicating things, you can simply use the file explorer to remove files from that dir, beware of which files you remove/alter.. initflashfiles.dat has some operations to be done after flashing the device(creating folders,renaming files, moving them to startup/start menu/etc folders), I thought that if the file didn't exist on the windows folder, whatever invoques initflashfiles.dat would crash, but it doesn't seem to be the case, I haven't put this to test, but I've found several missing files on the initflashfiles.dat(and a typo, "floder", go figure what it means - lazy/rushed editing IMO), so there seems to be some tolerance to the operations contained in that file.
I won't edit the wiki until I'm 100% sure that what I know is correct, but to sum it up:
dump the files
add/delete files with explorer
edit the registry using rgucomp
edit initflashfiles.dat using the original windows notepad & use an hexeditor to remove the 1st 2 bytes
run NBBuild.bat to create the *.nb file
OSchecker.exe to validate the *.nb file
nbhtool.exe to create the nbh
flash it(I prefer the sd card method)
Code:
rgucomp needs setting _FLATRELEASEDIR environment variable to current directlry like this:
set _FLATRELEASEDIR=.
Dump default.hv/user.hv file to .reg with:
rgucomp.exe -nologo -o default.hv > default.reg, then add line "REGEDIT4" to the beginning of REG file.
Modify the .reg file to your liking, (save it in UTF-16 with CR+LF terminations and a new line at the end of the file) and convert it back to .hv
And don't forget to flash Olipro's Hard SPL before, it may save your device.
"and convert it back to .hv"
http://forum.xda-developers.com/showpost.php?p=1186635&postcount=1
(no wonder I didn't find this info, forum search is almost useless, googled for rgucomp and voilà, first result(above) right answer)

[01 DEC 09] TUTORIAL: How I cook ROMs for XPERIA + all my kitchens, tips and tricks

.
TUTORIAL:
HOW I COOK ROMs for the XPERIA X1
A complete, step by step GUIDE
[01 DEC 09]: SEX1 R5 pure ROM KITCHEN UP FOR DOWNLOAD at the ROM thread​
PS1 My ROMs are NOT intentionally protected: feel free to dump and use any components you please
PS2 Don't be shy: ASK !! but don't be dumb: SEARCH !!
INTRODUCTION​
Glad to see everybody is trying to cook these days: we are all here to learn and share
Following xda-devs spirit, I am writting this little guide to help those who could be intrested in cooking their own ROMs
Don't be shy: If I did it, YES YOU CAN do it too !!
Let's get real: NO COOKED ROM WILL 100% FULLFILL YOUR NEEDS/EXPECTATIONS BECAUSE WE ARE ALL DIFFERENT
Let's get real again: THE ONLY WAY TO STOP COMPLAINTING ABOUT "this" OR "that", FLAMING A CHEFF'S TREAD, IS BY DISCOVERING HOW HARD AND COMPLICATED THE PROCESS IS, but don't dismay: this thread is meant to guide you step by step into the cooking world
I have been reading and learning a lot, trying to build something that would suite MY OWN NEEDS, I have been using my ROMs for quite a while and I am happy and satisfied: I show off my phone and I can proudly say "I did it myself"
So I invite all of you to give it a try too: it's worth the experience
But first, may I invite you to take a look at some works:
Link to latest SEX1 R5 -release 5- ROM thread (kitchen and complete cooking log at post 3)
Link to DEUTSCH SEX1 ROM + KUCHEN thread
Link to LATIN SEX1 ROM + COCINA thread
Link to SEX1 R4 public beta testing thread
Link to SEX1 R3 -release 3- PURE, BareBone & XPERT ROMs thread
Link to SEX1 R3 public beta testing thread
Link to SEX1 release 1a ROM thread
STEP 1: BASIC REGISTRY SKILLS​
Every good cooker/cheff needs basic REGISTRY skills
As a good reading/searching-needed noob, I have compiled some knowledge and here are my 2 cents:
BASICS
1- Registry keys can be generated (created) or changed with a RGU file (unicode format) or XML/PROVXML file (UTF-8 format)
Both can be edited with notepad, but make sure you choose the right format when saving
(use "save as": it will let you choose format)
Differences:
- UTF-8 for XML or unicode for RGU
- dword values must be hexadecimal in RGUs and decimal in XMLs
- RGUs store registry keys only, XMLs store registry keys, file operations, etc
2- A PROVXML file is a glorified XML: it loads automatically when cold-booting the device (hard reset or first boot), which means all of it's instructions, file operations & registry keys will be auto-executed and will override similar instruction from RGUs
In the other hand, XMLs have to be invoked ("runned") during customization (usually from OEM\Operatorpkg\config*.txt)
ORDER OF IMPORTANCE
1- When cooking the ROM, all RGU files are compiled and gathered to create the main, barebone system registry (see Jack's comment some posts down)
2- After flashing the phone, when the ROM is loaded for the first time (when it takes forever to boot = "cold boot", same as after a hard-reset), all commands inside all PROVXMLs are auto-executed, overriding corresponding registry keys from REG/RGU files
3- After the "set date" and "align" screen, the auto-customization process starts:
Anything inside "config.txt" will be autoexecuted (apply themes, install CABs, run XMLs...)
Here is where I execute my customization XMLs and any required OEM customization XML
Here is an example "config.txt":
Code:
LOCK:Enabled
CAB: \WINDOWS\ActiveX_Deployment_signed.CAB
CAB: \WINDOWS\WM6.1_PPC_dawn_Opera_15969_signed.cab
CAB: \WINDOWS\gtrab_SEX1_Customization.CAB
XML: \WINDOWS\SEX1_fileoperations.xml
XML: \WINDOWS\My_panelconfig.xml
TSK: \WINDOWS\Naked_chiks.TSK
LOCK:Disabled
RST: Reset
- As a side note, "config.txt" usually goes inside OEM\OperatorPkg, and runcc.lua governs which files are auto-launched
- I put most of the big CABs inside OEM\PACKAGES, eg. PACKAGE_Kovsky_ActiveX_Deployment
- I put the small or orphan CABs into OEM\OperatorPkg, together with my XML files, to keep them handy and keep them in mind at a glance towards the customization files
Conclusion: Better put all of your important registry tweaks in XML or PROVXML files instead of searching for a specific registry key inside more than one hundred RGUs, anyway they will be overrided by any XML or PROVXML instruction pointing to that same registry key
COOKING IMPLICATIONS
1- If required, each OEM or SYS PACKAGE has its own RGU file and/or PROVXML files
Some PACKAGES don't need registry settings, so they don't have an RGU inside
2- The RGU name must be THE SAME as the PACKAGE identifier DSM file
3- Only ONE RGU file is allowed per PACKAGE, but each PACKAGE can contain as many PROVXMLs as required
4- PROVXMLs are a very useful tool because we can add lots of customized instructions to our ROMs ("move this file", "delete that file", "rename this one", "remove Hidden attributes", etc)
5- I prefer to edit the "stock" PROVXMLs instead of creating new ones: a single format error will make the whole XML unusable and the customization process will omit it
SAMPLE RGU FILE
BASIC RGU / REG RULES:
- First line must say "REGEDIT 4" (don't ask me why )
- Anything apres a ";" is just a comment and won't be processed
- Last line must be empty (again don't ask me why )
Code:
REGEDIT4
; this line has a semicolon, so it will not be processed
; gtrab SEX1 registry tricks compilation
; google rulez: those who search shall find !!
; DISABLE SECURITY WARNINGS
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000101a"=dword:00000001
; VIBRATE AND RING
[HKEY_CURRENT_USER\ControlPanel\Sounds\RingTone0]
"Script"="av0pw3r"
"Sound"="\\Windows\\Rings\\Sony Ericsson.mp3"
"Category"="Ring"
; HIDE SIM CONTACTS
[HKEY_CURRENT_USER\ControlPanel\Phone]
"ShowSIM"=dword:00000000
; DISABLE AUTO WORD SUGGESTION
[HKEY_CURRENT_USER\ControlPanel\Sip]
"SuggAutoCorr"=dword:00000000
"SuggWords"=dword:00000000
; ENABLE SCREEN TAP SOFT SOUND
[HKEY_CURRENT_USER\ControlPanel\Volume]
"Screen"=dword:00000001
; DISABLE AUTO DIM / AUTO TURN OFF SCREEN
[HKEY_CURRENT_USER\ControlPanel\BackLight]
"BatteryTimeout"=dword:00000000
"ACTimeout"=dword:00000000
"LightDetectOn"=dword:00000000
; DISABLE AUTO TURN OFF DEVICE
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts]
"ACSuspendTimeout"=dword:00000000
"BattSuspendTimeout"=dword:00000000
; ENABLE TOUCHFLO SCROLL SOUND
[HKEY_LOCAL_MACHINE\Software\OEM\TFLOSettings]
"EnableSound"=dword:00000001
; MIC AGC ON
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\AdvancedCPL]
"MicrophoneAGC"=dword:00000001
; IMPROVE BT A2DP SOUND QUALITY
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\A2DP\Settings]
"MaxSupportedBitPool"=dword:00000028
"BitPool"=dword:00000028
"UseJointStereo"=dword:00000000
; BT DEFAULT DEVICE NAME
[HKEY_CURRENT_USER\Software\Microsoft\Bluetooth\Settings]
"LocalName"="SEX1"
; WM6.5 PATCH - TASKBAR BATT ICON CLICK OPENS POWER SETTINGS
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\TaskBar]
"LimitedClock"=dword:00000001
"ConsistentClockOrBattery"=dword:00000000
; SCROLLBAR SLIGHTLY THICKER
[HKEY_LOCAL_MACHINE\System\GWE]
"cyHScr"=dword:0000000f ; Hex f = Dec 15, standard value was Dec 13
"cxVScr"=dword:0000000f ; Hex f = Dec 15, standard value was Dec 13
"cyVScr"=dword:00000015 ; Hex 15 = Dec 20, untouched standard value
"cxHScr"=dword:00000015 ; Hex 15 = Dec 20, untouched standard value
; DISABLE SMS WAKE UP
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"DisableSMSWakeUpEvent"=dword:00000001
; EMAIL LED ILLUMINATION ON
[HKEY_LOCAL_MACHINE\Software\Drivers\illumination\27]
"Enable"=dword:00000001
; USE LARGE KEYS FOR SIP KEYBOARD
[HKEY_CLASSES_ROOT\CLSID\{42429667-ae04-11d0-a4f8-00aa00a749b9}]
"KBMode"=dword:00000000
Again: DON'T FORGET to leave the last line empty !!!
XML / PROVXML SAMPLE
Check this *.PROVXML file guys, I edited it to rename my SEX1_stwater*.png custom backgrounds to stwater*.png (thus making them the "default" backgrounds after the flash)
Also, there's a registry change example included in this sample XML:
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKCU\Software\Microsoft\Today">
<parm name="Skin" value="\Windows\Classic Blue.tsk" datatype="string"/>
<parm name="UseStartImage" value="1" datatype="integer"/>
<parm name="DPI" value="192" datatype="integer"/>
<parm name="MultiColorThemeEnabled" value="1" datatype="integer"/>
</characteristic>
</characteristic>
<characteristic type="FileOperation">
<characteristic type="%CE2%" translation="install">
<characteristic type="stwater_480_800.jpg" translation="install">
<characteristic type="Copy">
<parm name="Source" value="%CE2%\SEX1_stwater_480_800.jpg" translation="install" />
</characteristic>
</characteristic>
<characteristic type="stwater_800_480.jpg" translation="install">
<characteristic type="Copy">
<parm name="Source" value="%CE2%\SEX1_stwater_800_480.jpg" translation="install" />
</characteristic>
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>
Continued...

STEP 2: THE KITCHEN​
[01 JUL 09] Uploaded the kitchen I used to cook my SEX1 R3.61 XPERT ROM​Improvements: 1- During cooking process, it will let you choose between LZX or XPR compression without having to change any files (now it uses th "mythical" universal cecompr.dll ) 2- Before closing, it pauses to let you explore or copy temp files 3- Smaller in size and super FAST: cook a 100 MB ROM in one minute (using XPR)
[01 JUN 09] SEX1 KITCHEN, more simple, small & easy to use. Download at post footer
[01 JUN 09] COCINA SEX1 con ejecutable ('script') en español, más sencilla, pequeña y fácil de usar. Descarga al pie de este post
BASICS
Every Kitchen requires Microsoft Visual Basic redistributable & Microsoft .NET Frameworks 3.5 to run
Download here: http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&DisplayLang=en
Some Kitchens must to be placed in the root directory C:\
The SEX1 kitchen can be placed anywhere in your PC, even in your desktop if you wish
INTRODUCTION
A "kitchen" is a compilation of tools, some are optional and some required to cook a ROM
The SEX1 Kitchen has the minnimum required tools only, making it smaller
Some users have written SCRIPTS to automate the cooking process and make things easier, so even I can cook
The script guides you instead of manually launching every required app in the correct order
Just click "Cook.bat" "kovskykitchen.bat" or "buildNB.bat" (it depens on which kitchen you are using) and the automated script will do the rest
This SEX1 Kitchen is a modified derivant from Bepe's old Kitchen structure with updated tools, and in this case I wrote the script for the automated process myself
Erviu's Visual kitchen is a more modern, UI-oriented alternative, but by the time being I will focus on the structure and some basic concepts for this classic ole' style kitchen from Bepe because Visual Kitchen uses a dfferent folder structure
STRUCTURE
Inside the Kitchen you will find 4 folders and the Kitchen's batch script:
BATCH SCRIPT:
- When finished populating OEM, SYS and ROM (XIP) folders with your desired OEM packages and CE|OS build choice, double click the batch script to start cooking and have a smoke or a coffee while it finishes (this Kitchen is unattended, it takes around 2 minutes to auto-cook a 100 MB ROM with standard compression)
For the english Kitchen: double click "Cook.bat"
Para la Cocina en español: doble click "Cocinar.bat"
- The batch script can be edited with notepad
I inserted some REMARKS ("REM") inside the script:
1- First one if you want to include a pause in the right place to manually edit file attributes before cooking the ROM
2- Another one in case you want to Hex-edit "imgfs.bin" to manually change compression from stock WRX to new LZX
NOTICE 1: LZX compression can be used in this Kitchen by populating the \ROM\ folder with a LZX compression enabled "os.nb.payload" or by editing the new "imgfs.bin" during the cooking process
NOTICE 2: LZX uses a different compressor DLL, it can be downloaded at post footer and relaced in \tools\ folder
KITCHEN FOLDERS:
- The \Tools\ folder is the "oven": it contains all the required tools to cook the ROM
I added step by step explanations into the script, so you can check it to see what happens and which apps are called, to better understand the cooking process: It's worth taking a look
We should be grateful with bepe, bot, ervius, MrVanx, OM-BY, blasphemer, udk and many others for these amazing tools
One year ago the process was SO TEDIOUS and HARD... now it is a matter of clicks !!
- The other 3 folders, OEM SYS & ROM, are where the future ROM parts must be placed:
Download the Kitchen first, then populate these folders with your desired recipee
- Where to get OEM, SYS and ROM (XIP) contents from ??
Use mines (from this tutorial), or dumped ones, or from other users who have shared them
There are many many available around the subforum, just do your homework and search
NOTICE 1: SYS packages must be 192 dpi 480 x 800 resolution !!
NOTICE 2: ROM (XIP) with os.nb.payload must come from a XPERIA, otherwise it must have been ported for the XPERIA
NOTICE 3: If you plan to use a ROM (XIP) folder from jerpelea or my newer "SEX1 release 3", the proper compressor DLL must be downloaded and replaced at "/tools/" folder (the ROM compression selection lyes inside "os.nb.payload")
After populating these folders, your future ROM is basically already there, dismantled into the 3 folders:
- ROM folder is the core
CE build version is here, in "xip.bin" (in some kitchens like this one, "xip.bin" is already inside "os.nb.payload")
- SYS folder contains all Microsoft Operatin System shizzz (media player, Titanium, bootscreen, backgrounds, themes, calendar... etc)
OS build version is here, in \OS\ folder
- OEM folder contains Sony or HTC customizations (Dialer skin, Xperia Panels, TouchFlo...)
OEM version (customization) is here, in \OEMVersion\ and \OperatorPkg\ folders
- In most kitchens your new cooked ROM will "appear" in the RUU folder, which contains a "Rom Update Utility" app required to flash your fresh new custom smokin' cooked ROM to the phone
In the SEX1 Kitchen the new cooked ROM will "appear" in the root kitchen folder, renamed to kovsimg.nbh, ready to be flashed with the microSD method (safer IMHO)
Of course it can be renamed to RUU_signd.nbh and USB-flashed from the PC with the RUU app too
OPTIONAL TOOLS FOR THE SEX1 KITCHEN
Along with the Kitchen, I have uploaded some very useful tools to this post
They are not required but some people could find them usefull and can be optionaly added to the kitchen:
(I wrote and included instructions for each tool inside the ZIP)
xvi-32 Hex Editor -> useful to hex-edit files (I Hex-edit my ROMs to change the ROM initial date, tutorial @ post 90)
Page Pool changer by OM-BY -> Changes the ROM page pool size (some say 0 is better, others prefer 8MB or even 16MB. I use 0=auto)
SYS version by MRVanx -> Gives the real version of every package in SYS folder (don't be surprised: all SYSs floating around are hybrids somehow)
RUU ROM Update Utility 3.22.4.3 for Xperia X1 -> To flash ROMs from the PC
LZX compression: To make the SEX1 Kitchen COMPATIBLE with LZX-compressed ROM/XIPs, just replace the CE compressor DLL in \TOOLS\ folder with the one posted below
Continued...

STEP 3: The OEM folder, HERE'S WHERE WE'RE GONNA PLAY !!​
Downloads
Download OEM, ROM & SYS folders (OEM base: R3AA010 WWE) (XIP|SYS 21815) here from SEX1 R3.61 XPERT [01 JUL 09]
Download OEM folder (base: R2A+R3A "beta" WWE) here from W4X.23 [01 MAY 09]
NOTICE: All OEM folders and PACKAGEs I use are optimized for Bepe's old style Kitchen
Change Log of my OEM packages
release 3 OEM change log:
I dumped R3AA010 UK ROM -> deleted unnecessary OEM packages and streamlined others into \OperatorPkg ("AAinfo.txt", "runcc.lua", operators config "Provision.zip", etc), but kept \ExtendedPkg,
then I:
- Edited OEM\OEMDrivers RGU to:
enable XPERIA start up anime from cold boot (keys were originally added during customizaton in "fileoperations.xml"),
disable SMS sent notification pop up ("NoSMSsentmsg" value 0 -> 1)
disable reg keys for Auto Error Reporting's fatalerror DLL
- Edited OEM\ExtendedPkg\"fileoperations.xml" to:
remove the Bond trailer link inside
- Deleted "fatalerror.dll" in OEM\OEMDrivers
- Deleted "Bond trailer.mp4" and Handango store link in OEM\ExtendedPkg
- Added PACKAGE SD tune UP by tnyynt
- Added my multi-PACKAGE MS SDK certificates + registry lock OFF + CAB insallation warnings disabled
W4X.23 OEM change log:
I dumped XPERIA R2A ROM & downloaded R3A beta OEM packages @ cheffs develop and share centre thread,
then I:
- Deleted unnecessary OEM folders, gathered all XPERIA SEMC contents (from \ExtendedPkg) into two CABs, put them inside \OperatorPkg and edited "config*.txt" to invoke that CABs during customization
- Wrote XMLs for SEMC file operations and edited "config*.txt" to invoke those XMLs during customization (after my SEMC CABs installations, otherwise files wouldn't be found !!)
- Deleted Bejeweled, Sudoku and other unused packages
- Replaced R2A "kovsky" packages with R3A beta packages
- Added PACKAGE for Xtrakt game
- Added PACKAGE for other Panels (Growing panel, Facebook panel, etc)
- Edited OEM\OperatorPkg\"panelconfig.xml" accordingly to the new panels I added, and in my desired panel slot order
OEM - PACKAGES TUTORIAL
Inside SYS and OEM folders we will find PACKAGES
- A PACKAGE contains an app or util or configuration or else
- A PACKAGE is a group of files that do something: There's a PACKAGE for Adobe reader, another one for OEMDrivers, Dialer, VideoTelephony, GoogleMaps, etc
- Basically speaking, this is what we call "cook": to REMOVE or ADD PACKAGES to a recipe and customize the ROM with apps and utils or tweaks
MORE EASYER ?? Bepe's ole style kitchen uses bepe's BuilOS 0.91 utility to control which PACKAGES are included or not in the new ROM, without having to delete PACKAGES folders every time
You need to create a "option.xml" file inside each PACKAGE for the BuildOS to display it in the list of available, selectable PACKAGES
If a PACKAGE doesn't contain "option.xml" BuildOS will assume it must be cooked, by default
How to create "option.xml" ?? It can be manually created, or automatically created with ervius' package creator
HOW ARE FILES ARANGED ??
- Most files in a ROM (inside OEM or SYS PACKAGES folders) are "normal" files
- But some special "system" files have been disasembled in "Modules"
Eg.: If you search for "shellres.dll" you will not find it, but you will find a folder called "shellres.dll" with *.bin, *.txt and some S000, S001, S002 etc files inside: This is "shellres.dll", but disasembled into "modules"
"recmod.exe" converts Files <-> modules
Dissasembled files are re-assembled when the ROM is flashed
EVERY FILE inside all OEM and SYS PACKAGES will go to \Windows unless stated different​
How to tell a file not to go to \Windows ??
Read fards' explanation on post 12 from this thread Initflashes.dat governs what folders are created and which files are moved
Another way to move files is using ye ole *.PROVXML files with proper instructions (I suggest you to open and study some of the stock *.PROVXML files to understand the basic syntax, it's very easy once you have seen a couple of them)
SELECTING ROM CONTENTS
Each package is an app or utility or program or set of customizations, you can add or remove at will, replace a "KOVSKY" app for a "RHODIUM" or "BLACKSTONE" one, but beware: some apps require others !!! Example: If I delete "PACKAGE_Kovsky_PhoneCanvas_VT" (which i the XPERIA phone dialer) and replace it for another dialer skin, I should also delete (or replace) "PACKAGE_Kovsky_VideoTelephony" (It wouldn't make sense to mix up the skins)
Don't worry, this is basic common sense thing, but of course requires a standard trial and error learning curve​
CUSTOMIZING / TWEAKING THE ROM
Most of the more important user-related registry keys are inside OEM folder packages
As I stated before, registry changes can be made "inside" every RGU or, as Itje suggested, better put 'em on a PROVXML file, so the "basic" structure of the ROM is not altered next time you want to cook a different ROM and you don't want that change again
TIPS
- Build your mental "structure" of what you want in your ROM
- Start with basic packages cook the ROM and flash it, if it boots and workss, continue tweakin' / moddin'
- Make "maybe yes/maybe not" apps or utils (packages) OPTIONAL in BuildOS with Ervius Package Creator
(The file "option.xml" will not be cooked the ROM, it is there ONLY to tell the kitchen "this is an optional package and the cheff is going to decide wether to select it or not while cooking")
- Avoid LOTS of wasted time by following this advice from a somnolent beginner: KEEP TRACK OF EVERYTHING YOU DO -> WRITE AND MAINTAIN A CHANGE LOG !!!
Who knows ?? Maybe next day you won't remember "which" RGU you edited late last night, or even worst: "what da heck" you tweaked, or "what for"
- Some programs can not be added as packages because some of their files may have repeated names with other packages:
THE KITCHEN WILL STOP COOKING AND WARN FOR A "REPEATED" FILE
(the ROM can't flash 2 files with the same name to \Windows - remember everything goes into \Windows folder during first boot !!)
CABs are very usefull in this case, but beware:
CABs WILL NOT "auto-install", you have to "invoke" them during the CUSTOMIZATION PROCESS, usually adding a line into a "config*.txt"
I chose to drop some CABs inside "OperatoPkg" (again: to keep an eye on them), and kept "stock" PACKAGES for other CABs (check Xtrakt or Opera packages as an example, and open the config*.txt files to see how these CABs are "invoked" to install during first boot customization process)
SOME PACKAGES
Attached to this post footer you will find a OEM PACKAGE I prepared, meant to add the XPERIA boot start up animation to any ROM (my OEMs all have the animation enabled by default)
BatteEnhancer will include Ethermind's 1% battery driver for XPERIA with required registry changes
SDK+CAB-REG will install SDK certificates (SDKcerts), disable the "non-signed" warnings when installing CABs and turn registry security off (to be edited with any reg editor)
SD tune UP from tnyynt will make your SD card read/write faster
.NET Frameworks (.NET CF) version 3.7
Continued...

STEP 4: THE XIP AND SYS FOLDERS FROM MY ROMS​
Downloads
Download ROM (XIP) folder OS build 21806 here from SEX1 release 3
Download SYS folder CE build 21806 here from SEX1 release 3
Download ROM (XIP) folder OS build 21500 here from W4X.23 (source: jerpelea's kitchen)
Download SYS folder CE build 21500 here from W4X.23
Some changes I often make inside SYS folder
- SYS\Base_DPI_192\: Customize "StartMenu_Selection.png" (honeycomb background for selected item)
- SYS\Base_dpi_192_resh_480_resv_800\: Customize "stwater*.jpg" (XPERIA silver theme aluminum background)
- SYS\Redist_dpi_192_resh_480_resv_800\: Customize "welcomehead.192.png" (WM6.5 orange bootscreen says "SEX1")
Applying Halsted's principles to the cooking process, better avoid making changes inside the SYS folder,
instead, now I run my personalizations during the customization process (remember "\OEM\OperatorPkg\config*.txt" ?? Yey !! there, using some XMLs and CABs !!)
HOW TO CHANGE / UPGRADE AND PORT XIP | SYS GUIDE​
- XIP (CE build version) and SYS (OS build version) can be upgraded separatedly, which means you can have a "21500|21806" build or whatever
- Language and resolution can be changed without having to port
To upgrade SYS build version:
Replace folders inside SYS with newer build ones
Done
- Beware !! don't change ".VM" and "WinCENLS_WWE" folders, they are device specific
- The Kitchen's automated "G'reloc" will do the rest of the dirty work during cooking (reallocating modules in ROM memory)
- Wanna find out what SYS version each folder is ?? Use SYS version by MRVanx
To upgrade XIP build version:
Insert the new "xip.bin" into "os.nb.payload"
Easy, ain't ??
- Beware !! "xip.bin" is device specific
- If a "xip.bin" containing the desired OS build is not available for the device, it can be ported from any "xip.bin" (from other HTC device), then it can be inserted into the native "os.nb.payload"
- MORE INFO on how to extract "xip.bin" from "os.nb.payload", how to port "xip.bin" and how to insert the new "xip.bin" into payload: go to page 11, post 106
To change ROM resolution:
Let's say you just put your hands on a newer SYS build, but it is QVGA (XPERIA is WVGA):
All SYS folders labeled "resh_240_resv_320" should be replaced with "resh_480_resv_800" WVGA resolution folders
That's it !!
- TIP: It doesn't matter if correct res folders are taken from a previous build
- Syntax Note: "resolution horizontal 240 x resolution vertical 320"... get it ??
To change ROM language:
Let's say you want to convert the ROM to spanish language:
Dump a Spanish OEM and add folders to OEM (at least the basic OEM ones)
Replace all "Lang_0409" (WWEnglish) folders in SYS with "Lang_0c0a" (spanish) folders
Edit ROM\XIP\ RGU: change MUI locale lang from 0409 to 0c0a
Piece of cake
- Beware !! ".VM" and "WinCENLS_WWE" folders are device & language specific
- TIP: When editing the RGU, search strings for "lang" or "0409" & you will know what to change
HOMEWORK: I WANNA SEE YOUR NEWER BUILDS XIP | SYS PORTS POSTED, STRAIGHT AND RUNNING GUYS !! ​
KEEP READING THE THREAD GUYS, you can find more useful info and tips from Xperianced senior cookers !!
.

gtrab said:
1- When cooking the ROM, all *.RGU files are compiled and gathered to create the main, barebone system registry
Click to expand...
Click to collapse
Actually, all the rgu files will be compiled into user.hv (anything under HKCU) and default.hv(anything other than HKCU) first. Therefore, it's the final place to check the registry outcome if you have lots of RGUs and the content are overlapped.
Good job and keep up the good work.

Thanks for pointing out jack
Your help and tips are greatly appreciated, as much as your ROM works
.

Very nice thanks! This can be very usefull for our n00b cookers! Maybe I will try it sometime!

Thanks alot. This is a very good information for newbies like me.. Going to start and cooking later

Wow, thanks A LOT for that!
This was really needed... off to cooking

Thanks a Lot !!! You're really a GOOD MAN !

Great, that's really great and gives us a view inside the things behind the ROM

well researched however you've missed a couple of things..
initflashes.dat is editable using notepad and is used to set up files that you'd rather not access from windows. it is used to copy files from windows to the folders they need to be in, such as program files.
Every file you put into the rom will be in windows folder.
it's best if you reduce the amount of provxmls whenever you can, as well as the DSM files (one reason to use Bepes latest kitchen as it doesn't leave them in the rom),
the less files in windows the better if you want more speed.

great tutorial. thanks again.
I have downloaded the OEM package and tried. Everything works.
I have question:
Do you know how to turn off the notification stuff on the title bar? Every time when I press the task manager icon, I either hit the battery or the speaker volume icon, therefore these notifications pops up. I want to make the battery and speaker icon non-touchable.

kluks said:
great tutorial. thanks again.
I have downloaded the OEM package and tried. Everything works.
I have question:
Do you know how to turn off the notification stuff on the title bar? Every time when I press the task manager icon, I either hit the battery or the speaker volume icon, therefore these notifications pops up. I want to make the battery and speaker icon non-touchable.
Click to expand...
Click to collapse
I know how to disable the battery icon click -> power app in WM6.5:
undo the "click battery opens power control panel" REG trick
(batery icon tap response comes disabled by default... waiting for the NEW POWERDRIVER surprise )
@FARDS:
MANY TAHNKS: GOOD POINT,
Will quote your text in front page

you can also use runcc (with mortscript) to trigger Sdautorun on your Sd card.
http://forum.xda-developers.com/showthread.php?p=3613983#post3613983
Runcc looks like it's going to be more important in future..

great tut so far.

XIP and SYS folders uploaded
SYS changes explained
more details added to Step 1 and 2

great work man! you are the man!

Awesome! Thank you so much! I really want a 6.5 ROM with rhodium dialer, rhodium youtube, and rhodium album. I have been wanting to cook a 6.5 ROM but could not get through it so far. Hopefully I will be able to accomplish this now. Looking forward to the rest of your guide and your kitchen. Perhaps I can apply the knowledge you have already given to jerplea's kitchen though.
The option.xml info was much needed. I was so confused as to why when I added packages to the OEM folder they would not show up in build OS.
Thanks again!

If you cook many diffrent roms (multilang etc):
Make provxml files with your regsettings/tweaks/hacks or w/e, and run them in customization..so that when you swap with newer builds with your packages, you wont have to go through the rgu/reg files to make the changes everytime..
you just bring the provxml to next kitchen...in that way you always are sure to have your fav settings with you
Ofcourse...they might need update from time to time..and the settings in a 6.1 rom might not work on a 6.5 rom... and vice versa
cheers