Pixel 5 (redfin): after updates of build process + docs, they don't describe a working install procedure, anymore
The published states don't compose to a working install, anymore.
The build process now seems to have been modified to create an own boot image vendor_boot-e-1.15-s-*
in addition to the recovery image recovery-e-1.15-s-*
, however:
- Both files are lumped together and uploaded in a single file
recovery-IMG-e-1.15-s-*-stable-redfin.zip
- No checksums are provided for this, neither for the .zip archive nor the individual .img files. So no way to follow the verification instructions.
On the download page https://images.ecloud.global/stable/redfin/ there is now a most recent incomplete listing like this:
Android S
e-1.15-s-20230913330639-stable-redfin.zip [MD5 | SHA256] / Recovery and boot img
e-1.14-s-20230816320616-stable-redfin.zip [MD5 | SHA256] / recovery-e-1.14-s-20230816320616-stable-redfin.img [SHA256]
And on the instructions page https://doc.e.foundation/devices/redfin/install
- Under "Flashing additional partitions" there are only references to file names
boot.img
anddtbo.img
which don't exist. So no way to follow the install instructions.
[EDIT: points added from comments below:]
- The recovery download link unconditionally points to the dev build: /e/OS Recovery for dev build but only stable build contains an IMG .zip file, and it should probably just mention to download the proper (corresponding) recovery?
- The "installing a custom recovery" instructions say to run
fastboot flash vendor_boot recoveryfilename.img
However, there is now a vendor_boot-e-* file as well as a recovery-e-* file. It's not clear to which partition should the files go, both to vendor_boot?
On the dev build download page:
- there isn't even a recovery image anymore now, neither as .img nor in a .zip file: https://images.ecloud.global/dev/redfin/