Database Develop

MagiskSU Install Help

HTC One M9
Venom Rom - ViperOne
Phh's SuperUser installed
Magisk 11.1 installed
Android N
Flashed a new rom (Viper) and it gave me the option to install PHH's SuperUser and Magisk, so I did. Once setting up the device I updated Magisk to 11.1 and installed the PHH's SuperUser (Magisk version) off of the official RT thread here on XDA.
Magisk Manager says I have Magisk 11.1 installed correctly and it is properly rooted, but my phone does not pass safety net, instead it says "CTS Profile Mismatch." After looking through the settings I saw the option for Magisk Hide so switched it off and back on and it says...
"You are not rooted with MagiskSU, using Magisk Hide might not be enough! It's not officially supported, and you would need additional tools (e.g Suhide) to pass Safety Net."
Can someone please help me with what to do?
Thank you,
Ollie Bednal.

obednal97 said:
HTC One M9
Venom Rom - ViperOne
Phh's SuperUser installed
Magisk 11.1 installed
Android N
Flashed a new rom (Viper) and it gave me the option to install PHH's SuperUser and Magisk, so I did. Once setting up the device I updated Magisk to 11.1 and installed the PHH's SuperUser (Magisk version) off of the official RT thread here on XDA.
Magisk Manager says I have Magisk 11.1 installed correctly and it is properly rooted, but my phone does not pass safety net, instead it says "CTS Profile Mismatch." After looking through the settings I saw the option for Magisk Hide so switched it off and back on and it says...
"You are not rooted with MagiskSU, using Magisk Hide might not be enough! It's not officially supported, and you would need additional tools (e.g Suhide) to pass Safety Net."
Can someone please help me with what to do?
Thank you,
Ollie Bednal.
Click to expand...
Click to collapse
Remove PHH Superuser completely - including apk - and re-flash Magisk.
osmOsis's UnSu script does a good job of removing all traces of root.

jhedfors said:
Remove PHH Superuser completely - including apk - and re-flash Magisk.
osmOsis's UnSu script does a good job of removing all traces of root.
Click to expand...
Click to collapse
Thank you for your quick response!
Where and how do I find and install the original boot.img to remove phh's superuser?

obednal97 said:
Thank you for your quick response!
Where and how do I find and install the original boot.img to remove phh's superuser?
Click to expand...
Click to collapse
The original boot image is what is in the ROM zip. However, as you mentioned that root is preinstalled, you should flash osmOsis's UnSu zip to get rid of root before reflashing Magisk.

jhedfors said:
The original boot image is what is in the ROM zip. However, as you mentioned that root is preinstalled, you should flash osmOsis's UnSu zip to get rid of root before reflashing Magisk.
Click to expand...
Click to collapse
Thank you very much for your help, just doing it now ?

jhedfors said:
The original boot image is what is in the ROM zip. However, as you mentioned that root is preinstalled, you should flash osmOsis's UnSu zip to get rid of root before reflashing Magisk.
Click to expand...
Click to collapse
Just done it all! It works beautifully!
I messed up the first time cause I couldn't remove Superuser app completely but I got round that and did it all again and its all green lights
Installed Magisk ☑
Rooted ☑
Safety net passed ☑
Thank you very much!

obednal97 said:
Just done it all! It works beautifully!
I messed up the first time cause I couldn't remove Superuser app completely but I got round that and did it all again and its all green lights
Installed Magisk ☑
Rooted ☑
Safety net passed ☑
Thank you very much!
Click to expand...
Click to collapse
Awesome!

cts profile mismatch
i have a xiaomi device which has epic rom based on android 6.0 with magisksu preinstalled by i cant bypass safetynet check either. what should i do?? i did a reinstall of magisk but it didn't helped.

aldo-000 said:
i have a xiaomi device which has epic rom based on android 6.0 with magisksu preinstalled by i cant bypass safetynet check either. what should i do?? i did a reinstall of magisk but it didn't helped.
Click to expand...
Click to collapse
If the ROM has Magisk pre-installed, you may want to check in the ROM thread. Otherwise try everything I suggested in this thread.

