magiskhide props no longer working - OnePlus 7T Questions & Answers

I'm on global OnePlus 7t. I recently reverted back to 10.09 from open beta 2. Netflix and Disney+ stop working as soon as I unlock the bootloader. That's usually no problem since I just use magiskhide props to solve that problem but I tried it today and can't get it to work. I tried multiple device props and still can't clear ctsProfle. Any help would be greatly appreciated. Thank you

Never****ingMind. I just read that I should enable magiskhide in settings and that did it. Smdh. Thanks anyway

Related

Tez suddenly not working(India)

Hello,
I am facing issues getting tez to work with Magisk. Till date it was working completely fine with Magisk Hide enabled. My device is passing the safetynet check however Tez has stopped working.
Any help would be appreciated.
ali.jujara said:
Hello,
I am facing issues getting tez to work with Magisk. Till date it was working completely fine with Magisk Hide enabled. My device is passing the safetynet check however Tez has stopped working.
Any help would be appreciated.
Click to expand...
Click to collapse
Might want to follow the rules before asking for help. Like describing what trouble shooting you have done, posting a logcat, you know things that are troubleshooting basics.
Read this to get some idea

Stockish P2XL Magisk and Google Pay

I was running Android 9 Aug?2018 update with a custom kernel and Magisk. A few weeks ago Google Pay stopped working and i read the long thread here about the Google Play store update and Magisk no longer hiding root. I dirty flashed an updated stock rom and removed the format (-w) switch. I stayed with the stock kernel. Re-rooted with update Magisk root and Magisk app. In Magisk i pass SafetyNet Check ctsProfile and basicIntegrity. When i try to use Google Pay I still get the error message that i cannot use GooglePay there. I am very close to just going completely stock with no root as I am not jacking with my phone as much as i did years ago, android is progressing nicely and plus many devs have moved on from the P2XL. I just really dont want to have to re setup my phone. Any thing else i can try to use GooglePay before i go back to stock?
P2XL Bootloader unlocked
Android: 9.0 3/5/19
Magisk V19.0 (19000)
Magisk Manager 7.1.1
Not running any Magisk Modules
Thanks for any help or suggestions
fortillian said:
I was running Android 9 Aug?2018 update with a custom kernel and Magisk. A few weeks ago Google Pay stopped working and i read the long thread here about the Google Play store update and Magisk no longer hiding root. I dirty flashed an updated stock rom and removed the format (-w) switch. I stayed with the stock kernel. Re-rooted with update Magisk root and Magisk app. In Magisk i pass SafetyNet Check ctsProfile and basicIntegrity. When i try to use Google Pay I still get the error message that i cannot use GooglePay there. I am very close to just going completely stock with no root as I am not jacking with my phone as much as i did years ago, android is progressing nicely and plus many devs have moved on from the P2XL. I just really dont want to have to re setup my phone. Any thing else i can try to use GooglePay before i go back to stock?
P2XL Bootloader unlocked
Android: 9.0 3/5/19
Magisk V19.0 (19000)
Magisk Manager 7.1.1
Not running any Magisk Modules
Thanks for any help or suggestions
Click to expand...
Click to collapse
There is a lot of talk in many threads about this. There is a good tutorial or two around that do work but seemingly only temporarily then it breaks again. Seems Google would a way to detect stuff that is not patched yet. I am at work so I don't have much time to go searching but it should not be hard to find. It includes deleting a folder and reinstalling and hiding magisk.
CyberpodS2 said:
There is a lot of talk in many threads about this. There is a good tutorial or two around that do work but seemingly only temporarily then it breaks again. Seems Google would a way to detect stuff that is not patched yet. I am at work so I don't have much time to go searching but it should not be hard to find. It includes deleting a folder and reinstalling and hiding magisk.
Click to expand...
Click to collapse
Yea, I've been through that 106 page thread and a few others. Renamed folders, deleted folders, reinstalled apps, hid services in magisk hide. I was never a fan of NFC payment until I started using it lol.
Try safety patch module in Magisk to pass Safetynet
HueyT said:
Try safety patch module in Magisk to pass Safetynet
Click to expand...
Click to collapse
I appreciate the reply. installed this plugin. cleared cache/data for Google Pay and Deleted the GMS folder again. Reinstalled GPay, no joy
Trying to decide on checking out Android Q or Dirty Unicorn. I dont jack with my phone much anymore, may be worth it to checkout Q and lock it up for GPAY atleast for now.
fortillian said:
I appreciate the reply. installed this plugin. cleared cache/data for Google Pay and Deleted the GMS folder again. Reinstalled GPay, no joy
Trying to decide on checking out Android Q or Dirty Unicorn. I dont jack with my phone much anymore, may be worth it to checkout Q and lock it up for GPAY atleast for now.
Click to expand...
Click to collapse
I'm thinking the same

