yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Polishow:
Anybody else with this problem? My 6 Pro gets soft bricked with the

SD1A.210817.036.

It loses the signal (Tmobile) then restarts to recovery saying

“Cannot Load Android System. Your Data May Be Corrupt” It gives me the option to "Try again." or to "Factory data reset."

Device Completely stock

This is what I have done

1

Try Again (Same behavior)

2

Factory Reset (Multiple times), would let me finish the setup but as soon restores my data and apps happens all over again.

3

Sideload Rescue OTA (SD1A.210817.036.) same ****

4 now with heavy weapons

Unlocked bootloader, manually flashed factory images (Unlocked) the factory image it's an older version but seems to work perfectly (I'm able to set up and restore my data, but the phone automatically downloads the OTA update and the same thing all over.

5

Got a device replacement (Hella lucky they had my device in stock)

6

Different new Pixel 6 Pro Same behavior as soon the OTA hits and finishes to restore my apps.

7

Tried Manually flash, use the online google tool with different builds (tried the Tmobile stock)

Always the same problem.

There's any way to wipe/repartition only the System portion? I remember having something similar back in the days with an S2 and was able to fix it with a Reflashing of the PIT partition through Odin

Any suggestions?
[Google Pixel 6 Pro] mang0:
Are you able to take the OTA with a fresh start / no restoring data and apps?
[Google Pixel 6 Pro] Podster16:
updated in the uk but phone is getting warm during use and battery life is poor, well compared to Huawei p30 pro its actually shocking, about half at best as i'm used to multiday battery life

The UI isn't as user friendly as EMUI, why is it so bad compared to EMUI, thought getting a Pixel phone would be an improvement, how wrong was i.

how quick are the software updates for these phones hopefully improvements are on the way
[Google Pixel 6 Pro] Morgrain:
My accubattery says that my P6 Pro is capable of delivering 9h54minutes of SoT (discharge rate of roughly 10%/1hour), not sure if you are trolling, if you have a rogue app, a broken phone or if the P30 Pro indeed only loses 5% battery every hour of SoT, which would be a monstrous achievement.

What is known however, and not everyone is aware of that, is that Google phones are constantly calling home - meaning they offer 100% app functions - and because of that, "idle" battery life (like 1% lost every hour, depending on the amount of apps, more) is relatively bad. You can easily fix this with apps like Naptime or Servicely, even though those might only function in a limited way without root.

As a reference: https://dontkillmyapp.com/

What should also be mentioned, is that Google Pixels are not multi-day. They are designed by Google to run for one day, and for one day safely (anticipated battery saving functions, whatnot) - it's their decision to guarantee all app functions and therefore limit their phones battery life somewhat (some also call it: "muh spying, no good" - even though that only leaves me with a chuckle, Google already knows almost everything there is to know about most people, they don't need more information to know when you take a sh*t or watch porn), if you are looking for a mutli-day battery phone, Pixels can't help you (except if you root and use something like LKT like I usually do, that way you can get the awesome Pixel experience + awesome battery life) - but that requires work and of course you don't have to or should, if you don't like that.

--

