yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Covart:
Anything after end of February, no workie with new kernel. You can download the app, but you won't be able to pay via pay pass. Online transactions will still register, but you aren't physically using your NFC chip.

The whole GWallet thing was brought up a bunch in Tasks thread in late Feb through all of March.

If you have a fix, I would love to hear about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
I used it on 04/15 via a paypass terminal at a 7-11. I was using Task's latest release at that time. I was unaware there was a problem with it. Can't say since then, as I haven't actually tried it.

I didn't use this app to install it. I placed the latest Modaco version (before Paul went to the xposed framework method of modding it) in /system/app/, set permissions, changed build.prop to htc_jewel, rebooted, set up Google Wallet, reverted build.prop, rebooted, and voila...like I've always done.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Covart:
I don't use an installer either. I update manually, and tried to use it in March and again in April with no luck. Only difference I can see between my way and yours is that I alter build prop for Galaxy Nexus, vice HTC Jewel. I will give it another shot. I just haven't seen anyone report success with Tasks ROM and the new Kernel until your post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fbiryujin:
I'm on AT&T GS3 Stock rooted and this seems to hang for a while, then reboots but Wallet never appears. What should I do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
Cm is a AOSP rom. I'm on the most recent cm 10.1 (4.2.2) nightly and wallet works fine. I restored the build prop after setting it up and it still works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DXP2:
Yeah I can confirm it does not work on Task650's AOKP 4.2.2 ROM. It is a really good ROM but no Google Wallet.

Hopefully we find a way to get it to work on the new kernel soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bigsl0ppy:
I have to disagree I'm using ver1.6-96-v13 on tasks 5-8-13 rom and it works flawlessly. Installed using the installer then edited the build.prop for galaxy Nexus activated/rebooted then edit back. I use pay pass at least 3 times a week with no hiccups. It's the first thing I set up after each task update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] popi09:
What carrier would I choose if I'm trying to install this when I have a AT&T s3 but using a T-Mobile SIM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DXP2:
I am on the latest Task650 AOKP ROM right now and after I boot back up after using the "Wallet Installer v3" app and tap Wallet it says sign in may take up to five minutes then after a few seconds says "Device Not Ready: Wallet is unable to proceed until this device is fully initialized. Make sure the device has network access and try rebooting if the problem persists."

How did you get it to work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
Did you end nfc?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DXP2:
Tweaked some stuff and got it working on the 5.9.13 build of task650s AOKP ROM.

;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
OK, I just tried it again at a McDonald's and payment went through just fine on Task's latest 050913 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Try out my newest app, RemoteFlash! I think you guys will like it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbenson1226:
Will this work on a Verizon GS3 running the latest CM RC4? I'm having issues when reverting back to the old build prop. Says not supported my on carrier when I reopen wallet after set up.

I update wallet to the latest v16. Could that be the issue? Should I stick with v13?

I'm coming from a Verizon Gnex so I'm used to wallet just working...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
The problem is that you updated to v16. You need to stay on the version Wallet Installer installs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbenson1226:
I though so. Is there an extra security check in the new version or something similar?

Thanks for the reply.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Not exactly. The problem is that it just hasn't been patched the normal way. Everyone is switching to Xposed, but several of my users don't want to, so I need to do it myself, or find another workaround.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nellycruzz:
This work on s2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Unfortunately no, sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbenson1226:
I'm not familiar with Xposed. Is there a thread for that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amgpower63:
I second this. I Googled xposed and ended up on a porn site. Wasn't disappointed.

Sent from Samsung Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corno1979:
lol.

One nice thing about this app as opposed to xposed is the way toggling build.prop changes is an easy one-click operation.

Is there an app that makes toggling build. prop values similarly easy (for lazy chumps like me)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
My Newest Project On Portal!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ParishM:
is it ok to let playstore update wallet ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
No
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmajuri1:
OTA 4.1.2 no wallet install

I have tried to use the app to install wallet.

root yes

busy box yes

i select jbtw,att

then it installs reboots

but gets stuck with the blue led on and vibrates every 3 seconds short quick pulse

any ideas

i just got the ota today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
Make sure you have the latest BusyBox.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmajuri1:
Thank you that worked perfect. setting wallet up now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
For some reason the server holding the files is down. I'll look at it in the morning and see what happened. Sorry for any issues you may have had!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickd88:
Just wondering if there has been any word or update on the server issue?

