Develop Bugs

[XAP][Source] DeployProvXMLv2.1 - Fixes self-chaining, adds diagnostics

Hi hackers,
Version 2.1 of DeployProvXML is here, and should be more robust than the previous version:
1: The CustClear.provxml file is now copied both using the filesystem DLL (like v1) and using XML provisioning (hopefully works aroudn the HTC update blocking filesystem access.
2: The CustClear.provxml file is now self-chaining. Really, this time - so long as you run the program *once*, you can even change the included CustClear.provxml, re-deploy, and run Connection Setup; your new version will then be copied to \Windows. (Re-run CS to actually process your new version). No more need to re-run DeployProvXML after each use of Connection Setup!
3. The program now contains more diagnostics. It sets a registry value at launch (using ComRegRW.DLL), changes that registry value (using provxml) when deploying the file, and changes it again when the deployed file is processed by Connection Setup (as part of the CustClear.provxml). It also checks that the value is as expected avter deploying.
REQUEST:
Anybody who has an interop-unlocked HTC phone with the latest official HTC update (meaning you can't use TouchXplorer anymore), please run this app, then run Connection Setup, then use a registry editor to check the key HKCU\Software\DeployProvXML. It should have a value, LastOperation. Please include the data in the value (or the fact that it doesn't exist) with your reports. Thank you!
Description:
Another handy little utility for people with HTC phones, this app simply copies a CustClear.provxml file from its install directory to \Windows, then exits. The idea is to make sure that you're never without at least a basic file that can be used by Connection Setup to unlock your phone. New in v2, every time you run Connection Setup, the file will automatically restore itself to the Windows directory. This ensures you'll never accidentally get caught with a locked phone after an upgrade or something!
The included Provxml has three parts. However, you can customize it however you like by opening the XAP file and editing the embedded provxml. The parts are:
1: Applies the registry settings to unlock the phone, including Interop-Unlock.
2: Applies a test value in the registry, at HKCU\Software\DeployProvXML. This value is harmless but can be used to test if the app is working.
3: Chain-copies itself from DeployProvXML's install folder into Windows again, replacing the copy that Connection Setup consumes.
Note that this program does not actaully apply the provxml, merely copies it to where Connection Setup expects to find it. It should close immediately after starting; this is not a bug. If you see a dialog box instead, something went wrong and you should report it below!
This program is only going to work on HTC phones, since it uses the HTC DLLs for provxml, file access, and registry. It is a 7.0 app but is compatible with Mango if you have Interop Unlock already.
XAP is in DeployProvxml\bin\debug. Source included for those interested.

Do you think a deployer for OMNIA 7 is possible ?
Maybe with a .dll of WP7 Root Tools ?
So users who didn´t prepare their device for our OnDevice provxml app under NoDo could also enable this feature...

contable said:
Do you think a deployer for OMNIA 7 is possible ?
Maybe with a .dll of WP7 Root Tools ?
So users who didn´t prepare their device for our OnDevice provxml app under NoDo could also enable this feature...
Click to expand...
Click to collapse
This has been solved I can finally test the app myself now. I changed the path to copy the provxml from the iso storage of the app instead of the provxml folder.

Interop.Services
Just read this http://translate.google.com/transla...oducing-windows-phone-7-5-native-programming/
Any joy?

Looks cool, but I'll need to investigate further. It has definitley been reproted that Homebrew apps without ID_CAP_INTEROPSERVICES don't work even in Mango. It sounds like this guy is maybe using a marketplace signed DLL, though? Not sure - the translation isn't great. He's working from an app that I've never explored, and that appears to be specific to the Japanese Mango phone.

how do we use it. will it permanently unlock when we update to official Mango?

Ttblondey said:
how do we use it. will it permanently unlock when we update to official Mango?
Click to expand...
Click to collapse
Install app in NoDo.
Run in once.
Upgrade to Mango.
Run the Connection Setup app (from Marketplace).
Hit "OK" in Connection Setup.
Your phone is now dev-unlocked and will not automatically relock. Additionally, you can now install Mango homebrew.
I suggest you then run DeployProXml again, since installing an update, even something like a HTC firmware update, may re-lock the phone. So long as you've run DeployProvXml since the last time you ran Connection Setup, though, you can unlock again.
If this helps, please hit Thanks!

piaqt said:
Just read this http://translate.google.com/transla...oducing-windows-phone-7-5-native-programming/
Any joy?
Click to expand...
Click to collapse
he does pretty much the same from what I read. You just use oem dll's and have some native functions to work with. f/e htc has file operations + regoperations + provxml, samsung has regoperations + provxml (trough which you can do regops). This manufacturer dll probably contains fileops as well, which is nice since there might also be a chance that there will be a working provxml method and with the fileops you can copy the provxml files to the desired location. In theory ofcourse.

Marvin_S said:
he does pretty much the same from what I read. You just use oem dll's and have some native functions to work with. f/e htc has file operations + regoperations + provxml, samsung has regoperations + provxml (trough which you can do regops). This manufacturer dll probably contains fileops as well, which is nice since there might also be a chance that there will be a working provxml method and with the fileops you can copy the provxml files to the desired location. In theory ofcourse.
Click to expand...
Click to collapse
There are two differences that are worth noting, though.
A) This is a phone that came with Mango. There was never any chance to unlock it for Mango homebrew. It blocks apps with ID_CAP_INTEROPSERVICES - something we had to work around with registry edits.
B) Related to A, he can call native code without having ID_CAP_INTEROPSERVICES. This isn't supposed to be possible at all. Makes me wonder if he's actually calling anything in the DLL or if he's just loading the COM object but not using it and calling that success.

