Bank app Error Magisk 26.1 - Magisk

Hello, I hope you can help me with this.
Yesterday I updated to the latest version of the custom rom I'm using (EvolutionX) and I had to flash the zip file manually through recovery since it didn't install automatically.
After that, magisk stopped working correctly, the root of my banking applications is not hidden, as you can see in the images, I have everything hidden and activated correctly (I think), I would appreciate it if you help me with this since the same thing happened to me a long time ago , and not finding a solution I had to do a hard reset and install a new rom.
The bank app says: "this device does not meet the minimum security requirements for this application"
(Sorry for my english, helpe pls)

alesky0903 said:
Hello, I hope you can help me with this.
Yesterday I updated to the latest version of the custom rom I'm using (EvolutionX) and I had to flash the zip file manually through recovery since it didn't install automatically.
After that, magisk stopped working correctly, the root of my banking applications is not hidden, as you can see in the images, I have everything hidden and activated correctly (I think), I would appreciate it if you help me with this since the same thing happened to me a long time ago , and not finding a solution I had to do a hard reset and install a new rom.
The bank app says: "this device does not meet the minimum security requirements for this application"
(Sorry for my english, helpe pls)
Click to expand...
Click to collapse
Hi, try updating the safety net fix module and also try this

Try Universal SafetyNet Fix 2.4.0 Mod by Displex

remove that old module and install te new one 2.4.0 mod

Related

[Q] Magisk v16 Problems T715

