• 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

roirraW "edor" ehT

Recognized Contributor
@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)
 
Last edited:

nxt

Senior Member
Mine is updating now, 64.35 MB, I'll update with before and after build numbers when it finishes.

EDIT: Almost an hour later and it's still optimizing apps, around 50%. Took about an hour and a half and a reboot, finally updated.

Unlocked model from Google Store USA.
Before:
Build Number: SD1A.210817.019.C2
Android security update: Oct 5
Baseband: g5123b-91479-210916-B-7738070

After:
Build Number: SD1A.210817.036
Android security update: Nov 5
Baseband: g5123b-92009-211008-B-7805583
 
Last edited:

Indashio

Senior Member
Oct 24, 2014
513
231
Mine is updating now, 64.35 MB, I'll update with before and after build numbers when it finishes.

EDIT: Almost an hour later and it's still optimizing apps, around 50%. Took about an hour and a half and a reboot, finally updated.

Unlocked model from Google Store USA.
Before:
Build Number: SD1A.210817.019.C2
Android security update: Oct 5
Baseband: g5123b-91479-210916-B-7738070

After:
Build Number: SD1A.210817.036
Android security update: Nov 5
Baseband: g5123b-92009-211008-B-7805583
 
Last edited:

Morgrain

Senior Member
Aug 4, 2015
585
489
My P6 Pro still can't find the update :(

Supposedly the update should fix my fingerprint reading issues, so I'm sorta stoked to see that one comin' rather sooner than late.

Any way to force it? Stil no factory images/OTA, so I'm out of options.
 

Samitro1

Member
Nov 11, 2014
8
5
My P6 Pro still can't find the update :(

Supposedly the update should fix my fingerprint reading issues, so I'm sorta stoked to see that one comin' rather sooner than late.

Any way to force it? Stil no factory images/OTA, so I'm out of options.
Does it really fix fingerprint issues? do we have the changelog?
 

Morgrain

Senior Member
Aug 4, 2015
585
489
No changelog yet that I am aware of, only reports of people claiming that after the update you have to re-learn the fingerprint scanner and then it supposedly works better.
 
  • Like
Reactions: roirraW "edor" ehT

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
    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?!
    Looks like you need to navigate to your ADB folder in terminal. It appears you are not running the commands from within the folder if I am reading your post right.

    for instance when I pull up terminal it says C:\Windows\blah blah

    My ADB folder is on the root of the C: drive so in command prompt I do 'cd/adb' which changes to my adb directory.

    Command prompt then shows 'C:\ADB' which is where I need to be.

    I'm sure I'm not explaining this well but you need to navigate to your ADB directory in command prompt before running the adb sideload command.

    Or if you navigate to where your ADB folder is on your hard drive in explorer and Hold Shift + right click on the folder you should have an option to open a command prompt window from that location. Then you can just run your commands as you should be in the right spot.
    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.
    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' "
  • 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