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

Magisk General Support / Discussion

Search This thread

pndwal

Senior Member
How to install abfb3bb3? John says he pushed the build but it's not seen in the app and I can't install it from GitHub manually.
Well he didn't say 'pushed a build'. Said 'the code' (no release yet):
John Wu, 1h

The Zygisk API is finalized and the first iteration of Zygisk module loading implementation is done! The code is pushed to GitHub for those adventurous, I'll do a bit more polishing before releasing a long awaited canary release!

Gotta be close though! 😛

... Gonna build it @ipdev ? 🤗 PW
 
Last edited:
  • Like
Reactions: ipdev and 73sydney

pndwal

Senior Member
Pretty brave paragraphism on a partially tangental reply :)

Just saying, it would be nice to get some good news for a change

Blindly flipping switches on stuff doesnt seem to be working well for most people.

If people are designing one thing (zygisk) to disable the functionality of another thing (riru), it should be made abundantly clear up front, so that people arent wasting their collective time trying to put square pegs in round holes...

As someone who needs momo-hider level hiding in their daily lives, its a lot of work trying to sift through whats going on

Long live (vvb2060) magisk alpha 31, for it still provides...

See you soon in Zygote Game, ill be wearing a tracksuit, and be badly dubbed (even in English)

..Nigel..
Pretty brave calling Zygisk Evil too mate! - Look up; it's the biggest ship on the horizon now!

Anyone using Alpha is a maverick who oughta be expert at fitting multiple square pegs in round holes, but you're welcome to keep playing with your peg board. - Just don't miss the good news for a fixation on finances!

I'll be playing Zygote proper soon I hope, wearing winklepickers and a waistcoat; the banks can go jump. 🧀 / 🍰 PW
 
Last edited:

pndwal

Senior Member
thats more like it...but will webview work with riru mods installed

i await Marvins testing :)

Might have a go myself
Latest Alpha report (w/ RN8T):
S/N ✓
LSPosed ✓
Viper4Android FX ✓
Webview ✓
MomoHider w/ all 4 hydetypes X
- breaks widgets, apps, stability.
- next reboot breaks Zygisk
MomoHider w/ initrc, isolated ✓
(w/ or w/o Riru - Enhanced Mode for MH)
Screenshot_2021-10-18-03-13-38-318_io.github.vvb2060.mahoshojo.jpg

Screenshot_2021-10-18-03-08-38-147_io.github.vvb2060.magiskdetector.jpg

Screenshot_2021-10-18-03-08-20-079_io.github.vvb2060.zygiskdetector.jpg

Riru - Enhanced Mode for MH only ✓
Screenshot_2021-10-18-03-17-41-984_io.github.vvb2060.mahoshojo.jpg

Screenshot_2021-10-18-03-25-15-063_io.github.vvb2060.magiskdetector.jpg

😛 PW
 
  • Like
Reactions: jons99 and 73sydney

73sydney

Senior Member
Jul 21, 2018
1,990
1,777
Sydney
Google Pixel 2 XL
Latest Alpha report (w/ RN8T):
S/N ✓
LSPosed ✓
Viper4Android FX ✓
Webview ✓
MomoHider w/ all 4 hydetypes X
- breaks widgets, apps, stability.
- next reboot breaks Zygisk
MomoHider w/ initrc, isolated ✓
(w/ or w/o Riru - Enhanced Mode for MH)
View attachment 5435469
View attachment 5435471
View attachment 5435473
Riru - Enhanced Mode for MH only ✓
View attachment 5435475
View attachment 5435477
😛 PW

Good info Marvin

You beat me to it...in the middle of restoring apps after a clean flash....Momohider config noted, will test same
 
  • Like
Reactions: pndwal and jons99

zgfg

Senior Member
Oct 10, 2016
6,113
3,622
What's going on now - SafetyNet in Magisk (Alpha) still passes but all others I tried fail (Signature verification)?

How come that only SN checker in Magisk app does not have a problem?!
 

Attachments

  • IMG_20211017_190013.jpg
    IMG_20211017_190013.jpg
    160.4 KB · Views: 43
  • IMG_20211017_190050.jpg
    IMG_20211017_190050.jpg
    141.7 KB · Views: 41
  • IMG_20211017_190050.jpg
    IMG_20211017_190050.jpg
    141.7 KB · Views: 42
  • IMG_20211017_190117.jpg
    IMG_20211017_190117.jpg
    183.2 KB · Views: 43

