yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] Garry58:
Seems like it, good point. Though, when you set it to Black, other notification lights are still suppressed? I had an unread message and no light, assuming because it was charging (even though it was set to black). Could be something else.
[Samsung Galaxy S 5 Unified Development] x2k13:
I don't really know if this is the right place to discuss this, as I don't now if it's releated to LOS 18.1 on klte only, so please be patient with me.

I have some sort of "cosmetic" problem which I can't seem to find a solution to.

I had an sd-card formatted as external/removable storage which appeared (during runtime) in /storage as mount point labeled "E9AF-B328" (see attached image as well). The FS on the card is exfat, obviously.

Yesterday the card began acting up, LOS telling me it can't read anything and the card has to be formatted first...and so on. So I took the card over to my pc and it mounted without problems, dmesg on console saying "device wasn't unmounted properly..fsck.." Okay, no problem, lets do this.

I backuped the sd-card's contents to my PC, reformatted the card to extfs, copied the backup back, inserted it in my G900F, booted. System asked me to choose what to use the card for, tapped removeable storaged, et voila, all good again, just had to re-map some storage paths for a few apps, no big deal.

Now for the "cosmetic" part:

When browsing to /storage with a file manager, I noticed that the "new" card had been mounted as "BA04-0366", which is okay, since the FS on the card is new and so has a different ID. But, the old mount point "E9AF-B328" is still there.

I tried to find the file that must have stored the setting to add the mount point to /storage, but had no luck.

Deleting it from /storage manually doesn't work, because it will get replaced the second I delete it. Which is weird because on Linux the mount point will be just gone, so I was expecting this to be the case on Android as well.

So the old mount point must have been stored in a file I don't know where it is to edit/comment that mount point out. The different fstab files I could find on the phone don't contain the mount point's ID. I ran out of ideas.

All this is no showstopper, don't get me wrong. I just want to know if anyone knows a proper solution to this.

:)

TL;DR

Old sd-card mount point still in /storage, cannot remove it, how to do it?
[Samsung Galaxy S 5 Unified Development] kurtn:
Shutting down android does not automatically eject the SD card. You have to tap eject before removing SD.
[Samsung Galaxy S 5 Unified Development] jenssa:
I tried today to update from the April 25th build to the May 2nd build (LineageOs 18.1 for klte), and it didn't boot. It got almost up but was always thrown back into TWRP recovery. I tried a few times and also tried to wipe Dalvik and Cache, but to no avail. Had to reinstall April 25th build from recovery.
[Samsung Galaxy S 5 Unified Development] x2k13:
So what can I do now?

Okay, here's what I've tried so far:

Ejected the new card during runtime, then shutdown. Took another, identical card, formatted it on console like this:

sudo mkfs.exfat -i E9AFB328 /dev/sdd1

resulting in

File system exfat, labeled E9AF-B328 (the same as the othe card had before).

Inserted card, rebooted, system showed this mount point active, but – the other one that had been added using the newly formatted card is now inactive but still there. The same situation, actually.
[Samsung Galaxy S 5 Unified Development] kurtn:
Some strange GApps or magisk?
[Samsung Galaxy S 5 Unified Development] jenssa:
I cannot say. I am a complete amateur in this business, but for what it is worth, I don't think the problem lies with either of them. For the record: I use the BiTGApps-arm-11.0.0-R19_signed, and am very happy with it. I have a problem with Magisk - it fails the Safetynet test, but as it does manage to hide root from my bank apps, that doesn't matter much to me. It did pass the Safetynet in the unofficial builds of los 18.1, but I haven't been able to install Magisk by the recommended method (fastboot - I'm not even sure if one can use fastboot on the SM-G900F?). Sorry to be of so little help.
[Samsung Galaxy S 5 Unified Development] kurtn:
I would try to uninstall magisk before ota update.
[Samsung Galaxy S 5 Unified Development] Bifidusse:
I registered only to thank you haggertk for this support. I especially bought a second-hand klte to replace my FP1 for which there's no update available anymore. This is awesome, you made the job Samsung (and many others) didn't. Thank you so much !

