Hi. It looks like all barclays apps are not working on LineageOS any more. They find the phone rooted all of a sudden. Does anyone know of a solution??
Mine started playing up with the update on the 29th. But not sure if this is a Lineage only issue. Many users in the play store comments, saying the same thing. Can't get any further than the initial splash screen. No error codes or anything.
My girlfriend has her Oneplus One with LineageOS and since the last Barclays app update last week version 1.48, the app get always stuck during the loading screen. It was working perfectly fine. Updated LineageOS to latest version but no change, cleared Barclays app cache and data, still no luck. Cleared cache partition, no change.
The phone is not rooted, so Barclays app simply became incompatible with LineageOS since the last update on their app.
Yup same problem, I spoke with Barclays on the phone and on twitter....got nowhere.
my GF is trying support with Barclays over facebook, was told to call the support line after a while troubleshooting
Make sure she mentions the Play Store comments, to show this is not an isolated thing.
she called support and they mentioned they know already about this problem and are working to resolve it
Same issue here. Thought It was a ROM issue, thanks for clarifying.
Pommy192 said:
Same issue here. Thought It was a ROM issue, thanks for clarifying.
Click to expand...
Click to collapse
Not necessarily, several other phones with their original firmware are having the same issue.
Just to ad I found this thread for the same reason
Latest LineageOS , LG G4, Launch barclays it asks for call permissions - Granted, it then hangs on Barclays Logo
I know it doesnt work with root access and always moans i dont have AV installed when I do (maybe its looking for kaspersky that they promote)
I'm on the latest LineageOS update, LG G4. Even did a full factory reset with no luck.
I think this will not change, barclays has not updated their app in a while since this problem started and I reported a few times it to them, perhaps I'm the only one doing it
I've tried a couple of times, but they dont seem all that bothered. They are not even bothering to address the comments on the play store.
Gigabit88 said:
I've tried a couple of times, but they dont seem all that bothered. They are not even bothering to address the comments on the play store.
Click to expand...
Click to collapse
I've found it much easier just to use the Barclay's Mobile Banking site via a browser, they're not interested in fixing the app for rooted users.
It's secure and requires you set up a secret word, which during login, will ask you for a couple of letters from in a random order, over and above your passcode and form account details.
https://bank.barclays.co.uk/olb/auth/MobiLoginLink.action
mines not even rooted though? I lost root with the image, it normally moans about root but this is different I stuck on another image and it worked fine grrr
---------- Post added at 11:11 AM ---------- Previous post was at 11:01 AM ----------
This may fix it - let me know
https://www.reddit.com/r/LineageOS/comments/6vi5bp/heres_how_i_got_the_barclays_app_to_work_on_my/
So the new update to the Barclays app now thinks my LineageOS is rooted, when its not.
Gigabit88 said:
So the new update to the Barclays app now thinks my LineageOS is rooted, when its not.
Click to expand...
Click to collapse
same here. was working fine (on oneplus one lineage os 14.1), then barclays update the app to 1.48 and it started hanging at the splash screen. barclays app has been updated again to 1.52, but now thinks my phone is rooted.
Yup, Barclays have blocked LineageOS users on purpose. Why? Because they hate root access and in May an update to LineageOS could successfully hide root from any application (barclays included) as it changes the permissions on the su binary.
More details about that here:
https://lineageos.org/Changelog-9/
Thus, what did Barclays do? Well because they cannot check if device is rooted or not reliably with LineageOS, they decided to block the OS all together so now it simply checks if the device is running LineageOS.
It sucks, but it's the way it is. I've simply removed the Barclays app from my phone - A choice between Barclays app on Stock Rom running old android version and LineageOS with latest security updates? Well LineageOS wins.
The new barclay's update says "We're working to fix the problem with our app detecting some Android devices as rooted". They might change something for someone, can anyone confirm that this update fixes something? I would not be able to test it until tonight when arrive home, since it is my gf phone the one with lineage.
Cheers!
Nope, still detecting as rooted.
Nexus 6 - Lineage 02/02/2018
Related
Can't believe there aren't 10 threads about this for the G3 already. I've learned what everyone has who's rooted and trying to install Android Pay. No deal. And this really sucks, because I was looking forward to this.
I tried to install it from Google Play, but there's no install button. It says device is not compatible. So, I followed advice I've found on line. Installed Root cloak, cloaked Busybox and Wallet, and I disabled Superuser. Still no install button.
Next, I downloaded the latest Google Play Services and Android Pay APK's and installed them. Now when I try to open Android Pay, I get the error, "Android Pay is not Available". I'm not running xposed, BTW. I have an ls990 on Candy5.
I expected to run into problems loading my cards that are already saved on Wallet or when I go to use it, but I didn't count on not being able to install and open it. Has anyone with a rooted G3 been able to? If so, how?
I just unchecked "Enable Superuser" in SuperSU Pro, and Pay installed fine after that. Then I just re-enabled Superuser.
That's one of the the things I did, but it doesn't work. hmmm....
I've tried everything. Nothing works.
---------- Post added at 04:23 PM ---------- Previous post was at 04:22 PM ----------
Disable SU, Root Cloak, some Device hider thing... Nothing works.
i have tried but not work
i have tried but not work!
Nothing I've read has helped. Most rooted users can't load cards. I can't even download the app from Google Play, and the apk installs but won't open up. Frustrating!
It updated automatically for me. But I can't load a card either now. This is really frustrating because use wallet everyday to make purchases.... WTF Google! I hope someone can fix this and soon. I've tried every work around so far
Rooted users on stock ROMs have had various degrees of success with Pay. Those of us with AOSP ROMs are almost universally getting nowhere.
Bramton1 said:
Rooted users on stock ROMs have had various degrees of success with Pay. Those of us with AOSP ROMs are almost universally getting nowhere.
Click to expand...
Click to collapse
When I get a chance, I'll restore an old nandroid of Barepop and see how it goes. Here and on G+, it seems I've seen people on AOSP at least get to the point where they're adding cards. This is the first time I recall seeing a line drawn between stock & AOSP. Worth a shot. Thanks!
Can't get this to work, stock or skydragon
I have been rooted with SuperSu/Suhide since September and now am using Magisk 14.2 with the October security updates (flashed image and removed "-w" to retain data). I pass all of the safetynet checks from various apps under both conditions. I am having a problem adding cards to Android Pay. I add the card, verify the CVC, agree to the terms, and then get a popup saying that Google Play services has stopped. It does not finish verifying the card and clicking on the card results in the "Google Play services keeps stopping" error. This has happened since the September security update (did clear user data then) and I cannot find what may be causing it. I did edit the hosts file and build.prop when using SuperSu/Suhide, but now only the hosts file with Magisk. Anyone have a similar issues or know of solutions? Thanks.
So no one else has experienced this? Does Android Pay and Magisk work fine?
:good:
mwalt2 said:
So no one else has experienced this? Does Android Pay and Magisk work fine?
:good:
Click to expand...
Click to collapse
Not sure if it's related, but I updated to September's Oreo build using fastboot flash of the factory image. I removed -w to save data. After this I was no longer able to purchase apps in the play store, always caused the play store to crash. Free downloads worked fine but paid transactions never went through. I ended up flashing the factory image and wiping data and all is well. I am unrooted.
mwalt2 said:
So no one else has experienced this? Does Android Pay and Magisk work fine?
:good:
Click to expand...
Click to collapse
I have the same issue can't buy apps. Get to the point of buying it and get FC. Doesn't matter if I'm rooted or not. Tried magisk and suhide
Not sure what could be the exact reason. I had google play services stopped problem on my Note 3, but it was not rooted. I followed a guide on Mobipicker, that worked for me. You can also refer, but not sure that will work for rooted devices.
I know this is old, but I found this thread because I had been having the same problem...I found the fix for my situation and figured I'd share in case anyone else came across the same issue... Everytime I tried to verify my card Google play services stopped...
I remembered that it checks that you have a secured lock screen when you set up at some point...I turned off smart lock location, on body detection, and face... Worked without any problems...
I'm at home, so I'm not sure if smart lock was preventing it from working just by being turned on, or if it thought I didn't have a secured lock screen because smart lock was triggered by me being at home...
Hi all, I recently rooted my phone and for some reason Netflix won't launch at all. It just hangs on the Netflix logo. If I reninstall the app on first launch the app will force close and then after re-lauch it will once again hang on the Netflix logo. I've cleared the cache and deleted any folders relating to netflix. I'm not sure what to try next or if anyone has any advice on how to fix this that would be amazing. thank you!
Edit: I've found a solution to this problem! Follow this guide here:
https://forum.xda-developers.com/ap...le-netflix-t3708126/post74586497#post74586497
After downloading and installing the old April 2017 Netflix app simply lauch
The app and sign in. After you have signed in update the app on Google play
And you should be good to go! Hope this helps anyone else with the same
Issue ?
Netflix doesn't work on rooted deviced it checks if your device is rooted and if so won't work.
Roxas598 said:
Netflix doesn't work on rooted deviced it checks if your device is rooted and if so won't work.
Click to expand...
Click to collapse
I've had Netflix work on every previous rooted phone i have had, is this just a Razer phone issue? Even hiding the root from Netflix in Magisk doesn't seem to do anything.
camy25695 said:
I've had Netflix work on every previous rooted phone i have had, is this just a Razer phone issue? Even hiding the root from Netflix in Magisk doesn't seem to do anything.
Click to expand...
Click to collapse
The bootloader needs to be locked. I would not advise trying it unless the phone is 100% stock as there have been issues mentioned in the past.
camy25695 said:
I've had Netflix work on every previous rooted phone i have had, is this just a Razer phone issue? Even hiding the root from Netflix in Magisk doesn't seem to do anything.
Click to expand...
Click to collapse
It's either root or bootloader it checks but it's only something they started doing months ago. pokemon go does it too.
Roxas598 said:
It's either root or bootloader it checks but it's only something they started doing months ago. pokemon go does it too.
Click to expand...
Click to collapse
Damn, that's discouraging. No wonder why I've been holding off rooting this device. I'm not use to a/b root anyway. Before my razer, I had an s5 for many years so I know a lot of things have changed since then.
Hey guys just updated to the latest magisk manager and magisk root on my pixel a few days ago but i just noticed that my Google pay had removed my bank card. Checked magisk manager and went into the magisk hide list and nothing was checked so i manually checked necessary apps including Google pay. Now even after that and after a reboot and clearing data of Google pay AND despite magisk passing a safetynet check Google pay still refuses to accept my bank card. Should i roll back to an earlier version when it was working? Is there something broken in the lastest magisk manager?
Thanks in advanced.
February security update
Magisk manager 7.0
Magisk 18.1
ElentalX-P2-2.09
No idea why you have the problem but I just made a purchase today at the supermarket Price Chopper...
Here is my setup:
CyberpodS2 said:
No idea why you have the problem but I just made a purchase today at the supermarket Price Chopper...
Here is my setup:
Click to expand...
Click to collapse
Thanks so much for confirming must be a problem on my end. I've been getting random freezes at night which had me waking up with no alarm. Guess it's time for a clean install because obviously something went wrong on my end. Thanks again G.
Yeah....there's a (good) chance that it's just as what happened with @acheney1990 and me...
you can read all about it HERE, but suffice it to say; it can easily be on the banking's end "flagging" with all the validation that's needed -- which is it's own headache trying to understand why they keep tripping it up this way....
Hey did you ever happen to get a solution on this? I seem to have run into the same problem because everything is setup the same as before, but since I've upgraded to Pie in Feb security, I can't use Google Pay (unable to pay in store), Zelle, or the Chase app (force closes immediately, apparently on checking my GPS location it seems).
My problem started when I updated my Moto x4 to latest Pie update 29.69-26-5. I was on Magisk 18.1, and Manager 7.0 which I had to uninstall to get the update. After reinstalling Magisk, Passing safety net, I get a message at the POS saying my phone won't work with Google Pay. My debit card (Chase) is still listed in Google pay on my phone but when I try to add another card I get "This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way"
if I clear the storage and uninstall and re-install Google Pay, it still has my debit card listed, so for whatever reason, it's keeping my payment info even though I cleared the storage.
ongoing issue over on the Magisk Forum. An update to Google Play Services isn't working nicely with Magisk.
Itachisasuke said:
ongoing issue over on the Magisk Forum. An update to Google Play Services isn't working nicely with Magisk.
Click to expand...
Click to collapse
Hmmmm...if this is the case, wouldn't "removing updates" and installing an older/stable version (from apkmirror.com or something) and keeping it from updating be a workaround, for now....?
simplepinoi177 said:
Hmmmm...if this is the case, wouldn't "removing updates" and installing an older/stable version (from apkmirror.com or something) and keeping it from updating be a workaround, for now....?
Click to expand...
Click to collapse
That is exactly what has been suggested and even outlined here and there. I tried a couple different scenarios but it became too cumbersome trying to juggle it all. I'll just wait for an update to be released. Lol
Hi
I was on Android 12 and signed in to the beta program 10 days ago.
I've noticed that APKs that were fine on Android 12 are not working anymore on Android 13 Beta.
APKs are crashing at opening.
I thought that may have been an issue related to the beta version of Android but couple of days ago Android 13 stable rolled out (I've signed out from the beta) but those apps are still not working.
I've found older APKs for a couple of apps and one works and one not.
How can I solve this without a factory reset?
Thank you in advance
What are the apps that are crashing? What does a logcat show when the app crashes?
Google introduced restrictions in A13 for side loaded apps. No longer can they use accessibility apis nor can they access notifications etc. Just speculation but if the apps you are using are old they may be crashing because of these changes.
skymera said:
What are the apps that are crashing? What does a logcat show when the app crashes?
Google introduced restrictions in A13 for side loaded apps. No longer can they use accessibility apis nor can they access notifications etc. Just speculation but if the apps you are using are old they may be crashing because of these changes.
Click to expand...
Click to collapse
You can bypass those restrictions by going to the app info page of the app and clicking on the 3 dot menu in top right corner.
Lughnasadh said:
You can bypass those restrictions by going to the app info page of the app and clicking on the 3 dot menu in top right corner.
Click to expand...
Click to collapse
Wasn't aware of this, thanks!
I don't have any issues with manually installed apks...
Hi, i have the same Problem with every sideloaded App.
There are no 3 dots in the right Corner.
I don't know exactly how to bypass Them
Waiting till the weekend to update, but what APKs are giving the error?
skymera said:
Wasn't aware of this, thanks!
Click to expand...
Click to collapse
Can't find this
Jeff_N said:
Hi, i have the same Problem with every sideloaded App.
There are no 3 dots in the right Corner.
I don't know exactly how to bypass Them
Click to expand...
Click to collapse
Do those apps need Accessibility and/or Notification Access permissions? If not, then I don't think the 3 dot menu needs to be there as it is only for those specific permissions (or whatever other permissions Google might add to the list in the future).
For example, I have Adaway installed but it doesn't have the 3 dot menu because it doesn't need either of those permissions. The same for App Manager.
I am really confused with this new "session-based install" security.
What are "session-based install" and "non-session-based install"
Play store app install --------- surly "session-based install" 100%.
3rd-party store install --------- is said also to be "session-based install".
Firefox download an apk --------- is said to be "non-session-based install",
But how the firefox different from a 3rd-party store????? a system white list something?
safetynet, selinux, forcing many settings, anti-rollback, non-store app restrictions.........
I enjoyed so much that google throws sht tons of troubles to billions of advanced users, to fight an enemy that may not even exist.
(how many people have their phone bootloader secretly unlocked remotely by a hacker and installed root malware, unknowingly?)
Gives a warning is good eg. bootloader locked warning is great IMO. But force the hands and keep finding ways to screw the advanced users as hard as they can, to get the "everything is under my control" status is the wrong path.
I read the news that malware devs have already found a way to bypass this restriction.
In the end, like many others, It achieved nothing, except giving trouble to advanced users and devs.
A global bypass must be also on the way, especially from China. Millions like 90% of APPs are not store-based in China since the google ban, and people are used to download apk from every companies' websites as we do on Windows PC.
somethingsomethingroot said:
Waiting till the weekend to update, but what APKs are giving the error?
Click to expand...
Click to collapse
3 APKs from the company I'm working for (not on PlayStore) 2 sideloaded apps, and a LADB signed sideloaded APK
For example you cut and CC cleaner keeps crashing all the time.
Same here. Almost every app not from Play Store keeps closing right on tap to start them.
Tried to sideload them per USB with full rights. Same.
My company apps that didn't come from the play store are opening without a problem
Thats Vers Strange, indeed.
Every sideloaded App, modded or Not does Not work
Thought it was me...this is bs!
What's the next step...start posting logs I assume?
It's not EVERY sideload for me but about 1 in 3 I'd say.
btw...I got an 'install failed' trying to install/flash the viper4android mod not realizing how old it was...now I'm seeing lotsa audio/sound related crap in logcat reader. If I AM 'currupt' somehow, will just a rom re-flash fix a magisk issue or do I need a full wipe?
Tia for any guidance offered!
Zaxx32 said:
Thought it was me...this is bs!
Click to expand...
Click to collapse
Me too but looks like is some security thing from Android 13. I really hope that somebody finds a workaround soon or I'll have to switch back to 12
salamala893 said:
Me too but looks like is some security thing from Android 13. I really hope that somebody finds a workaround soon or I'll have to switch back to 12
Click to expand...
Click to collapse
12 won't work right on the 13 bootloader, and you can't downgrade the bootloader.
When I initially tested flashing only the 13 bootloader on my Pixel 6 Pro, while still running Android 12, it booted fine, I unlocked the phone, and all looked normal. But I didn't launch apps, especially Chrome, YouTube, and plenty of other things. If I had, I would have noticed problems that others have had since then. It was since found that certain/many kinds of apps will not work right running on Android 12 when you have the 13 bootloader installed.
I know this above is not what this thread is discussing, but since you mentioned it, I just wanted to point out that if you're on any Pixel 6/Pro/a with Android 13's bootloader flashed, you won't be able to use stock Android 12 on it. You'll be able to flash everything but the bootloader, boot it up, and unlock it, but before long you would discover problems that you wouldn't be able to work around and would effectively make your phone unuseable for many things that we take for granted.
By the way, hopefully you have the 13 bootloader flashed to both slots. Having the 13 bootloader on only one slot is a little dangerous.
Code:
adb reboot bootloader
fastboot --slot all flash bootloader bootloader.img
Guys, but are you talking of sideloaded apps, or apps installed as apk?
gpvecchi said:
Guys, but are you talking of sideloaded apps, or apps installed as apk?
Click to expand...
Click to collapse
Apks