Related
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.
I have found a theoric solution so far for interop-unlocking an HTC Phone. Disassembling HTC Connection Setup (since it the HTC.Shell.Registry.dll) and modifying it using IL Spy for example and include the line of code to modify the register (the dll stated before is capable of doing this).
Windows Marketplace App is capable of installing apps with Interop Services (you can install HTC Connection in fact) so we could sniff (i.e. via Wireless) the app traffic to detect when it dowloads the xap. Then by using the router settings (or a proxy or something like that) we could divert the traffic to a modified xap so the Market will download the modified xap instead (or we could even totally use another app ).
This will work only if the market hasn't those characteristics:
* It uses HTTPS to download the xaps (by the analysis I have done so far it seems not)
* It checks in any way the downloaded xap.
Do you think it could be a good idea?
I am not an expert in those things but by discussing with a colleague he stated that could be possible (difficult however in his opinion).
Microsoft?
Do you think Microsoft guys wouldn't have thought about this before and have taken preventive measures?
Never doubt HTC's ability to compromise an OS. lol I'm not all that familiar with xaps yet but I would think they have some sort of checksum or key that it can check the app with to make sure it's not corrupt.
xHausx said:
Never doubt HTC's ability to compromise an OS. lol I'm not all that familiar with xaps yet but I would think they have some sort of checksum or key that it can check the app with to make sure it's not corrupt.
Click to expand...
Click to collapse
Indeed... plus this. A similar methodology could be used to prevent what the OP suggests. I'm certainly not trying to rain on the OP's parade... in fact I hope that siomething similar can be achieved.
ATM it looks like that the only problem is that the market xaps are digitally signed. By the way the MultipleXAPInstaller program lets you sign the package when sideloading it.
i found the latest Registry Editor can run on my hd7, so maybe the interop-unlock will happen soon.
so,is it possible to interop unlock mango HTCs ?
it will run, but it wont write the values
It runs. We have also found the DLL capable of accessing the registry (they are in HTC Hub and HTC setup) but they require interop-unlock .
the only way to interop unlock is the DFT free ROM ?
Currently DFT rom is the only way for HTC WP7 device
Well XAP files are no way tampering the interop and HTC have custom build into the OS the Interop utilities as shell dll's. e.g HTCRegistryUtility.dll which we can find in any HTC ROM.
All other COMRw or COMReg dll files what we find in HTC xap files are all wrappers to trigger the typeinfo from InprocSrvr ID's predefined for HTC Interops.
Thats the reason all phones (HTC,Samsung,LG) cannot use same Unlock methods.
Best way is to somehow poke a custom certificate to spctrustroot and sign the xap files you download with that again and install.
Or somebody has to hackdown the pacmaninstaller.dll file inside the ROM and create a updatecab for that.
http://forum.xda-developers.com/showthread.php?t=1354706&page=6
this thread provides a new way to unlock
but it doesn't wok on my hd7(if it's related to my SPL version --5.0)
So, I rooted my device only a few days after getting it, and apparently there is an essential update for the Media Hub app. When I launch the app, it tries to redirect me to the market, but the market displays "No Results Found." I located the app on the desktop market it's named com.sdgtl.mediahub.tmo.vplus but it will not allow me to download it because it says none of my devices are compatible. The description of the app explicitly states that it is only for T-Mobile 4G devices and lists the Galaxy S II. I can only deduce that it does not recognize my device as compatible due to being rooted. I have searched the web but the only versions of Media Hub that I have found are those compatible with other carriers and devices. My device was rooted with Odin using the method detailed on this site, and I am not running a custom ROM. If someone knows of a way to get around downloading this from the market, another location I can download it from, or would be able to provide me with an option I haven't considered, it would be most appreciated.
Thanks
Hi,
Phone: Nokia Lumia 735
OS: WM 10.0.14393.2551
Interop Tools (Store): 2.1.27.0
After opening weather app it says, that I need to download new version, but there is no update in store. I have found some internet sources recommending reinstalling app since there is some glitch that held old version due too combined os update and hard reset. Unfortunately pressing on app let it only pin to main screen and there is no uninstall option. I have dig deeper (and I regret) that so called default apps can be uninstalled with Interop Tools. I install Interop Tools (Store), but there is nowhere "applications" section as at least 2 sources says, so I can remove app. I'm guessing this is due to missing so-called "extension providers". On main screen of Interop Tools there is option called "Get extensions", but it redirects to some website with basic auth / htaccess in domain insidewindows.net so i'm unable to download anything.
Is there anyway you could help me kick this off, so I can reinstall weather widget? I would be grateful for some easy steps if possible, cause I'm obviously missing something and feel really dumb because of it :/
Uninstall the weather app using Interop tools
and then install it from store