Maybe it is some handshake and as long as it was done before, you are good 
Edit: Guess my thoery was wrong.
Well, not sure what that’s supposed to tell me, because Revolut X is now working on my rooted crDroid phone (after I did the login on that older app version and then upgraded to the latest one), however it’s not working on /e/OS (same error as in the title of this thread with the old app version).
/e/OS
crDroid (rooted with Magisk Hide + DenyList enforced)
Can confirm that it does not function, even with the workaround of a previous version. I download the previous version, sends me to login but before being able to go beyond phone or email address, it requires an update. Said update will then give the Error message of the “Custom firmware”… wondering if there’s an intermediate version between 10.54 and 10.58, does anyone know about it?
Damned, that’s really bad! Still not sure what’s missing in /e/OS that it detects it as custom ROM because on my other phone with crDroid + Magisk it did not complain that it’s a custom ROM but because it detected root. The workaround by using an older version to log in and then upgrade was the only way so far to make it work (on both phones).
Wondering if an installation on a phone with relocked bootloader would help.
Nope! This is I did. It still doesn’t work. Furthermore, re-locking your bootloader will reset your phone to factory settings, which will erase everything…
1 Like
After updating to the official /e/OS v2.6.3, installing Revolut through the App Lounge still gives the same problem of not supporting custom firmware. Any fix?
Damned, there was a little hope that v2.6.3 would solve that. Unfortunately no solution as long as nobody knows what’s missing in /e/OS that makes the app determine that it’s running on a custom ROM.
Perhaps you could collect a log Capture a debug information from /e/OS.
Some logcat -- getting started
Problem with turning off the phone | stable version Samsung S7 - #46 by aibd
I was surprised what I found here. The problem there would seem quite hard to work around …
if I understand correctly this is a method for checking the app against a register held by Google
… but in an email reply from the company they appeared committed to using Google to validate the device.