…Enter suggestions to improve documentation in this category. Do not raise bugs or issues here…
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
Hi !
I’m trying to install e/os on a S7 tab LTE. But following the Pre-Install Instructions (3.), after extracting the contents of the /e/OS build zip file, the mentionned file vbmeta.img doesn’t seem to exist.
Thanks in advance for your help
1 Like
Hello @ccc, Welcome to the /e/ users forum.
There are incoherences for some devices between instructions and provided files…
- Have a look into the main .ZIP
or
- Take the one from lineage
1 Like
Hi!
On the download page /e/OS community gts7l download there are three different builds.
But none of their timestamps match to them on the lineageOS-Page.
Which vbmeta.img is the right to use?
Can you give me a hint, please?
Best regards!
Hello @DSPX, Welcome to the /e/ users forum.
they are all the same, to be super safe take one related to android version…
1 Like
Then I wonder why their sha256 hashes differ. 
Can you explain me why that is?
sha256 hashes are related to the differents /e/ builds .ZIP,
not to vbmeta.img
. . .
(LineageOS 23.2 is based on AOSP 16)
because of their creation date…
I’m sorry for being so slow on the uptake. But I was referring to the hash values of the vbmeta.img files for each version.
These have different hash values, so they can’t be identical. I thought they were supposed to contain the checksums for the respective img files of the image.
There should be a corresponding vbmeta.img file for each build that includes a boot.img, dbto.img, and recovery.img.
I’m sorry for being so persistent, but I’m a bit afraid of bricking my tablet.
samsung devices are quite unbrickable
in any case you can restore back the Official Samsung software (thanks to the leacked tools long time ago)
not all these files are needed for all devices…
I’m glad to hear that.
But I still do not understand why there isn’t a specific vbmeta.img-File in the .zip-File. 
it is a mistake (an oversight) in configuration of the build script for this device,
that is then launched automatically each month on the /e/ build infrastucture
(for the set of 287 supported devices).
what are the possible OSes to run on your PCs ?