As the title says. Is it possible to use Google pay without having to disable xposed framework and reboot every time you want to use it? I switched over from iphone 7 plus and I like how Google pay works as good as apple pay. It would be nice if I could use it without having to disable xposed every time. Any bypass?
Xposed installed via Magisk? Have you tried the built in Magisk hide thing? Select Google Pay.
m. murray said:
As the title says. Is it possible to use Google pay without having to disable xposed framework and reboot every time you want to use it? I switched over from iphone 7 plus and I like how Google pay works as good as apple pay. It would be nice if I could use it without having to disable xposed every time. Any bypass?
Click to expand...
Click to collapse
Don't wanna suggest you to use Xposed right now since it isn't compatible with Samsung firmwares and there aren't Custom builds for Samsung Nougat or Oreo
It seems to work fairly OK with Magisk 16.7. I've tried GravityBox, XprivacyLua and Greenify and they work fine. Ofc, 16.7 ruins your baseband so it's not actually usable, but Xposed seems to be working.
wirespot said:
It seems to work fairly OK with Magisk 16.7. I've tried GravityBox, XprivacyLua and Greenify and they work fine. Ofc, 16.7 ruins your baseband so it's not actually usable, but Xposed seems to be working.
Click to expand...
Click to collapse
You'll probably find somehow a bug related to Xposed lol, it still isn't ready to work at 100% on Samsung ART libs, and AFAIK nobody is working on a custom Xposed build for Samsung fws
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?
If anyone is having issues with flashing xposed I found a thread where there is universal systemless xposed now.
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
I'm going to give it a go even though I've never had issues with xposed, but it seems that with systemless root and systemless xposed you'll keep your OTA capabilities, but a few apps like Android Pay will not work. Make sure to read the whole thread and throw them a thank you for making this.
kingoftheafro said:
If anyone is having issues with flashing xposed I found a thread where there is universal systemless xposed now.
I'm going to give it a go even though I've never had issues with xposed, but it seems that with systemless root and systemless xposed you'll keep your OTA capabilities, but a few apps like Android Pay will not work. Make sure to read the whole thread and throw them a thank you for making this.
Click to expand...
Click to collapse
systemless xposed works fine (and seems to make the system lag less then regular xposed) however 86.7 is out and you need to also make sure you have the "material design xposed installer" installed as it's the only version that detects systemless xposed. The regular one will not do the job.
famewolf said:
systemless xposed works fine (and seems to make the system lag less then regular xposed) however 86.7 is out and you need to also make sure you have the "material design xposed installer" installed as it's the only version that detects systemless xposed. The regular one will not do the job.
Click to expand...
Click to collapse
Wow that was fast. I know about the installer which is why I said read who page lol. It has link and description for installer on the page.
famewolf said:
systemless xposed works fine (and seems to make the system lag less then regular xposed) however 86.7 is out and you need to also make sure you have the "material design xposed installer" installed as it's the only version that detects systemless xposed. The regular one will not do the job.
Click to expand...
Click to collapse
Just looked and there isn't an 86.7. You were looking at release 85.7. 86.1 is the most recent release for systemless xposed.
kingoftheafro said:
Just looked and there isn't an 86.7. You were looking at release 85.7. 86.1 is the most recent release for systemless xposed.
Click to expand...
Click to collapse
You are correct. I'm on 85.7 (initially had 85.1 and upgraded) so the newest IS 86.1
famewolf said:
You are correct. I'm on 85.7 (initially had 85.1 and upgraded) so the newest IS 86.1
Click to expand...
Click to collapse
How is 85.7? I'm going to be flashing 86.1 as a test for @The Marionette on the v2 version of his Material MM Rom
kingoftheafro said:
How is 85.7? I'm going to be flashing 86.1 as a test for @The Marionette on the v2 version of his Material MM Rom
Click to expand...
Click to collapse
Been running fine with all the modules I've used. Nowhere near as jerky a gui as the regular one was..I have NO idea why it would make a difference but that's my impression as well as @The Marionette's impression.
famewolf said:
Been running fine with all the modules I've used. Nowhere near as jerky a gui as the regular one was..I have NO idea why it would make a difference but that's my impression as well as @The Marionette's impression.
Click to expand...
Click to collapse
I'm currently on 85.7 as 86.1 wasn't recognized after installation 2 times by the installer. So far no issues with that, but with MM in general every now and then when I leave the phone for extended periods of time it won't turn back on when the power button is pressed. I've tried everything to keeping the cores full bore and it still happens like it's a deep sleep that it can't wake from and I have to restart the phone.
Xposed framework is not yet ready for Android 7, so i was thinking if there is any alternative to xposed framework. If there is, plz let me know. Thanks in advance.
only thing that can be done now is wait
Wait... and pray they can even make it work. The developers of Xposed Framework have said soon this method will no longer work, in fact, if you remember last year when Marshmallow came out it was several months and the devs almost shut down Xposed and gave up, but got a lucky break. It might move forward for Nougat, or could stop here... either way, it won't last much longer. Better get used to stock Android or custom ROMs.
acejavelin said:
Wait... and pray they can even make it work. The developers of Xposed Framework have said soon this method will no longer work, in fact, if you remember last year when Marshmallow came out it was several months and the devs almost shut down Xposed and gave up, but got a lucky break. It might move forward for Nougat, or could stop here... either way, it won't last much longer. Better get used to stock Android or custom ROMs.
Click to expand...
Click to collapse
Thanks for the information, already using custom rom but there are some apps which asks for xposed framework to work.
manmali said:
Thanks for the information, already using custom rom but there are some apps which asks for xposed framework to work.
Click to expand...
Click to collapse
Ah... I assume you mean Greenify with its ability to hibernate system apps (everything else works in Greenify w/o Xposed except that), but Marshmallow and Nougat really don't need that anyway with Doze mode.
Still, Xposed is a dying thing, security in Android is getting tighter everyday, and that won't stop... And since Xposed is only intended for stock ROMs, as more and more security holes get closed, it makes it harder and harder to keep system-level mods working. Xposed is not intended for custom ROMs.
acejavelin said:
Ah... I assume you mean Greenify with its ability to hibernate system apps (everything else works in Greenify w/o Xposed except that), but Marshmallow and Nougat really don't need that anyway with Doze mode.
Still, Xposed is a dying thing, security in Android is getting tighter everyday, and that won't stop... And since Xposed is only intended for stock ROMs, as more and more security holes get closed, it makes it harder and harder to keep system-level mods working. Xposed is not intended for custom ROMs.
Click to expand...
Click to collapse
I didn't know this all, thanks for sharing. There are lot of apps (xposed modules) in play store ,is there any way to make them work in custom rom??
manmali said:
I didn't know this all, thanks for sharing. There are lot of apps (xposed modules) in play store ,is there any way to make them work in custom rom??
Click to expand...
Click to collapse
I didn't say it won't work, it's not supported... Xposed is not currently compatible with Nougat, it might be later or may not, just have to wait and see. Xposed was only intended for and supported on stock roms.
Xposed works by modifying the operating system framework, basically the structure of the components and how they are displayed... And most devices share a common, stock (or nearly stock) framework from the AOSP code base, Xposed works by modifying this on the fly to do things like replacing the battery icon or allowing you to hibernate system apps... This is all fine and dandy until you try to get it to make changes to a system that uses a modified framework already, like a custom ROM, depending on what it tries to do it may be successful or may cause the device to come to a crashing halt and be unbootable, or just cause weird little quirks that don't make sense, but it has tried to change something that was already changed causing an unpredictable mixture. This is why custom rom developers won't even look at a problem if Xposed is installed.
So the answer is, it might work, might not, but it's an unsupported configuration on ever custom ROM out there and you are on your own with it. Make sure to make backups, cross your fingers and make only absolutely necessary changes.
Replacing an LG G3 with just another LG G3, both 6.0 both rooted. Before I couldn't log into snapchat because Xposed framework was active. That was never a problem, would just uninstall the framework, log into snapchat, and then reinstall the framework. Now I can't get logged in at all, not even without xposed installed whatsoever. Seems to be just the fact the devices is rooted, maybe? Same version of snapchat btw, so I guess its a check on server side. I tried RootCloak both with and without Xposed. Any other things I can try?
EDIT - Yeah after a lot of research figured out about Magisk and safteynet and all that jazz. Just gotta get into learning how to get Magisk working on my VS985 now.
Dunno where else to put this but so far none of the unofficial xposed solutions support the pixel phones because no one seems to want to work with the A/B file layout so if anyone here wants to pick up a project id greatly appreciate that one and i know ive seen a number of others asking for it in different magisk and unofficial xposed threads. Thanks for reading my post and potentially contributing to a fairly noble cause.
Unknown if this is a pixel success. Anyone who knows please do reply.
https://www.xda-developers.com/official-xposed-framework-android-nougat/
alladinscastle said:
Unknown if this is a pixel success. Anyone who knows please do reply.
https://www.xda-developers.com/official-xposed-framework-android-nougat/
Click to expand...
Click to collapse
Doesn't support A/B partition layout yet. No version of xposed except magisk systemless will even flash and even then the magisk systemless xposed also doesn't seem to work right for pixel phones yet
KittyRgnarok said:
Doesn't support A/B partition layout yet. No version of xposed except magisk systemless will even flash and even then the magisk systemless xposed also doesn't seem to work right for pixel phones yet
Click to expand...
Click to collapse
The couple of xposed modules I tried seemed OK (Greenify, youtube adaway...). I just didnt like it because it seemed to break Facebook and Facebook Messenger Apps (caused constant crashes for some reason) and also broke SafetyNet too, which defeats the purpose of even using Magisk. But overall you're most likely correct the modules still need to be updated for Nougat.
Damn...and I was so thrilled when the Nougat version came out.
Guess I stick with rooted Oreo was thinking about reinstall nougat cause of framework but sounds like it's not that great for pixel
cgrimm9 said:
Guess I stick with rooted Oreo was thinking about reinstall nougat cause of framework but sounds like it's not that great for pixel
Click to expand...
Click to collapse
Yeah xposed was my main reason for rolling back but for me none of the modules were being read as properly activated. Its fine though because I have my custom ROM back since there aren't any for Oreo yet.
A thread at pixel xl is saying yes and no with various install methods
UPDATE: added pie controls from xposed to my pixel running RR ; )
Resolved: Systemless Xposed (SDK25) module in magisk now flashes and sticks without fail. Installing the modded Xposed provided in the module description allows the framework/app/modules to interface properly. With both the Systemless framework and the modded app all modules updated as of this month will work
If you haven't already replaced SuperSU with Magisk, do that.
ItWasAllIntended said:
If you haven't already replaced SuperSU with Magisk, do that.
Click to expand...
Click to collapse
Well, choice is good, choice is what it should be, glad I have a choice to use what I want.
SR5-SuperSU-v2.82-SR5-20171001224502
Sent from my Pixel using XDA-Developers Legacy app
piperx said:
Well, choice is good, choice is what it should be, glad I have a choice to use what I want.
SR5-SuperSU-v2.82-SR5-20171001224502
Click to expand...
Click to collapse
I highly recommend switching to magisk at least until we get a proper non magisk Xposed and this is coming from someone who has used SuperSU their whole life
KittyRgnarok said:
Resolved: Systemless Xposed (SDK25) module in magisk now flashes and sticks without fail. Installing the modded Xposed provided in the module description allows the framework/app/modules to interface properly. With both the Systemless framework and the modded app all modules updated as of this month will work
Click to expand...
Click to collapse
Works on Oreo?
xneuromancer said:
Works on Oreo?
Click to expand...
Click to collapse
No nougat only, Xposed is not supported on Android Oreo at all yet