• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

General New report of actual Verizon OTA SD1A.210817.037.A1 on Pixel 6/Pro

Search This thread

snovvman

Senior Member
Jun 6, 2008
1,530
511
For those who are using the unlocked P6P (not the VZ version) AND are on the Verizon network, please share the version that OTA updated you to.

Google released the image for P6P and P6, as well as OTA for sideloading. Each have separate versions for Verizon. This has happened in past devics. I would like to know which flash to use for an unlocked devices on the Verizon network--the generic version of the flash or the VZ-specific version?

Thanks.
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Recognized Contributor
For those who are using the unlocked P6P (not the VZ version) AND are on the Verizon network, please share the version that OTA updated you to.

Google released the image for P6P and P6, as well as OTA for sideloading. Each have separate versions for Verizon. This has happened in past devics. I would like to know which flash to use for an unlocked devices on the Verizon network--the generic version of the flash or the VZ-specific version?

Thanks.
https://forum.xda-developers.com/t/...rate-fingerprint-reader.4352027/post-85848409
 
  • Like
Reactions: kkjb

MasterBelch

Senior Member
Oct 22, 2020
66
65
Anyone still not get the update? I have the unlocked version from Google on Verizon.

I got impatient and had a dummy T-Mobile sim laying around so I powered off and switched out my Verizon sim. An update immediately pulled. It took about an hour and 20 mins or so downloading, installing, and optimizing apps. Powered off when done and switched back the Verizon sim. My updated build number is SD1A.210817.036.

From what I've read SD1A.210817.036 is the build number for every Google phone minus Verizon customers. Theirs would be SD1A.210817.036.A8. I'm assuming the latter build number is strictly for Verizon variant, bootloader locked customers.

Anyway, things seem to be fine and I haven't noticed any issues. Fingerprint sensor worked 99% of the time before and works the same now... along with everything else.
 

TonikJDK

Senior Member
Dec 9, 2012
2,695
1,373
Google Pixel 6 Pro
I'm assuming the latter build number is strictly for Verizon variant, bootloader locked customers

In the past it was for different network or modem updates specifically for VZ and were used for any phone using VZ. It it pretty common. In a month or two they will all merge together. I doubt you will see any noticable difference.
 
Last edited:
  • Like
Reactions: MasterBelch

hennooo

New member
Oct 29, 2021
3
3
Google Pixel 6 Pro
I got impatient and had a dummy T-Mobile sim laying around so I powered off and switched out my Verizon sim. An update immediately pulled. It took about an hour and 20 mins or so downloading, installing, and optimizing apps. Powered off when done and switched back the Verizon sim. My updated build number is SD1A.210817.036.

From what I've read SD1A.210817.036 is the build number for every Google phone minus Verizon customers. Theirs would be SD1A.210817.036.A8. I'm assuming the latter build number is strictly for Verizon variant, bootloader locked customers.

Anyway, things seem to be fine and I haven't noticed any issues. Fingerprint sensor worked 99% of the time before and works the same now... along with everything else.
I found an old expired sim from Singapore. Update immediately started. When I changed back to my German sim while the update was preparing, it disappeared again. Update completed with the Singapore sim. I don't know if the update offers any improvements for me though.
 
  • Like
Reactions: MasterBelch

Polishow

Member
Apr 3, 2014
36
10
World
OnePlus 3
OnePlus 9 Pro
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?
 
Last edited:

mang0

Senior Member
Jan 12, 2012
569
194
San Diego
OnePlus 6T
Google Pixel 6
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?
Are you able to take the OTA with a fresh start / no restoring data and apps?
 

Podster16

Member
Mar 31, 2017
15
19
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
 

Morgrain

Senior Member
Aug 4, 2015
564
474
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
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.
 
Last edited:

Morgrain

Senior Member
Aug 4, 2015
564
474
Anyone still not get the update? I have the unlocked version from Google on Verizon.
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.
 
  • Like
Reactions: roirraW "edor" ehT

Podster16

Member
Mar 31, 2017
15
19
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/

