Develop Bugs

I have a Google store pixel running on the Verizon build, and it seems hard to fix.

I'll try to keep it short, but;
I bought a Google edition Pixel XL from swappa because I saw a really good deal on it and couldn't pass it up. Though even though it's a google bought phone (I checked the IMEI and unlocked the bootloader with no problems, so it basically has to be), I'm on the Verizon build of NDE63X instead of NDE63V, which is the "regular" build. I'm not sure if this could pose any problems in the future, but I thought I'd try to get on the regular build in case.
I tried sideloading the normal OTA image, but it denied by saying it was out of date as compared the build I'm on now? It was downloaded straight from the Google developers page, so that doesn't seem to make sense to me. Eventually I toyed around and ended up flashing the phone with the google edition of the OTA, and everything seemed to be in order. All of this was a pretty long and painstaking process because I've known barely anything about the intricacies of Android before like 2 days ago and have just been learning it all from scratch. However, when I finally was in the V build over the X build, I saw my phone had an update; I went ahead and installed it just thinking that it was standard and maybe the OTA I flashed in was lacking the November security patch or something. When this update went through, it put me back on the X build. Needless to say I was a little frustrated, I kinda felt like I just wasted a royally large amount of time.
So I guess that leaves the question of; why/how exactly did this happen? Is it an issue?
My bootloader is unlocked now after that whole fiasco; should I relock it? Is it any kind of significant security issue? I've heard that relocking the bootloader can brick the phone entirely, and lord knows I don't want that.
If I keep the bootloader unlocked, what exactly can I do with it? I know it allows to install custom kernals/roms, but I'm not exactly sure what that's like or what it's exactly capable of. I know, this is a very general question that I could google. But I'd also just like to hear people's inputs about it.
Will my phone get regular updates with the bootloader unlocked, or would it unable/cause some kind of error?
Thanks in advance for any replies! Like I said, I'm still really new to this whole thing, so if you could kind of explain answers and/or instructions in kind of a black-and-white way that would help me a lot. All of this is kind of intimidating, but it's also been a lot of fun, I like learning about it all.

@cam30era
This is what I did, I actually had it on the V build, for all of about 20 minutes. Then it pushed an update through and the update changed it back to the X. I'm not sure if I screwed something up along the way or exactly how it happened, but it seemed like a kind of unique thing.

Actually, if you'd like to downgrade, make sure your bootloader is unlocked. Flash the boot image from the factory image zip. After that you can sideload the V ota.
Sent from my Pixel XL

So what exactly is your problem with the build that you have other than being the "Verizon" version? The phone isn't going to function any different and there are probably little to no differences in the software other than a letter on the build number.
Sent from my Pixel XL

Odds are that the radio is the only difference. There were different radios for the Nexus 6 between VZW and GSM, but the firmware was basically identical there too. I really don't get why everyone is hell-bent on the VZW firmware being different or no good with the Pixel but they weren't with past devices.
Sent from my Pixel XL

That would only affect models sourced from Verizon...
Sent from my Pixel XL

imnuts said:
Odds are that the radio is the only difference. There were different radios for the Nexus 6 between VZW and GSM, but the firmware was basically identical there too. I really don't get why everyone is hell-bent on the VZW firmware being different or no good with the Pixel but they weren't with past devices.
Sent from my Pixel XL
Click to expand...
Click to collapse
Agreed. AS long as you keep your bootloader unlocked you can flash what you want. If you see something amiss flash another version.
Flashing the verizon firmware on a Non verizon phone should be fine. @imnuts said, same questions and answers with the Nexus 6. I flashed all sorts of builds just to see how they would perform... IN the end there were all the same.

why has my pixel not received the 7.1.1 update yet?

when checking for system updates it says that i am on the latest update 7.1. i dont have the option to update to 7.1.1. does anyone have this problem?

FLUFFYMANGOES said:
when checking for system updates it says that i am on the latest update 7.1. i dont have the option to update to 7.1.1. does anyone have this problem?
Click to expand...
Click to collapse
I'm on Verizon and I'm in the same boat. I wouldn't sweat it. I'm sure it will come soon, these roll outs are staggered. On my old 6p it seemed I was always about a week or two out before getting the update.

I assume there will have to be an update to the root method before we will be able to obtain root after installing the new build?

Have you tried removing sim, rebooting, and trying to search for update again on WiFi with the sim out? My last phone was an unlocked model and it seemed like Verizon didn't want me to get updates but the above tip worked.
Sent from my Pixel XL using Tapatalk

I believe the OTA just came out today.
On other Pure Nexus devices I may not receive the OTA for a few days.
If your not rooted then you just download the system image from the google developer site. Take out the -W command to wipe device and you will be fully updated.

because your pixel is not l33t

The update states that it could take time for the update to become available in each location...

You can side load the ota with fastboot. That's what I did and Im on Verizon.

Updates typically roll out over the course of a couple of weeks. Be patient or sideload the OTA yourself

the thing is that i got my pixel straight from google and my friend who lives in the same area got his pixel from verizon and already has his update. My father's 1 year old nexus 6p already has the update as well clearly google does not have their priorities straight.

