yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
I can finally upgrade to 4.3, just needed a working Wallet. Thanks so much for figuring this out!:laugh:

EDIT: Finally flashed to 4.3. This is what I did. I forgot to disable Wallet, so I did so through the website, wallet.com. After flashing I edited the xml file, then I booted into recovery and flashed the nfc fix. Then I downloaded and pushed the new .apk. When I booted up, the wallet icon did not appear in the notification bar. And after setting up, I have tap and pay not available. What went wrong?:(

T-Mobile SGS3, Stock rooted T-Mob 4.3, nfc fix from your thread and modded 2.0-R141-V14 .apk

EDIT: I just noticed that auto-upate is on by default in the playstore. I didn't notice any update, but I wonder if that's what did it. Never mind, somehow I got the wrong .apk.

EDIT: Turns out it was the old MD5 modem. I was on wifi the whole time after flashing and didn't notice I did not have a cell signal. Wallet tap and pay is setting up! Thanks!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moonfire711:
Thank you very much for the work that went into this NFC fix and for the work that has gone into the modified Wallet.apk. I had forgotten to reboot after pushing the app to system/app and the tap to pay feature kept failing. As soon as I rebooted and tried again, it worked. The real test will come when I can actually make it to a store to test. Thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
After I pushed the right .apk and flashed the right modem to get a cell signal, everything set up fine. Used it tonight and had to explain to someone who was so impressed he wants to buy a Nexus or a Sprint GS3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LancerV:
This worked for my TW 4.3 Note 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FreydNot:
Thanks so much for this thread. I'm happy it give the technical nitty gritty details as well as instructions. Tap to pay is now working on my T999 running rooted stock 4.3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cnlson:
will this work for a vzw sgs3 with isis as well? i have isis and wallet on my vzw s3 and both are working right now. but not when i upgrade to 4.3 so i've temporarily reverted back to 4.1.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dseda86:
Does this has to be done on s4 running 4.3 rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] longjohnsteve:
Does this work on 1747m (bell) ? I'd love to be able to use wallet. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
It should work, although I haven't tested or heard of anybody that has. If it works for you please let me know.

No, this is in the S3 forums for a reason.

Yes, it should work fine.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cnlson:
well today i got a spare s3 to try it with. i need to ask you for a little help. i'd like to package the correct features xml with it and the wallet you made.

any easy instructions on how to add to your flashable zip?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] robertlewisca:
Need Root?

Apologies if this is a dumb question. In the previous wallet fixes for previous versions of Android, they all required root. It doesn't specifically say so in these instructions. Is it possible to get this working without root?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
No, because you need to move it to the system/app folder which requires root.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] longjohnsteve:
Not really sure if I'm doing something wrong here. Im using a 1747m s3 with bell with a 4.3 tw rom (dandroid) and I cannot find <-NFC-> in the features file. Could I just add the section required and go from there?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bajanman:
[MENTION=1016795]loserskater[/MENTION]

I can confirm that the Google wallet works with the Isis SIM installed...

I just helped another member getting this set up. And he also had a Isis SIM...

He stated all he did was uninstall the Isis app that's on the phone. Then everything worked fine!!

Me 3¢®™
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeremyds45:
I can confirm that Isis in general does not work with gophone, so I'm stoked that this fix for Google wallet does
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cainmadness:
I'm not certain what is going wrong. I modified the features.xml and put the .apk to the proper place with Root Manager, yet I don't see the app anywhere on my app list or Application Manager.

The edit to features.xml is working as I put the logo line of code to be displayed, and can see that on my notification bar. The permissions for the .apk were swet to -rw-r-r-- and flashed the file like on the original post. Is there something I'm missing?

T-Mobile SGS3, Stock 4.3 and Rooted. No custom kernel or modem, etc. Just a rooted, stock phone. On previous/older ROMs I have had Wallet up and running, but not since I put 4.3 on my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cainmadness:
Everyone can ignore my previous post. I somehow managed to get it working.

SGH-T999, Stock TW 4.3, rooted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neo760:
Will Isis still work with this? Can I have both Google and Isis working, or is it one or the other?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bajanman:
You can have a Isis SIM in your phone, and have this working no problem. But having both Isis and GW working. Don't think that's going to be possible...:eek::confused:

