NFC proper emulation on Samsung Galaxy Note5 - NFC Hacking

Hello XDA community,
I'm looking forward to try and actually emulate my travel card. It's called a Rav Kav, and the location of it is Israel. From what I've seen you are required to edit the NFC configuration file to somehow maybe emulate a physical card. I tried an app that requires root. It unfortunately shows me a message "NFC configuration file is invalid". So I tried another app. This app might've worked, but I'm not sure because when I tried the scanner app it didn't white register. I'm still experimenting with the app it seemed to work in, but suspiciously it doesn't require root.
I thought of a couple things and I thought maybe entirely flashing a new rom would work? I honestly don't know. And also I'm not planning on using Samsung Pay or Google Pay anytime soon as these two don't support any israelian banks, so what's the point.
Any solutions?

Bump. Wow really old post, but any answers?

Related

Random Google wallet issues???

My experiences with Google wallet have been strange. Here's a run down:
Attempt 1
Went to Macy's, took about 4 tries before it went through.
Attempt 2
Went to meijer, got an error saying card reader could not be detected. I tried several times before giving up.
Attempt 3
Went to 7-11, no problems whatsoever.
Attempt 4
Went back to meijer tried a different checkout lane then the last time. No problems.
Attempt 5
Meijer, one more time went to the SAME lane as the time it worked. Didn't work this time got that error again saying couldn't detect card reader.
Is anyone else's this inconsistent? I don't understand. I unlock my phone, hold it up to the machine until it says sent. Any suggestions? Why is it like this? Everyone else stories I read say it works flawlessly or it doesn't work at all.
Sent from my Galaxy Nexus using xda premium
are you using any particular case, did you update the app to the newest build?
Any errors I've encountered could be chalked up to one of two things. Either the pad was not turned on/not connected (make sure there is a green light on the pad), or the network is down\you dont have a network connection.
The network has been somewhat spotty for me over the last day or two. Today it was down for almost 2 hours. An easy way to tell if the network is down is to look at the app, select payment cards, then choose the card you are using. I use the google prepaid card, tap it and at the bottom under userid if there is a number you are connected to the network.. If the network is down or you do not have connectivity you will see something that says "can't connect to bank". You can not make a purchase if you do not see your userid, I always open the app now and check while I'm waiting in line.
krichek said:
Any errors I've encountered could be chalked up to one of two things. Either the pad was not turned on/not connected (make sure there is a green light on the pad), or the network is down\you dont have a network connection.
The network has been somewhat spotty for me over the last day or two. Today it was down for almost 2 hours. An easy way to tell if the network is down is to look at the app, select payment cards, then choose the card you are using. I use the google prepaid card, tap it and at the bottom under userid if there is a number you are connected to the network.. If the network is down or you do not have connectivity you will see something that says "can't connect to bank". You can not make a purchase if you do not see your userid, I always open the app now and check while I'm waiting in line.
Click to expand...
Click to collapse
Thanks! I'll give that a shot(checking the user id) that sounds like it could be helpful.
@nyplaya
no, I don't have a case and I don't know if I have the latest updated version. I haven't checked because I didn't want to update and become a victim of the secure element error. I'm not exactly sure what the cause is and didn't want to risk it. But if its safe to do so, how do I find out if I have the latest version and where would I get it?
Sent from my Galaxy Nexus using xda premium
daledenton said:
Thanks! I'll give that a shot(checking the user id) that sounds like it could be helpful.
@nyplaya
no, I don't have a case and I don't know if I have the latest updated version. I haven't checked because I didn't want to update and become a victim of the secure element error. I'm not exactly sure what the cause is and didn't want to risk it. But if its safe to do so, how do I find out if I have the latest version and where would I get it?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
you can do one of two things, follow the OP here:
Or you can try my little faster method: not sure if it is for the paid version only but if you download and install the APK of wallet, then use the app appmonster to backup the app, you can then simply select it in appmonster to view in the market and it bi-passes the restriction of the carriers in the normal market app it allows updating

Not sure what's going on, but Google Wallet is now available (but unusable) for T989

