• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Magisk General Support / Discussion

Search This thread

ionuutzuu

Senior Member
May 9, 2013
68
13
Pitesti
Hello, can any1 help me with a bootloop problem?

I have a Poco F2 Pro which had working magisk module on MIUI 12.2.6.0.RJKEUXM and I received update to 12.5.2.0.RJKEUXM and now when I patch the boot.img it cause a bootloop. If i put the original boot.img it works good, if I wipe data from a custom recovery it also boots.

Does any1 know the cause of my bootloop? Why it works with factory reset and doesn't with all my data? I just don't want to loose and get over from all my stufff. Too many apps and customization to redo. The bad part is that I can't do a rollback... The phone doesn't boot also.
 

pndwal

Senior Member
Hello, can any1 help me with a bootloop problem?

I have a Poco F2 Pro which had working magisk module on MIUI 12.2.6.0.RJKEUXM and I received update to 12.5.2.0.RJKEUXM and now when I patch the boot.img it cause a bootloop. If i put the original boot.img it works good, if I wipe data from a custom recovery it also boots.

Does any1 know the cause of my bootloop? Why it works with factory reset and doesn't with all my data? I just don't want to loose and get over from all my stufff. Too many apps and customization to redo. The bad part is that I can't do a rollback... The phone doesn't boot also.
I believe that's an upgrade from Android 10 to Android 11.

Most likely you didn't disable modules before updating and one or more are incompatible in Android 11.

Research disabling modules using Safe Mode or placing file flags in data/adb/

Eg:
https://topjohnwu.github.io/Magisk/faq.html#q-i-installed-a-module-and-it-bootlooped-my-device-help
Or:
https://www.didgeridoohan.com/magisk/MagiskModuleIssues#

😎 PW
 
Last edited:
  • Like
Reactions: J.Michael

pndwal

Senior Member
Nope. I haven't. What can I do now? Magisk manager is uninstalled. How modules could load without manager installed?
Sorry, wrong.

App data in Magisk App only affects a few app specific settings.

data/adb/ directory stores modules, SU settings, hidelist (now denylist) etc etc, and these survive App uninstall... Magisk still functions with all settings without App...

Adding links in post above. PW
 
Last edited:
  • Like
Reactions: J.Michael

jnshk

Member
Jan 20, 2014
23
5
Is there anything in your module other than the directory tree you want overlaid?
In particular, is there a hidden file ".disable"?
Could you post the output of "ls -alR /data/adb/modules/module-name"?
Thank you for following up to help me sort this out! I didn't see anything in either of the modules' contents that would indicate a problem. Here is the output of the ls command for the 2 modules:

EDIT: Do the permissions look correct? Have I somehow ended up with incorrect permissions on necessary files?

Code:
:/ # ls -alR /data/adb/modules/busybox-ndk
/data/adb/modules/busybox-ndk:
total 13
drwxr-xr-x 3 root root 3488 2021-10-23 09:56 .
drwxr-xr-x 4 root root 3488 2021-10-23 17:02 ..
-rw-r--r-- 1 root root    0 2021-10-23 09:55 auto_mount
-rw-r--r-- 1 root root  309 2021-10-23 09:55 module.prop
drwxr-xr-x 3 root root 3488 2021-10-23 17:18 system

/data/adb/modules/busybox-ndk/system:
total 22
drwxr-xr-x 3 root root  3488 2021-10-23 17:18 .
drwxr-xr-x 3 root root  3488 2021-10-23 09:56 ..
drwxr-xr-x 2 root root 20480 2021-10-23 09:55 xbin

