Pixel stuck on October update - Google Pixel Questions & Answers

Hi
Sorry if this has already been addressed. My Pixel is stuck on the October update and has not received the November update. Tried pressing system update six/ten times in a row to no avail. Phone says it's up to date.
Other than sideloading any ideas? Is the device faulty?
Contacted Google who say the phone should have received the update on 19 November and advised to wait until the December update is released. If it doesn't update then they will ask for a bug report.
My Nexus Player updated a few days after the release but it never updated to the October one.
Thanks for any help or advice.

Just side load it, you are not alone. Seems to be pretty common.

Still Stuck? I didn't get the update myself until yesterday 11/30. Might try it again.

If yall are still waiting, most pixel (non xl) users were complaining of this. Apparently they just released the ota for the Pixel, so we should be getting it soon.

IF, you need a step by step guide, check my video post here: https://www.youtube.com/watch?v=wRL_L6vt5lU I cover both, OTA sideload and factory image flashing. Fyi if you look at the factory image, there's a mistyped command in the video, but the video also has the text correction. Just want to make sure you notice that while watching the video. Hope this helps!

Related

Google beta program.

Enrolled in the google beta program but I'm not getting the ota for my pixel 2. It's been 72 hours. I got the ota for my pixel c within minutes. Anyone know how to force the ota or something?
It appears that people on the November security patch for 8.0 are not getting the 8.1 beta OTA pushed to them. Most likely need to wait for DP2 at this point.
Hopefully the preview 2 comes out soon.
I just signed up a few minutes ago, refreshed the system update screen on my pixel 2, and the update popped right up
flakmunkey said:
I just signed up a few minutes ago, refreshed the system update screen on my pixel 2, and the update popped right up
Click to expand...
Click to collapse
You were on November security patch?
gm007 said:
You were on November security patch?
Click to expand...
Click to collapse
Did the novembver security patch require any weirdness to get? I only ask because while i'm not sure if I had that installed, I do know for sure I had all of the most current OTA updates. I got the phone from Best Buy last Thursday and there was a software update when I first booted it. I check for new software this morning and it told me I was up to date. I then proceeded to sign up for the beta program, refreshed the update page that said I was up to date, and the 8.1 update was waiting for me
flakmunkey said:
Did the novembver security patch require any weirdness to get? I only ask because while i'm not sure if I had that installed, I do know for sure I had all of the most current OTA updates. I got the phone from Best Buy last Thursday and there was a software update when I first booted it. I check for new software this morning and it told me I was up to date. I then proceeded to sign up for the beta program, refreshed the update page that said I was up to date, and the 8.1 update was waiting for me
Click to expand...
Click to collapse
Some people didn't get November update and i read somewhere that they pulled the 8.1 preview for pixel 2 , that's why I'm asking.
http://www.androidpolice.com/2017/1...android-8-1-developer-preview-factory-images/
flakmunkey said:
I just signed up a few minutes ago, refreshed the system update screen on my pixel 2, and the update popped right up
Click to expand...
Click to collapse
Well I'm 4 days in and still no ota ?
Sent from my Google Pixel 2 using XDA Labs
mrnovanova said:
Well I'm 4 days in and still no ota ?
Sent from my Google Pixel 2 using XDA Labs
Click to expand...
Click to collapse
If it makes you feel any better I am in the same situation. 4 days no OTA. I am on the November Security patch.
Is it worth it to try flashing factory images to get back to September and then try to get the beta OTA?
I can confirm rolling back to September images does allow you to immediately get the prompt to download the 8.1 beta.
If you are impatient like me, it's worth a shot.
I will add this: Make sure your ADB and Fastboot are up to date! I ended up softbricked/stuck in the bootloader for awhile after flashing back to the September images. I finally figured out my old version fastboot was the problem. After getting the latest fastboot/adb it was a breeze.

Not receiving Google Security Updates

