Database Develop

[SafetyNet Fix][PoC] Pass SafetyNet after 2017-07-17 on Magisk V13

EDIT: Official fix is out, please follow this link: https://forum.xda-developers.com/showpost.php?p=73079059&postcount=25
Good evening,
since Google broke all our beloved SafetyNet passing phones I decided to have a look at it. Turns out they have extended their property scanning.
There is an easy fix BUT: I have no idea how this fix interferes with Magisks internal behavior. @topjohnwu Why are properties used for magisk internals?
SafetyNet checks now for these properties, so we have to delete them:
Code:
[init.svc.magisk_pfs]: [stopped]
[init.svc.magisk_pfsd]: [stopped]
[init.svc.magisk_service]: [stopped]
[persist.magisk.hide]: [1]
EDIT: @dimon222 had a look at magisk source and answered my question why these properties even exist:
BTW, I shortly check'd source of Magisk, it seems 3 of those flags are related to exit code after start of Magisk services on boot. Basically, they're automatically set by Android when service with such name is started.
I guess dev will probably rename those services to avoid detect or hide it somehow.
https://github.com/topjohnwu/Magisk/blob/master/scripts/init.magisk.rc
And the last flag is some internal for Magisk.
It feels like something serious, but I don't know if its only used during boot. Maybe if u reset it after boot, it won't be automatically reloaded by Magisk, and it will continue to use hide.
https://github.com/topjohnwu/Magisk/search?utf8=✓&q=MAGISKHIDE_PROP
Worth to check if SafetyNet apps are still working after that, not just SafetyNet check itself. Its quite possible that it won't hide, if it gets this property from global variable at realtime.
Click to expand...
Click to collapse
How to fix this:
1. This fix is only a temporary fix. You will have to apply it after every reboot.
2. Use a Terminal emulator app or adb to enter these commands.
3. Use resetprop to delete the properties - again: I have no idea how this interferes with magisk behavior!!!! Do this at your own risk:
Code:
su
resetprop --delete init.svc.magisk_pfs
resetprop --delete init.svc.magisk_pfsd
resetprop --delete init.svc.magisk_service
resetprop --delete persist.magisk.hide
Using Magisk Core mode? also execute this command:
Code:
resetprop --delete ro.magisk.disable
4. Optional/Not recommended: If you want to make this temporary fix more permanent, add all the required resetprop calls to a .sh file inside /magisk/.core/service.d/ and let magisk automatically execute the script for you every startup.
Troubleshooting if this didnt work:
Still doesnt work? Try this: https://forum.xda-developers.com/showpost.php?p=73056617&postcount=65
Check for other magisk properties using "getprop | grep magisk" and delete them as well (at your own risk!)
After deleting the properties SafetyNet check will pass again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What kind of functionality do you still have after this? Does magisk manager crash? Do modules work? Does su work?

Can you please explain in detail that how to do it.
Thanks

Would these persist through a flash-all without wiping the device? I still couldn't get safety net to pass after that.

ali.ahmad said:
Can you please explain in detail that how to do it.
Thanks
Click to expand...
Click to collapse
Looks like you just need adb shell or a terminal emulator on your phone, and su/root.

ali.ahmad said:
Can you please explain in detail that how to do it.
Thanks
Click to expand...
Click to collapse
Yes please, I'm a little lost too

ali.ahmad said:
Can you please explain in detail that how to do it.
Thanks
Click to expand...
Click to collapse
Type it into a terminal on your phone.

No luck

It worked for me, thank you.
Enviado desde mi SM-N930F mediante Tapatalk

Interesting. I'm curious, how were you able to detect what safety net is actually detecting?
I haven't tried your fix as it's not super imperative for me to get safetynet passing for myself just curious what you are using to find this stuff out.
Either way thanks for the work

Then, is these sure? I don't have a computer here to unbrick my phone.

