Database Develop

Question [Solved] Root and Gpay?

Hi guys
I recently decided to root my Exynos S21U, all fine to far but I'm fighting to get Google Pay to work properly - so far without success.
Has anybody here got a rooted S21U with working Gpay and could kindly share what you did to make it work?
Thanks,
Axel

U dont need root to have google pay.
Download apk from here and install it on your device:
https://apkpure.com/google-pay/com.google.android.apps.walletnfcrel

Beso said:
U dont need root to have google pay.
Download apk from here and install it on your device:
https://apkpure.com/google-pay/com.google.android.apps.walletnfcrel
Click to expand...
Click to collapse
I don't think he's rooting to get Google Pay.
He wants a rooted phone, but is dealing with the side effect that it renders GPay un-usable.
Correct me if I'm wrong @s3axel
BTW @s3axel , have you tried Magisk Hide?

Yes, my device is rooted and I want to get Gpay to work
What I tried so far, all without success (of course all With Magisk Hide enabled for at least Gpay, Google Play Services and Google Framework)
- Magisk Stable
- Magisk Canary
- Props Magisk module
- Safetynet Fix 1.1.1
Funny enough everything is working fine in my other phone (Mi11U) with Magisk Stable and Magisk Hide enabled, nothing else...
Thus I was curious for reports from people who use their S21U rooted and with Gpay to learn what I need to do.....

s3axel said:
Yes, my device is rooted and I want to get Gpay to work
What I tried so far, all without success (of course all With Magisk Hide enabled for at least Gpay, Google Play Services and Google Framework)
- Magisk Stable
- Magisk Canary
- Props Magisk module
- Safetynet Fix 1.1.1
Funny enough everything is working fine in my other phone (Mi11U) with Magisk Stable and Magisk Hide enabled, nothing else...
Thus I was curious for reports from people who use their S21U rooted and with Gpay to learn what I need to do.....
Click to expand...
Click to collapse
It's possible to make it work (I'm on S21 Ultra 5G, latest Magisk canary, AUC8).
Follow these instructions to the letter and you'll get going ;-)
Working: Magisk with Google Pay as of gms 17.1.22 on Pie
Ok. I tried this and it worked on gms 17.1.22, allowing one to add cards and pay in store. Warning YMMV, but this is the process I did to get this working. One caveat is that I suspect users will have to reverse some step if gms is updated and...
forum.xda-developers.com
By the way, once you succeed in make it work, I suggest you update the thread title with something like [SOLVED] or [WORKING], so other newcomers can benefit from it

rodrigofd said:
It's possible to make it work (I'm on S21 Ultra 5G, latest Magisk canary, AUC8).
Follow these instructions to the letter and you'll get going ;-)
Working: Magisk with Google Pay as of gms 17.1.22 on Pie
Ok. I tried this and it worked on gms 17.1.22, allowing one to add cards and pay in store. Warning YMMV, but this is the process I did to get this working. One caveat is that I suspect users will have to reverse some step if gms is updated and...
forum.xda-developers.com
By the way, once you succeed in make it work, I suggest you update the thread title with something like [SOLVED] or [WORKING], so other newcomers can benefit from it
Click to expand...
Click to collapse
Thanks, this worked fine once I found the correct Magisk module
Just for reference flashing this module did its magic and kept the fingerprint in 3rd party apps working...

Question Does unlocking and flashing a custom rom mess up payment apps

With google coming up with increasingly stricter policies of what deems a device safe and rise of hardware attestation for safetynet, does the note 10 face these issues, or do the payment/banking apps work fine?

I have a Samsung A51 and once my device was rooted the Samsung Pass application will not allow me to record and use any security passwords or biometric security. The application gives me a message stating that because my device is rooted I can no longer use Samsung Pass. However, I am still able to use passwords and biometrics on my bank accounts application.

Last year, I changed the firmware of the LG V35 ThinQ I had and Google Pay would not work for me.

if it comes rooted yes , you will have to hide the root otherwise wont work

Everything works fine for me. I'm using a custom rom and I'm rooted. Play store shows my device is certified, and it passes safetynet on magisk.

TechV said:
Everything works fine for me. I'm using a custom rom and I'm rooted. Play store shows my device is certified, and it passes safetynet on magisk.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Same here

mite_jan said:
if it comes rooted yes , you will have to hide the root otherwise wont work
Click to expand...
Click to collapse
What is the best way to hide the root?

To hide root, enable magisk hide, and change the magisk manager to something else, like mgsk. I enable gpay in magisk hide, and even changed magisk manager to mgsk (You can use any name, but remember the name you change to), and I'm now able to access gpay. Works everytime.

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.

Looking for some tips - Unable to get these two Belgium apps working with Magisk

