yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: Galaxy S5 GPS Problem & Rooting Before Installing TWRP?

Thanks for the suggestion but in the post you linked to this is too complicated for no good reasons : "you’ll need to extract the .bin baseband files (usually called modem.bin and/or NON-HLOS.bin) from them" and "You will need to do perform this for modem.bin and NON-HLOS.bin separately" and does not include the other firmwares included in the linked bootloader/modem combos in S5 Odin Flashable Modem & Bootloader.

Also the link in the post you referred to: "Find the latest baseband under the “Odin” heading here." is 404: "Invalid thread specified."

Except for the special case S5 G900V it's recommended to flash a matched pair of modem & bootloader.

As you can see top left in the Odin3 screenshot of that Odin Flashable... post it took only 15 seconds to flash that single file combo on my S5 G900M and you can see in the Odin3 log window of that screenshot everything that was successfully flashed.

Besides flashing the most recent stock Samsung as suggested to [MENTION=7910837]Massedil[/MENTION] to make sure there is no GPS hardware problems is the only 100% reliable troubleshooting step as there can be problems with the custom ROM & user's settings & the third-party apps he installed.

***

Rooting Before Flashing TWRP?

That's really weird because Bluetooth is not enabled by default on a clean install first boot.

You don't need to root stock Samsung OS to install TWRP with Odin3. Odin is a god & can do all kind of things to your device regardless of the OS installed on it, rooted or not. :cool:

Good for you & thanks :good: for reporting back.

This said it should not take "a couple of hours". :eek:

***
[Samsung Galaxy S 5 Unified Development] BLepers:
Very very happy with the new LineageOS version, but I think the airplane mode does not fully power off the modem.

Model: G900-F (SM-G900FZWAAUT)

LineageOS version: 16.0-20191115-NIGHTLY-klte (latest)

Radio/Baseband version: G900FXXU1CQK3 (latest)

Bootloader: G900FXXU1CRH1 (latest)

Bug also happens on G900-V, and previous versions of the modem firmware. I followed the official guide to install lineageos (so clean install?)

Step to reproduce:

- switch airplane mode on

- call *#*#4636#*#* and in "phone information", the radio power is still on and it is not possible to really turn it off (the button is active but has no effect)

This is also confirmed by GSam battery monitor (shows that radio is always powered on even in airplane mode).

I think the problem has been reported by another user in that thread, but I could not find a solution. Happy to do some debugging, but I'm not sure where to start.
[Samsung Galaxy S 5 Unified Development] Sobhan Mazaheri:
Tnx for your guidance [MENTION=4122877]curiousrom[/MENTION]

I think the problem has been resolved by recent changes
[Samsung Galaxy S 5 Unified Development] Liebesrind:
It was the twrp-App! :rolleyes: No problem without installing it after flashing the rom...
[Samsung Galaxy S 5 Unified Development] minoo14534:
Galaxy S5 Klte Wahtsapp and Telegram very Low Volume

Since the last update, I've noticed that while using apps like Wahtsapp or Telegram, the voice has become very quiet. :eek:

It does not affect at normal calls.

Everything was really great before that.

I also ran dalvik cache and cache in twrp it did not help unfortunately.

Does anyone have any idea why this might be.

thanks for any help
[Samsung Galaxy S 5 Unified Development] minoo14534:
Wahtsapp Low Volume

Hello, Thanks for the quick reply.

The problem only applies to Wahtsapp

Not in the normal voice recording also not in telegram and normal calling.

The hole of Main Microfon is free.

I also tried installing several versions of Wahtsapp, without success.

Unfortunately, the XML file in ADB section can not be opened either.

remote object '/system/vendor/etc/mixer_paths_0.xml' does not exist.

1. Boot into TWPR recovery and mount system partition in rw mode (enable checkbox mount-> system, uncheck system mount in read-only).

2.Open terminal and pull the file from the device by

Code:

adb remount

adb pull /system/vendor/etc/mixer_paths_0.xml

I'll see what that is.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: S5 Main Mic Recording Boost & Survival Script - WhatsApp

Many typos. It's WhatsApp, NOT Wahtsapp & it's mixer_paths.xml, NOT /mixer_paths_0.xml

You can also use TWRP > Advanced > File Manager > navigate to /system/vendor/etc/mixer_paths.xml, copy to external card, edit, copy back, chmod 644 to give the proper permission (rw-r--r--) then reboot.

