yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Eyalkn:
JB 4.3

[MENTION=4979049]Prl91[/MENTION] , I get this message on JB 4.3.

"Device Not Ready, Wallet is unable to proceed until this device is fully initialized. Make sure the device has network access and try rebooting if the problem persists" I tried enabling and disabling airplane mode, disabling the wi-fi and using data and rebooting and still the same issue. Auto update is disabled so this is the version that came with the installer. Does it suppose to work on JB 4.3?
[Verizon Samsung Galaxy S III] Prl91:
Unfortunately there were changes in the latest firmware that seem to have stopped Wallet Installer from working. I've heard of some success, but in general I don't think the two play well together. I think the problem may be a change in NFC libraries, but I no longer have an S3 to test on unfortunately.
[Verizon Samsung Galaxy S III] xObey:
Just tried installing on the tmo sgs3 on the new carbon rom 4.3 nightlies, it installed normally for me.
[Verizon Samsung Galaxy S III] grundy923:
Bricked my phone. Awesome. Thanks for that. Now I remember why I never both with rooting my phone.
[Verizon Samsung Galaxy S III] Dearborn1977:
You're welcome!
[Verizon Samsung Galaxy S III] grundy923:
So if you're thinking about trying to get Wallet installed on your Verizon Galaxy S 3 and are hoping this is the way, turn around, go back, and keep looking else where. All this did was brick the hell out of my phone. I can't even get into download mode now.
[Verizon Samsung Galaxy S III] Stranger_84:
Hmmm what did you do wrong? Works just fine for me and many others
[Verizon Samsung Galaxy S III] grundy923:
Hmm... If I had to pinpoint 1 thing that I did wrong, I would have to say running WalletInstallerV3.apk.
[Verizon Samsung Galaxy S III] Prl91:
There's no need for flaming. This is a support thread. Take your inapropriate comments to PM.
[Verizon Samsung Galaxy S III] Stranger_84:
Was the latest busybox installed?
[Verizon Samsung Galaxy S III] grundy923:
Saying that running an APK bricked my phone is flaming? That's new...

Yes, of course. My phone was rooted, unlocked bootloader, installed newest version of Busybox, ran WalletInstallerV3, picked JB TouchWiz, Verizon, clicked install, phone instantly rebooted and would not come back on. I can boot into Recovery mode just fine, but there's not much I can do there. When I boot into download mode it wont stay in download mode it just reboots in under a second.
[Verizon Samsung Galaxy S III] Prl91:
I'm simply saying that constructive criticism and support is acceptable and highly encouraged here, not so much simply saying that it ruined your phone. Wallet Installer works for many people, and I'm sorry that it didn't work for you, but it does have value to other users. I'm simply trying to keep the thread productive.
[Verizon Samsung Galaxy S III] grundy923:
And I'm trying to warn people that it can brick their phone.
[Verizon Samsung Galaxy S III] Prl91:
Everyone knows the risks involved, which max out at a soft brick. Please keep the conversation on topic. Thank you.
[Verizon Samsung Galaxy S III] grundy923:
I never took it off topic. All I've ever talked about is what this thing did to my phone. How is that off topic?
[Verizon Samsung Galaxy S III] Prl91:
This is your last warning. Ask all the support questions you want. You will be helped, but please do not continue arguing with me. Thank you.
[Verizon Samsung Galaxy S III] kentedman:
If you can get to recovery, just restore your latest nandroid backup.
[Verizon Samsung Galaxy S III] annoyingduck:
And if you don't have a backup you can use adb and push a zip onto your root storage via recovery (twrp, not sure about cwm). Or just slap a zip onto a micro sd card from your cpu using an adapter and flash from there.

Anytime you get involved with a hack like this you should always backup prior.

This method has proven to be the easiest way to get wallet on our devices, though I have had many soft bricks using different methods in the past, but that was expected with such a hack. If this apk bricked everyone's device, I think it's safe to say the thread would be closed. That's a bold statement and completely out of line.
[Verizon Samsung Galaxy S III] Mixinitup4Christ:
Just used wallet installer on CM10.2 (Mastamoons Builds) and it seems to have worked correctly, although I haven't tried to purchase anything yet.
[Verizon Samsung Galaxy S III] jrc27:
I just got it to work on Mastamoons build as well...It's funny because this is the first time i was able to get it to work
[Verizon Samsung Galaxy S III] Mixinitup4Christ:
Well although it seemed to install, nothing happened when I attempted to pay with it. I've been thinking about dropping back to 4.2.2 anyway hmmmm :thumbdown:
[Verizon Samsung Galaxy S III] stimpco:
"Google Wallet Unable to Authorize"

