Magisk General Support / Discussion

Search This thread

Riyad_

Senior Member
Jan 23, 2015
234
100
Chittagong
After installing or removing a module in magisk 22.1 when click the reboot option there is a message that show formatting data instead of rebooting. and also after that the system boot itself into recovery. i can't say its a boot loop because if reboot the device by using power key it works . Also after booted into recovery ,reboot to system also works fine. anyione facing this issue ???
 

Didgeridoohan

Forum Moderator / Developer Relations
Staff member
May 31, 2012
11,482
11,799
Gothenburg
Google Nexus 4
Nexus 6
i been traumatized with 22.0 so can i just directly install the update without extra preparation and not expecting any issue or bootloop?
You should always expect and prepare for issues and bootloops, but the most of the problems we saw with the v22.0 update should have been fixed in v22.1. This entry from the changelog is my best bet on what was causing the broken boot images we saw in the last release:
  • [App] Prevent multiple installation sessions running in parallel

I say go for it (as long as you have all your important data backed up, of course).
 

jhedfors

Senior Member
Oct 16, 2009
1,383
674
St Paul, AZ
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
Is there a replacement for the announcement thread? It hasn't been updated for a long time and I cannot find any reference to it being discontinued.
 
  • Like
Reactions: J.Michael

ashrr

Member
Apr 10, 2021
5
5
I got a notification to update to 22.1 today, pressed it and nothing happened. Tried to open the manager app and it wouldn't open so I waited 5 minutes then rebooted to see if it would fix it but bootlooped instead. I was on the latest version before updating which I think was 22.0. I've just tried flashing 22.1 again in recovery but I'm still bootlooping. Any ideas how I can fix this?
 

ineedroot69

