Develop Bugs

Tom XAP Author: Change request

(The original thread has too many pages, and would likely go unnoticed.)
We, in Chevron support land, keep receiving the same complaints over and over again re: Tom XAP Installer. Users are attempting to use Tom XAP Installer (v1.2) to deploy interop-required XAPs and they're receiving the misleading error message:
- Please Make sure your phone was unlocked!
- Please Make sure you connected device to PC and Zune lauched
Try again ?
Click to expand...
Click to collapse
We'd appreciate if you added code to detect 0x81030120 and show a proper error message. It should say something like:
Your phone is not "interop unlocked", which this XAP requires [...] Check out this thread on XDA for more information.
Click to expand...
Click to collapse
Thanks.

Why not just tell people to use the official MS deployment tool?

I always use the Ms original tool , or a private one from one here at xda.

ceesheim said:
I always use the Ms original tool , or a private one from one here at xda.
Click to expand...
Click to collapse
which one do you use. Actually those who wants to sideload should have a few xap installer apps in their pc then they will know whether it's the chevron unlock or their installer that has a problem>I know that installer has some pros and cons.

Ttblondey said:
which one do you use. Actually those who wants to sideload should have a few xap installer apps in their pc then they will know whether it's the chevron unlock or their installer that has a problem>I know that installer has some pros and cons.
Click to expand...
Click to collapse
I use the MS one and a closed beta from ultrashot (ultrashot one isn't online and maybe never will so don't ask him, if he wants to release he will )
no the problem is @ tom xap sideloader , and I didn't see him here for a long time @ the wp forums

[INFO] List of Unlocks by Type/OEM

UNLOCKS LISTED FROM MOST TO LEAST POWERFUL, MORE POWERFUL INCLUDES LOWER LEVELS. THIS IS NOT A CARRIER UNLOCK THREAD.
Dell (1st Gen)
Full Unlock: No method yet
Root Unlock: No method yet
Interop Unlock: No method yet
Developer Unlock: Two (was three) methods:
* Register for AppHub account to sideload 10 apps ($99 a year)
* Register for AppHub student to sideload 3 apps (Free, must be a student)
* Purchase Chevron Labs Token to sideload 10 apps (Tokens have sold out, old tokens valid until July 2012)
HTC (1st Gen)
Full Unlock: Via custom ROM's
Root Unlock: Per app via Root Tools (v1 drivers required), Per app via HtcRoot Project (v0 drivers required)
Interop Unlock: Via Heathcliff74's unlock pending driver version
Developer Unlock: Two (was three) methods:
* Register for AppHub account to sideload 10 apps ($99 a year)
* Register for AppHub student to sideload 3 apps (Free, must be a student)
* Purchase Chevron Labs Token to sideload 10 apps (Tokens have sold out, old tokens valid until July 2012)
HTC (2nd Gen)
Full Unlock: No method yet
Root Unlock: No method yet
Interop Unlock: No method yet
Developer Unlock: Two (was three) methods:
* Register for AppHub account to sideload 10 apps ($99 a year)
* Register for AppHub student to sideload 3 apps (Free, must be a student)
* Purchase Chevron Labs Token to sideload 10 apps (Tokens have sold out, old tokens valid until July 2012)
LG (1st Gen)
Full Unlock: No method yet
Root Unlock: Per app via Root Tools
Interop Unlock: Via OEM diagnosis tool/registry editor
Developer Unlock: Three (was four) methods:
* Via OEM diagnosis tool/registry editor to sideload unlimited apps (Free, works on all firmwares)
* Register for AppHub account to sideload 10 apps ($99 a year)
* Register for AppHub student to sideload 3 apps (Free, must be a student)
* Purchase Chevron Labs Token to sideload 10 apps (Tokens have sold out, old tokens valid until July 2012)
Nokia (2nd Gen)
Full Unlock: Phones with the Qualcomm bootloader (Q&A)
Root Unlock: No method yet
Interop Unlock: Phones with the Qualcomm bootloader (Q&A)
Developer Unlock: Two (was three) methods:
* Register for AppHub account to sideload 10 apps ($99 a year)
* Register for AppHub student to sideload 3 apps (Free, must be a student)
* Purchase Chevron Labs Token to sideload 10 apps (Tokens have sold out, old tokens valid until July 2012)
Samsung (1st Gen)
Full Unlock: Via custom ROM's
Root Unlock: Per app via Root Tools
Interop Unlock: Via WindowBreak/Heathcliff74/voluptuary unlocks (Must be prior to KK2 firmware)
Developer Unlock: Three (was four) methods:
* WindowBreak to sideload unlimited apps (Free, also Interop Unlocks. Firmware dependant)
* Register for AppHub account to sideload 10 apps ($99 a year)
* Register for AppHub student to sideload 3 apps (Free, must be a student)
* Purchase Chevron Labs Token to sideload 10 apps (Tokens have sold out, old tokens valid until July 2012)
Samsung (2nd Gen)
Full Unlock: No method yet
Root Unlock: Per app via Root Tools
Interop Unlock: Via WindowBreak/Heathcliff74/voluptuary unlocks pending firmware version
Developer Unlock: Three (was four) methods:
* WindowBreak to sideload unlimited apps (Free, also Interop Unlocks. Firmware dependant)
* Register for AppHub account to sideload 10 apps ($99 a year)
* Register for AppHub student to sideload 3 apps (Free, must be a student)
* Purchase Chevron Labs Token to sideload 10 apps (Tokens have sold out, old tokens valid until July 2012)
If any of this info is out of date please post upto date info in this thread and I will update it.
Briefcase said:
Please take in mind that there are lots of phones out there which can be interop unlocked but only by reverting back to ROMs before certain driver versions. Once such ROM is loaded, apply Interop Unlock, and let zune update to the latest version. This can be a time consuming operation. Also note that while upgradeing this interop unlocked roms will remain interop unlocked (no updates have been found which relock the phones as of yet) it might mean that certain tools (TouchExperience for example) stop working because they use exploits only available in certain drivers.
Click to expand...
Click to collapse
Thanks: Briefcase for original idea, all the great devs who work to find unlocks (Jaxbot, Heathcliff74, DFT Team, GoodDayToDie, and others)

