Database Develop

[Guide] Pass Safetynet on a rooted 7.0 AOSP based ROM - Updated 11-01-2016

Update (11/09) - This method no longer works with the november security updates from Google as it causes suhide to break.
Here are the steps to follow
If you are already rooted, fully unroot. I do this by doing the following.
1) In the SuperUser app, go to settings and choose to do a full unroot. Choose "No" when it prompts you to restore your stock boot.img
2) Let the system reboot normally.
3) Reboot to recovery
4) If you have Magisk installed, flash the Magisk uninstaller Link
5) If you have suhide installed, flash rm-suhide 0.51 Link
6) Flash your ROM's boot.img extracted from your ROM (simply dirty flashing should also work), or install a custom kernel of your choice
At this point you should have a stock boot.img (or custom kernel) with no traces of SuperUser anywhere
Install SuperUser 2.78 Link
Install suhide 0.55 Link
Reboot into system. Verify that you have root. I'm not 100% sure this is necessary, but I like to do it before proceeding.
Reboot back into recovery.
Flash xsetpropSu.zip (attached to this post) Link
Reboot the system
Install RootSwitch 1.3.3.2 Link
Open up RootSwitch, uncheck disable all SU daemons. Disable Root
Pass SafetyNet
Optional
Using tasker to automatically disable root when certain applications are run. @NYZack made a little writeup here
Credits:
@NYZack - Helping me figure out how to put all of this together
@Captain_Throwback - For help with xsetprop
@Chainfire - SuperSU + SuHide
@topjohnwu - Magisk

work around found

no longer relevant post..

I don't know if the kernel can be modified to pull that trick. Even if someone does though, it's not going to last long. Every bypass you can find, Google can find. Then they know what to fix. The only way to win, is not to play.
And no, you can't lock the bootloader without wiping data.

Well I got it to work...I will turn this thread into a Guide. Who knows how long it will last, but...at least it's working for now.

Thread updated with instructions. I hope this can help someone!

So there's no way to do this without rooting and magisk?

3dawg said:
So there's no way to do this without rooting and magisk?
Click to expand...
Click to collapse
I want root, so I did not try to do that. If your bootloader is unlocked, I do not think there's a way to do it.

Thanks
skaforey said:
Thread updated with instructions. I hope this can help someone!
Click to expand...
Click to collapse
Yes I just followed these instructions and I am green panel. I have to check at a terminal to pay with phone but it probably will work. One note that was kinda unclear in case others do same....It should read :
Turn the Root switch ON....not OFF....when wanting to use AP. You can turn it back on when you want to do other things that require root permissions. I believe this is dynamic and working with the magisk mount point in addition to tricking the boot process into thinking the bootloader is locked.
Thanks so much for this. I was so angry with Google. And I was just going to say FK it and not use AP.
WORKS! Do all the steps in the order he says above and you can turn root off and on at will and have Android Pay work just fine! YAY!

skaforey said:
This thread started as a plea for help, but thanks to @NYZack I have gotten it to work.
Here are the steps to follow
If you are already rooted, fully unroot. I do this by doing the following.
1) If you have suhide installed, download rm-suhide 0.51 Link
2) In the SuperUser app, go to settings and choose to do a full unroot. Choose "No" when it prompts you to restore your stock boot.img
3) Let the system reboot normally.
4) Reboot to recovery
5) Flash rm-suhide 0.51
6) Flash your ROM's boot.img extracted from your ROM (simply dirty flashing should also work), or install a custom kernel of your choice
At this point you should have a stock boot.img (or custom kernel) with no traces of SuperUser anywhere
Install SuperUser 2.78 Link
Install Magisk v8.zip Link
Install suhide 0.55 Link
Reboot into system
Install Magisk Manger 2.1 (apk) Link
Open up Magisk Manager app and go to modules. Click on the + button. Add the following zip for xsetprop Link
Install RootSwitch 1.3.1.2 Link
Reboot system
Using Root Explorer (or some other file manager capable of root access), browse to /magisk/xsetprop and modify post-fs-data.sh . Add the following line to the end of the file, save and exit
Code:
xsetprop ro.boot.flash.locked 1
Reboot system
Open up RootSwitch, uncheck disable all SU daemons. Disable Root
Pass SafetyNet
Click to expand...
Click to collapse
FYI - The latest version of the xSetProp zip (0.2.1 as of this post) handles setting that prop automatically, and has additional logging. I'd recommend using that and you can remove that portion of your guide.

