yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Since you've got reboots, I'd be interested in seeing your /sys/fs/pstore/console-ramoops, if there is one.

If it's this module, it's outdated and needs to be updated to a current module template.

I'm not sure what you mean by 14.9. There hasn't been a Magisk v14.9...
[Magisk] korom42:
[MENTION=4667597]Didgeridoohan[/MENTION] [MENTION=4470081]topjohnwu[/MENTION] I want to inform developer that we are using

this tool

to patch oreo stock kernels to make it rootable + fix DRM, maybe this could help understanding how new xperia kernels work ..

I already posted debug logs for :

Magisk-v14.5(1456)

(100% working)

#5101 + stock kernel img (Patched with the tool mentioned above)

Magisk v14.6 (Breaks DRM) #4652

Magisk v15.0 (bootloop) #4793

Magisk v15.1 (bootloop) #5073
[Magisk] Veid71:
my bad, i thought i attached them but i suppose not, but either way ive attached them to the original one and this one. let me know if theres anything else i can help with ^_^ [MENTION=4470081]topjohnwu[/MENTION] [MENTION=4403217]Pkt_Lnt[/MENTION]
[Magisk] tdhite:
Recovery Install == No magisk.img

The magisk.img is not created on clean install of Magisk 15.10. Versions less than 15 always work properly.

Setup:

1) Galaxy S6 (G920P)

2) Clean rom install (data and cache wiped; means Dalvik also wiped by definition);

3) Install Magisk 15.1 -- No magisk.img is created.

Logs attached:

recovery.log

directory listing of /data and /data/adb (recursive on the latter) after flashing Magisk 15.10.

This is repeatable, and it does not matter whether stock boot image is placed, or a custom kernel (boot image). Magisk fails to properly install identically, though reports successful installation.

[edit]The file uploader does not (for whatever reason) show two log files uploaded, so I place the data directory listing in a hidden listing below.

/data:
drwx------ 3 root root 4096 Dec 30 17:11 adb
drwxrwx--- 2 root root 4096 Apr 25 2016 lost+found
drwxrwx--- 5 media_rw media_rw 4096 Apr 23 2017 media
drwxrwx--t 3 system misc 4096 Dec 30 14:53 misc
-rw-r--r-- 1 root root 11279324 Dec 30 17:11 stock_boot_474a00ac328f0e5d4c46119195c92a0382eae001.img.gz
drwxrwxr-x 2 system system 4096 Dec 30 14:53 system

/data/adb:
drwxr-xr-x 3 root root 4096 Dec 30 17:11 magisk

/data/adb/magisk:
-rwxr-xr-x 1 root root 5987 Dec 30 17:11 boot_patch.sh
-rwxr-xr-x 1 root root 1002396 Dec 30 17:11 busybox
drwxr-xr-x 2 root root 4096 Dec 30 17:11 chromeos
-rwxr-xr-x 1 root root 109552 Dec 30 17:11 magisk
-rwxr-xr-x 1 root root 2464536 Dec 30 17:11 magisk.apk
-rwxr-xr-x 1 root root 287344 Dec 30 17:11 magiskboot
-rwxr-xr-x 1 root root 790056 Dec 30 17:11 magiskinit
-rwxr-xr-x 1 root root 11250 Dec 30 17:11 util_functions.sh

/data/adb/magisk/chromeos:
-rwxr-xr-x 1 root root 548140 Dec 30 17:11 futility
-rwxr-xr-x 1 root root 1208 Dec 30 17:11 kernel.keyblock
-rwxr-xr-x 1 root root 1199 Dec 30 17:11 kernel_data_key.vbprivk
/data:
drwx------ 3 root root 4096 Dec 30 17:11 adb
drwxrwx--- 2 root root 4096 Apr 25 2016 lost+found
drwxrwx--- 5 media_rw media_rw 4096 Apr 23 2017 media
drwxrwx--t 3 system misc 4096 Dec 30 14:53 misc
-rw-r--r-- 1 root root 11279324 Dec 30 17:11 stock_boot_474a00ac328f0e5d4c46119195c92a0382eae001.img.gz
drwxrwxr-x 2 system system 4096 Dec 30 14:53 system

/data/adb:
drwxr-xr-x 3 root root 4096 Dec 30 17:11 magisk