Definitions of Unlocks:
FULL: Policy has been modified to allow for running of native executables. This lets you do things like running properly recompiled Windows Mobile code. This also allows for all the things root unlock offers.
ROOT: Policy is elevated on a per app basis via Root Tools (version 0.9) to allow Silverlight apps to run with root privilege. This lets you do things like install XAP's via IE.
INTEROP: Achieved by setting MaxUnsignedApps to 300 or greater. This allows an app to use the Interop Services capability, meaning it can use drivers on the phone. This allows for neat things like editing the registry or accesssing the file system. Just to be clear though just because your device is Interop Unlocked that does always mean that hacks that require Interop Unlock to deploy will work on your device since they may use exploites that don't exist on your device.
DEVELOPER: This allows a user to sideload apps.
Heathcliff74 does a great job of explaining this all in greater detail over HERE, or in his BLOG.
WHAT PHONE DO YOU HAVE:
Dell (1st Gen) Phones:
Venue Pro
HTC (1st Gen) Phones:
Arrive*
7 Pro
HD7
HD7S
Mozart
Surround
Trophy*
HTC (2nd Gen) Phones:
Titan
Titan II
Radar
LG (1st Gen) Phones:
Optimus 7
Quantum
Nokia (2nd Gen) Phones:
Lumia 610
Lumia 710
Lumia 800
Lumia 900
Samsung (1st Gen) Phones:
Focus
Omnia 7
Samsung (2nd Gen) Phones:
Focus Flash
Focus S
Omnia W
*CDMA only phones can only be interop/full unlocked via custom ROM's, also the Verizon Trophy can be Interop Unlocked but requires v1 drivers and extra steps to unlock.

If you got the time you should incorperate the following caveats (see my post here):
Please take in mind that there are lots of phones out there which can be interop unlocked but only by reverting back to ROMs before certain driver versions. Once such ROM is loaded, apply Interop Unlock, and let zune update to the latest version. This can be a time consuming operation. Also note that while upgradeing this interop unlocked roms will remain interop unlocked (no updates have been found which relock the phones as of yet) it might mean that certain tools (TouchExperience for example) stop working because they use exploits only available in certain drivers.
Click to expand...
Click to collapse
Because now, although better than having no list at all, it isn't complete.
Also methods for developer unlock are the same for any phone type so they could be taken apart. You migh also want to explain what the different type of unlocks are for to be very complete (link to approriate resources).

Good job. Ask mods to pin this thread to the forum's top.
P.S. May be, Q&A is better place for that topic?

sensboston said:
Good job. Ask mods to pin this thread to the forum's top.
P.S. May be, Q&A is better place for that topic?
Click to expand...
Click to collapse
Yeah, I thought about where to post this for a bit, I figured it has more to do with dev & hacking but if a mod feels it should be in the Q&A or maybe even General by all means. I just figured it might cut down on the Q's asked here in Development if it stays here.

u wrote 7 times about how to get dev-unlocked, little bit redudant, don't you think so ? what about a grid, displaying it clearer? just a suggestion
so far, well done

roqstr said:
u wrote 7 times about how to get dev-unlocked, little bit redudant, don't you think so ? what about a grid, displaying it clearer? just a suggestion
so far, well done
Click to expand...
Click to collapse
Redundant, Yes. But if I don't do it that way I can almost guarantee that someone will ask/say "So I can't developer unlock my phone? I know it says all phones can dev unlock via these means but does that include mine?"
These are the same people that ask Q's in the dev & hacking forum...

excellent vedemecum
now we have a fast look place to check unlocking status of our devices.
thank you!

How does the new version of WP7 Root Tools fit into this?
It's going to allow you to give root access on an app-by-app basis... which gives the apps you select the same level of access as a full unlock, without being a full unlock.

we will cross that bridge when we get there.

A few clarifications:
HTC gen1.5 (the CDMA phones, Sptrint's Arrive and Verizon's Trophy) are special cases.
Arrive can't be interop-unlocked at all right now, short of a custom ROM. This is because it can't use Connection Setup.
VTrophy can be IUed, but requires special instructions beyond the normal steps for pure-GSM phones.
Last I checked, there aren't any *published* custom ROMs for the Verion Trophy (not sure about the Arrive) although I know some are in development.
HTC Custom ROMs:
Up-to-date GSM phones will need their bootloaders downgraded. For gen1 phones, there are some ways to do this. If you don't downgrade first (to bootloader/SPL 3.1 or below) and try to install a custom ROM, you'll break the bootloader somewht permanently (very hard to repair).
LG phones:
The registry editing can be used for dev-unlock as well as interop-unlock. In fact, Interop-unlock is meaningless without dev-unlocking first (applies to all phones).
Samsung phones (both generations):
WindowBreak is a dev-unlock as well as an interop-unlock. You might want to distinguish it from the other Samsung interop-unlocks, which require first getting a dev-unlock somehow.
I hope to get full-unlock (I already have arbitrary-app-as-root) on HTC gen1 via the HtcUtility driver (part of HtcRoot project). But, that will take time and will only work on very old firmware (from the Mango beta days). It will also require already being interop-unlocked.