I have a Pixel 2 with the bluetooth connection issues. When I go look for the Google Security Updates, it says that I am up-to-date. I did a factory reset and tried to get the update afterwards, but it has the same issue where it is not finding the update.
Has anyone successfully been able to find a way to get the phone to find the updates, or should I get a hold of Google to return the phone?
Thanks,
Mark
I have also not received the November security update, every time I check it says it is up to date. I bought the unlocked version from the Google Store and am using Verizon.
This reddit thread shows a way to potentially force it, i have not tried it yet -- https://www.reddit.com/r/GooglePixe..._on_september_security_patch_regular_pixel_2/
UPDATE: I have tried it, and it did not work
I also tried it and it didn't work. I would be more patient, but the Bluetooth issue is quite frustrating. I'll give it a few more days then will contact Google again for a replacement device.
Despite they say that the check for updates button now always bring the latest update. There's a lot of people that doesn't get it when pressed and have to wait a few days or weeks to get them like always.
Things that could affect the check for update button:
- Not being 100% stock un-rooted
- Being subscribed to the Android Beta
- and sometimes if you start executing an OTA update and it fails you might need to wait a few days for a second chance.
None of these reasons apply to you obviously but just giving my experience.
The best 100% official workaround to get now the update is to install the update manually using the stock recovery:
https://developers.google.com/android/ota
Sent from my Pixel 2
thesebastian said:
Despite they say that the check for updates button now always bring the latest update. There's a lot of people that doesn't get it when pressed and have to wait a few days or weeks to get them like always.
Things that could affect the check for update button:
- Not being 100% stock un-rooted
- Being subscribed to the Android Beta
- and sometimes if you start executing an OTA update and it fails you might need to wait a few days for a second chance.
None of these reasons apply to you obviously but just giving my experience.
The best 100% official workaround to get now the update is to install the update manually using the stock recovery:
https://developers.google.com/android/ota
Sent from my Pixel 2
Click to expand...
Click to collapse
Are the ones marked Verizon for the Verizon version, or also for people who bought the unlocked version and are using Verizon? My current version is OPD1.170816.010, which is not a Verizon version, so I guess I would want OPD1.170816.025 since the version I currently have is not the Verizon version? Still find it crazy that an update would come this late, never got them this late on my 5X. I never understood the point of if I manually check I cant just auto get the OTA (I know there was that article somewhat recently that they are moving to that though).
I got 023 over the air automatically on my Pixel 2. Haven't downloaded the OTA from the developer site some I got this phone.
OPD3.170816.023, Nov 2017, Verizon
I too bought unlocked from Google but using on Verizon. I was on .10 and waited weeks after release for a push, but it never came. So I manually flashed the .25 update. No issues, working perfectly, with the Nov security update.
I am still on september security update. Got a Pixel 2 (Verizon). Hope they hurry up. Its almost december
Sorry to bring up an old thread, but I have the same problem ever since I cleared the Google Play Services' data through the app's interface. The OTAs just stopped coming. I have been flashing full OTA images since August, but it is getting really annoying. I still didn't get the November's patch, nor the December's one. It always says my system is up to date. I didn't try clearing the Play Services Framework's data, as it isn't effective and only causes trouble. I tried clearing the Play Services' data though many times, but it doesn't help.
I am rooted with Magisk. Everything else is fully stock (rom, kernel, recovery) and I do pass the Safety Net test.
If anyone has a solution to this problem, please share it with the world. I don't believe that I am the only one with this problem.
Same here, rooted pixel 2, currently away from pc so would love to update from phone
Sent from my Pixel 2 using Tapatalk
I've had the same problem with my P2XL for the last couple of month. I have just been downloading the full updated firmware and flashing from my computer, but it would be nice to be able to update while travelling with no computer.
Details:
-Magisk rooted, everything else stock, including recovery.
-Google edition - I used to get updates, not sure what changed.
-Not on beta. I even tried signing up and then unsubscribing. No help.
-"Check for update" button does nothing.
-Clearing data on Google Services Framework doesn't help.
-I'm in Mexico on Telcel, but updates have worked in the past.
Haven't been receiving OTA updates since flashing the Pie factory image in August.
Device is stock apart from being rooted with Magisk.
Update button always says system is up to date, so I eventually sideloaded the latest OTA image at the end of November but still didn't receive any update notification in December.
I'm starting to suspect the update manager in Pie is detecting root or something, because I used to receive updates just fine on Oreo, and everyone else who has this problem also seems to be rooted.

On August 5 patch level, shows up to date

Hi
I have standard Pixel 2 with Magisk installed (for thethering restrictions bypass). I finally got around to getting OTA from July to August one. So got Android 9. I followed the OTA update guide for Magisk. Everything got installed, but now it keeps saying my phone is up to date. Even thought it's still on August Security patch. Anyone else experienced this?
I can just download rest of the patches manually and side load, but I rather avoid doing it.
Thanks
Were you on the beta update program for P. If so have you opted out? I had to opt out before I got this month's update. Didn't realise you had to do this.
Sent from my Pixel 2 using Tapatalk
Nope. Just getting everything through OTA.
Yeah the same thing happened to me
UDPoster said:
Hi
I have standard Pixel 2 with Magisk installed (for thethering restrictions bypass). I finally got around to getting OTA from July to August one. So got Android 9. I followed the OTA update guide for Magisk. Everything got installed, but now it keeps saying my phone is up to date. Even thought it's still on August Security patch. Anyone else experienced this?
I can just download rest of the patches manually and side load, but I rather avoid doing it.
Thanks
Click to expand...
Click to collapse

XT1900-1 November security patch link request

Does anyone have a link to the new Nov security patch that came through last night for Fi?
Even with uninstalling Magisk, my phone doesn't want to install the update, so i'll just flash manually with fastboot.
I've checked https://mirrors.lolinet.com/firmware/moto/payton/official/FI/ but haven't seen the Nov firmware yet.
Thanks in advance,
You will either have to do a factory reset on your current version and root after you apply the OTA November update or wait a few weeks for it to be posted to Lolinet.
NeoandGeo said:
You will either have to do a factory reset on your current version and root after you apply the OTA November update or wait a few weeks for it to be posted to Lolinet.
Click to expand...
Click to collapse
Same situation here as Enemy Lines, but to be clear N&G, the only way updating this security patch is happening is with a factory reset, correct? Either one right now to install the OTA, or flashing the full updated firmware once it's on Lolinet which means a reset as well. According to Magisk, it should handle this with no problem. But apparently can't in this case.
lolinet should have it in 2-3 weeks, but that would mean a full flash.
lmsa doesn't have it.
I don't know if it is possible to download an OTA sec patch - haven't seen it offered to me.
I trust you know that if you have a modified recovery, like twrp, the patch will fail because the install needs to reboot through (stock) recovery to finish installing it.
I just went ahead and reflashed the Oct rom (minus the userdata delete), let the Nov update install, then repatched for magisk.
I must have changed something in the system partition and didn't realize it ?*
KrisM22 said:
lolinet should have it in 2-3 weeks, but that would mean a full flash.
lmsa doesn't have it.
I don't know if it is possible to download an OTA sec patch - haven't seen it offered to me.
I trust you know that if you have a modified recovery, like twrp, the patch will fail because the install needs to reboot through (stock) recovery to finish installing it.
Click to expand...
Click to collapse
Didn't know that, but suspected that was the case. Thanks for confirming. Guess I'll just full flash it when it hits Lolinet.
If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like. I will post this as a new thread.
Don't disagree Khris. Heck I ran 8.0 until about a month ago and flashed up to 9.0. What I really want is to get that damned annoyed perpetual update from interrupting my phone every five minutes. I turned off Automatic Updates in Dev Ops but that doesn't seem to have helped. Anyone have a useful solution.
SilverPosition said:
Don't disagree Khris. Heck I ran 8.0 until about a month ago and flashed up to 9.0. What I really want is to get that damned annoyed perpetual update from interrupting my phone every five minutes. I turned off Automatic Updates in Dev Ops but that doesn't seem to have helped. Anyone have a useful solution.
Click to expand...
Click to collapse
LOL I have heard that complaint before and I know of no way to stop the notification. Go for it!!!
I'm going to give Enemy's October approach a try. It's all tediously [un]necessary, I suppose. Anyway, thanks for everyone weighing in. Always useful stuff here.
That should work with no problem. and no waiting!
EDIT - I found when I was doing that a lot, I used Nova launcher as it would save apps and desktop and made setup after flash much faster.
If you are just looking to get rid of the update notification you can use Titanium Backup or similar to freeze the 'Motorola Update Services' process.
Thanks Kris and Neo. Nova launcher certainly helps and I appreciate the tip with Titanium Backup and Motorola Update.
That said, here's this for anyone interested:
Like Enemy Lines I went to Lolinet and downloaded the October firmware. I used @munchy_cool’s useful firmware flash guide because he’s got the right Flash-All.sh or .bat scripts in his links. (Link below.) Before flashing I opened the Flash-All.sh and deleted the following command: ./fastboot erase userdata
That preserved my stuff which I’d have lost in a straight flash or factory reset. I downloaded the November patch, updated, reinstalled TWRP and Magisk.
Mac people, once you’ve opened terminal, you may have to activate the Flash-All.sh script with the following command and your password: sudo chmod +x flash-all.sh
If you’re unsure about any of this, read Munchy_Cool’s guide and watch the included vid.
https://forum.xda-developers.com/mo...-to-flash-official-factory-t3808348?nocache=1
No idea why this posted twice.
Thanks!
The stock firmware repository updated a few days ago, new date showing for last activity. No new uploads as of yet, but I believe the updated date precedes the actual firmware being available.
39-6-2 for fi - yeah that's the "Nov 1" one I ota'ed on 11-27, and 11-27 is the date of the ota. So it takes about 4 weeks for us to get it and another 3 weeks for lolinet to post it. So, yeah, if you're in a rush, grab the latest and then let it ota. - at least on retus ATT prepaid...

Question issues with updates

Hi, i have a Pixel 7 pro (no carrier, eu, stock, locked bootloader) and am experiencing the following:
until yesterday i was running:
security update: november
play system update: october
os: october
i tried with the pixel repair tool to no avail. so, yesterday i applied for the beta... installed, rebooted (many times) and... still stuck with the stable from october. i then downloaded the official ota and applied it... now i have
security update: december
play system update: october
os: december
now, why the play system won't update? also, the privacy and security settings are still separated... for what is worth, the free VPN has already been active for a few days.
is my OS broken? should i try with sideloading the update again? i'm not in the mood for a reset and i have many apps (banking too) which would be a hassle to config again.
ujh said:
Hi, i have a Pixel 7 pro (no carrier, eu, stock, locked bootloader) and am experiencing the following:
until yesterday i was running:
security update: november
play system update: october
os: october
i tried with the pixel repair tool to no avail. so, yesterday i applied for the beta... installed, rebooted (many times) and... still stuck with the stable from october. i then downloaded the official ota and applied it... now i have
security update: december
play system update: october
os: december
now, why the play system won't update? also, the privacy and security settings are still separated... for what is worth, the free VPN has already been active for a few days.
is my OS broken? should i try with sideloading the update again? i'm not in the mood for a reset and i have many apps (banking too) which would be a hassle to config again.
Click to expand...
Click to collapse
I updated yesterday to Dec.Release, I I'm with this. To be honest, don't know if is as expected
well, fair enough... it may be a slow rollout of single features...? -.-
ujh said:
Hi, i have a Pixel 7 pro (no carrier, eu, stock, locked bootloader) and am experiencing the following:
until yesterday i was running:
security update: november
play system update: october
os: october
i tried with the pixel repair tool to no avail. so, yesterday i applied for the beta... installed, rebooted (many times) and... still stuck with the stable from october. i then downloaded the official ota and applied it... now i have
security update: december
play system update: october
os: december
now, why the play system won't update? also, the privacy and security settings are still separated... for what is worth, the free VPN has already been active for a few days.
is my OS broken? should i try with sideloading the update again? i'm not in the mood for a reset and i have many apps (banking too) which would be a hassle to config again.
Click to expand...
Click to collapse
Android Pixel updates get rolled out in phases, meaning it's not available for everyone at the same time. Maybe you need to wait an hour, maybe a day, maybe a week.
If you feel the need to immediately update at the earliest time possible, you should look into ADB flashing.
Morgrain said:
Android Pixel updates get rolled out in phases, meaning it's not available for everyone at the same time. Maybe you need to wait an hour, maybe a day, maybe a week.
If you feel the need to immediately update at the earliest time possible, you should look into ADB flashing.
Click to expand...
Click to collapse
That's true... But about the settings tabs not yet unified?
ujh said:
That's true... But about the settings tabs not yet unified?
Click to expand...
Click to collapse
I updated to december and also have not gotten that "feature", it's likely that it's a google sided switch/ App update that is necessary to change that, meaning it's not at all necessary to update the firmware of the phone factually, but Google still wants the "feature drop" as a sales argument, hence the big focus on the firmware updates, even though the actual features could easily be delivered as in-app updates.
yeah... i read somewhere else that that "feature" and others will be available with an upcoming update within this month... lol
ujh said:
That's true... But about the settings tabs not yet unified?
Click to expand...
Click to collapse
I think that's part of the PermissionController APK, which is part of the PermissionController Mainline module. So I think Google needs to update that Mainline module before we get it.
However, you should be able to toggle the flag on with this adb command...
adb shell cmd device_config put privacy safety_center_is_enabled true

Categories

Resources