yashsingh1/xdaforums huggingface dataset:
[Magisk] edzamber:
[MENTION=4470081]topjohnwu[/MENTION]

Hi all,

Do you know how to install a Package into data partition with pm command by edify script or sh script ?

I tryed this but no luck :

run_program("/system/bin/pm", "install", "/data/app/Magisk.apk");

I search into Magisk script how it install Magisk apk from common folder but i don't find how it working...

I took Magisk apk exemple but i would like to install any apk in my Rom's updater-script into Data partition because package_extract_dir command working but app not appear in app drawer after reboot..

Many thanks for help.
[Magisk] raphael.e:
Root not sticking after reboot, apps not shown in superuser menu after root granted and no logs for root available. However logs attached for magisk.

Device Oneplus 3t

Unofficial lineageos 15.1

Magisk 15.2 (1520)
[Magisk] pat357:
You should use package_extract_file and also need to set the proper permissions :

package_extract_file("com.piriform.ccleaner.apk", "/data/app/com.piriform.ccleaner-1.apk");
set_perm(0, 0, 0644, "/data/app/com.piriform.ccleaner-1.apk");
[Magisk] Sebastl:
Update: If you already read my last post, skip the first part ;)

Specs:

Ulefone Armor 2 7.0 / Kernel 4.4.15 / No F2FS / Allow OEM Unlocking / Bootloader Unlocked / Fresh Stock Rom / Fresh TWRP 3.1.1 / Fresh Magisk 15.2 (1520) Debug Build / Magisk Manager 5.5.3 / Permissive
Modules DO NOT WORK

Searching / Debugging so far:

Magisk Manager Log shows a: [B]mount /dev/block/loop0->/sbin/.core/img failed with 13: Permission denied[/B]
/sbin/.core/img exists and has 755. Manually losetupping and mounting works. (Thx @anvitiousky)

