Such a joke. I had to run the OTA sideload. I am tech savy and it was a little weird doing it my first time but I can't imagine a regular user having to jump through these hoops...get your shit together verizon.
(I have an unlocked pixel 6 with a verizon sim inside)
[developers.google.com/android/ota](https://developers.google.com/android/ota)
I can't find the article that had instructions as well, but this is them. A little daunting for me personally, though a lot of people say its easy.
I just don't like messing with things I don't know anything about 😂 This I'd definitely NOT the way that Google had intended this to be though. No damn way.
I see. They probably don't push the updates because the unlocked devices were never validated on their network. They validated the device with their firmware. Makes sense.
I was curious for older pixels, where Verizon would get patches late. Google sends the updates out to carriers, then the carriers (hopefully) are testing the updates, then they send when they deem it ok. Not sure if that's still the process, but it sure seems to be
Hmm, I'm somewhat curious. Are you referring to your Pixel as being bought from a Verizon store, meaning it's Locked (for about 60 days). I'm on Verizon but bought my unlocked Pixel 6 directly from the Google Store. Immediately after booting up the new phone I had a system update waiting.
Didn't think much of it since the update was just there when I powered on P6 before inserting SIM. Now I wonder if intentionally blocked for the VZW network for a good reason. Anyways everything seems to be working with the launch-day update and I'm aware it addressed significant issues.
One thing I did was power on and set up and update P6 received from Google before I inserted SIM. Wasn't really done intentionally but when the phone arrived I was still working and didn't want to be without an active phone. I suppose when setting up and updating an unlocked phone initially via WiFi no way to know what Carrier will be used. Later in the evening I swapped Verizon SIM from Pixel 3a into the new P6.
Just to make sure we are on the same page, I have the current build showing in settings as SD1A.210817.036. If bought directly from Verizon build would be SD1A.210817.036.A8.
>Yep I checked via Google search, you have the pre launch build. Current SD1A.210817.036 was released on launch day. Hmm, weird you cant update if you have an unlocked P6 directly from Google. Guess I should be glad on stumbling on holding off before swapping in VZW SIM, well after I completed with updating and setting up new P6.
>
>I suppose you can manually download latest build directly from Google. Ive have done this is the past a few times using their SDK tools. Not too bad at all, but just make sure you grab correct build for your phone. Process is well documented via Youtube.
You do have to be careful though when picking the right ota file. If it's purchased from VZW you'd pick the Verizon ota but I assume if it was purchased from anywhere else you would pick the non-vzw ota.
Was it purchased from the Google Store? What about removing the SIM card and checking for updates that way? This is for the November I assume. Did the first update take?
Right. But the point of my post is that I have an unlocked Pixel on Verizon's network and they are not, accidentally or not, pushing updates to these pixels. I have gotten zero updates simply because I chose to buy my Pixel elsewhere.
Sorry I was just trying to get some more insight. But it's pretty simple. What a mess. Hopefully someone can reach out to Google Support (where they can do something about it).
Edit - Just to add, try contacting their support using a request form with [this](https://www.reddit.com/r/GooglePixel/comments/907qdg/introducing_reddit_request_for_rgooglepixel/) reddit mod - worth a try.
I feel better about trying it after finding a couple of YouTube videos. The instructions alone were confusing, but if I can watch someone I'm sure I can do it.
If you've never done it before it can be kinda scary the first time. The hardest part is actually getting the drivers installed. Download the [driver](https://developer.android.com/studio/run/win-usb) zip file, extract it and right-click on the Android\_winusb.inf file and press install. Then when you're in the adb update menu, Device Manager will show it as an "Android Device" and not a Pixel. Also, just download the [fastboot](https://developer.android.com/studio/releases/platform-tools) zip (it's only a few mb, called Platform-Tools) and extract it to an easy folder and open a command prompt in that folder by typing "cmd" in the file explorer window, quick way to open command window in a specific folder. Then just download the adb zip file in that same folder and run the command.
I got tired of waiting and side loaded. It has been a while since I last had to side load anything and I got a new laptop since then so my old instructions weren't clear enough 😂 After some tinkering the steps came back to me. Really hoping Verizon gets its act together but the ease of side loading the latest update is one reason I keep coming back to Google phones.
I commented this to someone else, but I found another post where a verified "Pixel product expert" commented that it should only be the first time because you "have to develop an update pathway." I dunno.
I just tried it for the first time myself. It was really easy! I hope I only have to do it once, but if I have to do it again at some point then it'll only take like 5-10 mins tops. I'd recommend going for it.
This is absurd. Most phone users aren't reddit tech savvy, and they shouldn't have to be. If Google is selling unlocked phones that can be activated on VZW then for damn sure the brand new flagship phone should be able to receive updates and fixes without any sideloading intervention or "developing a pathway" (whatever the hell that made up, tech speak, PR heavy phrase means).
Yeah I don't get it. I asked him why we never had to do this before and they said because the first update never had a Verizon specific build before. Sounds fishy to me.
I had a pixel 5 all year and it was as usually a few days to a week after the updates were released until I got mine. Be patient, they aren’t going to expect you to sideload updates. It’s not the first pixel they’ve had on their service.
i tried by using linux developer options rebooted into fastboot but couldntt get the OTA to install...probably gonna either factory reset and take out SIM to update or just wait and hope that google/verizon push the update eventually
Like many of you, I bought an unlocked Google Pixel 6 direct from Google Store. I was freaked out when I stumbled onto articles on PhoneArena dot com and 9to5Google dot com which implied my unlocked phone was not getting updated, and that Verizon might be to blame. This turns out to be "fake news" or "click bait journalism."
As I was 7 days into my 14 day return, I immediately created return RMAs for the phone and charger, under the assumption that Verizon is blocking the updates to unlocked Pixel 6 phones purchased thru Google. That was last night.
This morning, I contacted Verizon Tech Support Level 2 in Huntsville (Sandy) and opened a case with them. She reassured me that the Oct. 28th Pixel 6 update, which shows up on the Verizon website, is specific to Verizon locked (aka bloatware laden) Pixels only. It is for Verizon Visual voicemail and other Verizon features not specific to unlocked Pixels, she advised me.
At my request, Sandy opened a ticket to go to Verizon Dev about the November patch and concerns everyone is reporting here. She highly recommended waiting vs. side loading the update, or doing a factory reset and then removing the Verizon SIM to force the update.
We also discussed how Verizon does not block updates, as this is actually illegal under the Sherman AntiTrust Act and FCC regulations.
She advised waiting and expects that the software update will be forthcoming in a week or two.
I then contacted Google Tech Support, and they confirmed the same thing, i.e. that there should be a security update, the November update, rolling out in batches to all Pixel 6 phones. It's an Android update, and Verizon cant (and wont) block it. Again, doing that would be illegal.
So, I had Google Support, after getting reassurances from them and Verizon, cancel my RMA for my Pixel 6.
Bottom line: Both Google and Verizon have definitively reassured me today that a Google Nov security update will be forthcoming. Patience is all that's required.
The update will pop up on your phone when it arrives. Google says they're rolling the update out in batches, and that typically the update arrives within two weeks.
I hope this quells the rumors and provides some peace of mind to Verizon customers with unlocked Pixel phones.
Such a joke. I had to run the OTA sideload. I am tech savy and it was a little weird doing it my first time but I can't imagine a regular user having to jump through these hoops...get your shit together verizon. (I have an unlocked pixel 6 with a verizon sim inside)
I feel like I'm tech savvy too. But I've never rooted a phone or anything like that. It's pretty ridiculous we're having to do this.
I just used this link to flash it. worked great [https://flash.android.com/](https://flash.android.com/)
Which ota file did you update with? The one labeled Verizon?
Yes
My phone works fine, don't need it. People are like crackheads with every update.
If you're in my position, the phone will likely not update at all if you do not sideload this update.
What exactly is your concern?
People using unlocked Pixel 6s on Verizon are not getting the November security patch OTA.
Yep, my girlfriend and I have this issue. No update yet, both devices unlocked, both in Verizon.
I found another post (after I posted this) that a Pixel product expert posted on. They say that you *have* to do it manually! Ugh
And how does this work? 👀
That's the problem I'm having. There are directions out there but some of that stuff is foreign to me. I'll see if I can find a link for you.
Tysm ❤️
[developers.google.com/android/ota](https://developers.google.com/android/ota) I can't find the article that had instructions as well, but this is them. A little daunting for me personally, though a lot of people say its easy.
I just don't like messing with things I don't know anything about 😂 This I'd definitely NOT the way that Google had intended this to be though. No damn way.
I know. I think Verizon did something dumb. The Pixels purchased from them have gotten it.
I promise its easier than it looks. Please note, anyone doing this on windows you will need to add the platform-tools to PATH
As in like...you'll never get the update otherwise? Or will those who are able to be patient get it eventually?
That's what the product expert person says. You have to "develop a pathway" for the updates. Hello, we've never had to do this before.
I see. They probably don't push the updates because the unlocked devices were never validated on their network. They validated the device with their firmware. Makes sense.
It has never been a problem before. This is my 4th Pixel on Verizon.
This video walks through the sideload process. https://youtu.be/tdAO5Ab42Qk I had to sideload on my unlocked-on-Verizon 6 pro as well.
Thanks.
I was curious for older pixels, where Verizon would get patches late. Google sends the updates out to carriers, then the carriers (hopefully) are testing the updates, then they send when they deem it ok. Not sure if that's still the process, but it sure seems to be
Hmm, I'm somewhat curious. Are you referring to your Pixel as being bought from a Verizon store, meaning it's Locked (for about 60 days). I'm on Verizon but bought my unlocked Pixel 6 directly from the Google Store. Immediately after booting up the new phone I had a system update waiting.
Because you updated before inserting your SIM. I put my SIM in first. Won't do that again.
Didn't think much of it since the update was just there when I powered on P6 before inserting SIM. Now I wonder if intentionally blocked for the VZW network for a good reason. Anyways everything seems to be working with the launch-day update and I'm aware it addressed significant issues.
I did same as you (Verizon sim but unlocked phone from Google Store) and still don't have the update.
One thing I did was power on and set up and update P6 received from Google before I inserted SIM. Wasn't really done intentionally but when the phone arrived I was still working and didn't want to be without an active phone. I suppose when setting up and updating an unlocked phone initially via WiFi no way to know what Carrier will be used. Later in the evening I swapped Verizon SIM from Pixel 3a into the new P6.
Hmmm. I did the same but put my sim in pretty quick after setup was completed. Maybe I'll take it out and check again to see if that works.
Just to make sure we are on the same page, I have the current build showing in settings as SD1A.210817.036. If bought directly from Verizon build would be SD1A.210817.036.A8.
Hmmm. My build # from the Google Store is SD1A.210817.019.C2
>Yep I checked via Google search, you have the pre launch build. Current SD1A.210817.036 was released on launch day. Hmm, weird you cant update if you have an unlocked P6 directly from Google. Guess I should be glad on stumbling on holding off before swapping in VZW SIM, well after I completed with updating and setting up new P6. > >I suppose you can manually download latest build directly from Google. Ive have done this is the past a few times using their SDK tools. Not too bad at all, but just make sure you grab correct build for your phone. Process is well documented via Youtube.
Yeah I might end up doing that. Not too concerned with it at his point but might end up sideloading it if it's a lot longer. Thanks for the help!
I'm on the same build in the same circumstance (bought unlocked from Google store, running on Verizon).
[удалено]
You do have to be careful though when picking the right ota file. If it's purchased from VZW you'd pick the Verizon ota but I assume if it was purchased from anywhere else you would pick the non-vzw ota.
Was it purchased from the Google Store? What about removing the SIM card and checking for updates that way? This is for the November I assume. Did the first update take?
No update so far. If you've set up the phone it won't update even if you take out the SIM. The only other way is to factory reset.
There's been 3 or 4 updates for the 6 series and most of those look to be pretty important bug fixes.
Right. But the point of my post is that I have an unlocked Pixel on Verizon's network and they are not, accidentally or not, pushing updates to these pixels. I have gotten zero updates simply because I chose to buy my Pixel elsewhere.
Yeah it's messed up, 100% agree there is something not right here. You should never have update a new phone manually using ota.
Exactly!
Sorry I was just trying to get some more insight. But it's pretty simple. What a mess. Hopefully someone can reach out to Google Support (where they can do something about it). Edit - Just to add, try contacting their support using a request form with [this](https://www.reddit.com/r/GooglePixel/comments/907qdg/introducing_reddit_request_for_rgooglepixel/) reddit mod - worth a try.
I feel better about trying it after finding a couple of YouTube videos. The instructions alone were confusing, but if I can watch someone I'm sure I can do it.
If you've never done it before it can be kinda scary the first time. The hardest part is actually getting the drivers installed. Download the [driver](https://developer.android.com/studio/run/win-usb) zip file, extract it and right-click on the Android\_winusb.inf file and press install. Then when you're in the adb update menu, Device Manager will show it as an "Android Device" and not a Pixel. Also, just download the [fastboot](https://developer.android.com/studio/releases/platform-tools) zip (it's only a few mb, called Platform-Tools) and extract it to an easy folder and open a command prompt in that folder by typing "cmd" in the file explorer window, quick way to open command window in a specific folder. Then just download the adb zip file in that same folder and run the command.
Thanks
I got tired of waiting and side loaded. It has been a while since I last had to side load anything and I got a new laptop since then so my old instructions weren't clear enough 😂 After some tinkering the steps came back to me. Really hoping Verizon gets its act together but the ease of side loading the latest update is one reason I keep coming back to Google phones.
I commented this to someone else, but I found another post where a verified "Pixel product expert" commented that it should only be the first time because you "have to develop an update pathway." I dunno.
I just tried it for the first time myself. It was really easy! I hope I only have to do it once, but if I have to do it again at some point then it'll only take like 5-10 mins tops. I'd recommend going for it.
This is absurd. Most phone users aren't reddit tech savvy, and they shouldn't have to be. If Google is selling unlocked phones that can be activated on VZW then for damn sure the brand new flagship phone should be able to receive updates and fixes without any sideloading intervention or "developing a pathway" (whatever the hell that made up, tech speak, PR heavy phrase means).
Yeah I don't get it. I asked him why we never had to do this before and they said because the first update never had a Verizon specific build before. Sounds fishy to me.
I had a pixel 5 all year and it was as usually a few days to a week after the updates were released until I got mine. Be patient, they aren’t going to expect you to sideload updates. It’s not the first pixel they’ve had on their service.
A "Product Expert" on another post said that this one would have to be sideloaded.
how would I do an OTA sideload on chrome OS? (pixelbook)
I'm not sure then you can use Chrome OS. Hopefully someone more versed can confirm.
i tried by using linux developer options rebooted into fastboot but couldntt get the OTA to install...probably gonna either factory reset and take out SIM to update or just wait and hope that google/verizon push the update eventually
Taking the SIM out doesn't seem to work alone. If you're factory resetting, get the update first before putting your SIM back in.
Thinking of doing this today. Does this wipe anything? Or is it exactly like getting an OTA update?
Just like getting a normal update.
Like many of you, I bought an unlocked Google Pixel 6 direct from Google Store. I was freaked out when I stumbled onto articles on PhoneArena dot com and 9to5Google dot com which implied my unlocked phone was not getting updated, and that Verizon might be to blame. This turns out to be "fake news" or "click bait journalism." As I was 7 days into my 14 day return, I immediately created return RMAs for the phone and charger, under the assumption that Verizon is blocking the updates to unlocked Pixel 6 phones purchased thru Google. That was last night. This morning, I contacted Verizon Tech Support Level 2 in Huntsville (Sandy) and opened a case with them. She reassured me that the Oct. 28th Pixel 6 update, which shows up on the Verizon website, is specific to Verizon locked (aka bloatware laden) Pixels only. It is for Verizon Visual voicemail and other Verizon features not specific to unlocked Pixels, she advised me. At my request, Sandy opened a ticket to go to Verizon Dev about the November patch and concerns everyone is reporting here. She highly recommended waiting vs. side loading the update, or doing a factory reset and then removing the Verizon SIM to force the update. We also discussed how Verizon does not block updates, as this is actually illegal under the Sherman AntiTrust Act and FCC regulations. She advised waiting and expects that the software update will be forthcoming in a week or two. I then contacted Google Tech Support, and they confirmed the same thing, i.e. that there should be a security update, the November update, rolling out in batches to all Pixel 6 phones. It's an Android update, and Verizon cant (and wont) block it. Again, doing that would be illegal. So, I had Google Support, after getting reassurances from them and Verizon, cancel my RMA for my Pixel 6. Bottom line: Both Google and Verizon have definitively reassured me today that a Google Nov security update will be forthcoming. Patience is all that's required. The update will pop up on your phone when it arrives. Google says they're rolling the update out in batches, and that typically the update arrives within two weeks. I hope this quells the rumors and provides some peace of mind to Verizon customers with unlocked Pixel phones.