āclean installā via /e/Recovery u-2.6.3 was uncomplicated and flawless. The reboot felt very long because the Samsung logo stood still āforeverā and a thought [ā¦] germinated. But no, I was wrong: the animated e-logo finally appeared and after the slogan āmy data is MY dataā appeared it was clear to me - /e/OS-U (A14) is running.
The icons are small due to the high screen resolution (1440 x 2960 px), but itās easy to customize them. Good preliminary work by @Ivan_Meler, thanks for building /e/ROM @ronnz98
I could not use the e-recovery e-2.7-u-20250112* in the Galaxy S8 and S8+ because the adb connection could not be established with them. With a version e-2.6.3 recovery, flawless adb connections are possible.
Unfortunatey no, I only have current /e/OS-U as build environment.
What a pity that Note 8 seems not to work, as S8 and S8+ for /e/OS have been confirmed working and using same sources from Ivan including kernel as Note 8
I havenāt mentioned it in detail, but the installation of e-2.7-u-20250112-UNOFFICIAL-dreamlte/dream2lte was a bit tricky and didnāt work straight away. I tried several times and finally I was able to āpersuadeā the devices to work.
I canāt remember the successful steps in detail. The day is long and Iāve now degoogled several other devices. However, one thing I know for sure is that I could not use /e/ recovery e-2.7-u-20250112 because the e-Recovery could not execute the adb sideload command due to lack of adb connectivity similar to Galaxy S5 (klte).
Iād like to know how to generate and create my own unofficial e/os images, and how they were generated, so that I can suggest an alternative or solve the problem by contributing. Would you have any information to share with me?
A fully functional installation of e-2.7-u-20250112-UNOFFICIAL-dreamlte.zip is possible, but with a few detours. I will carry out a new installation on a second S8 and document it step-by-step. Time will tell.
Itās not the same way to install e-2.7-u-20250112-UNOFFICIAL-dreamlte signed dev-keys by @ronnz98 as my first installation two days ago, but now I know itās the shortest way, and - that there are several ways to successfully install it.
The pivotal point is the recovery. Because the e-Recovery does not work to its full extent, I installed it first:
recovery.img from lineage-21.0-20240619-UNOFFICIAL-dreamlte.zip by @Ivan_Meler
then
lineage-21.0-20240619-UNOFFICIAL-dreamlte.zip by @Ivan_Meler (probably not absolutely necessary)
At first glance, this configuration works as it should.
A) Transferring e-2.7-u-20250112-UNOFFICIAL-dreamlte.zip by @rozz98 to a microSD card
B) Reboot into the LOS21.0 recovery
C) Factory reset > Format data + cache partition
D) Apply update > Choose from sdcard (microSD card)
D) Reboot system now
E) Wait patiently until the system has initialised.
Rejoice!
signed dev-keys 
