Google wallet fix for SGS3 US variants AT&T, T-MOBILE, US Cellular, VERIZON, etc

Search This thread

firefreak664

Senior Member
Oct 1, 2010
188
73
Re: Google wallet fix for SGS3 US variants AT&T, T-MOBILE, US Cellular, VERIZON, etc

Did you reset GW from within inside the app?

Sent from my SGH-I747 using Tapatalk 2

---------- Post added at 08:04 AM ---------- Previous post was at 08:02 AM ----------

Its only a couple of extra steps during the wiping and install process. It should take you one extra minute

Sent from my SGH-I747 using Tapatalk 2

Thanks I just reinstalled it BTW on the new app how can we tell it has the secure setting right.
 

TheIowaKid

Senior Member
Feb 5, 2011
191
13
Re: Google wallet fix for SGS3 US variants AT&T, T-MOBILE, US Cellular, VERIZON, etc

I took the gapps package that I flash with AOSP based roms and added the latest Wallet to it with 7zip. Now, everytime I do an update (I'm currently using Task's AOKP), I flash gapps and wallet is still there and still set up. It has worked flawlessly and I have made purchases with it as well.

Edit: It figures, as soon as I hit post I realized that my setup wouldn't work with trying new roms. It only allows Wallet to survive an update. My bad

But wait, so at this point all you would need to do is edit build prop and go through the setup? That's not so bad. Its one less recovery reboot at least. Right?

Sent from the future on a Nexus device
 

1Shotwonder

Senior Member
Jul 21, 2009
159
29
Kissimmee
Re: Google wallet fix for SGS3 US variants AT&T, T-MOBILE, US Cellular, VERIZON, etc

Well I wasnt able to successfully setup wallet on my current rom wicked v6 idk if I have an issue with my phone personally but does anyone have a confirmed working wallet on wicked v6?

When I have time to I will restore to the rom I can get gw working and do a complete new install of the wicked v6 from that point where I have a working google wallet which is on freegs3 rom


Sent from my SGH-T999 using xda app-developers app
 

RaymondPJR

Senior Member
Oct 7, 2010
5,805
1,246
Portland
As much as I like using wallet i also like trying new ROMS. it's just too much hassle if I have to go through this whole install procedure every time I flash a new one
!

Sent from my SGH-I747 using xda premium

I felt that way too at first, but then I just put the pertinent files in a folder on my extSDcard (I always stay with Samsung based ROMs), including a saved copy of the modded build.prop. That means all I have to do is remember to reset GW before I flash a new ROM. When new ROM is flashed it's a cinch to reinstall GW!:good:

---------- Post added at 05:23 PM ---------- Previous post was at 05:17 PM ----------

Well I wasnt able to successfully setup wallet on my current rom wicked v6 idk if I have an issue with my phone personally but does anyone have a confirmed working wallet on wicked v6?

When I have time to I will restore to the rom I can get gw working and do a complete new install of the wicked v6 from that point where I have a working google wallet which is on freegs3 rom.

Sent from my SGH-T999 using xda app-developers app
I ran Wicked V6 forever with GW installed. You must have done something wrong. I was running the file that eded in 87 plus the latest "fix" file and the Nexus build.prop edit. Make sure you don't have your Playstore set to auto-update. If you do change that setting beforehand or freeze Playstore. You can reverse this after you change your build.prop back after successfully adding your card/s.
 

1Shotwonder

Senior Member
Jul 21, 2009
159
29
Kissimmee
Re: Google wallet fix for SGS3 US variants AT&T, T-MOBILE, US Cellular, VERIZON, etc

I was running the 4.1.-1 fix file is there a newer file than that? I didnt have the gw on auto update I checked it after seeing some issues with that from others. I have had wallet installed before as I said on freegs3 and if I restore back to that rom I'm on v87 and all I have to do is change build.prop and log in, cards setup quick and then change back buil.prop and works perfectly. As soon as I restore to my current rom change build.prop and flash that 4.1.-1 fix file and new gw app I can get logged in but the adding cards takes forever then eventually fails says error adding cards reboot phone or try again later so thays why I'm wondering if maybe my secure element is fine back in the gs3 rom but now in the v6 somewhere between the two roms something went wrong so maybe I need to go back and start from that backup

