yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chronus719:
I would guess that Google Wallet cross-references the Zip Code, etc., when charging your card to prevent fraudulent charges, so it doesn't surprise me that international cards are not working even though Wallet for some reason lets you add a card without the correct billing information.

For those of you getting hung up on activating your card or verifying account, make sure you're on your data connection and not Wi-Fi. I've had issues over the period of flashing new ROMs, etc., where I would get hung up on a Wi-Fi connection but it would go through almost instantly on a mobile data connection.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the_ape:
The details on the card registered are however now correct, as you can login to wallet.google.com and set it there. So it's obviously something else that's not in place. Oh well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chronus719:
His didn't work using an unpatched version of the newest Google Wallet APK. The OP has since been updated with a patched version of the APK, which will allow you to return your build.prop values to stock without breaking Wallet functionality.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chronus719:
I wonder if they're only running authentication on US cards then, and international cards are not going to go through until they add support from their end.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkeyman:
Get off of WiFi to finish setup...

I would have to concur on this as I mentioned previously that when mine was hanging initially and I went into the WiFi settings to disrupt the setup and returned back it eventually went through and finished setup once I disabled WiFi so this method has been confirmed to work by myself as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jawonder:
Guys make sure when you put the apk in system/app you set permissions to-rwrr-and then boot into recovery and reboot , it's working great for me on JB AOKP and i'm back on my original build,prop,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ksujace:
This worked great on my SGH-I9300 running CM10 Preview (Nightly 08032012) ... will test to see if I can acutally use it at CVS or McDonalds today :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smashcz:
Just wondering, why revert build.prop to the original values?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
A few reasons.

1. Correct market compatibility for apps

2. Some ROMS won't install when they assert that you're not running the intended hardware

3. Some apps (even the xda app) use the values, and might do the wrong thing.

4. It's just nice not to have to impersonate another phone :) s3 and proud.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pprice520:
Quick question, this doesnt work on cm10 incredible 2? Or did I not do it right? Ik not an inc2 thread

follow me on Twitter.com/pprice520
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
Got it working and setup but as soon as I revert original build.prop it says not available blah blah.

Guess I will keep it thinking its a Gnex. Oh well small price to keep it working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tal0s:
Installed as directed and reverted to original build prop using root explorer.

This is working as advertised. - Diet ICS 7/22, ICS Domination 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peaster3:
Used it at Home Depot today. Everyone thought I was the bee's knees! Awesome work and thanks! Using CM10 at the moment.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HeroKhar:
Thanks guys, just bought something at McD's, Lady there was impressed, no Force Close either!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HeroKhar:
I only have one issue, on JB, when I tap the "More..." option in Settings, most of the time, the Settings app freezes and stops responding, very rarely does it let me in so that I can disable my NFC and other options. But I can easily back out and go back into my home screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pprice520:
Can someone message me to help get it on my cm10 dinc2 aero modded v12

follow me on Twitter.com/pprice520
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smashcz:
Should I reset even if I'm updating to new version (same rom-aokp) without wiping data, only cache?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] random1204:
Trying to make this work on CM10, but it keeps saying that there was an error adding my card and to try again later?

Anyone know what to do here?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
It could be ur bank not responding, Google servers being slow.

Did u try another card?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] random1204:
Well, I'm adding my prepaid card, I haven't tried my debit.

I'll see if that one adds...but I don't know why my google prepaid isn't going...

EDIT: As soon as I typed this, after trying the whole thing over again, it worked.

...of course. Haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HeroKhar:
You can follow my guide here: http://xdaforums.com/showthread.php?t=1810282
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tefloncoated:
Wrong thread, sorry

Has anyone experienced an issue where the NFC just stops working? The check box is still ENABLED in settings, but the NFC tags are not being read. This happens with screen off or on (i have the fix enabling NFC with the screen off installed). I have to disable and re-enable NFC in the settings to make it work again and be able to read the same tag. Then, after a period of time, NFC stops working again and i have to repeat the process. Seems this started happening after i installed and set up the Google Wallet fix... Thanks!

