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.
Related
I hope starting a new thread is the way to go on this...
I just updated to the new Sprint Official WM 6.1 ROM, and immediately could not connect to the internet.
I tried running the IOTA automatic data provisioning update (Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start) and it failed repeatedly with a 1012 error. As was posted by others, I noticed that there was a "CurrentUserName" setting in Start->Settings->System->Device Information that had [email protected] where I would have expected to see [email protected] instead. (that would have been my Sprint provided email address) The first thing I tried was to go to the phone dialpad and dial ##3282# to start the EPST program and check my data provisioning settings (this requires that you know your MSL - Master Service Lock Code - if you are going to edit). UserName was blank there, so I tapped the blank setting and held down until an "EDIT" menu popped up. I tapped "EDIT" and changed it to the previously correct [email protected] value. After saving changes and another reboot, I still could not connect to the internet, run IOTA, and the "CurrentUserName" was still wrong. After searching through various settings looking for a way to change the currentusername, I installed PHM Registry Editor and searched again.
In HKEY_LOCAL_MACHINE/Software/OEM/DIM there is a key "EnableCurrentUserName" and it was set to 1. I edited that and set it to 0, exited the Registry Editor, and restarted the device by holding the power button until it warned me about shutting down. I tapped "Yes" and it shut down and restarted. The "CurrentUserName" setting no longer appeared in the Device Information page. At this point I was able to run IOTA successfully and imediately after that I could use the internet and other data services.
I hope this helps someone. Sorry to be so long winded, but I was trying to answer as many "How? Where?" questions as I could as I went.
Briefly:
1. Using WM Registry Editor software, change HKLM/Software/OEM/DIM/"EnableCurrentUserName" from 1 to 0 then save changes and exit editor.
2. Dial ##3282# and edit UserName to correct [email protected] address. Device will reboot when you exit and save changes.
3. Run IOTA by going to Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start
Thanks to all the others here who have helped me along the way,
Scruffy
anyone else know if this works?
i just flashed the new sprint rom and now the data connection does not work.. no internet.. ? I was just wondering if anyone else had this problem and does this fix it?
After some more time with this ROM installed I have found that it is not neccessary to change the ##DATA# (##3282#) user name settings. Just change the HKEY_LOCAL_MACHINE/Software/OEM/DIM/EnableCurrentUserName value to zero, save changes and then you can run the IOTA update successfully (or at least I can).
I have found that I need to do this every time I do a hard reset of my device. I hope this helps someone else.
Scruffy
this did not work for me.. I Get error code 67
i started a new thread here........ http://forum.xda-developers.com/showthread.php?t=415666
so maybe someone will chime in... the ##3282# does not work for me at all.. you hit that on the dial pad and nothing happens... so i can not access that menu...
For now i went back to a OEM rom and called sprint and they got me working by doing a MASTER RESET... also ##3282# works on OEM roms but i think the file EPST.EXE is missing from the CUSTOM roms... any input would be great..
Not working for me.
i'm sure a master reset from within #778 or whatever would work but i don't feel like
putting in the data again.
Scruffy said:
I hope starting a new thread is the way to go on this...
I just updated to the new Sprint Official WM 6.1 ROM, and immediately could not connect to the internet.
I tried running the IOTA automatic data provisioning update (Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start) and it failed repeatedly with a 1012 error. As was posted by others, I noticed that there was a "CurrentUserName" setting in Start->Settings->System->Device Information that had [email protected] where I would have expected to see [email protected] instead. (that would have been my Sprint provided email address) The first thing I tried was to go to the phone dialpad and dial ##3282# to start the EPST program and check my data provisioning settings (this requires that you know your MSL - Master Service Lock Code - if you are going to edit). UserName was blank there, so I tapped the blank setting and held down until an "EDIT" menu popped up. I tapped "EDIT" and changed it to the previously correct [email protected] value. After saving changes and another reboot, I still could not connect to the internet, run IOTA, and the "CurrentUserName" was still wrong. After searching through various settings looking for a way to change the currentusername, I installed PHM Registry Editor and searched again.
In HKEY_LOCAL_MACHINE/Software/OEM/DIM there is a key "EnableCurrentUserName" and it was set to 1. I edited that and set it to 0, exited the Registry Editor, and restarted the device by holding the power button until it warned me about shutting down. I tapped "Yes" and it shut down and restarted. The "CurrentUserName" setting no longer appeared in the Device Information page. At this point I was able to run IOTA successfully and imediately after that I could use the internet and other data services.
I hope this helps someone. Sorry to be so long winded, but I was trying to answer as many "How? Where?" questions as I could as I went.
Briefly:
1. Using WM Registry Editor software, change HKLM/Software/OEM/DIM/"EnableCurrentUserName" from 1 to 0 then save changes and exit editor.
2. Dial ##3282# and edit UserName to correct [email protected] address. Device will reboot when you exit and save changes.
3. Run IOTA by going to Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start
Thanks to all the others here who have helped me along the way,
Scruffy
Click to expand...
Click to collapse
how do i find [email protected] where would that be?
Scruffy said:
3. Run IOTA by going to Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start
Click to expand...
Click to collapse
I just upgraded to NFSFAN's latest ROM, everything went well but I can not get my internet to work. The one thing I did notice is under the services tab, internet is not an option. I loaded the dcd sprint carrier 20090714 cab am I missing something else?
Thank you for any help you can provide.
Update:
Well I went back and flashed to the HTC 6.1 rom, then back to the 6.5 rom. That fixed my internet issues, but that option is still missing for me. Then after all of that my MSID was really screwed up. Everything seems to be good now.
please please help me clear the instructions
i have a horribly vague idea of what i need to do, to get the internet working again.
i already got the IOTA_1120 zip file in my cell but when i even try to open it up it says that there is no application that is related to to it, so i must start this application and open up the file from within. How do i do this? am I even doing what im supposed to??
Where exactly is HKEY_LOCAL_MACHINE/Software/OEM/DIM and how do i get there???
if you could please instruct me with simple stieps i would greatly appreciate it, simple being like start>program files> etc.
please help i am one step away from smashing this damm cell into the wall
electricfeel_2012 said:
i have a horribly vague idea of what i need to do, to get the internet working again.
i already got the IOTA_1120 zip file in my cell but when i even try to open it up it says that there is no application that is related to to it, so i must start this application and open up the file from within. How do i do this? am I even doing what im supposed to??
Where exactly is HKEY_LOCAL_MACHINE/Software/OEM/DIM and how do i get there???
if you could please instruct me with simple stieps i would greatly appreciate it, simple being like start>program files> etc.
please help i am one step away from smashing this damm cell into the wall
Click to expand...
Click to collapse
The path of HKEY.... is actually on the registry. You need to use a registry editor (like PHM Regedit) to make the necessary changes to the registry. I would recommend you to re-read those instructions as they will not get any easier than that. Alternatively, if you are on Sprint's official rom and have absolutely no clue what you are doing, you can always call them and ask them for help.
As far as the IOTA zip file, if you cannot open it, that means that you do not have any program to extract from compressed files in your device. Your best bet is to transfer the file to the desktop and extract it there. Once you are done, place the extracted contents back in the device and run it in there.
Thanks to Dave Amenta, i got around to the Registry Editor in the Dell Venue Pro. I am able to read values, but not able to set them..May be i am doing something wrong. I am giving it to the community to crack it open.
Here is what you need to do to get to the registry editor:
1. Go to the EM App in the DVP.
2. Choose RD Test. It will prompt for a textbox to enter something (its basically asking for password). Enter *#6336# . Now voila, you are in MFC Test.
3. Scroll to the bottom of the list and choose About EM.
4. Now it will say sorry..bla,.bla.. It will also have a textbox for another password. Enter *#734#
5. Voila you are in Registry Editor.
6.To read a value, go to the 'Path' prompt. While in, choose L M/C R/C U, etc..they are nothing but HKEY_LOCAL_MACHINE\HKEY_CURRENT_USER,etc.. Then enter the remaining path name. In the Key field, enter the key you want to query. In the Type, press the down arrow and choose the type. Now hit the 'Get' button on top, you will see the result (If you enter all right). If you want to set data, i think you enter the value in Data field and hit set. But, so far no luck. Iam still researching.
IMPORTANT: DO not do this as this is super advanced user mode. You might end up brick'ng ur DVP if you do not know what your are doing.
This sounds awfully similar to the LG registry editor on the phone. I do not have a DVP in my possession, but I know a friend who does. I shall try this and let you know how it goes. (BTW, Dell Venue Pro works on Wind and Mobilicity in Canada)
I am trying to do a AT Hyperterminal command to unlock the phone.,Will see how it goes.
notebookgrail said:
Thanks to Dave Amenta, i got around to the Registry Editor in the Dell Venue Pro. I am able to read values, but not able to set them..May be i am doing something wrong. I am giving it to the community to crack it open.
Here is what you need to do to get to the registry editor:
1. Go to the EM App in the DVP.
2. Choose RD Test. It will prompt for a textbox to enter something (its basically asking for password). Enter *#6336# . Now voila, you are in MFC Test.
3. Scroll to the bottom of the list and choose About EM.
4. Now it will say sorry..bla,.bla.. It will also have a textbox for another password. Enter *#734#
5. Voila you are in Registry Editor.
6.To read a value, go to the 'Path' prompt. While in, choose L M/C R/C U, etc..they are nothing but HKEY_LOCAL_MACHINE\HKEY_CURRENT_USER,etc.. Then enter the remaining path name. In the Key field, enter the key you want to query. In the Type, press the down arrow and choose the type. Now hit the 'Get' button on top, you will see the result (If you enter all right). If you want to set data, i think you enter the value in Data field and hit set. But, so far no luck. Iam still researching.
IMPORTANT: DO not do this as this is super advanced user mode. You might end up brick'ng ur DVP if you do not know what your are doing.
Click to expand...
Click to collapse
It looks like the button isn't wired up to perform the SET command - the event handler is there, the button is there, but clicking it even without entering any data should return "1", but it's not doing anything...
What do you mean by AT unlock? What commands are you going to send to the modem? Do you have the modem drivers? If not, take a look here: http://forum.xda-developers.com/showthread.php?t=929468
kltye said:
It looks like the button isn't wired up to perform the SET command - the event handler is there, the button is there, but clicking it even without entering any data should return "1", but it's not doing anything...
What do you mean by AT unlock? What commands are you going to send to the modem? Do you have the modem drivers? If not, take a look here: http://forum.xda-developers.com/showthread.php?t=929468
Click to expand...
Click to collapse
When i get home, i will post the Registry Set Command CS code.
AT command - Yes, the command to the modem. And yes, i used the HTC Modem driver you linked for the DVP. I am able to query the modem from the modem properties - but i can't enter any commands in that properties window. So i am going to do a hyperterminal to send AT commands for SIM Locking and try to unlock it.
I also came across a test called 'SIM Lock' in Protocol, which returns what is its locked to.
notebookgrail said:
When i get home, i will post the Registry Set Command CS code.
AT command - Yes, the command to the modem. And yes, i used the HTC Modem driver you linked for the DVP. I am able to query the modem from the modem properties - but i can't enter any commands in that properties window. So i am going to do a hyperterminal to send AT commands for SIM Locking and try to unlock it.
I also came across a test called 'SIM Lock' in Protocol, which returns what is its locked to.
Click to expand...
Click to collapse
The registry set command is:
IEmToCom.sync("EM:REGISTRY_SET:" + <path> + "," + <key> + "," + <data type, e.g. DWORD> + "," + <data> + "," + <path_type expressed as int> + ";", 1, false);
I was working with Dave over the weekend, but it looks like whatever value we insert is not being accepted - quite possibly because Dell hasn't implemented the interface yet.
this should surprise me and yet...
THIS IS DELL!
kltye said:
What do you mean by AT unlock? What commands are you going to send to the modem? Do you have the modem drivers? If not, take a look here: http://forum.xda-developers.com/showthread.php?t=929468
Click to expand...
Click to collapse
For the AT unlock, go to protocol, then TMO, then AT Command - Here you can pass various AT Commands. Unfortunately, we need the Password to reset any setting here. The password is 8 char long. And the DVP is 'ph-net pin' locked.
damn.....i think it probably means that we need to get the modem rom somehow in order to figure out how to generate the unlock PIN
I'm probably missing something really obvious here, but what does SIM unlocking have to do with registry write access?
kltye said:
I'm probably missing something really obvious here, but what does SIM unlocking have to do with registry write access?
Click to expand...
Click to collapse
It was a off topic discussion. I should have started a new thread for it. My mistake.
Is there anyone volunteering to reset their phone (cold boot)? I think i might have found the way to edit the registry. There are 2 modes for the EM App. One is Driver and another is socket. Not sure which one is by default. But i know how to change them. It requires a reset of the phone (cold boot) to take effect. I have too much of data on my phone to try it and reload everything. I can PM them the details and see if they are able to edit the registry.
notebookgrail said:
Is there anyone volunteering to reset their phone (cold boot)? I think i might have found the way to edit the registry. There are 2 modes for the EM App. One is Driver and another is socket. Not sure which one is by default. But i know how to change them. It requires a reset of the phone (cold boot) to take effect. I have too much of data on my phone to try it and reload everything. I can PM them the details and see if they are able to edit the registry.
Click to expand...
Click to collapse
You could try calling new EMToCom() rather than EMToComByDriver() when you initialize the connection, and see if that works. I've tried it and it seems that it fails to execute the command, with the debug window printing:
A first chance exception of type 'System.Runtime.InteropServices.COMException' occurred in EM.dll
calling COM receive error(socket) : 0xffffffff
I tried calling the turn on LED command via my flashlight app that works fine with the driver connection, but I'm getting the same exception when I connect via socket. Do you know if there's a special way to send commands if you connect via socket?
notebookgrail said:
Is there anyone volunteering to reset their phone (cold boot)? I think i might have found the way to edit the registry. There are 2 modes for the EM App. One is Driver and another is socket. Not sure which one is by default. But i know how to change them. It requires a reset of the phone (cold boot) to take effect. I have too much of data on my phone to try it and reload everything. I can PM them the details and see if they are able to edit the registry.
Click to expand...
Click to collapse
I'll be a guinea pig
domineus said:
I'll be a guinea pig
Click to expand...
Click to collapse
Sent you a PM.
Shoot me the details and I may be able to help out sometime this week.
it didn't work for me...doubt it will work for anyone else =/
domineus said:
it didn't work for me...doubt it will work for anyone else =/
Click to expand...
Click to collapse
Was it doing the same blank result box? Any difference did you notice with either the Driver or Socket option? - i mean not just registry editor, but overall.
blank result no changes =/
I hope we all find some progress on this because I believe that this is what is holding us back from a lot of customization on this phone....
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?
Hello Folks,
Yeah this is the First thread, First Post about the Windows 10 Mobile Hacking.
Now the First Interop Unlock hack for W10M is now available. It's currently limited to LUMIA/SAMSUNG phones, although we're trying to extend it to other OEM Device, of course. (It requires specific Driver/Services to "RUN" into "SYSTEM" Privileges. Hence, other OEM Device is lack of these. I.e HTC/Micromax etc. etc.)
*** UPDATE : Microsoft is trying to break our hack through blocking "NdtkSvc" on Lumia. So the hack currently doesn't work directly on Lumia 950/550 or later. Even if you updated extras+info on any lumia you will loss Service Access. So Stay Away from Extras+Info***
A brief summary, for those unfamiliar with interop-lock:
Windows Phone allows a number of high-privilege app capabilities, which can be used to make changes to the OS which are normally not possible for a third-party Applications.
The limitation on whether we can use these capabilities or not is based on what "level" of developer unlock the phone has.
ON WP7/8/8.1
Standard "ISV" (Independent Software Vendor) Dev Unlock (max 10 apps or less) is what pretty much everybody gets.
OEMs, however, get a special OEM Developer Unlock (300 apps or more) which gives them the ability to use much higher-privilege app capabilities than the standard ISV unlock permits. The name comes from ID_CAP_INTEROPSERVICES, the capability which was most important in WP7/WP8/8.1.
However, there are a great many interesting capabilities. Note that Interop-unlock by itself does not enable all of these. However, at least on Lumia/Samsung phones, it is now possible to enable *all* the capabilities.
As per my Research Microsoft has give up some FREEDOM to the 3rd Party Developers. Now the "ISV" Developers can sideload apps with the All "SECOND PARTY CAPABILITIES". However, having a Some hive privilege "SYSTEM" Resource that we can expand it to Enable All Capabilities.
The instructions are as follows:
1. Turn "ON" Developer Unlock Mode. (Go to Settings> Update & Security> For Developers)
2. Download "Root Tool.xap" from attachments and deploy It.
Recommended:
Go to "JailBreak Tool"
Select your choice, That's It !
Custom:
Go to Device Specific Registry Editor Tool.
Select "HKEY_LOCAL_MACHINE"
Write default values.
(For Lumia)
Code:
"SOFTWARE\Microsoft\DeviceReg\Install"
"MaxUnsignedApp"=DWORD:7FFFFFFF
(For Samsung)
Code:
"SOFTWARE\Microsoft\DeviceReg\Install"
"MaxUnsignedApp"=DWORD:2147483647
Preventing Unlock:
Code:
"SOFTWARE\Microsoft\DeviceReg"
"PortalUrlInt"="https://127.0.0.1"
"PortalUrlProd"="https://127.0.0.1"
Unlocking NEW Capability Engine:
Write these values:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SecurityManager\AuthorizationRules\Capability\capabilityRule_DevUnlock]
"CapabilityClass"="capabilityClass_DevUnlock_Internal"
"PrincipalClass"="principalClass_DevUnlock_Internal"
ENJOY
Hence, this is not a Complete "Root Access" but we are working on it to gain Full SYSTEM Access.
Still, If you got any Issue's after this tutorial then ask your "Questions" In Q/A Thread.
SPECIAL Thanks to @vcfan (Without the RPC Code from "vcFAN" was Impossible to Interop Unlock or Capability Unlock)
Thanks to @ngame and @GoodDayToDie
Thanks Everybody for your Big Support.
Reserved For Common Q/A
Reserved For Further Developments, LOGS and Related Apps
Questions and Answers
Will this work on other OEM Device / Are you working on this for other OEM Device / What about HTC, or some other OEM?
The current hack relies on a Lumia/Samsung-specific component. Adding support for other phones will require new hacks. We are looking into it.
Can I re-lock my phone if I want to?
Yes, easily. The simplest method is to turn off the "Developer mode" in Settings> Update & Security> For Developers. This doesn't remove any changes that were made using the interop-unlock, though (for example, it won't undo the Capability-Unlock hack, not will it set back the Full FS Access hack). Apps that require interop-unlock will still be installed, but may no longer run. To manually remove interop-unlock, you can reset all the registry values that were changed by the interop-unlock hack to their original values, and remove all the apps. There still may be a great many other changes that also need reverting, though, if you want to get back to stock settings.
Can I get my phone completely back to stock settings without knowing every little thing I changed?
Yes, a hard (factory) reset will undo all changes made by interop-unlock, or any apps (including ones that require interop-unlock), and will remove all apps. If you need to send your phone in for warranty servicing and are worried that they won't take it because you interop-unlocked it, this approach will fix that (they would probably tell you to hard-reset anyhow, if it's conceivably a software problem).
Will the interop-unlock survive a hard reset?
Not using this method! Read the question above. This unlock is purely in software, not firmware; it is reset along with everything else.
Thanks bro, I worked on my lumia 830 with build 10512.
But I already had the vcREG installed, root_tool not worked for me.
denisf1981 said:
Thanks bro, I worked on my lumia 830 with build 10512.
But I already had the vcREG installed, root_tool not worked for me.
Click to expand...
Click to collapse
Try Once.
XAP Updated. My Mistake, I was not checked anything.
djamol said:
Try Once.
XAP Updated. My Mistake, I was not checked anything.
Click to expand...
Click to collapse
Thank you, now work
Hi djamol,
Thanx for this. So after doing this, are we able to say put HOSTS to block ads? I have not had the time to try this, gonna do this after work
oelapoel said:
Hi djamol,
Thanx for this. So after doing this, are we able to say put HOSTS to block ads? I have not had the time to try this, gonna do this after work
Click to expand...
Click to collapse
It's a full interop/cap unlock based on VCREG 1.1 project
you can navigate Lumia registry editor -> templates -> check the check boxes -> apply
then use Custom PFD to set these values :
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SecurityMana ger\AuthorizationRules\Capability\capabilityRule_D evUnlock]
"CapabilityClass"="capabilityClass_DevUnlock_Inter nal"
"PrincipalClass"="principalClass_DevUnlock_Interna l"
if you see any SPACE in values above they are seems xda bug . no spaces in above strings
Do I need to use the WP10 deployer or does the 8.1 work too?
I am asking because I don't yet have VS2015 installed and would like to not require it (first because I am used to VS2013 and second because the dreamspark servers seem to be incredibly slow)
ngame said:
It's a full interop/cap unlock based on VCREG 1.1 project
you can navigate Lumia registry editor -> templates -> check the check boxes -> apply
then use Custom PFD to set these values :
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SecurityMana ger\AuthorizationRules\Capability\capabilityRule_D evUnlock]
"CapabilityClass"="capabilityClass_DevUnlock_Inter nal"
"PrincipalClass"="principalClass_DevUnlock_Interna l"
if you see any SPACE in values above they are seems xda bug . no spaces in above strings
Click to expand...
Click to collapse
amazing. confirmed interop unlock works on my NL1520. no more ads.. this is the most annoying thing using w10m. cheers
I'll play around a bit more later on when i have time
Can anyone plz explain what to do after installing root tools........
Anyone is getting manifest error?
Error: The manifest could not be loaded and may not be valid
@souma_rox
The instructions are as follows:
1. Turn "ON" Developer Unlock Mode. (Go to Settings> Update & Security> For Developers)
2. Download "Root Tool.xap" from attachments and deploy It.
Recommended:
For Lumia:
Open "vcReg" Tool.
Hit the Application Bar and select "Templates".
Here will see two options, Interop/Capability Unlock and "Full File System" Access through the MTP Protocol.
Check your options, and click "Apply".
You are Done !
basically: you run root tools and go to "LUMIA REGISTRY EDITOR". bottom right corner. click the "..." and "TEMPLATES", tick interop unlock + full fs access" and click APPLY. restart. thats it
@onecosmic
try using WP SDK 8.0. Do not use 8.1
oelapoel said:
@souma_rox
The instructions are as follows:
1. Turn "ON" Developer Unlock Mode. (Go to Settings> Update & Security> For Developers)
2. Download "Root Tool.xap" from attachments and deploy It.
Recommended:
For Lumia:
Open "vcReg" Tool.
Hit the Application Bar and select "Templates".
Here will see two options, Interop/Capability Unlock and "Full File System" Access through the MTP Protocol.
Check your options, and click "Apply".
You are Done !
basically: you run root tools and go to "LUMIA REGISTRY EDITOR". bottom right corner. click the "..." and "TEMPLATES", tick interop unlock + full fs access" and click APPLY. restart. thats it
@onecosmic
try using WP SDK 8.0. Do not use 8.1
Click to expand...
Click to collapse
I installed root tool on my lumia 920 but when i tap to "lumia registry editor" it crash!
What i can do?
oelapoel said:
@onecosmic
try using WP SDK 8.0. Do not use 8.1
Click to expand...
Click to collapse
Thanks!
I can confirm - working on Lumia 930 WP build 10512.
ADeltaX said:
I installed root tool on my lumia 920 but when i tap to "lumia registry editor" it crash!
What i can do?
Click to expand...
Click to collapse
Please let me know your firmware version and OS version
What version of 920 do you have?
RM-820/821/822 or chinese type L920T?
ngame said:
Please let me know your firmware version and OS version
What version of 920 do you have?
RM-820/821/822 or chinese type L920T?
Click to expand...
Click to collapse
OS version: 10.0.10512.1000
Firmware: 3051.50009.1451.1009
RM-821
ADeltaX said:
OS version: 10.0.10512.1000
Firmware: 3051.50009.1451.1009
RM-821
Click to expand...
Click to collapse
OK same as my device . I will write a little tool for you .
I took off the file required due to missing registry entrys. will repackage the files needed and upload a new version. stay tuned.
Hey guys, attached is the file required to unlock VoLTE and WiFi-Calling on the Lumia 950DS and Lumia 950 (Att) for T-Mobile. Before attempting these step, you will first unlock Mass Storage mode, using HeathCliff74's method using wpinternals here.
If you need VoLTE and WiFi calling enabled on the Lumia 950XL's take a look at nate0's work here.
Disclaimer: Do this at your own risk. I am not responsible for damage incurred to your mobile device for these modifications. If you have problems, you can always replace the modified file with the originals and then use WDRT to reflash the NVI settings.
Things to Know:
-For the DUAL SIM Models, I turned off the 2nd SIM slot from displaying in the upper left corner as I do not use it. SO DO NOT USE THIS METHOD POSTED HERE IF YOU NEED THE 2ND SIM SLOT WORKING.
-Also, another limitation right now for this method is, the 5GHz Wi-fi Calling in "WIFI ONLY" mode currently does not work, but the 2.4GHz works for now in WiFi ONLY. I am still working on this, but because of school, i haven't had much time to look into this seeing how it's my last semester. The rest of the stuff should work perfectly, Cellular Prefered, Wifi preferred, Wifi Calling OFF with IMS registration, etc...
After successfully unlocking mass storage, boot to mass storage mode and replace the following files with the ones attached in the zip file.
1. Back up the entire ADC folder in \PROGRAMS\CommonFiles
2. Back up the modemconfiguration.cab file in \PROGRAMS\CommonFiles\OEM\Public\MMO\Multivariant
After backing up the files in Steps 1 and 2:
3. Delete the ADC folder in \PROGRAMS\CommonFiles and replace it with the ADC folder from the attached zip file.
4. Copy and replace the modemconfiguration.cab file from \PROGRAMS\CommonFiles\OEM\Public\MMO\Multivariant with the modemconfiguration.cab from the zip file.
5. Copy the MO_VoWiFi_Operator_Name_15818.dll file to \Windows\System32\ folder.
6. Restart the phone out of mass storage and wait for the prompt to restart your phone for a network update.
Thanks to HeathCliff74 for his awesome work with WPInterals and nate0 for findings on the Lumia 950XL's.
Cool. I found a method that worked for this for me on the XL model here. Use what you need from that if you want to make a guide...
So both americans....
nate0 said:
Cool. I found a method that worked for this for me on the XL model here. Use what you need from that if you want to make a guide...
Click to expand...
Click to collapse
Ok, i'll take a look thanks . Quick question thought, when you successfully unlocked VoLTE, when your in a call, did you have to set the HD Voice string manually? because for some reason the HD Voice string variable doesn't show up, even with the ims registration confirmed for the voice call.
anubis23 said:
Ok, i'll take a look thanks . Quick question thought, when you successfully unlocked VoLTE, when your in a call, did you have to set the HD Voice string manually? because for some reason the HD Voice string variable doesn't show up, even with the ims registration confirmed for the voice call.
Click to expand...
Click to collapse
No. It was provisoned already I belive from the ADC files I replaced. That key is burried somewhere in one of those files.
I am curious, how stable is your WiFi calling? VoLTE works flawlessy for me, on occassion I get kicked off of ims registration before a call, but it comes back (probably signal related). But I have it enabled without Wifi calling, meaning the modem file I use does not enable wifi calling... I ask because I could not find the final entries for the nvi file to make VoLTE and WiFi calling both work reliably, at least from my perspective...
nate0 said:
No. It was provisoned already I belive from the ADC files I replaced. That key is burried somewhere in one of those files.
I am curious, how stable is your WiFi calling? VoLTE works flawlessy for me, on occassion I get kicked off of ims registration before a call, but it comes back (probably signal related). But I have it enabled without Wifi calling, meaning the modem file I use does not enable wifi calling... I ask because I could not find the final entries for the nvi file to make VoLTE and WiFi calling both work reliably, at least from my perspective...
Click to expand...
Click to collapse
I haven't been able to extensively test the configuration yet, but I used the mcfg_sw/hw from the Alcatel Idol 4s files to strip out its modem settings, then recreate then in the nvi format. i just finished enabling the volte now im looking into the hd voice string.
anubis23 said:
I haven't been able to extensively test the configuration yet, but I used the mcfg_sw/hw from the Alcatel Idol 4s files to strip out its modem settings, then recreate then in the nvi format. i just finished enabling the volte now im looking into the hd voice string.
Click to expand...
Click to collapse
Ah nice. I used the 640 LTE tmobile nvi files....Yours might be better off since it is built more for W10M...Gonna keep an eye on this thread. Let me know if you need anything.
I have an Idol 4S if you need help. I really wish the 810 would work
Any update? Steps taken? Its great you got it working, but post the deets man!
Sorry about the wait. I uploaded the work that has been done so far. Haven't been able to continue with unlocking the 5ghz in WiFi Only mode because of school schedule so I posted what I have for now. Have fun .
Hi
Talon Pro said:
I have an Idol 4S if you need help. I really wish the 810 would work
Click to expand...
Click to collapse
I have a Lumia 810 but unfortunately, i kind of took it apart for a reason unknown, it was a wonderful phone. It shouldn't be too hard to get WiFi Calling and VoLTE working on it if wpinternals works on it.
anubis23 said:
I have a Lumia 810 but unfortunately, i kind of took it apart for a reason unknown, it was a wonderful phone. It shouldn't be too hard to get WiFi Calling and VoLTE working on it if wpinternals works on it.
Click to expand...
Click to collapse
Problem is, it doesnt do LTE, it has hardly any bands and none that are actually 4G Also, ive never been able to unlock it because i cant find the emergency files (i think its those), but havent tried with the 2.4 version yet.
Ok, so i followed your directions and after rebooting out of mass storage, i get the gears screen over and over and over. I do get the MS start image, but then gears and rebooting again. The progress bar doesnt move on the gear screen though.
@Talon Pro
You can access the full filesystem of the 950 or 950 XL using the sftp method. I have been using that since long before we had mass storage publicly available and it works well. Use swish sftp which integrates in windows explorer and directions from this guide here
In a nut shell:
Gain access to the file systems using Interop Tools app.
- In Interop Tools go the SSH--Account Manager and add an account. The account user name should be System.
- Tap the account System so it is highlighted and then tap templates to use.
- Tap enable full file system access with sftp. Then go to the template options and hit the authentication drop down setting it to password.
- Add the password (4 digit pin of your choice).
- Once your phone is on wifi, add an SFTP Connection under Swish. Set the user to system. Set the path to /c/. Once added double click it, trust the key, and login with the pin you set. Explorer will open with your phones files. The guide above is a bit more detail and additional info on sftp file system access made by snickler if you need.
nate0 said:
@Talon Pro
You can access the full filesystem of the 950 or 950 XL using the sftp method. I have been using that since long before we had mass storage publicly available and it works well. Use swish sftp which integrates in windows explorer and directions from this guide here
In a nut shell:
Gain access to the file systems using Interop Tools app.
- In Interop Tools go the SSH--Account Manager and add an account. The account user name should be System.
- Tap the account System so it is highlighted and then tap templates to use.
- Tap enable full file system access with sftp. Then go to the template options and hit the authentication drop down setting it to password.
- Add the password (4 digit pin of your choice).
- Once your phone is on wifi, add an SFTP Connection under Swish. Set the user to system. Set the path to /c/. Once added double click it, trust the key, and login with the pin you set. Explorer will open with your phones files. The guide above is a bit more detail and additional info on sftp file system access made by snickler if you need.
Click to expand...
Click to collapse
Accessing the files wasnt an issue, but how do i get it out of the boot loop cycle now? WPI cant see it even.
Nvm, i was able to force it into flash mode (up, down and power) and then reboot and WPI saw and grabbed it locked the boot loader and im back into windows and it wants to restart to do the install.
Talon Pro said:
Accessing the files wasnt an issue, but how do i get it out of the boot loop cycle now? WPI cant see it even.
Nvm, i was able to force it into flash mode (up, down and power) and then reboot and WPI saw and grabbed it locked the boot loader and im back into windows and it wants to restart to do the install.
Click to expand...
Click to collapse
There is always a risk to unlocking a boot loader and enabling mass storage mode for Windows phones using Heathcliff74's tools, so it is good to know at least there is alternate way to access the file system on the 950 if we have to.
Now that im back in, neither SIM works at all.
Talon Pro said:
Now that im back in, neither SIM works at all.
Click to expand...
Click to collapse
Hi there, which phone are you currently attempting this on? I remember something similar happened to me. I can try and recreate the problem later today after classes and I'll get back to you. I believe the steps included flashing the CustomerNVI file for the model via thor2 that fixed your issue. If you need your know back working asap, you can always replace the files and then restore the NVI data via thor2:
thor2 -mode uefiflash -ffufile "FFU FIle for your phone.ffu" -do_full_nvi_update -do_factory_reset -skip_flash -reboot
anubis23 said:
Hi there, which phone are you currently attempting this on? I remember something similar happened to me. I can try and recreate the problem later today after classes and I'll get back to you. I believe the steps included flashing the CustomerNVI file for the model via thor2 that fixed your issue. If you need your know back working asap, you can always replace the files and then restore the NVI data via thor2:
thor2 -mode uefiflash -ffufile "FFU FIle for your phone.ffu" -do_full_nvi_update -do_factory_reset -skip_flash -reboot
Click to expand...
Click to collapse
Um, the thread is titled 950DS lol. Its not my main phone so i can deal with waiting a bit for a fix. I just booted it back to Mass Storage so reverse it, but ill wait till you get back to me later.
Any update?