FIX for google wallet activating (updated op)

Search This thread
By:
Advanced…
Captain_Throwback

Captain_Throwback

Recognized Developer
Aug 22, 2008
20,445
23,058
The Nothing
Asus Eee Pad Transformer Prime
HTC One (M8)
NORCALkID said:
When you fixed the build prop did you uninstall google wallet? Then rebooted? Then did you download the new app from.the market?

Don't forget to deactivate the wallet app from settings menu

Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Yup. Did all of that. I even tried it once disabling Superuser, but it was still a no-go.
 
dpilcher

dpilcher

Senior Member
Jun 17, 2010
269
20
Denver
I went back and tried again, this time I downloaded the new Wallet and installed before setting it up. Didn't get the unsupported message this time, but the card still doesn't set up. Back home now and will try one more time, didn't uninstall the original wallet will do this wipe everything that has to do with this block, install fresh and give it another go. Has to be some underlying reason they are blocking this.

EDIT: Still a no go, going back to og build.prop

One thing I did notice, when I log into wallet on my PC a paypal transaction showed up. I obviously didn't use the wallet and sent the payment through paypal and have not put this card in as payment type on paypal. The card I used to attempt to get the prepaid wallet card has NEVER been used other than that one transaction. If they can grab a transaction from another source and show up on wallet, wth is that all about.
 
Last edited:
K

kmagn13

Senior Member
Oct 13, 2008
138
7
worked like a charm!!!!

for the people that it is not working for: Did you have wallet setup before?
 
W

whiskey7mm

Guest
Google Wallet Support wallet-support@google.com

Thank you for getting in touch with our team. We're aware that Google
Wallet payment cards are unavailable and our engineering team is working
hard to make sure Google Wallet is working as intended. We will be sure to
let you know when full functionality has resumed.

Thank you in advance for your patience and understanding.

Regards,

Chuck A.
The Google Wallet Team
 
A

Antebios

Senior Member
Apr 29, 2004
320
34
Houston, TX
It worked! I changed the properties and both ro.product.model properties. Afterward I rebooted. It took a long while to authenticate, and a good while for Google Prepaid cars to be added, but it eventually worked. I did not uninstall GW, already had SU denied. Woo-hop! I have my money back! Tomorrow I'm going to go try to buy something.

Funny: look at the signature below by the XDA Android app. It's using the build properties that were modified for this fix, even though I'm typing this on my EVO LTE.

Sent from my GT-I9300 using XDA
 
S

Socrguru

Senior Member
Feb 4, 2007
424
162
Bennington, NE
So something strange for me - I got the device initialized using the fix in this thread, but couldn't get the card added. Uninstalled Wallet, changed my build.prop back to normal, and rebooted. Did the whole thing again (changed build.prop again), only this time the device wouldn't initialize. Uninstalled, reverted to normal build.prop, rebooted again.

Just for S's & G's, I decided to try Wallet again. Opened it, updated it through Play Store as it asked, then opened it again. Got to the legal screen and for some reason decided to scroll all the way to the bottom, then clicked I Agree. And it initialized very quickly. I still can't add a card (that keeps timing out still), but I double-checked and my build.prop is saying jewel.

Could they have fixed the initialization thing? Did I get dumb luck? Or does scrolling through the legal crap actually do something...?

EDIT: Eh nevermind, just get stuck at "Validating device" or whatnot after a reboot. Ignore this post :p
 
Last edited:
Cuppeerr

Cuppeerr

Senior Member
Mar 15, 2010
2,916
841
29
Grapevine, Texas
I just tried again on normal sprint build.prop and got past adding account:)

I'm attempting to add a card right now:)

Sent from my EVO using Tapatalk 2
 
Cuppeerr

Cuppeerr

Senior Member
Mar 15, 2010
2,916
841
29
Grapevine, Texas
Socrguru said:
So something strange for me - I got the device initialized using the fix in this thread, but couldn't get the card added. Uninstalled Wallet, changed my build.prop back to normal, and rebooted. Did the whole thing again (changed build.prop again), only this time the device wouldn't initialize. Uninstalled, reverted to normal build.prop, rebooted again.

