Related
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.
I want to root my device.
But I'm unable to decide that I should root via supersu or Magisk.
I've read that magisk provide systemless root, but what the advanteges of systemless root/magisk?
Can someone help me that what's the use/advantage of Magisk?
is it much stable then supersu?
I don't want to risk my device as I'm app developer
akash.galaxy07 said:
I want to root my device.
But I'm unable to decide that I should root via supersu or Magisk.
I've read that magisk provide systemless root, but what the advanteges of systemless root/magisk?
Can someone help me that what's the use/advantage of Magisk?
is it much stable then supersu?
I don't want to risk my device as I'm app developer
Click to expand...
Click to collapse
If you are an app developer, use Magisk. Magisk allows you to pass google's safety tests (Safetynet) - which you should know about if you develop apps! but basically, google will not think your device is compromised is you use Magisk, but WILL think your device is compromised if you use SuperSU - even if SuperSU is installed in Systemless mode. Don't forget to enable magisk hide in the Magisk Manager app to make sure this works though.
Some app developers will check safetynet upon launching their app to see if the device is compromised, and if it is, either restrict features, or deny access entirely. A good example of this is Banking apps, though they usually use their own root detection - but that can be hidden with Magisk Hide. - No bank wants their app being used on a compromised device, where a virus with root access could collect information. The more you know
manor7777 said:
If you are an app developer, use Magisk. Magisk allows you to pass google's safety tests (Safetynet) - which you should know about if you develop apps! but basically, google will not think your device is compromised is you use Magisk, but WILL think your device is compromised if you use SuperSU - even if SuperSU is installed in Systemless mode. Don't forget to enable magisk hide in the Magisk Manager app to make sure this works though.
Some app developers will check safetynet upon launching their app to see if the device is compromised, and if it is, either restrict features, or deny access entirely. A good example of this is Banking apps, though they usually use their own root detection - but that can be hidden with Magisk Hide. - No bank wants their app being used on a compromised device, where a virus with root access could collect information. The more you know
Click to expand...
Click to collapse
Thanks bro, and, is it stable too? I mean, are there any risks involved?
akash.galaxy07 said:
Thanks bro, and, is it stable too? I mean, are there any risks involved?
Click to expand...
Click to collapse
There are risks with any kind of root on your phone, as an app developer, you should know that.
You could get a virus that takes advantage of root to encrypt all of your files.
Again, you should know this if you are an app developer, there is a difference between creating a single app, and developing applications as a whole!
Magisk is very stable though, more so on OxygenOS but it will be pretty stable with LineageOS too! I have had no problems whatsoever! I have been using android pay and all my root apps without my phone ever crashing! And if you are careful, you won't get a virus (root will not cause a virus, user stupidity gets virus') - enjoy
I'd like to add the main advantage to why I use Magisk.
All my system modifications (build.prop changes, debloating, changed/removed ui audio, etc) are still there after a system update. Even if I have to do a clean install with a wipe, all it takes is flashing a couple of extra zips and everything is right back were I want it.
Didgeridoohan said:
I'd like to add the main advantage to why I use Magisk.
All my system modifications (build.prop changes, debloating, changed/removed ui audio, etc) are still there after a system update. Even if I have to do a clean install with a wipe, all it takes is flashing a couple of extra zips and everything is right back were I want it.
Click to expand...
Click to collapse
Can you please link me to Magisk installation thread for Oneplus 3t. I can't find any on XDA. I found one thread that belongs to Magisk dev but it is very confusing with installing all the systemless SuperSU and such.
vipivj said:
Can you please link me to Magisk installation thread for Oneplus 3t. I can't find any on XDA. I found one thread that belongs to Magisk dev but it is very confusing with installing all the systemless SuperSU and such.
Click to expand...
Click to collapse
There's no specific 3T thread that I know of... It's all there in the Magisk forums. It's not as complicated as it might seem.
If you're unrooted, just flash the Magisk zip in TWRP. Done!
If you have systemless SuperSU installed and want to keep it, just flash the Magisk zip in TWRP. Done!
If you have systemless SuperSU installed and want to switch to MagiskSU, you'll need to first remove SuperSU. Use the full unroot option in the SuperSU app and say yes when asked if you want to restore the boot image backup. After that, flash the Magisk zip in TWRP. Done!
If you have any other root installed, just flash the Magisk zip in TWRP and the installation script will do it's best to remove it and install MagiskSU instead. Done!
Edit: There might be variations on the above, depending on if you're using stock ROM or not. Take a look at the link in my signature if you run into problems. I've tried to collect as much info, tips and tricks as possible in one place.
Didgeridoohan said:
There's no specific 3T thread that I know of... It's all there in the Magisk forums. It's not as complicated as it might seem.
If you're unrooted, just flash the Magisk zip in TWRP. Done!
If you have systemless SuperSU installed and want to keep it, just flash the Magisk zip in TWRP. Done!
If you have systemless SuperSU installed and want to switch to MagiskSU, you'll need to first remove SuperSU. Use the full unroot option in the SuperSU app and say yes when asked if you want to restore the boot image backup. After that, flash the Magisk zip in TWRP. Done!
If you have any other root installed, just flash the Magisk zip in TWRP and the installation script will do it's best to remove it and install MagiskSU instead. Done!
Edit: There might be variations on the above, depending on if you're using stock ROM or not. Take a look at the link in my signature if you run into problems. I've tried to collect as much info, tips and tricks as possible in one place.
Click to expand...
Click to collapse
Thanks, it is clear now. Is it possible to 100% pass safety net with Magisk? I read somewhere that it's a hit and miss.
Apart from the Magisk modules what's the benefit of rooting with Magisk instead of superSU? I saw many people still support superSU than Magisk, does it mean that Magisk has some flows or bugs?
vipivj said:
Thanks, it is clear now. Is it possible to 100% pass safety net with Magisk? I read somewhere that it's a hit and miss.
Apart from the Magisk modules what's the benefit of rooting with Magisk instead of superSU? I saw many people still support superSU than Magisk, does it mean that Magisk has some flows or bugs?
Click to expand...
Click to collapse
I've had no issues passing SafetyNet on my OP3T. It depends on what ROM you're using and if you have any other modifications that Magisk Hide can't hide. Apart from Magisk Hide and systemless modifications Magisk is also open source, if you value that kind of stuff...
There might be apps out there that use specific SuperSU stuff and won't work fully with MagiskSU. I haven't had any issues though (apart from a couple of workarounds, like for Tasker - again, see my signature) and many app developers are starting to make their apps work with MagiskSU as well. Most work out of the box though.
MagiskHide
You can use apps like Android Pay or Snapchat on a rooted device
Didgeridoohan said:
I've had no issues passing SafetyNet on my OP3T. It depends on what ROM you're using and if you have any other modifications that Magisk Hide can't hide. Apart from Magisk Hide and systemless modifications Magisk is also open source, if you value that kind of stuff...
There might be apps out there that use specific SuperSU stuff and won't work fully with MagiskSU. I haven't had any issues though (apart from a couple of workarounds, like for Tasker - again, see my signature) and many app developers are starting to make their apps work with MagiskSU as well. Most work out of the box though.
Click to expand...
Click to collapse
Another noob question, what is the difference between normal and systeless SuperSU?
Considering current known problems Magisk have , isn't it a good idea to use Magisk superSU combo and SuperSU hide?
vipivj said:
Another noob question, what is the difference between normal and systeless SuperSU?
Considering current known problems Magisk have , isn't it a good idea to use Magisk superSU combo and SuperSU hide?
Click to expand...
Click to collapse
Systemless root doesn't alter /system... If you want a more in-depth explanation I'm sure your friend Google can explain it to you.
For OP3T on OxygenOS (I'm currently on 4.1.3) I've not experienced any issues with Magisk. I don't know what those "currently known problems" are that you're worried about...
Didgeridoohan said:
Systemless root doesn't alter /system... If you want a more in-depth explanation I'm sure your friend Google can explain it to you.
For OP3T on OxygenOS (I'm currently on 4.1.3) I've not experienced any issues with Magisk. I don't know what those "currently known problems" are that you're worried about...
Click to expand...
Click to collapse
I meant those issues happens with Tasker etc. Thank you for the answers, you've been very helpful.
I started googling and reading in XDA as well but you know the doubts that comes along ?
vipivj said:
I meant those issues happens with Tasker etc. Thank you for the answers, you've been very helpful.
I started googling and reading in XDA as well but you know the doubts that comes along
Click to expand...
Click to collapse
Ah... Ok. Those kind of issues are easy to work around and the next version of Tasker will have official MagiskSU support.
Use Magisk Manager
I also used Magisk Manager in my old device at it worked fine and as magisk allow you to root Android without effecting on system files I could also install root unsupported apps as well. So i think Magisk is the best solution for you.
link deleted by Moderator due to untrustworthy site will be a help full site to gather more info about magisk from one place.
Topjohnwu has strictly stated that any website which spreads Magisk is not official and cannot be trusted. The only official place is the XDA Thread. If you see any Member promoting an external site related to Magisk, please report the post.
This module hides bootloader unlock from the entire system, including GMS, meaning that stock ROMs can pass custom verification, as well as custom ROMs with magisk enabled. Module code is here. The actual code of this module (see post-fs-data.sh) can be used to pass safetynet on stock ROMs, even without magisk, provided your /system is unmodified! :angel::highfive:
The module is tested on my Honor 9 Lite, unlocked, lineageos 15.1, MM 5.6.3, Magisk 16.0
Download: Magisk Downloads page
WARNING: phhusson ROMs, as well as official Google gsi's without a fingerprint patch cannot pass safetynet without V2 or higher, or magiskhide props config
Debugging:
Please open a root shell and run
Code:
safetypatch
and select option 1 to debug.
If, in /proc/cmdline, androidboot.verifiedbootstate is green, this module is functioning correctly and some other aspect of your system is detected by safetynet.
Note: Pie ROMs might need ianmacd magisk builds to pass any kind of safetynet. In my experience you need this module and ianmacd magisk.
hackintosh5 said:
This module hides bootloader unlock from the entire system, including GMS, meaning that stock ROMs can pass custom verification, as well as custom ROMs with magisk enabled. Module code is here. The actual code of this module (see post-fs-data.sh) can be used to pass safetynet on stock ROMs, even without magisk, provided your /system is unmodified! :angel::highfive:
The module is tested on my Honor 9 Lite, unlocked, lineageos 15.1, MM 5.6.3, Magisk 16.0
Download: https://github.com/penn5/SafetyPatch/releases/tag/v1
Click to expand...
Click to collapse
Hello, thanks for your work, but i don't understand how this module, by this shell:
Code:
mount -o bind /data/local/tmp/cmdline /proc/cmdline
sed 's/ORANGE/GREEN/' /proc/cmdline > /data/local/tmp/cmdline
is supposed to fix the SN ?
Also i don't think that it could help to fix the SN if Xposed is installed ? Tell me if i'm wrong..
Rom said:
Hello, thanks for your work, but i don't understand how this module, by this shell:
is supposed to fix the SN ?
Also i don't think that it could help to fix the SN if Xposed is installed ? Tell me if i'm wrong..
Click to expand...
Click to collapse
This is not for SN, but to fix safetynet fail. Use HCU to fix SN.
Sent from my kminiltexx using XDA Labs
Doesn't Magisk itself already hides the unlocked BL state?
Sent from my Xiaomi Redmi Note 5 using XDA Labs
VincentJoshuaET said:
Doesn't Magisk itself already hides the unlocked BL state?
Click to expand...
Click to collapse
No. Magisk hides itself
Sent from my kminiltexx using XDA Labs
hackintosh5 said:
No. Magisk hides itself
Sent from my kminiltexx using XDA Labs
Click to expand...
Click to collapse
Wrong...
MagiskHide does hide a few system properties, among others an unlocked bootloader.
https://github.com/topjohnwu/Magisk...2cebb240c4/native/jni/magiskhide/hide_utils.c
If you have an additional method for hiding an unlock bootloader, that would make a great addition to MagiskHide. You could open a pull request for it to be included in a future release.
Didgeridoohan said:
Wrong...
MagiskHide does hide a few system properties, among others an unlocked bootloader.
https://github.com/topjohnwu/Magisk...2cebb240c4/native/jni/magiskhide/hide_utils.c
If you have an additional method for hiding an unlock bootloader, that would make a great addition to MagiskHide. You could open a pull request for it to be included in a future release.
Click to expand...
Click to collapse
Correct...
MagiskHide doesn't hide anything in the cmdline. If you're going to disclaim my module, at least do your research. Even in the README, I tell the commands that the module uses.
Yes, that's a good idea. I will submit a PR, thanks for the idea!
Sent from my kminiltexx using XDA Labs
hackintosh5 said:
If you're going to disclaim my module, at least do your research.
Click to expand...
Click to collapse
Calm down... There was no disclaiming of your module in my post. Just your statement that Magisk does not hide an unlocked bootloader. It does...
But of course, there are many different Android devices and there are many different ways of doing things, and they don't work the same universally. Which is why I suggested you make a PR of the method you have. :good:
I'm using a pixel xl on dp3 and this doesn't help to pass basic integrity. Both basic and cts are still failing
bkkzak said:
I'm using a pixel xl on dp3 and this doesn't help to pass basic integrity. Both basic and cts are still failing
Click to expand...
Click to collapse
Official ROMs not designed for production use will intentionally force the system to fail safetynet. This will be detected and so fail
Sent from my kminiltexx using XDA Labs
hackintosh5 said:
This module hides bootloader unlock from the entire system, including GMS, meaning that stock ROMs can pass custom verification, as well as custom ROMs with magisk enabled. Module code is here. The actual code of this module (see post-fs-data.sh) can be used to pass safetynet on stock ROMs, even without magisk, provided your /system is unmodified! :angel::highfive:
The module is tested on my Honor 9 Lite, unlocked, lineageos 15.1, MM 5.6.3, Magisk 16.0
Download: https://github.com/penn5/SafetyPatch/releases/tag/v1
WARNING: phhusson ROMs cannot pass safetynet.
Click to expand...
Click to collapse
Excuse me, how do I install the module?
Twixy13 said:
Excuse me, how do I install the module?
Click to expand...
Click to collapse
Magisk Manager -> Modules -> + -> Find the zip.
Sent from my kminiltexx using XDA Labs
Do i need a custom kernel for this to work?
It's not working on my stock honor 8. I even tried it with magiskhide props config with a honor 9 and galaxy 6 fingerprint and play store is still uncertified which means safetynet fails
JimZiii said:
play store is still uncertified which means safetynet fails
Click to expand...
Click to collapse
The two are related, yes, but one doesn't exclude the other (you can pass SafetyNet and still be uncertified).
Check SafetyNet with the Magisk Manager or a separate app. If it passes, clear data for the Play Store and reboot. That should be it...
Didgeridoohan said:
The two are related, yes, but one doesn't exclude the other (you can pass SafetyNet and still be uncertified).
Check SafetyNet with the Magisk Manager or a separate app. If it passes, clear data for the Play Store and reboot. That should be it...
Click to expand...
Click to collapse
Ok, for some reason I still can't pass. I've checked it with magisk and a separate app. Even after I factory reset my phone, flashed new firmware and the first thing I installed was magisk to try the safetynet and still I couldn't pass. First I thought it might be something in the new firmware so I tried a bunch of older firmwares which all had the same result.
JimZiii said:
Ok, for some reason I still can't pass. I've checked it with magisk and a separate app. Even after I factory reset my phone, flashed new firmware and the first thing I installed was magisk to try the safetynet and still I couldn't pass. First I thought it might be something in the new firmware so I tried a bunch of older firmwares which all had the same result.
Click to expand...
Click to collapse
This is getting slightly OT for this thread (but that's up to @hackintosh5, of course). Take a look here (start with the Basics and then move on to the SafetyNet chapter) and if you still need help after that, I think you'd better move it to the General support thread:
https://www.didgeridoohan.com/magisk/MagiskHide
And don't forget this part:
https://www.didgeridoohan.com/magisk/MagiskHideHelp
Didgeridoohan said:
This is getting slightly OT for this thread (but that's up to @hackintosh5, of course). Take a look here (start with the Basics and then move on to the SafetyNet chapter) and if you still need help after that, I think you'd better move it to the General support thread:
https://www.didgeridoohan.com/magisk/MagiskHide
And don't forget this part:
https://www.didgeridoohan.com/magisk/MagiskHideHelp
Click to expand...
Click to collapse
Ok, I think I found the problem, magiskhide don't seem to be working. I get logs so logging must be on and namespace is working because there's no error on proc_monitor or anywhere else in the magisk logs. But if I hide a root checker our another app using root they still get root.
Do you have any ideas?
JimZiii said:
Ok, I think I found the problem, magiskhide don't seem to be working. I get logs so logging must be on and namespace is working because there's no error on proc_monitor or anywhere else in the magisk logs. But if I hide a root checker our another app using root they still get root.
Do you have any ideas?
Click to expand...
Click to collapse
Is magisk hide actually turned on?
Sent from my kminiltexx using XDA Labs
hackintosh5 said:
Is magisk hide actually turned on?
Sent from my kminiltexx using XDA Labs
Click to expand...
Click to collapse
yes its on, i've added specific apps to try if they still got root and there's no difference when i check the box in magisk hide for apps
JimZiii said:
yes its on, i've added specific apps to try if they still got root and there's no difference when i check the box in magisk hide for apps
Click to expand...
Click to collapse
Apps can still detect root, even if you pass safetynet. Run the magisk inbuilt checker
Sent from my kminiltexx using XDA Labs
Hi,
It's a long time that I don't use root on my Oneplus 3T.
What I want to know is that if with the latest Oxygen Os, unlocked bootloader and latest magisk root / magisk hide I will be able to use Google Pay.
I know that Google can update SafetyNet detection algorithm, so usually if that happens after how long Magisk is updated to hide root again?
Thanks!
I had a message last time that tells me that if I have my bootloader unlocked, no matter if I have Magisk or not, Google Pay won't let me pay with NFC
tetra96 said:
I had a message last time that tells me that if I have my bootloader unlocked, no matter if I have Magisk or not, Google Pay won't let me pay with NFC
Click to expand...
Click to collapse
Without hiding the status of the bootloader, for sure Google Pay won't work. But Magisk Hide, can hide root status and bootloader status.
That's what I want to know, if Magisk Hide working or not
Waiting more responses from other users
andQlimax said:
Without hiding the status of the bootloader, for sure Google Pay won't work. But Magisk Hide, can hide root status and bootloader status.
That's what I want to know, if Magisk Hide working or not
Waiting more responses from other users
Click to expand...
Click to collapse
Google Pay works fine with Magisk. You don't need to hide it or hide Magisk Manager.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Google Pay works fine with Magisk. You don't need to hide it or hide Magisk Manager.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Can you explain how you were able to make it work? Because whether I hide Google Pay in Magisk or not, when I try to setup my credit card in Google Pay it says "Couldn't finish setup to pay in shops. This phone can't be used to pay in shops. This may be because it is rooted or altered in some other way."
I have a OnePlus 3 Oxygen 5.0.6 and Android 8.0.0 with Magisk 17.1.
axelryder said:
Can you explain how you were able to make it work? Because whether I hide Google Pay in Magisk or not, when I try to setup my credit card in Google Pay it says "Couldn't finish setup to pay in shops. This phone can't be used to pay in shops. This may be because it is rooted or altered in some other way."
I have a OnePlus 3 Oxygen 5.0.6 and Android 8.0.0 with Magisk 17.1.
Click to expand...
Click to collapse
That's odd. I didn't have to do anything to get it working. I'm on OOS 5.0.5 and Magisk 17.1.
Two question: is your phone encrypted and do you have a pin/password set?
My phone is encrypted and I use a password.
You could also try hiding Magisk Manager (I haven't needed to do this) and delete any Magisk folder on you internal storage.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
That's odd. I didn't have to do anything to get it working. I'm on OOS 5.0.5 and Magisk 17.1.
Two question: is your phone encrypted and do you have a pin/password set?
My phone is encrypted and I use a password.
You could also try hiding Magisk Manager (I haven't needed to do this) and delete any Magisk folder on you internal storage.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
I have a pin set, I don't think my phone is encrypted; although when I go to the Security menu, under "Encryption" it does say "Encrypted", but I don't remember setting it up. So I guess it is!
I did try to hide Magisk Manager from their option in the settings menu, but I still got the same error in Google Pay after;
As a side note, in Magisk SafetyNet Check does "Success", but ctsProfile is false, and basicIntegrity is false too; does that matter?
axelryder said:
As a side note, in Magisk SafetyNet Check does "Success", but ctsProfile is false, and basicIntegrity is false too; does that matter?
Click to expand...
Click to collapse
Yes; SafetyNet check means that app contacted with Google server with success, but the result of your device check is false, which means that your device is not certified "secure" in its current state.
Perhaps you tampered system partition?
tetra96 said:
I had a message last time that tells me that if I have my bootloader unlocked, no matter if I have Magisk or not, Google Pay won't let me pay with NFC
Click to expand...
Click to collapse
Did you try with a custom kernel? Your kernel needs SultanXDA's patch to pass safetynet with a unlocked bootloader. There is a magisk module here, that might work if you don't want a custom kernel. There's also some commands you can run on your devices terminal here, that might work too. I only have experience with using a custom kernel but the changelog for the module does say it was patched for OP3 support.
axelryder said:
...
As a side note, in Magisk SafetyNet Check does "Success", but ctsProfile is false, and basicIntegrity is false too; does that matter?
Click to expand...
Click to collapse
You've definitely installed something that breaks SafetyNet. Xposed used to do this, though I think it's been fixed to work with Magisk.
namanjr said:
Did you try with a custom kernel? Your kernel needs SultanXDA's patch to pass safetynet with a unlocked bootloader. There is a magisk module here, that might work if you don't want a custom kernel. There's also some commands you can run on your devices terminal here, that might work too. I only have experience with using a custom kernel but the changelog for the module does say it was patched for OP3 support.
Click to expand...
Click to collapse
Both Magisk and custom kernels patch the boot image so that it doesn't trigger dm-verity and pass SafetyNet. You don't need to use a custom kernel if you're using Magisk.
Sent from my OnePlus3T using XDA Labs
My Safetynet check is successful. Yet it doesnt work with Google Pay. I am told that PAY is not supported on my device as it is rooted.
przemcio510 said:
Yes; SafetyNet check means that app contacted with Google server with success, but the result of your device check is false, which means that your device is not certified "secure" in its current state.
Perhaps you tampered system partition?
Click to expand...
Click to collapse
BillGoss said:
You've definitely installed something that breaks SafetyNet. Xposed used to do this, though I think it's been fixed to work with Magisk.
Both Magisk and custom kernels patch the boot image so that it doesn't trigger dm-verity and pass SafetyNet. You don't need to use a custom kernel if you're using Magisk.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
I do indeed have Xposed installed, V90 beta 3. I guess maybe it's not fixed for Magisk after all :/
@przemcio510 do you use Xposed ?
axelryder said:
I do indeed have Xposed installed, V90 beta 3. I guess maybe it's not fixed for Magisk after all :/
@przemcio510 do you use Xposed ?
Click to expand...
Click to collapse
Yes, I do, Xposed breaks SafetyNet and there's nothing you can do to keep it installed and have SN passing
przemcio510 said:
Yes, I do, Xposed breaks SafetyNet and there's nothing you can do to keep it installed and have SN passing
Click to expand...
Click to collapse
Oh I see... well here's my problem I guess lol
On my Redmi note 4 From recent update of miui 10 and magisk 17.1 update google pay stopped working even though safety net check is passed. Earlier google pay was working fine.
Is there any work around?
Sahil Shaikh said:
On my Redmi note 4 From recent update of miui 10 and magisk 17.1 update google pay stopped working even though safety net check is passed. Earlier google pay was working fine.
Is there any work around?
Click to expand...
Click to collapse
This is a OnePlus 3T forum. Ask the question in the Redmi forum.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
This is a OnePlus 3T forum. Ask the question in the Redmi forum.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Okay, don't consider redmi note 4. Still do you got any way out for one plus 3?
Sahil Shaikh said:
Okay, don't consider redmi note 4. Still do you got any way out for one plus 3?
Click to expand...
Click to collapse
I think that your problem is specific to MiUI, because on our phones it works fine
Sahil Shaikh said:
Okay, don't consider redmi note 4. Still do you got any way out for one plus 3?
Click to expand...
Click to collapse
As per the previous post, Google Pay works just fine with Magisk installed. There's no need to hide it.
Sent from my OnePlus3T using XDA Labs
andQlimax said:
Hi,
It's a long time that I don't use root on my Oneplus 3T.
What I want to know is that if with the latest Oxygen Os, unlocked bootloader and latest magisk root / magisk hide I will be able to use Google Pay.
I know that Google can update SafetyNet detection algorithm, so usually if that happens after how long Magisk is updated to hide root again?
Thanks!
Click to expand...
Click to collapse
It is reliant on safetynet AFAIK, and that passes on my device when using Magisk - havent tried Android Pay as of yet, but am aware that Safetynet passes.
Hey guys, I'm rooted + magisk using the Dr. Ketan tool (Option 1) + Xposed + Beast Kernel. All good so far in regards to rooting, kernel and xposed.. Just the SafetyNet Check fails on Magisk. Tried changing the flash order to flash the Dr Ketan tool in the last, in case that would make it pass but no luck. So I've got a couple questions -
1. How to make SafetyNet pass
2. Can I update magisk version from magisk app? Or will I need to stick with the version that came along with the tool which is 17.2
Thnks!
You won't pass safetynet if you're using xposed (I don't think there's any way around it but uninstalling xposed)
n1Bb135 said:
You won't pass safetynet if you're using xposed (I don't think there's any way around it but uninstalling xposed)
Click to expand...
Click to collapse
Yep although my banking apps do pass well after hiding them via magisk, so that's good enough even if safetynet shows failed.
Any idea about if I can update magisk version other than coupled on the root tool?
Thanks!
rezapatel said:
Yep although my banking apps do pass well after hiding them via magisk, so that's good enough even if safetynet shows failed.
Any idea about if I can update magisk version other than coupled on the root tool?
Thanks!
Click to expand...
Click to collapse
In magisk manager there's an update prompt/button if there's an update
n1Bb135 said:
In magisk manager there's an update prompt/button if there's an update
Click to expand...
Click to collapse
Aware of that, but I meant to ask if it'd be okay to update the magisk version without a bootloop or any other issues.