Related
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?
Hello!
I recently activated Online Banking for my Bankaccount. They use pushTAN with their own build app. I used xposed and SuperSU, but decided to flash a new ROM with only magisk. My current device is the Huawei P8lite with OmniROM and magisk 13.3. My device passes SafetyNET and it says certified at the Play Store. I checked magisk hide for the pushTAN app and the normal Sparkasse app. The Sparkasse app works, but it still says that my device is rooted. The pushTAN app however wont start. It says, that the app was closed and opens a website in chrome saying that my device is unsecure because I have root. I just flashed this ROM and I have no other root requiring apps installed. I've uploaded both apps to my G-Drive, so maybe someone can look and see why it still sees root. the pushTAN app is more important.
pushTAN.apk
Sparkasse.apk
Soo, I used the phone of my brother now. After getting my TAN I was able to set up the normal Sparkassen App. It works fine. But the pushTAN app still doesn't work on my device. I tried another different ROM now, but still no difference.
Any news on that?
I have the exact same problem. Axon 7 here, rooted via Magisk. Magisk is set to "hide" from pushTAN app and also "hide from various detections" in settings.
pushTAN crashes and redirects to a webpage hinting that i have rooted my device.
Same issue for me :/ once i run Magisk-uninstaller pushtan app works immediately
I can approve: it works if you temporarly uninstall magisk, without? uninstalling the root patch.
Other way would be to install s-pushtan into an emulator on your PC, like this:
Download S-pushTAN on PC with MEmu
Download S-pushTAN on PC with MEmu Android Emulator. Enjoy playing on big screen. pushTAN is the correct procedure for anyone who wants to make mobile banking.
www.memuplay.com
But, I would NOT trust a download that packs app and emulator into a single package. This massively increases the likelyhood of a special hack applied that spies on s-pushtan. I recommend finding any plain Android emulator then install S-pushtan from Play store. This might be more difficult, though.
Would be a joke if it really worked, since S-pushtan is all about using different devices for login and transaction authorization. This would be broken if you use an emulator on your PC. So it would make the transaction even more insecure than a rooted phone.
I'll have a look if there is an official, viable alternative to s-pushtan.
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
Apparently, my bank updated the app with a new feature that doesn't let me access it anymore, it says that the operating system is not supported, i use a custom rom(AEX) in my Redmi 4x, i believe that the rom is the problem, the root is being hidden with MagiskHide and i have no problems with SafetyNet, maybe i can change some parameter in build.prop to make it work? i did something similar to try to run Fortnite in my phone a while ago, any ideas on what parameters may be relevant to that?
It's a brazilian bank(Banco Inter)
Need Solution for this Problem as Well
I have the same problem.
The new app version 8.4.6 is not working while up till version 8.4.5 it was working just fine.
Their support is absolutely clueless on how to help, but as @Levyks said, apparently they are blocking custom roms now.
Is it possible to make the custom rom look as an original rom from manufacturer?
Same problem.
I'm with the same problem...
IMHO has nothing to do with fact whether it's a Custom ROM or a Stock ROM. Any app ( banking apps included ) easily can find out whether present Android OS got tampered or not.
Same problem any help? Can't use my bank app... WhatsApp also can detect I have a custom ROM, any solution?
Incomtus said:
Same problem any help? Can't use my bank app... WhatsApp also can detect I have a custom ROM, any solution?
Click to expand...
Click to collapse
Many apps like banking / payment apps today detect whether Android is got rooted or not: it's an easy for them to do so.
Same problem here in Lineage OS 18.1. My non-rooted device pass safetynet and CTS by default. But many Banking application had started detecting that I am using custom rom and don't open at all. Then I rooted my device with magisk and enabled 'magisk hide' but no success.
Hi! A solution that worked for me: use the renaming function in Magisk (you can find it in the Settings).
I had the same problem on a Redmi 4X, LOS 16, no working banking app even with Magisk hide. After renaming Magisk, I was able to log in and use it as intended. Also I left Magisk hide turned on.
My guess is that these kind of apps are looking specially for Magisk, and if it's detected, they just won't let you use them.
A13 stock. Magisk 25203. PS Remote Play app 5.5, and hidden in the Magisk deny list, like other apps.
Other typical root detecting apps foiled, but not this one. Hiding the Magisk manager itself didn't help.
Suggestions?
Assuming you're on the stock ROM, else you might need to use MagiskHide Props Config. Try turning on Zygisk and adding Displax's version of USNF and Shamiko (note: Shamiko is a closed-source root hider, so your call if you trust it). Keep in mind that if you use Shamiko, then the "enforce deny list" switch needs to be off. Shamiko reads from the list and handles it instead (so you do still need to have Google Play Services and PS Remote Play in the deny list). So far I haven't had anything detect root with this setup as long as it's in my deny list, though I don't have a PlayStation so I can't test it with this specifically.
I am on A13 stock. I'll look into this. FWIW, one doesn't need a PlayStation to see the app PS Remote App fail the root check, which is upon opening it, resulting in error 88001003
PS Remote Play - Apps on Google Play
Access your PS5 or PS4 wherever you go.
play.google.com
Interesting, it's happening the moment you open the app? I don't have a Playstation account, but I can open the app and get in far enough to see the account login screen with no error. That's on my system with the above utilities installed as well as Magisk and LSposed, running the Android 13 QPR1 beta. If you set all that up and it's still happening, try clearing the PS Remote Play app's data, too.
Jaitsu said:
Interesting, it's happening the moment you open the app?
Click to expand...
Click to collapse
Yes. It may be using some data from the general PS App to auto-login, but it appears as instantaneous error to me, even after full storage/cache wipe and force close.
I just updated USNF, and installed the MOD version on top of that as you suggested, still no go. Disney+, Nintendo, other apps that check still work. Play Store certified, pass YASNAC.
Haven't tried the Shamiko thing yet
Are you hiding the Magisk app itself?
I'm using Canary manager, btw
deusfaux said:
Yes. It may be using some data from the general PS App to auto-login, but it appears as instantaneous error to me, even after full storage/cache wipe and force close.
I just updated USNF, and installed the MOD version on top of that as you suggested, still no go. Disney+, Nintendo, other apps that check still work. Play Store certified, pass YASNAC.
Haven't tried the Shamiko thing yet
Are you hiding the Magisk app itself?
I'm using Canary manager, btw
Click to expand...
Click to collapse
I am hiding the Magisk app itself, with the default "Settings" name. Normal release (25.2/25200) of Magisk. Do you have any other root-related apps the PS Remote Play app might be looking for? (Though I myself have Fox's Magisk Module Manager, LP, the TWRP app, and Franco Kernel Manager installed on my phone and they don't seem to be setting it off.)
I'd suggest turning off USB debugging. I had similar issue with some of my banking and other apps and tried every possible solution but didn't work. Finally I read somewhere to turn off USB debugging and Eureka!!
I've narrowed it to something the recent app version 5.5 is doing
Versions 5.0 and earlier have no problems loading.
My USB debugging is/was off.
It must be looking at / for some other app I have installed, which is really annoying to troubleshoot
Hello,
As you said, I downgraded the app to the version 5.0 ans now I can login
But I can't associate the playstation
It ask me to upgrade to the last version and if i refuse, the association failes.
Do you have the same problem ?
Thx
twingo_man said:
Hello,
As you said, I downgraded the app to the version 5.0 ans now I can login
But I can't associate the playstation
It ask me to upgrade to the last version and if i refuse, the association failes.
Do you have the same problem ?
Thx
Click to expand...
Click to collapse
Ver 5.01 asked me if I wanted to update but i could choose 'later' and successfully connect to my PS5
i choose later but I can't connect to my ps5
i will try to put it on wifi...
twingo_man said:
i choose later but I can't connect to my ps5
i will try to put it on wifi...
Click to expand...
Click to collapse
We should also try to determine what exactly latest version is detecting and preventing app from working