Everytime I turn on my Nexus 5, the date goes back to 04/20/1971. It only happens with the latest build of PA (5.1). I've tried different Gapps and clean flashed the rom but no luck. Any ideas?
Thanks in advance.
Have yoi checked the time-settings if it is automatically updated?
Checked. It's on auto but it still rolls back on every boot. Takes a while to sync it to the actual date.
Related
Hello
I'm getting date and time error on every restart I perform. Due to this WhatsApp stops working and treeless me to correct the date. I found out that after performing restart the phone's date reverts to 1/1/1970 and time 5:45AM. The phone than within a minute corrects it automatically. This wasn't an issue with 4.2.2
If anyone could help me with this, it would be great.
Thanks
what steps have you taken to try and fix it?
playya said:
what steps have you taken to try and fix it?
Click to expand...
Click to collapse
Nothing. It just gets fixed automatically after a minute or two. I can even see it literally, the change on the notification bar from 5:45 to the correct time.
I'm on stock, never rooted or unlocked the boot loader.
Hi there! I'm running the latest (well, almost...) nightly build on my device, a Google Nexus 7 Wifi (2013) [flo]. For some reason, I haven't been able to update since the 4.4.4-20141202-flo nightly, because every single day it downloads the current update, verifies it against the MD5, then when I tell it to update it says there's a zip file signature verification error and cancels the install. I'm kind of afraid to turn that off, because last time I did that I had to do a complete factory restore on my device to get it usable again. Any ideas what's wrong?
Oh, I forgot to mention, I've also tried downloading the updates directly, still has the same problem. That's actually why I know what error message is popping up.
YmerejO42 said:
Oh, I forgot to mention, I've also tried downloading the updates directly, still has the same problem. That's actually why I know what error message is popping up.
Click to expand...
Click to collapse
That sounds like around when the DL server ran out of disk space.
Manually flash the latest from dl.omnirom.org
Entropy512 said:
That sounds like around when the DL server ran out of disk space.
Manually flash the latest from dl.omnirom.org
Click to expand...
Click to collapse
It actually started two days after that problem was sorted, and the two updates for those days worked fine. Also, as I'd said, I'd tried manually downloading the updates during this period. However, yesterday morning, starting with the update for the 7th, it started working again, so I'm once again up to date.
i tried to to sideload a 700m some zip file to fix the prob, it doesn't work on my 6p cause the version is moved to mtc20L, i need help!
What rom are you running on?
You'll find everything you need in this thread : http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
oussamalabbize said:
What rom are you running on?
You'll find everything you need in this thread : http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
Click to expand...
Click to collapse
thanks for reply. my 6p is running 6.0.1 (MTC20L) before it couldn't start up. now i do the recovery steps ,i can see the version is the same. i tried everything except the factory image cause i didn't get phone unlocked.
about three days ago, i turned off my 6p ,when i restarted it , it just stuck on the google logo and then restart and stuck on the google logo again and again.
i did nothing wrong before, even i hadn't got the 7.0 official ota update, i only got a 27M updating package of september which was described as a preparation update for the update of 7.0
my device is locked both oem and the bootloader, so i can only do the reset to factory mode, clear data and cache, no use. i tried to adb sideload the recent google OTAs including MTC20L ,7.0.0 (NRD90T) 7.0.0 (NRD90U), no use. before the brick occured, i got my device ota mtc20l. now i can do nothing but wait for more help fromanyone and hoping google may give a cure.
Hi there,
I started this topic because I am out of options and I don't know what to do at this point.
My Phone is a XT1562 DualSim.
I recently flashed http://forum.xda-developers.com/moto-x-play/development/rom-spetrum-mm-volte-t3462690 and I also installed "MODEM" (MPD24.107-70) from page 1, but not right away.
First I wiped everything expect "internal storage". The phone booted but it restarted during boot (which might be okay) but then it rebooted again during boot. The boot process finally finished and I got to the screen "Android is starting - Optimising app x of y." The phone rebooted even during that process and that is definitely not normal I think. So after a couple of reboots android did finally optimise all apps but the phone did still reboot withing the first 30 seconds after it was booted.
From here I did a lot of testing and doing. These are my findings:
- When I set phone to flight mode / airplane mode it does NOT reboot... Hurray!
- When I flash another ROM (Official CM 13, http://forum.xda-developers.com/mot...m-cyanogenmod-13-preview-moto-x-play-t3252255) the phone runs like a charm, NO reboots whatsoever.
- - But as soon as I flash gapps and the phone is booted, I get the reboots again (usually within the first 30 seconds).
- - Again setting the phone to flight mode prevents itself from rebooting.
- - Apparently it doesn't matter what version of gapps I flash. I even tested the light version (ARM, 6.0, Pico, from http://opengapps.org/). It still reboots. I also tried gapps mini and stock.
Oh and I don't think its MODEM (mentioned above) related, because I faced these problems already before I installed / updated the MODEM. Well I thought its MODEM related, that's why I went back to MODEM stock version MPD24.107-52 but that did't help either. I should mention that I am not sure if I had MPD24.107-52 installed originally but spetrum (the rom developer) pointed me to that version: http://forum.xda-developers.com/showpost.php?p=69129552
I also restored my working TWRP backup from an android I used for month and guess what, yep, reboots
brrrrr this is frustrating
I never experienced that before and frankly I am out of ideas.
Anything is welcome and appreciated
Thank you
If nothing helps reflashing the whole firmware is always an option
minimale_ldz said:
If nothing helps reflashing the whole firmware is always an option
Click to expand...
Click to collapse
Thanks I haven't done that.
To be clear, you mean firmware as in stock rom / factory image?
I always go back to flashing stock rom with rsdlite whenever things went wrong and I can't solve it by flashing small fixes.
rancor187 said:
Thanks I haven't done that.
To be clear, you mean firmware as in stock rom / factory image?
Click to expand...
Click to collapse
I mean full stock firmware you flash with fastboot or RSD. Roms are usually only system + kernel, so not very helpful in your case
Guys! Good news. I did go back to stock firmware and from there to official CM13. Of course I had to root and install TWRP again but it was worth it.
I lost a few days spending my time with it but I'm glad its all good now thanks to you.
Right after the 7.0 NRD90U update, Play Store can't download or will download extremely slow any update-app.
Plus it can't download the system update (stays in waiting to download for 2 mins and then it says couldn't download)
So i searched as much as i could for a solution and tried litterally everything (rebooting, pulling sim card, airplane mode on and off, changing wifi network, switching to 4g/3g even 2g, factory reseting, booting to safe mode, deleting cache and data for every app possible) and haven't changed a thing.
I never rooted or unlocked the bootloader and never used Doze mode (also i made sure it was turned off)
I want to fix this ****ty bug or whatever without flashing stock images if possible
UPDATE
for some seriously strange reason it worked!
right after i posted this thread i pressed retry and it downloaded the NBD90X update and then immediately after first boot it downloaded the final NBD91K update
even the playstore now works just fine
i really don't know wtf happened