Related
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.
Has anyone gotten Samsung Pay to work with Magisk? I've got it installed as a gear plugin and safetynet passes. However, somehow Samsung Pay still detects root, even though it's hidden in magisk hide.
Same. Then this droidx program protecting pay app
Sent from my SM-N910V using XDA-Developers Legacy app
Try the universal safteynet net module
Is your Knox tripped? Samsung Pay might check that independently of the root-status of your phone.
grymkmb said:
Is your Knox tripped? Samsung Pay might check that independently of the root-status of your phone.
Click to expand...
Click to collapse
I'm on an LG
I've got the same issue with galaxy tab 3
I got warranty bit warning was showing on the boot screen, so I'm pretty sure I triggered Knox. The reason I was using magisk was to prevent this issue, but I guess Google figured out how to detect its presence. I downloaded a fresh copy of the firmware, which will cause Knox to reset but it also factory resets the tablet. I will still use magisk on my new s8+ phone. I hope magisk will work more effectively to where I can use exposed and its modules. After jellybean, magisk wasn't able to allow exposed to be used because of the way Android sets up its environment to execute apps. Hopefully soon a work around will be accomplished especially since Oreo is coming to my two devices by the end of the year, I guess if not sooner.
Same problem here; Magisk works but Samsung pay won't work
Even tried freezing magisk. Though still no go must be detecting something.
hkbladelawhk said:
Has anyone gotten Samsung Pay to work with Magisk? I've got it installed as a gear plugin and safetynet passes. However, somehow Samsung Pay still detects root, even though it's hidden in magisk hide.
Click to expand...
Click to collapse
I tried the same thing but couldn't make it work. I think it is due to the fact that the "System Status" is custom (or modified) since magisk modifies the "boot" partition, and that you probably installed a custom recovery to install magisk. That's why OTA also don't work without first flashing back the original boot and recovery images. I don't have an LG to verify that the "System Status" appears on those.
If it does, what could be tried is to install xposed and a module that fakes the system status (if you've got marshmallow or before)
sevenday4 said:
I got warranty bit warning was showing on the boot screen, so I'm pretty sure I triggered Knox. The reason I was using magisk was to prevent this issue, but I guess Google figured out how to detect its presence. I downloaded a fresh copy of the firmware, which will cause Knox to reset but it also factory resets the tablet. I will still use magisk on my new s8+ phone. I hope magisk will work more effectively to where I can use exposed and its modules. After jellybean, magisk wasn't able to allow exposed to be used because of the way Android sets up its environment to execute apps. Hopefully soon a work around will be accomplished especially since Oreo is coming to my two devices by the end of the year, I guess if not sooner.
Click to expand...
Click to collapse
Sorry, once knox is tripped there is no going back. However, installing Magisk fools the phone into thinking knox is still untriggerred (0x0). By reflashing the original firmware, what you did is restore the "boot" partition that was modified by magisk. By doing that, your phone should get back its "official status", allowing OTA. However, Knox will stay tripped. Anyway, Knox does little... and is only used by samsung softwares.
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
Booo!
someone please made an apps that can hide or fake the Knox status.
Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
This is possible by disabling safetynet check at boot level before compiling the kernel
Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
Does this apply for non-Samsung phones? I understand that Knox has a tripped flag, but on a non-Samsung phone, what exactly is "tripped"? As with everyone else, I'm pretty frustrated that I still can't use Samsung pay, even on a phone that passes safety checks and has MagiskHide.
gghose said:
Does this apply for non-Samsung phones? I understand that Knox has a tripped flag, but on a non-Samsung phone, what exactly is "tripped"? As with everyone else, I'm pretty frustrated that I still can't use Samsung pay, even on a phone that passes safety checks and has MagiskHide.
Click to expand...
Click to collapse
Works for me on a Samsung phone, after hide I just had to rename all busybox exe's.
Doesn't work for me on a OnePlus 3T, OOS 4.1.7, rooted with Magisk 14.0. This stopped working after the Samsung Pay (Gear version) was updated right around August 21st. Maybe I'm just missing one or more binaries or apps that still must be hidden. I don't have any busybox apps installed, though I previously did, and I removed the busybox binaries where I knew to find them. Maybe it's detecting Magisk's su install, or some other binary I still need to remove. SafetyNet passes just fine, and I can use AndroidPay and CapitalOneWallet on the phone, but I can't use the SPay tab in the Gear app without getting the "rooted phone" message.
Magisk hide 14
Hi Yeti47: I have a samsung galaxy s8 sm-g950f. It is rooted wit renovate ice and magisk 14. What modules I have to check in magisk hide to make samsung pay working? Please answer me in [email protected]. Thank you so much. Bye.
Finally solved it. Busybox can be installed in /data/local, apart from /system/xbin or /system/bin. Samsung Pay will find it there. After I removed it, I was able to get Samsung Pay (Gear Version) working again on my OnePlus 3T.
Spot on fella, just got it working on OP5 with lineage ROM.
dcbii said:
Finally solved it. Busybox can be installed in /data/local, apart from /system/xbin or /system/bin. Samsung Pay will find it there. After I removed it, I was able to get Samsung Pay (Gear Version) working again on my OnePlus 3T.
Click to expand...
Click to collapse
Root explorer won't let me remove it from xbin. How exactly did you do it?
Sent from my iPad using Tapatalk
i have galaxy s7 with superman rom 2.8 and rooted with magisk. I have a question in case you could help. I'm using version2.8 with magisk for root.
There are a couple of business apps like yammer and skype for bsns that I cannot use as they detect my phone is rooted and won't allow me due to root. Magisk hide doesn't seem to resolve the issue. Any other way I can hide root?
Take a look under "Hiding root from apps" in the troubleshooting guide. Might be some pointers in there that could help.
For Skype you can try this magisk module.
There is an issue with that module on magisk 18 though, root gets detected every so often and kills skype, it actually makes magisk fail safetynet. Toggling magisk hide off and back on in settings will temporarily fix it. Hopefully there's some kind of fix either from magisk or that module because it's severely annoying, but that's the only thing I've found that gets skype working with root.
(edit: dammit, didn't mean to resurrect an almost year old thread, I saw January and a 9 and I got confused )
I need help figuring out a way to hide root from apps like Snapchat or Pokemon go. I know there are other forums, but none that are like this issue I'm having. Magisk doesn't seem compatible with my Samsung Galaxy S8 Active, SM-G892U, as it caused some kind of issue that says to contact someone as something unauthorized was installed on the device. I can't get TWRP either, since that isn't compatible with my device anyway. RootCloak doesn't work, as it doesn't let me switch my root back on. I have nothing else to resort to. I hope there is still a way, otherwise I will unfortunately have to use another phone, or unroot. If anyone has a fix or some method, please help!
How did u achieve root
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.