The subject says it all.
Please tell us, which app and which version specifically.
I have the same problem with the Danish banking app MobilePay after updating to version 8.23.0.
Anyone succeeded in solving this issue?
MobilePay, as per the subject. Version is 8.23.0, same as the other poster.
Hello,
I experienced the same problem on my FP5 after the app was updated.
I simply cleared the storage of the app (Settings > Apps > MobilePay > Storage & cache > Clear storage) and logged in again.
Maybe this will work for you too?
Same problem
FP5, MobilePay, MItID
Vivaldi browser or Samsung
Made it work on 2.8, stopped working on 2.9. and not working now on 3.01.
Have cleared storage. Get past authenticatin by MitID, but is sent back to MitID llogin page.
If I minimize that, the MobilePay page is behind and sys “Approval faild try agin later”
See attatched in danish. (the minimized on the lower right)
It seems that MobilePay (or MitID) ignores the user’s default browser (Vivaldi in my case) during MitID authentication and uses /e/os’ default browser instead. Something’s rotten anyway. I managed to get past the error mentioned earlier in this thread, by uninstalling the default browser, but it required some effort.
Disclaimer. I installed the /e/os myself on a Samsung a52s so the bootloader is unlocked. I would suspect this “hack” doesn’t work if you bought a fairphone with /e/os preinstalled. But don’t know. I don’t Think it would hurt to try.
Please search the internet for “abd android usb” and you’ll probably find some more detailed instructions for for step 1 and 2 below.
- Enable developer tools on the phone and activate USB debugging.
- Connect the phone to a Linux PC (this can also be done on Windows).
- Using the adb program, I found the name of my phone:
adb devices
- Then I connected to my phone:
adb -s [device] shell
- I ran the command:
pm uninstall -k foundation.e.browser
- Exited the shell:
exit
I restarted the phone, and then I was able to get MobilePay to work. However, I used MitID authentication by scanning the QR code from my iPad.
Succes!
Have collected a guide in danish, as this is probably only an issue in Denmark/Scaninavia (copy and save as markdown (md) file):
Fjern eller deaktiver standardbrowser i /e/OS pĂĄ Fairphone 5 for at fĂĄ MitID og MobilePay til at virke
Denne guide viser, hvordan du fjerner eller deaktiverer den indbyggede browser (foundation.e.browser) i e/OS pĂĄ en Fairphone 5, sĂĄ apps som MitID og MobilePay tvinges til at bruge en anden browser (fx Vivaldi eller Samsung Internet).
FormĂĄl
- OmgĂĄ problemer med MitID-login i MobilePay og lignende apps
- Tving systemet til at bruge en anden browser end den indbyggede e/OS-browser
Forudsætninger
- Du har selv installeret /e/OS (bootloader er lĂĄst op)
- ADB er installeret pĂĄ din Linux-maskine (Fedora)
- Du har adgang til terminal
- USB-debugging er aktiveret pĂĄ telefonen
Trin-for-trin guide
1. Aktivér udviklertilstand og USB-debugging
- GĂĄ til
Indstillinger→Om telefonen - Tryk 7 gange på
Build-nummerfor at aktivere udviklertilstand - GĂĄ til
Indstillinger→System→Udviklervalg - Aktivér:
USB-debugging
2. Forbind FP5 til Linux og kontroller ADB
Tilslut telefonen med USB-kabel. Kør:
adb devices
Du bør se:
List of devices attached
AB1234567 device
Hvis du bliver bedt om at godkende forbindelsen på telefonen, så tryk “Tillad”.
3. Fjern eller deaktiver e/OS’ indbyggede browser
Browseren foundation.e.browser er ofte installeret som systemapp, og derfor kan du enten afinstallere eller deaktivere den:
Ă…bn ADB-shell:
adb shell
Forsøg afinstallation:
pm uninstall -k foundation.e.browser
Hvis du fĂĄr:
Failure [DELETE_FAILED_INTERNAL_ERROR]
… så fortsæt med deaktivering i stedet:
Deaktiver browseren:
pm disable-user --user 0 foundation.e.browser
Afslut shell:
exit
4. Genstart telefonen
adb reboot
Alternativt: Genstart manuelt.
5. Installer og sæt ny browser som standard
- Installer fx Vivaldi eller Samsung Internet via Aurora Store
- GĂĄ til
Indstillinger→Apps→Standardapps→Browser-app - Vælg din nye browser som standard
Test
- Prøv MobilePay og MitID
- Hvis de virker, er det fordi systemet nu bruger din nye browser i stedet for den fjernede/deaktiverede
foundation.e.browser
Gendan browser hvis nødvendigt
Hvis du får brug for at gendanne browseren, kør:
adb shell cmd package install-existing foundation.e.browser
Senest opdateret: juni 2025
Testet pĂĄ: Fairphone 5 med /e/OS 3.01
Bidragydere: Søren Thaulow
Licens: Fri brug og deling – gerne med henvisning til e/OS-forumtråd.
Hi, Hello, Good morning,
No ? Guys, this is a self-help forum, we’re here to potentially help you, we’re not at your service…
Thanks, but no. I still get the “woops something went wrong message”. My NDR SH app (will create a separate post) has stopped working as well. Assuming that it has something to do with e os not satisfying the app requirements for the latest versions of apps.
Please explain your post.
1/ Be polite. It’s always nice to say hello and thanks for your help.
2/ Please describe the problem a little instead of saying, it’s all in the title.
What is so hard to understand in my previous message?
Bug reports are in their nature, a bit on the terse side.
Civilization has overcome nature. Just be polite, nothing more. People are here to help and with every word, you affect anyone here in this thread because they are reading it.
Thank you!
We’re on a community site, so a minimum of information and politeness is required. If you want to file a bug report, there’s Gitlab for that…
I can confirm this works with wifi-debugging on Fairphone 3+.
I can confirm this also works for me. Thanks for the writeup. ![]()

