Hello All,
So I finally thought Apple was lagging a bit too much in hardware specs and moved to Android with the Samsung S4 and hence now popping my cherry with my first post on here.
I decided to root my device to zap all the bloatware, but soon found like many others I couldn't use the Barclays Mobile Banking App or Pingit.
After a LOT of Googling and trying different reported methods such as hiding files, temp unrooting apps, factory resets... non worked for me. So as banking is very important to me I decided to un-root it (After all, I only rooted it to remove Bloatware, and 90% of it I can disable anyway and it doesn't cause me any storage issues).
Once un-rooted I found that I could once again use the Mobile Banking app (after calling the helpline and having them de-register the device so I could re-register), however I still couldn't use the Pingit app which was saying the device was reporting the device as rooted. The helpdesk were non-the-wiser and offered to get back to me which they did after about 4 days and I had already resolved the issue.
So here's what I found and how I fixed it....
Unlike the Mobile banking app which checks if the device is rooted each time you start it, the pingit app checks it each time and then sync's this information to your Google account for backup purposes. Therefore it will re-download this information saying the device has been rooted when you reset the phone and recover your purchases.
Now these instructions are for a non-rooted S4 but may differ on other devices, but I hope it helps others tearing their hair out like I was:
1) Uninstall the Pingit app
2) Go to "Settings" > "Accounts" > "Backup Options" > "Backup and reset"
3) Untick "Back up my data" & "Automatic Restore"
4) Perform a "Factory data reset"
5) Install Pingit and it should work.
6) You should now be able to re-enable "Back up my data" & "Automatic Restore" which will override the previous cloud data.
This method worked for me and the process may be simplified without having to do a full reset, i'm not sure as i'm still new to Andoid but I hope it helps a lot of frustrated people out there.
p.s. I also came across a scenario where it could affect users with a phone which has never been rooted... For example if you previously owned a rooted phone and had installed "Pingit", then tried to install it on a new phone which has never been rooted, it could also re-download the backup which says it's been rooted and disables the app. Therefore you should just follow the above instructions and it should work.
Hope it helps, cheers.
Daskew78 said:
Hello All,
So I finally thought Apple was lagging a bit too much in hardware specs and moved to Android with the Samsung S4 and hence now popping my cherry with my first post on here.
I decided to root my device to zap all the bloatware, but soon found like many others I couldn't use the Barclays Mobile Banking App or Pingit.
After a LOT of Googling and trying different reported methods such as hiding files, temp unrooting apps, factory resets... non worked for me. So as banking is very important to me I decided to un-root it (After all, I only rooted it to remove Bloatware, and 90% of it I can disable anyway and it doesn't cause me any storage issues).
Once un-rooted I found that I could once again use the Mobile Banking app (after calling the helpline and having them de-register the device so I could re-register), however I still couldn't use the Pingit app which was saying the device was reporting the device as rooted. The helpdesk were non-the-wiser and offered to get back to me which they did after about 4 days and I had already resolved the issue.
So here's what I found and how I fixed it....
Unlike the Mobile banking app which checks if the device is rooted each time you start it, the pingit app checks it each time and then sync's this information to your Google account for backup purposes. Therefore it will re-download this information saying the device has been rooted when you reset the phone and recover your purchases.
Now these instructions are for a non-rooted S4 but may differ on other devices, but I hope it helps others tearing their hair out like I was:
1) Uninstall the Pingit app
2) Go to "Settings" > "Accounts" > "Backup Options" > "Backup and reset"
3) Untick "Back up my data" & "Automatic Restore"
4) Perform a "Factory data reset"
5) Install Pingit and it should work.
6) You should now be able to re-enable "Back up my data" & "Automatic Restore" which will override the previous cloud data.
This method worked for me and the process may be simplified without having to do a full reset, i'm not sure as i'm still new to Andoid but I hope it helps a lot of frustrated people out there.
p.s. I also came across a scenario where it could affect users with a phone which has never been rooted... For example if you previously owned a rooted phone and had installed "Pingit", then tried to install it on a new phone which has never been rooted, it could also re-download the backup which says it's been rooted and disables the app. Therefore you should just follow the above instructions and it should work.
Hope it helps, cheers.
Click to expand...
Click to collapse
I'm very surprised to see nobody else reporting this issue or thanking you for it.!
I've had this issue with the Barclaycard and Barclays Mobile Banking apps, and been scratching my head trying to figure out why.
I understood that some apps simply scan the directory for folders named "Root" or "Su" so I found these leftover and removed them. Nothing. I uninstalled the SuperSu App and both worked once bizarrely and then the following time stated I was rooted again. Their method of "detecting" root, as you've described - is crap! That is a stupid way of doing it, (because its foiled me for days!).
Hey ho, this looks like the only thanks you've received strangely, I'm surprised to see so few affected by this - thanks for your post! :thumbsup:
Hi,
I have exactly the same problem but it was down to to restoring a Google backup from a rooted phone to a non rooted one. It's too late for me to do a factory reset. Is there any other way of making this app work now?
voipman2012 said:
Hi,
I have exactly the same problem but it was down to to restoring a Google backup from a rooted phone to a non rooted one. It's too late for me to do a factory reset. Is there any other way of making this app work now?
Click to expand...
Click to collapse
Not that I know of, have you searched the directories for any apps / folders that might give the impression the device is rooted?
The Barclays apps seems to scan for SuperSU and potentially Root Checker apps. If it finds them, then Barclays presume you are a danger to yourself with your device and it won't work [emoji53]
I'm growing tired of Barclays now anyway, particularly their refusal to run with Android Pay and go about things in their own way. Yet they will use Apple Pay.
Let me know how you get on..
Sent from my Nexus 6P using XDA-Developers mobile app
Well, A lot of Android users have been struggling with snapchat while trying to log in, it keeps saying ''Oh no, your login temporarily failed''. I like Snapchat, so since I wasn't able to use it I've been investigating and trying all possible solutions.
This is what I've found; The problem isn't Root itself, but Xposed Framework. In my case I just went to Xposed>Framework>Uninstall, then reboot and finally I was able to login and use snapchat as usual. I know unistall xposed framework might not be an actual solution for all of you, but I wanted to put this information here so It may help someone. I'm as dissapointed as all of you because of this decision snapchat took.
I have this problem for two days , unable to connect to my account. But before I did not have this problem when I was already root
http://forum.xda-developers.com/android/apps-games/attention-post-qa-troubleshooting-t3178095
Thread closed
Today I reboot my Op3 after a while.
I usually keep it running without any problem and i just reboot a couple of times in a month.
Before this, I've not done anything new, no strange websites, no strange apk, no installation of anything exept for the app HeyMonster, installed a week ago and I've update 2 modules of Xposed (Wifi Password and Youtube Background Player) right before rebooting.
A part from those, I've not done anything that could have created this problem.
So, I reboot.
After that, WhatsApp started to ask to gain root access.
As a normal root app.
But this is not normal at all.
So, I searched around, but i found nothing, I looked in my phone, in services, app, stuff, but i didn't find anything abnormal.
I run a scan of my phone with PandaAntivirus Pro, but it found nothing (not that I was really believing in it).
So, I guess that is a malware that i got from IDon'tKnowWhere.
And I actually don't really know what to do about it.
I Know that reflashing and start over is the sure solution but, before that, I'd like to realize what and why is this happening.
Thanks to anyone
Weird that I too got the same root request from WhatsApp only a while ago. Two requests from "WhatsApp" and "WhatsApp UID". Any leads?
$$% ¥*hftd÷$_
Me too, but for now I will deny
Sup fellas just posting this from my phone
Basically I rooted it with CFAUTO root I found on a site that seemed trustworthy due to its credibility found on various sites.
Root works perfectly along with Xposed for awhile but eventually a week later every single app will start force closing, or immediately fail to launch on touch. From instagram to KiK to play store itself.
Rebooting is not a good solution as it resolves into a boot loop.
This has been happening consistently for a few weeks. The only solution to get my phone back up and running is to do a factory reset (which in turn means setting everything up again to my preferences. )
This pretty much led me to leave the phone as it comes plus a few common apps and just rely on my iPad more.
Does anyone have a solution? I followed the tutorial down to the T. Video and guide. I'm considering switching to stock but want to see if anyone else had this issue or was able to fix it
I would say to use this guide.
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
Havent tried CFAUTO root, and I dont think its recommended.
I had a similar issue with apps force closing, though I didn't use cfauto root.
The issues I had, after finding out from much trial and error, was that after I rooted my apps would update before Google play services. This would cause problems because the updated apps needed the updated play services to run.
Revert back to stock, then make sure that Google play services is up to date before updating any other app. After play services are up to date, make sure your play store is up to date. Then go ahead and update all of your apps. Next reroot your phone.
Like I said before I didn't use cfauto root, but I hope this helps.
Guys i need urgent help i am rooted with magisk and have installed latest version. i have magisk hide enabled and have chosen snapchat in the options. Magisk hide perfectly works with other apps that i want to hide it from but it doesnt with snapchat. I now have been locked out of my snapchat account for 1 week and i urgently need help. i don't know what the issue is my snapchat i downloaded clean from the playstore but it keeps saying you are trying to access snapchat from third party apps. literally any help appreciated.
Thanks
Also i do not have xposed
Unroot. Install snapchat and confirm it works. Then root and hide with Magisk.
Or you can do my trick, take a backup of Snapchat (and it's data) with titanium backup, then uninstall Snapchat and restore it with Titanium Backup, I never had to put magisk hide like this for many years now and it has always worked even with rom updates and every flash of roms I did so far.
Hope it helps.
vinct94 said:
Or you can do my trick, take a backup of Snapchat (and it's data) with titanium backup, then uninstall Snapchat and restore it with Titanium Backup, I never had to put magisk hide like this for many years now and it has always worked even with rom updates and every flash of roms I did so far.
Hope it helps.
Click to expand...
Click to collapse
Do I back it up when I'm rooted or do I unroot then take a backup?
1. Uninstall snapchat
2. Flash magisk uninstaller in recovery
3. Start phone
4. Install snapchat and login
5. Reinstall magisk an enable magisk hide bevore opening snapchat
You're the first other person I've been able to find online reporting this issue. I've had the same problem and it started in December.
It doesn't seem to have anything to do with Magisk being hidden or being logged in beforehand. Even if I restore a logged in backup from another phone or unroot, log in, then root again, Snapchat force logs me out after a day or so. Then when trying to log in again, it'll say the account has been temporarily locked, and eventually if I wait long enough, I can log in again and have a message from Team Snapchat telling me my account was locked for X hours. I got up to 72 hours and gave up on Snapchat. Tried making a brand new account as well bad same thing happens.
I'm not sure what the hell they are detecting or how. I've never used any third party Snapchat clients and Magisk is the only thing I'd suspect them to be looking for. But I've no clue how and why no one else in the online world seems to be having this problem but us two... However, OxygenOS could possibly be a contributing factor in some way as we both as OP device (I have a 6T).
NarenParashara said:
FINALLY someone who has the same problem as me. OnePlus 3T here, have you guys tried uninstalling substratum?
Click to expand...
Click to collapse
no i actually don't have substratum i really don't know the problem, i unrooted and rerooted however i cant actually check because im still banned for a week from snapchat i think im just gonna give up. however no i have a new problem when i reboot the phone i get the red message saying its corrupted and may not work it still boots tho but that message is really annoying
Mofo50C said:
i did have the settings database thing but that was a long time ago and i didnt modify any settings i got it so i can take a backup of its apk and send it to a friend. (dont ask XD) but other than that no i dont even have substratum. Right also i tried unrooting it and rerooting it and now my phones giving the red message saying its corrupted and may not work properly. it still turns on but it says that at boot. Is there a way to fix this
Click to expand...
Click to collapse
You mean the screen that says "the device cannot be checked for corruption"? That doesn't mean it is corrupted. It just means through bootloader is unlocked so it can't guarantee the system hasn't been modified from stock. But that's the whole purpose of unlocking the bootloader, so you just have to live with seeing it whenever you reboot.
---------- Post added at 09:31 PM ---------- Previous post was at 09:27 PM ----------
NarenParashara said:
Then Titanium Backup, maybe?
By the way, how do you check how long you've been locked out for?
Click to expand...
Click to collapse
It's so stupid. They send you so message through Snapchat itself from "Team Snapchat", so of course, you don't know how long you were locked out for until after the fact ?
It seems to start at 12 hours and go up by 12 mkre hours each time they lock it.
Its not Titanium Backup. I have it and Snapchat with no issues (Magisk). I don't have any theme modules though.
So the other night, I uninstalled Magisk on my old OP5T bad logged into Snapchat. Its been a couple days and I am still logged in and they haven't locked my account or anything. So it seems that somehow, it is detecting Magisk on our phones, despite any attempts at hiding it. ?
I'm just absolutely puzzled by how this is only affecting a few of us. I suppose there could be more of us out there who just haven't posted about it, like myself until I came across this thread.
Something I have noticed that may help people on OOS. I have Snapchat cloned through Parallel Apps cause I have a few logins, it seems the accounts that always get banned and detect Magisk are running on the original app, the cloned app hasn't been banned once.
Snapchat can be i PITA when rooted ... Magisk Hide works currently for me on OOS 9.0.3 though.
Don't know if this changed, but it only checks for root at login. So Unrooting -> Logging in Snapchat -> Rooting with Magisk Hide enabled worked previously for me.
But right now, Magisk Hide seems to fool it even during the login process, didn't get any error message like "We can't login right now" (Which it used to say when it detected root)
Guys this is really lame. It started for me a few days ago. I have Pixel 2 XL and I am up to a week now as well. I love SnapChat. I did not have an Instagram until this happened to me the first time. Let them lose valuable active users when they are trying to secure more. The SnapChat update for Android is kind of trash from the few minutes I got to use it like. The camera already was supported on my device well. Now I cannot share multiple memories in one message from chat. I have to go to memories and individually send them. *edit: replaced a censored word with 'trash'
DevonDeception said:
Guys this is really lame. It started for me a few days ago. I have Pixel 2 XL and I am up to a week now as well. I love SnapChat. I did not have an Instagram until this happened to me the first time. Let them lose valuable active users when they are trying to secure more. The SnapChat update for Android is kind of trash from the few minutes I got to use it like. The camera already was supported on my device well. Now I cannot share multiple memories in one message from chat. I have to go to memories and individually send them. *edit: replaced a censored word with 'trash'
Click to expand...
Click to collapse
lose active users? You do understand that root users are like less then 1 or 2% so they dont really care about those uses if you can make the system more secure.
There are dozens of us! Yeah, well I am, or was pretty active. I don't disagree that we are small in numbers, and I'm not sure if the amount of people rooting is growing or shrinking. I have not installed custom ROM in years, but still root.;
My banking app seems to recognize Magisk after a couple days no matter what I do as well.
Got the same problem on my S9. Magisk 18.1 on a modified samsung ROM. Works flawlessly without magisk, pretty much instant account-lock when I install it. Hide or not, doesn't matter.
Ok so I read this whole thread up to now and I have the exact same issue with an Xperia XZ Premium. Now I only rooted and unlocked my bootloader around a week ago. Prior to this when I was on oreo I used the Andromeda substratum non root method and even modified the theme on Snapchat without issues no ban what so ever. I then updated to pie on locked bootloader and still fine. Only to the point I rooted did I get ban issues. So I have no magisk modules and only around 3 root apps (one being substratum which wasn't even working for me anyway).
Yesterday it would not let me login and I found that my safetynet checks were both false and I'm not sure how they were because every other time I checked they were true and I never flashed anything. I managed to fix this by uninstalling magisk and restoring my system backup. I then installed magisk again and used magisk hide. I just got banned not too long ago.
I think they must be detecting the actual magisk app rather than root itself. That's my theory, the only way to know for sure is just to have the APK installed without magisk flashed but I don't want to get the account banned again. For now I've decided that I'll not have magisk flashed and that I'll just go without it since I wasn't really using any root apps anyway. If I still get banned after that then we would know that it's not magisk but I can report back after. I've noticed that the ban happens at 5.40pm UK time for me every 1 day.
I have an Xperia Z2 which has super su installed but it isn't rooted since I just use it as a spare phone I used Snapchat on it temporarily and didn't get any bans on that. I'll try it on my XZ Premium as is without magisk installed and if I still get banned then I'm not sure what it would be.
Okay so after not having magisk installed I now got a 2 day ban and I'm not sure how because I do not have root installed and all my other apps that are installed are the same from before I ever even rooted so I'm unsure as to why I have this ban now which is beyond stupid. The only thing I can put it down to now is the screen recording app I have but I don't even have magisk installed so I don't understand how it wants to decide to ban me for an app I don't even have installed. If anyone can work anything out with this is would be great. I do still have an unlocked bootloader.
RJASSI21 said:
Okay so after not having magisk installed I now got a 2 day ban and I'm not sure how because I do not have root installed and all my other apps that are installed are the same from before I ever even rooted so I'm unsure as to why I have this ban now which is beyond stupid. The only thing I can put it down to now is the screen recording app I have but I don't even have magisk installed so I don't understand how it wants to decide to ban me for an app I don't even have installed. If anyone can work anything out with this is would be great. I do still have an unlocked bootloader.
Click to expand...
Click to collapse
even if you did not modify it it's still a good idea to reinstall the app after ban(or even wipe data if possible). I had this problem before when after unrooting i got banned, i formated data and then i was fine.