[Renate]

That failed at product. Was the last time a failure at vendor?
It is failing at different spots, isn't it?

Here's the trimmed-down logs from mine (good) and yours (bad):
(They are different devices so the hashes are not supposed to be the same.)

== GOOD ==

ActionProcessor: finished DownloadAction with code ErrorCode::kSuccess
ActionProcessor: starting FilesystemVerifierAction
	Hash of boot: p7Hqd9v1wuKI7lLLkZbXyQ6q8N7+Wcho0bePpmNS9tg=
	Hash of dtbo: b0LvfQxEzhhv6XoLPcLBcTHbRKFGYY93ko/32fyYPdI=
	Hash of product: RPBwsDz0NTGcPQzkZP1bKsG6y8Kv8tkLleREUgzpUbI=
	Hash of system: w+8HH1av4Io+jLQSOOPU8IMPrFO4JTDOp1pXiW2SjC0=
	Hash of system_ext: mHEq7QZ14rhRSUe0El7COBrEkHakZjDqNk+1u818IBA=
	Hash of vbmeta: YpvAClGrpMpk7vj13ePLeSgRK9fK3M9Akc+IlURkWrs=
	Hash of vbmeta_system: ND2lcx0jmmM3NYYXzK0xs/z1DhXQTAzQJTlyHkJc4A8=
	Hash of vendor: BvdgwFrPsGYRDHIcldkNVYDv/m+KXlF71T4007bazN8=
	Hash of xbl: rD5nVc9pLohGdh85TPY+du4yEixZh2WYH509ysy8POA=
ActionProcessor: finished FilesystemVerifierAction with code ErrorCode::kSuccess

== BAD ==

PartitionInfo new modem sha256: 9T6r9vOmVqnYNjIQOobJc45ftSESKfsYYWSWht2p+54= size: 40488960
PartitionInfo new product sha256: jvuR+pJgk3OimbtNZhZZ8s2B2wHv+z6lSm8NA/dygD8= size: 459763712
...
ActionProcessor: finished DownloadAction with code ErrorCode::kSuccess
ActionProcessor: starting FilesystemVerifierAction
	Hash of boot: V1kNtiYXrWTGawiBxww1EZsrKckmYR/5p15eQSVrluY=
	Hash of dtbo: IqDqDNdfPmAUOq9MvDwC1LtDv/9FiwhQexpQj5CczZU=
	Hash of modem: 9T6r9vOmVqnYNjIQOobJc45ftSESKfsYYWSWht2p+54=
	Hash of product: YHKAJhju/XflE039+XNJeaRAu2tkTDi2KXE5PivS2LE=
	New 'product' partition verification failed.

I just updated my Poke5 another two times (both slots) and it went perfectly.

Mmm, if you have a Type C hub with PD (takes power in) you might try that.
I don't think it's worth buying one though unless you have a use for it.

The other thing is, use a Python payload dumper and dump payload.bin on your desktop.
It will tell you whether all the files in it are straight replace or whether some are incremental.

When you have product (as uncompressed single image) you can generate the SHA256 of that, then encode that with Base64 and it should be the same as either the first or the second hash. I just checked that on a few of my partitions and it all checks out.