yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] GREGHARKINS:
I did this

There's been modded apk's, xposed modules, nfc lib patches, etc all leading up to installing the new wallet version and having tap+pay enabled. All have failed for me except for what I just did.

This is what I did and so far all looks promising (have to test actual payment). My method is for aosp, currently running cm10.2.

1: uninstalled current playstore version of wallet (the new one we can download without nfc activated)

2: I did not reboot, just ran wallet installer

3: after the reboot I set up wallet completely. While setting up, a notification appeared notifying of an update. It did not auto update because of new permissions in the new version of wallet.

4: after setting up I then updated wallet from the playstore. Opened it to verify nfc capabilities.

5: restored build.prop via installer

6: done! Nfc still enabled within wallet.

---------- Post added at 09:46 AM ---------- Previous post was at 09:45 AM ----------

Then used this fix

This is how I got tap-to-pay to work with the new Wallet and my VZW SIII (thanks to loserskater):

Change the following lines in build.prop to

Download the NFC fix.

Boot into recovery, flash the fix, reboot.

Download the new Wallet from the Play Store and set it up.

Change build.prop back to what it was before.

Reboot and profit.

Proof:
[Verizon Samsung Galaxy S III] joekiv:
If i'm reading this correctly, ISIS won't work unless your unrooted and I believe that GW won't work if you are. So they can't coexist on the same phone. Correct? When you reinstalled Google Wallet did you do it with the new Secure Sim installed or did you switch back to your original SIM
[Verizon Samsung Galaxy S III] cnlson:
What nfc fix? Link please.

---------- Post added at 12:11 PM ---------- Previous post was at 12:07 PM ----------

correct on s3, gnex shouldn't have any problem

nope

Yes, so far I've not tested a payment yet. If it doesn't work I'll get a new sim, the old one isn't active after it's replaced.
[Verizon Samsung Galaxy S III] ohemetophobia:
I was running the version previous to 2.0 from a patched apk and with busybox and xposed. Today I used wallet installer to modify the build.prop and installed the 2.0 update. So far, tap to pay shows that it's available. I will test my luck with the Coke Machine at work, hopefully network connectivity won't be an issue because I can't get a viable data connection.
[Verizon Samsung Galaxy S III] GREGHARKINS:
This post

http://xdaforums.com/showthread.php?p=45789816

Go back to page 25 if using 10 posts per page the link is there
[Verizon Samsung Galaxy S III] joekiv:
"Yes, so far I've not tested a payment yet. If it doesn't work I'll get a new sim, the old one isn't active after it's replaced."

Would like to know if it works. I have a secure SIM, but I haven't installed it yet. Waiting to see what happens when they roll it out nationwide. As of right now, I'm leaning towards GW.
[Verizon Samsung Galaxy S III] ohemetophobia:
My test worked. I successfully purchased a soda via tap to pay on 2.0 with d2vzw.
[Verizon Samsung Galaxy S III] annoyingduck:
Confirmed working nfc tap payments100% New wallet version on as aosp.

-Uninstall any version of wallet currently installed

-run washer installer app

-after reboot set up wallet completely

-update wallet from the playstore

-open wallet to confirm tap+pay

-close wallet

-restore build.prop using wallet installer

Been testing at several locations, all working correctly. Super easy!
[Verizon Samsung Galaxy S III] lieffring:
Just did this on cleanrom 7 and works perfect! Thanks for the info!
[Verizon Samsung Galaxy S III] Afro Samurai:
This method seems to be what's up. Right now I have the most current google wallet with tap to pay enabled. I'm on Synergy rom currently. No xposed modules or framework either. Just the apk from this thread and these directions...:victory::victory: Still gotta try it though.
[Verizon Samsung Galaxy S III] roaddog665:
Confirmed working on stock rooted TW. Just made tap +pay purchase with no problems.
[Verizon Samsung Galaxy S III] Bright09:
anyone?
[Verizon Samsung Galaxy S III] supercell2000:
Worked perfectly, thanks!
[Verizon Samsung Galaxy S III] lieffring:
No unless you have an NFC battery
[Verizon Samsung Galaxy S III] Afro Samurai:
If I'm right you can use your NFC SIM with Isis wallet and it won't work if your rooted. But, they have a fix in the S4 thread. It may work on our device but I haven't tried it out since I got Google Wallet working.

