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.

Playing the Slots: Firmware Slots on the Pixel XL

So, my Google Edition Pixel XL arrives tomorrow, and I've been digging around in preparation (I've previously owned the OG Droid and Galaxy Nexus, so consider myself marginally competent as a consumer of non-OEM firmware). Anyway, I'm super intrigued by the firmware slots I've heard mentioned, but was hoping for some clarification on how they work.
-Do they run from the same Data partition, so you can run one Kernal/ROM one day, and the other on another day, back and forth, forever...
-Or are they more like a nandroid backup?
Thanks for helping me understand this new feature,
Christian

Same data.
So remember what they were built for. They were built to run the same​ OS and provide seamless updates. They were not built for dual boot.
You can do a little trickery. Like same Rom with one rooted and one not pretty easily. Beyond that it is very tricky, there are a couple of folks here that seem to habe a handle on it.
Hopefully they will be along shortly.

The slots on the Pixel XL seem to trip up a lot of people who try to install TWRP, a custom Rom or root the phone. The really frustrating thing is that I did my research too and came across completely contradictory information regarding how they relate to custom flashing and should be handled. Even worse, the custom flashing guide on XDA for this phone is terrible. If you read through all the pages at various points it tells you to do something different than at the beginning of the thread and it doesn't deal with the dual slots at all. Google also seems to keep breaking root on the Pixel XL where SU programmers have to come up with updates and new flashing procedures to keep root working. The Pixel XL is the only phone I have ever owned that I am afraid to flash on, but if you are braver than me then I certainly wish you luck.

bricked pixel xl after july security update

Hey all,
I recently had to get my pixel replaced from Google and they sent me a refurbished one about a week ago. I updated to the July security update yesterday and over night my battery drained from 43% to 3% when I woke up. Took a shower and came back 15 mins later to find my pixel completely dead and wouldn't take a charge or anything. Weird thing is, my computer will find it in fastboot, but won't let me flash anything because it isn't the correct device even though I downloaded the factory images for the Verizon pixel XL, which I have. I'm just curious if anyone else experienced something like this after the update or if I got a bad refurb. Either way it's on its way back to Google now. I'm just curious before updating my broken phone to the new update

I'm not sure what you mean by it wasn't the correct device. If you were able to unlock the bootloader then Google didn't send you a Verizon Pixel XL which might be why you couldn't flash the Verizon image on your phone.

jhs39 said:
I'm not sure what you mean by it wasn't the correct device. If you were able to unlock the bootloader then Google didn't send you a Verizon Pixel XL which might be why you couldn't flash the Verizon image on your phone.
Click to expand...
Click to collapse
You can flash any of the pixel XL images to a pixel XL device. Whether it is Google or Verizon version makes no difference. Mines Verizon version running the T-Mobile build.

toknitup420 said:
You can flash any of the pixel XL images to a pixel XL device. Whether it is Google or Verizon version makes no difference. Mines Verizon version running the T-Mobile build.
Click to expand...
Click to collapse
I didn't know that. I thought maybe the build had to be the same variant that was originally shipped with the phone. Wonder what was meant by wasn't the correct device then?

jhs39 said:
I didn't know that. I thought maybe the build had to be the same variant that was originally shipped with the phone. Wonder what was meant by wasn't the correct device then?
Click to expand...
Click to collapse
I don't think his device was actually in the bootloader. Which could explain the incorrect device issue. I think he was in some Qualcomm mode. Which you need manufacturer tools to fix from there.

New to Pixel 2. Questions re Root/Magisk