SENT FROM MY SAMMY TO YOUR? EYES USING TAPTALK
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ruff97:
thank you this work on my Note 2 on sprint
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Casey707:
Which file do I edit?

Maybe this is a dumb quesiton, but here goes...

I have 2 "features.xml" files in the System folder. one has a ".xml.bak" file extension and the other is just ".xml".

There is only a <!-- NFC --> section in the "features.xml.bak" file, is this the correct one to edit? Why do I have 2 files in there?

Edit: It is bacasue of some changes i made in Xposed with Wanam.

I am thinking that i can remove the new Wanam edited features.xml, and remove the ".bak" extension from the old file then edit that one
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeremyds45:
Pulled a noob and updated wallet yesterday, now I no longer have nfc tap to pay, what can I do? Redo everything? Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bajanman:
Yes basically you'll need to delete the installed one...:(

Then just push the new modded V151 into your system.

Whatever you did to get it to work, just redo those steps...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theramsey3:
I did the same thing. Just go to play store, search for google wallet, then click on uninstall, it will uninstall the update you took. You then need to open the wallet app on the phone which is still there cause it only uninstalled the update, sign back in, enter your pin and click on setup tap and pay. You should be good to go from there...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] llama555:
Anyone get [MOD] Google Wallet 2.0-R151-v8-update to work on the Verizon version? Specifically the new Alliance 21 Rom by Beans?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adsbar:
Sadly, no luck on Alliance 21 from here.

Reset GW on beans20

Flashed Alliance 21

Installed modded nfc-access.xml to system/etc

Flashed latest modded GW

Tried it - tap and pay setup failed

Installed modded feature.xml

Flashed NFC fix in recovery - reboot

Tap and pay setup failed

Bad order of events?

Any ideas?

Alan

I just did 2 things, and got my tap and pay working:

1. Turned on S-beam

2. Flashed this zip in recovery

http://xdaforums.com/showpost.php?p=50046810&postcount=404&nocache=1&z=2217255807481706

I realize that S beam should make no difference, and the flashable zip is just a repeat of my steps above (in a very convenient format). I must have messed up one of the steps. However, it worked for me.

Alan
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ddurandd:
Hope this isn't a dumb question, but is there a way to have Play Store update all apps except Wallet? I know how to disable automatic updates, but I'd like the rest of my apps to update automatically.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
No there isn't. But if you use the latest version in the app thread, the play store won't be able to update it.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chalky7880:
Worked flawlessly. Thanks loserskater.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
Wha.... The version for the S3 doesn't work that way! The app store is trying to update it, which like the guy above said, is a pain because you can't just stop that one download.:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
Have you looked in my app thread? There's an update that involves nfcee_access.xml and installing the app like a regular app, not pushing to system.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
That's it! I pushed it to the system. Sorry about that!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bramton1:
I tried this with Wicked, but had some issues with features.xml, Tap and Pay ultimately failed to set up.

1. On Wicked, the file appears to be feature, not features.

2. There is no section marked NFC. Just the tags.

3. Here are the tags in feature.xml I found that I think are related.

<CscFeature_NFC_SetSecureEventType>ISIS</CscFeature_NFC_SetSecureEventType>

<CscFeature_SmartcardSvc_SetAccessControlType>GPAC, MODE1</CscFeature_SmartcardSvc_SetAccessControlType>

<CscFeature_SmartcardSvc_HideTerminalCapability>eSE</CscFeature_SmartcardSvc_HideTerminalCapability>

<CscFeature_NFC_CardModeRoutingTypeForUicc>ROUTE_ON_WHEN_SCREEN_UNLOCK</CscFeature_NFC_CardModeRoutingTypeForUicc>

<CscFeature_NFC_EnableSecurityPromptPopup>all</CscFeature_NFC_EnableSecurityPromptPopup>

<CscFeature_NFC_EnableInvalidTagPopup>true</CscFeature_NFC_EnableInvalidTagPopup>

I edited the first tag to GOOGLE and the second tag to NONE. The third and fourth tags I replaced with the comparable ones in the OP. The fifth and sixth I deleted.

Help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
Wallet Update

OP, did you get the email from Wallet that explains why Tap and Pay may not work for devices running anything less than KitKat in future? Will this affect us using the modded app?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ddurandd:
Google Wallet stopped working for me on April 14th. I thought it was me at first, but then I saw this:

http://www.phonedog.com/2014/03/14/google-wallet-tap-pay-feature-to-stop-working-on-pre-android-4-4-devices-starting-april-14/

I'm on Intergalactic 4.1 which is a TW 4.3 variant

Anyone else having trouble on 4.3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ddurandd:
So I went to the AT&T store today and got a free replacement SIM with the ISIS security feature.

I downloaded the ISIS app, but got the error saying my phone was rooted.

I then installed the rootcloak Xposed module and added Isis to the list of apps that I hide root from.

The rest was the same as Wallet - register, add a credit, and Tap and Pay success!

It worked at CVS just now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] draexo:
I thought ISIS was a Verizon product?

I run Slimrom - Android 4.4.2. Still can not get tap n pay to work. It says it's set up but it won't work at checkouts like it used to. I'm on Verizon.

Sent by my SlimKatted S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bajanman:
Look at the link 2 post above yours!!

Google stopped it on any 4.3 device, so tap& pay will only work on official kit-kat!! Not CM or Asop kit-kat. True kit-kat touchwiz...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] draexo:
I took that to mean any 4.4+ would work. Including ASOP and CM. What I am saying makes sense as there is no 4.4 Touch Wiz.

Sent by my SlimKatted S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ddurandd:
ISIS is used by Verizon, AT&T and T-Mobile
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
This is a bummer, Google meant business! I intend to go to the T-Mobile Note 3 soon, I wonder if that has Kit-Kat available? I'll wait till that day comes. Miss my Wallet!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bajanman:
+1[emoji106]

Wallet[emoji19][emoji53]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RaymondPJR:
Great, I got my Note 3 about a week ago only to find out it has a chip that doesn't work with Google's new security feature that carriers can't block and allows Tap and Pay to work on Kit-Kat! It's said the drivers may be put into the next Kit Kat update, but we all know how long that takes!:crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amart79196:
A week ago the att s3 released this:

"Android™ 4.4.2 KitKat upgrade is available for the Samsung Galaxy S® III (AT&T)(SGH-i747). "

So, that would be a s3, with official kitkat and touchwiz. I guess maybe looserskater could possibly port this fix over to T-Mobile version for a fix possibly?

Or do we need to wait for T-Mobile to have an official update done as well?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] apraetor:
Sure there is.

1. Go to the Google Wallet page in the Play Store app

2. Press the menu key

3. Uncheck "autoupdate"

Note: This only works if you have autoupdate enabled globally in the Play Store app preferences. If you have autoupdating disabled, and normally install updates by pressing "update all" on the My Apps page of the store then you're SOL. This is because when you disable autoupdating of all apps what the Play Store app is actually doing is just unchecking the "autoupdate" tickbox of all your apps.
[General Questions and Answers] sunshine9:
I bought a second hand S4 mini, which apparently is locked to a foreign provider (not available in my country). Nice surprise that was. Trying to fix this, I rooted my S4 mini I9195 succesfully (I think). I flashed "recovery-clockwork-6.0.3.7-serranoltexx.tar.zip" and "S4Mini_RootKit_v1.zip", without any special warnings or issues. So far so good.

However, if I reboot my phone after the flashing, it still gives a warning message that a simlock is present. I was assuming that by installing the rooted firmware the simlock would be removed as well, but apparantly I am still missing something. Could you guys give me advice how to proceed?
[General Questions and Answers] Lgrootnoob:
I believe that a "simlock" is at the hardware level.

So flashing any software will most likely have no change.

I found this

^It's for the note 3 but it has some interesting links in the article.

Have fun!
[Moto X General] Adam7986:
I am seeing tons of the battery life threads, which to be honest, was expected. and I just wanted to put this in perspective for you guys. Currently, I own a Galaxy Nexus, but I am getting a Moto X within the next few days thanks to Moto's Cyber Monday (Wednesday) deal. My battery life average is about 4.5 hours with 1 hour SOT on a full charge. This is not my bad or minimum. This is my average. I spend half of my workday with my phone off and I never leave a charger behind lol.

So in summary, your battery life is still amazing to me if you get 14 hours with 3 hour SOT or anything better and I am really excited to not carry a charge cable everywhere lol
[Moto X General] phositadc:
I LOLed.

