scat doesn't work with Samsung Exynos 5G devices

[handymenny]

The Finnish S10 5G on which we were testing, after the update that enabled 5G in Finland has stopped working with scat. I tried to use my raw writer and the output was empty, so I think no diag messages are sent.
The same problem occurs with S20 5G (family) in Finland, UK and Italy. There is a similar problem also with all the S7 and S7 edges that we've tried, I don't know if it's related to this issue, but such a problem never happened with S6, S8, S9, S10 4G, S10e and other (midrange) exynos devices that we've tested.
We tried to disable 5G in the settings but nothing changed.

Moreover 5G devices show two DMs, DM and DM(2CP), in *#0808#, but it's impossible to enable the second one. I guess the second DM is only for qualcomm devices.

There is no error or warning, so I've nothing else to share

[peremen]

Hmm, that's interesting. Maybe the entire diagnostic protocol have been changed, so further engineering might be required in this case.

[handymenny]

No. Even with official samsung tools isn't possible to access the diag of these devices, apparently in some firmwares the diag is disabled or "busy", this also happens with 4G devices. I forgot to close this issue, in the end it is not a problem of SCAT, but of the devices

[whitecloudy]

Could you plz tell me where can I find the 'Official samsung tools' for diag?

[peremen]

Update on Samsung devices: Some years ago Samsung made the magic number check of START DIAG message more strict, that was the reason why there is no DIAG data from Samsung devices as SCAT simply uses AAAA as magic number which is not valid. While the magic number is available on the baseband firmware itself, and possible to be obtained by disassembly, but the problem is I don't want to play a whack-a-mole game on those numbers (I use number A, Samsung update blocks number A and adds new one B, and repeat). This hurts also users too.

I added an option to supply the magic number on START DIAG (--start-magic), but the number itself I am afraid to tell in the public place.

[peremen]

As an alternative, you can use SilentLog hidden application to get the SDM files and can decode using SCAT. Check the information on https://github.com/fgsect/scat/wiki/Baseband-Dumps

[spicyKo0l]

Hi Peremen, Greetings of The Day! Thank you for your support. I am writing to you regarding Samsung S7 Exynos 8890 as I am unable to see the traffic when trying to capture. I had also seen the comments regarding that you have no solution and you are not clear why it is not working on Samsung S7 but you had given some reference issue#27 where you had given alternatives.

1. START DIAG (--start-magic) I am not clear where to and what to give.
2. SDM files, I tried enabling SilentLog but not able to see *.SDM files on the S7.

[peremen]

START DIAG (--start-magic) I am not clear where to and what to give.

Please PM me (see my profile) for the correct value, thanks.

SDM files, I tried enabling SilentLog but not able to see *.SDM files on the S7.

Samsung SilentLog should store directly to the mass storage of the Android. I don't have and can't test on all possible devices.

[peremen]

Update: Several people found what is the magic number independently. I can share the detail, but I don't want to share the detail, as raised in the discussion here. Remember, Qualcomm already implemented RSA encryption on newer 5G DIAG data, and Samsung already changed how OTP authentication works in their SilentLog app. I do not want make everyone's life miserable.