Interop Tools - A versatile registry app for all devices, now on Github

Search This thread

gus33000

Senior Member
Aug 9, 2016
452
588
Bordeaux
Is remote registry working, like remote CUSTOM PFD ? Thanks.

It is working, you need to start the app on the phone, tap "This phone" then scroll down the welcoming page, open remote access, type a port number (I personally use 9000), turn remote access on, then open the app on desktop, tap remote device, enter the phone ip and the port you specified and connect, you'll receive a prompt on the phone asking if you want to allow the connection. Note: if you ever lock the phone the connection will be lost.
 
  • Like
Reactions: manstein

manstein

Member
Jan 21, 2012
48
10
I couldn't install the app on PC. I installed independencies and the certificate (both pc and user options). Everytime, I get 0x800B0109.
What to do ?
Edit : got it to install, must manually specify the certificate storage.
Thanks Gus for this incredible tool.
 
Last edited:

hamidparham

Member
Aug 17, 2016
14
1
31
Nishapur
What build are you on (on the phone)?

Thanks for this amazing tool! However I can't turn on any of the unlock options neither. I was able to turn on Restore NDTKSvc but none of the other options worked even after several reboots.
I have the app installed on internal memory of my Lumia 630 which I have used the targeting info of Lumia 636 to update it to build 14393.67.
Btw, I already had version 1.8 installed (which I uninstalled before deploying version 1.9) and so when I tried to deploy the first two dependencies (Microsoft.NET.Native.Framework.Debug.1.3 & Microsoft.NET.Native.Framework.1.3), it said that a higher version is installed. I don't know if that's important or not, just providing details! :rolleyes:
 

gus33000

Senior Member
Aug 9, 2016
452
588
Bordeaux
Thanks for this amazing tool! However I can't turn on any of the unlock options neither. I was able to turn on Restore NDTKSvc but none of the other options worked even after several reboots.
I have the app installed on internal memory of my Lumia 630 which I have used the targeting info of Lumia 636 to update it to build 14393.67.
Btw, I already had version 1.8 installed (which I uninstalled before deploying version 1.9) and so when I tried to deploy the first two dependencies (Microsoft.NET.Native.Framework.Debug.1.3 & Microsoft.NET.Native.Framework.1.3), it said that a higher version is installed. I don't know if that's important or not, just providing details! :rolleyes:

The dependencies shouldn't be the problem, it's odd that you can't use those options even with restore ndtk on. Is restore ndtk staying on after a reboot?

Gus, it's possible to install XAP files with your app?

Not yet.
 

hooddy

Senior Member
Jan 16, 2008
307
55
My L810 won't interop unlocked. Both switch of restore NDTKSvc isnt' workin - it's just wont turn on. Can some one advice me please?
 

hooddy

Senior Member
Jan 16, 2008
307
55
uh that's weird. Was this phone ever able to be interop unlocked with other ways? I have a feeling that it's too old to have NDTK already which would explain why you can't edit anything.

No its dont. Its T-Mobile only phone similar to L820 moar or less. It cant be interoped by WPInternals coz i cant find appropriated hex file. I can just made custompfd for WP8.1 to edit entry for phone model to install W10M or upgrading WP8.1 to WP8.1.2. Thats all (
 
Last edited:

hamidparham

Member
Aug 17, 2016
14
1
31
Nishapur
The dependencies shouldn't be the problem, it's odd that you can't use those options even with restore ndtk on. Is restore ndtk staying on after a reboot?

Yes it does. Other options immediately switch off as I switch them on. I had used version 1.7 when I was still on TH and I couldn't unlock it then neither. Although even Restore NDTKSvc wouldn't work back then and every option I hit would crash the app. The same was the case with version 1.8 after updating to RS. But with this new version I was able to at least Restore NDTKSvc. I also checked that path you mentioned earlier and the value is "c:\windows\system32\ndtksvc.dll".
I tried to unlock with vcReg tool but I get error initializing "check if you have permissions (ID_CAP_INTEROPSERVICES). registry function disabled".
However I think something may have happened because I connected my phone to my pc and it opened to the root path instead of "Data\Users\Public". Also I tried changing a key in the registry which I was getting permission error trying to modify it before, and I didn't get any errors this time, although the value remained unmodified after tapping Write.
This is the first time I'm trying to unlock my phone and it's all very odd indeed!
 
Last edited:

gus33000

Senior Member
Aug 9, 2016
452
588
Bordeaux
Yes it does. Other options immediately switch off as I switch them on. I had used version 1.7 when I was still on TH and I couldn't unlock it then neither. Although even Restore NDTKSvc wouldn't work back then and every option I hit would crash the app. The same was the case with version 1.8 after updating to RS. But with this new version I was able to at least Restore NDTKSvc. I also checked that path you mentioned earlier and the value is "c:\windows\system32\ndtksvc.dll".
I tried to unlock with vcReg tool but I get error initializing "check if you have permissions (ID_CAP_INTEROPSERVICES). registry function disabled".
However I think something may have happened because I connected my phone to my pc and it opened to the root path instead of "Data\Users\Public". Also I tried changing a key in the registry which I was getting permission error trying to modify it before, and I didn't get any errors this time, although the value remained unmodified after tapping Write.
This is the first time I'm trying to unlock my phone and it's all very odd indeed!

The NDTK path is getting created by my app actually if it doesn't exist. And you seeing the root is actually not the result of ndtk working since you can do that without NDTK. Tried re-flashing the phone? Maybe something screwed up with the oem service and it doesn't start up anymore.
 

hamidparham

Member
Aug 17, 2016
14
1
31
Nishapur
The NDTK path is getting created by my app actually if it doesn't exist. And you seeing the root is actually not the result of ndtk working since you can do that without NDTK. Tried re-flashing the phone? Maybe something screwed up with the oem service and it doesn't start up anymore.

I haven't flashed my phone yet, but I guess I have to(?). Is there some way to check the OEM service thing?
 
Last edited:

gus33000

Senior Member
Aug 9, 2016
452
588
Bordeaux
Disclaimer: I'm aware that beta 1.9-pre breaks installation of any app in the store. The only way to fix this is to software reset and never turn on cap unlock on beta 1.9-pre.

This is why this release was labelled as a pre-release anyway. I'm investigating the issue and working on a fix at the moment.
 

gus33000

Senior Member
Aug 9, 2016
452
588
Bordeaux
Does anybody have a store installation issue when applying cap unlock in beta 1.9-pre? If yes does beta 1.8 cap unlock fixes it? and what build are you running atm? I'm having a hard time diagnosing this issue. If you don't have that issue too please report it with the build you're running. Thanks!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 69
    a6Gu3VN.png


    IMPORTANT ANNOUNCEMENT (11/25/2017): https://forum.xda-developers.com/showpost.php?p=74628972&postcount=1071
    IMPORTANT ANNOUNCEMENT (08/02/2020): https://forum.xda-developers.com/showpost.php?p=83193721&postcount=1236

    Source code: https://github.com/gus33000/InteropTools

    OP update is still Work in progress

    READ BEFORE POSTING ANYTHING
    • Interop Tools can't be installed, like with a lot of other apps that uses restricted CAPs, if you CAP unlocked your phone using vcREG, vcREG changes 2 registry values that breaks the whole deployment system since one build of the rs1 development, so please reset your phone, use only vcREG to install an older NDTK if needed, and install Interop Tools (h/t @vcfan see your DMs)
    • Interop Tools doesn't require and will never require any CAP unlock
    • Please read the installation instructions carefully
    • Interop Tools versions older than or equal to Beta 1.8.1 are not supported in any way, please update the app
    • I'm not responsible for any damage made by your device if this ever happens even though I'm really careful each time I'm posting a new version
    • When submitting a bug report, please specify what apps related to Interop/Cap unlock you have installed, if you did anything, some reproduction steps and the phone model you are using, along with if you cap unlocked your device.

    INSTALLATION INSTRUCTIONS
    If you have an IT version older or equal to Beta 1.7 already installed, please uninstall it and reboot your device prior to installing/updating Interop Tools
    1. Download the latest Interop Tools appxbundle for your device architecture and its dependencies
    2. Extract both zips, and extract the certificate file if you're installing Interop Tools on a desktop device
    3. If you're on a Desktop device, double click the certificate file, select Local Machine as the installation location, press next, select place the certificate into the following certificate store, and pick trusted peoples, then press ok, and next.
    4. Install Interop Tools dependencies like any regular appx, by opening up the Device portal for your device, going into the application section, click on browser for the app package, select the dependency appx, and then press install, do that for each dependency
    5. The install Interop Tools main appxbundle by pressing browser, pick it, then press install.

    ENABLE SYSTEM REGISTRY ACCESS INSTRUCTIONS
    For x50+ lumia devices by Microsoft

    1. Download and install vcREG and proceed to install the older NDTK version as instructed in the vcREG thread, for support about this whole process, please see the vcREG thread in the same forum section
    2. Don't do any CAP unlock, otherwise Interop Tools might not install properly
    3. Install Interop Tools if you never installed it like instructed on this post

    For other lumia devices by Microsoft

    1. Go to the Interop Unlock section of Interop Tools
    2. If restore NDTK isn't on, turn it on, and reboot your device

    For all other OEM devices

    1. Download the NDTK packages and the WPAK utilities from here: http://forum.xda-developers.com/attachment.php?attachmentid=3860782&d=1472659473 http://forum.xda-developers.com/attachment.php?attachmentid=3860780&d=1472659433
    2. Go to the Interop Unlock section of Interop Tools, and tap the button that says "Enable installing NDTK on any device"
    3. Put the two NDTK cabs in one empty folder on your PC
    4. Open a command prompt as administrator and make sure you're in the directory where the iutool executable is located from the WP(AK) zip
    5. run "iutool -V -p "<fulllocationwherethetwondtkpackagesarestored>" with your phone connected into the PC
    6. if iutool throws an error, please unplug your device, go to the control panel, devices and printer, select your phone, should be ghosted, click on uninstall device, and then replug the device and wait for it to reinstall. If you still have issues, run GETDULOGS from the same CMD prompt, and post the cab you get along with a message in this thread
    7. When the installation is finished, open Interop Tools, go to the Interop Unlock section, and tap restore the original manufacturer info button.


    You can find a Q&A in the post below the OP.

    FEATURES

    This app allows you to:
    • Edit the registry through the registry editor
    • Browse the registry hives through the registry browser
    • Find sepecific registry values/keys through the search page
    • Apply tweaks to your device
    • Interop and Cap unlock your device
    • Access device information
    • Remotely edit the registry through the built-in desktop app
    • Manage Applications
    • Manage Certificates
    • Perform standard registry operations such as deleting, renaming, and copying details
    • Built-In Command Prompt inside the app (coming in pre-1.9)
    • Manage SSH accounts and more (coming in pre-1.9)
    • and more.

    This app includes a lot of neat features which makes a better experience while editing the registry such as for example, the key suggestion bar in the registry editor, or the jump to button in the browser.

    STATE OF THE APP

    The app is still in development and has some rough edges. I would appreciate if you could report bugs about it, but before make sure you read the Q&A.
    Currently the app has limited support for the registry for all devices running at least Windows 10 Mobile build 10240 by default.
    Some specific devices have extra support out of the box, please read the list inside the spoiler below.

    Lumia handsets (including other handsets with the ndtk service installed):
    SYSTEM level access for editing and reading the following registry values and hives:

    HKLM
    HKCU
    HKCR
    HKU
    HKCC

    REG_DWORD
    REG_QWORD
    REG_SZ
    REG_MULTI_SZ
    REG_EXPAND_SZ
    REG_BINARY


    SYSTEM level access for LG and Samsung devices (untested, please report some feedback about it):

    HKLM
    REG_DWORD
    REG_SZ


    You can however enable more access privileges by following the instructions above, about enabling system registry access.



    LINKS

    See the second post for current pre-releases
    Main Mega folder for download links and older versions: http://bit.ly/InteropTools See the current pre-releases
    App Twitter account (for direct communication if I'm not available directly): http://twitter.com/InteropTools
    My Personal Twitter account: http://twitter.com/gus33000

    SCREENSHOTS

    zltkFtw.png
    rGlm2aX.png
    zwLQAJU.png
    bCbsRRg.png
    EDP4LT3.png
    1tDDpEt.png
    QaiBLah.png
    cwpsErc.png
    cjBnYlc.png
    IYEBYo4.png
    H2UiBrt.png
    V8to4uy.png
    M4JYRwn.png
    TGzJ267.png
    PikCFwS.png
    29
    It's been a long time since I made an announcement on here, I originally wanted to release a new build yesterday for all of you but some big things happened and before releasing it I need to announce a few things:

    Recently I got way more busy than I really imagined, and as a result I didn't really find much more time to continue working on the app. So I've been trying to look for somebody to help developing the app with me, but I also didn't find time to do this. As a result many of my plans for the app never came to light yet, and I wish I could also refactor some key areas of the application as well. Yesterday I got a notification from Microsoft saying they banned the application from the store, because of the privacy link going down (something they don't usually ban for but I imagine they were waiting for that little thing to ban the app), as I'm speaking the app is in the process of getting pulled. Sure it's not a big deal for most of you, but it really affects me a bit and on top of this, the store app while useless for now for most of you, had really big plans going for it that I never really talked about (those plans are the entire reason it exists in the first place). So with no time and MS roasting me it's hard to find motivation to continue working on the app. At first I was also very happy to provide support for it, especially here on XDA, and on twitter as well, which also managed to find new friends a year ago. But as you probably noticed I don't post anymore on here (I wish I could), work is slowly eating my time, and I'm sad about it.

    But to be clear, I'm not going to let the application die, I found somebody that was gladly nice enough to propose his help for the development of the app, I don't want to say who it is yet but he is awesome and I have been knowing him since a long time. I'm not going away either, when I'll have time I'll still try to continue working on the app. But I wanted to say, I will probably not be releasing builds all the time as I used to in the early days, and I would also like to thank every single one of you here that gladly helped others, without even me asking them, essentially doing what I should have been doing. It means a lot more for me than just helping people.

    That being said, a new application listing is getting created in the store and I'm fighting with MS to appeal the decision (which I'm allowed to do but it may take some time and may not even be possible to bring the store preview listing back). On top of this, somebody a long time ago before me reserved the "Interop Tools" application and pfn name to the store, which I'm not too happy about it, but if I had a guess it's probably Microsoft playing with me since the beginning.

    Back to topic, here's a new build of Interop Tools (only legacy, no store version obviously....), same instructions as usual, I'll just note one important bug fix I made which will probably make all of you happy:

    The app will not crash and exit anymore
    Yes you heard it right, when a crash will happen the app will just display an error popup and will not close.
    Along with this some important bug fixes were made but I don't have much time to detail all of them.

    Download: https://mega.nz/#!zBthTSqJ!H9829o_cTn760UiV_vQAIpTImQLel2ajszQsjUsRvGA

    To all of you, once again, thank you, I didn't realise until yesterday the people around the app, it's been amazing since last year to have seen the app grow that much and people around it helping each other, have a good weekend people, and don't brick your devices too much.

    every setback has a major comeback
    21
    THIS VERSION IS OUTDATED. PLEASE USE INTEROP TOOLS L IF YOU DON'T WANT TO USE EXTENSIONS. YOU CAN FIND BUILD 2.0.7x.0 HERE: https://forum.xda-developers.com/showpost.php?p=73608163&postcount=1006

    Original post follows as below. Do not ask for support for this version, it's deprecated and nobody should use it.

    Releasing Interop Tools Release Candidate 3

    Changelog: http://insidewindows.net/2017/02/12/interop-tools-release-candidate-3-change-log

    Sorry for the little delay, but the lack of electricity for one whole week and being busy didn't help at all to get a proper release faster. Anyway, have fun with the changes! And as always... Removed SOON again.
    19
    Sorry for the lack of updates lately folks, but got pretty busy with life IRL, and just started becoming free again, pushed a new status update about Interop Tools on insidewindows here which talks about why that posts exists and what to expect from the new upcoming Interop Tools S release. Have a nice week, oh and I'll try to reply to everything next week :)

    Interop Tools L: https://mega.nz/#!XQNnCbCS!ePnfB08AldVAtkeeNapOaVWxq9bAvR1noCq7hD_Vv9w

    Update 6/24/2017 10:56 AM UTC+1: A new build of Interop Tools L and extensions have been released to fix a big issue. Please update to the new version of both extensions and the app, Sorry for the inconvenience.
    17
    And it happened, welcome to the first preview of ITS :)

    Link: https://www.microsoft.com/store/apps/9ntgwlc0d3cs
    Important release notes: http://insidewindows.net/2017/04/02...the-store-its-2-0-technical-preview-build-18/

    Current provider extensions (reg NDTK and WinRT): https://mega.nz/#F!yUUB1LCb!N_s6HHYgI2sw1IdY258w_w

    Have fun, and keep in mind it's still a preview :)