Hello, lovelies of XDA. I'm looking from some advice from those who better understand what they're doing, as I (like a true novice) have reached what seems to be a "point of no return" with my phone.
I'm using a Samsung Galaxy S4 that I have rooted and updated to Lollipop using the methods described in these threads:
http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
http://forum.xda-developers.com/gal...to-root-i337ucufnj4-4-4-4-11-13-2014-t2939553
http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
I went from Lollipop 5.0.1, to KitKat 4.4.4, got root access, then updated to Lollipop again via the KeepRoot thread. This took me forever, but everything seemingly worked fine. Until I messed it all up. I used TitaniumBackup to remove apps that were on the safelists on this forum after creating backups. However, I started receiving an "Unfortunately, Google Play Services have stopped." error message every time I tried to add a new Google account in my phone's settings. In my efforts to attempt to fix this, I managed to delete the Google account that was working on the phone, and now I have no access to Google Play at all. Whenever I try to launch anything involving Play or Google accounts, I get the "...Play Services has stopped." error. I was hoping to maybe start fresh, but I don't even know where to begin. I was thinking I could reflash using the method in the "Update to I337_OC3 - 5.0.1 and KeepRoot" thread, but I have no way to get the FlashFire app on my phone as it can no longer access the Play store. When I try to install it wirelessly from my computer, it thinks that the app is already Installed, even though there's no Google account (or Play access) on my phone. What is my next logical step to try to get things working again?
Thanks in advance for your attention and efforts.
I'm sure there's an apk of flashfire app somewhere on the internet.
Do you have a custom recovery? If so you could try flashing a gapps package and see if it works.
Hello everybody!
There is something strange going on with NFC payments in my Nexus 6p and I've been unable to figure out what.
What I did:
- Rooted my Nexus 6p (in 6.0.0) using the systemless method
- The two NFC bank payment apps that I tried (BBVA Wallet and CaixaBank Pay) decided they wouldn't work because the phone was not secure.
- When 6.0.1 came out, I flashed it and didn't root again.
- The apps still didn't work.
- I uninstalled SuperSU (it was still installed, 'though it didn't work)
- Now, BBVA Wallet works and CaixaBank Pay still complains because the phone is "not secure".
- I was told by CaixaBank Pay support that even if I was un-rooted I'd have to uninstall SuperSU. I told them that I had already done that and that other apps where working, but I got no answer.
So, does anybody have any idea about what to try? I guess if I started anew I'd have no problems, but I don't want to reinstall 200+ apps... and without Titanium Backup.
Thanks in advance.
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.
Hey Folks!
Hope someone can help me out here. I've read a whole bunch of forums and have tried a number of potential solutions to no avail. I have Magisk 15.2 installed and am running Lineage OS 14.2. Multiple apps confirm I pass Safetynet and I can successfully add a card to Android Pay. However, when I try to pay at a terminal, nothing happens. I have tried multiple terminals with no success. Nfc is enabled and android beam works.
Thanks!!!
Try enabling Core Only Mode in Magisk settings, try disabling systemless BusyBox, or try uninstalling your version of Magisk and trying the latest beta. SafetyNet is a nightmare to keep up with. Every time it updates, Magisk gets broken and we have to wait for a new update. Unfortunately, the only real solution is to stop using SafetyNet-dependent apps or keep a locked bootloader/unrooted phone. Or perhaps have one phone for custom ROM stuff and another one for SafetyNet stuff. :/ This is why I'm so vocal about ROMs passing SafetyNet. Hopefully you'll find a fix.
Hey there. Thanks! My phone already passes safety net, though, so I don't think that's the issue... That's what's so bizarre about it! Would you still recommend taking those steps with Magisk Manager?
lastconfederate2 said:
Hey there. Thanks! My phone already passes safety net, though, so I don't think that's the issue... That's what's so bizarre about it! Would you still recommend taking those steps with Magisk Manager?
Click to expand...
Click to collapse
You don't get an error message or anything? Sorry, I missed that. Not sure what the issue is, then. I assume by the other apps, you mean legit apps that actually check for SafetyNet, like downloads in Netflix, a game like Fire Emblem Heroes or a banking app like RBS. If you're able to use those apps or use all of the features perfectly, the issue might just be Android Pay, which probably now detects Magisk(?). Anyway, unless you're actually able to use an app that uses SafetyNet, those SafetyNet checkers don't count for much.
Correct. No error messages, Netflix and others work fine, successfully registered a card in Android Pay, it just doesn't do anything at payment terminals.
lastconfederate2 said:
Correct. No error messages, Netflix and others work fine, successfully registered a card in Android Pay, it just doesn't do anything at payment terminals.
Click to expand...
Click to collapse
I am experiencing the same issue but with Omni 7.1 and Magisk 15.2.
Card was added but giving "Card read error" at payment terminal.
If changing the settings or flashing a beta build doesn't get it to work, then I'm not sure what will. If you're able to, backup your existing ROM and factory reset it. If your Pro3 variant has an official LeEco ROM that passes SafetyNet natively, flash that and lock the bootloader and set up Android Pay to see if it works. Can't offer much else to help you, sorry.
Might be nothing to do with your problem, but i noticed when using nfc to add contacts with other nfc phones etc, that this phone has its nfc chip at the bottom/middle of the phone (it was a while ago, hope I've not remembered incorrectly). Until i realised this i had problems getting it to work.
Edit.. my memory is so bad in now thinking it was the very very top of the phone. Try both.
Thanks for your help, everyone. I discovered today that if I initiate the transaction while my screen is locked, it will actually start the process. I can then unlock the screen and re-tap and it will successfully complete about 75% of the time.
Nothing still happens if i tap the terminal with screen unlocked.
Not perfect, but it works for now!
lastconfederate2 said:
Thanks for your help, everyone. I discovered today that if I initiate the transaction while my screen is locked, it will actually start the process. I can then unlock the screen and re-tap and it will successfully complete about 75% of the time.
Nothing still happens if i tap the terminal with screen unlocked.
Not perfect, but it works for now!
Click to expand...
Click to collapse
Are you still able to get it to work like this? What was the last update you installed? I am trying to do some research to figure out why this happens on many different devices with different roms and such. Most seem to have the ability to get Pay to work and load cards into it, but using at stores and tapping the terminals does nothing(currently my issue).
So what is you setup as of now? Magisk ver, universal safetynet fix(if you're using that) ver, OS ver/date, and what security patch?
If you can provide those things it would be helpful.
Thank you.
Yes, that is still how it works, though I've found over time that it works more like 25% of the time. The last LOS update I have installed is February 10th. I'm using Magisk 15.3, running Android 7.1.2, and last security patch is 1/05/18.
Thanks!
Any luck with this?. Havent tried lock screen pay yet, but unlocked it doesn't work.
LOS 15.1- GTi9506
wkwk said:
Any luck with this?. Havent tried lock screen pay yet, but unlocked it doesn't work.
LOS 15.1- GTi9506
Click to expand...
Click to collapse
Google switched the API last week and rebranded Android Pay as Google pay
https://www.xda-developers.com/google-pay-android-pay-google-wallet/
Have you tried installing Google Pay?
https://play.google.com/store/apps/details?id=com.google.android.apps.walletnfcrel&hl=en
tsongming said:
Google switched the API last week and rebranded Android Pay as Google pay
https://www.xda-developers.com/google-pay-android-pay-google-wallet/
Have you tried installing Google Pay?
https://play.google.com/store/apps/details?id=com.google.android.apps.walletnfcrel&hl=en
Click to expand...
Click to collapse
Yes same issue.
Interestingly, upgrading to official LOS 15.1 this week completely resolved the issue. Google Pay works great unlocked, now.
lastconfederate2 said:
Interestingly, upgrading to official LOS 15.1 this week completely resolved the issue. Google Pay works great unlocked, now.
Click to expand...
Click to collapse
It will probably work in Lineage 14.1 once its been updated for the newer api.
I haven't yet received the OTA Android Pay to Google Pay update. Does the new GP app still work with Magisk root?
Works fine, blocks it automatically just like it did with android pay, you don't even need to hide the app. It just works.
basicreece said:
Works fine, blocks it automatically just like it did with android pay, you don't even need to hide the app. It just works.
Click to expand...
Click to collapse
Perfect timing on your reply. The update showed up in my list this morning and I let it through based on this, and it's just as you said. Thanks.
Its not working for me. GP still thinking my device is root. Magisk V16.0 oneplus One and safetynet both false ....
Doesn't work, I get message: "payment declined" when I want use my Google pay at terminal