Develop Bugs

Google Wallet Help

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...

[Q][Oddball] Google Wallet Can't Add Prepaid

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.

Google wallet secure element stopped responding

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

[Q] Google Wallet - Reader Detected - CM10

When I bought my S3, I used it for about 20 minutes before rooting it and installing CM10. I've flipped through a few nightlies on it and just set up Google Wallet a few days ago. I never used it. I think I flashed another nightly at some point and then tried using Google Wallet at a BP gas station. My phone triggered the first time and I had to enter my PIN. I put the phone back to the reader after entering the PIN and received a message "Reader Detected, please have the cashier check...." ( I need to grab a screenshot of the exact error).
I read up on a few things and reset the app from within the app and completed a resetup of the app. I tried at a different BP this morning and got the same result.
Am I just SOL using Google Wallet now - did I fry the Secure Element? From what I can read it doesn't seem like that I did.
Anyone else running CM10 able to get their Wallet working? I've seen a few guides for the international S3 but I don't want to do that and really fry something.

Do you have the cm dualboot installed?
Sent from my SPH-L710 using xda premium

jdostal said:
When I bought my S3, I used it for about 20 minutes before rooting it and installing CM10. I've flipped through a few nightlies on it and just set up Google Wallet a few days ago. I never used it. I think I flashed another nightly at some point and then tried using Google Wallet at a BP gas station. My phone triggered the first time and I had to enter my PIN. I put the phone back to the reader after entering the PIN and received a message "Reader Detected, please have the cashier check...." ( I need to grab a screenshot of the exact error).
I read up on a few things and reset the app from within the app and completed a resetup of the app. I tried at a different BP this morning and got the same result.
Am I just SOL using Google Wallet now - did I fry the Secure Element? From what I can read it doesn't seem like that I did.
Anyone else running CM10 able to get their Wallet working? I've seen a few guides for the international S3 but I don't want to do that and really fry something.
Click to expand...
Click to collapse
It sounds like it might be the reader at the gas stations a lot of BPs don't have there's updated. Or if you have a case on your phone that could also cause interference.
Sent from my SPH-L710 using xda app-developers app

Reset google walet helped me before had the same thing with dirty flash
Sent from my SPH-L710 using xda app-developers app

Jbluna said:
Do you have the cm dualboot installed?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Nope, didn't even know it existed!

budde2 said:
It sounds like it might be the reader at the gas stations a lot of BPs don't have there's updated. Or if you have a case on your phone that could also cause interference.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I do have a case - I've done NFC transfers with my wife's phone but I'll try the next transaction with the case off. And I'll head somewhere else, thanks for the heads up on BP.

Tried McDonalds this morning - figured I needed coffee so might as well use them as a test bed.
No case this time. Put the phone on the reader, got the NFC sound and got prompted to enter PIN. Picked up the phone, entered PIN and was prompted to put the phone back to the reader. Put the phone back to the reader, got the NFC sound and the wallet "W" logo lit up. And that was it. I let it sit for 5 seconds or so then pulled the phone away and got the "reader detected..." message.
Do I just need to let this thing sit on the reader longer?

I've had this issue before, coincidentally at BP and McDonald's. Both times I used the reader I had forgotten to tell the person behind the counter "credit." So, maybe that's the reason?
Sent from my SPH-L710 using xda premium

So I grabbed the leaked official Sprint Jelly Bean ROM and put it on my phone. Didn't clear out Google Wallet ahead of time and re-set it up once I got the phone running again.
Went to a different McDonalds for another coffee (this testing is going to over caffeinate me) and it worked no problem. So it could be a CM10 problem or it could be the cashier at the other places I've tried. What I need to do now is put CM10 back on the phone and go to the McDonalds that it worked on to see if it is now broken.
For now though, a stock ROM is solid.

jdostal said:
So I grabbed the leaked official Sprint Jelly Bean ROM and put it on my phone. Didn't clear out Google Wallet ahead of time and re-set it up once I got the phone running again.
Went to a different McDonalds for another coffee (this testing is going to over caffeinate me) and it worked no problem. So it could be a CM10 problem or it could be the cashier at the other places I've tried. What I need to do now is put CM10 back on the phone and go to the McDonalds that it worked on to see if it is now broken.
For now though, a stock ROM is solid.
Click to expand...
Click to collapse
Its the other places not running it correctly. I I've used wallet with CM at McDonald's. I've had it work, I've also gotten the msg you got.
Sent from my SPH-L710 using xda app-developers app

