Develop Bugs

Android P dp4 / Magisk safety net

Coming from Android P dp3, I wiped and clean flashed dp4. Set up as new, then flashed Magisk.
I have tried different settings, but for the life of me, I cannot get ctsProfile to pass.
Anyone else having a similar issue?

I was on DP3 and both failed for me.. so I just assume wait for an update from the Magisk dev.

Same, will be waiting...

mine was working fine on dp3 but fails cts profile on dp4 (pixel 1 though)

I thought ctsProfile always failed with just Magisk and you need a custom kernel too? I'm waiting for an update to Flash Kernel.

henderjr said:
I thought ctsProfile always failed with just Magisk and you need a custom kernel too? I'm waiting for an update to Flash Kernel.
Click to expand...
Click to collapse
i don't know it was passing on DP3

Did you guys clear data on play services and play store?

The funny thing is that I flashed without wipe and not installing magisk. The cts profile still failed.
Haven't tried fully wipe though.
Sent from my Pixel 2 XL using Tapatalk

henderjr said:
I thought ctsProfile always failed with just Magisk and you need a custom kernel too? I'm waiting for an update to Flash Kernel.
Click to expand...
Click to collapse
Ah -- yes, I probably was on Flash on dp3 -- hard enough to remember what I had for lunch yesterday let alone recall the modding I do to my phone from weeks prior
ram4ufriends said:
Did you guys clear data on play services and play store?
Click to expand...
Click to collapse
Yup. -- think the Flash Colonel will help.

Nope. On my DP3 with magisk, CTS passed.
henderjr said:
I thought ctsProfile always failed with just Magisk and you need a custom kernel too? I'm waiting for an update to Flash Kernel.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

Magisk only worked on boot on DP3 for me. After a couple of minutes it nagged about Magisk v16.4 (which was installed) being available.

So in dp3 I got safety net to pass by clearing Google play services and and the playstore, and after updating to dp4 nothing I did work

KevinThaKid said:
So in dp3 I got safety net to pass by clearing Google play services and and the playstore, and after updating to dp4 nothing I did work
Click to expand...
Click to collapse
I noticed safety net does not pass on DP4 also. have not been able to figure it out either ( may just have to wait for update to magisk ).

wassco said:
I noticed safety net does not pass on DP4 also. have not been able to figure it out either ( may just have to wait for update to magisk ).
Click to expand...
Click to collapse
Not Magisk. Google seems to have done it intentionally.
Guess we've been spoiled the previous builds
https://twitter.com/topjohnwu/status/1014059549643247616?s=09
and
https://developer.android.com/preview/release-notes
"Android P beta devices aren't Compatibility Test Suite (CTS) approved, but they have passed preliminary testing and provide the same set of APIs for developers. Apps that depend on CTS-approved builds might not work normally on supported devices."

I rolled back to DP3, will wait for DP5 to see if it is fixed. I need GPay and that safetynet to pass for stuff daily.
Oh well...working fine on DP3 for me everything I use! Spoiled is right.

techlogik said:
I rolled back to DP3, will wait for DP5 to see if it is fixed. I need GPay and that safetynet to pass for stuff daily.
Oh well...working fine on DP3 for me everything I use! Spoiled is right.
Click to expand...
Click to collapse
Look after flash kernel thread..seems like Google fixed it

The SafetyNet issue has been fixed with a server-side update by Google. I only cleared storage on my Google Play Store app and the device has become 'Certified'. SafetyNet passes and I've just added my card to Google Pay again.

widezu69 said:
The SafetyNet issue has been fixed with a server-side update by Google. I only cleared storage on my Google Play Store app and the device has become 'Certified'. SafetyNet passes and I've just added my card to Google Pay again.
Click to expand...
Click to collapse
Good to know I will update back to dp4 later and do that

widezu69 said:
The SafetyNet issue has been fixed with a server-side update by Google. I only cleared storage on my Google Play Store app and the device has become 'Certified'. SafetyNet passes and I've just added my card to Google Pay again.
Click to expand...
Click to collapse
I tried that but no luck

