Magisk General Support / Discussion

Search This thread

Spartacus500

Senior Member
Nov 6, 2014
781
153
I removed Magisk root in recovery with uninstall.zip, and nothing completely solved the problem, still TB checker open error ... I have no idea 😔
 

m0han

Senior Member
Apr 30, 2012
5,797
2,890
OnePlus 11

Attachments

  • Screenshot_20230403-114023_Soul.png
    Screenshot_20230403-114023_Soul.png
    118.5 KB · Views: 40
  • Like
Reactions: J.Michael

Erfirya

Member
Aug 20, 2022
18
9
The link doesn't work. Since you had sought help here and seem to have fixed it yourself, it would be in the fairness of things that you share the 'fix' here so that others are also enlightened.
My problem was with LSPosed module. It was displaying "SEPolicy is not loaded properly", "Partially activated" in the manager. The problem was caused by Magisk or a cleared partition. So I had to disable/re-enable the module and reboot. After booting it was fixed.
 
  • Like
Reactions: J.Michael

Feduz

Senior Member
Jun 1, 2014
130
18
OnePlus 8T
I've updated my OnePlus 8T (A13) as always to KB2003_11_F.63. But I cannot be able to modify/update the hosts file (via LP to block ads), tried also with terminal but I cannot modify hosts file properties. I've flashed also via Magisk "systemless hosts - unified" by gloeyisk but with no success. Any tips to verify which is the problem?
 
Last edited:
  • Like
Reactions: BillGoss

zgfg

Senior Member
Oct 10, 2016
9,646
7,510
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11
I've updated my OnePlus 8T (A13) as always to KB2003_11_F.63. But I cannot be able to modify/update the hosts file (via LP to block ads), tried also with terminal but I cannot modify hosts file properties. I've flashed also via Magisk "systemless hosts - unified" by gloeyisk but with no success. Any tips to verify which is the problem?
On A13 and earlier, System is READ-ONLY on the file system level, you can not make any changes on the system partitions

If not familiar with and with the systemless root concept (present in Magisk since 2021 or so), please search, read back, study, there were tons of similar questions and answers

Eg, how AdAway+Systemless hosts mechanism works - no hard changes on the /system/etc/hosts file, Magisk mounts changes on every reboot

Etc, etc. The way how all systemless modules work
 
  • Like
Reactions: vpvfi and J.Michael

Feduz

Senior Member
Jun 1, 2014
130
18
OnePlus 8T
On A13 and earlier, System is READ-ONLY on the file system level, you can not make any changes on the system partitions

If not familiar with and with the systemless root concept (present in Magisk since 2021 or so), please search, read back, study, there were tons of similar questions and answers

Eg, how AdAway+Systemless hosts mechanism works - no hard changes on the /system/etc/hosts file, Magisk mounts changes on every reboot

Etc, etc. The way how all systemless modules work

I've always used Magisk with systemless, also on A13 until 2 days ago. I think it's changed something
 

zgfg

Senior Member
Oct 10, 2016
9,646
7,510
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11
I've always used Magisk with systemless, also on A13 until 2 days ago. I think it's changed something
In the first post you wrote:
"But I cannot be able to modify/update the hosts file (via LP to block ads), tried also with terminal but I cannot modify hosts file properties"

That's not systemless approach but hard changes that are not possible on the read-only System As Root (SAR)
 
  • Like
Reactions: J.Michael

Feduz

Senior Member
Jun 1, 2014
130
18
OnePlus 8T
In the first post you wrote:
"But I cannot be able to modify/update the hosts file (via LP to block ads), tried also with terminal but I cannot modify hosts file properties"

That's not systemless approach but hard changes that are not possible on the read-only System As Root (SAR)
yes I've tried also manually to modify (didn't know that was not possible). Then everytime I've used LP that patch/update (I don't know how) the hosts file adding the new lines to block ads, but after this new update seems changed some logic
 

zgfg

Senior Member
Oct 10, 2016
9,646
7,510
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11
yes I've tried also manually to modify (didn't know that was not possible). Then everytime I've used LP that patch/update (I don't know how) the hosts file adding the new lines to block ads, but after this new update seems changed some logic
So again, this Google's concept with read-only System is not new, we all live with that here since 2021 or so (depending on devices, ROMs, Android version, etc). And the corresponding systemless root was introduced to Magisk way back to provide the method to overcome the problem

If it hit you just now, then good (or bad) for you - but you will need to read about, learn and to live with that...

Sorry, it's not a short story to explain you now what can you do, etc, in few lines. Everything what is needed can be found in this thread, AdAway thread, etc