I became so dependent on this app, I'm gonna have to actually look it up and try to remember how to do manually all over again if it doesn't come back up soon. Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gocats7:
How does this work with the latest version of Google wallet? I'm on 4.3 and tap and pay shows not available. I'm wondering if the keys that need to be modified have changed. Suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbenson1226:
Keep an eye on this thread: http://xdaforums.com/showthread.php?p=45699789#post45699789
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
The server/host has been fixed! Let me know how it works, and sorry for the delay.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] njinstantkarma:
New Version 2.0

Does this support the latest google wallet version 2.0? I reapplied your app today and everything worked however Im still on the older version 1.06. Should I update the wallet app from playstore then try your app? or will your app have the latest 2.0 version soon?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
Install 1.96 through his wallet app and xposed wallet app (make sure it is applied in xposed and rebooted) . While your build prop is still under nexus, set up your Google wallet. Once it is set up, install the new update. Verify "ready to tap and pay" in the updated wallet app then restore build prop. Enjoy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] majikfox:
Still had to install the app from Play store

This worked for me except that after the app rebooted my device I had to go to the Play Store and install Google Wallet.

After I installed Wallet from the Play Store the Tap to Pay and other features are working.

I should note that I'm on Cyanogenmod nightlies and I selected AOSP because there was no Cyanogenmod option.

---------- Post added at 04:00 PM ---------- Previous post was at 03:55 PM ----------

Try this:

1. Clear data/uninstall Wallet.

2. Run this app.

3. Install Wallet from the Play Store.

4. Set up Wallet including Tap to Pay.

5. Restore build.prop using the app.

This worked for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnston212:
I tried this, but the app gave me a missing secure element error message.

I'm running Hyperdrive 16 if that helps any.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronfable:
Same thing with me any updates?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skim7x:
I had kind of a weird experience, but wanted to share it for those searching.

Samsung Galaxy S3 AT&T

Rooted

CM 10.1.3-RC2-d2att

Downloaded BusyBox from Playstore and "Updated" to what seemed to be an older version of what was installed on my S3... but I figured I'd just update since it told me to.

Installed Google Wallet Installer V3

Bootloop.

Restored Nandroid Backup that I had made earlier.

Everything working as usual.

Installed Google Wallet Installer V3 (WITHOUT installing BusyBox)

Phone reboots just fine

No Google Wallet app seen.

Phone Info shows "Galaxy Nexus" as phone

Went to PlayStore and installed Google Wallet from Play Store

Google Wallet has Tap to Pay capability!

Opened Google Wallet Installer V3 and restored build prop

Phone restarts

Google Wallet maintains Tap-to-pay functionality

Phone Info shows SAMSUNG-SGH-I747 again, which is the correct model number.

:victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skim7x:
So I tried using Google Wallet today on a vending machine at work. The card reader said "Tapped... waiting for authorization" and then "authorization failed." and would not let me charge my card. I did restore my build prop. Did it fail because I restored my build prop, or is it maybe just the vending machines at work? I'll try another place, but just wondering if anyone else has an idea of what is going on, or if anyone else has had this issue. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaragaki:
Same thing happened to me. Then I tried to re-install CWM and do a restore, but when I rebooted, it locked at the Samsung logo. I had to reload JB with Odin to get working again. And still can't install CWM without it locking up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
If you flashed back with Odin I don't understand why you wouldn't be able to flash CWM... I've never heard of this happening before. Did you have busy box installed out of curiosity?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
**Sorry, didn't mean to add an extra post.**
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaragaki:
My steps:

1. Installed Busy Box. 2. Downloaded and ran Google Wallet Installer. 3. System rebooted into CWM (not TWRP). 4. Tried to restart system. Locked on Galaxy logo. 5. Download mode reinstalled JB with Odin. 6. Reflashed CWM. 7. Tried to restart system. Locked on Galaxy logo. Rinse, Repeat.

So I have a working phone, but I can't reboot it. CWM was working just prior to this.

