Hi,
I have a Nexus 6P (as you could guess) runner Nougat, and for some reason my phone doesn't get the monthly security OTAs.
When Nougat was officially released, I waited a free days, and after getting tired of clicking the "check for updates" button, I sideloaded the image zip through ADB.
My phone used to be rooted, but I reverted everything and locked the bootloader.
A few days after the September update was released my phone didn't get it, so I sideloaded it too. Now the same thing is happening with the October update.
One of the reasons I unrooted my phone is so I don't have to manually update the phone every month, so it's quite annoying.
Has anyone experienced this? My first guess would be that Google is doing a staged rollout, but we're talking security updates here. That would mean they're willfully exposing you to 1-day vulnerabilities.
P.S. my phone is not a carrier phone
Sent from my Nexus 6P using XDA-Developers mobile app
Similar trouble with me
I was tired of waiting for the Nougat update. So as many sites had suggested, I enrolled in the beta program and got the update. Post that I unenrolled my device.
Still running android 7 with August security patch. Haven't received any update since...
Not really sure what am I supposed to do to get the updates... Battery life is now horrible... Read that September patch would fix it... But still not got it
It sucks....
I don't have a solution. I get that it's annoying that the OTA system isn't exactly fast.
But I mean, if you look at it another way, sideloading will always be the fastest way to do it. Personally, I do it asap once it's released. I actually like that we have this option. People who don't care as much can wait and people who want it asap can sideload.
I'm rooted. As soon as an update comes out, I use flashfire to update my 6P. It's really simple and really fast.
Enviado de meu Nexus 6P usando Tapatalk
casadomack said:
I'm rooted. As soon as an update comes out, I use flashfire to update my 6P. It's really simple and really fast.
Enviado de meu Nexus 6P usando Tapatalk
Click to expand...
Click to collapse
The last time I tried FlashFire it didn't work for OTA. Does making changes to build.prop break it? Maybe that's why I couldn't apply OTA update?
But you're not supposed to use the OTA images. You have to use the factory images.
https://developers.google.com/android/nexus/images
In Flashfire use "+”, "flash firmware package" and select the downloaded image.
I've unchecked everything but "boot", "system" and "vendor".
You can find more complete tutorials here in xda, but it's that simple.
Enviado de meu Nexus 6P usando Tapatalk
Related
I'm on the last release of the beta, stock beta.
I took my Nexus off the beta... But I'm not getting any OTA updates.... Am I stuck on the beta now? I thought I would get the new version people are talking about from the other day.
God.... I don't want to ADB flash it.
Flashing has gotten so much more complicated the last couple years. And with all the talk about people bricking, I don't want to take any risks.
I apologize if this has been asked already, any useful information gets buried so fast these days.
Maybe I'm just getting old. ****.
Sent from my Nexus 6P using Tapatalk
I'm on nrd90m I left the beta, and nothing happens. Why isn't it updating g to nrd90u ....
Sent from my Nexus 6P using Tapatalk
The ota rolls out in stages. Give it time, youll get it
Okay. Thanks. That's sort of what I was thinking. But I couldn't find anything that said I would go forward out of the beta and not wiped and back to mm
Sent from my Nexus 6P using Tapatalk
I'm on NRD90M same as u we will get the update to U also jus give it time
Sent from my Nexus 6P using Tapatalk
I installed NRD90M through beta and immediately un-enrolled.
Do i need to re-enroll in beta to get the NRD90U OTA update ?
Salim Zhulkhrni said:
I installed NRD90M through beta and immediately un-enrolled.
Do i need to re-enroll in beta to get the NRD90U OTA update ?
Click to expand...
Click to collapse
No, the OTA will come to your device soon and if you can`t wait flash the firmware in fastboot.
Now that the official release is out is it possible to dirty flash, unenroll from beta and not lose data? I know unenrolling will instantly result in a wipe... Which is kinda ridiculous. Windows phone just leaves you on your current build till public releases catches up... Is there a way to do this on android and still get OTA official updates?
Sent from my Nexus 6P using Tapatalk
letrain02 said:
Now that the official release is out is it possible to dirty flash, unenroll from beta and not lose data? I know unenrolling will instantly result in a wipe... Which is kinda ridiculous. Windows phone just leaves you on your current build till public releases catches up... Is there a way to do this on android and still get OTA official updates?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Unenroling now won't wipe the phone as it did on the beta releases.
It will just sit and wait for nrd90u to roll out? Then flash OTA without losing data? Do I need to fastboot nrd90u? Or just wait?
Sent from my Nexus 6P using Tapatalk
All the little warning says is "if your on a beta version" we will OTA flash and erase all. Wish it was more clear on their website. Technically nrd90m is the beta version.
Sent from my Nexus 6P using Tapatalk
Thanks for the help.
Sent from my Nexus 6P using Tapatalk
I'm still on NRD90M and still enrolled in the Beta Program.
I'm just waiting for the OTA to be pushed to my phone.
If you want you can go ahead and Fastboot the NRD90U image and jus don't wipe your data u should be fine since u already on Nougat.
I wouldn't recommend dirty flashing as sometimes it can lead to fc's and such. But that's me I've never dirty flash period. But I know some peeps do it and have no issues.
But far as I know I haven't heard of anyone that's on NRD90M receive the OTA update to NRD90U yet..
Sent from my Nexus 6P using Tapatalk
I may be missing something, but according to Google, NRD90M is an official release as it is not prefixed with NP. It states, all beta builds are prefixed with NP.
'Ok. I tried to unenroll when google first said they released N officially but it wanted to flash OTA downgrade me and wipe data. I'm guessing because it hadn't been officially released for Nexus 6p yet. Now that it has been released officially. Even though a different build number, apparently it doesnt ask that anymore.
Sent from my Nexus 6P using Tapatalk
If you download the factory image, extract it and edit in notepad the flash-all.bat script with removing the -w behind update command at the end you will get up to the latest version without the need to wipe and unregister from the beta.
I unenrolled from the beta program and didn't get any notification to install a system update. I then flashed the official version posted by Google and wiped data on purpose to start fresh.
I wiped and flashed factory a few days ago, this morning unenrolled from beta. No notifications on my phone, checking for system update doesn't say download available.
Should mark this as solved but I can't edit the title in Tapatalk. Unenrolled, not notification like before. But the official nrd90u has come through OTA yet...or will it?
Sent from my Nexus 6P using Tapatalk
im pretty sure the NRD90M build is the official build along with the NRD90U
Not according to google....https://developers.google.com/android/nexus/images
It's solved now. No problems.
Sent from my Nexus 6P using Tapatalk
guys help. I was on the NRD90M build on the Nexus 6P. I got an OTA for the Septemeber Security Patch, installed it and now my build number has changed to NRD90T. Does anyone know what is going on?
Septemeber Security patch with an August kernel version?
So, if NRD90M is beta and I'm not in the beta program any longer, how do I get on official track without losing data? I'm not rooted and bootloader is locked.
Sent from my Nexus 6P using XDA-Developers mobile app
The understanding I've read from info in the beginning of the thread is to wait for OTA, or adb flash "official" and take out the -w...it's in an earlier post
Sent from my Nexus 6P using Tapatalk
What I mean is, will I get an OTA or do I need to manually flash one. And if manual, which do in flash? I haven't seen a definitive answer on what you should expect if on NRD90M. Wrist case, I re-join the beta, get a OTA then leave and get the OTA that wipes data.
Sent from my Nexus 6P using XDA-Developers mobile app
I was on NRD90M up until yesterday and I decided to go ahead and fastboot the NRD90U Factory Images back to all stock then flashed TWRP 3.0.2.2 made nandroid then flashed SuperSU 2.78 all good now.. only reason is BC nobody had a definite answer if I would receive a OTA or not so I went ahead now no more concern's.
But I can say for sure 90M and 90U are definitely different as I have noticed little things here n there..
Sent from my Nexus 6P using Tapatalk
Very strange. I'm on DP4. About 10 minutes ago I checked for an OTA to the new official 8.0 build and hey presto, up came the Android Oreo update available message. When I hit download and install, I got an error message and now the update is no longer available. Just says I have the latest version. Anyone else experience this?
I joined the beta program today. My version is 8.0.0. Is that beta or final?
Sent from my Pixel XL using Tapatalk
SpaceGooner said:
Very strange. I'm on DP4. About 10 minutes ago I checked for an OTA to the new official 8.0 build and hey presto, up came the Android Oreo update available message. When I hit download and install, I got an error message and now the update is no longer available. Just says I have the latest version. Anyone else experience this?
Click to expand...
Click to collapse
I'm having the exact same issue and Google's help don't know ****. She keeps telling me it's not even available even though I can clearly see the update smh
Sent from my Pixel XL using XDA Free mobile app
Mine is stuck like this, lol. I have a great WiFi signal and everything. Not sure what's up.
I have this and amazing Internet speeds.
Exact same issue here
Wonder if it's those that are on DP that are effected, anyone confirm they flashed OTA successfully via DP or N?
It has been removed and is supposed to be online again, that says Google. Waiting and relaxing
I'm now on the latest version according to the updates section. Meh, I'll factory install it in the morning.
According to other threads, they had problems with signature of the update packages being incorrect. They stopped otas, and are dropping them again, I believe.
Just a second ago the OTA was available again. Tried to download it and got the same error message as the first time around. Once again it has been replaced by your system is up to date. Some crazy weirdness definitely going on here. I think I'll try again tomorrow.
noidea24 said:
According to other threads, they had problems with signature of the update packages being incorrect. They stopped otas, and are dropping them again, I believe.
Click to expand...
Click to collapse
Ah, that would explain things.
I started a help session, and they said I needed to be unrooted for the OTA to be able to do anything. I'm going to try unrooting, but tbh I'll probably just end up flashing from the factory image.
SonarMonkey said:
I started a help session, and they said I needed to be unrooted for the OTA to be able to do anything. I'm going to try unrooting, but tbh I'll probably just end up flashing from the factory image.
Click to expand...
Click to collapse
That would be pretty obvious, you can't get system updates if you're rooted on literally any device.
richfreestone said:
That would be pretty obvious, you can't get system updates if you're rooted on literally any device.
Click to expand...
Click to collapse
I knew it wouldn't install, but it usually downloads it so that I can use Flashfire. This time around it seems that it won't even do that.
I have got 2 OTA URLs for build OPR6.170623.011/8.0.0 from my Australian Telstra carrier Pixel XL registered in Beta Program.
One is incremental from DP4, the other I'm not sure but is 951MB.
Will post them up here and update with the exact contents shortly...
64MB:
https://ota.googlezip.net/packages/.../75739c219338945fd6460465b0ec6346c56235ca.zip
Code:
ota-required-cache=0
ota-streaming-property-files=payload.bin:2654:68615126,payload_properties.txt:68617832:154,care_map.txt:569:156,compatibility.zip:772:1841,metadata:63:464
ota-type=AB
post-build=google/marlin/marlin:8.0.0/OPR6.170623.011/4283328:user/release-keys
post-build-incremental=4283328
post-timestamp=1502993522
pre-build=google/marlin/marlin:8.0.0/OPP4.170623.014/4187591:user/release-keys
pre-build-incremental=4187591
pre-device=marlin
951MB for OPR6.170623.012 (it disappeared before i could accept the OTA) (update - is now trying to push this OTA to my Telstra carrier Pixel XL which seems to be incorrect as I should be on the .011 build not .012):
https://android.googleapis.com/pack.../8cfe91d60eafcec2c74e3eef4c2506473b2d7187.zip
Code:
ota-required-cache=0
ota-streaming-property-files=payload.bin:2549:996875675,payload_properties.txt:996878276:154,care_map.txt:464:156,compatibility.zip:667:1841,metadata:63:359
ota-type=AB
post-build=google/marlin/marlin:8.0.0/OPR6.170623.012/4283428:user/release-keys
post-build-incremental=4283428
post-timestamp=1502994895
pre-device=marlin
From another post on XDA for OPR6.170623.012:
https://android.googleapis.com/pack.../80cafb69c50be0fb6ed197998bd7434b26155355.zip
Code:
ota-required-cache=0
ota-streaming-property-files=payload.bin:2654:52977084,payload_properties.txt:52979790:154,care_map.txt:569:156,compatibility.zip:772:1841,metadata:63:464
ota-type=AB
post-build=google/marlin/marlin:8.0.0/OPR6.170623.012/4283428:user/release-keys
post-build-incremental=4283428
post-timestamp=1502994895
pre-build=google/marlin/marlin:8.0.0/OPP4.170623.014/4187591:user/release-keys
pre-build-incremental=4187591
pre-device=marlin
In the US and just enrolled in Beta, got the update, unenrolled in Beta and all is good.
dhaugru said:
In the US and just enrolled in Beta, got the update, unenrolled in Beta and all is good.
Click to expand...
Click to collapse
I tried that, still no OTA update, it's been about 2 hours.
Sent from my Pixel XL using Tapatalk
imnuts said:
I tried that, still no OTA update, it's been about 2 hours.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
No update for me either.
Sent from my Pixel XL using Tapatalk
imnuts said:
I tried that, still no OTA update, it's been about 2 hours.
Click to expand...
Click to collapse
millerd79 said:
No update for me either.
Click to expand...
Click to collapse
And it's coming down now, almost 3-4 hours after signing up for the beta.
Sent from my Pixel XL using Tapatalk
I haven't seen an OTA update since I factory reset back in June... I have manually pushed all my otas, it's getting annoying,. Anyone know why I wouldn't receive otas normally?
Sent from my Nexus 6P using Tapatalk
coolasice1999 said:
I haven't seen an OTA update since I factory reset back in June... I have manually pushed all my otas, it's getting annoying,. Anyone know why I wouldn't receive otas normally?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you are enrolled in beta program but are using non-beta stock, you could try unenrolling from beta. My friend did it and he got an update instantly which otherwise he wouldn't.
NoobInToto said:
If you are enrolled in beta program but are using non-beta stock, you could try unenrolling from beta. My friend did it and he got an update instantly which otherwise he wouldn't.
Click to expand...
Click to collapse
I've never enrolled in the beta
Sent from my Nexus 6P using Tapatalk
coolasice1999 said:
I've never enrolled in the beta
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
There is no harm in checking.
Anyways, google improved ota system quite recently(around 1-2 weeks ago). When you manually check for ota, there is 100% chance that you will get the ota if it exists. It sounds too good to be true, but it is. Check that out.
So if you dont get ota, then something is really wrong.
NoobInToto said:
There is no harm in checking.
Anyways, google improved ota system quite recently(around 1-2 weeks ago). When you manually check for ota, there is 100% chance that you will get the ota if it exists. It sounds too good to be true, but it is. Check that out.
So if you dont get ota, then something is really wrong.
Click to expand...
Click to collapse
No OTA, says I'm up to date on Sept security patch
Sent from my Nexus 6P using Tapatalk
coolasice1999 said:
No OTA, says I'm up to date on Sept security patch
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I suggest you try enrolling and subsequently unenrolling from android beta program at android.com/beta
Maybe that will shift you to the proper ota queue?
NoobInToto said:
I suggest you try enrolling and subsequently unenrolling from android beta program at android.com/beta
Maybe that will shift you to the proper ota queue?
Click to expand...
Click to collapse
Tried that, got nothing. Swapped from my VZW sim to my projectfi sim. Still nothing. Says I'm up to date. Really not wanting to factory reset....
Sent from my Nexus 6P using Tapatalk
No answer for you. Just wanted to throw in that my updates seem to have quit after manually pushing Oreo.
so ... is anyone still on an older build and not seeing any updates? my other N6P hasn't received any security updates since July patch.... am i stuck? how can i fix? i was previously on the beta but i can't find the page to un-enroll...
I joined the beta 2 days ago and never received any update. I'm going to have to reset and see what happens....
Sent from my Nexus 6P using Tapatalk
coolasice1999 said:
I joined the beta 2 days ago and never received any update. I'm going to have to reset and see what happens....
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
can you share the link so i can try as well?
---------- Post added at 01:25 PM ---------- Previous post was at 01:16 PM ----------
2x4 said:
can you share the link so i can try as well?
Click to expand...
Click to collapse
nevermind, got it
https://www.google.com/android/beta?
2x4 said:
so ... is anyone still on an older build and not seeing any updates? my other N6P hasn't received any security updates since July patch.... am i stuck? how can i fix? i was previously on the beta but i can't find the page to un-enroll...
Click to expand...
Click to collapse
Definitely unenroll. No reason to be in the beta program now. Even if you are stock with a locked bootloader you can manually sideload a full OTA. There are many tutorials on how to do this.
v12xke said:
Definitely unenroll. No reason to be in the beta program now. Even if you are stock with a locked bootloader you can manually sideload a full OTA. There are many tutorials on how to do this.
Click to expand...
Click to collapse
i'm actually asking for my second N6P which my mom uses, which is why i'm hoping there's a way to fix this without having to sideload since i'd have to do it with her via TeamViewer....
is it necessary to unlock the bootloader to do this or can i just flash the latest factory image or OTA with the bootloader locked via ADB?
Linkk to the beta program is https://www.google.com/android/beta
Getting the OTA's fine. Latest one I have is September 5th, so expecting Octobers any time soon.
Guys, I mentioned beta program because you are supposed to UNenroll from it to get normal updates. Remember that.
NoobInToto said:
Guys, I mentioned beta program because you are supposed to UNenroll from it to get normal updates. Remember that.
Click to expand...
Click to collapse
I was never enrolled up until two days ago,. Never received an OTA. Joined beta, waited 48 hrs and unenrolled... Still never received OTA... On Sept Oreo patch which I manually flashed.....
Sent from my Nexus 6P using Tapatalk
coolasice1999 said:
I was never enrolled up until two days ago,. Never received an OTA. Joined beta, waited 48 hrs and unenrolled... Still never received OTA... On Sept Oreo patch which I manually flashed.....
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It was just a suggestion. It didn't work for the OP either. I wonder what could be the real problem.
What carrier are you guys on btw?
NoobInToto said:
It was just a suggestion. It didn't work for the OP either. I wonder what could be the real problem.
What carrier are you guys on btw?
Click to expand...
Click to collapse
Both projectfi and vzw
Sent from my Nexus 6P using Tapatalk
Factory reset and the update came right away,. Something in my data was stopping it... We shall see with the next one if it comes automatically in November...
Sent from my Nexus 6P using Tapatalk
I also haven't received an OTA update in quite a while. The latest update I was able to receive OTA is the August patch.
I enrolled and un-enrolled from the beta program with the hope that the Oreo OTA would push but only got 7.1.2.
It's a little unusual. I factory reset also after un-enrolling just to see clean it out, to get rid of any bugs that be preventing the OTA. Didn't work.
I would rather not have to sideload the OTA since I always make mistakes with ADB and command prompt.
I am on Project Fi fyi.
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.