Related
Hello folks!
I have a weird problem with my rooted OPX 3.1.3. I'm still using this version because Xposed is not yet officially supported with the november patch (last time I checked, it was being tested).
I haven't been able to successfully hide supersu and Xposed with Chainfire's SuperSU (even tough I think it's very good!). So, instead, I'm using PHH's SuperSU 266-2 with Magisk v9 (and Xposed 86.6). As expected, I can use Android Pay (by hiding it with Magisk Hide functionality), but after a while, I lose the root access... I don't know what to do to cause the problem, I just know it happens. So, I can't give you a step-by-step to reproduce it, which makes it more difficult to diagnose.
A reboot "fix" this, but it's kind of annoying. As this happened to someone else? What could cause this kind of problem?
Thanks and let me know if you need more info!
Remove magisk manager from greenfy-like apps, close the androidpay app after using anf if possible keep magisk manager opened worked for me
My setup is SuperSU 2.78 SR4, suhide, magisk v9, rootswitch 1.3.3.2 and PoGo and Android Pay works. I used the ramdisk patch. Root is never lost.
gamer765 said:
My setup is SuperSU 2.78 SR4, suhide, magisk v9, rootswitch 1.3.3.2 and PoGo and Android Pay works. I used the ramdisk patch. Root is never lost.
Click to expand...
Click to collapse
Um magisk thosent do anything in that case as supersu is independent from it and su hide is the only thing doing anything in that case
Majesty00 said:
Hello folks!
I have a weird problem with my rooted OPX 3.1.3. I'm still using this version because Xposed is not yet officially supported with the november patch (last time I checked, it was being tested).
I haven't been able to successfully hide supersu and Xposed with Chainfire's SuperSU (even tough I think it's very good!). So, instead, I'm using PHH's SuperSU 266-2 with Magisk v9 (and Xposed 86.6). As expected, I can use Android Pay (by hiding it with Magisk Hide functionality), but after a while, I lose the root access... I don't know what to do to cause the problem, I just know it happens. So, I can't give you a step-by-step to reproduce it, which makes it more difficult to diagnose.
A reboot "fix" this, but it's kind of annoying. As this happened to someone else? What could cause this kind of problem?
Thanks and let me know if you need more info!
Click to expand...
Click to collapse
The "losing root" problem with Magisk Hide is known and under investigation. I saw someone claiming that they didn't experience it anymore after doing a complete uninstall of Magisk and starting over. Otherwise, the only solution at the moment is to reboot the device or disable Magisk Hide.
Xmaster24 said:
Um magisk thosent do anything in that case as supersu is independent from it and su hide is the only thing doing anything in that case
Click to expand...
Click to collapse
I'm giving him an alternative that works where he doesn't lose root spontaneously and need to reboot to fix.
gamer765 said:
I'm giving him an alternative that works where he doesn't lose root spontaneously and need to reboot to fix.
Click to expand...
Click to collapse
But magisk in your alternative those nothing it's completely inactive, he would only find magisk useful if he was using another module but not xposed as superSU plus systemless xposed always leads to SN fail
Majesty00 said:
Hello folks!
I have a weird problem with my rooted OPX 3.1.3. I'm still using this version because Xposed is not yet officially supported with the november patch (last time I checked, it was being tested).
I haven't been able to successfully hide supersu and Xposed with Chainfire's SuperSU (even tough I think it's very good!). So, instead, I'm using PHH's SuperSU 266-2 with Magisk v9 (and Xposed 86.6). As expected, I can use Android Pay (by hiding it with Magisk Hide functionality), but after a while, I lose the root access... I don't know what to do to cause the problem, I just know it happens. So, I can't give you a step-by-step to reproduce it, which makes it more difficult to diagnose.
A reboot "fix" this, but it's kind of annoying. As this happened to someone else? What could cause this kind of problem?
Thanks and let me know if you need more info!
Click to expand...
Click to collapse
+1
I have same issue. I randomly loose root and I have no idea why. I hope someone can help.
I also will try to disable the magisk hide and see if it helps.
FlintStoned- said:
+1
I have same issue. I randomly loose root and I have no idea why. I hope someone can help.
I also will try to disable the magisk hide and see if it helps.
Click to expand...
Click to collapse
I am having the same problem, but am not using the Magisk hide feature. Have to reboot to restore root - very annoying!
I disabled battery optimization on magisk and super user so we'll see if these fixes it or not.
Edit: as long as magisk hide is on this doesn't seem to help. It's a bug with magisk hide apparently.
I have noticed this twice, and it seems to be related to having the phone die from low battery? This is the only common condition I can recognize with the last two times it has happened.
Revenge282 said:
I have noticed this twice, and it seems to be related to having the phone die from low battery? This is the only common condition I can recognize with the last two times it has happened.
Click to expand...
Click to collapse
This happens to my phone and it's not died from having low battery.
Link_of_Hyrule said:
This happens to my phone and it's not died from having low battery.
Click to expand...
Click to collapse
Yeah, I let it die last night with Magisk Hide off, so that certainly seems to be the issue. I kept root and other modules after I turned it back on.
But even with Magisk Hide on, I never experienced any issues unless the phone died. I had rebooted it a ton of times and never lost any modules. I'm convinced that it has something to do with a "ungraceful" reboot situation and how Magisk Hide must unload itself.
Maybe that's an issue as well but my phone if I pick it up after it's been sitting there and charging or a good amount of battery and try to use root it says there isn't root unless I restart.
The same issue with Magisk hide on Xiaomi Redmi Note 3 Pro
Sent from my Xiaomi Redmi Note 3 using XDA Labs
Started experiencing this on Nexus 6p stock NMF26F. Predominantly happening overnight.
tzortst said:
Started experiencing this on Nexus 6p stock NMF26F. Predominantly happening overnight.
Click to expand...
Click to collapse
Also facing this problem on Nexus 6 (nougat 7.0.1).
In addition to this, when ROOT is lost, Magisk Log is empty.
It happens whatever the day/hour... it just seems to happen after a few hours without using the phone.
- Phone never dead due to battery empty
- android pay DISABLED
- PokemonGO not installed
- Android installed from a Factory Image (november patch NBD91P)
- Magisk V9 + phh_root_r266-2 (the only module)
- magisk hide ENABLED + magisk busybox DISABLED + systemless hosts ENABLED
- greenify installed, but neither Magisk Manager nor SuperSU in the greenified applications
lebaud07 said:
Also facing this problem on Nexus 6 (nougat 7.0.1).
In addition to this, when ROOT is lost, Magisk Log is empty.
It happens whatever the day/hour... it just seems to happen after a few hours without using the phone.
- Phone never dead due to battery empty
- android pay DISABLED
- PokemonGO not installed
- Android installed from a Factory Image (november patch NBD91P)
- Magisk V9 + phh_root_r266-2 (the only module)
- magisk hide ENABLED + magisk busybox DISABLED + systemless hosts ENABLED
- greenify installed, but neither Magisk Manager nor SuperSU in the greenified applications
Click to expand...
Click to collapse
Magisk log is empty because the Magisk Manager can't access the cache folder where it's located (no root, remember ).
It's a known bug, probably due to Magisk Hide being a little too aggressive.
I've noticed that I lose root every time I open Magisk Manager, so I've decided to hide it from to app drawer & have Greenified it in an attempt to stop it from running at all after initial boot - will report back if it works or not.
Edit: so I rebooted and haven't opened the Magisk Manager app since last boot and haven't lost root yet, so, so far so good. (15hrs 30m uptime) - will update if I do.
Edit2: haven't lost root in 2 days now, so looks like a temporary fix?
enabling Magiskhide caused me to lose root
I am a big idiot who can't follow directions I know and I will give many details so that someone may help me out of this situation.. please have patience.
I managed to unlock the bootloader, get custom recovery, and bypass dm verity on my new oneplus 3t a3000 running 4.5.1 stock. The issue is I rooted with supersu because that's what I'm use to and then flashed xposed into the system the old fashioned way (it's been a LONG time since I rooted and didn't really want to mess with magisk). I realize now that safety net has come to get me and I realized too late that magisk is superior.
I tried android pay and snapchat log in after rooting and flashing the 88.1 version of xposed framework and neither worked. I have everything almost but the safety net nonsense is annoying me because I use snapchat often but have to use another phone. I realize my stupid mistake in not flashing with magisk.
Besides being accustomed to supersu, you're wondering why I chose it and got xposed rather than magisk+ systemless xposed? I wanted to get certain modules such as youtube background playback and such quickly which I did but now I can't bypass safety net. I heard that even with safety net triggered, I could use Titanium Backup to move over a backed up version of snapchat that I had already logged in to my phone... problem is I had no backup and when I tried logging into my old rooted phones, snapchat refused to log in. I tried backing up snapchat on a non rooted phone through adb and moving that to the oneplus for Titanium Backup to restore but that didn't work.
So I guess my best bet is to disable root (uninstall supersu and xposed framework) and get magisk in replacement in hope that magisk hide works so I pass safety net then I can log in to snapchat and back it up. Can someone please guide me through the process? The amount I already know would imply I can figure this out but me trying to figure stuff out only caused much frustration today and yesterday.
In clarity, I want supersu gone (and xposed temporarily? I am not sure what is actually triggering snapchat to block me) and magisk in so I can pass safety net then I want (systemless xposed is what it's called? so I can add back my xposed modules). I am running blu spark twrp if that makes a difference.
Hugeee thanks to whomever can help me. Again I know I am dumb
If you want to pass safety net you will have to ditch xposrd all together. And magisk doesn't support bypassing safety net. It's one of those it may work but they are not making an active effort to get around it. Time is coming to make a choice. Mods or safety net.
Things triggering SafetyNet:
- root
- Xposed
- unlocked bootloader
- custom kernel (most of OP3/3T kernels already hide bootloader/kernel status)
- userdebug / dev-keys in build.prop
If you want to pass SN to log in to Snapchat, you have to remove root and Xposed, migrate to Magisk, log in to Snapchat and then install Xposed.
You can't use SN-enabled apps along with Xposed (although there is a module "No Device Check", which makes CTS return true, but for example Android Pay won't work still, because of basicIntegrity).
PS Look up iYTBP - this is a better version of YouTube with background playback built-in with no root needed.
Uninstall the xposed framework, login to snapchat and then reinstall xposed. You will have to repeat this process every time you logout, reinstall the app or clean flash a rom.
Edit- I see that you have supersu. I think you'll have to use magisk to pass safetynet.
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.
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.
I got a new banking app today that detects root, its https://play.google.com/store/apps/details?id=no.vipps.bankid
no problem with the Swedish bankid or other Norwegian banking apps. google pay/wallet works.
I tried blocking it in magisk block list. then with Shamiko, I'm afraid to test too many thing since google wallet is working now.
Try this modified USNF module. The issue you may be having is the new Play Integrity API.
I tried the previous version and now this one, still the same. I'm in no hurry to fix it, all other stuff work and the old bankid solution works 2 more years I think (hope)
I'm in your exact same position.
I have the MagiskHide module and used the DenyList, I also tried Shamiko, no luck for this app.
I tried the modified USNF module and no luck either.
I have several other apps where the above methods to avoid detection are working without problems, but not this one.
In the same boat as you guys. Also tried the modified magisk delta project with the old magisk hide, no luck.
Where is this?
SafetyNet is good, all other banking-and wallet-apps is working. RootBeer is not detecting root.
Oneplus 7t pro, stock latest stable rom. Magisk delta. Hide root from all apps. Renamed magisk app.
same problem here. tried everything i could find and no luck. might be a DRM problem? because 1 other issue i cant fix is apps like Netflix and prime video which are currently unusable because of DRM.
My app was updated today, and immidiatly after the update I tried activating/logging in, and to my surprise it worked. There is a one hour grace/waiting period to activate, and I'm currently waiting for that.
If it is not working after the wait, I will update this post. So if no update, it is working.
See my previous post in this thread about my setup.
jale said:
My app was updated today, and immidiatly after the update I tried activating/logging in, and to my surprise it worked. There is a one hour grace/waiting period to activate, and I'm currently waiting for that.
If it is not working after the wait, I will update this post. So if no update, it is working.
See my previous post in this thread about my setup.
Click to expand...
Click to collapse
same for me. so its probably okay for everyone for now. disable auto update on it now hahaha and lets hope it stays that way.
Can confirm, it works now without any change to Magisk or other modules.
I waited the 1h period and after that I was able to activate it and use it to login.
I am using Shamiko and a modified USNF module, but probably are not required.
Great to know that it's working now. But, for next time i can give u guyz some more option to keep in mind:
**renaming/deleting the "twrp/fox" folder of the recovery, deleting all files related to magisk or xposed. Also, hiding developer mode option by "devoptshide" from lsposed. **