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

Magisk General Support / Discussion

Search This thread

zgfg

Senior Member
Oct 10, 2016
6,402
3,819
Just tried Fresh too, same result as you.

In case there's any confusion, to be even clearer:

Lesson for all on Android 11+:

*** There will SOON be NO real point using 'Hide the Magisk app' function post Android 10 !!! ***

This is because all apps / updates hosted on playstore from Nov 2021 will be prohibited from acquiring app list to detect installed apps anyway!

Apps older than this are NOT required to comply with Android 11 rules (API Level 30), so may still acquire app list / detect Magisk app. However no updates may be hosted on Playstore without complying, so such apps (banking etc) will clearly become obsolete / be abandoned in a short time anyway.

- These changes are summarised well by Momo home-screen comments (vvb2060, Rikka).

😁 PW
If one still needs to hide the Magisk app, then instead of taking Hide Magisk app option in Magisk app settings page (again, not to be confused with Magisk Hide), the following works:
Riru and Riru-LSPosed (Magisk modules)
+
Hide My Applist (LSPosed module)

Screenshot below shows how RootBeer Fresh (old target API 28 that otherwise finds the Magisk apk) cannot detect Magisk apk anymore.
Ofc, I have also DenyList enabled for RBF, to prevent detecting the Magisk itself

I use that MHA module now also for 'dettaching' four apps from Google Play (same thing, MHA hides them from Google Play) to prevent updating them automatically or by mistake (e.g. one of them is YouTube because of Vanced root that requires me to stay on a particular YT version from July or so)

Unlike with some other methods, it's easy to stop hiding/dettaching - just disable hiding in the MHA module
 

Attachments

  • Screenshot_2021-10-23-16-34-54-503_com.kimchangyoun.rootbeerFresh.sample.jpg
    Screenshot_2021-10-23-16-34-54-503_com.kimchangyoun.rootbeerFresh.sample.jpg
    488.7 KB · Views: 58

pndwal

Senior Member
If one still needs to hide the Magisk app, then instead of taking Hide Magisk app option in Magisk app settings page (again, not to be confused with Magisk Hide), the following works:
Riru and Riru-LSPosed (Magisk modules)
+
Hide My Applist (LSPosed module)

Screenshot below shows how RootBeer Fresh (old target API 28 that otherwise finds the Magisk apk) cannot detect Magisk apk anymore.
Ofc, I have also DenyList enabled for RBF, to prevent detecting the Magisk itself

I use that MHA module now also for 'dettaching' four apps from Google Play (same thing, MHA hides them from Google Play) to prevent updating them automatically or by mistake (e.g. one of them is YouTube because of Vanced root that requires me to stay on a particular YT version from July or so)

Unlike with some other methods, it's easy to stop hiding/dettaching - just disable hiding in the MHA module
Yup I added that a few days ago (only have that and CustoMIUIzer) but didn't play much yet... Looks to have several uses. - Seems hiding Magisk app will soon be irrelevant however... PW
 

jnshk

Member
Jan 20, 2014
23
5
I'm not sure if this is the correct place to ask, but I've got Magisk 23.0 installed on an Android head unit (Rockchip PX6 - MTCE) with Android 10. I'm trying to convert a couple of apps to system apps using the "terminal systemizer" module and I've discovered that Magisk does not seem to be mounting the systemizer or busybox modules to the xbin path.

When I enter the ls command in terminal, it lists all of the standard functions, but does not list any of the functions that should have been added as a part of Magisk modules.

Can anyone point me in the direction for a fix or workaround to this issue?
 

zgfg

Senior Member
Oct 10, 2016
6,402
3,819
I'm not sure if this is the correct place to ask, but I've got Magisk 23.0 installed on an Android head unit (Rockchip PX6 - MTCE) with Android 10. I'm trying to convert a couple of apps to system apps using the "terminal systemizer" module and I've discovered that Magisk does not seem to be mounting the systemizer or busybox modules to the xbin path.

When I enter the ls command in terminal, it lists all of the standard functions, but does not list any of the functions that should have been added as a part of Magisk modules.

Can anyone point me in the direction for a fix or workaround to this issue?
With A11, read only SAR (System As Root) is introduced and you can no more write directly to hosts file or restore system apps from Titanium backups, move apps to system, etc