FLUFFYMANGOES said:
the thing is that i got my pixel straight from google and my friend who lives in the same area got his pixel from verizon and already has his update. My father's 1 year old nexus 6p already has the update as well clearly google does not have their priorities straight.
Click to expand...
Click to collapse
Most likely gets rolled out by production number or something. Your buddy's phone was probably made before yours, and your father must've purchased his Nexus 6P right when it was released. Like someone else said, these things take time anyways. Be patient or take the time to sideload the OTA yourself.
Sent from my Pixel XL using Tapatalk

Funny my Pixel C got the update yesterday.

I had a strange issue - I hit "Check for Update" and my device began downloading the 263MB update. Once finished downloading, it went to step 2, however it never moved past Step 2. A restart didn't fix the issue. Anything I can do? I'd obviously still would like the update despite whatever strange bug this is. This is a Google Store bought Pixel, on T-Mobile.

Project Fi phone on "V" image.
So yesterday I restored to stock V image.
Wiped everything.
Installed factory V.
Didn't root, kernel or install TWRP.
Nada.
Then checked every hour or so for the O update.
Nothing.
Here I am, 24 hours and still no update available.
So I tried turning off WiFi.
Rebooted.
Waited 20 minutes and then checked and found an update.
Could just be coincidence or maybe enabling data (turning off WiFi) somehow triggered the update as being available.

Verizon Pixel Updated to NMF26U - Re-Lock Bootloader or No?

So I got a Verizon Pixel XL NDE63P and unlocked the bootloader. I then updated to NMF26U (Stock Image). If I lock the bootloader will it get stuck since it isn't a verizon Image? or will it be ok since it is a Pixel stock image? I'm trying to get rid of the ugly corruption message.

message will always be there. Do not relock the bootloader my friend.

Alright thanks.

Quite a few people here that tried it and now have completely bricked phones.

I'll just leave it alone then....

This may sound strange but if it really bothers you then you could see if someone on here with a locked vzw device is interested in a swap. It would require some trust but could be mutually beneficial.

efaden said:
So I got a Verizon Pixel XL NDE63P and unlocked the bootloader. I then updated to NMF26U (Stock Image). If I lock the bootloader will it get stuck since it isn't a verizon Image? or will it be ok since it is a Pixel stock image? I'm trying to get rid of the ugly corruption message.
Click to expand...
Click to collapse
There is absolutely no difference between the software you have and the software that's on a google bought pixel. They have been releasing the same exact build for both devices. There is no difference between the two. However if you ever lock your bootloader you will never be able to unlock again.

cntryby429 said:
This may sound strange but if it really bothers you then you could see if someone on here with a locked vzw device is interested in a swap. It would require some trust but could be mutually beneficial.
Click to expand...
Click to collapse
I want it unlocked. I just don't want the ugly screen.... but I can deal with it.

Don't mess with it.
One day we may have the ability to alter this screen. But people aren't working on that since it's so minor.

The Pixel XL shows that screen for less than 10 seconds. The Pixel C is over 30 seconds. I can live with 10 seconds.

Mike02z said:
The Pixel XL shows that screen for less than 10 seconds. The Pixel C is over 30 seconds. I can live with 10 seconds.
Click to expand...
Click to collapse
I consider it a "Badge of Honor".

Custom Recovery?

I did some quick research and didn't find anything on TWRP for the Pixel 2 XL. There were a few guides that said to use the Pixel XL img but that sounds like a bad idea. I'm just wondering if anyone knows anything about it. Thanks

nitro_89 said:
I did some quick research and didn't find anything on TWRP for the Pixel 2 XL. There were a few guides that said to use the Pixel XL img but that sounds like a bad idea. I'm just wondering if anyone knows anything about it. Thanks
Click to expand...
Click to collapse
If you use any Pixel 1 files on your Pixel 2, you're gonna have a bad time. Seriously though, root and recovery will come in due time, and there'll probably be device specific files and instructions because of the dual nightmare partitions and recovery is likely tied in with the boot partition like with the original Pixels. Hopefully though since a lot of the hurdles were passed figuring it out on the OG Pixel it shouldn't be as long of a wait. Staying optimistic.

PIXEL 2 XL QUESTIONS ~ Bootloader, Black Smudge, Etc.

After unlocking the Bootloader on my Pixel 2 XL (Android 8.1 DP1) my Play Store Device Certification as "Uncertified", is that normal??
Also, I've seen thread about the screen's Blue shifts and comparing build date but has anyone compared the Black smudge effect?
My RMAed Pixel2 XL (Build date 10/18) has it really bad. Is everyone experiencing this? Is it just part of the POLED Tech?
Lastly, has Android 8.1 DP1 been buggy for anyone? It's constantly crashing the Google app and sometimes doesn't register taps on my screen (across all apps different locations)
I've Factory resetted twice this week.
Thanks!

I unlocked my Pixel and this shows whenever I turn my phone on/off. I've never owned a Pixel or Nexus, is this normal?

rank78 said:
I unlocked my Pixel and this shows whenever I turn my phone on/off. I've never owned a Pixel or Nexus, is this normal?
Click to expand...
Click to collapse
Yes, that is normal. You need not worry.

Also, it cannot be removed. It will always show if you have an unlocked bl

You'll need to get used to that message...

Lawlrus said:
Also, it cannot be removed. It will always show if you have an unlocked bl
Click to expand...
Click to collapse
galaxys said:
You'll need to get used to that message...
Click to expand...
Click to collapse
Dammit, it's annoying as hell. Thanks guys.