UPDATE: FYI, so it looks like this is due to the Wallet: http://xdaforums.com/showpost.php?p=29899578&postcount=1136
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smashcz:
nobody knows?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
Yes you should. I am on Jellybro JB and when I updated to latest version even tho I dirty flashed (just cache and dalvim wipe) i needed to redo the GW fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chronus719:
Yes, before every single ROM is flashed do this. Regardless of if it is an update to your existing ROM or a completely new one, without exception.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evo4eva:
Now when the op says to reset from within the app, does that mean to reset to default and clear all data before flashing a new rom? If not could somebody please explain what he means? I would greatly appreciate it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
Go to Wallet click setting and click Reset Google Wallet, that will remove ur cards that GW has stored. Its safer if u do it rather then just flashing another ROM. As Google security might flag ur phone as insecure if u don't reset ur self. That's what I understand from reading the posts here about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gtluke:
Anyone have the time/skill to make a flashable zip for AOSP AT&T phones? I wish I was skilled enough, I read about it for an hour on how to do it but I suck too much. I keep flashing my phone with CM10 and other variants so I have to dork around with wallet constantly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malinois16:
Used it today at McDonald's! Worked like a charm!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brushrop03:
So how do I know if my Google Wallet is jacked up because I didn't reset?

I was using Diet ROM which had it preinstalled but then I flashed Blazer Rom. Reinstalled wallet on Blazer, but it won't add my Google Account.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
Google wallet help line and they will help u with prepass security issues. Plan on being on the phone awhile from what I have heard they take forever.

I have never reset my GW so far and have flashed the fix at least 5 times so fat without being locked out.

Check ur email as u would have gotten and email from Google wallet when u first activated it it will have the help line numbers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brushrop03:
Well that sucks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
I tried the fix, which works as the app starts, but have been unable to authenticate my cards.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brushrop03:
So I went back to Diet Rom which had the app preinstalled and was able to set everything up again. Reset Google Wallet and flashed Blazer's rom. I installed manually and got the App to open, but I can't past "Adding your Account"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MentalDragon:
OMG!!!

I have tried everything i can possibly think of. I have had this working before on a stock rooted rom. But everytime I try to get it to work on a CM10 rom it destroys NFC. Completely removes it from the options!!!!! How is that possible??????? Grrrrrrrrrrrrrrrrrrrrrr...Ok back to the drawing board.

Edit: SGS3 on CM10 task and ktoonez 8/8/2012. Everytime i go through the Wallet steps i loose option for NFC in settings. If I am in stock rooted rom I can do this with no problem. If I dont do Wallet steps I still have NFC option in setting with CM10.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rkennison:
Keep trying, they will go. Oddly, what i found to make them work ( and I just did this not 20 minutes ago ), is once you select a card and it's trying to add it, press the back key to take you back to the previous screen. Let it sit there.. Mine bombed out over and over until I did that. Then i was able to activate 2 cards back to back no problem. Don't ask me why.. all I know is it worked 2x in a row that way.

I'm on 8-10-2012 #2 AOKP build by task
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aquethys:
This is normal? (The unsupported device)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Yes, it should still work without issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] darkwire:
For those of you seeing the unsupported device, remember to uncheck the auto update from Play. You might need to uninstall Wallet+removing the settings if it already updated.

Unchecking the box fixed that issue for me after a reinstall.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
I was on diet and google wallet was all set up, the buildprop was galaxy nexus. Even had the 10 bucks from google but never actually got the chance to use it. Installed aokp jb latest. Downloaded the file here and installed it and wallet. Wallet opens fine and I can go into my cards. But when I try to activate the google prepaid card again it just sits at verifying account with money network. Tried clearing cache and all that but no luck. Oh and I did reset wallet before flashing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrdindon:
Not working anymore on S3 Rogers

Wallet used to work with previous version then someday disappeared from touchwiz...

the apk was still under /system/app.

tried to install the new one and modifying build.prop accordingly gives me : "application not installed" when I launch the new apk copy pasted to /system/app. (I also chmod the file accordingly...)

Any ideas ?

