I have the Nexus 6P and had the new 8.x Oreo update pending for a few days now. Finally had time and patience for possible issues to get it done this evening. So.. I do a last update on apps, and the update freakin' DISAPPEARED on me! I go to settings/about/system update and it's now telling me that my system is currently up to date (on Android 7.1.2).
What the heck happened? And how do I get it showing up for me again?
If I where you I would just downloaded the firmware you want and flash it manually. That way you would have a clean start and likely avoid any hiccups. Of course that would mean you would have to unlock your bootloader and use a computer. Other then that there's no magic way to make the update appear. Use to be you had to sign up for the beta program but don't think that's necessary anymore.
Exodusche said:
If I where you I would just downloaded the firmware you want and flash it manually. That way you would have a clean start and likely avoid any hiccups. Of course that would mean you would have to unlock your bootloader and use a computer. Other then that there's no magic way to make the update appear. Use to be you had to sign up for the beta program but don't think that's necessary anymore.
Click to expand...
Click to collapse
I was ALL INTO rooting my devices for a while but then I got tired of 'managing' another device. I just left this one (the Nexus 6p) and my last phone (LG G3) both stock OS. The Nexus has been pretty solid for me for a year and a half.
This morning there's still no update pending. Very odd.
FractalSphere said:
I was ALL INTO rooting my devices for a while but then I got tired of 'managing' another device. I just left this one (the Nexus 6p) and my last phone (LG G3) both stock OS. The Nexus has been pretty solid for me for a year and a half.
This morning there's still no update pending. Very odd.
Click to expand...
Click to collapse
If you tire of waiting, enable Developer Options/USB debugging then ADB sideload the Full OTA image provided by Google. No need to unlock the bootloader.
Sent from my Nexus 5X using Tapatalk
FractalSphere said:
I was ALL INTO rooting my devices for a while but then I got tired of 'managing' another device. I just left this one (the Nexus 6p) and my last phone (LG G3) both stock OS. The Nexus has been pretty solid for me for a year and a half. This morning there's still no update pending. Very odd.
Click to expand...
Click to collapse
You should have no trouble downloading the correct full OTA and sideloading it via stock recovery. You've been stuck for quite a while.
Related
Hey guys,
I recently updated my OmniROM 18092014 version on my nexus5 but now its not showing any OTA in System updates of my device. I dont want to flash each update. Is there any solution please provide.
I'm also facing same issue. If it's a must for you then manually download and flash
Sent from my Nexus 5 using XDA Free mobile app
Same here. The last update shown was from 12.09.
boyz211 said:
Hey guys,
I recently updated my OmniROM 18092014 version on my nexus5 but now its not showing any OTA in System updates of my device. I dont want to flash each update. Is there any solution please provide.
Click to expand...
Click to collapse
You're not alone. Not working on mako also...Hope it gets solved sometime cause it's a nice feature.
opendelta has been broken since the 13th.
this is pretty normal -- get used to it.
A few of the guys are starting to look into it. Last I checked, it sounded like for whatever reason our SSL cert wasn't getting properly updated on one of the servers. I don't remember exactly, as the issue started when I was away on vacation and I haven't quite recovered from vacation yet.
(I'm not involved with maintaining the servers but I'm one of the more active people on the forums.)
I guess google isn't going to send me the new update bc im stuck on the January security and the MMB29V build. Can I use Wug's toolkit to flash the MHCI9I that also give me the updated radio/baseband ?
I did have 2 updates when i unboxed and powered on few days ago but this is as far as it updated. Wondering which build everyone else is on via OTA
I am on tmobile as my carrier. Thanks, been a minute since I had a Nexus device
If your bootloader is unlocked, just flash the image from here using fastboot: https://developers.google.com/android/nexus/images#angler. Make sure you read up on not losing your data when you do this. I usually flash all the img files one at a time, except userdata, don't flash that one. Don't need to flash cache. Don't flash recovery unless you're on stock recovery.
It will update your bootloader and radio.
Aerowinder said:
If your bootloader is unlocked, just flash the image from here using fastboot: https://developers.google.com/android/nexus/images#angler. Make sure you read up on not losing your data when you do this. I usually flash all the img files one at a time, except userdata, don't flash that one. Don't need to flash cache. Don't flash recovery unless you're on stock recovery.
It will update your bootloader and radio.
Click to expand...
Click to collapse
Yea I'm aware I can manually flash the update but I actually also want to know if other tmobile customers are 3 updates back like myself.
I'll eventually just root, unlock and flash Pure nexus rom but for the time being I'm just gathering this info.
Not me. I am T-Mobile and rooted with no other special mods and I've been receiving the update notifications. Now I take measures to return my phone to stock when an update occurs before trying to apply it, but so far I am on the current March update
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Not me. I am T-Mobile and rooted with no other special mods and I've been receiving the update notifications. Now I take measures to return my phone to stock when an update occurs before trying to apply it, but so far I am on the current March update
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hmm. Odd. I am bone stick right now and was just going to give it a week or so to populate and maybe push it out to me. The whole reason I picked up the 6p is bc I got tired of Samsungs lie and wait game with updates.
I recently just got a March update - probably last week.
I'm also T-Mobile and just got my phone a week ago, still on January security patch.
Sent from my Nexus 6P using Tapatalk
toddalvandi said:
I'm also T-Mobile and just got my phone a week ago, still on January security patch.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Oh OK. Atleast it's 1 other person.
FormeriPhoney said:
Oh OK. Atleast it's 1 other person.
Click to expand...
Click to collapse
I've also had a issue where my phone will sometimes randomly hang up right as I answer a call or some time during. Not sure if it's related but I thought some of the updates may include bug fixes.
Sent from my Nexus 6P using Tapatalk
For reasons that haven't been specified yet, the builds labeled MOB30D have been removed from the Nexus Factory Image page.
I uploaded it on the mirror, so, you can download if you want flash it. [Nexus 7 (2013) Wi-Fi]
https://mega.nz/#!15kGUSYA!6mKmEy1oZldroLtBDgOepWBt25xTqeVc7jC9TJ1Efyg
Weird they pulled it. Whats up with that. I didn't flash it. Notice any problems or super-secret files left in there?
I haven't flashed it either. I assume the found a bug.
Sent from my Nexus 6P using Tapatalk
I flashed it but I not noticed any issues so far
I still haven't flashed it but have been listening to some Mobb Deep. MOB30D!
Anyone having issues with this release? Debating whether or not to flash my unit. I notice that the Nexus 7 WiFi has binary files available with a MMB29X release.
This is interesting....found this link on Sprint's website: https://community.sprint.com/baw/message/1038775
Almost seems like MMB30D was suppose to have been the mid-March security release.
Features/Enhancements:
•Revision of March Android Security Update to include new fixes
For those who flashed this MMB30D onto the Nexus 7, what is the date in ABOUT PHONE. Is it April 1 or April 2?
Candy[MAN] said:
Anyone having issues with this release? Debating whether or not to flash my unit. I notice that the Nexus 7 WiFi has binary files available with a MMB29X release.
This is interesting....found this link on Sprint's website: https://community.sprint.com/baw/message/1038775
Almost seems like MMB30D was suppose to have been the mid-March security release.
Features/Enhancements:
•Revision of March Android Security Update to include new fixes
For those who flashed this MMB30D onto the Nexus 7, what is the date in ABOUT PHONE. Is it April 1 or April 2?
Click to expand...
Click to collapse
2 april
The last image for the Nexus 7 2013 razor that I see is still MMB29V.
So much for Google being responsive in getting security updates out. I would have thought that after making a big deal out of that mid-March kernel fiasco that they would have fixed and re-released the images for the three devices that they pulled for whatever reason on Monday. It's now the weekend and no explanation or update from Google. Why am I not surprised?
Build "MOB30D" again available for download via direct link.
On site, it still not displayed.
https://dl.google.com/dl/android/aosp/razor-mob30d-factory-15169856.tgz
what make you guys think this is for flo razor if sprint say : Nexus 5 software update - version MOB30D
and when we download, it says RAZOR !?! WTF !
Displax said:
Build "MOB30D" again available for download via direct link.
On site, it still not displayed.
https://dl.google.com/dl/android/aosp/razor-mob30d-factory-15169856.tgz
Click to expand...
Click to collapse
Was this link not working before (after it was pulled) or was it just taken off the site?
Candy[MAN] said:
Was this link not working before (after it was pulled) or was it just taken off the site?
Click to expand...
Click to collapse
All direct links stopped working after ~20 minutes after hiding from site.
And today they start working again, but still not displayed in the list.
I just factory defaulted my Nexus 7 (2013) device and installed this new factory image (MOD30D). Once I logged into my Google account, I got an email that I successfully logged into a Nexus 7 (2102).......2012??? WTF?
I wonder if there is/was an issue with the image's fingerprint where it would think that the 2013 model is actually a 2012 model.
Builds MOB30D for both models Nexus 7 2013, finaly, available in the list.
https://developers.google.com/android/nexus/images
These builds are uploaded again to nexus pages. And include a lots of bug fixes.
Just flashed new image with WUG, rerooted, flashed Xposed and ElementalX
I'm confused. I flashed MOB30D when Google first posted it, but then took it down. Now MOB30D is back up. Do I need to re-lash it?
DaveImagery said:
I'm confused. I flashed MOB30D when Google first posted it, but then took it down. Now MOB30D is back up. Do I need to re-lash it?
Click to expand...
Click to collapse
They probably took it down for some reason first time. Flash again.
htb2050 said:
They probably took it down for some reason first time. Flash again.
Click to expand...
Click to collapse
These monthly updates while obviously a good thing, there also kind of a pain in the ass. Every month I have to flash the new image, re-root the phone, use Titanium Backup, to go in and delete enough from sys partition, to flash Xposed, followed by flashing my beloved ElementalX kernel. Unless there is some way to streamline all that, a noob like me isn't aware of. Presumably we got just a couple weeks till the May security update anyway. I'll wait.
DaveImagery said:
These monthly updates while obviously a good thing, there also kind of a pain in the ass. Every month I have to flash the new image, re-root the phone, use Titanium Backup, to go in and delete enough from sys partition, to flash Xposed, followed by flashing my beloved ElementalX kernel. Unless there is some way to streamline all that, a noob like me isn't aware of. Presumably we got just a couple weeks till the May security update anyway. I'll wait.
Click to expand...
Click to collapse
Use WUG no wipe option, then root with WUG. Not all that difficult.
Sent from my Nexus 7 using XDA-Developers mobile app
Want to change my build from Verizon NBD91V to N4F26O for all other carriers. Any easy way to do it? Can I side load an OTA or do I have to side load a factory image and lose all my stuff? Any other way to do it? I'm stuck on 7.0 and would like to update to 7.1.1. or 7.1.2.
Thanks
Sent from my Nexus 6P using Tapatalk
Yes, you can easily flash between builds/carriers with no ill effects. Download the full Google stock image (not OTA) and do it manually with flash-all.bat (first edit this file in Notepad to remove the -w (wipe) switch so as to not lose your userdata) or you can install and use a toolkit like NRT or Skipsoft found here on XDA to automate the process. Google has released a few images specific to Verizon that included a modified radio, but that radio also works well on all networks. Current radio version is v03.79 for Verizon and v03.78 for all others.
You could always flash a custom rom.
So I flashed a stock image, will I still get OTA updates? Haven't gotten Feb. Update yet.
Sent from my Nexus 6P using Tapatalk
08BlackWRX said:
So I flashed a stock image, will I still get OTA updates? Haven't gotten Feb. Update yet.
Click to expand...
Click to collapse
If you did flash stock, and remained completely stock (ie. not rooted, no custom recovery or kernel) you should get regular OTA security updates. Your OP says you wanted to flash N4F26O which is the February update. March updates are coming out this week, so I would just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
v12xke said:
If you did flash stock, and remained completely stock (ie. not rooted, no custom recovery or kernel) you should get regular OTA security updates. Your OP says you wanted to flash N4F26O which is the February update. March updates are coming out this week, so I would just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
Click to expand...
Click to collapse
I'm actually on N4F26J, I couldn't get N4F26O to work with the Nexus Toolkit for some reason. And yes I'm completely stock otherwise.
Sent from my Nexus 6P using Tapatalk
08BlackWRX said:
I'm actually on N4F26J, I couldn't get N4F26O to work with the Nexus Toolkit for some reason. And yes I'm completely stock otherwise.
Click to expand...
Click to collapse
The only way I know of to try to force an OTA is to swap a SIM from a different carrier into your phone, let it connect (carrier shows in notification). Try to update in settings>>about phone. Then swap your SIM back in. If this doesn't work (it did for me) then.... March updates are coming out this week, so just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
v12xke said:
The only way I know of to try to force an OTA is to swap a SIM from a different carrier into your phone, let it connect (carrier shows in notification). Try to update in settings>>about phone. Then swap your SIM back in. If this doesn't work (it did for me) then.... March updates are coming out this week, so just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
Click to expand...
Click to collapse
Good to know, thanks.
Sent from my Nexus 6P using Tapatalk
08BlackWRX said:
Good to know, thanks.
Click to expand...
Click to collapse
Boom!
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
andMego said:
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
Click to expand...
Click to collapse
Unless he is willing to manually update, there are only a few options. One would be try enrolling and then un-enrolling in the 8.0 beta program. Others have reported soon after un-enrolling they received an OTA. The other is borrowing a SIM from a different carrier for a few minutes, trying to update the system in settings, and then switching the SIM back. This will sometimes trigger an OTA. Finally, a more drastic measure would be to do a factory reset. Other than that he will just have to wait.
andMego said:
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
Click to expand...
Click to collapse
You could try checking if his phone is enrolled in android beta program. If it is, you could try unenrolling from the beta program, and the phone may get further update (only a mild possibility, but it has happened atleast once to a n6p I know).
Alternatively, if you want the update badly, you could download the full ota image and do a ADB sideload via stock recovery. Pretty simple process, works with locked bootloaders.
NoobInToto said:
You could try checking if his phone is enrolled in android beta program. If it is, you could try unenrolling from the beta program, and the phone may get further update (only a mild possibility, but it has happened atleast once to a n6p I know).
Alternatively, if you want the update badly, you could download the full ota image and do a ADB sideload via stock recovery. Pretty simple process, works with locked bootloaders.
Click to expand...
Click to collapse
I'm in the same boat ?
v12xke said:
One would be try enrolling and then un-enrolling in the 8.0 beta program. Others have reported soon after un-enrolling they received an OTA.
Click to expand...
Click to collapse
Didn't work.
andMego said:
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
Click to expand...
Click to collapse
My wife's Nexus 5X on T-Mobile just got Oreo a few days ago. I'm still waiting (but hopeful) for my Nexus 6P update. Neither of us were rooted or beta.
I was stuck on the August security patch too. I didn't realize it until September and then October rolled around.
I'm also on TMobile. I ended up just ended up manually updating. Worked without issue.