Captain_Throwback said:
FYI - The latest version of the xSetProp zip (0.2.1 as of this post) handles setting that prop automatically, and has additional logging. I'd recommend using that and you can remove that portion of your guide.
Click to expand...
Click to collapse
Thank you! Instructions updated (also tried to give proper credit all around).
I think Chainfire might be in the process of doing something similar without the need for Magisk.
I suppose we could also probably use the xsetprop binary along with a su.d script to run the necessary commands on startup? This would avoid having to use Magisk all together.
If I get some time I might try that out.

No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!

Pkt_Lnt said:
http://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
Click to expand...
Click to collapse
Thanks so much for taking the time to write this out.
I am 100% successful with M ROMs like ResRemix
However on my Nexus 6 with N ROMs (like Nitrogen or cDroid) I can't get SafetyNet to pass this way. With Root Switch I can get PoGo to work but following these instructions to a T I still don't have green SN
I wonder if it is the kernel ? What kernel have you been successful with?
Lastly are you aware of any way to find success with 7.1 ROMs?
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
photolarry said:
No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!
Click to expand...
Click to collapse
Is the message you are getting coming up with SafetyNet or with PoGo ... or when ??

jcrompton said:
Thanks so much for taking the time to write this out.
I am 100% successful with M ROMs like ResRemix
However on my Nexus 6 with N ROMs (like Nitrogen or cDroid) I can get SafetyNet to pass this way. With Root Switch I can get PoGo to work but following these instructions to a T I still don't have green SN
I wonder if it is the kernel ? What kernel have you been successful with?
Lastly are you aware of any way to find success with 7.1 ROMs?
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
Is the message you are getting coming up with SafetyNet or with PoGo ... or when ??
Click to expand...
Click to collapse
Yea I know I think it's something to do with either the kernel I've selected or perhaps suhide no longer works...I'm not sure what the deal is. I'm running Franco #55 and even without root, I get failure but inside the testing app ...see attached

Thanks for this write-up! I was able to pass SafetyNet in both apps while running Pure Nexus 7 w/ Stock OpenGapps.
I think one key thing that was skipped in the OP - be sure your ROM is SafetyNet compatible to begin with. I've run numerous ROMs that even before Google started checking bootloaders, wouldn't pass SafetyNet even if unrooted. For example, I just tried the OP method with Despair's new 7.1 ROM and it failed (probably won't work on 7.0 either). But with Pure Nexus 7.0 it works great.

MrBrady said:
Thanks for this write-up! I was able to pass SafetyNet in both apps while running Pure Nexus 7 w/ Stock OpenGapps.
I think one key thing that was skipped in the OP - be sure your ROM is SafetyNet compatible to begin with. I've run numerous ROMs that even before Google started checking bootloaders, wouldn't pass SafetyNet even if unrooted. For example, I just tried the OP method with Despair's new 7.1 ROM and it failed (probably won't work on 7.0 either). But with Pure Nexus 7.0 it works great.
Click to expand...
Click to collapse
I'm using stock Rom and only custom kernel so this should work on Nbd90z....I'd think. Last test was dreaded message but I'm trying to add few things to suhide blacklist. We shall see

I get the green screen. But then when I tap at store nfc terminal...it claims error....I'm going to try hiding nfc service, and what I think is play services based on uid chainfire explained. I'll try a small purchase and remember to screen capture the error if occurs

skaforey said:
Thank you! Instructions updated (also tried to give proper credit all around).
I think Chainfire might be in the process of doing something similar without the need for Magisk.
I suppose we could also probably use the xsetprop binary along with a su.d script to run the necessary commands on startup? This would avoid having to use Magisk all together.
If I get some time I might try that out.
Click to expand...
Click to collapse
I built the mod for people that were already using Magisk. If you're not using Magisk, then of course you can try just putting the binary in /su/xbin and put the post-fs-data.sh in /su/su.d and see if that works for setting the props at boot time.
I don't use Xposed, so using Magisk + phh's Superuser was my target for the module. I also did try the su.d method with SuperSU, but it wasn't working on my device. I also didn't want to have to use RootSwitch. But feel free to unpack the zip and try whatever combinations you want.