At this time everything works, but I haven't test all the apps I use on a daily basis.
[Samsung Galaxy S 5 Unified Development] jenssa:
Thanks, you're right! I was unable to uninstall Magisk (tried all the tricks), and after a lot of fuzz I was able to install los recovery again and perform a full factory reset. That seems to have gotten rid of Magisk. The update now seems to work. Now I need to install Magisk again. However, I have not succeeded using the patched_image method.
[Samsung Galaxy S 5 Unified Development] kurtn:
My preferred installation method: rename apk to zip and flash in recovery

My preferred uninstallation tap uninstall in app
[Samsung Galaxy S 5 Unified Development] wuko:
Hallo,

S5,klte, last nightly, Trebuchet launcher

adopted Sdcard

Symbols from new installed apps vor moved from drawer to homescreen

are deleted from homescreen after

restart.

Any advice ????
[Samsung Galaxy S 5 Unified Development] x2k13:
Had the same problem. Switched to another launcher.
[Samsung Galaxy S 5 Unified Development] jenssa:
Thanks, I think it works smoothly now. My only question is whether to install twrp again. It was a hazzle to swope it with los recovery, but the latter doesn't provide a back-up solution. Do we need that, or is Titanium sufficient for most purposes?
[Samsung Galaxy S 5 Unified Development] x2k13:
I think TWRP is the solution you want. You can do full backups and installing is really easy using heimdall in download mode. Updating TWRP is easy as well, just flash the .img to recovery and that's it. Major plus is the ability to decrypt data partition when the phone is encrypted. LOS recovery lacks that function completely, so basically all you can do with LOS recovery is OTA updates and wipe the phone.
[Samsung Galaxy S 5 Unified Development] jenssa:
Thanks for all your kind help. I'm now back on twrp recovery. (But I had to flash in Odin - cannot use fastboot on Samsung, it seems, nor did I get Heimdall to work. I'm ok now, however.)
[Samsung Galaxy S 5 Unified Development] curiousrom:
Failed OTA Update BiTGApps - Script: Capture Bootloop Logcat - Magisk SafetyNet Test

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.

It may also be an issue with BiTGApps's update survival script which should be located in the /system/addon.d/ folder.

Try using MindTheGapps which worked for me as described in Galaxy S5 LineageOS 17.1 Upgrade to 18.1 + OTA Update Success or use the Open GApps Pico for Android 11 ARM test build linked in that post.

Both can be dirty flashed without affecting the apps you installed, their data & your settings: flash both LineageOS followed by the GApps package in one go without wiping anything except the Dalvik / Art cache & Cache.

***

Script: Capture Bootloop Logcat - Recovery Log

You can find a recovery log after a successful or failed OTA update or manual update in the /cache/recovery/ folder which may help troubleshooting an issue.

A logcat may help find the reason a device fails to boot.

Magisk may be able to create a logcat of a failed boot or bootloop in /cache/ if you use a script in /data/adb/post-fs-data.d even if the device does not boot to System.

For more info see https://www.didgeridoohan.com/magisk/MagiskHelpBugs > Logcat boot script.

I attached a script I created for my S5 with @DiamondJohn's amazing & nerdy TeMeFi app which keeps two 30 seconds long logcats of the last 2 boots named for example: 20210502061513_boot_logcat.log.

Just unzip the attached logcat_on_boot_Magisk_curiousrom.zip and copy the script logcat_on_boot to the /data/adb/post-fs-data.d/ folder, set the file's permissions to rwx r-x r-x 755 & reboot. Then check in /cache/ to see if it worked.

My script settings:

###################################################################
## Set up all the variables / parameters
temp_file_location="/cache";
file_postfix="_boot_logcat.log";
temp_file_name="$(date +"%Y%m%d%H%M%S")";
dest_file_location="/cache";
let max_wait_for_mount_sec=300;
dest_file_name="$temp_file_name";
logcat_length_sec=30;
test_mount_file="DUMMY_TEST_DELETE_ME";
max_number_of_logs=2;
extra_logs="Y";
###################################################################

If you want to create a custom script for yourself: TeMeFi > Magisk > scroll all the way down to Logcat of Boot.

***

Magisk SafetyNet Test Failing - API Error

Maybe it's just a bug with the SafetyNet test API in Magisk 22.0 & 22.1 as seen in the attached screenshot. That has been reported many times in the XDA Magisk support thread because it seems to work with your bank's app.

