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

Magisk General Support / Discussion

Search This thread

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,117
14,026
Gothenburg
Google Nexus 4
Nexus 6
Do you want screenshots with English language?
Not necessary... It's quite clear that the last screenshot shows that the Magisk app doesn't recognise that Magisk is installed. So, something's wrong somewhere.

Generally that could mean that the Magisk app is installed to external/adoptable storage (it needs to be installed to the internal storage or stuff like this happens), or you previously had Magisk installed with the Magisk app repackaged with a random name and now the regular app isn't recognised as a trusted root manager, or something else...
 

adehade1983

Member
Sep 27, 2017
8
0
Samsung Galaxy J3 (2016)
Not necessary... It's quite clear that the last screenshot shows that the Magisk app doesn't recognise that Magisk is installed. So, something's wrong somewhere.

Generally that could mean that the Magisk app is installed to external/adoptable storage (it needs to be installed to the internal storage or stuff like this happens), or you previously had Magisk installed with the Magisk app repackaged with a random name and now the regular app isn't recognised as a trusted root manager, or something else...
Previously safetynet not working and I installed magisk again. After second installation was something wrong with boot.img and installation any apk (from twrp. magisk. and system) was stopped. Now after third installation safetynet and root start working after fixing boot.img. But magisk not working correctly. Please help me. How to fix it?
Previously safetynet not working and I installed magisk again. After second installation was something wrong with boot.img and installation any apk (from twrp. magisk. and system) was stopped. Now after third installation safetynet and root start working after fixing boot.img. But magisk not working correctly. Please help me. How to fix it?
 
Last edited by a moderator:

jons99

Senior Member
Nov 5, 2019
213
248
Previously safetynet not working and I installed magisk again. After second installation was something wrong with boot.img and installation any apk (from twrp. magisk. and system) was stopped. Now after third installation safetynet and root start working after fixing boot.img. But magisk not working correctly. Please help me. How to fix it?
you need to patch your boot img
 

pndwal

Senior Member
Previously safetynet not working and I installed magisk again. After second installation was something wrong with boot.img and installation any apk (from twrp. magisk. and system) was stopped. Now after third installation safetynet and root start working after fixing boot.img. But magisk not working correctly. Please help me. How to fix it?
Just uninstall Magisk App, then go to phone settings, apps, and check list there for another Magisk App instance, likely with custom name you assigned, or simply named "settings" etc. Uninstall this also. (Superuser and hidelist settings / modules are not stored in app data and will remain.) Reinstall current APK version... PW
 
Last edited:
  • Like
Reactions: J.Michael

hfam

Senior Member
Aug 13, 2010
107
89
@Didgeridoohan, @pndwal, and all the rest, THANKS for all the help!!

It was as straightforward as indicated, and my Pixel 5a 5G is fully rooted on Magisk v23, SafetyNet fully functioning with riru+drag0n SafetyNet fix+MagiskHide. ALL banking apps work perfect, SN check passes, a rooted apps are perfect, I am SOOO happy, it went absolutely perfectly. No WAY I could have (or would have) tackled this cold on my own!

In a P5 thread, @jcmm11 was answering some concerns and I posted that I'd post a step by step over there for any help it may provide for the new 5a 5G users, so I'll come back and update this post with a link to that when it's ready (later tonight, UFC 266 main card is just kicking off, so later tonight for sure).

Cheers and mad respect to all you awesome selfless folks who make the Magisk world spin round, I'm so grateful.
 

eeeemc

Senior Member
Jan 12, 2011
131
13
My Samsung A71 BANKING APPS not allowing me said my device detected rooted.

I have modules in Magisk such as : Magiskhide Props Config/Riru/Riru Enhanced mode for Magisk Hide/Riru LSposed/Systemless Hosts/Universial SafetyNet Fix.

I've properly installed <> restart device <> installed <> restart device.

I've turn Magisk Hide & hide Magisk with new apps new to the hide magisk. I've put BANKING APPS to the hide list.

Check Safety Net shows all PASSED in Blue color.

So I do not understand until which methods I can use in order to avoid BANKING APPS kicks me. ( used to be okay before Aug-2021 that I can use simple Magisk hide and BANKING APPS working without kick me )

