[Magisk v14.0] Universal SafetyNet Fix | Universal Hide [v2 Beta 5]

Search This thread

marisaleh

Senior Member
Sep 22, 2009
172
32
If Your Device Didn't Pass The SafetyNet, Try DeviceSpoofingTool4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435.
But DeviceSpoofingTool works the same way as
Magiskconfig props tool, by emulating a working
certificate.

I want to be able to pass safetynet by using the
device's native certificate, like I used to by using
the Universal Safetynet fix zip

---------- Post added at 12:33 PM ---------- Previous post was at 12:27 PM ----------

If Your Device Didn't Pass The SafetyNet, Try DeviceSpoofingTool4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435.
But DeviceSpoofingTool works the same way as
Magiskconfig props tool, by emulating a working
certificate.

I want to be able to pass safetynet by using the
device's native certificate, like I used to by using
the Universal Safetynet fix zip
 

Dreamer(3MF)

Senior Member
Mar 17, 2018
753
1,144
But DeviceSpoofingTool works the same way as
Magiskconfig props tool, by emulating a working
certificate.

I want to be able to pass safetynet by using the
device's native certificate, like I used to by using
the Universal Safetynet fix zip

P.S. The Module Of Universal Safetynet Fix Uses One Of Xiaomi's Fingerprints To Pass The SafetyNet So If You Want To Check That, Try To Flash The Following Modified One Which Supports Magisk v16.0(1600) To v17.1(17100) From This Post https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431/post76776696 & After Reboot, Check The Current Used Fingerprint (Install Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write getprop ro.build.fingerprint --> Click On Enter). On The Other Hand, One Of The Differences Between The Module Of DeviceSpoofingTool4Magisk & The Other Modules Is Getting Its Activation After Flashing It & 1st Reboot Without Using Any Other App/Tool/File Such As Terminal Emulator To Activate Its Commands.
 
Last edited:

marisaleh

Senior Member
Sep 22, 2009
172
32
P.S. The Module Of Universal Safetynet Fix Uses One Of Xiaomi's Fingerprints To Pass The SafetyNet So If You Want To Check That, Try To Flash The Following Modified One Which Supports Magisk v16.0(1600) To v17.1(17100) From This Post https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431/post76776696 & After Reboot, Check The Current Used Fingerprint (Install Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write getprop ro.build.fingerprint --> Click On Enter). On The Other Hand, One Of The Differences Between The Module Of DeviceSpoofingTool4Magisk & The Other Modules Is Working Properly After Flashing It & 1st Reboot Without Using Any Other App/Tool/File Such As Terminal Emulator To Activate Its Commands.
So please can you confirm to me:

Do all safetynet fix solutions use spoofing ie other
fingerprints
what does this old module: universal-safetynet-fix-v2-beta-5-magisk-v14.zip use, does it also use spoofing.

So there is no way where I can use the phone's own
certificate to pass safetynet.

My phone is: Elephone S8, it is Google supported, but
it is not certified, even before rooting it.

So is it possible to ever get it to pass using its own
certificate?

And thank you very much for your help.
 
Last edited:
  • Like
Reactions: Dreamer(3MF)

Dreamer(3MF)

Senior Member
Mar 17, 2018
753
1,144
So please can you confirm to me:

Do all safetynet fix solutions use spoofing ie other
fingerprints
what does this old module: universal-safetynet-fix-v2-beta-5-magisk-v14.zip use, does it also use spoofing.

So there is no way where I can use the phone's own
certificate to pass safetynet.

My phone is: Elephone S8, it is Google supported, but
it is not certified, even before rooting it.

So is it possible to ever get it to pass using its own
certificate?

And thank you very much for your help.

Yes, The Old Module universal-safetynet-fix-v2-beta-5-magisk-v14.zip Is Using Also The Spoofing Method (Xiaomi's Fingerprint). And If Your Device Is Not Certified By Google (Which Means That The Used Fingerprint Is Not Suitable To Pass The SafetyNet), Maybe You Can Pass The SafetyNet By Using A Custom Rom Or By Using A Spoofing Tool To Certify Your Device & Pass The SafetyNet.
If You Have Any Question, Post It & I Will Try To Reply As I Know. We Are Here To Get More Info & Help Each Other.
 
Last edited:

marisaleh

Senior Member
Sep 22, 2009
172
32
Yes, The Old Module universal-safetynet-fix-v2-beta-5-magisk-v14.zip Is Using Also The Spoofing Method (Xiaomi's Fingerprint). And If Your Device Is Not Certified By Google Which Means That The Used Fingerprint Is Not Suitable To Pass The SafetyNet. Maybe You Can Pass The SafetyNet By Using A Custom Rom Or By Using A Spoofing Tool To Certify Your Device & Pass The SafetyNet.
If You Have Any Question, Post It & I Will Try To Answer. We Are Here To Get More Info & Help Each Other.
Thank you very much,
I would like to share with you my conclusion:

From Google side:

A device can be supported by Google, you can check
It in the Play Store, under supported devices.

A Google supported device will not necessarily be
A Google certified device. To be certified, the device
Manufacturer has to submit tests to Google for
Approval and hence the device will be certified.

If the Play Store says: device not certified, this means
That device will never pass safetynet with its current
Certificate. Hence the only way is to use spoofing.

If the Play Store says: device is certified, this means
That device will pass safetynet with its current Certificate

Therefore, all the safetynet fix solutions use spoofing
To pass uncertified devices by Google.
 
  • Like
Reactions: Dreamer(3MF)

Dreamer(3MF)

Senior Member
Mar 17, 2018
753
1,144
Thank you very much,
I would like to share with you my conclusion:

If the Play Store says: device is certified, this means
That device will pass safetynet with its current Certificate.

I Would Like To Clarify That Not Every Certified Device Can Pass The SafetyNet But The Device Certification Is An Important Point Which Will Be Checked By Many Apps Such As Netflix & Pokemon-Go.
 
Last edited:

PetNoire

Senior Member
Sep 7, 2018
56
60
Can you please attach your version of universal
safetynet fix.

Thank you very much
i will aas soon as my post count is high enough

[/COLOR]
But DeviceSpoofingTool works the same way as
Magiskconfig props tool, by emulating a working
certificate.

I want to be able to pass safetynet by using the
device's native certificate, like I used to by using
the Universal Safetynet fix zip

i feel like DeviceSpoofingTool came with a certificate that wasnt approved. i got a notice at boot that the vendor info didnt match so it was clearly spoofing it but wouldnt pass anything. could probably change it but just simply wasnt interested. too much invested in this one by then.


my end goal is to use universal with my moto g5's stock settings to pass on lineage as the one included already does (though with the wrong vendor message) at this point the only issue seems to be that it is hiding magisk from itself. when the module is enabled, it passes all the safetynet checks and i can use bank apps and pokemon go, but cant use root and magisk manager keeps asking me to install the zip which is already installed. i currently have to mount magisk.img in recovery and remove the module to get the root functionality back. soon as my post count hits 10, i'll upload what i have so far and a zip to disable it again, and keep working until it stops breaking root and can be left on

if anyone used this on magisk 14, can you please tell me if root worked then?
 
Last edited:

DShot92

Member
Sep 15, 2012
27
1
redmi note 4
miui 10 global beta flashed with MiFlash
installed magisk with twrp (treble version, i just previously installed lineage but didnt like it)
In the magisk manager i see that root is ok (lucky patcher works as usual), but cts check fails.
i've found universal fix but it wont install, "error 1, magisk must be installed"

Any help?
 

teddy0209

Senior Member
Feb 5, 2011
2,321
692
redmi note 4
miui 10 global beta flashed with MiFlash
installed magisk with twrp (treble version, i just previously installed lineage but didnt like it)
In the magisk manager i see that root is ok (lucky patcher works as usual), but cts check fails.
i've found universal fix but it wont install, "error 1, magisk must be installed"

Any help?
Just use the one available in the repo... Magiskhide props

Sent from my MI 5 using Tapatalk
 

PetNoire

Senior Member
Sep 7, 2018
56
60
redmi note 4
miui 10 global beta flashed with MiFlash
installed magisk with twrp (treble version, i just previously installed lineage but didnt like it)
In the magisk manager i see that root is ok (lucky patcher works as usual), but cts check fails.
i've found universal fix but it wont install, "error 1, magisk must be installed"

Any help?

Did you try my new version of it? Here
 

Top Liked Posts

  • There are no posts matching your filters.
  • 222
    Universal SafetyNet Fix
    This module tries to pass SafetyNet on devices that triggered it.

    It works by doing some magic with the system props, which are changed to match with the required by Google to pass it's security test (SafetyNet). However, that is not all...

    The real magic here is the Universal Hide part, which is a custom implementation of Magisk Hide. It basically does the same magic as Magisk Hide, but in a shell-y simple way.
    It reads the file Magisk Hide uses to store apps that should be hidden and then monitors logcat until a hidden app is opened. Once this happens, it enters it's mount namespace to unmount all Magisk related mount points.
    That way you can hide root or bypass SafetyNet for almost to all apps. App's that use custom checks to detect root are one of the few exceptions as we cannot anticipate what they check.

    Why did I basically duplicated Magisk Hide? Well, Magisk Hide doesn't work properly for all devices, so this is a fast solution until topjohnwu fix all the issues.

    Information

    Requeriments
    • Magisk v13.x/14.0
    • MagiskSU

    Links
    Download Beta
    Download Stable (very outdated)
    Download uninstaller
    Source code

    Installation
    1. Flash the .ZIP from TWRP
    2. Reboot

    Donations
    If you feel I helped you, you can buy me a coffee here. :)

    Changelog

    v1.10.1
    • Fixed Magisk Hide detection for Magisk v12

    v1.10
    • Module is now universal, not for Xiaomi devices only
    • Module refactored
    • Magisk v13 beta support
    • Added some props
    • Added SafetyNet fix for Magisk v12
    • Check if Magisk Hide was properly started and try to fix
    • Zip signed

    v1.9.1
    • Fixed logging code: ignore output of wait for unmount loop

    v1.9
    • Added new supported devices: Redmi Pro, Mi 4S, Redmi 4X
    • Changed Redmi Note 3 MTK prop
    • Changed wait for Magisk SafetyNet check to a function and run in a subshell

    v1.8.2
    • Fixed Redmi Note 3 MTK device name typo

    v1.8.1
    • Fixed forgotten set_prop function calls

    v1.8
    • Added new supported devices: Mi Note Pro, Redmi 1, Redmi 1S
    • Fixed Mi 5 prop
    • Removed run enable script
    • Code improved

    v1.7
    • Added new supported devices: Mi 6
    • Added "ro.bootimage.build.fingerprint" prop
    • Removed reinitiate Magisk Hide
    • Added run Magisk Hide when boot & service steps are completed
    • Improved log code: waiting to SafetyNet test and Magisk Hide folder unmount, silence some shell output

    v1.6
    • Added new supported devices: Mi Pad, Mi Note, Mi 3/Mi 4, Mi 2/2S, Mi Pad 2, Mi Pad 3
    • Added code to reinitiate Magisk Hide

    v1.5
    • Added new supported devices: Redmi 4, Redmi 4 Prime, Redmi 4A

    v1.4
    • Added new supported devices: Redmi 3/Prime, Mi 4i
    • Added code to generate useful logs and enable Magisk Hide if not enabled
    • Changed to use resetprop directly from script @laggardkernel
    • Removed build description because is useless



    v1.3
    • Added new supported devices: Redmi 2/4G, Redmi 2 Prime
    • Added some extra code to support device with different model name

    v1.2
    • Added new supported devices: Mi 4c, Mi 5c, Redmi Note 3 Special Edition, Mi Note 2, Redmi Note 4X

    v1.1
    • Added new suported devices: Mi Max, Mi Max Prime, Redmi 3S/Prime/3X

    v1
    • Initial release
    • Suported devices: Redmi Note 2, Redmi Note 3 MTK, Redmi Note 3 Qualcomm, Redmi Note 4 MTK, Mi 5, Mi 5s, Mi 5s Plus, Mi MIX

    Thank you
    112
    Universal SafetyNet Fix v2 Beta 5

    I'm testing some functions and they could doesn't work stably in all devices, so I decided to release betas to test new things and get some feedback.

    USNF Settings
    Use from terminal emulator with root provileges, run this to see usage
    Code:
    usnf
    v2 Beta 5 changelog
    • Added Magisk v13+ support to Universal Hide
    • Added module settings
    • Fixed fake not mount namespace support message due 32-bit devices
    • Better Magisk version detection
    • Separated every type of mount points to own unmount command
    • Fixed some problem when clear logcat
    • Fix fingerprint issue
    • Added reboot ask to module settings
    • Removed Magisk v13 props to fix SafetyNet
    • Copy busybox and magiskhide in every boot
    • Removed Magisk Hide disable and enable loop
    • Output Magisk related props in the log
    • Hide permissive mode
    • Hide the original Magisk binaries of /sbin_orig folder
    • Added more props to hide
    • Updated bundle Busybox binaries to 1.27.1
    • Removed the waiting for Magisk boot end
    • Better output in Magisk log
    • Some code syntax cleanup
    • Cleanup some code
    • Hide more Magisk props
    • Added output to Magisk log of target process namespace at unmount
    • Added partial support for Magisk v12
    • Added support for newer Huawei devices unmounting vendor mountpoint
    • Added Magisk 13.5 Beta support
    • Fixed unmount of some modules
    • Improved module outputs in Magisk log

    Previous beta changelogs

    v2 Beta 4
    • Own Magisk Hide implementation renamed to Universal Hide
    • Fixed Universal Hide when there are not modules
    • Kill module if mount namespaces are not supported
    • Enable full Universal Hide if Zygote namespace is not found in Magisk log
    • Check if system shell runs correctly when is runned by BusyBox's nsenter applet, if not use BusyBox's shell
    v2 Beta 3
    • Completed own implementation of Magisk Hide to unmount all when any process listed in hidelist file is runned for Magisk v12 only, auto-enabled only if you Magisk Hide doesn't work
    v2 Beta 2
    • Own implementation of Magisk Hide to unmount all when SafetyNet process (com.google.android.gms.unstable) is runned to bypass SafetyNet for Magisk v12 only, auto-enabled only if you Magisk Hide doesn't work
    • Fix for unmount mirror, dummy & busybox
    v2 Beta 1
    • Unmount mirror, dummy & busybox in the namespace of the process you hide for Magisk v12 like Magisk v13 does. No more /dev/magisk ugly rename workaround.


    If you have issues, join here (Telegram group): https://t.me/USNFGroup

    Magisk v14 hotfix here
    79
    Hotfix for Magisk v14

    Use only with Magisk v14+

    *re-uploaded
    25
    Universal SafetyNet Fix v2 Beta 4

    I'm testing some functions and they could doesn't work stably in all devices, so I decided to release betas to test new things and get some feedback. Have in mind that you wont got support by me if something works bad with a beta version.

    v2 Beta 4 changelog
    • Own Magisk Hide implementation renamed to Universal Hide
    • Fixed Universal Hide when there are not modules
    • Kill module if mount namespaces are not supported
    • Enable full Universal Hide if Zygote namespace is not found in Magisk log
    • Check if system shell runs correctly when is runned by BusyBox's nsenter applet, if not use BusyBox's shell

    Previous beta changelogs

    v2 Beta 3
    • Completed own implementation of Magisk Hide to unmount all when any process listed in hidelist file is runned for Magisk v12 only, auto-enabled only if you Magisk Hide doesn't work
    v2 Beta 2
    • Own implementation of Magisk Hide to unmount all when SafetyNet process (com.google.android.gms.unstable) is runned to bypass SafetyNet for Magisk v12 only, auto-enabled only if you Magisk Hide doesn't work
    • Fix for unmount mirror, dummy & busybox
    v2 Beta 1
    • Unmount mirror, dummy & busybox in the namespace of the process you hide for Magisk v12 like Magisk v13 does. No more /dev/magisk ugly rename workaround.


    If you have issues, post these information
    1. Magisk log in Magisk Manager or magisk.log file in /cache
    2. universal-safetynet-fix.log file in /cache
    3. Install RootBeer Sample from Google Play, HIDE IT from Magisk Hide, run it, click the button and take screenshot.

    ATM is not fully compatible for Magisk v12 due the last SafetyNet update. Universal Hide (my own "Magisk Hide") doesn't support Magisk v13+ too.

    Beta 5 test builds is fully compatible for Magisk v12/v13+
    17
    Uninstaller

    Created the uninstaller zip from @Dark❶'s uninstaller template.
    This can be flashed from recovery to remove the module.

    May be useful in case of bootloops (although we know there are none) or may be other cases.
    I have tested at my end, works flawlessly.
    @Deic please add to OP if you find it useful.