yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy Note 3] Fenny:
su root ls -l /dev/ > /sdcard/out.txt
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Lol good then I read it right, about to post
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
The Output is attached
[T-Mobile Samsung Galaxy Note 3] Fenny:
Okay, well we may have to do some work in the kernel. assuming this com device "felicia" is just a software frontend for something that we have on our devices, then all we have to do is enable it in the kernel build.

However, it looks to me like our hardware impl may differ from that of the sprint version.
[T-Mobile Samsung Galaxy Note 3] ttabbal:
If we know what we need, I can mod a kernel for you. I'll grab the tmo and sprint sources and poke around for that device.
[T-Mobile Samsung Galaxy Note 3] Fenny:
Have at it man, I'm about at the point where my brain is fried today. The idea of setting up two kernel source trees makes me cringe. ;D
[T-Mobile Samsung Galaxy Note 3] ttabbal:
:D

I can see that. They can be a pain for sure.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Really appreciate all your guys are doing for us in the Note 3 thread. Look forward to any progress and donation at least from me for the help
[T-Mobile Samsung Galaxy Note 3] TheNewGuy:
Me too!
[T-Mobile Samsung Galaxy Note 3] Fenny:
Just confirmed that the /dev/felica_cen device exists on the international LTE Device (N9005), and that both the sprint, and international devices use: nfc_nci_jni.so.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Most likely because the T-Mobile version supports the ISIS Wallet which doesn't use the phone's built in secure element but instead uses a secure element present on the ISIS-enabled SIM card.

If that is true, we will have to bring back device access to the built-in secure element somehow (and the AT&T and Verizon versions will have the same problem so we should join forces with their devs).

I wonder if flashing the ROM from the international LTE version would work at all?
[T-Mobile Samsung Galaxy Note 3] Fenny:
Yes, this one will require kernel work, assuming y'all still have the appropriate hardware in your devices.

And it might at that... I don't have the device or I would be tempted to try flashing the system partition from the N9005, I can't recommend that to others without testing though.

*Edit* 5Min until the N9005 kernel source finishes downloading.

Just have to snag the N900T source, and then we can have a party. :D
[T-Mobile Samsung Galaxy Note 3] siraltus:
Let me know if you want me to do some testing. :victory:
[T-Mobile Samsung Galaxy Note 3] Fenny:
Be warned, testing totally untested kernels could lead to fun with odin in your future! I'll let you know though ;P
[T-Mobile Samsung Galaxy Note 3] siraltus:
I always do full backups before I potentially muck up a working configuration. :P
[T-Mobile Samsung Galaxy Note 3] Fenny:
The build operation begins! CONFIG_BCM2079X_NFC_I2C=y, and CONFIG_AUTHENTEC_VPNCLIENT_INTERCEPTOR not set.

FYI it turns out that FeliCa is the protocol that BCM2079X uses... Who knew? :D

Let's just hope you have the hardware to go with it.

If the build fails, I'll try it again with

CONFIG_NFC_PN547, and CONFIG_NFC_PN547_8941_CLOCK_REQUEST unset.

It seems to have built okay you can try it here:

*snip* Removed (Odin flashable)

You will need to use the NfcNci.apk NfcTest.apk and associated lib/so files from the Sprint or International rom with this kernel.

Just in case here is the stock kernel as well:

http://www.cheatersedge.org/android/n900tStockKernel.tar (Odin flashable)
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
I hope Samsung did not do what they did with HTC one, The secure element was not built in except for in the Sprint Variation...That would be a total bummer and I would be pissed. The Note 2 made me proud and the S4, Hopefully the Note 3 isn't where they deviated
[T-Mobile Samsung Galaxy Note 3] Infos3c:
I did some googling about devices with/without a secure element and found out about the uproar when Nexus 7 was released without GW support.

The Nexus 7 has no hardware secure element, but Google did a work-around somehow and it now supports GW - I didn't dig much further. I just pulled the files from the 4.3 release of tilapia and it has an NfcProvision.apk in addition to Nfc.apk. Obviously, there may be a software kernel SE as well.

This could help down the road if we find out that Samsung forked the HW for Tmo without an SE. I'm REALLY hoping they didn't, but after what we saw with the Tmo Note II wireless charging hw, you never know.

