Database Info

[Q] Nexus 5 wipes itself without asking

Hi,
I have a nexus 5 since April 2014, and since then it has wiped itself 3 times without my permission (once in July, and recently in Sept and Oct). Maybe since kitkat upgrade ?
Always the phone was on the table and screen locked with PIN - so this isn't a case of accidentally selecting factory reset.
Also, no remote wipe command was sent.
I discovered the reset while picking up the phone to use it and seeing the famous robot screen with the text "erasing data".
Has anyone encountered this issue and how to prevent it?
Also, does anyone know if once the erasing process starts how to interrupt / reverse it?
This isn't a case of a email hack as I have 2 step verification and remote wipe not possible as the phone was not connected to WiFi or cell data network at the time.
Does anyone know how a factory reset can occur aside from selecting from the menu or remote wipe?
Also phone is stock no root, etc..

Sot73 said:
Hi,
I have a nexus 5 since April 2014, and since then it has wiped itself 3 times without my permission (once in July, and recently in Sept and Oct). Maybe since kitkat upgrade ?
Always the phone was on the table and screen locked with PIN - so this isn't a case of accidentally selecting factory reset.
Also, no remote wipe command was sent.
I discovered the reset while picking up the phone to use it and seeing the famous robot screen with the text "erasing data".
Has anyone encountered this issue and how to prevent it?
Also, does anyone know if once the erasing process starts how to interrupt / reverse it?
This isn't a case of a email hack as I have 2 step verification and remote wipe not possible as the phone was not connected to WiFi or cell data network at the time.
Does anyone know how a factory reset can occur aside from selecting from the menu or remote wipe?
Also phone is stock no root, etc..
Click to expand...
Click to collapse
When you refer to remote wipe, I assume you are referring to Android Device Manager. But there are other apps that could do this, like Cerberus. Do you have any other security apps installed?

Hi,
Yes I'm referring to ADM. The first time it happened I had Mobile Iron installed. The other 2 times I made sure not to install that app. So no security apps at all except maybe exchange email account that probably allows remote wipes, but I viewed the logs on my exchange account for wipes sent and no such command was sent.
Also, I have 2 iOS devices that are on mobile iron and exchange for over a year and no wipes occurred.

[Completed] Woke up this morning to Bitlocker Blue Screen - No Updates Installed

Hi all,
Lumia 1020 running Developers Preview Latest Build on Cyan Update
Basically to recap, I woke up this morning, phone seemed to be working fine. Left the house and tried to put on some music. The 'On The Phone' music only contained my own music I had ripped and copied over via USB no Xbox Music albums. I thought it might be a licensing issue whereby it wasn't picking up my Music subscription, and decided to restart the phone -> slide down power off. This shut the phone down remarkably quickly and when I turned it back on - Bitlocker Blue Screen.
So far recovery via the Nokia Recovery Tool has failed. with Error 0x80131500 every time, so I'm now trying other more 'advanced' recovery options.
The only thing I can think of that has recently changed with the phone is last night I started populating my Music folder (created via the link in New details emerge about rumored Microsoft Xbox Music Locker service | Windows Central) on my OneDrive and copied across some of my own DRM free music. Which I subsequently downloaded some of these DRM free files via the 'Files' app to the phone.
My phone is connected to my work Office365 Exchange account, but I'm the Sys Admin so I know nothing got changed there yesterday that would have enabled Bitlocker. I had previously rolled back my phone to pick up the OTA Cyan updates some months ago and subsequently re-enabled the Preview For Developers and was up to date with updates - the last being approx 2-3 weeks ago. (I had also flashed my Regional Variant to be an o2 GB variant, but this has worked flawlessly)
Any comments from the similarly afflicted would be useful!
​Rich
UPDATE: Product Support Tool for Store fails the flash with error:
FA_ERR_VERIFY_FAIL: 0xFA00000D
Exception:
Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.MurzimProgrammingException: FA_ERR_VERIFY_FAIL: 0xFA00000D
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__c(Object state)
Now I need help!

