[Google Pixel 6 Pro] roirraW "edor" ehT:
@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:

Spoiler content hidden.

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:

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:

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.

Spoiler content hidden.