Can anyone tell me how they rooted?
I tried booting twrp, installing magisk 16, 14.4., 16.4
Installing twrp, flash 16, 14.4, 16.4
Copy the stock boot and patch via the magisk manager, install in twrp,
No luck anyway.
Edit: Twrp can't decrypt a pattern.

Device uncertified after Magisk root on latest factory Android 11

Hi all,
Got a new phone and finally decided to see if I could root the old Pixel 2 XL. It's unlocked, bought directly from Google. Never before unlocked bootloader until now.
It was flashed to factory Android 11 2020-12, and rooted from there. Magisk 21.1 beta was installed from zip while booted into TWRP 3.0.4, as advised in this thread. The latest Play System Update (Oct 5, 2020) was automatically installed while I was messing around afterwords.
I confirmed root access thru a checker and Termux, which is pretty neat! Hadn't rooted a device in a long time!
Unfortunately, device certification fails in Play Store, Magisk SafetyNet check and being unable to add a credit card to Google Pay. Magisk says basicIntegrity passes, but CTSprofile fails.
Things I've tried, mostly from this exhaustive guide:
Hidden Magisk Manager
Enabled MagiskHide, rebooted
Remove Magisk zip from storage
Lock bootloader again, rebooted
Clear app storage for Play store and Play services, rebooted
Disable USB debugging
Disable Play Protect scanning
Looked over XDA boards, Magisk changelog/documentation/guides
Things I haven't done (yet?):
Spoofing device fingerprint. I wouldn't expect this to be necessary, since it's actually authentic! But maybe there's more to it that I don't understand?
Start over from scratch, with Magisk Canary build - doesn't appear to be any improvements to MagiskHide according in current release notes
Is this possible to achieve?

composition said:
Is this possible to achieve?
Click to expand...
Click to collapse
SafetyNet:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
Google I believe is using hardware-backed CTS profiling, which Magisk cannot circumvent. Your only chance of passing CTS is to hope Google ISN'T using the hardware-backed version, so you can employ one of the workarounds I gave in the link above.

There is a setting in magisk manager that let's you switch the attestation check. I'm having a brain fart as to where it is atm but I'll poke around and if/when I find it, I'll reply again.

Larzzzz82 said:
There is a setting in magisk manager that let's you switch the attestation check. I'm having a brain fart as to where it is atm but I'll poke around and if/when I find it, I'll reply again.
Click to expand...
Click to collapse
Apparently we're both having brain farts. I didn't even think there was such a setting. Then again, I don't use Google Pay.

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 [rooted device] Galaxy wear 4 not connecting

I was recently able to root my Oneplus 9 Pro, after getting all my data back on getting my device at least usable I decided to try and set back up my watch. I keep being unable to connect. I've blocked galaxy manager/wear from magisk and I've hit a brick wall any advice?

drybonesification said:
I was recently able to root my Oneplus 9 Pro, after getting all my data back on getting my device at least usable I decided to try and set back up my watch. I keep being unable to connect. I've blocked galaxy manager/wear from magisk and I've hit a brick wall any advice?
Click to expand...
Click to collapse
you most likely need to hide magisk from more (or all) google related apps and services on your device. had the same issue with me. i'm pretty google based sign in would also not be working for you in this situation. the solution for me was to re rehide magisk from everything.

That's what I originally thought and was racking my head against it. This is the only this I can't get working post root. I saw Samsung devices have a Bluetooth patch when searching but no universal patch, at least I can't find one

drybonesification said:
That's what I originally thought and was racking my head against it. This is the only this I can't get working post root. I saw Samsung devices have a Bluetooth patch when searching but no universal patch, at least I can't find one
Click to expand...
Click to collapse
is safetynet passing for you?

Seems to be so, everything other then my gear manager is working as intended

For me on a13 the galaxy wear app just crashes while trying to connect (non root)