What the title says basically...
I don't like having my phone rooted and would rather not bother with Magisk.
You could install magisk and deactivate root. Then you're not able to give out or decline root access to apps.
JD. A said:
You could install magisk and deactivate root. Then you're not able to give out or decline root access to apps.
Click to expand...
Click to collapse
But why does all the Oreo rom fail SafetyNet?
I don't want yo use Magisk because I don't want to have to update every time SafetyNet is updated and Magisk fails.
I thought LinageOS would be out for this phone by now. They seem to be the only ones that are keen on keeping in SafetyNet friendly.
Back to Nougat for now I suppose.
mottokeki said:
But why does all the Oreo rom fail SafetyNet?
I don't want yo use Magisk because I don't want to have to update every time SafetyNet is updated and Magisk fails.
I thought LinageOS would be out for this phone by now. They seem to be the only ones that are keen on keeping in SafetyNet friendly.
Back to Nougat for now I suppose.
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but safetynet checks if your bootloader is unlocked. If it's unlocked you fail the safetynet check. There's a workaround in custom kernels that disables that check or returns it false, makes saftynet thinks that bootloader is locked.
LOS is out 7.1.2. We just have to wait for Oreo. If you wanna try a oreo rom either install magisk or a custom kernel and that should fix safetynet for you.
Related
Hello!
Now after Google seems to be tweaking the hell out of its Safetynet (bootloader check and whatever) I was wondered where this will lead us to. Especially since our devices, at least the Exynos ones come with an unlocked bootloader..
I tried a dozen of combinations from the above named tools without any success, as my mobile banking app seem to rely on that crap now too since it's latest update (I can live without Pokemon go ) it got me all little worried.
What are your experiences, how did you lock out Safetynet, do you guys ignore it? So many questions regarding that topic. Feel free to leave any comment.. :good:
From what I understand all s7 come with bootloader locked by default but on exynos variant, it's unlockable with a "OEM Unlock" toggle in developer option. So normal user who don't root or modified the phone don't affect by new safetynet.
So if you don't need root, you can turn off OEM Unlock and flash back stock rom. But if you need root, there's no known method for now to bypass safetynet.
Sent from my SM-G935F using Tapatalk
I haven't been able to log in PokemonGO with my S7 and on my OnePlus One for the last 24 hours
Samsung Galaxy S7
TWRP 3.0.2-3
Superman ROM v1.14 (SELinux status [kernel]: Permissive)
Supersu v2.78-sr1 systemless
topjohnwu's Xposed v86.2 systemless
Suhide v0.55
06suhide
RootSwitch 1.2.4
Click to expand...
Click to collapse
EDIT: It now works with my OnePlus One (removed the 06suhide fix and ticked the "Stop all SU deamons" option in RootSwitch), but stills doesn't work with my S7
OnePlus One
TWRP 3.0.2.0
Official ROM Cyanogen OS v13.1.2 Android 6.0.1
SELinux Status: Enforcing
Supersu v2.78-sr1 systemless
Suhide v0.55
06suhide
+Added RootSwitch 1.2.4
Click to expand...
Click to collapse
I've heard they can now detect and block Custom Recovery. I don't think it's true.
I tried that Again now, using Hydra Kernel 1.7.1 without that modified Boot stuff. Removed SuperSu and Xposed, flashed the new Root Free Kernel and safetynet i's Not Flagged. The Main Problem for me (and many others) ist, that the Phone wont Boot after installing SuHide 0.5x! I've used the Not Flagged System as testbase, TWRP doesnt Alter it in any Way, but once i install either Magisk v8 or SuperSu 1.78R1 it gets Flagged Again.. So without SuHide, which doesnt Boot the Phone at All its worthless..
Trying to pass safetynet to use my banks app and pokemon go, using the latest LOS14.1
I tried going the Magisk way, but it still fails CTS.
Is there anyway to make it happen with root and passing safetynet?
You have to use Magisk for root. SuperSU and LineageOS's versions of root will not pass safetynet from my experience. I don't know if it helps but I also have the Play Store and Nintendo's games enabled on Magisk Hide.
eMadman said:
You have to use Magisk for root. SuperSU and LineageOS's versions of root will not pass safetynet from my experience. I don't know if it helps but I also have the Play Store and Nintendo's games enabled on Magisk Hide.
Click to expand...
Click to collapse
I used this guide and it didn't work. Is there another MagiskSU that I'm missing?
EDIT: I got it to work! In the guide above, it says to flash SU in Systemless mode. I just flashed Magisk without SU and it worked! Thanks!
You need Magisk v12 and kernel that includes bootloader status patch. I'm using old version of AX7Kernel, but Beastmode also has it. Not sure about other ones. I'm running relatively recent build and using Android Pay pretty frequently.
@edit And make sure to enable Magisk Hide
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 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.
Hi guys,
Im im on stock nougat B12 rom , bootloader unlock and rooted. Bank apps etc when trying to unlock with fingerprint say "failed to get authorisation data"
Anyone had this issue?
crazyazz said:
Hi guys,
Im im on stock nougat B12 rom , bootloader unlock and rooted. Bank apps etc when trying to unlock with fingerprint say "failed to get authorisation data"
Anyone had this issue?
Click to expand...
Click to collapse
Rooted with what? If Magisk, check if you pass safetynet. If you don't, you may want to try the MagiskHide Props Config module, though i don't know if it would work on stock where props are already fine.
Thanks for the reply, rooted with magisk 16.7 other versions cause boot loops, i got the response is invalid to safetynet test
MagiskHide Props Config module need atleast v17.0 anything above 16.7 causes boot loops. Maybe I will give up on stock rom, what do you recommend?
crazyazz said:
MagiskHide Props Config module need atleast v17.0 anything above 16.7 causes boot loops. Maybe I will give up on stock rom, what do you recommend?
Click to expand...
Click to collapse
You could try going Treble, liquid remix is a good candidate with Speedy vendor or at least Kranoner's vendor.
There was a kernel that fixed the Magisk problems, mayhe check that up before switching
I did have an issue with this on Nougat B12 too. It worked to unlock the phone but not for my banking app.
On Oreo it's working really well, although the app has been updated too.