Rooting with Magisk and it works until I rebooted the phone.
I'm also following instructions on how to use Google pay with a rooted device and not able to get it working. Hiding Magisk Manager and Google pay
cassato said:
Rooting with Magisk and it works until I rebooted the phone.
I'm also following instructions on how to use Google pay with a rooted device and not able to get it working. Hiding Magisk Manager and Google pay
Click to expand...
Click to collapse
None of that is currently working.
The only way I actually got root to stay was installing core values, then changing those values after it was installed.
I'm not the best explaining this stuff but if you want to inbox me I'm sure I can walk you through it.
Related
Anyone else having an issue with Android Pay. I am rooted (systemless) and finally decided to add a card to Android Pay. I've been able to get into Android Pay and tap the plus button to add the card just to test that it would work. I'm just now getting around to setting it up now. This time however tapping the plus button, I get the error message when you are rooted the traditional way. I didn't install any new apps that weren't directly from the Play store or that use root in any way.
I checked and noticed Android Pay was updated though. I went ahead and rebooted and was now able to add a card. But in the middle of adding another card I got the same error message. I dismissed it and was able to add another card. For some reason I could not add my Bank of America Visa though. So I haven't used it yet at a terminal. Anybody seen this issue?
synnyster said:
Anyone else having an issue with Android Pay. I am rooted (systemless) and finally decided to add a card to Android Pay. I've been able to get into Android Pay and tap the plus button to add the card just to test that it would work. I'm just now getting around to setting it up now. This time however tapping the plus button, I get the error message when you are rooted the traditional way. I didn't install any new apps that weren't directly from the Play store or that use root in any way.
I checked and noticed Android Pay was updated though. I went ahead and rebooted and was now able to add a card. But in the middle of adding another card I got the same error message. I dismissed it and was able to add another card. For some reason I could not add my Bank of America Visa though. So I haven't used it yet at a terminal. Anybody seen this issue?
Click to expand...
Click to collapse
Ugh. I was going to post that I hadn't seen this before, but before doing so I removed my discover card from AP and tried to add it again - got that dang error message you're referring to. Then rebooted my phone and tried to re-add it, and this time got further to where it says "contacting your bank" before again failing. Ugh Google why! Might try side loading the old version of AP see if that makes a difference.
EDIT: Very, very odd. I rolled back to the previous 1.1.1 version and tried adding the card again. The first time it failed instantly, but the 2nd time I tried (immediately after) it went through fine.
EDIT2: Just tried adding a completely different card after RE-updating to the latest version and it added perfectly fine right away the first time I tried. No idea what's going on here.
I might try going to a terminal later today to see if it works with the cards I already have added and I want that free Chromecast
I can't seem to add any more cards. They both say failed to verify info.
I was able to use Android Pay at the grocery store today. I still haven't been able to add any other cards thoug,even though I've waited 24 hours since adding the last two.
Decided to root today for the first time on this phone and I am also having this issue, so I went back to stock. I am on MMB29P. I had installed twrp, then flashed the systemless root version 2.66. Root was working fine, but the safteynet checker failed and I tried adding a card and got the Android Pay error. I have not tried the old method of installing the modified boot / SU... I just let 2.66 patch the boot image for me. I really just wanted to use Adaway too.
Edit: I guess adaway modifies the system partition, so that is probably why this wasn't working for me. Since that was the main reason for me to root, guess I'm staying on stock.
Read this thread on systemless root.
http://forum.xda-developers.com/nexus-6p/themes-apps/systemless-root-themed-apps-t3292105
If it were me though I would just flash the /unSU zip, then flash SuperSU 2.61 http://download.chainfire.eu/746/SuperSU/BETA-SuperSU-v2.61-20151207213702.zip . Then AP should just work without having to run any terminal commands. I've done it this way numerous times and it worked every time.
As for Adaway, if you flash the systemless hosts zip before installing Adaway AP will be unaffected.
Adaway thread http://forum.xda-developers.com/showthread.php?t=2190753
systemless hosts download https://www.androidfilehost.com/?fid=24269982087016285
I only ever add one card though.
And I don't have busybox installed (although I did install it previously and AP worked without issue)
So I can't add my Bank of America card because it can't verify my system, but I can still use android pay with the card I already have added. Not sure what to do at this point. Also want to point out the safety net app passes.
Ever since I rooted SC doesn't work for me at all. I'm on Android 6.0.1 and when I try to login it won't let me, yet on I'm old phone, which is rooted as well let's me. Help please!
Xenolife1234 said:
Ever since I rooted SC doesn't work for me at all. I'm on Android 6.0.1 and when I try to login it won't let me, yet on I'm old phone, which is rooted as well let's me. Help please!
Click to expand...
Click to collapse
Root breaks Snapchat login but once you're logged in, you can root and it will continue working. Unfortunately though, since you're already rooted, you can try to use something like RootCloak (no idea if that works with Snapchat) to hide the fact you're rooted or else unroot, login and then re-root.
@treela is correct.
I am on Nougat (NPJ25.93-14).
What I did - Rooted my phone using Magisk and enabled Magisk Hide.
Snapchat logs in even after rooting.
treela said:
Root breaks Snapchat login but once you're logged in, you can root and it will continue working. Unfortunately though, since you're already rooted, you can try to use something like RootCloak (no idea if that works with Snapchat) to hide the fact you're rooted or else unroot, login and then re-root.
Click to expand...
Click to collapse
OK will try that. Thanks!
treela said:
Root breaks Snapchat login but once you're logged in, you can root and it will continue working. Unfortunately though, since you're already rooted, you can try to use something like RootCloak (no idea if that works with Snapchat) to hide the fact you're rooted or else unroot, login and then re-root.
Click to expand...
Click to collapse
I'm confused what version of Xposed should I install? Arm, Arm64, or x86? I need Xposed before I get root cloak.
phh's superuser works fine with SnapChat. SuperSU does not in my experience.
Although, the foolproof way is to, on another device, install Snapchat, log in, THEN root, and install Titanium Backup and make a backup. After that, copy the files from your /storage/emulated/0/TitaniumBackup or whatever other directory (there should be a couple gzip files), and transfer those to an SDcard. On your new device, pop in the SD (or usb-otg), install Titanium Backup, transfer the files and then restore DATA ONLY. Just make a backup once and you shouldn't have to do it ever again.
I'm considering doing this https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 in order to get snapchat working again, but what's not clear is whether that process wipes the phone or not (I'm assuming it does).
I was going to try the "log into a second device then backup to first" process here https://forum.xda-developers.com/xposed/snapchat-rooted-phones-xposed-t3283198 but it looks like that doesn't work anymore?
There's also a post deleting a certain file https://forum.xda-developers.com/general/general/snapchat-rooted-devices-xposed-nougat-t3483001 but I get "operation failed" inside Root Browser whenever I try to rename, move, edit permissions for the file liboemcrypto.so
Current Android Version 6.0 and I followed the root process here: https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808 using the alternate SuperSU version.
The way I have always done it is just restore a backup with TB with data. I have had problems in the past, but another way would be to find a ROM with a root on/off switch (Like a CM base where you can enable/disable in dev options), unroot, log in to Snapchat, BACK UP TO TB (and save it in 9 places in case it gets corrupted somehow), and then root once again.
Going back to stock is pretty extreme for this issue honestly. You can work around it without going through that process. The reason the xposed process you linked isn't working is because of root, not JUST because of xposed. So those people would need to disable the xposed framework, then unroot, THEN log into Snapchat. They seem to be missing a step.
xgerryx said:
The way I have always done it is just restore a backup with TB with data. I have had problems in the past, but another way would be to find a ROM with a root on/off switch (Like a CM base where you can enable/disable in dev options), unroot, log in to Snapchat, BACK UP TO TB (and save it in 9 places in case it gets corrupted somehow), and then root once again.
Going back to stock is pretty extreme for this issue honestly. You can work around it without going through that process. The reason the xposed process you linked isn't working is because of root, not JUST because of xposed. So those people would need to disable the xposed framework, then unroot, THEN log into Snapchat. They seem to be missing a step.
Click to expand...
Click to collapse
What would happen if I tried SuperSU's "full unroot" function? Agree going back to stock is pretty extreme, but I also noticed I don't have the latest update, and presumably at some point I'll need to update to Nougat. There aren't any apps that I use that require root anymore.
Easiest way to use snapchat and root. Login to snapchat before rooting. Root. Do not log out of snapchat. Or you can go the magisk way with magiskSu and use magisk hide.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
chromatica86 said:
Easiest way to use snapchat and root. Login to snapchat before rooting. Root. Do not log out of snapchat. Or you can go the magisk way with magiskSu and use magisk hide.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
I just read the install guide for magisksu, it looks super easy, I'll try this first. thank you
I am trying to login to Snapchat but it keeps saying there's an error with the login and I found out it is because I am rooted. A fix I found involves full unroot and I don't want to do that. Can anyone help me?
Snapchat
Ive used snapchat rooted. On mutiple roms.
Snapchat for some devices (like the v20 now) is checking for root. It's hit or miss really. On my VS995 Snapchat wouldn't work till I did suhide. So you'll have to most likely use Magisk or SU-Hide or some kind of root hiding thing to get past it.
Just install Snapchat on a other device, log in, make a backup with Titanium Backup and load it on your main device.
This worked for my rooted S5 KLTE
D.Va said:
I am trying to login to Snapchat but it keeps saying there's an error with the login and I found out it is because I am rooted. A fix I found involves full unroot and I don't want to do that. Can anyone help me?
Click to expand...
Click to collapse
magisk hide is option 1
rootswitch is option 2
full unroot, sign in, then re-flash the supersu zip to re root is option 3
restore a app+data backup from a logged in device using backup app like titanium is option 4..
Team DevDigitel said:
magisk hide is option 1
rootswitch is option 2
full unroot, sign in, then re-flash the supersu zip to re root is option 3
restore a app+data backup from a logged in device using backup app like titanium is option 4..
Click to expand...
Click to collapse
Personally i feel option 2 is easiest but not all kernels like it.
I wish these things could be put in to roms so when we flash them, there's no alternate flashing needed that could cause issues.. I had nothing but issues tryna get both of those options to work, but again it was probably kernel related so I just gave up on it..
jdmsohc22 said:
I wish these things could be put in to roms so when we flash them, there's no alternate flashing needed that could cause issues.. I had nothing but issues tryna get both of those options to work, but again it was probably kernel related so I just gave up on it..
Click to expand...
Click to collapse
Actually, the Stock deOdexed US996 ROM has them built into it, also allows for hotspot provisioning without having to edit anything. I've been running it for a few months now, and been flawless on every aspect, other than it disables the ability to use MyVerizon apps, and Verizon's visual voicemail.
Im hoping someone can help me or possibly direct me to a youtube video to achieve what im looking to achieve
I struggled with, but finally managed to upgrade my device to stock 7.0, but rooted with magisk. When i tried to install xposed it forced a bootloop, so i restored a backup i had just made prior, and all has been well. I had wanted to install and use "Root cloak" as, at least so far thats been working on my 8.0 device (also Samsung, also stock but rooted but with SU method in that case, i couldnt get SU alone to work on my 7.0, for whatever reason)
I left it alone, but I'm noticing more and more that apps Id like to use come up saying "device is incompatible", which at first i thought it was weird as the play store itself allowed the install... but then upon some basic looking around, it seems that the apps have a way of detecting root, even through "magisk hide" - the feature directly included in magisk manager.
currently when i try to test for safetynet directly in the magisk manager, it doesnt actually properly test at all, no pass or fail, it just said unable
the rather peculiar part is that some of these apps arent all even banking apps, theyre for games. I cant figure out why gaming apps have issues with root access, especially when these apps themselves dont have root access, but thats kind of an aside
Any simplified help anyone can offer would be great! i am slightly familiar with editing the build prop, but i wouldnt know which values to change or even if that method is still effective. i used to use that on a quite older device (captivate glide) to spoof which version of android i was on in order to download app updates (which did work just fine, so why my older version wasnt supported is beyond me, lol)
thank you in advance for any help you can offer!