Everything worked great, app starts fine, but is being declined at the local merchant (soda machine) at my work... I'm on AOKP jb-mr1_milestone-2. Wallet used to work fine on stock/rooted. I've tried using the app before & after restoring the build.prop. Any suggestions? -Thomas
[Verizon Samsung Galaxy S III] supercell2000:
Is there any way to know if there's an update available on the server side? Wallet is working flawlessly for me, so I would be hesitant to update, but I see that on Google Play it's at version 16 and my latest download from your server is 13.
[Verizon Samsung Galaxy S III] ufjay5:
I'm running bone stock 3'3...dl wallet installer...it rebooted but no wallet app..am I doing something wrong?
[Verizon Samsung Galaxy S III] kentedman:
If you use Xposed framework there is wallet unlock module. Use this app (wallet installer) to get wallet installed initially and then using the xposed module you can keep wallet activated through ROM updates and even play store updates.
[Verizon Samsung Galaxy S III] GREGHARKINS:
How is everyone handling the device and carrier name change?

Are you changing it back and it still works or are u leaving it as the fake info all the time
[Verizon Samsung Galaxy S III] Eyalkn:
Wait but as long as you are configured as Verizon in the build.Prop you won't suppose to see it at all in the play store.
[Verizon Samsung Galaxy S III] kentedman:
true.... I currently have the latest Wallet version working, but I wont see new updates automatically. I'd need to change build.prop and check for new updates manually.

What I did:

A) the Xposed module thread is here: http://xdaforums.com/showthread.php?t=2126241 It requires manual modification of the build.prop for initial install. Using this app was much easier.

B) I used wallet installer to edit build.prop and install. Rebooted and configured Wallet. Went to the Play store and updated wallet to latest version. (dont reopen wallet yet). Enabled Xposed Module, rebooted. Used Wallet installer to restore build.prop, rebooted.

Ended up with latest version of Wallet, installed and activated. Never had to manually touch the build.prop. I've dirty flashed sever ROM updates in the meantime. as long as I makes sure the Xposed module is active before opening Wallet, I've never had to reactivate it.
[Verizon Samsung Galaxy S III] roachkv:
Not sure what I'm doing wrong. I'm running rooted, deodexed VRBMF1.

I downloaded and installed Xposed framework. Rebooted.

I downloaded and installed the XposedWalletPatcher. Rebooted.

I activated the XposedWalletPatcher and rebooted.

I downloaded and installed your WalletInstaller (from the link in the OP). I checked JB TW rom and VZW, and then I hit install. It did something for a couple of seconds and rebooted.

But I don't have Wallet on my phone.

What did I do wrong?
[Verizon Samsung Galaxy S III] MajicManDroid:
What modem are you on. I just saw a thread that said a t-mobile user was having an issue due to the modem he was on. I'm going to roll mine back and see if that fixes things.
[Verizon Samsung Galaxy S III] jrc27:
When i do it, i use the wallet installer first (this edits the build.prop and installs wallet), then install xposed framework and reboot, then install the wallet patcher module, activate it in the modules section and reboot, then open wallet and set it up, then use the wallet installer to restore build.prop
[Verizon Samsung Galaxy S III] mikejr83:
Thanks for the quick reply. The only reason I don't go with a modified build.prop and unmodified wallet is because I use a few Verizon only apps like NFL Mobile. I've never asked but assumed that the modified build.prop would cause those to not work.

Do you know if this is true?
[Verizon Samsung Galaxy S III] Prl91:
I can't say that I know. If I were you I would make a backup, try out an unmodded version of wallet(mine or whoever's you prefer) and see if NFL and your other Verizon apps still work correctly. No harm in trying, right?

**Also, mine now backs up your original build.prop, so if something doesn't work or you want to go back to a modded version, just click my "restore build.prop" button**
[Verizon Samsung Galaxy S III] tonu42:
That's why I made the edit scripts haha. I'm telling you, using sed commands will make life much easier haha. You can make it default to using sed and instead of backing up and what not you can use the sed command again to edit build prop :)
[Verizon Samsung Galaxy S III] Prl91:
Yea, I used "sed" this time. I left a physical backup though, just in case they want to restore it manually incase something goes wrong with the app.
[Verizon Samsung Galaxy S III] tonu42:
You should try using Google code for hosting scripts. On my Google prototype to install Linux I downloaded like 4gigs of data in an hour. They have a very good connection. I'm stalling downloading each time now.
[Verizon Samsung Galaxy S III] Prl91:
I thought about that, but I ended up buying a domain and am working on setting it all up in my spare time. Hopefully it will be ready to go soon!
[Verizon Samsung Galaxy S III] tonu42:
Yea..... painfully slow now hahah. Check your PM its important.