Concerning the phone getting warm, I am still not able to replicate this (except shooting videofootage, which is normal for the phone to get warmer, even though I certainly wouldn't call it hot, it doesn't get uncomfortable, it's just noticeable that it gets warmer) - are you, by chance, active in 5G networks? There is no 5G connectivity near my home, so I never used that, I am 4G or Wifi only. Maybe this is the rootcause for those people here that talked about heat issues.

What might also cause a heat issue is a big ass case that might trap heat between the phone and the case - do you use a case? which one do you use? Maybe we can further narrow it down, if people with the same set of problems all use 5G and/or have similar cases.
[Google Pixel 6 Pro] Morgrain:
I also still wait for the update (EU unlocked, still running on pre-release .015), I talked to a Google rep and first he claimed that if the phone doesn't get an update, it's up to date - after telling him "no, I know that newer firmware is already out" - he checked for a minute and then told me, that I should expect the rollout for all phones including mine in the next 3 days.
[Google Pixel 6 Pro] Podster16:
not sure on the screen on time but i have done nothing different to my normal saturday, so drove to MTB ride phone 100% out on the bike taking a few photos, its no not even 12hrs later and im down to 25% which is poor compared to P30 pro, not had a phone this bad on battery since iphone 3, this is just my experience so far lets hope there is a software update, i have the same apps installed on both phones, maybe EMUI just manages battery/apps better and my previous windows and Huawei phones have raised my expectations of what is an acceptable standard for battery life

as for the heat no case fitted as yet, i have now turned off the 5g now after reading other posts, buts thats poor if buying a phone with 5g but the only way to get average battery life is turn off functions, just WOW
[Google Pixel 6 Pro] Morgrain:
If that's the case, that definitely sucks - Google will probably be able to somewhat mitigate such a 5G battery life/heat problem with an update, even though that will probably result in slower speeds (not much else to do if a relatively "old" modem is relatively inefficient), but that's just a wild guess from me, maybe it's even a simple bug that can be fixed easily. But you never know until it happened.
[Google Pixel 6 Pro] Frankie1588:
Thanks everyone for their response regarding the update on Verizon. Wasn't sure if I was an outlier.
[Google Pixel 6 Pro] Polishow:
Yes
[Google Pixel 6 Pro] iceman4357:
I am on Verizon with unlocked Google phone and still have yet to get the update. I wonder if I take the SIm out if it will get it to go? Dont have another SIM to pop in. Assume that probably next week Verizon people will get the update I hope. Looking forward to better finger print reader. I am a little underwhelmed by the photos of the 6 Pro. Hope they improve the quality/consistency between the zoom, regular and wide angle.
[Google Pixel 6 Pro] stevek216:
Same here, Verizon no update
[Google Pixel 6 Pro] snovvman:
From what I can gather, those using a Verizon SIM (even with unlocked phones) are not getting a push. When another carrier's SIM is inserted, OTA is received. Aside from the delays for the VZ OTA, this leads me to believe that even an unlocked, non-Verizon Pixel 6/Pro, the image due is A8. However, I would like to confirm.

For you who have an UNLOCKED device AND Verizon SIM inserted, when you get your OTA, please report the version of the image--.036 or .036.A8?

Thanks.
[Google Pixel 6 Pro] jrg67:
Add me to the list. P6P unlocked on Verizon, no update available. Not sure what is happening but Google better work it out quickly. Just for good measure, I looked on Verizon's website for the P6P and it does have the software listed as available since 10/28 and it does have A8 at the end so we do know that is definitely for the Verizon bootloader locked variant. The question still though is if that will be what us google store unlocked people get on vzw. I'd just load the ota via connecting to my computer but I don't want to load the wrong one. This makes no sense.
[Google Pixel 6 Pro] snovvman:
Now that A8 has posted, give it a day or two, let's hope it will push to your phone soon. Please do report back if/when it does.
[Google Pixel 6 Pro] Cares:
I'm using unlocked on Verizon and just manually flashed OTA Verizon version SD1A.210817.036.A8... No issues that I'm noting so far. Using the OTA instead of the full images seems to be the only way to avoid wiping your device if you want to maintain root.
[Google Pixel 6 Pro] jrg67:
So the .A8 did not take away your ability to unlock the bootloader?
[Google Pixel 6 Pro] Cares:
I'm on an unlocked Pixel not Verizon version so I don't think any version would take away my ability to unlock. Either way, I was already unlocked prior to sideloading the OTA and remained unlocked/rooted so I don't know if the patch did anything to the ability to unlock.
[Google Pixel 6 Pro] jrg67:
I understand. This is sort of frustrating to not be able to update and not knowing what's going on. I've had Nexus and Pixel phones on vzw for 8 years and this is literally the first time an OTA hasn't been available at 2pm EST on the first Monday of the month.
[Google Pixel 6 Pro] TonikJDK:
It did not, nor will it in the future. These carrier specific versions have always been just modem network differences. They will all be merged into one release in the next month or two. It will happen again.
[Google Pixel 6 Pro] jrg67:
Thanks for the clarification Tonik, I may end up just side loading the OTA tonight then.
[Google Pixel 6 Pro] TonikJDK:
Just to follow up with more details after sideloading the VZ version I can still slide the unlock slider. I did that before posting the above and should have mentioned.
[Google Pixel 6 Pro] JasonVaritekMVP:
Thanks for the follow-up. I may run mine unrooted for first time since froyo but I definitely want to be sure not-unlocking the bootloader doesn't cost me the ability to do so in the future. Your report is comforting.
[Google Pixel 6 Pro] xray49er:
I am also on Verizon with the October security update c2. Does it matter if I flash the Verizon firmware or can I just flash the global firmware with no letter number combination at the end?

Thanks
[Google Pixel 6 Pro] xray49er:
I got impatient and just flashed the global ota. All my Verizon services work and I can still switch my oem unlock for future use. Just didn't want to take the chance with Verizon. I'm not around any of the mmwave so I could care less about that. Actually I don't even know if that works since I didn't pay the 10 dollar upgrade fee that Verizon charges.
[Google Pixel 6 Pro] ridobe:
I have an unlocked google version P6P and I'm on Verizon. I have updates turned off because I like to flash the images myself. I don't care about root any more. But, bootloader is clearly unlocked. They cannot and won't lock the bootloader.

I flashed the .A8 image first thing. No issues for a while but I noticed I didn't have cell service (sitting at home on wifi). Went for a bike ride and my buds stopped playing because my phone wouldn't connect. Came home and flashed the global version and I've had service ever since. No idea what the difference is, but I really don't think it matters even when the modem is different. In the past, i've flashed different versions and I don't think I've ever seen a difference.
[Google Pixel 6 Pro] jrg67:
I just flashed the Verizon OTA .A8 to my G-Store purchased unlocked non Verizon phone and I'm fine. I toggled bootloader unlock before I did it and then toggled it off after I flashed it. The option was still there and available so it most likely is just modem files. I have cell service as well and did run a few speed tests on sub6 5G which is sort of a joke bc LTE is faster. We'll see what happens next month.
[Google Pixel 6 Pro] dipole:
Just flashed the global on my unlocked but on verizon p6pro...

everything went ok, hope they figure it out for next month
[Google Pixel 6 Pro] buschris:
.036
[Google Pixel 6 Pro] buschris:
you're right. I tested in a known fast 5G area today. 4G is the same speed as 5G lol
[Google Pixel 6 Pro] nozz93:
I got the update today (Pixel 6 Pro from the Google store in Germany with an o2 SIM). The build number is SD1A.210817.036.
[Google Pixel 6 Pro] snovvman:
Thanks for reporting. Based on many others' observations, it's strange that the unlocked P6Ps were not getting OTA if a VZ SIM was in the phone, but immediately gets the OTA if another carrier's SIM was inserted. Now, your unlocked phone with VZ SIM would get the .36 rather than A8 after all this time.
[Google Pixel 6 Pro] snovvman:
How old is your SIM? Sometimes older SIMs could limit connectivity. You did not get any cellular connection at all with A8?
[Google Pixel 6 Pro] snovvman:
Regarding unlocked phones using Verizon SIMs, there are many questions about what the correct firmware version, at least what the automatic OTA push is for an unlocked phone with a Verizon SIM in it. The important question is what the Verizon-specific firmware, A8, intended for? Is it meant for the Verizon locked version or any P6/P using a VZ SIM? I know Google does this each time it releases a new phone, it would be nice to get clarity on the issue.
[Google Pixel 6 Pro] V0latyle:
For unlocked devices, just use the vanilla build. Don't use the Verizon firmware.

For VZW locked phones, only the VZW update will install via ota sideload; others will fail.

Kinda makes you wonder what the point of the VZW factory images is.
[Google Pixel 6 Pro] jrg67:
Has anyone else on VZW with an unlocked G Store purchased NON Verizon variant P6 gotten the OTA?

@buschris, dumb question but can you confirm you indeed have a non vzw variant P6 with a vzw SIM inserted and you were able to pull the OTA and not side load it?
[Google Pixel 6 Pro] jrg67:
Any reason why you're saying to not use the Verizon specific firmware? Again, I flashed it on my P6P non vzw variant and I seem to be fine unless I'm missing under the hood that I'm not aware of. Can you shed some light?
[Google Pixel 6 Pro] V0latyle:
If you happen to relock the bootloader, you may not be able to unlock it again. The ability to toggle OEM Unlocking and therefore unlock the bootloader is baked into the ROM, and I would assume that VZW builds have ro.oem_unlock_supported set to 0.

Further, I would imagine that the VZW firmware may restrict some features on the device that would otherwise function, as the unlocked version is intended to be a global market device.
[Google Pixel 6 Pro] reaper000:
I'm on plain 036.

Unlocked P6P from Google store using a Verizon SIM (but I'm also prepaid, not regular)
[Google Pixel 6 Pro] jrg67:
The bootloader on mine is currently locked but I still have the ability to toggle the switch on and off. I've got to think there's more to the bootloader locked vzw variant bc if it was that easy to know the setting and possibly edit it within a rom, the vzw variants would all be hackable. So far, nobody has been successful in unlocking the bootloader of a vzw variant. Not sure if I can flash the global version of .036 over the .A8 version I have but as it stands right now, I still have the toggle enabled in dev options.

Edit - the toggle for bootloader unlock was there and off, I turned it on and took the screenshot so I can confirm it's functional.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I disagree with that part - being able to toggle (or not be able to toggle) OEM unlocking being baked into the ROM. You might have way more experience with this aspect than I do since I left Verizon half a year after getting my Pixel 1 and never looked back, but it's always been my impression that the ability to unlock is tied to the hardware some other way.

I won't be responsible if someone tests this theory and comes up with the short end, however. :D

This, I easily believe, or at least wouldn't be surprised.
[Google Pixel 6 Pro] Cares:
For those using USNF v2.2 are you using it with the latest Canary build?
[Google Pixel 6 Pro] ridobe:
Sim is ~2 months old so it's not that. I was pretty surprised. But, I'm on the global version now and all's well. I'll be sticking with it from now on.
[Google Pixel 6 Pro] V0latyle:
Locking/Unlocking Bootloader - Android Source

There are only 3 ways this property could be changed:

1. At ROM build time

2. Via recovery

3. Kernel root access

The last 2 would require an unlocked bootloader.

Even extremely low level methods such as JTAG most likely wouldn't work due to Android Verified Boot protecting data integrity; if you were to change the binary code on a physical storage device (chip) you would also have to change the cryptographic signature it's verified against.

USNF 2.2.0 was written to use Zygisk, so Magisk 23010 or newer is required.
[Google Pixel 6 Pro] MArtyChubbs:
I've been using a unlocked Google store phone on the Verizon network since the Pixel 1. Using carrier specific factory image will not lock your bootloader. The specific build optimizes the modem for the specific carriers network.
[Google Pixel 6 Pro] jrg67:
Just for the hell of it, I just tried to flash the regular global .036 over the vzw .036.A8 version and it failed citing the image was older than what I currently have now and downgrade isn't an option. Oh well, like I said, the toggle is still there and working for me. We'll see what Google does next month. I am still feeling these are mostly modem optimizations built in to the image for the specific carrier mentioned. If you look at previous builds for all the other phones, there are several that are carrier specific, especially when a new OS is released. Then eventually, as someone else mentioned, they merge them all together after a few months. Probably settings and coding that needs to be worked out to have the images compatible with all carriers. 🤷
[Google Pixel 6 Pro] V0latyle:
Why wouldn't you just flash radio, then?

What I would like to know, is why Verizon apps always automatically install when your phone is activated on Verizon. I literally only use Verizon for the service; I don't use their visual voicemail (Google Voice instead), I don't use their messages (Hangouts) and I don't use their cloud storage (Google Drive).
[Google Pixel 6 Pro] snovvman:
I just did this with success. I was on A8, rooted, and was able to factory flash back to .36 with no issues, along with re-rooting without wiping. Were you trying to OTA?
[Google Pixel 6 Pro] MArtyChubbs:
Why would you just flash the radio? Assuming you're updating the build, right?

Verizon wants to ensure their subscribers can find the apps on their phone without having to go and download them separately. I'm sure they'd like to keep users in their ecosystems where they can subscribe to their services and make money. It's not too much of an inconvenience to delete them, is it? Unless you wipe the phone every time then I can understand your frustration.
[Google Pixel 6 Pro] jrg67:
I tried with the OTA as I am not rooted and bootloader is still locked (toggle was on but I didn't run the adb command bc I don't want to wipe my phone). I just did the normal adb sideload OTA.zip. it's ok, I'm sure it's fine and like I said, we'll see what happens for December. If I get the global OTA or if I end up now on the Verizon track.
[Google Pixel 6 Pro] Frankie1588:
I'm interested in side loading the OTA for my unlocked P6P on Verizon, but confused which to get. I saw some mention regular and global. Where is that distinction made? Do I get the A8 Verizon one from this link?

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Google Pixel 6 Pro] Yensid eno:
Did you ever get the update? I have not and have same build as you. Thanks
[Google Pixel 6 Pro] Yensid eno:
Still no update on unlocked p6p on Vz network. Sim card is older, I think at least year and a half or more. I had location issue that seems better but which Google said I should consider updating to new sim card. Guess I need to get one.
[Google Pixel 6 Pro] volantis:
I have the P6 unlocked and using the Verizon eSim. No update so far.
[Google Pixel 6 Pro] bobby janow:
Any update on OTA? I got my P6 yesterday and still on October patch but having FP reader problems. On the VZW web page it only shows the October update: https://www.verizon.com/support/google-pixel-6-update/ So I'm wondering if anyone got ti from VZW yet? I'm tempted to adb install it but I've not done that is a couple of years. I've done it and it's easy enough but does that preclude you from getting an OTA in the future? And has anyone here done it that way?
[Google Pixel 6 Pro] Morgrain:
I received my OTA a day ago.

For forced "safe" OTA updates you can - by the way - use Googles own tools

->https://pixelrepair.withgoogle.com/carrier_selection

or

->https://flash.android.com/welcome

Once the OTA is up, those tools should be able to help you.
[Google Pixel 6 Pro] bobby janow:
So just to clarify you received the November update 036.A8 as an OTA? If so, then I can wait.
[Google Pixel 6 Pro] Morgrain:
Yup, my phone just prompted me randomly yesterday after about 2 hours into the new day with "System Update available, plx restart ty cucu <3" - after having smashed that update button manually for the better part of 6 days...
[Google Pixel 6 Pro] nxt:
I got the update a day later and replied, it's the 2nd post after my original.
[Google Pixel 6 Pro] Yensid eno:
Sorry, I got lost in different posts and missed your update. Thanks for responding.
[Google Pixel 6 Pro] stevek216:
I'm still waiting, unlocked pixel 6 pro with Verizon sim. Might just have to flash it...
[Google Pixel 6 Pro] Frankie1588:
Still waiting as well. Pixel 6 Pro unlocked with Verizon eSIM. Ill likely give it one more week before I flash the OTA. Do I grab the A8 OTA from here?

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yes, specifically here on that page.
[Google Pixel 6 Pro] Frankie1588:
Thank you!
[Google Pixel 6 Pro] Frankie1588:
Decided to sideload the OTA. Got sick of waiting. Thanks everyone for their help on this matter!

EDIT: Sideload finished without issue. Now on latest build.
[Google Pixel 6 Pro] znel52:
I got impatient and just did the sideload OTA to 36.A8. all went well. Now if my galaxy watch 4 classic could get the big DUJA update already that would be great.
[Google Pixel 6 Pro] Justin933:
I am using an unlocked Pixel 6 and still running SD1A.210817.019.C2 even though I have manually checked for update. Ting SIM card. Going to manually sideload it I suppose.
[Google Pixel 6 Pro] Alekos:
Which ota are you guys using for non-vzw models that are on the vzw network? Anyone know what the difference is exactly? I assume it has some carrier-related apps. I also assumed the vzw ota's were specifically for vzw models but I guess not.
[Google Pixel 6 Pro] Justin933:
I'm on Ting (verizon towers) on an unlocked p6 - I just manually upgraded to the .036 firmware. Everything is working fine, but not sure what the difference would be.
[Google Pixel 6 Pro] Alekos:
0.36 or 0.36.A8 (vzw version)?
[Google Pixel 6 Pro] Justin933:
just .036
[Google Pixel 6 Pro] Frankie1588:
I got A8 as a Verizon customer.
[Google Pixel 6 Pro] Alekos:
I wonder if this will help with monthly auto updates for unlocked vzw customers. It's insane how big this issue is. Most unlocked phones on vzw can't auto update? This is so bad.
[Google Pixel 6 Pro] pntballer505:
So it has been years time since I've played with adb and side loading.

I was curious to what I'm doing wrong here. I followed all the steps.

-I am able to boot into recovery from the adb command line.

-I check adb devices and it says sideload next to it.

But when I try to sideload the ota zip file, it just says "cannot read 'oriole-ota-sd1a.210817.036.a8-41f0de82.zip' "

Won't let me sideload the zip. Am I doing something dumb here lol?
[Google Pixel 6 Pro] Yensid eno:
I have had my p6p 256 unlocked on VZ network for almost 2 weeks. Still no update and I have installed a new sim card, restored to factory, and basically done all I can to get update to load with no luck. I don't want to load it manually as this could be a forever problem and it should do it itself. Sigh...
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hi. You'll likely have to give more details.

Using the newest Platform Tools from Google?

Using the newest drivers from Google?

Give an example of a command you've tried (the whole command line) including the location for where you tell it to sideload the file from.