Related
Hello,
I've noticed that since Android 7.0, Android System Webview will be disabled by default, and Chrome will used instead. However, I'm wondering that if I were to replace my factory installed Chrome to Beta or even Canary, will it bring any issues other than stability issues (caused by untested code, in Canary, for example) for web rendering activity? Will it cause my system to break?
What I was planning to do, is by uninstalling Stable Chrome (first rooting my phone via Magisk, then uninstall it using Root Uninstaller), and then install Canary afterwards.
On Angler (Nexus 6p) I flashed the latest stock rom. (After a complete wipe) Afterwards I flashed TWRP and unzipped Magsik. Subsequently I did update to the latest version. After that I changed the packagename of Magsik manager. Furthermore I installed Xposed framework. Afterwards I enabled root hide for the TAN app:
https://play.google.com/store/apps/details?id=com.starfinanz.mobile.android.dkbpushtan&hl=en
This software is meant to give you the tan without using sms services.
Still, the app crashed right at the start without any error notification. Android Version is 8.1 and Magsik is v16. While I did the test, the bootloader was unlocked and TWRP was still the recovery. Can these two things affect the verification of the Banking app? I tried this several times ago in the past, but I was never to make this app running.
If anyone would be able to give helpful advice here, it would be very much appreciated.
Best,
scarline
I have heard that DKB Tan2Go does not work with newer Android versions like Oreo 8.1.x at all.
I can also confirm that. I tried it on a Sony cellphone. The cellphone was not rooted and with a completely new and 'clean' ROM. It was to no avail.
A friend has been forced to buy a chip reader. I am fortunate to be able to use normal TAN lists at the moment. If the DKB tries to exclude me from online banking, I will change the bank.
DKB Tan2Go seems to be one of the worst and most insecure apps ever. The reviews in Google PlayStore confirm this conclusion.
Maybe there will be a solution someday?
DKB TAN2go works with Magisk:
1. Install the TAN2go app (but don't open it)
2. Add the TAN2go app in Magsik Manager in the menu "Magisk Hide"
3. Reboot the phone (I don't know if this is necessary)
4. Open TAN2go, works fine.
**** DKB and this stupid security features which bring absoltuely no security.
That's exactly what I tried - without success. I read that it only worked with an old, obsolete version of Tan2Go. However, I could not find this version and I'm not sure if it still works at all. Did you have the latest version of Tan2Go from Google PlayStore? According to DKB, the recent Tan2Go does not work with devices that was once rooted or had a CustomROM. Even if you go back to stock the Root Counter changed and DKB Tan2Go will never work on this device. Unfortunately, I have to confirm that.
I am working on it to change the bank, because of that.
exaveal said:
DKB TAN2go works with Magisk:
**** DKB and this stupid security features which bring absoltuely no security.
Click to expand...
Click to collapse
Indeed!
Yes, I have installed the latests version of LineageOS, latest version von Magisk and the latests version of the TAN2go app.
I tried that to no avail. I heard once the root counter has a value other than 0, one can't go back. Probably it is also the Sony bootloader and it is different with other devices?
exaveal said:
Yes, I have installed the latests version of LineageOS, latest version von Magisk and the latests version of the TAN2go app.
Click to expand...
Click to collapse
I have a Xiomi Mi5 rooted with Magisk and Tan2go used to work for the last year or so. But yesterday I tried to make a transaction and BOOM! App crashed without an error message. Tried to use a newer Magisk, tried reinstalling the App, nothing helped.
The worst thing is that I do not know if some of my programs have a battery checker or a screen reader plugin that I am not aware of, or if Tan2Go suddenly detects my root. Regardless, crashing without an explanation is like the worst programming practice ever.
Since I do not need this kind of ****e in my life I will probably change Bank, I mean what good is an internet Bank if you cannot do transactions over your mobile device?
Well, willy-nilly I try to use the only other option from DKB: the German TAN Generator. Every other bank equips you with such a device, if they want you to use it. The DKB does not. Actually, I ordered the 3rd TAN Generator and fully paid for it. The first one drains the battery within days. The second one let me type in all the numbers and for no reason the TAN code does not show up on display.
These devices are very annoying anyway, because you have to type in a lot of numbers for every money transfer, the characters are very small (on the laptop) and you have to carry the TAN Generator + the DKB debitcard all the time. Of course this is less secure.
I would change the bank immediately, but want to keep the Visa credit card. I have higher limits on it. That's the only reason. As soon as I found an alternative bank in Europe, I will leave the DKB for good.
It dont worked with Lineage 14.1 but with 15.1 unoffical build on Samsung S4 together with latest Magisk .Rom from here
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-galaxy-s4-lte-android-8-1-oreo/
Works for me
Just tried again. It hasn't been working for me in the past. When downloading & opening the app, I had the same problems.
Then I simply followed the above advice: downloading the app again, didn't open it, hide with Magisk, reboot and opened the app - worked well and was able to register for tan2go.
I am using Lineage 16.0 and Magisk v18.0
DKB already updated their app - they patched it
kyodhin said:
Just tried again. It hasn't been working for me in the past. When downloading & opening the app, I had the same problems.
Then I simply followed the above advice: downloading the app again, didn't open it, hide with Magisk, reboot and opened the app - worked well and was able to register for tan2go.
I am using Lineage 16.0 and Magisk v18.0
Click to expand...
Click to collapse
The app version from September (version 2.3.0) does work, the newer app version from 4.4.19 (version 2.4.0) does not...
Tested working combination: Magisk 18.0, Magisk Manager 6.1, DKB version 2.3.0
Can confirm that, working with magisk and 2.3.0. Not working anymore with 2.4.0.
I have another Tan app from another bank and with the new version it also stops working. Seems that magisk is now quite to popular and they working on better detection. Magisk hide is useless on the recent version of these tan apps.
That really sucks. No way to get 2.4.0 working. Hoping for a magisk fix. Are the magisk developer informed that there are problems with magisk hide? I think others will have similar problems too.
I successfully got 2.4 working again, after it got updated and refused to start.
Following the steps from this post made it work again (German):
https://www.android-hilfe.de/forum/...trotz-magisk.901517-page-2.html#post-11532359
I installed Magisk 19.0 (beta) but contrary to the above mentioned post I left my Magisk modules installed as they were before the update.
Both the Magisk modules as well as TAN2Go 2.4 are now working again.
I had to authenticate the new TAN2Go installation by adding it as a "new device" using SMS verification.
I was not able to get it to run with the above mentioned instuctions.
Device: Nexus 6P (angler), ROM: LineageOS 15.1-20190419, Magisk modules: MagiskHide Props Config (required for ctsProfile test), Busybox for Android NDK (required for MagiskHide Props Config).
DKB Tan2Go crashes immediately when started.
Same for me. The above instruction doesn't work.
Downgrade to 2.3.0
I experienced the same problem. Had to do an important transfer yesterday. And of course Tan2Go-2.4.0 crashed. I'm using Magisk v18.1.
Today I did a downgrade via Aptoide to 2.3.0 and had to register the smartphone again via SMS. This worked without any problems.
To avoid the update problem and keep with 2.3.0:
Start Titanium Backup
Select the DKB Tan2Go App
Long click on the App.
Connect with Google Play Store (forced)
Long click the App again.
Disconnect from Google Play Store
Hope it helps. I don't think there's much to change in the DKB Api. I'll use 2.3.0 until they block it via the API.
If more people confirm the proposed solution with Magisk v19, I'll try it maybe.
I got it working with v2.4.0, but don't know which step was the solution. Switching to the "Canary" channel of Magisk or hiding the Magisk Manager in the settings. I think the last one was the solution.
Can you guys try and give feedback?
Don't forget to uninstall and install the app before testing again.
musv said:
If more people confirm the proposed solution with Magisk v19, I'll try it maybe.
Click to expand...
Click to collapse
I have the same issue. Hopefully it can be fixed via Magisk one day.
Worked with T2G 2.4, 19, 7.1.1
Walhalla said:
I got it working with v2.4.0, but don't know which step was the solution. Switching to the "Canary" channel of Magisk or hiding the Magisk Manager in the settings. I think the last one was the solution.
Can you guys try and give feedback?
Don't forget to uninstall and install the app before testing again.
Click to expand...
Click to collapse
Hi Walhalla,
Hi All
In Settings "General">"Hide" via other apk name it worked for me. V19.0, v7.1.1, Tan2Go 2.4
Thanks to the guide created by pjottrr I successfully unlocked bootloader and rooted my device. Now I'm onto what I assume is the next step, which is to flash a custom rom via fastbootd?
Im aiming to 'degoogle' my device by getting rid of gapps and installing microG to substitute play services, though i'm not sure which custom rom is compatible with setting up microG.
Is there anyone here that can share their experience with a particular custom rom + microG integration? Or is there another method for what I'm trying to achieve
Android 10
OPMS30.80-63-6-8-5
US Retail
Mint Mobile
Moto G Power XT2041-4 Sofia
Check out https://forum.xda-developers.com/t/rom-rav-sofia-10-unofficial-lineageos-17-1.4250763/post-84701445.
It isn't microG, but it does have FDroid app store baked in. It's a really solid ROM. The only glitch is with tethering. Tethering works exactly as it is supposed to but when you exit out it reboots the phone.
tcaudill01 said:
Check out https://forum.xda-developers.com/t/rom-rav-sofia-10-unofficial-lineageos-17-1.4250763/post-84701445.
It isn't microG, but it does have FDroid app store baked in. It's a really solid ROM. The only glitch is with tethering. Tethering works exactly as it is supposed to but when you exit out it reboots the phone.
Click to expand...
Click to collapse
Thanks for the suggestion. Would I be able to install microG to replace the core gapps after flashing this rom onto my device? I was going to add the nanodroid magisk module to do so following This guide
Banana_sam said:
Thanks for the suggestion. Would I be able to install microG to replace the core gapps after flashing this rom onto my device? I was going to add the nanodroid magisk module to do so following This guide
Click to expand...
Click to collapse
There are NO gapps in this ROM. FDroid is a non google app store. You should be able to install microg without having to remove anything.
tcaudill01 said:
There are NO gapps in this ROM. FDroid is a non google app store. You should be able to install microg without having to remove anything.
Click to expand...
Click to collapse
Well all that's left now is to try and give it a go. I'll report back once it's completed!
Ive flashed the rom! No problems it seems so far. Now im trying... but not sure how to install microG. The aforementioned guide says to install magisk manager to install microG. Only problem is that magisks latest release notes claim that magisk manager is no more, that its already inside the latest apk, which I installed when rooting. So how do I install microG using the manager supposedly baked into the latest apk?
Edit: I was able to install microG successfully. I didnt know that custom ROMs came unrooted. I rooted it following the same steps as the first time and then I was able to easily flash the microG module in magisk with no issues.
Thank you so much to all the people on this forum. Im a total noob and seemingly was able to successfully accomplish what I was after, with very minor hiccups(that were caused by my noobness of course haha)
Guess I might have spoken too soon.. On microG the permission to access location in the background, and permission to receive SMS arent ticked in the self-check menu. Any ideas on how I could go about easily fixing this?
Banana_sam said:
Guess I might have spoken too soon.. On microG the permission to access location in the background, and permission to receive SMS arent ticked in the self-check menu. Any ideas on how I could go about easily fixing this?
Click to expand...
Click to collapse
You should be able to just click on the items which arent checked and microG will ask for the permissions so you can grant them in the pop-up
DknsBs said:
You should be able to just click on the items which arent checked and microG will ask for the permissions so you can grant them in the pop-up
Click to expand...
Click to collapse
Ive tried this but to no avail. Oddly enough, I made a 2nd user account on the same device and on there microG has all the permissions checked.
I installed it via the magisk module. Do you think it would make a difference to try uninstalling it and maybe try installing via the f-droid store?
Check out my post here. I have successfully installed crdroid 7.4 with Nanodroid plus microG and a real Play Store.
tinbilly said:
Check out my post here. I have successfully installed crdroid 7.4 with Nanodroid plus microG and a real Play Store.
Click to expand...
Click to collapse
I appreciate the tip, but this is for crdroid, I've already went with lineage and as of yet don't plan on switching to try something new. besides that, microG works fine on my 2nd user account which Ive switched to use and that I mentioned in an earlier post in this thread. And on my newly embarked journey to retain privacy and protect my data I've come to discover its better to use a second user account as your daily go-to account instead of your admin account which grants root permissions. My second use account doesn't have root permissions so in theory this should protect me better.
I guess what I thought was an issue with microG might have been a blessing in disguise since it's forced me to use it on my 2nd user account where all the permissions are granted and now I should be a bit more protected from root access attacks
--->This is a working method as of May 2023 to have root on any rom version for redmi k20pro.
--->This will help you root and keep root hidden along with using lsposed modules.
--->These steps work on any device and any rom
You can find extra guides for the steps you dont understand by searching on xda forums. Some of these guides are linked to at the bottom of this post
Your bootloader needs to be unlocked to follow this guide. See link at bottom for guides to do the same.
****************************
I am not responsible for any data loss or damage. Follow at your own Risk
****************************
1. Install twrp or orangefox recovery on your phone.
2. Flash Magisk 25.2 (Version 26 has many issues. This version is better to use)
3. Reboot, install magisk apk(rename magisk.zip file to magisk.apk and install)
4. In magisk modules, install shamiko
5. In magisk modules, install safetynet 2.4.0
6. Add any app you want to hide root from in denylist of magisk. Additionally add Google play Services, Google play store, google services framework and google play protect to denylist(enable show system apps option in menu available on top right of denylist)
(IMP: Do not enable enforce denylist, Shamiko does this function)
7. If you have already logged into google play store and it shows device not certified in about section of play store -remove google account from phone and clear data of play store, play services, google services framework. Reboot amd try again. It will show certified status after about 10 minutes of logging in
8. Some custom roms may have device fingerprints which will get detected as custom rom. If that happens, use hide user debug and lineage props magisk module. Note: This version from github can only be flashed in Androidacy Fox Module Manager due to issue in zip packaging. Download this file which is just a properly repackaged version that can be flashed in any magisk manager.
Next install Reset Sensitive props magisk module. A combination of simply installing these modules will fix custom rom detection on any custom rom.(Example on opening whatsapp or GPay for first time)
Additional step(not necessary): Your rom may have additional build.prop entries that indicate a custom rom. Look for such build properties by opening build.prop in root browser on your device, then change any that have a custom rom name in them using magiskhideprops(Refer instructions to use magiskhideprops in the link)
9. Now, hide the magisk app in magisk app settings(set name to something like setting or app)
10. Freeze magisk manager app using link2sd/swift backup/ airfrozen or any other similar app. You can enable app when you need to install or disable modules or grant superuser access to new apps. You can also use Androidacy Fox MMM manager to find, install and remove magisk modules
_____________________________________________________________________________
Done, you can stop at this stage if you dont need lsposed.
Be warned that youw ill need to re-add any app you uninstall and reinstall in denylist.
If you want to use lsposed, continue with below steps after skipping step 10.
_____________________________________________________________________________
11. Install lsposed module 1.8.6 zygisk version
12. Install hide my appslist. Follow instructions in this link to learn how to correctly configure and hide magisk manager, lsposed and any other root apps you have.
You will need dataisolation enable magisk module if using android 10 and below for hidemyapplist to fully work.
13. Install Ruru and 'Play Integirty API Checker'.
Run Ruru and watch it pass all tests.(almost no banking app uses the level of detection used by ruru) Use play integrity api checker to check safetynet status - should pass basic integrity and cts profile.
Momo shows some messages like abnormal environement and TEE but that is ok.
Remember that you should enable denylist and Hide my applist for Ruru/Momo similar to how you enable for banking apps to hide.
Your root access is perfectly hidden now.
_____________________________________________________________________________
If you want to hide Developer Options_____________________________________________________________________________
You have a few options for this.
1. I personally turn usb debugging off in settings and use WADB app to enable wireless adb. I am using this on android 11 as other options dont fully hide or trigger xposed hook detection(which does not cause issues with the banking apps I have tested so far)This is not detected by any apps.
2. If on android 10 or lower, you can use hide user debug magisk module by huskydg which you can get from this telegram channel. I dont know if it can be linked here .
This effectively hides user debug without trigerring any root/xposed detection. Ruru may show 1 entry for usb debugging enabled but that is fine. If it doesnt work, it will show 2-3 detected entries for debugging mode.
I have uploaded the file here but dont know if it will last
3. If above options dont work,use devoptshide app, enable it in lsposed for apps you want to hide user debug from.This method will trigger xposed hook detection in Ruru but none of the banking apps i tested so far have an issue with that. Ruru may show 1 entry for usb debugging enabled but that is fine. If it doesnt work, it will show 2-3 detected entries for debugging mode.
4. I have not personally tested this but this module is an updated version of hide userdebug module by huskydg and it might help hide usb debugging on android 11 and up.You will have to try it yourself for now.I expect it to work.
GitHub - Magisk-Modules-Alt-Repo/ezme-nodebug: Change some props and "remove" LineageOS ones.
Change some props and "remove" LineageOS ones. Contribute to Magisk-Modules-Alt-Repo/ezme-nodebug development by creating an account on GitHub.
github.com
_____________________________________________________________________________
If an app detects root accidentally and refuses to run on your device again even if root is not detected again/ Spoof device ID for apps_____________________________________________________________________________
1. Now you need to use android faker lsposed module to randomize imei, max adress, android device id,hardware id.
Enable android faker in lsposed only for the app you want to change id for. Dont enable it for android system or android framework(Goal is to change id for a single app).Before doing these steps you need to clear data of play store, play services and google services framework, remove your google account from device settings and reboot. This will reset your gsf id.
This will give xposed hook detection in butbank apps dont seem to look for it.
2. If the above method does not work, use Xprivacylua. Enable for the app you want to change id, only use setting for device identifiers,use tracking, telephony data, analytics, get applications. Xprivacylua is not properly hidden even by Hide My Applist but apps dont look for it.So use this if above options does not work.
_____________________________________________________________________________
If you need to disable Widevine L1 DRM protection to use scrcpy screen mirroring etc
_____________________________________________________________________________
Install the liboemcryptodisabler module in magisk.Do note that widevine will drop to L3 but uninstallation brings it back to L1.
NOTE: Drm content cannot be mirrored on scrcpy if you are using android 12 or 13. Use roms with android version upto 11 if you need to watch drm protected content through scrcpy.(at your own risk. I do not advise illegal activity.)
Spoiler: liboemcryptodisabler
Magisk Modules Repository By Androidacy - Androidacy
This is the Androidacy Magisk Modules Repository, where you can search, browse, and download your favorite Magisk modules right now.
www.androidacy.com
Enjoy your properly hidden rooted device with all functionalities.
___________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________
I have added a few useful posts by other members if you dont know how to do any of the above mentioned steps. Any others steps can be learned with guides from XDA -Use search
1. Simple guide to flashing on K20 Pro
His advice on not using orangefox for custom roms other than stock miui/ xiaomi.eu roms may be right, I have not tried it. Orangefox personally works best for me.
2. Guide to flashing custom roms, changing between miui and custom roms
3. Bootloader unlock, twrp, root instructions and rom links
4. Common issues with Redmi K20 Pro | fingerprint unlock | ghost touch | Dim display | sensor issues | bluetooth and calling
Confirmed working in May 2023.
Guide will be eventually updated with Magisk Delta which is better for root hiding
I am amazed how smoothly my update went from old magisk version that started having issues. I followed first part of this tutorial (without lsposed), I downloaded newest versions of everything (magisk 26.1 - had to directly install magisk in magisk too, Shamiko-v0.7.1-166-release, rest same as in tutorial) and it just worked. No more problems with old magisk. Deny list is working flawlessly!, safetynet is passing, Google Play Store says that device is certified. Thank you so much for this tutorial!
czacha994 said:
I am amazed how smoothly my update went from old magisk version that started having issues. I followed first part of this tutorial (without lsposed), I downloaded newest versions of everything (magisk 26.1 - had to directly install magisk in magisk too, Shamiko-v0.7.1-166-release, rest same as in tutorial) and it just worked. No more problems with old magisk. Deny list is working flawlessly!, safetynet is passing, Google Play Store says that device is certified. Thank you so much for this tutorial!
Click to expand...
Click to collapse
As of right now, magisk 25.2 works much better than magisk 26.1. You can continue to use it if you dont face any issues.
I believe I followed all the steps correctly including downgrading to magisk 25.2, the only step that I might not have followed correctly would be using hidemyapplist, but I'm getting CTS profile mismatch in microG safetynet attestation test. I have an LE2115 with lineageos 20 (specifically lineage-20.0-20230514-nightly-lemonade-signed.zip). I do get the "orange state" warning when I turn on my phone, I could make that go away by flashing an older version something (I forgot what but I've done it before) in TWRP but I wanted to avoid that since the only APPARENT effect is the orange state warning and I don't know if it will break later in LOS as they keep updating. I'd appreciate any help you could give me to fix this.
EDIT: just used magiskhidepropsconf and edit fingerprint and set it to htc exodus and now I pass all tests.
I just rooted my phone and wanted to put out there how I got my bank (Santander UK) app working.
Hiding Magisk, using the Deny List and Zygisk, and using the Universal SafetyNet Fix package did not work.
What did work was using the Shelter app to create a sandbox and installing the Santander app in that.
Edit: It stopped working after a while, and I'm not quite sure why it worked at all in the sandbox when it wasn't unsandboxed. The phone passes safetynet so it ain't that. I'm wondering if its detecting the unlocked bootloader in some other way, and not the root.
Eavolution said:
I just rooted my phone and wanted to put out there how I got my bank (Santander UK) app working.
Hiding Magisk, using the Deny List and Zygisk, and using the Universal SafetyNet Fix package did not work.
What did work was using the Shelter app to create a sandbox and installing the Santander app in that.
Click to expand...
Click to collapse
Man! I wanted to use Shelter on my stock A52 4G to put proprietary apps in, but since it's had a custom OS on it before I can't use work accounts anymore. When I go back to LOS I'll have to try this, thanks!
@Eavolution what rooted phone/OS do you have? I'm unable to install Shelter on my rooted SG10Exynos/OS9 and get the same "Cannot create work profile.. a custom OS has been installed"
nukescript said:
@Eavolution what rooted phone/OS do you have? I'm unable to install Shelter on my rooted SG10Exynos/OS9 and get the same "Cannot create work profile.. a custom OS has been installed"
Click to expand...
Click to collapse
I'm on a redmi note 10 pro, rooted using a magisk modified boot.img with an unlocked bootloader on miui14, android 13. Weirdly the banks app only worked for a bit then put up a warning again and wouldn't let me use it. I wonder why it worked for a bit in a sandbox but not unsandboxed, and how it clocked from within the sandbox that the thing was rooted.
My phone passes safetynet with magisk set up how it is so it ain't using that, I have a suspicion that it's not detecting the root, but the unlocked bootloader.
I've got issues with both Barclays & Santander apps. I pass SafetyNet with the help of Magisk 26.0 & safetynet-fix-v2.4.0-MOD_1.2. It's the Play Integrity API that I cant bypass, and that these banking apps are using.
I have the same issue with Barclays App.
I found that using Magisk Delta, Barclays works again.
Unfortunately, Google Wallet doesn't work with Magisk Delta; it can detect root, but with the official version of Magisk Google Wallet works.
Basically:
Magisk Delta: Barclays works and Google Wallet doesn't work
Official Magisk: Barclays doesn't work (error 00006) and Google Wallet works
edit:
I'm on Samsung Galaxy A71 with Android 13 (Secirity patch level 1 April 2023)
These are the two Magisk setups I used:
Magisk v26.1 (Barclays doesn't work - Google Wallet Works)
MagiskHide Props Config v6.1.2-v137 (installed using this guide https://forum.xda-developers.com/t/magisk-google-wallet-pay-with-magisk.4471279/page-7)
Universal SafetyNet Fix v2.4.0 installed and enabled
Zygisk enabled
Enforce DenyList enabled
Magisk App hidden
Magisk Delta 25210 (Barclays works - Google Wallet doesn't work)
MagiskHide Props Config v6.1.2-v137 (installed using this guide https://forum.xda-developers.com/t/magisk-google-wallet-pay-with-magisk.4471279/page-7)
Universal SafetyNet Fix v2.4.0 installed and enabled
Zygisk enabled
Enforce SuList enabled
Magisk Delta App hidden
xsecret said:
I have the same issue with Barclays App.
I found that using Magisk Delta, Barclays works again.
Unfortunately, Google Wallet doesn't work with Magisk Delta; it can detect root, but with the official version of Magisk Google Wallet works.
Basically:
Magisk Delta: Barclays works and Google Wallet doesn't work
Official Magisk: Barclays doesn't work (error 00006) and Google Wallet works
edit:
I'm on Samsung Galaxy A71 with Android 13 (Secirity patch level 1 April 2023)
These are the two Magisk setups I used:
Magisk v26.1 (Barclays doesn't work - Google Wallet Works)
MagiskHide Props Config v6.1.2-v137 (installed using this guide https://forum.xda-developers.com/t/magisk-google-wallet-pay-with-magisk.4471279/page-7)
Universal SafetyNet Fix v2.4.0 installed and enabled
Zygisk enabled
Enforce DenyList enabled
Magisk App hidden
Magisk Delta 25210 (Barclays works - Google Wallet doesn't work)
MagiskHide Props Config v6.1.2-v137 (installed using this guide https://forum.xda-developers.com/t/magisk-google-wallet-pay-with-magisk.4471279/page-7)
Universal SafetyNet Fix v2.4.0 installed and enabled
Zygisk enabled
Enforce SuList enabled
Magisk Delta App hidden
Click to expand...
Click to collapse
Does this still work for you with latest barclays app?
first_damned said:
Does this still work for you with latest barclays app?
Click to expand...
Click to collapse
Actually I found a workaround, I'm currently using Magisk Alpha (26100) + Universal SafetyNet Fix (v2.4.0-MOD_1.2), and now I can use both Google Wallet and Barclays (latest version v2.79.0).
I think the modded version of Universal SafetyNet Fix fixed the problem, I think it works with Magisk Delta too (but I haven't tested it).
[MODULE] [MOD] Universal SafetyNet Fix
Universal SafetyNet Fix [MOD] Magisk module Hello. This is my modification [FORK] of the original Universal SafetyNet Fix module from @kdrag0n. Created for the (temporary?) restoration of working capacity in the conditions of constant change...
forum.xda-developers.com
xsecret said:
Actually I found a workaround, I'm currently using Magisk Alpha (26100) + Universal SafetyNet Fix (v2.4.0-MOD_1.2), and now I can use both Google Wallet and Barclays (latest version v2.79.0).
I think the modded version of Universal SafetyNet Fix fixed the problem, I think it works with Magisk Delta too (but I haven't tested it).
[MODULE] [MOD] Universal SafetyNet Fix
Universal SafetyNet Fix [MOD] Magisk module Hello. This is my modification [FORK] of the original Universal SafetyNet Fix module from @kdrag0n. Created for the (temporary?) restoration of working capacity in the conditions of constant change...
forum.xda-developers.com
Click to expand...
Click to collapse
Soumds promising. Please can you detail exactly what you did to get it working? And how did you install magisk alpha? Also on which rom does this work on? As I want to use it on lineage os. Thank you in advance this is very much appreciated!
first_damned said:
Soumds promising. Please can you detail exactly what you did to get it working? And how did you install magisk alpha? Also on which rom does this work on? As I want to use it on lineage os. Thank you in advance this is very much appreciated!
Click to expand...
Click to collapse
There's not much to explain, I just rooted my Galaxy A71 (with Android 13) following this guide:
How to Install Magisk on your Android Phone
Magisk is a powerful tool that can help you customize some aspects of your phone or even grant you root access. Here's how you can install it!
www.xda-developers.com
Then I installed Magisk Alpha v26.1 (when prompted, give root permissions to Magisk Alpha)
GitHub - vvb2060/magisk_files
Contribute to vvb2060/magisk_files development by creating an account on GitHub.
github.com
Then in Magisk Alpha I enabled the Zygisk and Enforce DenyList settings.
Then in Magisk Alpha under Configure DenyList settings select all the apps you want to hide the root, I suggest all your banking apps, Google Play Store, Google Services Framework, Google Wallet.
Some apps are not visible, so you need to turn on the Show system apps setting.
Then hide your Magisk Alpha app, so select Settings>Hide the Magisk app
Then I uninstalled Magisk (official), before uninstall Magisk (official) make sure that Magisk Alpha is correctly installed, otherwise you will lose the root and have to start from the beginning, so just make sure that (in Magisk Alpha) next to Zygisk and Ramdisk it says Yes.
Then I installed the Universal SafetyNet Fix v2.4.0 [MOD_1.3] module in Magisk Alpha:
Releases · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix
github.com
Just download the zip file, and go Magisk Alpha>Modules>Install from storage and select the zip file to install the safety net fix, and reboot your phone.
By the way I just reinstalled Magisk (Official) v26.1 + SafetyNet v2.4.0 MOD_1.3, but Barclays app immediately detected the root (Google Wallet works), I guess Barclays implemented some algorithm to detect Magisk (official), maybe some files that are only present when Magisk (official) is installed?
Other tests I've done:
Barclays App works even if you don't hide Magisk Alpha app.
Barclays App works even if you don't uninstall Magisk (official), so if Magisk Alpha is installed and it's your root manager and Magisk (official) is installed without being your root manager, Barclays app still works.
Barclays App works event SafetyNet Fix module is not enabled (in Magisk Alpha), this module is used to make Google Wallet work
In the DenyList it is sufficient to enable the activities com.barclays.android.barclaysmobilebanking and com.barclays.android.barclaysmobilebanking_zygote, if you leave the other 3 activities disabled Barclays app will continue to work without detecting the root.
xsecret said:
There's not much to explain, I just rooted my Galaxy A71 (with Android 13) following this guide:
How to Install Magisk on your Android Phone
Magisk is a powerful tool that can help you customize some aspects of your phone or even grant you root access. Here's how you can install it!
www.xda-developers.com
Then I installed Magisk Alpha v26.1 (when prompted, give root permissions to Magisk Alpha)
GitHub - vvb2060/magisk_files
Contribute to vvb2060/magisk_files development by creating an account on GitHub.
github.com
Then in Magisk Alpha I enabled the Zygisk and Enforce DenyList settings.
Then in Magisk Alpha under Configure DenyList settings select all the apps you want to hide the root, I suggest all your banking apps, Google Play Store, Google Services Framework, Google Wallet.
Some apps are not visible, so you need to turn on the Show system apps setting.
Then hide your Magisk Alpha app, so select Settings>Hide the Magisk app
Then I uninstalled Magisk (official), before uninstall Magisk (official) make sure that Magisk Alpha is correctly installed, otherwise you will lose the root and have to start from the beginning, so just make sure that (in Magisk Alpha) next to Zygisk and Ramdisk it says Yes.
Then I installed the Universal SafetyNet Fix v2.4.0 [MOD_1.3] module in Magisk Alpha:
Releases · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix
github.com
Just download the zip file, and go Magisk Alpha>Modules>Install from storage and select the zip file to install the safety net fix, and reboot your phone.
By the way I just reinstalled Magisk (Official) v26.1 + SafetyNet v2.4.0 MOD_1.3, but Barclays app immediately detected the root (Google Wallet works), I guess Barclays implemented some algorithm to detect Magisk (official), maybe some files that are only present when Magisk (official) is installed?
Other tests I've done:
Barclays App works even if you don't hide Magisk Alpha app.
Barclays App works even if you don't uninstall Magisk (official), so if Magisk Alpha is installed and it's your root manager and Magisk (official) is installed without being your root manager, Barclays app still works.
Barclays App works event SafetyNet Fix module is not enabled (in Magisk Alpha), this module is used to make Google Wallet work
In the DenyList it is sufficient to enable the activities com.barclays.android.barclaysmobilebanking and com.barclays.android.barclaysmobilebanking_zygote, if you leave the other 3 activities disabled Barclays app will continue to work without detecting the root.
Click to expand...
Click to collapse
Works top man!
Another test I did:
Barclays works even if Zygisk is disabled, but Google Wallet will not work because Universal Fix will be suspended, as this module requires Zygisk to work