Related
Anyone gotten this build via OTA? I got impatient and flashed the factory images. Just curious about that weird build number...https://www.reddit.com/r/GooglePixe...nyone_seen_nhg47k_in_the_wild_might_or_might/
bjoostema said:
Anyone gotten this build via OTA? I got impatient and flashed the factory images. Just curious about that weird build number...https://www.reddit.com/r/GooglePixe...nyone_seen_nhg47k_in_the_wild_might_or_might/
Click to expand...
Click to collapse
I thought I was the only one, I didn't get the OTA yet either, I'm still waiting even though it's supposed to be out and Verizon normally has it ready to download immediately when they say it's ready on their software update page.
I haven't heard anyone on Verizon getting an OTA yet, which is odd like you implied. I wonder what they're holding off for. It also didn't mention the Android version bump in their notes.
Well that helps, I have a play store phone but Verizon service and I haven't been able to get OTA yet even when I tell it to go look. I guess I will have to wait until Verizon gets going on this. Taking the sim card out and rebooting does not help.
Sent from my BTV-W09 using Tapatalk
bjoostema said:
I haven't heard anyone on Verizon getting an OTA yet, which is odd like you implied. I wonder what they're holding off for. It also didn't mention the Android version bump in their notes.
Click to expand...
Click to collapse
I got the OTA, it's 7.1.2 and definitely the NHG47K
LaosPerson said:
I got the OTA, it's 7.1.2 and definitely the NHG47K
Click to expand...
Click to collapse
Are you able to grab the link?
rozyman17 said:
Are you able to grab the link?
Click to expand...
Click to collapse
Link for what? Sorry I'm confused lol.
Link for the OTA. I sideloaded the E build, but wouldn't mind putting on the K build
Any time there is an update I just grab it from https://developers.google.com/android/images. I haven't tried flashing the OTA from the page since I usually grab the full factory image (I don't mind starting over lol). I am on Verizon and my build number after I flash the factory image is N2G47E. There are no Verizon apps on the images , but during set up it will prompt to download all that Verizon crap-ware, which you can cancel or uninstall.
As of last night, Verizon has released the K build, which is not up on the developer site. Must be something in there that is better than the E build on their network. Just an FYI.
rozyman17 said:
Link for the OTA. I sideloaded the E build, but wouldn't mind putting on the K build
Click to expand...
Click to collapse
I did the same thing earlier this week. Just checked for updates and nothing. Hope I am not hosed lol.
I ended up with the Verizon version OTA last night (non rooted, google play phone on Verizon service). I did not notice any Verizon-ware installed on the phone, at least not yet. Seems pretty flawless so far.
Sent from my Pixel XL using Tapatalk
Anyone able to upload the OTA?
I would be concerned with the Verizon firmware locking the bootloader on Google Play store Pixels
I don't think that's how it works.
After the frustration it took for me to get stock 7.1.2 on my PXL, I'll wait to see how people like the K build before I consider going back to 7.1.1 so I can be recognized and offered the OTA.
No one has the OTA file yet? Assume that I can't to back to 7.1.1 to get this OTA? I sideloaded the E build earlier this week.
Trooper27 said:
No one has the OTA file yet? Assume that I can't to back to 7.1.1 to get this OTA? I sideloaded the E build earlier this week.
Click to expand...
Click to collapse
There's always loading the 7.1.1 factory image back, but you can only do that when unlocked. I just hope this is a one-off, because over time it might become 'a thing' if people who sideloaded are on a different release track as others'. It would be nice to know if this is just 7.1.2 with VZW branding, or if it gives better performance on Verizon's network, but evidently we're too dumb to understand exactly what's different between stock 7.1.2 and their version.
It seems to bounce back and forth, sometimes there is a Verizon specific firmware sometimes there isn't, but it would be nice to know before side loading how many branches of the firmware there will be.
Sent from my Pixel XL using Tapatalk
destruya1 said:
There's always loading the 7.1.1 factory image back, but you can only do that when unlocked. I just hope this is a one-off, because over time it might become 'a thing' if people who sideloaded are on a different release track as others'. It would be nice to know if this is just 7.1.2 with VZW branding, or if it gives better performance on Verizon's network, but evidently we're too dumb to understand exactly what's different between stock 7.1.2 and their version.
Click to expand...
Click to collapse
I am not unlocked so I have no option of doing that. I had no clue there would be a Verizon specific build or what I have not sideloaded earlier this week. Guess I have to learn patience LOL.
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Capture the URL for it ?
Here is the link: https://ota.googlezip.net/packages/ota-api/google_marlin_marlin/d872269d3aff80d3b7f81d28c972d1d59f36f8f6.zip
(I'm not allowed to link to it directly due to my account age - sorry!)
Ohber1014 said:
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Click to expand...
Click to collapse
This happened to me. I have a Verizon version dePixel8 and sideloaded E build a few days ago. Today I got the update message and it upgraded to K in about 2 minutes.
Gather this is for the Verizon models?
Ohber1014 said:
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Click to expand...
Click to collapse
It's an update specifically for the Verizon Pixels. It contains a number of bug fixes and improvements according to the release info. A simple Google search will locate more info including the specifics of the bug fixes and improvements.
So this OTA will update my Google store device to the Verizon build? Weird. I'll just flash the whole build later.
So, after applying this update - what build does it show?
Just flashed the OTA. It does indeed update Google Store devices to the Verizon build of 7.1.2, NHG47K. Looking in the OTA zip, the update may only affect the system and vendor partitions.
I had this happen after I flashed the January build I think it was. I have a play store pixel on vzw and it was trying to update my regular stock rom the vzw-specific version. It sounds like if you're on vzw service then you'd benefit from their improvements. I'm waiting for beans to update his rom before I update from 7.1.1. I just hope it includes these vzw changes.
It would be nice to know what changed. I, for one, would rather not be bothered with the Verizon version of the OTA. I don't want any of the apps, bloat, etc that they're surely going to try pushing. There is a reason I bought from Google and not Verizon.
The only difference between the VZ model and the Google model is the VZ model has a locked bootloader. If you put a VZ Sim in either one it will install 3 apps that you can uninstall completely, not just disable.
alsip1023 said:
It would be nice to know what changed. I, for one, would rather not be bothered with the Verizon version of the OTA. I don't want any of the apps, bloat, etc that they're surely going to try pushing. There is a reason I bought from Google and not Verizon.
Click to expand...
Click to collapse
I put it on my Google phone since it has a different radio for Verizon. There is no extra bloat or anyrhing, just like there wasnt when the phone first came out. The image is from google, the updates are from Google. None of that is going to happen. Except for the bootloader VZ is playing by Google's rules on this phone.
Google makes carrier specific images all the time. This is no big deal.
hub1 said:
The only difference between the VZ model and the Google model is the VZ model has a locked bootloader. If you put a VZ Sim in either one it will install 3 apps that you can uninstall completely, not just disable.
Click to expand...
Click to collapse
I was referring to the difference between the 7.1.2 builds, not the phones.
alsip1023 said:
I was referring to the difference between the 7.1.2 builds, not the phones.
Click to expand...
Click to collapse
So was I.
TonikJDK said:
I put it on my Google phone since it has a different radio for Verizon. There is no extra bloat or anyrhing, just like there wasnt when the phone first came out. The image is from google, the updates are from Google. None of that is going to happen. Except for the bootloader VZ is playing by Google's rules on this phone.
Google makes carrier specific images all the time. This is no big deal.
Click to expand...
Click to collapse
Thanks for playing the guinea pig. Good to know nothing obvious was added in terms of bloat.
With that being said, that Pixel update is handed to Verizon to "test and certify". Then it is sent to the Pixels. Verizon only promised to not delay updates. They may still add apps, bloat, etc... Should they so choose.
Added information:
Google Store Pixel XL: Unlocked since 7.0.1, shows unlocked, and the bar is flipped to the right (as in enabled) but is overall greyed out after "K" update.
Verizon Purchased Pixel XL: Unlocked since 7.0.1, shows unlocked, and the bar is flipped to the left (as in disabled) but is overall greyed out after "K" update.
Not sure what this means. If anything, I found it interesting. Once it's unlocked, unless I submit a relock, it can't be relocked by OTA right?
Found this thread in a search. I have a playstore pixel xl unlocked bootloader, stock root on verizon. I sideloaded 7.1.2 build N2G47E. After sideload the system update still shows. Before re-rooting I tried to install it but it always comes back "Couldn't update, installation problem". I verified that the sideload installed and am in fact on N2G47E.
I even reset the phone, locked the bootloader and it still failed. I have since unlocked & re-rooted running stock. Update still shows and still fails. I've turned off auto updates so it only happens if I manually check and try to install. Other than this the phone is running fantastic.
Should I sideload the verizon ota build? I know I'll loose root but want to make sure bootloader stays unlocked and can re-root after moving to Verizon build. Can anyone confirm this? Post above seems to confirm the bootloader stays unlocked but doesn't mention root. Btw to root I am not flashing twrp, just fastboot to it and flash su.
gordonlw said:
Found this thread in a search. I have a playstore pixel xl unlocked bootloader, stock root on verizon. I sideloaded 7.1.2 build N2G47E. After sideload the system update still shows. Before re-rooting I tried to install it but it always comes back "Couldn't update, installation problem". I verified that the sideload installed and am in fact on N2G47E.
I even reset the phone, locked the bootloader and it still failed. I have since unlocked & re-rooted running stock. Update still shows and still fails. I've turned off auto updates so it only happens if I manually check and try to install. Other than this the phone is running fantastic.
Should I sideload the verizon ota build? I know I'll loose root but want to make sure bootloader stays unlocked and can re-root after moving to Verizon build. Can anyone confirm this? Post above seems to confirm the bootloader stays unlocked but doesn't mention root. Btw to root I am not flashing twrp, just fastboot to it and flash su.
Click to expand...
Click to collapse
Hello,
You bought a Google version, you are fine. You can sideload Verizon's OTA if you are on Verizon's network. Otherwise, no benefits...
Even true Verizon's unlocked Pixel owners, as long as they don't lock bootloader, it will stay unlocked, no matter what they flash FYI.
You can install SU with fastboot boot twrp as well.
Cheers...
Worked great thanks!
I am a bit confused by all the posts about this subject
I would like to unlock my phone, for future rooting, when everything is more stable, meanwhile I want to get OTA updates on the phone "automaticaly", is that possible
You can definitely unlock the bootloader and still receive OTA.
And for your first point, rooting is plenty stable already, so no need to wait for that. Though if you aren't well versed in fastboot or root upgrade processes, you should definitely read all the most recent guides on it to make your transition smoother.
Thank you :good:
I did my share of rooting with Samsung S1, S3 and S5
Then bougth an LG V10, had to buy a "IMAGE" from a Chinese guy, using Alibaba "paypal" in chinese, to be able to activate LTE 20
Have been quiet for a couple of years, and didnt really have the need to root to have the V10 doing what I wanted, but want to be able to root if I have too much free time
melorib said:
Thank you :good:
I did my share of rooting with Samsung S1, S3 and S5
Then bougth an LG V10, had to buy a "IMAGE" from a Chinese guy, using Alibaba "paypal" in chinese, to be able to activate LTE 20
Have been quiet for a couple of years, and didnt really have the need to root to have the V10 doing what I wanted, but want to be able to root if I have too much free time
Click to expand...
Click to collapse
You will probably find this less confusing than Odin. But you need to read up on using latest SDK, adb, fastboot, etc.
We're now using Magisk to root and be able to use Paypal.
wtherrell said:
You will probably find this less confusing than Odin. But you need to read up on using latest SDK, adb, fastboot, etc.
We're now using Magisk to root and be able to use Paypal.
Click to expand...
Click to collapse
Thanks, I work with IT, and already used adb to enable LTE frequencies on my LG V10. And of course I have been reading about Magisk, but will wait for more stable versions
melorib said:
Thanks, I work with IT, and already used adb to enable LTE frequencies on my LG V10. And of course I have been reading about Magisk, but will wait for more stable versions
Click to expand...
Click to collapse
There's issues with Magisk and some other phones, but topjohnwu has a Pixel 2 I believe, so he tests on that.
Magisk for our phones is perfectly stable, the only issue is people don't like the dtbo image being edited to remove AVB 2.0/dm-verity.
My bootloader is unlocked on my XL 2 and I am on Verizon. I have yet to get the January OTA. I haven't gotten an OTA since I got the phone in October
canemaxx said:
My bootloader is unlocked on my XL 2 and I am on Verizon. I have yet to get the January OTA. I haven't gotten an OTA since I got the phone in October
Click to expand...
Click to collapse
Strange, there was at least an update in January
Nov, Dec and January .....I have had to flash the full image if all 3. No OTA has ever come to this device
canemaxx said:
Nov, Dec and January .....I have had to flash the full image if all 3. No OTA has ever come to this device
Click to expand...
Click to collapse
Why? I want OTA updates...
I'm not sure why they just have not come to my phone.
canemaxx said:
I'm not sure why they just have not come to my phone.
Click to expand...
Click to collapse
You only unlocked the bootloader? Maybe because it is Verizon, the bootloader is supposed to to be locked!
I can't see that being the reason as I bought the phone from the Google store
canemaxx said:
I can't see that being the reason as I bought the phone from the Google store
Click to expand...
Click to collapse
Sounds strange, maybe you updated before OTA was available for Verizon...
In 2 weeks I get mine, going to unlock before any update, it was bought December, so it has at least one update missing...
canemaxx said:
I can't see that being the reason as I bought the phone from the Google store
Click to expand...
Click to collapse
You can buy the locked Verizon phone from the Google Store, but apparently you ordered the correct one (unlocked, carrier free). Devices on the Verizon network (both locked and unlocked) receive regular OTAs, so don't worry- the status of the bootloader has nothing to do with why your device hasn't received the update yet. The difference is having the unlocked variant, you don't have to use Verizon specific images, and you can change carriers at any time, including internationally. Usually with just a SIM card change.
The OTA updates are staged randomly and roll out over a couple of weeks. Your OTA will eventually come by itself. Sometimes people wait a month (or even longer). If you don't want to wait, then just download the OTA and sideload it. Every month, the new OTAs (and full images) are posted by Google. You are free to download and flash them. Instructions on how to do this are provided by Google at the top of the download page. You don't even need to be bootloader unlocked to sideload OTAs.
v12xke said:
You can buy the locked Verizon phone from the Google Store, but apparently you ordered the correct one (unlocked, carrier free). Devices on the Verizon network (both locked and unlocked) receive regular OTAs, so don't worry- the status of the bootloader has nothing to do with why your device hasn't received the update yet. The difference is having the unlocked variant, you don't have to use Verizon specific images, and you can change carriers at any time, including internationally. Usually with just a SIM card change.
The OTA updates are staged randomly and roll out over a couple of weeks. Your OTA will eventually come by itself. Sometimes people wait a month (or even longer). If you don't want to wait, then just download the OTA and sideload it. Every month, the new OTAs (and full images) are posted by Google. You are free to download and flash them. Instructions on how to do this are provided by Google at the top of the download page. You don't even need to be bootloader unlocked to sideload OTAs.
Click to expand...
Click to collapse
Thanks I know how to sideload or flash the full image but just was hoping I wouldn't have to again and again
Are your phones enrolled on the Android Beta Program ? My P2 was and I never got the Jan. Update till I Unenrolled from the beta program. Immediately afterwards I checked and Jan update was available.
For the June security update, there's a version specific to T-Mobile (OPM4.171019.021.E1). My carrier is an MVNO of T-mo. Should I load that version or the standard OPM2.171026.006.C1 image?
P2 XL, stock rooted.
why not just check for updates, it will give you the correct OTA, no need to flash factory images for the security patch.
angus242 said:
For the June security update, there's a version specific to T-Mobile (OPM4.171019.021.E1). My carrier is an MVNO of T-mo. Should I load that version or the standard OPM2.171026.006.C1 image?
P2 XL, stock rooted.
Click to expand...
Click to collapse
You could also go to "Settings" , "System" then "About Phone" and it will give your current build at the bottom. Just see which May OTA you have installed and use the corresponding June update.
NeroDan said:
You could also go to "Settings" , "System" then "About Phone" and it will give your current build at the bottom. Just see which May OTA you have installed and use the corresponding June update.
Click to expand...
Click to collapse
The May update does not have a T-Mobile specific option; only Fi or not.
angus242 said:
The May update does not have a T-Mobile specific option; only Fi or not.
Click to expand...
Click to collapse
It will start with OPM2 or OPM4 though. Just download whatever one you currently have.
NeroDan said:
It will start with OPM2 or OPM4 though. Just download whatever one you currently have.
Click to expand...
Click to collapse
I have OPM1 LOL
I want to do a fresh install. I think I'll just do the May factory OPM2, allow the OTA to run for June and then root.
Thanks!
uicnren said:
why not just check for updates, it will give you the correct OTA, no need to flash factory images for the security patch.
Click to expand...
Click to collapse
I've been on the system update downloading screen for over a half hour (88.3MB). I'm just going to do a fresh install with the May factory image and allow the OTA to run before rooting again.
angus242 said:
For the June security update, there's a version specific to T-Mobile (OPM4.171019.021.E1). My carrier is an MVNO of T-mo. Should I load that version or the standard OPM2.171026.006.C1 image?
P2 XL, stock rooted.
Click to expand...
Click to collapse
The t mobile version is because people were having problems with Lte reception when using pixel 2 on t mobile network. It's the same as the other June update but with added radios. I normally flash the reg pixel update (non-carrier version) from Google.
Today I dirty flashed the t mobile version on top of the non-carrier specific may version from last month.
It worked flawless.
I noticed the last month or so my Lte is weird. No service or reception sporadically. So apparently they made an update just for factory unlocked pixel 2's running on T-Mobile. BTW TMobile don't even sell pixel 2's, so it's not a t mobile specific rom
T-Mobile seems to be your best bet....
Im on the same boat... I'm on Sprint. I got the June date and my Build number is OPM4.171019.021.E1 Which is the same build number as the factory image for T-Mobile. I guess its not specific to only T-Mobile... Im about to do a clean flash to root and install magisk. I hope it works lol
I'm on MintMobile(Tmo towers) and flashed the OPM4 image which apparently is meant Google Fi customers but so far I haven't noticed a difference between it and the OPM2 image I usually go with.
I'm on T-Mobile, installed the T-Mobile image (which I do every month because I'm rooted and use a custom kernel), now no more WiFi calling for me
Have these fixes been upstreamed into the P betas?
sirxdroid said:
I'm on T-Mobile, installed the T-Mobile image (which I do every month because I'm rooted and use a custom kernel), now no more WiFi calling for me
Click to expand...
Click to collapse
Did you get this resolved? I am considering downloading the T-Mobile version since my LTE randomly doesn't work even when I have a strong signal.
PuffDaddy_d said:
Did you get this resolved? I am considering downloading the T-Mobile version since my LTE randomly doesn't work even when I have a strong signal.
Click to expand...
Click to collapse
Moved to Pie since, but while on Oreo I did use the T-Mobile builds.
Folks with the Google purchased unlocked version....did you get the update? I have not so far. I know I can side load it but I am curious if it is just me.
Nothing for me. I'm curious tho, I had to sideload the Nov update to get the Verizon build. So now I'm waiting to see if the OTA will come for Dec.
Nothing for me either. If I wanted to sideload the OTA, would I get the one for US carriers? I don't see a Verizon specific one this time around.
Frankie1588 said:
Nothing for me either. If I wanted to sideload the OTA, would I get the one for US carriers? I don't see a Verizon specific one this time around.
Click to expand...
Click to collapse
My question exactly. I'm wondering if they are now doing away with the Verizon specific builds and keeping it standard across all US carriers. Same situation here and no update yet.
I haven't received the update yet either. I've got the files downloaded and ready but I'm gonna wait a little bit to see what happens.
I believe the .a1 update is for Canada, correct me if I'm wrong
bizdiddy said:
My question exactly. I'm wondering if they are now doing away with the Verizon specific builds and keeping it standard across all US carriers. Same situation here and no update yet.
Click to expand...
Click to collapse
I sideloaded the US carrier OTA to both mine and my wife's Verizon P6Ps with no issues.
spotmark said:
I sideloaded the US carrier OTA to both mine and my wife's Verizon P6Ps with no issues.
Click to expand...
Click to collapse
Just to confirm, yours are the unlocked variant from Google right? Thanks!
Frankie1588 said:
Just to confirm, yours are the unlocked variant from Google right? Thanks!
Click to expand...
Click to collapse
No, they are both bootloader locked Verizon variants.
Edit - My apologies. I didn't notice that you were asking about unlocked models.
At this point I've seen no evidence that anyone in the US on Verizon has had the update properly pushed OTA to their phone.
I miss the days when the "Check for Update" button worked and would actually pull the update.
jimistixx said:
At this point I've seen no evidence that anyone in the US on Verizon has had the update properly pushed OTA to their phone.
I miss the days when the "Check for Update" button worked and would actually pull the update.
Click to expand...
Click to collapse
Yup. I never got any OTAs since day 1 on mine. Had no issues with this with my 2 XL or 5.
I'm using unlocked on Verizon and had to sideload the US update. So far the phone is a lot more stable and reception seems to be slightly better.
Guyinlaca said:
I'm using unlocked on Verizon and had to sideload the US update. So far the phone is a lot more stable and reception seems to be slightly better.
Click to expand...
Click to collapse
Thanks! Going to sideload now.
Lets light up the Google forum a bit. There is already a thread on it so please add your experience. There is something missing between Google and Verizon.
Pixel 6 Pro not getting December update - Google Pixel Community
support.google.com
bizdiddy said:
My question exactly. I'm wondering if they are now doing away with the Verizon specific builds and keeping it standard across all US carriers. Same situation here and no update yet.
Click to expand...
Click to collapse
They always work towards having one US version. If you look at the history of the other phones on the factory image page you will see where they split apart but often come back together in a month or two.
So as we sideload we load the US version.
I have a pixel 6 pro unlocked purchased from Google and haven't received the update. I hate to ask but can someone point me in the right direction to side load the update. I've never side loaded an update and could use the assist. Thank you all in advance
jughead75 said:
I have a pixel 6 pro unlocked purchased from Google and haven't received the update. I hate to ask but can someone point me in the right direction to side load the update. I've never side loaded an update and could use the assist. Thank you all in advance
Click to expand...
Click to collapse
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
There are full instructions at the link above but let me give you cliff notes.
Download the platform tools to your computer so you have ADB.
Download the CORRECT OTA image from the link above and copy the zip to the platform tools folder. Do not extract it, leave it as a zip.
Connect your phone to your computer with USB Debugging turned on in Developer Options.
Reboot into recovery then issue the adb command to load the OTA file.
TonikJDK said:
Lets light up the Google forum a bit. There is already a thread on it so please add your experience. There is something missing between Google and Verizon.
Pixel 6 Pro not getting December update - Google Pixel Community
support.google.com
Click to expand...
Click to collapse
They don't even have the update on their software update page yet. The 11/16 update states it is October patch level. Lame. No wonder no one is getting it. There is zero reason to wait for a Verizon OTA any longer. I have the Google version unlocked on Verizon and flashed the US December build.
Google Pixel 6 Software Update | Verizon Customer Support
Get instructions on downloading the latest software update for performance improvements to your Pixel 6, including current Android security patches.
www.verizon.com
TonikJDK said:
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
There are full instructions at the link above but let me give you cliff notes.
Download the platform tools to your computer so you have ADB.
Download the CORRECT OTA image from the link above and copy the zip to the platform tools folder. Do not extract it, leave it as a zip.
Connect your phone to your computer with USB Debugging turned on in Developer Options.
Reboot into recovery then issue the adb command to load the OTA file.
Click to expand...
Click to collapse
Thank you! I appreciate the help
Bumping this with a title change. Just learned my kids unlocked has not updated. He is on ATT.
So wondering if other carriers have the same issue.
I got impatient and sideloaded the OTA for my unlocked P6P on Verizon's network. I used the .017 OTA image and all went smoothly.