I'm running a completely stock Nexus 5 that has never been rooted. It's gotten all updates going back to my purchase in November 2013, but has recently missed the last two security updates; still sitting on Build MMB29V (March 1, 2016), I've missed the midMarch and April updates. Any idea how I get back into the Google update queue? Don't think it's a matter of impatience. I know I can manually apply updates, would prefer to stay OTA. I've cleared the cache in Recovery as well as checked for updates while in Safe Mode. No go. Any other ideas?
You can sideload OTA via adb. That's very simple.
Sent from my Nexus 5 using Tapatalk
Very simple indeed, updated without a hitch and no user data erased. Glad I now know the process. Many thanks.
Related
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.
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.
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
Anyone been able to revert to Android 10 from the developer preview without unlocking and using factory images? OTA back to Feb not working for me. Am I screwed into using it untill March OTA comes out since it will be newer? Any help would be appreciated
Sent from my Pixel 3a using Tapatalk
jmtjr278 said:
Anyone been able to revert to Android 10 from the developer preview without unlocking and using factory images? OTA back to Feb not working for me. Am I screwed into using it untill March OTA comes out since it will be newer? Any help would be appreciated
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
I just put my 3 XL back to stock before selling it. I like my little 3a so I'm keeping this one.
I had to unlock -> flash factory firmware -> relock. Data is wiped definitely. You cannot downgrade with an OTA it will absolutely need reflashed and wiped with a factory image.
jmtjr278 said:
Anyone been able to revert to Android 10 from the developer preview without unlocking and using factory images? OTA back to Feb not working for me. Am I screwed into using it untill March OTA comes out since it will be newer? Any help would be appreciated
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
I'm not surprised that you can't go back to the Feb OTA update and this means that the March OTA update isn't going to work either.
The "issue" is the fact that you have changed major Android versions - from Android 10 to Android 11. You can generally move to a higher version using an OTA update, but you can't downgrade or move back to a lower version without flashing a factory image. Even if the image is pushed out via an OTA update (like would happen if you revert to stock from a beta release), the phone still has to go through a factory reset to ensure everything is downgraded to the lower version. This is something that the regular monthly OTA updates aren't set up to do.
Long story short, you have two options - one is to go ahead an unlock the bootloader and flash the Android 10 factory image. The second is to wait until the Android 11 beta program starts, enroll in it and install the Android 11 beta, and then opt out of the program and be reverted to Android 10. To be honest however, I'm not 100% this will work because I really don't know if you can move from the Android 11 Developer version to the Android 11 beta version via an OTA update. In either case, you are going to experience a factory reset and loose all of your data and information, so plan ahead and backup anything you want to keep.
Solved. Unlocked bootloader, flashed factory Feb. Relocked. All set. Had issues work some apps and Android pay. All expected.
Sent from my Pixel 3a using Tapatalk
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