--

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.
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
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Sure.

    -I am using the latest platform tools available.
    -I think I'm using the newest drivers. Not quite sure. I uninstalled and reinstalled drivers
    in device manager.

    -I placed the Oriole(I realize that is not for the Pro, I am on the regular 6)zip ota file in the platform tools directory.
    -Debugging enabled.
    -First command "adb reboot recovery"
    -Power and volume up, then scroll down to "Apply update from adb"
    -Ran "adb devices" to make sure it said sideload next to device name.
    -Finallay "adb sideload oriole-ota-sd1a.210817.036.a8-41f0de82.zip"

    Not sure if I'm doing something wrong with the file name or directory, but everything else seemed to be in order.
    • The latest drivers are available here. Make sure and install/update them if necessary when you're in sideload mode.
    • You have oriole-ota-sd1a.210817.036.a8-41f0de82.zip in the same folder as adb?
    • You could try moving the folder that has Platform Tools and the zip file closer to the root of your file system, such as in C:\T\, to avoid having been in too long a filepath.
    • Check the SHA-256 hash of your zip file compared to what's shown on Google's site? My Windows program of choice to check the hash of a single file is HashTab. If you install it, then right-click the OTA zip file, choose Properties, then click the HashTab tab, choose Settings to enable SHA-256, then you can paste in the SHA-256 hash that Google shows for the OTA you downloaded, and it'll tell you if that pasted hash matches the actual files' hash.
    • You could try the non-Verizon variant of the OTA "oriole-ota-sd1a.210817.036-fac7e678.zip" with SHA-256 of fac7e67859e10838950af963d5e196e94ae3bf72317e505e71a87ea6160cca38.
    Total guesses here, though, not sure what else the problem could be.
    3
    Good advice.

    I've tried mostly everything, and the drivers and adb interface appear to be working how they should. I think this may be user error in that I am putting the wrong filename in the "adb sideload" command.

    in the terminal it shows: C:\WINDOWS\system32>adb sideload oriole-ota-sd1a.210817.036.a8-41f0de82.zip

    "* cannot read 'oriole-ota-sd1a.210817.036.a8-41f0de82.zip' *"

    Is this wrong or am I missing something about the file I'm pasting or which directory I'm placing it in?!
    Do you have ADB and the OTA zip in the "C:\WINDOWS\system32\" folder? If not, do you have them in the same folder together? If so, "CD" (Change Directory) to the path where you have both ADB and the OTA zip. Like:

    Code:
    CD "C:\Users\Me\Downloads\Platform Tools\"
    adb sideload oriole-ota-sd1a.210817.036.a8-41f0de82.zip

    It is definitely the correct filename for one of the two SD1A.210817.036 OTAs - specifically the SD1A.210817.036.A8 (Verizon) one. Whether you should be flashing the SD1A.210817.036.A8 OTA or the regular SD1A.210817.036, we have no way of telling without more information, like @znel52's question about if you're on Verizon (and which model P6P you're using on Verizon if so - Unlocked or Verizon edition).

    There's still a chance that the zip file is just corrupt. Checking the hash to see if it matches what's on Google's site would tell you. If it's not a match, the file you have is corrupt and you should re-download it and re-check the hash. I check hashes on all important files that I flash to my phone, when the hash is available.
    2
    If you are on the Pro you need 'Raven' not 'Oriole'. Looks like you downloaded the wrong OTA file.
    Totally missed that. Good catch!

    But when I try to sideload the ota zip file, it just says "cannot read 'oriole-ota-sd1a.210817.036.a8-41f0de82.zip' "
    2
    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.
    2
    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?
    If you are on the Pro you need 'Raven' not 'Oriole'. Looks like you downloaded the wrong OTA file.
  • 4
    @pntballer505 reports getting the .037.A1 OTA on Verizon at post #138.

    Old Verizon OTAs:
    Several reports of the actual Verizon .036.A1 OTA, starting with @stevek216 at post #126.

    https://support.google.com/pixelpho...t-software-to-get-all-the-features?hl=en&s=09

    Checking for the software update
    [Please check your device to see if you already have the latest software installed. Verify your Build number matches the official build by checking Settings -> About phone -> Build number. See section below]

    After you complete the phone setup, the software update automatically downloads silently in the background. After the download completes, it will prompt you to reboot the phone. In case the software update is not seen, follow the instructions below:
    Go to Settings -> System -> System update -> Check for update
    Install the software update
    Depending on your network connection speed and amount of apps involved, this will take about 25-50 minutes
    Reboot the device after taking the update

    Updating your apps
    Many of the key apps have new features and improvements for Pixel 6. Please check to make sure that your apps are up to date by going to Play Store -> Your Account Icon -> Manage apps & device -> Update all.

    Timing
    Due to deployment timelines and staged rollouts, some updates may not be available until 10/28.

    Software update Build number
    After the software update, your device software version (Settings -> About phone -> Build number) will be be one of the following:
    SD1A.210817.036
    SD1A.210817.036.A8 (Verizon customers)
    4
    Same, nothing to update to.
    It will come if they build it. I setup and popped the sim in. Be patient. It takes an hour to download. Damn. It's still updating. Best phone I ever had. I don't understand these complainers
    3
    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
    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.
    3
    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.
    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. 🤷
    3
    and this update does what? You guessed it. Absolutely NOTHING
    You are correct, Google just likes to release firmware updates that do nothing.
    /s