Related
Now, I know no-one actually likes reading threads, and would prefer to just post a new question at the end (I'm guessing partly because the threads are so long, but that's because everyone is doing it) so I'm going to try and give solutions to as many of the issues with ChevronWP7, sideloading and anything else that's not quite working.
Note, none of this is to facilitate any kind of software pirating (we will notice if it gets discussed, and it's in the forum rules - and kinda immoral).
Firstly, Windows Vista (I think SP2) or Windows 7 is required, this won't work on XP without a few hacks/tweaks, and it's not worth me writing the whole process out, plus I don't have an XP machine to hand, so I can't try things.
The most common issues can be fixed with just installing the correct software.
You NEED to have the official WP7 Developer Tools installed, they're a free download from Microsoft, and if you're planning on doing development (which is after all part of the reason for wanting sideloading) you kind of need them.
There's a guide on how to install them (provided by Microsoft) here. You only need the basic toolset from here, but installing the October update won't cause any issues.
This should solve the following exception:
Code:
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.
as well as a few other issues.
When running any of the tools, if you encounter issues, try either running the tool as an administrator or turn of UAC (for both, do a search if you've no idea what I'm on about), this may solve some issues with access rights etc.
Once you've got that installed, Chevron issues are in post #2, sideloading XAPs in #3.
ChevronWP7 Issues
With Chevron, most things are explained well in the opening post of this thread. Read it.
Chevron works by tricking your phone into thinking it's communicating with Microsoft servers, when it's actually just communicating with Chevron, this means certain web based activities may interfere (Skype for example).
The best way of finding out what's going on, is to use the following guide, it should work, if that fails, then post a question.
sushovande said:
Okay so here is *everything* I did to succeed in re-unlocking my Samsung Focus
1. Have Winphone developer tools installed
2. Connect Phone via USB
3. Wait till zune starts and sync completes
4. Verify that zune is not in a guest relationship
5. open a command prompt, type netstat -a to confirm that port 443 is not being used
6. open an admin command prompt, navigate to c:\windows\system32\drivers\etc\ then type notepad hosts and delete any references to windowsphone developer services
7. go to the settings on the phone and turn airplane mode on (so that the phone is forced to use internet via zune)
8. While the phone is still on the settings page, run Chevron with admin privileges
And it worked!
Click to expand...
Click to collapse
There's no way to know whether a device is unlocked or not until you come to sideloading, which is the point where it matters anyway. Nothing (visible) will change on the device, so don't bother looking for any changes.
WP7 devices occasionally phone home (as far as I know they only do so when connected with Zune) to check whether they should be unlocked or not. If not, they quietly re-lock themselves, and non-marketplace apps will say something along the lines of "This application has been revoked". You'll need to try unlocking again with Chevron and possibly reinstall the apps. There's not much that can be done other than legitimately unlocking your devices.
There's a sideload limit of 10 applications, though there's a version of Chevron that has this limit hacked out of it, I just can't remember where it is. For most legitimate uses, this limit should be fine (and is better than the student/DreamSpark limit of 3).
XAP Installation
A first port of call if Toms XAP Installer doesn't work is to use the official one. It does work.
If you've installed the Developer Tools linked to in the first post, you'll have it already, and should be able to sideload, if your device has been unlocked. If it hasn't you'll have issues, and you should take a look at post #2 in this thread.
Disclaimer, use this at your own risk, if this voids your warranty I’m not being held responsible, blah blah all that junk.
Well, first, thanks go out for Microsoft for releasing a support tool for Windows Phone yesterday. Inside that tool, were unreal hidden gems.
Basically they’ve created a managed wrapper over the whole update process for us, rather nice of them.
So I flashed my HTC Mozart back to RTM (7004) via a ROM update HTC ship and whipped up a little application to flash pre-NoDo (7008), NoDo (7355), NoDo update 1 (7389) & NoDo update 2 (7390) all in a single process. No I don’t care which carrier you are on, which phone you have, it’ll just update your phone accordingly.
We really have to commend Microsoft here for being able to split up the OS updates into differential packs, which saves users downloading 200+ MB updates, unlike the IFruit updates.
All you need to do is run the ChevronWP7.Updater.exe console app and follow the prompts.
Make sure you select the RIGHT language for your device. To double check what your default language is, go to Settings > Keyboard and if your selected language is displayed in the Console app, you’re good to select it. If it isn’t in the list, DON’T flash it just yet.
Now, download the following files.
x86 Operating System (32 bit)
Windows Phone Support Tools
http://download.microsoft.com/download/1/5/4/15427EAF-AD42-4E4A-8179-9A3C5483E366/WPSupportTool-x86.msi
ChevronWP7.Updater
http://www.megaupload.com/?d=G1OEGML1
x64 Operating System (64 bit)
Windows Phone Support Tools
http://download.microsoft.com/downl...E4A-8179-9A3C5483E366/WPSupportTool-amd64.msi
ChevronWP7.Updater
http://www.megaupload.com/?d=40MA6F02
Once you’ve installed the support tools and extracted the ChevronWP7.Updater.zip to the desktop, plug your phone in and wait 30 seconds.
Now start ChevronWP7.Updater.exe (this should kill Zune) and follow the prompts.
If you’re updating from Version 7004, you need to run the Updater TWICE, this needs the preUpdate before we can flash NoDo.
Again, if your language isn’t in the Chevron updater, DON’T attempt to update your phone. Some of the applications won’t work otherwise.
This “might” work for HD2 owners, haven’t tried it out just yet. If it does, report below and tell me .
There is NO revert process, again, flash at your own risk.
I flashed my Samsung Omnia 7 works fine
Big Tenks to walshie
If I do so like you suggest with my HD2 (WP 7.0.7004.0), he still asks to update the february update..
And I did it twice like suggested...
Thanks anyway!
It doesn't work for me but I still have to install the February update. Does anyone know if there is already a new rom with this update included?
Thx!
Works for me, Samsung Focus AT+T and had to run it twice to get both updates.
Source
Where does this method pull the updates from? Is it the same update being tested by AT&T for the Focus?
Didn't work for me...tried 4 times and kept getting some error, then got booted from the program...not sure what the deal is. Samsung Focus, AT&T
Sent from my SGH-i917 using Board Express
Also not working for me- Samsung Focus on AT&T. Program runs, reboots phone, seems to update, but on examination I'm still at 7004.
Sadly I should've resisted. I did this on my AT&T Samsung Focus, everything is great except I have no marketplace and no Zune functionality..
LastOttoman said:
Disclaimer, use this at your own risk, if this voids your warranty I’m not being held responsible, blah blah all that junk.
Well, first, thanks go out for Microsoft for releasing a support tool for Windows Phone yesterday. Inside that tool, were unreal hidden gems.
Basically they’ve created a managed wrapper over the whole update process for us, rather nice of them.
So I flashed my HTC Mozart back to RTM (7004) via a ROM update HTC ship and whipped up a little application to flash pre-NoDo (7008), NoDo (7355), NoDo update 1 (7389) & NoDo update 2 (7390) all in a single process. No I don’t care which carrier you are on, which phone you have, it’ll just update your phone accordingly.
We really have to commend Microsoft here for being able to split up the OS updates into differential packs, which saves users downloading 200+ MB updates, unlike the IFruit updates.
All you need to do is run the ChevronWP7.Updater.exe console app and follow the prompts.
Make sure you select the RIGHT language for your device. To double check what your default language is, go to Settings > Keyboard and if your selected language is displayed in the Console app, you’re good to select it. If it isn’t in the list, DON’T flash it just yet.
Now, download the following files.
x86 Operating System (32 bit)
Windows Phone Support Tools
http://download.microsoft.com/downl...-4E4A-8179-9A3C5483E366/WPSupportTool-x86.msi
ChevronWP7.Updater
http://blog.walshie.me/Share/ChevronWP7.Updater.x86.zip
x64 Operating System (64 bit)
Windows Phone Support Tools
http://download.microsoft.com/downl...E4A-8179-9A3C5483E366/WPSupportTool-amd64.msi
ChevronWP7.Updater
http://blog.walshie.me/Share/ChevronWP7.Updater.x64.zip
Once you’ve installed the support tools and extracted the ChevronWP7.Updater.zip to the desktop, plug your phone in and wait 30 seconds.
Now start ChevronWP7.Updater.exe (this should kill Zune) and follow the prompts.
If you’re updating from Version 7004, you need to run the Updater TWICE, this needs the preUpdate before we can flash NoDo.
Again, if your language isn’t in the Chevron updater, DON’T attempt to update your phone. Some of the applications won’t work otherwise.
This “might” work for HD2 owners, haven’t tried it out just yet. If it does, report below and tell me .
There is NO revert process, again, flash at your own risk.
I flashed my Samsung Omnia 7 works fine
Big Tenks to walshie
Click to expand...
Click to collapse
In the future, just link directly to my Blog, direct linking to the installers doesn't enable me to update them if there is an issue.
so i shouldn't be doing this if i have Samsung Focus on AT&T?
mastamind518 said:
so i shouldn't be doing this if i have Samsung Focus on AT&T?
Click to expand...
Click to collapse
If you follow the post, there are detailed instructions for Samsung Focus users.
walshieau said:
If you follow the post, there are detailed instructions for Samsung Focus users.
Click to expand...
Click to collapse
thanks it worked. shows 7390.
Focus
Worked for me too on my ATT branded, locked Samsung Focus. Now running 7390.
Have an AT&T Focus, carrier unlocked, Chevron'ed and I can't seem to update. I have tried using the "Windows Support Tool" and still no luck. See log below if it looks right
UpdateWP version 4.7.1404
Applying updates to device
Id: \\?\usb#vid_045e&pid_0710#b7d536af-3362-ca4a-6b09-6f8888553bf1#{ca3d7387-f67b-11da-bbec-8000600fe800}
SN: af36d5b7 - 62334aca - 6b096f88 - 88553bf1
Name: SGH-i917
KITLName: QSD8XXX19417BBB
Manufacturer: SAMSUNG
ModelId: 1
MobileOperator:
Version: 07.00.07004.00-00000
Checking your phone's status.
Checking your phone's status: Completed in 0.01 seconds
Checking system requirements.
Checking system requirements: Completed in 0 seconds
Downloading updates.
Downloading updates: 0%
Downloading updates: Completed in 3.07 seconds
Checking system requirements.
Checking system requirements: Completed in 0 seconds
Installing updates. Please wait: 100%
Installing updates. Please wait: Completed in 5.57 seconds
Rebooting your phone..
Rebooting your phone: Completed in 42.3 seconds
Completing updates..
Completing updates: Completed in 1.28 seconds
The device has been updated to version 07.00.07004.03-00.00.00000.00-00.00.00000.00
When i look at the "About" status it still shows 7.00.07004.0
Any ideas?
Hi, HTC Surround
I am updating and it goes to downloading update but fails to go any further. just closes chevron
Any Ideas
Updated fine, but after the update anything related with messaging (SMS's, E-mail some contacts) doesn't work. Orange HTC Mozart running branded 7008...
Chevronwp7update was removed from the site. Where else can it be downloaded from?
Same here HTC Mozart telstra
Sent from my T8697 using XDA Windows Phone 7 App
Updater seems to be offline?
Anyone has got updated Links or a mirror?
Thanks in advance
Ok, I installed the Debrander xap util and it debranded to 00-88. I then ran Zune and it showed update available. It upgrade phone to 7008 from 7004. But even after that running chevron update still fails.
Maybe it was pulled from the site due to unforeseen problems.
Btw, don't reinstall debrander over your original debrander as it loses the original carrier details no I cannot rebrand to at&t unless I do a reg hack *I think*
I have used the INTEROP-UNLOCK and sorted the GRPS connection....
My question is what are the limitations of this unlock?
I have not been able to get MMS working even after reloading the network profile, I have a locked phone to 3UK network.
I believe that when a phone is carrier unlocked MMS does not function, isn't is the INTEROP-UNLOCK similar?
I cant use the official Samsung Network profile app in the market place as I am locked to 3UK, but if I carrier unlock the phone, will I be able to use this official app to reconfigure (as a new phone) the 3G settings and the MMS settings to work as a stock phone.
Also, for carrier unlocked phones, via a 3rd party when we get an unofficial update from Microsoft, does it re configure the settings to work with the official Samsung network app.
I have posted a couple of times to find info on one of the above items, and have been told to to look at the forums, I have spent a lot of time reviewing them and I dont think the above points have been answered concisely....
Your help would be greatly appreciated.
http://www.wpxap.com/thread-171460-1-1.html
here you can see
Even when the page was translated from simplified Chinese, the link didn't explain any of the questions raised above...
Search for Samsung Tools in this forum. Install it and run it. Checkmark the prevent device from relocking, unlock, and run adc checkmarks. Press ok, after it reboots it will fix your mms issue
Sent from my SGH-i917 using XDA Windows Phone 7 App
W99DEY said:
I have used the INTEROP-UNLOCK and sorted the GRPS connection....
My question is what are the limitations of this unlock?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1265321
A Quote from it... Dont forget to hit thanks !
Heathcliff74 said:
On WP7 there are already a lot of different unlocks:
Developer-uplock/ChevronWP7 unlock: This will allow you to side-load apps from your desktop to your phone. A legit developer-unlock costs $99 per year (this will also allow you to deploy your apps in the Marketplace). ChevronWP7 made an unlock tool, which allows you to dev-unlock your phone for free. This method only works on WP7 version 7.0.7004.0 and 7.0.7008.0. It does not work anymore since version 7.0.7355.0 (pre NoDo). But it is possible to unlock your phone on version 7.0.7008.0 and then use some tricks to upgrade your phone and keep the unlock. You can even upgrade to Mango RTM and still have the unlock. Look in this thead to get full instructions. Also the ChevronWP7 team will release an unlock-method that will only cost a few bucks and will apply an official dev-unlock on any version of WP7, but it won't allow you to release apps to the Marketplace.
Interop-unlock: On RTM and NoDo versions of WP7 it was possible to run apps with native code. These apps would use a COM-Interop-Bridge to transit between managed and native code. These apps need to be tagged with the Interop-capability called "ID_CAP_INTEROPSERVICES". These apps don't seem to run on Mango. Not even when you have a legit Developer Unlock. There are two reasons for that. The first reason is that most native libraries need some modifications to run on Mango. I found out how to do this and modified WP7 Root Tools so that it is compatible with Mango. The other reason is a deployment-restriction. That is the Interop-Lock that needs to be Unlocked. If you have a normal Dev-unlock on Mango and you try to deploy an app with that uses COM interop, the deployment will fail with error 0x81030120. contable and Marvin_S found out that the MaxUnsignedApp registry-value is responsible for the Interop-Lock. I did more research and I identified the code that checks this value. In fact, if you have the MaxUnsignedApp value set to 300 or higher, your interop will be unlocked. The value of MaxUnsignedApp is determined by the type of developer-unlock you have. A normal AppHub account will have it set to 10 and a student account will have it set to 3. So a value of 300 or higher is not a realistic value for a normal developer account. It is probably only set to this value for Microsoft employees and OEM developers. Until now, the only way to do an INTEROP-UNLOCK for MANGO meant that you have to downgrade to NoDo first, then prepare your device by loading provxml files to your device, upgrade to MANGO and then use OEM tools to execute the provxml files and do the necessary unlocks. But that is a lot of work and for some devices not even possible, because there are simply no ROM's available. But I have found an exploit that works on Samsung and HTC devices, which allows you to UNLOCK INTEROP your MANGO device. For it to work, it must already be developer-unlocked! Read this guide for instructions.
FullUnlock: This a type of unlock which allows you to run Native Executables. Normally you can only compile Silverlight apps, which will be run in a sandbox. The app is compiled as a DLL, which will be run in TaskHost.exe. I you would like to compile Test.exe, you won't be able to run it, because there is a policy-system and certificate-system that prevent you from running it. Cotulla already cooked a ROM with FullUnlock, but unfortunately this is not yet working as expected. I also did research on this together with fiinix. Thanks go out to him for working with me on that matter. We did not get it working back then, but I think I now have enough exploits to get this working. I will do some more testing on this later on. WP7 Root Tools does not need FullUnlock to be able to run.
Full Root Access: As stated previously, Silverlight apps and system executables have their own sandbox, which is defined by a Least Privilege based policy system. Even when you break into native code, you are still running in your sandbox. For example, you can try to copy a file in managed code. You will only have access in Isolated Store. If you use COM interop to call native code and you try to use the FileCopy() API, you can still only copy files in your Isolated Store. To break out of the sandbox, there are a couple of possible exploits. But they are still limited in their possibilities. To get unrestricted access to the API's and Resources on your device you will need to completely bypass the policies that the system has defined for your app. YukiXDA and I have in close contact with eachother for a period of time and we learned a lot from eachother. I found some of the exploits, thanks to him! YukiXDA unfortunately has left the community. A very big thanks to YukiXDA for working with me on this matter. Before he left he cooked a ROM for HTC HD2 which has Full Root Access cooked into it. The way he did it was to effectively shut down the policy-sytem. Although this opens up a lot of possibilities for homebrew, this is also kind of risky, because the system is also open to malware. And this technique only works on devices which have an unlocked bootloader (currently HTC HD2 and most HTC WP7 devices have unlocked bootloaders). I developed another type of Full Root Access. I can enable Full Root Access for the entire device (differt than what YukiXDA did, but effectively the same). But I can also enable/disable this per app. So the user can decide which app is trusted enough to get Full Root Access. Other apps will still run in their predefined sandbox. I am currently developing a new version of WP7 Root Tools which will support Full Root Access. To do this I will apply Full Root Access for WP7 Root Tools first. A user can use WP7 Root Tools to enable Full Root Access for another app. So if a developer wants to create an app that needs Full Root Access (for example some type of backup-app), the user of the app must use a ROM which has Full Root Access cooked into it, or the user must run WP7 Root Tools to allow Full Root Access for the app. There are two disadvantages. WP7 Root Tools must first install Full Root Access for itself. Obviously WP7 Root Tools does not have Full Root Access at that moment yet. So there are other exploits necessary to apply this. Currently I have exploits for this, but they use some device-specific features. I have exploits for Samsung, HTC and LG. Other brands, or possibly a device-independent exploit, may follow later. This means that WP7 Root Tools only works on these devices, and with that also the apps that need Full Root Access will only work on these devices. The other disadvantage is that, with the current state of Interop-unlocking, all users of WP7 Root Tools, and with that also all users of the apps that need Full Root Access, will need to be on dev-unlocked-NoDo first, in order to apply an Interop-Unlock for Mango. Because WP7 Root Tools and all apps that use Full Root Access need Interop Unlock. When I have the version of WP7 Root Tools with Full Root Access finished I will release an SDK, which will make access to the system a lot easier. The SDK will consist of a native library and a managed wrapper library. Developers will be able to access the Registry and Filesystem using only managed code and the libraries from the SDK. The app will of course need to be unlocked, using WP7 Root Tools on the device. But using the SDK is mandatory. You can also write your own native code. I will write a guide on how to do that later on. An app that has Full Root Access (provided by ROM or by WP7 Root Tools does not need any device-specific libraries. All API's can be used. For API's that are not in the SDK libraries you need to write your own COM wrapper.
Click to expand...
Click to collapse
Hi W99DEY
I had the same problem as you - I am on the three uk network, with a samsung omnia 7, updated to mango, interop unlocked, reset mms/internet settings and the mms does not work.
I spent a while trying to figure this out, but I found a solution as to how to get mms working after interop unlock.
Here's how you do it:
1. Revert to your last back up of your phone - this needs to be pre interop unlock and your mms should be working at this point. Do this by connecting to zune, going to update and clicking backup.
2. Install mango updates.
3. Once zune says you can unplug your phone after the updates, unplug it and use heathcliffs method of interop unlock: http://forum.xda-developers.com/showthread.php?t=1271963
But stop at stage 10 - don't try and repair your mms yet.
4. Deploy any other provxml you may want. May I suggest this one, to enable tethering:
http://forum.xda-developers.com/showthread.php?t=1238519
Don't try to repair the mms yet.
5. ***This is the important bit*** Currently your mms won't work, and there is only one method which will get it to work:
Run the Diagnosis app and dial this to enable auto configure sim setting: *#94765#
It will ask you to restart the device. Confirm that.
Other methods like - setting apn, using samsung tools, etc. do not work so don't try them.
6. Plug your phone back into zune, it should want to update again (mine did) Saying it needed to install Samsung updates. Install them.
7. You're done and your mms should now work - make sure you're not connected to the wifi when trying to send a mms as it may not work.
------
***Important*** After you've applied the fix and got the mms to work do not run any more provxml files as that will screw your settings again, and this method only works once for some reason.
Also don't run any other methods of fixing mms settings like using samsung tools etc. as this will not work, and if you try these before using the diagnosis method, then the diagnosis method will not work. And the diagnosis method will only work once.
If anyone has any ideas as to how to make this fix work more than once for 3uk samsung omnia 7's please let me know.
If this was helpful please say thanks
Cheers Parsl for the response.... More or less did what you did, think I tried Samsung Tools 1st.... ;-)
Yeah, I used Samsung tools and that didn't work. I found the only thing that worked was the diagnosis method. But only once - as the first time round I then applied the tethering provxml and then the diagnosis method didn't work a second time, so rebooted and then did it all in the order I mentioned.
Have you got your mms working now?
Sent from my OMNIA7 using XDA Windows Phone 7 App
Can someone please simplify all this for me?
The information on this site is so convoluded in terms of methods, some expired , some still valid, and guesses that are plain wrong, and irrelevancies.
I have been reading, installing, and uninstalling for hours into days.
Samsung Focus
1. Can Mango unlock be achieved with unlock from 7004?
2.I was on NoDo unlock and followed some instructions for the Focus that did not work. It went right to Mango LOCKED (as many others have reported).
I made a nice little back up of my NoDo unlock but can't get back to it using any version of Zune or any method, they all result in restore errors.
My back up might as well be on the north pole because I can't get to it.
3.I flashed back to 7004 and couldn't get chevron to unlock again like I used to be able to on XP or WIN 7 with various zune versions back to 4.7.
I'm wondering if the newer Zunes corrupted that somehow because last time it worked was on a fresh zune install on windows 7.
And besides that, they all ask to be upgraded before they do a back up, usually.
4.But even if it is unlocked at ROM 7004, zune updates (if chosen) will send it back to mango and locks it agian right? That's what happened last time , it just kept updating the phone for hours and then it was back to mango.
5.It appears my only option now is Mango locked or 7004 flash Rom with possible unlock.
Hopefully answers here will help others as well.
A few answers, though not compreheensive:
1) You don't have to let WP7 install each update, if you wanted to stop at, for example, NoDo 7392, you could. Just wait untilt he update gets that far, then pull the plug and/or hit Ccancel in Zune. Left to itsself, it will install all available updates.
2) The phone automatically dev-relocks whenever a major update is installed - this happens even to people with legitimate develop-unlock (and it's annoying!) For Samsung, I believe the technique for preserving unlock is the same one used to get interop-unlock on Mango: place an unlock provxml file in \provxml\ on the phone's filesystem (you can either use Heathcliff74's WP7 Root Tools to do this, or you can just install his interop-unlock XAP) and make sure you have a working version of the Samsung Diag app (should allow you to process provxml files). Once you have that, you can install all the way up to the Mango update safely, I think (I don't have a Samsung, but it should work) and use the Diag app to process your provxml file, which will both dev-unlock and interop-unlock the phone.
Not sure what's up with your backups; I can't really help you there without more information. What error do you get? What version of Zune are you using (you probably should use the latest version, 4.8.whatever)? How big is the backup (it's in %localappdata%\Microsoft\Windows Phone Update\)?
As for what guides to follow, starting with the stickies is always a good idea.
Hello,
I have a HTC Mozart device wich is momentarily running on unlocked NoDo.
I have followed various guides from xda but I end up running a locked Mango (most of the guides require after Mango update to run HTC Connection Setup to unlock... which I am unable to run (black scren) and all other apps tell me revoked by Microsoft).
is there any latest guide a little more foolproof?
It seems that after 18th October something happened with Zune which prevents Mango unlock...
Gyuritzy said:
Hello,
I have a HTC Mozart device wich is momentarily running on unlocked NoDo.
I have followed various guides from xda but I end up running a locked Mango (most of the guides require after Mango update to run HTC Connection Setup to unlock... which I am unable to run (black scren) and all other apps tell me revoked by Microsoft).
is there any latest guide a little more foolproof?
It seems that after 18th October something happened with Zune which prevents Mango unlock...
Click to expand...
Click to collapse
After you install the interop-unlock xap while on nodo then goto mango you reinstall the diag app and in the Diagnosis app dial: *#9908#.. Select "Heathcliff74 Interop Unlock"
then tap Save, tap Close and exit the Diagnosis app
@lucasryan: Those are the instructions for a Samsung phone. They don't work at all on an HTC phone.
@Gyuritzy: Currently, Microsoft is pushing the Mango update and an HTC update together. The HTC update blocks the unlock path used with Mango. If your phone gets that update - which means if it gets Mango through the retail update path - there's no current way to interop-unlock it.
If you can get Mango through an atypical upgrade path (I came from the beta, which worked), or if you use a custom ROM (be *very careful* of the bootloader version if you try this!!), you can get interoop-unlocked Mango on HTC. It's not easy, though.
Ahh i see that i quoted his post now. as alan93 has focus
What solution do I have to load Mango without HTC update? Should I try with RCT2RTM type of packagge?
@GoodDayToDie
#1 - ahh ok, but I'm sure watching the update tentativley is required right? For like an hour and a half.
#2 - now see, there you go again, this is only for dev-unlock people which , i'm not even sure what that is..what? you pay $100 to MS to get it? It needs to be stated more clearly where ever that solution is posted AT THE VERY TOP like this "IF YOU ALREADY HAVE A DEV UNLOCK ....
@ lucasryan - That can't be right, -->"installing interop unlock on NoDo then go to Mango"...STOP RIGHT THERE. when you go to Mango it wipes everything out and you have no more access...unless of course ..YOU ALREADY HAVE A DEV UNLOCK...what ever that is.
I did try the diagnosis trick on update to mango after putting that file on there but the diagnosis version would not go higher than 908 or what ever. Couldn't get 1112 or what ever the one that is needed.
Please, just say there is no way to unlock Mango unless you have a dev unlock and that is low percentage as it is...then I won't expect so much.
Thanks for the replies.
Here is the zune error I get on trying to restore to my NoDo unlock.
http://answers.microsoft.com/en-us/...-restore/3ec7091d-d79d-422c-9995-cfe186e0155b
As you can see nobody is dying to answer it.
I think the code number means "this goon is trying to restore to an unlocked version, don't answer him".
@alan93: Developer Unlock is the term used for the change to your phone made by the Windows Phone Registration Tool (if you have a marketplace developer account), ChevronWP7 Unlocker (possible on pre-NoDo), ChevronWP7 Labs (coming soon), or changing the DeveloperUnlockState registry value located at HKLM\Comm\Security\LVMod to 1 (possible with the LG registry editor, or by using the Samsung diag app or HTC Connection Setup app to process to provxml file). The registry change is actually what matters; the other methods are simply ways to achieve it.
Dev unlock allows you to install XAP files - a renamed ZIP file with some manifest XML files, one or more managed (.NET-based) DLL files, and possibly other files needed by the application. Due to a bug in the application installer, you can also use a XAP to put arbitrary files almost anywhere in the filesystem (the installer can't write to the \Windows\ directory).
One of those manifst files specifies capabilities that the app has, which controls permissions of the app (for example, ID_CAP_ISV_CAMERA allows access to the public camera APIs). As of Mango, including beta versions, it is no longer possible to install apps with the ID_CAP_INTEROPSERVICES capability unless the MaxUnsignedApp registry value (located in HKLM\Software\Microsoft\DeviceReg\Install) is set to at least 300 (the default value is either 10 or 3, depending on the unlock method used). ID_CAP_INTEROPSERVICES is required for interfacing with drivers, a way for applications to run at high permissions (for example, to write to the registry). Each time you install a major upgrade, such as Mango, this value is reset to its default. An app with ID_CAP_INTEROPSERVICES therefore can't be installed (or run, if it was installed before upgrading to Mango) until this MaxUnsignedApp registry value is changed, a process referred to as Interop-unlock (term coined by Heathcliff74 on this forum). Marketplace-installed apps are exempt from this restriction, which is why things like Connection Setup (which has ID_CAP_INTEROPSERVICES) can be used.
For what it's worth, I got my dev-unlock by purchasing a marketplace developer account ($100 from MS). One day I may even submit an app to the marketplace, but so far all the apps I've written use homebrew and wouldn't be acceptable for the marketplace, so I just publish them here.
Thanks great explanation.
I intend to write my own too, I wrote one and have a few more great ideas but didn't want to pay until i made sure I was able to write them completely and testing on the simulator sux. And last I heard, the media player doesn't work with it.
I just think the fee and lockout just hurts development thereby limiting the success of WP7.
If it was $50 or less I would probably pay it.
I mean for crying out loud I'm a certified MCP/MCAD, they should give me a break here.
UPDATE 2: Heathcliff74 has taken a look into the reason that this method wasn't working on phones with the HTC updates for Mango, and appears to have found a work-around! I strongly suggest that people try his version instead of mine. The instructions are similar but not identical. Scroll down to the bottom of this first post and use the HTC Interop Unlock XAP located there:
http://forum.xda-developers.com/showthread.php?t=1271963
If you want to post your results in this thread, please specify which XAP you are using, mine or Heathcliff74's. There are known limitations with mine. There still seem to be some limits with his, be we aren't sure exactly what they are yet.
UPDATE: This is disappointing, but apparently HTC has put yet another roadblock in our way. I'm working on a way around the next one. I can't say how long it will take, but I beat the last one (process arbitrary provxml on an interop-locked phone) and I'll beat this one (allow Connection Setup to modify the registry again, after the HTC updates).
I'll update this thread again when I have a new version to test. Guesses as to the problem's root cause, suggestions for fixing it, and anything else you've found are all welcome.
I'm not taking the initial release of the app down, but unless you have an HTC phone which somehow is on Mango, doesn't have the HTC updates, and isn't already interop-unlocked, this isn't going to do anything for you. If you are in that situation, have at it - for now though, I'm just leaving it up so people can download it and pull it apart.
What it does: Modifies your HTC phone to allow maximum unsigned apps, which will also allow you to deploy and run apps with ID_CAP_INTEROPSERVICES. This does not require rolling back to pre-Mango. It is designed for use on stock ROMs. It is expected to work on all GSM HTC Windows Phone 7 devices. It might even work on the Arrive (can't hurt to try). You can read more about Interop Unlock here: http://forum.xda-developers.com/showthread.php?t=1271963
What it needs:
HTC Windows Phone (in theory, any of them)
Developer-unlock (AppHub account or ChevronWP7 Labs should be fine)
Connection Setup app (it's in Marketplace under HTC Apps)
What you do:
0) Install Connection Setup, if you haven't already.
1) Start Connection Setup, just to make sure it works. You don't have to do anything, just start it.
2) Exit Connection Setup using the Back button (so it's not running or suspended).
3) Install HtcInteropUnlock.xap. You don't need to run it.
4) Run Connection Setup again.
5) Expand the AppBar menu (... at the bottom) and choose "manual select".
5.a) The Country and Carrier list-picker boxes should become enabled.
5.b) If they don't, hit "manual select" again, it takes two taps on my phone.
6) Tap on Country and select "Phone Customization" (you can use the jump list to get to P quickly).
7) Carrier should automatically change to "Dev and Interop Unlock" (make sure this happens).
8) Hit the check mark at the bottom (AppBar "ok").
9) Make sure it reports success, then hit Done.
10) Try to install / run an interop app (or just install an 11th unsigned app).
Please report what happens, including the following info:
Your phone model (mine is HTC HD7, T-Mobile US branded).
Your version info (mine is 7720, no HTC Mango updates).
Success or failure of the whole operation.
If failure, indicate the exact step that went wrong, and what happened instead.
Be aware: This method does not damage your data connection in any way, but it will probably prevent Connection Setup from working normally. This can be undone. However, I didn't want to put the effort into making it reversible until I knew whether it worked on other phones, so if you need Connection Setup for its official purpose, don't install the initial release of this app.
This app builds on the work of multiple members of our community. Special thanks go to:
Heathcliff74, for researching interop-unlock and discovering the xap-deployer hack.
kounadisk, for researching how to add custom entries to Connection Setup.
I am already interop-unlocked but
OMG I am tempted to roll back to nodo, update the official way then unlock this way!
Watching this thread Kudos!
For what it's worth, I'm interop-unlocked already too, so I haven't actually tested this app on a non-IU phone. However, it should work just fine, provided that Connection setup was installed from the Marketplace.
On the plus side, by using this method you can restore your interop-unlock if you ever lose it (if you IUed the way I did, then an update might cause you to lose IU without being able to get it back the same way - but this method should still work).
that's worked
W00t! Can you please tell me your phone model and software version too? Thanks!
Radar 7740: The option shows up, I can "apply" it but it does nothing.
Surround 7740: I can apply Phone Customization but when I open HTCInteropUnlock app, nothing happens
TeNsTrKe15 said:
Surround 7740: I can apply Phone Customization but when I open HTCInteropUnlock app, nothing happens
Click to expand...
Click to collapse
Read the instructions...You just install the app and the follow the other steps. No need to open it.
Nothing special is supposed to happen. The change is invisible. As for the Interop Unlock app itself, it's just a stub - all of the "what it does" is entirely in the install process. Once it's installed, you can even remove the app.
Try installing this app: http://forum.xda-developers.com/showthread.php?t=1238519
If you can install it (without modifying the XAP file) then your interop-unlock worked!
Alternatively, try installing Registry Editor 1.2.0.0 from TouchXperience: http://forum.touchxperience.com/viewtopic.php?f=20&t=593. It goes in the Settings hub, but if you can install and run that, then there was great success!
MJCS said:
Read the instructions...You just install the app and the follow the other steps. No need to open it.
Click to expand...
Click to collapse
even so, i still cant install interop apps. error 0x81030120
TeNsTrKe15 said:
Surround 7740: I can apply Phone Customization but when I open HTCInteropUnlock app, nothing happens
Click to expand...
Click to collapse
I suspect this might not work if you have the HTC updates installed.... the OP indicated he has not installed any HTC updates
Ok, tried this on my HTC Titan.
I selected "Phone Customization" as country and "Dev and Interop Unlock" as carrier and applied these settings. The Connection Setup app reported that it successfully configured the phone.
But ... it does not seem to have any effect (yet, I hope!). I still can't sideload more than 10 apps.
My Titan is on WP7 version 7.10.7740.16.
Connection Setup app is version 1.12 (build 2119.18323)/
I'm hoping it works anyhow, but it's possible it wouldn't. It really depends what's in those updates.
For example, we know they modified the HTCFileUtility driver in some way, but we don't know exactly how. TouchXplorer stopped working, but Connection Setup (which also uses ComFileRW.dll) still works. I know it works because if it didn't, you wouldn't be able to see the Phone Customization option.
It's possible that the update made some other change that made it impossible to change the MaxUnsignedApp value from within Connection Setup or something unfortunate like that.
I can modify the app to make some more obvious change when Connection Setup does its thing. For example, forcibly change your phone's accent color or some such. Really, though, I'm hoping that won't be needed.
One thing to try is rebooting the phone. I don't think it's required, but it can't hurt and might help.
Can you make it write to a specific registry path and then tell us what that path is. I would like to see if it can at least write to the registry.
Dev/Interop applies from Connection Setup but can't install an app with interop (ansar's USBModeSwitch XAP) enabled (in my case 3rd unsigned app since i have a student account).
Mozart 7720, with latest HTC updates installed.
update: rebooted. not installing still. it auto-starts Connection Setup, ran it again, doesnt work still.
cheers.
GoodDayToDie said:
One thing to try is rebooting the phone. I don't think it's required, but it can't hurt and might help.
Click to expand...
Click to collapse
Rebooting does not help... Still can't sideload more than 10 apps.
I think it would be a good idea to try and edit some other registry setting in the provxml, that has visible consequences. Then at least we can verify if changing that setting works.
Didnt work for me. Unbranded HD7, HTC Updates 7720.
Sounds promising though
@MJCS: It already writes a test value to the registry:
KEY: HKCU\Software\DeployProvXml
VALUE: InteropUnlock
DATA: "Success" (String)
Can somebody who was already interop-unlocked but has installed the HTC updates use this app, then check if that value exists? It does on my phone, but of course I don't have the HTC updates.
What are the passwords for the dbz files?
Nevermind its 030D681B-1DFC-4bd0-A72A-A9B3CCCDA653
Yeah there must be some sort of time-bomb that clears out the interop setting.
http://forum.xda-developers.com/showthread.php?p=18916888#post18916888
GoodDayToDie said:
@MJCS: It already writes a test value to the registry:
KEY: HKCU\Software\DeployProvXml
VALUE: InteropUnlock
DATA: "Success" (String)
Can somebody who was already interop-unlocked but has installed the HTC updates use this app, then check if that value exists? It does on my phone, but of course I don't have the HTC updates.
Click to expand...
Click to collapse
My HD7S has all the latest updates, and is already interop-unlocked.
I tried the app out, and checked the registry and found no such entry.
I hope you get this figured out today before I pick up my Titan. Haha.