@Waterdevil First of all, sorry to hear about your father.
Waterdevil last night my pixel 7 pro switched off, because no energy. Today I loaded it, switched on, then there was an update running. I had to reboot, but it said with red attention:
“Your device is corrupt. It can’t be trusted and may not work properly.”
Due to the way A/B seamless updates work, a failed update will not cause your device to become corrupt. The OS will automatically switch back to the slot that worked last and boot normally.
Waterdevil fastboot flashing unlock
When sideloading, you do not have to unlock the bootloader (please refer to the sideloading instructions). If you unlock the bootloader, the phone automatically performs a factory reset. This means that the data on the phone is not recoverable.
As documented in this help article
When the fastboot flashing unlock command is sent, the device should prompt users to warn them that they might encounter problems with unofficial images. After the user acknowledges the warning, the device should perform a factory data reset to prevent unauthorized data access. The bootloader should reset the device even if it can't reformat it properly. Only after a reset can the persistent flag be set so that the device can be reflashed.
Waterdevil If this corruption error will occur again, then this OS is the biggest bullshit on planet!
There seems to be an upstream issue with firmware, which Google has to fix. This upstream issue has caused many phones to incorrectly say that there is no OS (or some other error message, I forget which error it was exactly). I understand being upset because this issue should have been fixed by Google before Android 14 was released.