Cant get safetynet working. But only with this kernel - Magisk

Hello. Im user of nexus 5 with this kernel: Click!
And paranoid android 7.2.3 rom
And i cant pass safetynet no matter what i try :/
Tried:
1.Removing and reinstalling magisk
2.patching bootimg
3.reinstalling kernel
It still cant pass. Even basicintegrity.
When i flash stock paranoid kernel it pass without any problems. Why?
It was working on attached kernel, but suddenly, just stopped.
Help please

Why not provide a link to the kernel thread instead? I don't want to download any unknown files...
I did search for the kernel though, and saw this in the feature list:
Disabled more stuff of debugging
Click to expand...
Click to collapse
MagiskHide uses Android's logging functions to monitor what apps and services to hide from. If this has been switched off, MagiskHide won't work and SafetyNet will trigger.
If that's what the above mentioned feature means, you might be able to turn on logging again with a kernel management app like Kernel Adiutor.

thanks a lot!

Related

Magisk safety net fails not sure why.

Hi
I'm using a Samsung Galaxy S4
I rooted the stock Samsung rom with SuperSU prior to install Magisk
At first I couldn't install 13.3 I had to install 12.0 because of some unknown reason installing 13.3 I got the error image mount failed same with all previous 13. versions however now 13.3 is now installed and SuperSU isn't installed.
When I run the SafetyNet Check in Magisk it reports:
ctsProfile: false
basicIntegrity: false
I want to be able to use apps like Android pay and such
Can someone please help me with getting this to work
Thanks!
Magisk v12.0 can't pass SafetyNet without workarounds like Universal SafetyNet fix module (and since the last update to SafetyNet a few days ago I've no idea if that works either).
You can't use Magisk to pass SafetyNet with SuperSU installed.
Here's some reading for you:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Pro tip: Try using the search function and browse the stickied threads before posting. There are very few things that hasn't been covered already in one way or another...
Didgeridoohan said:
Magisk v12.0 can't pass SafetyNet without workarounds like Universal SafetyNet fix module (and since the last update to SafetyNet a few days ago I've no idea if that works either).
You can't use Magisk to pass SafetyNet with SuperSU installed.
Here's some reading for you:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Pro tip: Try using the search function and browse the stickied threads before posting. There are very few things that hasn't been covered already in one way or another...
Click to expand...
Click to collapse
I've got 13.3 installed and SuperSU isn't installed plus I've already read a lot on this subject and most of my searches did nothing for me that's why I thought I would make a thread to see if anyone could help me.
AyanamiRei0 said:
I've got 13.3 installed and SuperSU isn't installed plus I've already read a lot on this subject and most of my searches did nothing for me that's why I thought I would make a thread to see if anyone could help me.
Click to expand...
Click to collapse
That was not very clear from your first post...
If you haven't already, start by reading through the link I posted. You wan't post #4.
Didgeridoohan said:
That was not very clear from your first post...
If you haven't already, start by reading through the link I posted. You wan't post #4.
Click to expand...
Click to collapse
Interesting trying to start magiskhide manually does nothing.
You could have remnants of Su on your phone. Even if you use the full uninstall method you can have leftovers. Tried a complete fresh reinstall?
phuhcue said:
You could have remnants of Su on your phone. Even if you use the full uninstall method you can have leftovers. Tried a complete fresh reinstall?
Click to expand...
Click to collapse
Oh it's working fine now installing Lineage OS and then install Magisk and it works perfectly.
With me my experiments with magisk in the past left some files in my data partition behind which makes safetynet fail.
I found them by going into twrp recovery, starting and adb shell and then executing find . | grep -i magisk
the two files i found were:
data/data/com.google.android.gms/files/backup_diff_script/com.topjohnwu.magisk
data/property/persist.magisk.hide
i deleted them with rm and safety net worked again.
So I can confirm that for my phone, unlocked bootloader, custom modem and custom recovery does not matter at all. But if your filesystem still contains traces of magisk, is a nono for google safetynet, pretty silly this road they are taking here.
safety net
i have the same problem on galaxy note 3 with magisk 15.3 on my galaxy s7 everything is ok but in note 3 i have safety net false...
can anyone help me?
spanpana said:
i have the same problem on galaxy note 3 with magisk 15.3 on my galaxy s7 everything is ok but in note 3 i have safety net false...
can anyone help me?
Click to expand...
Click to collapse
Old device... If the kernel version is lower than 3.8 it'll likely not have support for mount namespace and MagiskHide won't work. A custom kernel or ROM might work...
Didgeridoohan said:
Old device... If the kernel version is lower than 3.8 it'll likely not have support for mount namespace and MagiskHide won't work. A custom kernel or ROM might work...
Click to expand...
Click to collapse
thank's for your reply...!
i have custom rom resurection remix v.5.8.2 but i didnt change the kernel can you explain me how to do that please because i don't know...?
spanpana said:
thank's for your reply...!
i have custom rom resurection remix v.5.8.2 but i didnt change the kernel can you explain me how to do that please because i don't know...?
Click to expand...
Click to collapse
Check your kernel version first (usually found in Settings - About Phone). If it's less than 3.8, ask for help in your device's forum for if there's any custom kernels or ROMs available with an updated kernel.
Didgeridoohan said:
Check your kernel version first (usually found in Settings - About Phone). If it's less than 3.8, ask for help in your device's forum for if there's any custom kernels or ROMs available with an updated kernel.
Click to expand...
Click to collapse
ok my friend thank you very much...!:laugh::good:
Didgeridoohan said:
Old device... If the kernel version is lower than 3.8 it'll likely not have support for mount namespace and MagiskHide won't work. A custom kernel or ROM might work...
Click to expand...
Click to collapse
That's interesting. I get the same message on my old phone (running the 3.4.113 kernel), but I'm unable to even open Mario Run if MagiskHide is disabled. But when it's enabled, the game runs just fine. Is that normal? I thought Mario Run made use of SafetyNet... I'm using microG + DroidGuard Helper. I've tried running Android Pay, but I get this error message. But I'm not even sure if Android Pay is supposed to work since I'm using microG... What other apps use SafetyNet so I can try them?
Thanks.
robotsrules said:
That's interesting. I get the same message on my old phone (running the 3.4.113 kernel), but I'm unable to even open Mario Run if MagiskHide is disabled. But when it's enabled, the game runs just fine. Is that normal? I thought Mario Run made use of SafetyNet... I'm using microG + DroidGuard Helper. I've tried running Android Pay, but I get this error message. But I'm not even sure if Android Pay is supposed to work since I'm using microG... What other apps use SafetyNet so I can try them?
Thanks.
Click to expand...
Click to collapse
MagiskHide can't do it's thing to hide itself on such an old kernel, but it can still hide sensitive prop values. That's why Mario Run works... IIRC it looks for ro.debuggable, on of the props changed to "safe" values by MagiskHide.
Didgeridoohan said:
MagiskHide can't do it's thing to hide itself on such an old kernel, but it can still hide sensitive prop values. That's why Mario Run works... IIRC it looks for ro.debuggable, on of the props changed to "safe" values by MagiskHide.
Click to expand...
Click to collapse
Oh, I get it now... Thanks