Sent from the S3 of The Afro Samurai
[Verizon Samsung Galaxy S III] Bright09:
well thanks my miss understanding lol may have to get Google wallet set up but thought about replacing my battery hardly use NFC anyone know if hypervirion 2300mah is good or just stick with zero lemon
[Verizon Samsung Galaxy S III] shmeyer917:
I am having an issue keeping NFC on. I am running AOKP.

Anyone know of a fix for this?

Thanks in advance.
[Verizon Samsung Galaxy S III] Afro Samurai:
You could always just give it a shot. Setup Google Wallet and see if it works with the batteries you have. It can't hurt.
[Verizon Samsung Galaxy S III] ratledge:
How-to update Jellybean working to latest Google Wallet version

Confirmed working NFC tap payments 100%

New wallet version on a rooted TouchWiz (with previous Wallet already working)

+SKIP the Uninstall step!

-run wallet installer app, select JB & VZW

-after reboot, update wallet from the playstore

-open wallet to update / synchronize new version and confirm tap+pay

-close wallet

-restore build.prop using wallet installer

Tested at several locations, all working correctly. Super easier!

You can link your bank account, now, also - assuming that you want to do so.
[Verizon Samsung Galaxy S III] qdtphotog:
Doesn't work for me

I tried similar steps above but when I opened the Wallet app after installing it, I got this error message about "insufficient secure element privileges for this system image (release-keys)". Then the only options I had was exit the app. Does anybody know how to get past it? This is driving me crazy. Thanks.
[Verizon Samsung Galaxy S III] ratledge:
You already had the previous version working? Doesn't make sense, really. It wouldn't work without the secure element, either. The key is getting it installed once using "Wallet Installer". That adds SE in the process - pretty certain.

I suppose you can chase down the "Secure Element" hack (a couple of page back, I think) first. Should work. YMMV...
[Verizon Samsung Galaxy S III] Rev. Voodoo:
Yup... Followed this process running CarbonROM latest nightly, got out to the local store for some Hallowe'en gear and it worked perfectly. I'm pretty frikkin' happy about this development!
[Verizon Samsung Galaxy S III] tducote:
It depends on the version of the Hyperion battery. I've got some that work, but I don't think their older ones had a few capabilities.
[Verizon Samsung Galaxy S III] Bright09:
well i ordered the two 2300mah zero lemon battery's few days ago xant wait to try them out
[Verizon Samsung Galaxy S III] cnlson:
wallet in the market for everyone?

ok i just went to the market in my wifes phone, and it's there, it installs, and it doesn't complain at all..

whats going on?
[Verizon Samsung Galaxy S III] Prl91:
It may just be that your build.prop is already edited. If so, the Play Store will install it.
[Verizon Samsung Galaxy S III] stimpco:
It will install just fine, but the option for Tap and Pay settings is likely missing... yes?
[Verizon Samsung Galaxy S III] cnlson:
that's it! i had set my build.prop to a nexus 4 and it let me set up tap and pay but hers will not set up (not rooted)

wierd thing is after i reverted the build.prop tap and pay remains

it looks like now, the steps are

1) install correct libs

2) change build.prop

3) install from market

4) setup tap and pay

5) revert build.prop

profit???
[Verizon Samsung Galaxy S III] cnlson:
my wifes, unrooted non build prop edited s3 installed it perfectly
[Verizon Samsung Galaxy S III] WettbackMartyr:
Wallet is now in the play store for all US carrier android phones. But the option to pay with NFC is limited to the carriers that supported it from the beginning (I. E. SPRINT in the US, and Google phones). You can now install it without modification from any US carrier but your NFC payments will not be enabled or even an option without a modification of some sort. That's what's going on in a short story version.
[Verizon Samsung Galaxy S III] cnlson:
If as a part of this thread or the linked one a few posts earlier with the flashable NFC fix you install the sprint NFC libs and you set it up with a modified build prop, on a vz 535 at least, it will setup tap and pay. I have reverted my build prop and it still shows tap and pay available. I'll try it tomorrow at work on the candy machine that worked with isis and see.

Here's the link to the post that has the link to the NFC flashable

http://xdaforums.com/showthread.php?p=45918538
[Verizon Samsung Galaxy S III] WettbackMartyr:
Thanks let me know what happens. Truly interested in the results. :thumbup:
[Verizon Samsung Galaxy S III] TJF2012:
Yup i did these steps and it works fine.. tested at a couple of locations.. worked perfect!!! I am one happy camper

