[OFFICIAL] LineageOS 17.1 for Galaxy S5 klte + Variants

Search This thread

761gg1i3219

Member
Apr 11, 2020
37
1
Re: S5 Cannot Boot in Recovery. - Frozen or Bootloop Reset



So, did you try to flash the most recent stock Samsung OS with Odin3 or not? :unsure:

If so, does it work properly or not?
***

It wasn't easy (because I had a few reboots in the process) but I did it, with Heimdall, unluckily I still am in a boot loop, the phone starts and after a few seconds showing "Samsung Galaxy S5" it reboots. I can still access Download and (Stock) Recovery mode.
I know all odds are against me but I'm still hoping there's something I can do, especially now that 18.1 will become official very soon for klte.
Is there a way to know if I flashed the wrong Stock Firmware? As in, how can I know what specific version I need (I mean original country/carrier)? Should I try them all or at least the most probable ones?
 
Re: S5 Cannot Boot in Recovery. - Frozen or Bootloop Reset

Is there a way to know if I flashed the wrong Stock Firmware?

The best way to know the truth about what is the exact S5 model is to turn off the phone & boot in Odin Mode (aka Download mode): press and hold Home + Power + Volume Down buttons and confirm with Volume up to Continue.

The PRODUCT NAME that you can see after you accept the disclaimer is the real model number. (screenshot)

I saw several cases on XDA of S5 users scammed with a S5 made for the Chinese market labeled SM-G900F which is for the European market but the Download mode said the truth.

As in, how can I know what specific version I need (I mean original country/carrier)?

It does not matter. Just install with Odin3 the most recent stock Samsung OS for that exact device model.

But you can try with DevCheck > System > Product code and Original CSC. (screenshot)

Or with adb and this command:

adb shell getprop > getprop.txt

For example for my S5 in that getprop.txt:

[ril.product_code]: [SM-G900MZKATPA]
[ril.radiostate]: [10]
[ril.rfcal_date]: [2015.08.25] <<< date my S5 G900M was manufactured.

The Original CSC is the last 3 digits of the ril.product_code.

Try a S5 LineageOS Super Clean Install including Format Data (not wipe) + wiping System, Dalvik / Art cache & Cache after installing the most recent stock Samsung OS which is also described in it.

I wrote that post for LineageOS 16.0 but it works also for 17.1 & 18.1.
***

It wasn't easy (because I had a few reboots in the process) but I did it, with Heimdall...

As a Windows user I hate the finicky Heimdall & it's clunky Zadig sidekick. BTW the driver for it breaks Odin3's connection to the device & must be removed for it to work again.

Odin3 is a fast & simple professional proprietary tool made by Samsung to flash stock Samsung OS on Samsung devices that works only on a Windows PC.

Do yourself a favor & borrow a Windows PC for a few minutes if you are on Linux or a Mac.
***
 

Attachments

  • Download_Mode_Odin_S5_G900M_curiousrom.png
    Download_Mode_Odin_S5_G900M_curiousrom.png
    2.9 MB · Views: 45
  • DevCheck_System_Bootloader_Radio_S5_curiousrom.png
    DevCheck_System_Bootloader_Radio_S5_curiousrom.png
    174.1 KB · Views: 42
Last edited:

761gg1i3219

Member
Apr 11, 2020
37
1
Re: S5 Cannot Boot in Recovery. - Frozen or Bootloop Reset



The best way to know the truth about what is the exact S5 model is to turn off the phone & boot in Odin Mode (aka Download mode): press and hold Home + Power + Volume Down buttons and confirm with Volume up to Continue.

The PRODUCT NAME that you can see after you accept the disclaimer is the real model number. (screenshot)

I saw several cases on XDA of S5 users scammed with a S5 made for the Chinese market labeled SM-G900F which is for the European market but the Download mode said the truth.



It does not matter. Just install with Odin3 the most recent stock Samsung OS for that exact device model.

But you can try with DevCheck > System > Product code and Original CSC. (screenshot)

Or with adb and this command:

adb shell getprop > getprop.txt

For example for my S5 in that getprop.txt:

[ril.product_code]: [SM-G900MZKATPA]
[ril.radiostate]: [10]
[ril.rfcal_date]: [2015.08.25] <<< date my S5 G900M was manufactured.

