[UPDATE][TOOL][CM7] ThemeTools v1.1.5 - Testers needed - Android Themes

ThemeTools
DOS script to easy execute often used tasks for multible themes.
Guide in second post!!
Suggestions and feature requests are welcome!
Functions:
Code:
* multible theme support
* extract APKs
* build APKs
* sign APKs
* generate XML files
* configuration of XML file generation
* install APK
* delete existing XML's
* multible modes for fast use or detailed output
* ttHelper TrayApplication to bring the ThemeTool window to front with strg+num0
* update notification and installation
* path independent (long foldernames, white spaces)
Tools I use in the Script:
Code:
* apktools
* adb from AndroidSDK
* testsign.jar from Stericson
* XMLGenerator.jar from nhnt11
To do:
Code:
[B]* test with Windows XP[/B]
[B]* spelling - HELP NEEDED[/B]
because I'm not a native english speaker I'm sure there are enough mistakes
[B]* help file - HELP NEEDED[/B]
help file is a little bit short ATM
[B]* support for more than 9 themes[/B]
[B]* cleaning up the Code[/B]
Changelog:
Code:
[B]* v1.1.5 - 15.09.2011[/B]
+ new Quick Mode
+ ttHelper
- removed inScript function to switch update notification
[B]* v1.1 - 13.09.2011[/B]
+ different modes
+ remember last used theme on script-exit
+ check for dependencies
+ config file generation if none exists
+ automatic creation of missing folders
+ added update functions
[B]* v1.0 - 12.09.2011[/B]
+ first release
Credits:
Code:
* Stericson for the autosign and inspiration for this script
* nhnt11 for XMLGenerator
* creators of adb and apktool
* xda-forums (for Guides, Howtos, etc.)
* google for the things I didn't find here :D
and as always....
!!! USE AT OWN RISK !!!
>> DOWNLOAD <<