jdostal said:
When I bought my S3, I used it for about 20 minutes before rooting it and installing CM10. I've flipped through a few nightlies on it and just set up Google Wallet a few days ago. I never used it. I think I flashed another nightly at some point and then tried using Google Wallet at a BP gas station. My phone triggered the first time and I had to enter my PIN. I put the phone back to the reader after entering the PIN and received a message "Reader Detected, please have the cashier check...." ( I need to grab a screenshot of the exact error).
I read up on a few things and reset the app from within the app and completed a resetup of the app. I tried at a different BP this morning and got the same result.
Am I just SOL using Google Wallet now - did I fry the Secure Element? From what I can read it doesn't seem like that I did.
Anyone else running CM10 able to get their Wallet working? I've seen a few guides for the international S3 but I don't want to do that and really fry something.
Click to expand...
Click to collapse
the secure element thing is a myth. i've never reset GW before wiping and it always works for me on CM10

I'm starting to think the same. When I switched to the official ROM I didn't do anything according to popular wisdom, just overwrote the phone with the new ROM and things worked. I switched back to CM10, just need to make it over to the McDonalds again to see if it works or not.
Its not like this is the most useful thing in the world either, considering how few places accept it, but I like to see if I can get things to work

jdostal said:
I'm starting to think the same. When I switched to the official ROM I didn't do anything according to popular wisdom, just overwrote the phone with the new ROM and things worked. I switched back to CM10, just need to make it over to the McDonalds again to see if it works or not.
Its not like this is the most useful thing in the world either, considering how few places accept it, but I like to see if I can get things to work
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1809548&highlight=google+wallet
more place will begin to accept it... i hope. cause it's awesome

I think it is actually something in CM10 causing the issue. I went back to CM10 and went back to the same stores that I had gotten it to work in using stock and had issues again. Ah well.

Just FYI for everyone still having issues with GWallet. I did the reset from inside the app, and it just so happens there was an upate for the app when I did that. Now running version 1.5-R81 - v4
I went to a McD to try it out and it worked. I did tell the cashier that it was "credit" since I read on another thread somebody had mentioned that. It lookes to me like he punched something on the screen. Rooted, FreGS3 v0.2.0 with Agat kernel v0.2.1
Hope it helps
Sent from my SPH-L710 using xda premium

I've used Tap and Pay at several locations with great success. CVS, Home Depot, Mcdonalds, and 711. I have also tried at BP several times and always got the error message you described. I always get strange looks from the cashier. One time a gas station attendant yanked the reader away and started asking what did I think I was doing? He seemed to think I was trying to hack into his card reader or something.

Constant Google Play Store error 927

What i have done so far is: cleared cache, uninstalled updates and then let it update on its own and then trying to update/resume downloads, factory reset. It is happening on my One and LG G pad. Anybody run across a fix or have any tips other than what I've already tried? I contacted Google and like an idiot when he asked about me being rooted i said yes. He blamed my problems on being rooted. I dont believe that is the problem since i went all the way back to stock with the same problems. Beyond frustrated.

planedoc said:
What i have done so far is: cleared cache, uninstalled updates and then let it update on its own and then trying to update/resume downloads, factory reset. It is happening on my One and LG G pad. Anybody run across a fix or have any tips other than what I've already tried? I contacted Google and like an idiot when he asked about me being rooted i said yes. He blamed my problems on being rooted. I dont believe that is the problem since i went all the way back to stock with the same problems. Beyond frustrated.
Click to expand...
Click to collapse
Read this. I have never had the problem but if it can be fixed in sure this article covers it
http://www.winphonedroid.com/error-927-android/

spokanite said:
Read this. I have never had the problem but if it can be fixed in sure this article covers it
http://www.winphonedroid.com/error-927-android/
Click to expand...
Click to collapse
The only one i havent tried is creating a new account. That kinda defeats the purpose and then I'll lose all my paid apps. Thanks though.

planedoc said:
The only one i havent tried is creating a new account. That kinda defeats the purpose and then I'll lose all my paid apps. Thanks though.
Click to expand...
Click to collapse
Yeah that ones kind of pointless. I think what some people say is create a new account just to update all your apps and then switch back. Maybe uninstall paid apps prior as well. And then re install once you update core apps.

To me it sounds like a google problem with your account. Does this happen when downloading new apps, when updating an already installed app, or both? Is it just paid apps or free apps too? Try to create a new google account just to see if you can successfully download a new app, or update your current apps. If it works with the new account, then the problem is google and not your phone.

Well, your not gonna believe what fixed it....I changed my password. Maybe something or someone got a hold of my password somehow and blocked the play store..thanks for all the suggestions!
Sent from my HTC6500LVW using Tapatalk

planedoc said:
Well, your not gonna believe what fixed it....I changed my password. Maybe something or someone got a hold of my password somehow and blocked the play store..thanks for all the suggestions!
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I'm glad you got it worked out. That's annoying it was something so ridiculous.

Well..turns out that must have been temporary. After changing it, worked for a little while then, I had to change my password after purchasing apps twice, error out after each purchase...Google tech help is worthless.
Sent from my HTC6500LVW using Tapatalk