Why not just try the 118 zip mod?

***
[Samsung Galaxy S 5 Unified Development] sharktm:
just a question about the extremely low microphone gain on Whatsapp which i also encounter on a SM G900F with the latest 19 november build and nano gapps, can be fixed if whatsapp is moved to system using root or ADB? the phone app is a system app and the voice calls seems to be ok regarding the microphone.
[Samsung Galaxy S 5 Unified Development] gregrwm:
bluetooth only works for my mic, the other party's voice is still at the phone. is this a known issue?

could it be i need to update my radio? i have baseband G900PVPU2BOD3.

how might i learn what's the most recent radio?

might i find it in twrp-flashable form and from a trustworthy source/channel?

how might i know if the one here is the most recent, and trustworthy:

https://shell.boxwares.com/Download.aspx?L=1912

or might there be a stock package that works with twrp?

many thanks...
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 G900P Modem & Bootloader Update

Your G900PVPU2BOD3 baseband/modem/radio is from an old Android 5.0 2015 as you can see in https://www.sammobile.com/samsung/galaxy-s5/firmware/SM-G900P/

That may explain your problem & probably the fingerprint sensor does not work too.

You could get a Samsung stock G900PVPS3CQD1 on that page or here: https://samfrew.com/download/GALAXY__S5__/O172/SPR/G900PVPS3CQD1/G900PSPT3CQD1/

The shell.boxwares link you posted is no good because it's not the most recent modem & it does not include the other firmwares described in S5 Odin Flashable Modem & Bootloader.

I could not find a flashable modem/bootloader combo for the S5 G900V so see the ...hard way chapter in that post.

In a nutshell:

Do a full backup in TWRP (except the caches) to the external Micro SD card which BTW does not include the internal sdcard.

Backup the internal sdcard to computer.

Flash Samsung stock using Odin3.

Test mobile data, screenshot or write down working APN settings.

Flash TWRP using Odin3.

Backup the EFS partition only to external Micro SD card.

Restore TWRP backup made in step 1 but ONLY the System, Data & Boot (kernel) partitions & nothing else! That means not the modem, EFS & caches.

"...might there be a stock package that works with twrp?" - NO, Odin3 is required as you can see in the 1 file instructions in the sammobile G900PVPS3CQD1 download page which includes an Odin3 download link.

***
[Samsung Galaxy S 5 Unified Development] Plasmator-x64:
[MENTION=4122877]curiousrom[/MENTION],

How do I clean install LOS 16 on to my SM-G900W8 running CM13 ?

Model = SM-G900W8

Baseband = G900W8VLS1DPF3

Android = 6.0.1

OS = CyanogenMod

Version = cm-13.0-20161213-UNOFFICIAL-klte

TWRP = 3.0.2-2
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 SM-G900W8 LineageOS 16.0 Clean Install

Thanks for the detailed device setup info. :good:

If you have a GApps package installed you could do a fresh Google Backup that you could restore on first boot as described in S5 super clean install.

That post includes links to update TWRP using TWRP itself, your G900W8VLS1DPF3 (2016) baseband/modem/radio + your aboot bootloader to DQB2 (2017).

An updated TWRP is required for the built-in LineageOS OTA updater to work properly.

Do a full TWRP backup + an internal sdcard backup to external Micro SD card so you may return quickly to your current setup in case of a problem.

Please report back if it worked for you or not. :cool:

***
[Samsung Galaxy S 5 Unified Development] Plasmator-x64:
Samsung Galaxy S5 ( SM-G900W8 ) - LineageOS 16.0 - Super Clean Install

[MENTION=4122877]curiousrom[/MENTION],

Success !!! Easy As Pie !!!

:D:D:D

I successfully upgraded my Samsung Galaxy S5 ( SM-G900W8 ) from CyanogenMod 13.0 to LineageOS 16.0. Below are my notes from the upgrade process.

(A) Device Info - After Upgrade

(B) Device Info - Before Upgrade

(C) Resources - Files Used

(D) Backup - Device Config

(E) Upgrade - Baseband + Modem + Radio + Bootloader + TWRP

(F) Install - LineageOS 16.0 + GApps Pico + AddOnSu

(G) Restore - Device Config
[Samsung Galaxy S 5 Unified Development] faizal2090:
Kindly update us on the stability and performance of ROM after few days of usage