/data/adb/magisk:
-rwxr-xr-x 1 root root 5987 Dec 30 17:11 boot_patch.sh
-rwxr-xr-x 1 root root 1002396 Dec 30 17:11 busybox
drwxr-xr-x 2 root root 4096 Dec 30 17:11 chromeos
-rwxr-xr-x 1 root root 109552 Dec 30 17:11 magisk
-rwxr-xr-x 1 root root 2464536 Dec 30 17:11 magisk.apk
-rwxr-xr-x 1 root root 287344 Dec 30 17:11 magiskboot
-rwxr-xr-x 1 root root 790056 Dec 30 17:11 magiskinit
-rwxr-xr-x 1 root root 11250 Dec 30 17:11 util_functions.sh

/data/adb/magisk/chromeos:
-rwxr-xr-x 1 root root 548140 Dec 30 17:11 futility
-rwxr-xr-x 1 root root 1208 Dec 30 17:11 kernel.keyblock
-rwxr-xr-x 1 root root 1199 Dec 30 17:11 kernel_data_key.vbprivk

/data/lost+found:
[Magisk] Didgeridoohan:
You sure about the "less than 15" thing? If I remember correctly, the magisk.img creation was removed from the installation process with Magisk v14.0 and moved to boot and/or module installation. Flashing a template 1400+ module after a Magisk installation, or simply rebooting, should create the Magisk image if it's not available.

In other words, it's intended...
[Magisk] gilcu3:
I don't have that file:

1|hammerhead:/ # ls /sys/fs/
cgroup/ ext4/ f2fs/ fuse/ selinux/

Regarding to my suspicion on USSD Dual Widget app, now I realize I see that line cos it happens everytime the device boots, so it shouldn't be the cause of the reboot. Any other log I should extract? I really have no clue. In 14.0 I randomly lost root (and had to reboot to fix). I know that changed in 14.3 beta, and remains in 15.0, 15.1, maybe that is the source of the problem now (just a guess)
[Magisk] tdhite:
All 14.x versions create magisk.img on flash. That is 100% correct, in fact, otherwise kernels cannot install a module post kernel installation. Further, debloating ROMs, which prefer to *not* have Preload (carrier 'bloat' software) install want to install their modules before the first boot. It will be a terrible plan, imho, to force a complete reboot before allowing for module installation, which is the effect of not creating magisk.img at flash. Obviously we module writers can go ahead and create that on the fly, but that's not a good plan, imho.

For example, my SkyHigh kernel does this process (and always worked with all 14.x versions):

1) Install kernel (boot image fixup);

2) install Magisk;

3) Install kernel boot support module.

Hopefully that all helps.

See above -- pretty much defeats the purpose. I can verify that works, though, so will do that. To emphasize the above a slightly different way: removing the ability to properly form the first boot after a data wipe, particularly with custom kernels and debloating ROMs is really a less than thrilling 'new feature' of 15.x if it was truly intended. :(
[Magisk] SacredDeviL666:
Happy New Year in advance if in case i am sloshed with all those beers by the time :cyclops:

As [MENTION=4667597]Didgeridoohan[/MENTION] suggested if you post an issue with a log and then please wait for someone to respond.

The one's who respond please not this thread isn't a HOW TO thread. This thread's sole purpose is to reports bugs of current Beta version along with logs.

Safety Net is the least of priority and it will be fixed/broken as its a cat and mouse game.

Imagine if someone has to go through 400posts of no logs and thank you it works fine. Hey mine works not sure why yours doesn't work cluster !!!

Honestly anyone who is actually willing to read and support wouldn't even bother anymore if you start making a mess out of this thread.

Lets not make this thread a ditch ground for all those unwanted stuff.

Magisk General Support/Discussions

Op's request before you post in this thread.

2017.12.29 Magisk v15.1 Release Note

One of the best guides and troubleshooting methods :- Magisk Installation and troubleshooting
[Magisk] DeimosPhobos:
I have a question, I tried updating from 14.2 to 15.0 and it caused a encryption issue which caused me to have to RUU my HTC Bolt to fix, I'm going to attempt to update again, as I have made a working backup in case of failure, I want to help with logs if it fails, but can someone point me to where the logs will be so I can upload them? I see the instructions for where the logs are, but is this kind of error a different type of log, since the error occurs after update on reboot? Just someone plz point me in right direction!! I want to help!!!
[Magisk] gothicVI:
Could be a corrupted database. Had the same issue some weeks ago. Flashing the uninstaller and reflashing magisk did it for me.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Magisk] mosolicious:
Didn't work for me.

I get two errors in the Magisk log - SuperUser log is empty.

Probably unrelated, however an error nontheless:

fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory

and

sqlite3 open failure: unable to open database file

Full log attached.
[Magisk] bdick21:
I just repeated the last few steps of the Magisk installation instructions with stock boot.img instead of patched_boot.img. So the steps you need to perform are:

1. Copy the stock boot.img to your PC.

2. Flash the stock boot.img to your device using the following command:

fastboot flash boot /path/to/boot.img

3. Reboot your device using the following command:

fastboot reboot

Here's a full tutorial on how to flash boot.img using fastboot:

https://xdaforums.com/showthread.php?t=1752270
[Magisk] SlimSnoopOS:
Hey guys,

For older devices like your Nexus 5, kernel logs are located in this path:

/proc/last_kmsg

If I remember correctly, this log is erased or overwritten on subsequent reboots.
[Magisk] gilcu3:
Yes indeed there is such file in my nexus 5. Will wait for next random reboot, and post file here, thanks for the info!!
[Magisk] RagingHarry:
Sadly must confirm this, my 1+3 and my Galaxy Tab 2 LTE 2016 worked perfect with Magisk v13 and both fail to pass safetyNet.
[Magisk] Iradj:
It seems that the Core Only mode work for most users for now. Oh man how Google managed to detect Installed Modules.
[Magisk] psychoela:
safetynet failed but apps in the list magisk hide still can use without problems,lol:eek:
[Magisk] YellowTM:
Is Core only mode working for latest beta? Because enabling it isn't doing anything for me, both still fail.
[Magisk] RagingHarry:
Nice tip just tried with uninstall in my only addon, osmosis busybox, passes safetyNet in both occasions.
[Magisk] JEANRIVERA:
if you have actually modified system core only mode will probably still fail
[Magisk] Toutatis_:
I'm still passing SafetyNet with b3da28e (Nexus 6P / Dirty Unicorns) :confused:

Edit: I'm not using any module though.
[Magisk] koko115:
Galaxy s8+ On latest beta magisk safetynet pass only when i disable all modules then reboot. If only one module is on, then after restart safetynet fail.
[Magisk] Bobthahog:
Safety net now fails on my Sprint Galaxy note 5. Still on version 12 but just passed it yesterday.
[Magisk] Hawtpants:
I installed a module through TWRP but it doesn't show up in the module list. Is this normal? Also, I am having installation errors when trying to install things through the repo. First time using Magisk.
[Magisk] Nomelas:
Looks like it's certain modules. If I disable the adblock module, SafetyNet passes again.
[Magisk] jaredallard:
I updated to magisk v13 and some apps randomly crash, well, a lot do. Some don't. Webview stopped showing up as well.
[Magisk] Captain_Throwback:
Please read the OP.
[Magisk] mttrwlnd:
Currently, the only modules I'm using are Viper4Android, and the Audio Modification Library it depends on.

Magisk Hide fails with a CTS mismatch when those are on, so I had to enable Core mode..
[Magisk] bayran321:
I have magisk v12 Safety net now fails and yesterday passed it
[Magisk] ottopilot:
magisk v13.0 success on XT1575
[Magisk] JEANRIVERA:
Any modules active?
[Magisk] Captain_Throwback:
I think everyone is getting distracted by the recent change to SafetyNet. This thread isn't really to report that SafetyNet is or isn't passing. Let's try to stick to issues with the Beta release related to installation errors and functional issues. I'm 100% certain that [MENTION=4470081]topjohnwu[/MENTION] knows about the change to SafetyNet.
[Magisk] wangdaning:
On a Huawei Nova CAZ-AL10. Magisk v12 never worked, would always lose root. The beta flashes fine and all looks good in the Manager. Whenever I try to install a module I get "Installation Error!" and if I try in TWRP I get "error 1".
[Magisk] fndpena:
Same here... 6p but 1e87780. I was avoiding the latest after the comments here. I also don't have any modules.
[Magisk] gothicVI:
Maybe try uninstalling, flash clean boot image and flash magisk then. Don't forget to clear caches!

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Magisk] TheDevFreak:
I'm on latest 15.1 with the android wear 2 rom for the LG G Watch W100. I can't use any magisk modules that utilise /system modding.

