• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

Magisk General Support / Discussion

Search This thread

pndwal

Senior Member
Yeah, im 100% sure it started when i installed magisk.
The problem is not that i cant connect to a network, i cant even turn on Wifi to even at least scan for networks.
Mobile Data seems to connect but doesnt provide internet!

Im on Global MIUI 12.0.5.0


EDIT: I Downloaded the offical ROM from Xaomis Site and Patched and Flashed it and its still not working :/
Bit further:
WiFi issues w/ Magisk are usually a result of flashing mismatched patched boot image. (Search closed GitHub issues.)

I noticed latest MIUI for Mi 9T Global Stable appears to be V12.0.8.0.QFJMIXM, as of 2021-04-13.
https://xiaomifirmwareupdater.com/miui/davinci/

Mi 9T EEA is V12.0.5.0.QFJEUXM, and V12.0.5.0 is latest for other variants also.

Mi 9T Global Stable V12.0.5.0.QFJMIXM came out in 2020-10-10.
https://xiaomifirmwareupdater.com/archive/miui/davinci/

Please make sure both current ROM (Global MIUI 12.0.5.0 ?) and boot.img you patched / flashed is actually Mi 9T Global variant as well as same version (build); These must normally be an exact match, especially because boot image contains the kernel which must be compatible with system...

Otherwise, consider updating to Mi 9T Global Stable V12.0.8.0.QFJMIXM, (Nb. Mi 9T Global Stable Beta (Recovery type) V12.1.2.0.RFJMIXM Android 11.0 ROM is another available option) and be sure to extract / patch / flash boot image from this also. PW
 
Last edited:

pndwal

Senior Member
Some early news

Latest @vvb2060 Magisk Alpha build (June 23, 2021) change log:​

Chinese Translated:

alpha update log​

Magisk (1eb83ad8-alpha)​

  • Based on 1eb83ad8, please refer to the upstream update log for related modifications
  • Properly process any data from magiskd
  • Support SharedUserId
  • Delete the backup file after restoring the boot image
  • Built-in current version update log
  • Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline
  • Support bootimg v4 format
  • Support bootconfig
  • Detect /data/adb/magisk/ not updated and prompt to repair
Edit:
Following are new commits:
  • Remove the disabled and pending deletion marks when upgrading the module, and it is not allowed to mark as pending deletion before restarting
  • Fix that it cannot be flashed in some TWRP
  • Modify the search order of the module sepolicy location and fix the problem that some devices do not load the module sepolicy
  • Listen to the PACKAGE_FULLY_REMOVED broadcast to remove completely uninstalled apps from magiskhide
  • Display the modal waiting pop-up window when hiding/restore the Magisk application
https://github.com/vvb2060/Magisk/b...af4f3d37e69/app/src/main/res/raw/changelog.md

My earlier notes:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85098469

Current notes:

[It seems this build is only partially rolled out 3hrs ago, and magisk_files repo is not yet updated with package files.] Repo us now updated! Check 'earlier notes' for installation method / details.

I am not expecting Alpha build users will see Update button notice in Magisk App for this build (as with last build) as Version has (again) NOT been changed from "1eb83ad8-alpha". Again, I'm not sure if this is intended.

