7.1.1 for the Nexus 6P on Verizon
- Thread starter Bebusy
- Start date
I just received a replacement phone from Google for my 6P for a problem. I'm on Verizon. After activating it, it prompted to update to 7.1.1. After updating it I noticed that it is NMF26F. I thought that build is not for verizon. Also noticed that it is still at the December security patch level.
vzwuser76
Well-known member
- Jan 28, 2011
- 1,669
- 26
- 0
That's what I figured. I could understand if there was an issue making WiFi Calling work on the Verizon 6p's, but otherwise it shouldn't be any different than any past updates, so I don't see what the problem is.
Maybe google compares your V build against the file list on the ota website, which does NOT include the V build.
So, their software logic is, nope not there, so no new ota to anything later is not pushed.
I ended up sideloading the J build. Interesting to see whether my J is now visible to google, and will receive the next update in February.
If you are on V, you might be stuck there until google changes their ota decision logic. Gosh, all they might need to do is put the V build onto the ota website to make your V phone visible.
So, their software logic is, nope not there, so no new ota to anything later is not pushed.
I ended up sideloading the J build. Interesting to see whether my J is now visible to google, and will receive the next update in February.
If you are on V, you might be stuck there until google changes their ota decision logic. Gosh, all they might need to do is put the V build onto the ota website to make your V phone visible.
Mikey D_PhD
Well-known member
- Apr 4, 2011
- 430
- 36
- 28
Bit the bullet and sideloaded the J build. No issues so far. We'll see how the February update goes, I suppose.
I've tried a couple times to sideload, but I keep getting an error in adb that it can't read the file when I try to send it. You should be able to download the zip file straight to your phone and install it that way without using a pc
GSDer
Well-known member
- Jan 30, 2011
- 8,469
- 15
- 0
The file is in the same directory as ADB?
You verified the checksum to make sure you got a good download?
GSDer
Well-known member
- Jan 30, 2011
- 8,469
- 15
- 0
Yea. Checked everything. Even re-downloaded. Reloaded drivers. Just to make sure everything was good. Guess I'll just wait for it to get pushed whenever that may be
Mikey D_PhD
Well-known member
- Apr 4, 2011
- 430
- 36
- 28
FYI... Once I did the "ADB reboot recovery" command and then phone rebooted, I then pressed volume up and power to get to the recovery menu. After selecting "apply update from ADB" and before typing the command line for the ADB sideload, I unplugged and replugged the USB cable and made sure that windows device manager saw the phone. The first time I used the ADB command to reboot into recovery, Windows didn't "see" the phone. Unplugging and replugging the USB cable fixed that issue for me.
Also...Make sure you get the OTA file and not the factory image. The download pages for both are very similar.
Also...Make sure you get the OTA file and not the factory image. The download pages for both are very similar.
Thanks for the info. I'll double check everything and try again sometime this week. Pretty sure I got the ota downloaded but I'll see. I'll also try unplugging and plugging in again to make sure
Reading the last few posts ... it really is time for someone to pop in and say again how it's so super easy to sideload that people must be crazy stupid not to do it...
Mikey D_PhD
Well-known member
- Apr 4, 2011
- 430
- 36
- 28
Make sure you're opening the SDK Manager.exe file to check for updates. I was having a very similar issue to the one you've described, and I realized that the program needed to update since the last time I had used it to sideload an earlier OTA file. This program is in the sdk folder, and the sdk folder is in your Android folder.
jordans0nly
Well-known member
- Jun 26, 2010
- 446
- 1
- 18
I just read this whole thread. Looking at picking up a 6p, but man, lol. Nah. Jk. Side loading shouldn't be a problem.
Looks like there is a new file for OTA
https://developers.google.com/android/ota#angler
7.1.1 (NUF26K, Feb 2017, Verizon Only) Dont see any chnages on my prepaid Verizon. No WiFi calling, no Visual voicemail.
https://developers.google.com/android/ota#angler
7.1.1 (NUF26K, Feb 2017, Verizon Only) Dont see any chnages on my prepaid Verizon. No WiFi calling, no Visual voicemail.
Last edited:
Well, I think with this we can discard the theory that they're conspiring with VZW to push us toward Pixel. Now, if we can just get this pushed to our phones...
Nate Silver
Well-known member
- Apr 6, 2016
- 46
- 0
- 0
Similar threads
Trending Posts
-
-
Pixel 7 Adobe deleted files by accident, how to recover
- Started by R1945
- Replies: 11
-
-
-
Facebook
Twitter
Instagram