Btw, do not use Magisk Canary 25210, you will never make Systemless hosts (and many other modules) to work - but that was also extensively covered in the posts here during the last three weeks
 
  • Like
Reactions: J.Michael

Feduz

Senior Member
Jun 1, 2014
130
18
OnePlus 8T
So again, this Google's concept with read-only System is not new, we all live with that here since 2021 or so (depending on devices, ROMs, Android version, etc). And the corresponding systemless root was introduced to Magisk way back to provide the method to overcome the problem

If it hit you just now, then good (or bad) for you - but you will need to read about, learn and to live with that...

Sorry, it's not a short story to explain you now what can you do, etc, in few lines. Everything what is needed can be found in this thread, AdAway thread, etc

Btw, do not use Magisk Canary 25210, you will never make Systemless hosts (and many other modules) to work - but that was also extensively covered in the posts here during the last three weeks
So maybe it's the latest version the problem, is there a procedure to go back to a previous one?
 

pndwal

Senior Member
So maybe it's the latest version the problem, is there a procedure to go back to a previous one?
Without going into detail, 25207 was a bit broken and 25208 worse... some fixes came with 25209 but (livable) issues remain... 25210 was badly broken...

Easy method to roll back (bypass downgrade prevention while retaining root):
Rename 25209 or 25206 .apk to .zip and flash as a module from Magisk App and reboot... Uninstall 25210 Magisk App, then install proper (25209 or 25206) .apk package.

👍 PW
 

J.Michael

Recognized Contributor
Jan 20, 2018
2,072
2,467
Samsung Galaxy Tab A series
So maybe it's the latest version the problem, is there a procedure to go back to a previous one?
Try to understand what you are fixing before you try to fix it.

Make sure you are really doing, now, what you used to do.

When you "edit" a hosts file, exactly what file do you edit? The full path matters.

If you used to get away with editing /system/etc/hosts, you will probably have to change your procedure.

If you used to edit /data/adb/adaway/system/etc/hosts and then reboot:
  • if you forgot, and tried to edit /system/etc/hosts, just go back to doing it the right way
  • if you did exactly that this time, and it's not working, read about the Magisk versions that are not working -- *now* is the time to "roll back" Magisk
What is "LP", and what does it have to do with Adaway?
 
  • Like
Reactions: jons99

