yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Themes] adderz91:
Splash Screens

Now the following to screens replace the second or third screens you see when you boot your device. I cant remember which one exactly. These match the "Red" and "Lime" themes up above. These also wernt done by me but im uploading them again because i think they fit in perfectly.

Simply rename them welcomehead.96 then copy them to the Windows folder, you may need to use TotalCommander or Resco File Explorer to copy it over if File Explorer wont let you.

Welcome Heads Download Link
[General Topics] MarkRain:
I decided to buy a contact/dialer/callerID program for my samsung and i'd like to know your opinion about the option i can choose from.

I tried Iconsoft PhonEx and Resco Contact Manager, and i found vantages and disadvantages on each program...

Can you tell me which program would you buy and why? :)
[General Topics] MarkRain:
No suggestion for such a software??

What i'd like to have is:

-Nice caller ID that override the system one.

-A contact manager easy to use, expecially with a good searching function.

-A dialer nicer than the default wm one. (that's not hard :D)

-Popups for incoming messages (for that i already use Vito sms-chat)

Inesoft Phonex have almost all that, but the search though the contacts is a panic, the letter scrollbar is too small for me.

Resco contact manager has some problem to override the system caller id in my phone, the default one in shown over the resco one.

Is there a more complete solution??

edit: maybe it's the wrong section?? :o
[General Topics] deedee:
Contact Manager i use iContact and for caller id i use the full screen option from S2U.
[General Topics] MarkRain:
Thanks, this could be a nice solution...

Icontact has a good search function, and s2u a good caller id.

I was looking for a more intergate solution, but i'll give a try :)
[G1 General] nabzilla1990:
just wondering if anyone is thinking of Tweaking the HTC Magic Rom to make it faster and better with voice search and other needed features
[G1 General] dgrave:
Keep looking through android development, its in here...dunno if its with your exact requests but...

As for the voice search, i did exactly what the post thread said and just added from adp1.5, so i added voice search.apk, worked like a charm after i rebooted.

http://xdaforums.com/showthread.php?t=517646&highlight=haykuro
[G1 General] harpreet1988:
Why not just use a Rogers build? Rogers ROM is identical to the Magic ROM.
[G1 General] nabzilla1990:
no the magic rom looks better overal
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] akash_84:
Hi all,

Strange one here - my topaz turns itself on? Not sure if it is a powerbutton issue or software but I can only replicate it when I put the phone down or pick it up

Will try hard reset to see if its software causing it - very strange issue though!

Anyone remember the application that locks ALL buttons? Another test will be to lock all buttons including power button unless I remove the stylus or something.
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] akash_84:
OK I think I solved it.

Seems to be the stylus - whether it is the stylus itself (because I might have mixed it up with a TD1 or a HD) or whether it is something inside - who knows

I'll test with the spare stylus when I get home - interesting though eh? :)_
[Windows Mobile Software Development] 12aon:
When I first started on this project, this kitchen existed of 5 script each containing few lines of code, only able to handle one LUA script at a time. I had just helped out on the first ever manila 2.0 VGA port and I could see the use of a kitchen that did most of the manual labour automatically. At that time my understanding of what needed to be done to successfully edit script was limited. As I tried to add more features to the script I learned more about LUA, the handling and decompiling of the scripts. I chose to make the kitchen do as much for you on first run. The kitchen got more mature after I met hilaireg who knew a lot more about batch scripting than I did and who's perfectionist style made the kitchen what it is today.

After we teamed up we started a little manila group and got into contact with co0kiemonster. He's the one who created\updated most of the tools on which the script relies, and so not only optimizing manila handling but also pushing it's boundaries. We put in the applications that best handle manila files and connected these via the script. Since our last update co0kie kept developing the tools and they became a lot better. A batch script isn't really the way to handle this but until we get a real manila GUI, we decided to give the script one last update. Since this will likely be the last big project hilaireg will be presenting here, this last version is dedicated to him.

Workstation/System Requirements:

The Manila Kitchen environment can run on a Windows XP, Windows Vista, and Windows 7 platform providing the following requirements are met:

Microsoft .NET 3.5 SP1 (M9Editor)

Elevated priviledges

Windows XP/Vista/Seven

Kitchen Contents:

ROOT

MANILATOOL.CMD by hilaireg & 12aon

Manila Kitchen Guide

Revision History

_SOURCE folder

_TOOLS folder

Shortcuts to tools

TOOLS

LUATOOL.EXE by Co0kiemonster