jhedfors said:
If the ROM has Magisk pre-installed, you may want to check in the ROM thread. Otherwise try everything I suggested in this thread.
Click to expand...
Click to collapse
uninstalling magisk, still can't bypass safetynet test but i can play pokemon go., wired.... i will ask about the rom. do you another way making pg playable on rooted device??

aldo-000 said:
uninstalling magisk, still can't bypass safetynet test but i can play pokemon go., wired.... i will ask about the rom. do you another way making pg playable on rooted device??
Click to expand...
Click to collapse
Did you do what I suggested? If so, can you say what you did?

aldo-000 said:
i have a xiaomi device which has epic rom based on android 6.0 with magisksu preinstalled by i cant bypass safetynet check either. what should i do?? i did a reinstall of magisk but it didn't helped.
Click to expand...
Click to collapse
Is it based on Developer or Stable ROM? Develop ROMs can't pass SafetyNet because they don't have the correct CTS profile. If it's based on Stable ROM, try flashing Global Stable again and Epic ROM afterwards, that might or might not help, no guarantees. You are only guaranteed to pass CTS profile match with Global Stable. But like you said, if Pokemon Go works you don't really need CTS profile.

i have moto E 3g 2 gen[OTUS] with Recusrtion remix 5.8.1 android 7
have flashed magisk but it gives error :1 error installing magisk 11.1 , while i did same with moto e [Condor] 1st gen and got success everything is working
even i clean the old su
can you help @jhedfors

Hi, I've just switched over to magisksu from supersu. I did as you suggested above... flashed unSu and the boot image and magisk. Then installed the Magisk manager from play store. It shows the device is rooted and that latest magisk is installed. However, safenet check fails.
Any suggestions on what to do?
Thanks

neptune_ said:
Hi, I've just switched over to magisksu from supersu. I did as you suggested above... flashed unSu and the boot image and magisk. Then installed the Magisk manager from play store. It shows the device is rooted and that latest magisk is installed. However, safenet check fails.
Any suggestions on what to do?
Thanks
Click to expand...
Click to collapse
Reboot with setting everything enable except disabling magisk it worked for me

Rush94 said:
Reboot with setting everything enable except disabling magisk it worked for me
Click to expand...
Click to collapse
Tried that, but SafetyNet check still fails

neptune_ said:
Tried that, but SafetyNet check still fails
Click to expand...
Click to collapse
Try enabling hide magisk enable busybox and then reboot

Rush94 said:
Reboot with setting everything enable except disabling magisk it worked for me
Click to expand...
Click to collapse
Rush94 said:
Try enabling hide magisk enable busybox and then reboot
Click to expand...
Click to collapse
Tried that too, still fails

neptune_ said:
Tried that too, still fails
Click to expand...
Click to collapse
Try some of the tips here:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828

Didgeridoohan said:
Try some of the tips here:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Click to expand...
Click to collapse
Thanks. I did read through there and tried some suggestions. Nothing seems to work.
I may have to use a rom that comes packaged with magisk?
Sent from my LG G3 using XDA Labs

How to go from normal root to systemless root for Magisk?

Title says it all. Im currently using using SuperSU so looking for Systemless root and looking for Xposed to work as well.

Remove SuperSU, flash Magisk. That's basically it... If you have issues on the way there's lots of info in the support read and some things to try here:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828

Didgeridoohan said:
Remove SuperSU, flash Magisk. That's basically it... If you have issues on the way there's lots of info in the support read and some things to try here:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Click to expand...
Click to collapse
Do I remove SuperSU thru it's manager and then flash Magisk?

riahc3 said:
Do I remove SuperSU thru it's manager and then flash Magisk?
Click to expand...
Click to collapse
Yes, choosing the full unroot option. It is also good to have the unsu zip by osm0sis handy, but the full unroot option should work.

jhedfors said:
Yes, choosing the full unroot option. It is also good to have the unsu zip by osm0sis handy, but the full unroot option should work.
Click to expand...
Click to collapse
This just flash Magisk? No Xposed issues?

riahc3 said:
This just flash Magisk? No Xposed issues?
Click to expand...
Click to collapse
I don't use Xposed, as it does not work on Nougat. You will need to install the Xposed module in the Magisk Downloads tab.

