Hello,
I have unrooted my OnePlus 5, reflashed back to stock OxygenOS and stock recovery, and relocked the bootloader. I also did a factory reset. Basically, I wanted 100% stock.
However, my banking app complains, that I have Root and will not let me use Tap & Pay. Pretty much every app I have tried on the Play Store doesn't detect any root (because there is none). Except one: Security Check that is used by my bank.
What could be causing this? Maybe some leftovers?
I have a similar issue with another phone. Were you able to find the reason/solution?
Related
I rooted my phone using towel root, everything seemed fine until it started randomly crashing. Now the crashing happens like this, the screen will freeze (with like weird tearing) then either restart or stay frozen. The only root app I use is wifi tether router. I did notice supersu will fail to update the binaries. Not sure if that could be a cause.
My question is how do I unroot it. So I can at least attempt any kind of fix. I'm still under warranty.
Can anyone help me at all? Please
waterbottels said:
I rooted my phone using towel root, everything seemed fine until it started randomly crashing. Now the crashing happens like this, the screen will freeze (with like weird tearing) then either restart or stay frozen. The only root app I use is wifi tether router. I did notice supersu will fail to update the binaries. Not sure if that could be a cause.
My question is how do I unroot it. So I can at least attempt any kind of fix. I'm still under warranty.
Can anyone help me at all? Please
Click to expand...
Click to collapse
A thorough way to unroot and reset everything is to Odin back to stock and then do a factory reset. The stock tar can be found here.
kinstre11 said:
A thorough way to unroot and reset everything is to Odin back to stock and then do a factory reset. The stock tar can be found here.
Click to expand...
Click to collapse
I was able to get supersu to work again, could I do an unroot through that even if I used towelroot?
waterbottels said:
I was able to get supersu to work again, could I do an unroot through that even if I used towelroot?
Click to expand...
Click to collapse
There is an unroot option in SuperSU (although I've never done it so I don't know if it actually unroots or just cleans up things to allow a clean unroot. The other thing I'm not sure it does is restore Knox which is something that will be checked for by the manufacturer). If you're taking your phone back or sending it in under warranty you probably should make sure you uninstall anything you need root for prior to unrooting, but if you're on a custom rom or want to make sure everything is back to factory (including Knox) I would recommend doing what I suggested in my last post.
Same Problem
Same problem as OP. I had a Note 3 originally that I took the update to 4.4.2 and used Towelroot and everything was fine. I recently broke the bejesus out of my Note 3 and got a replacement under the warranty. I used Towelroot on the new Note 3 and I am getting random freezing and a weird line that appears across the screen once it freezes. Sometimes it will reboot others I need to pull the battery.
What is happening? I am now back to stock and want to root again. Anyone have a solution to this?
I am trying to login to Snapchat but it keeps saying there's an error with the login and I found out it is because I am rooted. A fix I found involves full unroot and I don't want to do that. Can anyone help me?
Snapchat
Ive used snapchat rooted. On mutiple roms.
Snapchat for some devices (like the v20 now) is checking for root. It's hit or miss really. On my VS995 Snapchat wouldn't work till I did suhide. So you'll have to most likely use Magisk or SU-Hide or some kind of root hiding thing to get past it.
Just install Snapchat on a other device, log in, make a backup with Titanium Backup and load it on your main device.
This worked for my rooted S5 KLTE
D.Va said:
I am trying to login to Snapchat but it keeps saying there's an error with the login and I found out it is because I am rooted. A fix I found involves full unroot and I don't want to do that. Can anyone help me?
Click to expand...
Click to collapse
magisk hide is option 1
rootswitch is option 2
full unroot, sign in, then re-flash the supersu zip to re root is option 3
restore a app+data backup from a logged in device using backup app like titanium is option 4..
Team DevDigitel said:
magisk hide is option 1
rootswitch is option 2
full unroot, sign in, then re-flash the supersu zip to re root is option 3
restore a app+data backup from a logged in device using backup app like titanium is option 4..
Click to expand...
Click to collapse
Personally i feel option 2 is easiest but not all kernels like it.
I wish these things could be put in to roms so when we flash them, there's no alternate flashing needed that could cause issues.. I had nothing but issues tryna get both of those options to work, but again it was probably kernel related so I just gave up on it..
jdmsohc22 said:
I wish these things could be put in to roms so when we flash them, there's no alternate flashing needed that could cause issues.. I had nothing but issues tryna get both of those options to work, but again it was probably kernel related so I just gave up on it..
Click to expand...
Click to collapse
Actually, the Stock deOdexed US996 ROM has them built into it, also allows for hotspot provisioning without having to edit anything. I've been running it for a few months now, and been flawless on every aspect, other than it disables the ability to use MyVerizon apps, and Verizon's visual voicemail.
Some history with the phone. I've gone back and forth a few times with this phone. At one point the bootloader was unlocked, I was rooted, etc etc. This was quite a while ago. Since then I have flashed the factory rom, locked the bootloader and ran 100% pure stock until this morning and everything worked just fine. Android Pay worked, etc. Today I decided I'd do a factory reset and not bother restoring data. Prior to doing that, I decided to give Magisk a quick try just for the heck of it. I flashed the current Oreo factory image (With Sept security patches) left the bootloader unlocked, flashed TWRP, installed Magisk via TWRP. Didn't really give it much of a chance but either way, after a quick check safetynet failed. So I figured, whatever no big deal. I flashed the factory image again, then relocked the bootloader, and eventually rebooted and signed back into my account and didn't bother restoring any backup. Let all the stock apps install/update, checked Android Pay.....and it wouldn't allow me to add a card. I checked the Safetynet tests and it fails the CTS Profile match. I'm pretty much at a loss now as to what in the world the problem is. The phone is fresh off of a factory reset and the bootloader is locked. No magisk, no root, nothing.
Another REALLY strange thing is, during boot up, I have to unlock the phone, then it continues booting up and eventually finishes the boot up process, although I think I recall reading about this being some new security thing. Either way, don't think it relates to my issue.
Well I unlocked the bootloader again, flash the August 7.1.2, relocked the bootloader, and after updating apps and Google Play Services, all is well again. Guess I'll just grab the OTA and go from there.
Wow, so sideloading the OTA broke it again.
Ug...found out there's a build 019. Apparently there's a problem with build 017. Sideloaded 019 and now I have no issues with safetynet.
glad someone else is seeing this, sideloaded OTA build 017 and Android Pay stopped working with it failing Safetynet's CTS Profile check
ParadingLunatic said:
Ug...found out there's a build 019. Apparently there's a problem with build 017. Sideloaded 019 and now I have no issues with safetynet.
Click to expand...
Click to collapse
Where is this 019 OTA? I'm having this same problem. I thought I was the Andromeda I tried but I knew that was rootless.
Thanks for shedding light on this.
---------- Post added at 07:45 PM ---------- Previous post was at 07:35 PM ----------
Did some more digging. Found it. Gonna see if it works.
Sent from my Nexus 6P using XDA-Developers Legacy app
ParadingLunatic said:
... Another REALLY strange thing is, during boot up, I have to unlock the phone, then it continues booting up and eventually finishes the boot up process, although I think I recall reading about this being some new security thing. Either way, don't think it relates to my issue.
Click to expand...
Click to collapse
This is because when you set the screen lock you checked the box to ask for the lock code when the system boots up. It's a good security measure that insures that if the phone is lost or stolen, a reboot will not allow someone to bypass the screen lock.
stevemw said:
This is because when you set the screen lock you checked the box to ask for the lock code when the system boots up. It's a good security measure that insures that if the phone is lost or stolen, a reboot will not allow someone to bypass the screen lock.
Click to expand...
Click to collapse
Yup I figured that out. I knew it was an added security feature but I couldn't recall where it was set. It seems that in Oreo, when you enroll in the fingerprint setup during the initial phone config, when it forces you to create a PIN it automatically sets that option without asking unlike how before, it used to ask.
ParadingLunatic said:
Yup I figured that out. I knew it was an added security feature but I couldn't recall where it was set. It seems that in Oreo, when you enroll in the fingerprint setup during the initial phone config, when it forces you to create a PIN it automatically sets that option without asking unlike how before, it used to ask.
Click to expand...
Click to collapse
Didn't realize it was automatically set in Oreo. I went thru 7 and the preview, so this option was already set. I will be getting the Pixel 2 XL, so it's something for me to check on.
TLDR: App Manager crashes Settings on selection in all scenarios tried, both rooted and unrooted. Solutions or explanations?
So it's basically as described there. App Manager is crashing on a new Moto G4 XT1625 no matter what I do. I am at a loss. It crashes while rooted with Magisk, crashes when Magisk is uninstalled, crashes when I do a fresh flash of the Motorola stock ROM. I've even rooted and gone into Titanium Backup and ensured nothing is frozen, and it crashes.
I can long press apps on the drawer to reach individual app settings, but I cannot get into the App Manager itself. I've tried clearing the cache via this entry into the settings app info, and I've cleared the cache via TWRP. Neither has seemed to affect the crash either.
The only common denominator I can think of between all attempts is that the bootloader is obviously unlocked, but I can't connect that to the crash in my head.
At a loss here - any ideas? What am I missing, or what else might I try? Thanks for any education.
got this crash as well on my xt1622, TWRP, marshmallow, rooted
BUT THE MOST IMPORTANT REASON that cause this is because I deleted some unused (india) apps after rooting. Then the app manager messed up.
I just flashed the stock Nougat yesterday (https://forum.xda-developers.com/moto-g4/help/xt1622-nougat-root-questions-t3701145) - clean, no root, no TWRP, no modifications. Then, the app manager worked as expected. I doubt this will help as you stated that you already tried to flash the stock rom. You might have some other problem there.
libralibra said:
got this crash as well on my xt1622, TWRP, marshmallow, rooted
BUT THE MOST IMPORTANT REASON that cause this is because I deleted some unused (india) apps after rooting. Then the app manager messed up.
I just flashed the stock Nougat yesterday (https://forum.xda-developers.com/moto-g4/help/xt1622-nougat-root-questions-t3701145) - clean, no root, no TWRP, no modifications. Then, the app manager worked as expected. I doubt this will help as you stated that you already tried to flash the stock rom. You might have some other problem there.
Click to expand...
Click to collapse
Indeed I have, which makes it all the more confusing as to what could remain unchanged and still affect it. Although, it is something that you encountered it under the same general environment (twrp, marshmellow, rooted). I disabled a few apps when I first rooted, and assumed that was the cause as you saw, but no idea why the flashing did not fix it...
I have a OnePlus 2. Still in great condition but stock ROM not performing great so I updated to Pixel Experience (unrooted), and its breathed new life into the device, so very pleased. However the one problem with using a custom ROM is of course banking apps can be particularly finicky about it and I really need Barclays Mobile app to work.
Ive endlessly read a lot of other threads about this but they are all about getting it to work on rooted devices. Magisk etc and other solutions that will constantly be patched by Barclays are just not good solutions. So running the device unrooted should eliminate most of the issues.
I still cant get it to run though but since Im not rooted this should be achievable if we can figure out what checks the app is making.
Here what Ive done so far:
I have TWRP recovery (obv to install new ROM)
PixelExperience ROM,
Ive relocked the bootloader
SafetyNet Check PASS
RootCheck - NOT ROOTED
Play Store - Device Certified
Changed build.props entry ro.build.tags=release-keys
Tried changing android_id.
Interestingly I have LLoyds, Santander and Nationwide banking apps all working.
But Barclays still says device is rooted. Just before this there's briefly a message that pops up saying "T0017 Not Authorised".
What other things can I try?