Depending on the manufacturers/models/firmware versions it can start with A10 or even A9 (Huawei EMUI 9)

You can inspect how much 'free space' you have on the system partitions (if they are made read-only they don't need free space) by su -c df command in Terminal app (you will need to grant the root)

Check also (textual file, only READ, do not make changes) /vendor/etc/fstab.*** file for definitions of /system and/or / (root filesystem).
If ro= read only, you can not write/delete/add/change over the system.
This is not 'incomplete root' or some deficiency in Magisk but the way how filesystems are defined by vendors when they release firmwares

This is not new. People should have already be aware of read-only SAR systems, and forget the old-school apps like Titanium, etc

You should be using systemless hosts and systemless modules (all newer modules should be systemless)

If needed, search in this thread, in Magisk documentation on Github, on Internet what the term "systemless" means and how it works

Generally, modules write their changes to /data/adb/modules/***/system... and Magisk takes care to mount those changes to the /system when booting (initializing Magisk)

E g.,for BusyBox use the module BB Android NDK and uninstall all the old BB root apps you have experimented with
 
  • Like
Reactions: J.Michael

vandyman

Senior Member
Jul 30, 2012
699
326
S.Jersey
Google Pixel 5
Google Pixel 6
I'm not sure if this is the correct place to ask, but I've got Magisk 23.0 installed on an Android head unit (Rockchip PX6 - MTCE) with Android 10. I'm trying to convert a couple of apps to system apps using the "terminal systemizer" module and I've discovered that Magisk does not seem to be mounting the systemizer or busybox modules to the xbin path.

When I enter the ls command in terminal, it lists all of the standard functions, but does not list any of the functions that should have been added as a part of Magisk modules.

Can anyone point me in the direction for a fix or workaround to this issue?
Try installing BusyBox into "systems/bin"

For some odd reason I have not been able to install BusyBox pro into xbin for a long time.
 

jnshk

Member
Jan 20, 2014
23
5
With A11, read only SAR (System As Root) is introduced and you can no more write directly to hosts file or restore system apps from Titanium backups, move apps to system, etc

Depending on the manufacturers/models/firmware versions it can start with A10 or even A9 (Huawei EMUI 9)

You can inspect how much 'free space' you have on the system partitions (if they are made read-only they don't need free space) by su -c df command in Terminal app (you will need to grant the root)

Check also (textual file, only READ, do not make changes) /vendor/etc/fstab.*** file for definitions of /system and/or / (root filesystem).
If ro= read only, you can not write/delete/add/change over the system.
This is not 'incomplete root' or some deficiency in Magisk but the way how filesystems are defined by vendors when they release firmwares

This is not new. People should have already be aware of read-only SAR systems, and forget the old-school apps like Titanium, etc

You should be using systemless hosts and systemless modules (all newer modules should be systemless)

If needed, search in this thread, in Magisk documentation on Github, on Internet what the term "systemless" means and how it works

Generally, modules write their changes to /data/adb/modules/***/system... and Magisk takes care to mount those changes to the /system when booting (initializing Magisk)

E g.,for BusyBox use the module BB Android NDK and uninstall all the old BB root apps you have experimented with

Thank you for the detailed response. I will check up on the 'read only' status of my system, as that may be the case for my device's software/firmware.

In this case, I've not bothered with a standalone BusyBox--I simply installed the BusyBox NDK module within Magisk, as well as the terminal systemizer module--and I am not using Titanium Backup. This all came about as I was trying to convert Tasker to a system app in order to give it more capability in order to perform a few automated tasks that I'd like to enable. Although I don't yet quite understand the implications of systemless, I was under the impression that as the system booted up, Magisk would load these modules and merge/mount them into the system so that they would be accessible once
everything was up and running? However, the contents of "busybox-ndk/system/xbin/" and "terminal_systemizer/system/xbin/" do not seem to get merged with the system and are not found/recognized by the shell--which is why I thought that perhaps something is wrong?

So is the ability to convert a third-party app to a system app essentially disabled with modern Android implementations? If the system configuration is locked and read only, in this case, how are system apps able to be updated? I will do some further reading on systemless in regards to Android to see if I can understand it better.
 
  • Like
Reactions: J.Michael

zgfg

Senior Member
Oct 10, 2016
6,402
3,819
Thank you for the detailed response. I will check up on the 'read only' status of my system, as that may be the case for my device's software/firmware.

In this case, I've not bothered with a standalone BusyBox--I simply installed the BusyBox NDK module within Magisk, as well as the terminal systemizer module--and I am not using Titanium Backup. This all came about as I was trying to convert Tasker to a system app in order to give it more capability in order to perform a few automated tasks that I'd like to enable. Although I don't yet quite understand the implications of systemless, I was under the impression that as the system booted up, Magisk would load these modules and merge/mount them into the system so that they would be accessible once
everything was up and running? However, the contents of "busybox-ndk/system/xbin/" and "terminal_systemizer/system/xbin/" do not seem to get merged with the system and are not found/recognized by the shell--which is why I thought that perhaps something is wrong?

So is the ability to convert a third-party app to a system app essentially disabled with modern Android implementations? If the system configuration is locked and read only, in this case, how are system apps able to be updated? I will do some further reading on systemless in regards to Android to see if I can understand it better.
Check with some BB checker - as on the screenshot

My BB applets are installed to:
/data/adb/modules/busybox-ndk/system/xbin

and Magisk mounts them to /system/xbin
 

Attachments

  • Screenshot_2021-10-23-23-44-17-170_com.andreacioccarelli.rootchecker.jpg
    Screenshot_2021-10-23-23-44-17-170_com.andreacioccarelli.rootchecker.jpg
    363.6 KB · Views: 40
  • Like
Reactions: J.Michael

jnshk

Member
Jan 20, 2014
23
5
Try installing BusyBox into "systems/bin"

For some odd reason I have not been able to install BusyBox pro into xbin for a long time.

I tried changing the directory name inside the module from xbin to bin and it did not seem to make any difference. As before, the files did not get mounted to system/bin just as they had not been getting mounted to system/xbin.

Check with some BB checker - as on the screenshot

My BB applets are installed to:
/data/adb/modules/busybox-ndk/system/xbin

and Magisk mounts them to /system/xbin

My modules are also installed at /data/adb/modules/#module-name#/system/xbin, however Magisk does not seem to be mounting them to system/xbin. I checked status with a root+bb checker and it reports the device has root but not busybox.
 

Attachments

  • 20211023_170553.jpg
    20211023_170553.jpg
    205.6 KB · Views: 49

pndwal

Senior Member
Latest vvb2060 Alpha Magisk build

*** For Mavericks only! ***

Chinese Translated:

Magisk Alpha update log

7496d515-alpha

• [General] Based on 7496d515, the content that has been merged into the upstream is no longer listed
• [App] Correctly handle any data from magiskd
• [App] Support SharedUserld
• [App] Delete the backup file after restoring the boot mirror image
• [App] Built-in current version update log
• [App] Use the local version when you can't download the stub, now it can be used completely offline
• [App] Switch to Java 8 modern time APl
• [General] Add an obsolete cgroup v2 path
• [MagiskSU] If necessary, fall back to /dewpts
• [Busybox] Cancel optimization based on undefined behavior
• [General] No longer automatically unlock the device block
• [Magisklnit] Do not intervene when booting to DSU
• [General] Fix the flicker problem when the Windows subsystem for Android is running

How to install?

Install and load Magisk through the Magisk application. Generally, it should be done directly in the application. For special circumstances such as the first installation, the image should be patched and then flashed in with the fastboot/odin tool. Custom Recovery is not a supported method.

Update Journal
From 23.0 to 7496d515

• [General] Support pure 64-bit devices
• [General] Support Android 12 emulator
• [Zygisk] Code injection framework
• [General] Remove MagiskHide
• [General] Support Simulator to add modules
• [MagiskBoot] Support zlImage format
• [MagiskBoot] Add zopfhi encoder
• [Magisklnit] Support bootconfig
• [App] The repair installation function will now check if the script under /data/adb/magisk/ has been updated or not
• [Magiskini] Support some Meizu devices
• [MagiskSU] If the kernel supports it, use isolated devpts
• [MagiskSU] Fix the pts configuration code, now no additional sepolicy rules are needed
• [MagiskBoot] Support v4 boot image header format
• [Magiskinit] Supports oplus.fstab for some OnePlus and Oplus devices.
• [App] Updated modules to be restarted, not marked as pending deletion.
• [App] Deleted online repository library
• [App] Add mounting information to the saved log file
• [App] Suitable for Android 12 API level
• [App] Display the waiting pop-up window that is running when hide/restore the original app
• [Stub] Open source obfuscation function
• [Script] Check and display the sepolicy rule folder of the module.
• [App] When the window pops up, hide the screen and add layers. Android 12+ is required.
• [App] Delete the floating bottom bar and change it to a general bottom operation bar. • [General] Support compilation and cache
• [General] Add rejection list function
• [App] Delete DoH
• [App] Delete SafetyNet
• [App] Allow the log page to be opened when Magisk is not installed
• [App] Display Zygisk status, add a reminder to restart to take effect
• [Zygisk] Disable conflicting riru module
• [Sepolicy] Fix Android 8 terminal cannot get root
• [Sepolicy] Add execmem to allow hook in zygote and system_server
• [Resetprop] Erase the old content completely when editing/deleting
• [Zygisk] Public module API

👍 PW
 
Last edited:

zgfg

Senior Member
Oct 10, 2016
6,402
3,819
New Alpha Changelog
WIP

alpha update log

Magisk (7496d515-alpha)

• [General] Based on 7496d515, the content that has been merged into the upstream is no longer listed
• [App] Correctly handle any data from magiskd
• [App] Support SharedUserld
• [App] Delete the backup file after restoring the boot mirror image
• [App] Built-in current version update log
• [App] Use the local version when you can't download the stub, now it can be used completely offline
• [App] Switch to Java 8 modern time APl
• [General] Add an obsolete cgroup v2 path
• [MagiskSU] If necessary, fall back to /dewpts
• [Busybox] Cancel optimization based on undefined behavior
• [General] No longer automatically unlock the device block
• [Magisklnit] Do not intervene when booting to DSU
• [General] Fix the flicker problem when the Windows subsystem for Android is running

How to install?

Install and load Magisk through the Magisk application. Generally, it should be done directly in the application. For special circumstances such as the first installation, the image should be patched and then flashed in with the fastboot/odin tool. Custom Recovery is not a supported method.

Update Journal
From 23.0 to 7496d515

• [General] Support pure 64-bit devices
• [General] Support Android 12 emulator
• [Zygisk] Code injection framework
• [General] Remove MagiskHide
• [General] Support Simulator to add modules
• [MagiskBoot] Support zlImage format
• [MagiskBoot] Add zopfhi encoder
• [Magisklnit] Support bootconfig
• [App] The repair installation function will now check if the script under /data/adb/magisk/ has been updated or not
• [Magiskini] Support some Meizu devices
• [MagiskSU] If the kernel supports it, use isolated devpts
• [MagiskSU] Fix the pts configuration code, now no additional sepolicy rules are needed
• [MagiskBoot] Support v4 boot image header format
• [Magiskinit] Supports oplus.fstab for some OnePlus and Oplus devices. [App] Update modules to be restarted, not allowed to be marked as pending deletion. [App] Deleted online warehouse

[App] Add mounting information to the saved log file

[App] Suitable for Android 12 API level

[App] Display the waiting pop-up window that is running when hide/restore the original app [Stub] Open source obfuscation function

[Script] Check and display the sepolicy rule folder of the module. [App] When the window pops up, hide the screen and add layers. Android 12+ is required. [App] Delete the floating bottom bar and change it to a general bottom operation bar. [General] Support compilation and cache

[General] Add rejection list function

[App] Delete DoH

[App] Delete SafetyNet

[App] Allow the log page to be opened when Magisk is not installed

[App] Display Zygisk status, add a reminder to restart to take effect

[Zygisk] Disable conflicting riru module

[Sepolicy] Fix Android 8 terminal cannot get root [Sepolicy] Add execmem to allow hook in zygote and system_server

[Resetprop] Erase the old content completely when editing/deleting

[Zygisk] Public module API
Did you try maybe?
There are pretty bad reports on TG...
 
  • Like
Reactions: 73sydney

J.Michael

Recognized Contributor
Jan 20, 2018
972
894
Samsung Galaxy Tab A series
I tried changing the directory name inside the module from xbin to bin and it did not seem to make any difference. As before, the files did not get mounted to system/bin just as they had not been getting mounted to system/xbin.



My modules are also installed at /data/adb/modules/#module-name#/system/xbin, however Magisk does not seem to be mounting them to system/xbin. I checked status with a root+bb checker and it reports the device has root but not busybox.
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"?
 
  • Like
Reactions: ipdev

pndwal

Senior Member
Did you try maybe?
There are pretty bad reports on TG...
Not yet! ... Having my dinner. 🍔🍟😛

Thanks for warning!... Other mavericks can try and report first...

Nb. Last build was a quick fix for prior (same day) broken release... Bound to happen I guess, they are test builds after all... PW
 
Last edited:
  • Like
Reactions: 73sydney

73sydney

Senior Member
Jul 21, 2018
2,001
1,802
Sydney
Google Pixel 2 XL
Samsung Galaxy S20
Not yet! ... Having my dinner. 🍔🍟😛

Thanks for warning!... Other mavericks can try and report first...

Nb. Last build was a quick fix for prior (same day) broken release... Bound to happen I guess, they are test builds after all... PW

Pretty lazy of you to release tease and run to dinner without testing :p

I think you know i wont be the maverick on this one :)

Interesting to read about the change to app listing earlier
 

zputnyq

Senior Member
Apr 19, 2013
608
277
New canary (23010) from TJW has been released today.
I'm not really following development.
Does anyone know about the apps listed on denylist whether it is contained system apps or not ?
 
  • Like
Reactions: pndwal

pndwal

Senior Member
Pretty lazy of you to release tease and run to dinner without testing :p

I think you know i wont be the maverick on this one :)

