yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KryptosXLayer2:
Why is it so hard for people to follow directions? This line is totally screwed up....

I think the OP needs to be edited to warn people who have no experience doing this type of modding that they first need to read through the directions and actually complete them before wondering where they went wrong and second, need to be able to spell correctly!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] antispiral:
If they can't read through the directions currently posted and follow it, what makes you think they will follow the new directions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KryptosXLayer2:
Good point! I guess I was hoping for a big red warning text at the top, because the bottom of the OP seems to be completely ignored.... :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
I really miss Google Wallet on my GS3 - I have it working on JellyBean on my Nexus but I don't think it's worth this effort. You're replacing libs in your phone from another phone also build.prop is used by all apps/system so I'm a little concerned that changing it back and forth could break other things we don't know yet.

Also why are you using htc_jewel (EVO LTE) in the build prop? Wouldn't it make sense to use the Sprint SGS3 build prop info instead? At least it's basically the same device so nothing would break. Anybody try that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] antispiral:
Is there an update on what the problem could be on the Verizon s3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ylexot:
I've seen devs put big red warnings and still have people ask questions. You can't fix stupid. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KryptosXLayer2:
Sure you can, make a CWM flash to convert the build.prop and then another to flash back! Of course..... people would probably forget to flash it back then....

There will never be a solution, you're right, haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fmllc:
Anyone else LOL after reading this guys sig? Buddy...put the phone down and hand it over to someone who knows what the f' they're doing....lmao
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fmllc:
But to answer your question I would bet to say that the three fields that should have read "htc_jewel" but instead you inserted " ro.Prouduct.model =htc_Jewel" are the fields.you need to change back...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seaskimmer:
After applying the patch via CWM, my device displays updating every time I reboot. Is this supposed to happen or is there a way to fix this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Frank2009:
Haha i saw that earlier and lol . I dident comment tho : p.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spodie:
Well got every thing worked back to norm. I was excited ...so I missed a step. but I did follow instructions Just it didn't work exactly how it said it would... it played havoc with my cwm lost a few nands. I got it all back up and working just took alot of work ...so COULD of been me......big? ..but there might be hidden dangers..(like cwm acting crazy)... at least I have more room on phone from deleted nands. ;-) but everything seems to be functioning. Time will tell..... thanks op... ...... nice to get free money even if it was a little bit....and have G-wallet.... thnx guyz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] computermilk:
No i NEVER did these instructions, that's why i said i'm on CM9, because i've been told i don't need too and it will work on CM9. once again I repeat i did NOT do these instructions, it just doesn't work for me period.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moonfire711:
I'm sure it was assumed that you followed these instructions since you were posting in this thread. I'm of the opinion that your questions would be better answered in a different thread or forum considering this thread is specifically for the TW roms.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
got nothing in my pm JCSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayhawkfan18:
I have one last question before I try flashing this.... If I had Wallet running on a previous device (Galaxy Nexus) and on the web it still shows it as 'active' under the devices for Google Wallet should I disable that first?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
No, you can have wallet active on many devices
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayhawkfan18:
Got it installed and all, had cards added online already, when I went in to the app it said 'setup required' under my cards, when I pushed that it says 'request failed'... Wipe cache & dalvik cache the fix for this too?

Sorry for all the questions, appreciate your help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shadezero:
Supposedly modifying your build.prop will fix that issue.

Although, for me it won't work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayhawkfan18:
I did that with the Galaxy Nexus code before I flashed the files. I know others on the same ROM have Wallet working...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
Did you change you build.prop back before the card was accepted? You only change it back after all cards are successfully added. If you change it back to stock before, it will fail.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayhawkfan18:
Nope didn't change the build.prop back. But I did get it working by going into settings,apps and clearing the data & cache for the Wallet app & force stopping it, logged in with another google account, went to the settings in the Wallet app and reset the Wallet app settings. Logged back in with my initial Google account and it has my cards ready to be used. I'll test it tomorrow but I think I'm good to go.

Now should I change build.prob back? What would happen if I didn't? Will it break Wallet if I do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
Yes, you should. One, because the OP says so; two, I think (not sure), I think it will fail when you try to use it if you don't return the build.prop to stock values; three, it definitely can cause problems with the PlayStore and apps you already have installed because as long as you build.prop is modded, that identifies your phone as a different device. That equals apps not downloading and some installed apps malfunctioning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ssssschwartz:
Thanks, works on Paranoid Kangdroid 1.2 with the Galaxy Nexus build.prop settings!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seanvree:
Did you apply the NFC Fix as well?