Thank you very much., edmond
 

pndwal

Senior Member
New Alpha w/ same TJW commit code (ie. doesn't merge new TJW code) out on Telegram channel.

Seems it includes new vvb2060 commit:

Would appreciate explanation from someone au fait with such commits; I'm not. 👍

I see devpts is a linux virtual filesystem directory used for terminal emulators. Is this a fix for TE? PW
 
Last edited:

zgfg

Senior Member
Oct 10, 2016
5,881
3,346
New Alpha w/ same TJW commit code (ie. doesn't merge new TJW code) out on Telegram channel.

Seems it includes new vvb2060 commit:

Would appreciate explanation from someone au fait with such commits; I'm not. 👍

I see devpts is a linux virtual filesystem directory used for terminal emulators. Is this a fix for TE? PW
I don't know more but AFAIK, it was related to the discussion on TG as on the screenshot
 

Attachments

  • IMG_20210926_081632.jpg
    IMG_20210926_081632.jpg
    419.8 KB · Views: 61

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,117
14,026
Gothenburg
Google Nexus 4
Nexus 6
My Samsung A71 BANKING APPS not allowing me said my device detected rooted.

I have modules in Magisk such as : Magiskhide Props Config/Riru/Riru Enhanced mode for Magisk Hide/Riru LSposed/Systemless Hosts/Universial SafetyNet Fix.

I've properly installed <> restart device <> installed <> restart device.

I've turn Magisk Hide & hide Magisk with new apps new to the hide magisk. I've put BANKING APPS to the hide list.

Check Safety Net shows all PASSED in Blue color.

So I do not understand until which methods I can use in order to avoid BANKING APPS kicks me. ( used to be okay before Aug-2021 that I can use simple Magisk hide and BANKING APPS working without kick me )

Thank you very much., edmond
Try uninstalling the Magisk app. That's a very popular way of detecting Magisk, and even repackaging the app with a random name doesn't fully prevent it.

More:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
 
  • Like
Reactions: J.Michael

pndwal

Senior Member
I don't know more but AFAIK, it was related to the discussion on TG as on the screenshot
Yup, that's what tipped me to latest Alpha having merged commits from new https://github.com/vvb2060/Magisk/commits/pts branch.

It's hard to follow now that actual build release commits no longer appear in his Magisk repo.

I just wondered what that commit did, but it seems to be related to his other one there (already merged by TJW): Fix terminal on android 8 …
"No need to handle untrusted_app_all_devpts on modern devices, but devpts policy is different for older devices."
https://github.com/topjohnwu/Magisk/commits/master PW
 

pndwal

Senior Member
My Samsung A71 BANKING APPS not allowing me said my device detected rooted.

I have modules in Magisk such as : Magiskhide Props Config/Riru/Riru Enhanced mode for Magisk Hide/Riru LSposed/Systemless Hosts/Universial SafetyNet Fix.

I've properly installed <> restart device <> installed <> restart device.

I've turn Magisk Hide & hide Magisk with new apps new to the hide magisk. I've put BANKING APPS to the hide list.

Check Safety Net shows all PASSED in Blue color.

So I do not understand until which methods I can use in order to avoid BANKING APPS kicks me. ( used to be okay before Aug-2021 that I can use simple Magisk hide and BANKING APPS working without kick me )

Thank you very much., edmond
And just in case you haven't cleared bank apps data, you need to do this after every failure / new countermeasure (eg added app to hidelist) is introduced.

... Also, you could give Riru-MomoHider a crack (replace Riru-Unshare):
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85125319 PW
 
  • Like
Reactions: J.Michael

pndwal

Senior Member
Latest Alpha Magisk cb4361b7-alpha

*** For Mavericks only! ***

Riru / Zygisk coexistence seems to be back!
🎉🎊⚡🥝🧀

Chinese Translated:
alpha update log
Magisk (cb4361b7-alpha)


● [General] Based on cb4361 b7, the content that has been merged upstream is no longer listed
● [App] Correctly process any data from magiskd
● [App] Support SharedUserld
● [App] Delete the backup file after restoring the boot image
● [App] Built-in current version update log
● [App] Use the local version when the stub cannot be downloaded, now it can be used completely offline
● [App] Switch to the modern time API of Java 8
● [DenyList] handle suspicious props
● [App] Update SafetyNet extension, update snet.jar version to 18
● [General] Add an obsolete cgroup v2 path
● [Sepolicy] Add execmem to allow zygote and system_server Hook
● [MagiskSU] If necessary, fall back to /dev/pts
● [Zygisk] Fix Circumstances that may not take effect
● [Busybox] Cancel optimization based on undefined behavior
● [General] No longer automatically unlock the device block
● [Zygisk] From the current situation, there is no crash report to prove zygisk and riru
Incompatible, temporarily cancel the restriction, observe the situation

Upstream update log
From 23.0 to cb4361b7


● [General] supports pure 64-bit devices
● [General] Support Android 12 emulator
● [Zygisk] Code Injection Framework
● [General] Remove MagiskHide
● [General] Support special simulator loading module
● [MagiskBoot] Support zImage format
● [MagiskBoot] Add zopfli encoder
● [Magisklnit] Support bootconfig
● [App] Repair installation function will now check the script under /data/adb/magisk/ is not updated
● [MagiskInit] Support some Meizu devices
● [MagiskSU] If the kernel supports it, use isolated devpts
● [MagiskSU] Fix the pts configuration code, now no extra sepolicy rules
●[MagiskBoot] Support v4 boot image header format
● [MagiskInit] Support opltus.fstab for some OnePlus and Opal devices
● [App] Update modules to be restarted, not allowed to be marked as pending deletion
● [App] Delete online warehouse
● [App] Add mounting information to the saved log file
● [App] Adapt to Android 12 API level
● [App] Display the waiting pop-up window when the app is hidden/restored
● [Stub] Open source obfuscation function
● [Script] Check and display the sepolicy rule folder of the module
● [App] Hide screen overlay for pop-up window, Android 12+ is required
● [App] Delete the floating bottom bar and change it to the general bottom operation bar
● [General] Support special compilation 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 restart reminder
● [Zygisk] Correctly handle child zygote
● [Zygisk] Disable conflicting riru modules
● [Sepolicy] Fix Android 8 terminal cannot get root

👍 PW
 
Last edited:

pndwal

Senior Member
cb4361b7-alpha report:
w/ RN8T, Stock MIUI, Android 10

Two reboots needed initially.

Zygisk & Riru w/ Universal SafetyNet Fix 2.1.1, LSPosed, Un-Share all working fine.

SafetyNet passing w/ SafetyNet Google Play Services process denied.

ViPER4Android FX Neon driver status normal.

With Zygisk enabled Riru-MomoHider causes instability / system crashes even when only app_zygote_magic hiding is configured. 😕

Great progress! 👍 PW
 
Last edited:

zgfg

Senior Member
Oct 10, 2016
5,881
3,346
cb4361b7-alpha report:

RN8T, Stock MIUI, Android 10

Two reboots needed initially.

Zygisk & Riru w/ Universal SafetyNet Fix, LSPosed, Un-Share all working fine.

SafetyNet passing w/ SafetyNet Google Play Services process denied.

ViPER4Android FX Neon driver status normal.

With Zygisk enabled Riru-MomoHider causes instability / system crashes even when only app_zygote_magic hiding is configured. 😕

Great progress! 👍 PW
Webview also ok?

Edit:
Yes, it is, tested myself (see the next post)
 
Last edited:

zgfg

Senior Member
Oct 10, 2016
5,881
3,346
cb4361b7-alpha report:

RN8T, Stock MIUI, Android 10

Two reboots needed initially.

Zygisk & Riru w/ Universal SafetyNet Fix, LSPosed, Un-Share all working fine.

SafetyNet passing w/ SafetyNet Google Play Services process denied.

ViPER4Android FX Neon driver status normal.

With Zygisk enabled Riru-MomoHider causes instability / system crashes even when only app_zygote_magic hiding is configured. 😕

Great progress! 👍 PW
Btw, I needed only one reboot (to system):
-updated apk
-patched the boot.img
-rebooted to TWRP to flash the patched boot img (leaving zygisk and denylist enabled)
-rebooted to system

And everything was ok, incl. the Webview
 
  • Like
Reactions: pndwal and ipdev

hfam

Senior Member
Aug 13, 2010
107
89
Hey all,
As promised, I wrote up a step-by-step tutorial for the Pixel 5a (though it applies to about all the Pixels, much of it I used on my Pixel 2 over the past 4+ years):


I know it's a book, but I wanted to make sure I put it in everyday language and tried to make it so even a first timer could go through it and feel confident moving forward and getting root, passing SafetyNet, and update with system updates in the future with confidence.

Anyhow, it's my attempt to give something back to the community I've gained so much from and leaned on so many times for help. If it helps even one person I'll be happy.

Thanks again to the entire community, and particularly the folks who have been here helping tirelessly and without reserve to get everyone up and going. You all know who you are and I gave proper name attribution in the tutorial thread. I'm exhausted, so I'm gonna go grab some dinner, that took hours to write! hahahahaah!!

Be well everyone, SO happy my P5a is fully functioning, you folks are just amazing.

hfam
 

ipdev

Recognized Contributor
Feb 14, 2016
1,551
1
1,995
Google Nexus 10
Nexus 7 (2013)
cb4361b7-alpha report:
w/ RN8T, Stock MIUI, Android 10

Two reboots needed initially.

Zygisk & Riru w/ Universal SafetyNet Fix 2.1.1, LSPosed, Un-Share all working fine.

SafetyNet passing w/ SafetyNet Google Play Services process denied.

ViPER4Android FX Neon driver status normal.

With Zygisk enabled Riru-MomoHider causes instability / system crashes even when only app_zygote_magic hiding is configured. 😕

Great progress! 👍 PW
Some have been waiting..
Some have been using vvb2060's alpha builds..

I have been sneaking a peak by running personal builds from John's master branch. :sneaky:
Magisk - GitHub - Building and Development - Link

A few days ago (23.Sep.2021), I was surprised when my OnePlus 6T passed SafetyNet. o_O
It has been about three or four weeks since it passed SafetyNet.

Problems I have run into..
Every now and then, something misfires on boot and Magisk is not active (Installed N/A).
Normally a reboot is all that is needed, occasionally I have to re-install magisk.

I ran into an old issue on my 6T (clean install) installing Magisk.
I had to flash a magisk patched image to both the active and inactive boot slot.
Need to test again with another clean install.​

Currently I have a few devices running these (sneak peak) build(s) and passing SafetyNet.

OnePlus 5T
Older device, does not have the hardware for hardware attestation.
  • Stock OnePlus OS 10.0.1 (SDK29)
  • Magisk (snapshot build)
  • MagiskHidePropsConf (Magisk Module)
    • Enable Zygisk
    • Enable DenyList
    • add com.google.android.gms.unstable to the DenyList.
      Magisk is in /sbin so only needed to Deny .unstable
    • Enable the MagiskHide props. option in the MagiskHidePropsConf module.
Reboot in between steps as needed.

OnePlus 6T
  • Stock OnePlus OS 11.0.0 (SDK30)
  • Magisk (snapshot build)
  • Universal SafetyNet Fix (Magisk Module)
    • Enable Zygisk
    • Enable DenyList
    • add com.google.android.gms.unstable to the DenyList.
    • add com.google.android.gms to the DenyList.
Reboot in between steps as needed.

Pixel 3a
Custom rom that passes SafetyNet on it own.
Installing Magisk breaks SafetyNet.

  • ABC Rom 11 (SDK30)
  • Magisk (snapshot build)
    • Enable Zygisk
    • Enable DenyList
    • add com.google.android.gms.unstable to the DenyList.
    • add com.google.android.gms to the DenyList.
Reboot in between steps as needed.

Earlier today, I setup an update channel so I could test a few more things.
  • Install update from online.
  • Repack (Hide/Restore) the Magisk app.
All worked. :)
Note:
I will have to wait until the next commit(s) to see if I can update while the Magisk app is hidden. 🙃

---

So far The next step of growth and development of Magisk is looking great. :)

I am excited and eagerly waiting for the next canary build for proper testing. :D

Cheers all. :cowboy:

PS.
Some screenshots from my 6T. ;)


Edit (5.Oct.2021):
Please see my follow up post.
Post 48,294 - Link
 

Attachments

  • Screenshot_20210923-210802.jpg
    Screenshot_20210923-210802.jpg
    201.2 KB · Views: 108
  • Screenshot_20210926-190910.jpg
    Screenshot_20210926-190910.jpg
    210.5 KB · Views: 88
  • Screenshot_20210926-190917.jpg
    Screenshot_20210926-190917.jpg
    71.2 KB · Views: 85
  • Screenshot_20210926-190924.jpg
    Screenshot_20210926-190924.jpg
    159.8 KB · Views: 83
  • Screenshot_20210926-190937.jpg
    Screenshot_20210926-190937.jpg
    304.8 KB · Views: 85
  • Screenshot_20210926-190950.jpg
    Screenshot_20210926-190950.jpg
    224.5 KB · Views: 87
  • Screenshot_20210926-191018.jpg
    Screenshot_20210926-191018.jpg
    314.9 KB · Views: 92
  • Screenshot_20210926-191026.jpg
    Screenshot_20210926-191026.jpg
    218.3 KB · Views: 83
  • Screenshot_20210926-191040.jpg
    Screenshot_20210926-191040.jpg
    257.5 KB · Views: 95
  • Screenshot_20210926-191102.jpg
    Screenshot_20210926-191102.jpg
    258.6 KB · Views: 104