---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------

Im also trying to find your donate button but its not showing up on my xda app. Do i need to view it on a pc?
[Verizon Samsung Galaxy S III] Rev. Voodoo:
I'd gotten so used to reinstalling wallet everytime I upgraded ROM nightlies, I was quite surprised when it stuck around this time!

Now that the actual play store version runs just fine, it stays in place and works after flashing a new nightly.... very cool!
[Verizon Samsung Galaxy S III] BlaJod:
Ok Rooted Verizon S3 running Bonestock 3.4, have had the previous build of wallet running for the longest time, payments successful all the time, followed instructions on how to (update, edit build.prop etc) to get the new version of wallet working. Now, installs fine doesn't really matter if you leave build.prop same (Galaxy Nexus, yakju and maguro) or if you change it back to stock, I realize that so I've left mine the same <--. Tap and pay shows within the app and everything seems like it's going to work the way it should at checkout, but I cant remember the last time it was successful with the updated app. The picture attached is what I get pretty much instantly when I place the phone near the reader. Could this be the lib issue people are talking about, I'm lost at this point.
[Verizon Samsung Galaxy S III] joekiv:
Update from Play Store or Not

I have a rooted Verizon S3, Stock Rom, TWRP Recovery. Never had GW on Phone. I read through all these post and in multiple earlier posts it is stated that you should NEVER update wallet from the play store. Latter post state that it is the 1st thing you should do after installing & setting up wallet. Which is it?
[Verizon Samsung Galaxy S III] jrc27:
. I just did this...ran the installer, set up wallet, updated wallet from the play store and then returned build.prop to normal. Tap and pay set up fine but I haven't been able to test it at a store....
[Verizon Samsung Galaxy S III] joekiv:
Are you on stock rom?
[Verizon Samsung Galaxy S III] jrc27:
Sorry, running CM 10.2
[Verizon Samsung Galaxy S III] Sublime2:
Well, after numerous trys I have succeeded in installing wallet with TAP.

Running hyperdrive 16 on a Verizon S3.

Also, I did NOT update after the install.
[Verizon Samsung Galaxy S III] ratledge:
Mine is - obviously rooted, or you can't mess with the build.prop file.

Rooted, de-odexed TouchWiz (VRBMF1) here...
[Verizon Samsung Galaxy S III] joekiv:
I think you're missing what I'm saying. You do know that you can be rooted AND on Stock rom, as I am. In my original post I stated: Rooted, TWRP Recovery and Stock Rom. My question is directed to updating Wallet from Play Store without a 'custom' rom. Some post state never update from Play, while others say it's the first thing you should do after setting up Wallet. I want to know if anyone on a 'rooted' Stock Rom did the update from the Play Store successfully. Two different ways of proceeding. I would like to get it right the 1st time.
[Verizon Samsung Galaxy S III] ratledge:
Well, I can't say for certain - because I obviously haven't tried any other way, but reading everyone else's comment here, I have to assume that you can install this version from the market without using the "Wallet installer", but you end up without "Tap and Pay" functionality. I don't know why anyone would want it that way, but yes, with a stock ROM you can install from the market from what I read here, but you won't have Tap&Pay.

I'm pretty certain all the posts that say "never update" were done before the new version came out. Now, I can't say for certain that they won't change the way it works - they just did - so maybe leaving auto update turned off isn't a bad idea until future versions are released and tested.

I always used a stock rooted ROM until VRBMF1, but went with the de-odexed version this time so I don't have to chase down updates that are meant for use with odex or not. I can see how it gets confusing, but at this point you can update from the market, but assuming you have it now, you likely lose Tap&Pay unless you let "market installer" add the "secure element" capabilities.