Top Liked Posts

  • 3
    It was the stable version 26.3 through a direct install from stable 25.2. I looked through logs and no error whatsoever came up so I doubt the modules had anything to do with it.
    I think that 25.2 to 26.3 is a big enough jump that there have been problems, but they usually prevent booting.

    Still, it couldn't hurt for you to restore your stock system, then manually patch and flash using Magisk manager app 26.3 to patch.

    Let us know if your SIM card behaves any better.
    2
    I've installed LineageOS on my OnePlus 3T. Then I've installed Magisk according to Magisk Installation Instructions. My phone does haven't separated vbmeta partition. So, I checked "Patch vbmeta" option

    After every LineageOS update, I patched boot.img and checked "Patch vbmeta" option

    And now, in latest Magisk release I have not seen this option, when trying to patch boot.img.

    What should I do now? Does Magisk now can determintate that vbmeta partition doesnt exist?
    1
    Updating to Magisk 26.3 disabled my unlocked phone's ability to read my SIM card, so now it gives me Invalid SIM card or SIM card not detected
    Issues like that are classic symptoms of mismatched boot.img, eg user updates ROM then flashes previously patched boot.img... Many system updates require corresponding changes in kernel which resides in boot.img... PW

    Please say how you updated (how boot.img was obtained)... and did you update ROM also? PW
    1
    It was the stable version 26.3 through a direct install from stable 25.2. I looked through logs and no error whatsoever came up so I doubt the modules had anything to do with it.
    Again, what is youe phone/ROM? Things like that are important and you still omitting to provide the info

    Eg, if some Pixel, better use PF app for installing/updating Magisk, specially if the model/ROM requires patching init_boot

    Does Magisk app show Randisk No on top - if so, it has been mentioned here several times that before Direct install (or also before patching the boot img !!!), user should disable Recovery option (yes, that's a known bug in v26.3)
    1
    Just to make sure... Did you test your SIM card is working on another phone, and that another SIM card is not working on yours?
    Yes I literally walked into a T MOBILE store and the employee put the same sim card into a display phone and it worked normally, even that same phone showing up on my T-Mobile account
  • 9
    Latest Magisk Stable:
    Release Notes

    2023.9.4 Magisk v26.3​

    v26.3​

    • [General] Fix device information detection script
    • [General] Update BusyBox to 1.36.1
    • [General] Update toolchain that produces broken arm32 executables
    • [App] Fix root service unable to bind on OnePlus devices
    https://topjohnwu.github.io/Magisk/releases/26300.html

    👍 PW
    8
    I consider it to be unfair to define "modder" or "developer" as "anyone who dumps partitions/nandroid".
    <SNIP>

    <SNIP>
    Since it's not available without unlocking, 'anyone who dumps partitions / performs nandroid' has to agree to modify the device by unlocking which changes original product features including disabling security functions and other features... Then they generally install a custom (modified) recovery...😆
    <SNIP>
    I miss the days when I could just use adb to dump the data partition into an image file and flash it back. 😿️

    Better yet, when I could wipe system, install a different OS version and leave userdata alone.
    [The original Clean/Dirty flash install.] 🙃️

    As for the Cat and Mouse game...

    My money is on the Mice. 😜️
    "Look, sorry - are we talking about the little white furry things with the cheese fixation and women standing on tables screaming in early sixties sit coms?"

    Slartibartfast coughed politely.

    "These creatures you call mice, you see, they are not quite as they appear. They are merely the protrusion into our dimension of vast hyperintelligent pandimensional beings. The whole business with the cheese and the squeaking is just a front."
    ― Douglas Adams, The Hitchhiker's Guide to the Galaxy

    Cheers all. :cowboy:

    PS.
    I miss FlashFire.
    😥️
    8
    This illustrates why I always want to be able to use a device upon which TWRP (or perhaps OrangeFox) is functional. As long as I've taken a proper full nandroid backup of a previous working system, I can easily nandroid-restore that working system after an upgrade, if I wish.

    I am not happy with Google for continuing to "enhance" (ha ha!) Android as time goes on,
    Yeah... And Microsoft should have stayed with DOS, and maybe Windows as a DOS add-on!...
    thereby making it more and more difficult to get TWRP and OrangeFox working with newer Android versions.
    That's certainly NOT their intention...

    There's a lot to be said for new innovations and OEM requirements both in the mart of competitive commerce and for the value -added benefits to general Android users...

    Just as a few examples,
    • SAR/2SI enhancements allow for A/B partitioning and 'seamless' (streamed) delta OTA updates,
    • Shared blocks architecture allows for dynamic sup-super partitions which may be RO but are resizable with no unused space, upgradable to larger /system etc in future and space optimised/saving etc,
    • Project Treble (Android 8+)
    https://www.xda-developers.com/goog...ze-android-so-oems-can-update-devices-faster/
    modularised Android so that OEMs can serve Android updates more quickly by reducing OEM dependence on SoC vendors for every single OS update and introduced a new 'vendor interface' and Vendor Test Suite (VTS)... It also facilitated
    • The GSI Project (Android 9+)
    https://developer.android.com/topic/generic-system-image
    which allows app developers to install and run the latest Android Generic System Images to perform app testing on a variety of existing Android devices, and use GSIs from different Android OS release stages... Extra benefits include:
    - Broader test coverage on a greater set of real devices
    - More time to fix app compatibility issues
    - More opportunities to fix compatibility issues in Android that are reported by app developers
    • Project Mainline (Android 10+)
    https://www.xda-developers.com/android-q-project-mainline-security/
    (modules:)
    https://www.xda-developers.com/android-project-mainline-modules-explanation/
    expands on Treble's modularisation to further address fragmentation, adding Android Pony EXpress update packages to allow updating system modules (APEX includes all needed libraries, ART, HALs and precompiled code on addition to apps) through Google Play in Android 10 and 25 new modules with A11, as well as reducing how dependent Google is on OEMs for delivering security updates to key OS components. It also facilitated
    • The GKI Project (Android 11+)
    https://source.android.com/docs/core/architecture/kernel/generic-kernel-image
    with its Generic Kernel Image is an essential change aimed addressing the issue/costs of fragmentation which "has several negative effects on the Android community". GKI/Mainline reductions in fragmentation thus:
    - Make security updates less labor intensive
    - Allow merging Long-Term Supported updates
    - Removes factors that Inhibit Android platform release upgrades
    - Allows easier contribution of kernel changes back to upstream Linux

    So Treble and Mainline, with their GSI and GKI changes/requirements, are initiatives to facilitate easier updates for vendors, give incentive to support devices much longer, etc.

    Google is in the business of promoting it's mobile OS and producing development milestones that reduce costs, improve efficiency, lifecycle, specs etc for OEMs and end users in order to stay competitive, relevant, innovative and appealing... And they make major architectural changes for these reasons...

    They aren't in the game of "making it more and more difficult to get TWRP and OrangeFox working"; they appreciate these efforts but (quite reasonably) have the (different) priorities mentioned above...

    Just as with Magisk injection, there is much pressure on Dee's Troy and team (and other custom recovery teams) to get TWRP functioning properly, let alone to mount and decrypt user data with an ever changing Android architecture, but there are clearly more complex considerations than for simple Magisk injection... Even so, Google allows and even supports such custom mod efforts...

    Moreover it's not Google's fault that community projects like TeamWin find it difficult to devote the time, conscript the Devs or otherwise overcome obstacles needed to properly support new Android iterations... They actually supply clear documentation as part of AOSP for these changes to benefit all Android devs, whether OEMs, app makers or custom modders...

    I don't really know why TWRP has not progressed past Oct 2022 3.7.0 A12 base builds at this time despite the fact that 'Android 13 development had started' already, but the difficulty they have keeping up is not new... I note that everything there is still © 2014 to 2022, also that:
    TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our Zulip channel or on forums like xda-developers.
    https://twrp.me/about/
    and that, just as when Dees Troy lamented that 'real life' was preventing TWRP keeping pace, the four base team members are still appealing for volunteers:
    We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
    -----​

    Despite the difficulty the TWRP four have keeping up with the Google juggernaut, apparently many devices running A13+ have at least unofficial TWRP support with working decryption. Some won't allow permanent flashing but temp booting TWRP works nonetheless, and some have other issues...

    Re devices launched with Android 13:

    Just on Thursday, Dev @Nebrassy posted a TWRP build for OnePlus 11 which is apparently working despite some niggles:
    https://forum.xda-developers.com/t/recovery-12-unofficial-teamwin-recovery-project.4625181/

    This device has dedicated /recovery_a and /recovery_b partitions and Qualcomm SoC, and the Dev doesn't even own the device...

    For Pixel 7 series, the delay getting TWRP w/ decryption working seems to be Tensor SoC / device tree syncing and possibly StrongBox / KeyMint / Titan chip implementation(?) rather than general Android Architectural changes and initiatives.

    However, just yesterday @Wishmasterflo posted a test build of OrangeFox recovery (this is "synced with the latest Teamwin changes", and originally from a Dev who later joined LineageOS) for the Pixel 7a:
    https://forum.xda-developers.com/t/...g-thats-being-worked-on.4532237/post-88986509
    Nb. The Dev cannot test ATM as his device is still locked...

    Pixel 7a users: If someone tests and this works, I'm sure custom recovery support for Pixel 7 series devices will gain momentum...

    Takers?
    -----​

    ... FWIW, some modders will experiment/toy with the latest devices / Android versions as soon as they arrive... Others will stay with old tech because of affordability but migrate ASAP... Still others will refrain as long as possible, whether out of nostalgia or for other reasons...

    Similarly, some car drivers will migrate to EVs quickly... Others will when the price point is more agreeable... Still others will refrain as long as possible, and some will hanker for the ICE age with the smell of petrol and the roar of engines long after it's gone!

    Personally, despite not being able to afford a Tesla yet, I think auto makers in general have not moved to new tech nearly fast enough!...I expect them to continue to "enhance" transportation options as time goes on however... And I cannot be unhappy when phone market leaders adapt, innovate and move with the times either...

    Just might be able to get me a 2nd hand P7Pro now that the P8's in the wind, and wire a fast-charge outlet into the dash of the ol Ford Perfect... 😜 PW
    4
    .... thereby making it more and more difficult to get TWRP and OrangeFox working with newer Android versions.

    That's certainly NOT their intention...

    I never said that I believe that to be intentional.

    It's just one of the unintended consequences of Google's continued "improvements" (ha ha!) of Android coupled with the increased usage by more and more developers of root-blocking and mod-blocking technologies.

    Yes, Google is in business to make money with its advertising dissemination and with devices and OS's and services which facilitate that. They have a right to make money in this way and in countless other ways that they might choose. And developers have the right to choose how to make money with their own apps, as well.

    It's just that Google's and many developers' Android-related products and services continue to grow increasingly unappealing to me.

    I still find Android to be less onerous than iOS, but the undesirability gap between them continues to get narrower and narrower for me.
    4
    OnePlus Users:

    Nb. Issue:
    Magisk app freezes when rooted on OOS10+OOS11 devices after commit 3938322 APP, Regression
    is fixed in 26.3 with libsu update! 🎉👍 PW
  • 1100
    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