jhedfors said:
I don't use Xposed, as it does not work on Nougat. You will need to install the Xposed module in the Magisk Downloads tab.
Click to expand...
Click to collapse
Im on 6.0 so I do and its important.
Well, here goes nothing I guess....

When SuperSU asked if I wanted to recover the boot image (I think it was that) I said no.
Issues with that?

Checking patch status
SuperSU patched boot detected!
Adding auto patch scirpt for supersu
SuperSU image mount failed...
Will still try to complete installation
Device still does boot...which I guess is still a good sign.

Says Ive lost root....
Magisk does say it is installed.

riahc3 said:
Checking patch status
SuperSU patched boot detected!
Adding auto patch scirpt for supersu
SuperSU image mount failed...
Will still try to complete installation
Device still does boot...which I guess is still a good sign.
Click to expand...
Click to collapse
Reflashed the SuperSU zip.....Opening Magisk Manager.....its currently stuck opening it. Only the logo with the background appears.
Android says "Magisk Manager is not responding".
OK! Wow, that took a while lol....
Latest version of Magisk installed....
Properly rooted
279:SUPERSU
Checking SafetlyNet Failed: CTS Profile Mismatch

riahc3 said:
Reflashed the SuperSU zip.....Opening Magisk Manager.....its currently stuck opening it. Only the logo with the background appears.
Android says "Magisk Manager is not responding".
OK! Wow, that took a while lol....
Latest version of Magisk installed....
Properly rooted
279:SUPERSU
Checking SafetlyNet Failed: CTS Profile Mismatch
Click to expand...
Click to collapse
CTS profile mismatch will happen if you're using SuperSU.
The one thing that went wrong was you saying no to restoring the boot image backup. If you want to use MagiskSU you'll need to flash it over a boot image that doesn't have the SuperSU patches.

Didgeridoohan said:
CTS profile mismatch will happen if you're using SuperSU.
The one thing that went wrong was you saying no to restoring the boot image backup. If you want to use MagiskSU you'll need to flash it over a boot image that doesn't have the SuperSU patches.
Click to expand...
Click to collapse
At this point, is there is a way to fix it?
I have gotten also gotten systemless Xposed installed

riahc3 said:
At this point, is there is a way to fix it?
I have gotten also gotten systemless Xposed installed
Click to expand...
Click to collapse
If you're happy with your current setup, leave it be. If you need to pass SafetyNet (you'll need to disable Xposed for that) you'll have to start over.

Didgeridoohan said:
If you're happy with your current setup, leave it be. If you need to pass SafetyNet (you'll need to disable Xposed for that) you'll have to start over.
Click to expand...
Click to collapse
Doesnt systemless Xposed pass SafetyNet?

riahc3 said:
Doesnt systemless Xposed pass SafetyNet?
Click to expand...
Click to collapse
No.

Didgeridoohan said:
No.
Click to expand...
Click to collapse
Oh! My mistake then
I could careless about SafetyCheck as I need Xposed modules.
Besides, that, then Magisk is working? That was pretty simple. Thank you for your help.
Reading thru your thread, I cant really see what SafetyCheck implies. Does it just affect that stupid Pokemon crap? I imagine it affects more things like banks but I dont think mines will depend on that.

riahc3 said:
Oh! My mistake then
I could careless about SafetyCheck as I need Xposed modules.
Besides, that, then Magisk is working? That was pretty simple. Thank you for your help.
Reading thru your thread, I cant really see what SafetyCheck implies. Does it just affect that stupid Pokemon crap? I imagine it affects more things like banks but I dont think mines will depend on that.
Click to expand...
Click to collapse
Magisk works fine with SuperSU. It's if you'd ever want to hide root from some process or app that you might have some trouble, since Magisk Hide is developed with MagiskSU in mind.
There are some banking apps, Android Pay, Pokemon Go other apps that utilise SafetyNet. I do believe that more and more apps will use in the future and the cat and mouse game of hiding root is gonna continue...

