Tried all steps as u said
Uploaded with ImageShack.us
That´s why im asking a way to check if my phone is really unlocked, cause it seems not, even after windowbrake "runned" well.
The WindowBreak Project
- Thread starter Jaxbot
- Start date
-
- Tags
- unlock windowbreak
Tried all steps as u said
Uploaded with ImageShack.us
That´s why im asking a way to check if my phone is really unlocked, cause it seems not, even after windowbrake "runned" well.
does this new hack require the chevron? or, does it work without any other unlock tool ? i dont see this anywhere unless i missed it.
You must not have looked very hard...
No, it does not require Chevron. It's something completely different, though it achieves the same thing (plus interop unlock)
Please try the official dev tools. They include a program called XapDeploy.exe (in Start menu as "Application Deployment"). You don't have to run it as Admin, but you do need to have Zune running, connected to the phone, and the phone ready to use (not sleeping or at the lock/wallpaper screen).
If you're still getting an error off that program, then the odds are the unlock didn't work for you (you could try describing the steps you took again).
If you're still getting an error off that program, then the odds are the unlock didn't work for you (you could try describing the steps you took again).
new unlock tool
i have read this post and may have missed it somewhere. My question is does this new unlock work without having chevron , or does it need chevron unlocked already.
---------- Post added at 04:10 PM ---------- Previous post was at 04:08 PM ----------
i have read this post and may have missed it somewhere. My question is does this new unlock work without having chevron , or does it need chevron unlocked already.
---------- Post added at 04:10 PM ---------- Previous post was at 04:08 PM ----------
ok, ooops maybe i did miss it. then please ignore the last post. forgive my blindness as the post can sometime run together. thank you very much for your quick reply .
i SWARE i´m not a complete dumb and probably stucked at a small detail.
i did install, uninstal and reinstall all MS devkits.
there is just NO "XapDeploy.exe" in my 3 HDs
i already read lots of step by step posts and had past experience on unlocks (my phone was unlocked by chevron before nodo).
is there someone patient enough to trying help me? i may give even teamviewer access, because its really hard when you dont understand exactly the order of all required steps to make it work...
for lots of people here seems so easy... but... i´m in difficult!
Thanks and sorry about my "sad history"
Last edited:
I can extract a xml file to /Application/Install/[AppGuid]/
but can't extract to /Application/Install/[AppGuid]/Install/
Is there a policy to prevent that ?
but can't extract to /Application/Install/[AppGuid]/Install/
Is there a policy to prevent that ?
i SWARE i´m not a complete dumb and probably stucked at a small detail.
i did install, uninstal and reinstall all MS devkits.
there is just NO "XapDeploy.exe" in my 3 HDs
i already read lots of step by step posts and had past experience on unlocks (my phone was unlocked by chevron before nodo).
is there someone patient enough to trying help me? i may give even teamviewer access, because its really hard when you dont understand exactly the order of all required steps to make it work...
for lots of people here seems so easy... but... i´m in difficult!
Thanks and sorry about my "sad history"
Mine is in:
C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v7.1\Tools\XAP Deployment
Are you sure you have the Windows Phone SDK installed? Emulator and everything?
There shouldn't be... I believe I've extracted there before.
If you're trying to overwrite a file, and that file is in use (app is running), it will be locked.
If you're trying to install an app, that just won't work. The file will extract but that doesn't mean the app will install.
If you're trying to install an app, that just won't work. The file will extract but that doesn't mean the app will install.
Hypothetically, you could invoke the app installation process from within the phone directly. However, the only way that we know how to do this on stock ROMs is using provxml to install Marketplace-signed apps. It *should* be possible to install unsigned apps when we can run provisioning with maximum permissions, but nobody has made it work yet.
There are custom ROMs (for HTC, since the bootloader can be unlocked) that support installing XAPs directly. You could also try either invoking the installation process (tweak some stuff in HKEY_CLASSES_ROOT, maybe?) or have an opp call into the XAP installation / AppMgr libraries directly. I suspect in either case there would be permissions problems, though.
There are custom ROMs (for HTC, since the bootloader can be unlocked) that support installing XAPs directly. You could also try either invoking the installation process (tweak some stuff in HKEY_CLASSES_ROOT, maybe?) or have an opp call into the XAP installation / AppMgr libraries directly. I suspect in either case there would be permissions problems, though.
Hey Jaxbot, I did some testing and, for whatever reason, heathcliffe's unlock.xml works 100% of the time, and the windowbreak.xml only works like 50% of the time... You should include both in the .zip you have on the website. If anyone failed with the windowbreak one, download the zip file on your computer, go to the /../../../provxml/ directory in it, place heathcliffe's unlock.xml in there, then email the zip to the email address on your phone. Open the zip on your phone and proceed as you would with windowbreak, but choose "unlock" instead of windowbreak.
That doesn't make sense, considering as both our XMLs do exactly the same thing; mine just has some extra bits in it that fix Visual Studio settings and stuff.
Heh, glad it's not just me...
I'm seeing the same thing as shinkstor. Putting heathcliff's xml file on the phone (using your method) works every time, and performs the registry edits that are called for in the xml file. The windowbreak xml file doesn't seem to be making ANY modifications to the registry when it's read by the GPRS tool.
I know it doesn't make sense, but something is going wrong, and everything I've checked points to the problem being within the Windowbreak xml file.
I'm seeing the same thing as shinkstor. Putting heathcliff's xml file on the phone (using your method) works every time, and performs the registry edits that are called for in the xml file. The windowbreak xml file doesn't seem to be making ANY modifications to the registry when it's read by the GPRS tool.
It says "Diagnosis (ver.0103)"
Like I said, heathcliff's xml file performs an interop unlock every time, so the Diagnosis app is doing its job here. Whatever extra stuff is in your xml file is throwing it for a loop, I guess.
Last edited:
Really odd, because it works 100% for me. Wonder if it has to do with my ADC implementation, then.
What if you split the xml into 2 files? Something like:
Step One.xml
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\Comm\Security\LVMod">
<parm name="DeveloperUnlockState" value="1" datatype="integer" />
</characteristic>
<characteristic type="HKLM\Software\Microsoft\DeviceReg">
<parm name="PortalUrlProd" value="" datatype="string" />
<parm name="PortalUrlInt" value="" datatype="string" />
</characteristic>
<characteristic type="HKLM\Software\Microsoft\DeviceReg\Install">
<parm name="MaxUnsignedApp" value="2147483647" datatype="integer" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\System\AutoDataConfig">
<parm name="RunADC" value="1" datatype="integer" />
</characteristic>
<characteristic type="HKLM\System\AutoDataConfig">
<parm name="ConfigurationStatus" value="0" datatype="integer" />
</characteristic>
<characteristic type="HKLM\System\AutoDataConfig">
<parm name="Attempt" value="0" datatype="integer" />
</characteristic>
<characteristic type="HKLM\System\AutoDataConfig">
<parm name="MaxAttemptsAllowed" value="3" datatype="integer" />
</characteristic>
</characteristic>
</wap-provisioningdoc>This way you can diagnose what part is not working.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
99"What am I doing, why am I here, what is this about, and where am I going with this."
Hello all. After dealing with rumors, rumors of rumors, and the like, I've finally managed to disclose something I hold very dear to me: the WindowBreak project.
As the name suggests, this is a jailbreak project for Windows Phone 7. I started something a while back that had little success, but through the months, I've managed to figure out something that should bring light into the Windows Phone jailbreaking scene.
Real quick, though:
What this is: A project, with information about some interesting exploits I found, and a call for the community to dive in.
What this isn't: A full fledged jailbreak. Please don't post replies such as "when will XXXX device be supported". It just wastes time, and I assure you, I want every device included.
It also is not a full unlock. Just interop.
The details
So here's the sitch. We all know how Heathcliff74's interop unlock works. XAP files are just ZIP files, and ZIP files can have entries that allow extracting in parent directories.
Interesting thing is, this can be done using the ZipView application, which normally stores data in \Application Data\Volatile\Zipview\<random id>
Thus, creating a directory in a ZIP file called ../../../../provxml will copy all those files into the \provxml\ folder upon extraction.
See what I did there?
Limitations
Of course, there are limitations.
1) We cannot extract into \Windows\. There's a policy that prevents it.
2) The bad one: We can only extract known MIME types, at least to my knowledge. This is because the files are only extracted when they are clicked on in ZipView. And clicking on a .dbz file, for example, will just say the file type is not supported. Bummer.
What we can do...
As mentioned above, this can be used for a fresh out of the box jailbreak for Samsung devices, using provxml. Here's a video of that:
Try it yourself: with a Samsung device, go to http://windowsphonehacker.com/windowbreak and press WindowBreak Me.
In theory, this would be all we need to jailbreak most Windows Phone devices. Unfortunately, Nokia and HTC devices block the registry entries in provisioning files. I'm not sure what the extent of this "whitelist" (or is it a blacklist?) is, and details/tests on this would be appreciated.
What needs to be done...
Nokia: I don't have a Nokia device, but I've been working a great deal on figuring out how to crack it's shell, and have a couple of ideas. If I'm able to get my hands on a Nokia device soon, I'll try some of these unorthodox exploits out, otherwise I'll need some daring volunteers.
HTC: I do have an HTC device, but I can't figure out how to extract the files for the Connection Setup program. If someone can give me details on what the password encryption is on it, etc, for the HTC interop unlock, that would be much appreciated.
Other devices: Not a lot of demand for these (and LG needs no jailbreak, since it has MFG), but if something comes up, feel free to share where the provisioning files exist and I'll see about "windowbreaking" them.
So this is my little project, and I hope the details I'm sharing will lead to further development. My personal device (Samsung Focus) is easily interop unlocked now, without costing me a cent. I'd really like this to be the case for everyone; I'm not saying the $9 unlock for Chevron Labs is bad, in fact, it's greatly supported homebrew. What I am saying, though, is that freedom is still possible, and regardless, any developments made here will further support interop unlocking on Chevron/apphub unlocked devices. With that in mind...
Merry Christmas.
Special thanks to: Heathcliff74 for much of the research and idea behind the exploit
All the supporting members of XDA, who bring appreciation for what we do. Thank you.14Cool! Ridiculous that I didn't think of this myself
I will send you the password of the dbz files when I get home. I don't have it here.
But the real problem for HTC and NOKIA are the whitelists. I've been working on this for the past time. And today I made more progress. I developed a new way of debugging native 3rd party dll's/drivers. U can isolate functions and call them from a test app for unit-testing. This makes testing a lot easier. This will help me find exploits much faster. I can even call the whitelist functions of HTC and NOKIA on my Samsung now Working on it right now.
Good find!!
Heathcliff746Wow. It actually worked. Changed some stuff around, added folders and files into a Marketplace XAP and then had Fiddler replace it when downloading. .. trick works, XAP installs, etc. Beautiful... just beautiful. *sob* I can really make something out of this
Nice call!
P.S. apparently i was wrong about the size check. Was pretty sure I wasn't, though. Not sure what happened, but it works right now, so I'll just not complain.4DBZ Password
030D681B-1DFC-4bd0-A72A-A9B3CCCDA653
---------- Post added at 10:30 AM ---------- Previous post was at 10:29 AM ----------
Oh and it was found here http://xdaforums.com/showthread.php?p=189168884First of all, the OS version does *not* matter here, it's all about the firmware version or bootloader version.
Second, "jailbreak" is a very ambiguous term on WP7, and one I really wish people wouldn't use, because there are multiple levels of unlocking.
The first, developer-unlock, is actually a feature of the OS and is supported by Microsoft. All phones can be dev-unlocked, but normally you have to pay for it (an AppHub account, intended for Marketplace developers, lets you unlock up to 3 phones and install up to 10 unsigned apps on each, for $99/year). Students can get a free account through DreamSpark, but only for one phone and up to three unsigned apps at once. There's another way, for $9 a ChevronWP7 Labs token lets you unlock one phone and put up to 10 unsigned apps on it. Unfortunately, those tokens are sold out and we have heard nothing on them getting any more (had to be approved by Microsoft). There are also some hacks that will dev-unlock a phone, such as WindowBreak (this thread). There aren't currently any such hacks available for HTC, though.
Next, there's interop-unlock. This means removing the 3- or 10-app limit, and also allowing the installation of apps that can use system components (drivers and long-running services) to break out of their sandboxes. These apps, commonly called "interop" apps after the ID_CAP_INTEROPSERVICES line in their manifests' that enables this capability, include things like registry editors and the HtcRoot project. All ways of getting interop-unlock are based on hacks. For Samsung phones, WindowBreak can be used to interop-unlock at the same time as dev-unlock. For HTC phones, though, you need to first be dev-unlocked before you can interop-unlock.
The third level is called "full unlock" and means the policy system that controls app sandboxing and user permissions has been disabled completely. Any app can run, and all apps run with full access to the whole device. Although this heightens the risk of malware or o accidentally damaging the device, it also allows all kinds of cool features to be added right into the phone, as well as enabling some very cool apps (including ports of WinMo apps). Currently, the only way to get full-unlock is to use a custom ROM.
In order to use a custom ROM, your device must have an unlocked bootloader. This is done by installing an alternate bootloader called RSPL, and can be made permanent by installing HSPL. You can read the DFT (Dark Forces Team, who are responsible, directly or indirectly, for almost all custom ROM achievements on WP7) threads on R/HSPL on this forum. Although all first-gen HTC phones are now supported for xSPL, be aware that it can only be installed over stock SPL (bootloader) versions on 3.1 or lower. Most fully up-to-date phones will be running SPL 5.x.
For you, in particular, you can either try interop-unlocking, or you can try installing an unlocked bootloader and a custom ROM. The first option preserves your phone data, but is less permissive in what you can do. The second option allows almost anything, but you'll have to wipe the phone and will also be at the mercy of any bugs in the custom ROMs. Additionally, either option may require rolling back the phone in some way (firmware for interop-unlock, SPL for bootloader unlock), and interop-unlock will require first getting dev-unlock (may cost money).
