Deleted the moto x cam and tried google cam.. than tried installing the motorola cam from the playstore and I get this... what gives? Can anyone help me with this? My phone is screwed up.. actually have had 4 moto x now and each one does this... use the flash and it flashes fine but before the photo snap... so its useless dark pictures.. but thought it was a cam app problem but every cam I try does it.. so it must be hardware related I guess. but now the issue is this app not installed, I get it downloaded fine and starts installing but ends with the attached screenshot.
Thanks
I would recommend NOT deleting system apps in the future. From your screenshot it looks like a Verizon moto x? I'd suggest downloading the 4.4.4 sbf and fastboot flashing the system image
You know you can have both cameras installed and working. No need to uninstall the stock one.
Sent from my Nexus 10 using Tapatalk
if I flash the SPF will I lose any data personal stuff, is that like doing a factory reset?
doitinthedirt said:
if I flash the SPF will I lose any data personal stuff, is that like doing a factory reset?
Click to expand...
Click to collapse
You'll lose everything. Including images, songs, apps etc
thanks I will just use the Google cam I got that to install was just hoping somebody would have a clue as to how to get around this app not installed horsecrap
I am rooted with write protection off and bootloader unlocked
If you simply fastboot flash the system image you will NOT lose any data. If you use rsd to completely flash the entire phone then you will lose data. Like I recommended, I'd flash the correct system for your carrier and Android version
Sent from my XT1060
However, you must use mfastboot,.exe to flash the system.img. Using fastboot will fail on the system.img. Perhaps someone could pull the system camera apk which you could copy back into /system/app and set the permissions properly.
here's a screenshot of the current permissions with the app in the system app folder.. does that look correct? I'm still not showing it as a usable app when I reboot
mfastboot the system.img for what ever version android you are on and problem solved. No data lost. System restored back to stock. Takes all of 5 minutes to do.
Permissions are correct, but that is still the optional camera from Play. I extracted the system camera apk which is the 3.3.20.8 version of the system camera from my T-Mo 4.4.4 version. You are showing Verizon 4.4 so I don't know if it compatible with your system. I'll try to pm you a copy of what I have, but a full mfastboot flash of the system.img would be the best way to restore it.
Thanks, that pic was my cam from my razr m, but i also have the original cam app from the moto x i copied and saved before deleting it.. and it gives the same message
Did you have it backed by chance via titanium backup?
I think I had the free version of titanium pro on my phone at one time, what do you mean backed up.. do you mean saved? It was a few months ago i remember trying to freeze an app and said i needed the pay version so i found another app that freezes free.
doitinthedirt said:
Thanks, that pic was my cam from my razr m, but i also have the original cam app from the moto x i copied and saved before deleting it.. and it gives the same message
Click to expand...
Click to collapse
Did you save and replace the .odex file for the camera also and set permissions on both? Did you use GoogleCamera.apk and GoogleCamera.odex?
not sure why but I did just get my own copy to install one of them, I made a couple copies and uploaded to Google Drive and I did not copy the odex file wasn't aware I had to.
I do appreciate your help!
the version I did get to work was the original Moto X version from my 4.4 moto x. I still want to try and get my razr M 4.1.2 camera to work on it I liked it much better
I don't think that will work. From what I recall from my beloved M, the camera app required different kernels, so you couldn't use them interchangeably. But I like the moto x camera over the google camera.
Related
Okay, I am just wanting to clear things up for myself with this question. I've seen it similarly asked on other threads, but I have yet to find answer to them.
Currently, I am Stock + camera update + rooted with RockMyMoto. I haven't frozen or uninstalled or otherwise done anything to system apps or files (I disabled a few through Android itself before root, but never touched them since) I do use Permissions Denied; an app that does what it says for any app I chose, however I only use it for non-system apps. My phone is essentially stock, with root (bootloader locked). Thats all I want for whenever I update to 4.4 at the moment. Speaking of which...
I am trying to determine the best way to go about this. Since I havent done much to my phone, I am curious to know if I can just install the OTA (since I've altered no system files, but I know this isn't usually advised) then apply the latest root method done by jcase. Can it be as straight forward as that? Or do I absolutely need to flash back to STOCK stock, apply the camera update, the apply the 4.4 update, THEN use his method?
Trying to find a method that is at least safe. Preferably safe, quick and easy. But I know these methods aren't always quick .
NameLessThugZero said:
Okay, I am just wanting to clear things up for myself with this question. I've seen it similarly asked on other threads, but I have yet to find answer to them.
Currently, I am Stock + camera update + rooted with RockMyMoto. I haven't frozen or uninstalled or otherwise done anything to system apps or files (I disabled a few through Android itself before root, but never touched them since) I do use Permissions Denied; an app that does what it says for any app I chose, however I only use it for non-system apps. My phone is essentially stock, with root (bootloader locked). Thats all I want for whenever I update to 4.4 at the moment. Speaking of which...
I am trying to determine the best way to go about this. Since I havent done much to my phone, I am curious to know if I can just install the OTA (since I've altered no system files, but I know this isn't usually advised) then apply the latest root method done by jcase. Can it be as straight forward as that? Or do I absolutely need to flash back to STOCK stock, apply the camera update, the apply the 4.4 update, THEN use his method?
Trying to find a method that is at least safe. Preferably safe, quick and easy. But I know these methods aren't always quick .
Click to expand...
Click to collapse
Pawnymoto hijacks the stock recovery so you won't be able to install the update, you need to flash the stick recovery at the least
Sent on my Moto X
flashallthetime said:
Pawnymoto hijacks the stock recovery so you won't be able to install the update, you need to flash the stick recovery at the least
Sent on my Moto X
Click to expand...
Click to collapse
What do I need in order to do that, or should I just RSD lite back to a stock Moto X?
NameLessThugZero said:
What do I need in order to do that, or should I just RSD lite back to a stock Moto X?
Click to expand...
Click to collapse
I would say its safer to rsdlite back to 100% stock, that way you know everything is ready to accept the ota and you won't end up in a bootloop
Sent on my Moto X
Dear all. I am trying to restore, due to Titanium Backup Pro halting while integrating system updates into rom (I'll never do that again). Because of me doing that, the Google framework was the app that was reintegrating... thus my entire phone was soft-borked. I am trying to restore, but every time I run either the commands listed here and the Moto X Toolkit 1.3.4. Both result in sitting at this point in an infinite loop (waited 20 minutes each time):
Screenshot
Please tell me my phone is not bricked. I just bought the thing, and I made a quick decision to try integrating system updates, which had no problem on my old phone. And I take it that my protection plan does not cover this, even though my phone is a VZW Dev Edition. They would count it as my fault by unlocking the bootloader, wouldn't they? I would think that the warranty at this point still covers things like cracked screens (which I wanted), but not things that are my fault.
I have 4.4 KitKat installed.
Edit: It also sits here indefinitely sometimes:
INDEFINITELY SOMETIMES (lol - makes so much sense)
CartlandSmith said:
Have you tried flashing 4.4 sbf firmware using RSD Lite? Try flashing the 4.4 sbf firmware using RSD Lite first.
Click to expand...
Click to collapse
Didn't realize there was such a thing. I was relying strictly on Google. Thanks, I'll try.
Edit: Lol.... so that's what an SBF is.. I had no idea it was practically the same package.
Edit: Apparently my phone must be bricked. It says "Connected", but can't read any version information. :
Screenshot Edit: NVM... used wrong XML.
It's flashing now. And....FINALLY!!! It continued!
Phone is booting now! Thanks so much.
CartlandSmith said:
And that is the beauty of RSD Lite - it won't let you flash the wrong XML!
Click to expand...
Click to collapse
Apparently that XML in that post doesn't erase userdata or customize. I needed this because of my Google services framework problem (apparently my backup was deleted from TiBu, and it was already integrated into the rom...again, never doing that again), so I added the entries to the XML. Phone is first-time booting, and the wizard showed up at boot.
Thanks again.
Never....ever....ever restore system apps with titanium backup...or any app. You've seen why.
I'm sure you know...but others reading this. Never.
Ever. Lol
Sent from my Nexus 5 using Tapatalk
kj2112 said:
Never....ever....ever restore system apps with titanium backup...or any app. You've seen why.
I'm sure you know...but others reading this. Never.
Ever. Lol
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
But what about reintegrating the system app updates that are downloaded from the market? They normally can't replace the system app, because the system partition is write-protected (of course). TiBu has an option to reintegrate these into the system partition.
I'm rooted and unlocked with 4.4.x XT1060 verizon
I don't want to take the OTA but i'm getting tired of being nagged to do so. I've tried moving the update file out of the 'cache' folder to somewhere else, but literally every time i turn on my phone I'm being nagged to upgrade.
Ideas?
peters4n6 said:
I'm rooted and unlocked with 4.4.x XT1060 verizon
I don't want to take the OTA but i'm getting tired of being nagged to do so. I've tried moving the update file out of the 'cache' folder to somewhere else, but literally every time i turn on my phone I'm being nagged to upgrade.
Ideas?
Click to expand...
Click to collapse
I believe using Titanium Backup to freeze the MotorolaOTA application is the usual advice. Older advice is to rename the OTAcerts.zip file in /system/etc/security but I don't know if that still works.
thanik you for the TBU freeze advice. i'll give that a try.
easier than that... go into settings>apps>all, scroll down to MotorolaOTA and untick the "show notifications" box. Done.
Thanks for this insight.
if you are rooted, to stop OTA's you can also rename 3C_OTA.APK and 3C_OTA.ODEX in either /apps or /privapp folder (using a file explorer with root abilities). Then you need to boot to recovery and clear cache..
When you are ready for OTA"s again, just rename them back, and reboot.
KidJoe said:
if you are rooted, to stop OTA's you can also rename 3C_OTA.APK and 3C_OTA.ODEX in either /apps or /privapp folder (using a file explorer with root abilities). Then you need to boot to recovery and clear cache..
When you are ready for OTA"s again, just rename them back, and reboot.
Click to expand...
Click to collapse
I did this but am still getting the OTA screen coming up. Maybe it's because the update file is already downloaded? If so, where does that hide. I've been looking but can't seem to find it. I've also been looking for the MotoOTA app to freeze that but that doesn't seem to exist anymore. I kinda wondering if I delete the update file, having the OTA.apk's renamed might stop it from trying again. Just not ready for the upgrade plus would rather have the full XML update instead of the OTA to be to fix any screw-ups I might have.
Yeah, same. The notifications can be dealt with using the "show notifications" step above. But the full screen pop-up reminder is harder to avoid. I'm surprised Moto is pushing this so hard.
What about uninstalling the Motorola update services update?
Sent from my XT1053 using Tapatalk
eldamobo said:
Yeah, same. The notifications can be dealt with using the "show notifications" step above. But the full screen pop-up reminder is harder to avoid. I'm surprised Moto is pushing this so hard.
What about uninstalling the Motorola update services update?
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Oddly enough, I only got one notification and then never again. Now it's just the full screen interrupt. It was really annoying when at a concert when trying to grab a video or two. Kept popping in and stopping the recording. If I wasn't at work I'd try to remove the update services. For now, I've gotten them frozen so let's see if it still nags like that.
I wish that once you say 'Maybe Later' at the first prompt it just leaves it to the update software menu under 'About Phone' instead of trying to force it.
dandroid213 said:
I did this but am still getting the OTA screen coming up. Maybe it's because the update file is already downloaded? If so, where does that hide. I've been looking but can't seem to find it. I've also been looking for the MotoOTA app to freeze that but that doesn't seem to exist anymore. I kinda wondering if I delete the update file, having the OTA.apk's renamed might stop it from trying again. Just not ready for the upgrade plus would rather have the full XML update instead of the OTA to be to fix any screw-ups I might have.
Click to expand...
Click to collapse
Did you boot to recovery and Erase cache?
When the OTA zip is downloaded, its stored in /cache which is only accessible if you are rooted. So booting to recovery and erasing cache will remove it from your phone.
KidJoe said:
Did you boot to recovery and Erase cache?
When the OTA zip is downloaded, its stored in /cache which is only accessible if you are rooted. So booting to recovery and erasing cache will remove it from your phone.
Click to expand...
Click to collapse
*This is on a Dev Edition if that makes a difference*
I do have access to /cache and it had the same in it as prior to clearing the cache, 3 folders (backup, lost+found, and recovery) and one text file (last_log under recovery.) This is a change from the last Moto I had. Granted that was the Droid X (damn them locked bootloaders) so older Android version. I've also looked for other ZIP's and the newest I can find is from the last time I had to update SuperSU.
I also cleared the davlik-cache on the second attempt but not sure if that would even come into play here. Unless TWRP is borked, cache has been cleared a few times now and now davlik as well.
But will say after freezing the Update Services, I haven't gotten the full screen nag again. Not sure what else is dependent on that but if it works, I'll keep it frozen for now and try breaking it more once home.
did you ever figure this out? My verizon dev edition moto x is driving me crazy with the OTA pop up...
fully rooted, unlocked over here, TWRP recovery.
I just renamed the OTAcerts.zip file in /system/etc/security and the 3C_OTA.APK and 3C_OTA.ODEX files in /system/privapp and rebooted.
I will see if that works...
So with a massive amount of thunderstorms last night I was without power (still am but at work so meh.) So I never got a change to try anything else. But I will report that freezing the Moto Update Services with TBackup worked perfectly. Haven't gotten a nag screen since. I'm just worried about other issues later down the line when trying to update other Moto services.
I'm not rooted, so for those not rooted, I'm using greenify on the update service. It also seems to shut the full screen nag off for now. That said, I think freezing would be better.
Not able to find update file to delete
Trying to get rid of nag screen for update MOTO X 2013 Sprint to version 212.144.2. Unchecked MotorolaOTA app, this did not work.
I am rooted, anyone know where to find file with Root Explorer to delete it? I don't want to accidentally install update.
On a side note, I am being asked to upgrade to v212.144.2 which I don't see anyone installing this OTA. BTW I am using my Sprint phone in South America
I just purchased a droid 4 from Verizon, have wiped it a few times, but my front facing camera, keyboard, soft key lights are not working. I have searched online for fixes, Motorola said i could pay 150.00 in order to get it replaced. I figured i would come here first to see if anyone had a suggestion or a link to where i could wipe it before it took the 4.4 patch to where it seems to have totally messed it up according to other online sources .
timothy_pierce said:
I just purchased a droid 4 from Verizon, have wiped it a few times, but my front facing camera, keyboard, soft key lights are not working. I have searched online for fixes, Motorola said i could pay 150.00 in order to get it replaced. I figured i would come here first to see if anyone had a suggestion or a link to where i could wipe it before it took the 4.4 patch to where it seems to have totally messed it up according to other online sources .
Click to expand...
Click to collapse
Are you running with the stock rom?
Have you tried a custom rom?
I mean do you know if it't software issue or hardware issue?
Sent from my XT894 using Tapatalk
dom2319 said:
Are you running with the stock rom?
Have you tried a custom rom?
I mean do you know if it't software issue or hardware issue?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
I am running the latest version of android for that series of phone, believe its 4.4 from verizon, i have not rooted it yet, i am trying to figure out how to get it back to the original state before the updates. As it seems since the update many consumers have had these same issues with out being able to fix them, i have tried fixes that i obtained from the Motorola forums and the lighting situation did not work. Am not sure its hardware due to the keyboard being functional. I appreciate any and all help.
ok found a video on how to bypass the non sim set up panel and here are the versions of android i am running.
98.72.188.xt984.Verizon.en.US
Android version 4.1.2 sorry i messed up the version earlier.
timothy_pierce said:
ok found a video on how to bypass the non sim set up panel and here are the versions of android i am running.
98.72.188.xt984.Verizon.en.US
Android version 4.1.2 sorry i messed up the version earlier.
Click to expand...
Click to collapse
Hi Timothy,
OK you're running Android JellyBean, AFAIK Verizon never released a Kit-Kat (Android 4.4) update for the device.
Personally, given that AFAIK it's not possible to roll back to a previous version of Android (you can only reinstall the previous version), I would suggest you root it, install SafeStrap and do a quick install of something like Cyanogen (not the best ROM for Droid 4 IMHO but will quickly do the job). At least those can be rolled back.
Rooting and installing SafeStrap is SO utterly easy on this device that it should be made harder
For a start, everything you'll need, if you want, can be grabbed from my Google Drive
h t t p s://drive.google.com/folderview?id=0B3MTT4jOK738fmdLLURMQVBGWkVpTDBMTmg1UGFUd3JWNDNlcUVzQWZFQXBpT3dCMFJhdTg&usp=drive_web&tid=0B0EWnwDplBc0fnBGbDg3ZmdZNC1ET1JZeVRWdE8tZ2p1Um41OThLeTZ2WWtRNE9TUXJpS2M
If you don't have any file manager yet (as you'll need one), ES File Explorer is a great one, as you'll most certainly need it.
Rooting:
Get Towel root from:
h t t p s://drive.google.com/folderview?id=0B0EWnwDplBc0fi1KMVVIRmQteDhFYWcwSGFselpXWmpfV29LWlZlZVVHdlU0b0FBQnYtNkk&usp=drive_web&tid=0B0EWnwDplBc0fnBGbDg3ZmdZNC1ET1JZeVRWdE8tZ2p1Um41OThLeTZ2WWtRNE9TUXJpS2M#list
install it and root your Droid4
Installing SafeStrap:
Check out this page for info about SafeStrap
h t t p://blog.hash-of-codes.com/how-to-safestrap/
Once your device is rooted, you can install SafeStrap
Again you can grab a copy from my Google drive:
h t t p s://drive.google.com/folderview?id=0B0EWnwDplBc0fk5aeUhFSjlQMzZ2TXNYM0lsWVRDWklLOU1nYkUybzU1emJDV1IwS0tkazg&usp=drive_web&tid=0B0EWnwDplBc0fnBGbDg3ZmdZNC1ET1JZeVRWdE8tZ2p1Um41OThLeTZ2WWtRNE9TUXJpS2M
Installing a custom rom:
Once you have installed SafeStrap
You can download CM11 which I've tested from:
h t t p s://drive.google.com/folderview?id=0B0EWnwDplBc0fnJJd0s1ZV85aEE1YkF0TjNzM28tcmxfOVkzZVJ0OUVhLThrR29sb19vVW8&usp=drive_web&tid=0B0EWnwDplBc0fnBGbDg3ZmdZNC1ET1JZeVRWdE8tZ2p1Um41OThLeTZ2WWtRNE9TUXJpS2M
- Copy the file to your SDcard0 (usually named MOT)
- Boot into SafeStrap, create a small partition (1000 MB for data is enough) in Slot1
- install CM 11 and see if the problem is fixed in CM11 and report back to me
Take care
Dominique
or just see [INDEX] Motorola Droid 4
Anyone managed to get Android Pay working?
I keep getting an error message when trying to add a card.
I'm rooted on 5.1 with latest play services etc.
Tried rootcloak and disabling supersu but neither worked.
acetkbez said:
Anyone managed to get Android Pay working?
I keep getting an error message when trying to add a card.
I'm rooted on 5.1 with latest play services etc.
Tried rootcloak and disabling supersu but neither worked.
Click to expand...
Click to collapse
1. Flash a stock (unmodified build.prop), unrooted rom.
2. Install Android Pay and the latest Google Play Services (version 8.x-230, not the one from google play store)
3. Add all credit cards you want to use in Android Pay
3. Flash your rooted rom (don't wipe data, but wiping cache is okay).
4. Use it.
You will not be able to add additional cards while on a rooted rom, but you will be able to use Android Pay. If you need to add more cards, you need to go back to the stock rom.
Android Pay no longer works on modified system images. There is no way to bypass this, currently.
TheSt33v said:
1. Flash a stock (unmodified build.prop), unrooted rom.
2. Install Android Pay and the latest Google Play Services (version 8.x-230, not the one from google play store)
3. Add all credit cards you want to use in Android Pay
3. Flash your rooted rom (don't wipe data, but wiping cache is okay).
4. Use it.
You will not be able to add additional cards while on a rooted rom, but you will be able to use Android Pay. If you need to add more cards, you need to go back to the stock rom.
Click to expand...
Click to collapse
I'm on the 5.1 OTA but I still can't add my card.
GreaterLesser said:
I'm on the 5.1 OTA but I still can't add my card.
Click to expand...
Click to collapse
What error message do you get? Are you sure you've installed the correct google play services? It's not the one you get from the google play store. You have to find it elsewhere. The version that I'm using is 8.1.15 (2250156-230).
TheSt33v said:
What error message do you get? Are you sure you've installed the correct google play services? It's not the one you get from the google play store. You have to find it elsewhere. The version that I'm using is 8.1.15 (2250156-230).
Click to expand...
Click to collapse
Should I use the latest one from here then? http://www.apkmirror.com/apk/google-inc/google-play-services/
GreaterLesser said:
Should I use the latest one from here then? http://www.apkmirror.com/apk/google-inc/google-play-services/
Click to expand...
Click to collapse
Use the one that matches the number I provided in my previous post exactly (it ends in 230, and it's listed under September 14th ). The last three numbers correspond to different types of phones (android version, screen form factors, etc.). 230 is the code for our Turbos on 5.1.
TheSt33v said:
Use the one that matches the number I provided in my previous post exactly (it ends in 230, and it's listed under September 14th ). The last three numbers correspond to different types of phones (android version, screen form factors, etc.). 230 is the code for our Turbos on 5.1.
Click to expand...
Click to collapse
Strange - That's what I did. I'll try wipe the app's data and start over. Thanks
EDIT: I figured it out. I forgot I had changed my phone's resolution to 1080p and dpi down to 480 (which fits GP Services 8.x-238 but not confirmed to work with 8.x-230 in Android Pay) to save on battery when gaming. So it was the custom DPI that was messing with play services. Changed res back to 1440p and DPI back to 640 and rebooted. It works fine now. Thanks
GreaterLesser said:
Strange - That's what I did. I'll try wipe the app's data and start over. Thanks
EDIT: I figured it out. I forgot I had changed my phone's resolution to 1080p and dpi down to 480 (which fits GP Services 8.x-238 but not confirmed to work with 8.x-230 in Android Pay) to save on battery when gaming. So it was the custom DPI that was messing with play services. Changed res back to 1440p and DPI back to 640 and rebooted. It works fine now. Thanks
Click to expand...
Click to collapse
Yep, that'll do it.
TheSt33v said:
Yep, that'll do it.
Click to expand...
Click to collapse
Similar instructions for 4.4.4 rooted turbos? And does anyone know if a TiBu restore for AP brings back cards?
Sent from my Electric Boogalocked Turbo
rayjr13 said:
Similar instructions for 4.4.4 rooted turbos? And does anyone know if a TiBu restore for AP brings back cards?
Sent from my Electric Boogalocked Turbo
Click to expand...
Click to collapse
Theoretically, yes, except you'll want the version of google play services that ends in 030 since you're not on lollipop. Not sure about TiBu, but it should work.
030, exactly. that what I was anticipating Now to find a stock mofo kk img lol
---------- Post added at 09:31 PM ---------- Previous post was at 08:49 PM ----------
I'm surprised I'm struggling so much to find a stock unrooted system image for mofo. Downloading the firmware files but not sure I know which is which from Rootjunky's website and if it 21.21.15 like I believe it to be can i flash with mofo onto that firmware? I've only flashed using 21.44.15
Argh, noticed that I couldn't get Android Pay working today as well. Sad to see that it requires a reflash, but such is life. Thanks for all the info!
-Collin-
CollinFX45 said:
Argh, noticed that I couldn't get Android Pay working today as well. Sad to see that ito requires a reflash, but such is life. Thanks for all the info!
-Collin-
Click to expand...
Click to collapse
Well there are supported mofo flashable images for lollipop but not for KK yet. This would allow system flash only. And then reflash back to your current modo system. Waiting for a stock KK image w/o root. Still can't understand how/why this hadn't been available since the start of mofo
Sent from my Electric Boogalocked Turbo
Android Pay no longer works with any rooted image. There is no working method to use it yet. Older methods have been broken by Google.
Also, if you want a stock KK image, simply flash the sparsechunks from the stock KK firmware with fastboot. The one on rootjunky's website should work fine, and fastboot won't allow you to flash an image that is not correct for your phone, unlike mofo.
Those rootjunky images aren't the OTA system 21.44 are they? What did Google fix? Guess old Google wallet it is for now.
Sent from my SCH-I605
rayjr13 said:
Those rootjunky images aren't the OTA system 21.44 are they? What did Google fix? Guess old Google wallet it is for now.
Sent from my SCH-I605
Click to expand...
Click to collapse
I don't remember which version it is, but if rootjunky posted it, it's an image that is compatible with mofo. I'm pretty sure he directs you to that image in his video tutorial on how to use mofo. If I understand correctly, Google updated their Safetynet api (which is responsible for Android Pay security enforcement, among other things). In the past, it only did a check when you added a card, which is why you could get around it by adding cards with a stock rom and switching to a modified rom later. Now it checks every time you try to pay for something.
acetkbez said:
Anyone managed to get Android Pay working?
I keep getting an error message when trying to add a card.
I'm rooted on 5.1 with latest play services etc.
Tried rootcloak and disabling supersu but neither worked.
Click to expand...
Click to collapse
Won't work on rooted devices, cloaked, or otherwise.
Tapped out from my Motorola Droid Turbo, featuring Android 5.1. Please pardon my brevity.