GoodDayToDie said:
There are two differences that are worth noting, though.
A) This is a phone that came with Mango. There was never any chance to unlock it for Mango homebrew. It blocks apps with ID_CAP_INTEROPSERVICES - something we had to work around with registry edits.
B) Related to A, he can call native code without having ID_CAP_INTEROPSERVICES. This isn't supposed to be possible at all. Makes me wonder if he's actually calling anything in the DLL or if he's just loading the COM object but not using it and calling that success.
Click to expand...
Click to collapse
Ahh yeah your right. Yeah I realy wonder what the trick behind it is and if he manages to install it.
Something else I have not tried yet, but what happens if you deploy it without the id_cap and than run it. It will not work obviously, but what happens if you redeploy with the tag in? Will it still get rejected? Because the phone rejects the app I think.

Hey, the ZIP contains a folder, which, if I package into a XAP, fails on deployment. What's the best way to get this packaged into a usable XAP?

trying to figure out how to install this app.

@thesecondsfade:
Bottom line of the first post:
"XAP is in DeployProvxml\bin\debug. Source included for those interested."
I distribute most of my apps this way, unless the source is really big and the XAP alone is a significantly smaller download for some reason.
@Ttblondey:
Is your phone dev-unlocked?
Is your phone either pre-Mango, or interop-unlocked?
Do you have a XAP deployment program and the Zune software?

GoodDayToDie said:
@thesecondsfade:
Bottom line of the first post:
"XAP is in DeployProvxml\bin\debug. Source included for those interested."
I distribute most of my apps this way, unless the source is really big and the XAP alone is a significantly smaller download for some reason.
@Ttblondey:
Is your phone dev-unlocked?
Is your phone either pre-Mango, or interop-unlocked?
Do you have a XAP deployment program and the Zune software?
Click to expand...
Click to collapse
My TouchXplorer does not work anymore after updating to the official Mango, though my phone is still unlocked. This XAP will definitely helps if new firmware/updates come along to deploy Provxml to /windows.
I've installed it but how can I verify if this is being installed/copied to /windows?

GoingInside said:
My TouchXplorer does not work anymore after updating to the official Mango, though my phone is still unlocked. This XAP will definitely helps if new firmware/updates come along to deploy Provxml to /windows.
I've installed it but how can I verify if this is being installed/copied to /windows?
Click to expand...
Click to collapse
This app uses the same DLL as TouchXplorer, which means it doesn't work either (I wrote a number of apps using that DLL, including a backup tool, and none of them can see any files anymore). I'm not sure exactly what was changed, but yeah, they broke it. My hope is that Heathcliff74's WP7 Root Tools will restore file browsing on HTC soon.
As soon as I finish restoring my phone, I'll try writing a version of the app that uses ProvXML to copy the file, instead of ComFileRW.dll (which no longer works if you get the final HTC update). Using ProvXML is limited in some ways - you can't browse the filesystem, for example - but it works great for this type of operation.

i'm on force unlock from Ansar's thread with Pedbe way final mango.Been trying to use advancedconfig 1.3,1.4 battery meter it don't work anymore.Good thing I can sideload(that's important)

GoodDayToDie said:
This app uses the same DLL as TouchXplorer, which means it doesn't work either (I wrote a number of apps using that DLL, including a backup tool, and none of them can see any files anymore). I'm not sure exactly what was changed, but yeah, they broke it. My hope is that Heathcliff74's WP7 Root Tools will restore file browsing on HTC soon.
As soon as I finish restoring my phone, I'll try writing a version of the app that uses ProvXML to copy the file, instead of ComFileRW.dll (which no longer works if you get the final HTC update). Using ProvXML is limited in some ways - you can't browse the filesystem, for example - but it works great for this type of operation.
Click to expand...
Click to collapse
Ok, guess I'll have to wait for the experts (Heathcliff74 and you etc) to solve this HTC drive update issue. Thank you!

GoingInside said:
Ok, guess I'll have to wait for the experts (Heathcliff74 and you etc) to solve this HTC drive update issue. Thank you!
Click to expand...
Click to collapse
@GoingInside, and anybody else in the same boat (latest HTC update installed, filesystem browsing broken), please try the latest version (v2, now on the initial post)! After running the app once, run Connection Setup and hit OK. After you do that, use a Registry Editor to check for the presence of the following registry key: HKCU\Software\DeployProvXML.
Please report whether that key is present. If it is, that means the app is fully functional even with the latest update!

I only have a NoDo Backup (my phone came with nodo) - can I get the interop unlock trough dev unlocking the phone and then running our app?
nvm, I am now downgrading to NoDo and Will then update to the HTC RTM (the one that Comes via zune). As soon as I am there I will tell you if i had luck with it or not (I hope I can interopunlock on NoDo as the 3 apps sideloadlimit is crap)
Update 1: I am on NoDo and I started your app. It cloesd, i went to Connection Setup and ran it. Will check if the registry value is there as soon as some XAPs are deployed (first time that I can deploy more than 3 XAPs )
Update 2: Now going trough the Beta - RTM - HTC Update Update marathon. Will Report back as soon as I am on HTC's RTM

