[ROM][UNOFFICIAL-ABANDONED][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)

Search This thread
SMS Issue - Modem & Bootloader Update

Thank you for providing klteaio for our beloved SM-G900AZ!

SMS messages aren't working, I suspect as mentioned in the OP that a modem firmware upgrade would probably fix it. But does anyone know where can I find such a firmware .bin to flash with Odin, or is the only option to do a full/clean install with stock ROM?

What do you mean by "SMS messages aren't working" exactly? You can't send or receive or both? Are you using the LineageOS stock Messaging app?

Check the APN settings and make 100℅ sure that they are identical to your network provider's recommendations.

In LineageOS 17.1: > Settings > Network & internet > Mobile network > Advanced > Access Point Names > APN. Maybe it's the same path in 18.1?

How old is your SIM?

I am asking because on S3 i9300 LineageOS 14.1 for 2 weeks I could receive but not send SMS. Then I bought a Galaxy S5 SM-G900M & on LineageOS inserted that old SIM and still had the can't send SMS problem + was not getting LTE.

Went to my network provider's shop & got a new SIM & LTE appeared instantly on the status bar after booting it. And the SMS problem was solved.
***

See S5 Odin Flashable Modem & Bootloader. While nobody made a package for the SM-G900AZ yet, you can see a list of firmware files that you could extract from stock Samsung OS & make one that you could share so I could add it.

What does it say in Settings > About phone > Android version > Baseband version?

Looking in sammobile's stock firmwares for the SM-G900AZ here and on updato here I don't see anything more recent than 2017-05-14 Android 5.0 G900AZTUS3BQD1.

Their paywall policies varies apparently randomly depending on the device & age of the OS but I used both sammobile.com & updato.com to download stock Samsung OS. Some users recommend samfw.com.

They all have flashing instructions using Odin3 in their respective download pages.
***
 
Last edited:
  • Like
Reactions: lavamind

lavamind

New member
Mar 14, 2021
3
3
@curiousrom Thanks for the detailed reply! The issue was with sending SMS. Receiving worked fine. After reviewing your message the first thing I tried was to switch to the stock Messages app (from Signal), and there was no problem at all sending/receiving SMS with it! Switched back to Signal and the problem appears to be solved. In case it might help someone else, my baseband version is G900AZTUS3BOGD.
 
  • Like
Reactions: curiousrom
Re: SMS Issue Signal & Messaging - Modem & Bootloader Update

@curiousrom Thanks for the detailed reply! The issue was with sending SMS. Receiving worked fine. After reviewing your message the first thing I tried was to switch to the stock Messages app (from Signal), and there was no problem at all sending/receiving SMS with it! Switched back to Signal and the problem appears to be solved. In case it might help someone else...

You are welcome & thanks for reporting back about how you fixed it. :cool:👍

...my baseband version is G900AZTUS3BOGD

Checking on updato.com here > G900AZTUS3BQD1 > updato uses the label Phone for the modem/baseband/radio: G900AZTUS3BQD1.

The higher the last 4 alphanumeric characters, the more recent it is but since Samsung does not document it's modem changes I don't know if you would gain anything by updating.

Rule of thumb: if it ain't broke, don't fix it. ;)
***
 
S5 Mic Boost Magisk Module - Stereo Recordings

Why is the microphone so quiet when making phone calls and voice messages?
Doesn't anyone have a tip for me?

If your device is rooted with Magisk, thanks to a post by @dcarvil in the old 16.x thread here for inspiration, I created a module for myself for a S5 G900M klte to boost the mic via the mixer_paths.xml because my WhatsApp's sound messages were too low.

I did not create a module installer for it yet but you can download the attached Module_mixer_paths_mic_Boost_curiousrom.zip, unpack it and copy the mixer_paths folder to /data/adb/modules & reboot.

After that in the Magisk app > Modules: enable mic_boost_118 as seen in the screenshot & reboot.

I boosted the value for both mics near the USB port and the one on the top of the S5 next to the IR blaster from 95 to 118. If you change it to a higher value expect some distortions in some apps:

Code:
<!-- Recording Scenario  -->
    <path name="rec-main-mic">
        <path name="main-mic" />
        <ctl name="DEC2 Volume" value="118" />
    </path>

    <path name="rec-sub-mic">
        <path name="sub-mic" />
        <ctl name="DEC4 Volume" value="118" />
    </path>

I use a vacuum cleaner once in a while to clean the USB port, the mic hole next to it & also the top mic hole next to the IR blaster which is used when you have stereo recording enabled in some third-party recording apps like Easy Voice Recorder for example. (screenshots)

You can modify the mixer_paths/system/vendor/etc/mixer_paths.xml file in that module folder if you want to change the values of other stuff & reboot to apply.
***
 

