Related
I'm currently running stock rom with Blu_spark kernel. I've been using magisk, lately updated to 14.3 version.
My problem is I can not pass SafetyNet check. Both ctsProfile and basicIntegrity are false.
I tried Universal SaftyNet Fix but it didn't help at all.
Is there any hope to pass it on stock rom?
Do you have Xposed installed?
Thanks, I completely forgot about it
The other safety net problem people are currently having with Magisk is that if you update Magisk within Magisk Manager some scripts needed to pass safety net are no longer installed by default. If you flash Magisk instead through TWRP it seems to install like normal and you don't need to perform additional steps to pass safety net.
I've been trying very hard to pass safety net on my axon 7, I first tried when I had LineageOS, Magisk and Xposed (not systemlessly installed) and a few other tweaks that appeared to modify the system partition, then after realising they may be affecting safety net I completely wiped my device (data,cache,system) to make sure I had a completely fresh start. Then proceeded to flash the MicroG version of LineageOS, and install Magisk and Xposed Systemlessly making sure nothing I did affected the system partition. So I thought I would be set, did safety net check andddd it failed. Then I did some searching and found safety net will check for bootloader unlocked status, so I found a kernel (HELLSGATE.V1) which tricks safety net (or is supposed to) into believing bootloader is still locked. And safety net still fails, this is really annoying I'm just wanting to use Android Pay yet I can't. Does anyone have any idea as to what would be tripping safety net in my case, or how they manage to pass on their device?
Spooderman46 said:
I've been trying very hard to pass safety net on my axon 7, I first tried when I had LineageOS, Magisk and Xposed (not systemlessly installed) and a few other tweaks that appeared to modify the system partition, then after realising they may be affecting safety net I completely wiped my device (data,cache,system) to make sure I had a completely fresh start. Then proceeded to flash the MicroG version of LineageOS, and install Magisk and Xposed Systemlessly making sure nothing I did affected the system partition. So I thought I would be set, did safety net check andddd it failed. Then I did some searching and found safety net will check for bootloader unlocked status, so I found a kernel (HELLSGATE.V1) which tricks safety net (or is supposed to) into believing bootloader is still locked. And safety net still fails, this is really annoying I'm just wanting to use Android Pay yet I can't. Does anyone have any idea as to what would be tripping safety net in my case, or how they manage to pass on their device?
Click to expand...
Click to collapse
Xposed is causing safetynet to fail. No matter how Xposed is installed, it will always trigger safetynet. But with systemless xposed, you can disable xposed in the xposed installer app by toggling it at the top and rebooting
Teet1 said:
Xposed is causing safetynet to fail. No matter how Xposed is installed, it will always trigger safetynet. But with systemless xposed, you can disable xposed in the xposed installer app by toggling it at the top and rebooting
Click to expand...
Click to collapse
Still get 'invalid response' through magisk manager even after disabling xposed
This is why mine stayed stock......
Normally I would at least unlock, install TWRP and root to de-bloat, install V4A and maybe Xposed. Had to wean myself off those mods on this phone but used to it now. Life is much simpler
Nougat is pretty good. Be nice to see Oreo official soon.
Spooderman46 said:
Still get 'invalid response' through magisk manager even after disabling xposed
Click to expand...
Click to collapse
Safetynet doesn't check the bootloader. Look I can even pass safetynet while dualbooting LOS. Just wipe system and install LOS, OpenGApps and Magisk, maybe some other mod like the AK4490 patch and Viper4ARISE. That definitely will pass safetynet.
After a long time using SuperSU, I switched to Magisk yesterday, for it's modules and of course Magisk Hide. So, starting with a full stock B414 rom, I unlocked my BL, installed OldDroid's TWRP and flashed Magisk 16.0 .
Everything went fine, I'm able to give root access to my apps. What I'm trying to do now is passing SafetyNet check.
I downloaded SafetyNet "attest" from the store and ran a test -> Basic integrity : false and CTS profile match -> false :crying:
Reading various tutorials, I enabled magisk hide, selected a few google apps to hide (store, services framework) , enabled Host systemless and magisk Core (rebooted my phone between these changes), cleared Store data. Regardless of what I've done, I keep failing at SafetyNet check. Did I miss something basic ? Did someone manage to pass safetynet on a P9 Lite with Nougat ?
EinderJam said:
After a long time using SuperSU, I switched to Magisk yesterday, for it's modules and of course Magisk Hide. So, starting with a full stock B414 rom, I unlocked my BL, installed OldDroid's TWRP and flashed Magisk 16.0 .
Everything went fine, I'm able to give root access to my apps. What I'm trying to do now is passing SafetyNet check.
I downloaded SafetyNet "attest" from the store and ran a test -> Basic integrity : false and CTS profile match -> false :crying:
Reading various tutorials, I enabled magisk hide, selected a few google apps to hide (store, services framework) , enabled Host systemless and magisk Core (rebooted my phone between these changes), cleared Store data. Regardless of what I've done, I keep failing at SafetyNet check. Did I miss something basic ? Did someone manage to pass safetynet on a P9 Lite with Nougat ?
Click to expand...
Click to collapse
Hello,
i used it some times ago...
Try to enable usb-debugging together with magisk/hide,
then reboot and see what happen.. ( this is what i done )
All the best
Thanks for your answer ! However, it didn't changed anything, safetynet check failed. Interesting fact, after rebooting, both magisk hide and usb debugging are disabled... Is this normal ?
EDIT : It's more than that, usb debugging gets disabled as soon as I quit settings
managed to fix this using another xda thread, but safetynet keeps failing and magisk hide is always disabled on startup
https://twitter.com/topjohnwu/status/1029239685338419200
I was running stock 7.1.1 and everything was fine. Then i decided to try LOS 15.1, with magisk 17.4 but encountered an issue with safetynet cts profile false that prevented me from using android pay. I then proceeded to flash B35 EDL, and then do the sd upgrage to Oreo B20, but i still have the same issue with failing cts profile.
AI'm no longer rooted, running stock but still fail safetynet. Any one have any ideas what I can try next? at this point i just want cts profile to pass on the current oreo b20 stock.
Thanks!
It could be that SafetyNet detects that you have an unlocked bootloader, but there are ways to hide that (custom kernel, Magisk, etc). Do you have Xposed installed? That's an automatic SN fail. You haven't changed system partition in any way at all? It's also possible that Google hasn't yet approved B20 despite it being official rather than beta. There could be other factors too. SN looks at lots of things, many of which Google won't talk about.
You need to install magisk hide props and then in a terminal
"Su"
Grant superuser
Then
"Props"
And follow the on-screen instructions. Stupid that Google pay has a problem with rooted phones as it's painfully simple to get around it
You can find magisk hide props in the "download" section of magisk manager
Check the settings in the Google play store, Device not certified can be an issue when you change Roms.
The link between the device and Google has been broken, hence the device not certified.
There is an app Device ID that can add the certification back to its original state.
Hope this helps
Turned out to be it was because of the unlocked bootloader.
funny story... i locked the bootloader without having oem unlock enabled . Got bricked, couldn't boot into EDL... so i had to take it apart and ground the test point to put it into EDL.
xavoc said:
Turned out to be it was because of the unlocked bootloader.
funny story... i locked the bootloader without having oem unlock enabled . Got bricked, couldn't boot into EDL... so i had to take it apart and ground the test point to put it into EDL.
Click to expand...
Click to collapse
There's a tool for that now; you may not have had to open it: https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
TPMJB said:
You need to install magisk hide props and then in a terminal
"Su"
Grant superuser
Then
"Props"
And follow the on-screen instructions. Stupid that Google pay has a problem with rooted phones as it's painfully simple to get around it
You can find magisk hide props in the "download" section of magisk manager
Click to expand...
Click to collapse
Im trying out Magisk 16.7 (I saw some posts that said 17 causes bootloops) and MM 6.0.1. I don't see hide props in downloads? What can I do to pass safetynet? Thanks
I'm now running twrp with Oreo B20 stock.
xavoc said:
Im trying out Magisk 16.7 (I saw some posts that said 17 causes bootloops) and MM 6.0.1. I don't see hide props in downloads? What can I do to pass safetynet? Thanks
I'm now running twrp with Oreo B20 stock.
Click to expand...
Click to collapse
try this thread https://forum.xda-developers.com/axon-7/development/kernel-magisk-17-stock-roms-t3856809/page2
Update to Magisk v17 and then try the above solution
xavoc said:
Im trying out Magisk 16.7 (I saw some posts that said 17 causes bootloops) and MM 6.0.1. I don't see hide props in downloads? What can I do to pass safetynet? Thanks
I'm now running twrp with Oreo B20 stock.
Click to expand...
Click to collapse
"Magisk hide props config" is literally what it is called. If you can't find it, you're doing it wrong.
If all else fails, google then install manually.
Had to upgrade to magisk 17 to see the hide prop module download. Still couldn't pass safetynet with Oreo B20. Switched to LOS 15.1 and now everything works.
i went from stock everything, oem unlock, fastboot install of twrp fajita, flash stock rom downloaded from oneplus, then magisk
then i was having an issue with magisk , viper audio wasnt working properly
restarted to recovery, meant to wipe dalvik but pressed something else and borked the phone.
wiped everything, re installed the twrp recovery, re flashed zip. re flashed magisk again
now, i have to turn on magisk hide ( to pass cts profile ), which is something i never had to do before and i cant find netflix on the play store.
what can i do to correct the cts profile fail please.
Use this module: Magisk Hide Props Config
It requires: BusyBox, installer in this thread first post.
To activate the module and chose your new certified fingerprint you will need a terminal emulator, you can use any one you want really, personally I use this one.
Any questions ask.
Hi
I tried this, everything went through smoothly enough but it did not resolve the issue. To be clear this is what i did.
downloaded the magiskhide props module, installed through magisk
downloaded the busybox installer , installed through magisk
restarted
opened terminal, ran command 'props'
went through the process or redoing the files for the fingerprint reader according to make and model of my phone.
restarted
disabled magiskhide in magisk
restarted
still failing cts
did i miss something
it also mentioned that i am using a custom rom, i am using a stock rom downloaded from oneplus. i have unlocked the bootloader and am rooted using magisk .
do i need to re download and start again?
OhioYJ said:
Use this module: Magisk Hide Props Config
It requires: BusyBox, installer in this thread first post.
To activate the module and chose your new certified fingerprint you will need a terminal emulator, you can use any one you want really, personally I use this one.
Any questions ask.
Click to expand...
Click to collapse
leonzon said:
disabled magiskhide in magisk
Click to expand...
Click to collapse
Why are you disabling this? You need Magisk hide enabled. I rename Magisk as well. My phone passes safetynet and CTS. On the latest version of Magisk MagiskHide is off by default, it used to be on by default. TopJohnWu announced that a while back here.
OhioYJ said:
Why are you disabling this? You need Magisk hide enabled. I rename Magisk as well. My phone passes safetynet and CTS. On the latest version of Magisk MagiskHide is off by default, it used to be on by default. TopJohnWu announced that a while back here.
Click to expand...
Click to collapse
ok , so maybe thats all this is? damn, im sorry for wasting your time. What do you mean by you rename magisk, in the app drawer? the process?
thanks
leonzon said:
ok , so maybe thats all this is? damn, im sorry for wasting your time. What do you mean by you rename magisk, in the app drawer? the process?
thanks
Click to expand...
Click to collapse
In recent versions when you choose hide and it picks a random name for the Magisk Manager app it lets choose a name for the app instead of just Manager.