Magisk General Support / Discussion

Search This thread

m0han

Senior Member
Apr 30, 2012
5,004
2,053
I'm running Magisk Delta. Zygisk enabled and Deny list properly configured, but not enforced.
i'm on the latest delta. i see no option to disable 'enforce denylist'. well, i 'removed' dlu and shamiko, rebooted, installed shamiko 0.5.1 afresh. now momo 4.3.1 does not find zygisk. but, init.rc is modified.
 

martyfender

Senior Member
Mar 9, 2017
3,269
1,750
Indianapolis, IN
yes. no option to disable 'enforce denylist'. i'm on the latest delta. the only change to the setup i had shamiko 0.5.0 on is usnf was updated to 2.3.1.

p.s.: that was my post you quoted, but the name is seen as vMAC and not m0han. how come?
I have one of my devices on the delta. I believe there is no option to disable enforce denylist because the delta includes magiskhide and with it the denylist must be enabled. I asked @huskydg this twice to clarify, but he never responded, if I recall he responded with something else.
 
I have one of my devices on the delta. I believe there is no option to disable enforce denylist because the delta includes magiskhide and with it the denylist must be enabled. I asked @huskydg this twice to clarify, but he never responded, if I recall he responded with something else.
Turning Magisk hide off acts like disabling enforce.
 

Attachments

  • Screenshot_20220628-150730_Magisk Delta.png
    Screenshot_20220628-150730_Magisk Delta.png
    229.7 KB · Views: 45
  • Screenshot_20220628-150748_Momo.png
    Screenshot_20220628-150748_Momo.png
    141.1 KB · Views: 46
  • Like
Reactions: m0han

zeppelinmad4

Senior Member
Feb 10, 2010
123
21
Jacksonville Beach, Fl
I am not sure where I am supposed to post this. I have a google pixel 6 pro rooted on android 13.3. I accidentally hit 'reboot to recovery' in magisk and I am stuck in a bootloop. I am able to get into fastboot mode but adb does not recognize my device. Device manager recognizes it as lemobile android device>android bootloader interface. I searched on here, the pixel 6 forum and just google but am not too sure what I should do. I don't know if I have a rogue module but I do not know how to uninstall it since I cannot find a twrp for the pixel 6 pro.

edit: I didn't realize it was 'fastboot devices' instead of 'adb devices'. I downloaded the android 13.3 factory image and am now installing via the 'flash-all' script. Hoping I don't run into any more problems.
 
Last edited:

martyfender

Senior Member
Mar 9, 2017
3,269
1,750
Indianapolis, IN
I had tried that and rebooted, but shamiko still showed as not working because of denylist being enforced. I will try again, with the new shamiko though.
I disabled magiskhide in the delta, installed the new shamiko and rebooted and shamiko now shows as working. Onn 8 first gen, Android 9 tablet. The latest momo only reports init.rc modified.
 
  • Like
Reactions: casouzaj and m0han

zgfg

Senior Member
Oct 10, 2016
7,619
5,024
funny thing is 'shamiko doesn't work....'.
Now reading all these recent posts about Delta, everything is pretty logical

Keywords: Delta, Alpha, old MagiskHide, DenyList missused for MagiskHide - all in all, no place for Shamiko in that context

That's why I suggested to move that discussion how to use work with Delta to the Delta specific thread
 
  • Like
Reactions: TKruzze and ipdev

zgfg

Senior Member
Oct 10, 2016
7,619
5,024
Read notes.md it will show you what version of Magisk Canary is available.
True, but for that one must be somewhat familiar with GitHub, while newbies usually are not, and then they ask how this/how that/where is what, what to click, etc

Alll downloads (Stable, Beta, Canary, Debug) are easily, on TWO CLICKS, directly accessible from the Magisk app - see post #52425
 
  • Like
Reactions: 73sydney

pndwal

Senior Member
funny thing is 'shamiko doesn't work....'.
Just to clarify:

Shamiko basically restores MagiskHide (hides root traces from apps with reverting Magisk modifications) for Zygisk Magisk builds and needs Denylist Enforced disabled so Magisk modifications are not reverted/denied for listed apps... Since Delta integrates the same function and has already 'hijacked' the denylist for hide purposes when MagiskHide is enabled (read 'In Use'), there's a conflict... Shamiko hiding and Delta hiding are not compatible... PW
 
  • Like
