How To Guide September 12, 2022 Verizon factory image (TP1A.220905.004.A1) - PSA about Android 13 in OP - Unlocking the Pixel 6 Pro bootloader & central repository

Search This thread

roirraW "edor" ehT

Forum Moderator
Staff member
Thanks, so with OTA even bootloader is flashed to both slots, right?
You're welcome!

Actual Over The Air update you receive and install automatically, or sideloading?

Actual Over The Air automatic update definitely flashes to both slots. The nature of how two slots works is the OTA updates the slot you're not using first, then when you reboot you're booting into the newly updated slot, and then the OTA applies to the slow you're no longer using.

I don't sideload so I have no idea if there's any difference in behavior. Plus some people haven't had success with sideloading the OTA and have to use another method (either full factory image and/or the Official Google Android Flash Tool.
 

V0latyle

Forum Moderator
Staff member
Thanks, so with OTA even bootloader is flashed to both slots, right?
No. OTA is an "out of band" update - it's installed to the inactive slot, regardless of whether you use the automatic system OTA, or you sideload the update package.

The only way to ensure bootloader is flashed to both slots is to do it manually.
 

V0latyle

Forum Moderator
Staff member
Actual Over The Air automatic update definitely flashes to both slots. The nature of how two slots works is the OTA updates the slot you're not using first, then when you reboot you're booting into the newly updated slot, and then the OTA applies to the slow you're no longer using.
Not sure this is the case...I don't believe the system does anything to the "old" slot until the next OTA.
 

roirraW "edor" ehT

Forum Moderator
Staff member
Not sure this is the case...I don't believe the system does anything to the "old" slot until the next OTA.
It was definitely the case with the Pixel 1 with the first a/b system. It did this so if for example, you're running slot A before the OTA, the OTA updates slot B while you're running slot A, then you reboot, it boots automatically into slot B, then it updates slot A while you're running slot B. This way, if slot B fails for some reason, it'll boot into slot A (which is already updated) with no issues...hopefully.
 
  • Like
Reactions: Lughnasadh

V0latyle

Forum Moderator
Staff member
It was definitely the case with the Pixel 1 with the first a/b system. It did this so if for example, you're running slot A before the OTA, the OTA updates slot B while you're running slot A, then you reboot, it boots automatically into slot B, then it updates slot A while you're running slot B. This way, if slot B fails for some reason, it'll boot into slot A (which is already updated) with no issues...hopefully.
I mean, I've been wrong before. The Android documents don't mention this but it makes sense to me.
 
  • Like
Reactions: roirraW "edor" ehT

Lughnasadh

Senior Member
Mar 23, 2015
3,905
4,179
Google Nexus 5
Huawei Nexus 6P
Not sure this is the case...I don't believe the system does anything to the "old" slot until the next OTA.
This is the case. The current slot is unaffected in case there is an error in updating the inactive slot or the inactive slot fails to boot. In such cases, the device will revert to the unaffected current slot. Only on the next OTA will the former current slot be updated.
 
  • Like
Reactions: roirraW "edor" ehT

Lughnasadh

Senior Member
Mar 23, 2015
3,905
4,179
Google Nexus 5
Huawei Nexus 6P
It was definitely the case with the Pixel 1 with the first a/b system. It did this so if for example, you're running slot A before the OTA, the OTA updates slot B while you're running slot A, then you reboot, it boots automatically into slot B, then it updates slot A while you're running slot B. This way, if slot B fails for some reason, it'll boot into slot A (which is already updated) with no issues...hopefully.
Interesting. I've never heard of that. Always thought the current slot was unaffected until the next OTA update.
 
  • Like
Reactions: roirraW "edor" ehT

V0latyle

Forum Moderator
Staff member
This is the case. The current slot is unaffected in case there is an error in updating the inactive slot or the inactive slot fails to boot. In such cases, the device will revert to the unaffected current slot. Only on the next OTA will the former current slot be updated.
Easy way to test this...Someone who updated via OTA can boot into bootloader and use fastboot set_active other to switch to the other slot. However - I do not recommend doing this on the Android 13 update until the next OTA.
 
  • Like
Reactions: roirraW "edor" ehT

Lughnasadh

Senior Member
Mar 23, 2015
3,905
4,179
Google Nexus 5
Huawei Nexus 6P
"...no partition used by the current slot should be updated as part of the OTA update (including partitions for which there is only one copy)."

I don't see anything in the documentation about updating the former current slot after the device has booted into the new slot. Maybe need to dig deeper...

Eh, I never use OTA's anyway 🙃

 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
Interesting. I've never heard of that. Always thought the current slot was unaffected until the next OTA update.
Who knows. I could be remembering wrong. I swear I thought that's what I read about it when I first got my Pixel, and I thought it made sense - once the initially updated Slot B boots successfully, Slot A gets updated to match. After all, I always thought Google wanted both slots to be on the same software as a backup to boot to just in case.
 
  • Like
Reactions: Lughnasadh

roirraW "edor" ehT

Forum Moderator
Staff member
Easy way to test this...Someone who updated via OTA can boot into bootloader and use fastboot set_active other to switch to the other slot. However - I do not recommend doing this on the Android 13 update until the next OTA.
Maybe I'll test it on my unlocked Pixel 1. First I'll flash the full firmware to both slots, then take the OTA and after all success, make comparisons between each slot's Software in Settings. Yeah, I think I'll do that. I don't mind fooling with the old phone.

Edit: Triple posting, self! Shame on me! :)
 

V0latyle

Forum Moderator
Staff member
Maybe I'll test it on my unlocked Pixel 1. First I'll flash the full firmware to both slots, then take the OTA and after all success, make comparisons between each slot's Software in Settings. Yeah, I think I'll do that. I don't mind fooling with the old phone.

Edit: Triple posting, self! Shame on me! :)
Yeah this would be a pretty safe idea. I still have my old Pixel 2 that I can try this on as well.
 
  • Like
Reactions: roirraW "edor" ehT

exocetdj

Senior Member
Dec 2, 2011
6,896
4,420
Jah's making me crazy
rooted on 12l stock - the method i used to update to a13 was

