From what I have been following (since I had it installed a long time on the Smartphone, meanwhile I cancelled their service), a lot (what is actually ‘a lot’ 
) of users complained and they didn’t care and just said ‘it is how it is now’.
1 Like
I managed to get it working on e/OS 2.9 on tetris through the following prop changes:
resetprop -d ro.lineage.version
resetprop -d ro.lineage.device
resetprop -d ro.modversion
resetprop -d ro.lineage.build.version
resetprop -d ro.lineage.build.version.plat.rev
resetprop -d ro.lineage.build.version.plat.sdk
resetprop -d ro.lineage.releasetype
resetprop -d ro.lineagelegal.url
resetprop -d ro.elegal.url
resetprop -n sys.oem_unlock_allowed 0
resetprop ro.boot.flash.locked 1
resetprop init.svc.adb_root stopped
resetprop ro.boot.verifiedbootstate green
resetprop ro.build.user nobody
resetprop ro.build.host localhost
resetprop ro.build.tags release-keys
resetprop ro.build.type user
Its possible not all of them are necessary. Don’t know if app will log me out on reboot.
3 Likes
I see the thread here was active as recently as 2 weeks ago: Play Integrity and Android's hardware attestation API (Revolut) (#8395) · Issues · e / Backlog · GitLab
Would it be worth updating it with your approach to getting this working? Maybe it would help them resolve it for others?
1 Like
Unable to create an e.foundation gitlab account. You can post it there if you want. Also, once logged into revolut you can restart the phone and revert prop changes and it still keeps you logged in and revolut working as expected. I do not pass any Play integrity attestations, so its probably not necessary for revolut to work.
I installed Magisk on a Teracube, made the resetprop commands you mentioned but ended up Revolut complaining about the device being root, probably because Revolut detekt Magisk. Did you do something else on top what you said ?
1 Like
Merci beaucoup, pour votre travail.
Je voudrais essayer, si ca fonctionne pour moi.
Pouvez-vous m’aidez, s’il vous plait ?
Est-ce possible de lancer ces commandes avec “adb shell getprop …” ?
Faut-il faire un “adb shell getprop …” pour sauvegarder les propriétés afin de les sauvegarder ensuite ? Quelle commande pour restaurer les propriétés ?
Grand Merci par avance.
j’ai installé Magisk et changer les props préconisé par jdcdp plus haut.
en revanche, je n’ai plus le même message d’erreur (avant) “malheureusement Revolut n’est pas pris en charge sur les appareils avec firmware sur mesure” → mantenant “revolut n’est pas rpis en charge sur les appareils débridés”.
J’ai du oublié qq chose ? faut-il desintaller magisk ?
commencez par essayer en masquant Magisk…
1 Like
Getting an error message in new ID creation on /e/OS Gitlab?.
If this was your experience you simply need to follow the advice there and ask in the forum here for @admin help.
1 Like
Magisk DenyList for the revolut app should do the trick. Or any other root hiding tool.
1 Like
fait : Magisk DenyList, Masquer Magisk
mais toujours la même erreur. Auriez-vous une idée, svp ?
After a reboot, Revolut is detecting a root device even if we just do the following: resetprop ro.boot.verifiedbootstate green
If we do all other commands listed by jdcdp except the verifiedbootstate one, the firmware is still considered custom.
just verified this point but not working : i ve always got “revolut n est pas prise en charge sur les appareils débridés”.
just after changing properties, is it necessary to :
*change root acces in magisk
*delete magisk app ?
- mask dev android options?
is it necessary to disintall revolut app ? install a specific version ?
You may need a dedicated Magisk module to hide the root
Or tweak the package installer signature