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
I recently downloaded an app called "Island" from the google play store and stumpled across this problem:
"The security policy prevents the creation of a work profile because a Custom OS has been installed on this device.
I have a Samsung Galaxy S7 (7.0)
Rooted with Unofficial Xposed Framework (by PurifyOS)
Also have Superkernel v2.70 installed.
Is there a way to bypass this using an Xposed module or other rooted applications?
You can try xTouchWiz Xposed module which has a function to fake the system status as Official instead of Custom under the security hacks section.
Alternatively you can use Magisk which should hide everything but Xposed from apps.
What worked for me was connecting the device to wifi or putting in an activated sim card before doing the work profile setup process.
Same problem here (S9 Soldier Rom), did someone made it work?
No one yet?
Has anyone gotten this to work?
Beanvee7 said:
You can try xTouchWiz Xposed module which has a function to fake the system status as Official instead of Custom under the security hacks section.
Alternatively you can use Magisk which should hide everything but Xposed from apps.
Click to expand...
Click to collapse
I don't have Xposed but I recently rooted with Magisk. And MagiskHide is not working for this. Do we have to hide system apps as well? I actually get this error when I add my Gsuite work account.
If you want to make your Google Pay work, make sure you followed those steps below
Use AOSP/LOS or OEM Based rom. MIUI 7 and 8 have problems with SafetyNet [Even if you have Magisk installed]
***MOST IMPORTANT***
[###ROOT###]
Check your Selinux Mode in the About Phone section in Settings.
Selinux is another Google Protection featured with Kitkat in 2014
If you have Permissive, change it to Enforcing using this app [Download Attached Files]
Reboot after applying Enforcing. Don't Delete Selinux Mode Changer, You will lose your Enforcing and will be switched back to Permissive
Use Magisk only - Don't use SuperSu, it doesn't have Hiding features and it is not supported anymore
If magisk triggers your SafetyNet (Main reason why Google pay stops working) install the SafetyPatch module or Magisk Hide Props or check your SafetyNet. That will fix your safety net.
Don't use XPOSED, it will trigger safety net even if magisk hide working. Xposed modify Boot.IMG, the reason for the safety net to trigger. If you cant live without Xposed, use EDXPOSED magisk module, install Riru core, riru edxposed and Xposed installer that will not trigger your safety net (Please note: Android 5.1 Android 6.0 get bootloop because of EdXposed, sorry guys no luck)
Don't Update you GOOGLE PAY - google updates security patch, magisk too Update your Google pay rarely
Always update your magisk and try to download magisk from Github.
Check your Safety net and make sure your Selinux is in Enforcing Mode
???
If that helped you, you are welcome
thanks for this solution.
Regards
Ginifa
dviree said:
???
Click to expand...
Click to collapse
Not sure what is so funny?....
Not able to install
amelbeabk said:
That Google Pay image says your phone is rooted, but it says that as an example as what could have tripped off Safety Net.
Safety Net failing doesn't mean you a rooted. Safety Net is designed to fail if you have an Unlocked bootloader.
Click to expand...
Click to collapse
It sucks, but for things like Google Pay, I'd strongly suggest that you just give up. Google is contractually obligated to play this game with you and try to prevent you from using it on a rooted "insecure" device so they can process card payments.
I have moto G5+ with unlocked bootloader and magisk. Google pay works fine and saftey net does not fail if bootloader is unlocked
I have a custom rom. Only way to get Magist working was to install EdXposed and hide module. SafetyNet Test also says safetynet passes but my gpay doesnt want to work. Assuming its seeing edxposed perhaps. Anything else i can do
dk0dave said:
I have moto G5+ with unlocked bootloader and magisk. Google pay works fine and saftey net does not fail if bootloader is unlocked
Click to expand...
Click to collapse
I also have moto G5+, But still not unlock boothloader. I need study more for unlocked it, however this comment is helpful to get a decision for me, Thanks.
Tutuapp Movie HD Cokernutx
Google Play warns me to uninstall SELinux Changer, then shuts my phone down. I tried uninstalling it then rebooting, but the phone is behaving extremely oddly and shutting down by itself.
Now I have to format it, just to be sure.
murick_show said:
If you want to make your Google Pay work, make sure you followed those steps below
Use AOSP/LOS or OEM Based rom. MIUI 7 and 8 have problems with SafetyNet [Even if you have Magisk installed]
***MOST IMPORTANT***
[###ROOT###]
Check your Selinux Mode in the About Phone section in Settings.
Selinux is another Google Protection featured with Kitkat in 2014
If you have Permissive, change it to Enforcing using this app [Download Attached Files]
Reboot after applying Enforcing. Don't Delete Selinux Mode Changer, You will lose your Enforcing and will be switched back to Permissive
Use Magisk only - Don't use SuperSu, it doesn't have Hiding features and it is not supported anymore
If magisk triggers your SafetyNet (Main reason why Google pay stops working) install the SafetyPatch module or Magisk Hide Props or check your SafetyNet. That will fix your safety net.
Don't use XPOSED, it will trigger safety net even if magisk hide working. Xposed modify Boot.IMG, the reason for the safety net to trigger. If you cant live without Xposed, use EDXPOSED magisk module, install Riru core, riru edxposed and Xposed installer that will not trigger your safety net (Please note: Android 5.1 Android 6.0 get bootloop because of EdXposed, sorry guys no luck)
Don't Update you GOOGLE PAY - google updates security patch, magisk too Update your Google pay rarely
Always update your magisk and try to download magisk from Github.
Check your Safety net and make sure your Selinux is in Enforcing Mode
Click to expand...
Click to collapse
Hello, hope you can help, installed Beyond ROM and Thunderstorm kernel. Google pay not working, SE for Android status shows 'enforcing' when the apk is installed the 'permissions' and ''enforcing' tabs are greyed out. Thank you
Hi,
My question is simple, what is the difference between Xposed and EdXposed, and if there is a way to install it without loosing safety net.
My phone is a Oneplus 7 with android 10.
Thanks and best wishes for the new year!
EdXposed Framework allows to install XPosed Framework on devices running Android 10, Pie, and Oreo .
EdXposed requires your device must be rooted with Magisk v20.2+
By means of MagiskHide you can prevent SafetyNet's hardware attestion will fail.
jwoegerbauer said:
EdXposed Framework allows to install XPosed Framework on devices running Android 10, Pie, and Oreo .
EdXposed requires your device must be rooted with Magisk v20.2+
By means of MagiskHide you can prevent SafetyNet's hardware attestion will fail.
Click to expand...
Click to collapse
So it's impossible?
Biasio said:
So it's impossible?
Click to expand...
Click to collapse
Latest SafetyNet version not only checks for Android got rooted but also for device's bootloader got unlocked. The problem for John Wu - developer of Magisk - is that the new key attestation workflow now is hardware-based, and the code is sent by OEM to Google's server. May be some day he will find a solution ... it's unlikely that MagiskHide will be able to alter the key or intercept the transmission, IMHO.
Resume: Until then SafetyNet works as expected by OEMs and app developers, who have an interest in having an unmodified Android.
To add, you could try magisk module MHPC (Magisk Hide Props Config) which is what you'd use to modify device fingerprint and other system props.
The particular features in MHPC you may want to use which MIGHT get SafetyNet to pass are the Device Simulation and Force Basic Attestation. Combined, along with setting a similar device's fingerprint as long as that selected device isn't designed with hardware attestation, could be enough to fool SN. EdXposed coupled with Magisk's own Hide feature to hide themselves from GSF, GPS, Gpay, etc, should prove successful. The issue lies mostly with which order the software is installed and hidden, sometimes with rebooting being absolutely essential between certain steps. It really is a trial and error process.
Biasio said:
Hi,
My question is simple, what is the difference between Xposed and EdXposed, and if there is a way to install it without loosing safety net.
My phone is a Oneplus 7 with android 10.
Thanks and best wishes for the new year!
Click to expand...
Click to collapse
Turn Off Edxposed module from magisk download and install LSposed apk install it...Goto magisk and download module Riru LSposed...reboot your phone... That's It Check your safety net.... Dont forget to off or remove Edxposed module or any other xposed enhanced framework module you using...lemme know if it worked for you...
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.