Attachments

  • Module_mixer_paths_mic_Boost_curiousrom.zip
    4.6 KB · Views: 40
  • Magisk_Module_mic_boost_118_S5_curiousrom.png
    Magisk_Module_mic_boost_118_S5_curiousrom.png
    147.2 KB · Views: 90
  • Easy_Voice_Recorder_S5_curiousrom.png
    Easy_Voice_Recorder_S5_curiousrom.png
    431.7 KB · Views: 89
  • Easy_Voice_Recorder_Stereo_S5_curiousrom.png
    Easy_Voice_Recorder_Stereo_S5_curiousrom.png
    107.5 KB · Views: 86
Last edited:

CHGICEMAN

Senior Member
  • S5 Mic Boost Magisk Module - Stereo Recordings




    If your device is rooted with Magisk, thanks to a post by @dcarvil in the old 16.x thread here for inspiration, I created a module for myself for a S5 G900M klte to boost the mic via the mixer_paths.xml because my WhatsApp's sound messages were too low.

    I did not create a module installer for it yet but you can download the attached Module_mixer_paths_mic_Boost_curiousrom.zip, unpack it and copy the mixer_paths folder to /data/adb/modules & reboot.

    After that in the Magisk app > Modules: enable mic_boost_118 as seen in the screenshot & reboot.

    I boosted the value for both mics near the USB port and the one on the top of the S5 next to the IR blaster from 95 to 118. If you change it to a higher value expect some distortions in some apps:

    Code:
    <!-- Recording Scenario  -->
        <path name="rec-main-mic">
            <path name="main-mic" />
            <ctl name="DEC2 Volume" value="118" />
        </path>
    
        <path name="rec-sub-mic">
            <path name="sub-mic" />
            <ctl name="DEC4 Volume" value="118" />
        </path>

    I use a vacuum cleaner once in a while to clean the USB port, the mic hole next to it & also the top mic hole next to the IR blaster which is used when you have stereo recording enabled in some third-party recording apps like Easy Voice Recorder for example. (screenshots)

    You can modify the mixer_paths/system/vendor/etc/mixer_paths.xml file in that module folder if you want to change the values of other stuff & reboot to apply.
    ***
    YOU are my hero of the day. I was pretty desperate.
    I wonder why the ROM manufacturer doesn't install this right away!
     
    • Like
    Reactions: curiousrom

    aventurer

    Member
    Mar 8, 2016
    25
    7
    ROM seems good so far, but haven't tested too much on it. Anyone have ideas why I can't get signature spoofing to work on this? I've tried SmaliPatcher, Haystack11 method (creating new services.jar and pushing over), and can't seem to get it to work.

    Excellent work though, thanks to the developers of this ROM.
     

    kurtn

    Senior Member
  • Jan 28, 2017
    4,008
    1,730
    Small town in Bavaria
    @aventurer
    ROM seems good so far, but haven't tested too much on it. Anyone have ideas why I can't get signature spoofing to work on this? I've tried SmaliPatcher, Haystack11 method (creating new services.jar and pushing over), and can't seem to get it to work.

    Excellent work though, thanks to the developers of this ROM.
    Signature Spoofing for Android 11
    Guide by bluede-v Will

    First of all Flash your ROM and Magisk (you need to download the latest version to get Magisk working on Android 11)

    Click on Build number (7x) to enable Developer Options

    After that enable ADB-Debugging and Root-ADB-Debugging in your ROM in case of LineageOS go to Setting -> System -> Developer Options

    So Lets go this is the more complicated part. but also really easy if you done it once.

    I'm using Debian Linux but it should be possible on every OS. In Windows use the Linux Subsystem.

    You need to have ADB installed on your System tho.

    ADB link: https://adbdownload.com

    First of all you need to download this 2 Files:


    Rename "spoof\_AVDapi30.zip.ONLY'MAGISK&ANDROID-STUDIO" to "spoof\_AVDapi30.zip"

    Next Download this zip: https://gitlab.com/oF2pks/haystack/-/archive/11-attempt/haystack-11-attempt.zip

    Also download this jar file: https://github.com/DexPatcher/dexpa...nload/v1.8.0-beta1/dexpatcher-1.8.0-beta1.jar

    So now unzip the haystack-11-attempt.zip and put the dexpatcher.jar file into to Folder.

    This part I use Bash shell in Linux.
    Bash:
    adb pull /system/framework/services.jar

    java -jar dexpatcher-1.8.0-beta1.jar -a 11 -M -v -d -o ./ services.jar 11-hook-services.jar.dex 11core-services.jar.dex
    (After that Command you should have 4 files all named classes*.dex)
    Bash:
    mkdir repack

    zip -j repack/services.jar classes*.dex
    After that you should have a new services.jar in your repack Folder.

    Now You need to open the spoof\_AVDapi30.zip go in /system/framework/ and delete the old services.jar and put your own file in. that's in your repack Folder.

    Don't ruin the zip-format of the file tho because otherwise Magisk will cry while install.

    After that put your spoof-AVDapi30.zip and your microG\_AVDx86api30\_magiskMaRViN.zip on your Phone and Flash via Magisk.

    Reboot and you hopefully have Signature spoofig working. If you run in any Problems check out the GitHub Links here. there will be comments that maybe will help.

     

    aventurer

    Member
    Mar 8, 2016
    25
    7
    @kurtn Ty. This is the exact Haystack11 method I tried. As soon as I flash spoof_AVDapi30.zip and reboot I get stuck in a bootloop. I tried it twice, but it's possible I somehow missed a step. Even after pushing the services.jar file over Signature Spoof Checkers still say disabled, but when I try to flash NanoDroid Patcher (I know it doesn't work on Android 11) for the heck of it, it stops out saying signature spoofing is already enabled.

    Were you able to get it to work on the S5? I'm trying on the SM-G900T.
     

    kurtn

    Senior Member
  • Jan 28, 2017
    4,008
    1,730
    Small town in Bavaria
    @kurtn Ty. This is the exact Haystack11 method I tried. As soon as I flash spoof_AVDapi30.zip and reboot I get stuck in a bootloop. I tried it twice, but it's possible I somehow missed a step. Even after pushing the services.jar file over Signature Spoof Checkers still say disabled, but when I try to flash NanoDroid Patcher (I know it doesn't work on Android 11) for the heck of it, it stops out saying signature spoofing is already enabled.

    Were you able to get it to work on the S5? I'm trying on the SM-G900T.
    Sorry, I didn't try myself. It's not just about preparing services.jar, but also some trick with magisk. Maybe you should discuss that in the linkage thread.
     
    • Like
    Reactions: curiousrom

    aventurer

    Member
    Mar 8, 2016
    25
    7
    Sorry, I didn't try myself. It's not just about preparing services.jar, but also some trick with magisk. Maybe you should discuss that in the linkage thread.
    Yep that was all. It works!

    All you need to do is copy the newly created services.jar into the right place in spoof_AVDapi30.zip and flash via Magisk. I didn't need to push services.jar onto my phone.
     
    • Like
    Reactions: ludwig83 and kurtn

    wolfiediscord

    New member
    Nov 17, 2018
    2
    1
    Hey! Great ROM so far. I have been experiencing an annoying issue with my S5.
    Problem: When downloading an album using Apple Music (no google services) to the external SD card, a kernel panic occurs.
    Model: SM-G900T
    Build Number: lineage_klte-userdebug 11 RQ2A.210305.006 eng.hagger.20210306.053118 test-keys

    Since this was a random reboot, the last_kmsg is located here. I am also using TWRP, but this is not an issue with the recovery, as the LineageOS recovery wouldn't make a difference in a kernel panic.

    EDIT: Reformatting the SD Card as exFat makes no difference. The device still kernel panics.
    EDIT 2: Downloading to the Internal Storage is fine, it is just the SD card that makes it kernel panic.
    EDIT 3: Found a temporary workaround. Download the music using the internal storage, then transfer it to the external SD card.
     
    Last edited:
    • Like
    Reactions: pmduper
    Official LineageOS 18.1 Launched!

    FYI the Official LineageOS 18.1 is launched as you can read in this official blog: Changelog 25 - Exemplary Eleven, Ravishing Recorder, Captivating Calendar, Beaming Backup

    The first batch of builds should be available starting 2021-04-01 if all goes well with with the LineageOS automated builder. Click on nightly even if the lineage-16.0 label has not been updated yet.

    Note that the Galaxy S5 klte family is not included in the initial promotion but should follow eventually.
    ***
     
    Last edited:

    haggertk

    Senior Member
    Note that the Galaxy S5 klte family is not included in the initial promotion but should follow eventually.

    I'll probably ship in the coming week. They're ready, but I don't want to be the first set our the door on the infra. As it is, we're already flying this thing in direct law tonight.
     
    I'll probably ship in the coming week. They're ready, but I don't want to be the first set our the door on the infra. As it is, we're already flying this thing in direct law tonight.
    Many thx for your good work!. Just a short question regarding the update procedure from 18.1 unofficial to 18.1 official. Will this be done with the settings/system/"updater" or do we have to "dirty flash" a complete new image via TWRP (i use twrp instead of lineage recovery. pls. forgive me :) )

    I found another spare S5 on my stock. Maybe its worth to do a fresh new install of 18.1 including Lineage recovery with that. This is good for some training with the new recovery.

    What is the official maintainers opinion whiche recovery is the best one?mean the one which is supported at the highest level. if you @haggertk tell me its Lineage recovery cause your tests have been done with that - then i will go from TWRP to official lineage recovery to support your work!
     
    Last edited:

    ludwig83

    Member
    May 9, 2018
    25
    13
    Many thx for your good work!. Just a short question regarding the update procedure from 18.1 unofficial to 18.1 official. Will this be done with the settings/system/"updater" or do we have to "dirty flash" a complete new image via TWRP (i use twrp instead of lineage recovery. pls. forgive me :) )

    I found another spare S5 on my stock. Maybe its worth to do a fresh new install of 18.1 including Lineage recovery with that. This is good for some training with the new recovery.

    What is the official maintainers opinion whiche recovery is the best one?mean the one which is supported at the highest level. if you @haggertk tell me its Lineage recovery cause your tests have been done with that - then i will go from TWRP to official lineage recovery to support your work!
    Hey! In my opinion, there is no need for TWRP any more...Lineage Recovery is real simple and it works fine...
    Best Regards...
     
    Hi Ludwig, yes my thoughts either. TWRP is a 3rd party "product" with some nice features. But looking back, i only used it for flashing the next release ROM to the phone. I do not use the magisk stuff, i am just a happy LOS user currently trying to get rid of the google stuff. Therefore the only usecase for me is flashing/updating/upgrading the phone and i assume the LOS recovery is the best solution for things like that.
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 1
      @jimsters sure it's ok to post but might get more attention if not posted in an abandoned thread. 😉
      This is official now.
      1
      @jimsters sure it's ok to post but might get more attention if not posted in an abandoned thread. 😉
      This is official now.
      ah ok thanks
    • 53
      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:
      My picks:

      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:
      • Download latest build
      • Boot into recovery
        • Lineage recovery images are included in the download section and that's what I support. If you feel like using TWRP and something isn't working then take it up with the TWRP maintainer
      • If not updating from one of my earlier unofficial builds, then format/system, /data, and /cache
        • For Lineage recovery:
          • Format -> Format data/factory reset (this does /data and /cache)
          • Format -> Format system partition
        • For TWRP figure it out. And no, "wipe data" isn't the same as formatting data
      • Install LineageOS zip
      • If this is your initial installation of LineageOS 18.1, then flash any addons (e.g., gapps)
      Reporting Bugs:
      • DO NOT even think about reporting bugs if you are running a custom kernel, Magisk, or Xposed
      • Grab a logcat after the problem has occurred
      • If there is a random reboot then grab /proc/last_kmsg. A logcat AFTER the reboot will be worthless
      • Note which build AND device you have
      • Read the thread, at least the last month's worth of posts. Don't report things that others already have.
      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 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. It was kind of broken in 17 and we likely won't merge the changes to add it back in for 18. I'm not going to pick the open changes to re-add support because I'm not going to deal with "but it worked on haggertk's unofficial builds" bug reports after we eventually go official. If this affects you then just bite the bullet, copy any data off you really want to save, and reformat as exfat.
      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.
      23
      Note that the Galaxy S5 klte family is not included in the initial promotion but should follow eventually.

      I'll probably ship in the coming week. They're ready, but I don't want to be the first set our the door on the infra. As it is, we're already flying this thing in direct law tonight.
      9
      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: 👍
      ***
      9
      Official LineageOS 18.1 Launched!

      FYI the Official LineageOS 18.1 is launched as you can read in this official blog: Changelog 25 - Exemplary Eleven, Ravishing Recorder, Captivating Calendar, Beaming Backup

      The first batch of builds should be available starting 2021-04-01 if all goes well with with the LineageOS automated builder. Click on nightly even if the lineage-16.0 label has not been updated yet.

      Note that the Galaxy S5 klte family is not included in the initial promotion but should follow eventually.
      ***
      7
      Hey @haggertk, I have a SM-S902L. Can I use the rom for SM-S900L for my device? If not would you be so kind and add support for my model? I had been waiting for lineage 17.1 for quite some time now and installed an unofficial build to get android 10. I just found this amazing thread which is a way for me to get android 11. :love: Please consider my request. Thanks ;)

      Yeah, that's easy -- I dropped G900AZ and S902L during 17.1 bring-up because I wasn't about to formally fork a device tree and create a new build for those devices that needed <M RIL stack without any evidence of a continuing userbase. I have the work already done locally for 17. One commit in that device tree and then importing the vendor blobs will have it done for 18.