Install play services 8.1 and Android Pay.
http://www.apkmirror.com/apk/google...-8-1-15-2250156-270-x86-android-apk-download/
https://www.apkmirror.com/apk/google-inc/android-pay/android-pay-1-0-102576552-android-apk-download/
I cannot get the Android Pay to work, even with doing a full unroot. I still get an 'not supported' error. See here https://m.reddit.com/r/nexus6/comments/3khcez/android_pay_does_not_currently_work_with_an/
Works fine on my phone, I am running stock rooted and with an unlocked bootloader.
Edit: I take that back, the app runs fine but when I add a card it tells me it cannot verify the software my phone is running is android compatible or something like that.
Good to know, looks like Android Pay doesn't like custom roms.
SPIK3 said:
Works fine on my phone, I am running stock rooted and with an unlocked bootloader.
Edit: I take that back, the app runs fine but when I add a card it tells me it cannot verify the software my phone is running is android compatible or something like that.
Click to expand...
Click to collapse
Thats not good, can anyone with a locked bootloader AND root try Android Pay to see I'd it works?
Thanks.
Android Pay is not supported on rooted phones
Mister_Simon said:
Android Pay is not supported on rooted phones
Click to expand...
Click to collapse
Doing a full unroot does not work as well. So its not just a root issue.
You are all 551 users, right? Obviously it isn't going to work on the 550 as that has no NFC.
it gives me play services force close every time when I try to add a new card... and I update the gps to 8.1.15 and latest pay from the playstore its the same..
ipaq114 said:
it gives me play services force close every time when I try to add a new card... and I update the gps to 8.1.15 and latest pay from the playstore its the same..
Click to expand...
Click to collapse
Wrong services updated
Rooted w stock Rom and locked boot loader
yumms said:
Thats not good, can anyone with a locked bootloader AND root try Android Pay to see I'd it works?
Thanks.
Click to expand...
Click to collapse
I'm running stock Rom, rooted, locked boot loader and I also get the can't verify error when I try to add a card
Solved-Kinda
petejfjohnson said:
I'm running stock Rom, rooted, locked boot loader and I also get the can't verify error when I try to add a card
Click to expand...
Click to collapse
Hey I was just able to add my cards by unrooting. Once you've added your card(s), you can re-root and android pay keeps working. It seems the error only exists when trying to add cards. I'm running stock rom, rooted, and with a locked bootloader.
FYI, I was able to get Android Pay to work. I did a clean install of the SuperZen rom. Disabled root via SuperSU app, added my cards and re-enabled root.
I was running rooted stock .59 with unlocked bootloader and custom recovery. When the last update came out I unrooted via supersu, flashed stock recovery and took the OTA. Out of Laziness I never rerooted or flashed custom recovery. Was able to add credit card fine a couple days ago.
Well, when rooted the cards said can't be used and when fully unrooted the transaction is successful.
Related
I've heard that using towelroot will root your phone but not unlock your bootloader. What does this entail? Can I still use Xposed Installer/ other root apps? Can I recieve OTA updates? Can I unroot again? Are there any downsides?
Looking forward to hearing about any experiences with this app.
Fakusnamus said:
I've heard that using towelroot will root your phone but not unlock your bootloader. What does this entail? Can I still use Xposed Installer/ other root apps? Can I recieve OTA updates? Can I unroot again? Are there any downsides?
Looking forward to hearing about any experiences with this app.
Click to expand...
Click to collapse
I just got my N7 and I unlocked the bootloader. I then used towelroot to root it and it worked fine. I have not flashed a custom recovery so I don't think OTA should be an issue.
But...
utsmaster18 said:
I just got my N7 and I unlocked the bootloader. I then used towelroot to root it and it worked fine. I have not flashed a custom recovery so I don't think OTA should be an issue.
Click to expand...
Click to collapse
It's just that some of my other devices (samsung ones, admittedly) don't get OTA updates since I've rooted them, even though they're available. I've also heard that rooting most devices sort of cuts off the updates, and that towelroot prevents that by leaving the bootloader alone.
Fakusnamus said:
It's just that some of my other devices (samsung ones, admittedly) don't get OTA updates since I've rooted them, even though they're available. I've also heard that rooting most devices sort of cuts off the updates, and that towelroot prevents that by leaving the bootloader alone.
Click to expand...
Click to collapse
After rooting you don't need to worry about updates with a nexus device (or any other really). As you'll notice in the N7 Android Development section, there are a TON of lollipop builds and it hasn't been officially released yet. In other words, all updates will be baked into custom ROM's so there's no need to worry about official updates. And to root a nexus, simply unlock the bootloader and flash a custom recovery like TWRP, there's no need for tools
DroidIt! said:
After rooting you don't need to worry about updates with a nexus device (or any other really). As you'll notice in the N7 Android Development section, there are a TON of lollipop builds and it hasn't been officially released yet. In other words, all updates will be baked into custom ROM's so there's no need to worry about official updates. And to root a nexus, simply unlock the bootloader and flash a custom recovery like TWRP, there's no need for tools
Click to expand...
Click to collapse
Ugh...Yeah I was aware of that. If you read my question again, that was not what I was asking for. My queries were about the towelroot application in particular and if I could recieve OTA updates if I left the bootloader alone. I did not ask for alternatives.
I don't understand why you would rely on an app for root with a locked bootloader on a Nexus device. It's so simple to unlock the bootloader and root. There's only, at a minimum, thousands of guides on how to do it. If you're worried about updates, unlock the bootloader.
nhizzat said:
I don't understand why you would rely on an app for root with a locked bootloader on a Nexus device. It's so simple to unlock the bootloader and root. There's only, at a minimum, thousands of guides on how to do it. If you're worried about updates, unlock the bootloader.
Click to expand...
Click to collapse
Because I've heard unlocking the bootloader stops OTA updates. I don't want to have to download roms as my download speed is abysmal. Google services have (on average) 8 times the normal download speed at my place (no idea why), so I'd much rather recieve OTA updates from Google than download a rom.
Just another thought and I get your question, but if you did unlock the boot loader and then just downloaded the factory image from here https://developers.google.com/android/nexus/images you WOULD be downloading it from Google so you should get the same speeds. Now I know you asked about towelroot and I've not used it, but if you're worried about download speeds the images in that link are directly from Google. I know what you mean though, I have very good download speeds and no matter what I download it does seem like the one's direct from Google are about 25% faster. They've got good networking that's for sure.
Fakusnamus said:
Because I've heard unlocking the bootloader stops OTA updates. I don't want to have to download roms as my download speed is abysmal. Google services have (on average) 8 times the normal download speed at my place (no idea why), so I'd much rather recieve OTA updates from Google than download a rom.
Click to expand...
Click to collapse
Heard that an unlocked bootloader prevents OTAs? I don't know where you heard that, but that's completely wrong. Bootloader state has absolutely no affect on OTAs. What an unlocked bootloader does is give you the ability to have complete control over your device. Flash any rom, flash any recovery, and never have to worry about losing root.
Take some time to read and learn before you start tinkering.
nhizzat said:
Heard that an unlocked bootloader prevents OTAs? I don't know where you heard that, but that's completely wrong. Bootloader state has absolutely no affect on OTAs. What an unlocked bootloader does is give you the ability to have complete control over your device. Flash any rom, flash any recovery, and never have to worry about losing root.
Take some time to read and learn before you start tinkering.
Click to expand...
Click to collapse
When I've rooted my phones in the past, I've stopped recieving OTA updates, even though they put out new ones. My friend who unlocked the bootloader on (and rooted) his nexus 7 also stopped recieving OTA updates. Are you saying that I can unlock bootloader and root my nexus 7 and I'll still receive OTA updates and/or can update to Lollipop when they release it a few weeks later for the device?
Fakusnamus said:
When I've rooted my phones in the past, I've stopped recieving OTA updates, even though they put out new ones. My friend who unlocked the bootloader on (and rooted) his nexus 7 also stopped recieving OTA updates. Are you saying that I can unlock bootloader and root my nexus 7 and I'll still receive OTA updates and/or can update to Lollipop when they release it a few weeks later for the device?
Click to expand...
Click to collapse
USUALLY it's a custom recovery that prevents OTAs not an unlocked bootloader or rooted device.
For example, I have a nVidia Shield which I prefer to get the OTAs for as the stock OS is perfect for my needs. Whenever an OTA is available, I have to reflash the stock recovery, apply the OTA and then I can flash a custom recovery again. I could have chosen to not use a custom recovery but I prefer to - so I just flash the stock one (1.0-3.0Mb size maybe?) and then back to custom after the OTA. takes 2min extra work before and after the OTA.
esmith13 said:
USUALLY it's a custom recovery that prevents OTAs not an unlocked bootloader or rooted device.
For example, I have a nVidia Shield which I prefer to get the OTAs for as the stock OS is perfect for my needs. Whenever an OTA is available, I have to reflash the stock recovery, apply the OTA and then I can flash a custom recovery again. I could have chosen to not use a custom recovery but I prefer to - so I just flash the stock one (1.0-3.0Mb size maybe?) abd then back to custom after the OTA. takes 2min extra work before and after OTA.
Click to expand...
Click to collapse
I can tell you for sure that neither me, nor my friend have flashed custom recovery. Still no updates.
Fakusnamus said:
I can tell you for sure that neither me, nor my friend have flashed custom recovery. Still no updates.
Click to expand...
Click to collapse
What android version and kernel date do you currently show in "About Tablet" at the bottom of the settings screen?
The best way is to use towelroot now, and backup your data with titanium backup, then you can unlock your bootloader if you want for lollipop.
esmith13 said:
What android version and kernel date do you currently show in "About Tablet" at the bottom of the settings screen?
Click to expand...
Click to collapse
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Fakusnamus said:
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Click to expand...
Click to collapse
Question still stands... What Android version and what Kernel date?
Okay...
Okay, this is going on a massive tangent. My question was : If I root the nexus 7 with towelroot, can I still update to lollipop when the update rolls out? What can or can't I do with towelroot? (except not flash custom recovery or roms)
Fakusnamus said:
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Click to expand...
Click to collapse
I don't have it on me right now, but its a brand new one, and I've done nothing to it, so whatever kernel that is. I'm guessing the android version is 4.3 .
esmith13 said:
Question still stands... What Android version and what Kernel date?
Click to expand...
Click to collapse
I don't have it on me right now, but its a brand new one, and I've done nothing to it, so whatever kernel that is. I'm guessing the android version is 4.3 .
Just unlock the bootloader now. It'll save you so much time and headache in the future.
I have a rooted Samsung Tab S wifi with this firmware installed T800XXU1ANFB. In order to unroot do i need to flash it with the same stock firmware it has on it. Or can i flash it with an updated stock firmware?
Metamorph22 said:
I have a rooted Samsung Tab S wifi with this firmware installed T800XXU1ANFB. In order to unroot do i need to flash it with the same stock firmware it has on it. Or can i flash it with an updated stock firmware?
Click to expand...
Click to collapse
Just select full unroot from settings in the supersu app.
I am a newbie... so here goes.
I did root it but when I go to verify it it doesn't verify. SuperSU was put on my device, but it wants to update the binary and I did that, but it keeps failing.
What I want to do is unroot it entirely and set it back to factory settings so I went to the settings in SuperSU like said above. If it is unrooted, how would I know? SuperSU is still on my table And only able to.bto.be disabled instead of e tirely removed.
I also think it didn't work because maybe I was trying to root it with a auto file for kitkat instead of lollipop. And links to the version for this lollipop are in a few places but each time I try to extract what I've downloaded the file is corrupt and it never unzips.
I've got the galaxy tab s 10.5; 16gb; wifi only (sm-t800) running lollipop 5.0.2
I'd really like to root so I can get the bloatware off, but if it isn't possible at the moment then I'd might as well go back to an unrooted device.
I'll take all the help I can get or be directed to. I've been pulling my hair out for two days on how to figure it out.
After you have unrooted reboot and you will be unrooted. Root can be verified with Root validator.
For root you can use my build here:
http://forum.xda-developers.com/showthread.php?t=3079488
ashyx said:
After you have unrooted reboot and you will be unrooted. Root can be verified with Root validator.
For root you can use my build here:
http://forum.xda-developers.com/showthread.php?t=3079488
Click to expand...
Click to collapse
On a second reboot I noticed I wasn't rooted. Thanks. I finally am rooted now.
ashyx said:
After you have unrooted reboot and you will be unrooted. Root can be verified with Root validator.
For root you can use my build here:
http://forum.xda-developers.com/showthread.php?t=3079488
Click to expand...
Click to collapse
I'm having a different problem but I am sure it is related to this topic.
I ended up being properly rooted after I got the correct one for lollpop 5.0.2. Then I realized that The Sims Freeplay would not work. I tried to use root cloak and I had no luck. I thend tried to use xposed, but it hasn't been upgraded to Lollipop yet.... so I thought about if rooting my device was really worth it since the only game I religiously play is The Sims Freeplay (apparently they are cracking down on people who hack their game.... which is all good and well because because it has nothing to do with my game... I have a rooted device to get rid of bloatware, not to hack the game that I play in a legit way -- but whatever)...
So I chose to unroot from SuperSU like I did once before (when I wasn't properly rooted, but SU was still on my device) just to see what would happen.
I've used Odin two more times to put back the original root file I got to work for Lollipop and now on the second reboot, SuperSU still hasn't been put on my device (like it originally had did long before I even rooted properly).
So now TWRP boots up every time I want to just go straight to my download screen and from there I click on download to get to my screen. That's when I use odin and the cf-auto.
I hope I don't sound confusing. I just want to know where can I go from here?
Apparently the Sims Freeplay is being a real PITA about people trying to play their game on a root device (doesn't surprise me with EA), but I want to play it on my device rooted or not... but now my tablet feels like it's both. It's not straight out of the store box and it's not fully rooted...
What the heck am I doing wrong now?
If you have twrp installed you don't need to flash cfautoroot again. Just reboot from within twrp and it will offer to root.
If you are still having problems see the link below.
http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-twrp-t800-t3079488
If you are having problems getting into download mode you are not doing it properly.
Hold POWER + VOL DOWN + HOME.
Under which category will it offer to root and will there be a way to get the sims freeplay working? If not I'd like to get back to straight out of the box for the tablet... but something tells me after reading for a few hours last night that thats impossible.
geekery15 said:
Under which category will it offer to root and will there be a way to get the sims freeplay working? If not I'd like to get back to straight out of the box for the tablet... but something tells me after reading for a few hours last night that thats impossible.
Click to expand...
Click to collapse
If you unroot with the supersu app you will be fully unrooted.
To reroot boot into twrp then reboot.
I have a LG G3 D851 Gold that is stuck on android 4.4.2 (software version: D85110c). It tries to do an OTA update however when it tries installing it it fails halfway through and just reboots and most of the time it says the software is up to date. I tired the LG Mobile Support Tool; when I use that it says I have an update available for a few seconds and then it says my phone is up to date. I called LG, T-Mobile, and Google and they all just blamed the problem on someone else and wouldn't help me.
Any ideas? I have never rooted or flashed a phone before so I don't want do that if I don't have to.
Doctorsab said:
I have a LG G3 D851 Gold that is stuck on android 4.4.2 (software version: D85110c). It tries to do an OTA update however when it tries installing it it fails halfway through and just reboots and most of the time it says the software is up to date. I tired the LG Mobile Support Tool; when I use that it says I have an update available for a few seconds and then it says my phone is up to date. I called LG, T-Mobile, and Google and they all just blamed the problem on someone else and wouldn't help me.
Any ideas? I have never rooted or flashed a phone before so I don't want do that if I don't have to.
Click to expand...
Click to collapse
so the phone you currently have doesn't have root access?
Still_living714 said:
so the phone you currently have doesn't have root access?
Click to expand...
Click to collapse
No, it's not rooted. I've never rooted a phone before so even doing that would be a new thing for me.
Would it help me if I rooted it?
Doctorsab said:
No, it's not rooted. I've never rooted a phone before so even doing that would be a new thing for me.
Would it help me if I rooted it?
Click to expand...
Click to collapse
while taking an official download you can't have root access or it'll throw you into a bootloop. In my opinion you should root so you can really customize your phone and get some pretty cool apps. If you're on kitkat there's this one click root app you can use and it's very easy,probably take you 20 minutes to get root access and install SU app.
Still_living714 said:
while taking an official download you can't have root access or it'll throw you into a bootloop. In my opinion you should root so you can really customize your phone and get some pretty cool apps. If you're on kitkat there's this one click root app you can use and it's very easy,probably take you 20 minutes to get root access and install SU app.
Click to expand...
Click to collapse
I think I will end up doing that and putting on lollipop on the phone, but I haven't been able to find instructions that I could understand.........I don't want to mess up and brick my phone.
Doctorsab said:
I think I will end up doing that and putting on lollipop on the phone, but I haven't been able to find instructions that I could understand.........I don't want to mess up and brick my phone.
Click to expand...
Click to collapse
pm me and I will help you
I have an unlocked HTC 10. I recently received an OTA update.
I have been using android pay just fine with no issues. However after the most recent Android Pay update. I was getting an error message explaining I may need to "unroot" my device..
My device has NEVER been rooted and android pay has worked great!!!
As an extra precaution, I did a factory reset to my phone, and re-downloaded android pay.
Now I get a new error, but very similar. When I try to add a card after installing, now it says
"Android Pay can't be used
Google is unable to verify that your device or the software running on it is Android compatible".
After already factory resetting and uninstalling/reinstalling the app... I'm not sure what to do... I don't want to root or flash... but I am looking for options....
thanks
I read somewhere that flashing elemental X as the kernel will fix this, but I'm waiting for more people to confirm. I'm also guessing flashing a new kernel doesnt requiring wiping or anything? and lastly, how can i backup my existing kernel to reflash in case **** goes haywire? anyway, hope that helps.
Also using S-OFF and LOCKED bootloader will work.
tabp0le said:
Also using S-OFF and LOCKED bootloader will work.
Click to expand...
Click to collapse
RELOCKED bootloader status won't let android pay work?
GottaStayFly said:
RELOCKED bootloader status won't let android pay work?
Click to expand...
Click to collapse
I"m not sure about that.
SafetyNet is looking for the flag that the unlocked bootloader throws, someone more familiar with recent flags than me should know which way the flag is set upon relocking bootloader.
The ElementalX kernel has the option, but I believe that's another option for s-off users, I'm not sure if it will work for s-on unlocked users.
I think if it doesn't pick up "relocked" when it checks SafetyNet, it wont be long until it does. This is a cat and mouse game, and google has the right to "take its ball and go home" with root users, I just wish they wouldn't use that against us enthusiast users, who are their best advocates since we carry so much weight on advising all the non tech oriented unrooted consumers when it's time for them to purchase new smartphones. We are the ones that the rest of consumers call for advice or when something is broken.
Will taking this update break root or cause other issues? Just received the notice a few hours ago.
Current setup:
S-on
Unlocked
Rooted
Stock ROM still (obviously)
SW v1.80.651.1
Sprint
I waited for the N7, and returned it without opening it before the fiasco. Because I was going to wait for the Pixel, which ended up being astronomical in price. So I waited for the V20, only to find it has a "Verizoned" bootloader. And just this past weekend I settled on the HTC 10.
If anybody can provide me helpful information, I would appreciate the consideration.
ETA: NM - simply made a copy on sd card, then renamed with .bak in update folder and nag went away. Seemed to be a small incremental update from .1 to .6.
So it sounds like the lesson here is if you haven't unlocked your bootloader yet, don't, if you want to use Android Pay. From what I've read, using Sunshine to go S-off LOCKED will allow android pay to work, as long as you aren't rooted. Also there are a couple kernels you can use to disable to check for unlocked bootloader.
Is this all correct?
Sent from my HTC One_M8 using Tapatalk
Hello everyone.
I have really tried to find an answer to my question but I failed. If anyone can help me or just give me a hint where to look I will be very thankful.
My problem is that some time ago I have decided to try and install LineageOS on my G960F/DS. Everything went fine, but after few days I wanted to go back to a stock firmware.
I have downloaded a stock firmware, reflashed with Odin, did all the wipes and stuff and my phone works fine (then I realized that S9 has this shi*ty eFuse, but let's forget it now).
Still I am not able to activate my Google Pay. Everytime I try to activate my bank card I get a message
Your phone may be rooted or modified in some different way.
Click to expand...
Click to collapse
I know there is a thong called Magisk Hide, but as far as I know it is not working.
Is there any way to get Google Pay to work?
Magisk hide works on my rooted device.
basicreece said:
Magisk hide works on my rooted device.
Click to expand...
Click to collapse
As far as I know it will not: https://forum.xda-developers.com/galaxy-s9/how-to/root-galaxy-s9-s9-official-stock-8-0-t3843098
Polarkreis said:
As far as I know it will not: https://forum.xda-developers.com/galaxy-s9/how-to/root-galaxy-s9-s9-official-stock-8-0-t3843098
Click to expand...
Click to collapse
Literally just used Google pay, like 2 minutes ago. I'm rooted using magiskhide.
This actually has happened to me also after the last update. I use Google Pay all the time and now it says I'm rooted. I'm not rooted because I have a ATT S9.