So I just tried to setup my Google Wallet on my Nexus 7. It said my device was not supported this is the message I received: "Some users may disable important security mechanisms in order to gain system-level "root" access to their device. We strongly discourage doing so if you plan to use Google Wallet. We are unable to support devices with the unauthorized operating systems as the security layers of the device may be limited." So my question is there ANY way to bypass this and use wallet?
It still works.. Just ignore the message...
I get the same on my GSM Nexus
raqball said:
It still works.. Just ignore the message...
I get the same on my GSM Nexus
Click to expand...
Click to collapse
okay, thanks. how come i can't see my credit cards that i have added on my computer?
The unsupported device message for being rooted is normal it will still work. Wallet accounts are individual to the device which is why you prob dont see the cards. Wallet on my GNex is a diff id than the one on my N7.
dbett4 said:
okay, thanks. how come i can't see my credit cards that i have added on my computer?
Click to expand...
Click to collapse
You have to add your credit card to the "Google Prepaid Card"
From there you can transfer funds from your credit card you linked to the Google Pre Card and set that as your default card.
Google wallet doesn't show in play after rooting.
I got that display after I rooted.
OTA Rootkeeper fixed the problem - just temporarily unroot before stating wallet.
The message is there for a reason. If your nexus is rooted and somebody steals it, they can use su to access the Google Wallet asec data without needing to enter the PIN. Doing a "temporary unroot" might suppress the message but it doesn't actually solve the security problem.
I'm glad to see this thread, as I was wondering if wallet would still work now that I've rooted.
I have to admit, I don't really see how Wallet on a tablet can be considered convenient. I can see it on a phone, since I always have that with me. That said, I'll happily use the free $10!
Related
There are dozens of threads about this issue, but no-one knows how to solve it. It's time to badger Google about it. Here's how:
Click this link:
http://support.google.com/googleplay/bin/request.py?&policy=apps&contact_type=contact_policy
Select "Payment, purchasing or pricing", then "Other" (do not select "My payment method is grayed out" as it takes you nowhere).
Type your name, then your Google order number if you know what it is. I don't, so I just typed "NA".
Under Issue description I typed the following:
"I can't use my Google Play balance ($25.00) for any order. This option is grayed out and the following error is displayed: "This payment method cannot be used for this purchase. (RBC)". Please advise.
Thanks,
[my name]"
Where did you activate your Nexus 7 and which country do you use it in? It's only possible to use the 25USD in the USA as far as I know. This is how I bypassed it in the UK (Wanted to buy TV shows, Music etc).
1. Download and install Hotspot Shield.
2. Download and install Connectify.
Doing this will;
1. Make your connection think it's a USA connection via a proxy
2. Allow you to forward the USA connection to your Nexus 7 using a personal WIFI Hotspot.
Now my Nexus 7 thinks it is in the USA and this allows me to use Play Music, Play Magazines, Play Movies AND TV (This includes buying it).
Please NOTE this is my second Nexus 7. The first one I used on my primary email and received the £15 then I tried this with my second. I used a new gmail address and to my surprise it works flawlessly. That is untill I run out of Credit. I've now added both emails to my Nexus(es?) and can access all the Apps and Games from my UK account and everything else from my US account. My only gripe is all the prices are in USD and have to buy apps and games on my other device to stop it from realising I'm not in the USA.
I'm getting this error
TheChaoticLlama said:
Where did you activate your Nexus 7 and which country do you use it in? It's only possible to use the 25USD in the USA as far as I know.
Click to expand...
Click to collapse
To the best of my knowledge I used a US-based VPN throughout the process. Maybe I missed something.
Bamboo_flute said:
I'm getting this error
Click to expand...
Click to collapse
Then please report it to Google. The more support tickets they get about this issue, the less likely they are to ignore it.
Google's reply but helpless
I get the replay from Google for same subject but it is not helpful at all. Can anyone work out ?
The contents of Google reply as below:
I appreciate you writing in with your question. I understand you are trying to use your $25 credit, but the option is grayed out. I know how frustrating this can be, especially when you would like to use it. Below I have provided the info needed to help you with this issue. And some explanation on the credit itself.
Your Google Play $25 credit is our gift to you when you have, or add, a valid form of payment to your Google Wallet account.
Your Google Play credit is ready to use right away. Just open the Google Play Store app on your Nexus 7 or visit play.google.com and start shopping, and remember to select “Google Play balance” when you’re checking out. If you have credit remaining, you can use it on your next Google Play purchase.
Your Google Play credit can only be used on Google Play. You can shop on the web at play.google.com or on the Google Play Store app on your phone.
*Note that the $25 credit may not be used to buy a subscription or in the Devices section of play.google.com toward the purchase of a Nexus device or on any device accessories.
Google Play credit can not be combined with other payment methods and is not redeemable for cash. For full terms and conditions, please visit: http://play.google.com/intl/en_us/about/offer-terms.html
If I can assist you further or if you have any concerns, please let me know.
Regards,
Coty
The Google Play Support Team
oren_b said:
There are dozens of threads about this issue, but no-one knows how to solve it. It's time to badger Google about it. Here's how:
Click this link:
http://support.google.com/googleplay/bin/request.py?&policy=apps&contact_type=contact_policy
Select "Payment, purchasing or pricing", then "Other" (do not select "My payment method is grayed out" as it takes you nowhere).
Type your name, then your Google order number if you know what it is. I don't, so I just typed "NA".
Under Issue description I typed the following:
"I can't use my Google Play balance ($25.00) for any order. This option is grayed out and the following error is displayed: "This payment method cannot be used for this purchase. (RBC)". Please advise.
Thanks,
[my name]"
Click to expand...
Click to collapse
I think they're deliberately being useless. It's more cost-effective for Google to keep the $25 (multiplied by the number of users) than to actually provide this sum to customers.
I have written to Google and have received 4 replies from the CS person who kept copy pasting information from the FAQs. None of their copy-pasted information had anything to do with what I was telling them. >_> I'm so frustrated... Not so much that I can't access the remaining balance I have but rather that I can't change my home address...
I have a Nexus 10. I wanted to add my corporate email to the device. When I did I was told I had to add a pin number and encrypt the device. I performed both of these actions no problem. I rebooted the device twice during all of this and was able to enter my pin successfully and use the device.
Fast forward to this afternoon. After using the device for awhile I determined that the slowness caused by the encryption was no longer worth having my corporate account on the device.
I go into Settings and delete the corporate account. I tried to go into Security to remove the pin and encryption but both were greyed out. I thought all I had to do was reboot the device and I would be able to disable both.
I rebooted and now I'm stuck at the "Type password to decrypt storage". My pin no longer works on this screen. It keeps giving me a response of "Try again."
Does anyone know what's going on or how I can fix this?
I'm guessing the security is messed up (somehow, don't know how) from removing the corporate account.
But, just for future reference, the only way to remove encryption from an Android device is to factory reset it. It's not as simple as just going into security and removing encryption.
Sent from my Nexus 7 using xda premium
squshy 7 said:
I'm guessing the security is messed up (somehow, don't know how) from removing the corporate account.
But, just for future reference, the only way to remove encryption from an Android device is to factory reset it. It's not as simple as just going into security and removing encryption.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I heard and seen otherwise. I was shown, by someone who has a Nexus 10, that you can remove the encryption as long as you remove the account and removed the device from the OWA site.
Unfortunately, that person is no longer available to me to help.
So basically I'm screwed and all of my information on the device is gone. No one else has any thoughts?
Well, your data is probably lost, but you can easily factory reset it from recovery.
Skullpuck said:
I heard and seen otherwise. I was shown, by someone who has a Nexus 10, that you can remove the encryption as long as you remove the account and removed the device from the OWA site.
Unfortunately, that person is no longer available to me to help.
So basically I'm screwed and all of my information on the device is gone. No one else has any thoughts?
Click to expand...
Click to collapse
I think you can skip the password via adb. http://forum.xda-developers.com/showthread.php?t=1800799
lKBZl said:
I think you can skip the password via adb. http://forum.xda-developers.com/showthread.php?t=1800799
Click to expand...
Click to collapse
Unless I misread, or misunderstood it looks like that'll only work for *pattern* unlock not pin.
Edit: Nevermind, it looks like this post in that thread might have your answer:
http://forum.xda-developers.com/showpost.php?p=30285850&postcount=12
To the OP, if it's a simple pin, a brute force script or program could make short work of it in minutes (or hours at most; depending on length of password).
Skullpuck said:
I heard and seen otherwise. I was shown, by someone who has a Nexus 10, that you can remove the encryption as long as you remove the account and removed the device from the OWA site.
Unfortunately, that person is no longer available to me to help.
So basically I'm screwed and all of my information on the device is gone. No one else has any thoughts?
Click to expand...
Click to collapse
You saw a way to remove certificates for your corporate email account, not remove encryption from your device.
There is only one way to remove device encryption, and that is by factory reset, by design. It wouldn't be very secure otherwise.
Skullpuck said:
I heard and seen otherwise. I was shown, by someone who has a Nexus 10, that you can remove the encryption as long as you remove the account and removed the device from the OWA site.
Unfortunately, that person is no longer available to me to help.
So basically I'm screwed and all of my information on the device is gone. No one else has any thoughts?
Click to expand...
Click to collapse
Sorry, you heard wrong, or you were listening to a fruitcake. By definition you cannot "remove" encryption. It changes the whole file.
Think of it like this. I just scrambled an egg. Then I'm like "oh no! I don't like scrambled eggs! Can someone help me remove the scramble?"
It's not that easy. Sure, there is brute force, if your apps were THAT important it might be worth it to try.
But the short solution: factory reset your data, or give it the pin it wants.
Swiped from my Nexus 10 using xda-developers app
In the future, NEVER use the corporate account system built into iphone / android, this let's your company apply security policies that can wipe your device remotely, and your encryption junk. Use something like Touchdown app which still syncs your contacts, emails, and calendar into your device for any other app to use, but the security policies only get applied to Touchdown. I know this from experience when my former company's IT department "accidentally" wiped everybody's devices messing around in Exchange. "Whoops."
alright guys. Quick question. Has anyone had any of the "secure element" issues on the Nexus 4? I have been looking around and not found anything related to the N4 talking about the secure element. Lots of stuff on the old G-Nex and Nexus S forums though.
To be clear, I am NOT having the error message about secure element come up on the screen. However, after my most recent flash every time I try to use wallet, the paypass terminal says "unable to authorize payment, try another card". Again, there is no "secure element" message, just an error on the paypass terminal.
I tried it on the vending machines at my work and it erred. I then went to CVS just to try it there and it also said the card couldn't be authorized.
I called Google and they said that they see the transactions attempt to go through but show that the card is being declined at point of sale. So, it makes me think that it is not an outage on Google or even a secure element issue. After all, no secure element error code and if it at least attempts to go through, seems to not be secure element.
So, I figured it may be a google wallet outage. Nope. I then figured maybe paypass was down. Nope, it worked with other cards. But every time I try to use the phone it simply rejects the payment. And yes, I know the card my wallet account is linked to is still good...
I flashed a complete factory image back to stock unrooted and it still wont go through.
And I was also sure to always wipe the app before I flashed anything, so I don't think the secure element would have been damaged anyhow, but just seeing if perhaps anyone knows of a secure element issue or some other issue.
Thanks for your time and assistance.
thos25 said:
alright guys. Quick question. Has anyone had any of the "secure element" issues on the Nexus 4? I have been looking around and not found anything related to the N4 talking about the secure element. Lots of stuff on the old G-Nex and Nexus S forums though.
To be clear, I am NOT having the error message about secure element come up on the screen. However, after my most recent flash every time I try to use wallet, the paypass terminal says "unable to authorize payment, try another card". Again, there is no "secure element" message, just an error on the paypass terminal.
I tried it on the vending machines at my work and it erred. I then went to CVS just to try it there and it also said the card couldn't be authorized.
I called Google and they said that they see the transactions attempt to go through but show that the card is being declined at point of sale. So, it makes me think that it is not an outage on Google or even a secure element issue. After all, no secure element error code and if it at least attempts to go through, seems to not be secure element.
So, I figured it may be a google wallet outage. Nope. I then figured maybe paypass was down. Nope, it worked with other cards. But every time I try to use the phone it simply rejects the payment. And yes, I know the card my wallet account is linked to is still good...
I flashed a complete factory image back to stock unrooted and it still wont go through.
And I was also sure to always wipe the app before I flashed anything, so I don't think the secure element would have been damaged anyhow, but just seeing if perhaps anyone knows of a secure element issue or some other issue.
Thanks for your time and assistance.
Click to expand...
Click to collapse
On your phone, go to Wallet > Settings > Reset Google Wallet app, then clear the app data in settings.
Next, on a PC, go to https://wallet.google.com/manage/ and remove all payment cards.
Back on your phone, setup wallet and add the credit cards there.
I had the issue once on my Nexus S and this fixed it for me.
SpookyTunes said:
On your phone, go to Wallet > Settings > Reset Google Wallet app, then clear the app data in settings.
Next, on a PC, go to https://wallet.google.com/manage/ and remove all payment cards.
Back on your phone, setup wallet and add the credit cards there.
I had the issue once on my Nexus S and this fixed it for me.
Click to expand...
Click to collapse
thanks. I'll give it a shot. Hopefully this fixes it. Seemed strange since I wasn't getting an error message but the point of sale is rejecting it. Google said it is showing up on their end as declining for expired card, but I know the cards aren't expired.
We will see. My main concern was simply that this is a Secure Element issue and perhaps the newest version of wallet just doesn't indicate it.
Ill report back soon.
thos25 said:
thanks. I'll give it a shot. Hopefully this fixes it. Seemed strange since I wasn't getting an error message but the point of sale is rejecting it. Google said it is showing up on their end as declining for expired card, but I know the cards aren't expired.
We will see. My main concern was simply that this is a Secure Element issue and perhaps the newest version of wallet just doesn't indicate it.
Ill report back soon.
Click to expand...
Click to collapse
I think the main issue with the secure element was related to the Google prepaid card. It stored the money in the SE, so the idea that you could put $20 on it, back it up, spend the money, restore, and spend it again would have become a cat and mouse security nightmare for Google.
SpookyTunes said:
I think the main issue with the secure element was related to the Google prepaid card. It stored the money in the SE, so the idea that you could put $20 on it, back it up, spend the money, restore, and spend it again would have become a cat and mouse security nightmare for Google.
Click to expand...
Click to collapse
Unfortunately no dice.
I wiped the app. Diabled it. uninstalled all updates. I went all out just to make sure to clear everything. And of course wiped all data from within the app itself prior to clearing data and cache, etc.
Deleted all payment info off of the google account using the link you provided.
Then I enabled the app, reinstalled updates and entered all new payment information. No dice.
So then I added in a card which I have never even had linked to the google wallet account. I figured perhaps just the card itself is somehow jacked up within Google network (expiration date or something). I tried the brand new card which has never been used before and it failed to authorize as well.
Im a bit lost at this point with other things to try. I do have a couple of old nandroids which I can try, but I am not sure if it will resolve the issue as I had already tried another one without success.
Any other ideas guys?
thos25 said:
Unfortunately no dice.
I wiped the app. Diabled it. uninstalled all updates. I went all out just to make sure to clear everything. And of course wiped all data from within the app itself prior to clearing data and cache, etc.
Deleted all payment info off of the google account using the link you provided.
Then I enabled the app, reinstalled updates and entered all new payment information. No dice.
So then I added in a card which I have never even had linked to the google wallet account. I figured perhaps just the card itself is somehow jacked up within Google network (expiration date or something). I tried the brand new card which has never been used before and it failed to authorize as well.
Im a bit lost at this point with other things to try. I do have a couple of old nandroids which I can try, but I am not sure if it will resolve the issue as I had already tried another one without success.
Any other ideas guys?
Click to expand...
Click to collapse
Only flash back to stock 4.2.2 ROM and re-lock the bootloader. Also try skipping the update to Wallet.
I'm actually on stock 4.2.2 now. I tried to flash factory image after it wasn't working on a custom ROM.
Boot loader didn't get locked though. I won't be able to try anything else until Monday though since the only readily available pay pass is on the vending machines at work.
Sent from my Nexus 4 using xda app-developers app
SpookyTunes said:
I think the main issue with the secure element was related to the Google prepaid card. It stored the money in the SE, so the idea that you could put $20 on it, back it up, spend the money, restore, and spend it again would have become a cat and mouse security nightmare for Google.
Click to expand...
Click to collapse
Something like this did occur back when Google was providing Nexus 7 users with I think $10 wallet credit. People would restore their accounts (or maybe just sync a new account, not too sure), and get their credit again, essentially, infinite spending (within that limit)
Okay. So I am back at work with access to a vending machine with an NFC reader…
I have tried several things with no luck. First, I noticed there was a “verify your identity” section under wallet settings.
1) I verified my identity figuring perhaps it needed verification before it would allow any transactions. That didn’t work.
2) I have an NFC payment on 5/24 so I restored my 5/24 nand to try to see if that would restore functionality. It didn’t.
3) I then flashed the 5/25 update to the CM Nightly ROM I used on 5/24. I know I had done this so I figured I would try that. Plus, I have an NFC payment on 5/25 (last time NFC was used) so I figured I would try that. No luck.
I am really confused. I am not getting a secure element error, so I don’t think the chip is locked out. I called my CC company and they see the transaction come through and approve it, but never get a charge on it. Google also says they see the transaction request. This means the phone is sending the information as it should, which also makes me think the chip is NOT locked out. If flashing prior ROMS didn’t work, and flashing a complete factory image doesn’t work, it makes me think it has to be on Googles end somewhere.
I wonder if perhaps the virtual card I was assigned from Bancorp is somehow messed up.
another update. I added a new gmail account to the phone. Basically I created a new gmail just to try something.
I then reset the app, added the new gmail account info to the phone. I then set it up using all of my same payment information. Once the app was set up I tried it out at the vending machine and it worked.
So, since using an entirely new account works. This pretty much confirms that the app itself is not messed up and that there is no issue with the secure element either.
After I confirmed that the app works using a new account, I then reset the app, put in my actual gmail account again, and set up wallet again. This time it didn’t work. At this point I would say it is pretty safe to assume that it is definitely an issue with google wallet on googles end or perhaps on Bancorp Money Networks end.
I've been having this exact same issue with my Nexus 4. Still have not been able to fix it. I just tried setting it up with another account that I don't recall ever really having had Wallet with and that still didn't work. I have not tried to make a completely new gmail account yet. It's very weird, you'd think Google Wallet would just send the same info as my actual credit card does, the blink function in that one works fine.
I am having the same problem on my Gen Nex as well. Very annoying!
I've been able to use it in a few different places without problems now. I haven't gone back to these vending machines at work though so I don't know if Google ever did something after I contacted them. I was so upset when I contacted them because I explain my problem with as many details as possible, I am very clear about how I have a Nexus 4 and how this used to work fine. They reply back to me with some dumb generic message about how in order to use the NFC function in Wallet I have to have a NFC enabled device, which isn't even true because you can't use Google wallet on most phones NFC or not. Honestly it's like they just didn't read my email at all. I emailed them back asking if they even read the email but they never got back to me.
I managed to get two s5's rooted and annoyingly enough, unless I put my sims card in them, neither gmail or the playstore will connect or login via wifi. I only have one sims activated and that is my internet connection which I tether via wifi to my other devices.
Is there a way to work around this? If this is too remedial a question or unwelcome in this thread, I apologize.
I'd like to be able to set up a freshly flashed and rooted phone to accept my gmail account and work with playstore on wifi, sans a sims installed. Do I need to create a gmail account for each and every phone I wish to set up? Will this fix the problem of doing a phone not having a active verizon sims installed? For whatever reason, my playstore access and gmail push are wonky and dubious at best when having the same account being "registered" on multiple devices and I'm not sure if it started recently when gmail for some reason started sending notices to said email account of when another device logged in.
DroidinAndStuff said:
I managed to get two s5's rooted and annoyingly enough, unless I put my sims card in them, neither gmail or the playstore will connect or login via wifi. I only have one sims activated and that is my internet connection which I tether via wifi to my other devices.
Is there a way to work around this? If this is too remedial a question or unwelcome in this thread, I apologize.
I'd like to be able to set up a freshly flashed and rooted phone to accept my gmail account and work with playstore on wifi, sans a sims installed. Do I need to create a gmail account for each and every phone I wish to set up? Will this fix the problem of doing a phone not having a active verizon sims installed? For whatever reason, my playstore access and gmail push are wonky and dubious at best when having the same account being "registered" on multiple devices and I'm not sure if it started recently when gmail for some reason started sending notices to said email account of when another device logged in.
Click to expand...
Click to collapse
I too manage two S5's, rooted and I have no problems. The one without a Sim works great off of WiFi. Playstore works fine logged into the same account.
Tulsadiver said:
I too manage two S5's, rooted and I have no problems. The one without a Sim works great off of WiFi. Playstore works fine logged into the same account.
Click to expand...
Click to collapse
That's perversely encouraging and assures me I haven't lost my mind expecting something impossible that I thought I knew to be true. Neither of my S5's, my N4 or Z2 will reliably hook up with gmail and the play store both. This one S5 will not allow me set up a new gmail account on the device and gmail has stopped pushing to my DD S4. Remove account, clear cache, date force stop all google processes, reboot and same. Lots posted about it and I know google hasn't banned me as it is working on some devices. Besides, I behave.
Now if I can get supersu to install from an APK with a wifi connection, I can at least proceed.
Congrats on yours and thanks for confirming it should work.
Well I popped the sims card in the one, which had been flashed back to ngc from oa8 (my other one hadn't ever tried to OTA update from nk2) and playstore and gmail cooperated fine. However, SDM started downloading an update, which I'll assume is OTA to OA8 or OC4. The first time before I pulled the battery I got playstore hooked up and forced SDM to stop. Pulled the battery and SDM continued where it left off and I managed supersu and busybox. Deferred the install of the update and wonder how critical it is that the downloaded file be removed prior to safestrapping it and then OC4 rooting it with the tether addon.
The other S5 on nk2 hasn't tried to OTA update so it must be down on the list despite being readily activate-able with clean IMEI and no issues.
I wish I could figure out why google services such as gmail and playstore are being contumacious on my devices.
I had that same problem of an update trying to get on my phone before I could get it rooted ( an s4) and it messed my phone up bad. I had to finally take the update to get it working again
I would put all the files, towelroot, busybox, SuperSU, safestrap, and titanium backup on my ext SD card. Flash back to stock NGC. Don't use your Sim or log onto WiFi. Root your phone and freeze SDM.
Tulsadiver said:
I had that same problem of an update trying to get on my phone before I could get it rooted ( an s4) and it messed my phone up bad. I had to finally take the update to get it working again
I would put all the files, towelroot, busybox, SuperSU, safestrap, and titanium backup on my ext SD card. Flash back to stock NGC. Don't use your Sim or log onto WiFi. Root your phone and freeze SDM.
Click to expand...
Click to collapse
It never attempted the OTA until the active sim card was in place. I used it on wifi many times including several times today and had even worked fine with the playstore/gmail on wifi up until recently when gmail stopped pushing to my dd period, and every other device in which my DD's sims card wasn't inserted.
The OTA update file has been downloaded, but not installed. I deferred it to 5 am and didn't check automatic. I am assuming I can defer it again although I'd somehow feel better removing it and freezing SDM until I decide if I am going to OC4 it or do a custom rom. Nice would be native call recording, native tethering and being able to overclock it a bit. A lightweight lollipop and xposed would probably do the trick other than maybe overclocking. Too much reading for one day.
It is currently on NCG, rooted, supersu, busy box, and safestrap all installed. I think I'll install a root file explorer try to find it and also do Titanium Backup while I'm at it. I wish I knew where it was and if removing it was as simple as just deleting a file.
Any ideas? I have two in the same state and think I'm going to make one of them my DD since getting root on a verizon N4 doesn't look likely anytime soon. The N4 is kinda big anyhow. I have to have tethering and would like it easier than foxfi since I feel obligated to use as much of my unlimited data as possible. I think I read the native call recording can be enable from the dialer at the cost of the "add call" which I don't use or even know what it is.
DroidinAndStuff said:
It never attempted the OTA until the active sim card was in place. I used it on wifi many times including several times today and had even worked fine with the playstore/gmail on wifi.
The OTA update file has been downloaded, but not installed. I deferred it to 5 am and didn't check automatic. I am assuming I can defer it again although I'd somehow feel better removing it and freezing SDM until I decide if I am going to OC4 it or do a custom rom. Nice would be native call recording, native tethering and being able to overclock it a bit. A lightweight lollipop and xposed would probably do the trick other than maybe overclocking. Too much reading for one day.
It is currently on NCG, rooted, supersu, busy box, and safestrap all installed. I think I'll install a root file explorer try to find it and also do Titanium Backup while I'm at it. I wish I knew where it was and if removing it was as simple as just deleting a file.
Any ideas? I have two in the same state and think I'm going to make one of them my DD since getting root on a verizon N4 doesn't look likely anytime soon. The N4 is kinda big anyhow. I have to have tethering and would like it easier than foxfi since I feel obligated to use as much of my unlimited data as possible. I think I read the native call recording can be enable from the dialer at the cost of the "add call" which I don't use or even know what it is.
Click to expand...
Click to collapse
Try your root/cache folder to find your update.
Tulsadiver said:
Try your root/cache folder to find your update.
Click to expand...
Click to collapse
Getting on that this morning. I wish I could figure out why it keeps downloading and installing playstore on wifi and still won't work until I put my sims in it. I've gone through everything short of uninstalling all of google services and reinstalling them on several devices. My wifi only z2 tab acting stupid with google would be a vexation if I let things like that bother me.
Thanks and I'm popping the sims in it and going to try cleaning it up and locking down SDM.
___________________________________________________________________________________________________________________
Installed the root browser and the update zip was in cache.
Deleted.
Went to system with the display icon.
App then deleted the SDM apk and the SDM odex file.
Hopefully that will keep it from pulling that stunt again until I decide what to do with it.
Guess I should do it with the other one and figure out why that same sims won't make gmail push to my DD or the play station work in it or why my non-pc wifi only devices won't work except through their browsers. I think there must be some conflict with which devices the playstore is recognizing as being associated with my accounts.
Must be something in my google settings and what a conglomerated octopus google services has turned into.
Thanks again. Feel free to tell me if my down and dirty bandaid overlooked anything!
Good luck to you!
The only thing weird about my google account and gmail is that the email address I login with is not the one that shows up under "accounts" and the login email address is not a gmail address. Somehow the two different email accounts are linked together.
Tulsadiver said:
Good luck to you!
The only thing weird about my google account and gmail is that the email address I login with is not the one that shows up under "accounts" and the login email address is not a gmail address. Somehow the two different email accounts are linked together.
Click to expand...
Click to collapse
Yeah, I wish I know what Google was up to exactly. Acknowledging the 'this device logged into your account' and verifying that it's me, seems like should seamlessly eliminate issues. That doesn't appear to be the case and I think my problems started when I somehow agreed for them to send me such notices relative to the gmail account I use on my other devices, not both gmail accounts associated with my DD.
On my DD, I have two gmail accounts that I've had for ages. They have always worked fine on my android devices. Recently that changed and I'm not sure why but I know when. On my other many devices, I've just registered one of my gmail accounts to them, the same one each time, and they too all seemed to quit working at the same time, initially offering no problems to working on wifi.
However, I am curious as to your thoughts on Ricks Rom as I looked over the specs and it seems to be about what I'm looking for although for some unqualified reason, my mind has been thinking I wanted a rom based on lollipop. It says it has native or hacked hotspot and native call recording. Can it be overclocked? I don't use Facebook, Twitter or any of the gimmicky apps that come preinstalled on the phones and find most all of them, especially the Samsung redundant ones, to be annoying and intrusive.
Do you know for sure if Xposed will or will not work with it?
How many security certificates come system installed on Ricks Rom? My guess is that something like 200 come stock and I don't like the looks of many of them and wish I knew how come and why.
Thank you, I appreciate your sharing information. It is nice to gather up pieces to puzzles and hopefully being able to solve them. I'll get this gmail playstore thing fixed if it means I have to go fishing long enough to forget about it! Maybe somebody else finding themselves in a similar situation may find some of our particular details useful to fixing these oddities.
I'm running RicksRom (v19 right now) on my DD and have been using it since I first got my phone a year and a half ago. I don't have Xposed but don't know why it wouldn't work. This is a pretty lean ROM but it does have quite a few security certificates. I'm running MOAR on my spare phone that is currently on lollipop. I have this phone as a spare to play with but wouldn't run lollipop. Too quirky and I like the theming capabilities of KitKat better.
Tulsadiver said:
I'm running RicksRom (v19 right now) on my DD and have been using it since I first got my phone a year and a half ago. I don't have Xposed but don't know why it wouldn't work. This is a pretty lean ROM but it does have quite a few security certificates. I'm running MOAR on my spare phone that is currently on lollipop. I have this phone as a spare to play with but wouldn't run lollipop. Too quirky and I like the theming capabilities of KitKat better.
Click to expand...
Click to collapse
Thanks, lean sounds fine and overclocking a bit would be even nicer! I'll dig through that thread a bit more and see if anyone has verified Xposed to work with it conflict free and if it can be clocked.
I went through my gmail account settings on my PC and under Recent Activity/Notifications and Alerts... there is no way to uncheck any alerts that have been checked. I am pretty sure my issues started when I recently checked "Email" for Suspicious Attempt to Access Account. The password change email notice has been checked since forever.
Going to the Playstore on my PC, it lists all of my devices, past and present although it has dropped some that haven't accessed for a while, and now makes me think I need to give them all nicknames since I have multiples of the same Model Number devices. However, it lists all current and recent as well reconciles. What it won't do from my PC browser, is anything but sit there doing nothing when I hit install for a selected app. It will not give a pop down menu to select which device and the playstore account settings are very minimal. I will see if nicknaming them helps since there are multiple devices with the same model number. This type of online PC install used to work fine and would prompt with a pop down menu to select which device, regardless if they were online via the sims or wifi, and then download and install if the selected device was online. I don't recall ever doing that when I had multiple devices having access with the same model number.
Another interesting thing is that Verizon must have access to the playstore and/or gmail device list. I know this from speaking with a very helpful tech rep this week about my data connection speed on my DD. She verified seeing devices on this account even if they hadn't ever had my sims card installed. Merely been online with my one email account registered and playstore accessed from it. That kinda surprised me. I wonder if there is some Google Services/Verizon conflict that may be causing this.
Hello - I'm working with google on this but they haven't been able to figure it out. Maybe someone here can. Unrooted 6P, but I don't think the phone is the issue.
I tried adding a card (MasterCard)to android pay, but my bank wouldn't allow it because of a security hold. Now, when I try to add a new credit or debit card, the MasterCard shows in the add card menu under the heading "You added this one to your Google Account already, so you'll just need to confirm some details." This card does NOT show on the google payments page. The google tech doesn't see it on his end. He does see pre-auths from me trying to add it. He wants me to master reset the phone, but when I load AndroidPay on another device - it shows the same thing for the MasterCard. I've cleared all data for the app on the 6P, but since it's showing in AndroidPay on my other device, I'm thinking it must be floating in google's servers.