[ROM][OFFICIAL] LineageOS for Samsung Galaxy S5 LTE+ (G901F) / LTE-A (G906S/K/L)

dziugas1959

Member
Jan 22, 2018
8
0
0
I used multiple versions of Odin (3.14, 3.13, 3.10, 3.09) and Heimdall. I'm also unable to get stock roms to work.
When flashing TWRP with Odin, I set the TWRP image tar as AP.

I think it all happened like this:
Bought the phone second hand. Installed LineageOS 15 succesfully. As with my other S5, I followed the official LineageOS steps, but was unable to get Heimdall to work. (Possibly because of pre-installed Samsung drivers on my PC. Heimdall does work when uninstalling the Samsung drivers.) So I switched to Odin and flashed it successfully.

Some time later, when LineageOS 16 was released, I installed LineageOS 16 cleanly/freshly using the official steps, but got the same Heimdall problem again. (I didn't knew at that time that the Samsung drivers were the problem.) So I used Odin again. But the LineageOS 16 setup didn't went smoothly, I got crash reboots in the LineageOS setup and possibly later also crashes in the TWRP menu at some places. (I don't know exactly anymore.)

Now, months later, I'm attempting to try it again. I was scared to update my regular S5 (klte) because of this problem with my S5 plus (kccat6), but it went fine for my klte. But the kccat6 still has the same problem or worse, I'm unable to get into the TWRP menu anymore.

Is the phone bricked? (Download mode and flashing still work.)
Or maybe there is a hardware failure somehow?
Here is what i used (Try to follow step by step):
Enter download mode
Samsung Odin 3.12.3, Then AP twrp-3.3.1-0-kccat6.img.tar
Then boot to Recovery And in TWRP, make sure you Wipe Data Type: YES, Restart Recovery, And then using the USB cable plugged in your PC drag and drop the Official LineageOS .zip file and flash it. (Flash Opengapps aswell)
It should boot up
 

deoxy

Senior Member
Jul 29, 2011
50
4
0
Here is what i used (Try to follow step by step):
Enter download mode
Samsung Odin 3.12.3, Then AP twrp-3.3.1-0-kccat6.img.tar
Then boot to Recovery And in TWRP, make sure you Wipe Data Type: YES, Restart Recovery, And then using the USB cable plugged in your PC drag and drop the Official LineageOS .zip file and flash it. (Flash Opengapps aswell)
It should boot up
twrp-3.3.1-0-kccat6.img.tar doesn't exist anymore as an official TWRP image. They removed it, because it gave "not bootable any more" devices and "bricked phones" according to https://forum.xda-developers.com/showpost.php?p=81486609&postcount=2284 and
https://forum.xda-developers.com/showpost.php?p=81504239&postcount=2285

I don't know if I used this version in the past, causing the problem. I think the first attempt to install LineageOS was at 3 November 2019, when the problem first occured.

Anyway, I just tried that version. because the phone is already f*ked up, so there is nothing further to lose.
I downloaded Odin 3.12.3 from https://forum.xda-developers.com/showthread.php?t=2711451
And twrp-3.3.1-0-kccat6.img.tar from https://forum.xda-developers.com/showpost.php?p=81486609&postcount=2284

When selecting the tar file as "AP" in Odin, Odin immediately also asks for a BL file. I only used the AP file, as I see in other guides. After flashing successfully I immediately turn off the phone by removing batteries, and then start recovery with vol_up+home+power and release when I see "Recovery booting..." in blue text. But then the same problem occurs: the phone stays in this screen, and after about 20 seconds, the phone gives a buzz and another buzz followed by an reboot. So I'm unable to get in TWRP.

I don't know if it's useful, but here's the output of my heimdall print-pit: https://pastebin.pl/view/f67eb36a
 
Last edited:

dziugas1959

Member
Jan 22, 2018
8
0
0
twrp-3.3.1-0-kccat6.img.tar doesn't exist anymore as an official TWRP image. They removed it, because it gave "not bootable any more" devices and "bricked phones" according to https://forum.xda-developers.com/showpost.php?p=81486609&postcount=2284 and
https://forum.xda-developers.com/showpost.php?p=81504239&postcount=2285

I don't know if I used this version in the past, causing the problem. I think the first attempt to install LineageOS was at 3 November 2019, when the problem first occured.

Anyway, I just tried that version. because the phone is already f*ked up, so there is nothing further to lose.
I downloaded Odin 3.12.3 from https://forum.xda-developers.com/showthread.php?t=2711451
And twrp-3.3.1-0-kccat6.img.tar from https://forum.xda-developers.com/showpost.php?p=81486609&postcount=2284

When selecting the tar file as "AP" in Odin, Odin immediately also asks for a BL file. I only used the AP file, as I see in other guides. After flashing successfully I immediately turn off the phone by removing batteries, and then start recovery with vol_up+home+power and release when I see "Recovery booting..." in blue text. But then the same problem occurs: the phone stays in this screen, and after about 20 seconds, the phone gives a buzz and another buzz followed by an reboot. So I'm unable to get in TWRP.

I don't know if it's useful, but here's the output of my heimdall print-pit: https://pastebin.pl/view/f67eb36a
Ironicly i use 3.3.1-0 and it work's fine, back at the topic at hand, you say, that you have S5 Klte, and S5 plus Kccat6? If so, have you tried checking that the battery might be an aftermarket, and TWRP is just blocking it? That was a real issue on the stock S5 Recovery, so i recommend if the Klte and Kccat6 baterries match, then you might wanna putting it in, if it work's then you know you have a bad aftermarket battery
Edit: Suprisingly i found a video from 2019, with a S5, and one comment
"i did flashed twrp + firmware but no luck cant access recovery any other solution pls ?
Have you managed to fix?
"Youtube Username" yeah it was battery issue replace with new one and problem solve
 
Last edited:

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,322
6,211
263
tiny.cc
twrp 3.4.0 for kccat6 and lentislte

Hi all, I thought I'd give you something new to play with. I used the official TeamWin tree android-7.1 branch to build these twrps as part of this roomservice:

Code:
?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-14.1" />
  <project name="LineageOS/android_kernel_samsung_apq8084" path="kernel/samsung/apq8084" remote="github" revision="cm-14.1" />
  <project name="TeamWin/android_device_qcom_common" path="device/qcom/common" remote="github" revision="android-7.1" />
  <project name="TeamWin/android_device_samsung_kccat6" path="device/samsung/kccat6" remote="github" revision="android-7.1" />
  <project name="TeamWin/android_device_samsung_lentislte" path="device/samsung/lentislte" remote="github" revision="android-7.1" />
</manifest>
twrp-3.4.0-0-kccat6.img
twrp-3.4.0-0-kccat6.tar

twrp-3.4.0-0-lentislte.img
twrp-3.4.0-0-lentislte.tar
 

deoxy

Senior Member
Jul 29, 2011
50
4
0
Ironicly i use 3.3.1-0 and it work's fine, back at the topic at hand, you say, that you have S5 Klte, and S5 plus Kccat6? If so, have you tried checking that the battery might be an aftermarket, and TWRP is just blocking it? That was a real issue on the stock S5 Recovery, so i recommend if the Klte and Kccat6 baterries match, then you might wanna putting it in, if it work's then you know you have a bad aftermarket battery
Edit: Suprisingly i found a video from 2019, with a S5, and one comment
"i did flashed twrp + firmware but no luck cant access recovery any other solution pls ?
Have you managed to fix?
"Youtube Username" yeah it was battery issue replace with new one and problem solve
Yes, I have a S5 Klte bought newly and a second hand S5 Plus Kccat6. I have three batteries, one original from the Klte from 2014, one from the Kccat6 from 2015, and one original bought separately from 2017. All batteries have the same product number, and look identical, but with different production dates on them. I tried them all in the Kccat6.

I also just tried twrp-3.4.0-0-kccat6.tar from @ripee, but I still have the problem.
 

andreoide

Senior Member
Mar 5, 2013
1,781
264
113
Enschede
I used multiple versions of Odin (3.14, 3.13, 3.10, 3.09) and Heimdall. I'm also unable to get stock roms to work.
When flashing TWRP with Odin, I set the TWRP image tar as AP.

I think it all happened like this:
Bought the phone second hand. Installed LineageOS 15 succesfully. As with my other S5, I followed the official LineageOS steps, but was unable to get Heimdall to work. (Possibly because of pre-installed Samsung drivers on my PC. Heimdall does work when uninstalling the Samsung drivers.) So I switched to Odin and flashed it successfully.

Some time later, when LineageOS 16 was released, I installed LineageOS 16 cleanly/freshly using the official steps, but got the same Heimdall problem again. (I didn't knew at that time that the Samsung drivers were the problem.) So I used Odin again. But the LineageOS 16 setup didn't went smoothly, I got crash reboots in the LineageOS setup and possibly later also crashes in the TWRP menu at some places. (I don't know exactly anymore.)

Now, months later, I'm attempting to try it again. I was scared to update my regular S5 (klte) because of this problem with my S5 plus (kccat6), but it went fine for my klte. But the kccat6 still has the same problem or worse, I'm unable to get into the TWRP menu anymore.

Is the phone bricked? (Download mode and flashing still work.)
Or maybe there is a hardware failure somehow?
Remove the battery, there is a sticker telling you exact what model you own.
Download the right TWRP, ROM AND GAPPS
in twrp clear all and everything, flash the rom and gapps in THE SAME FLASH without rebooting ( 2 files in one flash) , than reboot, there you go :D
 

dziugas1959

Member
Jan 22, 2018
8
0
0
twrp 3.4.0 for kccat6 and lentislte

Hi all, I thought I'd give you something new to play with. I used the official TeamWin tree android-7.1 branch to build these twrps as part of this roomservice:

Code:
?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-14.1" />
  <project name="LineageOS/android_kernel_samsung_apq8084" path="kernel/samsung/apq8084" remote="github" revision="cm-14.1" />
  <project name="TeamWin/android_device_qcom_common" path="device/qcom/common" remote="github" revision="android-7.1" />
  <project name="TeamWin/android_device_samsung_kccat6" path="device/samsung/kccat6" remote="github" revision="android-7.1" />
  <project name="TeamWin/android_device_samsung_lentislte" path="device/samsung/lentislte" remote="github" revision="android-7.1" />
</manifest>
twrp-3.4.0-0-kccat6.img
twrp-3.4.0-0-kccat6.tar

twrp-3.4.0-0-lentislte.img
twrp-3.4.0-0-lentislte.tar
Very Cool! Thumbs Up for this Gem :D

---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------

Yes, I have a S5 Klte bought newly and a second hand S5 Plus Kccat6. I have three batteries, one original from the Klte from 2014, one from the Kccat6 from 2015, and one original bought separately from 2017. All batteries have the same product number, and look identical, but with different production dates on them. I tried them all in the Kccat6.

I also just tried twrp-3.4.0-0-kccat6.tar from @ripee, but I still have the problem.
Well it might be that a chip or a over-time problem happened a.k.a hardware related, my other explanation is A. You are doing something wrong that i can't see B.The phone is not a Klte and not a kccat6 Those are the only alternative explanation's if not a hardware problem
 

deoxy

Senior Member
Jul 29, 2011
50
4
0
Remove the battery, there is a sticker telling you exact what model you own.
Download the right TWRP, ROM AND GAPPS
in twrp clear all and everything, flash the rom and gapps in THE SAME FLASH without rebooting ( 2 files in one flash) , than reboot, there you go :D
The stickers says it's a SM-G901F and I flashed TWRP and LineageOS 15 for SM-G901F without problems in January 2019. Also download mode says it's a SM-G901F.
The problem is that the phone reboots before entering the TWRP menu.

Well it might be that a chip or a over-time problem happened a.k.a hardware related, my other explanation is A. You are doing something wrong that i can't see B.The phone is not a Klte and not a kccat6 Those are the only alternative explanation's if not a hardware problem
Another option could be that I bricked the software somehow in an unrecoverable state without the phone having a hardware failure? Or should download mode always be able to restore such problems?
For example, if I would repartition with a wrong PIT file, than flashing TWRP back is not enough to solve the problem, right? (I tried two pit file designed for kccat6 and also multiple stock roms for kccat6)
 

andreoide

Senior Member
Mar 5, 2013
1,781
264
113
Enschede
The stickers says it's a SM-G901F and I flashed TWRP and LineageOS 15 for SM-G901F without problems in January 2019. Also download mode says it's a SM-G901F.
The problem is that the phone reboots before entering the TWRP menu.


Another option could be that I bricked the software somehow in an unrecoverable state without the phone having a hardware failure? Or should download mode always be able to restore such problems?
For example, if I would repartition with a wrong PIT file, than flashing TWRP back is not enough to solve the problem, right? (I tried two pit file designed for kccat6 and also multiple stock roms for kccat6)
Ah... messing with pit files huh...
My guess is your troubles lie there sad enough.
There is no need almost ever to change the pit, unless you have deep insight in what you r doing....
My advice: change all pit backwards original from factory as you bought it, flash the right twrp latest for kccat from twrp.me website in Odin, flash latest working build cvxda for kccat4 and at the same time latest gapps.
Maybe after flashing twrp you try boot in twrp, if you can, clean all, than proceed in Odin
 

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,322
6,211
263
tiny.cc
The stickers says it's a SM-G901F and I flashed TWRP and LineageOS 15 for SM-G901F without problems in January 2019. Also download mode says it's a SM-G901F.
The problem is that the phone reboots before entering the TWRP menu.


Another option could be that I bricked the software somehow in an unrecoverable state without the phone having a hardware failure? Or should download mode always be able to restore such problems?
For example, if I would repartition with a wrong PIT file, than flashing TWRP back is not enough to solve the problem, right? (I tried two pit file designed for kccat6 and also multiple stock roms for kccat6)
The download mode is your lifeline. Without a hardware failure, you would need to rePIT with a proper pit file. Try extracting the PIT from a stock rom and flashing it separately from the stock from which you took the PIT that you flash. Perhaps flashing the stock in its entirety doesn't apply the PIT as it should. To be extra sure that you're flashing the right stock, be sure to download the one that matches your original CSC.

If no older twrp or cwm versions work, then that would confirm the incorrect partitioning.
 

gramouk

Member
Jan 21, 2019
31
0
0
Hi, Rom is pretty cool. So much faster than stock.
I have an issue however regarding the installation of microg. I have done it via f droid and flashing nanodroid. But I can't find the app on my phone. Some apps don't work.
Can someone point me towards the right way to get microg on this rom please.
microg requires signature spoofing, apparently this rom doesn't have this prerequisite. How can I enable that?

Thanks
 
Last edited:

andreoide

Senior Member
Mar 5, 2013
1,781
264
113
Enschede
After latest release, i also flashed the open gapps, than i face the problem Trebuchet was not available wich i use. So i twrp'd my backup back to before flashing, than only flashed the 24 sept rom update and voila, working as normal :laugh:
 

andreoide

Senior Member
Mar 5, 2013
1,781
264
113
Enschede
Hi, Rom is pretty cool. So much faster than stock.
I have an issue however regarding the installation of microg. I have done it via f droid and flashing nanodroid. But I can't find the app on my phone. Some apps don't work.
Can someone point me towards the right way to get microg on this rom please.
microg requires signature spoofing, apparently this rom doesn't have this prerequisite. How can I enable that?

Thanks
https://download.lineage.microg.org/kccat6/
If you look there, you see there is no microg for kccat lineage 17.0

Use the search option in threads may help you getting answers more quickly
 

gramouk

Member
Jan 21, 2019
31
0
0
Yeah, could install microG via magisk and edxposed but some apps (strava, tinder, insight timer...) don't work. Gonna have to go pico... screw google.

Has anyone successfully managed to install latest version 2020-09-24?

---------- Post added at 02:17 PM ---------- Previous post was at 02:00 PM ----------

twrp 3.4.0 for kccat6 and lentislte

Hi all, I thought I'd give you something new to play with. I used the official TeamWin tree android-7.1 branch to build these twrps as part of this roomservice:

Code:
?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-14.1" />
  <project name="LineageOS/android_kernel_samsung_apq8084" path="kernel/samsung/apq8084" remote="github" revision="cm-14.1" />
  <project name="TeamWin/android_device_qcom_common" path="device/qcom/common" remote="github" revision="android-7.1" />
  <project name="TeamWin/android_device_samsung_kccat6" path="device/samsung/kccat6" remote="github" revision="android-7.1" />
  <project name="TeamWin/android_device_samsung_lentislte" path="device/samsung/lentislte" remote="github" revision="android-7.1" />
</manifest>
twrp-3.4.0-0-kccat6.img
twrp-3.4.0-0-kccat6.tar

twrp-3.4.0-0-lentislte.img
twrp-3.4.0-0-lentislte.tar

I can't DL the tar image...?
 
Last edited:

maanteel

Senior Member
Apr 19, 2015
66
27
38
Thank you @ripee ,
TWRP sucessfully updated from 3.3.1 to 3.4.0

Just installed the .img file in TWRP as Image in the Recovery Partition.

---------- Post added at 22:38 ---------- Previous post was at 22:25 ----------

I can't DL the tar image...?
Maybe an other or 2 other web browsers help to download from Google drive the .tar file instead of a .bin.
 
Last edited:

gramouk

Member
Jan 21, 2019
31
0
0
@gramouk, I just downloaded both .tar files from the very links I posted. Can you please explain what download problem you are experiencing?
Yeah all good sorry, didn't see the tiny download icon on top... I was just clicking away on the file name. Not a google fan as I said lol
Cheers

So any success stories concerning latest nightly?
 

gramouk

Member
Jan 21, 2019
31
0
0
I have a code error 64 when flashing gapps in TWRP.

I am using open_gapps-arm64-9.0-pico-20200930 and latest TWRP posted here.

Help please :crying:
 

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,322
6,211
263
tiny.cc
In other news, I'm not sure how much time Corinna has to focus on Q and beyond for kccat6 and lentislte, but I am in the middle of fixing up a few remaining bugs on trlte, which uses the same apq8084 kernel that she is working on. When (and more importantly if) I fix what's left, I will apply the same commits to the lentislte-common sources, and hopefully give you guys a useable Q build.

But no promises...
@gramouk, you need to download the "arm" open gapps, not "arm64". The chipset for your phone is 32-, not 64-bit.
 

gramouk

Member
Jan 21, 2019
31
0
0
I have a code error 64 when flashing gapps in TWRP.

I am using open_gapps-arm64-9.0-pico-20200930 and latest TWRP posted here.

Help please :crying:
Thanks mate, saving my life. Sometimes I surprise myself at being such a noob :p

Ok everything worked fine, but now I can't access the content of my phone via my PC, I can only read the SD card... this is starting to get on my nerves
Can't even access my files from within the phone...
 
Last edited: