So I downloaded the new Android Pay app last night, but it doesn't seem to work if you have a custom ROM installed. I have a T-Mobile phone and I'm currently on Resurrection Lollipop (CM 12.1 based) and it gives me the error "Google is unable to verify that your device or the software running on it is Android compatible".
This needs to change.
UPDATE - I found a workaround that *may* help out. Go into SuperSU and disable root (or disable however you want), try adding your cards again, and then go re-enable root. This has worked for many people on other phones with this error, but it didn't help on my T-Mobile S4
Let me know if you get it to work on another ROM (or even if it works at all on stock right now) or if you have a workaround for this.
Dowload - http://www.mediafire.com/download/1b..._930000657.apk
is not working on official at&t rom 5.0.2 FC android System
Edgardo Regazzoni said:
is not working on official at&t rom 5.0.2 FC android System
Click to expand...
Click to collapse
Does it give the same error?
Related
I'm running Cataclysm ROM (the Sept. 10 beta), Franco kernel, and I'm rooted and use Xposed. I receive this error when I try to add a card in Android Pay: "Android Pay cannot be used: Google is unable to verify that your device of the software running on it is Android compatible". I tried disabling root entirely and using RootCloak (Xposed) to hide root from Android Pay and Google Wallet, but I still can't use Pay. Wallet still works as it always has.
I've seen scattered reports of this here and there but no concrete solutions. Has anyone figured out a workaround?
I get this same message on a LG G2, fully stock, rooted, running 5.0.2.
After some searching, I found this, and it did work for me: https://www.reddit.com/r/Android/comments/3k0ge4/android_pay_workaround_without_xposedrootcloak/
Short version: In SuperSU, disable root, goto Android Pay and activate cards. After cards are activated, enable root. Cards still worked.
I'm not sure if you will need to remove the xposed framework (uninstall from inside the xposed installer) and then disable root. I do not use xposed, so I can't confirm this.
This worked perfectly, thanks!
I also recommend using Lockscreen Disabler with Xposed to get rid of the lockscreen requirement.
Do you have to be on the stock kernel? I'm on the latest 5.1.x build of stock lollipop and have Xposed Framework & Franco Kernel installed. I tried full un-root in SuperSu and rebooting, but I still can get Android Pay to complete the card setup. Do I have to re-flash the stock kernel? I figured this was going to be a PITA. lol I understand Googles need for security on the devices with Android Pay, but the check they are doing have to be so hard-core.
Were you able to successfully make a payment with Android Pay? I can add my cards to the app, but Android Pay isn't working for me at McDonald's or Walgreens.
Will Android Pay work on KitKat or only 5.x.x? I have 2 Nexus 5s, one with 4.4.4 and another with 5.1. On the one with 5.1, I have tried the rootcloak method to put both New Google Wallet and Android Pay to the list, force stopped Android Pay, ran it to the end, and it still gives me the error saying that it cannot be used and is unable to verify the device or software running on it is Android compatible. I also had already updated to GPS v8.1.14 and was under the impression that it wasn't functioning properly, so I rolled back to a previous version of 8.1.13, still returns the same error.
Did you even read all of what OP had to say:
"I tried disabling root entirely and using RootCloak (Xposed) to hide root from Android Pay and Google Wallet, but I still can't use Pay. "
So your comment helps not at all since OP said they disabled Root and STILL have this issue. I have the exact same issue at OP so your comment is not the answer to this question. Any one ELSE have any idea how to resolve when you have already disabled root as OP said.
---------- Post added at 09:19 AM ---------- Previous post was at 09:17 AM ----------
Any one who actually READ what OP said have an answer? How to resolve this situation when you have already DISABLED ROOT in SU.
Possible Fix to Android Pay Root + Xposed Issue...
Just found this. Posted last night. Won't be able to test it for a few hours when I get off this plane...
Since it has bothered me for a few days now, I'm going to post this in a few related threads to help others getting the AP rollout. I just found this which looks promising ( http://www.droidforums.net/threads/new-xposed-module-hides-root.284455/ ) Obviously, this requires xposed and is a little bit off topic here, but this approach was not working for me anyway (stock rom and kernel but rooted and with xposed. Also xposed rootcloak did not work either)
I'm on a plane currently, so I cannot test this, but if anyone else can confirm it works / does not work, that would be great. I had gotten to the point that I was able to set up my AMEX card after a clean stock 5.1.1. install and make a purchase before rooting and adding xposed back in the mix. However, now that I am rooted again, I had a purchase denied earlier today. Hopefully this is the solution.
I have not tried it, but heard it did not always work: https://plus.google.com/u/0/114618417341022236593/posts/dUW1QxDjiFH
this didn't work for me, G3 CM12.1
None of this has worked for me.
Yeah I tried root cloak, disabling super user, and all that but none of it work on my G3 running CM 12.1 either
Disabling root in SuperSU did not work for me.
Also seems no one has had this problem, but on a dark layer theme "invertion ui" the text of the card and exp and ccv are white on white, and none of the above has worked for me either.
Nexus 5
Chroma
Xposed
Hells Core b20
same issue with stock nexus 5 that at some point in the past was rooted... after several updates, i never bothered to re-root. SuperSU still there, but doesn't start - no root. But still Android Pay wont work with this error. ugh.
My workaround was to revert to Wallet.
After failing to get Android Pay to work on my rooted Nexus5 with all the suggestions above, I remembered that Google Wallet worked for me last week before updating to Android Pay. I went to Titanium Backup and restored it, and Voila Wallet with all my data! Next, I unchecked the Auto-Update setting in Google Play for the Android Pay app. Then I remembered a Titanium BU Feature that allows you to break the market link of the app. I have not tried a transaction yet, but it sure looks like the old Wallet app will work just fine.
My wife runs a stock non-rooted HTC Mini2 and is perturbed that her loyalty cards are locked out by Android Pay. I think the solution here is to install a version of Wallet that I found on APK mirror/. I'll need to enable "untrusted" apps in settings after gaining developer rights, but it should work without much effort beyond that. I'll try it when she gets home.
I'm rooted with Xposed. I uninstalled Xposed and SU but I still get the error message. Is there any way round this please?
(this belongs elsewhere but 10 posts...)
I have a rooted S4 and just installed Dandvh's Google Play Edition v.20150919 (http://forum.xda-developers.com/showthread.php?t=2539361) rom. I used TWRP to install, wiping everything but internal storage, then flashed the rom. Installed fine, no errors. Took the usual bit of extra time to boot the first time then up and running clean and stable. The issue is that the OTA Updater app doesn't work, severely limiting my ROM options. It didn't install as part of the rom install, though I'm not sure if it's normal to just get it off the play store. I get an error message about not being compatible with the ROM and can't access it (error message screen cap below). Just in case, I wiped the phone and flashed again just to be sure, same result. The OTA Updater is important as this is where you can change kernals, audioFX stuff, toggle advanced power menus, and quite a bit more. When I used this ROM during the first part of the year OTA Updater worked just fine but I switched off in July to try another ROM so maybe something with the ROM has changed? I tried searching for any comments in the thread to indicate either that something changed with OTA Updater or if anyone else had a similar problem, found nothing. Would appreciate if anyone might know why OTA Updater isn't working or how I might correct it. Thanks.
Edit #1: I haven't changed the model number to SGH-M919 (as seen in the screen cap) in build.prop yet as if I can't get this ROM to work right I'll need to flash something else.
Edit #2: I noted in the patch notes that the ROM was updated for OTA Updater 2.4.2 and I was running 2.5.3 so I uninstalled it and installed 2.4.2. No luck there either.
Version and Build Screenshot
https://imgur.com/SQ6ie5i
Error message
https://imgur.com/TfWN7p2
As in the title states I have the galaxy tab 2 7.0 and recently I installed CWM and a ROM and everything looked like it went right however after I reloaded my tablet nothing seems different it jus seems to return to stock setting and now I cant do the OTA software update which means now certain apps and games I can no longer uses as it says my device isnt compatible. My goal was to simple update from Jellybean to at Least Kitkat.
Can someone help me. where did I go wrong?
Fleacore210 said:
As in the title states I have the galaxy tab 2 7.0 and recently I installed CWM and a ROM and everything looked like it went right however after I reloaded my tablet nothing seems different it jus seems to return to stock setting and now I cant do the OTA software update which means now certain apps and games I can no longer uses as it says my device isnt compatible. My goal was to simple update from Jellybean to at Least Kitkat.
Can someone help me. where did I go wrong?
Click to expand...
Click to collapse
Go to sammobile and flash the latest stock firmware for your device .
Newyork! said:
Go to sammobile and flash the latest stock firmware for your device .
Click to expand...
Click to collapse
Well after a short research I found a ROM called Resurrection Remix, loaded with 5.0.2 (or Lollipop) however now everything is force closing and I barely got my laptop to see it as MTP again after installing a new Binary (glad that did that trick for that) but I cant get it to boot into CWM Recovery bc I cant access the app the only thing it will let me do right now is change the Binary.
How can I fix this issue?
Edit: Okay so I got that solved with doing a factory reset twice, booted in CWM, loaded up the GApps. Now just wondering if there is away to make it not seen with phone options like the dialer or msgs as its jus a plan old tablet, doesnt take a sim card and has no carrier. I do have the source code but I am not tweaking that til I get a better understanding of it.
After a lot of research and tries (amazingly without bricking) I am now running an even newer version of a CM 13 Marshmellow
Hello all! OK, I have a Samsung Galaxy Note 10.1 (GT-N8013) that I'm still using and love, still running stock everything (Android 4.1.2, Build JZO54K.N8013UEUCMA3). Ideally, I'd like to upgrade to 4.4.2 and root it.
I checked the "Software Update" link on the device (in Settings), and sure enough, it says that I have I have an update downloaded...I'm thinking that it's an update to 4.4.2 that was pushed out to this device some time ago, but I'm not sure...I'm worried that it's some sort of "Samsung-software-only" update or something similarly useless that I may like less than what I have. So I have several questions:
1) Has anyone else experienced this before who can say what this update most likely is? If it's not 4.4.2, what is it?
2) I want to root this device, but from the different forums I've been reading, it appears that it's easier to root 4.1.2; rooting 4.4.2 seems to have met with mixed success, and that makes me nervous. But if I root, I won't be able to do the software update (and I don't want to deal with the custom 4.4.2 roms out there unless I have to, as the process seems very involved).
Does anyone have some insight or advice? Am I wrong about the difficulty involved in rooting stock 4.4.2? Thanks in advance for all your input!
4.1.2 is the last release for N8013 .
Custom Roms have 4.4.2 .
Question is why do you want to root ?
JJEgan said:
4.1.2 is the last release for N8013 .
Custom Roms have 4.4.2 .
Question is why do you want to root ?
Click to expand...
Click to collapse
Hello JJegan...thanks for responding to me!
I successfully rooted my phone (a Samsung Galaxy S4) some time ago, and I love it...rooting gives me more finely-grained control over my device, particularly since a lot of apps ask for (in my opinion) rather intrusive permissions (e.g., why should a word-processing app want to know my location?). I have an app on my phone that monitors permissions requested and gives me the option to allow or deny access; I feel better having that and I just wanted to add that to my tablet.
If you're saying that 4.1.2 is the last release (that's what my tablet came with), then what is this software update the tablet is referring to? Also: I have noticed a few custom ROMs available for the 8013, but a lot of them are quite involved and require some unsettling jerry-rigging (e.g., after installation you must disable the phone portion of the ROM because it is added in by default, then you must install a Wi-Fi fix afterward that some users have reported does not always work, etc.)...so I'm worried about that option. But even if I find a custom 4.4.2 ROM that works great, would I be able to root after installing it?
Thanks!
But even if I find a custom 4.4.2 ROM that works great, would I be able to root after installing it?
YES via SuperSu
JJEgan said:
But even if I find a custom 4.4.2 ROM that works great, would I be able to root after installing it?
YES via SuperSu
Click to expand...
Click to collapse
I have SuperSU on my rooted phone: correct me if I'm wrong, but SuperSU only allows you to manage superuser access for your apps, right? I don't think that app itself can give you root. I'm thinking I'll have to use the second of two methods mentioned in this post, but there have been conflicting reports of whether this works on an N8013 running 4.4.2.
Oh, and for anyone else who might be researching this thread with similar questions in the future: I managed to reach someone in Samsung customer support (wow!): If you have the stock Android 4.1.2 on your Galaxy Note 10.1 GT-N8013, the software update that the machine may say is available to you is an update to 4.2.2 and that is "the most recent update" (read: last one) provided for this model. You'll have to find a custom ROM to get it to 4.4.2...very disappointed in that!
Long time since i actually rooted . As i understand the supersu zip flashed through TWRP recovery will root your phone .
https://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
4.1.2 is the last listed release from Samsung .for N8013 .
N8010 is up to 4.4.2 as stock rom .
I have been running Cryogenmod 12.1 for my Samsung SM-A300FU but its UNOFFICIAL and a preview the webpage i got it off says 'Wifi and Camera NOT WORKING'. I guess thats what i get for following my mates advice.
Because of this, i looked at CM13 (Android 6) which i got off the XDA site and i have made sure it is for my phone and model, the SM-A300FU. Of course, being my luck it didnt work. I get the error of 'Executing updater binary in zip' and i have wiped my phone then tried to install it and i have also tried to completly remove all OS and files then install it which apparently fixed it for people, but not me of course. In a desperate measure i even bluetoothed the ROM to another phone then back into my SM-A300FU to get it onto the internal storage but that obviously didnt change anything.
Finally, i gave up and tried to downgrade back to Android 5.0.2 although this isnt a CM zip. Once again, this ROM doesnt work. It just gives me an error saying it failed, no reason in particular.
I have a few issues for a whole range of files. Any help in fixing any or all of these would be much appreciated.
Links to the files I sites i downloaded the files from:
CM 12.1 UNOFFICIAL (Not meant to work fully) - https://forum.xda-developers.com/samsung-a-series/orig-development/rom-cyanogenmod-12-1-samsung-galaxy-a3-t3273323
CM 13 (Doesnt install) - https://forum.xda-developers.com/samsung-a-series/orig-development/rom-cyanogenmod-13-0-unofficial-samsung-t3326297
Android 5.0.2 ROM (Doesnt install) - http://www.youmobile.org/blogs/entry/-Firmware-Download-Samsung-Galaxy-A3-SM-A300FU-Official-Android-5-0-2-Lollipop-update-Rolling-out
So to reitterate: I installed the CM 12.1 ROM without issues but it turns out to be a mod that doesnt work fully meaning its unsuitable for me. I downloaded CM 13 but this gets an error. I downloaded a Android 5.0.2 ROM which has an error it doesnt even tell me about.
XDA Visitor said:
I have been running Cryogenmod 12.1 for my Samsung SM-A300FU but its UNOFFICIAL and a preview the webpage i got it off says 'Wifi and Camera NOT WORKING'. I guess thats what i get for following my mates advice.
Because of this, i looked at CM13 (Android 6) which i got off the XDA site and i have made sure it is for my phone and model, the SM-A300FU. Of course, being my luck it didnt work. I get the error of 'Executing updater binary in zip' and i have wiped my phone then tried to install it and i have also tried to completly remove all OS and files then install it which apparently fixed it for people, but not me of course. In a desperate measure i even bluetoothed the ROM to another phone then back into my SM-A300FU to get it onto the internal storage but that obviously didnt change anything.
Finally, i gave up and tried to downgrade back to Android 5.0.2 although this isnt a CM zip. Once again, this ROM doesnt work. It just gives me an error saying it failed, no reason in particular.
I have a few issues for a whole range of files. Any help in fixing any or all of these would be much appreciated.
Links to the files I sites i downloaded the files from:
CM 12.1 UNOFFICIAL (Not meant to work fully) - https://forum.xda-developers.com/sa...m-cyanogenmod-12-1-samsung-galaxy-a3-t3273323
CM 13 (Doesnt install) - https://forum.xda-developers.com/sa...-cyanogenmod-13-0-unofficial-samsung-t3326297
Android 5.0.2 ROM (Doesnt install) - http://www.youmobile.org/blogs/entr...ial-Android-5-0-2-Lollipop-update-Rolling-out
So to reitterate: I installed the CM 12.1 ROM without issues but it turns out to be a mod that doesnt work fully meaning its unsuitable for me. I downloaded CM 13 but this gets an error. I downloaded a Android 5.0.2 ROM which has an error it doesnt even tell me about.
Click to expand...
Click to collapse
Greetings and welcome to assist. Which recovery are you using ? Have you tried to update to the latest ? Also if that doesn't work try using odin to go back to latest stock then reflashing custom recovery
Why not make an account and let the experts here
https://forum.xda-developers.com/samsung-a-series
guide you
Good Luck
Sawdoctor