[Magisk] toyongbanatero:
Hey guys, I currently have problems with my Magisk installation (I messed up a bit). Here's what happened:

So I installed Magisk a couple days ago, using the patched boot.img method. Everything went well. I also installed Xposed Magisk, but for some reason, it is not compatible with my phone (where I am using my SD card as an adoptable internal memory).

I really needed Xposed so I decided to factory reset my phone, but I forgot to uninstall Magisk first (or more accurately, I didn't know I'll run into problems with that). I was thinking that it wouldn't affect much because the patched boot.img will still be installed right?

After the factory reset, I tried installing Magisk Manager again and yeah, it still said that Magisk v16.0 was installed. I also tried running root apps and I still have root. I tried installing a module in Magisk but it fails. I tried a couple other ones but it really doesn't want me to. Here's the Magisk log:

06-26 10:29:37.378 230 230 I Magisk : Magisk v16.0(1600) daemon started
06-26 10:29:37.384 230 234 I Magisk : ** post-fs mode running
06-26 10:29:44.718 230 368 I Magisk : ** post-fs-data mode running
06-26 18:29:44.722 230 368 I Magisk : * Creating /sbin overlay
06-26 18:29:44.724 230 368 I Magisk : * Mounting mirrors
06-26 18:29:44.724 230 368 I Magisk : mount: /sbin/.core/mirror/system
06-26 18:29:44.725 230 368 I Magisk : link: /sbin/.core/mirror/vendor
06-26 18:29:44.726 230 368 E Magisk : mount /data/adb/magisk->/sbin/.core/mirror/bin failed with 2: No such file or directory
06-26 18:29:44.726 230 368 I Magisk : bind_mount: /sbin/.core/mirror/bin
06-26 18:29:44.726 230 368 I Magisk : * Setting up internal busybox
06-26 18:29:44.727 369 369 E Magisk : execvpe failed with 2: No such file or directory
06-26 18:29:44.730 230 368 E Magisk : symlink /sbin/.core/mirror/bin/busybox->/sbin/.core/busybox/busybox failed with 17: File exists
06-26 18:29:45.111 230 422 I Magisk : ** late_start service mode running
06-26 18:29:45.113 230 422 I Magisk : * Running service.d scripts
06-26 18:29:45.113 230 422 E Magisk : opendir: /sbin/.core/img/.core/service.d failed with 2: No such file or directory
06-26 18:29:45.113 230 422 I Magisk : * Running module service scripts

Here's the log while installing a certain module:

- Copying zip to temp directory
- Installing Volume_Steps_Increase-14.0.0.zip
- Mounting /system, /vendor, /data, /cache
***********************************
! /data/magisk isn't setup properly!
! Please install Magisk v14.0+!
***********************************
Failed!
! Installation failed

After that, I tried flashing my stock boot.img back (but I didn't uninstall the app, which probably made it more worse?), rebooting then flashed the patched boot.img again. I don't remember if I tried uninstalling from the Magisk app but I think I did. After several trial and error, nothing's changed.

The last thing I tried was to install v16.4 directly from the Magisk app, and it was successfully installed, but I still couldn't install modules. However, the Magisk log looks like this now (and only just these lines):

06-26 23:01:23.946 464 499 E Magisk : fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
06-26 23:01:24.055 464 499 E Magisk : fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory

If anyone has any general suggestion on what I should do, I would be very thankful.

I was planning on uninstalling Magisk (again?) from the Manager app but I decided that I should consult here first. Thanks!

EDIT:

I tried to uninstall completely Magisk today (in the app then flashing my stock boot.img back), then factory resetting again, and setting up everything again in hopes that it would solve my problem, but it didn't. I can't do the custom recovery installation because my phone won't let me reboot to the custom recovery and just replaces the stock one. Any kind of help is very much appreciated.

I do have root so anyone who have suggestions on what files I should edit in the magisk folders (if there's a chance it will fix it), I'll be glad to try it. Thanks!