Maybe they haven't shut down HSPA(+) in major cities yet.

I'm gonna miss this phone when it's finally time to retire it. It's been an adventurous couple of years since I bought it for $50 in 2019.

Every time i update the rom i have to reinstall magisk and change some properties in build.prop for the samsung watch to work.
How can i get both of them to survive OTA updates?

rena_ said:

Every time i update the rom i have to reinstall magisk and change some properties in build.prop for the samsung watch to work.
How can i get both of them to survive OTA updates?

Magisk should survive, if you flash the apk in recovery. No idea with build prop. I only use gadgetbridge.

Boatshow said:

I noticed the firmware repository now has baseband G900TUVU1GRJ1 for the SM-G900T. It's actually pretty old but nobody could source it for a while, nice!

Anyone have any remarks about it before I flash it?

I realize this was awhile ago, but do you still have a copy of this or know where I could find it?

Also I still have HSPA(+) service as well and I am in the US.

Gavin Capacitor said:

I realize this was awhile ago, but do you still have a copy of this or know where I could find it?

Also I still have HSPA(+) service as well and I am in the US.

I never ended up flashing whatever I downloaded (if it ain't broke break it later) but there's a firmware repository in the first post of this threadand it has a G900TUVS1GPK3_G900TUVS1GPK3_baseband_firmware.tar.md5. Not sure what that corresponds to and T-Mobile's removed the software update log.

Boatshow said:

I never ended up flashing whatever I downloaded (if it ain't broke break it later) but there's a firmware repository in the first post of this threadand it has a G900TUVS1GPK3_G900TUVS1GPK3_baseband_firmware.tar.md5. Not sure what that corresponds to and T-Mobile's removed the software update log.

So I downloaded that and flashed it - it gives me the baseband G900TUVS1GPK3 (December 15, 2016). I had (and re-flashed back to) baseband G900TUVU1GQC2 (April 2, 2017). I managed to find an archive of the t-mobile support page which is where I'm getting the dates from: T-Mobile S5 Firmware

The one you mentioned in the original post - G900TUVU1GRJ1 (December 6, 2018) - is afaik the latest one so I was hoping you had it. My calls are kinda garbled if they aren't over HSPA and I thought that baseband might help because it mentions a DTMF fix. If anyone has it I would appreciate it.

Incidentally I have the full stock firmware for G900TUVU1GQC2 if anyone wants it.

Hello guys,

first thanks for supporting the klte. Thanks to this fantastic ROM my girlfriend could use her old S5 for several more years before switching to a new S20FE.

Now my primary phone broke and I installed the latest LineageOS.
All working really smooth so far apart from the fingerprint reader.
It wouldn't react when I swipe down the home button when trying to setup fingerprint unlock.
The fingerprint reader was working before, just don't remember whether it was in an earlier LineageOS version or with stock since she preferred to use the pattern unlock method and it was too long ago I tried out the fingerprint reader.
I verified installed firmware as requested in the first post. Baseband version is reported as G900FXXU1CQK3, so I guess it should be fine?
Earlier on the phone was running LineageOS 16.0 and I wiped all partitions before installing lineage-18.1-20220731-nightly-klte-signed through TWRP.
Would it still make sense to update using G900FXXU1CSA1_G900FXXS1CQA4_baseband_firmware.tar.md5 from the downloads?
If so what's the correct procedure to do this with Odin without losing all data? Looking at the contents of the archive I only see smaller sized partitions but just want to be sure I don't wipe any userdata by ticking the wrong checkboxes.
Unfortunately the URL (https://jira.lineageos.org/browse/BUGBASH-257) which explains the process that I found after some research is not accessable anymore (also no archived version on archive.org), so sorry for asking this question.
Any help appreciated!

Edit: I was brave and flashed G900FXXU1CSA1_G900FXXS1CQA4_baseband_firmware.tar.md5 with CP option in Odin. Now baseband version reported is G900FXXS1CQA4.
Unfortunately fingerprint reader is still not working.

Since i configured the fingerprint reader, my battery very very often is empty. Removing the configured fingerprint or dirty flash doesn't help, so i have to flash it again with formatting data. I had read about this problem before but i had the impression the problem had be gone.

S5 LineageOS 18.1 Update 2022-08-14 - Android Security Bump

Using the built-in Updater I OTA updated S5 G900M LineageOS 18.1 klte build 2022-07-17 + MindTheGapps + Magisk 23.0 + TWRP 3.6.2_9-0 to build 2022-08-14: everything went smoothly as usual & GApps + Magisk survived the update.

There are several changes listed in https://download.lineageos.org/klte/changes/ but most importantly it includes the monthly Android security bump: Bump Security String to 2022-08-05 and if you click on the left side of that page on Topic R_asb_2022-08 you will see that they are all related to that security bump and all made by Mr. haggertk.

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

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 - August 2022 for details about the security fixes.

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

S5 Screen Lock Fingerprint Battery Usage

rena_ said:

Since i configured the fingerprint reader, my battery very very often is empty. Removing the configured fingerprint or dirty flash doesn't help, so i have to flash it again with formatting data...

Several S5 users including myself reported excessive battery usage after registering some fingerprints.

Check this test I made on 17.1, did not try on 18.1 but it's the same I presume: S5 Screen Lock Fingerprint Battery Tests @ Idle - BetterBatteryStats

Maybe you had something else also eating the battery because I follow the S5 threads since 15.1 & did not see an other user saying that he needed to format after removing the registered fingerprints.

Besides using BBS as described in the test linked above check this post for more battery usage analysis using GSam: S5 klte LineageOS 18.1 Battery Usage @ Idle Test - Sleeps Like a Rock
***

millenixGER said:

...I installed the latest LineageOS.
All working really smooth so far apart from the fingerprint reader.
It wouldn't react when I swipe down the home button when trying to setup fingerprint unlock.
The fingerprint reader was working before, just don't remember whether it was in an earlier LineageOS version or with stock... I was brave and flashed G900FXXU1CSA1_G900FXXS1CQA4_baseband_firmware.tar.md5...

You installed a recent vendor's firmware so it's probably a hardware issue as our S5s are getting older.

The best way to confirm or rule out a hardware issue is to flash the most recent Samsung's OS for your device but why bother because as you can read above the fingerprint reader may eat the battery on LineageOS.

"If so what's the correct procedure to do this with Odin without losing all data?" - You did it successfully but for other users wondering see S5 Odin Flashable Modem & Bootloader.
***

millenixGER said:

Hello guys,

first thanks for supporting the klte. Thanks to this fantastic ROM my girlfriend could use her old S5 for several more years before switching to a new S20FE.

Now my primary phone broke and I installed the latest LineageOS.
All working really smooth so far apart from the fingerprint reader.
[...]

When coming from a non-Lineage version you need to format data in twrp instead of just wiping it. Otherwise you'll have those issues with the fingerprint scanner.

Regards,
Zy.

where can i find twrp for sm-g870a?