Can anyone with Magisk test this module? (Samsung 7.0/Nougat) - Galaxy S6 Q&A, Help & Troubleshooting

I'm having an issue with a Magisk module that I've created for my Galaxy S6 Edge (G925T) to systemlessly replace the fonts. The module replaces most of the system fonts with a font called Arsenal, as well as changes emoji to Emoji One and the monospace font to Monoid. When I have it enabled, SafetyNet fails even with MagiskHide enabled (it didn't used to up until recently). I need anybody willing to test, running a Samsung-based ROM with Magisk and MagiskHide enabled, to do the following so that I can determine whether it's just an issue with my device, or if there may be new SafetyNet checks in place:
- Take a full backup with TWRP (just to be on the safe side)
- Ensure that SafetyNet is FULLY PASSING on your device before installing this module (both basicIntegrity and ctsProfile)
- Flash the zip attached in TWRP
- Ensure that the fonts have changed on your device
- Check SafetyNet again.
Then, answer the following questions:
What phone model do you have?
What ROM are you on?
What security patch are you on?
What kernel are you using?
Is SELinux/SE for Android Enforcing or Permissive?
What version of Magisk are you using?
Does SafetyNet pass?

Related

Deodex stock oreo (signature spoofing)

Hello,
I want to use microg but I need to enable signature spoofing (don't want to use xposed). When deoxing my services.jar I get stuck at Samsung logo. Doesn't matter if manual with smali or nanodroid patcher.
My setup is s7 with twrp, no verity dm script and stock oreo with magisk root.
Is there something special I need to do? Remove knox? Selinux permissive?
Hope you can help me
FIY or other people with same problem
I found a magisk module to do it for me: https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053
Just activated signature spoofing systemless. Now everything is working. Safety net passes when you hide magisk for micro g helper

Magisk SafetyNet attestation failed

I have just updated to LineageOS 16 (unofficial) and installed Magisk 21.0.
As noted in this article: android-safetynet-hardware-attestation, when I run Check SafetyNet it comes up with the Attestation Failed! notice.
Just thought I would make a note of this, in case others want to compare their findings.
Moto G4 Plus XT1642
currently running lineage-16.0-20200928-UNOFFICIAL-athene
I run the Stock Oreo 8.1 from https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367 with last official TWRP and ElementalX Kernel
Had device not certified on Play Store and ctsProfile failed in Magisk SafteyNet check (basicIntegrity OK and evalType BASIC)
Installed Magisk module MagiskHide Props Config and picked certified fingerprint for my device.
After reboot SafteyNet check passed
Can you please share how to pick a certified fingerprint for a device? Rooted my Pixel 3 XL and the safetynet attestation failed. I installed the module you said, but I don't know what to do next, I'm new with this
Edit: I managed to fix it with the safetynet fix v1.1.0 found on xda

Question Boot.img

I was able to extract the boot image on my Android phone using python then I was able to patch it with a fixed magisk APK that passes safetynet. I will make a video and post links to where I got everything from
Sorry guys I forgot to mention you need the safety net universal fix module here's the XDA link I forgot to mention that in the video my apologies
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Here's the tutorial on how to extract the boot image on your Android device using python

[GUIDE] Passing Safetynet

This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders or custom verified boot keys. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on January 12, 2021.
Instructions:
1. Make sure Magisk hide is enabled.
2. Download the universal safety net fix from kdrag0n's github repository right here.
3. Install it from Magisk manager.
4. Test if it works, if not then download this version of the module instead.
5. If it works congratulations your device now passes safetynet responses.
Credits
@kdrag0n
Worked for me, thanks!
This version of the safetynet fix only works for Magisk v24+(Zygisk).
If you are on version 23.0 of Magisk this should work. But it requires Riru v24.0.0 or newer installed and Magisk hide enabled.
I've attached my results from a SM-A750FN variant.

OnePlus 7 Google Wallet (Pay) "your device doesn't meet security requirements"

Installed Android 12 GM1900_11_H.32
APP Magisk Cannery 25.2 (25200)(33) Installed 831a398b (25206)(D)
TWRP 3.7.0_12-0
Zygisk
Enforce Deny List - Deny list is configured for all google apps
Riru (not enabled, it then allows zygisk to run)
Universal safetynet fix v2.2.1
MagiskHide Props Config v6.2-v137
I cannot hide the Magisk app it creates a new app name but it won't load and magisk is still there and of course, google Wallet won't run
everything else is ok rooted and running.
Is anybody with experience of this problem and any solution? would appreciate feedback
p.s. SafetyNet 'attest' returns "Response signature validation error" other SafetyNet tests run OK.
Aussiewaterdragon said:
Installed Android 12 GM1900_11_H.32
APP Magisk Cannery 25.2 (25200)(33) Installed 831a398b (25206)(D)
TWRP 3.7.0_12-0
Zygisk
Enforce Deny List - Deny list is configured for all google apps
Riru (not enabled, it then allows zygisk to run)
Universal safetynet fix v2.2.1
MagiskHide Props Config v6.2-v137
I cannot hide the Magisk app it creates a new app name but it won't load and magisk is still there and of course, google Wallet won't run
everything else is ok rooted and running.
Is anybody with experience of this problem and any solution? would appreciate feedback
p.s. SafetyNet 'attest' returns "Response signature validation error" other SafetyNet tests run OK.
Click to expand...
Click to collapse
I am facing the same issue.
Android 12 GM1900_11_H.36
Magisk 25.2 (25200)(33)
Package ifk.peqffjnp
Universal SafetyNet Fix 2.2.1 by kdrag0n
The SafetyNet test is passed.
However, I can't pay...

Categories

Resources