Senior Member
  • Nov 13, 2019
    751
    1
    150
    I got a notification to update to 22.1 today, pressed it and nothing happened. Tried to open the manager app and it wouldn't open so I waited 5 minutes then rebooted to see if it would fix it but bootlooped instead. I was on the latest version before updating which I think was 22.0. I've just tried flashing 22.1 again in recovery but I'm still bootlooping. Any ideas how I can fix this?
    what do you mean by flashing? i thought only the app receive update(which is apk and can be directly installed like any other apk)

    did you just decided to download the new magisk apk and flash it instead of installing the update directly from magisk app... ohh nooo

    also perhaps youre wifi connection is slow (since it's downloading the update) should've have waited longer instead of rebooting your device
     
    Last edited:

    ashrr

    Member
    Apr 10, 2021
    5
    5
    what do you mean by flashing? i thought only the app receive update(which is apk and can be directly installed like any other apk)

    did you just decided to download the new magisk apk and flash it instead of installing the update directly from magisk app... ohh nooo

    also perhaps youre wifi connection is slow (since it's downloading the update) should've have waited longer instead of rebooting your device
    Yh renamed the apk to zip and flashed that after the normal method failed.
    I doubt it was due to a slow connection, I get about 200mb down from the room I was in. Yh I probably should've waited a bit longer but 5+ minutes is usually more than enough.
     

    ineedroot69

    Senior Member
  • Nov 13, 2019
    751
    1
    150
    Yh renamed the apk to zip and flashed that after the normal method failed.
    I doubt it was due to a slow connection, I get about 200mb down from the room I was in. Yh I probably should've waited a bit longer but 5+ minutes is usually more than enough.
    you have TWRP? just grab the partition Magisk backup and fastboot flash it
     

    JimSmith94

    Senior Member
    Jul 21, 2007
    2,745
    522
    Midlothian, TX
    I'm not 100% sure what bricked my Pixel 5 but after installing the April Security update and patching boot.img, it was stuck on the fastboot screen with no boot image on slot b. I believe it happened because I patched boot. img without checking and installing the new Magisk Manager first. UbreakIFix was unable to force flash so now I'm waiting for them to get in a new motherboard. As I said, I'm not positive this caused it, but perhaps this warning will keep someone else from doing something stupid like I did.
    I won't get my phone back until sometime next week. Before I build up the courage to root it again, can someone confirm that my patching the boot image after installing the April Security update but without checking for a Magisk Manager update first was what bricked my Pixel 5?
     
    • Like
    Reactions: J.Michael

    ashrr

    Member
    Apr 10, 2021
    5
    5
    Yh I do. Where can I find magisk backup partition? I used to flash custom roms and kernels back when I had my Nexus 4 but these days it's just stock with magisk so I'm pretty much new to this whole thing.
    Ok I'm getting nowhere. I got the backup boot.img which I extracted from /data/magisk_backup_sha1/boot.img.gz and flashed it using the command fastboot flash boot boot.img and my OP 5T just shows a white led and ends up in some diagnostic mode. I've also tried flashing the stock boot.img then flashing magisk but that didn't work either. Does anyone want to help me with some instructions a 5 year old could follow?
    I have a twrp backup from a while ago which is for the same android version but an older magisk version and I also have one with the broken boot after the failed update from 22.0 and before attempting to flash 22.1 again in twrp.

    Edit: I've gotten back into android by restoring my system backup from late 2019. I then uninstalled the broken magisk app installed 22.1 again and all is working fine. I've tried restoring the broken system image but it bootlooped again. What could be causing this? The only thing I can think of is substratum.
     
    Last edited:
    • Like
    Reactions: ineedroot69

    ineedroot69

    Senior Member
  • Nov 13, 2019
    751
    1
    150
    Ok I'm getting nowhere. I got the backup boot.img which I extracted from /data/magisk_backup_sha1/boot.img.gz and flashed it using the command fastboot flash boot boot.img and my OP 5T just shows a white led and ends up in some diagnostic mode. I've also tried flashing the stock boot.img then flashing magisk but that didn't work either. Does anyone want to help me with some instructions a 5 year old could follow?
    I have a twrp backup from a while ago which is for the same android version but an older magisk version and I also have one with the broken boot after the failed update from 22.0 and before attempting to flash 22.1 again in twrp.

    Edit: I've gotten back into android by restoring my system backup from late 2019. I then uninstalled the broken magisk app installed 22.1 again and all is working fine. I've tried restoring the broken system image but it bootlooped again. What could be causing this? The only thing I can think of is substratum.
    i previously asked that too "why is magisk called systemless when it's capable corrupting system partition" but nobody answered me i guess it's one of those question like

    Which Came First, the Chicken or the Egg?​

    nobody know thou it's better left unanswered
     

    DiamondJohn

    Recognized Contributor
    Aug 31, 2013
    5,054
    4,401
    Sydney
    i previously asked that too "why is magisk called systemless when it's capable corrupting system partition" but nobody answered me i guess it's one of those question like

    Which Came First, the Chicken or the Egg?​

    nobody know thou it's better left unanswered
    Magisk itself is not Systemlesss, in that it modifies the BOOT partition, which some would cal a "system" modification. However, technically NOT touching the SYSTEM partition.

    The "magic" of Magisk is that after that, all modifications that appear to be to the SYSTEM partition are actual achieved by systemless mods; the mods are in the DATA partition.

    Its the differentiation between BOOT and SYSTEM, and that the changes made by Magisk are systemless. Magisk is not ...errr.. "bootlesss";)
     
    Last edited:

    ineedroot69

    Senior Member
  • Nov 13, 2019
    751
    1
    150
    Magisk itself is not Systemlesss, in that it modifies the BOOT partition, which some would cal a "system" modification. However, technically NOT touching the SYSTEM partition.

    The "magic" of Magisk is that after that, all modifications that appear to be to the SYSTEM partition are actual achieved by systemless mods; the mods are in the DATA partition.

    Irs the differentiation between BOOT and SYSTEM, and that the changes made by Magisk are systemless. Magisk is not ...errr.. "bootlesss";)
    that make sense so if magisk installation got corrupted then system partion would appear to be corrupted to since magisk is symlinking or like emulating system partition
     

    DiamondJohn

    Recognized Contributor
    Aug 31, 2013
    5,054
    4,401
    Sydney
    that make sense so if magisk installation got corrupted then system partion would appear to be corrupted to since magisk is symlinking or like emulating system partition
    That could be the case, but if yur boot partition is corrupted (ie not working) then there would be no chance for your phone to work exactly; booot gets loaded before system). But also (as you stated), if the Magisk install starts making "bad" changes to tour system, then the system wont boot / operate correctly. The first step to recover from such a situation is commonly to flash back the original boot image (doing so is built into magisk), and hence remove the system changes and hopefully that will give you a working system. Or remove all your modules (ie systemless changes)

    PS: in case you haven't already, simply report your own double post to get it removed.
     

    J.Michael

    Senior Member
    Jan 20, 2018
    595
    359
    @ineedroot69 If you think you can't boot because of a Magisk module, try booting to Safe Mode. I think when you boot to Safe Mode, Magisk does not run. Then, the next time you boot, Magisk runs but does not activate any modules. At that point, you have root, so you should be able to delete or disable the modules.
     

    Iron_Overheat

    Senior Member
    Apr 13, 2016
    104
    16
    On clean flashed (fully wiped) LineageOS 18.1, Xiaomi Mi A1, v22.1, the app didn't work initially after flashing the apk renamed as .zip (it threw an error message trying to download and install the full app after tapping it in the app drawer). I then manually installed the app by using the normal apk. Everything works fine su wise but attempting to install a module crashes the app, event though notifs say it's downloading (but doesn't install).
     

    op3tguy

    New member
    Apr 11, 2021
    2
    2
    First time here and I hope I'm asking this question in the right place.
    Oneplus 3T running OOS 9.0.6 since about Jan. 2020 with Magisk installed a long time ago.
    TWRP 3.5.2_9

    This morning there was a download for Magisk which I ignored. (Little download arrow at the top of the screen.)
    I was using the phone fine for a few hours until I got out of the car and put it in my pocket.
    10 minutes later I noticed it was hot, took it out and found it stuck at the prompt for start/recovery/bootloader etc.

    It will not complete its boot.
    I can get to TWRP, I've tried flashing v22.1 but it fails in the same way.

    ! Unsupported/Unknown image format
    - Unmounting partitions
    Updater process ended with ERROR: 1

    I've attached the dmesg.log and recovery.log if that helps.

    I have Nandroid backups from the last time (after) I upgraded to OOS 9.0.6.

    Any help would be appreciated.
     
    • Like
    Reactions: J.Michael

    Top Liked Posts

    • 7
      Which logs are helpful when devices bootloops on splash screen?

      I read https://www.didgeridoohan.com/magisk/MagiskHelp but is last_kmsg need be taken after booting to Android after flashing stock boot.img?

      I have took and posted logs by booting to TWRP. Is that a correct way?


      Thanks
      The kmsg (Kernel Message) file is constantly written to while booted into an Android environment.
      System or Recovery.

      A new kmsg file is created every time you boot the device into an Android environment.
      The previous kmsg file is moved to last_kmsg

      Both files are replaced each time you (re)boot into an Android environment.

      Example.

      You boot into system and get stuck at the splash screen.
      Your device is currently writing to /proc/kmsg

      You force a reboot into recovery.
      The previous /proc/kmsg was moved to /proc/last_kmsg
      Your device is currently writing to /proc/kmsg

      /proc/kmsg is now the current recovery boot
      Your previous boot into system is now /proc/last_kmsg

      If you now reboot from recovery into recovery again.
      The previous /proc/kmsg is moved to /proc/last_kmsg
      Your device is currently writing to /proc/kmsg file.​

      /proc/kmsg is now the current recovery boot
      Your previous boot into recovery is now /proc/last_kmsg


      Note:
      • Newer devices use /sys/fs/pstore instead of /proc/last_kmsg
      • You normally need heightened privileges (root) to grab kmsg or pstore.
        A custom recovery normally allows you root access.

      Hope it helps more than confuse. 🙃

      Cheers. :cowboy:
      4
      The kmsg (Kernel Message) file is constantly written to while booted into an Android environment.
      System or Recovery.

      A new kmsg file is created every time you boot the device into an Android environment.
      The previous kmsg file is moved to last_kmsg
      ...snip...
      And there is also the magisk boot log method, which I think from memory is basically just a logcat during boot, and is more if you can boot normal before it fails. More info at @Didgeridoohan web site:
      3
      Hi everyone, I'm using OP7 pro (10.0.10). Magisk was working fine before today; however, I tried updating my magisk manager to 22.1 and now I can't open magisk manager - first time I open the app, the magisk logo appears then disappears and nothing happens; second time I open it says "magisk keeps stopping".



      I googled around and tried to: a) restart my phone, b) clear cache and/or storage, c) try to use magisk manager without wifi/data, but none of them worked.



      Google pay still works and rooted apps like titanium backup still work (although "magisk manager keeps stopping" pops up, I can use the rooted apps).



      Is there any way I can fix this without losing my data and my root? Thanks
      Make sure you find in Settings, Apps the old Magisk Manager (or however you renamed if hiding) and ununstall.
      If needed uninstall and reinstall also the new Magisk app.
      You will not loose Magisk root, modules, hide etc
      3
      Hey guys, my phone xiaomi Mi 11 pro has rooted succes with magisk 22.1 ver. But it's only "youtube vanced" working, Mixplorer newest ver not work athough it's has permission. It's cant modify system/root.
      Anyone know how to solve that problem?

      sorry for my bad English.
      If you have a newer device (Which it sounds like you do), then your system is mounted as Read-Only, and basically can not be changed to RW. Thats how newer android on newer devices, runs
      2
      Aside from trying Canary Magisk (not sure if you did), might be worth waiting for next Stable build. Seem to be quite a few fixes already committed to be merged... PW
      What puzzles me is that even after un-rooting I had the bootloop, and only applying Magisk 20.3 fixed it.
      Also saw a popup when checking Magisk App that Magisk 22.1 app doesn't give support to Magisk <20.4 (I had 20.3), which could have been the problem from the start.

      When I manage to have some time to fiddle more with Magisk, I will try updating to Magisk20.4 via TWRP and try again, this time with the next Stable Magisk version of course (which I hope doesn't drop support for 20.4 🤞).

      About Canary, I didn't even consider it, since I couldn't afford the risk of doing anything that could potentially do even more damage as I was still trying to understand what was happening first and taking only affordable risks if possible. While I consider I can defend myself on bash, I lack the Andoid's ecosystem knowledge that could let me know what went wrong and that kind of stuff, so thanks ipdev for summarizing it, it will be really helpful in case I run again into trouble :).

      Have a nice day!
    • 12

      Latest Public (Stable / Beta)

      Release Notes and Changelog:


      2021.4.9 Magisk v22.1​

      This release is focused on fixing regressions and bugs. Check the v22.0 release notes if coming from older releases.

      Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 will only support Android 5.0 and higher.

      Bug Fixes​

      • [App] Prevent multiple installation sessions running in parallel
      • [App] Prevent OutOfMemory crashes when checking boot signature on PXA boot images
      • [General] Proper cgroup migration implementation
      • [General] Rewrite log writer from scratch, should resolve any crashes and deadlocks
      • [General] Many scripts updates fixing regressions
      • [MagiskHide] Prevent possible deadlock when signal arrives
      • [MagiskHide] Partial match process names if necessary
      • [MagiskBoot] Preserve and patch AVB 2.0 structures/headers in boot images
      • [MagiskBoot] Properly strip out data encryption flags
      • [MagiskBoot] Prevent possible integer overflow
      • [MagiskInit] Fix sepolicy.rule mounting strategy
      • [resetprop] Always delete existing ro. props before updating. This will fix bootloops that could be caused by modifying device fingerprint properties.
      🎉 👍 PW
      11
      Latest Debug (Canary)
      Changelog and Release Notes
      https://github.com/topjohnwu/magisk-files/blob/ea57c9b33b3a6ce2e0e65ce4c33dfb1c01552fcb/notes.md :

      Magisk (f49966d8) (22103)​

      • [App] Update snet extension. This fixes SafetyNet API errors.
      • [App] Fix a bug in the stub app that causes APK installation to fail
      • [General] Fix a C++ bug that causes undefined behavior
      • [MagiskHide] Update package and process name validation logic

      Diffs to v22.1​

      • [General] Remove all pre Android 5.0 support
      • [MagiskPolicy] Remove unnecessary sepolicy rules
      • [App] Update snet extension. This fixes SafetyNet API errors.
      • [App] Fix a bug in the stub app that causes APK installation to fail
      • [General] Fix a C++ bug that causes undefined behavior
      • [MagiskHide] Update package and process name validation logic
      👍 ...And things are all Rosy 'n Safe in the Custom Mod. world once again... but ironically, only on the bleeding edge... (Confirmed on my RN8T. 🙂 )

      News for those not wanting to get cut (Public Stable / Beta users) below. 😜

      Thanks John... And other collaborators for additional fixes! PW
      9
      Update snet.jar extension
      The existing API key was revoked for some reason.
      Release an updated extension jar with a new API key.

      In addition, add some offline signature verification and change how
      results are parsed to workaround some dumbass Xposed module "faking"
      success results, since many users really don't know better.

      @topjohnwu

      topjohnwu committed 19 minutes ago
      9
      Latest Debug (Canary)
      Changelog and Release Notes
      https://github.com/topjohnwu/magisk-files/blob/56d4ca44e12927217ae761df0874e3cd7d05cea4/notes.md :

      Magisk (fb8000b5) (22104)​

      • [App] Hide annoying errors in logs when hidden as stub
      • [App] Update stub implementation
      • [App] Some internal code refactoring
      • [App] Update snet extension implementation

      Diffs to v22.1​

      • [App] Update snet extension. This fixes SafetyNet API errors.
      • [App] Fix a bug in the stub app that causes APK installation to fail
      • [App] Hide annoying errors in logs when hidden as stub
      • [General] Remove all pre Android 5.0 support
      • [MagiskPolicy] Remove unnecessary sepolicy rules
      • [General] Fix a C++ bug that causes undefined behavior
      • [MagiskHide] Update package and process name validation logic

      May fix sundry issues with Magisk App! 👍 PW
      8
      Strange how people think they don't need to read the other posts but expect that their questions should be addressed and answered😌
    • 1046
      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
      155
      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!!
      119
      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.
      74
      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
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone