New Whatsapp not working on Lumia 720 (Win10M) - Windows 10 Mobile

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?

Related

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

I've been following on the Mango upgrades and whatnot, since I just recently upgraded my Samsung Focus to Mango. However, I have yet to see a way to pass ChevronWP7 to a Samsung WP7. I know with LGs you can use the MFG regedit, and with HTCs you can use this xml method found here:
http://forum.xda-developers.com/showthread.php?t=1101344
Is anyone anywhere working on a way to pass ChevronWP7 from NoDo to Mango on a Samsung device? I just want some confirmation, because I'd love to use Mango to it's fullest extent. Thanks guys!
VenezuelaDan said:
I've been following on the Mango upgrades and whatnot, since I just recently upgraded my Samsung Focus to Mango. However, I have yet to see a way to pass ChevronWP7 to a Samsung WP7. I know with LGs you can use the MFG regedit, and with HTCs you can use this xml method found here:
http://forum.xda-developers.com/showthread.php?t=1101344
Is anyone anywhere working on a way to pass ChevronWP7 from NoDo to Mango on a Samsung device? I just want some confirmation, because I'd love to use Mango to it's fullest extent. Thanks guys!
Click to expand...
Click to collapse
can you please provide us with a guide or the steps you used to upgrade your focus
i checked several threads here, but was unable to upgrade & kept getting an error message: " no devices were found"
I made this post here: http://forum.xda-developers.com/showpost.php?p=15329491&postcount=5
Your device needs to already be dev unlocked and in NODO!!
Someone else has confirmed that you need diagnosis version is 1122.
1. Make a backup of your device. You can use my app for that if you wish: http://forum.xda-developers.com/showthread.php?t=1103011
1.1 - Make a backup
1.2 - Make a backup
1.3 - Make a backup!!!!
Get the point? you CAN NOT get the official Mango update when its released without reverting to NODO so MAKE A DAMN BACKUP! I personally have 4 backups just in case!
2. I installed this unlock.xml: http://forum.xda-developers.com/showpost.php?p=15316160&postcount=9
3. Install WP7 Root Toosl by Heathcliff .5 alpha from his thread: http://forum.xda-developers.com/showthread.php?t=1021135
4. Load the root tools and using the explorer create a directory called provxml in the root of the drive if it doesnt already exist.
5. Using the root tools copy unlock.xml file from: Applications\Install\D19A80F2-1717..... (you may have to browse folders in that path) to the provxml folder at the root of the device. (I apologize but I don't know the exact path I believe it starts in the root but I would have to revert to nodo to know for sure as the root tools don't work in mango.
6. *OPTIONAL TEST* Once that file is there you can test it to be sure it works like I did by changing one of the unlock reg keys and applying the XML to confirm it changes back. I used the root tools registry editor part to browse to: "HKLM\Software\Microsoft\DeviceReg" I changed the value "PortalUrlProd" by adding random text as it should be clear/empty/null. Then I applied the xml by going to the diagnosis tools from my shortcut or by going to the phone app and then the keypad and typing: ##634#. Once in Diagnosis enter: *#9908# to get to the GPRS profiles. Tap the dropdown and you should see unlock in your list. Select unlock and then save at the bottom. It only takes a second and says success in the window below the dropdown. Now exit diagnosis and use the root tools again to confirm the registry value you set before is now cleared/empty/null. If that works you can proceed with confidence.
7. Perform the 2 step mango update from this link: http://windowsphonehacker.com/articles/get_the_mango_update_now._without_being_a_developer.-06-30-11
8. Once updated and in mango apply the xml by: going to the diagnosis tools from a shortcut or by going to the phone app and then the keypad and typing: ##634#. Once in Diagnosis enter: *#9908# to get to the GPRS profiles. Tap the dropdown and you should see unlock in your list. Select unlock and then save at the bottom. It only takes a second and says success in the window below the dropdown. Again diagnosis version 1122 is needed for this to work.
One word of warning. I had to reconfigure the APN to get network to work but I still couldnt receive MMS. So in the end I read that to get it set up you have to reset the phone and let the configuration steps set up network profile. I wasnt about to do that so I called AT&T and said I was going to another country and needed my unlock code to put a sim card in from there and they gave it to me. They said I needed another carrier SIM to input it. Instead I went to diagnosis and entered: #7465625*638*# That brought me to the Network Lock screen. I made sure disabled was checked and entered the unlock code they gave me on the phone in the NCK section and tapped execute. That unlocked my phone which let me use the samsung network profile tool available form the samsung marketplace (only on phone) to select the ATT (not AT&T) profile. Actually I toggled to AT&T then back to ATT and everything worked!
Yup.... What he said!!!
Mango on my Focus is awesome. I didn't do the unlock though because that tutorial came after I upgraded to mango. Now I'm too scared to do it again. And frankly, the whole process takes forever. In the end, it's worth it!!! I just need a working registry editor now because I'm back to that stupid 16-bit colors!!! I hate it.
It's not necessary to make a back-up if you just don't care about the data. Simply install an OEM ROM from the carrier of your choice on the Samsung Focus. I have several phones and just figured *meh* who cares - I'll reinstall the apps I want and just lose my game saves (please let cloud game saves come to WP7 soon!!)
This of course doesn't address the unlock issue. My hope is soon we get a non-branded ROM for the Samsung Focus sooner rather than later so I can finally resolve the MMS issues.
As far as unlocking I have given up for the time being. May just buy a Chevron unlock...
I'm not having MMS issues on mine. Just the damn 16-bit color limit. All the gradients are chopped. I want the 24-bit back. It's just a small registry hack! Why can't samsung or AT&T update it.
pdangcil said:
I'm not having MMS issues on mine. Just the damn 16-bit color limit. All the gradients are chopped. I want the 24-bit back. It's just a small registry hack! Why can't samsung or AT&T update it.
Click to expand...
Click to collapse
Odd I havent tested it with the diag screen but I still occassionaly get the "Red screen" on boot up which is a symptom of the color change hack.
pdangcil said:
Yup.... What he said!!!
Mango on my Focus is awesome. I didn't do the unlock though because that tutorial came after I upgraded to mango. Now I'm too scared to do it again. And frankly, the whole process takes forever. In the end, it's worth it!!! I just need a working registry editor now because I'm back to that stupid 16-bit colors!!! I hate it.
Click to expand...
Click to collapse
Too scared? Bah! I have done it 4 times with no problems and I have 4 backups of my phone pre-mango so whats to be scared of?
Get At&T settings back the easy way
Instead of going through the pain with At&T this will fix the AT&T settings after you are done wit the unlock. from the diagnosis app
g_AutoSimSetting : 40*047#3, *#94765#
sandrobber said:
Instead of going through the pain with At&T this will fix the AT&T settings after you are done wit the unlock. from the diagnosis app
g_AutoSimSetting : 40*047#3, *#94765#
Click to expand...
Click to collapse
Interesting... so it disables then re-enables the auto-sim setting? Should we do the reboot in the middle that it asks for?
hx4700 Killer said:
I made this post here: http://forum.xda-developers.com/showpost.php?p=15329491&postcount=5
Your device needs to already be dev unlocked and in NODO!!
Also I don't know if it is required but my diagnosis version is 1122.
1. Make a backup of your device. You can use my app for that if you wish: http://forum.xda-developers.com/showthread.php?t=1103011
1.1 - Make a backup
1.2 - Make a backup
1.3 - Make a backup!!!!
Get the point? you CAN NOT get the official Mango update when its released without reverting to NODO so MAKE A DAMN BACKUP! I personally have 4 backups just in case!
2. I installed this unlock.xml: http://forum.xda-developers.com/showpost.php?p=15316160&postcount=9
3. Install WP7 Root Toosl by Heathcliff .5 alpha from his thread: http://forum.xda-developers.com/showthread.php?t=1021135
4. Load the root tools and using the explorer create a directory called provxml in the root of the drive if it doesnt already exist.
5. Using the root tools copy unlock.xml file from: Applications\Install\D19A80F2-1717..... (you may have to browse folders in that path) to the provxml folder at the root of the device. (I apologize but I don't know the exact path I believe it starts in the root but I would have to revert to nodo to know for sure as the root tools don't work in mango.
6. *OPTIONAL TEST* Once that file is there you can test it to be sure it works like I did by changing one of the unlock reg keys and applying the XML to confirm it changes back. I used the root tools registry editor part to browse to: "HKLM\Software\Microsoft\DeviceReg" I changed the value "PortalUrlProd" by adding random text as it should be clear/empty/null. Then I applied the xml by going to the diagnosis tools from my shortcut or by going to the phone app and then the keypad and typing: ##634#. Once in Diagnosis enter: *#9908# to get to the GPRS profiles. Tap the dropdown and you should see unlock in your list. Select unlock and then save at the bottom. It only takes a second and says success in the window below the dropdown. Now exit diagnosis and use the root tools again to confirm the registry value you set before is now cleared/empty/null. If that works you can proceed with confidence.
7. Perform the 2 step mango update from this link: http://windowsphonehacker.com/articles/get_the_mango_update_now._without_being_a_developer.-06-30-11
8. Once updated and in mango apply the xml by: going to the diagnosis tools from a shortcut or by going to the phone app and then the keypad and typing: ##634#. Once in Diagnosis enter: *#9908# to get to the GPRS profiles. Tap the dropdown and you should see unlock in your list. Select unlock and then save at the bottom. It only takes a second and says success in the window below the dropdown. I had diagnosis version 1122 so I don't know if that is needed for this to work or not.
One word of warning. I had to reconfigure the APN to get network to work but I still couldnt receive MMS. So in the end I read that to get it set up you have to reset the phone and let the configuration steps set up network profile. I wasnt about to do that so I called AT&T and said I was going to another country and needed my unlock code to put a sim card in from there and they gave it to me. They said I needed another carrier SIM to input it. Instead I went to diagnosis and entered: #7465625*638*# That brought me to the Network Lock screen. I made sure disabled was checked and entered the unlock code they gave me on the phone in the NCK section and tapped execute. That unlocked my phone which let me use the samsung network profile tool available form the samsung marketplace (only on phone) to select the ATT (not AT&T) profile. Actually I toggled to AT&T then back to ATT and everything worked!
Click to expand...
Click to collapse
Thank you very much
worked wondefully
3G data internet was not working at first but works great after manually choosing ATT from network profile app
MMS issues don't exist anymore if you install the Samsung Tools XAP. Even if you upgrade to Mango after, some remnants remain from the unlock, and one of those is the expanded MMS settings this tool gives (my phone is locked after mango because I didnt do this hack, but my MMS, 3G, and custom live tile colors still work....)
hx4700 Killer said:
I made this post here: http://forum.xda-developers.com/showpost.php?p=15329491&postcount=5
Your device needs to already be dev unlocked and in NODO!!
Also I don't know if it is required but my diagnosis version is 1122.
1. Make a backup of your device. You can use my app for that if you wish: http://forum.xda-developers.com/showthread.php?t=1103011
1.1 - Make a backup
1.2 - Make a backup
1.3 - Make a backup!!!!
Get the point? you CAN NOT get the official Mango update when its released without reverting to NODO so MAKE A DAMN BACKUP! I personally have 4 backups just in case!
2. I installed this unlock.xml: http://forum.xda-developers.com/showpost.php?p=15316160&postcount=9
3. Install WP7 Root Toosl by Heathcliff .5 alpha from his thread: http://forum.xda-developers.com/showthread.php?t=1021135
4. Load the root tools and using the explorer create a directory called provxml in the root of the drive if it doesnt already exist.
5. Using the root tools copy unlock.xml file from: Applications\Install\D19A80F2-1717..... (you may have to browse folders in that path) to the provxml folder at the root of the device. (I apologize but I don't know the exact path I believe it starts in the root but I would have to revert to nodo to know for sure as the root tools don't work in mango.
6. *OPTIONAL TEST* Once that file is there you can test it to be sure it works like I did by changing one of the unlock reg keys and applying the XML to confirm it changes back. I used the root tools registry editor part to browse to: "HKLM\Software\Microsoft\DeviceReg" I changed the value "PortalUrlProd" by adding random text as it should be clear/empty/null. Then I applied the xml by going to the diagnosis tools from my shortcut or by going to the phone app and then the keypad and typing: ##634#. Once in Diagnosis enter: *#9908# to get to the GPRS profiles. Tap the dropdown and you should see unlock in your list. Select unlock and then save at the bottom. It only takes a second and says success in the window below the dropdown. Now exit diagnosis and use the root tools again to confirm the registry value you set before is now cleared/empty/null. If that works you can proceed with confidence.
7. Perform the 2 step mango update from this link: http://windowsphonehacker.com/articles/get_the_mango_update_now._without_being_a_developer.-06-30-11
8. Once updated and in mango apply the xml by: going to the diagnosis tools from a shortcut or by going to the phone app and then the keypad and typing: ##634#. Once in Diagnosis enter: *#9908# to get to the GPRS profiles. Tap the dropdown and you should see unlock in your list. Select unlock and then save at the bottom. It only takes a second and says success in the window below the dropdown. I had diagnosis version 1122 so I don't know if that is needed for this to work or not.
One word of warning. I had to reconfigure the APN to get network to work but I still couldnt receive MMS. So in the end I read that to get it set up you have to reset the phone and let the configuration steps set up network profile. I wasnt about to do that so I called AT&T and said I was going to another country and needed my unlock code to put a sim card in from there and they gave it to me. They said I needed another carrier SIM to input it. Instead I went to diagnosis and entered: #7465625*638*# That brought me to the Network Lock screen. I made sure disabled was checked and entered the unlock code they gave me on the phone in the NCK section and tapped execute. That unlocked my phone which let me use the samsung network profile tool available form the samsung marketplace (only on phone) to select the ATT (not AT&T) profile. Actually I toggled to AT&T then back to ATT and everything worked!
Click to expand...
Click to collapse
One important observation:
Diagnose v922 does NOT see Unlock.xml , thus you can't apply the GPRS profile. You need to update to v1122.
To get Diagnose v1122, you need to re-brand your phone back to the original carrier. In my case it was:
HKLM\System\Platform\DeviceTargetingInfo\MobileOperator = "ATT-US"
After that, I got a Samsung update (updated radio+sw) in Zune, and with it I also got the diagnose v1122.
If you still get Diagnose v922 after the "Samsung Update", then delete Diagnose app and run *#634# and Diagnose will be updated.
Another word of warning.
This is a BETA Mango update.
I just tried it and my Focus and after the update it got stuck at Samsung logo. However, it can be fixed, read my post here.
Might have to do with SD card I use (16 GB Class 2) but I doubt it as I didn't have any issues in over 5 months, updates 7004 to 7392.
Upgraded a Focus once and then got locked out. Updated again and when I do the Diagnosis then *#9908# and select unlock, it says Loading GPRS Profile for unlockProvision and then nothing. Same happened with the last upgrade so now I worried that I'm only a little time away from getting locked again.
Deano69 said:
Upgraded a Focus once and then got locked out. Updated again and when I do the Diagnosis then *#9908# and select unlock, it says Loading GPRS Profile for unlockProvision and then nothing. Same happened with the last upgrade so now I worried that I'm only a little time away from getting locked again.
Click to expand...
Click to collapse
I think it worked. I did the extra step 6, and I've tested with the "PortalUrlProd" value before the actual update and it was reset. Same as you, I got the "Loading GPRS profile..." message and nothing else. But it worked.
EnderPsp said:
Another word of warning.
This is a BETA Mango update.
I just tried it and my Focus and after the update it got stuck at Samsung logo. However, it can be fixed, read my post here.
Might have to do with SD card I use (16 GB Class 2) but I doubt it as I didn't have any issues in over 5 months, updates 7004 to 7392.
Click to expand...
Click to collapse
I have a 16GB Sandisk Class 2 memory card in my focus and it works fine. I had read that diag 1122 *might* be needed but wasnt sure until now
hx4700 Killer said:
I have a 16GB Sandisk Class 2 memory card in my focus and it works fine. I had read that diag 1122 *might* be needed but wasnt sure until now
Click to expand...
Click to collapse
Btw, can someone make a xap with Diagnose 1122, please? Rogers firmware doesn't seem to get the "Samsung Update" that installs v1122, and I'm stuck with default v927... Or give any pointers how to get the new Diagnose
I'm pretty sure that if I flash the AT&T fw I'll get v1122, but I like Rogers rom better (mine is originally an AT&T Focus).
EnderPsp said:
Btw, can someone make a xap with Diagnose 1122, please? Rogers firmware doesn't seem to get the "Samsung Update" that installs v1122, and I'm stuck with default v927... Or give any pointers how to get the new Diagnose
I'm pretty sure that if I flash the AT&T fw I'll get v1122, but I like Rogers rom better (mine is originally an AT&T Focus).
Click to expand...
Click to collapse
I got it somewhere else on here, didnt need it though:
Is there any way to get the updated diagnosis app on Omnia 7? (Optus Australia, build 7392)
That XAP won't allow me to sideload for some reason, and even if it did, that won't help me after I get into Mango.

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

Hello all,
I just wanna share a tutorial on how to restore glance screen on Windows 10 Redstone for older devices. I made this tutorial because there are so many people asking how to restore glance functionality after they update their device to Redstone. There are some guides on it but they are really hard to find. There is even an option to enable old glance screen on Gustav's Interop Tools but lot of people don't know how to use it
This tutorial is based on what I always did to restore the glance screen on my Lumia 920. Make sure that your device had glance screen feature when it was on Windows Phone. Otherwise, this trick wouldn't work. Follow this tutorial on your own risk. I'm not responsible for any damage caused to your device.
Part 1: Install Interop Tools & Glance Screen APPX
On your PC, Download the latest version of Interop Tools from https://forum.xda-developers.com/windows-10-mobile/windows-10-mobile-apps-and-games/app-interop-tools-versatile-registry-t3445271 and the attached glancescreen_appx.zip. Put all the APPXs (including dependencies) on your phone storage (e.g. Download folder)
On your phone. go to Settings > Update & security > For developers
Turn on Developer mode, Device Discovery and Device Portal
Open Microsoft Edge, and go to http://127.0.0.1/ to open Device Portal (it is possible to do this using your PC via WiFi but it'll be slower since the APPXs need to be transfered via WiFi)
If there is a certificate error, ignore it and click Continue to this webpage
You might be asked to authenticate. Go to the previous developer settings and click Pair button
On the Device Portal, Click Apps on the left sidebar
Install all Interop Tools dependencies ONE BY ONE. After that, install the main Interop Tools APPX
Install glancescreen.appx
Turn off Device Discovery and Device Portal on the developer settings
Part 2: Restore Missing Glance Files & Registry
Open Interop Tools > This Device. Open sidebar, choose Interop Unlock
Check Restore NDTKSvc and restart your device (on some occasions, the other option can't be turned on until you restart your device)
Open Interop Tools > This Device > Interop Unlock. Check Full Filesystem Access and restart your device once more (some folders can't be seen until you restart the device)
Connect your device to your PC via USB
On your PC, download the attached missing_glance_files.zip and put them on [Your Phone]\Data\SharedData\OEM\Public\ using Windows Explorer
Open Interop Tools and turn off Full Filesystem Access
Open sidebar, choose Tweaks
Scroll down and turn on Enable Old Glance Screen (RS1)
Part 3: Fix Glance Font (Non-WXGA devices only)
Open Settings > System > About. Click More info button and check your device Screen resolution
If it's 768x1280 (WXGA), jump to part 4. Otherwise, open Interop Tools > This Device. Open sidebar, choose Registry Browser
Navigate to HKLM\Software\OEM\Nokia\lpm\FontFile
If your device screen resolution is 480x800 (WVGA), replace lpmFont_WXGA.bin with lpmFont_WVGA.bin. For other resolutions, you might wanna check out the other fonts inside lpmFonts_4.1.12.4 folder in the attached missing_glance_files.zip
Part 4: Update Glance Screen
Open Store. Open sidebar, choose Downloads and updates
Click Check for updates and update Glance Screen
Restart your device
Miscellaneous
How to Fix MTP Root Path to Deactivate Full Filesystem Access
How to Increase Glance Font to Fit Device Screen Like on Windows Phone
I hope this tutorial helps. Goodluck!
hi
thank you.
can you help me for change glance font size for this method?
Arshen said:
hi
thank you.
can you help me for change glance font size for this method?
Click to expand...
Click to collapse
Is it too small? If so, follow the steps below...
How to Increase Glance Font to Fit Device Screen Like on Windows Phone
The glance font on Windows Phone is bigger than on Windows 10 Mobile so that the text fits the device screen. I actually prefer the smaller font size because that's how the glance screen displayed on the new devices and it looks more elegant. But if you still want to increase the font size, here's the steps...
Open Interop Tools > This Device. Open sidebar, choose Registry Browser
Navigate to HKLM\Software\OEM\Nokia\lpm\FontFile
Replace \Data\SharedData\OEM\Public\lpmFonts_4.1.12.4\ with \Windows\system32\
Write the change
AWasisto said:
Is it too small? If so, follow the steps below...
How to Increase Glance Screen Font
The glance font on Windows Phone 8.1 is bigger than on Windows 10 Mobile. I actually prefer the smaller font size because that's how the glance screen displayed on Lumia 950 and it looks more elegant. But if you want to increase the font size, here's the steps
Open Interop Tools > This Device. Open sidebar, choose Registry Browser
Navigate to HKLM\Software\OEM\Nokia\lpm\FontFile
Change the value to \Windows\system32\lpmFont_WXGA.bin
Write the change
To restore the default W10M glance font, change the value to \Data\SharedData\OEM\Public\lpmFonts_4.1.12.4\lpmFont_wxga.bin
Click to expand...
Click to collapse
i want to make glance screen font small!
how can i do this?
Arshen said:
i want to make glance screen font small!
how can i do this?
Click to expand...
Click to collapse
Try this value: \Data\SharedData\OEM\Public\lpmFonts_4.1.12.4\lpmFont_720p_hi.bin
You can try lpmFont_720p.bin or lpmFont_wvga.bin if it's not small enough. lpmFont_720p_hi.bin > lpmFont_720p.bin > lpmFont_wvga.bin
Does anyone have a problem with the MTP after turning off full filesystem access?
Arshen said:
i want to make glance screen font small!
how can i do this?
Click to expand...
Click to collapse
this worked for me on my Lumia 810
https://forum.xda-developers.com/windows-10-mobile/glance-screen-original-files-lumia-820-t3463740
will it really work on unsupported devices which does not support glance , because MS said its a Hardware feature ?
TulakChoco said:
this worked for me on my Lumia 810
https://forum.xda-developers.com/windows-10-mobile/glance-screen-original-files-lumia-820-t3463740
Click to expand...
Click to collapse
Whoa I've just realized the font needs to be changed for WVGA devices. Thanks! Tutorial updated
adityashingade said:
will it really work on unsupported devices which does not support glance , because MS said its a Hardware feature ?
Click to expand...
Click to collapse
If glance screen was available on the device while it's on Windows Phone, then it would work. Otherwise, nope, I don't think so
thanks, working on my 920.
On my 1020 worked yeah but after while screen goes crazy and nightmode when time change place to up its fuked. 15014 not worked even soft reset or what ever. 15007 worked while after glance installed.
So last 2 fast updates (15007 and 15014) glance not working anymore what ever you do. Not trying to install anymore glance and phone works ok and im happy.
jaspi72 said:
On my 1020 worked yeah but after while screen goes crazy and nightmode when time change place to up its fuked. 15014 not worked even soft reset or what ever. 15007 worked while after glance installed.
So last 2 fast updates (15007 and 15014) glance not working anymore what ever you do. Not trying to install anymore glance and phone works ok and im happy.
Click to expand...
Click to collapse
Does it flicker vertically? I have two Lumia 920, both of them use the same firmware and build. But one of them flickers like hell when showing glance screen and the flicker won't stop until I reboot the device. I read somewhere it's a software problem, someone said that the double tap to unlock option needs to be be turned off (i haven't tried that btw). But I think it has something to do with the hardware since the other 920 worked flawlessly without turning off the double tap to unlock option. Still have no idea why some devices does that...
Btw warning updated, I only tested this on RS1
No nothing vertically just crazy blurred mesh screen and cant do anything. Shutting phone like pushed shutdown putton when screen is blurred and do like normally (fingered down) phone shut down and camera sounds do work but screen is total mesh. Hard reset worked and when booted i didnt even try to put glance stuff on and now work. Nothing to do about doubletab i tested just glance stuff. Ok latest fast build is jamming making calls, not showing maked calls and sendet messages so hell please dont even try it.. Going back to last worked backup (slow build) and wait some
Q- put the whole zip(missing glance file.zip) in oem\public or ,put the files ,
I put file nd not working on L540,help please
thank you
:good::good::good: work perfect in lumia 920
SSWJ said:
Q- put the whole zip(missing glance file.zip) in oem\public or ,put the files ,
I put file nd not working on L540,help please
Click to expand...
Click to collapse
Does Lumia 540 support glance when it was on Windows Phone 8.1? If it doesn't, this tutorial won't work
It's working quite well on my 810
AWasisto said:
Does Lumia 540 support glance when it was on Windows Phone 8.1? If it doesn't, this tutorial won't work
Click to expand...
Click to collapse
Oh no It doesn't support
i use interop tool to restore glance screen in lumia 920 w10 using this.
it fonction; but when i connect my phone to pc it always open Filesystem Access
i desactivate Full Filesystem Access in Interop Tools > This Device > Interop Unlock and restart my device but still have the same issu
please any help thanks
ettoumia said:
i use interop tool to restore glance screen in lumia 920 w10 using this.
it fonction; but when i connect my phone to pc it always open Filesystem Access
i desactivate Full Filesystem Access in Interop Tools > This Device > Interop Unlock and restart my device but still have the same issu
please any help thanks
Click to expand...
Click to collapse
Finally! I thought I'm the only one having trouble deactivating full filesystem access
How to Fix MTP Root Path to Deactivate Full Filesystem Access
If you can't deactivate full filesystem access by just unchecking its checkbox on Interop Tools, I found a way to fix it
Open Interop Tools > This Device. Open sidebar, choose Interop Unlock
Check Full Filesystem Access
Enter C:\Data\Users\Public on MTP Root Path
Click the write button next to MTP Root Path
Uncheck Full Filesystem Access
Restart your device

Lumia 640XL dual sim damned

So, i copied an provxml file to the phone and hardreset it. Phone has gone to sad face. Meanwhile, i unlocked bootloader, enabled root access, disabled root acces, lockedback bootloader. And flashed to wp8.1 using wdrt. The problem is that my phone was impersonated as lumia950xl before to get last insider builds.. And after reflash i got Reset Protection recovery key screen. After i erased phone from my account and got the key, i cant recover phone. I fear to make emergency call and go to store to activate my account on phone.
Interesting....
I have an FRP locked 640 XL I bought off ebay for parts. I think I know what you mean by, "I fear to make emergency call and go to store to activate my account on phone." Microsoft seems at this point the only entity that can disable reset protection on the chip.
nate0 said:
Interesting....
I think I know what you mean by, "I fear to make emergency call and go to store to activate my account on phone."
Click to expand...
Click to collapse
No, you don't. Make the call, activate video call, store will open to install skipe, there in store settings page you can insert your credentials.
augustinionut said:
No, you don't. Make the call, activate video call, store will open to install skipe, there in store settings page you can insert your credentials.
Click to expand...
Click to collapse
That is one way to do it, but it won't disable FRP will it?
So, there is internet connection. I can insert Microsoft account, it notify me if i insert wrong password....but when i put good password and press login...bang....there is no internet connection, please retry Fkng Microsoft.
augustinionut said:
So, there is internet connection. I can insert Microsoft account, it notify me if i insert wrong password....but when i put good password and press login...bang....there is no internet connection, please retry Fkng Microsoft.
Click to expand...
Click to collapse
How about just bypassing it?
Just how? There is no return. Im talking about first screen, where it ask for key or account. After inserting account , no login
https://m.youtube.com/watch?v=4RQtSq0oqDM
Maybe this is your solution
Bypassing is the first step. I have not yet found a way to disable it...if even possible.
No keyboard settings on wp8.1.
augustinionut said:
No keyboard settings on wp8.1.
Click to expand...
Click to collapse
Upgrade to W10M...If you push the cabs for W10M to it via iutool you might actually bypass the FRP setup...that has happened to me before. But if you hard reset again on W10M unsuccessful to disable FRP it will show again.
A full list of cabs for lumia 640 xl dual sim rm_1067?
Download the wim file here
Open it in 7zip. Extract the folder for 640-640XL to a directory and push the cabs. You might even be able to just avoid all the work and download Microsofts otcupdater tool and use it to upgrade back to W10M...either or will work.
nate0 said:
Microsofts otcupdater tool
Click to expand...
Click to collapse
Phone started to download. Now at gears spinning.
@augustinionut
So the Skype trick...it is a bypass only right?
Phone updated to 10.0.13080.107 I passed first screen, apps don't open, configuration neither... i will try to update thru otcupdater.
Needed to manually install phonesettings.appx.
augustinionut said:
Phone updated to 10.0.13080.107 I passed first screen, apps don't open, configuration neither... i will try to update thru otcupdater.
Click to expand...
Click to collapse
If there is an FRP trip on your device, it will return but not until a Factory Reset/Hard Reset. But at least you get to use your phone again...
Edit: Oh and if you decide to try to remote wipe your phone once your account is back on. Don't just in case you have the same problem as me. My phone is FRP locked and bypassed. I was able to login with my account and add the phone to my account. One day was messing around and decided to test the remote wipe feature. It worked, sort of... There is some bug or an issue now that every time I sign into the phone to add it back to my account it immediately remote wipes it again. WP8 won't do this though since it does not run a compatible verison of the OS to use such features on the 640 XL.
I'm goying thru the second update
Tomorrow i will look here https://msdn.microsoft.com/en-us/library/windows/hardware/dn757558(v=vs.85).aspx using WPinternals.
EDIT:
Third update now...
EDIT2: i installed reset protection cab. But strange, cant reset phone, no internet connection . And language don't stick, it changed to default allways.
Still fighting https://docs.microsoft.com/en-us/windows-hardware/manufacture/mobile/reset-protection
So today i repeated all stuff. I reseted user data meanwhile the bootloader was unlock and root access activated. The sad face appeared again. So....flash to wp8.1.... and all from the beginning.
augustinionut said:
So today i repeated all stuff. I reseted user data meanwhile the bootloader was unlock and root access activated. The sad face appeared again. So....flash to wp8.1.... and all from the beginning.
Click to expand...
Click to collapse
Maybe wait to see what Heathcliff74 has on his next release...?

[HELP] How do I fix Glance Screen settings crashing in extras settings?

Well as title says. How do I do that? Everytime I open glance screen settings in extras, it closes and throws me back to settings. Really want to add background image to glance and etc, without resetting OS and losing all my data.
https://forum.xda-developers.com/showpost.php?p=71927078&postcount=67
dxdy said:
https://forum.xda-developers.com/showpost.php?p=71927078&postcount=67
Click to expand...
Click to collapse
Unfortunately it didn't fix my problem
Try uninstall it and install again
No need to install at least on my lumia 1020 glance screen app. Put just those files to MainOS-data-SharedData-OEM-Public in windows Phone internals Mass Storage Mode and last u need to use interop tools (2.0.95.0 on me and latest dont work) Tweaks and there "enable old glance screen....." and after reboot u have working glancescreen..

Enabled WiFi Calling on Lumia 950DS for T-Mobile.

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?

Categories

Resources