riahc3 said:
Im on 6.0 so I do and its important.
Well, here goes nothing I guess....
Click to expand...
Click to collapse
I am also on android 6.0.1 and need to install magisk to work with safetynet to install games like pokemon , supermario run etc . Why do you say Xposed is required? also, did full unroot from within superSU app worked for you or you flashed UnSu for that?
Thanks

anshulsingh said:
I am also on android 6.0.1 and need to install magisk to work with safetynet to install games like pokemon , supermario run etc . Why do you say Xposed is required? also, did full unroot from within superSU app worked for you or you flashed UnSu for that?
Thanks
Click to expand...
Click to collapse
I use Xposed modules in my daily life and cannot afford to be without them.

Magisk safety net fails not sure why.

Hi
I'm using a Samsung Galaxy S4
I rooted the stock Samsung rom with SuperSU prior to install Magisk
At first I couldn't install 13.3 I had to install 12.0 because of some unknown reason installing 13.3 I got the error image mount failed same with all previous 13. versions however now 13.3 is now installed and SuperSU isn't installed.
When I run the SafetyNet Check in Magisk it reports:
ctsProfile: false
basicIntegrity: false
I want to be able to use apps like Android pay and such
Can someone please help me with getting this to work
Thanks!

Magisk v12.0 can't pass SafetyNet without workarounds like Universal SafetyNet fix module (and since the last update to SafetyNet a few days ago I've no idea if that works either).
You can't use Magisk to pass SafetyNet with SuperSU installed.
Here's some reading for you:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Pro tip: Try using the search function and browse the stickied threads before posting. There are very few things that hasn't been covered already in one way or another...

Didgeridoohan said:
Magisk v12.0 can't pass SafetyNet without workarounds like Universal SafetyNet fix module (and since the last update to SafetyNet a few days ago I've no idea if that works either).
You can't use Magisk to pass SafetyNet with SuperSU installed.
Here's some reading for you:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Pro tip: Try using the search function and browse the stickied threads before posting. There are very few things that hasn't been covered already in one way or another...
Click to expand...
Click to collapse
I've got 13.3 installed and SuperSU isn't installed plus I've already read a lot on this subject and most of my searches did nothing for me that's why I thought I would make a thread to see if anyone could help me.

AyanamiRei0 said:
I've got 13.3 installed and SuperSU isn't installed plus I've already read a lot on this subject and most of my searches did nothing for me that's why I thought I would make a thread to see if anyone could help me.
Click to expand...
Click to collapse
That was not very clear from your first post...
If you haven't already, start by reading through the link I posted. You wan't post #4.

Didgeridoohan said:
That was not very clear from your first post...
If you haven't already, start by reading through the link I posted. You wan't post #4.
Click to expand...
Click to collapse
Interesting trying to start magiskhide manually does nothing.

You could have remnants of Su on your phone. Even if you use the full uninstall method you can have leftovers. Tried a complete fresh reinstall?

phuhcue said:
You could have remnants of Su on your phone. Even if you use the full uninstall method you can have leftovers. Tried a complete fresh reinstall?
Click to expand...
Click to collapse
Oh it's working fine now installing Lineage OS and then install Magisk and it works perfectly.

With me my experiments with magisk in the past left some files in my data partition behind which makes safetynet fail.
I found them by going into twrp recovery, starting and adb shell and then executing find . | grep -i magisk
the two files i found were:
data/data/com.google.android.gms/files/backup_diff_script/com.topjohnwu.magisk
data/property/persist.magisk.hide
i deleted them with rm and safety net worked again.
So I can confirm that for my phone, unlocked bootloader, custom modem and custom recovery does not matter at all. But if your filesystem still contains traces of magisk, is a nono for google safetynet, pretty silly this road they are taking here.

safety net
i have the same problem on galaxy note 3 with magisk 15.3 on my galaxy s7 everything is ok but in note 3 i have safety net false...
can anyone help me?

spanpana said:
i have the same problem on galaxy note 3 with magisk 15.3 on my galaxy s7 everything is ok but in note 3 i have safety net false...
can anyone help me?
Click to expand...
Click to collapse
Old device... If the kernel version is lower than 3.8 it'll likely not have support for mount namespace and MagiskHide won't work. A custom kernel or ROM might work...