M9EXT.EXE by Co0kiemonster

MANILANAMES.EXE by Co0kiemonster

M9EDITOR.EXE by 6Fg8

CFC_GUI.EXE by Chainfire

NOTEPAD2.EXE by Florian Balmer, Compiled by Co0kiemonster

MANILAHASH.EXE by NisseDILLIGAF

XVI32.EXE by Christiaan Maas

RAPICOPY.EXE, RAPIPROC.EXE, RAPISTART.EXE by Scott Seliman

GREP.EXE by Tim Charron

Current Version (Attached Files)

Manila Kitchen 5.05.06, 4.7 MB (06/05/2010)

Previous Versions

Manila Kitchen 5.04.23, 4.7 MB (23/04/2010)

Manila Kitchen 5.03.04, 4.1 MB (04/03/2010)

Manila Kitchen 4.10.16, 9.3 MB (16/10/2009)

Manila Kitchen 4.10.02, 7.7 MB (02/10/2009)

Credits:

Special thanks to the following folks for sharing their knowledge and expertise. If I missed someone, it's purely accidental – send me a note and I will add your name to the list.

6fg8

chainfire

co0kiemonster

sztupy
[Windows Mobile Software Development] 12aon:
Overview

The Manila Kitchen is an automated environment that includes tools (utilities) to perform decompilation, editing, and recompilation of HTC Manila OEM files.

Instructions are passed to the MANILATOOL command script which in turn, initiates various executables to perform the necessary actions required on the HTC Manila OEM files.

Some of the tools used by MANILATOOL were written by 6fg8, chainfire, co0kiemonster, and sztupy. As such, some of these tools are not compatible with excessively long path names or paths that contain spaces or brackets. To avoid issues, place the Manila Kitchen in a relatively short path that does not contain spaces or brackets such as: C:\XDA\Manila_Kitchen

The Manila Kitchen provides the following benefits:

Consolidated Tools

All of the tools required to perform Manila related activities have been incorporated. These include decompilation, comparison, recompilation, .CAB creation, direct deployment to mobile devices, updating Mode9 Editor reference index, and backing up. The executables are initiated with the appropriate command parameters and in the correct sequence by MANILATOOL thus eliminating the "guess work" typically required.

Improved Resiliency

The activities required to manage HTC Manila OEM files are complex in nature. In some cases, a Manila file may fail to be decompiled or cause one of the initiated executables to generate and error as a result of an unexpected condition. The MANILATOOL command script will attempt to recover from such errors when possible so as to complete the command that was initiated.

Command Line Help and Version Information

Wondering what command parameters are available in the MANILATOOL command script? Simply append -HLP to the end of the MANILATOOL command script to display a summary of parameters available. To determine the version of the MANILATOOL command script in use, append -VER to the end of the MANILATOOL command script.

Enhanced File Recovery

Accidentally changed a file and need the previous version? The MANILATOOL command script performs a backup before any critical operation making it easier to retrieve a previous version of a file.

Enhanced Script Diagnostics

Although a significant of amount effort has gone into the development of the Manila Kitchen, it is possible that a script logic error may occur. To assist in troubleshooting such errors, the MANILATOOL command script includes a comprehensive logging debugger.

Topic Index

Preparing the Kitchen Environment ....... 3

Initializing the Kitchen​

Decompiling Manila OEM Files ............ 4

LUA Editing

Mode9 Editing

General Editing

Updating 'm9editor.names.txt'

Updating the Repository​

Working with Manila Files ............... 5

Initializing the Kitchen​

Recompiling Manila OEM Files ............ 6

Recompilation​

Testing the Manila OEM File Changes ..... 7

Installer .CAB Method

Direct to Device Method
​

Reference Web Links ..................... 8

Frequently Asked Questions (FAQ) ........ 9
[Windows Mobile Software Development] 12aon:
Preparing the Kitchen Environment

The Manila Kitchen environment must be initialized prior to initial use. During the initialization phase, all MANILATOOL command script parameters are enabled and the contents of following folders, sub-folders, and files are removed and recreated:

_backup

_queue

Decompiled

Release

Repository

Workspace

The following configuration files will be reset to their initial settings:

m9editor.cfg .\_TOOLS\M9Editor

notepad2.ini .\_TOOLS\Notepad2

xvi32.ini .\_TOOLS\XVI32

The following applications shortcuts will be reset to their initial settings:

CFC_GUI.lnk

M9Editor.lnk