I also noted that the nfcee_access.xml from my download of the N9005 stock fw did NOT have the GW keys - only some Samsung stuff. Putting that in my nfcee stopped the SE release keys errors, but didn't help with FCs.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
This could indeed be helpful, and I have a feeling that its very likely the hardware SE is probably not there, I was worried about that after I saw the One and when I saw the S4 it wasnt like that, I had hope, but then I started getting worried...We shall see
[T-Mobile Samsung Galaxy Note 3] Infos3c:
I'm just hoping that only the stock kernel has been modded to ignore the hw secure element (or something similar) and not actual removal or permanent disabling of the hw SE.
[T-Mobile Samsung Galaxy Note 3] Fenny:
Hopefully my kernel does the trick.

Anyone test it?

I just realized an additional thing that needs to be done. I will need to patch the NfcNci.apk from the other source ROM. Imma sleep now. I'll look at it tomorrow.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Should we hold off on the kernel right now? Also do we need to pull the Nfc apk and libs from the sprint Rom?
[T-Mobile Samsung Galaxy Note 3] siraltus:
Let's wait. The kernel will be no good without the patched NFC libraries. I really hope the SE is there. I wonder if we could somehow use the SE on the SIM card if it isn't.
[T-Mobile Samsung Galaxy Note 3] Fenny:
Replace the files from this tar in /system/ (no, it's not flashable).

http://www.cheatersedge.org/android/files.tar

I would just rename the original files to .bak so that you can look at the permissions on them to be sure.

*hint* NfcNci == Nfc on the original system.

Make sure you do an ls -l of the originals to see what ownership/perms were (also make a backup), and chmod/chown them correctly.

Then you can flash the kernel posted above with Odin.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Are you sure the libnfc-nci.so file is supposed to have a hyphen instead of an underscore?

Are we supposed to rename them - like NfcNci.apk --> Nfc.apk? You said "replace" so I'm taking your instructions literally (no renaming).

(FYI, I'm a technical writer at Oracle and I write documentation for one of our software suites - we are VERY, VERY careful in how we word our instructions - one wrong character or ambiguity and a customer's production systems blow up, not good when they're bleeding tens of thousands of dollars a minute because of that).
[T-Mobile Samsung Galaxy Note 3] Fenny:
Certain about the hyphen, yes. Some of the files in lib will be new, and some of the files in etc will be new. Thus the *hint*. The classes contained within those APKs are identically named from a java perspective, so you must rename/remove Nfc.apk and NfcTest.apk.

If in doubt, make a nandroid.

And check logcat and dmesg for complaints about missing files.

Fingers crossed that the hardware is there.

TLDR; Correct, no renaming.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Kernel boot failed. Bombs into download mode with error "Could not do normal boot." Had to restore my nandroid.
[T-Mobile Samsung Galaxy Note 3] Fenny:
Okay, well sounds like the hardware isn't there then. Sad. Guess it's time to look at the N7's soft impl?
[T-Mobile Samsung Galaxy Note 3] siraltus:
Who knows? It bombed immediately - literally, split second after the screen went black after I flashed the kernel, could be a bunch of other things that are preventing it from booting, no? Maybe the Qualcomm SecureBoot is preventing it from booting?

Also, where did you see the 2013 N7 has a software secure element implementation? That would defeat the whole purpose of a secure element. I did see in the Wallet changelog that "Now supports Nexus 7" but all that probably means is that now the NFC-less version installs on it, whereas before version 2.0 Wallet wouldn't install on it at all due to lack of an SE.
[T-Mobile Samsung Galaxy Note 3] Fenny:
Hmm, okay, could be something in the initfs... I suppose I could look at it, and Yes, I suppose you could be right about SecureBoot as well.

I saw someone mention it in this thread I though, that the old one had a new Nfc related app pop up in /system/app in an update just before it started "supporting it".

Here:
[T-Mobile Samsung Galaxy Note 3] siraltus:
Yeah, we shouldn't immediately discard all of our efforts just because our first and totally blind kernel build did not boot.

A guy over in the Sprint Note 3 forum successfully built a booting kernel with SELinux Permissive: http://xdaforums.com/showthread.php?t=2475726

You could talk to him to see how he got it to boot.

And nice, I had no idea... I wonder if it does actually support Tap-and-Pay now...
[T-Mobile Samsung Galaxy Note 3] Fenny:
I am going to build a completely stock kernel, and we can see if perhaps something is wrong with my build env.

just did a make clean; make with the tmo defconfig, We'll see if a mostly stock kernel boots.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
There was a Nfc provision apk and screen shots of tap and pay purchases from the Nexus 7. I don't know what they did to make it work I tried to find a read on it but I couldn't. I was able to see tap and play support
[T-Mobile Samsung Galaxy Note 3] siraltus:
Question - does flashing the kernel via Odin wipe the dalvik cache? Maybe I should boot into recovery and wipe it after flashing the kernel but before trying to boot it?
[T-Mobile Samsung Galaxy Note 3] Fenny:
No, it does not, however, if it happened that early in the boot dalvik had not even been loaded.
[T-Mobile Samsung Galaxy Note 3] siraltus:
OK, just curious...

Yeah, it literally just went straight to download mode with "Could not do normal boot."

---------- Post added at 02:33 PM ---------- Previous post was at 02:28 PM ----------

On the 2013 Nexus 7, right? The 2012 one has a secure element.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Yes, let me re look it up to confirm
[T-Mobile Samsung Galaxy Note 3] Fenny:
Tell me if this one boots:

http://www.cheatersedge.org/android/n900/Fenny-StockBuiltKernel.tar
[T-Mobile Samsung Galaxy Note 3] Infos3c:
Yes, I specifically downloaded the pre-2012 "tilapia" 4.3 version.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Yes, sir. This one booted perfectly. Keep on hackin', we'll figure this Wallet BS out. :D
[T-Mobile Samsung Galaxy Note 3] Fenny:
Got to love the kernel name. :)

So, I nuked my Compiler cache before this build:

http://www.cheatersedge.org/android/n900/Fenny-nfcModKernel-2.tar

You may want to try this one just to see if it boots before you move the NFC files from the previous post into place.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Then there's hope that we can do a software secure element if we don't have a hardware one! Or maybe even find a way to use the SE on the ISIS SIM card... ahh, here's to dreaming!
[T-Mobile Samsung Galaxy Note 3] Fenny:
FYI, the zImage did come out at a different size on this build than the last one, so that is potentially a good sign.

If it's implemented in java, and hardware independent, I can make it my biatch!
[T-Mobile Samsung Galaxy Note 3] siraltus:
Yes, sir, this one booted perfectly fine, too. Moving your NFC patch files into place now.
[T-Mobile Samsung Galaxy Note 3] Fenny:
Make sure to check for the felica device blocks in /dev/. If they aren't there, it won't work.

*edit*

Sounds like I had some bad compiler cache! I bet it came from the arm-eabi v4.6 toolchain that comes in AOKP.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Well, sir, good news and bad news. After moving all your files into place, the phone booted with no errors and NFC works just fine.

The bad news is Wallet still crashes and I see no /dev/felica_cen device when I list the contents of /dev. So are we screwed or are we screwed? Damn you, T-Mobile!
[T-Mobile Samsung Galaxy Note 3] Fenny:
That may be good news. Let me try to force enable felica in the defconfig now.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Alrighty, I won't restore my nandroid just yet, then. :)
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
You guys are way above my head how is it any of us can help. I am reading but i don't know how you guys are coming up with all this info esp about Felicia
[T-Mobile Samsung Galaxy Note 3] siraltus:
Happy to help, and it's fun to really learn about the gory innards of our brand new toy! Why doncha hit the Thanks button for Fenny and me, will ya? Much appreciated!
[T-Mobile Samsung Galaxy Note 3] Fenny:
I did a quick dirty build of it, and I am running a clean build now.

If you want to try it right now: (Be warned, dirty builds have a nasty habit of not wanting to boot, but it's easy enough to Odin back the working one.)

http://www.cheatersedge.org/android/n900/Fenny-nfcModKernel-2.1(dirty).tar

Otherwise the clean build will take a minute.
[T-Mobile Samsung Galaxy Note 3] siraltus:
How long for the clean? I'd rather just do that, I'm working on a song now (I make electronic music, BTW.) So I'd rather just not waste time on dirty...
[T-Mobile Samsung Galaxy Note 3] Fenny:
It varies. Maybe ~40 min?

Interesting reading in the section about FeliCa

http://en.wikipedia.org/wiki/Near_field_communication
[T-Mobile Samsung Galaxy Note 3] siraltus:
Cool, I'll be up till midnight (Eastern Time). Where are you located?
[T-Mobile Samsung Galaxy Note 3] Fenny:
Rockin' the Rockies over here in SL, UT. :D
[T-Mobile Samsung Galaxy Note 3] siraltus:
Werd, Brooklyn, NY here. :D
[T-Mobile Samsung Galaxy Note 3] Fenny:
Okay, let's see how we did. (It was done around the right time, but sometimes, at work I actually have to work... sad.)

http://www.cheatersedge.org/android/n900/Fenny-nfcModKernel-2.1(clean).tar
[T-Mobile Samsung Galaxy Note 3] siraltus:
Aaaaand this one bombed instantly with "Can't do normal boot" just like our first attempt earlier today. Sigh. I had high hopes for this one!
[T-Mobile Samsung Galaxy Note 3] Fenny:
Yeah, it definitely doesn't like it when I turn on felica. If I had one of these phones, I would hook it up to UART, and have a go at getting an error log. But that's not something a sane person who likes to keep their warranties does with devices like these. I'll look through the code and see if I can find any dependencies I might have missed.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Something like a MAX232 TTL to RS-232 transceiver? I have a board like that... if you have the pinout. :P
[T-Mobile Samsung Galaxy Note 3] Fenny:
Sadly, I do not have the pinout, but there is a pretty good chance that samsung has a (very) tiny molex style connector on there for it, I know they did on the s, s2, and s3... or was that for JTAG? Now I'm not so sure.

And here I was feeling special with my little USB-serial dongle with jumper wires on it. :P
[T-Mobile Samsung Galaxy Note 3] siraltus:
Hmm... wish there was a service manual somewhere... I have only seen one picture of Note 3 innards so far online. And as for warranty, that's long gone as I tripped the KNOX WARRANTY VOID bootloader flag (irreversible until someone figures out how to remove the Qualcomm SecureBoot write protection) the second I rooted the thing.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Yo, check this out: http://xdaforums.com/showthread.php?t=2480353

Also, if we do succeed with an SE-enabled kernel, we should make it SELinux Permissive as well. :D
[T-Mobile Samsung Galaxy Note 3] Fenny:
I can definitely do that. I found a missing dependency. I'm honsetly surprised it compiled without it...

Added an ifdef for our board to the code. I'll have to make two builds and see which of the two works.

Building a new one now.

*edit*

Here they are: Try A, and then B if A doesn't work.

http://www.cheatersedge.org/android/n900/Fenny-nfcModKernel-2.2A.tar

http://www.cheatersedge.org/android/n900/Fenny-nfcModKernel-2.2B.tar
[T-Mobile Samsung Galaxy Note 3] siraltus:
Both immediately bombed to download mode with good old "Cannot do normal boot." :(
[T-Mobile Samsung Galaxy Note 3] Fenny:
UGH, lame, any chance you can get a logcat of the wallet crash with the v2 one that booted and had working NFC? I am curious about something.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Sure. How do I logcat the crash?
[T-Mobile Samsung Galaxy Note 3] Fenny:
The easy way would be to plug in your device, and run:

adb logcat > alogfile.txt

Then while plugged in, open google wallet, and recreate the crash, at which point you should either close the logcat process, or unplug the device. so that we don't end up with a whole bunch of random log data at the end of the log.

Then just post the logfile.

You can also use on-device apps like catlog to record a logcat.
[T-Mobile Samsung Galaxy Note 3] siraltus:
OK strange... the NFC-patched kernel that booted last night now doesn't boot anymore... what the hell!?
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
The 2013 Nexus 7 did not have a secure element, I feel like the note 3 does not either and it's through the sim that Isis works. The issue happened on the HTC One. There have been many complaints to the FCC in regards to the carriers illegally blocking wallet so their answer is the NFC Sim cards and Google Wallet admitting defeat instead of using their brain. Google should block the manufacturer and carriers from using Android until it is left alone and only used the way it was intended. No Apple blocking. MONEY hungry d bags always ruin good thing. Wake up google, make the Nexus utilize the secure element in the phone and Nfc and there isn't nothing the carrier can do.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Well it's a fact ISIS Wallet uses the secure element on the ISIS SIM card.

The SM-900T not having a built-in SE would be a bummer as it is the best Note 3 variant in the US, but not the end of the world, since ISIS actually works fine, it's just clunkier. I used it at Walgreens in NYC yesterday and it worked flawlessly. It's just ugly and not Google Wallet. :P
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Isis won't even install for me, well it installs but it failed three times to set up my phones secure element. I miss Google Wallet.
[T-Mobile Samsung Galaxy Note 3] HughesNet:
You have to do it with wifi off. It is setting up your sim so it needs to do it over cellular not wifi and when wifi is on cellular is disabled. Isis is OK but extremely limited in number of retailers. Like only 4 or so different c companies I can find in Phoenix. Mostly convenience stores and drug stores.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Yeah I tried that. I just never get the text nor do I know how long after I attempt to set it up is it supposed to take
[T-Mobile Samsung Galaxy Note 3] Fenny:
You may still need to replace the Nfc.apk from my first post in this thread to overcome the security checks if you are deodexed.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
I am good to go it finally worked.....I Miss Wallet still
[T-Mobile Samsung Galaxy Note 3] TheNewGuy:
Is there a way around the root check? Mine says it can't install because it's rooted.
[T-Mobile Samsung Galaxy Note 3] siraltus:
No need. ISIS works out of the box without any ROM modifications. You just have to install the ISIS Root Bypass mod for XPosed if you're rooted. I've been using it and it works fine.

---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------

Install the ISIS Root Bypass mod for the Xposed Framework.
[T-Mobile Samsung Galaxy Note 3] Fenny:
Ahh interesting.

Well, today I realised that the kernel booting, and then not booting sounds like maybe a SELinux thing, so I diffed my initfs... aaand It turns out I can't spell enforce, care to try another kernel? :D

http://www.cheatersedge.org/android/n900/Fenny-nfcModKernel-2.3A.tar
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
This for NFC Mod, if it boots what do you want us to do
[T-Mobile Samsung Galaxy Note 3] Fenny:
Do an "ls /dev/" and tell me if there is a felica listed. :D

If it's there replace these files in system and set permissions properly:

http://www.cheatersedge.org/android/files.tar

Then grab a logcat, and we can see what we can see.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Still doesn't boot. Bombs to download mode instantly. :(
[T-Mobile Samsung Galaxy Note 3] Fenny:
Well, I think we can officially give up on felica. :/
[T-Mobile Samsung Galaxy Note 3] siraltus:
Well, it was worth trying. :( But did you read my other post? The NFC-modded kernel that booted before suddenly doesn't boot anymore! (the one you had me flash after the completely unmodded one you built). I tried flashing it again recently and it bombed to download mode... but it booted once before. Weird!
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Just woke up sorry... Just saw you guys were at it again sorry it didn't work but thanks for all you did
[T-Mobile Samsung Galaxy Note 3] siraltus:
Maybe instead we can somehow mod Google Wallet to use the ISIS SIM card as its secure element?
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Probably a whole lot easier than a nfc modded kernel, that should be way easier
[T-Mobile Samsung Galaxy Note 3] blacklabel2020:
That would be much better to do. I just switched to a isis sim. Hope we can make this happen.
[T-Mobile Samsung Galaxy Note 3] TheNewGuy:
This is a good read.

http://nelenkov.blogspot.com/2012/08/accessing-embedded-secure-element-in.html?m=1

Lots of stuff. . It got me thinking, but it will take someone smarter then me.
[T-Mobile Samsung Galaxy Note 3] Fenny:
Yes, this is the same issue as with Wifi calling, both are stored on the UICC. I have gotten access to the ISIM application on my t-mo UICC with the S4, and I am sure it is possible. One thing that we do have as an advantage is that because the stock rom supports Wifi Calling, we KNOW that the proprietary RIL binaries were built with SEEK. That means we have a lot better access to our UICC, and not just to the SIM application on it.

The major disadvantage is that I don't have one of these phones, and at the rate things are going, it could be months before we get full access to it.

Alternatively, it may be easier to kang the code from the isis application and inject it into the g-wallet application, and the addition to the N7 for tap to pay has possibilities for a software solution.
[T-Mobile Samsung Galaxy Note 3] TheNewGuy:
Look at this post for the patches it talks about.

http://xdaforums.com/showthread.php?t=1281946

It says right in it that you can make it use the sim SE.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Good find man
[T-Mobile Samsung Galaxy Note 3] Fenny:
Sadly, I don't think much of that code will help us in a non-aosp environment. We are stuck using vendor binaries for which we don't have the source.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Guess we wait for CyanogenMod to start building for this phone, then. Also, I couldn't find anything on the purported "software" SE for the N7 and bdorr1105 never provided any source (or did I miss it?). I have doubts it really exists.

Edit: I found this article today - http://www.androidpolice.com/2013/1...hows-the-new-clock-about-easter-egg-and-more/

It's KitKat 4.4 running on the 2013 Nexus 7, which has no hardware secure element, and in the settings screen there is a "Tap & Pay" option - this, of course, proves nothing, as it could just be left in for now and removed when it ships, or tapping it would only show you a screen full of greyed out options or a sad "This device does not support Tap & Pay" message, but there is a very small amount of hope. I'm not getting excited until I see it in action, though.
[T-Mobile Samsung Galaxy Note 3] Infos3c:
http://www.tomsguide.com/us/Google-Wallet-Nexus-7-Jelly-Bean-NFC-MasterCard,news-15922.html

http://xdaforums.com/showthread.php?t=1796931