Related
So, with Snapchat not working with anyone with a rooted device is there a workaround? Or do we have to wait until there is a work around? i've tried Xposed and some frameworks but that doesn't work either.
I only updated my phone today and haven't had an issue with Snapchat and root so I have no idea how long it's been going on for. Been looking across the internet and can't really come across anything solid so far, so apologies for another thread on the subject.
Sorry if this is the wrong area too.
Only solution I've found is us use the SuperSU app to uproot, then log in to SnapChat, then reroot.
If I unroot will that reset my phone or anything?
Once you do manage to log in, make a TB backup so you can restore the log-in in the future without having to unroot.
i can't log into Snapchat at all
rizb said:
So, with Snapchat not working with anyone with a rooted device is there a workaround? Or do we have to wait until there is a work around? i've tried Xposed and some frameworks but that doesn't work either.
I only updated my phone today and haven't had an issue with Snapchat and root so I have no idea how long it's been going on for. Been looking across the internet and can't really come across anything solid so far, so apologies for another thread on the subject.
Sorry if this is the wrong area too.
Click to expand...
Click to collapse
snapchat and root are no problem the problem is that snapchat check if xposed is installed or not that's why it won't log in...snapchat don't work if xposed is installed...
uninstall xposed through twrp and log to snapchat after that re-install xposed twrp
- tapatalked - from my VANTABLACK S7 EDGE
Perfectdevil said:
snapchat and root are no problem the problem is that snapchat check if xposed is installed or not that's why it won't log in...snapchat don't work if xposed is installed...
uninstall xposed through twrp and log to snapchat after that re-install xposed twrp
- tapatalked - from my VANTABLACK S7 EDGE
Click to expand...
Click to collapse
I don't have Xpsoed installed at all, that's what i'm confused about .
You can login snapchat, but you have to install systemless supersu + systemless xposed +suhide + magisk7
I can get pass safetynet check (checked today)
What I ended up doing, which works, is I wiped my phone on TWRP, reinstalled my firmware (superman) chose not to install root/Xposed, downloaded/signed into Snapchat, then rooted my phone. Long winded but it works.
Backup your snapchat data from a unrooted phone. I used titanium and restore on rooted
Just use Casper instead of original snapchat app.
Sent from my SM-G935F using XDA-Developers mobile app
You are unable to sign into Snapchat if you have the Xposed Framework enabled or Rooted.
(Rooted has never been a issue with me)
But Xposed framework is normally the cause, Even if you used Xposed or not, If the framework is present you cannot Login.
Simple Open up Xposed App (If you installed Via Superman you have have enabled to option and installed it)
From there you have a option to uninstall.
Reboot and once booted back up, login. Once logged in use Titanium Backup to backup the App plus Data.
Reinstall Xposed Framework and you should still be logged into Snapchat.
If you ever have any issues, Delete the app and restore from your backup, you have no need to uninstall Xposed as the Data is restored from the app keeping you logged into the app
mtk- said:
You can login snapchat, but you have to install systemless supersu + systemless xposed +suhide + magisk7
I can get pass safetynet check (checked today)
Click to expand...
Click to collapse
Hi, If im already rooted with supersu by chainfire and xposed installed what is the next step i have to do for install systemless, suhide and magisk or i have to start all overagain? Thanks
Sent From My Samsung Galaxy S7 Edge Duos SM-G935FD
_u2pop_ said:
Hi, If im already rooted with supersu by chainfire and xposed installed what is the next step i have to do for install systemless, suhide and magisk or i have to start all overagain? Thanks
Sent From My Samsung Galaxy S7 Edge Duos SM-G935FD
Click to expand...
Click to collapse
I have heard that just using suhide is enough to pass Snapchats new Root detection.
I have not tested as am still running the old version with Snaprefs
dave7802 said:
I have heard that just using suhide is enough to pass Snapchats new Root detection.
I have not tested as am still running the old version with Snaprefs
Click to expand...
Click to collapse
I hadnt had any problems whit SC and root untill 2 days ago either, easy fix is to unroot through the SU app, log into snap, and reflash superSU from TWRP.. worked for me
Firething said:
I hadnt had any problems whit SC and root untill 2 days ago either, easy fix is to unroot through the SU app, log into snap, and reflash superSU from TWRP.. worked for me
Click to expand...
Click to collapse
What option you used in SuperSU to unroot? I tried permanent unroot and it didnt work
Hello,
I've got a question about snapchat.
I'm sorry if im posting this in the wrong place, im new here!
I want to use snapchat 9.3.1.0 so i can use snapprefs.
I'm rooted and have xposed framework installed.
I am currently logged in in the newest snapchat version.
I made a backup of my snapchat with TB, deleted the new version of snapchat, installed snapchat 9.3.1.0, opened titanium backup and restored 'DATA ONLY'.
When i open snapchat, the app says: There are no snaps, and it says i've got no friends (which makes me sad). Any idea how i can fix this?
Thank you!
Lorenzo
It seems they recently changed things in an update. I have a rooted device with exposed, running superman rom. I used to just turn the switch off inside xposed, restart, login to snapchat, turn xposed back on and it was fine as long as I didn't log out. Now, none of that works.
My solution was to go to recovery, dirty flash my rom without root or xposed, login to snapchat, and go back and dirty flash again with root and xposed.
Way too much effort for snapchat, but it worked!
madhub said:
Just use Casper instead of original snapchat app.
Click to expand...
Click to collapse
We have a winner.
Firething said:
I hadnt had any problems whit SC and root untill 2 days ago either, easy fix is to unroot through the SU app, log into snap, and reflash superSU from TWRP.. worked for me
Click to expand...
Click to collapse
This worked. Thanks!
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
squandry said:
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
Click to expand...
Click to collapse
If it's in the context of getting pokemon go working, I think this might help get what you need: https://www.reddit.com/r/TheSilphRo...around_for_the_pokémon_go/?sort=new&limit=500
squandry said:
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
Click to expand...
Click to collapse
It's working for me with android pay.
Safetynet is passing for me using Magisk v9 & phh's Superuser r266-2, but a new version of each was released last week that chatter in other forums seem to suggest device-specific trouble with. I might try but first wanted to know if anyone else in the LePro3 world already has and had problems. My current interest in safetynet is for Android Pay and DirectvNow.
suhridkhan said:
It's working for me with android pay.
Click to expand...
Click to collapse
Thanks!
robertzas said:
If it's in the context of getting pokemon go working, I think this might help get what you need: https://www.reddit.com/r/TheSilphRo...around_for_the_pokémon_go/?sort=new&limit=500
Click to expand...
Click to collapse
Linked method is outdated ever since the introduction of November security patch.
Magisk V10 and phh SU r266 working fine for me on 20s
Upgrading worked for me too and I like how safety net check is part of the new status screen.
Seems like known issue but installing Xposed caused safetynet to fail, both before and after upgrade. Uninstalling Xposed caused safety net to pass again.
Root working and safetynet still passing on my x727 after taking the Magisk Manager upgrade to Magisk 11.1 and MagiskSu.
are all of you on a stock ROM and bootloader locked, I am using lineage OS 13, but safety net fails? do you have any idea how to fix this, just wanted to use ANDROID PAY, or do I need to be on STOCK ROM, just don't like the EUI and the status bar icons and the way they look(it's just me). Any help would greatly be appreciated=)
I am on stock ROM and unlocked bootloader. Magisk lets the unlocked bootloader stay. I don't see how safetynet could be expected to fully pass on a non-OEM supported ROM, especially over the longhaul of the cat-and-mouse game.
I don't like EUI either but changing out the launcher and even the notifications pulldown with Play Store apps helps immensely, along with using Titanium to freeze the bloatware. The main EUI remnants left after that is the lockscreen, the settings application, and the recents screen which I tolerate so as to have safetynet.
I could not pass safety net, got CM13, with MAGISK installed. Dang=)
squandry said:
I am on stock ROM and unlocked bootloader. Magisk lets the unlocked bootloader stay but I don't see how safetynet could ever pass on a custom ROM.
I don't like EUI either but changing out the launcher and even the notifications pulldown with Play Store apps helps immensely, along with using Titanium to freeze the bloatware. The main EUI remnants left after that is the lockscreen and the recents screen which I tolerate so as to have safetynet.
Click to expand...
Click to collapse
Hi, Did this but after installing MAGISK, everything passed, except FINGERPRINT got disabled, says hardware not supported. Android Pay works,just went to gas station and tried it, works flawlessly. FINGERPRINT is the problem I'm seeing now. Thanks for any help.
Sent from my LEX727 using XDA-Developers Legacy app
You mean you can't use the fingerprint sensor to unlock your phone? I am not sure, that works fine for me.
squandry said:
You mean you can't use the fingerprint sensor to unlock your phone? I am not sure, that works fine for me.
Click to expand...
Click to collapse
Yup, what boot image did you install? I think the problem was the boot image I used, are you on the 20's now? thanks
I am running the aboot from dr4stic's 19s unlocked bootloader zip, everything else is from the stock 20s OTA zip.
Ok, I have spent several hours trying to make it work and now time to ask for help. I got Leeco LePro 3 with custom Ron based on EUI, and trying to get Magisk working. First I tried installing system less SuperSU and Magisk, but it failed safety check multiple times, so I tried uninstalling SuperSU and use Magisksu, but not I am not able to move forward. I installed Magisk manager and when it try to install Magisk manager it downloads but doesn't show way to install it, I even try flashing Magisk 12 zip using TWRP, but it fails to update. Can someone please help me with getting Magisk working with safety check?
bocondo said:
I even try flashing Magisk 12 zip using TWRP, but it fails to update. Can someone please help me with getting Magisk working with safety check?
Click to expand...
Click to collapse
Flashing Magisk with TWRP should work. What do you mean by it fails to update?
Hi,
I have a issue with Google Pay,
first of all I've made a succeful contact-less payment while BL was locked (linked paypal to g pay), but now after unlocking BL and flashing Magisk - I can't, it gives me an error on terminal 'Transaction rejected'
Ofc SafetyNet test passes, and google play store sees my phone as certified device;
Google play services, google pay, google play, paypal and phone are hidden in magisk manager.
So the question is - Have somebody made a succeful contact-less payment with unlocked BL on our OP6T?
Thanks!
it works here perfectly fine using magisk 17.3
Pokemon Go works also (and everything else)
I use Gpay everyday no issue
My op6t is also unlocked and root via magisk and I face the same problem, it worked the first time but now I keep trying to gpay in each store but it fails every time.
I'm using gpay on daily basis, I didn't need to hide it in magisk but you can try to clear gpay/paypal cache or reinstall it.
I'm on OOS 9.0.7 with Magisk 18.0
Yep, got the phone the day it came out, rooted it 5 minutes after it arrived, used pay every day since, never hid anything in magisk. I know that's little help but at least you know you've something going on with your specific configuration. I'm .7 with Magisk 18.0.
I've been using Google Pay on my phone every day since launch with unlocked Bootloader and Magisk. I never had a problem. Magisk 18 and OOS 9.0.7 right now.
Same here no issue with GPay linked with my Revolut credit card
And I have been using gpay with Magisk without issues. Bootloader is unlocked.
Unfortunately I'm not having the same luck with Pokemon go. Can you lead me in the right direction.... Do you have anything specifically set up in magisk hide I should be aware of. Main reason I still root is Pokemon Go.
Setup: OS 9.0.2 Magisk v.18.
---------- Post added at 09:56 AM ---------- Previous post was at 09:53 AM ----------
OnkeIM said:
it works here perfectly fine using magisk 17.3
Pokemon Go works also (and everything else)
Click to expand...
Click to collapse
Unfortunately I'm not having the same luck with Pokemon go. Can you lead me in the right direction.... Do you have anything specifically set up in magisk hide I should be aware of. Main reason I still root is Pokemon Go.
Setup: OS 9.0.2 Magisk v.18.
Sent from my [device_name] using XDA-Developers Legacy app
unlocked bootloader + root works always for me with this config:
- Magisk 18.0
- marked needed apps in "Magisk Hide"
- use " change Magisk package name"-option in settings
- install Magisk modul "MagiskHide Props Config"
- modul needs to setup in a terminal/console-app (open terminal, type "props" , follow option 1)
works for for me on Pokemon, GooglePay, Ingress and other all other apps that didn't started due root detection
Flakito97 said:
Unfortunately I'm not having the same luck with Pokemon go. Can you lead me in the right direction.... Do you have anything specifically set up in magisk hide I should be aware of. Main reason I still root is Pokemon Go.
Setup: OS 9.0.2 Magisk v.18.
---------- Post added at 09:56 AM ---------- Previous post was at 09:53 AM ----------
Unfortunately I'm not having the same luck with Pokemon go. Can you lead me in the right direction.... Do you have anything specifically set up in magisk hide I should be aware of. Main reason I still root is Pokemon Go.
Setup: OS 9.0.2 Magisk v.18.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
main reason should not be Pokemon Go since it is a multiplayer game...
The only thing i always do is
1. Change package name from magisk
2. Activate desired app in magisk hide
It always worked with every app I tried like Telekom App or Banking App.
Right now I don't have root anymore, I got my 6T replaced because of a dead pixel and currently don't want to increase my widevine level
OnkeIM said:
main reason should not be Pokemon Go since it is a multiplayer game...
The only thing i always do is
1. Change package name from magisk
2. Activate desired app in magisk hide
It always worked with every app I tried like Telekom App or Banking App.
Right now I don't have root anymore, I got my 6T replaced because of a dead pixel and currently don't want to increase my widevine level
Click to expand...
Click to collapse
Gotcha, well yes I did those but no luck.
No worries. Thanks for the response!
Sent from my [device_name] using XDA-Developers Legacy app
Randomly today without any change or update to my OnePlus 6t Google Pay told me "you can no longer use Google Pay in stores." My CTS match is good everything looks fine. Did they patch anything recently?
Sent from my ONEPLUS A6013 using Tapatalk
xlxcrossing said:
Randomly today without any change or update to my OnePlus 6t Google Pay told me "you can no longer use Google Pay in stores." My CTS match is good everything looks fine. Did they patch anything recently?
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I am seeing the same error starting last night and continuing into today.
alryder said:
I am seeing the same error starting last night and continuing into today.
Click to expand...
Click to collapse
Well at least I'm not alone which tells me they patched the CTS exploit...guess we will have to wait for a possible magisk update.
Sent from my ONEPLUS A6013 using Tapatalk
Before I begin this is just a workaround but works flawlessly and you will be able to use google pay again. uninstall the current version of google play services and google pay. You want to be on the previous version of google pay.. Then Google search previous version of google play services (I believe its 14.7.99). Install then restrict background data on both google play store and google play services and all will work great... Do not update either until magisk comes out with an update that will work with the latest play services update versions... This was driving me crazy until I gave this a try after all else failed... Have Fun Spending your Money!!!lol
anthony10126 said:
Before I begin this is just a workaround but works flawlessly and you will be able to use google pay again. uninstall the current version of google play services and google pay. You want to be on the previous version of google pay.. Then Google search previous version of google play services (I believe its 14.7.99). Install then restrict background data on both google play store and google play services and all will work great... Do not update either until magisk comes out with an update that will work with the latest play services update versions... This was driving me crazy until I gave this a try after all else failed... Have Fun Spending your Money!!!lol
Click to expand...
Click to collapse
Which version of Google Pay are you using? I got 2.84.237487748 and it's still working for now. At least the app opens normally & hasn't told me I can't use it. I haven't actually tried paying for something in a few days. And I think I just updated the GPay app within the last week.
FWIW, I'm still using Magisk 17.3 on OOS 9.0.12. With Magisk 18.x, Magisk Hide would stop working, SafetyNet checks would fail and the device would become uncertified. I've had no such issues with 17.3. Although I don't know if any of those things would cause Google Pay to stop working because even with those things happening, Google Pay has never stopped working for me. But now that I've said that, it'll probably will in 3, 2, 1....
sharksfan7 said:
Which version of Google Pay are you using? I got 2.84.237487748 and it's still working for now. At least the app opens normally & hasn't told me I can't use it. I haven't actually tried paying for something in a few days. And I think I just updated the GPay app within the last week.
FWIW, I'm still using Magisk 17.3 on OOS 9.0.12. With Magisk 18.x, Magisk Hide would stop working, SafetyNet checks would fail and the device would become uncertified. I've had no such issues with 17.3. Although I don't know if any of those things would cause Google Pay to stop working because even with those things happening, Google Pay has never stopped working for me. But now that I've said that, it'll probably will in 3, 2, 1....
Click to expand...
Click to collapse
I downgraded Google pay to 2.81. If you haven't used you're Google pay in the past few days chances are you're Google pay is not working. Google play services updates in the background without you knowing which is why I suggested turning off background data.. staying on magisk 17 shouldn't make a difference..
Even with only an unlocked bootloader it won't let you set up google pay (no twrp, no magisk, no root, just unlocked bootloader).
Hi,
im a little bit confused about this problem. From one day to another, G Pay stopped working with NFC. "This device cant be used because its rootet or modified."
I use Magisk with stock Rom severeal month now and gpay ran without any problems. The confusing thing is that I didn´t changed anything what could cause this behaviour.
What I already tried:
-GPay: Delete cache, uninstalled updates. Tried many times to activate NFC payment.
-Erased Cache in TWRP
-Installed complete offline OTA. (Root and TWRP was gone and it still wont work)
-Tried Magisk Hide and random app name.
Does anybody have an idea? I dont want to reset the whole phone for this or lock the bootloader.
Thanks for your help!
Did you update the Gpay app? Mine still works but I never installed the update
I've got the latest Google Pay version and it's been working fine.
What version of Magisk are you using? Do the SafetyNet checks pass? Does Google Play Store show that the device is certified? I've had issues with Magisk 18 & 18.1 where Magisk Hide would stop working and SafetyNet checks failing.
If you're on Magisk 18.x & SafetyNet checks fail for you, try uninstalling Magisk & Magisk Manager. Install version 17.3. Install Magisk Manager 6.1.0. Enable Magisk Hide and hide Google Pay and Google Play Store. Clear storage on Google Play Store. See if SafetyNet checks pass. Check that the device is certified. Try Google Pay again.
I don't know for sure that this will fix the problem with Google Pay, but it's what I've done after having issues with Magisk.
sharksfan7 said:
I've got the latest Google Pay version and it's been working fine.
What version of Magisk are you using? Do the SafetyNet checks pass? Does Google Play Store show that the device is certified? I've had issues with Magisk 18 & 18.1 where Magisk Hide would stop working and SafetyNet checks failing.
If you're on Magisk 18.x & SafetyNet checks fail for you, try uninstalling Magisk & Magisk Manager. Install version 17.3. Install Magisk Manager 6.1.0. Enable Magisk Hide and hide Google Pay and Google Play Store. Clear storage on Google Play Store. See if SafetyNet checks pass. Check that the device is certified. Try Google Pay again.
I don't know for sure that this will fix the problem with Google Pay, but it's what I've done after having issues with Magisk.
Click to expand...
Click to collapse
Magisk: 18.1 (worked with this version), Safety Net is passing (Thats why im so confused about it)
Playstore is showing me that it is certified.
I never had a failed SN check.
Probably because having a rooted phone, especially if you are using to send/receive money, opens up a SECURITY HOLE, even if you are using something to "bypass" google.
NOTHING is 100% safe, but, I for one, will never root my phone, if I am using it to spend money.
The days of rooting will be over one of these days. Google is locking down things more and more.
hlzocker said:
Magisk: 18.1 (worked with this version), Safety Net is passing (Thats why im so confused about it)
Playstore is showing me that it is certified.
I never had a failed SN check.
Click to expand...
Click to collapse
Make sure you have hide enabled for pay.
I'm on 18.1 and I don't have issues.
I fought with the same problem.
latest Magisk Canary build was the solution that worked for me:
https://forum.xda-developers.com/showpost.php?p=78946079&postcount=31551
Coumodo said:
I fought with the same problem.
latest Magisk Canary build was the solution the worked for me:
https://forum.xda-developers.com/showpost.php?p=78946079&postcount=31551
Click to expand...
Click to collapse
Yes, that solved the problem for me. Now the activation was successfull. Thanks!
Hey, all
Successfully upgraded and rooted my phone on Android 11 and have now discovered my banking app isn't working; it's crashing within seconds of trying to start.
I have Magisk itself hidden and my banking app, Navy Federal, checked under the MagiskHide section but it's not making a difference.
Anyone else having this issue and/or figured a way to resolve it?
Magisk hide isn't always going to work.
You could try hiding the magisk name but beyond that there isn't a lot you can do
@PassingInTime Are you passing the Safetynet check?
Yeh, see if magisk mgr is passing safety net...
XxSUPRAxX said:
@PassingInTime Are you passing the Safetynet check?
Click to expand...
Click to collapse
Magisk shows all pass. Firefox is actually crashing on launch now as well. Not sure what's going on yet, but I'm hoping to avoid resetting...again.
PassingInTime said:
Magisk shows all pass. Firefox is actually crashing on launch now as well. Not sure what's going on yet, but I'm hoping to avoid resetting...again.
Click to expand...
Click to collapse
What banking app has the issue? Ill test it out on my device.
Sometimes it's bank sided, when I rooted my device after updating to A11, my bank app didn't work and I thought it had something to do with root.
I ended up calling them, it turned out that they didn't update the app and after a couple of days I received an update and it's working again.
If it worked for you before root, try to hide Magisk, does it pass safetynet anyway?
EDIT: Just noticed that it passes safetynet, I'd suggest to restore stock boot and see if it works, if so, try rooting again.
Are you using beta canary?
roote3 beta 3 NFCU app works for me. magisk hidden and magisk name changed.
Enable USB debugging and use ADB logcat ... Start the app ... Stop the logcat and check for errors in the log ... Maybe you'll find why in there
cali310 said:
roote3 beta 3 NFCU app works for me. magisk hidden and magisk name changed.
Click to expand...
Click to collapse
Finally works for me too - took them awhile.