My banking app (NAB Mobile Banking), like most, doesn't like it if my phone doesn't pass CTS or if it's rooted when setting up tap-and-pay.
Since I've started using Magisk I've had lots of trouble getting this banking app to work properly.
This is how I have learnt to set it up .
1. Install Magisk. I'm using 15.3.
2. Wipe the app's data in Settings>Apps. But *do not* start the banking app!
3. Hide the app in Magisk.
4. Reboot the phone.
5. Set up the banking app.
At this stage it's usable but in order to be able to survive reboots and restoring from backups I do the following:
6. Hide Magisk Manager. If I don't do this the app will lose the tap-and-pay capability on reboot.
(Thanks @Didgeridoohan for the suggestion)
Old
6. Backup the app using Titanium Backup (TB).
7. Freeze the app using TB before rebooting the phone for whatever reason. If I don't do this the app will lose the tap-and-pay capability.
I take my backups in this state.
Once the phone has rebooted I then:
8. Defrost the app in TB.
9. Make the app the default for tap-and-pay as this gets lost by the freeze/defrost process.
If I have forgotten to freeze the app across reboots then tap-and-pay won't work. However I can:
10. Use TB to restore the app's data, set it as the default for tap-and-pay and I'm good to go.
End Old
The following actions will break the tap-and-pay function and require me to go through the setup process all over again:
a. Setting a new lock screen password, even it's the same as the previous one.
b. Wiping /data in TWRP because even though I restore the backup the lock screen password gets broken requiring me to do the following:
i. Run the following commands in TWRP Terminal to remove the current password before rebooting the system:
Code:
cd /data/system
rm gatekeeper.* locksettings.*
ii. Set a new lock screen password (see point (a) above).
My details:
Phone: OnePlus 3T
OS: OxygenOS 5.0.1
Root: Magisk 15.3, Magisk Manager 5.5.5
Banking app: https://play.google.com/store/apps/details?id=au.com.nab.mobile
Security: Password set and required on start up; fingerprint setup
You don't mention anything about hiding the Manager. Does that make a difference?
Didgeridoohan said:
You don't mention anything about hiding the Manager. Does that make a difference?
Click to expand...
Click to collapse
I never considered that.
I may try that to see if it makes a difference.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
I never considered that.
I may try that to see if it makes a difference.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
For some apps it makes all the difference...
If you haven't checked it out already, there's a bunch of tips like that in the troubleshooting guide.
Different but somewhat related: Since I'm on a custom ROM, Magisk Hide doesn't properly enable passing SafetyNet. The only way I could get it to work was to enable Magisk Hide for specific apps and to install the Universal SafetyNet Fix module (https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431). Maybe you could try that module too and see if it helps.
Didgeridoohan said:
For some apps it makes all the difference...
If you haven't checked it out already, there's a bunch of tips like that in the troubleshooting guide.
Click to expand...
Click to collapse
So, I tried hiding Magisk Manager and now I can reboot the phone without causing issues for the banking app. Thanks very much for the suggestion!
I did read [some of ] the installation and trouble shooting guide but, even now, I wouldn't have tried hiding the manager because my app can be set up properly without issues. It's only the reboot that caused problems. And hiding the manager has fixed this.
I've updated the OP to reflect this.
Sent from my OnePlus3T using XDA Labs
I am curious if anyone has gotten Chase Pay working with Magisk installed. I have turned off xposed ( which is known to fail safetynet), turned on magisk hide, did Magisk random package regeneration, and passed safetynet, but Chase Pay still gives me the error of having root on my phone. My Android Pay is working just fine since I pass SafetyNet, but Chase Pay doesn't.
c19932 said:
I am curious if anyone has gotten Chase Pay working with Magisk installed. I have turned off xposed ( which is known to fail safetynet), turned on magisk hide, did Magisk random package regeneration, and passed safetynet, but Chase Pay still gives me the error of having root on my phone. My Android Pay is working just fine since I pass SafetyNet, but Chase Pay doesn't.
Click to expand...
Click to collapse
You may have skipped a step. At this point, try clearing the Chase Pay app data, reboot, then run and sign into Chase Pay again. That is, once it has "seen" Magisk, it remembers it until you clear its stored data.
At least, that works for me. The only thing that doesn't work is fingerprint sign-on. When I enable that in Chase Pay, it complains that the devices is rooted, and will not enable this feature. The rest of the app seems to work, however. If anyone finds a solution to that issue, please share.
I also have no issues with Android/google pay but chase pay is giving the root error.
I have done steps 1-6 without chase pay working properly. Is there any way to check the chase pay error log and see where it is getting stopped?
I don't think I have ever rooted my Galaxy S7 and I don't even know how.
But I am getting rooted/Malware error with Chase Pay ( I can login but does not let me pay)
I checked with couple applications such as root checker and safteynet and both say that I am not rooted and my phone pass the safety test. Anyone know what the problem is? and how to fix it?
Chase Pay is also saying my phone is rooted. I get beyond the intro so Magisk hide is working to some degree. After that when tapping the pay button is when I get the error.
Tuxedo.Bond said:
Chase Pay is also saying my phone is rooted. I get beyond the intro so Magisk hide is working to some degree. After that when tapping the pay button is when I get the error.
Click to expand...
Click to collapse
Did you hide Magisk Manager (in Magisk Manager>Settings) before setting up Chase Pay?
Screenshot of the settings after hiding by the Manager attached.
Sent from my OnePlus3T using XDA Labs
Yes, hiding Magisk Manager did the trick. Thanks!
BillGoss said:
Did you hide Magisk Manager (in Magisk Manager>Settings) before setting up Chase Pay?
Screenshot of the settings after hiding by the Manager attached.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Hi
So I am about to try the same path for the NAB app. From reading the thread I need to
Magisk Manager
Hide for the app
hide the manager
clean the nab app data/cache
reboot
then start the NAB app'
tried that but app keeps crashing on attempting to create nab pay
EDIT
tried removing data/cache again - seemed to work.
So what happens if I unhide magisk manager ???
KeyzerSuze said:
Hi
So I am about to try the same path for the NAB app. From reading the thread I need to
Magisk Manager
Hide for the app
hide the manager
clean the nab app data/cache
reboot
then start the NAB app'
tried that but app keeps crashing on attempting to create nab pay
EDIT
tried removing data/cache again - seemed to work.
So what happens if I unhide magisk manager ???
Click to expand...
Click to collapse
If you unhide the manager, then NAB pay will stop working if you reboot.
I've also found that even with everything hidden, NAB pay will stop working after some time (a week?).
I've switched to Google Pay which works a lot better and doesn't require hiding the manager.
Sent from my OnePlus3T using XDA Labs
Didgeridoohan said:
You don't mention anything about hiding the Manager. Does that make a difference?
Click to expand...
Click to collapse
Thank you!
This is annoying the hell out of me. I can't get Chase Pay to work. I've gone into Titanium backup and deleted the data for the app. Went into app settings and deleted the storage & cache for the app. Made sure the app is hidden in Magisk and made sure Magisk is hidden. Rebooted phone and still says the app is detecting root. What am I doing wrong?
defens23 said:
This is annoying the hell out of me. I can't get Chase Pay to work. I've gone into Titanium backup and deleted the data for the app. Went into app settings and deleted the storage & cache for the app. Made sure the app is hidden in Magisk and made sure Magisk is hidden. Rebooted phone and still says the app is detecting root. What am I doing wrong?
Click to expand...
Click to collapse
Are you on Magisk 17.1 and have your removed the Magisk folder from your user storage (/sdcard)?
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Are you on Magisk 17.1 and have your removed the Magisk folder from your user storage (/sdcard)?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Yes. I'm on 17.1. No I didn't delete the folder. I'll try that.
defens23 said:
Yes. I'm on 17.1. No I didn't delete the folder. I'll try that.
Click to expand...
Click to collapse
Delete the folder, delete the Chase app storage, reboot.
Sent from my OnePlus3T using XDA Labs
Related
I recently rooted my new Mi A2 Lite using Magisk.
So my current banking app detected the root and now I cannot use it anymore. I tried Root Cloak and MagiskHide but both of them did not work either. It still shows the message saying my phone is rooted.
How do I debug that now. I need it to be working anyhow.
App: K-Plus; play.google.com/store/apps/details?id=com.kasikorn.retail.mbanking.wap
https://didgeridoohan.com/magisk/MagiskHideHidingRoot
arunsharmaofficial said:
I recently rooted my new Mi A2 Lite using Magisk.
So my current banking app detected the root and now I cannot use it anymore. I tried Root Cloak and MagiskHide but both of them did not work either. It still shows the message saying my phone is rooted.
How do I debug that now. I need it to be working anyhow.
App: K-Plus; play.google.com/store/apps/details?id=com.kasikorn.retail.mbanking.wap
Click to expand...
Click to collapse
I recently had the same problem, but with a different banking app.
What helped me in the past was to hide Magisk Manager with a random package name. It is an option in Magisk Manager itself. Unfortunately it doesn't work anymore but i could mask Magisk Manager with the Samsung app S Secure and now it's working again .
This was included in my Galaxy S7 ROM so you probably need to find the apk for the app or find a similiar working app for your phone model.
Hope this helps.
Daci54 said:
I recently had the same problem, but with a different banking app.
What helped me in the past was to hide Magisk Manager with a random package name. It is an option in Magisk Manager itself. Unfortunately it doesn't work anymore but i could mask Magisk Manager with the Samsung app S Secure and now it's working again .
This was included in my Galaxy S7 ROM so you probably need to find the apk for the app or find a similiar working app for your phone model.
Hope this helps.
Click to expand...
Click to collapse
Alright! Can you clarify what on how to hide Magisk with a different package name. I am still pretty new to Magisk. Thanks.
arunsharmaofficial said:
Alright! Can you clarify what on how to hide Magisk with a different package name. I am still pretty new to Magisk. Thanks.
Click to expand...
Click to collapse
Open Magisk Manager, go to settings and tap on Hide Magisk Manager. If your banking app doesn't work right away try a restart. If it still doesn't work try to mask Magisk Manager with S Secure or similiar apps.
The magisk hide feature does not work
nm180618 said:
The magisk hide feature does not work
Click to expand...
Click to collapse
It does work, the steps I took were:
1) Install Banking app
2) Open it and get notified about the phone being rooted
3) Use Magisk Hide feature to hide the Banking app
4) Go to phone's app settings
5) Baking app settings
6) Clear storage data (Clearing only the cache could work too, I didn't test it)
7) Profit!
Hope that works for you.
Magisk hide doesn't seem to be working for me. Magisk says it's working and safety net passes, but I've tested multiple apps and they can see that I'm rooted. Hiding magisk with a random package name doesn't work either.
Yesterday I installed magisk and went to hide options and checked my banking app. I was amazed to see banking app allowing me to do everything without limited functionality due to "root" like before. But today banking app detected root again and limited all functions, how? There haven't been any updates for banking app yet it seemed to no longer be fooled by magisk.
Same goes for me with the K-Plus app as well. (สวัสดีคับผม) Use Magisk Hide to hide the root access but it crashes the bank app instead.
Not sure what I've missed.
Gpay and banking are still detecting root/custom rom
Magisk and manager installed.
module SaMoDXv1 installed.
Safteynet is showing green
gpay and banking apps hidden
Using hide magisk function
removed all Magisk related stuff from SD card.
Cleared cache from gpay and banking apps .
Turned off usb debugging.
What else is there?
Just installed root checker basic, it sees root. I hide magisk from it and it still sees root. Is that right?
beythas said:
Same goes for me with the K-Plus app as well. (สวัสดีคับผม) Use Magisk Hide to hide the root access but it crashes the bank app instead.
Click to expand...
Click to collapse
Try following the 'Promon' section in https://github.com/Ingan121/UDSBypass
Hi,
I'ould like installing Fde.ai on my One plus 6 rooted with Ice Renovate 11.1 rom, but I'm not sure that installation is compatible with "Rice tweaks", a tweak app for this rom no my device.
Peraphs there is someone who does know the answer?
Tks and regards.
Roberto
What I do
Go to setting -> Magisk Hide -> disable then enable.
This way worked with me .
I used Magisk Manager v 7.2.0 (213).
Magisk v 19.3 (19300).
What worked for me is using the "Hide Magisk Manager" feature in settings. Now apps are not promoting about device being rooted and are running fine now.
Anyone solved this problem?
I still have a banking app with this problem. I tried many times but still not working.
Magisk hide dont work for this app.
nguyenlinh said:
Anyone solved this problem?
I still have a banking app with this problem. I tried many times but still not working.
Magisk hide dont work for this app.
Click to expand...
Click to collapse
So far there are very few apps that I've seen that can not be tricked with tips from the guide linked in the second post of this thread. Give it a shot...
Can you try it?
https://play.google.com/store/apps/details?id=vietcombank.itcenter.smartotpcorp
I Cannot run this app.
Thanks
nguyenlinh said:
Can you try it?
https://play.google.com/store/apps/details?id=vietcombank.itcenter.smartotpcorp
I Cannot run this app.
Thanks
Click to expand...
Click to collapse
Runs fine with the app on the Hide list and the Magisk Manager repackaged with a random name.
More:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Can someone check this for me?
https://play.google.com/store/apps/details?id=no.apps.dnbnor&hl=en_US
Iam using MH v60 with 19.3 still nothing. Iam fighting with that about 4 months now((((
I've been scratching my head for weeks now this app keeps on detecting root on my device. I've previously tried canary build, but currently on 20.1 and it still detects it. App is MagiskHided, Magisk Manager repackaged, both SafetyNet basicIntegrity and ctsProfile is passed. My other banking app that also checks for root works, even the rootbeerFresh is showing all green and this app still detects root. I don't know what else to try.
Device Info:
OnePlus 6T running Evolution X rom (Android 10), I also tried on OOS pie, doesn't work as well.
Magisk 20.1
This app used to work just by MagiskHide and repackaging Magisk Manager, since the update, I think they changed something. Any help is appreciated.
I tested it right now and had no issues starting the app once added to the Hide list. OnePlus 3T, Android 9 (ArrowOS), Canary build 20302 with hidden Manager build 269.
That means Magisk can hide from the app just fine and there might be something about your specific setup that's being detected. Could be an app, could be a directory on your storage, could be the ROM itself (this is the second time lately that I've seen a user having issues with root detection on Evolution X, on a Poco F1 though. May be unrelated.).
As always, there are a lot of hiding tips available here:
https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Didgeridoohan said:
I tested it right now and had no issues starting the app once added to the Hide list. OnePlus 3T, Android 9 (ArrowOS), Canary build 20302 with hidden Manager build 269.
That means Magisk can hide from the app just fine and there might be something about your specific setup that's being detected. Could be an app, could be a directory on your storage, could be the ROM itself (this is the second time lately that I've seen a user having issues with root detection on Evolution X, on a Poco F1 though. May be unrelated.).
As always, there are a lot of hiding tips available here:
https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Click to expand...
Click to collapse
DId you MagiskHide it beforehand or did you try without MagiskHide first? I want to make sure that the app doesn't "remember" that it has detected root previously
terraflops said:
DId you MagiskHide it beforehand or did you try without MagiskHide first? I want to make sure that the app doesn't "remember" that it has detected root previously
Click to expand...
Click to collapse
I made sure that it could detect root first, so I opened it once without adding it to MagiskHide (got the same screen you showed above). And, I did not have to clear any data for the app after adding it to the list, it just started up without issue.
terraflops said:
DId you MagiskHide it beforehand or did you try without MagiskHide first? I want to make sure that the app doesn't "remember" that it has detected root previously
Click to expand...
Click to collapse
any luck for this problem?
I also have this issue. Any luck?!
I have the same issue and finally found a solution for it ! Change the folder twrp name on internal storage was a trick but don't forget to hide the aplication go mobile from magisk hide then boom I can use the banking aplication on my root devices .
I'm not using any xposed so if you are on xposed try rename the folder of it usually it store on folder download on the internal if that doesn't work try to uninstal the xposed application on your mobile menu(you can instal it again after you're done with banking)
Another trick that I found latelly was I change the recovery ....any recovery besides the twrp (orangefox,pitchblack,batik etc)
Aldino21 said:
I have the same issue and finally found a solution for it ! Change the folder twrp name on internal storage was a trick but don't forget to hide the aplication go mobile from magisk hide then boom I can use the banking aplication on my root devices .
I'm not using any xposed so if you are on xposed try rename the folder of it usually it store on folder download on the internal if that doesn't work try to uninstal the xposed application on your mobile menu(you can instal it again after you're done with banking)
Another trick that I found latelly was I change the recovery ....any recovery besides the twrp (orangefox,pitchblack,batik etc)
Click to expand...
Click to collapse
Awsome maaan, like that simple trick could be solve the pricky app
Hey, i have a problem since my last update for my Banking App (VR-SecureGo; Update to 20.27.0 (from 20.23.0 i think)). The problem is that Magisk is getting detected even with Magisk Hide enabled, repackaged Magisk Manager and passing SafetyNet.
I don't know what can I do to bypass this root detection. I can't downgrade version anymore because the last version isn't supported anymore.
My specifications:
Device: Pixel 2 XL
Version: Android 11
ROM: Stock (Rooted with Magisk boot.img)
Installed Magisk: v22.1
Installed Magisk Manager Version: v22.1
Installed Magisk Modules: Universal SafetyNet Fix
(EdX/LS)posed: Not installed (anymore; tried to bypass detection with LSPosed and XPrivacyLua spoof, but don't work)
Edit: Before anyone refers me to the other posts, i've already seen them and tried their solutions, but none of them work
PS: Sorry for my bad english, I'm german
Did you try freezing the hidden magisk app prior starting the banking app?
This is the only working solution i could find for DKB Tan2Go.
JMaster7 said:
Hey, i have a problem since my last update for my Banking App (VR-SecureGo; Update to 20.27.0 (from 20.23.0 i think)).
Click to expand...
Click to collapse
The same here of course :-(
I tried all too, only restoring the last backups (made with swift backup) did help for now.
VR SecureGo, PSD-SecureGo and PSD.Banking app are affected.
These apps did work with Magisk 22.x and Edxposed.
ratelutz said:
Did you try freezing the hidden magisk app prior starting the banking app?
This is the only working solution i could find for DKB Tan2Go.
Click to expand...
Click to collapse
Can you please explain a bit more, what you mean?
Very simple:
Configure magisk hide, hide the magisk app, freeze the hidden magisk app, start your banking app
ratelutz said:
Very simple:
Configure magisk hide, hide the magisk app, freeze the hidden magisk app, start your banking app
Click to expand...
Click to collapse
Thx.
ratelutz said:
Very simple:
Configure magisk hide, hide the magisk app, freeze the hidden magisk app, start your banking app
Click to expand...
Click to collapse
Yes, this works but a little laborious :-(
Thank you.
tramp20 said:
Yes, this works but a little laborious :-(
Thank you.
Click to expand...
Click to collapse
Yes, annoying if done manually.
But this can be automated with Tasker.
As i tap (start) my banking app,
Tasker:
-kills it right again
-freezes the hidden magisk app
-and restarts the banking app
jokk3l said:
Yes, annoying if done manually.
But this can be automated with Tasker.
As i tap (start) my banking app,
Tasker:
-kills it right again
-freezes the hidden magisk app
-and restarts the banking app
Click to expand...
Click to collapse
And the most reliable and fastest method is using logcat reader and reacting on app started event
ratelutz said:
Very simple:
Configure magisk hide, hide the magisk app, freeze the hidden magisk app, start your banking app
Click to expand...
Click to collapse
i have similar problem with other app
so what do you mean by (freeze the hidden magisk app)
ratelutz said:
And the most reliable and fastest method is using logcat reader and reacting on app started event
Click to expand...
Click to collapse
This!
abogrhen said:
i have similar problem with other app
so what do you mean by (freeze the hidden magisk app)
Click to expand...
Click to collapse
Magisk Manager app can be hidden (repacked/renamed) to make it harder to be detected.
Freezing can be done via apps like airfrozen or via shell command "pm disable-user <PACKETNAME>"
jokk3l said:
This!
Magisk Manager app can be hidden (repacked/renamed) to make it harder to be detected.
Freezing can be done via apps like airfrozen or via shell command "pm disable-user <PACKETNAME>"
Click to expand...
Click to collapse
The hide already done
but the freezing is new to me
i will try
Thanks. Airfroze did help me to bypass root check.
ratelutz said:
And the most reliable and fastest method is using logcat reader and reacting on app started event
Click to expand...
Click to collapse
How can I do that? Freezing Magisk does work for me. The method jokk3l described is a bit buggy on my phone. I have to open the VR Banking app twice. But thank you jokk3l, that's better than doing evertyhing by hand.
Edit: YouTube helps! Thank you for posting your solutions!
Was there another update? I rooted just yesterday and can't get SecureGO to work at all.
I'm using Magisk 23.0 on Android 10.
I already renamed Magisk, activated MagiskHide and used airfrozen to freeze the renamed app, but SecureGO refuses to start
For me it works just fine with freezing Magisk.
Maybe you need to clear cache and data of securego first after you renamed and hid magisk!?
paulquappe said:
For me it works just fine with freezing Magisk.
Maybe you need to clear cache and data of securego first after you renamed and hid magisk!?
Click to expand...
Click to collapse
Tried freezing, then clearing data / reinstalling SecureGo and even then it doesn't start.. is there any way to check if other apps can "see" the root? I'm wondering whether MagiskHide even works at all..
I got same problem here but with another bank app, C6 Bank.
The way I could have it working with root is on Android 10. With Android 11 can't make it run anymore.
Hi @ all.
I had the same problem with the vr securego app. It helped to completely uninstall Magisk and reinstall it again. Then the work around works with the Magisk hide, Hide Magisk app and freeze. Many greetings
FreezyLemon said:
Tried freezing, then clearing data / reinstalling SecureGo and even then it doesn't start.. is there any way to check if other apps can "see" the root? I'm wondering whether MagiskHide even works at all..
Click to expand...
Click to collapse
Did you solve your issue with this app? Having LOS 18.1, Magisk 23.0 with MagiskHide and freezed the app by with Airfrozen but it does not work. Neither VRSecure-GO nor DKB-Tan2GO are working anymore
Hi
I have a problem in the clubhouse app that login not complete on any rooted device ... no problem on Non Root devices
I hide magisk app add clubhouse to magisk hide and EDExposed blacklist but still not working.
also, the same issue is in Mcdonald's app.
any idea how to solve these issues
Note: My Bank app works after adding it to magisk hide and hide magisk app, which means i did it right.
thanks
anyone help me please
Have you tried removing the Magisk app? That's a popular way of detecting Magisk, even with a repackaged app. It's practically impossible to completely hide it on anything below Android 11, and even then it's necessary for the app to target A11 for full hiding to work (which won't happen until Google enforces that, maybe later this year).
Of course, Xposed/EdXposed/LSPosed tools can probably be used to hide the app fully...
Didgeridoohan said:
Have you tried removing the Magisk app? That's a popular way of detecting Magisk, even with a repackaged app. It's practically impossible to completely hide it on anything below Android 11, and even then it's necessary for the app to target A11 for full hiding to work (which won't happen until Google enforces that, maybe later this year).
Of course, Xposed/EdXposed/LSPosed tools can probably be used to hide the app fully...
Click to expand...
Click to collapse
thanks for your reply
if i removed magisk .. everything that use root will stop and i don't want that
also can you please tell me how to hide the app fully using EDXposed
I did not say "remove Magisk"... I said "remove the Magisk app". Just uninstall the app and try and see if Clubhouse still triggers. If it works we know it's looking for the app and you'll have to either freeze/uninstall the Magisk app when using Clubhouse and then reinstall it again afterwards, or use one of the available isolation methods. I've got a few of those mentioned here, but I'm sure you can find more if you search (it's been covered a lot):
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Isolation_apps
zamlkawy said:
Hi
I have a problem in the clubhouse app that login not complete on any rooted device ... no problem on Non Root devices
I hide magisk app add clubhouse to magisk hide and EDExposed blacklist but still not working.
also, the same issue is in Mcdonald's app.
any idea how to solve these issues
Note: My Bank app works after adding it to magisk hide and hide magisk app, which means i did it right.
thanks
Click to expand...
Click to collapse
for Mcdonald's try this
[MOD][XPOSED][4.1+] McRoot (McDonalds Global App)
McRoot McDonalds Global App security fix Remove checks of: root unacceptable apps unacceptable device properties (developer options etc) Note: The app requests SafetyNet pass! Use Magisk+Riru+Riru-Unshare etc Install notes: install apk...
forum.xda-developers.com
Hi. I also have Magisk installed on my device. I uninstalled Magisk app, tried logging into clubhouse again, but still the issue persists.
After receiving the missed call while trying to sign in, I get the notification, 'There was an error please try again'
Clearing the clubhouse app data, uninstalling and reinstalling the app again hasn't helped at all. I get the same issue.
I have Magisk 23.0 installed on my Oneplus5T running Android 10.
I can't get anywhere with the AZ Mobile ID (https://play.google.com/store/apps/details?id=com.idemia.mobileid.us.az&hl=en_US&gl=US). I have a OnePlus 9 Android 11, rooted with stable v23. Passes Safertynet. Every other app works for me - banking (citi, wells fargo, amex), payment (paypal, venmo, cashapp), stores (wawa, quickchek, circle k).
The AZ Mobile ID app will not start at all. Click on the icon, and nothing happens - it like I didn't even click on it. It I click on it again, I get the android popup "AZ Mobile ID keeps stopping."
Has anyone gotten this app to work, or possibly another app by Idemia R&D?
mx597turbo said:
I can't get anywhere with the AZ Mobile ID (https://play.google.com/store/apps/details?id=com.idemia.mobileid.us.az&hl=en_US&gl=US). I have a OnePlus 9 Android 11, rooted with stable v23. Passes Safertynet. Every other app works for me - banking (citi, wells fargo, amex), payment (paypal, venmo, cashapp), stores (wawa, quickchek, circle k).
The AZ Mobile ID app will not start at all. Click on the icon, and nothing happens - it like I didn't even click on it. It I click on it again, I get the android popup "AZ Mobile ID keeps stopping."
Has anyone gotten this app to work, or possibly another app by Idemia R&D?
Click to expand...
Click to collapse
I have a Pixel 3a running Android 11, Magisk v23 stable and passes Safetynet. I also have the Magisk app hidden since I was having problems with another app giving warnings that my phone was rooted.
I was able to get the app working. I installed the app but did not open it. Then went to Magisk hide and hid the app. After hiding the app, you should be able to open the app. I did notice that I had to click on the app twice before it initially opened but that could have been my problem and not necessarily the app.
mx597turbo said:
I can't get anywhere with the AZ Mobile ID (https://play.google.com/store/apps/details?id=com.idemia.mobileid.us.az&hl=en_US&gl=US). I have a OnePlus 9 Android 11, rooted with stable v23. Passes Safertynet. Every other app works for me - banking (citi, wells fargo, amex), payment (paypal, venmo, cashapp), stores (wawa, quickchek, circle k).
The AZ Mobile ID app will not start at all. Click on the icon, and nothing happens - it like I didn't even click on it. It I click on it again, I get the android popup "AZ Mobile ID keeps stopping."
Has anyone gotten this app to work, or possibly another app by Idemia R&D?
Click to expand...
Click to collapse
If you have installed the titanium backup and/or AFWall then either hid them with HMA or uninstall in addition to adding AZ Mbile ID to the MagikHide and you will got it works as i did.
@desertcat and @Eng.Raman thank you both for the help. I followed both your suggestions, including deleting my twrp folder, hiding AZ MID in magisk, renaming magisk, freezing magisk manager with Airfrozen, and deleting TiBackup. Nothing helped so far, getting the same exact behavior as before - click on the icon, and nothing happens. Click again and get the android popup.
Would you mind sharing what modules you're running in Magisk? Maybe one of mine is causing the issue...
mx597turbo said:
@desertcat and @Eng.Raman thank you both for the help. I followed both your suggestions, including deleting my twrp folder, hiding AZ MID in magisk, renaming magisk, freezing magisk manager with Airfrozen, and deleting TiBackup. Nothing helped so far, getting the same exact behavior as before - click on the icon, and nothing happens. Click again and get the android popup.
Would you mind sharing what modules you're running in Magisk? Maybe one of mine is causing the issue...
Click to expand...
Click to collapse
I use Universal SafetyNet Fix (2.1.0), Riru, Riru Enhanced mode for Magisk Hide, MagiskHide Props Config, CloudflareDNS4Magisk, Universal GMS Doze and Systemless Hosts.
@desertcat Thank you so much. I was able to get that app working. I had to add the modules Universal SafetyNet Fix and Riru Enhanced mode for Magisk Hide. I also disabled busybox (although I don't know if this made a difference.
Funny that I had no problems with any other app that I used, and was able to pass safetynet with just MagiskHide Props Config and hide.
mx597turbo said:
@desertcat Thank you so much. I was able to get that app working. I had to add the modules Universal SafetyNet Fix and Riru Enhanced mode for Magisk Hide. I also disabled busybox (although I don't know if this made a difference.
Funny that I had no problems with any other app that I used, and was able to pass safetynet with just MagiskHide Props Config and hide.
Click to expand...
Click to collapse
Good to see that you were able to successfully get the app to work.
Without Universal SafetyNet Fix and Riru I wasn't reliably passing SafetyNet. Riru Enhanced mode for Magisk Hide helped with one app that kept giving annoying messages about my phone being rooted.
The only app that I've used that required BusyBox was Titanium Backup. I uninstalled Titanium Backup since it doesn't work on Android 11 and thus BusyBox also was uninstalled.
I got the app to work, but I can't get the link to register with the app to continue. The link sent to my phone just says bad link when opening in browser