Can't get this working. Errors out at ""Android Pay cannot be used. Google is unable to verify that your device or the software running on it is Android compatible". I'm on Neo Adrenaline 2.4 with newest firmware. Tried with and without Xposed, with/without SU ticked/unticked, with/without RootCloak plus Xposed module running.
Seems to affect many platforms including some all stock.
Any ideas?
schneid said:
Can't get this working. Errors out at ""Android Pay cannot be used. Google is unable to verify that your device or the software running on it is Android compatible". I'm on Neo Adrenaline 2.4 with newest firmware. Tried with and without Xposed, with/without SU ticked/unticked, with/without RootCloak plus Xposed module running.
Seems to affect many platforms including some all stock.
Any ideas?
Click to expand...
Click to collapse
I can confirm it works on stock/rooted RUU when you disable root via supersu app.
I believe for custom roms, it's not doing a root check per se, but a new device compatibilty check. This (new) xposed module should return the check true: http://repo.xposed.info/module/com.pyler.nodevicecheck
Skitals said:
I can confirm it works on stock/rooted RUU when you disable root via supersu app.
I believe for custom roms, it's not doing a root check per se, but a new device compatibilty check. This (new) xposed module should return the check true: http://repo.xposed.info/module/com.pyler.nodevicecheck
Click to expand...
Click to collapse
Thanks for the tip but it didn't work either.
But, maybe I to ditch Adrenaline. What stock/rooted RUU did you flash? Thanks.
schneid said:
Thanks for the tip but it didn't work either.
But, maybe I to ditch Adrenaline. What stock/rooted RUU did you flash? Thanks.
Click to expand...
Click to collapse
Try going to your build.prop file and changing the following
ro.product.version=ADRENALINE 2.4 Port Final
to
ro.product.version=4.17.605.5
I am not sure what build NEO used, but it is a suggestion
make sure you do a uninstall and DELETE of the files mentioned here: http://forum.xda-developers.com/verizon-htc-one-m8/themes-apps/android-pay-fyi-alert-t3205038
IF that works, I will add it to my OP
carm01 said:
Try going to your build.prop file and changing the following
ro.product.version=ADRENALINE 2.4 Port Final
to
ro.product.version=4.17.605.5
I am not sure what build NEO used, but it is a suggestion
make sure you do a uninstall and DELETE of the files mentioned here: http://forum.xda-developers.com/verizon-htc-one-m8/themes-apps/android-pay-fyi-alert-t3205038
IF that works, I will add it to my OP
Click to expand...
Click to collapse
No joy. Tried ro.product.version=4.17.605.5 and ro.product.version=4.17.605.9 as I am on the new Firmware.
What stock/rooted ROM did you use? Might be time to clean house.
Yea, go into superuser and disable superuser. Then install the card. Then after card is installed go back and enable superuser. That's what I had to do.<br/>
schneid said:
No joy. Tried ro.product.version=4.17.605.5 and ro.product.version=4.17.605.9 as I am on the new Firmware.
What stock/rooted ROM did you use? Might be time to clean house.
Click to expand...
Click to collapse
I am using Fluent 6.1, I did change my build.prop to 4.17.605.9, not sure if that is responsible or just the disabling SU. I know I had to delete those files at one point
Flashed Fluent 6.1 and disabled SU. Tried adding a Citi and USAA card, both advertised as approved, but Pay told to me use a card from an authorized bank. Did NOT get the incompatible message. Got an email from Google saying I successfully added a card and a $1.00 transaction appeared on my USAA card. Enabled SU and again got the incompatible message. Since my 'banks" aren't approved anyway, I TWRP'd back to Adrenaline. Android Pay is too hard for me.
schneid said:
Flashed Fluent 6.1 and disabled SU. Tried adding a Citi and USAA card, both advertised as approved, but Pay told to me use a card from an authorized bank. Did NOT get the incompatible message. Got an email from Google saying I successfully added a card and a $1.00 transaction appeared on my USAA card. Enabled SU and again got the incompatible message. Since my 'banks" aren't approved anyway, I TWRP'd back to Adrenaline. Android Pay is too hard for me.
Click to expand...
Click to collapse
I can add my cards successfully, but when I go and attempt to pay with them Android Pay tells me that that my card is not supported in Android Pay of something to that effect.
Are you stating that if I do no have SU enabled then it will work and I will be able to use the cards I have in AP?
To be honest that is a complete nightmare to disable SU every time i want to tap and pay. I just went back to Wallet, it just works flawlessly without jumping through hoops like that. Google made a huge FLOP on this one, not the first and won't be the last either.
carm01 said:
I can add my cards successfully, but when I go and attempt to pay with them Android Pay tells me that that my card is not supported in Android Pay of something to that effect.
Are you stating that if I do no have SU enabled then it will work and I will be able to use the cards I have in AP?
To be honest that is a complete nightmare to disable SU every time i want to tap and pay. I just went back to Wallet, it just works flawlessly without jumping through hoops like that. Google made a huge FLOP on this one, not the first and won't be the last either.
Click to expand...
Click to collapse
The OP is stating that. I've struck-out completely.
Has anyone had any success using Android Pay on a non-stock ROM? I'm on CleanROM. I disabled superuser and was able to add my Amex, but I receive the same "card is not supported" error.
If you are rooted, Google is intentionally blocking Pay. Read here:
http://www.androidpolice.com/2015/09/25/google-security-engineer-visits-xda-forums-to-explain-why-android-pay-doesnt-support-rooted-devices/
Now we know. Hopefully someone will find away to sneak around the blockade.
I can confirm working with clean install of:
[ROM|RADIO|FIRMWARE][5.0.1] Stock-Rooted | Sense 6 | m8vzw | 09-09-15
http://forum.xda-developers.com/verizon-htc-one-m8/development/wip-4-17-605-9-stock-resources-firmware-t3196906
and SU ticked OFF.
Have my USAA MC and Amex and PayPal cards working.
My Citi AAdvantage cards are NOT supported. Citi CS has a long list of other unsupported cards even though Google and them are hyping their cards are supported
schneid said:
I can confirm working with clean install of:
[ROM|RADIO|FIRMWARE][5.0.1] Stock-Rooted | Sense 6 | m8vzw | 09-09-15
http://forum.xda-developers.com/verizon-htc-one-m8/development/wip-4-17-605-9-stock-resources-firmware-t3196906
and SU ticked OFF.
Have my USAA MC and Amex and PayPal cards working.
My Citi AAdvantage cards are NOT supported. Citi CS has a long list of other unsupported cards even though Google and them are hyping their cards are supported
Click to expand...
Click to collapse
I am using the same ROM (the unbloated version) and was ONLY able to get it working by disabling root AND removing Xposed framework.
I have yet to see if it actually works but I do suspect Xposed may screw it up. I'll stick with plastic rather than give up Xposed.
Related
So until/if we are able to get Google Wallet working, we are stuck with Isis. Just installed on my new Droid Max's but getting "This phone has been rooted" error.
Anyone have a workaround to get Isis working on a rooted Maxx/Ultra/Moto X?
***SOLVED / EDIT***
Got this working, please don't thank me as I just compiled other people's work!
1. Root device using PwnMyMoto by JCase:
Post: http://forum.xda-developers.com/showpost.php?p=45598648&postcount=1
APK: http://forum.xda-developers.com/attachment.php?attachmentid=2266105&d=1379514916
2. Install Xposed framework by rovo89
Posting: http://forum.xda-developers.com/showpost.php?p=24267797&postcount=1
APK: http://dl.xposed.info/latest.apk
3. Install Xposed framework in the Xposed app by going to Framework-->Install/Update, then reboot
4. Download the Isis Root Bypass Plugin v1.1 for Xposed framework thank to Joderme
Post: http://forum.xda-developers.com/showthread.php?t=2425346
APK: http://forum.xda-developers.com/attachment.php?attachmentid=2280830&d=1380060162
5. Activate the Xposed Isis Bypass Plugin under "Modules" in the Xposed app.
6. Reboot, install Isis and you should be ready to go!
Thanks to anyone else who helped develop any of the above apps, tricks, and tools.
Disable root in superuser
Sent from my XT1080 using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=2044362
Have you all tried this? my Maxx gets here later this week, but that was what I planned on using.
Can you deny access to root when it prompts, or does it just detect the su binary
redpipe said:
Can you deny access to root when it prompts, or does it just detect the su binary
Click to expand...
Click to collapse
the one I posted? It gives you the option to customize if you're on GB, JB, and also an AOSP function, along with what carrier, then when installing it asks for root, reboots, and then you have the Google Wallet app next to it afterwards.
dbtrumpetguy said:
the one I posted? It gives you the option to customize if you're on GB, JB, and also an AOSP function, along with what carrier, then when installing it asks for root, reboots, and then you have the Google Wallet app next to it afterwards.
Click to expand...
Click to collapse
Does not prompt, just detect somehow. I thought I had solved the problem by going into SU and click "Temp Unroot", then was able to continue with Isis setup and put all my CC's in. Went back into SU, unchecked "Temp Unroot", however my root got messed up and had to re-root. Once re-rooted, Isis went back to giving me the same error message :/
Any other workarounds?
MrZ123 said:
Does not prompt, just detect somehow. I thought I had solved the problem by going into SU and click "Temp Unroot", then was able to continue with Isis setup and put all my CC's in. Went back into SU, unchecked "Temp Unroot", however my root got messed up and had to re-root. Once re-rooted, Isis went back to giving me the same error message :/
Any other workarounds?
Click to expand...
Click to collapse
Also just tried the XPosed workaround that seems to have worked on the S4 and doesn't seem to be working for me.
MrZ123 said:
Does not prompt, just detect somehow. I thought I had solved the problem by going into SU and click "Temp Unroot", then was able to continue with Isis setup and put all my CC's in. Went back into SU, unchecked "Temp Unroot", however my root got messed up and had to re-root. Once re-rooted, Isis went back to giving me the same error message :/
Any other workarounds?
Click to expand...
Click to collapse
What SU do you have? I can't find temp unroot in the included one
Sent from my DROID MAXX via Tapatalk 4.
Casen said:
What SU do you have? I can't find temp unroot in the included one
Sent from my DROID MAXX via Tapatalk 4.
Click to expand...
Click to collapse
3.1.3 from the market and swipe sideways to options
MrZ123 said:
3.1.3 from the market and swipe sideways to options
Click to expand...
Click to collapse
Been using ISIS for a few days now in NYC and love it. Every cab has a sensor for NFC and luckily I have Amex and Chase so can use both of them!
I know people love Google wallet but it seems NFC payments aren't coming on Verizon.
So how do we get ISIS to work and be rooted at the same time!?!?
MrZ123 said:
Been using ISIS for a few days now in NYC and love it. Every cab has a sensor for NFC and luckily I have Amex and Chase so can use both of them!
I know people love Google wallet but it seems NFC payments aren't coming on Verizon.
So how do we get ISIS to work and be rooted at the same time!?!?
Click to expand...
Click to collapse
Got it working, please see OP for details!
Doesn't work for me. Followed instructions to the t. Launch Isis and it asks for root. Hit deny and it force closes after a few seconds. I start it again and it tells me device is rooted.
The new version of the Isis app isn't compatible with this. The dev will need to update the module.
I tinkered around some, and I discovered this solution which is currently working on my MAXX:
Delete ISIS.
Install Xposed.
Install XPrivacy.
Reinstall ISIS, but do not run it yet.
There will be a notification to configure ISIS permissions in XPrivacy.
The only thing you need to restrict is Shell (commands, superuser).
Run ISIS. You should be able to log in successfully.
Or. Wait 2-3 weeks for 4.4 and Google Wallet.
Sent from my DROID MAXX via Tapatalk 4.
This method worked for me, but I had to find the proper xposed module on another thread, Got my old serve account linked up and a google wallet card in the mail too.
http://forum.xda-developers.com/showthread.php?t=2425346
Updated the app/module to v2.0, got it working for me.
Isis does the job, but its awkward loading money onto my amex first. I miss GW.
Hi Vodafone users,
you have already noticed that the new payment app Vodafone Wallet do not work with rooted devices. It asks for su support and has a FC.
Here my easy instruction that let it work with root.
You only need to set in shell blocking su with the xposed module xprivacy (full version).
Kind regards
Peterle
The Peterle said:
Hi Vodafone users,
you have already noticed that the new payment app Vodafone Wallet do not work with rooted devices. It asks for su support and has a FC.
Here my easy instruction that let it work with root.
You only need to set in shell to blocking su with the xposed module xprivacy (full version).
Kind regards
Peterle
Click to expand...
Click to collapse
Thank you!
It works!
I rejoiced prematurely.
Now I get the message:
Wallet can't be set up.
Sorry, something went wrong and Wallet can't be setup. Please try again later.
Call Customer care or close Wallet.
Click to expand...
Click to collapse
massaquah said:
I rejoiced prematurely.
Now I get the message:
Click to expand...
Click to collapse
Try rootcloak?
usvimal said:
Try rootcloak?
Click to expand...
Click to collapse
Yes, didn't work.
Try to reinstall it. I had the same issue yesterday.
Edit:
I turned xprivacy for Vodafone Wallet off. Let it show me the root warning. Then block su via xprivacy and it starts normally. [emoji39]
Please i need help with xprivacy antes Vodafone wallet
The Peterle said:
Try to reinstall it. I had the same issue yesterday.
Edit:
I turned xprivacy for Vodafone Wallet off. Let it show me the root warning. Then block su via xprivacy and it starts normally. [emoji39]
Click to expand...
Click to collapse
Hello, please i need some help with this.
Yesterday i buy the license pro for the xprivacy, and ok, now i have xprivacy pro.
The problem, is dont Work the Vodafone wallet, i test a couple of times and i test all the opcions and nothing...
Please help me, i try your instruccions and always Fc, clase force., if you up a images of proccesing i Will very happy with you.
A lot of thanks for your time
The thing is that it work only for a few minutes. U only need to set blocking su in shell.
When it FC you must give the app all rights and open it with the root warning then block su and open it again.
It is not a stable solution but it works.
Regards Peterle
There's a Cydia variant, too.. Instead of the Xposed Variant you could try this. Heard it works better for a lot of apps.
The Peterle said:
The thing is that it work only for a few minutes. U only need to set blocking su in shell.
When it FC you must give the app all rights and open it with the root warning then block su and open it again.
It is not a stable solution but it works.
Regards Peterle
Click to expand...
Click to collapse
Thanks, but with your instructions,always have a Fc, When charguing Vodafone wallet, I dont know why,
Its imposible for me, thanks allright
The Peterle said:
Try to reinstall it. I had the same issue yesterday.
Edit:
I turned xprivacy for Vodafone Wallet off. Let it show me the root warning. Then block su via xprivacy and it starts normally. [emoji39]
Click to expand...
Click to collapse
When you write you got the same issue, do you mean you got exactly this error message?
Wallet can't be set up.
Sorry, something went wrong and Wallet can't be setup. Please try again later.
Call Customer care or close Wallet.
Yep. But try to open one time without blocking su and after that with blocking su. It's still working then for a few minutes.
Edit. And u have to close it via task manager each time.
Regards Peterle
The Peterle said:
Yep. But try to open one time without blocking su and after that with blocking su. It's still working then for a few minutes.
Edit. And u have to close it via task manager each time.
Regards Peterle
Click to expand...
Click to collapse
1. Unblocked Wallet in XPrivacy
2. Started Wallet. No tour, Error message at once: Wallet can not be setup on a rooted phone. FC
3. Closed via task manager
4. blocked su in XPrivacy
5. started Wallet, tour started, press "Skip Tour", error message "Wallet can't setup......"
(
Stange.
Please give a try to reinstall Wallet again.
Regards
The Peterle said:
Stange.
Please give a try to reinstall Wallet again.
Regards
Click to expand...
Click to collapse
Thank you for trying to help!
But reinstalling the app doesn't change anything.
I'm using an LG G3 rooted, I used rootCloak, added vodafone wallet to the list of apps, and after force stopping the wallet and starting it again it worked flawlessly.
evilgt500 said:
I'm using an LG G3 rooted, I used rootCloak, added vodafone wallet to the list of apps, and after force stopping the wallet and starting it again it worked flawlessly.
Click to expand...
Click to collapse
Did you alo install SElinux Mode Changer and Cydia Substrate as described in the rootcloak instructions?
I want to give it a try and I am not sure if I really have to install all three packages.
massaquah said:
Did you alo install SElinux Mode Changer and Cydia Substrate as described in the rootcloak instructions?
I want to give it a try and I am not sure if I really have to install all three packages.
Click to expand...
Click to collapse
I only downloaded the xposed module from the xposed repo, activated it and rebooted the phone.
I didnt install anything besides that.
evilgt500 said:
I only downloaded the xposed module from the xposed repo, activated it and rebooted the phone.
I didnt install anything besides that.
Click to expand...
Click to collapse
Ok, I managed to successfully hide root from the app and I don't get the message about Wallet not running on rooted phones. (I achieved the same thing with XPrivacy mentioned by the op.)
But I still get the error message
Wallet can't be set up.
Sorry, something went wrong and Wallet can't be setup. Please try again later.
Call Customer care or close Wallet.
Click to expand...
Click to collapse
I am beginning to wonder if there's something wrong with my sim card.....
massaquah said:
Ok, I managed to successfully hide root from the app and I don't get the message about Wallet not running on rooted phones. (I achieved the same thing with XPrivacy mentioned by the op.)
But I still get the error message
I am beginning to wonder if there's something wrong with my sim card.....
Click to expand...
Click to collapse
Did you try calling costumer service? I got that message before using rootcloak, but after that it just worked. I would bet it's the sim that is not working properly.
Hey everyone, I got Android Pay working with the latest version of TruPure (2.6)
This should also work on other stock moto ROM's, as it isn't much different.
I saw this thread (http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659) and made a few changes.
Step 0:
I do not think that this will work with Xposed or Google Dialer/Contacts installed, but I have not tested to confirm. I also uninstalled and reinstalled Android Pay before starting the process, and did not set it up. No need to wipe google play services data as other ways of implementing Pay have done (this causes problems with Android Wear, which I have) This works with the latest version of supersu, 2.67.
Step 1:
Reboot into TWRP recovery, wipe system, cache, and dalvik (art). Data wipe is not needed, at least on my phone.
Step 2:
go to the terminal (in twrp, under the advanced tab) and enter the following two commands.
Code:
echo SYSTEMLESS=true>>/data/.supersu
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
this will make TruPure use systemless root on the next install.
Step 3:
Flash TruPure 2.6, and do not select Google Dialer in the installer. Make sure in the log that SuperSu is installed systemless, if not, you did step 2 wrong.
Step 3v2: if you don't want to install TruPure (honestly why not it's great) flash your room of choice in this step. If the ROM comes with xposed or other tweaks, this will not work.
For a stock ROM, flash here, then flash SuperSU 2.67, then continue.
Step 4: Reboot system, wait for apps to optimize.
Step 5: start up your favorite terminal app, run
Code:
su
accept the prompt
Code:
chmod 751 /su/bin
Step 6: Launch and set up Android Pay, no reboot required
Hope this helps! Your milage may vary!
:good: say thanks if I helped! :good:
Just so you're aware the link you included is broken and depending on which version of SU is installed Step 2 might not be necessary as version 2.62-3 automatically installs systemless.
Well this is big news.. The newest SuperSU is systemless by default? If im reading this correctly, the Google Play update will make this option usable/.
Xposed will definitely break Pay for obvious reasons.
Installing Google Dialer will break Pay too if the required framework JAR and permissions XML are also installed. You can install the dialer without those files, but I doubt CID and lookup will function as it should.
Sent from my XT1575 using Tapatalk
Fixed the broken link, and clarified that this is only tested on the latest supersu.
SR3TLAW said:
Well this is big news.. The newest SuperSU is systemless by default? If im reading this correctly, the Google Play update will make this option usable/.
Click to expand...
Click to collapse
The newest SuperSU isn't systemless by default, step 2 is where we change the string to request the systemless. No need to download a special SuperSU package.
drewksparks said:
The newest SuperSU isn't systemless by default, step 2 is where we change the string to request the systemless. No need to download a special SuperSU package.
Click to expand...
Click to collapse
Spasticdroid said:
Xposed will definitely break Pay for obvious reasons.
Installing Google Dialer will break Pay too if the required framework JAR and permissions XML are also installed. You can install the dialer without those files, but I doubt CID and lookup will function as it should.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Sounds like regardless there is no still no way with Exposed or Google Dialer
SR3TLAW said:
Sounds like regardless there is no still no way with Exposed or Google Dialer
Click to expand...
Click to collapse
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
drewksparks said:
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
Click to expand...
Click to collapse
Whats all the fuss about Google Dialer, does it make dreams come true?
drewksparks said:
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
Click to expand...
Click to collapse
RootCloak has never worked with Android Pay.
Sent from my XT1575 using Tapatalk
Spasticdroid said:
RootCloak has never worked with Android Pay.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
My mistake. I thought I remembered something about it working. So, at the moment, there seems to be no way to make Android Pay work with Xposed or Google Dialer. I personally get by very well without both.
Has anyone tried it with multirom and have the second rom without any root or xposed? I'm gonna give it a go and see how it pans out.
Sent from my XT1575 using Tapatalk
Hi All. Can't seem to get this working. I'm on my 5th attempt at installing. I entered the install commands in TWRP 3.0 exactly as described using TruPure 2.6. Installed OpenGApps Stock. Confirmed I achieved systemless root and changed the permission in the su/bin folder using Root Explorer. I don't have ad-away or any other modification and I installed TruPure as this thread suggests. Each time, SafetyNet check fails. Any other thoughts on what might be causing this?
On a possibly related note, root doesn't seem to survive a reboot after changing the folder permissions...
bsilver2988 said:
Hi All. Can't seem to get this working. I'm on my 5th attempt at installing. I entered the install commands in TWRP 3.0 exactly as described using TruPure 2.6. Installed OpenGApps Stock. Confirmed I achieved systemless root and changed the permission in the su/bin folder using Root Explorer. I don't have ad-away or any other modification and I installed TruPure as this thread suggests. Each time, SafetyNet check fails. Any other thoughts on what might be causing this?
On a possibly related note, root doesn't seem to survive a reboot after changing the folder permissions...
Click to expand...
Click to collapse
Android Pay is going to fail if there's more GApps installed to system other than what was shipped by default on the Pure. You can however, install updated versions of the default shipped apps, or even debloat the ROM of the default shipped apps (which TPMM does), and still have Android Pay working.
Looking at the list of stock Open GApps, Google+, Google Calculator, Google Camera, Google Contacts, Google Fit are a few that never was installed as system apps on stock ROM.
EDIT: Stock apps on the Moto X Pure Edition
/system/app
Android System WebView (WebViewGoogle)
Chrome Browser - Google (Chrome)
Clock (DeskClockGoogle)
Cloud Print (CloudPrint2)
Exchange Services (Exchange3Google)
Gmail (Gmail2)
Google Calendar (CalendarGoogle)
Google Docs (EditorsDocs)
Google Drive (Drive)
Google Keyboard (LatinImeGoogle)
Google Now Launcher (GoogleHome)
Google Photos (Photos)
Google Play Movies & TV (Videos)
Google Play Music (Music2)
Google Sheets (EditorsSheets)
Google Slides (EditorsSlides)
Google Talkback (talkback)
Google Text-to-Speech (GoogleTTS)
Google Translate (Translate)
Hangouts (Hangouts)
Maps (Maps)
YouTube (YouTube)
/system/priv-app
Google Play Services (GmsCore)
Google Play Store (Phonesky)
Google App (Velvet)
Click to expand...
Click to collapse
Spasticdroid said:
Android Pay is going to fail if there's more GApps installed to system other than what was shipped by default on the Pure. You can however, install updated versions of the default shipped apps, or even debloat the ROM of the default shipped apps (which TPMM does), and still have Android Pay working.
Looking at the list of stock Open GApps, Google+, Google Calculator, Google Camera, Google Contacts, Google Fit are a few that never was installed as system apps on stock ROM.
EDIT: Stock apps on the Moto X Pure Edition
Click to expand...
Click to collapse
Thanks for this! It makes perfect sense. Unfortunately I'm still getting a Fail when I run the test. Any other thoughts?
EDIT: Figured it out! I guess OpenGapps itself was incompatible with this setup. Installing TruPure without it solved the problem. Thanks for the help!
Thanks @drewksparks, followed your detailed instructions and confirmed by buying me a beer with my phone running True Pure 2.6.2. Now to decide if it's worth giving up Xposed, Gravity Box, Amplify, etc. Hmmm I want it all.
drewksparks said:
Hey everyone, I got Android Pay working with the latest version of TruPure (2.6)
This should also work on other stock moto ROM's, as it isn't much different.
I saw this thread (http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659) and made a few changes.
Step 0:
I do not think that this will work with Xposed or Google Dialer/Contacts installed, but I have not tested to confirm. I also uninstalled and reinstalled Android Pay before starting the process, and did not set it up. No need to wipe google play services data as other ways of implementing Pay have done (this causes problems with Android Wear, which I have) This works with the latest version of supersu, 2.67.
Step 1:
Reboot into TWRP recovery, wipe system, cache, and dalvik (art). Data wipe is not needed, at least on my phone.
Step 2:
go to the terminal (in twrp, under the advanced tab) and enter the following two commands.
Code:
echo SYSTEMLESS=true>>/data/.supersu
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
this will make TruPure use systemless root on the next install.
Step 3:
Flash TruPure 2.6, and do not select Google Dialer in the installer. Make sure in the log that SuperSu is installed systemless, if not, you did step 2 wrong.
Step 3v2: if you don't want to install TruPure (honestly why not it's great) flash your room of choice in this step. If the ROM comes with xposed or other tweaks, this will not work.
For a stock ROM, flash here, then flash SuperSU 2.67, then continue.
Step 4: Reboot system, wait for apps to optimize.
Step 5: start up your favorite terminal app, run
Code:
su
accept the prompt
Code:
chmod 751 /su/bin
Step 6: Launch and set up Android Pay, no reboot required
Hope this helps! Your milage may vary!
:good: say thanks if I helped! :good:
Click to expand...
Click to collapse
To all the smart puppies outthere, would like to know is it is possible to get this to work on CM13 or AOSP based Custom ROMs. Android Pay is the only thing keeping me runnign TruePureMM. Not that it's a bad ROM but the customization you get from the CM13 ROMs like Bliss is crazy awesome. I'd be a ginnie pig and try it out if someone comes up with something like this for CM13 or AOSP ROMs. Thanks guys.
cerobles1 said:
To all the smart puppies outthere, would like to know is it is possible to get this to work on CM13 or AOSP based Custom ROMs. Android Pay is the only thing keeping me runnign TruePureMM. Not that it's a bad ROM but the customization you get from the CM13 ROMs like Bliss is crazy awesome. I'd be a ginnie pig and try it out if someone comes up with something like this for CM13 or AOSP ROMs. Thanks guys.
Click to expand...
Click to collapse
Won't work unfortunately. Too many files and apps and such are needed in CM and CM-based ROMs (example: Bliss) for them to work properly, and in turn breaks Android Pay.
If we can ever get an AOSP-based ROM, which is bare (meaning not built with AOSP apps included) working on this device, we may have a chance, just like how some ROMs on Nexus devices, such as Chroma and PureNexus, works with Android Pay.
The last thing needed would be a proper GApps package containing only the default GApps found in a stock Pure/Style ROM to install (can be updated versions of those apps too.)
Sent from my XT1575 using Tapatalk
As title says. I installed android pay. I went through the setup which changed an nfc setting from sim card to processor. Then I restarted my phone. About 6 apps are missing. If I go to settings/ application manager/All. I can see them there but they are greyed out with an SD symbol above them.
Annoyingly this includes "suoersu". Android pay doesn't work with root so I was hoping to turn root off temporarily. I can't uninstall supersu, install it from the playstore or from apk. I can't even install other versions like superuser etc.
Any idea as to what's going on greatly appreciated.
It's a galaxy S5 with xtrestolite rom.
lgg2flash said:
As title says. I installed android pay. I went through the setup which changed an nfc setting from sim card to processor. Then I restarted my phone. About 6 apps are missing. If I go to settings/ application manager/All. I can see them there but they are greyed out with an SD symbol above them.
Annoyingly this includes "suoersu". Android pay doesn't work with root so I was hoping to turn root off temporarily. I can't uninstall supersu, install it from the playstore or from apk. I can't even install other versions like superuser etc.
Any idea as to what's going on greatly appreciated.
It's a galaxy S5 with xtrestolite rom.
Click to expand...
Click to collapse
Why don't you simply clean install the rom again? For using android pay you can try using Magisk and SuperSU systemless mode.
Thanks for the reply. I will give magisk a go.
This phone is my work phone and also has lots of photos and video pf my kids. I think it's all backed up but I always lose something when I reflash. Currently apps that were granted root in the past still have it so not a big issue yet. Xposed is missing tho so I won't be able to update modules. If that bugs me enough I may have to reflash rom. It has been smooth for 2 years at least. Probably due for a refresh. Maybe even a new phone.
My daughter got a new phone, after struggling with bootloops and magisk issues. Finally got everything working correctly.
But,
I got root to go fine, only thing is she has had location issues. Google maps, other GPS or location services did not work.
So I uninstalled xprivacylua and seems like services came back, looks like I wasn't hiding anything on it anyways. Or I don't remember what it was.
So instead of reinstalling xprivacylua I decided to look for different answers .
Maybe some other solutions.
Here is a list of apps and modules that are installed. I think some of them overlapped and are kind of messed up. To many that my head is spinning.
Magisk
23.0 (23000)
Magiskhide Props Config.
Riru
Riru LS exposed (Tried switching back and forth to edxposed)
Systemless Hosts
Universal Safetynet fix 1.1.2. (Tried different versions)
LS Esposed one module,
Hiddencore module (enabled Google services Framework and google play services)
Also cleared Data and Cache on google play store.
Rebooted every time
Always safety net failure.
I know its a lot to take in , and do appreciate any feedback or help on this issue.
Is it an 8T? Are you running stock OOS with magisk?
In that case all you need to pass safteynet should be Magisk 23 with magisk hide activated. No need to bother with Magisk hide propconfig, or edexposed or anything.
If you are running a custom rom it is a different matter
I have magisk 23 and magisk hide is active on all google play services, but it still fails.
Its 8t with stock rom.
I think this is why its a little confusing since on my stock 7 pro I have google play services and only android.gms, and android gms unstable hidden and it works fine.
There is not a custom recovery on either of these phones.
Magisk and magisk hide works fine for me, so don't know what to say.
Perhaps try to uninstall Riru and exposed to make sure that they aren't triggering safety net?
You have to get termux. Get su superuser permissions then type props a menu will load press 2 then select yes to change device name then y again to reboot then it should pass safety net
Screens of magisk hide props config
scottlam1 said:
You have to get termux. Get su superuser permissions then type props a menu will load press 2 then select yes to change device name then y again to reboot then it should pass safety net
Click to expand...
Click to collapse
Nope.. Terminal Emulator is actually recommended. With Termux, you are required to use root access for props to work.
with Terminal Emulator, you can just type:
props
and then it'll load. no "su" necessary. That's termux. I've had some issues that these people are talking about with my OnePlus 8T (KB2005, unlocked completely).. I'll try Termux just to rule this out, but this is highly doubtful as to whether or not safetynet passes based on this--it's attempting to modify the same values. Anyway, when I unlocked that bootloader on a stock rom, CTS Profile started showing as false. So I did get the stock on there correctly and it initially passed with a LOCKED bootloader. There's an alpha TWRP that you can actually flash if you want. There's a couple others where you can only boot it.. there's a lot of "only's" here.. and I couldn't get it going with any of the apps mentioned, including ditching EdXposed and deciding to try LSPosed, but that + XPrivacyLau didnt seem to help me. Maybe I'm doing something wrong. From what I can tell I've done everything right and I've got quite a bit of experience attempting/doing this. Sometimes Device SImulation and forced BASIC ATTESTATION can be a lifesaver.
On my OnePlus 6T, I don't have this problem.. then again it's on Android 10. I can't even get a proper root explorer for Android 11. I seriously can't stand what they did to Android 11.. it's so ridiculous how many apps are now incompatible. Root Explorer Pro was possibly the best Root File Manager I've ever used and I've used it since day 1.
Anyway, I'm gonna give all of this a shot in different order.. and this time I'll see if Magisk can do the trick (last time it was on some different firmware and i just now was able to get it going by flashing via Fastboot in Linux). It's the manual way (payload dumper) as opposed to MSMDownloadTool -- which could be used via a VM.. and maybe even better than using Windows tools where you literally have no idea what you're actually doing. I'm just saying. Android is a linux distro, technically.. and we're trying to use just basic root apps for Android 11, and they don't seem to work.. it's insane. They did something with the partitions and it's apparently having issues even mounting R/W even with Magisk giving it root permissions. Btw, Magisk Canary is now outdated, as far as I can tell? Or it's just nowhere to be found when it comes to versions. Either way, I have tried multiple. So I'll try again in a different order.
Sorry for the long post. I've just had it. I've been working on this for a WEEK non stop.. 5-6 days and this is the first sign of progress (reverting via fastboot via Linux, which is the same thing as the MSMDownloadTool ultimately... without the hassle of finding it)
Let me know if there's anything else.. cause I've tried just about everything out there. Remember, for me, so far... unlocked bootloader = CTS Profile failure.. but locked bootloader + stock rom? Passed. I don't know. Before it wasn't passing with a stock rom that came with it so that drove me nuts and made no sense, hence me saying "progress" ... heh. Anyway.. Please let me know if you guys do find anything that works for it. I'm at my wits end. There's basically almost zero support for the 8T but plenty for the 8 and 8 Pro. So that also gets on my nerves. Sorry, once again, for this really long post. Some of it is just venting and I'll update if I get somewhere with it.
.. and now this morning after installing magisk, by just booting twrp (not flashing, but booting) and then using LSPosed/XPrivacyLua (I installed MagiskProps too but I barely did anything aside from pick a fingerprint) --- and it passed? WHAT?
I'm gonna look into this, but I'm not complaining. Let's see if I can find good Android 11 apps for actually browsing the system and being able to r/w any elusive partitions -- wasn't working well with Android 11 before. Not sure if that's around with a simple design anymore. Root Explorer Pro was king of that. Then Android 11 stepped in. I still have to install Lucky Patcher, if it will even work as a module for LSPosed. (Yes, I'm one of those idiots) -- I fully expect it to fail with that but I might be pleasantly surprised. Who knows. So, we'll just call this mixed results. For now -- Passing somehow. I don't understand aside from LSPosed and XPrivLua.. maybe magiskprops. Not sure which one did what first to cause this to go the right direction.
All I can say is all I have is magisk props not the other 2 modules you speak of
Well this is super weird. I didnt see my daughter for 2 days and she said everything is working fine.
I did tons of reboots and other installs/uninstalls and nothing worked.
But now I do safety net check and it works fine.
I dont get it.
If I do have issues again I will post here and follow instructions.
Thank you for your time and help
eracet said:
Well this is super weird. I didnt see my daughter for 2 days and she said everything is working fine.
I did tons of reboots and other installs/uninstalls and nothing worked.
But now I do safety net check and it works fine.
I dont get it.
If I do have issues again I will post here and follow instructions.
Thank you for your time and help
Click to expand...
Click to collapse
Ok asked her what she did. Mentioned updated YouTube vanced. And not sure of anything else.