Database Develop

Kaiser Splash Screen Repository [Pictures & Files]

Splash Screen (Boot) File Repository.
I Thought I would start a thread for the splash screens that people are using or those that people have designed for others.
Essentials for creating the splash screens are:
An art program to create the picture that you want, please make sure that your image is 240x320 pixels 24bit colour depth and save it as a .bmp
Follow the instructions in this post by pof (not exactly clear on the HTC rom tool section, just pick anything for the fields in the program and load the correct splash.nbh file by clicking the ... to the right of the splash1 field)
Here are a couple of pictures of some splash screens to get started with.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Put one of these files in the same directory as KaiserCustomRUUv1 and then run the program it will ask you questions make sure you answer yes to them all and then patch the phone. Once done it will automatically reboot your phone and show you the new splash screen.
Russ
Please make sure you edit your original post to add more pictures & files to save having lots of pages per person.

Is this for the first screen where it says 'smart mobility' or is for the animated HTC screen? If the latter, how do you make (which format) & upload an animated one?

I have no idea on the animated one but I am only guessing when I say that its the smart mobility one at the very beginning when you power on the phone on.
As for the animated one if it is the windows start-up then that is a 320x320 pixel 24 bit .png file called welcomehead.96.png on my T-Mobile UK phone so I would suggest starting there in your search for replacing the animated one (if its a .gif then you are ok).
Russ

Thanks mate!!
Awesome stuff
Here's my appreciation in the form of some Anime fan service shots
If I knock up any more I'll share them

There are also some animated ones in this thread.

my theme
great!
Post your splash

I like the easy way.
Just make your picture 240x320, save as welcomehead.96.png and copy to \windows\ on the Kaiser.
Bob's your Uncle.

I've always liked this one, it goes well with the Stock ROM's HTC logo when booting into Black. I believe that the welcomehead png's need to be 320 x320 to cover things when booting in landscape. These welcomehead splashes are so easy to just drop into the windows directory, no rom burning needed, getting the original file's read only attribute turned off is the only hurdle. I used resco file explorer to do it.

Due to the limitation of 4 images per post I guess we are going to have to make more posts per person.
Here are a couple of windows based ones I made. I actually have the carbon one on mine at the moment and it looks alot better on the device.
The animated gif does not work on my t-mobile even adding the registry key of hklm/software/htc/startupanimation/giffile and pointing it to the relevant named file so I guess thats only for those who have changed their roms (unless your on t-mobile rom and its working please correct me if i'm wrong)
Russ
at&t_deathstar.jpg created by RemE

A little contribution for the third splash screen...
Here is my work :
All in .png format, 240x320 pix, rename it welcomehead.96.png and paste it in the windows directory.
I've tried to keep the TyTN II'spirit ~smart'n'pro !
;-)

zachto said:
I like the easy way.
Just make your picture 240x320, save as welcomehead.96.png and copy to \windows\ on the Kaiser.
Bob's your Uncle.
Click to expand...
Click to collapse
I did as you sugested but it does not work, I created a new file put it in the windows directory, now i have two files there by the same name, I try to delete the original one but i get an error its a ROM file can not be deleted, and when I start my device the original still boots up instead of the new one, any sugestions to do it the easy way ?

My work....

continue...

arimus said:
I did as you sugested but it does not work, I created a new file put it in the windows directory, now i have two files there by the same name, I try to delete the original one but i get an error its a ROM file can not be deleted, and when I start my device the original still boots up instead of the new one, any sugestions to do it the easy way ?
Click to expand...
Click to collapse
You can't have two file with the same name so something must be different (unless the 2nd one has a (2). I found that I had to use resco file explorer to change the original welcomehead file's attributes and remove the "read-only" flag. Then I was able to copy over it with my own splash .png files.
Also the welcomehead files "should" be 320x320 to give you a correct image if booting in landscape but I never boot this way and I imagine others don't either.

Hey Deathace, do you have this screen in a plain version with no logos, just the swirl?

RemE: here you go.
Russ

Perfect Thanks!

Deathace said:
RemE: here you go.
Russ
Click to expand...
Click to collapse
did you make those? those are sweet

welcomehead.96 read only
I got Resco File Explorer, I went to the windows directory and changed welcomehead.96.png to read only, but it doesn't stick. It immediately reverts back to read only. So, I can't copy the new file in.

ChaoticPi said:
I got Resco File Explorer, I went to the windows directory and changed welcomehead.96.png to read only, but it doesn't stick. It immediately reverts back to read only. So, I can't copy the new file in.
Click to expand...
Click to collapse
copy the new file from your PC to the 'My Document' folder on the Tilt. Then on Tilt, copy (or move) the file from the "MY Docs" folder to the \windows directory. You get a prompt ot overwrite, say yes to that, then you will get a second warning about the file being replaced is a ROM file, say OK to this too....