Sent from my XT1053
[Moto X General] eeshlikhith:
You should see Moto Gs battery life :|
[Moto X General] jimmyhauser:
I am generally happy with battery life. But every so often I will see my battery drain about 30-40% overnight. I assume it is a wifi or cellular issue as it also happened on my gs4 and nexus 4. Never happened on any of my iPhones or windows phones though. I assume android's modem software is just poorly written.
[Verizon HTC One (M7)] pointedge:
My phone has been stuck on the pouring screen for a while now, i want to to unplug and reset it and retry rumrunner, but there was a warning not to unplug. Currently my phone is displaying the htc logo on a black background and the program is on pouring <3> for maybe 30 min. Can I unplug, or is there a procedure to cancel rumrunner?
[Verizon HTC One (M7)] HypostaticOnion:
Sounds like it's in ruu mode which is weird...

If I've helped, please hit the thanks button
[Verizon HTC One (M7)] karn101:
I did when I first did mine. Was stuck in pouring for about 15 minutes and I unplugged it, but I wasn't stuck in RUU like you are. I'd unplug it. Verify you're running the correct version as well.
[Verizon HTC One (M7)] pointedge:
I ended up just unplugging it and doing a hard reset and retrying. I reinstalled HTC drivers and resarted, also had to turn off fastboot verification, enable debugging, and turn off "fast boot" under power settings. Minimal ADB and Fastboot is also easier and smaller to install instead of the full Android SDK from google, since that's all you need for this. Hope this helps someone else stuck in the situation. I asked in IRC and they gave me the reset advice, but said not to close rumrunner and leave the phone plugged in during the reset, that might also work.
[Nexus 5 Q&A, Help & Troubleshooting] JayHall2502:
Has anyone else experienced when trying to share something from 1 app to another that hangouts is the only option available? I've noticed this problem with Plume, Chrome, and a few other apps. When in the Pocket app, it works like it should though. This is the only bug I've notice with Hangouts. I'm rooted and have Xposed Framework with just Advanced Power Menu downloaded. I actually like using Hangouts despite some of the other problems I've heard about (but not experience). Wondering if there's something I can do to fix this.
[Nexus 5 Q&A, Help & Troubleshooting] Valdeck:
Not a issue here. It is the first in my list but if I use the down arrow I can't fit all the options on my screen
[T-Mobile, Samsung Galaxy SIII] loserskater:
This nfc fix is designed for 4.3 TW roms.

For older versions, see here: http://xdaforums.com/showthread.php?t=1769083

Install Instructions:

Navigate to /system/csc

Open features.xml

Look for <!-- NFC -->, and replace that section with the following:

<!-- NFC -->
<CscFeature_NFC_SetSecureEventType>GOOGLE</CscFeature_NFC_SetSecureEventType>
<CscFeature_SmartcardSvc_SetAccessControlType>NONE</CscFeature_SmartcardSvc_SetAccessControlType>
<CscFeature_NFC_DefaultCardModeConfig>ESE</CscFeature_NFC_DefaultCardModeConfig>
<CscFeature_NFC_CardModeRoutingTypeForEse>ROUTE_ON_WHEN_SCREEN_ON</CscFeature_NFC_CardModeRoutingTypeForEse>
[COLOR="Red"]<!-- If you want the NFC icon in the statusbar add this line, otherwise remove it -->[/COLOR]
<CscFeature_NFC_StatusBarIconType>Att</CscFeature_NFC_StatusBarIconType>

Download file below

Flash file in recovery

Install wallet by following the instructions here: http://xdaforums.com/showthread.php?t=2457569

Notes:

If you installed any other nfc fix, you'll need to revert back to your rom's "stock" system. Just flash your rom again.

This will work on either odexed or deodexed roms, as it will remove any associated .odex files.

Devs:

This is a modified Nfc.apk taken from a Sprint build.

Here's a rundown of what's happening:

NfcService looks at /system/etc/nfcee_access.xml and checks for the Google wallet signature.

It also looks at /system/etc/security_nfc_profile.dat for certain files and their sha-1. If it can't match the file with it's sha-1 it marks the system as tampered and will not allow access to the secure element.

This modified Nfc.apk will always return true when it looks at security_nfc_profile.dat.

To-do:

Create a script that will modify features.xml during install.

Download:

