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
Related
Just received JDQ39.I537ucuamf3 OTA, anyone have any idea what it was? Probably just made it even harder to root lol.
arcticwolf8 said:
Just received JDQ39.I537ucuamf3 OTA, anyone have any idea what it was? Probably just made it even harder to root lol.
Click to expand...
Click to collapse
I usually don't take OTA updates if I have any plans of rooting or keeping root.
U.S. localized versions of the latest MEA/MF2 branch of Samsung official builds.
Check over in the i9505 threads for more info. It's possible some things have been tweaked for AT&T, but probably not a whole lot.
That update will probably allow app2sd functionality, not to mention the "purple smearing" effect some have complained of, and a few other little updates.
But as the other poster said, I wouldn't flash it until it's confirmed that it doesn't patch the loki aboot exploit. Otherwise, you can say goodbye to custom roms and root.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Questions go in Q&A
Thread moved
Unfortunately the update is FORCED. In mine there was no way to not accept it. If you hit cancel it just reboots and installs anyway. So not much choice on not taking it...
It does include app2sd though. Which is nice.
Sent from my SAMSUNG-SGH-I537 using Tapatalk 2
JasonJoel said:
Unfortunately the update is FORCED. In mine there was no way to not accept it. If you hit cancel it just reboots and installs anyway. So not much choice on not taking it...
It does include app2sd though. Which is nice.
Sent from my SAMSUNG-SGH-I537 using Tapatalk 2
Click to expand...
Click to collapse
Only forced if you're completely stock and un-rooted.
At a bare minimum, you should root, and freeze the appropriate OTA update apps to prevent that kinda thing.
Again, AT&T will eventually patch the loki-exploit, and possibly at the same time roll out "root defeating" kernels.
It's just a matter of time.
There isn't an option but to be completely stock and unrooted with this phone yet unfortunately.
arcticwolf8 said:
There isn't an option but to be completely stock and unrooted with this phone yet unfortunately.
Click to expand...
Click to collapse
Right. Thus my statement that we don't have a choice but to take the update on the S4 Active (right now at least).
Sent from my SAMSUNG-SGH-I537 using Tapatalk 2
It seems the update will only download on wifi, so if you want to avoid taking it in hopes that root comes out soon, do not use wifi.
Sent from my SAMSUNG-SGH-I537 using xda premium
_MetalHead_ said:
It seems the update will only download on wifi, so if you want to avoid taking it in hopes that root comes out soon, do not use wifi.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
God dang it! I wish I read this thread BEFORE accepting the update. Now I really hope AT&T or Samsung has not patched anything that prevent root.
I cannot NOT use Wifi since I have very limited data plan...
Has it ever happen in the past, at least with AT&T phone, that they send OTA update that PREVENT rooting the phone EVER?
Don't fret. We have some mighty fine developers here. You will be able to root it.
Shammyh said:
U.S. localized versions of the latest MEA/MF2 branch of Samsung official builds.
Check over in the i9505 threads for more info. It's possible some things have been tweaked for AT&T, but probably not a whole lot.
That update will probably allow app2sd functionality, not to mention the "purple smearing" effect some have complained of, and a few other little updates.
But as the other poster said, I wouldn't flash it until it's confirmed that it doesn't patch the loki aboot exploit. Otherwise, you can say goodbye to custom roms and root.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
LCD screens don't suffer from the purple smearing anyway. That's just something that AMOLED screens do. No way around it except to change the colors a bit. Which was all they did for the GS4.
TenEightyPee said:
[[[[[[[[[[[[[[[[[[[[[[[[[ ===== ]]]]]]]]]]]]]]]]]]]]]]]]
UNROOT and RETURN TO STOCK:
File Name: Oneclick_I537UCUAMF1.7z
MD5: 5860A429420FF9029C8CF687F43E3D83
Password: rootzwiki
-deleted since I'm new and cant post links-
[[[[[[[[[[[[[[[[[[[[[[[[[ ===== ]]]]]]]]]]]]]]]]]]]]]]]]
Click to expand...
Click to collapse
I never took the update (I didn't connect to wifi so it didn't force me to update) but now I want to update it. However, when I hit the update button it tells me that 'the software update was interrupted' and won't download the new FW. If I hit it again it says I have to wait another 24 hrs. I tried changing the date to a day ahead but it still failed. I was able to update the wifes phone no problem but I accepted it as soon as it notified me.
Is the above link the current FW? I see the name is UCUAMF1 but mine came with UCUAMF2 from the store... I'd rather just update the FW since it appears everyone else got forced to update but can still root it.
Edit: Phone fixed itself overnight connected to wifi.
S4 Active, Custom ROM
Hi friends, im kinda new at this i have an S4 active and i need to download the Custom rom to flash it again from factory its the AT&T version but the baseband says I537UCUAMF3 and i cant quite find were to download if from. Hope any of you can help me if this isnt the right place for the question sorry
Wow. These updates are coming fast.
https://twitter.com/Motorola/status/403621158362161152
congrats to tmo users. Still waiting for the at&t roll out.
Yep. Getting it on the GSM Dev Edition right now.
Getting mine too!
Sent from my XT1053 using XDA Premium 4 mobile app
Not available to me, as I'm on the 4.4 leak.
I'd flash back to stock right now, but the USB cable I have with me has been flaking out all day.
I'm excited to see if the official release fixes some of the issues I've been having with video playback. I'm getting seg-faults from several players while trying to decode MKVs. (Various files, some h.264 and some webm.)
---
I'm super impressed with how Motorola has been handling the 4.4 rollout.
Just got the Update Available pop-up on T-mo, non-Dev edition.
OH EM GEE!
I JUST got my Moto X yesterday and spent all morning unlocking the bootloader, flashing TWRP and doing a full backup. I figured 4.4 was at least a few weeks out (like an idiot).
I just caused myself a lot of work. **sigh** time to start researching how to get back to stock to upgrade.
-Collin-
Can someone post a screen shot of the build number and kernel date?
Sent from my XT1053
phositadc said:
Can someone post a screen shot of the build number and kernel date?
Sent from my XT1053
Click to expand...
Click to collapse
I guess this doesn't help, but it has the software version:
https://www.dropbox.com/sc/ztzaymkqvs8sjp3/ix_OoJmjA_
-Collin-
Actually that does help. It's a newer version than the leak. Which means all the time I spent setting up the leak is a waste since now I need to return to stock to get the OTA!
Sent from my XT1053
phositadc said:
Actually that does help. It's a newer version than the leak. Which means all the time I spent setting up the leak is a waste since now I need to return to stock to get the OTA!
Sent from my XT1053
Click to expand...
Click to collapse
Exactly! Well, you probably have more work than me though as I'm on custom-recovery 4.2.2.
So, how can I save this update for us? Could we then flash?
-Collin-
phositadc said:
Can someone post a screen shot of the build number and kernel date?
Sent from my XT1053
Click to expand...
Click to collapse
For anyone that needs the build number and screenshot:
CollinFX45 said:
Exactly! Well, you probably have more work than me though as I'm on custom-recovery 4.2.2.
So, how can I save this update for us? Could we then flash?
-Collin-
Click to expand...
Click to collapse
I'm also curious about this as I am unlocke, rooted, and with a custom recovery but not on the leak.. would i just have to get the stock recovery?
elijahah said:
I'm also curious about this as I am unlocke, rooted, and with a custom recovery but not on the leak.. would i just have to get the stock recovery?
Click to expand...
Click to collapse
That's what I am thinking. I backed up my stock recovery from another version of the Moto X I had (Mexico Nextel version) and I wonder if I could flash that right now, then unroot, then take the OTA.
Worth a try? Worst case is that I have to use RSDLite and start over.
-Collin-
I just installed it. It does feel faster than before. I dont have any lag on the unlock like some people were complaining about. New camera focus is nice
sleepyguy007 said:
I just installed it. It does feel faster than before. I dont have any lag on the unlock like some people were complaining about. New camera focus is nice
Click to expand...
Click to collapse
The lag doesn't seem to always occur. I only get it now and then, no idea when or if it will happen. It might take a day or two before you see it.
Well that came out of nowhere. Updating now.
Argh. No luck flashing the stock recovery, unrooting and then trying to take the OTA update. It booted into stock recovery, installed the update halfway, gave an "error" and then rebooted and said the update failed. Darn, I guess something must have changed in the system files to cause an error with the update
Guess I have to wipe it clean with RSDLite and do this the hard way.
-Collin-
got my update on gsm dev edition that's running on at&t...
interesting cause I though my update would come direct from Motorola and not be tied to any specific carrier release...
CollinFX45 said:
Argh. No luck flashing the stock recovery, unrooting and then trying to take the OTA update. It booted into stock recovery, installed the update halfway, gave an "error" and then rebooted and said the update failed. Darn, I guess something must have changed in the system files to cause an error with the update
Guess I have to wipe it clean with RSDLite and do this the hard way.
-Collin-
Click to expand...
Click to collapse
Same here. Just finished going back to stock with rsd downloading update now
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!
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.