Magisk General Support / Discussion

Search This thread

J.Michael

Recognized Contributor
Jan 20, 2018
1,105
1,043
Samsung Galaxy Tab A series
“E:[libfs_mgr]Error updating for slotselect”

Maybe this recovery mode warning is the cause. Any ideas?
Does the Magisk Manager say yours is an A/B device?
I have never seen a reference to selecting a slot with Odin.

Have you checked the forums for the A51 5G?
Or, do you know enough about both devices to know that A51 is nothing like A52?
 

AndrzejDwo

Senior Member
May 26, 2018
1,070
754
Samsung Galaxy Note 3
Samsung Galaxy S5
Been looking around but have only found Rooting guides for Android 12 on Pixel Threads.

Is there a Specific guide to root Samsung's Android 12? (Specifically the S21 Ultra)
Or are they roughly the same.
The only difference while rooting S21Ultra running Android 12 is that you need to use Magisk Canary instead of Stable version. All the rest is the same, you can even use A11 vbmeta. Take a look in s21ultra twrp/root guide and join tg group for latest twrp.

Cheers
 
  • Like
Reactions: pndwal

Fishballs

Member
Apr 27, 2017
13
4
Samsung Galaxy S21 Ultra
The only difference while rooting S21Ultra running Android 12 is that you need to use Magisk Canary instead of Stable version. All the rest is the same, you can even use A11 vbmeta. Take a look in s21ultra twrp/root guide and join tg group for latest twrp.

Cheers
Wait-
So no more Patching of AP for A12?

I didn't use TWRP to root for A11, and all this vbmeta thing confuses me.
 

AndrzejDwo

Senior Member
May 26, 2018
1,070
754
Samsung Galaxy Note 3
Samsung Galaxy S5
Wait-
So no more Patching of AP for A12?

I didn't use TWRP to root for A11, and all this vbmeta thing confuses me.
I think you can still use patched AP method (but with canary release), vbmeta gets patched during this process as well, it's nothing to get confused about. I never used patched AP method tho, rooting with custom recovery is much easier/faster imo. And I feel more confident with TWRP instead of stock recovery.
Here you have the guide:
Thread '[RECOVERY][UNOFFICIAL] TWRP for Galaxy S21 Ultra (Exynos)' https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-s21-ultra-exynos.4240993/

Cheers
 

pndwal

Senior Member
i just uninstalled magisk from the app, and my phone is just restarting and not turnin on!
Seems you have more or less fixed this in your HELP thread, but still have issues... Of course you need to provide at least some information to get help here; you basically told us "it didn't work 😫 "

From other thread I see you have Samsung phone.

FWIW, seems you missed some of the official Installation Instruction notes for Sammy:

Important Notes​

  • Never, ever try to restore either boot or recovery partitions back to stock! You can brick your device by doing so, and the only way to recover from this is to do a full Odin restore with data wipe.
  • To upgrade your device with a new firmware, NEVER directly use the stock AP tar file with reasons mentioned above. Always patch AP in the Magisk app and use that instead.
  • Never just flash only AP, or else Odin may shrink your /data filesystem size. Flash AP + BL + CP + HOME_CSC when upgrading.
The first point is your problem; either uninstall method in Magisk App restores boot image (either stock boot or recovery partition), and this doesn't work for newer Samsung devices. Seems you now need to follow the advice on recovering properly...

Please read official Installation Instruction page, especially Samsung section as Sammy procedures are quite different from standard & fraught. Hope it helps. PW
 
Last edited:
  • Like
Reactions: J.Michael

sahil_bhandari

Senior Member
Aug 14, 2021
102
10
18
Bombay
www.youtube.com
Erro when bild magisk

I defined the vars env and is using the lastest Android Sdk, but always getting erros
My system: Ubuntu 20.04.3 LTS in a Virtual box machine
my env:
ANDROID_SDK_ROOT=/root/Android/Sdk
PATH=/media/android-studio/jre/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

He is the log:

./build.py ndk && ./build.py all

  • Downloading android-ndk-r21e-linux-x86_64.zip
  • Extracting NDK zip
  • Patching static libs
  • Building the stub app
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /media/Magisk/stub/src/main/java/com/topjohnwu/magisk/DelegateComponentFactory.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
No issues found.