I think this is due to:

12-31 22:47:20.984 159 176 E Magisk : mount /dev/block/platform/msm_sdcc.1/by-name/system->/sbin/.core/mirror/system failed with 16: Device or resource busy
12-31 22:47:20.984 159 176 I Magisk : mount: /sbin/.core/mirror/system

looks like it's failing to mount the system mirror

If anyone knows a fix i would be very greatful
[Magisk] ImSpooky:
Bootloop on OnePlus 3T (OOS 5.0.1)

The latest update of Magisk has a bootloop issue with the latest version of Oxygen OS on the OnePlus 3T.

I'm not sure how to get logcat when my device is hitting a boot loop, however I will attach my recovery.log file.

The full name of the OTA update file is OnePlus3TOxygen_28_OTA_062_all_1712272248_fc84.zip and it can be found here... https://drive.google.com/uc?id=1lKmMWXLJkTdWuvDKuxmNbyQQrcR5eAjd

Please let me know if there's any more information I can submit, or if there's anything I can run to test stuff out.
[Magisk] merbiyatch:
My mistake sir typo right there. 14.0* anyways thanks for clarifying that it as the modules problem. Would there be an alternative for that module?
[Magisk] Rom:
Same problem boot image by flash in TWRP, problem related to the signature according to the flash log with the latest version of Magisk, would anyone have an idea to solve this problem?

Device and ROM info in my signature.

Thanks in advance.
[Magisk] Didgeridoohan:
Like the other times you've asked, I'm going to answer: That's simply the message that appears when your boot image isn't signed.

Don't worry about it.
[Magisk] Rom:
Indeed, as it can be read in my logs files, indeed my boot image is not signed Ok it is compared to that, but then why is it not taking in consideration by Magisk?

I know i can look stubborn, but my little finger himself tells me he doubts that Magisk does not make his own image, maybe I'm wrong saying that :angel:..

So according to you, it does not affect then?
[Magisk] Didgeridoohan:
It does not affect anything. And actually, that's according to [MENTION=4470081]topjohnwu[/MENTION]. I asked him about that myself when it started appearing in the logs... :p
[Magisk] Rom:
Ok, it's noted. And it's a great news:good:

About the element of your answer:

"And actually, that's according to [MENTION=4470081]topjohnwu[/MENTION]."

I guess it's due to the goodwill of him to filter or not an certain class of flash log.
[Magisk] targitay13:
Trying to install Magisk for the first time.

Samsung XCover3 (SM-G388F), Android 5.1.1

Got original factory firmware from samsung archives and flashed it with ODIN (All of BL, AP, CP, CSC)

Extracted boot.img from AP_xxx file and put it to phone

Downloaded and installed latest Magisk Manager 5.5.3 (86)

But when pressed install - install - patch boot image file and select that boot.img file, i'm getting an error:

- Device platform: arm

- Extracting files

- Use boot image: /data/data/com.topjohnwu.magisk/install/boot.img

- Mounting /system, /vendor

- Unpacking boot image

MagiskBoot v15.2(1520) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/data/data/com.topjohnwu.magisk/install/boot.img]

KERNEL [6618876] @ 0x10008000

RAMDISK [1203180] @ 0x11000000

SECOND [0] @ 0x10f00000

EXTRA [268435712] @ 0x00074000

PAGESIZE [50331648]

OS_VERSION [0.0.1]

PATCH_LEVEL [2000-00]

NAME []

CMDLINE []

Segmentation fault

- Checking ramdisk status

MagiskBoot v15.2(1520) (by topjohnwu) - Boot Image Modification Tool

- Stock boot image detected

- Backing up stock boot image

MagiskBoot v15.2(1520) (by topjohnwu) - Boot Image Modification Tool

Compressing to [stock_boot_37ef352491287df97097e7d424edd7790edd4088.img.gz]

cp: can't stat 'ramdisk.cpio': No such file or directory

- Patching ramdisk

MagiskBoot v15.2(1520) (by topjohnwu) - Boot Image Modification Tool

Add entry [init] (0750)

Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]

Save SHA1: [37ef352491287df97097e7d424edd7790edd4088] -> [.backup/.sha1]

