• Off Topic

  • Banking apps have updated and are now complaining about root

Here are my steps to having it working:

  1. Create a new profile
  2. Go to ‘install available apps’. Select Aurora Store, Google Play Services, Google Services Framework. Leave other profile settings at defaults
  3. Switch to that profile, elect to ‘set up now’
  4. Start, English UK, allow location, skip fingerprint, skip PIN, skip restore, start
  5. Start Aurora, accept all the defaults, grant permissions, login as anonymous
  6. Search for Lloyds Bank, select ‘Lloyds Bank Mobile Banking’, install (now it’s version 127.01)
  7. Open the Lloyds Bank app, it briefly says ‘authenticating your device’ and then asks you to login or open an account.

When I did this flow and logged in to the app a few days ago, it worked. I have not tried logging in on the new profile I made just now to write the above, but it evidently passed the ‘authenticating your device’ check.

Can folks who are having problems try these steps and see if you get different results? No account needed to try them.

  • ntop replied to this.

    Hi all, I just hit this issue too, so thought I'd do a quick reply. I'm won't go into technicalities, but I basically run two phones with separate profiles for 'Google apps'. I install them through Aurora, have never logged in to Google directly. Bank of Scotland App on my Pixel 5 suddenly started with the 'rooted' message. It wont play at all. I then tried my Pixel 6, which has a similar setup, it's working fine so far.

    I notice Aurora is suggesting a Bank of Scotland updated to version 127.01. which is the borked version on the Pixel 5. The working version on Pixel 6 is 126.01.

    So looks like the Lloyds banking world has decided to turn the screw. Is this part of the Farage fandango? [not a political comment, just the way things are going with these banks, as already mentioned above regards fiat v crypto]

    Also have a Nationwide app, so far working fine. Looks like I'm gonna need to get away from Lloyds Banking Group.

    The Marriott app just joined the fray and throws a "Magisk detected by app" error. Like mentioned above, I think it's a generic error looking for something on the phone. I have the same issue on my other profile that has Google Services installed.

      Foggy
      Hi Thanks for taking time for the steps.
      I did below steps:
      Create a new profile
      Go to ‘install available apps’. Select Aurora Store
      used gos app to install "google play services" in sandboxed"
      Start Aurora, accept all the defaults, grant permissions, login as anonymous
      Search for Lloyds Bank, select ‘Lloyds Bank Mobile Banking’, install (now it’s version 127.01)
      tired to log in but same result and i didn't get "authenticating your device"

      Thanks

          @ntop

          ntop Interesting. So you don’t get ‘authenticating device’ but you get a ‘login or open an account’ screen. When you go to login what happens? Normally it asks for user id and password, then a second screen asking for 3 letters of security information. Do you get those screens or does it fail before you’ve entered the full login information?

          (On first time setup they also called me and asked me to enter the code shown on the screen into the phone call. Not sure if that’s because I’ve not used mobile banking with them before)

          • ntop replied to this.

              Foggy
              Thanks for reply

              I don't get to the second screen with codes
              Enter username and password then get about device is rooted..

              Halifax works fine but only Lloyd's

                When you receive a warning from your banking app indicating that your device may be insecure, jailbroken, or rooted, this is usually due to a SafetyNet/Play Integrity API issue. Specifically, your device fails to pass MEETS_DEVICE_INTEGRITY.

                For more details, see the planned feature on this topic at the GrapheneOS issue tracker: Issue #1986.

                As of now, there are no direct solutions available to users. However, you can help by contacting your bank. Inform them of this issue and suggest they refer to the GrapheneOS Attestation Compatibility Guide for their developers, available here: Attestation Compatibility Guide.

                • ntop replied to this.

                  akc3n
                  Thank you so much for the update. Appreciated

                    bookreader The problem with that model is you always need a trusted third-party to custody the gold for everyone, and that trust has been broken time and time again throughout history.

                        I can confirm that the app version 128.02 is also not functioning, displaying the same error: "Sorry, you can't use this app as we've detected that your device has been jailbroken/rooted. You can still use our Mobile Banking or Internet Banking sites via your web browser."
                        As previously mentioned by akc3n, this is due to an API issue where your device fails the MEETS_DEVICE_INTEGRITY check.
                        The only recourse is to persistently contact your bank's technical support, urging them to address the issue by adhering to GrapheneOS's Attestation Compatibility Guide - highly unlikely that they will do that as they don't care about our existence.
                        It seems that in the future, they may restrict access to only Google Chrome on a Windows mobile phone :)))

                          • [deleted]

                          • Post #43

                          pacemaker Why not Embarras them on Twitter?

                            mhbcrypto Why do you need a 3rd party to store your gold? I don't. The 3rd party storage problem comes when you are dealing with proxy currencies. I.e. paper money that represents gold held by a 3rd party.

                              I hadn’t started Lloyds since posting in this thread and now I get, when it does ‘authenticating your device’:

                              9300101: Sorry, we have de-registered your device as we’ve detected it’s been jailbroken/rooted. You will not be able to use the app but you can continue to use our mobile site.

                              If I ‘try again’ I get:

                              App launch failed
                              Sorry, we’re having a few technical problems. Logging in again may fix the issue, but if this doesn’t help, please try again later. (7)

                              If I try the app installed in a blank profile as per the instructions above it asks me to login (didn’t do it on that app before) then a similar message (9300100, “Sorry, you can’t use this app as we’ve detected that your device has been jailbroken/rooted…”

                              So looks like I fired whatever tripwire there is in the app.

                              • ntop replied to this.

                                Foggy
                                Let me know if you find a fix pls

                                Thanks

                                  I ended up extracting Lloyds apk version 126.01 (installed from Aurora and works fine) from my Pixel 7 Pro to install it on my new Pixel 8 Pro as Pixel 8 Pro gets the latest, non-working version from Aurora by default.

                                  So currently running the 126.01 and will not update for time being.

                                    Volen
                                    What's your setup pls as I tired 126 but fails

                                        ntop

                                        The app is installed in the work profile (Shelter) with Play Services installed. No other specific config.

                                          DeletedUser28
                                          Starling Bank app has been working for me ever since I joined GrapheneOS probably 2-3 years ago. Exception being the Google Pay functionality. I contacted them in 2021 to confirm whether they use SafetyNet but they refused to divulge that information. I don't know whether I should contact them pro-actively and point them to the attestation page, as it's been working well so far.