Checked Magisk.log -> Saw nothing enlightning
Checked Magisk_Debug.log -> Saw nothing enlightning
Checked Logcat -> Saw nothing enlightning
Strace log : -> Valid until mount command ( Log matches the loop part from [B]Magisk/core/jni/utils/img.c/*loopsetup[/B] exactly )
[B]16789 mount("/dev/block/loop3", "/sbin/.core/img/", "ext4", 0, NULL) = -1 EACCES (Permission denied)[/B]

Okay, lets analyze the mounting in magisk compared to manually:

losetup /dev/block/loop0 => /dev/block/loop0: [b31b]:1900558 (/data/adb/magisk.img) 'losetup worked after the start - but the mount apparently not
mount /dev/block/loop0 /sbin/.core/img => drwx------ 2 root root 4096 1970-01-01 01:00 lost+found 'manually mounting worked
----vs-----
magisk --mountimg /data/magisk.img /sbin/.core/img => /dev/block/loop1 (/dev/block/loop1: [b31b]:1900558 (/data/magisk.img)) 'finding first free loop worked apparently

Update:

Where is the difference ?

=> Magisk/core/jni/utils/img.c uses xmount(device, target, "ext4", 0, NULL); instead of mount

This leads us to xwrap.c and the corresponding mount syntax.

So lets compare the mount straces:

[B]mount("/dev/block/loop0", "/sbin/.core/img/", "ext4", MS_SILENT, NULL) = 0
mount("/dev/block/loop0", "/sbin/.core/img/", "ext4", 0, NULL) = -1 EACCES (Permission denied)[/B]

I really want to apologize to affected people and also to Ulefone for my wrong conclusion that they shipped without kernel loopback support.

It was a long day, 10pm, no signs of modules, Loopback Device Tester said "No" and the failing "ENXIO" two lines before was just the last part of getting the free loop device :crying:

Im sorry - i hope i found the proper cause now ! If yes - could anybody of the gurus explain what the big difference is ? Just supposed to oppress a warning
[Magisk] topjohnwu:
Very great findings!

I just checked AOSP toybox's implementation, and suprisingly it has the MS_SILENT flag enabled by default!

This will be fixed in the next release
[Magisk] Part.0:
magisk manager 5.5.4 's setting FC !

tried clean install using twrp still FC, and through app manager results the same,, rolled back to 5.5.3 working ok with magisk v15.3. -Oreo 8.1-

*log attached
[Magisk] Indashio:
My log

Problem on Magisk 15. On 14,5 everything working good.

On my Xperia XZ Premium Sony camera not working Does not respond to touch. Google camera takes pictures in green.
[Magisk] korom42:
15.3 still bootloop on Xperia XZ Dual (F8332) latest Oreo firmware 8.0
[Magisk] R324D:
Have anyone face this on latest magisk? I got magisk manager 5.5.4 FC's on magisk 15.3 when opening settings menu inside manager.

Device OnePlus X, Running oreo 8.1,.

Log attached.
[Magisk] bagarwa:
Suggestion

Default duration for root grant

.

I have a suggestion for the Magisk Manager app. When any app requests root access and Magisk su prompt appears, "Forever" option is selected by default. My suggestion is - please provide an option in setting like "Set default grant duration". This way, I can set it to "10 mins" and next time I launch any app that requests root, I can simply tap "grant", without having to switch from Forever to 10 Mins first.

Use Case -

I don't install a new root app every other day. Whatever app I want to have permanent root access, I have already granted them permission and they aren't going to prompt me again.

But there are apps whose root feature I use infrequently. For example, a file manager, or adaway, or Busybox. I want them to have root access only when I'm using their root features. Thus, "10 minutes". And I need to grant this temporary permission every time I use them for the said purpose. So, the ability to set that as the default grant duration will be helpful.
[Magisk] :
FC for me too when clicking on the su menu.. Was okay with magisk 14, on Omni 8.1 OnePlus 3T
[Magisk] SeishiNui18:
Update doesn't stick upon reboot

Updating via Manager 5.5.4 from 15.2 to 15.3 shows successful but doesn't stick with 15.3 after reboot and still shows 15.2

Thanks for the fingerprint feature, works fine for me.
[Magisk] nick491:
Read that others are having this issue as well...

Just installed the latest Magisk Manager 5.5.4 as well as Magisk 15.3 and am unable to launch settings, the app crashes.

Running the latest Nitrogen OS 8.1 and GAPPs 8.1 mini on shamu. Please view the included log.
[Magisk] lalitjoshi06:
Same as previous. Updated to 15.3 but No module workings . failed with 13:permission denied

Data and cache in f2fs.

Magisk Logs attached.
[Magisk] Ja_som:
EDIT: issue solved

https://xdaforums.com/showpost.php?p=75204188&postcount=11

Hello [MENTION=4470081]topjohnwu[/MENTION] I still can't use newer version of Magisk, since v15 my Nexus 5X (stock Android 8.1) does not respond after few hours and I need to hard reboot. The latest working version is v14. Here is my previous report post: https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post74972734
[Magisk] Skittles9823:
What rom? I've had no issues besides hanging on the bootloader on first boot after installing magisk or sometimes a module but a single reboot fixes that. No issues with getting suck while in system here.
[Magisk] Ja_som:
Stock Android 8.1, it is mentioned in my linked post (also it is in my signature, visible via web page), but I added it also to my last one.

I had that hang on boot too, sometimes I had to reboot it 5times to boot, I'm not sure why the device does not respond after few hours. Maybe it does one of my root apps, but I don't know which one. I don't think it can be one of my modules, I tried it w/o them with same result.
[Magisk] SlimSnoopOS:
Do you use f.lux or a screen filter app? I've noticed the same issue on my 5X and was going to troubleshoot this weekend. I've been wanting to figure this out for weeks but haven't had the time yet. This thread below in the 6P forums reports similar issues:

https://xdaforums.com/showthread.php?t=3727651
[Magisk] Ja_som:
Yes, I use f.lux, will try to uninstall it and update back to 15.3, thanks for it.
[Magisk] Sebastl:
Thanks for changing to MS_Silent so fast [MENTION=8369284]topjohnwu Magisk Queries[/MENTION].

But unluckily, MS_Silent didnt seem to be the culprit ;(

The traced down mount calls are identical now, but nonetheless no mounting via --mountimg.

As i am out of ideas now how to narrow this down ive included all relevant logs.

I'm willing to check or try anything out on that phenomenon if you have got some additional ideas.

153_strace_magiskmount.txt = strace log of a mount try with "magisk --mountimg"
153_strace_mount.txt = strace log a manual mount

Sidenotes:

On my Device Safetynet is triggered with both checks on this version.

Recovery log of install complains about "Unable to locate class 'com/topjohnwu/magisk/utils/BootSigner" when updating
[Magisk] peikojose:
I really don't care about that "error" message, but somehow in the older versions I was able of getting rid of it (I don't remember what I did), so now it is impossible to get rid of it or maybe reflashing stock boot.img and then the patched one maybe I can remove it?

Pixel 2, 8.1 stock.
[Magisk] Badger50:
Maybe try this. Worked for me :good:

https://xdaforums.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176/post75171478
[Magisk] TheDevFreak:
Just updated to Magisk 15.3 and I am still getting the same issue. I have attached the log from MagiskManager

the key point is still the

01-12 17:00:22.405 158 163 I Magisk : ** post-fs mode running
01-12 17:00:23.096 158 175 I Magisk : ** post-fs-data mode running
01-12 17:00:23.103 158 175 I Magisk : * Creating /sbin overlay
01-12 17:00:23.104 158 175 I Magisk : * Mounting mirrors
01-12 17:00:23.105 158 175 E Magisk : mount /dev/block/platform/msm_sdcc.1/by-name/system->/sbin/.core/mirror/system failed with 16: Device or resource busy
01-12 17:00:23.105 158 175 I Magisk : mount: /sbin/.core/mirror/system

also this is a module that is trying to load that utilising the /system mirror (and it cannot)

01-12 17:00:23.333 158 175 I Magisk : gWatchVirtualHomeButton: constructing magic mount structure
01-12 17:00:23.335 158 175 E Magisk : opendir: /sbin/.core/mirror/system/app failed with 2: No such file or directory

If any other logs are wanted I will post them, just let me know.
[Magisk] Stunherald:
Installation on Xperia X performance via TWRP fails.

Unable to locate class 'com/topjohnwu/magisk/utils/BootSigner'

and

Unknown ramdisk format! Dumped to ramdisk.cpio.raw

twrp log attached

Thank you in advance if someone could take a look on it :]

//EDIT: Scratch that. This fixes it and that Magisk works flawlessly :]
[Magisk] Sebastl:
One last thought about the MS_Silent Problem (i just call it this way now):

When comparing the manual and --mountimg straces, in manual mode without adding -t it tries to find the proper FS.

After getting Filesystems the first try is ext3:

mount("/dev/block/loop0", "/sbin/.core/img", "ext3", MS_SILENT, NULL) = -1 EACCES (Permission denied)

But the Error is EACCES not EINVAL like in the following tries

mount("/dev/block/loop0", "/sbin/.core/img", "ext3", MS_SILENT, NULL) = -1 EINVAL (Invalid argument)
mount("/dev/block/loop0", "/sbin/.core/img", "ext2", MS_SILENT, NULL) = -1 EINVAL (Invalid argument)
mount("/dev/block/loop0", "/sbin/.core/img", "ext4", MS_SILENT, NULL) = 0

Inbetween is just the following code:

openat(AT_FDCWD, "/dev/block/loop0", O_RDONLY) = 4
ioctl(4, BLKROSET, [0]) = 0

And thats what the toybox implementation responsible for that has to say:

rc = mount(dev, dir, type, flags, opts);
// Did we succeed, fail unrecoverably, or already try read-only?
if (!rc || (errno != EACCES && errno != EROFS) || (flags&MS_RDONLY))
break;
[B] // If we haven't already tried it, use the BLKROSET ioctl to ensure
// that the underlying device isn't read-only.[/B]
if (fd == -1) {
if (toys.optflags & FLAG_v)
printf("trying BLKROSET ioctl on '%s'\n", dev);
if (-1 != (fd = open(dev, O_RDONLY))) {
rc = ioctl(fd, BLKROSET, &ro);
close(fd);
if (!rc) continue;

Worth a try ? Any opinions ?
[Magisk] rmean:
Facing the same problem on 8.1 January update, Pixel (Sailfish). Reinstalling Magisk doesn't help, Flashing in TWRP neither. Filesystem of /data is ext4.
[Magisk] TheDevFreak:
Anyone got any ideas? The issue doesn't produce anything on

/data/adb/magisk_debug.log
[Magisk] korom42:
Finally magisk 1531 booted for my xperia xz on Oreo 8.0 . Noticed that it's breaking sony drm credentials , note this was happening with magisk 14.6 too and last version that works 100% as I mentioned before was 14.5 (1456)
[Magisk] uvera00:
Magisk Manager unable to save superuser request resulting in apps requesting root every launch

logs in attached zip
[Magisk] Tecalote:
Magisk 15.3 working very well on Huawei P9 Thx :)

But on Huawei P8 there's an issue if using Direct Install without enabling AVB2.0/dm-verity (see Screenshot)

After reboot black window with NCK and no mobile network.

Install-Log attached.

If Rooting fresh with TWRP (clean boot.img) the problem isn't and AVB2.0 is not enabled, but if using direct install it becomes the problem
[Magisk] martyfender:
From your description, it sounds like it worked when you flashed an original boot.img, which is always recommended that, though was not totally clear, from what you wrote?

I am certainly not the one to troubleshoot this, but I see several errors that I don't see in my logs:

! Insufficient boot partition size detected

Cannot find the file entry [ramdisk.cpio.xz]

Backup mismatch entry: [init] -> [.backup/init]
[Magisk] Tecalote:
Okay - Huawei P8 Android 6 Firmware b399. (no encryption by default)

Rootet with Magisk 15.2 (flasht in TWRP)

Installed 2 modules: Busybox for Android NDK and SELinux Permissive Script

Everything working.

Got notificatoon: Magisk Update 15.3

Used Direct install - got Problem with NCK

Used Direct Install by enabling checkbox AVB2.0 /dm-verity - problem is solved

What I don't understand is, why enabling dm-verity is necessary by using Direct Install over existing Magisk -

but if phone hasn't Root or flashing clean boot.img and flash Magisk with TWRP - Magisk working without dm-verity checked..

I just wanted to report.
[Magisk] tlf55:
Hi, I've installed the latest magisk beta and I've an issue with safety net .. it's "false"

I'm on a OnePlus 5 Other custom ROM Omni ROM 8.1 latest weekly !

It's not the ROM or the kernel because if I uninstall magisk, safety net is "true"

But when I flash back magisk it's "false" again ..

I've tried to unckeck and check back magisk hide in manager but it's not solving the issue

The weird thing is that even if it's false Android pay and other banking app are still working !

Can you look a it ?

Here's the log
[Magisk] rahulk096:
Can't flash with twrp 3.2.1 on my redmi note 4 oreo
[Magisk] Camlin3:
[MENTION=4470081]topjohnwu[/MENTION]

Log file attached
[Magisk] kryzeK:
I've the problem with f2fs /data on OnePlus 3T running OmniROM 8.1, and I have FC on Superuser session on Magisk Manager.

My logs is attached.
[Magisk] citytrader:
In my Moto Z Play under 7.1.1 I get an error trying to install modules from Magisk Manager (if I do manually install of the modules from the recovery, they never appear listed in Magisk Manager)

Thanks a lot for your efforts and time in resolving any issue.
[Magisk] Didgeridoohan:
It's a known bug, but there's been little useful information found on it yet...

The most common denominator I've find is that a lot of users reporting about it are using Android 8.1 custom ROMs (like OmniROM for those OnePlus users). I've tried to reproduce the problem on my Nexus 6, but couldn't find anything...

What's needed is someone with the issue that can do some proper troubleshooting and find the actual cause.
[Magisk] rom-g:
Thanks U and Didgeridoohan for your support.

This is the output i obtain when i run the script :

u0_a112@osprey_u2:/ $ su
root@osprey_u2:/ # /cache/f2fstest
Creating filesystem with parameters:
Size: 8388608
Block size: 4096
Blocks per group: 32768
Inodes per group: 512
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 2048
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/512 inodes and 1070/2048 blocks
Usage: mount [-r] [-w] [-o options] [-t type] device directory
mkdir: '1': File exists
mkdir: '2': File exists
mkdir: '3': File exists
test
1
2
3
4
test
root@osprey_u2:/ #
[Magisk] buttie:
On HTC 10 Lifestyle AdAway is not showing prompt for root and thus not starting at all, it just sits on empty title screen. Root for other apps (Titanium, MatLog, Total Commander, Power Menu, etc.) works without problem, device also passes SafetyNet check.

Logcat and debug log attached.
[Magisk] dentistgev:
Magisk 15.3 problem with apps

Magisk 15.3 has problems with some apps, like Root rashr, AdAway, no any dialogue windows with root access guarantee. Here is log from Magisk
[Magisk] Ja_som:
About AdAway

https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post75216992

Probably those apps needs to be updated.
[Magisk] gpablo1:
I can't install any module. From manager I receive this error:

From recovery mode I receive the same message. I'm using stock ROM of Oukitel Mix 2 phone.
[Magisk] madbat99:
Is your data partition f2fs?
[Magisk] martyfender:
Magisk manager log. Occasionally, Magisk Manager crashes on launch.

could you please let me know how this log looks?

thanks
[Magisk] Didgeridoohan:
[MENTION=8871551]bootlocked[/MENTION] You're new, so I'm going to give you a few pointers...

First, don't post logs directly in the thread. Attach the file, link it or use a service like Hastebin or Pastebin. If you feel you HAVE to post it directly in the thread, at least use hide tags.

And secondly, make sure you post in the right place or else you just add to the noise and clutter. You wan't the systmless Xposed thread.

Edit: And use the search function. It's often the case that whatever issue you have has been talked about before.

By the way... This goes for a majority of the users posting in this thread! Read the OP. If it has rules for posting, follow them. If it seems like the thread doesn't match what you're looking for, don't post and look for a more appropriate thread..
[Magisk] SacredDeviL666:
Thread cleaned again :cyclops:

Can we respect the Op's requests and any other feature request or suggestions could be discussed in Magisk General Thread.

If someone wants a older version of magisk please search and download from his repo or ask in general this thread isn't for that.

Safety Net & Banking apps will keep breaking and the fix will be temporary, so don't pester with those requests and avoid mentioning the dev's name on every single post!

Thanks and Peace.:highfive:
[Magisk] serajr:
Xperia devices vs Oreo stock firmware drmfix hack

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

I read several reports here about the new versions of magisk being breaking the drmfix for xperia devices, and this is really happening!

I think you no longer need logs to try to fix this issue, since several have already been posted (and from what I read, they are not conclusive). I also think it's best to explain how the hack is made and how it works (in different versions of magisk).

The hack itself is made in the

init.environ.rc

by adding the line in blue:

# set up the global environment
on init
[COLOR="Blue"][B]export LD_PRELOAD libdrmfix.so[/B][/COLOR]
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
...

(libdrmfix.so is present at both folders: /system/vendor/lib(64)/libdrmfix.so)

Output from

export

command - Magisk v14 (1456):

F8131:/ $ export
ANDROID_ASSETS
ANDROID_BOOTLOGO
ANDROID_DATA
ANDROID_ROOT
ANDROID_SOCKET_adbd
ANDROID_STORAGE
ASEC_MOUNTPOINT
BOOTCLASSPATH
DOWNLOAD_CACHE
EXTERNAL_STORAGE
HOME
HOSTNAME
[B][COLOR="blue"]LD_PRELOAD[/COLOR][/B]
LOGNAME
PATH
SHELL
SYSTEMSERVERCLASSPATH
TERM
TMPDIR
USER
F8131:/ $

Output from

export

command - Magisk v15 (1531):

F8131:/ $ export
ANDROID_ASSETS
ANDROID_BOOTLOGO
ANDROID_DATA
ANDROID_ROOT
ANDROID_SOCKET_adbd
ANDROID_STORAGE
ASEC_MOUNTPOINT
BOOTCLASSPATH
DOWNLOAD_CACHE
EXTERNAL_STORAGE
HOME
HOSTNAME
LOGNAME
PATH
SHELL
SYSTEMSERVERCLASSPATH
TERM
TMPDIR
USER
F8131:/ $

LD_PRELOAD was not exported! Maybe exports are being made at a point before root is obtained. It seems that in the latest androids (Oreo in case), LD_PRELOAD needs root (I'm not pretty sure about that).

LD_PRELOAD can still be exported in the

init.rc

(on post-fs) instead of aforementioned file, but with same results!

Well, I hope this clarifies the problem we are facing, and a proper fix be possible.

Thanks in advance!

Nvm... in the end, it was always selinux's fault.

The issue was properly fixed in the xperia stock kernel patching tool(s). For the record, by patching sepolicy file.

Thanks anyway!
[Magisk] SacredDeviL666:
Thread cleaned again.

Why are we discussing about how to install Magisk and IYTB in this thread? (its a rhetorical question, please don't respond)

Please stay on topic as mentioned in OP
[Magisk] gps3dx:
This issue exist for me as well.

01-27 02:22:52.971 1280 1280 I Magisk : Magisk v15.3(1531) daemon started
01-27 02:22:53.037 1280 1286 I Magisk : ** post-fs mode running
01-27 02:22:53.868 1280 1340 I Magisk : ** post-fs-data mode running
01-27 02:22:53.869 1280 1340 I Magisk : * Creating /sbin overlay
01-27 02:22:53.870 1280 1340 I Magisk : * Mounting mirrors
01-27 02:22:53.870 1280 1340 E Magisk : mount /dev/block/mmcblk1p5->/sbin/.core/mirror/system failed with 16: Device or resource busy

I'm on clean nougat 7.1.2 CM 14.1 image from http://www.android-x86.org.

I tried stable magisk v15.3 and beta magisk v15.3(1531) - result is the same.

( difference are in the x86 folder files, i.e magiskboot & magiskinit )

P.S my android is NOT running from an img or sfs file, since i've expanded and extract the system onto my tablet's hdd ext4 partition.

Also, i've added "rw" to "root=/dev/ram0" (i.e it's now "root=/dev/ram0 rw")to the "linux" line in grub, so that my /system is for sure in RW state.

P.S.S also, please note that this issue EXIST even if I don't use the xposed module - so it's a pure magisk issue as reported here by others.

I Attached my logs
[Magisk] VincentJoshuaET:
Magisk logs are empty. Also, /magisk/.core only file is hidelist.

Any reason for this? I think this affects MagiskHide as I can't pass SafetyNet.
[Magisk] DEMONVoz:
1+3, OOS beta 30, oreo, magisk 15.3, clean installing with all wipe. Magisk isn't mounting module's paths. logcat and magisk log in archive

View attachment logs.zip
[Magisk] John2146:
Same here on Z-Unleashed
[Magisk] today1:
I get error for try install Magisk-v15.3(1531).zip FIY using twrp

I have SM-G900F
[Magisk] martyfender:
Have you tried the f2fs loop back fix Magisk module? Or you may need a custom kernel.

https://xdaforums.com/apps/magisk/guide-magisk-official-version-including-t3577875

Info by arter on the f2fs bug:

https://xdaforums.com/showpost.php?p=70492947&postcount=8793
[Magisk] John2146:
Thanks for the more informations. I've already seen the module but I didn't consider it a stable solution. Set garant always in setting is good enough for me:good:
[Magisk] jenslody:
The log states the problem clearly and gives a hint for a solution:

! Boot image patched by other programs
! Please restore stock boot image

You either have another rooting solution installed or a prerooted rom.
[Magisk] uncleabubear:
Oukitel K6 Bug report

Android 7.1.1.

Kernel 4.4.22+

Build Oukitel K6 V22

Thread on XDA

Magisk Beta 1531 flashed with TWRP causes bootloop.

Tried unlocking bootloader and fastboot flash boot patched_boot.img also causes bootloop.

Magisk v14.0 is working but does not upgrade in Magisk Manager.

Recovery log.

Boot.img is in TWRP rar download.

Many thanks Andrew
[Magisk] SacredDeviL666:
Thread cleaned..... AGAIN :silly:
[Magisk] siealex:
Do I need the uninstaller to upgrade Magisk from stable to beta? I want to preserve all installed modules, and the uninstaller erases them and their settings. Or do I need only the stock boot image?
[Magisk] jenslody:
Just do the update, normally nothing special is needed.

The only difference (at the moment) is the more verbose logging ( /data/adb/magisk_debug.log ).
[Magisk] Tecalote:
The only unpleasant sideeffect of cleaning is that the search function refers to entries that can not be found in most cases...

For example if I search in the Thread for Mate 9 I find posts, but when I try to open them I cannot find most posts on the page - just wanted to report ;)