I just spoke to my bank a second time and this time the opinion was that the problem is due to the Custom ROM, no other customers had complaints this week and it is in fact the banks job to deal with such issues, not the developers (Atruvia)… They don’t have a solution but will get back to me next week.
To me that seems unlikely since the OS hasn’t changed within the last week but the app has. But what do I know.
As explained in this post, there are several reasons why a banking app refuse to start.
A rooted device or unlocked bootloader normaly be treated as unsafe environment.
It is running again!
The last 4 days I had no chance to use the App SecureGo+ of the ‘Renault Bank direkt’ (version 4.1.3). But today I have tested again - and it works again. My system is a Fairphone 3+ with /e/OS 3.1.4.
That’s strange since neither e/OS nor your app has been updated. Did you change anything else?
No, I have nothing done.
I’ve tried to summarize the feedback in this thread so far. For me it keeps unclear, what’s the reason is. Official builds with locked bootloader have the issue too.
Fairphones seems not to have this issue. Google Pixel even have it with official builds and locked bootloader.
App doesn’t work:
| Reporter | Phone | Android | e/OS/ | official / community | bootloader |
|---|---|---|---|---|---|
| @eos.b02pz | Pixel 5 | 3.1.4 | locked | ||
| @albigdd | Pixel 7 (panther) | 13 | 3.1.1 | official | locked |
| @Tentos | OnePlus 6 (enchilada) | 15 | 3.1.4 | not locked | |
| @asterix | Pixel 5 | 3.1.4 | |||
| @Sunfish | Pixel 4a | 3.0.4 | |||
| @msp | S5e (gts4lvwifi) | 3.1.4 | community | not locked | |
| @hakunamatata | Pixel 5 | 13 | 3.1.4 | offical | locked |
| @SaMa | Pixel 6a | 3.1.4 | not locked | ||
| @mathias.schmidt | S10 (beyond1lte) | 13 | 3.1.4 | community | not locked |
App still works with 4.2.0 / 4.2.1
| Reporter | Phone | Android | e/OS/ | official / community | bootloader |
|---|---|---|---|---|---|
| beedaddy | FP6 | 3.1.4 | official | locked | |
| msp | FP4 | 3.1.4 | official | locked | |
| MiSta | OnePlus Nord (avicii) | 12 | 3.1.4 | official | not locked |
| MiSta | Galaxy A5 2017 (a5y17lte) | 11 | 2.1 | community | not locked |
| ingolf | FP6 | 15 | 3.1.4 | official | locked |
| Sunpower | FP4 | 3.1.4 | official | locked (?) |
Wow, man, A for effort 
The only thing I notice so far is that the devices that don’t work with the app anymore are mostly (6/8) older (<=2020) than the devices that have no problems, except for Pixel 6a and 7.
But there is @joojoo whose FP3+ is working again now for unknown reasons. So 2/6 phones now working (again) are older.
Someone over at the iodéOS forum writes:
“VR SecureGo Plus”: received update from support of my bank: with 4.2.0 a too sensible security component was introduced. It was removed with 4.2.1 (that was potentially the reason why it was so quickly published after 4.2.0). Nevertheless even 4.2.1 has an issue on (at least) iodeOS and a ticket was created now. Hopefully soon 4.2.2 will be available and usable again.
Well… ‘me too’. Does not work even with updated Version to 4.2.1
Samsung S10 (beyond1lte) with /e/OS Version 3.1.4-t-20250919528048-community-beyond1lte, unlocked.
Updated to SecureGo+ 4.2.1 (421005) and it is still working on my OnePlus Nord (avicii) with /e/OS 3.1.4-s-official (A12).
Missed to mention in my first post: Bootloader is unlocked!
Just for test purposes I installed SecureGo+ 4.2.1 (421005) on my old and not more maintained legacy Samsung Galaxy A5 2017 (a5y17lte) running /e/OS 2.1-r-dev (A11, community) with unlocked bootloader and what a surprise: Also on that old phone the App seems to work correctly.
Oh no literally same situation here.
Pixel 5 redfin
A 13 offical
Securego plus v.4.2.1 from app lounge
It used to work until a few days ago. How does this picture tan work at GLS bank?
Ok, I may sound a bit harsh, but if you have a problem with the sh*tty SecureGo Plus app I recommend exchanging your bank with N26. Why? Because they do listen and change their app according to user requests.
I am (still) having accounts on VR bank and therefore need to use this app. I installed it on a pretty old tablet with Lineage 11 and Magix root. Upto 4.2.0 everything worked well, more or less. Every now and then I had to re-check the app on the magix exclude list. After 4.2.0 this did not work any longer, so I de-installed magix, and it worked again. For me this (and the old lineage) is no problem as the tablet is only used for exactly this banking app.
But my real banking is taking place on N26 with latest e/os and every google feature disabled and de-installed. In an older N26 app version this was a problem because a notification took place every time one transfered money. I wrote them and explained that I dont want to have google on my phone for privacy reasons. About a month later a N26 app was released which did not use google notification any longer and the transfers are immediately checked by entering the pin. This is how I expect work from a true banking service provider. Contrary to that Atruvia never made a useful statement about privacy and complaints, only bad PR blabla.
Surprisingly I just received a message from Atruvia:
We have been able to narrow down the problem and will release an update shortly.
Unfortunately, I cannot give you an exact time yet.
As soon as the update is available, you can update your app as usual.
Now really, this is exactly what I called PR blabla. What is the basic saying here:
Now what is your expectation about any app you consider using? That there will be continuous updates coming somewhen. A simpler and more fundamental message is hardly thinkable. In fact they said nothing.
Sorry @skraw, even though I partly share your view, I don’t see it that way in the case of Atruvia:
The security requirements for banking apps are very high, and there are certainly many things to consider that we are not even aware of. Not all rooted devices or devices with unlocked bootloaders are actually insecure, but it is one of many indicators that suggest this may be the case. And if some implementation details of a CustomROM are different to the mainstream Androids out there then it is always possible that some additional security checks will trigger the alarm and the app will block.
App developers must constantly make compromises to ensure security on the one hand and that the app works on as many devices as possible on the other.
I’m absolutely no fan of all these banking apps at all! I prefer to do my banking stuff on a PC and I use a ChipTAN generator for authentification as often as possible. But for some tasks (e.g., credit card transaction authorisation) they are often mandatory.
That’s the actual problem: Banks need to reconsider whether it makes sense to force their customers to use such apps due to the lack of alternatives! They should always offer reasonable alternatives for such tasks. We, the customers, should regularly complain to the banks if this is not possible. In my opinion, the developers of banking apps are the wrong people to address such complaints to!
The SmartTAN Photo doesn’t use the phone. You need a little extra device where you insert your banking card (TAM-Generator). When the GLS-Bank requires a TAN, it shows a colourful QR-code-like dot pattern on the device you’re working with. Then you use the SmartTAN-devise to capture this code, and it shows the generated TAN.
So absolutely no phone app required. When I called the GLS-service they switched the TAN method from SecureGO to SmartTAN for me during the phone call. Otherwise, I wouldn’t have been able to contact them and change it myself.
I keep a ChipTAN generator around as well, but AFAIK, at least at the Berliner Volksbank, ChipTAN only works for SEPA and Internet Banking, not for EMV transactions with Mastercard or VISA, so I can’t use my card to pay online if SCA is required. That requires either the app, or… shudder… SMS.
I tend to agree but in this case I take their message as an admission of guilt. I spoke with some moron from my bank (Umweltbank) and he spoke with some moron from their “technical department” and they said it was completely due to the Custom ROM, nothing they could ever do, the app works perfectly fine blabla. So the message from Atruvia was a change in tone for me and I take that. Knowing the app still doesn’t work…
Also checked on my side (4.2.1) with FP 5 on 3.1.4 (Android 13) with locked bootloader - also need it for Umweltbank - and at least for me its working
Really strange that it works for some and for other not