SecureGo Plus worked fine until I updated the app to version 4.2.0. The app now closes and the browser is opened forwarding me to the webpage of the maintainer of the app stating “For security reasons the banking app was closed”. I suspect that the app assumes that the device is rooted, which it is not.
The link that forwards me to the webpage of the maintainer reads: https://ka-app.vr-bankingapp.de/services_online/mobile_auth/exit/dispatch?action=Rooting&reason=0&manufacturer=Google&model=Pixel+5&AndroidVersion=33&shieldVersion=8.0.1&root=40AFAADB&type=plus&flavour=wl
That is why I think the app assumes the device is rooted.
To be honest I am not sure as I used the install wizard and followed the instructions, so I guess the bootloader is locked. Is there a way to check this?
You can reboot into fastboot mode. The last line on the screen, “DEVICE STATE - locked”, would state that it is locked. You can also (in fastboot mode) use the command fastboot getvar unlocked which would tell you whether it is (un)locked.
I have the same problem with VR SecureGo Plus 4.2.0.
Device Pixel 7 (panther)
e/OS/ release 3.1.1-t (latest official - 3.1.4 is not available)
Bootloader locked
Some weeks ago, I had a similar problem with the Bank Norwegian app with version 5.4.151. In this case, I downgraded the app and everything worked again. Of course, this can’t be a solution.
I have also the same problem with SecureGo Plus 4.2.0.
Device: OnePlus 6 (enchilada)
/e/OS 3.1.4-a15
Bootloader not locked (not lockable)
Device rooted (however, the previous version 4.1.5 works fine if it is added to the Magisk white list).
I am lucky because I can use my iPad with SecureGo Plus to confirm banking transactions, but I know that not everyone is in this comfortable situation.
It seems that a bugticket needs to be opened in the /e/OS GitLab if some devices with locked bootloader no longer work?
SecureGo plus 4.2.0 (420015) works without problems on my OnePlus Nord (avicii) with /e/OS 3.1.4-s-official (A12).
I’m using the non-branded version provided by Atruvia itself.
There are several bank specific variants of the SecureGo+ App available, e.g., Sparda SecureGo plus, VRSecureGo plus… They all are developed by Atruvia. Maybe there are small differences concerning the strictness on handling an unlocked bootloader.
You mean my downgrade of the Bank Norwegian App? I’ve just installed an older version from the Aptitude store. After his, I had to identify again in the app.
With the VR SecureGo Plus I feare the same. But in this case, I would have to wait for a letter by my bank. I’ll hope to avoid this.
The feedback in this thread is quite diverse. On some phones, it works on other not. It seems not to depend on locked/unlocked bootloader and not on the Android version.
And the non-branded version of Atruvia behaves the same Unfortunately. Thank you @MiSta for this hint.
Aurora Store also offers the possibility to download older versions of an app (if still available) from the Google Play Store. It seems that the version 4.1.5 has the version code 415004.
Fortunately, version 4.2.0 (420015) of de.fiduciagad.securego.wl seems to still work on my fp6 with 3.1.4-a15-20250915526528-official-FP6 and locked bootloader.
Yes, app downgrades are usually not possible in Android. You may have to uninstall SecureGo Plus, install version 4.1.5 and then request a new registration of your smartphone/app at your bank.
I would love to give you better news. However, I also could not restore the app and its configuration (i.e., link to bank account) from an earlier backup with NeoBackup. Secure information is probably stored in the security chip (or something similar) of your smartphone and cannot be read. (This is actually a feature, not a bug: Secret information is only used in the trusted environment of the chip to sign transactions etc. and does not leave the chip. Hence, the secret information cannot be hacked.)
I have Google Pixel 4a with 3.0.4 and SecureGo Plus 4.2 and it also doesn’t work.
I called my bank (GLS) a minute ago and explained this problem to the guy who’s specialist for SecureGo. Clear answer: From version 4.2 on SecureGo will NOT work without Google anymore. No chance.
I let him switch to SmartTAN Photo and that works.
Not my preferred solution but it works.