GoodDayToDie said:
A few clarifications:
HTC gen1.5 (the CDMA phones, Sptrint's Arrive and Verizon's Trophy) are special cases.
Arrive can't be interop-unlocked at all right now, short of a custom ROM. This is because it can't use Connection Setup.
VTrophy can be IUed, but requires special instructions beyond the normal steps for pure-GSM phones.
Last I checked, there aren't any *published* custom ROMs for the Verion Trophy (not sure about the Arrive) although I know some are in development.
HTC Custom ROMs:
Up-to-date GSM phones will need their bootloaders downgraded. For gen1 phones, there are some ways to do this. If you don't downgrade first (to bootloader/SPL 3.1 or below) and try to install a custom ROM, you'll break the bootloader somewht permanently (very hard to repair).
LG phones:
The registry editing can be used for dev-unlock as well as interop-unlock. In fact, Interop-unlock is meaningless without dev-unlocking first (applies to all phones).
Samsung phones (both generations):
WindowBreak is a dev-unlock as well as an interop-unlock. You might want to distinguish it from the other Samsung interop-unlocks, which require first getting a dev-unlock somehow.
I hope to get full-unlock (I already have arbitrary-app-as-root) on HTC gen1 via the HtcUtility driver (part of HtcRoot project). But, that will take time and will only work on very old firmware (from the Mango beta days). It will also require already being interop-unlocked.
Click to expand...
Click to collapse
I made a note about the Arrive in the second post already, I'll add the Trophy to the note.
I'll will clarify the whole WindowBreak thing, I have it listed that higher level unlocks include the lower level abilities but I suppose it would be a good idea to mention that WindowBreak doesn't need dev unlock first.
I plan to note full privilege app escalation once that is available but I don't want to confuse people for now.
I'll have to give ya a thanks tomorrow, I seem to have maxed myself out today but thanks for all the good points.

Great idea & post! Would hit the thanks button if they had it on the WP7 app.
Sent from my Kick Ass Lil Radar using XDA Windows Phone 7 App

Congrat for the idea. Good work, I read the thread twice a day and I wait for a news. THX (+)

