yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] D9yHyi8Fe3mo1YgM:
[MENTION=4122877]curiousrom[/MENTION] At first, thank you very much for all your help!

Your suggestions show that the problem somehow is complicated and that I am probably the first one who suffers from it, and for some reason, I can't connect to the phone via ADB (I'm still investigating).

However, a few clarifications: I never had installed the TWRP app, so we can rule out that reason. I also did not convert third-party apps into system apps (to be honest, I never heard about that - I'll have to research why people want to do this :)).

The patch I used for TWRP to make it backup the internal storage as well is described here:

https://xdaforums.com/android/apps-games/app-twrp-tipatch-backup-internal-t3831217

Unfortunately, I did not understand how to boot into safe mode. Booting into safe mode does work only if I have installed the stock firmware, doesn't it? I had installed LineageOS before the "accident", and I tried the key combinations you suggested, but I was not able to get into safe mode.

But I have made progress another way. For testing (and knowing that I had that not-so-recent full TWRP backup), I wiped the system, data, dalvik and cache partition. Then I installed the newest nightly (LineageOS-xxx-20191202-xxx). That installation took very little time, and the boot loop did no longer exist afterwards; the phone behaved like it should.

Of course, I had lost all data during that procedure. Therefore, I booted into TWRP, restored the data partition from within there, and rebooted to system. Then -bang-: That reboot took many minutes and in turn finished with a reboot into TWRP.

Since then, I have confirmed that behavior multiple times. When I wipe, I can install LineageOS without problems (tried three different versions which were available during the last months), the boot loop goes away, and all is fine. As soon as I restore the data partition, the next boot takes several minutes, re-establishes the boot loop and ends with a reboot into TWRP.

Does anybody have an idea what on earth in the data partition could make LineageOS re-establish the boot loop as soon as it encounters it during boot? To be honest, I am at a point where I can't afford to put much more time into analyzing the problem. Instead, if I am the first one with that problem, I'll just reinstall everything from scratch (and wait for the snail mail letters from the banks ...).

Thank you very much again for your help!
[Samsung Galaxy S 5 Unified Development] kurtn:
[MENTION=8052456]D9yHyi8Fe3mo1YgM[/MENTION] i think you have GApps in your setup? So you should flash them together with lineageOS after wiping /system.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: SM-G900F always boots into TWRP after LOS 16 OTA update

Thanks :good::cool: for reporting back & the additional info.

You can't connect to adb probably because you said above that you disabled adb debugging & that's why I suggested to boot in Safe Mode to enable it after restoring your problematic Data backup.

And you need to connect to computer while in Safe Mode & authorize the device before reproducing the boot loop again.

Edit: [MENTION=8052456]D9yHyi8Fe3mo1YgM[/MENTION] - See XDA portal article What is ADB? How to Install ADB, Common Uses, and Advanced Tutorials for more info.

Safe Mode works regardless of the ROM because that function is hard coded & gives a command to the aboot (bootloader's name on the S5) before the OS is loaded just like Recovery & Download Mode.

Safe Mode as tested on my S5 LineageOS 16.0:

Turn off the S5.

Turn on the S5.

As soon as you see the aboot Samsung S5 splash logo (screenshot) press Volume down & keep on pressing it until it boots to System (screen lock or your desktop.

If Safe Mode was not working on S5 running LineageOS then I could not have made the screenshots I posted above my dear Dr. Watson. ;)

BTW for S5 users running LineageOS: in the Power menu you can long press either Power off or Restart & select boot in Safe Mode. (screenshot)

Good that you proved that there is no boot problems with the recent LineageOS builds.

"...what on earth in the data partition could make LineageOS re-establish the boot loop" - It could be a ton of things like apps, settings, tweaks, Permission Manager error, corrupted files, etc, etc. That's why a boot fail logcat is the best troubleshooting tool.

Thanks for the link to the TWRP patch. This said it's very easy to backup the content of the internal sdcard to computer & external Micro SD card without it & TWRP is so important to do stuff like OTA updating that I am wary of modifying it in any way.

I would recommend to use TWRP to flash the stock version of it. See How To Update TWRP 3.3.1-0 Using TWRP Itself.

For sure starting from scratch and doing a S5 super clean install is the best for a trouble free setup.

I did that 8 months ago & had zero boot or freezing problems since then.

***
[Samsung Galaxy S 5 Unified Development] D9yHyi8Fe3mo1YgM:
[MENTION=4122877]curiousrom[/MENTION] [MENTION=8031265]kurtn[/MENTION] Thank you very much - I SOLVED THE PROBLEM!

Actually, it was [MENTION=8031265]kurtn[/MENTION]'s hint which put me on the right track, although I am not sure if it was the additional thing I did (see below) or if it was the gapps installation which resolved the problem, because I did the following things at the same time:

I booted into TWRP again and wiped dalvik, cache, system and data again. Then at first I restored only the data partition and did not reboot afterwards. Then, after I had done this, in the same TWRP session, I installed the new LOS nightly and then the gapps.

This did the trick! The phone booted, my data and my banking apps (and all other things) worked as usual, the boot loop was not there any more.

I am not sure if the restore / installation order did the trick (in the previous attemps, I always restored data after having installed the new LOS, but this time, I reversed the order), or if it was the new gapps installation (after the LOS installation).

Anyways, once again, thank you very much for all your help!

P.S. Thank you very much for your explanations and instructions regarding the safe mode. That was very enlightening; I didn't know that LOS incorporates the safe mode.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: SM-G900F always boots into TWRP after LOS 16 OTA update

Good for you & Thanks :good: to [MENTION=8031265]kurtn[/MENTION] for the suggestion.

Sadly without the bootloop logcat we will never know why your OTA update failed in the first place.

Make frequent TWRP backups & enable Google Backup since you had problems & did not do a clean install.

Good luck!

***
[Samsung Galaxy S 5 Unified Development] D9yHyi8Fe3mo1YgM:
Thank you very much again!

I'll for sure follow your advice and make frequent TWRP backups and copy them to my PC from now on. This is very easy, because on one hand, I have all data in internal storage, and on the other hand, I have an SD card in the phone (32 GB) solely for backups. Furthermore, I have installed SSHelper, so I can easily copy those backups to my PC via SFTP. From now on I swear I'll regularly boot into TWRP, make a full backup from internal to SD, reboot to system, fire up SSHelper and copy the backup to my PC.

However, I'd like to avoid Google Backup because I'd like to keep that device as Google-free as possible; thanks to the fantastic LOS, it is possible to run a nearly Google-free Android system. I think that this device will never see a Google account :)

Regarding the actual reason for the problem, I believe it was indeed the gapps. Applying naive logic (and probably missing something obvious):

I did two things at the same time to make it work again. The first was to carry out actions in reverse order, i.e. to first restore data, then install LOS. I currently believe that this actually was not the key to success, because this is the same what happens with the OTA update: The data is already there, then LOS is installed.

In contrast, the second thing I did (that is, install / update the gapps immediately after having installed LOS, following kurtn's advice) surely does not happen automatically during or after the OTA update.

This leads me to the impression that my previous gapps package was not compatible with the new LOS version (or vice versa). Neither LOS nor gapps had been updated for at least 6 months, perhaps even longer. I can very well imagine that the combination of quite old gapps with a brand new LOS gives all sorts of problems.

Once again, thank you very much!
[Samsung Galaxy S 5 Unified Development] kurtn:
Let me write down a few things i think I've learned.

Most flashable addons place ota survival scripts in system/addon.d folder. So, afer dirty rom flashing the addons get restored. If you don't want that restore, simply wipe system first.

In the last months lineageOS got more restrictive regarding quality of addons. Something with permissions of system apps. That's why some ota updates now end in twrp.

When you now have a setup with fresh lineageOS and addons, future OTA updates should be no problem. No need to flash new GApps, because they are mostly self-updating.
[Samsung Galaxy S 5 Unified Development] D9yHyi8Fe3mo1YgM:
[MENTION=8031265]kurtn[/MENTION] Thank you very much for the explanation. I'll try as you advise. Additionally, I'll take the backup thing more seriously :)
[Samsung Galaxy S 5 Unified Development] D9yHyi8Fe3mo1YgM:
LOS 16.0 from 20191201 always shows "Preparing for Setup" notification

After my recent endeavors with installing LOS 16.0 from 2019-12-01 (see posts above), I have two minor problems left. One is off-topic in this thread, and the other is:

When I swipe down the status bar, there always is a notification that Android is preparing for setup (see first screenshot). When I tap on that notification, a new screen opens claiming that I can "finish setting up my SM-G900F soon" (see second screenshot). Nothing else happens, it stays there forever as-is.

When I close this screen by using the sensor key at the right bottom (the "back" key), another new screen appears (see third screenshot). Here we can see that it obviously did not detect that the phone already is connected via WiFi, which definitely is the case. Hence, tapping on "WI-FI SETTINGS" does not lead anywhere.

So I have two questions:

1) What exactly does LOS try to tell me when claiming that it is preparing for setup, taking into account that the system already runs perfectly (apart from the problem which is the subject here)? What does it want to setup?

2) How do I get rid of that notification (besides disabling system notifications globally)?

Thank you very much again!
[Samsung Galaxy S 5 Unified Development] kurtn:
LineageOS has nothing to do with that. You see a GApps setup. Maybe you can kill that.
[Samsung Galaxy S 5 Unified Development] dante7000:
flashed latest build for kltekor,phone goes off anytime i try using the camera. I had to download "footej camera" from the playstore,no sudden shutdowns anymore. Thanks Brunowp8
[Samsung Galaxy S 5 Unified Development] ozzycao:
Wow! I was thinking that my chager was broken! Its true: is very

Hard to charge nowadays.
[Samsung Galaxy S 5 Unified Development] fparri:
Thanks a lot. I downloaded and flashed it :)
[Samsung Galaxy S 5 Unified Development] Nsane457:
Sadly, neither of these solutions work for me.

Flashing the EFS partition is the one general solution that works for me every time. I did a full nandroid backup on the one installation of LOS16 that didn't corrupt the EFS partition and flash if after first boot of any new LOS16 install. Works like a charm.
[Samsung Galaxy S 5 Unified Development] Sebastian505:
i duuno but it's works for me :rolleyes:
[Samsung Galaxy S 5 Unified Development] portsample:
Happy to report lineage-16.0-20181019-UNOFFICIAL-klteactivexx installed and is running fine on my S5 Active 870F "Frankenphone".