1 - completely nuke magisk via the app
2 - the device initiated a reboot so as soon as the screen went black i held power and down for fastboot mode - i then connected the device to PC
3 - in "flash-all.bat" i changed "fastboot -w update image###.zip" to "fastboot update --skip-reboot image###.zip"
4 - closed "flash-all.bat" and then i launched it - when finished i was in fastbootd mode - i then rebooted device to fastboot mode
5 - in CMD i typed and enter "fastboot set_active other" and then relaunched "flash-all.bat" - WIN!! as i was booted with all my data previously on A12 intact
6 - i then installed stable magisk 25.2 and patched boot image from A13 and then rebooted to fastboot mode
7 - i then opened CMD once more and typed and entered "fastboot boot magisk-patched.boot.img" which booted the device rooted - finally i directly installed magisk via the app
 

Namelesswonder

Senior Member
Jan 26, 2014
270
400
Google Pixel XL
Google Pixel 6 Pro
Maybe I'll test it on my unlocked Pixel 1. First I'll flash the full firmware to both slots, then take the OTA and after all success, make comparisons between each slot's Software in Settings. Yeah, I think I'll do that. I don't mind fooling with the old phone.

Edit: Triple posting, self! Shame on me! :)
I don't remember it being that way back then, because I remember the pain when LineageOS 14 was testing update_engine on the Pixel and I had to take up to modifying both vendor slots to have persistent modifications as each nightly update would be swapping system slots. Worked for the time as files on /vendor would supersede those on /system. Would need to be redone every time the monthly update was flashed, but ultimately had to stop doing it as LineageOS started including the vendor partition in the update payload as users would get vendor-system mismatch warnings because the vendor partition could be stale as update_engine doesn't update both slots at once. Users moving from stock Android to LineageOS would have the other slot be stale unless they --slot all the factory image at the time. Easily solved by LineageOS just bundling in the vendor partition with the update payload.

I could test if this is still true, but I'm still using my Pixel XL and have LineageOS 18.1 set up just the way I like. I did test on a Pixel 5, and update_engine still only updates one slot at a time.

Code:
[[email protected]:/tmp/redfin-sq3a.220705.003.a1]$ fastboot --slot all flash bootloader bootloader-redfin-r3-0.4-8351081.img 1>/dev/null 2>&1
[[email protected]:/tmp/redfin-sq3a.220705.003.a1]$ fastboot --slot all flash radio radio-redfin-g7250-00202-220422-b-8489468.img 1>/dev/null 2>&1
[[email protected]:/tmp/redfin-sq3a.220705.003.a1]$ fastboot reboot bootloader
Rebooting into bootloader                          OKAY [  0.016s]
Finished. Total time: 0.066s
[[email protected]:/tmp/redfin-sq3a.220705.003.a1]$ fastboot getvar version-bootloader
version-bootloader: r3-0.4-8351081
Finished. Total time: 0.023s
[[email protected]:/tmp/redfin-sq3a.220705.003.a1]$ fastboot --slot all -w update image-redfin-sq3a.220705.003.a1.zip 1>/dev/null 2>&1
[[email protected]:/tmp/redfin-sq3a.220705.003.a1]$ fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.012s
[[email protected]:/tmp/redfin-sq3a.220705.003.a1]$ adb sideload ~/Downloads/redfin-ota-tp1a.220624.014-3301931b.zip 1>/dev/null 2>&1
[[email protected]:/tmp/redfin-sq3a.220705.003.a1]$ fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.012s
[[email protected]:/tmp/redfin-sq3a.220705.003.a1]$ fastboot getvar version-bootloader
version-bootloader: r3-0.5-8633620
Finished. Total time: 0.017s
[[email protected]:/tmp/redfin-sq3a.220705.003.a1]$ fastboot -aa
Setting current slot to 'a'                        OKAY [  0.314s]
Finished. Total time: 0.324s
[[email protected]:/tmp/redfin-sq3a.220705.003.a1]$ fastboot reboot bootloader
Rebooting into bootloader                          OKAY [  0.013s]
Finished. Total time: 0.063s
[[email protected]:/tmp/redfin-sq3a.220705.003.a1]$ fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.018s
[[email protected]:/tmp/redfin-sq3a.220705.003.a1]$ fastboot getvar version-bootloader
version-bootloader: r3-0.4-8351081
Finished. Total time: 0.016s

The Android 12 slot did become unbootable, but it's possible that the full OTA did that and the incremental OTA wouldn't.
 

roirraW "edor" ehT

Forum Moderator
Staff member
@V0latyle @Lughnasadh @Namelesswonder

Yep, I was wrong. Apparently, I misunderstood this six years ago and it just never came up again for me. LOL! I swear I thought I had read it, but it must be true, if I did read it, right? 😜

I was doing the testing and I was finding that after the OTA from the second to last update for the Pixel 1 to the last update available, and then after successfully using the updated slot, if I then changed slots and tried to boot into it, the phone would sit trying to boot for 10-15 minutes with the G in the middle with the moving line underneath it, then eventually fail to Android Recovery, where I could Try again (which I did once with no luck) or Factory Reset - which besides factory resetting, also took me to the already updated Slot, not the one I was most recently trying to get into.

I've got kind of a headache now from trying to keep the slots and information straight (that's what the documentation was for below), so I give up. LOL! I assume Slot A (QP1A.191005.007.A1) doesn't work with Slot B's (QP1A.191005.007.A3) data since I had already booted into Slot B, and which is half expected but I thought there would be a chance it would work with such a relatively minor change and tiny OTA.

When I started with flashing both slots with the second to last update as a starting point, I tried flashing both slots at the same time, but as I believe has already been said, didn't work back then anyway:
S:\platform-tools - Pixel 1 (non-XL - sailfish)>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully

