Hello,
I want to install the Android 14 version of e/OS on my A52 4G and whatever versions are available in the download directory https://images.ecloud.global/dev/a52q/, none of them provide the vbmeta.img file in the zip file. Any advice on how to proceed?
Thanks in advance.
First, there was no vbmeta.img in the package, so as adviced by Xxpsilon (thanks to him) I downloaded and used the one here : lineage-21.0-20250101-microG-a52q-vbmeta.img as /e/OS-U (A14) is based on LineageOS 21.1 (A14).
So, I flashed the latest official Samsung ROM and flashed Vbmeta.tar with Odin.
I tried to flash the recovery recovery-e-2.8-a14-20250220470208-community-a52q.img with Odin too but it failed. Odin crashed each time. Then I decided to flash the latest TWRP recovery for the A52 4G with Odin and everything went fine.
Last step, flashing e-2.8 version.
I tried through the installation through « Apply update from SD card » or through adb with the adb sideload command and each time, it doesn’t work.
In both cases, TWRP messages are :
Supported API : 3
Finding update package…
Verifying update package…
Update package verification took 28.5 s (result 1).
Install completed with status 2.
Installation aborted.
I went in the logs and found messages like this :
I Failed to verify against RSA key 0
E failed to verify whole file signature
E Signature verification failed
E Error 21
I checked the sha256 of the downloaded e-2.8-a14-20250220470208-community-a52q.zip and it’s correct.
Does anyone had the same issue ? Any advice to complete the installation ?
Thanks, It seems I need to go in Settings to do so but I don’t have the User interface. After the installation here is what I got when I reboot into recovery
How do I do to disable the zip signature ?
@Halwa maybe the /e/OS-U biuid is faulty! I would first try to install the official and stable CustomROM LineageOS 21.0-for-microG. That would be a good starting point to then try to install /e/OS.
That’s an option indeed but I assume I’m not the only one willing to install e/OS-U build. So if it was really faulty, It would probably be mentionned in the forum.