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

Magisk General Support / Discussion

Search This thread
Hi all. What do you think I should do if magisk manager doesn't start and just hangs?

Basically my Magisk Manager notified me of new update, so i went to menu (where all apps are shown) and clicked on Manegr (i changed the name of Magisk Manager). Sadly app didn't start, and android OS became almost not responding, it kinda crashed. This happens everytime i want to run magisk manager.

I am thinking of uninstalling magisk manager and reinstalling it, but i'm not sure how that will affect the root, and also because it has different name (Manegr). My other idea is dirty installing it over the current one, but same problems could arise.

Anyone got similar problem?
Hello,
I had the same problem. Just uninstall the app, download the latest version from github, then reinstall and change the name again. All the settings you made should be retained, that's how it was for me.

Kind regards
 
  • Like
Reactions: J.Michael

unknowndrop

Member
Sep 9, 2012
15
3
Hello.

I am planning to install Proton to my Pixel 2 XL over stock rom. Since I am really out of rooting 'scene'. Does magisk bypass safetynet and snapchat or mcdonalds app work while magisk is installed?
 

pndwal

Senior Member
guys, I see the latest magisk seems way more complicated than it needs to be requiring patching method, and checks for ramdisk support.
Covered, but just wanted to add that while methods for Magisk Installation (especially initial install) on modern devices have certainly become more complex due to device architecture changes, John has only been keeping up with / accomodating current needs. Patching method is very much needed were TWRP support is lacking / broken / impossible. Ramdisk support is actually ALWAYS needed to install Magisk, but where support for Ramdisk in boot partition is missing (and Magisk is Installed in Recovery partition ramdisk), installing from Custom Recovery has NEVER worked. Devices with ramdisk in custom partitions (eg Huawei Ramdisk partitions) also require new methods.

John Wu himself takes pains not only to update, improve and keep Magisk device compatibility way ahead of practically any other software solution (currently supports any device with unlocked bootloader from Android 5 to present), but also to keep anyone interested informed about progress / what it means / how it works / how it affects existing users.

Of course, many changes have had to be introduced to add compatibility with so many changes in OEM system architecture, as well as Google's requirements to move to higher API levels. But, as stated, John has purposely retained legacy Custom Recovery zip Installation support for devices with compatible TWRP (Nb. latest v. 3.5.2 does not yet support Android 11+). But he states:
This installation method is deprecated and is maintained with minimum effort. YOU HAVE BEEN WARNED!

It is very difficult to accurately detect the device’s information in custom recovery environments. Due to this reason, installing Magisk through custom recoveries on modern devices is no longer recommended. If you face any issues, please use the Patch Image method as it is guaranteed to work 100% of the time.
https://topjohnwu.github.io/Magisk/install.html#custom-recovery

Regarding challenges overcome making Magisk compatible with evolving Android architecture, see:
https://topjohnwu.github.io/Magisk/boot.html

This lists four distinct Android Device types using various Boot methods, the first being "Good old legacy ramdisk boot", the next three requiring major innovation to accommodate System As Root, A/B partitions, Dynamic Partitions, Two Stage Init, USES_RECOVERY_AS_BOOT, Recovery partition ramdisk only, etc. Great technical read.

Incidentally, for anyone interested in general Magisk history:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-83707709 PW
 
Last edited:

pndwal

Senior Member
Hello.

I am planning to install Proton to my Pixel 2 XL over stock rom. Since I am really out of rooting 'scene'. Does magisk bypass safetynet
Yes, at present time in combination with Universal SafetyNet Fix Magisk module, and, if Rom does not include a Google Certified fingerprint, MagiskHide Props Config module w/ a certified fingerprint selected.
Someone else?
or mcdonalds app work while magisk is installed?
Works fine if checked in MagiskHide list. (May need to clear data after hiding root.)

PW
 

pndwal

Senior Member
Hi all. What do you think I should do if magisk manager doesn't start and just hangs?

Basically my Magisk Manager notified me of new update, so i went to menu (where all apps are shown) and clicked on Manegr (i changed the name of Magisk Manager). Sadly app didn't start, and android OS became almost not responding, it kinda crashed. This happens everytime i want to run magisk manager.

I am thinking of uninstalling magisk manager and reinstalling it, but i'm not sure how that will affect the root, and also because it has different name (Manegr). My other idea is dirty installing it over the current one, but same problems could arise.

Anyone got similar problem?
Good advice above.

New Magisk App is not compatible with old Magisk Manager. It should be unhidden (restored) or removed before new App is installed.
https://topjohnwu.github.io/Magisk/releases/22000.html

Your general Magisk settings / modules etc will be preserved if you do it afterward too (remove App AND Manager if both installed before new Install), as uninstalling Manager / App only does not remove these from data/adb/ 👍 PW
 
  • Like
Reactions: J.Michael

pndwal