Jolt420 said:
What kind of functionality do you still have after this? Does magisk manager crash? Do modules work? Does su work?
Click to expand...
Click to collapse
SU still works, Magisk hide seems to work as well (safetynet passes, so magiskhide has to work)
I don't use many modules, only AppSystemizer and this one still works
ali.ahmad said:
Can you please explain in detail that how to do it.
Thanks
Click to expand...
Click to collapse
You need to enter the commands either in a Terminal Emulator app on your phone or use adb to connect to your phone and then enter the commands.
Also keep in mind that the fix is only temporary, you need to apply the fix after every reboot.

Astur13 said:
Then, is these sure? I don't have a computer here to unbrick my phone.
Click to expand...
Click to collapse
It is only temporary. After every reboot you have to apply the fix again. So if it doesnt work/bug your phone simply reboot

Test_subj said:
No luck
Click to expand...
Click to collapse
please provide the output of
Code:
getprop | grep magisk
after applying the fix

Is there a way to load commands from a txt or something like that? It's a bit of a bother to manually enter it every time we reboot.

[email protected] said:
Good evening,
since Google broke all our beloved SafetyNet passing phones I decided to have a look at it. Turns out they have extended their property scanning.
There is an easy fix BUT: I have no idea how this fix interferes with Magisks internal behavior. @topjohnwu Why are properties used for magisk internals?
SafetyNet checks now for these properties:
Code:
[init.svc.magisk_pfs]: [stopped]
[init.svc.magisk_pfsd]: [stopped]
[init.svc.magisk_service]: [stopped]
[persist.magisk.hide]: [1]
How to fix this:
1. This fix is only a temporary fix. You will have to apply it after every reboot.
2. Use a Terminal emulator app or adb to enter these commands.
3. Use resetprop to delete the properties - again: I have no idea how this interferes with magisk behavior!!!! Do this at your own risk:
Code:
su
resetprop --delete init.svc.magisk_pfs
resetprop --delete init.svc.magisk_pfsd
resetprop --delete init.svc.magisk_service
resetprop --delete persist.magisk.hide
After deleting the properties SafetyNet check will pass again
Click to expand...
Click to collapse
Worked for me! Thanks!

ivanes82 said:
Is there a way to load commands from a txt or something like that? It's a bit of a bother to manually enter it every time we reboot.
Click to expand...
Click to collapse
You could store it in a .sh file on sdcard and execute the .sh file. (dont forget chmod +x)
It also might work to put the .sh file in /magisk/.core/service.d to let magisk automatically execute the script at startup, but im not sure if thats too early

Worked for me on the 6P. Magisk and root seem good so far.

[email protected] said:
You could store it in a .sh file on sdcard and execute the .sh file. (dont forget chmod +x)
It also might work to put the .sh file in /magisk/.core/service.d to let magisk automatically execute the script at startup, but im not sure if thats too early
Click to expand...
Click to collapse
Thank you very much. It is only as a temporary solution.

Worked for me on HTC 10, Magisk 13.2

Fail to login SnapChat -> MagiskHide Activated

I have activated MagiskHide
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but SN has failed ... And i dosn't can connect
If you would know how to make everything green
Thx

https://www.didgeridoohan.com/magisk

Didgeridoohan said:
https://www.didgeridoohan.com/magisk
Click to expand...
Click to collapse
I have Delt Xposed but I am using it :/

1. Delete snapchat.
2. Install again.
3. Go to magisk hide and check snapchat
4. Try to login.
5. If it won't help, unroot phone, login to snapchat and root again.
Redmi Note 4X RR 6.0.0 Tapatalk

voxan24 said:
I have Delt Xposed but I am using it :/
Click to expand...
Click to collapse
Disable Xposed -> reboot -> Check SafetyNet (should be green) -> Login to Snapchat -> Enable Xposed -> reboot -> enjoy
Works for me.

worked for me too (last post )
on note 4 8.1.0 ustom rom with last version of magisk at the time of this post

I have the issue that I can not login on snapchat with magisk installed.
Magisk manager is hidden (as you can see a part of the package name in the 3rd line of the magisk manager part)
Snapchat is ticked in the magisk hide
You can see that safety net is passing and still I can not login on snapchat until I uninstall magisk.
I tried using a snapchat build from october 2018 (non beta) and it didn't let me log in either.