GoodDayToDie said:
@GoingInside, and anybody else in the same boat (latest HTC update installed, filesystem browsing broken), please try the latest version (v2, now on the initial post)! After running the app once, run Connection Setup and hit OK. After you do that, use a Registry Editor to check for the presence of the following registry key: HKCU\Software\DeployProvXML.
Please report whether that key is present. If it is, that means the app is fully functional even with the latest update!
Click to expand...
Click to collapse
Unfortunately, it seems that the new XAP (v2) doesn't work as well. Copy and deploy the latest DeployProvXML.xap (dated 5/10/2011) to my HTC trophy. After running Connection Setup, I can't find the registry key: HKCU\Software\DeployProvXML. I only found MICROSOFT under HKCU/Software/.
But please continue your research into this. THANKS!

[XAP] WP7 Root Tools 0.8 for MANGO

THIS THREAD IS DISCONTINUED!
WP7 ROOT TOOLS 0.9 HAS BEEN RELEASED!
Download here: www.wp7roottools.com
Further discussion: here
__________________________________________________
With this tool you get root-access to parts of your WP7 device. This version contains a registry-editor, a file-explorer with basic file-operations and a certificate-installer with write-access to the certificate-stores.
This tool is in alpha stage. That means that it is not feature complete and it is not yet properly tested. This tool also provides you with high privileges with which you can alter low level settings and data on this device. All this may result in unexpected and undesired behavior, which may ultimately damage your device. Use this tool with care and use it at your own risk. The developer of this tool cannot be hold responsible for any kind of damages, caused directly or indirectly by using this tool.
The current version of this tool can only be used on Samsung devices. A small part of the code uses Samsung-specific functionality. The performance of the tool may sometimes be slow. This is the result of the way access to the system is elevated. The next version of WP7 Root Tools will run on more devices, like HTC and LG. Also the access is elevated more directly.
IMPORTANT NOTICE: If you get error 0x81030120 when you deploy WP7 Root Tools to your device, then please read this guide!
Your phone needs to be INTEROP-UNLOCKED. On WP7 there are already a lot of different unlocks:
Developer-uplock/ChevronWP7 unlock: This will allow you to side-load apps from your desktop to your phone. A legit developer-unlock costs $99 per year (this will also allow you to deploy your apps in the Marketplace). ChevronWP7 made an unlock tool, which allows you to dev-unlock your phone for free. This method only works on WP7 version 7.0.7004.0 and 7.0.7008.0. It does not work anymore since version 7.0.7355.0 (pre NoDo). But it is possible to unlock your phone on version 7.0.7008.0 and then use some tricks to upgrade your phone and keep the unlock. You can even upgrade to Mango RTM and still have the unlock. Look in this thead to get full instructions. Also the ChevronWP7 team will release an unlock-method that will only cost a few bucks and will apply an official dev-unlock on any version of WP7, but it won't allow you to release apps to the Marketplace.
Interop-unlock: On RTM and NoDo versions of WP7 it was possible to run apps with native code. These apps would use a COM-Interop-Bridge to transit between managed and native code. These apps need to be tagged with the Interop-capability called "ID_CAP_INTEROPSERVICES". These apps don't seem to run on Mango. Not even when you have a legit Developer Unlock. There are two reasons for that. The first reason is that most native libraries need some modifications to run on Mango. I found out how to do this and modified WP7 Root Tools so that it is compatible with Mango. The other reason is a deployment-restriction. That is the Interop-Lock that needs to be Unlocked. If you have a normal Dev-unlock on Mango and you try to deploy an app with that uses COM interop, the deployment will fail with error 0x81030120. contable and Marvin_S found out that the MaxUnsignedApp registry-value is responsible for the Interop-Lock. I did more research and I identified the code that checks this value. In fact, if you have the MaxUnsignedApp value set to 300 or higher, your interop will be unlocked. The value of MaxUnsignedApp is determined by the type of developer-unlock you have. A normal AppHub account will have it set to 10 and a student account will have it set to 3. So a value of 300 or higher is not a realistic value for a normal developer account. It is probably only set to this value for Microsoft employees and OEM developers. Until now, the only way to do an INTEROP-UNLOCK for MANGO meant that you have to downgrade to NoDo first, then prepare your device by loading provxml files to your device, upgrade to MANGO and then use OEM tools to execute the provxml files and do the necessary unlocks. But that is a lot of work and for some devices not even possible, because there are simply no ROM's available. But I have found an exploit that works on Samsung and HTC devices, which allows you to UNLOCK INTEROP your MANGO device. For it to work, it must already be developer-unlocked! Read this guide for instructions.
FullUnlock: This a type of unlock which allows you to run Native Executables. Normally you can only compile Silverlight apps, which will be run in a sandbox. The app is compiled as a DLL, which will be run in TaskHost.exe. I you would like to compile Test.exe, you won't be able to run it, because there is a policy-system and certificate-system that prevent you from running it. Cotulla already cooked a ROM with FullUnlock, but unfortunately this is not yet working as expected. I also did research on this together with fiinix. Thanks go out to him for working with me on that matter. We did not get it working back then, but I think I now have enough exploits to get this working. I will do some more testing on this later on. WP7 Root Tools does not need FullUnlock to be able to run.
Full Root Access: As stated previously, Silverlight apps and system executables have their own sandbox, which is defined by a Least Privilege based policy system. Even when you break into native code, you are still running in your sandbox. For example, you can try to copy a file in managed code. You will only have access in Isolated Store. If you use COM interop to call native code and you try to use the FileCopy() API, you can still only copy files in your Isolated Store. To break out of the sandbox, there are a couple of possible exploits. But they are still limited in their possibilities. To get unrestricted access to the API's and Resources on your device you will need to completely bypass the policies that the system has defined for your app. YukiXDA and I have in close contact with eachother for a period of time and we learned a lot from eachother. I found some of the exploits, thanks to him! YukiXDA unfortunately has left the community. A very big thanks to YukiXDA for working with me on this matter. Before he left he cooked a ROM for HTC HD2 which has Full Root Access cooked into it. The way he did it was to effectively shut down the policy-sytem. Although this opens up a lot of possibilities for homebrew, this is also kind of risky, because the system is also open to malware. And this technique only works on devices which have an unlocked bootloader (currently HTC HD2 and most HTC WP7 devices have unlocked bootloaders). I developed another type of Full Root Access. I can enable Full Root Access for the entire device (differt than what YukiXDA did, but effectively the same). But I can also enable/disable this per app. So the user can decide which app is trusted enough to get Full Root Access. Other apps will still run in their predefined sandbox. I am currently developing a new version of WP7 Root Tools which will support Full Root Access. To do this I will apply Full Root Access for WP7 Root Tools first. A user can use WP7 Root Tools to enable Full Root Access for another app. So if a developer wants to create an app that needs Full Root Access (for example some type of backup-app), the user of the app must use a ROM which has Full Root Access cooked into it, or the user must run WP7 Root Tools to allow Full Root Access for the app. There are two disadvantages. WP7 Root Tools must first install Full Root Access for itself. Obviously WP7 Root Tools does not have Full Root Access at that moment yet. So there are other exploits necessary to apply this. Currently I have exploits for this, but they use some device-specific features. I have exploits for Samsung, HTC and LG. Other brands, or possibly a device-independent exploit, may follow later. This means that WP7 Root Tools only works on these devices, and with that also the apps that need Full Root Access will only work on these devices. The other disadvantage is that, with the current state of Interop-unlocking, all users of WP7 Root Tools, and with that also all users of the apps that need Full Root Access, will need to be on dev-unlocked-NoDo first, in order to apply an Interop-Unlock for Mango. Because WP7 Root Tools and all apps that use Full Root Access need Interop Unlock. When I have the version of WP7 Root Tools with Full Root Access finished I will release an SDK, which will make access to the system a lot easier. The SDK will consist of a native library and a managed wrapper library. Developers will be able to access the Registry and Filesystem using only managed code and the libraries from the SDK. The app will of course need to be unlocked, using WP7 Root Tools on the device. But using the SDK is mandatory. You can also write your own native code. I will write a guide on how to do that later on. An app that has Full Root Access (provided by ROM or by WP7 Root Tools does not need any device-specific libraries. All API's can be used. For API's that are not in the SDK libraries you need to write your own COM wrapper.
Registry Editor
The current version of the registry editor has an issue with string-values that contain special unicode characters and non-ansi-characters. There was no quick fix for that. So currently I have marked these values with "<INVALID STRING>" and made them non-editable. I think I can fix this in the next version of WP7 Root Tools.
File Explorer
I specifically mentioned that this version has basic file-operations, because not everything is implemented. This is what you can do:
- Cut / Copy / Paste / Delete / Rename single files
- Delete empty folders
- Create new folders
This is what you can't do (will be possible in later versions):
- Cut / Copy / Paste multiple files or entire folders
- Delete folders with content
- Rename folders
Certificate Installer
You might wonder why I created a certificate installer, because it is already possible to add certificates. When you email a certificate to yourself and tap that attachment, WP7 will install it. But if you install like this, the certificate will always be installed in the "Root" certificate store. With my certificate installer you can also install in "CA", "My" and "Code Integrity" stores. This may be very useful for hacking attempts. You can install a certificate by browsing to the ".cer" file and tap it. The possibilities for getting a certificate file on your phone will follow below. If you start installing certificates on your phone you should consider making backups in advance. I once experienced Zune going totally bezerk after installing certs. Zune took 100% and lost connection with the phone all the time. Everything was back to normal when I deleted the certs. In this version there is no view on the certificate stores available yet. In a future version you will be able to view the contents of all the certificate store and also uninstall certificates from there.
Desktop Sync
This version does not have a connection with the desktop computer. So it is not possible to use WP7 Root Tools to transfer files between the phone and the desktop. I hope to add this feature soon. Currently you can use other tools to get files onto your phone and then use WP7 Root Tools to move the files to the desired location. WP7 Root Tools has write access on every folder of your phone.
How to transfer files to your phone:
Mail the file to yourself. Use your phone to go to your mailbox (not webmail). The attachment will be downloaded in the background. Then use WP7 Root Tools to navigate to \Application Data\Volatile\EmailAttachments\Attachments(number). You have to look which attachment is the one you want. The filename may be changed. The extension is the same.
If you have RTM or NoDo, you can install Davux' webserver on your phone. Configure a password in that webserver. The IP of the phone is visible in the webserver app. Browse to the phone like this: http://192.168.1.2/IsolatedStorage using the IP of the phone. Upload a file to the phone. Open WP7 Root Tools 0.5 alpha. Navigate to this folder: \Applications\Data\9BFACECD-C655-4E5B-B024-1E6C2A7456AC\Data\IsolatedStore\. There's your file. You can copy it to another location if you want.
Use the Zune storage hack, described here and here. If you copied the files to your phone in this way, they will be located at \My Documents\Zune\Content in one of the subfolders. Again, the files here are renamed. You have to find the file you want and then rename it.
If you like this, hit the "Thanks" and/or "Donate to me" button.
Ciao,
Heathcliff74
Some screenshots:
{
"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"
}
Version history
0.1 - 2011/04/04 - Initial release: only registry-editor
0.2 - 2011/04/13 - Performance improvements and minor fixes
0.3 - 2011/04/14 - Bugfix in registry-editor
0.4 - 2011/06/14 - File browser added
0.5 - 2011/06/24 - File Explorer with basic file operations and certificate installer
0.6 - 2011/09/17 - Compatible with Interop-Unlocked Samsung Mango devices
0.7 - 2011/09/17 - Bugfix in registry-editor
0.8 - 2012/01/02 - Session and Multi-Tasking awareness + Mango UI improvements (better responsiveness)
History: http://forum.xda-developers.com/showthread.php?t=1021135

