Hello.
Unfortunately, I fear there’s a problem within the file “e-2.6.3-u-20241217455570-community-a52sxq.zip”, available at this link “/e/OS community a52sxq download”. More precisely, at the time of writing this report, the file “vbmeta.img” is not present within the ZIP file mentioned above. Thank’s for your kind attention.
Hi @kob welcome to the /e/ forum.
Although a different device this thread explores the same subject [Galaxy A52 4G] vbmeta disapear (again) from /e/OS build downloads page.
Nor do I find vbmeta.img
in the extracted recovery-IMG-e-2.6.3-u-20241217455570-community-a52sxq
~/TEST-a52sqx/recovery-IMG-e-2.6.3-u-20241217455570-community-a52sxq$ ls
boot-e-2.6.3-u-20241217455570-community-a52sxq.img
boot-e-2.6.3-u-20241217455570-community-a52sxq.img.sha256sum
dtbo-e-2.6.3-u-20241217455570-community-a52sxq.img
dtbo-e-2.6.3-u-20241217455570-community-a52sxq.img.sha256sum
recovery-e-2.6.3-u-20241217455570-community-a52sxq.img
recovery-e-2.6.3-u-20241217455570-community-a52sxq.img.sha256sum
vendor_boot-e-2.6.3-u-20241217455570-community-a52sxq.img
vendor_boot-e-2.6.3-u-20241217455570-community-a52sxq.img.sha256sum
You might “borrow” a vbmeta.img from a Lineage-21 build … download.lineageos.org/devices/a52sxq/builds.
Thanks lot aibd.
You are right, “vbmeta.img” is missed in the RECOVERY too: I’m not too sure, but I assume it’s because “vbmeta.img” is only needed for installation and not for recovery or upgrades.
“Borrow” the file from LineageOS? … I prefer wait for the build to be properly updated.
Thanks again and best regards!
there two hypothetics :
- the vbmeta.img is not needed
- you should take the one from lineage as they are the same
The build itself may not produce vbmeta.img
as I speculated on the other thread.
If it is required, this is a “packaging issue” which seems to have been forgotten / omitted. Perhaps a case for Report an issue.
Thanks Piero for the reply.
I think “vbmeta.img” is essential because, according the instructions in the guide, it’s the file that starts the installation procedure. I’m also convinced “vbmeta.img” from LineageOS can work, but, as I’ve already written, I prefer to wait for a new eOS build complete with all the components.
Best regards!
Good suggestion aibd.
I’ll try to report the “package problem” at the link you posted.
Thanks and best regards.
I have informed the build team about this. Will update when I get a response from them.
Thanks Manoj!
Best regards.
I installed this e/OS build (v2.6.3) on an A52sxq and it worked without any issues. So I assume its not needed. Just had to do a factory reset after flashing e/OS recovery. This phone had the stock ROM installed previously.
The build team has made changes to their script and the vbmeta.img should be back in the build image starting from v2.8 as v2.7 is already under testing.
Thanks @Mr.V.
Thanks @Manoj.
So the matter is now fully clear.
Best regards and thanks to all folks!
Hi Manoj, the problem with the missing vbmeta.img is also there in the image v2.7 for the A72q.
Is there also an information, that it will come again back with the v2.8?
Best regards and thanks also to all folks!
According to some users experiences, it appears that vbmeta.img is not needed for this phone series.
The LineageOS Android distribution offers, e.g., the download of vbmeta.img
Thanks a lot. I will try it with the link for the a72.
Best regards.
(-;
This topic was automatically closed after 30 days. New replies are no longer allowed.