Database Develop

Magisk - secure folder, software updates - all not working

I successfully installed magisk on my samsung s8 but now the secure folder, software updates and maybe other apps don't work as they recognise my phone being rooted. I thought the point behind magisk was to hide the phone from looking rooted?
how can i fix this issue?
thanks

You tripped KNOX by flashing custom binaries. You're boned.

is there a way to root the phone without tripping KNOX?

cpu2007 said:
is there a way to root the phone without tripping KNOX?
Click to expand...
Click to collapse
There might be, but I don't think there's any going back for you. As far as I know you can't revert a triggered KNOX...

I installed magisk because I thought knox won't be tripped but I was wrong.
Does anyone know how I can use secure folder, software updates and banking apps now that my app is rooted? they can all recognise my app is rooted and won't work

cpu2007 said:
I installed magisk because I thought knox won't be tripped but I was wrong.
Does anyone know how I can use secure folder, software updates and banking apps now that my app is rooted? they can all recognise my app is rooted and won't work
Click to expand...
Click to collapse
You can still hide Magisk from many apps with Magisk. You'll just have to activate Magisk Hide in the Manager settings. SafetyNet is added by default and any other app that detects root might be fooled if you add it to the Magisk Hide list.
I've said it before and I'm sure I'll say it again. The purpose of Magisk is NOT to hide root and pass SafetyNet (it's just a really nice feature); it's to make your system modifications systemless. You could use this to keep your devices ability to update through OTA, with a couple of extra steps. But, the main advantage for me (and it's the deal-breaker) is that I don't have to redo any of my system modifications after an update. These could be changing screen density, debloating system apps, systemising apps, changing prop values, etc. Before Magisk I could spend 30-45 minutes after an update just setting upp all the system tweaks the way I wanted it, only to realise a couples of days later I'd forgotten something. Now, with Magisk - flash the update, done!
Recommended reading if you're new to Magisk:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
https://forum.xda-developers.com/apps/magisk/magisk-details-dummies-to-developers-t3473486
And if you're having issues:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828

I have activated Magisk Hide and selected the app (Lloyds banking app) then restarted the phone but the app can still recognize that the phone is modified.
I'll look at the other solution that are being proposed in one of the links you've sent and sew how it goes but if anyone has any advice on how to fix this, that will be great.
I have backup for my bootloader,boot,system etc - flashing that back, will it revert the knox?
Thanks

cpu2007 said:
I have backup for my bootloader,boot,system etc - flashing that back, will it revert the knox?
Click to expand...
Click to collapse
I don't do Samsung, but as I understand it: nope.
More info can probably be found in your device's forum here on XDA.

cpu2007 said:
I have activated Magisk Hide and selected the app (Lloyds banking app) then restarted the phone but the app can still recognize that the phone is modified.
I'll look at the other solution that are being proposed in one of the links you've sent and sew how it goes but if anyone has any advice on how to fix this, that will be great.
I have backup for my bootloader,boot,system etc - flashing that back, will it revert the knox?
Thanks
Click to expand...
Click to collapse
Realise this is a very late reply, but if still had no joy with Lloyd's banking app, it will store it's root detection so will still think your phone's rooted even after Magisk Hide. Need to wipe the app data or reinstall.

Question - Android 5, Existing Root, Knox 0x0, No TRWP installation.

Hello, just looking for some clarification if possible before I destroy my device!
So I currently have a T-Mobile Galaxy Note 3 (SM-N900T) that has been towel rooted on kitkat 4.4.2 and then flashfire'd to the latest stock Lollipop 5.0 firmware available for my device to keep root.
I have also FlashFire'd the latest unofficial xposed framework for samsung lollipop 5.0.x by dkcldark and I do not have TRWP, or any custom recovery.
As far as I understand xposed is not compatible, or at least probably not the one im using. I'm willing to sacrifice it and go with Magisk for its ability to hide root from apps if at all possible.
I believe the root I have is not systemless. I also believe the t-mobile note 3 has an unlocked bootloader. Though I'm not 100% positive.
Edit: Final note, within Magisk Manager ... it says I am "Properly Rooted, with 2.82:SUPERSU"
So now on to the questions:
1. If I uninstall my current xposed framework and download Magisk Manager, can I successfully install Magisk and accomplish "hiding root/by passing safetynet" from apps on my device that is currently rooted probably via system without a custom recovery?
2. Will Knox also stay un-tripped at 0x0? Or since the boot.img will be modified, this would be tripped? Even though I did not use a custom recovery, or kernal at all?
Appreciate the replies XDA! Thanks.

