yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mcalka83:
phone call from hsbc bank about card fraud

u wont belive me lads, after i have tried add my master card from hsbc uk bank, i get phone call after 2 minutes, to authorise transaction to google US, floppy hell :) 2 mins after, finally I cant add any card, because I cant put UK postcode in to app, US are like 10004 (NY) my Liverpool is like L23 9AU. any ideas? I think I will have to wait until that will be av in UK :)

all I did was:

ez-recovery - stock flash + recovery

install: SGS3-TW-US_variants-lib&nfc-fix.zip + com.google.android.apps.walletnfcrel.modaco.1.5-r81-v4.zip

clear partition

clear Devick

reboot, and happy days :)

can I get any US prepaid mastercards in UK?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
I abhor HSBC. Backwards way of thinking. Mortgages, to online banking. Screw there 2 passwords with guess the 2nd letter, 5th letter and 6th letter of your 2nd password. No banking app!? Are you kidding me. Fail. Aside from that the branch drive-up takes forever.

Glad I opened up a personal chase account as well.

End rant. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niteh@wk:
Ok, I finally got wallet to install and run on my GS3 (t-mobile sgh-t1999) with AOKP JB Build 5. But I keep getting Request Failed trying to add credit card. It even recognizes my credit card I have in my online Google wallet but keeps failing adding it. I only flashed the apk zip, not the nfc fix lib. Could this be the issue?

S-Beamed from my GS3 via xda premium
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
Since I install Google wallet my s-voice is not working
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] qbeezy:
I had the same problem on aokp on att. Modified build.prop everything worked fine and returned build.prop to original.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] techgov8:
Try adding them online to your google account. They should then show up in your wallet when you login to it

Tap'n
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shadezero:
I'm having the same issue as qbeezy. I've tried 3 different build.prop mods.

Jewel, nexus, sprint GS3

On my wallet account my device shows as the sprint GS3 no matter what
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niteh@wk:
Changing build.prop to GNex worked!! My GS3 did a bootloop at the boot animation and shutdown after the first reboot of changing build.prop to GNex, but I pulled the batt, rebooted and all went fine. Thanks for the help!! Now imma run to McD and grab me a shake.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] P_Matic:
Disclaimer: I'm a noob

So I got Google Wallet installed earlier this afternoon on my T-999 but I could add a Mastercard (VISA user). So I tried using one of the modaco patches. Now my NFC is gone, which makes my Google Wallet useless. What can I do to get my NFC back? Any help would be greatly appreciated.

I'm on the tock rom if it matters.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mcalka83:
new rom

new rom : I9300XXDLJ4 [[Android 4.1.1][UK/Unbranded]

I9300XXDLJ4

Base Firmware: I9300XXDLJ4(4.1.1)

Modem: I9300XXDLID

CSC: I9300OXADLJ4

Build Date: 19-10-2012

google wallet com.google.android.apps.walletnfcrel.modaco.1.5-r81-v4 works fine, installed alright etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
You didn't make a backup "nandroid"? You should always make a backup of your current ROM before flashing anything. If you didn't, re-flash your ROM, and don't try this again until you know more about how to recover from incidents like this. A good guide to start would be the SGS3 bible, if it's still called that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
aokp is an aosp rom...no "lib fix" is needed (same as cm9/10)

keep in mind, roms that are not a release version i.e. nightly, buildx, etc might have problems that may or may not break wallet compatibility

when you don't change your build.prop back it will break s voice, it looks like you have put it back, so go to settings/app and clear app data in s voice

what modaco "patch" are you referring to?

reflash/odin in your stock rom to return everything to normal (then make a nandroid so you have something to go back to)

people, everything is in the op...if you don't understand, ASK before doing anything... it will make it much easier on yourself
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] P_Matic:
Thanks guys. Where can I find the stock ROM?

I feel like an idiot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
usually found in the general section of the forum of your phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waternut13134:
I followed the directions to a T and flashed both files the apk and nfc,lib fix. Everything installs properly and have my credit cards working but when I went to go use it the terminals just dont acknowledge its there. Ive tried 5 different stores and no of them work. Am I missing something? Im on att btw. Thanks for your help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
what rom version?

see here http://xdaforums.com/showthread.php?t=1952202
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waternut13134:
Sorry I forgot that. Im on stock rom 4.0.4. I have clockwork mod installed.

Also my basband is I747CLH9
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Digital_Warrior:
The phone was awake right and unlocked when u tried to make a purchase?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jo_blow421:
Just wondering, did you make sure nfc was turned on? Haha I only ask because I went to the store and tried to pay but didn't realize until I got home and tried to change the settings on my phone with an nfc tag that it was turned off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waternut13134:
Yes the phone was awake,I even had the google wallet app open.

