crDroid is not an app but a custom ROM. It needs to be clean flashed, no need to go back to OxygenOS. And never lock your bootloader (unless the used ROM supports it).
The Revolut situation has nothing to do with Play Integrity, it’s only about custom ROM and root detection.
You mean the ECB? 
Revolut can do whatever they want, and it is for your safety to protect you from whatever bullshit they think is possible on a phone with a custom ROM.
Same here with Teracube2e Zirconia and the latest official (not community) eos for this device.
The app installs, starts properly. The the below message comes after attempting to open a new account.
Not rooted, developer options off.
install low level detector app and compare crdroid with e/os
I believe I might have had Cr droid before but deleted it.
As for complaining, kinda did that to Revolut before to no avail. You just get a standard reply that they don’t accept custom ROM. As for being shady that they kinda force you to use Android or iOS, tough luck since 99% of people use that and not even sure if it’s necessarily illegal or problematic in any way
Well, the ECB yes, but for example in France I’d say also Banque de France and the DGCCRF. Worth to try?
Yes @MasterOne, I am asking for it, because on the official website of crDroid (crDroid.net - How to install crDroid 11 for OnePlus 9 Pro (lemonadep)) they write the following in the installation instructions: “Warning: The provided instructions are for crDroid 11 running on OnePlus 9 Pro (lemonadep ). These will only work if you follow each section and step precisely.
Do not continue after something fails!”
That’s why I’m worried that if I install the crDroid ROM directly from the LineageOS ROM, Will I accidentally brick my phone :)? Thank you for your answer 
Usually a clean flash going from one custom ROM to another is enough, unless the two require different device firmware (don’t know about OnePlus, but for POCO phones the firmware can be flashed separately, otherwise reflash the full official ROM and then go from there). But that’s OT and should be researched at a place like xda-developers forum.
Hi @MasterOne yes you were right it works now thank you very much for your advice :). crDroid is even better than LineageOS, it has so many settings and customization options that no root or Magisk needs to be installed. And above all, all applications work and the whole system seems more stable and smoother than with LineageOS. I was able to switch from LineageOS Android 15 to crDroid Android 15 (on Oneplus 9 Pro) with no problems using these tutorials:
https://www.one-tab.com/page/bBQruXKDQVmOBRyh_jqu5Q
I couldn’t post more youtube links here because it was considered spam, so here is one link where all the links are (in the last two videos - in the first from 2:31 and in the second from 3:59) all links are in chronological order in which I also used them
Thank you :). If anybody have questions ask me
I really was hoping for a feedback from the /e/OS devs, because that issue definitely is not connected to Play Integrity, because otherwise the Revolut apps would not run on plain vanilla crDroid without GAPPS/microG.
The catch is, this issue really is a show-stopper for a lot of people (including myself and my whole family), because Revolut can just not be replaced by any other service, as it’s more than just a personal banking app, but also investing, for business and a crypto currency exchange (hence three different apps: Revolut, Revolut Business and Revolut X; all three causing the same issue).
As of now, it’s either crDroid or back to stock ROM. 
Then you should raise an issue in gitlab. That’s where the developers hang out, and where their work is scheduled & tracked
Hello guys, wanted to share my findings.
Apparently Revolut has blacklisted a bunch of build.prop properties.
I am on lineage, and I’ve commented all the “ro.lineage.*” props. App now is working as intended.
EDIT: As much as this solves the issue, it’s not something I advise the end user to do, because it might break OS specific things like updates.
This thing also involves having root access because you need to modify /system/build.prop
I did this only out of curiosity of finding a solution, but it is a thing that is up to the OS maintainers to decide to do or not. It might be out of discussion for /e/OS, graphene OS, lineage and other OSes, but I cannot tell because I am not a dev.
Already thought that it might be something rather simple!
Hello there.
Just to say that I have the same problem with e.os 2.7
Revolut didn’t want to work any more and ‘says’ that I must upgrade.
And then, the same message!!! >.<
As long as not implemented by the used ROM, finding the easiest way to temporarily make that modification is the goal. After all, you only need that modification in place to log-in with the Revolut apps, after which the modification can be reverted to its original state.
Statement from the GrapheneOS team concerning the resolution of this issue:
This will be temporarily solved by our next release until they begin enforcing a Play Integrity API check instead of specifically detecting and banning GrapheneOS via our
ro.build.userandro.build.hostproperties being set tographeneoswhich has been changed tobuild-userandbuild-hostwhich is what AOSP uses for reproducible kernel builds. The stock OS sets them to build bot information for the OS builds.
Can someone ping the /e/OS devs or post this to their issue tracker? I have no access and didn’t plan to create an account there.
Damned, I just tried to sign-up to create that issue myself after all but it won’t let me (“1 error prohibited this user from being saved: Email is not allowed for sign-up. Please use your regular email address. Check with your administrator.”). So anybody here who already has access or is willing to sign-up and post this resolution there?
Issue #8395 should be updated (as it’s not a Play Integrity issue) and a new one should be created.
I believe it does increasingly sound like Play Integrity …
In Overview of the Play Integrity API | Google Play | Android Developers App developers are addressed
You can also opt-in to additional information in the response including the volume of requests a device had made recently and signals about the environment, including the app access risk verdict and the Play Protect verdict. If anything is wrong with the verdicts, then your app’s backend server can decide what to do to defend against problems like abuse and fraud, misuse and cheating, unauthorized access, and attacks.
If I understand the rest of the page correctly, this means that App devs can ask for “any device information” at a very early stage … use or manipulate the information on their own (not Google) servers … then launch their “blocker” at any chosen event.
Play Integrity and simply build.props check are two different things.
The solution of changing ro.build.user and ro.build.host to build-user and build-host is confirmed to be working for the Revolut apps by the GrapheneOS team.
Now it’s up to the /e/OS dev team to swiftly implement these changes!