I just replaced SuperSU with Magisk in my Galaxy S4. So, to answer your questions.
You'd have to replace SuperSU with MagiskSU in order to enable the hide feature. I don't think Towelroot is usable with Magisk, and since there is no CF-Autoroot for Magisk you'd have to install a custom recovery, which will - if I'm not mistaken - trip Knox. At this point in your Note 3's lifespan, the last thing I would be worrying about is Knox, as your warranty on the device is no longer extant.

So using the Magisk Manager app to install Magisk while on my rooted device without a custom recovery will not work and itself replace SuperSU with MagiskSU while keeping knox 0x0?
I was under the impression if you were pre-rooted u could use Magisk Manager, and it would replace the current root with Magisks. And also that it detects if you have a systemless root or not. Installing itself into the system if that's the type of root you had, otherwise systemlessly.
While yeah my device is no longer under warranty, It's just my own personal preference to preserve it.

custom recovery will trip knox... Magisk needs a custom recovery to install the framework as mentioned
i do understand your preference about maintain knox untripped...
do you really use it? (knox app... It was discontinued .... Samsung official press release ... and I did received a email about it)
or intend further sell your device as "original" at eBay? it's a joke...
imho ... knox at this point is a good security sandbox.... but there is alternative ways to secure your apps and personal/professional data...
If install a custom rom nougat flavour and Magisk performance device will increase It... lookup at note 3 devs thread
best regards
Enviado de meu Lenovo A7010a48 usando Tapatalk

Alrighty thanks for the info!
I do not currently use it, but I also don't use Samsung Pay ... and don't really *need* to play Pokemon go, or Super Mario Run... I'll keep my phone rooted, xposed framework, latest firmware, knox 0x0 for now and possibly consider tripping the knox flag at a later time. Assuming no new "root hide" work-around becomes available and based on future safetynet blocked apps.
The SM-N900T is still a very great device... Additional SD Card slot, removable battery, 3 gigs of ram, 32 gigs space, 2.3GHz Quad-Core CPU, 1080p 5.7" Full HD Super AMOLED® screen.
I see no reason yet to upgrade the phone even being about 4 years old now.

I do remember something like a "safe" custom recovery was for the note 3 line, I have used it on my note 3 from Verizon when I had it.
Just see if you can use it, and flash Magisk with it, unless it is obsolete as it may be was replaced by flashfire?
Sent from my Nexus 6P using XDA Labs

Strephon Alkhalikoi said:
I just replaced SuperSU with Magisk in my Galaxy S4. So, to answer your questions.
You'd have to replace SuperSU with MagiskSU in order to enable the hide feature. I don't think Towelroot is usable with Magisk, and since there is no CF-Autoroot for Magisk you'd have to install a custom recovery, which will - if I'm not mistaken - trip Knox. At this point in your Note 3's lifespan, the last thing I would be worrying about is Knox, as your warranty on the device is no longer extant.
Click to expand...
Click to collapse
Which Custom Rom do you use? I currently cant find a good one to root with magisk (also S4)

Well, my S4 isn't my daily driver anymore, so I threw a stock-based ROM on it: MachineX. That ROM however uses MicroG, so I had to modify an OpenGApps package to remove the MicroG components and replace them with proper Google ones.
If you're still using your S4, use an AOSP 7.1.2 ROM instead. Less hassle, and runs better.

