Better click his 'like' button!
PW
Magisk General Support / Discussion
- Thread starter topjohnwu
- Start date
PW
No fun if you give away the secret.Better click his 'like' button!
Keep giving away the important ones...No fun if you give away the secret.
That one's sure to help me (and others) in future. (My last LOS had boot.img in root of zip IIRC.)
Edit: Found this tutorial for PC also (Uses Payload Dumper Tool and Python to extract firmware files including boot.img):
How to Extract payload.bin and get stock boot image file - DroidWin
To extract the payload.bin file from stock firmware and get the stock boot image file, you should refer to the instructions given in this guide.
www.droidwin.com
[Tutorial] Android OTA payload dumper on Android
Introduction This tutorial will teach you how to specifically extract the boot.img from your OTA/ROM's payload.bin on your Android device, rather than a computer. In addition to this, you will also have the ability to access all other img files...
Don't know why LOS doesn't host the image files for root users; perhaps they make it difficult intentionally as Magisk makes prop spoofing etc easy and the have strict anti-spoofing policies etc... or perhaps some other reason, I don't know. PW
Last edited:
If you have a working TWRP you should be able to backup the boot-partition and patch the image-file from backup with Magisk.Keep giving away the important ones...
That one's sure to help me (and others) in future. (My last LOS had boot.img in root of zip IIRC.)
Edit: Found this tutorial for PC also (Uses Payload Dumper Tool and Python to extract firmware files including boot.img):
And here's one to extract using phone!:How to Extract payload.bin and get stock boot image file - DroidWin
To extract the payload.bin file from stock firmware and get the stock boot image file, you should refer to the instructions given in this guide.
[Tutorial] Android OTA payload dumper on Android
Introduction This tutorial will teach you how to specifically extract the boot.img from your OTA/ROM's payload.bin on your Android device, rather than a computer. In addition to this, you will also have the ability to access all other img files...forum.xda-developers.com
Don't know why LOS doesn't host the image files for root users; perhaps they make it difficult intentionally as Magisk makes prop spoofing etc easy and the have strict anti-spoofing policies etc... or perhaps some other reason, I don't know. PW
But boot.img for magisk update must be original from stock image or a arleady boot IMG patched by Magisk ?
Can some One explain how to update from 21.4 to 22 cause disaster i made Yesterday ?
Thank you
Can some One explain how to update from 21.4 to 22 cause disaster i made Yesterday ?
Thank you
Keep giving away the important ones...
That one's sure to help me (and others) in future. (My last LOS had boot.img in root of zip IIRC.)
Edit: Found this tutorial for PC also (Uses Payload Dumper Tool and Python to extract firmware files including boot.img):
And here's one to extract using phone!:How to Extract payload.bin and get stock boot image file - DroidWin
To extract the payload.bin file from stock firmware and get the stock boot image file, you should refer to the instructions given in this guide.
[Tutorial] Android OTA payload dumper on Android
Introduction This tutorial will teach you how to specifically extract the boot.img from your OTA/ROM's payload.bin on your Android device, rather than a computer. In addition to this, you will also have the ability to access all other img files...
Don't know why LOS doesn't host the image files for root users; perhaps they make it difficult intentionally as Magisk makes prop spoofing etc easy and the have strict anti-spoofing policies etc... or perhaps some other reason, I don't know. PW
Excellent, my question was somehow useful to others
read the changelog which can be found here https://topjohnwu.github.io/Magisk/releases/22000.html
I'm sorry to report that Magisk v22.0 (22000 build) isn't able to correctly patch vbmeta img leading to a boot loop into download mode
SM-A307FN
ITV_A307FNXXU2BTG1
people online were able for sure to correctly root this model with previous releases of magisk
SM-A307FN
ITV_A307FNXXU2BTG1
people online were able for sure to correctly root this model with previous releases of magisk
I had same corrupted boot.img thru update (froze during direct update, looped to fastboot after I restarted phone) fixed by fastboot flashing working boot image previously patched w/ earlier Magisk.
Next, I tried patching boot image, and gave up as Magisk app 'froze' again, and nothing happened.
The next day, I tried to reproduce issue with Logcat Reader running, first by patching image only again, and this time it patched fine w/ dialogue ->> 'all done', so (happily) I couldn't reproduce issue.
I may have restarted phone again, but otherwise did nothing differently, so seems problem is a fickle one.
I'd extract boot image from currently used ROM package (assuming ramdisk = no (in Magisk app) for your device), ensure you unhid Manager and have no hidden Manager app / stub left over if you previously hid it, reinstall Magisk 22.0 app (with or without root), then see if patching boot image dialogue completes for you. If so, fastboot flash should work fine!
If not, I'd keep 21.4, at least till next Canary fixes... PW
After reading all adventurous stories with trepidation
I ventured by
- Backing up (Swift/Migrate)
- Extracting & Patching boot image (as a backup)
Magisk Manager was not hidden.
Well, it went smoothly without any issues.
Upgraded Magisk Manager to now App and
Magisk to now Magisk (from 21.4 -> 22)
Maybe it would be better if
MagiskHide and
Hide Magisk Manager
changed to
Stealth/Camouflage Magisk and
MagiskHide
I ventured by
- Backing up (Swift/Migrate)
- Extracting & Patching boot image (as a backup)
Magisk Manager was not hidden.
Well, it went smoothly without any issues.
Upgraded Magisk Manager to now App and
Magisk to now Magisk (from 21.4 -> 22)
Maybe it would be better if
MagiskHide and
Hide Magisk Manager
changed to
Stealth/Camouflage Magisk and
MagiskHide
I honestly prefer magisk as a system app. Guess i wont be updating magisk for a while
It's now Magisk-v22.0.apk, not zip unless renamed.
It's on Magisk main GitHub page as always.
Access from Magisk app main page (GitHub 'cat' symbol), or check OP (ALWAYS check OP) here, click Announcement Thread, and wallah!... first link is to Magisk main page on GitHub! PW
Yep, i was using that one, and it made apps recognise root(btw i'm using mcdonald's app for testing hiding root from apps which detects it, as i was suprised that trivial app for some reason is that complexed and made to search for anything like bank apps, even for busybox as i now found out), so i hope magisk module busybox will hide it better, now will wipe phone and put everything again, and test it with module xD
SuperSu+pro версия,не запустится Magisk.Пишет ошибка при загрузки файла,любого.SuperSu затребовал обновления что и сделал,потом сам перезагрузил.сторонний канал невкючать написано.загружать файлы по другим каналам.
Если у вас установлен magisk, вам больше не нужен SuperSu + pro. вы можете управлять рутированным приложением внутри magisk
Guys.... While you are allowed to post in other languages on XDA, the post also need to be translated to English (see forum rule #4).
Would anyone be so kind to point me to a procedure to install the newest Magisk? The way I always did it was to install it from TWRP custom recovery after a ROM update, and then every subsequent one I'd install via the app. However this time app update has failed and left me with a broken boot.img so I had to reflash the stock boot.img and then custom recovery.
So again - how do I install the newest Magisk without getting any corruption? OnePlus 6 here.
EDIT: Okay nevermind. It worked via the app now. So turns out the main issue as to why it failed the first time was probably the MagiskHide being enabled (which I thought I disabled, but I just mistook it for hiding the app - NOT THE SAME THING!).
So again - how do I install the newest Magisk without getting any corruption? OnePlus 6 here.
EDIT: Okay nevermind. It worked via the app now. So turns out the main issue as to why it failed the first time was probably the MagiskHide being enabled (which I thought I disabled, but I just mistook it for hiding the app - NOT THE SAME THING!).
Last edited:
Thats a useful option I haven't considered for some time!
Been checking on flashing boot.emmc.win and there's some confusion, but generally people are reporting this can simply be renamed boot.img and flashed. (system.ext4.win etc may need to be unpacked and repacked due to compression/encryption).
I haven't flashed yet, but can confirm Magisk recognises my backup renamed boot.img as 'Magisk patched boot image', and re-patches this fine!
Thanks for the useful heads-up.
Last edited:
After wipe out, putting twrp and magisk, now play store isn't working for some reason to download or update any app, neither play store itself doesn't wana update, what to do?
Edit: nvm, after more times rebooting, now it works xD
Edit: nvm, after more times rebooting, now it works xD
Top Liked Posts
-
3
Yes
See this log for patching recovery image (Recovery mode checked):
Direct Installation log is similar.Code:- Device platform: arm64-v8a - Installing: e136fb3a (22102) - Copying image to cache - Unpacking boot image - Checking ramdisk status - Stock boot image detected - Patching ramdisk - Repacking boot image **************************** Output file is written to /storage/emulated/0/Download/magisk_patched-22102_xumwp.img **************************** - All done!
But recovery ramdisk and boot ramdisk are implemented differently.
As John took pains to point out, type III (Ramdisk= no) devices (generally speaking) DON'T support boot-ramdisk (even if added manually when missing, as Magisk does) due to lack of bootloader support. However, since bootloader (generally speaking) supports recovery-ramdisk, Magisk in recovery is an option.
As I understand it, to use any ramdisk type requires ramdisk specific bootloader support. Kernel and ramdisk can be patched, but bootloader (again, generally) cannot be, due to proprietary nature.
Bootloader support (or lack of it) presents the real challenge.
Yep, understand that.
But I don't understand fully what's going on yet.
Since trying with stock, I tried patching and flashing TWRP image (w/ fastboot) both w/ stock boot, and Magisk patched boot image with similar results; patching succeeds (completes w/ no errors), but get 'system has been destroyed' on booting.
Then, with Magisk in boot, I've checked Recovery mode and tried Direct Install. Surprisingly, this succeeds, and reboot (from Magisk App) lands me in recovery.
It appeared I now had Magisk in Recovery as all settings were for this, but on powering off and trying to boot with recovery key combo / releasing keys at splash screen (for system with Magisk in recovery), like you, I have great difficulty getting to system. I get recovery unless I release keys on vibration, and almost BEFORE splash screen appears! I get System with root this way, but I'm not sure I'm not simply releasing keys too early to boot using recovery at all (ie. that this isn't actually Magisk in boot.)!
To test this, I've variously to flash stock boot.img (to see if I can boot with and without root as instructions say I should have ability), and with boot.img patched with a slightly different version of Magisk (for bootup comparison), but ANY such changes in combination with patched working recovery image result in 'System Has Been Destroyed', Fastboot mode only available, and this is fixed only by flashing unpatched recovery image.
Seems the symptoms I have may be similar to yours (difficulty booting to system from recovery key combo, etc). At the very least, I'm not convinced I actually have Magisk in recovery, although it has clearly been Patched / altered.
At this stage, I suspect that Xiaomi devices that appear as type III (and possibly other devices) may not be properly accounted for in John's Booting Shenanigans summary. I'm thinking the unexplained bootloader compatibility with ramdisk in boot may somehow be there to boot recovery, although not needed for system.... or other perhaps something else is going on.... So we may in fact have more than IV basic boot-types of Android device... There seem to be more discrepancy with John's Type III model that just having Magisk in Boot ability.
I'd love to get my head around this!
Covered by @zgfg. PW3
Magisk shows Error when checking SafetyNet, not Fail.
Might be everyone checking SafetyNet recently using Magisk's API key?
¯\_(ツ)_/¯
If the device shows as certified in PlayStore, you are currently passing SafetyNet.
Cheers all.
2
At the end of 2019, when I got my Xiaomi Mi 9T, I think it was MIUI 10/Pie and Magisk v19 or v20, I searched how to root.
Since it's reporting Ramdisk=No (SAR yes, A/B no - I checked also querying by adb) and by following the Magisk Github documentation it was 'clear' I had to patch recovery, not boot
Fortunately, I found two independent guides for my Mi 9T claiming that for Magisk one must patch boot.img - hence I happilly did the same, specially because I also use TWRP (in Recovery) in parallel
Since then, I do it the same way through all MIUI updates (now on MIUI 12.6/A11 Xiaomi.eu) and all Magisk (Canary) updates
I always wanted to test but never really tried what would happen if I patch Recovery instead (cannot test now since I'm now on weekly Xiaomi.eu beta that distributes without recovery.img in the zip, and their firmwares must be flashed through TWRP)
I only tested updating Magisk by flashing the zip from TWRP, and it properly found and re-patched the Boot - however I never tried cold installation of Magisk from TWRP, would it properly imstall to Boot (but I think I've seen other users for my Mi 9T confirming it working well)
Ofc, I don't know does it work the same way or 'all' Xiaomi phones22 -
12
Latest Public (Stable / Beta)
Release Notes and Changelog:
2021.4.9 Magisk v22.1
This release is focused on fixing regressions and bugs. Check the v22.0 release notes if coming from older releases.
Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 will only support Android 5.0 and higher.
Bug Fixes
- [App] Prevent multiple installation sessions running in parallel
- [App] Prevent OutOfMemory crashes when checking boot signature on PXA boot images
- [General] Proper cgroup migration implementation
- [General] Rewrite log writer from scratch, should resolve any crashes and deadlocks
- [General] Many scripts updates fixing regressions
- [MagiskHide] Prevent possible deadlock when signal arrives
- [MagiskHide] Partial match process names if necessary
- [MagiskBoot] Preserve and patch AVB 2.0 structures/headers in boot images
- [MagiskBoot] Properly strip out data encryption flags
- [MagiskBoot] Prevent possible integer overflow
- [MagiskInit] Fix sepolicy.rule mounting strategy
- [resetprop] Always delete existing ro. props before updating. This will fix bootloops that could be caused by modifying device fingerprint properties.
PW8
Looks like you have /dev/bootimg as your real partition location and it is still higher in the list in util_functions.sh like how I fixed it in the linked commit, so this is definitely a regression from some other recent change to Magisk.. sigh, I'll look into it.
6#Xiaomi.eu, #OTA, #Magisk 22006, #Viper4Android, #sepolicy.rule
This week, Xiaomi.eu weekly update 21.3.24 (MIUI 12.5, A11) was late a day and a half, hence I upgraded yesterday night
As usual:
- I downloaded the zip, extracted boot.img and patched (already from my previous Xiaomi.eu 21.3.18, rooted by Magisk 22006)
- Flashed the Xiaomi.eu zip from TWRP, wiped Dalwik and Cache and rebooted
- Then rebooted once again to TWRP and flashed the boot.img that was patched in advance
I could probably flash its patched boot img right after flashing the 'OTA' zip (saving one time booting to the not-rooted system and rebooting to TWRP), but I rather play the safe and many times proven game
Upon rebooting with the patched boot img, I have Magisk 22006 root again, with all modules (except V4A), root granted apps snd apps enabled for Magisk hide
This time the old trick to make V4A did not work. Maybe because of the known sepolicy.rule bug in Magisk 22006, or maybe I was not 'patient' enough and made a mistake in steps
Anyway, I also wanted to test, hence I modified V4A's post-fs-data.sh in accordance to:
https://forum.xda-developers.com/t/...-0-viper4android-fx-2-7.3774651/post-84121895
rebooted, and it did the trick
The modified post-fs-data.sh for:
/data/adb/modules/ViPER4AndroidFX
is zipped and attached
The zip also contains DDC and Kernel folders to be copied ton Internalmemory: /Android/data/com.pittvandewitt.viperfx/files
for V4A Convolvers and headphone profiles
Hence now I have again AML, V4A plus another audio mode (320 kbps bitrate for my phone) and V4A is happilly again Supported and Proccessing (still in the Legacy mode)6
/dev/BOOT is known (usually) not an actual boot partition, hence nanddump failing.
I had originally fixed this back here: https://github.com/topjohnwu/Magisk/commit/2aede97754fec67d393bde0c7725ed84d8c3c112
So not sure if we're looking at some kind of a regression, or just a further edge case.
@io2345 what's the actual, correct location of your boot partition? Please give me the output of `ls -alR /dev`6Latest Canary Changelog, including Release Notes:
Magisk (9c0e1897) (22007)
- [General] Fix logic to copy sepolicy.rule during module installation
- [resetprop] Always delete existing ro. props before updating. This will fix bootloops that could be caused by modifying device fingerprint properties.
Diffs to v22.0
- [App] Prevent multiple installation sessions running in parallel
- [App] Prevent OutOfMemory crashes when checking boot signature on PXA boot images
- [General] Proper cgroup migration implementation
- [General] Rewrite log writer from scratch, should resolve any crashes and deadlock
- [General] Many scripts updates fixing regressions
- [MagiskHide] Prevent possible deadlock when signal arrives
- [MagiskHide] Partial match process names if necessary
- [MagiskBoot] Preserve and patch AVB 2.0 structures/headers in boot images
- [MagiskBoot] Properly strip out data encryption flags
- [MagiskBoot] Prevent possible integer overflow
- [MagiskInit] Fix sepolicy.rule mounting strategy
- [resetprop] Always delete existing ro. props before updating. This will fix bootloops that could be caused by modifying device fingerprint properties.
PW -
1046This 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 Thread155Hello, 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
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
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!!119Ah, 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.76Thread 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.74Hello 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
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone