Database Info

[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

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.

Droid Explorer - 0.8.7.0 [7/13/2010] - The Gibson

Droid Explorer is the #1 Open Source Android device manager for Rooted devices.
Device Requirements
Rooted Android Device with busybox
Guide to installing busybox on the Droid
PC Requirements
Windows (looking for a developer to help create UI for mono)
.NET Framework 3.5 SP1
Some plugins require Java Runtime Environment and Java Web Start
Confirmed Devices
All Devices have been rooted and busybox installed
HTC Dream / G1 / ADP1
HTC Sapphire / Magic / MyTouch 3G / ADP2 / Ion
HTC Hero / G2 / CDMA Hero
Google Nexus One
Motorola DROID
Samsung Galaxy / i7500
Acer Liquid
HTC EVO
Features
Includes the required windows USB drivers - you will be prompted to install the drivers during installation if running vista/7
Auto setup of Android SDK tools and drivers during install
Use an existing Android SDK if you already have one set up
Multiple Device Support
No need to mount SD card to access files
Copy any file on the device to PC
Copy files to clipboard
Copy update to device and auto-apply
Drag & Drop copying from Explorer to Droid Explorer
Auto detection of connected/disconnected device
Open files on PC
Plugin Framework
Application Manager
Right Click APK to install/uninstall
Take screen shots of device (landscape & portrait)
Open right from "My Computer" (a lot like how WinMobile is with active sync)
SQLite Manager Plugin
Uses System Icons for files displayed in explorer
Familiar Explorer like UI, including an Explorer like location bar
Android Screencast plugin
Install/Uninstall APK files right from explorer
Standalone plugin runner
Window 7 JumpLists for plugins
DesktopSMS plugin - Send SMS messages from your desktop
Service can be controlled now from the options dialog (can create the service if you do not use the installer)
Backup plugin for the "Bare Bones" Roms
Run shell scripts on the device by double clicking them
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'd like any thoughts you may have for other features to add to Droid Explorer. Report bugs or request features here or on the project issue tracker.
Web Installer (x86)
Requires internet connection to download android sdk tools
x86 Serivce will not work on x64 OS
Web Installer (x64)
Requires internet connection to download android sdk tools
Use this install if running a 64 bit OS
Standalone Installer (x86)
Does not require internet connection. Larger download.
Standalone Installer (x64)
Does not require internet connection. Larger download.
Use this install if running a 64 bit OS
Older Releases
Source Code Available at CodePlex

Change log 0.8.7.0
Can now use existing SDK instead of the "trimmed" version
Settings stored in the registry now check both Local Machine and Current User
Lots of other little fixes
Change log 0.8.6.0
fixed missing file in the standalone installer
added check for minimum .net framework version in to bootstrapper (v3.5sp1)
increased the service start/stop timeout in the bootstrapper from 30 seconds to 60 seconds
removed initial strings from download panel labels of bootstrapper
htc desire / bravo icon added for attached devices - thanks to beadza for identifying the device
added ability to only install the SDK Tools by running install with /sdk switch
sdk install mode checks if DE is installed, if not, it switches to full install mode
bart plugin now also checks the sd-ext mount point for the license.
added the sd-ext app paths as valid application paths
added sd-ext app paths to the application backup plugin
removed anda.pk plugin as the site is dead.
screencast plugin changed to pull the jnlp file directly from the trunk of the project. If there
is an error, it falls back to a "local" file
fixed issues with spaces in folder names
motorola backflip icon added for attached devices - thanks to zibiza for identifying the device
new screenshot app that handles all resolutions. Uses new methods to get the framebuffer data
adjusted the RGB565 class to better handle other devices for screenshots
started to implement communicating with adb over TCP like ddms does.
acer liquid icon added for attached devices - thanks to fyodor0218 for identifying the device
started working on the ability to use existing sdk (not yet an option, but soon)
Change log 0.8.5.1
Fixed typo in the final step when uninstalling
Fixed x64 issues for windows 7 x64 - still broke on Vista x64 & XP x64 (sorry people, i'm still working on it!)
Default button for bootstrapper changed to the "next" button instead of cancel
added incredible icon for attached devices
added nexus one icon for attached devices
added galaxy S (gt-i9000) icon for attached devices
added acer liquid icon for attached devices
updated the samsung moment icon
added a new "open" version of the moment - rename in the assets directory to "moment.ico" to use.
Change log 0.8.5.0
android screen cast updated to load the lastest build from the trunk
changed publish to use skydrive share instead of the api from the msbuild tasks
added platform tools 2.2
added sdk tools r6
updated repository.xml
added help video link when the device cannot be found
attempting to fix the registry read issues with XP SP3 x64 and Vista x64
removed the "fade out" of the expandos from the treeview to remove the flicker
fixed the issue with opening offscreen
fixed workitem:10275, changed "Close" to "Finish" in the description of the final step of installer
fixed the "hanging" of trying to delete a file. added the '-f' switch to never prompt.
Change log 0.8.4.3
Fixed the install / start up issues caused by the platform tools having a typo in the file name
Change log 0.8.4.0
Fixed issue with cyanogen 4.2.14.x
fixed issue with bart manager plugin license (sorry for the delay)
added 2.1 r1 platform tools
added usb drivers r3 - adds support for nexus one
fixed issue with install plugin crashing if application is already installed.
Change log 0.8.3.0
Fixed bug with device not identifying recovery mode
Display QR code to purchase bart manager if license not found.
mount partitions in recovery mode to find bart manager license
bart manager now attaches to process to output the info
another attempt to set as root when starting for non-adp devices
There is a known bug with droid explorer detecting a device already "connected" going in to recovery mode.
Flash recovery now works in any mode, not just recovery
bart manager license now available for purchase on market.
Change log 0.8.2.3
Drivers removed for windows XP until XP issue with the drivers can be resolved.
added device icon for the nexus one / passion
Code setup to allow some plugins to be purchased.
The .net 3.5 check has been removed for the time being until a better solution can be implemented.
build published via [url:MSBuild Deployment Tasks|http://mdt.codeplex.com]
some bugs fixed here and there
What happened to 0.8.2.2? - Windows locked the directory when I was building that version so it failed and I couldn't delete it to rebuild so I skipped it.
Change log 0.8.2.1
Fixed install issues with 0.8.2.0 - should install for x86 and x64
Change log 0.8.2.0
created a WiX custom action library for checking for the android usb drivers
install logging is now merged in to one file and off by default. use /l[og] to turn on logging
tools will always be downloaded/extracted during install. This lets the tool update to newer tools if needed
fixed delete file when the file name has a space in the file name.
sdk tools upgraded to r4
fixed bug in uninstall if the service did not exist on the machine
should now successfully check for the android usb drivers and install them if revision 2 is not installed.
remember location of "open file dialog"
added code that should check for .net 3.5 sp1 before "crashing" for not having it installed.
added check that the user is installing the correct version (x86 or x64) for their system
Change log 0.8.1.0
added a splash screen so the user is aware that the app is running right away
.NET Framework 3.5 SP1 check added to installer.
apk shell extension now uses the path stored in the registry for the tools.
added logging to the install process
kill all adb processes before attempting to cleanup the sdk path during install.
apk seems to not be working, still debuging the issues. it will be back.
defined a platform constant to the project scripts, x86: PLATFORMX86, x64: PLATFORMX64, ia64: PLATFORMIA64
fixed bug with reading / writing to the registry in x64. now looks in HKLM\Software\WOW6432Node\
fatal errors are now caught and user given option to restart app, close app, or report bug
there is still a bug with installing the driver, the check isnt working so the driver still needs to be installed manually.
Change log 0.8.0.1
fixed installer issue where it crashed if you do not have a proxy set up
x64 installer has issues. - Tempory Fix - Will fixed in next release
Change log 0.8.0.0
added the r2 windows usb drivers, which add support for droid and other devices
added new checks for the drivers. Checks for dream/magic/sholes - these are the devices that google defines in the .inf file.
images moved to external resources library
changed the installer images to be more "custom"
removed need for droid explorer to require "run as administrator" - Yay!
the bootstrapper now handles starting the service. This makes sure the sdk is setup before it starts.
bootstrapper is self contained, the msi is an embedded resource and all referenced assemblies are ILMerged
repository file is hosed on the droid explorer google code site, it is based on the same one that google uses for the android sdk setup
the tools are also hosted on the google code site, this is so the download size is smaller, since all unused bits are removed.
A fully standalone version of install is also available. No need for internet access to install.
boot strapper support uninstall - setup.exe /uninstall
removed reference to the "common.shared" assembly.
added a properites dialog for folders/files
properties dialog shows security settings as well.
fixed icons in context menu for new folder/file
Change log 0.7.12.0
fixed the error that anda.pk plugin logs when it starts because it did not implement "Runnable"
shell extension for apk files so the apk icon displays in explorer - based on http://code.google.com/p/apkshellext/
seems there is a bug in some APKs that dont display their icon, nor do they display the default icon.
registers and unregisters the shell extension on install/uninstall
driver check now works better in the installer
removed some tools menu items that have been replaced by plugins
Installer now gives "options" on what features to install
changed default apk icon to be the "android package" icon
fixed bug with launching ddms and hierarchy viewer
fixed bug launching the google applications backup plugin
added methods to the core command runner to make a mount point read/write and readonly
added icon for the motorola droid
added icon for the samsung moment
added icon for the htc droid eris
Change log 0.7.11.0
USB Drivers installed - This is still in "alpha", should only install them if you need them. please report any issues. It doesn't actually install the drivers, it places them in the driver store, when the device is attached, and the new hardware wizard displays, selecting "automatically install (recommended)" should find the drivers automatically. This installs the 1.6 drivers.
fixed logcat not starting
created a new logcat console that colorizes the log entries
save the logcat output (minus the log level indicator (W/I/D/E/))
support for android screencast 0.2
Change log 0.7.10.1
Fixed crash on device going from connected to disconnected state
Change log 0.7.10.0
Sign Package plugin (signs zip file with test keys)
modified IPlugin to now have methods for creating the toolstrip button and menu items
DroidExplorer.Core.Plugin.PluginHeler added. Contain default static methods for creating the toolstrip button and menu
and.apk now a plugin instead part of "core"
started a contacts manager
started a tool to export facebook contacts from official application to android contacts
added "recovery" as device state.
now "attaches" while in recovery mode.
screenshot now works in recovery mode.
screenshot rotates the current image before refreshing when switching between landscape & portrait
flash recovery image now a plugin - only active when in recovery mode
some bug fixes that I don't remember the exact details on
Change log 0.7.9.0
new shell console enhanced
getprop wrapped to get device properties
explorer icon now attempts to load an icon of the device
- Known devices:
- Bahamas (Tattoo)
- GT-I7500 (Galaxy)
- Hero (G2/Hero)
- Sprint Hero (do not yet know what it identifies itself as in ro.product.device may just show normal hero)
- cliq (need to verify what ro.product.device returns)
- Saphire (MyTouch3G/ION/Magic)
- Dream (G1/ADP1)
- Pulse (need to verify what ro.product.device returns)
- Zii Egg (need to verify what ro.product.device returns)
Device properties viewable in options->environment->known devices->[device-serial]->properties (only when device is connected)
fixed bug with screenshot image being landscape but window portrait.
fixed bug with large icons not always showing the right icon
Change log 0.7.8.0
Desktop SMS now launched from officially signed jar file
Plugin tool strip disabled / enabled when device disconnected / connected
SymLinks and Directories can now also be renamed
F2 starts file/link/directory rename
Executable files now run if double clicked (open from context menu)
Shell Console (could still be buggy so the normal shell window is still available)
double clicking sh scripts run them
plugins that are registered as a file type handler will show up in the right click menu for the file
Change log 0.7.7.0
Renaming of files (folders and links coming)
Google Application Backup (GAB) plugin added
GAB supports HTC's ADB1 update packages (containing system.img), pulling from the device or from normal update.zip
Screen shot plugin supports portrait & landscape modes (use button or right click image)
Screen shot threaded so it doesn't "hang"
Change log 0.7.6.0
Fixed screen shot plugin from opening off screen if droid explorer is maximized or positioned on the right of the screen.
Check for the USB Driver version and download the tool set based on that. If you select the sdk yourself, you must select the correct tools yourself.
USB Driver Version info available in Options->Environment->Android SDK
Speed up of navigating to different directory. Reduced the number of LS calls that are made to build the tree and listview
Change log 0.7.5.0
Fixed plugins executing when loading within Runner
Fixed bug with additional plugin getting the same changed values as other plugin.
Change the SDK path from the Options dialog (requires restart of application)
Fixed bug with apk's not displaying.
Fixed Batch Installer not "showing"
provided a way to manually install, start and stop the droid explorer service - for non-installer users
added ability to save debug output to a file
moved debug window filter buttons to the right
debug window will display below DE if there is room, otherwise, it will display at the top of the screen
added plugin to launch DesktopSMS. Requires the DesktopSMS Server APK be installed on the device - Currently usinging a signed jar by me, hopefully the developer will sign his version.
can now copy symlinks files to clipboard
Change log 0.7.4.0
Changed the SdkInstallDialog to use a WebRequest instead of the WebClient. Hopefully this will help some peoples issues...
Window settings are now saved and reloaded.
Remembers the folder view state (large icon, details, etc)
added --color=never to directory listing command. this should fix the issue people with Heros are having
moved the options dialog tree config to its own file, as it really isnt configured by the user.
added batch installer plugin (alpha) that can install/uninstall multiple apk's at one time.
added logging info for droid explorer. (saved in %USERAPPDATA%\DroidExplorer\logs)
it should also handle "unhandled" errors better
wired up Tools menu items
Added property to indicate if a plugin can be ran by the Runner
Jumplist items added for runnable plugins
Change log 0.7.3.0
app.manifest added to projects. requestedExecutionLevel = requireAdministrator. This means in Vista/Win7 it will prompt w/ UAC. I can not get around this at this time.
this is because in order for the service to use the same settings as the application, i need to save them in the install directory.
The sdk tools, if downloaded, is no longer stored in the user directory, it is stored in the install directory, see above for the reason.
Known devices moved back to HKLM for the same reasons above.
New Options form added.
Device manager now part of options dialog
plugins can now reside in any directory as long as it is added to the plugins settings
plugins can now be enabled or disabled from the options dialog
Service is now working because of the requireAdministrator change.
DroidExplorer.Runner added - a tool that can execute a plugin; usage: DroidExplorer.Runner.exe /type=Full.Plugin.Class.Name,Plugin.Assembly.Nam/any /additional /args
if the type argument is not specified, then it will display a plugin selection dialog.
Installer plugin. This is launched by the runner when an APK file is opened in Explorer.
Registry settings to register .apk files to open with DroidExplorer.Runner /Installer (create with MSI installer)
.apk files can be installed by double clicking them or by right clicking and selecting "Install"
.apk files can be uninstalled by right clicking and selecting "Uninstall"
the initial device selection dialog is only required if more then 1 device is connected.
If you have set up to use the SDK tools by downloading the tools and put them in your user application data directory, when launched, it will prompt you to re-setup the tools. They are not stored in the user directory because the Service can not access that directory.
Just realized the bug with the device name not showing in the titlebar/addressbar. This is already fixed and will be in the next release.

Future Features you will see in Droid Explorer
Complete integration with the Managed Android Debug Bridge. R
Root will not be needed, at least for copy file operations. Things like flashing recovery, and deleting from /system will still require root.
Busybox dependency will be dropped.
SQLite Database Manager to replace the feature lacking plugin that exists now.
Faster navigation when changing directories
What features do you want to see?

[Android-x86] All in One - Tips, Tricks, Apps & Etc | Bug & Issues | Q&A

Hi XDA ,Hi Friends And Welcome Guest
Before everything Remember that Please hit Thanks when someone helps you out!
Download Android x86:
There are several versions, but I suggest you Download this version :
Android-x86 4.4-r1 live & installation iso
on Aug 8, 2014, by Chih-Wei Huang
Install Android x86:
There are several methods, but I suggest you follow me
Make the system R/W for root access
[HOW-TO] Install Android x86 on any PCs / Laptops / VM
Manage Ext Partition from Windows:
You need to install ext2fsd
Ext2Fsd is an ext2 file system driver for Windows (2k, XP, Vista and Win7). It’s a free software. Anyone can modify or distribute it under GPL2.
Downloads:
View and download Ext2Fsd packages
Express Installation with Ext2Fsd installer:
Double click on Ext2Fsd-version.exe to execute Ext2Fsd installer and follow the setup wizard to install and configure Ext2Fsd.
To uninstall Ext2Fsd, just click “Uninstall Ext2Fsd” in start menu, or use Add/Remove programs in control panel to uninstall. Need restart your computer to get it finished.
Done
if you wanna add something to sd card just follow this path:
X:\android-4.4-r1\data\media\0
Please hit Thanks when someone helps you out!
Edit Grub Bootloader
Follows this path on windows
X:\grub
And find menu.lst
Then open with Notepad or Notepad++ and edit lines.
The example of menu.lst ( don't use for yourself )
HTML:
default=0
timeout=6
splashimage=/grub/android-x86.xpm.gz
root (hd0,4)
title Android-x86 KitKat
kernel /android-4.4-r1/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 video=-16 SRC=/android-4.4-r1
initrd /android-4.4-r1/initrd.img
title Windows
rootnoverify (hd0,0)
chainloader +1
Install App on Android x86:
Tap the clock on the taskbar, tap the pop out that appears, and then tap Settings.
Scroll down the list and tap Security, then on the right, scroll down and tap Unknown sources.
Tap OK on the prompt that appears.
1. Install Apps From Google Play Store
2. Installing app Using The Conventional Method
Step 1: Use Windows and Copy .apk file to this path
X:\android-4.4-r1\data\media\0
Step 2: Run File manager from Android and install file from this path:
\data\media\0
3. Installing app using Dropbox
Tweaks:
Android Xposed: tweak your phone's UI
[ROOT] Kernel Tweaker | Original Thread
Clean Master Phone Boost
Check Post #2 & #3. ​

Bug & Issues
Recovery:
CWM - TWRP ???
Flash Gordon????
Not work
If you have any idea pleas help us. :laugh:

Apps - Tools - Utility
Mount internal hard drive:
Automatically mount and dismount USB sticks on various devices like the Galaxy Nexus, Nexus 7 and Nexus 10. The Nexus 4 is not supported - this is an issue with the device, not with StickMount !
[APP][01.07.2014] StickMount v3.10 [ROOT]
Change Language on HW Keyboard:
A non visible soft keyboard (Input Method) intended to be used with hardware Bluetooth and USB keyboards. It automaticly detects Bluetooth keyboards (and in some cases also USB keyboards) and brings up the Input Method dialog. It also supports a lot of different keylayouts for non-US external keyboards.
[Android 1.6+] External Keyboard Helper Pro
Turn Ethernet To Wifi:
If you want an app that needs wifi And you want it to run on ethernet Go here
[MOD][Xposed] Fake Wifi Connection [1.6]
Fake GPS or Mock Locations:
Go Here and check it : [APP][OSS] Fake GPS Path
Rotate everything In landscape Mode:
Rotation manager is a tool that lets you choose which application you want to rotate or which one you don't want to rotate. It is a really simple app designed for the least possible power and RAM consumption.
Download From Here

Duel Boot for Windows:
Easy BCD:
EasyBCD Community Edition allows you to create a multiboot environment in order to run multiple operating systems on the same computer.
The application also features BCD (Boot Configuration Data) Backup/Repair utilities that provide users with the possibility to reset the BCD configuration or recreate and repair boot files.
Download Link
http://www.softpedia.com/get/System/OS-Enhancements/EasyBCD.shtml
Installing Windows After Android-x86
There are two different approaches:
Recovering GRUB after re-installing Windows
Please refer to the Reinstalling GRUB2 guide.
Master Boot Record backup and re-replacement
This method does not work for computers with UEFI boot. In consequence, it won't work for pre-installed Windows8 and some pre-installed Windows7.
Back-up the existing MBR, install Windows, replace your backup overwriting the Windows boot code:
Create an NTFS partition for Windows (using fdisk, GParted or whatever tool you are familiar with)
Backup the MBR e.g. dd if=/dev/sda of=/mbr.bin bs=446 count=1
Install Windows
Boot into a LiveCD
Mount your root partition in the LiveCD
Restore the MBR e.g. dd if=/media/sda/mbr.bin of=/dev/sda bs=446 count=1
Restart and Ubuntu will boot
Setup GRUB to boot Windows

reserved

The Android-x86 4.4-r2 released (the second stable release of kitkat-x86).
http://www.android-x86.org/releases/releasenote-4-4-r2
Stable - Fast

Wiko Sunny 3 rooting (attempt) and "un-big-tech"-ing

I try to share my experience about this cheap phone (bought I think for 45€ : was the cheapest of the hypermarket, around 2019).
Here are some specs : https://www.gsmarena.com/wiko_sunny3-9733.php
First of all, this is a SPD (Spreadtrum) based device, not MTK (Mediatek). (Surely, it would have been easier on an MTK Wiko like the Jerry...)
My goal was to get root access and finally try to install a big-tech free system alternative.
I confess, I spent about one month on it. Here are my findings and the final result I could achieve.
Long story short : I could not get root (I'll explain it below). But I could "un-google" it as much as it is possible without breaking anything essential.
Here is the story and it's lessons learned, in a hopefully logical order.
1. Tried all (really all!) available "out of the box" rooting apps without any result.
2. However there is an "allow unlock bootloader" switch in the "developper settings" (once taped a couple of times on the "build" of the system menu...)
there was no way to really "unlock" it using any appliable fastboot command (tried really everything).
3. Magisk (latest or any other) could not patch the boot.img (or recovery.img).
As root access means the ability to get at some point a writable filesystem, and as this is mounted by boot/recovery.img, this is the key process here.
4. So I went to linux to modify them : tried again all dedicated tools to unpack, edit and repack the boot and recovery.img.
mkbootimg/unpacbootimg, abootimg, but it turns out, they don't repack the files in an acceptable way for this system.
Independently from change made or not (in some .rc file inside the ramdisk, initrd), those usual dedicated tools just cannot repack the file correctly, at least for this device.
Lastly, when I tried bootimg.exe (for windows) of "cofface" (https://github.com/cofface/android_bootimg/blob/master/bootimg.exe)
I could find out that it extracted an other file that abootimg and others was not even aware of : dt_image (binary having an SPRD header).
And this (avesome) tool is able to repack it with it.
But now, the new boot.img was 12Mo and not 36Mo as before. Turns out there is a huge empty (00 bytes) overlay, and a vbmeta (AVB) signature, somewhere at a precise place and at the end of the file.
So I completed and patched the file by a hex editor, to make it the same as the original one. (There were also some 2 "minor" diffs at the beginning of the file that I tried every combination with to make the device boot with it. No way.
I believe now, fdl2-sign.bin, one of the two mandatory required files to flash anything on the device (that gets allways flashed first), checks the signature of boot.img (and recovery.img), so a modification of these would need a brand new signature. (Tell me if I'm wrong: I'm not a pro) And I gave up at this point.
5. Before (understanding the above), I tried also by just changing system/vendor to make root tools available :
Mounted on Linux : strangely, when the filesystem was rebuilt by "make_ext4fs" the flashing crashed, but just unmounting it and then "img2simg" to get the android "spars" format, worked fine (despite for ex. the record of the mountpoint inside the file).
I tried to add all the necessary files (su, busybox, etc.) to "system "and "vendor"... retoutching everythig back to original time stamps, etc.etc.
but the loaded system denies access to all "new" files (and also to some others). Then I tried to change some "policies" files in /etc/selinux (like plat_sepolicy.cil), only trying to get how it works (I added some lines about my files taking as example a well authorized binary)... if ever the added binaries could be accessed even on a -ro filesystem. But nothing changed.
All file added or modified, such as a new bootanimation.zip, becomes "access denied" as well, despite adding them to policies files.
Same for some "new" sounds to media folder : they will be listed but not played (so you only get silenced wake-up instead .
6. After that I decided to un "big-tech"(BT) everything and replace as much (BT tracked) functions as possible by "clean" FOSS apps from F-Droid.
And this, at my surprise, I could get it through 100% (I believe).
The idea in short :
1 - make a clean firmware flush (perhaps with already reduced preinstalled apps)
2 - uninstall/deactivate on the device anything you want and can, replace needed default apps (by FOSS equivalent), especially the launcher(wiko app starter).
3 - edit system and vendor (on linux), delete unwanted apps (making according changes on some .xml control files doesn't change anything and only might cause problems: just deleting the packages seems enough here)
4 - then reflash only the modified system and vendor (reboot and see)
Now, for those who (I would like to say "hate" BT enough to accept loosing the shiny comfort they offer, but lets say) want to get rid of preinstalled privacy breaking BT apps, here is the howto : (with explanation for also the novice)
a) First, download the latest firmware update :
Wiko Mobile : Customer Area / Connection.
customer-world.wikomobile.com
b) Launch the app and push the start flushing button (play button). This will unpack the boundled .pac file into a temporary directory (into the app folder's "ImageFiles\_DownloadFilesE10_2C10D_0" : the suffix changes at each startup. Save this folder to somewhere else (because quiting the app will erase it).
c) Now you need to launch a linux OS, (that can of course access the saved rom files) mainly to mount and modify system.img and vendor.img.
I will detail this for the novice.
Basically, open any teminal, then install if its not yet done, the following needed tools :
sudo apt-get install e2fsprogs
sudo apt-get install android-tools-fsutils
to use Midnight Commander which will save you a lot of time, make also a
sudo apt-get install mc
Then "sudo mc".
Once in MC, do Ctrl+o to switch (back and forth) to command line
d) Uncompress the system+vendor image files, mount, modify, then umount and recompress them :
Uncompress by : "simg2img vendor.img vendor-whatever.img" (same with system.img)
Then (create some "sys", "ven" folders) and : "mount system-whateweryoucalledit.img sys -rw" (thats all, same for vendor).
It turns out, you can just easyly erase some apps (but not anything!) and they just won't be installed, or will "disappear" if they were...
You can delete already from system: in "app" and "priv-app" folders any Facebook related app or service, plus Youtube, Chrome, Gmail... Duo, Messages, TTS, Calendar, Maps. From vendor: Photos, Music, Contact (and also Chrome vendor overlays). Normally you could only deactivate them from the device, but that way they won't be present at all.
You can also edit /etc/prop.default, as follows, but honestly, I did not recognized anything really working, except the sys.usb config and mock.location (allowing fake gps position app).
ro.secure=0 ---> these 2 doesn't seem to do anything without a patched boot.img
security.perf_harden=0
ro.adb.secure=1 ---> needed, otherwise you won't get adb access dialog
ro.allow.mock.location=1 ---> allows fake gps app
ro.debuggable=0 ---> if 1: will just crash "developper settings" because of its defaults
persist.sys.usb.config=none ---> you will be free to set it
Do not try to "ro.adb.secure=0" because you just won't get confirmation box for trusted adb connection attempts and they just won't work!
Same, don't be tempted by "ro.debuggable=1" bacause you will not even be able to access "developper options" any more as its defaults will conflict with this setting an it will just crash over and over. I did it, I payed the price to start it over again...
Now, it seems, ro.secure=0 and security.perf_harden=0 does just nothing as well, without being able to modify boot.img first.
Changing eventually "ro.build.type=user" (in system/build.prop or anywhere else) to "eng" or to "userdebug" makes just the flashing operation to crash. (same by patching boot/recovery.img in hex mode (which looked attractive at first sight) but led to flush crash as well, mainly for the vbmeta thing I tried to describe above.
When finished, just "umount sys" and "umount ven"
Then recompress the files by "img2simg vendor-whatever.img vendor.img" (same with system).
(This first amputation and further, could be done perhaps later all at once, but thats how I did. Of course its about to avoid first installations but without breaking the setup process.)
e) Flash the new firmware to the device, replacing system and vendor.img by the modified files :
The modified files shouldn't be bigger than the original ones, at least not bigger than their size stated (in Mb) in the k120.xml (system:1400,vendor:300) but there is no reason anyway as after my experience all added files will become "access denied". (Should they become bigger than that you will have to change these values in k120.xml and re-pac them (using spd research tool, that will update k120.xml) before using them again, otherwise the flashing will fail.)
So now, get ready for the flashing:
Un mount the back cover of your Wiko Sunny 3, remove for a few seconds the battery, then replace it.
Now, here is something I had to figure out myself because there isn't anywhere a clear description of it, and this is foundamental to be able to flash :
First thing to do is to launch your flashing software, choose the pac file if necessary and push the action button to get ready for the device's connection.
You can wait some time, while the app unpacks the included .pac file. (spd factory/research tools lets you choose your pac file, the one downloaded refers to it only through its .ini file).
So pushing the "start flashing" still nothing happens, the flashing app (unpacks the pac file and) just waits for the devive to connect... This can last forever, don't worry.
Now, to be able to connect de device in service/flashing mode, it should NOT go into charging mode when you connect it.
Thats why, you have to connect the (computer) USB slot by pressing continuosly volume up on the device (after havig removed and reinserted the battery) AND wait until the app detects it and starts the transfer. Do not release the volume-up until it gets at least 3-4%. (Many guides speak about 3 sec or so, the only thing accurate is that the app starts effectively the transfer.) If you release it too quick, the phone goes into charging mode and the COM port used to flash closes, and you will need to repeat the operation.
(And of course you need all required drivers loaded previously. The driver for flashing is called SPRD or SPD Driver R4.20.4201: seems the latest)
If successful, the device gets rebooted.
---------
Here I'd like to ask some pros of XDA : what signal boots the device after flashing? Can it be reproduced without flashing? In other words, can we start/boot an extincted device by USB signal? If yes, how ?
---------
As the first-time setup launches, just decline/skip ewerything, most of all the final wiko/vendor offer (this keeps you safe from vendor commercial services). Just get to the home screen.
See what you have got.
f) Now, setup your anti big-tech privacy free environment. For example, deactivate google play including its service. (Yes, "big-tech haters" don't rely on this ;-)
To know where are the spies, I installed TrackerControl (version 2022.02.10 from F-droid) which gives enough info on that even without root. You will be surprised. There are "feedbacks" to google, to the vendor, and also to Microsoft, even without launching anything, just the wifi on. Even the caller app has trackers...
The best thing is that this (GPL) app lets you know what package causes the leak. You can just write them down, for later deletion.
It turns out, I could delete all of them (mainly from system.img, monted again on Linux) without that anything breaks.
I replaced the caller/dialer, calender, contact, everything, by new default apps. Replaced the Wiko launcher by the Fairphone launcher (from F-Droid).
I installed ungoogled chromium from https://github.com/wchen342/ungoogled-chromium-android/releases (chrome public). (Strangely could not install other browsers!). I replaced Google TTS by "eSpeak NG" (the final config is a little bit tough : have to download "espeak-ng-data" (voices) and push it to the "sdcard" then, slowly, it finds it and it works. (Well, ok, its not the fine google tts thats far the best actually, but its still a tts...) And yes, there is still the keyboard to tap keywords to look for. ;-)
g) When done, take and mount again the system.img file (you flashed) and take out what (following the list of tracker apps found by "TrackerControl", which are mainly (for me) : (for howto, see d) above)
/system/priv-app/phonesky // playstore : com.android.vending
/system/priv-app/GoogleDialerGo // contains trackers!
/system/priv-app/GmsCore // googleplayservices (yes it works without it)
/system/priv-app/WIKOSetupWizard
/system/priv-app/WIKOLauncher // easyly replaced (by Fairphone's 1/2/3)
/system/priv-app/WIKOInstaller
/system/priv-app/AppCloud // wiko appstarter (77 trackers)
/system/priv-app/SearchSpeachService // (google) tracker by definition
/system/priv-app/AntitheftPlugin
can be removed as well (and still some others, but its more wise to stop here, till it still works ;-)
NB : The 3 "Vital-app", probably commercial boudles, must be really present but they can be uninstalled cleanly (weather, smart-assistance, gaming).
Finally, enjoy your non-rooted, but privacy tuned Wiko Sunny 3, and install clean FOSS apps from F-Droid (or from elswhere).
One more thing: Its not because an app is "free and open source" that it won't track you : choose your apps carefully, observing all permissions they ask for.
For example, there isn't much acceptable explanation for a calculator to claim "full network access" or a game to be "launched at startup" or get "system configuration" rights.
And sadly, as we still do not have root access on this device, there isn't much control available on apps, permissions, network or system. But it is possible now to free it from big-tech trackers, as much as possible.
Of course, as usually in these cases, I cannot guarantie anything. It just worked for me like that (reproduced several times), and I think there is no reason that for anybody else it would produce a differet outcome.
Your comments are allways welcome.