HOW TO: Build your own rom, by ITJE **UPDATED 11 nov**

Itjes Guide on how to cook your own rom, fast and dirty J Part 1
First of all, this guide will not tell you everything you need, I cant show you where to find reg entries, where all files are located. It’s a guide that will show you the basics. I will tell you how to extract a official nbh to os.no, how to dump it to respective oem and sys folders where you will do your “cooking”
First of all download Hypercore Kitchen here, then run the install file.
You will now have a folder called hypercore on your desktop, and a folder called core, located on c:\core
After install, download this fixed batch folder: batch or from mirror here: Batch
Delete the batch folder in c:\
Extract it to c:\core, and replace the original one.
The reason for doing this, is that there had to be some changes in the batch files for it to work.
Now you have a functional hypercore kitchen and you can start working.
I am gonna release a OEM, SYS and ROM folder for you, but not yet. I want you to understand how mutch work it takes to build a rom, and you need to go through some of the steps that all the other chefs must when they build roms. Why not just make it simple and give you everything? There is a answer to that, and you might not like it: Because I don’t want to….
Download your official RUU from here
Use winrar or similar to extract the files in the installer, choose extract to a folder.
Open the folder you extracted the files to, and find the RUU_signed.nbh
Copy it to c:\core\tools
Open your command-promt (dos editor)
Go to c:\core\tools
Your command promt should now look something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When this is done, you must enter this: nbhextract ruu_signed.nbh
The nbh will now be extracted and in the core\tools folder you now have all the files dumped from the nbh
The screen should now look something like this:
See the second last line Extracting: 06_OS.nb
That is the file you will need.
Rename the 06_OS.nb to OS.nb
Copy the OS.nb, then close the core\tools folder
Move to your desktop, and open the hypercore folder
Then enter the extract folder, and paste your OS.nb there
Go back to hypercore main folder, open the Panel folder, then open the Extract folder.
Inside the extract folder you will find a file/shortcut called Dump .nb and .bin
Now a panel will open and give you 4 options:
Now you are dumping the OS.nb into a xdump folder located in panel\extract
Your answer here is 1 since im doing this guide for heralds
Now a new window is gonna pop up and tell you that in that windows your OS.nb should be placed, and if you did what I told you correctly, then the OS.nb is located there already. So close that window, and then another option in the command promt will ask you to hit enter when ready, witch I now suppose you are.
The OS.nb is now being extracted into the xdump folder located in the extract folder. This takes aprox a minute or so.
When the OS.nb is finished extracting, you will get a option to start pkg.tools. just close that option,its not working for some reason, I never really looked into it, I just did a “workaround”
In panel\extract you will find pkg tool
Start the pkg tool, and you get a command promt window, read it, and then press enter.
Now you should see this:
Choose option 3
Pkg tools will now open.
Go to the file menu in upper left corner, chose open, then browse to hypercore\extract\xdump\
Highlight the dump folder and press ok.
GO TO NEXT POST IN THIS THREAD

