Database Develop

Method of getting past safety net

I recently found this method of getting past safety net without losing xposed mods: https://www.reddit.com/r/TheSilphRo...y_have_found_a_workaround_for_the_pokémon_go/
I haven't tried it out yet, but I was checking to see if anyone had as I know that unrooting on the turbo is a dangerous prospect. Would this be recommended?

jedibob7 said:
I recently found this method of getting past safety net without losing xposed mods: https://www.reddit.com/r/TheSilphRo...y_have_found_a_workaround_for_the_pokémon_go/
I haven't tried it out yet, but I was checking to see if anyone had as I know that unrooting on the turbo is a dangerous prospect. Would this be recommended?
Click to expand...
Click to collapse
There's nothing dangerous about this, but it won't work. Magisk is incompatible with our devices, so forget anything involving that. In order for suhide to work, you need a stock marshmallow rom that will pass safetynet on its own, and we don't have that. Your best bet is to install the Resurrection Remix rom and use the iSu app that the dev made for it to hide the built in CM root, but you still won't be able to use xposed.

That worked until two days ago. Now safety net has patched it and isu doesn't work anymore. This is confirmed by BHB27.
So sad. I only got to enjoy android pay with cm13 for 3 days..
TheSt33v said:
There's nothing dangerous about this, but it won't work. Magisk is incompatible with our devices, so forget anything involving that. In order for suhide to work, you need a stock marshmallow rom that will pass safetynet on it's own, and we don't have that. Your best bet is to install the Resurrection Remix rom and use the iSu app that the dev made for it to hide the built in CM root, but you still won't be able to use xposed.
Click to expand...
Click to collapse

fmz0507 said:
That worked until two days ago. Now safety net has patched it and isu doesn't work anymore. This is confirmed by BHB27.
So sad. I only got to enjoy android pay with cm13 for 3 days..
Click to expand...
Click to collapse
Lame. Well, Chainfire did warn us that this was a losing battle. I guess he was right.

Actually there's some light to the end of the tunnel lol It was some later changes that broke it. BHB is still figuring out what caused it.
But if you use isu1.2 and kernel 202.1 it still works (also must enable SE linux in the kernel editor). I didn't have to do all that to get it to work but for now this config still works..
But yes, this is a hard battle to fight.
TheSt33v said:
Lame. Well, Chainfire did warn us that this was a losing battle. I guess he was right.
Click to expand...
Click to collapse

What are the factors that cause a device to fail SafetyNet?

Hello everyone!
Since Snapchat is one of my most used social app and unfortunately i use a rooted device with custom ROM.
I've seemed to try all the hiding methods on the forums inuding, Playstore Visa, Magisk HideProps and all.
Tried Magisk Hide, but that fails to. Enabling core only module messes up my Magisk Completely, i dont know how
So i need to to know what factors trigger Safetynet.
My Device -
Samsung galaxy core prime
CrDroid 7.1.2
Magisk 16.2 Beta
Kernel SElinux permissive (if it matters)
Thanks!

If you scroll down here, you'll find a table with examples over the different things that'll trigger SafetyNet:
https://developer.android.com/training/safetynet/attestation#compat-check-response
But, are you passing SafetyNet or not? You're only talking about Snapchat, and if I remember correctly you can pass SafetyNet and Snapchat will still complain.

Didgeridoohan said:
If you scroll down here, you'll find a table with examples over the different things that'll trigger SafetyNet:
https://developer.android.com/training/safetynet/attestation#compat-check-response
But, are you passing SafetyNet or not? You're only talking about Snapchat, and if I remember correctly you can pass SafetyNet and Snapchat will still complain.
Click to expand...
Click to collapse
No i do not pass Safetynet.

