[Galaxy A52 4G] vbmeta disapear (again) from /e/OS build downloads page

Hi folks,

It looks like the build process missed again to package the vbmeta.img for the recovery download.

https://images.ecloud.global/community/a52q/

Somehow similarly to this bug from last year but a bit differently because here we have a .img instead of a .zip for version 2.6

Any clue maybe @Manoj ?

1 Like

In lieu of “documentation” we do have [Walkthrough] Extract eRecovery and boot images using payload-dumper-go … but maybe in this case you have to extract from the ROM itself.

As you speculate, not really useful here:

./payload-dumper-go -o OutputFolder -p dtbo,vbmeta,recovery e-2.6.3-u-20241217455570-community-a52q.zip 
Please wait while extracting payload.bin from the archive.
2024/12/24 21:27:07 Failed to extract payload.bin from the archive.

Do you have any other resource to extract it from the ROM?

Anyway, the problem of the “broken” build and should still be fixed, noop?

You can use the older one.

Sorry

So the command would probably work as

./payload-dumper-go

followed by

e-2.6.3-u-20241217455570-community-a52q.zip

which would give

./payload-dumper-go e-2.6.3-u-20241217455570-community-a52q.zip

@piero
It looks like the signature is not recognized then and prevent Version 2.6.3 to boot correctly. I tried:

@aibd

./payload-dumper-go e-2.6.3-u-20241217455570-community-a52q.zip

Please wait while extracting payload.bin from the archive.
2024/12/24 21:54:58 Failed to extract payload.bin from the archive.

Respectively after a consecutive factory reset I still get this message (see below), but was expecting the vbmeta to get rid of it, or I’m mistaking?

OK … so are you trying to install or upgrade ?

The method at LineageOS seems “different”

https://wiki.lineageos.org/devices/a52q/install/

https://wiki.lineageos.org/devices/a52q/upgrade/

I’m trying to install and yep I followed also Lineage’s instructions so far.

I think that the Lineage vbmeta.img will work to do this job … maybe the build process does not produce this “item” this time, idk.

Thanks guys, I did “a bit” of overkill and used a Magisk patched one before realizing the combination with Lineage could do the job.

Looking forward to seeing vbmeta.img again in compiled ZIP from /e/OS to avoid others to spend a lot of time searching for inconsistency in documentation.