Output: out/stub-release.apk

  • Building binaries: magisk magiskinit magiskboot busybox
make: Warning: File 'obj/local/armeabi-v7a' has modification time 1,4 s in the future
make: *** Deleting file 'libs/armeabi-v7a/magisk'
/root/Android/Sdk/ndk/magisk/toolchains/llvm/prebuilt/linux-x86_64/bin/arm-linux-androideabi-strip:./libs/armeabi-v7a/magisk: File format not recognized
make: *** [/root/Android/Sdk/ndk/magisk/build/core/build-binary.mk:774: libs/armeabi-v7a/magisk] Error 1
make: *** Waiting for unfinished jobs....

Build binary failed!
did you managed to solve that issue please help me too
 

pndwal

Senior Member
Bit further FWIW:
Pixel testers wanted.
Confirmed by @RikkaW it can somehow be fixed by correcting vbmeta's flags. She's having Pixel 5 Android 12 rooted permanently by Magisk without cleaning userdata. We need more people to help test now...
See here:
https://github.com/topjohnwu/Magisk/issues/4343#issuecomment-981104538
and here:
https://github.com/topjohnwu/Magisk/issues/4941#issuecomment-981104664
Also, re MIUI:
https://github.com/topjohnwu/Magisk/issues/4447

Nb. PR referenced is WIP / draft ATM. PW
 
  • Like
Reactions: ipdev

Fishballs

Member
Apr 27, 2017
13
4
Samsung Galaxy S21 Ultra
I think you can still use patched AP method (but with canary release), vbmeta gets patched during this process as well, it's nothing to get confused about. I never used patched AP method tho, rooting with custom recovery is much easier/faster imo. And I feel more confident with TWRP instead of stock recovery.
Here you have the guide:
Thread '[RECOVERY][UNOFFICIAL] TWRP for Galaxy S21 Ultra (Exynos)' https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-s21-ultra-exynos.4240993/

Cheers
Thanks for the help, really appreciated.
It works, got BUKG rooted (≧▽≦)
 
  • Like
Reactions: AndrzejDwo

moocow1452

Senior Member
Nov 16, 2011
348
109
Livonia
On the latest Canary, my Oculus Go spit out a console-ramoops that was a little garbled after the Magisk installation where a previous one was much more legible. Is there a reason for that or a method to get cleaner data?
 

ipdev

Recognized Contributor
Feb 14, 2016
1,748
1
2,958
Google Nexus 10
Nexus 7 (2013)
I got little sleep last night and about to go to bed tonight.

Had a bit of a hard time following the Magisk issues linked.
I will go though them again tomorrow after more than three hours sleep.

So a one-off Magisk build including PR 4975 to test on Pixels to find out if it:
  • Allows Pixel 4a (5G) [bramble] and newer to use Magisk without disabling verity and verification on Android 12.
    No need to wipe data initially.​
  • Non-Pixel devices that share the same issue.
  • Make sure it does not break Magisk on Pixel 4a [sunfish] and older.
    Along with other devices that do not have the issue and may still be on Android 11 or below.​

Sound about correct. 🙃

Cheers. :cowboy:
 

pndwal

Senior Member
I got little sleep last night and about to go to bed tonight.

Had a bit of a hard time following the Magisk issues linked.
I will go though them again tomorrow after more than three hours sleep.

So a one-off Magisk build including PR 4975 to test on Pixels to find out if it:
  • Allows Pixel 4a (5G) [bramble] and newer to use Magisk without disabling verity and verification on Android 12.
    No need to wipe data initially.​
  • Non-Pixel devices that share the same issue.
  • Make sure it does not break Magisk on Pixel 4a [sunfish] and older.
    Along with other devices that do not have the issue and may still be on Android 11 or below.​

Sound about correct. 🙃

Cheers. :cowboy:
Good on ya doc! I was hoping some maverick Pixel user would lose some sleep to help fix this one!

Sounds like on right track, but I only took cursory glances at Pixel issues recently as I'm a Xiaomi user currently... not sure of anything, but I'm sure you're the right guy to help...