SnapDrag910 said:
No i do not pass Safetynet.
Click to expand...
Click to collapse
I'm going to assume you've checked here (if not, here's a great link):
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
And you can always take a look at the basics (what Magisk can't hide, as an example):
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Magisk_can_not_hide
And if nothing else, here's some info on what to provide when having problems:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Asking_for_help

Didgeridoohan said:
I'm going to assume you've checked here (if not, here's a great link):
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
And you can always take a look at the basics (what Magisk can't hide, as an example):
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Magisk_can_not_hide
And if nothing else, here's some info on what to provide when having problems:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Asking_for_help
Click to expand...
Click to collapse
Whoa! thanks alot @Didgeridoohan

Sometimes rooted phones , and custom ROMs
Also kernel in rare cases and Xposed

Cherifiali said:
Sometimes rooted phones , and custom ROMs
Also kernel in rare cases and Xposed
Click to expand...
Click to collapse
Ok. Thanks to all for helping me. Ill give my phone one more shot.
Also @Cherifiali my phone has -
Rooted -
Custom Kernel -
Xposed -
Custom ROM -

SnapDrag910 said:
Ok. Thanks to all for helping me. Ill give my phone one more shot.
Also @Cherifiali my phone has -
Rooted -
Custom Kernel -
Xposed -
Custom ROM -
Click to expand...
Click to collapse
Maybe you ROM so
Try saftynet modules for Magisk

Pie os with google pay working

Please post a PIE ROM with Google pay working(India)
CUSTOM ROM or root detected is the error when using PIE ROM like havoc,pixel,aosp.........
Please provide ROM with Google pay working....

All Pie ROMs do have Google Pay working. You've not installed Magisk, which is a must to pass Safetynet on Custom ROMs. No Magisk != No Safetynet pass. You can't not install Magisk and stay rootless, it still will detect your bootloader is unlocked and will still fail Safetynet.

Hey, Skydragon 12/10 build and H4K3ROM seems to work with google pay india as i tried.
I think Google pay india has some issue or what am not sure. It isn't working with any other ROM as of now. Even when we've Hidden all google apps and related app, also have tried hiding magisk it self.

Safetynet and GPay working flawlessly here, without Magisk or any hacks and tweaks. Cheers.

shawnsaimohan said:
Please post a PIE ROM with Google pay working(India)
CUSTOM ROM or root detected is the error when using PIE ROM like havoc,pixel,aosp.........
Please provide ROM with Google pay working....
Click to expand...
Click to collapse
Dirty Unicorns latest RC build passes Safetynet out of the box. Google Pay working. No Encryption yet.

Dirk said:
Dirty Unicorns latest RC build passes Safetynet out of the box. Google Pay working. No Encryption yet.
Click to expand...
Click to collapse
Apparently Google Pay in India (rebranded from Google Tez) has issues on the latest RC. No reports of any issues from other regions.

legendavey said:
Apparently Google Pay in India (rebranded from Google Tez) has issues on the latest RC. No reports of any issues from other regions.
Click to expand...
Click to collapse
The issue was the user, not the ROM.
---------- Post added at 14:58 ---------- Previous post was at 14:56 ----------
>Akshay< said:
Hey, Skydragon 12/10 build and H4K3ROM seems to work with google pay india as i tried.
I think Google pay india has some issue or what am not sure. It isn't working with any other ROM as of now. Even when we've Hidden all google apps and related app, also have tried hiding magisk it self.
Click to expand...
Click to collapse
Try it without Magisk, on a ROM that passes Safetynet out of the box.

Dirk said:
The issue was the user, not the ROM.
---------- Post added at 14:58 ---------- Previous post was at 14:56 ----------
Try it without Magisk, on a ROM that passes Safetynet out of the box.
Click to expand...
Click to collapse
i can't say about without magisk but with magisk those above roms and also bootleggers rom seems to work for me. I've not tried rom without magisk, will probably try it when i have some time to clean flash again and test.
i thought he was doing the same probably and facing the issue so shared what i found for a solution. Didn't mean to say bad about any rom or dev.

>Akshay< said:
Hey, Skydragon 12/10 build and H4K3ROM seems to work with google pay india as i tried.
I think Google pay india has some issue or what am not sure. It isn't working with any other ROM as of now. Even when we've Hidden all google apps and related app, also have tried hiding magisk it self.
Click to expand...
Click to collapse
Yes. Google Pay for India uses a different package name as the rest of the world that has contactless (NFC) payments. We have UPI gateway based payments and way more stringent rules by NPCI. Since they're two separate packages, it definitely makes sense that Google Pay works for some but the rebranded Google Tez in India has issues with some ROMs without Magisk.
I'm using the Indian Google Pay (aka Tez) on LineageOS beta without Magisk and I have had zero issues so far. It didn't work very well on the DU RC for me, kept logging me out after a while. But I haven't had a single issue for three weeks now on the LOS beta.

legendavey said:
..Google Tez in India has issues with some ROMs without Magisk.
I'm using the Indian Google Pay (aka Tez) on LineageOS beta without Magisk and I have had zero issues so far. It didn't work very well on the DU RC for me, kept logging me out after a while. But I haven't had a single issue for three weeks now on the LOS beta.
Click to expand...
Click to collapse
I think you meant with Magisk? Otherwise you just contradicted yourself with your next sentence.
If a ROM passes Safetynet, i.e Selinux Enforcing/Verified Boot Patches in Kernel/Certified in Play Store then any app no matter what it's name or where it's used, will work if it checks for Safetynet status.
The problems i've seen reported were all with Magisk. Then there are factors like people not knowing to clear Cache/Data on Play Store if coming from a failing setup to a passing one, before trying Google Pay.
Sadly, at the moment Magisk is going to be needed most of the time because the number of ROMs that pass Safetynet out of the box right now is about Three, including DU. With all the Selinux Permissive ROMs Magisk is the only solution.
I wouldn't count on LOS passing out of the box once it's in Stable. That would break their 'Charter'. The maintainer has already said he hasn't done anything deliberately to pass Safetynet. Maybe accidentally...? Who knows. It will eventually need a custom Kernel with the verified boot patches to pass. (Not Caesium though as it still breaks the camera when paired with LOS. The old 'Black image with flash' issue. Still a problem on LOS Pie and presumably any ROMs that will be based on it like RR, if and when it arrives. RR of course comes with Caesium so will need a Kernel flashed on top that doesn't break the camera).
So many problems still with Pie. I'm back on RR Oreo with Franco Kernel for now. (And no Black image problem!)

Dirk said:
I think you meant with Magisk? Otherwise you just contradicted yourself with your next sentence.
If a ROM passes Safetynet, i.e Selinux Enforcing/Verified Boot Patches in Kernel/Certified in Play Store then any app no matter what it's name or where it's used, will work if it checks for Safetynet status.
The problems i've seen reported were all with Magisk. Then there are factors like people not knowing to clear Cache/Data on Play Store if coming from a failing setup to a passing one, before trying Google Pay.
Sadly, at the moment Magisk is going to be needed most of the time because the number of ROMs that pass Safetynet out of the box right now is about Three, including DU. With all the Selinux Permissive ROMs Magisk is the only solution.
I wouldn't count on LOS passing out of the box once it's in Stable. That would break their 'Charter'. The maintainer has already said he hasn't done anything deliberately to pass Safetynet. Maybe accidentally...? Who knows. It will eventually need a custom Kernel with the verified boot patches to pass. (Not Caesium though as it still breaks the camera when paired with LOS. The old 'Black image with flash' issue. Still a problem on LOS Pie and presumably any ROMs that will be based on it like RR, if and when it arrives. RR of course comes with Caesium so will need a Kernel flashed on top that doesn't break the camera).
So many problems still with Pie. I'm back on RR Oreo with Franco Kernel for now. (And no Black image problem!)
Click to expand...
Click to collapse
I think my post was pretty clear, but I can type it out again using different words if you want.
LOS 16 beta allows GPay India (Tez) without Magisk, without any tweaks. *Doesn't* work on DU or *any* other ROM without Magisk in my experience. Magisk doesn't break Safetynet, it *fixes* it on most ROMs that don't pass by default.
Yes, DU passes Safetynet out of the box without Magisk too, but it occasionally logs me out of GPay India (Tez) and Netflix occasionally disappears from the Play Store. Which means something isn't working properly. Probably because its a userdebug build. I honestly couldn't care about DU rn because encryption is broken and they seem to be ignoring my report about it on JIRA.
I know about the LOS charter. I'll probably flash a custom kernel like Franco when LOS goes official.
I dunno what these problems with Pie that you speak of are. I haven't had a single issue and is now my daily driver. Oreo battery is also horrible compared to Pie in my experience, and the interface feels outdated. But you do you, bud.

shawnsaimohan said:
Please post a PIE ROM with Google pay working(India)
CUSTOM ROM or root detected is the error when using PIE ROM like havoc,pixel,aosp.........
Please provide ROM with Google pay working....
Click to expand...
Click to collapse
RR 7.0.0

Best ROM for MI 9 Lite

What's the best custom ROM (and its' build number) in terms of performance, stability, functionality & battery life? (note: 2-sides call recording must be available)
Thanks

To answer my own question - I found that the best ROM is the stock Xiaomi 11.0.1 (QFCMIXM/) ROM, rooted with Magisk and using SKVALEX call recording through Magisk. Works perfectly.
As I don't mind tripping safetynet, installed edXposed, cleared dalvik cache, installed edXposed manager. Flawless.
p.s. Tried xiaomi.eu ROMs, too many minor and sometime major issues made me decide to stick with stock.

Very helpful infos, thanks.
I am with xiaomi.eu rom v11.0.4 with magisk installed and also adaway for ad blocking,
There are some bugs, but I dont't want many chinese useless apps (except the usefull ones, e.g remote control, compass, etc).
Do you recomend going back to global?

Absolutely. You can always carefully debloat it using apps such as Titanium Backup.

MMX
doclucas said:
To answer my own question - I found that the best ROM is the stock Xiaomi 11.0.1 (QFCMIXM/) ROM, rooted with Magisk and using SKVALEX call recording through Magisk. Works perfectly.
As I don't mind tripping safetynet, installed edXposed, cleared dalvik cache, installed edXposed manager. Flawless.
p.s. Tried xiaomi.eu ROMs, too many minor and sometime major issues made me decide to stick with stock.
Click to expand...
Click to collapse
The MiuiMix,it's a good room, whith a saver battery.
Safetynet it's ok.
At the end, it's Muii.
You can uninstall unnecessary apps with XiaomiADBFastbootTools.

Thanks for the recommendation, @paco666. I may check it out in the future.
I was able to fix safetynet by instaling the latest canary edXposed from the CI:
https://ci.appveyor.com/project/ElderDrivers/edxposed/history
This specific latest build ATM:
https://ci.appveyor.com/project/ElderDrivers/edxposed/builds/32933762/artifacts
Also removed one module from there that tripped safetynet and it's ok now, although it does fail from time to time, but only for a few minutes and then returns back to normal green.
I highly recommend using edXposed with CustoMIUIzer module which adds A LOT of enhancements, including extended power menu and disabling secure content protection etc.
https://repo.xposed.info/module/name.mikanoshi.customiuizer
"Hidden Settings" app from the play store is also very useful:
https://play.google.com/store/apps/details?id=com.ceyhan.sets&hl=en
This is my backup phone and overall I am extremely pleased with it. My main phone is Samsung Note 10+ and I still love this Xiaomi, thanks to all the modules, apps, great specs and built in features.
P.S. I could do without the annoying 7 days waiting time (for bootloader unlocking code), but that's currently my only gripe.

SafetyNet basicintegrity fails

I have two Xiaomi phones, one Redmi Note 8 and one Redmi Note 10, both with unlocked bootloaders. I made a fresh factory reset on them and installed the latest version of Magisk.
My problem is that SN basicintegrity fails on both of them (and ctsProfile as well of course). But I want to take care of basicintegrity first.
What I have done already is to enable MagiskHide and also Hide Magisk app with a custom name.
For MagiskHide, I selected all modules under "Google Play services" and "Google Play Services for AR". Not sure if I should select anything else. I also tested hiding with a root checker app and it looks that hiding works.
I have no Magisk modules installed. Using stock ROM on both phones.
Is there anything else I should to to pass basicintegrity SN?

API error?
If so, just wait for some days new version will solve this problem.

Pixel 3 XL on android 11 with magisk 22. Safetynet passed up until a few days ago. Not now tho. I wonder what changed?

Guys just put some more effort into searching, there is one big Magisk support thread and lot of discussion about this issue

Update to latest Canary
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk

Lord Sithek said:
Guys just put some more effort into searching, there is one big Magisk support thread and lot of discussion about this issue
Click to expand...
Click to collapse
It's difficult to find info in one big thread, not sure why that's how most discussion happens. Separate threads make more sense.

hkjo said:
It's difficult to find info in one big thread, not sure why that's how most discussion happens. Separate threads make more sense.
Click to expand...
Click to collapse
Multiplying posts doesn't make sense in my opinion. Several different threads were created for the same issue. It's not really that difficult to check few last pages of the main support thread since the issue is relatively new

Yeah, multiple threads on the same topic aren't good.
But one big thread that mixes different discussions beats the whole idea. Threads were invented for a reason. To concentrate discussion on a specific topic or sub-topic, and to have a sensible title. To save you from scanning posts in a megathread to find out if they're about your topic or not. Also, not all discussion is necessarily recent.

I had the exact same issue yesterday.
A quick search of the support thread took me to
The solution

wfred said:
I had the exact same issue yesterday.
A quick search of the support thread took me to
The solution
Click to expand...
Click to collapse
Hello,
Please, if you could—I hope you could—post the link to the solution you found. The masked link isn't working.
Thanks!

Cyb3rFr4nk said:
Hello,
Please, if you could—I hope you could—post the link to the solution you found. The masked link isn't working.
Thanks!
Click to expand...
Click to collapse
The linked solution is:
Update Magisk (to build 22103 or later).
This thread is about the Magisk apps SafetyNet checker extension needing an update due to an API error. SafetyNet wasn't actually failing...
If you need a few tips on how to get SafetyNet passing, there are some collected here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet

Cyb3rFr4nk said:
Hello,
Please, if you could—I hope you could—post the link to the solution you found. The masked link isn't working.
Thanks!
Click to expand...
Click to collapse
Here you go, don't know why it was messed up
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Basically it was moving to the canary

Didgeridoohan said:
The linked solution is:
Update Magisk (to build 22103 or later).
This thread is about the Magisk apps SafetyNet checker extension needing an update due to an API error. SafetyNet wasn't actually failing...
If you need a few tips on how to get SafetyNet passing, there are some collected here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
Click to expand...
Click to collapse
Thank you!
I had visited the link to your site, through Google search, while searching for a fix. I also went to magisk general discussion thread, and started reading from April 23rd backwards, in a bid to locate/trace "the solution." While doing that, I came across "the solution," but didn't really try that as I'm on a later stable build (23000) than that canary build.
Background: I started facing this issue, yesterday, after I installed 23.0, from 20.4—which I had been on for a long time and didn't really want to upgrade from to avoid something like this, but after updating my Redmi Note 7 to MIUI 12.5 (Q) (I'm on xiaomi.eu stable), I started having restarts. So, I made the jump.
The restarts stopped after uninstalling that build, so I decided to upgrade to the latest stable. Did that, only to find that SafetyNet no longer passes. Basic integrity fails, and that was before installing EdXposed, which usually causes this. When I first noticed it, I checked my Play Store for device certification status, and it came out positive. That changed after a couple of reboots—I don't know which one in particular, as there were quite some during that time.
I've tried everything—except uninstalling and re-installing magisk—without success: different versions of Universal SafetyNet Fix, MagiskHide Props, enabling and disabling MH.
I have decided to put up with it. Since only a couple of my apps are affected (no GPay in my country), I am trying to make do without them until I get my new phone. Don't wish to do something that would require a factory reset/data wipe, as this is currently my DD, and I'd hate to get stranded.
Thanks all the same.

