Hello, I've been using Magisk for about 3 years on my Xperia XZ and it's been working without any issues, and I've also been using Bitdefender app for over a year and there have been no conflicts or issues whatsoever, that was the case until today when I was updating Magisk (the manager app also) to the latest version 20.1 and for the manager 7.4.0 then Bitdefender reported both of them as PUA and if I remember correctly as trojan also, I uninstalled them immediately until I get some feedback on this.
So any ideas on this?
False positive, although rooting a phone is a security problem! (that means your scanner is right about reporting it) so either negate/ignore magisk warning in your virus check, or add your virus scanner to magisk-hide.
Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk
broomer68 said:
False positive, although rooting a phone is a security problem! (that means your scanner is right about reporting it) so either negate/ignore magisk warning in your virus check, or add your virus scanner to magisk-hide.
Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk
Click to expand...
Click to collapse
The thing is Bitdefender has no issues with the old versions of Magisk, that's why I'm asking.
I guess I'll just use the old version of Magisk and wait for a newer version than the current one.
Thanks for your time.
Qattos said:
The thing is Bitdefender has no issues with the old versions of Magisk, that's why I'm asking.
I guess I'll just use the old version of Magisk and wait for a newer version than the current one.
Thanks for your time.
Click to expand...
Click to collapse
Like already stated, false positive... Most likely brought on by the new stub apk implementation. Nothing to worry about and if you just repackage the Manager Bitdefender won't be able to detect you have the app installed anyway.
Didgeridoohan said:
Like already stated, false positive... Most likely brought on by the new stub apk implementation. Nothing to worry about and if you just repackage the Manager Bitdefender won't be able to detect you have the app installed anyway.
Click to expand...
Click to collapse
+1
I know it's false positive but the fact that it so easy detects even re-packaged MM and Installer as rooter apps a bit alarming.
gkornaks said:
+1
I know it's false positive but the fact that it so easy detects even re-packaged MM and Installer as rooter apps a bit alarming.
Click to expand...
Click to collapse
Is it detecting the v7.4.0+ stub repackaged Manager? If so, it's doing a damned good job and hats off to them.
If you're not using the v7.4.0+ stub repackaged Manager it's unfortunately impossible to completely hide it...
V7.4.0 re-packaged. The strange things is that all previous versions were never detected.
gkornaks said:
V7.4.0 re-packaged. The strange things is that all previous versions were never detected.
Click to expand...
Click to collapse
I'm assuming you're on an Android version before Pie. If so the stub won't be used (it's new to v7.4.0, and as I said above I wouldn't be surprised if that is what they're reacting to) and completely hiding the Manager isn't possible. You'll likely just gonna have to live with it. Doesn't Bitdefender have a whitelist or something that you can use?
I'm on Pie. There's no whitelist in Bitdefender. I can live with it.
gkornaks said:
I'm on Pie. There's no whitelist in Bitdefender. I can live with it.
Click to expand...
Click to collapse
Now I'm curious. Is the stub installed? And what is it actually reporting about?
Installed directly from previous version of MM. Reporting: Riskware.Rooter.BH
gkornaks said:
Installed directly from previous version of MM. Reporting: Riskware.Rooter.BH
Click to expand...
Click to collapse
You're quite sparse when it comes to information, aren't you? :laugh: Not making it easy...
Let's take it one step at a time: What is the version information for your installed Manager (all possible info, maybe even a screenshot, please)?
Sorry, currently babysitting, wife at work See attached.
gkornaks said:
Sorry, currently babysitting, wife at work See attached.
Click to expand...
Click to collapse
Isn't that just called parenting?
Anyway, your setup is not using the stub (you would see a 3, the stub version, within brackets after your installed version). Meaning that completely hiding the Manager isn't possible and since you're on Pie it also means that broadcasts isn't working properly on your device. Could be caused by updating to Magisk v20.1 with an already hidden Manager. If you unhide the Manager, reboot the device and then rehide it, does it use the stub?
Still the same and yes I've upgraded to v20.1 from hidden MM.
Same here. Had Magisk for 2-3 years never problems until latest magisk manager update.
Strange Behaviour here.
Magisk 22.0 on Oneplus 8 Pro running OpenBeta 7 (Android 11/rooted)
As long as Magisk is running with default name, everything is fine.
As soon as i hide the app with custom Name and ID, Bitdefender pops up with an Alarm stating Magisk as PUA and Riskware/downloader.
Changing Magisk back to normal, everything is fine again.
Kind of annoying.
qudo said:
Strange Behaviour here.
Magisk 22.0 on Oneplus 8 Pro running OpenBeta 7 (Android 11/rooted)
As long as Magisk is running with default name, everything is fine.
As soon as i hide the app with custom Name and ID, Bitdefender pops up with an Alarm stating Magisk as PUA and Riskware/downloader.
Changing Magisk back to normal, everything is fine again.
Kind of annoying.
Click to expand...
Click to collapse
It's not wrong... The stub that is used when hiding the app is a downloader. It's sole function is to download the main Magisk apk and dynamically load it.
Didgeridoohan said:
It's not wrong... The stub that is used when hiding the app is a downloader. It's sole function is to download the main Magisk apk and dynamically load it.
Click to expand...
Click to collapse
OK, so it works as designed.
Fair enough.
I can live with the Alarm in Bitdefender as long as i can use my Banking Apps and trick Microsoft Company Apps.
Same here since today Update of bitdefender... What can i do?
Related
I've seen a few threads on the Blackberry Work app, but they all seemed have become idle at the end of 2017. Has anyone been able to run new versions of Blacberry Work with the new versions of Magisk?
I'm running an unrooted custom ROM, but the way new versions of the ROM are compiled (using Android Clang) are triggering the checker. Was hoping I could flash Magisk to hide root and custom rom detection from the app.
It depends on what the app is detecting, of course, but take a look under "Hiding root from apps" in the troubleshooting guide. The rest of the post might have some useful tips as well.
I ended up installing Magisk and hiding from the app. It works really well, so we can go ahead and close this thread. Thanks for the follow up.
napes22 said:
I ended up installing Magisk and hiding from the app. It works really well, so we can go ahead and close this thread. Thanks for the follow up.
Click to expand...
Click to collapse
Is BB Work still working for you with Magisk? Our company moved to BB Good (now Work) years ago. I stopped rooting back then since it was too much of a hassle to figure out and I need to have my work email. If this works, the only thing holding me back would be getting official updates from OnePlus. I have the 5T.
jvnat said:
Is BB Work still working for you with Magisk? Our company moved to BB Good (now Work) years ago. I stopped rooting back then since it was too much of a hassle to figure out and I need to have my work email. If this works, the only thing holding me back would be getting official updates from OnePlus. I have the 5T.
Click to expand...
Click to collapse
Yes I can confirm that magisk root does work with BB Work. You have to use the "hide" function in the Magisk Manager and select BB work.
FYI
I am using a stock rom with root.
Tip: don't use xposed framework if you want a working BB work app.
I flashed Magisk in my redmi note 3 kate and installed the magisk manager apk app, everything is working fine, but my question is: Should I install phhSuperUse, rather than this variant has SU because it was built to be installed with magisk ?
Excuse me, I'm not very familiar with the subject and I've been reading about this and I'm a little confused
---------- Post added at 10:22 PM ---------- Previous post was at 10:20 PM ----------
What is the difference when using the magisk modules?
always use xposed framework plus S.U. But since I can no longer download some apps in play store I have resorted to install magisk on my device.
Hello,
Is it still working ?
It work with Good for Enterprise , but i am not able to install UEM Client and BB Work ?
UEM Client seems fine and show device as unrooted but then setting up Blackberrry Dynamics failed due to that , any idea ?
Regards,
Darkwa said:
Yes I can confirm that magisk root does work with BB Work. You have to use the "hide" function in the Magisk Manager and select BB work.
FYI
I am using a stock rom with root.
Tip: don't use xposed framework if you want a working BB work app.
Click to expand...
Click to collapse
I have a message bb work data wiped. And installation fails at the last point. How can I solve it?
Greetings
Wysłane z mojego MI 6 przy użyciu Tapatalka
As of yesterday, blackberry is detecting my root for some reason. Nothing has changed so my guess is that it has something to do with my company's policy changing? At this point I'm very confused
napes22 said:
As of yesterday, blackberry is detecting my root for some reason. Nothing has changed so my guess is that it has something to do with my company's policy changing? At this point I'm very confused
Click to expand...
Click to collapse
I am in the same boat. I can no longer get Magisk 18.0 and BB Work (or any of the BB enterprise apps) to function. I immediately get the "jailbroken" message. I have no idea what changed. :crying:
I am going to try 18.1 and will report if things change.
DaCHeF36 said:
I am in the same boat. I can no longer get Magisk 18.0 and BB Work (or any of the BB enterprise apps) to function. I immediately get the "jailbroken" message. I have no idea what changed. :crying:
I am going to try 18.1 and will report if things change.
Click to expand...
Click to collapse
Magisk 18.1, Manager 7.0, and following this guide is what works:
https://www.didgeridoohan.com/magisk/MagiskHide
Make sure the "Basics" are taken care of, manually.
Hide Magisk Manager package under settings, MagiskHide "Work" only now (no "Work Profile" choice present in the new version). I removed all root-requiring apps. The combo here worked. I may go one by one to see if any of those apps made a difference. Regardless, it works following those instructions. Good luck. :good:
DaCHeF36 said:
Magisk 18.1, Manager 7.0, and following this guide is what works:
https://www.didgeridoohan.com/magisk/MagiskHide
Make sure the "Basics" are taken care of, manually.
Hide Magisk Manager package under settings, MagiskHide "Work" only now (no "Work Profile" choice present in the new version). I removed all root-requiring apps. The combo here worked. I may go one by one to see if any of those apps made a difference. Regardless, it works following those instructions. Good luck. :good:
Click to expand...
Click to collapse
Perfection, thanks so much. Running DU on taimen with Magisk 18.1 substratum TitaniumBackup Franco app. All good!
Sent from my Pixel 2 XL using Tapatalk
Blackberry Appstore
bigknowz said:
Perfection, thanks so much. Running DU on taimen with Magisk 18.1 substratum TitaniumBackup Franco app. All good!
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
@DaCHeF36 Spoke too soon, not able to load BB Access or Appstore, thoughts?
bigknowz said:
@DaCHeF36 Spoke too soon, not able to load BB Access or Appstore, thoughts?
Click to expand...
Click to collapse
I'm not sure about the Appstore, but I am stuck at an "Authenticating" screen for Access. If I make any progress I'll let you know.
Canary
DaCHeF36 said:
I'm not sure about the Appstore, but I am stuck at an "Authenticating" screen for Access. If I make any progress I'll let you know.
Click to expand...
Click to collapse
Everything works on Canary, running 18100.
bigknowz said:
Everything works on Canary, running 18100.
Click to expand...
Click to collapse
Magisk 19.0 and the new 7.1.1 Manager combination seem to work with all BB apps. Maybe it's just me, but the Work Profile option returned in Hide.
Are there any dependencies for BB apps we need to also hide from Magisk?
DaCHeF36 said:
Magisk 19.0 and the new 7.1.1 Manager combination seem to work with all BB apps. Maybe it's just me, but the Work Profile option returned in Hide.
Click to expand...
Click to collapse
I only need to use the BB work app, are you hiding any other app except BB Work ? Also,a) are you hiding the Magisk Manager, b)using Magisk Hide to hide BB Work or c)doing both?
TarunN5 said:
I only need to use the BB work app, are you hiding any other app except BB Work ? Also,a) are you hiding the Magisk Manager, b)using Magisk Hide to hide BB Work or c)doing both?
Click to expand...
Click to collapse
Work and Work profile setup are hidden. Work profile setup is definitely there again. I use Access, Tasks, and Connect too. I have them all hidden even though that may be overkill. I hide Magisk Manager using the built in package option too. I also followed the guide to ensure that all settings like debug, etc. were off. Gold. I excluded the BB apps from auto-updating. I don't plan to upgrade them unless the back-end requires it at some point.
DaCHeF36 said:
Work and Work profile setup are hidden. Work profile setup is definitely there again. I use Access, Tasks, and Connect too. I have them all hidden even though that may be overkill. I hide Magisk Manager using the built in package option too. I also followed the guide to ensure that all settings like debug, etc. were off. Gold. I excluded the BB apps from auto-updating. I don't plan to upgrade them unless the back-end requires it at some point.
Click to expand...
Click to collapse
Thanks, can you please tell me what exactly do you mean by "work profile" and "work profile setup". The app I see is i dont see a work profile app in the play store either. Can you also please send a screenshot of the BB apps that you have hidden in Magisk? This is the first time I'm using BB on my phone so pardon my noobness
I am using the DnB online banking app. The new version of the app, released a few days ago, detects magisk root with hide turned on. Safetynett is also intact. Thought it may be of interest; I will be using the older version for now.
Link to app page:
https://play.google.com/store/apps/details?id=no.apps.dnbnor
caniko2 said:
I am using the DnB online banking app. The new version of the app, released a few days ago, detects magisk root with hide turned on. Safetynett is also intact. Thought it may be of interest; I will be using the older version for now.
Link to app page:
https://play.google.com/store/apps/details?id=no.apps.dnbnor
Click to expand...
Click to collapse
I have the same issue with Santander Wallet. But SafetyNet is intact and I am able to use GPay.
Please share if you find a solution elsewhere.
Any solution to this?
My banking app checks if ADB debugging is enabled, but it still says "root detected". If I disable ADB debugging, it works fine
Sent from my MI 5 using Tapatalk
Same thing with the Barclays banking app. It was working fine until a few days ago with Magisk Hide. Now, the app sends a superuser request and no matter what you choose (grant or deny), it detects the phone is rooted and gives a message that it doesn't support rooted devices. Also, the app hasn't updated since January 4th, so something else must have changed.
Edit. Using this method worked for me https://forum.xda-developers.com/apps/magisk/santander-app-custom-rom-root-device-t3794753/post77321403#post77321403
I use two apps which are detecting root in my OnePlus 6 with OOS Beta 11 and Magisk 18:
VR-SecureGo
Die TK-App
Same problem
Well, I am not using a "Banking" app. But can say that an install of the Marlboro app.!!!
Install was ok. However, when starting app, it said that my phone was rooted! Then it stated that it can not be used on my devise and shut down. Will not actually restart now!
Devise - Samsung Galaxy S5, On Lineage 15.1 latest build, as well as Unofficial 16.0 build. With or with out SmartPack Kernel.
Both using the Latest Magisk 8.1!
(Yes, no Exposed used) just a few modules...
P. S. I can say, in 7.0-7.3 this was NOT an issue.
My only, other issue with 8.0 an 8.1.... Extremely hard to use the 2nd Partition (formatted - Ext4) Using Link2SD Plus! Can say didn't not have this on on prior Versions.
Still trying to fix this, but nothing yet (working many hours this past week) and nothing to stick... Yet!
Tanx for letting me blow off some steam on this...
Anyone that's having issues with root detecting apps could give the new MagiskHide implementation a try (it's been rewritten from scratch). Would be interesting to know if there's any improvement... Currently only found in the Canary builds (as of now at build 18108), but will of course find it's way to a stable release eventually. Having more users test the new implementation before a stable release is of course always nice though...
I tried beta manager, same thing. Unable to pay with Google pay.
Tesco pay+ now detects root as of today. It is enabled in Magisk Hide. App last updated 31st Jan but it was working fine last weekend - Google changed detection possibly?
if you have warez apps (lucky patcher, freedom, creehack, aptoide, acmarket, gameguardian etc) installed it may detect and uses 'root detected' as a generic message
My phone is One Plus 5T with bootloader unlocked and using the BETA latest OxygenOS.
Nothing was updated and from one day to another my google pay does not work anymore. Tried to add the card again, and it told me about "my phone is altered in some ways"
Before magisk was doing the job. Looks like we need to wait for some updates. I am amazed about the only few entries I found in internet about that.
caniko2 said:
I am using the DnB online banking app. The new version of the app, released a few days ago, detects magisk root with hide turned on. Safetynett is also intact. Thought it may be of interest; I will be using the older version for now.
Link to app page:
https://play.google.com/store/apps/details?id=no.apps.dnbnor
Click to expand...
Click to collapse
I got DNB running with magisk Canary , use magisk hide and and systemles hosts in magisk settings .
stian230 said:
I got DNB running with magisk Canary , use magisk hide and and systemles hosts in magisk settings .
Click to expand...
Click to collapse
Does it still work for you? I keep getting phone is rooted with latest Canary build.
SLAiNTRAX said:
Does it still work for you? I keep getting phone is rooted with latest Canary build.
Click to expand...
Click to collapse
It works for me ?. Running magisk canary and DNB app .
fleischbanane said:
I use two apps which are detecting root in my OnePlus 6 with OOS Beta 11 and Magisk 18:
VR-SecureGo
Die TK-App
Click to expand...
Click to collapse
VR SecureGo works for me with this instruction:
https://www.android-hilfe.de/forum/...trotz-magisk.901517-page-2.html#post-11532359
pollonhokairos said:
VR SecureGo works for me with this instruction:
https://www.android-hilfe.de/forum/...trotz-magisk.901517-page-2.html#post-11532359
Click to expand...
Click to collapse
Thank you very much. With Magisk 19 I have zero issues!
Salty Wagyu said:
Tesco pay+ now detects root as of today. It is enabled in Magisk Hide. App last updated 31st Jan but it was working fine last weekend - Google changed detection possibly?
Click to expand...
Click to collapse
I've similar issue, OnePlus 6, latest stock ROM, latest Magisk (v19.2), it detects the root... Can someone suggest me something to resolve this?
Has anyone else than Stian got DNB to work? I am using magisk 19.3 and it's not working.
Hi, today I installed official NHS App 1.3.0 and it detects root just after start. App is on Magisk Hide list and Magisk itself is working. I can use Google Pay and other banking app are working.
Magisk log attached
And what about hiding the Manager itself? More details and tips here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Didgeridoohan said:
And what about hiding the Manager itself? More details and tips here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Click to expand...
Click to collapse
Yes didgeridoohan is right. Hiding magisk manager can solve it.
Sent from my Andromax R I46D1G using Tapatalk
Didgeridoohan said:
And what about hiding the Manager itself? More details and tips here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Click to expand...
Click to collapse
Perfect, I completely forgot about this feature. Now it's working. Thank You.
Chamelleon said:
Perfect, I completely forgot about this feature. Now it's working. Thank You.
Click to expand...
Click to collapse
I tried this (8th June) and the NHS app still detects root. I have made sure there are no files called Magisk..., and deleted the (old empty) Magisk folder. I have only one Manager installed and hidden, and it works for other apps.
Does your copy still work OK?
I'm aware there are further tricks to play, but they mostly require knowledge I don't have and information about what the app is detecting in, for instance, build.prop.
Yup, after last update NHS or Magisk (I don't know witch one) it detects root again.
Chamelleon said:
Yup, after last update NHS or Magisk (I don't know witch one) it detects root again.
Click to expand...
Click to collapse
I had no problem running NHS 1.10.0 with Magisk 19.3 with MagiskHide and repackaged Manager.
That's weird. I tried re-hide magisk and reinstall NHS app and still it detects root.
I only installed the NHS app last week and it flagged up root because I initially forgot to tick it under MagiskHide. Since selecting it though, it hasn't complained about root.
I'm running v1.10.0 of the app, with ianmacd's Magisk builds, both of which are on the latest versions.
I did just notice that I can't take screenshots of the NHS app. Attempting to do so results in a toast message explaining that its blocked by security policies. Banking apps etc all still allow me to take screenshots though.
hshah said:
I only installed the NHS app last week and it flagged up root because I initially forgot to tick it under MagiskHide. Since selecting it though, it hasn't complained about root.
I'm running v1.10.0 of the app, with ianmacd's Magisk builds, both of which are on the latest versions.
I did just notice that I can't take screenshots of the NHS app. Attempting to do so results in a toast message explaining that its blocked by security policies. Banking apps etc all still allow me to take screenshots though.
Click to expand...
Click to collapse
Then it seems that the NHS App (1.10.0 also on mine) must be detecting something else that you haven't got, but I and others have. What version of Android do you run? I'm on 7.1.2 LineageOS (14)
passtim said:
I tried this (8th June) and the NHS app still detects root. I have made sure there are no files called Magisk..., and deleted the (old empty) Magisk folder. I have only one Manager installed and hidden, and it works for other apps.
Does your copy still work OK?
I'm aware there are further tricks to play, but they mostly require knowledge I don't have and information about what the app is detecting in, for instance, build.prop.
Click to expand...
Click to collapse
Did you try to reboot your phone. Sounds stupid but it worked for me. Yesterday I tried to open British Gas app but no luck so I rebooted my phone and now all apps hidden by Magisk are working again.
Chamelleon said:
Did you try to reboot your phone. Sounds stupid but it worked for me. Yesterday I tried to open British Gas app but no luck so I rebooted my phone and now all apps hidden by Magisk are working again.
Click to expand...
Click to collapse
I've powered off and rebooted many times and nothing has changed. Or are you suggesting some specific order of actions?
Does anyone have the NHS installed and working now? I just came to this app at v1.18.0 and it doesn't say detects root but just gives an error massage about technical problem, which I think is probably root related. Canary build 245/20001 and Manager hidden and app on the hide list.
btb55 said:
Does anyone have the NHS installed and working now? I just came to this app at v1.18.0 and it doesn't say detects root but just gives an error massage about technical problem, which I think is probably root related. Canary build 245/20001 and Manager hidden and app on the hide list.
Click to expand...
Click to collapse
A version that worked with Magisk was issued that worked for me.
passtim said:
A version that worked with Magisk was issued that worked for me.
Click to expand...
Click to collapse
Thanks, which version is it and do you still have it?
btb55 said:
Thanks, which version is it and do you still have it?
Click to expand...
Click to collapse
Sorry, should have said. It's 1.19.0.
passtim said:
Sorry, should have said. It's 1.19.0.
Click to expand...
Click to collapse
It's OK, thank you, 1.18.0 is the latest on Playstore, can I ask how you got it?
btb55 said:
It's OK, thank you, 1.18.0 is the latest on Playstore, can I ask how you got it?
Click to expand...
Click to collapse
I just received updates in the normal way from Google Play. I investigated a bit further.
Looking at the versions listed as available I see it's 1.18.0 in the Store.
The NHS app itself on my mobile initially says it is 1.19.0 on the front page as it loads. However, once fully loaded the app then changes its version number to "version 1.19.0 (1.18.0)".
When I go to the Settings, Applications, and inspect the NHS App it says it is 1.18.0.
So take your pick as to what version it really is
passtim said:
I just received updates in the normal way from Google Play. I investigated a bit further.
Looking at the versions listed as available I see it's 1.18.0 in the Store.
The NHS app itself on my mobile initially says it is 1.19.0 on the front page as it loads. However, once fully loaded the app then changes its version number to "version 1.19.0 (1.18.0)".
When I go to the Settings, Applications, and inspect the NHS App it says it is 1.18.0.
So take your pick as to what version it really is
Click to expand...
Click to collapse
Thanks, take your pick indeed
I found the issue, and it may help others, it wasn't rooting that caused the problem but the adblocker. Disabling it gets the app working, I'm going to try and narrow down which ads I can specifically allow just for this app.
Hi, my original plan was keeping my OP7 root-free because I need that banking app - which has an incredibly good root detection.
Long story short, a few days later and went back to my old habits... Magisk, Kernel, you name it. And the banking app stopped working again.
I do pass the safetynet test, have repackaged Magisk Manager. Google Pay is working like a charme. But Fidor bank seems to be better than Google, at least in this regard. I tried logging traffic using adguard, the app does not connect to anything, no dns requests as well.
Most of the times the app won't start at all, sometimes the first screen flashes for a very short period, and sometimes chrome opens with a webpage from the bank telling me my device is modified. How the **** do they know?
Maybe you guys may have a hint in what direction I could continue poking, because carrying a second phone just for banking is a little bit overkill...
h0l said:
Hi, my original plan was keeping my OP7 root-free because I need that banking app - which has an incredibly good root detection.
Long story short, a few days later and went back to my old habits... Magisk, Kernel, you name it. And the banking app stopped working again.
I do pass the safetynet test, have repackaged Magisk Manager. Google Pay is working like a charme. But Fidor bank seems to be better than Google, at least in this regard. I tried logging traffic using adguard, the app does not connect to anything, no dns requests as well.
Most of the times the app won't start at all, sometimes the first screen flashes for a very short period, and sometimes chrome opens with a webpage from the bank telling me my device is modified. How the **** do they know?
Maybe you guys may have a hint in what direction I could continue poking, because carrying a second phone just for banking is a little bit overkill...
Click to expand...
Click to collapse
Did you clear data of the banking app after Repackaging Magisk & adding it to Magisk Hide? I assume you did it.
Sent from my OnePlus6T using XDA Labs
DarkSJ1998 said:
Did you clear data of the banking app after Repackaging Magisk & adding it to Magisk Hide? I assume you did it.
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
I did. And rebooted. And reinstalled. And combinations of those.
A short screenrecord of what is happening as soon as I try to open the app can be found here (youtube link)
I have the exact same Problem
Everything works: Netflix, other banking apps, etc.. Just Fidor. I do not really know how their detection works, but I assume it's not just a root detection.
The weird thing is, it worked flawlessly 2 years ago Now it's just annoying..
Waited a few versions oft Magisk now, however nothing changes.
You're not alone
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Same problem here ... since the new fidor version v3.14 is out, no way to getting it to work. Downgrade to 3.12 is futile, it forces the update to 3.14 immediately.
As an amendment to my post above (where you'll find pretty much all you need to hide from almost any app), I've successfully tested and hidden root from Fidor v3.14.0.1.
https://forum.xda-developers.com/showpost.php?p=79997227&postcount=98
Thank you, the issue seems to have been addressed there. But as far as I can see, the canary version does not have the optional modules, correct? So I think, unfortunately I will have to wait for an adapted release of the regular magisk.
rpc75 said:
But as far as I can see, the canary version does not have the optional modules, correct?
Click to expand...
Click to collapse
I have no idea what that means... Magisk modules works just fine on the Canary releases.
Didgeridoohan said:
As an amendment to my post above (where you'll find pretty much all you need to hide from almost any app), I've successfully tested and hidden root from Fidor v3.14.0.1.
https://forum.xda-developers.com/showpost.php?p=79997227&postcount=98
Click to expand...
Click to collapse
Thanks for sharing!
I have successfully installed the canary Magisk, have Magisk hide enabled, safetynet pass etc.
All bank apps work after adding them to the hide list, for example trying "Kontist" w/o hide gave error, with hide it works.
However, Fidor (3.14.0.1) is still not working for me :/
The app stays open for 1-2 seconds on the canary build, quite a bit longer than on stable version (instant close), clean cache + clean app data, still no luck.
So Fidor must use another detection method that the other bank apps don't have.
Any advice would be greatly appreciated!
dagoban said:
Thanks for sharing!
I have successfully installed the canary Magisk, have Magisk hide enabled, safetynet pass etc.
All bank apps work after adding them to the hide list, for example trying "Kontist" w/o hide gave error, with hide it works.
However, Fidor (3.14.0.1) is still not working for me :/
The app stays open for 1-2 seconds on the canary build, quite a bit longer than on stable version (instant close), clean cache + clean app data, still no luck.
So Fidor must use another detection method that the other bank apps don't have.
Any advice would be greatly appreciated!
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Similar Problem, my bank brought out a new app, that is detecting the root/custom rom somehow. The app closes and shows me security bull**** about root, jailbreak, custom roms. I don't know how everything should be hidden, SafetyNet checks out but this app can detect it. No idea how.
alike03 said:
Similar Problem, my bank brought out a new app, that is detecting the root/custom rom somehow. The app closes and shows me security bull**** about root, jailbreak, custom roms. I don't know how everything should be hidden, SafetyNet checks out but this app can detect it. No idea how.
Click to expand...
Click to collapse
Check the link, one post before yours...
Didgeridoohan said:
Check the link, one post before yours...
Click to expand...
Click to collapse
Thanks, I was already going through that one.
Turns out the Banking app was detecting the Original Magisk Package.
Hiding Magisk Manager itself fixed my problem. Thanks for the link.
Didgeridoohan said:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Click to expand...
Click to collapse
Still did not get Fidor to work. Crashes after the initial first 2-3 seconds. If I uninstall Magisk it works again. Disabling modules, delete files from sd-card, etc. didn't change a thing.
This also seem not to be the problem, since it works after uninstalling Magisk.
Fidor is hidden from Magisk, Magisk is repacked with other name.
Mind giving specific instructions on what you did to make Fidor work on your device?
Thyrador said:
Mind giving specific instructions on what you did to make Fidor work on your device?
Click to expand...
Click to collapse
It's all right there in the link provided. I'm not doing anything that's not described there... Of course, there's a whole lot of things there that I didn't do.
Here's my setup:
Android Pie.
Magisk v19.4 (19307), with hidden Manager.
The app on the Hide list.
My internal storage is full of Magisk files and I never bother to disable any modules (all of the ones I have installed can be hidden without issue). I also have OEM Unlocking disabled, but that's just by chance and not something I've done because of an app detecting it...
Didgeridoohan said:
It's all right there in the link provided. I'm not doing anything that's not described there... Of course, there's a whole lot of things there that I didn't do.
Here's my setup:
Android Pie.
Magisk v19.4 (19307), with hidden Manager.
The app on the Hide list.
My internal storage is full of Magisk files and I never bother to disable any modules (all of the ones I have installed can be hidden without issue). I also have OEM Unlocking disabled, but that's just by chance and not something I've done because of an app detecting it...
Click to expand...
Click to collapse
So basically same setup. Still doesn't work with latest Fidor Release.
Thyrador said:
So basically same setup. Still doesn't work with latest Fidor Release.
Click to expand...
Click to collapse
When you say "basically", what's the difference?
Didgeridoohan said:
When you say "basically", what's the difference?
Click to expand...
Click to collapse
That's the question. Even if I do a complete fresh install without anything else beside Magisk and Fidor: as soon as Magisk is running (hidden manager & Fidor, SafetyNet Pass and certified in PlayStore), Fidor stops working.
Thyrador said:
That's the question. Even if I do a complete fresh install without anything else beside Magisk and Fidor: as soon as Magisk is running (hidden manager & Fidor, SafetyNet Pass and certified in PlayStore), Fidor stops working.
Click to expand...
Click to collapse
You're going to have to start digging deeper then...
I'm trying to use this app: play.google.com/store/apps/details?id=br.com.banrisul
I've added to the hiding list and enable core only mode, it still closes at startup after saying my phone is either root or running a modified system. I've tested with rootbeercheck and it doesn't detect root in any of its tests.
i.imgur.com/60Zs5IH.png
No issues opening the app here... That means Magisk is perfectly capable of hiding from it, but you might have something else in your setup that triggers it.
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Didgeridoohan said:
No issues opening the app here... That means Magisk is perfectly capable of hiding from it, but you might have something else in your setup that triggers it.
Click to expand...
Click to collapse
but what exactly would trigger it? The link talks mostly about methods to hide magisk, I didn't find anything about what to do if magisk is working but the check fails. I've uninstalled titaniumbackup and rootbrowser. I've disable adb and developer options, I've deleted any folder or downloaded file related to magisk or those apps.
I'm running lineageos, would that be it? How would I go about it?
Could be any number of things... Your ROM might be one of them (more details about that?). It's pretty much impossible for me to do anything else but make educated guesses. The only thing I can say with relative certainty is that it shouldn't have anything to do with Magisk (since I can hide from the app just fine when testing).
You do pass SafetyNet, right? Could be that this is one of those apps that actually use SN.
Didgeridoohan said:
Could be any number of things... Your ROM might be one of them (more details about that?). It's pretty much impossible for me to do anything else but make educated guesses. The only thing I can say with relative certainty is that it shouldn't have anything to do with Magisk (since I can hide from the app just fine when testing).
You do pass SafetyNet, right? Could be that this is one of those apps that actually use SN.
Click to expand...
Click to collapse
It passes both checks.
I am running lineage OS 14.1 (Android 7.1.2) on a moto g4.
My main guess is that it's detecting something about your ROM. LOS is well known enough for apps to look for certain properties of it.
Didgeridoohan said:
My main guess is that it's detecting something about your ROM. LOS is well known enough for apps to look for certain properties of it.
Click to expand...
Click to collapse
Yes, after searching around a bit more I found about why. I completely forgot that I had flashed supersu on my phone before flashing magisk. So I guess that's what the app was freaking out about. So I flashed a supersu removal and reflashed my ROM, now the app is working normally
Thanks for the help!
Same problem
Hello everyone
After the last update of my banking app and wallet too
Both apps stopped starting due tl root device detection
While it was working well yesterday
I just updat apps to the last version
I think these app's developers find a way to detect magisk
Of course im hiding and randomly renaming it
hammohammo said:
Hello everyone
After the last update of my banking app and wallet too
Both apps stopped starting due tl root device detection
While it was working well yesterday
I just updat apps to the last version
I think these app's developers find a way to detect magisk
Of course im hiding and randomly renaming it
Click to expand...
Click to collapse
What version of the application do you want?
I have the latest version installed and it does not detect root