Hi there,
You have a dedicated forum for this device and for more relevant you must start asking there:
Nokia Lumia 1020 > Lumia 1020 Q&A, Help & Troubleshooting
Have a nice day

Woke up this morning to Bitlocker Blue Screen - No Updates Installed

Hi all,
Lumia 1020 running Developers Preview Latest Build on Cyan Update
Basically to recap, I woke up this morning, phone seemed to be working fine. Left the house and tried to put on some music. The 'On The Phone' music only contained my own music I had ripped and copied over via USB no Xbox Music albums. I thought it might be a licensing issue whereby it wasn't picking up my Music subscription, and decided to restart the phone -> slide down power off. This shut the phone down remarkably quickly and when I turned it back on - Bitlocker Blue Screen.
So far recovery via the Nokia Recovery Tool has failed. with Error 0x80131500 every time, so I'm now trying other more 'advanced' recovery options.
The only thing I can think of that has recently changed with the phone is last night I started populating my Music folder (created via the link in New details emerge about rumored Microsoft Xbox Music Locker service | Windows Central) on my OneDrive and copied across some of my own DRM free music. Which I subsequently downloaded some of these DRM free files via the 'Files' app to the phone.
My phone is connected to my work Office365 Exchange account, but I'm the Sys Admin so I know nothing got changed there yesterday that would have enabled Bitlocker. I had previously rolled back my phone to pick up the OTA Cyan updates some months ago and subsequently re-enabled the Preview For Developers and was up to date with updates - the last being approx 2-3 weeks ago. (I had also flashed my Regional Variant to be an o2 GB variant, but this has worked flawlessly)
Any comments from the similarly afflicted would be useful!
​Rich
UPDATE: Product Support Tool for Store fails the flash with error:
FA_ERR_VERIFY_FAIL: 0xFA00000D
Exception:
Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDia log.MurzimProgrammingException: FA_ERR_VERIFY_FAIL: 0xFA00000D
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDia log.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDia log.RecoveryDialogModel.<HandleDownloadVariantPack ageCompleted>b__c(Object state)
Now I need help!

Lumia 520 Flashing Exception
Same problem with my Lumia 520 as well.
Flashing results in same exception. Looks as if some kind of memory issue.
Mobile continuously restarts and radiates too much heat.
Please let us know will microsoft provide a fix for same in the WRT update?

[Q] Still getting license verification issues w/ Pro

Hi,
I don't have lucky patcher installed and have gone thru the FAQ section to fix this issue but problem still remains. I have one tablet that Pro stays activated, but it does not stay activated on my Android TV box. I think the cause is that the tablet which works has an inbuilt battery, so the date/time is always correct (regardless of internet being on/off), whereas the android box has no battery and if you switch on the box without an internet connection (I usually do this as the main reason for the box is to watch my 600+ films from my external HDD), the date/time goes back to 1970 and the license verification issue appears.
I'm assuming this is the cause of the problem as when I first install Pro on the TV box from google play store (with internet on), Pro says it is activated. It's when I reboot without the internet on, that the problem occurs.
Any ideas? (apart from keeping internet on all the time )
Just confirmed that it is system date related, by trying a few scenarios. I can fix the problem by having the internet on when I boot the TV box (and system date is automatically updated from the net), then Pro says it's activated. Once the date is set, it appears that I can then turn off the internet and use Pro until the next boot. However, if I boot with internet off and try to use Pro, I get the license error.
If I boot with internet off, then fix system date manually, I still get Pro license error, so I assume Pro does some initial license check the first time you use Pro after a boot, and the internet must be on for this to happen.

