So I called up Google about the problem I started recently having with Google wallet. I get the error message that the secure element stopped responding. Upon searching online the issue seems to still not to be resolved even with other officially supported devices. Google transferred me to Samsung rep who seemed to have never heard of the issue or received any guidance from her employer on steps to take towards a resolution. Her only idea seems to be for me to mail them my phone on the off chance that they might be able to fix it.
Has anyone else had this issue come up and either get it fixed or any other result?
I really wanted to try out Google wallet, but after this happened I am going to stay away unless they figure out how to fix it without replacement of my perfectly working brand new phone. The thought of being sent a refurbished phone as a replacement sickens me.
Sent from my Galaxy Nexus using Tapatalk 2
I'm really curious about this too. Used Google Wallet today and it's pretty cool. Then I lost my dialer while trying to add inverted gapps to Apex. I'd normally just flash another rom but I don't want to mess up that secure element. :-/
I'm guessing you did a factory reset.
Read this. http://www.droid-life.com/2012/05/2...let-forever-learn-how-to-safeguard-your-info/
Sent from my Galaxy Nexus using Tapatalk 2
You killed it! You murderer!
Seriously, it's dead Jim.
It self destructs if it thinks you are trying to tamper with it; a countermeasure to keep somebody from stealing your account info. Only solution is to RMA the phone under warranty.
Rma?
Through Samsung, Verizon or an insurance claim? I had a 1 chat session with Samsung (Complete waste of time)
It's dead, only way to fix it is to get a different replacement phone.
Glad I still have a backup of stock rooted thank you qbking tutorials.
Sent from my Galaxy Nexus using xda premium
Although I never saw a secure element error, my wallet was stuck at "initializing" forever. It happened after I wiped data to go to a newer build of AOKP. I hadn't heard about doing the reset from within the wallet app to prevent it. I've updated ROM's and flashed many times, as well as many factory resets since, and it still occurs.
Today I updated to the latest market release of wallet. It now walks me thru activation, but hangs at "Activating account" forever now instead. I'm sure they're all the same issue.
Now, I have some thoughts on this. Recently Titanium Backup added a new feature. After doing a "wipe data / factory reset" in CWM, you now get prompted when you open TiBackup, that the device ID has changed, and it asks if you want to restore back to a backed up one. If you choose yes, it immediately applies it and reboots. Now, since they just added this feature, I only have a recent one backed up. But I wonder if this isn't the whole problem? TiBackup says it's how apps recognize that they're installed on your specific device and it can break licenses etc.
I wonder if I had the device ID from when I first installed Wallet, if that's all i would need to fix this?
Thoughts?
I called Google and Samsung the result is that I have to send in my phone for repair, not a replacement.
Sent from my HTC One X using Tapatalk 2
aturyan said:
I called Google and Samsung the result is that I have to send in my phone for repair, not a replacement.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
And it hardly seems worth it for something silly like Google wallet. I'll just not even bother with it. The nfc still works and that's the important part.
Sent from my Galaxy Nexus using Tapatalk 2
Related
So I am an idiot.
I flashed the zip for google wallet on thursday and had everything working. Loaded money onto it, used it 3 times. everything was good.
Decided to try and erase data and use a different email address.
After I did that I got secure element is not responding.
I tried to recover a backup with no google wallet ever on it and i get the same thing.
i tried to load just the .apk and same thing.
does anyone know how to get it working again after this error message? i have tried a factory reset...
No one knows?
Sent from my Galaxy Nexus using XDA App
i remember reading a thread about this yesterday i think you have to reflash the APK. good luck
blacktimusprime said:
i remember reading a thread about this yesterday i think you have to reflash the APK. good luck
Click to expand...
Click to collapse
What do you mean reflash?
I restored prior back up and tried to use the .apk and reflashed the zip. Same thing.
Sent from my Galaxy Nexus using XDA App
ran into this same problem, can not seem to get wallet to work and i am worried that if it ever dose get released for verzion gnex that it wont work. Really hope someone is able to figure out what is causing it or how to fix it.
I'm still looking for a fix. Will let you know if I find one.. do the same if you find a fix
Sent from my Galaxy Nexus using XDA App
Will do, saw in the wallet .apk thread that if that happens and you don't have a nandroid back up of before wallet was on there then the best you can do is get a new device because the element has locked the phone out. Seems like it would be a silly feature to lock the phone out forever rendering it useless forever but who knows. Maybe someone smarter then me can figure out a solution if not i'm sure i can make up a good reason to exchange mine before the 14 days are up.
noev.. went and exchanged for new nexus today.
I unlocked boot loader. Rooted. Made a backup before installing google wallet this time.
Loaded the .apk and installed. Worked fine.. clicked on pre paid card. Took forever to get card info..
And there's $10 on it again. Weird because I only had some change on before. I have loaded money on it and made 3 purchases. Their still in transaction history but I'm at $10 again.
Gonna go try it out again.
Sent from my Galaxy Nexus using XDA App
civicsisedan said:
noev.. went and exchanged for new nexus today.
I unlocked boot loader. Rooted. Made a backup before installing google wallet this time.
Loaded the .apk and installed. Worked fine.. clicked on pre paid card. Took forever to get card info..
And there's $10 on it again. Weird because I only had some change on before. I have loaded money on it and made 3 purchases. Their still in transaction history but I'm at $10 again.
Gonna go try it out again.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
unlimited money glitch!!!! profit! lol
predation said:
unlimited money glitch!!!! profit! lol
Click to expand...
Click to collapse
yeah im glad i didnt have more than $10 on it and have it reset to $10..
that would suck...
Hello
I recently got my Galaxy Nexus and I am trying to use Google Wallet but running into a problem I haven't seen yet (A search revealed 1 other person with the problem but was able to resolve by wiping data from the app. This didn't work for me.)
I am running 4.0.4 AKOP build 29. I am unlocked and rooted. Wallet version 1.1-R52v7.
The app installs just fine. I have it linked to my google account. However, I cannot add a Google Prepaid card. It attempts to add for ~ 1min, then says, "Error adding card. Try again later."
I tried uninstalling / reinstalling. I tried the previous version. I also tried wiping the data from the app itself. Nothing has worked so far
Can someone point me in the right direction?
Thanks in advance.
Anyone? I'm very anxious to use GWallet!
You need to use a US credit card. View the adding funds thread for instructions that usually work.
Google wallet won't work if your rooted. Very disappointing.
Sent from my Galaxy Nexus using xda premium
Big-A-Rob said:
Google wallet won't work if your rooted. Very disappointing.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Any Proof? I have seen many reports of Rooted Users having it work just fine?
Big-A-Rob said:
Google wallet won't work if your rooted. Very disappointing.
Click to expand...
Click to collapse
Rubbish ... It works fine.. You just get a banner warning that it's on an "unsupported device".
RobbieCrash said:
You need to use a US credit card. View the adding funds thread for instructions that usually work.
Click to expand...
Click to collapse
I am located in the US. I also don't have the option to add funds because it will not allow me to add a prepaid card.
vk2bea said:
Rubbish ... It works fine.. You just get a banner warning that it's on an "unsupported device".
Click to expand...
Click to collapse
I have this banner. I simply used superSU to get rid of it, so the phone it thinks it does not have root. However, with/without superSU it still does not allow me to add a prepaid card
Can anyone else shed some light on this?
Anyone? I'm so close I can feel it!
Mine does the same. Idk wtf is going on. It worked before on my other nexus.
Sent from my Galaxy Nexus using XDA
So I called Google, they connected me to the money network. Guy took a quick look. It is something on their end nothing to do with my phone. He can see my IMEI trying to activate but erroring out.Was escalated to T2 tech support and I am waiting on a phone call back.
They called me back. Had me reset the app. Still nothing worked. This has been escalated now to T3 tech support. I was told I would get a call back tomorrow :-/
Does anyone have any ideas on how to fix this issue?
impass3093 said:
They called me back. Had me reset the app. Still nothing worked. This has been escalated now to T3 tech support. I was told I would get a call back tomorrow :-/
Does anyone have any ideas on how to fix this issue?
Click to expand...
Click to collapse
Did u reset the app before you wiped data sounds like you didn't and have been locked out. If so you will need a new phone
Sent from my GNex {GSM} T-Mobile
Just out of curiosity, has your IMEI number maybe reverted to Samsung's default number?
Reason I ask is because that happened to me while using my Nexus S and I had the same issue you're having.
Sent from my Galaxy Nexus using xda premium
I'm also experiencing this issue. So frustrating! I used to have Wallet on my phone...but I tried to reset it to get the extra $5 and haven't been able to get it back up and running since. That's what I get for being greedy!
If anyone has any ideas...it would be greatly appreciated. I've done almost everything: reset app, clear cache, uninstalled, installed older versions....cant get it for the life of me!
brmayhem said:
Just out of curiosity, has your IMEI number maybe reverted to Samsung's default number?
Reason I ask is because that happened to me while using my Nexus S and I had the same issue you're having.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
What do you mean Samsung's default number? I have came to the general conclusion that it something to do with the Money Network. They are blocking my phone, my IMEI, from connecting. I was able to login with my Google account on another phone just perfectly and get my prepaid card.
spaceman860 said:
Did u reset the app before you wiped data sounds like you didn't and have been locked out. If so you will need a new phone
Sent from my GNex {GSM} T-Mobile
Click to expand...
Click to collapse
I can open the app just find. It initializes, lets me sign in, make my PIN code, just not add a prepaid card. And I have wiped the data from in the app multiple times trying to get it to work
mattyb65 said:
I'm also experiencing this issue. So frustrating! I used to have Wallet on my phone...but I tried to reset it to get the extra $5 and haven't been able to get it back up and running since. That's what I get for being greedy!
If anyone has any ideas...it would be greatly appreciated. I've done almost everything: reset app, clear cache, uninstalled, installed older versions....cant get it for the life of me!
Click to expand...
Click to collapse
Me too, I want this working so bad! Hopefully T3 tech support can help me out. I feel like all that they need to do is reset/unblock/do something, with my IMEI number on their end.
Does anyone else have any ideas?
24hr bump
impass3093 said:
What do you mean Samsung's default number? I have came to the general conclusion that it something to do with the Money Network. They are blocking my phone, my IMEI, from connecting. I was able to login with my Google account on another phone just perfectly and get my prepaid card.
Click to expand...
Click to collapse
A while back I flashed a ROM to my Nexus S that corrupted my nv_data.bin file which in turn changed my original IMEI to Samsung's generic's. (004999010640000)
After that happened I was unable to re-use Wallet because Money Network's service will not allow that IMEI to work in their system, for obvious reasons.
Check the IMEI on your phone's back cover or box and compare it to the one in your Android's system. Hopefully they match. There's no solutions for the Nexus S currently. You'd have to send it back to Samsung. Good luck.
This happened to me even after Google fixed the provisioning of the Prepaid Card. I just kept Removing and Adding the Card. Eventually, after a couple of days it fixed itself. Try Resetting the App, Deleting Data, uninstalling, and then re-installing.
Money network finally got it working for me. I believe they did a master reset. It now works
Sent from my Galaxy Nexus
How do I contact Money Market? I am having the same exact issue.
The FIRST thing I did when I got my new gnex was put AOKP MS6 on it.
I want to try out Google Wallet, but I don't want to attempt to set it up and get an insecure element error and be screwed for life.
Do I need to go 100% takju stock and relock the bootloader and then set it up and then restore AOKP and then set it up again?
Can I do it over AOKP somehow?
Not sure how this secure element root thing works, any ideas on this?
You can install Wallet on AOKP right now from the Play Store and be good to go, I've been doing that since I've had my phone and it works just fine. From what I understand the security element only fails when you don't reset Google Wallet from within the app itself and try restoring the app (like with Titanium Backup) to another ROM. Just don't freak out when Wallet says 'unsupported device' when you use it, it's normal for a rooted phone.
Sent from my Galaxy Nexus using Tapatalk 2
So I download the app, open it, hit "reset" and set it up on my current ROM as-is?
orangekid said:
So I download the app, open it, hit "reset" and set it up on my current ROM as-is?
Click to expand...
Click to collapse
You can install it just fine as is. Only do the in app reset if you plan on moving from one custom ROM to another.
C0dy said:
You can install it just fine as is. Only do the in app reset if you plan on moving from one custom ROM to another.
Click to expand...
Click to collapse
ok I will try it out.
Orange kid you got another nexus? You're old one is still a beast
Jellin' like a felon
kevinjgray88 said:
Orange kid you got another nexus? You're old one is still a beast
Jellin' like a felon
Click to expand...
Click to collapse
lol, yeah I am back on the Gnex. My girl is still using the white Note you sent
But I got that flashing bug and really wanted a device I could truly tailor as my own, including my custom soft buttons and all the things I love about this phone, so I got back on the gnex.
I used an SGS3 but honestly I didn't find it any better than the galaxy nexus, I think the hype is starting to wear off on those phones.
Good to see you're still rocking the one I sent you, this really is the best phone on the market IMO til maybe the next nexus device.
and for this topic, I installed Wallet and set it up as C0dy suggested and added my credit card and it seems to work fine, just need to try it out now
In a somewhat similar situation. I have a rooted phone that I was running Wallet on, decided to try a new ROM and forgot to reset Wallet before doing my factory reset. If I am reading the responses correctly I should be fine re-getting the app from the Play store and using it again as long as I'm not trying to re-use data from my previous flash, right?
Orange kid did you ever use Google wallet on this nexus because I have got the unsecure element from the get go?
Jellin' like a felon
kevinjgray88 said:
Orange kid did you ever use Google wallet on this nexus because I have got the unsecure element from the get go?
Jellin' like a felon
Click to expand...
Click to collapse
I never did, didn't even think about it. That's weird. There's gotta be a way to fix it like contacting Google or restoring a nandroid
Sent from my Galaxy Nexus using xda app-developers app
Yeah it's not a big deal just wanted to check it out. But even the very first time I downloaded it I got the secure element thing. Error code E1000 I think
Jellin' like a felon
I'm not sure what the verdict on the cause for the secure element error was (read: not how to prevent it), but since I've rooted my phone I've always restored my deviceID from within Titanium Backup when I flash a new rom. I've probably done around 15 clean flashes and even more dirty flashes, and after restoring my deviceID every time, I've yet to run into the Secure Element error.
Just my 2 cents worth.
kevinjgray88 said:
Yeah it's not a big deal just wanted to check it out. But even the very first time I downloaded it I got the secure element thing. Error code E1000 I think
Jellin' like a felon
Click to expand...
Click to collapse
Well I got the phone from an XDAer so it may have been something that was installed on it from before like that. Must be something internal in the phone that gets tripped, I'm not actually 100% sure what that insecure element thing even means.
orangekid said:
Well I got the phone from an XDAer so it may have been something that was installed on it from before like that. Must be something internal in the phone that gets tripped, I'm not actually 100% sure what that insecure element thing even means.
Click to expand...
Click to collapse
Thanks, who was it? He ruined my life, I have nothing to live for now. :banghead:
For real tho its not a big deal, just from time to time I re download it in hopes of it working, but honestly if I do get it to work I probably would never use it lol.
Jellin' like a felon
Lol I haven't used it once, I get the feeling it won't work and everyone will laugh at me.
Sent from my Galaxy Nexus using xda app-developers app
Secure element issues
I have been experiencing secure element issues. I just sent my LTE Nexus to Samsung and they would not fix it. The NFC chip can't be fixed, the entire board would have to be replaced, which they are unwilling to do. Samsung is blaming Google. Tech pointed out that Wallet writes to secure element, so Google needs to create code to restore NFC to default state. I'm complaining to Google about this, because it is looking like the issue will crop up when ISIS payment system rolls out, so issue goes beyond Wallet.
Tomorrow I am receiving a CLNR from Verizon, which scares me. I see too many posts about people returning their phones 4+ times before they get a good one. May stick with my no NFC having GNex instead of switching.
i don't have the Secure Element error, but instead the Unsupported Device error.
i used to have Google Wallet working on the Vicious ROM. but then i was in the process of selling the Galaxy Nexus, so i clean wiped it and flashed a new ROM.
i didn't realize until after i did that, i should have reset my Google Wallet settings. so now i'm trying to install it again to reset it, but it's not letting me run it. is it safe to say that it's reset and that i'll be able to use Google Wallet on my Galaxy S3 (once i root it)?
Well, since we haven't seen a full restore available for MA7 I'm going to do what I did with MA5 and make one clicks for all but the modem.
If the situation changes I'll repost with new one clicks.
[ROM][ODIN][TAR]SPH-L900 MA7 (MA7 Modem/Kernel/ROM - Stock) - SXTP Developers
NOTE: THIS THREAD WILL NOT BE MAINTAINED ANY FURTHER BY OP AS IT HAS A MORE CURRENT VERSION AVAILABLE.
PLEASE CONTACT IF THERE ARE ANY ISSUES. THANK YOU.
Cool nice to see you on the job...
Sent from my SPH-L900 using Tapatalk 2
Faaaaaannnn-tastic.
Awesome!
Sent from my SPH-L900 using Tapatalk 2
Please mention this in your instructions, it's very, very important for Google Wallet users:
Before wiping your current ROM, you MUST reset your Google Wallet app by going into Settings --> Reset Google Wallet in the Wallet app, or you will permanently lock out your secure element and will never be able to use Google Wallet again - you will have to get a new phone!
This is because your Google Wallet app is married to the secure element with a unique crypto key when you first set up Google Wallet on your phone and if you wipe your phone without first resetting Google Wallet, that key will be lost forever, rendering the secure element useless.
Performing a Google Wallet reset will unmarry the app from the secure element and reset it to its original state so that it can accept a new Google Wallet installation when you wipe your phone and then restore it to stock.
siraltus said:
Please mention this in your instructions, it's very, very important for Google Wallet users:
Before wiping your current ROM, you MUST reset your Google Wallet app by going into Settings --> Reset Google Wallet in the Wallet app, or you will permanently lock out your secure element and will never be able to use Google Wallet again - you will have to get a new phone!
This is because your Google Wallet app is married to the secure element with a unique crypto key when you first set up Google Wallet on your phone and if you wipe your phone without first resetting Google Wallet, that key will be lost forever, rendering the secure element useless.
Performing a Google Wallet reset will unmarry the app from the secure element and reset it to its original state so that it can accept a new Google Wallet installation when you wipe your phone and then restore it to stock.
Click to expand...
Click to collapse
Added here. Thanks for the heads up.
garwynn said:
Added here. Thanks for the heads up.
Click to expand...
Click to collapse
No worries. I had to get another Note 2 when this happened to me... thankfully had phone insurance.
That truly happens on the Note2? I remember others saying it happens on other phones but I could never brick my secure element as I tried about a hundred times it seemed. Chalked up as one of those rumors.
Sent from my little Note2
digiblur said:
That truly happens on the Note2? I remember others saying it happens on other phones but I could never brick my secure element as I tried about a hundred times it seemed. Chalked up as one of those rumors.
Sent from my little Note2
Click to expand...
Click to collapse
It doesn't matter what phone you use, that's just how Google Wallet and the secure element work together. Google "Secure element has stopped responding" and you'll see how many people have bricked their secure element because they didn't know this.
This only happens in a very specific situation - when you go to a different ROM or do a factory reset without resetting Wallet first, in which case the secure element remains forever married to a Wallet installation that's lost.
If y
siraltus said:
It doesn't matter what phone you use, that's just how Google Wallet and the secure element work together. Google "Secure element has stopped responding" and you'll see how many people have bricked their secure element because they didn't know this.
Click to expand...
Click to collapse
I remember when google wallet 1st came out it store info to the secure element and MANY Evo LTE users bricked the element when the Evo 1st came out then google pulled the wallet apk for afew weeks and switched where the info is now stored to avoid this issue...ive flashed away plenty on my evo lte and this now without reseting wallet......its an urban myth now.
Edit: Heres thelink its stored on the cloud and not the secure element
http://googlecommerce.blogspot.com/2012/08/use-any-credit-or-debit-card-with.html
Sent from my SPH-L900 using Tapatalk 2
siraltus said:
It doesn't matter what phone you use, that's just how Google Wallet and the secure element work together. Google "Secure element has stopped responding" and you'll see how many people have bricked their secure element because they didn't know this.
This only happens in a very specific situation - when you go to a different ROM or do a factory reset without resetting Wallet first, in which case the secure element remains forever married to a Wallet installation that's lost.
If y
Click to expand...
Click to collapse
Except that's not true because many people have done both of those many times and it still worked fine. I have myself.
And, people have lost their secure element when they did reset wallet, and people have lost it even when they hadn't flashed anything or even so much as rebooted. Just worked one day and not the next.
So we don't know what kills them yet.
Sent from my SPH-L900 using xda premium
Rite on! Thanks for this Garwynn! Much appreciated man.
siraltus said:
It doesn't matter what phone you use, that's just how Google Wallet and the secure element work together. Google "Secure element has stopped responding" and you'll see how many people have bricked their secure element because they didn't know this.
This only happens in a very specific situation - when you go to a different ROM or do a factory reset without resetting Wallet first, in which case the secure element remains forever married to a Wallet installation that's lost.
If y
Click to expand...
Click to collapse
I've never had a single issue on either my gs3 or my gn2 flashing or upgrading firmware and being able to use google wallet. Even with the gn2 and Wallet not being "officially" supported. I have a hard time believing any of this is true...it certainly hasn't been in my case. I'll toss my Nexus 7 in there as well. Flashed plenty roms and upgraded firmware...no issues whatsoever.
superuser is denying all requests...flashed the rooted restore
jutaejrtouch said:
superuser is denying all requests...flashed the rooted restore
Click to expand...
Click to collapse
nevermind one clicked back to stock and rooted via toolbox with supersu...all working fine
I just flashed the MA7 FULL STOCK RESTORE one click. The build updated but the kernel and baseband were still LJC. Did I do something wrong?
KEYofR said:
Except that's not true because many people have done both of those many times and it still worked fine. I have myself.
And, people have lost their secure element when they did reset wallet, and people have lost it even when they hadn't flashed anything or even so much as rebooted. Just worked one day and not the next.
So we don't know what kills them yet.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Except that read this thread: http://forum.xda-developers.com/showthread.php?t=1721222
I destroyed my secure element on my GN2 just two days ago and NOTHING was able to make Wallet work again. I went from the NoWiz ROM to stock rooted MA7 and wiped the entire phone (including /data and /.android.secure) in the process, installed Wallet, it threw the "secure element has stopped responding" error and NOTHING could make it work again because I didn't back up my previous ROM. I had to get my phone replaced under carrier insurance.
What's wrong with including the modem? I just got this phone like 3 days ago so im just wondering why no modem?
Sent from my SCH-I535 using xda premium
siraltus said:
Except that read this thread: http://forum.xda-developers.com/showthread.php?t=1721222
I destroyed my secure element on my GN2 just two days ago and NOTHING was able to make Wallet work again. I went from the NoWiz ROM to stock rooted MA7 and wiped the entire phone (including /data and /.android.secure) in the process, installed Wallet, it threw the "secure element has stopped responding" error and NOTHING could make it work again because I didn't back up my previous ROM. I had to get my phone replaced under carrier insurance.
Click to expand...
Click to collapse
So what? All that web article does is parrot stuff people have been guessing at here. It's not sourced from Google.
The fact that your SE bricked doesn't prove anything except that sometimes they brick. No one disputes that.
Sent from my SPH-L900 using xda premium
Err quick question
Do i need to reset all back to stock ljc to flash the tar in odin or can i just flash (Modem and firmware) over ma5?
Wrong kernel in OCs... that's what I get for doing in early am. Will fix tomorrow.
Modem cannot be included because dump is too big to flash via Odin.
Sent from my SPH-L900 using Tapatalk 2
Here it is in a nutshell: Error 927 on ANY download, any app, any game, be it paid or free, on my Nexus 7 (2013) FHD. I've done the following:
- Cleared the data and cache for the Google Play Store, Download Manager, and Google Services Framework.
- Uninstalled updates for the Google Play Store and Google Services Framework.
- Deleted and re-added my Google account.
- Rebooted.
- Hard reset.
- Downgraded to 4.3 and re-upgraded to 4.4.2.
- Tried to download the apps and games from the Google Play website, and get "An unexpected error has occured. Please try again later."
- Changed the filter and proxy settings on my Cisco router.
- Switched to LTE, and... same thing.
- Created another Google account, and it worked, but I will NOT be forced to re-purchase the apps I've spent nearly $80.00 on over the years, or upload my music collection to Google Music again.
- Reached out to Google for help, and... crickets.
I'm at the end of my rope. If this isn't resolved soon, I'm returning the Nexus to Wal-Mart. I've NEVER had this sort of issue before, even with my first-generation Nexus 7. I've had Android tablets since my Motorola Xoom awhile back. I've ALWAYS had Android tablets. I'd hate to have to abandon Android because of this idiocy, but I may have to do so. I don't want to have to go with Apple for both my smartphone and tablet, but it's starting to look that way.
If anyone has any suggestions that aren't listed above, please, help me out. I love my Nexus 7, but without apps and games, it's pretty worthless.
Thanks in advance.
Normally deleting and adding back the Google account is a solution for Play Store problems, but as you said, you tried that. Some have reported that error 927 is because of a network connection error. How is web browsing? YouTube?
abarax said:
- Downgraded to 4.3 and re-upgraded to 4.4.2.
Click to expand...
Click to collapse
How did you do that? Did you download the 4.3 ROM to flash it? Did you unlock and flash a custom recovery?
When all else fails, flash the stock ROM, especially with your downgrading and upgrading. Google's files include a "flash-all.bat" within that will wipe everything and flash the stock ROM and recovery.
https://developers.google.com/android/nexus/images#razor
Pandae said:
Normally deleting and adding back the Google account is a solution for Play Store problems, but as you said, you tried that. Some have reported that error 927 is because of a network connection error. How is web browsing? YouTube?
All web browsing and pre-installed apps work just fine. Just any attempts to update those apps, or install any other apps from Google Play, fail with error 927.
How did you do that? Did you download the 4.3 ROM to flash it? Did you unlock and flash a custom recovery?
When all else fails, flash the stock ROM, especially with your downgrading and upgrading. Google's files include a "flash-all.bat" within that will wipe everything and flash the stock ROM and recovery.
https://developers.google.com/android/nexus/images#razor
Click to expand...
Click to collapse
I actually have flashed the stock ROMs, from the original 4.3 to 4.4.2, with the exact same results. I've also made certain not to unlock the bootloader and to not root as to recreate the OOB experience as well. At this point, my options are exhausted.
abarax said:
I actually have flashed the stock ROMs, from the original 4.3 to 4.4.2, with the exact same results. I've also made certain not to unlock the bootloader and to not root as to recreate the OOB experience as well. At this point, my options are exhausted.
Click to expand...
Click to collapse
Are you able to install apps on another device with the same account? If not it may be a problem with your account...
Dexxon said:
Are you able to install apps on another device with the same account? If not it may be a problem with your account...
Click to expand...
Click to collapse
I know his pain I have flashed reflashed installed stock and im using a atrix 2 with ics 4.0.4
im hoping its a google server problem and it will be fixed
I was having the same problem for the last two days and I went to settings/Google account and noticed there was a sync error with sound search for Google play and I manually synced it and now apps download .
Sent from my Nexus 5 using Tapatalk
I went into my account removed my devices from it on the web and signed in on my phone now it works
Sent from my MB865 using Tapatalk
I've been having the exact same issue for 4 days. Regardless of rom, phone, or gmail account I use. I've done every wipe format imaginable even Odin as I have a Samsung phone same issue. Now I cant even get any Google apps to connect at all. Such as Google plus play store YouTube etc...Google says never heard of it before sorry.
dawiseguy77 said:
I've been having the exact same issue for 4 days. Regardless of rom, phone, or gmail account I use. I've done every wipe format imaginable even Odin as I have a Samsung phone same issue. Now I cant even get any Google apps to connect at all. Such as Google plus play store YouTube etc...Google says never heard of it before sorry.
Click to expand...
Click to collapse
I'm having the exact same problem now for a few days. I called Google support and they are aware of the problem and had no resolution. I was told too bad basically.
Out of curiosity, for those having this issue, did you upgrade to a 4.4.2 ROM?
I updated to stock rooted 4.3 galaxy note 2 Verizon and it happens on all of my gmail accounts too
Sent from my SCH-I605 using Tapatalk
I have the same problem. Ran across this thread doing a search for the error 927. Running a Verizon HTC One and an LG G Pad 8.3. Both have the same problems, and i too have called Google several times. Their answer was to call HTC. I was livid. I changed my password, but was only a temporary fix until I made a purchase from the Play store. Then the error came back. I realize i am in the Nexus 7 forums but wanted to chime in since the problem is happening to me too. Hopefully Google comes up with a fix. Too much money tied up to just create new account, which does work by the way.
Creating a new account shouldn't even be an option what it the issue happens on the new account? Google just needs to fix it.
Sent from my SCH-I605 using Tapatalk
dawiseguy77 said:
Creating a new account shouldn't even be an option what it the issue happens on the new account? Google just needs to fix it.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
I agree...I would be ok if they just said we're working on a fix, but just to ignore me and say call the manufacturer pizzed me off.
Sent from my HTC6500LVW using Tapatalk
planedoc said:
I agree...I would be ok if they just said we're working on a fix, but just to ignore me and say call the manufacturer pizzed me off.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Yeah Google making me mad too
Sent from my SCH-I605 using Tapatalk
Same boat. I did everything the original poster did as well. Called into play store support and eventually got passed off to tier 2 support. Haven't heard anything in over a week.
The issue affects every device I log into with my account. Originally showed rpc:s-7 error, now 927.
Anyone with this problem find a solution? Again, I've done everything the op posted. In the past I've been able to correct the problem. But this time, no go.
Have the same problem... In every device I'm using with my account... 3 tablets, 2 cell phones. Spent more than 400 dollars in apps.. Can't download, nor even update. Always error 927. Changed password and problem persists.. It's obviously a problem with my account.. Wonder what could I do.
Have you tried installing apps from Google Play on a computer?
Hello, just an update...
My problem has gone... Seems it was from google side.
Too bad I had to flash my cel 3 times before I realized it was happening to all my devices.
Don't know if the password change had anything to do with the fix since, at least, it didn't work immediately.
If you encounter the same problem don't panic... give it a little time, hopefully it fixes on its own.
Thank you very much.