yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] RJV3:
Does anyone have the old apk of wallet that doesn't include the old Xposed framework apk. I'm running hyperdrive 10 and it includes xposed. I'm trying to install the old wallet but whenever I flask the last night in the op., my xposed gets jacked and nfc doesn't work.
[Verizon Samsung Galaxy S 4] brizey:
Try flashing it while you are still in recovery and before you ever boot the ROM. That seems to solve a lot of these problems on ME7 and AOSP based ROMs. I just started doing it as a matter of course.
[Verizon Samsung Galaxy S 4] RJV3:
I think it may be the zip file itself. When I flash in recovery and reboot to install the region and root check disabled, my nfc is jacked. It always used to work before. I can't figure out why now it's acting up?
[Verizon Samsung Galaxy S 4] Bait-Fish:
Open the zip on a PC in WinRar and delete the Xposed installer within.

I also had the same behavior, NFC not working with the downgraded Wallet on TW. I never did figure it out either. Tried all sorts of combinations too, hybrid new/old, never could downgrade.
[Verizon Samsung Galaxy S 4] RJV3:
Thanks for the tip. But if the old wallet apk breaks nfc then it's a bit pointless. New wallet apk does not seem to work when running elite or ktoonz kernel, both which allow for Smart features to work properly. Not sure why, but new wallet apk apparently works if running stock optimized kernel.
[Verizon Samsung Galaxy S 4] ssn713:
Is it the old wallet apk that is borking the nfc or is it that the zip from the OP also includes an older version of the exposed installer that's not compatible with 4.3 roms?
[Verizon Samsung Galaxy S 4] RJV3:
It's the apk that breaks nfc..... I'm not on a 4.3 rom. I'm on hyperdrive 10. 2 which is 4.2.2 based. Hyperdrive comes with xposed. The old apk would just flash the older xposed framework which can easily be updated from the download section of the framework. It's when I flash the zip nfc breaks. I cannot figure it out. The old apk worked fine on hyperdrive 9.1, then 10. Breaks on 10.1 and 10.2. The new apk of Google wallet. Sets up fine, but the transaction won't go through. Really hoping someone can help me with this issue as no one has been able to help for either old or new apk.
[Verizon Samsung Galaxy S 4] tech_head:
Take a look at this http://xdaforums.com/showthread.php?t=2454971&page=26

I have the new version working on MI1 with no issues.

I had to do it manually though.
[Verizon Samsung Galaxy S 4] Parafly:
Hey guys, sorry for jumping in, i had this working on my s4 however I had to make a warranty replacement. I was still on VRUAMDK. the original build. when i get the new phone, if it's on a newer version, is it still possible to get Wallet working, even with the newer revised wallet APK that lets you send money store cards etc\

EDIT: I see the new thread for the new version here --> http://xdaforums.com/showthread.php?t=2454971
[Verizon Samsung Galaxy S 4] dled1286:
Hey guys and just wanted to throw something out there. I just updated my phone to the latest Slimroms 4.4.2 Beta and Wallet from the play store is working beautifully. I know that all of the carrier versions of JFLTE are supported on Slimkat and the Kitkat base is alot more efficient as well so it might be worth looking into for some of you guys
[Verizon Samsung Galaxy S 4] will.bates94:
So how do I stop my nfc from stopping because it's leaving my phone completely unusable.
[Verizon Samsung Galaxy S 4] bmforrest:
Installation without a custom recovery

So, what happens if you try this without a customer recovery? I'm asking for a friend :) .....ok you got me. So now i have really hosed things up. My phone goes into a continous error of "Nfc stopped working. rendering the phone unusable. I;ve tried to wipe the phone and hard reset and nothing is working. Anyone have any ideas?
[Verizon Samsung Galaxy S 4] tech_head:
Do a No-Wipe install of the stock firmware. Search is your friend.

The stock install will put everything back that was modified.

A hard reset won't fix software/libraries, etc that have been moved or modified.
[Verizon Samsung Galaxy S 4] bmforrest:
Is it possible to flash a stock rom with a locked bootloader.I'm running I545VRUEMK2. I've tried to use ODIN and I keep getting an error something having to do with MAGICCODE. I've been reading that means it's locked.
[Verizon Samsung Galaxy S 4] tech_head:
If you are on MK2, you should be able to flash MK2. You can't go backward.

No Wipe MK2 -> http://xdaforums.com/showthread.php?t=2578209

Saferoot -> http://xdaforums.com/showthread.php?t=2565758