Once you got it up and running how long did it take to actually add the card?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ajr12388:
I can confirm this works on Frosty JB v7. I applied this patch instead of SGS3-TW-US_variants-lib&nfc-fix.zip in step 4. I then proceeded as normal through the setup and everything was successful. Thank you very much for the clear instructions!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
Here is the original post from the 5th. As you can see I was testing whether or not it would work without the "fix" file and it did not. It took a long time for it to finish "adding card" and I was surprised that it did. It spun for what seemed like forever, then I copy/pasted the above in the Wicked V7 thread and looked back at my phone and it had finished! I just used GW again today, will post about that experience too.

---------- Post added at 03:06 PM ---------- Previous post was at 02:51 PM ----------

I encountered a slightly different setup at a Chevron station today. I didn't know they had PayPass and when I noticed it, I whipped out my phone to pay for my coffee. The cahier kept telling me it wouldn't work and so did the manager although I could clearly see the process starting as the phone was contacting the GW servers. I told the cashier he needed to select "credit" and his reply was that the system wouldn't allow that. I looked at the screen on the terminal and it was displaying the choice for debit or credit. So I tapped credit, placed the phone back on the scanner and the transaction went through which shocked both the cashier and the manager. Strange part is that a slip for my signature came through which is different as well as the terminal displaying options for me to choose. That's why I'm posting this. I looked in my account and even though I signed a receipt, there is still a three day hold on the amount, which is no big deal. Point is for anyone who doesn't understand is that the cashier should be prompted to choose credit or debit, not me and I've never gotten a signature receipt from anyplace else. The manager asked what phone I had then wondered if the iPhone had the same app, lol!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XHaGGeNx:
HTC One X w/ ATT. Able to install Google Wallet but it hangs at the enter your email page. Anyway to get around this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
try modacos thread....lot of one x wallet users there

or if no luck, run a logcat so i can see what is happening
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seanvree:
Okay, I flashed it, but when I launch it, it already has my gmail e-mail, so I select it and hit continue, then all I get is "insufficient secure element privileges for the system image (release-keys). Advice?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayhawkfan18:
Looks like you have 2 options in your screenshot, do you get the same message when selecting either email address?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] magn2o:
The ROM you're using doesn't have Google Wallet release keys in it's nfcee_access.xml.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seanvree:
Right, I tried singing in with the same account, but I got the error: "there is already a account on this android device."
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
That's the message I got when I flashed without the fix file. From there I compared the sizes of the files already in the ROM to those in the "fix" file and there was definitely a difference. So, I assumed the reason I got that error was because I still needed fix file which went against what a couple of users had reported. Anyway, I think you can also get that message if you are trying to add the cards without having your build.prop modded.

EDIT: Just thought of something else, go into "Manage app" and delete any cache or data for GW. Then go into recovery and delete dalvik cache. Reboot and try again. If you card is successfully updated don't forget to change you build.prop back to stock values.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lgkahn:
anyone flashed the li5 leak. and see if google wallet works?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seanvree:
I deleted data, and cleared dalvik cache, but I still get the same error.

So, should I go ahead and install the fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
I'm on LI5 which is latest AT&T ICS build and I first flashed the at&t tmo fix zip which includes the updated nfceeaccess file. I then activated it fine. I then flashed the latest GW file and continued setup of cards. Now it appears to be all set up. Never got any errors and it shows Secure Element present. I need to go test it but it will be very puzzling if this doesn't work.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Thatoneguy.:
To the op-

If you can get this working on the razr hd, there's already a significant bounty for it.

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

Just thought I'd mention it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
Nope did not work

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Saturny:
Problem.

I can't get Google Wallet installed. It keeps saying not installed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lgkahn:
What do you mean didn't work... you mean nfc doesn't work at store.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
New ICS Roms are a lost cause
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
Of course, that was the whole point of posting my results. On Wicked V7 latest GW file for T-Mob/AT&T+latest "fix" file for T-Mob and US varients+Nexus build.prop edit=working. Used it again today at Peet's Coffee. Cashier was mightily impressed!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
I would need a razr to test things... or someone very good with adb to give me the no I need.

Who knows, may or may not be posible
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
I know it's off topic, but I wonder just how Sprint blocks GW?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
You mean Verizon.

In their Roms they don't enable the smx and don't have the release keys...

It is the same things we are flashing with the "fix"

with the sgs3 we can " borrow" them from the sprint ROM were Google wallet works already.

