Related
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
Hello everyone I currently have an issue to install some banking apps and MobileIron.
I cant use google pay, postfinance TWINT and Mobileiron (because of root getting detected or not passing safetynet or xposed.)
I am not passing Safetynet unless I check "only use core functions" in magisk.
I am hiding MobileIron with MagiskHide and I am also hiding Xposed Installer from MobileIron with suhide.
I already tried having another app block root and xposed detection for MobileIron (uncheck)
What can I do to get it to work?
Please don't tell me to just "unroot" or go back to stock.
Have a great day!
Uninstall xposed , Nothing else i can say
I now the issue well with Postfinance Twint on my rooted Samsung Galaxy S5.
Uninstalling xposed will show no effect, because your phone is locked with a root detection. The only solution I've found was to install the old version 1.1.16.0, the last version before root detecting. This works fine for me (except the QR-Scanner which shows "Error 13: The Scandit SDK license validation failed", but you can use the code input instead).
If someone knows a better solution: post it!
Reading this I stopped my thoughts about rooting. I'm using many banking apps, most of all SEQR for nfc payments. I see myself running into problems getting my finance apps to work once rooted...
lucajasonmiani said:
Hello everyone I currently have an issue to install some banking apps and MobileIron.
I cant use google pay, postfinance TWINT and Mobileiron (because of root getting detected or not passing safetynet or xposed.)
I am not passing Safetynet unless I check "only use core functions" in magisk.
I am hiding MobileIron with MagiskHide and I am also hiding Xposed Installer from MobileIron with suhide.
I already tried having another app block root and xposed detection for MobileIron (uncheck)
What can I do to get it to work?
Please don't tell me to just "unroot" or go back to stock.
Have a great day!
Click to expand...
Click to collapse
did you try "Hide Magisk Manager" option in Magisk Manager?
maybe your bank app is looking for Magisk Manager package too.
I'm not using app that you mention but you can try .
No problems with new version 2.0.20.0 (PostFinance Twint) on rooted Samsung Galaxy S5
I had a similar problem with my banking app. I solved it by installing island app. It basically creates an "island" where you can separate specific apps from the rest of your phone apps. When I put my banking app in the island it worked perfectly (also used magisk hide).
You'll have two versions of the same app when you do this. Just remember to always run the island version of the app not the normal version. There will be a small icon indicating which is which.
Hope it works with you!
lo2ay said:
I had a similar problem with my banking app. I solved it by installing island app. It basically creates an "island" where you can separate specific apps from the rest of your phone apps. When I put my banking app in the island it worked perfectly (also used magisk hide).
You'll have two versions of the same app when you do this. Just remember to always run the island version of the app not the normal version. There will be a small icon indicating which is which.
Hope it works with you!
Click to expand...
Click to collapse
Even with the island app, tez app is not working.
All,
I've been fighting with this for a while and I swear that I'm doing everything right (at least, I think I am).
Here's what I'm running:
1. euro build
2. magisk 23.0 (canary build)
I go through the setup, oem unlock and reboot again. I always run into a problem with magisk patched img and safety net failing.
The threads out there have gotten too thick and off-topic with folks asking for other stuff unrelated to the task at hand. I'm beyond confused with all the threads and need a clean and cohesive approach. Again, people, I need a better direction on this. No one-liners and smart ass answers.
Thank you to those that respond with a solid tutorial. Go layman if need be. =)
Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com
I recommend following this YouTube tutorial step by step. Also, The Magisk 23.0 build STILL has MagiskHide at the moment, so you may want to enable that.
TL;DR, you'll have to install Riru, LSposed, and XPrivacyLua and their respective magisk modules. While the video showed how to pass SafetyNet and get Google Play "Device is Certified", you can implement the same processes to ANY app having issues with root.
dude6595 said:
Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com
Click to expand...
Click to collapse
Once again: Everything that counts is money!
There will be other devs presenting solutions for root and hiding root so that we won't need Magisk any longer.
Until then I'll stay with 23.0
I'm considering buying this phone but if it lacks support for BASIC attestation would mean that hiding root would be impossible and hence the phone would be useless for me.
Zincoshine said:
I'm considering buying this phone but if it lacks support for BASIC attestation would mean that hiding root would be impossible and hence the phone would be useless for me.
Click to expand...
Click to collapse
As of now with magisk 23.0 on Android 11 I'm able to hide everything g-pay all banking credit card apps working. Magisk is changing in Android 12 so I'm unsure. But I believe there are still some modules we can use to hide su access in magisk canary beta for 12.
There are several modules for Magisk that allow for basic. I have been using them since I bought the phone on release day, and have been able to use all apps. I would recommend sticking to Magisk v23 instead of the newer version, as hide has been removed (for now). You will get conflicting advice on this, and will most likely have to make a decision to move to a12 or keep hide down the line.
Lmk if you would like my list or modules.
mattie_49 said:
As of now with magisk 23.0 on Android 11 I'm able to hide everything g-pay all banking credit card apps working. Magisk is changing in Android 12 so I'm unsure. But I believe there are still some modules we can use to hide su access in magisk canary beta for 12.
Click to expand...
Click to collapse
I have no intention of ever updating to Android 12 so this won't matter. My oneplus 5T has been on Android 8.1 for years (mainly because I wanted that sweet sweet taste of the original rovo89 Xposed framework) and it has worked fine but it's clearly nearing the end of its life and has a slightly broken screen.
OP9 LE2110 with OOS 11.2.8.8.LE25BA rooted with Magisk 23. Working apart of banking app. G Pay is ok
Everything is working great with latest Magisk Alpha, Universal SafetyNet Fix and Zygisk enabled with Deny list (New MagiskHide)
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.