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 am using future pay app whenever i try to open it, it says "root detected you cannot use this app" i have used magisk hide and also denied permission of telephone and sms from google play services and play store but still no luck
What should i do ?? I use this app a lot but it doesn't work on a rooted custom rom
After magisk hide did you force stop and clear data from future pay?
mecoromeo said:
After magisk hide did you force stop and clear data from future pay?
Click to expand...
Click to collapse
Thank you for replying i found a solution to my problem
The safetynet check fails after few hours or so and i have to turn the toggle switch for magisk hide off and then on, once i do it the app works fine without any issue
I hope this safetynet issue gets solved after a few upates of magisk
Glad to hear that the issue was resolved. If you still have safety check issue, try to flash magisk again, clear cache and dalkiv. That should fix it. I don't have issues with Magisk right now, but I had a similar issue before and the step above fixed it
I seem to be having an odd problem. I accidentally deleted my Magisk Manager and after reinstalling it it gives me the Safetynet API Error. I've tried reinstalling, clearing the data, etc. with no change. The particularly odd part is that there doesn't seem to actually be a problem and everything is working fine. GPay, modules, everything appears to function without issue. Anyone have an idea of how to fix this?
*Potentially Solved
Downgrading to 8.0.1 makes it so that the Magisk Manager show me passing the Safetynet check without me changing anything. It seems like the failed Safetynet test is just a problem with the most recent release.
Hi,
I love using Naptime app by Franco cause it installs a magisk module called GMS doze which enables battery optimization for Google Play Services.
Problem is this module only comes with Naptime app. So I want to have this module as a flashable zip, which would allow me to install without Naptime app.
I like the app but it doesn't work properly with my Android 11 device.
I know magisk modules are stored in data/adb/modules but they're not stored a zip there. So I can't get it out.
How can I get a magisk module out of magisk manager to have it as a flashable zip?
Thank you
By means of ADB you copy the module in question onto your desktop computer, where you then can insert it into a flashable ZIP it.
Alright Im new to XDA but not new to rooting. I'm hoping to get some answers with a glitch I have found. I have passed safety net no problems (I am rocking a oneplus 8 pro and its been rooted since I got it!) Until now! Magisk say api error , and other safety-net apps fail too! The weird thing is Netflix and my baking apps work no problems so I'm not to worried but it bugs the crap out of me! The troubleshooting steps I took was, I factory reset and rerooted (after hours of trying to find out what change) I went back to stock ROM and rerooted the phone and still cannot figure it out! I went ahead and put lineage 18.1 back on and hope I can find some answers later. Maybe I can get someone to check there safety net through magisk and see if its a me problem or a magisk problem. Thanks guy!
Hi to all;
So i decided to do a clean update from MIUI 12 to MIUI 13 (which I think was a big mistake) ; using Orange Fox to format the data and install the official EU MIUI 13 OS and Magisk 25.2 afterwards. The phone boots up fine; I set up my account and Magisk is also setup (Magisk Hide, enforce deny list and configured the deny list to deny google play services, etc) I run a safety net attestation and all is fine too, so I proceeded to check Playstore and in the about it also says 'certified'. So I went to search for Netflix; but it does not show.
I searched for countless hours in search for a solution but I could not find anything that would work
I even tried re installing MIUI13 without magisk but Netflix does not show up in Playstore; plus that in the about section of Playstore device is uncertified. (Could this be that this happens because the bootloader is unlocked?
So this time I re-installed everything from scratch, Magisk included, and same as before the only app that does not show in Playstore is Netflix; the only way I was able to get Netflix installed & running was installing it as an apk.
In the playback specifications on Netflix Widevine is at L1 which should be good I guess?
Sorry for the long post but I am at a loss and hoping someone might have experienced something similar or maybe found a solution to my issue please?
I have banking apps that are working fine and have no issues what so ever so I know that the denylist on Magisk is working properly otherwise these apps would not let me authenticate.
I am including some screenshots to give a better explanation of my issue.
Thank you !
To anyone having similar issues to the one I was having above; the following post fixed my issues; here .