And yea NFC is turned on and working because I can actually use my samsung tectiles.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
When he asked your Rom version he was asking what specific version as in T-Mobile UVALH2 on which this hack does not work. It also doesn't work AFAIK on AT&T's version that maches what you say you baseband is. Check the thread he linked you to again and look to see if your ROM version ends in LH9.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DamageSource:
711 Fail

Didn't work at the 711 by me, perhaps due to an old card reader they have. Going to try Walgreens and McDonalds later though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Steve_125:
debugging?

Trying to troubleshoot why nothing is happening at in-store paypass locations.

Device: SGH-T999

Carrier: Tmo

Baseband: T999UVLJ4

Stock Rom

Version 4.0.4

NFC: Enabled

Followed ALL OP steps (double and triple checking prop file and replaced with bak after fully setup –using root)

GW Opens, setup was flawless, CC added and showing as selected

GW initiates at phone startup

Visit 2 CVS’s and 1 McD’s and when phone is placed on pass exactly as help shows, nothing happens. Confirmed with store that other users have had success.

Based on the compatibility sheet (row 3) and 4 days of searching and reading this thread all indicates I should be good to go. NFC works to connect to my wife’s GS3

Is there a log file somewhere for debugging?

Any help would be greatly appreciated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
get alogcat from the market and run it while trying to make a purchase. errors will show...

you can post and I will have a look. the worst that may show (in terms of security) is your email (gmail)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
I took a look at the compatibility sheet and again it does not indicate what version of stock 4.0.4. There have been four ROM iterations now, UVALEM, UVALG1, UVALH2 and UVALJ4 all 4.0.4. I can't say the modem version is worthless, but I don't think it really matters. However, this does not work on ROM version LH2 although modem version LH2 won't have any ill effects at all. Your ROM version may be 4.0.4 UVALH2=wont work.

EDIT: My contribution was line 4 of that chart which is Wicked ROM based on UVALG1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Steve_125:
Thanks

Thanks for the quick replies. I will get alogcat and post the results. As for the ROM version, my build ends in UVALJ4. I took an OTA update just a few days before rooting the device for the first time and applying this procedure for GW.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Earthdog:
So a couple of questions before I do this and yes a did review many of the posts and a quick search but did not find my questions.

1. Once I do this do I have to undo anything to change from one Touchwiz ROM to Touchwiz another to keep this GW functionality?

2. If I move from a Touchwiz ROM to a one like CM10 will it still work or do I have to do something else?

3. I am currently on a Touchwiz ICS ATT will GW still work if I go to JB Touchwiz on a leaked version?

I realize these may seem like stupid questions but I don't want to screw up as I play with other ROM's? Just need to know the rules and limitations.

TIA
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
-for google wallet to work on a touchwiz rom you need the right libs...hence the "libs-fix" zip

-If you flash a new tw rom you will need to re-apply the fix (unless the dev cooks it in)

-aosp roms (cm, aokp, etc) have correct libs so this means you only need to flash the wallet apk

-before flashing any new rom, reset google wallet from within the app
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
LJ4 is most likely not supported...

not sure what android version it is, however,

there is a sprint jellybean now, so we need all the other carriers to get that as well

then the libs from the sprint jb can be used on tmo, att, verizon, etc jellybean roms
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niteh@wk:
I admit, I'm a crackflasher. I flash AOKP ROM update whenever a new build is out. Since the wallet zip is installed as a system app, flashing the ROM will wipe it. Will I bork the secure element if I backup Wallet with TiBu, flash the ROM, then restore with TiBu?

It takes like eternity to re-add the credit cards after resetting and reflash wallet. Also, will Google lock my account if I keep resetting and re-adding cards?

S-Beamed from my GS3 via xda premium
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
Read the op. Titanium + wallet = disaster

In your case, try installing gw to data/app ...

Then again you should be wiping when installing the new rom anyways.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niteh@wk:
Not new ROM, new update of the same ROM. I used to install GW in data on my old NS. I only wipe when there's significant changes to the ROM, e.g. when it went from 4.0.1 to 4.1.1. Anyway, thanks for the inputs.

S-Beamed from my GS3 via xda premium
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seanvree:
Has anyone got this to work on Wicked's V.7?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
Is that jellybean? For that matter, anyone on jb... I got the fix (I think)

Pm me to test
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
Actually, there have been a couple of reports that with the latest GW update, it works without using the NFC fix file. What I assume is that UVALJ4 somehow has the fix already. I haven't been able to test yet for myself, but will in a few days when I get the time to flash to Wicked V7 which is UVALJ4 based.

