Maybe @c.jordan and @Unsorted7674 … you should wait for an edit of the OP … but we have a convention … that …
- “fastboot /e/OS ROMs” have a leading IMG in the filename
… but a sideload ROM would be expected to have a name
- in a format similar to
e-1.21.2-s-20240403391680-stable-one.zip
as alluded to by @AnotherElk.
Explore
Download and extract both (mentioned above) install candidates to :
~/test/murena-one
~/test/murena-one$ ls
e-1.21.2-s-20240403391680-stable-one
e-1.21.2-s-20240403391680-stable-one.zip
IMG-e-1.21.2-s-20240403391680-stable-one
IMG-e-1.21.2-s-20240403391680-stable-one.zip
1) Leading “IMG”
~/test/murena-one/IMG-e-1.21.2-s-20240403391680-stable-one$ ls
bin-linux-x86 gz.img spmfw.img
bin-msys lk.img sspm.img
boot.img logo.bin super.img
cache.img md1img.img tee.img
cam_vpu1.img MT6771_Android_scatter.txt teksunhw.bin
cam_vpu2.img preloader_g1970upt_v2_gk_p60c_oj_r.bin userdata.img
cam_vpu3.img preloader_ufs.img vbmeta.img
dtbo.img recovery.img vbmeta_system.img
flash_one_factory.sh scp.img vbmeta_vendor.img
Loosely speaking this is a “fastboot ROM”
2) sideload type download
~/test/murena-one/e-1.21.2-s-20240403391680-stable-one$ ls
boot.img META-INF system.transfer.list
cam_vpu1.img preloader_ufs.img tee.img
cam_vpu2.img product.new.dat.br teksunhw.bin
cam_vpu3.img product.patch.dat vbmeta.img
dtbo.img product.transfer.list vbmeta_system.img
dynamic_partitions_op_list recovery.img vbmeta_vendor.img
gz.img scp.img vendor.new.dat.br
install spmfw.img vendor.patch.dat
lk.img sspm.img vendor.transfer.list
logo.bin system.new.dat.br
md1img.img system.patch.dat
Loosely speaking this is a “sideload ROM” complete with META-INF