General Pixel 6 and 6 Pro get out-of-cycle November update to improve the fingerprint sensor

Search This thread

eijnaix

Senior Member
Mar 25, 2013
104
13
Google Pixel 6 Pro
certutil -hashfile raven-ota-sd1a.210817.037-1543ec70.zip MD5
MD5 hash of raven-ota-sd1a.210817.037-1543ec70.zip:
ccdda1ddb265e0e0e2252f7976dea919
CertUtil: -hashfile command completed successfully.

Is this the correct file for US set pixel 6 pro unlocked ?

I dont understand the part about the checksum from this part

developers.google.com

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


developers.google.com
developers.google.com

  1. Verify the checksum of the image: the OTA mechanism has a built-in validation feature, but verifying will save you some time if the file is incomplete. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is also shown next to the download link.
 

mosio

Senior Member
Jan 22, 2009
324
64
certutil -hashfile raven-ota-sd1a.210817.037-1543ec70.zip MD5
MD5 hash of raven-ota-sd1a.210817.037-1543ec70.zip:
ccdda1ddb265e0e0e2252f7976dea919
CertUtil: -hashfile command completed successfully.

Is this the correct file for US set pixel 6 pro unlocked ?

I dont understand the part about the checksum from this part

developers.google.com

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


developers.google.com
developers.google.com

  1. Verify the checksum of the image: the OTA mechanism has a built-in validation feature, but verifying will save you some time if the file is incomplete. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is also shown next to the download link.
You need to run SHA256 checksum instead of MD5, so go with:
certutil -hashfile raven-ota-sd1a.210817.037-1543ec70.zip SHA256
Then you should match this one:
1637255677775.png