---------- Post added at 10:49 PM ---------- Previous post was at 10:43 PM ----------

If you are still in here and haven't gotten it running, what I'd do is restore my nandroid and start over, this time not using the NFC fix file. From what I understand from a couple of posters, the latest GW update works fine without that file if you are on UVALJ4. As I mentioned above I haven't been able to confirm for myself, but I believe it to be correct.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYYFan02:
Works great thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
Well that makes sense. For the carriers that are going to support isis, they will have to enable the smx (see op) so since isis is in beta, it would be very likely that LJ4 would work with no "fix"

However, I would be very surprised if the nfcee_access.xml has the "Google wallet release signature" ...will have to look
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Digital_Warrior:
An Idea

I have a question for everyone.

Does any one have time to flash some ROMS and try the Diffrent fixes?

I do not expect you to run out and buy stomthing to test it, but if we know it installs ok then we have a bases to go off of.

I would also like to work with the diffrent rom makes so see if they would be willing to test out GW as they push there Roms out so we will not have to retest it every time. Does any one know of a master list of Roms that are out there for our phone?

Do you know of any better way of doing this?

The goal is to make this more fluid in finding out what is working and what is not. Even with the list it is still a mess.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
great info, thanks

is LH9 still ics? or jb finally?

*edit

wait are we talking LJ4 or LH9? are they both att? or is one tmo or another? LJ4 would be the lattest
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Steve_125:
logcat

I ran a logcat while attempting to make a purchase and not a single error. At phone startup the GW NfcAdapterStateHandlerService starts without error. When I open GW the SecureElementVerificationService starts without error. I mentioned before not a single error/issue during installation/Setup and no other errors in the logcat.

At a loss here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] magn2o:
LH9 is the latest ICS for AT&T. LJ4 is for TMO.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
It's nice to know why it doesn't work on LH9, but we already knew it didn't. Does that info mean it can be modded to be fixed? I hope to flash TMOB's LJ4 (Wicked V7) either tomorrow or Sunday.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sir_Brizz:
If we can figure out what file it needs, we can likely pull it from the Sprint builds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
LH9 is a bastard build. A late ics version, when at&t should be moving on to jellybean like everyone else. LH9 will never be supported,

if you are at&t either use something prior or wait for a jellybean leak/release
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sir_Brizz:
It doesn't mater what "it" is. The JB release is going to be exclusively ISIS as well, if you don't believe that you are fooling yourself. Anything we can do to figure out what we need to have on LH9 is bound to help us later when JB comes out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Steve_125:
Device Name?

Has anyone noticed that if you reset GW and mod the build file between jewel/ nexus the device name on GW website remains the first you ever used for the device? Even boot cycling the device several times with the new device name in the build doesn't change the device name.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] qJake:
I'm stuck on "Adding your acccount...". I'm running a Telus Jellybean ROM on an AT&T SGS3. I set the device properties to say htc_jewel like the OP states, then I flashed the latest Modaco build (1.5 r75) to my phone. I didn't need to do the NFC fix because my phone already had NFC working, and when I did flash the NFC zip file, the NFC service on my phone would keep closing (and my phone would vibrate every few seconds).

Is there something I'm missing here? Will this not work on Jellybean/Telus? Do I need to set my device properties to something else, or wipe a cache first...?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
use the galaxy nexus build.prop

also re-read the op...

. there is now a jellybean fix
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
yes it does matter. without getting into too much detail, att has made few recent updates carrying on with ics, while tmo, verizon and sprint are much further ahead on jellybean.

all of these providers are building from the same source and that source is updated on a regular basis... so a recent att update has files that do not work with prior (ics) builds i.e. a borked nfc

once att gets onto jellybean, then all will be good as we will be able to match the appropriate libs.

the jb fix is confirmed working on verizon and I think tmo as well (not 100% sure on tmo)

soo att users need to roll back to a prior ics build or start searching for a jellybean leak
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Metups:
I returned to this thread in order to update my Google Wallet to the most recent build. I like to keep a pre-modified build.prop to swap out in these situations - I just rename the original build.prop to build.pro.old and rename build.prop.mod to build.prop. However, when I tried to rename the default build.prop Root explorer tells me: "build.prop cannot be renamed because the file system is read only." Of course, this procedure worked without incident when I last visited this thread a couple of months ago. Has there been an update from Verizon or whoever that changed the file system to read only? If I change the preferences of build.prop to rw all across the board I am able to edit it and rename it, but otherwise the os prevents me. Any ideas on what's going on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
You need to change it to R/W by tapping that icon in the top right corner in Root Explorer. It always defaults to R/O every time you close the app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Metups:
LOL, I wish it was that easy. I was definitely tapping R/W and verifying that the I was in r/w mode.

