Related
Hello everybody!
I have FW4, VS2010 Ult, XNA Game Studio 4, ExpressionBlend 4. I want to start development for WP7 and found MS' toolchain (467Mb ISO!), but it's huge! (and no separate components is available). What else do I need to develop for WP7? Guessed I need phone emulator and some libraries/SDK, but cannot find appropriate packages. Can somebody help me, please?
Also, do I need unlocked image? What exactly is locked in emulator?
Thanks in advance.
The only basics you really need Visual Studio, and this download which is the Developer Tools Package, it contains all the files, the emulators, etc
http://www.microsoft.com/downloads/...cf-a63a-4f97-952c-8b51b34b00ce&displaylang=en
One thing you should certainly take a look at is the Silverlight for Windows Phone Toolkit, which you can get here:
http://silverlight.codeplex.com/releases/view/55034
It's stuff that really should be in the main SDK download, but it simply isn't.
In this video i show you how to jailbreak and sideload apps to your windows phone 7 device. This procedure should work on any WP7 device and not just the HD2
Before Doing Anything You Need To Install The WP7 SDK So That Your Computer Can Connect To Your Device
WP7 SDK
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=04704acf-a63a-4f97-952c-8b51b34b00ce
ZUNE SOFTWARE
http://www.mediafire.com/?pesqg3asdoghea3
WP7 Unlock Tools
http://www.mediafire.com/?r3cx4mfeecuieo0
How To Install WP7 (Windows Phone 7) On Your HTC HD2
http://www.youtube.com/watch?v=Nac3Fnf-lY4
EDIT: Whoops meant to post this on the other thread. Going to put it there instead...
http://forum.xda-developers.com/showthread.php?p=10661354#post10661354
Hi Tom - thanks for this, it worked fine for me yesterday. Today, having done some changes to my app, I tried again and it won't work. Got a message on the phone (Samsung Omnia 7) saying that Microsoft had revoked the application!
I have applied and paid for App Hub registration (over a week ago) but not received it yet, so I was just wanting to try things out in the meanwhile.
Cheers.......Wilf Healy
Please ignore my previous post....
Hi again Tom - mea culpa. I had not run ChevronWP7.exe correctly! It's fine now.
Cheers...........Wilf Healy
Great stuff!
Hi Tom,
This is great stuff, many thanks for this. I just bought a HTC Surround (AT&T locked) and I'm in the process of unlocking it. My question is can I use either of of the ROMs (android or WP7) on my HTC Surround?
Thanks
hmmm, Tom's XAP installer keeps giving me error messages -
************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SmartDevice.Connectivity, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.SmartDevice.Connectivity, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
Is this to do with zune? or my phone? It's a HTC Mozart that i just unlocked with the chevron tool...
TIA!
Can't unlock Omnia M by any method . It's version is 8773 preloaded from company
bvneet said:
Can't unlock Omnia M by any method . It's version is 8773 preloaded from company
Click to expand...
Click to collapse
dude, this thread is over a year an a half old and didn't need the bump!
it is miss leading tho as it wont work with every device but that the way it is
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
UNLOCKS LISTED FROM MOST TO LEAST POWERFUL, MORE POWERFUL INCLUDES LOWER LEVELS. THIS IS NOT A CARRIER UNLOCK THREAD.
Dell (1st Gen)
Full Unlock: No method yet
Root Unlock: No method yet
Interop Unlock: No method yet
Developer Unlock: Two (was three) methods:
* Register for AppHub account to sideload 10 apps ($99 a year)
* Register for AppHub student to sideload 3 apps (Free, must be a student)
* Purchase Chevron Labs Token to sideload 10 apps (Tokens have sold out, old tokens valid until July 2012)
HTC (1st Gen)
Full Unlock: Via custom ROM's
Root Unlock: Per app via Root Tools (v1 drivers required), Per app via HtcRoot Project (v0 drivers required)
Interop Unlock: Via Heathcliff74's unlock pending driver version
Developer Unlock: Two (was three) methods:
* Register for AppHub account to sideload 10 apps ($99 a year)
* Register for AppHub student to sideload 3 apps (Free, must be a student)
* Purchase Chevron Labs Token to sideload 10 apps (Tokens have sold out, old tokens valid until July 2012)
HTC (2nd Gen)
Full Unlock: No method yet
Root Unlock: No method yet
Interop Unlock: No method yet
Developer Unlock: Two (was three) methods:
* Register for AppHub account to sideload 10 apps ($99 a year)
* Register for AppHub student to sideload 3 apps (Free, must be a student)
* Purchase Chevron Labs Token to sideload 10 apps (Tokens have sold out, old tokens valid until July 2012)
LG (1st Gen)
Full Unlock: No method yet
Root Unlock: Per app via Root Tools
Interop Unlock: Via OEM diagnosis tool/registry editor
Developer Unlock: Three (was four) methods:
* Via OEM diagnosis tool/registry editor to sideload unlimited apps (Free, works on all firmwares)
* Register for AppHub account to sideload 10 apps ($99 a year)
* Register for AppHub student to sideload 3 apps (Free, must be a student)
* Purchase Chevron Labs Token to sideload 10 apps (Tokens have sold out, old tokens valid until July 2012)
Nokia (2nd Gen)
Full Unlock: Phones with the Qualcomm bootloader (Q&A)
Root Unlock: No method yet
Interop Unlock: Phones with the Qualcomm bootloader (Q&A)
Developer Unlock: Two (was three) methods:
* Register for AppHub account to sideload 10 apps ($99 a year)
* Register for AppHub student to sideload 3 apps (Free, must be a student)
* Purchase Chevron Labs Token to sideload 10 apps (Tokens have sold out, old tokens valid until July 2012)
Samsung (1st Gen)
Full Unlock: Via custom ROM's
Root Unlock: Per app via Root Tools
Interop Unlock: Via WindowBreak/Heathcliff74/voluptuary unlocks (Must be prior to KK2 firmware)
Developer Unlock: Three (was four) methods:
* WindowBreak to sideload unlimited apps (Free, also Interop Unlocks. Firmware dependant)
* Register for AppHub account to sideload 10 apps ($99 a year)
* Register for AppHub student to sideload 3 apps (Free, must be a student)
* Purchase Chevron Labs Token to sideload 10 apps (Tokens have sold out, old tokens valid until July 2012)
Samsung (2nd Gen)
Full Unlock: No method yet
Root Unlock: Per app via Root Tools
Interop Unlock: Via WindowBreak/Heathcliff74/voluptuary unlocks pending firmware version
Developer Unlock: Three (was four) methods:
* WindowBreak to sideload unlimited apps (Free, also Interop Unlocks. Firmware dependant)
* Register for AppHub account to sideload 10 apps ($99 a year)
* Register for AppHub student to sideload 3 apps (Free, must be a student)
* Purchase Chevron Labs Token to sideload 10 apps (Tokens have sold out, old tokens valid until July 2012)
If any of this info is out of date please post upto date info in this thread and I will update it.
Briefcase said:
Please take in mind that there are lots of phones out there which can be interop unlocked but only by reverting back to ROMs before certain driver versions. Once such ROM is loaded, apply Interop Unlock, and let zune update to the latest version. This can be a time consuming operation. Also note that while upgradeing this interop unlocked roms will remain interop unlocked (no updates have been found which relock the phones as of yet) it might mean that certain tools (TouchExperience for example) stop working because they use exploits only available in certain drivers.
Click to expand...
Click to collapse
Thanks: Briefcase for original idea, all the great devs who work to find unlocks (Jaxbot, Heathcliff74, DFT Team, GoodDayToDie, and others)
Definitions of Unlocks:
FULL: Policy has been modified to allow for running of native executables. This lets you do things like running properly recompiled Windows Mobile code. This also allows for all the things root unlock offers.
ROOT: Policy is elevated on a per app basis via Root Tools (version 0.9) to allow Silverlight apps to run with root privilege. This lets you do things like install XAP's via IE.
INTEROP: Achieved by setting MaxUnsignedApps to 300 or greater. This allows an app to use the Interop Services capability, meaning it can use drivers on the phone. This allows for neat things like editing the registry or accesssing the file system. Just to be clear though just because your device is Interop Unlocked that does always mean that hacks that require Interop Unlock to deploy will work on your device since they may use exploites that don't exist on your device.
DEVELOPER: This allows a user to sideload apps.
Heathcliff74 does a great job of explaining this all in greater detail over HERE, or in his BLOG.
WHAT PHONE DO YOU HAVE:
Dell (1st Gen) Phones:
Venue Pro
HTC (1st Gen) Phones:
Arrive*
7 Pro
HD7
HD7S
Mozart
Surround
Trophy*
HTC (2nd Gen) Phones:
Titan
Titan II
Radar
LG (1st Gen) Phones:
Optimus 7
Quantum
Nokia (2nd Gen) Phones:
Lumia 610
Lumia 710
Lumia 800
Lumia 900
Samsung (1st Gen) Phones:
Focus
Omnia 7
Samsung (2nd Gen) Phones:
Focus Flash
Focus S
Omnia W
*CDMA only phones can only be interop/full unlocked via custom ROM's, also the Verizon Trophy can be Interop Unlocked but requires v1 drivers and extra steps to unlock.
If you got the time you should incorperate the following caveats (see my post here):
Please take in mind that there are lots of phones out there which can be interop unlocked but only by reverting back to ROMs before certain driver versions. Once such ROM is loaded, apply Interop Unlock, and let zune update to the latest version. This can be a time consuming operation. Also note that while upgradeing this interop unlocked roms will remain interop unlocked (no updates have been found which relock the phones as of yet) it might mean that certain tools (TouchExperience for example) stop working because they use exploits only available in certain drivers.
Click to expand...
Click to collapse
Because now, although better than having no list at all, it isn't complete.
Also methods for developer unlock are the same for any phone type so they could be taken apart. You migh also want to explain what the different type of unlocks are for to be very complete (link to approriate resources).
Good job. Ask mods to pin this thread to the forum's top.
P.S. May be, Q&A is better place for that topic?
sensboston said:
Good job. Ask mods to pin this thread to the forum's top.
P.S. May be, Q&A is better place for that topic?
Click to expand...
Click to collapse
Yeah, I thought about where to post this for a bit, I figured it has more to do with dev & hacking but if a mod feels it should be in the Q&A or maybe even General by all means. I just figured it might cut down on the Q's asked here in Development if it stays here.
u wrote 7 times about how to get dev-unlocked, little bit redudant, don't you think so ? what about a grid, displaying it clearer? just a suggestion
so far, well done
roqstr said:
u wrote 7 times about how to get dev-unlocked, little bit redudant, don't you think so ? what about a grid, displaying it clearer? just a suggestion
so far, well done
Click to expand...
Click to collapse
Redundant, Yes. But if I don't do it that way I can almost guarantee that someone will ask/say "So I can't developer unlock my phone? I know it says all phones can dev unlock via these means but does that include mine?"
These are the same people that ask Q's in the dev & hacking forum...
excellent vedemecum
now we have a fast look place to check unlocking status of our devices.
thank you!
How does the new version of WP7 Root Tools fit into this?
It's going to allow you to give root access on an app-by-app basis... which gives the apps you select the same level of access as a full unlock, without being a full unlock.
we will cross that bridge when we get there.
A few clarifications:
HTC gen1.5 (the CDMA phones, Sptrint's Arrive and Verizon's Trophy) are special cases.
Arrive can't be interop-unlocked at all right now, short of a custom ROM. This is because it can't use Connection Setup.
VTrophy can be IUed, but requires special instructions beyond the normal steps for pure-GSM phones.
Last I checked, there aren't any *published* custom ROMs for the Verion Trophy (not sure about the Arrive) although I know some are in development.
HTC Custom ROMs:
Up-to-date GSM phones will need their bootloaders downgraded. For gen1 phones, there are some ways to do this. If you don't downgrade first (to bootloader/SPL 3.1 or below) and try to install a custom ROM, you'll break the bootloader somewht permanently (very hard to repair).
LG phones:
The registry editing can be used for dev-unlock as well as interop-unlock. In fact, Interop-unlock is meaningless without dev-unlocking first (applies to all phones).
Samsung phones (both generations):
WindowBreak is a dev-unlock as well as an interop-unlock. You might want to distinguish it from the other Samsung interop-unlocks, which require first getting a dev-unlock somehow.
I hope to get full-unlock (I already have arbitrary-app-as-root) on HTC gen1 via the HtcUtility driver (part of HtcRoot project). But, that will take time and will only work on very old firmware (from the Mango beta days). It will also require already being interop-unlocked.
GoodDayToDie said:
A few clarifications:
HTC gen1.5 (the CDMA phones, Sptrint's Arrive and Verizon's Trophy) are special cases.
Arrive can't be interop-unlocked at all right now, short of a custom ROM. This is because it can't use Connection Setup.
VTrophy can be IUed, but requires special instructions beyond the normal steps for pure-GSM phones.
Last I checked, there aren't any *published* custom ROMs for the Verion Trophy (not sure about the Arrive) although I know some are in development.
HTC Custom ROMs:
Up-to-date GSM phones will need their bootloaders downgraded. For gen1 phones, there are some ways to do this. If you don't downgrade first (to bootloader/SPL 3.1 or below) and try to install a custom ROM, you'll break the bootloader somewht permanently (very hard to repair).
LG phones:
The registry editing can be used for dev-unlock as well as interop-unlock. In fact, Interop-unlock is meaningless without dev-unlocking first (applies to all phones).
Samsung phones (both generations):
WindowBreak is a dev-unlock as well as an interop-unlock. You might want to distinguish it from the other Samsung interop-unlocks, which require first getting a dev-unlock somehow.
I hope to get full-unlock (I already have arbitrary-app-as-root) on HTC gen1 via the HtcUtility driver (part of HtcRoot project). But, that will take time and will only work on very old firmware (from the Mango beta days). It will also require already being interop-unlocked.
Click to expand...
Click to collapse
I made a note about the Arrive in the second post already, I'll add the Trophy to the note.
I'll will clarify the whole WindowBreak thing, I have it listed that higher level unlocks include the lower level abilities but I suppose it would be a good idea to mention that WindowBreak doesn't need dev unlock first.
I plan to note full privilege app escalation once that is available but I don't want to confuse people for now.
I'll have to give ya a thanks tomorrow, I seem to have maxed myself out today but thanks for all the good points.
Great idea & post! Would hit the thanks button if they had it on the WP7 app.
Sent from my Kick Ass Lil Radar using XDA Windows Phone 7 App
Congrat for the idea. Good work, I read the thread twice a day and I wait for a news. THX (+)
voluptuary;23445194[COLOR="Red" said:
*[/COLOR] CDMA only phones can only be interop/full unlocked via custom ROM's, also the Verizon Trophy requires extra steps and specific drivers to unlock.
Click to expand...
Click to collapse
This is not completely true. Arrives can only be IU with custom ROM. The Verizon Trophy with v1 drivers stock ROMs CAN be IU but you follow a slightly different procedure (Heathcliff has it in his first post here). I came up with this procedure and several (myself included) have used it.
---------- Post added at 02:11 PM ---------- Previous post was at 02:07 PM ----------
Well, technically what is stated is true since the VZW Trophy is not a CDMA only but CDMA and GSM, but it is not clear what is written implies the Trophy is fine with Stock as long as v1 drivers are used.
LiFePo4 said:
This is not completely true. Arrives can only be IU with custom ROM. The Verizon Trophy with v1 drivers stock ROMs CAN be IU but you follow a slightly different procedure (Heathcliff has it in his first post here). I came up with this procedure and several (myself included) have used it.
---------- Post added at 02:11 PM ---------- Previous post was at 02:07 PM ----------
Well, technically what is stated is true since the VZW Trophy is not a CDMA only but CDMA and GSM, but it is not clear what is written implies the Trophy is fine with Stock as long as v1 drivers are used.
Click to expand...
Click to collapse
I'll try to make it a little more clear.
Leapo said:
How does the new version of WP7 Root Tools fit into this?
It's going to allow you to give root access on an app-by-app basis... which gives the apps you select the same level of access as a full unlock, without being a full unlock.
Click to expand...
Click to collapse
While it gives root access to Silverlight apps, it won't be the same as full unlock. You will not be able to run native executables etc.
thx alot for this topic
simple request can u add the unlocking topic of each non released yet phone
Dr.Mazika said:
thx alot for this topic
simple request can u add the unlocking topic of each non released yet phone
Click to expand...
Click to collapse
If it's not released then how will we know what can and can't be done on it yet? I think it's safe to just assume that if a phone isn't out yet and thus not in the hands of a dev the status of unlocks of any kind aside from official dev unlocks would be 'unknown'
Wow, coming from Android this is a complete 180
Just a quick question, but I have a Samsung Omnia W and did a succesful Windowbreak on it so are you saying that it is now Interop as well as Developer unlocked ??
If that is so then I wonder why it is that the majority of 3rd party apps I have managed to succesfully put on my phone do not work.
Apps such as Metro Themes, Advanced Configuration Tool and WP7 Root Tools. I am basically looking to apply custom colours to my tiles and background and have not been able to do it at all.
I thought a Developer unlock would allow me to do all these things ?
I must be missing something
Cheers for a great guide !! Really makes things much more clear !!
Cheers, LL13-
Download: www.wp7roottools.com
Today I am proud to announce the immediate availability of WP7 Root Tools 0.9 alpha and WP7 Root Tools SDK 0.1!
WP7 Root Tools 0.9 brings true Root Access to devices with stock ROM's, but it also works on devices with custom ROM's and Full Unlock. Your device needs to be Interop Unlocked to use WP7 Root Tools!
This is still an alpha-release, because there are a lot of new hacks and the tools are still not feature complete! I have rewritten about 75% of all code from the previous release. So before you install WP7 Root Tools you should make a backup of your device. WP7 Root Tools will make changes to system settings and, although this has been tested, it is still possible that a problem occurs. In that case you want to have a recent backup of your device. Installing WP7 Root Tools will be your own responsibility. The author of WP7 Root Tools and the SDK cannot be held responsible for any damages caused directly or indirectly by installing and using WP7 Root Tools or the SDK!
Windows Phone is a closed system to protect the user and his/her personal data from malware and to protect the intellectual property of the developers. The downside of this closed system is that homebrew developers are very limited in their ability to control and tweak a Windows Phone device. 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!
WP7 Root Tools 0.9 now has a File Explorer, Registry Editor, Certificate Installer and a Policy Editor! Thanks to true Root Access on Windows Phone, this new version of WP7 Root Tools will work a lot faster than previous releases and it supports a lot more devices!
WP7 Root Tools should work on these devices:
- Samsung first and second generation devices
- 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 generation devices with custom ROM and Full Unlock
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. 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.
I also created an SDK, which developers 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! Over the last days Rafael Rivera from the Chevron WP7 team has tested the SDK and he is finishing up the first homebrew app that will use my SDK. He is planning to release his Backup-app soon.
I also need to thank some people for making this possible:
- My wife! (for having to put up with me while doing all this hacking!)
- YukiXDA (for helping me with research on policies)
- Justin Angel (for sending me a NOKIA)
- Cees Heim (for supplying an HTC device for testing)
- Rafael Rivera and Chevron WP7 team (for pioneering WP7 Unlocking)
- HD2Owner (for helping me make custom ROM's for testing)
- fiinix (for helping me with research on policies)
- Ultrashot
- xb0xm0d
- AndrewSh
- Ondraster
- Barin
- Football
- Cmonex
- GoodDayToDie
- Jaxbot
- Dennis Wilson
I will update the guides and manuals on www.wp7roottools.com and here on XDA in the next coming days. I need some time to update all of it.
Have fun with Homebrew now!
Heathcliff74
reserved*****
reserved***** (2)
reserved***** (3)
reserved***** (4)
thank you for your hard work
SO AWESOME!!! Thank You SOOOO Much!!!
big thx 4 all your work man!thxthxthx...
Sent from my OMNIA7 using Board Express
Previous Versions
Thanks for your great work. Do we need to uninstall previous versions before installing the latest version? I have .8, how do I install .9?
Great news, thanks a lot! Successfully installed on Focus and Surround, no problems at all.
But I've tried "BT file transfer" and "Opera mini" (after install I've enabled "trusted" status for the apps): both apps not working properly. Should we expect updated versions of these apps (built with your SDK) or it's some another issue?
Fantastic work, Heathcliff74. Oh man, this is going to be awesome.
Suggestion: use one of your reserved posts to compile a list of trusted apps that benefit from policy elevation.
Two that I've found so far (one of mine):
Root Webserver (in my sig) - runs better with Root Tools than ever before.
TouchXperience - gives way more access through WPDM.
Two others that are in development:
LockWidgets - the preview build has some bugs, but it can be run with Root Tools.
XapHandler - the test build has some known issues (can't install or update if the app is already installed) but fresh install works at least some of the time.
Awesome work! I can confirm that the install works perfectly on an LG Quantum.
Big day!
I need some free space in C:/ to make backup.
sensboston said:
Great news, thanks a lot! Successfully installed on Focus and Surround, no problems at all.
But I've tried "BT file transfer" and "Opera mini" (after install I've enabled "trusted" status for the apps): both apps not working properly. Should we expect updated versions of these apps (built with your SDK) or it's some another issue?
Click to expand...
Click to collapse
WP7 Root Tools will give Root Access to Silverlight apps. DFT BT and Opera Mini both use native executables. You can't give the executables root access with WP7 Root Tools (in fact, you only give the launchers Root Access). These apps could possibly be recompiled to run under TaskHost.exe (as all Silverlight apps do), but I'm not sure about the inner workings of the apps. You'd have to ask the developers.
I will investigate this matter. With all the hacks I have now, I should be able to give Root Access to executables too, but that needs more research.
Ciao,
Heathcliff74
@sensboston: Those tools both require additional native binaries. WP7 Root Tools elevates apps, including all the DLLs they load (which is how the SDK works - it's a homebrew DLL, similar to the old Native.dll and company). However, it doesn't work with out-of-process binaries. Opera requires an EXE (which is obviously its own process) and BT File Transfer requires a driver.
In theory, supporting these would be possible. They'd need to be signed, and the certificates added to the Code Integrity store, but that's already possible. However, they'd also need new policies added. The current version of Root Tool only supports modifying the policies for installed TaskHost (Silverlight/XNA, possibly including some native code) apps, not adding policies for other apps.
BTW, although it's very limited, it turns out that Application.GetResourceStream can be used on files outside the app (with sufficient permissions). That means, if you want to write an app that only needs to access existing files at known locations, you don't even need to mess with native code... although the Root Tools SDK will make it quite easy to do such apps anyhow.
Thanks HeatCliff
Thanks man for this wonderfull pice off work
Heathcliff74 Installed on My Omnia 7 Thanks a lot for your Hard Work
JamesAllen said:
Thanks for your great work. Do we need to uninstall previous versions before installing the latest version? I have .8, how do I install .9?
Click to expand...
Click to collapse
You can just reinstall. No need to uninstall. From this new version on (version after 0.9) you better do an "UPDATE". Not all xap-installers support updating. A lot of them will do a full-install-cycle. If you do a full-install-cycle, you'll loose the permissions and you will have to do the 2-phase-install sequence again. If you do an in-place-update, you will keep the permissions and everything keeps working as expected.
Heathcliff74
Damn, doesn't work for me.
Verizon HTC Trophy
OS 7.10.8107.89
Firmware: 2305.13.20110.605
Hardware: 003
Thanks for the work! Hopefully I'll see support later. I probably updated to the HTC v2 drivers at some point.
dreamcaster012 said:
Damn, doesn't work for me.
Verizon HTC Trophy
OS 7.10.8107.89
Firmware: 2305.13.20110.605
Hardware: 003
Thanks for the work! Hopefully I'll see support later. I probably updated to the HTC v2 drivers at some point.
Click to expand...
Click to collapse
Hmm. are you interop unlocked? I'm no expert with HTC's but that versionnumber looks like your drivers are not that new and could possibly be supported. If you are not Interop Unlocked, then read the opening post of my Interop Unlock thread. At the end of that post is a section specifically for Verizon Trophy's
Heathcliff74