Magisk hide hides the KNOX status. Simply replace SuperSU to MagiskSU.

Deic said:
Magisk hide hides the KNOX status. Simply replace SuperSU to MagiskSU.
Click to expand...
Click to collapse
That it does but I've yet to see anyone successfully use S Pay/Pass after tripping Knox, with or without Magisk.

Strephon Alkhalikoi said:
and since there is no CF-Autoroot for Magisk you'd have to install a custom recovery, which will - if I'm not mistaken - trip Knox.
Click to expand...
Click to collapse
Sure, CF Autoroot does not trip Knox?
But Chainfire says so here: "If you have a KNOX-enabled device, using CF-Auto-Root will trip the KNOX WARRANTY VOID status !" :crying:

@ThemGo: You got me. I must have been drinking when I mentioned CF AutoRoot. The point I was trying to make to the original poster about Knox was that there was no way to keep it at 0x0 if installing Magisk.
But, were you that bored that you had to hunt through a five month old post?

Getting Safety Net to Pass Again After Uninstalling Xposed?

After installing Xposed I realized its current functionality isn't what it used to be so I uninstalled it to restore the ability to pass Safety Net, and it fails both the ctsProfile and basicIntegrity checks. What do I need to do to fix that?
I have Magisk 14.3 installed on a ZTE Axon 2017U, Android 7.1.1, if any of that is relevant.

Cyrus D. said:
After installing Xposed I realized its current functionality isn't what it used to be so I uninstalled it to restore the ability to pass Safety Net, and it fails both the ctsProfile and basicIntegrity checks. What do I need to do to fix that?
I have Magisk 14.3 installed on a ZTE Axon 2017U, Android 7.1.1, if any of that is relevant.
Click to expand...
Click to collapse
You shouldn't have to do anything else - I just tested, and just unchecking Xposed in my Magisk modules list and rebooting was all it took to get SafetyNet completely passing again. No other mods or alterations to /system that might have made it angry?

Xposed triggers SafetyNet, period. There's a Xposed module to pass the CTS profile check but you can't fully pass SafetyNet with Xposed active.

Jaitsu said:
You shouldn't have to do anything else - I just tested, and just unchecking Xposed in my Magisk modules list and rebooting was all it took to get SafetyNet completely passing again. No other mods or alterations to /system that might have made it angry?
Click to expand...
Click to collapse
I didn't have it installed as a module, I had it installed separately. I have it uninstalled now. I don't know what else I could have done to cause Safety Net's check to fail.
Didgeridoohan said:
Xposed triggers SafetyNet, period. There's a Xposed module to pass the CTS profile check but you can't fully pass SafetyNet with Xposed active.
Click to expand...
Click to collapse
I have it uninstalled completely. Any ideas what residual changes could cause this issue?

Cyrus D. said:
I didn't have it installed as a module, I had it installed separately. I have it uninstalled now. I don't know what else I could have done to cause Safety Net's check to fail.
I have it uninstalled completely. Any ideas what residual changes could cause this issue?
Click to expand...
Click to collapse
Ah... I didn't first understand you had uninstalled it in an attempt to pass SN.
Try a dirty flash of your ROM/factory image/firmware package.
Don't forget to uninstall the Xposed installer.

Just want to update that I got it working by running the uninstaller again from TWRP. Apparently the in-app "recovery" uninstallation didn't work properly despite reporting it did.
Edit: I just realized that Netflix was not updating because of it detecting Safety Net checks failed. That company is disgusting. It's locked to 720p outside of systems that have newer DRM, meaning on a PC you have to use Microsoft Edge, nothing else will work. And even then you can't get over 1080p unless it's attached to a certified DRM machine/qualified TV, and has a latest generation Intel chip for more built-in hardware DRM. I wish I was making this up, and I wish I knew that before I was paying for a "4K" account.