Didgeridoohan said:
Old device... If the kernel version is lower than 3.8 it'll likely not have support for mount namespace and MagiskHide won't work. A custom kernel or ROM might work...
Click to expand...
Click to collapse
thank's for your reply...!
i have custom rom resurection remix v.5.8.2 but i didnt change the kernel can you explain me how to do that please because i don't know...?

spanpana said:
thank's for your reply...!
i have custom rom resurection remix v.5.8.2 but i didnt change the kernel can you explain me how to do that please because i don't know...?
Click to expand...
Click to collapse
Check your kernel version first (usually found in Settings - About Phone). If it's less than 3.8, ask for help in your device's forum for if there's any custom kernels or ROMs available with an updated kernel.

Didgeridoohan said:
Check your kernel version first (usually found in Settings - About Phone). If it's less than 3.8, ask for help in your device's forum for if there's any custom kernels or ROMs available with an updated kernel.
Click to expand...
Click to collapse
ok my friend thank you very much...!:laugh::good:

Didgeridoohan said:
Old device... If the kernel version is lower than 3.8 it'll likely not have support for mount namespace and MagiskHide won't work. A custom kernel or ROM might work...
Click to expand...
Click to collapse
That's interesting. I get the same message on my old phone (running the 3.4.113 kernel), but I'm unable to even open Mario Run if MagiskHide is disabled. But when it's enabled, the game runs just fine. Is that normal? I thought Mario Run made use of SafetyNet... I'm using microG + DroidGuard Helper. I've tried running Android Pay, but I get this error message. But I'm not even sure if Android Pay is supposed to work since I'm using microG... What other apps use SafetyNet so I can try them?
Thanks.

robotsrules said:
That's interesting. I get the same message on my old phone (running the 3.4.113 kernel), but I'm unable to even open Mario Run if MagiskHide is disabled. But when it's enabled, the game runs just fine. Is that normal? I thought Mario Run made use of SafetyNet... I'm using microG + DroidGuard Helper. I've tried running Android Pay, but I get this error message. But I'm not even sure if Android Pay is supposed to work since I'm using microG... What other apps use SafetyNet so I can try them?
Thanks.
Click to expand...
Click to collapse
MagiskHide can't do it's thing to hide itself on such an old kernel, but it can still hide sensitive prop values. That's why Mario Run works... IIRC it looks for ro.debuggable, on of the props changed to "safe" values by MagiskHide.

Didgeridoohan said:
MagiskHide can't do it's thing to hide itself on such an old kernel, but it can still hide sensitive prop values. That's why Mario Run works... IIRC it looks for ro.debuggable, on of the props changed to "safe" values by MagiskHide.
Click to expand...
Click to collapse
Oh, I get it now... Thanks

Can't get Magisk to work on Pixel

I have pixel (sailfish) running lineage 15.1 w/ microG and I've followed the exact steps from the official Magisk install page using Magisk v18.1 with manager 7.0 only to get the same safetynet api error. Ive even tried other suggested installation methods from: https://android.gadgethacks.com/how-to/install-magisk-your-pixel-pixel-xl-0177522/
And it left me in a bootloop whereby I had to wipe and reinstall everything.
Anybody please help!

