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.
Related
I've been on this forum for roughly a week looking through articles and I'm seriously confused at this.
I have a Samsung Verizon note 4 on Lollipop
Baseband N910VVRU2BOG5
I'm trying to either downgrade it, root it, etc. Everything I've tried just sends me in circles. I get theres no perma-root method, but can I do anything at this point?
DikStarrbuck said:
I've been on this forum for roughly a week looking through articles and I'm seriously confused at this.
I have a Samsung Verizon note 4 on Lollipop
Baseband N910VVRU2BOG5
I'm trying to either downgrade it, root it, etc. Everything I've tried just sends me in circles. I get theres no perma-root method, but can I do anything at this point?
Click to expand...
Click to collapse
It depends on what you want to do, as there are ways around doing certain things that usually require a rooted device. For instance, if you want to back up your apps and their data, there's an app called Helium that works on non-rooted devices.
will4958 said:
It depends on what you want to do, as there are ways around doing certain things that usually require a rooted device. For instance, if you want to back up your apps and their data, there's an app called Helium that works on non-rooted devices.
Click to expand...
Click to collapse
Right now, what I really want to do is 'block' mock locations check. But I cannot figure out how to downgrade my phone, if its even possible. And I cant root my phone. I have tried Kingroot, but it said my phone wasnt rootable yet. But I read somewhere I can downgrade my phone to a rootable OS, but that didnt work either, so I dunno what I can do.
DikStarrbuck said:
Right now, what I really want to do is 'block' mock locations check. But I cannot figure out how to downgrade my phone, if its even possible. And I cant root my phone. I have tried Kingroot, but it said my phone wasnt rootable yet. But I read somewhere I can downgrade my phone to a rootable OS, but that didnt work either, so I dunno what I can do.
Click to expand...
Click to collapse
Unfortunately, unless you updated to a version of Lollipop using one of the safe update options mentioned in one of the threads, you can't downgrade to a previous version. There is a program called Debloater, I believe, that will block any app you want on your phone, but you still can't uninstall said app. All the program does is essentially disable the blocked app from running. For instance, when I didn't want my phone automatically checking for system updates, I would use Debloater to block the two apps on the phone that are required for it to perform those automatic checks. All you do is start Debloater on your computer, plug your phone into a USB port, set the phone to 'Media Device', and wait for the program to recognize the device. Once it does, just select the app(s) you want to block. Just out of curiosity, though, what version of Lollipop are you currently running? If you're on 5.0.1, I can understand why you don't want to stay there. I was on it for a little while, but only as a pit stop on my way to 5.1.1. I can say with assurance that after running my phone on 5.1.1 for at least a couple weeks or more, it runs very smoothly, even better than it did on 4.4.4, which was supposed to be better than 5.0.1 as far as performance goes. My battery lasts about as long as it did on Kit Kat, and I haven't experienced any crazy overheating issues.
Hello,
I've gone as long as I can without rooting, but the call of the wild is just too strong. After reading a few posts, I'm comfortable with the process, but just wanted to make sure that I am not going to shoot myself in the foot if I take the OTA to the latest Sprint version (my current software version is 2.42.651.6).
I basically just want to be able to tether internet to my kids' tablets while we're on a road trip, and I need Safetynet to not trip, so that my banking apps stay functional. It looks like I've got a couple of ROM options that will be Safetynet safe; am I correct to assume that they offer native tethering as well, or will I need to separately modify the database files (as described in threads here at XDA)?
Thanks!
Both Viper and LeeDroid can pass Safetynet and has built in tethering.
You can also go back to stock if you need to. Keep in mind there are a couple of banks that does detection beyond Safetynet.
I've been using Viper ROM for the past year. BoA, Chase, Amex and Discover work with my rooted ROM. So does PayPal and Venmo.
Android Pay however, doesn't.
Viper has Magisk to bypass Safetynet. However, I've not tried it because it was too much of a bother for me to flash an RUU and then flask Magisk on. You can try it if you are still unrooted. It is perfect for these kind of scenarios.
Recently, I decided to update my rooted tab to the newest firmware, through an application on my Windows PC. After updating, I noticed that Netflix now refuses to work despite the fact I had it working on my previously rooted device. Is there any way to be able to actually get it up and running again?
Have you tried uninstalling the app and reinstalling it?
Ziken said:
Have you tried uninstalling the app and reinstalling it?
Click to expand...
Click to collapse
I just tried that, and as I expected, still met with the same message.
On a rooted device I had before this one, I couldn't get Netflix to work. I went to their site and even made a phone call to find out there is an apk file for rooted devices buried on their site. Seems like I may have had to try a few of them to get one to work. This was probably 3-4 years ago.
Oh, and I had to explain to the guy what "rooted" means and why I wanted to do that!
Netflix is broke. Nobody has fixed it.
Hi,
Netflix has confirmed to Android Police that since version 5.0, released mid-May, the application relies entirely on Google's Widevine DRM. But it only works if Android is intact.
In practice, the availability of the application depends on the eligibility of your smartphone to SafetyNet, and therefore to Android Pay. So an unlocked smartphone no longer has access to Netflix on the Play Store, even if it meets the requirements of Widevin DRM
But no matter: the application itself always works on smartphones rooted and unlocked, at least for the moment.
If it is already installed, you can continue to enjoy it without doing anything. If it is not, simply install it manually, after downloading the APK from APKMirror
https-www-apkmirror-com/apk/netflix-inc/netflix/
Regards,
AxelEric.
I bought galaxy watch and I own a rooted xiaomi mi 9.
Samsung pay on my smartphone says I cant use it because its rooted, even if im using magisk hide and safety net is passing. I can even use google pay, everything works but samsung pay!
Can you help me?
Looks like ive resolved it..i renamed magisk with random name, deleted every reference innfile system (every folder named twrp/magisk ecc), then it started working
As I know with rooted smartphone don't working pay service. I guess reason is security. If you found a way to get this service with rooted smartphone - lucky you. But even banks as I know stopping to work if detecting that smartphone is rooted. Anyway I can't understand why need these days to root smartphone even with not stability OS which is not official and only creator know will be any new version of it or not. Smartphones these days have a lot of memory is powerful and most apps they letting to delete or hide it. Why need to modify original stock ROM? For problems with service, because like this one stopping to work and need to find way to get it again. I just can't understand.
Hello,
Yesterday, I successfully rooted my Samsung Galaxy S10+. But since I still had some questions about it, I went on and posted a thread here. User Spaceminer then pointed out that my original post was in the wrong subforum and linked me here. Naturally, I looked at some of the most popular posts in hopes to find answers to my questions. But what I found confused me more than it gave me answers.
Since 2014 with the Samsung Galaxy S5 I got used to rooting in order to disable bloatware, protect my data and customize my phone. I continued doing that with the S8+ until I recently got my hands on the S10. Now, my main reason for rooting are still the same; I want disable (not necessarily uninstall) bloatware, protect my privacy and customize my phone (such as changing the background of the dial when calling someone). But that thread made me wonder if it is even essential to root. I also found a similar post on reddit and most answers seem to agree that it is not necessary to root your phones.
Now, my situation is a bit different. For one, I already rooted my phone. Second, I don't care about warranty nor custom ROMs. But I do want to install a banking app. Also, it is a bit cumbersome to not only have to manually update your phone with every update but the booting requirements with the warning screen are also a bit annoying. So, my question is the following:
What are the advantages of rooting that are not possible without? I have 3 main concerns: Bloatware, Privacy and Customization.
The reason why I posted this in a separate threat is that I was not able to come to a definitive conclusion on my own and most discussion threads are over a year old. By now, the whole process of rooting and what is possible changed since then, so I want to get a more recent insight. I hope you can help me out.
With kind regards,
DasMalzbier
Tbh root is not needed, unless you want to use a custom rom. Most things are already in the android now.
Calyx os not make for samsung Galaxy series and 12 update also comes this year so i think rooting is unnecessary for s10 series
Root is 100%, absolutely necessary for using the phone. I cannot use any phone without it. Critical root-only capabilities:
full system backups (in twrp)
titanium backup
disable updates permanently (update ONLY when want to)
app freezers (app quarantine)
disable/remove bloatware
disable google play services/google play
automate/tasker
cf lumen
adblockers
wifi tether
busybox
superuser
ssh tunnel
update android to later version / install custom roms
optimize system
button mapper
custom theming / substratum
nav gestures
tidypanel
xposed
root explorer
app privacy customizations
3c all-in-one toolbox
more
Without root, the phone is unusable to me. I will never buy any phone without root capability. I am willing to go to different carriers just to get root on the device, or go to different manufacturers if root is blocked. For example, I will never buy a huawei device - they are locked.
I would like to say yes but I can't. the stock apps are very well designed.
The biggest concern is that custom Roms are released faster than modded apps.
For example I tried about ten GCAMs and all of them have a bug... and it becomes more complicated with Exynos.
OpenGcam is not worth samsung app.
Unable to get voice match to work.
Alarms that you can't set to a specific day with the google app.
And so on.
Root is useful when the manufacturer no longer updates the devices.
I regret having Root mine because I lost Samsung Pay and other things.
DemotionFR said:
I would like to say yes but I can't. the stock apps are very well designed.
The biggest concern is that custom Roms are released faster than modded apps.
For example I tried about ten GCAMs and all of them have a bug... and it becomes more complicated with Exynos.
OpenGcam is not worth samsung app.
Unable to get voice match to work.
Alarms that you can't set to a specific day with the google app.
And so on.
Root is useful when the manufacturer no longer updates the devices.
I regret having Root mine because I lost Samsung Pay and other things.
Click to expand...
Click to collapse
The only one that would have any consequence of rooting is Samsung Pay.
xbt- said:
Root is 100%, absolutely necessary for using the phone. I cannot use any phone without it. Critical root-only capabilities:
full system backups (in twrp)
titanium backup
disable updates permanently (update ONLY when want to)
app freezers (app quarantine)
disable/remove bloatware
disable google play services/google play
automate/tasker
cf lumen
adblockers
wifi tether
busybox
superuser
ssh tunnel
update android to later version / install custom roms
optimize system
button mapper
custom theming / substratum
nav gestures
tidypanel
xposed
root explorer
app privacy customizations
3c all-in-one toolbox
more
Without root, the phone is unusable to me. I will never buy any phone without root capability. I am willing to go to different carriers just to get root on the device, or go to different manufacturers if root is blocked. For example, I will never buy a huawei device - they are locked.
Click to expand...
Click to collapse
can you carrier /network unlock with the root >?
NickosD said:
Tbh root is not needed, unless you want to use a custom rom. Most things are already in the android now.
Click to expand...
Click to collapse
No, even if you wanna use custom rom you don't need to root. Just pick the rom with the apps you want or just use the gapps packages you want, if want essential to work gapps then use pico or nano. If there is still something you want to remove and the romdoesn't allow, just use adb shell commands and thats it. Less issues with banks not working because of Magisk (root). I know Magisk has a feature to hide itself, change its name but depending on the app, the libs can be found and know that is Magisk, so for security purposes some apps don't work and some aren't even shown in the Google Play Store just because you rooted the device.
logandavid said:
maybe now the root is not needed but later down the road when your phone will get obsolete and newer android OS updates will be halted for S10+ then you'll be more attracted towards custom roms. Actually it is just personal preference.
Click to expand...
Click to collapse
It's happening right now, I doubt S10+ will receive Android 13 and now just security and bug fix updates are being shipped by Samsung.
Haknor said:
It's happening right now, I doubt S10+ will receive Android 13 and now just security and bug fix updates are being shipped by Samsung.
Click to expand...
Click to collapse
It won't get any new Android upgrades AFAIK.
But appart from tripping knox, what else do I lose if I unlock my bootloader? I read once, quite a while ago, that the battery is limited to 80% of its full capacity. Is that true?
io_gh0st said:
It won't get any new Android upgrades AFAIK.
But appart from tripping knox, what else do I lose if I unlock my bootloader? I read once, quite a while ago, that the battery is limited to 80% of its full capacity. Is that true?
Click to expand...
Click to collapse
Depending on the version, you'll notice stock camera to be limited or not work as expected, secure folder, dual messenger either not working, it can trigger some banks or payment apps (especially if you root), no more ota updates (if you keep using stock rom), drm content can stop working, samsung pay, Play Store might limited the apps you see and so on... Not sure about the battery, for me unlocking the bootloader and switching to another rom made my battery last more than stock, but it depends on the rom, the device, it's not a rule of thumb.