Cyrus D. said:
Just want to update that I got it working by running the uninstaller again from TWRP. Apparently the in-app "recovery" uninstallation didn't work properly despite reporting it did.
Edit: I just realized that Netflix was not updating because of it detecting Safety Net checks failed. That company is disgusting. It's locked to 720p outside of systems that have newer DRM, meaning on a PC you have to use Microsoft Edge, nothing else will work. And even then you can't get over 1080p unless it's attached to a certified DRM machine/qualified TV, and has a latest generation Intel chip for more built-in hardware DRM. I wish I was making this up, and I wish I knew that before I was paying for a "4K" account.
Click to expand...
Click to collapse
So actually you mean there was no SafetyNet pass after installing with Xposed uninstaller? Did you eventually fixed it? I guess it's a matter of deleting a few leftover files. Can you point out which files you've deleted (if any) and their storage path1? However, I think you can check these out by looking into the actual Xposed framework zip...
Sent from my Z2 Play using XDA Labs

The Analog Kid said:
So actually you mean there was no SafetyNet pass after installing with Xposed uninstaller? Did you eventually fixed it? I guess it's a matter of deleting a few leftover files. Can you point out which files you've deleted (if any) and their storage path1? However, I think you can check these out by looking into the actual Xposed framework zip...
Sent from my Z2 Play using XDA Labs
Click to expand...
Click to collapse
I actually don't remember much of anything, I switched to a Galaxy S9+ a long time ago and haven't looked back. I thought it'd be intolerable being on a locked device, but so far most functionality seems to work. With ADB commands most things more or less work, such as Greenify. Too bad I can't uninstall all the bloatware (using ADB commands to uninstall them just result in them being reinstalled on reboot).
This is kind of unfortunate for me because now I plan on sticking with Samsung devices, which are usually insanely priced and I have a real beef with Samsung. I got mine on a special promotion for getting $50 contract instead of a $40 one, + $25/m for 24 months for the phone. So $600 for the phone and an extra $120 which I wouldn't have paid otherwise (in Canadian dollars) but I do get some useful functionality out of it so whatever.

Question Does unlocking and flashing a custom rom mess up payment apps

With google coming up with increasingly stricter policies of what deems a device safe and rise of hardware attestation for safetynet, does the note 10 face these issues, or do the payment/banking apps work fine?

I have a Samsung A51 and once my device was rooted the Samsung Pass application will not allow me to record and use any security passwords or biometric security. The application gives me a message stating that because my device is rooted I can no longer use Samsung Pass. However, I am still able to use passwords and biometrics on my bank accounts application.

Last year, I changed the firmware of the LG V35 ThinQ I had and Google Pay would not work for me.

if it comes rooted yes , you will have to hide the root otherwise wont work

Everything works fine for me. I'm using a custom rom and I'm rooted. Play store shows my device is certified, and it passes safetynet on magisk.

TechV said:
Everything works fine for me. I'm using a custom rom and I'm rooted. Play store shows my device is certified, and it passes safetynet on magisk.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Same here

mite_jan said:
if it comes rooted yes , you will have to hide the root otherwise wont work
Click to expand...
Click to collapse
What is the best way to hide the root?

To hide root, enable magisk hide, and change the magisk manager to something else, like mgsk. I enable gpay in magisk hide, and even changed magisk manager to mgsk (You can use any name, but remember the name you change to), and I'm now able to access gpay. Works everytime.

Question How do I hide root from certain apps?

Hey, I rooted my phone just yesterday, and today I went to musescore just to see that they for whatever reason don't allow rooted phones to use their app?
So I tried enabling zygisk, DenyList, and I added musescore to the denylist and restarted my phone, but somehow musescore still knows that I'm rooted.
Is it possible that vbmeta is somehow related? if so then what file exactly am I supposed to flash as vbmeta (I use custom ROM).
If not, then what can I do to hide root from the app?