Thanks in advance
[Samsung Galaxy S 5 Unified Development] mangokm40:
I use the TMobile version of the s5 as my everyday phone. I'm running the 10/22 version of LOS16.

I've tried updates to the 11/17 and 11/22 versions. On both cases, the signal suffered greatly. In the house, I get 4 or 5 bars everywhere.

However, both of my attempts to update created a situation with no service or 1 bar of signal strength. In the case of 11/17, I tried it for 3 days. The 11/22 I tried only for about an hour. In both cases, restoring (TWRP) to the 10/22 install solved the signal issue.

Is this happening to anyone else?

Thanks.
[Samsung Galaxy S 5 Unified Development] Plasmator-x64:
What are you using to measure Signal Strength ?

I'm using "Signal Strength" by Lakshman from the Google Play Store.

"Signal Strength" by Lakshman

https://play.google.com/store/apps/details?id=com.cls.networkwidget
[Samsung Galaxy S 5 Unified Development] mangokm40:
I don't have any app installed. It's just a difference in "bars" when at home. I've been updating monthly. The Nov update appears to create the problem.

I was just wondering if anyone else noticed this.
[Samsung Galaxy S 5 Unified Development] Plasmator-x64:
[MENTION=9679442]mangokm40[/MENTION],

The download for the 10/22 version of LOS16 is no longer available.

Where can I download the file "lineage-16.0-20191022-nightly-klte-signed.zip" ?
[Samsung Galaxy S 5 Unified Development] mangokm40:
I don't know where the file might be available. I have it, but don't know a way to make it available.
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 Cellular Network Signal Strength

You guys are barking at the wrong tree.

Tons of variables affect the phone signal strength, network type connection & download speed including the network provider, weather, geography, time of day & network traffic handled by the cell tower at a given time, outdoor/indoor, cell tower in line of sight or with obstacles like buildings, how you hold the phone, etc, etc.

On the S5 itself the signal strength depends mostly on:

The modem/baseband/radio firmware.

The EFS Partition.

The RIL (Radio Interface Layer) in the ROM & as you can see in the LineageOS Gerrit S5 dev haggertk did not change anything since a long time: owner:haggertk@lineageos.org branch:lineage-16.0 ril

The setting you choose in > Settings > Network & internet > Mobile network > Advanced > Preferred network type

See the app links & the attachments in S5 LTE Download Speed Variations.

The only valid test would be to have 2 exact same S5 models with the same modem next to each other with different ROM builds, connected to the same network & compare the signal strength in real time.

***

[MENTION=9679442]mangokm40[/MENTION] - If you lose network connection after updating try restoring a working EFS Partition backup.

See No Network, No IMEI, No SIM & EFS Partition Restore Fix.

***
[Samsung Galaxy S 5 Unified Development] mangokm40:
I concede that I'm a neophyte. :)

However, I thought I was eliminating the variables you listed:

I am not changing the modem/baseband, EFS, or Mobile Network prefered type when I install the ROM. (or am i?) That's why I posted to see if anyone else had trouble with signal after update.

You mentioned this: "If you lose network connection after updating try restoring a working EFS Partition".

I don't lose network connection so much as the signal quality goes from great to poor. But I have been restoring everything but Modem partition when I bring back the 10/22 ROM. That includes the EFS partition. Are you saying I should try the latest ROM, and restoring only the EFS partition? I actually thought EFS was not changed by ROM update.

Thanks for taking the time.
[Samsung Galaxy S 5 Unified Development] Reverse-anastomosis:
Its not supposed to change efs, but for some reason on certain klte models it seems to corrupt efs during update, and sometimes randomly. When I was still using my g900v I kept a backup of just a working efs on the device and would restore it whenever I thought things with network were getting funky. I'd recommend trying this before getting too far into anything else.
[Samsung Galaxy S 5 Unified Development] gregrwm:
Bluetooth keeps stopping

After installing stock (including baseband) G900PVPS3CQA2, activating a bluetooth headset, and installing boldbeast call recorder, i can make calls with and without bluetooth with no problems, boldbeast is able to record calls without bluetooth, tho with bluetooth the calls work properly but boldbeast records silence, which is a known issue, boldbeast says that needs root. Neither king nor towel succeeded, probably because i was upgraded, so i figured how about try LineageOS.