Record new entry: [init] -> [.backup/.rmlist]

Dump cpio: [ramdisk.cpio]

MagiskBoot v15.2(1520) (by topjohnwu) - Boot Image Modification Tool

open: kernel failed with 2: No such file or directory

MagiskBoot v15.2(1520) (by topjohnwu) - Boot Image Modification Tool

open: kernel failed with 2: No such file or directory

- Repacking boot image

MagiskBoot v15.2(1520) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/data/data/com.topjohnwu.magisk/install/boot.img]

KERNEL [6618876] @ 0x10008000

RAMDISK [1203180] @ 0x11000000

SECOND [0] @ 0x10f00000

EXTRA [268435712] @ 0x00074000

PAGESIZE [50331648]

OS_VERSION [0.0.1]

PATCH_LEVEL [2000-00]

NAME []

CMDLINE []

Segmentation fault

! Unable to repack boot image!

Failed!

! Installation failed

What am I doing wrong?
[Magisk] DodoGTA:
Attach your boot image
[Magisk] pat357:
Magisk 14.0 -> 15.2 : sqlite3 open failure: unable to open database file

After updating my Magisk v14.0 -> 15.2 (from inside the Manager, direct install), I got this error in the log :

sqlite3 open failure: unable to open database file

Phone : see signature

complete log is attached :
[Magisk] bggold:
After a couple reboots dtbo gets patched again. Attached is the log before rebooting after dtbo patching. Hope this helps.

Thanks
[Magisk] Veid71:
MM doesnt seem to want to open for some reason so i decided to downgrade to 5.5.2 to see if that was the issue but that doesnt work either not sure whats going on this time heres the log for the install and the log for matlog thanks for any suggestions or ways to fix it guys :) [MENTION=4470081]topjohnwu[/MENTION] [MENTION=4667597]Didgeridoohan[/MENTION]
[Magisk] korom42:
Magisk v15.2 (bootloop)
[Magisk] Jamoeda:
Magisk 15.2, Op5t.

Can't install modules from magisk manager. Root work, safety net pass. You guys have this problem?
[Magisk] koekoek91:
Magisk 15.2 boots fine on my Xperia XZ.

[MENTION=4470081]topjohnwu[/MENTION] [MENTION=4667597]Didgeridoohan[/MENTION]

Sadly Magisk v15.2 is still breaking DRM for our Sony Xperia XZ.

Beta version 14.5 (1456) is still the latest version that works 100% for us.

I've uploaded magisk debug log here: https://ufile.io/uubso
[Magisk] nan0s7:
On op3t, LOS 15.1 (so 8.1 oreo), Magisk 15.2 installs fine, but granting root is broken-ish. Like, the pop-up prompt works fine, and root works when granted, but immediately after granting Magisk forgets about that app, and every time the app requests root it needs to be granted again. Checking in the superuser tab in Magisk Manager shows only the first app granted since initial Magisk install, and the manager app crashes then you try to use any of those toggles for the app that is shown.

Here's the logcat: https://pastebin.com/bzLw74hX

P.S. I've noticed that if my first prompt response since installing Magisk (after uninstalling it) is a deny, the app will crash as soon as I click on the superuser section of the manager app. Don't know if that warrants another logcat, but I'll give one if needed.

---------- Post added at 02:50 AM ---------- Previous post was at 02:42 AM ----------

On my op3t running latest LOS 15.1 (unofficial 8.1) Magisk (15.2) manager (5.5.3) crashes when trying to view and or toggle things in the superuser section of the app. This also has the side-effect of granted apps not "sticking" after I've granted them permission when prompted (yes, when "forever" is selected). But the weird thing is, after a clean install, the first app that is granted root does work fine, but the second and others don't work properly.

Of course a workaround is to just always grant root requests instead of giving a prompt but that isn't the best practice, for sure.

I'll also note this occurs with version 15.1 as well, and doesn't depend on whether I have modules installed or not.

EDIT: Sorry for the dual-post; for some reason my first post was messed up on my end and didn't look like it went through.
[Magisk] targitay13:
Didn't find how to attach the file directly to the forum, so here is the link (active for 7 days) - https://filecloud.me/c1j52z7a4tof.html

(Forum engine prevents me to post links as a very new user, so please copy-paste it...)

