[ROM][OFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)

Search This thread

kurtn

Senior Member
  • Jan 28, 2017
    3,984
    1,725
    Small town in Bavaria
    Ah, no wonder my System UI was crashing when I dirty flashed from 17.1. Anyway I clean flashed (luckily my S5 is not my main device, I use it for watching streaming video only, so setup is minimal) and fixed that problem. Gonna install Magisk soon. Thanks!
    I don't see how magisk should be part of a minimal installation
     

    MilkyWay20

    New member
    Dec 21, 2020
    4
    2
    Hi,
    I made a dirty flash from 17.1 to 18.1. But now I'm not able to unlock the phone. After entering the PIN the screen become black. After a second it shows me that the phone is locked.
    Any solution to unlock the phone?
     
    • Like
    Reactions: curiousrom

    ludwig83

    Member
    May 9, 2018
    25
    13
    Read a lot about Magisk the last days...so I tried it out yesterday! Magisk v23.apk renamed to .zip and sideloaded through Lineage Recovery (aply update). No problems at all. works fine. After that I made the OTA update through auto updater...Magisk is still there. the only thing I recognized is that Lineage Recovery did not update. maybe I have to do the uninstall workaround (uninstall but no reboot and after ota install in Magisk Manager again) ...what do you think?
     

    ludwig83

    Member
    May 9, 2018
    25
    13
    @MilkyWay20 ...when you read a little bit before you post something ...


    its not really hidden ...it happend on the 1 Side....
     

    kurtn

    Senior Member
  • Jan 28, 2017
    3,984
    1,725
    Small town in Bavaria
    Read a lot about Magisk the last days...so I tried it out yesterday! Magisk v23.apk renamed to .zip and sideloaded through Lineage Recovery (aply update). No problems at all. works fine. After that I made the OTA update through auto updater...Magisk is still there. the only thing I recognized is that Lineage Recovery did not update. maybe I have to do the uninstall workaround (uninstall but no reboot and after ota install in Magisk Manager again) ...what do you think?
    Magisk is nothing to try out for fun. It is a massive security hole. You need to know what you do. And you only install it, if you really find no other way to do whatever you intend using magisk for.
     
    Warning: Cannot Unlock the S5 After Upgrading from LineageOS 17.1 to 18.1

    I made a dirty flash from 17.1 to 18.1. But now I'm not able to unlock the phone. After entering the PIN the screen become black. After a second it shows me that the phone is locked.
    Any solution to unlock the phone?
    Just found the solution on... {quote of a post about the OnePlus One snipped by me}...

    For dirty upgrade remove your PIN before upgrade. If you have already upgraded go back to TWRP and delete that file: /data/system/locksettings.db

    Thanks for reporting the issue & posting the solution you found. :cool: 👍

    You could also have found the issue & the solution on page #1 of this thread as mentioned in @Massedil's post here which includes a haggertk quote.

    I don't understand why @haggertk does not mention this in the OP and also does not add a warning in https://wiki.lineageos.org/devices/klte/upgrade . ¯\_(ツ)_/¯

    I saw seven S5 klte* users reporting that same issue so far. 🤪

    I also mentioned that issue in Galaxy S5 LineageOS 17.1 Upgrade to 18.1 + OTA Update Success Using TWRP and wrote in that post: I always disable screen & SIM locks before an update or upgrade just to remove variables that may go wrong.
    ***
     
    Last edited:

    x2k13

    Senior Member
    Warning: Cannot Unlock the S5 After Upgrading from LineageOS 17.1 to 18.1




    Thanks for reporting the issue & posting the solution you found. :cool: 👍

    You could also have found the issue & the solution on page #1 of this thread as mentioned in @Massedil's post here which includes a haggertk quote.

    I don't understand why @haggertk does not mention this in the OP and also does not add a warning in https://wiki.lineageos.org/devices/klte/upgrade . ¯\_(ツ)_/¯

    I saw seven S5 klte* users reporting that same issue so far. 🤪

    I also mentioned that issue in Galaxy S5 LineageOS 17.1 Upgrade to 18.1 + OTA Update Success Using TWRP and wrote in that post: I always disable screen & SIM locks before an update or upgrade just to remove variables that may go wrong.
    ***
    At first I thought deleting the locksettings.db might fix the lag when unlocking the SIM card after reboot, before the lock screen appears, unfortunately it doesn't. 🤔

    Would have been nice to finally find a way to get rid of this bug, especially because jfltexx doesn't have this issue despite of being the slower and older device. 🤗
     
    • Like
    Reactions: curiousrom

    buntbart

    Member
    Mar 24, 2018
    5
    2
    Thank you so much for still maintaining this old bones called klte, dear haggertk!! 🥳
    I already updated four klte's without major problems to LineageOS 18.1.
    The only thing that stopped working after the update seems to be "Bluetooth GPS Provider" but that's not your fault and I already found an alternative called "Bluetooth GNSS"
    So thank you, thank you, thank you! 👍
     
    S5 LineageOS 18.1 Update 2021-05-16 - Lost Some Shortcuts

    Using the built-in Updater I OTA updated S5 G900M LineageOS 18.1 klte build 2021-05-09 + MindTheGapps + Magisk 23.0 + TWRP 3.5.2_9-0 to build 2021-05-16: Magisk survived the update but some shortcuts were lost on Home page.

    There was no spectacular changes in https://download.lineageos.org/klte/changes/ but updated anyway so I could post about it.

    One change is labeled Snap: api2: add QR scanner mode but it was already working before the update in my S5's stock Camera app. So I guess it's for newer devices with a newer camera api while the S5 is using the legacy Snap api v1.

    One minor annoyance is that as you can see in the screenshots some of my shortcuts were missing after the automatic reboot.

    I use the stock LineageOS Trebuchet launcher and these were shortcuts created with some apps: stacked shortcuts in a folder created with the LineageOS Settings widget, shortcut to an album created with Simple Gallery Pro, shortcuts to some web pages created with the Chrome browser and shortcuts created with Z-More Shortcuts¹.

    I suggest to capture some screenshots of your Home page(s) for reference before updating to help re-create them afterwards.

    Thankfully after re-creating the shortcuts, they survived a reboot.

    I don't know which change caused this. ¯\_(ツ)_/¯

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

    ¹ Note: for some reasons I can open the Z-More Shortcuts link on my computer but cannot find it in my phone's Play Store. Maybe it's because the dev removed it to replace it with a paid app instead with a new name: Power Shortcuts.
    ***
     

    Attachments

    • Trebuchet_Home_Update_2021-05-16_LineageOS_18-1_S5_curiousrom.png
      Trebuchet_Home_Update_2021-05-16_LineageOS_18-1_S5_curiousrom.png
      1.9 MB · Views: 38
    Last edited:

    jenssa

    Member
    Dec 8, 2018
    25
    3
    64
    Oslo
    I often find my phone in the state shown on the picture. It doesn't respond to any buttons, and I must always remove the battery to reboot. I don't know if it is hard- or software induced. Does anyone have similiar experience or know what this is?20210516_151541_031929.jpg
     
    I often find my phone in the state shown on the picture. It doesn't respond to any buttons, and I must always remove the battery to reboot. I don't know if it is hard- or software induced. Does anyone have similiar experience or know what this is?View attachment 5311067
    This is Smart cover screen. to disable go:
    Settings -> Connected Devices (Bluetooth, NFC) -> Connection Preferences (Bluetooth, NFC) -> Smart Cover (Control your accessory behavior) -> Off
     
    • Like
    Reactions: curiousrom

    Lakeerie

    New member
    Apr 29, 2021
    2
    0
    I often find my phone in the state shown on the picture. It doesn't respond to any buttons, and I must always remove the battery to reboot. I don't know if it is hard- or software induced. Does anyone have similiar experience or know what this is?View attachment 5311067
    yesterday i gave my phone my wife. she put it in her pocket - i did'nt know, how to place it on my bike. when she gave it back to me, i had the same screen and i reset it by removing the battery. i guess that in her pocket the home button was constantly pressed.
    Thanks to haggertk for his perfect 18.1 version. i'll spend some money to our local food bank as haggertk supposed to do.
     

    Top Liked Posts

    • 5
      That happens when you pass a magnet near your phone and it thinks you have a smart cover accessory.

      Settings > Connected Devices > Connection Preferences > Smart Cover > Off
      1
      Disabling Smart Cover - FlipFlap

      To my surprise: I find a screenshot of this 'blue screen of death' in my gallery.

      That happens when you pass a magnet near your phone and it thinks you have a smart cover accessory.

      Settings > Connected Devices > Connection Preferences > Smart Cover > Off
      That's right.

      Might as well recycle some screenshots made for an old S5 LineageOS 16.0 thread.

      FYI an other method: if not rooted you can use the adb command method described in How to disable any pre-installed system app bloatware on Android without root using adb.

      These tweaks will survive updates.

      Just go to > Settings > Apps & notifications > 3-dots > Show System > app's name > Advanced > scroll all the way to the bottom to get the package name to be used in adb. In this case it is FlipFlap:

      Windows Command Prompt:

      adb shell pm disable-user --user 0 org.lineageos.flipflap

      Mac/Linux Terminal:

      ./adb shell pm disable-user --user 0 org.lineageos.flipflap
      ***
    • 10
      SDcard corruption may be caused by a recent Google security patch. I experienced this once with the "new" unofficial LOS17 for the Samsung P605, coming from unofficial 14.1,where this never happened before. But others started complaining about the same issue, after this antique rom got a recent security patch.
      It's (likely) not. I've found an issue in the legacy paths of the recent sdfat (Samsung exfat driver) revision. I haven't been able to recreate the bug/assert after the fix. After getting a second confirmation I'll upload the merge the change.

      Every kernel < 4.8.y that had updated to sdfat 1.4.5 is affected.
      7
      Follow-up on corrupted external extfat sdcard

      Test case :

      1/ spotify updates its cached files located on the external extfat sdcard
      2/ spurious reboot occurs
      3/ upon reboot, the scdard is corrupted and can't be mounted

      Diagnosis:

      Checking manually the sdcard using fsck.exfat identifies the corrupted files, which are preventing the card to be mounted : see attached log

      - fsck.exfat identifies the corrupted files but is enable to fix anything, whatever the option

      - fsck.exfat Lineageos version 1.04 (checked in by haggertk)

      - fsck.exfat current version 1.12

      Although this makes no difference because of pending issue #117 : Can't repair corrupted exfat

      - Inserting the sdcard into a PC, Windows detects the issue and offers to "scan and repair" the drive. Once the sdcard is "fixed", it can be used in the PC without problems. Although, a Windows "scanned and repaired" sdcard will still appear as corrupted in Lineageos and can't be mounted.

      Options:

      1/ On another device that can mount the sdcard, delete manually the previously identified corrupted files ; it's usually sufficient to fix the issue.

      2/ Otherwise, backup the sdcard content, reformat (also restore the volumeid), then restore the backup.

      Other thoughts :

      Under stress writing to the sdcard, lineageos can reboot unexpectedly. Since this is not an isolated incident, this should definitely be investigated, since as a result the sdcard will be more likely corrupted and the actual tools don't allow to repair it.

      I am not sure how to recover the log files preceding the reboot, once the device as rebooted. if someone can instruct me how to do so, I'll post them the next time this happens, which is unfortunately too frequently.
      6
      S5 LineageOS 18.1 Update 2021-06-06

      Using the built-in Updater I OTA updated S5 G900M LineageOS 18.1 klte build 2021-05-30 + MindTheGapps + Magisk 23.0 + TWRP 3.5.2_9-0 to build 2021-06-06: everything went smoothly.

      Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :cool: 👍
      ***
      6
      It's (likely) not. I've found an issue in the legacy paths of the recent sdfat (Samsung exfat driver) revision. I haven't been able to recreate the bug/assert after the fix. After getting a second confirmation I'll upload the merge the change.

      Every kernel < 4.8.y that had updated to sdfat 1.4.5 is affected.
      I have been testing @haggertk sdfat patch for the past 24h and I haven't experienced any spurious reboot nor sdcard corruption so far, whereas normally my phone would reboot several times a day and the sdcard card would generally end up being corrupted.
      5
      That happens when you pass a magnet near your phone and it thinks you have a smart cover accessory.

      Settings > Connected Devices > Connection Preferences > Smart Cover > Off
    • 31
      2okPze5.png



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

      LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps) . LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

      Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

      Device source code:
      Kernel source code:

      Build Compatibility:
      The noted models are the only ones supported. If you have a model that isn't listed and ask politely then I might work to add compatibility.
      BuildModel
      klteSM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8
      klteactivexxSM-G870F
      klteaioSM-G900AZ, SM-S902L
      kltechnSM-G9006V, SM-G9008V
      kltechnduoSM-G9006W, SM-G9008W, SM-G9009W
      klteduosSM-G900FD, SM-G900MD
      kltedvSM-G900I, SM-G900P
      kltekdiSC-04F, SCL23
      kltekorSM-G900K, SM-G900L, SM-G900S

      Downloads:
      Installation Instructions:
      Reporting Bugs:
      Compatibility Notes:
      • Bootloader version doesn't matter. Anyone who tells you so doesn't know what they are taking about. My Developer Edition G900V is still running the original 4.4.2 KK aboot. My G900W8 is running the latest 6.0.1.
      • All builds except for klteactivexx and klteaio MUST be running a marshmallow (6.0.1) radio for RIL to work. If you are about to report that RIL/radio isn't working then I pretty much guarantee this is your issue.
      • You MUST be running a marshmallow (6.0.1) NON-HLOS for the fingerprint reader to work. If you are about to report a fingerprint reader problem then you either have old firmware (update it), your /data was previously encrypted and you performed a "clean" flash without FORMATTING /data (start over and FORMAT /data), or your reader is just broken.
      • External SD cards don't support POSIX (ext*, f2fs) or NTFS filesystems anymore. If this affects you then just bite the bullet, copy any data off you really want to save, and reformat as exfat.
      • The latest TWRP seems like it works, but if someone has issues then perhaps try using the actual supported recovery.
      Donations:
      • I absolutely don't personally accept them. If you really feel that this work deserves it, then find a local food bank or animal shelter/rescue and throw some money their way. You can also throw some the way of LineageOS, but we're actually doing pretty well right now.
      10
      SDcard corruption may be caused by a recent Google security patch. I experienced this once with the "new" unofficial LOS17 for the Samsung P605, coming from unofficial 14.1,where this never happened before. But others started complaining about the same issue, after this antique rom got a recent security patch.
      It's (likely) not. I've found an issue in the legacy paths of the recent sdfat (Samsung exfat driver) revision. I haven't been able to recreate the bug/assert after the fix. After getting a second confirmation I'll upload the merge the change.

      Every kernel < 4.8.y that had updated to sdfat 1.4.5 is affected.
      9
      S5 LineageOS 18.1 Update 2021-05-09 - Security Bump, Camera U.I. Fix & Kill App Option

      Using the built-in Updater I OTA updated S5 G900M LineageOS 18.1 klte build 2021-05-02 + MindTheGapps + Magisk 22.1 + TWRP 3.5.2_9-0 to build 2021-05-09: everything went smoothly & GApps + Magisk survived the update.

      There are a bunch of changes as you can see in https://download.lineageos.org/klte/changes/ but of note:

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

      The Vendor security patch level just below it 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.

      See Android Security Bulletin - May 2021 for details about the security fixes.

      With the change Snap: use translucent control background on 16:9 the stock camera is showing the full frame preview again (screenshot). There are other minor Camera changes.

      Interesting also there is a new Kill foreground app option in > Settings > System > Buttons > for Home, Back & Recents buttons which is useful when an app is frozen or you want to prevent it from using some RAM in the background (screenshot). Note that it may make it slower to open that killed app the next time you want to use it.

      BTW you can create a direct link to Updater & much more with the LineageOS Settings widget. I stacked a few of them on Home to create a LineageOS shortcut folder for quick access.

      Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :cool: 👍
      ***
      7
      Galaxy S5 LineageOS 17.1 Upgrade to 18.1 + OTA Update Success Using TWRP

      I upgraded my S5 7 days ago and did not lose any apps & settings: Galaxy S5 G900M LineageOS 17.1 klte build 2021-04-18 + Open GApps Pico + TWRP 3.5.2_9-0 >>> LineageOS 18.1 klte build 2021-04-25 + MindTheGapps for Android 11 ARM + Magisk 22.1 which I just OTA updated to LineageOS 18.1 klte build 2021-05-02: everything went smoothly & GApps + Magisk survived the update.

      The only major issue is the unusable stock Camera as described here: LineageOS Snap Camera U.I. Not Showing the Full Image Preview. Edit: Good news, following a conversation with a dev this commit was merged & will be included in next build: Snap: use translucent control background on 16:9.

      Note: three S5 users so far AFAIK, including @Massedil in his post here, reported not being able to unlock their devices after upgrading to 18.1 from 17.1. I always disable screen & SIM locks before an update or upgrade just to remove variables that may go wrong.

      Old versions of TWRP may fail to apply OTA updates. See How To Update TWRP Using TWRP Itself.

      BTW don't install the TWRP app when offered in TWRP as it may causes bootloop because LineageOS is enforcing priv-app whitelisting rules.

      Several S5 klte variants users reported failed to boot on 17.1 with a modem older than Android 6.0.1. This may also cause No Network or No Service issues on 17.1 & 18.1. See S5 Odin Flashable Modem & Bootloader.

      Also before a major upgrade to a higher version but not before regular updates: Magisk > Uninstall > Restore images to preserve my Magisk settings & modules while disabling Magisk (screenshot).

      Re-flashed Magisk-22.1.zip after successful boot to System after the upgrade.

      MindTheGapps is similar to Open GApps Nano. See Open GApps Package Comparison.

      Searching apps with Google in /System:
      • Android Accessibility Suite
      • Android Auto
      • Android Setup
      • Data Transfer Tool
      • Exchange Services
      • Google (search app)
      • Google Calendar Sync
      • Google Contacts Sync
      • Google Partner Setup
      • Google Play services
      • Google Play Store
      • Google Services Framework
      • Google Text-to-speech Engine
      • Market Feedback Agent
      • Markup
      You can also download the MindTheGapps package, unzip & search it with apk.

      You can disable the Google's search app with it's optional personal data hungry Assistant in it's app info. Which I did because it has too many running services for my taste.

      AFAIK from the available Open GApps for Android 11 test builds 20210130 @ the present, only the Pico package was reported as issue free in the Open GApps support thread on XDA: GAPPS DAILY Open GApps for Android; All Android Versions & Devices.

      I have been an Open GApps Pico user for years on several devices but since there are no official releases for Android 11 @ the present, I decided to test MindTheGapps because that's what LineageOS links to @ the present in https://wiki.lineageos.org/gapps.html and wanted to post about it.

      See https://wiki.lineageos.org/devices/ > {device} > Upgrade to a higher version of LineageOS.

      After a full TWRP backup (including the important EFS partition but except the Cache) & triggering a fresh Google Backup* (Settings > System > Advanced > Backup in 17.1), I did the same steps as described in that upgrade guide except that I use TWRP 3.5.2_9-0 so sideload must be started manually on the S5 before sideloading from the computer: TWRP > Advanced > ADB Sideload > Swipe to Start Sideload.

      Or simply copy the files to the device & flash from there using TWRP.

      To make the TWRP backup smaller I use SD Maid > AppCleaner to clear the cache of all apps & make sure to delete all downloaded updates in Updater by long pressing them or if rooted move them from /data/lineageos_updates/ to external or internal SD Card.

      In case of failing to boot you can restore only the System, Data & Boot (boot.img is actually the kernel) partions from the full backup.

      Obviously there are other backup methods but that's the one I use since a couple of years & restored them both successfully.

      On some devices, some versions of TWRP do not work well with LineageOS 18.1 and the Lineage recovery is recommended in those cases but on my S5 klte, TWRP wins hands-down with it's backup/restore feature, File Manager, installing both manually or via sideload & applying successfully OTA updates so I don't see any reasons for switching to the Lineage recovery @ the present.

      Tip: to make the S5 18.1 U.I. faster & more fluid when opening the apps drawer, scrolling through home pages, opening Settings, etc: > Settings > Accessibility > toggle on Remove animations.

      Try it before & after as fast as you can to see the difference.

      *: Warning for people using a pattern lock screen see this bug report: Google cloud backup cannot be restored when using a 4x4, 5x5 or 6x6 lock screen pattern
      ***

      Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :cool: 👍
      ***
      7
      Follow-up on corrupted external extfat sdcard

      Test case :

      1/ spotify updates its cached files located on the external extfat sdcard
      2/ spurious reboot occurs
      3/ upon reboot, the scdard is corrupted and can't be mounted

      Diagnosis:

      Checking manually the sdcard using fsck.exfat identifies the corrupted files, which are preventing the card to be mounted : see attached log

      - fsck.exfat identifies the corrupted files but is enable to fix anything, whatever the option

      - fsck.exfat Lineageos version 1.04 (checked in by haggertk)

      - fsck.exfat current version 1.12

      Although this makes no difference because of pending issue #117 : Can't repair corrupted exfat

      - Inserting the sdcard into a PC, Windows detects the issue and offers to "scan and repair" the drive. Once the sdcard is "fixed", it can be used in the PC without problems. Although, a Windows "scanned and repaired" sdcard will still appear as corrupted in Lineageos and can't be mounted.

      Options:

      1/ On another device that can mount the sdcard, delete manually the previously identified corrupted files ; it's usually sufficient to fix the issue.

      2/ Otherwise, backup the sdcard content, reformat (also restore the volumeid), then restore the backup.

      Other thoughts :

      Under stress writing to the sdcard, lineageos can reboot unexpectedly. Since this is not an isolated incident, this should definitely be investigated, since as a result the sdcard will be more likely corrupted and the actual tools don't allow to repair it.

      I am not sure how to recover the log files preceding the reboot, once the device as rebooted. if someone can instruct me how to do so, I'll post them the next time this happens, which is unfortunately too frequently.
    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