[UNOFFICIAL BUILD] Samsung Galaxy S 5 LTE (klte) for /e/OS-T

[ronnz98]

Samsung Galaxy S 5 LTE (klte) for /e/OS-T-1.16.1
Using also lineage-UL sources. Untested!
This build took me some hours to built. I don’t think I will do this even again. If someone is interested on taking this over I can write a how-to (Only if the ROM boots and works…)

e-1.16.1-t-20231104-UNOFFICIAL-klte.zip
https://www.androidfilehost.com/?fid=16385555061192796987

Please see sources and install instructions including recovery here:
https://xdaforums.com/t/unofficial-lineageos-20-0-android-13.4498857/

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

[make-nz]

UNOFFICIAL BUILDS OVERVIEW built by me

Sadly, no boot From TWRP and SD it does install, but then goes into ODIN mode, no more recovery either then. Did this twice, same result. Then flashed TWRP again and installing this: Worked well, so I rebooted into recovery from there and tried your ROM as a dirty install, but again, it only went into ODIN mode. Thanks anyway, maybe Mr. Sandman brings you an idea over night

[Xxpsilon]

@ronnz98

Samsung Galaxy S 5 LTE (klte) for /e/OS-T-1.16.1
e-1.16.1-t-20231104-UNOFFICIAL-klte.zip

/e/ ROM e-1.16.1-t-20231104-UNOFFICIAL-klte.zip
/e/ Recovery e-1.16.1-t-20231104-UNOFFICIAL-klte
Both images can be installed, but do not boot.

/e/ ROM e-1.16.1-t-20231104-UNOFFICIAL-klte.zip
TWRP recovery: twrp-3.7.0_9-0-klte.img.tar
TWRP cancels the installation of @ronnz98 ROM with error message ‘1’
LOS 18.1 ‘official’ recovery cancels installation of @ronnz98 ROM

---

---

/e/OS-R ‘official’ e-1.16-r-20231020343335-dev-klte.zip
/e/OS-R ‘official’ recovery-e-1.16-r-20231020343335-dev-klte.img

LOS 18.1 ‘official’ lineage-18.1-20231102-nightly-klte-signed.zip
LOS 18.1 ‘official’ recovery-lineage-18.1-20231102-nightly-klte-signed.img

LineageOS-18.1-for-microG ‘official’ lineage-18.1-20230918-microG-klte.zip
LOS-18.1-for-microG ‘official’ lineage-18.1-20231018-microG-klte-recovery.img

crDroid ‘official’ crDroidAndroid-11.0-20231017-klte-v7.35.zip
TWRP recovery: twrp-3.7.0_9-0-klte.img.tar

[ronnz98]

Thanks for your feedbacks! I just saw that there are updated sources available for the klte. I will try a last build as well as an /e/OS-S build

[ronnz98]

e-1.16-s-20231105-UNOFFICIAL-klte.zip
https://www.androidfilehost.com/?fid=16385555061192796988

Who want to try?

[ronnz98]

One final try for /e/OS-T

I sorted out the errors with I commented out in the first try and used the updated sources…

e-1.16.1-t-20231105-UNOFFICIAL-klte.zip
https://share.jaguar-network.com/6133d44b-9c2b-4002-8a16-1e0817e02112

[Xxpsilon]

/e/ ROM e-1.16.1-t-20231105-UNOFFICIAL-klte_by_ronnz98.zip
TWRP 3.7.0_9-0-klte.img.tar
Both images can be installed, but after the reboot the e-System does not start, it starts in Samsung ‘Downlaod mode’

/e/ ROM: e-1.16.1-t-20231105-UNOFFICIAL-klte_by_ronnz98.zip
/e/ Recovery: e-1.16.1-t-20231105-UNOFFICIAL does not start; the system gets stuck in the ‘Samsung Galaxy S5’ logo.
@ronnz98 ROM can be installed because the e_recovery does not work.

Thank you for your time,@ronnz98

[make-nz]

@Xxpsilon

Both images can be installed, but after the reboot the e-System does not start, it starts in Samsung ‘Downlaod mode’

Sorry, have to confirm for T, but have not testet S: e-1.16-s-20231105-UNOFFICIAL-klte.zip

[ronnz98]

Ok. So I give up building for T. Did someone try the S version in the meanwhile?

[make-nz]

S gets stuck here, but TWRP is still ok!	A hint? Recovery Size too large?	My TWRP version

|

|

|

|

I took the lineage-20.0-Recovery-2023-04-18-klte.img from XDA and could not flash it in ODIN, after I converteded it to .tar.

Tried in TWRP as .img and got the above error.

[ronnz98]

Found something very interesting about S5 klte boot behavior:
https://xdaforums.com/t/unofficial-lineageos-19-1-android-12l.4427639/
Interesting comments are #9 and #11

Furthermore, can you try to extract recovery.img from latest Lineage build for klte here:
https://sourceforge.net/projects/khalvat/

You used LOS20 recovery for LOS19.1 build- that might also be an issue

[ronnz98]

https://sourceforge.net/projects/khalvat/files/Android%2013/klte/
There is also a recovery here, maybe worth to try?

[make-nz]

@ronnz98

https://sourceforge.net/projects/khalvat/files/Android%2013/klte/
There is also a recovery here

This is what I took – meant from XDA-Dev

@make-nz

I took the lineage-20.0-Recovery-2023-04-18-klte.img

And about those comments, first I thought "a bit too close to April 1. "
But also, it is stuck at a boot-loop in this case

@ronnz98

extract recovery.img from latest Lineage build for klte here:
https://sourceforge.net/projects/khalvat/

Did that, now I goes into ODINmode again, no working recovery left — like in T

@ronnz98

You used LOS20 recovery for LOS19.1

No, I used TWRP. Allways went back to same version.

As a test I’ll download his LOS19.1 and see how it goes and what recovery is in it.

Stay tuned…

[make-nz]

@make-nz

As a test I’ll download his LOS19.1 and see how it goes and what recovery is in it.

Stay tuned…

Within my usual TWRP => flashed LOS-19.1recovery => S: e-1.16-s-20231105-UNOFFICIAL-klte.zip

Results in:

@make-nz

stuck at a boot-loop in

Side note:
From my usual TWRP, I could install, boot configure the XDA-Dev:
lineage-19.1-20231009-UNOFFICIAL-klte.zip

Anything else I can do for those fellows, in my red box

[piero]

When building, recovery is available here :
"/out/target/product/<devicecodename>/recovery.img"

[ronnz98]

yes but also in the ZIP file

[piero]

it should be well named and available aside the “e.ZIP” file in the "/.e/zips/<devicecodename>/" folder,
but it is deap inside the “e.ZIP” … (encripted into “system.new.dat.br”) isn’t it ?

[ronnz98]

Yes, true for Q and R. But S and T has it in the ZIP