Just make sure you enabled MagiskHide in Magisk's settings.

Test with apps like SafetyNet Test or SafetyNet Helper Sample for example like in the attached screenshot which I just made.

***
[Samsung Galaxy S 5 Unified Development] jenssa:
I haven't experienced that problem. Trebuchet is still on the phone, and remains inert. However, I have had a few instances of Nova stopping too, and the phone is rather slow, even if better than with Trebuchet. Perhaps there are still better launchers. My main problem now is to pass the safetynettest with Magisk. I haven't been able to flash the patched-boot.img from the PC, and have instead flashed it in Twrp from internal storage. It doesn't seem good enough, even though the Magisk looks alright. I use the latest canary build. Any suggestions?
[Samsung Galaxy S 5 Unified Development] BigPulco:
I am not expert, may be someone else may better help you than me but I am thinking that followings are true;

1) Ones you already install TWRP in your phone than no need to go to PC for the rest. Installing lineageOS binaries from the PC or from the phone memory as using TWRP is the same.

2) Seems that TWRP version is important somehow, so use the latest one which is twrp-3.6.1_9-0,

3) Latest nightly lineageOS binary seems quite good, so you may use that one,

4) Magisk is something different. Magisk designer already explains in their pages what are changed and the new usage of Magisk. But, in short; versions later than Magisk 23.0 is something new; a new era, and I suggest to use Magisk V23.0 for the moment...

5) As a installing procedure I suggest following reference procedures of curiousrom

Clean Install with TWRP.

TWRP & Lineage Recovery - Format Data vs. Wipe

Galaxy S5 LineageOS 18.1 - Magisk Installation
[Samsung Galaxy S 5 Unified Development] Sobhan Mazaheri:
Hi Guys

Lineageos 19.1 (Android 12L) For S5 Klte-klteduos-kltechn

by: khalvat

https://xdaforums.com/t/unofficial-lineageos-19-1-android-12l.4427639/
[Samsung Galaxy S 5 Unified Development] bouncingmarsupial:
You may pass safetynet and the like for banking etc via this method:

1. Install Lineageos 18.1 and TWRP latest.

2. Install Magisk 22 or 23 through TWRP (Zip) For some reason I couldn't install the latest Magisk through TWRP. You must install through recovery (TWRP or the like) otherwise you won't have root.

3. Update Magisk to 23-24, enable Zygisk (beta)

4. Install following modules: Shamiko (reboot after, I have v0.4.4 (106), Universal SafetyNet FIx v2.2.1 (reboot after)

5. Hide the magisk app. Do NOT enforce DenyList. Configure Magisk's DenyList by selecting your banking app. Reboot.

All of my banking apps works for now. Some variation may occur in the steps listed.
[Samsung Galaxy S 5 Unified Development] r3actor:
Hey guys, this might be a stupid question but here it is:

I got a Galaxy S 5 phone (currently still have to check what is the exact model).

There is an official Android 5 installed on it.

Do I need to install another 'official' Samsung ROM first (like Android 6), before I install LineageOS 18.1, OR I can just Install 18.1 ?

I'm not sure what would be a proper steps (rooting, TWRP, etc). I did installed ROMs before on my Galaxy S2, Galaxy Tab 7.0, Galaxy Tab SM-T560. I'm just not sure what would be a 100% correct steps for Galaxy S5 ? To be honest, I fear that I will use (radio) or...that my phone will not be able to be used as a phone (for calling) if I lose 'modem'?

Can someone write a correct steps for putting LOS 18.1 over official Android 5, without scewing something up?

Thanks!
[Samsung Galaxy S 5 Unified Development] kurtn:
Find out exact model! Do a factory reset and setup original rom. Try built in updater.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Bad News: No Official LineageOS 19 for the S5 klte* Family

@haggertk the LineageOS maintainer for the S5 klte* since way back to 14.1 posted this in the S5 Unofficial LineageOS 19.1 Android 12L thread:

The good news is that LineageOS supports 2 versions @ the same time so official LineageOS 18.1 will continue receiving monthly Android security updates & some patches until LOS 20 (or similar) is launched sometime in more or less 12 months.

Thanks Mr. haggertk for this amazing run.

***
[Samsung Galaxy S 5 Unified Development] moreorless:
I just wanted to say thank you to "Mr. haggertk" for his efforts ot keep this device alive and keep up with all demands from us users :) hehe

