Shutdown phone (from working screen) and do not have it cabled up
Follow the recovery step (USB debug is active in /e/ already by default - at least in mine)
the key recovery step is - hold both volume buttons and plug cable in (that is connected to the machine you want to load the recovery image from)
As soon as torquiest screen shows, release hold. Press volume-up once per instructions
Do the recovery install (./Heimdall/build/bin/heimdall flash –RECOVERY <recovery img file> –no-reboot)
Do power-off with buttons vol-down+power
USB cable still plugged in, hold vol-up+power to boot - release power button and keep holding vol-up (not: release power shortly and repress …. which was my fault for the last 2w)
Download the Wifi firmware (in my case cd eos; wget ``https://github.com/Simon1511/sm7325-BL-supporter/releases/download/v1.16/blsupporter-v1.16.zip``; cd ..)
Sideload the drivers as described in the ticket (adb sideload ./eos/blsupporter-v1.16.zip)
In my case, the signature failed - as this phone is a testing device, I just accepted on the phone screen the failure and told the device to continue the load
On the phone screen, select reboot
Enter all your pins (SIM + phone in my case), connect Wifi
Be happy!
So the last bug/annoyance to tackle is the permanent visible Android menu of the 3 buttons, which I selected during /e/ configuration. Sometimes it hinders applications to show the whole screen.
Low prio - now I will focus on apps + workflows.
For the moment, I will not update to Android 15 - the comment on an A11 kernel with an A15 user land showed me, that I need to understand more about Android versioning and builds, before I can take sensible decisions.
Next stops:
Test all office apps (M365 suite mainly, so far working! - including MDM subscription to Intune, controlled by the company I work for)
Test all my hobbyist + personal finance apps (not so many - yet to start)
Find the “optimal” camera app (I heard, the Graphene one shall be nice)
Develop workflows (and probably setup a bunch of containers) how to do get the integrated experience that I have from Apple for all those years:
Phone backup
Emails via IMAP shall be simple
Calendar + Contacts sync - probably via NextCloud/Murena
Notes with syncing - probably via NextCloud/Murena
Password with syncing - probably stay with KeePass variants (KeePassium)
Photos with syncing - probably via Immich or NextCloud/Murena
VPN home (via wireguard)
My journey can finally start, I’m comfortable with flashing an Android phone now.
If time allows, I will try to understand the build process so far to attempt adding the Xiaomi 11T Pro, that is sitting fresh on my desk to LineageOS and /e/ (it was a gift - and as there are community builds of LineageOS for the phone, should be easy to get it “officially” supported - famous last words).
Once all my workflows are up and running - and all containers as well as phones have backup&restore drills done, I will hopefully take the step and switch my primary phone to /e/.
Thanks for taking the first steps of the journey with me,
@Manoj, the documentation is still confusing because of the reference to a non-existent and unneccesairy vbmeta-image.
New users are confronted with time-consuming barriers that they would not have to worry about if this part is fixed.
Can this be shared with te documentation-maintainer?
The vbmeta files are required as per the maintainers on LOS guides which we follow for devices which do not have /e/OS maintainers. The files were missing in the current build. This issue should be resolved in v3.6 build which should be coming out next week.
I’m trying to install /e/OS on my A52S 5G for the first time. I encountered the same issue as ‘lukap’: The “e-3.6-a15-20260314594305-community-a52sxq.zip” does not contatin the vbmeta.img file (as stated in instructions in Install /e/OS on a Samsung Galaxy A52s 5G - “a52sxq” ).
Reading the thread I don’t understand how to solve it and how to install it.
.