…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
Camera problem, only one back camera can be used
I tried to follow the r8q documentation, but the vbmeta.img file was not included in the zip file to download: e-3.4-a15-20260115569564-community-r8q.zip
Hello @takuu, Welcome to the /e/ users forum.
This is not the only device concerned..
please try without (no risk other than not be able to) and share feedback here.
1 Like
Hello when trying to boot into recovery mode, it is necessary to keep the USB cable connected and press the buttons when the phone restarts, maybe you can mention that, would have saved me a lot of time 
Does the official firmware for Samsung S20 FE (r8q) allow executing ADB commands with root privileges? Will it be possible to run:
pm disable <package.name> ?
Hello @odin, Welcome to the /e/ users forum.
there is no “official” build for this device but “community” that allow executing ADB commands with root privileges
pm disable <package.name>
Thank you for reply!
And for the good staff too)
I tried to flash my device, I assume its not working without flashing vbmeta.tar. and I can not find it
Steps:
- unlocked the bookloader (/)
- downloaded the recovery image (/)
- tried to flash the recovery image with heimdall (linux alternative to Odin) as I do not have Windows Computer available
- back in recovery mode, it still looks like the stock one
heimdall output:
heimdall flash --RECOVERY recovery.img --no-reboot
Heimdall v2.1.0
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna https://glassechidna.com.au
Copyright (c) 2021-2024 Henrik Grimler
This software is provided free of charge. Copying and redistribution is encouraged.
Initialising connection...
Detecting device...
Claiming interface...
Initialising protocol...
Resetting device...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
So ether I fail to cleanly return to recovery mode (can exit download only via reboot) or falshing recovery doesn’t work, even it tells me success…
Any idea what I could possibly done better. (except using Odin, thats not an option)
Hello @devivan, Welcome to the /e/ users forum.
If missing, take the vbmeta.img file from lineage LineageOS Downloads
1 Like
Are you already familiar with the Samsung technique to First boot into recovery?
what I tried:
- flash with vbmeta from lineagoe and flash recovery from /e/os
- flash with vbmeta from lineagoe and flash recovery from lineageOS
Does not matter what I try, recovey interface looks same (StockOS one), and sideloading results in Signature verification failed
Now My guess is: heimdall does not work properly, since lineagOS stuff also not working
commands used:
# flash vbmeta.img:
$ heimdall flash --VBMETA vbmeta.img
Heimdall v2.1.0
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna https://glassechidna.com.au
Copyright (c) 2021-2024 Henrik Grimler
This software is provided free of charge. Copying and redistribution is encouraged.
Initialising connection...
Detecting device...
Claiming interface...
Initialising protocol...
Resetting device...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading VBMETA
100%
VBMETA upload successful
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
# flash recovery:
$ heimdall flash --RECOVERY recovery.img
Heimdall v2.1.0
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna https://glassechidna.com.au
Copyright (c) 2021-2024 Henrik Grimler
This software is provided free of charge. Copying and redistribution is encouraged.
Initialising connection...
Detecting device...
Claiming interface...
Initialising protocol...
Resetting device...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
I did it
After several attempts I noticed while flashing in download mode a red hint: Only official released binaries are allowed to be flashed (vbmeta)
I investigated how this can be resolved and found a [youtube video](https://www.youtube.com/watch?v=Wk1UCLMDH18)
tldr: after unlocking the bootloader, which cause to wipe your system, boot to stock os again, enable developer mode, connect to wifi and ensure that oem unlock option is visible, even its disabled, because bootloader already unlocked. it its there and switched on, you are good to go
- reboot to download:
adb reboot download - flash vbmeta from lineageOS:
$ heimdall flash --VBMETA vbmeta.img --no-reboot
Heimdall v2.1.0
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna https://glassechidna.com.au
Copyright (c) 2021-2024 Henrik Grimler
This software is provided free of charge. Copying and redistribution is encouraged.
Initialising connection...
Detecting device...
Claiming interface...
Initialising protocol...
Resetting device...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading VBMETA
100%
VBMETA upload successful
Ending session...
Rebooting device...
Releasing device interface...
- flash recovery from lineageOS:
$ heimdall flash --RECOVERY recovery.img --no-reboot
Heimdall v2.1.0
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna https://glassechidna.com.au
Copyright (c) 2021-2024 Henrik Grimler
This software is provided free of charge. Copying and redistribution is encouraged.
Initialising connection...
Detecting device...
Claiming interface...
Initialising protocol...
Resetting device...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Releasing device interface...
- switch safely to recovery mode
- select update, download from ADB
- run sideload, wait:
$ adb sideload e-3.6-a16-20260318595986-community-r8q.zip
Total xfer: 1.00x
- reboot, wipe / factory reset if fails to boot
- enjoy
TIL:
- read the steps carefully, do all of them, even they seem to be redundant
- heimdall works fine
The only question Left: is relocking bootloader supported on /e/os community builds?
Hi All,
First of all; amazing work your doing!
I just wanted to say I managed to install E/OS on my G781B using this vbmeta: https://github.com/ata-kaner/r8q_archive/releases/download/vbmeta/vbmeta_patched_G781B.tar
and for the rest I just followed the install instructions.
Everything seems to work so far, but it’s early days.
Here in Spain it seems 2G will be around until 20230, so I’m not too worried about VoLTE yet.
update: I couldn’t get Curve to work and there is a weird issue with the screen brightness going to completely dark so it’s unusable.