Thanks to Haggertk et al for builds to the S5 Active.
[Samsung Galaxy S 5 Unified Development] Brantman:
VZW networking issues/questions (900V model, 10/19 ROM, QL1 baseband)

I have a long commute, so I have been able to watch the behavior (presumably) when the phone has to hand off to a new tower: when this happens, the LTE signal drops, then returns as 3G. 3 seconds in airplane mode, and it returns as LTE-meaning the LTE was available all along. This seems to happen when the phone is idle sometimes, and it has happened when I'm walking around a store (I assume no tower changes). Is there a setting somewhere to prefer LTE when both are available? I know there was something similar in older versions of android for wifi versus cell (aggressive handoff) that seemed to trick the phone into seeing one as an artificially better signal. Is there such a thing buried in the settings somewhere? or in the code? [MENTION=2693412]haggertk[/MENTION]

Other than that, this ROM is fast, smooth and the battery life is better than 15.1, even with the constant network switching and searching. Thank you to the developers for keeping this phone alive and surprisingly current.
[Samsung Galaxy S 5 Unified Development] anonnow:
This rom is so smooth. I dirty flashed over Havoc 8.1 and it's still smooth as butter. Only problem I've ran into is the mobile data toggle is sometimes disabled and grayed out. Putting the phone in airplane mode and rebooting, disabling airplane mode fixes the problem. All in all, it's amazing I can run the latest version of Android on my old S5! Especially for as smooth as it is! Thanks to all involved, this is awesome. As a flashaholic, this goes in the books as top ROM to date.
[Samsung Galaxy S 5 Unified Development] ItzRsh:
Anyone flashed it on kltedous?
[Samsung Galaxy S 5 Unified Development] Gitanitos:
I flashed some weeks ago only to see if it works (dirty flash).

The good new is It works like 15.1 and at last in Spain LTE works well (Vodafone Spain).

I returned to 15.1 because in 16.1 I have the same problem and I prefer to wait to official LOS16.

My problem in Los16 or 15.1 is that every time that I start or restart the phone, many times the phone doesn't recognize the SIM card or others, SIM card have been recognized and unlocked but don't have any network.

So finally I need to wait two minutes and restart without WiFi in order to have SIM + Network...

Sometimes, even having Network (LTE or others) I don't receive SMS so I must "again" to restart the phone many times and check if I receive SMS.

I don't know if this problem it's only linked to G900FD (Duos version) or more people have it.

Enviado desde mi SM-G950F mediante Tapatalk
[Samsung Galaxy S 5 Unified Development] RuKaDa:
@Brunowp8 or @haggertk

Does this ROM requires to update modem and bootloader? I am on G900F with CQAV, what issues could I expect if don´t update them?