Thanks for your help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GHOSTIVVI:
I'm running Cm10 8/14 build on i747 (AT&T version) and can confirm this still works. I used it at a local McDonalds yesterday, bought 20 piece chicken nuggets!! ( I didn't eat all of them btw ;) )
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FFJASON1:
I just flashed Triune II , 08/15/12, rom and am now getting an "insufficient secure element privileges" error message. Google Wallet worked fine on previous roms using the OP instructions. I have posted this in the rom thread as well and thought there may be some general suggestions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Main Target:
I flashed a .zip that was apparently made for AOSP (I thought it was this thread but now I can't find it) and for the first time ever with out any modifications other than the.zip I was able to launch wallet. I am unable to use any of my cards though because the all come up with request failed. These cards were already in Google wallet. An I doing something wrong? Was the method I used to get wallet up and running pulled for some reason?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nightkid:
I have the same problem.. Any help? I am on the latest Diet. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
I think you might have done a boo boo... Before you flash a Rom you are supposed to clear out Google wallet or it, according to some posts here in xda, will break the secured element...

Search for something like "psa Google wallet" and you should find it here on xda.. I haven't gone through the entire thread but you might want to read it.

Update: the first thread in this post also warns about flashing before resetting Google wallet...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] soccermon15:
OP, it might be helpful to mention in step 7 that the permissions need to be edited to -rw-r--r-- once the apk is pasted in /system/app. I knew to do it just because I had done it before. But there might be some who don't know that needs to be done. And if this thread successfully gets moved to the general section, I'd definitely throw that in there since there will be less experienced users there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mirrored:
can we get a newer version so we can add other cards besides citi mastercard?

---------- Post added at 07:54 PM ---------- Previous post was at 07:44 PM ----------

so I did this method and it worked great but I accidentally updated the app in the Play store. It said the usual "your device is not supported" upon opening the app, so I exited out and pressed uninstall on the app page in the play store.

the app was still installed so I hit open from the app page in the play store. it opened as usual and acted like I had cleared data on the app. so I went through choosing my account and it got stuck on "activating account." so I rebooted my device and now it's stuck on "initializing device." I restored a nandroid when wallet was working fine and its still stuck on "initializing device."

any ideas? did I fry my security element? can I call google to have it reset?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wild Weasel:
Root manager is not free, and all the other file managers I try cant copy to the /system folder.

anything out there for free?

Edit: found a good file manager, that is free unlike OP's, please add it OP: ES file explorer, gives you superuser, and R/W privileges.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] timeToy:
According to: http://xdaforums.com/showthread.php?t=1769083 ES explorer will NOT work for this
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tal0s:
Confirming ES File Explorer will NOT work for this.

Problem occurs when saving buildprop with ES.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] McAwesome:
Works fine for me but as you may notice from my SIG I have to stay on modified build prop no big deal to me for this awesome app.

Mc2992
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
I had the same issue, wasn't from breaking the secure element. What you need to do is:

1) Download the zip flashable wallet

2) Install Triune again (on top of itself)

3) before rebooting install wallet zip

4) reboot into system

5) change build.prop

6) run wallet and setup

7) once setup change build.prop back

Done! I think the issue was around installing Wallet into System after it's booted up (not sure why).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatonjb:
the other way seems a little more simple. what is the advantage of this way?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] THISisTIG:
GW not yet available.... after i had it working

I'm hoping this is the right place to be posting this... So far I've flashed the 9/2 CM10 nightly which includes a version of google wallet preinstalled. I was able to modify the build.prop files and got my wallet up and running with the preinstalled wallet version. Then deleted the old build.prop and renamed the new build.prop with the updated Nexus data all using root explorer. I claimed my Google prepaid card, added new cards and got it all set up. I've read conflicting stories on backing up after your wallet is completely set up so I decided to give it a go. I backed up using TWRP and after the reboot I received the message "unfortunately, GW is not yet available for your device or mobile network." I don't think i broke my secure element YET because I've seen the messages that those with broken elements are getting.However, im unsure on what steps to take next to try and get it back up and running. Should I revert to my TWRP backup that had the wallet up and running? Flash my backup from before i modified my build.prop which was an unofficial nightly from 8/16 or try something all together new? Hopefully you guys can help!! I really don't want to ruin my chances to use the GW. It looks pretty awesome.

** Update!! I just checked my build.prop and it doesn't appear that the changes saved when i backed out of root explorer!! Im thinking this could be an easier fix than i thought. Can i just remodify the build.prop and reboot and reopen my GW account or do i somehow need to delete my current copy of GW and flash a hacked copy and start from there?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatonjb:
I am not sure, what makes this option better then the other option that has been posted? its seems like a crap load of work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rkclarke:
Works on a Verizon Samsung Nexus running AOKP

Thank you VERY much!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smashcz:
is it ok to update to newest version in play store? (1.5-r79-v5) (Sep 5)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgoat:
I have an att gs3 and edited my build prop to this. I am able to use an unmodified apk from the play store. I didn't revert my build prop to stock.

ro.product.model=SPH-L710
ro.product.brand=Samsung
ro.product.name=d2spr
ro.product.device=d2spr

