[HTC Tornado] tobbbie:
Finally with the help of Gregory's old Tornado kitchen I could identify the culprit which made the WM6.1 and especially WM6.5 Tornado Builds unstable. So find here the final result of the Tornado Kitchen evolution:

http://www.mediafire.com/?702i46jc477ey <-- Click Me!

The files there and their purpose:

all kitchen (WM6, WM6.1 and WM6.5) with ~93MB: tobbbie-OSB-Kitchen-Tornado-WM6,WM61,WM65-(Ger+Eng).7z

Note that is just 1.5-times the size of just one kitchen and you get 3 in a box :-)

WM6.1 Kitchen (my favorite) with ~59MB: tobbbie-OSB-Kitchen-Tornado-WM61-(Ger+Eng).7z

All example builds are created with this one, names of the builds are like the configuration files, re-cooking is a snap here!

4 ready made builds (nk.nbf) to flash in 2 flavors each (Ger/Eng and Eng/Ger) with ~135MB (content of ~247MB): tobbbie-WM61-builds(nk.nbf).7z

Just the same 8 builds, but as os.nb0 files (so not Tornado encrypted) which makes them much better compressible. You get the same 247 MB of builds with just one file of ~39MB: tobbbie-WM61-builds(OS.nb0).7z

The tools you need to make your Tornado get that new stuff loaded. 2 Directories with the needed tools, just follow the obvious sequence. This includes nb2nbf_tornado.exe to convert os.nb0 to nk.nbf, of course.: tobbbie-Tornado-Flash-Tools.7z

Before I elaborate much on the details (and nobody would ever care), just pick what you need and get going. For questions, just come back here.

On the content:

The OEM parts are identical on WM61 and WM65 and the selected packages will auto-insert their relevant settings CPL via registry. This does not work on WM6 and there you have to take care yourself. 90% stem from the history of the Nitrogen Kitchen (which is built on others' contribution). Over time some panels were re-arranged and options added.

The SYS are for WM6 the original from Nitro's kitchen, the WM61 comes from the Rose (S740) and the WM65 from the Captain (S521).

Here the listed history of my kitchen:

there was the Nitrogen WM6 Kitchen - the first for me, as I was a late starter, only picking up cooking because wanted to get SDHC support in my beloved Candy-bar phone. Long time happy with that until there came the OS Builder framework which has really opened up so many new doors...

I ported that batch kitchen to the Hurricane with WM6 but left it there (still nagging me to get that ported to OSB, we will see...)

Then I picked up porting Aleut's WM6.5 kitchen for the Typhoon to Ger/Eng and finally also to OSB (with some special care on non-relocatable modules).

Finally I publish here the end of the story for Tornado including all builds and each of them tweaked to the limit (smallest XIP) but still portable and reversible from the dump. Play with it if you like!

Thanks go to:

cotulla and llnhhy for the SDHC on Tornado (I would not have started all this cooking without THIS contribution!)

Nitrogenious for his WM6 kitchen

Gregory for

the "format BINFS <size>" before loading the nk.nbf - this distributes the flash between ROM size and later available device storage on a 1MB granularity (and only works on the Tornado afaik - not Typhoon and Hurricane for sure)

letting me dig into his last Tornado kitchen (Tornllnhhy_last.zip, unpublished) which allowed me to find out what makes the difference between a stable reboot and such that occasionally lose Bluetooth, Wifi or both - always having wifioff.exe hang the device. The WM6.1 and WM6.5 kitchen would have never been published without this:

; from gregory's WM65 rgu
[HKEY_LOCAL_MACHINE\Services\BTHLINK]
"Prefix"="BTL"
"Dll"="bthlink.dll"
"Index"=dword:00000000
"Order"=dword:00000008
"Keep"=dword:00000001
"Context"=dword:00000000
"DisplayName"="bth"
"Description"="bth"

It seems that adding that dll to the service initialization part will rectify the boot sequence in the way that a stable reboot is achieved. I have a mortscript do the reboot and symptom collect and could supply proof that hundreds of reboot can happen in a row without ever loosing BT and/or WiFi. Before that tweak the range of failure was 30-50%!

barin for OS Builder

ultrashot for parts of OS Builder and continued support for my questions in the context of understanding some more about the virtual memory concept and the paging pool.

The gained insight has made me drop UPX from the builds and be generous with granting paging pool size. There is no gain in hunting for free RAM on expense of the paging pool! Reserve ~25-30% of available RAM to the paging pool, but not less than ~4MB. More than 12MB on smartphone is no gain, so my builds have 8MB. You can alter this (without re-cooking) using the "Smart PagePool changer" which is part of each kitchen set.

many others at xda-developers that make this such an informative place to be

I know I have to add links to some references - this will come later.

Candy-bar smartphones for ever!