Database Info

Provxml file?

Do changes (registry) made to the provxml files override the settings (registry) in the default.hv? I am wondering if it is easier to just make changes to the provxml files insead of going into the default.hv file and making the changes there. Are there any downsides to editing the rom this way? Thanks again

One downside is that some setting implimented with provxml files require a reset before they take effect. Anything that would need a reset if you chenged it using a Reg Editor will be like this. Good example is the Tilt Keyboard fix.
Personally I prefer to edit the rgu files.
My experience tells me that changes happen in the order:
rgu files in SYS Folders
Then
rgu files in OEM Folders
Are combined to build your initial registry.
Finally provxml file changes are applied...
Adding Registry Keys/Settings to the rgu file in OEMMisc is usually a good place. If the Key doesn't exist simply add it to that file.

Yes, they do. No downsides really but I tend to use the hive unless there's an existing provxml that overrides a default setting (such as rom version).

..........................

............................................

.....................................

excellent work as always, thanks a lot!

Nice. Make as many options as there can be.

email settings
very nice, just installed so far so good. installed my cabs no problem, instruction to do this are pretty clear.
i have been reading about UC from slueth on how it install my setting for my email, not having much luck understanding, got it to install my cabs no problem. next i am trying to learn how to copy my email settings, i dont know if this can be done with this program? and if you can help me do this, its only 1 email account pop3 so not much info.
thanks
Lupe

Sounds cool, in fact, I liked it the first time, When it was UC. Just kidding I had to say it, just had to. I look forward to giving this a go when I have a moment.

JimmyMcGee said:
Sounds cool, in fact, I liked it the first time, When it was UC. Just kidding I had to say it, just had to. I look forward to giving this a go when I have a moment.
Click to expand...
Click to collapse
Thanks...I think
Let me take this opportunity however to say a couple of things about UC, and specifically how this tool is really for a different purpose.
First off, although UC is a nice standard, even Sleuth acknowledges that there is really nothing new in what he is doing with UC. He took some standard autorun.exe techniques and registry entries and bundled them to make a procedure that used to take 3 or 4 steps now take 2. UC adds nothing new, other than a standardized way to use autorun.
Also, UC mainly is meant for fully automated installs of a storage card. So, you pop your card in the slot, and sdautorun processes the sdconfig.txt automatically. UC can install CABs, provision XML and copy files (with limited success). However you must first set up your sdconfig.txt file and build your XML files manually or by exporting registry keys. You must set all this up beforehand in the sdconfig file.
SASHIMI takes a different approach in that you don't need to set up a config.txt file and it isn't bound to statically install the same things each time. In addition, since it can import reg keys natively (well, technically it calls another included app to do it, but it's all bundled in the installer) you don't need to go through the hassle of exporting reg keys, and then converting them to .XML (and optionally rolling them into a .CAB file).
Other advantages SASHIMI has:
In addition to running fully automated, you can choose to run only Manual, or Manual+Auto which will allow you each time to be prompted with a set of CABs and .REG files which you wish to install.
Customizing .CAB installs by tethering/binding .REG and .MSCR files so you can easily map additional configuration entries to a particular .CAB
Logging, so you can track what has been done
Transfer entire directory structure. If you have several folders with multiple subfolders you want transfered from storage you can do this easily.
Modular - the multiple directory structure allows for nice compartamentalization and organization of applications and configuration settings. Things aren't stored in static config.txt files or difficult XML. Simple .REG files, CABS, and optionally MortScript files if you want to use them.
All of these benefits come with only one drawback, which is inherent in this technique. That is it may not be fully automated. Of course this makes sense because if you want to be prompted about which CABs you want to set up or where you want to install them, you need to invest a little time answering prompts. I think the time to do this is considerably less than creating a config.txt file.
In addition, SASHIMI can be run using only Auto mode, in which case it is fully automated (and logged). In fact, it can even be configured to be run automatically when the SD card is put in if you so choose (I will be writing up instructions for that).
So, it really depends what you want to do. I honestly feel that SASHIMI can do everything autorun (and thus UC) can do and more. The exception is it can't import XML. I may update this by including autorun in the package and build this feature in as well. Personally, I think it's easier to work with .REG than .XML. UC however, has a slightly simpler structure which of course why it isn't as feature rich. I think it lends itself more to it's main purpose...which is to be cooked into ROMs and do a fully automated install at boot.
However, as the name implies, SASHIMI is a RAW installer and is meant more for users who want full control of what is getting installed (generally users who use lighter, uncooked ROMs and want to install more apps, etc.
Although, as I said everyone can use it. I think you really need to download it and run through the tutorial to see the power it has.
thx!

Awesome!!!!!! Been following your dev work on this and I should say this is a really great new level you've taken this package!!!!

Gonanaaa try this!

Thanks for this
Sashimi works great. You did a marvelous job of documenting it. Follow the directions and you have an easy solution for us flashing junkies....Bravo!

parleyp said:
Sashimi works great. You did a marvelous job of documenting it. Follow the directions and you have an easy solution for us flashing junkies....Bravo!
Click to expand...
Click to collapse
Thanks for your support.
Please feel free to make suggestions/bug reports/feature enhancements.
I couldn't think of anything else it needed at the time, but I'm sure it's not perfect.
On my list so far is:
Add support to use XML provisioning files (in addition to REG). - Not sure if I will put this in both Manual AND Auto modes...thinking maybe just Auto.
Writeup instructions, and maybe a little update that shows/updates the program to run in UC/Autorun mode. - This will allow it to run in auto mode as soon as the SD card is placed in the device (or a new device is started for the first time with the SD in the slot).
Integrate a config.txt / sdconfig.txt file so those of you who run UC can easily move/switch between both apps. Basically the idea is SASHIMI will process the config.txt file in addition to what it already does. It is kind of repetitive, since then you would be able to either import an XML through my methods, or just put your XML/CPY/EXEC commands in the config.txt file. Obviously if you ONLY use config/sdconfig.txt then there really isn't a need to use SASHIMI too, but if you want the extra options while still maintaining any work you did with UC then it's a go!
I would like to try to keep the app aroung it's central purpose, which is as an installer automater/helper app...so try to keep suggestions/recommendations around that.
thanks

better than uc, imho
thanks for you help bengalih, from your other thread, got my emails set up,
i used tiermanns Personal OEMizer to create my provisioning XML.
i then used the task manager you provided and bam, it worked.
this is why i believe SASHIMI is the best choice. i flash many roms, not all roms have the same programs installed, when i use uc i have to change my config.txt or i might install something that is already in the rom or i might miss something that is not in the rom. yea yea i know, cry me a river
heres what i like, i put my stuff in auto file, like my spb mobile, spb weather and a few others that no one installs because they must be purchased, then all my others in the "manual file" stuff like pcm keyboard, rss hub, htc end key, etc and google search which makes you stop and accept user agreement, if i have something in the manual file thats already installed in the rom you just flashed, just click no when it gets to it and on to the next cab.
i believe with sleuths uc if a cab requires a reboot it cant be used, for example i can put spb phone suite in manual and once completed it ask if i want to reboot, i select no and now it goes to the next cab, once im done with the cabs i want to install then i reboot very very nice
thanks
Lupe

overhaulengines said:
thanks for you help bengalih, from your other thread, got my emails set up,
i used tiermanns Personal OEMizer to create my provisioning XML.
i then used the task manager you provided and bam, it worked.
this is why i believe SASHIMI is the best choice. ...
Click to expand...
Click to collapse
Thanks Lupe...glad you got it worked out.
I am finishing up the next version, which will incorporate UC as well, so if users have an sdconfig.txt file they want to use it can also be used by SASHIMI (in reality I am calling UC's SDAutorun.exe to do it). So, it will be like a combined installer.
There still isn't a substitute for UC in terms of cooking it into a ROM to run automatically on first boot, but with my next version you will be able to use the sdconfig.txt and you will also be able to initiaze SASHIMI when the storage card is inserted. This makes it ideal if you need to provision alot of phones and each one is slightly different.
It sounds like you are taking advantage of the manual+auto install...great. FYI if a .CAB is already unstalled, then the following will happen:
1) If in Manual mode, it will ask you to remove the old CAB first and then it will ask you the location to install the new one. Of course you can always skip the CAB in manual mode if you don't want to reinstall.
2) If in Auto mode it will automatically remove the CAB and install it again.
Ah, one last thing...the Task Manager is DotFred's task manager, I can't take the credit for that application, and I will be sure to credit him in the next release notes.

Version 3.0 coming soon.
I'm finishing up version 3.0 to be release by end of week.
Here are the following updates:
v.3.0
- XML integration added! Use XMLs with/instead of .REG files to provision your device.
- UC integration and the ability to use sdconfig.txt files.
- Option to auto-launch when Storage Card is inserted.
- Better Log handling and INTEGRATED log viewer.
- Additional menus for less clutter and more choices!
- More status dialogs to let you know what's happening when.
- Ability to create/restore Program Menu shortcuts to any location.
- \Scripts and \Root directories available in both Auto and Manual modes for more control!
- Moved tandem/bundled .REG processing before .CAB installation for the ability to import registry entries prior to application install. .MSCR and .XML tandem files process after .CAB installation.
- Optimized code formatting
Let me know if there are additional options you would like to see.

Does the SDConfig.txt file use eliminate the ability to use the programs default folder based way of separating and installing? The program is excellent as is. But if I were shooting for the moon I would suggest adding ability to export personal information to .XML or .REG from current device for use after flash...

aadadams said:
Does the SDConfig.txt file use eliminate the ability to use the programs default folder based way of separating and installing? The program is excellent as is. But if I were shooting for the moon I would suggest adding ability to export personal information to .XML or .REG from current device for use after flash...
Click to expand...
Click to collapse
I completely agree with this. If you were able to have the tool create the .xml and/or .reg files from your currently installed ROM, it would make an excellent tool a killer app.
Thanks for the work!

aadadams said:
Does the SDConfig.txt file use eliminate the ability to use the programs default folder based way of separating and installing? The program is excellent as is. But if I were shooting for the moon I would suggest adding ability to export personal information to .XML or .REG from current device for use after flash...
Click to expand...
Click to collapse
No, the SDConfig.txt file is an ADDITIONAL step in the Auto phase.
So, after running either the Auto, or Manual+Auto modes the last step will be to process an SDConfig.txt file if it exists AND the option to use UC is enabled within SASHIMI.
I think that answers your question.
I did also add the option to do a backup of the entire registry to a file. But, your suggestion gives me an idea....
I can't really provide an interface with MortScript to do a selective backup of the registry, but what I may be able to do is read another configuration file. So, the user would create a file with the following format:
HKCU\Settings\Phone Settings\
HKLM\Control Panel\Sounds\
HKLM\Software\Application1\
Click to expand...
Click to collapse
Whatever keys are listed in the entries will be written out to a .REG file in the Manual\Reg directory and can then be imported if desired or moved to Auto\Reg.
Would that suffice for what you are asking?

That, my friend, would be EXCELLENT! This is an awesome application! Keep up the good work!

Thanks for everything, sir. I cannot wait to try this out.

Ok, I have implemented all the above features.
I just need to do a bit more testing and then repackage the .CAB and update the documentation.
Unless i get anymore feature requests/bug reports I will be upping this probably by Friday.
If any new feature requests are too complex (but worth doing) they may wait until next version.

where i can get all registry of lastest mango

I want to find something in registry of mango that mean to font of OS.
there is something Different to nodo that make my native language not work in some place.
I'm looking for it so i need all registry of mango.
if some one have plz send me one. Thank you.

View Single Post

Have another Thanks from me for this, man... let me find some very useful things.
BTW, the XML file in the CAB appears to be standard provxml format; I just opened it in notepad, copied the pieces I wanted into another file, made a few changes, renamed it CustClear.provxml, and loaded it with Connection Setup. Worked great!

Thank you. drkfngthdragnlrd

@drkfngthdragnlrd
Is this registry pulled from your phone or from a cooked ROM you flashed? Is there a way to dump the registry from a Mango phone itself? Thanks

LiFePo4 said:
@drkfngthdragnlrd
Is this registry pulled from your phone or from a cooked ROM you flashed? Is there a way to dump the registry from a Mango phone itself? Thanks
Click to expand...
Click to collapse
They were from my phone. I had a stock ROM & upgraded to 7720.68 via the leaked method here on XDA. I than, copied out all the RGU's in \Windows\ of my phone. I merged all these RGU's into 1 large file & imported it into WinCE CAB Manager. Being as they are RGU's this is not the full registry. There are some values that aren't written till after first boot/run by the executables of WP7. I'd say this CAB is 90+% of all the registry.

drkfngthdragnlrd said:
They were from my phone. I had a stock ROM & upgraded to 7720.68 via the leaked method here on XDA. I than, copied out all the RGU's in \Windows\ of my phone. I merged all these RGU's into 1 large file & imported it into WinCE CAB Manager. Being as they are RGU's this is not the full registry. There are some values that aren't written till after first boot/run by the executables of WP7. I'd say this CAB is 90+% of all the registry.
Click to expand...
Click to collapse
Excellent! Another question; I am really after my exchange activesync registry keys; do you know if these are in any of the RGU files (I am thinking not)? When you add an account (be it POP3, IMAP4, EAS) does this get generated with an RGU that is accessible?
P.S. I have been using the 30day demo of WinCE CAB Manager and love how it shows the tree structure of your file. Was there any particular trick to merging the RGUs?

LiFePo4 said:
Excellent! Another question; I am really after my exchange activesync registry keys; do you know if these are in any of the RGU files (I am thinking not)? When you add an account (be it POP3, IMAP4, EAS) does this get generated with an RGU that is accessible?
P.S. I have been using the 30day demo of WinCE CAB Manager and love how it shows the tree structure of your file. Was there any particular trick to merging the RGUs?
Click to expand...
Click to collapse
I'm not sure about the Active sync thing. I'd assume they get written once you set up your email accounts. You could look, I have no clue of the top of my head, not something I looked into.
As for merging the RGU's, I used Visual Studio, but you can use any text editor to open them. My only suggestion is to pay close attention & make sure you copy & paste correctly. Also, you only need the first line "REGEDIT 4.0 or something like that once. So don't copy the extra entries from the other RGU's.

drkfngthdragnlrd said:
As for merging the RGU's, I used Visual Studio, but you can use any text editor to open them. My only suggestion is to pay close attention & make sure you copy & paste correctly. Also, you only need the first line "REGEDIT 4.0 or something like that once. So don't copy the extra entries from the other RGU's.
Click to expand...
Click to collapse
I copied all .rgu from my phone to my PC, renamed them all to .reg, and then used WinCE CAB Manager to import each one and presto, I have a nice registry and viewer (then just save as a CAB project)!

LiFePo4 said:
I copied all .rgu from my phone to my PC, renamed them all to .reg, and then used WinCE CAB Manager to import each one and presto, I have a nice registry and viewer (then just save as a CAB project)!
Click to expand...
Click to collapse
Yeah, it's nice to have a use for WinCE CAB Manager in WP7 as it's no longer useful for creating CAB's that are installable.

@drkfngthdragnlrd - I did this on NoDo for a start (easy to get RGU to PC) but how did you go about it in Mango? I was reading along in the other thread where there were discussions about this but nothing clearly stated.

LiFePo4 said:
@drkfngthdragnlrd - I did this on NoDo for a start (easy to get RGU to PC) but how did you go about it in Mango? I was reading along in the other thread where there were discussions about this but nothing clearly stated.
Click to expand...
Click to collapse
I used TouchXplorer to copy the files into an app's Isolated Store & than used [APP 2011-08-20][BETA] WP7AppBackup - Backup / Restore third party app data to back-up the app data. Than you just look inside the back-up files.

[Q] Cannot access registry anymore after accentcolor change

Hey there,
I got a Samsung Omnia 7 with Telekom Branding and a serious problem. I cannot access the registry of my phone anymore with any tool. WP7 Root tools and the registry editor from TouchXperience keeps crashing.
What I been doing is trying to add a new accent color.
I first went to [HKEY_LOCAL_MACHINE\ControlPanel\Themes] and then in the folder which contains the theme names. I have created there a correct Dword entry and called the name "grau".
Well, then I switched into [HKEY_LOCAL_MACHINE\ControlPanel\Themes\0\Accents] and wanted to add there another accent color with the index number 11. I was looking for the hex values on my PC while my phone screen got locked.
After unlocking it again, I couldnt access any of the tools anymore.
Also when I go into the control panel -> design (where you can choose light/dark background and accent color) it just kicks me out of the menu.
I dont know what I should do, I need something which lets me access the registry somehow or an app which could remove the key...
Any help is greatly appreciated

You can do write-only registry operations in a few ways, but one of the easiest is to use provxml. Download the Interop Unlock XAP from the Dev&Hacking sub-forum and open it in 7-zip (the built-in Windows ZIP explorer won't work for this). There's a .. folder. Navigate it up to ..\..\..\..\.. or so, then there's a provxml folder. Open it, and there's a file inside. Edit that file. It'll have some registry write commands in an xml format (wap-provisioning, you can read about it on MSDN if you want). Put the registry commands you want into the file and save it back into the XAP archive. Then, follow the normal steps for interop-unlock on a Samsung phone, except don't install the original app (deploy your modified version). This will process the provxml and make the registry changes.
Note: provxml can be used to delete registry values as well as create or modify them. This is a great way to undo partial jobs like adding a new theme that isn't supposed to be there.

Thanks a lot for your reply.
It worked out. I removed all those broken keys.
I had done loads of registry changes and a bunch of tweaks for the phone, at the end I did a hard reset.
I'll wait for tools the next time

xap deployment mechanism?

Hello everyone,
I'm new to wp7 and wince. I want to know what happened when I deploy a xap to my wp7 phone. Because my phone has not been unlocked, I could not see files on the phone. How about the XML files in the xap? Where do they go? If there are any registry values that will be changed? Thanks.

Roughly speaking, the process goes like this (I might have the order wrong in a few steps, this is based on observation not reverse engineering):
First, the phone verifies that installing unsigned apps is allowed and that you haven't hit the app limit.
Second, it unpacks the WMAppManifext.xml file from the XAP and p****s it.
Third, it checks whether the app's capabilities are allowed (in particular, if you aren't interop-unlocked, ID_CAP_INTEROPSERVICES will be prohibited).
Fourth, it copies the XAP into a temp folder (under \Application Data\<something>\GUID, I forget exactly where).
Fifth, it registers the app in the AppMgr, a database that contains info about installed apps and shows them in the app list.
Sixth, it creates a "chamber" (basically, a user account) specifically for the app, with permissions specified by the manifest CAPs.
Seventh, it creates a folder at \Applications\Install\{GUID} and one at \Applications\Data\{GUID} where GUID is the app's ProductId.
Eighth, it unpacks the XAP into that Install\{GUID} folder.
Ninth, it adds policies to the PolicyEngine (security system) that allows the app to read its install folder, read/write its data folder, and to be launched into its chamber.
Tenth, it deletes the temp folder where the app was unpacked.
The registry should not be affected during this process. Files in the XAP are unpacked onto the filesystem mostly unmodified.

GoodDayToDie said:
Roughly speaking, the process goes like this (I might have the order wrong in a few steps, this is based on observation not reverse engineering):
First, the phone verifies that installing unsigned apps is allowed and that you haven't hit the app limit.
Second, it unpacks the WMAppManifext.xml file from the XAP and p****s it.
Third, it checks whether the app's capabilities are allowed (in particular, if you aren't interop-unlocked, ID_CAP_INTEROPSERVICES will be prohibited).
Fourth, it copies the XAP into a temp folder (under \Application Data\<something>\GUID, I forget exactly where).
Fifth, it registers the app in the AppMgr, a database that contains info about installed apps and shows them in the app list.
Sixth, it creates a "chamber" (basically, a user account) specifically for the app, with permissions specified by the manifest CAPs.
Seventh, it creates a folder at \Applications\Install\{GUID} and one at \Applications\Data\{GUID} where GUID is the app's ProductId.
Eighth, it unpacks the XAP into that Install\{GUID} folder.
Ninth, it adds policies to the PolicyEngine (security system) that allows the app to read its install folder, read/write its data folder, and to be launched into its chamber.
Tenth, it deletes the temp folder where the app was unpacked.
The registry should not be affected during this process. Files in the XAP are unpacked onto the filesystem mostly unmodified.
Click to expand...
Click to collapse
Thank u for ur excellent reply! I am trying to find ways to interop unlock my nokia phone. Thanks a lot!

Good luck! I've been looking for interop-unlocks for months now (sometimes in Nokia, sometimes in other OEMs like my HTC, sometimes in the OS itself) but more people is always better. Sometimes a new perspective is all it takes.