FPSUsername said:
I have the issue that I can not login on snapchat with magisk installed.
Magisk manager is hidden (as you can see a part of the package name in the 3rd line of the magisk manager part)
Snapchat is ticked in the magisk hide
You can see that safety net is passing and still I can not login on snapchat until I uninstall magisk.
I tried using a snapchat build from october 2018 (non beta) and it didn't let me log in either.
Click to expand...
Click to collapse
Did you fix it?

pixelgasm said:
Did you fix it?
Click to expand...
Click to collapse
Nope, just uninstall magisk, login and reinstall it. Use a secondary user account to login into other accounts, apparently you don't have magisk there, so it isn't being detected.

How to use Snapchat with magisk (After Ban)
FPSUsername said:
Nope, just uninstall magisk, login and reinstall it. Use a secondary user account to login into other accounts, apparently you don't have magisk there, so it isn't being detected.
Click to expand...
Click to collapse
Follow these steps to use Snapchat with magisk -
1.) Update to latest Magisk stable build v20.0 - https://github.com/topjohnwu/Magisk/...gisk-v20.0.zip
2.) After updating magisk, Go to Magisk Manager > Magisk Hide and check/enable Snapchat and Google Services (all services have to be marked).
3.) Hide Magisk Manager by it self, go to Magisk Manager > Settings and "Hide Magisk Manager" so it will repack Magisk Manager with random name.
4.) Delete "busybox" binary from /system/xbin directory and install BusyBox module from Magisk Manager > Downloads.
5.) Clear data and cache of Snapchat, try to login this time, it will work for sure, if it doesn't, login to this and click unlock my account - https://accounts.snapchat.com/accounts/login?continue=https://accounts.snapchat.com/accounts/welcome
I have tried this myself and it works, my first main account was permanent banned on magisk canary build, After that I deleted that account and started out with fresh new account.
Tested on -
Samsung Galaxy S9+
Rom - Ulitamte Rom v11.3
Magisk - v20.0 (Stable)
Kernel - ElementalX

LELBOT said:
Follow these steps to use Snapchat with magisk -
1.) Update to latest Magisk stable build v20.0 - https://github.com/topjohnwu/Magisk/...gisk-v20.0.zip
2.) After updating magisk, Go to Magisk Manager > Magisk Hide and check/enable Snapchat and Google Services (all services have to be marked).
3.) Hide Magisk Manager by it self, go to Magisk Manager > Settings and "Hide Magisk Manager" so it will repack Magisk Manager with random name.
4.) Delete "busybox" binary from /system/xbin directory and install BusyBox module from Magisk Manager > Downloads.
5.) Clear data and cache of Snapchat, try to login this time, it will work for sure, if it doesn't, login to this and click unlock my account - https://accounts.snapchat.com/accounts/login?continue=https://accounts.snapchat.com/accounts/welcome
I have tried this myself and it works, my first main account was permanent banned on magisk canary build, After that I deleted that account and started out with fresh new account.
Tested on -
Samsung Galaxy S9+
Rom - Ulitamte Rom v11.3
Magisk - v20.0 (Stable)
Kernel - ElementalX
Click to expand...
Click to collapse
I hope you realize that it's an old post of mine. Ofc things changed in the past months. It seems to work fine if you just add snapchat to magisk hide. None of the other steps you mentioned are needed. I haven't tried it without the magisk hide, but I think that it will work as well.

Hello there,,
I am stuck in the same problem .. I did every step mentioned above and Safetynet check is always green & successful .. but still Snapchat is able to identify that I have Root on my device..
I can't find any real useful way that works 100% to hide the root. Snapchat allows me to login without problems but after like 2 - 3 days it send me a message that it will lock my account because of the " use of third-party app " ! .. Now my account is locked for 2 weeks and I read that it could be permanently locked !
I really need help .. I'm using ported samsung Note 7 fan edition ported Light Rom