SGS3_4.3_TW_nfc_fix.zip
[T-Mobile, Samsung Galaxy SIII] 4Orr:
As always, great work, Loserskater! You are a great Dev!
[T-Mobile, Samsung Galaxy SIII] krad42:
Awesome was able to actually setup tap and pay. Running tmo s3 tw 4.3 doc holiday deodex ROM. Still need to test paying with it.

Thanks

Tested out actually paying with this at Walgreens worked perfectly. Phone was unlocked, once tapped took me to wallet to input pin. Worked great. Thanks for the mod op.
[T-Mobile, Samsung Galaxy SIII] j.c.briggs:
I didn't see a thread like this in Sprint SGS3... will it work to correct the NfcPaymentSetupFailure: 1 issue?
[T-Mobile, Samsung Galaxy SIII] loserskater:
It should work fine on Sprint as the files were pulled from a Sprint build, but it's worth a shot

Sent from my SAMSUNG-SGH-I747
[T-Mobile, Samsung Galaxy SIII] aswin.dwarakanath:
Worked Great!

Works great on a TMO Galaxy S3 (Rooted stock 4.3 ROM).

Tap and Pay just finished setting up. Haven't tried a transaction yet. But looks good so far.

Update : tried a transaction at cvs and it worked great.
[T-Mobile, Samsung Galaxy SIII] red rocket:
Works on 4.3 T999L stock rooted.
[T-Mobile, Samsung Galaxy SIII] StrikeWun:
:good: worked on my g3 sgh-t999 rooted stock 4.3
[T-Mobile, Samsung Galaxy SIII] aswin.dwarakanath:
Update to Version - 2.0 R 151 v8-Release?

I see the above update in the play store and I did not update yet. Is it safe to update?
[T-Mobile, Samsung Galaxy SIII] loserskater:
No, don't update through the play store. Go to my wallet thread for any updates.

Sent from my SAMSUNG-SGH-I747
[T-Mobile, Samsung Galaxy SIII] thegreatkazoo:
says its setup. will try a purchase tomorrow.

Followed the instructions to the t. hope it works.

gs3 on stock 4.3 rooted with clockworkmod
[T-Mobile, Samsung Galaxy SIII] masondoctorjt:
Whenever I open Google wallet now after updating according to this thread, I get a sign in error, but everything seems to work. I haven't tried tap to pay though, but it says it set up correctly.
[T-Mobile, Samsung Galaxy SIII] loserskater:
It happens to everybody, and it doesn't affect anything. Just back out of that screen. Tap and pay still works.

Sent from my SAMSUNG-SGH-I747
[RAZR i Q&A, Help & Troubleshooting] Stanz3k:
I'm wondering if anyone can figure out how to remove (or set to " ") the carrier name of the notification bar, without unlocking the bootloader. Root can now be achieved thanks to jcase's TwerkMyMoto.

I've tried Xblast Tools and this. The carrier name can be changed everywhere but the notification bar it seems using XBlast tools.

Any help?
[RAZR i Q&A, Help & Troubleshooting] alienyd:
search around in here for modded systemUI with carrier removed :)
[RAZR i Q&A, Help & Troubleshooting] rodrigoauditore:
There is a way to change it with Modaco Toolkit or with Carrier Changer ;)
[RAZR i Q&A, Help & Troubleshooting] Stanz3k:
Only one I can find that will work on odexed roms is this. But don't I need to be in recovery mode to modify these files? I assumed they would be in use otherwise.

If it doesn't work with XBlast tools carrier name changer is it going to be any more likely to work with Modaco Toolkit? For Carrier Changer all I can find is this?
[RAZR i Q&A, Help & Troubleshooting] rodrigoauditore:
You can always try, It's part of xposed

Enviado desde mi XT890 mediante Tapatalk
[RAZR i Q&A, Help & Troubleshooting] Stanz3k:
Modaco Toolkit actually worked. Thanks for that suggestion :)

That's my #1 thing I wanted done. Though I am somewhat interested in some of the other tweaks now.

So my next question is: Am I under the right impression that I will never be able to access adb in recovery mode without first unlocking my bootloader? This seems to be the most limiting thing.
[RAZR i Q&A, Help & Troubleshooting] dagoban:
What exactly do you mean?

Its possible to have adb su access with a locked bl, what else do you need?
[RAZR i Q&A, Help & Troubleshooting] Stanz3k:
Any idea what I am missing then? when I reboot to recovery my ADB does not see my phone.