voluptuary;23445194[COLOR="Red" said:
*[/COLOR] CDMA only phones can only be interop/full unlocked via custom ROM's, also the Verizon Trophy requires extra steps and specific drivers to unlock.
Click to expand...
Click to collapse
This is not completely true. Arrives can only be IU with custom ROM. The Verizon Trophy with v1 drivers stock ROMs CAN be IU but you follow a slightly different procedure (Heathcliff has it in his first post here). I came up with this procedure and several (myself included) have used it.
---------- Post added at 02:11 PM ---------- Previous post was at 02:07 PM ----------
Well, technically what is stated is true since the VZW Trophy is not a CDMA only but CDMA and GSM, but it is not clear what is written implies the Trophy is fine with Stock as long as v1 drivers are used.

LiFePo4 said:
This is not completely true. Arrives can only be IU with custom ROM. The Verizon Trophy with v1 drivers stock ROMs CAN be IU but you follow a slightly different procedure (Heathcliff has it in his first post here). I came up with this procedure and several (myself included) have used it.
---------- Post added at 02:11 PM ---------- Previous post was at 02:07 PM ----------
Well, technically what is stated is true since the VZW Trophy is not a CDMA only but CDMA and GSM, but it is not clear what is written implies the Trophy is fine with Stock as long as v1 drivers are used.
Click to expand...
Click to collapse
I'll try to make it a little more clear.

Leapo said:
How does the new version of WP7 Root Tools fit into this?
It's going to allow you to give root access on an app-by-app basis... which gives the apps you select the same level of access as a full unlock, without being a full unlock.
Click to expand...
Click to collapse
While it gives root access to Silverlight apps, it won't be the same as full unlock. You will not be able to run native executables etc.

thx alot for this topic
simple request can u add the unlocking topic of each non released yet phone

Dr.Mazika said:
thx alot for this topic
simple request can u add the unlocking topic of each non released yet phone
Click to expand...
Click to collapse
If it's not released then how will we know what can and can't be done on it yet? I think it's safe to just assume that if a phone isn't out yet and thus not in the hands of a dev the status of unlocks of any kind aside from official dev unlocks would be 'unknown'

Wow, coming from Android this is a complete 180
Just a quick question, but I have a Samsung Omnia W and did a succesful Windowbreak on it so are you saying that it is now Interop as well as Developer unlocked ??
If that is so then I wonder why it is that the majority of 3rd party apps I have managed to succesfully put on my phone do not work.
Apps such as Metro Themes, Advanced Configuration Tool and WP7 Root Tools. I am basically looking to apply custom colours to my tiles and background and have not been able to do it at all.
I thought a Developer unlock would allow me to do all these things ?
I must be missing something
Cheers for a great guide !! Really makes things much more clear !!
Cheers, LL13-

[XAP + SDK] WP7 Root Tools 0.9

Download: www.wp7roottools.com
Today I am proud to announce the immediate availability of WP7 Root Tools 0.9 alpha and WP7 Root Tools SDK 0.1!
WP7 Root Tools 0.9 brings true Root Access to devices with stock ROM's, but it also works on devices with custom ROM's and Full Unlock. Your device needs to be Interop Unlocked to use WP7 Root Tools!
This is still an alpha-release, because there are a lot of new hacks and the tools are still not feature complete! I have rewritten about 75% of all code from the previous release. So before you install WP7 Root Tools you should make a backup of your device. WP7 Root Tools will make changes to system settings and, although this has been tested, it is still possible that a problem occurs. In that case you want to have a recent backup of your device. Installing WP7 Root Tools will be your own responsibility. The author of WP7 Root Tools and the SDK cannot be held responsible for any damages caused directly or indirectly by installing and using WP7 Root Tools or the SDK!
Windows Phone is a closed system to protect the user and his/her personal data from malware and to protect the intellectual property of the developers. The downside of this closed system is that homebrew developers are very limited in their ability to control and tweak a Windows Phone device. With WP7 Root Tools I attempt to open up the system in a gentle way, so that users stay in control of their device, while homebrew apps can get more control to get the maximum power out of your Windows Phone device!
WP7 Root Tools 0.9 now has a File Explorer, Registry Editor, Certificate Installer and a Policy Editor! Thanks to true Root Access on Windows Phone, this new version of WP7 Root Tools will work a lot faster than previous releases and it supports a lot more devices!
WP7 Root Tools should work on these devices:
- Samsung first and second generation devices
- LG devices
- HTC first generation devices with Mango v1 drivers (SPL 4.x or lower)
- Samsung first generation devices with custom ROM and Full Unlock
- HTC first generation devices with custom ROM and Full Unlock
On devices with stock ROM's WP7 Root Tools need to install Root Access. The first time it runs, a 2-phase-installation will start. The app will inform you to start the first install-phase. Then the device will reboot after a few seconds. After the reboot you need to start WP7 Root Tools again immediately! Then the second phase of the installation will start and your device will be rebooted again. After the second reboot you are ready to use WP7 Root Tools. You can use the Policy Editor to give other homebrew app a "trusted" status. With this you will give the app Root Access privileges. So be very careful to which app you give Root Access!! You are responsible for giving access to an app! If you are not sure, read the forums to decide if an app is trust-worthy.
I also created an SDK, which developers can use to profit from Root Access. It provides a way to gain access to the filesystem and the registry (and more) from their managed Silverlight application. No need to worry about COM interop and C++ anymore! The package contains a read-me with short instructions. More details and examples will follow soon! Over the last days Rafael Rivera from the Chevron WP7 team has tested the SDK and he is finishing up the first homebrew app that will use my SDK. He is planning to release his Backup-app soon.
I also need to thank some people for making this possible:
- My wife! (for having to put up with me while doing all this hacking!)
- YukiXDA (for helping me with research on policies)
- Justin Angel (for sending me a NOKIA)
- Cees Heim (for supplying an HTC device for testing)
- Rafael Rivera and Chevron WP7 team (for pioneering WP7 Unlocking)
- HD2Owner (for helping me make custom ROM's for testing)
- fiinix (for helping me with research on policies)
- Ultrashot
- xb0xm0d
- AndrewSh
- Ondraster
- Barin
- Football
- Cmonex
- GoodDayToDie
- Jaxbot
- Dennis Wilson
I will update the guides and manuals on www.wp7roottools.com and here on XDA in the next coming days. I need some time to update all of it.
Have fun with Homebrew now!
Heathcliff74

reserved*****

reserved***** (2)

reserved***** (3)

reserved***** (4)

thank you for your hard work

SO AWESOME!!! Thank You SOOOO Much!!!

big thx 4 all your work man!thxthxthx...
Sent from my OMNIA7 using Board Express

Previous Versions
Thanks for your great work. Do we need to uninstall previous versions before installing the latest version? I have .8, how do I install .9?

Great news, thanks a lot! Successfully installed on Focus and Surround, no problems at all.
But I've tried "BT file transfer" and "Opera mini" (after install I've enabled "trusted" status for the apps): both apps not working properly. Should we expect updated versions of these apps (built with your SDK) or it's some another issue?

Fantastic work, Heathcliff74. Oh man, this is going to be awesome.
Suggestion: use one of your reserved posts to compile a list of trusted apps that benefit from policy elevation.
Two that I've found so far (one of mine):
Root Webserver (in my sig) - runs better with Root Tools than ever before.
TouchXperience - gives way more access through WPDM.
Two others that are in development:
LockWidgets - the preview build has some bugs, but it can be run with Root Tools.
XapHandler - the test build has some known issues (can't install or update if the app is already installed) but fresh install works at least some of the time.

Awesome work! I can confirm that the install works perfectly on an LG Quantum.

Big day!
I need some free space in C:/ to make backup.

sensboston said:
Great news, thanks a lot! Successfully installed on Focus and Surround, no problems at all.
But I've tried "BT file transfer" and "Opera mini" (after install I've enabled "trusted" status for the apps): both apps not working properly. Should we expect updated versions of these apps (built with your SDK) or it's some another issue?
Click to expand...
Click to collapse
WP7 Root Tools will give Root Access to Silverlight apps. DFT BT and Opera Mini both use native executables. You can't give the executables root access with WP7 Root Tools (in fact, you only give the launchers Root Access). These apps could possibly be recompiled to run under TaskHost.exe (as all Silverlight apps do), but I'm not sure about the inner workings of the apps. You'd have to ask the developers.
I will investigate this matter. With all the hacks I have now, I should be able to give Root Access to executables too, but that needs more research.
Ciao,
Heathcliff74

@sensboston: Those tools both require additional native binaries. WP7 Root Tools elevates apps, including all the DLLs they load (which is how the SDK works - it's a homebrew DLL, similar to the old Native.dll and company). However, it doesn't work with out-of-process binaries. Opera requires an EXE (which is obviously its own process) and BT File Transfer requires a driver.
In theory, supporting these would be possible. They'd need to be signed, and the certificates added to the Code Integrity store, but that's already possible. However, they'd also need new policies added. The current version of Root Tool only supports modifying the policies for installed TaskHost (Silverlight/XNA, possibly including some native code) apps, not adding policies for other apps.
BTW, although it's very limited, it turns out that Application.GetResourceStream can be used on files outside the app (with sufficient permissions). That means, if you want to write an app that only needs to access existing files at known locations, you don't even need to mess with native code... although the Root Tools SDK will make it quite easy to do such apps anyhow.

Thanks HeatCliff
Thanks man for this wonderfull pice off work

Heathcliff74 Installed on My Omnia 7 Thanks a lot for your Hard Work

JamesAllen said:
Thanks for your great work. Do we need to uninstall previous versions before installing the latest version? I have .8, how do I install .9?
Click to expand...
Click to collapse
You can just reinstall. No need to uninstall. From this new version on (version after 0.9) you better do an "UPDATE". Not all xap-installers support updating. A lot of them will do a full-install-cycle. If you do a full-install-cycle, you'll loose the permissions and you will have to do the 2-phase-install sequence again. If you do an in-place-update, you will keep the permissions and everything keeps working as expected.
Heathcliff74

Damn, doesn't work for me.
Verizon HTC Trophy
OS 7.10.8107.89
Firmware: 2305.13.20110.605
Hardware: 003
Thanks for the work! Hopefully I'll see support later. I probably updated to the HTC v2 drivers at some point.

dreamcaster012 said:
Damn, doesn't work for me.
Verizon HTC Trophy
OS 7.10.8107.89
Firmware: 2305.13.20110.605
Hardware: 003
Thanks for the work! Hopefully I'll see support later. I probably updated to the HTC v2 drivers at some point.
Click to expand...
Click to collapse
Hmm. are you interop unlocked? I'm no expert with HTC's but that versionnumber looks like your drivers are not that new and could possibly be supported. If you are not Interop Unlocked, then read the opening post of my Interop Unlock thread. At the end of that post is a section specifically for Verizon Trophy's
Heathcliff74

Just a Lumia x50 interop unlock idea

Hi there
i have just an idea
I have a Lumia 1520 , Lumia 830 & Lumia 520 thats interop unlocked.
is it possible to alter these backup on a Interop Unlocked phone ( in the registry orso) that it backup more then the standard settings.
For example backup also the portal & devicereg settings from the registry.
Then on a Lumia x50 phone restore that backup ... so it will be interop unlocked by restoring this backup
Will this work ??
I saw a lot of settings in the registry what will be and will not backupped.
Please think this over for a second.
We all want to be that is an option to interop unlock these Lumia x50 phones
I am working with a Lumia 950XL and want to have some changes. I allready send the requests in the feedback hub but i don't think they will pick this up
Thanks for all the support so far
Micheal

I don't think that can be possible though.
There is much better ways to achieve interop unlock.
We can call drivers through IOCTL. I can use CopyFile function from one of nokia drivers. Which runs into system context.

djamol said:
I don't think that can be possible though.
There is much better ways to achieve interop unlock.
We can call drivers through IOCTL. I can use CopyFile function from one of nokia drivers. Which runs into system context.
Click to expand...
Click to collapse
Yeah, but not all drivers can be used to "Interop Unlock". Only drivers with ID_CAP_INTEROPSERVICES capability declared in their manifest can be accessed. By the way, which driver you used to access CopyFile function?

lukjok said:
Yeah, but not all drivers can be used to "Interop Unlock". Only drivers with ID_CAP_INTEROPSERVICES capability declared in their manifest can be accessed. By the way, which driver you used to access CopyFile function?
Click to expand...
Click to collapse
ID_CAP_OEM_CUSTOM has same "TransientObjects" that interop capability had.
You can call with same SecurityDescriptor
That means every Windows 10 Mobile is bydefault interop unlocked

djamol said:
I don't think that can be possible though.
There is much better ways to achieve interop unlock.
We can call drivers through IOCTL. I can use CopyFile function from one of nokia drivers. Which runs into system context.
Click to expand...
Click to collapse
@djamol unfortunately does Nokia drivers were removed from X50 series.
OP even we interop unlock x50 series we have no chance to change registry values because NDTKSVC in x50 series had been changed to a new version and it's limited .
We could restore old NDTKSVC in old series but in x50 this won't work because of lack the old signatures . OS won't trust old signs so if you have a 950XL with Interop unlock + Capabilities unlock you have nothing more than the thing you have right now .
hope you got it but we are working on x50 series, trust me

lukjok said:
Yeah, but not all drivers can be used to "Interop Unlock". Only drivers with ID_CAP_INTEROPSERVICES capability declared in their manifest can be accessed. By the way, which driver you used to access CopyFile function?
Click to expand...
Click to collapse
ngame said:
@djamol unfortunately does Nokia drivers were removed from X50 series.
OP even we interop unlock x50 series we have no chance to change registry values because NDTKSVC in x50 series had been changed to a new version and it's limited .
We could restore old NDTKSVC in old series but in x50 this won't work because of lack the old signatures . OS won't trust old signs so if you have a 950XL with Interop unlock + Capabilities unlock you have nothing more than the thing you have right now .
hope you got it but we are working on x50 series, trust me
Click to expand...
Click to collapse
Lol, It's very funny.
There isn't possible way ? Sideload app as first party developer unlock with eku, then CreateProcessInChamber() ?

djamol said:
Lol, It's very funny.
There isn't possible way ? Sideload app as first party developer unlock with eku, then CreateProcessInChamber() ?
Click to expand...
Click to collapse
Look, chambers are not problems. For example NDTKSVC run as system but it checks witch values you want to change if that change were trusted it will changed if it doesn't it won't be changed . If you have other idea for this let me know somewhere else . Uh I sent you a message there did you read it?

ngame said:
[MENTION=5889633]...
...
...
but we are working on x50 series, trust me
Click to expand...
Click to collapse
Again if you need help or you will try something ..? i have a spare Lumia 950XL to test things out if you want
m

megasounds said:
Again if you need help or you will try something ..? i have a spare Lumia 950XL to test things out if you want
m
Click to expand...
Click to collapse
I have one of these useless phones

ngame said:
I have one of these useless phones
Click to expand...
Click to collapse
Hahahaha... That's strange!

Lumia after factory reset and no updated Extra & Info Interop Unlock

Hi,
I reset my Lumia 535 and updated all apps exclude Extra & Info.
But Interop Tool L 78- 79 and S dont work with the last Registry Provider. Nothing to choice in the Provider option, but they are list under Provider in the tool. I dont can change the registy with them.
Which app work on 10.0.15063.1155 to full unlock?
Thanks

joke19 said:
Hi,
I reset my Lumia 535 and updated all apps exclude Extra & Info.
But Interop Tool L 78- 79 and S dont work with the last Registry Provider. Nothing to choice in the Provider option, but they are list under Provider in the tool. I dont can change the registy with them.
Which app work on 10.0.15063.1155 to full unlock?
Thanks
Click to expand...
Click to collapse
The same issue that I explained few months ago here in another thread, but didn't get an useful answer. I have a Nokia Lumia 920 device, and with many different builds of Win10m, either many builds of WinPhone 8 & 8.1 tried to modify Virtual Memory values, everytime following all kind of guides step by step correctly, but always failed to Interop Unlock my Lumia 920.
I tried to do it following guides that works with Registry Providers and without mentioning them, working with Interop Tool S, with Interop Tool L, with previous versions of them, with Custom PFD, with VcReg, ... with any of possible known tools &/or any version of them, but always failed.
Resuming, I don't know if those tools just works with counted and specific devices where the Lumia 920 is not included, if it is my own Lumia 920 that could have any kind of internal problem that I need to solve first (maybe flashing an specific ROM, unlocking/restoring Bootloader, erasing all and manufacture it again [hahahaha], ...), but I never get success with it.
__
In other way, I use to ask about the possibilities of get a dual boot or change OS on Lumia 920, after read that in few lower models were possible to run Android and install GRUB2 on them (what could give anyone the chance to select between 2 Operative Systems installed), and the typical answer is that "if you want android, just buy an android device" or "work on something like this is not relevant" or "is stupid to try it, because drivers of components and blablabla", and mostly answers with silence (no answer in months/years).
XDA is supossed to be a forum to try to collaborate by developing or helping those who develop or want to implement what others develop. But above all, developing things that could be a big challenge that we want to overcome, because after all, this is what did, does and will continue doing the XDA community the greatest dev community of internet; but with this kind of passive attitude and without any curiosity, (which are reflected in that kind of answers up related), doesn't help at all, and even less in the Windows section, so low and less advanced compared to Android, due to the lack of interest of the most of the great developers of this great family.
Recently I offered myself with my own device in another thread to work in something. Well, let's see in a future if I get any proposal or collaboration. Surely never.
__