Hi all, i'm using a stock rom, rooted with magisk and debloated (manually). I always faced this problem, the 90% of the modules i try to install ends with something like that:
See Screen below
However i've never asked help because i tought it was a Magisk problem resolvible with an update...but every update ended always in the same way for me when trying to install some modules. I've also attached some logs here of when i tried to update xposed systemless if someone could help me it will be really apprecciated!
P.s Anyone facing the same problem? I've read somewhere that a similar problem is common with Motorola devices but idk if this is the case
Giuskiller said:
Hi all, i'm using a stock rom, rooted with magisk and debloated (manually). I always faced this problem, the 90% of the modules i try to install ends with something like that:
See Screen below
However i've never asked help because i tought it was a Magisk problem resolvible with an update...but every update ended always in the same way for me when trying to install some modules. I've also attached some logs here of when i tried to update xposed systemless if someone could help me it will be really apprecciated!
P.s Anyone facing the same problem? I've read somewhere that a similar problem is common with Motorola devices but idk if this is the case
Click to expand...
Click to collapse
Is this via Magisk manager?
ashyx said:
Is this via Magisk manager?
Click to expand...
Click to collapse
Yes this is via Magisk Manager, however the same error (could not mount something) appears also when i try to install a module via twrp. The "best" thing is that some module just works both way (Busybox NDK for example) while other fails both ways. No module work in a way and doesn't work in another. So basically if a module work in magisk can be installed also via twrp otherwise it cannot be installed, no matter what i try
I have the same problem. Trying to install viper4a.
I have no clue how to fix it
Giuskiller said:
Yes this is via Magisk Manager, however the same error (could not mount something) appears also when i try to install a module via twrp. The "best" thing is that some module just works both way (Busybox NDK for example) while other fails both ways. No module work in a way and doesn't work in another. So basically if a module work in magisk can be installed also via twrp otherwise it cannot be installed, no matter what i try
Click to expand...
Click to collapse
I think this is a bug in Magisk with the way some modules attempt to install and mount, which is why some work.
I'm surprised though that they don't install in TWRP. Is your device encrypted, can you mount /data in recovery?
ashyx said:
I think this is a bug in Magisk with the way some modules attempt to install and mount, which is why some work.
I'm surprised though that they don't install in TWRP. Is your device encrypted, can you mount /data in recovery?
Click to expand...
Click to collapse
Actually i'm at university, but when i come back home i will try and let you know. What i can say for now is that every zip i've flashed so far worked just flawlessy (well, apart magisk's ones)
Downloaded atmos dolby only module for nougat....rebooted snd stucked on samsung logo. Ohhhh.... How to get rid of this module, is anyway to do it?
Please help
Edit:
installed module uninstaller and followed it - > https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
working now.
Looking for info how to install viper4Android....
netgar said:
Downloaded atmos dolby only module for nougat....rebooted snd stucked on samsung logo. Ohhhh.... How to get rid of this module, is anyway to do it?
Please help
Edit:
installed module uninstaller and followed it - > https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
working now.
Looking for info how to install viper4Android....
Click to expand...
Click to collapse
Well as far as i know, if you're on stock rom you won't be able to install audio mods because they're in conflict with something in the Rom. You should use a custom rom instead. However not sure 100% about this, maybe some audio mods can work, but you should ask someone else, i'm not so informed

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.

Magisk Modules not working

Hi everyone,
I am pretty new to rooting, flashing, modding etc.
My problem is as follows:
I am on Pie 10.0.1.0PDIMIFJ, upgraded to it thanks to a guide in this forum.
After upgrading (bootloader has been unlocked beforehand of course) I got root through patched boot.img and Magisk Manager.
I did this in order to be able to gain some everyday treats such as Youtube background playing and especially V4A.
I could install these modules via Magisk, but they do not seem to work.
V4A is asking for driver installation everytime I reboot my phone, and I have to reboot after every driver installation.
This happens independently from the version of Viper I am trying to install.
After installing Youtube Vanced nothing changes. Playing stops when closing the app while a video is turned on.
I also tried a couple of other modules but none seems to be working.
I read somewhere that this could be connected to "SELinux permissive" something . I am sorry, I do not really know what that's about but maybe someone out there could give me a hint as to where I have to look.
I do not need a guide or anything, don't mind learning something on the way
Help would be greatly appreciated.
Thank you guys in advance
Anyone?
Same/similar issue
I am also experiencing the same issue, was able to install Viper and pixel Camera mod, then after no matter what module I install it does not show up in the app drawer atleast, I tried App systemizer , Cloudfare DNS and SF font.. nothing seems to work than the first installed two modules. Tried to install and remove them multiple times.
Cleared magisk cache
installed M<agisk from TWRP multiple times.
tried to install modules from TWRP as well.
I am so new to all these, please dont mind any mistakes.
Thanks.
The same problem I got.How to do to enable camera 2api.

help for rooted note 8

Hi guys. I need some help for my rooted galaxy note 8. I had rooted my phone a long ago and all was working good. All apps including banking apps were working fine with magisk hide. But few days ago i wanted to update my phone so i flashed stock rom with odin and updated my device. Earlier my bootloader version was 6 and now its updated to version 8. Then after updating i flashed latest twrp and rooted with magisk. I flashed magisk version 20.1 and magisk manager version was 7.4.0 . Then magisk update was available so i updated to magisk version 20.2 and magisk manager to version 7.5.0 . Now the problem starts. I am facing 3 issues.
1- my phone starts freezing and then reboots randomly. It happens quite frequently atleast 2-3 times in a day. Every time i clear cache partition from twrp but problem persists. I had checked ram also but ram useage is also fine. Please help me with this issue.
2- while searching for the solution of above problem i read somewhere that it might be because of safety net check. Earlier safetynet check was pass but now safety net check was fail. I flashed bypass safety net mod. But when my phone reboot a warning appears that your device has some internal problem. Contact the manufacturer. I pressed ok and phone starts. It seems to work normal but then i realised my device was not connecting to any wifi network. When i click on available wifi nothing happened. So i uninstalled the safety net bypass mod and then wifi start working again.
3- now final thing i want to know. If the above problem did not solve then i have to unroot my phone which i dont want. But if i had to then i dont want to flash stock rom. I want to unroot from magisk app itself. I had edited build.prop file for using samsung health app. So now if i unroot from magisk app will the changes made by me in build.prop file remain or it will revert back. Also will banking apps work or not....
I know its very lengthy post but please help
Wow...
70 views no comment..... it seems all the developers and tech people are enjoying winter break
Try going back to previous version of Magisk. I have Snapdragon N8 so I have supersu. But I did update my A20g with newest Magisk and had an issue. I know you have N8 but was just saying maybe could be new Magisk.
My SM-N950U Still Rooted Note 8

Payconiq By Bancontact APP and Magisk Hide

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

Categories

Resources