yashsingh1/xdaforums huggingface dataset:
[Magisk] mindyabiznis:
Yes you did indeed, and thank you very much...

I changed serious mode to enforcing using an app called The SELinux Switch and I now pass safetynet and am certified on Google play store:victory:

Now if I could just find a way to hide root from the Arriva M-ticket app I'll be laughing.

Turns out I don't need this module at all, I have checked with terminal emulator that magiskhide is running and it seems to be working with everything except the Arriva app.

Something is strange though because android is telling me in my trust settings that root access is disabled.
[Magisk] kenny.lam:
It works on Havoc Os custom rom, Android 9 pie, magisk. Now I am certified from Google and can download Netflix. Thanks much for your work
[Magisk] SaikiK:
Thanks

Works like a charm.
[Magisk] Gabrech:
Thanks !

Worked also on Pixel experience 9 with oneplus 5t. Paid today with a card on GPay. Great !
[Magisk] holofractal:
It did, but this module fixed that :)
[Magisk] Asbrand_VII:
Thank you very much, man!

Works on Xiaomi Mi9 on Pixel

Experience 10 (21/11/2019)
[Magisk] lottarake:
Worked on my OnePlus 6T with Android 10 crDroid and Omnirom, and now working on the 7 Pro with HavocOS. Thanks, this always works flawlessly.
[Magisk] Greatness83:
Thanks! Working on OP6T OB2

Gpay is working again!
[Magisk] damca:
Thanks! Working on Samsung Galaxy N9 960F 8GB/512GB - Dr.Ketan Q02 ROM with Tweaks Pro