aimmhr said:
Hello there,,
I am stuck in the same problem .. I did every step mentioned above and Safetynet check is always green & successful .. but still Snapchat is able to identify that I have Root on my device..
I can't find any real useful way that works 100% to hide the root. Snapchat allows me to login without problems but after like 2 - 3 days it send me a message that it will lock my account because of the " use of third-party app " ! .. Now my account is locked for 2 weeks and I read that it could be permanently locked !
I really need help .. I'm using ported samsung Note 7 fan edition ported Light Rom
Click to expand...
Click to collapse
Same problem here, I'm on Magisk v20.4 and i can't find a way to hide root to the latest Snapchat build with Android 9 even with Magisk hide activated on Snapchat and Google services.
As far as i remember, i never had this problem on Android 8 with Magisk v19.3 and Magisk hide activated.

Natizyskunk said:
Same problem here, I'm on Magisk v20.4 and i can't find a way to hide root to the latest Snapchat build with Android 9 even with Magisk hide activated on Snapchat and Google services.
As far as i remember, i never had this problem on Android 8 with Magisk v19.3 and Magisk hide activated.
Click to expand...
Click to collapse
Sad to know that you got the same problem..
Even the latest Magisk did not provide a solution for this issue.
For me the only way to use snapchat is to use a non rooted rom.. It works .. but Android phone without root is not interesting ..