manilaHASH.lnk

Notepad2.lnk

HexEdit32.lnk

The following Manila Mode9 reference index will be reset to their initial settings:

m9editor.names.orig.txt .\_TOOLS

mnf_m9paths.orig.txt .\_TOOLS

m9editor.names.orig.txt .\_TOOLS\M9Editor

Initializing The Kitchen

The following procedure will initiate the Manila Kitchen initialization process. All HTC Manila OEM files found in the .\_SOURCE folder will be copied to the .\_queue folder.

Currently, there are two versions of Manila reference index names; one for pre-Manila 2.5 and one for post-Manila 2.5. It is possible to set the initial Manila reference version during the kitchen initialization procedure. For example, if the .\_SOURCE folder contains a specific version of HTC Manila OEM files, specify the Manila version as part of the parameter. If the kitchen will contain a mix of pre-Manila 2.5 and post-Manila 2.5 files, an incomplete set of Manila files, or an unknown Manila file, specify 0.0 as the kitchen version.

The following procedure will initiate the Manila Kitchen initialization process.

► To initiate a Manila Kitchen reset and specify Manila version 1.3

Place a copy of the original (untouched) HTC Manila OEM files or packages in the .\_SOURCE folder.

Double-click (launch) the Command Prompt shortcut found in the root of the kichen folder.

At the prompt, type the following command: manilatool.cmd -oem:1.3

Press ENTER.

► To initiate a Manila Kitchen reset and specify Manila version 2.5

At the prompt, type the following command: manilatool.cmd -oem:2.5

Press ENTER.

► To initiate a Manila Kitchen reset and specify a mix, small set, or unknown Manila files

At the prompt, type the following command: manilatool.cmd -oem:0.0

Press ENTER.
[Windows Mobile Software Development] 12aon:
Decompiling Manila OEM Files

HTC Manila OEM files must be decompiled before changes can be made to them. The decompilation of HTC Manila OEM files occurs on files that are found in the .\_queue folder. Use the Manila Kitchen initialization process to copy the HTC Manila OEM files from the .\_SOURCE folder to the .\_queue folder before attempting to decompile files.

As files are processed, they are removed from the .\_queue folder and placed in a .\Processed folder. Once completed, decompilation mode will be disabled so as to prevent accidental loss of work to decompiled Manila files. The Manila Kitchen must be initialized in order to enable decompilation mode.

Decompilation

The decompilation process passes each manila file found in the .\_queue folder to the LUA processor (luatool.exe) tool. During the decompilation process, the LUA processor (luatool.exe) tool validates the decompilation and produces additional output files if the decompilation was not successful.

Additionally, the decompilation process will extract a copy of embedded Manila (Mode 9) scripts, initiate the LUA processor (luatool.exe) tool to decompile the extracted script, and validate that the decompilation occurred successfully.

Upon completion, a decompiled version of the Manila file will be found in one of the following folders - which are determined by the results of the decompilation process:

Completed: .\Workspace\_lua (successfully decompiled)

Incomplete: .\Workspace\_lua (partially decompiled)

Error: .\Workspace\_lua (failed decompilation)

InternetPortal: .\Workspace (XML files)

Manilapages: .\Workspace (XML files)

Mode9: .\Workspace (Mode9 files)

PNG: .\Workspace (Image files)

QTC: .\Workspace (Image files; in Graphics folder)

SQLite: .\Workspace (Database files)

TTF: .\Workspace (True Type Font files; in Graphics folder)

XML: .\Workspace (XML files)

Unknown: .\Workspace (Unknown files)

The following procedure will initiate the Manila Kitchen decompilation process.

► To initiate HTC Manila OEM file decompilation

Ensure desired HTC Manila OEM files are present in the .\_queue folder once the kitchen initialization has completed.

Double-click (launch) the Command Prompt shortcut found in the root of the kichen folder.

At the prompt, type the following command: manilatool.cmd -dec

Press ENTER.
[Windows Mobile Software Development] 12aon:
Recompiling Manila OEM Files

Once editing is complete, the Manila files must be recompiled before they may be used on a mobile device.

Should an error be encountered during recompilation, the MANILATOOL command script will create a Manila LUA error log file in the .\Release\_error folder and continue recompiling Manila LUA files. In the event of a "hard" recompilation error, the contents of .\Release\_lua folder will be removed and the previous successful recompilation will be restored.

Recompilation

