I recently updated my phone, 2014 Moto X from USC. Was on a stock 5.1 ROM, just installed CM12.1 and Xposed framework (including a number of modules, naturally). Between then and now, I've started having issues with some apps, Facebook and Messenger being initially noticed, just now Chrome Canary, as well as date and time not saving after reboot. I pulled some logs of the errors, before Chrome started quitting, with timestamps, but I don't know what I'm looking at, let alone how to even look for a fix for these issues that would, hopefully, not involve uninstalling Xposed or going back to a stock ROM. If anyone can help, I would greatly appreciate it. I would attach a more recent log file, but I keep getting a network error message. I'll post it later if I can, if anyone requests it.
For anyone finding this post, I'm impatient and tried fixing my issues through other means. Apparently Xposed didn't like Chrome Canary, Facebook, or Messenger. At least not on my device. Ended up resetting and installing the latest CM13 nightly. Date and time was fixed until I installed Xposed, again. Realized my problem was I didn't have automatic date and time set. Chrome Canary continued to not work. Don't know about Facebook or Messenger as I found alternatives to the official apps that I prefer. After installing some modules, Xposed would cause my phone to bootloop after rebooting. So, still don't have Xposed, but my problems were resolved. Would rather be able to use Xposed, though. If anyone can offer any advice in that direction, I would be grateful.
So, an update, feels like this thread is more of a diary than a forum post, though. Xposed didn't work because of the November security patch. A fix has been made, though experimental, and can be found at the following link for anyone that would like Xposed on their post-Nov ROM, but it doesn't work on all devices, the thread suggests. http://forum.xda-developers.com/xposed/discussion-xposed-marshmallow-t3249095/page453
I've got lastpass installed and have chosen to use the accessibility option as I want it to fill the forms in chrome, however the option in accessibility keeps disabling on it's own.
Anyone know a solution?
Wish I did, having the same issue. Seems to only occur after a restart though. I normally switch it off at night and let the alarm switch it back on in the morning.
I changed the app launch settings to manual in the battery menu to fix this
Sent from my CLT-L09 using Tapatalk
I changed the setting in the battery menu to "manual" but it still keeps disabling several times a day. Does anyone know is there's a fix?
I have a Mate 10 Pro and I have usually been getting this issue after a Huawei software update.
Old thread I know, but the only solution that has always worked for me is the following.
1. Uninstall Lastpass
2. Restart your phone
3. Install Lastpass and enable all the functions you like, including draw over other apps, fill helper bubble etc.
The options at least for me stay enabled until the next update. Without doing the above steps, they will just get auto-disabled after a few seconds.
This forum is meant for people who are getting locked out of their accounts due to "3rd Party Plugins or Applications"
We need to stop this from happening so share your experiences and thoughts on the matter.
I have 2 devices: a Nexus 6P running Pie (Pixel Experience) and a Pixel 3XL on the stock Pie rom. Both are rooted with Magisk Canary builds and both have Magisk Hide turned on. Snapchat never detects root on the Nexus but ALWAYS detects it on the Pixel. I've even repackaged Magisk on the Pixel but that doesn't help. I've read that it's easier for apps to detect root on A/B partition devices so maybe the newer, updated Snapchat apps have code to detect it. When I have time, I'll try an old version and see if it works...
Note that I don't believe Snapchat bans just by detecting root. It is detecting certain apps that are somehow triggering it. If you check the list of apps that you have given permission for superuser, it would be one of those. The app that I had that was triggering Snapchat was an app named app ops. I had downloaded it and just giving it permissions alone was getting me banned on Snapchat. I think this problem only affects users running Oreo or higher for whatever reason. I myself had an old phone running marshmallow with app ops and never experienced a ban. I don't think that any of the people reporting the problem had anything lower than Oreo. If you have somehow discovered the app causing your problems, uninstalling it may not fix your problem. I had to wipe my phone in order to fix it because I was still receiving bans despite uninstalling the app that was causing my problems
I've never installed app ops so that's not my problem.
As for A/B partitioning, I'm on a Samsung galaxy Note 8 and it didn't come out with this on my device so yeh ?
The main thing I found out that I had to do, was repackage the manager and I haven't been banned for the last 4 days
I am on the S8 plus and was locked out for 12 hours before. Snapchat continued to lock me out even when I fully uninstalled magisk. I decided to clean install a different Rom which seemed to do the trick. A month later I decided to go back to my original Rom and guess what? Can't even login coz of some mod I think.
So I would say it depends on what mods you have installed yourself or packaged with the custom ROM.
Snapchat ban
I have same problem. Yesterday they gave me ban but i was unbanned with their site. But today they give me one more ban but now is for 24h ... anyone know how to fix snap or maybe hide root? S7 9.0 blackdiamond v3
Downloaded an early January 2019 version of Snapchat and signed up for a new account on my Pixel 3XL. All was good at first then I closed the app. When I tried to sign back in, I got the "problem connecting to server" error which requires an update to the most current version. I updated and after just a few hours, I got the "12 hour account locked" message for "3rd party apps". I've had Magisk Manager repackaged but that obviously didn't help. BTW, I have not repackaged Magisk on my Nexus 6P and it's still works. I found a comment by a user of the Bitmoji app (which I use on my Pixel but not my Nexus) that reported his Snapchat was locked by this app so I uninstalled it. We'll see how it goes when my 12 hour ban is up...
Update: I uninstalled Bitmoji. I also added the systemless host module in Magisk and enabled systemless mode in Adaway. That is supposed to prevent Adaway from modifying the system partition but neither worked. I'm on a 24 lock now....
newkydawg said:
Update: I uninstalled Bitmoji. I also added the systemless host module in Magisk and enabled systemless mode in Adaway. That is supposed to prevent Adaway from modifying the system partition but neither worked. I'm on a 24 lock now....
Click to expand...
Click to collapse
What apps have you given superuser? The app causing you problems is likely in that list
I had this happen before to me, i uninstalled edXposed and i was able to use snapchat even while on a 24 hour ban
iMystic said:
What apps have you given superuser? The app causing you problems is likely in that list
Click to expand...
Click to collapse
Nope. I have the same apps on my Nexus 6P and it doesn't get locked out. In fact, my wife's Nexus 6P has the same apps, is rooted with SuperSu and she doesn't get locked out so IDK...
newkydawg said:
Nope. I have the same apps on my Nexus 6P and it doesn't get locked out. In fact, my wife's Nexus 6P has the same apps, is rooted with SuperSu and she doesn't get locked out so IDK...
Click to expand...
Click to collapse
I don't know if this would affect you but an app that was causing the problems on my phone with Android 9.0 has no affect on an old phone running Android 6.0.1. I don't know why this happens but if you were running a new version of Android such as Android 9.0, an app that may not cause problems on your 6P may cause problems for you. And again, I have no idea why this happens but I can guarantee that was my problem and I haven't had a ban since
iMystic said:
I don't know if this would affect you but an app that was causing the problems on my phone with Android 9.0 has no affect on an old phone running Android 6.0.1. I don't know why this happens but if you were running a new version of Android such as Android 9.0, an app that may not cause problems on your 6P may cause problems for you. And again, I have no idea why this happens but I can guarantee that was my problem and I haven't had a ban since
Click to expand...
Click to collapse
Both my Pixel 3XL and Nexus 6P are running Android 9 rooted with Magisk Canary (19005). Both have the same apps with superuser rights. All this to say that Snapchat was working fine on both for months and for about the last 6 weeks, my Pixel 3 XL's account gets locked and my Nexus 6P does not.
Thanks for trying to help and glad you figured your problem out.
I'm copying this from the SnapFreedom thread who's problems obviously mirror your own. I'll be editing parts out, but some of it should still apply if you guys are getting locked out.
XPrivacyLua
Install it from FDroid or Xposed Repo and check the boxes for "Determine activity" and "Get applications" in Snapchat's tab. You can also enable "Get location" to spoof your location and still use SnapMaps.
Magisk
A few points, these probably don't apply, but they're still worth doing.
Repackage it through Settings -> Hide Magisk
Make sure to block all components under "Google Play Services" and "Google Play Store". There's a few things that aren't blocked by default that might trigger SafetyNet.
Snapchat
Hoo boy...
Don't use anything higher than, and including, 10.41.6.0. It's pretty much a ban-fest. With SnapTools, we use 10.20.5.0 and 10.26.5.0. Those are probably your safest bets. Also, if you plan on downgrading, use any 10.39 app. Something in how logins work has changed in the later versions, so apps like Preferences Manager don't work.
Theming your app should be okay. I did it for months and never got a ban.
Only give it the bare minimum permissions. Storage, Camera, and Microphone. Location too, if you're into being tracked by your friends and Snapchat.
Do NOT use modified apps. At all. Ever. They're the easiest things to detect.
If you want to block ads reliably, you can use this Magisk Module. This WON'T stop bans.
Snapchat also logs your device ID. If you've received a temp-ban prior to this, make sure to change your Device ID. If you're on Oreo, you can use this app. If not, you can use Titanium Backup to change it. The latest version with this function is version 8.2.2. But honestly, the most reliable way is to reflash your ROM.
TevW said:
I'm copying this from the SnapFreedom thread who's problems obviously mirror your own. I'll be editing parts out, but some of it should still apply if you guys are getting locked out.
XPrivacyLua
Install it from FDroid or Xposed Repo and check the boxes for "Determine activity" and "Get applications" in Snapchat's tab. You can also enable "Get location" to spoof your location and still use SnapMaps.
Magisk
A few points, these probably don't apply, but they're still worth doing.
Repackage it through Settings -> Hide Magisk
Make sure to block all components under "Google Play Services" and "Google Play Store". There's a few things that aren't blocked by default that might trigger SafetyNet.
Snapchat
Hoo boy...
Don't use anything higher than, and including, 10.41.6.0. It's pretty much a ban-fest. With SnapTools, we use 10.20.5.0 and 10.26.5.0. Those are probably your safest bets. Also, if you plan on downgrading, use any 10.39 app. Something in how logins work has changed in the later versions, so apps like Preferences Manager don't work.
Theming your app should be okay. I did it for months and never got a ban.
Only give it the bare minimum permissions. Storage, Camera, and Microphone. Location too, if you're into being tracked by your friends and Snapchat.
Do NOT use modified apps. At all. Ever. They're the easiest things to detect.
If you want to block ads reliably, you can use this Magisk Module. This WON'T stop bans.
Snapchat also logs your device ID. If you've received a temp-ban prior to this, make sure to change your Device ID. If you're on Oreo, you can use this app. If not, you can use Titanium Backup to change it. The latest version with this function is version 8.2.2. But honestly, the most reliable way is to reflash your ROM.
Click to expand...
Click to collapse
There are all the reasons why i purely stopping to use Snapchat, and also due to the fact that the application is so badly optimized for Android (even since the complete redesign of the application), in the end considering my use so irregular, I just uninstalled it, so no problem.
The time of Snapprefs and Snaptools was fun and funny, and especially less vicious as a concept than the basic one.
The good old days, but all good things must come to an end.
Rom said:
snip
Click to expand...
Click to collapse
It's what happens when a company becomes complacent and puts more effort into blocking modifications instead improving their terrible app.
Update:
About 2 weeks ago, I flashed the May rom update for my Pixel 3 XL, installed Snapchat ver. 10.41.6.0, hid SC and all components of Google Play Services and Google Play Store in Magisk and I haven't been banned! I detach SC from the Play Store with TiBu but it somehow gets reattached. I just don't update it. Thanks @TevW !!!
I have got a problem, I have a Nokia 7 Plus, stock fw no changes at all!
And I keep getting banned... Support is a joke, I just get automatic replies...
The only reason i may have for getting bans is if snap scans the sd card, where I have magisk and roms files from other devices...
Any tips ???
newkydawg said:
Update:
About 2 weeks ago, I flashed the May rom update for my Pixel 3 XL, installed Snapchat ver. 10.41.6.0, hid SC and all components of Google Play Services and Google Play Store in Magisk and I haven't been banned! I detach SC from the Play Store with TiBu but it somehow gets reattached. I just don't update it. Thanks @TevW !!!
Click to expand...
Click to collapse
I tried to follow the instructions but snapchat keeps saying there was a connection problem with the server.
TevW said:
I'm copying this from the SnapFreedom thread who's problems obviously mirror your own. I'll be editing parts out, but some of it should still apply if you guys are getting locked out.
XPrivacyLua
Install it from FDroid or Xposed Repo and check the boxes for "Determine activity" and "Get applications" in Snapchat's tab. You can also enable "Get location" to spoof your location and still use SnapMaps.
Magisk
A few points, these probably don't apply, but they're still worth doing.
Repackage it through Settings -> Hide Magisk
Make sure to block all components under "Google Play Services" and "Google Play Store". There's a few things that aren't blocked by default that might trigger SafetyNet.
Snapchat
Hoo boy...
Don't use anything higher than, and including, 10.41.6.0. It's pretty much a ban-fest. With SnapTools, we use 10.20.5.0 and 10.26.5.0. Those are probably your safest bets. Also, if you plan on downgrading, use any 10.39 app. Something in how logins work has changed in the later versions, so apps like Preferences Manager don't work.
Theming your app should be okay. I did it for months and never got a ban.
Only give it the bare minimum permissions. Storage, Camera, and Microphone. Location too, if you're into being tracked by your friends and Snapchat.
Do NOT use modified apps. At all. Ever. They're the easiest things to detect.
If you want to block ads reliably, you can use this Magisk Module. This WON'T stop bans.
Snapchat also logs your device ID. If you've received a temp-ban prior to this, make sure to change your Device ID. If you're on Oreo, you can use this app. If not, you can use Titanium Backup to change it. The latest version with this function is version 8.2.2. But honestly, the most reliable way is to reflash your ROM.
Click to expand...
Click to collapse
Does this mean that I can't use energized adblock magisk module? Do I have to use only the Snapchat adblock magisk module that you linked for any kind of adblocking on the device.
Thanks!
Im on MIUI global 10.3.3. For me the app permissions get reset randomly. Like for example, WhatsApp gets the contacts permission revoked all of a sudden and i have to regrant the permission. Is anyone else facing a similar issue?
Happened the same to me
Happened the same here, MIUI 11, Android Pie, Redmi Note 8 (ginkgo).
I had temporarily turned off the MIUI optimizations from the developer settings, but I almost immediately re-enabled them. I hope it won't happen again.
Let me know if you find anything useful about it, there's absolutely no useful Google result about this.
Me too, some apps will randomly get its permission revoked. One instance I was using the app, I force closed it, when I opened it again it asked for permission again. Maybe something related to apps not being closed properly?
Sent from my Mi 9T Pro using Tapatalk
I think it is related to MIUI optimization
I think it is related to MIUI optimization in some way I am also getting same issue with my K20 pro only thing i have done is switching MIUI optimization off for around 10 min for installing Vanced.
Kashdelhi said:
I think it is related to MIUI optimization in some way I am also getting same issue with my K20 pro only thing i have done is switching MIUI optimization off for around 10 min for installing Vanced.
Click to expand...
Click to collapse
Yes, MIUI Optimization on/off resets things.
However, it is not needed to switch MIUI optimization to insttall Vanced YT (at least for root version) - their Manager just wrongly warns/asks to switch it off (I installed Vanced YT several times in the last two months, only with Install via USB option enabled in Developer menu)
Hello,
my Oneplus 7+ is running stock Android 11. Magisk has been installed and since a month ago everything was working fine (even DKB TAN2go and other banking apps). Last month an update for Comdirects Photo TAN was released and it stopped working. Luckily I was not the only one to encounter it and the description from @ralphabt here solved the issue for me.
Since this morning Google Pay stopped working (of couse I only noticed when I tried to pay and had my wallet nearby). SafetyNet fails (basic and cts). If I disabled the modules that I installed for the PhotoTan fix, SafetyNet is working again.
I found the MagiskHide Props Config, which I don't have a problem installing and testing, but I was wondering if there anything else I can try before fixing an issues that is caused by a solution for another issue.
Thanks a lot!
If SafetyNet now triggers from the Riru/EdXposed stuff you'll likely have to wait for an update to those modules (or try the latest beta/alpha/canary releases). Or try LSPosed instead (seems like more people have success with that). It's a cat and mouse game...
Im still waiting for anyone to give me a valid reason to use Xposed of any sort....
I pulled it out recently after jettisoning Xposed back in Marshmallow days, and was completely unsurprised that in my attempts to avoid root detection when i was having bank app issues it just broke things harder
Your biggest issue is getting SafetyNet pass...
Getting Google Pay and banking apps is another level...
My current setup for working bank apps (my bank at least) and working Samsung Pay & Google Pay is, should you wish to have a crack:
Magisk Alpha - here (second most recent at time of posting) or here for latest:
Riru - here
Riru-Momohider - my own mod of that module attached to my post here (where i just added creation of the 4 optional config options to the installations script, to avoid manual jiggery pokery, touching 4 files in a terminal every ROM flash didnt seem like a fun thing after the 3 ROMS i tested that week i started using Riru-Momohider)
Im talking those are the only modules i use. Even a simple font replacement module will give up a system modification to most root detection apps. So no fonts, no emojis swapping, no fiddly shizz. Keep it simple.
You can get an idea of what may be setting things off via Magisk Detector here, or VD Infos here (apologies to Didge, as mentioning that may be a trigger )
And i now get to tell you that this only currently works on 2 ROM's for my device, all the others cough up the existence of root through modifications made by devs to build.prop etc
So even in the best circumstances, and with all the right magisk and riru modules, the ROM youre using can still betray you.
Isnt that fun?
Worth pointing out (so frequently am i pointing this out these days im thinking of removing the link to my GPay Magisk Module from my sig) that for like 6 months now its been unnecessary for a lot of people to
a) Use the Google Pay db fix originally sussed out by @BostonDan, or my Magisk Module that does the same thing
and
b) Enable MagiskHide for Google Pay...
Actually getting SafetyNet is rather easy - if I remove EdXposed and XPrivacyLua it is working again and Google Pay as well. I only installed (my only reason) it, as it was required to get that banking app running.
I am using different banking apps and it the past the one from german DKB was rather difficult, but with newest Magisk (23) and Magisk Hide it is working.