S:\platform-tools - Pixel 1 (non-XL - sailfish)>flash-all
Sending 'bootloader_a' (32480 KB) OKAY [ 0.891s]
Writing 'bootloader_a' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.058s]
Sending 'bootloader_b' (32480 KB) OKAY [ 0.891s]
Writing 'bootloader_b' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 1.999s]
Finished. Total time: 6.253s
Rebooting into bootloader OKAY [ 0.008s]
Finished. Total time: 0.009s
< waiting for any device >
Sending 'radio_a' (57156 KB) OKAY [ 1.451s]
Writing 'radio_a' OKAY [ 3.601s]
Sending 'radio_b' (57156 KB) OKAY [ 1.451s]
Writing 'radio_b' OKAY [ 3.902s]
Finished. Total time: 10.846s
Rebooting into bootloader OKAY [ 0.026s]
Finished. Total time: 0.031s
< waiting for any device >
Warning: slot set to 'all'. Secondary slots will not be flashed.
--------------------------------------------
Bootloader Version...: 8996-012001-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: XXXXXXXXXXXXXXXXXXXXXXX
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.048s]
Checking 'version-bootloader' OKAY [ 0.049s]
Checking 'version-baseband' OKAY [ 0.048s]
Setting current slot to 'a' OKAY [ 0.219s]
extracting boot.img (30 MB) to disk... took 0.115s
archive does not contain 'boot.sig'
Sending 'boot_a' (30793 KB) OKAY [ 0.799s]
Writing 'boot_a' OKAY [ 2.350s]
archive does not contain 'boot.sig'
Sending 'boot_b' (30793 KB) OKAY [ 0.798s]
Writing 'boot_b' OKAY [ 2.403s]
archive does not contain 'init_boot.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
archive does not contain 'vbmeta.img'
archive does not contain 'vbmeta_system.img'
archive does not contain 'vbmeta_vendor.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'vendor_kernel_boot.img'
archive does not contain 'super_empty.img'
fastboot: error: Could not check if partition odm has slot all
Press any key to exit...

I then manually flashed each Slot to the second to the last update. One interesting aspect of this is this portion of both sets of flashes:

Flashing Slot A:
Code:
Sending sparse 'system_a' 1/4 (524284 KB)          OKAY [ 12.972s]
Writing 'system_a'                                 OKAY [ 30.911s]
Sending sparse 'system_a' 2/4 (524284 KB)          OKAY [ 12.910s]
Writing 'system_a'                                 OKAY [ 43.875s]
Sending sparse 'system_a' 3/4 (524284 KB)          OKAY [ 12.952s]
Writing 'system_a'                                 OKAY [ 54.928s]
Sending sparse 'system_a' 4/4 (461052 KB)          OKAY [ 11.393s]
Writing 'system_a'                                 OKAY [ 61.682s]
archive does not contain 'system_dlkm.img'
archive does not contain 'system_ext.img'
extracting system_other.img (291 MB) to disk... took 1.226s
archive does not contain 'system.sig'
Sending 'system_b' (298348 KB)                     OKAY [  7.401s]
Writing 'system_b'                                 OKAY [ 36.020s]

Flashing Slot B:
Code:
Sending sparse 'system_b' 1/4 (524284 KB)          OKAY [ 12.972s]
Writing 'system_b'                                 OKAY [  3.599s]
Sending sparse 'system_b' 2/4 (524284 KB)          OKAY [ 12.904s]
Writing 'system_b'                                 OKAY [  3.583s]
Sending sparse 'system_b' 3/4 (524284 KB)          OKAY [ 12.961s]
Writing 'system_b'                                 OKAY [  3.544s]
Sending sparse 'system_b' 4/4 (461052 KB)          OKAY [ 11.406s]
Writing 'system_b'                                 OKAY [  3.161s]
archive does not contain 'system_dlkm.img'
archive does not contain 'system_ext.img'
extracting system_other.img (291 MB) to disk... took 1.252s
archive does not contain 'system.sig'
Sending 'system_a' (298348 KB)                     OKAY [  7.411s]
Writing 'system_a'                                 OKAY [  2.058s]

I find it curious that at the end of flashing the sparse system image to the active slot, there's a very quick thing about flashing one "system" to the other slot. I haven't noticed if that happens on the P6P, but just curious what that's about.

Heh. My "Verizon" Pixel 1 which I unlocked the bootloader on when it was on Android 7.10 before that got re-disabled on Android 7.11 - the bootloader is definitely unlocked (adb reboot fastboot shows unlocked) but OEM Unlocking is in the disabled position and grayed out, even when connected to Wi-Fi.

I doubt-checked and made sure there isn't anything on this phone that I want I don't already have backed up.

I extracted the sailfish-qp1a.191005.007.a1-factory-78c6703e.zip (October 2020 update, second to the last for the Pixel 1) to the same folder of a fresh extract of Platform Tools v33.0.2.

I modified the flash-all.bat to include --skip-reboot at the end of the fastboot flash update line, so I can switch slots at the end and flash-all.bat again.

It was already on Slot A, so I flash-all, wow flashing is slow on the Pixel 1 - at least it seemed much slower, and I'm sure it was. Not bothering to add up the times in the output and compare, lol.

S:\platform-tools - Pixel 1 (non-XL - sailfish)>flash-all
Sending 'bootloader_a' (32480 KB) OKAY [ 0.890s]
Writing 'bootloader_a' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.048s]
Finished. Total time: 3.103s
Rebooting into bootloader OKAY [ 0.009s]
Finished. Total time: 0.010s
< waiting for any device >
Sending 'radio_a' (57156 KB) OKAY [ 1.450s]
Writing 'radio_a' OKAY [ 0.497s]
Finished. Total time: 2.136s
Rebooting into bootloader OKAY [ 0.008s]
Finished. Total time: 0.010s
< waiting for any device >
--------------------------------------------
Bootloader Version...: 8996-012001-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: XXXXXXXXXXXXXXXXXXXXXXX
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.048s]
Checking 'version-bootloader' OKAY [ 0.049s]
Checking 'version-baseband' OKAY [ 0.049s]
Setting current slot to 'a' OKAY [ 0.100s]
extracting boot.img (30 MB) to disk... took 0.125s
archive does not contain 'boot.sig'
Sending 'boot_a' (30793 KB) OKAY [ 0.789s]
Writing 'boot_a' OKAY [ 0.266s]
archive does not contain 'init_boot.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
archive does not contain 'vbmeta.img'
archive does not contain 'vbmeta_system.img'
archive does not contain 'vbmeta_vendor.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'vendor_kernel_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
archive does not contain 'product.img'
extracting system.img (1986 MB) to disk... took 7.303s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/4 (524284 KB) OKAY [ 12.972s]
Writing 'system_a' OKAY [ 30.911s]
Sending sparse 'system_a' 2/4 (524284 KB) OKAY [ 12.910s]
Writing 'system_a' OKAY [ 43.875s]
Sending sparse 'system_a' 3/4 (524284 KB) OKAY [ 12.952s]
Writing 'system_a' OKAY [ 54.928s]
Sending sparse 'system_a' 4/4 (461052 KB) OKAY [ 11.393s]
Writing 'system_a' OKAY [ 61.682s]
archive does not contain 'system_dlkm.img'
archive does not contain 'system_ext.img'
extracting system_other.img (291 MB) to disk... took 1.226s
archive does not contain 'system.sig'
Sending 'system_b' (298348 KB) OKAY [ 7.401s]
Writing 'system_b' OKAY [ 36.020s]

