the command to flash the recovery is it:
fastboot flash vendor_boot recoveryfilename.img
Or is it: fastboot flash vendor_boot recovery recoveryfilename.img
I had issues the other night on a Pixel 5 going from eOS a13 to a15. I think I ended up using the second command, but the upgrade of eOS 13 to 15 did not take.
Install /e/OS on a Google Pixel 5 - âredfinâ
fastboot flash vendor_boot recovery-e-3.3-a15-20251211556482-community-redfin.img
but not sure it is needed for simply upgradingâŠ
(you already have a recovery-e and it will be upgraded along the main /e/.ZIP)
piero@HP-p6-2038fr:~/Téléchargements$ ./payload-dumper-go -l e-3.3-a15-20251211556482-community-redfin.zip
Please wait while extracting payload.bin from the archive.
payload.bin: /tmp/payload_953249376.bin
Payload Version: 2
Payload Manifest Length: 115721
Payload Manifest Signature Length: 267
Found partitions:
abl (1.0 MB), aop (197 kB),boot(101 MB), devcfg (45 kB),dtbo(17 MB), featenabler (90 kB), hyp (414 kB), keymaster (250 kB), modem (153 MB), product (848 MB), qupfw (57 kB), system (1.6 GB), system_ext (536 MB), tz (3.0 MB), uefisecapp (127 kB), vbmeta (8.2 kB), vbmeta_system (4.1 kB), vendor (793 MB),vendor_boot(101 MB), xbl (3.6 MB), xbl_config (82 kB)
Edit : if you are switching branch, you may have to unlock the bootloader.
but first try as it is.
So it is at eOS a13 official and I am trying to go to a15 community, I did it the other night but when all was done the update did not take was still at a13.
So are yo saying recovery goes in with the adb sideload downloaded_file_name.zip. Like the main eOS file?
Edit: bootloader is unlocked I believe. Edit: No the bootloader was not unlocked 
(solution check if bootloader is locked official builds)
fastboot oem device-info
I am sure I will get it right away , I will say what works. 
So no matter what I do if I try either eOS a14 or a15 I always get this error when flashing recovery.
C:\PT>fastboot flash boot boot-e-3.3-a14-20251214557450-community-redfin.img
Sending âboot_bâ (98304 KB) OKAY [ 2.372s]
Writing âboot_bâ OKAY [ 1.982s]
Finished. Total time: 4.779s
C:\PT>fastboot flash dtbo dtbo-e-3.3-a14-20251214557450-community-redfin.img
Sending âdtbo_bâ (16384 KB) OKAY [ 0.484s]
Writing âdtbo_bâ OKAY [ 0.432s]
Finished. Total time: 1.334s
C:\PT>fastboot devices
15251FDD40003H fastboot
C:\PT>fastboot flash recovery recovery-e-3.3-a14-20251214557450-community-redfin.img
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 100663296).
Sending ârecoveryâ (98304 KB) OKAY [ 2.380s]
Writing ârecoveryâ FAILED (remote: âNot allowed to flash (recovery)â)
fastboot: error: Command failed
If I am at official a13 and I start to recovery the new image never goes in?
As i understand, there is no partition called recovery on your device, is it vendor_boot
Please read Pixel (5) rercovery flashing command clarification - #2 by piero
What is the output for Pixel (5) rercovery flashing command clarification - #4 by piero
What is the answer please ?
piero,
Thanks for you help.
I did end up going back to google a14 using the flash tool but at the end of the process I did not lock the bootloader. I did have to run âfastboot flashing unlockâ even though the bootloader was unlocked.
I then installed the eOS recovery and then eOS a15_3.3. In the above error I posted I was also skipping the step to restart the bootloader with the side keys after loading: fastboot flash dtbo dtbo-e-3.3-a14-20251214557450-community-redfin.img.
The reason it would not write the file when I used the side load is the bootloader was locked. I usually donât lock the bootloader even in when I load official build, in this case I did and I just forgot to check. I will edit my original post now.