It`s a safety measure to confirm that the file correctly saved on your local drive.
 

Tool Belt

Senior Member
Feb 5, 2011
843
310
Google Pixel 6
certutil -hashfile raven-ota-sd1a.210817.037-1543ec70.zip MD5
MD5 hash of raven-ota-sd1a.210817.037-1543ec70.zip:
ccdda1ddb265e0e0e2252f7976dea919
CertUtil: -hashfile command completed successfully.

Is this the correct file for US set pixel 6 pro unlocked ?

I dont understand the part about the checksum from this part

developers.google.com

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


developers.google.com
developers.google.com

  1. Verify the checksum of the image: the OTA mechanism has a built-in validation feature, but verifying will save you some time if the file is incomplete. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is also shown next to the download link.


That appears to be the correct file for a non VerizonP6 Pro. It looks like you ran an MD5 hash. The SHA-256 hash is different and the one shown on the web site. As the instructions say running the SHA-256hash yourself is not critical as the " OTA mechanism has a built-in validation". It will, however save you some heartache if the file you downloaded is not complete and/ot is corrupted.
 

eijnaix

Senior Member
Mar 25, 2013
104
13
Google Pixel 6 Pro
That appears to be the correct file for a non VerizonP6 Pro. It looks like you ran an MD5 hash. The SHA-256 hash is different and the one shown on the web site. As the instructions say running the SHA-256hash yourself is not critical as the " OTA mechanism has a built-in validation". It will, however save you some heartache if the file you downloaded is not complete and/ot is corrupted.
thanks for the prompt reply.

I've downloaded the file 3 time.... it always the same file size.
 

HtcDesire2

Senior Member
Sep 2, 2010
357
135
Wellington
Xiaomi Mi A1
Google Pixel 6
After rebooting my pixel 6 to recovery "adb devices" is not able to find the devices.

What could be the problem?

I tried 3 different cable, Ubuntu/Windows 10/11 but none are able to identify device in recovery :(
 

Attachments

  • 2021-11-19 09_42_32-VDI - VDX3614 - Desktop Viewer.png
    2021-11-19 09_42_32-VDI - VDX3614 - Desktop Viewer.png
    30.3 KB · Views: 40

neptun2

Senior Member
Jul 25, 2009
424
184
I updated via adb and frankly don't see serious improvement at least with my unknown brand screen protector. I rescanned my fingerprint after update. Tomorrow i expect better protector and will see how it goes with it.
 

HtcDesire2

Senior Member
Sep 2, 2010
357
135
Wellington
Xiaomi Mi A1
Google Pixel 6
Did you press power button and up volume to get to the on phone menu? From there you need to select load ADB

Damn, this is something new for me.I was in "Recovery NO Command" mode and then pressed the power button and a single tap on volume up allowed me to go to recovery.

Reference Thread:

 

Stupifier

Senior Member
Jun 8, 2010
1,913
680
If I have an unlocked Pixel 6 but am on Verizon.....which OTA would I use?
SD1A.210817.037
OR
SD1A.210817.037.A1, verizon

Update: I tried the SD1A.210817.037.A1, verizon one and it seems to be fine.....no issues with WiFi or Verizon Signal at least...rebooted fine. Dunno if it was the right one or not, just reporting what happened.
 
Last edited:

buschris

Senior Member
Jan 20, 2011
538
121
OnePlus 7 Pro
If I have an unlocked Pixel 6 but am on Verizon.....which OTA would I use?
SD1A.210817.037
OR
SD1A.210817.037.A1, verizon

Update: I tried the SD1A.210817.037.A1, verizon one and it seems to be fine.....no issues with WiFi or Verizon Signal at least...rebooted fine. Dunno if it was the right one or not, just reporting what happened.
Flash the non verizon one
 

Uchman365

Member
Feb 2, 2020
6
0
Wow, this is more like it, much improved sensor response for me. I actually did not have any issues with FP thing until I reset to solve the excessive battery drain. Solved one issue to create another lol
 

phupton

Senior Member
Mar 13, 2006
90
18
UK
So my verdict on the update is that the FPR is improved but it's a long way off that of other phones. Android or iPhone.

The bright light is a bit of a paint too in darker places but that will never change as it's down to the tech being used.
 

bobby janow

Senior Member
Jun 15, 2010
6,324
2,333
So my verdict on the update is that the FPR is improved but it's a long way off that of other phones. Android or iPhone.

The bright light is a bit of a paint too in darker places but that will never change as it's down to the tech being used.
Agree, it's not perfect but at least it's not frustrating every unlock. I can't speak to other phones, some are saying it's better and some slightly worse, but it certainly shows that it can be improved with an update. I suspect FPR and battery life will get better with each of them. Only a limited rollout mid November perhaps testing for the December update.
 

phupton

Senior Member
Mar 13, 2006
90
18
UK
Here's another change I've noticed since updating.

Previously, I never ever saw my carrier details or the WiFi calling option displayed at the top of the phone.

Now, when I pick up the phone, just before unlocking I see my carrier details and WiFi calling scrolling on the top left of the screen.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Hmmm, looks like I got wrong link. How best can I back out to get phone working again? Its stuck on the Google boot screen.
    Proper OTA sideload should bring you up, this time use the Pixel 6 OTA. As per OTA page (https://developers.google.com/android/ota):

    "This page contains full OTA update packages that allow you to restore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader."

    So:
    1. Boot to bootloader: hold pwr button + vol dwn button
    2. Boot to recovery: in bootloader select Recovery and press pwr button and plug in your cable
    and then according to OTA instructions:
    3. To access the recovery menu, hold the Power button and press Volume Up once. The recovery text menu will appear.
    4. To enter sideload mode, select the option Apply update from ADB.
    5. Run the following command:

    adb devices
    and check that your device shows up with "sideload" next to its name.

    6. Run the following command:

    adb sideload ota_file.zip
    where ota_file.zip is the name of the file you have downloaded and verified.

    7. Once the update finishes, reboot the phone by choosing Reboot system now.
    3
    adb sideload raven-ota-sd1a.210817.037-1543ec70.zip

    My phone is a Pixel 6.

    It aborted, on the phone too....
    Shouldn't it be "Oriole" for the Pixel 6?
    3
    Im back online with the updated build number. You all are life savers. Thanks for your patience and help.
    You're welcome. We tripled teamed you lol. @Tool Belt @mosio Good job. Now enjoy your functioning FPR. Let us know if it's working as well for you as it is for most of us.
    3
    No news is good news? He's probably updating now and hopefully successfully.
    edit: lol ninja'd
    I think we got him back on the correct path.
    2
    Wondering now with this revelation that most seem to be seeing improvements if I should re-consider keeping hold of the handset. I'm wondering if Google will be able to iron out the majority of niggles through updates in the near future 🤔

    No promises but this all feels like any other new Pixel rollout. New hardware with a new OS has always created these kinds of issues. They always seem to iron out most of them by the first of the year.