extracting vendor.img (253 MB) to disk... took 1.001s
archive does not contain 'vendor.sig'
Sending 'vendor_a' (259272 KB) OKAY [ 6.411s]
Writing 'vendor_a' OKAY [ 34.017s]
archive does not contain 'vendor_dlkm.img'
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 7.370s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 6509568 4k blocks and 1630208 inodes
Filesystem UUID: c1a83b3e-1f27-11ed-a597-97a5de11350a
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'userdata' (180 KB) OKAY [ 0.078s]
Writing 'userdata' OKAY [ 2.148s]
Finished. Total time: 349.026s
Press any key to exit...

After flashing slot A was done, I opened another command prompt, I'm still on the Fastboot screen and Slot A, so I fastboot --set-active=b, then fastboot reboot bootloader and verify it now says I'm on Slot B. I flash-all again.

S:\platform-tools - Pixel 1 (non-XL - sailfish)>fastboot --set-active=b
Setting current slot to 'b' OKAY [ 0.099s]
Finished. Total time: 0.110s

S:\platform-tools - Pixel 1 (non-XL - sailfish)>fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.007s]
Finished. Total time: 0.013s

S:\platform-tools - Pixel 1 (non-XL - sailfish)>flash-all
Sending 'bootloader_b' (32480 KB) OKAY [ 0.889s]
Writing 'bootloader_b' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 1.748s]
Finished. Total time: 2.801s
Rebooting into bootloader OKAY [ 0.008s]
Finished. Total time: 0.010s
Sending 'radio_b' (57156 KB) OKAY [ 1.490s]
Writing 'radio_b' OKAY [ 0.498s]
Finished. Total time: 2.151s
Rebooting into bootloader OKAY [ 0.008s]
Finished. Total time: 0.011s
--------------------------------------------
Bootloader Version...: 8996-012001-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: XXXXXXXXXXXXXXXXXXXXXXXXXXXX
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.047s]
Checking 'version-bootloader' OKAY [ 0.047s]
Checking 'version-baseband' OKAY [ 0.047s]
Setting current slot to 'b' OKAY [ 0.098s]
extracting boot.img (30 MB) to disk... took 0.124s
archive does not contain 'boot.sig'
Sending 'boot_b' (30793 KB) OKAY [ 0.783s]
Writing 'boot_b' OKAY [ 0.265s]
archive does not contain 'init_boot.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
archive does not contain 'vbmeta.img'
archive does not contain 'vbmeta_system.img'
archive does not contain 'vbmeta_vendor.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'vendor_kernel_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
archive does not contain 'product.img'
extracting system.img (1986 MB) to disk... took 7.449s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/4 (524284 KB) OKAY [ 12.972s]
Writing 'system_b' OKAY [ 3.599s]
Sending sparse 'system_b' 2/4 (524284 KB) OKAY [ 12.904s]
Writing 'system_b' OKAY [ 3.583s]
Sending sparse 'system_b' 3/4 (524284 KB) OKAY [ 12.961s]
Writing 'system_b' OKAY [ 3.544s]
Sending sparse 'system_b' 4/4 (461052 KB) OKAY [ 11.406s]
Writing 'system_b' OKAY [ 3.161s]
archive does not contain 'system_dlkm.img'
archive does not contain 'system_ext.img'
extracting system_other.img (291 MB) to disk... took 1.252s
archive does not contain 'system.sig'
Sending 'system_a' (298348 KB) OKAY [ 7.411s]
Writing 'system_a' OKAY [ 2.058s]

extracting vendor.img (253 MB) to disk... took 1.016s
archive does not contain 'vendor.sig'
Sending 'vendor_b' (259272 KB) OKAY [ 6.410s]
Writing 'vendor_b' OKAY [ 1.808s]
archive does not contain 'vendor_dlkm.img'
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 1.745s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 6509568 4k blocks and 1630208 inodes
Filesystem UUID: dfb80e82-1f28-11ed-88a6-a748c4377f49
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'userdata' (180 KB) OKAY [ 0.053s]
Writing 'userdata' OKAY [ 0.057s]
Finished. Total time: 97.847s
Press any key to exit...

It's funny how after the initial round of flashing system_a, there's a single small flashing system_b when I'm on Slot A, and vice versa for when I'm on Slot B. Bolded in the logs above.

I then click the power button to "Start" - to boot up. Blast that old stupid white Google splash screen!

Argh, I forgot to sign out of my account on the phone before flashing it, so now I'm forced to sign in again in case I stole my phone. What is my password!? At least once I sign in to verify I didn't steal my own phone, it doesn't automatically add the account and start syncing, it's nice enough to ask if I really want to add that account or not.

Why on this fresh device is there a "Downloaded from iCloud" subfolder in my DCIM folder? I don't use iCloud. Heh. There's also "Pictures/Restored from iPhone/Other Photos". Weird.

1660850597332.png
2. Slot B Update available - Screenshot_20220818-152415.png
3. Slot B Update screen - Screenshot_20220818-152627.png
4. Slot B Update screen progress - Screenshot_20220818-153303.png

Taking a long time for a 29.43 MB update.

5. Slot B Update ready for reboot - Screenshot_20220818-153731.png

Clicked "Restart now".

6. Slot A Finishing system update - Screenshot_20220818-154051.png

7. Slot A Finishing system update - Screenshot_20220818-154107.png

8. Slot A Build # - Screenshot_20220818-154123.png

9. Slot A Update screen - Screenshot_20220818-154138.png

adb reboot bootloader reveals I am now on Slot A, as expected.

fastboot --set-active=b to switch to Slot B.

fastboot reboot bootloader to verify I'm now on Slot B - I am.

