I have kenzo cyanogen ROM installed (13.0-20160617 unofficial kenzo) I have used Lloyds banking app for a long time but tonight it tells me I can't log in as using a rooted or jail broken device. I haven't updated the app for a while or ran any other updates.
Is this room rooted by default? As I didn't think it was and I didn't think I had root.
Is there a way to fix it so I can use my banking app again?
It has a root option which you can enable. I can suggest trying root cloak but that also means you'll have to install xposed. Make sure root is turned off in dev settings and clear the cache/data of the banking app before trying root cloak. Otherwise you may have to settle for their website.
Root is off in the developer options. I wonder if the banking app can see the ROM or something else is not stock? Its frustrating as it was the reason I didn't root my phonephone/want it rooted.
I noticed that even installing an older version of the app I get same error so maybe something else has changed . if a system app has somehow updated and caused this? I am still on the original ROM from june. I haven't installed nightlies.
Either that or my account has somehow been flagged so even old app versions dont work(deleted data and folders etc from the app first.)
regarding ths problem - Im guessing its not looking at root as this is disabled, but it can see either an unsupported rom, or something else. Can i flash a different rom (prefereably not Miui) and regain the banking app? a rom that would be classes as supported?
I am unable to run apps like "tez" , "bhim" on pixel experience rom installed in redmi note 3. Apps say that my phone is rooted but its not. I confirmed it by installing"root checker" app. My device is not rooted. is there any solution for this problem? is it because of permissive Selinux?
Magisk
arnabbandopadhyay said:
I am unable to run apps like "tez" , "bhim" on pixel experience rom installed in redmi note 3. Apps say that my phone is rooted but its not. I confirmed it by installing"root checker" app. My device is not rooted. is there any solution for this problem? is it because of permissive Selinux?
Click to expand...
Click to collapse
Install magisk 15.3 or whichever is latest and hide all the apps that don't require root in magisk hide, after that clear data of playstore and apps like tez etc. I used this method, it is working perfectly fine.
Hit thanks if a solution works. it will encourage us to answer queries.
yachandra said:
Install magisk 15.3 or whichever is latest and hide all the apps that don't require root in magisk hide, after that clear data of playstore and apps like tez etc. I used this method, it is working perfectly fine.
Hit thanks if a solution works. it will encourage us to answer queries.
Click to expand...
Click to collapse
I dont want to root my phone. Will magisk root my phone?
Easy & fast track method is just flash Magisk.zip and enjoy any app in any custom rom.
...but it will root your device!
arnabbandopadhyay said:
I dont want to root my phone. Will magisk root my phone?
Click to expand...
Click to collapse
Yes it will root your phone. But there won't be any root detection problems. I use snapchat, Tez etc on my phone
yachandra said:
Yes it will root your phone. But there won't be any root detection problems. I use snapchat, Tez etc on my phone
Click to expand...
Click to collapse
Is it safe to use banking apps on rooted device?
Yes it is safe to use banking apps on rooted device , if you're concerned about safety just don't install cracked apks or apps from outside other than playstore and use jio security or any such antivirus app
Simple method: you don't have to root the device. turn off play protect and find my device. You will get the OTP and you will be logged in. Then turn play protect and find my device on. (Tested only on Google pay. Don't know about BHIM).
May be because of unlocked bootloader
arnabbandopadhyay said:
i am unable to run apps like "tez" , "bhim" on pixel experience rom installed in redmi note 3. Apps say that my phone is rooted but its not. I confirmed it by installing"root checker" app. My device is not rooted. Is there any solution for this problem? Is it because of permissive selinux?
Click to expand...
Click to collapse
hi friend i was also faced the same issue , on my asus zenfone max pro m1 with pixel experience 10 plus and lineage os 16 and 17, using magisk couldnot help.
On Angler (Nexus 6p) I flashed the latest stock rom. (After a complete wipe) Afterwards I flashed TWRP and unzipped Magsik. Subsequently I did update to the latest version. After that I changed the packagename of Magsik manager. Furthermore I installed Xposed framework. Afterwards I enabled root hide for the TAN app:
https://play.google.com/store/apps/details?id=com.starfinanz.mobile.android.dkbpushtan&hl=en
This software is meant to give you the tan without using sms services.
Still, the app crashed right at the start without any error notification. Android Version is 8.1 and Magsik is v16. While I did the test, the bootloader was unlocked and TWRP was still the recovery. Can these two things affect the verification of the Banking app? I tried this several times ago in the past, but I was never to make this app running.
If anyone would be able to give helpful advice here, it would be very much appreciated.
Best,
scarline
I have heard that DKB Tan2Go does not work with newer Android versions like Oreo 8.1.x at all.
I can also confirm that. I tried it on a Sony cellphone. The cellphone was not rooted and with a completely new and 'clean' ROM. It was to no avail.
A friend has been forced to buy a chip reader. I am fortunate to be able to use normal TAN lists at the moment. If the DKB tries to exclude me from online banking, I will change the bank.
DKB Tan2Go seems to be one of the worst and most insecure apps ever. The reviews in Google PlayStore confirm this conclusion.
Maybe there will be a solution someday?
DKB TAN2go works with Magisk:
1. Install the TAN2go app (but don't open it)
2. Add the TAN2go app in Magsik Manager in the menu "Magisk Hide"
3. Reboot the phone (I don't know if this is necessary)
4. Open TAN2go, works fine.
**** DKB and this stupid security features which bring absoltuely no security.
That's exactly what I tried - without success. I read that it only worked with an old, obsolete version of Tan2Go. However, I could not find this version and I'm not sure if it still works at all. Did you have the latest version of Tan2Go from Google PlayStore? According to DKB, the recent Tan2Go does not work with devices that was once rooted or had a CustomROM. Even if you go back to stock the Root Counter changed and DKB Tan2Go will never work on this device. Unfortunately, I have to confirm that.
I am working on it to change the bank, because of that.
exaveal said:
DKB TAN2go works with Magisk:
**** DKB and this stupid security features which bring absoltuely no security.
Click to expand...
Click to collapse
Indeed!
Yes, I have installed the latests version of LineageOS, latest version von Magisk and the latests version of the TAN2go app.
I tried that to no avail. I heard once the root counter has a value other than 0, one can't go back. Probably it is also the Sony bootloader and it is different with other devices?
exaveal said:
Yes, I have installed the latests version of LineageOS, latest version von Magisk and the latests version of the TAN2go app.
Click to expand...
Click to collapse
I have a Xiomi Mi5 rooted with Magisk and Tan2go used to work for the last year or so. But yesterday I tried to make a transaction and BOOM! App crashed without an error message. Tried to use a newer Magisk, tried reinstalling the App, nothing helped.
The worst thing is that I do not know if some of my programs have a battery checker or a screen reader plugin that I am not aware of, or if Tan2Go suddenly detects my root. Regardless, crashing without an explanation is like the worst programming practice ever.
Since I do not need this kind of ****e in my life I will probably change Bank, I mean what good is an internet Bank if you cannot do transactions over your mobile device?
Well, willy-nilly I try to use the only other option from DKB: the German TAN Generator. Every other bank equips you with such a device, if they want you to use it. The DKB does not. Actually, I ordered the 3rd TAN Generator and fully paid for it. The first one drains the battery within days. The second one let me type in all the numbers and for no reason the TAN code does not show up on display.
These devices are very annoying anyway, because you have to type in a lot of numbers for every money transfer, the characters are very small (on the laptop) and you have to carry the TAN Generator + the DKB debitcard all the time. Of course this is less secure.
I would change the bank immediately, but want to keep the Visa credit card. I have higher limits on it. That's the only reason. As soon as I found an alternative bank in Europe, I will leave the DKB for good.
It dont worked with Lineage 14.1 but with 15.1 unoffical build on Samsung S4 together with latest Magisk .Rom from here
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-galaxy-s4-lte-android-8-1-oreo/
Works for me
Just tried again. It hasn't been working for me in the past. When downloading & opening the app, I had the same problems.
Then I simply followed the above advice: downloading the app again, didn't open it, hide with Magisk, reboot and opened the app - worked well and was able to register for tan2go.
I am using Lineage 16.0 and Magisk v18.0
DKB already updated their app - they patched it
kyodhin said:
Just tried again. It hasn't been working for me in the past. When downloading & opening the app, I had the same problems.
Then I simply followed the above advice: downloading the app again, didn't open it, hide with Magisk, reboot and opened the app - worked well and was able to register for tan2go.
I am using Lineage 16.0 and Magisk v18.0
Click to expand...
Click to collapse
The app version from September (version 2.3.0) does work, the newer app version from 4.4.19 (version 2.4.0) does not...
Tested working combination: Magisk 18.0, Magisk Manager 6.1, DKB version 2.3.0
Can confirm that, working with magisk and 2.3.0. Not working anymore with 2.4.0.
I have another Tan app from another bank and with the new version it also stops working. Seems that magisk is now quite to popular and they working on better detection. Magisk hide is useless on the recent version of these tan apps.
That really sucks. No way to get 2.4.0 working. Hoping for a magisk fix. Are the magisk developer informed that there are problems with magisk hide? I think others will have similar problems too.
I successfully got 2.4 working again, after it got updated and refused to start.
Following the steps from this post made it work again (German):
https://www.android-hilfe.de/forum/...trotz-magisk.901517-page-2.html#post-11532359
I installed Magisk 19.0 (beta) but contrary to the above mentioned post I left my Magisk modules installed as they were before the update.
Both the Magisk modules as well as TAN2Go 2.4 are now working again.
I had to authenticate the new TAN2Go installation by adding it as a "new device" using SMS verification.
I was not able to get it to run with the above mentioned instuctions.
Device: Nexus 6P (angler), ROM: LineageOS 15.1-20190419, Magisk modules: MagiskHide Props Config (required for ctsProfile test), Busybox for Android NDK (required for MagiskHide Props Config).
DKB Tan2Go crashes immediately when started.
Same for me. The above instruction doesn't work.
Downgrade to 2.3.0
I experienced the same problem. Had to do an important transfer yesterday. And of course Tan2Go-2.4.0 crashed. I'm using Magisk v18.1.
Today I did a downgrade via Aptoide to 2.3.0 and had to register the smartphone again via SMS. This worked without any problems.
To avoid the update problem and keep with 2.3.0:
Start Titanium Backup
Select the DKB Tan2Go App
Long click on the App.
Connect with Google Play Store (forced)
Long click the App again.
Disconnect from Google Play Store
Hope it helps. I don't think there's much to change in the DKB Api. I'll use 2.3.0 until they block it via the API.
If more people confirm the proposed solution with Magisk v19, I'll try it maybe.
I got it working with v2.4.0, but don't know which step was the solution. Switching to the "Canary" channel of Magisk or hiding the Magisk Manager in the settings. I think the last one was the solution.
Can you guys try and give feedback?
Don't forget to uninstall and install the app before testing again.
musv said:
If more people confirm the proposed solution with Magisk v19, I'll try it maybe.
Click to expand...
Click to collapse
I have the same issue. Hopefully it can be fixed via Magisk one day.
Worked with T2G 2.4, 19, 7.1.1
Walhalla said:
I got it working with v2.4.0, but don't know which step was the solution. Switching to the "Canary" channel of Magisk or hiding the Magisk Manager in the settings. I think the last one was the solution.
Can you guys try and give feedback?
Don't forget to uninstall and install the app before testing again.
Click to expand...
Click to collapse
Hi Walhalla,
Hi All
In Settings "General">"Hide" via other apk name it worked for me. V19.0, v7.1.1, Tan2Go 2.4
I recently unlocked my bootloader and flashed the latest xiaomi.eu MIUI 12 stable rom for my pocophone and flashed magisk for root access as well. Everything was fine and dandy untill i attempted to open my banking app, it greeted me with a messege saying that i don't have minimum security even though my phone passes all safetynet tests, i don't know where the problem is and i wish to solve it without having to switch back to stock.
Please help.
Have u tried renaming magisk manager and hiding it from banking apps. Worked for me.
ScarAss**** said:
I recently unlocked my bootloader and flashed the latest xiaomi.eu MIUI 12 stable rom for my pocophone and flashed magisk for root access as well. Everything was fine and dandy untill i attempted to open my banking app, it greeted me with a messege saying that i don't have minimum security even though my phone passes all safetynet tests, i don't know where the problem is and i wish to solve it without having to switch back to stock.
Please help.
Click to expand...
Click to collapse
Use magisk hide and hide it from your banking apps. If that doesn't work, hide it from google apps too.
mecoromeo said:
Use magisk hide and hide it from your banking apps. If that doesn't work, hide it from google apps too.
Click to expand...
Click to collapse
Tried it but no luck, I even uninstalled magisk but it still didn't work.
sanjay0501 said:
Have u tried renaming magisk manager and hiding it from banking apps. Worked for me.
Click to expand...
Click to collapse
How do i rename magisk?
https://forum.xda-developers.com/7t-pro/help/10-3-2-device-meet-minimum-security-t4084467/page2
Try this. He downloaded shelter to setup a working space for his bank apps
Use island app
Hi everyone, i've been out from the custom rom world for a while and i noticed that some things have changed; i read that rooted devices cannot run banking or securtity apps or even applications like netflix ect ect...
I recently decided to upgrade my old poco f1 to a Android 13 rom, but i stopped because i need banking apps to work and i don't know thant much anymore about the topic, is there anyone that could help me find a rom that supports the use of banking apps or any rom is good unless the device is rooted?
Thank yall in advance.
If the ROM passes SafetyNet out of the box then there should be no issues with the majority of the banking/financial apps provided you don't root your device. If you do root your device (with Magisk) you will need to use the Shamiko Magisk module to hide root. There's 2-3 additional steps which you can easily Google. In my case I can use every such app in all my rooted devices. Root breaks SafetyNet but most apps with the exception of Google Pay work just fine. To fix SafetyNet you can flash the Universal Safetynet Fix module. I don't know about others but after flashing this module Google login doesn't work. I can't add another Gmail account for example or use my Google credentials to newly log into apps etc. Since I don't use Google Pay much it's OK and I keep the USNF module disabled. Currently I am using crDroid A12. Will switch to it's A13 flavor in the coming months.