Sent from my SGH-T999 using xda app-developers app
 

RaymondPJR

Senior Member
Oct 7, 2010
5,805
1,246
Portland
I was running the 4.1.-1 fix file is there a newer file than that? I didnt have the gw on auto update I checked it after seeing some issues with that from others. I have had wallet installed before as I said on freegs3 and if I restore back to that rom I'm on v87 and all I have to do is change build.prop and log in, cards setup quick and then change back buil.prop and works perfectly. As soon as I restore to my current rom change build.prop and flash that 4.1.-1 fix file and new gw app I can get logged in but the adding cards takes forever then eventually fails says error adding cards reboot phone or try again later so thays why I'm wondering if maybe my secure element is fine back in the gs3 rom but now in the v6 somewhere between the two roms something went wrong so maybe I need to go back and start from that backup

Sent from my SGH-T999 using xda app-developers app
I don't know what else to tell you. All I did was reset GW before I left Wicked V5 (open the app, go into settings and reset). Flashed V6 and set up phone. Later on I modded the build.prop then went into recovery and flashed 4.1.-1 fix file and 87 GW file. Booted up and opened wallet. Card was already there like it's supposed to be since reseting doesn't delete your card. It prompted me saying "Setup Required". Tapped and card was successfully setup, then deleted modded build.prop and restored build.prop.bak. Rebooted and went to test.

EDIT: Actually I'm using the 97 GW file this time. I used 87 on Wicked V5. I always follow the same steps and have no problems setting up. I've never had the secure element problem either. I'd just search this thread up top using only "secure element" and read some of those posts to find out where to look for the Secure Element version.
EDiT: I racked my brain trying to remember where to find it and it's in the GW app itself. Tap icon>put in password>hit menu button>tap "About". Mine says v1.6
 
Last edited:

78Staff

Senior Member
Sep 26, 2007
1,526
457
Cosmo, Fl
EDIT: Actually I'm using the 97 GW file this time. I used 87 on Wicked V5. I always follow the same steps and have no problems setting up. I've never had the secure element problem either. I'd just search this thread up top using only "secure element" and read some of those posts to find out where to look for the Secure Element version.
EDiT: I racked my brain trying to remember where to find it and it's in the GW app itself. Tap icon>put in password>hit menu button>tap "About". Mine says v1.6

97? or 96...

1.6 here as well (on 96), I think it's been 1.6 for a few versions now.
 

ParishM

Senior Member
Feb 8, 2007
169
33
Ft. Lauderdale
I felt that way too at first, but then I just put the pertinent files in a folder on my extSDcard (I always stay with Samsung based ROMs), including a saved copy of the modded build.prop. That means all I have to do is remember to reset GW before I flash a new ROM. When new ROM is flashed it's a cinch to reinstall GW!:good:



so if i understand this i guess you would rename the build.prop file to .bak then copy and paste
the modded file on the extsd into the system folder then run the wallet setup and eventually
restore the original build.prop ?
 

gravedigger76

Senior Member
Dec 5, 2012
2,408
705
Dublin
Re: Google wallet fix for SGS3 US variants AT&T, T-MOBILE, US Cellular, VERIZON, etc

Does anyone know,
Google wallet works only in places where they have the sign for Google wallet accepted, or at any place they have fast pass nfc scanners at registers?


Sent from my SGH-I747 using xda premium
 

acloaf

Senior Member
Jul 22, 2012
107
33
Lethbridge
Re: Google wallet fix for SGS3 US variants AT&T, T-MOBILE, US Cellular, VERIZON, etc

Does anyone know,
Google wallet works only in places where they have the sign for Google wallet accepted, or at any place they have fast pass nfc scanners at registers?


