Whoa, there are a lot of potentially *REALLY* handy files in there. If they're retail-signed (unlikely, but I can hope...) then we should be able to get them working on retail phones. If not retail-signed, they may still be useful though we'd need to run them in a chamber with ID_CAP_DEVELOPERUNLOCK (I'm still hoping I can manage to get that cap onto a service chamber; that would be awesome).
[XAP][GUIDE] Interop Unlock for WP8 + all Capabilities
- Thread starter GoodDayToDie
- Start date
Not sure why you highlighted the fact that the SD card, which has a nice simple identifier, is mounted as drive D: since that's not exactly news. I'm much more interested in why you have drives E, F, and G; WP8.1 mounts the Data partition at U: (as well as at C:\Data), and there are a few other partitions which are mounted off of C:\EFIESP, C:\DPP, and C:\MMOS that could also have been assigned drive letters, but I wouldn't expect it to be those drive letters.
Because he is running custom CSC. Btw, he's the author of this tweak. Setting drive letters to partitions allows you to see 'em via MTP.
Aha! Clever. Would have tried that myself, except for the inability to set binary-type registry values on my Samsung (short of CSC, which I never tried).
Still wish I knew why MTP doesn't read through volume mount points like C:\EFIESP correctly. It *should* but it doesn't.
Still wish I knew why MTP doesn't read through volume mount points like C:\EFIESP correctly. It *should* but it doesn't.
Maybe It is well known but I didn't see anywhere to post it
you can see usb or some other capabilities didn't mentioned in Visual Studio
I tried to add them manually to AppxMainfest (like what we do for ID_CAP_INTEROPSERVICES ) I get warning and after trying to Install I get Error :
any idea about this capability or how to use it ?
is there any chance to add a new capability here ?
Code:
HKLM\SoftWare\Microsoft\SecurityManager\WindowsCapabilitiesI tried to add them manually to AppxMainfest (like what we do for ID_CAP_INTEROPSERVICES ) I get warning and after trying to Install I get Error :
Code:
Error 4 App manifest validation failed. Value 'usb' of attribute '/Package/Capabilities/Capability/@Name' must be a valid capability. C:\Users\****\documents\visual studio 2013\Projects\SomeTest\SomeTest\Package.appxmanifest 37 17 SomeTestis there any chance to add a new capability here ?
That looks more like an error of packaging than an error of installation. Visual Studio raises similar complaints if you try to build a .XAP file with "secret" capabilities.
That registry key (which is new to 8.1) maps WinRT capabilities to SIDs. Some of those SIDs are for existing Windows Phone capabilities (like location; pretty sure that's the same SID as ID_CAP_LOCATION); others are new.
This should be investigated!
That registry key (which is new to 8.1) maps WinRT capabilities to SIDs. Some of those SIDs are for existing Windows Phone capabilities (like location; pretty sure that's the same SID as ID_CAP_LOCATION); others are new.
This should be investigated!
I packed it without "usb" capability . then add this cap to the Related xml file in appx
after trying to install I get same error as Visual Studio .
seems for WP8.1 store apps there is a check before deploying file ! Deployer first capabilities *Then* phone checks the capabilities or also maybe phone doesn't check for them ! I'm not sure about it but I know there's a before deploy cap check .
maybe adding Capabilities SID as Silverlight apps can help us to get higher access easier .I'll try and notice if there were any good news
OK OK .
bad news .
we need to create a new DLL file or a Third Party appx deployer to run other capabilities
In this address :
you can see Microsoft.Phone.Tools.Deploy.dll file .
In Microsoft.Phone.Tools.Appx you can see this Enum : ST_Capabilities and ST_Capabilities1
In these two enums you can see this code :
OK so we are limited to these caps untill we Patch this file .
but maybe you have this question why we can deploy so many capabilities In silverlight apps very simple .
here is the reason :
we have same enums for wp7.1 , 8.0 and also 8.1 :
here is 7.1 :
and here is 8.1 :
bad news .
we need to create a new DLL file or a Third Party appx deployer to run other capabilities
In this address :
Code:
C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.1\Tools\AppDeployIn Microsoft.Phone.Tools.Appx you can see this Enum : ST_Capabilities and ST_Capabilities1
In these two enums you can see this code :
Code:
public enum ST_Capabilities
{
appointments,
contacts
}
Code:
public enum ST_Capabilities1
{
internetClient,
internetClientServer,
privateNetworkClientServer,
documentsLibrary,
picturesLibrary,
videosLibrary,
musicLibrary,
enterpriseAuthentication,
sharedUserCertificates,
removableStorage
}OK so we are limited to these caps untill we Patch this file .
but maybe you have this question why we can deploy so many capabilities In silverlight apps very simple .
here is the reason :
we have same enums for wp7.1 , 8.0 and also 8.1 :
here is 7.1 :
Code:
public enum CT_CapabilityName
{
ID_CAP_APPOINTMENTS,
ID_CAP_CAMERA,
ID_CAP_CONTACTS,
ID_CAP_FILEVIEWER,
ID_CAP_GAMERSERVICES,
ID_CAP_IDENTITY_DEVICE,
ID_CAP_IDENTITY_USER,
ID_CAP_INTEROPSERVICES,
ID_CAP_ISV_CAMERA,
ID_CAP_LOCATION,
ID_CAP_MEDIALIB,
ID_CAP_MICROPHONE,
ID_CAP_NETWORKING,
ID_CAP_NETWORKING_ADMIN,
ID_CAP_PHONEDIALER,
ID_CAP_PUSH_NOTIFICATION,
ID_CAP_RINGTONE_ADD,
ID_CAP_SENSORS,
ID_CAP_WEBBROWSERCOMPONENT,
ID_CAP_OEMPUBLICDIRECTORY,
ID_HW_FRONTCAMERA
}
Code:
public enum CT_CapabilityName
{
ID_CAP_ACCESSIBILITY = 0,
ID_CAP_APPOINTMENTS = 1,
ID_CAP_CALLMESSAGING_FILTER = 0x3f,
ID_CAP_CAMERA = 2,
ID_CAP_CELL_API_COMMON = 0x25,
ID_CAP_CELL_API_LOCATION = 0x27,
ID_CAP_CELL_API_OEM_PASSTHROUGH = 0x24,
ID_CAP_CELL_API_UICC = 0x3a,
ID_CAP_CELL_API_UICC_LOWLEVEL = 0x26,
ID_CAP_CELL_WNF = 40,
ID_CAP_CONTACTS = 3,
ID_CAP_CSP_FOUNDATION = 0x3b,
ID_CAP_CSP_MAIL = 0x2c,
ID_CAP_CSP_OEM = 0x38,
ID_CAP_CSP_W4_APPLICATION = 0x2d,
ID_CAP_CSP_WIFI_HOTSPOT = 0x3d,
ID_CAP_DEVICE_MANAGEMENT = 0x2a,
ID_CAP_DEVICE_MANAGEMENT_ADMIN = 0x29,
ID_CAP_DEVICE_MANAGEMENT_BOOTSTRAP = 0x34,
ID_CAP_DEVICE_MANAGEMENT_SECURITY_POLICIES = 0x2e,
ID_CAP_DU_MIGRATOR_STATUS_OEM = 0x30,
ID_CAP_DU_PROVISIONING = 0x2f,
ID_CAP_GAMERSERVICES = 4,
ID_CAP_IDENTITY_DEVICE = 5,
ID_CAP_IDENTITY_USER = 6,
ID_CAP_INPUT_FEATURES = 0x43,
ID_CAP_INTERNET_EXPLORER_FAVORITES = 0x3e,
ID_CAP_INTERNET_EXPLORER_SEARCH_PROVIDER_KEYS_HKCU = 0x45,
ID_CAP_INTEROPSERVICES = 7,
ID_CAP_ISV_CAMERA = 8,
ID_CAP_KIDZONE_CUSTOMIZATION = 0x36,
ID_CAP_LOCATION = 9,
ID_CAP_MAP = 0x22,
ID_CAP_MAP_WRITE = 0x33,
ID_CAP_MEDIALIB_AUDIO = 10,
ID_CAP_MEDIALIB_PHOTO = 12,
ID_CAP_MEDIALIB_PHOTO_FULL = 13,
ID_CAP_MEDIALIB_PLAYBACK = 11,
ID_CAP_MICROPHONE = 14,
ID_CAP_NETWORKING = 15,
ID_CAP_NETWORKING_ADMIN = 0x10,
ID_CAP_NV_READWRITE = 0x2b,
ID_CAP_OEM_ADC = 0x37,
ID_CAP_OEM_DEPLOYMENT = 60,
ID_CAP_OEMPUBLICDIRECTORY = 0x19,
ID_CAP_PEOPLE_EXTENSION = 0x11,
ID_CAP_PEOPLE_EXTENSION_IM = 0x39,
ID_CAP_PEOPLE_EXTENSION_MOBILE = 0x12,
[XmlEnum("ID_CAP_PEOPLE_EXTENSION_MOBILE")]
ID_CAP_PEOPLE_EXTENSION_MOBILE1 = 50,
[XmlEnum("ID_CAP_PEOPLE_EXTENSION")]
ID_CAP_PEOPLE_EXTENSION1 = 0x31,
ID_CAP_PERSONAL_INFORMATION_IMPORT = 0x13,
ID_CAP_PHONEDIALER = 20,
ID_CAP_PROXIMITY = 30,
ID_CAP_PUSH_NOTIFICATION = 0x15,
ID_CAP_REMOVABLE_STORAGE = 0x23,
ID_CAP_RINGTONE_ADD = 0x16,
ID_CAP_RUNTIME_CONFIG = 0x42,
ID_CAP_SENSORS = 0x17,
ID_CAP_SHELL_DEVICE_LOCK_UI_API = 0x1a,
ID_CAP_SMS_INTERCEPT_AGENT = 0x40,
ID_CAP_SMS_INTERCEPT_RECIPIENT = 0x41,
ID_CAP_SPEECH_RECOGNITION = 0x1b,
ID_CAP_SYNC_EXTENSION = 0x35,
ID_CAP_VOICEMAIL = 0x1d,
ID_CAP_VOIP = 0x1c,
ID_CAP_WALLET = 0x1f,
ID_CAP_WALLET_PAYMENTINSTRUMENTS = 0x20,
ID_CAP_WALLET_SECUREELEMENT = 0x21,
ID_CAP_WEBBROWSERCOMPONENT = 0x18,
ID_CAP_WIFI_BASIC = 0x44
}
@GoodDayToDie Lumias are calling out to you......lol jk
and we must guess which phone you have???
if you have Lumia phone, for interop unlock your phone must have Sd card... if not you cant interop unlock...
first: you need developer unlock (pay or free)
second: you need to install WP SDK 8.1 (full or lite) to computer
third: you need to unlock phone with tool from WP SDK 8.1
fourth: now you can deploy xap files to phone or SD (depend to settings in storage sense where to install app) with tool from WP SDK...
fifth: http://xdaforums.com/windows-phone-8/development/xap-vcreg-lumia-reg-editor-live-interop-t3135326 and http://xdaforums.com/showpost.php?p=62601965&postcount=175
I am using Lumia 640 XL Dual LTE
After rom builder install and when the build button is pressed, success msg comes ., and in the instructions it was said to hard rest, after hard rest the phone is back to normal as a new phone. I don't see a thing. I at least expect some software to mod the OS. Ut I see no thing.
Is there any other way to Install Windows 10 to my phone using the PC. I don't have WiFi.
Attachments
Last edited:
hard reset?????? no, i dont see this.... read my instructions here http://xdaforums.com/showpost.php?p=62601965&postcount=175
Can't get to understand how do I add ID_CAP_INTEROPSERVICES capability on Windows 10 Mobile.
I have a Samsung ATIV S with 10.0.10586.164 on it.
I've used WOLF's InteropUnlocker_W10M.xap app to internal memory, ran it on the phone and now it says:
Obviously I don't because when I run any app that requires Interop services, I get an error, or I simply cannot deploy the app. For example, if I start vcREG, it returns:
If I use CustomPDF Registry Editor + Tweaks and navigate to HKLM\SOFTWARE\Microsoft\SecurityManager\Capabilities, I don't see ID_CAP_INTEROPSERVICES Multistring value there. And I cannot add it myself, because there is no change access to the HKLM\SOFTWARE\Microsoft\SecurityManager\Capabilities key.
Everywhere on the forum it says that absence of ID_CAP_INTEROPSERVICES capability means that, obviously, the phone is not interop-unlocked.
On Windows Phone 8.1 Update 2 I used the old trick:
1. Installed CustomWPSystem to internal memory.
2. Installed Preview For Developers to the SD card.
3. Placed CustomPFD.xap anywhere on the phone (either SD Card or Phone's internal memory)
4. Opened CustomWPSystem and deployed CustomPFD to the SD card.
The CustomWPSystem app replaces files of Preview For Developers with CustomWPSystem and you're good to go.
How is it done on Windows 10? The old September version of extras + info app can be downloaded from Microsoft CDN through apps4fun... but I cannot deploy it. Seems like its XAP is not accepted by Deployment tool (and for some reason it cannot be opened as a ZIP archive; what's wrong with it.)
How do you add ID_CAP_INTEROPSERVICES capability on a SAMSUNG ATIV S phone running Windows 10 Mobile?
Could somebody please elaborate?
Thanks.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
71It took us much longer than WP7 did, but the first Interop Unlock hack for WP8 is now available. It's currently limited to SAMSUNG phones, although we're trying to extend it to other phones, of course.
WARNING: Samsung is trying to break this hack! If you take the retail upgrade to GDR3 including the Samsung firmware update, it will not work!
A brief summary, for those unfamiliar with interop-lock: Windows Phone allows a number of high-privilege app capabilities, which can be used to make changes to the OS which are normally not possible for a third-party app. The limitation on whether we can use these capabilities or not is based on what "level" of developer unlock the phone has; standard "ISV" (Independent Software Vendor) dev unlock (max 10 apps or less) is what pretty much everybody gets; OEMs, however, get a special OEM Developer Unlock (300 apps or more) which gives them the ability to use much higher-privilege app capabilities than the standard ISV unlock permits. The name comes from ID_CAP_INTEROPSERVICES, the capability which was most important in WP7. In WP8, however, there are a great many interesting capabilities. Note that Interop-unlock by itself does not enable all of these. However, at least on Samsung phones, it is now possible to enable *all* the capabilities.
Guide for Samsung's ATIV phones:
If you want to enable sideloading even more high-privileged apps, you'll want the following:
Capabilities which will be enabled, without further modification, by using interop-unlock:
One of the goals of this thread will be to explore what we can do with interop-unlock, and look for ways to achieve full permissions. I think I've found one, but it requires the ability to write registry multi-string values. Basically, if we could add a "superuser" privilege, or enable the use of ID_CAP_BUILTIN_TCB, which already has it, this would allow the creation of "root" apps.
Aside from myself, credit for this hack goes to @cpuguy for the Native Toast Launcher tool which permits accessing otherwise-unreachable code, and @-W_O_L_F- for helping put the pieces together. I'm not actually certain which one of us achieved the interop-unlock first; we were both working on it. @Heathcliff74 continues to be a help on the quest for full-unlock.
The source code for the apps below is posted at http://xdaforums.com/showpost.php?p=45606584&postcount=8822Root unlock achieved (EDIT: Sigh, not quite) on my ATIV S. Details forthcoming. In the meantime, rest assured: it is possible. This still won't let old apps be used, but it will let new "root" apps be written. Basically, an all-new WP8 Root Tools.
EDIT: Agh. Still not working. I'm trying, though!1917Hi all,
Sorry for this off-topic message. But everybody who concerns this, follows this thread. So I'll drop it here.
Today something amazing happened. I received a package from Italy. It was the long-awaited Samsung Ativ-S developer device. Many people donated money so we could buy a new phone for @sireangelus and he could send his phone to me. Within a few days money was collected, new device bought and sent to @sireangelus. After that, silence... I sent several PM's to him often no response. Or messages of him trying to be funny or whatever. But nothing was sent. I'm not easily pissed off, but last week, almost 2 months after he promised to send the phone, I got really angry and I sent him a couple of whatsapp messages to convince him he should keep his promise and don't be an @$$. Today I received the package.
This night I had some time to check it out. Conclusion: it is really a developer device and very valuable for research! Yay!
I already had an incident with it. I connected the device in mass-storage mode to my laptop, while I already had a WP8 virtual disk mounted. Windows 8 decided that all partitions needed to be unique and it actually changed the entries in the partition table of the Samsung (!!!) It couldn't boot any more. Luckily, I could still use mass-storage, so I could still inspect the device. I found that the partition table was corrupted and I could manually fix it. Pfew! All is working well again and I can further dissect it.
Thanks to @sireangelus for finally sending the phone. I advise you to act more pertinent the next time you sell something, in order to avoid that people are getting really pissed off at you.
Thanks to all guys who donated to make this possible. I hope to bring you new hacks soon!!
Ciao,
Heathcliff7416Questions and Answers
Can I install WP7 interop apps using this?
They will install, but there's no point. They almost certainly won't actually work. Interop-unlock enables access to parts of the OS which third-party developers were not intended to touch; consequently, there's no backward compatibility. Even the methods used for native code on WP7 (which is different from, but nearly essential to make use of, interop-unlock) won't work on WP8. However, it should be possible to port many of those applications to WP8.
Will this work on Lumia phones / How can I get this on my Lumia / Are you working on this for Lumia phones / What about HTC, or some other OEM?
The current hack relies on a Samsung-specific component. Adding support for other phones will require new hacks. We are looking into it, rest assured; at this time, however, there is no way to gain interop-unlock on any WP8 device other than a Samsung one.
EDIT: It looks like there should soon be a Huawei W1 custom ROM with interop-unlock included. I don't deal with custom ROMs, but you may be able to use homebrew apps on that phone too.
EDIT: Lumia phones *can* be interop-unlocked via JTAG. However, this requires some extra hardware and some phone disassembly. Not an online hack, and not for the faint of heart.
But what if we installed the Diagnosis app on a Lumia phone (using Fiddler proxy or similar) and then followed this guide?
I repeat, Samsung-specific component. Nokia doesn't put the required services/drivers for Samsung's Diagnosis app into their Lumia firmware, so the app would not work!
Can I upgrade my phone to GDR3 if I have this?
Yes. However, be aware: if you install Samsung's updates that come with the retail GDR3 update, it will break your ability to re-unlock, or to use some homebrew apps! (Developer preview updates are fine, as those are purely Microsoft code and don't mess with the Samsung components.)
EDIT: There's a way to unlock the Samsung services for full access again on GDR3. You still need to interop-unlock beforehand, though.
Can I re-lock my phone if I want to?
Yes, easily. The simplest method is to use the Windows Phone Developer Registration tool (the one that comes with the SDK) to de-register the phone (you can then re-register it if you want to get your normal dev-unlock back). This doesn't remove any changes that were made using the interop-unlock, though (for example, it won't undo the EnableAllSideloading hack, not will it set back the Full FS Access hack). Apps that require interop-unlock will still be installed, but may no longer run. To manually remove interop-unlock, you can reset all the registry values that were changed by the interop-unlock hack to their original values, and remove all the apps. There still may be a great many other changes that also need reverting, though, if you want to get back to stock settings. See next question.
Can I get my phone completely back to stock settings without knowing every little thing I changed?
Yes, a hard (factory) reset will undo all changes made by interop-unlock, or any apps (including ones that require interop-unlock), and will remove all apps. If you need to send your phone in for warranty servicing and are worried that they won't take it because you interop-unlocked it, this approach will fix that (they would probably tell you to hard-reset anyhow, if it's conceivably a software problem).
Will the interop-unlock survive a hard reset?
Not using this method! Read the question above. This unlock is purely in software, not firmware; it is reset along with everything else.
Can I upgrade my phone to WP8.1 if I have this?
Tentatively, yes! We're still working on figuring out exactly what WP8.1 means for the homebrew scene. The short version is that most apps and some (but not all) of the hacks they contain seem to still work, though. However, see next question...
Can I interop-unlock my phone on WP8.1?
At this time, I don't believe this is possible (unless you can use a custom ROM). One step of the process appears to have been "fixed" and we will need to find a different way. -W_O_L_F- has indicated that he has one, possibly coming soon...
