…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,
how can I install eOS on Samsung Galaxy A52s 5G using Linux? is there are replacement for Odin? You have instructions to install adb on Linux but not how to install flash and install eOS?
Hello @lukap, welcome to this forum.
you have the choice about Linux flashing-tools for Samsung devices
thank you.
I will try to use one of these methods for flashing. ALs the HowTO helps as it seems it outlines the main steps of installing the eOS (or probably any custom ROM) to a phone. That’s helpful for first-time installing a different os on the phone.
1 Like
I think downloads in /e/OS community a52sxq download do not contain vbmeta.img file (as stated in instructions in Install /e/OS on a Samsung Galaxy A52s 5G - “a52sxq”).
1 Like
you have two options :
- take those from lineageos
- extract them from the /e/ build
that’s what i’m saying, they are not in the zip of the build. vbmeta.img is not in the /e/ build zip
@manoj, why are these files provided, when the instructions talk about vbmeta.img ?
I wrote notes, allow me to share them here:
prep tools and files
you need 4 things: adb, heimdall (flasher), eOS recovery, eOS system
- adb from Android Developer Tools (SDK Platform Tools release notes | Android Studio | Android Developers) for Linux
- heimdall 2.1 from Grimler ~grimler/Heimdall - Heimdall is a cross-platform open-source tool suite used to flash firmware (aka ROMs) onto Samsung Galaxy devices. - sourcehut git
- /e/OS recovery & /e/OS system builds available from /e/OS community a52sxq download
unlock bootloader
prep the phone to be able to “be hacked”
- in settings > About Phone > Software Information, tap mutiple times on Build number to turn Developer mode on.
- Developer options are now available in main settings. There turn OEM unlocking on and USB debugging too
- turn the phone completely off (hold power button and volume-down for longer, and then choose power off on screen), disconnect USB cable from phone, and -THIS IS IMPORTANT TO DO CORRECTLY- while holding both volume buttons (up and down), CONNECT USB CABLE back to the phone (it will boot) - and keep holding volume buttons until the black screen turns to turquose
- as instructed on screen, unlock the bootloader with holding volume-up button for a bit longer
- (NOT SURE ABOUT THIS STEP BEING NECESSARY: reboot the phone. it will probably ask you all the basic questions again (for installing user etc) - you can safely skip everything as possible. check in settings under OEM unlocking - it should say “booloader already unlocked”)
flash the recovery
change the tool within which phone can get a new operating system
- turn off the phone (holding power+vol-down) and get back to turquise screen with holding both volume buttons and inserting usb cable. this time shortly press volume up to enter ‘download’ mode
- unzip e/OS recovery zip
- use heimdall to flash recovery with something like:
heimdall flash --RECOVERY recovery-e-2.7-u-20250109460550-community-a52sxq.img --no-reboot - power off with buttons vol-down+power
- after flashing the recovery YOU MUST NOT BOOT BACK TO SYSTEM BUT TO RECOVERY!
boot to recovery and install (sideload) system
- hold vol-up+power to turn it on. the system will bother you with unofficial sofware, release power button and keep holding vol-up until you are greeted with big e in the new recovery.
Use vol-up and vol-down to navigate and power buttons to confirm: - Select Factory reset and then Format Data / Factory reset. confirm again.
- Select Format Data
Return to the main menu by going further up from the menu to arrow pointing left(back). - Select Apply update, and Apply update from adb. - you’ll enter sideload mode.
- sideload the e/OS with something like:
./adb sideload ../a52sxq/e-2.7-u-20250109460550-community-a52sxq.zip - It will now start the transfer. Wait. It will pause at 47%
- The phone said that it failed to verify signature. I confirmed patching anyway.
- Phone reported script succeeded: result was [1.000000]
- computer terminal reported Total xfer: 1.00x
Rebooting should take you to fresh install of e/OS!
1 Like
What is the difference between ‘recommened’ and ‘prefered’ ?
- from a Terminal on the Computer, using the adb sideload recommended method
or - from the Recovery-manager on the Device, using the SDcard or internal storage preferred method
Do I miss the word ‘or’ between Odin.3 and Galaxy-Flasher Linux?
Like the next arrow (see common steps for all other devices (adb&fastboot) contains 3 sub items:
-windows (Me 
)
-MacOS
-Linux
If you are not confortable with command lines (most Windobe users) you would prefer to use Grafic tools
and only need Odin3 for windows (adb not needed, fastboot not usefull on Samsung devices)
1 Like
You can convert the recovery.img to .TAR using “7zip”
I am (a bit) ok with command lines using CommandPrompt for simple excutions (renaming folders or extracting stuff from files, etc)
1 Like
So you also can use the adb sideload method
or get the twrp-3.7.1_12-0-a52sxq.img.tar from the link in step 4?
1 Like
but that is step 8/9. I’m only at step 6…
this is useful for windows as well? I only have to adept the heimdall steps ot odin?
1 Like
Yes, I think the main difference is in the tool used for flashing. as far as I know, heimdall is only for linux, so you need to find another tool that works well on Linux - I have no experience with Windows, sorry.
Hello,
I managed to install eOS on Samsung Galaxy A52s 5G using Heimdall on a mac. After many hours I concluded that for some reason Odin3 on Windows didn’t work in my situation.
What I do not exactly understand is that the eos recovery image (zipfile) contains 4 files with .img extension, but only one (recovery-e-2.8-a14-20250220470208-community-a52sxq.img) is needed to flash the new recovery system on the Samsung. Are the others not necessary? Or are they also sideloaded later?