Just for S's & G's, I decided to try Wallet again. Opened it, updated it through Play Store as it asked, then opened it again. Got to the legal screen and for some reason decided to scroll all the way to the bottom, then clicked I Agree. And it initialized very quickly. I still can't add a card (that keeps timing out still), but I double-checked and my build.prop is saying jewel.

Could they have fixed the initialization thing? Did I get dumb luck? Or does scrolling through the legal crap actually do something...?

EDIT: Eh nevermind, just get stuck at "Validating device" or whatnot after a reboot. Ignore this post :p
Click to expand...
Click to collapse

Lol I tried that a couple days ago just for kicks and it didn't work but the server is working for me now I'm trying to add a card and my build.prop is unmodified:)

Sent from my EVO using Tapatalk 2
 
S

Socrguru

Senior Member
Feb 4, 2007
424
162
Bennington, NE
-Cupper- said:
Lol I tried that a couple days ago just for kicks and it didn't work but the server is working for me now I'm trying to add a card and my build.prop is unmodified:)

Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse

Have you rebooted since you got the account activated? I wasn't able to get the card activated so I tried rebooting for good measure, and Wallet just sat at "Initializing your device" for a really long time...
 
Cuppeerr

Cuppeerr

Senior Member
Mar 15, 2010
2,916
841
29
Grapevine, Texas
Socrguru said:
Have you rebooted since you got the account activated? I wasn't able to get the card activated so I tried rebooting for good measure, and Wallet just sat at "Initializing your device" for a really long time...
Click to expand...
Click to collapse

Nope, lemme do that. Still is fine. I also just cleared data and disabled root and it still works. It's just hanging on adding card right now

Sent from my EVO using Tapatalk 2
 
Last edited:
  • Like
Reactions: Socrguru
You must log in or register to reply here.

Similar threads

flex360
  • Locked
[ROM][3.22.13][3.44]Stock w Goodies|Sense 5 Icons|Wallpapers|Sounds|Battery & More
Replies
9K
Views
924K
tgrgrd00
tgrgrd00
regaw_leinad
[ROOT] RegawMOD EVO 4G LTE Rooter | Updated 01.26.13
Replies
2K
Views
427K
wwjoshdew
wwjoshdew
kushdeck
[12-4-12][ROM] CM10 for the evoLTE! - butta!
Replies
7K
Views
897K
Magnum_Enforcer
Magnum_Enforcer
utnick
[MOD] (UPDATED 07/03) Google Wallet Patch/Fix apk -- flashable zip by OMJ
Replies
338
Views
72K
loserskater
loserskater
-viperboy-
  • Locked