Edit, This works on Task's AOKP. I get a funky triple reboot the first time after changing the build.prop then no issues at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] THISisTIG:
If you read my lengthy post ... MY BAD! I can confirm wallet is working on i535 Verizon SGS3 running CM10 M1 release. I would recommend not using any version of GApps that has a preinstalled wallet. Find a copy without and flash the most recent wallet posted at the 1st page of this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] michelbites:
So I got Google Wallet working today. (first time with this.) After reverting my build.prop back to normal I got a dialog screen come up saying Google Wallet is no longer supported on this device. I didn't think ATT was blocking Google Wallet actively. So I changed my build.prop back to the modified version and it works normally.

is there a problem leaving my build.prop like this? will this damage my phone? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
The only side effect I notice is my signature
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mauzydpt:
What are the verizon galaxy nexus defaults that we had to change to maguro and yakju? I see the att defaults. I know the first is toro but what do we change yakju back to?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mike02z:
Worked like a charm on my Verizon SGN. I run JBSourcery and my original build.prop settings were:

ro.product.device: toro

ro.product.name: mysid

ro.product.model: Galaxy Nexus
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mauzydpt:
Thanks, mine is working too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theroo:
Works for me without editing build prop
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Hey guys hoping someone can help me out, this wallet fix use to work for me before I did a full reset from scratch and started using the cm10 nightlies from 9/13+up and now I'm on the code fire ROM and it still doesn't work. From my SIG and the fact I was able to install max Payne I know I edited build prop properly but when I do the move of the apk into system/app and the reboot recovery and regular reboot there's no wallet app installed. The apk is still in the system/app folder but it does nothing and won't boot up even if I change permissions to rw-r-r which I didn't have to do when it was working before. Any help is greatly appreciated hopefully we can get it working again I'm already missing it like crazy lol oh I'm on an I747m from Telus.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] michelbites:
The reason I ask is when I revert the build.prop back to stock it just breaks the google wallet. I have to keep it as a Galaxy Nexus and not the S3...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erandhawa:
Nope won't cause any issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Seriously no help at all? Geez guys. Well as an update I just flashed to AOKP's latest build and no change. Either when I first reboot after doing the fix I'll get a Wallet force closure from there, there's no icons no nothing for wallet I only know it's there still because the APK would still be in the app folder. Any help guys, on what I can be doing wrong? Or what I could try?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] z3nith66:
any idea if this will work on the international version? i9300?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scottlee64:
For the longest time I was seeing nothing in the drawer as well (occasionally I'd get the FC on boot). What worked for me on my Canadian Bell S III was to drop the (modaco-patched) app into /system/app/, set permissions to 0644, reboot, "defrost" with Titanium Backup, open wallet, set up account, change build.prop to be a Galaxy Nexus, reboot again, add cards to google.com/wallet (didn't even spoof my address. Used the actual Canadian CC addresses), then add them to the phone, revert build.prob, reboot. I don't know if that's the way things should have been done but Google wallet opens and allows me to select cards now. I have to defrost it every time I boot, so I still have to figure that out, but the rest of it seems fine. I certainly had much trial/error during the whole process, but that's it from start to finish.

Bear in mind that I have yet to attempt to pay for anything with it. Hoping to try a Tim Hortons some time this weekend.

Edit: It occurred to me while trying to fall asleep that I changed my "home address" in google wallet's website to a US address prior to activating my account on my phone. I don't know whether this did or didn't permit the account to be activated, but thought I should mention it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tachhire:
Build Prop

OK so I followed the step to the "T", and when i reset my build props google wallet doesnt work. However, as soon as I change them back to the Galaxy Nexus it works just fine. Can u help me with a work around? Or can i just leave my build properties as is since google wallet works? Just so u know i am running CM10 9/28, and it is ATT. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] resrevni:
What's the difference between this Google Wallet and the one in the other thread?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dB Zac:
If you can't get the play store one to work, this one might
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dualmoon:
A couple of notes here. Running CNA latest (as of post time) and everything seems to have gone swimmingly. I did, however, have to change the permissions as the apk had -rw------- (600) instead of -rw-r--r-- (644). Also, rebooting into recovery is probably superfluous. Otherwise works perfectly.

A note for everyone else, if you don't feel like paying $4USD for something that should be free anyway, try Solid Explorer. It looks amazing and is the best file manager I've used thus far. I even dumped Anttek for it.