[Samsung Galaxy S 5 Unified Development] curiousrom:
.Re: OTA Update, Bootloop & Open GApps

In your recovery log I can see:

I:operation_start: 'Flashing'
Installing zip file '/external_sd/LOSupdater/lineage-16.0-20190829-nightly-klteduos-signed.zip'

about to run program [/tmp/install/bin/backuptool.sh] with 3 args…

chown: /system/priv-app/GoogleBackupTransport/GoogleBackupTransport.apk: No such file or directory
chmod: /system/priv-app/GoogleBackupTransport/GoogleBackupTransport.apk: No such file or directory
chmod: /system/priv-app/GoogleBackupTransport: No such file or directory

script succeeded: result was [1.000000]

Why would you have a script trying to change the ownership & permissions (chown & chmod) of that system file apk? That script is probably in /system/addon.d. It could be Open GApps update survival script: 70-gapps.sh.

I have Open GApps Pico on my S5 which installed /system/priv-app/GoogleBackupTransport/GoogleBackupTransport.apk so why the script can't find it on your device?

But right after that in your recovery log:

************************
* Magisk v19.3 addon.d
************************
- Mounting system
- [B]Encrypted data[/B], keep forceencrypt
I:TWFunc::Set_Brightness: Setting brightness control to 0
- Target image: /dev/block/mmcblk0p15
[B]libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 2615 (main), pid 2615 (main)[/B]
- Unpacking boot image
Parsing boot image: [/dev/block/mmcblk0p15]

"Encrypted data..." - Is your S5 encrypted & you "forgot" to mention that?:eek:

Magisk modifies the boot image which is the kernel in fact & that is the first thing that the S5's aboot booloader loads which may explain your bootloop. The boot.img is located in /dev/block/mmcblk0p15.

I did not research that error but maybe you could: site:xdaforums.com/ magisk Fatal signal 11 (SIGSEGV)

One of the strategies of The Art Of Troubleshooting is Bare Bones: paring it back to the bare essentials.

That's why I suggested to test without Magisk. To eliminate variables to see if the problem is really LineageOS and not some other variables you may have introduced.

I:Updater process ended with RC=0
I:Install took 69 second(s).

So LineageOS installed successfully except for those errors.

[MENTION=7847310]Vini69[/MENTION] - If you have the time & inclination maybe after a Format Data, not wipe as described below, and you could install only the most recent LineageOS & nothing else?

***

Getting Out Of Bootloop & OTA Update Recovery Log

I forgot to mention this in S5 Boot Loop After Updating & will edit the post:

If you are stuck in a bootloop after an OTA update, without turning off the device maybe you can boot directly to Recovery: hold Home + Volume Up + Power & release the buttons as soon as you see the Samsung splash bootloader logo.

If it does not work for the S5 if you press the Power button for 8-10 seconds while in bootloop or Download Mode the S5 goes black & turns off. Release the power button as soon as the screen goes black. Then boot in Recovery.

Then in TWRP > Advanced > File Manager > navigate to /cache/recovery/last_log and copy it to external SD card then connect to a PC as MTP is enabled by default in TWRP and copy it. Rename it something like Recovery_log.txt & you could attach it to a reply as it can reveal some errors.

That last_log is the last thing TWRP did before rebooting. I often copy that file while in System using a root enabled file explorer to check what the LineageOS Updater script did.

***

LineageOS 16.0 Update 2019-08-29 Success

Update 2019-08-29 downloaded & installed successfully via the LineageOS built-in OTA Updater as seen in the screenshot: > Settings > About phone > press on Android version 9 on Galaxy S5 G900M LineageOS 16.0 klte build 2019-08-24 + Open GApps Pico + LineageOS AddonSU, 200+ apps including 20 with root privilege, no custom kernel or system mods of any kind.

From the TWRP Recovery's last_log:

I:operation_start: 'OpenRecoveryScript'
Running Recovery Commands
I:command is: 'install'

...writing 1024 blocks of new data...

...about to run program [/tmp/install/bin/backuptool.sh] with 3 args

...script succeeded: result was [1.000000]

...I:Updater process ended with RC=0
I:Install took 74 second(s).
Done processing script file...

***

Booting To System Fails & Goes To Recovery

Maybe you have some garbage leftover.

See S5 LineageOS super clean install which includes Format Data instead of just a simple Data wipe

And to troubleshoot & exclude a variable don't install any root method which you can do later at any time.

That's good to update modem & bootloader.

If you have problems across different ROMs that's an extra reason to Format Data.

BTW "latest" will not mean a thing for future readers after the next update so including the build date & LineageOS version is good practice IMO. ;)

***

Don't Use Open GApps?

You don't give any setup description which makes it difficult to troubleshoot. :eek:

Edit: When I wrote this post the most recent Open GApps was dated 27 August 2019 as you can see in the attached screengrab of https://opengapps.org/?api=9.0&variant=pico.

If "opengapps 2019.08.30" ever existed maybe it was removed because it was defective as looking in this Open GApps ARM downloads directory it jumps from 20190827 to 20190831 with nothing in between.

Why not copy the exact name of the file you have problems with & post that like: open_gapps-arm-9.0-pico-20190827.zip for example? Tip: in Windows right-click the file > Properties > copy name.

"I was having problem" - What problem exactly? What error message at what stage?

Maybe you got the wrong Open GApps package. It must be Open GApps ARM 9.0.

ARM because that's the architecture of the S5 & 9.0 because LineageOS 16.0 is based on Android 9.0.

Maybe the download was corrupted? Open GApps includes a MD5 Checksum for each files so you can check the integrity of the file using an hash calculator utility.

"do not flash opengapps." - That's bad advice unless you mention the exact name of the file & describe the problem.

***

:good::cool::good::cool::good::cool::good::cool:

If you guys with booting problems would include setup description (root method, Magisk version + module names if any, Xposed, custom kernel, GApps package, etc) then maybe we could find the problem like we did in S5 LineageOS 16.0 - Magisk V19.0 Beta - Reboots in Download Mode for example.

:good::cool::good::cool::good::cool::good::cool:

***