So, with baseband still as above, i installed LineageOS 16.0-20191120-NIGHTLY-kltedv. i can make calls with and without bluetooth. But after installing boldbeast call recorder, before even making any calls, i get "Bluetooth keeps stopping". i've attached a logcat. after updating to 20191125 i was able to make a brief call using bluetooth, and able to press the boldbeast record button, end the call, find the call in the recorded calls list, but upon trying to playback the recording i got "Bluetooth keeps stopping".

Getting this working on LineageOS would be super. Or i'd be grateful for clues about either the best way to root recent stock roms or obtain trustworthy rooted roms for g900p/kltespr.
[Samsung Galaxy S 5 Unified Development] Plasmator-x64:
Two Day Update - LineageOS 16.0 20191122 Nightly KLTE

A brief update after 2 days running "lineage-16.0-20191122-nightly-klte-signed.zip".

All is stable and running as expected with no major system issues to report. I will post again at the end of the week.

After the upgrade I had to switch my root explorer to "Solid Explorer 2 PRO" as "ES File Explorer PRO" was removed from the Play Store. Got all my apps installed, configured and running smoothly. The performance of the SM-G900W8 & LOS 16.0 is definitely better.

BTW, I wanted to ask you S5 users and sorry if it's the wrong place.

Do any of you own another mobile device running LineageOS ? What brand and model ? Are you happy with the device ?

I was hoping to pick up something with a better camera, screen, faster processor etc.

Nothing too extremely expensive :D
[Samsung Galaxy S 5 Unified Development] mangokm40:
Thanks. I will try this when I grab a Dec update. :)
[Samsung Galaxy S 5 Unified Development] gregrwm:
recording on s5 with bluetooth, magic extra flashing steps, rooting recent stock

Stock+Boldbeast Call Recorder works, except not with bluetooth, unless rooted (regional s5 versions MMV). But Towel, King, and CF-Auto didn't root.

So next i tried LineageOS. Which took a bit of coaxing, so perhaps this report might help someone.

Bluetooth&Boldbeast weren't playing nice on LineageOS, so to rule out radio related issues i flashed stock. The 2 most recent g900p roms from sammobile, CQD1 and CQC1, both booted as far as the pulsating "SAMSUNG" and stayed stuck there. Well hmm. i'd made sure the s5 had sufficient charge, had launched odin as administrator, used the AP button, Auto Reboot and F. Reset Time were both set, and the s5 was directly connected and rebooted automatically when finished flashing.

So then at curiousrom's bidding i took the further steps of removing the battery for 15min and holding power for 15sec, and moving the flash files to the odin folder and the odin folder to c:\, flashed twrp (without Auto Reboot) and used twrp to format data. Well one or more of those extra steps were magic, then flashing CQD1 was indeed better, able to boot up. Yea! Bright bulb that curiousrom. And way helpful.

So then i had an updated baseband. But back in LineageOS sadly installing boldbeast still brought down bluetooth, "Bluetooth keeps stopping". Sad. Getting this working on LineageOS sure would be super.

So then i learned more about how to root recent stock. For the s5 at least, and no doubt many others, just flash SuperSU using twrp. Surprising the simple and effective way is so little known. Rooted, stock, boldbeast, and bluetooth cooperate and just work. Yea!
[Samsung Galaxy S 5 Unified Development] D9yHyi8Fe3mo1YgM:
SM-G900F always boots into TWRP after LOS 16 OTA update - how to solve?

I am running TWRP 3.3.1 and LOS 16.0 since several months without any problem on my Samsung SM-G900F. Today, silly as I am, I have accidentally installed the OTA update it offered.

As a result, the device now always boots into TWRP when I power it on via the power key. When I instruct TWRP to reboot into system, it indeed reboots the system. But this then takes several minutes and actually doesn't boot the system, but ends with rebooting, taking me into TWRP again.

How do I solve this problem without data loss?

I have come across commands like

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota

which I executed in TWRP's terminal. But this didn't help. Actually, I hadn't expected it to help because I have found those commands in articles regarding other phones. However, it seems to be the only method to solve the problem without reinstalling completely.

Is there a command like the one above for the Galaxy S5?

Thank you very much in advance!
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: SM-G900F always boots into TWRP after LOS 16 OTA update

I updated without any problems my Galaxy S5 G900M LineageOS 16.0 klte + Open GApps Pico + LineageOS AddonSU, no custom kernel or system mods of any kind via OTA at least 20 times since S5 super clean install LineageOS 16.0 more 8 months ago.