Last edited:

Top Liked Posts

  • 6
    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
    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.
    5
    Latest TJW debug (Canary) Magisk Changelog:

    Magisk (d7e7df3b) (23010)
    A new chapter for Magisk!

    For those who missed my blog post, please check here https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458

    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 use selected processes
    [MagiskBoot] Support patching 32-bit kernel zImages
    [MagiskBoot] Support boot image header v4
    [MagiskInit] Support /proc/bootconfig for loading boot configurations
    [MagiskInit] Better support for some Meizu devices
    [MagiskInit] Better support for some Oppo/Realme devices
    [MagiskSU] Use isolated devpts if the kernel supports it
    [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 the Magisk app is removed

    https://github.com/topjohnwu/magisk-files/blob/9537c5d8cedfc09ca723ae0392b1219e75d9b636/notes.md

    ...And all the best with it everyone! 🙂 PW
    3
    Thanks I really appreciate it.
    On my device running stock android 6.0.1 none of its system apps listed there
    It doesn't show them by default, you have to enable that option in the search window.
    3
    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 ?
    If like on Alpha (expected to be), you have to enable Show System apps and Show OS apps. Then you must manually enable GMS (it's been described here couple of times for Alpha but you'll figure out when you enable/expand as above)
  • 11
    diareuse has been MIA for a bit. Pinged him a couple times on the GitHub Issues, but no answer. Hopefully he's okay. 😕

    Mmm. Nothing on his Twitter since February... That's concerning.

    Yeah and in a week it'll be 1 full year since his last commit to Magisk too. 😕

    Good news is diareuse just reached out and is indeed alive and well, just working on multiple paying jobs in real life. 🙂
    11
    Latest Alpha Magisk cb4361b7-alpha

    *** For Mavericks only! ***

    Riru / Zygisk coexistence seems to be back!
    🎉🎊⚡🥝🧀

    Chinese Translated:
    alpha update log
    Magisk (cb4361b7-alpha)


    ● [General] Based on cb4361 b7, the content that has been merged upstream is no longer listed
    ● [App] Correctly process any data from magiskd
    ● [App] Support SharedUserld
    ● [App] Delete the backup file after restoring the boot image
    ● [App] Built-in current version update log
    ● [App] Use the local version when the stub cannot be downloaded, now it can be used completely offline
    ● [App] Switch to the modern time API of Java 8
    ● [DenyList] handle suspicious props
    ● [App] Update SafetyNet extension, update snet.jar version to 18
    ● [General] Add an obsolete cgroup v2 path
    ● [Sepolicy] Add execmem to allow zygote and system_server Hook
    ● [MagiskSU] If necessary, fall back to /dev/pts
    ● [Zygisk] Fix Circumstances that may not take effect
    ● [Busybox] Cancel optimization based on undefined behavior
    ● [General] No longer automatically unlock the device block
    ● [Zygisk] From the current situation, there is no crash report to prove zygisk and riru
    Incompatible, temporarily cancel the restriction, observe the situation

    Upstream update log
    From 23.0 to cb4361b7


    ● [General] supports pure 64-bit devices
    ● [General] Support Android 12 emulator
    ● [Zygisk] Code Injection Framework
    ● [General] Remove MagiskHide
    ● [General] Support special simulator loading module
    ● [MagiskBoot] Support zImage format
    ● [MagiskBoot] Add zopfli encoder
    ● [Magisklnit] Support bootconfig
    ● [App] Repair installation function will now check the script under /data/adb/magisk/ is not updated
    ● [MagiskInit] Support some Meizu devices
    ● [MagiskSU] If the kernel supports it, use isolated devpts
    ● [MagiskSU] Fix the pts configuration code, now no extra sepolicy rules
    ●[MagiskBoot] Support v4 boot image header format
    ● [MagiskInit] Support opltus.fstab for some OnePlus and Opal devices
    ● [App] Update modules to be restarted, not allowed to be marked as pending deletion
    ● [App] Delete online warehouse
    ● [App] Add mounting information to the saved log file
    ● [App] Adapt to Android 12 API level
    ● [App] Display the waiting pop-up window when the app is hidden/restored
    ● [Stub] Open source obfuscation function
    ● [Script] Check and display the sepolicy rule folder of the module
    ● [App] Hide screen overlay for pop-up window, Android 12+ is required
    ● [App] Delete the floating bottom bar and change it to the general bottom operation bar
    ● [General] Support special compilation 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 restart reminder
    ● [Zygisk] Correctly handle child zygote
    ● [Zygisk] Disable conflicting riru modules
    ● [Sepolicy] Fix Android 8 terminal cannot get root

    👍 PW
    11
    Hey all,
    As promised, I wrote up a step-by-step tutorial for the Pixel 5a (though it applies to about all the Pixels, much of it I used on my Pixel 2 over the past 4+ years):


    I know it's a book, but I wanted to make sure I put it in everyday language and tried to make it so even a first timer could go through it and feel confident moving forward and getting root, passing SafetyNet, and update with system updates in the future with confidence.

    Anyhow, it's my attempt to give something back to the community I've gained so much from and leaned on so many times for help. If it helps even one person I'll be happy.

    Thanks again to the entire community, and particularly the folks who have been here helping tirelessly and without reserve to get everyone up and going. You all know who you are and I gave proper name attribution in the tutorial thread. I'm exhausted, so I'm gonna go grab some dinner, that took hours to write! hahahahaah!!

    Be well everyone, SO happy my P5a is fully functioning, you folks are just amazing.

    hfam
    10
    cb4361b7-alpha report:
    w/ RN8T, Stock MIUI, Android 10

    Two reboots needed initially.

    Zygisk & Riru w/ Universal SafetyNet Fix 2.1.1, LSPosed, Un-Share all working fine.

    SafetyNet passing w/ SafetyNet Google Play Services process denied.

    ViPER4Android FX Neon driver status normal.

    With Zygisk enabled Riru-MomoHider causes instability / system crashes even when only app_zygote_magic hiding is configured. 😕

    Great progress! 👍 PW
    Some have been waiting..
    Some have been using vvb2060's alpha builds..

    I have been sneaking a peak by running personal builds from John's master branch. :sneaky:
    Magisk - GitHub - Building and Development - Link

    A few days ago (23.Sep.2021), I was surprised when my OnePlus 6T passed SafetyNet. o_O
    It has been about three or four weeks since it passed SafetyNet.

    Problems I have run into..
    Every now and then, something misfires on boot and Magisk is not active (Installed N/A).
    Normally a reboot is all that is needed, occasionally I have to re-install magisk.

    I ran into an old issue on my 6T (clean install) installing Magisk.
    I had to flash a magisk patched image to both the active and inactive boot slot.
    Need to test again with another clean install.​

    Currently I have a few devices running these (sneak peak) build(s) and passing SafetyNet.

    OnePlus 5T
    Older device, does not have the hardware for hardware attestation.
    • Stock OnePlus OS 10.0.1 (SDK29)
    • Magisk (snapshot build)
    • MagiskHidePropsConf (Magisk Module)
      • Enable Zygisk
      • Enable DenyList
      • add com.google.android.gms.unstable to the DenyList.
        Magisk is in /sbin so only needed to Deny .unstable
      • Enable the MagiskHide props. option in the MagiskHidePropsConf module.
    Reboot in between steps as needed.

    OnePlus 6T
    • Stock OnePlus OS 11.0.0 (SDK30)
    • Magisk (snapshot build)
    • Universal SafetyNet Fix (Magisk Module)
      • Enable Zygisk
      • Enable DenyList
      • add com.google.android.gms.unstable to the DenyList.
      • add com.google.android.gms to the DenyList.
    Reboot in between steps as needed.

    Pixel 3a
    Custom rom that passes SafetyNet on it own.
    Installing Magisk breaks SafetyNet.

    • ABC Rom 11 (SDK30)
    • Magisk (snapshot build)
      • Enable Zygisk
      • Enable DenyList
      • add com.google.android.gms.unstable to the DenyList.
      • add com.google.android.gms to the DenyList.
    Reboot in between steps as needed.

    Earlier today, I setup an update channel so I could test a few more things.
    • Install update from online.
    • Repack (Hide/Restore) the Magisk app.
    All worked. :)
    Note:
    I will have to wait until the next commit(s) to see if I can update while the Magisk app is hidden. 🙃

    ---

    So far The next step of growth and development of Magisk is looking great. :)

    I am excited and eagerly waiting for the next canary build for proper testing. :D

    Cheers all. :cowboy:

    PS.
    Some screenshots from my 6T. ;)


    Edit (5.Oct.2021):
    Please see my follow up post.
    Post 48,294 - Link
    9
    Latest Alpha Magisk Chinese Translated:
    (For mavericks only! 😬)

    alpha update journal Magisk (cb4361b7-alpha-2)

    • [General] Based on cb4361b7, the content that has been merged into the upstream will not be listed anymore
    • [App] Correctly process any data from magiskd
    • [App] Support SharedUserld
    • [App] Delete the backup file after adding a thick boot mirror
    • [App] Built-in current version update log
    • [App] Use the local version when you cannot download the stub, now it can be used completely offline
    • [App] Switch to Java 8 modern time API
    • [DenyList] Dealing with suspicious props
    • [App] Expand and update SafetyNet, update the snet.jar version to 18
    • [General] Add an outdated cgroup v2 path
    • [Sepolicy] Add execmem to allow hook in zygote and system_server
    • [MagiskSU] If necessary, fall back to /dev/pts
    • [Zygisk] Repair may not take effect
    • [Busybox] Cancel optimization based on undefined behavior
    • [General] No longer automatically unlock the device block
    • [Zygisk] There is no report to prove that zygisk is incompatible with riru, remove the restriction
    • [Resetprop] Completely erase the old content when modifying/deleting
    • [General] Fix the race condition of thread pool
    • [Magisklnit] Do not intervene when booting to DSU

    How to install ?

    To install and use Magisk through the Magisk application, the general relationship should be completed 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. Customizing Recovery is not a supported method.

    You update the journal
    From 23.0 to cb4361b7

    • [General] Support pure 64-bit devices
    • [Generall supports Android 12 emulator
    • [Zygisk] Code injection framework
    • [General] Remove MagiskHide
    • [General] Support Simulator to add modules
    • [MagiskBoot] Support zimage format
    • [MagiskBoot] Add zopfhi encoder
    • [MagiskInit] Support bootconfig
    • [App] The repair installation function will now check if the script under /data/adb/magisk/ has not been updated
    • [Magisklnit] 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
    • [Magisklnit] Support oplus.fstab for some OnePlus and Opal devices
    • [App] Restart and update modules, not allowed to be marked as pending deletion
    • [App] Delete online warehouses
    • [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 helmet and add layer. Android 12+ is required.
    • [App] Delete the floating bottom bar and change it to the general bottom operation bar.
    • [General] Support compilation 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 the status of Zygisk, add a reminder that restart is effective
    • [Zygisk] Correctly handle the child zygote
    • [Zygisk] Disabled riru module
    • [Sepolicy] Fix Android 8 terminal cannot get root

    👍 Marvin.
  • 1067
    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