After a week with MobilePay I could not login anymore. After a few attepts I got this message: “MobilePay does not support rooted devices”.
I delete app and reinstalled. Now it is working again (maybee).
Anyone with simlar expirience?
Yep, I get the same error today “rooted” device not supported, I haven’t tried reinstalling yet.
Hi everyone,
good to see we’re once again working together to get around this “security” check.
FYI: This comment does not contain a permanent solution, but a potential temporary one.
tl;dr: Uninstall MobilePay, reboot phone, install MobilePay, log-in with MitID etc… works again - for a couple of minutes.
I’m sporting a Fairphone 5 on which I previously was also not able to log-in to MobilePay with MitID. This was resolved with help from @oliveradams who provided the uninstall-default-browser trick in this thread - thanks again!
So, after applying that fix I now have another default browser (Brave) and the default browser removed. MobilePay worked great for several months. That changed after a recent MobilePay update, after which I got the same “Security check failed (…)” message as @Thaulow above (while still on /e/os 2.9).
Today I updated to /e/os 3.0.1 and rebooted my FP5, after which a lot of apps also updated - including MobilePay. Full of new hope, I tried logging in to MobilePay again… Same error… A little disheartened I gave it one last shot after all other app updates had completed:
- I uninstalled MobilePay
- I rebooted once more (because, “have-you-tried-turning-it-off-and-on-again” actually works sometimes)
- I re-installed MobilePay (from the /e/os App Lounge)
- I logged in (needed to go through SMS activation + MitID authentication again)
- I was in - and able to make a transfer

Unfortunately my happiness was cut short as the red text of doom once again appeared after a few minutes. I was able to snap a quick screenshot before closing the app and getting “locked out” again:
This error hints at the initial “authentication” login potentially being different from subsequent “refresh” ones.
I’m sorry I can’t provide a permanent solution, but I hope that this additional info may help nonetheless in finding one.
I’ll be watching this thread, and hope that one of you figures it out, or will update it if I’ll be lucky enough to.

