List of incompatible modules

[snake-4]

For modules marked with ⚠️, additional steps may be necessary. Modules marked with ❌ are incompatible.

---

[⚠️] Font modules

• To prevent crashes, install HusykDG's FontLoader.
• If you're using Font Manager, try its Fix apps crashing feature.

[⚠️] Modules mounting to /vendor (e.g., ViPER4Android)

• Some browser apps may crash with an EGL error. If you don't experience this issue, no additional steps are needed.
• Set ro.zygote.disable_gl_preload prop to 1 to fix this.

[⚠️] Shamiko

• Requires Zygisk Assistant v2.1.3+ and Shamiko v1.1.1+.

[❌] Modules with runtime resource overlays (e.g., Pixelify)

• Currently, there are no plans to address this issue, but contributions are welcome.

[pexillove]

先刷了这个模块，在刷shamiko，系统直接损坏

[gabriel20xx]

Is there any plan to make this module compatible with Shamiko?

[snake-4]

Is there any plan to make this module compatible with Shamiko?

It should work now if you're using the latest version of both modules.

[EddYTG]

Another module that can't be used with Zygisk Assistance is Youtube RVX root module and youtube music RVX root module every time I tried to install Zygisk Assistance with this 2 module install abd enable after I reboot the Zygisk Assistance module will disappear like it have been remove. That's so sad

[snake-4]

Another module that can't be used with Zygisk Assistance is Youtube RVX root module and youtube music RVX root module every time I tried to install Zygisk Assistance with this 2 module install abd enable after I reboot the Zygisk Assistance module will disappear like it have been remove. That's so sad

It is compatible and this was answered in #15 #40 #43 #67 #68. You have to whitelist the YouTube app, see #67 (comment) for a visual guide of this.

[EddYTG]

Another module that can't be used with Zygisk Assistance is Youtube RVX root module and youtube music RVX root module every time I tried to install Zygisk Assistance with this 2 module install abd enable after I reboot the Zygisk Assistance module will disappear like it have been remove. That's so sad

It is compatible and this was answered in #15 #40 #43 #67 #68. You have to whitelist the YouTube app, see #67 (comment) for a visual guide of this.

Thank you for your guide sir. The module I was used is from rvx team not the one that #67answer any way i have change to those module and now it work fine thank you very much sir.

[iscle]

[⚠️] Modules mounting to /vendor (e.g., ViPER4Android)

Hi! Thanks for your work, it's really interesting to see how root gets hidden. I'm one of the devs working on the reverse-engineered ViPER4Android. What's the issue with it? Do you have some recommendations to fix it? :)

[snake-4]

[⚠️] Modules mounting to /vendor (e.g., ViPER4Android)

Hi! Thanks for your work, it's really interesting to see how root gets hidden. I'm one of the devs working on the reverse-engineered ViPER4Android. What's the issue with it? Do you have some recommendations to fix it? :)

It's not really related to ViPER4A, but to some versions of Adreno EGL drivers. Since the module mounts to /vendor, APatch and KSU will mount an overlayfs at /vendor.

This makes all file IO go through that device before it is unmounted and results in different inode and/or dev values for the same path (depending on the kernel config).

The EGL driver fails to load OpenGL 3.1+ extension if EGL was preloaded before the Zygote fork and the overlayfs was unmounted afterwards due to the effect I've mentioned. Unfortunately I don't have a device with such driver so I couldn't debug the issue myself.

[backslashxx]

[⚠️] Modules mounting to /vendor (e.g., ViPER4Android)

Hi! Thanks for your work, it's really interesting to see how root gets hidden. I'm one of the devs working on the reverse-engineered ViPER4Android. What's the issue with it? Do you have some recommendations to fix it? :)

I have a bit of a workaround for this but this will require overlayfs.
you can inject something like this on module's post-fs-data.sh

MODDIR="${0%/*}"
# you can fake this to whaever, you can even
# mimic a vendor mount like my_bigball
modid="vendor_audio"

# make sure $MODDIR/skip_mount exists!
# this way root manager wont mount it
# we handle the mounting ourselves
[ ! -f $MODDIR/skip_mount ] && touch $MODDIR/skip_mount

[ -w /mnt ] && basefolder=/mnt
[ -w /mnt/vendor ] && basefolder=/mnt/vendor

mkdir $basefolder/$modid

cd $MODDIR

for i in $(ls -d */*); do
	mkdir -p $basefolder/$modid/$i
	mount --bind $MODDIR/$i $basefolder/$modid/$i
	mount -t overlay -o "lowerdir=$basefolder/$modid/$i:/$i" overlay /$i
done

I guess this is a vendor-mount-mimicking method / hiding-in-plain-sight.
It will global mount things though so, it is a double edged sword.
but yeah detectors don't flag for it yet since it is harder to differentiate.

If its of any use, I can PR to your repo, just point me where.

Demo: https://github.com/backslashxx/weebu/