Google Wallet 1.1-R67-v4 (June 6th update)

Re: Google Wallet 1.1-R63-v12 (May 16th update)

My old wallet was working fine. Just did cvs yesterday.
But with something new, I just HAD to install it. (the crackflash rom mentality)

Some were reporting that it asks for su every time when rebooting. It grants it auto. The small popup like when adfree is granted su after a reboot.
 
Re: Google Wallet 1.1-R63-v12 (May 16th update)

It is alot more than just a Disclaimer because if it shows up you can not use it for NFC functions at all. I have been using Google Wallet on my rooted device for months it just needed a "fix" to be flashed after a fresh install. This current version is working on my rooted device and it knows I am rooted with no "fix".

that's not true even a little bit. the disclaimer has been showing on mine for months and i use wallet regularly
 
that's not true even a little bit. the disclaimer has been showing on mine for months and i use wallet regularly

Correct its just a disclaimer.. I think he was just confusing it with earlier, back a few months it wouldn't work at all while they were "fixing" it... Lol

Sent from my Galaxy Nexus using Tapatalk 2
 
Re: Google Wallet 1.1-R63-v12 (May 16th update)

I seem to be having a similar experience to what a few others posted:

I 'm on VzW and side-loaded the "original" wallet leak on 4.0.2 stock (unlocked and rooted though at the time). Worked fine, and of course I had the yellow bar at the top with the "unsupported" disclaimer.

Update the phone to the VzW 4.0.4 leak a couple of weeks ago...still unlocked, and since re-rooted.

Tried all the workaround tonight to try to get the play store to allow me to update - going to google play website via unlogged in browser, searching for wallet app, logging in, backing out and select play store, etc. None of that would work. Finally reset the old app, clearing data, uninstalled it and downloaded / installed the new one in this thread. Oddly it took be four tries to log into my wallet account in the new version before it recognized my password -- maybe I'm fat fingered tonight... But...it finally worked, logged me in, restored my $10 balance and all seems happy. In the startup process, it DID prompt me for superuser access -- which I granted.

After all that, I can exit the app, restart, and all seems fine -- and there's no longer a yellow warning banner up top with the "unsupported" disclaimer. Seems that this version, once granted SU status, is happy to operate on my rooted, unlocked VzW GN without showing the disclaimer.

Will give it a try at the store tomorrow...

Jon
 
  • Like
Reactions: 2defmouze
Re: Google Wallet 1.1-R63-v12 (May 16th update)

I seem to be having a similar experience to what a few others posted:

I 'm on VzW and side-loaded the "original" wallet leak on 4.0.2 stock (unlocked and rooted though at the time). Worked fine, and of course I had the yellow bar at the top with the "unsupported" disclaimer.

Update the phone to the VzW 4.0.4 leak a couple of weeks ago...still unlocked, and since re-rooted.

Tried all the workaround tonight to try to get the play store to allow me to update - going to google play website via unlogged in browser, searching for wallet app, logging in, backing out and select play store, etc. None of that would work. Finally reset the old app, clearing data, uninstalled it and downloaded / installed the new one in this thread. Oddly it took be four tries to log into my wallet account in the new version before it recognized my password -- maybe I'm fat fingered tonight... But...it finally worked, logged me in, restored my $10 balance and all seems happy. In the startup process, it DID prompt me for superuser access -- which I granted.

After all that, I can exit the app, restart, and all seems fine -- and there's no longer a yellow warning banner up top with the "unsupported" disclaimer. Seems that this version, once granted SU status, is happy to operate on my rooted, unlocked VzW GN without showing the disclaimer.

Will give it a try at the store tomorrow...

Jon

Thanks for the update.. was going to say to people who it wouldn't install for to just keep trying. There's no reason it should not install.

And going around the web it looks like everyone agrees the SU access request is probably more of a bug than anything... some people are able to get it to work fine not granting it while other have to, I say just give it and put it out of your minds, lol.
 
You happen to give it root access or no? Just curious..

Sent from my Galaxy Nexus using Tapatalk 2

Yup I gave it root access shows the disclaimer bar but works fine

Sent from my Galaxy Nexus using Tapatalk 2.1.1
 
Re: Google Wallet 1.1-R63-v12 (May 16th update)

for some reason when i transfer the file onto the root of my sd card it shows up as 0 for the file. ill go to install it but there is nothing there the file size is 0. am i doing something wrong?
 
for some reason when i transfer the file onto the root of my sd card it shows up as 0 for the file. ill go to install it but there is nothing there the file size is 0. am i doing something wrong?

Doesn't need to be on the root of the sd. Just open the download and install. :)

Sent from my Galaxy Nexus using Tapatalk 2
 
Re: Google Wallet 1.1-R63-v12 (May 16th update)

I am on stock 4.0.2 and I am seeing the same thing as others have reported that is unable to install
 
Re: Google Wallet 1.1-R63-v12 (May 16th update)

No, doesn't install on stock 4.0.2. Had to reinstall the last version.
 
Very weird that it isn't installing on 4.0.2 for you guys. Anyway here's another link to the earlier version which does work on 4.0.2 in case anyone misplaced it, lol :)
http://db.tt/KzJC4vPY

Sent from my Galaxy Nexus using Tapatalk 2
 
Re: Google Wallet 1.1-R63-v12 (May 16th update)

Unable to install new version never had wallet before stock unrootrd 4.02
 
Re: Google Wallet 1.1-R63-v12 (May 16th update)

anyone have a work around to get wallet working on the tmobile samsung galaxy s2 yet? I am able to install no problem, either by download the apk, or using the browser/market workaround.

Still get the "unsupported carrier message. " any way around this?