Reserved.........
Reserved.........

Reserved for guides....
Reserved for guides....

Reserved for guides....
Reserved......

I can't deploy it to my non-hacked developer unlocked focus running mango rtm. I get the following error when using the newest windows phone 7.1 sdk rc application deployment tool: Error - 0x81030120
EDIT: If I remove the line "<Capability Name="ID_CAP_INTEROPSERVICES"/>" from WMAppManifest.xml I can deploy it... but it crashes after the warning screen. Looks like Mango shipped devices might be out of the picture. There is something different about a normally developer unlocked phone and a pre-mango hacked to unlock one. Something that is changed durring the process listed http://forum.xda-developers.com/showthread.php?t=1152422 makes the "Error - 0x81030120" go away.

voluptuary said:
I can't deploy it to my non-hacked developer unlocked focus running mango rtm. I get the following error when using the newest windows phone 7.1 sdk rc application deployment tool: Error - 0x81030120
Click to expand...
Click to collapse
Is it possible you need the fullunlock and not just devunlock for this to install? I have an HTC so can't confirm.

That's what it looks like. Not a problem for me right now, and still a *huge* leap forward (homebrew native code on Mango!! That means everything from screen capture to the DFRouter app to things like SMS access!). It's going to suck if it's not worked around by the time I get my next device and it comes with Mango, though.