Any suggestions are welcome. I hope you can resolve the issue; it's a worthwhile effort. And worth the $.$$ if it's working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
I'm really sorry you're having issues, I've had no reports of this happening, but I'll work with you as much as I can to solve your issue. If you can get your system booted back up I think I have a fix for you. If you have terminal emulator we can rewrite your recovery manually with dd. Sound good?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MasterDecker:
I think I know the issue. Get your phone to boot up, install goomanager and install TWRP. His program installs TWRP, and your using CWM. There appears to be a conflict with CWM wanting to be the recovery, instead of letting TWRP do it. Once you have it installed and running then you can reload CWM if your so inclined.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Thanks for the info MasterDecker. I use a VZW S3, so all I can use as input is responses from users who have your carriers model. While not many have had problems, I can't possibly know all the little quirks of the other models. Thank you for giving me some insight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
You'll have to do what I did cuz had the same issue. Download the twrp recovery img and rename it recoverytwrp.img (for easy to remember purposes). Also, turn off stupid auto correct lol.

Download terminal emulator from the market.

Open terminal emulator and type su then hit enter.

Then type dd(space)if=/sdcard/(location of img file)/recoverytwrp.img(space)of=/dev/block/mmcblk0p18 then hit enter.

You should see a couple of lines pop up that say bytes in bytes out. Then type exit and hit enter, then type exit and hit enter again. Just put a space, not the word in between dd and if and between the recoverytwrp.img and of.

Sent from my Black Jelly I747 by graffixnyc theme by wanam ported and tweaked by David Dee ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
I'll look into a fix for some of your phone's problems today. I write to the recovery using the same method highlighted above, so I'm not sure why on some it's not sticking.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] njinstantkarma:
twrp

New verison of twrp is availiable at this link

http://xdaforums.com/showthread.php?t=1793224&page=29

its 2.3.2.3 is it ok to install this new recovery then install your app.... or should I install your app and recovery then flash the newest twrp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MasterDecker:
Your quite welcome. Also please as noted previously have busy box installed BEFORE running the app. This will save a lot of problems in the long run.

---------- Post added at 10:29 AM ---------- Previous post was at 10:05 AM ----------

You should be fine with installing the latest TWRP recovery, then running the app. From what I was able to look at, the app looks to see if you have TWRP installed, if you don't, then it installs it for you, but if you do, then it bypasses that, and continues with the install.

I can tell you that as of this morning, running back with my original build prop, and using Google Wallet, I made 2 purchases this morning, and both worked flawless.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Glad to hear it's working for you! Like I said, there aren't many issue reports. It's usually the user's mistake, but I fully understand that custom Roms and mods don't always play nice. I tried to make the app as conservative as possible, so we'll see how this all turns out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] will900:
Thanks for this app it worked great, just had to install busy box first. I wanted to install Google wallet for some time now but it seemed like it was work to get to work but with this app it was so easy. Going to test it out when i go to the store :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Great to hear! If all works out okay, may I ask for a review on the Play Store? A lot of people are buying it, but none are leaving reviews lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MasterDecker:
Sure, I can do that. $49.95

I'll post it up tonight when I get home.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] will900:
I just put a review on the play store:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Haha I don't know about the $50, but a review would be nice lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Thank you : ) I really appreciate that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaragaki:
Thanks for the replies. I'll try this and Phoneguy589's suggestion when I get home.

Sorry to start the conversation and then duck out. Work you know... I'll report back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
It's fine! Hope all works out okay.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaragaki:
This worked!! Phew! Back to square one and will try the new script. Thanks MD and Prl91. I want to get this working!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
No problem! I think the credit should go to MasterDecker on this one though ; )
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
Sorry, just left a review. Haven't tested it but it installed and I can access my credit cards so so fast so good. :thumbup:

Sent from my Black Jelly I747 by graffixnyc theme by wanam ported and tweaked by David Dee ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Awesome!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Also, just to fill in users following the thread, jaragaki got his Wallet running using the app! Thanks to everyone following my various threads on this, and especially those people providing support to those having technical difficulties.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdmusicman72:
???

How does one get around the "Secure Element Missing" issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
That's the point of the NFC fix in the ICS TouchWiz and JB TouchWiz options. Most of those ROMs don't come with the proper libraries. Did you already use my installer?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shadyguy:
This worked out great! Awesome app :good:

I am going to leave a 5 star review $1.99 well spent.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Awesome! Thanks for the purchase and feedback : )
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gordo1603:
Made a purchase today from a coke machine using wallet and hade no issues!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MasterDecker:
Can't blame a guy for trying.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Great! Glad you're happy with it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
I had to manually edit the device name in my prop for the actual wallet setup to work. Other than that, I'm quite pleased with it. At least the prop restore feature worked :)

I'm running AOKP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Glad it worked! It's odd that it didn't automatically do it, but at least you figured it out!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mspayde:
Ok, I am not able to get any further than the Wallet install. It hangs at the install screen. I have TWRP 2.3.2.3 installed, running the Task & Ktoonsez's AOKP (12/2/12) with Ktoonsez's kernel (12/12/12). I followed the instructions from this post and tried to install twice, clearing the cache prior to each I stag install...with the same result. I looked for the files named Wallet, Recovery, etc. and found nothing. The only thing that I did not do was factory reset and start from scratch, which I will do if necessary. Does anyone have any suggestions?

Thanks for the help to everyone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
It may hang at the Google wallet initialization screen for a while. It did for me at least. Just reboot once, and then let it do it's thing for an hour and then check on it. It shouldn't normally take that long, but I've seen stranger things happen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mspayde:
Following up with a new error message that says phone not ready...See attachedI
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
Manually change your build.prop. There is a thread in the general section about what prop values to change.

Mine did the same thing that yours did.

I am also running the Task & Ktoonsez AOKP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
I would recommend deleting Google Wallet and reinstalling busybox and trying my app again. I would recommend restoring your build.prop before running my app again though. That way your backup isn't overwritten.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Thanks for the input! It sounds like a possible ROM specific issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
If it makes you feel any better about this being a rom specific issue, when I installed Ac!d audio, I had to manually add the build prop lines. The script in the installer had failed there too.

That being said, I'm going to change the rating from 4 stars to 5 :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
That's odd! Thanks for the rating : ) Sorry you had trouble, you're one of the first that has had ROM related issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdmusicman72:
Deleted

---------- Post added at 11:56 PM ---------- Previous post was at 11:52 PM ----------

Yes.. Still getting the error message.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dB Zac:
Yes, I installing busybox cured my issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Did you install busybox first?

**I know I ask that a lot, but out of all 3 threads, that's the most common issue.**
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amendolaro1:
How about some note 2 love
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Maybe! I don't know a thing about the Note 2 besides hardware specs, but I can look into it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MasterDecker:
I'm not worried about it. Just happy that he it got working. The good thing is that now you have a work around for those with CWM installed. Honestly I've found that with CWM, it does not play well with the GS III often. I also found it doesn't play well with the Asus Eee Pad transformer TF101.

I found TWRP, and love it. If I may make a suggestion though, put the work around in the original post, so that others are aware of it prior to buying the app. Might even consider putting it as a requirement prior to install, so that others don't have the same issue. Even though your app auto installs TWRP, having it there prior to installing the app makes it faster to install, and a smoother user experience.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Thanks for the suggestion. I will add a note about it tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] njinstantkarma:
Im also getting the same error running AOKP...

Wallet is unable to proceed until the device is fully initiated. Make sure the phone has network access and try rebooting if the problem persists...

Im not sure exactly how to change the build prop, and On the playstore someone commented that changing the build prop he had to change the device name manually and it worked.... Any idea how I can fix this... any instructions or anyway to implement this into the app so it does it automatically...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Yes. The change of the build.prop works, but there are two ROMs out there that don't let it stick for some reason. The values to edit: ro.product.model=Galaxy Nexus

ro.product.name=yakju

ro.product.device=maguro

Then reboot your device after saving it. I would also recommend making a backup called build.prop.bak
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] njinstantkarma:
I had to change the Model to Galaxy Nexus

the other two entries were already there. Saved it rebooted and everything worked.. Thanks for your help and Thanks for your app best 2.00 Ive spent on the playstore in a while.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
You're welcome! I try to help as much as possible. Out of curiosity, what did the model originally say?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
I had a couple of posts about how to fix this. They are within the last couple of pages.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] njinstantkarma:
The model name was 1747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Okay. I'll cross check that with my app and see what the change in your ROM was.