Tip: Provide more troubleshooting info and get better & more relevant suggestions.

LineageOS build date? Magisk & modules? Custom kernel? GApps package?

Did you have adb debugging enabled in Developer options & was your computer ever authorized to connect to your S5?

Do you have a recent full TWRP backup (screenshot) in external Micro SD card /TWRP/BACKUPS/ ?

If you had Google Backup enabled check here to see if you have a recent backup that you could restore on first boot either in clean install stock Samsung OS or LineageOS: https://drive.google.com/drive/u/0/backups

Waiting for the info.

***
[Samsung Galaxy S 5 Unified Development] D9yHyi8Fe3mo1YgM:
At first, please apologize that I obviously did not provide all necessary information. Here it is:

LineageOS build date:

Since the phone does not boot any more, I can't provide the exact version. I have installed that version several months ago. The version that was offered via OTA and that I accidentally have tried to install was lineage-16.0-20191129-nightly-klte-signed.zip

Magisk and modules:

No magisk and no modules installed (neither module nor app).

Custom kernel:

No, standard kernel.

GApps package:

Yes, nano version, installed via TWRP several months ago after LOS installation.

ADB debugging enabled:

Several times, each time only temporarily (for testing); not enabled at the time of the "accident". One of my PCs (a test machine) has been authorized to connect to the device in USB debugging mode.

Google Backup:

No (not even a Google account).

Recent full TWRP backup:

I have a not-so-recent full TWRP backup (even with the data partition - have patched TWRP for that). However, I'd like to avoid restoring from that backup, because I have installed some banking apps since I have created it; reinstalling them means waiting for some letters (snail mail) from the respective banks ...
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: SM-G900F always boots into TWRP after LOS 16 OTA update

Thanks :good: for the additional troubleshooting info.

The first thing to do is a TWRP backup of your current installation as it's possible to restore part of it.

"I have a not-so-recent full TWRP backup (even with the data partition - have patched TWRP for that)" - The time between backups is related to the data we are willing to lose in case of a fatal failure or if the device is lost or stolen.

I guess you mean that your TWRP patch (link?) backups the internal sdcard (/data/media/0/) which is not included in the TWRP Data partition backup as described in TWRP FAQ: What is a data/media device?

If you would have adb debugging enabled you could capture a logcat of what is happening during the failed boot to system.

This is a continuous verbose logcat tested on my S5 after causing on purpose a bootloop by installing the awful TWRP app as a system app when prompted in TWRP:

1- Boot to TWRP

2- Connect device to computer

3- Open adb CMD.

4- Paste this in adb but do not hit enter yet:

adb logcat V > 2019-12-01_logcat_Boot_Fail.txt

5- TWRP > Boot to system

6- As soon as the device's screen goes black hit enter in adb.

adb will respond: Waiting for device until it starts booting.

7- Let the device bootloop for several minutes or until it reboots in recovery.

8- Hit ctrl+c to stop the logcat & free-up the 2019-12-01_logcat_Boot_Fail.txt.

Open logcat with WordPad, Notepad++ or similar & search with beginning of crash or fatal.

You could attach the logcat to a reply.

Try booting in Safe Mode which disables all your installed app & if the problem is solved then the problem is caused by something you installed (screenshots).

From Samsung support - How do I start my Samsung Galaxy S5 in Safe Mode?:

1. Turn off the device.

2. Press and hold the Power/Lock key for one or two seconds to turn on the device.

3. When the Samsung logo displays, press and hold the Volume down key until the lock screen displays. When the lock screen displays Safe mode will be shown in the lower-left corner of the screen.

4. To exit Safe mode press the Power/Lock key and then touch Restart.

You could then enable adb debugging in Safe Mode & capture a bootloop logcat as describe above.

Good luck!

***

Edit: [MENTION=8052456]D9yHyi8Fe3mo1YgM[/MENTION] - Several users (including me) on different devices reported fail to boot if you select install the TWRP app when asked in TWRP. That app is fluff, wants to start at boot, run in the background, collect data & is not necessary anyway because the TWRP updates are not frequent & it's easy enough to update manually.

Did you converted some third-party apps as system apps?

I OTA updated my S5 from build 2019-11-21 to 2019-12-01 & everything is fine. Of note from the moment I clicked install to full automatic reboot to System it took 7 minutes. That may very depending on your setup, settings & installed apps.

***