Thanks in advance
[Magisk] jenslody:
Works fine here. Can you get the magisk_debug.log after the installation did not work?
[Magisk] DodoGTA:
Your issue is already known: https://github.com/topjohnwu/Magisk/pull/340
[Magisk] Jamoeda:
I can't fix this issue and install modules. Logs attached. Can you guys help?
[Magisk] otyg:
15.2 not installing on xiaomi redmi note 3 pro, if I update from the app it will crash (since 15 - 15.2) , if I update from twrp every reboot will say Magisk Not installed, If I run the magisk uninstaller it says magisk not installed),

I also attached another recover log (recovery1.log), which I upgrade incrementally from 14.0, uninstall , re- install 14 - 15 - 15.1 - 15.2 ) so you can see where error starts

------

edit:

Updated TWRP and Magisk 15.2 seems to install now.
[Magisk] SeishiNui18:
Not updating via Manager

I'm on beta 15.1 and updated Manager to 5.5.3 then tried to update to 15.2 but after reboot still shows 15.1
[MENTION=8369284]topjohnwu Magisk Queries[/MENTION] [MENTION=4667597]Didgeridoohan[/MENTION]
[Magisk] zhenchao:
My MiBox 3S (MDZ-19-AA) can't install Magisk

maybe related to a special ramdisk packing method:confused:

Log and boot.img URL: 1drv "dot" ms/u/s!ArpHBtnXvt7HpSvWDwuDPZS3CKdd
[Magisk] Sebastl:
<Trying 15.2 / NOT having F2FS>

I have the same phenomenon as the guy here.

"mount /dev/block/loop0->/sbin/core/.img failed with 13: permission denied"

A thing we have in common is a custom TWRP from the same guy for similar devices (Ulefone Armor 2 / Blackview BV8000 Pro).

That made me think/check about kernel logging the Magisk installation.

I found the following:

Could the initial problem lie in SELinux Problems of the recovery while installing Magisk?
[Magisk] targitay13:
Still trying to install Magisk to my SM-G388F with non-standard PXA1908 boot.img header...

So that's what I've tried at the moment:

Got Magisk sources from GitHub,

modified bootimg.h as mentioned at https://github.com/topjohnwu/Magisk/pull/340 (little changes to header struct),

rebuilt binaries,

placed all scripts from "scripts" folder, my boot.img and fresh builded "magisk", "magiskboot" (patched) and "magiskinit" files into phone's /data/local/tmp dir,

run boot_patch.sh using adb shell.

With modified magiskboot i successfully got "new-boot.img" file after script.

Then i tried to tar it with Windows 7-zip and flash with Odin (fail)

Tried with cygwin tar (Odin flash fail)

Notiсed, that new-boot.img doesn't have some symbols at the end, after "SEANDROIDENFORCE" text (some signature?), copied it from original boot.img with hex-editor...

Odin still can't flash it.

Magisk Manager always download original Magisk-xxx.zip, which cannot parse non-standard header.

How do i tell it to use my modified binaries?

Or what else can i do, to re-sign new-boot.img (and get "patched_boot.img") using built-in procedures?

Or there is another problem with flashing, not signature?
[Magisk] gargashish0901:
Not able To Install Magisk

Please help as Not Able to Install Magisk via Redwolf twrp. RN4 mido

Log attached

View attachment 4378534

View attachment 4378533
[Magisk] DodoGTA:
Have you made sure to tar it with raw (aka ustar) format?

And, what error Odin gives when trying to flash that .tar file?
[Magisk] targitay13:
Yes, it's ustar format ("ustar" string at byte offset 257).

Odin's log isn't informative. It says simply "FAIL!"...
[Magisk] scruffy0402:
Having the same issue on 5.5.3/14.5 on pixel xl.
[Magisk] BeeWall:
I'm getting the error "/sbin/.core/mirror/bin/magisk: not found" when trying to install template 1500 modules. Log attached, that's the only error. Older modules install fine. The file in question does indeed not exist. Should I make it as a symlink to something?

EDIT: I made the file as a symlink to /root/magisk and it worked.
[Magisk] guest4711:
This is the main folder of magisk 15.++ If it does not exist there seems to be a problem with magisk. Are you sure you have magisk 15 or higher installed?

I'd try to reinstall magisk 15.2, reboot and try again.