Boot won't continue after installation

[awfm9]

I installed the module from the latest ZIP file here (v2.3), and now my LineageOS (with microG services) is in an infinite wait at the start-up animation. I'm using the latest official version of Magisk. Any idea on how to fix this?

[HuskyDG]

https://github.com/HuskyDG/magisk_overlayfs#bugreport

[HuskyDG]

Please try with this https://github.com/HuskyDG/magisk_overlayfs/actions/runs/4254778120

[awfm9]

The issue is that I can't seem to get a normal file system in the recovery shell, with or without mounting the system partition. Otherwise I would just be able to remove the module from the shell, or the module folder. I reckon that would work?

In a similar vein, how can I update the module if I can't find it on the file system? Sideloading does not work (and I wouldn't expect it to).

I execute a search on the root for the relevant folder names (find / -name <name>), and anything that is found comes up empty (no files) with ls.

[awfm9]

I imagine it could be relevant that I have Shamiko installed, and Magisk is running in Zygote mode.

[awfm9]

When I try to mount my data directory, I get this error:

130|sunfish:/ # cat /system/etc/fstab
/dev/block/by-name/metadata /metadata ext4 discard,data=journal,commit=1 0 0
/dev/block/bootdevice/by-name/modem_b /vendor/firmware_mnt vfat shortname=lower,uid=0,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 0 0
/dev/block/bootdevice/by-name/userdata /data f2fs discard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier 0 0
sunfish:/ # mount /data
mount: '/dev/block/bootdevice/by-name/userdata'->'/data': Invalid argument

[awfm9]

I'm really a bit at a loss here. When I go straight from boot to recovery, to enabling ADB, the fstab file still seems to be invalid:

sunfish:/ # mount -a
mount: '/dev/block/bootdevice/by-name/modem_b'->'/vendor/firmware_mnt': No such file or directory
mount: '/dev/block/bootdevice/by-name/userdata'->'/data': Invalid argument

[awfm9]

I just fixed the boot loop like this from recovery:

adb sideload ~/Downloads/Magisk-v25.2.apk
adb shell
1|sunfish:/ # /cache/data_adb/magisk/magisk64 --daemon                                                               
sunfish:/ # /cache/data_adb/magisk/magisk64 --remove-modules                                                         

[HuskyDG]

To recover from bootloop, you can download magisk delta, rename to disabler.zip and flash. After reboot, you can revert back to official magisk.

[awfm9]

By the way, my original intention was to hide the custom ROM from Momo.

I use Magisk in Zygote mode, with MagiskHide Props Config, Shamiko and Universal SafetyNet Fix, and it successfully seems to hide everything except for the custom ROM.

I read somewhere that it is due to some folders that need to be hidden on the file system, hence this attempt.

If you have any hints in that regard, that would be great. Anyway, many thanks for your responsiveness here.