YayJohn said:
Hey, I rooted my phone just yesterday, and today I went to musescore just to see that they for whatever reason don't allow rooted phones to use their app?
So I tried enabling zygisk, DenyList, and I added musescore to the denylist and restarted my phone, but somehow musescore still knows that I'm rooted.
Is it possible that vbmeta is somehow related? if so then what file exactly am I supposed to flash as vbmeta (I use custom ROM).
If not, then what can I do to hide root from the app?
Click to expand...
Click to collapse
After force deny list did you've deleted caches of google play and google services and reboot? check also google play store inside settings if certified, if certified then it should work for your app too.

Maybe try installing Universal SafetyNet Fix?
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
And some applications can be extra finicky. LIke for me, Google Pay always takes its time to get persuaded about not being rooted. Also there might be other components either of this app or for system apps that might need hiding. I would generally try following guides for making banking apps work.

YayJohn said:
Hey, I rooted my phone just yesterday, and today I went to musescore just to see that they for whatever reason don't allow rooted phones to use their app?
So I tried enabling zygisk, DenyList, and I added musescore to the denylist and restarted my phone, but somehow musescore still knows that I'm rooted.
Is it possible that vbmeta is somehow related? if so then what file exactly am I supposed to flash as vbmeta (I use custom ROM).
If not, then what can I do to hide root from the app?
Click to expand...
Click to collapse
I'm not familiar with that app, but I know that some apps also check for the presence of the Magisk Manager app. If you've already tried Zygisk and the deny list, then another thing to do would be to hide the Magisk app. It the Magisk Manager, go to Settings > Hide Magisk app.

What worked for me is installing Insular ( from Fdroid) and then clone the App that complains about root to the work environment.

I just downloaded musescore and installed it. It hasn't detected root on my phone. I use Shamiko to hide root. Get Fox's magisk module manager from fdroid. Then use it to install Shamiko. Make sure you turn off Enforce Denylist in magisk so Shamiko can enforce the deny list. Hide the magisk app using the feature in magisk. It works for me.

YayJohn said:
Hey, I rooted my phone just yesterday, and today I went to musescore just to see that they for whatever reason don't allow rooted phones to use their app?
So I tried enabling zygisk, DenyList, and I added musescore to the denylist and restarted my phone, but somehow musescore still knows that I'm rooted.
Is it possible that vbmeta is somehow related? if so then what file exactly am I supposed to flash as vbmeta (I use custom ROM).
If not, then what can I do to hide root from the app?
Click to expand...
Click to collapse
Oh yes I can't seem to open musescore too even with safety net pass. But it is because I am using MicroG. I tried it on my other phone with Play Services and it works fine with hidden root (shamiko and magisk disabled) and safety net pass.

BigChungus321 said:
Oh yes I can't seem to open musescore too even with safety net pass. But it is because I am using MicroG. I tried it on my other phone with Play Services and it works fine with hidden root (shamiko and magisk disabled) and safety net pass.
Click to expand...
Click to collapse
I use MicroG as well. I can load the app and use it, I just can't subscribe because it requires GSF to make payment.

IrishJames said:
I use MicroG as well. I can load the app and use it, I just can't subscribe because it requires GSF to make payment.
Click to expand...
Click to collapse
You can open it right? But can you select and open a random piano piece or something like that. For me, the piece loads up then detects something (root, safety net idk) then just tells me I can't for root reasons. I tried using shamiko too and all the root hiding methods I know and I still couldn't open a piece. It does load the main menu for me too on MicroG+patch playstore but can't open the contents.

It's been roughly a month. Has anyone found a fix for this issue yet? There was discussion about the issue here where a dev 'fixed' the app for someone with a rooted phone. However I cant tell what the dev did because all his messages are deleted, for all I know he could of shared an apk or something, guess I'll never know. I've decided to try to get in contact with one of the people whose issue managed to get fixed, although I don't know if he'll ever respond. Apparently in the forum, he told the dev that he assumed the block was intentional. Maybe this could hint us towards a fix because maybe the block doesn't target rooted users?
BigChungus321 said:
I tried using shamiko too and all the root hiding methods I know and I still couldn't open a piece.
Click to expand...
Click to collapse
If thats the case then perhaps the app isin't checking for root? Theres no way musescore has more sophisticated anti-root software than some banking apps out there. Perhaps it's detecting the os that the user uses instead? I can confirm this because my samsung s7 edge with the same lineage os version as my Xiaomi doesn't want to play any scores either. This issue also happens to people who have no custom rom or even no root, it has to do with the os that you use rather than being an issue with root.
So what, did I type 2 paragraphs on a one month old forum just to rant? No. I will find the issue (well, I already found the reason in the text above), and I will try to fix it, not by making any workarounds such as cloning the app but getting the app to reliably work on a rooted / custom rom phone.
EDIT: Maybe using something to spoof the OS to make apps think it's a different OS?

POTENTIAL FIX: So in new versions of magisk, the developer decided to remove magiskhide. Turns out that having magiskhide turned on makes musescore actually be able to function. I tested this on my samsung s7 edge (didn't want to brick my Xiaomi phone by accident just yet and it worked. However I labelled this 'POTENTIAL' as downgrading magisk isin't really a plausible fix and could still be considered a workaround.

RoboNinjaR said:
It's been roughly a month. Has anyone found a fix for this issue yet? There was discussion about the issue here where a dev 'fixed' the app for someone with a rooted phone. However I cant tell what the dev did because all his messages are deleted, for all I know he could of shared an apk or something, guess I'll never know. I've decided to try to get in contact with one of the people whose issue managed to get fixed, although I don't know if he'll ever respond. Apparently in the forum, he told the dev that he assumed the block was intentional. Maybe this could hint us towards a fix because maybe the block doesn't target rooted users?
If thats the case then perhaps the app isin't checking for root? Theres no way musescore has more sophisticated anti-root software than some banking apps out there. Perhaps it's detecting the os that the user uses instead? I can confirm this because my samsung s7 edge with the same lineage os version as my Xiaomi doesn't want to play any scores either. This issue also happens to people who have no custom rom or even no root, it has to do with the os that you use rather than being an issue with root.
So what, did I type 2 paragraphs on a one month old forum just to rant? No. I will find the issue (well, I already found the reason in the text above), and I will try to fix it, not by making any workarounds such as cloning the app but getting the app to reliably work on a rooted / custom rom phone.
EDIT: Maybe using something to spoof the OS to make apps think it's a different OS?
Click to expand...
Click to collapse
Its not opening for me because I'm using MicroG. Like banking apps, MuseScore checks for specific Play Services version. Since microg uses idk android4.4 play services, it will fail to load any Banking Apps or apps of the same kind that uses that check regardless of root 'cause that version's too old and a potential for security. For the OS check, I guess it does check it too. I tried on two emulators and both failed to load a piece as well (might be because of safetynet cuz emulators can't pass it). There are xposed and magisk modules that can spoof OS and even prevent the app from seeing user installed apps. I haven't tried that method because I switched ROM now and got MuseScore working fine even without hiding root.

BigChungus321 said:
Its not opening for me because I'm using MicroG. Like banking apps, MuseScore checks for specific Play Services version. Since microg uses idk android4.4 play services, it will fail to load any Banking Apps or apps of the same kind that uses that check regardless of root 'cause that version's too old and a potential for security. For the OS check, I guess it does check it too. I tried on two emulators and both failed to load a piece as well (might be because of safetynet cuz emulators can't pass it). There are xposed and magisk modules that can spoof OS and even prevent the app from seeing user installed apps. I haven't tried that method because I switched ROM now and got MuseScore working fine even without hiding root.
Click to expand...
Click to collapse
Weird. I have microG and I managed to get musescore working without switching roms. All I did was use safety net fix, enabled zygisk and added it to the deny list. Tried it before and it didn't work, probably because I didn't install safetynet fix. Who knows, maybe it's related to what type of GApps you install. I guess this issue is fixed for now.