Senior Member
Good day dear community,
I have a question regarding the use of the app S-pushTAN(https://play.google.com/store/apps/details?id=com.starfinanz.mobile.android.pushtan) and the Magisk Manager.
I have hidden the app in MagiskHide and renamed Magisk. There is no file/folder named Magisk, root or TWRP in my memory, yet the app does not work based on root detection according to the message. What can I do? Does anyone have any ideas? The picture shows the current Magisk version I am using.

Many thanks already

Translated with www.DeepL.com/Translator (free version)
Don't know the app, but generally:

Check you have full SafetyNet pass. If not, see my post above:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85013583

Check Google Play Services as well as your app is in MagiskHide list. If not, toggle MagiskHide off then on again in Magisk App Settings and check again.

Next, clear your apps data (to reset flags) and try it again.

More here:
https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot# 👍 PW
 
  • Like
Reactions: J.Michael

Elmarigo

Senior Member
Jun 13, 2014
195
73
On my my Galaxy A40 Magisk shows "A/B" as "No", despite the phone being partitioned as A/B (but with B partition unused).
I wonder if that's the reason, why te last Magisk update killed my phone into a state, where only an complete Odin stock reflash could recover.
Not even restoring the all partition backup I had through TWRP could help around the issue.
 

73sydney

Senior Member
Jul 21, 2018
1,990
1,777
Sydney
Google Pixel 2 XL
Hello.

I am planning to install Proton to my Pixel 2 XL over stock rom. Since I am really out of rooting 'scene'. Does magisk bypass safetynet and snapchat or mcdonalds app work while magisk is installed?

Just a quick FYI, when i tested the most recent Proton for Pixel 2XL, it did not pass SafetyNet

Dev is aware. (Dev is also dev of https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/ , which is built into his Proton ROMs and now built into others as well)

The older build: proton-aosp_taimen-ota_11.3.3.zip did pass fine, and from memory it passed out of the box, no fiddling needed, other than the standard install of the latest version of Magisk (v23) and Magiskhide toggled on in Magisk Manager > Settings.

You can grab the previous 11.3.3 taimen (Pixel 2XL) builds (G-Apps included or G-Apps free) here:


OR

Dev has a web based installer (Chrome best) here: https://protonaosp.kdrag0n.dev/install/web/

Though ive never used it, so i cant tell if you that earlier 11.3.3 is a choice via that method.

If you get stuck either way, manually, or via the web installer, reply in the Proton thread.

I used 11.3.3 for a long while, and waiting for the dev to fix the recent issues before i go back to it
 

beejkitsune

Senior Member
May 2, 2015
115
23
31
Durham, England
Google Pixel 5
I've searched the thread to no avail and wondered if anyone could advise.

After updating to the latest version, upon rebooting my phone gets stuck at "Phone is starting" message and doesn't progress further no matter how long I leave it. I had to then flash the original boot img and even trying to flash a patched img, I still get the same error message.

My only other resort would be to completely wipe and start from fresh but if anyone could suggest something else I could try first I would be very grateful. TIA!
 

73sydney

Senior Member
Jul 21, 2018
1,990
1,777
Sydney
Google Pixel 2 XL
I've searched the thread to no avail and wondered if anyone could advise.

After updating to the latest version, upon rebooting my phone gets stuck at "Phone is starting" message and doesn't progress further no matter how long I leave it. I had to then flash the original boot img and even trying to flash a patched img, I still get the same error message.

My only other resort would be to completely wipe and start from fresh but if anyone could suggest something else I could try first I would be very grateful. TIA!

Which device are you using?
What ROM?
Custom recovery?
How did you get the original boot img?
 
  • Like
Reactions: J.Michael

73sydney

Senior Member
Jul 21, 2018
1,990
1,777
Sydney
Google Pixel 2 XL
Apologies, should have mentioned that. Pixel 5, stock ROM and latest security patch (May 2021), stock recovery and I got the original boot IMG from developers.android.com.

Okay so from the stock ROM (im assuming its similar to my stock Pixel 2XL one), youre using the boot.img from inside the nested image zip inside the main stock ROM zip and not the bootloader image in the main zip?

Have you tried flashing boot.img to both slots?

In fastboot mode...

fastboot flash boot_a boot.img
fastboot flash boot_b boot.img

Beyond that nothing is really rattling around the old brain pan here after 19 hours of being awake, and im about to head to bed as its just hit 6am here
 

pndwal

Senior Member
Apologies, should have mentioned that. Pixel 5, stock ROM and latest security patch (May 2021), stock recovery and I got the original boot IMG from developers.android.com.
Source of boot.img used is a concern.

Please consider downloading complete currently used ROM and extracting image(s) to ensure they are a proper match as per official Installation Instruction method. Nb. mismatched boot.img may still work, but often with issues such as wifi problems, etc.

Could be recovery.img has also become corrupted, especially if Magisk App on your device shows Recovery mode option.

Extract image from current stock ROM package and flash from PC using fastboot just as for boot.img. This often fixes 'Your system is corrupt' and other similar errors.

More details:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84944727

Hope it helps. PW
 
Last edited:
  • Like
Reactions: 73sydney

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,751
5,583
Sydney
I am subscribed to a Magisk module developer thread, which to my annoyance (mostly due to the new forum interface) I cannot find right now. Does a anyone have the link to the developer thread handy?
I am looking into the magiskpolicy file, which is documented at https://topjohnwu.github.io/Magisk/tools.html#magiskpolicy
These se linux commands are placed into a sepolicy.rule file in the module directory. My questiuons are:
1. Can the lines end with a semi-colon (";")? I previously built ROMs from source, and the standard format was to include the semi-colon at the end of each line (see here for an example)
2. Can I include comments (preceeded with a hash (#) character. Again, see the above example file

The reason I ask instead of just try, my device (Pixel 4a) does no0t have TWRP for A11, and so getting out of a boot-loop is problematic, at best.
 

Tanvir Rezwan

Member
Apr 15, 2021
10
6
Seen this?:
https://forum.xda-developers.com/t/pubg-crashing-fixed-on-rooted-phones.4073331/

Seems pubg now detects root, but doesn't Give any error, just crashes.

So you need to hide root from pubg like any security centric bank app. My method:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84936057

Nb. Hide / wipe order.

Additionally, seems you also need to hide Magisk App according to 'pubg-crashing...' thread OP.

Nb.2. OP there may be confused about the need for MagiskHide Props Config module. It shouldn't make ANY difference unless props are also 'configured' (added / altered) through its terminal emulator interface, but OP hasn't indicated any changes to make / configuration. (I could be wrong, but try first without it.)

Hope this one helps! 😛 PW
Its not pubg also my system gets lagged without restart my device with in 24 hours.. And then my system ui is not responding showed

My module iam using are
In the ss

Seen this?:
https://forum.xda-developers.com/t/pubg-crashing-fixed-on-rooted-phones.4073331/

Seems pubg now detects root, but doesn't Give any error, just crashes.

So you need to hide root from pubg like any security centric bank app. My method:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84936057

Nb. Hide / wipe order.

Additionally, seems you also need to hide Magisk App according to 'pubg-crashing...' thread OP.

Nb.2. OP there may be confused about the need for MagiskHide Props Config module. It shouldn't make ANY difference unless props are also 'configured' (added / altered) through its terminal emulator interface, but OP hasn't indicated any changes to make / configuration. (I could be wrong, but try first without it.)

Hope this one helps! 😛 PW

Screenshot_20210515-143208.png
Screenshot_20210515-143225.png
Screenshot_20210515-143236.png
 
  • Like
Reactions: J.Michael

73sydney

Senior Member
Jul 21, 2018
1,990
1,777
Sydney
Google Pixel 2 XL
Source of boot.img used is a concern.

Please consider downloading complete currently used ROM and extracting image(s) to ensure they are a proper match as per official Installation Instruction method. Nb. mismatched boot.img may still work, but often with issues such as wifi problems, etc.

Could be recovery.img has also become corrupted, especially if Magisk App on your device shows Recovery mode option.

Extract image from current stock ROM package and flash from PC using fastboot just as for boot.img. This often fixes 'Your system is corrupt' and other similar errors.

More details:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84944727

Hope it helps. PW

The Pixel official ROMs have a zip which contains some files, including bootloader, and then a nested zip which contains all the img files, and he was definitely using the correct boot.img file

main zip:

bxsP8Wl.jpg


nested zip within main zip, containing all the img files

OIOvV7O.jpeg


Its one thing i really like(d) (because of course the Pixel 2XL is now out of support) about the stick ROM, it was simple to get at the various img files if you borked something, none of the payload.bin nonsense :)
 
  • Like
Reactions: J.Michael

73sydney

Senior Member
Jul 21, 2018
1,990
1,777
Sydney
Google Pixel 2 XL
Its not pubg also my system gets lagged without restart my device with in 24 hours.. And then my system ui is not responding showed

My module iam using are
In the ss



View attachment 5309785View attachment 5309787View attachment 5309789

My first thought: bin the LSpeed module

Ive never met a "speedup/optimizer" script or module or app yet post-Marshmallow that does anything but make a device slower, warmer or chew more battery

My second thought is always going to be: bin Xposed :)
 

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
    2
    I see you've said this several times now... Please say what issue you have... All good for me in browser and app. PW
    I "Search in this thread" for "Alpha", from the XDA app.
    It lists me the whole bunch of posts without a single occurence of the keyword Alpha - see the screenshots

    How could I use that 'help' if I really want to search wether the Magisk Alpha was already discussed and particularly e g. how to setup MagiskHide in Alpha?!

    SupposevI'm really new to this thread and I really cannot start reading backwards through the hundreds of posts (mostly repaeting questions and answers: Where is the repo in the new Canary, or Why my updated Magisk app does not find the Magisk installed, etc).
    Then, I could not do any better but also repeat the.question, thus further poluting the thread and burying down those small number of worth and informative posts
    2
    [ ... ] hundreds of posts [ ... ]
    Literally thousands of posts, actually. This one is number 49,396.

    This is a hugely daunting amount of data to dig through. I'm very much in favor of a new thread for advanced Magisk users.
    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
    2
    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.
  • 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