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

Magisk General Support / Discussion

Search This thread

pndwal

Senior Member
It is a oneplus 8T, but I think you are right. Just offering and alternative for some people.
Haha - recent device!

But you brand may well be why Google haven't fully switched on Hardware TEE!

They messed up TEE Attestation implementation so Google switched it off at server end in March 2020 (?) and have since been waiting for OEMs like OnePlus to fix it on their devices apparently... Google selectively applies it ATM, and I'm not sure if any OnePlus users see evalType HARDWARE.

Don't think you actually need the sensitive - props fix offered by MHPC in place of USNF to pass SafetyNet; I'm fairly sure the same props fix is not implemented in USNF till 2.x.x series, so I shouldn't have this now and still pass.

Of course you may need this as I believe props set to 'trigering' values is devices dependant... You could simply disable MHPC to see if you still pass, but only if you don't also require fingerprint spoofing in addition. (You may have tried this).

I'll edit my post above to indicate that some devices may need sensitive props fix in addition! 😁 PW
 
Last edited:

Qnorsten

Senior Member
Mar 14, 2012
192
86
Haha - recent device!

But you brand may well be why Google haven't fully switched on Hardware TEE!

They messed up TEE Attestation implementation so Google switched it off at server end in March 2020 (?) and have since been waiting for OEMs like OnePlus to fix it on their devices apparently... Google selectively applies it ATM, and I'm not sure if any OnePlus users see evalType HARDWARE.

Don't think you actually need the sensitive - props fix offered by MHPC in place of USNF to pass SafetyNet; I'm fairly sure the same props fix is not implemented in USNF till 2.x.x series, so I shouldn't have this now and still pass.

Of course you may need this as I believe props set to 'trigering' values is devices dependant... You could simply disable MHPC to see if you still pass, but only if you don't also require fingerprint spoofing in addition. (You may have tried this).

I'll edit my post above to indicate that some devices may need sensitive props fix in addition! 😁 PW
Yea I saw Hardware evaltype for my old oneplus 5 in 2020, but then they changed it back. I know it probably won't last forever, but right now I am happy as long as I don't need to bother with custom keystores or anything. Lets hope the OEMs take their sweet time in fixing the attestation implementations

The props fixes are already included in the latest USNF, so you don't need to use MHPC for these in that case. Not sure if they were included in USNF 1.2.0 or not.

Was just offering an alternative for some devices that don't need USNF at all.
 
Last edited:
  • Like
Reactions: pndwal

ipdev