The recompilation process occurs on files that found in the .\Workspace\_lua\Completed folder. Once completed, the files are ready for deployment to a mobile device that is directly connected to a workstation or via an installer .CAB file.

The following procedure will initiate the recompilation process.

► To initiate Manila file recompilation

At the prompt, type the following command: manilatool.cmd -rec

Press ENTER.
[Windows Mobile Software Development] 12aon:
Testing the Manila OEM File Changes

The Manila Kitchen environment provides additional tools for testing a final work product. Manila files can be distributed to mobile devices using one of the following methods:

Installed .CAB

Direct to Device

The quickest method of distributing recompiled Manila files is via an installer .CAB file. The direct to device method of distributing recompiled Manila files is via ActiveSync over a USB/Serial connection - this method is

quickest during development activities.

Installer .CAB Method

The MANILATOOL command script provides a parameter to automatically create a redistributable .CAB file. The installer .CAB can be copied to the mobile device and launched using the device File Explorer. Alternatively, the installer .CAB file may be installed via ActiveSync. Should an installer .CAB fail to install on a device, it is likely that policy restrictions are in effect.

The following procedure will initiate the .CAB creation process.

► To initiate the CAB Wizard tool

At the prompt, type the following command: manilatool.cmd -cab

Press ENTER.

Direct to Device Method

The MANILATOOL command script includes a parameter to automatically stop the mobile device Manila executable (manila.exe), transfer a copy of the Manila files, and restart the mobile device Manila executable.

The copy operation may fail on a device where policy restrictions are in effect. Additionally, the Manila executable may not restart in such cases.

The following procedure will initiate the comparison process.

► To initiate RAPI Copy tool

At the prompt, type the following command: manilatool.cmd -dep

Press ENTER.
[Windows Mobile Software Development] 12aon:
Reference Web Links

Manila 3D Kitchen

http://winmo.sztupy.hu/manilakitchen.html

http://xdaforums.com/showthread.php?t=487331

Manila Tutorial

http://xdaforums.com/showthread.php?t=399212

LUA Decompiler

http://xdaforums.com/showthread.php?t=568281

LUA 5.1 Decompiler

http://winmo.sztupy.hu/luadec.html

http://xdaforums.com/member.php?u=1433290

http://xdaforums.com/showthread.php?t=479910

LUA Decompiling Tutorial

http://winmo.sztupy.hu

http://winmo.sztupy.hu/manilakitchen/rhodium2_manila_wvga_src.zip

TF3D Manila Mode9 Editor

http://xdaforums.com/showthread.php?t=464984

MNF - Manila Name Finder

http://xdaforums.com/showthread.php?t=546820

CFC - The Manila/TF3D Image Editor

http://xdaforums.com/showthread.php?t=437777

TouchFLO/Manila/SenseUI

http://xdaforums.com/group.php?groupid=131

Co0kie's Beta Testing and Development

http://xdaforums.com/group.php?groupid=192

Max Sense Testers

http://xdaforums.com/group.php?groupid=185

GT7 Sense 2.1 Theme Beta Testers

http://xdaforums.com/group.php?groupid=202

Leaked Full EXT/Manila 2.5 Packages-latest official sprint tp2

http://xdaforums.com/showthread.php?t=642817
[Windows Mobile Software Development] hilaireg:
Enabling the Logging Debugger

Although a significant of amount effort has gone into the development of the Manila Kitchen, it is possible that a script logic error may occur. To assist in troubleshooting such errors, the MANILATOOL command script includes a comprehensive logging debugger.

The logging debugger can provide basic, expanded, or verbose (full) logging. To enable the logging debugger, append -DEB:[1-5] to the end of the MANILATOOL command script. For example, to set the logging debugger level to 1, type the following command at the Command Prompt:

manilatool.cmd -hlp -deb:1

Processing activities are displayed in the Command Prompt window and are recorded in the ManilaTool_Log_#.##.##.txt file. The log file will include the version of MANILATOOL command script and the command parameters that was requested. The following logging debugger levels are available:

Level 0:	Default. The MANILATOOL command script typically operates at this level.

Level 1:	Provides slightly more details on the script processing activities. Specifiy this logging level to view the results of actions performed on a Manila file.

Level 2:	Provides comprehensive details on the processing activities performed on a Manila file. Specify this logging level when trying to determine why a Manila file may have failed to be processed. Choosing this logging level on a large number of Manila files will increase the time it takes to complete Manila file processing.