Pass SafetyNet with Xposed?

I've been reading several threads here and in other forums as well, and I still not sure if this is possible at all, or it depends on the Xposed modules, etc.
I'm planning to do a clean install of the RR ROM, 6.0.1, try to remove all traces of root, then flash magisk and see if I can pass SafetyNet.
Does a custom kernel interfieres with that?
And if I pass it... any possibility to use Xposed (being active) and pass SafetyNet? Or at least hide it for problematic apps, like Netflix, or Mario Run?
Thanks in advance.
No, Xposed and SafetyNet is a no-go for now.
If you have a device, which ROM has security patches older than November 2016, you may try to use suhide along with Magisk and its MagiskHide, but no guarantees.
The ROM I plan to use is from september, you mean with suhide maybe SafetyNet could pass with Xposed enabled?
Thanks!
eXtremeDevil said:
I've been reading several threads here and in other forums as well, and I still not sure if this is possible at all, or it depends on the Xposed modules, etc.
I'm planning to do a clean install of the RR ROM, 6.0.1, try to remove all traces of root, then flash magisk and see if I can pass SafetyNet.
Does a custom kernel interfieres with that?
And if I pass it... any possibility to use Xposed (being active) and pass SafetyNet? Or at least hide it for problematic apps, like Netflix, or Mario Run?
Thanks in advance.
Click to expand...
Click to collapse
With Xposed Safetynet gone.
But you can use no device check module to pass ctsProfile True. But you can't anything about basicintegrity.
the ctsProfile in important. This mean you can play super Mario run or use Netflix in your device. But because of the basicintegrity you can't download or update this app from play store. You can download from apkmirror site.
Netflix and super Mario run in my phone.
Sent from my HTC U11 using Tapatalk
arianat said:
With Xposed Safetynet gone.
But you can use no device check module to pass ctsProfile True. But you can't anything about basicintegrity.
the ctsProfile in important. This mean you can play super Mario run or use Netflix in your device. But because of the basicintegrity you can't download or update this app from play store. You can download from apkmirror site.
Netflix and super Mario run in my phone.
Sent from my HTC U11 using Tapatalk
Click to expand...
Click to collapse
Let's see if I understood it correctly. Can I have custom ROM + Magisk + SuperSU + custom kernel + Xposed active and with this module I can use that kind of apps?
Thanks!
eXtremeDevil said:
Let's see if I understood it correctly. Can I have custom ROM + Magisk + SuperSU + custom kernel + Xposed active and with this module I can use that kind of apps?
Thanks!
Click to expand...
Click to collapse
Yes. I have custom kernel on ViperU 1.7 custom Rom in HTC U11
but I think you can't use superSu with magisk. You must use one of them. Why you want superSu? Magisk has superuser
Just install Xposed and install no device check module in Xposed installer
Sent from my HTC U11 using Tapatalk
arianat said:
Yes. I have custom kernel on ViperU 1.7 custom Rom in HTC U11
but I think you can't use superSu with magisk. You must use one of them. Why you want superSu? Magisk has superuser
Just install Xposed and install no device check module in Xposed installer
Sent from my HTC U11 using Tapatalk
Click to expand...
Click to collapse
I use an older Magisk that supports SuperSU. If I need newer Magisk for this to work, or if the module doesn't work with SuperSU, please let me know.
Thanks!
Best way really is root switch, requires reboot and disables xposed bit gets the job done.
kekistaneerefugee said:
Best way really is root switch, requires reboot and disables xposed bit gets the job done.
Click to expand...
Click to collapse
I don't want to be disabling Xposed and rebooting everytime...
eXtremeDevil said:
I use an older Magisk that supports SuperSU. If I need newer Magisk for this to work, or if the module doesn't work with SuperSU, please let me know.
Thanks!
Click to expand...
Click to collapse
The module worked with superuser and superSu
I tested
Sent from my HTC U11 using Tapatalk
Great, thanks, for now I will try MagiskSU. Just flashed ROM, removed su and SN passed. But installed boeffla kernel and not anymore. Is it normal? Can I avoid that? Gonna flash Magisk 13.3 now and check.
Thanks for everything guys!
Never mind, got SN again. But after installing Xposed systemless 87 I get bootloop Any idea why? Or is it really a very long boot? I have no Xposed modules at the time, just trying to boot it.
EDIT
Thanks to liveboot, I can see a boot error: Xposed: Can't find file.
Any clues???
Try install classic. If you don’t want disable xposed for pass basicintegrity , no need to install system less. Systemless xposed not active in my phone and I installed classic.
What’s your device? Do you wipe delvik & cache?
I flashed systemless Xposed from recovery and that did the trick.
If disabled, I pass SN. With the No device check module I pass cts profile.
But, Netflix does not work with that configuration. Maybe that app has extra checks? Thanks.
Sent from my ONE A2003 using Tapatalk
eXtremeDevil said:
I flashed systemless Xposed from recovery and that did the trick.
If disabled, I pass SN. With the No device check module I pass cts profile.
But, Netflix does not work with that configuration. Maybe that app has extra checks? Thanks.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
What's do you mean extra configuration?
It's must work with pass ctsProfile. Just you can't update or download from play store.
Do you downloaded last version of Netflix for your device dpi and CPU architect from apkmirror?
Sent from my HTC U11 using Tapatalk
With Xposed disabled, and SafetyNet passing at 100%, Netflix says that my device is not compatible. Even installed from Google Play.
BTW, Mario Run only works if Magisk Hide is enabled for it, I guess that's normal (with Xposed active this time)
Thanks for all the clarifications, now I have a better understanding of it all
I guess this is the cause?
https://www.reddit.com/r/netflix/comments/69l2fp/all_netflix_no_longer_available_to_android/
Can anyone confirm?
Thanks!
eXtremeDevil said:
With Xposed disabled, and SafetyNet passing at 100%, Netflix says that my device is not compatible. Even installed from Google Play.
BTW, Mario Run only works if Magisk Hide is enabled for it, I guess that's normal (with Xposed active this time)
Thanks for all the clarifications, now I have a better understanding of it all
Click to expand...
Click to collapse
I don't know why Netflix not work for you. I have Netflix in my phone and using every day.
What's your phone Android build?
Netflix must work on your phone.
I have U11 and installed viperU magisk version custom rom. Android 7.1.1 and August patch.
Custom kernel and classic PurifyOS Xposed with so much modules like xprivacy, appsetting, hush sms, no device check , location report enabler, chromepie, native clipboard, and ...
Sent from my HTC U11 using Tapatalk
I have Resurrection Remix 6.0.1 from september 2016.
Is there a log or something where I can check what is cause Netflix refusal to work?
Do you have Magisk Hide enabled for those apps?
Thanks.
EDIT
Actually, Mario Run is now giving me the code error screen
CTS profile is passing.
EDIT 2
Additional info:
Super Mario Run works fine only for two levels, then is error 804-5100.
Netflix above version 4 (5 and later) says it is incompatible with my device.
- Both appear on Play Store.
- Store version is 8.1.73, installed this afternoon and cleared data.
- Bootloader is unlocked (maybe I should try to relock?).
- I can't find device verification in Play Store settings (is not there), even tried this:
https://forum.xda-developers.com/oneplus-2/help/module-fix-google-play-certification-t3602629
with no luck.
- Xposed installed with modules but disabled (from Xposed Manager).
- SafetyNet passing 100%.
- Tried both and without Magisk Hide enabled for the apps.
- Disabled superuser and enabled Magisk Core only.
- Build version: 6.0.1_r66 - MOB31E (my signature is outdated).
- I had Lucky Patcher but I uninstalled it.
- Also tried this:
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
Nothing works.
Maybe some other app(s) is being detected by Netflix? Maybe a log would help? Or a full bug report?
Is it the ROM version? Maybe is device specific? Should I open a thread on the device's forum? Am I missing something?
Thanks in advance!
EDIT 3
Android Pay seems to work. I don't have NFC, I only got to the add card screen, but I guess that's enough.
EDIT 4
Kernel is Boeffla.
you need root switch

