Develop Bugs

[Q] Passing Chevron WP7 from NoDo to Mango on Samsung Focus

I've been following on the Mango upgrades and whatnot, since I just recently upgraded my Samsung Focus to Mango. However, I have yet to see a way to pass ChevronWP7 to a Samsung WP7. I know with LGs you can use the MFG regedit, and with HTCs you can use this xml method found here:
http://forum.xda-developers.com/showthread.php?t=1101344
Is anyone anywhere working on a way to pass ChevronWP7 from NoDo to Mango on a Samsung device? I just want some confirmation, because I'd love to use Mango to it's fullest extent. Thanks guys!

VenezuelaDan said:
I've been following on the Mango upgrades and whatnot, since I just recently upgraded my Samsung Focus to Mango. However, I have yet to see a way to pass ChevronWP7 to a Samsung WP7. I know with LGs you can use the MFG regedit, and with HTCs you can use this xml method found here:
http://forum.xda-developers.com/showthread.php?t=1101344
Is anyone anywhere working on a way to pass ChevronWP7 from NoDo to Mango on a Samsung device? I just want some confirmation, because I'd love to use Mango to it's fullest extent. Thanks guys!
Click to expand...
Click to collapse
can you please provide us with a guide or the steps you used to upgrade your focus
i checked several threads here, but was unable to upgrade & kept getting an error message: " no devices were found"

I made this post here: http://forum.xda-developers.com/showpost.php?p=15329491&postcount=5
Your device needs to already be dev unlocked and in NODO!!
Someone else has confirmed that you need diagnosis version is 1122.
1. Make a backup of your device. You can use my app for that if you wish: http://forum.xda-developers.com/showthread.php?t=1103011
1.1 - Make a backup
1.2 - Make a backup
1.3 - Make a backup!!!!
Get the point? you CAN NOT get the official Mango update when its released without reverting to NODO so MAKE A DAMN BACKUP! I personally have 4 backups just in case!
2. I installed this unlock.xml: http://forum.xda-developers.com/showpost.php?p=15316160&postcount=9
3. Install WP7 Root Toosl by Heathcliff .5 alpha from his thread: http://forum.xda-developers.com/showthread.php?t=1021135
4. Load the root tools and using the explorer create a directory called provxml in the root of the drive if it doesnt already exist.
5. Using the root tools copy unlock.xml file from: Applications\Install\D19A80F2-1717..... (you may have to browse folders in that path) to the provxml folder at the root of the device. (I apologize but I don't know the exact path I believe it starts in the root but I would have to revert to nodo to know for sure as the root tools don't work in mango.
6. *OPTIONAL TEST* Once that file is there you can test it to be sure it works like I did by changing one of the unlock reg keys and applying the XML to confirm it changes back. I used the root tools registry editor part to browse to: "HKLM\Software\Microsoft\DeviceReg" I changed the value "PortalUrlProd" by adding random text as it should be clear/empty/null. Then I applied the xml by going to the diagnosis tools from my shortcut or by going to the phone app and then the keypad and typing: ##634#. Once in Diagnosis enter: *#9908# to get to the GPRS profiles. Tap the dropdown and you should see unlock in your list. Select unlock and then save at the bottom. It only takes a second and says success in the window below the dropdown. Now exit diagnosis and use the root tools again to confirm the registry value you set before is now cleared/empty/null. If that works you can proceed with confidence.
7. Perform the 2 step mango update from this link: http://windowsphonehacker.com/articles/get_the_mango_update_now._without_being_a_developer.-06-30-11
8. Once updated and in mango apply the xml by: going to the diagnosis tools from a shortcut or by going to the phone app and then the keypad and typing: ##634#. Once in Diagnosis enter: *#9908# to get to the GPRS profiles. Tap the dropdown and you should see unlock in your list. Select unlock and then save at the bottom. It only takes a second and says success in the window below the dropdown. Again diagnosis version 1122 is needed for this to work.
One word of warning. I had to reconfigure the APN to get network to work but I still couldnt receive MMS. So in the end I read that to get it set up you have to reset the phone and let the configuration steps set up network profile. I wasnt about to do that so I called AT&T and said I was going to another country and needed my unlock code to put a sim card in from there and they gave it to me. They said I needed another carrier SIM to input it. Instead I went to diagnosis and entered: #7465625*638*# That brought me to the Network Lock screen. I made sure disabled was checked and entered the unlock code they gave me on the phone in the NCK section and tapped execute. That unlocked my phone which let me use the samsung network profile tool available form the samsung marketplace (only on phone) to select the ATT (not AT&T) profile. Actually I toggled to AT&T then back to ATT and everything worked!

Yup.... What he said!!!
Mango on my Focus is awesome. I didn't do the unlock though because that tutorial came after I upgraded to mango. Now I'm too scared to do it again. And frankly, the whole process takes forever. In the end, it's worth it!!! I just need a working registry editor now because I'm back to that stupid 16-bit colors!!! I hate it.

It's not necessary to make a back-up if you just don't care about the data. Simply install an OEM ROM from the carrier of your choice on the Samsung Focus. I have several phones and just figured *meh* who cares - I'll reinstall the apps I want and just lose my game saves (please let cloud game saves come to WP7 soon!!)
This of course doesn't address the unlock issue. My hope is soon we get a non-branded ROM for the Samsung Focus sooner rather than later so I can finally resolve the MMS issues.
As far as unlocking I have given up for the time being. May just buy a Chevron unlock...

I'm not having MMS issues on mine. Just the damn 16-bit color limit. All the gradients are chopped. I want the 24-bit back. It's just a small registry hack! Why can't samsung or AT&T update it.

pdangcil said:
I'm not having MMS issues on mine. Just the damn 16-bit color limit. All the gradients are chopped. I want the 24-bit back. It's just a small registry hack! Why can't samsung or AT&T update it.
Click to expand...
Click to collapse
Odd I havent tested it with the diag screen but I still occassionaly get the "Red screen" on boot up which is a symptom of the color change hack.

pdangcil said:
Yup.... What he said!!!
Mango on my Focus is awesome. I didn't do the unlock though because that tutorial came after I upgraded to mango. Now I'm too scared to do it again. And frankly, the whole process takes forever. In the end, it's worth it!!! I just need a working registry editor now because I'm back to that stupid 16-bit colors!!! I hate it.
Click to expand...
Click to collapse
Too scared? Bah! I have done it 4 times with no problems and I have 4 backups of my phone pre-mango so whats to be scared of?

Get At&T settings back the easy way
Instead of going through the pain with At&T this will fix the AT&T settings after you are done wit the unlock. from the diagnosis app
g_AutoSimSetting : 40*047#3, *#94765#

sandrobber said:
Instead of going through the pain with At&T this will fix the AT&T settings after you are done wit the unlock. from the diagnosis app
g_AutoSimSetting : 40*047#3, *#94765#
Click to expand...
Click to collapse
Interesting... so it disables then re-enables the auto-sim setting? Should we do the reboot in the middle that it asks for?

hx4700 Killer said:
I made this post here: http://forum.xda-developers.com/showpost.php?p=15329491&postcount=5
Your device needs to already be dev unlocked and in NODO!!
Also I don't know if it is required but my diagnosis version is 1122.
1. Make a backup of your device. You can use my app for that if you wish: http://forum.xda-developers.com/showthread.php?t=1103011
1.1 - Make a backup
1.2 - Make a backup
1.3 - Make a backup!!!!
Get the point? you CAN NOT get the official Mango update when its released without reverting to NODO so MAKE A DAMN BACKUP! I personally have 4 backups just in case!
2. I installed this unlock.xml: http://forum.xda-developers.com/showpost.php?p=15316160&postcount=9
3. Install WP7 Root Toosl by Heathcliff .5 alpha from his thread: http://forum.xda-developers.com/showthread.php?t=1021135
4. Load the root tools and using the explorer create a directory called provxml in the root of the drive if it doesnt already exist.
5. Using the root tools copy unlock.xml file from: Applications\Install\D19A80F2-1717..... (you may have to browse folders in that path) to the provxml folder at the root of the device. (I apologize but I don't know the exact path I believe it starts in the root but I would have to revert to nodo to know for sure as the root tools don't work in mango.
6. *OPTIONAL TEST* Once that file is there you can test it to be sure it works like I did by changing one of the unlock reg keys and applying the XML to confirm it changes back. I used the root tools registry editor part to browse to: "HKLM\Software\Microsoft\DeviceReg" I changed the value "PortalUrlProd" by adding random text as it should be clear/empty/null. Then I applied the xml by going to the diagnosis tools from my shortcut or by going to the phone app and then the keypad and typing: ##634#. Once in Diagnosis enter: *#9908# to get to the GPRS profiles. Tap the dropdown and you should see unlock in your list. Select unlock and then save at the bottom. It only takes a second and says success in the window below the dropdown. Now exit diagnosis and use the root tools again to confirm the registry value you set before is now cleared/empty/null. If that works you can proceed with confidence.
7. Perform the 2 step mango update from this link: http://windowsphonehacker.com/articles/get_the_mango_update_now._without_being_a_developer.-06-30-11
8. Once updated and in mango apply the xml by: going to the diagnosis tools from a shortcut or by going to the phone app and then the keypad and typing: ##634#. Once in Diagnosis enter: *#9908# to get to the GPRS profiles. Tap the dropdown and you should see unlock in your list. Select unlock and then save at the bottom. It only takes a second and says success in the window below the dropdown. I had diagnosis version 1122 so I don't know if that is needed for this to work or not.
One word of warning. I had to reconfigure the APN to get network to work but I still couldnt receive MMS. So in the end I read that to get it set up you have to reset the phone and let the configuration steps set up network profile. I wasnt about to do that so I called AT&T and said I was going to another country and needed my unlock code to put a sim card in from there and they gave it to me. They said I needed another carrier SIM to input it. Instead I went to diagnosis and entered: #7465625*638*# That brought me to the Network Lock screen. I made sure disabled was checked and entered the unlock code they gave me on the phone in the NCK section and tapped execute. That unlocked my phone which let me use the samsung network profile tool available form the samsung marketplace (only on phone) to select the ATT (not AT&T) profile. Actually I toggled to AT&T then back to ATT and everything worked!
Click to expand...
Click to collapse
Thank you very much
worked wondefully
3G data internet was not working at first but works great after manually choosing ATT from network profile app

MMS issues don't exist anymore if you install the Samsung Tools XAP. Even if you upgrade to Mango after, some remnants remain from the unlock, and one of those is the expanded MMS settings this tool gives (my phone is locked after mango because I didnt do this hack, but my MMS, 3G, and custom live tile colors still work....)

hx4700 Killer said:
I made this post here: http://forum.xda-developers.com/showpost.php?p=15329491&postcount=5
Your device needs to already be dev unlocked and in NODO!!
Also I don't know if it is required but my diagnosis version is 1122.
1. Make a backup of your device. You can use my app for that if you wish: http://forum.xda-developers.com/showthread.php?t=1103011
1.1 - Make a backup
1.2 - Make a backup
1.3 - Make a backup!!!!
Get the point? you CAN NOT get the official Mango update when its released without reverting to NODO so MAKE A DAMN BACKUP! I personally have 4 backups just in case!
2. I installed this unlock.xml: http://forum.xda-developers.com/showpost.php?p=15316160&postcount=9
3. Install WP7 Root Toosl by Heathcliff .5 alpha from his thread: http://forum.xda-developers.com/showthread.php?t=1021135
4. Load the root tools and using the explorer create a directory called provxml in the root of the drive if it doesnt already exist.
5. Using the root tools copy unlock.xml file from: Applications\Install\D19A80F2-1717..... (you may have to browse folders in that path) to the provxml folder at the root of the device. (I apologize but I don't know the exact path I believe it starts in the root but I would have to revert to nodo to know for sure as the root tools don't work in mango.
6. *OPTIONAL TEST* Once that file is there you can test it to be sure it works like I did by changing one of the unlock reg keys and applying the XML to confirm it changes back. I used the root tools registry editor part to browse to: "HKLM\Software\Microsoft\DeviceReg" I changed the value "PortalUrlProd" by adding random text as it should be clear/empty/null. Then I applied the xml by going to the diagnosis tools from my shortcut or by going to the phone app and then the keypad and typing: ##634#. Once in Diagnosis enter: *#9908# to get to the GPRS profiles. Tap the dropdown and you should see unlock in your list. Select unlock and then save at the bottom. It only takes a second and says success in the window below the dropdown. Now exit diagnosis and use the root tools again to confirm the registry value you set before is now cleared/empty/null. If that works you can proceed with confidence.
7. Perform the 2 step mango update from this link: http://windowsphonehacker.com/articles/get_the_mango_update_now._without_being_a_developer.-06-30-11
8. Once updated and in mango apply the xml by: going to the diagnosis tools from a shortcut or by going to the phone app and then the keypad and typing: ##634#. Once in Diagnosis enter: *#9908# to get to the GPRS profiles. Tap the dropdown and you should see unlock in your list. Select unlock and then save at the bottom. It only takes a second and says success in the window below the dropdown. I had diagnosis version 1122 so I don't know if that is needed for this to work or not.
One word of warning. I had to reconfigure the APN to get network to work but I still couldnt receive MMS. So in the end I read that to get it set up you have to reset the phone and let the configuration steps set up network profile. I wasnt about to do that so I called AT&T and said I was going to another country and needed my unlock code to put a sim card in from there and they gave it to me. They said I needed another carrier SIM to input it. Instead I went to diagnosis and entered: #7465625*638*# That brought me to the Network Lock screen. I made sure disabled was checked and entered the unlock code they gave me on the phone in the NCK section and tapped execute. That unlocked my phone which let me use the samsung network profile tool available form the samsung marketplace (only on phone) to select the ATT (not AT&T) profile. Actually I toggled to AT&T then back to ATT and everything worked!
Click to expand...
Click to collapse
One important observation:
Diagnose v922 does NOT see Unlock.xml , thus you can't apply the GPRS profile. You need to update to v1122.
To get Diagnose v1122, you need to re-brand your phone back to the original carrier. In my case it was:
HKLM\System\Platform\DeviceTargetingInfo\MobileOperator = "ATT-US"
After that, I got a Samsung update (updated radio+sw) in Zune, and with it I also got the diagnose v1122.
If you still get Diagnose v922 after the "Samsung Update", then delete Diagnose app and run *#634# and Diagnose will be updated.

Another word of warning.
This is a BETA Mango update.
I just tried it and my Focus and after the update it got stuck at Samsung logo. However, it can be fixed, read my post here.
Might have to do with SD card I use (16 GB Class 2) but I doubt it as I didn't have any issues in over 5 months, updates 7004 to 7392.

Upgraded a Focus once and then got locked out. Updated again and when I do the Diagnosis then *#9908# and select unlock, it says Loading GPRS Profile for unlockProvision and then nothing. Same happened with the last upgrade so now I worried that I'm only a little time away from getting locked again.

Deano69 said:
Upgraded a Focus once and then got locked out. Updated again and when I do the Diagnosis then *#9908# and select unlock, it says Loading GPRS Profile for unlockProvision and then nothing. Same happened with the last upgrade so now I worried that I'm only a little time away from getting locked again.
Click to expand...
Click to collapse
I think it worked. I did the extra step 6, and I've tested with the "PortalUrlProd" value before the actual update and it was reset. Same as you, I got the "Loading GPRS profile..." message and nothing else. But it worked.

EnderPsp said:
Another word of warning.
This is a BETA Mango update.
I just tried it and my Focus and after the update it got stuck at Samsung logo. However, it can be fixed, read my post here.
Might have to do with SD card I use (16 GB Class 2) but I doubt it as I didn't have any issues in over 5 months, updates 7004 to 7392.
Click to expand...
Click to collapse
I have a 16GB Sandisk Class 2 memory card in my focus and it works fine. I had read that diag 1122 *might* be needed but wasnt sure until now

hx4700 Killer said:
I have a 16GB Sandisk Class 2 memory card in my focus and it works fine. I had read that diag 1122 *might* be needed but wasnt sure until now
Click to expand...
Click to collapse
Btw, can someone make a xap with Diagnose 1122, please? Rogers firmware doesn't seem to get the "Samsung Update" that installs v1122, and I'm stuck with default v927... Or give any pointers how to get the new Diagnose
I'm pretty sure that if I flash the AT&T fw I'll get v1122, but I like Rogers rom better (mine is originally an AT&T Focus).

EnderPsp said:
Btw, can someone make a xap with Diagnose 1122, please? Rogers firmware doesn't seem to get the "Samsung Update" that installs v1122, and I'm stuck with default v927... Or give any pointers how to get the new Diagnose
I'm pretty sure that if I flash the AT&T fw I'll get v1122, but I like Rogers rom better (mine is originally an AT&T Focus).
Click to expand...
Click to collapse
I got it somewhere else on here, didnt need it though:

Is there any way to get the updated diagnosis app on Omnia 7? (Optus Australia, build 7392)
That XAP won't allow me to sideload for some reason, and even if it did, that won't help me after I get into Mango.

[GUIDE] INTEROP-UNLOCK - NEW unlocks for ALL SAMSUNG WP7 devices!!

NEW: I created new unlocks for (almost) all Samsung WP7 devices, including 2nd generation devices like Focus S and Omnia W! More info here. Guides will be updated as soon as possible!
In Mango there is a new type of lock: INTEROP-LOCK
Normal WP7 apps are Silverlight or XNA apps. They run managed code. Some apps also use native code (C++), but Microsoft restricts the use of native code to certain selected partners, because native code is more sensitive to errors and need higher care. But there are no real boundaries for running native code on WP7 devices, as I explained here. If your device is AppHub- or ChevronWP7-unlocked, you can run the apps with native code. For example the Version and Language tool from this thread uses native code, but it can run on normal unlocked devices. But there are also apps that need access to drivers on your phone. These apps need the Interop Services capability. This capability is only allowed to software from Microsoft and from OEM's. But many homebrew apps need this capability too, to get higher privileges for tweaking your device. The new Interop Lock means that this capability is locked down. So, even when you have a legit AppHub-unlock or ChevronWP7 Labs unlock, you still can't side-load apps that need higher privileges to run. For example WP7 Root Tools needs this capability to run. But when your device is INTEROP-LOCKED it will show error 0x81030120 when you try to deploy it to your device.
Contable and Marvin_S did research on it and found that the registry setting MaxUnsignedApp is responsible for the INTEROP-LOCK. I did more research and I identified the code that is responsible for this check. 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.
So I wanted to allow people with MANGO shipped on their device and using a legit developer unlock, to use WP7 Root Tools and other MANGO-compatible homebrew apps.
I have developed a method to do this. I have a Samsung Omnia 7 and it works on my device. It should also work on Samsung Focus. ATLien68 brought to my attention that it is also possible for LG devices to do an Interop Unlock on Mango. So I created a guide for LG too.
This only works on devices that already have a developer-unlock!
DISCLAIMER
I will not take any responsibility for any damages caused directly or indirectly from using the software-package or the instructions. Read the instructions thoroughly and proceed carefully!
BACKUP
You may want to make a backup of your device in case something goes wrong. This is what I do to make a backup:
1. Download hx4700 Killer's WP7 Backup version 1.6 from this thread. Note that I use version 1.6, not 1.8.
2. Download this archive. It is from xboxmod's WP7 Update Cab Sender thread.
3. Use Zune 4.8 final (4.8.2345.0).
4. Setup-UpdateWP 4.8 beta 3 from the archive.
5. Extract the "Tools" folder from the archive.
6. Setup the Backup tool to reference Zune.exe and the UpdateWP.exe in the extracted Tools-folder.
7. Create your backup. The backup app will allow you to archive any previous backup. Your phone will restart and go in Download-mode. When the backup is finished, the app will tell you to disconnect. Even though your phone says you still can't disconnect, you can safely disconnect the phone and it will restart.
SAMSUNG
WARNING!! The new Samsung Omnia 7 KK2 update will prevent the use of Interop Unlock and WindowBreak! This Samsung Firmware update is accompanied with the 7.10.8107.79 if you update with Zune. Other Samsung devices are probably affected too, but I don't know if the update code for those device is KK2 too. If you are already unlocked, this update will not relock your device. If you want to keep the possibility of Interop Unlock open, then use the method described in this thread to update to 7.10.8107.79 without updating to Samsung KK2!
1. Download the software package Interop Unlock by Heathcliff74 v2.xap.
2. Connect your phone to your desktop computer, running Zune.
3. Check for updates and let all pending updates install.
4. Uninstall the Samsung Diagnosis app.
5. Dial ##634# to install the latest Samsung Diagnosis app.
6. Use any Windows Phone App Deployment tool to install Interop Unlock by Heathcliff74 v2.xap.
7. Run the Samsung Diagnosis app. You should see version 1027, 1122 or 0103 at the top. The version is the compile-date without year. So version 0103 is actually newer than 1122. Versions from before 2010/10/27 do not seem to work. If you have such an old version of the Diagnosis App you need to run the latest Samsung Update (Mango Drivers) from Zune or update manually as described here. After the update you need to perform step 4 and 5 again.
8. In the Diagnosis app dial: *#9908#
9. Select "Heathcliff74 Interop Unlock"
10. Tap "Save", tap "Close" and exit the Diagnosis app. You are now unlocked, but your 3G settings are screwed (side-effect).
11. To repair your 3G settings use one of these six options:
---- 11.1. NEW: This option only works on 1st generation Samsungs. Download "Samsung Repair 3G by Heathcliff74.xap" and run it on your phone. It should work immediately.
---- 11.2. Use the Diagnosis app (thanks to Vintage144 for the tip).
-------- 11.2.1. Open up the Diagnosis app.
-------- 11.2.2. Dial this to enable autoconfigure sim setting: *#94765# (or dial 40*047#3, it's the same - more diagnosis codes here)
-------- 11.2.3. It will ask you to restart the device. Confirm that.
---- 11.3. If your device is not locked to a specific operator, you can use the Samsung Network Profile app (for 1st generation) or Wireless Manager (for 2nd generation)
-------- 11.3.1. Uninstall the Samsung Network Profile / Wireless Manager app.
-------- 11.3.2. Download and install the latest version of the Samsung Network Profile / Wireless Manager app from the Marketplace.
-------- 11.3.3. Open the Samsung Network Profile / Wireless Manager app.
-------- 11.3.4. Select a different Network Operator.
-------- 11.3.5. Now Select your own Network Operator again.
-------- 11.3.6. Exit the Network Profile / Wireless Manager app.
---- 11.4. Use lyriquidperfection's Samsung Tools (probably only works on 1st generation Samsungs).
-------- 11.4.1 Download the Samsung Tools here.
-------- 11.4.2. Deploy the tools to your phone (which is now possible due to Interop-Unlock)
-------- 11.4.3. Start "Samsung Tools"
-------- 11.4.4. Select "Run ADC"
-------- 11.4.5. Tap "Reboot"
---- 11.4. Use WP7 Root Tools for manual repair (I will add an option to repair 3G in the next version, currently only works on 1st generation Samsungs).
-------- 11.5.1. Download WP7 Root Tools here.
-------- 11.5.2. Deploy WP7 Root Tools to your phone (which is now possible due to Interop-Unlock).
-------- 11.5.3. Open WP7 Root Tools.
-------- 11.5.4. In the registry editor navigate to Local Machine\System\AutoDataconfig.
-------- 11.5.5. Set value ConfigurationStatus to 0 and set value RunADC to 1.
-------- 11.5.6. Restart your phone.
---- 11.6. Use TouchXperience Advanced Config Tool 1.4 (thanks to Ludovic B. for the tip, probably only works on 1st generation Samsungs).
-------- 11.6.1. Download Advanced Config Tool here.
-------- 11.6.2. Deploy Advanced Config Tool to your phone (which is now possible due to Interop-Unlock).
-------- 11.6.3. Open Advanced Config Tool.
-------- 11.6.4. Go to "Tweaks" and scroll down.
-------- 11.6.5. Check "Run Auto Data Config".
-------- 11.6.6. Scroll down and tap "Reboot phone".
Resolve Samsung connection problems
Thanks for this info to lulede!!
A lot of Samsung owners have complained here about connection problems. They blamed Interop Unlock, but apparently this has more to do with enabling "Internet Connection Sharing" than with "Interop Unlock". You should be able to recover the connection, apply this:
1. Start Diagnosis App> *#32489#
2. Tap "Back" 2 times to go back to Phone Control
3. Choose: [7] Network Control
4. Choose: [1] GFC
5. Choose: [3] Setting Cancellation
Wait for it to say success, then reboot.
LG
1. Install the MFG app by dialing: ##634#
2. Open the MFG app. The password is: appmfg#*#
3. Go to Engineer Menu -> Other Settings -> Edit Registry
4. Set your ROOT PATH to "HKEY_LOCAL_MACHINE"
5. Set your input path to "\Comm\Security\LVMod"
6. Set your input key to "DeveloperUnlockState" and set to DWORD.
7. Leave input data box empty and tap "SET".
8. The output should be 0.
9. Now enter "1" in the inputbox and tap "SET".
10. The output should be 1.
11. Set your input path to "\Software\Microsoft\DeviceReg"
12. Set your input key to "PortalUrlProd" and set to DWORD.
13. Clear the input data box and hit "SET".
14. Output result should be "0".
15. Set your input key to "PortalUrlInt" and set to DWORD.
13. Clear the input data box and hit "SET".
14. Output result should be "0".
15. Set your input path to "\Software\Microsoft\DeviceReg\Install"
16. Set your input key to "MaxUnsignedApp" and set to DWORD.
17. Clear the input data box and hit "SET".
18. The output should be 0.
19. Now enter "2147483647" in the inputbox and tap "SET".
20. Output result should be "2147483647".
HTC
I didn't do this hack for HTC's all by myself. This hack is a joint collaboration of XDA members. A valuable part of this hack was done by Kounadisk and GoodDayToDie. Thanks to them!
Also thanks to CeesHeim for arranging a hand-on HTC device for me to test with.
This hack need the HTC Connection Setup app. HTC Arrive can't run the HTC Connection Setup app. Therefore this hack will not work on HTC Arrive. Verizon Wireless Trophy users should follow slightly different steps. Scroll down for instructions that are specifically meant for Verizon Wireless Trophy.
Developer unlock can be either AppHub or Chevron Labs.
Important note: From what I understand, HTC has released *two* OEM updates after Mango. The first one was released together with Mango and included the first Mango drivers from HTC. I will call those the HTC Mango Drivers v1. The second one is being rolled out now and is by other people referred to as the "tethering update". This update also contains updated drivers. I will call those the HTC Mango Drivers v2. If you have a 1st generation HTC device, you may or may not have installed the HTC Mango Drivers v1 or v2. If you are on Mango with Interop Lock, you may need this hack to perform Interop Unlock. The HTC Mango drivers have extra protection which will reject the configuration settings for Interop Unlock. The current hack for HTC defeats the extra protection in HTC Mango Drivers v1. But in HTC Mango Drivers v2 there is an even more advanced protection, which is a breaking change that causes the Interop Unlock to fail. The second generation HTC devices (HTC Radar / HTC Titan) come with the HTC Mango Drivers v2 preloaded. So currently only First generation HTC Mango devices can only be Interop Unlocked if there are no HTC Mango updates or only HTC Mango Drivers v1. So the first generation HTC devices that also have the HTC Mango Drivers v2 and the second generation HTC devices can currently not be Interop Unlocked. I am looking for an exploit in the HTC Mango Drivers v2. If you have a first generation HTC device and you have the HTC Mango Drivers v2 and you still have a backup from before that last update, you can restore that backup and apply Interop Unlock. You can update to the latest drivers again and preserve the Interop Unlock.
There are also users with 1st generation HTC devices only HTC Mango Drivers v1, who report that this is not working. This can be fixed. These people should read the notes at the end of this guide!
1. Make sure you have a backup of your device (scroll up for instructions)
2. Make sure you hava a backup of your backup (No kidding! Zune may overwrite the backup you made. Here's the backup: %LocalAppData%\Microsoft\Windows Phone Update)
3. Download this attachment to your PC: HTC Interop Unlock.xap
4. Connect your device to a PC running Zune and install the xap-file using any xap-deploy-tool. You don't need to start the app. If it starts automatically, you can close it right away.
5. Download and install HTC Connection Setup on your HTC device (if you don't have it already)
6. Start HTC Connection Setup.
7. Tap the three dots in the down-right corner of your screen and tap "manual select".
8. Tap on the country. This will open a list of countries you can select.
9. In the country-list scroll to "Interop Unlock" and select it.
10. Tap on the round ok-button at the bottom of your screen and wait until connection setup is finished.
11. Tap "Done" to exit the app.
12. Now open "Connection Setup" again. This is to prevent Connection Setup opening when you restart your device.
13. It will show you your current operator.
14. Tap on the round ok-button at the bottom of your screen and wait until connection setup is finished again.
15. Tap "Done" to exit the app.
Note for people who don't have this working: I changed the order of the steps in the guide a little bit. If you have attempted to deploy other hacks using HTC Connection Setup (GoodDayToDie version for Interop Unlock or something else) it could be that the files that were deployed are blocking this new hack. You should try to uninstall HTC Connection Setup, restart your phone and then follow the the steps in the guide again (with changed order). Hope that works for you.
Steps for Verizon Wireless Trophy users (thanks to LiFePo4 for modified instructions):
1. Make sure you have a backup of your device (scroll up for instructions)
2. Make sure you have a backup of your backup (No kidding! Zune may overwrite the backup you made. Here's the backup: %LocalAppData%\Microsoft\Windows Phone Update)
3. Download this attachment to your PC: HTC Interop Unlock.xap
4. Connect your device to a PC running Zune and install the xap-file using any xap-deploy-tool. You don't need to start the app. If it starts automatically, you can close it right away.
5. Download and install HTC Connection Setup on your HTC device (if you don't have it already)
6. Go to Settings / Cellular and set Mode to GSM. Exit back to main screen and wait for data connection to go away (there will be a little box with the crossed circle in the upper left where connection status is shown).
7. Start HTC Connection Setup.
8. Tap the three dots in the down-right corner of your screen and tap "manual select".
9. Tap on the country. This will open a list of countries you can select.
10. In the country-list scroll to "Interop Unlock" and select it.
11. Tap on the round ok-button at the bottom of your screen and wait until connection setup is finished.
12. Make sure you perform step 12 and 13 directly after each other! Tap "Done" to exit the app. This will take you back to the applist.
13. Quickly Uninstall HTC Connection Setup and never allow it to run again.
14. Power off and back on phone.
15. Go back to Settings / Cellular and set Mode to CDMA. Exit to main screen and verify 3G is there.
16. Go back to Settings / Cellular and set Mode to Global. Exit.
17. Uninstall the HTC Interop Unlock.xap
This method does not loose 3G (HTC connection setup really does no good with the CDMA network so it used only once for Interop Unlock; if it ever runs a second time it screws up the CDMA data connection).
Note to people who have trouble with their HTC Connection Setup restarting automatically on every reboot of the device, or having problems with their data connection:
Normally the Connection Setup should be restored automatically with this hack. But if something goes wrong, it is possible that your HTC Connection Setup is left in a unservicable state. I that case follow these steps:
1. Download and deploy the attachment: Repair HTC CS.xap
2. Run Connection Setup.
3. Apply settings of your operator.
4. Uninstall Repair HTC CS.
That should do it.
Note to everybody: Please report success and failure, including all device specs and abnormalities (errors etc)! I want to improve the guide as much as possible!
Have fun with homebrew now!
Heathcliff74

No link for Interop-Unlock xap

snickler said:
No link for Interop-Unlock xap
Click to expand...
Click to collapse
I added it again. My browser was behaving strangely. It got lost somehow.

Heathcliff74 said:
I added it again. My browser was behaving strangely. It got lost somehow.
Click to expand...
Click to collapse
Dude you have the legendary tools .

So, if I just have a Mango device that is Dev unlocked, I can use this and get a "full unlock" on my phone ?
I really would like to know if it works on one of the HTC leaked roms. I really want to upgrade due to the better performance, DLNA support, better radio, etc but, I can't get a "full unlock" on it due to not going back to NoDO (and there is NO backup rom for the Verizon HTC Trophy, Yes, I have looked).
Does this have the INTEROP tag in the app ? If it does not, it should install no problem on a dev unlocked device.
Almost tempted to go back to NoDo and upgrade with only a Dev unlock to 7720 to try this, if I can get a full unlock from that point, I know it will work and this would be epic !
This sounds awsome if it works on HTC devices....
Crossing fingers....

i have tried deploying it on my htc mozart. it gives an error message saying 'the program has been blocked by group policy'

no LG support yet?
(I don't need it but thought I'd ask anyway)
thanks

Ok. Not working as expected
The good news: It still seems to be working on Samsung! But you will need an updated version of the xap. I will post it in a few minutes.
I tried to deploy CustClear.provxml to \Windows. On my device that seemed to work. I thought I had disabled my root-access. But I forgot to disable some of my policies. The result was that I had access to write to \Windows this way, while 'normal' device don't have that.
But I still seem to have write-access to \provxml for Samsung. I double-checked it now.
I will update the opening post.
Sorry to HTC users
Ciao,
Heathcliff74
---------- Post added at 02:35 AM ---------- Previous post was at 01:39 AM ----------
DavidinCT said:
So, if I just have a Mango device that is Dev unlocked, I can use this and get a "full unlock" on my phone ?
I really would like to know if it works on one of the HTC leaked roms. I really want to upgrade due to the better performance, DLNA support, better radio, etc but, I can't get a "full unlock" on it due to not going back to NoDO (and there is NO backup rom for the Verizon HTC Trophy, Yes, I have looked).
Does this have the INTEROP tag in the app ? If it does not, it should install no problem on a dev unlocked device.
Almost tempted to go back to NoDo and upgrade with only a Dev unlock to 7720 to try this, if I can get a full unlock from that point, I know it will work and this would be epic !
This sounds awsome if it works on HTC devices....
Crossing fingers....
Click to expand...
Click to collapse
"FullUnlock" is a prove-of-concept from Cotulla. You can read about it here. FullUnlock is a way to run native executables.
This is slightly different. I called this "Interop Unlock". Interop locking is meant to block native code in a Silverlight app. All your normal apps are Silverlight apps. Many homebrew apps are Silverlight apps that use native code, like WP7 Root Tools. The method described in this thread is to allow Silverlight apps use native code. This is not for native executables.
Read more about the different type of unlock here.
Most custom roms already have this kind of unlock. This is primary meant for devices with Mango shipped on it.
This app does not have the Interop-flag in it. It is meant to allow to deploy other apps with the Interop flag that previously would not install.
Anyway, for now this seems to be working only on Samsungs. So unfortunately no HTC support as yet.
Ciao,
Heathcliff74

Gosh I wish the Dell Venue Pro had cool stuff, I am almost to the point of giving up hope. Ill never lose my NODO backup just in case thanks cliff

Heathcliff, you never cease to amaze me. Great work. One issue though. The Network Profile app doesn't work on my AT&T Focus, when I open it up it says "It cannot be used if in a locked state by mobile operator. If I click OK it won't let me change from AT&T.
But the good news is I was able to install your new root tools now! No rolling back to Nodo needed. I just need a way to fix my 3G without network profile
EDIT: I just tried installing the "unofficial" network profile app that works on locked phones, but the app doesn't open. It goes right back to the start screen.
EDIT 2: OK I think I have 3G back. I installed Samsung Tools by lyriquidperfection here, I selected Set 'Run ADC' flag at next boot. I now have my 3G logo back. He included the source for the xap, maybe you could include this with your xap that we can run?

Awesome!!!!!!!! Works perfectly!

I've always been able to install apps with "ID_CAP_INTEROPSERVICES". However I can never run them as they crash right away. I was really excited when I first heard of this today but now i'm just confused.

ANyone with a HTC device confirm this works ?

Nice! Worked perfectly for me (Samsung Focus) I did have to use Samsung Tools to get my 3G back since I couldn't use the Network thingy but that wasn't a problem since my phone can now sideload interop apps.

What Omnia7 ROM have you flashed, so that can get the newest Diagnosis app? I have flashed the newest WP7_Product NoDo Rom (I8700XXKC1_XXKB2) and it comes with Diagnosis ver.0103. Uninstalling and re-entering Diagnosis mode, installs the same old version.

chemeng said:
What Omnia7 ROM have you flashed, so that can get the newest Diagnosis app? I have flashed the newest WP7_Product NoDo Rom (I8700XXKC1_XXKB2) and it comes with Diagnosis ver.0103. Uninstalling and re-entering Diagnosis mode, installs the same old version.
Click to expand...
Click to collapse
I have the same ROM and the same Diagnosis app version and it works fine.

Please Help me...the trick works but i'm not able to get my 3g connection working again...I didn't understand the "samsung network profile" thing in the guide before doing the trick and now i'm without connection...how can I repair it? I'm from Italy and i have an omnia 7 and i'm not able to find the app "samsung network profile" in my marketplace...you can just tell me how to go back, it's not a problem if i'll lose the interop-unlock...

CrazySE said:
Please Help me...the trick works but i'm not able to get my 3g connection working again...I didn't understand the "samsung network profile" thing in the guide before doing the trick and now i'm without connection...how can I repair it? I'm from Italy and i have an omnia 7 and i'm not able to find the app "samsung network profile" in my marketplace...you can just tell me how to go back, it's not a problem if i'll lose the interop-unlock...
Click to expand...
Click to collapse
Just look at the previous page:
ryotgz said:
EDIT 2: OK I think I have 3G back. I installed Samsung Tools by lyriquidperfection here, I selected Set 'Run ADC' flag at next boot. I now have my 3G logo back.
Click to expand...
Click to collapse

worked perfectly on my omnia 7 with mango rtm
thanks!

so no chance for Dell Venue Pro?

Windows Update settings in Windows 10 Mobile

Has anyone checked if changing this registry entry can influence on Windows Update work?
HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsStore\WindowsUpdate
I have info that changing this value to these numbers will affect WU in such ways:
2 - WU will warn before downloading and installing updates.
3 - WU will automatically download and suggest to install updates.
4 - WU will automatically download and automatically plan the installing of updates.
5 - WU won't do anything; a user should download and install updates manually.
But is it right?

you have registry, you have value and someone told you it will effect the WU. ...but you asking someone else to check because you are too lazy. LOL

djtonka said:
you have registry, you have value and someone told you it will effect the WU. ...but you asking someone else to check because you are too lazy. LOL
Click to expand...
Click to collapse
No. I just have the latest build installed and can't check it myself.

Andrew[N] said:
Has anyone checked if changing this registry entry can influence on Windows Update work?
HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsStore\WindowsUpdate
I have info that changing this value to these numbers will affect WU in such ways:
2 - WU will warn before downloading and installing updates.
3 - WU will automatically download and suggest to install updates.
4 - WU will automatically download and automatically plan the installing of updates.
5 - WU won't do anything; a user should download and install updates manually.
But is it right?
Click to expand...
Click to collapse
as of 1607 it doesn't work unless on enterprise SKU, it did work back in 1511 I think, and option 5 was selected by default, I don't remember my phone ever doing anything other than checking for updates, I had to press download every time
but.. some people say it does work, so give it a try, I personally just gave up and just changed the phonemodelname to a 920

I cleared the question.
It works only in Windows 10 Mobile Enterprise. Windows ICD has these settings.
I installed W10M Enterprise on my phone and will check if it works, but it seems, that everything will be OK.

Production ring, the value 5 work.

[TUTORIAL] Restore Glance on Windows 10 Redstone for Unsupported Devices

Hello all,
I just wanna share a tutorial on how to restore glance screen on Windows 10 Redstone for older devices. I made this tutorial because there are so many people asking how to restore glance functionality after they update their device to Redstone. There are some guides on it but they are really hard to find. There is even an option to enable old glance screen on Gustav's Interop Tools but lot of people don't know how to use it
This tutorial is based on what I always did to restore the glance screen on my Lumia 920. Make sure that your device had glance screen feature when it was on Windows Phone. Otherwise, this trick wouldn't work. Follow this tutorial on your own risk. I'm not responsible for any damage caused to your device.
Part 1: Install Interop Tools & Glance Screen APPX
On your PC, Download the latest version of Interop Tools from https://forum.xda-developers.com/windows-10-mobile/windows-10-mobile-apps-and-games/app-interop-tools-versatile-registry-t3445271 and the attached glancescreen_appx.zip. Put all the APPXs (including dependencies) on your phone storage (e.g. Download folder)
On your phone. go to Settings > Update & security > For developers
Turn on Developer mode, Device Discovery and Device Portal
Open Microsoft Edge, and go to http://127.0.0.1/ to open Device Portal (it is possible to do this using your PC via WiFi but it'll be slower since the APPXs need to be transfered via WiFi)
If there is a certificate error, ignore it and click Continue to this webpage
You might be asked to authenticate. Go to the previous developer settings and click Pair button
On the Device Portal, Click Apps on the left sidebar
Install all Interop Tools dependencies ONE BY ONE. After that, install the main Interop Tools APPX
Install glancescreen.appx
Turn off Device Discovery and Device Portal on the developer settings
Part 2: Restore Missing Glance Files & Registry
Open Interop Tools > This Device. Open sidebar, choose Interop Unlock
Check Restore NDTKSvc and restart your device (on some occasions, the other option can't be turned on until you restart your device)
Open Interop Tools > This Device > Interop Unlock. Check Full Filesystem Access and restart your device once more (some folders can't be seen until you restart the device)
Connect your device to your PC via USB
On your PC, download the attached missing_glance_files.zip and put them on [Your Phone]\Data\SharedData\OEM\Public\ using Windows Explorer
Open Interop Tools and turn off Full Filesystem Access
Open sidebar, choose Tweaks
Scroll down and turn on Enable Old Glance Screen (RS1)
Part 3: Fix Glance Font (Non-WXGA devices only)
Open Settings > System > About. Click More info button and check your device Screen resolution
If it's 768x1280 (WXGA), jump to part 4. Otherwise, open Interop Tools > This Device. Open sidebar, choose Registry Browser
Navigate to HKLM\Software\OEM\Nokia\lpm\FontFile
If your device screen resolution is 480x800 (WVGA), replace lpmFont_WXGA.bin with lpmFont_WVGA.bin. For other resolutions, you might wanna check out the other fonts inside lpmFonts_4.1.12.4 folder in the attached missing_glance_files.zip
Part 4: Update Glance Screen
Open Store. Open sidebar, choose Downloads and updates
Click Check for updates and update Glance Screen
Restart your device
Miscellaneous
How to Fix MTP Root Path to Deactivate Full Filesystem Access
How to Increase Glance Font to Fit Device Screen Like on Windows Phone
I hope this tutorial helps. Goodluck!

hi
thank you.
can you help me for change glance font size for this method?

Arshen said:
hi
thank you.
can you help me for change glance font size for this method?
Click to expand...
Click to collapse
Is it too small? If so, follow the steps below...
How to Increase Glance Font to Fit Device Screen Like on Windows Phone
The glance font on Windows Phone is bigger than on Windows 10 Mobile so that the text fits the device screen. I actually prefer the smaller font size because that's how the glance screen displayed on the new devices and it looks more elegant. But if you still want to increase the font size, here's the steps...
Open Interop Tools > This Device. Open sidebar, choose Registry Browser
Navigate to HKLM\Software\OEM\Nokia\lpm\FontFile
Replace \Data\SharedData\OEM\Public\lpmFonts_4.1.12.4\ with \Windows\system32\
Write the change

AWasisto said:
Is it too small? If so, follow the steps below...
How to Increase Glance Screen Font
The glance font on Windows Phone 8.1 is bigger than on Windows 10 Mobile. I actually prefer the smaller font size because that's how the glance screen displayed on Lumia 950 and it looks more elegant. But if you want to increase the font size, here's the steps
Open Interop Tools > This Device. Open sidebar, choose Registry Browser
Navigate to HKLM\Software\OEM\Nokia\lpm\FontFile
Change the value to \Windows\system32\lpmFont_WXGA.bin
Write the change
To restore the default W10M glance font, change the value to \Data\SharedData\OEM\Public\lpmFonts_4.1.12.4\lpmFont_wxga.bin
Click to expand...
Click to collapse
i want to make glance screen font small!
how can i do this?

Arshen said:
i want to make glance screen font small!
how can i do this?
Click to expand...
Click to collapse
Try this value: \Data\SharedData\OEM\Public\lpmFonts_4.1.12.4\lpmFont_720p_hi.bin
You can try lpmFont_720p.bin or lpmFont_wvga.bin if it's not small enough. lpmFont_720p_hi.bin > lpmFont_720p.bin > lpmFont_wvga.bin

Does anyone have a problem with the MTP after turning off full filesystem access?

Arshen said:
i want to make glance screen font small!
how can i do this?
Click to expand...
Click to collapse
this worked for me on my Lumia 810
https://forum.xda-developers.com/windows-10-mobile/glance-screen-original-files-lumia-820-t3463740

will it really work on unsupported devices which does not support glance , because MS said its a Hardware feature ?

TulakChoco said:
this worked for me on my Lumia 810
https://forum.xda-developers.com/windows-10-mobile/glance-screen-original-files-lumia-820-t3463740
Click to expand...
Click to collapse
Whoa I've just realized the font needs to be changed for WVGA devices. Thanks! Tutorial updated
adityashingade said:
will it really work on unsupported devices which does not support glance , because MS said its a Hardware feature ?
Click to expand...
Click to collapse
If glance screen was available on the device while it's on Windows Phone, then it would work. Otherwise, nope, I don't think so

thanks, working on my 920.

On my 1020 worked yeah but after while screen goes crazy and nightmode when time change place to up its fuked. 15014 not worked even soft reset or what ever. 15007 worked while after glance installed.
So last 2 fast updates (15007 and 15014) glance not working anymore what ever you do. Not trying to install anymore glance and phone works ok and im happy.

jaspi72 said:
On my 1020 worked yeah but after while screen goes crazy and nightmode when time change place to up its fuked. 15014 not worked even soft reset or what ever. 15007 worked while after glance installed.
So last 2 fast updates (15007 and 15014) glance not working anymore what ever you do. Not trying to install anymore glance and phone works ok and im happy.
Click to expand...
Click to collapse
Does it flicker vertically? I have two Lumia 920, both of them use the same firmware and build. But one of them flickers like hell when showing glance screen and the flicker won't stop until I reboot the device. I read somewhere it's a software problem, someone said that the double tap to unlock option needs to be be turned off (i haven't tried that btw). But I think it has something to do with the hardware since the other 920 worked flawlessly without turning off the double tap to unlock option. Still have no idea why some devices does that...
Btw warning updated, I only tested this on RS1

No nothing vertically just crazy blurred mesh screen and cant do anything. Shutting phone like pushed shutdown putton when screen is blurred and do like normally (fingered down) phone shut down and camera sounds do work but screen is total mesh. Hard reset worked and when booted i didnt even try to put glance stuff on and now work. Nothing to do about doubletab i tested just glance stuff. Ok latest fast build is jamming making calls, not showing maked calls and sendet messages so hell please dont even try it.. Going back to last worked backup (slow build) and wait some

Q- put the whole zip(missing glance file.zip) in oem\public or ,put the files ,
I put file nd not working on L540,help please

thank you
:good::good::good: work perfect in lumia 920

SSWJ said:
Q- put the whole zip(missing glance file.zip) in oem\public or ,put the files ,
I put file nd not working on L540,help please
Click to expand...
Click to collapse
Does Lumia 540 support glance when it was on Windows Phone 8.1? If it doesn't, this tutorial won't work

It's working quite well on my 810

AWasisto said:
Does Lumia 540 support glance when it was on Windows Phone 8.1? If it doesn't, this tutorial won't work
Click to expand...
Click to collapse
Oh no It doesn't support

i use interop tool to restore glance screen in lumia 920 w10 using this.
it fonction; but when i connect my phone to pc it always open Filesystem Access
i desactivate Full Filesystem Access in Interop Tools > This Device > Interop Unlock and restart my device but still have the same issu
please any help thanks

ettoumia said:
i use interop tool to restore glance screen in lumia 920 w10 using this.
it fonction; but when i connect my phone to pc it always open Filesystem Access
i desactivate Full Filesystem Access in Interop Tools > This Device > Interop Unlock and restart my device but still have the same issu
please any help thanks
Click to expand...
Click to collapse
Finally! I thought I'm the only one having trouble deactivating full filesystem access
How to Fix MTP Root Path to Deactivate Full Filesystem Access
If you can't deactivate full filesystem access by just unchecking its checkbox on Interop Tools, I found a way to fix it
Open Interop Tools > This Device. Open sidebar, choose Interop Unlock
Check Full Filesystem Access
Enter C:\Data\Users\Public on MTP Root Path
Click the write button next to MTP Root Path
Uncheck Full Filesystem Access
Restart your device

[help] can't add registry

Hello all..as i was saying that i can't add registry in my phone using interop tool. I am using interop tool L. i am getting this error
something went worng could not add specific key,no changes to phone registry were made.so i used registry editor but nothing changed there is no new registry created.here are screenshots....thank u

[email protected] said:
Hello all..as i was saying that i can't add registry in my phone using interop tool. I am using interop tool L. i am getting this error
something went worng could not add specific key,no changes to phone registry were made.so i used registry editor but nothing changed there is no new registry created.here are screenshots....thank u
Click to expand...
Click to collapse
I happen to have the same problem lately... If you try to read the key/value, it's gonna return the value/key value but, no registry is created.

xxJMarian said:
I happen to have the same problem lately... If you try to read the key/value, it's gonna return the value/key value but, no registry is created.
Click to expand...
Click to collapse
See if i read the value the operation says read but if i try to add registry it says no specific key added, no change to phone registry were made and i am not understanding why this is happening..

I have had imports fail but the Edit Registry option works. And vice versa. Depends on the device too. On the Nokia models I can edit almost anywhere just by installing and enabling interop unlock. If I use my 950 XL or a 650 which have some added security features it becomes hit or miss. Even if I push the generic ndtk cab to the device. Other times I have to do a hard reset before I can edit the registry where I need. Usually after a recent update or build version release.
EDIT: I just looked at your pics. You are trying to add Sirepuser to the system control key but why are you adding it that way? I am assuming the template is not working? Also why did you need to toggle Restore NDTKsvc? Was editing working before that and then stopped? Lastly which device model are you using Interop Tools on?
I get what you mean. Must be interop tools can add keys/values there using the template but can't read them.

nate0 said:
On the Nokia models I can edit almost anywhere
Click to expand...
Click to collapse
Can you edit or create keys/values inside HKCU? Registry editor shows that you "created" the key/value you want but, once you look at it with the browser, the value or key created is not there...

It seems the key or values under certain areas of the registry are either not supported or not accessible for read from InteropTools.
Edit: If I enable root access after unlocking the boot loader on my 1520 I can see the key values under HKLM\BCD00000001. Must be related to a plolicy interop tools cannot run past, and unlocking the security policies allows it to be unrestricted.

nate0 said:
It seems the key or values under certain areas of the registry are either not supported or not accessible for read from InteropTools.
Edit: If I enable root access after unlocking the boot loader on my 1520 I can see the key values under HKLM\BCD00000001. Must be related to a plolicy interop tools cannot run past, and unlocking the security policies allows it to be unrestricted.
Click to expand...
Click to collapse
Ok agree what you say this means interop tool can't read and write these keys but they are present then why i cant get cmd access.

I have no idea. That's a whole other topic...have you read thoroughly how to do it from the forums? What steps have you done?

nate0 said:
I have no idea. That's a whole other topic...have you read thoroughly how to do it from the forums? What steps have you done?
Click to expand...
Click to collapse
Yes i have read all the steps carefully and do as it says but nothing happened i am getting the same error i thinked there is no key under ssh that's why i am getting this error but after knowing that interop tool can't read these keys i don't know what to do ?. Were you able to get cmd access???

nate0 said:
I have had imports fail but the Edit Registry option works. And vice versa. Depends on the device too. On the Nokia models I can edit almost anywhere just by installing and enabling interop unlock. If I use my 950 XL or a 650 which have some added security features it becomes hit or miss. Even if I push the generic ndtk cab to the device. Other times I have to do a hard reset before I can edit the registry where I need. Usually after a recent update or build version release.
EDIT: I just looked at your pics. You are trying to add Sirepuser to the system control key but why are you adding it that way? I am assuming the template is not working? Also why did you need to toggle Restore NDTKsvc? Was editing working before that and then stopped? Lastly which device model are you using Interop Tools on?
I get what you mean. Must be interop tools can add keys/values there using the template but can't read them.
Click to expand...
Click to collapse
Its was in the tutorial it said on ndtksvc and reboot and i am using Microsoft Lumia 540 os build 10.0.15063.540 interop tool L version 2.0.79

[email protected] said:
Yes i have read all the steps carefully and do as it says but nothing happened i am getting the same error i thinked there is no key under ssh that's why i am getting this error but after knowing that interop tool can't read these keys i don't know what to do . Were you able to get cmd access???
Click to expand...
Click to collapse
Yes, but via ssh. CMD access from the IT app requires elevated privileges and some other tweaks. I can open that part of InteropTools with root enabled without error but was unable to type. You would need to check with gus33000 about that. I just use cmd over ssh for now.
---------- Post added at 03:56 PM ---------- Previous post was at 03:54 PM ----------
[email protected] said:
Its was in the tutorial it said on ndtksvc and reboot and i am using Microsoft Lumia 540 os build 10.0.15063.540 interop tool L version 2.0.79
Click to expand...
Click to collapse
You should only need to toggle the Restore NDTKsvc if you suddenly lose the ability to edit the registry after successfully getting access the first time. I have had this happen after an update or if system settings updated...

The registry browser has limited access to the registry, it can't enumerate every key, but that totally doesn't mean they aren't here, that's why you have a registry editor section in the page to actually add values where you can't see anything, in your screenshots you wrote fine to those values, so it worked.

gus33000 said:
The registry browser has limited access to the registry, it can't enumerate every key, but that totally doesn't mean they aren't here, that's why you have a registry editor section in the page to actually add values where you can't see anything, in your screenshots you wrote fine to those values, so it worked.
Click to expand...
Click to collapse
Then why i can't get cmd access i have tried everything....every step as it was in interop tool but nothing happened. I tried to connect to ssh server via ssh client on windows store but i can't get success. I just want to know where i am missing..

[email protected] said:
Then why i can't get cmd access i have tried everything....every step as it was in interop tool but nothing happened. I tried to connect to ssh server via ssh client on windows store but i can't get success. I just want to know where i am missing..
Click to expand...
Click to collapse
Did you set a custom password in interop tools and did you get cmd.exe and cmd.exe.mui via ssh on the device?
You also can't use a client on the device itself.

gus33000 said:
Did you set a custom password in interop tools and did you get cmd.exe and cmd.exe.mui via ssh on the device?
You also can't use a client on the device itself.
Click to expand...
Click to collapse
Yes i set custom password but didn't get cmd access via ssh

nate0 said:
Yes, but via ssh. CMD access from the IT app requires elevated privileges and some other tweaks. I can open that part of InteropTools with root enabled without error but was unable to type. You would need to check with gus33000 about that. I just use cmd over ssh for now.
---------- Post added at 03:56 PM ---------- Previous post was at 03:54 PM ----------
You should only need to toggle the Restore NDTKsvc if you suddenly lose the ability to edit the registry after successfully getting access the first time. I have had this happen after an update or if system settings updated...
Click to expand...
Click to collapse
Okk can you help to get cmd access via ssh please

nate0 said:
Yes, but via ssh. CMD access from the IT app requires elevated privileges and some other tweaks. I can open that part of InteropTools with root enabled without error but was unable to type. You would need to check with gus33000 about that. I just use cmd over ssh for now.
---------- Post added at 03:56 PM ---------- Previous post was at 03:54 PM ----------
You should only need to toggle the Restore NDTKsvc if you suddenly lose the ability to edit the registry after successfully getting access the first time. I have had this happen after an update or if system settings updated...
Click to expand...
Click to collapse
Okk can you help to get cmd access via ssh please

got success
finally got success access cmd via ssh.thanks everyone for helping me..so the conclusion i got:-
first some keys are protected so can't be access by interop tool but can be edit by registry editor.
Second you have to set custom password through ssh account manager but i don't know why system console in interop tool is not working but you can access cmd via ssh if you have done all the steps correctly and i finally i know where i was missing all the time it was not registry as i was thinking it is not present the thing i was missing was i tried to connect to ssh client on my device it didn'tworked but when i tried to connect to cmd with another device via ssh it worked and all credit goes to @gus33000 and @nate0 who helped me...Thank you:good: