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

Magisk General Support / Discussion

Search This thread

Snowpuppy

Member
Aug 20, 2018
14
1
When, I wrote about you expressing your frustrations, I was reminiscing about my past frustrations the first time I tried to root my device. :eek:
After, reading your post 'again'. I noticed there are some Verizon Pixel XL owners that have unlocked their bootloader with this method:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
That are unable to root their phone. It doesn't seem to matter which factory image their using, or if they did a factory reset. I am not technically proficient enough to figure out why. :(

I did a variation of this method (without the uninstall user command). However, this is the only way to unlock bootloader on Verizon Pixel XL phones and people have gotten Magisk to work on Verizon's Pixel XL so... There's gotta be something.

What would prevent Magisk's bootfile from loading?
 

byReqz

Senior Member
Jul 14, 2016
249
65

Attachments

  • Screenshot_20180908-205305.jpg
    Screenshot_20180908-205305.jpg
    150.7 KB · Views: 402
Yeah, invalid, its not that important but strange
Perhaps you should MagiskManager force to redownload the small code segment needed for checking.

(Cleaning the storage of MagiskManager should do the trick. All relevant data (hidelist, root permissions, modules) are stored elsewhere so you should not lose important settings (custom update channel, theme setting etc. are effected).)
 
Last edited:

rhardy

Member
Dec 5, 2011
22
5
Ottawa
OnePlus 7T
I'm running the latest Magisk v17.1 using MagiskManager v5.9.1 on a Nexus 6P with latest available Android 8.1.0 with 2018-09-05 security patch. I'm having issues with long delays before Magisk kicks in after boot up. This problem has been an issue for several months. It has happened with many recently security patches and I've completely wiped the device and the issue doesn't go away. For some reason I'm having issues with long delays before my device is usable after startup. i.e. I'll get to functional home page, the device will be idle and startup processes are done but it takes between 90 seconds and 2 minutes before the Magisk startup tasks run and root is available. Any one know how to address this?
 

rub1k

Senior Member
Nov 6, 2008
137
29
Google Pixel 3a XL
I need help rooting a Nexus 6 using Magisk 17.1, please.

Here are the steps I'm doing. Could someone please let me know if I'm doing something wrong?

- Flash most recent 7.1.1 factory image (N8I11F, Oct 2017) and wipe data.
- Boot all the way through, log in to my Google account, let the phone settle.
- ADB push Magisk-v17.1.zip to /sdcard.
- Reboot to bootloader.
- Flash most recent TWRP (3.2.3.0) via "fastboot flash recovery".
- Reboot bootloader and go into TWRP recovery.
- Flash Magisk-v17.1.zip from /sdcard.
- Reboot.

Phone gets stuck on "Google" white logo... forever.

If I power off/reboot, data partition is corrupt and I have to start all over and I get stuck in the same place.

Any ideas/suggestions on how to proceed, please?

Thanks much in advance.

EDIT: I've tried "fastboot boot twrp-3.2.3.0.img" and flashing Magisk from there instead but the result is the same (doesn't seem to matter if TWRP runs from recovery partition or via 'fastboot boot').
 

byReqz

Senior Member
Jul 14, 2016
249
65
Perhaps you should MagiskManager force to redownload the small code segment needed for checking.

(Cleaning the storage of MagiskManager should do the trick. All relevant data (hidelist, root permissions, modules) are stored elsewhere so you should not lose important settings (custom update channel, theme setting etc. are effected).)
downloaded it right before the screenshot
 

Mandeep Hundal

Senior Member
Apr 24, 2017
104
4
Hello

I having issue with 17.0 version of magisk.
I after installing I tried to patch the boot img but result was failure.
Also lost root access , now even I try to install 16.0 but result also failure how to fix it.
 

Tecalote

Senior Member
Aug 6, 2015
4,080
3,116
Leipzig
Huawei Mate 40 Pro

Thanks :good:
Yes, this can be (easily) done, if TWRP has support for encryption and access to /data

Hey mate! Can you help me? What file does it mean by flashing patched ramdisk.img. Is it the stock ramdisk image that my phone software is in? I tried fastbooting patched ramdisk.img but magisk doesn't give me the option to continue. I can't even install magisk zip file. It just downloads but doesn't get installed.

The instruction has been updated (to make it clearer for users): https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
 
  • Like
Reactions: 25Swagat and dr4go

demonoidmaster

Senior Member
Nov 19, 2015
1,029
331
Oh it's not a bug. It's designed by Samsung. If you root any Samsung device, you will trip KNOX and lose all functionality of Samsung Pay and never get it back.
you know you can root without tripping it right? Hell you can even disable knox entirely, all depends on the device i think though

---------- Post added at 12:56 AM ---------- Previous post was at 12:53 AM ----------

No, he wasn't mentioning op3t, he was refereing to oneplus devices.

I never claimed something like that. "twrp-3.2.2-0 and 3.2.3-0 aren't able to decrypt data on oneplus devices" is just not true - exactly that was claimed. Please read my posting and the one I've responded to. I was never claiming it's working on each and every oneplus device, I have given one example of a working oneplus device. The generalisation you claim to be in my answer was in the posting I responded to.

Read before blaiming me for something I've never stated!
Oh you're right i misread what he said, (but you're condescending) so I'll leave it at that because i don't feel like replying to everything else you said. But regardless people have had decrypting issues on some devices (any models), this isn't news, it's actually true that it happens.

---------- Post added at 12:59 AM ---------- Previous post was at 12:56 AM ----------

Perhaps you should MagiskManager force to redownload the small code segment needed for checking.

(Cleaning the storage of MagiskManager should do the trick. All relevant data (hidelist, root permissions, modules) are stored elsewhere so you should not lose important settings (custom update channel, theme setting etc. are effected).)
False about root permissions, they along with the hidelist and any other settings get all wiped clean (unless this changed but i don't wanna clear it's data just to test)
 
Last edited:

Tecalote

Senior Member
Aug 6, 2015
4,080
3,116
Leipzig
Huawei Mate 40 Pro
I'm almost tempted to try this on my Pixel XL because the issue sounds very similar but I know it's a bad idea.
This is a Huawei-specific solution for Patch01 - I can not say anything about Pixel, because I do not know this device. I would recommend that you inquire in the Pixel Forum exactly.
However, boot img patching with Magisk is possible on all devices - but which flag must be set for Pixel - I really dont know.

We can do that also on every Huawei Phone, but normally without the flag: "Preserve AVB/dm-verity" - and "Preserve force encryption" is always required on Huawei Phones with Stock Firmware, because data is encrypted, except on Custom Roms if data is posibly decrypted through "format data"

You see, it is different. I would not do anything, if you are not sure. Except, if you want to experiment. But then only if you can make a full Nandroid backup with TWRP that you can play back in the worst case (at least from boot (or ramdisk) kernel, data, vendor)
Which issue sounds very similar?
 

Nickm2

New member
Apr 20, 2013
2
0
SafetyNet passes for a few minutes after boot, and then starts failing.

SafetyNet is passing right away after boot (both CTS Profile and Basic Integrity). At some point later on, SafeyNet starts to fail. It seems to happen at random. Sometimes, it'll start failing within seconds of being booted. Other times, it'll pass just fine for a few hours, and then start failing. I have had absolutely no luck finding the culprit. I've disabled all battery optimization that I'm able to (in case there was a process being killed somewhere), have tried using core only mode, and have checked the logs for any indication of the issue, with no luck. After boot, SafetyNet passes, at which point I'll clear the logs, and check a few minutes later. SafetyNet will usually be failing by that point, and there is nothing in either logs.

Device Info:
OnePlus 6 (A6003)
Oxygen OS 5.1.11 / Android 8.1.0
Security Patch Level July 1, 2018
Magisk 17.1
Magisk Manager 5.9.1

Does anyone have any ideas or has anyone else encountered this issue? I've found a few people on Reddit with the same issue, but haven't seen anything on XDA about it, so it seems to be a relatively rare problem.
 

Top Liked Posts

  • 5
    Notes for passing SafetyNet in new Magisk

    For TJW builds going forward you will need to add Google Play Services process(es) to denylist. For devices where Magisk resides in /sbin (many pre. Android 11), only deny SafetyNet process, com.google.android.gms.unstable. For Android 11+ etc (non /sbin), deny Main process, com.google.android.gms also.

    You also need solutions to edit keystore and possibly need to cause model mismatch etc to trigger fallbacks to basic attestation for various types used if device is equipped for Hardware TEE.

    Universal SafetyNet Fix (+Riru) was the best (all in one) solution for this and it even fixed 'sensitive' props issues, but with with Zygisk active we don't have a proper solution yet. (See above.)

    Using old USNF 1.2.0 does needed Keystore changes for pre Android 12 ROMs not 'heavily skinned'... Samsung and other users may have issues with the older solution, and could try reverting to pre-Ruru test module here:
    https://github.com/kdrag0n/safetynet-fix/pull/13#issuecomment-767863635
    This will Shim the keystore service instead of replacing it; it doesn't work for all heavily skinned ROMs, but various custom solutions are linked from same thread. Also, this solution works for some Android 12 ROMs. 🙂

    This may be enough to pass, but some devices may need a fix for 'sensitive' props set to 'trigering' values in addition. Just installing MHPC module does this as an alternative to USNF 2.x.x series; it is enabled by default.

    If your device is affected by September 2021 Google server end changes, you need to alter model prop (eg by using MHPC w/ Force Basic Attestation configured) in addition to cause fallback to Basic (a simple mismatch causes) for this particular hardware attestation.

    -Nb. there are several fallbacks needed but it seems any one type gives Evaluation type = basic, so basic evalType is misleading.
    -Nb.2. This early method can cause issues with OEM specific functionality like Galaxystore, camera functions etc as change is seen globally even if close model is selected as is recommended; 2.x series USNF w/ Riru could target Google Play Services only.
    (See Universal SafetyNet Fix GitHub and notes for individual releases.)

    You will also need to spoof a certified fingerprint if ROM is not certified (using a certified fingerprint). - MHPC with certified fingerprint configured is the best solution.

    Enjoy while it lasts! 🤠 PW
    5
    Ok, Alpha Dev explains this (Chinese translated):

    Seems latest Zygisk tweeks for new Zygisk LSPosed module now cause unresolved conflicts with Riru (likely due to using the same resources simultaneously I guess).

    John committed code to ensure these couldn't coexist some time ago, and vvb2060 reversed this in a few Alpha builds.

    Anyway, looks like Riru's fate is sealed going forward.

    I'm guessing most Riru modules will move to Zygisk in short order now. Users who want to use Riru modules for any reason will need to forgo Zygisk it seems...

    FWIW, I have SafetyNet passing with old USNF 1.2.0 and the Google Play Services SafetyNet process added to the DenyList in new Canary on Redmi Note 8T.

    I'll.post Notes for passing SafetyNet for others next. 👍 PW
    Yes, no other way, but LSPosed Zygisk version runs fine

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

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

    But generally, with the new Magisk, Google got what they approved
    3
    So there's no point updating magisk today if it's just gonna break things and it's already working as is right ?
    There is no point in updating if everything works for you. Updating at this time is very likely to break things.
    2
    Notes for passing SafetyNet in new Magisk

    For TJW builds going forward you will need to add Google Play Services process(es) to denylist. For devices where Magisk resides in /sbin (many pre. Android 11), only deny SafetyNet process, com.google.android.gms.unstable. For Android 11+ etc (non /sbin), deny Main process, com.google.android.gms also.

    You also need solutions to edit keystore, cause model mismatch etc to trigger fallbacks to basic attestation for various types used if device is equipped for Hardware TEE. - Universal SafetyNet Fix (+Riru) was the best (all in one) solution for this, but with with Zygisk active we don't have a proper solution yet. (See above.)

    Using old USNF 1.2.0 is enough for devices not affected by September Google server end changes.

    If your device is affected, you can pass by altering model prop (eg by using MHPC w/ Force Basic Attestation configured) in addition to cause fallback to basic (simple mismatch causes) for this particular hardware attestation.
    -Nb. there are several fallbacks needed but it seems any one type gives Evaluation type = basic, so basic evalType is misleading.
    -Nb.2. This early method can cause issues with OEM specific functionality like Galaxystore, camera functions etc as change is seen globally even if close model is selected as is recommended; 2.x series USNF w/ Riru could target Google Play Services only.
    (See Universal SafetyNet Fix GitHub and notes for individual releases.)

    You will need to spoof a certified fingerprint if ROM is not certified (using a certified fingerprint). - MHPC with certified fingerprint configured is the best solution.

    Enjoy while it lasts! 🤠 PW

    An alternative to using USNF 1.2.0 for devices that wasn't affeted by September google server end changes is to just use MHPC and enable it to spoof the magisk hide props (https://github.com/Magisk-Modules-R...README.md#setreset-magiskhide-sensitive-props) and enable com.google.android.gms and com.google.android.gms.unstable in the deny list works for me.
    2
    I woke up this morning to a Magisk app update notification for the first time in a long time.
    Ive never had an app update have a problem.
    The app updated and now it doesnt work, it crashes as soon as I open it.
    Cant open it. Cleared data, rebooted, no luck. Reinstalled previous magisk apk but its not detecting magisk installed.
    Any ideas?
    Welcome to the party!
    Please read the last 13 posts before yours.
  • 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
    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
    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