The Original CSC is the last 3 digits of the ril.product_code.

Try a S5 LineageOS Super Clean Install including Format Data (not wipe) + wiping System, Dalvik / Art cache & Cache after installing the most recent stock Samsung OS which is also described in it.

I wrote that post for LineageOS 16.0 but it works also for 17.1 & 18.1.
***



As a Windows user I hate the finicky Heimdall & it's clunky Zadig sidekick. BTW the driver for it breaks Odin3's connection to the device & must be removed for it to work again.

Odin3 is a fast & simple professional proprietary tool made by Samsung to flash stock Samsung OS on Samsung devices that works only on a Windows PC.

Do yourself a favor & borrow a Windows PC for a few minutes if you are on Linux or a Mac.
***
Maybe I'm not explaining myself well, so pardon me.
I don't get why you hate Heimdall so much since it's open source, it has a nice CLI and GUI, using Odin wouldn't make a difference.

The problem I have is not how to flash my phone cause I did it already many times with Heimdall, that is irrelevant.

I am sure I have a SM-G900F, I was asking about how to find country/carrier code because I have to flash the exact firmware for my phone, saying "the most recent stock Samsung OS for that exact device model." doesn't really help since here https://www.sammobile.com/samsung/galaxy-s5/firmware/#SM-G900F there are dozens of firmwares for the SM-G900F and I don't know which one is my phone's.

The app you suggested would help but since I am stuck in a bootloop, how can I install and run the app?
Same goes for adb, the pc doesn't detect the phone since it is not starting.
 
S5 LineageOS 17.1 klte & Variants Update 2021-04-04

FYI OTA updated my Galaxy S5 G900M LineageOS 17.1 klte build 2021-03-28 + Open GApps Pico + Magisk 22.0 + TWRP 3.5.1_9-0 recovery to build 2021-04-04 & everything went smoothly except that Magisk 22.0 did not survive the update. Flashing Magisk-v22.0.zip fixed it.

No big changes in this update & all the changes with the word Intel in the changelog do not apply to the S5 klte family: https://download.lineageos.org/klte/changes/.

Thank you Mr. haggertk & to the entire LineageOS Team for supporting our S5's. :cool: 👍
***

One can see in last night's Lineage builder run that it failed for 11 devices so haggertk waiting a bit for a more stable Lineage building infrastructure before promoting the S5 klte family to 18.1 makes sense.
***
 
Last edited:
  • Like
Reactions: bersem and dcarvil
Lineage Automated Builder & 18.1

Why does it say Lineage 16.0 though, Is that on purpose?

No, that's just an oversight and label for that sub-site. The devs are really busy trying to make the infrastructure capable of building both 17.1 & 18.1 for a total of 157 supported devices @ the present as you can see in https://github.com/LineageOS/hudson/blob/master/lineage-build-targets but if you look at the individual devices in the build run they have the proper build version.

I'm assuming we'll have to flash 18.1 manually in the future, even if it gets official build, right?

Yes manually to upgrade from 17.1 to 18.1 but afterwards OTA update or manually if you wish for 18.1. There is an official guide for upgrading and TWRP can be used instead of the Lineage recovery which I did going from 16.0 to 17.1 without losing apps & settings: https://wiki.lineageos.org/devices/klte/upgrade

I'd imagine some people may want to stay on 17.1

Some late adopters yes but 17.1 will not get updates anymore after official 18.1 is launched because Lineage normally supports only 1 version per device.
***
 
Last edited:
  • Like
Reactions: pmduper and Garry58

HippoMan

Senior Member
May 5, 2009
1,643
483
Hippoland
S5 LineageOS 17.1 klte & Variants Update 2021-04-04

FYI OTA updated my Galaxy S5 G900M LineageOS 17.1 klte build 2021-03-28 + Open GApps Pico + Magisk 22.0 + TWRP 3.5.1_9-0 recovery to build 2021-04-04 & everything went smoothly except that Magisk 22.0 did not survive the update. Flashing Magisk-v22.0.zip fixed it.

I also lost Magisk with this latest update. And it wiped out SwiftKey, as well. I had to redownload and reinstall it.
 
  • Like
Reactions: curiousrom
20210404 build causes latest TWRP (v3.5.1_9-0) to reboot upon start of dirty flash...

That's weird. You can find a recovery log after a successful or failed OTA update or manual update in the /cache/recovery/ folder.

