Develop Bugs

Verizon specific 7.1.2 build?

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.

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

Moto Z2 Force not getting OTA updates

I have a ATT branded Moto Z2 with a Cricket SIM. I got the phone in late november, and it came with Android 7.1.1 with the June 1 SPL. I know that ATT has released several updates, the latest in December with the November 1st SPL,
but everytime I check for updates it says that my phone is up-to-date.
So far I tried to check for updates after a factory reset, and also tried to do an OTA update with an old ATT SIM in it. Nothing seems to be working.
I have posted on the lenovo support page but so far I have not got any answer. I am not the guy that has to have the latest software running, but the updates fixed the BlueBorne security hole...
Othat than using a Cricket SIM, the phone is stock, not rooted.
has anybody encountered the same problem? Thank you

So I have two Tmobile versions of this phone. one rooted/unlocked, one not. I am also having a problem with receiving OTA. Mine stock device is on an August Security patch and there have been two released patches since then. I just got off the phone with both motorola and tmobile and they are both useless. I explained over and over that i wasn't calling about the oreo release, that i was calling about ANY updates and they couldn't get that through their head. Further, tmobile states they haven't released an 8.0 ota which we all know is false since several people on this forum have received it.... very frustrating. I may have to unlock my stock device if I ever want an actual update.
ululi said:
I have a ATT branded Moto Z2 with a Cricket SIM. I got the phone in late november, and it came with Android 7.1.1 with the June 1 SPL. I know that ATT has released several updates, the latest in December with the November 1st SPL,
but everytime I check for updates it says that my phone is up-to-date.
So far I tried to check for updates after a factory reset, and also tried to do an OTA update with an old ATT SIM in it. Nothing seems to be working.
I have posted on the lenovo support page but so far I have not got any answer. I am not the guy that has to have the latest software running, but the updates fixed the BlueBorne security hole...
Othat than using a Cricket SIM, the phone is stock, not rooted.
has anybody encountered the same problem? Thank you
Click to expand...
Click to collapse

Chrisy8s said:
So I have two Tmobile versions of this phone. one rooted/unlocked, one not. I am also having a problem with receiving OTA. Mine stock device is on an August Security patch and there have been two released patches since then. I just got off the phone with both motorola and tmobile and they are both useless. I explained over and over that i wasn't calling about the oreo release, that i was calling about ANY updates and they couldn't get that through their head. Further, tmobile states they haven't released an 8.0 ota which we all know is false since several people on this forum have received it.... very frustrating. I may have to unlock my stock device if I ever want an actual update.
Click to expand...
Click to collapse
At least the T-Mobile versions can be rooted. As far as I know, the ATT cannot as of yet.

theres only been one update since august and thats a fixed august. the other being the oreo update thats available now
if you would like to update your phone we have the ota updates and can get you updated without unlocking your bootloader just let me know [email protected] on hangouts

Chrisy8s said:
So I have two Tmobile versions of this phone. one rooted/unlocked, one not. I am also having a problem with receiving OTA. Mine stock device is on an August Security patch and there have been two released patches since then. I just got off the phone with both motorola and tmobile and they are both useless. I explained over and over that i wasn't calling about the oreo release, that i was calling about ANY updates and they couldn't get that through their head. Further, tmobile states they haven't released an 8.0 ota which we all know is false since several people on this forum have received it.... very frustrating. I may have to unlock my stock device if I ever want an actual update.
Click to expand...
Click to collapse
What OTA for Tmobile? Mine has NCX26. 7 as stated in Tmobile support site, I do know that OCX oreo release is suppose to be live but support site doesn't show it andy phone hasn't gotten it.

Found a way to get it to download updates.
So, after wasting my time with Motorola and ATT so-called "technical support", I decided to try something: I rebooted the phone in recovery mode (VOlume down + Power button) and put it in recovery mode. Rebooted from recovery mode, and bingo, it downloaded the next update (September SPL). It now shows "background installation..." in progress. Hopefully this is going to be the solution.

I did the update manually using the file nash_opx 27.109-34_subsidy-DEFAULT_regulatory-DEFAULT_CFC. Xml. zip and it worked perfectly.

djsboy said:
I did the update manually using the file nash_opx 27.109-34_subsidy-DEFAULT_regulatory-DEFAULT_CFC. Xml. zip and it worked perfectly.
Click to expand...
Click to collapse
I think I may have found the right recipe. The trick is to check for updates while NOT on WiFi. So move away from WiFi coverage, but still within Cell coverage, with Data on. Check for updates. It will say that an update is available and will be download when within WiFi range. Move back to where you have WiFi, and bingo, it will start downloading. I did it twice yesterday afternoon, once to go from the Sept to the Oct SPL, and then from the Oct SPL to the Nov SPL, which is the last available update according to the ATT page. All of this with my Cricket SIM. WHy this works is beyond my pay grade to figure out. I will eagerly wait for the next update to be posted to see if this trick works consistently. Again,
this seems to work with my ATT branded phone.