Interesting to read about the change to app listing earlier
Haha... Actually I've often done that... Not teasing, just trying to get an Engrish translation up early as a public service for mavericks... and none of them need my endorsement, nor is it implied in any way...

Alpha use is on your own collective heads! ... Don't shoot the messenger!... Man up and own it!...

But if you don't, you're a wimp with no sense of adventure!

... a tease 🙄...

And what are YOU, a man or a mouse? 😁 PW
 
  • Like
Reactions: 73sydney

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,299
1
14,663
Gothenburg
Google Nexus 4
Nexus 6
New canary (23010) from TJW has been released today.
I'm not really following development.
Does anyone know about the apps listed on denylist whether it is contained system apps or not ?
It does contain system apps. I just updated to the 23010 Canary, enabled zygisk and the Deny list. Added Play Service's gms and unstable (gms is necessary depending on your Android version) parts to the list and voilà: SafetyNet still passes.

I'm also using my MHPC module to set all the bootloader props, etc, that was removed from Magisk with this update. If you're using the Universal SafetyNet Fix that's included in that module already.
 

zputnyq

Senior Member
Apr 19, 2013
608
277
It does contain system apps. I just updated to the 23010 Canary, enabled zygisk and the Deny list. Added Play Service's gms and unstable (gms is necessary depending on your Android version) parts to the list and voilà: SafetyNet still passes.