How do you upgrade kernel version-MagiskHide not working-M3 Lite 8

Solved! 3.18 kernel is bigger than 3.8! just some bad math.
Guys, I fixed it by simply enabling logging in the ProjectMenu by using the code ()()2846579()() in the calculator, pressing Background settings and pressing log settings and ticking all the boxes. But you have to do this every boot.
donster42019 said:
Guys, I fixed it by simply enabling logging in the ProjectMenu by using the code ()()2846579()() in the calculator, pressing Background settings and pressing log settings and ticking all the boxes. But you have to do this every boot.
Click to expand...
Click to collapse
That's odd but doing that worked for my Mediapad M3 (not lite) and now it passes Safetynet. Do you know why this is, is there an article on why enabling those 3 logging items does it?
Also is your device certified on playstore or not (and are you using Magiskhide props module?)
donster42019 said:
I want to use my device so that I can use apps such as Pokemon Go or Super Mario Run with root. As I am using a rooted device with magisk, the SafetyNet check fails every time. And Huawei just decided to use a kernel version of 3.18 for EMUI 5.1. :silly: And Magisk Hide needs kernel version 3.8. Does anyone know how to fix this?
Click to expand...
Click to collapse
Try using latest Magisk Canary. Works well for me

AdAway with temp root

I have an unlocked bootloader with TA-Backup like described in this thread.
But to get my banking app working I only want ro use the stock kernal.
I use the newest firmware: G8441_47.2.A.10.28_1310-4373_R3C
Is it possible to install AdAway if I boot with a different kernal with root and activate the host files?
After a reboot the stock kernal will be used with working adaway.
Does this work?
DripleX said:
I have an unlocked bootloader with TA-Backup like described in this thread.
But to get my banking app working I only want ro use the stock kernal.
I use the newest firmware: G8441_47.2.A.10.28_1310-4373_R3C
Is it possible to install AdAway if I boot with a different kernal with root and activate the host files?
After a reboot the stock kernal will be used with working adaway.
Does this work?
Click to expand...
Click to collapse
Better option for you on that situation is to use a dns proxy for ad filtering
something like this app
https://f-droid.org/en/packages/org.jak_linux.dns66/
Yes I use a app like this, but the problem is, that sometimes it takes up to 1 - 2 min till it is connected to the DNS Server.
Have you tried if the banking app works with magiskhide and "hide magisk package name" from magisk settings?
vofferz said:
Have you tried if the banking app works with magiskhide and "hide magisk package name" from magisk settings?
Click to expand...
Click to collapse
Yes, I tried this, but as I read in some other threads, this will only work with newest Magisk.
But then I have to recompile the kernal for myself.
@DripleX, If you like to check if magisk is causing your (banking) apps to detect root, you may try this:
j4nn said:
Dear @albenex, although I would also assume it should be possible to resolve this with use of magiskhide and other settings, I've uploaded not-pre-rooted kernels for the latest fw version into my experimental folder here.
So you can clean up all traces of magisk (factory reset may be needed to be sure) and use a boot-*-47.2.A.10.45-hideunlock.img kernel to test it. Also be sure to run unmodified stock fw.
Click to expand...
Click to collapse
These kernels are not pre-rooted with magisk but include the patch to hide bootloader unlock.
That should provide you setup very close to still locked phone (if you have your TA-locked restored).
If the app is working with the *-hideunlock.img kernel, magisk would need to be made hidden to get it working with a rooted kernel.
If it did not work even with the not-prerooted kernel, it would mean BL unlock is detected some other way (most likely using your Android Attest key - assuming you have it "provisioned") as it seems to be the case with google pay.
A donation was received on Tue Apr 30 15:03:03 UTC 2019 - I assume it has been from you @DripleX.
If so, thank you.
Thank you @j4nn for your reply!
I will check this after my vacation.
And yes, I made the donation