My ATT Z2 force, starting from last evening (1/24/2018), kept getting security update, from September, 2017. Then this morning, October 2017 and November 2017. Does this mean we are going to get Oreo update soon ?

So I've had my Moto zforce 2 for 3 days now. We're is the Oreo update ? T-Mobiles site says it was released Dec 22nd ?

lcc014 said:
My ATT Z2 force, starting from last evening (1/24/2018), kept getting security update, from September, 2017. Then this morning, October 2017 and November 2017. Does this mean we are going to get Oreo update soon ?
Click to expand...
Click to collapse
Dude..Let us know when u get Oreo update....So am I

Anyone on TMobile receive the ota update ?

There are issues with calling and sms on the T-Mobile variant. The update has been pulled while they sort out the issues.

Well that makes sense why I'm not seeing it then.

I am still not able to get the AT&T update past June. I tried the reboot into recovery and nothing. Is there a way to manually install the update from an SD card which would allow for OTA updates in the future?

TheLooq said:
There are issues with calling and sms on the T-Mobile variant. The update has been pulled while they sort out the issues.
Click to expand...
Click to collapse
Good. On my account we got 2 of them for Christmas. A few days after Christmas, one of them updated to Oreo. At this point, the Galaxy S7 Edge on our account could not hear the Z2 Force. Went through everything with T-Mobile support including network settings reset, factory resetting both the Samsung and Motorola phones. Didn't fix it. Meanwhile, the Z2 Force that was still on Nougat was fine. A few days later, it also updated to Oreo, and now neither Z2 Force can be heard on the Samsung. I hope they get this mess cleaned up soon since it's been a month.

It seems to be only between those two phones. Until the next update/patch is released, the workaround is to disable VoLTE in call settings on the z2.

Got AT&T update to 8.0.0 this morning.

I received notice of the Tmobile Oreo update, downloaded it, but cannot install it. It only says something went wrong and didn't install the update. I have the bootloader unlocked and Magisk installed. I followed the instructions for Magisk dual partition updates. I uninstalled Magisk using Restore Images and did not reboot. I went to System Updates and downloaded the update again. It never went to Security Update Installing, step 1. I am on Magisk v 16.0 which passes the SafetyNet check, ctsProfile: true and basicIntegity: true. At this point, should I completely uninstall Magisk, flash the OreoFlashAll.zip or the NASH_TMO_C_OCX27.109-36_subsidy-TMO-regulatory-DEFAULT_CFC.xml.zip? Or something different?

lcc014 said:
Got AT&T update to 8.0.0 this morning.
Click to expand...
Click to collapse
Let us know if you lose the animated home button as I did after the At&t update. I asked the question in the room and no one answered. Hopefully I didn't break any rules by asking here. Thank you.
Sent from my Moto Z (2) using Tapatalk

May update for Fi Carriers!

Greetings,
Has anyone on Fi Project updated to the May Security with the
Google provided "Fi Carriers" firmware? And if yes, anything different
than the regular firmware for regular Security Update?
Thank you.

If you have access to a PC, just ADB sideload it. I've been on Fi for years and their update schedule is atrocious considering that this is Google's own phone service. I've gone as long as 6 weeks past an update release before it hit my phone through OTA. In any case, the only thing they specify carriers on the versions is for optimized radios for the specified carrier.

AndrasLOHF said:
If you have access to a PC, just ADB sideload it. I've been on Fi for years and their update schedule is atrocious considering that this is Google's own phone service. I've gone as long as 6 weeks past an update release before it hit my phone through OTA. In any case, the only thing they specify carriers on the versions is for optimized radios for the specified carrier.
Click to expand...
Click to collapse
Thanks for the reply.
Have you updated to this one yet, for May? Or just the regular Unlocked Firmware?!

samteeee said:
Thanks for the reply.
Have you updated to this one yet, for May? Or just the regular Unlocked Firmware?!
Click to expand...
Click to collapse
I sideloaded the one labeled Fi Carriers.

AndrasLOHF said:
I sideloaded the one labeled Fi Carriers.
Click to expand...
Click to collapse
Did your sideload take longer than usual? I'm on OPM2 for the April update and I seem to get stuck on validating package for OPM4. Not getting anything when I hit the update button in settings for the OTA.

miller7796 said:
Did your sideload take longer than usual? I'm on OPM2 for the April update and I seem to get stuck on validating package for OPM4. Not getting anything when I hit the update button in settings for the OTA.
Click to expand...
Click to collapse
Not too sure. I started the update then left it running on my work desk a while.

miller7796 said:
Did your sideload take longer than usual? I'm on OPM2 for the April update and I seem to get stuck on validating package for OPM4. Not getting anything when I hit the update button in settings for the OTA.
Click to expand...
Click to collapse
I'm on T-Mobile pre-paid and I went from OPM2 to OPM2 . It took the normal amount of time to sideload the ota update.

I just flashed the OMP4 system image without the -w and was up and running again in just a few minutes. It's a 1.6 gig download but it doesn't take long with a fast internet connection. I haven't noticed any difference between this build labeled for FI carriers and the OMP2 build I was on for April though.