"Restarting adb... Installation aborted." without any further details after abd sideload
OTA update packages must be signed with one of the keys expected by the system or the installation process will reject them.
You cannot just apply a zip to a stock ROM using the stock recovery, even if it is signed. It must be signed with the key used when building the ROM/recovery, which is only available to the device maker. If you want to apply an update you need to have a custom recovery at the very least which should allow you to bypass the signature verification.

Release keys
The Android tree includes test-keys under
build/target/product/security. Building an Android OS image using make
will sign all .apk files using the test-keys. Since the test-keys are
publicly known, anybody can sign their own .apk files with the same
keys, which may allow them to replace or hijack system apps built into
your OS image. For this reason it is critical to sign any publicly
released or deployed Android OS image with a special set of
release-keys that only you have access to.
Signatures and sideloading
Before installing a package, recovery will verify that it is signed with one of the private keys matching the public keys stored in the recovery partition, just as it would for a package delivered over-the-air.