[Google Pixel 8 Pro] Zilla0617:
Ok i understand how this could be confusing. I was not necessarily assigning blame to PF. When i flash ota using Pixel flasher even when successful, Pixel flasher gets stuck on non-responsive state. This occurs during a successful flash usually after my phone reboots, not sure why this happens.

I selected stock boot initially when trying to flash, couldn't find any conclusive info on whether its safe to flash patched init_boot with initial ota flash. With back-to-back, I meant flashing ota consecutively (after the initial flash PF is non-responsive I unplugged after my phone after it boots to system non-rooted and flash a second time) following the aforementioned steps. After flashing twice consectutively, I use PF to flash the patched init_boot to root my phone which worked fine. (How do i verify both slots are flashed with the appropriate patch)

My active slot already had verity and verification disabled. As stated in a previous post, the instructions for flashing ota does not outline on how to go about maintaining disabled verity and verification with each monthly patch. I researched to see if I can I do a custom sideload of ota, but I read this route does not take into account disabling verity and verification even if its marked. So I performed the regular ota flash making sure to disable both ver & verf. (Need explanation on how to perform correctly)

How do I know its successful in switching slots and having new ota image on both slots? I've read that flashing twice in a row it flashes the inactive slot first then active. I did this exact procedure for flashing Oct patch (my 1st time using pixel flash to flash ota) and assumed both slots had Oct patch. I normally flash monthly patches with factory image using adb, but your suggestion and others seem to conclude ota is safer so i decided to switch to ota in case something happen.

With the custom kernel installed and rooted I restarted the phone and immediately went to fastboot screen. I decided to reflash ota using pixel flasher, but PF error after rebooting the phone preventing it from flashing ota. It more than likely was either an issue with kernel not being compatible with Nov patch or with module I installed, so i tried restore stock kernel by flashing boot, dtbo, vendor_boot but could not get to fastbood to flash vendor_dlkm.

This is where I messed up and confused init_boot and boot to go back to stock from ( last 2 years with P6P so it was habit to use boot)

I remembered i could flash Nov patch to the inactive slot, so i tried to switching slots to make inactive active (ie. b active -> a inactve) When i performed the adb command to switch slots, thats when i found out that my inactive (a) had no OS installed. Sought help in a thread and it was mentioned to use android flash tool. Restored my phone but lost data in the process.

So to summarize, not sure why PF is non-responsive after flashing phone, maintaining disabled ver & verf. when flashing monthly patches, and how to correctly verify both flash both slots particularly when PF is non-responsive after flashing phone. I apologize if it appeared that I assigned blame to PF. Thanks for your input.