EFForg / EFForg/rayhunter

`MessageParsingError` related to an unknown `ResponsePayload` during startup.

Open
#405 2 comments 0 reactions 0 assignees View on GitHub
bug parsing
Dominant language
Rust
Stars
5.8k
Forks
490
Avg merge
3d 10h
Merged PRs (30d)
23

Description

## Device Info

- **Device:** TP-Link M7350
- **Hardware Revision:** v3 (installer auto-switched to v5 exploit, which worked)
- **Firmware Version:** `8.0.3 Build 240801 Rel.37n`
- **Rayhunter Version:** v0.3.4 (installer-windows-x86_64)
- **SD Card Format:** FAT32 with MBR

## Installation Output Snippet

Succeeded in rooting the device! Now you can use 'telnet 192.168.0.1' to get a root shell...
Mounting sdcard on /media/card
Sending file /media/card/config.toml
Sending file /media/card/rayhunter-daemon
Sending file /etc/init.d/rayhunter_daemon
Done. Rebooting device. After it's started up again, check out the web interface at http://192.168.0.1:8080/

## Error Message from Telnet (manual launch)

/media/card/rayhunter-daemon /media/card/config.toml

R A Y H U N T E R
[ERROR rayhunter::diag_device] error parsing message: MessageParsingError(Parse("Could not match enum variant id = 2650802784 on enum ResponsePayload"), [96, 10, 0, 158, 1, 0, 0, 0, 0, 0, 0, 0, 0])

## Behavior

- Web interface loads successfully on `http://192.168.0.1:8080`
- Green line appears at the top
- Diagnostics may not fully work
- No other issues observed so far

## Request

Could you confirm whether firmware `8.0.3 Build 240801 Rel.37n` is supported?
If not, I'd be happy to help test updated parsing logic for the new message variant ID (`2650802784`).

Thanks for building this amazing tool!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.