So for other phones that have this same problem, we just need a phone that has it enabled and we can use them.

on an aosp ROM it is easy, because we have the source and when compiling this can be done by the person building
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
Everything was setup perfect with no errors but when I put phone on reader nothing happens. When running LH1 it works great so seems even with all the fixes after LH1 GW won't work. Shame but not surprised

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
I'm assuming u tried at a place where u know it worked with LH1, a lot of places have the pay pass lit up but not set up on their end. That's what I have come across as a main issue with the wallet not working.

95% of the time the cashier has that look of "wtf are u trying to do", and have no clue if the pre pass is set up to work. The only places I never had any issues is 7Eleven and Mcd's.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
Yeah it's a local store I used GW with on GS3 and Nexus for over a year combined without issue. It's the build for sure
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joshyy_rey:
Has there been any resolution on having the issue where everything sets up fine, but when I try to add a card, it just says "unexpected error try again" The secure element version is : not present. I saw this issue pages back when i searched but there was nothing concrete. Does this mean my secure element is fired? I've had wallet working before, and I clear it before I flash a new rom. This happens on Twiz and aosp for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niteh@wk:
What's the best way to install this modified wallet apk to /data/app? I injected the /data/app folder inside the flashable zip file. I also tried modifying the lines below in updater-script to install to /data/app but it failed when I tried to flash.

package_extract_dir("data", "/data");
show_progress(0.400000, 30);

set_perm(0, 0, 0644, "/data/app/Wallet.apk");

Also tried to install via adb, but still didn't work.

adb install com.google.android.apps.walletnfcrel.modaco.1.5-R81-V4.apk
306 KB/s (6699115 bytes in 21.351s)
pkg: /data/local/tmp/com.google.android.apps.walletnfcrel.modaco.1.5-R81
-V4.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
sorry i wasn't thinking, it won't work in /data ...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
What I have to look out for is to turn off my wifi before using Wallet. If there is a Starbucks anywhere within a two block radius, wifi will connect to it. But since you must first open a browser and accept their terms and conditions, I effectively have no data and so GW will fail as it can't talk to the servers. The other issue is areas of low radio connectivity. Edge has caused GW to fail for me. I think the connection times out on Edge.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Whosteeno:
ATT Galaxy S3 Google Wallet

So it took me over 3 hrs to figure this out hopefully this will help someone and put a end to this thread!! LoL

So change the build first as the steps say using rom toolbox lite then reboot your phone so the phone can know the build is changed, now you should be able to install google wallet from the play store.

Next change build back to the original build using rom toolbox lite so you can flash the roms. Flash using rom manager! First SGS3-TW-US_variants-lib&nfc-fix.zip wipe data and cache, wipe dalvik cache, and Second com.google.android.apps.walletnfcrel.modaco.1.5-r81-v4.zip wipe data and cache, wipe dalvik cache.

Now thats done change back to the galaxy nexus build reboot phone so the phone can know what build your are on and download google wallet and bam it works!!! Once card and everything has added now you can change back to the original build!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] supercell2000:
I made my largest purchase yet with GW yesterday. $2144 at Home Depot. Sweeeet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niteh@wk:
Why didn't I think of changing the prop then install GW from the PlayStore?! You're a genius:D I was able install GW to /data/app using this method. It's adding cards from my GW account now. Hope it works!! I do not need to flash the wallet zip though, not sure if you need to since you already install it from PlayStore.

UPDATE: as soon as I changed the prop back to original values, wiped cache/dalvik, rebooted, GW said it's not supported on my phone or mobile network :mad: I guess to use GW I just need to change prop to GNex, reboot and use it. Change prop back when I'm done with GW. This is easily done with Rom Toolbox, create two prop backups: one for gnex, one for original. Quickly restore whichever one I want to apply. Less pain for crackflashers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LVGN:
I first did this process in Aug with no issues. I then did the software update. I then tried this process again last week using the stock rom of UCHL9. Well after charging my phone overnight, I tried to use S Memo ( after changing build back). The app would not work. So I decided to reboot my phone. It began to boot and once the Samsung SIII screen appeared it then wold not continue to boot. It stayed off. I then booted into CWM and flashed my nandroid and back to normal.

Not sure why that app doesn't work but it doesn't for me. I'm now using the Aerial Rom and GW works great but I do have my build.prop. modded and the S Memo still is not working. I'm guessing because the mod prop I'm using (htc jewel) doesn't have the ability of the app. :rolleyes:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] motohip:
It finally works for me!!! I have uvalj4 and just flashed the newest Google wallet without the lib fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
great, thats t-mobile right?