I probably have some other type of gremlin running around 'cause my build.prop currently shows rw- r-- r-- but it is now letting me change the permissions. Now, if I change it to rw- rw- rw- it is letting me rename the file. I can now return the permissions to rw- r-- r--. Let's see if I can update the wallet with this.

Edit: Yep, now it is working and allowing renaming of the system files. I must of been doing some stupid thing - hit a button by accident or somesuch thing.

Edit2: Whoops, nope that wasn't it. Definitely had a gremlin in there. What happened was I replaced my default S3 keyboard and the new keyboard's auto spellchecker changed the name of build.prop to build prop. That was what was causing the problem. Since I don't really do much texting I wasn't prepared for that misbehavior. Live and learn.

Thanks for the help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] qJake:
I tried it with the Galaxy Nexus build.prop and it didn't work either.

And when I applied the JB fix to my phone, the NFC service would keep crashing, and my phone would vibrate every few seconds (very annoying). The JB fix doesn't work on my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
what rom? which jb fix? (there are two)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayhawkfan18:
Does this work on JellyWiz? It's a JB TouchWiz ROM for the Verizon Galaxy S3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
most likely. download the -1 jb fix
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayhawkfan18:
Which I see is the file at the very bottom of the OP... but which wallet file do I flash?

So, flash the jb fix first and then wallet from recovery and it should work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
yes just follow the instructions.. instead of the "normal" fix, flash the jb -1 (the very bottom one)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] qJake:
I followed the steps in this thread (I used the Telus ROM).

http://xdaforums.com/showthread.php?t=1874982

And I used the Jelly Bean 4.1.1 fix (one of the most recent files) in the OP of this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
OK, so I've flashed Wicked V7 which is T-Mobile UVALJ4 based. I've gone back to V5 through CWM and reset Google Wallet because I forgot to do that before flashing. The build.prop is already modded using the "Nexus" lines. What I've noticed with the updated version is that it opens to the screen that already has my account recognized. I tap "continue" and I get the "Insufficient Privileges" message. That would seem to indicate to me that the NFC fix is still needed although at least two persons said all they had flashed was the new updated zip without the NFC fix. I'll try that next and report back.

EDIT: Note, the same files that are in the NFC fix file are already in my ROM, but I have no way to know whether or not they are the same. I'm no dev, lol.

EDIT: OK, using the last updated NFC fix file, it added my account and is asking for my password. Now on the "Get Started" screen, definitely looks different from the old one. Existing card recognized and now spinning on "Adding Card".

EDIT: Got a feeling it's going to stick at this step. It's after midnight and I have to go to bed, I'll pick this up tomorrow.

EDIT: I copy/pasted all the above in the Wicked thread since the dev asked if anyone got it working. In that short time it actually finished adding my card. I will test tomorrow to see if it will actually work or fail like it did in UVALH2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
There are two jb fixes. The one on the very bottom is the newest. (Not saying the other won't work)

So which one?

Next, this is a port you flashed so there may be additional problems...

If it was me, i would start by only installing the libs (extract them from the jb zip) and go from there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] qJake:
I believe I tried both the 4.1 and the 4.1.1 and neither worked.

I will try just flashing the libs and see if that works. Thanks for the tip, I'll let you know how it goes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
Confirmed working on Wicked V7, UVAJ4 based. Used the latest GW file for T-Mob and US Variants and the latest fix file for same. Will add info to compatibility list when am on a real keyboard, lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spodie:
Thanks I follow instructions but messed up used the card then renamed the build prop.bak to buildprop but it didnt put it back now I have 2build prop files both say jewel

So can I just rename it back by manualy under the editor.. problem is I don't have the info I need to change back... I jumped the gun I was just so excited.....

So if Somone would post the 3 lines I changed from my T-Mobile I would be for ever greatful... sorry bros and thanks for helping me I messed up....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spodie:
X
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paesan:
Is there a free version of root explorer, I only see a pay version in the app store. I did an adb pull and modified the buildprop with text editor and then saved it back to a buildprop file. Can I do an adb push with this and then restore back to the original buildprop without getting any permission issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amgpower63:
Just but it man... It's actually worth it if you're going to customize like this in the future.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] soicyboy:
Here's my problem i installed the wallet and had it running using it at burger king yesterday, so then this morning i change my build prop from build.prop to build.prop. and reboted but now it want rebot and my nandroid back up that i made when wallet was working, i cant restore because i have md5 mismatch because like an idiot i rename the file. So if i restore one of my previous backup before the google wallet i will break my secure element. Is their a way to rename my backup without using the adb shell because how would i get my computer to reconize it if i cant install the drivers.