Related
Certified Device/SafetyNet "CTS profile mismatch" with LineageOS 14.1 and Magisk 12.0
Edit: My motivation is that I want use apps which checks Google Certified Device status and existing root. For example Netflix or Banking Apps (just examples for apps that are performing those kind of checks).
I have a Samsung Galaxy Tab 10.1 WiFi (SM-T520, picassowifi, n2awifi).
I have LineageOS 14.1 (lineage-14.1-20170518-nightly-n2awifi-signed.zip) in combination with OpenGApps (open_gapps-arm-7.1-nano-20170525.zip) and Magisk (v12) installed on the tablet.
In the Magisk settings I have...
BusyBox: disabled
Magisk Core Only Mode: disabled
Magisk Hide: Enabled
Systemless host file: Enabled
SuperUser Access: Apps and ADB
WIth "Magisk Hide" I have activate every app that Magisk Hide shows me with the app selection.
I have restartet my tablet.
I have startet Magisk Manager app and run the SafetyNet check... it shows up the error: "CTS profile mismatch".
I have startet Google Play store app and within Play store app settings the "Device Certification" status is "Not certified".
Using the very same installation procedure from my tablet, my smartphone (OnePlus 3T) showed me a green "SafetyNet passed" status. I had to install a Magisk module dedicated for my OP3T to "fix" the Google Play store certification check.
The current situation leads to two questions:
How to pass SafetyNet check?
How to "fix" Google Play store device certification check?
Edit: "Developer Mode/Tools" and ADB are disabled.
It may not help you too much but I was able to get Super Mario Run, an app notorious for not working if safety net isn't working correctly, to work by uninstalling all interations of supersu completely and then installing the latest v13 beta of Magisk. I still get the "CTS Profile Mismatch" but when using the hide option, Mario Run started working again when it wouldn't even load before. Make a TWRP backup before you change anything though.
My company is now enforcing and managing BYOD with AirWatch. I'm trying to enrol my Magisk-rooted Pixel 2 XL. I've searched around XDA and other sites and I was able to enrol the phone when I use Magisk Hide to hide from the AirWatch agent, aka now the Intelligent Hub. It creates a Work profile and installed several work related apps. The only other app aside from Intelligent Hub I've tested so far is Boxer and it works for the few minutes during my test.
When I say Boxer works for a few minutes, that is because next I attempted to open Workspace One. As it loads, I'm guessing it checks other details about the phone, then it would popup a message saying Work apps and profile removing because the device is "compromised" and uninstall the work apps and Word profile.
I would like to use Magisk Hide and hide from Workspace One app, but Magisk Hide doesn't even list that and other apps in the Work profile. An admin at work checked the AirWatch server and it shows the device compromised detection with the status "Malicious file found - Check files in system or exec folder".
So my question is, outside of troubleshooting step by step from wiping phone and setting up each thing from scratch, anyone else have an insight on what else I can check?
FYI, these are the following setup I have on my phone
- Pixel 2 XL
- Rooted with latest version of Magisk and Manager
- Latest Pie 9.0 Aug 2019 Update
- Magisk Modules Installs: Busybox, Viper4Android
- Apps with Root Access: AdAway, BetterBatteryStats, Franco Kernel Manager, Material Terminal, Titanium Backup
s0l1dsn8k3 said:
My company is now enforcing and managing BYOD with AirWatch. I'm trying to enrol my Magisk-rooted Pixel 2 XL. I've searched around XDA and other sites and I was able to enrol the phone when I use Magisk Hide to hide from the AirWatch agent, aka now the Intelligent Hub. It creates a Work profile and installed several work related apps. The only other app aside from Intelligent Hub I've tested so far is Boxer and it works for the few minutes during my test.
When I say Boxer works for a few minutes, that is because next I attempted to open Workspace One. As it loads, I'm guessing it checks other details about the phone, then it would popup a message saying Work apps and profile removing because the device is "compromised" and uninstall the work apps and Word profile.
I would like to use Magisk Hide and hide from Workspace One app, but Magisk Hide doesn't even list that and other apps in the Work profile. An admin at work checked the AirWatch server and it shows the device compromised detection with the status "Malicious file found - Check files in system or exec folder".
So my question is, outside of troubleshooting step by step from wiping phone and setting up each thing from scratch, anyone else have an insight on what else I can check?
FYI, these are the following setup I have on my phone
- Pixel 2 XL
- Rooted with latest version of Magisk and Manager
- Latest Pie 9.0 Aug 2019 Update
- Magisk Modules Installs: Busybox, Viper4Android
- Apps with Root Access: AdAway, BetterBatteryStats, Franco Kernel Manager, Material Terminal, Titanium Backup
Click to expand...
Click to collapse
The following works but I am not sure if all the steps are crucial and which ones may be superfluous. Those instructions in (parentheses) may be not necessary).
I am not a programmer (Basic on a C-64 doesn't count, I take it), don't know anything about computer architectures etc., just able to follow instructions and wrap my mind around them to tweak my devices.
The main part is to "Hide Magisk Manager" after Boxer is installed (but before it is opened/setup) as that also creates another Magisk app (instance?) with the new name for the work profile where Boxer etc. show up and can be hidden with Magisk Hide.
The other (first) part is to hide anything that would alert and conflict with Hub before or during setting up the work profile - I pretty much hid everything under Magisk Hide...
I don't know BYOD nor Workspace One, so the solution below may not work.
- uninstall Hub (that's the only app remaining after the auto-uninstall, right?)
- if Magisk Manager is already hidden: go to Settings\Restore Magisk Manager "with original package and app names" - that seems to be important, as hiding it later and with another name will then also create a Work Profile where one can see and click and hide the work profile apps such as Boxer (not sure if it works the other way around, i.e. starting off hidden with a different name and then later restoring to original will create a Magisk work profile)
- Magisk Hide: click almost every system app, not just the Google ones, but almost everything, camera, calendar, contacts etc. and your phone maker's versions as well (not sure what is necessary, but only Google system apps didn't seem to do it...), also all root and SU related apps like BusyBox etc. (not sure what Hub looks for)
(- System\Apps > clear storage data for Google Play Store and other Play Apps, also make sure Hub is really uninstalled. If not or having problems at least clear data storage as well)
- reboot (can also go into TWRP and wipe cache/Dalvik, not sure if necessary)
- install Hub, don't open it
- open Magisk, go to Magisk Hide: click Hub
(- close Magisk)
(- reboot)
- open Hub, let setup run its course creating the work profile
- if there are conflicts showing in Hub (and/or on your employer's MDM website for your device), e.g. root certificate not installed, don't install any apps yet such as Boxer etc. and reboot instead
- Are those conflicts resolved after reboot?
- install Boxer and other apps (trough Hub itself, MDM website push (or Google Play)) but don't open/start them
(- reboot)
- open Magisk, go to Settings\Hide Magisk Manager and click on it, pick a name and confirm: this will then change the name of Magisk AND create a another Magisk app (with the new name) for the work profile.
- open that new Magisk work profile and go to Magisk Hide: click Boxer (and other apps controlled by Hub); Hub itself and everything already hidden in the private (= non-work) profile Magisk app should show up here as already hidden. Double and triple check.
(- reboot)
- open Boxer and start set-up
That's it. Stable, even after another reboot.
Did this solution work for you @s0l1dsn8k3?
I am in a similar boat. @s0l1dsn8k3 please let me know if you found an alternate solution.
I am in a similar boat. @s0l1dsn8k3 please let me know if you found an alternate solution.
I can't use a credit card via google pay. Google pay writes that I have a root device even though it is marked in magisk in exceptions.
Magisk show - safety net verification error.
Please help.
Thanks
jkmaxfli said:
I can't use a credit card via google pay. Google pay writes that I have a root device even though it is marked in magisk in exceptions.
Magisk show - safety net verification error.
Okrasné help.
Thanks
Click to expand...
Click to collapse
You have to hide it fully in magisk. And then reboot
Are you using stock rom? Or any other custom rom? If you can't pass safetynet, Magisk hide doesn't "hide", so we have to locate the error.
I using Stock Rom.
Fully hide, reboot And nothing change.
Flash magisk module and you will be ok
https://github.com/kdrag0n/safetynet-fix/releases/download/v1.1.1/safetynet-fix-v1.1.1.zip
In Google Play:
Certification play protect - the device is not certified.
what should I do with it now
hexisg said:
Flash magisk module and you will be ok
https://github.com/kdrag0n/safetynet-fix/releases/download/v1.1.1/safetynet-fix-v1.1.1.zip
Click to expand...
Click to collapse
Thanks ill try it
after flashing the module test your safetunet status.
after clear data of Goole Play Store , google Services and google Pay.And you should be good to use Google Pay.
Safety net is successful, Google play is also successful, but the payment card cannot be added - error:
request failed - transaction could not be performed. When adding a credit card.
Edit:
...the current credit card cannot be removed, it is said to be associated with some one payment method. I wanted to try removing it completely and signing in again. :-(
jkmaxfli said:
Safety net is successful, Google play is also successful, but the payment card cannot be added - error:
request failed - transaction could not be performed. When adding a credit card.
Edit:
...the current credit card cannot be removed, it is said to be associated with some one payment method. I wanted to try removing it completely and signing in again. :-(
Click to expand...
Click to collapse
Try deleting all data a of Google Play Services and Google Pay app, restart the phone, and try if you u can do it now
I tried that, unfortunately no change.
Try this:
Working: Magisk with Google Pay as of gms 17.1.22 on Pie
Ok. I tried this and it worked on gms 17.1.22, allowing one to add cards and pay in store. Warning YMMV, but this is the process I did to get this working. One caveat is that I suspect users will have to reverse some step if gms is updated and...
forum.xda-developers.com
Release GPay SQLite Fix v2.4 · stylemessiah/GPay-SQLite-Fix
Changes to service.sh: -Fixed broken/mangled pipes that left the log file blank - dont ask me why If you need logging (only useful if youre having an issue and want to troubleshoot) you can choose ...
github.com
UnderscoreKer said:
Try this:
Working: Magisk with Google Pay as of gms 17.1.22 on Pie
Ok. I tried this and it worked on gms 17.1.22, allowing one to add cards and pay in store. Warning YMMV, but this is the process I did to get this working. One caveat is that I suspect users will have to reverse some step if gms is updated and...
forum.xda-developers.com
Release GPay SQLite Fix v2.4 · stylemessiah/GPay-SQLite-Fix
Changes to service.sh: -Fixed broken/mangled pipes that left the log file blank - dont ask me why If you need logging (only useful if youre having an issue and want to troubleshoot) you can choose ...
github.com
Click to expand...
Click to collapse
Dont work :-(
So for now, to sum it up:
magisk safety net is pass-ok.
In magisk I have two fix modules (screenshots) and google pay adding a credit card still not working. Still error OR-TAPSH-08.
I also read on the net that it helped someone wait 1 day and then the payment card went to add.
Next:
when I run clean and select the security check, it turns out to me that there is a problem in the payment environment.(screenshots)
jkmaxfli said:
Dont work :-(
So for now, to sum it up:
magisk safety net is pass-ok.
In magisk I have two fix modules (screenshots) and google pay adding a credit card still not working. Still error OR-TAPSH-08.
I also read on the net that it helped someone wait 1 day and then the payment card went to add.
Next:
when I run clean and select the security check, it turns out to me that there is a problem in the payment environment.(screenshots)
Click to expand...
Click to collapse
Not trying to be mean or anything but, have you enabled magisk hide?
Uninstall universal safety net fix first and restart.
IMPORTANT: Make sure that you are running the latest version of magisk.
Make sure hide is on and you have selected all core Google services and gpay.
Then install magiskhide props config and restart.
Install an command terminal from the play store and type "props". You may have to enter "su" first.
Type "1" then “f”
Then follow the steps to select your phone model.
Then apply the fingerprint and restart.
If you cannot find your phone model, then ignore this step.
Go into magisk settings and click on the option to hide the magisk app. The app should reinstall itself under the "settings" name.
Restart again.
Then, turn data and WiFi off, go into settings and clear the storage/data of all Google apps and especially Google play services. Then just reflash the gpay fix (DON'T RESTART). Turn connection back on and try to add your cards as well as any nfc setup for those cards.
Then restart your phone.
Then go into Google play store, and into settings, and ensure that the device is certified.
This allowed me to get gpay working, however, I'm running a custom rom though.
You may want to carry your cards physically in case the phone doesn't work for the first month or so.
Hello.
I have a magisk hide.
For the item google services framework, if I check, after leaving and re-entering the already checked google services framework is not, the check mark does not hold.(screenshot)
jkmaxfli said:
Hello.
I have a magisk hide.
For the item google services framework, if I check, after leaving and re-entering the already checked google services framework is not, the check mark does not hold.(screenshots)
Click to expand...
Click to collapse
Hi, sorry, I had to edit my reply several times.
Just enable them all just in case. For the 2nd screenshot, enable the hide thing. I have it enabled so the option says to restore it.
For the services framework bugthing, ignore it. The gpay fix was the one that added it. Just expand it and ensure its on
I'll try it all, thank you. I'll get back to you today
I'm tangled in it, you wrote a lot. Please send me one more steps 1 to ..... Thank you very much
!!!!!!!!!!!!!!!!!!!!!!!!! Dude, you're really a giant, it all works !!!!!!!!!!!!!!!!!!!!!!!
Safety net in magisk PASS.
Google play store - device is certified.
Credit card added successfully.
Tomorrow I will try payment using a mobile phone and NFC and see if it is fully functional.
I'll let you know tomorrow if the payments are working.
BIG BIG thanks
Is there some way to get back MagiskHide functionality now that it's not supported in core?
I have 23016 installed (for latest p6xl)
Fry-kun said:
Is there some way to get back MagiskHide functionality now that it's not supported in core?
I have 23016 installed (for latest p6xl)
Click to expand...
Click to collapse
It's unnecessary as zygisk works fine to hide apps.
Ooh, I will try that!
Fry-kun said:
Is there some way to get back MagiskHide functionality now that it's not supported in core?
I have 23016 installed (for latest p6xl)
Click to expand...
Click to collapse
In addition to what @jlokos said about using the deny list, the Alpha version of Magisk by vvb2060 still has the Magisk Hide function I believe. Just another option...
Lughnasadh said:
In addition to what @jlokos said about using the deny list, the Alpha version of Magisk by vvb2060 still has the Magisk Hide function I believe. Just another option...
Click to expand...
Click to collapse
I have SafetyNet fix & Zygisk denylist, and it's working for Play store.
It looks like some apps are not happy with Zygisk, though, namely amazon app store (appears to detect root)
Will try vvb2060's, is this it?
Further fix `oplus.fstab` support · vvb2060/[email protected]
A Magic Mask to Alter Android System Systemless-ly - Further fix `oplus.fstab` support · vvb2060/[email protected]
github.com
Hmm not quite, not sure if it includes that yet this one doesn't but the code is in master, looking around
Fry-kun said:
I have SafetyNet fix & Zygisk denylist, and it's working for Play store.
It looks like some apps are not happy with Zygisk, though, namely amazon app store (appears to detect root)
Will try vvb2060's, is this it?
Further fix `oplus.fstab` support · vvb2060/[email protected]
A Magic Mask to Alter Android System Systemless-ly - Further fix `oplus.fstab` support · vvb2060/[email protected]
github.com
Hmm not quite, not sure if it includes that yet this one doesn't but the code is in master, looking around
Click to expand...
Click to collapse
This is the latest (from Telegram group). Join the Telegram group to keep up with latest. Can't give a link b/c it's not allowed.
Latest seems to include the MagiskHide cleanup, and amazon appstore is detecting root
Did you clear data and cache of the ama appstore?
stroke55 said:
Did you clear data and cache of the ama appstore?
Click to expand...
Click to collapse
Yup
Edit: and there are no extra settings for MagiskHide, how is this supposed to be different?
I installed Jeff's crappy appstore, selected it in Magisk Alpha's 23016 hiding list, was able to start it without any root-detection-message and uninstalled it instantly thereafter So it should work. What do mean by extra settings for Magisk hide? I just selected it in the hiding list.
To clarify, the app store starts but hides some apps if it detects root.
Play store does the same if it detects root (currently doesn't, thanks to safety net fix). For instance, Netflix, Pokemon Go, etc..
Also noticed Netflix & such are unable to start with "Sign in ... with your saved password" flashing like crazy & unable to actually sign in.
logcat says
12-16 21:31:18.375 1505 3393 W InputManager-JNI: Input channel object 'aeeda26 com.google.android.gms/com.google.android.gms.auth.api.credentials.assistedsignin.ui.AssistedSignInActivity (client)' was disposed without first being removed with the input manager!
This is very likely a different issue... but present with 23016 canary.
Maybe I should try to reflash & try fresh
Fry-kun said:
Is there some way to get back MagiskHide functionality now that it's not supported in core?
I have 23016 installed (for latest p6xl)
Click to expand...
Click to collapse
Hmm ... you must have done something wrong ... hiding works fine for me. I would suggest to:
- remove all magisk modules (and reboot)
- re-patch boot.img and download to PC
- in the Magisk app, click 'Magisk deinstall
- reboot (no root now)
- reboot to bootloader
- flash patched boot.img
- reboot
- re-install Magisk app, 'hide' the app in settings
- enable zygisk
- configure denylist, make sure that when you select an app you also select ALL services underneath it for hiding
- install USNF 2.2.0
Now check your root detection apps, they should work.
Netflix should also work (clear cache for Play Store and Google Play-services)
All is working fine for me.
I just factory reset, reinstalled magisk, added a plain account (no copy apps from old phone), enabled zygisk, added USNF, hid magisk.
Installed YASNAC (passed), reset storage for Play Store (device is now certified), installed Netflix.
Added Netflix to denylist, reset Netflix storage.
Opening Netflix -- still infinite loop of gray "Sign in ... with your saved password" at the bottom.
Pixel 6 Pro, sq1d firmware. Magisk canary (23016)
Aside, adding Google Play-services to denylist doesn't survive a reboot. There are "denylist rm" entries in the log after safetynet-fix, maybe it removes those..?
Fry-kun said:
I just factory reset, reinstalled magisk, added a plain account (no copy apps from old phone), enabled zygisk, added USNF, hid magisk.
Installed YASNAC (passed), reset storage for Play Store (device is now certified), installed Netflix.
Added Netflix to denylist, reset Netflix storage.
Opening Netflix -- still infinite loop of gray "Sign in ... with your saved password" at the bottom.
Pixel 6 Pro, sq1d firmware. Magisk canary (23016)
Aside, adding Google Play-services to denylist doesn't survive a reboot. There are "denylist rm" entries in the log after safetynet-fix, maybe it removes those..?
Click to expand...
Click to collapse
You should not add Google play services to denylist !
Then clear Netflix cache again, reboot ... try again ...
foobar66 said:
You should not add Google play services to denylist !
Then clear Netflix cache again, reboot ... try again ...
Click to expand...
Click to collapse
I tried it with no Play Services, and clearing Netflix storage, same thing.
This is happening specifically when my google account is on the phone and it has a saved Netflix login info.
Also tried with SD1A fw from Nov., same thing.
I tried removing the saved pw - everything is fine, Netflix works.
Re-saved the pw after logging in, logged out & opened Netflix again -- same issue (see attached)
In other words, it's not really Netflix that's the problem...
Fry-kun said:
I tried it with no Play Services, and clearing Netflix storage, same thing.
This is happening specifically when my google account is on the phone and it has a saved Netflix login info.
Also tried with SD1A fw from Nov., same thing.
I tried removing the saved pw - everything is fine, Netflix works.
Re-saved the pw after logging in, logged out & opened Netflix again -- same issue (see attached)
In other words, it's not really Netflix that's the problem...
Click to expand...
Click to collapse
When you log out of Netflix (from within the app; click profile icon upper right; then 'log out') do you then get the app's login screen? If yes, can you log in properly on that screen?
Only other suggestion which I have is: log out of Netflix from a browser/web. Remove your Netflix password from your Google account (also on the web). Login on Netflix (browser), save password again in your Google account. Then try again on Android/phone.
Will try..
Meanwhile, apparenly Amazon app may just be garbage: https://www.theverge.com/2021/12/1/22811710/amazon-android-12-appstore-drm-issues
Fry-kun said:
Will try..
Meanwhile, apparenly Amazon app may just be garbage: https://www.theverge.com/2021/12/1/22811710/amazon-android-12-appstore-drm-issues
Click to expand...
Click to collapse
Amazon app works for me, just ordered Spigen cover, screen protector and lense protector all from Spigen on Amazon.
My banking app dont even like developer settings enabled or root or root hiding at all, can even see i have bootloader unlocked, so i am forced to live with no root through.
Fry-kun said:
Will try..
Meanwhile, apparenly Amazon app may just be garbage: https://www.theverge.com/2021/12/1/22811710/amazon-android-12-appstore-drm-issues
Click to expand...
Click to collapse
I had a heck of a time with the Amazon app but it didn't have anything to do with root. Was adaway. Had to run the log and white list a few things now it's good to go.
Hi,
I installed microG Lineage 20 on my Moto G 5G Plus. Everything works fine except that one (banking) app that complains that "Google Play Services are not Installed".
I assume that means SafetyNet?
I tried to get it to work using the path depicted here: https://forum.xda-developers.com/t/safetynet-on-lineageos-20-microg.4558065/, but no luck on this phone.
Is there anyway to get safety net to pass, ideally without rooting the phone/using magisk?
EDIT: there's a switch in the microG settings "Allow Device Attestation" but it's greyed out ...
Best,
N
Ok, first of all, you have to enable "Device Registration" in the microG settings. Didn't know that.
That way, I got to the point where I can check for device attestation, and get the notorious "CTS Profile Doesn't Match" error.
I've tried using Magisk and Zygisk, and the Univesal SafetyNet fix, but to no avail, still not passing.
EDIT: tried the modded universal safety net fix by displax, not the check says "integrity check failed" ... not sure whether I sould count that as progress or not
Hi,
I had the same problem, but I found the solution and now I successfully pass safetynet with LOS 20 microG.
You have to do 3 steps:
Enable zygisk in Magisk and configure denylist to hide root from 'microG Services Core'
Enable 'Device Registration' and 'Google SafetyNet' at microG settings
Install Magisk module MagiskHidePropsConf, reboot, then configure it in any Terminal Emulator as follows:
su (start root shell)
props (run props command line tool)
1 (edit device fingerprint)
f (choose from the list)
select any fingerprint you like, then proceed and reboot
This third step solves CTS profile mismatch error by changing the device's fingerprint to one trusted by Google.
It should work.
Edit: I did not use any 'Universal SafetyNet fix' module.
Hmm ok, I have read about it but never tried, as the page states is a deprecated project ... That'd probably mean I'd have to install an older version of Magisk, right ?
Hmm... I haven't noticed yet. Good to know.
It's working fine for me with the latest Magisk version.