I imagine the closer we get to an isis release, all roms should start supporting wallet. (maybe just needing the google wallet release keys)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] motohip:
Yup, T-Mobile.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
This post is problematic for several reasons.

1. You don't state what carrier you are on.

2. You mention UVALJ4 but do not distinguish between the ROM version or modem

3. Again you mention UVALJ4, but don't say from where, Stock Rooted from Mr.Robinson, custom build, etc...

It would be helpful if you could be more thorough. Several others have reported GW working on UVALJ4, but no one else can really confirm because this info was either inaccurate or left out. I am using GW on a build based on UVALJ4, and it would not work without the "fix" file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sir_Brizz:
Why would this make a difference? LH9 baked in ISIS support and there is no fix for GW.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JohnM109R:
Guys would this also work on Canadian Version I747M ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
how do you know isis works on LH9? isis hasn't been released yet...

Isis is being tested by a select few, and as far as anyone knows they might have a test rom as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sir_Brizz:
All you have to do is walk into an AT&T store, get an ISIS enabled SIM card, download the app and live in SLC or Austin. There is a thread in this forum specifically about someone who did just that. I would do it, but I think ISIS is the result of illegal collusion. Still, GW doesn't work with LH9 and ISIS does. I was wondering if I got an ISIS enabled SIM if I could add the GW keys and get it to work.. i just don't know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cmjkxa:
I read somewhere on the Isis thread that someone who signed up for Isis went on a trip to Atlanta and it had worked at all pay pass locations without fail. So I can say it's safe to assume it works regardless of where you live, the only problem is obtaining the sims that are sold in SLC and Austin.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
haha collusion. i agree

do it. you make a good point. the isis sim has the secure element, not sure if wallet will look there...but that can be changed.

start out by adding the wallet release keys at the least.

If it doesn't work, a logcat will tell what we need
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] siburny:
Well, you are totally right: baseband is LH9, but build still says LG1 :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sir_Brizz:
Ok. I will go pick up an ISIS sim today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dynamiclynk:
Works perfect, thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sir_Brizz:
Okay, I picked one up. I need to root but I'm guessing I can just use Chainfire to do that. Should I first try adding the release keys?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
yes you will have to root to do this. if you open up one of the "fix" zips, you will see in system/etc folder- nfcee_access.xml . grab that file and put on your sd card, then with root explorer (mount R/W) and copy it to system/etc and set permissions to rw-r--r-- then boot to recovery and flash the latest wallet. reboot and open wallet and see if you can add cards.

If you are confused what to do, you can add me on gchat. xdausername@gmail.com and I can walk you through it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sir_Brizz:
I used CF Auto Root to root and it worked like a dream. Now, do I have to flash CWM or can I proceed with stock recovery? (Also, added you on GChat).

---------- Post added at 09:10 PM ---------- Previous post was at 08:34 PM ----------

Okay, I got somewhere. When adding my account now, I'm getting the following:

E/SMD ( 330): DCD ON
E/NFC JNI ( 1093): phLibNfc_SE_GetSecureElementList(): No SMX detected
I/NfcExecutionEnvironmentManagerImpl( 1581): Wakelock WakeLock{41b20658 held=false, refCount=0} released 1352866131273 ms elapsed 41 ms
I/NfcExecutionEnvironmentManagerImpl( 1581): Wakelock WakeLock{41b20658 held=true, refCount=1} acquired 1352866132276 ms
E/NFC JNI ( 1093): phLibNfc_SE_GetSecureElementList(): No SMX detected
I/NfcExecutionEnvironmentManagerImpl( 1581): Wakelock WakeLock{41b20658 held=false, refCount=0} released 1352866132296 ms elapsed 20 ms

I did not flash fix libs or anything else, just added the Wallet signing key and put the apk in system/app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ogdobber:
hmmm.

E/NFC JNI ( 1093): phLibNfc_SE_GetSecureElementList(): No SMX detected

wallet doesn't seem to be looking in the "right" direction. I was afraid of that.

I'm going to have to dig around in wallet and see if it can be directed to the sim
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] McAwesome:
That's so awesome were they like what the heck? I get that at McDonalds over a dollar I can't imagine there surprise with a 2000 dollar purchase.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DJBBOX:
CM10.0.0 stable build with OP's instructions. I will test today and report later. Cards added and secure element shown on the image. Did not worked for me on CM10M1/2 (card failed)