aimmhr said:
Sad to know that you got the same problem..
Even the latest Magisk did not provide a solution for this issue.
For me the only way to use snapchat is to use a non rooted rom.. It works .. but Android phone without root is not interesting ..
Click to expand...
Click to collapse
I've finally found a way to make it working again !
This is what i've done :
1) Log-in to snapchat.
2) Root with magisk.
3) Magisk Hide: Snapchat, Google, Google Play Store, Google services framework, Google Play services.
4) Install Magisk module "MagiskHide Props Config" (needed to pass SafetyNet control: ctsProfile + basicintegrity).
5) Install Magisk module "HARDWARE OFF" (needed to reset SafetyNet evalType from HARDWARE to BASIC) : https://forum.xda-developers.com/showpost.php?p=83028387&postcount=40658.
6) Go to Magisk options and select 'Hide Magisk Manager' to repack magisk with a new name (needed to completely hide the root).
7) Make sure Signature Verification is not disable and that no patches have been installed to android via "LuckyPatcher".
8) If installed, pleas uninstall "RIRU" Magisk module and any "riru"-related modules.
9) If installed, please make sure to uninstall Xposed Framework or any variant (systemless_Xposed, EdXposed, etc...) and all modules from it.
10) Make sure to uninstall LuckyPatcher if you have it and delete all residual files.
11) If installed, please uninstall Busybox and re-install it systemless-ly via the magisk module.
12) Now run this script in termux to fix snapchat root-detection (this will clean up your system file structure so it'll not return any false positives) : https://pastebin.com/haHtch32
If everything is done correctly, you should be able to use snapchat again without any issues and also without to worry about being banned again. At least for now ^^
Hope this can help.
Btw, sorry for my bad english, it's not my native language.

Two Magisk Manager Apps in system tray. One force closes, the other does not.

I'm having an issue where Magisk Manager (among other applications) have two icons in the app drawer. I think this is due to one of them being a "system app" and the other just being a normal application.
The issue I am having is that the normal Magisk application force closes upon launching, while the system app is able to open, but does not have any options for installing zips from repos.
I am using a Moto Z Play on 8.0. I've tried completely uninstalling Magisk and reinstalling but did not have luck with this. I'm not sure what I can do to fix this issue?
Thank you for any help!
Here are some screenshots showing this.
The system tray showing both apps:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The app details for the system app (I noticed this app details is not substratum themed):
The app details for the normal app (I noticed this app details is substratum themed):
The system application showing that Magisk is installed:
But the system application showing no option to install from repos:

Uninstall both apps and reinstall with the apk from the release thread, and you should be good to go.

Thank you for the reply.
I have uninstalled both installations, and installed the v5.7.0 from the release thread. Unfortunately the application force closes upon launching. I actually started this uninstall/reinstall process due to this initial issue of the Magisk Manager force closing upon launch. From my searches this is usually fixed by clearing the applications data and cache and a reboot. However, for me those steps did not work.

One thing I find odd is that it says it "keeps stopping" but the application does launch just fine...
EDIT: Let me post back with some logcat details, once I figure out how to get those

Here is a link to the logs that I got via running ./adb logcat -v long > magisk.txt and then immediatly launching the application. I hope it is helpful: https://paste.ee/p/sJfvb

MrTissues said:
Here is a link to the logs that I got via running ./adb logcat -v long > magisk.txt and then immediatly launching the application. I hope it is helpful: https://paste.ee/p/sJfvb
Click to expand...
Click to collapse
There's this in there:
Code:
[ 07-06 16:34:52.493 29515:29536 E/AndroidRuntime ]
FATAL EXCEPTION: Thread-2 Process: com.topjohnwu.magisk, PID: 29515
java.lang.StringIndexOutOfBoundsException: length=441; index=-1
at java.lang.String.charAt(Native Method)
at com.topjohnwu.superuser.internal.StreamGobbler.run(Unknown Source:52)
Doesn't look too good...
I would be interested in seeing your Magisk debug log. If you're not already on Magisk v16.4 beta, please install that and provide the debug log that you'll find in /data/adb. It'd probably also be a good idea to run the uninstaller first and do a clean install (from which it would be interesting to see the install log).

Thanks!
Here are the logs for uninstalling Magisk, installing Magisk 16.4 beta, and then installing f2loopback fix (necessary for Moto Z): https://paste.ee/p/A9ZXz
Here are logs from Magisk itself: https://paste.ee/p/P5iyO
The need for f2loopback is maybe troubling, though I can confirm that this did work. I know Magisk is properly doing its thing b/c I am able to get root access (confirmation dialog appears) in apps like Solid Explorer so that I can provide these logs. Its just the Manager itself that has crash issues.

I see that a new version v5.8.0 was released of the Manager. Unfortunately the problem remains.
The beta version of Magisk v16.6 does not work on my phone, it causes boot loops. Maybe the f2loopback patch needs to be updated for it.

MrTissues said:
I see that a new version v5.8.0 was released of the Manager. Unfortunately the problem remains.
Click to expand...
Click to collapse
Could you provide a logcat from v5.8.0 crashing? Just to make sure that all the information collected is relevant?
The beta version of Magisk v16.6 does not work on my phone, it causes boot loops. Maybe the f2loopback patch needs to be updated for it.
Click to expand...
Click to collapse
You could test by going without the f2loopback module. It wouldn't be necessary for basic Magisk functionality, and then we'd knew if it was caused by the module or not.

Based on the orange icons, you have some things installed under your work profile as well. That's why there's 2.

I've had problems Magisk disappearing on my OnePlus 5T. I've run the Uninstaller in TWRP followed by 18.1. Now have two Magisks in the add drawer: one labelled 'Magisk Manager' which says the phone is rooted and all is well; the other (same icon) is labelled simply 'Manager' and says that Magisk isn't installed! As things stand, it's just a nuisance. Everything seems to work fine with the Magisk. I'm reluctant to uninstall the 'Manager' in case in brings down the other one, but I'd love to tidy it up.
Running OOS 9.3.

@chriscross
https://www.didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_Managers

[script&magisk][root]Disable analytics, app measurement, campaign tracking, etc

Attached is a reasonably simple script which disables (or enables) a number of services for application analytics, application measurement, facebook ads, firebase performance monitoring and a few more. The amount of services disabled depends on the applications which you have installed. In my case 430+ services were disabled when running the script. This will increase security and possibly improve battery life a bit.
You must be rooted to use the script. The script code is pretty simple, have a look.
Download the attached file, rename and remove the ".txt" extension.
Instructions to install/use:
Code:
# push the script to your phone using adb
> adb push dss /sdcard/
# go onto your phone
> adb shell
# switch to root
% su
# mount /system as read-write
% mount -o remount,rw /system
# copy the script to the /system/bin/ directory
% cp /sdcard/script /system/bin/
# make sure it is executable
% chmod 755 /system/bin/dss
# execute the script
% dss disable
# output printed to the screen
% reboot
To enable the services again just run the script with argument "enable".
Alternatively, flash the attached magisk module from within the Magisk app. It will achieve the same effect.
Note that the magisk module will run for quite some time in the background whilst your phone is already fully booted.
To check what the module is doing, do:
Code:
> adb shell
% su
% tail -f /data/adb/modules/dss/log
When it has finished you will see "-- done" in the log.

Welkom :good:
I suggest to make a magisk module of this script to make it user friendly.
Keep up the good work old friend

Great to see you again, good idea to make it into a module. Will look at it tomorrow.

Good to see! Look forward to the module, Cheers

Can't you just run the script using EXKM?

For the ones who want to see if you have any of those apps (basically see if you need it/ if the custom kernel or Magisk module already hasn't disabled them).
Run this in Minimal ADB or whichever ADB tool you prefer:
Bash:
- adb shell
- su
- PLIST=`/system/bin/cmd package list packages | grep -v Swift | sort | sed 's/package://g'`
for i in $PLIST; do
echo "$i"
done
This will list all packages you've installed, see if it has any of the packages mentioned above.

OK, I looked into making this a magisk module ...
Problem is that you only have to run the script once (with disable).
So it is not really something which needs to run upon every boot.
Therefore, a magisk module is a bit pointless IMHO.
Anyway, the magisk module is attached if you want to try it.

@foobar66
Is this safe to try on the 6T?

..Cory.. said:
@foobar66
Is this safe to try on the 6T?
Click to expand...
Click to collapse
Yes, no problem.

foobar66 said:
Yes, no problem.
Click to expand...
Click to collapse
Thanks brother, will try shortly!

can anyone report their findings on this? does it improve things?

best way to know is try it make backup to feel safe

So I just need to flash magisk module, reboot so it will be activated and then I can remove it?

I do not know if it improve anything but i had to reboot twice. After the first reboot nothing worked as expected. Now it seems to work normal

Updated OP with the magisk module.

Thanks a LOT - very good addition to AFWall
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 20:38 ---------- Previous post was at 20:29 ----------
foobar66 said:
OK, I looked into making this a magisk module ...
Problem is that you only have to run the script once (with disable).
So it is not really something which needs to run upon every boot.
Therefore, a magisk module is a bit pointless IMHO.
Anyway, the magisk module is attached if you want to try it.
Click to expand...
Click to collapse
Well, can I just delete the Magisk module after running it once?
---------- Post added at 20:56 ---------- Previous post was at 20:38 ----------
ATTENTION ANDROID 10 Users: not working on Q-Beta 4

does this play nice if I have oxytweaker module which already disables some of the logging and analytic stuff?

Thanks. Look forward to trying this. If we want to reverse the module do we just delete it from Magisk? Thanks

carro_d said:
does this play nice if I have oxytweaker module which already disables some of the logging and analytic stuff?
Click to expand...
Click to collapse
i would say it does the same, its just another approach
and oxytweaker also changes some build prop stuff, so this is like the "light" version, thats focussed on the analytic stuff

Would this break safety net? Thanks!

How to make Gpay work in a Rooted system (At least, worked to me)

1 – Patch Magisk Canary V21 on Recovery.
2 – Go to Magisk, tap settings and activate MagiskHide.
3 – At MagiskHide tap search icon > show system apps and hide the bank´s app, Google Pay, Google Play Services (Tap the "Google Play Services" text to expand several more options. Here, make sure the switches next to each hook are enabled.), Google Play Store.
4 – Still in settings, hide Magisk Manager (For this, deactivate the Play Protect in Play Store settings).
5 – At the modules section, search and install:
-Busybox for Android NDK
-Riru (core)
-Riru – EdXposed
-GPay SQLite Fix (https://github.com/stylemessiah/GPay-SQLite-Fix/releases/download/v2.2/GPay.SQLite.Fix.v2.2.zip)
-MagiskHide Props Config
-SQLite for ARM aarch64 devices
-Reboot the smartphone
6 – Flash in magisk the Riru – EdXposed Canary (Try SandHook, if framework isn´t active, reinstall YAHFA version) (https://ci.appveyor.com/api/buildjo...sed-SandHook-v0.5.0.6_4587-master-release.zip
https://ci.appveyor.com/api/buildjo...Xposed-YAHFA-v0.5.0.6_4587-master-release.zip)
7 – Go to EdXposed Manager and confirm if EdXposed Framework is active, after that tap setings in the menu and active App list Mode, White List Mode, Force Hook Modules, Pass SafetyNet.
8 – At the menu, open the Applications(White List) and activate the Bank´s Apps, Google Pay and Google Play Store.
9 – At the menu, open the modules and install HiddenCore Module, RootCloak, activate them with the EdXposed Manager and reboot.
10 – Go to RootCloak > Manage Apps > Plus (on the side of 3 dots) > Add Custom Apps > Now select all the bank´s apps, Google Pay, Google Play Services and Google Play Store.
11 – Install Termux or any other termninal
12 – Download the Gpay-gms-patch.sh (https://github.com/davidramiro/gpay-gms-patch/blob/master/gpay-gms-patch.sh)
13 - Open terminal emulator or use adb shell and browse to the script's directory (e.g. cd /sdcard/Download/)
-Make the script executable with chmod +x gpay-gms-patch.sh
-Get SU permissions by entering su (confirm the Magisk prompt)
-Execute the script by entering sh gpay-gms-patch.sh
-Follow the on screen instructions.
-Reboot the device.
14 – Download and flash in Recovery GooglePay_fix_v2.zip (https://mega.nz/file/uhRzhIiY#IEREDUp8rLIiWWRlQvRkbxmtDBoc0jQwNjw77N-7QEs)
15 –Clear all data of Google Play store, Google Play services, Google Service Framework, Google Pay, then reboot the system.
16 – Finally, open Google Pay and add yours credit cards.

Hey, so i tried this method on my new S20 plus and when i try to install Riru – EdXposed i get an error in installing claiming that i don't have Riru (core) or i'm using the wrong version (or something like that).
I treid to continue with the rest of the steps but when i open the Edxposed Manager it says the framework is not active and the same result if i try to install the YAHFA version.
It all seems to tie back to me not being able to install Riru – EdXposed.
I'm running the latest Android 11 released recently and i'm rooted with Magisk 21.1.
Can you help?
EDIT: Here is a screenshot of the error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

N1ghtr08d said:
Hey, so i tried this method on my new S20 plus and when i try to install Riru – EdXposed i get an error in installing claiming that i don't have Riru (core) or i'm using the wrong version (or something like that).
I treid to continue with the rest of the steps but when i open the Edxposed Manager it says the framework is not active and the same result if i try to install the YAHFA version.
It all seems to tie back to me not being able to install Riru – EdXposed.
I'm running the latest Android 11 released recently and i'm rooted with Magisk 21.1.
Can you help?
EDIT: Here is a screenshot of the error
View attachment 5162389
Click to expand...
Click to collapse
Sorry answer only now, but yeah you can't install edxposed without install riru - core first... Did you try install riru - core first and what says?

Hi, yeah I have riru-core installed

N1ghtr08d said:
EDIT: Here is a screenshot of the error
Click to expand...
Click to collapse
I have the same issue on my S20FE (SM-G781B), what I think is the reason for the error is 'Riru - core' have been changed to just Riru and the version updated past 21.3. So your older version (0.4.6.4) of EdXposed isnt not compatible (or visa version) with Riru v23.
I am currently trying to find a copy of Riru - core v21.3 to test Edxposed 0.4.6.4 to see if it will even work. I say this because Riru v23 and EdXsposed (0.5.1.4) will install but EdXposed manager shows that the framework installed but not working.

spektroos said:
-Riru (core)
Click to expand...
Click to collapse
What version did you install?

b1k3rdude said:
I am currently trying to find a copy of Riru - core v21.3 to test Edxposed 0.4.6.4 to see if it will even work. I say this because Riru v23 and EdXsposed (0.5.1.4) will install but EdXposed manager shows that the framework installed but not working.
Click to expand...
Click to collapse
So found and installed Riru-core 21.3 and installed that along with 0.4.6.4 with out rebooting, and now I have a bootloop.