/e/ on Samsung Galaxy A5 (2017) SM-A520F ? Not at the moment!
The current problem: /e/ OS build for a5y17lte works with dev (7-nougat). Since May 2018 the SM-A520F receives StockROM Android 8.0.0 updates. The current build Android 8.0.0 A520FXXUCCSK1 is from November 2019.
Click on the .gif-link to see an eight picture animation.
Upgrades & Updatesare good thing in itself, but - Samsung has massively protected the bootloader against changes. That goes so far that after the update due to updates of the security guidelines, the old software can no longer be used (see also Biildanimation Figure #5).
● The security of your device has been improved.
●● After the update, you will no longer be able to use the old software due to security policy updates.
This makes it more difficult to switch to /e/ OS e-0.7-n- and increases the risk of a device brick.
=> Samsung A5 2017 - reboots instead of shutting down
=> Help installing /e/ on samsung Galaxy A5 (2017)
=> [UNOFFICIAL BUILD] Samsung Galaxy A5 (2017) (a5y17lte)
I know the theoretical solution (StockROM Android 8.0.0 Firmware Downgrad to Android 7.0 with its Bootloader, Modem/Baseband update, TWRP Recorvery and /e/ OS install, but is the effort worth the risk? Isn’t it better to wait until the maintainers of the /e/OS Build Team release an upgrade to /e/OS 8-Oero or even /e/OS e-9-Pie?
Switching from StockROM Android to /e/ OS requires above all uncomplicated builds with 9-pie]([UNOFFICIAL BUILD] Samsung Galaxy A5 (2017) (a5y17lte)) and 10-Q in the foreseeable future) and a well-functioning /e/ ecosystem service.
As soon as the installation of /e/OS on the Galaxy A5 ➅ 2017 is done, I will share my experiences here further.