[Magisk] Nodens:
This is a thread to track known workarounds for known issues for Magisk Beta.

DO NOT post any questions or random stuff in this thread as they will be ignored. The point is to have a clear tracking table for known workarounds as they

are currently getting lost in the post spam of the official beta thread. Discussions on workarounds or the problems they aim to fix/alleviate, should happen in the official

thread.

ONLY post known workarounds with references to the posts that introduce them and validate them and I will add them to the list. What you are reporting

must be related to the Magisk Beta. This thread is not about generic issues unrelated to the beta.

Error 1 during installation of v13.0 (96f8efc)

Users who get Error 1 during installation of v13.0 (96f8efc), specifically those who get the following error in the recovery log:

ioctl LOOP_SET_FD failed: Device or resource busy

[MENTION=8340552]jenslody[/MENTION] has made a modified version of (96f8efc) that fixes the problem for many users. LINK HERE. This version uses an older updater-binary script that correctly identifies non-64-bit paths to install Magisk (afaik).

The .zip package has been updated and now also includes the fix for very slow installation on some devices (described below).

Apparently the real issue behind this error is the toolbox failing to mount the loop device as reported by [MENTION=4476591]Deic[/MENTION] here: LINK HERE

The fix is moving the bundled busybox path variable earlier in the path export. I have modified the current update-binary script (which also includes the very slow installation on some devices fix) in the .zip attached here: LINK HERE
​

SafetyNet fails with v.13.0 (96f8efc)

[MENTION=4476591]Deic[/MENTION] has made a module that might solve the issue. LINK HERE. It should be noted that this doesn't fix every possible issue, since some modules like Xposed Framework will trigger SafetyNet no matter what you do. Try disabling all your modules, verify that SafetyNet passes, then one-by-one reactivate the modules to identify the culprit.
​

Viper4Android doesn't work (multiple causes)

Status: Abnormal

If you are using v.13.0 (96e8efc) and V4A installs but the Driver Status says "Status: Abnormal," user [MENTION=7836278]LazerL0rd[/MENTION] provided a solution HERE. Download the .txt file and place it in /magisk/.core/post-fs-data.d/, then change the '.txt' to '.sh'. Change the permissions to 0755.
​

Processing: No in apps like YouTube

This can be remedied in some devices by removing the deep_buffer in the various audio_policy and audio_effects system files. You can make a script to remove these lines yourself or use the Universal Deep_Buffer Remover [AUDMODLIB] module by [MENTION=5357345]ahrion[/MENTION] if you are already using his ViPER4Android FX 2.5.0.5 [AUDMODLIB] module (note that this is not the one found in the Magisk Manager modules repo!).
​

Installation of v.13 beta takes hours!

According to many patient users, the installation will succeed, even if it takes hours. [MENTION=571197]Nodens[/MENTION] explains what the problem is, and a solution for it, in this informative post: LINK HERE.

Modded 96f8efc .zip package by [MENTION=1042140]tdunham[/MENTION] : LINK HERE.

This is fixed in current beta.
​

MagiskHide failing to start.

Magisk log shows the following error:

bind_mount: /dev/magisk/mirror/system/xbin/dexlist -> /system/xbin/dexlist
* Running module post-fs-data scripts
[B]resetprop: prop [persist.magisk.hide] does not exist[/B]
** late_start service mode running
* Running service.d scripts

[MENTION=4317549]_litz[/MENTION] explains the problem and how to fix it here: LINK HERE.
​

Magisk Manager is not getting installed / Magisk Manager FCing

A lot of users report that the installer is not installing the manager automatically for them.

The Manager is included in the .zip file, in directory "common" and is named "magisk.apk. Extract it and install manually.

[MENTION=5046046]p34rp34r[/MENTION] also reports that reinstalling it manually has fixed the Manager FCing for him and other users: LINK HERE.
​

Module installed through Magisk Manager not visible on reboot

There have been several reports about installations of modules through Magisk Manager that are not visible in the Manager on reboot.

The big majority of those reports also report that on second reboot the module is properly listed.

It has also been reported that this never happens when modules are installed through TWRP instead.

According to my tests this also looks fixed on the latest beta. If someone still experiences this on the latest beta, please report it on main thread.
​

Magisk is not available on boot after installation but no error in shown in TWRP

[MENTION=8340552]jenslody[/MENTION] explains the issue and offers a modded zip here: LINK HERE.
​

Credits: The initial list was compiled by [MENTION=5046046]p34rp34r[/MENTION] in this post: LINK HERE.