Switching from Magisk stable (27.x) to canary (and vice-versa if I don't like canary) should be an easy thing but I don't see updated instructions. I had done this way back, IIRC, by choosing custom update and inserting a link which doesn't work anymore I have downloaded the canary version from the official Magisk site and what are the next steps? Please note that I don't want to unroot, root with canary and set up all the modules, which is a huge pain. I can think of two options: 1. Install the canary apk and it gets installed over the stable with modules intact 2. Change the canary apk extension to zip and flash from within Magisk I am not sure which is the best way, possibly their are better ways but my primary concern is not to set up modules again and easily reverse from canary to stable All this for a banking app detecting root

I've seen this question asked two years ago https://android.stackexchange.com/q/245205/131553 which asks for the same on Android 9,but with so many tools being developed (and abandoned) and changes in Android versions , is it possible now? I use Pixel 4a/6a, rooted, Magisk 25.2 on Android 13. There aren't any TWRP recoveries for them. With the perpetual cat and mouse game between root detection by banking and such like apps, I feel the cat (Google) will have an upper hand soon. So my thought is to have one slot rooted and the other slot unrooted and on the fly switch slots using an Android based way. I know it can be done using a PC but that's not what I want. Does anyone know of any way? Maybe Termux based or some kind of scripting? Or Magisk/Edxposed modules? I don't want multi-ROM or dual booting solutions (doubt if they exist for current Android versions) Edit 1. [Switch My Slot](https://github.com/gibcheesepuffs/Switch-My-Slot-Android) hasn't been updated after 2021. When I run that it closes saying bootctl binary missing 2. [Magisk Bootctl Binary](https://github.com/roihershberg/bootctl-binary) works only upto Android 12. I tried it but there appear to be some Magisk limitations too apart from failing since it is not designed for current API level. 3. I couldn't find any bootctl Magisk module in various repos

I am on Pixel 4a running stock Android 12. I was on Magisk 23.x with Lsposed (as Riru is anyway [deprecated](https://github.com/RikkaApps/Riru)) . I had no need of updating to the latest 24.1, since everything was fine and I didn't keep up with latest Magisk changes. Till a banking app update ruined my peace, because it detected root (SBI Yono for Indian readers). All my efforts to circumvent root detection failed @ and I was forced to consider updating Magisk hoping that the *Deny list* feature would help in preventing root detection (though it's not same as Magisk Hide) or else use a compatible root hiding app Shamiko (stable version released a few days ago). This looked to be challenging since **Magisk 24.1 does not support Riru**. So **how do I run Xposed modules like XPrivacyLua, Xposed Edge etc?** This was my biggest worry. Google-fu didn't help, but a vague comment on Reddit gave hope. More search revealed other issues and their solutions, which are in the answer below. It was worth the effort since Zygisk is a key feature of Magisk and I may as well step up my game (and your's). All the best and yes, I won't be updating this to keep up with changes but you hopefully have enough pointers to find your way @Safety-net passed; developer options state hidden;device shows certified in Play Store. Hiding Magisk app 23.x involves jumping through a lot of hoops, so didn't try that.

I have magisk installed on my phone – binary & daemon version 22.0:MAGISK (22000). It is great. I had to install MagiskHide to enable a banking app that otherwise did not work. I used the option to rename the MagiskManager binary to something else to prevent it from being detected – which was required for the (evil!) banking app to work. I now wish to update Magisk and install another framework. Unfortunately, whilst I can see the renamed binary to the gui / UI on my launcher, if I tap on it, it doesn't open – the shortcuts to "Modules" and "su" and so forth are still there, but the binary doesn't work. If I log in via adb shell, I can call su and all works that way. Other apps that rely upon root don't show the permissions dialogue if I did not previously authorise them – unfortunately, because I updated termux, that includes it and su just hangs. In a root shell, magisk and magiskhide all work – I have disabled magiskhide but still cannot open the manager application. If I install the latest version of Magisk from github, it cannot connect to the daemon and offers to flash an image. I am therefore in a bit of a pickle. I would like to know: – Can you run magisk --install-module to get it to update itself? Would that bring the gui back? – If not, can I manually undo whatever magiskhide did to rename or hide the MagiskManager gui? One option I have yet to try is flashing the latest magisk zip via twrp but I am slightly worried that having two versions of magisk is likely to be a BadThing™... EDIT: Here's what the (renamed) Magisk Manager binary looks like – none of the buttons work and nothing appears in dmesg when I tap them:

In the past,solutions for preventing root detection were centered around safety-net, Magisk hide or XPosed modules like Sudo hide. With Magisk 24.1 plus Magisk Hide isn't an option and modules like Sudo hide aren't being maintained anymore. All revolving around a "frontal attack" of detecting root The sneakier way would be to find other ways to detect the root status based on finding traces of modded framework/ Xposed modules/Lsposed framework and obviously know that device is rooted and refuse to work.Or worse, a combination of both frontal and sneaky detection! As I mentioned here https://android.stackexchange.com/q/245242/131553 , Shamiko seemed to be an option but the adverse comments around it discouraged me. Searching for alternatives to Shamiko, led me to the revelation that there are enough instances already of sophisticated banking/streaming/gaming using "sneaky" ways to circumvent user measures like faking safety-net etc. So, I was getting ready for the future when one of the banking apps I use would turn sneaky and be ready for it. This search led me to an Xposed module which looks promising and (another) self-answered question. **Caveat: YMMV** If you know of another solution, please add as an answer.

I have a [banking app](https://play.google.com/store/apps/details?id=com.sbi.SBIFreedomPlus) which was detecting root despite being hidden by Magisk. I managed to hide root from that app but on analyzing that app I found an activity that is very conveniently named DETECT MAGISK with activity name com.sbi.rc.DetectMagisk I want to know if I can disable only that activity so that the app cannot even make an attempt to detect root (I am not sure if the app would work or not with that activity disabled, but worth a shot) Pixel 4a, Android 12,rooted

John Wu, developer of Magisk, published a blog [State of Magisk:2021](https://twitter.com/topjohnwu/status/1431889845199147008) , a couple of days ago which led to some confusion as to what is to be expected. Can the changes be explained in *non-technical* language? **Note**: This is a self-answered question as a reference, consolidating from various sources. Moderators are welcome to convert this into a wiki in case future developments are added by other users.

I'm trying to get a certain NFC tap-and-pay app to work. It's called Nexi-Pay and AFAIK is only available in Italy. Due to "security concerns" they deny access to the app to rooted Android users. I managed to get past the root check with Magisk Hide, but now the app says that I have to disable "Android USB Debugging" to use it. Now, I tried doing so and it worked, but since it is a feature I use very often, it would be a pain to switch it on and off every time I need to pay for something. How can I make the app think ADB is disabled while it's actually not, a-la-MagiskHide?

Just when I was about to reach level 23, Pokemon Go stopped working with this message: > This device, OS, or software is not compatible with Pokémon GO I am using CyanogenMod 13.0-20160817-NIGHTLY-hammerhead (Android 6.0.1) on a Nexus 5, and can't live without root. QUESTION: Is there a way to make it work again? Screenshot (click image for larger variant)

How can I use the Tap and Pay payment app *Glase* (formerly *SEQR*) on a device which has been rooted using Magisk?

Many banks and video streaming services don't allow root on Android devices. My question is 1. Is it the app itself that detects root and refuses to work at some stage (for example by refusing to call the associated internet service)? 2. Is it the internet service that somehow directly or indirectly probes your device to see if it is rooted and if so instructs the app to disconnect or display some error message? I guess this might interest people for which the app _Hide Root_ doesn't work with some service providers.