Related
I'm on latest Firmware Rooted Using Magisk. Safety net failure even after Trying every fix modules hide options and what not. Kindly help.
It appears to be an issue with the newest release of the Magisk (the patch, not the app).
I can confirm mine was passing until installing an update to Magisk. After booting, it failed with or without the fix.
Found a fix on a telegram page, give full credits to modulesrepo and TeamFiles for finding this method.
-- Open Magisk and Flash Riru Core, But do not reboot.
-- Go back and flash Lsposed in magisk & reboot your device.
-- Now install XPrivacyLua apk
-- Open Lsposed and go to modules section and choose XPrivacyLua from there.
-- Select system framework, Settings storage and Google Play services there.(Uncheck the system apps from hide section settings for Play services to show up)
-- Reboot your device
-- Open XPrivacyLua and search google play services, click drop down menu in left of play services and tick 'use tracking' as shown in the screenshot.
-- Tick 'use tracking' on banking apps too and clear data of them after ticking
-- Now clear play services and play store data through your phone's settings.
-- Hide magisk and change name of magisk
-- Your Safetynet Should Pass Now!
Came across that a few days ago, but it seemed excessive.
[2023 FIX] Fix Magisk CTS Profile False Error - Bypass Safetynet
Magisk CTS Profile False Error is now popping up on almost everyone's device since Google made some changes in March. To Bypass Safetynet...
droidholic.com
Madbullben said:
Found a fix on a telegram page, give full credits to modulesrepo and TeamFiles for finding this method.
-- Open Magisk and Flash Riru Core, But do not reboot.
-- Go back and flash Lsposed in magisk & reboot your device.
-- Now install XPrivacyLua apk
-- Open Lsposed and go to modules section and choose XPrivacyLua from there.
-- Select system framework, Settings storage and Google Play services there.(Uncheck the system apps from hide section settings for Play services to show up)
-- Reboot your device
-- Open XPrivacyLua and search google play services, click drop down menu in left of play services and tick 'use tracking' as shown in the screenshot.
-- Tick 'use tracking' on banking apps too and clear data of them after ticking
-- Now clear play services and play store data through your phone's settings.
-- Hide magisk and change name of magisk
-- Your Safetynet Should Pass Now!
Click to expand...
Click to collapse
Thanks a lot, But thats a lot of modules for a phone without TWRP right now ....
I kept getting a failure error as well but now it's all good follow the instructions and links from this video. You don't have to follow the entire instructions you can skip to the part for the magisk safety net module and info
Now clear play services and play store data through your phone's settings ? how to do it ?
Deleted, posted in wrong thread, oops
Madbullben said:
Thanks! Really appreciated that you did this! The new chat bubbles are a good idea in theory but they are so bad and so much worse than the old chat heads and it was driving me crazy with the new chat bubble so this is amazing!
Click to expand...
Click to collapse
Did you make a wrong turn?
Did the fix. Safety net passes, Hulu and Disney+ work, but not Netflix
edit: got it working. restarting the first time didn't fix it, but the 2nd time did for some reason.
TiklMiPickles said:
Did the fix. Safety net passes, Hulu and Disney+ work, but not Netflix
edit: got it working. restarting the first time didn't fix it, but the 2nd time did for some reason.
Click to expand...
Click to collapse
Which one worked ?
Post #3 - The list or the video in Post #6 ?
JazonX said:
Which one worked ?
Post #3 - The list or the video in Post #6 ?
Click to expand...
Click to collapse
The video redirects to the latest canary build, so that is going to be broken.
twistedumbrella said:
The video redirects to the latest canary build, so that is going to be broken.
Click to expand...
Click to collapse
Loud and clear.
If no other option comes up, I will go with the guide with Riru.
It's a huge risk tbh, because ROG 5 doesn't have TWRP yet to revert if anything goes bad.
JazonX said:
Loud and clear.
If no other option comes up, I will go with the guide with Riru.
It's a huge risk tbh, because ROG 5 doesn't have TWRP yet to revert if anything goes bad.
Click to expand...
Click to collapse
Yeah. I'm waiting on the module to work. It's been converted to Riru, but both beta and canary builds of Magisk still fail. I haven't tested the stable one.
The one in the video works fine for me tho. Didn't work at first but for whatever magic reasons everything was fine after some restarts
twistedumbrella said:
Yeah. I'm waiting on the module to work. It's been converted to Riru, but both beta and canary builds of Magisk still fail. I haven't tested the stable one.
Click to expand...
Click to collapse
Just checked his github, sadly the latest version 2.1.0 seems to fix the issue - But it's a paid mod now.
Github has only 2.0.0 where the CTS still fails.
JazonX said:
Just checked his github, sadly the latest version 2.1.0 seems to fix the issue - But it's a paid mod now.
Github has only 2.0.0 where the CTS still fails.
Click to expand...
Click to collapse
It's not a paid mod. Only early access is paid - just wait until the developer releases it via github
twistedumbrella said:
Did you make a wrong turn?
Click to expand...
Click to collapse
Yep oops sorry about that
twistedumbrella said:
Yeah. I'm waiting on the module to work. It's been converted to Riru, but both beta and canary builds of Magisk still fail. I haven't tested the stable one.
Click to expand...
Click to collapse
As we don't have twrp, if something does fail can't we just use fastboot and flash the device again?
Madbullben said:
As we don't have twrp, if something does fail can't we just use fastboot and flash the device again?
Click to expand...
Click to collapse
Raw firmware can fix almost anything. Factory reset can fix the rest.
Hello Everyone,
I recently installed LineageOS 18.1 (build: lineage_kebab-userdebug 11). I have retrieved my Android ID using the ADB commands found here: Device Registration and registered my Android ID a few days ago but Google Play Store still shows: "Device is not certified" under Settings --> About --> Play Protect certification. Is there something I'm doing wrong or something else I need to do in order to get my device certified with Google Play Store?
use magisk hide props config I use the pixel 5 fingerprint and add new props
ro.product.model Pixel 5
ro.product.manufacturer Google
option 5 add those 2 after you change fingerprint you will pass and get stadia discounts just can't run edxposed I do but a few changes in that you fail hope that helps
ecompton59 said:
use magisk hide props config I use the pixel 5 fingerprint and add new props
ro.product.model Pixel 5
ro.product.manufacturer Google
option 5 add those 2 after you change fingerprint you will pass and get stadia discounts just can't run edxposed I do but a few changes in that you fail hope that helps
Click to expand...
Click to collapse
Thank you for the info. So you are saying in order to get my device "certified" with Google Play Store I need to root my device, add new props and change my fingerprint (I assume you mean Android ID)? I'm not sure what you mean by: "stadia discounts" or "edxposed". Also, I do not see where I need to root my device in the LineageOS documentation or the Google documentation so I'm still unclear why this must be done. Does Google block LineageOS devices from getting "certified" or something?
long as you used dual sim oos file to unlock your phone it won't unless you do something like that and Google thinks I have pixel 5 see pics I pass
alteredstate82 said:
Thank you for the info. So you are saying in order to get my device "certified" with Google Play Store I need to root my device, add new props and change my fingerprint (I assume you mean Android ID)? I'm not sure what you mean by: "stadia discounts" or "edxposed". Also, I do not see where I need to root my device in the LineageOS documentation or the Google documentation so I'm still unclear why this must be done. Does Google block LineageOS devices from getting "certified" or something?
Click to expand...
Click to collapse
Unlocking a bootloader breaks SafetyNet passes. This results in the play store as not being certified which usually hides specific apps such as Netflix and some other banking apps and will break them. Magisk is needed to help with spoofing your device to let the play store know your device is certified. Some ROMs have built in patches in which SafetyNet passes fine without root. I believe lineage does not do this with their ROM, so you will need magisk.
This is actually a decent article which describes this if you desire to read it - https://www.hexnode.com/blogs/safetynet-android-security/
azoller1 said:
Unlocking a bootloader breaks SafetyNet passes. This results in the play store as not being certified which usually hides specific apps such as Netflix and some other banking apps and will break them. Magisk is needed to help with spoofing your device to let the play store know your device is certified. Some ROMs have built in patches in which SafetyNet passes fine without root. I believe lineage does not do this with their ROM, so you will need magisk.
This is actually a decent article which describes this if you desire to read it - https://www.hexnode.com/blogs/safetynet-android-security/
Click to expand...
Click to collapse
Okay that makes sense. According to the: Patching Images section of the How to Install Magisk App guide I can install Magisk to the boot ramdisk (see screenshot). However, the LineageOS build I installed does not contain a "boot.img" in the zip file. There is however a "payload.bin" file which according to the: XDA Magisk Installation Guide I need to use "payload-dumper-go" to extract the boot.img from the payload.bin? Does that about sum it up or is there something else I'm missing?
alteredstate82 said:
Okay that makes sense. According to the: Patching Images section of the How to Install Magisk App guide I can install Magisk to the boot ramdisk (see screenshot). However, the LineageOS build I installed does not contain a "boot.img" in the zip file. There is however a "payload.bin" file which according to the: XDA Magisk Installation Guide I need to use "payload-dumper-go" to extract the boot.img from the payload.bin? Does that about sum it up or is there something else I'm missing?
Click to expand...
Click to collapse
Yep. You will need to extract the payload.bin file in which you will use the boot.img, then patch it with magisk, then flash the patched boot.img using fastboot. Then, you will need to use magiskhide to hide magisk itself and use the props spoof module to help with passing safetynet.
I want to say thank you for the help! I successfully installed Magisk and passed the SafetyNet checks! Everything seems to be working good. However, it seems my efforts might be wasted as Magisk is dropping support for hiding root access. This is unfortunate as I have a few job critical apps that will not work unless I hide them from root access in Magisk. Hopefully someone else will pick up the torch and continue development. It's a crime these big tech companies work so hard to prevent us from modifying hardware we own!
Hi, I flashed LineageOS 18.1 to my OnlePlus 8T (KB2003). The device is not rooted.
Since that, he device is no longer Play Protect certified and I am not able to install Netflix or use PayPal anymore.
Therefore I installed Magisk and MagiskHidePropsConf-v6.1.2 and followed the instructions above to change the fingerprint and hopefully hide, that the bootloader is unocked. But the device is still not certified (PayStore App > Settings > Info)
What have I done:
- extracted boot.img from LineageOS payload.bin
- boot.img was patched and fastboot flashed to my device (Patching_Images)
- 2 props added: ro.product.model: "Pixel 5", ro.product.manufacturer: "Google"
Did I forgot something?
But in general, why is it needed to change the fingerprint to Pixel 5? Should not work the default fingerprint of my OnePlus 8T as well?
BR Greg
gregattack said:
Hi, I flashed LineageOS 18.1 to my OnlePlus 8T (KB2003). The device is not rooted.
Since that, he device is no longer Play Protect certified and I am not able to install Netflix or use PayPal anymore.
Therefore I installed Magisk and MagiskHidePropsConf-v6.1.2 and followed the instructions above to change the fingerprint and hopefully hide, that the bootloader is unocked. But the device is still not certified (PayStore App > Settings > Info)
What have I done:
- extracted boot.img from LineageOS payload.bin
- boot.img was patched and fastboot flashed to my device (Patching_Images)
- 2 props added: ro.product.model: "Pixel 5", ro.product.manufacturer: "Google"
Did I forgot something?
But in general, why is it needed to change the fingerprint to Pixel 5? Should not work the default fingerprint of my OnePlus 8T as well?
BR Greg
Click to expand...
Click to collapse
All I needed to do to get Play Protect certified was to change my fingerprint to the OP8T KB2003 fingerprint included in MagiskHide Props Config. No other model spoofing needed.
I am still stuck on Widevine L3, however. Still haven't figured that one out, and may be unrelated.
Did you install and use the Universal SafetyNet Fix module?
If I set the kb2003 OP 8T (EU) fingerprint, it seemed not to work. But I will try again.
Do I need to clear some caches eg: play store, after changing the fingerprint or something else?
cpkelley94 said:
All I needed to do to get Play Protect certified was to change my fingerprint to the OP8T KB2003 fingerprint included in MagiskHide Props Config. No other model spoofing needed.
I am still stuck on Widevine L3, however. Still haven't figured that one out, and may be unrelated.
Click to expand...
Click to collapse
finally I installed Universal SafetyNet Fix and switched to the kb2003 fingerprint and reset all other modification like custom props for the pixel phone. Now it's working. No idea why it fails in previous approach
Strange, on my device. Not on lineage though - I pass safetynet without help from any modules. No props or even USF module. Rooted and bootloader unlocked.
Op8t 5g tmobile.
ykjae said:
Strange, on my device. Not on lineage though - I pass safetynet without help from any modules. No props or even USF module. Rooted and bootloader unlocked.
Op8t 5g tmobile.
Click to expand...
Click to collapse
which image are you using?
I read, that some images like https://evolution-x.org/ pass safetynet out of the box but I did'nt test this.
Finally the unlocked bootloader is the problem.
Mod Note
Closed upon OP request. Solution is in post #3.
Hello,
Ok so i have my Lenovo K33a42 with me, i have rooted it using magisk and installed Pixel Experience (right here). After installing the ROM, i saw i cant pass safety net (cts profile), i ignored it because i dont use any banking apps or such. When i tested safety net again today, i see a weird error saying "Can't access Google Play Services". Help me please. Thanks
Would you like to share your solution with us?
Ah sure,
So i couldnt pass CTS profile before Magisk 24 and after upgrading to Magisk 24 i couldnt pass safetynet at all. So i asked in android's discord and one guy asked me to enable Zygisk and install universal safetynet fix. I did it and i saw now i could pass basic integrity but not CTS profile (Note: my device does not use Hardware backed Attestation). Another guy there asked me to install MagiskHide Props Config module (after installing you have to do "su -c props" in a terminal emulator to do the next steps) and asked me to edit my device fingerprint according to my rom. As i am using Pixel Experience Android 9 i changed my fingerprint to Google Pixel 3 Android 9's. Before rebooting he asked me to enable Force Basic Key Attestation and then my phone automatically rebooted and then boom. I passed safetynet and to see if my device is certified or not i had to clear Google Play Services' data, i did it and after about some hours i checked Play Store and my device was certified. I still can't find Netflix on Play Store idk why. If you guys could help me out?
Thanks
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do:
- Update Magisk to 25.2, Update magisk app to 25.2 as well
- Rename Magisk app if you havent already
- [ OPTIONAL ] Add all google apps on deny list (good practice in case google wants to detect root throught their other apps)
- install these modules: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf and https://github.com/kdrag0n/safetynet-fix
- then:
step 1.) Download any terminal (I use termux)
step 2.) type SU
step 3.) type props
step 4.) edit device fingerprint
step 5.) follow the onscreen promt
step 6.) once successfully changed, reboot device
optional (i didnt have to but you can try) reset google play, play services and google wallet appdata.
step 7.) enjoy working google wallet.
- Reboot
NOTE: Remeber to clear google wallet just in case.
ANOTHER NOTE: If your device is not on this list: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/common/prints.sh
then you'll have to manually obtain an old fingerprint for your device, its all on here how to do:
MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
Enjoy.
EDIT: Alternatively try this:
https://github.com/Displax/safetynet-fix/releases/
it wont work for all from what I know but it was successful for some.
I only had to update magisk then add Wallet to the deny list.... Haven't tested an actual payment yet, but it stopped complaining about root when I open it.
I probably already had some of those modules installed from before. Some of the names look familiar.
Tried it at McDonald's... Didn't work. I guess the app stops complaining after a few goes of starting it up... Need to check in the "contactless setup" part of the Wallet app to be sure. Has a warning there if your device is "unsafe".
I'll try the full list of steps above tonight and confirm tomorrow if I can pay with it.
ahhh, it was not only with me... going to install to see if it passes...
None of the above works. If you try to pay contactless it will fail. If you try to add card it will fail also. I think that the new google wallet can detect if bootloader is unlocked. I don't see any workaround on this.
covar said:
None of the above works. If you try to pay contactless it will fail. If you try to add card it will fail also. I think that the new google wallet can detect if bootloader is unlocked. I don't see any workaround on this.
Click to expand...
Click to collapse
Yeah I removed Magisk and I still failed. It seems bootloader related I think.
covar said:
None of the above works. If you try to pay contactless it will fail. If you try to add card it will fail also. I think that the new google wallet can detect if bootloader is unlocked. I don't see any workaround on this.
Click to expand...
Click to collapse
works fine for me, I added something you should try as well in case it didnt work for you.
Danishblunt said:
works fine for me, I added something you should try as well in case it didnt work for you.
Click to expand...
Click to collapse
Still nothing. Have you try to make payment????
covar said:
Still nothing. Have you try to make payment????
Click to expand...
Click to collapse
I made 4 payments after the fix, latest being 12 minutes prior to this reply. it works fine.
I suggest starting from my post 1point by point. If it still doesnt work then you may have an app that somehow triggers the root detection that I don't have on my phone.
You should probably mention that picking correct CTS fingerprint is crucial. Sometimes its one version down for your device, but other times you have to use entirely different (but probably related somehow?) device FP, either because prior version doesn't exist, or Google simply doesn't accept it. The Google Pay thread has a scattered reports of working combos somebody should probably make a nicer list of.
I think some steps are not necessary. Like hiding all Google apps and SQ Lite
Also, momo-hider is depreciated. Use shamiko.
Lastly, I just installed magisk hide props (and configured it) and now it works.
Thanks its work✓ !! Is it permanent? Or someday its gonna pop out because some updates?
Magisk user
Paulo_1307_ said:
I think some steps are not necessary. Like hiding all Google apps and SQ Lite
Also, momo-hider is depreciated. Use shamiko.
Lastly, I just installed magisk hide props (and configured it) and now it works.
Click to expand...
Click to collapse
You are correct. The only thing to do is to configure props. I personally change the fingerprint and now works fine.
Paulo_1307_ said:
I think some steps are not necessary. Like hiding all Google apps and SQ Lite
Also, momo-hider is depreciated. Use shamiko.
Lastly, I just installed magisk hide props (and configured it) and now it works.
Click to expand...
Click to collapse
You're right, just listed old modules i gathered over time just in case without testing if they are needed anymore. Tested if they were needed and indeed, they arent.
Hiding the google apps is a good idea regardless if its needed or not.
Fixed the original post to reflect the changes.
Danishblunt said:
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do:
- Update Magisk to 25.2, Update magisk app to 25.2 as well
- Rename Magisk app if you havent already
- [ OPTIONAL ] Add all google apps on deny list (good practice in case google wants to detect root throught their other apps)
- install these modules: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf and https://github.com/kdrag0n/safetynet-fix
- then:
step 1.) Download any terminal (I use termux)
step 2.) type SU
step 3.) type props
step 4.) edit device fingerprint
step 5.) follow the onscreen promt
step 6.) once successfully changed, reboot device
optional (i didnt have to but you can try) reset google play, play services and google wallet appdata.
step 7.) enjoy working google wallet.
- Reboot
NOTE: Remeber to clear google wallet just in case.
ANOTHER NOTE: If your device is not on this list: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/common/prints.sh
then you'll have to manually obtain an old fingerprint for your device, its all on here how to do:
MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
Enjoy.
Click to expand...
Click to collapse
hi may I ask what does step 5 mean? Thanks!
darkhunter9 said:
hi may I ask what does step 5 mean? Thanks!
Click to expand...
Click to collapse
baisically just means follow instructions on your screen.
Paulo_1307_ said:
I think some steps are not necessary. Like hiding all Google apps and SQ Lite
Also, momo-hider is depreciated. Use shamiko.
Lastly, I just installed magisk hide props (and configured it) and now it works.
Click to expand...
Click to collapse
Can confirm this works
I had both GPay and Wallet installed on my Pixel 5; yesterday I got the "security requirements" notification.
I've now removed both apps. When I tap on the GPay tile in Quick Settings, it says "Hold to reader", but when I tap Show All, it says "Not set up". I'll test it later today.
Does anyone know how to clear cache for embedded GPay?
V0latyle said:
I had both GPay and Wallet installed on my Pixel 5; yesterday I got the "security requirements" notification.
I've now removed both apps. When I tap on the GPay tile in Quick Settings, it says "Hold to reader", but when I tap Show All, it says "Not set up". I'll test it later today.
Does anyone know how to clear cache for embedded GPay?
Click to expand...
Click to collapse
It will show an error when you try to do a transaction if you havent done the above. Minr also showed that it was reafy but when trying to pay it would throw error.
Danishblunt said:
It will show an error when you try to do a transaction if you havent done the above. Minr also showed that it was reafy but when trying to pay it would throw error.
Click to expand...
Click to collapse
I just went to Dollar General and successfully used tap to pay. I do not have either of the discrete apps installed, just embedded GPay.
Danishblunt said:
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do:
- Update Magisk to 25.2, Update magisk app to 25.2 as well
- Rename Magisk app if you havent already
- [ OPTIONAL ] Add all google apps on deny list (good practice in case google wants to detect root throught their other apps)
- install these modules: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf and https://github.com/kdrag0n/safetynet-fix
- then:
step 1.) Download any terminal (I use termux)
step 2.) type SU
step 3.) type props
step 4.) edit device fingerprint
step 5.) follow the onscreen promt
step 6.) once successfully changed, reboot device
optional (i didnt have to but you can try) reset google play, play services and google wallet appdata.
step 7.) enjoy working google wallet.
- Reboot
NOTE: Remeber to clear google wallet just in case.
ANOTHER NOTE: If your device is not on this list: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/common/prints.sh
then you'll have to manually obtain an old fingerprint for your device, its all on here how to do:
MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
Enjoy.
Click to expand...
Click to collapse
Even tho Xiaomi Mi 11 Lite 5g (European version) is not on either list, I got Google Wallet to play nicely (ie work! ) using this guide. In effect the Xiaomi Mi 11 Lite Indonesia Xiaomi:M2101K9AG must have similar coding to Xiaomi M2102K9G. I am now on 13.0.6 SKIEUXM MIUI version. I was worried in the termux app re warnings about ensuring device fingerprint is compatible etc, but when I got the sae warning in adb shell command within minimal adb & fastboot command, I decided to see what happens and it all worked for me. Have carried 2 transactions within Google wallet over yesterday & today with complete success. My device was already certified within Play protect part of Google Play Store.
So I have rooted phone with Magisk 25.2 version, zygisk and deny list set up ; magisk hidden (Hide) then froze Magisk Hide within SD Maid so my fully rooted phone runs Ad Away, no ads & all my banking apps eg Santander & Halifax work fine, so root is hidden from them. Given up trying to get Chase banking app tho
I haven't been able to get wallet to not detect root, so I can't add a card. I have magisk installed with universal safetynet fix. I've also set wallet, and play store to deny.
Anything else I'm missing?
I also get CTS profile match failed.
omf05 said:
I haven't been able to get wallet to not detect root, so I can't add a card. I have magisk installed with universal safetynet fix. I've also set wallet, and play store to deny.
Anything else I'm missing?
I also get CTS profile match failed.
Click to expand...
Click to collapse
Search in this forum. There's a magisk safety net patch that got mine working.
Bxperiaz3 said:
Search in this forum. There's a magisk safety net patch that got mine working.
Click to expand...
Click to collapse
I have the lastest patch installed for Safetynet. I'm wondering if maybe it's because I'm on the newest Pixel Update.
Guess I'll test out somethings when I get home.
Mine is working fine. Follow instructions on p7 pro thread.
omf05 said:
I have the lastest patch installed for Safetynet. I'm wondering if maybe it's because I'm on the newest Pixel Update.
Guess I'll test out somethings when I get home.
Click to expand...
Click to collapse
Which latest patch? You need to have this one installed.
Yeah...he probably doesn't have Displax's mod one...he's the fourth person I've seen on this forum that's come from the regular USNF forum wondering why the usual one's not passing...
side note: it's either that or people applying the Magisk OTA update method not knowing Magisk developer hasn't applied the difference to patch and restore init_boot versus boot...
OP, use the one Lughnasadh above linked...
Also -- the obligatory after applying the module, don't forget to clear cache & data of Google Play Services, Google Play Store, Google Play Protect, and Google Service Framework....
*note: also don't forget to install systemless hosts....
Also, you should check your Safetynet status using the 2 apps YASNAC and Play Integrity API Checker from the Play Store...if you're not passing those 2 (other than Strong_Integrity), you're not gonna pass wallet...
Lughnasadh said:
Which latest patch? You need to have this one installed.
Click to expand...
Click to collapse
Yeah, that's the one I have installed.
simplepinoi177 said:
Yeah...he probably doesn't have Displax's mod one...he's the fourth person I've seen on this forum that's come from the regular USNF forum wondering why the usual one's not passing...
side note: it's either that or people applying the Magisk OTA update method not knowing Magisk developer hasn't applied the difference to patch and restore init_boot versus boot...
OP, use the one Lughnasadh above linked...
Also -- the obligatory after applying the module, don't forget to clear cache & data of Google Play Services, Google Play Store, Google Play Protect, and Google Service Framework....
*note: also don't forget to install systemless hosts....
Also, you should check your Safetynet status using the 2 apps YASNAC and Play Integrity API Checker from the Play Store...if you're not passing those 2 (other than Strong_Integrity), you're not gonna pass wallet...
Click to expand...
Click to collapse
Thanks,
I must have missed something when I was doing it, was up pretty late lol