https://play.google.com/store/apps/...nb29nbGUuYW5kcm9pZC5hcHBzLndhbGxldG5mY3JlbCJd
I can download it directly from the play store, but still hit the same "device unsupported" message upon startup.
Maybe just a Play Store glitch?
Nope, not a glitch.
U need a secure element to be able to use Google wallet. Since one is not built into the phone a simple card with this feature added on is expected sometime in the future. Until then, no Google wallet
icenight89 said:
Nope, not a glitch.
U need a secure element to be able to use Google wallet. Since one is not built into the phone a simple card with this feature added on is expected sometime in the future. Until then, no Google wallet
Click to expand...
Click to collapse
Yeah I know all of that, but yesterday or two days ago, you couldn't even download wallet officially from the play store. Not sure why they are suddenly allowing it.
they may be opening it up in anticipation for the ics update and some sort of add on for the secure element.
-Mr. X- said:
they may be opening it up in anticipation for the ics update and some sort of add on for the secure element.
Click to expand...
Click to collapse
Yeah I forgot about the possibility of adding a secure element via sd card. That is probably what this is. I'm running the UCLD2 leak and I get the unsupported message (without a secure element, obviously).
algorhythm said:
Yeah I forgot about the possibility of adding a secure element via sd card. That is probably what this is. I'm running the UCLD2 leak and I get the unsupported message (without a secure element, obviously).
Click to expand...
Click to collapse
I figure it will be sd card or sim card update. however maybe samsung will some how make an updated battery that not only has the nfc antenna in it but the secure chip as well.
yea i noticed this yesterday. i made a post but nobody answered . i installed it but it didnt work it said "unsupported". damn i got excited for a minute there
Also TMobile has changed to where you have to purchase 3rd party apps through them using a credit card
Sent from my SAMSUNG-SGH-T989 using xda premium
It is because the unlocked galaxy nexus just came out and can be used on tmobile, so they made it so phones on tmobile can dl wallet, but only the nexus can use it. Hence the error message a couple of days ago, this application is not supported by your carrier. Just a speculation
Sent from my SGH-T989 using xda premium

Root and Google Wallet (also NFC)

