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.
Related
I'M A CHINESE.I hope my experience can help all WP7 fans. If this thread help you,It's my pleasure.
detail steps：
1. MAKE sure your phone has a 7004 or 7008 rom，than used chevronWP7.cer and chevronWP7.EXE to unlock your WP7. (this is step you can find in this forum)
2. After UNLOCK! prevent relocked. (belows is the easy way to edit your registry)
for HTC download xap in http://dl.dbank.com/c0u5q3xic8 and sideload it to your phone and run it ,press the green button.
for Samsung devices,see post #17 in this thread.
3. Update to NoDo via zune and your device still in unlocked state! (for some people cannot get nodo from zune, see below method,100% successful rate.)
methods to get zune nodo. http://forum.xda-developers.com/showthread.php?t=1012189 !!!!
Download USAIP.pbk open it and connect to EUROIP PPTP Hungary with
USERNAME: demo
PASSWORD: demo
Connect your phone to the PC
Disable WIFI in your phone but be sure not to open FLIGHT MODE
OPEN "Use cellular data connection to check for updates" in SETTINGS-UPDATE, AND KEEP YOUR PHONE IN THIS SCREEN
Start Zune and keep it running all the time
Manually search for an update within Zune (setting-phone-update)
After a few seconds (about 20-25 seconds for me) disable "Use cellular data connection to check for updates on your phone" --> WAIT FOR 20-30S,The update shows up! and enjoy it!
I MANAGED TO GET UPDATE BY USING THIS METHOD!!!
HAVE fune!
the update should go via zune. it should be official update。
If it works that's good news.. But is it that easy? I would thing that the update edits the registry...
If you update to 7008 the unlock still works that I know.. Are you sure that's not what happaned.. And you just got the Pre-NoDo update...?
BellPego said:
If it works that's good news.. But is it that easy? I would thing that the update edits the registry...
If you update to 7008 the unlock still works that I know.. Are you sure that's not what happaned.. And you just got the Pre-NoDo update...?
Click to expand...
Click to collapse
the vision is 7390.after 7008，unlock，then prevent unlock， then connect to zune， if you can find update， then you success。many chinese succeed，the only problem is MS，it promise everyone can update，but only very few people receive the notice of update through zune。
March thanks for XDA-DEVELOPERS(xboxmod)!
But I am still waiting the Nodo Version in Hong Kong, if it is true, it is a great job for the user!!!
I am a user of HD2 with wp7 two days ago.but now I have to switch to Android again as the wp7 is not fully developed,I think.anyway...thanks for sharing the good news...謝謝!
It seems to work based on user replies. However, it requires HTC-ProvXml-Deploy to work. What about us non-htc users?
as it was already said, we need to know if it works on non HTC devices?
Can anyone post the xap here?
Registered and downloaded the xap. It's attached as a zip, just change the file extension from .zip to .xap.
Wondering if this will truly be our way to update to NoDo and still keep our devices unlocked...
eternalemb said:
Registered and downloaded the xap. It's attached as a zip, just change the file extension from .zip to .xap.
Wondering if this will truly be our way to update to NoDo and still keep our devices unlocked...
Click to expand...
Click to collapse
thanks! I still cannot update to NoDo from Zune. Though my phone is unbranded
Is it the same with this?
[HTC] Prevent WP7 from Relocking
http://forum.xda-developers.com/showthread.php?t=913748
thats great, im sure this will be very helpfull to get a real JB goin...
too bad ive already updated :/
lemme quote the first post of the site translated (powered by microsoft translator):
http://www.qdppc.com/thread-48290-1-1.html said:
"Frog brothers produced"
---Prevent once and for all small patches of the lock (Prevent Relock:1B)
Simple, perfect, effectively address the WP7 lock problem again!
From then on no longer careful, make you lechery tour ZUNE!
Note: HTC models suitable for
Frog (Wagool) by XDA-DEVELOPERS (xboxmod) information produced by XAP patch (formerly:http://www.qdppc.com/thread-48230-1-1.html), an effective solution to mobile phone unlocking (prison break) is locked again after question!
"Steps"
1, verify that the phone has "escaped";
2, Prevent Relock.xap deployment installation attachment to mobile phone,immediately disconnect the ZUNE connection;
3, mobile Executive HTC-ProvXml-Deploy program, pressGreen(OK) button;
4, after you restart the phone, remove HTC-ProvXml-Deploy, well, everything OK!
"Description"
If the reset system (hard restart, restore factory, brushing machines), you need to "escape" and install this patch!
Reprint please specify the source
March thanks for XDA-DEVELOPERS(xboxmod)!
----------------
1, immediately disconnect the purpose is to prevent before continuing to the next step, have also been locked (in fact, in "flight mode" or under)
2,Deploy delete it or not as you, in fact, at this point the useless
PS: I'm not "boring", is a frog, HA HA ~ ~
Wagool
Click to expand...
Click to collapse
I received this morning notice of NoDO update... but I can wait a few days before to do...
harmoniic said:
Is it the same with this?
[HTC] Prevent WP7 from Relocking
http://forum.xda-developers.com/showthread.php?t=913748
Click to expand...
Click to collapse
+1
Any one plz answer this.
info5i2002 said:
It seems to work based on user replies. However, it requires HTC-ProvXml-Deploy to work. What about us non-htc users?
Click to expand...
Click to collapse
The whole prevent-relock thing essentially does this:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\DeviceReg]
"PortalUrlProd"=""
"PortalUrlInt"=""
On Samsung devices you can use the TouchXplorer Registry Editor to do this. Though it has limited access on Samsung devices. It will show an "Access Denied" when you open the DeviceReg registry-key. But it will still allow you to create new values there and overwrite the old values. So, open the DeviceReg-key and create the "portalUrlProd" and "PortalUrlInt" values as empty strings. That will prevent your Samsung from relocking. And as it seems, that tweak will even survive the NoDo-update.
is that only for htc device?
Heathcliff74 said:
The whole prevent-relock thing essentially does this:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\DeviceReg]
"PortalUrlProd"=""
"PortalUrlInt"=""
On Samsung devices you can use the TouchXplorer Registry Editor to do this. Though it has limited access on Samsung devices. It will show an "Access Denied" when you open the DeviceReg registry-key. But it will still allow you to create new values there and overwrite the old values. So, open the DeviceReg-key and create the "portalUrlProd" and "PortalUrlInt" values as empty strings. That will prevent your Samsung from relocking. And as it seems, that tweak will even survive the NoDo-update.
Click to expand...
Click to collapse
The xap samsung tools does the job automatically which is easier to use
Marvin_S said:
The xap samsung tools does the job automatically which is easier to use
Click to expand...
Click to collapse
So someone has tried to change these keys and update to nodo to see!!!!
Hey Guys,
I have been a long time viewer of XDA and found it incredible useful for both Android and WP7 communities.
I have just updated my Samsung Omnia 7 to the 7720 (RTM) build of Mango after the official Zune 4.8 came out. This meant that it took lots of trial and error and basically mashing instructions from a few different tutorials to get the build running.
As I can't find much reference for people who are trying to do this post-4.8 i thought it would be helpful to post what worked for me. I will try my best to link to the original threads for the steps and downloads I used and I take zero credit for the hard work done by those who wrote these tools and scripts.
(MODS: As this is my first post I couldn't put this in the Dev/Hacking forum, if up to scratch and necessary could you move it there?)
So here we go:
You will need:
WP7 Handset running NoDo
MicroUSB Cable
Windows 7 or Vista PC
Patience
A couple of hours to spare
Please note that as per every other tutorial of this kind, you are doing this to your own phone... don't blame me if things go bad!
This method of updating will remove your Chevron Unlock - if your a homebrew fan then i would look for other tut's or wait for official update!
1: Download this "Mango for All 0.3" from here
2: Extract the folders in the zip file to C:/takeonetomango .
3: Download "7720.rar" from here (originally found in this thread)
4: Extract the contents of 7720.rar to C:/ (VERY IMPORTANT! - you should end up with C:/RCtoRTM, C:/Zune etc).
5: If you currently have Zune and the Windows Phone Support tool - UNINSTALL THEM.
6: Open C:/Zune and run "Startzunelocal.exe" to install the (now old) Zune 4.8 Beta.
7: Open C:/Zune/Update and install "UpdateWP.exe" from either the x86 or x64 folder depending on which windows you use. (This is something of an idiot test. If you don't know which you should choose - stop here. Put the down your phone, uninstall Zune and put the official zune back - you should wait for the official mango update as this can seriously damage your phone.)
Explanation: So far, all the tools used to provision the phone and force the updates rely on the version of Zune and the WP Support Tool to match. Since the Zune 4.8 was officially released, there isn't a matching Support tool, which will cause all these bat files to fail their checks. This is why we will be rolling back to the old 4.8 beta a couple of times, just to please those checks.
8: Now you should have Zune Beta and the supplied UpdateWP installed. Now navigate to C:/takesonetomango. Plug in your phone and quit zune (you may need to wait a few minutes for the windows device driver to install). DO NOT UPDATE ZUNE AT THIS POINT. QUIT ZUNE.
9: With your phone plugged in and zune no longer running, right click "Update.bat" and run as Administrator
10: Follow the steps that appear in the command prompt. This will now do a backup of your phone and move it to a safe place (this is because you will need to go back to NoDo to get the official Mango update).
11: Go and put the kettle on. This is now going to take a while depending on how much stuff you have on your phone.
12:When the backup is done, it will move this backup to a safe place. Press any key to start that and finish drinking your coffee.
13: Once the backup is moved the command prompt will now do the interesting stuff. Its going to "Provision your phone" to trick Zune into thinking your a developer. Follow the instructions and be VERY PATIENT.
14: Once its all done, it will launch Zune. Stop any Sync'ing and go straight to check the phone for updates.
15: It should now say an Update is available and welcome to the Mango ISV beta. Hit Update now. You must update to the latest Zune first - this is fine - go for it.
16: When zune has updated, plug the phone back in and check for updates again. Now it will install the Mango 7712 (beta 2) update. Your phone will restart a couple times, be patient and wait until it has done TWO updates to your phone. Another coffee would be good.
CONGRATULATIONS! You now have Mango on your phone. However its not the latest RTM that you have been hearing about. So lets go install that -
17: With your phone unplugged, uninstall Zune again. And make sure you uninstall the "Windows Phone Support Tool" if it shows up in the program removal list.
18: Now go back to C:/Zune and install that old version again.
19: Now install "UpdateWP.exe" from the correct folder in C:/Zune/Update
20: Plug in your phone. Wait for the device driver to install again.
21: If Zune launches, quit Zune.
22: Go to C:/RCtoRTM and run "ISVto7720.bat" as an Administrator
23: This will take quite a while. All those other files in there are actually the RTM update itself. This one doesn't come over Zune, we only went back to the old zune to satisfy the checks in ISVto7720.bat.
24: After you have drank a few more cups of coffee your phone will have rebooted and installed the RTM release.
At this point you will need to unplug your phone and start playing with it. My apps and files and all settings etc stayed in place so yours should too.
Whilst playing with the new features on there you will want to launch zune and get it to update itself to the official 4.8 again otherwise the phone won't sync with it.
It's important to keep the C:/takesonetomango folder as there is a handy file called "Restore.bat" which will use the backup created earlier to put NoDO back on your phone as Microsoft says you will not be able to get the official release unless NoDO is on your phone.
Hope you find this useful. If I have linked to something and not given credit to the original author please let me know and I will change the credit.
Enjoy
Tips:
1. If you have any problems with errors for "prov.cab" users have reported that sometimes rebooting can sort it, otherwise edit the update.bat file with the explicit path to prov.cab. Thanks to everyone in the thread who suggested this to help others!
Is Hidden WiFi feature enabled in this release?
The code is probably there but don't know how to enable it yet! There is a long discussion here:
http://forum.xda-developers.com/showthread.php?t=1233612
There is plenty of other reasons worth updating though!
Help!
Hi.
Trying to follow these directions. At step 9, am getting this error:
"File prov.cab is not accessible. Please double check your file."
Any idea what I might have done wrong? Do I need to uninstall everything and start over again?
Theycallme Tim said:
Hi.
Trying to follow these directions. At step 9, am getting this error:
"File prov.cab is not accessible. Please double check your file."
Any idea what I might have done wrong? Do I need to uninstall everything and start over again?
Click to expand...
Click to collapse
try running as admin.
Im actually stuck at step 16
Zune wants to restart the phone but nothing happens and the phone screen shows a picture that i should plug in the cable, but it is already
zune also consumes 30% of the cpu and that since an hour...
any ideas how to continue ?
/edit
just abort and retry
now running 7720
Was doing that, but that was a good suggestion.
z33dev33l said:
try running as admin.
Click to expand...
Click to collapse
try running not as admin, worked for me...
Just uninstalled everything and am going to start over from step 1.
No disrespect to all of you Mango lovers, but really wish the Pre 3 had made it to market right now. ... I'm sure I'll be more forgiving of some of the Mango shortcomings once I have successfully completed this process.
For what it's worth, i followed the instructions and am now successfully running 7720 RTM Mango.
The only stumbling block i had was going from 7712 to 7720, "ISVto7720.bat" was closing seconds after opening, a quick PC restart later however it worked first time, plain sailing aside from that.
Really enjoying all the new features thus far and i'm sure there's more i've yet to encounter - thanks for the clear and easy to follow instructions to help me get there.
Great to hear at least some success with these instructions!
It is a bit hit and miss, to be honest and each machine seems to have its own little subtle differences in the order that it installs device drivers etc.
If you get the problem with Prov.cab double check you have extracted the folder to the right place, the bat files have explicit paths in them (it doesn't just look for prov.cab in the same folder, it looks specifically for C:/RCtoRTM/prov.cab for example).
Jay
I'm going to try this later on tonight.
I have de-branded my HD7 a few weeks back using the two roms.
RUU_Schubert_O2_UK_1.57.728.02_Radio_5.52.09.16_22.33a.50.10U_Signed_by_ansar
RUU_Schubert_HTC_Europe_1.69.401.01_Radio_5.54.09.21_22.33b.50.10_Signed_SCHUBER*T_RELEASE
I assume this still will work?
dctrdre said:
For what it's worth, i followed the instructions and am now successfully running 7720 RTM Mango.
The only stumbling block i had was going from 7712 to 7720, "ISVto7720.bat" was closing seconds after opening, a quick PC restart later however it worked first time, plain sailing aside from that.
Really enjoying all the new features thus far and i'm sure there's more i've yet to encounter - thanks for the clear and easy to follow instructions to help me get there.
Click to expand...
Click to collapse
Same problem here with a few error messages, but finalli working on LG E900.
Thanks Jay
Just wanted to confirm that it has worked fine. Thanks Jay for putting the guide together.
Sent from my HD7 T9292 using XDA Windows Phone 7 App
Does anyone know if this procedure works for the Verizon Trophy (SparkW), and if not, is there any way to load Mango RTM without developer unlock?
General sanity check question: if one chose to update to Mango via this "unofficial" method, how can he be sure that his phone will be in a "supported" state afterwards? Or, to rephrase, what would be the purpose of updating now just to have to revert to the last backup in order to update officially once the update is released by the manufacturer?
AnnihilatorSC said:
General sanity check question: if one chose to update to Mango via this "unofficial" method, how can he be sure that his phone will be in a "supported" state afterwards? Or, to rephrase, what would be the purpose of updating now just to have to revert to the last backup in order to update officially once the update is released by the manufacturer?
Click to expand...
Click to collapse
As I know, the beta update in 7712 has all 22 Languages, while the RTM update posted here only has 6.
For those who just use one of those 5-6 default languages should have no problem, but the others who enabled other languages in 7661 or 7712 should have found the update is "unfinished" (I hope someone will notice), though the build is 7720.68 which is supposed to be real RTM.
If the update through Zune has all 22 languages available, it should be worth to update officially. As you know, there are always people who don't want to see the "Not for resale" logo in the boot screen while keeping the Mango features, me too.
When someone captures the RTM update files in all 22 languages before the update through Zune, then I will see no point to roll back the update and do once more officially.
henry084 said:
As I know, the beta update in 7712 has all 22 Languages, while the RTM update posted here only has 6.
For those who just use one of those 5-6 default languages should have no problem, but the others who enabled other languages in 7661 or 7712 should have found the update is "unfinished" (I hope someone will notice), though the build is 7720.68 which is supposed to be real RTM.
If the update through Zune has all 22 languages available, it should be worth to update officially. As you know, there are always people who don't want to see the "Not for resale" logo in the boot screen while keeping the Mango features, me too.
When someone captures the RTM update files in all 22 languages before the update through Zune, then I will see no point to roll back the update and do once more officially.
Click to expand...
Click to collapse
Actually, my Trophy only has 5 languages available. I remember that the update will not show all 22 languages, but it will support all of them. Selected languages will only be available on your phone based on the phones firmware region.
Just updated my hd7 and my wife's focus 1.3v to mango. This walkthrough is definitely great. For the focus i used senboston "ISVto7720" instead of the one in rctortm package. It is in the other THREAD post #508 mentioned in the first post here. With your indulgence, could you please enlighten me on how to use the restore.bat. Maybe another walkthrough for this is needed. Thanks again!.
downloaderintruder said:
Actually, my Trophy only has 5 languages available. I remember that the update will not show all 22 languages, but it will support all of them. Selected languages will only be available on your phone based on the phones firmware region.
Click to expand...
Click to collapse
It does support multi-languages shown up since 7004 (cannot said to be support), just not be able to type.
What I mean is the interface languages, which suppose to be a full support, instead of partial support as you have mentioned.
In beta update 7712, language packs will be updated according to your registry settings in NoDo, instead of the ROMs we have. I am just curious if 7720.68 through Zune will update in the same way.
Hi hackers,
Version 2.1 of DeployProvXML is here, and should be more robust than the previous version:
1: The CustClear.provxml file is now copied both using the filesystem DLL (like v1) and using XML provisioning (hopefully works aroudn the HTC update blocking filesystem access.
2: The CustClear.provxml file is now self-chaining. Really, this time - so long as you run the program *once*, you can even change the included CustClear.provxml, re-deploy, and run Connection Setup; your new version will then be copied to \Windows. (Re-run CS to actually process your new version). No more need to re-run DeployProvXML after each use of Connection Setup!
3. The program now contains more diagnostics. It sets a registry value at launch (using ComRegRW.DLL), changes that registry value (using provxml) when deploying the file, and changes it again when the deployed file is processed by Connection Setup (as part of the CustClear.provxml). It also checks that the value is as expected avter deploying.
REQUEST:
Anybody who has an interop-unlocked HTC phone with the latest official HTC update (meaning you can't use TouchXplorer anymore), please run this app, then run Connection Setup, then use a registry editor to check the key HKCU\Software\DeployProvXML. It should have a value, LastOperation. Please include the data in the value (or the fact that it doesn't exist) with your reports. Thank you!
Description:
Another handy little utility for people with HTC phones, this app simply copies a CustClear.provxml file from its install directory to \Windows, then exits. The idea is to make sure that you're never without at least a basic file that can be used by Connection Setup to unlock your phone. New in v2, every time you run Connection Setup, the file will automatically restore itself to the Windows directory. This ensures you'll never accidentally get caught with a locked phone after an upgrade or something!
The included Provxml has three parts. However, you can customize it however you like by opening the XAP file and editing the embedded provxml. The parts are:
1: Applies the registry settings to unlock the phone, including Interop-Unlock.
2: Applies a test value in the registry, at HKCU\Software\DeployProvXML. This value is harmless but can be used to test if the app is working.
3: Chain-copies itself from DeployProvXML's install folder into Windows again, replacing the copy that Connection Setup consumes.
Note that this program does not actaully apply the provxml, merely copies it to where Connection Setup expects to find it. It should close immediately after starting; this is not a bug. If you see a dialog box instead, something went wrong and you should report it below!
This program is only going to work on HTC phones, since it uses the HTC DLLs for provxml, file access, and registry. It is a 7.0 app but is compatible with Mango if you have Interop Unlock already.
XAP is in DeployProvxml\bin\debug. Source included for those interested.
Do you think a deployer for OMNIA 7 is possible ?
Maybe with a .dll of WP7 Root Tools ?
So users who didn´t prepare their device for our OnDevice provxml app under NoDo could also enable this feature...
contable said:
Do you think a deployer for OMNIA 7 is possible ?
Maybe with a .dll of WP7 Root Tools ?
So users who didn´t prepare their device for our OnDevice provxml app under NoDo could also enable this feature...
Click to expand...
Click to collapse
This has been solved I can finally test the app myself now. I changed the path to copy the provxml from the iso storage of the app instead of the provxml folder.
Interop.Services
Just read this http://translate.google.com/transla...oducing-windows-phone-7-5-native-programming/
Any joy?
Looks cool, but I'll need to investigate further. It has definitley been reproted that Homebrew apps without ID_CAP_INTEROPSERVICES don't work even in Mango. It sounds like this guy is maybe using a marketplace signed DLL, though? Not sure - the translation isn't great. He's working from an app that I've never explored, and that appears to be specific to the Japanese Mango phone.
how do we use it. will it permanently unlock when we update to official Mango?
Ttblondey said:
how do we use it. will it permanently unlock when we update to official Mango?
Click to expand...
Click to collapse
Install app in NoDo.
Run in once.
Upgrade to Mango.
Run the Connection Setup app (from Marketplace).
Hit "OK" in Connection Setup.
Your phone is now dev-unlocked and will not automatically relock. Additionally, you can now install Mango homebrew.
I suggest you then run DeployProXml again, since installing an update, even something like a HTC firmware update, may re-lock the phone. So long as you've run DeployProvXml since the last time you ran Connection Setup, though, you can unlock again.
If this helps, please hit Thanks!
piaqt said:
Just read this http://translate.google.com/transla...oducing-windows-phone-7-5-native-programming/
Any joy?
Click to expand...
Click to collapse
he does pretty much the same from what I read. You just use oem dll's and have some native functions to work with. f/e htc has file operations + regoperations + provxml, samsung has regoperations + provxml (trough which you can do regops). This manufacturer dll probably contains fileops as well, which is nice since there might also be a chance that there will be a working provxml method and with the fileops you can copy the provxml files to the desired location. In theory ofcourse.
Marvin_S said:
he does pretty much the same from what I read. You just use oem dll's and have some native functions to work with. f/e htc has file operations + regoperations + provxml, samsung has regoperations + provxml (trough which you can do regops). This manufacturer dll probably contains fileops as well, which is nice since there might also be a chance that there will be a working provxml method and with the fileops you can copy the provxml files to the desired location. In theory ofcourse.
Click to expand...
Click to collapse
There are two differences that are worth noting, though.
A) This is a phone that came with Mango. There was never any chance to unlock it for Mango homebrew. It blocks apps with ID_CAP_INTEROPSERVICES - something we had to work around with registry edits.
B) Related to A, he can call native code without having ID_CAP_INTEROPSERVICES. This isn't supposed to be possible at all. Makes me wonder if he's actually calling anything in the DLL or if he's just loading the COM object but not using it and calling that success.
GoodDayToDie said:
There are two differences that are worth noting, though.
A) This is a phone that came with Mango. There was never any chance to unlock it for Mango homebrew. It blocks apps with ID_CAP_INTEROPSERVICES - something we had to work around with registry edits.
B) Related to A, he can call native code without having ID_CAP_INTEROPSERVICES. This isn't supposed to be possible at all. Makes me wonder if he's actually calling anything in the DLL or if he's just loading the COM object but not using it and calling that success.
Click to expand...
Click to collapse
Ahh yeah your right. Yeah I realy wonder what the trick behind it is and if he manages to install it.
Something else I have not tried yet, but what happens if you deploy it without the id_cap and than run it. It will not work obviously, but what happens if you redeploy with the tag in? Will it still get rejected? Because the phone rejects the app I think.
Hey, the ZIP contains a folder, which, if I package into a XAP, fails on deployment. What's the best way to get this packaged into a usable XAP?
trying to figure out how to install this app.
@thesecondsfade:
Bottom line of the first post:
"XAP is in DeployProvxml\bin\debug. Source included for those interested."
I distribute most of my apps this way, unless the source is really big and the XAP alone is a significantly smaller download for some reason.
@Ttblondey:
Is your phone dev-unlocked?
Is your phone either pre-Mango, or interop-unlocked?
Do you have a XAP deployment program and the Zune software?
GoodDayToDie said:
@thesecondsfade:
Bottom line of the first post:
"XAP is in DeployProvxml\bin\debug. Source included for those interested."
I distribute most of my apps this way, unless the source is really big and the XAP alone is a significantly smaller download for some reason.
@Ttblondey:
Is your phone dev-unlocked?
Is your phone either pre-Mango, or interop-unlocked?
Do you have a XAP deployment program and the Zune software?
Click to expand...
Click to collapse
My TouchXplorer does not work anymore after updating to the official Mango, though my phone is still unlocked. This XAP will definitely helps if new firmware/updates come along to deploy Provxml to /windows.
I've installed it but how can I verify if this is being installed/copied to /windows?
GoingInside said:
My TouchXplorer does not work anymore after updating to the official Mango, though my phone is still unlocked. This XAP will definitely helps if new firmware/updates come along to deploy Provxml to /windows.
I've installed it but how can I verify if this is being installed/copied to /windows?
Click to expand...
Click to collapse
This app uses the same DLL as TouchXplorer, which means it doesn't work either (I wrote a number of apps using that DLL, including a backup tool, and none of them can see any files anymore). I'm not sure exactly what was changed, but yeah, they broke it. My hope is that Heathcliff74's WP7 Root Tools will restore file browsing on HTC soon.
As soon as I finish restoring my phone, I'll try writing a version of the app that uses ProvXML to copy the file, instead of ComFileRW.dll (which no longer works if you get the final HTC update). Using ProvXML is limited in some ways - you can't browse the filesystem, for example - but it works great for this type of operation.
i'm on force unlock from Ansar's thread with Pedbe way final mango.Been trying to use advancedconfig 1.3,1.4 battery meter it don't work anymore.Good thing I can sideload(that's important)
GoodDayToDie said:
This app uses the same DLL as TouchXplorer, which means it doesn't work either (I wrote a number of apps using that DLL, including a backup tool, and none of them can see any files anymore). I'm not sure exactly what was changed, but yeah, they broke it. My hope is that Heathcliff74's WP7 Root Tools will restore file browsing on HTC soon.
As soon as I finish restoring my phone, I'll try writing a version of the app that uses ProvXML to copy the file, instead of ComFileRW.dll (which no longer works if you get the final HTC update). Using ProvXML is limited in some ways - you can't browse the filesystem, for example - but it works great for this type of operation.
Click to expand...
Click to collapse
Ok, guess I'll have to wait for the experts (Heathcliff74 and you etc) to solve this HTC drive update issue. Thank you!
GoingInside said:
Ok, guess I'll have to wait for the experts (Heathcliff74 and you etc) to solve this HTC drive update issue. Thank you!
Click to expand...
Click to collapse
@GoingInside, and anybody else in the same boat (latest HTC update installed, filesystem browsing broken), please try the latest version (v2, now on the initial post)! After running the app once, run Connection Setup and hit OK. After you do that, use a Registry Editor to check for the presence of the following registry key: HKCU\Software\DeployProvXML.
Please report whether that key is present. If it is, that means the app is fully functional even with the latest update!
I only have a NoDo Backup (my phone came with nodo) - can I get the interop unlock trough dev unlocking the phone and then running our app?
nvm, I am now downgrading to NoDo and Will then update to the HTC RTM (the one that Comes via zune). As soon as I am there I will tell you if i had luck with it or not (I hope I can interopunlock on NoDo as the 3 apps sideloadlimit is crap)
Update 1: I am on NoDo and I started your app. It cloesd, i went to Connection Setup and ran it. Will check if the registry value is there as soon as some XAPs are deployed (first time that I can deploy more than 3 XAPs )
Update 2: Now going trough the Beta - RTM - HTC Update Update marathon. Will Report back as soon as I am on HTC's RTM
GoodDayToDie said:
@GoingInside, and anybody else in the same boat (latest HTC update installed, filesystem browsing broken), please try the latest version (v2, now on the initial post)! After running the app once, run Connection Setup and hit OK. After you do that, use a Registry Editor to check for the presence of the following registry key: HKCU\Software\DeployProvXML.
Please report whether that key is present. If it is, that means the app is fully functional even with the latest update!
Click to expand...
Click to collapse
Unfortunately, it seems that the new XAP (v2) doesn't work as well. Copy and deploy the latest DeployProvXML.xap (dated 5/10/2011) to my HTC trophy. After running Connection Setup, I can't find the registry key: HKCU\Software\DeployProvXML. I only found MICROSOFT under HKCU/Software/.
But please continue your research into this. THANKS!
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
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.