LiFePo4 said:
Is it possible you need the fullunlock and not just devunlock for this to install? I have an HTC so can't confirm.
Click to expand...
Click to collapse
Maybe a dumb question, but what is the difference?
I was able to deploy after removing the interop reference, but the app just closes when I run it.

N!njaDuck said:
Maybe a dumb question, but what is the difference?
I was able to deploy after removing the interop reference, but the app just closes when I run it.
Click to expand...
Click to collapse
People are calling the "Full unlock" the step above the Dev unlock. It's when the reg keys are done to open up unlimited unsigned apps. If you are "fully unlocked" even with mango, you should be able to install this app with out having to remove the "interop" tags.

Hi mister,
I can't acces to registry HKLM\Software\Microsoft\... software closed !
Very big thankx for this work my friend !

Same problem here:
Deployment FAILED with the following ERROR:
0x81030120
Omnia 7, Mango RTM (Dev Unlock)
But still thanks for your work, that's a huge step.

it works !
can deploy and do stuff what idid on nodo with 05 on .
good work..Thanks, that i was waiting for.
omnia7mango rtm
edit :in hklm/software/microsoft the prog crashes..

so it's a no-go with just dev unlock? well I'll wait till mango is officially out and get a full unlock then...
still you've done a great job

@Heathcliff74:
I would like to thank you with my 2nd donation since you have started the WP7 Root Tools project: 1V361345JM332073Y.
Keep up your great work !
Best regards
contable

I am unable to deploy anything with Interopservices on my Focus. I am running Beta 2 with official dev unlock.

ryotgz said:
I am unable to deploy anything with Interopservices on my Focus. I am running Beta 2 with official dev unlock.
Click to expand...
Click to collapse
official dev unlock in unfortunately not sufficient, you will have to set the maxunsigned app flag to the maximum value. This is the only way you can deploy apps with native code besides trough the marketplace.
This means up until now new mango pre installed devices are not supported, but Im sure somebody is looking for a way to bypass this limitation.
So make sure you use a provxml method to upgrade to mango.
Heatcliff, thanks again for you work
Ow and @heatcliff: transfering files is a lot easier on mango, since you just have to copy them to the iso storage of root tools and than run WP Power Tools to download them. Maybe you can make a folder in root tools iso storage and a menu option to copy to iso storage for easy transfer to the pc. No need for a file server or anything.

Phenominal work Heathcliff74! Now I can browse the FS and have some closure for the ringtone deployment.. Now I know FOR SURE that the ringtones are in \My Documents\Ringtones still, but M$ puts them in a db in order for them to be accessible... Next version of R1ng3d will be looking through \My Documents\Ringtones and \My Documents\My Ringtones from back in the NoDo days

Thanks ... great app