photolarry said:
No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!
Click to expand...
Click to collapse
Still working for me. Are you sure you disabled root in Root Switch? It automatically re-enables upon logon. Also be sure your xsetprop file is correct.
You can check by using the getprop command

skaforey said:
Still working for me. Are you sure you disabled root in Root Switch? It automatically re-enables upon logon. Also be sure your xsetprop file is correct.
You can check by using the getprop command
Click to expand...
Click to collapse
I'm using it for android pay not pogo. And I did. I'm sure the prop is right or wouldn't get green go. It's an error from AP saying something about unable to verify and might be rooted....or words to that effect

Cant play pokemon go with xposed installed

Hi!
I have been trying for few days to get pokemon work with xposed installed in marshmallow 6.0.1 but with no luck.
I have almost tried everything that I have found in this forum and google.
My phone is Xperia XZ F8331
I have no problem play pokemon on nougot with rooted and magisk installed on my device. Everything works fine but no xposed on nougat for now, I want xposed on my device.
So I downgrade to marshmallow 6.0.1
I root my device
I install magisk
I hide root using magisk hide from pokemon
I start pokemon without any problem.
I install xposed using magisk and restart
Starting pokemon and getting no gps signal error. Pokemon wont start.
Is there any way to get around it? I have been trying everythingto get it to work but with no luck.

SamBamBim said:
Hi!
I have been trying for few days to get pokemon work with xposed installed in marshmallow 6.0.1 but with no luck.
I have almost tried everything that I have found in this forum and google.
My phone is Xperia XZ F8331
I have no problem play pokemon on nougot with rooted and magisk installed on my device. Everything works fine but no xposed on nougat for now, I want xposed on my device.
So I downgrade to marshmallow 6.0.1
I root my device
I install magisk
I hide root using magisk hide from pokemon
I start pokemon without any problem.
I install xposed using magisk and restart
Starting pokemon and getting no gps signal error. Pokemon wont start.
Is there any way to get around it? I have been trying everythingto get it to work but with no luck.
Click to expand...
Click to collapse
Try Root Switch app, it can be found in the suhide thread here on XDA. It will hide root (SuperSU) and Xposed.
Magisk can't hide Xposed at the moment.

Portgas D. Ace said:
Try Root Switch app, it can be found in the suhide thread here on XDA. It will hide root (SuperSU) and Xposed.
Magisk can't hide Xposed at the moment.
Click to expand...
Click to collapse
Already have tested it, no change. does it work for you?

SamBamBim said:
Already have tested it, no change. does it work for you?
Click to expand...
Click to collapse
I am using suhide with SuperSU and Root Switch. Everything works fine.

SamBamBim said:
Already have tested it, no change. does it work for you?
Click to expand...
Click to collapse
What ROM are you using ? If you wan't Xposed to work with PoGo on MM builds, the better is to get rid of Magisk as it seems to complicate things more other.. also install latest systemless SuperSu, Suhide and Root Switch and 86.2 Xposed Systemless. For me works perfectly on post November security patch's ROM (CM13)
Envoyé de mon Unsupported MI Cancro en utilisant Tapatalk

Milous98 said:
What ROM are you using ? If you wan't Xposed to work with PoGo on MM builds, the better is to get rid of Magisk as it seems to complicate things more other.. also install latest systemless SuperSu, Suhide and Root Switch and 86.2 Xposed Systemless. For me works perfectly on post November security patch's ROM (CM13)
Envoyé de mon Unsupported MI Cancro en utilisant Tapatalk
Click to expand...
Click to collapse
Im getting
Code:
do not support systemless xposed on rootswitch.
My rom is 39.0.A.3.30_R6B
My rootswitch v. is 1.3.3.2
Installed supersu "SR2-SuperSU-v2.79-SR2-20170103215521.zip"
Installed suhide-v0.54.zip
Installed "xposed-v86.2-sdk23-topjohnwu.zip"