[I'll be sure to update here when package files have been uploaded.] Now updated as mentioned above.

Edit: Package already available on Telegram:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85229385
See post after next for details.

Interestingly, in Magisk Documentation, @vvb2060 has updated "Internal Details" (Delete wrong info) and "Deployment"
(Add exploit conditions).
https://github.com/vvb2060/Magisk/tree/alpha/docs

😛 PW
 
Last edited:

pndwal

Senior Member
Some early news

Nb. It seems Lite builds will likely be of interest only to those wanting basic superuser privileges, and a way to hide root from bank apps that detect isolated processes, at least at this stage:

Latest @vvb2060 Magisk Lite build (June 23, 2021) change log:​

Chinese Translated:

Magisk Lite​

In Magisk in the whitelist mode, all applications are hidden by default, and only the applications ticked in Hide can obtain super user permissions. adb shell automatically has super user privileges. Module function is not available.

'magiskhide add UID package name' to add super-user application
'magiskhide rm UID package name' to remove super-user application
'magiskhide ls' lists the super-user applications

Magisk (1eb83ad8-lite)​

  • Based on 1eb83ad8, please refer to the upstream update log for related modifications
  • Properly process any data from magiskd
  • Support SharedUserId
  • Delete the backup file after restoring the boot image
  • Built-in current version update log
  • Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline
  • Support bootimg v4 format
  • Support bootconfig
  • Detect /data/adb/magisk/ not updated and prompt to repair
Edit:
Following are new commits:
  • Remove the disabled and pending deletion marks when upgrading the module, and it is not allowed to mark as pending deletion before restarting
  • Fix that it cannot be flashed in some TWRP
  • Modify the search order of the module sepolicy location and fix the problem that some devices do not load the module sepolicy
  • Display the modal waiting pop-up window when hiding/restore the Magisk application
https://github.com/vvb2060/Magisk/b...a1bc0ad2802/app/src/main/res/raw/changelog.md

My earlier notes:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85082149

Current notes:

This seems to be only partially rolled out 1hr ago, and magisk_files repo is not yet updated with package files.

I'll be sure to update here when package files have been uploaded.

😛 PW
 
Last edited:

pndwal

Senior Member
Magisk Alpha

Ok, I've updated mine.

All went fine for me.

Don't expect 'Update' notice in App as mentioned, even for Magisk (mask) after App update as version has (again) NOT been changed from "1eb83ad8-alpha". Again, I'm not sure if this is intended.

[After App update, you will notice different Release Notes Changelog in Chinese for Install Magisk (mask) and Install App. Expect Install App Changelog to be updated when release package (plus json) is pushed to GitHub repository.] It's now pushed / in sync with latest.

[At present, latest package file is still not pushed to GitHub repository.] It is now available from GitHub also.

I now understand this is often released earlier to Magisk Alpha Telegram group, and sure enough it's there! (It seems Chinese community there is more aware / informed of these builds than XDA community):
https://t.me/magiskalpha
Web based preview:
https://t.me/s/magiskalpha

Nb. See this for Devs notes also.

Nb.2. In Chrome, web based preview can be translated into English.

Magisk Lite

For anyone interested in this (those wanting basic superuser privileges, and a way to hide root from bank apps that detect isolated processes), this is released to Magisk Lite Telegram group also, but latest is unavailable as yet. 😕 :
https://t.me/magisklite
Web based preview:
https://t.me/s/magisklite

Nb. See this for Devs notes / working theory / difference with respect to standard Alpha / technical details re use, functionality etc.

Eg. Dec 4 build "restores the module function and can install a separate lite module.
Requirement: After the boot is complete, zygote and its child processes will no longer read any files mounted by the module.
(Otherwise, the mobile phone will have various inexplicable problems.)"

👍 PW
 
Last edited:

pndwal

Senior Member
Since I'm unwell presently, I've been killing time checking recent commits in Alpha that may help with device compatibility issues.

One is "Support bootimg v4 format" which has been refined again in current build.

Within the commit I found interesting information on the various ramdisk types. Thought I'd share:
The vendor ramdisk section is consist of multiple ramdisk images concatenated one after another, and vendor_ramdisk_size is the size of the section, which is the total size of all the ramdisks included in the vendor boot image.

The vendor ramdisk table holds the size, offset, type, name and hardware identifiers of each ramdisk. The type field denotes the type of its content.

The vendor ramdisk names are unique. The hardware identifiers are specified in the board_id field in each table entry. The board_id field is consist of a vector of unsigned integer words, and the encoding scheme is defined by the hardware vendor.

For the different type of ramdisks, there are:
- VENDOR_RAMDISK_TYPE_NONE indicates the value is unspecified.
- VENDOR_RAMDISK_TYPE_PLATFORM ramdisks contain platform specific bits, so the bootloader should always load these into memory.
- VENDOR_RAMDISK_TYPE_RECOVERY ramdisks contain recovery resources, so the bootloader should load these when booting into recovery.
- VENDOR_RAMDISK_TYPE_DLKM ramdisks contain dynamic loadable kernel modules.
https://github.com/vvb2060/Magisk/commit/2bdd553f03a0e3989c277332e64d3f4b24f2f396

🤓 PW
 
Last edited:
  • Like
Reactions: duttyend

zgfg

Senior Member
Oct 10, 2016
5,497
2,841
Magisk Alpha

Ok, I've updated mine.

All went fine for me.

Don't expect 'Update' notice in App as mentioned, even for Magisk (mask) after App update as version has (again) NOT been changed from "1eb83ad8-alpha". Again, I'm not sure if this is intended.

After App update, you will notice different Release Notes Changelog in Chinese for Install Magisk (mask) and Install App. Expect Install App Changelog to be updated when release package (plus json) is pushed to GitHub repository.

At present, package file is still not pushed to GitHub repository.

I now understand this is often released earlier to Magisk Alpha Telegram group, and sure enough it's there! (It seems Chinese community there is more aware / informed of these builds than XDA community):
https://t.me/magiskalpha
Web based preview:
https://t.me/s/magiskalpha

Nb. See this for Devs notes also.

Nb.2. In Chrome, web based preview can be translated into English.
Since I'm unwell presently, I've been killing time checking recent commits in Alpha that may help with device compatibility issues.

Hopefully, you are doing better (must not be that bad since you are playing with Chinese Alpha👍)

Thanks for the info. Updated also my Alpha (app and Magisk) to that June 23 build from Telegram, everything as you described

Mixed filings:
- good there are updates
- good there is a support group (although only Telegram and on Chinese)
- hoping he will update to his Magisk Repo
- hoping there will be better updating scheme in the future (updated version number, updating via Alpha channel, notifications)
- hoping there will be a Github Issues tracker or so
 
  • Like
Reactions: duttyend and pndwal

pndwal

Senior Member
Re. MagiskHide / bank apps / isolated processes, John Wu said in Aug 2020:
John Wu, Aug 26, 2020

It's no secret that services with isolatedProcess enabled can easily bypass MagiskHide. People started to find out that it's quite common to be able to bypass it by simply disabling said services. Apps like Servicely can do this, do you want Magisk Manager to natively support it?

- Yes, that would be handly - 89.5%
- Nah, no moar bloat plz - 10.5%
-1,472 votes - Final results

Note that *real* solutions for hiding isolated services require either (a) Magisk-lite, aka hide by default, mount if whitelisted, or (b) hook into zygote to alter some code.

(a) will not be officially considered since this will break some modules, (b) requires a lot of work
www.twitter.com/topjohnwu/status/1298468244596985856

So there's a tip for you MagiskHiders - try Servicely! (Controls for rooted phones.)

Among other functions, "You can also disable/enable permanently any service on your device. It's useful if you have services that tend to auto-restart and keep your device awake, or if you have games sending you never-ending notifications."
https://play.google.com/store/apps/details?id=com.franco.servicely

...And we've all heard of this Dev's (@franciscofranco's)
'Franco Kernel Manager'... And he just may need some love from XDA members ATM...

Gotta love Kernel Franco's response to that Twitter post too! 🙂

I don't think we ever got 'disable services with isolatedProcess' feature, and while John did have ambitious plans to (b) 'hook into zygote to alter some code', who knows where we're at with that now?!

That leaves (a) 'Magisk-lite, aka hide by default, mount if whitelisted', which 'will not be officially considered since this will break some modules'...

This was clearly a reference to the Magisk-lite project @vvb2060 had been working on since May 2020.

In Lite, with Magisk in whitelist mode, all applications are hidden by default and only checked applications can obtain super user permissions.

It has to be said that despite the fact builds since Dec. restore "the module function and can install a separate lite module", there are still significant problems with this. As the Dev makes clear (Chinese translated):
About modules:

The Lite version does not provide support for modules. Due to the implementation principle, many modules cannot operate normally.

Technically speaking, in Magisk-Lite, files replaced or added by modules do not exist for zygote and its sub-processes (ie application processes) after the boot is completed. If a module requires these processes to read mounted files after booting, this module will cause system problems.

In order to prevent incompatible modules from damaging the system after switching from the official version, Lite has modified the module directory and the module needs to be reinstalled.

If there is a module that cannot be installed normally, cannot run normally, or causes system problems after installation, no matter how seemingly unrelated the problems, it means that the module is not compatible.

Finally, to reiterate, the Lite version does not provide support for modules.
https://t.me/s/magisklite

So it seems a way to have our cake and eat it too (ie to hide isolated process leaks from bank apps detecting them, and have normal Magisk Module functionality) is a long way off yet... However, there are still a number of things desperate bankers can try before resorting to guns! 😜

And hopefully this clarifies a few things regarding Magisk Lite. 😷 PW
 
Last edited:

zgfg

Senior Member
Oct 10, 2016
5,497
2,841
Hopefully, you are doing better (must not be that bad since you are playing with Chinese Alpha👍)

Thanks for the info. Updated also my Alpha (app and Magisk) to that June 23 build from Telegram, everything as you described

Mixed filings:
- good there are updates
- good there is a support group (although only Telegram and on Chinese)
- hoping he will update to his Magisk Repo
- hoping there will be better updating scheme in the future (updated version number, updating via Alpha channel, notifications)
- hoping there will be a Github Issues tracker or so
One more observation. With Aplha (both Jun 23 and previous May 29 builds), I can manage Magisk Hide for com.miui.security.center (MIUU Security app) through the Magisk app

It used to work also in Canary, but since v22 or v23, TJW disabled for some system apps (it was possible only through Terminal by magiskhide add/rm/ls CLI commands)

Btw, does Netflix need to be enabled in Magisk Hide?
 

Attachments

  • IMG_20210624_100753.jpg
    IMG_20210624_100753.jpg
    259 KB · Views: 48
Last edited:
  • Like
Reactions: duttyend

handy1977

New member
Jun 23, 2021
4
0
[HELP] Google pay won't work s9 plus I installed magisk on s9 plus. It won't let me use Google pay says your phone is rooted. Anyway to get the app to work. Android 10 magisk 23.

I have enabled hide and installed props config latest still i am getting phone is rooted on Google pay app.
Cts failed Eval basic Basicintegrity pass


[URL unfurl="true"]https://ibb.co/tDC4jq0[/URL]


[URL unfurl="true"]https://ibb.co/GJhZNKX[/URL]

Here some images show my settings and safetynet test EvalType Basic
 

handy1977

New member
Jun 23, 2021
4
0
Some early news

Nb. It seems Lite builds will likely be of interest only to those wanting basic superuser privileges, and a way to hide root from bank apps that detect isolated processes, at least at this stage:

Latest @vvb2060 Magisk Lite build (June 23, 2021) change log:​

Chinese Translated:

Magisk Lite​

In Magisk in the whitelist mode, all applications are hidden by default, and only the applications ticked in Hide can obtain super user permissions. adb shell automatically has super user privileges. Module function is not available.

'magiskhide add UID package name' to add super-user application
'magiskhide rm UID package name' to remove super-user application
'magiskhide ls' lists the super-user applications

Magisk (1eb83ad8-lite)​

  • Based on 1eb83ad8, please refer to the upstream update log for related modifications
  • Properly process any data from magiskd
  • Support SharedUserId
  • Delete the backup file after restoring the boot image
  • Built-in current version update log
  • Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline
  • Support bootimg v4 format
  • Support bootconfig
  • Detect /data/adb/magisk/ not updated and prompt to repair
Edit:
Following are new commits:
  • Remove the disabled and pending deletion marks when upgrading the module, and it is not allowed to mark as pending deletion before restarting
  • Fix that it cannot be flashed in some TWRP
  • Modify the search order of the module sepolicy location and fix the problem that some devices do not load the module sepolicy
  • Display the modal waiting pop-up window when hiding/restore the Magisk application
https://github.com/vvb2060/Magisk/blob/lite/app/src/main/res/raw/changelog.md

My earlier notes:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85082149

Current notes:

This seems to be only partially rolled out 1hr ago, and magisk_files repo is not yet updated with package files.

I'll be sure to update here when package files have been uploaded.

😛 PW
Hi how do we download file. I see no links on the page
 

pndwal

Senior Member
Hopefully, you are doing better (must not be that bad since you are playing with Chinese Alpha👍)
Feel lousy but panadols help. Had lite cold but still got pfizer round II... Probably a bad move. Thanks for asking. 😷
Thanks for the info. Updated also my Alpha (app and Magisk) to that June 23 build from Telegram, everything as you described

Mixed filings:
- good there are updates
Yep, best thing. 👍
- good there is a support group (although only Telegram and on Chinese)
Might need to learn Chinese... at least it's Simplified Chinese! 😃
- hoping he will update to his Magisk Repo
I'm sure he will, but probably not a priority. Seems Telegram may be his official Release medium.
- hoping there will be better updating scheme in the future (updated version number, updating via Alpha channel, notifications)
Well he recently fixed commit for that:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85194479
So it appears he wants it to work.

The explanation for it not occuring now seems to be that he has named builds for the last commit synced from John Wu's master branch each time he builds.

These have all differed untill recently, but the last of John's commits was
https://github.com/vvb2060/Magisk/commit/1eb83ad812e75e775d8cd178a7a3832029cc9607 (Update Android Studio), and this has remained static since mid May.

The first 8 digits of this, 1eb83ad8, appended with '-alpha' has predictably constituted the version code for the last 3 builds, but I'm certain he could alter this protocol easily.

I imagine he will, but don't know why he hasn't yet.
- hoping there will be a Github Issues tracker or so
Yeah, but I don't know about the propriety of (or the need for) that as long as these are unofficial builds.

Actually, @vvb2060, along with @osmosis and others, have been responding to official Issues on John's GitHub since John's gone AWOL... Of course, he actually designed aspects of it, including the auto-close bot!

I'm also sure people will continue to submit issues here for the meantime, and @vvb2060 will continue to comment, create fixes and test them in his own builds as well as implement pull requests from John's GitHub in his own just as he has been doing for a year or so now.

I don't think the fact that fixes aren't presently being merged in John's builds is a real problem. Many fixes (for MTK etc) were working for / tested by users in @vvb2060's builds long before being accepted / merged into John's.

@vvb2060's close-issue bot may be a problem; users will need to report latest Canary build to get a foot in as things stand. 🙁 ... Perhaps he could tweak that?

And pull requests can still be submitted for merging in John's... And we can still hold our breath! 😛 PW
 
Last edited:

pndwal

Senior Member
Hi how do we download file. I see no links on the page
Like I said,
magisk_files repo is not yet updated with package files.

I'll be sure to update here when package files have been uploaded.
But what good will Lite do you? It breaks modules as explained... And it's entirely unnecessary for G Pay.

G Pay detects only Play Protect certification (ctsProfile/basicIntegrity SafetyNet API) currently, certainly not Isolated process leaks.

If you want to update later than official Magisk, use Magisk Alpha. PW
 
Last edited:
  • Like
Reactions: 73sydney

zgfg

Senior Member
Oct 10, 2016
5,497
2,841
Magisk Lite

For anyone interested in this (those wanting basic superuser privileges, and a way to hide root from bank apps that detect isolated processes), this is released to Magisk Lite Telegram group also, but is unavailable as yet. 😕 :
https://t.me/magisklite
Web based preview:
https://t.me/s/magisklite

👍 PW

Hi how do we download file. I see no links on the page
In today's posts from @pndwall (above) find a link to the Llite Telegram channel:

Open in Chrome, translate, locate the post with app-release.apk from May 15, click on (it will open Telegram app) and then Save to Download (just checked, checksum is the same as when I previously downloaded directly from vvb2060's Lite Github page - link and download instructions were also in an pndwall's earlier post from the beginning of June)

Since Jun 2, I did couple of tests by installing the Lite and testing the modules with (additional tricks to make many modules to DO work, but some did not) and posted about 3-4 times here to the Magisk XDA thread

Currently I'm back to Alpha (latest from the Telegram, Jun 23 build)
 
Last edited:

pndwal

Senior Member
[HELP] Google pay won't work s9 plus I installed magisk on s9 plus. It won't let me use Google pay says your phone is rooted. Anyway to get the app to work. Android 10 magisk 23.

I have enabled hide and installed props config latest still i am getting phone is rooted on Google pay app.
Cts failed Eval basic Basicintegrity pass


[URL unfurl="true"]https://ibb.co/tDC4jq0[/URL]


[URL unfurl="true"]https://ibb.co/GJhZNKX[/URL]

Here some images show my settings and safetynet test EvalType Basic
Failed SafetyNet and Play Protect 'Device is not certified' (PlayStore Settings) is your problem, aside from far too many processes hidden (search here; this causes instability).

Assuming your ROM is stock, a SafetyNet Fix module should be all that is needed, aside from toggling off all unnecessary apps in MagiskHide list, toggle off Google Play Services too, then toggle off and on again MagiskHide in App Settings and recheck Google Play Services in Hide list (only one process should be selected now, com.google.android.gms.unstable SafetyNet process). Only that and hide Google Pay app is needed to fix GPay detection. (Don't add extra processes within apps). Also, clear data in Google Play Services, Google Play Store and Google Pay after that.

Back to initial setup:
Universal SafetyNet Fix Magisk module
https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
will probably fix ctsProfile fail and work for you, but most Sammy users have issues with it. It's probably not the best available solution for 'heavily skinned' OS's like One UI as it will most likely break biometric authentication or other functions, and destabilize system because customised Keystore has been replaced with AOSP one.

A newer (experimental) fix from the same dev (shims the keystore service instead of replacing it) is now working for Sammy users (confirmed to fix S20 issues) and others with:
- some 32-bit ARM devices
- Heavy OEM skins
- Samsung One UI
- MIUI (needed for some variants only)
- Broken biometric authentication in apps
- Unstable system (i.e. rebooting and/or crashing)

Link (read OP here):
https://github.com/kdrag0n/safetynet-fix/pull/13#issuecomment-767863635

S9 users still report problems with this, but additional working module variations for several specific devices are found in the closed issues mentioned / linked from PR thread above. I think you'll find a modified fix for your Sammy in this post or elsewhere in this long issue thread:
https://github.com/kdrag0n/safetynet-fix/issues/6#issuecomment-764129632
Be aware, these solutions use Keystores from specific OneUI versions.

Happy reading! PW
 
Last edited:

pndwal

Senior Member
Btw, does Netflix need to be enabled in Magisk Hide?
This I'm unsure of.

Seems many use sideloaded package for Netflix, and I got confused about claims re. split apks using (cloning?) Play Services, non- detection, etc. I suspect the reports vary due to many unorthodox setups.

All I know is that my PlayStore loaded Netflix shows, installs and opens fine with SafetyNet / PlayProtect passing on my setup on stock Magisk Alpha rooted RN8T (w/ Riru-MomoHider and Universal SafetyNet Fix modules), and root is NOT yet hidden from Netflix in MagiskHide list.

I don't have a subscription so haven't tested further, but I doubt (I'm guessing of course) I'd have issues.

Further, my understanding is that since Netflix 5.0, the real issue may be Widevine (DRM) TEE, a different TEE to the one SafetyNet uses. Netflix said at the time:
With our latest 5.0 release, we now fully rely on the Widevine DRM provided by Google; therefore, many devices that are not Google-certified or have been altered will no longer work with our latest app and those users will no longer see the Netflix app in the Play Store.

I just checked DRM Info app, and it's reporting Widevine CDM security is L1 for HDCP 2.3, so happily it seems that's not seeing bootloader unlock etc, and I'm good for 4K streaming! PW
 
Last edited:
  • Like
Reactions: ipdev and Wolfcity

bradical711

Senior Member
Aug 26, 2017
405
253
Google Pixel 4 XL
I have used Netflix for a year plus now with no issues and I've never once hidden Netflix in magisk hide itself. (Although I do have the magisk app hidden and pass safetynet). My Netflix app shows 'L1' meaning I can stream Full HD as well as download my shows. So hide doesn't need to be enabled for the app itself but you do need to be able to pass safetynet as well as have the specs for "L1" AKA 'HD streaming' or more so 'DRM'. If Netflix appears in your playstore (because of passing safetynet), that's all you need to run and update the app. Nextflix just wants money and that's why you can also sideload the app, not have proper DRM management (L3) and still watch Netflix in low resolution.. obviously no downloads of shows/direct updates but that's at the cost of Netflix not knowing the device is secure. My device is a Pixel 4 XL, A11 June Stock ROM with custom kernel, magisk, 9 modules and passing safetynet. But no Xposed variants in my module selection.
 
Last edited:

zgfg

Senior Member
Oct 10, 2016
5,497
2,841
This I'm unsure of.

Seems many use sideloaded package for Netflix, and I got confused about claims re. split apks using (cloning?) Play Services, non- detection, etc. I suspect the reports vary due to many unorthodox setups.

All I know is that my PlayStore loaded Netflix shows, installs and opens fine with SafetyNet / PlayProtect passing on my setup on stock Magisk Alpha rooted RN8T (w/ Riru-MomoHider and Universal SafetyNet Fix modules), and root is NOT yet hidden from Netflix in MagiskHide list.

I don't have a subscription so haven't tested further, but I doubt (I'm guessing of course) I'd have issues.

Further, my understanding is that since Netflix 5.0, the real issue may be Widevine (DRM) TEE, a different TEE to the one SafetyNet uses. Netflix said at the time:

I just checked DRM Info app, and it's reporting Widevine CDM security is L1 for HDCP 2.3, so happily it seems that's not seeing bootloader unlock etc, and I'm good for 4K streaming! PW
For my Mi 9T with Xiaomi.eu A11 weeklies, DRM L1 certificate was already supported (screenshots)

Also, USNF is built-in to the ROM (to force eval type Basic, to let it pass CTS Profile attest), hence I don't need/use any particular module to pass SafetyNet (my Magisk Alpha app is also not repackaged)

Device is Certified (and Play Protect is ok), therefore I just regularly downloaded and installed Netflix from the Google Play

Before running the app I enabled MagiskHide for Netflix and then I configured the given Netflix account

Actually, I have a shared account with Standard subscription, hence without Ultra HD 4K support (my Mi 9T screen resolution is 1080x2340 hence also less than 4K)

Streaming works fine and Netflix Playback Specification shows L1, Full HD (screenshot)

Edit:
I have used Netflix for a year plus now with no issues and I've never once hidden Netflix in magisk hide itself. (Although I do have the magisk app hidden and pass safetynet). My Netflix app shows 'L1' meaning I can stream Full HD as well as download my shows. So hide doesn't need to be enabled for the app itself but you do need to be able to pass safetynet as well as have the specs for "L1" AKA 'HD streaming' or more so 'DRM'. If Netflix appears in your playstore (because of passing safetynet), that's all you need to run and update the app. Nextflix just wants money and that's why you can also sideload the app, not have proper DRM management (L3) and still watch Netflix in low resolution.. obviously no downloads of shows/direct updates but that's at the cost of Netflix not knowing the device is secure. My device is a Pixel 4 XL, A11 June Stock ROM with custom kernel, magisk, 9 modules and passing safetynet. But no Xposed variants in my module selection.

Thanks, I have removed Netflix now from MagiskHide, and it continues to stream with L1, Full HD
 

Attachments

  • DRM_Info-Widevine_L1.jpg
    DRM_Info-Widevine_L1.jpg
    207.8 KB · Views: 50
  • Widewine_L1-Certificate.jpg
    Widewine_L1-Certificate.jpg
    169.6 KB · Views: 50
  • Netflix-PlaybackSpec.jpg
    Netflix-PlaybackSpec.jpg
    234.8 KB · Views: 50
Last edited:

pndwal

Senior Member
Let the conspiracy theories begin (again) :)

I liked you better when you were just being an awful Magisk Alpha tease a few days ago :p :p :p

Who's teasing?... But I'll bite.

👴🏻🧸👴🏻🧸👴🏻🧸👴🏻🧸👴🏻🧸👴🏻🧸

I try to stick to facts (especially those fostering any sort of hope), as that was... And up to date Magisk. 😛

Why stir? There's plenty doing that... and better ways! 😜

And this is not PlaySchool mate! PW

images (3).jpeg

Nb. Any perceived likeness to individuals depicted here is regretted, and the author is truly sorry... for the bear concerned, that is.

🐻🐻🐻🐻🐻🐻🐻🐻🐻🐻🐻🐻
 
Last edited:
  • Like
Reactions: 73sydney

Top Liked Posts

  • 4
    New topic/problem, probably discussed here before but in six hours of searching/trying things I'm unable to get Magisk installed on Pixel 5 after updating to August update. I forgot (I'm 80 yo, so am allowed to do that!) to delete/uninstall the few modules I had installed which is probably the cause of the boot loops after flashing "magisk_patched-23000_v5rmk.img". I've uninstalled everything, rebooted, installed Magisk Manager, patched boot image and flashed, etc. several times but can't get Magisk installed. Fortunately, I am able to flash the stock boot.img and get back to a working phone, but nothing I've tried has gotten Magisk to install.

    I did try the "open a shell and type: adb wait-for-device shell magisk --remove-modules" but nothing was found at that stage.

    Any and all suggestions appreciated!
    Yes, it was asked/answered several times but let it be answered again 🤩

    Besides adb, there are two other ways of disabling (or even uninstalling) the remained modules

    You have to flash your patched boot.img, then

    a) Reboott to Android Safe mode, then reboot again to 'normal' mode.
    All modules will be disabled but also you will have to re-enable Magisk Hide again

    b) Use TWRP (if appropriate for your device), Advanced, File Manager, go to /data/adb/modules and to each folder (foder = module, you can recognize modules by folder names or by reading the textual file module.prop you will find inside) put a file that must be named: disable (exactly as that)

    Then, Magisk will disable the modules and you can manage them from Magisk app (emable or uninstall)

    You can find it also in a chapter about the modules in Magisk Wiki, available from Magisk Github (linked from Magisk apo)
    3
    New topic/problem, probably discussed here before but in six hours of searching/trying things I'm unable to get Magisk installed on Pixel 5 after updating to August update. I forgot (I'm 80 yo, so am allowed to do that!) to delete/uninstall the few modules I had installed which is probably the cause of the boot loops after flashing "magisk_patched-23000_v5rmk.img". I've uninstalled everything, rebooted, installed Magisk Manager, patched boot image and flashed, etc. several times but can't get Magisk installed. Fortunately, I am able to flash the stock boot.img and get back to a working phone, but nothing I've tried has gotten Magisk to install.

    I did try the "open a shell and type: adb wait-for-device shell magisk --remove-modules" but nothing was found at that stage.

    Any and all suggestions appreciated!
    Assuming you are sure you are patching image from updated ROM now in use, if you still have bootloop after flashing this I'd simply try boot to Safe Mode mentioned above to disable modules. Compatible modules can be enabled again later, others removed.

    Also, did you have Magisk App/Manager hidden previously? If so, Magisk is likely actually installed despite N/A showing as long as flashing Magisk-patched image succeeded.

    Especially if coming from pre 22.0, you need to UnHide / restore Magisk Manager before updating Manager / App.
    https://topjohnwu.github.io/Magisk/releases/22000.html

    In practice, failure to do this has also been an issue even updating from later 'compatible' builds.

    Now, you simply need to remove hidden Manager app (found in device settings, Manage apps, likely named 'settings' if you didn't chose a custom name) as well as new App, then reinstall new App to overcome conflicts / initialise App properly.

    Settings / modules etc are safe (don't run Uninstall options from within App or TWRP). PW
    3
    If you still have bootloop after flashing Magisk-patched image, I'd simply try boot to Safe Mode mentioned above to disable modules. Compatible modules can be enabled again later, others removed.

    Also, did you have Magisk App/Manager hidden previously? If so, Magisk is likely actually installed despite N/A showing as long as flashing Magisk-patched image succeeded.

    Especially if coming from pre 22.0, you need to UnHide / restore Magisk Manager before updating Manager / App.
    https://topjohnwu.github.io/Magisk/releases/22000.html

    In practice, failure to do this has also been an issue even updating from later 'compatible' builds.

    Now, you simply need to remove hidden Manager app (search and find) as well as new App, then reinstall new App to overcome conflicts / initialise App properly.

    Settings / modules etc are safe (don't run Uninstall options from within App or TWRP). PW
    No, I didn't have Magisk hidden. Thanks for all your support here! I recognize you and @zgfg from an issue I had several years ago!
    2
    New topic/problem, probably discussed here before but in six hours of searching/trying things I'm unable to get Magisk installed on Pixel 5 after updating to August update. I forgot (I'm 80 yo, so am allowed to do that!) to delete/uninstall the few modules I had installed which is probably the cause of the boot loops after flashing "magisk_patched-23000_v5rmk.img". I've uninstalled everything, rebooted, installed Magisk Manager, patched boot image and flashed, etc. several times but can't get Magisk installed. Fortunately, I am able to flash the stock boot.img and get back to a working phone, but nothing I've tried has gotten Magisk to install.

    I did try the "open a shell and type: adb wait-for-device shell magisk --remove-modules" but nothing was found at that stage.

    Any and all suggestions appreciated!
    2
    Yes, it was asked/answered several times but let it be answered again 🤩

    Besides adb, there are two other ways of disabling (or even uninstalling) the remained modules

    You have to flash your patched boot.img, then

    a) Reboot to Android Safe mode, then reboot again to 'normal' mode.
    All modules will be disabled but also you will have to re-enable Magisk Hide again

    b) Use TWRP (if appropriate for your device), Advanced, File Manager, go to /data/adb/modules and to each folder (foder = module, you can recognize modules by folder names or by reading the textual file module.prop you will find inside) put a file that must be named: disable (exactly as that)

    Then, Magisk will disable the modules and you can manage them from Magisk app (enable or uninstall)

    You can find it also in a chapter about the modules in Magisk Wiki, available from Magisk Github (linked from Magisk apo)
    I'll give "a" a try in the morning. It's a Pixel 5 - no TWRP unfortunately (I still miss it even after three Pixel phones!). Thanks for all your support here!
  • 9

    Latest @vvb2060 Magisk Alpha build (July 18, 2021) changelog:​

    Chinese Translated:

    alpha update log​

    Magisk (1eb83ad8-alpha-19)​

    • Based on 1eb83ad8, please refer to the upstream update log for related modifications
    • Properly process any data from magiskd
    • Support SharedUserId
    • Delete the backup file after restoring the boot image
    • Built-in current version update log
    • Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline
    • Support bootimg v4 format
    • Support bootconfig
    • Detect /data/adb/magisk/ not updated and prompt to repair
    • Remove the disabled and pending deletion marks when upgrading the module, and it is not allowed to mark as pending deletion before restarting
    • Fix that it cannot be flashed in some TWRP
    • Modify the search order of the module sepolicy location and fix the problem that some devices do not load the module sepolicy
    • Listen to the PACKAGE_FULLY_REMOVED broadcast to remove completely uninstalled apps from magiskhide
    • Display a modal waiting pop-up window when hiding/restore the Magisk application
    Edit: The following are new commits:
    • App adapted to Android 12
    • Android 12+ super user hides the screen overlay when the window pops up
    https://github.com/vvb2060/Magisk/b...73bce50fe5e/app/src/main/res/raw/changelog.md

    My earlier notes:
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85098469

    Current notes:

    magisk_files repo is now updated! Check 'earlier notes' for installation method / details.

    Alpha build users won't yet see Update button notice in Magisk App for this build as VersionCode has (again) NOT changed from 23001.

    I'm not sure if this behaviour will be addressed, but users will observe the 'Latest' version (1eb83ad8-alpha-19) now differs from 'Installed' (1eb83ad8-alpha).

    Package is now also uploaded to Telegram group.
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85229385

    Interestingly, in Magisk Documentation, @vvb2060 has updated "Internal Details" and "Deployment" since John did.
    https://github.com/vvb2060/Magisk/tree/alpha/docs

    😛 PW
    8
    reddit link shared by John Wu:
    reddit post

    Especially interesting a comment by the leader of the Android Security team:
    (I lead the Android Hardware-backed security team, so while this response isn't official, it's informed. Do keep in mind that I am a programmer, not a lawyer, and I have not consulted with legal, so don't rely on this as any sort of legal advice. Nor did I run this by PR, so if I put my foot in my mouth, it's totally on me. This is not an official Google communication, and I may get my hand slapped for it. Probably not, but it's happened to me in the past :) ).

    I know of no legal issues here. AFAIK, you're free to do what you like with your device. Doing these sorts of things may invalidate your warranty, depending on the details, but I'm guessing you already know that and have decided you're fine with it.

    What I do know is that if you've found a vulnerability, Google would not only like to hear about it, Google may pay you for it. If you're compromising the TEE or kernel on a Pixel device, the reward could be up to $250,000. If you're compromising the Titan M, up to $1,000,000. Even if your current exploit isn't on a Pixel device, if you can make it work on a Pixel you would qualify. Alternatively, your device manufacturer may have their own bug bounty program and you should look.

    Obviously, if you report the vuln, what we're going to do is to fix it, so you'll lose your SafetyNet bypass. The same will happen if you publish it for others to use. Vulnerabilities that allow SafetyNet bypass typically compromise far more than just SafetyNet, which is why Google is willing to pay so much money to identify and fix them. Also, we really believe that app developers should be able to find out if they're running on a "stock" device, with all of the security and functionality guarantees that implies, so fixing SafetyNet bypasses is important in and of itself.

    It's not that we don't like custom ROMs or rooting, in fact we find a lot of the innovation that takes place in the community very interesting and eagerly adopt good ideas we find there, but our primary focus is on protecting the 99.9% of Android users who run stock Android, and the developers who serve them. It's an unfortunate but unavoidable reality that this sometimes disadvantages ROM users. I, personally, have been holding regular meetings with various leaders in the modding community for seven years now, to get their feedback and to give them a heads up on security features we implement that might pose problems for them. My goals are to both serve the main Android userbase of some 3B people and to avoid harming the modding community. Sadly, sometimes those goals conflict, and the modders obviously lose in those cases.

    I also want to address the comments about John Wu joining Google. He is perfectly capable of communicating his own intentions and goals so I won't try to do that. I'll just say that I have no interest in shutting down Magisk. To the degree that it enables people to bypass Android security guarantees, that just shows that we have work to do, indeed it helps us to identify where we need to do that work. It's not like Magisk can somehow create vulnerabilities (it's not magic). If vulns exist, they're certain to be found and exploited by people with nefarious goals, so it's better for everyone if there's a healthy "white hat" community focused on finding problems and reporting or publishing them. I see the Magisk community as part of that white hat community, and John as a valuable contributor to Android security even before he started working for Google.
    8
    @pndwal and @ipdev

    I saw you guys did some testing on the mysterious reinstallation of an uninstalled Magisk app on a reboot. I present you with the changelog for Magisk v16.6:
    [Daemon] Check whether a valid Magisk Manager is installed on boot, if not, install stub APK embedded in magiskinit
    :p
    7

    Early Notice:​

    Latest @vvb2060 Magisk Alpha build (July 23, 2021) changelog:​

    Skipped a few due to rapid-fire! (This guy's a bit like Jorrit!)

    Chinese Translated:

    alpha update log​

    Magisk (1eb83ad8-alpha-23)​

    • Based on 1eb83ad8, please refer to the upstream update log for related modifications
    • Properly process any data from magiskd
    • Support SharedUserId
    • Delete the backup file after restoring the boot image
    • Built-in current version update log
    • Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline
    • Support bootimg v4 format
    • Support bootconfig
    • Detect /data/adb/magisk/ not updated and prompt to repair
    • Remove the disabled and pending deletion marks when upgrading the module, and it is not allowed to mark as pending deletion before restarting
    • Fix that it cannot be flashed in some TWRP
    • Modify the search order of the module sepolicy location and fix the problem that some devices do not load the module sepolicy
    • Listen to the PACKAGE_FULLY_REMOVED broadcast to remove completely uninstalled apps from magiskhide
    • Display the modal waiting pop-up window when hiding/restore the Magisk application
    • App adapted to Android 12
    • Android 12+ super user hides the screen overlay when the window pops up
    Edit: New changes since 1eb83ad8-alpha-19
    • For devices supported by the kernel, MagiskSU uses proprietary devpts to bypass some application detection
    • Rewrite MagiskSU's pty opening logic, no additional sepolicy rules are needed
    • Fix incorrect signal sending in MagiskHide
    • Add untrusted_app_30
    https://github.com/vvb2060/Magisk/b...e147e578c92/app/src/main/res/raw/changelog.md

    My earlier notes:
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85098469

    Current notes:

    Check 'earlier notes' for installation method / details.

    Alpha build users won't yet see Update button notice in Magisk App for this build as VersionCode has (again) NOT changed from 23001.

    I'm not sure if this behaviour will be addressed, but users will observe the 'Latest' and 'Installed' version suffix now differs.

    This build has not been uploaded at the time of this post. Watch this space!

    Latest in GitHub magisk_files repo is 1eb83ad8-alpha-20

    Latest available from Telegram group is
    1eb83ad8-alpha-22
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85229385

    Interestingly, in Magisk Documentation, @vvb2060 has updated "Internal Details" and "Deployment" since John did.
    https://github.com/vvb2060/Magisk/tree/alpha/docs

    🤠 PW
    7
    Tried using https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk after it was already rooted with Magisk, but adb said [INSTALL_FAILED_VERSION_DOWNGRADE]
    Just use Magisk/Canary button on Magisk GitHub home page to get app. Opens
    This is latest 23001

    Nb. Your link (where did you get that??) is to latest Canary in old archived magisk_files repo (note '_', not '-') so it's fetching 22003, ie. you would be trying to downgrade from 23000, and to downgrade you need to uninstall 23000 first, as with any app downgrade. 😜

    Nb. Regular app installation from device should work fine, then Direct install to update (or downgrade) Magisk should be available / work.
    Well golly, the whole reason I was trying to use canary was to file a bug report, but if nobody is maintaining it, then there's no point. Thanks for letting me know!
    Wouldn't say no point however.

    Magisk contributors (there are 201) like @osmosis (especially) and @vvb2060 are still distilling / fixing issues, and responding to many issues, as are other informed / experienced users. Many workarounds / non-integrated solutions have been supplied.

    Further, as has been noted, many fixes from topjohnwu Magisk Issues have been incorporated in vvb2060's Alpha builds (seems these go back at least to Dec 2018. Archived builds from Dec 2020 are available on his GitHub & Telegram) before merging in John Wu's.

    I doubt this will change, and vvb2060 has produced several builds since John's last ones already! This is the beauty of such an open source project. Links, latest etc:
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85226785

    It would be a misunderstanding to say only John is supplying fixes for Magisk Issues, just as he is not (any longer at least) its sole developer!
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85127113

    Nb. John already pretty much turned over current App design / fixes to @diareuse so he could concentrate on Magisk Mask itself:
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-83637567

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

    Clearly the issue of official builds continuing (in present form or other) is up-in-the-air atm, but a healthy / active / interested community still exists. 🙂 PW
  • 1057
    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