Related
I am running on stock rooted OF8 and can't seem to run android pay. Setting it up it says that it can't determine if it is compatible. Google wallet did work before. Anyone else run into this?
Apparently it doesn't work on rooted phones. Read some where that you can activate it and then root afterwards but haven't tried it yet.
Sent from my SM-G928T using Tapatalk
works for me non root for now
Were i can find android pay ?
It worked for me non rooted at a vending machine. Though rooted or not at Maverick and Smiths, (3 times total) it has caused my phone to freeze after I verify my pattern lock.
Anyone having that issue?
Haven't been even able to set it up. Rooted on OF8. I'm going to flash the new build tonight and see if I can get it working before I root again and see what happens.
Use an app like RootCloak or HideMyRoot. Once you hide root you can add your cards with no problems. Using it to pay you will need to hide root again.... way too many steps for it to be convenient for me.
shoresteve626 said:
Use an app like RootCloak or HideMyRoot. Once you hide root you can add your cards with no problems. Using it to pay you will need to hide root again.... way too many steps for it to be convenient for me.
Click to expand...
Click to collapse
Where can I get a working version of either of those apps? All the ones I found doing a Google search are outdated and people say they don't work anymore.
I use Hide My Root from the PlayStore. It worked for what i needed but you cant use it for individual apps like RootCloak can. I'm odexed and can't get RootCloak going.
https://play.google.com/store/apps/details?id=com.amphoras.hidemyroot
Worked for me today at mcdonalds i unrooted so i can update to get samsung pay.
I take it your Knox wasn't tripped with your root?
M9x3mos said:
I take it your Knox wasn't tripped with your root?
Click to expand...
Click to collapse
No
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'm currently on Resurrection 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)
Dowload - http://www.mediafire.com/download/1bvbsouwtcz9mx2/Android_Pay_1.0.102576552_930000657.apk
deke997 said:
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'm currently on Resurrection 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)
Dowload - http://www.mediafire.com/download/1bvbsouwtcz9mx2/Android_Pay_1.0.102576552_930000657.apk
Click to expand...
Click to collapse
Disabling SuperSU worked for me. It allowed Android Pay to verify my phone.
Not sure I like that I HAVE to have a Lock Screen setup. And, why can't Android Pay have a lock screen built into it like the new Google Wallet does. Wouldn't we want two part authentication?
Rob
I just installed Danvdh's new 5.1 GPE rom and I'm pretty sure Android Pay was already installed. Haven't tested it yet, though. Looking forward to seeing if Xposed will work alright to keep root enabled while using Pay.
HampTheToker said:
I just installed Danvdh's new 5.1 GPE rom and I'm pretty sure Android Pay was already installed. Haven't tested it yet, though. Looking forward to seeing if Xposed will work alright to keep root enabled while using Pay.
Click to expand...
Click to collapse
I re-enabled SuperSU after the install, and it seems to be working. However, it looks like updating also checks root. So, I had to disable root again to have the update to Android Pay take. But, re-enabled root after the update, and things seem to be working.
Rob
You all that state you have it working on T-MO SGH-M919, must be running the T-MO 4.4.4 software. I had it working too - even on a ROOTED 4.4.4. device. Once I install a CyanogenMod Custom LOLLIPOP ROM - and re-installed the AndroidPay, it no longer works. You get the message that ANDROID CANNOT BE VERIFIED (or some crap like that).
Phone works perfect for everything but that...and of course my GoogleWallet was upgraded and no longer has the TAP TO PAY feature...and you cannot get that one back either.
So I guess I need to find out how to get my phone back to STOCK T-MO 4.4.4, none of the downloads anywhere can actually be downloaded any more (unless anyone has a valid link one of those).
Thanks,
*BH*
I'll give you fair warning, as I participated in the lengthy discussion thread over at the Nexus 5 forum (the thread that had the Google developer participating). Here's the lowdown.
Due to liability pressure from Visa, MasterCard, and the others, Android Pay is very...uptight about its operating environment. It basically won't accept any environment it can't trust, and that basically boils down to a system that is stock and unaltered. Anything that can undermine Android's security model (root, custom ROMS, Xposed Framework, etc.) is red-flagged and the app will break. Now, before anyone begins moaning about how Google Wallet worked before, that will be going away soon under pressure from MasterCard. The new system is tokenized and closer to Chip transactions, which is where everyone will be going over the next few months, and under these new rules, if Google can't show due diligence in trying to maintain a chain of trust throughout the transaction (IOW, try their best to ensure a clean environment with no exploitable features), Google faces the bill for instances of fraud. Any attempt to address this problem simply cannot be done the way Android is setup now. Since anything with root access can do anything to the OS, there's just no way to corral this, not even with Marshmallow. Anyone who has used Samsung Pay will notice they take precautions, too. They're a little more lenient with root because they can protect the chain with Knox. Trip Knox and Samsung Pay balks.
Odds are, this development may make phone manufacturers turn back to things like Secure Elements (or some other system outside Android's scope) to provide a way to ensure a chain of trust even with root present. That's likely why Apple isn't too concerned with Apple Pay working with jailbroken phones (all Apple Pay-ready iPhones carry Secure Elements). Until further development, that's just the way it is with Android Pay.
I need help with getting Android Pay to work on my rooted Note 4 because I keep getting the Android Pay cannot be used message. I do know that Android Pay does does block rooted users so I've tried various workarounds with none of them working.
I tried the method where I installed Root Cloak and added Android Pay, Google Play Service and Google Service Framework to apps it hides root from and cleared the data from those 3 apps. I also installed No Device Check since from what I saw, Android Pay does use SafetyNet to check your devices firmware whether it has been modified or not. Does anybody have any ideas of how to get this to work without losing root access or having to go back to stock?
androidpay
ThatGuy94 said:
I need help with getting Android Pay to work on my rooted Note 4 because I keep getting the Android Pay cannot be used message. I do know that Android Pay does does block rooted users so I've tried various workarounds with none of them working.
I tried the method where I installed Root Cloak and added Android Pay, Google Play Service and Google Service Framework to apps it hides root from and cleared the data from those 3 apps. I also installed No Device Check since from what I saw, Android Pay does use SafetyNet to check your devices firmware whether it has been modified or not. Does anybody have any ideas of how to get this to work without losing root access or having to go back to stock?
Click to expand...
Click to collapse
In the chainfire superuser app disable superuser, then try and add a creditcard, go back to superuser reenable
Iceburn1 said:
In the chainfire superuser app disable superuser, then try and add a creditcard, go back to superuser reenable
Click to expand...
Click to collapse
I'm running CM12.1 if that matters. Would it work even with that or would I have to be running stock?
Im on stock however rooted using beastmode and twrp recovery. I disabled supersu and was able to add my credit cards however when i go to use it for example at a vending machine at school i get a message that says something like, Amex**** is unable to be used at this time and the same goes for my discover.
any ideas how to fix?
http://forum.xda-developers.com/showpost.php?p=62981452&postcount=55
Hi, my Mix2 arrived few days ago and I find MiUI quite nice, yet lacking few things. Those are easily available via xposed, hence I need to root. I'm also not so lucky in these matters so before I start to tinker with it I'd like to learn few things.
What are least dangerous ways to unlock and root phone? (heard sth about magisk, its quite new for me, haven't been rooting phones for couple years now) Is it good?
Suppose I succeed unlocking, rooting and flashing xposed, can I relock bootloader? I want that because ie AndroidPay needs that to work, and I haven't found any working rootcloack or similar (at least on Note2)
How reliable is 'the most official tool' for xiaomi flashing (from eu.xiaomi.com ?)? I mean can it bring back the dead or revert phone back to where I started, without any trace of tinkering?
As a new xiaomi owner are there any critical things I need to know?
Thanks!
If you flash magisk, which is the best thing ever btw, you won't have to relock bootloader to get Android pay working.
yeyeoke said:
If you flash magisk, which is the best thing ever btw, you won't have to relock bootloader to get Android pay working.
Click to expand...
Click to collapse
Thanks, I read about that and intend to use it. Though, there might be some issues with magisk and different versions. What features does it have?
So far, need to wait 3 days to unlock bootloader.
Mighty_Ahti said:
Thanks, I read about that and intend to use it. Though, there might be some issues with magisk and different versions.
So far, need to wait 3 days to unlock bootloader.
Click to expand...
Click to collapse
I've been using magisk on my Note 3 Pro since release and I've never had an issue. Yes, I got my mix 2 today and I'm also waiting for 3 days..
Mighty_Ahti said:
Hi, my Mix2 arrived few days ago and I find MiUI quite nice, yet lacking few things. Those are easily available via xposed, hence I need to root. I'm also not so lucky in these matters so before I start to tinker with it I'd like to learn few things.
What are least dangerous ways to unlock and root phone? (heard sth about magisk, its quite new for me, haven't been rooting phones for couple years now) Is it good?
Suppose I succeed unlocking, rooting and flashing xposed, can I relock bootloader? I want that because ie AndroidPay needs that to work, and I haven't found any working rootcloack or similar (at least on Note2)
How reliable is 'the most official tool' for xiaomi flashing (from eu.xiaomi.com ?)? I mean can it bring back the dead or revert phone back to where I started, without any trace of tinkering?
As a new xiaomi owner are there any critical things I need to know?
Thanks!
Click to expand...
Click to collapse
It's generally considered to be dangerous to relock a bootloader with anything other than perfectly stock/factory firmware installed. It may be ok to do this technically but it sort of "ties your hands" in some ways after making an unofficial modification and makes it a bit harder to recover from a botched situation.
You can have an unlocked bootloader and still use Android Pay. This can be achieved either with a ROM that is built to accomplish this (Epic ROM is an example of this) or by using Magisk, which allows root without any sort of SafetyNet trip in many cases. I don't believe there's *any* way to install Xposed and also use Android Pay or any other SafetyNet apps...the best alternative if you really want Xposed is to use Magisk and then install the Xposed Magisk module...you still can't pass SafetyNet with this setup but Magisk allows you to disable Xposed if you're willing to uncheck it in the Magisk Manager app and reboot the phone, after which time SafetyNet should pass ok...at least with this setup you'll be able to kind of have your cake and eat it too, though it's not ideal as you'll have to reboot if you want to change the status of Xposed.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Thank you for detailed answer. I didn't know that.
flyer_andy said:
the best alternative if you really want Xposed is to use Magisk and then install the Xposed Magisk module...you still can't pass SafetyNet with this setup but Magisk allows you to disable Xposed
Click to expand...
Click to collapse
I tried AndroidPay few times past few days and it didn't work at all. Perhaps terminals were not compatibile. So lets say I gave up on AndroidPay - can I use regular Xposed along with Magisk? Or does it have to be that module?
Mighty_Ahti said:
Thank you for detailed answer. I didn't know that.
I tried AndroidPay few times past few days and it didn't work at all. Perhaps terminals were not compatibile. So lets say I gave up on AndroidPay - can I use regular Xposed along with Magisk? Or does it have to be that module?
Click to expand...
Click to collapse
Oh! I think I may be able to help you with the Android Pay issue - my phone didn't work right with Android Pay until I made sure *all* Google apps' permissions were allowed via the Apps menu in Settings (along with "Autostart" via the security app)...and also toggled the NFC setting where it lets you select between "embedded secure element" and "HCE Wallet." It probably is on "HCE Wallet" but try toggling to "embedded secure element" and then back to "HCE Wallet" a couple of times. My Mix 2 would not make a terminal connection until I did this...it would just say "card read error." Seems like a firmware bug. Let me know if that helps!
But yeah if you don't want to use Android Pay then normal Xposed should be fine...you wouldn't need Magisk I don't think. Though, I'm not sure but I think the Magisk Xposed module probably functions the same as normal Xposed so I'm not sure there's an advantage in doing so. But of course it's all about personal preference!
Whoah, I'm still new to xiaomi/android7+ policies, where each app's permissions are reduced to bare minimum (messenger not being able to show notifications for example). I will definitely try this tomorrow.
So far I just managed to unlock BL, flash recovery and install magisk. SafetyNet checks ok. Will try xposed tomorrow after some payments ;D Thanks!
HCE wallet worked for me (I had it set to SIM wallet).
If I understand correctly here is the possible solution to xposed+magisk+androidPay.
I'd need phh's su binaries for that and keep crossing fingers for it to work on 7.1
I need to learn more about that stuff before I break something
So as I was expecting I experience troubles in installing Xposed.
I followed official way as in here And got bootloop.
I removed magisk stuff in recovery and fixed bootloop, then installed v89.0 (not .1) and also bootloop.
Im using SDK25, and miui 9 - 7.1.1 so it should be ok I think
Mighty_Ahti said:
So as I was expecting I experience troubles in installing Xposed.
I followed official way as in here And got bootloop.
I removed magisk stuff in recovery and fixed bootloop, then installed v89.0 (not .1) and also bootloop.
Im using SDK25, and miui 9 - 7.1.1 so it should be ok I think
Click to expand...
Click to collapse
Disable hooks from the xposed apps settings before flashing xposed
What hooks? I dont have any modules yet
Mighty_Ahti said:
What hooks? I dont have any modules yet
Click to expand...
Click to collapse
It's a toggle in the settings under experimental, disable resource hooks
Boot took longer but it works. Thanks! Do I have to keep it on all the time ?
Mighty_Ahti said:
Boot took longer but it works. Thanks! Do I have to keep it on all the time ?
Click to expand...
Click to collapse
Yeah, phone won't boot with it on. Don't think it makes much difference anyway
Hi @Mighty_Ahti, how much time was "longer"? it's been loading for over 5 minutes already. Thanks
Certainly below 5 minutes.
Probably been asked thousand times before but I want to get a samsung A7050FN specific answer to this query.
What features and functions would stop working once I unlock bootloader and root with the mentioned procedure on A70 thread?
This phone is near perfect for everyday driver except It needs some Titanium backup and viper4android along with few minor UI tweaks.
If some nice smartsian provide a list, I can peace fully proceed with rooting and bootloader unlocking
secure folder will stop working, also you will need to update your device with Odin.
Since Knox will be tripped, you won't be able to use "Knox features" like Secure Folder (there's 3rd party apps that do the same), Samsung Flox, Samsung Pay (if applicable), Samsung Pass, Samsung Health (there's a workaround for this one?). I've also read there could be problems with some apps like banking and Netflix. (Magisk hide root status feature is your friend) . If you're outside the EU tripping Knox will also void warranty.
xomikron said:
Since Knox will be tripped, you won't be able to use "Knox features" like Secure Folder (there's 3rd party apps that do the same), Samsung Flox, Samsung Pay (if applicable), Samsung Pass, Samsung Health (there's a workaround for this one?). I've also read there could be problems with some apps like banking and Netflix. (Magisk hide root status feature is your friend) . If you're outside the EU tripping Knox will also void warranty.
Click to expand...
Click to collapse
Don't care about secure folder or Samsung pay or warranty or loosing ability to update OTA. I can use odin for that
Can samsung pass and health be bypassed via the technique of changing ro.xxxx.tima= 1 to 0 in build prop file?
Don't use Netflix so don't care. Nor use any banking apps
Would fingerprint, face unlock, ar emoji and other camera features and Samsung themes kepp working?
Once you are rooted and your bootloader is unlocked does your boot screen changes to show tripped knox etc?
I rooted my A705MN. Samsung health does not work for me after tima change to 0. I read somewhere that you would have to modify the apk somehow. Never looked into it too much. You can read about it here https://forum.xda-developers.com/s10-plus/how-to/guide-samsung-health-root-device-t3946881
I am bummed that about the secure folder. I used it a lot with my unrooted S8. You can modify the build.prop to pass the SafetyNet check to be able to use banking and Netflix apps again.
Edit: here is another place to read https://forum.xda-developers.com/galaxy-s9/how-to/guide-s-health-knox-0x1-t3843483
fizzingbees said:
Don't care about secure folder or Samsung pay or warranty or loosing ability to update OTA. I can use odin for that
Can samsung pass and health be bypassed via the technique of changing ro.xxxx.tima= 1 to 0 in build prop file?
Don't use Netflix so don't care. Nor use any banking apps
Would fingerprint, face unlock, ar emoji and other camera features and Samsung themes kepp working?
Once you are rooted and your bootloader is unlocked does your boot screen changes to show tripped knox etc?
Click to expand...
Click to collapse
Samsung Pass uses biometrics to log-in and such, it won't work if the device is rooted. I don't know of any bypasses but I've found this https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977
I don't see why emoji and general camera features would stop working, they're not really security features, not that the stock camera is very useful. GCam is a better option for photography.
For now, I haven't rooted my device. From my understanding to enter a rooted state with Magisk you need to turn on your phone with a certain key combination, otherwise I don't think anything is displayed when the phone boots, why is that important?
banking? so like logging on to chase online app may not work if i unlock boot and root? that would be just dumb, i mean my nexus 6 was rooted and custom rom-ed and chase worked
xomikron said:
Samsung Pass uses biometrics to log-in and such, it won't work if the device is rooted. I don't know of any bypasses but I've found this https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977
I don't see why emoji and general camera features would stop working, they're not really security features, not that the stock camera is very useful. GCam is a better option for photography.
For now, I haven't rooted my device. From my understanding to enter a rooted state with Magisk you need to turn on your phone with a certain key combination, otherwise I don't think anything is displayed when the phone boots, why is that important?
Click to expand...
Click to collapse
Our Samsung A70 is very finicky with root and unlocked bootloader. And the rooting method we use is not so very official and stable for us.
So we need to use a certain key combination to keep root and magisk app when rebooting phone.
You mentioned gcam. Which version and config file are you using?
leo5111 said:
banking? so like logging on to chase online app may not work if i unlock boot and root? that would be just dumb, i mean my nexus 6 was rooted and custom rom-ed and chase worked
Click to expand...
Click to collapse
Actually its a security feature.
Many banking and enterprise applications don't work if your bootloader is compromised and your system rooted. They believe that by rooting and gaining administrative status, any hacker can bypass banking app security thereby compromising consumer safety
cealaska said:
I rooted my A705MN. Samsung health does not work for me after tima change to 0. I read somewhere that you would have to modify the apk somehow. Never looked into it too much. You can read about it here https://forum.xda-developers.com/s10-plus/how-to/guide-samsung-health-root-device-t3946881
I am bummed that about the secure folder. I used it a lot with my unrooted S8. You can modify the build.prop to pass the SafetyNet check to be able to use banking and Netflix apps again.
Edit: here is another place to read https://forum.xda-developers.com/galaxy-s9/how-to/guide-s-health-knox-0x1-t3843483
Click to expand...
Click to collapse
It's not like a70 has heart rate sensor and oximeter that I will. Be mad about Samsung health.
Still Samsung makes very stupid decision sometimes.
back to previous statement i NEVER have rooted my phone and then Chase app didnt work, so trying to see before bothering to try and root...EDIT...anyone here with rooted a70 and chase mobile app does it work? that and paypal
fizzingbees said:
It's not like a70 has heart rate sensor and oximeter that I will. Be mad about Samsung health.
Still Samsung makes very stupid decision sometimes.
Click to expand...
Click to collapse
I never really used Samsung Health with my unrooted S8. Fingerprint reader does not work to unlock my rooted A70 on Q (Android 10). It accepts the fingerprint but does not unlock the phone. It goes into a loop where it locks the phone again even I press the fingerprint sensor. I hate the ultrasonic reader lol. Does not work with screen protectors to prevent it from being scratched.
Can't use private mode in Samsung Internet anymore A lot of the features from Samsung seems to be disabled after tripping Knox. I used to love Samsung but with rooting now is a pain in the neck. The build.prop is different than 9 which sucks because I liked "overclocking" kind of making the CPU use all cores, it is not there anymore in Q. I am not sure that the Net improvements hacks for the build prop works anymore. Internet connection does not seem to be as fast for me as 9 was. Edit: I am not sure why the hell we can't use them because it erases the phone when we unlock the bootloader. Even if we re-flash stock they will not work because efuse is already tripped.
back to previous statement i NEVER have rooted my phone and then Chase app didnt work, so trying to see before bothering to try and root...EDIT...anyone here with rooted a70 and chase mobile app does it work? that and paypal
Click to expand...
Click to collapse
I am sorry I do not use those apps. You will have to edit your build.prop to get it to pass the SafetyCheck most likely. If Chase still does not work for you unrooted try contact their support and see if they can help you make it work. I am not liking rooted Q as much as rooted 9 was.
Okay so it means that t rooting and unlocking bootloader leads to Samsung secure folder, Samsung health, Samsung pay, secure login, banking apps and Netflix not working anymore.
Moreover specifically for A70, rebooting phone require specific key combination.
What about boot screen? Does it show any new text after rooting?
My note 4 after rooting shows kernal booting system or kernal booting recovery which is indication thst device has been tempered with.
I have a problem with the making phone calls after rooting. The sounds leak out as if it's on speaker (when it's not) and when on speaker it makes a very shape echo in the back ground.
P.S. havoc os
M.Sam90 said:
I have a problem with the making phone calls after rooting. The sounds leak out as if it's on speaker (when it's not) and when on speaker it makes a very shape echo in the back ground.
P.S. havoc os
Click to expand...
Click to collapse
Turn off voice enhancement in call settings. Or noise reduction in call settings
These settings are known to cause echo or static noise issues during call.
Also try turning off any sound mods you may have done after rooting
Report this issue at hovac os thread. Maybe it's a known issue with that Rom
Headset and sound issues
fizzingbees said:
Turn off voice enhancement in call settings. Or noise reduction in call settings
These settings are known to cause echo or static noise issues during call.
Also try turning off any sound mods you may have done after rooting
Report this issue at hovac os thread. Maybe it's a known issue with that Rom
Click to expand...
Click to collapse
Thanks for the reply but the issues is still the same any other adjustments to recommend ?
fizzingbees said:
Don't care about secure folder or Samsung pay or warranty or loosing ability to update OTA. I can use odin for that
Can samsung pass and health be bypassed via the technique of changing ro.xxxx.tima= 1 to 0 in build prop file?
Don't use Netflix so don't care. Nor use any banking apps
Would fingerprint, face unlock, ar emoji and other camera features and Samsung themes kepp working?
Once you are rooted and your bootloader is unlocked does your boot screen changes to show tripped knox etc?
Click to expand...
Click to collapse
fizzingbees said:
Our Samsung A70 is very finicky with root and unlocked bootloader. And the rooting method we use is not so very official and stable for us.
So we need to use a certain key combination to keep root and magisk app when rebooting phone.
You mentioned gcam. Which version and config file are you using?
Click to expand...
Click to collapse
Sorry for the late reply. I'm using GCam version 7.3.018 by Urnx05 (v1.4) with the config file by dotsx, you can check the file in Telegram by joining the group from this link.
xomikron said:
Sorry for the late reply. I'm using GCam version 7.3.018 by Urnx05 (v1.4) with the config file by dotsx, you can check the file in Telegram by joining the group from this link.
Click to expand...
Click to collapse
Can you kindly post direct link to gcam apk here along with config file as attachment
M.Sam90 said:
Thanks for the reply but the issues is still the same any other adjustments to recommend ?
Click to expand...
Click to collapse
Ask this question in havoc OS thread.
They can help you better than us
xomikron said:
Sorry for the late reply. I'm using GCam version 7.3.018 by Urnx05 (v1.4) with the config file by dotsx, you can check the file in Telegram by joining the group from this link.
Click to expand...
Click to collapse
I found your version but the auxiliary cameras cause the app to crash.
How do you fix this. Any help