Verizon specific 7.1.2 build? - Google Pixel XL Questions & Answers

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.

Related

Help! Is there a Verizon KDZ for the new VS98612a?

For some reason my phone will not let me take the newest update for the Verizon G4. Does anybody know of another way besides OTA or Verizon Update Assistant that I could update my phone? Can't find the KDZ to try and flash. Any help would be appreciated. Thank You
Mine won't see it either. They may have pulled the update?
Are you rooted?
geoff5093 said:
Are you rooted?
Click to expand...
Click to collapse
No not rooted
I would also love to hear of a way to update to Verizon's 12a without OTA. I unrooted my 11a version in order to get 12a to fix touchscreen issues. It seems the 12a OTA is not around, at least verizon doesn't want to give it to me.
Oddly enough after using kdz for 11a my software showed status as "Official". But a few hours later it switched to Modified, even though I'm not rooted. Not sure why.
I don't see it either
photos.by.fako said:
For some reason my phone will not let me take the newest update for the Verizon G4. Does anybody know of another way besides OTA or Verizon Update Assistant that I could update my phone? Can't find the KDZ to try and flash. Any help would be appreciated. Thank You
Click to expand...
Click to collapse
Same here, my phone is unrooted, and it is on Verizon Network.
I have tried OTA update, it keep saying i already have the latest update (which is 11A)
I have also tried Verizon Update Assistant Installer (working in windows 7, but not in Windows 10), same thing, when I tried to update, it keep saying I already have the latest update (which is 11A)
do any one know Verizon push OTA by the list? (e.g. some people will get first, and some people will get last) or every one should get OTA at once?
Also, is possible Verizon pull the 12A update due to notification issue?
thanks
It's highly likely that Verizon pulled this update. Nobody has reported receiving it since about 10/10. I'm sure we'll see a new one drop soon that fixes whatever was wrong with 12A.
oldblue910 said:
It's highly likely that Verizon pulled this update. Nobody has reported receiving it since about 10/10. I'm sure we'll see a new one drop soon that fixes whatever was wrong with 12A.
Click to expand...
Click to collapse
Thanks for the info.
Hoping Verizon does not take too much time, We will get Marshmallow soon, then 12A is no longer needed.

Notification to update to 7.1.2 while already on 7.1.2?

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!

Which image to flash when using Google Edition on Verizon?

Like the title says. I just bought a used Google Edition Pixel XL and will be using it on Verizon. Want to get a clean slate and start by flashing a clean system image. Should I flash NHG47L (May 2017, Verizon) or NHG47O (May 2017)? Does it matter?
sklarskyj said:
Like the title says. I just bought a used Google Edition Pixel XL and will be using it on Verizon. Want to get a clean slate and start by flashing a clean system image. Should I flash NHG47L (May 2017, Verizon) or NHG47O (May 2017)? Does it matter?
Click to expand...
Click to collapse
That is what I have.
The Verizon image. With a VZ SIM in it, it will pull the VZ OTA. Just some minor changes for their network, nothing else.
FYI, if you root and mod keep it up to date. There is a bug that has gotten a few folks. OTA fails...it keeps redownloading burning massive data.
Thanks for the quick reply!
TonikJDK said:
That is what I have.
The Verizon image. With a VZ SIM in it, it will pull the VZ OTA. Just some minor changes for their network, nothing else.
FYI, if you root and mod keep it up to date. There is a bug that has gotten a few folks. OTA fails...it keeps redownloading burning massive data.
Click to expand...
Click to collapse
hmmm i have a google phone on verizon, but i flashed the NHG47O version on my phone and everything seems good. I just wont get the ota now?
sruel3216 said:
hmmm i have a google phone on verizon, but i flashed the NHG47O version on my phone and everything seems good. I just wont get the ota now?
Click to expand...
Click to collapse
You will get the ota, and it will probably be the VZ version. When mine was on the Google version it offered me the VZ OTA.
TonikJDK said:
You will get the ota, and it will probably be the VZ version. When mine was on the Google version it offered me the VZ OTA.
Click to expand...
Click to collapse
ok cool. just wanted to make sure everything would still run fine. thanks

8.1.0 OTA question