Press Power Button to start booting. Took a VERY LONG time to boot, with the G logo and the line moving underneath it in the center. Maybe I should've put the first version of the Sailfish firmware on it instead of the second to the last. :D

Woah! What the heck? Android Recovery. Cannot load Android system, blah, blah, blah. Try again or factory reset? Try again! I'm a glutton for punishment!

Nope, no luck. Factory reset it is. Booted this time.
 

Attachments

  • 8. Slot A Build # - Screenshot_20220818-154123.png
    8. Slot A Build # - Screenshot_20220818-154123.png
    78.7 KB · Views: 15

Markelijk

Member
Sep 5, 2015
35
13
Hi, so I updated my P6P via OTA and rebooted succesully to A13. However I tried to change the slot from Slot B to A and restarted the phone. Now my screen is black and doesn't react to any button presses. Is there something I could do? Many many many thanks in advance!!
 
  • Wow
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
Check out the suggestions in this thread:


It eventually got the user to Fastboot, and from there you should be able to use Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
 

Markelijk

Member
Sep 5, 2015
35
13
Check out the suggestions in this thread:


It eventually got the user to Fastboot, and from there you should be able to use Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).

Thanks. The only thing is that OP does actually see something on his screen, and I see nothing. Windows does make a 'device connected/disconneced' sound when I'm pressing the power button in combination with volume buttons.
 
  • Wow