Edit: App works fine, works great, checked AOSP, hit download (slow) rebooted to recovery fine, flashed fine, etc etc.

Have you thought about download all the files to /cache/ and moving them over to /system? No need for recovery or all of that shenanigans.
[Verizon Samsung Galaxy S III] Prl91:
I would, but wallet has a tendancy to not stick unless flashed.
[Verizon Samsung Galaxy S III] tonu42:
Are you setting correct permissions on it once its been moved?
[Verizon Samsung Galaxy S III] Prl91:
Yup. When moved with root access it retains the permissions it came with.
[Verizon Samsung Galaxy S III] Ronin09:
Hard to connect to download. ..any remedy
[Verizon Samsung Galaxy S III] tonu42:
He was moving servers to a faster/better one. So give it an hour he said and it'll be back up.
[Verizon Samsung Galaxy S III] GREGHARKINS:
Did the new release come yet that fixes the disappearing sd files and keyboard SwiftKey issues
[Verizon Samsung Galaxy S III] Hulk0069:
He said the new release fixes that
[Verizon Samsung Galaxy S III] Ronin09:
Is this server still down does anybody know
[Verizon Samsung Galaxy S III] Prl91:
It is. I'm working on it now though. I went out and grabbed some food at a restraunt, I was starving lol Sorry for any inconveniences.
[Verizon Samsung Galaxy S III] Hulk0069:
Hey you gotta eat...glad your working on this
[Verizon Samsung Galaxy S III] fr8cture:
Any update on when i can try this out?
[Verizon Samsung Galaxy S III] Prl91:
Still working out bugs for the newest version. It'll be done tonight sometime.
[Verizon Samsung Galaxy S III] fr8cture:
Alright, can't wait to try it!
[Verizon Samsung Galaxy S III] Prl91:
For some reason the server holding the files is down. I'll look at it in the morning and see what happened. Sorry for any issues you may have had!
[Verizon Samsung Galaxy S III] Afro Samurai:
Thanks, I was pulling my hair out trying to figure out what I was doing wrong.
[Verizon Samsung Galaxy S III] cnlson:
any chance it's back up now?
[Verizon Samsung Galaxy S III] Prl91:
Not quite yet. I'll have it back up before the day's over. Probably in an hour or two hopefully. I just have to wait for my payment to clear, I still had my old card on auto-payment :dumb:
[Verizon Samsung Galaxy S III] cnlson:
uh, so here's my problem. i have killed my phone apparently.

how it started, i ran this once, no google wallet, ran it a second time still no google wallet. checked the market, could install google wallet, installed and of course ran into the "Insufficient secure element privileges for this system image (release-keys)" so i uninstalled GW, then ran the installer to change my build.prop back, checked after reboot and it was still galaxy nexus, so then i ran it again thinking it wasn't doing anything. on reboot my build.prop was completely gone. so on reboot it showed samsung, then galaxy s3 then blankscreen with nothing and the notification led simply pulses.

luckily my wife has the same phone so i copied her build.prop to my sd card and restored it in twrp and nothing changed, samsung, then galaxy s3 then led pulsing and phone vibrating from time to time.

as an aside, the app probably should only rename the build prop once and should only be able to restore if the renamed file exists... just a small suggestion.

aaaaaaaaaaaaaaaaaaand its back to working. had to chmod the file. (chose 755 no idea if thats correct or not but its back up now)

---------- Post added at 11:48 AM ---------- Previous post was at 11:40 AM ----------

if you need some redundant server space i'll contribute.
[Verizon Samsung Galaxy S III] stimpco:
I'm on MF1... just rolled back to MB1... I guess the question would be, do I need to roll the full build back?

MORE INFO:

Ever since I installed AOKP I'd been having weird issues like mms's not working to iPhone/Blackberry... plus the Wallet issue. I did a full wipe and went to CM 10.1.2... same issues. I'm now back to stock, rooted... SAME ISSUES. Tried the wallet app again today, failed the sale.

Thanks for the reply!

