[Samsung Galaxy S10+ Questions & Answers] mchl.nix:
Hello, I'm cross posting this from a reddit post [6]. I hope that is allowed and that I'm in the right sub forum. I'm at my wits end. All I can think of is formatting system and trying to flash a clean boot.img, ROM and Gapps or wiping the whole phone, which would suck because I have 2FA on there.

Update: I feel like the problem is, that /data is not mounted (correctly). When I'm in recovery and can access the phone via adb, the /data directory is empty. If I flash the magisk.zip then those files are in /data but after rebooting they are gone again.

Same with my feeling of overriding boot.img doesn't do anything. Are some partitions somehow stuck on read-only or something?

-------------

I've been sitting at this for hours and am all out of ideas. Here's my story:

I updated my Galaxy Note 10+ to LineageOS 20, which is Android 13. The Galaxy Wear App wouldn't work, because of a custom ROM and the trick of changing the build.prop files didn't work anymore.

I saw, that a Magisk Module might work, so I sideloaded it from the github page, then noticed, I didn't have root yet. I followed this guide [1] and patched the boot.img I got from the lineage OS website [2].

I rebooted, all was well and I installed a module to help with the Galaxy Wear App. Then I noticed, that my banking app is now complaining about my phone being rooted. So I checked how to hide that fact and saw, that putting Magisk into the Zygote and then adding the banking app to the "hidden list" or whatever it was called should fix it. But it didn't.

I heard about the universal safety net fix [3] and here's where it gets a bit hazy. I'm pretty sure I installed it and I *think* I also installed the KnoxPatch module, but I'm not sure anymore.

Well, after restarting on one of these two modules, I ended up being stuck on the lineage OS loading animation, right before the system finishes booting.

I have updated the ROM shortly before all this, but I had quite a few restarts in between.

So far I tried:

- Reflashing the patched magisk boot.img from the guide, that I still had lying around

- Flashing the clean boot.img from lineage os

- Flashing a clean recovery, reinstalling lineage and mindthegapps via the recovery hoping for a clean system

- Installing magisk via the rename-the-apk-to-zip approach

- Removing magisk via the rename-magisk-zip-to-uninstall-zip

- Removing magisk with this approach of patching the magisk boot.img and flashing it again [5]

(At this point I'm not even sure if me flashing the boot even does anything, because I could never get the magisk binaries to appear again)

- Trying to find and remove any magisk files using adb shell (I only found the addon.d script)

What I couldn't try:

- `adb shell magisk --remove-modules` since 'magisk' could not be found, but maybe I did something wrong? There were binaries in the beginning, but I don't know if they were still there, or if one of the flashing attempts worked, but I could only find magisk64 and when trying it, it complained about the daemon not running. Starting the daemon didn't help, though

- Get logs from the boot process. logcat is somehow not available and I can only connect with the phone, when in the lineage recovery, after I enabled adb. it's not available during the boot process

Really don't want to do a factory reset, as you can imagine, but I have no idea what else to try anymore. I hope you can help me.

[1] https://www.xda-developers.com/how-to-install-magisk/

[2] https://download.lineageos.org/devices/d2s/builds

[3] https://github.com/kdrag0n/safetynet-fix

[4] https://github.com/BlackMesa123/KnoxPatch/releases/tag/v0.5.2

[5] https://xdaforums.com/t/guide-magis...r-booting-into-magisk-core-only-mode.3990557/

[6]

https://www.reddit.com/r/Magisk/comments/13m2oi4