If you can get Magisk up and running, but get a SafetyNet API error when trying to check SafetyNet in the Manager, the problem lies elsewhere, most likely with your microG setup (or possibly that the Manager snet.apk hasn't downloaded properly, clear data for the Manager to fix that).
Test with a separate SafetyNet checker, and also test MagiskHide by adding a root app to the Hide list (if it can't detect root, MagiskHide works). If you get the same error with the other app we know that the problem likely isn't with Magisk.

Sorry for the newb question, but how do you clear Manager data? Thanks.

conundrew said:
Sorry for the newb question, but how do you clear Manager data? Thanks.
Click to expand...
Click to collapse
By going to the app information in the Android settings.

Still doesn't work. Getting the same message after everything you've suggested.

Even with a separate SafetyNet checker app? In that case it is very likely that it is your microG setup that isn't working. Ask for advice in your ROM thread.

Didgeridoohan said:
If you can get Magisk up and running, but get a SafetyNet API error when trying to check SafetyNet in the Manager, the problem lies elsewhere, most likely with your microG setup (or possibly that the Manager snet.apk hasn't downloaded properly, clear data for the Manager to fix that).
Test with a separate SafetyNet checker, and also test MagiskHide by adding a root app to the Hide list (if it can't detect root, MagiskHide works). If you get the same error with the other app we know that the problem likely isn't with Magisk.
Click to expand...
Click to collapse
Didgeridoohan said:
Even with a separate SafetyNet checker app? In that case it is very likely that it is your microG setup that isn't working. Ask for advice in your ROM thread.
Click to expand...
Click to collapse
Not sure exactly what I did but when I cleared Manager data and changed some microG settings, I was able to finally get SafetyNet Check Success but now it says: ctsProfile: false and basicIntegrity: false. Any advice?

conundrew said:
Not sure exactly what I did but when I cleared Manager data and changed some microG settings, I was able to finally get SafetyNet Check Success but now it says: ctsProfile: false and basicIntegrity: false. Any advice?
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet

Didgeridoohan said:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
Click to expand...
Click to collapse
So I did a clean install of LineageOS 16 only (no microG) and then installed Magisk following installation instructions and when I opened up Magisk Manager I don't see the option to do SafetyNet Check anymore. When I ran SafetyNet Test it said "GooglePlayServices is not available on this device". I was given the impression that microG was the problem which is why I installed LineageOS without microG, but it's still not working. Please help!

If you have neither Gapps or MicroG installed there's no way you can use anything SafetyNet related. It's Google's system, so you're going to have to install one or the other...

Didgeridoohan said:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
Click to expand...
Click to collapse
Didgeridoohan said:
If you have neither Gapps or MicroG installed there's no way you can use anything SafetyNet related. It's Google's system, so you're going to have to install one or the other...
Click to expand...
Click to collapse
Thank you!
Is there any benefit or even necessary to install a custom kernel, like ElementalX, for getting Magisk to work properly? Thanks.

conundrew said:
Thank you!
Is there any benefit or even necessary to install a custom kernel, like ElementalX, for getting Magisk to work properly? Thanks.
Click to expand...
Click to collapse
No.

Safetynet checks failing with Magisk 20.4

hi, i just flashed my xiaomi mix phone with Magisk 20.4. everything is new but the safetynet checks are failing.
i have previously tried on riru and edxposed. the checks say YES but i still cannot load pokemon go. i think those fixes are fake and not working, Google seems to be able to detect it still.
Can anyone help?
thanks.

jasonjiangyu said:
hi, i just flashed my xiaomi mix phone with Magisk 20.4. everything is new but the safetynet checks are failing.
i have previously tried on riru and edxposed. the checks say YES but i still cannot load pokemon go. i think those fixes are fake and not working, Google seems to be able to detect it still.
Can anyone help?
thanks.
Click to expand...
Click to collapse
Having the exact same issue with my Mix 3. Just flashed a few moments ago. Been looking at the other threads and it seems that no fix works as of now. Hoping that it isn't permanent as Google is cracking down on unlocked bootloaders.

Try to hide what you want via magisk hide.

Sorry, but that is not helpful. Same thing here. Device passed SafetyNet on 20.3. After upgrade to 20.4 it fails. What can I do to figure out what changed?

please refer here to set it up in your phone.
Be notice: If you don't use edxposed, just skip it. If you do, please remember to install canary version of edxposed in Edxposed manager !
Kris

Kris Chen said:
please refer here to set it up in your phone.
Be notice: If you don't use edxposed, just skip it. If you do, please remember to install canary version of edxposed in Edxposed manager !
Kris
Click to expand...
Click to collapse
Thank you! You were right, this was not caused by the Magisk upgrade, but by EdXposed. After upgrading to Canary version SafetyNet passes again.

I'd also like to add (in case someone stumbles across this thread looking for answers) that Magisk v20.4+ has MagiskHide disabled by default. On a fresh install you will have to enable it before Hide will be able to do it's thing.