Magisk General Support / Discussion

Search This thread

timg11

Senior Member
Jul 20, 2010
198
22
Google Pixel 3 XL
Google Pixel 5
I have Titanium version 8.3.2. SE Linux is enforcing.

I installed "The SELinux Switch" and changed to Permissive.
MyBackupPro now is able to restore backups, but Titanium Backup still hangs on restore.
I tried all the TiBk options for App processing mode:
  • Auto Direct - hangs with spinning circle forever
  • Auto Indirect - hangs with spinning circle forever
  • Interactive - first displays "There Was A Problem Parsing The Package”, then hangs with spinning circle forever

What else should I look at? Are there some specific Magisk Modules that are needed for TiBk?
What else have you done other than install Magisk, and install Titanium?
 

jcmm11

Recognized Contributor
Feb 10, 2012
3,589
3,614
Google Pixel 4a 5G
I installed "The SELinux Switch" and changed to Permissive.
MyBackupPro now is able to restore backups, but Titanium Backup still hangs on restore.
I tried all the TiBk options for App processing mode:
Auto Direct - hangs with spinning circle forever
Interactive - first displays "There Was A Problem Parsing The Package”, then hangs with spinning circle forever


What else should I look at? Are there some specific Magisk Modules that are needed for TiBk?
What else have you done other than install Magisk, and install Titanium?
To get Titanium running? Nothing. Titanium was probably the first app I installed after rooting. The only thing that may help figure out what's happening is a logcat
 

martyfender

Senior Member
Mar 9, 2017
3,391
1,860
Indianapolis, IN
I installed "The SELinux Switch" and changed to Permissive.
MyBackupPro now is able to restore backups, but Titanium Backup still hangs on restore.
I tried all the TiBk options for App processing mode:
  • Auto Direct - hangs with spinning circle forever
  • Auto Indirect - hangs with spinning circle forever
  • Interactive - first displays "There Was A Problem Parsing The Package”, then hangs with spinning circle forever

What else should I look at? Are there some specific Magisk Modules that are needed for TiBk?
What else have you done other than install Magisk, and install Titanium?

I see on apkmirror that there is a v8.3.3 available. I don't know if that will help or not.
• Fixed scheduled jobs getting killed on Android 8.0+ if scenario calculations took >5 seconds.
• Minor improvements.
• Updated translations.
 
Last edited:

stefano91av

Senior Member
Jul 13, 2014
277
76
@martyfender Starting from mmcblk0p3.img (size 30 Mb) I have obtained through Magisk app this file: patched_boot.img (size 10 Mb).
But now I have not able to install this patched_boot.img through Magisk app.... why?

---------- Post added at 16:17 ---------- Previous post was at 16:17 ----------