Tab S7+ SM-T970 SafetyNet

Hi I rooted my tab s7+ sm-t970 but when I use magisk it give me a SafetyNetApi error it never passes can someone help me fix this. Thank you
I have the same exact issue.
Maybe could be our root?
homogamez said:
Maybe could be our root?
Click to expand...
Click to collapse
I guess its possible. It's been a long time since I've rooted something. When I open the Magisk app it says install next to magisk and the same for app. I hit install and it goes through the processes but nothing happens. There's no other area to add modules or anything. Can we go start over and do it again without breaking something? I'm lost. lol
It also happens on One Ace and N10
Hopefully next version will fix it
I can use banking app but not netflix. I get the red warning at boot up so I figure I gotta be rooted. Maybe I'll try adding TWRP
EDIT:
Went to backup using TWRP and said my device isn't rooted. I give up. lol
There's a discussion about this issue. There's an error on API key.
You can get Safety net check from play store and see the actual results
Let me look for this thread because I don’t see a way to fix
Safetynet api error
Hello looking for help as I can't figure out what's wrong. I've tried downloading the code on only wifi and only mobile data and I still get the api error. I'm not running any add blockers. Using magisk canary.
forum.xda-developers.com
I'm about to become your favorite person ever, everyone! ​​I am currently passing SafetyNet after flashing the kdrag0n safetynet-fix to my Samsung Galaxy Tab S7+ SM-T970 and enabling the MagiskHide Props Config module in Magisk.​
HOWEVER, as was the case with literally all of the stock-based ROMs for the Galaxy S8, it appears that there will still be issues with a select few apps. For example, you will get soft-banned from Snapchat every few days. Also, certain healthcare apps will still be able to detect root (likely all related to Knox, since a Pixel 5 rooted via the same methods will launch the same apps without issue).
All the best from your fellow tinkerer - Godless1
(P.S. I'm going to copy and paste this into its own thread for better visibility.)

How To Guide Rooted S22: How to make the new Google Wallet work

If you rooted using the method on this forum, and your Google Pay app was recently upgraded to Google Wallet, you will probably find that it doesn't work anymore. Even if you have the Universal SafetyNet Fix installed and SafetyNet shows as passing, the new payment app will still detect your device as rooted. This is because it now uses Google Play Integrity instead of SafetyNet.
There's a lot of discussion in this thread. But the short version is, if you want to get payments working again:
1. Install MagiskHide Props Config.
2. Follow the instructions on that page to change your device fingerprint to Samsung Galaxy S21 (A11).
That's it! Some people in the thread also cleared data for Google Play Services but I don't think I did. Also in that thread is a verification app (first version, official version) for Google Play Integrity that you can use to make sure your device fingerprint setting is correct.
So far I haven't noticed any side effects from changing the fingerprint. I was unable to receive any SMS messages after first changing, but I rebooted a second time and that issue went away.
Just install safetynet-fix-v2.3.1-MOD.zip in Magisk. That worked on my OnePlus Nord CE (EU).
Vattu said:
Just install safetynet-fix-v2.3.1-MOD.zip in Magisk. That worked on my OnePlus Nord CE (EU).
Click to expand...
Click to collapse
Yeah this thread is now out of date. The updated safetynet fix is a much better option now.
You don't need just the safetynet module. You need Shamiko along that.
So latest Safetynet + Shamiko 0.5.2 (the latest version right now) and you're all set. You gotta whitelist the banking apps you use and they'll work perfectly fine. These 2 were enough to allow my preferred ridiculous banking app to work without an issue, without any other modules or tweaking and such.
dragos281993 said:
You don't need just the safetynet module. You need Shamiko along that.
Click to expand...
Click to collapse
You only need Shamiko if you use LSposed, right? I don't use LSposed and it's been enough for me to put all of my annoying apps on the Magisk denylist.
aurny said:
You only need Shamiko if you use LSposed, right? I don't use LSposed and it's been enough for me to put all of my annoying apps on the Magisk denylist.
Click to expand...
Click to collapse
No. I only had Magisk installed with Zygisk turned on. I first installed Safetynet Fix then Shamiko. The first module wasn't enough for my preffered banking app to not detect that the bootloader was unlocked. Shamiko fixed that. I simply installed it as a module in Magisk
Thanks, good to know. I haven't had that issue yet but I'll remember this in case I need it in the future!
aurny said:
If you rooted using the method on this forum, and your Google Pay app was recently upgraded to Google Wallet, you will probably find that it doesn't work anymore. Even if you have the Universal SafetyNet Fix installed and SafetyNet shows as passing, the new payment app will still detect your device as rooted. This is because it now uses Google Play Integrity instead of SafetyNet.
There's a lot of discussion in this thread. But the short version is, if you want to get payments working again:
1. Install MagiskHide Props Config.
2. Follow the instructions on that page to change your device fingerprint to Samsung Galaxy S21 (A11).
That's it! Some people in the thread also cleared data for Google Play Services but I don't think I did. Also in that thread is a verification app (first version, official version) for Google Play Integrity that you can use to make sure your device fingerprint setting is correct.
So far I haven't noticed any side effects from changing the fingerprint. I was unable to receive any SMS messages after first changing, but I rebooted a second time and that issue went away.
Click to expand...
Click to collapse
Thank you very much, it worked perfectly.
This actually worked, thank you!

Question Can/Should I use device simulation?

I'm almost done setting up my new RedMagic 8, and I have a couple of issues:
Disney+ won't install. This might be because I'm rooted, but I've installed Universal Safetynet fix, and I'm supposedly passing.
Gpay isn't working for me. This is _probably_ a rooting issue, but I'm confused because, again, I'm passing safetynet.
I'd probably chalk this all up to being rooted, but my old phone (OnePlus 7 Pro) is rooted, and I can use both of these apps on there. I've read about MagiskHide Props Config, and it warns that device simulation should only be done if you have to, but I'm starting to wonder if there's any other way to get these apps running.
Have you tried installing Shamiko?
I've never heard of that before, but I've installed it now. So far there isn't any difference. Do you know how it's different from Magisk enforcing the hide list?
jfsat said:
I've never heard of that before, but I've installed it now. So far there isn't any difference. Do you know how it's different from Magisk enforcing the hide list?
Click to expand...
Click to collapse
To get Google Pay/Wallet working, I used Universal SafetyNet Fix by kdrag0n and did the usual under Magisk settings -
Enable Zygisk
Enable Enforce DenyList
Configure DenyList -> Add your Google Pay/Wallet here
yoonhx said:
To get Google Pay/Wallet working, I used Universal SafetyNet Fix by kdrag0n and did the usual under Magisk settings -
Enable Zygisk
Enable Enforce DenyList
Configure DenyList -> Add your Google Pay/Wallet here
Click to expand...
Click to collapse
That worked on my old phone (OnePlus 7 Pro), but not my new phone (RedMagic 8 Pro).
I swear, it's getting harder and harder to be a rooted user. I just want to use Adaway! Why is that so much to ask?!

Categories

Resources