Hey Guys,
I have an original (2013) Moto X 1060 (Verizon) that I rooted using this method. http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602 It's been working great with no problems until today when my phone decided to update my google wallet app to the new android pay. Whenever I try to add a card to android pay I'm getting the error "Android Pay Cannot be used...... Google is unable to verify that your device or the software running on it is android compatible."
Googling has led me t believe that this is an error related to the app detecting root. I tried both of these methods, but neither has worked. http://bit.ly/1LnwzAZ http://bit.ly/1LnwEog . I've tried each separately with rebooting in between as well as trying them together all to no avail.
Other than following the guide above the only root-related things I have modified on the phone are the removal of some verizon apps via titanium backup and adding the following xposed module: "NoSafeVolumeWarning".
One thing that I noted was when I uncheck "Enable Superuser" inside of SuperSu 2.46 it displays a message saying "Uninstall Failed !" It still displays the "Superuser is disabled and hidden" underneath the box and if i enable it again and disable it it does not pop up with the uninstall failed message. Does this have something to do with write protection?
Any help would be greatly appreciated!
Thanks,
Adam
johnnyboy239 said:
Hey Guys,
I have an original (2013) Moto X 1060 (Verizon) that I rooted using this method. http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602 It's been working great with no problems until today when my phone decided to update my google wallet app to the new android pay. Whenever I try to add a card to android pay I'm getting the error "Android Pay Cannot be used...... Google is unable to verify that your device or the software running on it is android compatible."
Click to expand...
Click to collapse
Having the exact same issue. Just upgraded to 5.1 today, xposed Rootcloak as well as No Device Check installed. Also tried Disable SU. Still get the same issue.
Same. I tried uninstalling SU, Hide My Root, and Rootcloak...nothing has worked. Found out today that the app updated when I went to buy something at Walgreen's. How ****ing embarrassing is that?
So I have not yet found a solution to this and am still hoping someone has one. In the mean time, you can install this app http://www.apk4fun.com/share/7185/ (doesn't need to be from this site, it's just an old version of google wallet, and the one I used), go into settings>apps>google play services>manage data clear all data, and reboot. I just tried it at cub foods and it worked fine, but of course you do have to go into the app first, and I had to disconnect it from the app store with titanium backup so it wouldn't update to android pay again.
Was able to get Amex card working after uninstalling Xposed. However, I think I'm going to pass on Android Pay until they allow pin codes on the app, not the phone.
Same problem, few apps frozen with TiBu and xposed installed. Any other work around? s
johnnyboy239 said:
So I have not yet found a solution to this and am still hoping someone has one. In the mean time, you can install this app http://www.apk4fun.com/share/7185/ (doesn't need to be from this site, it's just an old version of google wallet, and the one I used), go into settings>apps>google play services>manage data clear all data, and reboot. I just tried it at cub foods and it worked fine, but of course you do have to go into the app first, and I had to disconnect it from the app store with titanium backup so it wouldn't update to android pay again.
Click to expand...
Click to collapse
check to see if your phone allows pin codes to be deactivated at times. I have mine set to not be used at home work and if I am carrying the phone. It is quite useful feature in settings Lockscreen but I am on COS 12.1 OnePlus basically CM
I haven't tried it yet, but I think they only way we'll get this working on root is to install it on stock unrooted, back it up with TiB or Helium, root and then reinstall/restore.
Lots of fail here as well. All the tricks you all listed + some others. It seems there is a lack of consistency for those that resolved. Some just say disabling root, uninstall busybox, uninstall xposed, rootcloak, device checker for play services, etc.
Nothing yet has worked for me. Luckily I backed up Wallet just before taking the update, so I may go back until the community has a solution.
Ezekial said:
Lots of fail here as well. All the tricks you all listed + some others. It seems there is a lack of consistency for those that resolved. Some just say disabling root, uninstall busybox, uninstall xposed, rootcloak, device checker for play services, etc.
Nothing yet has worked for me. Luckily I backed up Wallet just before taking the update, so I may go back until the community has a solution.
Click to expand...
Click to collapse
I'm in the same boat. Couldn't get AP to work. Just loaded up the previous version of Wallet. Now have two wallet apps, but whatever. Both appear to be working.
Has anyone tried to get Android Pay working by re-locking the bootloader and temp unrooting on a Nexus device (say, a tablet), then getting AP up and running, and then checking to see if it was usable on your other device(s)??....I was curious if Android Pay would work on ALL of your devices once it was set up properly. Working with lock, unlocking, rooting, etc. is much easier on a Nexus than it would be to work on a Moto, or similar.
Does this make any sense?
KenNashua said:
Was able to get Amex card working after uninstalling Xposed. However, I think I'm going to pass on Android Pay until they allow pin codes on the app, not the phone.
Click to expand...
Click to collapse
Tried AP for the first time at Panera today and failed...seems even with Root Cloak on AP and Google Play Service as well as No Device Check, it still fails.
Related
Hey everyone
I got the update from att and I lost root (rooted on mj5 before). I didn't actually want to update but I checked for updates and it did it automatically. My fault I know. Anyway, I had freedom installed and now I can't connect to any Google services. I removed my Google account and now I can't re add it.
I tried removing freedom the exact way it says to and it didn't work.
Any suggestions on what to do? I tried to re root with Kingo but it tells me "no support", which is strange to me because others have successfully used kingo with this update. Even if I'm not rooted, I just want google services working again.
If I was rooted again, I have read a few ways to try to fix the error.
I did try clearing app data for Google services and play store.
Thanks all
I'm on M3 rooted with Despair kernel.
Got Android pay update and tried to activate it by adding a credit card information. It bailed out saying that my phone can't be trusted, I figured out that's because of root.
I tried to unroot in SuperSu. First by disabling Enable Superuser root button, second by Full unroot. Both methods didn't work, Android pay still couldn't be activated.
I then tried to format and flash boot, system, recovery MPA44I images. I started to get a RED message your phone can't be trusted on boot. Android pay still couldn't be activated. NOTE: I didn't erase data partition.
I don't want to do a full factory reset.
What are my options now ?
jodvova said:
I'm on M3 rooted with Despair kernel.
Got Android pay update and tried to activate it by adding a credit card information. It bailed out saying that my phone can't be trusted, I figured out that's because of root.
I tried to unroot in SuperSu. First by disabling Enable Superuser root button, second by Full unroot. Both methods didn't work, Android pay still couldn't be activated.
I then tried to format and flash boot, system, recovery MPA44I images. I started to get a RED message your phone can't be trusted on boot. Android pay still couldn't be activated. NOTE: I didn't erase data partition.
I don't want to do a full factory reset.
What are my options now ?
Click to expand...
Click to collapse
http://www.androidpolice.com/2015/0...per-preview-but-it-will-in-the-final-release/
Sent from my Nexus 6 using Tapatalk
Thanks!
jodvova said:
Got Android pay update and tried to activate it by adding a credit card information. It bailed out saying that my phone can't be trusted . . .
What are my options now ?
Click to expand...
Click to collapse
Paying with money.
(Just joking, forgive me. I just got a message of the bank that we have to pay for nfc paying)
jodvova said:
I'm on M3 rooted with Despair kernel.
Got Android pay update and tried to activate it by adding a credit card information. It bailed out saying that my phone can't be trusted, I figured out that's because of root.
I tried to unroot in SuperSu. First by disabling Enable Superuser root button, second by Full unroot. Both methods didn't work, Android pay still couldn't be activated.
I then tried to format and flash boot, system, recovery MPA44I images. I started to get a RED message your phone can't be trusted on boot. Android pay still couldn't be activated. NOTE: I didn't erase data partition.
I don't want to do a full factory reset.
What are my options now ?
Click to expand...
Click to collapse
This might be worth a look.
http://www.xda-developers.com/xda-external-link/no-device-check-xposed-module/
adfurgerson said:
This might be worth a look.
http://www.xda-developers.com/xda-external-link/no-device-check-xposed-module/
Click to expand...
Click to collapse
Thanks for the link. I just tried it with N6Shamu and it doesn't seem to work for me.
CharFalco said:
Thanks for the link. I just tried it with N6Shamu and it doesn't seem to work for me.
Click to expand...
Click to collapse
Same here. Nexus 6, latest chroma build, rooted, bootloader unlocked, using xposed RootCloak and the No Device Check modules. No dice.
Is there any way to revert back to the old Google Wallet?
CyberZion said:
Is there any way to revert back to the old Google Wallet?
Click to expand...
Click to collapse
Go to the Android Pay app info, and uninstall updates. This will roll it back into Google Wallet. You should also go and uninstall the new wallet app if you have it so as to avoid confusion.
After that, I had to find an APK site that could update my wallet app back up to Version 9.0. I've since disabled auto-updates to the Google Wallet app until I see some signs of support for root.
I'm unlocked, rooted, and running Xposed w/ Android Pay setup and have had no issues...
ethan.r.besbris said:
I'm unlocked, rooted, and running Xposed w/ Android Pay setup and have had no issues...
Click to expand...
Click to collapse
Have you actually been able to make a purchase? I got everything setup and activated but received an error message when I tried to use it. I then disabled root and rebooted to try the payment again. Did not get the error message this time but the transaction did not complete.
I made a payment this morning using Pay without a problem.
ethan.r.besbris said:
I made a payment this morning using Pay without a problem.
Click to expand...
Click to collapse
Weird since Google has already announced on the complaints in GPS that currently Development Builds and Rooted Devices are not supported. Is Xposed Masking root for you?
GMoGoody said:
Weird since Google has already announced on the complaints in GPS that currently Development Builds and Rooted Devices are not supported. Is Xposed Masking root for you?
Click to expand...
Click to collapse
i installed it fine yesterday(into /data/data/), and added a card no problem. i have root, an unlocked bootloader, am running m(jdx rom), and have a custom kernel. using google play services 8.1.14.
simms22 said:
i installed it fine yesterday(into /data/data/), and added a card no problem. i have root, an unlocked bootloader, am running m(jdx rom), and have a custom kernel. using google play services 8.1.14.
Click to expand...
Click to collapse
Have you tried to make a purchase? @ethan.r.besbris was the only one I know of that has successfully purchased something with root. I too have everything installed but the vending machine and whole foods today gave me errors when actually trying a transaction. I am trying to figure out what the difference is. As of now I do not have Xposed installed.
GMoGoody said:
Have you tried to make a purchase? @ethan.r.besbris was the only one I know of that has successfully purchased something with root. I too have everything installed but the vending machine and whole foods today gave me errors when actually trying a transaction. I am trying to figure out what the difference is. As of now I do not have Xposed installed.
Click to expand...
Click to collapse
no, that was my mistake. after i installed it to see if all was alright, i uninstalled it, and got rid if my nfc. all my friends have gotten weird messages after install, so i assumed i was fine. i dont need it, or want it, i was just trying to help out my friends.
simms22 said:
no, that was my mistake. after i installed it to see if all was alright, i uninstalled it, and got rid if my nfc. all my friends have gotten weird messages after install, so i assumed i was fine. i dont need it, or want it, i was just trying to help out my friends.
Click to expand...
Click to collapse
No worries. Thanks for the input. Seems to be a lot of different results out in the wild right now. Not the best launch
Sent from my Nexus 6 using Tapatalk
ethan.r.besbris said:
I'm unlocked, rooted, and running Xposed w/ Android Pay setup and have had no issues...
Click to expand...
Click to collapse
What ROM?
Stock.
ethan.r.besbris said:
Stock.
Click to expand...
Click to collapse
Interesting, you're stock 5.1.1 rom like me but you're rooted w/ xposed. The only person rooted where it works is Simms22 and he's on JDX M rom which AP is said not to work. @simms22 what did you do special?
I'm rooted 5.1.1 and wanted to try and activate Android Pay since my bank is supported. Found some workarounds people were posting online, but they seem to not work for certain devices/roms. Just wondering if anyone here has had success.
Nope, I've tried everything short of flashing from ftf. I'm also curious if anyone's had luck.
Sent from my iPad using Tapatalk
Tried rootcloak for hiding root to Android pay?
Disable SuperSU in settings, setup android pay, re-enable SuperSU - worked for me.
Android Pay + Root?
cschmitt said:
Disable SuperSU in settings, setup android pay, re-enable SuperSU - worked for me.
Click to expand...
Click to collapse
Just tried this and couldn't get it to work.... can you give some more detail since I might be doing something wrong. Thanks! I unchecked the setting for (enable Superuser) is that correct?
Bayouland1 said:
Just tried this and couldn't get it to work.... can you give some more detail since I might be doing something wrong. Thanks! I unchecked the setting for (enable Superuser) is that correct?
Click to expand...
Click to collapse
Yes, that's exactly what I did. Are you receiving 'unable to add card' or 'could not verify system' (something like that.)
Guys i had this issue and then i flashed a PRF zip and set up android pay and it worked fine. Then i enabled xposed and all i think it came with supersu but i didnt use any root apps before setting up Android pay. But now i tried to use it and it said my card was not supported... maby my bank??It worked fine on Google Wallet. So i deleted card and was gonna re add it but now cant get past the error message again. I have rootcloak and disable device check xposed modules still no worky. Please let me know if you find a fix.
Sent from my D5803 using Tapatalk
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
same thing happened to me just now.
not sure what to do, not sure if i have to reinstall everything again
fmkilo said:
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
Click to expand...
Click to collapse
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
JokersWild0075 said:
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
Click to expand...
Click to collapse
Listen up folks. Do not and i repeat do not update any of samsungs apks. Until we can find out whats going on. It seems that samsung is now pushing updates thru their apks to check and get rid of SU. They are getting sneaky. So for now do not update any samsungs apk, not even thru google. Also do not update SU, this is another way to lose root. We are working on it. Please do not ask if we found anything, if a fix is found we will post our findings.
If you need shealth, iris scanner, samsung pay, android pay, or any other samsung apk, then you need to stay on stock firmware and not use root.
Also if anyone is having issue with files or odin not flashing, make sure you are not on the new PI4 stock ROM, if you are then odin will fail everytime and at this moment there is no way to root or down grade to the older firmware.
Otherwise Try to redownload all files as it seem that afh is/was having alot of issues with uploads and downloads. This not something that we can fix as we dont host or own that site.
Can you guys break down the steps to regain root without reinstalling the OS? Mine also lost root on v2.
It looks like my S-Health was automatically updated to the latest version, which has been reported to be a root of the cause.
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
elite-fusion said:
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
Click to expand...
Click to collapse
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
galaxyuser88 said:
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
Click to expand...
Click to collapse
I am currently logged into the Samsung account and have been for about 2 days now with no ill affects so far, downloaded a couple themes is all...that is with all the Sammy stuff froze and functional root.
I just bought a Pixel 3a from swappa.com. One of the things that I've noticed is that when I run any Niantic games, it tells me my device or OS is incompatible with this version. I suspect this may be because the bootloader is unlocked? However, the phone is NOT rooted.
Any ideas on what my options would be? Had a chat with Google and they're supposed to be emailing me once their experts find a solution, but not crossing my fingers on that. I already tried locking the bootloader with fastboot and had a freakout (was able to unlock it again and factory reset, LOL . . . )
summerblink said:
I just bought a Pixel 3a from swappa.com. One of the things that I've noticed is that when I run any Niantic games, it tells me my device or OS is incompatible with this version. I suspect this may be because the bootloader is unlocked? However, the phone is NOT rooted.
Any ideas on what my options would be? Had a chat with Google and they're supposed to be emailing me once their experts find a solution, but not crossing my fingers on that. I already tried locking the bootloader with fastboot and had a freakout (was able to unlock it again and factory reset, LOL . . . )
Click to expand...
Click to collapse
I'm unlocked, rooted (stock ROM and kernel), and spoofing gps and I'm still able to play Pokemon Go.
I'd recommend flashing the latest stock factory image to clear out anything the old user may have left behind.
If that doesn't work I'd root using Magisk, then hide Magisk and applicable apps.
gargleblarg said:
I'm unlocked, rooted (stock ROM and kernel), and spoofing gps and I'm still able to play Pokemon Go.
I'd recommend flashing the latest stock factory image to clear out anything the old user may have left behind.
If that doesn't work I'd root using Magisk, then hide Magisk and applicable apps.
Click to expand...
Click to collapse
Ok, cool, I'll try that! Thanks for the reply!
Wiped and rooted phone, installed stock rom from Google, and it worked! Pokémon Go AND Wizards United working. Thanks so much!
Im on Stock Rooted and Ex Kernel all you have to do is go to magisk use Mgaisk Hide the games and go into settings then HIDE Magisk or i think its repackage hide something aroudn that and yeah it works oh also you have to turn off debugging in dev options.
summerblink said:
Wiped and rooted phone, installed stock rom from Google, and it worked! Pokémon Go AND Wizards United working. Thanks so much!
Click to expand...
Click to collapse
If you decide to use the GPS spoof, I highly recommend fakegps route, it gives you a thumb stick so you can walk around while being a couch potato. It's 4 bucks.
Just use the Magisk module "systemize" to make it a priv-app, restart your phone, uninstall the app from the app store, enable expert mode in the GPS app, then disable fused locations the GPS app.
gargleblarg said:
If you decide to use the GPS spoof, I highly recommend fakegps route, it gives you a thumb stick so you can walk around while being a couch potato. It's 4 bucks.
Just use the Magisk module "systemize" to make it a priv-app, restart your phone, uninstall the app from the app store, enable expert mode in the GPS app, then disable fused locations the GPS app.
Click to expand...
Click to collapse
i have not been able to use any systemized priv-apps to work, they all crash the instant they open on 10, are you still on 9?
Xepherxv said:
i have not been able to use any systemized priv-apps to work, they all crash the instant they open on 10, are you still on 9?
Click to expand...
Click to collapse
I'm still on 9