[/COLOR @martyfender Starting from mmcblk0p3.img (size 30 Mb) I have obtained through Magisk app this file: patched_boot.img (size 10 Mb).
But now I have not able to install this patched_boot.img through Magisk app.... why?
 

Attachments

  • magisk_install_log_20190415_162022.log
    3.7 KB · Views: 4
Last edited:

martyfender

Senior Member
Mar 9, 2017
3,391
1,860
Indianapolis, IN
@martyfender Starting from mmcblk0p3.img (size 30 Mb) I have obtained through Magisk app this file: patched_boot.img (size 10 Mb).
But now I have not able to install this patched_boot.img through Magisk app.... why?

---------- Post added at 16:17 ---------- Previous post was at 16:17 ----------

[/COLOR @martyfender Starting from mmcblk0p3.img (size 30 Mb) I have obtained through Magisk app this file: patched_boot.img (size 10 Mb).
But now I have not able to install this patched_boot.img through Magisk app.... why?


You have copy it to your pc and flash it with fastboot with the tablet in bootloader mode.
I usually copy it to the adb/fastboot folder on the pc. I then shift, right click in an empty space in that folder and choose: open a command prompt here. This is assuming you are on Windows.
If, like me, you instead boot to Linux most of the time, you have to use sudo before all of the fastboot commands listed below, unless you are already running as root.
Code:
fastboot devices
Hit the enter key.
When you enter the above command you should see your fastboot serial number listed if the device is connected.
Code:
fastboot flash boot patched_boot.img
Hit the enter key. You should see info that the flash was successful after this.
Code:
fastboot reboot
The above command reboots to Android.

If a custom recovery is available for your device, such as TWRP, it is much easier to flash the magisk.zip through it. You don't even have to have TWRP installed, you can temp boot it with fastboot, from the pc, again copied to your PC.

Code:
fastboot boot twrp.img
substitute the name above with what ever your twrp image is named.
 
Last edited:

stefano91av

Senior Member
Jul 13, 2014
277
76
You have copy it to your pc and flash it with fastboot with the tablet in bootloader mode.
I usually copy it to the adb/fastboot folder on the pc. I then shift, right click in an empty space in that folder and choose: open a command prompt here. This is assuming you are on Windows.
If, like me, you instead boot to Linux most of the time, you have to use sudo before all of the fastboot commands listed below, unless you are already running as root.
Code:
fastboot devices
Hit the enter key.
When you enter the above command you should see your fastboot serial number listed if the device is connected.
Code:
fastboot flash boot patched_boot.img
Hit the enter key. You should see info that the flash was successful after this.
Code:
fastboot reboot
The above command reboots to Android.
I have this situation...
See attachment please
 

Attachments

  • Istantanea_2019-04-15_16-37-59.jpg
    Istantanea_2019-04-15_16-37-59.jpg
    117.1 KB · Views: 256

martyfender

Senior Member
Mar 9, 2017
3,391
1,860
Indianapolis, IN
I have this situation...
See attachment please

You are booted to Android, not fastboot/bootloader mode in that screen shot. The adb devices command indicates that.
On my Nextbook Ares 8A,Intel x86, Android 6.0.1 tablets, from a complete shutdown I hold the volume down key and the power button to boot to fastboot/bootloader mode. The key combos can vary, though to do this.
On my devices, volume up, power button, boots me to the EFI bootmanager.

On my older, now dead, Ares 8 tablet, Intel x86 with Android 5, volume up, power button, booted me to recovery. On your device, how do you reboot to Windows?
I had done some research in the past on Chuwi devices. Is yours an Intel device, also?

I updated my above post also, with more info.

UPDATE: From Android you can boot to the bootloader with this command:

Code:
adb reboot bootloader
 
Last edited:

stefano91av

Senior Member
Jul 13, 2014
277
76
You are booted to Android, not fastboot/bootloader mode in that screen shot. The adb devices command indicates that.
On my Nextbook Ares 8A,Intel x86, Android 6.0.1 tablets, from a complete shutdown I hold the volume down key and the power button to boot to fastboot/bootloader mode. The key combos can vary, though to do this.
On my devices, volume up, power button, boots me to the EFI bootmanager.

On my older, now dead, Ares 8 tablet, Intel x86 with Android 5, volume up, power button, booted me to recovery. On your device, how do you reboot to Windows?
I had done some research in the past on Chuwi devices. Is yours an Intel device, also?

I updated my above post also, with more info.

Thank you so much! Now I have root.
But I have two big problem:
1) system set automatically english language after reboot (i am italian, befor magisk root system was italian after reboot);
2) as from pictuers, busybox and init.d modules are not able to install.
How can I solve these problems?
 

Attachments

  • photo_2019-04-15_17-20-05.jpg
    photo_2019-04-15_17-20-05.jpg
    51.3 KB · Views: 230
  • photo_2019-04-15_17-20-09.jpg
    photo_2019-04-15_17-20-09.jpg
    42.9 KB · Views: 231
  • photo_2019-04-15_17-20-11.jpg
    photo_2019-04-15_17-20-11.jpg
    39.9 KB · Views: 230

martyfender

Senior Member
Mar 9, 2017
3,391
1,860
Indianapolis, IN
Thank you so much! Now I have root.
But I have two big problem:
1) system set automatically english language after reboot (i am italian, befor magisk root system was italian after reboot);
2) as from pictuers, busybox and init.d modules are not able to install.
How can I solve these problems?

I am afraid I haven't any experience with language. Can you go into Android settings, Language & Input to change it? Magisk Manager has settings also for language.
When you install a module, you have the option to save logs. If you post those logs, someone here may be able to help. I would also suggest posting the magisk.log in /cache/. Attach the logs to the post using the attach function or upload it to a file sharing site such as pastebin and post links. Please don't put the log in the body of a post as it makes it difficult to read, especially for mobile users.
I often find I have to hit the go advanced button option to see the attach button below. That is usually when I later edit my post, though.
If TWRP is available for your device, you may have better luck by downloading the modules.zip and flashing with it, instead. I have had cases where I had to do that in the past.
 