/data/adb/modules/busybox-ndk/system/xbin:
total 2059
drwxr-xr-x 2 root root   20480 2021-10-23 09:55 .
drwxr-xr-x 3 root root    3488 2021-10-23 17:18 ..
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 [ -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 [[ -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 acpid -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 adjtimex -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ar -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 arch -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 arp -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 arping -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ascii -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ash -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 awk -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 base32 -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 base64 -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 basename -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 bbconfig -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 beep -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 blkdiscard -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 blkid -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 blockdev -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 brctl -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 bunzip2 -> busybox
-rwxr-xr-x 1 root root 2087000 2021-10-23 09:55 busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 bzcat -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 bzip2 -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 cal -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 cat -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 chat -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 chattr -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 chcon -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 chgrp -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 chmod -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 chown -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 chroot -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 chrt -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 chvt -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 cksum -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 clear -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 cmp -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 comm -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 conspy -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 cp -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 cpio -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 crc32 -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 crond -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 crontab -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 cttyhack -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 cut -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 date -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 dc -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 dd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 deallocvt -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 depmod -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 devmem -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 df -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 dhcprelay -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 diff -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 dirname -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 dmesg -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 dnsd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 dnsdomainname -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 dos2unix -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 du -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 dumpkmap -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 dumpleases -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 echo -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ed -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 egrep -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 eject -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 env -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ether-wake -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 expand -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 expr -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 factor -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 fakeidentd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 false -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 fatattr -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 fbset -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 fbsplash -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 fdflush -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 fdformat -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 fdisk -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 fgconsole -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 fgrep -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 find -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 findfs -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 flash_eraseall -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 flash_lock -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 flash_unlock -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 flock -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 fold -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 free -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 freeramdisk -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 fsck -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 fsck.minix -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 fsfreeze -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 fstrim -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 fsync -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ftpd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ftpget -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ftpput -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 fuser -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 getenforce -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 getopt -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 grep -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 groups -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 gunzip -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 gzip -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 hd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 hdparm -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 head -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 hexdump -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 hexedit -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 hostname -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 httpd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 hush -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 hwclock -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 id -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ifconfig -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ifdown -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ifenslave -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ifplugd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ifup -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 inetd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 inotifyd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 insmod -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 install -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ionice -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 iostat -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ip -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ipaddr -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ipcalc -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ipcrm -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ipcs -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 iplink -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ipneigh -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 iproute -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 iprule -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 iptunnel -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 kbd_mode -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 kill -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 killall -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 killall5 -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 klogd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 less -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 link -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ln -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 loadfont -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 loadkmap -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 logread -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 losetup -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ls -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 lsattr -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 lsmod -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 lsof -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 lspci -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 lsscsi -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 lsusb -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 lzcat -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 lzma -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 lzop -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 lzopcat -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 makedevs -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 makemime -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 man -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 md5sum -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mesg -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 microcom -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mim -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mkdir -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mkdosfs -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mke2fs -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mkfifo -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mkfs.ext2 -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mkfs.minix -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mkfs.reiser -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mkfs.vfat -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mknod -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mkswap -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mktemp -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 modinfo -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 modprobe -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 more -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mount -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mountpoint -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mpstat -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 mv -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 nameif -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 nanddump -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 nandwrite -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 nbd-client -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 nc -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 netstat -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 nice -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 nl -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 nmeter -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 nohup -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 nologin -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 nslookup -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 nuke -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 od -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 openvt -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 partprobe -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 paste -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 patch -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 pgrep -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 pidof -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ping -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ping6 -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 pipe_progress -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 pivot_root -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 pkill -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 pmap -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 popmaildir -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 poweroff -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 powertop -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 printenv -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 printf -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ps -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 pscan -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 pstree -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 pwd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 pwdx -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 raidautorun -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 rdate -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 rdev -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 readlink -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 readprofile -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 realpath -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 reboot -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 reformime -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 renice -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 reset -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 resize -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 resume -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 rev -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 rfkill -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 rm -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 rmdir -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 rmmod -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 route -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 rtcwake -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 run-init -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 run-parts -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 runcon -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 rx -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 script -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 scriptreplay -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 sed -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 selinuxenabled -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 sendmail -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 seq -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 sestatus -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 setconsole -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 setenforce -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 setfattr -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 setfont -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 setkeycodes -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 setlogcons -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 setpriv -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 setserial -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 setsid -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 setuidgid -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 sh -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 sha1sum -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 sha256sum -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 sha3sum -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 sha512sum -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 showkey -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 shred -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 shuf -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 slattach -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 sleep -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 smemcap -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 sort -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 split -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ssl_client -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 start-stop-daemon -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 stat -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 strings -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 stty -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 sum -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 svc -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 svok -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 swapoff -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 swapon -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 switch_root -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 sync -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 sysctl -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 syslogd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 tac -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 tail -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 tar -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 tc -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 tcpsvd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 tee -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 telnet -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 telnetd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 test -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 tftp -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 tftpd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 time -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 timeout -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 top -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 touch -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 tr -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 traceroute -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 traceroute6 -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 true -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 truncate -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ts -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 tty -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ttysize -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 tunctl -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 tune2fs -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ubiattach -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ubidetach -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ubimkvol -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ubirename -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ubirmvol -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ubirsvol -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 ubiupdatevol -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 udhcpc -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 udhcpc6 -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 udhcpd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 udpsvd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 uevent -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 umount -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 uname -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 uncompress -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 unexpand -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 uniq -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 unix2dos -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 unlink -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 unlzma -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 unlzop -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 unshare -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 unxz -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 unzip -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 uptime -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 usleep -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 uudecode -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 uuencode -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 vconfig -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 vi -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 volname -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 watch -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 watchdog -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 wc -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 wget -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 which -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 whoami -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 whois -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 xargs -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 xxd -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 xz -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 xzcat -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 yes -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 zcat -> busybox
lrwxrwxrwx 1 root root      18 2021-10-23 09:55 zcip -> busybox
:/ # ls -alR /data/adb/modules/terminal_systemizer
/data/adb/modules/terminal_systemizer:
total 889
drwxr-xr-x 3 root root   3488 2021-10-23 17:02 .
drwxr-xr-x 4 root root   3488 2021-10-23 17:02 ..
-rw-r--r-- 1 root root 886868 2021-10-23 17:02 aapt
-rw-r--r-- 1 root root   7594 2021-10-23 17:02 mod-util.sh
-rw-r--r-- 1 root root    229 2021-10-23 17:02 module.prop
drwxr-xr-x 3 root root   3488 2021-10-23 17:18 system

/data/adb/modules/terminal_systemizer/system:
total 9
drwxr-xr-x 3 root root 3488 2021-10-23 17:18 .
drwxr-xr-x 3 root root 3488 2021-10-23 17:02 ..
drwxr-xr-x 2 root root 3488 2021-10-23 17:02 xbin

/data/adb/modules/terminal_systemizer/system/xbin:
total 26
drwxr-xr-x 2 root root  3488 2021-10-23 17:02 .
drwxr-xr-x 3 root root  3488 2021-10-23 17:18 ..
-rwxr--r-- 1 root root 17910 2021-10-23 17:02 systemize

Is there some setting in Magisk that might prevent it from making changes to xbin? Or is it possible that I caused some sort of problem during the install process? The install process (simplified) that I followed for this device is to push the su binary to bin and xbin via adb to give temporary root, then install the Magisk manager app to give full root. Once the Magisk manager app was installed, I updated Magisk and manager to current stable releases. After this was done, I manually removed the su binary that I had pushed to bin and xbin (via file explorer) as the current release of Magisk does not seem to use them and complained of multiple installations of root.
 
  • Like
Reactions: J.Michael

peikojose

Senior Member
May 13, 2012
1,038
178
Alpha Telegram group, link in vvb2060's GitHub, check (copy / translate thread there for latest build to see current issues etc).

Works with A12... But new TJW Canary should also as it builds basically the same recent commits... I'd try that with your devices disabled verify requirements.

Nb. While previous Alpha had Riru and Zygisk coexisting happily, seems Zygisk breaks Riru in both latest Alpha and Canary... PW
Thanks, yeah I'm sure we will have to disable verity again, what a pain in the *ss
 
  • Like
Reactions: pndwal

pndwal

Senior Member
Yeah, understood that.

I was asking (for confirmation) if Riru is working for anyone in new Canary W/ Zygisk... (Seems it also breaks in new Canary). PW
Ok, Alpha Dev explains this (Chinese translated):
Magisk alpha discussion group:

Due to lsposed requirements, no longer compatible
Seems latest Zygisk tweeks for new Zygisk LSPosed module now cause unresolved conflicts with Riru (likely due to using the same resources simultaneously I guess).

John committed code to ensure these couldn't coexist some time ago, and vvb2060 reversed this in a few Alpha builds.

Anyway, looks like Riru's fate is sealed going forward.

I'm guessing most Riru modules will move to Zygisk in short order now. Users who want to use Riru modules for any reason will need to forgo Zygisk it seems...

FWIW, I have SafetyNet passing with old USNF 1.2.0 and the Google Play Services SafetyNet process added to the DenyList in new Canary on Redmi Note 8T.

I'll.post Notes for passing SafetyNet for others next. 👍 PW
 

pndwal

Senior Member
Notes for passing SafetyNet in new Magisk

For TJW builds going forward you will need to add Google Play Services process(es) to denylist until a solution for hiding root associated modifications from GPS SafetyNet processes is incorporated in a module. For devices where Magisk resides in /sbin (many pre. Android 11), only deny SafetyNet process, com.google.android.gms.unstable. For Android 11+ etc (non /sbin), deny Main process, com.google.android.gms also. Nb. Once a solution for this is incorporated in Universal SafetyNet Fix (or other), users will likely need to remove the manually added process(es) for the fix to work as intended.

You also need solutions to edit keystore and possibly need to cause model mismatch etc to trigger fallbacks to basic attestation for various types of hardware attestation used if device is equipped for Hardware TEE.

Universal SafetyNet Fix (+Riru) was the best (all in one) solution for this and it even fixed 'sensitive' props issues, but with with Zygisk active we don't have a proper solution yet. (See above.)

Using old USNF 1.2.0 does needed Keystore changes for pre Android 12 ROMs not 'heavily skinned'... Samsung and other users may have issues with the older solution, and could try reverting to pre-Ruru test module here:
https://github.com/kdrag0n/safetynet-fix/pull/13#issuecomment-767863635
This will Shim the keystore service instead of replacing it; it doesn't work for all heavily skinned ROMs, but various custom solutions are linked from same thread. Also, this solution works for some Android 12 ROMs. 🙂

This may be enough to pass, but some devices may need a fix for 'sensitive' props set to 'trigering' values in addition. Just installing MHPC module does this as an alternative to USNF 2.x.x series; it is enabled by default.

If your device is affected by September 2021 Google server end changes, you need to alter model prop (eg by using MHPC w/ Force Basic Attestation configured) in addition to cause fallback to Basic (a simple mismatch causes) for this particular hardware attestation.

-Nb. there are several fallbacks needed but it seems any one type gives Evaluation type = basic, so basic evalType is misleading.
-Nb.2. This early method can cause issues with OEM specific functionality like Galaxystore, camera functions etc as change is seen globally even if close model is selected as is recommended; 2.x series USNF w/ Riru (or Zygisk) can target Google Play Services only.
(See Universal SafetyNet Fix GitHub and notes for individual releases.)

You will also need to spoof a certified fingerprint if ROM is not certified (using a certified fingerprint). - MHPC with a certified fingerprint configured is the best solution.

Enjoy while it lasts! 🤠 PW
 
Last edited:

gorilla p

Recognized Contributor
Nov 30, 2011
3,662
2,833
Milwaukee
Xiaomi Mi Pad 4
OnePlus 9
I woke up this morning to a Magisk app update notification for the first time in a long time.
Ive never had an app update have a problem.
The app updated and now it doesnt work, it crashes as soon as I open it.
Cant open it. Cleared data, rebooted, no luck. Reinstalled previous magisk apk but its not detecting magisk installed.
Any ideas?
 

Qnorsten

Senior Member
Mar 14, 2012
192
86
Notes for passing SafetyNet in new Magisk

For TJW builds going forward you will need to add Google Play Services process(es) to denylist. For devices where Magisk resides in /sbin (many pre. Android 11), only deny SafetyNet process, com.google.android.gms.unstable. For Android 11+ etc (non /sbin), deny Main process, com.google.android.gms also.

You also need solutions to edit keystore, cause model mismatch etc to trigger fallbacks to basic attestation for various types used if device is equipped for Hardware TEE. - Universal SafetyNet Fix (+Riru) was the best (all in one) solution for this, but with with Zygisk active we don't have a proper solution yet. (See above.)

Using old USNF 1.2.0 is enough for devices not affected by September Google server end changes.

If your device is affected, you can pass by altering model prop (eg by using MHPC w/ Force Basic Attestation configured) in addition to cause fallback to basic (simple mismatch causes) for this particular hardware attestation.
-Nb. there are several fallbacks needed but it seems any one type gives Evaluation type = basic, so basic evalType is misleading.
-Nb.2. This early method can cause issues with OEM specific functionality like Galaxystore, camera functions etc as change is seen globally even if close model is selected as is recommended; 2.x series USNF w/ Riru could target Google Play Services only.
(See Universal SafetyNet Fix GitHub and notes for individual releases.)

You will need to spoof a certified fingerprint if ROM is not certified (using a certified fingerprint). - MHPC with certified fingerprint configured is the best solution.

Enjoy while it lasts! 🤠 PW

An alternative to using USNF 1.2.0 for devices that wasn't affeted by September google server end changes is to just use MHPC and enable it to spoof the magisk hide props (https://github.com/Magisk-Modules-R...README.md#setreset-magiskhide-sensitive-props) and enable com.google.android.gms and com.google.android.gms.unstable in the deny list works for me.
 
  • Like
Reactions: BillGoss and ipdev

pndwal

Senior Member
I woke up this morning to a Magisk app update notification for the first time in a long time.
Ive never had an app update have a problem.
The app updated and now it doesnt work, it crashes as soon as I open it.
Cant open it. Cleared data, rebooted, no luck. Reinstalled previous magisk apk but its not detecting magisk installed.
Any ideas?
Did you have App hidden???
 

KaaMyA

Senior Member
Apr 26, 2009
598
158
Bogotá
Samsung Captivate Glide
Moto G
I woke up this morning to a Magisk app update notification for the first time in a long time.
Ive never had an app update have a problem.
The app updated and now it doesnt work, it crashes as soon as I open it.
Cant open it. Cleared data, rebooted, no luck. Reinstalled previous magisk apk but its not detecting magisk installed.
Any ideas?
Welcome to the party!
Please read the last 13 posts before yours.
 

pndwal

Senior Member
An alternative to using USNF 1.2.0 for devices that wasn't affeted by September google server end changes is to just use MHPC and enable it to spoof the magisk hide props (https://github.com/Magisk-Modules-R...README.md#setreset-magiskhide-sensitive-props) and enable com.google.android.gms and com.google.android.gms.unstable in the deny list works for me.
Guessing your device doesn't need Customised Keystore (fake provider) and wasn't affected by either January 12, 2021 or September 2, 2021 Google server end changes then as altering props is not the same. Ie device is old enough to lack required hardware for HKSA (Hardware TEE).

But you're right that this will work for some older devices... A Keystore altering mod will be needed for most however. PW
 

Qnorsten

Senior Member
Mar 14, 2012
192
86
Guessing your device doesn't need Customised Keystore (fake provider) and wasn't affected by either January 12, 2021 or September 2, 2021 Google server end changes then as altering props is not the same. Ie device is old enough to lack required hardware for HKA.
It is a oneplus 8T, but I think you are right. Just offering and alternative for some people.
 

Top Liked Posts

  • 3
    I.e., compared to you, I have additional detection:
    - Restriction on non-SDK interfaces is not working
    This flag in Momo App is related to using a DeOdexed Rom ( your and all the xiaomi.eu roms is deodexed ).
    Most of the stock roms are odexed BUT if someone decide to deodex even one file in his device rom for example: using the SmaliPatcher Module ( Which it will deodexing and patching the services.jar file in the "/system/framework/services.jar" ) then he will get that flag.
    3
    Root checker says I'm not rooted, but titanium backups says I am. Every root app is functioning the same. Substratum, adaway, matlog, and tasker are all still doing their thing. I just can't see anything or change any settings on them through the magisk manager.


    Is it an option to flash the old manager in twrp? I know have two magisk apps on my phone since the half way install of v22 got on here. I have the magisk app and then another one that says magic mask. When I tap on that one I get the install message I described before.
    I assume you updated with Magisk app hidden, and you renamed to 'magic mask' when hiding? This is supposed to work, appart from going from pre ver 22 to 22 or later as per 22.0 Changelog which says "

    RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!"​

    In practice the same / similar issues updating w/ hidden app often occur. (I'd say 50% success rate only)... Result is hidden app has partial control / other cannot see root etc.

    Solution is simple. Locate and uninstall hidden app (may need to uninstall unhidden app also) from device settings, apps, app info list, then reinstall apk. Nb. Your settings / modules won't be affected as they are stored in /data/adb, not app storage. PW
    2
    Working for me.

    View attachment 5475567

    Edit: See you got it sorted...
    Not that I 'sorted out' but they fixed Shamiko - with (42) three other users reported the same problem on TG channel, but when you woke up :), the bug was already fixed in the new Shamiko build (47)

    Anyway, more about my tests with Magisk Alpha 23015, Zygisk+DenyList, Shaniko and Momo v4.0.1:

    With USB debugging disabled, Magisk app repackaged and all modules disabled except Shamiko, I still have:
    - Partitions mounted abnormally
    - Restriction on non-SDK interfaces is not working
    - Bootloader unlocked

    Unfortunately, I cannot get any better than that?!

    I.e., compared to you, I have additional detection:
    - Restriction on non-SDK interfaces is not working

    but on the other side, I don't have yours:
    - Found Magisk
    - ART parameters are abnormal

    ---

    I can Restore Magisk app, enable BusyBox, Systemless hosts, AML, Viper4Android (using v2.7.2.1 - it doesn't switch to Permisive mode) and Smali Patcher (I only patch Secure Screenshots), they don't make any worse, I still have the same three Momo detections as above

    ---

    When I enable Zygisk-LSPosed module, Momo ads:
    - ART parameters are abnormal

    but by disabling the (single) line in the LSPosed system.prop file (workaround suggested by @Eng.Raman), I can avoid that abnormal Art params detection

    And with that workaround all my LSP modules (GravityBox, CustoMIUIzer, Hide My Apps) and their corresponding mods still work correctly

    ---

    When USB debugging in Developer options is enabled, Momo will add:
    - Debugging mode is enabled

    ---

    Finally, I can also enable Systemless debloating (by use of .replace files) and debloat various apps (tested by debloating 25 of them) from /system, /system_ext and /product - with no implications to Momo detections

    However - that's strange, if I debloat any app from /vendor (I tested separately with 3 of them), then Momo immediately detects (and only in that case for me):
    - Found Magisk
    2
    Root checker says I'm not rooted, but titanium backups says I am. Every root app is functioning the same. Substratum, adaway, matlog, and tasker are all still doing their thing. I just can't see anything or change any settings on them through the magisk manager.


    Is it an option to flash the old manager in twrp? I know have two magisk apps on my phone since the half way install of v22 got on here. I have the magisk app and then another one that says magic mask. When I tap on that one I get the install message I described before.

    I assume you updated with Magisk app hidden, and you renamed to 'magic mask' when hiding? This is supposed to work, appart from going from pre ver 22 to 22 or later as per 22.0 Changelog which says "

    RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!"​

    In practice the same / similar issues updating w/ hidden app often occur. (I'd say 50% success rate only)... Result is hidden app has partial control / other cannot see root etc.

    Solution is simple. Locate and uninstall hidden app (may need to uninstall unhidden app also) from device settings, apps, app info list, then reinstall apk. Nb. Your settings / modules won't be affected as they are stored in /data/adb, not app storage. PW
    Just one thing to add. ;)

    If you do not know what version of Magisk is installed.
    You can uninstall all the Magisk apps and reboot.

    Since Magisk is still active on the device, it will install the Magisk stub app on boot.
    Open the stub app and it will prompt to install the full version.
    This will guarantee you get the correct Magisk app version.
    The stub will point to the version of Magisk that the boot image is patched with.

    Cheers. :cowboy:
    2
    First of all, I did multiple searches. The search this thread function does not work correctly for me. My problem is: magisk canary 23015 has no modules. Suggestions online said clear repo cache, That option does not show. touching the layers button does nothing, all I have is install from storage. Can someone tell me how to populate this modules list, or how to download and install the modules to storage? Its a Pixel6Pro. Root is working great so I don't intend to re install.
    There are problems with search in XDA - nevertheless, when you updated Magisk, you could have read the ChangeLog to realize that support for Repo is gone from Canary and there is no such thing as wiping cache or so to 'help'

    Install Fox Magisk Modules Manager root app (sorry, I'm not going to search where from to install, but that was also posted here maybe twice - google for Fox Mmm on the Net)
  • 37
    I've been following the thread for a long time now, and I think some users are still confused regarding the differences between the different variants of Magisk that are available for use. I'm going to try and summarize them here, which should be helpful for everyone:

    Magisk Variant​
    Stable​
    Canary​
    Alpha​
    Custom​
    Release
    Official​
    Official​
    Unofficial​
    Unofficial​
    Maintainer
    topjohnwu​
    topjohnwu​
    vvb2060​
    TheHitMan7​
    Project Link
    Zygisk
    No​
    Yes​
    Yes​
    Yes​
    DenyList
    No​
    Yes​
    Yes​
    No​
    MagiskHide
    Yes​
    No​
    Yes*​
    Yes​
    Modules Repo
    Yes​
    No​
    No​
    Yes​
    Download Link

    *If you turn off Zygisk in Alpha, then DenyList will act like MagiskHide. So essentially, you can have Zygisk On + DenyList or Zygisk Off + DenyList running as MagiskHide.

    In case I've gotten something wrong, or can add more information, please let me know. :) Cheers!
    13
    Great guide, thanks... I think I followed a similar guide from you a while back, but forgot full path requirement... Pinged you as I thought you'd come through! 👍

    I didn't say MagiskBoot was part of Magisk binary however... I clearly said 'magiskboot * binary * isn't working for me'. 😜 ...

    Thanks for the method. PW
    This one might be a bit more confusing. ;)

    Not sure I can operate Magiskboot before I flash it to the device. Once I flash Magisk, I have access to fastboot through recovery, and that's it.
    While catching up last night, I missed that you are not rooted. :oops:

    ---

    Without root, you need a directory with heightened permissions that you can access.

    You should be able to use the /data/local/tmp/ directory.

    Unzip the Magisk apk file and push the appropriate architecture to the device.
    Then set the permissions to be executable.

    Linux/Mac command line example.
    Make the appropriate changes if you use Windows.​
    • Unpack the lib directory from the Magisk apk file.
      unzip app-debug.apk lib*
    • Push the matching Magisk architecture to the device.
      adb push lib/YourDeviceArchitecture/* /data/local/tmp/
    • Push the boot image you want to modify to the device.
      adb push boot.img /data/local/tmp/
    • Set permissions.
      adb shell chmod 0755 /data/local/tmp/*.so
    • Enter adb shell and change directories.
      adb shell
      cd /data/local/tmp/
    • Run the commands using the ./ prefix.
      ./libmagiskboot.so

    Make the changes you want, exit the shell and pull the new-boot image to the computer.
    Reboot into bootloader and boot the new-boot image.

    Note:
    /data/local/tmp/ should be an empty directory.
    You should clear the directory after you are done using it. ;)


    Quick example just unpacking and repacking a boot image without root.
    Magiskboot Example - Pastebin - Link

    Hope it helps more than confuse. 🙃

    Cheers. :cowboy:
    12
    Hi all. :D

    I do not use twitter so, I am out of the loop at times. :confused:
    Links to a few tweets were noted in an issue on USNF github earlier today.

    Seemed to be appropriate to mention here.

    From John Wu.
    PSA: MagiskHide of Magisk v23.0 no longer passes SafetyNet, even with BASIC evalType. Tested on my Pixel 4 XL running stock Android 12 with vanilla Magisk v23.0.

    MagiskHide is *officially* dead. If you need any kind of root hiding, it's the perfect time to find alternatives.
    There are already plenty of "root hiding" modules out there that I'm aware of, some even utilizing the latest features of Magisk canary.

    I'm obligated to distance myself from any tamper detection circumvention, so I will not assist/promote any modules. Do your own research 🙃

    From osm0sis
    *Cough* @kdrag0n's Universal SafetyNet Fix (USNF) *Cough* 😘
    To be specific, Magisk Canary, Zygisk and DenyList enabled, and USNF v2.2.0+ is the way forward. 🤘

    Cheers all. :cowboy:
    10

    Latest Magisk Canary:​

    Magisk (7e9d4512) (23014)​

    • Fix crashes when multiple Zygisk module is installed
    • Fix crashes in magiskboot under certain circumstances
    • Always unload Zygisk itself after post specialize
    • Add module suspension state in Magisk app (riru/zygisk modules)

    Diffs to v23.0​

    • [General] MagiskHide is removed from Magisk
    • [General] Support 64-bit only systems
    • [General] Support Android 12
    • [Zygisk] Introduce new feature: Zygisk
    • [Zygisk] Introduce DenyList feature to revert Magisk features in user selected processes
    • [MagiskBoot] Support patching 32-bit kernel zImages
    • [MagiskBoot] Support boot image header v4
    • [MagiskBoot] Support patching out skip_initramfs from dtb bootargs
    • [MagiskInit] Support /proc/bootconfig for loading boot configurations
    • [MagiskInit] Better support for some Meizu devices
    • [MagiskInit] Better support for some Oppo/Realme devices
    • [MagiskInit] Support init.real on some Sony devices
    • [MagiskPolicy] Load *_compat_cil_file from system_ext
    • [MagiskSU] Use isolated devpts if the kernel supports it
    • [MagiskSU] Fix root shell if isolated mount namespace is set
    • [resetprop] Deleted properties are now wiped from memory instead of just unlinking
    • [App] Build a single APK for all ABIs
    • [App] Switch to use standard bottom navigation bar
    • [App] Downloading modules within the Magisk app is removed
    https://github.com/topjohnwu/magisk-files/blob/55bdc45955e7ba1fe4d296b6fc06f926ebc9ddd1/notes.md
    👍 PW
  • 1070
    This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
    All information, including troubleshoot guides and notes, are in the Announcement Thread
    156
    Hello, I haven't given much support on XDA lately. It can be resulted from
    • University started and I have limited free time. In fact, I mostly develop during midnight
    • I live in Taiwan, which has large time zone differences between my European/American contributors/testers, which usually forces me to stay up late at night to discuss/test stuffs.
    • The new version is about to come, I don't want to spend effort on supporting old releases
    The planned update is delayed again and again, to some point I think I'll shed some light about what has been happening lately, also along with some announcements.

    New Forum!
    As you might have already discovered, Magisk got its own subforum on XDA! Many thanks to all the support you gave me, and much more information/features/support is about to come!
    **For developers supporting all the devices that are not using standard Android boot format, feel free to create threads in this section (actually, PLEASE do so) for your favorite devices after v7 is out. As I currently know, Asus devices require signing the boot image before flashing, and is model dependant; Sony devices seems to use ELF kernel that is unpatchable, or some has two ramdisks (inner + outer), both requires different workarounds; LG bootloader locked devices has to manually "BUMP" the boot image after flashing Magisk..... and there may be lots of other crazy boot image formats that haven't come up to my attention yet.
    It is impossible for me to support all these non-standard boot images, and I hope the community can collaborate to make Magisk running across all the devices. Overall, community collaboration is what XDA about :D

    The Pixel Phone
    Some of you might already know this news, that the next Pixel Phone right around the corner seems like it does not have ramdisk in boot image, which pretty much wrecked Magisk in all ways. However, it pretty much doomed root itself too. Kernel modifications is inevitable IMO, so I'll try to migrate my scripts to C programs that could possibly be included into the kernel itself. Note that I'm not familiar with linux kernel, I'm not even sure if my idea and concept is correct or not. But once the device is available, I think developers will find a way to bypass all the difficulties, and I'll do my best to learn things ;)

    Current Progress
    In the past month, I've spent quite some time learning SELinux, so that I can avoid using SuperSU's sepolicy patches. Thanks to the helps and tips from @phhusson and @Chainfire, I finally have a much clearer understanding of how SELinux works. The Magisk core parts (the scripts, boot image patches, new features, more supports) are actually done some time ago. What is causing all the delays is the Magisk Manager.
    To be completely honest, although I can code in Java without much issues, Magisk Manager is actually my first Android application, I had to reach out for assistance, and fortunately awesome developers like @DVDandroid and @digitalhigh contributed a lot, which makes the current Manager awesome.
    After the repo system and module management is mostly done, I was about to do some adjustments and release, but what we really done is decided to add another feature: auto-unroot with per-app settings. I decided to wait for it to be finished, and then do my adjustments. Due to reasons that'll be mentioned later, this feature will likely not be available for the next release (should come in future updates)

    Safety Net Disaster
    Those who are using Magisk for Safety Net bypass purposes must have known that Google recently updated the detection method of my Systemless Xposed. I still have no idea what Safety Net is detecting, so currently I cannot fix it on my side (also because I'm busy working on the next update). However, suhide developed by @Chainfire is able to hide Xposed and worked fine.
    However, only my Systemless Xposed v86.2, which is based on SuperSU's su.d, is supported using that method. v86.2 and v86.5 (latest, Magisk based) have nearly identical binaries, and the only difference is the path where the binaries are stored.
    I'm still not sure what's the real issue for it not being supported, I just hope it is not done intentionally.

    Conclusion
    Due to the fact that my Safety Net bypass is not 100% perfect now, I do not want to spend any more time waiting for auto-unroot to be polished. What I'm doing now is finishing up all the things I'd like to change in Magisk Manager (it has been a while since I last contributed to Manager, my fellow developers are doing all the heavy job), which might take a little more time, after that, packed with tons of information to be announced in Magisk Section, I'll release the long awaited update.

    Hope this lengthy post gives you the idea of the whole situation, and again thanks for all your support!!
    121
    Ah, some Chainfire bashing, I hope it is not too late for me to exercise additional villainy.

    First, let me make clear I have nothing against @topjohnwu, nor against Magisk. Magisk is an interesting project and it certainly displays @topjohnwu ingenuity and persistence. I don't doubt we will see more interesting things from his hands.

    -------------------------

    What has happened here is not all that dark and complicated, from either end. I returned from holidays, and someone pointed me at Magisk. My first thought: interesting!

    Among other things, the thread lists some issues with SuperSU, which in combination with the phrase The developer also requests users to not bug Chainfire with compatibility requests for SuperSU with Magisk from the portal article, raised my left eyebrow by nigh half an inch. The popular systemless xposed mod is apparently now based on it, and apparently it now no longer works with SuperSU, and apparently I'm not supposed to fix that, nor any of the other found issues. I found that a bit weird. So yes, I have told @topjohnwu that I was a bit surprised he was posting about issues with SuperSU without notifying me about them (I can't fix or help fix issues I'm not aware of, after all).

    He's also spreading a modified version of the SuperSU package, which is not all that uncommon, nor necessarily a problem. I have not looked into what he modified, I only ran a few quick tests on one of my devices, and found some commonly used commands run as root to be broken. I have informed him of this as well.

    It appears the tool of choice for Magisk is phh's Superuser, because of some of the mentioned issues with SuperSU. That's fine by itself, but fixing issues in that superuser by incorporating SuperSU's binaries into it is a somewhat questionable practise. After all, SuperSU is a commercial closed-source package that helps pay for my dinner, and superuser is a direct competitor. I have informed him that I was surprised he did this without asking for permission. I have expressed similar surprise on him spreading a modified version of LiveBoot (which helps pay for a snack now and then).
    @topjohnwu has also stated that Magisk's scripts are largely influenced by mine (I have not checked). Scripts based on mine are used all over the place on XDA, some people have crafted amazing things based on them, I have never made an issue of this (otherwise I would have just made them binaries). But yes, I have also stated to him that I don't think it's very nice to base something on one program, and then using that to (almost exclusively) push something directly competing with that program.

    tl;dr Towards @topjohnwu, I have:
    - expressed surprise he has issues getting Magisk to work with SuperSU, and has chosen not to inform me about those
    - expressed surprise he is using SuperSU binaries in a competing superuser without permission
    - expressed surprise he is posting a modified LiveBoot without permission
    - informed him of issues with the modified SuperSU he has posted
    - let him know I thought it wasn't very nice to be applying my scripts to benefit seemingly exclusively that same competing superuser

    To be crystal clear:
    - I have not asked for an apology
    - I have not asked for Magisk to be abandoned, neither the root hiding nor systemless module parts, and certainly not systemless xposed
    - I have not made an issue of any of this anywhere, until this post
    - I have not even specifically asked for anything to be taken down (though obviously in my opinion the other superuser package mixed with SuperSU's binaries, as well as the LiveBoot package, should go)
    - I have not reported this thread to XDA moderators for copyright violations or otherwise

    While my conversation with @topjohnwu may not win any awards for being friendly (though it may win some for brevity), I think all things considered my response has been rather mild. To be perfectly honest, until the apology post, I thought this was over with already. I think the apology post was triggered because I haven't replied to his last PM for a while - I was in the zone, it happens.

    To emphasize again, I have nothing against @topjohnwu, Magisk, or systemless xposed, and it is certainly not my goal to see any of them go. If it can be made to work together with SuperSU, great.

    I get it though: you think of something, you want to see if you can make it work, you finally get it to work, you publish it, it takes off - enthusiasm gets the better of you. Maybe in the rush some mistakes are made. That doesn't mean you have to just drop it and run. None of my stuff would make it past 0.1 if I stopped at the first big mistake :)

    Aside from said being in the zone coding, I usually regret actually responding to these sort of things the day after, which has made me hesitant to reply. Surprise me.
    76
    Thread temporarily closed so everyone sees this.

    The flood of "SafetyNet isn't working for me either!" posts are not helpful, at all. Please refrain from posting further, it will be looked into. Please do not forget that not passing SafetyNet is 100% NORMAL AND INTENDED when you have an unlocked booloader or running custom firmware. These are workarounds and they will be worked around in turn.

    The Flash
    Forum Moderator

    EDIT: Thread is reopened... I will be cleaning any SafetyNet posts for a while to keep the thread clean for real issues.
    75
    Hello everyone!

    I am aware that Google has updated Safety Net that makes Magisk itself a no go for Android Pay. In fact, I witnessed the change live while I am developing the new magiskhide, which should hide all Magisk modules and Magisk installed root.

    Google is serious about Safety Net now, clearly hunting down all possibility to run Xposed with Safety Net passed. I spend quite some time examining the new security measures last midnight, and fortunately it seems that it is possible to run Magisk and root along with Safety Net if no Xposed is running. I'm glad I removed the old root toggle at the right time lol, that is no longer feasible with the latest detection.

    So stay tuned for the next update, it will come with bug fixes, along with the new magiskhide to bypass that Safety Net.

    Google, how will a few systemless mods do any harm :p:p