Related
I got a problem. My Google Pay app doesn't work. I got magisk v18 with 2 modules: "universal safetynet fix v3-beta1 (magisk v17 fix)" and google face unlock. When I check the status it shows the two "ctsprofile" and "basicintegrity" as true both. In magisk hide, I selected "Google Pay" and "NFC service" apps, but also without their selection it isn't still recognized by a pos. Now, I'm really sure my payment card works, my bro one with a phone unrooted works fine.
How should I do for make pos recognize my LG H815 rooted Gpay?
Sorry my bad english
p.s. I haven't any xposed or similar installed.
On my OP6 with OOS 9.0.3, CTS returns false without any additional modules and Google Pay and other apps detect root and refuse to work. That happened with the update from 17.2 to 18.0
Unfortunately, I got no helping hint in the main support thread or in the other thread here reporting on failing banking apps.
Later... after downgrading to Magisk 17.2, MagiskHide is working again... an issue is open on Github on that.
Yeah but gpay still not working in my phone, also with magisk 17.2
theicecave said:
Yeah but gpay still not working in my phone, also with magisk 17.2
Click to expand...
Click to collapse
I'll try that when I'm next time in a shop here... but as Safetynet works, GPay should too...
akxak said:
I'll try that when I'm next time in a shop here... but as Safetynet works, GPay should too...
Click to expand...
Click to collapse
And that's the paradox. Lemme know.
Just was at a shop and paid successfully with Google Pay. 17.2 rocks.
Idk why mine is not recognized by pos. And for sure I can say that my NFC works, I use it with my headsets. It's a problem with my phone, it's rooted, and that's it. Gpay cannot be used with root, although it accepted my card payment card after I protected my ctsprofile etc. I lost hope
My OP6 is unlocked and rooted with Magisk. Back on 17.2 SafetyNet checks succeed again and I just could pay... with Magisk 18 though it failed.
What phone and how did you root?
akxak said:
My OP6 is unlocked and rooted with Magisk. Back on 17.2 SafetyNet checks succeed again and I just could pay... with Magisk 18 though it failed.
What phone and how did you root?
Click to expand...
Click to collapse
Which module do you use to protect safetynet, ctsprofile etc?
Just asking.. 'cause, as I told, also with magisk 17.2 it doesn't work.
No module, just plain Magisk and MagiskHide on Google Pay.
akxak said:
No module, just plain Magisk and MagiskHide on Google Pay.
Click to expand...
Click to collapse
No module? I need necessary to use "universal safetynet fix" to activating all 4 green checks on main page of magisk. Without it, last 2 (inside safetynet fix) are red: ctsprofile:false and basicintegrity:false.
And magisk hide with or not selecting gpay doesn't change anything.
However I'm considering the main problem is my rom, resurrection remix.
On OOS I have only two arrows...
ctsProfile and basicIntegrity
But I am on a stock rom
Yeah sorry my bad, I mean just these two.
I'm considering to flash my stock rom again. But it was Android 6. I should set nova launcher and lots of changes to modernize it : D
Also my bro used a stock one to let gpay work. Modded all ones seems not working.
I'm on Android 9 Pie... Nova is great, I use it myself.. with starting on the Oneplus, I stuck to the stock OS and had gold experiences... on the OP6 even mire as I can update it and keep it rooted from within the OS not needing TWRP anymore... allowing an easy upgrade process.
Just flashed up the stock rom of my H815. I installed magisk 17.2 (it's an android nougat). I activated MagiskHide only for Google Pay; now safety net says ctsProfile: false and basicIntegrity: true. I watched this thread and just at beginning of section Safetynet fix - changing device fingerprint seems to be my problem. But my phone hasn't fingerprint (rofl). So after installing modules MagiskHide Props Config and Busybox by osm0sis cts is still false. Watched this because seems the only well built guide about; this problem is splitted anywhere. No more ideas.
theicecave said:
Just flashed up the stock rom of my H815. I installed magisk 17.2 (it's an android nougat). I activated MagiskHide only for Google Pay; now safety net says ctsProfile: false and basicIntegrity: true. I watched this thread and just at beginning of section Safetynet fix - changing device fingerprint seems to be my problem. But my phone hasn't fingerprint (rofl). So after installing modules MagiskHide Props Config and Busybox by osm0sis cts is still false. Watched this because seems the only well built guide about; this problem is splitted anywhere. No more ideas.
Click to expand...
Click to collapse
If I understand you correctly, I think you've misunderstood... It's not about a fingerprint scanner, it's the device fingerprint property that needs to change. You'll have to run the props script and select a certified fingerprint from the list (the module is not a flash and forget module). But if you're on a stock ROM I would expect the CTS check to pass, so there might be something else going on. Anyway, try changing the device fingerprint and see if anything changes.
Didgeridoohan said:
If I understand you correctly, I think you've misunderstood... It's not about a fingerprint scanner, it's the device fingerprint property that needs to change. You'll have to run the props script and select a certified fingerprint from the list (the module is not a flash and forget module). But if you're on a stock ROM I would expect the CTS check to pass, so there might be something else going on. Anyway, try changing the device fingerprint and see if anything changes.
Click to expand...
Click to collapse
Idk how to do this and where is this list. He just attached a .zip on his thread.
Or maybe I do not understand english enough. Very probably.
theicecave said:
Idk how to do this and where is this list. He just attached a .zip on his thread.
Or maybe I do not understand english enough. Very probably.
Click to expand...
Click to collapse
If you're talking about the thread you linked, the "he" is me...
Take a look in the module documentation, most things should be covered there. But basically, what you need is a Terminal emulator where you just type 'props' and press enter. After that you can just follow the ui to do the rest.
Didgeridoohan said:
If you're talking about the thread you linked, the "he" is me...
Take a look in the module documentation, most things should be covered there. But basically, what you need is a Terminal emulator where you just type 'props' and press enter. After that you can just follow the ui to do the rest.
Click to expand...
Click to collapse
Solved following this. In effect, not so different on what were you talking about in your guide. At the moment both ctsprofile and basicintegrity are true, I just need to try Google Pay in a pos.
hi, i just flashed my xiaomi mix phone with Magisk 20.4. everything is new but the safetynet checks are failing.
i have previously tried on riru and edxposed. the checks say YES but i still cannot load pokemon go. i think those fixes are fake and not working, Google seems to be able to detect it still.
Can anyone help?
thanks.
jasonjiangyu said:
hi, i just flashed my xiaomi mix phone with Magisk 20.4. everything is new but the safetynet checks are failing.
i have previously tried on riru and edxposed. the checks say YES but i still cannot load pokemon go. i think those fixes are fake and not working, Google seems to be able to detect it still.
Can anyone help?
thanks.
Click to expand...
Click to collapse
Having the exact same issue with my Mix 3. Just flashed a few moments ago. Been looking at the other threads and it seems that no fix works as of now. Hoping that it isn't permanent as Google is cracking down on unlocked bootloaders.
Try to hide what you want via magisk hide.
Sorry, but that is not helpful. Same thing here. Device passed SafetyNet on 20.3. After upgrade to 20.4 it fails. What can I do to figure out what changed?
please refer here to set it up in your phone.
Be notice: If you don't use edxposed, just skip it. If you do, please remember to install canary version of edxposed in Edxposed manager !
Kris
Kris Chen said:
please refer here to set it up in your phone.
Be notice: If you don't use edxposed, just skip it. If you do, please remember to install canary version of edxposed in Edxposed manager !
Kris
Click to expand...
Click to collapse
Thank you! You were right, this was not caused by the Magisk upgrade, but by EdXposed. After upgrading to Canary version SafetyNet passes again.
I'd also like to add (in case someone stumbles across this thread looking for answers) that Magisk v20.4+ has MagiskHide disabled by default. On a fresh install you will have to enable it before Hide will be able to do it's thing.
So I'm trying to get Android 12 working with root and SafetyNet passing. I found that all the guides to be wrong or outdated. Problem with the latest Magisk canary is that it does not support MagiskHide. Problem with the latest stable Magisk (v23) is that it doesn't support Android 12. Here are the combinations I've tried:
Canary Magisk APK, Canary Magisk boot image, with Universal SafetyNet Fix v2.2.1 (Zygisk)
Result: No way to test if safety net passes within Magisk, but it doesn't seem to work.
Canary Magisk APK, Stable Magisk v23 boot image, with Universal SafetyNet Fix v2.1.3 (Riru)
Result: Does not work. MagiskHide automatically turns off after every reboot, probably because the canary boot image does not support it.
Stable Magisk v23 APK, Stable Magisk v23 boot image
Result: Device fails to boot. fast food indicates in an invalid signature. presumably happening because stable magisk v23 does not support Android 12.
Based on these test results these are my assumptions:
1. There is no way to run Magisk 23 on Android 12, and this article and its screenshot are fake:
https://www.droidwin.com/how-to-roo...k-on-android-12/#STEP_6_Boot_to_Fastboot_Mode
and this also does not work: https://krispitech.com/how-to-pass-safetynet-on-rooted-android-12/
OR
It was possible and Android 12 September 5th patch level but somehow not the latest December build?
There is no advantage to running mismatched Magisk APK and boot image versions
Both the Zygisk and Riru versions of the SafetyNet Fix do not work on the latest Android 12 builds.
The new DenyList system does nothing in allowing a SafetyNet bypass.
The ONLY working method That can possibly bypass safety net on Android 12 is using either of these 2 Magisk forks:
Custom Magisk by TheHitMan7 (Can’t find download link)
Alpha Magisk by vvb2060 (Can’t find download link)
Are these assumptions correct? Can someone please correct my misunderstandings?
You need Universal Safetynet Fix v2.2.0 or v2.2.1 which was just released 10 days ago.
To be honest, I haven't tried v2.2.1 yet, but I would imagine it will work. I'm on v2.2.0 right now.
Get it from here: https://github.com/kdrag0n/safetynet-fix
I have been using Magisk Canary 23016, USNF 2.2.0, and MagiskHide Props Config 6.1.2 on my Pixel 5 running the December Android 12 release. SafetyNet passes, GPay works.
I have DenyList blocking both GPay and Google Play Store..
Either you have something configured wrong, or you're having a unique issue. Others have been able to pass SafetyNet using a similar configuration.
No, Magisk Stable does not currently support Android 12. You MUST use Canary 23016; none of the previous builds properly handle the vbmeta flags in the boot image header.
I'm using the latest magisk canary, USNF 2.2.1 and no magisk hide props and am passing. I have Zygisk enabled, but that's about it. Install was flawless. Followed V0latyle's thread on going from A11 to A12 when the canary update dropped.
Thank you everyone, I got it working the way you said! I was super close.
-----------------------------------
V0latyle said:
I have been using Magisk Canary 23016, USNF 2.2.0, and MagiskHide Props Config 6.1.2 on my Pixel 5 running the December Android 12 release. SafetyNet passes, GPay works.
I have DenyList blocking both GPay and Google Play Store..
Either you have something configured wrong, or you're having a unique issue. Others have been able to pass SafetyNet using a similar configuration.
No, Magisk Stable does not currently support Android 12. You MUST use Canary 23016; none of the previous builds properly handle the vbmeta flags in the boot image header.
Click to expand...
Click to collapse
I only blocked play services with deny list and it worked.
One of the guides told me to flash stock vbmeta (idk what this is), and this bricked it until I re-flashed the ROM. But I guess that's not needed anymore.
flyoffacliff said:
Thank you everyone, I got it working the way you said! I was super close.
-----------------------------------
I only blocked play services with deny list and it worked.
One of the guides told me to flash stock vbmeta (idk what this is), and this bricked it until I re-flashed the ROM. But I guess that's not needed anymore.
Click to expand...
Click to collapse
Which guide?
V0latyle said:
Which guide?
Click to expand...
Click to collapse
How to Root Pixel Devices via Magisk on Android 12
In this comprehensive tutorial, we will show you detailed steps to root your Pixel device via Magisk running Android 12.
www.droidwin.com
On step 7. It says it's not necessary for some reason on newer devices but pixel 5 and older still require it. What does flashing this file actually do? Like what's the file made of?
flyoffacliff said:
How to Root Pixel Devices via Magisk on Android 12
In this comprehensive tutorial, we will show you detailed steps to root your Pixel device via Magisk running Android 12.
www.droidwin.com
On step 7. It says it's not necessary for some reason on newer devices but pixel 5 and older still require it. What does flashing this file actually do? Like what's the file made of?
Click to expand...
Click to collapse
Nothing needs to be done with vbmeta as long as you're using Magisk 23016.
I'll try to explain what it is and what it does as simply as I can but there isn't really a simple explanation...
Some components of Android system security, such as Verified Boot, incorporate a means by which the data being loaded from critical partitions is checked in real time as it is loaded. This is called "device-mapper verity". The raw data itself is read at the block device level and used to create a hash; this hash is then compared to a reference hash to determine the data has not been modified. The partition that contains this reference hash is vbmeta.
When the Android 12 beta was first released, Magisk had not yet been updated to properly handle Android 12 boot image headers. Verified Boot is disabled for the most part when the bootloader is unlocked; however some elements still remain to ensure you're booting a proper device boot image. Magisk did not preserve necessary information in the boot headers, so the device wouldn't boot; we would get a message in bootloader stating failed to load/verify boot images
We figured out a workaround for this: disable dm-verity and vbmeta verification altogether. This was done by flashing the vbmeta partition with those two options:
Code:
flash vbmeta vbmeta.img --disable-verity --disable-verification
The problem with this is it has some sort of safety interlock that prevents system from loading if verity/verification are disabled and /data isn't clean. So, rooting required wiping data. You probably discovered this during your "brick": you got a screen reading Cannot load Android system. Your data may be corrupt.
We also discovered that the vbmeta workaround had to be performed every time vbmeta was flashed - meaning no OTA updates, because if vbmeta was flashed without the disable options, we wouldn't be able to boot a patched boot image, and even if we re-disabled verity/verification, the device still wouldn't boot unless data was clean. The only way to update AND reroot AND keep data was to ensure that verity and verification were disabled every time the device was updated.
Fortunately, Magisk 23016 fixed all of this. We don't have to mess with vbmeta anymore. Magisk properly preserves the flags in the boot header, meaning that AVB recognizes it as a legitimate boot image, and the device is happy.
has anyone able to pass safety CTSprofile ?
Basic integrity is pass but CTSprofile Check isnt passed...
anybody able to pass in A12 (OnePlus Nord)
tried all effort but dint work, even Universal SafetyNet Fix v2.2.1 (Zygisk) isnt working..
its makes Basic Integrity Fail after Flash ( Universal SafetyNet Fix v2.2.1 (Zygisk).
I roll back to A11 then sadly....
shhahidxda said:
has anyone able to pass safety CTSprofile ?
Basic integrity is pass but CTSprofile Check isnt passed...
anybody able to pass in A12 (OnePlus Nord)
tried all effort but dint work, even Universal SafetyNet Fix v2.2.1 (Zygisk) isnt working..
its makes Basic Integrity Fail after Flash ( Universal SafetyNet Fix v2.2.1 (Zygisk).
I roll back to A11 then sadly....
Click to expand...
Click to collapse
You're doing something wrong. Don't overlook anything. I'm on Android 12.1 and pass safety net, Google pay works, Netflix works.
Have you configured the deny list in magisk?? If not do that then. I'd start fresh, don't connect to anything on first start. Hide everything about those Google apps. Then add your accounts etc etc. This is what worked for me no problem
thatsupnow said:
You're doing something wrong. Don't overlook anything. I'm on Android 12.1 and pass safety net, Google pay works, Netflix works.
Have you configured the deny list in magisk?? If not do that then. I'd start fresh, don't connect to anything on first start. Hide everything about those Google apps. Then add your accounts etc etc. This is what worked for me no problem
Click to expand...
Click to collapse
I would like to know, how you are able to pass? I mean It is passed using Universal safetynet fix by Kdragon?
or without fix?
as you mention in your screenshot that you have put all google services in denylist,
I've already done that..
anything else ? you done it? can you show screenshot of your safetynet pass??
shhahidxda said:
I would like to know, how you are able to pass? I mean It is passed using Universal safetynet fix by Kdragon?
or without fix?
as you mention in your screenshot that you have put all google services in denylist,
I've already done that..
anything else ? you done it? can you show screenshot of your safetynet pass??
Click to expand...
Click to collapse
I'm using the latest safetynet fix v2.2.1 Kdragon
thatsupnow said:
I'm using the latest safetynet fix v2.2.1 Kdragon
Click to expand...
Click to collapse
Yes, you are able to pass both .. but i am having issue with OnePlus Nord A12..
On A11 i was able to pass without Universal fix..
but as I applied OTA of A12...
I lose safetynet pass.
let me know do you have any workaround?
I've applied Universal fix by Kdragon.. but before flashing Universal fix of Zygisk I was able to pass Basic Integrity but as soon as I flash Kdragon Universal fix of Zygisk both CTS profile & Basic Integrity gets failed... !!!!
I am still looking for solution to fix this issue..!! if you have any work around.. let me know.. I will do my best.. may be i need to modify device fingerprints with Security patch.? what you say?
shhahidxda said:
Yes, you are able to pass both .. but i am having issue with OnePlus Nord A12..
On A11 i was able to pass without Universal
I've applied Universal fix by Kdragon.. but before flashing Universal fix of Zygisk I was able to pass Basic Integrity but as soon as I flash Kdragon Universal fix of Zygisk both CTS profile & Basic Integrity gets failed... !!!!
Click to expand...
Click to collapse
shhahidxda said:
Yes, you are able to pass both .. but i am having issue with OnePlus Nord A12..
On A11 i was able to pass without Universal fix..
but as I applied OTA of A12...
I lose safetynet pass.
let me know do you have any workaround?
I've applied Universal fix by Kdragon.. but before flashing Universal fix of Zygisk I was able to pass Basic Integrity but as soon as I flash Kdragon Universal fix of Zygisk both CTS profile & Basic Integrity gets failed... !!!!
I am still looking for solution to fix this issue..!! if you have any work around.. let me know.. I will do my best.. may be i need to modify device fingerprints with Security patch.? what you say?
Click to expand...
Click to collapse
You do realise that your posting on the pixel 5 forum right?? I'd maybe go checkout what they are doing on the OnePlus side of the tracks
thatsupnow said:
You do realise that your posting on the pixel 5 forum right?? I'd maybe go checkout what they are doing on the OnePlus side of the tracks
Click to expand...
Click to collapse
Yes, I knew i am posting in Pixel 5 and this topic isnt mention on Oneplus section..
I am looking for a solution of this issue.. but nobody has mention it till now.
Android 12.1 + Magisk 25.1 + Zygisk + Google Play services on enforced Denylist > Works charmingly
Note 1: Enforce Denylist for all the Google Play services modules on Magisk.
Note 2: After reboot, clear data of Google Play services and Play Store to make a fresh start.
pseudokawaii said:
Android 12.1 + Magisk 25.1 + Zygisk + Google Play services on enforced Denylist > Works charmingly
Note 1: Enforce Denylist for all the Google Play services modules on Magisk.
Note 2: After reboot, clear data of Google Play services and Play Store to make a fresh start.
Click to expand...
Click to collapse
I have the same running on a Galaxy S10, but every time I put Google Play Services on the enforce Denylist and reboot it no longer shows there. I'm trying to be able to use my banking app, it worked charmingly on magisk 24 but not anymore. Any advice?
El3ssar said:
I have the same running on a Galaxy S10, but every time I put Google Play Services on the enforce Denylist and reboot it no longer shows there. I'm trying to be able to use my banking app, it worked charmingly on magisk 24 but not anymore. Any advice?
Click to expand...
Click to collapse
What do you mean by "it no longer shows there"? Does the Google Play services disappear after putting on denylist? Did you enable the "Enforce Denylist" option? Did you do a retest of SafetyNet after reboot?
El3ssar said:
I have the same running on a Galaxy S10, but every time I put Google Play Services on the enforce Denylist and reboot it no longer shows there. I'm trying to be able to use my banking app, it worked charmingly on magisk 24 but not anymore. Any advice?
Click to expand...
Click to collapse
Yea and it won't stick I've tried that too. You don't need to add Google Play services to the deny list anyway
thatsupnow said:
Yea and it won't stick I've tried that too. You don't need to add Google Play services to the deny list anyway
Click to expand...
Click to collapse
If you're using Universal Safetynet Fix, Play Services is blocked out of the box. I had the same thing happen in one of the newer releases and thought it was an issue. It isn't. Play Services is blocked even though it doesn't show it.
Hi,
I live in Belgium and it's been years that I'm using Cyanogen, then now Lineage. Recently, I made a bargain and bought 2 Google Pixel 4a, one for me and one for my girlfriend.
I installed Lineage on both of them, and I have to say that it's the best Android experience I had so far. We both love our device. It's small, powerful enough, camera pictures are amazing.
However, we are unable to get any banking apps working. We would like to use 2 applications:
1. Payconiq: https://play.google.com/store/apps/details?id=mobi.inthepocket.bcmc.bancontact&hl=en&gl=US
2. Keytrade: https://play.google.com/store/apps/details?id=be.keytradebank.phone&hl=en&gl=US
I succeeded to get Payconiq working on my phone, using Magisk 23 and Magisk hide. So far so good.
Since this morning, Magisk has been updated to 24.1, Magisk hide is gone and I have to use Magisk Zygisk... And Payconiq doesn't work anymore.
Regarding the second app "Keytrade", it never worked, with any version of Magisk. I don't know what they did in their app, but it seems that they were able to find a way to detect if a phone has a custom rom pretty nicely.
Maybe this is something that the author of Magisk should be aware of? Maybe I'm doing something wrong?
Do you have any piece of advice for me? I don't want to be forced to re-install the official rom, I still want to use Lineage and have those apps working.
Thanks!
Edit 1: After installing Universal Safetynet fix (https://github.com/kdrag0n/safetynet-fix), payconiq works, but not Keytrade.
Easiest way is to use a good browser like Brave to login to the bank's website bypassing the app.
I consider banking apps to be trash apps and never load them. The more needless apps you load, the greater the security risk.
Apps I sometimes use but don't like their behavior I package block when not in use and/or firewall block.
Rather than fight it, bypass it...
blackhawk said:
I consider banking apps to be trash apps and never load them.
Click to expand...
Click to collapse
Not helpful, because thanks to EU rules many banks simply and mandatorily require their app as the second authentication factor - especially when you don't want to use their "real" banking app and use the oldfashioned web interface instead.
Ramihyn said:
Not helpful, because thanks to EU rules many banks simply and mandatorily require their app as the second authentication factor - especially when you don't want to use their "real" banking app and use the oldfashioned web interface instead.
Click to expand...
Click to collapse
That sucks... so much for easy fixes
The Transporter said:
Hi,
I live in Belgium and it's been years that I'm using Cyanogen, then now Lineage. Recently, I made a bargain and bought 2 Google Pixel 4a, one for me and one for my girlfriend.
I installed Lineage on both of them, and I have to say that it's the best Android experience I had so far. We both love our device. It's small, powerful enough, camera pictures are amazing.
However, we are unable to get any banking apps working. We would like to use 2 applications:
1. Payconiq: https://play.google.com/store/apps/details?id=mobi.inthepocket.bcmc.bancontact&hl=en&gl=US
2. Keytrade: https://play.google.com/store/apps/details?id=be.keytradebank.phone&hl=en&gl=US
I succeeded to get Payconiq working on my phone, using Magisk 23 and Magisk hide. So far so good.
Since this morning, Magisk has been updated to 24.1, Magisk hide is gone and I have to use Magisk Zygisk... And Payconiq doesn't work anymore.
Regarding the second app "Keytrade", it never worked, with any version of Magisk. I don't know what they did in their app, but it seems that they were able to find a way to detect if a phone has a custom rom pretty nicely.
Maybe this is something that the author of Magisk should be aware of? Maybe I'm doing something wrong?
Do you have any piece of advice for me? I don't want to be forced to re-install the official rom, I still want to use Lineage and have those apps working.
Thanks!
Click to expand...
Click to collapse
How to pass SafetyNet on Android after rooting or installing a custom ROM
It is possible to pass SafetyNet, even after extensive modding like rooting or installing a custom ROM. Check out how to do that here!
www.xda-developers.com
Austinredstoner said:
How to pass SafetyNet on Android after rooting or installing a custom ROM
It is possible to pass SafetyNet, even after extensive modding like rooting or installing a custom ROM. Check out how to do that here!
www.xda-developers.com
Click to expand...
Click to collapse
Safetyfix passes on the phone... I don't know how the Keytrade app is doing to detect root on the phone.
blackhawk said:
That sucks... so much for easy fixes
Click to expand...
Click to collapse
So true Unfortunately, that seems the way to go in Europe considering banking. If you want it online instead of running to the bank clerk all the time, you're stuck with at least some authentication app. Things get only worse when there's no classical webinterface at all and you're bound to use a complete banking app instead (there are some neobanks doing so already).
The Transporter said:
I don't know how the Keytrade app is doing to detect root on the phone.
Click to expand...
Click to collapse
They simply recognize Magisk app in some way. I've read in some other threads here that a probable solution is to use the app called "Ice Box" to hide the Magisk app by freezing it. Might be worth a try for you.
Another way if you have zygisk enabled. Go to config denylist select play store play services gms you need to hit menu system apps first. And you apps you wish to hide. Then search magisk alpha telegram channel. Download shamiko module. Reboot your phone with enforce denylist selected. After reboot turn the enforce denylist toggle off and flash the shamiko module and reboot. If your app still does not work and you are using lsposed zygisk. You can download hide my applist Xposed module and further hide your app.
Pm me if you want to links to all as they are not supposed to be posted on xda
Have you managed to fix this?
I'm in the same boat.
My bank app 'keytrade bank' keeps detecting that I've rooted my device. This is what I tried
- I installed Magisk
- Installed module Shamiko
- Installed SafetyNet Fix v2.2.1
- Enabled Zygisk
- Configured DenyList
- Hide Magisk app
Awaces said:
Have you managed to fix this?
I'm in the same boat.
My bank app 'keytrade bank' keeps detecting that I've rooted my device. This is what I tried
- I installed Magisk
- Installed module Shamiko
- Installed SafetyNet Fix v2.2.1
- Enabled Zygisk
- Configured DenyList
- Hide Magisk app
Click to expand...
Click to collapse
You have to disable Enforce DenyList in Magisk.
Hi everyone! I have a rooted Pixel 7, with Magisk working perfectly. The only issue i have is with Google Wallet, even SafetyNetFix and Zygisk hide list didn't work. Can anyone with a rooted A13 device pay contactless?
Yes, it works perfectly with GPay/GWallet.
You shouldn't need to do anything else after enabling Zygisk, installing SafetyNetFix, then test if it passes the tests.
Which it should. If it doesn't, use the 2.3.1_MOD2-fix, not 2.4.0.
Had issues with 2.4.0 being inconsistent.
Download 'YASNAC' from the store, and run the test.
Does everything work?
If no, install 2.3.1_MOD2.
If yes, make sure you kill playstore and then wipe storage and buffer.
Do the same for gpay/wallet.
Reboot, and it should work.
Nothing should be added to the Zygisk hide-list.
Hi,
I also had the same problem.
Then I deleted the latest safetynetfix and used the version: v2.3.1
It works fine with this.
dmbardal said:
Yes, it works perfectly with GPay/GWallet.
You shouldn't need to do anything else after enabling Zygisk, installing SafetyNetFix, then test if it passes the tests.
Which it should. If it doesn't, use the 2.3.1_MOD2-fix, not 2.4.0.
Had issues with 2.4.0 being inconsistent.
Download 'YASNAC' from the store, and run the test.
Does everything work?
If no, install 2.3.1_MOD2.
If yes, make sure you kill playstore and then wipe storage and buffer.
Do the same for gpay/wallet.
Reboot, and it should work.
Nothing should be added to the Zygisk hide list.
Click to expand...
Click to collapse
Google Wallet still no worky after installing v2.3.1. Where can i find 2.3.1_MOD2?
LeoPeink said:
It doesn
Google Wallet still no worky after installing v2.3.1. Where can i find 2.3.1_MOD2?
Click to expand...
Click to collapse
https://forum.xda-developers.com/attachments/safetynet-fix-v2-3-1-mod_2-1-zip.5795137/
Link to comment by Displax:
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Installed 2.3.1_mod2.
YASNAC gives me "pass" on Basic Integrity but "Fail" on CTS profile match.
Google Wallet still gives me the "your device does not meet security requirements to pay contactless".
Any further advice?
EDIT: Hide Props Configuration Module is configured to spoof the device as a Pixel 6.
EDIT 2: I will install the Feburary update on my rooted phone, I'll retry when it is up to date so i dont have to mess with fingerprints. Thank you who helped
seanho12345 said:
Did you reboot the phone after clearing it? I've been wiping it a few time but it still not seemed to work.
Click to expand...
Click to collapse
dmbardal said:
https://forum.xda-developers.com/attachments/safetynet-fix-v2-3-1-mod_2-1-zip.5795137/
Link to comment by Displax:
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Click to expand...
Click to collapse
LeoPeink said:
Installed 2.3.1_mod2.
YASNAC gives me "pass" on Basic Integrity but "Fail" on CTS profile match.
Google Wallet still gives me the "your device does not meet security requirements to pay contactless".
Any further advice?
EDIT: Hide Props Configuration Module is configured to spoof the device as a Pixel 6.
EDIT 2: I will install the Feburary update on my rooted phone, I'll retry when it is up to date so i dont have to mess with fingerprints. Thank you who helped
Click to expand...
Click to collapse
not work with me
salamdiab said:
not work with me
Click to expand...
Click to collapse
Dont use props-modules.
Can you post your setup?
Like I've posted mine here
dmbardal said:
Dont use props-modules.
Can you post your setup?
Like I've posted mine here
Click to expand...
Click to collapse
Here's my current Magisk hidelist and module setup. I'm using Shamiko for hiding apps from root
I've had gpay working this entire time used it yesterday around 6PM EST. This morning went to the gas station and got the error the device doesn't meet the software requirements.
Just saw the update for Shimako and Safety net fix. Just ran it and cleared Gpay and Google Play. All looks good just need to test it out now.
canibuz said:
I've had gpay working this entire time used it yesterday around 6PM EST. This morning went to the gas station and got the error the device doesn't meet the software requirements.
Just saw the update for Shimako and Safety net fix. Just ran it and cleared Gpay and Google Play. All looks good just need to test it out now.
Click to expand...
Click to collapse
I'll try again later with Shimako.
To test Google Wallet, you can remove your credit card and add it back: if it does not give you the "unable to pay contactless on this device" you should be clear.
LeoPeink said:
I'll try again later with Shimako.
To test Google Wallet, you can remove your credit card and add it back: if it does not give you the "unable to pay contactless on this device" you should be clear.
Click to expand...
Click to collapse
Just tested it out and it failed.
Can confirm that the new 3.0 MOD from Displax works flawlessly. I just installed it and everything is working.
https://github.com/Displax/safetynet-fix/releases/download/v2.3.1-MOD_3.0/safetynet-fix-v2.3.1-MOD_3.0.zip
seanho12345 said:
Can confirm that the new 3.0 MOD from Displax works flawlessly. I just installed it and everything is working.
https://github.com/Displax/safetynet-fix/releases/download/v2.3.1-MOD_3.0/safetynet-fix-v2.3.1-MOD_3.0.zip
Click to expand...
Click to collapse
Ok it passes tests and lets me add a card to Google Wallet without warnings. I'll try to pay ASAP
If anyone else sees this thread, keep up to date here: https://github.com/Displax/safetynet-fix/releases
The latest version is v2.4.0-MOD_1.2 and works across all devices (not just Google Pixel) for passing safetynet / google pay etc...