Related
It looks like it should with Magisk, but I can't seem to get it to work. I have pay hidden, using magisk 17.1 and passing safety net. It sticks at card verification. It says "verifying with bank", then kicks me to the payment screen where it says "verification needed". Clicking on that gives me a momentary waiting circle, but nothing else happens. I've tried it with 2 different cards. US998, RR oreo 8.1.
nola mike said:
It looks like it should with Magisk, but I can't seem to get it to work. I have pay hidden, using magisk 17.1 and passing safety net. It sticks at card verification. It says "verifying with bank", then kicks me to the payment screen where it says "verification needed". Clicking on that gives me a momentary waiting circle, but nothing else happens. I've tried it with 2 different cards. US998, RR oreo 8.1.
Click to expand...
Click to collapse
That's not an issue with Pay. If Magisk was being blocked by root/unlocked bootloader, you would get a message when you first fire up Pay that your phone can't be verified so "Google Pay can't run on this device".
Have you contacted your bank to make sure they support it? If it's not being verified with your bank, sounds like you need to call them. For the last few years, my bank didn't. It wasn't until this past year that they actually allowed it.
I'm not sure what the issue was. It wasn't with the bank(s). I was having the same issue with all the cards I tried. Eventually did a wipe and it worked.
nola mike said:
I'm not sure what the issue was. It wasn't with the bank(s). I was having the same issue with all the cards I tried. Eventually did a wipe and it worked.
Click to expand...
Click to collapse
Well that's weird. Glad it's working though! :good:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
If we want to reuse root features should we give phone permissions again ?
If we want to use Google pay again later should we re hide magisk and permissions ?
JackFrost said:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
Sent from my Redmi 4 using Tapatalk
Yes and No
cneeli78 said:
If we want to reuse root features should we give phone permissions again ?
If we want to use Google pay again later should we re hide magisk and permissions ?
Sent from my Redmi 4 using Tapatalk
Click to expand...
Click to collapse
Phone permissions have nothing to do with root features, I didn't exactly understand what do you mean by reuse root features but I don't recall any root solution app or framework asking for Phone Permission. If you are asking about granting phone permission to Google Play Services after Google Pay registration, you should do it, it's not recommended to deny phone permission to Google Play Services. And once you hide Magisk you don't need to change it's state as Magisk will continue to work as expected whether it's hidden or not.
JackFrost said:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
Click to expand...
Click to collapse
Yes it's working
JackFrost said:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
Click to expand...
Click to collapse
thanks.its working
You are welcome
Arokia said:
Yes it's working
Click to expand...
Click to collapse
Karthik Arun said:
thanks.its working
Click to expand...
Click to collapse
There is a thanks button you can press if I could help you
JackFrost said:
There is a thanks button you can press if I could help you
Click to expand...
Click to collapse
Am I doing something wrong? I did everything but when I deny phone permissions I get a pop up saying its required to open google pay and cannot get passed that
raguilera510 said:
Am I doing something wrong? I did everything but when I deny phone permissions I get a pop up saying its required to open google pay and cannot get passed that
Click to expand...
Click to collapse
Did you by any chance remove phone permission from Google Pay app? You need to turn off telephone permission from Google Play Services and Google Play Store. Google Pay app needs phone permission to verify the phone number, don't turn off phone permission from Pay, do it for only play store and play services. Hope that helped.
Does not work
Once I renable telephone permission for Google Play Services, googlepay does not work anymore. Asks me to register and then I cannot register as I dont pass the security test. I am on lineage os 15.1
Non rooted lineageOS
I am a real newbie but i do use google pay a lot.
Will google pay just work on lineageOS that wasnt rooted or with magisk install, only with an unlocked bootloader. Or will i need extra work to do before i can use it?
kekekelasomot said:
I am a real newbie but i do use google pay a lot.
Will google pay just work on lineageOS that wasnt rooted or with magisk install, only with an unlocked bootloader. Or will i need extra work to do before i can use it?
Click to expand...
Click to collapse
Extra work? There's no extra work to install Magisk. It's part of the instructions when unlocking the bootloader and installing TWRP. Magisk Hide (part of Magisk Manager) lets Google Pay work.
When you unlock the bootloader and install TWRP (which you need to install ROMs), the next steps in the process include flashing three files IN TWRP: the no root checker, the no encryption and Magisk. I'm not clear why you would just stop short of finishing the process.
Unless you use Magisk Hide, simply unlocking the bootloader will cause Google Pay to then fail -- even without installing TWRP or a ROM.
Unlocked bootloader by itself -- without Magisk Hide (a part of Magisk) -- will cause Safety Net to fail. Google Pay will not work.
Why do you want Lineage OS without root? That's like owning a car with internal combustion engine, but refusing to put in gasoline. (or refusing to charge a Tesla.) You can do it, but to me it doesn't make sense.
You might as well stay on stock unrooted firmware.
I have stock rooted firmware. I'm not using any custom ROMs -- but at least I have root and my Magisk mods.
ChazzMatt said:
Extra work? There's no extra work to install Magisk. It's part of the instructions when unlocking the bootloader and installing TWRP. Magisk Hide (part of Magisk Manager) lets Google Pay work.
When you unlock the bootloader and install TWRP (which you need to install ROMs), the next steps in the process include flashing three files IN TWRP: the no root checker, the no encryption and Magisk. I'm not clear why you would just stop short of finishing the process.
Unless you use Magisk Hide, simply unlocking the bootloader will cause Google Pay to then fail -- even without installing TWRP or a ROM.
Unlocked bootloader by itself -- without Magisk Hide (a part of Magisk) -- will cause Safety Net to fail. Google Pay will not work.
Why do you want Lineage OS without root? That's like owning a car with internal combustion engine, but refusing to put in gasoline. (or refusing to charge a Tesla.) You can do it, but to me it doesn't make sense.
You might as well stay on stock unrooted firmware.
I have stock rooted firmware. I'm not using any custom ROMs -- but at least I have root and my Magisk mods.
Click to expand...
Click to collapse
Thank you. Just flash magisk and hide google pay using it. From what i under stand is i have root access+ unlocked bootloader+ google pay functionalities. And the reason not to root is just because i want the feel of stock android+some nice modification
Recently had this problem with G Pay also. Found where some just deleted 'cache' and 'data' from Google Play and Play Services. That worked for me too. Of course hide Magisk etc first.
AsItLies said:
Recently had this problem with G Pay also. Found where some just deleted 'cache' and 'data' from Google Play and Play Services. That worked for me too. Of course hide Magisk etc first.
Click to expand...
Click to collapse
Thank you. That's all I had to do to get it working for me.
Hi, I'm not able to get Google Pay working on my rooted V30. I unlocked bootloader and flashed TWRP, no checker, no encryption, using chazzdave's WTF tutorial. Now have Havoc installed. I have hidden root from play, play services, and pay. I've hidden magisk by scrambling APK. I've cleared cache and data of play, play services, and pay. I've revoked telephone permission for play services and play store, although I had to re-enable play services telephone permission during card setup because pay wouldn't go any further. But nothing. Just error message that root is enabled and cannot proceed.
One of my banking apps which didn't work on root is working after hiding from magisk, but no Google pay. Has something updated and a loophole been closed?
Thanks
Forsh said:
Hi, I'm not able to get Google Pay working on my rooted V30. I unlocked bootloader and flashed TWRP, no checker, no encryption, using chazzdave's WTF tutorial. Now have Havoc installed. I have hidden root from play, play services, and pay. I've hidden magisk by scrambling APK. I've cleared cache and data of play, play services, and pay. I've revoked telephone permission for play services and play store, although I had to re-enable play services telephone permission during card setup because pay wouldn't go any further. But nothing. Just error message that root is enabled and cannot proceed.
One of my banking apps which didn't work on root is working after hiding from magisk, but no Google pay. Has something updated and a loophole been closed?
Thanks
Click to expand...
Click to collapse
Use Magisk v19. I believe it's a beta at the moment
This is Magisk/Xposed Module that allows for Full SafetyNet pass. All green checks with Xposed installed still. Requires Xposed installed on top of Magsik. I recommend Xposed through Magsik for dual systemless, but stand alone install of Xposed is fine. This is a first if it's kind for Magisk with Xposed for full green checks on SafetyNet Check. A game changer. Hope you enjoy . As I do what I can to help keep this epyk monster V20 alive.
Tested For 7.0. May work for others. Backup before testing.
Android 8.0 h910 works perfect.
Seems like it can't bypass logd being disabled.
Alpha Omega 8.0 w/ Magisk Hide enabled, logd disabled = fail.
Edit: Forgot to enable the module in Xposed in addition to Magisk. After enabling in Xposed, it now passes SN with the same parameters as above.
Great stuff!
Edit 2:
While there are now all green checks in Magisk's safetynet check, Google Pay still detects root/alteration.
nickthaskater said:
Seems like it can't bypass logd being disabled.
Alpha Omega 8.0 w/ Magisk Hide enabled, logd disabled = fail.
Edit: Forgot to enable the module in Xposed in addition to Magisk. After enabling in Xposed, it now passes SN with the same parameters as above.
Great stuff!
Edit 2:
While there are now all green checks in Magisk's safetynet check, Google Pay still detects root/alteration.
Click to expand...
Click to collapse
Idk...try using Magisk hide for that on top of this mod. I personally never use Google pay
Mysticblaze347 said:
Idk...try using Magisk hide for that on top of this mod. I personally never use Google pay
Click to expand...
Click to collapse
Have you confirmed that safetynet is actually being satisfied in any other apps that require it?
nickthaskater said:
Have you confirmed that safetynet is actually being satisfied in any other apps that require it?
Click to expand...
Click to collapse
I can only confirmed it passes in Magisk. Can't varify fully as to other uses as I really don't need full Safteynet. I just like seeing it pass and that is why I posted this. I usually don't need full Green for my use.
I do however know that it help with screenshot protection bypass for some banking apps ect.
Don't install it. It messes up with your google app and system apps. There is no turning back one you installed it, fastboot flash can only clean your mobile after that. There is a reason it was banned from official xposed modules.
atul18 said:
Don't install it. It messes up with your google app and system apps. There is no turning back one you installed it, fastboot flash can only clean your mobile after that. There is a reason it was bannejd from official xposed modules.
Click to expand...
Click to collapse
This is why it is controversial. I personally have not had any issues. This is also why I said I recommend "dual piggyback - systemless". I was sceptical myself, main reason for the Magsik mod. Systemless is better than embedded.
Mysticblaze347 said:
This is why it is controversial. I personally have not had any issues. This is also why I said I recommend "dual piggyback - systemless". I was sceptical myself, main reason for the Magsik mod. Systemless is better than embedded.
Click to expand...
Click to collapse
Someone pushing it into xda community silently.
If it was legit it will be on github. There is something wrong about this. If you have much knowledge about code I have a report file on this module. I will post it here.
---------- Post added at 07:39 PM ---------- Previous post was at 07:33 PM ----------
https://forum.xda-developers.com/xposed/modules/hiddencore-module-doing-t3903984/post79085117
Well again...this is systemless (no systematic attaching) disable at will. No footprint left behind. Once deleted its removed....it's fully gone. How can I explain systemless even further? I ment no harm with this thread as to why I made Magisk based. I just thought was sweet to pass SafetyNet in Magisk. I never thought to check SafetyNet app or even knew of stand alone apk.
If this really is as bad as you supposedly say, then I will delete this thread soon. My apologies in advanced if so.
I can't use apps that check safetynet.
It's failing in the response validation
Mysticblaze347 said:
Well again...this is systemless (no systematic attaching) disable at will. No footprint left behind. Once deleted its removed....it's fully gone. How can I explain systemless even further? I ment no harm with this thread as to why I made Magisk based. I just thought was sweet to pass SafetyNet in Magisk. I never thought to check SafetyNet app or even knew of stand alone apk.
If this really is as bad as you supposedly say, then I will delete this thread soon. My apologies in advanced if so.
Click to expand...
Click to collapse
Don't worry, the module is safe
Daved+ said:
I can't use apps that check safetynet.
It's failing in the response validation
Click to expand...
Click to collapse
Sorry it don't pass others other than Magisk it seems. Makes ya wonder where Magsiks SafetyNet is from. I personally don't know what else to say on this matter . I just ported, I didn't create the app. Just the Magsik Module is all I did. I'm in the same boat...but I'm keeping because I like seeing Magsik all Green. Also most likely due to a signature validation that was removed in my guess. Another version of a cloak if ya wanna say.
It's sad since the module removed from the repo, we can't expect update(s)
@Mysticblaze347. I'm using it with Magisk V19. Passes SafetyNet (ctsProfile + Basic System Integrity). Reported by Magisk Manager.
Tests from Any other App reports SafetyNet test Failed!!
So it seems like you only handled checks in setup.zip which Magisk Manager uses to report SafetyNet status!
Sorry.. I edited my Thank you post to this one.
I install it from xposed, and my exposed installed from magisk. Yes it made the magisk green, but my screen can't auto sleep. Uninstalled made normal again. From HTC U11 Android 8.0
A San said:
I install it from xposed, and my exposed installed from magisk. Yes it made the magisk green, but my screen can't auto sleep. Uninstalled made normal again. From HTC U11 Android 8.0
Click to expand...
Click to collapse
That version from Xposed itself does that, this version don't. Whole different area. Also, heads up. I just ported, not created. This also ONLY passes Magisks SafetyNet check for some reason. Why I do not know. I just made an optional port.
Already try install from this application. It won't work with my HTC U11 Android 8.0. Still red.
A San said:
Already try install from this application. It won't work with my HTC U11 Android 8.0. Still red.
Click to expand...
Click to collapse
This Magisk module was made initially for Nougat 7.0. I am running it and it's fine.
Did you check the Xposed side after Magisk install for active module?. Requires 2 reboot s total.. Magisk, then Xposed.
Best Version!
The version of this HiddenCore module is 1.3, which does not have the remaining awake bug found in version 1.7.
Mysticblaze347 said:
This is Magisk/Xposed Module that allows for Full SafetyNet pass. All green checks with Xposed installed still. Requires Xposed installed on top of Magsik. I recommend Xposed through Magsik for dual systemless, but stand alone install of Xposed is fine. This is a first if it's kind for Magisk with Xposed for full green checks on SafetyNet Check. A game changer. Hope you enjoy . As I do what I can to help keep this epyk monster V20 alive.
Tested For 7.0. May work for others. Backup before testing.
Click to expand...
Click to collapse
I have a rooted (magisk 24.3) Nord N10 5G, I have enabled zygota and installed the safetynet fix from github.
Using "yet another safetynet checker" app, my phone went from fail to pass in both SafetyNet checks.
I've also installed Snapchat and verified that it works (supposedly it shouldn't if you don't pass safetynet?).
However, Google Pay says "Phone does not meet security requirements"
So... is there any way to make it work?
AVAndronov said:
I have a rooted (magisk 24.3) Nord N10 5G, I have enabled zygota and installed the safetynet fix from github.
Using "yet another safetynet checker" app, my phone went from fail to pass in both SafetyNet checks.
I've also installed Snapchat and verified that it works (supposedly it shouldn't if you don't pass safetynet?).
However, Google Pay says "Phone does not meet security requirements"
So... is there any way to make it work?
Click to expand...
Click to collapse
Make sure you have Magisk Props Config, Universal Safetynet fix, and if those don't work try Shamiko https://t.me/magiskalpha
Download the latest Release.zip from telegram and install through Magisk. Then you'll have to enable the Denylist in the settings and then select Google Pay app and all your Google services and apps etc. Afterwards untick the "enforce denylist" since Shamiko will enforce your denylist now. Shamiko uses the Magisk list I believe but you must have it disabled after you're done selecting your apps like I said above.
JazzieBoi said:
Make sure you have Magisk Props Config, Universal Safetynet fix, and if those don't work try Shamiko https://t.me/magiskalpha
Download the latest Release.zip from telegram and install through Magisk. Then you'll have to enable the Denylist in the settings and then select Google Pay app and all your Google services and apps etc. Afterwards untick the "enforce denylist" since Shamiko will enforce your denylist now. Shamiko uses the Magisk list I believe but you must have it disabled after you're done selecting your apps like I said above.
Click to expand...
Click to collapse
Thank you.
For some reason, it did not occur to me that I should Denylist the Google apps. After I've added GPay to the list, it now passes all security checks., and I don't need any props config or Shamiko, just the Safetynet fix is enough!
AVAndronov said:
Thank you.
For some reason, it did not occur to me that I should Denylist the Google apps. After I've added GPay to the list, it now passes all security checks., and I don't need any props config or Shamiko, just the Safetynet fix is enough!
Click to expand...
Click to collapse
Okay I'm pleased to hear you've fixed it. Essentially, you'd only need Shamiko if you're having problems with certain apps like bank apps and things of that nature. Glad you can use GPay now. Enjoy your phone.
Is anyone one else having any issues getting GPay to work on the latest 11.0.10 security patch by chance?
I think I may have just done something out of order. I have 2 Nord N10 5Gs, one is on 11.0.0 and working fine, and I'm trying to setup the other one on 11.0.10 ... and I'm currently having issues.
I actually am able to get safetynet to pass the checks fine, but sometimes GPay seems to still insist that the "Phone does not meet security requirements". I even have zygisk enabled and GPay and services blocked.
One thing though, Google Play Services never stays checked in the Deny List for me. Does anyone else experience this too?
In general, it seems that with the latest security patch, i have to freeze the Magisk app otherwise several apps seem to detect it now, even with zygisk, hide, and renaming the magisk app package.
EDIT: The answer was too simple. MagiskHidePropsConfig, and spoof a valid device profile.
Please drop the new tutorial to get wallet and tap to pay working, in passing cts and safteynet, magisk denylist for gpay, wallet, and play services. USNF installed, magisk props, still can't get it working
Got it working, admin please delete
ne0ns4l4m4nder said:
Got it working, admin please delete
Click to expand...
Click to collapse
How did you get it working? Have the same issue and have everything installed
ogkillergreen said:
How did you get it working? Have the same issue and have everything installed
Click to expand...
Click to collapse
It's not working for me either. I tried everything.
Followed the root thread in P6 pro forum,
Wipe data of, wallet, Google play services, Gpay. Install the modded USNF I attached. Install magisk prop, in magisk blacklist, gpay, wallet, play store, Google framework. Reboot. It should work, worked for me
ne0ns4l4m4nder said:
Followed the root thread in P6 pro forum,
Wipe data of, wallet, Google play services, Gpay. Install the modded USNF I attached. Install magisk prop, in magisk blacklist, gpay, wallet, play store, Google framework. Reboot. It should work, worked for me
Click to expand...
Click to collapse
Thanks! it worked
Got the first half...not sure exactly how to do the second:
'Install magisk prop, in magisk blacklist, gpay, wallet, play store, Google framework. '
Still a bit noob-ish with my root/magisk kung fu...
He meant Deny list in Magisk, there you select the apps
Cheers
tom1807 said:
He meant Deny list in Magisk, there you select the apps
Cheers
Click to expand...
Click to collapse
Thanks Tom I was working so I was using text to speech while i was driving
I have a rooted Samsung SG10Exynos/OS9 that bypasses SafetyNet with the help of Magisk 26.0 & safetynet-fix-v2.4.0-MOD_1.2 (meets BASIC INTERGITY) that I have been using the Starling Bank app 2.92.1.79025 without an issue. I stupidly upgraded to the latest version and got the attached screenshot saying that I had 14 days to restore the device to factory settings (I was still able to use the app after pressing ok). I even more stupidly thought that I could revert back to the previous version that I was using, using Titanium Backup which failed (the app would just flash continuous on launch) and then Swift backup (where it would just repeatedly crash even even before being launched requiring a force stop)
If I wipe data/uninstall/restart phone and install fresh from google play, I now get the attached screenshot saying again to restore to factory, but the button says close app. So being a digital bank, I'm now locked out of my account.
I've tried to install previous versions from APKMirror mirror after wiping data/uninstall/restarting phone, and then just restoring my data with my Titanium/Swift backups but still no joy.
Does anyone know how to downgrade/install not the latest version of Starling Bank, which doesn't have the increased STRONG INTERGITY check?
nukescript said:
I have a rooted Samsung SG10Exynos/OS9 that bypasses SafetyNet with the help of Magisk 26.0 & safetynet-fix-v2.4.0-MOD_1.2 (meets BASIC INTERGITY) that I have been using the Starling Bank app 2.92.1.79025 without an issue. I stupidly upgraded to the latest version and got the attached screenshot saying that I had 14 days to restore the device to factory settings (I was still able to use the app after pressing ok). I even more stupidly thought that I could revert back to the previous version that I was using, using Titanium Backup which failed (the app would just flash continuous on launch) and then Swift backup (where it would just repeatedly crash even even before being launched requiring a force stop)
If I wipe data/uninstall/restart phone and install fresh from google play, I now get the attached screenshot saying again to restore to factory, but the button says close app. So being a digital bank, I'm now locked out of my account.
I've tried to install previous versions from APKMirror mirror after wiping data/uninstall/restarting phone, and then just restoring my data with my Titanium/Swift backups but still no joy.
Does anyone know how to downgrade/install not the latest version of Starling Bank, which doesn't have the increased STRONG INTERGITY check?
Click to expand...
Click to collapse
It will force you to use the latest app.
Block firebaseremoteconfig.googleapis.com
theoneofgod said:
It will force you to use the latest app.
Block firebaseremoteconfig.googleapis.com
Click to expand...
Click to collapse
Also having the same issue. Is this something I should be blocking in Zygiskhide? I can't see it there. Googling the above isn't helping me.
Undeadwolfy said:
Also having the same issue. Is this something I should be blocking in Zygiskhide? I can't see it there. Googling the above isn't helping me.
Click to expand...
Click to collapse
You could try Magisk Delta as it now acts as whitelist so you add only what you want with root. This won't bypass Starling security though. You need to also block address above.
Undeadwolfy said:
Also having the same issue. Is this something I should be blocking in Zygiskhide? I can't see it there. Googling the above isn't helping me.
Click to expand...
Click to collapse
Blocking this address (firebaseremoteconfig.googleapis.com) through AdAway has fixed it for me! That is along with all the things that were needed to run it previously.
theoneofgod said:
You could try Magisk Delta as it now acts as whitelist so you add only what you want with root. This won't bypass Starling security though. You need to also block address above.
Click to expand...
Click to collapse
I think the part where I'm stuck is, what would you suggest to block that address? I can't do that in HMA or in Denylist because it doesn't exist.
I've tried blocking in AdAway and manually adding and still getting Starling recognising root.
I've blocked anything Google Play Services, Play Protect, Wallet too. Starling is my main bank. Has only been an issue in the last couple weeks.
A13 P6 Pro running the April security update 13 (TQ2A.230405.003.E1), Magisk 26101, USNF 2.4.0 Mod 1.2, passing Safetynet Basic+ CTS.
Will look at Magisk Delta next.
marian42 said:
Blocking this address (firebaseremoteconfig.googleapis.com) through AdAway has fixed it for me! That is along with all the things that were needed to run it previously.
Click to expand...
Click to collapse
This isn't working for me :/. Can you share what other modules you're running/how you've set up Magisk?
I followed the directions in this video.
I didn't do the final step where he renames the Magisk app, seems that it isn't necesary.
The YASNAC app shows that the device passes "Basic integrity" and "CTS profile match".
Also remember that blocking firebaseremoteconfig.googleapis.com might break other apps that use this domain (I've found one so far).
Undeadwolfy said:
I think the part where I'm stuck is, what would you suggest to block that address? I can't do that in HMA or in Denylist because it doesn't exist.
I've tried blocking in AdAway and manually adding and still getting Starling recognising root.
I've blocked anything Google Play Services, Play Protect, Wallet too. Starling is my main bank. Has only been an issue in the last couple weeks.
A13 P6 Pro running the April security update 13 (TQ2A.230405.003.E1), Magisk 26101, USNF 2.4.0 Mod 1.2, passing Safetynet Basic+ CTS.
Will look at Magisk Delta next.
Click to expand...
Click to collapse
It's a recent update that broke it.
Try Magisk 26.1, enable Zygisk and enforce deny list. Add systemless hosts. Add only Starling to the deny list.
Install safetynet fix 2.4.0 mod 1.2 by displax.
Add the domain I posted to adaway blocklist. Make sure its enabled and in root mode.
theoneofgod said:
It's a recent update that broke it.
Try Magisk 26.1, enable Zygisk and enforce deny list. Add systemless hosts. Add only Starling to the deny list.
Install safetynet fix 2.4.0 mod 1.2 by displax.
Add the domain I posted to adaway blocklist. Make sure its enabled and in root mode.
Click to expand...
Click to collapse
That's exactly how I have it running now. No change.
Undeadwolfy said:
That's exactly how I have it running now. No change.
Click to expand...
Click to collapse
It's the domain that did it for me. Working fine as of now.
theoneofgod said:
It's the domain that did it for me. Working fine as of now.
Click to expand...
Click to collapse
Thanks for updating. I have both of these in my AdAway too
Code:
firebaseinstallations.googleapis.com
firebaseremoteconfig.googleapis.com
Nothing doing
Undeadwolfy said:
Thanks for updating. I have both of these in my AdAway too
Code:
firebaseinstallations.googleapis.com
firebaseremoteconfig.googleapis.com
Nothing doing
Click to expand...
Click to collapse
Clean install for Starling? I'm trying to think if I did something else.
Oh. Have you "hidden" Magisk?
Just to weigh in here, I can confirm blocking:
firebaseremoteconfig.googleapis.com
Does indeed allow the Starling app to work. Yes blocking Firebase is going to stop some applications working, but you could always pause AdAway until you are done using the problematic app then resume AdAway when you want to use Starling.
Many thanks @theoneofgod
Not working
Reverting the Starling app back to version 2.95.1.79953 fixes things - just don't forget to re-add it to the Deny List.
I'll probably stay on this version until a new fix is found for the current version 2.96.0.80202.
darsh said:
Reverting the Starling app back to version 2.95.1.79953 fixes things - just don't forget to re-add it to the Deny List.
I'll probably stay on this version until a new fix is found for the current version 2.96.0.80202.
Click to expand...
Click to collapse
Wild, even this didn't work for me. No idea why I'm having issues.
Hi All
Quick update - Can confirm that rolling back to 2.95.1.79953 does fix things for now
This is using adaway to block the Firebase URLs in a custom host file and using enforce denylist. It doesnt work beyond that for now.
I swapped over to Magisk Alpha for now but i dont know what Starling are doing in the background to see that you have root at this point. Its very annoying
- Edit 2
They seem to be detecting the Enforce Denylist in Magisk (In any form)
Disabling it on version 2.95.1 shows the app can see root. Enabling it allows the app to proceed as if you are not rooted.
Give KernelSU a try if you can. No modules or any workarounds required.
theoneofgod said:
Give KernelSU a try if you can. No modules or any workarounds required.
Click to expand...
Click to collapse
Isnt that the same as the setting in magisk that hides root from everything not on the su list. Which also doesnt work.