An Idiot's Guide - The Lazy Gourmet!!! - Touch Pro, Fuze ROM Development

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

Related

[KITCHEN][WWE][20.03.2010]Windows Mobile 6.1 21056/20779 Kitchen for Raphael GSM

Welcome; I wanted to offer a little "something" back to the XDA community in the hopes that it will benefit others and to show my appreciation to the folks that make XDA the great community that it is.
There are many chefs that provide quality ROM's for you to use. However, if you've gotten excited about the idea of cooking your own ROM's, you've probably felt overwhelmed by the volume of Forum Threads and Wiki pages at your disposal to learn how to do this. The goal of this thread is to provide a starter kitchen so as to help new and intermediate chefs; the kitchen will produce a fully functional ROM for a Raphael device.
The kitchen includes a Read Me and Change Log file. The Read Me file contains answers to frequently asked questions as well as "known" issues. The Change Log file includes a list of changes that were made to files such as the .RGU, .PROVXML, etc.
Kitchen
Post #2 provides a kitchen that is built with Ervius Visual Kitchen; the post additionally provides updates to the content of the kitchen when necessary.
Discussions on the current version of the kitchen posted in this thread begins here: http://forum.xda-developers.com/showpost.php?p=5398310&postcount=1176
Application Packs
Post #3 provides additional applications that have been tested in the Ervius Visual Kitchen. It is recommended to download the packs before altering the kitchen.
OEM Packs
Post #4 provides OEM folders that are specific to the Ervius Visual Kitchen. These are intented for chefs who are looking to add the latest OEM to an existing kitchen.
ROM/SYS Packs
Post #5 provides ROM (XIP) and SYS folders that are specific to the Ervius Visual Kitchen. These are intented for chefs who are looking to add the latest ROM/SYS to an existing kitchen.
Workstation/System Requirements:
WinRAR 3.30
http://www.rarlab.com
IZArc 3.81
http://www.izarc.org
Microsoft Visual C++
http://msdn.microsoft.com/en-ca/visualc/default.aspx
Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)
Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)
Microsoft .NET Framework
http://msdn.microsoft.com/en-us/netframework/default.aspx
Microsoft .NET Framework 3.5 Service Pack 1
Microsoft .NET Framework 2.0 Service Pack 1
Microsoft .NET Framework 1.1 Service Pack 1
Tutorials:
The following tutorials are available for newcomers who wish to learn about how to use the kitchen in this thread:
Kitchen
Sous-Chef's Guide to Da_G's Ervius Visual Kitchen 9.7
http://forum.xda-developers.com/showthread.php?t=521632
Porting
Sous-Chef's Guide to XIP Porting in Ervius Visual Kitchen
http://forum.xda-developers.com/showthread.php?t=526610
Wiki:
Previous versions of the tutorials, kitchens, tools updates, fix packs, OEM packs, and ROM/SYS packs can be found at the Raphael Wiki in the WM6.1 ROM Kitchen (Simple and Visual) section.
http://forum.xda-developers.com/wiki/index.php?title=Da_G's_Simple_ROM_Kitchen
Languages, DPI, Resolutions:
Language localization packages, DPI files, and Resolutions can be found in the Development & Hacking forum.
http://forum.xda-developers.com/showthread.php?t=547314
Package Repositories:
Raphael OEM Package Repository
http://forum.xda-developers.com/showthread.php?t=482173
Raphael OEM Packages
http://www.4shared.com/dir/12314954/9a1ec6bc/sharing.html
Credits:
Special thanks to the following folks for sharing their knowledge and expertise. If I missed someone, it's purely accidental – send me a note and I will add your name to the list.
da_g
cmonex
olipro
bepe
ervius
ameet
Contributions:
A thanks goes out to the following folks for their contributions to the kitchen. If I missed someone, it's purely accidental – send me a note and I will add your name to the list.
da_g
aruppenthal
b4pjs
captain_throwback
eras2r
jmckeejr
noonski
notatreofan
nrgz28
r.camies
xboomer55
Visual Kitchen
Created using Ervius Visual Kitchen 1.8.2; includes sleuth255 User Customization (UC) version 2.0. This post includes a list of packages that are included in the kitchen, a change log, and a read me file - which can also be found in the documentation folder of the kitchen. Also, take a moment to look at the Visual Kitchen Pack post, there's a list of what is included in the pack attached to the post.
WWE Visual Kitchen 6.1, OEM: 5.12.206.1 (20779), SYS: 21055, ROM: 21056/20779, 158 MB, 17.01.2010
Post-Download Instructions:
Extract the contents of kitchen archive to the root of your hard drive (ex: C:\XDA) to avoid path length errors.
Move the kitchen to the desired location.
Cooking Instructions:
Launch Erviuskitchen.exe.
Click the Load ROM button.
Select the FUZE/PRO .ERV ROM file.
Click the Create ROM button; allow the process to complete.
Wait for the Done message to appear in the Bottom Status window.
Exit the Ervius VisualKitchen application.
Tip
If the compilation is successful, the last three (3) lines in the Report window of the Ervius VisualKitchen application will display: ROM Builded successfull! Reenabling all skipped packages. All packages Reenabled. All Done.
RUU_SIGNED.NBH will be in the RELEASE_Raphael kitchen folder.
Verify the BUILD_LOG file after compiling a ROM; module entries in SLOT0 typically indicate that the stability of the device will be unpredictable; recode some modules.
The Sensor SDK 4 package provides enhanced screen rotation support; it includes a .PROVXML file that can be customized to include additional applications - Whitelist & Blacklist.
Known Issues:
Bottom of text cut-off in Connection Setup with large menu package installed.
Very Rare: Tapping Cancel on Connection Setup panel may be required if panel appears during post-ROM flash and/or Hard Reset.
Very Rare: Airplane Mode may be enabled (instead of Phone Mode) post-Hard Reset configuration phase. Pro: make setup finish faster, Con: extra tapping steps to switch Phone mode back on from Comm Manager.
Kitchen Tools Update:
Latest version of Ervius Visual Kitchen tools that have been tested with the kitchen in this post. The KITCHEN_BUILD_ROM.BAT has been updated to include logging; otherwise, the remainder of the files are those found on the Ervius Visual Kitchen thread.
None Available
Kitchen Fix Packs:
A kitchen Fix Pack addresses issues and oversights that were discovered after the release of the Visual Kitchen. The Fix Pack only contains changes to files and packages that were released as part of the kitchen. The Fix Pack does not contain changes to packages that appear in a Visual Kitchen Pack; changes/fixes for packages in a Visual Kitchen Pack will be addressed as part of a new pack.
None Available
Visual Kitchen: Application Packs
The Kitchen Application Packs includes additional applications that have been tested in the Ervius Visual Kitchen. The packages have been organized (sequenced) so as to ensure that the ROM produced by this kitchen is the same as the Package Builder (legacy) kitchen.
The pack applications have all been set to Unselected (False) - a package must be double-clicked to include the package during ROM compilation. The PACKAGES.TXT files in each PACK will overwrite the base kitchen version - providing a description for each package.
The .TXT files attached to this post contain the list of packages that are in the corresponding kitchen pack.
Visual Kitchen PACK 1, 29 MB, 13.06.2009
Visual Kitchen PACK 2, 28 MB, 13.06.2009
Visual Kitchen PACK 3, 30 MB, 26.06.2009
Visual Kitchen PACK 4, 50 MB, 16.08.2009
Visual Kitchen PACK 5, 05 MB, 16.02.2010
Post-Download Instructions:
Extract the contents of kitchen pack archive to the root of your hard drive (ex: C:\XDA) to avoid path length errors.
Copy the contents of the extracted kitchen pack to the kitchen .\EXT folder.
Tip
The archive folder structure matches the kitchen folder structure that corresponds to the build on which the package has been tested.
Use a file comparison utility to ensure that you do not lose any changes you may have made to existing packages in the kitchen.
The applications in these packs were tested using the Customized Device profile (DEVICE_CUSTOMIZED).
Recoded Modules Application Packs (Optional)
Although Windows Mobile 6.1 improved Virtual Memory (VM) by providing SLOT 60 and 61, modules can not be allocated in SLOT 60/61 - only files. Current kitchen relocation tools did not require any changes as SLOT 1 and 0 are the only slots where modules can reside. Device stability is compromised however, when there are too many modules as "spilloff" occurs into SLOT 0 resulting in reduced available memory which causes the device to report memory errors (even if it's not truly out of memory) or erratic application functionality.
RECMOD Application Packs contain versions of packages that appear in the kitchen and existing kitchen packs. These packages have had their modules recoded; the package names have _RM appended at the end of the name. When using RECMOD packages, it is important to remove the non-recoded version from the kitchen to avoid ROM compilation errors.
Visual Kitchen Recoded Modules PACK 1, 15 MB, 16.08.2009
Visual Kitchen Recoded Modules PACK 2, 05 MB, 16.02.2010
Visual Kitchen: OEM Packs
Chefs looking to simply update their existing kitchen OEM folder without having to download an entire kitchen can now do so with an OEM pack. The OEM Packs include the OEM folder for specific builds of Windows Mobile 6.1 and have been tested in the Ervius Visual Kitchen. The OEM pack also includes a corresponding optional DEVICE_* and OVERRIDE_KEYPAD_* package.
The DEVICE_* package contains all of the files that were removed from the original OEM folder. Closely examine the contents of the package before use as it contains untouched stock files that were found in the released ROM.
The OVERRIDE_KEYPAD_* package contains a copy of the the KEYPAD.DLL file from the .\OEM\OEMDrivers folder and can be used to ensure that the desired KEYPAD.DLL is installed during ROM compilation.
A text (.TXT) file appears in the .\DOCS folder of each OEM pack which details changes that have been made. As a result of a limit to the number of post attachments, only the latest versions of the OEM pack change logs have been added.
OEM: 5.12.206.1 (20779), 06 MB, 30.07.2009
OEM: 5.11.502.2 (20771), 22 MB, 30.07.2009
OEM: 5.05.405.1 (20764), 08 MB, 30.07.2009
Post-Download Instructions:
Extract the contents of OEM pack archive to the root of your hard drive (ex: C:\XDA) to avoid path length errors.
Copy the contents of the .\OEM\Raphael\.VM\ folder in the kitchen to the extracted OEM pack .\.VM\ folder (ex: C:\XDA\VISUALKITCHEN-OEM-PACK-20771\OEM\Raphael\.VM\).
Rename the existing .\OEM folder in the kitchen (ex: OEM.20771 or OEM.precopy).
Kitchen Conversion Instructions:
Copy the contents of the extracted OEM pack, which now includes the contents of the .\OEM\Raphael\.VM\ folder, to the kitchen folder (ex: C:\XDA\My_Visual_Kitchen\).
Rename the .\OEM.<buildnum> folder copied to the kitchen to .\OEM (ex: OEM.20771 to OEM).
Tip
The archive folder structure matches the kitchen folder structure of the legacy kitchen found in this thread.
Use a file comparison utility to ensure that you do not lose any changes you may have made to existing packages in the kitchen.
Note
The DEVICE_* and OVERRIDE_KEYPAD_* packages will be set to Selected (True) - a package must be double-clicked to exclude the package during ROM compilation.
Visual Kitchen: ROM/SYS Packs
The ROM/SYS Packs include the ROM and SYS folders for specific builds of Windows Mobile 6.1 and have been tested in the Ervius Visual Kitchen. The ROM/SYS also includes corresponding base ROM compilation profiles, pre-configuration (ERV) files, that have been tested in the kitchen.
Chefs will find untouched versions of the base XIP.BIN and OS.NB.PAYLOAD (no imgfs) as well as the donor XIP.BIN and OS.NB.PAYLOAD (no imgfs) - when available.
A text (.TXT) file appears in the .\DOCS folder of each ROM/SYS pack which details changes that have been made. As a result of a limit to the number of post attachments, only the latest versions of ROM/SYS pack change logs have been added.
SYS 21056, ROM: 21056/20779, 37 MB, 17.01.2010
SYS 21056, ROM: 21056/20771, 37 MB, 17.01.2010
SYS 21056, ROM: 21056/20764, 37 MB, 17.01.2010
Post-Download Instructions:
Extract the contents of ROM/SYS archive to the root of your hard drive (ex: C:\XDA) to avoid path length errors.
Rename the existing .\OEM\Rapheal\.VM folder in the kitchen (ex: .VM.20771 or .VM.precopy).
Backup the existing .\ROM\Raphael\ files (.TXT, .BIN. PAYLOAD) in the kitchen. The files to backup are:
INFO.TXT
OS.NB.PAYLOAD
ROMHDR.BIN
XIP.BIN
Kitchen Conversion Instructions:
Copy the contents of the extracted ROM/SYS pack to the kitchen folder (ex: C:\XDA\My_Visual_Kitchen\).
Tip
The archive folder structure matches the kitchen folder structure of the visual kitchen found in this thread.
Use a file comparison utility to ensure that you do not lose any changes you may have made to existing packages in the kitchen.
Note
.NET Compact Framework (NetCF) is a merged version of 2.0 & 3.5.
The following applications have been removed from the SYS folder and placed in the kitchen EXT folder; they are also available in an Application Pack and the Package Repository noted in the first post of this thread.
- Auto Data Config (ADC)
- Adobe Flash
- Infrared Data port (IrDA)
- Live Search
- Modem Link
- Remote Desktop Mobile
- Voice Command (MSVC)
- Voice Over IP (VoIP)
- Windows Live (MSN)
- Windows Media Player (WMP)
Emulator
Da_G,
Thanks for the kitchen.
Just wonder if there's any good ROM emulator to test any mod before flashing into a real life device?
This will hopefully prevent bad ROM and bricking phone.
With HardSPL, you stand little chance of bricking the phone, you can always return to bootloader and flash a working ROM. But as to an emulator, yes there is one, but it does not emulate the hardware the Raphael has, so for that purpose it would not work, none of the drivers would load up and the emulator would not boot. You would have to create a special version without drivers - but then, you aren't really testing the important part As long as you have HardSPL, you can flash without worry.
As for a guide to mashing things up before cooking, i'm putting together a large collection of packages.. choosing what you want in the ROM will be as simple as checking boxes.. as far as editing the registry goes, you need a program that can open/save in unicode.. i personally use EmEditor..
Thanks Da_G. This one is working great. I checked with base OEM/ROM/SYS folders. If I want to include any cab files how can I include them? I tried to copy a cab file in packages folder and it didn't pick up. Is there any thing I need to do? Actually my idea was to include some cab files in the rom instead of using UC while flashing.
Thanks
You have to convert the cabs to packages first.
http://wiki.xda-developers.com/index.php?pagename=OEM Package Tutorial
Da_G said:
With HardSPL, you stand little chance of bricking the phone, you can always return to bootloader and flash a working ROM. But as to an emulator, yes there is one, but it does not emulate the hardware the Raphael has, so for that purpose it would not work, none of the drivers would load up and the emulator would not boot. You would have to create a special version without drivers - but then, you aren't really testing the important part As long as you have HardSPL, you can flash without worry.
As for a guide to mashing things up before cooking, i'm putting together a large collection of packages.. choosing what you want in the ROM will be as simple as checking boxes.. as far as editing the registry goes, you need a program that can open/save in unicode.. i personally use EmEditor..
Click to expand...
Click to collapse
You're the man I wait with great patience going to also try the idiots guide as well as building in PPCKitchen as we speak I've had some issue getting the ROM to build... do I need Visual Studio as my backend dev box? I have 2003 Visual Studio but I'm thinking I need a newer version as for EmEditor; I'll grab that too. Thanks for the coaching, I hope to churning the buttah lik you my friend lol.
You need the .NET 3.5 runtime for windows (not .NET CF 3.5 for windows mobile), you can find it at microsoft's site. I believe that's the only requirement for the apps in the kitchen to run..
I'm about half-way done on the packages, archive is only 55mb so far.. gonna post a pre on my ROM thread since it's based on my ROM.
Thanks a bunch Da_G! I feel tempted to cook something. Do you also have a package that can give a man more time? Now THAT would be useful!
No packages for more time, sorry
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here's the first version of all the packages i've made thus far: http://forum.xda-developers.com/showpost.php?p=3176535&postcount=1498
You don't need the kitchen from the first post, i included it in the package there.. same steps to follow, but i've included a good amount of packages.. of course there will be more coming soon, rome wasn't built in a day
Don't forget to scroll down on the list of packages, it goes off screen in buildos
Da_G said:
No packages for more time, sorry
Here's the first version of all the packages i've made thus far: http://forum.xda-developers.com/showpost.php?p=3176535&postcount=1498
You don't need the kitchen from the first post, i included it in the package there.. same steps to follow, but i've included a good amount of packages.. of course there will be more coming soon, rome wasn't built in a day
Don't forget to scroll down on the list of packages, it goes off screen in buildos
Click to expand...
Click to collapse
Da_G YOU RULE BRO!
Posted a Diamond Phone canvas + Slide 2 Answer package, you can get it here - thanks to player911 for fixing it all up
It will of course be included in the next revision, but here it is now
Da_G said:
Posted a Diamond Phone canvas + Slide 2 Answer package, you can get it here - thanks to player911 for fixing it all up
It will of course be included in the next revision, but here it is now
Click to expand...
Click to collapse
Quick question - why don't you use original Diamond package (called "PACKAGE_Diamond_PhoneCanvas_Slider") for S2A taken from 2.03 Diamond rom? - it's working perfectly in my PROven
Dunno, figured there was some issue with it? I don't use it.. when i tested it shortly it seemed to work fine, is there a difference from the package I posted?
I've updated several of the packages in the kitchen with new builds from the just-released diamond gsm rom, and added a couple more new packages. still no scripting to select the os version you want, but it'll come
On my way out the door, so no time to upload now.. hopefully tonight Gonna test them while i'm out.
Da_g kitchen works great still don't know what I'm doing or what's going but how do I change manila's and stuff? I want to use the confuzed backgrounds and colorings.
Thanks!
The easiest way to do that is to ask monx if he can share his customized packages, you can then just drop them in the \Packages folder and select them (providing he has made an option.xml to go with it)

[UC]XDA_UC Autoconfiguration User2User Thread[23-06-2009]

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!!!

[XDA_UC][UC][SASHIMI][S4X] S4X_Auto & S4X_Backup [DEC.02.2010] XDA_UC Mods & Answers

[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.

[Q] New Ervius Kitchen 1.82 Issues

First of all, thanks for all who contribute to the resources of winmo in this forum.
I found a nearly perfect ROM for my region from this forum, RUU_Leo_1_5_HTC_Asia_TW_2.14.709.P1_Radio_Signed_1 5.39.50.07U_2.10.50.26_Test stock ROM, so I want to cook it, without any modification except from module to file the ntfconfig.dll folder.
The build process thrown an error level 1, so I search XDA for possible solution which is REM out the this line in kitchen_build_rom.bat
set DSM_TEMPLATE=%dsm%
set DSM_INCLUDES=*
REM **************** TOOLS\platformrebuilder.exe
REM if not "%errorlevel%"=="0" goto error
Now it makes a RUU_Signed.nbh and I flash it to my HD2/LEO, Asia_TW version.
But I found some issues, expert please help me solve these:
1. The start menu folder icons were gone.
2. The start menu outlook folder is empy.
3. The start menu setting icon is not on the top (not a big issue but is better to have the default).
4. How do port a new XIP (21914) with only MSXIPKernel folder. this folder although has the same size with older 21892 MSXIPKernel folder.
Thnak you!
Edit: problem solved, I use oskitchen zero, and is working well!

[ROM] I love DFT (7392 ROOTED) [YukiXDA] [26/06]

Let's make HD2 the best Windows Phone 7 device ​
My tutorial on porting WP7 sys (and update to NoDo) for HD2 is in my 2nd post, you'll find too my tricks and ideas​
Thanks to Ruzzichella, DFT, bepe, cotulla, ervius, AnDim, Nokser, ansar, OndraSter, airxtreme, misar etc. etc.​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
16/05 First release:​Porting HD2 WP7 rom to NoDo (see 2nd post)
​New theme with transparency I've called Aero
​HTC Hidden Wi-Fi works since I've updated some OEM packages. To have a wifi mac adress which don't change at reboot try to set it in the nvram.txt file (see my second post)
​Rom is unlocked and prevented to relock.
​A video demonstration: Youtube_WP7_NoDo_ROM_HD2 (thanks Jaxbot)
​05/06 Update:​Green key is now hard remaped, I've chosen the function of bluetooth Headset: Play/Pause multimedia, Skip by pressing twice, Answer a call (when receiving), End call, (when in call), long press to rapidly call someone by speech input.
​Replaced camera button by a software button with autofocus like on Androïd so no more blur.
​Radio is working without the need of headphones.
​Added keyboards layout for some other countries and added some cool features. More layouts to come soon.
​Improve performances, localisation (assisted gps - agps), Bluetooth, battery consumption. (mine is between 3 and 6 mA)
​Solving of certains difficulties to establish a link with some Wi-Fi routers.
​Smooth gradients (no more 16bit banding bug) without lost of performances.
​Backlight adjusted and set to never by default (work have to be done)
​Changed volume settings and added a sound template to make it more clear.
​Replaced all Microsoft and OEM wallpapers by transparent png, so a total of 41.
​08/06 Update:​Replaced all overlaped modules of the 7392 base rom, so improve about everything​Speech recognition (long press Win key and Call contact Green key) works for every languages
​13/06 Update + 16/06 minor Update:Added direct access to Wi-Fi and Bluetooth in start menu and home tiles.
Added direct acces to Airplane mode and Brightness (16/06)
​Update of the HTC RIL manager module and added the last HTC Connection Setup for autodata config at boot.
​Added keyboard layouts but there is a limitation of 20 keyboards so I split the rom in 2.
​Added some other long press on keyboards layout ie w->www. f->ftp://ftp. (16/06)
​23/06 + 26/06 Update:Rom is rooted now (first WP7 rooted rom)
Optimisation of the policy database for root access (+live games fix) (26/06)
​Added direct acces to Cellular and Location
Added direct acces to Sound and Lock and changed all icons added to real metro theme (26/06)​Added 2 extra themes (Aero variations with transparency): Aero Black and Aero Rich​The Rom Files: v5_lang1 and v5_lang2 - These are the roms, no language pack!!! see below
Rom is split in two versions with differents keyboards layouts
In both: Spanish, French/Canada/Swiss, German, English US/UK, Italia
Lang1: Finish, Hungarian, Swedish, Czech, Danish, Dutch/Belgian, Norwegian, Polish, Poruguese/Brazilian, Filipino
Lang2: Turkish, Malay, Arabic(as Ecuador), Hebrew(as Uruguay), Farsi(as Bolivia), Chinese, Greek, Korean, Russian, Indonesian, Ukrainian, Thai(as El Salvador)​
A xap to give back the 3rd option speaker/headset in FM radio (but you'll need Headphones): ProvXml-FMradio.xap (thanks to xboxmod, for use see his thread)
A pack with all HD7 radios (files part00.bin to replace in Data.zip before flash): HD2 WP7 radios pack
If you want another hard keys remaping template see here​
If you like my work, don’t pay me a beer, don’t thank me but just send as much “MISS U” as you want to +33 682732382 (France)​
Tutorial to port sys (update to NoDo)​
Ok guys, I don’t know why DFT haven’t release an update for HD2 earlier since it take only few days to a noob to achieve a working NoDo rom. Their first version was built on a test rom with developer’s certificates from Microsoft and HTC, debug tools, recompiled drivers for HD2 and a method to build SLDR and NK sections. They had before everybody a test version of Mango too. So I suppose they, or only one, is working for HTC or has good contacts and perhaps had a commercial interest or was more interested by the exploit than giving users a great experience of WP7 on HD2, updates as soon as it’s possible and tools/knowledge to members like ervius, AnDim, Nokser etc. to achieve that by themselves. Someone in another post suggest an agreement not to release their mango before the 24th, it’s quite possible. But I don’t know and I don’t blame, it’s life lol
Perhaps we’ll see a version of Mango for HD2 soon (and new exiting videos^^’) but since a lot of people are waiting for NoDo (some desperate posts made me cry XD) I’ll give you a first version, and better, the method to achieve that by yourself for the next coming.
!The trip isn’t how to flash an HD7 rom on HD2 like certain people seems to believe and we don’t need a new malgr for the moment!
What you need:
DSM editor by Ervius http://forum.xda-developers.com/showthread.php?t=523139
WP7 Rom Tools by AnDim http://forum.xda-developers.com/showthread.php?t=884239
IMGFSFromDump-TURBO by airxtreme http://forum.xda-developers.com/showthread.php?t=610713
Imageinfo.bin, packages.cif/sof Tool by kokotas http://forum.xda-developers.com/showthread.php?t=674477
DFT rom and DWI by by bepe and Cotulla
A rom with 7392 SYS like RUU_Mozart_TMO_DE_1.32.111.01_5.65.09.25_22.45.50_ RELEASE http://forum.xda-developers.com/showthread.php?t=1065281 (MOZART is not important for SYS parts)
Some extra roms for updated other SYS languages
A rom with latests HTC packages to have the possibility of stuff like Hidden Wi-Fi like RUU_Schubert_O2_DE_3.04.207.01_Radio_5.66.09.21a_2 2.48.50.21 http://forum.xda-developers.com/showthread.php?t=1037967
Optional:
A rom for a new radio, this one seems to be the latest too
A rom for developpers tools and kitl like RUU_Schubert_hTC_Asia_SEA_WWE_1.57.728.02_Radio_5.52.09.16_22.33a.50.10_TEST
Roms for OEM APPS stuff that you want
A good HEX editor and a file/directories comparator may help a lot
Just a little time and patience lol
PS: open roms with an archive tool like 7-Zip and take the RUU_signed.nbh file, we only need this.
1. A new radio: (optional)
The radio is the part00.bin in the Data.zip
With HTCrie open the nbh which contains the radio you want, select GSM and extract the GSM.nb
Open it with an hex editor and search for 7F 45 4C 46 01 01 01 61, it’s the beginning of the part we need. The end is the series of 00 just after the last AMSS string you can find (refer to DFT part00.bin if you need help).
Keep only this section (delete the rest) and add some 00, for example if the files ends at the byte e004d0h go to e004ff.
Save the file, rename it part00.bin, you’ll have your new radio (in this case 5.66.09.21a).
Replace it in the Data.zip, you can flash now with DWI to test it.
You’ll show the new version in the Settings/About of WP7.
2. Change The SYS by 7392 Step 1: Common packages
With HTCrie open the nbh which contains the 7392 SYS build (or another you want), extend OS/IMGFS and select SYS. Extract it to a folder.
Do the same for other rom(s) containing extra languages in another folder.
Add the extra *_LANG_0XXX packages from the second directory to the first, after that you can delete it (the second folder lol, if only English was my native language^^).
You can use NabSync and NabSync_Lang_0XXX packages or not, if not delete them, just remember you’ll not need to add MOS entries in default.hv in this case.
Put the metadata package in another place, we’ll use it in step 2.
Put the content of all other packages in a new folder (for ex called IMGFS), with HTCRIE open the same 7392 rom, extend OS and in IMGFS content select .ROM and .VM modules, extract them in your IMGFS folder.
It’s your new SYS.
You could past/overwrite it in DFT IMGFS and build the rom now it will function (the DFT video of March) and YES it’s as simple as that, you’ll have new stuff from NoDo like copy/paste but not the possibility of Hidden Wi-Fi since it depend of OEM packages.
PS: It’s possible since there isn’t many changes in NK and SLDR sections made by NoDo, so we can use like that. dsm files are not very important (just to have good references of packages) and rgu content is added in default.hv
Modules that need to be updated are:
NK: cachefilt.dll, hd.dll and osaxst0.dll
SLDR: exfat.dll, filesys.dll, k.coredll.dll, k.fatutil.dll, kernel.dll, mtpuldrsvc.dll, pm.dll, sdbus.dll, sdmemory.dll and unifiedblock.dll
3. Change The SYS by 7392 Step 2: metadata package
With HTCrie extract the metadata package of the SHUBERT rom which contains OEM that you need, so we have to play with 3 metadata packages: DFT, SHUBERT OEM, MOZART SYS.
It could be a little simpler if we have a 7392 rom for SHUBERT but not for the moment.
Some files need to be updated, first is BasePolicy.xml, compare the new content of MOZART with DFT one, same for SCHUBERT (replace C:\WM700\release\LEO and C:\WM700_7392\release\MOZART by C:\WM700_7392\release\SCHUBERT). If you find new entries and you judge them useful (refer to dsm and find the package) then add them in MOZART one (it’s the most important for SYS).
Second is DefaultCerts.dat, these files contain certificates. In hex each one begin with 30 82 ?? ?? 30 82 so you can cut this file in x parts, one for each certificate.
The common build is Microsoft root, oem roots, Microsoft Windows Mobile PCA0, oem, Microsoft Mobile Device Unprivileged PCA0.
We’ll keep DFT one as bas as it’s include Qualcomm infrastructure development, Microsoft Corporation CE Image Update Test and HTC_Develop_Test, useful for later (we never know^^). DFT has included HTC_Develop_Test twice (like in dsm beside Microsoft Corporation CE Image Update Test) so you can remove the second.
What you need is to take DefaultCerts.dat from other metadata packages, extract OEM 168 or/and OEM 169 (personally I’ve included both from other roms so I’ll never have to touch this file again) and insert oem/oem root certificates in DFT one.
packages.cif and packages.sof are certainly updated but you can edit them with Imageinfo.bin, packages.cif/sof Tool.
Compare the imginf.txt you obtain for each roms you use (you can sort this file to make it more simple).
Like with BasePolicy.xml, if there is an entry that you judge useful, just add it in packages.cif and .sof (refer to this tool’s post in forum to know how use it well, but it’s quite simple).
The last two files but more important are default.hv and user.hv
To edit them just drag them onto HVEdit.exe by AnDim, you’ll obtain default.hvm and user.hvm which can be edited like rgu files.
To rebuild hv just drag hvm onto HVEdit.exe
I suggest keep the 7392 ones as base, compare them with DFT originals and modify entries you want.
For some you need a little knowledge (refer to forum) but for most it’s language entries and some tweaks.
You can refer to rgu files which differ and take a look at NoDo and 7392 pku to know which files/rgu are concerned (see forum to know how obtain pku for each zune update and extract them but don’t use files as they are in your build since most of them are not suitable (except dsm), they only contain information to update files/modules)
You can add for exemple your LiveID useful for HD2 users:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\GwpCPC]
"ActivationCode"="77777-77777-77777-77777-77777"
Copy the content of the new metadata package in your IMGFS folder. Now you have a fully functional SYS that you can use instead DFT one Let see OEM packages.
4. Change OEM packages Step 1: common packages
With HTCrie extract in two folders (like for SYS before) the OEM packages, one for DFT (for most you’ll find them at the wrong place: in SYS - like for most of TEST roms you can find) the other for the rom with most updated HTC packages.
You don’t need HTC_8x50_OS_UI_LEO as we replace it by HTC_8x50_OS_UI_SCHUBERT
You don’t need StartKitl and kitl.dll from DFT as it’s debug tool (we’ll see later) and HTC_CSPOSDrivers is new stuff so don’t search it in DFT rom.
Other packages which can be used without modification beside HTC_CSPOSDrivers are CSConn_DB, HTC_Global_Customization, OEM_8x50_BLDR, OEM_8x50_BSP, OEM_8x50_LOGO, OEM_8x50_MODEM, QC_8x50_OS_MM_CFG_2 so just delete them like for HTC_8x50_OS_UI_LEO in DFT folder to see more clearly.
5. Change OEM packages Step 2: updated packages
Like I’ve said we could use DFT OEM packages as they are but we won’t have new stuff from HTC like Hidden Wi-Fi. So we have to update some modules.
We could update the most of them (certain drivers are HD2 specific) but since we can’t update NK/SLDR sections for now you’ll got some troubles (I’ll speak of that later).
So for each package we change all files,rgu and dsm but we have to keep some modules from DFT.
For HTC_AppDrivers and HTC_OSDrivers don’t keep anything (so delete them from DFT folder) but remove HTCConnectionSetUp.dll since it is in SLDR and have some dependencies so you’ve got some troubles to connect secure wifi networks.
For HTC_8x50_OS_UI_COMMON, OEM_8x50_OS, QC_8x50_OS_GPS, QC_8x50_OS_MMRIL overwrite all modules with DFT ones
For HTC_8x50_OS_WIRELESS overwrite all modules. wl_server_serial.dll and wlan_oem.dll were files, we need updated ones in modules from new oem package for HTC Hidden Wi-Fi, the other thing to do is to verify in default.hv that BtOem, RSS and WLANOEM entries are in HKEY_LOCAL_MACHINE\Drivers\BuiltIn\ sections like in new roms and not in HKEY_LOCAL_MACHINE\Services\ like DFT’s one (and never both) otherwise it won’t work.
For OEM_8x50_OS_CAMERA replace modules and add camerasettingsmanifest.0XXX.xml from DFT in new one (since these files are normally in SLDR in new roms we have to add them). Use DSM editor to edit c6158f86-ef71-4a8b-8c04-0cf57c158b2f.dsm and add entries for these files (refer to this tool’s post to know how use it but it’s easy too).
For OEM_8x50_OS_SURF replace all modules. But you don’t have to add Backlightmdd_htc_6541.dll, just be sure you have backlightmdd.dll instead in default.hv like in new roms.
For QC_8x50_OS replace modules. You have to delete windiag.dll or verify in default.hv that “dll”=”windiag.dll” is replaced by “dll”=”” like in new roms.
6. Change OEM packages Step 3: extra packages (optional)
HTC_OEMAPPS contain OEM software.
You can add from different roms and operators. Just add the *.xap and * _License.xml you want, edit mpap_HTC_MASD_01.provxml to add/have only entries for these files and use DSM editor to edit 47c557c0-08b2-493c-a380-08c72d78e3ba.dsm and update the list of files in this package.
operatorpkg contain the HTC or Operator personalization files. Like for OEMAPPS, keep/add what you want from different roms, Email accounts/providers, Browser favorites are useful, MNS_Cust_xxx too, I’ve personally built a new theme with transparency called Aero, added the entries in the default.hv and add the 02XX*.xaml in this package.
A picture with transparency in png format for the lockscreen too.
After use DSM editor to edit 438abf0c-b691-4259-a742-1f224fa3b5ba.dsm like before.
You can add developer stuff/kitl and HTC tools packages too: AutoDeviceConfig, CommsDogfood, CoreOSDogfood, dogfoodDM, EtwChannelDefaultInternal, KitlShell, LoaderVerifierTestCerts, NetDrvVMINI, QC_8x50_OS_TEST, SensorView, SirepForPlatDev, StartKitl, TouchTools. GPSxxx from HTC_8x50_OS_WIRELESS.
Extract them from a test rom and add the content and entries in default.hv you find in rgu files.
HTC_TEST tools are xap files: DebugFlagEdit, GCFSettings, HTC BATTERY TOOL, HTCGPSTool, RegisterEdit, StopWatch, StressTool, USBModeSwitch. Refer you at the HTC_OEMAPPS explanations.
You have finished the job with OEM part, just extract the content of each of these packages in your IMGFS folder.
7. Wi-Fi problems: (optional)
Some people had some troubles with the old roms and wifi. In forum most were speaking about the SD-card but it didn’t solved the problem (and gone back to android^^).
It’s not the only problem. If you examine the file nvram.txt which is used to enable the built-in wifi chip there are some differences between files from DFT, HD2 3.14, SCHUBERT operators.
EDIT: macaddr=00:11:22:33:44:55 in its file seems the place to put a mac adress for routers with some mac filters.
I list it below, so i use a mix from HD2. When I was using the original, I didn't reached secured networks, I had to remove battery for hours.
Code:
DFT: SCH:TMOUS/WWE/TIM/O2UK HD2 3.14: SCH:Orange + MOZ:O2UK
boardrev=0x32 boardrev=0x36 boardrev=0x32 boardrev=0x36
pa0b0=5747 pa0b0=6003,6003,5576 pa0b0=6003 pa0b0=5552
pa0b1=64128 pa0b1=64086,64086,64172 pa0b1=64086 pa0b1=64245
pa0b2=65195 pa0b2=65195,65195,65155 pa0b2=65195 pa0b2=65200
pa0maxpwr=72 pa0maxpwr=82 pa0maxpwr=72 pa0maxpwr=78
opo=20 opo=16
ofdmpo=0xAAAAAAAA ofdmpo=0xAAAAAAAA
mcs2gpo0=0x6666 mcs2gpo0=0xAAAA mcs2gpo0=0x6666 mcs2gpo0=0xCCCC
mcs2gpo1=0x6666 mcs2gpo1=0xAAAA mcs2gpo1=0x6666 mcs2gpo1=0xCCCC
rssismf2g=0xa rssismf2g=0xa,0xa,0xa rssismf2g=0xa rssismf2g=0xa,0xa,0xa
rssismc2g=0xb rssismc2g=0xb,0xb,0xa rssismc2g=0xb rssismc2g=0xb,0xb,0xa
rssisav2g=0x3 rssisav2g=0x3,0x3,0x3 rssisav2g=0x3 rssisav2g=0x3,0x3,0x3
rcal_flag=0x61 rcal_flag=0x61
rxpo2g=2 rxpo2g=1 rxpo2g=2 rxpo2g=0
rxpo2gchnflg=0x1c00
btc_params6=20 btc_params6=20
I suggest to modify this entries in default.hv too
Code:
HKEY_LOCAL_MACHINE\Comm\BCMSDDHD1\Parms
"11nModeDisable"=dword:0 ; Wifi n
"PowerSaveMode"=dword:0 ; 0: Best Performance 1: Best Batterry 2: Between
"IBSSMode"="0" ; set the connection type in an ad hoc network (b/g)
"LegacyPowerCycle"=dword:0 ; new rom entry
"FrameBursting"="1" ; communication protocol (higher data transfer throughput)
8. Build your rom:
All this process can be found in the forum for more explanations:
Rename the your IMGFS folder to dump (yes you could have done it at the beginning^^) with HTCrie open the part04.bin from DFT you find in Data.zip, select IMGFS and extract IMGFS.bin
With ImgfsFromDump recompile the new IMGFS, the command line is: ImgfsFromDump imgfs.bin imgfs-out.bin
With HTCrie replace the IMGFS in part4.bin: select IMGFS, click on add files, choose imgfs-out.bin, it take only few seconds.
Replace part04.bin in Data.zip by the new one and flash it with DWI, you’ve got it!
If you like my work, don’t pay me a beer, don’t thank me but just send as much “MISS U” as you want to +33 682732382 (France)​
26/06 working great for me!
No issues other than the usual bugs!
To increase the speed, download Advanced Config Tool here: http://forum.touchxperience.com/viewtopic.php?f=11&t=890 and then in the "tweaks' section, check 'Don't dehydrate apps on pause' and UNckeck 'Enable Wi-Fi 802.11n Mode' or wifi won't work. (may or may not work, try not to fiddle with the settings too much )
Mango next !!
** also reserved for future comments *** =D
oh man. what have u done!! ;-)
waiting for the link.
GOD!!!
U are the ONE!!!!
Waiting for your link...
waiting on link too.
btw what do you mean send "Miss U" to the number?
Hope this brings out others to provide custom WP7 roms.
Hi YukiXDA,
I don't think you are a "noob" by any stretch of imagination.
I must admit most of it is too intimidating for me to even think of attempting. so I will, like I'm sure a lot of other users, will be waiting patiently for you to upload the ROM.
If I understand the last part right - All I would need to do to update my phone to NoDo is flash your updated ROM using DWI, isn't it?
Not noob but I begun from scratch lol
Imagination and thinking it's possible without DFT tools and new malgr. I regret the fact that there isn't a groupware at xda to achieve such of things (and a way to update SLDR/NK) since some guys have a lot of knowledge here. I hadn't but I didn't understand and not like that we are all waiting DFT tools and release as they have it from several months. So I tried ^^
Yes I've put my Data.zip beside DWI, same way as before for now
Remeber it's a first test version, we need reports...
It's uploaded
@thebranded:
I hope It 'll encourage other people to develop more WP7 stuff on HD2 too.
The problem of updating XIP is for any phones not just ours. But new drivers for future updates yes.
"btw what do you mean send "Miss U" to the number? " -> Just send a sms with "MISS U" as text (for my private life^^)
you are a fake foreigner,bie lai zhe tao le,tao bu chu shen me dongxi chu lai de。
hi XD(XD应该是国语?)
shen ma de fu yun a
神马都是浮云,鉴定完毕!
B!ueice said:
假洋鬼子,就别来这套了,到处乱喷,没人会理你的。
Click to expand...
Click to collapse
支持B!ueice,有本事的也建個論壇搞個直刷讓全世界人看看,別只是說這不好那不好的,這顯得你很沒本事。
這到底是神馬??跟神馬???
downloading now.
hey YukiXDA. what about u'r device? everything working good?
i'll test and report back.
Is this the real deal? Gotta get home & try this out. Anybody tried it yet?
Sent from my HD2 using XDA Windows Phone 7 App
JonnieLasVegas said:
Is this the real deal? Gotta get home & try this out. Anybody tried it yet?
Sent from my HD2 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Just installed now - only just got started and i don't have a code for sign in, so cant test live etc but so far looking good.
Says version is 7.0.7392.0.
Copy and paste is available and working..
wifi working...
....
It DOES appear to be unlocked - tried installing apps with toms XAP installer..
Says it fails after a while-but checked phone and app is on phone and working
this ROM
Hi,
I got an questions ?
1. How fast is this ROM ?
2. Is this ROM unlocked + prevented to lock again ?
3. Did you fix the green/yellow color after shot with flash ?
Thanks a for info and good work !

Categories

Resources