TP Link M7350 Installation not working

[Eddie3798]

Prerequisites

• I have read CONTRIBUTING.md

Rayhunter Version

v0.10.1

Device

Tplink M7350

Installer OS

macOS

Describe the Issue

Hello,

I have the TP Link M7350 device with firmware 9.0.3 Build 241219 Rel.1089n. I have conducted the install as per the instructions and can access the RayHunter UI. However, there is no green line on the device. Here is what the logs are saying:

[2026-02-17T07:05:20Z WARN rayhunter_daemon::config] unable to read config file, using default config
R A Y H U N T E R 🐳
[2026-02-17T07:05:20Z INFO rayhunter_daemon] Using configuration for device: Orbic
[2026-02-17T07:05:20Z INFO rayhunter::diag_device] Diag device initialization failed 1 times, retrying in 100ms: Failed to initialize /dev/diag: DIAG_IOCTL_SWITCH_LOGGING ioctl failed with error code -1
[2026-02-17T07:05:20Z INFO rayhunter::diag_device] Diag device initialization failed 2 times, retrying in 200ms: Failed to initialize /dev/diag: DIAG_IOCTL_SWITCH_LOGGING ioctl failed with error code -1
[2026-02-17T07:05:21Z INFO rayhunter::diag_device] Diag device initialization failed 3 times, retrying in 400ms: Failed to initialize /dev/diag: DIAG_IOCTL_SWITCH_LOGGING ioctl failed with error code -1
[2026-02-17T07:05:21Z INFO rayhunter::diag_device] Diag device initialization failed 4 times, retrying in 800ms: Failed to initialize /dev/diag: DIAG_IOCTL_SWITCH_LOGGING ioctl failed with error code -1
[2026-02-17T07:05:22Z INFO rayhunter::diag_device] Diag device initialization failed 5 times, retrying in 1.6s: Failed to initialize /dev/diag: DIAG_IOCTL_SWITCH_LOGGING ioctl failed with error code -1
[2026-02-17T07:05:23Z INFO rayhunter::diag_device] Diag device initialization failed 6 times, retrying in 3.2s: Failed to initialize /dev/diag: DIAG_IOCTL_SWITCH_LOGGING ioctl failed with error code -1
[2026-02-17T07:05:26Z INFO rayhunter::diag_device] Diag device initialization failed 7 times, retrying in 5s: Failed to initialize /dev/diag: DIAG_IOCTL_SWITCH_LOGGING ioctl failed with error code -1
[2026-02-17T07:05:31Z INFO rayhunter::diag_device] Diag device initialization failed 8 times, retrying in 5s: Failed to initialize /dev/diag: DIAG_IOCTL_SWITCH_LOGGING ioctl failed with error code -1
[2026-02-17T07:05:36Z INFO rayhunter::diag_device] Diag device initialization failed 9 times, retrying in 5s: Failed to initialize /dev/diag: DIAG_IOCTL_SWITCH_LOGGING ioctl failed with error code -1
[2026-02-17T07:05:41Z INFO rayhunter::diag_device] Diag device initialization failed 10 times, retrying in 5s: Failed to initialize /dev/diag: DIAG_IOCTL_SWITCH_LOGGING ioctl failed with error code -1
[2026-02-17T07:05:46Z INFO rayhunter::diag_device] Diag device initialization failed 11 times, retrying in 5s: Failed to initialize /dev/diag: DIAG_IOCTL_SWITCH_LOGGING ioctl failed with error code -1
[2026-02-17T07:05:51Z ERROR rayhun[2026-02-17T07:05:59Z WARN rayhunter_daemon::battery] Failed to get battery status: Tokio error: No such file or directory (os error 2)
[2026-02-17T07:06:14Z WARN rayhunter_daemon::battery] Failed to get battery status: Tokio error: No such file or directory (os error 2)

This last error then just repeats itself continuously.

I notice it's trying to configure the device as an Orbic, which I suspect is the problem, but I don't know how to fix this.

Any suggestions greatly appreciated!

Thank you

Ed

[untitaker]

from the output it kind of seems like half the files (battery etc) on your device are missing. that's not normal. was this newly bought?

[reinhard26]

I had the same issue on a new device with v0.10.1

Model: M7350
Firmware Version: 8.0.3 Build 240801 Rel.37n
Hardware Version: M7350(EU) v8.0

My device is running now on v0.10.1, and the problem seems to be that v0.10.1 needs a config.toml file for startup. To reproduce this behavior just rename your config.toml and power cycle your device.

this did the trick for me:
*) install v0.9.0
*) save a configuration (and check if config.toml is on the file system)
*) upgrade to v0.10.1

cheers, Reinhard

[thatsnailguy]

Vibe coder solved like this:

Root cause

file_exists sends this shell command over telnet:

test -f {path} && echo exists || echo missing

It then checks the output with:

output.contains("exists")

The problem is that telnet echoes the full command back before executing it. The output looks like this regardless of whether the file exists:

test -f /media/sdcard/config.toml && echo exists || echo missing\r\n
missing\r\n

Because output.contains("exists") matches the literal string echo exists in the echoed command line, the function always returns true — even when the file doesn't exist and the actual output is missing.

Impact chain

1. file_exists returns true for a non-existent config file
2. install_config prints "Config file already exists, skipping" and does nothing
3. No config.toml is written to the device
4. On first boot, parse_config falls back to Config::default() which uses device: Device::Orbic
5. The daemon uses Orbic-specific behavior on TP-Link hardware

On TP-Link M7350 v9, this means the daemon attempts to use the wrong device interface entirely. The user sees no obvious error — the installer reports success, but rayhunter doesn't function.

Workaround

• Passing --reset-config to the installer: ./installer tplink --reset-config
• Manually placing a correct config.toml on the SD card before running the installer, with device = "tplink" set

• Device: TP-Link M7350 v9.0 (Quectel EC25EUC modem, MDM9607 SoC)
• Rayhunter: v0.10.1 release binary
• Host OS: Windows 11 (installer run from Git Bash)
• Connection: Telnet over WiFi (192.168.0.1:23) and USB RNDIS

[untitaker]

@thatsnailguy yeah i think that's the issue. we should strip the original command from output before returning the output from the TelnetConnection

[untitaker]

#904 should fix this issue.

https://github.com/EFForg/rayhunter/actions/runs/22193257451 will shortly build the installer from this PR, please try it out

[reinhard26]

yes, this fixes the issue for me - a config.toml is copied to the device and rayhunter starts as expected

To simulate a new device, I stopped the rayhunter daemon, executed "rm -rf /media/card/*" and did a power cylce on the device. After that I executed "./installer tplink" and everthing looks fine now.

• Installer: installer-linux-x64
• Host OS: Ubuntu 24.04.3 LTS
• Model: M7350
• Firmware Version: 8.0.3 Build 240801 Rel.37n
• Hardware Version: M7350(EU) v8.0

thank you very much!

[Eddie3798]

Thank you for the input everyone. I don't understand code or how to code so I will need to paste all this into GPT and hopefully it can help me figure out how to implement what you've said.

Thanks again!