Google Wallet Patch -> http://xdaforums.com/showthread.php?t=2454971

GS4 Tether Unlock -> http://xdaforums.com/showthread.php?t=2512981
[Verizon Samsung Galaxy S 4] pradip.108:
Nice
[Verizon Samsung Galaxy S 4] JT114881:
Hey thanks for the quick fix. It did not brick the NFC but now I get the following error when I launch Wallet:

"Insufficient Privileges

Insufficient secure element privileges for this system image (test-keys)"

I restored from a backup before trying the method 1 again with your fixed ZIP.
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Just curious, can you try the same but this time flash the TouchWiz version instead and let me know? Also clear data/clear cache on Google Wallet in the Application Manager before doing that.
[Verizon Samsung Galaxy S 4] JT114881:
Working on it as I type this.

---------- Post added at 10:54 PM ---------- Previous post was at 10:26 PM ----------

Tried the ASOP version again after clearing wallet settings with the same results. TouchWiz version causes NFC service to crash over and over.
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Yeah I figured the TouchWiz version wouldn't work just thought it might be worth a try. The thing with the AOSP version is that it has to work already from the beginning with that ROM or it won't work at all, the main thing I'm doing on the AOSP version is just flashing the latest version of Google Wallet and just patching it to remove root/device/region checks (the same thing that worked for the Verizon Galaxy S III AOSP ROMs). But with every AOSP ROM your mileage may vary since each one is very customized to particular things. It should work for most though. Let's see if we can some people to test on some other AOSP ROM's before I remove it.

