Related
Ever since I unlocked the bootloader on my nexus 6p and installed a custom ROM, I haven't been able to login to snapchat. It keeps saying "Oh no! Your login temporary failed. Please try again later". I thought this was a snapchat problem and I tried uninstalling/reinstalling, tried different snapchat app versions, and even reset my password. No luck. I thought my snapchat account was locked, until I used my sister's iPhone and it logged in with no problems.
Does anyone have any advice or solutions? Could this possibly be a snapchat security issue because my nexus 6p is unlocked/rooted?
There was something about how snapchat is check for root now. I have mine rooted and it still works. Im really not sure whats going on.
There are a fix for it just install xposed and then install snapprefs. Hope it help :")
Here it was fixed with xposed uninstaller, then log in, and reinstall xposed.
Just like @Novek mentioned, remove Xposed if you have it using Xposed uninstaller and then reinstall Snapchat from the Play Store. You should be able to log in now. Then once login is successful reinstall Xposed. Apparently Snapchat only checks for root/Xposed when logging in for the first time. Worked for me just this morning with cyanogenmod 13 and latest Snapchat beta from the Play Store.
just watch this and follow his steps
JHEJL10 said:
Ever since I unlocked the bootloader on my nexus 6p and installed a custom ROM, I haven't been able to login to snapchat. It keeps saying "Oh no! Your login temporary failed. Please try again later". I thought this was a snapchat problem and I tried uninstalling/reinstalling, tried different snapchat app versions, and even reset my password. No luck. I thought my snapchat account was locked, until I used my sister's iPhone and it logged in with no problems.
Does anyone have any advice or solutions? Could this possibly be a snapchat security issue because my nexus 6p is unlocked/rooted?
Click to expand...
Click to collapse
How to fix Snapchat login temporarily failed for android devices rooted just type in youtube "How to fix snapchat login temporarily failed for android (ROOT)" it's a video posted in 25.06.2016 just follow my steps. Xda forum wont let insert links because i just opened this account[/YOUTUBE]
This will fix that snapchat problem if you have rooted divece. Subscribe and like it please!
1.) Uninstall xposed and snapchat
2.) Once booted back, install the snapchat version you like and login
3.) Install xposed again (and stay logged-in!)
It has nothing to do with root - snapchat checks för xposed
Skickat från min Nexus 6P via Tapatalk
Is there a solution without removal of Xposed ?
tool Rootcloack does not work ..
I just received my 6P yesterday. I'm on 7.0 and rooted it right away. I'm now too having this snapchat login issue. However, if I'm not mistaken (I'm a noob, forgive me), 7.0 doesn't even have Xposed. If Xposed is supposedly causing the snapchat issue, how come I can't log in? I don't even have Xposed on my phone to delete. Please help!
Anyone found a fix for this yet?
Sent from my iPad using Tapatalk
devinthedude81 said:
I just received my 6P yesterday. I'm on 7.0 and rooted it right away. I'm now too having this snapchat login issue. However, if I'm not mistaken (I'm a noob, forgive me), 7.0 doesn't even have Xposed. If Xposed is supposedly causing the snapchat issue, how come I can't log in? I don't even have Xposed on my phone to delete. Please help!
Click to expand...
Click to collapse
New Rising said:
Anyone found a fix for this yet?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Unroot, login to SnapChat, then root. I don't use the app so that's all I can offer.
Sent from my Nexus 5X using Tapatalk
devinthedude81 said:
I just received my 6P yesterday. I'm on 7.0 and rooted it right away. I'm now too having this snapchat login issue. However, if I'm not mistaken (I'm a noob, forgive me), 7.0 doesn't even have Xposed. If Xposed is supposedly causing the snapchat issue, how come I can't log in? I don't even have Xposed on my phone to delete. Please help!
Click to expand...
Click to collapse
The latest update to safetynet also now checks for magisk. So if you have magisk v7 or really any other version, uninstall that, login and then reinstall if you want to. I had the same problem before but its all good now.
---------- Post added at 04:42 AM ---------- Previous post was at 04:41 AM ----------
SlimSnoopOS said:
Unroot, login to SnapChat, then root. I don't use the app so that's all I can offer.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
root doesn't effect snapchat in any way. I've been rooted forever and the only times ive ever encountered problems logging in is when i had xposed or magisk.
Falitheman said:
The latest update to safetynet also now checks for magisk. So if you have magisk v7 or really any other version, uninstall that, login and then reinstall if you want to. I had the same problem before but its all good now.
---------- Post added at 04:42 AM ---------- Previous post was at 04:41 AM ----------
root doesn't effect snapchat in any way. I've been rooted forever and the only times ive ever encountered problems logging in is when i had xposed or magisk.
Click to expand...
Click to collapse
It is root. Like the other guy said, Snapchat uses Safetynet now (same checks AndroidPay uses). You can use Suhide. That's what I did.
rquinn19 said:
It is root. Like the other guy said, Snapchat uses Safetynet now (same checks AndroidPay uses). You can use Suhide. That's what I did.
Click to expand...
Click to collapse
I've logged in and out multiple times with out using hidesu...the only thing that ever worked for me was uninstalling Xposed or magisk
Falitheman said:
I've logged in and out multiple times with out using hidesu...the only thing that ever worked for me was uninstalling Xposed or magisk
Click to expand...
Click to collapse
And this was within the last few days?
rquinn19 said:
And this was within the last few days?
Click to expand...
Click to collapse
Actually yes it was on Friday when I logged out of Snapchat the first time while having magisk installed. I was confused for awhile so I tried uninstalling magisk and it worked perfectly
So I unrooted using the SuperSU app logged into Snapchat then flashed SuperSU again and I'm good now. Thanks
Sent from my Nexus 6P using Tapatalk
Running 7.0 rooted. Systemless I believe, Snapchat will not login. No Xposed installed nor any majik. Amy ideas?
Are the pico gapps enough for snapchat or does it require any other g services?
MnRAZB said:
Running 7.0 rooted. Systemless I believe, Snapchat will not login. No Xposed installed nor any majik. Amy ideas?
Click to expand...
Click to collapse
It's because you're rooted I had the same problem. The guy in this thread saying root doesn't matter is mistaken. Unroot, log into Snapchat, rerooot, done.
Did anybody using Magisk 16 on Honor 8? My main concern is the Magisk Hide and the safety checks...
Since Magisk 16 there are some support on Honor devices but in the real life I am not sure if is a point to going away from SuperSU...
It works fine. Supersu was taken over by a Chinese company. Chel stopped reviewing code for it. So unless you like your privacy, stick with supersu.
agraceful said:
It works fine. Supersu was taken over by a Chinese company. Chel stopped reviewing code for it. So unless you like your privacy, stick with supersu.
Click to expand...
Click to collapse
Everything is about privacy in this days...
Which is the last version of SuperSU, which was maintained by Chel?
So for privacy point is better Magisk. How is the privacy in Magisk? That's a big question
Which version of Magisk you're using? I have FRD-L09C432b394 but I am wondering if the Magisk Hide and the safety checks will work, because this s known problem with Honor/Huawei devices. I see the support from v16 for Honor devices but I don't know what's clearly mean that.
it's been working fine for me including safetynet. Interestingly, I have to keep USB debugging enabled to pass safetynet
jasonvxs4 said:
Interestingly, I have to keep USB debugging enabled to pass safetynet
Click to expand...
Click to collapse
THANK YOU, THANK YOU, THANK YOU!
I was looking everywhere as to why it was passing before the update to B404 and now was failing!
Flicked the option and passing safteynet again!
agraceful said:
It works fine. Supersu was taken over by a Chinese company. Chel stopped reviewing code for it. So unless you like your privacy, stick with supersu.
Click to expand...
Click to collapse
jasonvxs4 said:
it's been working fine for me including safetynet. Interestingly, I have to keep USB debugging enabled to pass safetynet
Click to expand...
Click to collapse
linkazoid said:
THANK YOU, THANK YOU, THANK YOU!
I was looking everywhere as to why it was passing before the update to B404 and now was failing!
Flicked the option and passing safteynet again!
Click to expand...
Click to collapse
What version of Magisk you're using on which firmware?
dewadi said:
What version of Magisk you're using on which firmware?
Click to expand...
Click to collapse
V16 on B404, was also using v16 on B403 too
I noticed earlier that my usb debugging was switching straight off after enabling. Make sure this isn't happening to you. Click the reset to default button at the bottom and then select it again
I'm using 16.3. Almost every single magisk version released has worked fine for me. Chel doesn't maintain it anymore. You can use an older version of supersu but I'm not sure why you'd want to do that. As far as usb debugging.. i always have that on anyway.. i have an L04 and I'm on 392 firmware. Magisk is much better. I was very very hesitant when I switched, specially since it wasn't at the state it is now, but I'm glad i switched.
linkazoid said:
V16 on B404, was also using v16 on B403 too
I noticed earlier that my usb debugging was switching straight off after enabling. Make sure this isn't happening to you. Click the reset to default button at the bottom and then select it again
Click to expand...
Click to collapse
agraceful said:
I'm using 16.3. Almost every single magisk version released has worked fine for me. Chel doesn't maintain it anymore. You can use an older version of supersu but I'm not sure why you'd want to do that. As far as usb debugging.. i always have that on anyway.. i have an L04 and I'm on 392 firmware. Magisk is much better. I was very very hesitant when I switched, specially since it wasn't at the state it is now, but I'm glad i switched.
Click to expand...
Click to collapse
Did you tried Magisk 16.4?
Sorry if I'm hijacking.
Since you're talking about 16.3 and 16.4, does Magisk hide works?
That was my previous problem with rooting. I would like to remove some apps and add AdAway, while using Google Pay.
zinko_pt said:
Sorry if I'm hijacking.
Since you're talking about 16.3 and 16.4, does Magisk hide works?
That was my previous problem with rooting. I would like to remove some apps and add AdAway, while using Google Pay.
Click to expand...
Click to collapse
Anyone have any clue about this?
zinko_pt said:
Anyone have any clue about this?
Click to expand...
Click to collapse
that's what I am running
jasonvxs4 said:
that's what I am running
Click to expand...
Click to collapse
Magisk hide working?
jasonvxs4 said:
it's been working fine for me including safetynet. Interestingly, I have to keep USB debugging enabled to pass safetynet
Click to expand...
Click to collapse
Thanks for this trick man! I was puzzled as to why I was failing the SN check after passing it for a few hours.
I will retry flashing Magisk 16 :good:
takichiman said:
Thanks for this trick man! I was puzzled as to why I was failing the SN check after passing it for a few hours.
I will retry flashing Magisk 16 :good:
Click to expand...
Click to collapse
Magisk 16.4 works fine with Hide and fingerprint sensor.
zinko_pt said:
Magisk 16.4 works fine with Hide and fingerprint sensor.
Click to expand...
Click to collapse
Thanks for the info. I will reflash magisk 16.4 on a fresh stock L04B395 ROM and update you if the Safetynet fails
takichiman said:
Thanks for the info. I will reflash magisk 16.4 on a fresh stock L04B395 ROM and update you if the Safetynet fails
Click to expand...
Click to collapse
Safetynet passes in my L09C432B405.
zinko_pt said:
Safetynet passes in my L09C432B405.
Click to expand...
Click to collapse
I confirm that it passes on my L04C567B395. But because of that stupid USB debugging option that keeps getting turned off, I have to continuously toggle/untoggle the option and eventually sometimes plugging the phone to a computer to trigger the adb, so I can pass the safetynet test.
For the record I'm using Magisk 16.4
linkazoid said:
THANK YOU, THANK YOU, THANK YOU!
I was looking everywhere as to why it was passing before the update to B404 and now was failing!
Flicked the option and passing safteynet again!
Click to expand...
Click to collapse
WOW finally pass the safetynet!!!
Thanks alot!! I'm using magisk v17.1 with h8 frd10, what a magic!:highfive:
Apps seems to intermittently identify that phone is rooted on magisk 18.0... this seems to be known issue...any work around apart from unhiding and hiding the app again in magisk?
The problem only started happening for me after I updated to v18.0. Didn't have any problems with v17.3. So I just did a complete uninstall of v18.0 and re-rooted with v17.3. No issues since.
sharksfan7 said:
The problem only started happening for me after I updated to v18.0. Didn't have any problems with v17.3. So I just did a complete uninstall of v18.0 and re-rooted with v17.3. No issues since.
Click to expand...
Click to collapse
Yes, it seems to be problem after 18.0.. it's on canary build 18.1 as well
I have the same problem in v 17.3 although it occurs less frequently than in version v 18.0. There is no problem in my old nexus 5x so I think it's something related to oneplus lmk battery optimization. I don't know
I'm using 18.0 and never had that issue. Shot in the dark here, but could it be some modules you're using? Are you using any at the moment?
I have the same issue as well. A resolution would be very welcome.
H4X0R46 said:
I'm using 18.0 and never had that issue. Shot in the dark here, but could it be some modules you're using? Are you using any at the moment?
Click to expand...
Click to collapse
No mods.. it seems to be a known issue across many
17.1, never had this issue
H4X0R46 said:
I'm using 18.0 and never had that issue. Shot in the dark here, but could it be some modules you're using? Are you using any at the moment?
Click to expand...
Click to collapse
The only modules I've been using are YouTube Vanced and Systemless Hosts for ad blocking with AdAway. Would something with either of those trigger something that would cause SafetyNet Check to fail? And just to be clear on the issue, SafetyNet will pass initially. Then after some time, a few hours or so, if you check again it'll fail, even if nothing on the system has changed. Toggling MagiskHide off then back on, will get SafetyNet to pass again.
Glad you actually made this thread because I thought I was the only one experiencing this. Magisk 18.0 on 9.0.11 and safetynet will randomly fail to pass sometimes. Reboot always fixes this issue, but sometimes it just resolves on its own without a reboot.
---------- Post added at 09:20 PM ---------- Previous post was at 09:12 PM ----------
sharksfan7 said:
Toggling MagiskHide off then back on, will get SafetyNet to pass again.
Click to expand...
Click to collapse
Well thanks for saving me the hassle of rebooting :good: that worked right away
Gang,
March security patch details were just released: https://source.android.com/security/bulletin/2019-03-01.html
Updates will rollout soon.
arturiu said:
Gang,
March security patch details were just released: https://source.android.com/security/bulletin/2019-03-01.html
Updates will rollout soon.
Click to expand...
Click to collapse
Good to see they are making it more secure. Nothing new apart from it
Update has started...
Update just arrived Pixel 2 XL UK
Sweet. As soon as there are custom kernels available, I'm jumping in
Any Bluetooth fixes?
Sentheb3ast said:
Any Bluetooth fixes?
Click to expand...
Click to collapse
Nothing for Pixel 2/XL.
Mr Patchy Patch said:
Nothing for Pixel 2/XL.
Click to expand...
Click to collapse
What Bluetooth issues/fixes are we talking about ?
For some reason after updated to March security update, I can't access to Facebook app or Twitter on my pixel 2 XL. After deleted and reinstalled the app, now I can't logging on the app anymore. It kept saying internet connection error. Besides this, every thing else work. I've been running with the same set up and update process since July 2018.
Rooted stock pie with AML, DDP and Viper4androidFX Magisk modules.
my370z said:
For some reason after updated to March security update, I can't access to Facebook app or Twitter on my pixel 2 XL. After deleted and reinstalled the app, now I can't logging on the app anymore. It kept saying internet connection error. Besides this, every thing else work. I've been running with the same set up and update process since July 2018.
Rooted stock pie with AML, DDP and Viper4androidFX Magisk modules.
Click to expand...
Click to collapse
Factory reset, if I had to guess.
muppetmaster916 said:
Factory reset, if I had to guess.
Click to expand...
Click to collapse
Nope.... found the problem. Problem was one of the new host file for adaway cause this...I temporary disabled adaway and everything work now. Next step is remove the host file and enable adaway.
Anyone having issues once rooted (through Magisk) to update /etc/hosts file? I'm trying to use Adway and I can't update the hosts file, but have root access.
collegencmc said:
Anyone having issues once rooted (through Magisk) to update /etc/hosts file? I'm trying to use Adway and I can't update the hosts file, but have root access.
Click to expand...
Click to collapse
Do you have the "systemless hosts" enabled and installed in magisk manager?
Badger50 said:
Do you have the "systemless hosts" enabled and installed in magisk manager?
Click to expand...
Click to collapse
Got it working now with that! Thanks!
I updated my NP1 to NOS 1.1.7( with fix) and today to 1.5 beta. My device is not rooted with locked bootloader and still is not google certified and fails CTS. Any ideas on how to fix this?
I tried the default Universal SafetyNet Fix and it didn't work, I also tried using a custom fingerprint but it would break my fingerprint scanner, I ended up using a modded version of the fix it CTS is passing for me.
MarcoReckless said:
I tried the default Universal SafetyNet Fix and it didn't work, I also tried using a custom fingerprint but it would break my fingerprint scanner, I ended up using a modded version of the fix it CTS is passing for me.
Click to expand...
Click to collapse
My device is not rooted and the bootloader is still locked. I just installed NOS 1.5 beta by downloading the update zip for EEA and installing it with *#*#682#*#* etc. I tried to certify my device with google and see if anything can be done....
Chaotick said:
My device is not rooted and the bootloader is still locked. I just installed NOS 1.5 beta by downloading the update zip for EEA and installing it with *#*#682#*#* etc. I tried to certify my device with google and see if anything can be done....
Click to expand...
Click to collapse
I'm afraid you can't do anything while locked, we were warned that bank apps would break.
Chaotick said:
I updated my NP1 to NOS 1.1.7( with fix) and today to 1.5 beta. My device is not rooted with locked bootloader and still is not google certified and fails CTS. Any ideas on how to fix this?
Click to expand...
Click to collapse
it is normal for SafetyNet to fail in beta
in the mail from nothing it also says that netflix and googel pay / wallet does not work.
as soon as it is official A13 everything works again
MarcoReckless said:
I tried the default Universal SafetyNet Fix and it didn't work, I also tried using a custom fingerprint but it would break my fingerprint scanner, I ended up using a modded version of the fix it CTS is passing for me.
Click to expand...
Click to collapse
Thanks, the modded version works very well.