"Your mileage may vary"...
[Verizon Samsung Galaxy S III] Prl91:
I originally stated to not update on the Play Store because, at the time, it would remove the changes in the modded Google Wallet application. Now that Wallet is readily available on Play, feel free to use Wallet Installer and then update, but I can't guarantee support. I only offer support for the version Wallet Installer installs. Other methods posted here are by other XDA members. I kindly asked that they move the alternate discussion to a new thread to lessen confusion, but so far that hasn't worked. In short, Wallet will work through Wallet Installer, but updating has never been personally recommended by me, at least with normal Wallet Installer use.
[Verizon Samsung Galaxy S III] joekiv:
I have no intention of doing it without the Wallet installer.
[Verizon Samsung Galaxy S III] ratledge:
Yep, sorry. I don't want to clutter the OP's thread, but I think I posted the answer back in #1243 & #1245. You need "Wallet Installer", or you don't have "Secure Element" - on VerizonWireless, anyway. Again, I don't know for sure about other providers.
[Verizon Samsung Galaxy S III] joekiv:
Thanks for that info. My original question was obviously getting unnecessarily circular.
[Verizon Samsung Galaxy S III] mastabrozif:
Nevermind
[Verizon Samsung Galaxy S III] Prl91:
No problem.
[Verizon Samsung Galaxy S III] joekiv:
Can't find Wallet

I ran the Wallet installer and it ran through and rebooted fine. But I could not find Wallet on the phone. Checked every screen, Application Manager and the App Drawer. I used ES File Explorer to check the build prop. The Wallet installer made a backup copy which I can open in the text editor, but I cannot open the 'new' build prop. Get a message stating "error getting the content". So I can't see or edit what's in there. Unsure of how to proceed at this point. Suggestions would be appreciated.

UPDATE: Used Root Explorer and was able to open Build Prop. Reads

Product Model : Galaxy Nexus

" Brand: Verizon

" Name: Yaksu
[Verizon Samsung Galaxy S III] ohemetophobia:
I don't think the wallet installer installs the app anymore. Since you have the build.prop edited correctly you can install wallet from the store. Once installed, run the app, set it up and make sure it shows tap to pay is ready for use. Then I use build.prop editor to change product name, device, and model back to their previous staet and then reboot the phone. I used wallet installer once to restore the build.prop but it put my phone in a boot loop.
[Verizon Samsung Galaxy S III] jrc27:
The last time I ran the wallet installer app (2 weeks ago) it installed wallet....
[Verizon Samsung Galaxy S III] joekiv:
You're the 1st person to mention that Wallet isn't in the Wallet Installer. So I Downloaded wallet form play store, but when I tried to set it up I got "insufficient secure element" error and wallet exited.
[Verizon Samsung Galaxy S III] ohemetophobia:
I know it used to be in there, it must be server error because it seems hit or miss as to when it installs wallet and it doesn't.

Anyway, uninstall wallet (updates) and then go to settings>About Phone and check to see if your phone shows as galaxy Nexus. Then make sure you have busybox installed and open busybox and click the install button there just to make sure you installed all the way. Use smart install if it isn't installed.

Once you've checked all the above, wallet the old version should be on your phone still. So open the old wallet, go through setup, and then update the app. Open the app after the update enter your pin and ensure tap to pay is enabled. If it is, you can proceed to build.prop editor and fix the values (don't reboot until you've changed all three values) to make your phone an S3 again. Reboot, enjoy.
[Verizon Samsung Galaxy S III] joekiv:
Additional

Uninstalled Wallet Updates, Busy box is installed, Phone is showing as Nexus. Open wallet and I get "Insufficient secure element" message. Only choice is to exit. Can't get to setup.

On further thought: I don't think this will work. Reason: the change in the build prop list 'Nexus'., but still has "Verizon" as the brand. The latest Wallet update won't work with Nexus on Verizon. So I'm guessing that's the problem. I reset build prop back to original and uninstalled Wallet. Will need to find another method.
[Verizon Samsung Galaxy S III] ohemetophobia:
http://xdaforums.com/showthread.php?t=2125300

Try using that method to get the previous version working. When this one dropped I used wallet to edit the build.prop and the followed the rest of the directions. Once installed via this method, keep your phone as a Nexus and then update the app. The xposed installer may make the difference. I know it works because I have it on my S3, but I'm also running liquid smooth 2.10. I'm assuming you're stock. Good luck.
[Verizon Samsung Galaxy S III] shootind5nukes:
You don't need to, it will work fine without updating. But if your like me and you want Tap and Pay it will work after updating, not before. I just a few days ago did it that way. Walletinstaller apk installed wallet, then I let wallet set up completely once that was done I used Google Play to update wallet, it worked fine and gave me Tap and Pay which I have used serveral times. BTW in case someone else didn't know you don't need a data connection for tap and pay to work, even though when you open wallet it'll say no internet connection available.

