Database Info

Wideawake's Custom AKU2.2

First I should warn that PPCGeeks.com nor me will not be held responsible if something were to go wrong. That being said its like any other update.....all you have to do is download the files from a link listed below. Extract them to the desktop open the the folder. Read the readme and run the .exe, same as the offical ones, BUT your PPC HAS TO BE IN BOOTLOADER MODE BEFORE running the .exe. (Hold power button, notes key, and soft reset) This ROM doesnt have to many "seen" differences, most changes have be made behind the scenes. I didnt remove the built-in voice dialer, because Im sure most dont use MSVC. Big thanks to isamu49 for his script to replace the bootscreen and providing me with all the carrier logos! Major thanks to XDA-Developers, and Buzzdev.net for the knowlege and tools used in the creation of this custom AKU 2.2! PLEASE HARD RESET AFTER YOU UPGRADE. I will be adding my extROM and full packages later today, just wanted to roll out the base OS for everyone.
Enjoy your new Custom AKU2.2!
Mike
Note: Upgrade CANNOT be done on a PC running Windows Vista, must be a XP machine.
Custom ROM Features
- A2DP built-in!
- HTC X Task Manager. (go to start/settings/system to enable)
- ApacheHax NO longer needed, registry pre-tweaked.
- Maximum number of connections tweak.
- No more dinging when volume is changed in call.
- Ligthen by removing un-needed files. (Saves about .5MB)
- UPX'd a few system files. (Saves about 6MB)
- ActiveSync Switch Included
- Vista Sound Theme along with .tsk.
- More Proformance enhacing reg. tweaks. (Thanks to MadManX for post)
- Couple Vista Ringers Added.
- Save Contacts by first name first.
- Sprint Users who download the custom with the extended will have PRL 20225 but you will have to manually run PPST.exe after customization is done.
Known Issues
- Video Mail not working, gives unknown format error
Carrier Bootscreen Download Links OS ONLY:
1. Sprint Logo - Download
2. Alltel Logo - Download
3. Qwest Logo - Download
4. Verizon Logo - Download
5. Telus Logo - Download
6. Bell Mobilty Logo - Download
7. UTStarcom Logo - Download
Advanced Users ROM
This ROM is for advanced users only! Comes with extROM unhide, NOT unlocked and a blank extROM. Loaded with NO files. I will post a verison with the apache unlock tool in it later, just ran out of time. Has Alltel bootscreen but you can change that with the tools posted in the splash screen thread. If I have time later today I will post the updated advanced version with all logos and the unlock tool by buzz.
Download: http://rapidshare.com/files/10913752/AdvancedCustom.rar
PS If you have any issues please read the readme file located in the extracted folder, if that doesnt help then report any issues to here.

Note: The installers I made, werent formatted right, so its gonna ask u were to extract. (Except for the Sprint and Alltel Upgrades) Once the files have been extracted run MaUpgradeUt_noID.exe with all the files in the same folder. I will try and fix the installers ASAP and reupload.

[KITCHEN][04/Jan/11]ELF(in) Kitchen(s)[ONLINE]

INTRO
I started trying to make a kitchen for our Elves based on bepe's Extended Kitchen and Elf(in) Hybrid Kitchen was "born".
Since then, bepe released his famous PlatformReBuilder(PRB) and I followed him, creating B2 Kitchen (page41 and on).
The Hybrid Kitchen is discontinued but I will keep it posted here for anyone who wants to play with it.
B2_Kitchen has started as an Elf(in) kitchen, but became a multidevice kitchen.
B2_Kitchen has started as a simple batch-file kitchen, but became a multifunctional kitchen.
At the end it is a GUI based on command-line tools just like some other visual kitchens.
The main applications are PlatformReBuilder and ImgfsTools.
So I don't actually feel that I made something new...
I take no credit!
CREDITS TO
bepe for the kitchens and other tools,
pof for the USPL, cmonex for the HSPL,
itsme , mamaich & tadzio for the brilliant but simple tools,
ervius for the great tools,
Noonski for the cooking class [This is how newbies gain the knowledge to cook] and for the inspiration,
Ababrekar for guideness in porting OS from another device,
Aman for sharing his knowledge&helping me make any fixes&upgrades
and many more members/developers of this forum which I consider as a free on line school whose tools and guides made this possible!
These kitchens are free to use or edit but at your own risk, I take no responsibility for any damage caused to your phone!​

