[Google Pixel 5 Guides, News, & Discussion] Raz0Rfail:
As I didn't get the OTA i downloaded the OTA manually https://developers.google.com/android/ota#redfin (11.0.0 (RD1A.201105.003.B1, Nov 2020, EU carriers)), and installed it as described.

After I saw in "About Phone" that november Update was sucessfully installed. Then I checked magisk and saw it doesn't was installed.

So I downloaded the full Factory Image https://developers.google.com/android/images#redfin (11.0.0 (RD1A.201105.003.B1, Nov 2020, EU carriers)), extracted the included zip file. In the extracted zip file. I extracted the boot.img file.

I copied the boot image to the pixel 5 and with magisk 21005 canary Build I patched the image.

The patched boot image i copied to my pc. Rebooted phone to fastboot mode and then i flashed the patched boot image with "fastboot flash boot <boot.img>".

Rebooted Phone into Android, but it stuck at "smartphone is starting". I waited some minutes, but no change.

So i switched back to original stock boot image and android boots up sucessfully.

Hmm I thought somehow I can achieve root again. So I installed the october build boot image which was pre modified with magisk.

With the patched october boot image it didn't boot up. It stuck on Google boot screen.

And at this point the phone was broken. I can flash the stock november boot image but phone doesn't boots up.

I tried to reflash the OTA Update but no chance, phone doesn't boots up.

So I tried the factory image for november, but I removed in the flash-all.bat the parameter "-w" in the updater command. So the phone shouldn't wipe the entire System.

I got the error message that the "product" partition wasn't found. So I tried it with the October Update and removed their aswell the -w parameter. But flashing result was the same:

PS C:\Oktober Update P5> cmd
Microsoft Windows [Version 10.0.19042.610]
(c) 2020 Microsoft Corporation. Alle Rechte vorbehalten.

C:\Oktober Update P5>fastboot flash bootloader bootloader-redfin-r3-0.3-6776358.img
Sending 'bootloader_b' (8890 KB) OKAY [ 0.150s]
Writing 'bootloader_b' (bootloader) Flashing Pack version r3-0.3-6776358
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition featenabler_b
(bootloader) Flashing partition logfs
OKAY [ 0.316s]
Finished. Total time: 0.658s

C:\Oktober Update P5>fastboot reboot-bootloaderping -n 5 127.0.0.1 >nul
fastboot: unknown option -- n

C:\Oktober Update P5>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.051s

C:\Oktober Update P5>fastboot flash radio radio-redfin-g7250-00016-200827-b-6795084.img
Sending 'radio_b' (134660 KB) OKAY [ 0.620s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g7250-00016-200827-B-6795084
(bootloader) Flashing partition modem_b
OKAY [ 0.501s]
Finished. Total time: 1.314s

C:\Oktober Update P5>Oktober Update P5>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.051s

C:\Oktober Update P5>fastboot update image-redfin-rd1a.200810.021.a1.zip
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: r3-0.3-6776358
Baseband Version.....: g7250-00016-200827-B-6795084
Serial Number........: ####################
--------------------------------------------
Checking product OKAY [ 0.070s]
Checking version-bootloader OKAY [ 0.068s]
Checking version-baseband OKAY [ 0.070s]
extracting boot.img (96 MB) to disk... took 0.262s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (16 MB) to disk... took 0.032s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
extracting product.img (2041 MB) to disk... took 7.030s
archive does not contain 'product.sig'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (784 MB) to disk... took 2.974s
extracting system_other.img (23 MB) to disk... took 0.096s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (661 MB) to disk... took 2.405s
archive does not contain 'vendor_other.img'
Sending 'boot_b' (98304 KB) OKAY [ 0.470s]
Writing 'boot_b' OKAY [ 0.305s]
Sending 'dtbo_b' (16384 KB) OKAY [ 0.163s]
Writing 'dtbo_b' OKAY [ 0.114s]
Sending sparse 'product' 1/8 (262140 KB) OKAY [ 0.974s]
Writing sparse 'product' 1/8 FAILED (remote: 'Partition product not found')
Finished. Total time: 18.011s

So I think my only opinion is to include the -w parameter and loose all my data on the phone -.-

At the moment we can't use magisk in november update, and I don't know which breaks the boot image that the phone doesn't boots up correctly into android and not stuck in "Phone is starting" :(.

EDIT:

With -w parameter I got the same error message:

Writing sparse 'product' 1/8 FAILED (remote: 'Partition product not found')

So I don't know how to recovery my phone :(