Gpay is working again!
[Magisk] domhall012N8:
I'm on same phone and Rom... Magisk says it's not a Magisk Module... Will not install :(
[Magisk] chooks06:
Did you download from the Magisk repo on the manager. Modules downloaded from there are usually compatible with the MM version on the device.

Any module not updated to that version of Magisk installed will not appear in the download list.

But I'm not using the same device as you though.
[Magisk] damca:
In magisk in left menu tap to download and than search, write safe and then you see SafetyPatch

Odesláno z mého SM-N960F pomocí Tapatalk
[Magisk] holymoz:
Bootloop on mi9lite stock miui11 pie
[Magisk] Luis4x4:
Thank you,it work for me.
[Magisk] holofractal:
Just started failing right now. Got a notification that my device doesn't meet safety standards. Failing both CTS and basic integrity :( with and without module.
[Magisk] holofractal:
I should also note, nothing on my phone has changed in a week.
[Magisk] exadeci:
This module works great but breaks AR on my Note 9 (Android 10) when enabled.

Maps live navigation and Minecraft Earth both can't use AR with this module, the camera works fine though.
[Magisk] JimZiii:
the reason i'm here is because i'm failing safetynet no matter where i check it. both inbuilt and other checkers. since i factory reset and updated my phone safetynet stopped passing and i noticed my play store became uncertified. i tried flashing several older firmwares to see if they worked and one time my bootloader got locked again and just as it got locked my play store said certified and safetynet was passing. so i'm pretty sure it's my bootloader thats being detected so i tried every mod i could find to hide my bootloader and every mod to pass safetynet but none of them worked. magiskhide is supposed to hide unlocked bootloaders also and now that i know magiskhide isn't working at all it's fairly obvious that's the reason
[Magisk] Dreamer(3MF):
Kindly Check The Following Versions Of Magisk

- Magisk-v16.3(1631) From This Link https://androidfilehost.com/?fid=962339331458996616

- Magisk-v16.7(1674) From This Link https://androidfilehost.com/?fid=3700668719832236565
[Magisk] JimZiii:
same problem. i think the issue is somewhere else since the regular magisk versions worked fine until i updated my phone
[Magisk] Dreamer(3MF):
Try To Flash The Old Rom Which Was Working Properly With Magisk Hide.
[Magisk] JimZiii:
it didn't help. i'm back on b407. previously i've had issues flashing firmware in twrp but right before i updated and lost safetynet i found a post saying its only possible to flash -PV roms through twrp and then they linked a thread to something called HuRUpdater which is a zip that lets you flash any from through twrp, so i thought maybe that's the issue. the last rom i had working was b394 which also has a -PV version so i downloaded both so that i could see if any of them worked but none of them works. i factory wiped and wiped system, flashed the rom, tried safetynet and basic integrity passed but no matter which rom i flashed, i even tried updating through the OTA's and trying magisk, as soon as i flash magisk i fail safetynet. and at that point thats the first thing i did after booting the phone.

i've tried older magisk managers and current, tried a bunch of older magisk roots because i still got the same ones on my sd card that i downloaded before all this happened. 16.0 is the oldest i've tried but all those worked before so i don't understand why they aren't working now.
[Magisk] hackintosh5:
Try with magisk 16.7. The fingerprint must be certified for production. If it isn't you must use MagiskHide Props Config. This module will just hide the unlocked bootloader.
[Magisk] hackintosh5:
MagiskHide DOES NOT hide unlocked bootloader reliably. That is why I made this module. This module needs MagiskHide to be enabled. If it's not working, the module won't work either. Please run in a root shell on the device: `cat /proc/cmdline` and post the output, stripping serial numbers etc.
[Magisk] hackintosh5:
This works on official magisk. No need for other ones.
[Magisk] JimZiii:
Where and how do I run these commands? Don't think I've done that before.

I'm already on 16.7, I've also tried 16.0, 16.3, 16.4, 16.6 and the ones posted by Dreamer(3MF).
[Magisk] hackintosh5:
In adb shell, or a terminal emulator from Google play
[Magisk] DenyDarko:
Interesting.

I can see "androidboot.verifiedbootstate=orange" in /proc/cmdline.

Thing is, I can't grab its contents without being root at the first place.
[Magisk] hackintosh5:
That means module is not functioning. Try /data/local/tmp/cmdline. If the file doesn't exist, the module script isnt running at all.
[Magisk] JimZiii:
If I type "cat/proc/cmdline" the terminal emulator just tells me "not found" and if i type "proc/cmdline" (which I saw another poster do) I get "can't execute: permission denied"
[Magisk] hackintosh5:
There's a space after cat but before /

proc/cmdline executes it, it's not an executable file so it will give a permission denied.
[Magisk] JimZiii:
Weren't really sure what to remove other than serialno so im sending it in a pm
[Magisk] candiesdoodle:
[MENTION=8556932]hackintosh5[/MENTION]

The correct command should be

sed 's/orange/green/' /proc/cmdline .....

The orange/green is case sensitive. Atleast on OP3 it is
[Magisk] hackintosh5:
On my device it's all caps... I'll see about fixing
[Magisk] hackintosh5:
I've pushed an update in magisk manager and GitHub, that should fix the case-sensisivity. After the module activates, it will switch from 'orange' to 'GREEN'
[Magisk] lauralbaby:
I'm running ResurrectionRemix 6.1, after installing I got The response is invalid from Safetynet.
[Magisk] hackintosh5:
This is due to a recent change in safetynet. It is a bug on the apps side ..
[Magisk] surya790:
Thank you!!!
[Magisk] AZDJedi:
Doesn't work for me. HTC One M7 with LineageOS Pie.

I've tried reflashing and wiping cache. When I run sudo safetypatch it just says permission denied. When I open /proc/cmdline there is no mention of the android line (green, orange, or rainbow lol).

Suggestions?

(As a side note, in my /proc/ folder I have a few hundred subfolders numbered 100 to 7000. Some are empty, some seem to be dupes of the /proc directory. What's up with that??)
[Magisk] ei146:
Thanks!

Works for me on a Moto G5 with unofficial Lineage OS 16.0.
[Magisk] mLuca:
Thanks
[Magisk] leiersai:
great patch!
[Magisk] elzafir:
Upon installing this module and rebooting, I was greeted with this message:

My device is Xiaomi Mi A2 (jasmine_sprout) with Havoc OS 2.8 custom ROM based on Android Pie. I have Magisk 20.2 installed.

Any ideas what this means?
[Magisk] estofjlw:
[MENTION=4667597]Didgeridoohan[/MENTION]

I would like to add my fingerprint to the safetypatcher startup shell file and remove the HUAWEI fingerprint

I have a Moto G7 Power (XT1955-5 Ocean RETUS) with cRDdroid on it and I have SafetyPatcher and Magisk Hide Props Config modules installed under Magisk.

Currently Magisk Manager reports the SafetyNet passes both green checks and the root checker reports HUAWEI as the fingerprint. It is also hardcoded in the /system/.build.prop file.

The ro.build.fingerprints are

motorola/ocean/ocean:9/PPOS29.114-134-4/e8b9:user/release-keys

motorola/ocean/ocean:9/PPOS29.114-134-7/d9234:user/release-keys

One is for the 134-4 version and the other is for the 134-7 version update 12/5/2019

I am not clear on how much of this and the format how to put in the startup shell in the /data/adb/modules/safetypatcher/post-fs-data.sh file

Can you provide me with that info so I do not screw up the module booting and if I need to manually edit the /system/build.prop file ??
[Magisk] G-diddy:
Is this working with Android 10 roms? I couldn't download certain apps on the Play Store on my OnePlus 6t with Carbon Rom Pie or stock Pie while rooted and didn't pass SafetyNet. I relocked my bootloader and upgraded to 10 to get Safety Net working but now I'm suffering with unrooted OOS stock with annoying constraints . Really want to find a good AOSP based rom with working Safety Net. Everything used to work fine with unlocked, rooted stock Pie and OTA update to 10 while unlocked and rooted until I downgraded back to Pie and flashed CarbonRom Pie. Is this because of a/b rom slot thing on OP6t? I miss my Nexus 6 days when this stuff was easier.
[Magisk] LunarstarPony:
Well This fix cts but it broke AR Core Grrrr AR won't even work after install this
[Magisk] Greatness83:
AR core works fine. Tried in multiple apps that supports AR and all work fine
[Magisk] ivoe:
I'm running OnePlus 7 pro oos 10 beta 8

This is working

Is there a reason for this to change the fingerprint on my device.

I'd prefer to not have this change as I've been noticing a HUAWEI was logging into my Google account.

I just found it was due to this so is there a reason?
[Magisk] Didgeridoohan:
Changing device fingerprint is how this and other similar modules passes the CTS profile check of SafetyNet. So it is necessary, yes.

This particular module uses a Huawei fingerprint, but if you look back on the thread there are discussions on how to edit the scripts and use a print more suited for your device.
[Magisk] tazlooney89:
Works correctly at my Motorola One (XT1941-5) with Android Pie 9 stock and January 2020 security patch, I can download and update Netflix without any problem, GPay works normally, and all the hardware of my phone works correctly, the best module, thanks!!! ?
[Magisk] rdr02:
Looking for support for smt330nu, lineage 16 installed magisk 20.3 with safety patch v3 from downloads in magisk I can get CTS profile to pass and I can see Netflix in google play but it will break google chrome and internet .
[Magisk] TheLinuxMan02:
This worked on my rooted LG V40 running HavocOS Q. I'm even able to install Netflix:laugh:
[Magisk] ncc1977d:
Does not work on my Pra-LX1 c432 (P8 Lite 2017) with IanMacs Magisk (latest Version) on AOSPE 6.6.
[Magisk] numbawon:
Just here to say thanks for this mod. Ended up using it till I get around to making a system less mod for turning on 5ghz wifi this device (build.prop mod. :) nice work. Edited the prod live on the system, and obviously that tripped the check, this worked around it.
[Magisk] razorbak56:
Hello

Works with lot of application, Google pay is ok but no hello bank, it say : your phone is root, no payment with nfc

Have you a solution?
[Magisk] BriaBeerGo:
Did you activate this app in Magisk Hide?
[Magisk] alexsirb:
Magic! :cool:
[Magisk] QuaX1:
I'm gonna quote Freddie Mercury on this one "It's a kind of magic"

Thanks OP, fantastic job
[Magisk] alex.do:
I am on S10+ stock ROM. Mine was all green before. One day I dont know what i was messing which causes cts profile false (basic integrity still true). This module works for me! But I like to keep my original fingerprint so I went on modifying the code a bit to use my original fingerprint I got cts profile false again (even with /proc/cmdline patched). So I think it has something to do with my fingerprint? It was true before? So somehow the safetynet check sends the fingerprint to google's server to do the checking and somehow google "blacklisted" mine? If so, may I ask here is there anyway to get our fingerprint removed from the blacklist?

Thanks for the good findings mate!
[Magisk] @ayahfachri:
Same as mine, I'm on Mi8 Pixel Rom Android 10. I passed cts and basic integrity all green before & device certified in playstore, but after awhile cts profile is red & device is not certified in playstore.

Will reflashing the rom and start all over again will solved this issue?
[Magisk] -Zteam-:
It seems Google has made some changes to these tests.

Lots of devices failing CTS profile, while other devices passes fine, at the moment no one really knows why,

https://xdaforums.com/showpost.php?p=81952853&postcount=2847

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228/page284
[Magisk] alex.do:
Confirm! Now changing fingerprint no longer makes cts true! Something has changed on google server.

Also I already added my device id to Google uncertified page (for it to be certified i think?), even twice! No luck so far.

In case you wonder the page is https://www.google.com/android/uncertified/
[Magisk] Simon1511:
So, with the "new" safetynet, people wont pass cts, right?

Im on crDroid 5.10 (Pie with december patch) with magisk and safetypatch installed. Device is a Galaxy A5 2017 and Im still passing cts.

Did the update came with march patch or so or why does my device still pass?
[Magisk] Didgeridoohan:
Because it's too old to have the necessary hardware for key attestation. For now, those devices will pass even with an unlocked bootloader, but there's no guarantee that they will keep doing that it Google tightens down security further.

Take a look here for more details:

https://www.xda-developers.com/magisk-no-longer-hide-bootloader-unlock-status/
[Magisk] theCroh:
Would that tighter implementation break every SafetyNet-using app on older phones even when they are completely stock?
[Magisk] Didgeridoohan:
Only Google would be able to answer that... To make SafetyNet completely secure they would have to enforce hardware key attestation though.
[Magisk] zzahkaboom24:
i tried that module out but by installing it my cts shows false even if it was true before. in /proc/cmdline my verifiedbootstate is orange. in /data/tmp a file was created but its blank. nothing in it. also a build.prop was created there but i dont think its because of the module. now i want to know what happened and where to get which logs from so i can attach them?

Edit the only logs the terminal shows me i have to send are from safetypatch.debug. i got a dmesg.log a log.txt a open_gapps_log.txt a recovery.log and a safetypatch.debug. which one should i attach? or which one belongs to that module so i can attach that?
[Magisk] Zefiro_1980:
Thanks hackintosh5,

only with your patch I managed to pass the SafetyNet on my Samsung Galaxy S6 (SM-G920F) with Android 10 (LineageOS 17.1). For safety I installed your "SafetyPatch" from the TWRP Recovery.

...I try with Android 9 (LineageOS 16.0) but it doesn't work in any way...:(

Instead with LineageOS 16 (Android 9) only with the module of "hackintosh5" I managed to pass the Google SafetyNet but with each restart of the mobile gives me a bad system error.
[Magisk] eric00x:
This fingerpint is too old for Xiaomi Redmi Note 8T EU with UNOFFICIAL LineageOS 17.1 from Febuary and does not pass SafetyNet at this moment. Use MagiskHide Props Config's fingerprint instead.
[Magisk] Didgeridoohan:
[MENTION=8556932]hackintosh5[/MENTION] With a whole bunch of reports of SafetyNet failing both CTS, and basic integrity and also reports of passing at least basic integrity by uninstalling Safetypatcher, I did some testing.

Seems like Google updated SafetyNet with some new checks and your /proc/cmdline bind mount is now a sign of a tampered device. Both SafetyNet checks change to pass if those two lines are removed from your post-fs-data.sh.

Edit: for those that have been guessing, it has nothing to do with the included fingerprint.
[Magisk] dpj52190:
Can you post which lines to remove in your comments please?

---------- Post added at 11:45 AM ---------- Previous post was at 11:37 AM ----------

can you post which lines to remove please ? i'm looking at v4.0.1 and its hard to find https://github.com/kam821/safetypatch/releases/tag/v4.0.1
[Magisk] Didgeridoohan:
Hadn't seen that version of Safetypatcher before... With that one it should just be a matter of setting the CMDLINE_REPLACE_ENABLED variable in safetypatch_conf (in the module directory under /data/adb/modules) to false.
[Magisk] dpj52190:
Hi everyone, for those coming here after recent updates from google and now you have ctsProfile: false or basicIntegrity: true/false

I followed on the above suggestion by Didgeridoohan and it works!

Here's what I did:

Download a root explorer, Download safetypatcher v3 from magisk manager

After installing/ before rebooting. Go to root explorer /data/adb/modules_update/safetypatcher/post-fs-data.sh need to edit this file and delete first occurrence of line

'mount -0 bind /data.........'

reboot phone,

clear data of google play framework, google play, and google pay.

another reboot

go to magisk manager and check safety net. it should work now.

**If its hard to edit file in /data/adb/modules_update/safetypatcher/. Then cope the file to your downloads folder. edit the file and paste the file back to original location. You'll need to set permissions on the final destination file. it should be -rw-r--r-- or same as other files in that folder.
[Magisk] UnMarsmallow:
It works, but safety pass only sometimes.
[Magisk] amelsfort:
I want to try these steps, but when I open the post-fs-data.sh file, line #17 starts with 'resetprop'. And two others start with 'mount -o bind /data....', so I'm not sure which one to delete/comment out.

I also tried version 4.0.1 mentioned above, but that didn't work (even after changing the file): Magisk keeps telling me the ctcProfile test fails.
[Magisk] TheDevil259:
I just tried it and it worked. You need to comment out the first occurrence of the line, namely "mount -o bind /data/local/tmp/cmdline /proc/cmdline", which is line 11 for me.
[Magisk] HippoMan:
Just to be clear: the above instructions work for v3.x. However, there is not even a /data/adb/modules_update directory when v4.0.1 is installed.

For v4.0.1 ...

- Uninstall SafetyPatch v3 module

- Install SafetyPatch v4.01

- Edit /data/adb/modules/safetypatcher/safetypatch_conf and set config variable CMDLINE_REPLACE_ENABLED=false

- Clear app data for Google framework, Google Play Store, and Google Pay

- Reboot

However, v4.0.1 didn't work for me any better than v3.x, regarding SafetyNet.

.​
[Magisk] Swierk:
for 4.01 please make some more reboots (as I remember I did)

- Disable EdXposed module

- Uninstall SafetyPatch v3 module or v4.01

- Reboot

- Install SafetyPatch v4.01

- Edit /data/adb/modules/safetypatcher/safetypatch_conf and set config variable CMDLINE_REPLACE_ENABLED=false

- Reboot

- Clear app data for Google framework, Google Play Store, and Google Pay

- Reboot

Sent from OnePlus 7 Pro, OxygenOS 10.0.3, TWRP 3.3.1-75, Magisk 20.4, Greenify 4.7.5, Modded Play Store 16.5.15, android core.java patched and SafetyNet pass OK
[Magisk] Didgeridoohan:
Just to clarify on that: modules_update is only available directly after installing a module and

before

rebooting. After that modules will always be found in the modules directory.
[Magisk] amelsfort:
I also tried v4.0.1 with changing the conf, but Magisk is still trying me the cts check fails. And the Play Store also says my device is not certified.

I'm on LineafeOS 17.1 on my Galaxy S10+.
[Magisk] acupunk:
V 4.0.1 is not working for me on OOS 10.3.2 oneplus 7 pro. Tried modifying files, wiping data etc... ? It was great while it lasted. Thanks for the hard work! I hope you get it figured out again. ?
[Magisk] douchewaffle:
Thought I'd wait a bit to ask but... is everybody failing SafetyNet even with Magisk Core-only mode? Without using any Magisk/EdXposed module for tampering w/ SafetyNet, I'm able to pass both checks... up until a few days ago I was passing both checks with Riru & Riru EdXposed but that's unfortunately no longer the case. The stench of Google really is akin to Apple these days, I don't see a reason to bother with Android anymore next device round... how long before both major players are equally wallgardened?

HTC 10 w/ Oreo 8.0.0
[Magisk] pndwal:
No, most have it working now by removing problem modules (like SafetyPatch, unless manually edited files manually as described in last posts here - I prefer to use MagiskHide Props Config module instead), and by using latest fixed EDXposed Canary builds.

Google's changes were / are bound to occur.

Read back in this thread: https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/ PW
[Magisk] a_khusairi:
SafetyNet check in magisk 20.4 with the latest canary Edxposed and Edxpose manager
[Magisk] pndwal:
MOD EDIT: QUOTED POST REMOVED

:confused: - Please read last two posts here (right before yours). Enjoy EDXposed (for now). PW
[Magisk] douchewaffle:
Don't rely on MagiskManager SN check, use an actual SafetyNet attestation app that reads the result from google remote servers. It's game over pal

It doesn't matter what module you use to "fakepass" SN, at the end of the day its a fake pass, any app that relies on remote response and not whats fakecached on the device, poop game over
[Magisk] pndwal:
Well you're partially right.

SafetyPatch and MagiskHide Props Config do use spoofing techniques, but Googles server end still sees and recognises these results (and SafetyNet check apps you mention will still return a passed result), so securitycentric apps including many banking apps, Netflix etc do appear in Playstore and work with these fixes, so the game is not over quite yet.

Of course, this will only be the case till Google implements their hardware key attestation which queries bootloader state directly, and, of course, they have recently demonstrated this ability. Then it will likely be game over.

Xposed modules that give CTS pass on the other hand, do give a wholly fake pass (even in Magisk SafetyNet check as you say) and these will return a failed result from Google's servers (unlike SafetyPatch and MagiskHide Props at present). This is because Google's servers still see original uncertified device fingerprint etc in this case, but Magisk SafetyNet check sees fake cached result.

The new basicIntegrity checks are another thing, and are now seeing unusual bind techniques etc employed by SafetyPatch and a few other modules as well as Xposed framework. MagiskHide Props Config and latest Canary EDXposed (fixed) are fine however.

This is what I thought you were actually concerned about, and I was just letting you know that you can in fact keep EdXposed and SN, and directed you to references / thread with details. That is to say: You CAN still have your cake and eat it too... but probably not for long. PW
[Magisk] douchewaffle:
Thanks, seems to be okay with canary, I assume for a short time. I hate google so much
[Magisk] amelsfort:
Yes, I have. I also got a lot of errors in the Google Play Store: DF-DFERH-01. When I turned Hide off and rebooted, the store was working fine again, although being not certified and not showing Netflix. :(
[Magisk] douchewaffle:
After re-getting SN to pass, I cleared data for play store, play services, and g services framework & reboot, status changed from uncertified to certified.
[Magisk] amelsfort:
Unfortunately I never managed to fully pass SN. According to Magisk the ctsProfile test always fails. Now, with Hide disabled, both tests fail. But at least the Store works now, just not certified.