Last edited:

stefano91av

Senior Member
Jul 13, 2014
277
76
I am afraid I haven't any experience with language. Can you go into Android settings, Language & Input to change it? Magisk Manager has settings also for language.
When you install a module, you have the option to save logs. If you post those logs, someone here may be able to help. I would also suggest posting the magisk.log in /cache/. Attach the logs to the post using the attach function or upload it to a file sharing site such as pastebin and post links. Please don't put the log in the body of a post as it makes it difficult to read, especially for mobile users.
I often find I have to hit the go advanced button option to see the attach button below. That is usually when I later edit my post, though.

For language before i had not this problem, only now after patched_boot.img flash.
Maybe unzip not works.... and busybox not works.... i am reading online....
 

Attachments

  • magisk.log
    1.9 KB · Views: 12
  • magisk_install_log_20190415_113538.log
    131 bytes · Views: 9

zputnyq

Senior Member
Apr 19, 2013
619
278
Thank you so much! Now I have root.
But I have two big problem:
1) system set automatically english language after reboot (i am italian, befor magisk root system was italian after reboot);
2) as from pictuers, busybox and init.d modules are not able to install.
How can I solve these problems?
1) I think you can change it from device setting (settings > language & input)
2) I have no idea, but logs are needed & report it to magisk modules' dev as well will be better :)
 

stefano91av

Senior Member
Jul 13, 2014
277
76
1) I think you can change it from device setting (settings > language & input)
2) I have no idea, but logs are needed & report it to magisk modules' dev as well will be better :)

ok, but it is so strange that my tablet in language setting is crazy now ahahahah
Now i have restore original boot.img and languange of system not change.
So there is a problem here between my tablet and magisk :(
I am reading that a clean flash of android system solves any problems (possible problem with busybox).
 
Last edited:

martyfender

Senior Member
Mar 9, 2017
3,391
1,860
Indianapolis, IN
For language before i had not this problem, only now after patched_boot.img flash.
Maybe unzip not works.... and busybox not works.... i am reading online....

I see this error in the magisk.log which I also recently had on one of the recent unofficial builds:

execve /sbin/.magisk/mirror/bin/busybox failed with 8: Exec format error

I've been told it may be that magisk's built in busybox may be detecting the wrong architecture, but I never got a clear answer. It was solved in later builds for me.
I am hesitant to recommend this, as some have had problems, but you might have better luck with beta v19 or the latest Canary build.
I would first try to get it to work with the current stable version.
 

stefano91av

Senior Member
Jul 13, 2014
277
76
I see this error in the magisk.log which I also recently had on one of the recent unofficial builds:

execve /sbin/.magisk/mirror/bin/busybox failed with 8: Exec format error

I've been told it may be that magisk's built in busybox may be detecting the wrong architecture, but I never got a clear answer. It was solved in later builds for me.
I am hesitant to recommend this, as some have had problems, but you might have better luck with beta v19 or the latest Canary build.
I would first try to get it to work with the current stable version.

so, is it better to wait a possible fix?
 

martyfender

Senior Member
Mar 9, 2017
3,391
1,860
Indianapolis, IN
A factory reset may solve the language problem. Keep a backup of your stock boot. Img, the v18 patched boot.img, if you decide to try the v19 beta or the Canary build to go back to if you have problems. You never did say if twrp is available for your device, as you could then do a full backup.
 
Last edited:

MaFiBoSS

Senior Member
Feb 24, 2010
126
50
404 not found
Hi,

Anyone have issues on app TV Vodafone? Not working on Magisk v18.1. Detects that the smartphone has root (Hide option enabled + APP selected on Magisk).

Note: In the previous version (17.3) of Magisk it was enough to kill the application (Magisk) in recent applications for the application of TV Vodafone to work (do not detect root).

Another application that does not work is PS4 Remote Play, last version 2.7.0, only the v2.6.0 works.

Update:

I jumped from v18.1 (STABLE) to v19.0 (BETA) + Magisk Manager v7.1.0, and the TV Vodafone app its working again (need to close the MM in background). Only the PS4 Remote Play app, v2.8.0 continues to detect the root.

If upgrade the Magisk Manager to v7.1.1, can't pass the SafetyNet and the Magisk Hide not working properly (all apps detect root).

Just my feedback.

Update2:

After installing the updated framework, I was able to run PS4 Remote Play app v2.8.0 :).

