today I tried to install the latest e.OS Version 3.01 an a Samsung A52s 5G. I used the instructions which were given at the device list at a52s…
I also used the latest original Samsung stock firmware [A528BXXSBGYC1] / SM-A528B/DBT/A528BXXSBGYC1 from 01.04.2025 as mentioned in the instructions.
“Update to latest A13/14 stock firmware” before install e.OS…
Also I noticed, that there was no ‘vmeta.img’ file in the recovery.zip, as expected. So I decided to use the vbmeta.img from LineageOS site.
After I managed to install recovery and the e.OS System, I noticed that the Wifi connection won’t turn on as expected and Wifi deactivated automatically after I short period of time.
Is the anyone who could help me on this? Maybe the maintainer of the A52s 5G at e.foundation could help me out?
I need to know which version of original stock firmware I should use to successful flash and use e.OS v.3.01 with the needed wifi function. So maybe I could use an older original firmware if samsung let me because of the rollback protection.
I think the problem occurs because of the latest Samsung Stock Firmware Update from 01.04.2025 which was probably not taken into account as the latest e.OS builds were made.
Some hours ago I managed to install the latest LineageOS 22.2 Rom and Wifi is working perfect with it.
The problem is clearly on the e.OS v.3.01 build for the A52s, I would say…
PS: I hope that this information will be taken into account when the switch to Android 15 take place soon.
I was just trying to downgrade to 2.9 from 3.0.1 because I was frustrated with this issue, It did not work because of roll-back-protection. I then looked up downgrading properly and now I think I will just wait for them to switch to Android 15, Thanks for that helpful information!
Hello!
We just installed /e/os, and had the same issue. We reinstalled 2.9, but it doesn’t find wifi networks either.
We followed this tutorial both times:
Although there was some small differences…
Does /e/os find wifi networks for y’all?
Me also … instead there was
dtbo-e-3.0.1-a14-20250607498955-community-a52sxq.img
boot-e-3.0.1-a14-20250607498955-community-a52sxq.img
vendor_boot-e-3.0.1-a14-20250607498955-community-a52sxq
Do they need to be installed?
Tried to flash dtbo-e-3.0.1-a14-20250607498955-community-a52sxq.img converted to tar with 7zip-Archive-Manager. But Oding is crashing with it. Also heimdall does not seem to work with my A52 5G
Actually I didnt install anything, but recovery.img → converted to tar with 7zip and then via abd sideload the eos.img
Installation of recovery.img via ODIN.
Hello!
We just installed, and had the same issue. We reinstalled 2.9, but there it doesn’t find wifi networks either.
We followed this tutorial both times:
I’m trying to install lineageOS 22.2 too, but I’m stuck in the part where I should install the stock rom (or else, I’m told, everything could break etc etc)… how did you install the stock ROM?
I use a linux pc, but I can’t find the files in the right format for neither heimdall nor TWRP.
I successfully installed twrp using heimdall, then elementary using twrp, and both heimdall and twrp seem, from their documentation, capable of installing an android ROM, if only I could download the stock ROM in the right format. I guess from the other thread you used odin, which does not work on linux
I wish u good luck at all and if u like, it would be very nice to tell me/us here about your forthcoming with flashing the samsung firmware stock files with linux. Maybe I also considering moving from windows to linux one day…
UPDATE: I decided to install LineageOS 22 on my Smasnug A52s 5G by just flashing the lineage rom in the /e/ os recovery screen with an Android Debug Bridge sideload, (I pressed these buttons while the phone was connected to the PC and powered off: Volume Up Power,). WiFi worked and so did everything else. (Lineage OS is a rolling release, /e/os is trying to be a stable Lineage OS). Lineage is the base of /e/os so you will get better support and documentation on Lineage OS then with a fork like /e/os. Thanks for reading this, I hope whoever is reading this will decide if waiting for /e/os to fix this issue or switching to Lineage OS is the better choice.
Thanks, Pete: I have installed elementary twice before… and I have found too much stuff. But for whatever reason I did not find this Thor that you got in your first result :-/
However, since goldfish_grub was brave enough to install lineage OS without flashing the stock rom first, I will try his method. If, later in the summer, I have more time with the device near, I will try Thor and/or Odin4Linux, and report to you/y’all, Pete
