Related
hi i have a magisk and twrp rooted oneplus 6 with radioactive kernel, and can't use google pay, i get an error message please check your settings after it's tried to verify with the bank, but the bank say everything is fine, and it was working before i unlocked bootloaders and installed custon software, any ideas out there, any help would be greatly appreciated, thanks
Rando
Try to hide google pay app with "magisk hide" in magisk app
Edit:
Google Pay is working with my OP6 [email protected] and TWRP
Google pay is working fine for me too also rooted with magisk
Some people have begun to have issues with Magisk and safetynet tripping over the past few days, we're trying to figure it out in the Magisk forums. This appears to have coincided with the Android Pie release and it's possible modifications have been made to safetynet. John Wu is looking into it. There are a few additional modules you can try along with Magisk Hide. Some work for some people. I've had no luck yet personally.
ClassicRando said:
hi i have a magisk and twrp rooted oneplus 6 with radioactive kernel, and can't use google pay, i get an error message please check your settings after it's tried to verify with the bank, but the bank say everything is fine, and it was working before i unlocked bootloaders and installed custon software, any ideas out there, any help would be greatly appreciated, thanks
Rando
Click to expand...
Click to collapse
Busybox always makes me fail safety net, even systemless. Make sure you haven't installed a magisk module with it or a custom rom with it. I think recent Google versions check for it.
ClassicRando said:
hi i have a magisk and twrp rooted oneplus 6 with radioactive kernel, and can't use google pay, i get an error message please check your settings after it's tried to verify with the bank, but the bank say everything is fine, and it was working before i unlocked bootloaders and installed custon software, any ideas out there, any help would be greatly appreciated, thanks
Rando
Click to expand...
Click to collapse
Try clearing play store data. Same thing happened to me and my play store was uncertified from unlocking the bootloader. Once I cleared app data it was certified and could add my card.
Yesterday 12:27 PM
Pundy
Try to hide google pay app with "magisk hide" in magisk app
Edit:
Google Pay is working with my OP6 [email protected] and TWRP
Click to expand...
Click to collapse
thanks for the tip but i already have it hidden.
Yesterday 11:25 PM
yldlj
Try clearing play store data. Same thing happened to me and my play store was uncertified from unlocking the bootloader. Once I cleared app data it was certified and could add my card.
Click to expand...
Click to collapse
i Tried this as it sounded promising, but no joy, i still can't get it to work, thanks for the help though so far everyone, but nothing has worked.
texasaggie1 said:
Busybox always makes me fail safety net, even systemless. Make sure you haven't installed a magisk module with it or a custom rom with it. I think recent Google versions check for it.
Click to expand...
Click to collapse
Unfortunately removing BusyBox didn't change the fail
fireguy0306 said:
Unfortunately removing BusyBox didn't change the fail
Click to expand...
Click to collapse
Have you tried using the island app ?
Also you know you have to wipe/reset Google Play before you check again correct?
once you fail safety net it will always fail no matter what until you reset Google Play
yldlj said:
Try clearing play store data. Same thing happened to me and my play store was uncertified from unlocking the bootloader. Once I cleared app data it was certified and could add my card.
Click to expand...
Click to collapse
i clear all data every time i change anything as standard practice, but thanks for the idea
texasaggie1 said:
Have you tried using the island app ?
Also you know you have to wipe/reset Google Play before you check again correct?
once you fail safety net it will always fail no matter what until you reset Google Play
Click to expand...
Click to collapse
i don't know what the island app is, but as above i wipe all data as standard everytime i change something, i'll look inti island, but i'm starting to thing this is just a bug
Have the problem as well..
I have the same problem. Running OP6, Android P Developer Preview 4, TWRP recovery and magisk (v16.7).
Magisk hide is enabled for GPay as well as many other banking apps. I know for sure its something to do with GPay, since the other apps that initially complained and triggered safetynet, started running as soon as I enabled Magisk hide for those apps.
ClassicRando said:
i clear all data every time i change anything as standard practice, but thanks for the idea
i don't know what the island app is, but as above i wipe all data as standard everytime i change something, i'll look inti island, but i'm starting to thing this is just a bug
Click to expand...
Click to collapse
Google pay issue with rooted oneplus 6 (PIE)
Hi all,
Try the steps as advised in the video, it worked for me
https://youtu.be/lyC1SpDWMNA
Thanks
Clear data of your and force app
Magisk hide check your app and other google app
And most imp disable phone permissions for google play service.....
android_smater said:
Clear data of your and force app
Magisk hide check your app and other google app
And most imp disable phone permissions for google play service.....
Click to expand...
Click to collapse
This worked for me thank you
Websterwjc said:
This worked for me thank you
Click to expand...
Click to collapse
Welcome...
ClassicRando said:
hi i have a magisk and twrp rooted oneplus 6 with radioactive kernel, and can't use google pay, i get an error message please check your settings after it's tried to verify with the bank, but the bank say everything is fine, and it was working before i unlocked bootloaders and installed custon software, any ideas out there, any help would be greatly appreciated, thanks
Rando
Click to expand...
Click to collapse
I finally found the route cause of gpay not working, it was my WiFi, I found the answer purely by accident when I was in a shop and had forgotten my wallet, so I did a last ditch attempt to set up gpay again with my mobile data and it worked first time, when I got home i deleted the app and reinstalled while trying to set up via WiFi again and I got the same error message, switched to mobile data and it set up perfectly.
I have no idea why my WiFi was stopping gpay from getting set up, but that was the cause, 100% certain.
android_smater said:
Clear data of your and force app
Magisk hide check your app and other google app
And most imp disable phone permissions for google play service.....
Click to expand...
Click to collapse
yes, this works.
Hi,
It was working before for me until 15th March, and now it completely stopped working. I've tried to re-add my card, but then it complains about the device is rooted or altered. I could keep device certification, and safetynet check passes. Tried these methods, nothing.
Does anyone has any suggestions?
Thanks
antivirtel said:
Hi,
It was working before for me until 15th March, and now it completely stopped working. I've tried to re-add my card, but then it complains about the device is rooted or altered. I could keep device certification, and safetynet check passes. Tried these methods, nothing.
Does anyone has any suggestions?
Thanks
Click to expand...
Click to collapse
Update Magisk to v19 and clear data of the app, hide it in Magisk Hide and try to re-add it
I have a fix I u didn't have one, First of all hide all Google apps from Magisk hide.
Then goto setting, apps, permission and disable telephone permission of google play services. That's it.
Not sure how I got here.
Yesterday, went to pay at a Grocery Story with Google Pay, got a message that said "You can no longer pay in stores with Google Pay." Magisk seemed okay, seemed like I was passing SafetyNet (tried two different apps, including Magisk's built-in checker). No big deal, paid the old-fashioned way.
Today, I decided since Magisk or Google Pay was going to be that way, I might as well update EMUI—I've put it off for a good six months or so, because everything was working fine. Now that it wasn't, why not do the whole shebang?
Update went smoothly. Now on B376 (I think).
Updated Magisk. Patched boot.img, all that.
Now, however, I'm getting this screen, and I think somewhere I must have flashed the wrong Magisk. I'm still rooted (Adaway works), but MagiskManager won't get past this screen.
Any ideas on how to do this properly so Magisk and MagiskManager are on the same page?
Hi Daina,
same problem here with a HTC U11. Unfortunately no ideas and no workaround yet.
---------- Post added at 03:22 PM ---------- Previous post was at 02:51 PM ----------
Hi Daina
I downloaded the new Magisk Release 18.1 from github.com and installed the ZIP File via TWRP. After a reboot everything works fine now.
TE]
Haluter said:
Hi Daina,
same problem here with a HTC U11. Unfortunately no ideas and no workaround yet.
---------- Post added at 03:22 PM ---------- Previous post was at 02:51 PM ----------
Hi Daina
I downloaded the new Magisk Release 18.1 from github.com and installed the ZIP File via TWRP. After a reboot everything works fine now.
TE]
Click to expand...
Click to collapse
Thanks for this.
Just downloaded Magisk 18.1.zip from Github. It's currently on my computer.
My question is... how do I install it at this point? I don't have TWRP on my Mate 9, since it's so finicky to use. Yesterday, after I updated EMUI, I installed Magisk Manager, and had it sort of install/do its thing. I assume it downloaded its own Magisk, though which version, I have no idea. I used the custom channel found here.
However, now that I'm retracing my steps, I just noticed the verbiage in @Wirmpolter's guide, that says
Latest Magisk Manager and magisk work now so no longer need to setup and flash the specific version found in the original post from topjhnwu.
Click to expand...
Click to collapse
So... no need to use the custom channel URL from Magisk Manager. Got it.
Any advice on how to proceed? Currently... I have Magisk and Magisk Manager installed. Magisk Manager is 7.0, but Magisk itself, I suspect, is not 18+.
If I had to lay it out, I might try:
Uninstall Magisk (uninstall.zip, or whatever it's called)
Reinstall Magisk Manager 7.0
Use @Wirmpolter's instructions, pulling, patching, and re-pushing boot image (again!) in fastboot.
Is there an easier way to do this? Just curious.
EDIT: Another quick question to the big bad XDA world out there: do I flash the Magisk uninstall zip in fastboot, as well?
So I did it.
I uninstalled Magisk Manager 7.0, which didn't work with the version of Magisk I flashed yesterday.
Installed an older Manager just to bring up the interface.
From there, I uninstalled Magisk completely, using the Uninstall option from within the manager.
Then I followed @Wirmpolter 's guide, only getting stuck when my computer refused to see my phone in fastboot. I finally managed it, though, and now I have Magisk 18.1, with the Magisk Manager 7.0 interface.
Google Pay is still failing, though, even though I pass Safety Net.
Anybody have any clues why?
daina said:
So I did it.
I uninstalled Magisk Manager 7.0, which didn't work with the version of Magisk I flashed yesterday.
Installed an older Manager just to bring up the interface.
From there, I uninstalled Magisk completely, using the Uninstall option from within the manager.
Then I followed @Wirmpolter 's guide, only getting stuck when my computer refused to see my phone in fastboot. I finally managed it, though, and now I have Magisk 18.1, with the Magisk Manager 7.0 interface.
Google Pay is still failing, though, even though I pass Safety Net.
Anybody have any clues why?
Click to expand...
Click to collapse
Try using play services version 15.1.78 beta, others had this too but that version of play services fixed it (for some reason).
ante0 said:
Try using play services version 15.1.78 beta, others had this too but that version of play services fixed it (for some reason).
Click to expand...
Click to collapse
Thanks. No luck. Obtained 15.1.78 beta from apkmirror, and installed. Tried it on the Coke machine at work, same screen.
Someone on reddit ended up wiping cache and data on Google Play Store and Google Play Services, but then they ended up having to set up their cards again in GPay. Do you think this is the way to go?
Was trying to avoid having to set up cards again, since one of my cards involves having to call the bank to get it authorized...
daina said:
Thanks. No luck. Obtained 15.1.78 beta from apkmirror, and installed. Tried it on the Coke machine at work, same screen.
Someone on reddit ended up wiping cache and data on Google Play Store and Google Play Services, but then they ended up having to set up their cards again in GPay. Do you think this is the way to go?
Was trying to avoid having to set up cards again, since one of my cards involves having to call the bank to get it authorized...
Click to expand...
Click to collapse
Try: https://forum.xda-developers.com/showpost.php?p=79029481&postcount=9
Its a temporary fix as well... But beats calling the bank I guess
Hi Daina,
after a short-lived success I ended with the same problems the next day. Afterwards I tried all suggestions from various forums but nothing worked.
After a short period of frustration I decided for a radical solution and installed a new OS on my HTC U11. (Lineage unofficial)
And... surprise! GPay works without any flaws.
I have followed the instructions here to update my OnePlus6 from OOS 09.09 to OOS 10. It all worked fine and I lost no data, although it has a few quirks. Minor bugs that I expect will get fixed in a coming release. The problem is that my phone no longer passes the SafetyNet tests, and so I can no longer use my phone for Google Pay. Is anyone else having that problem?
To be very clear, when on the 9.09 release with TWRP and Magisk my phone passed the SafetyNet tests and GooglePay work just fine. Now, both the Basic Integrity and CTS Profile Match tests fail.
I am on oneplus 6 android 10 openbeta 1
With unlock bootloader and encrypted.
Magisk installed.
This mod work on my phone
Yes. Passed both CTS and BasicIntegrity
Yep, here too. Everything passes, and i can pay with Google Pay.
ButtonBoy said:
I have followed the instructions here to update my OnePlus6 from OOS 09.09 to OOS 10. It all worked fine and I lost no data, although it has a few quirks. Minor bugs that I expect will get fixed in a coming release. The problem is that my phone no longer passes the SafetyNet tests, and so I can no longer use my phone for Google Pay. Is anyone else having that problem?
To be very clear, when on the 9.09 release with TWRP and Magisk my phone passed the SafetyNet tests and GooglePay work just fine. Now, both the Basic Integrity and CTS Profile Match tests fail.
Click to expand...
Click to collapse
Are you using edxposed? Google made some updates and is detecting edxposed, disable it and see if safety net passes.
ptmaniac said:
Are you using edxposed? Google made some updates and is detecting edxposed, disable it and see if safety net passes.
Click to expand...
Click to collapse
No. I did have AdAway & FDroid installed, though. I removed both of those, and still no joy.
ptmaniac said:
Are you using edxposed? Google made some updates and is detecting edxposed, disable it and see if safety net passes.
Click to expand...
Click to collapse
Turn on 'App List' in experimental settings and add all Google apps to the blacklist. Especially Play Services, Play Store and Framework as they are the culprits that detect EdXposed. Leave out any other Google apps that you have Xposed mods for such as Gmail and Play Store Dark Themes.
So the latest 31.0810.1226.77-1.1.138-2203 update has introduced Android 12..and killed Safetynet bypass. The kdragon Safetynet fix 2.2.1 no longer works and the device doesn't pass basic attestation either. Is there a workaround that doesn't involve unrooting it or are we ****ed for the time being? Goddamn Magisk had to deprecate their Magiskhide and safetynet bypass features. /rant
Just re-flash magisk should be enough. Else re-flash safetynet-fix-v2.2.1.zip after magisk.
course if you havent got TWRP installed you would have to re-flash the boot.img to get magisk working again.
I usually do that after every firmware update, reflashing the patched boot.img, and I already had the latest kdrag0n safetynet fix (2.2.1 as of now). This time after restarting on android 12, safety net failed and the Google pay app reported that my device is no longer certified. Guess I'll try again. Wait..is there finally now a TWRP for ROG 5? I miss using it from my old 1+3.
Edit - didn't work.
There is no TWRP for A12.
You will have to make a new patched boot image for A12. Go to Magisk and patch boot.img taken from Payload.bin (Payload dunper required) and flash it. That will get you root back.
Then you can use the universal safety net fix zip inside magisk.
BakaValen said:
Then you can use the universal safety net fix zip inside magisk.
Click to expand...
Click to collapse
Getting root on 12 is not the problem. The kdrag0n safetynet fix stopped working after upgrading to 12. I have the latest Zygisk version 2.2.1 that was updated last December.
I am on A12 latest. Rooted with safetynet passed using the fix. You must be doing something wrong.
Explain your process
Did the same process I've followed for every system update - patch boot.img with the payload dumper and patch script as described in this forum before applying the update, and flash it afterwards. The safetynet fix that had already been installed and working under 11 stopped, and removing and reapplying it does nothing.
Flash version 2.2.1.
I'm telling you. There is a process not being done correctly.
I'm on the latest A12 for the 5s with safetynet pass.
Send screenshots of install process (magisk black screen bit)
BakaValen said:
Flash version 2.2.1.
I'm telling you. There is a process not being done correctly.
I'm on the latest A12 for the 5s with safetynet pass.
Send screenshots of install process (magisk black screen bit)
Click to expand...
Click to collapse
Yes, I'm using 2.2.1. The flashing process appears to have worked, as shown -
It's the latest Magisk with zygisk enabled. FWIW here's the result of running safetynet test also.
KaiserSnorezay said:
Yes, I'm using 2.2.1. The flashing process appears to have worked, as shown -
It's the latest Magisk with zygisk enabled. FWIW here's the result of running safetynet test also.
Click to expand...
Click to collapse
Are you running Shamiko withLSPosed/Xprivacy + blocking tracking for Goog Play Services and the relevant apps? Safetynetfix 2.2.1 alone is no longer a full solution whether you're on A11 or A12 and regardless of your Magisk version...
If you mean adding play services to the deny list, then yes. Got rid of xprivacylua as it didn't help. Used it to block reading identifiers and tracking for play services and other components, to no avail. Right now even the basic integrity test is failing.
Update - Installed Shamiko, disabled the 'enforce denylist' in Magisk so that it takes over the job and rebooted..and nothing different.
Passed here just fine... all you need is a clean magisk install, then...
hide the magisk app itself.
enable zygisk, reboot.
flash zygisk version of usf https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
optionally: flash shamiko, reboot, then select play store and play service in deny list without enabling it.
check again in YASNAC, should pass now.
Don't know WTF is wrong this time, compared to every previous time it would just simply upgrade with no problems.
Installed this month's system update.
Uninstalled Magisk.
Patched the boot.img with Magisk, flashed it.
Reinstalled the Magisk apk. It was rooted, all my settings and modules showed up as usual.
Toggled zygisk to off, just to be sure, restarted, turned it back on, restarted.
NOTHING. Again the ****ing Safetynet fails.
KaiserSnorezay said:
Don't know WTF is wrong this time, compared to every previous time it would just simply upgrade with no problems.
Installed this month's system update.
Uninstalled Magisk.
Patched the boot.img with Magisk, flashed it.
Reinstalled the Magisk apk. It was rooted, all my settings and modules showed up as usual.
Toggled zygisk to off, just to be sure, restarted, turned it back on, restarted.
NOTHING. Again the ****ing Safetynet fails.
Click to expand...
Click to collapse
Google changed something today, as Google Pay now detects root when I had used it just yesterday without issue. It appears the safetynet fix needs fixing.
Strephon Alkhalikoi said:
Google changed something today, as Google Pay now detects root when I had used it just yesterday without issue. It appears the safetynet fix needs fixing.
Click to expand...
Click to collapse
Re-check that all GPay sub components are added to your Shamiko deny list and Shamiko configured properly (i.e with Magisk's own deny disabled). Also check and ensure that tracking is blocked for Gpay in Xprivacy.
If you don't have any one of those installed - you need it to be completely covered. Even if you pass Saftynet. Safetynet Fix and Magisk hide alone won't cut it, at least not currently. Tough apps like banking and payment apps will detect you.
Many people skip one or more of these and run into frustration with root detection..
I noticed that if I add Google play services (all components) to the Magisk deny list, it doesn't persist after reboot. Could that be it? Is it unable to modify the system partition? I'm using Shamiko, with Magisk enforce deny list option disabled.
Andrologic said:
Re-check that all GPay sub components are added to your Shamiko deny list and Shamiko configured properly (i.e with Magisk's own deny disabled). Also check and ensure that tracking is blocked for Gpay in Xprivacy.
If you don't have any one of those installed - you need it to be completely covered. Even if you pass Saftynet. Safetynet Fix and Magisk hide alone won't cut it, at least not currently. Tough apps like banking and payment apps will detect you.
Many people skip one or more of these and run into frustration with root detection..
Click to expand...
Click to collapse
It may be a glitch, as GPay is currently not complaining about root when I pull up one of my stored cards. Regardless, I don't have Shamiko installed, but will look into it so long as it doesn't require Xposed or any of its derivatives.
EDIT: Confirmed to be a glitch. Not more than five minutes prior to this edit I used GPay without trouble.
Did some more testing, given I had to install the latest June firmware anyway. Fully removed Magisk (I hadn't done this earlier) and reinstalled, it passes. The culprit for failure turned out to be LSPosed. When enabled, it fails SafetyNet. I can manage without it but if anyone knows a workaround please do tell.
KaiserSnorezay said:
Did some more testing, given I had to install the latest June firmware anyway. Fully removed Magisk (I hadn't done this earlier) and reinstalled, it passes. The culprit for failure turned out to be LSPosed. When enabled, it fails SafetyNet. I can manage without it but if anyone knows a workaround please do tell.
Click to expand...
Click to collapse
Same boat here. I got safetynet fix passed literally right after I disabled LSPosed. I glimpsed through the issues in LSPosed Github repo but they don't seem to be working on this.
I dont have any issues with safetynet.
Hi!
I have an issue and was wondering if anyone have a solution. Suddenly Google wallet stopped working, saying that my phone is not up to security standards. It worked fine until this Sunday.
I'm using beyondrom, magisk app (zygisk and hidden) with Universal safteynet fix v.2,4 and Shamiko v.0,6. I also have all Google services etc. in deny list.
Anyone have had the same issue and/or something to try to fix?
eddy92 said:
Hi!
I have an issue and was wondering if anyone have a solution. Suddenly Google wallet stopped working, saying that my phone is not up to security standards. It worked fine until this Sunday.
I'm using beyondrom, magisk app (zygisk and hidden) with Universal safteynet fix v.2,4 and Shamiko v.0,6. I also have all Google services etc. in deny list.
Anyone have had the same issue and/or something to try to fix?
Click to expand...
Click to collapse
What does Play Integrity Checker or TB Checker report for Play Integrity results?
V0latyle said:
What does Play Integrity Checker or TB Checker report for Play Integrity results?
Click to expand...
Click to collapse
Huh, actually only meets device and Basic Integrity, strong Integrity is red.
Any tips on what to do/check?
eddy92 said:
Huh, actually only meets device and Basic Integrity, strong Integrity is red.
Any tips on what to do/check?
Click to expand...
Click to collapse
Strong integrity will always be red on an unlocked bootloader. Basic and Device integrity are the only requirements, Wallet does not use Strong. If you don't already, enable DenyList on Wallet and GPay - make sure you expand and enable on all subprocesses. Then, clear Wallet data and reopen it.
I had this issue a few days ago and fixed it with this method.
V0latyle said:
Strong integrity will always be red on an unlocked bootloader. Basic and Device integrity are the only requirements, Wallet does not use Strong. If you don't already, enable DenyList on Wallet and GPay - make sure you expand and enable on all subprocesses. Then, clear Wallet data and reopen it.
I had this issue a few days ago and fixed it with this method.
Click to expand...
Click to collapse
I have tried this several times, even with installing the wallet app in between. Unfortunatley it does not work! I have no GPay app, just the Wallet one.
I have fixed several other apps with this method, but Wallet does not want to work with me
eddy92 said:
I have tried this several times, even with installing the wallet app in between. Unfortunatley it does not work! I have no GPay app, just the Wallet one.
I have fixed several other apps with this method, but Wallet does not want to work with me
Click to expand...
Click to collapse
If you're running the latest kdragon version of safteynet fix, try deleting the module and install the latest version of the safteynet fix by displax. I myself had problems sometime ago and this helped. Then clear everything again restart and it'll probably work.
erik2041999 said:
If you're running the latest kdragon version of safteynet fix, try deleting the module and install the latest version of the safteynet fix by displax. I myself had problems sometime ago and this helped. Then clear everything again restart and it'll probably work.
Click to expand...
Click to collapse
Hi, thanks for the tip. Sorry stupid question maybe, but where can i find Displax safteynet fix? When searching I can only find Kdrag0ns version. Even on Displax Github it seems to link to the Kndrag0n version.
EDIT: Sorry, nvm I found it! (Link if someone else is looking: https://github.com/Displax/safetynet-fix/releases)
Still does'nt work though
I just realised, with the latest beyondrom magisk got changed to magisk alpha, so you kinda have to go and re-hide the app and so on. Have you done that?
erik2041999 said:
I just realised, with the latest beyondrom magisk got changed to magisk alpha, so you kinda have to go and re-hide the app and so on. Have you done that?
Click to expand...
Click to collapse
I have not yet updated to BeyondROM 2.3, I am still on 2.2 BVL1 version (from december 22). I will update to version 2.3 when I can, then perhaps I can try these steps again. Meybe it can help.
I should not have to re-hide etc. since I didnt update, right?
Nope, sorry I thought you did. But that's probably the reason for why the wallet isn't working. In that case first update and go through all the steps, should work then. It's one of the reasons magisk got replaced by magisk alpha in the newest beyond rom version.
erik2041999 said:
Nope, sorry I thought you did. But that's probably the reason for why the wallet isn't working. In that case first update and go through all the steps, should work then. It's one of the reasons magisk got replaced by magisk alpha in the newest beyond rom version.
Click to expand...
Click to collapse
Excellent, I will try asap. Thanks for all help!!
eddy92 said:
I have not yet updated to BeyondROM 2.3, I am still on 2.2 BVL1 version (from december 22). I will update to version 2.3 when I can, then perhaps I can try these steps again. Meybe it can help.
I should not have to re-hide etc. since I didnt update, right?
Click to expand...
Click to collapse
If you're on a custom ROM you may need to use MHPC to spoof a valid device profile.
I had the same problem here, I managed to solve it by installing Magisk delta and Universal SafetyNet modded.