Reactions: roirraW "edor" ehT

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Looks like they finally updated the "Updating Pixel 6, Pixel 6 Pro, and Pixel 6a devices to Android 13 for the first time" section on the download page to include the correct command for Option 2 (adb reboot bootloader rather than adb reboot fastboot).
    5
    This thread confuses me. Can one root a device that is currently sim locked?
    SIM locking, which locks your SIM card to your device, i.e. can't move that same SIM card with another device, is not the same as being Carrier locked. The ability to lock your SIM card to your device is controlled by you only - by default, SIM cards are not locked to the device. You can use the search field in the device Settings to find "SIM card lock", which is in the "More security settings" submenu.

    As the others have said, Carrier unlocking and having the ability to bootloader unlock are two separate things, but typically if a device is not carrier unlocked, then you are also not able to unlock the bootloader. Being carrier unlocked does not necessarily mean you can unlock the bootloader. Example 1: Verizon. Example 2: All Samsung devices bought in the United States that can have mobile data connections. Samsung WI-Fi-only tablets can be bootloader unlocked (at the cost of tripping KNOX permanently), but obviously, in that case, there's no carrier involved.
    5

    BulletinLanguagesPublished dateSecurity patch level
    September 2022Coming soonSeptember 6, 20222022-09-05

    Pixel Update Bulletin—September 2022​


    Published September 6, 2022
    The Pixel Update Bulletin contains details of security vulnerabilities and functional improvements affecting supported Pixel devices (Google devices). For Google devices, security patch levels of 2022-09-05 or later address all issues in this bulletin and all issues in the September 2022 Android Security Bulletin. To learn how to check a device's security patch level, see Check and update your Android version.
    All supported Google devices will receive an update to the 2022-09-05 patch level. We encourage all customers to accept these updates to their devices.
    Note: The Google device firmware images are available on the Google Developer site.

    Announcements​

    • In addition to the security vulnerabilities described in the September 2022 Android Security Bulletin, Google devices also contain patches for the security vulnerabilities described below.

    Security patches​

    Vulnerabilities are grouped under the component that they affect. There is a description of the issue and a table with the CVE, associated references, type of vulnerability, severity, and updated Android Open Source Project (AOSP) versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.

    Kernel components​

    CVEReferencesTypeSeverityComponent
    CVE-2022-28388A-228694483
    Upstream kernel
    EoPModerateKernel

    Pixel​

    CVEReferencesTypeSeverityComponent
    CVE-2022-20231A-211485702*EoPCriticalTrusty
    CVE-2022-20364A-233606615*EoPCriticalKernel

    Qualcomm components​

    CVEReferencesSeverityComponent
    CVE-2022-25654A-223230190
    QC-CR#3075470
    ModerateKernel

    Qualcomm closed-source components​

    CVEReferencesSeverityComponent
    CVE-2022-25653A-223230071*ModerateClosed-source component

    Functional patches​

    For details on the new bug fixes and functional patches included in this release, refer to the Pixel Community forum.

    Common questions and answers​

    This section answers common questions that may occur after reading thisulletin.
    1. How do I determine if my device is updated to address these issues?
    Security patch levels of 2022-09-05 or later address all issues associated with the 2022-09-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Google device update schedule.
    2. What do the entries in the Type column mean?
    Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.
    AbbreviationDefinition
    RCERemote code execution
    EoPElevation of privilege
    IDInformation disclosure
    DoSDenial of service
    N/AClassification not available
    3. What do the entries in the References column mean?
    Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
    PrefixReference
    A-Android bug ID
    QC-Qualcomm reference number
    M-MediaTek reference number
    N-NVIDIA reference number
    B-Broadcom reference number
    U-UNISOC reference number
    4. What does an * next to the Android bug ID in the References column mean?
    Issues that are not publicly available have an * next to the Android bug ID in the References column. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
    5. Why are security vulnerabilities split between this bulletin and the Android Security Bulletins?
    Security vulnerabilities that are documented in the Android Security Bulletins are required to declare the latest security patch level on Android devices. Additional security vulnerabilities, such as those documented in this bulletin are not required for declaring a security patch level.

    Versions​

    VersionDateNotes
    1.0September 6, 2022Bulletin Published
    4
    @roirraW "edor" ehT Thank you, I was just curious in case a situation appeared again where I needed to have both slots the same (I like to ask before I get stuck up a creek w/o a paddle).
    You're welcome. Understood.

    Just at minimum do (and you should do first thing):
    Code:
    fastboot flash bootloader --slot all bootloader.img
    And that'll prevent you from getting stuck. Not doing that, you could wind up being bricked to a point where only Google could repair the phone.
    4
    Changes in this month's build - quoted directly from the Google Pixel Community post (as couldn't see them anywhere).
    Thanks!

    Am I missing something though? I thought September was meant to be a feature drop update?
    No. There should be a new Beta sometime this month, which would be QPR1 Beta 1. I'll have a separate thread for that, or will maybe revive my Beta thread.
  • 59
    SURPRISE new Factory Image:


    13.0.0 (TP1A.220905.004.A1, Sep 2022, Verizon, Verizon MVNOs)FlashLink5e431fe5b488b48c4543a22f18356d1ad45c04fdab07bfe451ca13bdf08d0039

    I see the September update for the 6a also came out. :)

    September 2022 factory image is available:

    13.0.0 (TP1A.220905.004, Sep 2022)FlashLink4dba4ced0ea829e3d334dee55d8b15daa4cd1b57848417a8787d68a0b6ce3793

    Kush M.
    Community Manager•Original Poster

    Google Pixel Update - September 2022​

    Announcement
    Hello Pixel Community,

    We have provided the monthly software update for September 2022. All supported Pixel devices running Android 13 will receive these software updates starting today. The rollout will continue over the next week in phases depending on carrier and device. Pixel 6a devices will receive the update later this month. Users will receive a notification once the OTA becomes available for their device. We encourage you to check your Android version and update to receive the latest software.

    Details of this month’s security fixes can be found on the Android Security Bulletin: https://source.android.com/security/bulletin

    Thanks,
    Google Pixel Support Team


    Software versions

    Global
    • Pixel 4 (XL): TP1A.220905.004
    • Pixel 4a: TP1A.220905.004
    • Pixel 4a (5G): TP1A.220905.004
    • Pixel 5: TP1A.220905.004
    • Pixel 5a (5G): TP1A.220905.004
    • Pixel 6: TP1A.220905.004
    • Pixel 6 Pro: TP1A.220905.004

    What’s included

    The September 2022 update includes bug fixes and improvements for Pixel users – see below for details.

    Battery & Charging
    • Fix for issue occasionally causing increased battery drain from certain launcher background activities
    • Fix for issue preventing wireless charging mode to activate in certain conditions *[1]

    Biometrics
    • Additional improvements for fingerprint recognition and response in certain conditions *[2]

    Bluetooth
    • Fix for issue occasionally preventing certain Bluetooth devices or accessories from connecting

    User Interface
    • Fix for issue occasionally causing notifications to appear truncated on the lock screen
    ---------------------------------------------------------------

    Device Applicability

    Fixes are available for all supported Pixel devices unless otherwise indicated below.

    *[1] Included on Pixel 4, Pixel 4 XL, Pixel 5, Pixel 6 & Pixel 6 Pro
    *[2] Included on Pixel 6a


    Details
    Other

    BulletinLanguagesPublished dateSecurity patch level
    September 2022Coming soonSeptember 6, 20222022-09-05

    Pixel Update Bulletin—September 2022​


    Published September 6, 2022
    The Pixel Update Bulletin contains details of security vulnerabilities and functional improvements affecting supported Pixel devices (Google devices). For Google devices, security patch levels of 2022-09-05 or later address all issues in this bulletin and all issues in the September 2022 Android Security Bulletin. To learn how to check a device's security patch level, see Check and update your Android version.
    All supported Google devices will receive an update to the 2022-09-05 patch level. We encourage all customers to accept these updates to their devices.
    Note: The Google device firmware images are available on the Google Developer site.

    Announcements​

    • In addition to the security vulnerabilities described in the September 2022 Android Security Bulletin, Google devices also contain patches for the security vulnerabilities described below.

    Security patches​

    Vulnerabilities are grouped under the component that they affect. There is a description of the issue and a table with the CVE, associated references, type of vulnerability, severity, and updated Android Open Source Project (AOSP) versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.

    Kernel components​

    CVEReferencesTypeSeverityComponent
    CVE-2022-28388A-228694483
    Upstream kernel
    EoPModerateKernel

    Pixel​

    CVEReferencesTypeSeverityComponent
    CVE-2022-20231A-211485702*EoPCriticalTrusty
    CVE-2022-20364A-233606615*EoPCriticalKernel

    Qualcomm components​

    CVEReferencesSeverityComponent
    CVE-2022-25654A-223230190
    QC-CR#3075470
    ModerateKernel

    Qualcomm closed-source components​

    CVEReferencesSeverityComponent
    CVE-2022-25653A-223230071*ModerateClosed-source component

    Functional patches​

    For details on the new bug fixes and functional patches included in this release, refer to the Pixel Community forum.

    Common questions and answers​

    This section answers common questions that may occur after reading thisulletin.
    1. How do I determine if my device is updated to address these issues?
    Security patch levels of 2022-09-05 or later address all issues associated with the 2022-09-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Google device update schedule.
    2. What do the entries in the Type column mean?
    Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.
    AbbreviationDefinition
    RCERemote code execution
    EoPElevation of privilege
    IDInformation disclosure
    DoSDenial of service
    N/AClassification not available
    3. What do the entries in the References column mean?
    Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
    PrefixReference
    A-Android bug ID
    QC-Qualcomm reference number
    M-MediaTek reference number
    N-NVIDIA reference number
    B-Broadcom reference number
    U-UNISOC reference number
    4. What does an * next to the Android bug ID in the References column mean?
    Issues that are not publicly available have an * next to the Android bug ID in the References column. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
    5. Why are security vulnerabilities split between this bulletin and the Android Security Bulletins?
    Security vulnerabilities that are documented in the Android Security Bulletins are required to declare the latest security patch level on Android devices. Additional security vulnerabilities, such as those documented in this bulletin are not required for declaring a security patch level.

    Versions​

    VersionDateNotes
    1.0September 6, 2022Bulletin Published

    Regarding Developer Support Android 12 images, see @Lughnasadh's post here.

    I am not linking directly to the Developer Support Android 12 images because I don't want them to be confused with Stable Android 12, and since the Developer Support images won't receive any OTAs...ever. They likely also will never be manually updated on the Developer Support images site, so they will forever be stuck with the security patch level they're currently on, which will become further out of date every month. You can Google search Developer Support Android images if you want to find them.

    Platform Tools has been updated slightly to v33.0.3:

    Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip

    Mac: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip

    Linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip

    Release Notes https://developer.android.com/studio/releases/platform-tools:

    33.0.3 (Aug 2022)​

    • adb
      • Don't retry adb root if first attempt failed.
      • Fix track-devices duplicate entry.
      • Add receive windowing (increase throughput on high-latency connections).
      • More specific error messages in the "more than one device" failure cases.
      • Reject unexpected reverse forward requests.
      • Fix install-multi-package on Windows.
    • fastboot
      • Remove e2fsdroid as part of SDK platform-tools.
      • Print OemCmdHandler return message on success.

    TL;DR regarding the PSA. If you update one slot to Android 13, you can fastboot reboot bootloader after and then fastboot --set-active=other to change slots in order to flash Android 13 to the new slot, but IF you have Android 13 on one slot and still have Android 12 (including Android 12 bootloader) on the other slot and you try to fully boot into Android 12, you will be permanently bricked and have to seek repair from Google. No one has yet found a way to repair this on our own. I will update if there is any progress. At least a small handful, and probably more, people have done this already.

    At a minimum, do this first: fastboot flash bootloader --slot all bootloader-devicename-slider-1.2-3456789.img (change the name of the bootloader file to the one for your device), then you *should* be much safer than without doing that first. Also note that the bootloader is NOT the same as boot.img (kernel). The bootloader image file has "bootloader" in the filename.

    IF you have already bricked your phone and the screen is blank - there is likely nothing we can do to help. You should seek to get a repair from Google, possibly under warranty.


    You CANNOT go back to Android 12 Stable. It *seems* as if you can, but Android 12 will not work 100% correctly after updating to the Android 13 bootloader.

    My tiny, early, very mini-review of Android 13 is here.

    Note that this is mainly for the officially listed "Unlocked" Pixel 6 Pro, available directly from the Google Store. All of this will also apply to any other (carrier-specific) variant of the Pixel 6 Pro which you can achieve an unlocked bootloader on. This includes T-Mobile and AT&T variants. It's likely Verizon variants will never be able to unlock their bootloader, or if so it will require paying the right person to do so.

    Feel free to ask about general questions, but for anything that's specific to your variant, you should use one of the other already existing threads. You'll find Verizon, AT&T, and T-Mobile-related threads in those respective search results.

    Here there be dragons. 🐉 I am not responsible for anything at all. 😹

    Unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device.


    Keep in mind that unlocking the bootloader or rooting might affect your phone's capability to use banking apps such as Google Pay, your local bank's app, or even the ability to install some apps like NetFlix. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12

    If you're going to re-lock the bootloader, make sure the ROM you have on your phone is completely stock (by flashing the latest official firmware) BEFORE re-locking it.

    There are no negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that the bootloader is unlocked. You will also continue to receive updates (if you've merely unlocked the bootloader, you can take updates as normal) unlike Samsung, Sony, et cetera, which have permanent major consequences with reduced functionality even if you un-root and re-lock your bootloader. If you're actually rooted (not just bootloader unlocked), you'll have to perform extra steps to manually update each month, and to keep root/re-root.


    All posts about Google Pay or banking will be reported to be deleted. Please keep this thread on-topic. There are at least one or two other How To Guide threads in this section in which folks discuss how to get around banking app restrictions when you're rooted or just have an unlocked bootloader. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12
    If users persist in discussing banking apps in this thread, I will have this thread locked and only update this first post when there is new and updated information regarding the subjects of the title of the thread: Unlocking the Pixel 6 Pro bootloader, rooting, and TWRP. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12

    Honorable mention to @Jawomo's aodNotify - Notification Light / LED for Pixel 6 Pro! (XDA link) / Notification light / LED for Pixel - aodNotify (Play Store link), which in my opinion restores useful functionality missing in most phones these days. It also solves some subjective issues some folks have with AOD (Always On Display), and/or solves/works around the problem where AOD is required for the optical fingerprint reader to work without the screen being on.​


    Check warranty status - *may* reveal if a phone is refurbished, only if the phone was refurbished through Google - thanks to @Alekos for making me aware of the site.
    Official Google Pixel Update and Software Repair (reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro yet)

    Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.

    Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen
    Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
    OEM unlocking in developer options needs to be toggled on. I don't "believe" you have to actually do the "fastboot flashing unlock" command.

    ADB/Fastboot, Windows Drivers, and unlocking the bootloader (thanks @sidhaarthm for confirming unlocking the bootloader works as intended, be sure to thank him in his post)
    • You'll need this if you're going to unlock the bootloader on your Pixel 6 Pro: SDK Platform Tools (download links for Windows, Mac, and Linux). Note that you can find links to download the tools elsewhere, but I wouldn't trust them - you never know if they've been modified. Even if the person providing the link didn't do anything intentionally, the tools could be modified without them being aware. Why take a chance of putting your phone security further at risk?
    • For Windows, get Google's drivers here Get the Google USB Driver (ADB will likely work while the phone is fully booted, but if you're like me, you'll need these drivers for after you "adb reboot-bootloader", to be able to use ADB and Fastboot.
    • Thanks to @96carboard for posting the details of unlocking the bootloader, be sure to thank him in his post. Unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device. Keep in mind that unlocking the bootloader or rooting might affect your phone's capability to use banking apps such as Google Pay, or your local bank's app. If you're going to re-lock the bootloader, make sure the ROM you have on your phone is completely stock (by flashing the latest official firmware) BEFORE re-locking it. My experience on my Pixel 1 was that there were no negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that the bootloader is unlocked. All of this should still be the case. You will also continue to receive updates. Unlike Samsung, Sony, et cetera, which have major consequences with reduced functionality even if you un-root and re-lock your bootloader. If you're actually rooted (not just bootloader unlocked), you'll have to perform extra steps to keep root/re-root.:


      The unlock process works like this:

      1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on (you can put a SIM card if you want, you just don't have to).
      2) When it starts harassing you to join Google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
      3) Settings --> About --> Build number. Repeatedly tap it until it says you're a developer.
      4) Back --> Network --> WiFi and connect it.
      5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize on the phone when requested.

      Using the Platform Tools previously mentioned in command line/terminal:
      6) #
      Code:
      adb reboot-bootloader
      7) #
      Code:
      fastboot flashing unlock

      Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.

      Official Instructions for Locking/Unlocking the Bootloader
    Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.
    I agree with this. be careful using drivers or adb/fastboot tools. Some are fine, but there's no need for it really anymore. Google has made it very easy to install drivers and Platform-Tools (adb/fastboot tool).

    Google provides the Fastboot/ADB tool (Platform-Tools) and Google USB Drivers (adb/fastboot interface). This will allow any Pixel to interface with Windows using the fastboot/adb protocol. Official Google USB Driver includes support for both the Fastboot and ADB driver interface. There are 3 main drivers (Fastboot, ADB and MTP/Portable File Transfer). The MTP/Portable File Transfer driver is built-in to Windows 7-11.

    Fastboot/ADB Driver Interface - Official Download Link:
    When flashing a full image or unlocking your bootloader, the fastboot interface is being used.

    First Download official Google USB Drivers (it's a zip file). Extract the zip (important!). Right-click on the android_winusb.inf file and hit install. You can then restart your phone to the Bootloader Screen (hold vol-down while it restarts or turns on). When you plug in your phone, Windows Device Manager will show a new device at the top: Android Device: Android Bootloader Interface.

    Using the ADB interface: It's the same driver. Enable USB Debugging on your phone, then plug it in to your computer. A prompt will appear on your phone (to allow USB Debugging). The driver in Device Manager will appear as Android Device: Android Composite ADB interface.

    Now you can download and use Platform-Tools to flash an Android Image, OTA or run adb/fastboot commands.
    Official Download Page
    "Android SDK Platform-Tools is a component for the Android SDK. It includes tools that interface with the Android platform, such as adb, fastboot, and systrace"

    It's best to make Platform-Tools available system-wide. Download Platform-Tools from the above link and extract it to your C:\ drive - that way you will have a folder to add to the PATH Environment under Window System Properties Menu, Advanced, Environment Variables, System Variables, PATH (google how to do this, very easy). What this does is allow adb/fastboot commands to be run from anywhere in the system, so you don't have to be in the platform-tools folder to run adb/fastboot commands and flash an Android Image (Official or Android Fork such as ProtonAOSP).

    Rooting-related


    No longer applies - Things that make rooting more complicated on Android 12
    @V0latyle posted a new thread with some very important and fascinating information about the increased difficulty to root Android 12: Read this before rooting. Be sure to thank him there.

    A list of the other important guides - be sure to thank the respective OPs
    For all relevant guide threads just click the yellow "How To Guide" quick filter above the list of threads in the Pixel 6 Pro section.


    TWRP (not made for the Pixel 6 Pro yet - will update when it has)
    I would guess that this should be the appropriate URL for official TWRP custom recovery for the Pixel 6 Pro, but who knows when/if that will actually be made available, and it may become available unofficially in these forum sections before being made official. I'll adjust this URL as needed. https://twrp.me/google/googlepixel6pro.html.

    Custom kernels for stock ROM(s)

    Factory Images (requires an unlocked bootloader)
    It's also handy to have to the full official firmware available, whether it's to recovery from accidents or for actual development. Note the official link to the general Factory Images for Nexus and Pixel Devices page. The following link goes directly to the Pixel 6 Pro (Raven) section: Pixel 6 Pro Factory Images. I prefer to actually bookmark a link to the device listed immediately below the device I want the firmware for, because Google dumbly (in my opinion) puts the latest firmware at the bottom of the list for each particular device, and that ends up making you scroll a lot after a year or two of monthly updates.

    Note: You can still get the December 2021 Factory Images and OTA from this thread, if you need them for any reason: Alternate links to December - all full factory images and OTAs available

    Full OTA Images (doesn't require an unlocked bootloader)

    The usefulness of having Verity and Verification enabled (now that it's not needed for root) - post #2 below.

    Regarding P6P 5G model numbers and capabilities - post #3 below.

    List of all Pixel monthly security bulletins and Play System Updates - post #4 below.

    How I root and update (which is identical whether rooting the first time or updating):
    • Use the latest Magisk Stable (in my case, I keep the app "hidden" / renamed)
    • Used the full firmware zip, extracted to the same folder as the latest Platform Tools (S:\platform-tools)
    • Extracted the new boot.img
    • Copied new boot.img to the phone
    • Patched the new boot.img with Magisk Stable
    • Renamed Magisk'd boot.img so I know what version of firmware it's for
    • Copied the Magisk'd boot.img back to the computer
    • Disabled all my Magisk Modules
    • Removed the "-w " from the flash-all.bat
    • Re-edited the flash-all.bat to verify I saved it with the "-w " taken out
    • Open a Command Prompt, navigated to S:\platform-tools
    • adb reboot bootloader
    • flash-all.bat
    • Let phone boot, unlock it, check that it's working, allow the update process to finish (gave it five minutes or so)
    • adb reboot bootloader
    • fastboot flash boot kernel.img (renamed Magisk'd boot.img)
    • fastboot reboot
    • Unlock, check everything's working
    • Re-enabled the most basic Magisk Modules which I was sure wouldn't cause a critical issue
    • Reboot, unlock, made sure everything's working
    Back to modding!

    I may append these first four posts with further useful information or links as needed.
    15
    The unlock process works like this;

    1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on.
    2) When it starts harassing you to join google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
    3) Settings --> About --> Build number. Tap it until it says you're a developer.
    4) Back --> Network --> Wifi and connect it.
    5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize when requested.
    6) # adb reboot-bootloader
    7) # fastboot flashing unlock

    Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.
    15
    SDK Platform Tools updated to v33.0.1 (March 2022):

    33.0.1 (March 2022)​

    • adb
      • Fixes Windows mdns crashes.
      • Fixes enable-verity/disable-verity on old devices.
      • Fixes "install multiple" on old devices
      • Improves the help output to include all supported compression methods.
    13
    Just to let everyone know, updating to .037 and re-rooting (without wiping anything) worked with no problems. My method is to just replace -w with --disable-verity --disable-verification in the flash-all.bat file and run the flash-all command. I then let it reboot, patch the boot image, return to bootloader and flash the patched boot image.

    Canary 23014

    EDIT: Thank you @ipdev for confirming my inquiry that this method would work back on Nov. 4 👍
    11
    SDK Platform Tools have been updated to v32.0.0 (January 2022). Update now before you forget and flashing the February update on the 7th gives you hassles. :)

    Direct download for Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip

    Revisions​

    32.0.0 (January 2022)​

    • adb
      • Fixed adb w/o args SEGV regression.
    • fastboot
      • Reinstated recovery execution from b/158156979 (removal of preprocessor guards for root/secure).