Did you check the sha256 of the downloaded file to make sure it's not corrupted?

Or if you use the built-in Updater it automatically checks the file when the download is completed.
***
 
Last edited:

x2k13

Senior Member
Nov 2, 2015
326
202
What was the update today, I don't see anything in the changelog. Or it's just no changes for klte?

p.s. I find it ironic, that S4 already on 18.1, but not S5. I know it's not that easy, but kinda funny
I expected for today's build already to be 18.1, like S4 download page has it.
 

jdrch

Senior Member
  • Jun 18, 2014
    407
    179
    Quad Cities, IA
    That's weird. You can find a recovery log after a successful or failed OTA update or manual update in the /cache/recovery/ folder.

    Did you check the sha256 of the downloaded file to make sure it's not corrupted?

    Or if you use the built-in Updater it automatically checks the file when the download is completed.
    ***
    Same problem with 20210411 build.

    Yes, I always check the hash before I flash and it was OK.

    It fails when flashing in TWRP. I've had catastrophic issues (boot failure, etc.) when flashing from within the OTA updater, and when in TWRP I can do a nandroid backup before flashing, so that's why I prefer TWRP.

    Because attempting the flash causes TWRP to reboot immediately there are no TWRP logs describing the issue :( The last build to flash properly in TWRP was the 20210328 build, so whatever was added after that seems to be the issue.
     
    S5 LineageOS 17.1 klte & Variants Update 2021-04-11 - Magisk 22.1 Survives!

    FYI I OTA updated my Galaxy S5 G900M LineageOS 17.1 klte build 2021-04-04 + Open GApps Pico + Magisk 22.1 + TWRP 3.5.2_9-0 recovery to build 2021-04-11 & everything went smoothly including Magisk 22.1 surviving the update.

    There is no changes compared to build 2021-04-04 as you can see in https://download.lineageos.org/klte/changes/ but I wanted to test the TWRP & Magisk updates vs. OTA.

    Before the OTA update made a full TWRP backup then I used TWRP 3.5.1_9-0 to update to TWRP 3.5.2_9-0 as described in How To Update TWRP Using TWRP Itself then rebooted to recovery to check the version and finally to System. (screenshots). Changelog https://twrp.me/

    I used the installed Magisk 22.0 app to update it to Magisk 22.1 app, then Direct install method to update Magisk itself to 22.1. (screenshots) Changelog: https://github.com/topjohnwu/Magisk/releases.

    Of note in that Magisk page it says this but it was not my case: "RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!".
    ***

    I was hoping for an upgrade to official LineageOS 18.1 or a security bump on 17.1 but that will have to wait for the next update I guess.

    Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :cool: 👍
    ***
     

    Attachments

    • Magisk_22.1_Update_S5_curiousrom.png
      Magisk_22.1_Update_S5_curiousrom.png
      384.1 KB · Views: 39
    • TWRP_3.5.2_9-0_S5_curiousrom.png
      TWRP_3.5.2_9-0_S5_curiousrom.png
      156.4 KB · Views: 39
    • Android_Version_2021-04-11_S5_curiousrom.png
      Android_Version_2021-04-11_S5_curiousrom.png
      125.9 KB · Views: 40
    Last edited:
    S5 LineageOS 17.1 klte & Variants Update 2021-04-18 - Bump Security

    I OTA updated my Galaxy S5 G900M LineageOS 17.1 klte build 2021-04-11 + Open GApps Pico + Magisk 22.1 + TWRP 3.5.2_9-0 recovery to build 2021-04-18 & everything went smoothly including Magisk 22.1 surviving the update.

    After the automatic reboot as seen in the screenshot > Settings > About phone > press on Android version > Android security patch level: April 5, 2021.

    The Vendor security patch level remains @ August 1, 2017 because the vendor is Samsung & it is not publishing security patches for it's S5 proprietary hardware related blobs anymore since August 2017.

    There are a bunch of changes in this update as you can see in https://download.lineageos.org/klte/changes/ but the ones with the word "intel" do not concern the S5.

    The klteduos 20210418 build failed as you can see in the LineageOS automated builder here so better luck next week.

    No official LineageOS 18.1 yet for the klte family until these haggertk's commits are marked as Merged top left instead of Active so patience is required:
    Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :cool: 👍
    ***
     

    Attachments

    • Updater_2021-04-18_LineageOS_17-1_S5_curiousrom.png
      Updater_2021-04-18_LineageOS_17-1_S5_curiousrom.png
      320.9 KB · Views: 26
    Last edited:

    argonaut459

    Member
    Sep 18, 2020
    36
    6
    Why o why has my screen have to break now?

    Btw the last links with
    Yet another ...
    And where the ...
    I don't get it. What are these links and things I can see there?
     

    Top Liked Posts

    • 2
      LineageOS Music app theme, cant change to dark?
      Enable override force-dark in developer options or update to 18.1
    • 7
      Official LineageOS 18.1 for the Galaxy S5 klte family Launched!

      FYI these haggertk's commits are now marked as Merged so it should be available in the next update if all goes well with the Lineage automated builder:
      And it's confirmed in the LineageOS build target list and the wiki pages https://wiki.lineageos.org/devices/ also.

      The respective wiki pages include an upgrade guide.

      Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :cool: 👍
      ***
      6
      S5 LineageOS 17.1 klte & Variants Update 2021-04-18 - Bump Security

      I OTA updated my Galaxy S5 G900M LineageOS 17.1 klte build 2021-04-11 + Open GApps Pico + Magisk 22.1 + TWRP 3.5.2_9-0 recovery to build 2021-04-18 & everything went smoothly including Magisk 22.1 surviving the update.

      After the automatic reboot as seen in the screenshot > Settings > About phone > press on Android version > Android security patch level: April 5, 2021.

      The Vendor security patch level remains @ August 1, 2017 because the vendor is Samsung & it is not publishing security patches for it's S5 proprietary hardware related blobs anymore since August 2017.

      There are a bunch of changes in this update as you can see in https://download.lineageos.org/klte/changes/ but the ones with the word "intel" do not concern the S5.

      The klteduos 20210418 build failed as you can see in the LineageOS automated builder here so better luck next week.

      No official LineageOS 18.1 yet for the klte family until these haggertk's commits are marked as Merged top left instead of Active so patience is required:
      Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :cool: 👍
      ***
      4
      Hello friends,
      I am using the tuned kernel for screen flickering problem. Will it work if I upgrade from 17.1 to 18.1
      18.1 will most likely overwrite tuned kernel when you upgrade. @fbs will prolly update to support android R when LOS 18.1 klte officially comes out.
      3
      Why o why has my screen have to break now?

      Btw the last links with
      Yet another ...
      And where the ...
      I don't get it. What are these links and things I can see there?
      Gerrit is the code review System used by lineageOS. Each change in source code has to be approved in that system, before changes get merged to official source code. The linked changes are not for lineageOS source code, but for the build servers. Hudson/build targets tells the build server, what device and version to build.
      3
      18.1 official is out for klte. The day has come!

      If you're looking for Google apps, MindTheGApps is the only one recommend for Android 11 atm. Our device is ARM, not ARM64. Don't forget to make a backup.
    • 9
      S5 LineageOS 17.1 klte & Variants Update 2021-04-11 - Magisk 22.1 Survives!

      FYI I OTA updated my Galaxy S5 G900M LineageOS 17.1 klte build 2021-04-04 + Open GApps Pico + Magisk 22.1 + TWRP 3.5.2_9-0 recovery to build 2021-04-11 & everything went smoothly including Magisk 22.1 surviving the update.

      There is no changes compared to build 2021-04-04 as you can see in https://download.lineageos.org/klte/changes/ but I wanted to test the TWRP & Magisk updates vs. OTA.

      Before the OTA update made a full TWRP backup then I used TWRP 3.5.1_9-0 to update to TWRP 3.5.2_9-0 as described in How To Update TWRP Using TWRP Itself then rebooted to recovery to check the version and finally to System. (screenshots). Changelog https://twrp.me/

      I used the installed Magisk 22.0 app to update it to Magisk 22.1 app, then Direct install method to update Magisk itself to 22.1. (screenshots) Changelog: https://github.com/topjohnwu/Magisk/releases.

      Of note in that Magisk page it says this but it was not my case: "RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!".
      ***

      I was hoping for an upgrade to official LineageOS 18.1 or a security bump on 17.1 but that will have to wait for the next update I guess.

      Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :cool: 👍
      ***
      8
      yUIn6TF.png

      Edit: FYI the LineageOS S5 klte family maintainer created a new thread here:

      [ROM][OFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)
      ***
      Code:
      #include "std_disclaimer.h"
      /*
      * Your warranty is now void.
      *
      * I am not responsible for bricked devices, dead SD cards,
      * thermonuclear war, or you getting fired because the alarm app failed. Please
      * do some research if you have any concerns about features included in this ROM
      * before flashing it! YOU are choosing to make these modifications, and if
      * you point the finger at me for messing up your device, I will laugh at you.
      */

      LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.

      All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit the Wiki.

      Important Info
      WARNING: the official 17.1 build 20201101 is defective, causing a bootloop & got removed from the Lineage servers. The ROMs affected are klte, klteduos & kltedv.

      If you updated to 20201101 and are caught in a bootloop as reported by several S5 users in the pages #3 of this thread and the following pages: flash an older version like 20201025 without wiping anything (a.k.a. dirty flash) and you will not lose your aps & settings:

      1- On the S5 you can simulate a battery removal if you press Volume down + Power button for 10-20 seconds while frozen, in bootloop or Download Mode: the S5 goes black & turns off.

      If you keep on pressing the buttons until the Samsung bootloader splash screen appears & release them then S5 should reboot in System.

      Or remove the battery to turn it off.

      2- With the S5 turned off hold Volume Up + Home + Power to boot in recovery and either sideload the older version or copy to the S5 the older build as MTP is enabled by default in TWRP and flash it from there.
      ***

      To flash this rom you need TWRP version 3.3.1-0 or newer or the Lineage Recovery specific to your device model.

      Some TWRP 3.4.0 users reported fail to install LineageOS after a wipe. Rebooting to TWRP recovery after the wipe solves this issue.

      The adb command adb reboot sideload does not work in TWRP for the S5 as if you sideload a file afterwards it will fail as I tested myself with this error message: " command is: 'sideload' and there is no value". You must manually select in TWRP > Advanced > ADB Sideload > swipe to begin sideload then you can sideload your file. You must do the same for each files if you sideload more than one.

      The S5 maintainer haggertk recommends not choosing Internal storage for the Micro SD card (adoptable storage) when formatting the card in the device and posted about it here: "...my opinion is no one should use adoptable storage. It's a fragile mess and always has been since Google explicitly does not care about sdcards.".

      Some S5 17.1 users reported being stuck in an endless boot animation after restoring a 17.1 TWRP backup. A workaround tested by @wireroot & posted here is to flash the original LineageOS ROM that you were running when you made that backup right after the restore operation. This was confirmed by @jdrch in his post here.

      An other possible workaround is to flash "fix_rootfs_label.zip" that you can find here right after restoring the TWRP backup. Note: this was NOT confirmed yet by S5 users in this thread.

      EFS Partition Restore - @Eadn33 reported here in the old 16.0 thread that he could not restore the EFS partition with TWRP 3.4.0 but could with TWRP 3.3.1-0 on his S5 G900V. Other models may have that problem also but no other reports so far. See EFS Partition Backup - No Service, No IMEI & No SIM Card Fix for explantions.

      Warning: do NOT select install TWRP app in TWRP as it will cause a bootloop.


      Download Links
      The Galaxy S5 klte variants currently supported by LineageOS are:

      klte - SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8
      klteactivexx - SM-G870A, SM-G870F
      kltechn - SM-G9006V, SM-G9008V
      kltechnduo - SM-G9006W, SM-G9008W
      klteduos - SM-G900FD, SM-G900MD
      kltedv - SM-G900I, SM-G900P
      kltekdi - SCL-23, SC-04F
      kltekor - SM-G900K, SM-G900L, SM-G900S

      Each respective download pages include a link to the official clean installation instructions and a link to Device info which includes a link about how to upgrade to a higher version. For example from official 16.0 to official 17.1 without losing your settings & apps.

      The wiki mentions only the Lineage recovery but several S5 users reported successful clean install or 16.0 > 17.1 upgrading while using TWRP instead.

      TWRP: https://twrp.me/samsung/samsunggalaxys5qualcomm.html

      Google apps (Optional. The S5 requires the ARM for Android 10 version because LineageOS 17.1 is based on Android 10 & the S5's ARM architecture.): https://wiki.lineageos.org/gapps.html

      As a rule of thumb the larger the Open GApps package, the more chance of a problem on first boot with the ever changing privapp-permissions.

      I prefer the smaller Pico package & just add the extra apps I need from Play Store and https://f-droid.org/ See Open GApps Package Comparison

      Some users prefer not installing any Gapps packages & use the Aurora Store v3 - a FOSS Google Play client to download apps from Play Store. Note that some apps may require the Google Play Services & librairies which are included in the Gapps packages & may not work properly or will not get timely notifications because of it.

      Root (Optional): The LineageOS AddonSU and Privacy Guard are deprecated in 17.1. :(

      Magisk which is the only root solution for 17.1 @ the present is not supported by LineageOS. See Magisk download & Installation instructions by the Magisk dev & also the excellent Magisk and MagiskHide Installation and Troubleshooting guide by @Didgeridoohan. Thread on XDA: Magisk General Support / Discussion.

      Magisk can be installed later at anytime so it's not necessary to install it during the initial installation of LineageOS.

      Bug Reporting
      If a bug is discovered, confirm it with other users in this thread & include your device model & build date (for ex. lineage-17.1-20201025-nightly-klte), then report it following the LineageOS wiki here: https://wiki.lineageos.org/bugreport-howto.html

      Known Bugs - Known Issues
      1- On an encrypted S5 17.1 + Gapps if Secure Startup is enabled it may fail to reboot or take a very long time to boot. See bug report here.

      From haggert's post here:

      ...there is some kind of timeout that hits ALL legacy devices - addition of gapps is seemingly enough to push it over the edge. Aside from first boot or upgrade, sometimes you'll be able to get in and sometimes not. I bet if you are able to decrypt in twrp and delete dalvik cache you'll get fully booted again.

      Bottom line, if you are encrypted, make sure to disable secure startup (go change the pin/pattern/password, even to the same thing, and say that you do not want to have to answer for the device to start). {bold by me}

      2- Not a bug really but some S5 users reported fail to boot on 17.1 or no SIM card recognized because they had an older baseband/modem. See S5 Odin Flashable Modem & Bootloader.

      Haggertk posted here about 17.1: "...I'm willing to bet that you have some L or earlier baseband. Except for the activexx build, you have to be running M baseband now." {bolding by him}.

      3- Google Backup cannot be restored if you use a 4x4, 5x5 or 6x6 lock screen pattern in LineageOS instead of the Android default 3x3 pattern. See the bug report here.

      4- Display accepts touch input while off due to proximity and screen does not turn back on after call bug report by @Eadn33. The bug was fixed with klte family builds 2020-11-13 or newer. Thank you Mr. haggertk.

      5- SMS reception notification delay depends on doze / unlock state by @wireroot. He posted about it in this thread here.

      6- Bluetooth Crashing - Some users reported having issues with Bluetooth in this thread: @KrautHolg here, @liquidraver here and here, @pmduper here, @navcar here and included a logcat, @badesh here and here, @mrmarioman who posted here.

      @KrautHolg created a report in the LineageOS bug tracker with a logcat here: Bluetooth repeatedly crashes with multiple devices for the S5 klte LineageOS 17.1.

      OTOH @Eadn33 reported here that he does not have any problems "with a soundbar, music and hands free in car , or scan tool for car". I tested for 2 hours listening to music with Bluetooth headphones, received a call & also had no problems on my S5 G900M klte.

      So far nobody created a Bluetooth bug report with an attached logcat in the LineageOS bug tracker for the S5 running LineageOS 17.1. See this post about how to create one: S5 Bluetooth Crashing Bug Report?

      7- Fingerprint Scanner: Some S5 users reported not being able to register their fingerprints in > Settings > Security > Fingerprint. Contrary to the Lineage instructions the finger must be swiped down & not just "Touch the sensor". See the screenshot & the linked trick if you still can't register the fingerprint in S5 G900F Fingerprint Issue.

      Not a bug but some users reported the scanner not working on older basebands but working after updating it like @jackass5 in his post here. See S5 Odin Flashable Modem & Bootloader.

      Several users, including me, reported a higher battery usage after registering some fingerprints. See S5 Screen Lock Fingerprint Battery Tests @ Idle - BetterBatteryStat

      8- Camera (Snap) > Settings > Storage > if you select SD Card the photos are saved to /external sdcard I.D./Android/Data/org.lineageos.snap/Files/ but taping on the thumbnail of the photo you just took mistakenly opens /storage/emulated/0/DCIM/Camera/. Additionally, Gallery does not see that Files folder but a third-party app like Simple Gallery Pro that does show the Files album.

      In LineageOS 17.1 build 2020-11-23 or newer the SD Card option was deleted instead of fixing the bug. See LineageOS 17.1 - In Camera the Option Save to SD Card has Been Removed in this thread.

      9- Call Forwarding Not Working - In both the stock Phone app or when dialing a code it's broken. See this post that includes a link to a bug report: S5 klte LineageOS 17.1 Call Forwarding Error. Thanks to @uyguremre for reporting the issue here.
      ***

      S5 U.I. Speed-Up Tip: Try those as fast as you can before the tweak: expand/close notification curtain, app drawer & scroll, recent apps & scroll, horizontal scroll fast between hope pages if you have a few, open Settings & scroll, etc.

      Then: Settings > Accessibility > enable Remove animations.

      Test again as you did before. Profit!

      LineageOS FAQ
      https://wiki.lineageos.org/faq.html

      LineageOS Stats
      https://stats.lineageos.org/

      Credits
      The S5 klte + variants LineageOS maintainer is @haggertk who valiantly supported the S5 klte family through LineageOS 14.1, 15.1, 16.0 & now 17.1. Big thanks for his perseverance & dedication. :cool:👍

      He is also one of the 9 LineageOS directors and maintains other devices as well as you can see in https://wiki.lineageos.org/contributors.html

      Many thanks also to the LineageOS team and all the contributors out there in the community that made the Lineage project possible. You can see their names or nicknames in the zoomable & searchable > Settings > About phone > Contributors.

      Haggertk seemed uninterested in creating an S5 17.1 tread on XDA or he is too busy maybe so I went ahead and created one using part of the OP of his old S5 LineageOS 15.x thread. If he wants a transfer of this thread's ownership I will gladly do it.


      Kernel Source Code:
      Kernel tree: https://github.com/LineageOS/android_kernel_samsung_msm8974/tree/lineage-17.1

      LineageOS Gerrit code review: https://review.lineageos.org

      Android version: 10

      Note: this post as well as posts #2 & 3 will be updated soon.
      ***
      7
      Official LineageOS 18.1 for the Galaxy S5 klte family Launched!

      FYI these haggertk's commits are now marked as Merged so it should be available in the next update if all goes well with the Lineage automated builder:
      And it's confirmed in the LineageOS build target list and the wiki pages https://wiki.lineageos.org/devices/ also.

      The respective wiki pages include an upgrade guide.

      Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :cool: 👍
      ***
      7
      S5 LineageOS 17.1 klte & Variants Update 2021-01-24

      I updated my Galaxy S5 G900M LineageOS 17.1 klte build 2021-01-17 + Open GApps Pico + Magisk 21.4 Stable + Magisk Manager 8.0.7 & TWRP 3.5.0 to build 2021-01-24 via the built-in OTA Updater: everything went smoothly as usual & Magisk survived the update.

      Some of the changes that you can see in https://download.lineageos.org/klte/changes/ do not concern the S5 klte family (Motoactions, fastcharge & nvidia) and the others like the ones concerning android_packages_apps_ThemePicker (Settings > Display > Styles & wallpapers) are not dramatic but I updated anyway to be able to post in this thread.

      Thank you Mr. haggertk & to the entire LineageOS Team for supporting our S5's. :cool: 👍
      ***
      6
      S5 LineageOS 17.1 klte & Variants Update 2021-02-14

      I updated my Galaxy S5 G900M LineageOS 17.1 klte build 2021-02-07 + Open GApps Pico + Magisk 21.4 Stable + Magisk Manager 8.0.7 & TWRP 3.5.0 to build 2021-02-14 via the built-in OTA Updater: everything went smoothly as usual & Magisk survived the update.

      There are no important changes except maybe some time zone stuff for certain regions as you can see in https://download.lineageos.org/klte/changes/ but I updated anyway so I could post about it here.

      Thank you Mr. haggertk & to the entire LineageOS Team for supporting our S5's. :cool: 👍
      ***
    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