Hello there xda developers-Community ,
this is my very first post and I hope this is the correct board I'm posting in .
I have an issue with Cydia Substrate on Android, but before explaining to you what the issue is, I'd like to explain to you what I wanted to do and why I need Cydia Substrate (if you don't really care you can skip this, of course ):
I'm using a banking-app which, when detecting root on a device, stops working completely (it doesn't just show a warning, it refuses the user from continuing to the next screen). Of course, I don't want to unroot my device. So I did some research and came across apps like Hide my Root and RootCloak which is a Xposed Module. All of these apps didn't work for me, even when installed and set up correctly. After doing some research again I found out that it doesn't work for other users either... Doing even further research I finally came across RootCloak Plus which works with Cydia Substrate and not Xposed anymore. I can't confirm it yet, but according to the thread this method should work with my app. So, I downloaded Cydia Substrate (I tried the Google Play-Version and the APK from the website) and RootCloak Plus from Google Play. But now we get to the main issue:
Everytime I open Cydia Substrate it shows me a message saying:
Note: something about your device made it impossible for Substrate to perform its internal safety check; can you please contact saurik via e-mail?
Click to expand...
Click to collapse
Of course, actually contacting saurik via e-mail wasn't my first option .
I tried to fix this issue on my own with doing the following:
I updated CyanogenMod to the latest nightly
I switched my superuser app from SuperSU to superuser and back to SuperSU
I tried changing the SELinux mode from "enforcing" to "permissive" with SELinuxModeChanger
Reinstalled the apps and rebooted my device serveral times
Unfortunately, even though this problem seems to be quite common, there are only a few to nearly no threads covering this topic anywhere (at least I only came across over a few of them).
Here are some of my specs and details, maybe any of this will help:
Device: Samsung Glaxaxy S4 (jfltexx)
CyanogenMod version: CyanogenMod 12 12.1-20150708-NIGHTLY-jfltexx (Android 5.1.1)
Superuser App: SuperSU Free (CM) v2.46 (binary up to date and SuperSU working with other apps just fine)
BusyBox version: BusyBox v1.23.2-Stericson
Root properly installed and working, confirmed by serveral apps.
Do you have any idea how to fix this issue? I hope you can help !
Thank you very much,
DigitalClark .
I have the exact same issue. On my streaming app, xposed module allows me to bypass warning, but I still can't watch any shows...
Lg G3 D855
Rooted, Resurrection remix 5.5.4
Lollipop 5.1.1
I've emailed Saurikit on the email address provided on google play, but no reply...
Sent from my LG-D855 using XDA Free mobile app
I have the same problem on a Sony Z2 (sirius) CM12.1
So if anyone has an idea for a solving I'd highly appreciate!
Bump, in-case if someone has ran across a similar issue and found a solution.
Cydia Substrate is supported on Android 2.3 to 4.3 according to their website. Also the app itself hasn't been updated since 2013. Thus the chances that it will work on 5.1.1 are pretty dim.
I get the same message. I am just wondering if SuperUser is the reason. I don't think SU can find it, will this cause the internal safety check message to occur?
If you jail break your device it will work
I have the same problem ASUS ZenFone 2
Related
I'm in need of some kinda urgent help and advice regarding a phone i have just purchased for my mother.
I've bought her a cheap Daxian TD888 on the MTK6589 chipset and i'm afraid i have been a silly boy and not done my research before purchasing - I was under the impression that it came with the Play Store installed etc and sadly, it comes with a hard to use chinese ROM.
Mothers being mothers, mine isn't anywhere near tech/phone friendly and this is her first smartphone (upgrade from a 6 year old Nokia/symbian brick) so i was wanting to get her onto a nice and simple stock android 4.1 or 4.2 or even a CMxx that i can just help her along with.
After some very panic based searching today, i'm not seeing much that can help me... infact... nothing regarding this phone at all.
So... have I been a dumbass and bought her a lemon or is there anyone that can help me out with advice or pointers on how to get a normal android ROM on this thing?
I'm not massively experienced with rooting but have managed it a couple fo times in the past on my old Nexus One.
Any help would be greatly appreciated.
scottmeister said:
I'm in need of some kinda urgent help and advice regarding a phone i have just purchased for my mother.
I've bought her a cheap Daxian TD888 on the MTK6589 chipset and i'm afraid i have been a silly boy and not done my research before purchasing - I was under the impression that it came with the Play Store installed etc and sadly, it comes with a hard to use chinese ROM.
Mothers being mothers, mine isn't anywhere near tech/phone friendly and this is her first smartphone (upgrade from a 6 year old Nokia/symbian brick) so i was wanting to get her onto a nice and simple stock android 4.1 or 4.2 or even a CMxx that i can just help her along with.
After some very panic based searching today, i'm not seeing much that can help me... infact... nothing regarding this phone at all.
So... have I been a dumbass and bought her a lemon or is there anyone that can help me out with advice or pointers on how to get a normal android ROM on this thing?
I'm not massively experienced with rooting but have managed it a couple fo times in the past on my old Nexus One.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I could probably help you get it rooted and that would allow you to install Play store on it as well as delete any chinese apps that sometimes come on the MT65XX devices if interested. As far as the rom goes, is there not an option in settings to change language to English? I have bought a few MediaTek devices directly from china, when I received the phone it had english on it already but when I reset the phones I would have to go into Settings and change chinese language back to english.
Motochopper should root your phone:
http://forum.xda-developers.com/showthread.php?t=2252248
One thing with these phones is that the android version is not always what is shown in Settings > About phone. Try using this tool from the first post of this thread:
http://forum.xda-developers.com/showthread.php?t=2160490&styleid=18
make sure you enable USB debugging on your phone first and it will help tell which version of android you are really running. If kernel say 2.6.xx you are on GB 2.3, if it is 3.0.xx then you are on ICS and if it says 3.4.xx then you are JB. I bought a MT6575 that said android version 4.0 in settings, it said gingerbread 2.2 on the box (I know 2.2 is Froyo), then on bottom of box it said Froyo 2.2!
Thanks Klown80 -
I'm just into work now so I'll have to hook it up to my own PC and root when i get home later... i'm just in full on panic mode over this (its a time sensitive issue as she's due to be in hospital for an extended period and i want to get this right for her before then)
Regarding the language settings in the current/stock rom, it has english US selected and while a lot of the language is in english, pretty much ALL popup dialogs are in chinese and the browser is unusable (all chinese text based) so... hence the panic.
I was (foolishly) thinking it would just be a simple enough flash to CM or stock android and hey presto - full english ROM.
I hate it when i don't do my homework first.
So... you recommend the root first, check exact android version number and go from there?
Even if it turns out to be an older 2.1/2.2/whatever version, i'd be happy enough to get something stock and full english based on there if its possible.
As she's never had a smart phone, it will all seem super smooth and flashy to her anyway.
I have now rooted (i think..) however, the superuser app comes up with an error upon opening -
superuser binary (su) must be updated
and i now i'm kinda stuck.
I have downloaded and tired various versions of the play store and while the at first allow me to enter google accounts details, it always crashes after that.
Every time i open the play store app, it just closes again.
Any suggestions on where i might be going wrong?
scottmeister said:
I have now rooted (i think..) however, the superuser app comes up with an error upon opening -
superuser binary (su) must be updated
and i now i'm kinda stuck.
I have downloaded and tired various versions of the play store and while the at first allow me to enter google accounts details, it always crashes after that.
Every time i open the play store app, it just closes again.
Any suggestions on where i might be going wrong?
Click to expand...
Click to collapse
Sounds like you need to update the binary then, if it allows you. If not then the root did not correctly root your device and we will have to go back a step and get that fixed first. As for Play Store, it usually takes more than just the Play.apk file to put Play Store on your device if it did not come with it stock. You also need (I am going off top of my head, I can give you exact names later) Google services framework.apk, Google login services.apk, Google Play services.apk. You need to have root to to this because you will need to move the vending.apk to /system folder and possibly change permissions on the apk before you install it. Once we can confirm root I can help you install a working Play Store if you like.
aphotaW are
Klown80 said:
Sounds like you need to update the binary then, if it allows you. If not then the root did not correctly root your device and we will have to go back a step and get that fixed first. As for Play Store, it usually takes more than just the Play.apk file to put Play Store on your device if it did not come with it stock. You also need (I am going off top of my head, I can give you exact names later) Google services framework.apk, Google login services.apk, Google Play services.apk. You need to have root to to this because you will need to move the vending.apk to /system folder and possibly change permissions on the apk before you install it. Once we can confirm root I can help you install a working Play Store if you like.
Click to expand...
Click to collapse
I've no idea how to update the binary so I guess i'm looking at a re-root.
I have had the usual issues of drivers not wanting to work (the Motochopper root process getting stuck at the daemon starting point) but I've manged to get the process to work twice so far.
(I've tried 4 different driver packages and they have all given the same results)
Could you possibly advise on how to update the binary file for superuser? I've just tried the root again and it skipped installing superuser as it was already found on the phone.. i haven't felt this noobllike in some time!
scottmeister said:
I've no idea how to update the binary so I guess i'm looking at a re-root.
I have had the usual issues of drivers not wanting to work (the Motochopper root process getting stuck at the daemon starting point) but I've manged to get the process to work twice so far.
(I've tried 4 different driver packages and they have all given the same results)
Could you possibly advise on how to update the binary file for superuser? I've just tried the root again and it skipped installing superuser as it was already found on the phone.. i haven't felt this noobllike in some time!
Click to expand...
Click to collapse
Sounds like the same prob with my.mtk device,
With motochopper i.get to update binary, but thats not possible.
You can try some of the roottools in my.acer811 thread.
I get many tipps from clown80.
scottmeister said:
I've no idea how to update the binary so I guess i'm looking at a re-root.
I have had the usual issues of drivers not wanting to work (the Motochopper root process getting stuck at the daemon starting point) but I've manged to get the process to work twice so far.
(I've tried 4 different driver packages and they have all given the same results)
Could you possibly advise on how to update the binary file for superuser? I've just tried the root again and it skipped installing superuser as it was already found on the phone.. i haven't felt this noobllike in some time!
Click to expand...
Click to collapse
Try uninstalliong Superuser or SuperSU and try again. Su binary should ask you if you want to update when you first open SuperSU, if you have Superuser, then you will need to open the app and go into settings to update binary.
meconte cutstones
Klown80 said:
Try uninstalliong Superuser or SuperSU and try again. Su binary should ask you if you want to update when you first open SuperSU, if you have Superuser, then you will need to open the app and go into settings to update binary.
Click to expand...
Click to collapse
It was aksing to try and update etc but its chashed every time - I was thinking that the root hadn't worked properly or something... anyway, I've uninstalled Superuser and reinstalled from a newer apk file (v3.2) i downloaded.
Its now running ok. Now that superuser is working... whats next?
scottmeister said:
It was aksing to try and update etc but its chashed every time - I was thinking that the root hadn't worked properly or something... anyway, I've uninstalled Superuser and reinstalled from a newer apk file (v3.2) i downloaded.
Its now running ok. Now that superuser is working... whats next?
Click to expand...
Click to collapse
Ok, is it just Superuser and not SuperSU correct? Can you go into settings in Superuser and towards the bottom there should be an option to update su binary. If it is SuperSU it will ask to update on its own when you open it. either way make sure it lets you update binary. Once binary is updated download and install any app that asks for root acces, so we can see if superuser request pops up.
Once we have confirmed root we can move onto installing Play Store. To do this you will need to be able to install a file explorer like ES file explorer so we can install the files we need for working Play Store.
Klown80 said:
Ok, is it just Superuser and not SuperSU correct? Can you go into settings in Superuser and towards the bottom there should be an option to update su binary. If it is SuperSU it will ask to update on its own when you open it. either way make sure it lets you update binary. Once binary is updated download and install any app that asks for root acces, so we can see if superuser request pops up.
Once we have confirmed root we can move onto installing Play Store. To do this you will need to be able to install a file explorer like ES file explorer so we can install the files we need for working Play Store.
Click to expand...
Click to collapse
In the superuser settings, there isn't anything apparent for trying to update the su binary.
the list reads as follows:
Security
Apps List
Log (on)
Notifications (on)
Backup apps/preferences
To anyone with this same device, this is method Scottmeister used to root his device. (Thanks Scott for being the tester! :good: )
http://forum.xda-developers.com/showpost.php?p=43163569&postcount=7&styleid=18
nuiryou food
HUGE thanks to Klown80 for the advice and patience!
For anyone else in a similar situation with an MTK6589 cheapo phone, and had issues with the Motochopper root method (the root getting stuck at 'daemon started successfully' etc etc.....
Klown80's chinese root tool works a treat. You will have a chinese superuser app that may be a little annoying (you might be able to swap it for SuperSU or something but I had issues doing that so i've kept the chinese one) but the root works perfectly and the instructions given by Klown80 in the linked thread are very easy to follow.
I still had some issues with getting google services installed so you may want to look for a play store installer workaround - I know there is a cheeky little chinese mod apk that can be used to get the play store working, but i can't post it here.
Should anyone come across this thread and know of a good, stock english rom that I might be able to use, please leave a comment!
Klown80 said:
To anyone with this same device, this is method Scottmeister used to root his device. (Thanks Scott for being the tester! :good: )
http://forum.xda-developers.com/showpost.php?p=43163569&postcount=7&styleid=18
Click to expand...
Click to collapse
Hello!
I have to a Daxian XY100 smart phone, Not a bad handy, but I try everything, and I can't root,
Can anybody help me?
petz765 said:
Hello!
I have to a Daxian XY100 smart phone, Not a bad handy, but I try everything, and I can't root,
Can anybody help me?
Click to expand...
Click to collapse
OK ! Nobody!:crying:
SRY for my bad englis
petz765 said:
OK ! Nobody!:crying:
SRY for my bad englis
Click to expand...
Click to collapse
I'm not a lucky guy!
Nobody answer to me.
Realy bad luck.
Sry for my bad englis.
Hey there, after reading this forum for awhile, I still haven´t managed to get a root on this device, tried framaroot, klingo root, iroot, and many more, i get the SuperSU app on the device but it doesn´t give root permissions to any other apps, have someone successfully root this tablet? or have any ideas? Thanks in advance!
Version is Android 4.4.2
Kingo root
I found and downloaded "Kingo Root". I ran it from my PC with my Dragon Touch 10.1" A1X Plus connected and it says I'm ROOTED. I already had a root checking App on my tablet and it verified that I'm rooted. Later today I'll try some Apps that require root like Titanium Backup and some different games.
Kingo seemed pretty straightforward and user friendly but until I have time to do some testing I won't be able to completely vouch for this software. But, I didn't get anything weird on my PC nor tablet so far. I do have Avast running on my tablet and AVG running on my PC so I should be protected from malware and viruses. I suggest that everyone protect your devices prior to loading any software.
Kingo Root doesn't work!
Racshamar said:
I found and downloaded "Kingo Root". I ran it from my PC with my Dragon Touch 10.1" A1X Plus connected and it says I'm ROOTED. I already had a root checking App on my tablet and it verified that I'm rooted. Later today I'll try some Apps that require root like Titanium Backup and some different games.
Kingo seemed pretty straightforward and user friendly but until I have time to do some testing I won't be able to completely vouch for this software. But, I didn't get anything weird on my PC nor tablet so far. I do have Avast running on my tablet and AVG running on my PC so I should be protected from malware and viruses. I suggest that everyone protect your devices prior to loading any software.
Click to expand...
Click to collapse
After testing last night I found that Kingo Root doesn't truly root the Dragon Touch 10.1" A1X Plus. While for a short time my root checker did show that I was rooted, Titanium Backup and other apps were not able to gain root access. At one point I had to perform a soft reset to get off a blank screen. I have discovered that the ROM used for this build is from HTC so maybe the root software used for this should be something used for HTC phones and tablets. So, keep searching folks because Kingo Root is NOT the answer for root accesss...Sorry!
My grandmother just got a "Bright Tab" 10" tablet. As far as I can determine, the same generic Chinese company that makes the particular tablet that gets branded as Dragon Tab normally makes this. This appears to be an unbranded version of the exact same tablet (I think specifically for Walmart to reduce costs a bit. They also threw in a lovely malware called "Google 12.0" that shows annoying popup ads frequently and slows down the whole system...) I noticed it even had a "DragonFire" and "DragonPhone" app in there.
Anyway, I did get it rooted. First, KingoRoot seems to sort of temproot. However it does appear to have an actual writable system partition, not one of those read-only images with a hybrid overlay mounted on boot as many systems do. So here's what you do. Run KingoRoot's app to temproot. Install SuperSU or your favorite SU app from the play store and while temprooted, manually install the real SU app to /system via the settings. Then remove the KingoRoot stuff (disable the KingoApp app temporarily to stop it from trying to take over, then you can uninstall it using TitaniumBackup assuming all goes well.) After all of this I seem to have true root and can now install Greenify, Xposed Framework, and so on.
I was hoping to find at least a CWM/TWRP option for this thing (I know CyanogenMod or any other AOSP -- or even a cleaner more proper build based on the stock ROM -- is impossible, but at least a proper recovery would be nice.) So far no good though.
Nazo said:
My grandmother just got a "Bright Tab" 10" tablet. As far as I can determine, the same generic Chinese company that makes the particular tablet that gets branded as Dragon Tab normally makes this. This appears to be an unbranded version of the exact same tablet (I think specifically for Walmart to reduce costs a bit. They also threw in a lovely malware called "Google 12.0" that shows annoying popup ads frequently and slows down the whole system...) I noticed it even had a "DragonFire" and "DragonPhone" app in there.
Anyway, I did get it rooted. First, KingoRoot seems to sort of temproot. However it does appear to have an actual writable system partition, not one of those read-only images with a hybrid overlay mounted on boot as many systems do. So here's what you do. Run KingoRoot's app to temproot. Install SuperSU or your favorite SU app from the play store and while temprooted, manually install the real SU app to /system via the settings. Then remove the KingoRoot stuff (disable the KingoApp app temporarily to stop it from trying to take over, then you can uninstall it using TitaniumBackup assuming all goes well.) After all of this I seem to have true root and can now install Greenify, Xposed Framework, and so on.
I was hoping to find at least a CWM/TWRP option for this thing (I know CyanogenMod or any other AOSP -- or even a cleaner more proper build based on the stock ROM -- is impossible, but at least a proper recovery would be nice.) So far no good though.
Click to expand...
Click to collapse
It appears that your method works. I was able to perform all of the steps except for the manual install of the SU app into the /system. But all of the apps that I've tried that require root access are working. I'm still evaluating the outcome but so far so good.
Glad to hear it worked at all. Maybe try again after a reboot now that the alternate SU app has taken over? Oh, I think I had actually run Kingoroot first before running the alternate app. Since it's a temp root you have to rerun it every startup until you get the alternate installed into the system I guess.
My grandmother finally listened to me and will probably be taking that tablet back now, so I can't really mess around with it anymore to give any specifics. I convinced her to get something else that I think will make her a true Android convert instead of just wanting some little side thing for reading only, so one way or the other that thing is probably going to go, lol.
Root with iroot
Sent from my Dragon Touch M8 using XDA Free mobile app
---------- Post added at 06:08 PM ---------- Previous post was at 05:54 PM ----------
I'm 100% rooted on a1x plus and m8 tablet https://m.youtube.com/watch?v=a5_iqHBjA7k
Sent from my Dragon Touch M8 using XDA Free mobile app
I just spent a couple hours trying both the iRoot and KingoRoot methods on a TabletExpress Dragon Touch M8 with Android 5.0 without success. I got to the point where I could open SuperSU, but then SuperSU wanted to update the binary and failed. I tried the KingoRoot tethered and apk installations. I tried using KingoRoot's Superuser App. Nothing worked. And Cyanogenmod is still a no-go.
Did you get kinguser? Or did you install supersu?
Sent from my Dragon Touch M8 using XDA Free mobile app
cfmoreno said:
Hey there, after reading this forum for awhile, I still haven´t managed to get a root on this device, tried framaroot, klingo root, iroot, and many more, i get the SuperSU app on the device but it doesn´t give root permissions to any other apps, have someone successfully root this tablet? or have any ideas? Thanks in advance!
Version is Android 4.4.2
Click to expand...
Click to collapse
Check out this video mate sorry i didn't post it earlier
https://youtu.be/57eLSvzBuII
---------- Post added at 06:20 AM ---------- Previous post was at 06:13 AM ----------
guest1984b said:
I just spent a couple hours trying both the iRoot and KingoRoot methods on a TabletExpress Dragon Touch M8 with Android 5.0 without success. I got to the point where I could open SuperSU, but then SuperSU wanted to update the binary and failed. I tried the KingoRoot tethered and apk installations. I tried using KingoRoot's Superuser App. Nothing worked. And Cyanogenmod is still a no-go.
Click to expand...
Click to collapse
I think i found a solution after messing with my dragon touch m8... use iroot and make sure when you connect the m8 to your computer you have the usb debugging checked...unlock the screen before you plug it in and when iroot reads it you should see a pop up on the screen click ok and click reconnect it worked for me
if all else fails check out my video
https://youtu.be/57eLSvzBuII
I wanted to start this thread because it appears the new Android Pay app will not work on rooted devices. It's not a device specific issue.
I was able to gain a small victory on my VZW MotoX 2014 unlock/rooted device. I disabled superuser within the SuperSU app and was able to add one of my CCs.
Thats where the good news stops. My phone does not work at retailers and I am no longer able to add any more CCs even with root disabled. There must be a fuse that triggers when the app discovers you are rooted.
I've tried xposed mods - Root Cloak and No Device Check with no luck.
I have not tried it at the store with the xposed mods, but I am not able to add any more CCs.
Thoughts?
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