jons99

Senior Member
Nov 5, 2019
219
263
What's going on now - SafetyNet in Magisk (Alpha) still passes but all others I tried fail (Signature verification)?

How come that only SN checker in Magisk app does not have a problem?!
new alpha is out and safetynet check is no more
photo_2021-10-17_21-29-18.jpg

so don't worry about it
I think it's an issue with googles server
 

73sydney

Senior Member
Jul 21, 2018
1,990
1,777
Sydney
Google Pixel 2 XL
Latest Alpha report (w/ RN8T):
S/N ✓
LSPosed ✓
Viper4Android FX ✓
Webview ✓
MomoHider w/ all 4 hydetypes X
- breaks widgets, apps, stability.
- next reboot breaks Zygisk
MomoHider w/ initrc, isolated ✓
(w/ or w/o Riru - Enhanced Mode for MH)
View attachment 5435469
View attachment 5435471
View attachment 5435473
Riru - Enhanced Mode for MH only ✓
View attachment 5435475
View attachment 5435477
😛 PW

Exciting news Marvin, Magisk (abfb3bb3-alpha) (from the Telegram Magisk Alpha group, and hopefully not to confuse folks using the other (mainstream) alpha from the original repo) is workies on my devices of many needy apps

First time in a while anything above (vvb2060's) Alpha 31 that has worked for me.

Even with having to manually denylist apps anew because the old magisk.db wasnt compatible and i couldnt just copy my usual one over, i still managed to get everything working without any apps seeing anything - shall back this magisk.db up for new experiments (and because im lazy)
 
Last edited:
  • Like
Reactions: pndwal and ipdev

zgfg

Senior Member
Oct 10, 2016
6,113
3,622
Latest magisk alpha isn't passing safetynet. I have Safetynet fix installed but it isn't passing basicIntegrityView attachment 5435581
Latest Alpha 8276a077 does not have SafetyNet checker anymore!

You must be running an older Alpha (maybe abfb3bb3 that was also released today but earlier - now no more the latest)
 

Attachments

  • Screenshot_2021-10-17-21-27-41-652_org.telegram.messenger.jpg
    Screenshot_2021-10-17-21-27-41-652_org.telegram.messenger.jpg
    411.6 KB · Views: 41
  • Screenshot_2021-10-17-21-28-14-759_com.topjohnwu.magisk.jpg
    Screenshot_2021-10-17-21-28-14-759_com.topjohnwu.magisk.jpg
    368.9 KB · Views: 41

73sydney

Senior Member
Jul 21, 2018
1,990
1,777
Sydney
Google Pixel 2 XL
fwiw, on the TheHitMan magisk alpha theres still SafetyNet test, and it returns a valid test result (pass), both the other SafetyNet testers i have installed (SafetNet attest' and YASNAC) fail to return a valid reply...response signature invalid...
 
  • Like
Reactions: pndwal and ipdev

zgfg

Senior Member
Oct 10, 2016
6,113
3,622
fwiw, on the TheHitMan magisk alpha theres still SafetyNet test, and it returns a valid test result (pass), both the other SafetyNet testers i have installed (SafetNet attest' and YASNAC) fail to return a valid reply...response signature invalid...
I suppose that for those here who still run Stable (or Canary), Safetynet checker in Magisk app would also wrongly show SN pass

There is a problem with Certificate expiration (attachemnt below from TG), seems that TJW's implementation does not properly look into the Certificate

But some say that if you wipe Data for Google Play Services), that SN in Magisk will also fail (hence there is some improper caching)
 

Attachments

  • -6296199319388270840_121.jpg
    -6296199319388270840_121.jpg
    247.9 KB · Views: 63

martyfender

Senior Member
Mar 9, 2017
3,175
1,695
Indianapolis, IN
I'm pretty sure something is going on on Googles side. I have one device that is on an older Magisk alpha cb4361b7-alpha-2 and it passes safetynet test in the Magisk app, but fails on 3 third party safetynet tests. This is also true on another, same device, with the latest 2 alphas.
 
  • Like
Reactions: pndwal and ipdev

ipdev

Recognized Contributor
Feb 14, 2016
1,620
1
2,177
Google Nexus 10
Nexus 7 (2013)
I suppose that for those here who still run Stable (or Canary), Safetynet checker in Magisk app would also wrongly show SN pass

There is a problem with Certificate expiration (attachemnt below from TG), seems that TJW's implementation does not properly look into the Certificate

But some say that if you wipe Data for Google Play Services), that SN in Magisk will also fail (hence there is some improper caching)
I'm pretty sure something is going on on Googles side. I have one device that is on an older Magisk alpha cb4361b7-alpha-2 and it passes safetynet test in the Magisk app, but fails on 3 third party safetynet tests. This is also true on another, same device, with the latest 2 alphas.

Yep.

Starting today.
SafetyNet is failing across the board for me. :(

PlayStore still shows certified but, I am sure that will change the next time Google scans the device(s).
(Edit. Then again, maybe not. :unsure: See PPS. and my next post.)

Cheers all. :cowboy:

PS.
Just like last time, prepare for multiple reports everywhere about failing SafetyNet. 🙃


PPS.
Then again, this could also just be a change in Google's SafteyNet like last time.
[When SafetyNet checker apps had to be updated.] :unsure:
 

Attachments

  • Screenshot_20211017-153633_SafetyNet_Check.png
    Screenshot_20211017-153633_SafetyNet_Check.png
    130.2 KB · Views: 60
  • Screenshot_20211017-154213_YASNAC.png
    Screenshot_20211017-154213_YASNAC.png
    81.9 KB · Views: 58
  • Screenshot_20211017-154232_Root_Checker_Pro.png
    Screenshot_20211017-154232_Root_Checker_Pro.png
    94.1 KB · Views: 57
Last edited:
  • Like
Reactions: rodken and 73sydney

ipdev

Recognized Contributor
Feb 14, 2016
1,620
1
2,177
Google Nexus 10
Nexus 7 (2013)
<SNIP>
But some say that if you wipe Data for Google Play Services), that SN in Magisk will also fail (hence there is some improper caching)
Quick test on my OnePlus 5T.
Stock OOS 10.0.1
Magisk canary


Even after clearing cache and all app data from PlayServices and PlayStore.
Reboot and give it time for Google to update PlayServices and PlayStore.

Magisk shows passing SafetyNet when other SafetyNet checkers have errors.
PlayStore came back as certified. ;)