You should see something like this:
Forget the missing manifests.
Now choose the Tools meny in pkg tools, and build packages, this will only take max a minute. (you will see nothing, just wait a bit.
When you have done his, browse to you xdump folder, open it, inside you will see the dump folder, rename the dump folder (not the xdump) to packages.
Copy the new packages folder and paste it into the hypercore\extract folder. Then close the pkg tools.
From now on, I will not give you screenshots of everything. You should get the picture on how it works now.
You will see a new commandpromt window, giving you 5 options, you choose option 4: Move oem and sys to hypercore\build.
You will get a question if you wanna backup, type n for no this time.
This takes 2-3 minutes, depending on your computer. The oem and sys is being moved to hypercore/build. Where the building process is gonna happen.
Next step is to go back to hypercore\panel\extract.
Open the dump XIP tool, and you get a new pop up window, just close it and press enter in the command promt. A new commandpromt window show you option 1 and 2, do both options, and when you have done this, the oem, sys and rom folder contains all you need to cook.
But that comes in next lesson.
I have now written this as easy as I can, if you don’t understand this, I cant help you more in this process, because I cant give it to you in a easier fashion.
Have fun
Itje

Part 2 of Itjes cooking lessons
How to add and remove and build your rom
I assume you have followed the instructions in the first part, learned to extract both the .nbh and the os.nb into rom, sys and oem folders.
My way of cooking:
First you need to find out what you want and not want in your rom. I will try to guide you into building a small apps rom.
So first I do, is deciding what I don’t want to have in my rom, and I usually go to the sys folder, and start removing stuff I don’t use:
But before you start removing in sys, highlight the sys folder, right click and choose properties, uncheck the read only box, if you don’t you can’t edit files.
Remove:
Transcriber + Transcriber_lang_04xx (xx is the country code in your rom) + Transcriber_ Lang_04xx_DPI_96
See what you need to do? Remove all the folders with the name transcriber in it
You can also do this with: Office, windowslive. Internetsharing, entertainment (games)
Be careful removing in SYS folder, delete wrong stuff, and you will have a brick when flashing.
That’s a easy “clean up” of the sys, there are also other stuff you can do.
You can make your own startup image, that is located in the Redist_dpi_96_resh_240_resv_320 folder, and is called welcomehead.96.png, edit with either adobe photoshop or corel, or any other picture editors that support png files.
Open the welcomehead.96.png and do your changes, save and your done. How to and all that with photos/pictures im not gonna do, so you need to find a way to do so yourself.
Now, you can go to OEM folder, where you can add and remove a lot off stuff.
I will not show you everything, you must figure some stuff out yourself.
But download OEM packages (This is easy to fin, its all over the xda forum.
Im assuming you have found in some stuff you wanna add, in.ex total commander, htc home, networkwizard, CommManager. Ocourse you can add more or less.
Add the oem packages into the oem folder. Total commander and networkwzard don’t require removal off default files from the oem folder, but comm. Manager do, and so do htc home. The way I use to find duplicate files, is before I add the oem packages, I open in.ex the new package with comm manager, and I highlight the OEM folder and rightclick and choose searchtab. Search for files, type in search “comm.” And all files containing the word “comm.” Will be displayed, dele them (make sure they belong to comm manager, that the names matches the one in your package)
When you have searched for all files in your package, and deleted them from the OEM folder, you can add you package.
Follow same steps for all packages you add, that can have duplicate files, if you don’t you will get error when building the rom, and the build process will terminate, tell you what file is duplicate. You must then find the file, and remove it (don’t remove the one in your new package)
You can also delete stuff from oem folder, I will take as example adobe.
The easy way to remove adobe, is to find a oem package with adobe, so you can see what files needs to be deleted. Use same way as I showed you with comm manager.
You can also delete gif files, png files and wav files to make more space, be carefulll so you don’t delete files that are needed by applications you wanna keep.
Now I hope this was clear enough.
Now you can go to the hypercore/panel/build section where you will find buildOS, run it it follow steps there.
If you get errors with duplicate files, you need to remove the duplicate and start buildOS again. And continue to do so if you get more errors.
But when the buildOS is finished, close it and a new window will pop up, chose your device, and press enter, and your os.nb will be built.
flash it to your device, and test it. If it didnt work, then you have done something wrong, or im just a lousy teacher
This was a very easy guide, I hope you find it usefull. There are lot of things you can do more then I have described now, but all you need is posted all over the forum. And if your dedicated enough, you will find all you need, just be patient. You cant find it all in one day,and you cant understand it all in one day.
Have fun
Happy cooking
cheers

----------------------------

Good work. Hopefully we can get some new roms going around.

itje said:
After install, download this fixed batch folder: batch or from mirror here : batch
Click to expand...
Click to collapse
Where's the link to the batch download?

LordPhong said:
Where's the link to the batch download?
Click to expand...
Click to collapse
right there
lol, was a bit tired yesterday, forgot to add the link

Cool - thank you itje for all the effort and time you are investing...
Can't wait for the next parts

trallala said:
Cool - thank you itje for all the effort and time you are investing...
Can't wait for the next parts
Click to expand...
Click to collapse
thx
has anyone been sucessfull extracting nbh to os.nb to oem, sys and xip (rom folder) following this tutorial?

When is the next part due? I really am eager to cook!!!

oddball1 said:
When is the next part due? I really am eager to cook!!!
Click to expand...
Click to collapse
havnt started on it yet
So I dont know maybe this weekend, but not later then the end of next week
patience, my friend, patience

is the next part just making the extended rom portion? I think there's a tutorial somewhere on this site but I can't seem to remember off the top of my head, right now.

itje said:
Download your official RUU from here
Click to expand...
Click to collapse
I'm being a pain in the arse again. there's no link there and I don't know if it's the same one as the official tmo release. I know I can probably use that one but would rather not.

hey itje the links for the new batch files doesnt seem to be working. i tried them and it just keeps popping up saying it cant DL
edit: nevermind i got it too work. it was blocked on the isp i was using.

itje said:
thx
has anyone been sucessfull extracting nbh to os.nb to oem, sys and xip (rom folder) following this tutorial?
Click to expand...
Click to collapse
itje said:
Rename the 06_OS.nb to OS.nb
Copy the OS.nb, then close the core\tools folder
Click to expand...
Click to collapse
where do we copy the OS.nb to? Since, I didn't know, I, manually, had to do it.
itje said:
Copy the new packages folder and paste it into the hypercore\extract folderThen close the pkg tools.
Click to expand...
Click to collapse
This didn't work for me. I had to manually past it in %systemroot%\Core\Extract\Packages after I closed the pkgtools. For some reason, it didn't find the Packages folder correctly.
After that, I followed everything else and it worked fine. Just as you described. Just waiting for part dos (spanish not MS-DOS).

everything works fine up until the end waiting on farther instructions.

EVERYTHING YOU ASK FOR IS ALLREADY THERE, START READING........
Just as its clear, from now im not gonna answer anyone who ask for something thats allready described in the tutorial.
But the link for ruu was not there, I'll give you that..

i am cooking my chinese rom ,and thanks you working.

ginolin said:
i am cooking my chinese rom ,and thanks you working.
Click to expand...
Click to collapse
Glad I can help

Honestly, if anything you did went wrong, is because you are not reading and reading it again before you do it!
Up to now, everything is well explained

how to add a new city to the weather plugin

hi,
ive read plenty of articles how to add a new custom city to the htc home weather plugin, ive found the current city on the
my city isnt in this list:
http://www.accuweather.com/includes/ajax-functions/favoriteCities.asp?region=EUR&country=SK
but if im using the search form, i find it:
http://www.accuweather.com/world-index-forecast.asp?partner=accuweather&traveler=0&locCode=EUR|SK|LO000|ZILINA
1. problem if i want to add my city in the .xml file inside the windows dir in the rom, i cannot change it, cause, its rom, also no the file attributes, i thought, maybe i create a new file with a new language code and use this, somehow, but i dont want to change my current language: english
2. ive tried to set it in the registry:location and locationcode, but the plugin writes eveytime: unable to retrieve data for selected city...
any ideas?

1. Have you searched the registry? There may be path of the .xml file so you yould just "redirect" to your modified file. (I dont know if there is such key or not, but you can try that...)

moneytoo said:
1. Have you searched the registry? There may be path of the .xml file so you yould just "redirect" to your modified file. (I dont know if there is such key or not, but you can try that...)
Click to expand...
Click to collapse
negative

Have anyone succeed to add a new city? I have changed the xml file but the new city isn't visible? Tried reboot after the change.
Why are there several files with similar name but same content?

mrfredde said:
Have anyone succeed to add a new city? I have changed the xml file but the new city isn't visible? Tried reboot after the change.
Why are there several files with similar name but same content?
Click to expand...
Click to collapse
how did you changed the file??? i even cannot change the attributes from total commander, explorer...anything

darksider said:
how did you changed the file??? i even cannot change the attributes from total commander, explorer...anything
Click to expand...
Click to collapse
I copyed the file and changed file type to .txt and edited it in Word Mobile. Then changed back to .xml and copyed back to \windows

mrfredde said:
I copyed the file and changed file type to .txt and edited it in Word Mobile. Then changed back to .xml and copyed back to \windows
Click to expand...
Click to collapse
mine windows doesnt allows to overwrite or change this file...

Now I hade edited the file, i copyed the file thru active sync and then back to Storage Card and then used Total Commander and copyed it to \windows.
But when i select the city it can't get the information for selected city.
Is there something else i have to change?

mrfredde said:
Now I hade edited the file, i copyed the file thru active sync and then back to Storage Card and then used Total Commander and copyed it to \windows.
But when i select the city it can't get the information for selected city.
Is there something else i have to change?
Click to expand...
Click to collapse
you can try to set the settings direct in the registry, its already a thread about it, here somewhere...

i now tried to change the url in the htchome.dll but i wont find the url to replace.
Someone must have solved this problem?

I am one of the folks here who wish to be able to add different cities. If somoeone figure out how to perform it, please just let us know

I have been able to copy to my desktop HH_0409_WeatherCities and HH_0809_WeatherCities (not sure witch one attributes to english language) I added the strings related to my city and now i try to replace them on the s730 but as other found, it is in ROM and i cannot chage its properties with total commander....need help, maybe i am not so familiar with TC. I am so close!

I added my city to the HH_0809_WeatherCities.xml file by copying it to my desktop and then copying it back into the smartphone. I think the edited file shadows the file in the ROM. I can now select my own city from the list, but the weather program still cannot update.
I can see that when I select a city, the registry values
HKLM\Software\HTC\HTCHome\Weather\Settings\Location​
and
HKLM\Software\HTC\HTCHome\Weather\Settings\LocationCode​
get the right values, however the registry key
HKLM\Software\HTC\HTCHome\Weather\Settings\CityIndex​
doesn't change, and I suspect that this is not good. I haven't been able to correlate this city index with a location code. I think it might be the index of the entry in the .xml file.

CityIndex is the position of the city on the list. But it doesnt matter, you can have any number and it will work.
When I change LocationCode to another place which is in the list, it displays it. It seems it's problem of the server, they just do not provide data for other cities this way. If I change LocationCode to my city, I get this message: "Unable to retrieve data for selected city."
EDIT: Here is some more info... http://forum.xda-developers.com/showthread.php?t=319187
The library needs to be modified to connect to different server. I have just tried the DLL from Kaiser but the weather plugin just disappeared. I will try to modify Wings's HTCHome.dll.

When u fix de htchome.dll I wont that file =) I tried to modify my file but i dosen't work.

WORKING!!!
1. Instal certificate
2. Instal Resco Explorer
3. Get loccode of your place on accuweather.com
4. Switch to non-HTC homescreen
5. Copy WeatherUpdateService.exe to temp dir on your smartphone and check it is set as system and read-only
6. Copy WeatherUpdateService.exe and replace the orignal in the Windows directory using Resco Explorer
7. Modify HH_xxxx_WeatherCities.xml (or registry - HKLM\Software\HTC\HTCHome\Weather\Settings\LocationCode and HKLM\Software\HTC\HTCHome\Weather\Settings\Location)
Refresh data.
Uses N2A's server. Say him thanks.

Thank you SOOOOOO MUCH! moneytoo, you're almost a god for me!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I did try to install the Kaiser HTCHome.dll. Can anyone pls upload the original for S730 so I dont need to reset my device; to much configuration for a saturday before x-mas

afx69 said:
I did try to install the Kaiser HTCHome.dll. Can anyone pls upload the original for S730 so I dont need to reset my device; to much configuration for a saturday before x-mas
Click to expand...
Click to collapse
Here you have.

moneytoo said:
WORKING!!!
Uses N2A's server. Say him thanks.
Click to expand...
Click to collapse
thanks much*

TotalFire's ROM Cooking Guide [Unfinished]

TotalFire's ROM Cooking Guide
I have been requested to write a simplified guide on how to cook ROMs For Xperia, as I have just started please be patient and ignore any empty posts for now.
This guide is for anyone who wants to learn how to cook ROMs for Xperia, you dont need any knowledge other than being able to flash a ROM on your Xperia
If any of the information stated is incorrect please tell me and i'll change it.​
Tutorial Layout:
1: Tutorial Layout
2: Setting Up The Kitchen
3: Cooking Your First ROM
4: Customizing Your ROM
5: Customizing Using Autorun
6: Fixing BuildOS Error's
Credits:
Bepe & Gtrab for the kitchen
Anyone else I forgot to mention

Setting Up The Kitchen​
The Kitchen is where all the files in the ROM are kept and where there put together into a ROM which is flashed. There are mainly two types of kitchens, an automated kitchen and a visual kitchen, in this tutorial I will be using a automated kitchen which was made by bepe and modified by gtrab. The only modification I did to the kitchen was to make it rename the ROM to RUU_signed.nbh so that it could be flashed from the PC. in this tutorial I will explain the filesystem used in the kitchen.
In the root of the kitchen you will find 4 folders, they are OEM, SYS, ROM and Tools, below I will explain whats in each folder and what it does.​
OEM
The OEM folder contains all the customizations made by the OEM or in this case chef. In the folder you will find lots of folders which begin with PACKAGE, these are most often applications, registry changes or both. The name can indicate which phone they come from for example a package which is called "PACKAGE_Kovsky_Camera" comes from the Kovsky (Xperia) and a package called "PACKAGE_Rhodium_PhoneCanvas" comes from the Rhodium (Touch Pro 2). Inside a Package you could find many different filetypes, every package has at least a dsm file inside, this is a identifier file. The dsm files name will have loads of random numbers and letters in such as "d9dd6d62-02d6-48d7-9764-18ac81aff3ad.dsm", this is it's unique identity no other package will have the same ID. Most Packages will also have a rgu file, an rgu file contains registry changes for the device, a package can contain only one rgu file and it must have the same name as the dsm file. Make sure when writing a rgu file to have the first line say "REGEDIT 4" and the last line must be empty, if this is not done the rgu will be ignored. One more filetype to look out for is a provxml file this contains registry changes just like the rgu but can be called anything and you can have as many provxml's as you want in a package, the registry edits are written in xml. The last file to look for is an "option.xml" file, these are used only by the kitchen to tell it if the package should be used, these are not needed but without one the kitchen uses the package without giving you a choice. The "option.xml" files can be made manually or generated with Ervius Package Creator but its easy enough to make it manually so I usually do. OEM Packages can be extracted from official ROMs and unprotected ROMs, you can also convert cab's into oem packages using Ervius Package Creator or doing it manually, later on in the tutorial I will add a guide on how to using Ervius Package Creator (manually doing it is too complicated). CABs can be installed without converting them to OEMs but the more CABs you have the longer it takes for the customization to finish when you first install the ROM, I will also show you how to install CABs without converting them to an OEM in a later tutorial, the use of this is if a CAB doesnt convert properly with Ervius Package Creator and you dont want to convert it manually.
ROM
In the ROM folder you will find the folder XIP and the file "OS.nb.payload", the "OS.nb.payload" file contains things such as the splashscreen, usually this file is not edited and the splashscreen is overwritten by a package in OEM. The "OS.nb.payload" is usually changed when upgrading the SYS folder because "XIP.bin" contains the kernel files which is inbuilt in the "OS.nb.payload" file. In the XIP folder there is boot.rgu file which contains registry entries used by windows mobile and isnt used by the OEM or chef, it is used exactly as an rgu file would in a package in the OEM folder. When upgrading to a new build of windows mobile this folder will be upgraded, it will need to be ported properly to xperia for it to work but i'll add a guide for that in a later tutorial.
SYS
The SYS folder contains all the files used by windows such as themes and applications like office mobile. Inside the SYS folder there are many other folders such as MediaOS (Windows Media Player) and WindowsLiveIM(Windows Live Messenger) These are basically packages made by windows similar to the OEM packages. I dont need to go into as much detail as I did with the OEM because the only time you use this folder is when you either swapping images to change skins or upgrading the windows mobile build. I will show you how to upgrade the SYS folder in a later tutorial because some of the files in SYS are device specific and resolution specific so you cant just take a SYS folder and overwrite your old one.
Tools
The Tools folder contains all of the applications the kitchen uses to build a ROM. I dont need to go into any detail because you never need to touch any of the files in the Tools folder but if you intrested, you can open the cook.bat file in the root of the kitchen which should tell you more about which applications do what.
Other than the 4 folders in the root of the kitchen is 4 files, they are Cook.bat, CustomRUU.exe, SYSVersion.exe and XVI32.exe Shortcut, below I will explain what each file does.​
Cook.bat
This files runs all of the tools in the kitchen to build to ROM.
CustomRUU.exe
You should have seen this file before, it is used to flash a ROM
SYSVersion.exe
This application checks the version of each individual SYS folder, useful to check the SYS build
XVI32.exe Shortcut
This application is used to HEX edit files, this can be used to HEX edit the ROM to change the default date, i'll show you how to do this at a later date.
Download the Kitchen Here​

Cooking Your First ROM​
I feel the best way to learn to cook ROMs is to get familar with the cooking process. In this tutorial you will cook a ROM using Gtrabs/Bepes kitchen and end up with RUU_signed.nbh will can be flashed on your xperia, hopefully this will give you an sense of what cooking is like.
Step 1
Extract the kitchen you downloaded in post 2 to any place on you computer, I have my kitchen on the desktop. Please make sure you have framework 3.5 installed onto your pc as its required.
Step 2
Run the file Cook.bat, a command prompt will open up shortly followed by a application called BuildOS. BuildOS lets you chose which packages to cook in your ROM without having to delete them every time. Only packages with an option.xml file will be shown meaning if its not there it, you will have to make one or else it will be cooked in without giving you a choice. As this is an early tutorial i recommend you like all packages in for now incase you remove required packages accidently. Now press the play button and wait until it says at the bottom left corner "done", once "done" appears close BuildOS.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
Step 3
After closing BuildOS, two Command Prompts will open, wait for one to close. Once one has closed you'll have one command prompt asking for you to chose a compression method, like in the picture below. What you do is press enter and an application called XVI32 will open, this is an HEX editor. Now you need to choose which compression method you want LZX or XPR, LZX compresses the ROM much better than XPR but takes longer to cook the ROM, most often I compress with XPR when testing but use LZX when releasing a ROM. All you do to change compression is look at the HEX editor it says either LZX or XPR, if it says LZX and you want XPR, change it to XPR, save and close and vice versa. After closing XVI32 There will be loads of white scrolling text wait for it to stop moving.
​
Step 4
You will now have a comand prompt, like below just press enter and wait for it to close. Congratulations!, you have just cooked your first ROM, if you would like to test it plug in your xperia and run CustomRUU.exe and just flash the ROM like you normally would.
Now that you've cooked a ROM you can try cooking another while removing some packages and following any customization suggestions in post 4​Click Here​

Customizing Your ROM​This Tutorial Contains Various Mini Tutorials On How To Customize Your ROM​
How to change your ROMs Name
In the kitchens tools folder there is a file called nbhgen.txt, edit the third line (which says "SEX1.R3" by default) to the new name of your ROM
In the kitchens OEM\OEMVersion there is a rgu file, edit the line in the file "ROMVersion"="SEX1-r3.61-XprT" changing "SEX1-r3.61-XprT" to the new name of your ROM
Note: Your ROM name can have a maximum of 16 characters and no more, change both of the above to chnage your ROMs name
How to change your ROMs Boot Screen
In the kitchens SYS\Redist_dpi_192_resh_480_resv_800 folder there is a file welcomehead.192.png which is the phones boot screen
Only the first 480 x 800 pixels are used from the image taking from the left side of the image
Adding Extra OEM Packages
Simply take the package and place it in the OEM folder of the kitchen
Some packages have a language package with must be cooked also for example "PACKAGE_Kovsky_Camera" & "PACKAGE_Kovsky_Camera_0409"
OEMs can be extracted from Stock ROMs and some custom ROMs (if there unprotected), I will show you how to extract ROMs in a later tutorial
Upgrading Windows CE Build (SYS)
Replace packages from your old SYS folder with ones from the new SYS folder
Dont replace the folders ".VM" or "WinCENLS_WWE" because they are unique to that device
Dont replace files with resolution packages with newer resolution packages of a different size, for example "Redist_dpi_192_resh_480_resv_800", this is for a phone with resolution 480 x 800, so dont replace it with something like this "Redist_dpi_192_resh_480_resv_640"
The same goes for DPI, make sure the new package is the same DPI as your old one, for example "Base_DPI_192" this package has a DPI of 192, dont change it to something like this "Base_DPI_96"
Finally packages that contain language files must be replace with files of the same language or else the OS will be in another language, for example "Browsing_Lang_0409" this package is and english package (0409 is english) so dont replace it with something like this "Browsing_Lang_0407"
Changing The ROMs Default Date
After cooking a ROM, open XVI32 in the root of your kitchen
Click File > Open and select the "RUU_signed.nbh" file from the root of your kitchen
Press Ctrl and F, and search for "Jan"
Below the line its selected there should be something like "Apr 23 2009", Change it to something like "Aug 18 2009"
"Apr" stands for April change it to the first 3 letters of the month you want to change it to

Customizing Using Autorun​This Tutorial Is Not Finished, Please Ignore It​
In most ROMs, there is a customizing screen which is shown just after the ROM is cold booted (ran first time or ran after hard reset). This is where all the CABs are installed, theme is set and the last registry entries are added. In this tutorial I will show you how to use autorun to customize your ROM.
First in the kitchen go into the OEM\OperatorPkg folder.
Installing CABs With Autorun
First place the CAB you want to install into the OEM\OperatorPkg folder
Open either config.txt or config_operator.txt, I would use config.txt
Add line in between "LOCK:Enabled" and "LOCKisabled", "CAB: \WINDOWS\your_cab_file.cab" replacing "your_cab_file" with the exact name of the CAB.
Remeber the more CABs you have, the longer it will take to customize, so only use it if converting it to a package doesnt work.
Installing TSKs (Theme's) With Autorun
First place the Theme you want to install into the OEM\OperatorPkg folder
Open either config.txt or config_operator.txt, I would use config.txt
Add line in between "LOCK:Enabled" and "LOCKisabled", "TSK: \WINDOWS\your_tsk_file.cab" replacing "your_tsk_file" with the exact name of the TSK, this changes your default theme
Put as many themes as you want in the OperatorPkg folder, they will all be added into the list in today settings

following every word!!

Very nj!
It's all clear and easy to follow: the perfect tutorial!
I was waiting for this for long time, thank you!

well done TotalFire, keep the high spirt

great work...i can finally understand how this works! When will you release another tutorial? I would love to know how to put programs in your rom (or the packages, for that matter) install skins or a connectio nsetup which runs automatically....
love this!

I'll try and release a few tommorow.
Does anyone know if its possible to disable smilies in a post?

yes when u reply click go advanced .then u click disable smilies in text!

rotastrain said:
yes when u reply click go advanced .then u click disable smilies in text!
Click to expand...
Click to collapse
Thank You
--------------

Totalfire , i believe after you finish this tutorial any beginner can cook his own rom with his own recipe
so please continue the same SIMPLE wording
thanks M8

I will, just need a bit more time

Please request tutorials, and i'll make then. Dont know which one to make next.

Nice tutorial I'm using Visual kitchen myself but nice tutorial for old style

killer8nl said:
Nice tutorial I'm using Visual kitchen myself but nice tutorial for old style
Click to expand...
Click to collapse
Ive just started using the visual kitchen, didnt give it much of a try last time. Seems good so far.

Fixing BuildOS Error's
While cooking ROMs you are very likely to come across error's, this post will show how to fix some of them.​
Default.hv And User.hv:
Open the file temp\log.txt, and scroll to the bottom of it
Look at the second last line, there should be an error message with the name of a rgu file
Higlight the rgu file and copy the name to clipboard
Search the root of the kitchen with the text you just copied from the last step
Look at the folder it says and open the rgu, there is a problem in there you need to fix

As i have switched to visual kitchen, it would be easier for me to make guides for that, would anyone prefer me to continue making a guide for the old style kitchen. BTW visual kitchen, is easier especially for thing like porting SYS and ROM.

if i need to remove anything from the OEM before cooking (like a panel), just delete the item? or is there another task i must perform as well?
BTW thanks for this tutorial, this is soo damn simple, nuff respect to you dude

[HELP] How to create folder and file if they dont exist.

Hi
I am new to tasker, so I am trying to learn things how to work with it.
This time I want to create a specific folder and file inside it if the folder and /or the file don't exist... I really don't have a clue... Please help me if you can..
Since I'm a newbie pls try to give me a solution in a simple way..
Thanks

These directions are not as simple as a newbie would want, but they're better than nothing.
To check whether a file / folder exists:
File > Test file
Set it up like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then check the value of %exists
If the value of the variable matches (without quotes) 'dir' then it is a folder; if it matches 'file' then it is a file.
To make a folder:
File > Create Directory
To make a file:
File > Write file

Sukarn said:
These directions are not as simple as a newbie would want, but they're better than nothing.
To check whether a file / folder exists:
File > Test file
Set it up like this.
Then check the value of %exists
If the value of the variable matches (without quotes) 'dir' then it is a folder; if it matches 'file' then it is a file.
To make a folder:
File > Create Directory
To make a file:
File > Write file
Click to expand...
Click to collapse
Thanks so much for reply, your explanation is super simple and really nice..
But I'm sorry I need to ask you couple more questions, since I said I'm a newbie I don't understand everything...
As you did "/sdcard/something" what should I replace "something" with? And also should I try to match the variable with the file or directory name or just simply %exist ~ file/dir?
I'm sorry if I sound stupid.. Please don't laugh at me.. I'm still learning
Thanks again and waiting eagerly for your reply... Thanks

Sukarn said:
These directions are not as simple as a newbie would want, but they're better than nothing.
To check whether a file / folder exists:
File > Test file
Set it up like this.
Then check the value of %exists
If the value of the variable matches (without quotes) 'dir' then it is a folder; if it matches 'file' then it is a file.
To make a folder:
File > Create Directory
To make a file:
File > Write file
Click to expand...
Click to collapse
Ok i got it work using shell command
For directory
Run Shell > [ -d /sdcard/dirname ] && echo 1 || echo 0
Store return variable %chkdir
Then checking the value of the variable 1 for exist 0 for not
Same way for file
Run Shell > [ -e /sdcard/filename ] && echo 1 || echo 0
Store return variable %chkfile
This method is working for now... I still look forward for your simple solution since your way is simpler but I need to understand it well
Thanks

dreamsayer said:
As you did "/sdcard/something" what should I replace "something" with?
Click to expand...
Click to collapse
"something" could be a file or folder or path to file/folder. Easiest way I can tell you to get the full path to a file or folder, without explaining how file paths work, is to long-press on that file/folder in ES File Explorer and then open its Properties, then tap on 'copy full path'
dreamsayer said:
And also should I try to match the variable with the file or directory name or just simply %exist ~ file/dir?
Click to expand...
Click to collapse
You typed %exist, but I'm typing %exists because that is the name I used for the variable in my screenshot.
dir is short for directory. Directory means folder.
If
%exists !~ file
AND
%exists !~ dir
then nothing of that name exists in that location.
If %exists !~ file
then what you checked does not exist as a file, but there could be a folder of that name in that location.
If %exists !~ dir
then what you checked does not exist as a folder, but there could be a file of that name in that location.
If %exists ~ file
then it exists as a file
If %exists ~ dir
then it exists as a folder

Sukarn said:
"something" could be a file or folder or path to file/folder. Easiest way I can tell you to get the full path to a file or folder, without explaining how file paths work, is to long-press on that file/folder in ES File Explorer and then open its Properties, then tap on 'copy full path'
You typed %exist, but I'm typing %exists because that is the name I used for the variable in my screenshot.
dir is short for directory. Directory means folder.
If
%exists !~ file
AND
%exists !~ dir
then nothing of that name exists in that location.
If %exists !~ file
then what you checked does not exist as a file, but there could be a folder of that name in that location.
If %exists !~ dir
then what you checked does not exist as a folder, but there could be a file of that name in that location.
If %exists ~ file
then it exists as a file
If %exists ~ dir
then it exists as a folder
Click to expand...
Click to collapse
Thanks a lot bro it works like a charm... Thanks for your patience with me

dreamsayer said:
Thanks a lot bro it works like a charm... Thanks for your patience with me
Click to expand...
Click to collapse
No problem. Everyone starts somewhere. No one starts as an expert.
Tips: use the ? button at the top, use the user-guide built into tasker, and save all documentation offline when it asks you, because you'll want to refer to the docs at random times.

Sukarn said:
No problem. Everyone starts somewhere. No one starts as an expert.
Tips: use the ? button at the top, use the user-guide built into tasker, and save all documentation offline when it asks you, because you'll want to refer to the docs at random times.
Click to expand...
Click to collapse
I'll do that thanks a lot...