[ROM][Updated 6.1.12]viperROM eLiTE v1.2.1 - OC Daemon, viperControl, and more!
Replies
4K
Views
438K
-viperboy-
-viperboy-

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 16
    C
    ckoadiyn
    This is a fix for google wallet to let you login and has been confirmed it will let you buy things after doing it. I am making a new thread so it doesnt get buried in the Google wallet stuck at initializing your device thread. Be sure to thank jkt97401 for finding it and DZLRULZ for doing it and confirming he could buy things again in the thread posted below. I also did it to confirm it works to allow login again.

    THIS WILL NOT FIX SECURE ELEMENT BRICKS!

    EDIT: this fix has been blocked from my understanding in order to continue to use wallet you have to leave the change and not revert back to the original build prop however you are welcome to try out reverting it.

    http://xdaforums.com/showthread.php?p=27131994#post27131994

    jkt97401 said:
    I found a workarround, this worked for me and hope it helps others!

    Go into build.prop and change these values:

    ro.product.model=
    ro.product.device=

    to both equal this: GT-I9300

    This makes your phone look like the Sprint galaxy nexus.

    Reboot your phone and try to open wallet!

    You may have to clear google wallet settings, I had to uninstall wallet and reinstall it after the build.prop change.

    Hit the thanks button if this helped!

    -------------- PS --------------

    The reason I tried this is because I heard Google temporarily blocked the HTC EVO 4G LTE from accessing Google Wallet. I don't know the exact reason why, but this seems to work at least for now.
    Click to expand...
    Click to collapse


    DZLRULZ said:
    DUDES! It totally worked. I will be trying a transaction in a few minutes and reporting back. I was sick over this, worried about secure element. I got stuck at 99% resetting the app and eventually had to reboot.

    I did what you suggested and it activated, and my $100.21 was still in the prepaid card no problem. Here's EXACTLY what I did to keep out of the unsupported device also:

    EDIT: REQUIRES ROOT ACCESS (but not HTC UNLOCK, which I do not have)

    -Enable SuperSU
    -Use ES File Explorer for root explorer (Settings->Root Explorer, give Superuser permission when asked) -> Mount File System (writable)
    -Edit build.prop in /system folder as described above (make a backup also so you can revert after activation!)
    -Disable root explorer in ES File Explorer
    -Disable SuperSU in SuperSU settings
    -Clear data for Wallet in Settings->Apps
    -Reboot
    -Open Wallet, log in
    -Add prepaid card
    -Close Wallet
    -Go to Android Settings->Apps->Downloaded->Wallet and force stop (hoping to keep it from knowing about the next step which is enable SuperSU to revert build.prop and keep away unsupported device message.)
    -Enable SuperSU
    -ES File Explorer -> Root Explorer -> Mount System
    -In /system folder replace build.prop with the backup I made (or just undo the changes manually if you like.)
    -Disable Root Explorer
    -Disable SuperSU
    -Reboot
    -Open Wallet and verify operation
    -Profit!

    Sorry if this is jumbled, have to get to work but excited that it is fixed and hopefully by reverting build.prop no strange behavior will result!

    Thanks again jkt97401!
    Click to expand...
    Click to collapse

    DZLRULZ said:
    If my toys break I get sad...that is all.

    Sent from my EVO 4G LTE using Forum Runner.

    ---------- Post added at 08:19 AM ---------- Previous post was at 08:17 AM ----------



    Yes, it worked to buy Mountain Dew at a gas station just now.

    Sent from my EVO 4G LTE using Forum Runner.
    Click to expand...
    Click to collapse



    Since people are having problems here is how it should look do not copy and paste.
    ro.product.model= GT-I9300
    ro.cdma.home.operator.alpha=Sprint
    gsm.sim.operator.alpha=Sprint
    gsm.operator.alpha=Sprint
    ro.cdma.home.operator.numeric=310120
    gsm.sim.operator.numeric=310120
    gsm.operator.numeric=310120
    gsm.sim.operator.iso-country=us
    gsm.operator.iso-country=us
    ro.net.apnwhitelist=admin
    ro.htc.checkin.delay=0
    ro.watch.appid=com.sdgtl.watch.jelcl_40_ics
    ro.telephony.ipv6_capability=1
    dev.defaultwallpaper=/system/customize/resource/beats.jpg
    dev.deviceimage_large=/system/customize/resource/jewel_cl_187x370.png
    dev.deviceimage_small=/system/customize/resource/jewel_cl_32x58.png
    # begin build properties
    # autogenerated by buildinfo.sh
    ro.build.display.id=1.13.651.1 710RD
    ro.aa.rid=146
    ro.cwkey=SPCS_001
    ro.aa.skulist=651
    ro.aa.customizationid=361715
    ro.aa.project=JEWEL_CL_ICS_40
    ro.aa.mainsku=651
    ro.aa.taskid=259183
    ro.aa.romver=1.13.651.1
    ro.aa.maincid=SPCS_001
    ro.aa.modelid=PJ7510000
    ro.aa.cidlist=SPCS_001
    ro.com.google.clientidbase=android-sprint-us
    ro.build.id=IML74K
    ro.build.display.id=IML74K
    ro.build.version.incremental=60201.1
    ro.build.version.sdk=15
    ro.build.version.codename=REL
    ro.build.version.release=4.0.3
    ro.build.date=六 4月 28 04:56:33 CST 2012
    ro.build.date.utc=1335560193
    ro.build.type=user
    ro.build.user=
    ro.build.host=ABM032
    ro.build.tags=release-keys
    ro.product.model= GT-I9300
    ro.product.brand=sprint_wwe
    ro.product.name=jewel
    ro.product.device= GT-I9300
    View
    7
    S
    Socrguru
    I get tired of editing things manually, so I made a script to edit the build.prop for us! (Based on the HTCLinkifyDispatcher Fix by smw6180).

    This will fix the lines in build.prop so you can try to fix Google Wallet. Steps:

    1. Reset Wallet from within the app (if you can)
    2. Uninstall Wallet updates through Play Market
    3. Settings > Apps > Wallet - Clear Data (mine was grayed out because of uninstalling Wallet first) and Stop the app
    4. Reboot into recovery
    5. Flash WalletFix.zip, clear cache/dalvik cache, and reboot to system
    6. Update Wallet through Play Market
    7. Setup Market - should work!
    8. Reboot to recovery
    9. Flash WalletFix-revert.zip and reboot to system
    10. Done!
    View
    6
    EPayne123
    EPayne123
    1. Reset Default Settings Through Wallet.
    2. Go To Market And Uninstall Wallet Updates.
    3. Enable Root Through SuperUser.
    4. Change Lines In Build.prop(1st "ro.product.model" ONLY worked for me, DO NOT Delete the newly created "build.prop.bak".)
    5. Disable Root.
    6. Reboot.
    7. Install Wallet Update.
    8. Setup Wallet & Activate Card.
    9. Wait For Card To Be Added Successfully(Will Get Notification Within 2 Minutes).
    10. Force Stop Wallet Through Settings -> Apps.
    11. Enable Root And Revert "build.prop" back.
    12. Disable Root.
    13. Reboot.
    14. Open Wallet And Check To Ensure Card Is Still Active And Showing Balance Of $10 IF Not Already Used The Initial Free $10.

    This Is My Process So Far. Let Me Know Your Experience. Not sure about other Root Browsers but Root Explorer actually creates a backup of "build.prop" the way it was before modifications named "build.prop.bak". What I did once I was ready to restore the lines to the initial text was just delete the "build.prop" file and renamed "build.prop.bak" to "build.prop".

    Brought To You By TapTalk 2 Via LTevo
    View
    2
    C
    ckoadiyn
    Anthonicia said:
    Did the build.prop earlier in the week and it worked fine until I flashed a new Rom. If u recall I was the one who posted about the secure element error.

    Just got phone replaced, well I guess it was yesterday morning now. This new phone has sense reloading every couple hours, complete phone resets, light leakage and the screen illuminates like an LCD tv when touched.

    Last phone had none of that. If it wasn't for bricking the secure element...

    What happened after I flashed a Rom with wallet was it was sticking at activating for device. I tried uninstalling and reinstalling. After trying to get wallet to work again it gave secure element error.

    Before flashing the Rom I only did the build.prop fix once and changed back to EVO from GT-I9300. It worked great until I flashed a Rom.

    So, I may mess around with this phone today since I'm just gonna.take it back. May cut my losses and keep unrooted til there's a fix for wallet. Not sure if I want to get into this return game over and over. Really wanted to love this phone. Data sucks so bad and WiFi drops every 10 seconds, just really learning to hate it.

    Begining to think HTC/Sprint/Google are all going to the ****ter. As much as I dislike apple they are really looking good right now, patent be or no.

    Sent from my EVO using XDA
    Click to expand...
    Click to collapse

    If you replace it make sure it is good before you walk out of the store and if you don't need wallet right now don't touch it root unlock and flash away then you can worry about wallet after Google fixes it.

    Sent from my EVO using xda premium
    View
    2
    Riff76
    Riff76
    -Cupper- said:
    wtf my phone is on the top and my moms is on the bottom. I'm rooted with custom roms and she's fully stock.

    2012-06-17%2022.04.20.png
    2012-06-17%2022.04.13.png
    Click to expand...
    Click to collapse

    Isn't that like phone incest? :D

    Sent via XDA Premium
    View

New posts