It seems Android pay is blocking custom ROMS and root. Hiding the SU binary and pushing a stock build.prop dont seem to alleviate the situation. Does anyone know of a workaround that allows one to keep his root and/or ROM?
I saw this pic on reddit when a user asked google http://imgur.com/FVhQPTz
It uses the SafetyNet API.
Tried setting it up on a stock / signed ROM, went through fine. Tried to backup the app+data and restore it on a custom ROM. Saw my complete account screen for a split second before the 'add new card' window came back and wouldn't go away.
This would not surprise me. Don't be surprised if you can't get around it. Root is too much of a security risk for something like that
I'm not very good with hacks and workarounds but I tried this and it didn't work.
http://androiding.how/android-pay-with-root/#comment-779
Note 2/i317 AT&T/unlocked sim/CyanideL ROM v19/Shift Kernel 5.7
SafetyNet API - fix Android Pay issue with Root / Custom ROMS / xposed
New Last Night...
http://repo.xposed.info/module/com.pyler.nodevicecheck
No luck on a Moto X (2014)...anyone else having any luck?
Nope
No luck on Safteynet API, root cloak, disabling root aps, etc. LG G3 modified stock rom and kernel.
in SuperSU i just disabled SU, NOT unroot, and then it allowed me to add card. im stock rooted s5
Same here
I'm reading that "custom ROMs are missing some proprietary files that Android Pay relies upon"
http://android.wonderhowto.com/how-to/get-android-pay-working-rooted-device-0164604/
It may allow you to add the card, but when you re-enable SU, Pay will not go through when trying to use it.
Downgrade to an 8.x version of Google Wallet. All versions in the 9.x range were preprogrammed to disable themselves when Android Pay came out. I switched back to 8.0-R190-v25 that's preinstalled on my Nexus 5 and disabled automatic updates for Android Pay on the play store.
If you have something like Titanium Backup (which most would if they're rooted), you can also detach Wallet form the Market, meaning it shouldn't know to update it.
Okay, let me start off by saying I thought I could not give up root for Android Pay. I tried workarounds, e.g., temporarily disabling supersu, which let me add cards but wouldn't actually process payment at store.
I have a Nexus 5 on Sprint, with official 6.0 factory imgs installed. I have TWRP recovery and an (obviously) unlocked bootloader. While rooted, I flashed ElementalX kernel (allowing for double-tap to wake, swipe to sleep, and under-volting--3 features I can't live without), modified build.prop to allow multi-window mode, and ran ADB commands to enable tethering (courtesy of Reddit instructions).
I then completely uninstalled SuperSU and BusyBox (no easy task--had to delete system apks and reboot numerous times). I also had to delete su and busybox entries from system/xbin for unrooting. After a reboot, I successfully installed Android Pay, added credit card, and have successfully used it at several retail outlets. More importantly, my kernel DT2W/swipe to sleep/undervolting options still work, as does tethering and multi-window. Apparently AP doesn't check for build.prop or boot mods, nor does it check for bootloader state or stock recovery. I do miss quickboot options I had with root however.
If I absolutely need something that requires root, e.g., Titanium Backup restore, etc, I can just boot into TWRP recovery through old-school holding down power/ volume button technique (hence why I miss quickboot features), flash SU and BusyBox zips I have on internal SD, reboot, do my business, and then unroot like I did above. FWIW unrooting is MUCH more difficult than rooting, but still very doable once you figure out all the steps.
Can you post the steps for cleanup? I have been trying it myself and have had no luck with getting A-Pay to actually work correctly.
Related
My goal is to COMPLETELY get rid of any root files / SuperSu files that are located on my device without having to reformat. Couple months ago i managed to install SuperSu and gained root and I did my own cleanup of bloatware apps and whatnot. Since then I have deleted SuperSu by going into the settings of SuperSu and clicking on the "Clean Root" option but without doing the original boot files option. Doing so, the phone reboots, cleans up , deletes SuperSU and i no longer have root. This is great and all but just one problem reminds.....
I can no longer play Pokemon GO because of the newest update that came out yesterday since it checks for rooted devices. Is there a way to completely remove all the files that are associated with the root process / SuperSU so that I can play this game. I have tried to use the app "SafetyNet Helper" to check for Google's SafetyNet CTS tests and it fails after i tried uninstalling SuperSU. I have heard of the Magisk app but it looks like you need a unlocked bootloader to install it.
Is there a way to get my phone back to the original state without reformatting my phone through Odin. At the end of the day, yes, i would rather have a rooted device than to play Pokemon GO but say what you will but this game has gotten me out, walking around my town, being social and actually making friendships.
Thanks for any help in advance,
Just go here. http://forum.xda-developers.com/tmo...ow-to-unroot-to-stock-o-loosing-data-t3445573
Newest update has blocked access to rooted phones. Even after hiding/ removing root access privileges (I've tried both hiding and un-rooting) I cannot log in, so I'm left only to assume that the version of the OS itself is blocked.
Simple question: Does anyone know of a way around this? I see hundreds of posts about magisk, but I cannot do that while using slimkat ( magisk requires android 5.0+)
I've really gotten into this game over the last coiuple months, but I refuse to revert to some vanilla stock version of android to play. If anyone could provide any info I'd greatly appreciate it.
I'd do what I always do when I need/want to run something of that nature: I install a "sacrificial ROM" alongside my Slim using MultiRom and boot into it when needed.
So...an app demands a non-rooted ROM? No problem: Here's a plain vanilla AOS sandbox for you to play in.
I'm playing to PoGo with any issues with SlimRom 6, I just deleted a file called su.bin from /system/bin and /system/xbin.
This erases root of the rom, and make it playable. Use SafetyNetHelper on Google Play Store to check if you pass the test (PoGo uses this test).
You can delete them (you have to delete both) on the file manager of TWRP.
The way i got mine to work(i can also use the Fake GPS hack with my POgo as well! ) is 1st i downloaded an already rooted(with SuperSU) rom for my phone off of xda and i installed the fake gps app through ucky patcher to make it a system app. i then downloaded a stock rom for my phone from here at xda, and i flashed it using Odin, this replaced everything to make it stock again but kept my system files(the fake gps app) so then all i had to do was redownload PoGo and login as normal and voila! their security check diverted and still able to fake gps it lol
Ive found a few for CM/Lineage versions, and COS12 but not one for COS 13 Official.
Does anyone happen to have a twrp flashable one? Or perhaps a list of safely removed items for the purposes of below usage.
And could all messaging and telephone/SIM services/apps & cyanogen phone home stuff, be removed as well? Making mine into a PokemonGo tablet for my kid. Doesn't need anything except for Play Services GPS/Wifi functionality, & ability to install from play store. I know it can all be removed through root however, everytime I root, and eventually full unroot, I get the incompatible OS screen that Niandicks setup to deter cheating... Have not found a way around it and do not want to deal with magisk, pph SU, suhide and so on, thus TiBU is not an option. Would like to just flash stock COS13 f/w, flash a debloat script and setup for my kid. That's all.
So the thing was the secure folder app and the samsung pay app and health app is saying I have root even though i never installed root, and even checked if i have root via root checkers saying that i have no root... how do i fix this???
Did you install a different ROM?
DarkerJava said:
Did you install a different ROM?
Click to expand...
Click to collapse
i haven't installed any rom but I did retrieved the old bootloader [ I changed to s8 boot loader but came back to the original boot loader (backup) ]
It appears that any modifications you've made in the past have left behind "pieces" or corpse folders/files. I have a 930F and in order to use banking apps, payment apps, etc. I had to use Magisk (hides from newer apps quite well). NO superuser or su framework can be present (apps see it right away and su doesn't hide well on new devices / apps). So I believe that there is a remnant or file related to root triggering the warning msg you are seeing. My advice would be to flash fresh firmware (also a full wipe).
*Sometimes changes made related to root (even if you don't have root) can trigger apps/system warnings even though you didn't root.
JOHN.WAYNE said:
It appears that any modifications you've made in the past have left behind "pieces" or corpse folders/files. I have a 930F and in order to use banking apps, payment apps, etc. I had to use Magisk (hides from newer apps quite well). NO superuser or su framework can be present (apps see it right away and su doesn't hide well on new devices / apps). So I believe that there is a remnant or file related to root triggering the warning msg you are seeing. My advice would be to flash fresh firmware (also a full wipe).
*Sometimes changes made related to root (even if you don't have root) can trigger apps/system warnings even though you didn't root.
Click to expand...
Click to collapse
Would this affect major os update? and how do I remove remnant/corpse files
I don't have any problems or require any help, just sharing some stuff
I got sick of playing cat-and-mouse with Google regards Google pay, and I've tried them all:
Downgrade play services
SQL Fix
Magisk modules
Deny telephony permissions etc etc....
I decided to test something and ended up with:
A TWRP backup of my fully magisk-rooted, formerly daily driver in all its rooted glory (I use stuff like drivedroid often which requires root)
And also:
A stock install of G930FOXA6ESGD_BTU, debloated with the aroma debloater and my own list of non-required stuff removed via ADB > shell <package manager>
I've also ADB'd the "skip tracks with volume buttons" app and greenify commands to use them without root in this Stock ROM.
Banking and GPay confirmed working.
So I am now using this as my daily driver, and boot into my rooted rom when I need to use drivedroid or other root-based goodies.
Enable OEM Unlock is enabled in both Rooted and Stock, and I swap between them as required via TWRP.
Sure, root is nice to have, I get that, but do you need it? if you can set up the Stock install to be as close to rooted as you can get by with, would you use this as a "solution" to constantly battling Gpay?
Thoughts, comments or suggestions welcome
Does it pass mastercard validations?
I don't have any Mastercards so I can't test that for you, sorry. If you test it, would you please report back just so people have the information? Thanks