Unable to Pass Safety Net? - ZTE Axon 7 Questions & Answers

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.

Related

How to pass SafetyNet?

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.

Tried manually flashing firmware with fastboot and now no system

Ok so I've been having a hell of a time with this phone so far. I have the boost mobile variant (xt1766). I unlocked the bootloader, installed twrp, but forgot to make a backup before flashing supersu, after which my phone would no longer boot so I flashed lineageOS. It booted up fine but I had no 3g connection so I wanted to go back to stock. I downloaded the stock firmware, but couldn't get RSD lite to install on my computer so I extracted all the files and flashed them manually with fastboot. After that my phone wouldnt boot and TWRP couldnt mount the data partition so I couldnt restore my lineage backups. I had to format the data partition in order to restore from backup but now I have nothing on internal storage, and my phone wont boot into system unless I boot into factory mode from the bootloader. It boots up fine in factory mode but now I have no network connection, no service whatsoever.
Under sim status it says Network: unknown, cellular network type: unknown, Service state: Radio Off, etc. I tried manually turning the radio on but that didn't work. I really just want to go back to stock but I don't understand how to accomplish this. I flashed everything in the firmware package in the correct order, and somehow it just rendered my phone useless. any help would be much appreciated. I've tried just about everything and I'm at a loss here.
Update:
I successfully got back to stock. For some reason executing the fastboot commands manually one at a time didn't work so I made a bat file with all the proper commands, executed it, and this time it worked. Not sure why it didn't work the other way but it might be because I didn't flash the stock recovery so as not to replace TWRP. Apparently when flashing firmware its all or nothing.
Are there any custom ROMs with 3G functionality for this device? Cuz so far every single one I've tried gets no network connection but this stock ROM is lame.
AMShiech said:
Are there any custom ROMs with 3G functionality for this device? Cuz so far every single one I've tried gets no network connection but this stock ROM is lame.
Click to expand...
Click to collapse
Not "lame" unless that's the latest descriptor for a reliable, fully functional, device optimized ROM that just works. If you want additional bling/tweaks flash Xposed framework and a few well regarded modules like GravityBox.
Alternatively, you can cycle through the various custom ROMs and decide which suite of compromises you're willing to live with. Suggest a careful read of the relevant ROM thread before diving in. Be sure to backup what works (including stock!) and store those nandroids on a SD card and/or off-device.
Good luck.
AMShiech said:
Update:
I successfully got back to stock. For some reason executing the fastboot commands manually one at a time didn't work so I made a bat file with all the proper commands, executed it, and this time it worked. Not sure why it didn't work the other way but it might be because I didn't flash the stock recovery so as not to replace TWRP. Apparently when flashing firmware its all or nothing.
Are there any custom ROMs with 3G functionality for this device? Cuz so far every single one I've tried gets no network connection but this stock ROM is lame.
Click to expand...
Click to collapse
That's because you're on boost, not many ROMs here have CDMA support. There is a fix in the help section. But stock is fine for me. Gravitybox and all features of any of the broken unofficial ROMs are all there. Rock solid, and LTE. But flash away dude.
madbat99 said:
That's because you're on boost, not many ROMs here have CDMA support. There is a fix in the help section. But stock is fine for me. Gravitybox and all features of any of the broken unofficial ROMs are all there. Rock solid, and LTE. But flash away dude.
Click to expand...
Click to collapse
I haven't been able to install the Xposed framework. Xposed installer says my CPU architecture is incompatible. When I flashed Xposed v89 for nougat my phone wouldn't boot past the boost logo. I keep hearing about people getting Xposed working on this device but I can't figure out how they're doing it. I would love to be able to have gravity box on this ROM.
Apparently the purityOS guys made an unofficial work around a while back but all the download links in that thread are dead and I can't find it anywhere else. It's my understanding that i need to be able to set selinux to permissive on boot in order to install Xposed.
AMShiech said:
I haven't been able to install the Xposed framework. Xposed installer says my CPU architecture is incompatible. When I flashed Xposed v89 for nougat my phone wouldn't boot past the boost logo. I keep hearing about people getting Xposed working on this device but I can't figure out how they're doing it. I would love to be able to have gravity box on this ROM.
Apparently the purityOS guys made an unofficial work around a while back but all the download links in that thread are dead and I can't find it anywhere else. It's my understanding that i need to be able to set selinux to permissive on boot in order to install Xposed.
Click to expand...
Click to collapse
No, regular Xposed. Wipe cache and dalvik, and wait. Let it sit 5 - 10 minutes. It has to optimize everything. Make sure it's the arm build. It works fine, just gotta let it sit. First boot takes a good bit.
Or use magisk, and install Xposed through that.
Do not use that old purity crap. That's why the links are dead. It's old crap. Xposed works fine with no extra steps or messing with selinux.
AMShiech said:
I haven't been able to install the Xposed framework. Xposed installer says my CPU architecture is incompatible. When I flashed Xposed v89 for nougat my phone wouldn't boot past the boost logo. I keep hearing about people getting Xposed working on this device but I can't figure out how they're doing it. I would love to be able to have gravity box on this ROM.
Apparently the purityOS guys made an unofficial work around a while back but all the download links in that thread are dead and I can't find it anywhere else. It's my understanding that i need to be able to set selinux to permissive on boot in order to install Xposed.
Click to expand...
Click to collapse
That's BS; don't overcomplicate things. Xposed framework installs fine in enforcing mode. Make sure you have the correct framework for Android 7.1 (SDK 25) and your hardware (arm). You will also need the corresponding management app. There is no need to wipe anything before/after flashing the framework although doing so can't hurt. First boot will take awhile; patience is a virtue.
Got Xposed working now with gravitybox and edge in full effect so this stock ROM is now much more tolerable. I guess I had the wrong version of Xposed installer and didn't wait long enough for boot to finish.
It broke safetynet though which I fully expected. I'd rather use the systemless Xposed magisk module so I can pass safetynet but I can't get any magisk modules to install successfully either through magisk or by flashing with TWRP. Apparently I'm not the only one having this issue either and it doesn't look like anyone has found a fix for it as of yet. I guess for now I'll have to live without Pokemon go lol
AMShiech said:
Got Xposed working now with gravitybox and edge in full effect so this stock ROM is now much more tolerable. I guess I had the wrong version of Xposed installer and didn't wait long enough for boot to finish.
It broke safetynet though which I fully expected. I'd rather use the systemless Xposed magisk module so I can pass safetynet but I can't get any magisk modules to install successfully either through magisk or by flashing with TWRP. Apparently I'm not the only one having this issue either and it doesn't look like anyone has found a fix for it as of yet. I guess for now I'll have to live without Pokemon go lol
Click to expand...
Click to collapse
Well yes there is most definitely a fix. Your problem is the f2fs loopback bug. Your solution is the f2fs loopback bug workaround module. It's in the magisk manager app. Download there, but install it in twrp. Then magisk modules will work. You must have halted your research a little early because this is well known, and posted in many places.
You still won't pass safetynet with systemless Xposed. Which a little reading would have also revealed. But, you can turn off Xposed in magisk , then reboot and pass safetynet. Do whatever it is you need safetynet for, then turn it back on and reboot. You must completely uninstall the Xposed you have to use magisk Xposed. You must use the Xposed installer APK that's linked in Xposed for magisk so it recognizes systemless Xposed. So uninstall Xposed with uninstaller zip, uninstall Xposed APK. Wipe caches. Then you can just go in magisk manager, scroll to the bottom of downloads, install Xposed sdk 25 module. Also Xposed installer APK linked 8n the readme that pops up when you click the Xposed module in magisk downloads. See screenshots below.
Also, there is more to pogo than safetynet. There is an entire thread devoted to it (more than one) in the magisk section of the forum.
You have a bit of reading to do in order to do the things you want. It's all very easy to find. You don't seem to be looking very hard.
madbat99 said:
Well yes there is most definitely a fix. Your problem is the f2fs loopback bug. Your solution is the f2fs loopback bug workaround module. It's in the magisk manager app. Download there, but install it in twrp. Then magisk modules will work. You must have halted your research a little early because this is well known, and posted in many places.
You still won't pass safetynet with systemless Xposed. Which a little reading would have also revealed. But, you can turn off Xposed in magisk , then reboot and pass safetynet. Do whatever it is you need safetynet for, then turn it back on and reboot. You must completely uninstall the Xposed you have to use magisk Xposed. You must use the Xposed installer APK that's linked in Xposed for magisk so it recognizes systemless Xposed. So uninstall Xposed with uninstaller zip, uninstall Xposed APK. Wipe caches. Then you can just go in magisk manager, scroll to the bottom of downloads, install Xposed sdk 25 module. Also Xposed installer APK linked 8n the readme that pops up when you click the Xposed module in magisk downloads. See screenshots below.
Also, there is more to pogo than safetynet. There is an entire thread devoted to it (more than one) in the magisk section of the forum.
You have a bit of reading to do in order to do the things you want. It's all very easy to find. You don't seem to be looking very hard.
Also I certainly hope that's not the app I think it is (the smiley face)? You're not allowed to promote or speak of that "warez" here. So screenshot is not a great idea.
Click to expand...
Click to collapse
I'm well aware that the problem is f2fs loopback but due to the bug I'm unable to install the fix. Can't install magisk modules so a fix in the form of a magisk module doesn't really help me. Ive tried installing it with TWRP a couple times with no success. As far as PoGo I've actually never even played that game. Was just curious about it.
And I'm not sure what app you're referring to but that "wow" face is a chrome shortcut. Changed it cuz I didn't like the default grey square.
AMShiech said:
I'm well aware that the problem is f2fs loopback but due to the bug I'm unable to install the fix. Can't install magisk modules so a fix in the form of a magisk module doesn't really help me. As far as PoGo I've actually never even played that game. Was just curious about it.
Click to expand...
Click to collapse
Trend continues; reread post you're disparaging. Or module OP. f2fs loopback 'fix' gets flashed in twrp or via fastboot (for the adventurous).
I edited my post shortly after your quote. Tried installing with TWRP more than once. Doesn't show up in magisk modules.
Just flashed with fastboot and now it seems to have worked. Fastboot for the win.
Maybe all caps will help out
go inside magisk manager> downloads search F2FS LOOPBACK BUG WORKAROUND, FLASH INSIDE TWRP!!! WILL NOT WORK IF ATTEMPTED TO FLASH THROUGH MAGISK MANAGER!!!!

Pass SafetyNet with Magisk

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

safetynet question - cts profile false

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.

RR-N 5.8.3 Safety Net Basic Integrity Fail

Magisk shows Cts Profile False, Basic Integrity False tries every solution available on the web also downloaded Magisk Hide Module, Turn On Magisk Hide in Magisk Manager, Turn Core Only Mode, Insalled Osmosis Busy Box, Changed Fingerprint of device etc all failed to pass safety net due to this i am unable to use Snapchat, Like Magic App, Netflix etc
Any resolution with this problem?
I can get root and the root hide from Magisk to work on the stock rom; but I've installed CyanogenMod 14.1 (android 7.1.1, rooted) and I have not found a way for the ctsProfile or Basic Integrity to pass. Magisk does continue to hide the root, but there are still apps that look for those two and I have found no resolution other than going back to stock rom with root (which is okay, but the custom mod is better).
Let me know.

Categories

Resources