I hear that Google Wallet does not work if the phone is rooted. I got unsupported device message. Here's my question :
- Can you use wallet app with rooted phone ? (actual work , I haven't tried yet ; I denied root access but the message still there)
- Do other NFC apps request root to run ?
Nhan Lam said:
I hear that Google Wallet does not work if the phone is rooted. I got unsupported device message. Here's my question :
- Can you use wallet app with rooted phone ? (actual work , I haven't tried yet ; I denied root access but the message still there)
- Do other NFC apps request root to run ?
Click to expand...
Click to collapse
It works fine with a rooted device, it just warns that it's not supported (and links to the article describing the security risks briefly).
In general root access isn't needed for anything NFC related - this was a recent addition to Google Wallet.
So you still can pay with GWallet on root phone :great: I also interested with NFC modding. I see there are many NFC card with vary capability (from 50b to 1Kb) , which one should I buy ? (I'll use for turn Wifi/Bluetooth on/off or Change brightness e.t.c)
Nhan Lam said:
So you still can pay with GWallet on root phone :great: I also interested with NFC modding. I see there are many NFC card with vary capability (from 50b to 1Kb) , which one should I buy ? (I'll use for turn Wifi/Bluetooth on/off or Change brightness e.t.c)
Click to expand...
Click to collapse
There's a thread for that...
http://forum.xda-developers.com/showthread.php?t=1697563
Confused
krohnjw said:
It works fine with a rooted device, it just warns that it's not supported (and links to the article describing the security risks briefly).
In general root access isn't needed for anything NFC related - this was a recent addition to Google Wallet.
Click to expand...
Click to collapse
I have an EVO 4G LTE and prior to rooting I definitely cleared my Google Wallet. But just now since rooting and installing Charmeleon, when I load Google Wallet I get this message:
Not Supported
--------------
Unfortunately, Google Wallet has not yet been certified in your country or on your device / carrier.
Obviously, this is not true, because it worked just fine prior to rooting.
Clicking OK merely closes it out, so how can it still work if I can't go any further?
It can still run up until that verification takes place, I've seen it many times on my sgs2 when we first got nfc enabled awhile back. Anyway to address your problem it could be a couple of things, first thing that comes to mind is your apn settings. My reasoning is you said it worked completely before and you flashed chameleon so the error your getting could definitely be that. Check your apn settings, make sure your connecting to the same servers as before. If that isn't the issue let me know as I don't have your lg so I couldn't tell you if it has something to do with the secure element at this time.
Actually I just did some quick research for you. It seems even people on stock rom are having issues with nfc and not just Google wallet but a lot of reports of not being able to detect nfc cards or other credit cards,pay pass etc. Does your nfc work in any of those capacities? If not I would start there because if that doesn't work Gwallet surely won't. Lastly I just read a few issues in the sprint version of the phones forum on xda people believe there's an issue with the placement. Check it out
Sent from my SGH-I777 using xda premium
Nizda1 said:
Actually I just did some quick research for you. It seems even people on stock rom are having issues with nfc and not just Google wallet but a lot of reports of not being able to detect nfc cards or other credit cards,pay pass etc. Does your nfc work in any of those capacities? If not I would start there because if that doesn't work Gwallet surely won't. Lastly I just read a few issues in the sprint version of the phones forum on xda people believe there's an issue with the placement. Check it out
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Thank you for looking into this, and for discovering others are having issues. I'm not sure how to go about checking my APN settings, but I am looking it up.. so as soon as I figure that out I will post back and let you know what I find lol
---------- Post added at 09:02 PM ---------- Previous post was at 08:57 PM ----------
I believe my APN was and is LTE/CDMA unless I'm miss understanding, this doesn't appear to have changed. As far as the other trial&error's you've suggested, I am going to have to try those later because I am at work for the night, and don't have access to anything here. Thank you for looking into this!
I can't Help You *_*
USAMac said:
I have an EVO 4G LTE and prior to rooting I definitely cleared my Google Wallet. But just now since rooting and installing Charmeleon, when I load Google Wallet I get this message:
Not Supported
--------------
Unfortunately, Google Wallet has not yet been certified in your country or on your device / carrier.
Obviously, this is not true, because it worked just fine prior to rooting.
Clicking OK merely closes it out, so how can it still work if I can't go any further?
Click to expand...
Click to collapse
You can check out my guide here for your answer http://forum.xda-developers.com/showthread.php?t=1810282

[Q] Adding Citi Card to Google Wallet

Has anyone been able to add their Citi MasterCard to Google Wallet lately? I've been trying since June 13th and it just times out. The card does get added to the Google online site. but not on the phone. I'm on the stock Sprint ROM and not rooted. The Google Prepaid card adds fine.
I originally added but then re-installed a rom and when I went to go re-add it I have been getting the same thing. They said its some sort of "out of sync" issue and I have a ticket open but never heard back.
I'd also had my citi card on the phone, but wiped Wallet to update to a newer version of Wallet. Now it just keeps timing out.
I called Citi and they cancelled the association with my phone, but it still just keeps timing out.
The Citi guy said there was a known issue with HTC EVO 4G LTE phones, but that there shouldn't be with mine.
Oh well, guess it's back to plastic until they sort it out.
Same here... Mine gets stuck in adding card. I have opened tickets. It seems to be a Wallet problem. Citi bank reset my account but still does not work. At least the prepaid works.
Ditto. I can add a prepaid card but when I try to add my Citi credit card it hangs every time (after several minutes) with the message "Error Adding Card". Citi says they have resolved Wallet problem with most phones, including the gnex, but they obviously don't know we're rooted. Many ROMs spoof different identification codes for various reasons, which could play a role. For example, the ROM I use shows device as "GT-I9300" and "toro" in the build prop. What do your build props show for device?
I was just now able to add my Citi card to the Wallet app on my HTC One X, so whatever server side issues they were having appear resolved , at least for the time being.
Sent from my HTC One X using Tapatalk 2
distortedloop said:
I was just now able to add my Citi card to the Wallet app on my HTC One X, so whatever server side issues they were having appear resolved , at least for the time being.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You rooted?
I just talked to Wallet support and they said being rooted is the likely reason we can't add a card. Here's the follow-up email Google sent:
"We strongly discourage gaining system-level "root" access to your phone if
you plan to use Google Wallet. We are unable to support devices with
unauthorized operating systems as the security layers of the device may be
limited.
If you have other questions, please reply to this email and I'll be happy
to help. Have a nice day!"
Yes, I am rooted, and using a custom rom.
I had the citi card on this phone with an older version of MoDaCo wallet hack, but lost it when I upgraded to last software hack. It took three days trying, but finally got it to take.
I also have Wallet on my GNex, but just with the prepaid. I don't recall which hack I got it on there with.
You might want to try the MoDaCo hack , it disables three different checks the app makes for root, device and carrier.
Sent from my HTC One X using Tapatalk 2
I am still unable to re-add my citicard. Added and worked fine in May under yakjuxw 4.0.2. But then flashed takju 4.0.4 and I haven't been able to add it back again since. Never been rooted. I had no idea that flashing the US version of software (or any rom) could blow out wallet until after it wouldn't work, I searched and found that the secure element may be blown. Called Citibank twice, sent google feedback twice, posted here in another thread. No help or feedback from anyone so far. I can't even tell if its a Citibank issue, google issue, or an issue caused on my phone because I flashed a new ROM without doing anything to google wallet first. It says verifying card, seems to go on to the next step but then gets stuck at adding card and says unable to add card, call Citibank. I'm not willing to try the prepaid card, for fear of losing any money I put on it. Its been about a month now like this, so I've pretty much lost all my initial trust in google wallet. Nice idea, but completely worthless.
distortedloop said:
Yes, I am rooted, and using a custom rom.
I had the citi card on this phone with an older version of MoDaCo wallet hack, but lost it when I upgraded to last software hack. It took three days trying, but finally got it to take.
I also have Wallet on my GNex, but just with the prepaid. I don't recall which hack I got it on there with.
You might want to try the MoDaCo hack , it disables three different checks the app makes for root, device and carrier.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Tried the MoDaCo hacked Wallet, no luck. I'm thinking all the recent "server issues" are related to Google tightening things up. If anyone really wants to use Wallet, might be best to return their phone to stock. Otherwise, just carry your credit card, it's not very heavy!
madAdam6LOVE said:
Tried the MoDaCo hacked Wallet, no luck. I'm thinking all the recent "server issues" are related to Google tightening things up. If anyone really wants to use Wallet, might be best to return their phone to stock. Otherwise, just carry your credit card, it's not very heavy!
Click to expand...
Click to collapse
LOL to just carry your card line.
There's so few places that I actually go to that have paypass that the Citi card on the pine is really just a novelty. Kind of a geek pleasure. Anyone with these high end phones that reads these forums is probably a cutting edge tech kind of person. We want this stuff to work just for fun.
If the server business is google cracking down, then why did it work for me this morning? I'm on same ROM, same root as when it wouldn't work.
I was going to switch roms today, but now I'm afraid it will break Wallet again.
I don't think Google wants to block anyone. They want people to use Wallet. The only blocks they put in place are to appease the telcos or the bank.
Sent from my HTC One X using Tapatalk 2
Google didn't think it through with Wallet. So many shortcomings.
Sent from my Galaxy Nexus using XDA
distortedloop said:
LOL to just carry your card line.
There's so few places that I actually go to that have paypass that the Citi card on the pine is really just a novelty. Kind of a geek pleasure. Anyone with these high end phones that reads these forums is probably a cutting edge tech kind of person. We want this stuff to work just for fun.
If the server business is google cracking down, then why did it work for me this morning? I'm on same ROM, same root as when it wouldn't work.
I was going to switch roms today, but now I'm afraid it will break Wallet again.
I don't think Google wants to block anyone. They want people to use Wallet. The only blocks they put in place are to appease the telcos or the bank.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You're right on with the cutting edge thing. I used to love to amaze sales clerks by paying with my phone. It was always the first time they ever saw that done.
I'm a bit of a crackflasher but until recently I was always able to reset wallet and then add my Citi credit card, probably did it 10 times. It stopped working with new ROMs at the same time Google was having issues with its server, which is why I'm thinking something's changed on Google's end when dealing with rooted phones and custom ROMs.
As I mentioned earlier, I'm wondering whether the ID info in the build.prop of custom ROMs is an issue. I know the ROM I'm using now identifies my Gnex as GT-I9300. I did try editing the build.prop to stock ID, and also tried the MoDaCo hack which supposedly bypasses such ID checks, to no avail.
Don't think I'm going to waste much more time on Wallet, but I'll keep an eye on this thread in hopes of a fix or hack.
There's certainly several things going on behind the scenes.
Don't forget that if your card is associated with Wallet already, trying to add it will fail. Try too many times and you get locked out for a day.
If a new ROM changes whatever that association indicator is, that cooks be the cause of the failure. Never hurts to call Citi and ask them to reset on their end.
I agree about retail clerks always never having seen pay with a phone before. I always get that "what the heck?" look. One clerk acted like I was pulling some kind of scam.
Sent from my HTC One X using Tapatalk 2
i posted about this issue a couple of months ago...not many people responded to that thread...i added my citi card successfully then reset the app to flash some stuff then when i tried to re-add it, it would give me an error message...i called citi a couple of times and they said they were going to reset it on their end
i tried it again a few weeks later and ever since then it just hangs on the adding card part...it doesnt error out...just hangs...i never got to try it at a store
Im rooted but just. My build is IMM76D.L700FD02. As for rooting what I understood was basically that was google pulling a CYA regarding the security issues with rooting, not that they were blocking the app.
distortedloop, do you get the notification about rooted devices not being supported when opening wallet?
ryan stewart said:
Im rooted but just. My build is IMM76D.L700FD02. As for rooting what I understood was basically that was google pulling a CYA regarding the security issues with rooting, not that they were blocking the app.
distortedloop, do you get the notification about rooted devices not being supported when opening wallet?
Click to expand...
Click to collapse
No, I don't get that warning, but I'm using MoDaCo's hacked Wallet app which disables the root, carrier, and device build checks.
Problem with wallet only with citi card?
It seems based on this thread, it really is only a problem with using the citi card with wallet.
I am using a rooted Nexus with custom rom and wallet works for me.
(Note: I have not changed roms since it has been working.)
redstar427 said:
It seems based on this thread, it really is only a problem with using the citi card with wallet.
I am using a rooted Nexus with custom rom and wallet works for me.
(Note: I have not changed roms since it has been working.)
Click to expand...
Click to collapse
Correct. Problem is adding Citi Card only. Wallet works fine. Prepaid cards add fine. Citi card fails to add after several minutes communicating with the server, returning the message "Error adding card". Initial verification of Citi account information is successful, the failure comes during "adding card to Google Wallet".
madAdam6LOVE said:
Correct. Problem is adding Citi Card only. Wallet works fine. Prepaid cards add fine. Citi card fails to add after several minutes communicating with the server, returning the message "Error adding card". Initial verification of Citi account information is successful, the failure comes during "adding card to Google Wallet".
Click to expand...
Click to collapse
Plus, the problem is just adding the Citi card to Wallet on the phone.
For me, the first attempt to put my Citi card on the phone failed, but the Citi card was added to my Google account online (also confusingly called Wallet now) and was available for selection in the Play Store.
Sent from my HTC One X using Tapatalk 2

[SIM unlocked] LG D693n Stylus turned "partially" SIM unlocked after Super-Sume

[SIM unlocked] LG D693n Stylus turned "partially" SIM unlocked after Super-Sume
I think this is weird enough for a new thread: I recently got this G3 Stylus and, as usual, I proceeded on rooting. This time using KingRoot. Done easily, I must admit. Now, since KingRoot installed some unwanted and "unreadable" stuff, I've turned my sight over Super-Sume (you know what it does)... Super-Sume performed it's job as expected, replacing everything it has to with Supersu. Following the process and right after reboot, something weird happend: my installed SIM card appeared as an "invalid SIM card". Rebooted again and still the same message. Turned off the phone, took the SIM card out, reinstalled, turned on again... same message. Device had lost network connection, but it was able to send and receive data!!!... started research about the particular issue, but found nothing similar anywhere. Then I've tried three SIM cards from different carriers and they worked flawlessly. Installed the "invalid SIM card" again (which is from the phone's original carrier, BTW) and the issue was still there. Then, about 12 hours later, data was lost as well and SIM became useless in this phone. Tested another card from the very same carrier and it was useless to; however, this two cards worked perfectly on three different phones, so not a card issue. Contacted Super-Sume developer and he told me there's NO relation between his app and such kind of issue. OK. Contacted carrier and they know nothing. OK. Next, I resolved to look for some hint at "Replace Kinguser with SuperSu" XDA thread, where fellow member "CVangelo" suggested to check if phone asks for unlock code. Well, it does. So the phone is SIM locked after all, but JUST FOR ONE CARRIER!!! which happens to be the phone's original carrier. Not to blame Super-Sume for the mess. Perhaps is a "gift" left from KingRoot due to getting rid of it. Or perhaps is just coincidental. Point is, this is clearly a weird issue as most of you can see; at least until somebody rises her/his hand with an explanation. Who's first?
CNK80Q3MX said:
Point is, this is clearly a weird issue as most of you can see; at least until somebody rises her/his hand with an explanation. Who's first?
Click to expand...
Click to collapse
Only thing I would say is that it is network locked but in the exact reverse of what you would expect. Never heard of such a thing or knew it was even possible. Is there anyone with experience in network locks who can explain exactly what kind of network lock this? It may help explain what might have happened and how.
Sent from my Nexus 7 using XDA Free mobile app
CVAngelo said:
Only thing I would say is that it is network locked but in the exact reverse of what you would expect. Never heard of such a thing or knew it was even possible. Is there anyone with experience in network locks who can explain exactly what kind of network lock this? It may help explain what might have happened and how.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Hey... no one seems interested. I'm assuming no one will until someone else have the same issue. Though, I've been making some questions to some other "lock acquainted" people and most say it is kinda "blacklisted" lock "for sure". In such cases, the original carrier locks first; if you try another network carrier SIM, it will work for typically 3 to 5 more days and up to 8 (no more than that) then, that carrier will lock as well, and so on. Thing is, this phone IS NOT "blacklisted" (I've already made an inquiry for that in the global page) and there's about 17 days since original carrier network became locked. So... weirdness remains. On the other hand: How is that you're using "XDA free app"? I'm forced to use "Premium" because "Free" simply didn't work anymore on my devices. I like free version because it has more options and you can sign and stuff...
CNK80Q3MX said:
Hey... How is that you're using "XDA free app"? I'm forced to use "Premium" because "Free" simply didn't work anymore on my devices. I like free version because it has more options and you can sign and stuff...
Click to expand...
Click to collapse
Really? I didn't even know there was Premium version. What's even the point of that? Lol. Whaddaya mean, the Free version didn't work anymore? Mine just keeps on ticking...but I only started using it after I had been signed up on the website and participating on XDA via the desktop browser for ages. Had you signed up on the website, or only on the app?
BW, do you have the apk of the free app? I can send it to you if you don't.
Sent from my Nexus 7 using XDA Free mobile app
CVAngelo said:
Really? I didn't even know there was Premium version. What's even the point of that? Lol. Whaddaya mean, the Free version didn't work anymore? Mine just keeps on ticking...but I only started using it after I had been signed up on the website and participating on XDA via the desktop browser for ages. Had you signed up on the website, or only on the app?
BW, do you have the apk of the free app? I can send it to you if you don't.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Well, signed both... "Premium" was once the paid app, as far as I know. I wasn't using "Free" app for a month or so; then when I required it again, it just didn't open. So I checked the store and they've turned "Free" into an earlier android versions app, thus it won't work for me anymore. Had to download "Premium" (now "Free") to keep going. If you can send the "Free" apk, I'll give it a try... Thanks!

Categories

Resources