-Thomas
[Verizon Samsung Galaxy S III] Prl91:
Sorry to hear that you had issues! Chmod 755 should be just fine. If I'm correct that grants read/write/execute to root and read to all others. Also, thanks for the offer! I may take you up on that!
[Verizon Samsung Galaxy S III] Mixinitup4Christ:
So the WhatABurger where I tested it the first time must have a broken NFC thingy. Just for fun I tried this again at a different store and it worked. I'm running Cyanogen Mod 4.3 (Unofficial Mastamoon Nightlies).
[Verizon Samsung Galaxy S III] cnlson:
No worries! It turns out that 644 seems to be the actual correct number but it's still OK to go with 755.

I hope you consider those updates just in case, to save those that don't have a nandroid or a spare phone to copy the build.prop from, but plus you could incorporate a server check in case it's not reachable for any reason.

Has your site come back up?

---------- Post added at 10:35 PM ---------- Previous post was at 10:33 PM ----------

When I used the isis app in Texas it was hit or miss if whataburger would have their nfc turned on that day.
[Verizon Samsung Galaxy S III] nconfer13:
So I'm reading these posts (in the thread) and I'm curious if Cynogen Mod 10.1.3 for Verizon is supported?
[Verizon Samsung Galaxy S III] cnlson:
Check this thread http://xdaforums.com/showthread.php?t=1794727

Afaik cyanogen doesn't need the hacked wallet this installs, just the build.prop change as the smx is already secure and with the build.prop swap you should be able to install from the market. After that all you would need to do is toggle the build.prop back until you wanted to update the app then toggle it back.
[Verizon Samsung Galaxy S III] cnlson:
Back up and running yet? I'm not going to rerun this until I know for sure it's working.
[Verizon Samsung Galaxy S III] PickledEggs:
I'm using a d2vzw running CM10.2 20130910 and the installer worked just fine, wallet installed, updated from play store, and was working, then after I restored my build.prop, it gave me an error when I opened wallet, saying "Wallet is not available for your device or mobile network"

Should I not have restored my build.prop? Is there any harm in leaving a different build.prop in there? Should I have not let it update from the market?

Thanks for any light you can shed on the issue, and thanks for the convenient one click app. It's so stupid that Verizon doesn't allow the app to be installed normally.
[Verizon Samsung Galaxy S III] Stranger_84:
Not suppose to let it update from the market
[Verizon Samsung Galaxy S III] siff:
Serve back up yet?
[Verizon Samsung Galaxy S III] jpmi23:
Mine did the same thing when I changed the build.prop back. Only difference is I didn't use the installer. Just changed the build.prop, rebooted, installed from the market, set it up, and rebooted. As soon as I change the build.prop back to the "stock" info, it won't work. If I leave it as being a Galaxy Nexus it seems to want to work fine. (CM10.2 09112013)
[Verizon Samsung Galaxy S III] jrc27:
i think so
[Verizon Samsung Galaxy S III] MajicManDroid:
I rolled back to a build where it worked after rolling the modem back and still no luck. I tired a different wallet install method with no luck. If you fix yours let me know.
[Verizon Samsung Galaxy S III] rsswga:
oh man awesome..works fine..thanks

sent from a violated Vzw Galaxy s3
[Verizon Samsung Galaxy S III] roachkv:
Having mucked around with those apps now. What do you think I should do?

Even though I "restored" my build.prop it still shows Galaxy Nexus. Guess I'll need to manually restore that...