Sent from my SGH-I747 using xda premium

Anywhere they have the scanners.

Sent from my SAMSUNG-SGH-I747 using xda app-developers app
 

RaymondPJR

Senior Member
Oct 7, 2010
5,805
1,246
Portland
97? or 96...

1.6 here as well (on 96), I think it's been 1.6 for a few versions now.

Oppps! My bad, 96.:eek:

---------- Post added at 03:26 PM ---------- Previous post was at 03:20 PM ----------

so if i understand this i guess you would rename the build.prop file to .bak then copy and paste
the modded file on the extsd into the system folder then run the wallet setup and eventually
restore the original build.prop ?

Not exactly. When you mod build.prop the original renamed to .bak is created automatically. I just copy/saved the modded version to sdcard before deleting it and restoring the original. That way next time just name the original .bak manually and copy/paste the modded saved version from sdcard. Saves a little time.
 

ParishM

Senior Member
Feb 8, 2007
169
33
Ft. Lauderdale
Oppps! My bad, 96.:eek:

---------- Post added at 03:26 PM ---------- Previous post was at 03:20 PM ----------



Not exactly. When you mod build.prop the original renamed to .bak is created automatically. I just copy/saved the modded version to sdcard before deleting it and restoring the original. That way next time just name the original .bak manually and copy/paste the modded saved version from sdcard. Saves a little time.


that's exactly what i just said LOL
 

mbartur

New member
Apr 23, 2010
4
0
E:Signature Verification Failed during flashing

E:Signature Verification Failed during flashing SGS3-TW-US_variants-lib_nfc-fix-jellybean_4.1-1.zip (and the same failure if I try to flash com.google.android.apps.walletnfcrel.modaco.1.5-r87-v15.zip).

I have tried both the htc-jewel and the Galaxy Nexus build.prop and got the same result.

I am running root66_ATT_I747UCDLK3.tar on AT&T Samsung Galaxy S3.
Kernel Version 3.031-274808
Build number: JR003L.I747UCDLK3

The problem may be due to an older Wallet that was installed on the phone in an earlier ROM and was not reset before the new ROM. After the new rom there was no trace of Wallet. I have removed all credit cards on the web and removed the device as well (on the web).

Any suggestion/help would be appreciated.
 

lgkahn

Senior Member
Mar 26, 2010
2,324
219
londonderry
Re: Google wallet fix for SGS3 US variants AT&T, T-MOBILE, US Cellular, VERIZON, etc

E:Signature Verification Failed during flashing SGS3-TW-US_variants-lib_nfc-fix-jellybean_4.1-1.zip (and the same failure if I try to flash com.google.android.apps.walletnfcrel.modaco.1.5-r87-v15.zip).

I have tried both the htc-jewel and the Galaxy Nexus build.prop and got the same result.

I am running root66_ATT_I747UCDLK3.tar on AT&T Samsung Galaxy S3.
Kernel Version 3.031-274808
Build number: JR003L.I747UCDLK3

The problem may be due to an older Wallet that was installed on the phone in an earlier ROM and was not reset before the new ROM. After the new rom there was no trace of Wallet. I have removed all credit cards on the web and removed the device as well (on the web).

Any suggestion/help would be appreciated.

this has nothing to do with wallet..it has to do with the version of cwm.. try a different version

Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
 
  • Like
Reactions: RaymondPJR

mbartur

New member
Apr 23, 2010
4
0
Can I load it through Odin? Just want to ensure that all apps and all data will remain intact. I want to be as close to stock ROM as possible WITH Google Wallet.
 

lgkahn

Senior Member
Mar 26, 2010
2,324
219
londonderry
Re: Google wallet fix for SGS3 US variants AT&T, T-MOBILE, US Cellular, VERIZON, etc

Can I load it through Odin? Just want to ensure that all apps and all data will remain intact. I want to be as close to stock ROM as possible WITH Google Wallet.