Can I ask which modem and bootloader are the builds based on?

Thanks for your work to bring us latest Android version. Great job guys :highfive:
[Samsung Galaxy S 5 Unified Development] HolyHog:
Here is a quote from Haggertk "There is 0 need to upgrade bootloader, in particular G900V bootloader. Given that I have a developer device, my bootloader is the original shipping KK one."

I can say from my experience that is has never mattered what bootloader or modem you have to run Linage roms. It only matters with some TouchWiz roms.
[Samsung Galaxy S 5 Unified Development] fitittome:
What Ubuntu version are people using to build Pie? I'm wondering if my inability to brunch are because I'm running 16.04? Apparently people on 18 seem to be OK.
[Samsung Galaxy S 5 Unified Development] Brunowp8:
You can use 16.04

I only use this version

Maybe you're doing something wrong to not work out
[Samsung Galaxy S 5 Unified Development] fitittome:
Doing something wrong...

I dunno. Probably but I think I'm doing the right things. I've started from scratch a few times just in case. I've set up the .profile as per the official build instructions and started from a clean directory. This is the process Kevin outlined.

$ cd ~/android/16.0
$ repo init -u https://github.com/LineageOS/android.git -b lineage-16.0
$ repo sync
$ source build/envsetup.sh
$ breakfast klte
$ mkdir -p .repo/local_manifests
$ curl https://raw.githubusercontent.com/haggertk/cm_build_stuff/lineage-16.0/local_manifest.xml > .repo/local_manifests/tmp.xml
$ repo sync haggertk
$ rm .repo/local_manifests/tmp.xml
$ breakfast klte
$ ./picks.sh

It all goes fine. initially it was going all the way through to brunch which failed at about 99% with this sort of error:-

ERROR: Dex2oat failed to compile a boot image. It is likely that the boot classpath is inconsistent.

But since then I repo synced and those Dex2oat errors were cropping up at about 40% through the build.

With the latest sync I'm struggling to get the ./picks.sh to execute properly.

Applying change number 231590...
--> Subject: "SimSettings: Add manual SIM provisioning support"
--> Project path: packages/apps/Settings
--> Change number: 231590 (Patch Set 2)
['git fetch github', u'refs/changes/90/231590/2']
remote: Enumerating objects: 98, done.
remote: Counting objects: 100% (98/98), done.
remote: Compressing objects: 100% (21/21), done.
remote: Total 144 (delta 85), reused 77 (delta 77), pack-reused 46
Receiving objects: 100% (144/144), 47.33 KiB | 0 bytes/s, done.
Resolving deltas: 100% (88/88), completed with 26 local objects.
From https://github.com/LineageOS/android_packages_apps_Settings
* branch refs/changes/90/231590/2 -> FETCH_HEAD
error: could not apply 3f1ce36... SimSettings: Add manual SIM provisioning support
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'
Recorded preimage for 'res/values/cm_strings.xml'
ERROR: git command failed

I reckon it's just too much a work in progress at the moment. I just don't know enough to fix these things, you know it's half a day that just vanishes each time I look at it! :crying:
[Samsung Galaxy S 5 Unified Development] Brantman:
More VZW network stuff:

(900V model, 10/19 ROM, QL1 baseband)

I wanted to change the bearer of the VZWInternet APN to LTE only, but the entire APN is ghosted and cannot be edited.

I then tried to create a new APN...I can fill in the APN field, but I can't even save it since I can't fill in the Name field.

I also cannot delete the tracfone APN, not that I need to.

Also, I've noticed that after a reboot, the APN will sometimes be deselected. Could this be the reason for losing connectivity after reboots?
[Samsung Galaxy S 5 Unified Development] Massedil:
I also have this problem with LOS 15.1 on G900P/kltedv and I have not tried whith LOS 16.

I have to put my sim unlock code 2 times after boot and sometimes I have to reboot again when it is not working after unlocking.

I don't know exactly what to do with Wi-Fi / air plane mode / removing battery to have a good boot, but sometimes it works fine.

I have seen that when the problem occurs in Settings > Network > Mobile network > APN everything is empty. Trying to reset APN does nothing.