SamBamBim said:
Im getting
Code:
do not support systemless xposed on rootswitch.
My rom is 39.0.A.3.30_R6B
My rootswitch v. is 1.3.3.2
Installed supersu "SR2-SuperSU-v2.79-SR2-20170103215521.zip"
Installed suhide-v0.54.zip
Installed "xposed-v86.2-sdk23-topjohnwu.zip"
Click to expand...
Click to collapse
Update suhide to the latest version (v0.55). The message "do not support systemless Xposed" can be ignored, it works fine. Make sure you have deleted "su" file from /system/bin and /system/xbin. Also, make sure SuperSU is installed in systemless mode (you can check by opening SuperSU app and scroll down to "Install SuperSU in system mode". If it says "can't be done in systemless mode", then everything is okay).
Also check if your ROM has the security patch level from before November 2016 (Settings -> About device), otherwise it will break Xposed.

It's nor working for my Xperia XZ or Xperia Z3 or Z1.
The only method that works to play Pokémon go with root for me is in Android 7 and only with Magisk.
Ill wait for a working xposed for Pokémon go for nougat, hope it happen soon. Thanks for trying helping me . I would have been glad to see if it really works for guys, I don't think the above method works, not for me anyway.

Safety net check has all the info regarding our device and it's officially oem rom.It checks it using internet by looking your device fingerprints.i had same problem with one of my device where i was not even able to run Pokemon go with stock no tampering at all as that update was officially given to me as beta by oem.It worked only when i left beta n went to official one.it has to do something with CTS profile as i was getting a mismatch before.

No root , no soft ban, 5.0-7.xx: https://forum.xda-developers.com/ap...-mock-root-t3623235/post72708198#post72708198

Pokemon Go detects Xposed installer?
I have a Verizon Samsung Galaxy S5 running the stock ROM, Android 6.0.1. I ran the Xposed installer. The installer warned me not to install it because it's not compatible, so I backed out. I haven't been able to play Pokemon Go since this. I was getting 504 errors in Google Play store. I was able to fix that. Pokemon Go installs from the Google Play store now. If I clear the data for Pokemon Go, I can maybe catch one Pokemon before the screen pops up that says I have an incompatible device or OS if I'm lucky.
The Xposed installer must have left some trace of itself on my phone.
Is a factory reset the only way to fix this? Will that even work?

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

[SOLVED] Can I really switch from SuperSU ?

