I haven't been able to find a thread on this. So here goes… I'm not able to get the Blackberry Work app that my firm uses to load without detecting root on Magisk v14.0,
What i have tried so far:
- Hide the app using Magisk hide
- Hide Magisk Manager
- Restarting the phone after applying settings above
- Switching between Core/Non-core modes
I can't imagine i am the only one experiencing this issue. Would be real greatly if someone could advise if Magisk can be configured to circumvante BB Work's detection. I really need this app for work (non pun intended)
Which version of BlackBerry Work are you using? Is it newer than 2.7.1.822? Is it asking you for an unlock code?
There was a problem with Huawei devices in some versions. They already fixed it, but for unknown reason 2.7.1.822 is still the latest that works on my Zenfone 2.
Wysłane z mojego ASUS_Z00A przy użyciu Tapatalka
I'm using the latest version. I can get pass all the password/codes, the problem starts after that. The app detects the root after login and i'm bounched back to the logon screen again. If i try to login now, it'll block me and i'm asked to contact my system admin.
I'll try to use the version you mentioned below when i get to the office tomorrow and see how it goes.
Still looking for a way to run Blackberry work app on rooted android!
Has anyone found a way??
deepchakra said:
Still looking for a way to run Blackberry work app on rooted android!
Has anyone found a way??
Click to expand...
Click to collapse
I've just checked this and the current version of BB Work from Google Play doesn't work with Magisk.
The last version that works fine is 2.7.1.822
Wysłane z mojego ASUS_Z00A przy użyciu Tapatalka
If you run a ROM unrooted, will Blackberry Work still detect the unlocked bootloader and/or custom recovery?
Can i write a Magisk module to spoof the device name that blackberry work reads? My company has a policy that only allows iPhones on blackberry work.
Anyone have a solution? I'm am running stock Android pie rooted and can't get bb work to work.
stu5797 said:
Anyone have a solution? I'm am running stock Android pie rooted and can't get bb work to work.
Click to expand...
Click to collapse
Im also running Pie. I have BB Work and UEM Client working fine on my setup with Magisk 17 and manager 5.9.6 or whatever that recent one is. I think the key is you need to use Elemental x kernel as well. So assuming you already have TWRP installed then you would:
1. Boot to TWRP
2. Install Elemental X Kernal
3. Install Magisk 17
4. Install Verified Boot signer v8
5. reboot and if you havent already install Magisk Manager
6. Make sure magisk manager is "hidden" in the settings, also use Magisk Hide to hide all the BB apps as well as one called something like "android.auto_generated.rro_..." I also run it in Core Only mode.
7. Reboot, delete any BB apps you might have already installed and then redownload and resetup. Just make sure everything is Hidden in Magisk Hide before launching it the first time. I can assure you that BB apps can be gotten to work with Magisk and Anrdoid 9.
---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------
napes22 said:
If you run a ROM unrooted, will Blackberry Work still detect the unlocked bootloader and/or custom recovery?
Click to expand...
Click to collapse
No it wont.
Thanks so much. I noticed if you install blackberry work and it detects anything, the code deactivates so you can not use the app. It must be a prefect install or it won't work
stu5797 said:
Thanks so much. I noticed if you install blackberry work and it detects anything the code deactivates so you can use the app. It must be a prefect install or it won't work
Click to expand...
Click to collapse
Make sure you hide Magisk Manager and that you use Magisk hide to hide Magisk from both Blackberry Work and Blackberry Work profile.
If you take those 2 steps it'll work.
napes22 said:
Make sure you hide Magisk Manager and that you use Magisk hide to hide Magisk from both Blackberry Work and Blackberry Work profile.
If you take those 2 steps it'll work.
Click to expand...
Click to collapse
This works perfectly. Excellent. :good:
What is "Blackberry Work profile"? I don't see that in the list of apps...
Is anyone still using latest app with magisk?
someuser08 said:
Is anyone still using latest app with magisk?
Click to expand...
Click to collapse
2.16.0.1156 BB Work (disabled auto update) on LineageOS 15.1 (Oreo 8.1.0). Magisk 18.1 with Manager 7.0.0. It's still working albeit the phone must be rebooted from time to time because Magisk disappears. This has been an issue for me on the past few versions of Magisk installed systemless.
I can't seem to get it to work for the last half of year (it was OK before). Its almost like work app detecting something else rather than root...
someuser08 said:
I can't seem to get it to work for the last half of year (it was OK before). Its almost like work app detecting something else rather than root...
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/blackberry-app-magisk-t3742178/page2
I removed magisk completely and it still doesn't work for me - I now think its detection of custom ROMs or unlocked bootloaders that kick in...
someuser08 said:
I removed magisk completely and it still doesn't work for me - I now think its detection of custom ROMs or unlocked bootloaders that kick in...
Click to expand...
Click to collapse
I have auto update turned off on my BB apps now. Currently running 2.16.0.1156 still. With Magisk 19.0 and Manager 7.1.1, all BB apps are working on LineageOS 15.1 (Oreo 8.1). If you use the "Basic" configuration guide for Magisk on these versions, you should be in business.
Settings like debugging and dev options could be some off the culprits preventing proper detection circumvention.
I found an old phone, formatted internal storage and got LOS 15.1 on it. BB is the only app installed(no magisk). After retrieving policies from the server it self wipes due incompatible security policy. I can only assume it detects custom ROM (tried the same with AEX). Is there a module in magisk that makes your phone look like official factory state?
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.
Hello everyone. I have created this thread (hopefully in the right place) to start a discussion on methods/developing methods to get fortnite to work on a rooted device, with magisk installed. Im currently running Dr. Ketan's rom (android pie) on a samsung galaxy note 9 and for obvious reasons (the fortnite galaxy skin) would like to play a few games and have it work without any hiccups. Im not looking to hack the game or any nonsense like that, so if anyone has a currently functioning method that doesnt require me to reflash stock firmware (as i dont have a pc and had to use a friends to unlock bootloader and such) and play on the unrooted device then re-root and install custom rom
evan5935 said:
Hello everyone. I have created this thread (hopefully in the right place) to start a discussion on methods/developing methods to get fortnite to work on a rooted device, with magisk installed. Im currently running Dr. Ketan's rom (android pie) on a samsung galaxy note 9 and for obvious reasons (the fortnite galaxy skin) would like to play a few games and have it work without any hiccups. Im not looking to hack the game or any nonsense like that, so if anyone has a currently functioning method that doesnt require me to reflash stock firmware (as i dont have a pc and had to use a friends to unlock bootloader and such) and play on the unrooted device then re-root and install custom rom
Click to expand...
Click to collapse
Uhh. Its already working. Atleast for me. You just need to hide magisk manager , hide Fortnite app and installer on magisk hide tab, disable usb debugging, and make sure there isn't magisk named folder or files inside your internal storage. That should do it. I'm on the note 8 and it works just fine
white7561 said:
Uhh. Its already working. Atleast for me. You just need to hide magisk manager , hide Fortnite app and installer on magisk hide tab, disable usb debugging, and make sure there isn't magisk named folder or files inside your internal storage. That should do it. I'm on the note 8 and it works just fine
Click to expand...
Click to collapse
Dang, really? Thanks man!
evan5935 said:
Dang, really? Thanks man!
Click to expand...
Click to collapse
Yep!! Its working on mine ....
white7561 said:
Yep!! Its working on mine ....
Click to expand...
Click to collapse
Its not workin for me bro, i hide magisk manage, have no folders or files named makgisk, or even have magisk in the name, hide the root apps with magisk as well as the fortnite installer and app before i launch each of them. It just deosnt work for me :'(
Are you running in magisk core mode, with adb/root disabled as well?
And what about USB/ADB Debugging? Have you turned that off as well?
white7561 said:
Yep!! Its working on mine ....
Click to expand...
Click to collapse
Didgeridoohan said:
And what about USB/ADB Debugging? Have you turned that off as well?
Click to expand...
Click to collapse
Yes but developer options is still on, does that make a difference? Also, I have not tried with magisk core mode off and root disabled, so if you are doing that then that may also be my issue
Edit: i turned on magisk core mode and disabled root and still does not work. Would having lucky patcher installed be an issue?
evan5935 said:
Yes but developer options is still on, does that make a difference? Also, I have not tried with magisk core mode off and root disabled, so if you are doing that then that may also be my issue
Edit: i turned on magisk core mode and disabled root and still does not work. Would having lucky patcher installed be an issue?
Click to expand...
Click to collapse
Prob yeah ...
white7561 said:
Prob yeah ...
Click to expand...
Click to collapse
Definitely was the issue. Deleted lucly patcher and also the Xposed installer (even though exposed isnt on Pie yet) and that combined with everything else did the trick
evan5935 said:
Definitely was the issue. Deleted lucly patcher and also the Xposed installer (even though exposed isnt on Pie yet) and that combined with everything else did the trick
Click to expand...
Click to collapse
Yep. Also . No xposed . Since it fails the safety net [emoji4]. Well. Happy gaming!! [emoji4][emoji4][emoji4]
Working still Season 9 Magisk 19.1? Not I
Anybody still using this method? I get all the way to the drop then get kicked out "can't sync user profile"
Magisk is hidden in a random folder, installer and game both hidden. Tried with Developer settings off and also with them on. Rooted.
Even Google Pay works so I'm head scratching here if there is a system processes that is now needing hidden or what to play the newest Beta. All help appreciated.
I have the same problem. Google pay is working but fortnite not
I'm on a rooted OnePlus 7 Pro and mine just stopped working yesterday. Was fine for about an hour after the Star Wars event then logged on around 10pm and I get kicked out as soon as I exited the bus. Keeps happening over and over again. No other software changes so I'm guessing there needs to be some update to Magisk to get it working again.
Chuck_C said:
I'm on a rooted OnePlus 7 Pro and mine just stopped working yesterday. Was fine for about an hour after the Star Wars event then logged on around 10pm and I get kicked out as soon as I exited the bus. Keeps happening over and over again. No other software changes so I'm guessing there needs to be some update to Magisk to get it working again.
Click to expand...
Click to collapse
Curious what was your setup? To have it work?
Pvt WhoOkid said:
Curious what was your setup? To have it work?
Click to expand...
Click to collapse
Stock OnePlus 7 pro with magisk and TWRP. Epic launcher and Fortnite both hidden in magisk hide. USB debugging turned off. No modules installed. Just using it for root. Worked fine until last night. Gpay and all other safety net apps work fine. It's just Fortnite. Logged in on a friend's Xbox and a really laggy ipad and could play on both so it's not my account - it's definitely the rooted phone and magisk no longer hides itself from Fortnite.
I'm really irritated with the whole thing because I was so close to finishing the season pass and now I can't play at all.
Here's another fix. These last few updates they have added more things to the blacklist. So remember that they basically scans the internal sdcard etc for MagiskManager folder right? Well now they scan TWRP folder too!! So try renaming it to something else without TWRP in it. And see if it works!. Just tried mine and still working just fine!
white7561 said:
Here's another fix. These last few updates they have added more things to the blacklist. So remember that they basically scans the internal sdcard etc for MagiskManager folder right? Well now they scan TWRP folder too!! So try renaming it to something else without TWRP in it. And see if it works!. Just tried mine and still working just fine!
Click to expand...
Click to collapse
Thanks for posting that. I renamed the folder and now it works again.
Now I need to figure out if I can leave it that way or if I need to keep switching the folder name back and forth to be able to use TWRP correctly.
Chuck_C said:
I'm on a rooted OnePlus 7 Pro and mine just stopped working yesterday. Was fine for about an hour after the Star Wars event then logged on around 10pm and I get kicked out as soon as I exited the bus. Keeps happening over and over again. No other software changes so I'm guessing there needs to be some update to Magisk to get it working again.
Click to expand...
Click to collapse
I have pretty much the same setup as you. Do you happen to get lag here and there? During game play? I was able to get mine working again by renaming the folder for trwp as suggested.
Chuck_C said:
Thanks for posting that. I renamed the folder and now it works again.
Now I need to figure out if I can leave it that way or if I need to keep switching the folder name back and forth to be able to use TWRP correctly.
Click to expand...
Click to collapse
With Tasker or Automate, you can set a trigger to automatically rename folder on start of Fortnite and rename back, after the game is closed.
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?
On my phone xiaomi A1 rooted it works on the wife's phone xiaomi note 5 pro rooted it used to work fine but for some reason it has suddenly detected root and won't work now. I have checked all the settings to do with hiding are still selected as before, strange thing is it has worked briefly for a few seconds but then stopped again.
Please can people tell me if they have had this happen and how they fixed it please.
What checks is it doing to detect root does anyone know?
Thanks
hycraig said:
On my phone xiaomi A1 rooted it works on the wife's phone xiaomi note 5 pro rooted it used to work fine but for some reason it has suddenly detected root and won't work now. I have checked all the settings to do with hiding are still selected as before, strange thing is it has worked briefly for a few seconds but then stopped again.
Please can people tell me if they have had this happen and how they fixed it please.
What checks is it doing to detect root does anyone know?
Thanks
Click to expand...
Click to collapse
Try updating magisk.
Try to disable xposed modules.
Try to disable all modules.
See if it works now.
Then one by one reenable them.
Sent from my SM-G985F using Tapatalk
vash_h said:
Try updating magisk.
Try to disable xposed modules.
Try to disable all modules.
See if it works now.
Then one by one reenable them.
Sent from my SM-G985F using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.
hycraig said:
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.
Click to expand...
Click to collapse
Credits Google
Now safetynet fails after March update
You need to change device props to pixel or lock bootloader
hycraig said:
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.
Click to expand...
Click to collapse
Biggest_Noob said:
Credits Google
Now safetynet fails after March update
You need to change device props to pixel or lock bootloader
Click to expand...
Click to collapse
My safteynet passes fine on both my devices
Thanks
somehow they manage to detect root even if magisk manager is running under custom package name and magisk hide is enabled.
Last version that is still running is 13.1.1 (apk available on apkmirror).
h4lli said:
somehow they manage to detect root even if magisk manager is running under custom package name and magisk hide is enabled.
Last version that is still running is 13.1.1 (apk available on apkmirror).
Click to expand...
Click to collapse
thanks @h4lli i couldn't see sky go version 13.1.1 for uk
so i got Sky Go UK 12.4.14 from apkmirror and can confirm is working fine
yeah still doesnt work, latest sky go app 20, latest magisk, still detects, anyone able to reverse the sky app to see what methods its using?
Fyi - any version other than the latest (20.6.1) at the moment forces an upgrade to 20.6.1, which then detects root.
Safety net is passing both basic and cts with Eval type basic. I'm on latest canary (20425).
I've tried :-
Uninstalling all apps that skygo could look for (titanium, openvpn etc.)
Using a work profile (shelter and island)
Disabling oem unlocking
Disabling usb/adb debugging
Disabling developer options
Deleting all files and folders that have magisk, twrp or titanium in them.
Basically everything here https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
So, I think it's basically no go for sky go at the moment. Happy to be corrected if someone has it working.
Beardy
beardymarrow said:
Fyi - any version other than the latest (20.6.1) at the moment forces an upgrade to 20.6.1, which then detects root.
Safety net is passing both basic and cts with Eval type basic. I'm on latest canary (20425).
I've tried :-
Uninstalling all apps that skygo could look for (titanium, openvpn etc.)
Using a work profile (shelter and island)
Disabling oem unlocking
Disabling usb/adb debugging
Disabling developer options
Deleting all files and folders that have magisk, twrp or titanium in them.
Basically everything here https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
So, I think it's basically no go for sky go at the moment. Happy to be corrected if someone has it working.
Beardy
Click to expand...
Click to collapse
Yeah still can't get it working. Damn it.
Hast everyone a sollution for running the sky Go App on rooted phones?
Skygo doesnt Work... hast anyone a sollution?
eula1977 said:
Skygo doesnt Work... hast anyone a sollution?
Click to expand...
Click to collapse
Have you tried this? It worked for me
SkyGo app detected root!
Hi everyone i have a problema using SkyGo app on my device because It detects the root. I renamed magisk , used magisk Hide , tried magiskhide props config , tried to delete cache and re-install SkyGo app but nothing worked...any solution...
forum.xda-developers.com