Should I uninstall everything and reinstall/run in the order you suggested?
[Verizon Samsung Galaxy S III] thejron:
Not working on latest beanstown ROM. :(
[Verizon Samsung Galaxy S III] MorphiousGX:
Elaborate?
[Verizon Samsung Galaxy S III] thejron:
I run the app, select tw jb and vzw. Phone reboots and no wallet app installed
[Verizon Samsung Galaxy S III] supercell2000:
As the OP stated earlier, he's having server issues, so if you try to run the app it will change your build.prop but not install wallet. Even though wallet didn't install you still have to run "restore build.prop" to get your phone back to SCH-I535. If it's to late for you to revert, just change build.prop manually.
[Verizon Samsung Galaxy S III] Mixinitup4Christ:
As stated the DEV is having problems with his hosting. However, when I flashed my last ROM and had this problem I installed wallet from the Play Store. I have successfully made a payment with that installation.
[Verizon Samsung Galaxy S III] cnlson:
That will work only if the securemx is installed also since that's not a part of tw normally
[Verizon Samsung Galaxy S III] I Fling Poo:
where do we get securemx? I can't find anything about it.
[Verizon Samsung Galaxy S III] cnlson:
Sorry smartmx http://xdaforums.com/showthread.php?p=28679456
[Verizon Samsung Galaxy S III] Prl91:
The server/host has been fixed! Let me know how it works, and sorry for the delay.
[Verizon Samsung Galaxy S III] v793jt0:
it still does not work for me
[Verizon Samsung Galaxy S III] Frijole:
Doesn't work for me either.
[Verizon Samsung Galaxy S III] cnlson:
it didn't work for me either. however i searched the phone for "wallet" and found d2vzw-wallet-tw-jb-1.6-r96-v13.zip. moved it from where ever it was located to download. then rebooted into recovery and flashed it. i cleared cache and dalvik and rebooted.

it was installed. i was able to sign in. and it appears (so far) to be working even after i put the build.prop back.

you aren't by chance running twrp recovery are you? i'm wondering if thats why it didn't go into recovery and flash automatically...
[Verizon Samsung Galaxy S III] Afro Samurai:
I'll see if this happens for me later today. This Isis wallet looks like some bs.

Sent from the S3 of The Afro Samurai
[Verizon Samsung Galaxy S III] cnlson:
I was lucky enough to be travelling with my wife in late january to TX and we were passing through austin so I stopped at a verizon store and grabbed a sim for my and my wifes phone. the NFC is in the SIM. I'm assuming this means if the secure element gets borked you just get a new SIM and all is well. With that we both got $25 for signing up and my wife immediately used hers for shoes. I used mine several times to get fast food, and i reloaded it a couple of times, there was no minimum reload, and used it at the vending machines at work.

However it was always adverse to root. but temp unrooting with supersu used to allow it to work as it does for all of the apps that i have that rootcheck. but now unless i flash back to completely stock it wouldn't even open. couple that with the fact they have closed the prepaid card so you have to have a amex, chase, or barkley card to use it. used to be cap 1 also but they've dropped support. so i uninstalled and have installed wallet.
[Verizon Samsung Galaxy S III] Afro Samurai:
So far it seemed as if the app installed correctly so the server issues appear to be good. I didn't have to flash a zip. I'm going to bed but I'll try to see if it works the next time I have an off day.:fingers-crossed:
[Verizon Samsung Galaxy S III] qdtphotog:
Something wrong

I used to use this Wallet installer without any problems. But it just gave me a good scare and had me re-flash my rom. So I installed the installer but this time it didn't seem to work because after rebooting, I didn't see the Wallet app. Although it did change my prop build. So I run the installer again - same thing. I figured it didn't work anymore so I ran the installer to restore my prop build. It didn't work - twice. Then all of the sudden the screen went blank. I pulled the battery a few times to turn it on but nothing. I finally had to boot into recovery and re-flashed the rom, which is "JellyBeans 19". Weird! :confused:
[Verizon Samsung Galaxy S III] Frijole:
Same issue here... Still not working :confused:
[Verizon Samsung Galaxy S III] annoyingduck:
There's been modded apk's, xposed modules, nfc lib patches, etc all leading up to installing the new wallet version and having tap+pay enabled. All have failed for me except for what I just did.

This is what I did and so far all looks promising (have to test actual payment). My method is for aosp, currently running cm10.2.

1: uninstalled current playstore version of wallet (the new one we can download without nfc activated)

2: I did not reboot, just ran wallet installer

3: after the reboot I set up wallet completely. While setting up, a notification appeared notifying of an update. It did not auto update because of new permissions in the new version of wallet.

4: after setting up I then updated wallet from the playstore. Opened it to verify nfc capabilities.

5: restored build.prop via installer

6: done! Nfc still enabled within wallet. Just need to test now.
[Verizon Samsung Galaxy S III] Prl91:
Glad to hear everything worked well for you!
[Verizon Samsung Galaxy S III] GREGHARKINS:
Worked like a charm

---------- Post added at 07:27 PM ---------- Previous post was at 07:26 PM ----------

Will test tomorrow
[Verizon Samsung Galaxy S III] GREGHARKINS:
The issue I'm having is nrc has stopped... I fixed it by keeping wallet from auto starting and it quit the error message anyone else have a different fix

---------- Post added at 05:41 PM ---------- Previous post was at 05:10 PM ----------

An update to the nfc issue

It only happens on Google Apps the rest seem to work perfectly
[Verizon Samsung Galaxy S III] GREGHARKINS:
Just flashed the nfc fix and is working like a charm
[Verizon Samsung Galaxy S III] Bright09:
since I have NFC Sim card will I be able to use wallet and s beam if I replaced my battery
[Verizon Samsung Galaxy S III] Afro Samurai:
I'd like to get this working. Could you say what steps you took?

Thanks.