Hi,
I had the HDX 8.9 Saturn running with the older rooted firmware (4.x). Then I updated to Android 5.1.1 with the help of the other thread here and everything was working immediately after that.
However, I noticed that there were some residues of the old Android 4 installation. Especially a very outdated Android Webview (v.41) was causing issues with some apps I wanted to use. (updating the webview from play store did not work as the old one was a system app and was not "overridden" by the play store app).
So after the upgrade the old webview was still there and the behavior of the 3rd party apps still like before. So I opened up Titanium Backup and removed the old webview as well as an app from Amazon (someting like amazon.webviewkkhelper or similar) with the same version as the outdated Android webview (the "kk" in the name made me think it was a Android 4.4 Kitkat residue).
Now, after a factory reset, however, I cannot sign in my Google account. After entering user/password the screen jumps back to the first screen (choose between login with existing account or new account).
In logcat I can see that apparently the webview is called and not found:
Code:
W/PackageManager( 997): com.amazon.webview.chromium is not installed for user 0
W/PackageManager( 997): com.android.webview is not installed for user 0
I'm not 100% sure that these messages are actually describing whats causing the issue, but they are a strong indicator that the google login wants to access a webview component.
Now, I have sideloaded the most recent webview from APKmirror, but it is called
Code:
com.google.android.webview
and is threfore probably not found / used.
Can anyone help me restore the system webviews that came with the Android 5.1.1 update?
Which versions of it do you guys see in the stock image?
Thank you in advance
Jochen
jo2012 said:
Hi,
I had the HDX 8.9 Saturn running with the older rooted firmware (4.x). Then I updated to Android 5.1.1 with the help of the other thread here and everything was working immediately after that.
However, I noticed that there were some residues of the old Android 4 installation. Especially a very outdated Android Webview (v.41) was causing issues with some apps I wanted to use. (updating the webview from play store did not work as the old one was a system app and was not "overridden" by the play store app).
So after the upgrade the old webview was still there and the behavior of the 3rd party apps still like before. So I opened up Titanium Backup and removed the old webview as well as an app from Amazon (someting like amazon.webviewkkhelper or similar) with the same version as the outdated Android webview (the "kk" in the name made me think it was a Android 4.4 Kitkat residue).
Now, after a factory reset, however, I cannot sign in my Google account. After entering user/password the screen jumps back to the first screen (choose between login with existing account or new account).
In logcat I can see that apparently the webview is called and not found:
I'm not 100% sure that these messages are actually describing whats causing the issue, but they are a strong indicator that the google login wants to access a webview component.
Now, I have sideloaded the most recent webview from APKmirror, but it is called
and is threfore probably not found / used.
Can anyone help me restore the system webviews that came with the Android 5.1.1 update?
Which versions of it do you guys see in the stock image?
Thank you in advance
Jochen
Click to expand...
Click to collapse
Assuming you rerooted install the Play Version of webview and then migrate it to the system partition using TB or another tool like Apps2SD. I have seen this both work and fail on Lollipop bases ROMs. Good luck.
Edit: Understand the naming issue; recent Google Play Services builds should look for both.
Davey126 said:
Assuming you rerooted install the Play Version of webview and then migrate it to the system partition using TB or another tool like Apps2SD. I have seen this both work and fail on Lollipop bases ROMs. Good luck.
Edit: Understand the naming issue; recent Google Play Services builds should look for both.
Click to expand...
Click to collapse
Thanks @Davey126, that helped. I installed the older webview v60 which was still called com.android.webview and made it a system app.
Then it worked again!
Login failed still but that was a different issue. Had my system further borked by trying to install Google stuff via flashfire... who knows what that did, but it did not work either. However, it prevented the old play store stuff to fail. I manually cleaned it up (hopefully) but at least now I can install the old playstore + gms again again .
Login worked afterwards. Lets see how it goes
Kindle Fire tablet are always a handfull... :silly:
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
Hello,
What would be the 2019 cleanest way to uninstall a system app?
My case: Flashed xiaomi EU (clean) ROM for a Redmi and it didn't come with youtube preinstalled. I ran to install it but now I noticed it cannot be uninstalled normally, only remove system updates (this one is funny because I assume removing system updates leaves a base version but not sure what a base version of youtube would be for a ROM that didn't have it in the first place, I guess youtube base version would be related to playstore version installed).
So I've seen uninstall procedures via ADB, titaniumbackup (don't own it yet) and other playstore apps. But not sure what would be the most recommended method nowadays, on a rooted phone (magisk) if that makes any difference.
Thanks for your time
I was wondering if there was an android 12 GSI rom out there that is not rooted but still has GAPPS installed? I am asking because I just now tried a couple of android 12 based GSI roms on my phone (lineageos 19 and octaviOS), and while both ran well, I wasn't able to run banking apps for example, or any other apps that check for rooted phones.
I tried: using magisk hide (even though it is being phased out), using zygisk on magisk 24, using shamiko on android 24, flashing an unSU script with TWRP, even manually deleting the SU binary in /system/xbin and /system/bin, and anywhere else where SU shows up, uninstalling magisk. Nothing seems to work. I even checked for no root with various rootcheck apps and while root is gone after all this, the banking, etc apps STILL don't run.
I am able to run those same apps on the rooted stock android 11 retus where magisk is hidden by zygisk with no problems. What is going on with the GSI roms?
Have you checked if the ROMs build properties are flagging the system as debug or development build? Though I'm not quite as versed in dealing with GSI, I'd consider the possibility that a flag is being set off, probably upon installing a GSI ROM would be my guess.
How do I update my Android System Webview? I'm WAY out of date (87. something).
I'm using the Resurrection Remix ROM.
Since it's a system app on Ressurection you'll either have to manually replace it or use magisk. One good option is to install bromite system webview which can be installed with magisk or again, manually with a file manager or adb. I use the magisk module which gets updated via Aurora Droid or Droidify or just installing the apk at that point. Hope this helps a tiny bit at least.
Installing SystemWebView
Bromite is a Chromium fork with ad blocking and privacy enhancements; take back your browser! - bromite/bromite
github.com
griz.droidx said:
Since it's a system app on Ressurection you'll either have to manually replace it or use magisk. One good option is to install bromite system webview which can be installed with magisk or again, manually with a file manager or adb. I use the magisk module which gets updated via Aurora Droid or Droidify or just installing the apk at that point. Hope this helps a tiny bit at least.
Installing SystemWebView
Bromite is a Chromium fork with ad blocking and privacy enhancements; take back your browser! - bromite/bromite
github.com
Click to expand...
Click to collapse
Thank you for the reply. I should have said NOT rooted, D'oh!
On my mostly de-googled rooted Samsung tablet I download/install the Trichrome library (unfortunately it's google) from apkmirror, then install webview from Aurora Store.
I've used Bromite Webview on other devices in the past (manual method, pre Magisk module), and currently use Bromite (and Mull) browsers as my primary
This is now my reason to root my phone, unless there's a way to update without doing so.
Any suggestions?