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

Search This thread

maanteel

Senior Member
Apr 19, 2015
87
39
Yes, I tried to flash only 0414 alone, no success. Also I tried to flash /e/ with no success. Always stuck in the animation loop.

I have an kccat6.
 
Last edited:

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,375
6,347
tiny.cc
Yes, I tried to flash only 0414 alone, no success. Also I tried to flash /e/ with no success. Always stuck in the animation loop.

I have a kccat6.
Ok I'll try making a kccat6 boot.img from 100% official sources. But with this information, I'm afraid that the fault may be on your side. It seems that your phone is set up to accept builds signed with Lineage's release keys, which shouldn't be a problem when clean flashing (one of the reasons you need to clean flash when switching to official builds). But in your case, I have no idea.

I hope my builds work for other people :p

Edit: actually, nevermind. I ran new builds today, 0415, with the compilation error fix moved to another file in the kernel, which does build and boots in another device in which I used this fix.
 
Last edited:
  • Like
Reactions: maanteel

maanteel

Senior Member
Apr 19, 2015
87
39
Unfortunately the clean flash of build 0415 does not boot into system. I flashed official cvxda boot.img additional, kccat6 booted into system.

I clean flashed /e/ again, no boot into system. I flashed boot.img , restart /e/ boots into system.

official Boot.img is the key :/

I solved my last issue (https://forum.xda-developers.com/t/...e-g901f-lte-a-g906s-k-l.3534283/post-84323077) when I installed stock rom again. I think it has something to do with the adoptable storage. But I removed that sdcard before I tried to clean flash the first time your unofficial.
Maybe I give it a try with install stock :unsure: and then again unofficial.
 
Last edited:

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,375
6,347
tiny.cc
Unfortunately the clean flash of build 0415 does not boot into system. I flashed official cvxda boot.img additional, kccat6 booted into system.

I clean flashed /e/ again, no boot into system. I flashed boot.img , restart /e/ boots into system.

official Boot.img is the key :/

I solved my last issue (https://forum.xda-developers.com/t/...e-g901f-lte-a-g906s-k-l.3534283/post-84323077) when I installed stock rom again. I think it has something to do with the adoptable storage. But I removed that sdcard before I tried to clean flash the first time your unofficial.
Maybe I give it a try with install stock :unsure: and then again unofficial.
Yes, that is another possible solution. A very inconvenient process but my builds should work if you flash them on top of stock.
 

slizer_

New member
Feb 5, 2017
2
5
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

kccat6-ripee.jpg
 

maanteel

Senior Member
Apr 19, 2015
87
39
Build 0415 is running :) , after a short visit of stock rom. One thing done.

1. Magisk 22.1 confuses me , it does not root. SafetyNet API error. Just flashed it as usually in TWRP.

2. Also Google Play app is not available (I flashed opengaaps nano) :
"google play services are not supported " is the error when starting the google app.

Some things are wrong - but I still have no glue.


Edit: I restored back to official with TWRP backup. Maybe I try it dirty. I assume the adoptable storage make problems.
 
Last edited:
  • Like
Reactions: andreoide

Deollzz

Member
Dec 24, 2015
16
3
I compiled it myself using the github sources, boots fine, as soon as encryption is enabled, it bootloops, (For me anyway).
No Magisk installed.
format data removes the encryption, and the Rom starts after installation without problems, but as soon as the encryption is activated, a reboot logically occurs which ends in a bootloop. Boot - Reset -Boot - Reset.
 
Last edited:
  • Like
Reactions: maanteel

Ralf_Volles

New member
May 8, 2021
2
0
hello, does it work ant+ in this rom?

thanks
I couldn't find an answer to Roguas question in the 2 years+ of postings since he asked. The original stock ROM does support the on borad ANT+ of the phone. But as I run this ROM and it seems not to support the on borad ANT+ hardeware of the phone, I kindly ask if any body does no a way to enable it?

Regards,
Ralf
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Changelog

    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.
    3
    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

    kccat6-ripee.jpg
    2
    I did it again :D


    booting into TWRP
    1. Swiped for Factory Reset (which is wiping data without wiping /data/media...)
    2. Advance Wipe: Dalvic/ART Cache, System, Data, Cache
    3. Install only Build 0401 (no gaaps, no magisk) - Install ZIP Successful
    4. Wiped Cache/Dalvik
    5. Reboot System

    also switched step 1+2

    no luck :/
    No idea, I used the official sources. The only change I made to the kernel is a minor build error fix that has no effect on the finished build.

    Edit: Can you extract the boot.img file from the signed build and flash it after you flash my 0413 build, then wipe cache and dalvik.

    Edit 2: I ran new builds today, 0414. Perhaps you will have better luck with these?
    2
    Root with Magisk 22.1 does not cause any problems, Viper FX and AFWall+ work fine, only the encryption of the smartphone is no longer possible.
    2
    Unfortunately the clean flash of build 0415 does not boot into system. I flashed official cvxda boot.img additional, kccat6 booted into system.

    I clean flashed /e/ again, no boot into system. I flashed boot.img , restart /e/ boots into system.

    official Boot.img is the key :/

    I solved my last issue (https://forum.xda-developers.com/t/...e-g901f-lte-a-g906s-k-l.3534283/post-84323077) when I installed stock rom again. I think it has something to do with the adoptable storage. But I removed that sdcard before I tried to clean flash the first time your unofficial.
    Maybe I give it a try with install stock :unsure: and then again unofficial.
    Yes, that is another possible solution. A very inconvenient process but my builds should work if you flash them on top of stock.
  • 83
    lineage-os-logo.png

    LineageOS for Samsung Galaxy S5 LTE+ / LTE-A

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

    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):

    Sources:


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

    Contributors
    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
    51
    Notes:

    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.

    Installation

    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:
      Code:
      $ 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:
      Code:
      $ 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:
      Code:
      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
      Screenshot_20170125_120950.png

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

      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:
      Code:
      $ 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
        Code:
        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:
      Code:
      $ 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.
    16
    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,
    Corinna
    16
    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.


    Corinna
    16
    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.

    Working:
    • 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

    Corinna
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