[Google Pixel 6 Pro] DRatJr:
I just patched my boot.img, and it looks like a couple of errors were thrown during the process. Just wanted to make sure I can proceed to updating. It shows the patched boot.img under the boot images so I think I'm good, but just wanted to double check.

For context I am trying to update while maintaining data and root.

==============================================================================
2022-11-02 11:07:33 PixelFlasher 4.3.1.0 Patching boot.img
==============================================================================
Deleting boot.img_912e5dba.img from phone in /storage/emulated/0/Download ...
Making sure boot.img_912e5dba.img is not on the phone in /storage/emulated/0/Download ...
Deleting magisk_patched*.img from phone in /storage/emulated/0/Download ...
Making sure magisk_patched*.img is not on the phone in /storage/emulated/0/Download ...
Transfering boot.img_912e5dba.img to the phone in /storage/emulated/0/Download ...
C:\Users\thisi\AppData\Roaming\PixelFlasher\boot_images4\912e5dba0da65a4404ee50899ef4d5192102275d\boot.img: 1 file pushed, 0 skipped. 193.1 MB/s (67108864 bytes in 0.331s)

Making sure boot.img_912e5dba.img is found on the phone in /storage/emulated/0/Download ...
Looking for Magisk Manager app ...
Magisk Manager Version: 25205
Magisk Version: 25205
Patching with rooted Magisk: a468fd94:25205
Cleaning up...
- Unpacking boot image
Parsing boot image: [/sdcard/Download/boot.img_912e5dba.img]
HEADER_VER [4]
KERNEL_SZ [25000489]
RAMDISK_SZ [0]
PAGESIZE [4096]
CMDLINE []
KERNEL_FMT [lz4_legacy]
VBMETA
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
Add entry [init] (0750)
Create directory [overlay.d] (0750)
Create directory [overlay.d/sbin] (0750)
Add entry [overlay.d/sbin/magisk32.xz] (0644)
Add entry [overlay.d/sbin/magisk64.xz] (0644)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[true]
Record new entry: [init] -> [.backup/.rmlist]
Record new entry: [overlay.d] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk32.xz] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk64.xz] -> [.backup/.rmlist]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
- Repacking boot image
Parsing boot image: [/sdcard/Download/boot.img_912e5dba.img]
HEADER_VER [4]
KERNEL_SZ [25000489]
RAMDISK_SZ [0]
PAGESIZE [4096]
CMDLINE []
KERNEL_FMT [lz4_legacy]
VBMETA
Repack to boot image: [new-boot.img]
HEADER_VER [4]
KERNEL_SZ [25000489]
RAMDISK_SZ [513898]
PAGESIZE [4096]
CMDLINE []

Looking for magisk_patched_912e5dba.img in /storage/emulated/0/Download ...
Found /storage/emulated/0/Download/magisk_patched_912e5dba.img
Pulling /storage/emulated/0/Download/magisk_patched_912e5dba.img from the phone to: magisk_patched_912e5dba.img ...
Getting SHA1 of C:\Users\thisi\AppData\Roaming\PixelFlasher\tmp\magisk_patched_912e5dba.img ...
SHA1 of magisk_patched_912e5dba.img file: 230049b67ff399f491f2f885d95338356bbd176a

Getting SHA1 of source boot.img ...
Source boot.img's SHA1 is: 912e5dba0da65a4404ee50899ef4d5192102275d
Getting SHA1 from Magisk config ...
Magisk Config's SHA1 is: c1c3ca15ec405f6d4e619618e608306a708a2d07
Comparing source boot.img SHA1 with Magisk's config SHA1 (they should match) ...

2022-11-02 11:07:44 ERROR: Something is wrong Magisk config has the wrong SHA1 ...

Checking to see if Magisk made a backup of the source boot.img
Good: Magisk has made a backup

Extracting short SHA1 from magisk_patched_912e5dba.img ...
Short SHA1 embedded in C:\Users\thisi\AppData\Roaming\PixelFlasher\tmp\magisk_patched_912e5dba.img is: 912e5dba
Comparing short source boot.img SHA1 with short SHA1 embedded in 912e5dba (they should match) ...
Good: Both SHA1s: 912e5dba match.

DB BOOT record ID: 2
DB Package_Boot record ID: 2

Please select a boot image!
Magisk Version: a468fd94:25205
Patch time: 11 seconds
------------------------------------------------------------------------------