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.
Related
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
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
Hi everyone,
I'm just hitting my head against the wall with this applciation...
I'm running OP6 with evolution X 4.5.
This app refuses to let me uses it saying that "There's an error, Check if usb debugging is activated. Check if you're rooted or if a custom rom is installed"
I've tried magisk hide, also hidding some google services, usb debugging isn't activated,...
It's the only app I knoiw so far that can detect root on my phone.
Can anyone help me find a workaround please?
thanks.
Same here...
I am using MicroG without Safetynet support and I think that is the issue, unfortunately.
Payconiq by bancontact / rooted device
Hello
I have the same problem with OP6 rooted ... magisk hide activated but when run the payconiq Bancontact app " There is an error " not possible to run the app.
Anybody for a solution ?
veronesi.n said:
Hi everyone,
I'm just hitting my head against the wall with this applciation...
I'm running OP6 with evolution X 4.5.
This app refuses to let me uses it saying that "There's an error, Check if usb debugging is activated. Check if you're rooted or if a custom rom is installed"
I've tried magisk hide, also hidding some google services, usb debugging isn't activated,...
It's the only app I knoiw so far that can detect root on my phone.
Can anyone help me find a workaround please?
thanks.
Click to expand...
Click to collapse
I used to use an old apk of the app but now it doesn't let me use it and forces me to upgrade to last version.
My wife's app is working well but she has a lg g7 thinq unrooted.
So if someone can help, it would be very much appreciated as every other app is working well, safety net is passed, and this app is my only way to pay contactless because my banking app doesn't have a payement option in it.
I'm using it without issues. I hide it and just turn off USB debugging when I'm using it.
Just to make sure, did you just enable Magisk Hide in the options and nothing else?
Or did you also - after enabling - go into the Magisk Hide option that now appeared in the menu and placed a checkmark after all programs for which you want to hide Magisk from, in this case Payconiq ?
Clear Payconiq cache and data, reboot and setup Payconiq.
I have the same problem.
Magic hide is enabled. USB debugging is disabled.
In the Magic hide menu, the Payconiq app has a checkmark. All my other banking apps work fine.
Phone = Samsung J7 (2016)
Does someone have a solution?
Thanks
What's your problem with this app Can't you run it Can someone show what message is showing For me, this application is not available in my country, so I downloaded it from outside. I have Magisk 21000 root and Magisk manager 8.0.2 (307) (11) and it works for me and nothing is screaming about root etc :highfive:
It is the "Payconiq by Bancontact" app.
It worked on my phone without root. Since my phone is rooted, it doesn't work any more.
My phone is rooted with Magisk 20.4 (20400) and Manager 8.0.2 (307)
When I use the app: I receive this message. I hope this can help...
Date: 12 Oct 2020 15:23:47 GMT+02:00
Device: samsung SM-J710F
App version: 5.5.3
OS version: 8.1.0
App token: /
Failure code: ERROR_SDK_INTEGRITY (81)
Hello,
Problem solved.
Thanks to Spartacus500 .
I ’ve seen there is an other version of Magisk. I didn’t even know there was an update. :silly:
I did the following thinks:
In Magisk Hide menu, uncheck Payconiq app.
Stopped Payconiq app and Cleared data.
In Magisk Hide, place checkmark at payconiq app.
Installed Magisk 21.0 (21000) Beta.
Reboot.
Run Payconiq app, and it works fine
Hope it stay this way :fingers-crossed:
Veke123 said:
Hello,
Problem solved.
Thanks to Spartacus500 .
I ’ve seen there is an other version of Magisk. I didn’t even know there was an update. :silly:
I did the following thinks:
In Magisk Hide menu, uncheck Payconiq app.
Stopped Payconiq app and Cleared data.
In Magisk Hide, place checkmark at payconiq app.
Installed Magisk 21.0 (21000) Beta.
Reboot.
Run Payconiq app, and it works fine
Hope it stay this way :fingers-crossed:
Click to expand...
Click to collapse
Which version of the app did you use?
Is it 5.5.3?
Can you share the apk?
I tried 5.8.3, 5.5.3 and 5.3.3 but there are all stuck at the start.
I am passing all checks on rootbeerfresh (root checker).
flotheking said:
Which version of the app did you use?
Is it 5.5.3?
Can you share the apk?
I tried 5.8.3, 5.5.3 and 5.3.3 but there are all stuck at the start.
I am passing all checks on rootbeerfresh (root checker).
Click to expand...
Click to collapse
I use the "Payconiq By Bancontact" app. I don't know which version it was that worked before, but after an update I can not run it anymore on a rooted phone.
I will send you the apk of the "Payconiq by Bancontact" app. Hope you can find a solution.
I tried the other app (Payconiq) version 4.3.5.3 (latest) and it seems to be working.
flotheking said:
I tried the other app (Payconiq) version 4.3.5.3 (latest) and it seems to be working.
Click to expand...
Click to collapse
sorry for bumping an old thread but what are you using now?
In my case I'm still using the old Payconiq and I don't know what I'm going to do when it gets finally phased out.
Well, I'll just pay in another way I guess.
seeschloss said:
In my case I'm still using the old Payconiq and I don't know what I'm going to do when it gets finally phased out.
Well, I'll just pay in another way I guess.
Click to expand...
Click to collapse
thx for responding, what version are you using?
5.14.1 Payconiq app works for me Magisk hide root
Spartacus500 said:
5.14.1 Payconiq app works for me Magisk hide root
Click to expand...
Click to collapse
sadly not working for me, when i hide app in magisk, launching gets aborted without error message
got it working again
latest magisk, latest riru, lsposed, gravitybox all installed without issues to payconiq
payconiq app hidden in magisk, magisk manager isn't hidden
the thing that got it working again was disabling magisk module G-visual mod, same for magisk module fullscreen immersive gestures. Apparently payconiq app doesn't like keyboard spacing to be changed ????
i'm quite happy that i found it, but if anyone could explain i'd very gratefull
Hello,
Can I also ask a question, please? How can payconiq detect that someone is using a custom-rom? I also get a message that I am using a Custom-rom and that it is not possible to install. However, I have not installed MAGISK and my phone is not rooted.
Thanks
Andi
Bergfex2 said:
Hello,
Can I also ask a question, please? How can payconiq detect that someone is using a custom-rom? I also get a message that I am using a Custom-rom and that it is not possible to install. However, I have not installed MAGISK and my phone is not rooted.
Thanks
Andi
Click to expand...
Click to collapse
Could be detecting your unlocked bootloader, various prop values, etc. For a list of props that are common detectors, and that MagiskHide changes (which of course is removed in the next stable release) you can check here:
https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf#setreset-magiskhide-sensitive-props