Hi there fellows ! ^^
First of all, I want you all to know that I really am sorry if this is something that has been asked before. I tried, but couldn't find an answer by myself and I don't want to damage my phone again (I may have been waaaaay too hasty in the past...). So here goes.
I have a Honor 5C NEM-L51 (European variant) which I rooted a while ago (two or three months ago maybe ? Can't remember for sure) by unlocking the bootloader, installing TWRP from ADB, flashing the SuperSU zip file... You know, the usual thing. After that I went ahead and installed Xposed Framework, Busybox and several applications and modules which needed root like many of you I guess. Everything went fine. And still is, for the record.
Now I realize that I may have been living under a rock because I discovered very recently that not only SuperSU can be downloaded from the Play Store but also that there is Magisk, an open-source alternative with more functionnalities. Guess what ? I want it.
Soooo I did some research and read this https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 along with other articles here and there on the web and it seems that I'd just have to install some Magisk Manager app' from the Play Store... Is that really all there is to do ?!
I'm worried because it says "If you're already rooted with MagiskSU or Latest Official Systemless SuperSU". Yep, the "Systemless" part get me worried. While I do understand what it means, I can't help but wonder : since I installed SuperSU from a flashable zip file, is it Systemless ? How can I tell ?
Plus the whole thing is kinda confusing to me. If I do that, will Magisk remove SuperSU ? But if so, won't there be a problem with Xposed and other apps that need root ? Same question applies if I first manually remove SuperSU (assuming I can actually do that) before installing anything else.
In short, how should I proceed ? Do I have to remove anything ? Can I do anything ?
Again, sorry if things had been told already. I really want to take my shot, but I don't wanna soft brick my device again by being too carefree one more time.
Thank you for your time and your help.

When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk

ken2802 said:
When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Click to expand...
Click to collapse
Thank you for your answer. Can I uninstall SuperSU to install Magisk su instead then ? Do I need to remove Xposed module and my root apps too ?
ken2802 said:
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
Yeah, I do know that, but I really do need my phone at the moment, so I'd kinda be in a world of pain if I brick it.

You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them

ken2802 said:
You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them
Click to expand...
Click to collapse
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?

Zarou said:
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?
Click to expand...
Click to collapse
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.

Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?

Zarou said:
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?
Click to expand...
Click to collapse
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu

ken2802 said:
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu
Click to expand...
Click to collapse
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?

Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
You can try but if magisk complain while instalation you need to flash a fresh boot image/Rom
Gesendet von meinem SM-G925F mit Tapatalk

Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.

Didgeridoohan said:
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.
Click to expand...
Click to collapse
Thank you, I managed to get by the whole thing with no issue. Problem solved !

Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.

tutabeier said:
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.
Click to expand...
Click to collapse
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.

Didgeridoohan said:
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.
Click to expand...
Click to collapse
Thanks. I probably missed something when reading the threads. I understood Magisk can root my devices, but didn't understood that simply installing it would root my device. So that's why I was flashing su binary and using SuperSU app.
Thanks a lot.

First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha

xdaVTU said:
First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha
Click to expand...
Click to collapse
It's not quite apparent from your post if you have rooted with SuperSU already and now want to use Magisk instead. But, considering that you're posting in a thread that deals with moving from SuperSU I'm gonna go with that... Kind of...
You will need an unlocked bootloader, yes.
If you've rooted with SuperSU you can reflash your ROM, or use something like @osm0sis unSU zip and then flash the stock boot image only. Depends on your setup which option is easier. If you're not already rooted, this step is unnecessary.
Installing Magisk is just as easy as that, yes.
The Manager is also installed when flashing the Magisk zip, so this step is unnecessary. However... In rare cases the Manager doesn't install with the zip. If that happens you just have to install it manually.
The only step I'd like to add is to have a backup of all important data and files on your device. That's always good practice when tinkering with your device...
The release thread and the installation/troubleshooting thread (I'm hoping to have time to update it for Magisk v15.2 tonight) are good resources when setting everything up and if you encounter issues. Searching through the general support thread is also a good idea if issues arise. Most questions have been answered numerous times already.

I'm new to Magisk but have a couple of questions. I have a pixel XL running Dirty UNICORNS rooted with SuperSU. If I want to use Magisk can I just flash my dirty UNICORNS rom, gapps and then the magisk.zip?
Sent from my Pixel XL using Tapatalk

Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir

jc1266 said:
Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir
Click to expand...
Click to collapse
No. You merely need to uninstall SuperSU, either through the SuperSU app (complete uninstall) or by using the unSU zip. You'll also have to make sure that you restore the stock unpatched boot image.
After that you can flash Magisk and you'll be good to go.

Uninstall exposed

Yesterday i migrated from cm 13 to cm14.1 (galaxy a500fu) and i tried to login to Snapschat before rooting the phone as i usually did on cm13, but is not working. I rooted it then full unruted from super su, tried root switcher also, none of those worked. So i gues the cm14.1 came with xposed preinstalled(is that possible?). I searched for the unistaller for 7.1 version but i only found for 6.1 and lower. Will it work if i install one of those lower zips?

Xposed is not out yet for Nougat, you can hide root via Magisk.

waseemmayaa said:
Xposed is not out yet for Nougat, you can hide root via Magisk.
Click to expand...
Click to collapse
tried Magisk too, when i open the app is telling me to install it from Play Store, a go there and "Item not found"

qp_blaze said:
tried Magisk too, when i open the app is telling me to install it from Play Store, a go there and "Item not found"
Click to expand...
Click to collapse
Install magisk manually from apkmirror or from any other website then install magisk zip by magisk app.

waseemmayaa said:
Install magisk manually from apkmirror or from any other website then install magisk zip by magisk app.
Click to expand...
Click to collapse
Managed to install it manually, but it won't pass safetynet check. I think is becouse of the custom rom. Searched a little bit more and found out that a kernel flash would fix this. You know nay kernel for my divice which cand pass safetynet?

qp_blaze said:
Managed to install it manually, but it won't pass safetynet check. I think is becouse of the custom rom. Searched a little bit more and found out that a kernel flash would fix this. You know nay kernel for my divice which cand pass safetynet?
Click to expand...
Click to collapse
Mate, if you want to pass the "saftynet" then enable the "Hide root" in the app setting in Magisk Manager then try it again.
Also after you have done that go to the Magisk Hide tab and select any app you want it to work with root enabled. This will allow you to have root and be able to use apps that does not work with root.
Sent from my Nexus 6P using XDA Labs