ukmark62 said:
Hi,
I don't have lucky patcher installed and have gone thru the FAQ section to fix this issue but problem still remains. I have one tablet that Pro stays activated, but it does not stay activated on my Android TV box. I think the cause is that the tablet which works has an inbuilt battery, so the date/time is always correct (regardless of internet being on/off), whereas the android box has no battery and if you switch on the box without an internet connection (I usually do this as the main reason for the box is to watch my 600+ films from my external HDD), the date/time goes back to 1970 and the license verification issue appears.
I'm assuming this is the cause of the problem as when I first install Pro on the TV box from google play store (with internet on), Pro says it is activated. It's when I reboot without the internet on, that the problem occurs.
Any ideas? (apart from keeping internet on all the time )
Just confirmed that it is system date related, by trying a few scenarios. I can fix the problem by having the internet on when I boot the TV box (and system date is automatically updated from the net), then Pro says it's activated. Once the date is set, it appears that I can then turn off the internet and use Pro until the next boot. However, if I boot with internet off and try to use Pro, I get the license error.
If I boot with internet off, then fix system date manually, I still get Pro license error, so I assume Pro does some initial license check the first time you use Pro after a boot, and the internet must be on for this to happen.
Click to expand...
Click to collapse
Once it's activated it can work without internet.
There is a another possibility that the data partition where mx player stores app data getting erased upon reboot or it might be stored in Ram.
In this case, MX Player will try to verify the license since old data got erased. But, Invalid system time settings will lead to the issues with connctivity to google license validation servers. So, MX Player will throw the error.

ktsamy said:
Once it's activated it can work without internet.
There is a another possibility that the data partition where mx player stores app data getting erased upon reboot or it might be stored in Ram.
In this case, MX Player will try to verify the license since old data got erased. But, Invalid system time settings will lead to the issues with connctivity to google license validation servers. So, MX Player will throw the error.
Click to expand...
Click to collapse
Thanks for the response.
It's not a particularly big issue for me, as I have other video apps to choose from. Just thought it was worth putting it "out there".

Question Problems with initial connection

Hello
I've been given a GW 4 recently. However, I have a not very new, but still working phone, which is a Redmi Note 4 (mido). At the beginning I've had no problem with the connection. I was able to install directly from the store the main apps needed: Samsung wereable (old gear) and g. watch 4 plugin. And it connected perfectly. Nevertheless, some other apps needed (samsung health and health monitor) are not available for my phone (due to android version). So, to try them, I reseted the watch and connected it to a newer Samsung Phone that I was lended. I had everything working ok but it was just to test all the functions temporaly since I'm planning (but not yet) to buy a new phone and I returned the Samsung phone to his owner.
For these reason I tried to connect the watch to redmi again, but now it's impossible to make it connect. There must be some issue with the phone or something because it detects the watch sometimes, but it happens that bluetooth given code to connect is random and does not match the one that appears in the watch, or it provides a new code in the phone again while it is already in the connecting procedure, things like that. Normally connection hangs when it reaches 80% or so.. I tried a few things:
-hard reset in the watch (via recovery)
-uninstalling and install the samsung apps
-installing older versions of the apps
-reseting network settings (it cleans bluetooth list of devices)
-cleaning bluetooth app cache and changing bt device name-
-Some other things that I cant remember to no avail
Any idea on how to proceed without factory reset the phone?
Thank you

Do you have more than one Google Account on the phone? I had to sign out of them all bar my main one and it worked.

Hello, I did not realise about this issue so I went through all the possible google accounts that may have included the device, and I remove it from all of them (4 in total)
But still no connection. The best I can achive is "Please finish the config in smartphone" in the watch and stuck at 88% of "preparing your watch" in the smartphone. But even when this happens it seems like Samsung wereable feels like the watch disconnects and it asks again to search for a device and to pair with a different bt code, while samsung watch 4 plugin stays 88% progress of connection.
It's quite strange. It must be some problem with the plugin.
After a while it says in the watch that connection was not possible with the phone. And it restablish factory values itself.
oxfordmark said:
Do you have more than one Google Account on the phone? I had to sign out of them all bar my main one and it worked.
Click to expand...
Click to collapse