I updated the opening post with two important notes, regarding error 0x81030120 and the crash in HKLM\Microsoft\Software.
Heathcliff74

Here some feedback:
1. speed is very good => browsing the windows folder is much faster than with touchxplorer on my HD7
2. after renaming or deleting a file there is no refresh of the folder
3. multiple file operations are still missing (you pointed that out on post #1)
=> e.g. would make life much easier if you want to copy files to the windows folder
4. a search function like touchxplorer has would be great
=> e.g. *.xap will list all xap files in a folder

Directions Please - Unlock/Backups/ROM/FLASH/MANGO/NODO/7004/Zune versions

Can someone please simplify all this for me?
The information on this site is so convoluded in terms of methods, some expired , some still valid, and guesses that are plain wrong, and irrelevancies.
I have been reading, installing, and uninstalling for hours into days.
Samsung Focus
1. Can Mango unlock be achieved with unlock from 7004?
2.I was on NoDo unlock and followed some instructions for the Focus that did not work. It went right to Mango LOCKED (as many others have reported).
I made a nice little back up of my NoDo unlock but can't get back to it using any version of Zune or any method, they all result in restore errors.
My back up might as well be on the north pole because I can't get to it.
3.I flashed back to 7004 and couldn't get chevron to unlock again like I used to be able to on XP or WIN 7 with various zune versions back to 4.7.
I'm wondering if the newer Zunes corrupted that somehow because last time it worked was on a fresh zune install on windows 7.
And besides that, they all ask to be upgraded before they do a back up, usually.
4.But even if it is unlocked at ROM 7004, zune updates (if chosen) will send it back to mango and locks it agian right? That's what happened last time , it just kept updating the phone for hours and then it was back to mango.
5.It appears my only option now is Mango locked or 7004 flash Rom with possible unlock.
Hopefully answers here will help others as well.

A few answers, though not compreheensive:
1) You don't have to let WP7 install each update, if you wanted to stop at, for example, NoDo 7392, you could. Just wait untilt he update gets that far, then pull the plug and/or hit Ccancel in Zune. Left to itsself, it will install all available updates.
2) The phone automatically dev-relocks whenever a major update is installed - this happens even to people with legitimate develop-unlock (and it's annoying!) For Samsung, I believe the technique for preserving unlock is the same one used to get interop-unlock on Mango: place an unlock provxml file in \provxml\ on the phone's filesystem (you can either use Heathcliff74's WP7 Root Tools to do this, or you can just install his interop-unlock XAP) and make sure you have a working version of the Samsung Diag app (should allow you to process provxml files). Once you have that, you can install all the way up to the Mango update safely, I think (I don't have a Samsung, but it should work) and use the Diag app to process your provxml file, which will both dev-unlock and interop-unlock the phone.
Not sure what's up with your backups; I can't really help you there without more information. What error do you get? What version of Zune are you using (you probably should use the latest version, 4.8.whatever)? How big is the backup (it's in %localappdata%\Microsoft\Windows Phone Update\)?
As for what guides to follow, starting with the stickies is always a good idea.

Hello,
I have a HTC Mozart device wich is momentarily running on unlocked NoDo.
I have followed various guides from xda but I end up running a locked Mango (most of the guides require after Mango update to run HTC Connection Setup to unlock... which I am unable to run (black scren) and all other apps tell me revoked by Microsoft).
is there any latest guide a little more foolproof?
It seems that after 18th October something happened with Zune which prevents Mango unlock...

Gyuritzy said:
Hello,
I have a HTC Mozart device wich is momentarily running on unlocked NoDo.
I have followed various guides from xda but I end up running a locked Mango (most of the guides require after Mango update to run HTC Connection Setup to unlock... which I am unable to run (black scren) and all other apps tell me revoked by Microsoft).
is there any latest guide a little more foolproof?
It seems that after 18th October something happened with Zune which prevents Mango unlock...
Click to expand...
Click to collapse
After you install the interop-unlock xap while on nodo then goto mango you reinstall the diag app and in the Diagnosis app dial: *#9908#.. Select "Heathcliff74 Interop Unlock"
then tap Save, tap Close and exit the Diagnosis app

@lucasryan: Those are the instructions for a Samsung phone. They don't work at all on an HTC phone.
@Gyuritzy: Currently, Microsoft is pushing the Mango update and an HTC update together. The HTC update blocks the unlock path used with Mango. If your phone gets that update - which means if it gets Mango through the retail update path - there's no current way to interop-unlock it.
If you can get Mango through an atypical upgrade path (I came from the beta, which worked), or if you use a custom ROM (be *very careful* of the bootloader version if you try this!!), you can get interoop-unlocked Mango on HTC. It's not easy, though.

Ahh i see that i quoted his post now. as alan93 has focus

What solution do I have to load Mango without HTC update? Should I try with RCT2RTM type of packagge?

@GoodDayToDie
#1 - ahh ok, but I'm sure watching the update tentativley is required right? For like an hour and a half.
#2 - now see, there you go again, this is only for dev-unlock people which , i'm not even sure what that is..what? you pay $100 to MS to get it? It needs to be stated more clearly where ever that solution is posted AT THE VERY TOP like this "IF YOU ALREADY HAVE A DEV UNLOCK ....
@ lucasryan - That can't be right, -->"installing interop unlock on NoDo then go to Mango"...STOP RIGHT THERE. when you go to Mango it wipes everything out and you have no more access...unless of course ..YOU ALREADY HAVE A DEV UNLOCK...what ever that is.
I did try the diagnosis trick on update to mango after putting that file on there but the diagnosis version would not go higher than 908 or what ever. Couldn't get 1112 or what ever the one that is needed.
Please, just say there is no way to unlock Mango unless you have a dev unlock and that is low percentage as it is...then I won't expect so much.
Thanks for the replies.

Here is the zune error I get on trying to restore to my NoDo unlock.
http://answers.microsoft.com/en-us/...-restore/3ec7091d-d79d-422c-9995-cfe186e0155b
As you can see nobody is dying to answer it.
I think the code number means "this goon is trying to restore to an unlocked version, don't answer him".

@alan93: Developer Unlock is the term used for the change to your phone made by the Windows Phone Registration Tool (if you have a marketplace developer account), ChevronWP7 Unlocker (possible on pre-NoDo), ChevronWP7 Labs (coming soon), or changing the DeveloperUnlockState registry value located at HKLM\Comm\Security\LVMod to 1 (possible with the LG registry editor, or by using the Samsung diag app or HTC Connection Setup app to process to provxml file). The registry change is actually what matters; the other methods are simply ways to achieve it.
Dev unlock allows you to install XAP files - a renamed ZIP file with some manifest XML files, one or more managed (.NET-based) DLL files, and possibly other files needed by the application. Due to a bug in the application installer, you can also use a XAP to put arbitrary files almost anywhere in the filesystem (the installer can't write to the \Windows\ directory).
One of those manifst files specifies capabilities that the app has, which controls permissions of the app (for example, ID_CAP_ISV_CAMERA allows access to the public camera APIs). As of Mango, including beta versions, it is no longer possible to install apps with the ID_CAP_INTEROPSERVICES capability unless the MaxUnsignedApp registry value (located in HKLM\Software\Microsoft\DeviceReg\Install) is set to at least 300 (the default value is either 10 or 3, depending on the unlock method used). ID_CAP_INTEROPSERVICES is required for interfacing with drivers, a way for applications to run at high permissions (for example, to write to the registry). Each time you install a major upgrade, such as Mango, this value is reset to its default. An app with ID_CAP_INTEROPSERVICES therefore can't be installed (or run, if it was installed before upgrading to Mango) until this MaxUnsignedApp registry value is changed, a process referred to as Interop-unlock (term coined by Heathcliff74 on this forum). Marketplace-installed apps are exempt from this restriction, which is why things like Connection Setup (which has ID_CAP_INTEROPSERVICES) can be used.
For what it's worth, I got my dev-unlock by purchasing a marketplace developer account ($100 from MS). One day I may even submit an app to the marketplace, but so far all the apps I've written use homebrew and wouldn't be acceptable for the marketplace, so I just publish them here.

Thanks great explanation.
I intend to write my own too, I wrote one and have a few more great ideas but didn't want to pay until i made sure I was able to write them completely and testing on the simulator sux. And last I heard, the media player doesn't work with it.
I just think the fee and lockout just hurts development thereby limiting the success of WP7.
If it was $50 or less I would probably pay it.
I mean for crying out loud I'm a certified MCP/MCAD, they should give me a break here.

[IDEA] Possible interop unlock for HTC Phones

I have found a theoric solution so far for interop-unlocking an HTC Phone. Disassembling HTC Connection Setup (since it the HTC.Shell.Registry.dll) and modifying it using IL Spy for example and include the line of code to modify the register (the dll stated before is capable of doing this).
Windows Marketplace App is capable of installing apps with Interop Services (you can install HTC Connection in fact) so we could sniff (i.e. via Wireless) the app traffic to detect when it dowloads the xap. Then by using the router settings (or a proxy or something like that) we could divert the traffic to a modified xap so the Market will download the modified xap instead (or we could even totally use another app ).
This will work only if the market hasn't those characteristics:
* It uses HTTPS to download the xaps (by the analysis I have done so far it seems not)
* It checks in any way the downloaded xap.
Do you think it could be a good idea?
I am not an expert in those things but by discussing with a colleague he stated that could be possible (difficult however in his opinion).

Microsoft?
Do you think Microsoft guys wouldn't have thought about this before and have taken preventive measures?

Never doubt HTC's ability to compromise an OS. lol I'm not all that familiar with xaps yet but I would think they have some sort of checksum or key that it can check the app with to make sure it's not corrupt.

xHausx said:
Never doubt HTC's ability to compromise an OS. lol I'm not all that familiar with xaps yet but I would think they have some sort of checksum or key that it can check the app with to make sure it's not corrupt.
Click to expand...
Click to collapse
Indeed... plus this. A similar methodology could be used to prevent what the OP suggests. I'm certainly not trying to rain on the OP's parade... in fact I hope that siomething similar can be achieved.

ATM it looks like that the only problem is that the market xaps are digitally signed. By the way the MultipleXAPInstaller program lets you sign the package when sideloading it.

i found the latest Registry Editor can run on my hd7, so maybe the interop-unlock will happen soon.
so,is it possible to interop unlock mango HTCs ?

it will run, but it wont write the values

It runs. We have also found the DLL capable of accessing the registry (they are in HTC Hub and HTC setup) but they require interop-unlock .

the only way to interop unlock is the DFT free ROM ?

Currently DFT rom is the only way for HTC WP7 device

Well XAP files are no way tampering the interop and HTC have custom build into the OS the Interop utilities as shell dll's. e.g HTCRegistryUtility.dll which we can find in any HTC ROM.
All other COMRw or COMReg dll files what we find in HTC xap files are all wrappers to trigger the typeinfo from InprocSrvr ID's predefined for HTC Interops.
Thats the reason all phones (HTC,Samsung,LG) cannot use same Unlock methods.
Best way is to somehow poke a custom certificate to spctrustroot and sign the xap files you download with that again and install.
Or somebody has to hackdown the pacmaninstaller.dll file inside the ROM and create a updatecab for that.

http://forum.xda-developers.com/showthread.php?t=1354706&page=6
this thread provides a new way to unlock
but it doesn't wok on my hd7(if it's related to my SPL version --5.0)

[w10m] screen recording

I badly need screen recording feature in w10m. is there any app to make this happen?? I read some where that microsoft released an API for screen recording back on WP8.1 but surprisingly nobody still hasn't been able to make such an app.... [emoji26] [emoji26] As I know W10M can be interop unlocked and can get FULL SYSTEM FILE access... Can anyone make such an app?? It will help us a lot...
Thnx in Advance... Any help will be appreciated

Project my screen.
https://www.microsoft.com/en-in/download/details.aspx?id=42536

that will need a PC... Need an app that can record screen without the need of PC

There isn't. It will be great if Windows 10 API allow us to create an app to do that.

MrCego said:
There isn't. It will be great if Windows 10 API allow us to create an app to do that.
Click to expand...
Click to collapse
Interop Unlock gives apps to run with high privileges (out of sandbox) .... Isn't Full system file access enough for creating such an app??

iammomin said:
Interop Unlock gives apps to run with high privileges (out of sandbox) .... Isn't Full system file access enough for creating such an app??
Click to expand...
Click to collapse
Interop Unlock doesn't mean allows to use high privileges. Even it can't do capability unlock. There is even no any capability to allow us to Capability Unlock.
We use OEM's svc "NdtkSvc" that we can use some registry functions with high privilege (because svc runs in system context). Which can write registry anywhere. WP/W10M there is no way to run apps out-of-sandbox. Unless SB Unlock.
We also mods "MTP" service which allowed us to browse file system in system account. (which is also from PC, but NOT FROM PHONE or not possible using any APP on phone)

djamol said:
Interop Unlock doesn't mean allows to use high privileges. Even it can't do capability unlock. There is even no any capability to allow us to Capability Unlock.
We use OEM's svc "NdtkSvc" that we can use some registry functions with high privilege (because svc runs in system context). Which can write registry anywhere. WP/W10M there is no way to run apps out-of-sandbox. Unless SB Unlock.
We also mods "MTP" service which allowed us to browse file system in system account. (which is also from PC, but NOT FROM PHONE or not possible using any APP on phone)
Click to expand...
Click to collapse
what is SB Unlock?? I have heard about an app which runs out of sandbox named Interop Tools...it runs out of sandbox and allow us to change registery etc.. which is a w10M app and also this app works without PC.. Correct me if I'm wrong

iammomin said:
what is SB Unlock?? I have heard about an app which runs out of sandbox named Interop Tools...it runs out of sandbox and allow us to change registery etc.. which is a w10M app and also this app works without PC.. Correct me if I'm wrong
Click to expand...
Click to collapse
I get that you're probably not super computer-savvy, but I'm still not sure why you think file system access would let us record the screen. The screen isn't written to the file system anywhere. The executable files in the file system are signed and cannot be modified or replaced.
"SB" stands for Secure Boot, which is the thing that prevents us from, for example, modifying or replacing the Windows kernel (the lowest level of the operating system). There's a potential SB unlock in development but it may not be ready yet. Another way to talk about an SB unlock would be an "unlocked bootloader".
However, even without an unlocked bootloader, we actually do have the ability to run un-sandboxed code. There are "jailbreaks" (hacks that allow removing the executable signature enforcement, allowing us to create, modify, or replace system binaries) for most versions of WP8.1 and W10M now. They may not last - MS tends to kill them off - but they just might, too. In theory, it's entirely possible to write a program that runs outside the sandbox (on a jailbroken phone) and lets you record the screen. I don't know of any such program in existence, though, and unless there's an open-source one that can be easily ported, it's not going to be a minor effort to create one.
Interop Tools runs within a sandbox, but can use RPC (a program-to-program function call) and SSH (a network communication protocol) to make changes that are not normally possible from within an app sandbox. This includes using a jailbreak and running CMD on your phone, unrestricted.

GoodDayToDie said:
There are "jailbreaks" (hacks that allow removing the executable signature enforcement, allowing us to create, modify, or replace system binaries) for most versions of WP8.1 and W10M now.
They may not last - MS tends to kill them off - but they just might, too.
In theory, it's entirely possible to write a program that runs outside the sandbox (on a jailbroken phone) and lets you record the screen. I don't know of any such program in existence
Click to expand...
Click to collapse
first of all thnx for the informational reply. As u said, there are jailbrakes for most version of w10m now and
it's entirely possible to write a program that runs outside the sandbox (on a jailbroken phone) and lets you record the screen. I would like someone to come up with a solution, (of course using some jailbrakes)
Sent from my E79 using Tapatalk

ARM version?