wfred said:
Here you go, don't know why it was messed up
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Basically it was moving to the canary
Click to expand...
Click to collapse
Cyb3rFr4nk said:
Thank you!
I had visited the link to your site, through Google search, while searching for a fix. I also went to magisk general discussion thread, and started reading from April 23rd backwards, in a bid to locate/trace "the solution." While doing that, I came across "the solution," but didn't really try that as I'm on a later stable build (23000) than that canary build.
Background: I started facing this issue, yesterday, after I installed 23.0, from 20.4—which I had been on for a long time and didn't really want to upgrade from to avoid something like this, but after updating my Redmi Note 7 to MIUI 12.5 (Q) (I'm on xiaomi.eu stable), I started having restarts. So, I made the jump.
The restarts stopped after uninstalling that build, so I decided to upgrade to the latest stable. Did that, only to find that SafetyNet no longer passes. Basic integrity fails, and that was before installing EdXposed, which usually causes this. When I first noticed it, I checked my Play Store for device certification status, and it came out positive. That changed after a couple of reboots—I don't know which one in particular, as there were quite some during that time.
I've tried everything—except uninstalling and re-installing magisk—without success: different versions of Universal SafetyNet Fix, MagiskHide Props, enabling and disabling MH.
I have decided to put up with it. Since only a couple of my apps are affected (no GPay in my country), I am trying to make do without them until I get my new phone. Don't wish to do something that would require a factory reset/data wipe, as this is currently my DD, and I'd hate to get stranded.
Thanks all the same.
Click to expand...
Click to collapse