GUIDE
01 - Installation
* Download and extract the Archive
* run "main.cmd"
the Script will create necessary folders and configuration files
You'll get a ERROR message that no themes are found, don't worry, thats normal for the first run. Just press "O" to open the themes folder and create a new folder.
Code:
\---Themes
\---$_ThemeName_$ // the Theme Name
|
+---source // all APK files in this folder can be extracted with the tool. the filename of the APK will be used as subdirectory ("example.apk" will create a directory "example" with th content of the APK
|
\---theme // directory with the content of your theme (res folder, AndroidManifest.xml, apktool.yml)
Now put your Theme Files in it, return to the script and press "R" to retry, now you should be in the main menu.
02 - Configuration
* open config.ini in configuration folder
there are 2 parts, [config] and [xml]
* [config]
theme=none
- this is the last used theme, at before first exit of the script the value will be none
update=no
- if enabled (yes) the script will search for updates at the start nad notify you (same as "Advanced Menu - check for Update)
ttHelper=no
- if enabled (yes) the ttHelper.exe will start automatic at scriptstart.
* [xml]
-tba
03 - ttHelper
ttHelper is a little tray icon which brings the ThemeTools window to front if "(strg)+(num0)" ar pressed. Also the ttHelper sends the ThemeTool window to taskbar after 5 seconds of inactivity. this is enabled by default at every programstart, but can be disabled with a right-click on the tray-icon.
Idea behind ttHelper was especcialy the "QuickMode", so you can easy switch to ThemeTools, generate xml's build, sign and install apk with just 3 keystrokes.
....more tba

How does this tool work? You just have to put your file a side and it will complie itself right?
Accidentally sent from my Nexus S using XDA Premium App

Nice tool!

melvinchng said:
How does this tool work? You just have to put your file a side and it will complie itself right?
Click to expand...
Click to collapse
Compiling, extracting, signing, etc. is all done automatic.
Folder Structure:
Code:
ThemeTools
|---bin
|---config
|---Themes
|---$_ThemeName_$ // the Theme Name
|---source // all APK files in this folder can be extracted with the tool. the filename of the APK will be used as subdirectory ("example.apk" will create a directory "example" with th content of the APK
|---theme // directory with the content of your theme
|---res
|---AndroidManifest.xml
|---apktool.yml

OGrue said:
Compiling, extracting, signing, etc. is all done automatic.
Folder Structure:
Code:
ThemeTools
|---bin
|---config
|---Themes
|---$_ThemeName_$ // the Theme Name
|---source // all APK files in this folder can be extracted with the tool. the filename of the APK will be used as subdirectory ("example.apk" will create a directory "example" with th content of the APK
|---theme // directory with the content of your theme
|---res
|---AndroidManifest.xml
|---apktool.yml
Click to expand...
Click to collapse
Thanks for this, may need this one day
Accidentally sent from my Nexus S using XDA Premium App

Looks like a good program. I will test it as soon as I get on my laptop.

Related

[FAQ][HowTo][KITCHEN][GER][WM65]BlackStone Buddy Count

RESERVED for FAQs and HowTos. Cauz posting is limited to 10.000 chars, I'll move the FAQs and HowTos to this thread and links to them will be posted in the kitchen/ ROM thread. The first two posts in that thread are too limited for the flood of FAQs and HowTos to that kitchen! So please don't post into this FAQ/ HowTo thread!!!
FAQs: Kitchen
FAQs
Kitchen:
The right order to flash:
Make sure your phone is plugged to an AC or at least charged at 50 percent!!!
HSPL: Flash HSPL first. The provided version is located in "_PREREQ" folder.
See http://forum.xda-developers.com/showpost.php?p=2710548&postcount=1 for help flashing HSPL and most recent versions.
Radio: Flash after HSPL! (it should meet the "rilphone.dll" version in "EXT\SHARED\MY_Drivers\DRV_Rilphone_(VERSION)". The radio is
provided in "_PREREQ\Radio_(VERSION)" folder. Radios can be flashed via microSD card. (See below for instructions)
ROM: Should be flashed last! Your custom ROM will be placed in "RELEASE_Blackstone" folder after hitting the create
button in ervius kitchen. ROMs should be flashed via microSD card. (See below for instructions). Remember to hardreset after flashing
new ROMs.
Flashing via SD Card:
Make sure your phone is plugged to an AC or at least charged at 50 percent!!!
Rename any file (e.g. "ruu_signed.nbh") you wish to flash to "BLACIMG.nbh" and copy it to the root of your microSD folder.
Next start the OlliNex Bootloader: This is best achieved by shutting your device down (or remove the battery), hold down the
"volume down" hard button and SHORTLY press the "Power switch". As soon as the "tricolor bootloader" appears, release the
"volume down" hard button (or else the process will be cancelled). The loader automatically searches for the "BLACIMG.nbh" file
in the root of your microSD card. When the bootloader is prompting to flash, hit the "Power switch" and wait for the progress to finish!
It will say, that everything has been flashed o.k. HARDRESET after flashing a new ROM!!! (See below for instructions)
Hardreset:
Make sure your phone is plugged to an AC or at least charged at 50 percent!!!
If you just flashed your new ROM and the loader is halted, saying everything is fine, remove the back cover and the battery (Unplug AC
also, if plugged in). After putting everthing together again, hold dow "volume down" and "volume up" together and SHORTLY press
the "Power switch". As soon as the "tricolor bootloader" appears, release the two volume buttons (or else the process will be cancelled). The
bootloader will prompt you to press "volume up" to proceed the hardreset. After the process has finished, press "volume up" again to boot your ROM.
Phone freezes during initial boot:
There are several reasons, why the phone sometimes freezes during boot:
The most obvious one: Be patient! Stay cool! Keep calm!
Due to the new Windows mobile 6.5 release and the fully loaded packages (HTC and custom features) ROMs will need a bit more time for the initial
(first) boot! Just be patient! Drink a coffee!
If the bootloader doesn't switch to the Windows mobile logo and freezes while displaying the ROM version (smart mobility screen, with orange
infos), you forgot to check "Real WM 6.5 AKU" in ervius kitchen options.
If the initial boot stops during the customizing screen, this is an issue of the OEM files, mostly some missing app in
"OEM\BlackStone\0407\ConfigAP\config_AP.txt". So remove the lines containing an app, you removed from the selection in ervius kitchen
(e.g. Opera).
Many things don't work (like installing cabs):
There could be several reasons, why some programs and apps don't work:
Windows Mobile customizing dind't start: If this happens hard-reset and be PATIENT on first (initial) boot. Wait some additional minutes
BEFORE calibrating the screen and "first use" of the phone. Due to the new Windows mobile 6.5 release and the fully loaded packages
(HTC and custom features) ROMs will need a bit more time for the first (initial) boot! Just be patient! Drink a coffee!
You missed some packages, when building your ROM. Check that the packages marked "KEEP THIS!!!" are not set to "FALSE" and
doublecheck, that there are no duplicated packages!
Future system builds:
A merge will be easily possible, Ill also provide a batch script for that. (But that is one of my last tasks...) By now you only have to copy
the new system files and folders into SYS directory (e.g. "SYS\23009") and copy all the language specific folders from the old release to the
new one. (e.g. "\SYS\23003\SHARED\0407\" to "\SYS\23009\SHARED\0407\". This is not a difficult task. Be sure to get the system files of
a WVGA release. All modifications needed to make WM65 builds run on BlackStone devices will be put in "MY_Drivers", "MY_Packages",
"MY_RegTweaks", ... folders in "EXT\SHARED". So new system builds should directly work without great changes. Im still working on the
folder structure. If you got any improvements, let me know.
FAQs: External packages
External packages:
Owner information:
In "EXT\SHARED\MY_RegTweaks_XDA\REG_Owner_Info_XDA" is a sample owner information. Edit this by going to "Start=>Settings=>Personal=>
Owner information". Make sure under "options" both entries are marked. Export the the following registry key with "PHM RegEdit" (Utilities folder):
[HKEY_CURRENT_USER\ControlPanel\Owner] into your kitchen. (Replace app.reg in "EXT\SHARED\MY_RegTweaks_XDA\REG_Owner_Info_XDA" folder.
If you cooked your ROM or just downloaded the provided ROM without the kitchen and you think the info box is annoying, it can be
turned off, by going to "Settings=>Personal=>Owner info=>Options". Disable the two options available. Or disable "REG_Owner_Info_XDA" in the
kitchen, when buidling ROMs to avoid future displaying of the information.
Sprite Terminator:
In "EXT\SHARED\MY_Packages\APP_SpriteTerminator" you will find the base app. Sprite Terminator is a commercial software, for tracking and
remote controlling your phone, once it gets lost or stolen. Cooking this into the ROM is a nice security feature. (Not for the thief... ) With
this kitchen a demo version is provided, but it will not function, until you install the original CAB (from manufacturers site) and export the
registry keys and "spriteterminator.xml" into the kitchen, after configuring/ registering the app. The files in
"EXT\SHARED\MY_RegTweaks_XDA\REG_SpriteTerminator_XDA" are just for file structure and registry setting demonstration. Registry information
is stored in "[HKEY_LOCAL_MACHINE\Software\Sprite Software\SpriteGuard]".
Use "PHM RegEdit" (Utilities folder) to export the values and replace "app.reg" in "EXT\SHARED\MY_RegTweaks_XDA\REG_SpriteTerminator_XDA"
folder.
FAQs: General troubleshooting
General troubleshooting:
Power failure during flash/ BRICK:
Make sure your phone is plugged to an AC or at least charged at 50 percent!!!
If you bricked your phone due to a power failure or another flash failure, try to remove the battery and AC, put everything together and let
the phone charge (Fully charged when the LED placed on the "power switch" changes from orange to green). Try to access the "tricolor
bootloader" after your phone has fully charged (See "Flashing via SD Card"). Reflash your ROM, the process should now finish. For more
detailed troubleshooting see section "How to reflash Stock/Shipped SPL - STEP BY STEP - FOR WARRANTY REASONS ONLY!" under this
link: http://forum.xda-developers.com/showpost.php?p=2710548&postcount=1
Registry files (app.reg):
Watch out for empty lines in values and keep the reg file conventions (REGEDIT4), breaking those will cause a parsing error when building
the ROM. Make sure there is an emtpy line feed at the end of each *.reg file. Files are stored in MS notepads' unicode format. Double
check for missing qutoes! Pathes in values have double backslashes ("\\"). If you export a file with "PHM RegEdit" (Utilities folder), by
"right clicking" a key and choosing "Export..." make sure the export type is "WinCE Registration Files (*.reg)". Always check the exported
files in notepad for parsing errors.
ROM will not build:
Most errors are space related. Make sure you got at least 1,5GB of free space on the partition, where you placed the kitchen.
Make sure the kitchen is placed in the root of a partition (e.g. "D:\Blackstone_WM65_kitchen")
Be sure, that the kitchen contains no folders with blanks in their name.
If any errors occour while building the ROM with ervius kitchen, which are VB based, make sure you got
Microsoft .NET Framework 3.5 installed.
Time bomb:
No need to worry about them, I didnt have one in the last three releases, I think these are shipping versions for the OEMs, but MS is still
improving things (like the slider speed in this Version) and it is no hack like removing animations or sth. like this. Furthermore ervius kitchen
would autmatically remove timebombs if found. So releases with this kitchen can be always used.
WM65 lock:
Some users don't like the WM65 "slide lock" feature or want to use their own locking program. In cooked ROMs use
"PHM RegEdit" in "Utilities" folder of your device to disable the locking feature, as the following code shows:
Code:
[HKEY_CURRENT_USER\ControlPanel\Backlight]
"AutoDeviceLockEnable"=dword:00000000
In the kitchen there is also a registry entry for that:
"REG_AutoDeviceLock_ON" in "MY_REG_Tweaks". Just disable that, if you cook your own ROMs with the kitchen to disable autolock.
(I prefer to use it)
FAQs: Part X
Part X of the FAQs
FAQs: Temporarily fixes/ hints for different builds
Temporarily fixes/ hints for different builds :
23004
Bluetooth HTC Comm Manager:
For (de-) activating Bluetooth, don't tap the green switch, tap left of the switch on the text saying "Bluetooth" and watch your taskbar, if the icon appears/ disappears. The switch is not working in that version. (But the workaround has the same effect )
HowTos/ tutorials
HowTos/ tutorials
WM65 honeycomb icons:
For easy editing of honeycomb icons, directly on your HTC device, start "hComber" from tools folder in the start menu.
General info for the kitchen:
In "EXT\SHARED\MY_Packages\APP_AAA_Icons" you will find the package for the Windows mobile 6.5 honeycomb icons.
Under "files" you will find all the icons in PNG format (90x90 Pixel for WVGA and 24bit depth), keep the naming convention, when creating
new icons. ("Start_Icon_APPNAME.png") See your windows folder for the standard WM6.5 honeycomb icons (e.g. "Start_Icon_Solitaire.png")
for sample icons. Put all your new icons in "EXT\SHARED\MY_Packages\APP_AAA_Icons\files\".
After creating new icons, you will have to add them to the registry. Use notepad for editing "EXT\SHARED\MY_Packages\APP_AAA_Icons\0407\app.reg".
Normal apps:
You got a REG key for every "*.lnk" file in "Windows\Start menu\Programs\" folder. e.g.:
[HKEY_LOCAL_MACHINE\Security\Shell\StartInfo\Start\AIM.lnk]
"Icon"="\\Windows\\Start_Icon_AIM.png"
I think it is self explaining, that you have to add such a key for your app/ icon, according to the sample.
Folders:
Same thing for apps in folders (e.g. Startmenu's "Utilities" folder), you just have to to add the folder before the "*.lnk" file in the registry.
Folders are created using "app.dat" for each language (e.g. "EXT\SHARED\MY_Packages\APP_AAA_Icons\0407\app.dat"). See the file
(e.g. with notepad), it is self explaining. Add a new line for each directory. This way you can create your own directories in the start menu
folder.
Icons for folders are applied through a reg entry for the directory itself, e.g.:
[HKEY_LOCAL_MACHINE\Security\Shell\StartInfo\Start\Multimedia]
"Icon"="\\Windows\\Start_Icon_Folder_Multimedia.png"
these are also in the language specific app.reg files. (e.g. "EXT\SHARED\MY_Packages\APP_AAA_Icons\0407\app.reg" as stated above.
System Icons:
System icons are mostly described by CPL numbers. Changes to them can be made by editing:
"EXT\SHARED\MY_Packages\APP_AAA_Icons\app.reg". I devided these from the other ones, because they are not language specific and all
packages and fixes made by me are supposed to be used in multilanguage kitchens.
By the "*.pngs" name you know which number belongs to which system shortcut. If you update a package in one of the folders of
"EXT\BlackStone\COMMON\" (e.g. "TouchFLO 3D") these numbers will change. So you will have to update
"EXT\SHARED\MY_Packages\APP_AAA_Icons\app.reg" as well.
The packages CPL number can be found out by editing the *.rgu" (registry file) or "app.reg" of the package you updated.
(e.g. "EXT\BlackStone\COMMON\BlackStone_External_Packages\TouchFlo_3_0_32567_2\938d4209-f7c2-4ea5-9b57-a338c0c645f8.rgu")
Manila program launcher icons:
Create a PNG:
Use you favorite image manipulating program (e.g. GIMP). The PNGs are 128 x 128 pixels and 24bit, no interlace.
Save it to "MyTools\Icon_Tools\CFC_Tool\_PNGs\APP_NAME.png" (no spaces in name)
Use CFC GUI to convert PNGs:
Up to date versions in this thread: http://forum.xda-developers.com/showthread.php?t=437777
Browse to "MyTools\Icon_Tools\CFC_Tool" folder, run "cfc_gui.exe", press "F3" (or "File"=>"Select folder"), choose the path:
"MyTools\Icon_Tools\CFC_Tool\_QTCs". Choose "Tools"=>"Import from PNGs"=>"Yes", locate the folder, where your PNGs are stored.
After conversion has been done, you'll end up with some new files in "MyTools\Icon_Tools\CFC_Tool\_QTCs" folder. So you can close
"CFC GUI".
Compress the icon:
Start "MyTools\Icon_Tools\CFC_Tool\1_compress_to_cfc.bat". The new files are stored in "MyTools\Icon_Tools\CFC_Tool\_CFCs\"
Renaming the files:
Rename the files to the naming convention. (e.g.: "MPI_MY_AIM.qtc") by starting: "MyTools\Icon_Tools\CFC_Tool\2_rename_to_qtc.bat"
Correct last spelling issues like capitalisation.
Copying the files:
From your PC copy the compressed icon files in "MyTools\Icon_Tools\CFC_Tool\_CFCs\*.*" to your phone's storage card. To test the files
on your device open "Total Commander" from "Utilities" folder and copy them to "\windows" folder.
Testing the icons:
Start "PHM RegEdit" from "Utilities" folder. Navigate to: "[HKEY_LOCAL_MACHINE\Software\HTC\Manila\ProgramLauncher]" The folders from
"0" till "29" contain the different apllications and the icon link. Choose the one you want to change. (e.g. "10:"IconPath"="windows\MPI_MY_ICQ.qtc"")
SOFT RESET!
Exporting for the kitchen:
When everything works fine, start "PHM RegEdit" again and export the: "[HKEY_LOCAL_MACHINE\Software\HTC\Manila\ProgramLauncher]" key
to your storage card.
Copy the CONTENT! of the reg file into app.reg file in "EXT\SHARED\MY_Packages_EXPERIMENTAL\APP_Manila_ProgramsTab_ON\0407\app.reg"
into the kitchen folder. (For german translations, 0409 for WWE)
Copy the icon files from "MyTools\Icon_Tools\CFC_Tool\_CFCs\*.*" to "EXT\SHARED\MY_Packages_EXPERIMENTAL\APP_Manila_ProgramsTab_ON\files\*.*"
Enable "APP_Manila_Rhodium_QTC" and "APP_Manila_ProgramsTab_ON" in ervius kitchen! You are ready to have cooked in manila program launcher icons!
Hints:
"OEM\BlackStone\0407\OperatorPkg\mxipupdate_oemoperators_102.provxml" contains the OEM standard links. (These were commented out
as sample, changes should be made to "EXT\SHARED\MY_Packages_EXPERIMENTAL\APP_Manila_ProgramsTab_ON\0407\app.reg") instead.
Also reserved
Also reserved
another reserved post for HowTos
another reserved post for HowTos
HowTos/ tutorials
Porting new WM65 builds into the kitchen: (Part I)
Example on Da_G's source, build 23052:
Thread:
[OS][WM6.5.x] Latest Releases (23052), Porting, Tutorials, Tools, VM, etc.
In this example the new release build, we want to port to the kitchen is 23052. Build 23037 is used as the old build version and the language is "0407" (german). But you can use this guide for any new/ old build version (e.g. 23054/ 23016) and any language. To port other languages, just replace the the language specific code with the one for your language. (e.g. 0409=english; 040c= french; 041D=swedish)
Obtain needed files:
Initflashfiles.dat for all languages (for build 23052)
Code:
Filename: "initflashfiles-dat-all-langs.zip"
=> This file is needed for language specific WM65 links in your startmenu
0407 DEU German Deutschland (for build 23052)
Code:
Filename: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar"
=> These are the german MUI files for the WM65 build
0409 USA English United States (for build 23052)
Code:
Filename: "WM65-23052-CE-OS-5-2-4098-LANG-0409-DPI-ALL-RESH-ALL-RESV-ALL.rar"
=> This is needed for the device specific DPI (192 for BlackStone's resolution)
23052 XIP/SYS CE OS 5.2.4098 Lang 0409 DPI 192 RESH 480 RESV 640
Code:
Filename: "WM65-23052-CE-OS-5-2-4098-LANG-0409-DPI-192-RESH-480-RESV-640.rar"
=> This is the WM65 operating system (OS)
Extract OS build and MSXIPKernel
Source: WM65-23052-CE-OS-5-2-4098-LANG-0409-DPI-192-RESH-480-RESV-640.rar
Code:
Extract:
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0409-DPI-192-RESH-480-RESV-640.rar\23052"
To: "SYS\"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0409-DPI-192-RESH-480-RESV-640.rar\Shared\23052\MSXIPKernel"
To: "ROM\Shared\23052\"
This is the WM65 build specific part of the kernel (MSXIPKernel), it changes with every release. So it has to be
updated in the kitchen, when testing new releases.
Copy OEMXipKernel:
Code:
Copy (including whole content):
Folder: "ROM\BlackStone\23037"
To: "ROM\BlackStone\23052"
This is the device specific part of the kernel (OEMXipKernel), its identical for each release, until HTC releases a
new BlackStone ROM, where we can dump a new device specific part.
Delete wrong resolutions:
Code:
Delete folder: "\SYS\23052\dpi_192_resh_480_resv_640"
Because BlackStone needs "dpi_192_resh_480_resv_800".
Create correct resolution folders:
Code:
Create folders:
"\SYS\23052\dpi_192_resh_480_resv_800"
"\SYS\23052\dpi_192_resh_480_resv_800\0407"
"\SYS\23052\dpi_192_resh_480_resv_800\COMMON"
Because BlackStone needs "dpi_192_resh_480_resv_800".
Extract correct resolutions files
Source: WM65-23052-CE-OS-5-2-4098-LANG-0409-DPI-ALL-RESH-ALL-RESV-ALL.rar
Code:
Extract: All folders ending in "*_dpi_192_resh_480_resv_800"
In this case:
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0409-DPI-ALL-RESH-ALL-RESV-ALL.rar\base_dpi_192_resh_480_resv_800"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0409-DPI-ALL-RESH-ALL-RESV-ALL.rar\MediaOS_dpi_192_resh_480_resv_800"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0409-DPI-ALL-RESH-ALL-RESV-ALL.rar\Phone_dpi_192_resh_480_resv_800"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0409-DPI-ALL-RESH-ALL-RESV-ALL.rar\Redist_dpi_192_resh_480_resv_800"
To folder: "\SYS\23052\dpi_192_resh_480_resv_800\COMMON"
Extract DPI files:
Source: WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar
Code:
Extract: All folders ending in "*_0407_DPI_192_RESH_480_RESV_800".
In this case:
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Base_Lang_0407_DPI_192_RESH_480_RESV_800"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Themes_Lang_0407_DPI_192_RESH_480_RESV_800"
To folder: "\SYS\23052\dpi_192_resh_480_resv_800\0407"
Create folder for language specific DPI files:
Code:
Create folder: "SYS\23052\DPI_192\0407"
Extract language specific DPI files:
Source: WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar
Code:
Extract: All folders ending in "*_0407_DPI_192".
In this case:
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Base_Lang_0407_DPI_192"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Enterprise_Lang_0407_DPI_192"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Entertainment_Lang_0407_DPI_192"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Office_Lang_0407_DPI_192"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Phone_Lang_0407_DPI_192"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\PhoneRedist_Lang_0407_DPI_192"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Redist_Lang_0407_DPI_192"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Transcriber_Lang_0407_DPI_192"
To folder: "SYS\23052\DPI_192\0407"
Create folder for language specific OS packages:
Code:
Create folder: "SYS\23052\SHARED\0407"
Extract language specific OS packages:
Source: WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar
Code:
Extract: All folders ending in "*_Lang_0407".
In this case:
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\ADC_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\AdobeFlash_LANG_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Autoupdate_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Base_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Bluetooth_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Browsing_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\browsingie_LANG_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Bth_A2DP_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Bth_HID_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Bth_Watch_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\CHome_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Enterprise_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Entertainment_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Fwupdate_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\IPSECVPN_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\IRDA_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\MediaOS_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\MSTag_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Office_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\OneNote_lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Phone_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\PhoneRedist_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Redist_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\RemoteDesktopMobile_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Skybox_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Skymarket_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\SqlCeMobile_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\Transcriber_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\VoiceCommand_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\WelcomeCenter_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\WindowsLive_Lang_0407"
Folder: "WM65-23052-CE-OS-5-2-4098-LANG-0407-DPI-ALL-RESH-ALL-RESV-ALL.rar\WMWidgets_LANG_0407"
To folder: "SYS\23052\SHARED\0407"
Extract initflashfiles.dat
Source: "initflashfiles-dat-all-langs.zip"
Code:
Extract:
File: "initflashfiles-dat-all-langs.zip\0407\initflashfiles.dat"
To: "OEM\BlackStone\0407\OEM_Lang_0407\initflashfiles.dat"
You may backup your old one, if you like. This is for creating links in WM65's startmenu.
Create folder for build specific extensions:
Code:
Create folder: "EXT\BlackStone\23052"
COPY THE DUMMY PACKAGES:
Code:
Copy:
Folder: "SYS\23037\SHARED\COMMON\FWUPDATE_Dummy"
Folder: "\23037\SHARED\COMMON\SQM_Dummy"
To folder: "SYS\23052\SHARED\COMMON\"
These are needed fo deactivating MS's home phoning functions (recommended). Deactivate
the corresponding "non dummy packages" (e.g. "SQM") and acrivate these ones in
ervius kitchen.
HowTos/ tutorials
Porting new WM65 builds into the kitchen: (Part II)
REDUCE SPACE:
Code:
Delete:
Folder: "SYS\23052\SHARED\COMMON\IRDA"
Folder: "SYS\23052\SHARED\0407\IRDA_Lang_0407\"
Because BlackStone has no IRDA. This is just an example. If you want to reduce more space, delete the
packages you like with their corresponding language. But remember, you don't have to delete them, you
can deactivate them in your ervius kitchen project, by doubleclicking the package, which sets it's
"Included" option to "False". So this package wont be build and doesn't waste space on your device.
RECMOD PACKAGES (the manual way):
Code:
Source: "TOOLS\RecMod.exe"
Create a shortcut of "RecMod.exe" to your desktop.
Navigate to:
"SYS\23052\SHARED\COMMON\browsingie\"
Drag and drop each "DLL folder" (e.g.: "browsui.dll") to the "RecMod.exe" shortcut on your desktop. A small
DOS windows will appear and close automatically. After that navigate to the folder of any DLL:
e.g.: "SYS\23052\SHARED\COMMON\browsingie\browsui.dll". You will notice a new DLL ("browsui.dll" in this case).
This is the unpacked version of the module. A module consists of at least three files: imageinfo.txt, imageinfo.bin,
S000. There can be more like S001, S002, S003 on so on. These modules are optimized for the BlackStone's (or any
other WM65 device) module memory. Due the module memory for the BlackStone being really limited, one has to make
files of some of them, or WM65 won't boot (Even with BlackStone native WM65 kernel, aware of WM65's slot 60 and 61).
After dragging and dropping all the files to your "RecMod.exe" shortcut, you will have to delete the modules.
Because in a windows file system a folder and a file cannot have the same name, you have to rename the folder, before
copying the new made "file DLL". e.g.: Rename "browsui.dll" to "browsui.dl" and then copy
"SYS\23052\SHARED\COMMON\browsingie\browsui.dl\browsui.dll" to
"SYS\23052\SHARED\COMMON\browsingie\browsui.dll". After that delete the module folder
("SYS\23052\SHARED\COMMON\browsingie\browsui.dl"). You will have to do this with every recmodded module.
I recommend to recmod the modules of at the following packages:
- Internet Explorer ("SYS\23052\SHARED\COMMON\browsingie")
- Microsoft Tag ("SYS\23052\SHARED\COMMON\MSTag")
Do not recmod the MUI files, these are small sized and not worth it. I do NOT recommend to recmond files
of the base as well. HTC has many modules in the new WM65 devices (like LEO/ FireStone). Modules
enhance speed and memory consumption. But because the module memory of the BlackStone is limited, you
cannot put too many of them into it.
Further information on modules will be posted later in the FAQ.
RESERVED
as u might have guessed, its reserved

[SOLVED] Smali + baksmali

---nvm got it working myself
pretty simple actually. Download the baksmali and the smali .jar files and just execute them on the appropriate files. Baksmali is icelandic i believe for diassembler whereas smali is icelandic for assmebler.
Syntax: java -jar baksmali.jar xxxx
haven't used smali to reassemble yet but will write the syntax when I get that.
You should post up how/what you did.
[Guide] baksmali guide howto example
This is a lame quick way to unpack and pack a apk a bunch of apks using baksmali current as of 8:34 AM 2/9/2010
hxxp://rmccurdy.c0m/scripts/ quickbaksmali.zip
Code:
* requires java ! in %PATH% !
* just place the java_ee_sdk-5 folder to make it portable !
* put the APKS files in the folder APKS
* you (can) edit the job2.bat with your keytool/key info etc ..
* run the baksmali.bat
* make your changes etc
* run the smali.bat
you should see the updated \META-INF folder in the 'new' apk
and the classes.dex should be new.
-rmccurdy.com
reference:... NM can't post urls
interesting and very handy. thanks,

Android Mate 1.0.5 - App manager + Root file explorer + Installer + Task manager

Android Mate 1.0.5 is released with many improvements! Android Mate, as its name suggests, implements what should be standard in Android system:
* Use tag to organize your apps.
* Fast context menu of application, including uninstall, backup, restore, properties, manage.
* Be able to stop running applications.
* Change icon and name of app in Android Mate home.
* Root file explorer, support copy, cut, paste, delete and rename. Can be sorted by name, or size or last modified time.
* Fast APK installer.

[RELEASE] Metamorph - Theme Control File Upgrader

Stericson have a new Metamorph App.
It uses xml theme control files instead of the old thm files.
danation from the ModMyMoto forum has made a program, that updates the thm file to the new xml format.
It works very very well.
Please at all themers:
Use the Pro Version, use the new Metamorph with xml. Upgrade your Morphs with the xml files. Its not many work for you, but you can help us themers and users if you do this.
Download
http://www.4shared.com/file/5l0E6t76/ThemeControlFileUpgrader.html
Original Post at ModMyMotoForum
http://www.modmymoto.com/forums/showpost.php?p=3917253&postcount=10
Thanks, danation, thanks stericson! Great work!
Ummm, do you themers not use the pro version?
Only a question. I think, this app from stericson is every buck worth!
I've upgraded my themes all for Metamorph xml files.
Now all themes have an xml AND a thm file, so everybody could use them.
Today is the day.
I hope, you themers out there have changed your theme control files to the new one (*.xml)
Today, stericson has released the new Metamorph free version which supports only the xml file.
Please update your themes. We dont want to have some chaos in the theming community, isn't it so?
Stop getting angry at Stericson for moving Metamorph into a safer environment for the user (giving more information as to what is being changed).
HTCClay put it best:
@Stericson you can't update...where do you get off making things better? How dare you...
Click to expand...
Click to collapse
This utility is VERY easy to use and will convert any .thm file to .xml in seconds.
JAguirre1231 said:
This utility is VERY easy to use and will convert any .thm file to .xml in seconds.
Click to expand...
Click to collapse
Thanks I've updated it, in case anybody still needs some converting to do. This is the final version, unless there are any bug fixes needed.
Included in the download is an executable JAR file that will work on any operating system that has the Java Runtime Environment installed (version 6 or later.) Windows, Mac, and most Linux Distros will be able to run this program.
An equivalent EXE file was also added for the convenience of Windows users.
Original download location at M3 is here.
Download from XDA here.
-1.3-
* Drag and drop directories - All .thm files in the directory and all subdirectories will be converted. Other files are ignored. You can convert all of your themes at the same time
-1.2-
* Drag and drop feature added (I borrowed some public domain code found here.) Tested on Windows 7 and Ubuntu. Should work on Mac and Kubuntu as well.
* Option to disable dialogs
-1.1-
* Fixed bug that always warned about duplicate files
* When errors are found, it finishes writing all valid data before terminating.
-1.0-
* Ignores single blank lines
* Captures notes after double blank lines
* Adds functionality to enter in header information
* Prevents file overwriting
* Puts framework at the bottom no matter where it is in the .thm file
I'm still not clear on how you actually *use* this converter. Could someone post a step-by-step breakdown? Right now, I have the thing sitting on the root of my SD. Do I need to move it to the Android Themes?
No, not using with your mobile phone.
Copy it to your pc.
Open the Programm and take your *.thm file you want to convert to an *.xml file.
Thats all.

[Q] Customized ROM

Is there a guide how to put your own apps in system\app??
i tried searching closes to this is a kitchen but i'm having some problems understanding it...
if there is a guide please do paste some links i want to learn how to edit and personalize the best roms that the devs here has created
thanks in advance
sorry this is not an answer but i know what you mean.. i tried just putting the apk in the app folder than zipping and signing the rom but the app never installs on boot... so please someone answer this question.. lol
Its pretty simple, all you have to do is
Unzip ROM, remove APK(s) from /system/app, add APK(s) to /system/app (or /data/app if you want them to be removable), rezip ROM, flash it.
but heres a more indepth explanation:http://www.askabouthugo.com/mobile-technology/how-to-remove-unused-android-apps-from-custom-rom/
heres another good link:
http://forum.xda-developers.com/showthread.php?t=639726
I strongly recommended installing dsxidia's rom kitchen, probably the best kitchen for customizing roms.http://forum.xda-developers.com/showthread.php?t=633246
Thanks for your answer... ill check it out,
i tried installing the ROM Kitchen but i cant get it running...
i wonder why...
im using windows 7 64bit...
when i run the icon on my desktop the cmd quickly appears and disappears
i tried to edit the batch file... added pause just so i could see the error message
'bash' is not a recognized as an internal or external command, operable program or batch file.
i check the location of what this batch file was trying to call
nothings under the bin on the installation path
any suggestions? ^_^
marchking said:
i tried installing the ROM Kitchen but i cant get it running...
i wonder why...
im using windows 7 64bit...
when i run the icon on my desktop the cmd quickly appears and disappears
i tried to edit the batch file... added pause just so i could see the error message
'bash' is not a recognized as an internal or external command, operable program or batch file.
i check the location of what this batch file was trying to call
nothings under the bin on the installation path
any suggestions? ^_^
Click to expand...
Click to collapse
some apps can be put in data/app folder instead of system/app
ldrifta said:
some apps can be put in data/app folder instead of system/app
Click to expand...
Click to collapse
some apps can be put in data/app folder instead of system/app
well my real issue is i want to fix some bugs with froyo by laszlo... which seems that the applications installed in sd - ext or external disappears when usb mass storage is used... im not completely sure that the usb mass storage is the one that triggers the bug... but what im thinking of is putting the apps that i want in system/app... coz when the bug happens it seems like it on safe mode only system apps are running then the app that are in data/app disappears
marchking said:
i tried installing the ROM Kitchen but i cant get it running...
i wonder why...
im using windows 7 64bit...
when i run the icon on my desktop the cmd quickly appears and disappears
i tried to edit the batch file... added pause just so i could see the error message
'bash' is not a recognized as an internal or external command, operable program or batch file.
i check the location of what this batch file was trying to call
nothings under the bin on the installation path
any suggestions? ^_^
Click to expand...
Click to collapse
Did you install exactly as instructed? Did you install jdk before you installed cygwin as instructed? Did you follow the kitchen.readme in the cygwin file when setting up cygwin? I say reinstall it but make sure you do every step correctly.
Sent from my COS-DS using XDA App
maximo360 said:
Did you install exactly as instructed? Did you install jdk before you installed cygwin as instructed? Did you follow the kitchen.readme in the cygwin file when setting up cygwin? I say reinstall it but make sure you do every step correctly.
Sent from my COS-DS using XDA App
Click to expand...
Click to collapse
i did follow the instructions carefully...
im not sure why nothing gets installed on the cygwin folder...
if i check the files inside the folder nothings there...
ill try to install it again tomorrow once i get home from work...
marchking said:
i did follow the instructions carefully...
im not sure why nothing gets installed on the cygwin folder...
if i check the files inside the folder nothings there...
ill try to install it again tomorrow once i get home from work...
Click to expand...
Click to collapse
theres 2 kitchen.readme's one in the kitchen , and one in the cgywin.zip you downloaded, when installing cygwin, follow the directions in the kitch.readme in the cygwin.zip
this is what mine says:
1) Unzip the contents of this archive
2) Run Setup.exe
3) Select "Install from Local Directory"
4) The root directory can be C:\Cygwin if you want, but ensure there are NO SPACES in the folder name
5) Local Package Directory *must* be the path to the cygwin_packages folder that you just extracted
6) When it shows all the package names, go to the top and select "All <-> Default" until it changes to "All <-> Install" (you must click on the arrows)
7) Click on Next and it will install everything you need for the Android Kitchen
This Cygwin installation includes the following packages, required for the kitchen to work:
* Devel / gcc
* Interpreters / perl
* Utils / cpio
* Utils / util-linux
* Utils / ncurses
* Archive / zip
* Archive / unzip
* Web / wget
Also, dont forget to rename the dsxidia folder to "kitchen", makes things easier.
maximo360 said:
theres 2 kitchen.readme's one in the kitchen , and one in the cgywin.zip you downloaded, when installing cygwin, follow the directions in the kitch.readme in the cygwin.zip
this is what mine says:
1) Unzip the contents of this archive
2) Run Setup.exe
3) Select "Install from Local Directory"
4) The root directory can be C:\Cygwin if you want, but ensure there are NO SPACES in the folder name
5) Local Package Directory *must* be the path to the cygwin_packages folder that you just extracted
6) When it shows all the package names, go to the top and select "All <-> Default" until it changes to "All <-> Install" (you must click on the arrows)
7) Click on Next and it will install everything you need for the Android Kitchen
This Cygwin installation includes the following packages, required for the kitchen to work:
* Devel / gcc
* Interpreters / perl
* Utils / cpio
* Utils / util-linux
* Utils / ncurses
* Archive / zip
* Archive / unzip
* Web / wget
Also, dont forget to rename the dsxidia folder to "kitchen", makes things easier.
Click to expand...
Click to collapse
yeah ive followed carefully the instructions...
but im getting bothered with this part
6) When it shows all the package names, go to the top and select "All <-> Default" until it changes to "All <-> Install" (you must click on the arrows)
when i click on it it changes to install then click again uninstall then default then something else... i made sure that install is selected...
still nothing gets installed in the cygwin folder... there are folders there but under bin and other folders not much is there...
btw i was wondering where i should put the dsxidia kitchen folder?
maximo360 said:
theres 2 kitchen.readme's one in the kitchen , and one in the cgywin.zip you downloaded, when installing cygwin, follow the directions in the kitch.readme in the cygwin.zip
this is what mine says:
1) Unzip the contents of this archive
2) Run Setup.exe
3) Select "Install from Local Directory"
4) The root directory can be C:\Cygwin if you want, but ensure there are NO SPACES in the folder name
5) Local Package Directory *must* be the path to the cygwin_packages folder that you just extracted
6) When it shows all the package names, go to the top and select "All <-> Default" until it changes to "All <-> Install" (you must click on the arrows)
7) Click on Next and it will install everything you need for the Android Kitchen
This Cygwin installation includes the following packages, required for the kitchen to work:
* Devel / gcc
* Interpreters / perl
* Utils / cpio
* Utils / util-linux
* Utils / ncurses
* Archive / zip
* Archive / unzip
* Web / wget
Also, dont forget to rename the dsxidia folder to "kitchen", makes things easier.
Click to expand...
Click to collapse
got it fixed! yeah!
the problem was...
when i extracted the files...
5) Local Package Directory *must* be the path to the cygwin_packages folder that you just extracted
ok its there...
but the when i open the cygwin_packages folder there is another folder containing all the things it needs...
i cut those things and moved it to cygwin_packages folder
before it was like cygwin_packages/$#@%^dsakjdgaskd%[email protected]#%^ folder
Time to cook! ^_^
marchking said:
Time to cook! ^_^
Click to expand...
Click to collapse
glad to hear it worked

Categories

Resources