Hi,
Recently I installed lineageos android 10 on Samsung Galaxy S3 Neo Duos
Then tried to use magisk to gain root privileges but simply can't do that
SafetyNet Check: All False
Installation Failed: UnSupported / UnKnown Image Format
I search about this problem and found the next link
LineageOS is dropping its own superuser implementation, making Magisk the de facto solution
I read it but can not figure why lineageos team drop superuser, but this is not my problem
I just need to know I there any way to root my device Even if without magisk
Or I Will need to downgrade to android 9
Also if the answer is I must downgrade to android 9
Does this mean any new rom start from android 10 + will not have any way to gain root privileges ???
Thanks.
---------------------------------------------------------
To 73sydney
First: Thank You
I take the next steps
Download lineage From Here
Install TWRP latest version TWRP-3.3.1-1-s3ve3g.img.tar With Odin3_v3.14.1
Use TWRP to install lineage_s3ve3gds: and everything worked correctly
Download Magisk-v20.3.zip
Copy it to my sd card
Open Device In Recovery mode and then use TWRP to install magisk
and it does not show any error messages
Install magisk.apk
Open magisk app
Show me: Magisk is not installed
Press Checking SafetyNet Status
Show CtsProfile: false, basicIntegrity: false
This is how I install android 10 and Magisk
Nothing to do with Android 10 as we just got LineageOS 17 on my Note 4, and i have Magisk running fine, only needed to fix CTS issue with MagiskHide Props Config as per following video
https://youtu.be/wKYC0r-m0Mo
It could be the way youre flashing magisk, or the way the ROM is built, because im just guessing because the Note 4 is unofficial LineageOS, the S3 build would be too. Frankly im surprised anyone would bother with the S3..
To get to the main issue though, lets get the basics... just how are you trying to install Magisk?
Just found your devices forum, theres like 3 threads/guys spraying LineagesOS builds into it. Perhaps tell them to work together for starters....
And really ideally they'd test for the possibility of rooting and root solutions before releasing because gets what question number 1 is going to be, how do i root this? Again, perhaps get them to work on it together
LineagesOS dropped their SU simply because its outdated, doesnt do what Magisk can do (modular addons to customise) and prolly mostly, its not used by anyone
I edit my post to explains all steps i take to install lineageos & magisk
Thank you for your reply
First I Edit my post to all steps you asked
Second: I am not an android professional
I tried to figure out what you means but can not.
I just want to know steps to gain root access
Please Notice: OEM option does not appear in developer options
So please if you can give me a link/resources to know how to root my device [Samsung Galaxy S3 Neo Duos With lineageOs 17.1] this will be very helpful
Thanks.
It's perfectly possible that it isn't possible to root your ROM with Magisk. It depends on how it's created... If it's using fake dts Magisk won't work. References:
https://twitter.com/topjohnwu/status/1226644269261213696?s=20
It was the same case for LineageOS 17.1 on the Nexus 4, but that was fixed. See the ROM thread for more details:
https://forum.xda-developers.com/nexus-4/development/rom-lineageos-15-1-t3758779
None of this is something that you as the user can do anything about. It has to be fixed by the developer, so let them know (if it is a case of the ROM using a fake dts).
Magisk 20.4 with the 7.5.1 manager is working perfectly in a Nexus 5 with LineageOS 17.1.
Related
Hi all when flashing any version above v12 on to my phone it gets stuck at the boot logo I am using Lineageos latest version of typing this but if I use v12 its fine but dont pass the CTS and stuff
I have tried to fully uninstall the magisk and reinstall it on the newer version and nothing can anyone help please
I have also fully reinstalled the ROM with formatting everything and it still don't boot
Your bootloader must be unlocked to flash LOS on the S5, right? I have the same setup as you and running no issues at all. Are you flashing the zip after flashing the ROM?
ldeveraux said:
Your bootloader must be unlocked to flash LOS on the S5, right? I have the same setup as you and running no issues at all. Are you flashing the zip after flashing the ROM?
Click to expand...
Click to collapse
The Samsung galaxy S5 plus (g901F) is different from Samsung galaxy S5 (g900) si magisk work on second one but on the first one magisk v13 never worked and it's confirmed at the lineage OS side. I'm on this case too so I confirm the issue.
Jet45 said:
The Samsung galaxy S5 plus (g901F) is different from Samsung galaxy S5 (g900) si magisk work on second one but on thé first one magisk v13 never worked and it's confirmed at the lineage OS side. I'm on this case too so I confirm the issue.
Click to expand...
Click to collapse
So glad someone eles has the same problem and I'm not on my own it just seems weird how the v12 works it don't pass but all loads fine. Let hope they find why and fix it.
Flash your stock bootloader then try flashing magisk
I'm using the stock bootload not changed my bootloader
If it was the bootloader why foes v12 work fine?
No request to have any information about this ?
What do the devs need (other than time of course) to try a troubleshooting ?
How to get this logs/boot image and logs ?
Managed to get it working, but did a clean install and lost it, first time I got it working I was at 19-07-2017 build with magisk manager 5.1.1 and magisk 12, with magisk folder mount and magisk ext SD access modules installed, then upgraded to 26-07-2017 build through official update from settings, and after installation I rebooted the phone into recovery and installed magisk 13.3 (as you know when updating we lose magisk root) and it worked.
Then did a clean install of 26-07 build (thinking it will work) but nope.
Recycool said:
Managed to get it working, but did a clean install and lost it, first time I got it working I was at 19-07-2017 build with magisk manager 5.1.1 and magisk 12, with magisk folder mount and magisk ext SD access modules installed, then upgraded to 26-07-2017 build through official update from settings, and after installation I rebooted the phone into recovery and installed magisk 13.3 (as you know when updating we lose magisk root) and it worked.
Then did a clean install of 26-07 build (thinking it will work) but nope.
Click to expand...
Click to collapse
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Jet45 said:
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Click to expand...
Click to collapse
I tried to do that again but I couldn't. As said:
In was on 19-07-2017 build with magisk 12 sdk and magisk manager 5.1.1 app, had magisk folder mount 0.8.5 and SD card access module, then on 26.07.2017 I received the weekly update, after update I rebooted the phone into recovery and instead of magisk 12 sdk I installed magisk 13.3 (for testing) and it worked. I tried doing that again but didn't worked so I don't know what to say lol.
Recycool said:
I tried to do that again but I couldn't. As said:
In was on 19-07-2017 build with magisk 12 sdk and magisk manager 5.1.1 app, had magisk folder mount 0.8.5 and SD card access module, then on 26.07.2017 I received the weekly update, after update I rebooted the phone into recovery and instead of magisk 12 sdk I installed magisk 13.3 (for testing) and it worked. I tried doing that again but didn't worked so I don't know what to say lol.
Click to expand...
Click to collapse
So I'll try to reproduce it at my side with that you've said, it may be a walktrough . Two brains to work on it may succeed
Jet45 said:
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Click to expand...
Click to collapse
I posted a logging of the problem on the main support thread, let's see what happens
https://forum.xda-developers.com/ap...sal-systemless-t3432382/page1765#post73249492
cross the fingers (I hope that you say like that in English)
Fingers crossed they sort it. Would love yo be able to use magisk again
Does anyone here have this issue on a stock ROM or is it just Lineage OS? From the log that was posted in the main support thread it looks like the Magisk installation was successful, but the system hangs on this one line before it can fully boot. I'm not qualified to read more than that out of the log though...
There's been some code added to GitHub in the last few days. Have anyone tried the latest unofficial snapshot? There was a new one built yesterday: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
Hi we got anymore news on this I have tried the latest beta one and it still gets stuck at booting.
It seems there is nothing to expect from nor magisk team neither lineage team. Nobody seem want to work on this really specific problem.
There are previous posts with this exact same issue that were never truly solved. I've tried the solutions that were found there but they never worked for me, and I think it didn't work for the OP as well.
Here's what I've done so far:
I've rooted my Samsung S5 G900W8 using something called CFAutoRoot through a software called Odin on my PC.
I then installed the latest TWRP, made sure it was the correct image/tar for my model.
I then tried installing Magisk, through TWRP recovery, by flashing? It returned an error saying "system patched by unsupported programs, please boot stock image"
I carefully grabbed the correct stock image for my phone, country and provider. (I didn't backup anything before starting)
I flashed the boot image through the TWRP recovery, and then flashed the latest Magisk which is v18.1 straight from the github source. This time it worked meaning the boot image fix worked.
I then grabbed the Magisk Manager apk straight from the github as well and installed it.
This is where I currently am stuck at. After opening the Magisk Manager app, initially it says Magisk isn't installed
But if I swipe up to refresh the page, it'll say that latest Magisk is installed. However, a popup will appear right after, saying "additional setup required".
If I click on yes, after a couple seconds it'll say "setup failed" and then just leave me from there. It says Latest Magisk is "installed" yes I dont have any option to do anything. No option to install Modules, or Hide Magisk.
I do the safetynet check however and it apparently says I pass
However, I downloaded a root checker app. When I didnt have Magisk installed, I passed the safetynet test. After I installed Magisk, even though the Magisk Manager app says I pass, this root checker app disagrees
I've tried installing 1 previous version behind the latest stable Magisk and same for Magisk Manager apk, all from the source github. Same results. I've come through a lot of obstacles to get to this point, but I'm at a complete dead end. Any help is heavily appreciated at this point. Please save me, I've spent hours upon hours to get this far!
I have pics except xda forums wont allow a new user like me to post them here. I also posted searching for help on Magisk Reddit and Pokemon Go Spoofing Reddit.
Other info:
Model Number: SM-G900W8
ANDROID VERSION: 6.0.1
ANDROID SECURITY PATCH LEVEL: FEB 1 2017
BASEBAND VERSION: G900W8VLU1DQB2
KERNEL VERSION: 3.4.0-10710752 [email protected] # 1
BUILD NUMBER: MMB29M.G900W8VLU1DQB2
Why spouting post after post about the same thing? Isn't it enough with just the one and then wait for someone to answer (spoiler: yes, it is)?
Did you remove the leftovers of the previous root at any point? Sounds to me like you've got to do some cleanup...
Some reading for you:
https://www.didgeridoohan.com/magis..._another_systemless_root_solution_to_MagiskSU
And, for any future posts about issues:
https://www.didgeridoohan.com/magisk/MagiskHelp
Didgeridoohan said:
Why spouting post after post about the same thing? Isn't it enough with just the one and then wait for someone to answer (spoiler: yes, it is)?
Did you remove the leftovers of the previous root at any point? Sounds to me like you've got to do some cleanup...
Some reading for you:
https://www.didgeridoohan.com/magis..._another_systemless_root_solution_to_MagiskSU
And, for any future posts about issues:
https://www.didgeridoohan.com/magisk/MagiskHelp
Click to expand...
Click to collapse
Sorry about that, I just figured I should post in the general support thread and a thread here. Kind of new on the what to and what not to, just desperately trying to get attention for an issue that doesn't have an answer. I'll try that out definitely though! Thank you!
Hi everyone! I have a little problem. I installed magisk cause I needed root to activate my volte, and then uninstalled magisk manager and flashed twrp again, however, my banking app still say I am rooted. Tryed to use magisk hide but my bank app still see it.
Are there some more files I have to delete to make my banking app work again? Why it still see root if uninstalled magisk?
Same problem here, my rom is:
[ROM][7.0][TW][Exynos][Stable]Refined Nougat N7FE Port 6.0
Welcome to the Galaxy note 4 Nougat project ONLY FOR Galaxy note 4 Exynos WARNING : PLEASE DO NOT PROCEED TO DOWNLOAD UNTIL YOU HAVE READ THE ENTIRE POST ! Some information you should know.. This is a full Note 7FE firmware port...
forum.xda-developers.com
After searching the forum thoroughly, trying multiple found solutions and trying to find the answer on my own I decided to ask here. What is the right procedure to clean flash A12 AOSP-based roms and getting root?
Some time ago, after updating to A11 rom, I noticed I can't use Magisk the way I used to to root my device - 'no ramdisk' status made me forget about rooting for a while. Now I want it back at any cost. This is why I want you to answer some of my questions, including the one above:
1. Is 'ramdisk: no' status caused by A11 and above versions?
2. Is there a way to have ramdisk status 'yes' on A12 ROM to root the device without having to patch boot.img?
3. Magisk installation doc has totally different way of rooting in my situation. According to it, for ramdisk status 'no' the only solution is 'Magisk in Recovery'. However, every time I saw someone talk about no ramdisk magisk patching, they were patching the boot image - it works fine and is even suggested by Magisk app. Who is wrong here and which solution is the right one?
4. Is there a way to get SafetyNet to pass on patched boot.img? Is there a way to get it to pass on a rooted A12 rom?
5. Some time ago, I have accidentally flashed european vendor instead of chinese one (I own chinese K20 Pro). I had no problems with it so I ran it for a few months and then flashed it back to chinese. Might this be the source of ramdisk issue?
Big thank you to anyone who replies. I have no important data on my device so there is no need for a data-safe solution. I feel like existing flashing/rooting guides seem outdated as they mention A10 at best. After more than 2 years of owning this device I still love it and am not going to replace it anytime soon and I hope there are still people like me! Cheers!
deadw0lf said:
After searching the forum thoroughly, trying multiple found solutions and trying to find the answer on my own I decided to ask here. What is the right procedure to clean flash A12 AOSP-based roms and getting root?
Some time ago, after updating to A11 rom, I noticed I can't use Magisk the way I used to to root my device - 'no ramdisk' status made me forget about rooting for a while. Now I want it back at any cost. This is why I want you to answer some of my questions, including the one above:
1. Is 'ramdisk: no' status caused by A11 and above versions?
2. Is there a way to have ramdisk status 'yes' on A12 ROM to root the device without having to patch boot.img?
3. Magisk installation doc has totally different way of rooting in my situation. According to it, for ramdisk status 'no' the only solution is 'Magisk in Recovery'. However, every time I saw someone talk about no ramdisk magisk patching, they were patching the boot image - it works fine and is even suggested by Magisk app. Who is wrong here and which solution is the right one?
4. Is there a way to get SafetyNet to pass on patched boot.img? Is there a way to get it to pass on a rooted A12 rom?
5. Some time ago, I have accidentally flashed european vendor instead of chinese one (I own chinese K20 Pro). I had no problems with it so I ran it for a few months and then flashed it back to chinese. Might this be the source of ramdisk issue?
Big thank you to anyone who replies. I have no important data on my device so there is no need for a data-safe solution. I feel like existing flashing/rooting guides seem outdated as they mention A10 at best. After more than 2 years of owning this device I still love it and am not going to replace it anytime soon and I hope there are still people like me! Cheers!
Click to expand...
Click to collapse
Although Magisk official guide on Github is not clear about, for MIUI you should patch boot.img, not recovery, and do not pay attention to Ramdisk no.
However, when patching boot.img, watch to the log window and you will see it reports there that it found Ramdisk
And that procedure works fine on A11 as well - I have it (MIUI 12.5.2 on my side)
I suppose you have the official A11 and you installed over custom A12 ROM).
Old Magisk v23 was released before A12, hence you should IMO go for the new Canary or Alpha 23016
Btw, you will be IMO better askung in the Magisk General XDA thread
zgfg said:
Although Magisk official guide on Github is not clear about, for MIUI you should patch boot.img, not recovery, and do not pay attention to Ramdisk no (when patching boot.img, watch to the log window and you will see it reports that it found Ramdisk)
And that procedure works fine on A11 as well - I have it (I suppose you have the official A11 and you installed over custom A12 ROM)
However, old Magisk v23 was released before A12, hence you should IMO go for the new Canary or Alpha 23016
Btw, you will be IMO better askung in the Magisk General XDA thread
Click to expand...
Click to collapse
Thank you for replying.
I am aware of Magisk Canary, I used it to root my current A12 rom. Yes, I flashed it over the latest chinese MIUI firmware. Is there any way to pass SafetyNet with it though?
deadw0lf said:
Thank you for replying.
I am aware of Magisk Canary, I used it to root my current A12 rom. Yes, I flashed it over the latest chinese MIUI firmware. Is there any way to pass SafetyNet with it though?
Click to expand...
Click to collapse
If you are on Canary 23016 (latest), you must enable Zygisk, and reboot
Then enable Enforce DenyList and go to Configure DenyList, enable Show System and OS apps, find Google Play Services and checkmark com.google.android.gms and
com.google.android.gms.unstable, and reboot again
If you were on the official, certified ROM, that would be enough to pass SafetyNet (since new Magisk app has no more the built-in SN checker, use one from PlayStore like YASNAC)
With your custom ROM you would probably need Universal Safety Net Fix= USNF 2.2.1 (latest).
Maybe even Magisk Hide Props Config (if USNF not enough) to spoof your unofficial/not Google certified ROM fingerprints - you will need to figure out (pain in the ass with custom ROMs)
zgfg said:
If you are on Canary 23016 (latest), you must enable Zygisk, and reboot
Then enable Enforce DenyList and go to Configure DenyList, enable Show System and OS apps, find Google Play Services and checkmark com.google.android.gms and
com.google.android.gms.unstable, and reboot again
If you were on the official, certified ROM, that would be enough to pass SafetyNet (since new Magisk app has no more the built-in SN checker, use one from PlayStore like YASNAC)
With your custom ROM you would probably need Universal Safety Net Fix= USNF 2.2.1 (latest).
Maybe even Magisk Hide Props Config (if USNF not enough) to spoof your unofficial/not Google certified ROM fingerprints - you will need to figure out (pain in the ass with custom ROMs)
Click to expand...
Click to collapse
This is exactly what I needed, thank you!
I dont have this model phone but i faced the same problem, i just flashed ArrowOS S along with magisk but i didnt realised it has now ramdisk no, before i was using AICP and it has ramdisk yes, so i installed latest version of magisk and the system updated but i dont have root anymore, what can i do?
I use OrangeBox for flashing
Edit: also it does replace the custom recovery?
The new Magisk is here and with it some major changes. One of the most important is the removal of support for "MagiskHide". There are many advanced users who have figured this all out already and few (maybe more) like me who are just kind of lost not knowing what should be exactly done to be able to update and be able to use Magisk as they were, before the update.
I was hoping that a kind soul would put up an easy step by step guide to help these users and at the same time it will avoid a lot of repetitive questions on the main thread. I personally spent a long time reading many pages and was not able to fully understand what should be done.
In my case all I want to achieve is to update and be able to hide Magisk like it was in the previous version. Should I start by un-hiding it first before doing the update?
(what and how and from where) should I add something that will replace the hiding function? Viola! these are the kind of simple questions that will help some of us get going
I hope that someone will bring his precious help
Yeah I unfortunately did my upgrade and fought with the whole process for 6 hours straight (lol) and I still don't know what I did exactly to even begin to write any instructions - other than 6 hours straight of reading and trying and hoping .....
Not sure if you have been able to refer to this which helped me.... But, I also have an very basic understanding of how my device (OnePlus 7T) works with Magisk... Hope this helps. May be see if your specific device has the instructions already posted in the device specific forum here?
Installation
The Magic Mask for Android
topjohnwu.github.io
I've not used the Magisk hide cause I haven't needed it - BUT, it's still available in the latest Magisk Manager (24.1) in the Magisk Manager settings. I'm only using the systemless hosts module (included in Magisk manager settings) for Adaway, and the universal safety net fix to get Google Play store to say my device is certified.
But I don't know what device you have nor do I know the specific ROM you are using.
Sounds like you have root already so I'm thinking that's the worst of this behind you if you've already done that much yourself. Sounds like it's a basic case of update the Magisk Manager app from itself then determine the method appropriate for root to update which could be through the Manager app or like I chose to use the boot IMG then patch that then install since my device has no working TWRP. That, and once I updated the manager app and panicked so I uninstalled it to try and downgrade to v23 .... Good luck and may be just don't update just yet if there is no specific need to at this time. Take your time and read and proceed when comfortable.
Please:
Start with your preferred method of backing up everything first.
Also, may be consider if it's necessary to update and why??? I'm on stock Andriod 11 and this Magisk update make me think it's intended to be more for those on Android 12 - but I could also assume wrongly.
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
That's the thread I'm reading now...
Thanks a lot for your reply wugga3. I also on my side found two very helpful posts. They explain the basics (just to get started) and to make the update . I hope with the information gathered I will be able to do the update without messing things up!
[Discussion] Google Pay Magisk Discussion Thread
This thread is inspired by the PoGo Magisk discussion thread. It's meant to keep the clutter of "Google Pay doesn't work" posts out of the main Magisk threads. Please use this to discuss issues with Google Pay and possible solutions. There's a...
forum.xda-developers.com
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Good and good luck...
One problem and probably the only problem I really had was self inflicted for not following the instructions properly and that was to uninstall any Magisk modules first or at that the appropriate step.
Other than that... still don't know your device or rom etc. Your device specific or rom specific forums may be able to provide you with much better assistance from members that have the same rom/device as you.
wugga3 said:
Good and good luck...
One problem and probably the only problem I really had was self inflicted for not following the instructions properly and that was to uninstall any Magisk modules first or at that the appropriate step.
Other than that... still don't know your device or rom etc. Your device specific or rom specific forums may be able to provide you with much better assistance from members that have the same rom/device as youI
Click to expand...
Click to collapse
I am using LineageOS 18.1 Android 11 for Samsung Galaxy Note 3 and I have twrp as recovery. Magisk 2.30 is already installed and device is rooted. I have no modules installed and in Magisk settings I have only MagiskHide enabled. All other settings are set to default. On Samsung Note3 forum there is no talk about this (understandable as the device is very old).
Ok great and is there any discussion for lineage 18.1 and root/update?
Since it's lineage 18 and based on Andriod 11 - I have to wonder if there is even the need to update Magisk as my limited understanding is that the Magisk update is aimed at Andriod 12? Other than that... I should expect from my prior understandings of Samsung that nothing much has changed with respect to root and updates of Magisk. Not much help but hopefully enough. May be best to wait until for now and usually I do also wait until all the facts are in and the bugs are sorted out (if any...) before I update if unnecessary.
Thanks wugga3,
I disabled "Check for updates" in Magisk app and decided to keep the older 2.30 version for now. Everything is working fine and so there is no reason to fix something which is not broken. The only reason I thought That I should update was a real advantage over the older version or a security weakness being fixed in the new one.
I am even seeing some people asking for help on how to downgrade! Anyway as you said wisely, it;s not after all a bad idea to wait a little to see how things work out for those who have upgraded and have new issues fixed before taking the jump.
Moving from 23.0 to 24.1 is straightforward
1. Update app
2. Update boot (Magisk) to 24.1, reboot
3. Enable Zygisk, reboot
4. Enforce Deny List, reboot
5. Install module USNF, reboot
6. Configure Deny List. Don't worry about Play Service because USNF will take care of it. Add any app detected root into it, and reboot every time it's updated
7. Install Fox Module manager and pick module you want
mingkee said:
Moving from 23.0 to 24.1 is straightforward
1. Update app
2. Update boot to 24.1, reboot
3. Enable Zygisk, reboot
4. Enforce Deny List, reboot
5. Install module USNF, reboot
6. Configure Deny List. Don't worry about Play Service because USNF will take care of it. Add any app detected root into it, and reboot every time it's updated
7. Install Fox Module manager and pick module you want
Click to expand...
Click to collapse
Thanks a lot for your post mingkee,
I am sure many like me will be happy and appreciate reading this instead of having to go through many pages and still not be totally sure what to do
Allow me to just ask one question as I did not understand the second option of your instruction:
I update Magisk from the application itself. Once updated what do you mean by update boot to 24.1? This is to be done in Magisk itself?
rezpower said:
Thanks a lot for your post mingkee,
I am sure many like me will be happy and appreciate reading this instead of having to go through many pages and still not be totally sure what to do
Allow me to just ask one question as I did not understand the second option of your instruction:
I update Magisk from the application itself. Once updated what do you mean by update boot to 24.1? This is to be done in Magisk itself?
Click to expand...
Click to collapse
After updated app to 24.1, you will see another update on top of the app (Magisk). Direct install would be the simplest method
mingkee said:
Moving from 23.0 to 24.1 is straightforward
1. Update app
2. Update boot (Magisk) to 24.1, reboot
3. Enable Zygisk, reboot
4. Enforce Deny List, reboot
5. Install module USNF, reboot
6. Configure Deny List. Don't worry about Play Service because USNF will take care of it. Add any app detected root into it, and reboot every time it's updated
7. Install Fox Module manager and pick module you want
Click to expand...
Click to collapse
this should be pinned somewhere, very simple and worked fine on my Poco F3 using miui.eu & android 11
thanks a lot