I saw there are a lot of interesting modules for pogo and I cant use them because it recognizes xposed..
In addition, the systemless xposed works for me only when magisk hide is off, is there any option to use them both? Thanks
(S8 plus, oreo, magisk v18)
No, Xposed will always trigger safetynet. Magisk module was created in order to make it easy to disable and enable it
Try to use "no device check" Xposed module.
Wysłane z mojego Redmi 4X przy użyciu Tapatalka
This has been brought up quite alot, and there really is no need for me to post anything about it again. But... To clarify some more on the above posts (and give me a perfect excuse to procrastinate a bit on my paper due on friday ):
Xposed cannot currently (and likely never) be hidden. On older systems this was possible but Google changed something in a security update (november 16, maybe?) and now it can't be done.
The "No Device Check" Xposed module that @Robert342 talks about above can be used to fake a CTS profile response, but that's about it. In the past, Pokemon Go only used the Basic integrity check (so the "No Device Check" module would be useless), but nowadays it also checks for a whole host of other things, like Busybox apps, root hiding apps, etc, and if I remember correctly the Xposed installer as well.
There might be some way of getting things running with PoGo (VirtualXposed, maybe), but I've never bothered to dig deeper into that kind of stuff (and I haven't actually used Xposed since Marshmallow). Too much effort... Would be much easier to just keep an untouched device for playing the game and another for all your rooting and modding needs.
And now for some semantics: It's not Magisk's SafetyNet, it's Google's. The Magisk Manager just uses Google's APIs for making a security check against their servers so you easily can check if MagiskHide is working as it should. And you can actually have the Magisk systemless Xposed module installed and still pass SafetyNet (as @azZA_09 is hinting about above). You'll just have to deactivate it and reboot whenever you need to pass SafetyNet and then reactivate it and reboot when you're done...
It's funny how just days after this last comment, EdXposed was released.
Also, it's even more funny that I only got to discover it today, after the despair that hardware-backed remote attestation in safetynet now is.
I guess it was a good year for some people at least.. And perhaps older phones not shipping with keymaster 2 might still enjoy escaping
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!
Hey, folks,
I have a question about the risks involved in using Magisk on the phone and also Xposed. Using Magisk and Xposed has always been elementary for me, however, I have never used my bank account on my phone as I am afraid of being vulnerable for using these applications. In my new job the use of my banking application is mandatory so I don't know if I should uninstall Magisk and Xposed. What do you guys think? Is it advisable to manage money on your phone with these applications installed?
thank you
Can you even run the banking app with xposed installed? It breaks safetynet and apps probably check for that. As for magisk yeah it's perfectly fine.
Hi,
I haven't had any problems. Being unable to sit up in front of a PC/Laptop, I handle *everything* on my phone.
Of course, like anything important, use proper security measures. Using a VPN is advisable. Look at places like the Android Authority Tech Store. They have deals here and there. I've purchased "Lifetime" (20 years) deals on 2 different quality VPN services, one for $20 and the other for $40. One goes out, or even out of business, I've got the other and my money's worth long ago, so no big deal.
I also use Avast! Anti-Virus (not asking for opinions), as it's Free. There's also an app that scans for cell specific stuff that "spies" on what your doing, called "Incognito" for $2-$3 (one time).
Use what you feel good about, that's just me. Just use common sense as always, of course.
But no, I have not had any issues. So either I'm secure, or they've gotten in, saw how little there is and decided that I need it more than they do and are probably working on ways to put money *in* for me.
TTYL
Posted from my way cool LG V20 (H910) Nougat 7.0
From my experience Magisk is completely safe, it hides root very good. Some banking apps might still recognize it and block it, but you can try hide the app in the magisk manager section or even generate a random package name for the magisk manager itself if the bank app still finds it.
Also, using EdXposed (the new "unofficial" version for oreo and pie) won't affect safetynet, but again some apps might recognize it. There is a module for that called "rootcloak", it hides root, xposed and particular keywords that you can manually add, from some apps you can choose.
Last time I tried that was 2 or 3 months ago, and my banking/security apps worked normally without any problem. You just have to play around a little with those hiding-settings when you flash them the first time, that's it.
Hello,
today my phone suddenly wrote to me that it is no longer possible to use google pay.
Phone Pixel 5. Stock firmware.
Google pay reports that the device is certified.
I use magical canary 23001. I have the safetynet fix module installed.
Google pay does not work. And magisk reports an error when verifying the safetynet.
Any help please?
Just to say that the same occurred to me on a Oneplus 8 pro: Google Pay says the phone is not safe and Safetynet fails with basicintegrity (-), ctsProfile (-) and evaltype = basic. The cause seems to have been a Google Pay update two days ago (or, more probably, Google Play Services or the like, since I had disabled Google Pay updates). I have universal safetynet fix and magiskhide props config installed. If anyone could help, I'd appreciate. Let me know if I have to post more information. Thanks
UPDATE - A guy on Reddit says he fixed it by uninstalling EdXposed. Actually, I had that module and removed it and now I seem to pass the safetynet test, although Google Pay still has some issues (I will try cleaning data and cache, and possibly do the same to Google Play Services, I am also trying to put Google Services Framework under Magiskhide...). He says LSPosed (instead of EdXposed) should be fine, which it apparently is.
andrearesti said:
UPDATE - A guy on Reddit says he fixed it by uninstalling EdXposed. Actually, I had that module and removed it and now I seem to pass the safetynet test, although Google Pay still has some issues (I will try cleaning data and cache, and possibly do the same to Google Play Services, I am also trying to put Google Services Framework under Magiskhide...). He says LSPosed (instead of EdXposed) should be fine, which it apparently is.
Click to expand...
Click to collapse
Thanks for this update. Was having the same issue on my OP6T. I had already eyed at switching to a different Xposed clone since this keeps occuring every few weeks. Maybe now is a good time as ever.
Great. Thanks you so much.
Hey, I did things like:
-Applied Magisk Hide
-Selected all in Push TAN
-Applied package rename of Magisk
And s push tan still detects fcking root/ magisk.
The only way it works is to freeze the magisk app with another app. But this solution is trashy and I dont want to every time freeze magisk if I need s push tan.
Are there some fixes? Or even APK edits which I can install?
#****ThoseBankingApps
You can rebuild the stub as described/discussed in this github issue:
https://github.com/topjohnwu/Magisk/issues/1084
Didgeridoohan said:
You can rebuild the stub as described/discussed in this github issue:
https://github.com/topjohnwu/Magisk/issues/1084
Click to expand...
Click to collapse
fck off dude. Where its "described" in your eyes? There is nothing usefull and not even links BRUH
Suakey said:
fck off dude. Where its "described" in your eyes? There is nothing usefull and not even links BRUH
Click to expand...
Click to collapse
It is, but you might have to scroll back quite a few posts (it'll be from August or September, IIRC).
And please be mindful of your language. I'll let it slip this one time, but before posting anything further I suggest you take a look at the forum rules.
Hello again. A small update with some background info I didn't have time to add earlier...
The reason it's almost impossible to hide the Magisk app, even with it repackaged with a random name, is Android's poor privacy. Up until now, any app could query any other app on your device... Now that should change though. From August 2021 all new apps and from November 2021 all app updates in the Play Store will be forced to target API 30 (Android 11). This means that they're forced to conform to new privacy changes that make it so that they no longer can query other apps on your device.
In other words: the real solution is to wait until S-Push TAN gets its next update or so and it should no longer be able to detect the Magisk app.
Didgeridoohan said:
Hello again. A small update with some background info I didn't have time to add earlier...
The reason it's almost impossible to hide the Magisk app, even with it repackaged with a random name, is Android's poor privacy. Up until now, any app could query any other app on your device... Now that should change though. From August 2021 all new apps and from November 2021 all app updates in the Play Store will be forced to target API 30 (Android 11). This means that they're forced to conform to new privacy changes that make it so that they no longer can query other apps on your device.
In other words: the real solution is to wait until S-Push TAN gets its next update or so and it should no longer be able to detect the Magisk app.
Click to expand...
Click to collapse
Thanks for this information.
But how can it be that the devs of Magisk cant block those requests of other apps? I mean then "magisk HIDE" is completely nonsene in my eyes.
Suakey said:
Thanks for this information.
But how can it be that the devs of Magisk cant block those requests of other apps? I mean then "magisk HIDE" is completely nonsene in my eyes.
Click to expand...
Click to collapse
MagiskHide (and from now on Deny) hides what Magisk (the actual service, not the app) changes. Because of the above mentioned privacy limitations in Android up until Android 10 it has been practically impossible to fully hide the app without Xposed style modules (of which there are a couple that also can do the job). Since Magisk isn't Xposed (or at least hasn't been up until now when Zygisk now is live) it's been impossible for Magisk to do this by itself. And now there's no longer any need once the A11 updates for the apps on the Play store goes live (hopefully).
Didgeridoohan said:
MagiskHide (and from now on Deny) hides what Magisk (the actual service, not the app) changes. Because of the above mentioned privacy limitations in Android up until Android 10 it has been practically impossible to fully hide the app without Xposed style modules (of which there are a couple that also can do the job). Since Magisk isn't Xposed (or at least hasn't been up until now when Zygisk now is live) it's been impossible for Magisk to do this by itself. And now there's no longer any need once the A11 updates for the apps on the Play store goes live (hopefully).
Click to expand...
Click to collapse
So that means actually that I have zero chance because im on Android 10? XD...