Hi,
I live in Belgium and it's been years that I'm using Cyanogen, then now Lineage. Recently, I made a bargain and bought 2 Google Pixel 4a, one for me and one for my girlfriend.
I installed Lineage on both of them, and I have to say that it's the best Android experience I had so far. We both love our device. It's small, powerful enough, camera pictures are amazing.
However, we are unable to get any banking apps working. We would like to use 2 applications:
1. Payconiq: https://play.google.com/store/apps/details?id=mobi.inthepocket.bcmc.bancontact&hl=en&gl=US
2. Keytrade: https://play.google.com/store/apps/details?id=be.keytradebank.phone&hl=en&gl=US
I succeeded to get Payconiq working on my phone, using Magisk 23 and Magisk hide. So far so good.
Since this morning, Magisk has been updated to 24.1, Magisk hide is gone and I have to use Magisk Zygisk... And Payconiq doesn't work anymore.
Regarding the second app "Keytrade", it never worked, with any version of Magisk. I don't know what they did in their app, but it seems that they were able to find a way to detect if a phone has a custom rom pretty nicely.
Maybe this is something that the author of Magisk should be aware of? Maybe I'm doing something wrong?
Do you have any piece of advice for me? I don't want to be forced to re-install the official rom, I still want to use Lineage and have those apps working.
Thanks!
Edit 1: After installing Universal Safetynet fix (https://github.com/kdrag0n/safetynet-fix), payconiq works, but not Keytrade.

Easiest way is to use a good browser like Brave to login to the bank's website bypassing the app.
I consider banking apps to be trash apps and never load them. The more needless apps you load, the greater the security risk.
Apps I sometimes use but don't like their behavior I package block when not in use and/or firewall block.
Rather than fight it, bypass it...

blackhawk said:
I consider banking apps to be trash apps and never load them.
Click to expand...
Click to collapse
Not helpful, because thanks to EU rules many banks simply and mandatorily require their app as the second authentication factor - especially when you don't want to use their "real" banking app and use the oldfashioned web interface instead.

Ramihyn said:
Not helpful, because thanks to EU rules many banks simply and mandatorily require their app as the second authentication factor - especially when you don't want to use their "real" banking app and use the oldfashioned web interface instead.
Click to expand...
Click to collapse
That sucks... so much for easy fixes

The Transporter said:
Hi,
I live in Belgium and it's been years that I'm using Cyanogen, then now Lineage. Recently, I made a bargain and bought 2 Google Pixel 4a, one for me and one for my girlfriend.
I installed Lineage on both of them, and I have to say that it's the best Android experience I had so far. We both love our device. It's small, powerful enough, camera pictures are amazing.
However, we are unable to get any banking apps working. We would like to use 2 applications:
1. Payconiq: https://play.google.com/store/apps/details?id=mobi.inthepocket.bcmc.bancontact&hl=en&gl=US
2. Keytrade: https://play.google.com/store/apps/details?id=be.keytradebank.phone&hl=en&gl=US
I succeeded to get Payconiq working on my phone, using Magisk 23 and Magisk hide. So far so good.
Since this morning, Magisk has been updated to 24.1, Magisk hide is gone and I have to use Magisk Zygisk... And Payconiq doesn't work anymore.
Regarding the second app "Keytrade", it never worked, with any version of Magisk. I don't know what they did in their app, but it seems that they were able to find a way to detect if a phone has a custom rom pretty nicely.
Maybe this is something that the author of Magisk should be aware of? Maybe I'm doing something wrong?
Do you have any piece of advice for me? I don't want to be forced to re-install the official rom, I still want to use Lineage and have those apps working.
Thanks!
Click to expand...
Click to collapse
How to pass SafetyNet on Android after rooting or installing a custom ROM
It is possible to pass SafetyNet, even after extensive modding like rooting or installing a custom ROM. Check out how to do that here!
www.xda-developers.com

Austinredstoner said:
How to pass SafetyNet on Android after rooting or installing a custom ROM
It is possible to pass SafetyNet, even after extensive modding like rooting or installing a custom ROM. Check out how to do that here!
www.xda-developers.com
Click to expand...
Click to collapse
Safetyfix passes on the phone... I don't know how the Keytrade app is doing to detect root on the phone.

blackhawk said:
That sucks... so much for easy fixes
Click to expand...
Click to collapse
So true Unfortunately, that seems the way to go in Europe considering banking. If you want it online instead of running to the bank clerk all the time, you're stuck with at least some authentication app. Things get only worse when there's no classical webinterface at all and you're bound to use a complete banking app instead (there are some neobanks doing so already).
The Transporter said:
I don't know how the Keytrade app is doing to detect root on the phone.
Click to expand...
Click to collapse
They simply recognize Magisk app in some way. I've read in some other threads here that a probable solution is to use the app called "Ice Box" to hide the Magisk app by freezing it. Might be worth a try for you.

Another way if you have zygisk enabled. Go to config denylist select play store play services gms you need to hit menu system apps first. And you apps you wish to hide. Then search magisk alpha telegram channel. Download shamiko module. Reboot your phone with enforce denylist selected. After reboot turn the enforce denylist toggle off and flash the shamiko module and reboot. If your app still does not work and you are using lsposed zygisk. You can download hide my applist Xposed module and further hide your app.
Pm me if you want to links to all as they are not supposed to be posted on xda

Have you managed to fix this?
I'm in the same boat.
My bank app 'keytrade bank' keeps detecting that I've rooted my device. This is what I tried
- I installed Magisk
- Installed module Shamiko
- Installed SafetyNet Fix v2.2.1
- Enabled Zygisk
- Configured DenyList
- Hide Magisk app

Awaces said:
Have you managed to fix this?
I'm in the same boat.
My bank app 'keytrade bank' keeps detecting that I've rooted my device. This is what I tried
- I installed Magisk
- Installed module Shamiko
- Installed SafetyNet Fix v2.2.1
- Enabled Zygisk
- Configured DenyList
- Hide Magisk app
Click to expand...
Click to collapse
You have to disable Enforce DenyList in Magisk.

Question How do I hide root from certain apps?

Hey, I rooted my phone just yesterday, and today I went to musescore just to see that they for whatever reason don't allow rooted phones to use their app?
So I tried enabling zygisk, DenyList, and I added musescore to the denylist and restarted my phone, but somehow musescore still knows that I'm rooted.
Is it possible that vbmeta is somehow related? if so then what file exactly am I supposed to flash as vbmeta (I use custom ROM).
If not, then what can I do to hide root from the app?

YayJohn said:
Hey, I rooted my phone just yesterday, and today I went to musescore just to see that they for whatever reason don't allow rooted phones to use their app?
So I tried enabling zygisk, DenyList, and I added musescore to the denylist and restarted my phone, but somehow musescore still knows that I'm rooted.
Is it possible that vbmeta is somehow related? if so then what file exactly am I supposed to flash as vbmeta (I use custom ROM).
If not, then what can I do to hide root from the app?
Click to expand...
Click to collapse
After force deny list did you've deleted caches of google play and google services and reboot? check also google play store inside settings if certified, if certified then it should work for your app too.

Maybe try installing Universal SafetyNet Fix?
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
And some applications can be extra finicky. LIke for me, Google Pay always takes its time to get persuaded about not being rooted. Also there might be other components either of this app or for system apps that might need hiding. I would generally try following guides for making banking apps work.

YayJohn said:
Hey, I rooted my phone just yesterday, and today I went to musescore just to see that they for whatever reason don't allow rooted phones to use their app?
So I tried enabling zygisk, DenyList, and I added musescore to the denylist and restarted my phone, but somehow musescore still knows that I'm rooted.
Is it possible that vbmeta is somehow related? if so then what file exactly am I supposed to flash as vbmeta (I use custom ROM).
If not, then what can I do to hide root from the app?
Click to expand...
Click to collapse
I'm not familiar with that app, but I know that some apps also check for the presence of the Magisk Manager app. If you've already tried Zygisk and the deny list, then another thing to do would be to hide the Magisk app. It the Magisk Manager, go to Settings > Hide Magisk app.

What worked for me is installing Insular ( from Fdroid) and then clone the App that complains about root to the work environment.

I just downloaded musescore and installed it. It hasn't detected root on my phone. I use Shamiko to hide root. Get Fox's magisk module manager from fdroid. Then use it to install Shamiko. Make sure you turn off Enforce Denylist in magisk so Shamiko can enforce the deny list. Hide the magisk app using the feature in magisk. It works for me.

YayJohn said:
Hey, I rooted my phone just yesterday, and today I went to musescore just to see that they for whatever reason don't allow rooted phones to use their app?
So I tried enabling zygisk, DenyList, and I added musescore to the denylist and restarted my phone, but somehow musescore still knows that I'm rooted.
Is it possible that vbmeta is somehow related? if so then what file exactly am I supposed to flash as vbmeta (I use custom ROM).
If not, then what can I do to hide root from the app?
Click to expand...
Click to collapse
Oh yes I can't seem to open musescore too even with safety net pass. But it is because I am using MicroG. I tried it on my other phone with Play Services and it works fine with hidden root (shamiko and magisk disabled) and safety net pass.

BigChungus321 said:
Oh yes I can't seem to open musescore too even with safety net pass. But it is because I am using MicroG. I tried it on my other phone with Play Services and it works fine with hidden root (shamiko and magisk disabled) and safety net pass.
Click to expand...
Click to collapse
I use MicroG as well. I can load the app and use it, I just can't subscribe because it requires GSF to make payment.

IrishJames said:
I use MicroG as well. I can load the app and use it, I just can't subscribe because it requires GSF to make payment.
Click to expand...
Click to collapse
You can open it right? But can you select and open a random piano piece or something like that. For me, the piece loads up then detects something (root, safety net idk) then just tells me I can't for root reasons. I tried using shamiko too and all the root hiding methods I know and I still couldn't open a piece. It does load the main menu for me too on MicroG+patch playstore but can't open the contents.

It's been roughly a month. Has anyone found a fix for this issue yet? There was discussion about the issue here where a dev 'fixed' the app for someone with a rooted phone. However I cant tell what the dev did because all his messages are deleted, for all I know he could of shared an apk or something, guess I'll never know. I've decided to try to get in contact with one of the people whose issue managed to get fixed, although I don't know if he'll ever respond. Apparently in the forum, he told the dev that he assumed the block was intentional. Maybe this could hint us towards a fix because maybe the block doesn't target rooted users?
BigChungus321 said:
I tried using shamiko too and all the root hiding methods I know and I still couldn't open a piece.
Click to expand...
Click to collapse
If thats the case then perhaps the app isin't checking for root? Theres no way musescore has more sophisticated anti-root software than some banking apps out there. Perhaps it's detecting the os that the user uses instead? I can confirm this because my samsung s7 edge with the same lineage os version as my Xiaomi doesn't want to play any scores either. This issue also happens to people who have no custom rom or even no root, it has to do with the os that you use rather than being an issue with root.
So what, did I type 2 paragraphs on a one month old forum just to rant? No. I will find the issue (well, I already found the reason in the text above), and I will try to fix it, not by making any workarounds such as cloning the app but getting the app to reliably work on a rooted / custom rom phone.
EDIT: Maybe using something to spoof the OS to make apps think it's a different OS?

POTENTIAL FIX: So in new versions of magisk, the developer decided to remove magiskhide. Turns out that having magiskhide turned on makes musescore actually be able to function. I tested this on my samsung s7 edge (didn't want to brick my Xiaomi phone by accident just yet and it worked. However I labelled this 'POTENTIAL' as downgrading magisk isin't really a plausible fix and could still be considered a workaround.

RoboNinjaR said:
It's been roughly a month. Has anyone found a fix for this issue yet? There was discussion about the issue here where a dev 'fixed' the app for someone with a rooted phone. However I cant tell what the dev did because all his messages are deleted, for all I know he could of shared an apk or something, guess I'll never know. I've decided to try to get in contact with one of the people whose issue managed to get fixed, although I don't know if he'll ever respond. Apparently in the forum, he told the dev that he assumed the block was intentional. Maybe this could hint us towards a fix because maybe the block doesn't target rooted users?
If thats the case then perhaps the app isin't checking for root? Theres no way musescore has more sophisticated anti-root software than some banking apps out there. Perhaps it's detecting the os that the user uses instead? I can confirm this because my samsung s7 edge with the same lineage os version as my Xiaomi doesn't want to play any scores either. This issue also happens to people who have no custom rom or even no root, it has to do with the os that you use rather than being an issue with root.
So what, did I type 2 paragraphs on a one month old forum just to rant? No. I will find the issue (well, I already found the reason in the text above), and I will try to fix it, not by making any workarounds such as cloning the app but getting the app to reliably work on a rooted / custom rom phone.
EDIT: Maybe using something to spoof the OS to make apps think it's a different OS?
Click to expand...
Click to collapse
Its not opening for me because I'm using MicroG. Like banking apps, MuseScore checks for specific Play Services version. Since microg uses idk android4.4 play services, it will fail to load any Banking Apps or apps of the same kind that uses that check regardless of root 'cause that version's too old and a potential for security. For the OS check, I guess it does check it too. I tried on two emulators and both failed to load a piece as well (might be because of safetynet cuz emulators can't pass it). There are xposed and magisk modules that can spoof OS and even prevent the app from seeing user installed apps. I haven't tried that method because I switched ROM now and got MuseScore working fine even without hiding root.

BigChungus321 said:
Its not opening for me because I'm using MicroG. Like banking apps, MuseScore checks for specific Play Services version. Since microg uses idk android4.4 play services, it will fail to load any Banking Apps or apps of the same kind that uses that check regardless of root 'cause that version's too old and a potential for security. For the OS check, I guess it does check it too. I tried on two emulators and both failed to load a piece as well (might be because of safetynet cuz emulators can't pass it). There are xposed and magisk modules that can spoof OS and even prevent the app from seeing user installed apps. I haven't tried that method because I switched ROM now and got MuseScore working fine even without hiding root.
Click to expand...
Click to collapse
Weird. I have microG and I managed to get musescore working without switching roms. All I did was use safety net fix, enabled zygisk and added it to the deny list. Tried it before and it didn't work, probably because I didn't install safetynet fix. Who knows, maybe it's related to what type of GApps you install. I guess this issue is fixed for now.