I'm also using my MHPC module to set all the bootloader props, etc, that was removed from Magisk with this update. If you're using the Universal SafetyNet Fix that's included in that module already.
Thanks I really appreciate it.
On my device running stock android 6.0.1 none of its system apps listed there. I tapped the arrow button on the upper right but stiil none of the system apps listed. Is it intended on device running stock android 6.0.1 ?
 
  • Like
Reactions: pndwal

pndwal

Senior Member
New canary (23010) from TJW has been released today.
I'm not really following development.
Does anyone know about the apps listed on denylist whether it is contained system apps or not ?
That's the wake-up call we all need! Glad I already ate. 😃
John Wu, 1h

The first canary release for 6 months!

Zygisk documentation and an example module will be uploaded soon

🎉🎊👍 PW
 

Top Liked Posts

  • 3
    Now that there is a new Magisk V24 stable thread.
    Will it be it be ruined like this thread?

    I really hope not. Who can post the most in the new thread does not count like it does here in this thread.
    Sorry for the off topic rant and being an a*s.
    Nb. It's a 24.0+ thread, but we haven't yet got stable! 😉

    Preventing a new thread from expanding fast has been my concern too, and @ipdev and I have discussed this over the last few weeks (he may have done so with others also).

    I can't / couldn't see an easy solution to this for a discussion / help thread... We did discuss a wiki style site / thread to supplement @Didgeridoohan's excellent database of solutions to cover use of new hiding modules and other more loosely magisk related topics / issues... This is what we've got - Ipdev stepped up to maintain it and I salute him for his efforts!

    Nb. It will likely help a lot if users read the first 5 posts before asking questions though... The intention is to keep these updated to cover the most commonly needed information...

    I don't think that this thread ruined however. It may be burgeoning, but it is / has always been a very valuable resource as a General Discussion thread, especially for those knowing what to search for / how to search... And as long as some who keep up with recent development are happy to help others, it seems to work well for all AFAICS... 😜 PW
    3
    With @topjohnwu as OP, this thread relies on moderators to do housekeeping as John is no longer active here... PW
    Exactly. People of this thread should report posts, if they deem it necessary and we'll take care of it, as usual.

    General info:
    No need to make a post about someone else's post being offtopic etc..
    2
    No, you're right. What might help is when some of the most helpful contributers like @pndwal and @zgfg and others could have rights to simply delete posts.

    I mean, what does a post like:

    add in the middle of a discussion about hiding Magisk? 🙄
    Or would it be better to just report such posts, or (dis)like them with a sad 🙁 or angry 😡 face?
    That will be one advantage of the new @ipdev 24.0+ thread; as an active OP he can delete posts / do housekeeping.

    With @topjohnwu as OP, this thread relies on moderators to do housekeeping as John is no longer active here... PW
  • 15
    Show will begin, I tried to put some short help for probably the posts/questions soon to expect

    ===

    Please carefully read Changelog

    Study the Magisk documentation available from the official Magisk Github page - particularly about installing Magisk (if you are not familiar with patching the image in Magisk app and flashing the patched img from Fastboot- i.e, not the old school about Magisk zip through TWRP)

    Everything bellow has already been discussed in this thread since Canary 2301x started to roll out - hence more details can be found in the older posts in this thread

    a) No more MagiskHide. New technology instead (for the same - to help hiding root): Zygisk+DenyList

    b) No more built in SafetyNet checker. Install from PlayStore e g: YASNAC

    c) Modules window does no more connect to the (now frozen) old Modules repository.
    You must download module zip files manually and "Install from local storage".
    Or search for and install Fox Magisk Module Manager (Fox Mmm) app - it will connect to the new, alternative repository

    ---

    1) Make sure that both Magisk app and Magisk are installed and updated to the new version. Inspect version numbers on the main Magisk window/page

    2) Make sure to uninstall all Riru modules (not compatible with Zygisk)

    3) Settings, Enable Zygisk and reboot.
    Then check on the main window does it show Zygisk Yes

    4) Settings, enable Enforce DenyList.
    Configure DenyList, enable filters to Show OS and System apps
    Find Google Play Services and check-in only the two processes ending with gms and gms.unstable.
    You will have to check in all your banking apps and so as you used with MagiskHide.
    Always reboot upon reconfiguring DenyList

    5) If SafetyNet does not pass, install USNF 2.2.1 and test again.
    Always reboot upon installing a module, also if/when you enable Systemless Hosts

    ---

    Intentionally, I didn't want to complicate with Shamiko for the new Magisk 24 users 👍

    PS: See the new thread:
    11
    Can you confirm that all apps checked in the deny list are hidden to the system, pleeeaaase ???
    Few things to note: You really need to read release notes before using any Magisk build, official or otherwise. 🙃

    The build @Johnson_Ran posted is his own build of latest unofficial Alpha Magisk + LoveSys fix for OnePlus 7 / 7 Pro (and possibly other devices) w/ ramdisk detection issue; I posted re. a test build based on canary, now he posted his personal Alpha Magisk with fix for OnePlus... Nb. The fix has NOT been merged in Magisk master, Canary or even latest vvb2060 Alpha yet.

    Well this concept of deny list is confusing so I tried to treat it as a MagiskHide list and all apps I checked are not working as they did with v23... ^^
    Do you mean Are root-related execution environment changes hidden from the app? If so, that depends...

    MagiskHide is dead and gone in TJW builds going forward; denylist is quite different - it 'reverts Magisk features in use for selected processes', ie w/ denylist "Magisk denies further modifications and reverts all changes it had done. Magisk will not spoof/alter/manipulate any non-Magisk related signals or traces to circumvent any device state detection." So denylist is actually made more powerful for hiding TEE mods because of Zygisk, but won't perform the spoofing / alterations / manipulations of non-Magisk related signals or traces formerly done by MagiskHide.

    Even more powerful hiding methods are now available however, thanks to John's strengthened Magisk framework; he just won't do it himself:
    www.twitter.com/topjohnwu/status/1445598597521633285

    Universal SafetyNet Fix and Shamiko are examples where Zygisk is used for advanced hiding by 3rd party modules. Nb. Denylist is not even needed if Devs choose to "do everything themselves"!
    www.twitter.com/topjohnwu/status/1445598601372069890

    As I indicated, the biggest favour users can do themselves is read release notes before using any Magisk build, official or otherwise. For TJW Canary start with this one:
    https://github.com/topjohnwu/magisk-files/blob/9537c5d8cedfc09ca723ae0392b1219e75d9b636/notes.md
    ... read the blog John links there (for good reason) also... and scroll down and read the 2020 one also for more understanding of the general Magisk roadmap / direction...

    ONLY after understanding these major changes, if you want to try HIGHLY EXPERIMENTAL bleeding edge vvb2060 Alpha builds, read IT'S Changelog (translate Chinese)... Latest here:
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86215689

    Coming back to your statement
    I tried to treat it as a MagiskHide list and all apps I checked are not working as they did with v23... ^^
    Note a major difference between TJW denylist and Alpha denylist:
    • [General] Use MagiskHide to hide when Zygisk is closed
    So denylist in Alpha works like MagiskHide / hidelist only after Zygisk is closed; Nb. you NEED TO REBOOT to disable Zygisk.

    After this Riru modules will also work (it's a choice; Riru or Zygisk, not both), and if you needed 2.x series Universal SafetyNet Fix for your device, you'll need to swap to a USNF-Riru build if you had USNF-Zygisk. Note: There is no option to do this in TJW Canary as current USNF-Riru builds require MagiskHide to function.*

    Nb.1. In TJW builds denylist WON'T be used as hidelist or with MagiskHide. Alpha restores MagiskHide... This is peculiar to custom Magisk forks...

    Nb. 2. There are differences with MagiskHide in Alpha. Importantly, toggling MagiskHide off then on again does NOT add Google Play Services safetynet process to denylist (whether in denylist or hybrid alpha hidelist mode). You need to do this manually to pass SafetyNet as follows:

    Add Google Play Services process(es) to denylist unless a solution for hiding root associated modifications from GPS SafetyNet process(es) is incorporated in an active 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.

    Happy reading / playing, and hope this helps! 😀 PW

    Edit:

    *FWIW, this makes Alpha attractive for anyone wanting to use Riru and pass SafetyNet on late devices (w/ TEE Attestation in hardware affected by September Google server end changes) with post 23001 Magisk builds... This may only be useful in the interim until general Zygisk module conversion / take-up and Riru is dropped...

    However if (and only if) Riru does get continued support / remains popular / doesn't die post Magisk 24000 (ie. Zygisk in Stable Magisk), and @kdrag0n reconsiders this:
    https://github.com/kdrag0n/safetynet-fix/issues/120#issuecomment-971831719
    we may see working USNF-Riru for official TJW post Zygisk Magisk...

    I suspect though that predictions of Riru's imminent demise will be realised, so don't hold your breath.

    Thanks for all the fun RikkaW and team; You did it (allowed modules to run code in apps w/ zygote injection / Xhook) first! 👏 PW
    10
    Guess I can advertise @ipdev's new WIP

    [Discussion] Magisk - The Age of Zygisk​

    thread now that public 24.0 release is out:

    First 5 posts have a good summation of new Magisk changes / direction / tips. 👍 PW
    9
    ...snip...
    Just meant nandroid restore should be usable to roll back since you seemed concerned you'd 'lose ability to use nandroid backup' & would need to restore beloved A10 setup / mods piece by piece!...
    ...snip...
    A LOT of config is stored in the settings. For example:
    PHP:
    settings put global "window_animation_scale" "0.5";
    Because I use to build ROMs from source and therefore clean flash my devices a lot, I built a method to extract and reinstate all my config, to be used selectively and in combination with normal back-up apps, to reinstate my device as close to its previous state without manually hunting and seeking all the settings, after a clean flash.

    I automated this task as a method within the app TeMeFI and can be found under Current State>Settings>Generate Set All
    8
    Guys (especially @zgfg and @pndwal), big thumb up 👍🏻 for your patience in explaining everything gazillion times over and over 😂
  • 1072
    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