Level 3:	Developer verbose level 1. Specify this logging level to view the script routine names that are invoked during operation as well as the variables that are dynamically set. Choosing this logging level on a large number of Manila files will greatly increase the time it takes to complete Manila file processing.

Level 4:	Developer verbose level 2. Specify this logging level to view the script routine names that are invoked during operation as well as the dynamic and common variables that are set. Choosing this logging level on a large number of Manila files will drastically increase the time it takes to complete Manila file processing.

Level 5:	Developer verbose level 3. Specify this logging level to view the script routine names that are invoked during operation, display all script variables. Additionally, this logging level will create a .\_debug folder which will contain a copy of the files that are normally removed during a script routine operation. Choosing this logging level on a large number of Manila files will significantly increase the time it takes to complete Manila file processing.

The following log files are generated during MANILATOOL command script processing:

ManilaTool_Log_#.##.##.txt

ManilaTool_FileCopyLog_#.##.##.txt

ManilaTool_LUAFilesLog_#.##.##.txt

ManilaTool_MNFLog_#.##.##.txt

ManilaTool_Mode9Log_#.##.##.txt

ManilaTool_NonLUAFilesLog_#.##.##.txt
[Windows Mobile Software Development] bilbobrian:
Very nice work as always 12 :)
[Windows Mobile Software Development] conflipper:
Very nice work on this, I am around now, So I can start to help out more, haha
[Windows Mobile Software Development] kinnyfaifai:
Forgive me for being an utter dumbass.

I've got your kitchen and was trying it out. However, what files do I need to drop into folder 01_manila? I've tried dropping just the manila file into it, the extracted *.luac scripts but I keep getting errors saying no files found.

Kindly point me in the right direction?

Thanks.

KF
[Windows Mobile Software Development] 12aon:
Yes sure, That's the reason I included the m9editor as well, for it's abilty todifferentiate between different kinds of manila files. Copy only the Lua files (unchanged) to the 01_manila folder. There is a checkbox in the m9editor and if you will check it, it allows copying of multiple files. After that you are good to go and you can run the 01_Decompile.bat, 12
[Windows Mobile Software Development] MRFERRARI23:
the 2 files I have in there now just look like this 18c01b6d_manila and 72ac571f_manila so I think they are in there right

as for running the program im doing so right from my desktop screen cause when I try to run it from c drive an I go to name the cab It doesnt give me that black pop screen it goes to this white page with info that doesnt allow me to do anything!

EDIT: how do I eliminate that space between mr vizziato?? I cleared the space by going to the start menu an going to my name but idk still nothing
[Windows Mobile Software Development] serg635:
12aon, Please, help me. I can`t decompilled file from manila 2.1 "53cc1e4f_manila",

if you can do this - help me please.

View attachment 291480
[Windows Mobile Software Development] 12aon:
Hey man, I am currently on a trip in the USA and I do not have the means to help you decompile at the moment. If you want it decompiled right away you can check out stupy's threads and tutorials (I have links in my first post) but I warn you this is kinda hard, good luck, 12
[Windows Mobile Software Development] serg635:
Ok, I will wait )))), and when you will be able to do this?
[Windows Mobile Software Development] muttim86:
Thanks, really useful that you did! ;)
[Windows Mobile Software Development] Co0kieMonster:
Man, this is seriously awesome :D

Extremely helpful tool, thank you very much :)
[Touch Diamond2, Pure Themes and Apps] ivanwaikit:
hi bros,

i need some help bros,

i can't connect/receive emails without wifi, when i just use 3G only, it said synchronizing error,

also when i try to use msn messager via 3G but fail too

must use WIFI.........??

do anyone have any ideal?
[Touch Diamond, MDA Compact IV ROM Development] blutz:
here is an issue I've seen posted in various 6.5 Rom threads here, but no strict solution given, and searching for an answer is a bit messy, so i think it deserves its own thread.

the scenario is that few days / hours after running newly flashed 6.5 rom, your device get clogged, and after a soft reset the device is back on First Boot screen, wiping off all the data and sometimes making the device unusable till next hard reset.. needless to say that apparently this is not a hardware issue, because original diamond roms run flawlessly.

please share your experience on this thread, and suggested solutions if any

thanks
[Touch Diamond, MDA Compact IV ROM Development] xvx45:
You must read all the information on this forum. This problem occur since 2.03 base cooked ROM, so before to flash a coocked ROM you have the choice to :

- use "task 29" in mtty before to flash

- flash a stock 2.03 ROM before flash coocked ROM.