I'm on V12.5.1.0.RJOMIXM, Magisk v23.
I woke up this morning and all of a sudden my device is not passing safetynet, failing on CTSprofile. It has worked fine for months and I haven't changed anything, other that play store auto updates being enabled
Edit: I awoke to a notification off gpay saying device doesn't meet security standards and that I can't use contactless if that makes a difference, never had a problem with it before
Certainly, you made some changes on the device.
I made no changes on the device. Do not state something as certain when you can not be certain
Regardless, I fixed it using the instructions here
If you are using magisk, so yes, you made changes on the device.
Lurxs said:
I'm on V12.5.1.0.RJOMIXM, Magisk v23.
I woke up this morning and all of a sudden my device is not passing safetynet, failing on CTSprofile. It has worked fine for months and I haven't changed anything, other that play store auto updates being enabled
Edit: I awoke to a notification off gpay saying device doesn't meet security standards and that I can't use contactless if that makes a difference, never had a problem with it before
Click to expand...
Click to collapse
Same thing happened here on Mi Mix 2S.
pancomido said:
Same thing happened here on Mi Mix 2S.
Click to expand...
Click to collapse
I can only assume Google updated something stealthily, I fixed it using this guide, follow at your own risk
Related
I know there's got to be some setting turned on that is preventing me from toggling the apps in Device Administrator because whenever I go to it, I can see the full list, and when I attempt to toggle one of them on or off, settings crashes and locks the phone. I have two apps that have been toggled on, so somehow I was given the ability to do it before this hard to find setting was turned on preventing me from toggling any more apps....
Any suggestions on what I'm doing wrong? Thanks!
KryptosXLayer2 said:
I know there's got to be some setting turned on that is preventing me from toggling the apps in Device Administrator because whenever I go to it, I can see the full list, and when I attempt to toggle one of them on or off, settings crashes and locks the phone. I have two apps that have been toggled on, so somehow I was given the ability to do it before this hard to find setting was turned on preventing me from toggling any more apps....
Any suggestions on what I'm doing wrong? Thanks!
Click to expand...
Click to collapse
I was getting the exact same issue on my S8+ yesterday. Do you perhaps have the latest/beta version of Call Recorder by SKVALEX installed? With my issue at least, I think it was down to that app, well a conflict between the two versions I had on the phone. May have been coincidence and could have been unrelated of course but removing both (old and beta) then just installing the latest beta sorted the issue, or t least the issue went away at the same time...
chippyuk said:
I was getting the exact same issue on my S8+ yesterday. Do you perhaps have the latest/beta version of Call Recorder by SKVALEX installed? With my issue at least, I think it was down to that app, well a conflict between the two versions I had on the phone. May have been coincidence and could have been unrelated of course but removing both (old and beta) then just installing the latest beta sorted the issue, or t least the issue went away at the same time...
Click to expand...
Click to collapse
Not, I don't have that app nor do I think this is AN app preventing me from adjusting Device Administrator toggles
I Had the same problem in my note 7, only thing I could do was a reset all app settings, that solved the issue
Background - switched from xposed to Edxposed to get Google Pay to work. It does now work but caused buggy side effects.
1. System soft reboots directly after a manual boot completed but is then okay usually if left to settle.
2. Screen says always on, will not respond to display settings options set to 'off' after 1 min. It will off by power key, just not auto off.
3. One xposed module does't work at all (Niwatori One Handed Mode). Xposed Edge and Gravity work fine so far.
I have 2 devices, an LG V20, LG G5 both on Oreo and both exhibiting exact same problems. 1 device uses Edexposed Manager, the other Edxposed Installer. Is installer now obsolete?
So the One handed Mode is the biggest problem. Is there a way to look under the hood to fix a non working module? If I could fix the other problems maybe I could find an alternative app for one handed mode.
Okay well "HiddenCore module" (xposed module) was causing the screen to stay on. As I said I just installed it cause I saw it thinking maybe it was necessary for Gpay. Turns out I uninstalled it, the screen will now auto off, and Gpay still works.
Only issue now is the soft reboot after boot completed. Not a huge deal, maybe it will be resolved in an edxposed update, although I am now using the latest Canary alpha, alas no change.
Okay well "HiddenCore module" (xposed module) was causing the screen to stay on. As I said I just installed it cause I saw it thinking maybe it was necessary for Gpay. Turns out I uninstalled it, the screen will now auto off, and Gpay still works.
Only issue now is the soft reboot after boot completed. Not a huge deal, maybe it will be resolved in an edxposed update, although I am now using the latest Canary alpha, alas no change.
ezzony said:
Only issue now is the soft reboot after boot completed. Not a huge deal, maybe it will be resolved in an edxposed update, although I am now using the latest Canary alpha, alas no change.
Click to expand...
Click to collapse
I experience the same and already reported it to devs.
https://github.com/ElderDrivers/EdXposed/issues/373
C3C076 said:
I experience the same and already reported it to devs.
https://github.com/ElderDrivers/EdXposed/issues/373
Click to expand...
Click to collapse
That thread is saying something about using a modified build of magisk. Did you try that and do you know where to get it?
edit: I'm using latest magisk 20 version.
The Edxposed Manager Canary release fixes this for me
Hello, I have a pixel 4XL coming from a pixel 2 XL. After rooting I normally disable a bunch of system services and apps I don't need, one is always fused location. This was never an issue on my 2XL, and when I first got my 4XL a few months ago I disabled it with out issue. Then I guess an update happened because everything was working fine with it disabled and then one day I needed to enable it to (first time) connect a bluetooth item. So I enabled it, connected the bluetooth device and then disabled it again. On reboot it was boot looped, only making it to the lockscreen then immediately booting again. I didn't have back-ups so I wiped the device and tested it again and sure enough disabling just fused location put it into boot loop.
What I don't understand is that this never happened on my 2XL or my 4XL at the beginning. In digging into the issue online it appears that other devices have had the same issue going back a couple years but oddly pixels didn't seem effected (as far as I can attest) till recently. I'm guessing something calls for the devices exact location on boot and with the fused location disabled it bootloops.
My question is, does anyone have any idea of a work around for this? Is there a way to have it disabled and not boot loop? Or can whatever is calling it and causing the boot loop also be disabled?
teffyd said:
Hello, I have a pixel 4XL coming from a pixel 2 XL. After rooting I normally disable a bunch of system services and apps I don't need, one is always fused location. This was never an issue on my 2XL, and when I first got my 4XL a few months ago I disabled it with out issue. Then I guess an update happened because everything was working fine with it disabled and then one day I needed to enable it to (first time) connect a bluetooth item. So I enabled it, connected the bluetooth device and then disabled it again. On reboot it was boot looped, only making it to the lockscreen then immediately booting again. I didn't have back-ups so I wiped the device and tested it again and sure enough disabling just fused location put it into boot loop.
What I don't understand is that this never happened on my 2XL or my 4XL at the beginning. In digging into the issue online it appears that other devices have had the same issue going back a couple years but oddly pixels didn't seem effected (as far as I can attest) till recently. I'm guessing something calls for the devices exact location on boot and with the fused location disabled it bootloops.
My question is, does anyone have any idea of a work around for this? Is there a way to have it disabled and not boot loop? Or can whatever is calling it and causing the boot loop also be disabled?
Click to expand...
Click to collapse
Leave it alone is a work around
c_86 said:
Leave it alone is a work around
Click to expand...
Click to collapse
Why would you respond with this comment? It's useless. If he wants to tinker with his phone he has all the right to do so.
airmaxx23 said:
Why would you respond with this comment? It's useless. If he wants to tinker with his phone he has all the right to do so.
Click to expand...
Click to collapse
Thanks. Primarily disabling it improved battery life and I rarely ever actually need gps for any reason (except ridiculously, pairing a Bluetooth device one foot away - thanks android).
Second, the fact that fused to location is taking AND sending your exact coordinates 24/7 to Google and whoever else they share your data with or however else they want to exploit it - isn't something to celebrate especially with the huge cost of the device itself. I can't be the only one who feels gross buying expensive devices that just log everything I do so it can be sold to the highest bidder?
Don't use your primary phone to spoof Pokemon Go.
Sent from my Pixel 4 XL using XDA Labs
all of a sudden safetynet is failing and i woke up to my phone saying you can no longer do contactless payments. What can I do?
It does pass when I hide modules but I have not installed anything new in months
Play Services update. https://twitter.com/topjohnwu/status/1245956080779198464?s=19
I woke up to a notification saying "your phone is no longer ready for contactless payments." It was working yesterday. I did the software check and it failed. Anyone else have this pop up?
I'm on A12 beta1, rooted, hardware off 2.0 module. Safetynet fails but has been for a couple weeks.