• Off Topic

  • Banking apps have updated and are now complaining about root

I tried it again just now, it logged in fine and I could see my transactions, no complaints.

Version 126.01
com.grppl.android.shell.CMBlloydsTSB73
Exploit protection compatibility mode: off
Notifications: off
Permissions: network and sensors

Sandboxed Google play
GMS version 23.42.12
Same permissions as above

Pixel 7 Pro
OS build UP1A.231105.003.2023111500
Native code debugging: enabled

Running in the third profile on my phone. No PIN/password/fingerprint lock set. Developer mode turned off in the banking profile.

  • ntop replied to this.

    Foggy
    I tired to download the app and also have Google play service running but I am getting jailbroken..
    Tired again but same result
    Google pixel 8

      @luigi @DeletedUser28 @Foggy @ntop @galaxyegg

      Thank you for trying to debug this. What keyboard do you all use? There have been instances of an app causing trouble because it doesn't consider your keyboard to be safe to use. There are now 2 reports indicating that Lloyds does in fact work fine but also plenty of negative experiences. Also are you running it in the owner or a secondary profile?

        spring-onion I've been using a fork of OpenBoard, but I just switched to the GrapheneOS (AOSP?) keyboard and it gave the same error. Owner profile.

          Same problem, same banks. I've tried from the Play Store and Aurora and with without/with all permissions enabled - no luck. The reason I switched to these banks was that they're not app only - glad I did now - it doesn't bode well for other banking apps. Seems like there's some kind of dark Google witchcraft afoot!

          spring-onion

          I've tried with the stock GOS keyboard and gboard (network revoked).

            I’m using the stock GOS keyboard in a tertiary profile - there are no apps in it besides Aurora and Lloyds (not even the Play Store app)

            • [deleted]

            • Post #30

            spring-onion There have been instances of an app causing trouble because it doesn't consider your keyboard to be safe to use.

            That's a really dumb thing to do. Just provide your own in-app keyboard if you're so concerned about users using insecure keyboards.

              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.