Related
I'm having a problem I can't seem to figure out. I'm trying to create a Custom Extended Rom for my Qtek 9000. So far this has only worked once for me. Every other time it will be installing one of the cabs and the progress bar will get to the end and it will just stick there.
I've recreated the ms_.nbf several times, tried different cab orders, tried different cabs. As I do a different build it usually give me a different cab it get's stuck on but the end result is always the same it gets stuck installing one of the cabs and never completes.
One thing that really drives me nutz is on my SD card I have the cab for showing the extended. If I do a softreset once it is stuck, run that, and then access the extended rom I can run all the cabs in the extended rom just fine without getting stuck at all.
Well, it's definately something that is occurring for me only once I have modified the Extended ROM image. I just toock the stock ms_.nbf and flashed that then did a hard reset, no problems installing.
Even adding only the smallest of cabs for me has caused the installs to fail. Strangely it is not necessarily failing on the install that was added as I have them at the end of the config and have even named them so they show last on the list of files in explorer.
And as I have said previously, every single one of these cabs install and run fine if done manually.
Further info:
Starting Rom - UNI_Qtek_WWE_11364_151_10300_Ship
File: ms_.nbf
Tools:
HTC64 Extended ROM Tool.exe
WinImage 8.0
MaUpgradeUt_noID.exe
Steps:
Use HTC64 to decode ms_.nbf which creates ms_.nba (naming to match other tools and guides)
open ms_.nba with winimage 8
add cab file
extract config.txt
open config.txt with notepad and add a line above LOCKisabled referrencing the new cab such as CAB: \Extended_ROM\MyCab.cab
save config
drag config to winimage, say yes to replace
save .nba file and exit winimage
use HTC64 to encode the .nba to .nbf using the original .prj file, saying yes to overwrite
use MaUpgradeUt_noID to write the extended rom to my Qtek 9000.
Perform the cold reset. Once system is up and running, perform a hard reset.
Watch the installs, note that it fails before ever getting to my file.
Come seeking help.
As a little further help in hoping some kind soul can give me a hand figuring out what is going on here is my latest config. The files are all files I got from the FTP here. This particular config in this order seems to stop at Default_Unsigned_Unhide_ExtendedROM.sa.cab. However, as I have said if I swap the order of files it will stop at a different spot. (Ex. I had UNI_BrowserPerformance.sa.CAB above Default_Signed_DisableSecurity.CAB and it stopped at Default_Signed_DisableSecurity.CAB). There have even been configurations where it will stop as soon as Signed_Version.sa.CAB even though I do not modifiy any part of the config above EnableDRM_Only.CAB.
LOCK:Enabled
CAB: \Extended_ROM\Signed_SSD_Shortcut_WWE.sa.CAB
CAB: \Extended_ROM\Signed_Version.sa.CAB
CAB: \Extended_ROM\CAB-Shortcut-BP-19Aug05.CAB
CAB: \Extended_ROM\Enable_VT_RTPlugin_0727_2_signed.CAB
CAB: \Extended_ROM\EnableDRM_Only.CAB
CAB: \Extended_ROM\Default_Signed_DisableSecurity.CAB
CAB: \Extended_ROM\Default_Unsigned_Unhide_ExtendedROM.sa.cab
CAB: \Extended_ROM\UNI_BrowserPerformance.sa.CAB
LOCKisabled
RST: Reset
Any insight, help, thoughts, etc that might get this working would be greatly appreciated.
Just to be clear I have no problem flashing any of the stock roms. Just myown home brew that fails.
Is there such thing available that would install a selection of cabs at the "click of a button".
Over my time here, I have managed to build a list of favourite applications, however whenever I reflash a new ROM on my device, I have to manually install these applications one by one.
I was wondering if there is some type of auto installer that would auto install a list of 'given' cab files by itself? (perhaps reading the list from an xml or a txt file), and if it required no user interaction, that'd be even better (well maybe it could ask one question, just once... "Install to Device or Storage Card?"
WizzKidd
yeah.. i would like to hav sthg like tat too...
it is very frustrating to install all the programmes after flashing different ROM...
if someone can make sthg like tat will b nice..
Yes there is! Try out Sashimi, you'll have to google for it, don't have it with me. It will install any CAB you throw at it plus it can also run xml files to configure things like email accounts, power settings, etc, etc. After flashing a new rom it takes me all of about 3 minutes to have everything I want installed and all my setting changed to how I want them.
crankshaft said:
Yes there is! Try out Sashimi, you'll have to google for it, don't have it with me. It will install any CAB you throw at it plus it can also run xml files to configure things like email accounts, power settings, etc, etc. After flashing a new rom it takes me all of about 3 minutes to have everything I want installed and all my setting changed to how I want them.
Click to expand...
Click to collapse
which version is that? only on their site it says that the HD will be supported in V8 but they only seem to be at V7.9
Scrap that V8 is out http://www.winmo-experts.com/viewtopic.php?f=7&t=4
I'll have to check that out. I was using 7.9. It aways gave an error about unsupported screen size but still worked fine!
Not sure why but the guy who developed it was banned from xda-dev I believe!
Any chance you can post the app here? Really can't be arsed to register on another site!!!
Cheers
Don't worry, just realised I'm already registered!
Hey, this is a nice app! I'll have to get that, seems great for fast setting up everything after flashing.
to everyone who uses sashimi:
im very interested in your regkeys you backup! maybe you can post your regexport.ini here so we all can see and use the useful regkeys for different programs and settings!
thanks!
Rozenthal said:
Hey, this is a nice app! I'll have to get that, seems great for fast setting up everything after flashing.
Click to expand...
Click to collapse
for that reason i have written my own "autorun" script which does the following:
install cabs
import provisioning files
import registry files
copy files
and could do lots of more...
this is how it works:
copy the script into a folder of your sd card, e.g. \Install. now copy
all cabs into \Install\Cab
all provisioning files into \Install\Xml
all registry files into \Install\Reg
all other files into \Install\Files
the script checks for files in a specific folder and executes the tasks required.
the script requires that mort script is installed. alternatively copy the mort script files (mortscript.exe, mortscript.dll, autorun.exe) into \Install so that you can immediately start with the autorun script after flashing or a hard reset (attention: in this case the name of autorun.mscr and autorun.exe have to be the same - do not rename the script file) . the script also needs a prog "taskmanager.exe" which is only required for importing xml and registry files. it does not do anything else (unless you intentionally run it)
mortscript is available here
task manager is available here
anyway, i have put together all files required in the zip file attached
here is AutoRun.mscr:
Code:
scriptpath = SystemPath("ScriptPath")
Call("InstallCabs")
Call("CopyFiles")
Call("ImportXML")
Call("ImportReg")
Message("Done. Press OK to Reset...", "AutoInstall")
Reset
Exit
Sub InstallCabs
ForEach file In Files(scriptpath \ "Cabs\*.*")
RunWait("\Windows\wceload.exe", """" & file & """ /nodelete /silent")
EndForEach
EndSub
Sub CopyFiles
XCopy(scriptpath \ "Files\*", "\", TRUE, TRUE)
EndSub
Sub ImportXML
ForEach file In Files(scriptpath \ "Xml\*.*")
RunWait(scriptpath \ "TaskMgr.exe", "/provxml " & file)
EndForEach
EndSub
Sub ImportReg
ForEach file In Files(scriptpath \ "Reg\*.*")
RunWait(scriptpath \ "TaskMgr.exe", file)
EndForEach
EndSub
but why dont you just use sashimi? it does the same plus some more things (email settings, wireless passwords,..)
Another vote for sashimi, my only dislike is the interface its shockingly bad. The window disappears for every menu option you go to!
output is version 8, the bug has been fixed, or you can use the modified version 7.9 for HD.
As you know how to save the settings for various programs to be able to restore automatically with sashimi?
you can automatically record programs that require activation key, how?
Most things can be done with the regexport.ini file in the program/ini folder.
You can define which registrykeys should be backed up. Most programs store there configuration and serial keys in the registry. So you just have to search for the right entry.
Here is my regexport.ini
Code:
[MySettings]
RegExportDirMode=Auto
key1=HKCU\Software\ageye\
key2=HKCU\Software\Conduits\
key3=HKCU\Software\FdcSoft\
key4=HKCU\Software\Ghisler\
key5=HKCU\Software\JBlend\
key6=HKLM\Software\FLIP\
key7=HKLM\Software\HTC\QuickGPS\
key8=HKLM\Software\Spb Software House\
key9=HKLM\Software\HTC\Manila\ProgramLauncher\
key10=HKCU\Software\HTCAddicts\cleanRAM\
key11=HKLM\Software\Microsoft\Bluetooth\A2DP\Settings\
key12=HKCU\Software\DaProfik\pRSSreader\
key13=HKLM\Software\HTC\HTCAlbum\Ignored\
egoist6 said:
for that reason i have written my own "autorun" script which does the following:
install cabs
import provisioning files
import registry files
copy files
and could do lots of more...
this is how it works:
copy the script into a folder of your sd card, e.g. \Install. now copy
all cabs into \Install\Cab
all provisioning files into \Install\Xml
all registry files into \Install\Reg
all other files into \Install\Files
the script checks for files in a specific folder and executes the tasks required.
the script requires that mort script is installed. alternatively copy the mort script files (mortscript.exe, mortscript.dll, autorun.exe) into \Install so that you can immediately start with the autorun script after flashing or a hard reset (attention: in this case the name of autorun.mscr and autorun.exe have to be the same - do not rename the script file) . the script also needs a prog "taskmanager.exe" which is only required for importing xml and registry files. it does not do anything else (unless you intentionally run it)
mortscript is available here
task manager is available here
anyway, i have put together all files required in the zip file attached
here is AutoRun.mscr:
Code:
scriptpath = SystemPath("ScriptPath")
Call("InstallCabs")
Call("CopyFiles")
Call("ImportXML")
Call("ImportReg")
Message("Done. Press OK to Reset...", "AutoInstall")
Reset
Exit
Sub InstallCabs
ForEach file In Files(scriptpath \ "Cabs\*.*")
RunWait("\Windows\wceload.exe", """" & file & """ /nodelete /silent")
EndForEach
EndSub
Sub CopyFiles
XCopy(scriptpath \ "Files\*", "\", TRUE, TRUE)
EndSub
Sub ImportXML
ForEach file In Files(scriptpath \ "Xml\*.*")
RunWait(scriptpath \ "TaskMgr.exe", "/provxml " & file)
EndForEach
EndSub
Sub ImportReg
ForEach file In Files(scriptpath \ "Reg\*.*")
RunWait(scriptpath \ "TaskMgr.exe", file)
EndForEach
EndSub
Click to expand...
Click to collapse
the script not working though I follow your intruction,what's wrong?
str0nz0 said:
Most things can be done with the regexport.ini file in the program/ini folder.
You can define which registrykeys should be backed up. Most programs store there configuration and serial keys in the registry. So you just have to search for the right entry.
Here is my regexport.ini
Code:
[MySettings]
RegExportDirMode=Auto
key1=HKCU\Software\ageye\
key2=HKCU\Software\Conduits\
key3=HKCU\Software\FdcSoft\
key4=HKCU\Software\Ghisler\
key5=HKCU\Software\JBlend\
key6=HKLM\Software\FLIP\
key7=HKLM\Software\HTC\QuickGPS\
key8=HKLM\Software\Spb Software House\
key9=HKLM\Software\HTC\Manila\ProgramLauncher\
key10=HKCU\Software\HTCAddicts\cleanRAM\
key11=HKLM\Software\Microsoft\Bluetooth\A2DP\Settings\
key12=HKCU\Software\DaProfik\pRSSreader\
key13=HKLM\Software\HTC\HTCAlbum\Ignored\
Click to expand...
Click to collapse
Thanks for your reply, I just solved a file.reg
Question
is possible to automatically with SAHIMI select the language for installation
resco explorer (multilingual) select /italiano / ok
resco audio explorer (multilingual) select /italiano / ok
is possible to automatically with SAHIMI select the answer is no when asked to reset to complete the installation of
SPB Wireles monitor select /no
SPB Phone Suite select /no
perhaps with a Mortscript running in tandem, I unfortunately do not have capable people who give me a hand?
Thanks for your reply, sorry my bad English
You can do that with the so called auto files.
it is explained in the manual of sashimi.
i have never tried it but it should work like you want.
str0nz0 said:
You can do that with the so called auto files.
it is explained in the manual of sashimi.
i have never tried it but it should work like you want.
Click to expand...
Click to collapse
unfortunately I do not know how to fill the auto file, could you please make some examples that help me understand
Thanks for the great help
ippoglosso said:
unfortunately I do not know how to fill the auto file, could you please make some examples that help me understand
Thanks for the great help
Click to expand...
Click to collapse
[AutoFile]
InstallLocation=0
WindowTitle="SpbPhoneSuite_it.arm.cab"
[ScriptCommands]
1=SendLeftSoft
2=
3=
4=
[AutoFile]
InstallLocation=0
WindowTitle="SpbWirelessMonitor3_it.arm.cab"
[ScriptCommands]
1=SendLeftSoft
2=
3=
4=
[AutoFile]
InstallLocation=0
WindowTitle="audiorec_p.arm.cab"
[ScriptCommands]
1=SendLeftSoft
2=
3=
4=
[AutoFile]
InstallLocation=0
WindowTitle="rescoexplorer_p.ARM.cab"
[ScriptCommands]
1=SendLeftSoft
2=
3=
4=
I do not know the commands
If you are using a UC capable rom (like miri 6.5) you can make a "SDconfig.txt" and it will install whatever cabs you want as part of the first install process at the windows installing screen.
UC Thread for more info.
SPB BackUp 2.0.2. Clean, simple, fast, easy.
Install once all that You want, make backup (is .exe).
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
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 KitchenDecompiling Manila OEM Files ............ 4
LUA Editing
Mode9 Editing
General Editing
Updating 'm9editor.names.txt'
Updating the RepositoryWorking with Manila Files ............... 5
Initializing the KitchenRecompiling Manila OEM Files ............ 6
RecompilationTesting the Manila OEM File Changes ..... 7
Installer .CAB Method
Direct to Device MethodReference Web Links ..................... 8
Frequently Asked Questions (FAQ) ........ 9
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.
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.
Working with Manila Files
Once the HTC Manila OEM files have been decompiled, changes may be made as required. The Manila Kitchen provides a single work area for Manila file editing; this is:
Workspace
Workspace
This workspace contains all of the decompiled Mode9 files, graphics, and other Non-LUA files that are typically manipulated using the M9Editor, Notepad2, and/or CFC_GUI.
Workspace\_lua
This area of the workspace contains all of the decompiled LUA files. Use a standard UTF-8 compatible editor such as Notepad2 to make changes to the files.
LUA Editing
Files that have failed to decompile during the initial decompilation process typically need to be manually edited so as to address the cause of the failure. Editable *.lua Manila files reside in the .\Workspace\_lua folder and may be change with a text editor such as Notepad2.
Once the Manila file has been fixed, initiate the the LUA Comparison (luatool.exe) tool to validate that the changes made to the file are correct.
The LUA Comparison process will compare the changes made to the decompiled Manila file against the original Manila file. If successful, the Manila file will be moved from the .\Incomplete or .\Error folder to the
.\Completed folder.
The following procedure will initiate the comparison process.
► To initiate Manila file comparison
At the prompt, type the following command: manilatool.cmd -cmp
Press ENTER.
Mode9 Editing (Mode 9, Graphics, PNG)
M9Editor is a tool for editing Manila files; nearly all aspects of a Mode9 LUA file can be viewed, changed, and saved. Mode 9 LUA Manila files are stored in the .\Workspace\Mode 9 folder and are changed with from within the M9Editor.
Additionally, the M9Editor tool provides graphics import/export capabilities as well as Chainfire File Compression (CFC) support. Lastly, the M9Editor tool includes a folder (directory) viewer which displays information specific to Manila files.
Although it is possible to decompile Manila files with the M9Editor tool, the current version (3.0.03) utilizes a deprecated version of the LUA Decompiler (luadec.exe) which is not supported by this Manila Kitchen.
► To initiate the M9Editor tool
Navigate to the Manila Kitchen folder.
Double-click the M9Editor shortcut.
General Editing (InternetPortal, Manilapages, QTC, PNG, SQLite, TTF, XML)
Some of the Manila files found in the .\Workspace folder may also be changed by other tools such as Notepad2 and CFC_GUI.
► To use an other tool to edit certain Manila files
Launch the desired tool (ex: Notepad2, CFC_GUI, etc.)
Select the Open file option from within the tool.
Navigate to the .\Workspace folder.
Select the Manila file to change.
Updating 'm9editor.names.txt'
From time to time, HTC adds new Manila files or updates the names of existing ones. To update the M9Editor Reference Index file, initiate the Manila name scan process using the MANILATOOL command script. The Manila Name Finder (mnf.exe) tool will iterate through the HTC Manila OEM files found in the .\_SOURCE folder and obtain the new names.
Updating the m9editor.names.txt reference index file ensures that the M9Editor tool is able to display the friendly Manila file name making it easier to work with Manila files - instead of the compiled Hash name used by HTC. Currently, there are two versions of Manila reference index names; one for pre-Manila 2.5 and one for post-Manila 2.5.
The Manila name scan process supports the following Manila versions: 2.5, 2.2, 2.1, 2.0, 1.3, 1.2, 1.1, and 1.0. Specifying a Manila version other than 2.5 will initiate the Manila Name Finder (mnf.exe) tool in pre-Manila 2.5 scan mode. The MANILATOOL command script determines which scan mode to use by first querying the 'kitchen-ver' file - if the value is 0.0; the mode specified in the command parameter is utilized.
Use one of the following procedures to initiate the appropriate M9Editor reference index update process.
► To initiate a pre-Manila 2.5 reference index update
At the prompt, type the following command: manilatool.cmd -mnf:2.1
Press ENTER.
► To initiate a Manila 2.5 reference index update
At the prompt, type the following command: manilatool.cmd -mnf:2.5
Press ENTER.
Updating the Repository
Updating the .\Repository folder ensures that a recent backup copy is available in the event that a change to *.lua must be reversed. During the repository update, decompiled *.lua files found in the .\Workspace\_lua folder are copied to the .\Repository\_lua and a hierarchy (by unhashed names) is created in the .\Repository\windows folder.
The .\Repository\windows folder hierachy displays shortcut links to the Manila files that correspond to a Manila feature. For example, navigate the hierarchy and double-click the shortcut link that corresponds to the file that requires modification - the appropriate tool will be launched.
The following procedure will initiate the repository update process.
► To initiate a repository update
At the prompt, type the following command: manilatool.cmd -lib
Press ENTER.
Frequently Asked Questions (FAQ)
What types of files can be placed in the '.\_SOURCE' folder?
Any type of file may be placed in the .\_SOURCE folder. The MANILATOOL command script will only copy files that contain the word "manila" in them to the .\_queue folder.
I accidentally specified the wrong version of Manila files during the kitchen initialization; is there a way to change it without initializing the kitchen again?
The default Manila file version is stored in the kitchen-ver file. Use a standard text editor such as Notepad2 to edit file. The file must contain a three characters equivalent to the version - valid versions are: 2.5, 2.2, 2.1, 2.0, 1.3, 1.2, 1.1, 1.0, and 0.0 (Unknown/Custom)
What is the '._BACKUP' folder used for?
Before most operations occur, a backup of files that will be changed or removed from/in a given folder is performed. This ensures that previous functional files remain available in the event that a "rollback" is required.
What is the difference between the "Incomplete", "Error", and "Completed" (successful) LUA folders?
Manila files that are successfully decompiled are will appear in the "completed" folder - 100% comparison result. Manila files that are decompiled but do not pass the comparison validation (less than 100%) are placed in the "incomplete" folder. Manila files that report a 0% decompilation result are placed in the "error" folder.
What is the difference between the files in the '.\Release\_lua', '.\Release\_error', '.\Release\CAB', and '.\Release\DEVICE' folders?
The .\Release_error folder will only appear when unexpected errors were encountered during Manila LUA file recompilation. The folder will contain logs detailing the problem that was encountered with a Manila LUA file. The folder is removed and recreated at each recompilation.
The .\Release\_lua folder contains the recompiled versions of the Manila LUA files that are found in the .\Workspace\_lua folder. These are the files can be distributed directly to a device or via CAB file.
The .\Release\CAB folder contains the recompiled versions of the files found in the .\Release\_lua folder. These are the files can be installed via ActiveSync or a Storage Card.
The .\Release\DEVICE folder contains the recompiled versions of the files found in the .\Release\_lua folder. These are the files can be installed via ActiveSync or a Storage Card.
What is the difference between the files in the '.\Processed', '.\Workspace', and '.\Repository' folders?
The .\Processed folder contains the HTC OEM Manila files that were copied to the .\_queue during the Manila Kitchen initialization process. During the decompilation process, the files are moved from the .\_queue folder to the appropriate folder - which is determined by the LUA Comparison tool results.
The .\Workspace\_lua folder contains decompiled versions of the HTC OEM Manila files - these are the files that are typically modified and recompiled. The remainder of the folders in the .\Workspace folder contain various non-LUA files.
The .\Repository\_lua folder contains a duplicate copy of the decompiled Manila files. The repository serves a form of backup.
What are the extra .TXT files that appear in the partially decompiled LUA script folders?
The *.error.txt file contains the STDOUT error that was generated by the LUA Decompiler. When this file appears, there is a logical error in there script, which makes it impossible to run the script. The file will usually contain the approximate (line number) location where the problem was encountered.
The *.log.txt file contains the compared disassembly output from the orignal Manila file and the decompiled LUA version - which appears in the folder. When this file appears, it is an indication that the script will function but it does not match the original Manila file.
The *.dis.txt file contains the raw (full) disassembly of the original Manila file and may be used to resolve the decompilation issue.
The *.status.txt file contains the decompilation result - 0% to 100%.
Visit the following website to obtain more information in troubleshooting a failed decompilation:
http://winmo.sztupy.hu
Is the disassembly output always correct?
Yes. Even though the some of the events may be not be displayed in the disassembly output, the correct sequence of events will be provided.
The M9Editor tool provides a built-in decompiler, why not just use that?
The internal LUA Decompiler (luadec.exe) provided with the M9Editor tool is an earlier version. This internal version does not provide the extra files required to resolved decompilation errors.
The M9Editor should be used when editing Mode9 files and attach extracted embedded LUA script back to their original Mode9 files.
There are strange errors such as '.\documents and settings\<profilename>\eee' errors, what is the solution? (Only in older versions)
One of the Manila Kitchen tools is in an unknown state or temporary files are locked and cannot be freed. Note the path location of the .\eee folder, restart the workstation, and manually delete the folder, sub-folders, and files.
An error message is displayed when attempting to delete a file or folder, what is the solution?
A running process is preventing the file or folder from being removed. Restart the workstation and manually delete the file or folder.
Can Error Reporting be disabled so as to not have to click the Close button every time the LUA Decompiler and/or LUA Comparison tool generate an application error?(Only in older versions)
As previously noted, some Manila files cause the LUA Decompiler (luadec.exe) and/or LUA Comparison (compare.exe) tool to generate an application error. Visit the following website(s) for more information on how to suppress the Error Reporting message box.
Windows XP
http://www.windowsnetworking.com/articles_tutorials/Disable-Error-Reporting-Windows-XP-Server-2003.html
Windows Vista/Seven
http://thehiddenguide.com/how-to-disable-error-reporting-in-windows-vista
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.
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.
Reference Web Links
Manila 3D Kitchen
http://winmo.sztupy.hu/manilakitchen.html
http://forum.xda-developers.com/showthread.php?t=487331
Manila Tutorial
http://forum.xda-developers.com/showthread.php?t=399212
LUA Decompiler
http://forum.xda-developers.com/showthread.php?t=568281
LUA 5.1 Decompiler
http://winmo.sztupy.hu/luadec.html
http://forum.xda-developers.com/member.php?u=1433290
http://forum.xda-developers.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://forum.xda-developers.com/showthread.php?t=464984
MNF - Manila Name Finder
http://forum.xda-developers.com/showthread.php?t=546820
CFC - The Manila/TF3D Image Editor
http://forum.xda-developers.com/showthread.php?t=437777
TouchFLO/Manila/SenseUI
http://forum.xda-developers.com/group.php?groupid=131
Co0kie's Beta Testing and Development
http://forum.xda-developers.com/group.php?groupid=192
Max Sense Testers
http://forum.xda-developers.com/group.php?groupid=185
GT7 Sense 2.1 Theme Beta Testers
http://forum.xda-developers.com/group.php?groupid=202
Leaked Full EXT/Manila 2.5 Packages-latest official sprint tp2
http://forum.xda-developers.com/showthread.php?t=642817
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
Very nice work as always 12
Very nice work on this, I am around now, So I can start to help out more, haha
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
kinnyfaifai said:
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
Click to expand...
Click to collapse
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
12aon said:
That's whats up!
@MRFERRARI23
What I think that going wrong with you is that your files are not called xxxxxxxx_manila make sure they are name that way or the cab creation script won't recognize them.
One other thing I noticed is that the path to the kitchen contains names with spaces like "mr vizziato". This can throw the kitchen off. To test this put the kitchen directly in you C:\ folder or in any rate not in the folder with spaces in in their names, and check back with me, 12
Click to expand...
Click to collapse
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
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 53cc1e4f_manila.zip
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
12aon said:
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
Click to expand...
Click to collapse
Ok, I will wait )))), and when you will be able to do this?
Thanks, really useful that you did!
Man, this is seriously awesome
Extremely helpful tool, thank you very much
Hello xda-developers
I'm not really sure if it's already mentioned here on the forums, but today I found out that provxml-files which where written as .rgu and translated by "rgu-2-xml" don't work for Windows Phone 7. The output file is saved as ANSI file. After updating to Mango I tried a "Developer Unlock.xml" file but it didn't work. Well, all the procedure back and again but now with a UNICODE file After right-clicking the (ANSI) xml-file, "edit" and re-saving it as UNICODE file I noticed that the size of the file increased I tried the provxml-Method again and it worked! Not sure if I'm the only one with this solution and like I already said: not sure if it's already said here Please let me know if it helped you
you unlock your device on Mango build?
hd2leo_fusion said:
you unlock your device on Mango build?
Click to expand...
Click to collapse
The provxml method works on Mango as well.
Yes, I unlocked Mango But for me there are still some unanswered questions about provxml =/ Does a provxml file only work once on Omnia 7?
experience7 said:
Yes, I unlocked Mango But for me there are still some unanswered questions about provxml =/ Does a provxml file only work once on Omnia 7?
Click to expand...
Click to collapse
Ηow you will run provxml on omnia ...
I was under the impression that provxm works only with htc connection setup ...
And yes after the appl (connection setup) finish the 1rst run its deleting the provxml file.
You can also use it on Samsung devices Here is the thread where I found it: http://forum.xda-developers.com/showthread.php?t=1152422
Yes, with Connection Setup on HTC it will be deleted - but what about the GPRS Manager used for Samsung devices? After executing a command (xml-file) in the GPRS Manager, it's still there ^^ Even if I restart the app or the whole phone -> After opening the GPRS Manager again, all the entries seem to stay there
EDIT: Okay, tested it again and it seems like you can apply the xml's as often as you want with GPRS Manager I flashed a older ROM so my phone was on 7004 again I unlocked using ChevronWP7 and installed WP7 root tools. I created a file which switches the Internet Explorer's search provider to Google Well, after execution I first opened IE9, pressed search and yup.. google.com came up - then, just to be sure I opened WP7 root tools and took a look at the SearchScopes in registry. They were changed to Google, so the xml really worked. Then I manually wrote everything back to default. I opened the Internet Explorer, pressed the search button and Bing came up.. so everything's like before. I applied the "Google Search.xml" again and.. yes, it worked: Same effect like above: Registry was changed, IE9 search is now google.com
Well so at the end I can say that this is really useful for switches like in my example. I created several switches like "Enable instant resuming.xml", "Disable instant resuming.xml", "Enable lockscreen never option.xml", "Use Bing (default) search.xml", "Use Google search.xml", ... Wow, Mango with fast resuming apps is wonderful!
experience7
All of my rgu's that I've converted using xboxmods tool rgu2xml have worked just fine on my hd7.
It does kinda suck that HTC connection setup deletes the provxml everytime
Sent from my HD7 using XDA Windows Phone 7 App
Hm.. yes, maybe on HTC (with HTC connection setup) it's enough to convert them. On my Omnia 7 i had to open the provxml files, and resave them as UNICODE ".xml" files It's nice that GPRS Manager on Samsung devices doesn't delete the .xml files
Thank you for this! I was wondering why Connection Setup-applied ProvXML wasn't working. This will hopefully do it.
I've come up with a way to chain provxml files. I don't yet know if it works - it depends on how the deletion after processing the CustClear file is implemented - but it has the potential to allow you to store a "working copy" ProvXML file in My Documents as a txt file (which you can open and edit with Word), and then every time you use Connection Setup, it copies your "working copy" file to \Windows, renaming it as it does. This should make further modifications easier; just copy the XML from a website or app, paste it into Word, and run Connection Setup twice (once to copy your edited file, once to process it).
If it works, I'll post the file.
OK, I couldn't get the chaining to work. It's still in the file, just commented out, in case anybody else wants to experiment.
Oh, and I added some very convenient (if you deal with things like I do all day) registry tweaks. Open .LOG files as though they were .txt (great for attachments) and add an expansion for the , key similar to the one that the . key has.
THis really help me, That's the reason why my unlock.xml didn't worked in 7712 back then. I thought it was the 7712.
minori_aoi said:
THis really help me, That's the reason why my unlock.xml didn't worked in 7712 back then. I thought it was the 7712.
Click to expand...
Click to collapse
I'm trying to keep my HD7 unlock after updating to 7712 but the many times I tried, the Connection Setup will not run after 7712 update. If you can share the file and method with steps you used, that would be appreciated.
I don't know why your HTC connection setup didn't start after the update But maybe you did something wrong.. Okay, let's go through the steps together
Well, for Samsung devices you need a .xml file (GPRS connection manager handles with .xml files).
And on your HD7 you need an .provxml file (HTC connection setup handles with .provxml files).
Okay, first step is to be developer unlocked on NoDo - I think you are, right? [If you want to test it: Just try to sideload an app. If it works your phone is unlocked.. else it's not.]
Now uninstall HTC connection setup and install it again. Do not sideload any app found in the internet - just install the official app from the marketplace.
The next step is to get the right .provxml file. You don't need to do the following steps: I've already attached one which works. But just that you can follow me: Basically the file has to apply the following changes:
1) Developer unlock
Code:
[HKEY_LOCAL_MACHINE\Comm\Security\LVMod]
"DeveloperUnlockState"=dword:1
2) Prevent from relock
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\DeviceReg]
"PortalUrlProd"=""
"PortalUrlInt"=""
3) Maximum sideloaded apps
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\DeviceReg\Install]
"MaxUnsignedApp"=dword:7fffffff
And to create a this file we need to open Notepad:
Code:
REGEDIT4
[HKEY_LOCAL_MACHINE\Comm\Security\LVMod]
"DeveloperUnlockState"=dword:1
[HKEY_LOCAL_MACHINE\Software\Microsoft\DeviceReg]
"PortalUrlProd"=""
"PortalUrlInt"=""
[HKEY_LOCAL_MACHINE\Software\Microsoft\DeviceReg\Install]
"MaxUnsignedApp"=dword:7fffffff
Simply save this file as a .rgu file.
Then you need the tool "rgu-2-xml.exe" which converts the .rgu to a .provxml file. I've also attached this tool.
Okay, the generated file has now to be in the "Windows" directory of your phone. You can use the "WP7 mass storage" trick to get the file to your device - just search here on xda-developers. After you've copied the file to your device it will be stored in "\My Documents\Zune\Content\0400\...". Now you need a file explorer for HD7. I'm not sure if you're already using a tool but TouchXplorer should do the job. Open your tool on the phone and navigate to the folder above. There should be several folders.. just browse through them and look for a file which has got a short name and another file ending as our file (CustClear.provxml). Check the file size - it has to be the same on PC and your phone. If it's the same file rename it to "CustClear.provxml" again. Then move the file to the "Windows" folder on your HD7. The file has got the right name and is on the right place.. let's go on:
Now don't start the HTC connection setup!
Be sure to update to the highest build available at the moment. It's Mango v7720. There are tutorials here on xda-developers.com on how to update to v7720 Run HTC connection setup only if you can see that your phone is running v7720. You can see this under settings > about > more information.
Then you should be developer unlocked and sideloading apps should work again.
If anyone finds a mistake in those instructions please tell me! Thanks
And please tell me if it worked
Thanks for this but I don't need it now as as I had solved my problem.
After 7403 update, I uninstalled Connection Setup and re-installed again.
Nonetheless, I will PDF your instructions and download the 3 files to try out and learn this. Thank you very much for providing the detailed instructions. I'm sure it might be useful for some others.
experience7 said:
I don't know why your HTC connection setup didn't start after the update But maybe you did something wrong.. Okay, let's go through the steps together
Well, for Samsung devices you need a .xml file (GPRS connection manager handles with .xml files).
And on your HD7 you need an .provxml file (HTC connection setup handles with .provxml files).
Okay, first step is to be developer unlocked on NoDo - I think you are, right? [If you want to test it: Just try to sideload an app. If it works your phone is unlocked.. else it's not.]
Now uninstall HTC connection setup and install it again. Do not sideload any app found in the internet - just install the official app from the marketplace.
The next step is to get the right .provxml file. You don't need to do the following steps: I've already attached one which works. But just that you can follow me: Basically the file has to apply the following changes:
1) Developer unlock
Code:
[HKEY_LOCAL_MACHINE\Comm\Security\LVMod]
"DeveloperUnlockState"=dword:1
2) Prevent from relock
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\DeviceReg]
"PortalUrlProd"=""
"PortalUrlInt"=""
3) Maximum sideloaded apps
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\DeviceReg\Install]
"MaxUnsignedApp"=dword:7fffffff
And to create a this file we need to open Notepad:
Code:
REGEDIT4
[HKEY_LOCAL_MACHINE\Comm\Security\LVMod]
"DeveloperUnlockState"=dword:1
[HKEY_LOCAL_MACHINE\Software\Microsoft\DeviceReg]
"PortalUrlProd"=""
"PortalUrlInt"=""
[HKEY_LOCAL_MACHINE\Software\Microsoft\DeviceReg\Install]
"MaxUnsignedApp"=dword:7fffffff
Simply save this file as a .rgu file.
Then you need the tool "rgu-2-xml.exe" which converts the .rgu to a .provxml file. I've also attached this tool.
Okay, the generated file has now to be in the "Windows" directory of your phone. You can use the "WP7 mass storage" trick to get the file to your device - just search here on xda-developers. After you've copied the file to your device it will be stored in "\My Documents\Zune\Content\0400\...". Now you need a file explorer for HD7. I'm not sure if you're already using a tool but TouchXplorer should do the job. Open your tool on the phone and navigate to the folder above. There should be several folders.. just browse through them and look for a file which has got a short name and another file ending as our file (CustClear.provxml). Check the file size - it has to be the same on PC and your phone. If it's the same file rename it to "CustClear.provxml" again. Then move the file to the "Windows" folder on your HD7. The file has got the right name and is on the right place.. let's go on:
Now don't start the HTC connection setup!
Be sure to update to the highest build available at the moment. It's Mango v7720. There are tutorials here on xda-developers.com on how to update to v7720 Run HTC connection setup only if you can see that your phone is running v7720. You can see this under settings > about > more information.
Then you should be developer unlocked and sideloading apps should work again.
If anyone finds a mistake in those instructions please tell me! Thanks
And please tell me if it worked
Click to expand...
Click to collapse
Is it possible to enable a custom notification sound via a reg edit in the omnia 7 running 7720 chevron unlocked? Maybe someone can make a prov file and instructions...
Well, maybe it's possible but I'm not really sure what you mean But I'm aware of provxml's capabilities, how to build them and how to set up the phone, so maybe I can help you
Thanks... I read somewhere that with a registry key we can change the path of the notification sound... This way we dont need to overwrite the original .wav... I believe this might be the only way to do it in mango since homebrew is blocked...
Need to check the registry key thread for this one, since i dont really know much about this...
Dehydration Hack
I have used this method to unlock and remove the side load limit on my HD7 and it works great. I am unsure how to create a file to turn the dehydration hack on and then off again after I have updated all the way to 7720. I used the HTC Connection setup once I fully updated, I have touch explorer I just have no clue what to do for the dehydration can anybody help me?
On HTC devices you can't create a simple switch to enable / disable the dehydration hack because once you've ran the HTC connection setup the provxml files will be deleted. But if you don't want to switch that often between on / off you can use this tool:
http://forum.xda-developers.com/showthread.php?t=907971
You'll have to create two .rgu files:
First one contains this:
Code:
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Microsoft\TaskHost]
"DehydrateOnPause"=dword:0
Second one contains this:
Code:
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Microsoft\TaskHost]
"DehydrateOnPause"=dword:3
Then you have to convert them to .provxml files. Put the first one in a folder called "Enable dehydration hack" and the second one into a folder called "Disable dehydration hack". This way you can't mess it up
Then use the tool mentioned above to deploy the .provxml which contains the setting you want to have on your phone - then finally run the HTC connection setup
For example you've enabled the dehydration: To disable it again you have to put the CustClear.provxml from "Disable dehydration hack" into the XAP file from xboxmod and deploy this XAP to your device. Then run HTC connection setup again and the changes will be applied - Dehydration hack will be turned off
Please tell me if it worked for you / helped you,
experience7
experience7 said:
On HTC devices you can't create a simple switch to enable / disable the dehydration hack because once you've ran the HTC connection setup the provxml files will be deleted. But if you don't want to switch that often between on / off you can use this tool:
http://forum.xda-developers.com/showthread.php?t=907971
You'll have to create two .rgu files:
First one contains this:
Code:
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Microsoft\TaskHost]
"DehydrateOnPause"=dword:0
Second one contains this:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\TaskHost]
"DehydrateOnPause"=dword:3
Then you have to convert them to .provxml files. Put the first one in a folder called "Enable dehydration hack" and the second one into a folder called "Disable dehydration hack". This way you can't mess it up
Then use the tool mentioned above to deploy the .provxml which contains the setting you want to have on your phone - then finally run the HTC connection setup
For example you've enabled the dehydration: To disable it again you have to put the CustClear.provxml from "Disable dehydration hack" into the XAP file from xboxmod and deploy this XAP to your device. Then run HTC connection setup again and the changes will be applied - Dehydration hack will be turned off
Please tell me if it worked for you / helped you,
experience7
Click to expand...
Click to collapse
Should be
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\TaskHost]
"DehydrateOnPause"=dword:0
There is simple, but usefull tool, able to launch any application, script, or other shell directive, by own tile icon tapping.
Using:
1. Rename UniLaunch7.xap to YourOwnName.zip
2. Edit zipped WMAppManifest.xml file:
- replace all occurences of string "UniLaunch7" by "YourOwnName"
- replace line "\Windows\calc7.exe" by your wanted exe, batch, or Mortscript full filepath (see my other threads about console and Mortscript).
3. If you want, replace ApplicationIcon.png by your own icon picture.
4. Repack zip and rename YourOwnName.zip to YourOwnName.xap
5. Deploy it to device
Notes:
Using batch with LaunUri.exe calling you can simply make any "undocumented" system CPL shortcut as internet sharing (LaunchUri app://5B04B775-356B-4AA0-AAF8-6491FFEA5629/_default), GPS enabling (LaunchUri app://5b04b775-356b-4aa0-aaf8-6491ffea5642/_default) etc. Examples are in attached zip (enable scripting first by HaRET Console 7 or another batch interpreter enabling tool e.g. PocketCMD7 registered to batch as cmd /C CALL "%1"
).
Using batch with registry changing you can make simply native installator or profile changer. For example simple scripts RingingOffVibrateOn.bat, RingingOffVibrateOff.bat and RingingOnVibrateOn.bat is tiled in my device.
You can see differences between UniLaunch7.xap and KeyboardCPL.xap (unzip booth) to understand tutorial. First one launches Calcullator, second launches Keyboard CLP.
I will prepare authomatical on-device launchers creator, probably as feature of Phone Commander.
More information on the benefits and advantages.
Or do explained in video