But for me the S5 it's a dying horse which I don't want to ride - it's no fun anymore. So I will ditch it and buy another phone.

Obviously due to age this device has not enough cpu performance and -more important- not enough RAM for todays apps which are crazy memory consuming software. LOS grew also over the years and consumes a lot of memory space compared to it predecessor version which seems to be the nature of the things :D

I don't think that it will get any better with future LOS Generations due to it's limitations.

Thanks and bye bye ...
[Samsung Galaxy S 5 Unified Development] Concept48:
HaggerTK we miss you , where are you ? Are you oke ?
[Samsung Galaxy S 5 Unified Development] g000n:
@haggertk thanks for all the work and support you've brought for us and our device.
[Samsung Galaxy S 5 Unified Development] r3actor:
Model is SM-G900F

But I'm a bit confused. What do you mean by 'do a factory reset and setup original rom'. I did facotry reset (before I asked the question here). But... rom original one that came with the phone when it was bought and it is Android 5. My goal is to put LOS ROM 18.1 on it, without making any mistakes in the process.

Could you please tell me what would be the propper way to get rooted phone with all the required things: TWRP etc?

Once again, phone was never 'played with'. It has its own original Samsung Android 5 rom that the phone came with from the shop. I'll be the first one to mess with that phone by installing anything 'custom made'.

btw. I see people mantion something like 'kite*' (or other) models. What does that mean and how can I check to which group my phone falls in? 'About device' sais its 'SM-G900F' (but I cant see anything like 'kite' or something like that written there)
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 LineageOS 18.1 Update 2022-04-17 - Android Security Bump

Using the built-in Updater I OTA updated S5 G900M LineageOS 18.1 klte build 2022-04-03 + MindTheGapps + Magisk 23.0 + TWRP 3.6.1_9-0 to build 2022-04-17: 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-04-05.

After the automatic reboot as seen in the screenshot > Settings > About phone > press on Android version > Android security update: April 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 - April 2022 for details about the security fixes.

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

***
[Samsung Galaxy S 5 Unified Development] kurtn:
Scroll down ans see your sm number.

Info about klte | LineageOS Wiki

wiki.lineageos.org

Go to settings / software update and trigger a manual check.
[Samsung Galaxy S 5 Unified Development] Orionbell37:
Hello and sorry if this question was aleady answered.

I am using TWRP to flash and backup LOS for years on my klte. Since the phone is not my main one and is exclusively dedicated to using my banking apps, I flash LOS updates only once in a while and as a precaution, always after backing it up.

For a couple of months now, I'm unable to restore the backups I've made just before. The phone can't boot up, it's stucked forever on the small LOS moving circle.

My current Twrp is 3.2.2-0, it's the one I used to flash LOS the first time.

Is updating it to the latest 3.6.1_9-0 wil solve the problem ?

Thanks.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Your TWRP version is too old.

See TWRP & S5 LineageOS 18.1 Update 2022-04-03 about using TWRP to update itself.

