I just enrolled my 5x for the beta program 2 days ago, i still havent received the ota update. I did manually flash 8.0 after using PN rom. Is there any fix for this issue?
Google may have stopped the ota for now. Probably soon we will get the dp2. Or if you didnt lock your bootloader you can flash the factory images without wipe.
Related
So about a few weeks ago, I received the MD4 OTA update. Ever since, I've been having problems with the phone occasionally freezing during app use. Whether its using Waze or playing Auralux, it will freeze. Pretty consistantly during Auralux. Heres the deal, I'm stock but rooted. I kept receiving the OTA update notification so I flashed the stock recovery to get the update.
Extremely annoying, currently browsing for a ROM that suits my fancy. Seems to me, I can't find one yet. Which is why I remained stock for so long.
You say that you flashed the Stock Recovery, and accepted the OTA. Did the Update go through ? Did you check Root afterward ?
Hi All,
Last week I received a system update for my Nexus 7 for Lollipop. At that time I didn't want to update so I dismissed the notification. The problem is that I can't get it to re-appear. I've already tried to check for updates 100 times over a couple of days. I've also cleared the Google Play Services and then check for updates, but didn't work.
Is there a simple way to get the update notification again?
Thank you for your help!
Yes, wait for the OTA to become available again. There's a possibility that the latest OTA (5.0.1) was pulled and is no longer available. If you really want the update, download the firmware from Google and flash it manually.
Edit: someone got the notification today. So who knows why you haven't received the notification.
I thought one you dismiss the notification and don't take the update you go back to the end of the queue - so it could be weeks before you get it again.
Happened to me as well. Got the notification last week for 5.0.1, didn't update but didn't dismiss it either. After a couple of days it just disappeared and so far hasn't shown again.
I'm still waiting on 5.0 here. Getting annoyed and was looking for sideload update options but if other people are still waiting on it I guess I'll hold off a bit longer.
If you're now running a modified stock rom, you will most likely have issues updating with the OTA. Here's a way to update without having problems or waiting for the OTA with no loss of data: Download the rooted rom from Scrosler found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , use Wugfresh's NRT 1.9.9 to update the bootloader that's also mentioned in Scrosler's thread, and then dirty flash (no wipes) the 5.0.1 rom with TWRP.
Phibernaut said:
I'm still waiting on 5.0 here. Getting annoyed and was looking for sideload update options but if other people are still waiting on it I guess I'll hold off a bit longer.
Click to expand...
Click to collapse
Stop waiting and do it manually. Why is everyone so consumed with sideloading? You can flash the latest firmware in fastboot without losing anything.
When I lost my update (long story) it took 3 days to come back. A little less than I was expecting but still a little more than I wanted. I'd expect you'll get it back in 2-3 days.
Same here! But will download it now instead. Tierd of waaiting
My phone was working pretty well on the 5.1.1 lollipop update, no crashes, somewhat okay battery life after a full factory reset and manual installation of programs (Reinstalling with kies seemed to kill battery life again). I jumped at getting the MM update when it as available. I had previously rooted my EVO 4g and had issues getting updates after a certain point, so I haven't rooted my Note 4 yet, since I was happy with the updates.
Now, though, the MM update keeps crashing my phone. It will sometimes maintain stable operation for 20 minutes, but it will eventually crash and reboot. I once got the mmc_read_failed error on a reboot, but I am not completely sure what is causing the issue. The phone worked fine until the OTA update installed. After that point, it crashed once while setting up my Google account and has been crashing regularly ever since.
What's the best way to fix this? Are there any good Marshmallow updates I can install, either rooted or stock. Also, any I can use Odin for?
palehorse864 said:
What's the best way to fix this? Are there any good Marshmallow updates I can install, either rooted or stock. Also, any I can use Odin for?
Click to expand...
Click to collapse
Check out @tx_dbs_tx 's stock pre rooted DeOdexed 6.0.1 romantic here:
http://forum.xda-developers.com/showthread.php?t=3352832
Factory reset AFTER your OTA updates clears up most problems.
Good luck
I had this happen. I was getting the mmc read failed 6x a day. Nothing fixes it. Internal mem failed. My free replacement came in today. TWRP, tx's rooted stock Rom/everything restored with tb..... Good to go.
Sad too, it was a launch day mint condition phone.
Sent from my SM-N910P using XDA-Developers mobile app
Hello, I'm having a strange issue with March Security Patch update. 3 days ago I received via ota this update, did it and everything was OK. The day after, I rebooted the phone, and sudden it turns black and rebooted by itself looping on coloured little balls before G logo. Another reboot and when it turns on I noticed that it downgraded by itself on February patch security, giving me the March update aviable via ota again.
I reupdated but the day after, once again the same thing. And once again yesterday...and once again today. What have I to do?
hbkekko said:
Hello, I'm having a strange issue with March Security Patch update. 3 days ago I received via ota this update, did it and everything was OK. The day after, I rebooted the phone, and sudden it turns black and rebooted by itself looping on coloured little balls before G logo. Another reboot and when it turns on I noticed that it downgraded by itself on February patch security, giving me the March update aviable via ota again.
I reupdated but the day after, once again the same thing. And once again yesterday...and once again today. What have I to do?
Click to expand...
Click to collapse
Is your bootloader unlocked or any root or anything of that sort? That's a very weird issue. There are reports of the Nexus 6 being downgraded to 7.0 by Google but I'm not sure if it's a software push they are doing to cause that to happen.
You may have to wipe cache and try the update again.
Jammol said:
Is your bootloader unlocked or any root or anything of that sort? That's a very weird issue. There are reports of the Nexus 6 being downgraded to 7.0 by Google but I'm not sure if it's a software push they are doing to cause that to happen.
You may have to wipe cache and try the update again.
Click to expand...
Click to collapse
I tried to wipe cache from settings, storage but didn't work. Yes I've unlocked bootloader but no root. Could this be the problem?
No, shouldn't affect anything just being unlocked. Now if you installed TWRP, that might cause this. I didn't use an OTA to go to the march update so idk if it might be at fault, I was on pure Nexus so chose to flash the factory image and haven't had any issues so far.
Sent from my Pixel XL using Tapatalk
Solved flashing the latest factory image via fastboot
Cliff notes: rooted/unlocked xl on stock 8.1 ota. that I sideloaded. Phone installed 9 ota, requested restart, now im on 9. I honestly do not remember accepting update.
How can this happen? and will there be issues?
More Details:
So an odd thing happened to today. My phone, a rooted/unlocked running stock rom, got a notification for an update to 9. I have had my phone since 1/17, and I have been rooted unlocked since day one. This is the first time I have received a update notification. I ignored it figuring ill just get the ota and sideload it like i have done previously. Later today my battery was low and I get a message stating the update install is paused due to low battery. Once it charged enough it told me to restart phone which i did, then quickly realized it may have been a bad idea. Phone booted, told me i had an unlocked phone blah blah, then I noticed my custom loading screen was replaced by the standard google screen. 30 seconds later android 9 boots up. everything works fine, lost root though.
specd_out said:
Cliff notes: rooted/unlocked xl on stock 8.1 ota. that I sideloaded. Phone installed 9 ota, requested restart, now im on 9. I honestly do not remember accepting update.
How can this happen? and will there be issues?
More Details:
So an odd thing happened to today. My phone, a rooted/unlocked running stock rom, got a notification for an update to 9. I have had my phone since 1/17, and I have been rooted unlocked since day one. This is the first time I have received a update notification. I ignored it figuring ill just get the ota and sideload it like i have done previously. Later today my battery was low and I get a message stating the update install is paused due to low battery. Once it charged enough it told me to restart phone which i did, then quickly realized it may have been a bad idea. Phone booted, told me i had an unlocked phone blah blah, then I noticed my custom loading screen was replaced by the standard google screen. 30 seconds later android 9 boots up. everything works fine, lost root though.
Click to expand...
Click to collapse
my phone is still on 8.1 and a check say's up to date, I have downloaded 9. ppr ota , would like to know before i side load, have you got root back ? I use magisk .
I have not attempted to get root back.
Did you have TWRP? Honestly, I'm in a situation where I'd like that to happen. Unfortunately I don't have access to my PC and would like to take the final OTA to Pie, but I'm rooted with Magisk, and.have TWRP installed, I'm worried about a bootloop.
I'm just trying to figure out if there is a way to force my phone to get the OTA update the normal way. My Pixel picked it up as soon as I manually checked for an OTA Update. My daily driver Pixel XL has been saying that I am up to date for the past 22 - 23 hours since the update went live, so I'm still stuck on 8.1.0. Does Google drip feed the update out in blocks based on IMEI to limit the impact on the download server?