Won't Read/Write After Android Oreo Update [Galaxy Note 8]

[amgalitzky]

I use a Samsung Galaxy Note 8 i had Android 7 & everything worked great.

Now i updated to Android 8 (Oreo) & ever since I can't download the app from the play store. I'm getting a message "Your device isn't compatible with this version".

After downloading it from github it wouldn't read/write tags it just keep on loading as if it's reading/writing but never finishes.

[ikarus23]

Well, this is really strange. Both of it. I know of no reason why an app should become incompatible on the app store after updating and I don't know why its never finishing on reading/writing.

As far as I know, the Note 8 never was compatible. At least this is what I've been told. That is why I added it to the list of incompatible devices. I also blocked it on Google Play, so this is the reason you can not download it from there (and most likely not due to an Android update).

But It seams like people having a hard time. NFC Today writes that the Note 8 "maybe" supports Mifare Classic (source). Have you tried other apps? Like NFC Taginfo or NFC Taginfo by NXP? It's really hard to debug this without a Galaxy Note 8 in my possession ;)

Also, this seems to be a duplicate to #175. Furthermore, users report that the Galaxy S8 works after updating to Oreo. Maybe Samsung changed some NFC stuff for the Note 8 as well when updating to Oreo, but for the worse.

[amgalitzky]

This is indeed strange. I was using it with Android Nougat without any issues, everything worked. And I was able to download it on Google Play too. ever since the update i have this issues.

I just tried testing NFC Taginfo & NFC Taginfo by NXP and i have the same issue there, the phone is detecting the NFC tag and can get the basic tag info but it works read/write/format.

[ikarus23]

Well, this is bad news for Note 8 owners. If you have the same buggy behavior with other apps, it is most likely that the NFC code in the Samsung Galaxy Note 8 Oreo update is broken. It wouldn't be the first time... Even my Google Nexus 5x has NFC issues 😞

As I don't own an Note 8 I'm not able to check if it's possible to develop a workaround. Sorry.

[amgalitzky]

Thanks let's hope they will fix it in a future update.

[norbital]

Same with me. Copied and wrote cards no problem... All nfc apps except pay apps are broken after Oreo... Thanks Samsung

[norbital]

Oh... Just wanted to thank you for your work. Great app while it worked for me

[amgalitzky]

I contacted Samsung and after some testing on their behalf they acknowledged in the issue and they told me they apply a fix in a future update.

[ikarus23]

@norbital You are welcome ;)
@amgalitzky Thanks for reaching out to Samsung! I will remove the Note 8 from the blacklist as soon as the patch is rolled out.

[gmkbenjamin]

I have Samsung Galaxy Note 8 SM-N950F variant in Australia, all apps started working with Mifare Classic after upgrading to Oreo 8.0.0 build number: R16NW.N950FXXU3CRC7 (without any additional patches), this includes NFC taginfo and MCT. Please remove it from the blacklist.

[ikarus23]

What now? @amgalitzky says the Note 8 does not work after updating to Oreo any @gmkbenjamin is saying it started working on the Note 8 after updating to Oreo?

Also, there are people saying it started to work on S8 and some other say it does not. See #172.

Are the that many version of the Note 8 / S8 with different Hardware/Software?

[amgalitzky]

I have a different build number my built number is R16NW.N950U1UEU3CRC1 i guess in Australia they have different software's

[gmkbenjamin]

Yep, there are 2 chipset versions and multiple carrier specific software version. I was so disappointed that I couldn't use this tool when I switched from pixel. I'm so happy now that I can use it again ;)

[ikarus23]

Okay, so there are working versions of the Note 8 and not working versions of the Note 8. This is exactly the same as with the S8. However, it is not that easy to unlock the working versions of the Note 8 in the Play Store. Have a look at #172 (comment) The available codenames of the Note 8 in Google Play are:

SCV37
greatqlteue
greatqlte
greatlte
greatlteks
greatqltecs
SC-01K
greatqltecmcc
greatqltechn

If you are able to find out the codename of the device that works I can unlock it...

[gmkbenjamin]

Mine is greatlte. And it works on Android 8. I'm not sure if carrier specific ROM comes into play though......

[norbital]

It seems to. Mine is greatqltecs (Canadian) and it generally doesn't work...
If I mess with it turning off and on NFC then immediately reading or writing a tag I can get it to work, but only a 1 in 10 success rate.

[ikarus23]

Thanks for the feedback @gmkbenjamin and @norbital!

I will wait a little longer before unlocking greatlte. Maybe someone with another ROM but the same model has more feedback.

@norbital Well, this sounds like a solid bug. And an annoying one too! Lets hope it gets fixed due to @amgalitzky's feedback to Samsung.

[amgalitzky]

I just got a software update (Version: N950U1UEU4CRD7/N950U1OYM4CRD7/N950U1UEU4CRD7) which did still not fix the issue.

[eslavnov]

@ikarus23 Thank you for a great app!

I have a Dutch Note 8 (greatlte) with original Oreo ROM (Build number: R16NW.N950FXXU3CRE5) and MCT version 2.2.3 works fine for me. Would be awesome if you could unblock it on Play store!

[ikarus23]

I added the Samsung Galaxy S7, S8 and Note8 to the list of compatible devices and made MCT available to them in the Play Store.

I hope the poor users of some bugged S8 and Note8 devices will receive their update soon so that they can use MCT as most other S8/Note8 users.

I will leave this issue open for discussion and feedback on the rollout of the update with the fixes.

[taylorwin]

I added the Samsung Galaxy S7, S8 and Note8 to the list of compatible devices and made MCT available to them in the Play Store.

I hope the poor users of some bugged S8 and Note8 devices will receive their update soon so that they can use MCT as most other S8/Note8 users.

I will leave this issue open for discussion and feedback on the rollout of the update with the fixes.

Hi ... I use note8（R16NW.N9500ZCS4CRL1）.
Upgraded to the latest through the Google Store, but still failed to read all block one time.
Read one block one times it is OK（Unstable sometimes fails）^^

Read normally with https://why.yuyeye.cc/mtools/en/index.html
Hope it helps you

[taylorwin]

Upgraded to the latest through the Google Store, but still failed to read all block one time.

help me …………

[ikarus23]

Have you tried the "retry authentication" option?

[taylorwin]

Have you tried the "retry authentication" option?

thank you for your reply

"retry authentication" Set it the value is 1 .but the same failed.
The status is Hang up（Create a key map）.
After failing multiple times, I must restart NFC to recognize the Mifrare card.

[ikarus23]

I'm sorry, but this really looks like an issue of your device or the ROM, but not MCT. I don't think there is something I can do.

[taylorwin]

I did some testing。

1. Just use keyA , MCT crashed.
2. Just use kenB , MCT crashed.
3. Use together keyA,kenB it work ok.

But i use Another mobile phone , just user keyA it is work ok .
All test use the same card （730031081031 FF078069 FFFFFFFFFFFF）.

[ikarus23]

Very strange. It might be connected to the other issues with only one key in the key file: #66.

[ikarus23]

I will close this now. It seams MCT works now on most of the Note 8/S7/S8 devices. Even if not, there is nothing I can do. It looks like there still some issue with some ROMs for specific models or countries.

@taylorwin Your issue could be different. If nothing has changed since April 2019 and even the latest testing version does not work, you could open another issue.