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

[mosio]

Still waiting on this update (spamming check for update since yesterday), I haven't used ADB in years and don't want to accidentally brick my daily driver phone.

If you`re not in US or Canada, then you`ll wait till December.

 

[eijnaix]

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

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

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]

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

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

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:

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

 

[Tool Belt]

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

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

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]

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.

 

[eijnaix]

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:
View attachment 5462357

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

it matches. thanks.

 

[HtcDesire2]

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

 

[phupton]

Did you press power button and up volume to get to the on phone menu? From there you need to select load ADB

 

[neptun2]

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]

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:

"No Command" shown in Recovery mode

I'm on fully stock (international version) and when I head to recovery mode i have a sleeping droid bot and "No Command" shown. I can do nothing here...what am i missing?

forum.xda-developers.com

 

[XNine]

Seeing all the help here, being clear and concise... I LOVE THIS COMMUNITY!

 

[Stupifier]

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.

 

[buschris]

updated... nothing changed.

 

[buschris]

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

 

[Stupifier]

Flash the non verizon one

Flash the non-Verizon one ON TOP of the Verizon one I already flashed???

That won't cause problem?

 

[Uchman365]

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]

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]

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]

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.

 

[evnStevn]

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

I haven't heard this word b-4 , but I like niggles! Lol