It appears July security patch has different API and current Hide/Deny List/USNF/Shamiko becomes invalid, and Wallet/G Pay will detect root even you hide it and passed Safety net
Stay on C.21 until the new solution comes out
mingkee said:
It appears July security patch has different API and current Hide/Deny List/USNF/Shamiko becomes invalid, and Wallet/G Pay will detect root even you hide it and passed Safety net
Stay on C.21 until the new solution comes out
Click to expand...
Click to collapse
This is an issue even on OOS11 I'm afraid, Google Wallet uses the Play Integrity API to detect root now. Passing Play Integrity's attestation without rom side commits is harder that safetynet, but i've managed to do it on OOS11 using the MagiskHide Props Config module, i spoofed an OnePlus 5T on Android 9 and was able to set up contactless on Google Wallet as before
mingkee said:
It appears July security patch has different API and current Hide/Deny List/USNF/Shamiko becomes invalid, and Wallet/G Pay will detect root even you hide it and passed Safety net
Stay on C.21 until the new solution comes out
Click to expand...
Click to collapse
I also had problems with Play Integrity after updating to C.33. But then I installed Displax's version of USNF and I'm now able to use Google Wallet/Pay again.
See https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517
BillGoss said:
I also had problems with Play Integrity after updating to C.33. But then I installed Displax's version of USNF and I'm now able to use Google Wallet/Pay again.
See https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517
Click to expand...
Click to collapse
I added on N10 (R with July patch)
nope
An update
There's an app you can check Play Integrity
Yes, I have it installed as well as USNF 2.3.1 mod installed
8T: first two passed
Thanks for the warning. If i didn't read this i would update to latest version. I need GPay.
BillGoss said:
I also had problems with Play Integrity after updating to C.33. But then I installed Displax's version of USNF and I'm now able to use Google Wallet/Pay again.
See https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517
Click to expand...
Click to collapse
This works, I got 3 cards setup out of maybe 5 I needed - the ones that wouldn't load, I deleted the bank app and tried a few times and they got approved eventually. This is so much easier than anyone else's solutions. Just Magisk, Zygisk deny list, this app, it works
Related
Hi everyone,
I'm wondering whether anyone has successfully used Android Pay on a Meizu Pro 5.
Some backstory of my problem:
In preparation for Android Pay releasing soon™ in the UK, I installed the apk to see how it was set up. When trying to add a card I got an error saying "Android Pay can't be used. Google is unable to verify that your device or the software running on it is Android compatible". After researching I found that normally this error is because the phone is rooted, but I'm not (although I have been in the past). I've tried flashing different firmware's and I still get the error.
Part of the Android Pay checks is the Google Safety Net API so I downloaded SafetyNet Helper Sample from Google Play and sure enough, it fails. It fails saying "CTS profile match: false". Is something wrong with my device or is it a Meizu problem?
Cheers
tl;dr
Android Pay not working. SafetyNet API saying "CTS profile match: false". Is it working for others?
Its not working on my Meizu Pro 5 either. I am on 5.6.5.17 beta and using it in UK. The SafetyNetAPIHelper is giving the same error as you mention. Were you able to find solution ? Halifax mobile is also not working.
cheers!
Mullen1618 said:
Hi everyone,
I'm wondering whether anyone has successfully used Android Pay on a Meizu Pro 5.
Some backstory of my problem:
In preparation for Android Pay releasing soon™ in the UK, I installed the apk to see how it was set up. When trying to add a card I got an error saying "Android Pay can't be used. Google is unable to verify that your device or the software running on it is Android compatible". After researching I found that normally this error is because the phone is rooted, but I'm not (although I have been in the past). I've tried flashing different firmware's and I still get the error.
Part of the Android Pay checks is the Google Safety Net API so I downloaded SafetyNet Helper Sample from Google Play and sure enough, it fails. It fails saying "CTS profile match: false". Is something wrong with my device or is it a Meizu problem?
Cheers
tl;dr
Android Pay not working. SafetyNet API saying "CTS profile match: false". Is it working for others?
Click to expand...
Click to collapse
dont tell me that android pay is not working
i ordered this phone because it had NFC chip in it
following this thread
---------- Post added at 01:38 AM ---------- Previous post was at 01:01 AM ----------
[email protected] said:
Its not working on my Meizu Pro 5 either. I am on 5.6.5.17 beta and using it in UK. The SafetyNetAPIHelper is giving the same error as you mention. Were you able to find solution ? Halifax mobile is also not working.
cheers!
Click to expand...
Click to collapse
i have been searching for solution and looks like there is xposed module to bypass this security check
can you test it out , i dont have the phone with me yet
http://repo.xposed.info/module/com.pyler.nodevicecheck
I installed the NoDeviceCheck apk from the link and no effect. SafetyNet Helper still says the CTS Profile Match : False and same error in Android Pay.
[email protected] said:
I installed the NoDeviceCheck apk from the link and no effect. SafetyNet Helper still says the CTS Profile Match : False and same error in Android Pay.
Click to expand...
Click to collapse
The following break Android Pay;
-Xposed Framework
-Non-stock DPI
-Busybox installed to /system/... (/su/bin works!)
-Certain custom ROMs
-Classic root method (use systemless instead)
-/su/xbin_bind using systemless root (delete this file in this path and reboot)
-Any modifications to /system
i think the root and xposed is the main thing that doesnt pass the check in android pay
i am not sure if you can unroot from the account
i will try to make it work as soon as i get the device
these 3 threads should be of any help
http://forum.xda-developers.com/nex...pay-rooted-t3260062/post64367735#post64367735
http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659/page39
http://forum.xda-developers.com/apps/supersu/supersu-safetynet-android-pay-t3298115
You have to know that none of Meizu devices has the certification for Google Services. https://support.google.com/googleplay/answer/1727131?hl=en
So I don't think Android Pay could work.
maxant69 said:
You have to know that none of Meizu devices has the certification for Google Services. https://support.google.com/googleplay/answer/1727131?hl=en
So I don't think Android Pay could work.
Click to expand...
Click to collapse
that can be tricked via the build.prop and faked as another branded device
but then again android pay doesnt want root and modification of the system
mite_jan said:
that can be tricked via the build.prop and faked as another branded device
but then again android pay doesnt want root and modification of the system
Click to expand...
Click to collapse
I don't think it is so simple.
Not sure how many of you play Pokemon Go, but recent security patches have blocked to ability to use GPS mock location apps.
The OP5 ships with 7.1.1 and May security update which means that mock location apps are no longer supported.
I read that you can root and move the GPS app to the system, meaning that you dont need to rely on Mock location.
So, I have rooted my OP5, with Magisk (SafetyNet passed)....so what to do next?
Any help would be greatly appreciated.
Thanks.
shaazzaarr said:
....so what to do next?
Click to expand...
Click to collapse
You move the GPS app to system. Duh!
Spoiler
You can use Link2SD to move the app to system
Most guides tell you to install a gps joystick of choice. After this install "Disable Service" app from the playstore. Run the app and disable fused locations service to terminate rubberbanding problems. The problem with oxygenos is that it gets stuck in bootloop as soon as you turn off the fused locations service. I didnt find a solution to this yet, so I'm hoping someone here can
shaazzaarr said:
Not sure how many of you play Pokemon Go, but recent security patches have blocked to ability to use GPS mock location apps.
The OP5 ships with 7.1.1 and May security update which means that mock location apps are no longer supported.
I read that you can root and move the GPS app to the system, meaning that you dont need to rely on Mock location.
So, I have rooted my OP5, with Magisk (SafetyNet passed)....so what to do next?
Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
Very simple solution. You'll need to be rooted though. I just magisk v13.3. As it bypasses safetynet.
1. Install NewGPS!Joystick from play store
2. Install lucky patcher (easy to find)
3. Open lucky patcher
4. Find newgps!joystick in the list, then convert it as a system app.
5. Open newgps!joystick, set where you want to start from. That's it.
Just open pogo and enjoy
Ken-ShinT said:
Most guides tell you to install a gps joystick of choice. After this install "Disable Service" app from the playstore. Run the app and disable fused locations service to terminate rubberbanding problems. The problem with oxygenos is that it gets stuck in bootloop as soon as you turn off the fused locations service. I didnt find a solution to this yet, so I'm hoping someone here can
Click to expand...
Click to collapse
I have it turned off with the app you named "Disable Service". I am using Android Auto so sometimes i have to re-enable it to use it as my car navigation. It always works perfectly fine without any boot issues.
Running Oxygen OS 4.5.1 and Android 7.1.1
I do love the Poco F2 Pro as great value for money, just disappointed there's no custom ROM support. I thought I'd see if I can get MicroG to work. It's not a super simple process, as requires first debloating and removing the Google Play Services before doing so. I had the best success actually using the Systemless Debloater using the terminal and Magisk. It sounds complicated, but is fairly simple. I would gradually remove a few apps at a time and do a TWRP backup and restore if it failed to boot up. I also disabled a majority of the Miui apps and services including Mi Account. When attempting to remove FindDevice the device failed to boot up, so have left it for now.
Debloater can be installed directly from Magisk by going to downloads and searching. Then check this https://forum.xda-developers.com/apps/magisk/module-terminal-debloater-debloat-t3584163
There's other articles on debloating also https://medium.com/@mail.anonymous....devices-via-android-debug-bridge-2e5bcd94dfa0
As obviously the ROM doesn't support signature spoofing natively for MicroG to wok it needs to be patched. I tried the NanoDroid MicroG Patcher, but it failed.
There is a way to do it with an Xposed module. But I was able to do it by using this tool. Seriously one of the best tools I've yet seen, so deserves all the credit.
Using the Smali Patcher 6.9. Download and run it on your computer. It creates a Magisk ZIP that can be flashed by TWRP or Magisk and enables signature spoofing and a range of other hacks.
https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053
After signature spoofing is enabled. You can flash MicroG. There's multiple ways to do this. I've been able to get all the boxes checked for signature spoofing support with MicroG, but just a few issues still getting the Play Store to sign in. I actually used this package by FriendlyNeighbourhodShane https://github.com/friendlyneighborhoodshane/minmicrog_releases/releases
But also NanoDroid MicroG installer would be fine, which can be downloaded by https://github.com/Nanolx/NanoDroid
This is still a work in progress. To just get Signature Spoofing and MicroG working isn't too hard, it's often a bit trickier to get the Play Store to function correctly, but only required for paid applications, as the Auora Store and F-Droid work well especially with the privileges extension, that allows them to auto update apps. This is included with the friendlyneighborhoodshane version of MicroG standard installer.
I'm curious why there is not even an unofficial Lineage. I mean, source code is out, isn't it?
dustojnikhummer said:
I'm curious why there is not even an unofficial Lineage. I mean, source code is out, isn't it?
Click to expand...
Click to collapse
Maybe devs need more time to port roms to our phone ¯\_(ツ)\_/¯
Ok following up this thread. It seems that most Xiaomi bloatware can be removed. This article seems to go over what can and can't be removed. https://selivan.github.io/2020/02/25/removing-bloatware-from-xiaomi-miui-android.html
Go get the Google Play store working in the end. Was able to by running the NanoDroid_MicroG.zip in TWRP. Modify the nanodroid-setup file and change it so PlayStore=10 to install PlayStore.
Boot up phone and go to MicroG settings. Enable the UnifiedNlp back ends. I enabled Google Device Registration. Then sign into your Google account from MicroG. Don't run the Play Store, but clear data.
Restart phone then try running the Play Store and see if it opens correctly.
I'm somewhat ok with this phone. I think the phone is great, but just wish I could get HavocOS or LineageOS for it. I'm going to test it for a while now and see how it goes.
Hello,
on Android 11 (Xiaomi.eu rom - tried with stable and beta), after installing the Smali Patcher module, i've got a bootloop. Have you tried to enable signature spoofing on Android 11 ?
Would love to have a full guide now when Lineage is out.
Lowxorx said:
Hello,
on Android 11 (Xiaomi.eu rom - tried with stable and beta), after installing the Smali Patcher module, i've got a bootloop. Have you tried to enable signature spoofing on Android 11 ?
Click to expand...
Click to collapse
Haven't tried on any Android 11 ROMs as yet. CrDroid and a few custom ROMs have signature spoofing already. I'll do a bit more testing and might update this thread if I can get MicroG all working on other ROMs.
Hello, it's good to know that this is possible however a full guide would be much more useful. Thank you!
Hi, magisk was passing saftey net. I installed magisk 21.2 with twrp and it says its installed. Installed Magisk hide and hid all Google apps and I think it changed the devices fingerprint in the install log. But no luck. Any ideas?
Miui 12.0.5 global
Vanmanman said:
Hi, magisk was passing saftey net. I installed magisk 21.2 with twrp and it says its installed. Installed Magisk hide and hid all Google apps and I think it changed the devices fingerprint in the install log. But no luck. Any ideas?
Miui 12.0.5 global
Click to expand...
Click to collapse
You just need to enable Magisk hide option in Magisk Manager (nothing specially to install for), and the required activity for GooglebPlay Services to hide will be already checked-in. You don't need to check in manually the other Google apps (and better you don't)
All that does not change device fingerprint or any prop.
If you really want to change props (incl. device fingerprint), use Magisk Hide Props Config (MHPC), find its XDA thread with the Guide in OP post (and more detailed guide on its Github)
And I don't see any problem ("no luck"?!) on your screenshot.
If SafetyNet is passing, better don't change any props/fingerprints - specially, before playing with, carefully study Magisk Wiki and MHPC Guide from Github
zgfg said:
You just need to enable Magisk hide option in Magisk Manager (nothing specially to install for), and the required activity for GooglebPlay Services to hide will be already checked-in. You don't need to check in manually the other Google apps (and better you don't)
All that does not change device fingerprint or any prop.
If you really want to change props (incl. device fingerprint), use Magisk Hide Props Config (MHPC), find its XDA thread with the Guide in OP post (and more detailed guide on its Github)
And I don't see any problem ("no luck"?!) on your screenshot.
If SafetyNet is passing, better don't change any props/fingerprints - specially, before playing with, carefully study Magisk Wiki and MHPC Guide from Github
Click to expand...
Click to collapse
Hi, Thanks for the reply.
I reinstalled to go back to default magisk settings. I have Magiskhide enabled. But for instance. The macdonalds app when redeeming an offer will say "security check failed". Also playstore cant see netflix and some other apps anymore with new version of magisk. I used magisk to pass safteynet to do that before, or it was doing that before but its not passing safteynet with 21.2 magisk now
I tried using MagiskHide Props Config to change the devices finger print but attestation keeps failing
Vanmanman said:
Hi, Thanks for the reply.
I reinstalled to go back to default magisk settings. I have Magiskhide enabled. But for instance. The macdonalds app when redeeming an offer will say "security check failed". Also playstore cant see netflix and some other apps anymore with new version of magisk. I used magisk to pass safteynet to do that before, or it was doing that before but its not passing safteynet with 21.2 magisk now
Click to expand...
Click to collapse
On Magisk Github find Wiki, there is the whole chapter devoted to the problems how certain apps detect root and tips how you can try to prevent
But it's a constant game of mice and cat - you may fix it for now (for some of those apps), but a newer version of that app may explore a new methods to again detect the root
As the minimum, enlist the given apps to the Magisk hide list.
Also, take Hide Magisk Manager and rename it - it may help (some apps look if Magisk Manager is installed).
Remove TWRP folder (some look for that) - read the Wiki, try all the tips suggested there
Btw, are you passing SafetyNet or no. First you must make sure to pass (my comments above are about that even if you pass SsfetyNet, that there are still apps that declare that phone is rooted, by taking other checks and methodes).
So, Msgisk Hide must be enabled.
If its still not passing SafetyNet, take a screenshot - does it pass Basic Integrity or not, does it show taking Basic or Hardware eval type for CTS
Some Magisk modules may also cause SafetyNet to fail. Disable all modules, reboot and try again
These are all important details, not just SN is failing or some app detects root...
thanks will do. Gave them a go and now trying changing my devices finger print. Just cant get attestation/basicintegrity or cts profile to pass. Only have magisk hide propconfig module @zgfg
See again my previous post - I've edited/added some details
I enabled magisk hide. Changed magisk name. Changed every fingerprint and simulation of device I could but still get this
I checked magisk hide with a root checker and its working with that. So somethings working. Cant find the magisk github wiki but finding lots of other stuff to try to get saftey net passing. Just no luck yet
trying to install HiddenCore Module from Xposed but the manager is saying xposed framework is not installed even though I've have Riru core and tried both frameworks. All this stuff worked before on my phone before the new magisk update or googles updated something maybe
had to install framework via TWRP. Got HiddenCore Module going and safety net check pass!!! However still cant redeem offers with macas because of security check fail. Wonder what there looking for now. Removed everything before and just hid with magisk but they must have updated. Also cant see my netflix in google play like i used to
Hi everyone,
I just recently had my Oneplus 8 pro coming back from warranty (fingerprint was not working anymore after display replace, even after I used msm) and then I restarted rooting it and customising it.
I took the device fingerprint (via getprop ro.build.fingerprint) before I rooted it and saw:
OnePlus/OnePlus8Pro_EEA/OnePlus8Pro:12/RKQ1.211119.001/Q.GDPR.202207300316:user/release-keys
This one never changed throughout rooting / magisk.
In Magisk I have:
- Zygisk
- Shamiko
- Universal Safetynet Fix
I did not install Props Config as my fingerprint is the same as it came from Oneplus / factory defaults, no change there.
I denied root awareness to all the things under Google Play Services and Play Store.
Yasnac shows I pass both: Basic Integrity and CTS Profile.
My bootloader of course is unlocked.
The Google Play Services show they are the latest version.
They show my device is certified.
Despite this:
- Netflix app in playstore says "This app isn't compatible with your device anymore. Contact the developers for more info."
Any clue what else I might be missing or what check they do ?
I've never used Netflix, but I'm guessing you'll have to Deny it "root awareness" as well? Or just grab the app off apkmirror