Reactions: 73sydney

zgfg

Senior Member
Oct 10, 2016
7,619
5,024
I was using Denylist Unmount v0.2 along with USNF V2.3.1.. Momo v4.3.1 detected Zygisk. Replaced DLU by the new Shamiko (v0.5.1). Momo doesn't see Zygisk anymore.
For me (recently I learnt it's 2SI device - whatever it means😁 - ok, 2 Stage Init), nothing changed

Latest Momo with latest Shamiko (latest USNF, DenyList disabled) on latest Canary still detects su, Magisk and Zygisk

As TJW named, mast..tion device👍
 
Last edited:
  • Like
  • Haha
Reactions: ipdev and 73sydney

pndwal

Senior Member
Related to which post exactly? In case it was mine, I read and understood every part of it.
Haha 😝... Suitably cryptic comment about fish prices...

It was in relation to
Sorry, I didn't decipher

It's Xiaomi Mi 11 Lite 5G NE, launched with MIUI 12.5, Android 11 - I didn't upgrade to A12, and running stock firmware (only Magisk and custom Recovery)

It's A/B device, with Recovery integrated to Boot, Magisk recognizes as Ramdisk Yes

2SI or not?
I answered and detailed the hallmarks of each Android boot-type (Legacy Ramdisk, Legacy SAR & 2SI "SAR"):
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-87082683

Next post:
IMG_20220629_051832.jpg

... Just don't understand what this has to do with the price of fish... It tells me nothing...

Perhaps you could explain?... 🤪 PW
 
  • Like
Reactions: dr4go

J.Michael

Recognized Contributor
Jan 20, 2018
1,256
1,195
Samsung Galaxy Tab A series
I am not sure where I am supposed to post this. I have a google pixel 6 pro rooted on android 13.3. I accidentally hit 'reboot to recovery' in magisk and I am stuck in a bootloop. I am able to get into fastboot mode but adb does not recognize my device. Device manager recognizes it as lemobile android device>android bootloader interface. I searched on here, the pixel 6 forum and just google but am not too sure what I should do. I don't know if I have a rogue module but I do not know how to uninstall it since I cannot find a twrp for the pixel 6 pro.

edit: I didn't realize it was 'fastboot devices' instead of 'adb devices'. I downloaded the android 13.3 factory image and am now installing via the 'flash-all' script. Hoping I don't run into any more problems.
Too late to be of help this time, but
I have seen people talk about using the "flash-all.bat" and they either add or delete a "-w" switch in order to *not* erase data.
 

Bouls

Member
Jun 22, 2022
9
2
Please see my last post for further explanation...


so since you seem to have this issue, you still need to do this...

Known issue, but not a regression, so no further fixes will come... (Edit: Except this one: https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-87068697 )

Basically, Direct install breaks due to previous Magisk injection method for 2SI being incompatible with new Magisk... It's more complicated in configurations where disabling verity/verification to boot is still required, but for most 2SI device users the solution is simply to do initial Patch and fasttboot flash original boot image again, thereby replacing the incompatible fstab-patched image...

🙃 PW
Bro, I formatted my data and everything and flashed disable dm verity force encrypt. After patching this file, I wasn't able to patch magisk.zip (I got the same error that I talked about in this thread."Unsupported boot image extra"). So I re-formatted my phone again and flashed magisk.zip only in twrp and it worked. But I want to disable force encryption in my device because I'm not able to access internal storage in twrp. Please I need help
 

J.Michael

Recognized Contributor
Jan 20, 2018
1,256
1,195
Samsung Galaxy Tab A series
Bro, I formatted my data and everything and flashed disable dm verity force encrypt. After patching this file, I wasn't able to patch magisk.zip (I got the same error that I talked about in this thread."Unsupported boot image extra"). So I re-formatted my phone again and flashed magisk.zip only in twrp and it worked. But I want to disable force encryption in my device because I'm not able to access internal storage in twrp. Please I need help
Search the threads again. I think, after installing TWRP, you use TWRP to wipe data. And somewhere in there you say "do not encrypt".
 

Top Liked Posts

  • 6
    Some Insight on the New Cat and Mouse Game...

    Since many are asking:
    Is there a fix for this? ... Can't pass MEETS_STRONG_INTEGRITY.
    I'm posting this WOT. 🤪

    I predict some will like it, some won't... You've been warned! 😜

    FWIW, Play Integrity MEETS_STRONG_INTEGRITY is akin to SafetyNet Evaluation type HARDWARE with CTS Profile match...

    Banks could have used this before (w/ S/N API) but haven't as it would have excluded too many users/devices/customers... Nothing has actually changed with new PI API; MEETS_STRONG_INTEGRITY will exclude the same group, so it's doubtful they'll rush to require this verdict...

    Basically, the means to enforce Hardware key-backed Attestation has already been here w/ either of these attestations, but banks don't want to exclude all those w/Android 7 and below, or many w/ broken keymaster 3+ implementations in Android 8+ devices (CTS Profile match with HARDWARE Evaluation type / MEETS_STRONG_INTEGRITY won't pass with locked bootloader), eg most OnePlus devices (nb. Keymaster may have been fixed in OnePlus devices launched with Android 12+)...

    I'm guessing the banks may well leverage this at some point if the time arrives when they feel there is a sufficient critical mass of devices w/ working hardware-backed keymaster (ie w/ hardware keystore, A8+) to trade against the number of modded (bootloader unlocked) devices in use especially if they deem Google slow to close the fallback-to-basic-attestation loophole that has allowed modders to bypass hardware based attestation to CTS Profile match enforcement (by triggering fallback to BASIC Evaluation type as well as bypassing enforcement) and also to allow its counterpart, MEETS_DEVICE_INTEGRITY verdict. (Nb. This verdict should not properly be obtained on modded devices, and it requires the same attestations as S/N as well as the same tricks to trigger fallback to BASIC attestation and bypass enforcement) The incentive to use this foolproof means is also certainly being weighed constantly against the cost / need to use their own custom means of sophisticated 'root' detection...

    Google also, as other authorities have commented, appears to be waiting for some 'acceptable' percentile / critical mass of such devices in use to be reached also, before they swing the 'big hammer' that is Hardware-backed Key Attestation enforcement and that will definitely spell the endgame for modders' use of bank apps, and possibly for OnePlus users and others whose devices have broken keymaster*

    *Nb. There are exceptions, eg Asus ROG Phone 3, where broken keymaster actually results in PI MEETS_STRONG_INTEGRITY and S/N CTS Profile match with Evaluation type HARDWARE regardless of bootloader status instead of the converse...

    It seems likely to me that OnePlus and other devices with broken keymaster can be spared if Google do prevent on-device triggering of fallbacks to basic attestation use simply by using device info contained in the cryptographic attestation sent to Google servers instead of userspace model props etc now used, to bypass enforcement at the server end. If they do this it would be a concession as modded OnePlus etc may then still be able to pass CTS Profile match / DEVICE_INTEGRITY while other modern modded devices won't...

    This would, however, be a way to swing the hammer a bit sooner, and either way, as can be seen from the above, they may be forced to do this once banks do indicate a willingness to enforce
    MEETS_STRONG_INTEGRITY in order to stop a landslide that would prevent all stock locked Android 7 and lower devices using bank apps etc... Or maybe they'll just let the landslide go and force bank app users to upgrade devices...

    Hopefully this gives some insight regarding what pressures may finally force Google to properly deploy (ie. strictly enforce) Hardware-based Key Attestation on devices that support it...

    Personally, I think Google has exercised great restraint, possibly out of some regard for the modding community since I can't see any other compelling reason not to have properly enforced CTS Profile match with HARDWARE Evaluation type where supported or Hardware attested MEETS_DEVICE_INTEGRITY sooner, unless the matter of ensuring that the API properly sees hardware identifiers (ie. these cannot be spoofed, which I believe would again require cryptographic server-side attestation that the device doesn't indicate the presence of hardware keystore) for bypassing hardware attestation enforcement in devices launched with Android 7 and earlier is proving difficult (but I'm fairly sure this mechanism will be a simple matter for Google and probably already in place)... 😛

    It may well be that Google is benevolently holding off but is using/will use MEETS_STRONG_INTEGRITY uptake data as tha natural indicator of the banks propensity for reliable HKA... My bet is that if Google doesn't have immediate plans to move to srtict HKA enforcement for MEETS_DEVICE_INTEGRITY, then they will when the banks themselves move to use the even stricter MEETS_STRONG_INTEGRITY verdict...


    👀 🤠
    4
    Honestly we are almost at the point where we should move these discussions into a standalone thread specifically for Play Integrity.
    3
    Alright so I looked a bit and had very little luck and gave up. Then I opened terminal emulator for some unrelated activity, ran su, and "device manager" stopped working. Gonna see what happens when I uninstall that...

    Worked lol shows which version is installed access to superuser tab and modules tab active haha
    Very simple (and you don't need Terninal, su, etc):
    - look into your Drawer and/or Settings/Apps and find your old hidden/renamed Magisk app
    - when you did in the past *Hide Magisk app" you were given a chance to rename it.. Hence you should know what name you gave it (default name is Setting)

    Find that app and uninstall, and reboot. You may additionally need to reinstall the new Magisk app

    If you look into this thread you will literally find hundredth of such posts and answers. Hence nothing new - before installing/updating the new Magisk app, one MUST open the OLD hidden (if he did hide it) and do "Restore Magisk app"

    Otherwise, when you install the new Magisk app, you will have a clash - new Magisk app does not see Magisk (because the old/hidden Magisk app is connected to Magisk)

    Unfortunately,v I also don't know why TJW does not acknowledge this problem and if they could not fix it, AT LEAST to make a note into the Installation instructions (I know, nobody would read☹️) and a warning into the Changelog

    Of course, he does not read this thread and he doesn't care about all the users experiencing the same problem (99% of them are not on the level to have GitHub account and to report there, and they don't bother him to his lovely Twitter🤣)
    2
    ... take chances... or take Restore the Magisk app before updating App...
    i guess you're aware about that fork not requiring 'hide/rename/restore the app before updating'... so, maybe this: https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-87272599
  • 7
    By the way, there is another thread with detailed OP instructions for the new Magisk v24/v25:

    And a thread that was opened for hiding root with the new Magisk:

    Those new threads were opened because of this old and cluttered thread.
    Unfortunately, people still report/ask here (and in parallel complain that thread is too big to read☹️)
    6
    Some Insight on the New Cat and Mouse Game...

    Since many are asking:
    Is there a fix for this? ... Can't pass MEETS_STRONG_INTEGRITY.
    I'm posting this WOT. 🤪

    I predict some will like it, some won't... You've been warned! 😜

    FWIW, Play Integrity MEETS_STRONG_INTEGRITY is akin to SafetyNet Evaluation type HARDWARE with CTS Profile match...

    Banks could have used this before (w/ S/N API) but haven't as it would have excluded too many users/devices/customers... Nothing has actually changed with new PI API; MEETS_STRONG_INTEGRITY will exclude the same group, so it's doubtful they'll rush to require this verdict...

    Basically, the means to enforce Hardware key-backed Attestation has already been here w/ either of these attestations, but banks don't want to exclude all those w/Android 7 and below, or many w/ broken keymaster 3+ implementations in Android 8+ devices (CTS Profile match with HARDWARE Evaluation type / MEETS_STRONG_INTEGRITY won't pass with locked bootloader), eg most OnePlus devices (nb. Keymaster may have been fixed in OnePlus devices launched with Android 12+)...

    I'm guessing the banks may well leverage this at some point if the time arrives when they feel there is a sufficient critical mass of devices w/ working hardware-backed keymaster (ie w/ hardware keystore, A8+) to trade against the number of modded (bootloader unlocked) devices in use especially if they deem Google slow to close the fallback-to-basic-attestation loophole that has allowed modders to bypass hardware based attestation to CTS Profile match enforcement (by triggering fallback to BASIC Evaluation type as well as bypassing enforcement) and also to allow its counterpart, MEETS_DEVICE_INTEGRITY verdict. (Nb. This verdict should not properly be obtained on modded devices, and it requires the same attestations as S/N as well as the same tricks to trigger fallback to BASIC attestation and bypass enforcement) The incentive to use this foolproof means is also certainly being weighed constantly against the cost / need to use their own custom means of sophisticated 'root' detection...

    Google also, as other authorities have commented, appears to be waiting for some 'acceptable' percentile / critical mass of such devices in use to be reached also, before they swing the 'big hammer' that is Hardware-backed Key Attestation enforcement and that will definitely spell the endgame for modders' use of bank apps, and possibly for OnePlus users and others whose devices have broken keymaster*

    *Nb. There are exceptions, eg Asus ROG Phone 3, where broken keymaster actually results in PI MEETS_STRONG_INTEGRITY and S/N CTS Profile match with Evaluation type HARDWARE regardless of bootloader status instead of the converse...

    It seems likely to me that OnePlus and other devices with broken keymaster can be spared if Google do prevent on-device triggering of fallbacks to basic attestation use simply by using device info contained in the cryptographic attestation sent to Google servers instead of userspace model props etc now used, to bypass enforcement at the server end. If they do this it would be a concession as modded OnePlus etc may then still be able to pass CTS Profile match / DEVICE_INTEGRITY while other modern modded devices won't...

    This would, however, be a way to swing the hammer a bit sooner, and either way, as can be seen from the above, they may be forced to do this once banks do indicate a willingness to enforce
    MEETS_STRONG_INTEGRITY in order to stop a landslide that would prevent all stock locked Android 7 and lower devices using bank apps etc... Or maybe they'll just let the landslide go and force bank app users to upgrade devices...

    Hopefully this gives some insight regarding what pressures may finally force Google to properly deploy (ie. strictly enforce) Hardware-based Key Attestation on devices that support it...

    Personally, I think Google has exercised great restraint, possibly out of some regard for the modding community since I can't see any other compelling reason not to have properly enforced CTS Profile match with HARDWARE Evaluation type where supported or Hardware attested MEETS_DEVICE_INTEGRITY sooner, unless the matter of ensuring that the API properly sees hardware identifiers (ie. these cannot be spoofed, which I believe would again require cryptographic server-side attestation that the device doesn't indicate the presence of hardware keystore) for bypassing hardware attestation enforcement in devices launched with Android 7 and earlier is proving difficult (but I'm fairly sure this mechanism will be a simple matter for Google and probably already in place)... 😛

    It may well be that Google is benevolently holding off but is using/will use MEETS_STRONG_INTEGRITY uptake data as tha natural indicator of the banks propensity for reliable HKA... My bet is that if Google doesn't have immediate plans to move to srtict HKA enforcement for MEETS_DEVICE_INTEGRITY, then they will when the banks themselves move to use the even stricter MEETS_STRONG_INTEGRITY verdict...


    👀 🤠
    6
    Its trivial to sniff or even MITM a desktop, or even just run WinPE and reset admin password and use the users own saved passwords in their browser, heck even export their passwords....

    In any event the biggest risk vector is social engineering

    Chasing root phone users only gives them a "feelgood", it does nothing to stop genuine misuse and fraud, at all.....

    I dont see Google or a bank sending out a representative every time someone makes a transaction to see if theyre genuine....trying to control the device is attacking the wrong end of the transaction and is ultimately pointless
    They're not chasing root users. They just want a guarantee that the device is secure, and they have good reason to. Rooting by nature compromises device security.

    I'm not saying your opinion is invalid; in this context however, it is irrelevant, because regardless of how you may feel about the situation, it's not going to change.
    5
    @pndwal You can build Magisk app with custom name and label as you want
    MagiskHide is still effective to hide root from banking apps. It's not dead if you don't care about safetynet stuff.


    Shamiko is taking off your panties on the basic of MagiskHide. So MagiskHide is still better.
    You believe Shamiko too much, It can't really hide zygisk, only fix the zygisk detection of Momo. However, I can't blame it because that was the nature of zygisk and it will never be fixed.
    Still not sure what you're trying to tell me...

    I think we agree on most of this stuff (except your apparent impression that Shamiko Devs have some sort of sexual agenda, or that it's users are somehow prone to 'self abuse'... I won't use the other term either...).

    If you think I have misrepresented any facts regarding Magisk, Shamiko or other, please say it plainly... I think what I provided for the sake of clarity was accurate... 🙁 PW
    5
    Latest Official TJW public Stable (release) Magisk build:

    Magisk

    2022.7.20 Magisk v25.2​

    Maintenance release fixing various issues.
    • [MagiskInit] Fix a potential issue when stub cpio is used
    • [MagiskInit] Fix reboot to recovery when stub cpio is used
    • [MagiskInit] Fix sepolicy.rules symlink for rootfs devices
    • [General] Better data encryption detection
    • [General] Move the whole logging infrastructure into Rust

    Full Changelog: here

    https://topjohnwu.github.io/Magisk/releases/25200.html

    🎉🎊 PW
  • 1084
    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