Cheers. :cowboy:
 

Attachments

  • Screenshot_20211017-161339.jpg
    Screenshot_20211017-161339.jpg
    246.5 KB · Views: 52
  • Screenshot_20211017-161418.jpg
    Screenshot_20211017-161418.jpg
    247.2 KB · Views: 51
  • Screenshot_20211017-161433.jpg
    Screenshot_20211017-161433.jpg
    110.2 KB · Views: 46
  • Screenshot_20211017-161454.jpg
    Screenshot_20211017-161454.jpg
    280.4 KB · Views: 48
  • Screenshot_20211017-161503.jpg
    Screenshot_20211017-161503.jpg
    328.7 KB · Views: 48
  • Screenshot_20211017-161511.jpg
    Screenshot_20211017-161511.jpg
    160.1 KB · Views: 47
  • Screenshot_20211017-161527.jpg
    Screenshot_20211017-161527.jpg
    180.4 KB · Views: 44
  • Screenshot_20211017-161942.jpg
    Screenshot_20211017-161942.jpg
    400.5 KB · Views: 52
  • Like
Reactions: pndwal and zgfg

zgfg

Senior Member
Oct 10, 2016
6,113
3,622
Latest Alpha Magisk cb4361b7-alpha

*** For Mavericks only! ***

Chinese Translated:
Magisk Alpha update log (abfb3bb3-alpha)