I noted that MIUI w/ related issue are all late MTK devices. 👏👍 PW
 

s3axel

Senior Member
Mine seems to be working just fine.
Using Magisk Alpha though..
Not sure if that makes the difference ouo
Thanks for your reply, is that the 23015 build ?.... just now I tried everything aside from factory reset, so that may be my last resort now..... but at least I know that it should/can work, so thats very helpful ;)
 
  • Like
Reactions: heyjoe66

Top Liked Posts

  • 1
    I figured I should post this here, and I am unsure if it is even supposed to happen. My phone is a XT1952-T, so a rebranded Moto G7 Play, and I am aware that the "bad key" and "N/A" appearing after an unlocked bootloader is normal. In my case though, these letters and numbers appear instead.

    This always happens after flashing the magisk_patched file. Sometimes it ends up corrupting the phone, and other times it lets me get through, but Magisk still says N/A on installed. I am using the correct boot.img that I pulled directly from LMSA.

    Whether I use TWRP or fastboot to flash it, this always ends up happening. I also flash the stock firmware with LMSA before flashing so that I ensure the previous test doesn't conflict with the next one. I don't ask for a fix, I am actually intrigued on why this happens, any ideas?
    Surprisingly I found out what these numbers and letters are. I am from a pretty long time ago, and only recently tried again to root. This is what I found when flashing (I should have seen this earlier tbh):


    C:\Users\Cash America\Desktop\platform-tools>fastboot flash boot magisk_patched-24300_Z6OMY.img
    (bootloader) is-logical:boot_a: not found
    Sending 'boot_a' (17661 KB) OKAY [ 0.491s]
    Writing 'boot_a' (bootloader) Image signed with key
    (bootloader) 80012A99-867FDA48-4E357816-0E549F1B-B067FBD5
    OKAY [ 0.342s]
    Finished. Total time: 6.552s


    Followed from: https://topjohnwu.github.io/Magisk/install.html#patching-images
    I did notice that the phone had "vbmeta_a" and "vbmeta_b", but didn't know what to do with them. No "vbmeta" I saw though.
    1
    Good morning, I've updated my Samsung Galaxy Tab S5e today via OTA (LOS 19.1, MiindTheGapps, Magisk 24.3).
    Although there is an addon.d script for Magisk, only the GApps were reinstalled, not Magisk. I had to do it again via adb.

    What could be the reason? File-permissions of the script are fine.
    Many factors...
    - If using TWRP, none are yet properly A12 compatible...
    - LOS recovery can't decrypt /data
    https://github.com/topjohnwu/Magisk/issues/3820#issuecomment-857241389
    - For A/B devices (i.e. addon.d-v2) the OTA must be run through the system settings updater app rather than LOS recovery
    https://github.com/topjohnwu/Magisk/issues/3820#issuecomment-857094000
    - A/B (addon.d-v2) when using TWRP may only work in certain branches (note the date here) https://github.com/topjohnwu/Magisk/issues/3820#issuecomment-856937113

    Nb. @osm0sis is the resident expert on all things addon.d (and designer of much of it) here.

    Hope this helps. 🙂 PW
  • 7
    Latest Shamiko:

    Shamiko v0.5.0

    0.5.0​

    • Better hiding Zygisk
    "... Momo enjoys helping Shamiko become stronger in all aspects despite Shamiko's goal of defeating her..."

    👍 PW
    6
    Looks like major libsu release is now imminent; most fixes are now merged.

    Should see major stability improvements in Magisk and root app implementation... Should see new commits for Magisk proper again soon too!

    John has made some major libsu changes (see libsu GitHub).

    Here are extra comments on vvb2060 fixes from her TG (Chinese translated....


    👀 PW
    libsu 5.0.0 is out!

    libsu/CHANGELOG.md

    5.0.0​

    Check the updated Javadoc and the example app for details on how to use the remote file system in the new nio module.

    New Features​

    • Introduce a new module: nio
      • Includes file system implementations for local and remote processes
      • New FileSystemManager class to access either local or remote file system implementations
      • New ExtendedFile class to extend functionality of the old Java File API
    • [core] New API Shell.isAppGrantedRoot() returns a nullable Boolean:
      • true if a root shell has been created
      • false if it has been determined that root access is impossible to get
      • null if the library has not, or could not determine the current root grant state. Future invocations of this method may return a non-null value if the library gained more information during shell creation.
    • [core] New API Shell.Builder.setContext(context): allow the developer to explicitly provide a Context object
    • [io] SuFile is updated to also extend ExtendedFile, which adds some new features and APIs

    Deprecation​

    • Version 5.0.0 will be the final release of the busybox module. If you cannot remove the usage of the module, you can pin the busybox module to version 5.0.0, as it is updated to be fully self contained, making it guaranteed to work with future libsu versions.
    • Usage of SuFile/SuFileOutputStream/SuFileInputStream/SuRandomAccessFile is discouraged. Although these APIs will remain for the foreseeable future, please migrate to use RootService + the nio module for all root I/O operations.
    • Shell.rootAccess() is deprecated. Please switch to use the more accurate Shell.isAppGrantedRoot() API

    John Wu, 2h

    Major libsu update 5.0.0!

    Introduces a new module "nio" to perform I/O operations through root services, moving away from the error prone, inefficient shell command backed I/O the library used to provide.

    It's already using splice under-the-hood. There is already some Linux magic!

    New readme etc. Read how you can Attach Debugger to Android Process in Root Services and more!
    https://github.com/topjohnwu/libsu

    👏👍🥳

    ... Back to regular Magisk programming... PW
    6
    Latest Official TJW debug Canary Magisk:

    Magisk (985249c3) (24309)​

    Pixel 6 Android 13 Beta 2 support is here!

    • [App] Support requesting root from non app process
    • [App] Fix deadlocking a background thread on non-root devices
    • [MagiskInit] Support GKIs with no ramdisk (Pixel 6 Android 13)

    Diffs to v24.3​

    • [MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)
    • [MagiskInit] Introduce new sepolicy injection mechanism
    • [MagiskInit] Support Oculus Go
    • [MagiskInit] Support GKIs with no ramdisk (Pixel 6 Android 13)
    • [App] [MagiskSU] Properly support apps using shared UID
    • [MagiskSU] Fix a possible crash in magiskd
    • [Zygisk] Fix function hooking on devices running Android 12 with old kernels
    • [BusyBox] Add workaround for devices running old kernels
    https://github.com/topjohnwu/magisk-files/blob/56da1fe5430b2c04701ce73d1658ba698ee92283/notes.md

    👍 PW
    6

    Latest Official TJW debug Canary Magisk:​

    Magisk (cc79a96f) (24307)​

    • [App] Update libsu with 100% new I/O layer
    • [MagiskInit] Mock enforce file with regular file to prevent possible race condition
    • Switch normal NDK with ONDK, preparing the toolchain to introduce Rust

    Diffs to v24.3​

    • [MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)
    • [MagiskInit] Introduce new sepolicy injection mechanism
    • [MagiskInit] Support Oculus Go
    • [App] [MagiskSU] Properly support apps using shared UID
    • [MagiskSU] Fix a possible crash in magiskd
    • [Zygisk] Fix function hooking on devices running Android 12 with old kernels
    • [BusyBox] Add workaround for devices running old kernels
    https://github.com/topjohnwu/magisk-files/blob/a66dfce1bf88a70e86bf86c5427b1c58e71a4fc2/notes.md

    👍 PW
    5

    Latest Official TJW debug Canary Magisk:​

    Magisk (42e5f515) (24308)​

    • Several minor bug fixes

    Diffs to v24.3​

    • [MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)
    • [MagiskInit] Introduce new sepolicy injection mechanism
    • [MagiskInit] Support Oculus Go
    • [App] [MagiskSU] Properly support apps using shared UID
    • [MagiskSU] Fix a possible crash in magiskd
    • [Zygisk] Fix function hooking on devices running Android 12 with old kernels
    • [BusyBox] Add workaround for devices running old kernels
    https://github.com/topjohnwu/magisk-files/blob/ba1cf1081e1fe6fce7fda626dfdb0a0faab27d4e/notes.md

    👍 PW
  • 1077
    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