Related
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.
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 have Lumia 720 running with Win10 build 10.0.10586.107
After the latest WA update,whatsapp is not even opening (When I try to open,it instantly closes)
Tried reinstalling -> not worked
Tried cleaning everything from phone/sd (including all my apps) and after this,factory reset -> not worked
Tried with backup enabled/disabled -> not worked
I don't think its possible to reinstall old version,since it'll need to update..
Is there anything I can do to fix this ? Anyone else have this problem ?
Btw,I have full access to the registry/root
I think its a WhatsApp problem. I'm on latest rs build and it also instantly crashes and wont open
Stange, works on my
Lumia 1020 OS 10.0.14905.1000
Lumia 830 OS 10.0.14905.1000
Lumia 950 XL OS 10.0.14393.82
Updated to Win 10.0.14393.67
And it's still not working
Try the beta version,
https://www.microsoft.com/nl-nl/sto...33ea8feddad3fe37825907ec)(270640)(2818683)()()
I fixed it.Formated about 10 times,tried different configs all the times.
Seems like the problem is with the bootloader unlock.
Even if I restore the bootloader,whatsapp doesn't work.
The only way to make it work is factory resetting and never unlock the bootloader.
I was unlocking the bootloader to access the root and enable virtual navigation bar,because my capacitive buttons are not working.
Now I have whatsapp but I don't have the navigation bar,then I cant use it anyways '-'
Btw,I'm using the latest win 10 build (anniversary edition)
--------------
Is there another way to enable the virtual navigation bar using another program ? (already tried interop tools)
My 1020 is bootloader unlocked
GiulioAdriano said:
Is there another way to enable the virtual navigation bar using another program ? (already tried interop tools)
Click to expand...
Click to collapse
Setting this registry value is enough to enable the navigation bar, any registry editing app will do for this:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shell\NavigationBar]
"SoftwareModeEnabled"=dword:00000001
GiulioAdriano said:
I fixed it.Formated about 10 times,tried different configs all the times.
Seems like the problem is with the bootloader unlock.
Even if I restore the bootloader,whatsapp doesn't work.
Click to expand...
Click to collapse
maybe... 5 different Lumia devices (535, 640 LTE, 640 DS, 650, 950XL), no bootloader unlocker or any hack, WhatsApp working fine....
Activated the nav bar using interop tools,without bootloader hack,whatsapp stopped working
GiulioAdriano said:
Activated the nav bar using interop tools,without bootloader hack,whatsapp stopped working
Click to expand...
Click to collapse
Then the Whats App crash is probably caused by the app dimensions being modified by the navigation bar, try starting the app with the navigation bar hidden.
gus33000 said:
Then the Whats App crash is probably caused by the app dimensions being modified by the navigation bar, try starting the app with the navigation bar hidden.
Click to expand...
Click to collapse
Still crashes
Today,when I started the phone (and the SO was still loading),I clicked on whatsapp and it opened and worked normally..but after "minimize" the program,when I went back to whatsapp,it started crashing again..
how to disable virtual soft mode navigation bar
I recently enabled soft mode navigation bar, but UC browser and WhatsApp and many more apps crashed immediately after opening. Then I disabled the virtual bar by using the value changing 1 to 0 in
How to enable-
HKEY_LOCAL_MACHINE /SOFTWARE /Microsoft /Shell /NavigationBar
and create a key called SoftwareModeEnabled of typed dword-integer-32bit sand assigned a VALUE "1".
How to disable- Go to
HKEY_LOCAL_MACHINE /SOFTWARE /Microsoft /Shell /NavigationBar
and change the key called SoftwareModeEnabled of typed dword-integer-32bit sand assigned a VALUE "0" (the change is 1 to 0)
By doing this the nav bar was gone, but apps are crashed like before.
Then I found three keys "isdoubletapoffenabled", "isusermanaged" and "ishintenabled". Don't do anything with "ishintenabled" by changing the value 0 to 1 - it will turn off your WiFi and mobile service (SIM card). It has its own value 0 by default. But the other two keys are usable. Change the two keys (double tap and user managed) from 1 to 0. Restart your phone and then you will able to open all apps like before without any problem and no crashes.✌
GiulioAdriano said:
Today,when I started the phone (and the SO was still loading),I clicked on whatsapp and it opened and worked normally..but after "minimize" the program,when I went back to whatsapp,it started crashing again..
Click to expand...
Click to collapse
crash stopped
Please check if your phone has Android 2.3 or above version. You can check the current version by going into Setting>About Phone.
Regards,
Jane
Author of Techrubik.com
gamerxzone said:
Please check if your phone has Android 2.3 or above version. You can check the current version by going into Setting>About Phone.
Regards,
Jane
Author of Techrubik.com
Click to expand...
Click to collapse
it is for Symbian, I owe Nokia E7
Whatsapp stuck on setting up account
Hello i have a similar problem i have unlocked the bootloader and flashed windows 10 mobile onto my phone. Edited the registery to receive more updates im using a nokia 925. Spoofing as 830. Everything is fine apart from whatsapp. It installs fine i get verification sent but it doesnt finsh setting up my account stays on setting up whatsapp. Ive not tried the beta version yet. Is there a way to edit the registry for whatsapp? If i dont unlock the bootloader i cant update to windows 10 mobile as the phones not supported. The phone runs windows 10 mobile great too even got glance screen working its just whatsapp. Any info would be grateful cheers.
No bootloader unlock required..
allrounder55 said:
Hello i have a similar problem i have unlocked the bootloader and flashed windows 10 mobile onto my phone. Edited the registery to receive more updates im using a nokia 925. Spoofing as 830. Everything is fine apart from whatsapp. It installs fine i get verification sent but it doesnt finsh setting up my account stays on setting up whatsapp. Ive not tried the beta version yet. Is there a way to edit the registry for whatsapp? If i dont unlock the bootloader i cant update to windows 10 mobile as the phones not supported. The phone runs windows 10 mobile great too even got glance screen working its just whatsapp. Any info would be grateful cheers.
Click to expand...
Click to collapse
There's no need for unlocking the bootloader to bring lumia 925 to win10.
I too have a 925 and just used the offline windows 10 packages to update it to windows 10, then used interop tools and updated to the latest build by spoofing the device model no.
And yes.. whatsapp is working well & fine...
Whatsapp problem
maddog78827 said:
There's no need for unlocking the bootloader to bring lumia 925 to win10.
I too have a 925 and just used the offline windows 10 packages to update it to windows 10, then used interop tools and updated to the latest build by spoofing the device model no.
And yes.. whatsapp is working well & fine...
Click to expand...
Click to collapse
Hello the problem i have is quite complicated. A friend of mine has a lumia 925 which i have updated to windows 10 mobile he does not have a microsoft account. we created an account for him which was fine then installed whatsapp on his phone. when we set his account up using his number it sent a verification code to his phone which we typed in. Then asked him to put a name in and a picture if desired. Once we did that we waited for the setup to complete but it wont. I put my details in as i already have a microsoft account and whatsapp worked fine. It seems to be that it doesnt support this phone even when its spoofed. So he cannot install whatsapp to this phone the issue seems to be related to just new accounts which are setup on windows mobile 10. The phone was detected as being synced and added to his account as well, so i am stuck with this ,the only other thing i could do is flash back to 8.1 set his microsoft account up from there then update to windows 10 then try to install whatsapp again. Or would interop tools tweak the registry? So whatsapp could install?
Reset ZenFone 2. Now asking to verify the account but getting "disallowed_useragent"
I was having touch-screen issues so I reset my phone. When I boot now I get prompted for language, wi-fi, etc. Next screen says:
Verify your account
This device was reset. To continue, sign in with a Google Account that was previously synced on this device.
Click to expand...
Click to collapse
The problem is that there's no place to enter any information, just a button "Verify account". When I press the button I get a Google error:
403. That's an error.
Error: disallowed_useragent
Google can't sign you in safely inside this app. You can use Google sign-in by visiting this app's website in a browser like Safari or Chrome.
Click to expand...
Click to collapse
...but I don't know the app and I can't do anything else on the phone. Can anyone provide an answer on how to fix it?
UPDATE:
So the OS version was really old. I went through a series of updates by side-loading the ROMs from the ASUS support site. After 3 or 4 upgrades I had a completely different experience and it let me verify my account. All seems well for now.
Just a couple of notes in case someone else has issues:
- Using Fedora (linux) desktop I needed to use "sudo ./adb devices" to be able to start the server and perform the side-load. Without "sudo" I was receiving an error about permissions.
- I performed the upgrades starting with the kernel version that was already on the phone and then upgraded to the next release each time after booting to each upgrade. I did this because I received an error on one upgrade saying I couldn't go there directly.
Peace.
I have the exact same issue with a phone that I'm trying to setup for my kid. Where did you get your firmwares for this phone?
Start by going here: https://icr-am.asus.com/webchat/icr...634.649586617.1546133606-337662955.1546133606
Then select "Download Center" from the chat window pane. Select your specific phone model. Select BIOS & FIRMWARE. Be sure to select the correct version for your phone (WW, CN, JP, etc.)
Good luck!
HI all. Keep in mind that I did my first root and install of Magisk this week for some gaming desires. I am a bit of a noob, but I had a blast learning about rooting. I was also encouraged because everything went pretty well and only took me around an hour.
Then I ran into a wall.
I use my Pixel 6 Pro to attend work meetings and track work form home or in my car. I had really grown to need this feature so I was a bit worried that I would have to reverse the root. So for the last 2-3 days I have been using trial and error and guides on how to hide banking apps. I saw so many threads that never resolved the teams issue or missed steps that I thought I would write up a detailed guide for what worked for me.
Keep in mind this is for Android 13 and a Google Pixel 6 Pro. This assumes you Rooted your phone and have latest Magisk installed as well.
Prep:
1. Go to Google Play Store settings and turn off automatic updating. I'm sure most people who use magisk do this anyway.
2. Go here https://en.uptodown.com/android/browsing and download older versions of Teams and Company portal. Not too old. You want something from just 2-3 months ago. If it is too old the phone won't let you install it but will put files on your phone that already know you're rooted.
3. Make sure you have the latest Universal Safty fix. You can run a scan to show if you meet the safety fix standard. Again I think the problem isn't safty fix so much as Company portal looks for an unlocked boot loader.
4. install Mgiskhide Props Config module and Android terminal from the play store. (You do this to put a legit looking device ID, or non unlocked bootloader ID - just encase your phone doesn't work, or has been previously detected). Its a simple process where you input some number options through android terminal to set the ID. Just follow the steps. AND MAKE SURE YOU DELETE TERMINAL AFTER YOU'RE DONE. They look for that.
GitHub - Magisk-Modules-Repo/MagiskHidePropsConf: This tool is now dead...
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
5. Use Magisk hide and rename Magisk to MYJOBSUCKS
Action:
1. install Shamiko https://github.com/LSPosed/LSPosed.github.io/releases/tag/shamiko-120
2. Reboot.
3. Make sure Zygisk is enabled.
4. Make sure Enforce Denylist is OFF (This seems nonsensical but Shamiko handles the enforcement now that it's installed. The Zygisk enforcement is a conflict.)
5. Go back and install Company portal and Teams. Don't do anything in either. Don't sign in. Don't configure. Don't open the apps.
6. Go back to Zygisk and open Configure Denylist. This, I feel, is the MOST important step that makes or breaks this process. Do the following in Denylist:
MAKE SURE YOU TOGGLE EVERYTHING not just the default hides. Each hide has a submenu and for sub processes to hide.
This is everything I had to deny to make it work:
Authenticator.
Carrier OMADM
Carrier provision service
Carrier services
Certificate installer
Com.andorid.angle
Companion device manager
device health service adaptor
device policy
Gpay
OemDMTrigger
Permission controller
TEAMS
Work setup
Company portal
Google play protect services
Google Play Store
*** I Believes the bottom 5 are the main ones - the rest I just guessed and may or may not impact things 100% *****
7. Sign into Teams.
8. This will force you to sign into Company portal. If it works - not much will happen because it will look like a legit non-rooted phone.
If it fails you'll have to setup your profile in Company portal and it always fails after a 5 step process and says DEVICE NOT HEALTHY) This means you didn't deny something or you didn't reboot or something. You also need to go into your google accounts and look for your work profile and delete it and uninstall teams and company portal - I think company portal leaves files that you want off so you have to start from scratch)
9. You should be able to join your work meetings and use teams.
Ongoing:
Make sure you never update teams or Company Portal.
I don't know if this works for other MS mobile apps because I don't check my mail on my phone - but I assume just adding them to the deny list would be the only step extra you need to take.
Thanks!!
For me it works without props config and with the latest version of MS Teams and the Intune portal app. Use Shamiko (latest), configure denylist but don't enable denylist in Magisk. Magisk is hidden (some banking app which I use checks the Magisk package name).
Guzzlor said:
HI all. Keep in mind that I did my first root and install of Magisk this week for some gaming desires. I am a bit of a noob, but I had a blast learning about rooting. I was also encouraged because everything went pretty well and only took me around an hour.
Then I ran into a wall.
I use my Pixel 6 Pro to attend work meetings and track work form home or in my car. I had really grown to need this feature so I was a bit worried that I would have to reverse the root. So for the last 2-3 days I have been using trial and error and guides on how to hide banking apps. I saw so many threads that never resolved the teams issue or missed steps that I thought I would write up a detailed guide for what worked for me.
Keep in mind this is for Android 13 and a Google Pixel 6 Pro. This assumes you Rooted your phone and have latest Magisk installed as well.
Prep:
1. Go to Google Play Store settings and turn off automatic updating. I'm sure most people who use magisk do this anyway.
2. Go here https://en.uptodown.com/android/browsing and download older versions of Teams and Company portal. Not too old. You want something from just 2-3 months ago. If it is too old the phone won't let you install it but will put files on your phone that already know you're rooted.
3. Make sure you have the latest Universal Safty fix. You can run a scan to show if you meet the safety fix standard. Again I think the problem isn't safty fix so much as Company portal looks for an unlocked boot loader.
4. install Mgiskhide Props Config module and Android terminal from the play store. (You do this to put a legit looking device ID, or non unlocked bootloader ID - just encase your phone doesn't work, or has been previously detected). Its a simple process where you input some number options through android terminal to set the ID. Just follow the steps. AND MAKE SURE YOU DELETE TERMINAL AFTER YOU'RE DONE. They look for that.
GitHub - Magisk-Modules-Repo/MagiskHidePropsConf: This tool is now dead...
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
5. Use Magisk hide and rename Magisk to MYJOBSUCKS
Action:
1. install Shamiko https://github.com/LSPosed/LSPosed.github.io/releases/tag/shamiko-120
2. Reboot.
3. Make sure Zygisk is enabled.
4. Make sure Enforce Denylist is OFF (This seems nonsensical but Shamiko handles the enforcement now that it's installed. The Zygisk enforcement is a conflict.)
5. Go back and install Company portal and Teams. Don't do anything in either. Don't sign in. Don't configure. Don't open the apps.
6. Go back to Zygisk and open Configure Denylist. This, I feel, is the MOST important step that makes or breaks this process. Do the following in Denylist:
MAKE SURE YOU TOGGLE EVERYTHING not just the default hides. Each hide has a submenu and for sub processes to hide.
This is everything I had to deny to make it work:
Authenticator.
Carrier OMADM
Carrier provision service
Carrier services
Certificate installer
Com.andorid.angle
Companion device manager
device health service adaptor
device policy
Gpay
OemDMTrigger
Permission controller
TEAMS
Work setup
Company portal
Google play protect services
Google Play Store
*** I Believes the bottom 5 are the main ones - the rest I just guessed and may or may not impact things 100% *****
7. Sign into Teams.
8. This will force you to sign into Company portal. If it works - not much will happen because it will look like a legit non-rooted phone.
If it fails you'll have to setup your profile in Company portal and it always fails after a 5 step process and says DEVICE NOT HEALTHY) This means you didn't deny something or you didn't reboot or something. You also need to go into your google accounts and look for your work profile and delete it and uninstall teams and company portal - I think company portal leaves files that you want off so you have to start from scratch)
9. You should be able to join your work meetings and use teams.
Ongoing:
Make sure you never update teams or Company Portal.
I don't know if this works for other MS mobile apps because I don't check my mail on my phone - but I assume just adding them to the deny list would be the only step extra you need to take.
Thanks!!
Click to expand...
Click to collapse
This solve my problem with my bank app thank you so much...!!!
foobar66 said:
For me it works without props config and with the latest version of MS Teams and the Intune portal app. Use Shamiko (latest), configure denylist but don't enable denylist in Magisk. Magisk is hidden (some banking app which I use checks the Magisk package name).
Click to expand...
Click to collapse
I'm not sure what was wrong but simply doing those steps did not work for me. I had to start from scratch and that's why I wrote all this up.
Guzzlor said:
HI all. Keep in mind that I did my first root and install of Magisk this week for some gaming desires. I am a bit of a noob, but I had a blast learning about rooting. I was also encouraged because everything went pretty well and only took me around an hour.
Then I ran into a wall.
I use my Pixel 6 Pro to attend work meetings and track work form home or in my car. I had really grown to need this feature so I was a bit worried that I would have to reverse the root. So for the last 2-3 days I have been using trial and error and guides on how to hide banking apps. I saw so many threads that never resolved the teams issue or missed steps that I thought I would write up a detailed guide for what worked for me.
Keep in mind this is for Android 13 and a Google Pixel 6 Pro. This assumes you Rooted your phone and have latest Magisk installed as well.
Prep:
1. Go to Google Play Store settings and turn off automatic updating. I'm sure most people who use magisk do this anyway.
2. Go here https://en.uptodown.com/android/browsing and download older versions of Teams and Company portal. Not too old. You want something from just 2-3 months ago. If it is too old the phone won't let you install it but will put files on your phone that already know you're rooted.
3. Make sure you have the latest Universal Safty fix. You can run a scan to show if you meet the safety fix standard. Again I think the problem isn't safty fix so much as Company portal looks for an unlocked boot loader.
4. install Mgiskhide Props Config module and Android terminal from the play store. (You do this to put a legit looking device ID, or non unlocked bootloader ID - just encase your phone doesn't work, or has been previously detected). Its a simple process where you input some number options through android terminal to set the ID. Just follow the steps. AND MAKE SURE YOU DELETE TERMINAL AFTER YOU'RE DONE. They look for that.
GitHub - Magisk-Modules-Repo/MagiskHidePropsConf: This tool is now dead...
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
5. Use Magisk hide and rename Magisk to MYJOBSUCKS
Action:
1. install Shamiko https://github.com/LSPosed/LSPosed.github.io/releases/tag/shamiko-120
2. Reboot.
3. Make sure Zygisk is enabled.
4. Make sure Enforce Denylist is OFF (This seems nonsensical but Shamiko handles the enforcement now that it's installed. The Zygisk enforcement is a conflict.)
5. Go back and install Company portal and Teams. Don't do anything in either. Don't sign in. Don't configure. Don't open the apps.
6. Go back to Zygisk and open Configure Denylist. This, I feel, is the MOST important step that makes or breaks this process. Do the following in Denylist:
MAKE SURE YOU TOGGLE EVERYTHING not just the default hides. Each hide has a submenu and for sub processes to hide.
This is everything I had to deny to make it work:
Authenticator.
Carrier OMADM
Carrier provision service
Carrier services
Certificate installer
Com.andorid.angle
Companion device manager
device health service adaptor
device policy
Gpay
OemDMTrigger
Permission controller
TEAMS
Work setup
Company portal
Google play protect services
Google Play Store
*** I Believes the bottom 5 are the main ones - the rest I just guessed and may or may not impact things 100% *****
7. Sign into Teams.
8. This will force you to sign into Company portal. If it works - not much will happen because it will look like a legit non-rooted phone.
If it fails you'll have to setup your profile in Company portal and it always fails after a 5 step process and says DEVICE NOT HEALTHY) This means you didn't deny something or you didn't reboot or something. You also need to go into your google accounts and look for your work profile and delete it and uninstall teams and company portal - I think company portal leaves files that you want off so you have to start from scratch)
9. You should be able to join your work meetings and use teams.
Ongoing:
Make sure you never update teams or Company Portal.
I don't know if this works for other MS mobile apps because I don't check my mail on my phone - but I assume just adding them to the deny list would be the only step extra you need to take.
Thanks!!
Click to expand...
Click to collapse
Awesome! This is the only method that worked for me after hours of struggling. Thank you!
Method is not working for me. Followed all steps
Not worked for me. Intune still detecting the root
Harshatxda said:
Not worked for me. Intune still detecting the root
Click to expand...
Click to collapse
Harshatxda said:
Method is not working for me. Followed all steps
Click to expand...
Click to collapse
This seems to be an ongoing evolving issue; especially in light of recent updates/events. There are many threads on the site here discussing it, although I've seen some that have been successful (but in various different device forums). The thread (linked below) seems to be fairly up-to-date recently updated that looks most promising...
[Tutorial] [Root] How to configure 'Microsoft Intune' to make it work with 'Magisk' (Update: Q1/2023)
Update 04.01.2023: I've updated/added additional steps to make this tutorial work again. This question was asked many times and often all the answers did not work: How do I get Magisk to work with Microsoft Apps like Microsoft Teams, Microsoft...
forum.xda-developers.com
Rooted Pixel 6A, rooted and literally <24H out of box. All I did was:
1. Hide Magisk (obviously)
2. Enable Zygisk
3. Configure DenyList (every Microsoft app I saw)
4. Enforce DenyList
5. Reboot
Portal passes device health test, and Teams works like a charm. Both are installed straight from Play Store.