I just received OPWS27.1.2 OTA on my Moto X4 Android 1 edition on Project Fi.
Got it last night on unlocked xt1900-1 on Project Fi. ~85MB and took a few moments to install.
Related
I purchased the small Pixel from Google store and have Verizon service and my Pixel is currently on NDE63P, it is rooted and running elemental X kernel. I have attempted numerous times to sideload NDE63V but for some reason am unable to get it to work. Is NDE63V the correct build I need to update to and why would my phone be on a Verizon build (NDE63P) when I purchased it from google.
Thanks in advance
Update: I now managed to incrementally sideload to the latest Oreo from the June Nougat I was stuck on.
Pixel purchased through Project FI. NOT rooted, bootloader LOCKED.
Summary on what worked for me:
-Was stuck on the June Nougat build some months now: 7.1.2 build NKG47L, Jun 2017, T-Mobile, Fi Carriers, and Rogers)
Sideloaded NKG47M (Jul 2017, T-Mobile, Fi carriers)
reboot
Sideloaded NKG47S (Aug 2017, T-mobile, Fi carriers, and Rogers)
reboot
Sideloaded OPR1.170623.026 (Sep 2017, Fi/Canada)
reboot
Sideloaded OPR1.170623.027 (Oct 2017, Fi/Canada)
reboot
I should note that at no point between the incremental OTAs was I offered an update. It was "Your system is up to date" the whole time. I understand some people are still waiting for the Oreo OTA but I should have at least been offered the July & August Nougat updates seeing as how the phone is not rooted, bootloader locked, no changes to system???
Anyhow, I'm now on the latest Oreo build and all is working fine so far. Maybe this post can help somebody with similar issue of not knowing which Oreo OTA to start off with coming from NKG47S
Hi,
I'm having trouble selecting an Oreo OTA file to sideload onto my Pixel. Here some background:
The google pixel is the first of my many android devices I have not rooted or unlocked the bootloader. I intend to keep it that way.
The Pixel in question was purchased directly from Google through Project Fi (when i registered for Project Fi). It is still running a project Fi sim.
The device is not rooted and the bootloader is locked.
Up until today (October 11th) the latest build version was NKG47L of 7.1.2 (with the June security updates. It has been showing "system up to date" and today I finally decided to sideload the most recent Nougat updates myself.
First I sideloaded NKG47M (Jul 2017, T-Mobile, Fi carriers), rebooted and then sideloaded NKG47S (August 2017, T-Mobile, Fi Carriers, and Rogers).
All went well and I'm now on the latest stable Nougat release.
I was hoping that sideloading the OTA updates would somehow get rid of this "system up to date" absurdity I've been having since the June build and offer me an update to Oreo. No such luck.
I'm sick of waiting and would like to sideload the Oreo OTA. I do NOT want to unlock bootloader, root or join the beta program.
The build naming has changed with the Oreo OTA files available from google and I'm completely lost as to which to sideload on my 7.1.2 NKG47S.
Aside from the carrier specific files obviously NOT for my original Google Project Fi device there are these 8.0.0 OTA files available:
- OPR6.170623.012, Aug 2017
- OPR1.170623.026, Sep 2017, Fi/Canada
- OPR3.170623.007, Sep 2017
- OPR3.170623.027, Oct 2017, Fi/Canada
- OPR3.170623.008, Oct 2017
The main thing that confuses me here is that there is no August build OTA file for 8.0.0 that specifies Project Fi as a carrier. I understand i need to go incrementally from the latest Nougat to the first Oreo for my device but I'm lost as to whether I should go with the August OPR6 build which does not specify any carriers or to go with the September build (OPR1) which lists project Fi carrier.
Anybody here can provide me with more insight or possibly have already sideloaded Oreo OTA onto a 7.1.2 NKG47S Pixel?
Go to settings>system>about phone and post your build number for me.
Milly7 said:
Go to settings>system>about phone and post your build number for me.
Click to expand...
Click to collapse
My current build number is in the OP.
It's NKG47S
jetfin said:
My current build number is in the OP.
It's NKG47S
Click to expand...
Click to collapse
Tough call. You said you purchased through Fi so I would try the Fi otas
Milly7 said:
Tough call. You said you purchased through Fi so I would try the Fi otas
Click to expand...
Click to collapse
Yeah, thanks, that's what I ended up gambling on and it worked fine. Going to update the OP.
Title says it all. Any reason why my pixel hasn't received November ota update?
Sent from my Pixel 2 XL using Tapatalk
Force it to check like for updates 5 or 6 times right in a row.
Has anyone got it? I still haven't on my Pixel.
Still haven't got it
Are you guys part of the beta program?
If you are exit the program, restart your phone and try again. If that doesn't work you can always sideload it via abd.
Download OTA here..
https://developers.google.com/android/ota#sailfish
I'm BL unlocked and trying to figure out how to sideload Nov OTA. I have twrp and magisk is installed.
You surely all know that November update for OG Pixel and Pixel XL was delayed and released only 6 days ago, because you all did some research before asking others to do it for you : November update google pixel
And probably because of possible Verizon specific-build, Verizon QA, and rollout phases it takes some time to get to the user, here is a very interesting read about Google devices and updates rollouts : Where is my update, and why?
Hey everyone,
I will clarify couple of things, which I was unable to find on the web.
Device: unlocked Pixel 3 XL , 64GB, bought directly from Google Canada. Bootloader is unlockable and sim unlocked.
I don't have any cell phone company contract either.
I was on Android 10 Beta 6.
I talked to google rep regarding which final Android 10 to get, .019 or .020, apparently those reps aren't allowed to tell you this information. Not sure why.
So he suggested to flash latest Android P (aug) and do an OTA update.
Steps:
1.) back up all my files.
2.) format from TWRP (since im Q beta 6) - gave me errors, but i guess it did go through?! not sure
3.) used "flash-all" for Android P august update.
4.)Completed all setup into the Android P.
5.) Went to settings to update Android, and got the Android 10 update.
6.)Android 10 update was completed after a restart.
7.) It shows Android 10, .019.
I had to flash Android P Aug 2019 before updating via OTA for Android 10 final version.
This was for Canadian Pixel 3 XL bought from Google Canada Store. It was sim unlocked and not carrier branded.
Hopefully it helps out others.
I have already updated to Android 12 but I just had a popup asking if I want to update to Android 12.
It is 1.69GB in size which from memory is the same size when I updated a few weeks ago.
What should I do next?
I will be testing that for you. I am already downloading the update and installing it.
Jpfonseca said:
I will be testing that for you. I am already downloading the update and installing it.
Click to expand...
Click to collapse
me too
Finished downloading. Installing now.
Strange, have the same updates, 1,88GB, I'll wait for you to check it out
Ditto here. please keep us updated.
At least it's not just me then
Thank god I found this, I was shocked to see the same update again. 1.69 GB for me, downloading now.
Same here, pixel 5 with android 12, asked to update again...
Nothing new, just verison changed to SP1A.211105.002.A1
same here ...pixel 4a 5g
Same here, Pixel 5 with android 12: it just asked to update again...
Mine installed ...
Previously : SP1A.211105.003
After : SP1A.211105.002.A1
According to their release details...
Pixel 4a 5G: Android 12 – SP1A.211105.003, SP1A.211105.002.A1 (Verizon, Verizon MVNO), SP1A.211105.004 (Telstra, Optus, Vodafone AU) – Factory image – OTA (2) (3)
Same here on a T-Mobile 4a 5G
Is there a way of asking Google directly what is going on?
voidby said:
Nothing new, just verison changed to SP1A.211105.002.A1
Click to expand...
Click to collapse
Same here. Before the update I was at SP1A.211105.002. I went ahead and took the update (reluctantly, but to get rid of the notification nag) and everything seems to be working ok. Then I went on Google's site and this verson is listed as 12.0.0 (SP1A.211105.002.A1, Nov 2021, Verizon, Verizon MVNOs)
My phone is NOT Verizon.
UPDATE: I just flashed the 12.0.0 (SP1A.211105.002, Nov 2021) factory image and I'm now back to where I was. Everything is working fine. I just feel a whole lot better with a version that is NOT for Verizon. I sure hope Google gets this straightened out.
Now I've checked again and the update is gone. Maybe it's better?
Just saw this on Twitter. Google knows they goofed, but we may never know what actually happened.
https://twitter.com/i/web/status/1458595873705926656
Just checked my phone and the update is not appearing now.
Glitch at their end.