B2 Kitchen
B2 Kitchen GUI (LATEST VERSION 2.0.0.0)
Supported Devices:
Elfin
Leo
Diamond
? (Testers Needed for other devices)
INSTALLATION:
Prerequisites:
Microsoft .NET Framework 3.5 (Windows Vista / Windows 7 have it pre-installed)
If you're using Windows Vista / Windows 7, make sure USER ACCESS CONTROL is turned OFF!
DO NOT change the structure of the kitchen!
If you don't want to use ImDisk Driver, you should get another 3rd party software able to create a RamDisk in order to use the relevant feature.
Installation:
Once you download the kitchen, install it following on screen instructions.
When you launch the kitchen for first time you'll get the chance to install ImDisk Driver if it isn't already installed.
(RECOMMENDED if you don't have another 3rd party software for Virtual Drive Management)
To get started, you should import a device by using an official_shipped_ruu.exe as a source.
Otherwise you could place your files manually.
(Be careful to put them in the correct way, respecting the kitchen's structure)
Download links:
Mediafire(For ALL users)
XDA(For XDA members)
********************************************************************************************************************
DESCRIPTION:(Video)
{
"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"
}
Dump any source you want in almost any known format:
RUU_Device_HTC_Version_Signed_Ship.exe
RUU_Signed.nbh
Flash.dio
OS.nbf
OS.nb.payload
OS.nb
nk.fat
Imgfs.bin
xip.bin
Part01.raw and Part02.raw
Import a new device by dumping the device's OFFICIAL Rom RUU_Device_HTC_Version_Signed_Ship.exe.
The kitchen will even create a CustomRUU.exe AND a Task29.exe for the imported device.
Import any new leaked build just with one click.
When you dump a rom / import a new device the kitchen is able to:
Remove any empty packages if you select -EmptyPkgs.
Sort each registry file from your dump to make it more readable if you select SortRegistry.
Sort all Packages into the required style.
Sort all manila localization files by lcid.
Build your rom according to your taste:
Set which packages will be included from the "Packages Selection" area.
Set Rom version, language, ModelID and CountryID that are required for generating the final flashable *.nbh. The Rom date will always be automatically set to current date.
Select among various builds and lcids which one to use for building your Rom.
Select whether to use a real 6.5 nk (if your device has a 6.5 nk) or not in your generated Rom by selecting 6.5nk.
Select whether to use ShaDrac's driver - Extendir - or not by selecting Extendir, without messing up (adding/removing Extendir.dll - editing boot.rgu) your XIP each time.
Select whether to reduce/remove ULDR or not at your generated Rom by selecting -uldr.
Select whether to increase the Storage Memory of your Rom or not by selecting -imgstart.
Choose your Rom's PagePool Size (0-20).
Select compression (XPR-LZX-None) method for building your Rom.
Add Radio and Splashscreen to your final flashable *.nbh.
Set the kitchen to take care the "SLOT 0 overfloating" issue when building a 6.5 Rom while your nk.exe is not a real 6.5 nk.exe by selecting Rec.Mod SYS
If you have used the above option and have recmodded some modules inside SYS/Shared in order to fix the "SLOT 0 overfloating" issue when no real 6.5 nk.exe is available, but now you want to use the same Build (= the same SYS/Shared) for building a new Rom for a device that has a real 6.5 nk.exe you can reversmode the same files by selecting Rev.Mod SYS.
Set the kitchen to search and find any duplicate items in your compilation that would cause crashing issues to PRB before starting the real building process by selecting DuplicateCheck.
Each time you build a rom a log file is created which you can easily see by clicking the "Process" Label.
Search for files or file's content (i.e. Search for a certain registry entry among *.reg files) using the search engine of the kitchen.
Access fast and easy certain files that are commonly used inside a Rom.
You can see lists of *.txt, *.mscr , *.xml , *.provxml , *.cpr & *_manila inside your kitchen by simply clicking the relevant button.
If you click on any file you see in those lists you open it for editing.
Flash any ROM you selected from a list of your created Roms to your device.
You'll get the chance to perform task29 on your PDA - THEN manualy enter Bootloader and FINALLY update the ROM if you have that special CustomRUU inside the kitchen.
Use a RamDisk (ImDisk Driver comes with this kitchen) for the building and dumping processes in order to gain speed and decrease hard disk fragmentation.
Cfc manila files and convert any normal Manila_package to a compressed one just with one click.
Exploit the possibilities of MortScript even during building your Rom:
Forget about app.dat - app.mscr is introduced in this kitchen.
Don't cook in hundreds of files that get copied to various locations but at the same time stay in your "Windows" directory slowing down your device - Create just one archive (app.xdaz) which extracts the files to the correct locations during boot leaving in "Windows" directory only one file with an unknown extension.
Convert cabs--->EXT Packages just with one drag n' drop on a button.
Convert files<-->modules just with one drag n' drop on a button.
Convert rgu files<-->hives just with one drag n' drop on a button.
Convert provxml files<-->reg files just with one drag n' drop on a button.
Convert bmp<-->nb just with one drag n' drop on a button.
Install any cab file to your pda just with one drag n' drop on a button.
Manipulate each package from the "Packages Selection" area just with one click:
Double click on the package to open its folder
Right click on the package to:
Edit directly the package's app.reg.
Edit directly the package's app.dat.
Edit directly the package's app.mscr.
UPX one/all package's executable(s).
Optimize package's png(s).
Optimize package's bmp(s).
Repack package's *.mui files.
Recmod one/all package's module(s).
NosplitMod one/all package's module(s).
Revmod one/all package's file(s).
Install the package to your pda.
Edit directly the initflashfiles.dat of the selected language just by right clicking inside the "Locale" box in the "Configuration" area.
Edit directly the boot.rgu of the selected build just by right clicking inside the "Build" box in the "Configuration" area.
If you want to edit directly the boot.rgu for the Extendir driver just right click the Extendir checkbox.
Read/Write directly the packages.cif and packages.sof of the selected build just by right clicking inside the "Build" box in the "Configuration" area.
Optimize XIP & SYS of the selected build just by right clicking inside the "build" box.
Build 3 different editions of your rom just by selecting an "Edition" (Premium, Basic, Lite) in the "Configuration" area.
This is optional, so if you leave "Edition" blank, then the "P" , "B" , "L" selection in the "Packages Selection" area doesn't matter!
Keep the kitchen accessible at all time. When you close the kitchen, it minimizes to tray from where you can access many functions and browse the kitchen's folders. By double clicking the tray icon you restore the kitchen's window.
If you want to really exit the kitchen while it is visible press F1!
Easily uninstall the kitchen from your system.
Easily save/load your project:
If you double click the "Save" icon then you'll save your current project (its name will be the Edition.build.locale.date&time of saving).
If you click the "Save" icon then you can select from a list of your projects which one to load.
Easily access all the tools that come with the kitchen. Even assign your own favorites to ALL the bottom buttons.
Check existing registry files for errors before building your Rom by right clicking the "Packages Selection" Label.
The time of this operation depends from the number of registry files, so you either give it enough time to finish if you have a lot of packages in your compilation or you click the Stop button to abort it.
Control your pda from inside the kitchen:
Restart your connected pda without even touching it.
Enter BootLoader.
Watch a list of processes currently running on your device.
View/edit/dump your device's registry.
********************************************************************************************************************
BASIC USAGE:
***Valid for any device - Just consider your device's name instead of the Elfin***
Packages Selection:
You can see all the SYS Packages from the BUILD & LOCALE you've chosen.
You can see all the EXT Packages you have in the kitchen's directories.
You can make sub-directories(limitation:up to 16!) to organize them better(i.e. EXT\Elfin\Tweaks , EXT\Elfin\TodayItems , EXT\Elfin\Apps , EXT\Elfin\Utilities , etc) and place your packages inside each sub-directory.
You can select which packages to include in your ROM by ticking the checkbox in front of the package's name. If you have it unticked then the package will be skipped.
If you double click inside the selection cell but not on the checkbox then you can select/deselect ALL packages.
You can see in the "Packages Selection" area that there are 3 columns "P" , "B" , "L" following the Package's name.
These will have an effect ONLY IF you select an Edition under "Configuration" area!
Code:
If you want "Package1" to be [COLOR="YellowGreen"]included[/COLOR]/[COLOR="Red"]excluded[/COLOR] in your [B]P[/B]remium edition then you must have the checkbox under "[B]P[/B]" [COLOR="YellowGreen"]ticked[/COLOR]/[COLOR="Red"]unticked[/COLOR].
If you want "Package1" to be [COLOR="YellowGreen"]included[/COLOR]/[COLOR="Red"]excluded[/COLOR] in your [B]B[/B]asic edition then you must have the checkbox under "[B]B[/B]" [COLOR="YellowGreen"]ticked[/COLOR]/[COLOR="Red"]unticked[/COLOR].
If you want "Package1" to be [COLOR="YellowGreen"]included[/COLOR]/[COLOR="Red"]excluded[/COLOR] in your [B]L[/B]ite edition then you must have the checkbox under "[B]L[/B]" [COLOR="YellowGreen"]ticked[/COLOR]/[COLOR="Red"]unticked[/COLOR].
There is also a ZIP Column. That Column is used to "mark" which EXT Packages you wish to convert to "Mscr_Packages" when you click "ExtToMscr" option.
Code:
If checkbox = unticked then nothing will change.
If checkbox = ticked then Selected Package will be converted to a Mscr Package (this is useful ONLY for applications that get installed to Program Files)
If checkbox = greyed then Selected Package will be converted to an Extendir Package (this is useful ONLY for applications that get installed to Windows and you're cooking Extendir in your Rom)
When you click the "ExtToMscr" the kitchen creates an archive (with the extension *.xdaz) from the Package's files and writes the necessary "app.mscr" (something like the equivalent of "app.dat").
For this it needs the "app.dat" inside the EXT Package so that it translates it to "app.mscr".
(This operation doesn't take place each time you hit the build button)
Your (original) EXT Packages will be copied to TOOLS\pkg\EXT.bak as a backup and only the (converted) Mscr Packages will be kept inside EXT[folder].
These new packages will be used ONLY IF you select "mscr" for ARType( = AutoRun Type) in the "Configuration" area.
Of course MortScript MUST be included in your Rom AND you must have the ARMS.mscr (script with #INSERTLINE switch) inside Autorun.mscr\Elfin folder.
Click to expand...
Click to collapse
Main Functions:
Obligatory routine:
Select device.
Select build.
Select locale.
Clicking the "Dump" button presupposes that you have placed a Rom file inside BaseROM folder.
When the process finishes you'll get a full dump of that Rom.
Drag n' drop a Rom file on this button works the same way!
Right Click on "Dump" button will show you two options:
Import New Device
meaning use another device's official rom to dump&prepare everything that is required by the kitchen to operate.
When everything is completed you'll be asked whether to auto move files or not!
Import New Build
meaning use any archive with the new leaked build to import the included SYS and XIP packages to the kitchen.
Next to the "Dump" button is 1 icon :
The folder-icon is a menu that includes shortcuts to various kitchen's folders.
Clicking the "Build" button starts the building process.
Next to the "Build" button are 3 icons :
The first one is a menu that includes :
ImDiskGui
ExtToMscr
RomTools
RePackOEM
CFCManila
The second one opens the below window. From there you can turn on/off the RamDisk feature, uninstall the kitchen, set your custom (build) commands, etc.!
The third one opens the Search utility of the kitchen.
Clicking the "Stop" button you stop the process you've started.
Clicking the "Phone-icon" button you have the options to:
Select from a list with your created Roms which rom to flash.
Restart your connected pda without even touching it.
Enter BootLoader.
Watch a list of processes currently running on your device.
Launch CeRegEdit
Double clicking the "Phone-icon" button you access the RELEASE\Elfin folder.
Clicking the "Flash" button you minimize the kitchen and start the CustomRUU (ElfinCustomRUU) in order to flash the ROM you selected to your device.
Right Click on "Flash" button will show you the option to Format&Flash, meaning that you'll get the chance to FIRST perform task29 on your PDA (ElfinTask29) - THEN manualy enter Bootloader and FINALLY update the ROM.
Right Click on "Configuration" label will show you the Advanced PRB Settings panel.
Clicking on "Radio" label opens the radio sub-folder.
Clicking on "Splash" label opens the splash sub-folder.
Addons:
You can easily access all the extra tools that come with the kitchen. - Drag n' Drop works for every dark-GRAY button.
You can assign your favorite links to ALL the buttons you see at the bottom!
Those links can be applications, folders, batch files or urls.
In order to set your own you should edit the file myaddons.ini under TOOLS\addons\ keeping the format addon#|Name|Path :
(Just right click on the button you want to change)
Code:
addon1|CFF Explorer|C:\Program Files (x86)\Explorer Suite\CFF Explorer.exe
addon2|Tiny Hexer|C:\Program Files (x86)\mirkes.de\Tiny Hexer\mpth.exe
addon3|Icon Editor|C:\Program Files (x86)\Icon Editor\IcoFX.exe
addon4|Manila Kitchen|C:\Program Files (x86)\Manila_Kitchen
.
.
.
********************************************************************************************************************
TO DO:
Any suggestions are welcomed!
Any bug reports are appreciated!

B2 Kitchen's Structure
This is the structure of the kitchen after importing a device and you shouldn't try to change it because you will have errors!
The build 23545 you'll see in the below pictures is an example in order to help you understand the kitchen's structure.​
Autorun.mscr is the folder where you can put your mortscript file that runs at first boot(named ARMS.mscr).
This mscr must include a line "#INSERTPOINT" !!! This line is required so that all "app.mscr" will be added at that exact point of your script!
The ARMS.mscr must be placed inside the subfolder named after your device.
BaseRom is the folder where you can put any rom you want to dump.
EXT is the folder where you store all your EXT Packages that you want to try in your ROM.
Here you can put any application,utility,todayitem,etc. and choose whether to include it or not, having in mind if it is or not essential for the windows to work!
Those Packages must be placed inside the subfolder named after your device.
OEM is the folder where you have OEMApps, OEMDrivers and other OEMFolders (Device Specific). Check out trueg's posts for more information about these folders.
Those OEMFolders must be placed inside the subfolder named after your device.
If you are cooking a rom in a different language than WWE, then create that subfolder.
For example if I want to cook a greek rom I'll create a subfolder 0408 along with 0409 and place my local.files in 0408.
If you are using the kitchen in OEM mode you can put inside the "Pkgs" subfolder your old-style packages (with *.dsm , *.rgu , etc.). You'll be able to choose whether to include or not each of those from the kitchen's packages selection!
RELEASE is the folder where your custom ROM (i.e.Yourdevice_ROM_Lang_0409_Build_21056.nbh) will be placed after cooking in order to flash it to your device using your CustomRUU.
You must have a subfolder named after your device under RELEASE and be careful with the names of the included *.exes (YourdeviceCustomRUU.exe & Task29\YourdeviceTask29.exe).
ROM is the folder where the XIP is placed.
If you enter this folder you'll see :
Like it is shown above, you must have all the XIP elements, except MSXIPKernel, inside the subfolder named after your device.
If your device has WinCENLS_Lang_0*** as part of XIP leave it there, otherwise an adviced location to store it is OEM\Yourdevice\0***\.
SYS is the folder where all the OS Packages (Not device Specific , but I'd say Screen Resolution Specific) are stored categorized by build number. Check out trueg's and Da_G's posts for more information about these Packages.
You must place those OS Packages inside the subfolders SHARED, dpi_96 , dpi_96_resh_240_resv_320 , etc. like it is shown below.
TOOLS is obviously the kitchen's "engine".
(Each time you build a rom you should find in there a log file from the building process which you can access by clicking on the Process label of the main application)
Inside CORE\Saved folder you must have a subfolder named after your device.
Inside CORE\Devices.list(file) you must have the settings for your device.
$DEV=YourDevice'sName
<1 for device that has only wm6.1kernel , 2 for device that has wm6.1kernel AND wm6.5kernel , 3 for device that has only wm6.5kernel>
KERNEL=3
dpi=192
resh=480
resv=800
ModelID=PB8110000
CID=11111111
chunksize=64
GSMHeaderType=0x301
<" -s" Switch if device's Splash.nb requires smartphone signature , leave blank if device's Splash.nb DOESN'T require smartphone signature>
SplashSwitch=
SplashHeaderType=0x600
<Size of device's Splash.nb>
SplashSize=786432
<" -t 0" for 0x00 or " -t 255" for 0xFF>
SplashPaddingType= -t 255
OSHeaderType=0x400
<hermes for Sectorsize=0x208 , kaiser for Sectorsize=0x808 , titan for Sectorsize=0x800 , leave blank for Sectorsize=0x200>
NBMerge=kaiser
<reduce for device that ULDR can ONLY be reduced , remove for device that ULDR can be totaly removed>
ULDR=reduce
Click to expand...
Click to collapse
Inside Radios folder (see below) you can store any %radio%_0x30$.nb in order to use in your Rom:
You must place those Radios inside the subfolder named after your device.
You can find all Elf(in) Radios here.
Inside splash folder (see below) you can store any
%##splash%_0x60$.nb in order to use in your Rom.
%##splash%_0x60$.bmp is required for previewing!
You must place those Splashscreens inside the subfolder named after your device.
You can find more SplashScreens here or you could make your own with the kitchen tools.
B2_Kitchen_GUI is the GUI that combines all the command line tools. Screenshots here.

Elfin Hybrid Kitchen
ELF(in) Hybrid Kitchen (DISCONTINUED - NEWER KITCHEN @ 2nd POST)
INSTALLATION:
1. Install on your pc Microsoft Visual C++ 2008 Redistributable Package and Microsoft .NET Framework 3.5!
2. Remove any previous version(if any)of the kitchen(shortcuts too) before "installing" the newer!
3. The archive should be extracted directly to the Drive where Windows are installed (most cases C:\) , otherwise nothing will work!
4. Once you do that, go into C:\ELF(in)_Hybrid_Kitchen and double-click "First_Run_For_ELF(in)_Hybrid_Kitchen.bat"!
5. IF you're using Windows Vista, make sure USER ACCESS CONTROL is turned OFF!
Download through: Mediafire
********************************************************************************************************************
DESCRIPTION:
(Be patient and keep your eyes on the DOS window for additional help&instructions while using this kitchen)
Main Functions:
[a] Dump any ROM from Kaiser, Polaris, Diamond, Xperia, Raphael, Elf(in)...
You may use these formats:
****.nbh (eg: RUU_Signed.nbh, Blue_Elves.nbh, etc) ,
****OS.nb (eg: New-OS.nb, 19588-OS.nb, etc) or ***windows.nb (eg:Mobile_windows.nb, New_windows.nb, etc) ,
****imgfs.bin (eg: imgfs.bin, new_imgfs.bin, etc) .
****.payload (eg: OS.nb.payload, 20270_OS.nb.payload, etc) . <- NOT FOR ELF(in) !
****.raw(only Part01.raw & Part02.raw) .
You get new OEM, SYS and xip.bin(unless you used *imgfs.bin) into C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\Temp .
If you used an ELF(in) ROM then you'll get a full dump, OEM, SYS and XIP, that you could move to C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19XXX\ and use it as a cooking base .
[b] Port any XIP from Kaiser, Polaris, Diamond, Xperia... You need xip.bin .
It requires:
NOT to change Ref_XIP folder inside C:\ELF(in)_Hybrid_Kitchen\Prepare_XIP and
If you have any problems in XIP Porting you have all the needed tools inside C:\ELF(in)_Hybrid_Kitchen\Prepare_XIP to try manually port the xip .
[c] Build your OS.nb (using the Ervius PkgToolsBuildos which can autofix & autorelocate SYS) .
You'll get the option to make a dumpable ROM using PkgToolsBuildos (by keeping unticked the box next to "All packages in one:") .
NOTE1: Inside ..\Build_ROM the OEM , SYS and ROM\XIP folders are empty . You may "fill" them with the required files .
NOTE2: Because Ervius PkgToolsBuildos is included in the kitchen, you could always use the functions that it provides apart from those described here .
NOTE3: If your xip_out.bin or out.bin is smaller than 2,49MB you could use the attached os.nb.payload (where imgfs start @ 0x280000)
[d] Flash any ROM to your device .
If you have a CID Locked device you have the option to flash a ROM using SoftSPL & your device remains CID Locked with the same SPL !
Additional Functions:
[1] Convert any cab to an OEM Package using Ervius Package Creator .
[2] Create a cab using IABovine's QuickCab 2.0 .
[3] Convert a bitmap to a Splash.nb (& reverse) using pof's nbimg .
[4] Convert files to modules & reverse using RecMod and reversmode . Not all files can be converted to modules.
[5] Convert 24 bit .bmp to .brn and reverse (for editing Cube gfx) .
[6] Compress executable files using UPX 3.03 .
Panel:
Easy access for many tools .
BASIC USAGE:
(Check out ayyu3m's great [PICTORIAL] COOKING YOUR 6.1 ROMS USING ELF(in) HYBRID KITCHEN)
1. Lets say you want to use a SHIPPED or DUMPED (NOT a COOKED!) ELF(IN) ROM as a Base.
--1.1.Double click the desktop-shortcut "Main Menu"
--1.2.Press [a]
--1.3.A window pops up beside the DOS screen. Place in there the RUU_Signed.nbh and close the window!
--1.4.Press [1]
--1.5.When the process is completed (& pressing any key returns you to main menu), you get another window opened with the files you want:
Packages(OEM&SYS)
XIP(folder)
xip.bin
--1.6.Keep that window open and double click the desktop-shortcut "Kitchen"
--1.7.Copy OEM and SYS to C:\ELF(in)_Hybrid_Kitchen\Build_ROM\
--1.8.Copy the XIP(folder) to C:\ELF(in)_Hybrid_Kitchen\Build_ROM\ROM\
2. The Base for cooking your ROM is set! Either clean up the OEM folder from things you wish to be removed or just (re)build the ROM.
--2.1.Double click the desktop-shortcut "Main Menu" (if you closed the main menu window)
--2.2.Press [c]
--2.3.PkgToolsBuildos starts
--2.4.Go to BuildOS Tab and click Load Rom.Select which Packages to include and press the green play button[Go]
--2.5.When this process is completed you'll have your OS.nb inside the "temp" folder and the (final product) RUU_Signed.nbh is generated in two places,
(i)..\CustomRUU\ <= For flashing CID Unlocked phones
&
(ii)..\RUU\ <= For flashing CID Locked phones using SoftSPL
NOTES:
A) Ref_XIP folder inside Prepare_XIP is the latest 3.10ROM's XIP, but modified as follows:
-removed modules:
cachefilt.dll, hd.dll, mencfilt.dll, osaxst0.dll
-removed files:
boot_ms.rgu, bmui.nb0
-edited files:
boot.hv, boot.rgu,
Code:
REMOVED ENTRIES:
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Filters\CacheFilt]
"Dll"="CacheFilt.dll"
"Order"=dword:2
[-HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Filters\CacheFilt]
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Index"=dword:00000001
"Prefix"="DRM"
"Dll"="lsomacore.dll"
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\LsFilter]
"Order"=dword:00000001
"Dll"="LSFILTER.dll"
[HKEY_LOCAL_MACHINE\Init]
"Launch98"="TimeWizard.exe"
-edited modules:
nk.exe
Code:
RTC is enabled
-ALL MSXIPKernel modules are relocated to achieve better XIPPorting
**If you include LockStreamDRM PACKAGE in your ROM and you use the Ref_XIP as your \ROM\XIP(folder), ADD the removed (from boot.rgu) entries
Code:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Index"=dword:00000001
"Prefix"="DRM"
"Dll"="lsomacore.dll"
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\LsFilter]
"Order"=dword:00000001
"Dll"="LSFILTER.dll"
[HKEY_LOCAL_MACHINE\Init]
"Launch98"="TimeWizard.exe"
in the PACKAGE's *.rgu.
B) Building your ROM
When you are building your ROM you need:
ROM\XIP(ALL FILES and MODULES) ,
ROM\romhdr.bin and
ROM\OS.nb.payload
This option builds the out.bin(buildxip.exe is used)from the XIP(folder).
C) PP Patching is included in the kitchen operation!
You just set your favorite pp size at the beginning(installing) and each Rom you build is already patched!
If you make the following hex change in nk.exe's S000
Aman said:
i've another method for u guys to change the PP. search the 03 15 A0 03 02 15 A0 13 00 10 83 E5 62 C2 FF EB in yours S000 of nk.exe and change the string marked in Red color to 00 00 A0 E1. from there onwards u can simply use the old Multi-platform PP changer.exe (that is also found in kaiser kitchen) to change ur PP on the OS.nb. this should make the kitchen even simpler
PS: this method works regardless of the device
Click to expand...
Click to collapse
then the kitchen's PP Patching doesn't work!
You should use the suggested by Aman Multi-platform PP changer v2.21 which is included in the kitchen's panel!
NOTE: I don't have an ELF to test, but after the above change then I think that the pp size is the same for both ELF&ELFIN(not dynamic).

Nice job Kokotas.

great job bro
i would like to test ur kitchen.

Repository:
ElfinCustomRUU.exe
ElfinTask29.exe
Task29&CustomRUU
B2_Kitchen_GUI_Setup
B2_Kitchen_GUI.exe

kokotas said:
Thanks man, but it will be great only if it works for everybody!
I'll pm you the password for the download link.
Regards!
Click to expand...
Click to collapse
TOGETHER we all can MAKE SURE that it works for everybody

how can I obtain pass? I will translate ebglish rom to Turkish and I need that tool..

Nice work.
Not going to switch right away at the moment.
But this looks very good.

I'm on the lookout for a cheep Touch so this will come in handy if I get my hands on a touch....

gullum said:
I'm on the lookout for a cheep Touch so this will come in handy if I get my hands on a touch....
Click to expand...
Click to collapse
gullum I have touch and I can't wait to cook a new room for touch

ill have a go i got a rom on my phone that that is needed in the upgrade rom list but i have been able to remove it

Project for work
i need to lock down some features of my works PDAs and would love to try your kitchen to attempt this.
can i have a password?

Got a Touch tonight for under 200$ used of cause so now I want a kitchen to make roms

kokotas said:
Sit taken
Click to expand...
Click to collapse
Well deserved!
Gr8 job, Ill keep an eye.

This is fantastic and I'd like to try it. I'd like to cook my rom using this kitchen. Would you pls. give me a password.

Removed password protection!The download link is open for everyone!
Read 1st post before starting to play with it!Get used to it and read carefully!
Some features are NOT tested yet!
Hope to hear some good news!
Even better...hope to hear that someone makes it better!
I'm done!Back to my readings and to Solid State Physics(I hate that lesson)
Best Regards!

This is on it's way to my pc now thanks in advance
I've already changed Bepe's kitchen to fit my cooking but this one seams more advanced so thanks again

kokotas said:
Removed password protection!The download link is open for everyone!
Read 1st post before starting to play with it!Get used to it and read carefully!
Some features are NOT tested yet!
Hope to hear some good news!
Even better...hope to hear that someone makes it better!
I'm done!Back to my readings and to Solid State Physics(I hate that lesson)
Best Regards!
Click to expand...
Click to collapse
u need to modify the Create_ROM_for_ELF.bat file used for Ervius' buildOS tool. its not working right now, pls check it

[11/Sep/10]ROLLUP STICKY - ALL GUIDES - LINKS - BEGGINERS - MUST READ - HTC Elf.

quick links :
Posting rules
Contact our forum mod for any problems or concerns.
USPL - CID Unlocking
HardSPL - CID Unlocking
Rom Update Utility error codes & solutions
GoldCard - Unbricking a dead device
Jtag - Unbricking a dead device
Elf(in) kitchens - Creating your own ROM
Click to expand...
Click to collapse
~.~​
notices :
if you have the cdma version check the vogue forum.
respect the rules & check in questions&answers for known solved problems.
elf&elfin look the same but they are not! Make sure you know which one you have and do not do anything that is meant for the elf on an elfin, and vice-versa.
if you can't find what you are looking for, use the forum's search engine for better results!
don't try anything with your phone if you're not sure...and to be sure you have to search,read,try to understand & then if you're still unsure ask for help before messing up your phone!
being grateful is a virtue!so...don't forget to donate to xda developers if you want to support this great forum & it's effort.
don't post in this thread!
Pm me or our forum mod for any suggestions, complaints, dead links, etc.
Click to expand...
Click to collapse
~.~​
contents :
new to all this!
information,etc.
unlocking,making backup,etc.
flashing roms
modifying,cooking,etc
troubleshooting guides,etc.
tests,projects,links,etc.
Thanks, Contact Us, Change Log.
Click to expand...
Click to collapse
~.~​

...Better get informed than flamed...
...Cause the next best thing to knowing something is knowing where to find it...​
Click to expand...
Click to collapse
1. General
(1) General Guide for For all users of the HTC_Touch (Needs updating)
(2) Wiki info for the GSM version of the HTC_Touch
(3) HTC Touch Technical Specifications
2. Useful terms
(1) Technical Terms
(2) Glossary
(3) NOR_vs_NAND
(4) CPU Texas Instruments OMAP 850
(5) Services & DLL's - Descriptions/Functionality
3. Some things you should know about your device
($) All the below info (and many more..) could be retrieved using dsixda's All-in-one tool to find your Device ID/CID/IPL/SPL/IMEI/Serial etc.
(1) Available ROM & RAM size
(Go to Start Menu/Settings/System/Device Information/Hardware and check the
Code:
"RAM size"
"Flash size"
in order to make sure which version (Elf or Elfin) of the Touch you have as it is stated in 1st post of this thread)
(2) IMEI (To get your IMEI just dial *#06# and a 17-digits number will show up. Keep somewhere the first 15 digits)
(3) Initial_Program_Loader(IPL) & (4) Second_Program_Loader(SPL)
(To Find your Device's IPL&SPL version enter bootloader. Note the version numbers)
(5) Device_ID(DID) & (6) Country[or]Contract_ID(CID)
(To Find your Device_ID(DID) and Country[or]Contract_ID(CID) follow this guide or this alternative)
4. Educational Reading
(1) Kaiser's G.W.E.N.I. (It may be for Kaiser, but you'll learn a lot reading this)
...

...The action starts!Better be careful!...
...
...The road to hell is paved with good intentions...​
Click to expand...
Click to collapse
5. Create your GoldCard (Unbricker in case of emergency)
(1) Wiki Guide for making your GoldCard (Will save your phone if you can find a Shipped ROM with the same Model ID)
(If the new wiki is still not ready check out this post here)
6. DumpRom (Basically a way to back up your device's original OS - Does not back up any personal info nor any user-installed applications)
(1) Dumping your device's ROM, Radio, MainSplash, etc.
(2) Guide for Dumping your device's ROM
(3) Invisible ROM dumper
(4) Dumping your IPL
(5) Dumping your SPL or Alternative Way
(6) Dumping your MainSplash
7. CID Unlock your phone (So that your phone will accept other ROMs with different CIDs & you'll be able to flash custom Roms or Roms from other carrier. You could do that in another way described in 10. Flashing Roms)
First, know the differences between a USPL, Hard SPL, temporary SPL, etc. (click here)
(1) Elf&Elfin HardSPLs (Free CID Unlocking)(Recommended!)
(2) Elf USPLs (Free CID Unlocking)
pof's patched 1.11.0000SPL
htctouchp's patched 1.17.0000SPL , patched 1.19.0000SPL <= Use these if your original SPL is 1.1X.0000(or your IPL is 1.1X.0002)!
(3) Elfin USPLs (Free CID Unlocking)
djvw's patched 2.20.0000SPL
htctouchp's patched 2.26.0000SPL , patched 2.28.0000SPL , patched 3.07.0000 , patched 3.10.0000 , patched 3.14.0000 <= Use these if your original SPL is 2.2X.0000(or your IPL is 2.2X.0002) - There are some reports that upgrading the latest manufactured Elf from 1.1X IPL&SPL to 2.2X IPL&SPL was successful, but take your own risk!
(4) Commercial CID Unlocker for both Elf&Elfin
8. After CID Unlocking, better check if it really worked
A safe way to find out if your CID unlocking worked is following this method & check the line:
Code:
g_cKeyCardSecurityLevel = ?
;If ?=0 => Touch=CID_Unlocked => Able to flash any ROM or Radio Update through Bootloader
;If ?=FF => Touch=CID_Locked => Try CID_Unlocking again BEFORE flashing anything
9. SIM Unlock your phone (So that you can use any carrier's SIM)
(1) Free Touch_Unlock (Members report that it's working only for Elf)
(2) HTC TOUCH SIM UNLOCKER FREE
(3) Commercial SIM Unlocker1
(4) Commercial SIM Unlocker2
(5) Commercial SIM Unlocker3
(6) dsixda's free unlocker
10. Available Roms,Radios,IPLs&SPLs
(1) Original Shipped Roms
---(1.1) Elfin's Original Shipped Roms, listed by CID & DID
---(1.2) Elf's Original Shipped Roms, listed by CID & DID
(If one Rom matches your CID & DID, you could always flash it successfully through bootloader. Always means even without CID Unlocking)
But have in mind that Original Shipped ROMs include IPL&SPL that will ovewrite yours and your device will be CID Locked after flashing these!
(2) Elf&Elfin's Dumped Roms, listed by CID & DID
(Consider these Roms as cooked ones, meaning that they can be flashed to your device ONLY IF it is CID Unlocked
or
[alternative1] you use SoftSPL
or
[alternative2] you use JumpSPL)
(3) Elf&Elfin's Custom Roms plus Alternative thread for old ROMs
(They can be flashed to your device ONLY IF it is CID Unlocked
or
[alternative1] you use SoftSPL
or
[alternative2] you use JumpSPL)
(4) Elf&Elfin Radio Updates - Alternative
(They can be flashed to your device ONLY IF it is CID Unlocked
or
[alternative1] you use SoftSPL
or
[alternative2] you use JumpSPL)
(5) Elf&Elfin IPLs&SPLs
(Be careful with these ROM parts)
...

...The fun part!...
11. Flashing Roms("Loading" the RUU_Signed.nbh on your device)
(1) If you have a CID unlocked device (Elf&Elfin) then
either enter bootloader & run the RomUpdateUtility(aka RUU)
or connect your normally booted device (NOT in bootloader mode but in Windows) to the PC ,wait to sync and run the RomUpdateUtility(aka RUU)
Remember to place your RUU_Signed.nbh file in the same folder where RomUpdateUtility.exe is!
(2) If you have a CID locked device & you don't want to mess with the SPL but still want to try another Rom you could:
---(2.1) Use SoftSPL for both Elf&Elfin
---(2.2) Use JumpSPL for both Elf&Elfin
But have in mind that if something goes wrong(Bad Flash or Bad Rom) you'll end up facing any possible problem with a device that is CID Locked!
(3) Open Source ROM Update Utility (RUU)
List of Customized ROMs(Random order)(Your ROM isn't listed here?Pm me to add it ASAP)
Code:
[LIST]
[*][URL="http://forum.xda-developers.com/showthread.php?t=535879"][ROM][WWE][July 23 '09] ELFIN WWE (WM6.5) M2D&BL[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=426540"][ROM][WWE][MAY 30 '10] Onyx WM 6.1 (21057) + WM 6.5.x (23569) + WM 6.5 (21889)[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=339935"][ROM][WWE]V4.0 Blue Touch ROM CE OS 5.2.1921 (Build 18521.0.7.0)[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=509822"][ROM][PDAVIET]WM6.5 ROM V78 (Core 21731) - HTC ELF & ELFin[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=541886"][UPG 12 may 10][ROM][WWE][ITA]Miky 6682 WM6.5 build 23569.[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=634936"][ROM][WWE][24-Apr-2010] ATHAR WM6.5.3-28232[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=569687"]|ROM|6.5.x|19/05| AHEN E6t |23569| - New Rom Uploaded[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=414280"][ROM][WWE][06.09.2008]Touch Surface Roms 6.10.SP0.02[ONLINE][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=551508"]|ROM|WWE|Feb09'10|ELF SX WM6.1 21054|WM6.5 21888|[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=514955"][ROM][PTG][13.05.2009] WM6.1 OS 5.2.20771 JADE Core + Manila2D PTG (black)[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=563499"][15 May 2010] [ROM] WM 6.5 21899 : FULL and LITE[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=640519"]CeROM v1.31 - WM 6.5 Build 28230 || Android [Wing Linux based ROM][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=451100"][ROM][WWE][Oct.11] kwbrs Topix 1.4.1 ELF(in) Unleashed [5.2.21055][Full&Lite][ONLINE][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=397739"][ROM][WWE] HTC Touch Official 6.1 ROM - ALMOST [Tabish ROM v3.3.6.1][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=415880"][ROM][WWE][08 JUNE 09] Touch ESSentiaL v4.5 FINAL [ ;) ][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=432776"][ROM][10-10-08]R2 Opal Rom Port WWE for ELF(in), Full & Ultra Lite[19971.1.2.26][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=646778"][ROM] 05.03.2010 Elf / Elfin C.P. SUPER CLEAN WM6.5.3 28230.571.632 by efsane[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=446217"][ROM][WWE][25.11.08] Vanilla series ELF(in) v2.0 [OFFLINE][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=406148"][ROM][WWE/DAN/NOR/NLD/FRA/GER/ITA/PTG/ESN/PLK/RUS]Throttle Diamond I[ONLINE][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=623867"][UPG 22 04 2010][ROM][WWE]ELFIN TouchofElfin_03 6.5.5 Build 23563[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=356465"][ROM][ITA]Touch (alias ELF) ROM original Rebuilt[ONLINE][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=320407"][ROM][WWE/GER/ITA] HTC Touch Rom with 55mbBigStorage&4mbPagepool 13/8/07[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=447394"][ROM][WWE][FR][Feb. 10 2009]AEther 0.5 + Obsidian flavor 0.2 + New XIP/SYS[ONLINE][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=505879"][ROM][WWE][25 April 09] Made in India v2 WINDOWS 6.1[ONLINE](link corrected)[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=371139"][ROM[WWE]HTC Touch: ROM Code 1.11.707.1B (Soft Black)[ONLINE][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=563628"][ROM][WM6.5][Elfin] Build 23071[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=373791"][ROM][GER][02.03.08]Piko ROM Wm6.1 Elf & Elfin[ONLINE][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=430204"][ROM][WWE][26.11.08]Official 3.10.710.0 WM 6.1 ROM - TrueG Edition[v4][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=573970"][ROM][WWE][UC][7-Dec-09] AGS Series WM6.5 21877 & Beta 28009[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=545743"][ROM]Windows 6.5 ROM 23071 Final Release SEN V1.0[/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=554043"][ROM][WWE][AUG 30 '09]khatri's 6.5[ONLINE][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=483078"][ROM][WWE][Feb 15] LeTama 21159.3 (WM 6.5 beta) updated 02/22, small changes [Online][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=392637"][ROM][WWE][20753 1.4.0] UC2.0 + Mortscript Ultra Clean Edition [OFFLINE][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=364901"][ROM][WWE]NEW 4|18|24MB Pagepool. Blue Elves ROM V5.0 (Build 19521)[ONLINE][/URL]
[*][URL="http://forum.xda-developers.com/showthread.php?t=369385"][ROM][WWE]Elf(in) ShadoW 2.1 TE[ONLINE][/URL]
[/LIST]

...Going deeper! #1...
...
...What we hope ever to do with ease we must learn first to do with diligence...​
Click to expand...
Click to collapse
12. Kitchens that work for Elf&Elfin (The "programs" used to rebuild/modify Shipped Roms & produce Custom Roms)
(1) Anichillus - Hypercore (Presented in Noonski's Cooking Class. Many things to learn there!)
(2) bepe - BETA: Extended Elf/Elfin Kitchen for WM6.1
(3) Ivanmmj - EasyPortOven V2.2 (Discontinued)
(4) Ervius - buildos+packagetools 4.2b3 & version 4.3b1
(5) Noonski - SuperProCore Kitchen (Discontinued)
(6) Kokotas - ELF(in) Kitchens
(7) Linux ROM Kitchen
(8) Noonski - o.r.e.e. wwe v3.07.720.05
(9) PPCKitchen.org - XIPKitchen
(10) Ervius - Visual Kitchen
(11) Vistang - Visual Kitchen
(12) Ivanmmj - SuperJustKitchen
(13) Airxtreme&OndraSter - OsKitchen
13. Modifying&Cooking stuff
(0) Noonski's Tutorials
(1) OEM Package Tutorial
(2) Full XIP Porting (& MANY MORE Guides) - XIP & SYS Porting Guide
(3) What's The Pagepool (Size) All About?
---(3.1) Universal ELF/IN 1.1x , 2.2x & 3.xx Roms PP Changer (Use this if you want to change the PagePool size for the ROM your device already runs(after flashing)) ,
---(3.2) PagePool Smart Changer(Works as the above but only for (old) 1.1x.xxx.xx ROMs) ,
---(3.3) Changing Pagepool for 2.2X.xxx.xx ROMs(Read this guide if you want to change the PagePool size on the ROM(*.nb or *.nbh file) before(!) flashing)
---(3.4) Changing Pagepool for 1.1x.xxx.xx ROMs(Works as the above but only for (old) 1.1x.xxx.xx ROMs)
---(3.5) Changing Pagepool for 3.XX.xxx.xx ROMs is similar to 2.2X.xxx.xx ROMs with only 1 difference
(4) Creating MIDlet shortcuts in start menu, and changing the shortcut icon
(5) Changing startmenu icon (You may need msigner) - Rename "Start" in system tray
(6) How to remove SQM (System Quality Metrics)
(7) SDAutoRun - User Customization
(8) UC ROM SDConfig.txt Builder
(9) AppToDate
(10) International MUI for Localizations
(11) How to tweak a rom because of size limitation(You could bypass that limitation(50MB for our ELF(in)s) using your SD card for flashing[This short "explanation" may help you understand])
(12) G'Reloc & other tools
(13) Tadzio's tools
(14) itsme's tools
(15) mamaich's tools
(16) bepe's Package Tool
(17) Powerful xip porting tool: XIPAddrTools 2.0
(18) QuickCab 1.0Cab
(19) SASHIMI AutoInstaller
(20) nbimg: HTC splash screen tool
(21) Cube Customization
(22) XIAMultiTheme
(23) Windows Mobile 6 Professional Emulator
(24) MortScript examples accumulation - Mortscript's Manual - Mortscript's Manual(HTML)
(25) cmonex's RomTools Pack
(26) htc ROM Image Editor
(27) DSMBuilder
(28) Noonski's Cooking Experiments & OEM packages - A Little Cooking Secret
(29) How to change ROM Date
(30) Increasing Touch Sensitivity
(31) [TUT]Apply your registry tweaks with a simple CAB file!
(32) Speed up OEM ROMS with NETCF3.5 without cooking
(33) HOW to translate ANY ROM
(34) File Explorer Extension v.2.03
(35) Opal/Jade Apps & Manilla2D Extraction Thread
(36) Download links for Dumped ROMs & XIPs for cooking
(37) Ather90's OEM Packages
(38) UPX Reference Post
(39) List Of .lnks
(40) Manilla 2D Home Settings XML Explained
(41) ULDR Removal for Elf/Elfins
(42) Change settings for all Notifications
(43) Chef Central
(44) Extendir - file system filter driver that optimizes performance
(45) Universal Tutorials
(46) OEM -> EXT rebuilder
(47) XDA_UC
(48) The Windows Mobile Image Update System
(49) Manila Development Tutorial
(50) IMGFSFromDump-TURBO
...

...Going deeper! #2...
(51) xidump v1.0 Beta
(52) NBH handling tool
...

...Got any troubles?Read here!...
...
...Clear your mind of can't...​
Click to expand...
Click to collapse
14. Troubleshooting guides
(1) Stuck in bootloader
(2) Dead[or]bricked Elf&Elfin
(Ultimate guide - All you need is there - DO NOT open a new thread for every dead device in this planet!)
(3) "Data crashes" when SIM card inserted (Not available yet, but check following links for help: link1 & link2)
(4) ActiveSync Fails
(5) Bootloader [mtty] commands
(6) RUU Error Codes List
(7) Goldcard (Potentially a Limited Unbricker) for ELF/ELFin
(8) Unbricker ROM
(9) HOW to fix turning off HTC ELF
(10) Unbricking solution for Elfs in 3.xx bootloader
(11) How to Jtag a HTC Touch Elf(in)
15. "Manuals"
(1) HTC ELF / Touch Service Manual
(2) How to Completely Disassemble the HTC Touch (check post 22 for a pdf)
...

...Interesting things going on...
16. Alternative OS running on Elf
(1) Linwizard/ Linux running on Elf
(2) Android running on Elf
17. Benchmarking Tests
(1) Difference between SPLs
18. Projects
(1) Touch Surface // The Cooking begins! [OFFLINE]
(2) UC2.0 + Mortscript Capable New Ultra Clean concept ROMs [OFFLINE]
(3) New XML customizable full screen today screen
(4) Shaps New UI - Touchxperience
(5) Manila 2D 2.0 on ELFin
(6) WP7 Porting/Tool Development
19. Useful Links
(1) Touch Friendly Programs for the Windows Mobile
(2) Tweaks&Tricks
(3) MSDN Library
(4) The (Java) MIDlet Bible
(5) All Opera Mobile/Mini version
(6) GPRS/Internet Connection Settings for the whole world
(7) Windows Mobile Themes
...

Mini guide for new users
A. Preparation
0.READ & understand some terms so that communication will be easier among us:
http://www.1800pocketpc.com/glossary
http://wiki.xda-developers.com/index.php?pagename=FAQ#techicalJargon
Then you may go through the links and guides of this rollup and get informed!
1.Find your Device ID , CID , etc:
http://forum.xda-developers.com/showthread.php?t=418892
2.Make a "GoldCard":
http://wiki.xda-developers.com/index.php?pagename=Elf_GoldCard or http://forum.xda-developers.com/showthread.php?t=437996&page=2#15
3.Make a backup of your current ROM and keep it:
http://wiki.xda-developers.com/index.php?pagename=Elf_HowtoDumpRom
4.Save your personal info(contacts,mails,etc):
Use whatever method you want...(eg. PIM Backup, ActiveSync, etc.)
B. Now that you have saved every important file and info for your phone you are good to go...
5.CID Unlock your Touch:
http://forum.xda-developers.com/showthread.php?t=445666
Use the NEW! Hard-SPLs!
or
http://forum.xda-developers.com/showthread.php?t=408637
Use the right USPL & IPL for your phone!
6.If CID Unlocking worked, you will be able to change the ROM, the Radio & the SpashScreen of your phone using the RomUpdateUtility(RUU)
and start having fun!
*.I'm sure all of you want the best for your device - after all that's why we all come here. But what is best for me is not always best for you too, meaning that it's a matter of personal taste. So please don't start asking which ROM is the best or fastest , etc.
If you have followed the above steps (0-5) then you have the opportunity to try out many different ROMs that are released here and see which one fits your needs. And there is always the option (if you didn't come here just to take and leave) to learn how to create your own ROM and build it according to your taste!

kokotas is the champ ! A great job. A perfect thread, Thanks for the help buddy.
If you are having any problem related to the Forum or
Let me know if...
* Forum rules are being broken.
* A thread or post needs moved or deleted.
* You have ideas for how to make the HTC Elf forum better.
You can PM me madnish30(Forum Moderator) here is the link you can use to PM me.
Now , if you have a problem with your device i.e. Elf and you can not seem to solve it at all. ( Be sure you have searched for the solution. ). Please do not post thread here and there, instead you can contact my team of helpers:
kokotas PM
captainstu72 PM
saurabh88 PM.
Please CC' your PM to me as well.
Please DO NOT SEND THE SAME ISSUE TO MULITPLE Helpers, Doing so can get you into trouble.
Enjoy The Forum, Respect The Forum.
change log :
Code:
[list]
[*][27.07.10] - thread revised and structure changed
[*][19.06.10] - added link for "how to jtag a htc touch elf(in)" @ post #5
[*][09.04.10] - all posts reviewed ! Updated info - fixed dead links
(needs some more work...)
[*][03.01.09] - added link for "notifications settings guide" @ post #4
- added link for "xdafbppc" project @ post #6
[*][06.12.08] - fixed link for "xipporterex" by ervius @ post #4
[*][06.12.08] - added link for new kitchen by ervius @ post #4
[*][02.12.08] - added link for new tool "xipporterex" by ervius @ post #4
[*][16.11.08] - added link for "unbricker rom" @ post #5
[*][14.11.08] - added link & simplified instructions for new hardspl 3.07 @ post #3
[*][13.11.08] - added link for new kitchen o.r.e.e. Wwe v3.07.720.05 @ post #4
- added link for uldr removal for elf/elfins @ post #4
- added link for upcoming new xipkitchen from ppckitchen.org @ post #4
[*][06.11.08] - added link for new uspl 3.07 @ post #3
- fixed link for questions&answers @ post #1
[*][23.10.08] - added link for manual full xip porting @ post #4
- added link for goldcard project(potential unbricker) @ post #5 & #3
[*][26.09.08] - added link for editing the "start" text of the start menu @ post #4
[*][20.09.08] - added link for m2d_settings_xml explanation thread @ post #4
- added link for midlet_"bible" thread @ post #6
[*][19.09.08] - added link for upx reference thread @ post #4
- added link for list_of_.lnk thread @ post #4
[*][18.09.08] - added download links for dumped roms & xips for cooking @ post #4
- added link for ather90's oem packages @ post #4
[/list]
Click to expand...
Click to collapse
~.~​

[Release] [Kitchen] - SuperJustKitchen v0.7 - Shields up!

SuperJustKitchen v0.7 Released.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices.
Word of warning:
None of the new EXT's have been tested and fixed for the Herald, Opal, Hermes AND Artemis. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.)
(I'm no longer updating each thread separately for each device but just updating my site and posting the release info here.)
Quick Links
FAQ
Installation Walkthrough
Kitchen Usage Walkthrough
Change Log and Known Bugs
Download Links
**Warning**
Before using this kitchen, you MUST read the walkthrough. Any questions that have been answered there and in the FAQ will be ignored. This is your only warning.
**Disclaimer**
I am not responsible for any damage that may be done to your phone with a ROM created in this kitchen.
I am not responsible for any damage done to your computer.
I am not responsible for anything... at all.
Introducing SuperJustKitchen!
​ SuperJustKitchen is based on ervius's excellent Visual Kitchen.
Features
A completely stripped ROM. All the files have been categorized in order to remake packages of all the programs that come stock on the HTC ROM.
LZX and XPR compression
6.1 and 6.5 support
Auto XIP and SYS porting
Auto ULDR removal (Gain 3mb of storage.)
Auto NBH packing
Auto Flashing (for testing your ROM before it's released to the wild)
Simplified structure. Click on RunMe to run and Support for support
Script to convert old OEM packages to new EXT packages
Auto file conflict fix (don't have to removing older file that conflict (not that there are any. )
Script for auto UPX compression of EXT folders
Script for auto compression of all PNG's in the kitchen
Save custom ROM settings (for cooks for multiple ROMs)
And more!
Builds included
21054 - WM6.1
21869 - WM6.5 with older GUI - Newer internal code - COM2 branch​ 23071 - WM6.5 with new redesigned GUI - COM3 branch
This is now an ENGLISH only kitchen. It is just too hard to keep up with 13 different languages! If anyone is interested in taking over the other languages, please let me know.
NOTE: In order for me to keep track of whether my time was well spent or wasted, if you use this kitchen to make a ROM, please either include SJK in the name or just mention that it was SJK cooked in your ROM's thread.
NOTE: This kitchen assumes that you know how to flash through SD, recover from a bad flash and are able to backtrack your steps to figure out how you broke your own ROM. If you do not understand these, please learn them first. Do not PM me asking me. I have written numerous walkthroughs on all these except on how to backtrack your steps. For that, just remember what you're doing as you do it and keep backups.​

FAQ
FAQ
Q: Can you get me package YYYY?
A: No. I will provide packages as I create them. I will not take requests. It takes a LOT of time to make a package, especially when I'm making it for 13+ languages. It takes a long time to find the corresponding packages or to create them from scratch.
Q: Will this work on my [Insert device other than Herald/Wing]?
A: Not, yet. That is why it's posted on the Herald forum.
Q: Will I be able to recreate JustHome or JustStable with this kitchen?
A: No. This is a completely new base. I made this kitchen and these ROM base from scratch.
Q: Will you personally teach me how to....?
A: No.
Q: My phone won't boot after flashing your ROM!
A: You disabled something you needed. Keep track of what you disable and then reenable the stuff that you need.
Q: My phone is bricked!
A: You didn't follow the instructions!
Q: When I use this, I get an error.
A: You didn't follow the instructions!
Q: How do I flash this?
A: It's not a ROM.
Q: How do I flash a ROM I make with this?
A: You must know how to flash before you use this. You must know how to recover from a bad flash. You must know the difference between USPL and HardSPL. You must know how to flash through the SD if needed.
Q: Will this work with Windows XP, Vista or 7?
A: All of the above. Just remember to follow the install instructions.

Walkthrough
Installation:
Step 1
Download the newest build from the download links.
Step 2
Extract the SuperJustKitchen folder into c:\kitchens\
Now you should have c:\kitchens\SuperJustKitchen\RunMe
Step 3 (Optional)
Extract the SuperJustKitchen shortcut into your desktop.
Step 4(Vista and Windows 7 only)
Go to your Start Menu and then click on Start Search or RUN.
Type in "c:\kitchens\SuperJustKitchen\Working_Folder\" without the quotation marks and press Enter.
Right click on erviuskitchen and click on properties.
Click on the Compatibility tab.
Place a check mark on Run this program as an administrator.
Press ok.

Change Logs and Bug Reports
Known Bugs
23047
No known bugs
21864
No known bugs
21064
Older Arcsoft don't work with this
All builds
No known bugs
******************************
Change Log
Unreleased
To-do for Future Release
Info ported to Herald
Info integrated into kitchen support script
Enhance kitchen support script to auto upload support information
Enhance support script to include system information
Enhance script to give option for kitchen host support and ROM/Device support
Add built in HardSPL installer (if you can use USPL, you can also HardSPL.)
Expand RunMe script to encompass support script and HardSPL.
Once info integration is completed, create script to auto detect incompatible phones
If phone is Herald and the IPL version is lower than 4.0, auto update IPL and SPL to newer IPL/SPL before automatically HardSPL'ing phone.
Include "restore to factory default" option. (Autodownload needed RUU from server, USPL into phone to override HardSPL.)
Indepth Cooking walkthrough to supplement kitchen walkthrough
Scripted installer with desktop shortcuts
Scripted Simple new build Port assistant
Much much more
Released
0.6
Cleaned up the Herald's initflashfiles and older packages (This fixes the double control panel icons.)
Ported 21869 and 23071
Cleaned up the Opal OEM a little.
Organized some EXT into categories. (This is still a work in progress.)
Starting with v0.6, I've created a script on my end that will automatically compress the kitchen and separate it into multiple parts:
SJK - The main kitchen files.
OPAL - The Opal files.
HERALD - The Herald files.
SYS - The Build files (Both SYS and XIP.)
EXT - The EXT files.
This should make it easier to update things from now on. I'm going to have scripts to only update certain things. This way, you should only need to download whatever has had the changes, instead of the whole kitchen. Later on, I hope to create an updater that will do these updates for you automatically. (At first, I won't be able to update the EXT without deleting any custom EXT's added by you, the user.)
0.5
English only support
MANY new EXT's (multiple versions for now)
Opal support
All EXT's are being categorized... work in progress
0.4
Added updated packages for the programs that are language agnostic.
Added 23060 and 23420 builds. Fixed their button issues by using 23053 to fill in the blanks. (230xx's are more stable, 234xx's are newer and have more features as well as more bugs.)
Added descriptions to every package (albeit, they're a little more technical that I wanted, but I got them straight from Da_G's mouth, so they're bound to be correct.)
0.3.1
I only left 3 builds. The newest 6.1, the newest 6.5 with the old gui and the newest 6.5 with the gui (23047, it's really nice!)
0.3
CABtoEXT - Thanks to Apreinchner - Update: Edited the script heavily (it went from 4 lines to 88 lines) in order to make it sort out and move all the newly created EXT's appropiately.
Ported 23034 all languages - even MORE gui changes!
Ported 23037 - stable
Ported 23409 - Again, MORE GUI changes! (A few bugs, though.)
Converted many of the problematic modules to files in the 23034
Change the all the languages' start menu on the 23034 build CPR to 4
Change ROM version to show that the ROM was built on SuperJustKitchen
Fix Adobe bug
Change ROM version to show that the ROM was built on SuperJustKitchen
Port other languages from 23031
Integrate Sort program into prepare structure - Script it
Presets for each build
Addition of 7 more languages?
Clean ROM more
0.2
Russian initflashfile.dat fixed - 6.5 start menu works fine now
Port 23028 0409 96dpi - deprecated
Change landscape mode in 21016 and 23028 to show 4 icons instead of 3
Script new EXT folder creation - extra buttons
Fix cab and sync bugs in 23016 and 23028
Port 21054 all languages (newest (and possibly the last) wm6.1)
Remove extra netcf's, extra dummy fwupdate, extra SQM's
6.5 compatible autorun
Port 23031 0409 96dpi
updated all language initflashfiles
Fixed issue with SMS on 6.5 builds
Fixed ActiveSync issues
Replace all start menu icons in all 6.5 in all languages with nicer ones
Empty folders disappearing fixed - different installer (placeholders fix it but some of those folders have to be empty...)
Remove compatibility for all other DPI's and resolutions other than 96dpi/320/340 for now to keep size down.
Remove compatibility with languages that aren't compatible with the Herald for now to keep size down.
0.1
Initial Release

Download Links
v0.4+
Just go to the new redesigned http://justkitchen.infoand click on the download section and then on the kitchen section.
v0.3.1
Version 0.3.1 is
SuperJustKitchen - With 21054(wm6.1), 23016(wm6.5), and 23047(wm6.5 with redesigned GUI.)
It's just one file with a ReadMe with instructions on how to install it.
v0.2
Version 0.2 is
SuperJustKitchen - With 21054(wm6.1), 23016(wm6.5), and 23031(wm6.5 with redesigned GUI.)
It's just one file with a ReadMe with instructions on how to install it.
v0.1
Version 0.1 was seperated into different pieces.
Main Kitchen Installer
SuperJustKitchen v0.1 - Alpha 1
Device Specific Installer
Herald
Build Installers
21051 - WM6.1
23016 - WM6.5 - Original WM6.5 interface
23022 - WM6.5 - The "new" WM6.5 finger-friendliness
EXT Installers
Non-DPI Specific EXT

Cooking Walkthrough
Cooking with SuperJustKitchen
*Warning: This is NOT a walkthrough on how to cook. It is a walkthrough on how to use this kitchen.*
The Layout
The Kitchen is stored in c:\kitchens\SuperJustKitchen\
To simply run the kitchen, double click on RunMe.
Advanced users: There will be a different walkthrough for you. (As far as how to add packages, builds, etc.)
The Usage
Once you doubleclick on RunMe, you will be greeted with the main kitchen window.
Here is a screenshot of the process. Use it to follow the steps.
{
"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 1 - Click on the Device drop down menu and choose Herald (Yes, even though it already says Herald.)
Step 2 - Click on the language drop down menu and choose your language. To find what the language codes mean, see the first page.
Step 3 - Choose a XIP.
Step 4 - Choose a matching SYS.
Step 5 - Make sure you enter a build number other than 2.00.00 in the field near these. Use 5.2.21051 or something similar instead. If not, the ROM will not flash.
Step 6 - Doubleclick on the packages that you want or don't want. (Green means enabled, gray disabled.)
Step 7 - If you want LZX compression, check the LZX Compression.
Step 8 - Click on create ROM.
Wait.
If you get any errors, you probably did not choose a build/language combination included. Look at the list of languages to see what I mean.

Credits
Credits
Ervius for his wonderful visual kitchen (you'll find a donation link for him under Working_Folder.)
HTC for making the HTC ROM
mrhayami for his brainstorming sessions with me to make the recursive scripts
Everyone else that I haven't mentioned

Advanced Tips and Tricks
Advanced Tips and Tricks
This section will detail both advanced cooking tips and advanced usage of my kitchen.
Kitchen structure:
If you notice, the structure of the kitchen is different from the old kitchens.
The only folders you need to worry about are the following:
Cooking Folders
EXT - This is where you would add new programs. EXT packages are similar to OEM packages, but they have a slightly different layout. They are processed by the kitchen after the OEM, so their settings are never overwritten by the stock settings of the base ROM.
OEM - You'll notice that within OEM, you have a HERALD folder. The reason being that this kitchen supports multiple devices at a time. Within the Herald folder, you'll notice several folders.
The .VM is used for memory mapping. DO NOT TOUCH THIS under ANY circumstance.
The COMMON folder where you would find most of the what you'd normally see in your old style OEM folder. (OEMAPPS, OEMDRIVERS, etc.)
Various folders named with 4 letters/numbers. These are language packs. They used to be part of the OEM folder but have been seperated to allow the kitchen to choose which language to cook more easily.
ROM - Inside you'll notice the following:
Device specific folder - Holds all the device specific XIP files/modules, including the nk (which is NOT a native 6.5 kernel.)
SHARED - Where the non-device specific parts go. This is what gets "ported" automatically by the kitchen. This makes it very simple to release upgrade ports to the kitchen.
SYS - The OS files. These are also divided by language, DPI and by resolution. (QVGA, SQVGA, WQVGA, VGA, etc etc) You will only be able to choose DPI's and resolutions compatible with your device.
Other folders:
RELEASE_Device - This is where your flashing software is and where the ROM ends up at in NBH format.
Prepare - I store things here for different reasons. At the moment, it holds the template for a 13 language EXT package.
Other features:
Extra buttons: Click this to access extra features.
The EXT version lets you choose between different EXT's compatible with different DPI's with the common ones (compatible with all DPI's) always displaying.
To be continued...

---Reserved---

Yep, still reserved.

It's still a work in progress, but I am ready for comments.

ivanmmj said:
It's still a work in progress, but I am ready for comments.
Click to expand...
Click to collapse
Commented. I'm trying it out now...figuring out how to work it.

Hah, love the FAQ
Question: For WM6.5 builds, do you have to check the Real WM 6.5 AKU box on the main kitchen screen? Or does it not matter? (I'll be finding out in a minute, anyways, lol)

i may have found a bug. I dont know remember the packages i chose but when it comes down to creating the rom i get a kitchen_build_rom.bat error. i dont get that anymore after altering the packages with HERALD, 409, EXT 0096, 96 DPI, dpi_96_resh_204_resv_320, 1.01.23016 ver., 23016 XIP, 23016 SYS.
Also, i havent been able to create a flash able rom yet. how do you reset the settings to default?
Edit: forgot to mention im on windows 7 build 7100. And yes i did do what was required on the 1st page.

I keep getting a file is corrupt error when I try to flash?

eichenberg said:
I keep getting a file is corrupt error when I try to flash?
Click to expand...
Click to collapse
Yo tambien.
The FAQ says that we didn't follow the instructions, lol.
My NBH is +50 MB, so idk what's the problem....hmm...

Wow works great! Im flashing through SD though. Just made a quick 6.5 build came out with 67.41 Storage and 25 ram

illconcepts said:
Wow works great! Im flashing through SD though. Just made a quick 6.5 build came out with 67.41 Storage and 25 ram
Click to expand...
Click to collapse
Yea, I think the .NBH files have to be over 50 MB in order to flash through PC. Anyone confirm that? (I'm trying out a 6.1 build, with the new Motorola homescreen, cuz it's sick)

ace10134 said:
Yea, I think the .NBH files have to be over 50 MB in order to flash through PC. Anyone confirm that? (I'm trying out a 6.1 build, with the new Motorola homescreen, cuz it's sick)
Click to expand...
Click to collapse
Let me know if you get that Moto home to auto start... im stumped.....

ace10134 said:
Hah, love the FAQ
Question: For WM6.5 builds, do you have to check the Real WM 6.5 AKU box on the main kitchen screen? Or does it not matter? (I'll be finding out in a minute, anyways, lol)
Click to expand...
Click to collapse
Do NOT check it. It will attempt to set all the modules to use another set of virtual memory that is not available to our NK.exe. It's only for originally 6.5 devices.
DestructDez1 said:
i may have found a bug. I dont know remember the packages i chose but when it comes down to creating the rom i get a kitchen_build_rom.bat error. i dont get that anymore after altering the packages with HERALD, 409, EXT 0096, 96 DPI, dpi_96_resh_204_resv_320, 1.01.23016 ver., 23016 XIP, 23016 SYS.
Also, i havent been able to create a flash able rom yet. how do you reset the settings to default?
Edit: forgot to mention im on windows 7 build 7100. And yes i did do what was required on the 1st page.
Click to expand...
Click to collapse
What was the error and what do you mean altering? I made this kitchen mostly on Windows 7 build 7100.
As far as default settings, I didn't include a default ROM. There are many things you should not disable if you want a booting ROM.
eichenberg said:
I keep getting a file is corrupt error when I try to flash?
Click to expand...
Click to collapse
If your ROM is smaller than 52100kb, then it has to be flashed through your SD card.
ace10134 said:
Yo tambien.
The FAQ says that we didn't follow the instructions, lol.
My NBH is +50 MB, so idk what's the problem....hmm...
Click to expand...
Click to collapse
How big is it? See above answer.

incl. ROM now: WM 6 updated Tornado kitchen with SDHC + 28/25MB total/avail storage

This kitchen is a continuation of the Nitrogenious kitchen released at XDA-devlopers.
Nothing has changed from the tools side, only subtle adaptations and altered content.
Thanks go to :
all the experts at XDA-developers (too many to list)
Nitrogenious for releasing his WM6 kitchen and the superb WM6 package contained therein.
The original kitchen is found here: http://forum.xda-developers.com/showpost.php?p=2150690&postcount=1
Mind that usage description has to be taken from there!
Cotulla for publishing the OMAP850_SDHC.dll that can handle SDHC cards and llnhhy for putting the crucial REG setting in his published package for the Tornado.
More details are discussed here: http://forum.xda-developers.com/showthread.php?t=576164
SGregory for revealing (at least I found it there) that "format BINFS" can actuall take a parameter that sizes the BINFS partition and thus opens the path to gain device storage space if the ROM gets smaller!
More details on saving space are outlined here: http://forum.xda-developers.com/showthread.php?t=491240
- Sir.B and geistteufel for the Squeezer batches for UPX. XDA-Develpoer threads are:
original: http://forum.xda-developers.com/showthread.php?t=481880 and post of geistteufel (the one used in this release): http://forum.xda-developers.com/showpost.php?p=3540501&postcount=92
Disclaimer:
This is for educational purposes only!
There will be no support for the published content!
Enjoy and contribute.
Warning:
Mind that from the "cooking" or "kitchen" point of view this is for sure an old base and possibly more elaborate tools and definitely newer OS versions exist. The produced files should not be able to "brick" your device if you correctly set the Image Name to "OS" in the last step of the cooking process. IPL or SPL should never be written unless you know exaclty what you do - the kitchen only cooks the OS part! Writing incorrect content to the IPL or SPL area will brick your device for sure, so be careful!
Motivation:
This effort was only done to get a running stable ROM with SDHC support included that occupies as little storage space as possible
still having mandatory elements on board
filling the remaining space with useful tools
Space saving strategies (order of benefit):
outsource parts to SD card where possible (.NET CF 3.5)
compress files (.exe and .dll) that are not stored as modules with UPX where function permitts.
remove files that are not needed for any function
remove media data (ringtones, pictures) and leave only the bare minimum
resize media data where possible to further decrease size
not done, but possible:
- remove optional packages (additional color schemes) (25k)
- remove empty packages (15k)
- summarize registry tweak packages to just one additional package (edit the .rgu) (few kB)
About UPX and builtin BINFS compression:
My experience is that the BINFS compression shrinks a set of example files (.NET CF 3.5 files that reside in the \Windows path) to about 49% while UPX'ed they only take 32% of their initial size. So on average you may gain 17% of the initial filesize in your ROM. The larger the file, the better is usually the gain.
Mind that UPX will only compress exe/dll files (even if they may be named differently, see Total Commander's *.tfx) and does not compress exe/dll that depend on .NET. It works luckily on the .NET CF core parts itself.
You should not compress (even if compression works, these DLLs will not load later):
resource DLLs
menu extension DLLs (context menus)
Updated and altered content:
added SDHC support by replacing the OMAP850_SDHC.dll with an SDHC capable version initially created for the StrTrk. So far there are no negative impacts visible.
altered the titles of the options to indicate the space they take - also UPX'ed size
moved the oemstartup.dll and the relevant pictures to the folder where the optional sounds already resided
added German T9 to the English T9 - so both is installed in the system if you select this. Mind that an additional language is not eating much space (~70k)
added the SafeInboxExtension as an own option to add, removed the InboxExtension from the combined "Group SMS + ..." menu
put moBlue to the latest version (2.1) and adapted rgu content.
added an option for registry changes called "tobbie GUI tweaks" that sum up everything that I think is useful (smaller menus, fonts, scrollbars, value for gamma).
updated the TotalCmd to the latest released version
created several additional packages from the previous default content (CeleTask, ClearType Tuner, ClockOnTop, ComManager, Dopod SIM Manager, .NET CF 3.5, OMAPClock, OxiosAlarms, OxiosMemory)
added a new package for .NET CF 3.5 where the GAC_* files have to reside on SD card. The complemtary ZIP containing the files to copy on SD card are located in the "_Changes" directory.
added the GPSID Settings tool to the GPSID directory
included the SP1 fixes supplied by Nitrogenious (FakeCursor not included)
changed several tweaked menus in the settings -> system tweaks
added options for volume setting of the initial beep and voice tag to the Voice Tag menu in system tweaks, changed category of the [HKEY_CURRENT_USER\ControlPanel\Sounds\VRecBeg] from "Notifcation" to "System" so that only the sounds sent form the VoiceTag are audible when the System sound volume is set to 0.
completely UPX'ed the SYS\MMSCAMCLKSTK *.exe and *.dll (except 2)
replaced the htcmidi.avd with the WM5 version to get back good midi playback,
added the HTCSourceflt.dll (from Nitrogenious SP1) to get midi playback in wmplayer
removed two large files from this directory which are nowhere referenced (CameraRC_*.dll).
updated WM5torage to the latest version (1.90), already setting suitable defaults.
fixed default settings for A2DP
Directory and contents
added a batchfile (you may want to edit) where the %SystemDrive% can be set to any value. This allows to install the kitchen on any drive you like and not on C:\ (the normal systemdrive) as it was mandatory. Mind that the scope of this %systemdrive setting is limited to the batch execution only. You can put the whole environment on a large RAMdisk (~380MB required) - this speeds up the cooking dramatically! A large RAM disk is available from "[ QSoft ] Qualitative Software" (1 year trial for the lite version) - see here: http://members.fortunecity.com/ramdisk/RAMDisk/ramdriv002.htm .
added a subdirectory "_Squeezer" where you find the UPX compression set "Squeezer" also published at XDA-developers (readme contained there). I have used this set to batch compress many files before putting them to ROM.
added a directory "_Changes" where you find the compressed and original versions of the files in equally named subdirectories OEM and SYS like in the WORK path. So in case you want to go back to the non-UPX-ed version they are there. Continuing the UPX-batch directory logic (2_Backup, 3_Compressed) there are further ones (4_removed and 5_changed) to document the changes done to the original content.
The rest of the kitchen is identical to the one Nitrogenious had released.
Download here: http://www.mediafire.com/file/xdiz2xzmote/Tornado_Kitchen_v09_by_tobbbie.exe
Quick Start:
- Unpack to C:\
- read cooking guide at Nitrogen's thread (see above)
- using defaults you get a ROM with: http://www.mediafire.com/file/z3ynij5ynzd/default-settings.gif
- available storage 27,97MB, free after 1.st boot 24,8MB
Correction: If you want to use the moBlue package, please edit the RGU file and add a blank line at the end. Using notepad will ensure that the file stays in unicode format.
Correction-2 (14.10.2010): You will experience that while WMP is playing the backlight will not go off as normal. This can be fixed by replacing the HTCWMPPlug.dll in the \windows directory on the device or in C:\Torn\_Changes\SYS\MMSCAMCLOCKSTK in the kitchen with the attached file.
Please make sure that your device is "SuperCID" before entering the "Format BINFS command. See post 3.
added 20100314: (edited 20100504)
Despite it is really extremely easy to cook your own ROM with the kitchen, let me give you a head start with your old Tornado. I have cooked the default settings to a ROM and added all tools that you need to step from a stock Tornado to the cooked one in a single archive.
Download it from here: http://www.mediafire.com/file/njm040ttoxm/_tobbbie-tornado-WM6(SDHC-NetCF_on_SD).exe
Unpacking it you will find a directory structure:
Code:
_tobbbie-tornado-WM6(SDHC-NetCF_on_SD)
├───1 prepare security
│ ├───1 HTCUnlock
│ └───2 SDA_ApplicationUnlock
├───2 prepare for custom flash
│ └───Utils
├───3 flash latest Radio and SPL
├───4 format BINFS 1b00000
├───5 flash ROM
└───6 copy NetCF to SD
└───Windows
Follow the actions in the directories one-by-one:
You only need to do steps 1 and 3 if you come from an official ROM but Step 2 (lokiwiz) needs only be done once per device.
If you flash another cooked ROM you can start from step 4.
Attention: In case you did not notice yet - the following procedures will completely erase all content that you stored on the device (email, SMS, MMS, ToDo, Contacts - simply everything) - the device will be as if it comes out of the box. So back up your data before you do this!
Here is what to do in detail, how and why:
Prepare security: This means that the restrictive program execution privileges have to be set less firm to allow step 2 to run later.
Connect your Tornado to the PC and let Active Sync connect. First run HTCUnlock-CVS.exe in the directory 1 HTCUnlock. This will install a program on your device. Run the installed program there and restart the device.
After the device has reconnected to Active Sync, on the PC run the program SDA_ApplicationUnlock.exe in the folder 2 SDA_ApplicationUnlock. It should confirm "succesfully unlocked".
Now the device is ready to receive the "SuperCID" that allows to flash any ROM to it, regardless of Operator or Vendor limitations. To be on the safe side later, please enter on the device *#06# and note down the IMEI that the device reports - you will need it later.
This needs only be done once per device - it is a permanent setting that survives all ROM updates.
Go to the folder 2 prepare for custom flash and
make sure there are no files *.bin left from previous device's activities
then execute Lokiwiz.bat. It will prompt you with 4 options:
Code:
U. Unlock
L. Lock
C. CID Unlock (SuperCID)
Q. Quit
--------------------
Type the letter and press Enter:
Input "C" <enter>.
It will copy a program (itsutils) to the device and it should ask you for permission to execute - grant execution and let the batch file continue. You should find 2 new files beside the Lokiwiz.bat (lock-backup.bin and cid-unlocked.bin). Move them to a safe place immediately and do not repeat the procedure or call another option!
Be careful to label these files unambigously (best is to append the device's IMEI to the name - get it with *#06# before and do not use the IMEI printed on the label of the device - as restoring a wrong *.bin file to a device will kill the GSM radio access (Message: Data Crashes, please contact your... when trying to connect to the network with a SIM card inserted).
Now the device is prepared to receive custom ROMs.
Let's first put the last available Radio ROM and SPL (Secondary Program Loader) to the device. Go to the directory 3 flash latest Radio and SPL and execute ROMUpdateUtility.exe. After successfull update the device will restart in the old OS, nothing has visibly changed - you could still use the device as it is, all your data are still there.
Now the preparations start to erase the old OS and flash the new one.
Deactivate USB connections for the Active Sync
Switch off the device and disconnect from USB
Press Camera Key and keep it pushed down while connecting the USB cable to the PC - wait until the 3-color screen appears and release the camera key.
Start ttermpro.exe in directory 4 format BINFS 1b00000
Select Serial and Port USB
Press <enter> in the terminal window, you should get prompt CMD>
enter info 2 <enter> you should see something like:
Code:
Cmd>info 2
GetDeviceInfo=0x00000002
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
HTCSSuperCID ' HTCE
Cmd>
The last line must show HTCSSuperCID ' HTCE.
If you see anything else there (e.g. HTCSVODA0504 㱍dHTCE - which is for an Austrian V1240) the lokiwiz in step 2 above did not work correctly. Still you have not destroyed anything (hopefully) - so to get the old OS start up again, enter ResetDevice <enter> - the device will restart and boot again. Think about what went wrong in the previous steps.
The lokiwiz batch file and the tools behind it are very powerful and can kill the GSM radio access of the device. Be careful with the *.bin files and keep those of different devices clearly apart.
In case you see HTCSSuperCID ' HTCE then you can pass the point of no return (after this the OS and all your data are deleted from the device) and enter at the prompt format BINFS 1b00000 <enter>. (The value 1b00000 depends on the ROM size, so if you use a different ROM, the value may also be different.) After a few seconds the prompt returns and the partition where the OS was stored is cleaned up now. The device will not boot beyond the 3-color screen in this state. You need to flash the new OS in the next step - but before this enter ResetDevice <enter> - the device will restart and return to the 3-color screen.
Terminate the tterm.exe, you will not need it any further.
Re-activate USB connections in Active Sync - you may forget it later.
Enter the directory 5 flash ROM and execute ROMUpdateUtility.exe. The procedure looks the same as in step 3 but takes a little longer. Do not get nervous as the time at 100% extends a few minutes. The device will reboot and bring you to the new OS.
The SD card that shall be used in the device needs to have the NetCF 3.5 files copied to the directory \Windows finally. This is NOT on the device but on the card - you can copy it on the PC while the sd card is in a card-reader or when the device has is mounted, there the path is \Storage Card\Windows
If the device had a SIM-Lock and it rejects your SIM, go to the lokiwiz.bat (again move out all *.bin files) and select "U" for SIM Unlock - again move the bin files in the directory to a safe place (but you should never need them). Mind that the "lock_backup.bin" is just a copy of the current encrypted area in the device. So this file is different after each step you completed before. Worse: if you do not save the FIRST lock-backup.bin you can never go back to this state.
Mind that lokiwiz.bat has worked for me on a Telenor Sim-Locked nordic ROM CID-locked QTEK 8310, so it should work for any other device as well. If you get the dreaded "Data Crashes..." message and your restore of the correct lock-backup.bin did not help either - your last resort is the SIM Unlock service here: http://imei-check.co.uk/c600_unlock.php. It costs you some bucks, but they seem to re-create the encrypted area with the matching IMEI of your device putting it in a SIM-unlocked and CID Unlocked state. Cheaper than buying a new device.
After you have sucessfully flashed your ROM - maybe you try cooking one yourself?

The selected default settings fill the ROM up to the last few hundred bytes. Adding options will surely jump over the next MB border and your ROM uploading preparations will have to format BINFS with a larger size.
If you have not read it elsewhere yet, the standard sequence to uplad a ROM is:
1.) cook ROM (OS part)
2.) determine size and format BINFS accordingly
more see this thread: http://forum.xda-developers.com/showpost.php?p=3439787&postcount=1
3.) upload ROM

If you start from scratch - so your device is still "untouched" by any custom ROM, you must prepare your device to allow the loading of a custom ROM. This happens in several steps to overcome the various security levels that try to prevent this:
Application unlock the current operating system. Look for "SDA Application unlock" this runs on the PC and remotely unlocks (via the Active Sync Connection) the security of the Windows Mobile operating system. This allows tools to run that you need for the next step.
Super-CID your device (and check if it worked!). Look for "lokiwiz" ZIP file in the forum here. Despite orginally created for the "Wizard" model, it also works for the Tornado in all respect, so it does the Super-CID and it does the SIM Unlock. I did it myself on a QTEK 8310 with a Nordic ROM and SIM-locked to Telnor.
To check if it worked, connect the device in Bootloader mode to the terminal program and enter "info 2" (without the quotes). It has to show HTCSSuperCID ' HTCE
Do not care about SIM lock yet, you can do that anytime later if necessary.
Good luck!

Thanks!
Thanks a lot. Nice work. Very useful. Could you please post one with a PRO rom, preferably the 6.5 version? Or at least the guidelines to make one?

I will not cook any further - this is why I released the kitchen. The strategies to save space are outlined in detail, so other cooks can take them and incorporate to their ROMs.
For me WM6 is sufficient - I don't need the "goodies" that came after that.

Thanks!
Oh fine. Thanks anyway. What is the perceived space saved from this method? And is there any performance hit?
I've seen that UPX'ing has a lot of performance boost so I'm wondering whether it can be made only to the packages or is it applicable to the exe's and large dll's from the CABs too. Since there are a few applications, which even when added later, install to the device memory directly. In these cases, UPX'ing might be highly beneficial in reducing the size as well as giving a speed boost. Any info on this?

Well, indeed you may think that UPX-ing will decrease performance as the file must be decompressed before running - but the opposite is the case!
you save space (most if installed, a little if in ROM - due to BINFS compression that is there anyway)
you get faster file-read time: This pays for especially well for large files (opera, office, acrobat, TomTom and alike). This will by far gain more than you loose for decompression (which goes directly to memory).
Looking at usual read-speeds of about 1MB/sec and an assumed 10 times faster decompression speed to memory, my feeling is that for speed reasons it will pay best for LARGE files (card and memory installed). Mind that after the file is read and loaded to memory, still the application needs to initialize itself. The last step is the same, no matter if UPX-ed or not.
If you tweak the bits for memory saving on the device it is no harm for anything smaller as well. Usually I stop UPX-ing below 50kB in size, but to have the ROM fit in the MB-frame I wanted to achieve I also had to UPX some smaller files as well. Just compare the directories of Nitrogenious' kitchen release and mine.

Hi,
Thanks for kitchen !
Sorry, I'm a novice in ROM cooking (I just modified a bit a ROM for my HTC Touch, long time ago, but I got no problem with flashing ROMS on HTC devices )
So I got a few questions/remarks.
1. I tried to build a custom ROM, but I got an error after selecting options.
I checked log file (a:\Torn\WORK\temp\log.txt) and I found following message :
Failed to parse value name HKEY_LOCAL_MACHINE\Software\hejhej.org\moBlue!!!
InitRegistry FAILED in file ".\Registry\37771312-772c-4ff9-a0a1-b555ad54a025.rgu" within a few lines of line 10.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\37771312-772c-4ff9-a0a1-b555ad54a025.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives
If I uncheck "MoBlue", all is OK, so I think MoBlue package is corrupt.
2. When building with default option, what values to put in nb2nbf (CID and start address) ?
I used same as http://forum.xda-developers.com/showpost.php?p=2150690&postcount=1 (82040000 for start adress and ORG_0401 for CID)
Is this OK?
(my phone is an Orange SPV600, CID unlocked, so I think I can put any value for CID)
3. I didn't really understand how to change ROM size. I checked your thread, but I'm still in the dark.
In nb2nbf, in size column, I got "33357824" = "0x13E20248".
So I used "format BINFS 014000000". Is the the way to go ?
Thanks for answers.

Answers!
1. Even I'm unsure about that.
2. Yes. Just select the OS option and it will fill the address by itself.
3. Yes. That is the method I follow. AFAIK, convert the bytes into it's hex equivalent and choose the nearest <higher> hex number with 5 0's at last.
And from what I understand from his post, if you have a ROM with 29.1 mb size, either reduce it to (29 mb - 64k) or add some apps and increase it to (30mb - 64k), to make the optimum use of the available space.

Hi AlainL,
...will have to look after the moblue part - strange, possibly the wrong format of the file (not unicode stored). The content should be ok. I fixed it after updating from the old moBlue inside the old kitchen to the 2.1 version copying the Registry content of the moBlue branch.
Regarding the address it is easy: when you select "OS" and click in the address field, the address is selected automatically - this is the right one.
Your assumption on the format BINFS <size> is correct. This is the way to format it. But your calculation is wrong. The Hex size of your value is 1FD0000 and thus you have to format with 2000000 or your device will not boot after flashing.

The solution to the moBlue problem in the .rgu is very easy.
Edit the .rgu file and add a blank line at the end - that's all.

Editing .rgu files
Just to be on the safer side:
Don't forget to save it in the Unicode format too. Turn off word wrapping while editing .rgu files.

They are all unicode - so if you edit with notepad it should keep this format.
Special attention is required when adding "Multistring" values to the registry. The can be imported as hex - and this hex code must be in unicode format, so 2 bytes per character.
So when exporting the values from the registry to add them to an .rgu package you must take care of this. Took me some tries until I had the .NET CF 3.5 with separated GAC_* package running.

tobbbie said:
Your assumption on the format BINFS <size> is correct. This is the way to format it. But your calculation is wrong. The Hex size of your value is 1FD0000 and thus you have to format with 2000000 or your device will not boot after flashing.
Click to expand...
Click to collapse
Hi
Thanks all for your answers.
I used the right number.
I just made an error while writing in this thread ("0x13E20248" = "333578824").
This cooking works very well.
I just got a problem, maybe someone can help me.
I added Esmertec Java and installed opera mini 4.2, opera mini 5 beta 2 (latest) and opera mobile 10 beta 2 (latest too).
All is OK with 4.2, but with 5b2 and 10b2, I can't pass license agreement screen, because I can't click on "Accept" button (nor "exit" one), neither with left or right menu button or with cursor.
I thinks it's Opera's fault, but if anyone got a suggestion ...
Finally, I got a question :
Now, I'm using a SPV C600 (Orange), and it doesn't have WiFi.
I plan to buy either a XPA1240 or Qtek 8310 (used, quite cheap), but I need to know if WPA is supported.
I can't check by myself, cause every time I try something related to WiFi, I end with an error "Driver not loaded".

I do not cook java in the device but have it installed on SD card - along with the midlets it will take later. The package I use is called "JBEDROSE" (20080813.2.1) and comes from the Vox forum. I have no problems using later versions of Opera there (including 5ß2). I suspect the accept requires a network connection to the opera server (WIFI or AS), so maybe this is your problem?
The WLAN support WEP, WPA, WPA2 and should also cover hidden SSIDs (but I don't use it). The Reg-Tweak "optimal performance for WLAN" is actually putting the WLAN in a mode that will NOT do continuous transmission (and drain your battery real fast - like in WM5) but in a mode that saves battery without affecting performance.
The prices for used 1240 or 8310 are rising at ebay currently

tobbbie said:
I do not cook java in the device but have it installed on SD card - along with the midlets it will take later. The package I use is called "JBEDROSE" (20080813.2.1) and comes from the Vox forum. I have no problems using later versions of Opera there (including 5ß2). I suspect the accept requires a network connection to the opera server (WIFI or AS), so maybe this is your problem?
Click to expand...
Click to collapse
I tied both with AS or via EDGE/GPRS connected (when loading EULA, netwok is required).
It looks like Opera 5b2 and 10b2 didn't recognized both menu button.
I will still do some tests.
tobbbie said:
The WLAN support WEP, WPA, WPA2 and should also cover hidden SSIDs (but I don't use it). The Reg-Tweak "optimal performance for WLAN" is actually putting the WLAN in a mode that will NOT do continuous transmission (and drain your battery real fast - like in WM5) but in a mode that saves battery without affecting performance.
Click to expand...
Click to collapse
Thanks, great
tobbbie said:
The prices for used 1240 or 8310 are rising at ebay currently
Click to expand...
Click to collapse
Because of your excellenet kitchen ?

Opera 5ß2 works on my Jbed (non cooked as I wrote). The opera 10ß2 is native WM - but said to not support smartphones (non-touchscreen) well, so I stick with Opera-mini for the occasional browsing I do there.

Now the default settings are contained in a ready cooked ROM - enjoy!
Appended to the first post:
added 20100314: (edited 20100504)
Despite it is really extremely easy to cook your own ROM with the kitchen, let me give you a head start with your old Tornado. I have cooked the default settings to a ROM and added all tools that you need to step from a stock Tornado to the cooked one in a single archive.
Download it from here: http://www.mediafire.com/file/njm040ttoxm/_tobbbie-tornado-WM6(SDHC-NetCF_on_SD).exe
Unpacking it you will find a directory structure:
Code:
_tobbbie-tornado-WM6(SDHC-NetCF_on_SD)
├───1 prepare security
│ ├───1 HTCUnlock
│ └───2 SDA_ApplicationUnlock
├───2 prepare for custom flash
│ └───Utils
├───3 flash latest Radio and SPL
├───4 format BINFS 1b00000
├───5 flash ROM
└───6 copy NetCF to SD
└───Windows
Follow the actions in the directories one-by-one:
You only need to do steps 1 and 3 if you come from an official ROM but Step 2 (lokiwiz) needs only be done once per device.
If you flash another cooked ROM you can start from step 4.
Attention: In case you did not notice yet - the following procedures will completely erase all content that you stored on the device (email, SMS, MMS, ToDo, Contacts - simply everything) - the device will be as if it comes out of the box. So back up your data before you do this!
Here is what to do in detail, how and why:
Prepare security: This means that the restrictive program execution privileges have to be set less firm to allow step 2 to run later.
Connect your Tornado to the PC and let Active Sync connect. First run HTCUnlock-CVS.exe in the directory 1 HTCUnlock. This will install a program on your device. Run the installed program there and restart the device.
After the device has reconnected to Active Sync, on the PC run the program SDA_ApplicationUnlock.exe in the folder 2 SDA_ApplicationUnlock. It should confirm "succesfully unlocked".
Now the device is ready to receive the "SuperCID" that allows to flash any ROM to it, regardless of Operator or Vendor limitations. To be on the safe side later, please enter on the device *#06# and note down the IMEI that the device reports - you will need it later.
This needs only be done once per device - it is a permanent setting that survives all ROM updates.
Go to the folder 2 prepare for custom flash and
make sure there are no files *.bin left from previous device's activities
then execute Lokiwiz.bat. It will prompt you with 4 options:
Code:
U. Unlock
L. Lock
C. CID Unlock (SuperCID)
Q. Quit
--------------------
Type the letter and press Enter:
Input "C" <enter>.
It will copy a program (itsutils) to the device and it should ask you for permission to execute - grant execution and let the batch file continue. You should find 2 new files beside the Lokiwiz.bat (lock-backup.bin and cid-unlocked.bin). Move them to a safe place immediately and do not repeat the procedure or call another option!
Be careful to label these files unambigously (best is to append the device's IMEI to the name - get it with *#06# before and do not use the IMEI printed on the label of the device - as restoring a wrong *.bin file to a device will kill the GSM radio access (Message: Data Crashes, please contact your... when trying to connect to the network with a SIM card inserted).
Now the device is prepared to receive custom ROMs.
Let's first put the last available Radio ROM and SPL (Secondary Program Loader) to the device. Go to the directory 3 flash latest Radio and SPL and execute ROMUpdateUtility.exe. After successfull update the device will restart in the old OS, nothing has visibly changed - you could still use the device as it is, all your data are still there.
Now the preparations start to erase the old OS and flash the new one.
Deactivate USB connections for the Active Sync
Switch off the device and disconnect from USB
Press Camera Key and keep it pushed down while connecting the USB cable to the PC - wait until the 3-color screen appears and release the camera key.
Start ttermpro.exe in directory 4 format BINFS 1b00000
Select Serial and Port USB
Press <enter> in the terminal window, you should get prompt CMD>
enter info 2 <enter> you should see something like:
Code:
Cmd>info 2
GetDeviceInfo=0x00000002
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
HTCSSuperCID ' HTCE
Cmd>
The last line must show HTCSSuperCID ' HTCE.
If you see anything else there (e.g. HTCSVODA0504 㱍dHTCE - which is for an Austrian V1240) the lokiwiz in step 2 above did not work correctly. Still you have not destroyed anything (hopefully) - so to get the old OS start up again, enter ResetDevice <enter> - the device will restart and boot again. Think about what went wrong in the previous steps.
The lokiwiz batch file and the tools behind it are very powerful and can kill the GSM radio access of the device. Be careful with the *.bin files and keep those of different devices clearly apart.
In case you see HTCSSuperCID ' HTCE then you can pass the point of no return (after this the OS and all your data are deleted from the device) and enter at the prompt format BINFS 1b00000 <enter>. (The value 1b00000 depends on the ROM size, so if you use a different ROM, the value may also be different.) After a few seconds the prompt returns and the partition where the OS was stored is cleaned up now. The device will not boot beyond the 3-color screen in this state. You need to flash the new OS in the next step - but before this enter ResetDevice <enter> - the device will restart and return to the 3-color screen.
Terminate the tterm.exe, you will not need it any further.
Re-activate USB connections in Active Sync - you may forget it later.
Enter the directory 5 flash ROM and execute ROMUpdateUtility.exe. The procedure looks the same as in step 3 but takes a little longer. Do not get nervous as the time at 100% extends a few minutes. The device will reboot and bring you to the new OS.
The SD card that shall be used in the device needs to have the NetCF 3.5 files copied to the directory \Windows finally. This is NOT on the device but on the card - you can copy it on the PC while the sd card is in a card-reader or when the device has is mounted, there the path is \Storage Card\Windows
If the device had a SIM-Lock and it rejects your SIM, go to the lokiwiz.bat (again move out all *.bin files) and select "U" for SIM Unlock - again move the bin files in the directory to a safe place (but you should never need them). Mind that the "lock_backup.bin" is just a copy of the current encrypted area in the device. So this file is different after each step you completed before. Worse: if you do not save the FIRST lock-backup.bin you can never go back to this state.
Mind that lokiwiz.bat has worked for me on a Telenor Sim-Locked nordic ROM CID-locked QTEK 8310, so it should work for any other device as well. If you get the dreaded "Data Crashes..." message and your restore of the correct lock-backup.bin did not help either - your last resort is the SIM Unlock service here: http://imei-check.co.uk/c600_unlock.php. It costs you some bucks, but they seem to re-create the encrypted area with the matching IMEI of your device putting it in a SIM-unlocked and CID Unlocked state. Cheaper than buying a new device.
After you have sucessfully flashed your ROM - maybe you try cooking one yourself?

Some updates to the guideline for flashing in the previous and the first post.
be careful with lokiwiz (several hints added)
last resort if you fail to superCID the device: http://imei-check.co.uk/c600_unlock.php
Enjoy - there is no real successor of the Tornado

Thank you for this. I updated my phone because the previous rom was slow and flawed as I discovered. Phone is working great now.