User To User Tips, Tricks ideas and issues thread.
XDA_UC is a silent User & Cook automation script.
It requires no user configuration (unless you count dripping stuff into a folder as configuring).
It differs opposed to the default Autorun & RunCC configuration that, as a user you do not need no make an SDConfig.txt file on your SD card.
And that you can start using your device immediately.
It will run in the background at the reboot the Cook has chosen to have it run.
But it adds a lot of extra tweaking functionality for hardcore Tweakers to.
What it basically does is install the beneath on the user side
My.tsk file from "\Storage Card\XDA_UC"
and if not present Cook.tsk from Windows Folder.
Copy Over User Files.
Check for "\Storage Card\XDA_UC\Copy2Root" if present, Disable Manila from Homescreen then Copy files from "\Storage Card\XDA_UC\Copy2Root" to the root of the device, Then checking for existence of wallpaper_TF3D.png or wallpaper_TF3D.jpg in "\Storage Card\XDA_UC\Copy2Root\Windows" and adding that to
[HKCU\Software\HTC\Manila]
"HomeBackgroundPath"="\\Windows\\wallpaper_TF3D.jpg"
Import registry files from "\Storage Card\XDA_UC\Copy2Root\Windows\manila.reg" If present
Re-enable Manila on Homescreen and redraw it. Now also works for the Sense 2.1 and up versions.
.xdas files in "\Storage Card\XDA_UC"
Silently run Legacy SDConfig.txt from Storage Card
(If your using RunCC.exe or Autorun you do not need to point to or use SDAutorun.exe or SDConfig.txt) Thanks to RoryB
Commands for SDConfig.txt can be found here....
.cab files in "\Storage Card\XDA_UC"
.cab files in "\Storage Card\XDA_UC\Storage", These cab files will be tempted to install to Storage Location.
.cab files in "\Storage Card\XDA_UC\Manual",These cab files will start with Full User interaction capabilities to choose where to install to.
.reg files in "\Storage Card\XDA_UC"
.xml files in "\Storage Card\XDA_UC"
.mscr files in "\Storage Card\XDA_UC"
.cer files in "\Storage Card\XDA_UC"
Create Shortcuts and more from Registry Keys
More information here....
Copy over welcomehead.192.01.png & welcomehead.192.02.png present in "\Storage Card\XDA_UC\Copy2Root\Windows" to the Windows folder.
Copy over welcomehead.96.01.png & welcomehead.96.02.png present in "\Storage Card\XDA_UC\Copy2Root\Windows" to the Windows folder.
Actually everything is copied over from Copy2Root folder to root, but the above Splashcreens get their file atributes removed before this happens.
Add native support for .mscr, .mortrun, .xda, xdai, xdas & .xdaz files
This thread is meant for user to user help and advice and sharing of tricks and tweaks.
Cooks should go to http://forum.xda-developers.com/showthread.php?p=3954547 for more information about the cooking side.
I have attached a Mort Script HTML Manual for those looking into learn about this type of scripting.
Before you consider buying me a beer. Please consider Donating to XDA to help out with the maintenance of the forum and get cool stars next to your Nickname showing your appreciation. Then there are always the people that without their apps this wouldn't have been possible at all that you can consider showing some love. Mort, DotFred & Sleuth255 All of whom made Apps Seemingly simple But oh so useful for the whole XDA and PocketPC community.
Hopefully A List of Cooked Roms with XDA_UC Pretty Soon.
Give me holler,
Or my main Homie Moderator Ameet.
Or you can ask your Favourite Cook to look into this and incorporate it into his or her rom
A Lot of Energy Rom's
www.energyrom.com
ELF/IN
AHEN E6f
ETEN Glofiish M700
ahmedfikry wm6.5 23089 light rom
Kaiser
jjblaster3
Raphael
Noonski's Secret Nightly Rom, Simpel Pro Classic (deuh)
Rhodium / Touch Pro 2
Juicy R0 @ PPCGeeks
Bikeandestroy Rom
DavidMMorley's v1.5.3 @ PPCGeeks
Bhar'S 21891_V2/23540_V2
*7ppc* for TP2
Rhodium / Touch Pro 2 CDMA
xpressyourcell's XpressDusk @PPCGeeks
xpressyourcell's XYC GTX @PPCGeeks
Samsung Omnia
Rock and Republic WM6.5 ROM @ XDA
Rock and Republic WM6.5 ROM @ PPCGeeks
Storm's ROM [CF03] @ Modaco
MrCapcom's i910 6.5 Custom Rom CF03 Edition
TechMaster7545 WM 6.5 CF03 Rom Build 23009 For I910
FloTanium ROM
Sony Xperia X1
WM6.5 для X1 Rumanian
Topaz
EPS Creme RC2 DE
RTT Topaz Peak, RTT Topaz Peak @ XDA,
Touch Dual
DJ Series
Touch Cruise 2 / Iolite
Serfer222's Iolite WM6.1 (build 21055)
Serfer222's Iolite, WM65, Russian, XDA_UC (Official Russian Mega ROM ported to Iolite)
Serfer222's Kitchen + Iolite WM6.1 (build 21055) WWE
HD / Blackstone
BiCh0n's ROM (french)
Touch HD2/Leo
Merlion NG Leo v1.30's Merlion NG Leo v1.30
RTT Shock Star RTM GER
BiCh0n's ROM (french)
Trinity/P3600
nAr & Icke WM6.5[WWE][FRA][DEU]
NoseDive's n083 P3600+i
Common Good Practices
Do Not Reboot untill The XDA UC Message tells you it's finished.
You do not need to make your .cab files read only. But out of safety of loosing them it is recommended.
Save your .reg files as Unicode, always start your .reg file with
Windows Registry Editor Version 5.00
In the first line. And leave one blank empty line at the end of the .reg file.
Test your tweaks and files instead of reflashing to many times. A self initiated script will be uploaded soon, so you can test on a device.
Save your .xml files as Unicode and check if they are correctly formatted by opening them for instance in Internet Explorer.
If it doesn't show you the content then it will tell you where to look for mistakes.
More XML tips
Commands for SDConfig.txt for Version 2.0
AutoShortcut Registry Tricks
AutoShortcut Registry Tricks
HTC Autoshortcut replacment and enhancements through registry keys:
Directory Copy
Copy over files from one folder to another, overwriting the present files.
This will also copy over any subfolders inside the folder being copied over.
The entry on the left is the destination folder, the entry on the right is the source folder.
See the example code below:
Code:
[HKEY_LOCAL_MACHINE\Software\XDA\DirCopy]
"\\My Documents\\Test"="\\Storage Card\\My Documents\\Test"
You can also use this registry entry if you just want to make an empty folder.
See the example code below:
Code:
[HKEY_LOCAL_MACHINE\Software\XDA\DirCopy]
"\\My Documents\\Test"="MakeDir"
FileCopy
Copy just one file over from one folder to another.
The entry on the left is the destination File, the entry on the right is the source file.
See the example code below:
Code:
[HKEY_LOCAL_MACHINE\Software\XDA\FileCopy]
"\\My Documents\\MakeDir.reg"="\\Storage Card\\XDA_UC\\MakeDir.reg"
Delete
Delete a file. This will not delete Files in cooked in Rom/Windows folder.
But it will for instance delete Read Only Pictures in My Documents
See the example code below:
Code:
[HKEY_LOCAL_MACHINE\Software\XDA\Write]
"\\Documents And Settings\\Somefile.xml"=""
Deleting of a whole directory has not been added as mistakes can be made to easily, resulting in a complete Device and SD card whipe.
If you understand the risks I reccomend to learn writing your own mortscripts to do this.
Write
Write more explicit shortcuts or files
The left entry is the destination file, the right entry is the text you want written into the destination file.
See the example codes below:
Code:
[HKEY_LOCAL_MACHINE\Software\XDA\Write]
"\\Windows\\Start Menu\\Programs\\Tools\\TF Detacher\\icon.lnk"="50#MPI_ProgramIcons.dll,-115"
[HKEY_LOCAL_MACHINE\Software\XDA\Write]
"\\My Documents\\Somefile.txt"="Hello World"
Auto Shortcut Creation
To create shortcuts to files or applications.
The left entry is the target link name, the right entry is the source file the link should be pointing to.
See the example code below:
Code:
[HKEY_LOCAL_MACHINE\Software\XDA\AutoShortCut]
"\\Windows\\Start Menu\\Programs\\SAP Settings.lnk"="\\Windows\\SAPSettings.exe"
If you want to be sure that the destination directory exists where you want the shortcut created you can add an extra Registry entry for Directory creation.
See the example code below:
Code:
[HKEY_LOCAL_MACHINE\Software\XDA\DirCopy]
"\\Windows\\Start Menu\\Programs\\Contacts"="MakeDir"
[HKEY_LOCAL_MACHINE\Software\XDA\AutoShortCut]
"\\Windows\\Start Menu\\Programs\\Contacts\\SAP Settings.lnk"="\\Windows\\SAPSettings.exe"
Run First Boot
Run a file or application at the first boot.
The left entry if for the file or application, the right entry is for paramaters you want passed to an application.
See the example code below:
Code:
[HKEY_LOCAL_MACHINE\Software\XDA\RunFirstBoot]
"\\Windows\\btdwake.exe"=""
SDConfig.txt Commands
Commands that will work in SDConfig.txt
Be aware that for commands with only three letters there needs to be a space between the : & \
XML: \Storage Card\Cabs\Personal.xml
XML: \Storage Card\Cabs\Personal.provxml
(To parse provisioning .xml or .provxml files Saved to ANSI)
REG: \Storage Card\Cabs\G-Alarm.reg
(To parse registry files in Windows Registry Editor Version 5.00 format)
CPY1:\Storage Card\Cabs\pim.vol
CPY2:\pim.vol
(To copy over one file, and if pim.vol is found in Cabs folder, Cprog.exe will be shut down first)
MOV1:\Storage Card\Folder
MOV2:\Windows\Folder
(Aplied to latest Beta's, but this will copy over folders and it's subfolders overwriting any existing files)
SC1: \Storage Card\Program Files\GoogleMaps\GoogleMaps.exe
SC2: \Windows\Start Menu\Programs\Google Maps.lnk
(Simple Shortcut creation)
WR1: \A File.txt
WR2: The Text That Goes Into the File
WR1: \Windows\Start Menu\Programs\Tools\Another App.lnk
WR2: 99#"\Windows\SuperApplication.exe"?AnotherAppWithIcons.exe,-IDI_APPICON
Yes for the Advanced Users. It removes Files Attributes from possible target file then deletes it before writing a new one.
Note that there needs to be a space before the written text starts! (Special NoPrize for the one that knows which file was originally under "AnotherAppWithIcons.exe")
CER: \Storage Card\Cabs\Work.cer
(Install certificates)
CAB: \Storage Card\Cabs\098MSN.CAB
(Cabs that can be installed silently without user intervention)
SCAB:\Storage Card\Cabs\098MSN.CAB
(Cabs that you want installed to Storage Card)
MCAB:\Storage Card\Cabs\098MSN.CAB
(Cabs that you want installed with full user interaction)
EXEC:\Storage Card\Cabs\something.exe
EXEC:\Storage Card\Cabs\mortscript.mscr
EXEC:\Storage Card\Cabs\Or A Link.lnk
EXEC:\Storage Card\Cabs\Or A Even a document.doc (consider this to be a regular Open or Run file as long as the file is known by system but that can be set be doing a .reg first with the file open registry settings)
KILL:AutoVer.exe
(to close running open apps, be aware there is no Slash needed)
DEL: \My Documents\Picture\leaf.jpg
(Remove read write permissions then try to remove the file, will of course not work on ROM/Windows files)
TSK: \My Cool Theme.tsk
Apply Theme
RESET
Will set the Reset flag to force reset at the end of XDA_UC
Questions & Answers
Question:: I am a new user of Windows Mobile and I don't understand many of the terms here, can you tell me in a simple language what exactly XDA_UC is doing for me or for my device?
Answer: XDA_UC aplies and installs installation files and user tweak files in a simple and straight forward manner that does not lock up your screen as the regular Autorun method's would with out the need to know how to configure a pre setup SDConfig.txt file. It runs in the background and you can start using the device after flash (thought you will be a little slower at start uas stuff is happening in the background)
Or if above is still not easy to understand, let's say like this: After you flashed a new ROM, or did a hard reset (or you run 'Clear Storage' from system settings page, it's same as so-called 'hard reset' here), all your programs and your tweaks or adjustment to the Operation System is wiped out and you only have a clean OS from the firmware on your phone. At this time, XDA_UC will silently install all your programs and apply all your tweaks alltogether in a straight-forward way, and you don't need to install or apply them one by one. Provided onlyif you already placed the (cab installer & registry tweak) files in the designated folder.
Question::I noticed the advantage of XDA_UC. But as a newbie to this society, seems I can not take full advantage of it. Any simple guidelines about what shall I learn and where to start?
Answer: The best way is to start learning which Registry settings you want personally always to be aplied to any rom. Look for CeRegEditor 4.3 so you can study, dump and compare the regitry to find the specific Registry keys that you can then save as .reg files. Installing cabs is nice and takes away a lot of hassle put adding your own. It's also smart to just make a shortcut to a specific program you already have installed on your SD as most work fine onze they have been installed before. That should save time on installing some cabs.
Question:: I have some Greenware in my storage card, every time after flashing a new ROM or a hard-reset, I need to make shortcuts for them inside \Windows\Start Menu\, Can XDA-UC do that for me?
Answer: You can either add a registry String line to any .reg file you put into the XDA_UC Folder
[HKEY_LOCAL_MACHINE\\Software\\XDA\\AutoShortCut]
"\\Windows\\Start Menu\\Programs\\Synchro Time.lnk"="\\Storage Card\\Program Files\\Synchro Time\\Synchro Time.exe"
And XDAUC will at the end of process convert all these registry settings to real shortcuts.
Or make a mortscript with the line:
CreateShortcut(SystemPath("ProgramsMenu") \ "Synchro Time.lnk","\Windows\Synchro Time.exe")
Question: What if I want to run XDA-UC by myself? Is it possible? Since what time to run (on first boot. second boot, or which boot after hard-reset) is decided by the cook of my ROM.
Answer: A Script will be provided soon for this, but it won't install if files that have already been installed at the XDA_UC run at the first boot.
Almost everything that get's installed by XDA_UC is written to the registry so if someone has the time to develop a managing tool can read this values.
Coming soon...
Is this something that can be installed/added to an existing rom that I can use stand alone, or does it have to be cooked into a rom? Thanks.
In principle this is supposed to be a cooked in thing, but Once i have tested the V 1.0.02 fully, and tweaked the timing a bit i might make a trimmed down "Run Whenever you like version or add to a SDAutorun Only Rom"
But it the adding to SDConfig.txt will need some testing, that if no one else is doing i will need to test first someday.
Noonski said:
In principle this is supposed to be a cooked in thing, but Once i have tested the V 1.0.02 fully, and tweaked the timing a bit i might make a trimmed down "Run Whenever you like version or add to a SDAutorun Only Rom"
Click to expand...
Click to collapse
OK, thanks for the reply. I will keep monitoring this thread to see how you're doing. I'm thinking this is a good way to update after a flash, but I'm not sure if I want to change roms right now. Also, not too many roms have it cooked in just yet.
Is this to install to main memory only?
If not, how do we differentiate which cabs we want in main memory and which in storage card?
I'm testing the next version which will recognize the Cab's in an extra Folder "SD" inside of XDA_UC.
Cab's placed there will open with full user interaction, so you can choose the location of where to install.
And it already has a silent, and at least 40% more effective method then a cabfile, of installing whatever to where ever you want.
I will also in time, unless someone beats me to the punch, an example .xdas file, to which you can add, your own .xml, .reg, files & folders and an silent.mscr to.
You can add a lot to that, and do whatever you want, if your willing to say goodbey to cabs that is.
Noonski said:
I'm testing the next version which will recognize the Cab's in an extra Folder "SD" inside of XDA_UC.
Cab's placed there will open with full user interaction, so you can choose the location of where to install.
And it already has a silent, and at least 40% more effective method then a cabfile, of installing whatever to where ever you want.
Click to expand...
Click to collapse
What happens if your cab is NOT successfully installed? Is there an error trap of some sort or does the program just stop or crash?
Noonski said:
I'm testing the next version which will recognize the Cab's in an extra Folder "SD" inside of XDA_UC.
Cab's placed there will open with full user interaction, so you can choose the location of where to install.
And it already has a silent, and at least 40% more effective method then a cabfile, of installing whatever to where ever you want.
I will also in time, unless someone beats me to the punch, an example .xdas file, to which you can add, your own .xml, .reg, files & folders and an silent.mscr to.
You can add a lot to that, and do whatever you want, if your willing to say goodbey to cabs that is.
Click to expand...
Click to collapse
Yes we need a really functional, powerful and flexible XDA_UC. But it may be a challege to balance this:
For advanced users -> They can do whatever they want to do with the UC, and it's wonderful.
For common users -> They can use the basic functions of it without complex learning process, and later on they just will find more and more supprise out of it.
For this purppose maybe a readme file somewhere is also good additive.
dmcnado said:
What happens if your cab is NOT successfully installed? Is there an error trap of some sort or does the program just stop or crash?
Click to expand...
Click to collapse
Good Question, I'm going to fing a cab that doesn't want to install first
But it should not install and there is no error trap besides that the cab will not show up on the installed programs in the control panel.
After that it contiunues.
wg5566 said:
Yes we need a really functional, powerful and flexible XDA_UC. But it may be a challege to balance this:
For advanced users -> They can do whatever they want to do with the UC, and it's wonderful.
For common users -> They can use the basic functions of it without complex learning process, and later on they just will find more and more supprise out of it.
For this purppose maybe a readme file somewhere is also good additive.
Click to expand...
Click to collapse
That is the intention. With a growing amount of users not that into tweaking, i feel the urge to draw them in and start learning and then contributing.
Noonski said:
That is the intention. With a growing amount of users not that into tweaking, i feel the urge to draw them in and start learning and then contributing.
Click to expand...
Click to collapse
Vow, wondering what if M$ heard of this. Some big guy is inspirating everybody to hack their OS!
Joking. Thanks for everybody' efforts to push forward the development of WM system. I am one of those that inspired by this sociaty and just joined the team.
But basically I still keep the business way of thinking about some great apps or better methods. That is, some details and some promotion (marketing term) is always needed before it get reachable to every user and widely spreaded. I think I can contribute more on this aspect.
Edit: I added two more questions on post#4. Anybody can answer please answer.
Did my best to answer these.
And i updated the info in post 1 to reflect the updates in V 1.0.02
I added something to your answer, but still not feel satisfied. Please just keep editing it. What we need is just like an explanation you made on the Rapheal ROM thread.
Another thing is the title of these two thread (sorry I keep commenting on these off-topic issues):
[UC]XDA_UC V1.0.02, Automated & Silent User & Cook, Configuration Service[12/07/09]
&
[UC]XDA_UC Autoconfiguration User To User Thread[23-06-2009]
Maybe I'm a little slow, but I takes me more than 5 seconds to (not completely) figure it out what is this talking about after first glance at the title, and then decide to take a look inside.
And then look at another big guy Menneisyys's thread title:
Sticky: Another revolutionary utility by me: add "find in page" support to most web browsers!
It is completely different effect on grasp reader's notices. And that makes difference on spreading speed.
Just comment, no matter is you insist to keep Noonski style.
wg5566 said:
Another thing is the title of these two thread (sorry I keep commenting on these off-topic issues):
[UC]XDA_UC V1.0.02, Automated & Silent User & Cook, Configuration Service[12/07/09]
&
[UC]XDA_UC Autoconfiguration User To User Thread[23-06-2009]
Maybe I'm a little slow, but I takes me more than 5 seconds to (not completely) figure it out what is this talking about after first glance at the title, and then decide to take a look inside.
And then look at another big guy Menneisyys's thread title:
Sticky: Another revolutionary utility by me: add "find in page" support to most web browsers!
It is completely different effect on grasp reader's notices. And that makes difference on spreading speed.
Just comment, no matter is you insist to keep Noonski style.
Click to expand...
Click to collapse
Is that really important? In my opinion the answer is no.
Noonski! Thank you for your Great work on this, i have included this in my rom and with Blazing Wolfs help got it up and running with no issues, except one.
Whenever i set XDA_UC to start of first initial flash it kills my modem i have to manuly pick the network the my phone uses to connect to the internet. IF i make XDA_UC start after a reboot it works perfect, I have tried to look at all The MSRC files and cant see to put my finger on the issue!!! Thanks in advance!!!
Related
So, you wanna cook a rom but don't know where to start??? Is the Raphael Kitchen & PPCKitchen to complicated? Are you only interested in changing a few graphics, or removing programs from a rom that you don't use?
Well, then this thread is for you. This info is also good for chefs with existing builds that want to make quick changes to OEM packages & keep their rom up to date with the latest apps & packages.
Firstly, I need everyone to say a big thank you to Bepe, Tolstoy at PPCGeeks, Bot, Kyphur, Oli, Pof, Cmonex, & a big thank you to qsqa!!!
This lite kitchen will allow you to make changes easily to all stock roms & even to cooked roms, if your chef is kind & confident enough to create a version that includes all of the rgu & dsm files. Have a paticular rom you like & only wish to change a few items? Ask your favorite chef to get with the spirit of XDA-Developers & to create an easybake compliant rom! Just like qsqa did!!!
I will also be releasing a rom, light & very empty for all of you wishing to have a rom that is suited best for the person that has to use it, YOU!
I will be including guides, tools, suggestions, roms & all the things necesarry to create your very own customized rom, both easily & based on a good solid stable build.
This is an easy five step process that allows you to make any unprotected rom your own & the tools & methods have been only slightly adapted by me from a nice guide prepared by Tolstoy aimed at CDMA devices.
First Things First - Preparing for your easybake experience!
Download the attached Raph_Blank_Kitchen at the bottom of post #1 or from here: http://rapidshare.com/files/174704051/RAPH_blank_kitchen.rar Uncompress/extract the Raph_Blank_Kitchen to your C: drive.
Find & download any OEM shipped/extracted or easybake compliant unprotected rom such as that I will release shortly, or from qsqa, i.e. PROven 1.08
After Extracting your new Raph Easybake Kitchen you will find a folder in C: named Raph_Blank_Kitchen. Within this directory you will find several more folders:
1: OEMizer - a tool to help you create oem packages, registry tweaks or provisioning xml's.
2: RUU - This folder is the output folder where you will find your rom completed & ready for flashing after an easy 5-step baking process.
3: Tools - This folder contains everything you need to cook a rom, change the page pool, etc...
Within the root directory, you will also find the following files/programs:
1: PrepIt.bat - This script deconstructs any Rom, seperating it into OEM, SYS, & ROM folders, placing the modules & files in their appropriate place for cooking. After running Prepit.bat you will see 3 new folders inside your kitchen, OEM, ROM & SYS.
A. OEM - This is the directory in the kitchen that you will copy your OEM packages into to add programs to your rom. You can also delete packages included by other easybake friendly roms.
B.SYS - This is the similar to the OEM in that you can delete packages from the donor rom, changing packages here will require the use of G'Reloc & possibly RebuildDSM or BuildDSM. Deletion of packages however is easy.
C: ROM - You won't do anything with this folder at this point in your chefdom, but this is where the OS & XIP meet.
2: G'Reloc.exe - This will relocate modules that you have altered.
3: BuildOS.exe - This builds the operating system portion. It combines the OEM's and System files.
4: BuildIt.bat - This script builds your rom. It will Package everything together and copies your new rom to the RUU directory.
Now you got it all set up!!! So, How easy is it???
Try 5 easy steps!!!
Yep!!! Five steps to your own cleaner customized rom:
1- PrepIt.bat
2- Add/Remove OEM Packages/Tweaks/Files
3- BuildOS
4- BuildIt.bat
5- Flash your newly customized Rom
Other important info:
So, now you have extracted the Kitchen to the C: drive, copied the base rom (.NBH file)
Step Details:
Step #1: Deconstructing your base rom
Run PrepIt.bat - Just double click on the file named PrepIt.bat, or run it from the CMD Prompt. This will again seperate the nb content from the nbh, split the nb content into the IMGFS & XIP Content, & Dump the Imgfs into the appropriate SYS or OEM Folder. This step also renames your donor rom to Input.nbh.
Step #2: Adding or Removing OEM & SYS Packages
Addng programs, registry tweaks, or provisioning xml's is as easy as copying the oem package into the OEM folder. Nothing to it! Oem packages can be made or downloaded from numerous sources.
ADD PROGRAMS- simply drag your OEM from the right PPCGEEKS_OEM directory and drop it into the c:\kitchen\OEM folder
Removing Items can be a little bit tricky. Use common sense here. Look for packages named after whatever you want removed & delete them. Most anything in an OEM folder can be removed with little consequence, some thing in the SYS folder you don't want to mess with though. Take a look, look for the name of what you want gone & if its a simple program like Total Commander for instance, just delete the appropriate folder & it will be gone.
Step #3: BuildOS.exe
Just click the BuildOS.exe BuildOS will then build a new OS while adding/removing the OEM packages that you either added or deleted in step two. Clicking BuildOS.exe will bring up a new window, That is the BuildOS program. In the window you should see most of the OEMS that you added. Make sure you check mark the OEM Packages that you have added. Once you are sure you have selected all the programs you want added to the rom, click that green arrow in the upper left of the window. This will create the OS. You will see the green progress bar to the bottom right.
BuildOS will say DONE in the bottom status area when complete.
There are a few things that can go wrong, but the most common is duplicate packages. Make sure your not adding a duplicate package to the rom & you should be okay.
Step #4: BuildIt.bat
This step will go thru the process of reconstructing the newly moddified rom back into the .nb & then the .nbh flashable format. If all went well, you'll have a new RUU_Signed.nbh in the RUU folder directory.
Step #5: Flash your new ROM
In the RUU folder you will find your new rom & the tools needed to flash it. Just click the ROMUpdateUtility.exe & it will flash your new rom.
Changing the Pagepool...
Now that your rom is complete, you may want to change the pagepool. Again, I have included everything you need to accomplish this in the Tools folder.
Step 1: Open the XVI32 folder & launch xvi32. Open the newly created rom in the RUU folder named RUU_Signed.nbh or drag & drop it to the XVI32 folder. In XVI32, use the search function. Select the bubble that says "Hex" & search for this hex string: 03 15 A0 03 02 15 A0 13 00 10 82 E5
Change the last four numbers to 00 00 A0 E1
Then press F3 on your keyboard or search for the Hex string: 03 15 A0 03 02 15 A0 13 00 10 82 E5 once again & again change the last four digits to 00 00 A0 E1.
The page pool is now NOP & can be opened & set to whatever number you like using the pagepool changer I've included in the Tools folder.
Moddifying Graphics & Customizing Packages
Coming Soon!
Other Useful & Important Tools
There are several tools that make customizing roms fun, fast & best of all...FREE. Of course there are other tools that cost money that are recommended, but let's see what we can come up with as for suggestions of free or low cost software for customizing roms. Where available & as time permits I will upload all of the tools &/or give links to the developers website along with basic instructions for making their use easy & frustration free!
A few of the must haves are as follows:
1. CERegistryEditor - This is an amazing tool that allows you to make registry changes on your device via activesync, export registry setting, unlock your registry, etc... This tool will also work with all registry formats including .reg, .rgu & most importantly .hv registry hives can be edited directly. This tool is amazing & very powerful as it allows you to export values as .rgu files that can then bee made into registry tweak OEM packages with the already included OEMizer or made into provisioning xml's using the famed rgu2xml tool in conjucntion with the OEMizer.
Coming soon: Tips & examples on using this tool to create registry & provxml packages.
2. EditPad Lite - EditPad Lite is a free version of EditPad Pro & is simply the BEST free text editor around period. EditPad will allow you to directly read & modify many important file such as initflash.dat. This allows you to remove or add things to your rom such as Folders, Start Menu items, etc... You can also use it to modify .rgu files, .reg files, .lnk shorcuts & many more.
Coming soon: Tips & examples on using this tool to modify many things in your rom.
3. Gimp - This is an amazing & most importantly free, graphic editing tool that handles numerous image file types. This can be used to edit, modify or change images to suit your own tastes. Items such as Dialer & Dial Pad Graphics & colors can easily be modified with gimp. Icons & folder icons, such as .ico files can also be edited allowing you to customize your folder icons when used in cojunction with PEexplorer, Gconvert, or Resource Tuner. Simply put, Gimp is a necesarry tool of great value when it comes to modifying or even creating new or existing graphics & images.
Coming soon: Tips & examples on using this tool to modify many things in your rom. Including an overview of some of the greatest & most overlooked features included in this tool.
Okay last one
EasyBake Compliant ROM's & Chefs!!!
1: PROven 1.0x by qsqa
2: M-ROM 1.1 by merten3000
3: Semilite or v2final by Aruppenthal
4: G3 Lite & Ultralight - Coming Soon!
Come on Elite Team!!! Other Chef's! Get with the spirit of XDA & let's see what happens when we are all free to expand on others breakthroughs!!!
Wow, I just start using it, want to modify qsqa rom LOL Thank You!
By the way I'm using win vista, hope everything of the kitchen work with it.
Again Thank You!
I think this deserves to be sticky. At least for the time being
ahh this program basically ensures me spending more time messing with my phone =]
thanks for your hard work!
Is this working with Vista 64-bit?
im running vista 64 and it works perfectly fine
just be sure to run as admin
beautiful tutorial,. congratulations and thank you GSLEON,.
hchavarria said:
Is this working with Vista 64-bit?
Click to expand...
Click to collapse
sure,.
When you have all needed files installed, it should work,.
any idea if this will work for tilt roms as well?
sdale said:
any idea if this will work for tilt roms as well?
Click to expand...
Click to collapse
The kitchen would need some modification to work on the tilt I believe. GSleon3 could say for sure. I will take a look at it if i get a chance.
BTW great work on this GSleon3
what a useless thread...... unsticky this please!!!!!!
LMAO JK gsleon..... Great job on this bud!!!
This Cooking device [kitchen] will not work with the new [ROM][DUTCH][28-12-2008] M-Rom v1.3 (XIP/SYS build 20931) 'unprotected' from merten3000.
Thanks for this thread and info. I want to begin cooking ROMs and was not sure where to start but now I do.
I would like to use the latest AT&T ROM for my build. How can one make it unprotected so it can be used in your kitchen?
I have the Sprint version of the HTC Touch and I would like to start cooking my own ROMs but I am having a hard time finding the Base ROM to Start cooking, (the ???.nbh file). If someone could guide me as to where I can get one of these file I would appreciate it. Is this something I can pull from my phone and if so what is the name of the file. Thanks
2009-08-25 UPDATE: It has been brought to my attention that sending MMS does not work. Fix is written ... See attachments. Just extract the EXE from dj13241_MMS_Fix.zip, copy to device and run. No message will be displayed, but MMS should work. This fix should work for ANY carrier.
2009-08-17 UPDATE: MSVC_Announce_Fix_v0.3 Released. See this thread.
2009-08-03 UPDATE: Version 1.3 Released. Changes: Removed "Microsoft VoIP" (seemed to be causing issues) and Adobe Flash (slow) packages
2009-07-31 UPDATE: Version 1.2 Released. Changes: Added "Microsoft VoIP" and "no2chem_nueTools_nueCPL-Kernel" packages to USER_OEM
2009-07-17 UPDATE: Version 1.0 (originally posted) has a bug. My BuildInitFlashFiles.exe put HEX FF FE at the beginning of the file (just like notepad). It is now corrected, and the download link has been redirected to version 1.1. I have also attached the correct BuildInitFlashFiles.exe in a zip.
Some packages copied from PPCKitchen.org.
Some links goto dcd1182.n715dp.com (dcd's file site).
Thank you to nosedive for his radio power off help.
Please post any bugs/issues you may find. Also, please let me know if everything is working properly. Thanks in advance.
ANY ROM BUILT WITH THIS KITCHEN REQUIRES:
-RADIO VERSION 3.35 OR NEWER. I use 3.42.30. GPS does not seem to work with 3.42.50!!!
-HardSPL. I use nueSPL ... Requires SD card for flash.
DOWNLOAD THE KITCHEN HERE! (v1.3)
Known Issues:
-Data connection settings need to be manually entered (I think this is corrected by installing carrier CAB)
-ArcSoft MMS application not included. Install from CAB. Can be installed manually or via SD Autorun (see below). DCD Carrier CAB must be installed first.
-A DCD Carrier CAB is required for proper functionality.
-Voice Command does not announce caller ID info properly "out of the box" ... I wrote a little app to correct this (MSVC_Announce_Fix ... See this thread). I have this installed from SD Autorun.
-Comm Manager button shortcut is not correct. It will work until you go to Start->Settings->Buttons and click ok; after that you will get an invalid shortcut error. I have a CAB to correct this ... See post #9.
What makes this kitchen different then any other? As is (no user modifications), once flashed, the OS starts up with the radio off! I did this to make flashing and restoring a cleaner process. I use SBP Backup for my backups. PPCPimBackup can also be used, but it does not backup/restore MMS messages.
The cooked ROM will have SD Autorun. I have created a folder and SDConfig.txt on my storage card to install all of the software I want from CAB files on first boot. I am going to write an application to build an SDConfig.txt ... More details later. SD Autorun also runs my SPB restore process (manual intervention required to complete restore). SDConfig can NOT run (EXEC) from the storage card. I wrote a small launcher that can be used to run an EXE from the storage card (WM_BackupLauncher.exe ... needs to be cooked into ROM ... Currently in USER_OEM package dj13241_settings_basic ... This program will run ONE specified in "\Storage Card\WM_BackupLauncher.txt".).
Here is my full SD Autorun config and files. See ReadMe.txt in ZIP.
To build your own SDConfig.txt:
-Create a folder on your storage card for the CABs (I use SDConfig_Files)
-Copy all CABs to be auto-installed to this folder
-Create SDConfig.txt in the root storage card ... Should look like this:
Code:
LOCK:Enabled
CAB: \Storage Card\SDConfig_Files\MSVC_Announce_Fix_v0.1.cab
CAB: \Storage Card\SDConfig_Files\dcd xxx Carrier 20081031.cab [U][B][CHANGE OR REMOVE THIS LINE][/B][/U]
CAB: \Storage Card\SDConfig_Files\GC VZW Arcsoft MMS 5.0.70.24.cab
CAB: \Storage Card\SDConfig_Files\Any_Other_Cab.cab [U][B][CHANGE OR REMOVE THIS LINE][/B][/U]
HIDE:Enabled
EXEC:\Windows\WM_BackupLauncher.exe
HIDE:Disabled
LOCK:Disabled
RST: Reset
WM_BackupLauncher.exe will just exit if "\Storage Card\WM_BackupLauncher.txt" doesn't exist or the EXE referenced in the TXT file doesn't exist. If you wish to use the auto-restore functionality, create the file, and put the full path (without quotes) to the exe used to restore your backup.
SPB Backup WM_BackupLauncher Instructions:
-Copy your latest backup file to \Storage Card\SDConfig_Files\LatestBackup.exe
-Create \Storage Card\WM_BackupLauncher.txt with (no quotes):
"\Storage Card\SDConfig_Files\LatestBackup.exe"
-Follow normal restore procedure. I always click Customize Restore, uncheck System Data, click Next twice, click Options, check Force ROM upgrade mode, click Done, click Next, Select ROM Upgrade Mode on the dropdown, and uncheck Overwrite existing items, keep clicking Next until restore process starts.
PPCPimBackup WM_BackupLauncher Instructions:
-Copy PPCPimBackup.exe to \Storage Card\SDConfig_Files
-Create \Storage Card\WM_BackupLauncher.txt with (no quotes):
"\Storage Card\SDConfig_Files\PPCPimBackup.exe"
-Follow normal restore procedure
I am going to write a registry customization tool for stuff like ClearType, Owner Info, Email Accounts, Change Button Names/Functions, etc. for use before cooking ... More details later. For now, I have hard coded some registry updates in dj13241_settings_basic.
To build a ROM:
-Run 00_CleanKitchen.bat
-Add (or remove) any additional packages to the USER_OEM folder.
-Run 01_BuildOS.bat
-Check BuildLog.txt for registry errors. Search for "(RGUComp) done!" ... Indicates success
-Run 02_CreateROM.bat
Your new cooked ROM will be in a folder called "Cooked_ROMs". All build files will be named with WM OS Build (21042), AKU (1.6.1), and Date/Time Stamp. Most registry build errors are because of either a key that RGUCOMP doesn't like, or the RGU file is not setup properly.
To flash using RUU (USB):
-Copy the NBH file from the Cooked_ROMs folder to the RUU folder
-Run ROMUpdateUtility.exe
The whole process:
-Build a ROM
-Flash the ROM
-Allow "User Customizations" to execute (this is Autorun and SD Autorun)
-Restore backups (My SDConfig.txt takes care of this)
-Reset phone
-Turn radio on (Manually or add "EXEC:\Windows\PhoneRadioOn.exe" to SDConfig.txt before LOCKisabled and RST:Reset)
-Install DCD Carrier CAB (unless it has been added to SDConfig.txt)
-Install ArcSoft MMS CAB (unless it has been added to SDConfig.txt)
Done!
Reserved for future use
MODS - Can someone help me here ... Somehow, the title of this whole thread is attached to the title of this post. If I make the title of this post "Reserved for future use", then the whole thread is called "Reserved for future use".
Titan WM 6.1 Build 21042 Kitchen
Reserved for future use
I found a bug ... The word completion and auto-correct do not seem to work. I'll take a look at it. If anyone has any info on this, please let me know what to check.
Thanks.
DJ13241
How much free RAM on boot?
Will Windows Media Player play .3gp or .3g2 files in this build?
About 20MB free on boot ... Includes nueKernel (Start->Settings->Kernel) which allows you to re-boot the ROM without Camera drivers to allow for more free memory (about 25 MB free total).
Media Player does play 3GP files. I can't seem to find a 3G2 file (and don't feel like converting an existing video) ... Can you send me one (just reply and attach)?
Sure. Here is some crappy one I found on my phone. I had to zip it because I kept getting an "Invalid file type" message.
When turning phone back on I get
The file CommManager cannot be opened.
Rempala said:
When turning phone back on I get
The file CommManager cannot be opened.
Click to expand...
Click to collapse
It looks like I screwed up the shortcut for the comm manager. The problem starts after you goto Start->Settings->Buttons, and the comm manager item is missing from the selection box. This should only effect ROMs built with my version 1.3 and older kitchens ... It will be fixed in the 1.4 release (soon).
I put together a CAB file to install the "Comm Manager" shortcut into Start->Programs and then set the button to use the new shortcut (see attached).
unL33T said:
How much free RAM on boot?
Will Windows Media Player play .3gp or .3g2 files in this build?
Click to expand...
Click to collapse
Your 3g2 video played in Media Player with no problems.
Just to let you know, that fix did not work.
Edward
dj13241 said:
It looks like I screwed up the shortcut for the comm manager. The problem starts after you goto Start->Settings->Buttons, and the comm manager item is missing from the selection box. This should only effect ROMs built with my version 1.3 and older kitchens ... It will be fixed in the 1.4 release (soon).
I put together a CAB file to install the "Comm Manager" shortcut into Start->Programs and then set the button to use the new shortcut (see attached).
Click to expand...
Click to collapse
Rempala said:
Just to let you know, that fix did not work.
Edward
Click to expand...
Click to collapse
Is there a Comm Manager shortcut in Start->Programs after installing the CAB? If so, you can set the button to run Comm Manager.
PS - You can always browse to \Windows and execute WrlsMgr.exe
[XDA_UC][UC][SASHIMI][S4X] S4X_Auto & S4X_Backup [DEC.02.2010] XDA_UC Mods & Answers
* * * << PLEASE CHECK THE UPDATES/NOTES TOWARDS THE BOTTOM OF THIS POST >> * * *
Click to expand...
Click to collapse
If you need to know about Energy's version of XDA_UC, or are not familiar with it, but use his ROMs please CLICK HERE NOW!!!
Click to expand...
Click to collapse
I have done some extensive modding of the MortScript from SASHIMI (by bengilah @ www.winmo-experts.com) and XDA_UC (by Noonski here @XDA) and have come up with a couple additions meant mainly for Energy's custom XDA_UC as it lacks some of the features that Noonski's version does, well now you can have ALL THAT & MORE!
What does S4X_AutoLauncher.mscr do?
01. it loads the S4X_Auto Script (S4X_Auto_*version*.mscr) with an updated version of MortScript.exe (4.3b15) and waits for it to finish (this way you don't have to install new version of mortscript for the mod to work!).
S4X_Auto script does the following, in the following order:
01. shuts down sense, kills manila.exe and any processes found in the "autoKillApps" section of the autoSettings.ini.
02. deletes AppData folder from device, if instructed by autoSettings.ini to do so.
03. installs CERT files found in XDA_UC_\_Mod_\filesCERT (+ subfolders)
04. provisions any XML files that have "email" or "wifi" in the name of the file.
05. silently sets windows them from the autoSettings.ini, place the filename.tsk(only - spaces are OK, but NO path) of the theme in the INI like this:
Code:
[AutoSettings]
theme=filename.tsk
if it is a theme that is not present on the rom you can place the file in the folder XDA_UC\_Mod_\filesTSK, and it will get copied to windows before being set as the default theme. if no theme is set in the autoSettings.ini, then any TSK files present in XDA_UC\_Mod_\filesTSK will be copied to windows, then a dynamic menu with all available themes will be shown, and you can choose one, if none is chosen (10sec timeout), then the default cooked theme will be left as the default.
06. installs CABs, located in root of XDA_UC\_Mod_\filesCAB, silently to device
07. installs CABs, located in root of XDA_UC\_Mod_\filesCAB or any subfolder thereof (EXCEPT FOR \netCF, \Dialer, \SDAuto or \SKIP), silently to device.
08. if a SASHIMI ".auto" file is present, it will install the cab semi-silently (no user interaction required), to device or storage card (see XDA_UC\_Mod_\_bin\INI\sample-file.auto for example)
09. install a custom dialer if there are CABs present in XDA_UC\_Mod_\filesCAB\Dialer (+ subfolders), shuts down the proper processes first and if that isn't possible it will skip installation so that there are no errors.
10. installs netCF CABs silently to device if present in XDA_UC\_Mod_\filesCAB\netCF (+ subfolders) (uses THIS method. )
11. looks for CABs in folder: XDA_UC\_Mod_\filesCAB\SDAuto(+ subfolders), installs them silently to your SD. The cabs don't HAVE to be UC compatible, but you will have to do some manual things if they aren't UC compatible... NOTE: not all CABs work with this method, if they don't work, please place them in folder: XDA_UC\_Mod_\filesCAB\Manual, for full user interaction when necessary. This is no longer a separate script, I have integrated it. credit to bengilah @ winmo-experts.com
12. SKIPS all CABs located in XDA_UC\_Mod_\filesCAB\SKIP (+ subfolders)
13. installs *.XDA, *.XDAI, *.XDAS & *.XDAZ files found in XDA_UC\_Mod_\filesXDA (subfolders as well)
14. imports all reg files found in XDA_UC\_Mod_\filesREG (+ subfolders)
15. provisions XML files found in XDA_UC\_Mod_\filesXML (+ subfolders)
16. executes EXE files found in XDA_UC\_Mod_\filesEXE (+ subfolders), if a parameter(s) is found in exeparams.ini, then it is run with those parameters
17. looks for *.wgt/*.widget files in folder: XDA_UC\_Mod_\filesWGT, and installs them with wmwidgetInstaller.exe (if present in ROM) automatically (not silent, but usually no user input is required).
18. looks for folders under folder: XDA_UC\_Mod_\filesSense\****, and copies the content of each folder to \Windows, this is useful for keeping your fixes/mods seperated so that when a new rom comes out that includes the fix/mod you can just delete that folder and it won't be copied to device anymore during XDA_UC setup =)
19. copies all files/folders from folder: XDA_UC\_Mod_\filesRoot, to the root of the device IE: XDA_UC\_Mod_\filesRoot\My Documents gets copied to \My Documents...etc...
20. if present, executes deleteOps.ini and deletes files and/or folders, see the XDA_UC\_Mod_\_bin\INI folder for sample .ini's
21. if present *.pib file in XDA_UC\_Mod_\filesPIM, starts PIMBackup and waits until user is finished importing settings, then...
22. looks for PIM.VOL in folder: XDA_UC\_Mod_\filesPIM, renames current, copies backup, then places a self actuating and deleting script in \Windows\Startup that will delete the old renamed PIM.VOL file at the next boot.
23. runs any MSCR (MortScripts) found in XDA_UC\_Mod_\filesMSCR (+ subfolders), if parameters exist in scriptparams.ini, then it runs the script with the given parameters.
24. imports CHT settings file, if present in folder: XDA_UC\_Mod_\filesCHT
25. finally, I have added logging (no matter whether script is ran manually or automatically by XDA_UC) and on-screen notifications (only during initial XDA_UC setup), the log file can be found in folder: XDA_UC\_Mod_\_bin\LOG\S4X_Auto_ver#_LOG.txt
XX. For ALL CAB & Widget file installs, looks for an entry in customlinks.ini, if present moves the link to the specified directory in the start menu after installation is complete
Click to expand...
Click to collapse
What does S4X_SDAutoLauncher.mscr do?
01. It loads the sdauto script with an updated version of MortScript.exe (4.3b15) and waits for it to finish (this way you don't have to install new version of mortscript for it to work!).
S4X_SDAuto_1.0.mscr script does the following, in the following order:
01. files are installed alphanumerically: 0, 1, a, A
02. supports SASHIMI ".auto" files, to automate installation of non UC compliant CABs (ie: pop up messages/windows during installation)
03. it writes a log to XDA_UC\_Mod_\_bin\LOG\S4X_SDAuto_1.0_LOG.txt
Click to expand...
Click to collapse
What does S4X_Backup do?
I DID NOT WRITE (MOST OF) THIS CODE, I ONLY MODDED IT TO MAKE IT WORK THE WAY I WANTED/NEEDED IT TO!!!!
01. * Full minus file > customRegXport, PIMBackup & CHTBackup
02. * FullBackupXport > Filebackup.ini, Regexport.ini, PIMBackup & CHTBackup
03. * CustomRegXport > run regexport.ini ONLY
04. * PIMBackup > Backs up PIM data with PIMBackup, if a file already exists in XDA_UC\_Mod_\filesPIM folder, it copies the file(s) to folder: XDA_UC\_Mod_\_Manual\filesPIM
05. * CHTBackup > Backs up Co0kie Home Tab data and saves it as "chtsettings.cht" in folder: XDA_UC\_Mod_\filesCHT
06. * filebackup > runs filebackup.ini ONLY
07. * Full Export > full registry exported saved in folder: XDA_UC\_Mod_\_Manual\filesREG
08. * View Regexport.ini > Shows you the contents of regexport.ini
09. * View Filebackup.ini > Shows you the contents of filebackup.ini
10. * _ E X I T _ * > self explanatory ;-)
11. when doing a REG export I added a check of fileSkipOverOrArchive in autoSettings.ini (found in XDA_UC\_Mod_\_bin\INI), 0 = ARCHIVE, 1 = OVERWRITE, 2 = SKIP), if set to ARCHIVE a subfolder is created in XDA_UC\_Mod_\_Manual\filesREG and the files present in XDA_UC\_Mod_\filesREG are moved there before export starts. this way you have a backup of previous reg settings.
Please see post #3 for examples of filebackup.ini and regexport.ini
Click to expand...
Click to collapse
XDA_UC RELATED LINKS:
'Energy' ROM/XDA_UC - User to user tips and tricks!
[UC]XDA_UC Autoconfiguration User2User Thread[23-06-2009]
[UC]XDA_UC V2.RC1, Automated & Silent User & Cook, Configuration Service[14/05/10]
[APP][2010/07/07] XDA_UC_NET - new PORTABLE version of User Customization. (v0.6)
MORTSCRIPT RELATED LINKS:
MortScript Examples Accumulation
[MortScript] Source Compendium
SASHIMI RELATED LINKS:
[UC] User Customization Backup for Touch Pro using Sashimi
[07/08/2008] Sashimi Tips & Tricks
[REF] How-To: automate backup (inc. Manila conf) before a ROM upgrade using SASHIMI
SASHIMI and new 6.5.x roms
Click to expand...
Click to collapse
In an attempt to keep THIS post clean, I am not going to post the code from these two scripts. I will attach my XDA_UC_Mod [latest], which contains both of these scripts which you can extract from the zip and look at all you want.
I am going to post the contents of my filebackup.ini and regexport.ini's for reference, for you non-SASHIMI converts or SASHIMI users who never took the time to learn that wonderful part of SASHIMI. See posts #2 (autoSettings.ini) and #3 (filebackup.ini, regexport.ini, example ini's) for that info...
Future Plans:
1. a way to automate PIMBackup restore w/an .ini
2. completely modularize the mod and allow an .ini to set/determine what actions are performed, hopefully to make process slightly quicker as only script code needed will be loaded/executed
03. regKeyDelete.ini - to automatically delete some keys from registry [ie: bootloader and init entries...etc...] will be written much like the regexport.ini from sashimi
Instructions
If you only want functionality to install cabs to SDCard silently, then just download the S4X_SDAuto_Mod and extract the zip to the ROOT of XDA_UC folder, otherwise if you want the full mod download the S4X_Auto_plus_Backup_Mod and extract it to the ROOT of XDA_UC folder, there is no need for both as the S4X_SDAuto_Mod is included in the full mod.
1. choose file and unzip to ROOT of XDA_UC folder
2. if running EITHER mod manually, run the .mscr file in root of XDA_UC or .exe in the _bin folder, do NOT run the .mscr file in the XDA_UC\_Mod_\_bin folder unless you have a 4.3b11+ version of MortScript already installed on your system
3. to use S4X_Backup run S4X_Backup.exe in the XDA_UC\_Mod_\_bin folder of XDA_UC or from the start menu > tools > S4X_Backup (only present if you've used xda_uc setup with my mod)
--------------------------------------------
S4X_Auto & Backup Mod [Latest] - mediafire mirror
S4X_SDAuto Mod[Latest] - mediafire mirror
--------------------------------------------
EDIT 12/27/2010 ATTENTION: As I am currently unable to keep up with the updates at the moment, XDA user powinmo, is providing some code updates at THIS POST, please download the full package, then download his code update if you are a first time user. Otherwise you can just download his update, to fix the current issues. Changelog for his update is HERE.
Click to expand...
Click to collapse
autoSettings.ini
Here are some basic explanations of what the settings in autoSettings.ini do. =)
Code:
[AutoSettings]
[b][color="red"]If for some odd reason device shuts off, reboots...etc during setup/customization, if this is ON (1), it will retry the last task, if OFF (0) it will continue after the last attempted task.[/color][/b]
aggresiveResume=1
[b][color="red"]If set to ON (1), will automatically remove appData folder from device[/color][/b]
appDataDelete=1
[b][color="red"]this relates to the S4X_Backup mod, if set to 0 it will "ARCHIVE" (copy to _Mod_\_Manual\filesREG\ARCHIVE_[date]) any existing REG files before exporting the new ones to _Mod_\filesREG[/color][/b]
fileSkipOverOrArchive=0
[b][color="red"]if ON (1) will display the fullpath in status updates[/color][/b]
FullPathStatus=0
[b][color="red"]If set to 0, will use mortscript built-in process kill function first (default is 0), if set to 1, will use SKTools.exe #KILLPROC command line function first to try to kill the process. I highly recommend keeping it on 0, but if you have trouble with apps not getting killed (IE: for dialer cab install, PIMBackup restore...etc) then try changing this.[/color][/b]
killApp=0
[b][color="red"]If ON (1), will automatically reboot device after AutoSetup/Customization is complete[/color][/b]
RebootAfterAuto=0
[b][color="red"]if ON (1), the autoProgressFile will be deleted after setup/customization is complete, maybe good for debugging, so you can look at file if there are issues[/color][/b]
resetAutoFlag=0
[b][color="red"]when copying files, or deleting them, if ON (1) will remove all file attributes and set only "ARCHIVE" attrib[/color][/b]
ResetReadOnly=1
[b][color="red"]will set a reg entry, if the script is run via the "AUTORUN" feature, ie: using the 2577 folder found under _Mod_\_bin[/color][/b]
SetAutoRunFlag=1
[b][color="red"]If ON (1), will keep open a status message window, that will update with each completed/skipped/failed task... everything is always logged to _Mod_\_bin\LOG\*LOG.txt, so not necessary for debugging, only if you want visual confirmation while you watch it work...[/color][/b]
statusOn=1
[b][color="red"]this pertains to the TSKfiles portion of the script, you can use the filename of any theme located in \Windows or _Mod_\filesTSK, it will automatically be set during setup/customization[/color][/b]
theme=EnergyROM 2010.tsk
[b][color="red"]If ON (1) will use FdcSoft TskMgr.exe (located in _Mod_\_bin) to import REG files, default (0) will use SKTools.exe (also located in _bin folder)[/color][/b]
UseTaskMgrRegImport=0
[b][color="red"]below is a list of apps/processes that the script will attempt to kill during the "disable htc sense GUI" portion of the script. you can add any app/process you like, but be careful and only use the process name and extension, do not include the path[/color][/b]
[autoKillApps]
app01=manila.exe
app02=AudioManager_eng.exe
app03=AlbumSearcher.exe
app04=changescreen.exe
app05=gyrator2.exe
app06=quickmenu.exe
app07=repllog.exe
app08=sipgt_app.exe
app09=tmail.exe
filebackup.ini
- anything set to "Auto" will backup to _Mod_\filesRoot
- anything set to "Manual" will backup to _Mod_\_Manual\filesRoot
- so that it doesn't actually get copied to your device during the
- copy2root part of my script, you must do it manually.
Code:
[Appz_Config]
FileBackupDirMode=Auto
ArkSwitch=\Program Files\Arkswitch\Theme\config.xml
changeScreen=\Windows\changeScreen.config
ET9_1=\Windows\ET9*.Cdb
ET9_2=\Windows\ET9*.Rdb
Lumos=\Program Files\Lumos\settings.txt
[Gen_Filez_Backup]
FileBackupDirMode=Auto
ShakeSave=\ShakeAndSave\*.*
[Opera_9]
FileBackupDirMode=Auto
Bookmarks1=\Windows\Opera9\opera6.adr
Bookmarks2=\Windows\Opera9\Profile\opera6.adr
Cookies1=\Windows\Opera9\cookies4.dat
Cookies2=\Windows\Opera9\Profile\cookies4.dat
Secure=\Windows\Opera9\secure\wand.dat
Settings=\Windows\Opera9\opera.ini
Skin=\Windows\Opera9\Skin\*.*
[Opera_10]
FileBackupDirMode=Manual
cookies=\Program Files\Opera Mobile 10\profile\cookies4.dat
pass=\Program Files\Opera Mobile 10\profile\secure\wand.dat
prof1=\Program Files\Opera Mobile 10\profile\datastorage\*.*,*
prof2=\Program Files\Opera Mobile 10\profile\op*.dat
prof3=\Program Files\Opera Mobile 10\profile\*.ini
[Sounds]
FileBackupDirMode=Manual
MP31=\Windows\*.mp3
WAV1=\Windows\*.wav
WMA3=\Windows\*.wma
MP32=\Windows\Rings\*.mp3
WAV2=\Windows\Rings\*.wav
WMA3=\Windows\Rings\*.wma
[AppData_StartMenu_StartUp]
FileBackupDirMode=Manual
htcAudMgr=\Application Data\HTC\AudioManager_Eng\*.*,*
htcDownMgr=\Application Data\HTC\DownloadManager\*.*,*
htcStocks=\Application Data\HTC\ygo\*.*,*
htcTwitter=\Application Data\HTC\Twitter\*.*,*
StartMenu=\Windows\Start Menu\Programs\*.*,*
StartUp=\Windows\StartUp\*.*
Themes=\Windows\*.tsk
regexport.ini
- anything set to "Auto" gets saved to _Mod_\filesREG
- anything set to "Manual" gets saved to _Mod_\_Manual\filesREG
NOW SUPPORTS (as of version 1.1) 6Fg8's customRegExport Mod, see below for explanation and HEED THE WARNING!!!
6Fg8 said:
The mod allows additional parameters in REGEXPORT.INI:
Code:
[COLOR=Blue]key1=<yourkeypath1>
key2=<yourkeypath2>,<value1>,<value2>,<value3>, ... ,<valueN>
key3=<yourkeypath3>,*[/COLOR]
key1 is the traditional way of exporting registry keys as its already implemented. It exports this key including all values/subkeys.
key2 specifies a key, plus the value names you want to export (value1-valueN). Value names are CASE SENSITIVE (!), if they dont match you end up with an empty key.
key3 specifies a key, plus ALL values, but WITHOUT subkeys.
WARNING: DO NOT mix filtered (like in key2, key3 examples) and unfiltered keys (key1) in the same section, as this will lead to missing values. If you need to do this, split them into separate sections.
examples from my own usage:
Code:
[COLOR=Purple][B][Opera vibration][/B][/COLOR]
[COLOR=Blue]RegExportDirMode=Auto
key1=HKEY_LOCAL_MACHINE\Software\Opera\Defaults,VibrationEnabled
[/COLOR]
[COLOR=Purple][B][power+backlight settings][/B][/COLOR]
[COLOR=Blue]RegExportDirMode=Auto
key1=HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts,BattSuspendTimeout,BattSuspendTimeoutSave,ACSuspendTimeout,ACSuspendTimeoutSave
key2=HKEY_CURRENT_USER\ControlPanel\BackLight,BatteryTimeout,BatteryTimeoutUnchecked,ACTimeoutUnchecked
[/COLOR]
Click to expand...
Click to collapse
Code:
[1000_MySettings]
RegExportDirMode=Auto
Attachments=HKLM\System\Inbox\Settings\AttachPath
AudioGateway=HKLM\Software\Microsoft\Bluetooth\AudioGateway
Backlight=HKCU\ControlPanel\Backlight
BLTimeouts=HKLM\System\CurrentControlSet\Control\Power\Timeouts
Clock=HKLM\Software\Microsoft\Clock
JPG1=HKCR\.jpg
Notifications=HKCU\ControlPanel\Notifications
Phone=HKCU\ControlPanel\Notifications\Phone
PhVol=HKCU\ControlPanel\PhoneVolume
PictureLoc=HKLM\System\Pictures\Camera\OEM\PictureLocation
SavLocAud=HKCR\SystemFileAssociations\audio\shell\save\Save Location
SavLocIE=HKCU\Software\Microsoft\Internet Explorer\Main\Default storage location
SavLocImg=HKCR\SystemFileAssociations\image\shell\save\Save Location
SavLocVid=HKCR\SystemFileAssociations\video\shell\save\Save Location
SoundCategories=HKCU\ControlPanel\SoundCategories
Sounds=HKCU\ControlPanel\Sounds
TCPWindowsSize=HKLM\Comm\tcpip\Parms
Volume=HKCU\ControlPanel\Volume
Wallpaper=HKCU\ControlPanel\Desktop
WMV1=HKCR\.wmv
[1001_TarkimSettings]
RegExportDirMode=Auto
KeyConfig=HKLM\Software\KeyboardConfig
[1002_HTCSoftwareHKCU]
RegExportDirMode=Auto
Camera=HKCU\Software\HTC\Camera
DownloadMgr=HKCU\Software\HTC\DownloadManager
Manila=HKCU\Software\HTC\Manila
People=HKCU\Software\HTC\People
TaskManager=HKCU\Software\HTC\TaskManager
[1003_HTCSoftwareHKLM]
RegExportDirMode=Auto
AudioBooster=HKLM\Software\HTC\AudioBooster
AudioManager=HKLM\Software\HTC\AudioManager_Eng
Camera=HKLM\Software\HTC\Camera
Config=HKLM\Software\HTC\Manila\Configuration
Facebook=HKLM\Software\HTC\FacebookSDK
InternetPush=HKLM\\Software\HTC\Manila\InternetPush
PhoneExtended=HKLM\Software\HTC\PHONE\PhoneExtendSetting
SlidingSound=HKLM\Software\HTC\SlidingSound
StartUpAnimation=HKLM\Software\HTC\HTCAnimation
Twitter=HKCU\Software\HTC\TwitterApp
YouTube=HKLM\Software\HTC\YouTube
[1004_Co0kie]
RegExportDirMode=Auto
Co0kie=HKLM\Software\HTC\Manila\Co0kie
Home=HKLM\Software\HTC\Manila\Home
Tasks=HKLM\Software\HTC\Manila\Tasks
[1005_HTCAccountMgr]
RegExportDirMode=Manual
AccountManager=HKLM\Software\HTC\HTCAccountManager
[1006_StartMenuIcons]
RegExportDirMode=Auto
StartMenuIcons=HKLM\Security\Shell\StartInfo\Start
[1007_MySoftwareHKCU]
RegExportDirMode=Auto
7zip=HKCU\Software\7-zip
ArkSwitch=HKCU\Software\ARKconcepts
DualBoot=HKCU\Software\Gen.Y
Changescreen=HKCU\Software\idevelopstuff\changescreen
FacebookApp=HKCU\Software\Microsoft\Facebook
Modaco=HKCU\Software\Modaco
Mort=HKCU\Software\Mort
Mosko=HKCU\Software\mosko.mobi
neuLight=HKCU\Software\Wei Enterprise
Palringo=HKCU\Software\Parlingo
PIMBackup=HKCU\Software\FdcSoft
QuickMenu=HKCU\Software\AlenSoft
RSS=HKCU\Software\Ilium Software
SIPChange=HKCU\Software\The Paradigm Group
SK=HKCU\Software\sk
TotalCommander=HKCU\Software\Ghisler
xTep=HKCU\Software\xTep
[1008_MySoftwareHKLM]
RegExportDirMode=Auto
Adobe=HKLM\Software\Adobe
AdvancedConfig=HKLM\Software\AdvancedConfig
eT9=HKLM\Software\Tegic\eT9
IE=HKLM\Software\Microsoft\Internet Explorer
Opera=HKLM\Software\Opera
PocketMusic=HKLM\Software\PocketMind
SRS=HKLM\Software\SRS
TouchInCallScreen=HKLM\Software\Marzens
[1009_Services]
RegExportDirMode=Auto
Stowaway=HKLM\Services\Stowaway
HTCVol=HKLM\Services\HTCVOLUME
MyPhone=HKLM\Services\MyPhoneService
MediaLibrary=HKLM\Services\MLUService
WinLive=HKLM\Services\Windows Live
PushInternet=HKLM\Services\PushInternetEngine
BTSyncServ=HKLM\Services\BthAsPlugin
deleteops.ini
- below is an example of the deleteops.ini
- used to delete individual files or entire folders
- wildcard (*) can be used
Code:
[DeleteFile]
file1=\Windows\StartUp\HTC*Up.lnk
file2=\Windows\StartUp\sdim.lnk
file3=\Windows\StartUp\Setup*.lnk
file4=\Windows\StartUp\LockDevice.lnk
[DeleteFolder]
folder1=\Windows\Start Menu\Programs\Games
folder2=\Windows\Start Menu\Programs\GPS
folder3=\Windows\Start Menu\Programs\*net
folder4=\Windows\Start Menu\Programs\Multimedia
folder5=\Windows\Start Menu\Programs\Office Mobile
folder6=\Windows\Start Menu\Programs\Tools
anyfilename.auto
- below is an example of an ".auto" file
- used to automate cab installs that require user input
Code:
[AutoFile]
InstallLocation= (0 = device, 1 = storage card)
WindowTitle="Keyboard and Mouse Setup" (name of window to perform actions on)
[ScriptCommands]
1=SendLeft
2=sleep(100)
3=SendCR
4=sleep(1500)
5=SendOK
customlinks.ini
- if you want a link for a specific cab to be installed
- to a different directory than the default
- put exact cab file name without extension as first param
- wildcard (*) can be used
- after cab is installed, the link will be moved to where you want it
Code:
[LNK Files]
Myapp-version*=Programs\MyApps
regedit.Rpr_ARM=Programs\Registry Tools
kevtris=NONE
*=Programs\Other Tools
exeparams.ini
- same as above, filename (no ext) as it exists in _Mod_\filesEXE as first parameter
- parameters go after the equals sign
Code:
[EXE Parameters]
cusTSK=\Windows\Windows Mobile Green.tsk
scriptparams.ini
- same as above, scriptname (no ext) as it exists in _Mod_\filesMSCR as first parameter
- parameters go after the equals sign, inside the quotes
Code:
[Script Parameters]
MyScript="varone=one vartwo=two varthree=three"
Your zip file
Your zip file doesn't work. It gives errors when you try to unzip it.
BTW I search the whole xda for a post saying this and I didn't find one...lol
Other links
Sorry... updating zip file now...
Cingularman said:
Your zip file doesn't work. It gives errors when you try to unzip it.
BTW I search the whole xda for a post saying this and I didn't find one...lol
Click to expand...
Click to collapse
see top post for correct updated file =)
Great reference Ben..as always very well done!
krook6023 said:
Great reference Ben..as always very well done!
Click to expand...
Click to collapse
thanks, just trying to be a contributing member, even if "my" stuff isn't exactly 100% original... MortScript is getting easier by the minute for me, coming from self taught php background a lot of it is similar or the same even... I'm sure there's some languages that php resembles... but I'm not really a programmer of any sort, just an accomplished "tinkerer" heh...
I posted this in the Energy thread - it was suggested I ask here... any help would be great. Thanks.
Hi -
Can you give me a step by step on the order in which you do stuff after flashing (when to reinsert the sim card, when to run PIM Backup, etc.)? I basically stole your entire XDA_UC (thank you btw!) just adding a couple files and reg settings for some applications and a few things don't seem to work for me (i.e., my favorite people never come back in the right order or even the right people, my hotmail gets screwed up, etc.). I just can never seem to get any of the backups to work exactly right and I've tried SASHIMI, NRG's Export/Importer, and XDA_UC. I just think I'm doing something at the wrong time and things are stepping on each other or something. Anyway, thanks for the help!
PS I'm installing the latest 23xxx CHT rom via SD card ...
shannyb1972 said:
Hi -
Can you give me a step by step on the order in which you do stuff after flashing (when to reinsert the sim card, when to run PIM Backup, etc.)? ...snip...
PS I'm installing the latest 23xxx CHT rom via SD card ...
Click to expand...
Click to collapse
sorry for the slow reply, had to pick up my Dad from his elbow surgury and ran into car trouble on the way home (he just spent almost 6k on fixing that stupid thing in about a 2mo period... lol)
anywas... if THIS POST doesn't answer all your questions feel free to ask anything more specific =)
benjamminzIS said:
had to pick up my Dad from his elbow surgury and ran into car trouble on the way home (he just spent almost 6k on fixing that stupid thing in about a 2mo period... lol)
Click to expand...
Click to collapse
The car or the elbow?
Anyway, hope he has a swift recovery (and thanks for the great posts)...
rmanaka said:
The car or the elbow?
Anyway, hope he has a swift recovery (and thanks for the great posts)...
Click to expand...
Click to collapse
ROFLOL... yeah guess I should have been a little clearer on that =P the car... what a waste... american cars = teh suck!
benjamminzIS said:
ROFLOL... yeah guess I should have been a little clearer on that =P the car... what a waste... american cars = teh suck!
Click to expand...
Click to collapse
Maybe we ought to start sponsoring you (like we did NRG for a new Fuze) so you can get a European car?
Tazkika said:
Maybe we ought to start sponsoring you (like we did NRG for a new Fuze) so you can get a European car?
Click to expand...
Click to collapse
lol... no, not my car = crap. my dad's car... lol... my car, Lexus IS300 = wrecked (not the one in sig) into the back of my best friends truck, back in July, was looking (rubbernecking) at flipped car on other side of road, road was wet, person in front of my friend slammed on their brakes to turn left (while I was looking at flipped car) I slid into back of my friends Nissan Titan (I now call them wreckalexuses) LOL I will get another one soon enough, I just got screwed by my insurance company AND GAP coverage and ended up having to pay out because they decided to total it... only thing holding me back at the moment is a 9-5er (or 11-7, hell I'd take anything right now... lol) so no worries...
Look at me! I'm cluttering my own thread!!! heheeee
here is a quick question:
I want to copy a folder and his content from storage card to My Documents\My Pictures.
so from : Storage Card\XDA_UC\Files\ ( ProGloss_60%) this is the folder to be copied )
to : \\\My Documents\My Pictures
how can I do that ?
benjamminzIS said:
sorry for the slow reply, had to pick up my Dad from his elbow surgury and ran into car trouble on the way home (he just spent almost 6k on fixing that stupid thing in about a 2mo period... lol)
anywas... if THIS POST doesn't answer all your questions feel free to ask anything more specific =)
Click to expand...
Click to collapse
Sorry about the car trouble... no worries, I don't consider less than 24 hours a slow response to a message board anyway. You regular posters on this free community board are more responsive than my help desk at work!
Anyway, your post explains very clearly what you do up to flashing the rom. My question is more about the order to do things AFTER you flash. For example, I flashed the latest yesterday and it says "update complete". What is the order I should do things at that point? When to replace the sim, when to hard reset, when to run PIM backup, do I need to manually disable anything that's running, etc.?
Thanks for your help!
ceesheim said:
here is a quick question:
I want to copy a folder and his content from storage card to My Documents\My Pictures.
so from : Storage Card\XDA_UC\Files\ ( ProGloss_60%) this is the folder to be copied )
to : \\\My Documents\My Pictures
how can I do that ?
Click to expand...
Click to collapse
if that's all you want copied then just place it in XDA_UC\Root\My Documents\My Pictures
then use this part of my copy2root script, put it in a txt file and rename the txt to .mscr and place in the XDA_UC folder :
Code:
XCopy( "\Storage Card\XDA_UC\Root\*.*", "", TRUE, TRUE )
if you're already using my mod then just place place them in the folder as I first stated and they will be copied during the setup...
shannyb1972 said:
For example, I flashed the latest yesterday and it says "update complete". What is the order I should do things at that point? When to replace the sim, when to hard reset, when to run PIM backup, do I need to manually disable anything that's running, etc.?
Thanks for your help!
Click to expand...
Click to collapse
O.K... gotcha...
after update:
1. at "update complete" put mSD in
2. put battery back in
3. reboot
4. wait for xda_uc message to pop-up, hit "YES" to start
5. after setup is complete (wait for the second message saying customization is complete, I click NO here)
6. this is where I run TouchProTweak to setup a couple things I haven't figure out how to do via reg settings.
7. remove back cover and slide SIM in over battery (if you don't want to do it this way then slide2shutdown, remove battery and insert SIM)
8. restart
9. wait for connection setup, do setup
10. here is where I enter into manila my facebook, twitter and youtube passwords and link facebook accounts from the all people > updates tab
11. start enjoying your freshly setup rom!
I don't hard reset, because of task29... so far (2wks) I haven't noticed any issues due to not hard resetting after first screen calibration.
as for people tab not being in right order... I don't know if anyone has figured out a fix for that... I don't really use it other than to have those particular people in it, so it doesn't really bother me if it comes back in correct order or not...
thanks will try it .
thanks it worked .
Boy, I hope this isn't a dumb question... I've searched without any luck, but I can't imagine no one has tried this yet: Is there a way to export ActiveSync settings for XDA_UC? I couldn't find anything like that in the Settings Exporter.
Hello,
I present my second Windows Mobile app:
SettingsExporter – I think the name is self-explaining. I tried to develop an easy to use application able to backup the vital system/user/programs settings and parameters to a .reg file, which enables the user to quickly restore the settings after a flash or HR.
Yes, we already have the fantastic fdcTaskManager from dotFred but this one exports either single registry key (with all the values and subkeys) or whole registry. My tool is able to store:
- single registry value
- several registry values in one key
- all the values of a key but without subkeys
- values which names start with a certain string
- values which names end with a certain string
- values containing certain string
- whole key with all subkeys/values
The last point is realized with a help of already mentioned fdcTaskManager under permission from dotFred (thank you Man!).
Program features/requirements:
- supports AppToDate
- requires NetCF 3.5 to be installed in your ROM.
- the app is partially dependent on the TaskManager from DotFred. A file called dotTaskMgr.exe should always be placed in program folder. Of course it is included in the download files.
- the program can run from any folder on both device memory or Storage Card. You don't even have to install it (that's why I included also a zip archive with all the files), you can just run it from the actual location. However the installation cab includes also program shortcuts (they appear in Start Menu) and files neccessary for AppToDate.
- REMARK: Because of .NetCF limitations the program cannot parse some of the value kinds, like REG_MUI or REG_QWORD however these types are used in so deep system settings that I wouldn’t even try to touch, so from this point of view they are not necessary for normal user customization purposes.
REMEMBER: never play with registry unless you know what you are doing. Always make backup of your data before you start to edit any registry values.
I spent many nights on testing this app and on choosing the settings worth exporting so everything should work fine (I made at least 10 flashes in the mean time and didn’t discover anything suspisious). However I cannot be held responsible for any damages to your ROM/device.
Below you can find my screenshots and download.
In following posts you can find also:
Program description - post #2
INI file syntax and notes - post #3
Description of default .ini files - post #4
How does it work?
Currently the SettingsExporter is basically a registry parser reading thru one (or more) of three config files (keys_....ini) in which the user puts keys/values that are supposed to be backed-up. For each line which is recognized as a registry value the program tries to gather it from the registry and writes to a (specified) text file as Microsoft Registry Entries (.reg) syntax. If the line is not recognized as a correct registry key/value or if it does not exist in the device’s registry, it is simply ignored.
Following the tip from Jackos (thanks Man!) there can be three config (.ini) files:
- keys_System.ini
- keys_Manila.ini
- keys_Other.ini
The user can choose to process one, two or all three .ini files. He can also choose if all the entries from the checked .ini files should be stored in one .reg file or the program should create one .reg file for each .ini file. This way we can divide our backup into groups and then restore them on different ROM (e.g. with different version of UI).
The main screen of the program consists of 5 main elements:
- “Current file path” text box with current path and name of the destination file. The path is initially set to \Storage Card\Backup\MyBackup.reg, but it can be changed either directly in this text box or using “Change File Name” button which opens the SaveFileDialog allowing you to choose a location and name for your destination file. Unfortunately the native .NetCF SaveFileDialog is poor and allows only to save in 2 folders depths, so this is the reason why I left the text box unlocked to allow manual editing of the path. Additionally when closing SettingsExporter saves last used path in registry so when you open it for the second time the initial path will be “yours”. This feature can be switched off in options.
- 3 checkboxes allowing you to choose which .ini files the app should process
- Save File button starting the Backup procedure
- Menu softkey allowing you to change the program options
- Exit softkey that (surprisingly) closes the application.
The Options screen (you can open it via Menu -> Options) is also very simple:
- Save all settings in one file – when you tap “Save File” all the .ini files which are “checked” in the main window will be processed and the effect will be saved in one file mentioned in the “Current file path” text box in the main window.
- Save in separate files – the “checked” .ini files will be processed but this time the effects will be stored in separate files. There will be separate destination files created basing on the same file name from the “Current file path” text box, but with appropriate suffix, so using the default MyBackup.reg file name, the destination files will be MyBackup_System.reg, MyBackup_Manila.reg, MyBackup_Other.reg.
- Backup previous output files – if any of the output (destination) files already exists it will be copied with “_old” suffix before writing new file.
- Associate Reg Files to fdcTM – this button associates the files with .reg extension to the fdcTaskManager which is located by default in the program directory. From this point on you can tap on a .reg file in File Explorer and it will be automatically imported to the registry. Use this function to easily restore your .reg files.
- Save last backup path – this option enables saving last used backup (destination) path upon program exit. Remember – the path is written to registry when you close the program. So if you configured the .ini file to store also SettingsExporter’s settings (stored in HKCU\Software\Skrobel\SettingsExporter) and you want to backup also this setting, you have to set the file path in the Main Window, then Exit the program (to write the path to registry) then open the program again and now you can press “Save File”.
ini files requirements
The .ini file should be a Unicode text file stored in the same folder that the program executable is stored. The names of the file must be exactly one of the names mentioned above (keys_System.ini, keys_Manila.ini, keys_Other.ini). Of course the “keys_Manila.ini” file is not reserved ONLY for values connected with Manila/HTC and the “keys_System.ini” doesn’t need to contain ONLY system settings. It’s my proposal for the entries grouping, but you can change the contents according to your own needs. Only leave the file names intact.
About the syntax:
I tried to make the syntax of these .ini files as simple as possible. So it’s really similar to the syntax of a normal .reg file, exctept it does not need a “REGEDIT4” nor “Windows Registry Editor Version 5.00” at the beginning and of course the values cannot be given next to the valuenames. Here are some examples of the content of an ini file:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connections]*
[HKEY_LOCAL_MACHINE\nls\overrides]
*
[HKEY_CURRENT_USER\Software\Microsoft\Inbox\Settings]
"SMSDeliveryNotify"
"SMSAvailable"
"SMSUnicode"
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\QuickGPS]
actSync
auto
roaming
[HKEY_CURRENT_USER\SOFTWARE\HTC\MANILA]
Manila://*
"Weather*"
*Co0kie*
*Enabled
And what does it mean?
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connections]*
It means that the specified key will be stored with all it’s values and subkeys (if there are any).
Code:
[HKEY_LOCAL_MACHINE\nls\overrides]
*
This one means that all the values under the [HKEY_LOCAL_MACHINE\nls\overrides] will be stored but without any subkeys.
Code:
[HKEY_CURRENT_USER\Software\Microsoft\Inbox\Settings]
"SMSDeliveryNotify"
"SMSAvailable"
"SMSUnicode"
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\QuickGPS]
actSync
auto
roaming
In these two cases only the mentioned values will be stored from the specified key.
Code:
[HKEY_CURRENT_USER\SOFTWARE\HTC\MANILA]
Manila://*
"Weather*"
*Co0kie*
*Enabled
And this is an example of using regular expressions.
Manila://* - means that all the values with names starting with “Manila://” will be saved
*Enabled - means that all the values with names ending with “Enabled” will be saved
*Co0kie* - means that all the values with names containing “Co0kie” will be saved
As you can see the quotes are ignored so you can put valuenames with or without them and it will not make any difference for the parser.
The current version of the program includes my .ini files that are a result of long and careful tests and save most of the configuration of WM6.5 and WM6.5.x. I created these .ini files on HTC Rhodium and different Jackos ROMs. Most of them should work on a variety of HTC devices, however I've already seen that many settings for HTC Kaiser is stored in different locations than on Rhodium. But as I wrote before: if a registry key/value mentioned in the .ini file is not found in the actual registry, it will not be stored in any form.
On the other hand some of the key names may not work or not exist on different devices/ROMs. Especially when you try to restore a bunch of settings taken from a Sense 2.5 ROM on a Titanium or CHome ROM, you should expect some problems. That’s where grouping comes in handy.
If you have ideas for other registry values which should be backed-up by default or settings for popular third party programs I don’t use, please share key/value names here with a short description of what the values mean. I will put them in the default .ini files so other users can benefit from them.
What settings are included in default .ini files
keys_System.ini
In this file I included many settins which are changed via standard Windows Mobile Control panel applets and a bit from Advanced Config:
- notifications settings (remember - when you restore these settings after a flash, you have to make sure your ringtones and sound files must be in the same places that they were during backup)
- locale/time zone information (no language specific settings, only message coding, date/time/number formats, locale and time zone)
- messaging settings like threading, delivery report, unicode etc.
- paired Bluetooth devices
- owner information
- volume settings
- screen off/suspend timeouts
- some phone/dialer settings
- Font size/Clear type
- basic ArcSoft MMS settings
- last used profile
- clock/alarm settings
- AGPS
- hardware button assignment (only Long Press Send Key on Rhodium)
- Long Press EndKey action
- some other settings like noise reduction, AGC, USB to PC and less important parameters
Click to expand...
Click to collapse
keys_Other.ini
In here I stored some of the third-party applications I use. Please propose other applications with their settings and I'll add them:
- PimBackup
- HTCAccountManager
- Palringo
- Total Commander
- RSS Hub
- SK Tools
- Spb Backup
- cleanRAM
- Skype
- ultrashot UTask
- Quick Shutdown
- QuickGPS
- Whip2Snap
- last but not least - own SettingsExporter settings
Click to expand...
Click to collapse
keys_Manila.ini
Manila has many versions with extremely different settings and behaviours so I tired to store ONLY the most basic settings which should work on all the manila versions (correct me if I am wrong):
[HKEY_CURRENT_USER\SOFTWARE\HTC\MANILA]
HomeBackgroundPath - self explaining
AnimationWallpaperFolder - default folder for "choose background" option
Home.WallpaperMode - setting connected to full screen weather animation
Manila://* - this allows to store the configuration of showed/hidden Sense tabs
"Weather*" - settings for Manila weather
Of course I could add here all CHT settings, but there are also different versions of CHT on the "market" so I personally prefer to use CHT Editor backup/restore functions than to try to make universal backup utility for Co0kie settings. But if you guys have some hints on this topic I appreciate any help.
Click to expand...
Click to collapse
I will try to post here detailed description of all the values I know and will try to add here all suggestions from the community. But this unfortunately depends on my free time...
this is post #5
post #6 just in case...
Congratulations on your release I'll try and report back soon!
Looks great.........
oh thanks a lot! i like to play a lot with co0kie home tab 2.0 and also with the registry so it will be very useful to save some lines of a reg key. In CHT 2.0 all setting are in hkcu/software/htc/manila/CHT.*** (also CHTE.*** and CHTI.***) and i would like to save registry setting like CHT.Tweaks.***
I will try and report back later. Thanks again!
c_shekhar said:
Looks great.........
Click to expand...
Click to collapse
It looks ****, but works great
Jackos, you always know something good to say.
Good morning Skrobel,
Once again thank you for taking the time to develop this application. Sorry I didn't get back to you earlier. I had technical difficulties.
Following our recent conversation I'm posting below my findings about version 0.1 beta.
Pros:
Easy, intuitive UI
3 customizable registry patterns for different settings
A lot of 3-rd party software patterns
Thought-out set of settings
Cons:
90's looking UI
No support for exporting Twitter and Youtube Account Manager settings
Poorly implemented AppToDate support
Partly Sense and CHT support
No way to backup e-mail accounts and signatures (I know it's difficult to assemble)
No file backup at all
No support for all registry types (not really needed through)
I think you will agree that this app still needs further development. In my opinion Sense SDK is good enough to start with.
Yours truly,
Jackos
Hello,
Thank you all for your comments. I plan further development, so whatever you will find, I will at least try to solve.
@Jackos
You deserve special thanks. I don't wan't to defend myself but please remember I am still n00b if about programming And I'd like to comment at least some of your cons:
90's looking UI - I fully agree. This is still on my "to-do" list. Honestly I have already tried to run the Sense SDK from eboelzner (on an early stage of the app) and I just couldn't get the controls to appear on the form. I haven't spent much time on it though as this was not the most important thing to do. And there are only a few controls in this app which are big enough to operate with finger
Poorly implemented AppToDate support - honestly I did it same way as you did for your ROMs I know there is a possibility to download up-to-date cab directly from within the program, but I think the vital thing is to inform the user that something has changed. Nevertheless I will try to improve also here.
No way to backup e-mail accounts and signatures (I know it's difficult to assemble) - yes, you're right. And WiFi settings would also be fantastic to backup. I honestly don't know how to handle it. I did an extensive search among some developers forums and nothing up to now...
No file backup at all - this honestly was not in my plans. I use SettingsExporter in conjunction with PIMBackup in which I have my configuration (stored by the SettingsExporter by the way), and I backup all my files, contacts, messages and calendar within 2 clicks. I don't think any file backup is necessary...
No support for all registry types (not really needed though) - I've seen a tool written using NetCF where (according to the description) it is possible. I will ask the developer for help.
The rest of the "cons" concerns the configuration files which are subject to develop continously and independently on the tool itself. I was kinda hoping that this thread will grow with suggestions of other values of which I don't know and/or I don't use. So whatever you feel should be placed here, please post it hence help to improve for other users.
Skrobel said:
No way to backup e-mail accounts and signatures (I know it's difficult to assemble) - yes, you're right. And WiFi settings would also be fantastic to backup. I honestly don't know how to handle it. I did an extensive search among some developers forums and nothing up to now...
Click to expand...
Click to collapse
There are some encryption algorithms that aren't reverse-able. I have no knowledge with one is used in WinCe so maybe it's not possible at all. You could try to backup settings without including passwords.
I guess we have to ask ultrashot. He knows nearly everything about nearly anything
Skrobel said:
I guess we have to ask ultrashot. He knows nearly everything about nearly anything
Click to expand...
Click to collapse
He's disassembling WM and SE mobile systems since he stopped using chamber pot
Strange, 35 downloads and nobody reported further problems? I don't believe there aren't any.
I dig up the e-mail and WiFi backup, but no real results yet. On the other hand I know how to handle the Sense SDK controls, so the next release will probably have better look as requested. But I don't want it to be the only update, so report guys, report
Runs fine on my Axim X51V running WM6.5. I've been using an old app until now called SettingSavior. And for specific third party apps, if I was able to find a registry entry where the registration key was stored, I used SKTools to create a reg file for that. then I used Shashimi to import cabs and .reg files.
Will explore your app more.
Some suggested other 3rd party apps for setting backup:
Sprite Backup
Galarm
Resco Explorer
Pocket Music
I used similar method to store my settings. I used CeRegEditor to make an "image" of the registry, then I changed my settings (also for third party apps), then I compared the saved image with the current state.
But if you use these programs and you have your setup created with SKTools, could you share it with me? I could check what settings are used for these apps, and update config files with them.
Thanks for creating this useful application ,I use this application, PIMBack-up and XDA_UC_NET - portable to fully automate the restore. Now a Hard reset or ROM update is a breeze.
Regards [email protected]
The material provided in the unofficial theme. In the case of a failed flash unit, and the topic of the site is not liable! All actions are at your own risk.
I present you the firmware WM 6.5.Standard Build 23 017
Just a flashing 3 languages (0407 (German), 0409 (English), 0419 (Russian)), the default English. And 3 input language.
Screen theme (Sliding Panel & Sliding Panel Media) converted from Rose Sliding Panel's, which made it possible to use HTC Weather.
After the firmware necessary to reboot the device!
Programs: Celetask, CHome configurator, Clock on Top, WM5torage, Registry edit.
Links:
http://www.mediafire.com/?hnd324uanwwz0id
https://rapidshare.com/files/3185754262/6.5.BIN
Calls, SMS sending, SMS takes, SMS as chat, Bluetooth works, in general, everything seems to be working pretty well!
Thanks to all who helped in creating this firmware!
downloading - will give you feedback asap
I have checked on the package and here are the comments:
The backlight/display driver is not acting according to the settings in the control panel. The display does not get off. The light gets off - but not the LCD. You can see that when you put the display in bright light. When making my kitchen for WM6 I have tried out several different drivers all having one or the other problem and finally decided for the one present there. Please re-check your choice in the light of above problem which creates a big battery drain unfortunately.
The German language is only fractional available. I think that the packages are missing some .provxml files or that these are not read correctly. You can cross-check needed actions for multi-language in my beginners guide for cooking. Especially tracking down the correct execution of .provxml is tricky. There are some threads at XDA dealing with this. I found finally that using the rapiconfig tool on the connected PC sending the files for execution is giving a fast and reliable method for debugging. Search for "provxml" and "rapiconfig".
For my kitchen I had added at the end of each .provxml a registry entry to write to HKLM\Platform with the name of the .provxml as an entry. This way you can check if the file was executed in the first place and then further investigate which was not.
Finally I have seen that the WM65 allows to have skinned menus which complement the sliding panels appearance. Would be good to see that in the WM6.5 ROM as well.
Good luck with your further cooking!
Oh one last thing: You should change your topic title to include "WM 6.5". Not all know that WINCE 5.2.23017 is one internal version of the WM6.5. I think that WM6.x translates to WINCE 5.2.y before that was WM5 with WINCE 5.1.z.
tobbbie thanks for the posts!In other rom, i want to do all languages good!
Upd.04.09.11
Hmmm... I don't know what with backlight driver!!!I i don't change him!
Nex update will be only with 2 languages (en-ger and eng-rus) because, i don't know how edit mxip_lang.vol!!!
Have you done anything lately to the ROMs? I finished my Typhoon and Tornado porting to OS Builder, so Hurricane is on the list now to have these old candy-bar phones complete on OSB.
When dumping the ROM with OSB, I noticed that you had used the "merge packages" option when assembling it. This makes it harder to get started, though not impossible as I have the XIP to build my own 6.5 (which I used from the Captain for the Tornado).
Where did you get the base from?
Which kitchen tools have you used?
Hi tobbbie!
Ok, i send you archive later.
but there is a problem, display driver(backlight) don't work correctly(i trying 5 or 6 backlight.dll) and if driver saving power correctly, when you receive incoming call, display don't turn on =(
I think best choose for hurricane is 6.1 =)
It is strange with the backlight. Usually the OEM parts are those that do NOT change in the porting process and so their behavior should also not when the SYS changes.
Problem with the Hurricane is that many OEM modules do not have a relocation section and so can not be properly relocated by some tools. In the batch kitchen I used, the wmreloc.exe could magically do the job nevertheless, probably by making clever general assumptions on the structure of the modules.
When porting Aleut's WM65 for Typhoon to OS Builder I have identified the modules without relocation section (wmreloc writes a special file to the modules folder for those) and "nailed" them to their current location by adding them to the OSB list of "do not relocate" modules.
To be sure that you start with a working set of modules, it is mandatory to start with a dump of such a working device and not a fresh directory setup - where you would rely on the relocation to properly work for ALL modules.
For Typhoon there were just 5 modules without relocation section because there existed a leaked WM5 "dogfood build" for that device. This had all modules including their relocation section. So just the non-Typhoon (Feeler and Amadeus) specific things (keyboard I remember) needed that special treatment.
For the Hurricane I had counted many more such modules and I am not sure if I will ever get a running OSB setup for this. Last time I tried I could not even get my working WM6 setup rebuilt, so this project may find an early ending.
Good news: I got my WM6 build running and re-built with OS Builder. Took some time to discover that the empty boot.rgu from OEMXipKernel package has left out the Launch20=service.exe from the resulting registry, which made the boot stop at that point.
So nailing the OEMDrivers does work here as well - there is hope for more to come here as well
Tobbbie, it's fantastic!!!
I use your kitchen to create imgfs.bin, then i use imgfs.bin with program nbwork to create os.nb(with uldr.bin xip.bin imgfs.bin) and then use you program xipbin =)
To port wm standard roms, i also tryed 28004, and once it's work, but there is no different =)
P.S. links add some minutes later, now uploading to mediafire.
Thanks for your work!
link: http://www.mediafire.com/?qu1x574f8u437g0,lb4ha9rm53n9gpu
And i also rying to poted wm pprofessional on hurricane,it start, but work with some lags, and need to rewrite some oem drivers =)
Why do you need extra tools outside my Hurricane kitchen set? If you put the WM6.5 XIP and Partition framework in the Source folder with the right names then the batch should deliver a ready-made .bin at the and as well.
The easiest way to get back to the one-step batch would be to pick one of your two-step created .nb files, rename it to 82040000-OS.nb and put it to the SOURCE folder.
Batch processing will cut out the pieces and supply the compression for imgfs later - no more two-step.
Last step of the kitchen is basically to joint the new created imgfs with the already ported XIP and ULDR (if present) to a new .nb and then put it to transfer format of the BIN file - transparent blocks with some kB size (not sure if it is64k) and a checksum so that transfer errors can be detected.
Anyway the important part is the creation of the imgfs and especially the correct relocation of modules, something special with the Hurricane and its many modules without reloc section.
You up'ed 2 files, one named "part1.." is there a part 2 also or is this the create_wm6_5?
I guess I will just use the SYS I have for WM61 (from Rose) and WM65 (from Captain) in my Tornado OS Builder kitchen for porting inside OS Builder. This is easier than porting from Batch to OS Builder.
I see no advantage of WM65 over WM61, but all done for the WM61 can be transferred 100% to WM65, so no big deal here. The added functions on WM65 are not worth it:
some memory and CPU hogging browser ad-on
and "widgets" you cannot use on smartphone anyway
and a 1MB bigger SYS with otherwise identical packages
make not up for the option to be able to skin your menus, they just get bigger and making that finger friendly on smartphone is a joke
Sliding panels are in WM61 already (for those who like it) but I have my private homescreen that does all I want on one page and it includes ToDos which the Sliding panels does not.
---------- Post added at 05:10 PM ---------- Previous post was at 05:08 PM ----------
sniper304 said:
And i also rying to poted wm pprofessional on hurricane,it start, but work with some lags, and need to rewrite some oem drivers =)
Click to expand...
Click to collapse
Why professional - you have touchscreen on Hurricane? Just the 96DPI is nice for more screen estate (smaller top/bottom bars) - but I don't care, really.
---------- Post added at 05:12 PM ---------- Previous post was at 05:10 PM ----------
BTW: WM6 Kitchen runs full gear and all options - time to port to WM61 and WM65
in part 1 your kitchen with sys 6.5
in create 6.5 nbwork and rom files(uldr.bin xip bin)
I don't like imgfstonb tool =)
Some times i get bad roms, with bugs, but when i used nbwork, all roms work good.
tobbbie said:
I see no advantage of WM65 over WM61, but all done for the WM61 can be transferred 100% to WM65, so no big deal here. The added functions on WM65 are not worth it:
some memory and CPU hogging browser ad-on
and "widgets" you cannot use on smartphone anyway
and a 1MB bigger SYS with otherwise identical packages
make not up for the option to be able to skin your menus, they just get bigger and making that finger friendly on smartphone is a joke
Sliding panels are in WM61 already (for those who like it) but I have my private homescreen that does all I want on one page and it includes ToDos which the Sliding panels does not.
Click to expand...
Click to collapse
I found one advantage WM65 over WM61 that maybe useful for some: WMPlayer shows embedded Album Art in WM65 while it does not in WM61. This includes the art display in the sliding panels Media Panel. I use Conduits PocketPlayer for years so never cared about this.
All OS Builder kitchen run well now (6.0, 6.1-Rose and 6.5-Captain). XIP porting was a little inconsistent across these versions but all startup and reboot without flaws.
Still have to cleanup the package sort order - at least in WM6.5 - and see if A2DP would work well (though it is a CPU hog and I would never recommend it).
Release may happen next weekend -> watch out for a dedicated thread then.
Best with the Hurricane cooking is that you will not have to care about ROM size and balancing with storage space on the device in 1 MB steps like on the Tornado - or be limited to fix size like on the Typhoon. The "l" (load) commend will trigger in the SPL a ROM-size matched formatting of the BINFS (in 64k steps, I guess).
Also "good" is that the device still has a RIL v1, so the Radio ROM is smaller (and less capable) then the Tornado Radio. You will hardly note the difference, however will NITZ (Time setting via GSM Network) not work with this RIL.
Even with 8MB Paging Pool (my default) you have free RAM of ~32MB (Sliding Panels Homescreen) or ~34MB with standard Homescreen. You could make the PP even 10-12 MB here and have the device even more "snappy" with several applications in parallel.
tobbbie Thanks for the good work!
I want also clean rom from FWUpdate, because in our phone it's not used, i some time make experiments with some files and when deleted one(i don't remember what file =((( )and it will free about 3 Mb Ram(on startup 35-36MB with sliding panels with weather =)), but i sometimes think, it's unbeliveble, because when i deleted that file, some system pictures don't work(etc. system notification) =(
I think the need to rewrite some system files in order to achieve this = (
No wild deletions, please. FWupdate is removed in the OSB kitchen and only one stub is left in WM6.1+ because otherwise the ROM does not work. Also some other packages are made optional (e.g. SQL mobile) - it so easy making something selectable with OSB (drag + drop), really fun to play with.
The OSB framework has sophisticated tools to analyse the dependencies, so a lot of insight to gain there. If you are curious, download my Tornado OSB Kitchen and do some dry-cooking, the Hurricane will be 98% the same. Also visit the main OSB kitchen thread to get the basic documentation.