I have a quick question for those that are a lot smarter than I.
Still nothing for me on the 8.1.0 OTA December update. I have an unlocked Pixel 2 XL and an unlocked OG Pixel XL. I was running the Beta on my OG Pixel and I unenrolled from the Beta and factory reset. Waited 24 hours for a stable version of Android Oreo.... still nothing and it is still showing that I'm on 8.1.0 with the November security patch. Also, when I reset my phone or power back on it's still showing that my phone is on the Beta. I have no idea what's going on with it.
Would any of you guys/gals have any other suggestions? I'm not comfortable with flashing or anything like that since I've never done it before. Should I just wait patiently because it will come eventually?
Thanks.
Shrews824 said:
I have a quick question for those that are a lot smarter than I.
Still nothing for me on the 8.1.0 OTA December update. I have an unlocked Pixel 2 XL and an unlocked OG Pixel XL. I was running the Beta on my OG Pixel and I unenrolled from the Beta and factory reset. Waited 24 hours for a stable version of Android Oreo.... still nothing and it is still showing that I'm on 8.1.0 with the November security patch. Also, when I reset my phone or power back on it's still showing that my phone is on the Beta. I have no idea what's going on with it.
Would any of you guys/gals have any other suggestions? I'm not comfortable with flashing or anything like that since I've never done it before. Should I just wait patiently because it will come eventually?
Thanks.
Click to expand...
Click to collapse
I got my Dec 5th patch update last night, so I'm sure it's only a matter of time for you.. If you're not comfortable flashing, than I would say just wait it out. It shouldn't be long.
What the poster above me said, just wait you will eventually get it. They roll it out in stages so they don't overload the servers. We all like instant gratification, which is why a lot of people flash it when it is released, but you will get it.
COMTB said:
What the poster above me said, just wait you will eventually get it. They roll it out in stages so they don't overload the servers. We all like instant gratification, which is why a lot of people flash it when it is released, but you will get it.
Click to expand...
Click to collapse
Any idea on why my original Pixel XL is still showing that I'm in Beta though? That's really what's confusing me.
Shrews824 said:
Any idea on why my original Pixel XL is still showing that I'm in Beta though? That's really what's confusing me.
Click to expand...
Click to collapse
When you unenroll, it will send you an OTA. Did you get that OTA? You mentioned you factory reset, but that's not what actually takes you off of the beta.
thacounty said:
When you unenroll, it will send you an OTA. Did you get that OTA? You mentioned you factory reset, but that's not what actually takes you off of the beta.
Click to expand...
Click to collapse
No, I did not get an OTA. I've checked on the site and it says that my device is no longer enrolled, however when I restart my phone (from a powered off standpoint) it still says I'm enrolled in the Beta. I check for an update and it says I'm up to date, yet it's running 8.1.0 with the November 5th security patch.
Sorry for so many questions, but I just thought I might be missing something. It's really not that big a deal to me because I know it will come eventually, but I just wondered why it was doing that. I reached out to Google via the chat and they said wait 24 hours for a stable version however it's been well over 24 hours and still nothing. I've unenrolled the device from previous beta's and have never had to wait. The OTA would immediately show up and I was good to go.
Is it safe to take the actual ota while rooted/TWRP/custom kernel? Will it just replace the boot partition or will it fail? I'm thinking I should do a flash all with the -w removed of the 8.1 instead of letting it go the ota. I just got the notification for it.
Shrews824 said:
Any idea on why my original Pixel XL is still showing that I'm in Beta though? That's really what's confusing me.
Click to expand...
Click to collapse
DId your OG Pixel XL get the officialy release?
COMTB said:
DId your OG Pixel XL get the officialy release?
Click to expand...
Click to collapse
No, it hasn't received the latest 8.1.0.
Shrews824 said:
No, I did not get an OTA. I've checked on the site and it says that my device is no longer enrolled, however when I restart my phone (from a powered off standpoint) it still says I'm enrolled in the Beta. I check for an update and it says I'm up to date, yet it's running 8.1.0 with the November 5th security patch.
Sorry for so many questions, but I just thought I might be missing something. It's really not that big a deal to me because I know it will come eventually, but I just wondered why it was doing that. I reached out to Google via the chat and they said wait 24 hours for a stable version however it's been well over 24 hours and still nothing. I've unenrolled the device from previous beta's and have never had to wait. The OTA would immediately show up and I was good to go.
Click to expand...
Click to collapse
At this point I would sideload and hope the Check for Update is fixed in January as expected.
thacounty said:
At this point I would sideload and hope the Check for Update is fixed in January as expected.
Click to expand...
Click to collapse
Well, I had mentioned in the original post that I'm not extremely comfortable doing that so I may just wait it out.
I have a question in regards to getting the OTA updates.
I'm in Australia and got my pixel 2 xl on a plan with Telstra as they are the exclusive carrier here. But I use a Vodafone sim in the phone.
Will this cause me to not get the OTA updates?

Question Unlocked on Verizon update (or other US carriers)

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.

Categories

Resources