• [General] Based on abfb3bb3, the content that has been merged into the upstream is no longer listed
• [App] Correctly process 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 cannot download the stub, now it can be used completely offline
• [App] Switch to Java 8 modern time APl
• [DenyList] Handles suspicious props
• [App] Expand and update SafetyNet, update the snet.jar version to 18
• [General] Add an outdated cgroup v2 path
• [MagiskSU] If necessary, fall back to /dev/pts
• [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
• [Magiskinit] Do not intervene when booting to DSU

How to install?

Use the Magisk application to install and print Magisk. In general, it should be installed directly in the application.

In 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 way.

Update journal
From 23.0 to abfb3bb3

• [General] Support pure 64-bit devices
• [General] Supports Android 12 emulator
• [Zygisk] Code injection framework
• [General] Delete MagiskHide
• [General] Support Simulator to add modules
• [MagiskBoot] Support zlmage format
• [MagiskBoot] Add zopfi 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
• [Magiskinit] Support oplus.fstab for some OnePlus and Opal devices
• [App] Restarted to update modules, not allowed to be marked as pending deletion
• [App] Delete online warehouse
• [App] Add mounting information for 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 pop up window hides the additional screen layer Android 12+ is required.
• [App] Delete the floating bottom bar, change to the general bottom operation bar
• [General] Support compilation caching
• [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 hook in zygote and system_server
• [Resetprop] Erase the old content completely when editing/deleting
• [General] Fix the race condition of thread pool
• [zygisk] Public module API

👍 PW
There was later today one more Alpha: 8276a077

Anyway, where can I see vvb2060 commits for his Alpha releases on TG?

Bcs, by looking to his commits here, I cannot find any branch with the commits newer than from the last month:
 
  • Like
Reactions: ipdev

purgy

Senior Member
Aug 29, 2013
104
17
Sydney
Re: riru vs zygisk, according to the lsposed tg, they've got an unreleased build that runs on zygisk without the need for riru at all.

Will be interesting to see how it all pans out.

Funnily enough, the services nsw check-in app is more concerned (even before the vaccine proof stuff) with sn status than CommBank.
 
  • Like
Reactions: pndwal and ipdev

Top Liked Posts

  • 6
    The advanced user can continue using telegram and github.
    Spreading the advanced info here is just surplus.

    The advanced users are just being lazy, Geez I would think we had a bunch of newbies here. 😜🤣
    Actually if I wouldn't follow this thread I would never know about Magisk Alpha, Magisk Custom, Shamiko and many other useful stuff. I wouldn't know how to find them or if they even exist. So I'm really greatful to all the people who share this info here
    3
    Exactly, I want Magisk to March forward.
    No root, no modding.
    Someone needs to take responsibility or close the thread.
    There is close to fifty thousand post here of chaos.

    The are multiple how to root threads in just about every device thread.
    The contributer or developer of said threads. Clearly points people in the right direction without all the BS.

    I will shut up and what everybody wants here.
    To be clear I can also post about any Magisk topic here.
    Example ;
    How can I root my Atari 2600 and add the angry birds module. Should I use version 23, Canary, beta, alpha. Please help, I don't understand. Lol
    It may be chaos, but...

    - It's a chronological catalogue of general Magisk support and discussion notes in one place.
    - It contains answers to nearly every Magisk issue.
    - It can be searched by keywords and by specific members to narrow down pertinent results, especially when members recall earlier discussion.
    - Contributing members can and will continue to use this thread as a database of issues / solutions and already have their own methods of keeping track or tracking down such previously proffered help.
    - It has enough active contributing members happy to help others to make it an effective means of obtaining timely solutions for issues encountered by the newbie or the experienced user.
    - It is one of Magisk's most valuable resources for the above and more reasons. As a couple of examples of more:
    - It provides an interesting diversion simply due to opinions / conjecture / ideas / poppycock / claptrap / balderdash as well as the notable and salient comments on all things Magisk.
    - It has modern moderators, modestly making minor modifications to misdirected, misconstrued or malevolent members mumblings...

    Why close it? 😬 PW
    3
    If this thread is specifically for discussing the Magisk app and patch, the thread title should be changed accordingly. If I were having problems with a particular module, this would seem like the most reasonable place to me to ask questions.

    As far as repetitive questions...that's just going to happen. You can try cutting down on this by addressing specific issues in the OP, but it's pretty insane to expect someone to read through over 49,000 posts to try to find an answer to their problem.

    At the end of the day, we are all expected to abide by and uphold the rules. As a reminder:

    2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.

    2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.

    2.5 All members are expected to read and adhere to the XDA rules.

    While I understand it can be frustrating to deal with new and inexperienced users, not to mention at times annoying, you are still expected to conduct yourself in a professional and civil manner, even if you're a Recognized Contributor or developer. Any sort of public shaming or ridicule is a direct violation of the forum rules, and will not be tolerated from anyone.

    I hope we understand each other.
    1
    ....that Magisk Custom 23015 debug cannot be reanamed to zip and flashed through TWRP....
    ...Then, you will have to fully configure the new Magisk Custom (MagiskHide, root apps, modules), everything from scratch....
    ....I also use Magisk Custom d208be84 (23015) and have no problem with MagiskHide....
    i'm on the latest Magisk Custom d208be84 (23015) (22). i usually do a dirty install - restore the hidden/renamed magisk manager back to normal before uninstalling, then install the new version, reboot to twrp, flash the renamed (apk to) zip and things are ok after a reboot.
    1
    Yeah, I am done with the ranting.
    Post 49411 shows what I was trying to stop. The poor guy read all the different ways and now he is stuck and no one wants to help him.

    My apologies sorry for the mess I have created, was trying to do the right think.
    Did you create a mess?... or just an interesting diversion?... Reckon you contributed a number of good points to the general Magisk discussion... No need to apologize... not to me anyway!

    And you certainly didn't create the chaos! 😝 PW
  • 39
    I've been following the thread for a long time now, and I think some users are still confused regarding the differences between the different variants of Magisk that are available for use. I'm going to try and summarize them here, which should be helpful for everyone:

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

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

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

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

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

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

    ---

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

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

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

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

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

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


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

    Hope it helps more than confuse. 🙃

    Cheers. :cowboy:
    12
    Hi all. :D

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

    Seemed to be appropriate to mention here.

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

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

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

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

    Cheers all. :cowboy:
    11
    It is assumed that "Public Release" Magisk users will read
    1) Magisk GitHub main page (linked from OP here by clicking Announcement Thread, then Magisk's GitHub Page).
    2) Official Installation Instruction linked from there (Useful Links).
    3) Release Notes that pop up when clicking Magisk or Magisk Beta links (under Downloads).

    Important Note for Canary Magisk users:

    As this thread, originally for "Public Releases" only, has also become the defacto Magisk General Support / Discussion thread for Canary builds (since original "Magisk Canary Channel - Bleeding Edge Builds"
    https://forum.xda-developers.com/t/closed-dev-magisk-canary-channel-bleeding-edge-builds.3839337/
    is closed for further replies; Nb. the OP links there are to old "archived" Canary build repo) and more recently has additionally included general discussion on some unofficial Magisk modified or pre-official release builds, If you intend to switch to debug Canary or other non-'public' builds please note the following:

    1) Please be familiar 1) & 2) above.

    2) Please check Release notes for your Canary build as well as upstream changes in earlier Canary builds at least back to previous public Stable. Since these don't pop up when clicking Canary link in John's main GitHub page, you need to know where to look.

    Current Canary repo is easily found by clicking topjohnwu at top of Magisk main page to go to root of topjohnwu GitHub, click magisk-files repo and change branch to canary. This is /magisk-files/tree/canary repo/branch.

    Here, clicking View code, then README.md will give you latest release notes only. You should click history (clock) icon, select a Canary update by date and Browse files before clicking View code, then README.md to see release notes.

    Currently, please start from Oct 24, 2021 update notes which include a link to John's 'blog post' State of Magisk: 2021 - very important information on current debug Canary changes and direction of future public Stable / Beta builds. Next, check notes up the page to current Canary.

    Please similarly check upstream notes for unofficial builds if you decide to try these by familiarising yourself with relavent GitHub / Telegram (/other?) pages.

    If you can't do this you really shouldn't be using 'bleeding edge' Canary or other builds. This is really basic preparation and will save yourself as well as others in this thread especially, much frustration, angst and annoyance. 😉

    If you have issues, you'll also find answers to most of them linked from main page under Useful Links in Frequently Asked Questions, Magisk Documentation and (the excellent, exhaustive & - dare I say it - elegant) Magisk Troubleshoot Wiki by @Didgeridoohan.

    For further understanding, the Magisk Documentation designated 'for developers' is actually most enlightening / useful for Magisk users in general; don't check YouTube 'tutorials', read John's succinct docs! - I recommend 'Android Booting Shenanigans' for starters (especially if interested in new Android architecture changes and challenges new devices pose for Magisk).

    I especially hope some of the detail above helps Magisk's more maverick (or otherwise intrepid) users! 😀 PW
    10

    Latest Magisk Canary:​

    Magisk (7e9d4512) (23014)​

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

    Diffs to v23.0​

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    The Flash
    Forum Moderator

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

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

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

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

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