If anyone needs: Sony_Framework-v1.zip.

---------- Post added at 08:14 PM ---------- Previous post was at 08:12 PM ----------

Hello,
I have magisk 19 on OP6T installed and every app was running fine.
Sometime in the recent past - may be past couple of days even Vodafone app is detecting the root and warning. Now TV app asks to undo system modifications and try again when I try to play GOT S8E01.. Anyone facing similar issue?

Hi, try what I mentioned above about the Vodafone TV app. :good:
 

AceS00

Member
Feb 26, 2019
33
2
Hey guys I am using the blackdiamond v2 (Note FE one ui port for s7 edge) So I got magisk manager installed and when I hide it, it doesnt hide but then theres 2 magisk manager any help?

Info:
(Arianoxx v4 kernel)
Magisk v18.1
Magisk manager v7.1.1
 
Last edited:

CSX321

Senior Member
Aug 21, 2009
644
300
Southern IL USA
I guess it's safe to delete all these old "stock_boot_xxxxxxx" files in /data, isn't it? It's a Pixel 3, so if I ever need to uninstall Magisk, I'll just flash the stock boot image myself.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    I can't access superuser and modules they are both lockedView attachment 6081641
    Your phone isn't rooted! The top section of your screenshot shows Magisk "Installed N/A".
    Installing the Magisk app isn't enough to root your phone.
    4
    I have always have problems with magisk and bug reports think I have even failed with the debug version lol, although its closed I have added that the bug is not present with the debug version
    Just open another with "version code: 27002" somewhere in first post, explain you tested both but issue is with Canary only, not Debug... Supply logs from broken build and wait for further instructions from Devs... Template requires the version code (or bot closes) + logs (or Devs will often close with comment like "no log no fix")...👍 PW

    Edit: Someone opened proper issue following template just now:
    https://github.com/topjohnwu/Magisk/issues/7921

    Looks to me like this commit has issues:

    Always update stub APK when upgrade

    committed5 days ago
    4
    Latest canary Update 27002 will not let me hide the Magisk app, get a failed toast, tried opening an issue but need to use the debug version,
    Installed the debug version and it works and hides the magisk app?
    4
    Hello, I'd like to write a module for magisk to transfer in userspace actions like this:
    "echo "16 2048" > /sys/class/leds/aw210xx_led/single_led_br" to allow led control on Nothing Phone 1 to any app, would you suggest me an example module I can take inspiration from?
    Write your service.sh script with whatever commands you need

    Then use any module you already have installed that does not have its service.sh script and add your scriot to that module, eg in case of Systemless Hosts itbwill be:
    /data/adb/modules/hosts/service.sh

    Or use some other module that does have its own service sh script and extend its script with your commands

    You may need to wait booting to finish (you have to debug how yout modifications works if executed earlier or later), in that case script will look like:
    #!/system/bin/sh

    until [ "$(getprop sys.boot_completed)" == "1" ]; do
    sleep 1
    done

    echo "16 2048" > /sys/class/leds/aw210xx_led/single_led_br

    You can add additional sleep if you need to further postpone upon the System finish booting, eg couple of seconds to establish WiFi connection or something

    Or if that is too late (some modifications must be done much earlier, while the System boots), you will have to use post-fs-data.sh script instead of service.sh script but then you must not wait for booting to finish and you must not use sleep

    Read on Magisk GitHub Developer info avout differences in service sh and post-fs-data.sh usage

    Read there generally about the structure of the module scriot, etc

    At the end reboot and test does it work

    Once you make sure that your script does the job properly, it will be an easy step to pack it into your own module

    Similar questions have been asked couple of times (and I responded with instructions and minumalistic sceleton to pack final scripts into the zip installation for a new module)
    4
    Not sure if the fix has been pushed yet but looking at GitHub it's been sorted
    Not pushed yet according to my magisk app.
    Luckily i don't hide or need to hide; this is a sad bug and i hope, for others' sake, it's pushed as soon as the developers can. But that's also why it's canary and not beta or release, it's why (or should be why) we use canary, to squash bugs before the rest experience them.
  • 1103
    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