Can't get Android 12 + Magisk + SafetyNet, no matter what... All the guides seem outdated

So I'm trying to get Android 12 working with root and SafetyNet passing. I found that all the guides to be wrong or outdated. Problem with the latest Magisk canary is that it does not support MagiskHide. Problem with the latest stable Magisk (v23) is that it doesn't support Android 12. Here are the combinations I've tried:
Canary Magisk APK, Canary Magisk boot image, with Universal SafetyNet Fix v2.2.1 (Zygisk)
Result: No way to test if safety net passes within Magisk, but it doesn't seem to work.
Canary Magisk APK, Stable Magisk v23 boot image, with Universal SafetyNet Fix v2.1.3 (Riru)
Result: Does not work. MagiskHide automatically turns off after every reboot, probably because the canary boot image does not support it.
Stable Magisk v23 APK, Stable Magisk v23 boot image
Result: Device fails to boot. fast food indicates in an invalid signature. presumably happening because stable magisk v23 does not support Android 12.
Based on these test results these are my assumptions:
1. There is no way to run Magisk 23 on Android 12, and this article and its screenshot are fake:
https://www.droidwin.com/how-to-roo...k-on-android-12/#STEP_6_Boot_to_Fastboot_Mode
and this also does not work: https://krispitech.com/how-to-pass-safetynet-on-rooted-android-12/
OR
It was possible and Android 12 September 5th patch level but somehow not the latest December build?
There is no advantage to running mismatched Magisk APK and boot image versions
Both the Zygisk and Riru versions of the SafetyNet Fix do not work on the latest Android 12 builds.
The new DenyList system does nothing in allowing a SafetyNet bypass.
The ONLY working method That can possibly bypass safety net on Android 12 is using either of these 2 Magisk forks:
Custom Magisk by TheHitMan7 (Can’t find download link)
Alpha Magisk by vvb2060 (Can’t find download link)
Are these assumptions correct? Can someone please correct my misunderstandings?
You need Universal Safetynet Fix v2.2.0 or v2.2.1 which was just released 10 days ago.
To be honest, I haven't tried v2.2.1 yet, but I would imagine it will work. I'm on v2.2.0 right now.
Get it from here: https://github.com/kdrag0n/safetynet-fix
I have been using Magisk Canary 23016, USNF 2.2.0, and MagiskHide Props Config 6.1.2 on my Pixel 5 running the December Android 12 release. SafetyNet passes, GPay works.
I have DenyList blocking both GPay and Google Play Store..
Either you have something configured wrong, or you're having a unique issue. Others have been able to pass SafetyNet using a similar configuration.
No, Magisk Stable does not currently support Android 12. You MUST use Canary 23016; none of the previous builds properly handle the vbmeta flags in the boot image header.
I'm using the latest magisk canary, USNF 2.2.1 and no magisk hide props and am passing. I have Zygisk enabled, but that's about it. Install was flawless. Followed V0latyle's thread on going from A11 to A12 when the canary update dropped.
Thank you everyone, I got it working the way you said! I was super close.
-----------------------------------
V0latyle said:
I have been using Magisk Canary 23016, USNF 2.2.0, and MagiskHide Props Config 6.1.2 on my Pixel 5 running the December Android 12 release. SafetyNet passes, GPay works.
I have DenyList blocking both GPay and Google Play Store..
Either you have something configured wrong, or you're having a unique issue. Others have been able to pass SafetyNet using a similar configuration.
No, Magisk Stable does not currently support Android 12. You MUST use Canary 23016; none of the previous builds properly handle the vbmeta flags in the boot image header.
Click to expand...
Click to collapse
I only blocked play services with deny list and it worked.
One of the guides told me to flash stock vbmeta (idk what this is), and this bricked it until I re-flashed the ROM. But I guess that's not needed anymore.
flyoffacliff said:
Thank you everyone, I got it working the way you said! I was super close.
-----------------------------------
I only blocked play services with deny list and it worked.
One of the guides told me to flash stock vbmeta (idk what this is), and this bricked it until I re-flashed the ROM. But I guess that's not needed anymore.
Click to expand...
Click to collapse
Which guide?
V0latyle said:
Which guide?
Click to expand...
Click to collapse
How to Root Pixel Devices via Magisk on Android 12
In this comprehensive tutorial, we will show you detailed steps to root your Pixel device via Magisk running Android 12.
www.droidwin.com
On step 7. It says it's not necessary for some reason on newer devices but pixel 5 and older still require it. What does flashing this file actually do? Like what's the file made of?
flyoffacliff said:
How to Root Pixel Devices via Magisk on Android 12
In this comprehensive tutorial, we will show you detailed steps to root your Pixel device via Magisk running Android 12.
www.droidwin.com
On step 7. It says it's not necessary for some reason on newer devices but pixel 5 and older still require it. What does flashing this file actually do? Like what's the file made of?
Click to expand...
Click to collapse
Nothing needs to be done with vbmeta as long as you're using Magisk 23016.
I'll try to explain what it is and what it does as simply as I can but there isn't really a simple explanation...
Some components of Android system security, such as Verified Boot, incorporate a means by which the data being loaded from critical partitions is checked in real time as it is loaded. This is called "device-mapper verity". The raw data itself is read at the block device level and used to create a hash; this hash is then compared to a reference hash to determine the data has not been modified. The partition that contains this reference hash is vbmeta.
When the Android 12 beta was first released, Magisk had not yet been updated to properly handle Android 12 boot image headers. Verified Boot is disabled for the most part when the bootloader is unlocked; however some elements still remain to ensure you're booting a proper device boot image. Magisk did not preserve necessary information in the boot headers, so the device wouldn't boot; we would get a message in bootloader stating failed to load/verify boot images
We figured out a workaround for this: disable dm-verity and vbmeta verification altogether. This was done by flashing the vbmeta partition with those two options:
Code:
flash vbmeta vbmeta.img --disable-verity --disable-verification
The problem with this is it has some sort of safety interlock that prevents system from loading if verity/verification are disabled and /data isn't clean. So, rooting required wiping data. You probably discovered this during your "brick": you got a screen reading Cannot load Android system. Your data may be corrupt.
We also discovered that the vbmeta workaround had to be performed every time vbmeta was flashed - meaning no OTA updates, because if vbmeta was flashed without the disable options, we wouldn't be able to boot a patched boot image, and even if we re-disabled verity/verification, the device still wouldn't boot unless data was clean. The only way to update AND reroot AND keep data was to ensure that verity and verification were disabled every time the device was updated.
Fortunately, Magisk 23016 fixed all of this. We don't have to mess with vbmeta anymore. Magisk properly preserves the flags in the boot header, meaning that AVB recognizes it as a legitimate boot image, and the device is happy.
has anyone able to pass safety CTSprofile ?
Basic integrity is pass but CTSprofile Check isnt passed...
anybody able to pass in A12 (OnePlus Nord)
tried all effort but dint work, even Universal SafetyNet Fix v2.2.1 (Zygisk) isnt working..
its makes Basic Integrity Fail after Flash ( Universal SafetyNet Fix v2.2.1 (Zygisk).
I roll back to A11 then sadly....
shhahidxda said:
has anyone able to pass safety CTSprofile ?
Basic integrity is pass but CTSprofile Check isnt passed...
anybody able to pass in A12 (OnePlus Nord)
tried all effort but dint work, even Universal SafetyNet Fix v2.2.1 (Zygisk) isnt working..
its makes Basic Integrity Fail after Flash ( Universal SafetyNet Fix v2.2.1 (Zygisk).
I roll back to A11 then sadly....
Click to expand...
Click to collapse
You're doing something wrong. Don't overlook anything. I'm on Android 12.1 and pass safety net, Google pay works, Netflix works.
Have you configured the deny list in magisk?? If not do that then. I'd start fresh, don't connect to anything on first start. Hide everything about those Google apps. Then add your accounts etc etc. This is what worked for me no problem
thatsupnow said:
You're doing something wrong. Don't overlook anything. I'm on Android 12.1 and pass safety net, Google pay works, Netflix works.
Have you configured the deny list in magisk?? If not do that then. I'd start fresh, don't connect to anything on first start. Hide everything about those Google apps. Then add your accounts etc etc. This is what worked for me no problem
Click to expand...
Click to collapse
I would like to know, how you are able to pass? I mean It is passed using Universal safetynet fix by Kdragon?
or without fix?
as you mention in your screenshot that you have put all google services in denylist,
I've already done that..
anything else ? you done it? can you show screenshot of your safetynet pass??
shhahidxda said:
I would like to know, how you are able to pass? I mean It is passed using Universal safetynet fix by Kdragon?
or without fix?
as you mention in your screenshot that you have put all google services in denylist,
I've already done that..
anything else ? you done it? can you show screenshot of your safetynet pass??
Click to expand...
Click to collapse
I'm using the latest safetynet fix v2.2.1 Kdragon
thatsupnow said:
I'm using the latest safetynet fix v2.2.1 Kdragon
Click to expand...
Click to collapse
Yes, you are able to pass both .. but i am having issue with OnePlus Nord A12..
On A11 i was able to pass without Universal fix..
but as I applied OTA of A12...
I lose safetynet pass.
let me know do you have any workaround?
I've applied Universal fix by Kdragon.. but before flashing Universal fix of Zygisk I was able to pass Basic Integrity but as soon as I flash Kdragon Universal fix of Zygisk both CTS profile & Basic Integrity gets failed... !!!!
I am still looking for solution to fix this issue..!! if you have any work around.. let me know.. I will do my best.. may be i need to modify device fingerprints with Security patch.? what you say?
shhahidxda said:
Yes, you are able to pass both .. but i am having issue with OnePlus Nord A12..
On A11 i was able to pass without Universal
I've applied Universal fix by Kdragon.. but before flashing Universal fix of Zygisk I was able to pass Basic Integrity but as soon as I flash Kdragon Universal fix of Zygisk both CTS profile & Basic Integrity gets failed... !!!!
Click to expand...
Click to collapse
shhahidxda said:
Yes, you are able to pass both .. but i am having issue with OnePlus Nord A12..
On A11 i was able to pass without Universal fix..
but as I applied OTA of A12...
I lose safetynet pass.
let me know do you have any workaround?
I've applied Universal fix by Kdragon.. but before flashing Universal fix of Zygisk I was able to pass Basic Integrity but as soon as I flash Kdragon Universal fix of Zygisk both CTS profile & Basic Integrity gets failed... !!!!
I am still looking for solution to fix this issue..!! if you have any work around.. let me know.. I will do my best.. may be i need to modify device fingerprints with Security patch.? what you say?
Click to expand...
Click to collapse
You do realise that your posting on the pixel 5 forum right?? I'd maybe go checkout what they are doing on the OnePlus side of the tracks
thatsupnow said:
You do realise that your posting on the pixel 5 forum right?? I'd maybe go checkout what they are doing on the OnePlus side of the tracks
Click to expand...
Click to collapse
Yes, I knew i am posting in Pixel 5 and this topic isnt mention on Oneplus section..
I am looking for a solution of this issue.. but nobody has mention it till now.
Android 12.1 + Magisk 25.1 + Zygisk + Google Play services on enforced Denylist > Works charmingly
Note 1: Enforce Denylist for all the Google Play services modules on Magisk.
Note 2: After reboot, clear data of Google Play services and Play Store to make a fresh start.
pseudokawaii said:
Android 12.1 + Magisk 25.1 + Zygisk + Google Play services on enforced Denylist > Works charmingly
Note 1: Enforce Denylist for all the Google Play services modules on Magisk.
Note 2: After reboot, clear data of Google Play services and Play Store to make a fresh start.
Click to expand...
Click to collapse
I have the same running on a Galaxy S10, but every time I put Google Play Services on the enforce Denylist and reboot it no longer shows there. I'm trying to be able to use my banking app, it worked charmingly on magisk 24 but not anymore. Any advice?
El3ssar said:
I have the same running on a Galaxy S10, but every time I put Google Play Services on the enforce Denylist and reboot it no longer shows there. I'm trying to be able to use my banking app, it worked charmingly on magisk 24 but not anymore. Any advice?
Click to expand...
Click to collapse
What do you mean by "it no longer shows there"? Does the Google Play services disappear after putting on denylist? Did you enable the "Enforce Denylist" option? Did you do a retest of SafetyNet after reboot?
El3ssar said:
I have the same running on a Galaxy S10, but every time I put Google Play Services on the enforce Denylist and reboot it no longer shows there. I'm trying to be able to use my banking app, it worked charmingly on magisk 24 but not anymore. Any advice?
Click to expand...
Click to collapse
Yea and it won't stick I've tried that too. You don't need to add Google Play services to the deny list anyway
thatsupnow said:
Yea and it won't stick I've tried that too. You don't need to add Google Play services to the deny list anyway
Click to expand...
Click to collapse
If you're using Universal Safetynet Fix, Play Services is blocked out of the box. I had the same thing happen in one of the newer releases and thought it was an issue. It isn't. Play Services is blocked even though it doesn't show it.

Categories

Resources