Database Develop

Do Magisk need SuperSU or something else?

I am about to install Magisk 12.0 but never used Magisk before and suddenly unsure if I need something together with Magisk, like SuperSU or similar?
BTJ

Ok, think I found it.. I can use MagiskSU and that one comes with Magisk-12.zip file?
Also, I see there is some talk about needing to install latest dm-verity and forced encryption disabler? I am running stock OOS 4.1.3 and just need root and perhaps install a custom kernel, for now .

Never mind.. Took a chance and installed twrp, Magisk 12 and Franco kernel and everything seems to be working...

xda890 said:
Never mind.. Took a chance and installed twrp, Magisk 12 and Franco kernel and everything seems to be working...
Click to expand...
Click to collapse
Exact same setup I'm running and it's working great! Time for you to start making some modules next...

Viper4Android Pie Compatible???

As the title states ...v4a is it compatible with pie? Im rooted running a custom rom rooted with magisk. Installed v4a thru magisk manager it installs but i get the install driver /re-install driver message everytime. Is it an workaround to get it working?

recepo1 said:
As the title states ...v4a is it compatible with pie? Im rooted running a custom rom rooted with magisk. Installed v4a thru magisk manager it installs but i get the install driver /re-install driver message everytime. Is it an workaround to get it working?
Click to expand...
Click to collapse
working fine here. maybe a root/magisk issue.

bober10113 said:
working fine here. maybe a root/magisk issue.
Click to expand...
Click to collapse
What rom are you on and which version of magisk are you running?

recepo1 said:
What rom are you on and which version of magisk are you running?
Click to expand...
Click to collapse
infinity rom.
magisk v18 and also newer test canary builds.
but prety sure its an issue where you don't wait 3 minutes after rebooting before doing actions that require root.
and not sure to which extent you tried to make magisk work with various files and mods but maybe you should just factory wipe and try and get magisk working before anything else. also mayke sure busybox is installed. and dont forget that 3 minute rule after a reboot.

bober10113 said:
infinity rom.
magisk v18 and also newer test canary builds.
but prety sure its an issue where you don't wait 3 minutes after rebooting before doing actions that require root.
and not sure to which extent you tried to make magisk work with various files and mods but maybe you should just factory wipe and try and get magisk working before anything else. also mayke sure busybox is installed. and dont forget that 3 minute rule after a reboot.
Click to expand...
Click to collapse
Thanks im sure it maybe an magisk issue im running 17.3 because i kept losing root on v18. I acquire root with v4a but it freezes and then keeps telling me to reinstall driver after reboot. I will try the 3 minute rule though..thank you. You installed v4a directly thru magisk or flashed a different version?

recepo1 said:
Thanks im sure it maybe an magisk issue im running 17.3 because i kept losing root on v18. I acquire root with v4a but it freezes and then keeps telling me to reinstall driver after reboot. I will try the 3 minute rule though..thank you. You installed v4a directly thru magisk or flashed a different version?
Click to expand...
Click to collapse
v3.3 on magisk dated of jan. 16th.
use aroma option. it will reboot on its own from magisk console and the just follow the automated steps in recovery

bober10113 said:
v3.3 on magisk dated of jan. 16th.
use aroma option. it will reboot on its own from magisk console and the just follow the automated steps in recovery
Click to expand...
Click to collapse
Thank you appreciate your help i will give it a try

I have tried everything for hours to get viper4android to work with no avail until now. Go to the xda download page and select the beta version. Boom. It works. I know you might have long forgot this or already figured it out but I had to share

old legacy magisk module has been working for months and months.

Questions regarding updating Magisk

Hi everyone!
It's been about a year and a half since I first installed Magisk on my phone with TWRP and considering that I now noticed I'm getting SafenityNet API error, I wanted to update my Magisk to the latest version and install the Universal SafetyNet module as well to fix this issue.
I just have some questions regarding this:
I'm running Magisk Manager 7.5.1 & Magisk 20.4 repacked and with Magisk Hide, how can I update from Magisk 20.4 to Magisk 23? My phone shows 22.1 as the latest.
Before updating do I need to restore Magisk Manager to the original package and app names?
Will updating Magisk affect my already installed Modules or will they stay in effect?
I'm using a Xiaomi with Android 9 Pie and MIUI Global 11.0.5.0
Thanks in advance.

reldinado said:
Hi everyone!
It's been about a year and a half since I first installed Magisk on my phone with TWRP and considering that I now noticed I'm getting SafenityNet API error, I wanted to update my Magisk to the latest version and install the Universal SafetyNet module as well to fix this issue.
I just have some questions regarding this:
I'm running Magisk Manager 7.5.1 & Magisk 20.4 repacked and with Magisk Hide, how can I update from Magisk 20.4 to Magisk 23? My phone shows 22.1 as the latest.
Before updating do I need to restore Magisk Manager to the original package and app names?
Will updating Magisk affect my already installed Modules or will they stay in effect?
I'm using a Xiaomi with Android 9 Pie and MIUI Global 11.0.5.0
Thanks in advance.
Click to expand...
Click to collapse
Maybe let Magisk Manager take you to v22.1, then you'll be one step away from v23.0 and hopefully at some point it becomes available. If upgrading to v22.1 succeeds you'll end up with one app that is Magisk SU and the manager all in one. I mention this in case you're wondering why Magisk Manager disappeared.
I don't understand what you mean about restoring Magisk Manager "to the original package and app names" but your modules should still work after upgrading. Worst case would be a module that didn't keep up with Magisk and isn't supported anymore.

reldinado said:
Before updating do I need to restore Magisk Manager to the original package and app names?
Click to expand...
Click to collapse
Yes, you do. See the v22.0 release notes:
https://topjohnwu.github.io/Magisk/releases/22000.html

Didgeridoohan said:
Yes, you do. See the v22.0 release notes:
https://topjohnwu.github.io/Magisk/releases/22000.html
Click to expand...
Click to collapse
Ahh, the question makes sense now. I've never needed to conceal Magisk.

Didgeridoohan said:
Yes, you do. See the v22.0 release notes:
https://topjohnwu.github.io/Magisk/releases/22000.html
Click to expand...
Click to collapse
Thanks to both of you for the clarifications.
I will unhide/restore the manager and will install 22 before going onward to 23.

The right A12 ROMs rooting procedure

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?

Guide for rooting

Hello,
I have a second hand p20 pro (C432) with emui 12 on it. I succesfully downgrade to emui 9.1, fw on 9.1.0.387, and got my bootloader unlocked.
Twrp by pretorian installed but can't do anything with it. Data is encrypted, i just need to flash magisk. What's the way to go?
Thx for those who could help,guide me.

aIecxs said:
read Huawei section (deleted)
https://web.archive.org/web/2020092...ithub.io/Magisk/install.html#emui-9-or-higher
Click to expand...
Click to collapse

Thank you sir, i'm now rooted.

But now, contacts, messages and phone dialer keep crashing....uninstalled magisk and everything is fine. Reflashed magisk and same problems

try older Magisk. install the apk and set this file as custom channel. then patch the kernel ramdisk.
https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad86/stable.json

i patch kernel.img not recovery_ramdis.img? or the 2?
i'm now with 21.4 and manager 8.0.7 but dialer still crashing (just recovery patched)

then it is probably not caused by magisk itself. maybe factory reset will help.

Maybe i messed to much when debloating fw, went with fresh install before flashing magisk and all working! thx for your help and advices