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!![]()
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?
SOFTWARE\OEM\Nokia\NokiaSvcHost\Plugins\NsgExtA\NdtkSvc\Path
What's the value ofHTML:SOFTWARE\OEM\Nokia\NokiaSvcHost\Plugins\NsgExtA\NdtkSvc\Path
SOFTWARE\OEM\Nokia\NokiaSvcHost\Plugins\NsgExtA\
There is onlybranchCode:SOFTWARE\OEM\Nokia\NokiaSvcHost\Plugins\NsgExtA\
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.
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!
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?