Edit: I tried 1000 different ways to get tap and pay to work including editing build.prop on my own and no method worked until I did the above method. Even when I used other methods and got Tap and pay to come up it always crashed NFC. The above method worked fine for me on cleanrom
[Verizon Samsung Galaxy S III] lieffring:
Yet another update for wallet in the play store and I just got liking to not update it.
[Verizon Samsung Galaxy S III] WettbackMartyr:
I woke up this morning to find an update waiting for me in the play store for Wallet. I figured for sure this would disable tap and pay for me and I'd have to uninstall and run Wallet Installer again, then update, then restore build.prop.. Ya know, the usual procedure. However to my disbelief, after I updated, with a d2vzw build.prop mind you, tap and pay still shows up as ready! Will see if it still works on my way to work this morning. No news is good news so I'll update if it fails. Peace!
[Verizon Samsung Galaxy S III] nahunta321:
I know this is not Q.A. buy can someone tell me that this work at all I see some people say it do some say it don't work
[Verizon Samsung Galaxy S III] shootind5nukes:
It works flawlessly. I left a row of customers and a cashier in awe when I paid with my phone at Walgreens today.
[Verizon Samsung Galaxy S III] ohemetophobia:
If you're talking about installing wallet, it's hit or miss for most. It worked about 3 versions ago (if you include this mornings update) After the update to version 1.96 I had to use a patched version of the app along with xposed installer. Then 2.0 came along and I'm not 100% sure xposed installer holds any bearing on whether or not it works, but I've been using wallet installer to edit my build.prop and then installing and setting up wallet before returning the build.prop to its original state using the build.prop editor in rom toolbox.
[Verizon Samsung Galaxy S III] joekiv:
Thanks to some personal assistance from shootind5nukes, I have Wallet up & running with tap & pay working. Got it installed without any stalls or misses.
[Verizon Samsung Galaxy S III] BlaJod:
Ok Rooted Verizon S3 running Bonestock 3.4, have had the previous build of wallet running for the longest time, payments successful all the time, followed instructions on how to (update, edit build.prop etc) to get the new version of wallet working. Now, installs fine doesn't really matter if you leave build.prop same (Galaxy Nexus, yakju and maguro) or if you change it back to stock, I realize that so I've left mine the same <--. Tap and pay shows within the app and everything seems like it's going to work the way it should at checkout, but I cant remember the last time it was successful with the updated app. The picture attached is what I get pretty much instantly when I place the phone near the reader. Could this be the lib issue people are talking about, I'm lost at this point.

Edit: Tried the flashable lib fix thats on page 126 and still get the same error (reader detected)

Anybody have any ideas at all?
[Verizon Samsung Galaxy S III] zetsumeikuro:
Is anyone else getting the unkown bs message and to see the cashier if purchase was successful? Pay to tap show's its functioning :confused:. Thanks in advance.
[Verizon Samsung Galaxy S III] BlaJod:
Yup does it say "Reader Detected" also? This has been my problem as well.
[Verizon Samsung Galaxy S III] zetsumeikuro:
No, I don't get the "Reader Detected" message.
[Verizon Samsung Galaxy S III] jrc27:
Yeah, but it was immediately after i paid, when the actual receipt was still downloading.
[Verizon Samsung Galaxy S III] zetsumeikuro:
Do you get a successful purchase?
[Verizon Samsung Galaxy S III] ohemetophobia:
I get it whenever there is weak or no Internet connection. You'll know if it is successful because you'll get the Coke from the machine or the receipt from the cashier. Wallet itself is just unable to determine whether the transaction is successful but it will get the info later when data connection is better.
[Verizon Samsung Galaxy S III] joekiv:
Same for me, got message, but transaction went through without any delay.
[Verizon Samsung Galaxy S III] jrc27:
yes
[Verizon Samsung Galaxy S III] TroobAdore:
seems legit
[Verizon Samsung Galaxy S III] zetsumeikuro:
Strange.. I have 3-4 bars of LTE in the breakroom. I guess it is just straight out failing for me because the machine just tells me to try a different card. But then when I swipe the card that wallet is linked to I have no problems.
[Verizon Samsung Galaxy S III] skybronco:
You don't need any data connection in order to make a purchase. You can be in airplane mode with NFC on and it will work if your wallet app is working right, I have personally done it that way with version 1.x

Regards
[Verizon Samsung Galaxy S III] joekiv:
No Internet connection needed

According to Google you do not need a data connection for purchases. You only need it to 'add' a new card or money