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

Search This thread


Jan 22, 2018
This is either good or bad, situation
A. Good* We finally getting 17.1
B. Bad* The device is no longer supported, which would be sad............
  • Like
Reactions: maanteel


Jan 22, 2018


but I have hope

I also have hope, that they will re-add, the kccat6 back in the official update fold, since abandoning it, would not only make 0 sense, the S5 Family is in the TOP 5 most used LineageOS Devices


Senior Member
Jan 28, 2017
Small town in Bavaria
I also have hope, that they will re-add, the kccat6 back in the official update fold, since abandoning it, would not only make 0 sense, the S5 Family is in the TOP 5 most used LineageOS Devices
Don't mix S5 and S5 plus. S5 has really high user count.
I expect one of the 2000 active users will step in and build unofficial lineageOS 16.0 with updated security patches.


Senior Member
Sep 17, 2015
Those EOL threads are typically used for unofficial builds.
sadly LOS 16.0 for the kccat6 wasnt as good as the LOS 15.1 build. Battery drain became a big issue when i used to have my s5+ as my main phone. switched 2 years to a xiaomi phone.
The Galaxy S5 G900F community is big but for our phone its dead

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Although I mentioned 17.1 in the last year, I'm busy with work in fighting the pandemic :p For now I am willing to run 16.0 builds for kccat6 and lentislte with future security updates, if you guys want, but they would not be signed by Lineage so you would have to clean flash them.
    twrp-3.5.2_9-0-kccat6 is in my Google Drive. lentislte was built officially.
    Hello ,
    i have twrp 3.2.3-0 and lineage-16.0-20210211-nightly-kccat6-signed and installed ripee lineage-16.0-20210414-UNOFFICIAL-kccat6
    over it without factory reset and it booted fine for me


    Build 0413 for kccat6 and lentislte in my Google Drive linked in my signature.
    * April 5, 2021, Android security patch level.
    * Synced with LineageOS sources.
    Where are we at in point of future and history?
    Is it still maintained or do I read right, lineage stop maintenance for our beloved S5Plus kccat6?
    Im asking because I'm confused like Confucius was a few years ago 💀 😳 🤔
    For people without GApps there is a route to updates without wiping
  • 83

    LineageOS for Samsung Galaxy S5 LTE+ / LTE-A

    - Your warrenty is now void.
    - You [b]WILL[/b] trip KNOX!
    - You have been warned.
    - Use at your own risk.

    This is the thread for the offical port of LineageOS to
    • Samsung Galaxy S5 LTE+, SM-G901F, codename kccat6, and
    • Samsung Galaxy S5 LTE-A, SM-G906S/K/L, codename lentislte.
    • This port is mostly stable. Still, there's no software without bugs.

    How to install:

    • For kccat6, use bootloader CQJ1, CQJ2 or later.
    • For lentislte use bootloader CPL1.
    • install custom recovery, ideally directly from the TWRP project.
      For kccat6: twrp-3.3.0-0-kccat6.img
      For lentislte: twrp-3.3.0-0-lentislte.img
      Note: TWRP 3.2.1-0 is required starting with Lineage-15.1/Oreo!
    • Enter recovery mode
    • Factory reset
    • Flash below ROM
    • Optionally flash Gapps. I suggest OpenGapps.
    • Optionally, if you want SU, install the LineageOS SU addon.
    • Reboot

    Know problems:

    • Sometimes the SIM doesn't show up after reboot.
    • Occasional Camera hiccups.

    State of kernel security:

    Download from:

    Official nightly builds:
    Test builds (only on demand or request):


    XDA:DevDB Information
    LineageOS for Samsung Galaxy S5 LTE+ / LTE-A, ROM for the Samsung Galaxy S5

    cvxda, sassmann, xamio, sktjdgns1189
    Source Code: https://github.com/LineageOS

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.10.x
    ROM Firmware Required: kccat6: CQJ1/CQJ2, lentislte: CPL1
    Based On: Lineage OS

    Version Information
    Status: Beta

    Created 2017-01-08
    Last Updated 2019-04-17

    Thanks to @Stamgastje for the first cut of these notes.

    History and older builds (LineageOS)

    The Lineage OS project -- a.k.a. Lineage Android Distribution (LAD) -- is a continuation of the CyanogenMod project, which was discontinued in December 2016. Before maintaining Lineage OS 14.1 ROM for this phone, @xamio maintained CyanogenMod ROMs (CM13, CM14.1). You can still find these builds via the link to his site (ionkiwi.nl) above. The original (and oldest) CyanogenMod builds for this phone were created by @sktjdgns1189. His original builds are still available here: http://fsrv1.sayanogen.com/KCCAT6-13/, and this was the original thread on this forum.


    Below some hints that may help you to install these ROMs on your phone.

    Clean install, or dirty flashing?

    What is the difference?
    The difference is whether you clean (format) the entire /data partition (which contains your apps and user data, as well as the dalvik cache), or not, before flashing the new ROM image:
    • A clean install means: clean the /system, /data (incl. dalvik cache) and /cache partitions, and then install the ROM
    • Dirty flashing means: clean the /system and /cache partitions, as well as the dalvik cache, but not the entire /data partition, before installing the ROM
    With a clean install, you need to manually restore your apps and user data after flashing the new ROM image. With a dirty flash, there is no need to do this -- so this is the faster, but riskier solution. Therefore, it is always recommended to make a backup of your apps (e.g. with Titanium Backup) and user data (internal storage) before flashing any ROM image.

    When could you consider a dirty flash?
    It is, generally speaking, possible to perform a dirty flash:
    • When upgrading a ROM to an newer build of the same ROM (but be careful when upgrading between major versions, e.g. from CM13 to CM14.1)
    • When upgrading from CyanogenMod 14.1 to Lineage OS 14.1 (as Lineage OS is the continuation of CyanogenMod, based on the same sources)

    When should you perform a clean install?
    In all other cases, so e.g.:
    • When downgrading a ROM to an older build of the same ROM
    • When switching between ROMS, e.g. from CyanogenMod to Resurrection Remix (or vice versa). Reason: different ROMs use different code bases that are usually not 100% compatible (exception is upgrading from CyanogenMod 14.1 to Lineage OS 14.1, see above)

    (Note: in case you choose to perform a dirty flash over your existing ROM, don't forget to re-flash the GApps package immediately afterwards!)

    How to dirty flash an official weekly over an unofficial build (and vice versa)?

    When trying to update an unofficial build to an official weekly build, I get an error message in TWRP saying
    "Can't install this package on top of incompatible data. Please try another package or run a factory reset". How do I fix that?

    At the start of an installation the installer checks the build keys. They differ between unoffical and official builds, and the installer refuses to overwrite builds with different keys. To fix this you have to install the official keys before trying to install the official build:
    1. Run this script called lineage-migration-signed.zip in TWRP.
    2. Then install the official ROM zip.
    You only have to do this for the first switch from unoffical to offical build.

    There may be reason to dirty flash an unofficial build over an official build, for instance, if you're developing or testing new stuff. The problem is the same, just in the other direction: You have to install the unofficial build keys:
    1. Run this script called lineage-migration-unsigned.zip in TWRP.
    2. Then install the unofficial ROM zip.

    Modem and bootloader

    Which version do I need?
    Builds from Sept. 19 (cm-13.0-20160919-UNOFFICIAL-kccat6xx.zip) and later should use a Marshmallow modem & bootloader (starting with 'C', so e.g. CPE1, CPH3, CPJ1). Older builds require a Lollipop modem & bootloader (starting with 'B', so e.g. BOH4, BOK2).

    Generally, it is recommended to use the latest modem that is compatible for your device.

    How do I get these images?
    The original ROM files containing the modem and bootloader files are available from the Sammobile site. You have to extract bootloader and modem files and flash them to your device using Odin (Windows) or Heimdall (Linux, MacOS, Windows).
    • Download the firmware file from Sammobile's firmware page for the G901F, G906S, G906K or G906L, depending on your device. The last ones available are CQJ1/CQJ2 for G901F, CPL2 for G906S/K/L. Assuming you download the CQJ1 version for G-901F, the resulting file will be called G901FXXU1CQJ1_G901FDTM1CQJ1_DTM.zip.
    • Unpack that file. On Windows, right click on the file and choose "Extract all...". On Linux/Mac, simply use the command line:
      $ unzip G901FXXU1CQJ1_G901FDTM1CQJ1_DTM.zip
      After unpacking you get a new file G901FXXU1CQJ1_G901FDTM1CQJ1_G901FXXU1CQC1_HOME.tar.md5. This is a standard tar archive and can be opened with any archiver capable of handling the tar format (especially with tar itself). The attached .md5 suffix indicates, that a md5 checksum has been attached to the file.
    • Extract the file. On Windows you can do this by installing the swiss-army knife of archivers, 7zip. It installs an entry for the right-click context menu. Use it to extract G901FXXU1CQJ1_G901FDTM1CQJ1_G901FXXU1CQC1_HOME.tar.md5. On Linux/Mac, simply use the command line:
      $ tar xf G901FXXU1CQJ1_G901FDTM1CQJ1_G901FXXU1CQC1_HOME.tar.md5
      Apart from the different download page and the different file names, the procedure is the same on the G906 variants.

      Either way, this extracts the following list of files:
      NON-HLOS.bin  cache.img.ext4   recovery.img  sdi.mbn
      aboot.mbn     hidden.img.ext4  rpm.mbn       system.img.ext4
      boot.img      modem.bin        sbl1.mbn      tz.mbn
      The files with suffix .img and .img.ext are the actual system files. You don't want them, unless you want to reinstall stock Samsung Android.
      The files NON-HLOS.bin and modem.bin constitute the baseband, all other files with .mbn suffix constitute the bootloader.

    How do I flash these images on Windows with Odin?
    This is only marginally more complex than by using Heimdall (see below). The difference is that Heimdall can immediately flash the extracted .bin and .mbn files, while Odin needs them packed into a tar file. Fortunately you already have 7zip!
    • Select all of the aforementioned .bin and .mbn files. Right click to open the context menu. Select 7zip and choose Add to archive... from the sub menu

      This opens 7zip's archive dialog. As Archive format choose tar. Append .md5 to the archive filename and press the OK button

      Congratulations, you're now the happy owner of an Odin file with only bootloader and baseband images.
    • Sidenote: You could also create a tar.md5 file, you just have to append the md5 sum to the just created tar file. It's not really tricky, but you'd need an additional md5sum tool which is not available on Windows by default, so we just skip this here.
    • If you haven't already, download and install Odin.
    • Boot the phone into download mode: Power off the phone, then press and hold Volume Down + Home + Power buttons. You'll see a severe warning message. Ignore it by pressing Volume-Up. You're now in download mode.
    • Connect your device to your PC's USB port.
    • Start Odin.
    • Select the .tar file you just created.
    • Enable (only) these options: 'Auto Reboot' and 'F. Reset Time'.
    • Flash the images.

    How do I flash these images on Linux/MacOS/Windows with Heimdall?
    • If you haven't already, download and install Heimdall. If you have trouble with the most recent version of Heimdall (the official version 1.4.1 has a few annoying bugs) you have to rebuild heimdall from source by yourself. Instructions for rebuilding can be found here and here.
    • Boot the phone into download mode: Power off the phone, then press and hold Volume Down + Home + Power buttons. You'll see a severe warning message. Ignore it by pressing Volume-Up. You're now in download mode.
    • Connect your device to your PC's USB port.
    • Check if Heimdall recognizes your device:
      $ heimdall detect
      If it doesn't, you have to do some digging:
      • On Windows you might have to install Samsung device drivers.
      • On Linux you might have to create a udev entry for your device. As root, open or create the file /etc/udev/rules.d/51-android.rules and add a line
        SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0660", USER="[insert your non-root username here]"
        , then reboot the machine.
      • On Mac... sorry, I have no idea what to do on a Mac in this case.
    • Flash the bootloader and baseband images:
      $ heimdall flash --APNHLOS NON-HLOS.bin \
      --MODEM modem.bin --SBL1 sbl1.mbn --DBI sdi.mbn \
      --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn
      This may take a minute or two and then reboot your device automatically. It might reboot into your recovery. That's nothing to worry about. Just reboot from there into system.
    Lineage 15.1 goes official for kccat6/lentislte

    Apart from the occasional SIM problem it looks like we're in a pretty good shape now. I triggered the process to make 15.1 the official release for our device. First official builds are going to be built tomorrow or, if the timing isn't quite right, the week after (Monday is lineage-15.1 build day ATM).

    Let's dive in,
    If I delete those files before reboot:
    /data/dalvik-cache/arm/[email protected]@boot-telephony-common...
    the sim card is recognized.

    Thanks, maybe that's a hint for a solution.

    You were really up to something there. @sassmann created a patch to remove these files at startup, and it seems this really makes the RIL startup *much* more reliable. Over 60 reboots with 4 devices with only one fail on one device, and after another small tweak no fail on that device either.

    We need a bit more time for testing so the patch may not make it into the tomorrow's official build, but what's one week, right?

    Edit: I merged the patches so this should be in tomorrow's builds. Thanks again, @Krapotke!
    Edit 2: @Krapotke, I gifted you Ad-free, I'm just so glad we have a workaround.

    LineageOS 15.1 (Oreo) preview builds

    I made LineageOS 15.1 preview builds available for kccat and lentislte.

    This is very much Work In Progress.
    Only for the experimentally inclined, don't use as daily driver.
    This is only for toying around, I don't take bug reports yet.

    • Audio
    • Bluetooth
    • Camera (Photos only)
    • Deep Sleep
    • Display
    • Fingerprint
    • Google Play (with clean install, and a bit bumpy at installation time)
    • GPS
    • Hardware Keys
    • Lights, Torch
    • NFC
    • RIL
    • USB
    • Sensors
    • Wifi
    Not working yet: Everything else. Most notably
    • Camera (Video)
    • Google Play (see above)
    • IR
    • SELinux

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone