Related
Hey guys! I've recently ran into an issue where Snapchat will not let me login. I contacted their support and received the following:
Hi there,
Thanks for reaching out! I am so sorry you're running into this issue.
Some Snapchatters using a rooted Android device may experience issues using the app. Snapchat works best on devices running original software. Rooted devices - particularly those containing exploitation software - circumvent security defenses built into the mobile device, exposing your Snapchat account to additional risk and may not be supported.
If you are experiencing issues logging in and have a rooted device, you may want to try unrooting your device, removing any exploitation software, and reinstalling the app then logging in.
To learn more, please visit here.
Hope this helps! Happy to address any other questions or concerns you have.
Thanks,
Vanessa
The "here" leads me to https://support.snapchat.com/en-US/a/failed-login
Is anyone else having problems with Snapchat while rooted. Using Lite ROM, SuperSU, and no Snapchat apk mods.
Thanks!
Stock 7.0,rooted with Franco kernel and no issues with snapchat
Pure Nexus Nougat Rooted will not let me log in to snap chat.
I went to a stock, unrooted ROM, and Snapchat let me log right in. I think the most recent safetynet is getting us.
I installed magisk but it fails both the tests .I tried it in stock and custom sense rom. How can i get magisk to get to work?I followed the same procedures that is required for magisk to be installed.Do i have to do something else ?My os version is 5.0.2.
$urajM said:
I installed magisk but it fails both the tests .I tried it in stock and custom sense rom. How can i get magisk to get to work?I followed the same procedures that is required for magisk to be installed.Do i have to do something else ?My os version is 5.0.2.
Click to expand...
Click to collapse
Failed both what tests...?
If you're talking about within Magisk app for safety net and cts, did you enable Magisk hide from within Magisk app?
By the way, this isn't any form of development, and should have been posted in Q&A section of the forum...
Sent from my Pixel 3 XL using Tapatalk
santod040 said:
Failed both what tests...?
If you're talking about within Magisk app for safety net and cts, did you enable Magisk hide from within Magisk app?
By the way, this isn't any form of development, and should have been posted in Q&A section of the forum...
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Sorry for that. By the way does magisk support htc one m7 ( i mean the sense roms of htc one m7)? When i flash magisk hide in my other phone it was set to on by default but in htc one m7 it was off.When i turned it on ,it still failed both the tests.Can you confirm that magisk works in htc one m7 version 5.0.2?
Has anyone been able to get a hold of the Android 11 Pixel Launcher on their unrooted Pixel 4 XL (outside of side loading the 1st Developer Preview)?
https://www.apkmirror.com/apk/googl...elease/pixel-launcher-r-android-apk-download/
Haven't tried it yet.
omniatic said:
https://www.apkmirror.com/apk/googl...elease/pixel-launcher-r-android-apk-download/
Haven't tried it yet.
Click to expand...
Click to collapse
Yeah. I tried that link, but kept getting the "Having trouble parsing the package" message when attempting to install it
It's due to the generation of Android being greater than ours right now. I haven't seen that message in a very long time . I believe it with some editing on the Android package it can be modified to work..
You just need to edit the android manifest to match the current SDK, but after doing so it'll have to be installed as a system app through magisk if I remember correctly. It'll give a signature error.
Sent from my Pixel 4 XL using Tapatalk
So there's no way to install this if you're on Android 10 and don't have root... Man, that sucks. The launcher looks freaking awesome.
OxygenOS Open Beta 17 (OnePlus 7 Pro)
Changelog:
System
Newly added user assistance feature to help user master usage skills quickly(Route: Settings>OnePlus Tips&Help)
Fixed the abnormal error occured in Lockbox
Fixed the auto-start issue with QXDM logs after reboot
Optimized user experience with long screenshot in some scenarios
Updated Android security patch to 2020.08
Messages
Optimized the categorization, messages of the same contact now merged in one card（India only）
File Manager
Fixed the issue that File Manager did not display some downloaded documents of apps
Network
Improved the stability of Wi-Fi transfers
OxygenOS Open Beta 17 (OnePlus 7 Pro)
2.2 GB official download link:
https://otafsg1.h2os.com/patch/amazone2/GLO/OnePlus7ProOxygen/OnePlus7ProOxygen_13.W.41_GLO_041_2007291643/OnePlus7ProOxygen_13.W.41_OTA_041_all_2007291643_5f80f3e.zip
Local Upgrade OnePlus 7 Pro
1.) Download zip file OxygenOS Open Beta 17 2.2 GB from Official server
and copy it to the root of the internal memory
(i.e., not in a folder such as Downloads, for example).
2.) Go to Settings> System> System Updates> Click the gear at the top right>
Local Upgrade> Click on the appropriate installation package> Update
3.) After the update is completed, click Restart
4.) The update was successful.
Note If you do not see the firmware file, then check the file extension should be .zip
(if you have .zip.jar just rename it by deleting .jar)
Who already updated?
Who already updated? Is it safe to do so? No being locked out of device or something? ?
KennethHau said:
Who already updated? Is it safe to do so? No being locked out of device or something?
Click to expand...
Click to collapse
If you have OnePlus 7 Pro
and you want to install OxygenOS Beta 17
-----------------------------------------------------
This is the official Beta version.
It is installed and used without any problems.
KennethHau said:
Who already updated? Is it safe to do so? No being locked out of device or something? ?
Click to expand...
Click to collapse
Just done no issue
Sent from my OnePlus7Pro using XDA Labs
Thanks! Updated too and all is fine
Any news about one handed mode in this build?
Sent from my GM1913 using Tapatalk
sudanking said:
Any news about one handed mode in this build?
Sent from my GM1913 using Tapatalk
Click to expand...
Click to collapse
Nope..it's not available.
No buds compatibility included. Can someone pull the buds APK from the stable and upload it?
This changelog is lame, time for 11 beta already
Google Pay broken?
Is anyone else having issues with Google Pay?
I'm getting an error saying that the device is rooted or running an uncertified software.
EDIT: looks like SafetyNet is failing.
W.
maddler said:
Is anyone else having issues with Google Pay?
I'm getting an error saying that the device is rooted or running an uncertified software.
EDIT: looks like SafetyNet is failing.
W.
Click to expand...
Click to collapse
I am on OB17 and Safety Net passed. I don't use Google Pay so I cannot comment. I am stock, no root.
I am having bootloop issue on oneplus7pro with OOS openbeta 17 after flashed Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip,it was working on openbeta16,anyone here facing the same issue?
Did someone update with Magisk and system update yet (using TWRP Retention.zip)?
My phone is rooted and I have a custom kernel installed, is it safe to update?
I'm having bootloop on ob17 using latest twrp and magisk canary, modules disabled, stock kernel. Boots fine if magisk is uninstalled.
die_braut said:
Did someone update with Magisk and system update yet (using TWRP Retention.zip)?
Click to expand...
Click to collapse
yes and no problems
FlipmodeBG said:
I'm having bootloop on ob17 using latest twrp and magisk canary, modules disabled, stock kernel. Boots fine if magisk is uninstalled.
Click to expand...
Click to collapse
No issues here. Did not use TWRP retention, just flashed installer.
omar302 said:
I am on OB17 and Safety Net passed. I don't use Google Pay so I cannot comment. I am stock, no root.
Click to expand...
Click to collapse
The only other thing that changed recently is an update to Google Play Services (beta).
Can you confirm which version you've got there?
EDIT: ignore, downgraded Google Play Services to latest stable version and still failing.
Not sure what went wrong, but I guess the only solution is a factory reset at this point
Thanks!
W.
@Oswald Boelcke @Funk Wizard
I'm new on op7/p forums but I'm coming from op5 and they have dedicated pinned threads for all OB/Stable builds instead individual ones for each new build.
Is possible to have this? Is there any volunteer?
Enviado desde mi GM1917 mediante Tapatalk
I have two Xiaomi phones, one Redmi Note 8 and one Redmi Note 10, both with unlocked bootloaders. I made a fresh factory reset on them and installed the latest version of Magisk.
My problem is that SN basicintegrity fails on both of them (and ctsProfile as well of course). But I want to take care of basicintegrity first.
What I have done already is to enable MagiskHide and also Hide Magisk app with a custom name.
For MagiskHide, I selected all modules under "Google Play services" and "Google Play Services for AR". Not sure if I should select anything else. I also tested hiding with a root checker app and it looks that hiding works.
I have no Magisk modules installed. Using stock ROM on both phones.
Is there anything else I should to to pass basicintegrity SN?
API error?
If so, just wait for some days new version will solve this problem.
Pixel 3 XL on android 11 with magisk 22. Safetynet passed up until a few days ago. Not now tho. I wonder what changed?
Guys just put some more effort into searching, there is one big Magisk support thread and lot of discussion about this issue
Update to latest Canary
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Lord Sithek said:
Guys just put some more effort into searching, there is one big Magisk support thread and lot of discussion about this issue
Click to expand...
Click to collapse
It's difficult to find info in one big thread, not sure why that's how most discussion happens. Separate threads make more sense.
hkjo said:
It's difficult to find info in one big thread, not sure why that's how most discussion happens. Separate threads make more sense.
Click to expand...
Click to collapse
Multiplying posts doesn't make sense in my opinion. Several different threads were created for the same issue. It's not really that difficult to check few last pages of the main support thread since the issue is relatively new
Yeah, multiple threads on the same topic aren't good.
But one big thread that mixes different discussions beats the whole idea. Threads were invented for a reason. To concentrate discussion on a specific topic or sub-topic, and to have a sensible title. To save you from scanning posts in a megathread to find out if they're about your topic or not. Also, not all discussion is necessarily recent.
I had the exact same issue yesterday.
A quick search of the support thread took me to
The solution
wfred said:
I had the exact same issue yesterday.
A quick search of the support thread took me to
The solution
Click to expand...
Click to collapse
Hello,
Please, if you could—I hope you could—post the link to the solution you found. The masked link isn't working.
Thanks!
Cyb3rFr4nk said:
Hello,
Please, if you could—I hope you could—post the link to the solution you found. The masked link isn't working.
Thanks!
Click to expand...
Click to collapse
The linked solution is:
Update Magisk (to build 22103 or later).
This thread is about the Magisk apps SafetyNet checker extension needing an update due to an API error. SafetyNet wasn't actually failing...
If you need a few tips on how to get SafetyNet passing, there are some collected here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
Cyb3rFr4nk said:
Hello,
Please, if you could—I hope you could—post the link to the solution you found. The masked link isn't working.
Thanks!
Click to expand...
Click to collapse
Here you go, don't know why it was messed up
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Basically it was moving to the canary
Didgeridoohan said:
The linked solution is:
Update Magisk (to build 22103 or later).
This thread is about the Magisk apps SafetyNet checker extension needing an update due to an API error. SafetyNet wasn't actually failing...
If you need a few tips on how to get SafetyNet passing, there are some collected here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
Click to expand...
Click to collapse
Thank you!
I had visited the link to your site, through Google search, while searching for a fix. I also went to magisk general discussion thread, and started reading from April 23rd backwards, in a bid to locate/trace "the solution." While doing that, I came across "the solution," but didn't really try that as I'm on a later stable build (23000) than that canary build.
Background: I started facing this issue, yesterday, after I installed 23.0, from 20.4—which I had been on for a long time and didn't really want to upgrade from to avoid something like this, but after updating my Redmi Note 7 to MIUI 12.5 (Q) (I'm on xiaomi.eu stable), I started having restarts. So, I made the jump.
The restarts stopped after uninstalling that build, so I decided to upgrade to the latest stable. Did that, only to find that SafetyNet no longer passes. Basic integrity fails, and that was before installing EdXposed, which usually causes this. When I first noticed it, I checked my Play Store for device certification status, and it came out positive. That changed after a couple of reboots—I don't know which one in particular, as there were quite some during that time.
I've tried everything—except uninstalling and re-installing magisk—without success: different versions of Universal SafetyNet Fix, MagiskHide Props, enabling and disabling MH.
I have decided to put up with it. Since only a couple of my apps are affected (no GPay in my country), I am trying to make do without them until I get my new phone. Don't wish to do something that would require a factory reset/data wipe, as this is currently my DD, and I'd hate to get stranded.
Thanks all the same.
wfred said:
Here you go, don't know why it was messed up
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Basically it was moving to the canary
Click to expand...
Click to collapse
Cyb3rFr4nk said:
Thank you!
I had visited the link to your site, through Google search, while searching for a fix. I also went to magisk general discussion thread, and started reading from April 23rd backwards, in a bid to locate/trace "the solution." While doing that, I came across "the solution," but didn't really try that as I'm on a later stable build (23000) than that canary build.
Background: I started facing this issue, yesterday, after I installed 23.0, from 20.4—which I had been on for a long time and didn't really want to upgrade from to avoid something like this, but after updating my Redmi Note 7 to MIUI 12.5 (Q) (I'm on xiaomi.eu stable), I started having restarts. So, I made the jump.
The restarts stopped after uninstalling that build, so I decided to upgrade to the latest stable. Did that, only to find that SafetyNet no longer passes. Basic integrity fails, and that was before installing EdXposed, which usually causes this. When I first noticed it, I checked my Play Store for device certification status, and it came out positive. That changed after a couple of reboots—I don't know which one in particular, as there were quite some during that time.
I've tried everything—except uninstalling and re-installing magisk—without success: different versions of Universal SafetyNet Fix, MagiskHide Props, enabling and disabling MH.
I have decided to put up with it. Since only a couple of my apps are affected (no GPay in my country), I am trying to make do without them until I get my new phone. Don't wish to do something that would require a factory reset/data wipe, as this is currently my DD, and I'd hate to get stranded.
Thanks all the same.
Click to expand...
Click to collapse