no it is cwm flashable. while it doesn't get rid off apps... to avoid issues you need to do a reset. also make sure you have a backup.. I also had to manually flash att jb modem after.

Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
 

Top Liked Posts

  • There are no posts matching your filters.
  • 238
    Understanding google wallet

    the new google wallet is now available on ALL devices, however the "tap and pay" feature isn't
    the tap and pay feature is officially only supported on the following devices
    Phones

    HTC One on Sprint
    HTC One SV on Boost Mobile
    HTC EVO 4G LTE on Sprint
    LG Viper 4G LTE on Sprint
    LG Viper 4G LTE on Zact Mobile
    LG Optimus Elite on Sprint
    LG Optimus Elite on Virgin Mobile
    LG Optimus Elite on Zact Mobile
    LG Nexus 4*
    Motorola Moto X on Sprint
    Motorola Moto X on US Cellular
    Samsung Galaxy Note II on Sprint
    Samsung Galaxy Note II on US Cellular
    Samsung Galaxy SIII on Sprint
    Samsung Galaxy SIII on MetroPCS
    Samsung Galaxy SIII on US Cellular
    Samsung Galaxy SIII on Virgin Mobile
    Samsung Galaxy SIII on Boost Mobile
    Samsung Galaxy S4 on Sprint
    Samsung Galaxy S4 on US Cellular
    Samsung Galaxy S4 Google Play Edition*
    Samsung Nexus S 4G on Sprint
    Samsung Galaxy Nexus on Sprint
    Samsung Galaxy Nexus*
    Samsung Galaxy Victory 4G LTE on Sprint
    Samsung Galaxy Victory 4G LTE on Virgin Mobile
    Samsung Galaxy Axiom on US Cellular
    Tablets

    ASUS Nexus 7 (2012)
    ASUS Nexus 7 3G (2012)*
    Samsung Nexus 10

    other phone can support tap and pay.... they just need a work around

    for google wallet (TAP) to work first your nfc libs need to be correct (smx enabled)
    and second the google servers need to see that your phone is supported for the initial setup (build.prop edit)

    for example, if you have an AT&T galaxy s3, the smx (most likely) is not enabled because they want you to use ISIS (which uses the secure element in the sim card)
    We cannot compile the att version of touchwiz because we have no source, we can take the correct libs from a sprint gs3 to use on an att phone (see lib fix below)

    When trying to get wallet to work on a new device/rom take the following steps
    1-instal wallet from play or side load. Set up and see if tap and pay is enabled. if no, see step 2
    2-change build.prop to galaxy nexus (see below) uninstall wallet then reboot and repeat step 1. if no, see step 3
    3-run a logcat while opening wallet and look for "wallet" , "nfc" , and "smx" . Most likely at this point you need a (lib fix) In other words, you need the smx enabled libraries and corresponding files from a supported device. flash appropriate files (see lib fix zip) and start at 1
    4-once google wallet TAP is working, the build.prop can be reverted, but sometimes is will break wallet (TAP) and it might take a couple times for success. keeping the build.prop as galaxy nexus has no real side effects (I currently have a sony galaxy nexus ;))


    old wallet fix
    *The lib&nfc fix is intended touchwiz roms
    For CM9/10,aokp, and any other aosp rom, just flash the desired version wallet as the libs and nfc apk are correct

    latest Wallet version 1.5-r87-v15 changelog
    where google wallet works
    Google wallet (rom) compatibly list
    to contribute here is the google wallet compatibly list thread

    Ok, first a little background

    basically what you are seeing if you try to install google wallet on at&t, tmo, etc, is you get stuck on "activating device"
    If you dig a little further and ran a logcat, you will see that there it no "SMX detected"

    What this means, when compiling the rom you need to enable SmartMX in the config headers located in the external/libnfc-nxp library. (thats why it works on CM9/10, they do this)
    this is impossible for us because there is no source for samsung's TouchWiz. We got a break on the international sgs3 as the latest update has the secure element enabled...so does the sprint sgs3

    well that got me thinking, and of course sprint's nfc libs are close enough to work without breaking anything


    so this is how to do it. (btw, you need root)
    1-make a nandroid! I am not responsible if you mess up your device
    2-edit you build.prop using root explorer (when you press save, it creates a build.prop.bak)
    do not use ES explorer, it does not save correctly, for that matter ONLY use root explorer! (or adb push/pull)
    /system/build.prop
    preferred
    Code:
    ro.product.model=Galaxy Nexus
    ro.product.name=yakju 
    ro.product.device=maguro
    or
    Code:
    ro.product.model=htc_jewel
    ro.product.name=htc_jewel
    ro.product.device=htc_jewel

    3-If you already have Wallet installed...open wallet, go to settings and "reset google wallet" (if it hangs at 99%, reboot and continue with steps)
    (if you are (re)installing a new rom, this applies too...reset google wallet from within app)
    4-boot to recovery and flash SGS3-TW-US_variants-lib&nfc-fix.zip for ics touchwiz roms or SGS3-TW-US_variants-lib_nfc-fix-jellybean_4.1-1.zip for jellybean touchwiz roms and then wallet version com.google.android.apps.walletnfcrel.modaco.1.5-r87-v15.zip
    (for CM9/10, I9300, aokp, aosp roms just flash the wallet zip)
    5-reboot device, you will get "android is updating" (only this first boot)(all apps)
    6-open google wallet and sign in. add your personal credit cards (you must add them from your desktop first if you have never used google checkout before)
    7-(optional)if you get "error adding card try again later", wipe cache and davlik cache from recovery (only once! it sometimes takes hours, not minutes)
    8-profit (hold on! your not done, continue on to steps 9 & 10)
    9-after it is all up and running (meaning cards added), mount r/w in root explorer, delete the modded build.prop, then rename build.prop.bak to build.prop
    10-make a new nandroid with working wallet and put it in a safe place in case you ever accidentally install a new ROM without resetting google wallet data.

    still confused, here is a video of how to do it by moonfire711
    step by step upgrading to jellybean and adding wallet for verizon here

    >Special thanks to Hammermann, he did a ton of nandroids! He confirmed for me that the sprint nfc libs worked
    >Special thanks to WarlockLord we now have success on verizon
    >thanks to mobilehavoc for the galaxy nexus build.prop tip
    >thanks to magn2o for patching the new wallet (until paul returned)
    >thanks to FreydNot for for the above tip and for being brave enough to be the first to flash this to his tmobile sgs3
    >thanks to chris.ayoubtexas, the first att user with success (beat out Hammerman because ES explorer was screwing him)
    >thanks to Maldewka for installing and confirming functionality on US Cellular
    >thanks to Paul at Modoco for the modded google wallet apk<<<Paul's thread


    notes*
    -if you have used google wallet on another device, your prepaid card on the sgs3 is not the same...so balances will not carry over on the prepaid card prepaid is finished
    -despite the new cloud-based authentication system, the app does not require the phone to have a data connection to make payments at NFC-equipped terminals
    -really the key to this fix is the libs with the security element enabled.
    -the build.prop edit is for enabling cards, once they are enabled it can be reverted
    -the wallet apk has 3 features patched out. The first was a device check, the second patch was an operator check and the third patch was removing the root warning
    -NEVER, I REPEAT NEVER RESTORE GOOGLE WALLET WITH TITANIUM BACKUP! (please click link on step 10)

    original build.prop values for at&t
    Code:
    ro.product.model=SAMSUNG-SGH-I747
    ro.product.name=d2uc
    ro.product.device=d2att
    original build.prop values for t-mobile
    Code:
    ro.product.model=SGH-T999
    ro.product.name=d2tmo
    ro.product.device=d2tmo
    original build.prop values for US Cellular
    Code:
    ro.product.model=SCH-R530U
    ro.product.name=d2usc
    ro.product.device=d2usc
    original build.prop values for verizon
    Code:
    ro.product.model=SCH-I535
    ro.product.name=d2vzw
    ro.product.device=d2vzw
    original build.prop values for Telus, Rogers, Bell
    Code:
    ro.product.model=SGH-I747M
    ro.product.name=d2vl
    ro.product.device=d2can
    original build.prop values for Wind Mobile
    Code:
    ro.product.model=SGH-T999V
    ro.product.name=d2vw
    ro.product.device=d2can

    stop! if you are unclear of what to download, read the instructions again
    newest files are at the bottom[/HIDE]
    22
    Bing Bang Boom: https://dl.dropboxusercontent.com/u/5084138/2013-09-18 03.27.57.png
    This is a modified version that does not require editing your build.prop!
    It will probably work on any device. The only thing you might have issues with is the nfc.

    Try the following:
    1. Force Stop on Wallet app
    2. Clear Cache and Clear Data on Wallet app (in Application manager)
    3. Delete all traces of it from both locations /system/app and /data/app/ (might be called Wallet.apk too)
    4. Reboot
    5. [OPTIONAL] Flash a fresh version of your AOSP-based ROM (no wipe required)***
    6. Push the apk from this link and set the permissions (DO NOT OPEN IT YET!!)
    7. Reboot
    8. Open the Wallet app and set everything up
    9. Check what Tap and Pay says in "About" section of the app
    10. Confirm what happens on transaction
    ***Note*** If the ROM your are flashing is TouchWiz-based for step 5 you need to flash one of the below for your device BEFORE step 6 and then continue.

    For Galaxy S3: http://xdaforums.com/attachment.php?attachmentid=1943165&d=1367940081
    For Galaxy S4: http://xdaforums.com/attachment.php?attachmentid=2006809&d=1370008832

    Details/How you can do it to:
    I grep'd the smali folder looking for Landroid/os/Build and replaced almost every model, product, device, fingerprint with a string of what it would return from a Nexus 4 build.prop.
    So this:
    Code:
    sget-object v0, Landroid/os/Build;->MODEL:Ljava/lang/String;
    was replaced with this:
    Code:
    const-string v0, "Nexus 4"
    The only ones I didn't replace were in user feedback and about.


    NOTE: Please share this as much as you'd like, but please give me credit. I've spent far too many hours on this.
    ANOTHER NOTE: If you get "Insufficient Privileges - blah blah (release-keys)" then you need to find an nfc fix for your device.

    EDIT: I updated the apk and used a maguro (Galaxy Nexus) build.prop and changed every reference to build.prop, except sdk/version numbers. I personally tested a transaction and it went through successfully.
    19
    I went ahead and patched the latest wallet version and removed the root check, carrier check and device check. This isn't my work. I simply diff'd modaco version and applied the same mods to the latest version.

    It's working fine on my device (SGH-I747).

    Download!

    * edit: APK has been repacked with compression.
    12
    Changed the lines, forced stop, cleared the data, deleted the com.google.android.apps.wallet folder in /data/data, rebooted and it went through. I am not sure that all the other steps were necessary but I did so just in case there was a trigger stored in a data file somewhere.

    Ok, so there is hope! I'm building a new one right now. I changed everything to the maguro build.prop and I modified ALL instances of model, product, device, id, etc. inlcuding in About and User Feedback.

    EDIT: Here's the new apk for anybody to try. I can't test transactions at the moment. You can just overwrite the system app, but I would suggest clearing data for wallet and then overwriting.
    http://xdaforums.com/attachment.php?attachmentid=2266586&d=1379530246
    7
    I might have this working on 4.3. Tap and pay is setup and ready to use, but it's 2am and I'm not going to 7-11 to test right now. I'll make my wife walk with me tomorrow morning. If everything goes well, I'll upload.

    If you've used @dannyben's fix you'll know about the nfc payment has stopped (at least that's what I think it was) error message. That's because he used AOSP based files, whereas mine is modified TW files so no popups.