EDIT: Try just flashing your ROM clean again, clear data/cache/uninstall Google Wallet, and see if you can get Google Wallet from the Play Store (without my mod) to show you a different message. If it shows you the same one then that ROM just doesn't have the necessary support for Google Wallet.
[Verizon Samsung Galaxy S 4] JT114881:
It shows that it is not compatible with my device. This is the same message it shows on my current nandroid restore before I flash any of the mods here.
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Now just try Step 4 from Method A, then reboot and try again.
[Verizon Samsung Galaxy S 4] tonu42:
Swag! Glad to see lots more people can benefit from us over at the S3 area!
[Verizon Samsung Galaxy S 4] open1your1eyes0:
The creator has risen!
[Verizon Samsung Galaxy S 4] BusyPooping:
ugh, ive been at the verizon logo for 30 minutes after the xposed framework steps. what should i do?>
[Verizon Samsung Galaxy S 4] xXPrOwLeRXx:
Flash stock image via Odin
[Verizon Samsung Galaxy S 4] iSaint:
Tried on att cm nightly and task aokp (att) no luck :(

Insufficient privileges
[Verizon Samsung Galaxy S 4] BusyPooping:
i dont think i have to go that far... i was hoping to avoid wiping data/ etc. with my rom.
[Verizon Samsung Galaxy S 4] xXPrOwLeRXx:
Restore a backup? I bricked mine twice now one before making a back up and the other I restored the back up. Both when changing the build prop file back to original.
[Verizon Samsung Galaxy S 4] BusyPooping:
mine happened after i did install/update xposed whatever. now i think its working.im trying not to restart from scratch.

im stuck at step 10 on the A list.
[Verizon Samsung Galaxy S 4] N00dle:
Haven't set up a card yet but it installed and runs just fine in TW for me
[Verizon Samsung Galaxy S 4] dseda86:
Works perfect on odex stock
[Verizon Samsung Galaxy S 4] f4s7d3r3k:
Just wanted to post that I did get this working on my Canadian variant, now just to test it out somewhere...

Thanks!
[Verizon Samsung Galaxy S 4] neincraft:
Confirmed working on ATT S4 stock. Using twrp to make a backup. I have a question though

If I accidentally install a new rom without resetting wallet, would I be able to restore back to when I had wallet and reset it, to unbrick the secure element? Would that work?
[Verizon Samsung Galaxy S 4] brizey:
Man it takes forever to reset.
[Verizon Samsung Galaxy S 4] N00dle:
Not to sound ungrateful or paranoid to the creator of this bypass but since this is a modded version is there by chance an issue of security with credit card info?
[Verizon Samsung Galaxy S 4] brizey:
OK...it reset Wallet (the service, not the app) just fine. You can check to see it if reset on the web under wallet/devices. It should say that the device has been removed from service.

I THINK this means you are good to go in terms of the secured element.

The reset hangs on the resetting of the app itself...at least it did for me. So I killed it and cleared the data.

I am all set up now on CleanROM, so what I did seems to work. I think the key is checking the website to make sure the device has been removed from your account. There is obviously a two-way communication happening between google and the phone (in particular the secure element). I am by no means an expert, but it sure made me feel better to see that the Goog had acknowledged that the device had been reset.
[Verizon Samsung Galaxy S 4] BusyPooping:
build.prop wont save.... anyone know what to do?

Im using root explorer and everytime I edit it and save, it doesn't show changes.
[Verizon Samsung Galaxy S 4] f4s7d3r3k:
Just download buildprop editor. Its the first one in the play store. I was having the same error
[Verizon Samsung Galaxy S 4] BusyPooping:
ok now its saying make sure i have network access? Im pretty sure i have network access

---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------

nevermind, im retarded. i got it working
[Verizon Samsung Galaxy S 4] ticrandall:
Ok, so everything seemed to work.. but I can't seem to use it. Tried at two places now and I put my phone up to the pad thing and nothing.. am I doing something stupid? My card is set up, nfc on.. and nothing happens.. any ideas?
[Verizon Samsung Galaxy S 4] f4s7d3r3k:
Didn't work in Canada

Unfortunately I was unsuccessful in paying at two places. I tried with two different credit cards that I have in my wallet, screenshot attached of what came up on my phone.On the reader it said something along the lines of tap not recognized. Any ideas?
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Has anyone else whom this method has actually worked had any success or difficulty actually purchasing something? I know sometimes with previous devices I've had issues with certain places where their NFC readers are just not working properly (even places that have worked before). I'll be honest I have yet to actually get a chance to test it myself for purchasing (that's usually the easy part), one person claims purchasing was successful for them. I'd like as much feedback as possible before I change anything else.
[Verizon Samsung Galaxy S 4] dseda86:
My transaction went through at a Duane reade but also received the message up top. Fortunately it was a successful transaction. It may have been because I forget to hit yes on the keypad? Idk. It worked but I've never received the above message before.
[Verizon Samsung Galaxy S 4] qman66:
it does have 4.2.2 in aosp
[Verizon Samsung Galaxy S 4] slackwaresupport:
worked fine. wallet ran, i setup my cards, etc.. moved build.prop back, rebooted, now it says unsupported device again and kills itself.
[Verizon Samsung Galaxy S 4] iSaint:
Can confirm working on att deodexed rom tested 1 min ago and I got a slurpee :D

Thanks man
[Verizon Samsung Galaxy S 4] middmd:
Worked and used it at Wegmans using method A. Method B didn't work (looked like the script wasn't mounting /system as R/W before attempting to edit build.prop
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Found, fixed, and reuploaded the fixed scripts. :good:
[Verizon Samsung Galaxy S 4] Bjray:
Worked perfect on ATT Galaxy S4 running SlimBean. Thanks!
[Verizon Samsung Galaxy S 4] JT114881:
Anyone get this working on Slim bean?

Also, was AOSP fixed again today?
[Verizon Samsung Galaxy S 4] open1your1eyes0:
No changes to AOSP just yet, just fixed the scripts but forgot to edit the reason on OP. Looks like one user above got it working not only on SlimBean but on AT&T version as well.
[Verizon Samsung Galaxy S 4] hamenoskili:
Installed successfully on stock rooted, Havent had a chance to test yet. On a side note my build prop changed back to the original settings automatically. Any ideas?
[Verizon Samsung Galaxy S 4] FAUguy:
Method A worked on GS4, stock ROM, rooted/unlocked.
[Verizon Samsung Galaxy S 4] morbidz:
worked in 7-11, Wawa, Hess, random vending soda machines. I'm on stock rooted AT&T
[Verizon Samsung Galaxy S 4] slackwaresupport:
this is what i get:

http://i.imgur.com/Pm74GNY.png

works fine until i restore my build.prop and reboot
[Verizon Samsung Galaxy S 4] dansan382:
I found the first "drawback" of doing this method and getting google wallet to work.

Since I got the device, when viewing my devices on the play store website the S4 never had a phone icon identifying it. Today for ****s n giggles i checked it out, guess the phone registered on play site as a galaxy nexus since doing the build prop changes. Not sure if I can get it to change back or if it will do it on its own.
[Verizon Samsung Galaxy S 4] open1your1eyes0:
I think the idea is you have to register the phone with the play store first before doing this Google Wallet mod. Checking in my Play Store it has been registered as SCH-I545 and still remains the same even after I have applied the Google Wallet mod.

I actually own a Verizon Galaxy Nexus device as well so you can ignore that one.
[Verizon Samsung Galaxy S 4] dansan382:
register the phone? I thought just signing into the phone and using it locks it in. It was showing as a S4 before i did the mod and now it switched. what process did you do to register the phone with Google Play?

Edit: on wallet.google.com it shows it as a Galaxy Nexus as well
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Sorry, that's what I meant, to sign-in first time. I'm not sure if you changed your build.prop back after the mod, you may just want to double-check on what it's current set to just in case. Other than that I'm not really sure why that changed then. I'm not sure if mine changed also when I did the mod but it's definitely back as it should be now. It has been about a week I would say.

EDIT: On Google Wallet site mine shows up as a Galaxy Nexus, but that's obvious because it was setup on our devices when it was shown as a Galaxy Nexus. Not too big a deal there, but should definitely be SCH-I545 on the Play Store device list.
[Verizon Samsung Galaxy S 4] dansan382:
nope, build prop lines look good.

honestly its not a big deal regardless. play store still works, so its whatever. maybe it will change, as i haven't had the mod in as long as you.
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Maybe it just takes time to propagate after a change. Maybe if you buy or download something it will cause the change as well.
[Verizon Samsung Galaxy S 4] dansan382:
Yea thats what I'm thinking.. I've downloaded plenty of apps so maybe after I buy something it might change. Like I said, not a big deal.. if it changes it changes, if it doesnt.. whatever
[Verizon Samsung Galaxy S 4] greenzone560:
This is how all problems should be resolved on XDA...there would be much less problems then.

Thanks btw, I just switched to CM 10.1 as it is officially supported (yay!) I am on AT&T I will try it out right away and repost back if it works. I've tried all other fixes and I either get the "data not setup properly" error, or "release- keys not supported" error so I hope this works! Cross your fingers!

I can confirm that this patch works on AT&T CM 10.1 build 6/3/13 even after the change of build.prop
[Verizon Samsung Galaxy S 4] Spunjah413:
Just wanted to say thanks!

Setup went flawless using ATT on Slim Bean V6. I'm not sure if it works, but everything installed smoothly and wallet app still functional after changing build.prop back.
[Verizon Samsung Galaxy S 4] brizey:
Used it today for the first time at the cafe at work. No issues...worked perfectly.
[Verizon Samsung Galaxy S 4] loonie01:
I was thinking the same thing. On the GS3, there was only one modded app to use. Here there is 2. What is the Xposed app do?
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Just wanted to let everyone know I have now added a video tutorial of the full process to the OP with big thanks to my good friend DroidModd3rX. Please feel free to comment and let me know if you guys have any questions or if this video helped please feel free to like and give credit to DroidModd3rX on his youtube channel. :good:
[Verizon Samsung Galaxy S 4] slackwaresupport:
ok.. 3rd time installing.. i get this on the initial run.

http://i.imgur.com/o9SbBus.png

says unsupported device at the top.. i noticed in the video, it doesnt. can anyone confirm this?

edit:

i think i got it.
[Verizon Samsung Galaxy S 4] brizey:
Mine said that i think and I have used it for purchases. I think it has to do with being rooted, IIRC from when I set it up for my N7 almost a year ago.
[Verizon Samsung Galaxy S 4] open1your1eyes0:
In case anyone is concerned or interested in how Xposed Framework works, here's a great explanation: http://www.howtogeek.com/164634/for...e-the-xposed-framework-to-tweak-your-android/
[Verizon Samsung Galaxy S 4] loonie01:
Thanks for that link.
[Verizon Samsung Galaxy S 4] AGunz82:
Same here, bummer.
[Verizon Samsung Galaxy S 4] Bert336:
OP..

You forgot one step on your video....

-After Wallet and Xposed is flashed... Open Xposed and select "Install/Update" and Reboot.

THEN

you can install Wallet patch.apk and select it under Modules...

I was stuck on the previous message as AGunz82 aswell...

until i did what i mentioned above..

thanks
[Verizon Samsung Galaxy S 4] AGunz82:
Nice! Was just going to post this. ?
[Verizon Samsung Galaxy S 4] brizey:
I know some of you are concerned about security, but frankly, you take a bigger risk every time you let a waiter walk away from your table with your credit card.

Just make sure you use a credit card and not a debit card (still have not figured out why those exist when credit cards are superior in every way, but to each his own I guess). Its a PITA if you get fraudulent charges (I just went through that with my main card), but really, the actual monetary risk is basically zero.
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Hmm good point I just noticed that as well. I'll see if they can make an edit of it in the video.

EDIT: I informed them, they will make a note/annotation in the video.
[Verizon Samsung Galaxy S 4] cashyftw:
Worked for my tmobile galaxy note 2, thank you!
[Verizon Samsung Galaxy S 4] ViperGeek:
Confirmed functionality on the overpriced vending machine at work. I logged into GW, typed in my PIN, held the phone up to the vending machine, it vibrated, and within two seconds I had a $1.50 bottle of Aquafina.

Stock (ODEXed) rooted ROM (VZ MDK) with the aforementioned wicked awesome Xposed patch.

- Dave
[Verizon Samsung Galaxy S 4] brizey:
And people are worried about someone stealing their money with a shady app...Pepsi beat them to it! lol :silly:
[Verizon Samsung Galaxy S 4] KryptosXLayer2:
I keep seeing that people are getting this working with "stock odexed rooted AT&T ROMs," but they're not saying if they're on MDB (DB) or the MDL (DL) update. I'm on MDB and the BEST I've been able to do is have the "Setting up wallet...." screen running for the last 17 mins, the worst is after about 2 mins on this screen, it pops up with "Device Not Ready" as someone posted they have had issues with on all the other Wallet patched threads! Am I the only @$$hole still left on MDB, did you all update and I'm the only one getting this hangup?

Also, this isn't my first time setting up Wallet on a device it wasn't meant for, I did it almost a year ago with my SIII, and have gone through these similar steps every time I have updated the ROM, so I know what I'm doing with this, please don't suggest simply reading the OP again and following the steps, I've tried doing this 4 times tonight thus far following the steps line-by-line..... The video wasn't much help either since it was littered with mistakes, so I've ignored everything I saw and followed the directions instead only to be sitting here for now 22 mins on the "Setting up Wallet...." screen!

EDIT - well F me.... after being stuck on that page for long enough, I decided to reboot one more time without doing anything different, and Wallet fired right up into the login screen! Got it working on MDB on AT&T stock odexed rooted! Leaving thanks now, great work and further proof that there isn't a need to upgrade yet
[Verizon Samsung Galaxy S 4] Matt4542:
Insufficient secure element privileges for this system image (release-keys).

I keep getting this error. I've tried 3 times now.
[Verizon Samsung Galaxy S 4] open1your1eyes0:
So I understand you guys are having some trouble with the current video that was up. In an effort to prevent further confusion I have updated with one that another user has posted. I have personally checked and made sure it adhered to the guide as close as possible and reflected the same order that worked on my device. Please let me know what you guys think of this new one.

PS

: One thing to keep in mind that with every custom ROM and different device YMMV. The only one I can confirm working 100% (because I have personally tested on my device) is Odexed stock ROM on the Verizon Galaxy S4. The way it is designed deodexed stock ROM should have no issues as well. Regarding AOSP ROMs it depends purely on the ROM itself. The ROM already has to support Google Wallet to some extent or this patch won't work at all. For AOSP ROMs this patch just helps to remove the root message, region check, and device check, but the rest is up to the ROM itself. If properly designed it should have no issues. I think the people with the majority issues may occur on debloated stock ROMs as it is possible they can remove things that Google Wallet requires to work. Once again, just a friendly reminder that with every ROM, your mileage may vary.
[Verizon Samsung Galaxy S 4] owenbeals:
Here is my Video that was removed from the OP incase anyone finds it easier to follow

http://www.youtube.com/watch?v=QABLkgEPfKU
[Verizon Samsung Galaxy S 4] greenzone560:
Backup your data, and flash a CM official ROM
[Verizon Samsung Galaxy S 4] CountParadox:
Australian variant GT-I9505 here, Frequently NFC PAyment.apk will crash, but I restarted my phone a few times, once it didnt crash, and the payment started (but declined because my cards prepaid and empty, haha)

So im pretty sure it works :D

Dont know why it crashed though...
[Verizon Samsung Galaxy S 4] Matt4542:
Did that. Now it reads

Wallet is unable to proceed until the device is fully initialized. Make sure the device has network access and try rebooting if problem persists.

I have rebooted.
[Verizon Samsung Galaxy S 4] slackwaresupport:
i figured it out.
[Verizon Samsung Galaxy S 4] itsdavetime:
Using AT&T S4...

When I install the Wallet zip then reboot, my phone keeps popping up "Unfortunately, Nfc Service has stopped". If I hit "OK", it just pops up again. I'm using Cyanogen 6/5 build.

Any suggestions?

Thanks
[Verizon Samsung Galaxy S 4] slackwaresupport:
nm..nm