[UNOFFICIAL BUILD] Samsung Galaxy A5 (a5y17lte) and A7 (a7y17lte) 2017 for /e/OS-T 3.x

/e/OS Devices UnOfficial Builds
1

Samsung Galaxy A5 (a5y17lte) and A7 (a7y17lte) 2017 for /e/OS-T 3.2

Well, another try. This time I think I applied all the patches correctly - though still no guarantee that it boots!

e-3.2-t-20251112-UNOFFICIAL-a5y17lte.zip
https://sourceforge.net/projects/eosbuildsronnz98/files/Samsung/Samsung%20Galaxy%20A3%20A5%20A7/e-3.2-t-20251112-UNOFFICIAL-a5y17lte.zip/download

e-3.2-t-20251113-UNOFFICIAL-a7y17lte.zip
https://sourceforge.net/projects/eosbuildsronnz98/files/Samsung/Samsung%20Galaxy%20A3%20A5%20A7/e-3.2-t-20251113-UNOFFICIAL-a7y17lte.zip/download

Please see sources and install instructions including recovery here:
https://xdaforums.com/t/rom-a5-7-2017-12-13-14-lineageos-19-1-20-21-unofficial.4517749/

Use it at your own risk!
Please support the developer(s)!

2

Hello
I’m sorry, it still isn’t working. I have an A5Y17LTE running /e/ 3.0.4-s.
I installed TWRP 3.7.0_9 using the command:./odin4 -a twrp-3.7.0_9-0-a5y17lte.img.tar

Immediately after (Upload Binaries → recovery.img → Close Connection)
I press the HOME+UP+POWER buttons to enter TWRP recovery mode

I select [Advanced] [SideADB] and then run the command: adb sideload e-3.0.4-s-20250716-UNOFFICIAL-a5y17lte.zip

The phone reboots but gets blocked on the GALAXY A5 logo.

I rolled back to the previous version 3.0.4-s used the same procedure/
If you compile a new version, I’m ready to test it.
Best regards

3

why not using the already installed recovery-e ?
(TWRP can’t manage encrypted /data partition)

4

I first tried e-recovery and got the same result: it froze on the Galaxy A5 logo.
When I tested TWRP, I just wanted to make sure it wasn’t simply because of e-recovery.
I wanted to be sure by following the procedure recommended by @ronnz98

5

Hello @ronnz98

I use your e-3.2-t-20251112-UNOFFICIAL-a5y17lte.zip to build a new version and I use too this documentation : How to Build the /e/OS ROM?

Of course my first build crash :slight_smile: /e/os Don’t have a product spec for: 'lineage_a5y17lte

I suppose, missing “Extracting proprietary blobs from block-based OTAs” ? I use the documentation : Extracting proprietary blobs to extract system.transfer.list and system.new.dat.brof your e-3.2-t-20251112-UNOFFICIAL-a5y17lte.zip @ronnz98.

But i stopped to the step : “After you have mounted the image(s), move to the root directory of the sources of your device and run extract-files.sh as follows”

./extract-files.sh ~/android/system_dump/

The problem, i don’t have extract-files.sh anywhere ?

What am I doing wrong? Does the error in the build log explain the absence of the blobs ?

Thanks

6

it is supposed to be into /device/samsung/a5y7lte/

7

Thanks @piero

Second build OK (BRANCH_NAME=v2.2-r" -e “DEVICE_LIST=a5xellte”) :partying_face:

!! I use exactly the documentation How to Build the /e/OS ROM? without Extracting proprietary blobs !!

For fun, i try a build of a5xelte v2.2-s but it crashed…of course

So now, i try to build with your help @piero @ronnz98 a version for LineageOS 19.1 that not support by /e/os exemple 2.2-s: Howto: Unofficial Builds using repo style for supported lineageOS devices that are not (yet) supported by /e/OS

Thanks, see you soon

8

As far as i know, android 12 and 13 based /e/ “S” and “T” branch are still maintained,
so if you find LineageOS 19.1 or 20 based _device_ and _kernel_ sources, you can try to build v1-s or v1-t that should result in e-3.7.2-s or e-3.7.2-t

10

Building this is not trivial, you need to look at the sources:

https://xdaforums.com/t/rom-a5-7-2017-12-13-14-lineageos-19-1-20-21-unofficial.4517749/

For A12 please look here:

For A13 please look here:

As far as I remember the A12 build did work but A13 not.

Extracting vendor files should be pretty easy, you need to run ./extract-files.sh ROMNAME

Replace ROMNAME with the actual ROM you are downloading, I would suggest to download from original sources by

Taking the lasted official LineageOS sources you can build only up to A11 (LOS18)

You can even try A14 ROM:

Since latest Kernel is 3.x for this device you will need to apply some patches that support older 3.x kernel for A12 onward, but they should be included in the compiling instructions

1 Like