Database Develop

Problems after rooting, Help!

2 days ago i rooted my G800F with CF-auto-root through ODIN. (Used the latest CF-auto-root from here , with ODIN v3.10.6)
But after that my device is too laggy!
Much slower as it had 512 RAM. Root success was confirmed with Root Checker
SuperSU was also installed but sometimes i get a message that SU binary isn't installed.
I 've tried with "ROM toolbox" and "System App Remover" to unistall some system apps but i got the message "Failed to Unistall xxxxxxx app". But if i entered again "ROM toolbox" i found out that the xxxxxx app wasn't there. It has been unistalled!
Once Play Store didn't let me upgrade some apps, because it said that i must logged in to my account (which i was already logged in), and others problems like that!
What shall i do now?
Root again the device? Unroot the device and root again? Unistall Knox? (i've read somewhere that Knox is responsible for problems after rooting). Find another version for CF- auto-root? (the latest is for Build ID LMY47X.G800FXXU1BPB2 but mine is LMY47X.G800FXXU1BPC4 if it matters)
Please help!

Yes, if you have root you must disable Knox. If it doesn't help, you can try go back to stock to see if it's a hardware issue (it will still lag), then root again if everything is fine for a day or two...

lfom said:
Yes, if you have root you must disable Knox. If it doesn't help, you can try go back to stock to see if it's a hardware issue (it will still lag), then root again if everything is fine for a day or two...
Click to expand...
Click to collapse
I have this device for about 2 years. These problems have begun just after rooting. So, i believe it is not a hardware problem.
By saying disable Knox you mean delete/unistall or freeze?
And how can i do that?

billphone said:
I have this device for about 2 years. These problems have begun just after rooting. So, i believe it is not a hardware problem.
By saying disable Knox you mean delete/unistall or freeze?
And how can i do that?
Click to expand...
Click to collapse
I would first use Link2SD to freeze all related to Knox and Security log first. If everything went right, backup and delete files.

lfom said:
I would first use Link2SD to freeze all related to Knox and Security log first. If everything went right, backup and delete files.
Click to expand...
Click to collapse
I freezed all apps and having the word Knox in their names. The phone isn't so laggy now but if i open some apps for rooted devices such as Busybox or Rom Toolbox they can't operate and got a message that my device isn't rooted. After that, no others apps for rooted devices are working! The SU doesn't open at all! All will work again after restart (except ofcourse Busy box Rom toolbox)
So what shall i do?
Unroot and root again? Root again over the previous root? What else?

billphone said:
I freezed all apps and having the word Knox in their names. The phone isn't so laggy now but if i open some apps for rooted devices such as Busybox or Rom Toolbox they can't operate and got a message that my device isn't rooted. After that, no others apps for rooted devices are working! The SU doesn't open at all! All will work again after restart (except ofcourse Busy box Rom toolbox)
So what shall i do?
Unroot and root again? Root again over the previous root? What else?
Click to expand...
Click to collapse
I thought that CF-Auto-Root disabled Knox protection when used, but maybe not... I think there is an option in SuperSU to disable it, you must use it as soon as you open it after using CF-Auto-Root and booting again to Android. If it doesn't have this option, it's not only Knox that makes the security system that prevents root, there is SecurityLog too (and on MM I think I've seen Rootpd that probably is a root protection daemon). Probably it removed su when you were disabling Knox. If you can root again over the current state, probably you can try disabling security system completely this time. Check other threads about rooting G800F, probably there is a list of apps you must disable.

lfom said:
I thought that CF-Auto-Root disabled Knox protection when used, but maybe not... I think there is an option in SuperSU to disable it, you must use it as soon as you open it after using CF-Auto-Root and booting again to Android. If it doesn't have this option, it's not only Knox that makes the security system that prevents root, there is SecurityLog too (and on MM I think I've seen Rootpd that probably is a root protection daemon). Probably it removed su when you were disabling Knox. If you can root again over the current state, probably you can try disabling security system completely this time. Check other threads about rooting G800F, probably there is a list of apps you must disable.
Click to expand...
Click to collapse
Thanks for your anwser.
The SU isn't permanently removed but only temporarily, because after restart it is working again
I 'll try to unroot and root again and we 'll see what happens

billphone said:
Thanks for your anwser.
The SU isn't permanently removed but only temporarily, because after restart it is working again
I 'll try to unroot and root again and we 'll see what happens
Click to expand...
Click to collapse
SuperSU is the app, su is the superuser daemon. Good luck.

billphone said:
Thanks for your anwser.
The SU isn't permanently removed but only temporarily, because after restart it is working again
I 'll try to unroot and root again and we 'll see what happens
Click to expand...
Click to collapse
So finally the problems are still here. The device is no longer laggy, but the root sometimes works sometimes doesn't.
I root again over the previous root, again the same. I unroot and again root, the same. I install a custom recovery and flash the SuperSU, the same results.
Initially working fine, giving rights to the applications but later sometime does not. With restart reverts briefly again.
What on earth has gone wrong? I have root many devices and all of them were working perfect!
I would like to avoid factory reset because i don't know how to restore my backup without problems.
Is there another solution?

Knox disables root, it can even revert custom recovery. Did you disable it, as well as Security Log (disable its updates in settings first), as suggested previously?

lfom said:
Knox disables root, it can even revert custom recovery. Did you disable it, as well as Security Log (disable its updates in settings first), as suggested previously?
Click to expand...
Click to collapse
Yes, i disable some apps with the word Knox in them. I don't know if is still a Knox app with a different name. Is there a list with Knox apps?
I didn't disable the Security Log neither its updates. Where can i find them?

So, finally i have a rooted device which randomly unroot itself!
And nothing can be done!

Samsung Pay and Magisk

Has anyone gotten Samsung Pay to work with Magisk? I've got it installed as a gear plugin and safetynet passes. However, somehow Samsung Pay still detects root, even though it's hidden in magisk hide.

Same. Then this droidx program protecting pay app
Sent from my SM-N910V using XDA-Developers Legacy app

Try the universal safteynet net module

Is your Knox tripped? Samsung Pay might check that independently of the root-status of your phone.

grymkmb said:
Is your Knox tripped? Samsung Pay might check that independently of the root-status of your phone.
Click to expand...
Click to collapse
I'm on an LG

I've got the same issue with galaxy tab 3
I got warranty bit warning was showing on the boot screen, so I'm pretty sure I triggered Knox. The reason I was using magisk was to prevent this issue, but I guess Google figured out how to detect its presence. I downloaded a fresh copy of the firmware, which will cause Knox to reset but it also factory resets the tablet. I will still use magisk on my new s8+ phone. I hope magisk will work more effectively to where I can use exposed and its modules. After jellybean, magisk wasn't able to allow exposed to be used because of the way Android sets up its environment to execute apps. Hopefully soon a work around will be accomplished especially since Oreo is coming to my two devices by the end of the year, I guess if not sooner.

Same problem here; Magisk works but Samsung pay won't work

Even tried freezing magisk. Though still no go must be detecting something.

hkbladelawhk said:
Has anyone gotten Samsung Pay to work with Magisk? I've got it installed as a gear plugin and safetynet passes. However, somehow Samsung Pay still detects root, even though it's hidden in magisk hide.
Click to expand...
Click to collapse
I tried the same thing but couldn't make it work. I think it is due to the fact that the "System Status" is custom (or modified) since magisk modifies the "boot" partition, and that you probably installed a custom recovery to install magisk. That's why OTA also don't work without first flashing back the original boot and recovery images. I don't have an LG to verify that the "System Status" appears on those.
If it does, what could be tried is to install xposed and a module that fakes the system status (if you've got marshmallow or before)
sevenday4 said:
I got warranty bit warning was showing on the boot screen, so I'm pretty sure I triggered Knox. The reason I was using magisk was to prevent this issue, but I guess Google figured out how to detect its presence. I downloaded a fresh copy of the firmware, which will cause Knox to reset but it also factory resets the tablet. I will still use magisk on my new s8+ phone. I hope magisk will work more effectively to where I can use exposed and its modules. After jellybean, magisk wasn't able to allow exposed to be used because of the way Android sets up its environment to execute apps. Hopefully soon a work around will be accomplished especially since Oreo is coming to my two devices by the end of the year, I guess if not sooner.
Click to expand...
Click to collapse
Sorry, once knox is tripped there is no going back. However, installing Magisk fools the phone into thinking knox is still untriggerred (0x0). By reflashing the original firmware, what you did is restore the "boot" partition that was modified by magisk. By doing that, your phone should get back its "official status", allowing OTA. However, Knox will stay tripped. Anyway, Knox does little... and is only used by samsung softwares.

There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.

Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
Booo!

someone please made an apps that can hide or fake the Knox status.

Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
This is possible by disabling safetynet check at boot level before compiling the kernel

Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
Does this apply for non-Samsung phones? I understand that Knox has a tripped flag, but on a non-Samsung phone, what exactly is "tripped"? As with everyone else, I'm pretty frustrated that I still can't use Samsung pay, even on a phone that passes safety checks and has MagiskHide.

gghose said:
Does this apply for non-Samsung phones? I understand that Knox has a tripped flag, but on a non-Samsung phone, what exactly is "tripped"? As with everyone else, I'm pretty frustrated that I still can't use Samsung pay, even on a phone that passes safety checks and has MagiskHide.
Click to expand...
Click to collapse
Works for me on a Samsung phone, after hide I just had to rename all busybox exe's.

Doesn't work for me on a OnePlus 3T, OOS 4.1.7, rooted with Magisk 14.0. This stopped working after the Samsung Pay (Gear version) was updated right around August 21st. Maybe I'm just missing one or more binaries or apps that still must be hidden. I don't have any busybox apps installed, though I previously did, and I removed the busybox binaries where I knew to find them. Maybe it's detecting Magisk's su install, or some other binary I still need to remove. SafetyNet passes just fine, and I can use AndroidPay and CapitalOneWallet on the phone, but I can't use the SPay tab in the Gear app without getting the "rooted phone" message.

Magisk hide 14
Hi Yeti47: I have a samsung galaxy s8 sm-g950f. It is rooted wit renovate ice and magisk 14. What modules I have to check in magisk hide to make samsung pay working? Please answer me in [email protected]. Thank you so much. Bye.

Finally solved it. Busybox can be installed in /data/local, apart from /system/xbin or /system/bin. Samsung Pay will find it there. After I removed it, I was able to get Samsung Pay (Gear Version) working again on my OnePlus 3T.

Spot on fella, just got it working on OP5 with lineage ROM.

dcbii said:
Finally solved it. Busybox can be installed in /data/local, apart from /system/xbin or /system/bin. Samsung Pay will find it there. After I removed it, I was able to get Samsung Pay (Gear Version) working again on my OnePlus 3T.
Click to expand...
Click to collapse
Root explorer won't let me remove it from xbin. How exactly did you do it?
Sent from my iPad using Tapatalk

Apps refuse to start because phone being rooted but it isn't!

At least 2 of my Apps refuse to start. One is my banking app and they do not offer any other way of interaction.
The problem is that the phone in fact is not rooted! It's just "OEM unlocked" to be prepared for root (which I need for E.g. titanium backup, but only maybe once a month).
Please give me a way out of this vicious circle!
I cannot remove the OEM unlock because it requires full wipe every time. Or is there a way?
Or what can I possibly tell the App Provider to improved their Code so that Oneplus phone state is being recognized (more) correctly?
Any help would be greatly appreciated.

Use Magisk I guess? Use it to hide root from that app.

Reeb_Lam said:
Use Magisk I guess? Use it to hide root from that app.
Click to expand...
Click to collapse
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?

ako673de said:
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
Click to expand...
Click to collapse
You need to do some reading about Safetynet. If you're OEM unlocked you fail Verified Boot checks. Most custom Kernels include a bypass for this. Magisk alone should also work. I think you missed one important step:
Open Play Store Settings. Scroll down. It says 'Uncertified' at the bottom, right? Now install and set up Magisk. Go to system App Settings and clear Data and Cache for Play Store. Return to the Play Store Settings and scroll down. Now it should say 'Certified'. It might not be immediate, but it will happen. Now your Banking Apps work.
If you don't want, or have no luck with Magisk, simply flash a Custom Kernel that bypasses Verified Boot, and works with OOS.
Simple.

Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?

ako673de said:
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
Click to expand...
Click to collapse
Link to other Thread?
I don't know Magisk but are you hiding Root from your Banking App? Have you cleared Data and Cache for the Banking App since getting Certified?

First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?

ako673de said:
Any other idea?
Click to expand...
Click to collapse
Nope. If Play Store says Certified you should be good to go. I can only imagine it's a Magisk issue. Post screenshots of your config and let the Magisk experts pick through them. Maybe there's something not set up correctly.

ako673de said:
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
Click to expand...
Click to collapse
Hide Magisk Manager. I had to do that to get my banking app to work.
Edit: you may need to reboot after hiding Magisk Manager and clear you banking app's data before it works.
Sent from my OnePlus3T using XDA Labs

Thank you, indeed that WORKED! Well, at least for 2 out of 3 Apps. I think I can tell which one: "HVB banking". Maybe could somebody cross-check this one on his/her phone?

After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?

ako673de said:
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
Click to expand...
Click to collapse
Did you reflash custom kernel after update?

I'm not using any. What I did right after the update is to disable dm-verity (with a patched boot.img), like I did last time. But magisk is not yet re-installed because I wanted to see at least once the HypoVereinsbank App working, which it in fact does (different to last time when the phone was not rooted as well, and the store not certified!).

ako673de said:
But magisk is not yet re-installed
Click to expand...
Click to collapse
That's why... You can't pass the ctsProfile check if your bootloader is unlocked, and if you can't pass the ctsProfile check the Play Store won't be certified. You need Magisk for that...

Now I'm getting confused. The initial mail of this thread explains the situation as it was when I opened this thread:
--> Original ROM, no root, and banking apps didn't work <--
The advice to clear data of the PlayStore immediately brought the PlayStore back to "certified".
This is clearly in contrast to what you're saying now.
I can imagine only one reason: Maybe the older PlayStore had a bug and therefore was able to "certify" even with unlocked bootloader?
Sidenote: My main intention to do the firmware upgrade was that the "safety net checks" in Magisk suddenly stopped working one day (with the error message "invalid response", most probably you know what I'm talking about, I've read some comments from you on this issue). Therefore it's maybe really not too unlikely that Google has changed something very basic. Could you please confirm?
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).

ako673de said:
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid

Sorry, now comes a probably often asked question: do I need the safetynet check option in magisk for something real? Or do the alternative apps fulfill all possible needs? What are these needs? Isn't that exactly what the PlayStore does to determine "certified"?

After quite some months of absolutely no "root" problems with any of my apps, since today o2banking again doesn't work.
I tried to update Magisk, but after update of the Magisk manager app to v7.1.1(203) it reports that Magisk is not installed at all, and any update of Magisk itself resulted in just the same. So I reverted back to v6.1.0(165) and everything seems to be okay, except that o2banking doesn't work. SafetyNet is clean, Magisk is hidden for o2banking and Magisk manager is repacked.
Does anybody know what the problem might be? Especially with that new version of the manager app, but also with Magisk v19.0 which cannot be installed from v6.1.0 (max. is v18.1). Any ideas welcome! I'm now on OOS 5.0.8 by the way.
SOLVED it myself: As mentioned somewhere in the update FAQ of Magisk there was a bug in manager v6.1.0 that causes the updated v7.1.1 to co-exist with the old version if the old version has been re-packed. If anybody encounters the same problem, the solution is at the bottom of this page: https://www.didgeridoohan.com/magisk/ManagerIssues.
o2banking will then still not work. Update to v19.0 is mandatory. But that is no problem then any more...

probably your banking app identified oxygen os as custom rom and have root. 1 out of 3 banking app in my phone doesn't work with lineageos even though i already hide magisk, but when running oxygen os with magisk hide, and also hide magisk manager (turn it on in magisk manager setting) all 3 banking app work just fine. maybe try sending a message to bank app developer to add oxygen os as exception.

Did you notice my edit? It was a problem with magisk manager update and magisk main version. Now everything is back up and running.

Kernal or ROM that hides KNOX Trip?

Hello,
I rooted and installed a custom ROM on my Note 9 a couple of months ago and yesterday I was getting annoyed not being able to use apps like Android Pay, Samsung Pay and Banking apps, So I decided to use Odin to flash the stock ROM back and set OEM Unlock to OFF. To my Horror, I found out the hard way about what a KNOX Trip was. I have no idea how I missed all the warnings on every ROM post about tripping it and not being able to change it back. I can now use my Banking apps, Android Pay and play Fortnite however, Because of the Knox being tripped I can no longer use Samsung Health and Samsung Pay
My Question is is there a way to just install a custom kernel or ROM that tricks apps like Samsung Pay and Samsung Health into working again without installing root and having modifications hidden so I can use my Banking apps and play games??
Any Help is very much appreciated!

After a bit more searching the forums and Google I now understand that no matter what I do I can't get Samsung pay to work which is fine. However any help on the rest is still appreciated! ?

You should go read some more as you also missed the part where tou can use magisk hide. but it wont get back spay.
Just use the forum sarch feature as if you were google searching ie:
magisk shealth
magisk hide
magisk google pay
magisk android pay
magisk insert what ever query

bober10113 said:
You should go read some more as you also missed the part where tou can use magisk hide. but it wont get back spay.
Just use the forum sarch feature as if you were google searching ie:
magisk shealth
magisk hide
magisk google pay
magisk android pay
magisk insert what ever query
Click to expand...
Click to collapse
I did use Magisk Hide to hide root from apps but some apps could still detect the custom rom was installed.

VortexHD said:
I did use Magisk Hide to hide root from apps but some apps could still detect the custom rom was installed.
Click to expand...
Click to collapse
so for example you went to magisk hide menu and selected your banking app and it didnt work?

bober10113 said:
so for example you went to magisk hide menu and selected your banking app and it didnt work?
Click to expand...
Click to collapse
Yes i selected my banking app along with google pay and all its services and Samsung pay with its services and none of them worked.
This also doesn't work for pokemon go and fortnite.

VortexHD said:
Yes i selected my banking app along with google pay and all its services and Samsung pay with its services and none of them worked.
This also doesn't work for pokemon go and fortnite.
Click to expand...
Click to collapse
how about safety net status, is it passing?

bober10113 said:
how about safety net status, is it passing?
Click to expand...
Click to collapse
Yes Everytime. I'm about to flash TWRP and only install a custom kernal with no root.

VortexHD said:
Yes Everytime. I'm about to flash TWRP and only install a custom kernal with no root.
Click to expand...
Click to collapse
try endurance. but besure ure rom base matches kernel ramdisk or u won't be able to get past lock screen. so do a full twrp backup in case
or just try dr ketan. usualy best all round working rom.

bober10113 said:
try endurance. but besure ure rom base matches kernel ramdisk or u won't be able to get past lock screen. so do a full twrp backup in case
or just try dr ketan. usualy best all round working rom.
Click to expand...
Click to collapse
I have installed a custom rom without root access and my banking app and games work perfectly however Google pay is detecting the unlocked bootloader. Anyway to hide this with out rooting the phone?

VortexHD said:
I have installed a custom rom without root access and my banking app and games work perfectly however Google pay is detecting the unlocked bootloader. Anyway to hide this with out rooting the phone?
Click to expand...
Click to collapse
for google pay, some actualy revert to an older version. just search the forums. for me magisk hide works great with my banking app. and for games, im not much of a gamer so i realy dknt know. but again you should try with dr. ketan rom just in case it works. just choose to flash kernel and magisk during setup.( do a clean install so factory wipe in twrp before flashing his rom)

Well i decided to just use Stock Rom and lock the bootloader so at least most of my apps then work. I installed a modified apk of Samsung Health but it doesn't contain the heart rate monitor but I suppose that's fine and I just have to accept that Samsung Pay will never work again

Where can i get the old version of Google pay which works with unlocked bootloader?
Sent from my SM-N960F using Tapatalk

S heath can work on a rooted device with a simple change to the build prop , but secure folder and spay remain a dud

Bank app detecting root or modified system

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