I thought it was linked with my LTE problem (https://xdaforums.com/showpost.php?p=77908767), but now, it seems not.
[Samsung Galaxy S 5 Unified Development] Xplor3r:
Here's a guide to [MENTION=7350242]Uldiniad[/MENTION] that might help you. Although it is on Windows 10, it uses the Linux Subsystem (Ubuntu 18.04) to build LineageOS 16. A thank you for him, by the way. [Guide] How to build LineageOS 16
[Samsung Galaxy S 5 Unified Development] KingKuno:
What's not working :

• Tell us

...

So VOLTE and WLAN Call is working???
[Samsung Galaxy S 5 Unified Development] swiftbones74:
VOLTE really?

Me thinks you must be joking around
[Samsung Galaxy S 5 Unified Development] curiousrom:
[MENTION=8052456]D9yHyi8Fe3mo1YgM[/MENTION] - Clean install without GApps because you wrote that you don't have nor want a Google account so what's the point of installing that?

Or delete the Open GApps update survival script: /system/addon.d/70-gapps.sh and flash LineageOS to remove it.

Or does your banking apps require the Google Play Services framework which is included in Open GApps but not in the LineageOS package?

***

Not without loging in with a Google account AFAIK.

***
[Samsung Galaxy S 5 Unified Development] kurtn:
Or that changed?

https://www.androidauthority.com/android-app-updates-no-account-954639/
[Samsung Galaxy S 5 Unified Development] D9yHyi8Fe3mo1YgM:
Again, thank you very much!

My question is obviously off-topic then. However, for the record: After having followed tutorials and instructions for two hours without success, I lost patience and have forcibly stopped the two Android Setup apps which were on the phone and have disabled them. The notification is now gone.

---------- Post added at 11:44 AM ---------- Previous post was at 11:27 AM ----------

Well, when I first installed the phone, I was a real newbie in that field. I remember that I decided to put the very basic Google service onto the phone (and therefore chose the nano variant of gapps), but not to create any Google account. As said before: An illogic newbie decision.

If I only had known this yesterday morning ... that eventually would have saved me from losing a complete day ... I just did not know about that trick (and for sure will archive this thread for future reference) and thus was very grateful for the hint to re-install the gapps package, which probably was the key to solve the problem. Reinstalling gapps seemed the only way to make the phone usable again together with my restored data partition, which was the only reason why I reinstalled gapps. Additionally, see below ...

Yes, exactly! At least one of this crap won't even start without Google Play Store installed! Really, not only the play services which it complained about when I first tried to install it, but also the Play Store app (this cost me another day two months ago to find out).

I have no clue if it would be possible to install the Play Store app without having installed the gapps package before, and I'm a bit reluctant with testing because I have lost so much time yesterday.
[Samsung Galaxy S 5 Unified Development] kurtn:
Or you try that:

https://download.lineage.microg.org/

It fakes the existence of some GApps components and replaces a few basic services wit open source implementation
[Samsung Galaxy S 5 Unified Development] D9yHyi8Fe3mo1YgM:
Thanks again! One more reference to keep for future use ... I'll soon setup a Galaxy S9+ DUOS and of course will install LineageOS on it. When doing so, I'll try the approach you proposed. It will be interesting to see if those silly banking apps will accept the "fake" Google libraries.
[Samsung Galaxy S 5 Unified Development] smallz2k:
ive been swapping roms as we Do ?

i was using The Noise rom which shows the phone as an s8 or s9 so i could play the Mobile 'call of duty' ?

Isthere any way of you putting a script into rom to do the same. as i love that game And prefer this rom?

Nice one all & Op.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Spoofing S5 as a S8?

Search thread Magisk General Support / Discussion with spoofing.

Check also the excellent Magisk and MagiskHide Installation and Troubleshooting guide by [MENTION=4667597]Didgeridoohan[/MENTION].

***
[Samsung Galaxy S 5 Unified Development] Noob9496:
How to OTA update? Klte + Tunned Kernel + Magisk 20 + TWRP.
[Samsung Galaxy S 5 Unified Development] kurtn:
Don't know about the kernel. But if you run official 16.0 simply go settings system advanced updater. Magisk will be automatically restored after update.
[Samsung Galaxy S 5 Unified Development] Noob9496:
I try update but i have bootloop.
[Samsung Galaxy S 5 Unified Development] kurtn:
Then boot into twrp, wipe system only flash ROM (and new GApps download if those have been part of your setup).

Magisk can be flashed later. For details scroll up like 30 posts.
[Samsung Galaxy S 5 Unified Development] Noob9496:
I use MicroG, EdXposed, adreno330 MOD and Bromite Web View. After wipe system and flash rom, i must install this addons again? I have problem with FakeGapps module. In logcat i have NullPointerException and FakeGapps has stopped sometimes.