Hi,
Hope you can help, if I root with super su for just change build pro settings, and then full unroot, will I keep the changes?? Or there is a another way to change build prop variable without root? I'm in G930F Nougat stock rom
Thanks
Yes the changes will remain if you unroot but why would you? You have already tripped KNOX etc by rooting in the first place, and your system status will remain 'Custom', so things like banking apps will likely still fail to work
No you can't change system files without root, build.prop is a system file
*Detection* said:
Yes the changes will remain if you unroot but why would you? You have already tripped KNOX etc by rooting in the first place, and your system status will remain 'Custom', so things like banking apps will likely still fail to work
No you can't change system files without root, build.prop is a system file
Click to expand...
Click to collapse
Thanks you so much for your answer, it's exactly because some video apps and banking as you said not work with root and they are essential for me. The problem is, I'm root since a long time, s health just work editing build prop, and since a few months ago, some apps like my bank, and video apps stop working because of root, and I need both things now, and I remember that before root(with already Knox tripped) they work fine.
speechgotham3 said:
Thanks you so much for your answer, it's exactly because some video apps and banking as you said not work with root and they are essential for me. The problem is, I'm root since a long time, s health just work editing build prop, and since a few months ago, some apps like my bank, and video apps stop working because of root, and I need both things now, and I remember that before root(with already Knox tripped) they work fine.
Click to expand...
Click to collapse
AFAIK, these apps just don't open anymore because of the SafetyNet profile missmatch you get when rooted (You can download an app like "SafetyNet Helper Sample" from Play Store to view your current SafetyNet status).
Apps like Snapchat, PokemonGO, my local banking app,.. use this technology, rather than the "custom" mark or the tripped knox.
So in my opinion you have three options now:
Use Magisk
When rooted with MagiskSU, your phone will still pass the SafetyNet Profile match, which will let you use your apps and root.
Root -> make your changes -> unroot
When you're completely unrooted you will once again pass the SafetyNet
(Probably doesn't work for you)Unroot -> Prepare Apps -> root again
Apps like Snapchat just check your SafetyNet status at login. That means when you're not rooted, you can log in to Snapchat, when you root afterwards (without a wipe of course) you're still logged in, even tho your phone wouldn't pass SafetyNet atm.
jaannnis said:
AFAIK, these apps just don't open anymore because of the SafetyNet profile missmatch you get when rooted (You can download an app like "SafetyNet Helper Sample" from Play Store to view your current SafetyNet status).
Apps like Snapchat, PokemonGO, my local banking app,.. use this technology, rather than the "custom" mark or the tripped knox.
So in my opinion you have three options now:
Use Magisk
When rooted with MagiskSU, your phone will still pass the SafetyNet Profile match, which will let you use your apps and root.
Root -> make your changes -> unroot
When you're completely unrooted you will once again pass the SafetyNet
(Probably doesn't work for you)Unroot -> Prepare Apps -> root again
Apps like Snapchat just check your SafetyNet status at login. That means when you're not rooted, you can log in to Snapchat, when you root afterwards (without a wipe of course) you're still logged in, even tho your phone wouldn't pass SafetyNet atm.
Click to expand...
Click to collapse
Thanks my friend I will try, because now I'm root with Magisk and with Magisk hide and does not work even with safety net pass
speechgotham3 said:
Thanks my friend I will try, because now I'm root with Magisk and with Magisk hide and does not work even with safety net pass
Click to expand...
Click to collapse
Which version of Magisk are you using?
What is the result of the SafetyNet Sample App?
jaannnis said:
Which version of Magisk are you using?
What is the result of the SafetyNet Sample App?
Click to expand...
Click to collapse
The latest one
Attach you an image
Thanks for your help
speechgotham3 said:
The latest one
Attach you an image
Thanks for your help
Click to expand...
Click to collapse
You could try installing the newest beta, which is 13.6, but I don't really believe this resolves your problem. You can get it from here: Magisk Beta Thread
Related
I've been rooting my Android phones since about 2012, but today I got a point of sale card reader for my business and I'm not having any luck hiding root from the app (square reader app). The app wont work at all so I tried a number of options in magisk manager (magisk hide the app, hide magisk manager, enable core mode only) rebooting between each try and clearing the square reader app data and setting it up fresh each time, but still no luck
I tried to uninstall magisk but the app still didn't work. So I eventually flashed back to stock and got rid of magisk all together, now the app works but I don't have root...
I tried installing magisk again after I got the app to work and hiding root from the app before I opened it up again, but it still somehow knew the device was rooted
Can anyone suggest anything I haven't tried? Or is there an alternative to rooting the OnePlus 6 (other than magisk) and hiding root? I had a bit of a look around but didn't find anything.
Thanks
I had to go back to 18.0, heard 18.2 works as well.
qbanlinxx said:
I had to go back to 18.0, heard 18.2 works as well.
Click to expand...
Click to collapse
Thanks for your reply. I tried with 18.0, damn, it still doesn't work, it still picks up that the phone is rooted
I tried the 18.2 canary build as well (18.2-e72c6685) no luck either
This app must be looking somewhere out of the ordinary for evidence of root in the phone
I have a bank application and facing the same problem. Hope someone can help us to make applications run by hiding the root
I think recent applications are looking for if knox security is tripped !! so in this case Magisk will not help
Ooohhh had to subscribe to this as I face the exact same issue!! Been trying to get my Square reader to work for a while with root and could never figure out how they are detecting root. Using Pixel XL here
Google changed something in Safety Net in play services, it passes, yet for me, google pay fails. That COULD be the issue, though I read 18.2 fixes that. Another option I helped a friend with is if it's detecting magisk itself via the files, culprit here was pokemon go.
Try opening your Magisk settings, the tick "hide magisk manager" clear the repo cache, and rename or delete the MagiskManager folder on the root of your storage. Reboot, clear data from the square app, and try again. Keep in mind, you have to unhide magisk to update it.
Skreelink said:
Google changed something in Safety Net in play services, it passes, yet for me, google pay fails. That COULD be the issue, though I read 18.2 fixes that. Another option I helped a friend with is if it's detecting magisk itself via the files, culprit here was pokemon go.
Try opening your Magisk settings, the tick "hide magisk manager" clear the repo cache, and rename or delete the MagiskManager folder on the root of your storage. Reboot, clear data from the square app, and try again. Keep in mind, you have to unhide magisk to update it.
Click to expand...
Click to collapse
In my case, I dont think its detecting the files. The reason i say that is because I play Pokemon Go just fine with no issues. So whatever Square is doing, its something different then what PoGo is doing.
Idledev said:
In my case, I dont think its detecting the files. The reason i say that is because I play Pokemon Go just fine with no issues. So whatever Square is doing, its something different then what PoGo is doing.
Click to expand...
Click to collapse
I agree, I have no problem hiding magisk and root from other apps, the square reader app must be somehow different. I've even gone through my storage and deleted any files or folders that might suggest the phone is rooted, but still no luck...
I also went into battery optimization settings to stop magisk from being put to sleep (which might stop magisk hide from working..?), that didn't work either.
I've found a temporary workaround to my problem anyway, I realized that I can share my internet (wifi hotspot) with my ipod touch, this way square reader works as the ipod touch isn't jailbroken or modified. It just means I have to carry around my ipod touch with me, which is a better trade off for me than having a stock, non root phone
Managed to get it working today! Upgraded my Pixel XL to the Android Q beta. By doing this, I had to run Magisk canary build. Installed square, enabled Magisk hide, rebooted and it worked fine! Not sure if the Android Q beta has anything to do with it,but give the canary builds of Magisk a try
Idledev said:
Managed to get it working today! Upgraded my Pixel XL to the Android Q beta. By doing this, I had to run Magisk canary build. Installed square, enabled Magisk hide, rebooted and it worked fine! Not sure if the Android Q beta has anything to do with it,but give the canary builds of Magisk a try
Click to expand...
Click to collapse
That's awesome! What canary build did you use?
I tried the latest build a few weeks ago and it didn't work for me
Build 18120
Idledev said:
Build 18120
Click to expand...
Click to collapse
No luck for me...
I updated to the latest canary build, cleared all data from square reader app, selected magisk hide, rebooted the device. After it booted up I tried to run it and it still detected root. I have a feeling that the OnePlus OS does something that doesn't totally allow me to hide root from the square reader app. It's annoying because for other apps root can be hidden
Maybe there's something in the Android Q build that lets you hide root better
Something that seems reliable right now on 18.1, Pixel Experience and OOS :
Combine Magisk Hide with Magisk "Core Mode". This seems to do the trick for now, Google Pay is triggered with normal mode, but works in Core Mode. Same for Snapchat and banking apps like N26.
But within this, you can't use any module.
kage00 said:
I also went into battery optimization settings to stop magisk from being put to sleep (which might stop magisk hide from working..?), that didn't work either.
Click to expand...
Click to collapse
This is always a good idea, on OOS at least, Magisk being optimized sometimes prevents the granting of root rights to apps, it never reacts to kernel applications requesting root on startup for example.
There's an issue with Googlypay services apparently. You need to downgrade it (remove factory updates) so it's down to version 14.something and then it should work.
You need to disable admin rights and background data to try to prevent autoupdates as well. This thread may be useful?
https://forum.xda-developers.com/ap...e-pay-magisk-discussion-t3906703/post79155616
DaveW1972 said:
There's an issue with Googlypay services apparently. You need to downgrade it (remove factory updates) so it's down to version 14.something and then it should work.
You need to disable admin rights and background data to try to prevent autoupdates as well. This thread may be useful?
https://forum.xda-developers.com/ap...e-pay-magisk-discussion-t3906703/post79155616
Click to expand...
Click to collapse
Hmm, I'm running the magisk xXx ROM and google pay is completely debloated/removed. when I get a spare half hour I might try removing the xXx module and flashing back to stock and following the advice in that thread. I'll let you know how it goes
kage00 said:
Hmm, I'm running the magisk xXx ROM and google pay is completely debloated/removed. when I get a spare half hour I might try removing the xXx module and flashing back to stock and following the advice in that thread. I'll let you know how it goes
Click to expand...
Click to collapse
Ummm yeah.. then the problem doesn't lie within Google pay it lies within the modifications that you are using.
I have to say I have never had any issues with Google pay or Android pay or any banking app using magisk. I don't even have to hide anyting. Of course I'm also not using any modified ROMs or kernels either
Hi guys,
I have this issue for a couple years now and I just cannot find a solution!
Google Pay, and 4 banking app from two different countries work fine with my 1+6 (stock ROM OOS 9.0.9 with magisk 19.4 - 7.3.4) but Square does not.
Did anyone find a solution?
Magisk config:
Magisk hide
Two modules OOS phone record and youtube
No core mode
All banking app and Square hidden
Hi title says all,
If you root your device is it possible to use snapchat?
On my rooted samsung device i was gettting after a few days a temporary ban.
Thanks, ?
Snapchat should work fine. I had one time over this weekend i got banned for 12 hours but at the time my Magisk was crashing from updating without removing substratum theme.
As long as you enable magisk hide and pay attention to updates, you should be fine.
You can use Snapchat if you don't install Xposed, I do know that much. Xposed gives you a temp. ban. There might be a work-around, but if you don't need that, you're good to go anyways
Don't have OP yet , but with other devices I've found that enabling Hide on Magisk for Snapchat actually makes things worse
Do others using Magisk have to enable Hide to use Snapchat?
jcrompton said:
Don't have OP yet , but with other devices I've found that enabling Hide on Magisk for Snapchat actually makes things worse
Do others using Magisk have to enable Hide to use Snapchat?
Click to expand...
Click to collapse
I have always hid Snapchat and Google Pay, along with other Google apps and never had an issue.
I have snapchat and I don't hide it from Magisk.
Sent from my GM1915 using Tapatalk
had issues on my Pixel 3XL
everything works perfectly fine on the OP7Pro
Well after a week rooting my device i was getting issues. But now i dont wanna risk a permanent ban for the sake of rooting ?
How to use Snapchat with magisk (After Ban)
bartjeh1991 said:
Well after a week rooting my device i was getting issues. But now i dont wanna risk a permanent ban for the sake of rooting
Click to expand...
Click to collapse
Follow these steps to use Snapchat with magisk -
1.) Update to latest Magisk stable build v20.0 - https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2.) After updating magisk, Go to Magisk Manager > Magisk Hide and check/enable Snapchat and Google Services (all services have to be marked).
3.) Hide Magisk Manager by it self, go to Magisk Manager > Settings and "Hide Magisk Manager" so it will repack Magisk Manager with random name.
4.) Delete "busybox" binary from /system/xbin directory and install BusyBox module from Magisk Manager > Downloads.
5.) Clear data and cache of Snapchat, try to login this time, it will work for sure, if it doesn't, login to this and click unlock my account - https://accounts.snapchat.com/accounts/login?continue=https://accounts.snapchat.com/accounts/welcome
I have tried this myself and it works, my first main account was permanent banned on magisk canary build, After that I deleted that account and started out with fresh new account.
Tested on -
Samsung Galaxy S9+
Rom - Ultimate Rom v11.3
Magisk - v20.0 (Stable)
Kernel - ElementalX
ricketrash said:
You can use Snapchat if you don't install Xposed, I do know that much. Xposed gives you a temp. ban. There might be a work-around, but if you don't need that, you're good to go anyways
Click to expand...
Click to collapse
You won't get a temp ban with xposed. I'm even using SnapTools (Snapchat modifications) along with xposed and I've been fine for about 3 months now.
I have problem to enroll device on company portal(intune)
"Can't create work profile because policy prevents custom OS"
Device status : rooted
Are there any way to enroll Work profile(intune) on knox tripped
There are magisk modules available, but they are not stable. Intune will detect root after a few days and your work profile will stop working.
I also need workprofile on my phone, hence have not rooted.
cyclonemon said:
I have problem to enroll device on company portal(intune)
"Can't create work profile because policy prevents custom OS"
Device status : rooted
Are there any way to enroll Work profile(intune) on knox tripped
Click to expand...
Click to collapse
Try knox patch lsposed module
cyclonemon said:
I have problem to enroll device on company portal(intune)
"Can't create work profile because policy prevents custom OS"
Device status : rooted
Are there any way to enroll Work profile(intune) on knox tripped
Click to expand...
Click to collapse
Lsposed module knokpatch like the other user said. Or use a custom rom with work profile patched, like BeyondRom. This assuming intune will work as the samsung secure folder works.
Also dont forget fix safetynet and you can use shamiko too. and hide root from intune, and from the normal apps in magisk.
If you have or install lsposed you can use hide my applist module too to hide any app or multiple you want from the apps you choose to not see them
Astral said:
Try knox patch lsposed module
Click to expand...
Click to collapse
marquelito said:
Lsposed module knokpatch like the other user said. Or use a custom rom with work profile patched, like BeyondRom. This assuming intune will work as the samsung secure folder works.
Also dont forget fix safetynet and you can use shamiko too. and hide root from intune, and from the normal apps in magisk.
If you have or install lsposed you can use hide my applist module too to hide any app or multiple you want from the apps you choose to not see them
Click to expand...
Click to collapse
Thank you all,
this issue has been solved when rooted by magisk delta and your recommendation, but I have new issue intune company hasn't responed when rooted by kernelsu.
Could you help me please for study case ?
When I first rooted my phone, everything was fine but after a few days some apps started showing up as "This app won't work on your device"
It wouldn't be a problem since I can just download the APK's, but I need to use the Revolut app, it is only available as a mobile app and when you don't install it from the Play store, it just doesn't work.
Can anyone show me a workaround for this?
Maybe a way to trick play store into letting me download all the apps as usual
or a way to trick the app into thinking it's been installed from the play store.
I thought about locking the bootloader again (OEM) but it'll wipe all data, and I don't want that. Because it's been a few months since I rooted my phone and I have a lot of data.
My phone is Samsung Galaxy S10E - SM-G970F if this info means anything.
hmm, try unrooting it, install all apps you need, and then re-root it again.
NikolaTechGuy said:
hmm, try unrooting it, install all apps you need, and then re-root it again.
Click to expand...
Click to collapse
Rooting wipes all the data tho
Quidney said:
When I first rooted my phone, everything was fine but after a few days some apps started showing up as "This app won't work on your device"
It wouldn't be a problem since I can just download the APK's, but I need to use the Revolut app, it is only available as a mobile app and when you don't install it from the Play store, it just doesn't work.
Can anyone show me a workaround for this?
Maybe a way to trick play store into letting me download all the apps as usual
or a way to trick the app into thinking it's been installed from the play store.
I thought about locking the bootloader again (OEM) but it'll wipe all data, and I don't want that. Because it's been a few months since I rooted my phone and I have a lot of data.
My phone is Samsung Galaxy S10E - SM-G970F if this info means anything.
Click to expand...
Click to collapse
you must pass safetynet as well as play integrity api in order for the apps to reappear. You can check this status by downloading the application YASNAC for safetynet status and Play Integrity API checker for checking play integrity status.
If your using magisk then you can flash safetynetfix module from here.
Flashing it should make the Basic integrity and cts profile check from False to true in yasnac
It should also turn Basic Integrity and Device Integrity from a Cross to a Tick
Strong integrity will always fail for rooted users. so forget abt that
Then go to apps > find playstore > storage > clear data
Open playstore again and you'll see an outdated UI dont worry it'll restore on the next app opening
in playstore then tap on your profile picture at the top right then go to settings. Scroll down and see if the device is play protect certified.
If it is the apps should reappear.
This is way too overkill tbh. you could just install Aurora store and call it a day since its litt playstore without accounts and stuff.
Captain_cookie_200 said:
you must pass safetynet as well as play integrity api in order for the apps to reappear. You can check this status by downloading the application YASNAC for safetynet status and Play Integrity API checker for checking play integrity status.
If your using magisk then you can flash safetynetfix module from here.
Flashing it should make the Basic integrity and cts profile check from False to true in yasnac
It should also turn Basic Integrity and Device Integrity from a Cross to a Tick
Strong integrity will always fail for rooted users. so forget abt that
Then go to apps > find playstore > storage > clear data
Open playstore again and you'll see an outdated UI dont worry it'll restore on the next app opening
in playstore then tap on your profile picture at the top right then go to settings. Scroll down and see if the device is play protect certified.
If it is the apps should reappear.
This is way too overkill tbh. you could just install Aurora store and call it a day since its litt playstore without accounts and stuff.
Click to expand...
Click to collapse
Yes but if I install it from the Aurora store I won't be able to use Revolut probably.
Also I installed the module, and though the YASNAC check has 2 ticks, the Play Integrity checker says failed on "Device integrity" and "strong integrity." What do i do then?
Quidney said:
Yes but if I install it from the Aurora store I won't be able to use Revolut probably.
Also I installed the module, and though the YASNAC check has 2 ticks, the Play Integrity checker says failed on "Device integrity" and "strong integrity." What do i do then?
Click to expand...
Click to collapse
hm what method of rooting do you use?
Captain_cookie_200 said:
hm what method of rooting do you use?
Click to expand...
Click to collapse
if you flashed the safetynet fix in magisk already then im afriad i dont know what else is wrong
Captain_cookie_200 said:
hm what method of rooting do you use?
Click to expand...
Click to collapse
Downloaded the firmware, and changed it using magisk, flashed it using ODIN.
It's Magisk 25.2
Zygisk: Yes
Ramdisk: No
But I also have the "Hide Magisk" option, and Systemless Hosts module
Captain_cookie_200 said:
if you flashed the safetynet fix in magisk already then im afriad i dont know what else is wrong
Click to expand...
Click to collapse
Yep I did.
Quidney said:
Yep I did.
Click to expand...
Click to collapse
i dont know then. i passed safety net on one ui 5 on galaxy A32 4G using that module
Captain_cookie_200 said:
i dont know then. i passed safety net on one ui 5 on galaxy A32 4G using that module
Click to expand...
Click to collapse
I also passed the check after the 25th reboot. It took some time to adjust I guess.
But I cannot hide my magisk launcher, it gets detected by Revolut. Welp
Quidney said:
I also passed the check after the 25th reboot. It took some time to adjust I guess.
But I cannot hide my magisk launcher, it gets detected by Revolut. Welp
Click to expand...
Click to collapse
Actually there is a way to fix that as well.
First of all go to magisk then press the gear icon on top right then select Hide the Magisk app. Allow it to install unknown apps. Give it a good name Let it do its work. do not go to home or anywhere while it is reinstalling the apk as something else
Second of all download shamiko from here.
First make sure you have enforce denylist disabled in the magisk's settings. Yep disabled. if it is enabled toggle it off
Then flash shamiko and reboot. Now once you boot back into the system. Open magisk again (or the new reinstalled renamed magisk app) and go to settings and then go to configure denylist. Now find your app and press the checkbox
Now see if it bypasses the root detection. if not then clear all your apps in your recents and try again. This trick always helps to get around apps with root checks.
Captain_cookie_200 said:
Actually there is a way to fix that as well.
First of all go to magisk then press the gear icon on top right then select Hide the Magisk app. Allow it to install unknown apps. Give it a good name Let it do its work. do not go to home or anywhere while it is reinstalling the apk as something else
Second of all download shamiko from here.
First make sure you have enforce denylist disabled in the magisk's settings. Yep disabled. if it is enabled toggle it off
Then flash shamiko and reboot. Now once you boot back into the system. Open magisk again (or the new reinstalled renamed magisk app) and go to settings and then go to configure denylist. Now find your app and press the checkbox
Now see if it bypasses the root detection. if not then clear all your apps in your recents and try again. This trick always helps to get around apps with root checks.
Click to expand...
Click to collapse
Just noticed since you have magisk hide your either using magisk delta or an older version of magisk. I guess you could just use magisk hide but incase that isnt working the method above is the way to go.
Captain_cookie_200 said:
Just noticed since you have magisk hide your either using magisk delta or an older version of magisk. I guess you could just use magisk hide but incase that isnt working the method above is the way to go.
Click to expand...
Click to collapse
I have 25.2 (25200), Zygisk.
But There's an option in the settings right now it says "Restore the Magisk App" because I've already hidden it.
Captain_cookie_200 said:
Actually there is a way to fix that as well.
First of all go to magisk then press the gear icon on top right then select Hide the Magisk app. Allow it to install unknown apps. Give it a good name Let it do its work. do not go to home or anywhere while it is reinstalling the apk as something else
Second of all download shamiko from here.
First make sure you have enforce denylist disabled in the magisk's settings. Yep disabled. if it is enabled toggle it off
Then flash shamiko and reboot. Now once you boot back into the system. Open magisk again (or the new reinstalled renamed magisk app) and go to settings and then go to configure denylist. Now find your app and press the checkbox
Now see if it bypasses the root detection. if not then clear all your apps in your recents and try again. This trick always helps to get around apps with root checks.
Click to expand...
Click to collapse
I'm on the phone with my friend while she sleeps so I cannot reboot the phone >_<
But I'll update you tomorrow probably if it works.
Quidney said:
I have 25.2 (25200), Zygisk.
But There's an option in the settings right now it says "Restore the Magisk App" because I've already hidden it.
Click to expand...
Click to collapse
oh i see. wait how.do you have magisk hide then
Quidney said:
I'm on the phone with my friend while she sleeps so I cannot reboot the phone >_<
But I'll update you tomorrow probably if it works.
Click to expand...
Click to collapse
oh i see. i just tested it on my device and yes it works. the shamiko method is listed prevents the root detection. hope it works fine for you
Captain_cookie_200 said:
oh i see. wait how.do you have magisk hide then
Click to expand...
Click to collapse
I don't have "Magisk Hide" I think that is another feature (Superuser -> Hide) which does not exist for me.
Quidney said:
I don't have "Magisk Hide" I think that is another feature (Superuser -> Hide) which does not exist for me.
Click to expand...
Click to collapse
magisk hide was removed. anyways try the shamiko method and tell if it works
Captain_cookie_200 said:
magisk hide was removed. anyways try the shamiko method and tell if it works
Click to expand...
Click to collapse
Yep everything worked out. I have Revolut now, and it doesn't detect magisk or root.
I still don't have Google Pay, but that's a job for future me.
Hi All,
I have recently updated Barclays mobile app on my OnePlus 6 rooted running LOS 19 but the app today detected the root (probably the latest update enable that). So I have cleared the data and cache however I cannot go through the menu to access my account and I get error 00006 now.
I have magisk hide enabled and this has been working with Barclays and the other banking app for a year now (excluding Santander which detects the root anyway)
Do you have any suggestions, please?
I'm in the same boat. Magisk delta with zygisk and app hidden etc etc incl. deny list latest Barclays app still detects root. Have even tried deleting Fox folder, in case it starts seeing that recovery folder. Tried lastest canary build, still the same. Anyone had success with running the latest Barclays app rooted? Poco F3 user BTW, but the principles should be the same...
Do you know if removing the root (magisk) fixes the issue?
reg66 said:
I'm in the same boat. Magisk delta with zygisk and app hidden etc etc incl. deny list latest Barclays app still detects root. Have even tried deleting Fox folder, in case it starts seeing that recovery folder. Tried lastest canary build, still the same. Anyone had success with running the latest Barclays app rooted? Poco F3 user BTW, but the principles should be the same...
Click to expand...
Click to collapse
danc.940 said:
Do you know if removing the root (magisk) fixes the issue?
Click to expand...
Click to collapse
Nope, haven't tried yet... But i'm guessing after removing root and clearing app data it would work...
reg66 said:
Nope, haven't tried yet... But i'm guessing after removing root and clearing app data it would work...
Click to expand...
Click to collapse
Actually, the app might still recognise custom rom. Can't face stock miui just over banking app. What a blow
reg66 said:
Actually, the app might still recognise custom rom. Can't face stock miui just over banking app. What a blow
Click to expand...
Click to collapse
Is there a way to hide also the unlocked bootloader? We won't know until we try it I guess. There is also a Reddit post where many people seem to have the same problem.
Keep an eye on that too until we find a solution.
Do you know where we could get the version of the app that still works with magisk? Is it possible to export the app? Maybe we can find someone with an old version and ask them to share the apk?
A way to roll back has been posted by u/SuzannaBadger in the Reddit thread, pasting here for visibility:
Hi,
I've found a temp fix for this for now.
Steps are as below:
1. Uninstall the current Barclays banking app.
2. Go to play store,settings,network settings and turn off 'auto update apps'
3. Download the old Barclays app from: https://barclays-bank-plc-banking.en.uptodown.com/android/download (it's legit)
4. Install the app.
5. Go into Majisk, settings, configure denylist and tick all Barclays options (may already be ticked, if this is the case ignore step 5)
6. Restart phone.
7. Open Barclays app and setup as you usually would.
Hopefully this works for you. Applist detector is even detecting I have the Majisk app (even though I have Shamiko and have hidden it) but the Barclays app still works as it's the previous version.
Click to expand...
Click to collapse
reg66 said:
Actually, the app might still recognise custom rom. Can't face stock miui just over banking app. What a blow
Click to expand...
Click to collapse
Is there a way to hide also the unlocked bootloader? We won't know until we try it I guess. There is also a Reddit post where many people seem to have the same problem.
https://www.reddit.com/r/Magisk/comments/118yl7n
Keep an eye on that too until we find a solution.
Do you know where we could get the version of the app that still works with magisk? Is it possible to export the app? Maybe we can find someone with an old version and ask them to share the apk?
Jenpyon said:
A way to roll back has been posted by u/SuzannaBadger in the Reddit thread, pasting here for visibility:
Click to expand...
Click to collapse
Great thanks for the update.
danc.940 said:
Is there a way to hide also the unlocked bootloader? We won't know until we try it I guess. There is also a Reddit post where many people seem to have the same problem.
Keep an eye on that too until we find a solution.
Do you know where we could get the version of the app that still works with magisk? Is it possible to export the app? Maybe we can find someone with an old version and ask them to share the apk?
Click to expand...
Click to collapse
Not sure about hiding unlock BL, never looked into it. If you've used the linked 2.72.2 barclays app, as i have, be sure to disable auto update in google playstore
EDIT: just seen it in step 2!! however, i just selected do not auto update for that specific app, rather than all apps
danc.940 said:
Do you know if removing the root (magisk) fixes the issue?
Click to expand...
Click to collapse
Yes it does fix the issue. I've checked and now have a hard choice of either restore magisk needing BCR heavily.
danc.940 said:
Is there a way to hide also the unlocked bootloader? We won't know until we try it I guess. There is also a Reddit post where many people seem to have the same problem.
Keep an eye on that too until we find a solution.
Do you know where we could get the version of the app that still works with magisk? Is it possible to export the app? Maybe we can find someone with an old version and ask them to share the apk?
Click to expand...
Click to collapse
Hiding unlocked bootloader most likely wouldn't help as just removing Magisk leaving bootloader unlocked makes Barclays app working perfectly. So they still just detect root and Magisk some other way. What was interesting was that when I removed Magisk and Barclays functionality was restored I run hidden Magisk app to restore Magisk. It asked to restore main Magisk app that I did. And even without restoring Magisk partition and rebooting Barclays stopped working having only Magisk app installed without root.
reg66 said:
I'm in the same boat. Magisk delta with zygisk and app hidden etc etc incl. deny list latest Barclays app still detects root. Have even tried deleting Fox folder, in case it starts seeing that recovery folder. Tried lastest canary build, still the same. Anyone had success with running the latest Barclays app rooted? Poco F3 user BTW, but the principles should be the same...
Click to expand...
Click to collapse
Try downloading an app called Ice Box and freeze Magisk with it.
That fixed the issue for the bank app I use.
See my replies here guys Post
All I've posted my notes on the reddit page above
Also I have a Santander account and I could never get this app working either!!!
Note this method still doesn't work on Santander!!
sound2005 said:
See my replies here guys Post
All I've posted my notes on the reddit page above
Also I have a Santander account and I could never get this app working either!!!
Note this method still doesn't work on Santander!!
Click to expand...
Click to collapse
Followed steps exactly. Still root is detected
reg66 said:
Followed steps exactly. Still root is detected
Click to expand...
Click to collapse
Thanks for replying back.
What issues did you get, ie FC, root detected etc..?
I'm going to keep trying on my phone and see if I can get this working
Ok guys, this method works 100%!!!
Test on my Samsung Note 8 (Android 10, Custom Rom)
Install this module:
GitHub - HuskyDG/MagiskHide at v1.6
Portable MagiskHide. Contribute to HuskyDG/MagiskHide development by creating an account on GitHub.
github.com
and wipe Barclays data, thats it!!!
Best to have Zygisk off and configure the denylist to get this working
Configure Magisk apps​
As Magisk app does not allow you to configure denylist when zygisk is off. You must toggle Zygisk on temprorily (not reboot) to configurate denylist and toggle Zygisk off after done.
Note that any modules that uses Zygisk will be disabled!!
sound2005 said:
Ok guys, this method works 100%!!!
Test on my Samsung Note 8 (Android 10, Custom Rom)
Install this module:
GitHub - HuskyDG/MagiskHide at v1.6
Portable MagiskHide. Contribute to HuskyDG/MagiskHide development by creating an account on GitHub.
github.com
and wipe Barclays data, thats it!!!
Best to have Zygisk off and configure the denylist to get this working
Configure Magisk apps​
As Magisk app does not allow you to configure denylist when zygisk is off. You must toggle Zygisk on temprorily (not reboot) to configurate denylist and toggle Zygisk off after done.
Note that any modules that uses Zygisk will be disabled!!
Click to expand...
Click to collapse
I'd tried this with Zygisk off but then USNF had become off and device didn't pass Safetynet. Then with Zygisk on and this module on Barclays still showed 0006. Denylist was configured for Barclays and not enforced.
atreal said:
I'd tried this with Zygisk off but then USNF had become off and device didn't pass Safetynet. Then with Zygisk on and this module on Barclays still showed 0006. Denylist was configured for Barclays and not enforced.
Click to expand...
Click to collapse
Try switching Zygisk on and off.
Reboot phone, wipe data and cache for play store and Barclays and try again mate
sound2005 said:
Try switching Zygisk on and off.
Reboot phone, wipe data and cache for play store and Barclays and try again mate
Click to expand...
Click to collapse
Well. Have to put thoroughly what exactly I meant been done.
1. Added Magiskhide module to Magisk and turned it on. Magisk was last stable 25.2
2. Uninstalled Barclays. Installed Barclays without running it yet.
3. Add Barclays to Denylist. Turn Zygisk off.
Reboot
4. Checked Safetynet with YASNAC. It failed. Checked modules page in Magisk - USNF was off apparently as Zygisk was off. YASNAC had been passed before all this attempts with this module when USNF was on.
4. Run Barclays - 0006.
5. Clear Barclays data. Turn Zygisk on in Magisk.
Reboot
6. YASNAC passed as USNF became on.
7. Run Barclays - 0006
And may I ask to give some light on what is meant that "it is better to keep Zygisk off". What does this "better" mean? Must be off? Then how do they mean to bypass Safetynet with USNF off?
atreal said:
Well. Have to put thoroughly what exactly I meant been done.
1. Added Magiskhide module to Magisk and turned it on. Magisk was last stable 25.2
2. Uninstalled Barclays. Installed Barclays without running it yet.
3. Add Barclays to Denylist. Turn Zygisk off.
Reboot
4. Checked Safetynet with YASNAC. It failed. Checked modules page in Magisk - USNF was off apparently as Zygisk was off. YASNAC had been passed before all this attempts with this module when USNF was on.
4. Run Barclays - 0006.
5. Clear Barclays data. Turn Zygisk on in Magisk.
Reboot
6. YASNAC passed as USNF became on.
7. Run Barclays - 0006
And may I ask to give some light on what is meant that "it is better to keep Zygisk off". What does this "better" mean? Must be off? Then how do they mean to bypass Safetynet with USNF off?
Click to expand...
Click to collapse
Hi
By all means you can try my setup:
Modules enabled:
Magiskhide (by Husky)
Magiskhide Props Config
Systemless host
Magisk v25.2 hidden
Denylist has been configured and Zygisk switch is off.
In Denylist I have the following as blocked:
Google play store
Google play services
My bank app
Oysercard app
Please note I've messed around extensively trying to get this to work and a lot of stuff I've added and remove to test out, so some modules (or even apps on the denylist) may no longer need to be there.
Also on step 3, could you turn Zygisk on (the app will tell you to reboot to apply changes) but do not reboot yet!!!, then turn off Zygist then reboot your phone.
Once rebooted clear cache and data for play store and Barclays
Then try banking app again.
If this still doesn't work, you may have a module triggering Barclays to recognise you have root, in which case you may need to disable/remove said modules.
One prime culprit would be Lsposed, if you have this then remove this as well.
Also please note, taken from developers site:
Configure Magisk apps
As Magisk app does not allow you to configure denylist when zygisk is off. You must toggle Zygisk on temprorily (not reboot) to configurate denylist and toggle Zygisk off after done.