Hey folks. Had the Pixel XL and was running Magisk, but wanted to get peoples impressions of root vs magisk on the Pixel 2.
Primary things I want it for: Adblocking, Viper audio, debloating, I can't even remember what the hell else I do.. (have been on a Samsung S9 temporarily after smashing my XL, didnt want to root for resale purposes)
Also, I know Pie just dropped, and the development here seems fairly active, so what is an estimated timeframe for 9.0 roms to drop? Not looking for ETA, so much as a general (1 month, 2 month, 3 years). On a similar note, is it possible to root/magisk the stock 9.0 rom? I see custom kernels, so methinks it is, but I want to be sure before I take the dive..
And finally, aside from warranty issues (which I don't qualify for anyways as my P2XL is second hand, and no invoice...stupid Australia), why WOULDNT I want to root?
Thanks

jewnersey said:
Hey folks. Had the Pixel XL and was running Magisk, but wanted to get peoples impressions of root vs magisk on the Pixel 2.
Primary things I want it for: Adblocking, Viper audio, debloating, I can't even remember what the hell else I do.. (have been on a Samsung S9 temporarily after smashing my XL, didnt want to root for resale purposes)
Also, I know Pie just dropped, and the development here seems fairly active, so what is an estimated timeframe for 9.0 roms to drop? Not looking for ETA, so much as a general (1 month, 2 month, 3 years). On a similar note, is it possible to root/magisk the stock 9.0 rom? I see custom kernels, so methinks it is, but I want to be sure before I take the dive..
And finally, aside from warranty issues (which I don't qualify for anyways as my P2XL is second hand, and no invoice...stupid Australia), why WOULDNT I want to root?
Thanks
Click to expand...
Click to collapse
No reason to not to root lol
Custom roms will come but slow
You can root pie as well with no problems
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs

I'm debating on taking the root plunge as well on my 2XL. Cannot decide either way. Not super familiar with ADB, but can read directions. Bricked my G2 back years ago, and had to reflash and such back to stock..Scary, but eventually got it to work.

AwkwardUberHero said:
I'm debating on taking the root plunge as well on my 2XL. Cannot decide either way. Not super familiar with ADB, but can read directions. Bricked my G2 back years ago, and had to reflash and such back to stock..Scary, but eventually got it to work.
Click to expand...
Click to collapse
Use this unofficial version of Magisk (1674) as opposed to the official (1671). https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
Why? Some users are experiencing boot issues with the official. This fixes it

Thanks for that. I am going to bite the bullet and do it today.

AwkwardUberHero said:
I'm debating on taking the root plunge as well on my 2XL. Cannot decide either way. Not super familiar with ADB, but can read directions. Bricked my G2 back years ago, and had to reflash and such back to stock..Scary, but eventually got it to work.
Click to expand...
Click to collapse
Just did mine (took 5 minutes). I am pretty comfortable with this stuff so let me know if you need any help.

jewnersey said:
Just did mine (took 5 minutes). I am pretty comfortable with this stuff so let me know if you need any help.
Click to expand...
Click to collapse
Did you just follow the steps one by one and it worked? I'll be doing this on Mac. Could install a VM with Windows if it makes it any easier.

I'm on windows, but you should be fine on Mac after installing ADB. Mac instruction for doing that are in the first post.
After that just follow directions to unlock and then install TWRP (my preference) .
Save everything important to your PC because it will get wiped.

[Bricked] Google Pixel 2 XL - OEM and BootLoader Locked. Could EDL be the solution?

So, i was reading a lot on xda. Trying to determine what i could do to bring my phone back to life.
I have a google pixel 2 xl, that shows a "Can't find a valid operating system"
Here is what caused it, plain and simple.
For whatever godly reason, i locked the oem and the bootloader.
Why? I got no idea, i really don't know what i was thinking.
No, adb debugging was not enabled, since i had just barely rooted it.
I was reading that perhaps it is possible to bring it back to life through edl, but all the conversations that had that key phrase didnt end up any where.
I already got another phone, so i would really like to use this as a learning experience, not just for me but for others that could potentially stop by and read this thread because they did the same thing as me.
Or could it be that it is just some fancy paper weight and EDL is a lost cause?
Thanks for any and all input.

lordsnoake said:
So, i was reading a lot on xda. Trying to determine what i could do to bring my phone back to life.
I have a google pixel 2 xl, that shows a "Can't find a valid operating system"
Here is what caused it, plain and simple.
For whatever godly reason, i locked the oem and the bootloader.
Why? I got no idea, i really don't know what i was thinking.
No, adb debugging was not enabled, since i had just barely rooted it.
I was reading that perhaps it is possible to bring it back to life through edl, but all the conversations that had that key phrase didnt end up any where.
I already got another phone, so i would really like to use this as a learning experience, not just for me but for others that could potentially stop by and read this thread because they did the same thing as me.
Or could it be that it is just some fancy paper weight and EDL is a lost cause?
Thanks for any and all input.
Click to expand...
Click to collapse
You're in the wrong section, this is the Pixel XL (Marlin) not the 2 XL, but I'll gladly take your paperweight .. lol

dictionary said:
You're in the wrong section, this is the Pixel XL (Marlin) not the 2 XL, but I'll gladly take your paperweight .. lol
Click to expand...
Click to collapse
ah darn it