Extracting short SHA1 from magisk_patched_4d938d3c.img ...
2023-04-01 13:08:09 NOTICE: The patched image file does not contain source boot's SHA1
This is normal for older devices, but newer deviced should have it.
If you have a newer device, please double check if everything is ok.
- You started with Android platform tools 34.0.1 (not good) but switched to 33.0.3 (good)
- You are posting in Pixel 6P thread but are using Pixel 7P, I don't mind, just making sure you are dealing with the proper firmware.
- Your phone is rooted with Magisk Delta 25210, but have magisk manager 25200 stable installed, don't mix and match.
- I can't speak of delta, 25210 but the official 25210 is no good.
- When creating a patch PF uses either the rooted Magisk core or the Magisk Manager, if the two versions are the same, the preference is to use the core.
If the manager is newer, then it uses the newer manager instead of the core. In your case because the core is at newer version, it is always using the core to create a patch, I suspect you're trying to create a patch with the stable version.
There are couple of ways to overcome that.
1- you can flash stock first and then create a patch, in which case it will use the manager (this is the preferred way)
2- you can temporarily remove su root rights from adb shell in Magisk Manager, in which case pf will not be able to access the core (which requires root access) and app report that the phone is not rooted, create a patch and it will use the manager.