Old TWRP backups were created in TWRP/Backups/*device's serial number*.

New ones are in TWRP/Backups/*device's model number*.

For example: TWRP/Backups/SM-G900M. So if you want to restore an old backup using a new version of TWRP just rename that old folder.

Create a new backup of the EFS partition for example to see what I mean.

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

***
[Samsung Galaxy S 5 Unified Development] r3actor:
Model is SM-G900F

As for software update I tried to do that. And when I press 'software update' 'Update now' ('Auto update' was already checked'), a small pop-up shows up with:

"Software update - Registering device..."

and after few seconds it ends with:

"Software update - Registration failed"
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 Firmware Update

That's probably because Samsung is not offering updates for the S5 on their server anymore.

See S5 Odin Flashable Modem & Bootloader for a quick & simple workaround.

I wrote this for Windows PC users & LineageOS 16.0 but the same steps works for 18.1: S5 super clean install except that you need a GApps ARM package for Android 11.

See this for the current official LineageOS GApps recommendations: https://wiki.lineageos.org/gapps.html

***
[Samsung Galaxy S 5 Unified Development] Orionbell37:
@ curiousrom

Thanks for the reply, it's very instructive.

In the meantime I've found a workaround for the boot issue. Immediately after restoring the backup, I flash the LOS zip build on top of it.

Everything is working flawlessly now.
[Samsung Galaxy S 5 Unified Development] Jesus Army:
Hello,

I will first start with a big thanks for the maintainer and all the community that is keeping this old phone alive!

I have tried since a week to put back to life a small stock of some S5 in Japanese Docomo version (SC-04F kltekdi) that I saved from garbage. I have 5 of them, and I did some various testings with some successes and some failures.

After having confirmed that they work (including radio and more specifically LTE) on stock ROM, and self update to last official stock on Android 6.0.1, I have tried to flash offical 18.1 builds as well as unoffical 17.1 (from xda unofficial 17.1 thread) and also ROM based on /e/ to see if I got same issues or not.

I am still stuck with two remaining issues on 18.1:

Radio does not work, and LTE seems to constantly do off/on every few secs

Phone do not charge while running LineageOS

Regarding 1. I have tried to flash the firmware package from first post with no luck. Also tried to flash from stock 4.4.1 same. Flash from latest stock 6.0.1 same (Even if yes first post said that it should be the way to solve that).

I have raised a case for that, but I realized that it was on a phone (yes I tried with many since I have 5 of them :D) flashed from Android KitKat 4, so i should probably resubmit with latest baseband : https://gitlab.com/LineageOS/issues/android/-/issues/4595

For info, the 17.1 unoffical available here works fine with radio using LTE: https://xdaforums.com/t/rom-10-unofficial-lineageos-17-1-for-klte.3992419/ (3g is not available anymore in Japan, so I am only able to confirm LTE, and actually only need LTE :))

Regarding 2. I have seen that the issue was reported twice here (at least, search within a thread is not so easy), but it seems that no much details were provided to troubleshot that except that someone has mentioned that he solved that on 17.1 with a custom kernel. I confirm that reflashing stock solve the issue, and that it happen with all my devices on 17.1 & 18.1 and even /e/ which is based on lineage 18.1. Charge in TWRP is fine as well. I can open a case with logs but not sure what to provide? For info apps like Ampere shows nothing like if there was no cable when a charger is plugged in.

For the story, I am trying to make at least one or two phones to revive, with the idea of using it as an emergency phone and tracker for my 6 years old son who need to go to school by himself like other Japanese kids at their age. And the official kid's phones from Docomo is crap and far from what a phone running google maps in background can provide as a position tracker (and does not provide the satisfaction of recycling a device). And for emergency in case he got lost, I just remove all apps and set two shortcuts on the home to call mom or dad. :)

I will open issues with logs files on gitlab if better, if someone tell me which log file I should include for the charging story, would be perfect! :) (For .1 I understand logcat and logcat radio can do the job)

Thanks!
[Samsung Galaxy S 5 Unified Development] hk133hk:
I haven't test LTE network but I also facing the 2. charging problem, for my situation, I flashed the original radio.img comes from stock JP rom (I remember that someone had share this file on XDA forum but I forgot to save the link), TAR the file and flash it by Odin.

After this process, the phone still won’t have any sound/notice when plug in the charger, and the battery percentage would not have any changes, but the USB voltage and current meter shows that the phone is actually charging, and you could see battery percentage changed after reboot the phone. (but still not showing any charging status, and battery percentage would have change only when you reboot the phone if your phone is still charging)
[Samsung Galaxy S 5 Unified Development] Jesus Army:
Hi hk133hk,

Thanks for your comment!

For the radio image to flash, do you refer to this one referred as firmware from the first post? (Who seems to contain modem among other files)

I have tried this one with no success. And also tried to flash after doing stock update until last version with no success as well. :(

I cannot try 3G here so not sure if is radio that does not work at all or only LTE.
[Samsung Galaxy S 5 Unified Development] hk133hk:
I figure out that I have posted the link and solution of fixing(half of) the charging problem on #970 of this post, and it should be modem file, not the radio image, I mix up with the bootloop solution of another phone, sorry for misleading.

I would test the cellular network on my Japan version S5 tomorrow(unless I forget this thing after having a sleep), and I would let you know my test result.