Related
I have been reading XDA-Developers for sometime and have marvelled at the ingenuity that many of you demonstrate in solving problems - I have now registered and here is my first post and hope someone can help - Digital Signing for applications we develop for WM5 is a real pain especially if you need privileged access to run as it is up to the carrier or device OEM if they want to grant you use of the certificate. I guess if you were selling software this could mean they could withold permission because they had a competitive application, all smacks of anti-trust...unprivileged access is more straight forward but is no good if you need to access the kernel or other specialist processes. I note from the XDA WM5 part of this forum that someone had changed a rom so that it would not moan at unsigned apps. Does anyone know if this change would allow any unsigned "privileged" application to be used on a JASJAR - if so does any kind person have the ability to create a CAB file that could or program that could enable this condition and another to revert to normal operation. This would make a huge difference for those wanting to develop and test apps on a device instead of just the PC emulator however it would still require signing to get the end result available for others to use on their devices - I guess we would also have to consider if this "modifying" app also needed to be signed to run in the first place - nice one MS :evil: , the user is no longer allowed to decide what he wants to install :roll: .
According to MSDN there is a tool in the WM2005 SDK called createcert.exe that allows you to create certificates for test purposes.
I didn't have much luck with it my self, but I haven't read all the documentation, so I probably screwed up when creating the certificate.
Have you tried it?
If you make it work, could you please give me some advice on it. Thanks!
hi
good day
my new friend is a developer
he made an app and wants to publish a beta for tests
so is there any idea on how to make a small package for testing like darijoa from badanation.de did it??
http://www.badanation.de/topic.php?t=3966&page=1
P.S: i am not a developer so i'll just deliver data
Thanks in Advance
With bada SDK...
There is an option to make package... so only "Binary" is included instead Source Code.
If no one is faster, I will make an Screenshot... sooon.
Best Regards
What's the problem? You just need to replace the application in the "\App\" folder on his own and edit the "\App\App.cfg". Darijoa installer is just part of the Bada SDK with skillfully written bat-file.
hahahahahaha
Xenon do you expect from me to understand this??
my friend is just a new bada developer who needed some help
he knows C/C++ but didn't study the bada SDK
i didn't believe him when he told me that he wrote an app just 4 days after downloading SDK (thats too fast for me)
anyway i'll tell him what adfree said and what you said too
Thanks for helping guys
XDA rocks
Hi Guys
adfree/Xenon, is there any way to install any app [without having certificate to this application] by Darijoa bat file? If I'm installing original app with cert, for example Voluntas, installation goes well. But I was tryin' something different - I put MyExplorer app in "App" folder, changed strings in config file. When I tried to install this app using this method, my phone says "Error 0108" - no certificate to myExplorer. Is there any way to install ANY application using this method? Is there any option to create certificate to application what I didn't created?
If you don't know what, I wanted to, I thought to create new spoof method for people using JL2 firmware. After this f*****n' Samsung Apps update, only way to run "non-free" games is to reflash their phones [downgrade to JK1 for example]. Not everybody want to do this
Btw, Xenon, good work with sp.so protection
adfree, good job with all U R doing
Best regards,
wxtester
I am sure Adfree has absolutely no interest in supporting a new "****ing" method of spoofing.
Btw, with that **** you are not damaging Samsung, but small developer groups and freelancers like us.
@wxtester
This installation method is only available for applications signed by developers certificate. And so by this way is possible to install only one application. Create a certificate - a task nearly impossible. Possible way to solve - edit apps_сompressed.bin, so I'm hope for success in the holod's QMD packing, this will open a new stage in the creation of custom firmwares.
The result of probably more than 100 hours of solo hackery: a working COM DLL for allowing any application to elevate itself to SYSTEM (root) permissions.
What you need:
An interop-unlocked HTC phone. Sorry second-gen and Arrive users.
A working HtcUtility driver. It's possible some HTC update at some point crippled this. It works for me; if it doesn't work for you let me know what updates you have.
What it does:
Allows changing the security token of any application to give that app unrestricted permissions. At this point, you can call any user-mode API, perform any operation, with full access.
It also allows you to read or write any value from memory, even kernel memory (this is how it modifes the security token).
What it can be used for:
Darn near anything. If it can be done while the phone is booted, you can do it.
What it can't be used for:
Modifying the ROM - the R and O stand for "read only" and they mean it.
Interop-unlocking a phone - it requires interop-unlock to get root in the first place.
How to use it:
In your app, include the HtcRoot.dll library.
Include the code from DriverAccessTest.cs in the test app (defines the COM API and enables using it).
Call the OpenHtcUtility function (will throw an exception if your device is incompatible).
Call the MakeMeRoot function (can also throw exceptions).
(OPTIONAL) Call the ReturnZeroIfRoot function to make sure your app is elevated (does not throw exceptions, will return an error code if you get one).
Do stuff with SYSTEM permissions (probably using another COM DLL, such as for registry or filesystem access).
Call the RestoreToken function (failure to do this *might* cause a kernel memory leak).
Call the CloseHtcUtility function (OS will probably handle this if program just exits).
What you can do right now:
Try the test app. It should pop up a series of messge boxes. Hopefully none of them say anything like "FAILURE".
Report any bugs or failures you discover.
Build things with this library, and publish them!
Breakdown of the download:
There are two folders in the ZIP, one for the Visual Studio 2010 C#/Silverlight XAP project, and one for the Visual Studio 2008 C++/COM DLL project.
The test XAP is in the HtcUtilityTest\bin\Debug folder.
The native (COM) DLL is also available in that folder, or under its own project.
If you want to mess with this, I'm going to assume you are already familiar with hybrid native/managed development for WP7. If not, Heathcliff74 has posted an excellent tutorial on this forum.
Special thanks to:
Heathcliff74 for the hybrid app tutorial and interop unlock info.
Paul_Hammons for the links and info about HtcUtility, the driver that makes this possible. Thread: http://forum.xda-developers.com/showthread.php?t=1434793
Supported devices / firmware versions / ROMs
All HTC devices (if interop-unlocked and with the right firmware numbers) should be compatible.
Some custom ROMs work, some do not. This will depend on the version of the firmware that the ROM's HtcUtility driver is taken from.
I believe I compiled the test app as Mango-only, but the native library doesn't care at all.
Compatible:
Stock ROMs with compatible firmware for HD7, Trophy, Mozart
HD2 (BttF [XBmod-Yuki] v2 SP1)
Not compatible:
Firmware version 2250.21.51004.401 or newer
Verizon Trophy firmware version 2305.13.20104.605 or newer
DFT ROM with build 8107, Firmware 5.10.401
Arrive (except on pre-Mango), Titan, Radar, Titan 2 (no interop-unlock)
Others are untested or results are incomplete.
Goals and future work:
Support more devices:
* Try and add support for newer firmware.
* Help ROM cookers ensure the library is supported.
* Look for similar openings in other OEM libraries.
Future-proofing:
* Allow installation of a mod to support this capability after known updates.
* Resilience against possible future updates.
* Allow users with incompatible devices to downgrade (possibly to NoDo), install the mod, and be able to use the phone after upgrading.
Improve the library:
* Fix some memory leaks.
* Clean up the code - remove dead code and improve comments.
* Allow reading/writing more than 4 bytes at a time from managed code.
* Add APIs to elevate other processes (by name or ID) to SYSTEM.
Develop homebrew around the library:
* Support accessing common APIs (filesystem, etc.).
* Resurrect the Advanced Explorer app, perhaps (registry and filesystem).
* Support native app launching on stock ROMs.
Also reserved
Reserved for OP #2
It does not work on HTC 7 Mozart (HTC Europe):
Error to Write the value 1337 to test address - System.Runtime.InteropServices.COMException (0x8007001F): A device attached to the system is not functioning
Click to expand...
Click to collapse
OS: 7.10.7740.16
Firmware: 2250.21.51101.401
Radio: 5.71.09.02a_22.51.50.21U
Boot: 5.11.2250.1(133487)
Please include the full error message or a description of what went wrong.
Failure on fully updated devices is unfortunately possible - my phone is (intentionally) a few updates behind. I'm looking into ways to make it work anyhow (either sending an older CAB update to roll back, or using the root acess to create an unlocker/root-enabler that survives subsequent updates). I'm going to look into how the full-unlock ROMs differ from standard ROMs, and see if I can do the same thing in running software.
Does it works with custom roms?
If the custom ROM has a working HtcUtility driver, then yes. My goal is to unlock the kind of capabilities normally restricted to custom ROMs on stock firmware, though.
@bleh815: Thanks for the report. That's frustrating; it looks like it is capable of doing read but not write. Write might just be restricted in what addresses is allowed, or it might be disabled entirely (the driver gives the same error code for every problem that I've encountered so far). Time to figure out
A) what update causes the problem (I'm on 2250.21.30102.531, HD7, stock ROM)
B) what restrictions that update introduces
C) how to work around those resrtictions (possibly by downgrading and then using root access to add something that will still work after upgrade).
GoodDayToDie said:
A) what update causes the problem (I'm on 2250.21.30102.531, HD7, stock ROM)
Click to expand...
Click to collapse
I've just downgraded a mozart of mine back to stock NoDo (TMOB-DE) to find out which OEM update breaks (actually fixes) it.
Cool, thanks! It's one of the post-Mango HTC updates; a Microsoft update wouldn't have modified an HTC driver, and my phone has all the pre-Mango HTC updates but it still works.
.
..........
Hi, at first it says "SUCCESS!", then it says "Trying to open a file gives error 1260" and then it says "Now opening a file gives error 0" and finally "Finally, opening a file gives error 1260".
System informations:
OS=7.10.7720.68
Firmwareversion=2250.21.12200.162
Radio=5.68.09.05a_22.50.50.21U
Bootloader=4.6.2250.0(129185)
HTC 7 Trophy.
That is *exactly* the sequence of messages it is supposed to give!!
In particular, the messages I need to see are the "SUCCESS" (the rest is potentially interesting info, but not very important) and then the "Now opening a file gives error 0".
The "SUCCESS" means that a sequence of read/write tests succeeded.
The "Now... error 0" means that the process has been elevated to full permissions.
The "Finally... error 1260" means that the security token was successfully restored at the end, so it was unable to open the file again. This is the expected and correct behavior.
I don't recognize your Firmware Version number; I'm guessing it's specific to your phone. What method did you use to upgrade to Mango?
how do i install it?
Tried on interop-unlocked HTC Surround, not working Tested any call in VS debug mode - no luck at all.
I can confirm that it works with any OS version, from 7004 to 8107.79
On a HTC 7 Mozart (TMOB-DE) it works with firmware 2250.21.13201.111 (Stock NoDo ROM) but the hole gets fixed with 2250.21.51101.111 (1st Post-Mango HTC Update).
You guys are gods taking programming to a hole new level!
I wish to see ms take you all more serious and not let wp7 fail like minmo6.5 did!
I wish I could get on your level!
I realy need some help lerning basic silverlight my self!
But I have read how hybrid working ant this is just fantastic!
conradulations on all your developments so far you guys are truly amazing!
Oh, that code, beautiful reading that!
Thanks for sharing this learnfull code!
I'd like to try it on my Verizon HTC Trophy, I would love to get file access back....
I downloaded the package and I even have VS 2010 installed but beyond that I have no idea as I am not a programmer.
Can someone post a compiled XAP for us to try to see if our phone works with it or not ?
Or some step by step VS 201 directions to try would also be helpful.
@Ttblondey: *FACEPALM* The path to the test XAP is given in the opening post. You install the XAP on your phone using any XAP deployment tool. It requires that your phone be interop-unlocked; Heathcliff74 has a nice long thread about that. The app is called called HtcUtilityTest. Run it, and report the results. If you want to actually *use* the DLL, the instructions for doing that are given too but you need to write some code.
@sensboston: PLEASE give a more complete report! Success and error messages, at the least. Also, your phone version info. Thanks!
@bleh815: THANK YOU! I mean, it's a little annoying to know how far back this was fixed ("First post-Mango HTC update" means the one that was included *with* Mango for most people, or the one after that?) but good to know. Now, to look at exactly what they changed...
@jackrabbit72380: Thanks man! As for working with it yourself, like I mention below, I'm planning to provide a universal homebrew library that people can easily use to do whatever they want.
@fiinix: You're welcome! Honestly, I didn't expect anybody to call my mess of debug-commented and mildly hacky C++ "beautiful" but that hack itself *is* pretty awesome. My only concern with using it is the risk of a context switch causing the wrong app's token to get overwritten, and I should probably look into that, but I think it's OK for the moment. There are bigger fish to fry.
In the meantime, it should open up a huge list of capabilities for tools like your DllImport project. I'm currently considering reviving Advanced Explorer (like TouchXplorer + Registry Editor, but open source; was never ported to Mango though) using the root access instead of using ComFileRW and the provxml driver. Let me know what you want to do with it!
One other thing I'd like to add is the ability to easily elevate *another* process; it's not hard to do but I haven't written it yet. This could be handy for apps where we don't have the source code (for example, elevate Schaps registry editor, which uses low-privilege native code for browsing, so it can read *all* registry locations instead of just some of them).
@DavidinCT: Well, running the test app is easy, just install the XAP. It just runs a battery of tests though, it doesn't actually *do* anything useful. To get filesystem access, you'll need to write some native code (which means using Visual Studio 2008 and the CE/Smart Device plug-in, see Heathcliff74's toturial on the subject). Basically, you would first use this DLL (accessed via COM, you can look at my own C# code for how to do that) to opent he driver handle and elevate the process to root. You could then write your own COM DLL that uses the standard Win32 filesystem APIs (CreateFile, etc. - all are documented on MSDN) and exposes those APIs, or the results of them, to managed code via COM. Then, back in your phone app (the one that called into my HtcRoot DLL) you can call into your own DLL to access the file system.
If that's too big a leap, don't worry. I plan to release a general-purpose high-privilege homebrew DLL that exposes some of the most-used functionality (filesystem, registry, provxml, and other things by request), is easily extensible (possibly using something like the DllImport project, where you just specify the function you want to call and the DLL it's located in right from C#), and that will be a lot easier to hack with. You'll still need to know C# and basic Silverlight, but it'll be a lot easier (and hopefully useful without knowing any C++ or COM).
GoodDayToDie, you are amazing, always keeping me interested!
When starting the test xap, I get the below, it then goes into the "Page Name" and that's it.
Device Info here, running a FullUnlock DFT Rom by a Chinese dev from the DFT Forum.
Nonetheless, top work on getting this started and can't wait to keep reading about the progress!
XeKToReX
{
"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"
}
Download here: www.wp7roottools.com
NEW: WP7 Root Tools 1.2 is released! It includes an Accent Color editor and Internet Sharing unlock now.
WP7 Root Tools
With this tool you get root-access to your WP7 device. The current version contains the Policy Unlock Installer, a registry-editor, a file-explorer with many file-operations, certificate-stores, a policy-editor, a tweaks-section and an Accent color editor. This is your all-in-one system-tool for Windows Phone 7.
If you like this app, you can donate to buy me a beer (or two).
With WP7 Root Tools I attempt to open up the system in a gentle way, so that users stay in control of their device, while homebrew apps can get more control to get the maximum power out of your Windows Phone device!
Supported Devices
Samsung first and second generation devices with Interop Unlock
LG devices
HTC first generation devices with Mango v1 drivers (SPL 4.x or lower)
Samsung first generation devices with custom ROM and Full Unlock
HTC first and second generation devices with custom ROM and Full Unlock
NOKIA devices with custom ROM and Full Unlock
Your phone needs to have at least INTEROP-UNLOCK. If you get error 0x81030120 when you deploy WP7 Root Tools to your device, then please read this guide! WP7 Root Tools will also work on devices with Full Unlock. If you want to know more about the different types of unlocks or if you want to know why WP7 Root Tools may or may not run on your WP7 device, you should read this guide.
License Agreement
WP7 Root Tools and WP7 Root Tools SDK are Copyright by Heathcliff74 / www.wp7roottools.com in 2012 - 2013
This license governs use of the "WP7 Root Tools" software. If you use the software, you accept this license. If you do not accept the license, do not use the software.
You are free to redistribute the software, as long as the copyright, conditions and disclaimer of this license are present whenever you distribute any portion of the software.
The software is licensed "as-is". You bear the risk of using it. The developer gives no express warranties, guarantees or conditions. To the extent permitted under your local laws, the developer excludes the implied warranties of merchantability, fitness for a particular purpose and non-infringement.
Redistributions of the copyrighted software may not be sold, nor may they be used in a commercial product or activity without first obtaining explicit permission of the developer.
Don't be stupid, make a backup!!
This tool is still in alpha stage. That means 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.
You can find backup-programs here on XDA. For example WP7 Easy Backup Tool by MarcHoover or WP7 Backup App by hx4700 Killer.
Installation
On devices with custom ROM and Full Unlock, the installation of WP7 Root Tools will be pretty straight-forward. You install the XAP and it works. On devices with stock ROM's WP7 Root Tools need to install Root Access. The first time it runs, a 2-phase-installation will start. The app will inform you to start the first install-phase. Then the device will reboot after a few seconds. After the reboot you need to start WP7 Root Tools again immediately! Then the second phase of the installation will start and your device will be rebooted again. After the second reboot you are ready to use WP7 Root Tools.
Update to a new version
If you have an earlier version of WP7 Root Tools installed and you have WP7 Root Tools Policy Unlock, I strongly advise to UPDATE the app, instead of doing a full install-cycle. Many XAP installers will do a full install-cycle. That can lead to problems, because during the installation WP7 Root Tools will temporary loose its Root Access. In that case WP7 Root Tools needs to do the 2-phase-installation again. This is usually not a problem, but future OEM- or OS-updates could make it possible that the reinstall will not be possible. So, to be on the safe side, first make a backup of the device (use a backup tool from the XDA forums) and then use a XAP installer that has the possibility to update an app. One such utility is XAPDeployX 0.9.
Registry Editor
The registry editor in WP7 Root Tools allows full Root Access to the registry. Be very careful with your tweaks, because this may profoundly influence the behavior of your device.
To delete a registrykey or -value you can tap-and-hold the item and choose delete in the context-menu.
The new version also has Advanced Search functionality.
File Explorer
The file-explorer supports all file- and folder-operations, like copying, moving, renaming and deleting files and folders. To select multiple files at once, you can tap an item on the left, which will pop up selection-boxes.
When you select files and folders with the selection-boxes, the file-operations can be chosen from the Applicationbar. It is also possible to tap-and-hold an item and choose the file-operation from the context-menu.
You can tap on an item to launch or open it. It might be necessary to give the app that needs to open the file root-privileges first. The new version of WP7 Root Tools allows you to give Root Access to System Apps like Office Mobile. So if you've given Root Access to Word, you can tap txt-files in any location to open them with Word. The new version will also allow you to give Root Access to Homebrew Native executables. The file-explorer shows whether an executable is "Installed" or "Not installed". If you tap (or tap-and-hold) on an executable that is not yet installed, you can choose to unlock the executable, give Root Access and launch it.
The new version also has Advanced Search functionality.
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.
Certificate Store
You can browse the 4 certificate stores. Tap-and-hold will show a context-menu. You can delete certificates or save them as a .cer file. Be aware that if you delete a certificate you can do severe damage to the system. So, be careful with that!
Policy Editor
The Policy Editor will show a list of all the installed apps. You can use the Policy Editor to give other homebrew app a "trusted" status. With this you will give the app Root Access privileges. So be very careful to which app you give Root Access!! You are responsible for giving access to an app! If you are not sure, read the forums to decide if an app is trust-worthy. The new version will also show System Apps. This is done because for devices that make use of Policy Unlock, it is useful to give Root Access to System apps sometimes. For example to open txt-files outside the My Documents folder.
It is also possible to launch apps from this list, by tapping on the app. But some apps will fail to start from here, because their default task is not configured correctly. This is not an issue in WP7 Root Tools, but those apps were simply not designed to be launched like this. They are listed anyway, because it could be useful to give Root Access to these apps.
Policy Unlock v2 also allows xap-packages with special configs to automatically give unlock Native Homebrew executables when the app is given Root Access. Read more in the "For developers" and "Desktop Sync" sections.
I've been working on unlocking Native Executables for a really long time now. Ever since I started this thread on XDA. I know it has been possible to run native executable using Full Unlock. But Full Unlock is only possible on WP7 devices with unlocked bootloaders. With the introduction of WP7 Root Tools Policy Unlock v2 also devices which have only Interop Unlock can now run these programs! But that was not the only goal. This unlock has become a prestige-project for me. Because I wanted to fully understand and control the WP7 Policy Engine. I now finally succeeded in doing this
So, is Policy Unlock v2 the same as Full Unlock?? No. But almost! Unfortunately, Policy Unlock still doesn't allow you to run Homebrew drivers, like the DFT Bluetooth stack. Later on I will try to apply the Policy Unlock hacks on the drivers too.
Tweaks
WP7 Root Tools adds a few Search-providers for Internet Explorer. You can choose it here. There are some more tweaks to customize your devices. From WP7 Root Tools 1.2 on, there are tweaks for unlocking Internet Sharing and for running Automatic Data Configuration. If your operator has blocked Internet Sharing, WP7 Root Tools can attempt to configure Internet Sharing and bypass the barrier that is installed on the phone. This probably won't work on LG devices, because their drivers don't support Internet Sharing. This unlock is only meant to unlock the operator barrier. Running Automatic Data Configuration can be useful when you switched 3G network and your phone has wrong settings for the data connection or the settings have become otherwise defective. If you have more ideas to add to this page, leave me a note.
Accent Color Editor
Add your own accent colors and select colors in real-time. Fully compatible with WP7.8.
Multi-language
The current version supports 18 languages: English, Dutch, Russian, German, Portuguese, Chinese, Hungarian, Czech, Spanish, Slovak, Polish, Italian, Greek, French. And these languages are available in separate downloads: Turkish, Arabic, Albanian and Serbian. The translations are done by volunteers and some elements by translation-engines. So the translations may not be perfect. Following versions will improve and add more translations.
For developers
I also created an SDK for developers, who can use to profit from Root Access. It provides a way to gain access to the filesystem and the registry (and more) from their managed Silverlight application. No need to worry about COM interop and C++ anymore! The package contains a read-me with short instructions. More details and examples will follow soon here on this site!
The new WP7 Root Tools has Policy Unlock v2 to unlock Homebrew Native Executables. You can do that using the WP7 Root Tools Explorer. But if a developers want to use such binaries in an app, it would be very user-unfriendly if the user needed to unlock these binaries manually. For this purpose I added functionality in the WP7 Root Tools Policy Editor. When an app is give Root Access, it will scan the app for a file called RootAccess.xml. If present, the xml is parsed and the binaries that are listed will automatically be given Root Access too. This is the format for RootAccess.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<RootAccess>
<Executable File="Native\NativeApp.exe" />
<Executable File="Native\NativeWinApp.exe" >
<Destination Path="\Windows\NativeWinApp.exe" />
</Executable>
<Library File="Native\NativeLib.dll" />
<Library File="Native\NativeWinLib.dll" >
<Destination Path="\Windows\NativeWinLib.dll" />
</Library>
</RootAccesss>
Take these notes into account:
The Destination paths are optional
Libraries are signed in Source and Destination
Executables are signed in Source and Destination
Executable gets policies in Source and Destination
File-path-attribute-value is relative to app path
Destination path is absolute
The first app that makes use of this feature is Ultrashot's WMDC Launcher, which can be used for Desktop Sync, as described in the next section. Ultrashot will soon make Opera Mini compatible with Policy Unlock too.
Desktop Sync
Ultrashot has released WMDC Launcher some time ago. Back then it was only possible to use that on devices with Full Unlock. With the introduction of Policy Unlock v2, it is also possible to run the app on devices that are compatible with WP7 Root Tools. Ultrashot has added RootAccess.xml to the xap-package, so the app will automatically be configured when it is given Root Access. Warning: it may take a while to apply on all unlocks, so be patient and let WP7 Root Tools do its job.
After WMDC Launcher is installed, given Root Access and lauched, you can use it to sync file-system and registry with your PC. On the PC you need to have Zune installed and running, and you need to have Windows Mobile Device Center installed and running. After that you Windows Phone will show up as Mobile Device in Windows Explorer.
For unrestricted remote Registry editing you can use Registry Workshop, or similar. In the registry editor you have to connect to the Mobile Device.
Thanks!
Special thanks to these people:
HD2Owner: for a lot of patience, learning me how to make my own test-ROM's.
Ultrashot and Cotulla: for a lot of nice hacking-chat-sessions and exchange of ideas.
CeesHeim: for providing a test-device.
AndrewSh, Ondraster and many others: for moral support.
Thanks to these people for helping with the translations: AndrewSh, HD2Owner, Paulo Santos, Reker Chen, Balcsida, Tukacs Gábor, Pavel "Paulos" Valach, Esteban Reche, David E. Salazar Paris, Brano Grenuš, Budniu, Fabio Di Peri, Chemeng, Alexandre Thouvenin, Orhan Bozkurt, Hassan Selim.
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)
0.9 - 2012/03/28 - Complete rewrite of the app (many device supported, full root access, policy-editor, etc)
0.10 - 2012/09/02 - Many user interface enhancements, Multi-file operations added, Improved performance in file-explorer, Shell handling added in file-explorer, better error handling and reporting and lots of small bug-fixes.
0.11 - 2012/09/03 - Bug-fixes and better device support.
0.12 - 2012/11/12 - Policy Unlock v2, 16 languages, launch apps from applist, applist also includes all system-apps now, advanced file-system-search, advanced registry-search, certificate Stores, tweaks-section, many bug-fixes and performance improvements.
0.13 - 2012/12/04 - Many bug-fixes and performance-improvements.
1.0 - 2013/01/05 - Bug-fixes and User Interface-improvements.
1.1 - 2013/03/26 - Added Accent Color editor and bug-fixes
1.2 - 2013/05/07 - Added color values to Accent Color editor, improved data-connection speed tweak, added Internet Connection Sharing unlock, added Automatic Data Configuration function, added shell-handler in Explorer for provxml-files, removed wrong buttons on Device tab, disabled cache for filesystem and searches, removed ads for better Root Tools experience
- Reserved -
- Reserved -
I have a question - can I add my cert to store (authority store, though I don't know which) in order to acquire ability to install self-signed cabs? My LG Panther has locked bootloader, so it looks like the only way to update at least to 7004.
Useless guy said:
I have a question - can I add my cert to store (authority store, though I don't know which) in order to acquire ability to install self-signed cabs? My LG Panther has locked bootloader, so it looks like the only way to update at least to 7004.
Click to expand...
Click to collapse
Nope, not quite, I am not best to describe the full problem but essentially there's another certstore stored on the device, when phone boots in to update mode it uses that cert store located in the ROM
Sent from my Samsung Focus S using XDA Windows Phone 7 App
These are great things
Thank you my friend
Useless guy said:
I have a question - can I add my cert to store (authority store, though I don't know which) in order to acquire ability to install self-signed cabs? My LG Panther has locked bootloader, so it looks like the only way to update at least to 7004.
Click to expand...
Click to collapse
The answer is: I'm not sure. It is not possible to add certs to a store for updating. But it might be possible to change the file which keeps the certs for cab updating. It needs more research. Some of this has already been discussed here.
Heathcliff74
Really good work......like it .......
Thank you....
Did you missed all trusted ?
djtonka said:
Did you missed all trusted ?
Click to expand...
Click to collapse
I considered implementing that. But I think it is dangerous. If there will ever become some type of malware on WP7, you would be very vulnerable. So I decided not to implement such option.
Heathcliff74
You are the Boss
Does registry expolorer keeps last opened location after restart or reopen cos only File explorer can do this so far?
How to unlock the native code?
I have installed opera mobile but don't work...
Inviato da mio OMNIA 7 usando Board Express Pro
A bug or a normal behavior?
First of all, i would like to really thanks you for this great tool. I would like to just ask some questions:-
I updated my wp7root tool 0.11 using XapHandler, and Everything went ok. After that i needed to open the Office hub but to my surprise it didn't work. I did a soft-reset just to find out that my start screen is Black . To be honest i got panicked though i have an update that i can reinstall. After few mins digging i found out that certain feature in the phone a still working (like search, voice commands etc.) I used the voice command and opened Wp7root Tools 0.12 and went through Policies just to find out that almost every System Apps were untrusted including Start App. When i trusted Start App i got my Start Screen back .
My questions are:-
1. is this (the untrusted start app) a bug?
2. Is it intentional that all the System App to be untrusted? if not
3. Do you have a list of System Apps that were trusted Originally?
Hope you have answers to those q.
Thanks
djtonka said:
You are the Boss
Does registry expolorer keeps last opened location after restart or reopen cos only File explorer can do this so far?
Click to expand...
Click to collapse
Dunno which registry editor you've been using. But my registry-editor does remember its last location.
Jonny Rosworth said:
How to unlock the native code?
I have installed opera mobile but don't work...
Inviato da mio OMNIA 7 usando Board Express Pro
Click to expand...
Click to collapse
Ultrashot is working on that. It needs a little bit of tweaking to be compatible with Policy Unlock.
kurdland said:
First of all, i would like to really thanks you for this great tool. I would like to just ask some questions:-
I updated my wp7root tool 0.11 using XapHandler, and Everything went ok. After that i needed to open the Office hub but to my surprise it didn't work. I did a soft-reset just to find out that my start screen is Black . To be honest i got panicked though i have an update that i can reinstall. After few mins digging i found out that certain feature in the phone a still working (like search, voice commands etc.) I used the voice command and opened Wp7root Tools 0.12 and went through Policies just to find out that almost every System Apps were untrusted including Start App. When i trusted Start App i got my Start Screen back .
My questions are:-
1. is this (the untrusted start app) a bug?
2. Is it intentional that all the System App to be untrusted? if not
3. Do you have a list of System Apps that were trusted Originally?
Hope you have answers to those q.
Thanks
Click to expand...
Click to collapse
Ok. That's remarkable. I have no clear answer. Can you tell me which device and which ROM (stock, custom, ..) you use and which OS version and which OEM firmware?
It sounds to me that this is some form of Inception between Full Unlock and Policy Unlock (that should normally work, but I can't possibly test all different devices and unlock at forehand).
Normally only very few system apps are defined to have Root Access. And "Start" is NOT one of them. I don't have a cleanly installed device to check which apps should have Root Access, but there are really only a few. I don't understand why the Startmenu would need Root Access in your case. And it is not a bug that "Startmenu" is not having Root Access. It actually surprises me that you could fix it this way.
Heathcliff74
Hi Heathcliff74 i´ve the same thing on my rom,i am using the mirolg tangoromhttp://forum.xda-developers.com/showthread.php?t=1751911 and !updated! my old roottools with sending the xap to my email account and downloading it on my device,after update (xap deployer by ultrashoot) i had to give roottools fullacces/trusted permissions for running,as the man obove said,there is nothing of the system marked as trusted(in roottools),but all is running correctly !
Omnia7xdax said:
Hi Heathcliff74 i´ve the same thing on my rom,i am using the mirolg tangoromhttp://forum.xda-developers.com/showthread.php?t=1751911 and !updated! my old roottools with sending the xap to my email account and downloading it on my device,after update (xap deployer by ultrashoot) i had to give roottools fullacces/trusted permissions for running,as the man obove said,there is nothing of the system marked as trusted(in roottools),but all is running correctly !
Click to expand...
Click to collapse
Just to be clear: You do NOT have a problem with missing Startmenu, right?
Because most system apps should NOT have Root Access. If your system apps do NOT have Root Access, but everything works fine, then there is NO problem!
Heathcliff74 said:
Dunno which registry editor you've been using. But my registry-editor does remember its last location.
Ultrashot is working on that. It needs a little bit of tweaking to be compatible with Policy Unlock.
Ok. That's remarkable. I have no clear answer. Can you tell me which device and which ROM (stock, custom, ..) you use and which OS version and which OEM firmware?
It sounds to me that this is some form of Inception between Full Unlock and Policy Unlock (that should normally work, but I can't possibly test all different devices and unlock at forehand).
Normally only very few system apps are defined to have Root Access. And "Start" is NOT one of them. I don't have a cleanly installed device to check which apps should have Root Access, but there are really only a few. I don't understand why the Startmenu would need Root Access in your case. And it is not a bug that "Startmenu" is not having Root Access. It actually surprises me that you could fix it this way.
Heathcliff74
Click to expand...
Click to collapse
Thanks for the quick answer!
Sry i didn't menssion that i have an original HTC ROM, with dev. unlock and introp-unlock installed. My device is HTC HD7, Os version 7.10.8773.98 and OEM firmware 2250.21.51101.
Hope those info will help you. I will try to make a video clip reproducing the event, hopw that will help you even more.
Yours
Omar
kurdland said:
Thanks for the quick answer!
Sry i didn't menssion that i have an original HTC ROM, with dev. unlock and introp-unlock installed. My device is HTC HD7, Os version 7.10.8773.98 and OEM firmware 2250.21.51101.
Hope those info will help you. I will try to make a video clip reproducing the event, hopw that will help you even more.
Yours
Omar
Click to expand...
Click to collapse
Hm. The fact that you have a stock ROM makes this only more weird. I still can't think of a possible explanation.
Did you toggle Root Access for system apps before the problem occurred? Any other remarkable things you've done with your phone that may explain this?
Did you use earlier versions of WP7 Root Tools without problems?
Sry,yes i ahve absolutely no problems,everything works fine,i was only not sure if the systemapps must have no permissions
Heathcliff74 said:
Hm. The fact that you have a stock ROM makes this only more weird. I still can't think of a possible explanation.
Did you toggle Root Access for system apps before the problem occurred? Any other remarkable things you've done with your phone that may explain this?
Did you use earlier versions of WP7 Root Tools without problems?
Click to expand...
Click to collapse
Hi again!
No i didn't toggle it Before the problem. I just installed it then when i tried office, it didn't work and then i found out about the problem. And to be honest i really didn't do anythink remarkable either. My privous experiance with WP7Root Tools and really good, didn't have any problem Before.
Please check your PM i sent you a link to the video clip i did about the problem. OBS!!! No sound
Yours
Omar
Awesome and great job.... Your hard work is very much appreciated!!
WP7 Root Tools v 0.12 alpha updated just fine and is functioning perfectly on my HD7 running Deepshining 7.8.
Thank you!
So someone flashed this new rom? What changes? I translated from china lumia 900's forum, here results.
1 used the State Bank 2175.2905.8858.12480 version as mastering.
The 2. Transplantation Lumia900 latest 2175.2907.8858.13030OEM.
3. Latest FULLUNLOCK V4 unlock procedure.
4. Using latest unlocking supporting software the Root rights management, gravity sensor, XAP deployment, file management, WM Device Center, the search key settings and Quick Start 7 software, and all models have added language to facilitate domestic players to use.
5. Supports XBOX game support IE deploy, support for unlimited XAP deployment of PC.
6. Delete multiple languages, or English only reserved yet.
Other registry optimization, debug mode, the default time zone correction.
If you deploy third-party software requires full unlock permission, be sure to set it as a trusted Root rights management, or it may not work properly, no matter what the time, Root permissions to manage the software, you can not delete, or may some other unknown problems. The first time after the start of the Brush to wait a minute or a the Welcome Message pop-up in use. Remember! ! !
http://translate.google.com/translate?hl=ru&sl=auto&tl=en&u=http%3A%2F%2Fwww.wpxap.com%2Fthread-564190-1-1.html
http://www.wpxap.com/thread-564190-1-1.html
2907 is MX (Mexico?) country variant. Anyway works fine for me, better than 2905. Faster and more stable.
2175.2907.8858.13030
wow that's great! downloading!!!!!!!!!!! :fingers-crossed:
Hi there,
can you tell me what's the difference between 12480 and 13030 firmware?
In my custom rom i used the 12480 because it's the latest offical rom for all countrys...
13030 is only for Mexico?
Any recommendations?
Ok, somebody help me out here. I might be stupid. NaviFirm doesn't show this ROM for me. Is there a downloas link on the chinese web page somewhere that I cannot seem to find?
Even the Mecixo one has all languages in.