Recognized Contributor
Feb 14, 2016
1,609
1
2,154
Google Nexus 10
Nexus 7 (2013)
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
USNF v1.2 did not support Android 12 so, a no go for those that updated to 12. :(

While I was messing around this morning, I rolled my Pixel 5 back to Android 11.

Stock Google (Android 11 October build).
Magisk canary.
USNF v1.2 module.
MHPC module (activated the sensitive props).
Code:
MagiskHide Props Config v6.1.0
by Didgeridoohan @ XDA Developers

=====================================
 MagiskHide props (active)
 Select an option below:
=====================================

Set/reset MagiskHide sensitive props.

Note that only props that originally are
set to sensitive values will show in the list.

1 - ro.boot.vbmeta.device_state (active)
2 - ro.boot.verifiedbootstate (active)
3 - ro.boot.flash.locked (active)
r - Reset all props
s - Boot stage
b - Go back to main menu
e - Exit
Enabling Zygisk, adding com.google.android.gms.unstable and com.google.android.gms to the DenyList.

Was enough to pass SafetyNet and keep Play certification.
No need to use MHPC's Force BASIC key attestation option.

Cheers. :cowboy:
 

pndwal

Senior Member
USNF v1.2 did not support Android 12 so, a no go for those that updated to 12. :(

While I was messing around this morning, I rolled my Pixel 5 back to Android 11.

Stock Google (Android 11 October build).
Magisk canary.
USNF v1.2 module.
MHPC module (activated the sensitive props).
Code:
MagiskHide Props Config v6.1.0
by Didgeridoohan @ XDA Developers

=====================================
 MagiskHide props (active)
 Select an option below:
=====================================

Set/reset MagiskHide sensitive props.

Note that only props that originally are
set to sensitive values will show in the list.

1 - ro.boot.vbmeta.device_state (active)
2 - ro.boot.verifiedbootstate (active)
3 - ro.boot.flash.locked (active)
r - Reset all props
s - Boot stage
b - Go back to main menu
e - Exit
Enabling Zygisk, adding com.google.android.gms.unstable and com.google.android.gms to the DenyList.

Was enough to pass SafetyNet and keep Play certification.
No need to use MHPC's Force BASIC key attestation option.

Cheers. :cowboy:
Thanks for that...

I've already edited the post to indicate old test module for 'Shim Keystore' is better for Samsung etc w heavy skins...

This also is reported to work for some Android 12 (Pixel 3xl reported) devices, so may be worth trying on P5.

I'll add note regarding Android 12. 😉 PW
 
Last edited:
  • Like
Reactions: ipdev

zgfg

Senior Member
Oct 10, 2016
6,054
3,552
Ok, Alpha Dev explains this (Chinese translated):

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
Yes, no other way, but LSPosed Zygisk version runs fine

It means that you must sacrifice Riru-Momohider (since Riru is sacrificed) and therefore you can no more hide su from the path (maybe there will be a new Momohider for Zygisk, if possible)

However, Zygisk itself is easily detectable, hence the hunting season for banking and similar apps is now open (SafetyNet can still pass but the apps long ago started to evaluate other methods to detect root, and the Zygisk detection code is open source)

But generally, with the new Magisk, Google got what they approved
 

Attachments

  • 1.jpg
    1.jpg
    132.7 KB · Views: 158
  • 2.jpg
    2.jpg
    294.9 KB · Views: 150
  • 3.jpg
    3.jpg
    225.3 KB · Views: 144
  • 4.jpg
    4.jpg
    151.2 KB · Views: 138
  • 5.jpg
    5.jpg
    144.7 KB · Views: 159
Last edited:

J.Michael

Recognized Contributor
Jan 20, 2018
913
797
Samsung Galaxy Tab A series
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.
If all you are doing is trying to replace / insert files in /system, I don't think you need anything other than "system" in the module directory. Try removing the "auto_mount" and "module.prop".
 

zgfg

Senior Member
Oct 10, 2016
6,054
3,552
If all you are doing is trying to replace / insert files in /system, I don't think you need anything other than "system" in the module directory. Try removing the "auto_mount" and "module.prop".
module.prop is metadata (open as text and you can read), to display info about the particular module
 

Attachments

  • IMG_20211024_225255.jpg
    IMG_20211024_225255.jpg
    187.2 KB · Views: 65
  • IMG_20211024_225028.jpg
    IMG_20211024_225028.jpg
    110.9 KB · Views: 65
  • Like
Reactions: J.Michael

pndwal

Senior Member
Yes, no other way, but LSPosed Zygisk version runs fine

It means that you must sacrifice Riru-Momohider (since Riru is sacrificed) and therefore you can no more hide su from the path (maybe there will be a new Momohider for Zygisk, if possible)

However, Zygisk itself is easily detectable, hence the hunting season for banking and similar apps is now open (SafetyNet can still pass but the apps long ago started to evaluate other methods to detect root, and the Zygisk detection code is open source)

But generally, with the new Magisk, Google got what they approved
It's early days, but while I have no real insight into effective hiding of Zygisk and acknowledge that some have said it can't be hidden I've yet to see any convincing proof or reasoning to support this.

Given its close resemblance to Riru, I wonder if we may see a Zygisk hiding module down the track, or if such efforts will come to light.

I'd love to hear from any with more understanding of how Zygote forks (clones?) processes, how apps detect Magisk-in-Zygote (Zygisk), difference with Riru etc.

Current Riru method for injecting into zygote using the "native bridge" is from Canyie (author of Riru-Momohider) and the hidden mechanism for hiding this by making the memory of Riru and module "anonymous memory" hidden from /proc/maps string scanning is from Haruue Icymoon (+ his 22 contributors?)

Is Zygisk injection method essentially the same? And could a similar memory hiding mechanism achieve effective Zygisk hiding?... PW
 

prot-

Senior Member
Jan 16, 2013
744
121
So there's no point updating magisk today if it's just gonna break things and it's already working as is right ?
 

pndwal

Senior Member
So there's no point updating magisk today if it's just gonna break things and it's already working as is right ?
It's only broken Riru as far as I can tell to date, and there are fixes / workarounds for most functions that relied on Riru already. See this re. Universal SafetyNet Fix 2.x series stop-gaps till we get Zygisk USNF for example:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85825005

Going forward, many modules will likely be built for Zygisk (John already gave tutorial:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85824367 ), and a fix is desirable for current Zygisk detection, but nothing else is broken including Bank apps as yet unless you cannot now hide as effectively from these w/ Zygisk...

The fact that Bank apps will likely build in Zygisk detection as new Magisk gains traction is a valid concern however. PW
 
Last edited:
  • Like
Reactions: Eng.Raman

martyfender

Senior Member
Mar 9, 2017
3,174
1,694
Indianapolis, IN
A second Magisk alpha was released today and it has been good so far, with one exception, before I re-hid the Magisk app, zygisk did not show as active. Also, after you install the Magisk apk and open it, you now get the update box showing that a Magisk update is available. That is strange, since I can find no evidence of new updates on vvb2060's github page, so where is his alpha channel hosted?
 
Last edited:
  • Like
Reactions: pndwal

pndwal

Senior Member
A second Magisk alpha was released today and it has been good so far, with one exception, before I re-hid the Magisk app, zygisk did not show as active.
I had similar behaviour w/ TJW build; I didn't hide, just force closed app and opened it again and it detected Zygisk... I think there are issues with new in ap Zygisk detection across builds.

Also, after you install the Magisk apk and open it, you now get the update box showing that a Magisk update is available. That is strange, since I can find no evidence of new updates on vvb2060's github page, so where is his alpha channel hosted?
I think Alpha recently only ever showed last GitHub hosted Alpha (b6298f86-alpha here: https://github.com/vvb2060/magisk_files/tree/9f13418f7ce6a47305801ba02433f61d76fd28a4 ) as 'Latest'; It never showed 'Update'...

Is your Update Channel set to Alpha?... May be set to Canary or other...

Also, do App Installed and Magisk Installed versions match? PW
 
Last edited:

LSS4181

Senior Member
Mar 13, 2012
442
148
Google Pixel C
Razer Phone 2
So there's no point updating magisk today if it's just gonna break things and it's already working as is right ?
If MagiskHide is already working for you, don't update to the latest canary. MagiskHide is no more with this version, and Zygisk is still experimental and not compatible with Riru.

I have a few apps that give me a slightly annoying warning if I'm rooted, but do not stop me from using them. Before updating, hiding root with MagiskHide works, that they did not show me the warning, but after updating to latest canary, they do, even after adding them to Zygisk+DenyList. I also tried Riru MomoHider and Riru Unshare but no avail (Momo can see everything), either they need real MagiskHide (which is no more), or I didn't configure them properly, since I only started using Riru very recently (for LSPosed).

Should say that these apps' root detection has nothing to do with SafetyNet, as I'm using microG (with NanoDroid) on which SafetyNet does not work correctly, and I don't need it to pass. SafetyNet is not equal to root detection.

It's not really an issue as I'm not really being prevented from using any apps at the moment, just some minor annoyances. I know it's kind of a transitional period at present, and I'm looking forward to whatever new approaches that aim to achieve what MagiskHide was able to do, and improve it.

EDIT: It seems the most recent Magisk Alpha at the time of writing re-added MagiskHide as a mutually exclusive option to Zygisk, and that works just like before. Don't know how things would work in the future, though.
 
Last edited:
  • Like
Reactions: prot-

martyfender

Senior Member
Mar 9, 2017
3,174
1,694
Indianapolis, IN
I think Alpha recently only ever showed last GitHub hosted Alpha (b6298f86-alpha here: https://github.com/vvb2060/magisk_files/tree/9f13418f7ce6a47305801ba02433f61d76fd28a4 ) as 'Latest'; It never showed 'Update'...

Is your Update Channel set to Alpha?... May be set to Canary or other... PW
It is set to the alpha and now I am on alpha 43d11d87 (23010). After updating the apk to alpha 43d11d87 and launching it, the blue update button for the first time in a while, showed up on the upper right, as normal, as in the past, when an update is available.
 
Last edited:

pndwal

Senior Member
It is set to the alpha and now I am on alpha 43d11d87 and shows the latest as N/A. After updating the apk to alpha 43d11d87 and launching it, the blue update button for the first time in a while showed up on the upper right as normal in the past.
So you seem to have a network issue if N/A shows rather than b6298f86-alpha w/ Alpha channel set IIANM.

Do you still have blue update button for Magisk? Do you have 43d11d87-alpha for both Installed App and Installed Magisk? Screenshot? PW
 

martyfender

Senior Member
Mar 9, 2017
3,174
1,694
Indianapolis, IN
So you seem to have a network issue if N/A shows rather than b6298f86-alpha w/ Alpha channel set IIANM.

Do you still have blue update button for Magisk? Do you have 43d11d87-alpha for both Installed App and Installed Magisk? Screenshot? PW
My mistake, I did not get N/A with the alpha channel setting, I had looked at the channel settings and changed it to custom channel and forgot to change it back to alpha. (I was just looking at the channel settings as you suggested.)
This was after I had installed the second alpha of today, 43d11d87. And yes it shows 43d11d87 in both the app and Magisk area. And to clarify, if you are not on the latest, 2 alphas were released today: 7496d515 and 43d11d87. The blue update button was gone, as normal, after updating Magisk itself to 43d11d87.
 
Last edited:

zgfg

Senior Member
Oct 10, 2016
6,054
3,552
My mistake, I did not get N/A with the alpha channel setting, I had looked at the channel settings and changed it to custom channel and forgot to change it back to alpha. (I was just looking at the channel settings as you suggested.)
This was after I had installed the second alpha of today, 43d11d87. And yes it shows 43d11d87 in both the app and Magisk area. And to clarify, if you are not on the latest, 2 alphas were released today: 7496d515 and 43d11d87. The blue update button was gone, as normal, after updating Magisk itself to 43d11d87.
Is there anything essentially new/different in today's latest 43d11d87?

Asking because there are some strange comments on TG about the come back of MagiskHide, but you can never be sure with translating
 

Top Liked Posts

  • 1
    I think you can still use patched AP method (but with canary release), vbmeta gets patched during this process as well, it's nothing to get confused about. I never used patched AP method tho, rooting with custom recovery is much easier/faster imo. And I feel more confident with TWRP instead of stock recovery.
    Here you have the guide:
    Thread '[RECOVERY][UNOFFICIAL] TWRP for Galaxy S21 Ultra (Exynos)' https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-s21-ultra-exynos.4240993/

    Cheers
    Thanks for the help, really appreciated.
    It works, got BUKG rooted (≧▽≦)
    1
    Does the latest magisk canary for Android 12 prevent deep sleep (since debug seems to be on)?
    No
  • 14
    For those who use Alpha or new Canary and miss the old Modules Repo:

    Download and install their root app that will act like the old Modules tab with the integrated connection to the Repo

    Actually, two Repositories - the old 'official' one plus the alternative new Repo (the old/original TJW's Repo is closed for submission of any new modules - only the modules that were admitted previously could still be updated to the old 'official' Repo)
    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:
    12
    Is there any good reason to update to a canary or alpha build if stable 23.0 does everything you want from it - apart from curiosity to where Magisk is heading with zygisk?
    I'm surprised seeing so many people installing unstable builds and running into problems.
    There are way too many people that update just for the sake of updating...
    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
  • 1069
    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