Cant access Orbic via ADB after enabling tethering
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 490
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 23
Description
### Bug Report Details
- **Rayhunter Version**: V0.5.1
- **Date**: 6-Aug-2025
- **Device, Model**: Orbic RC400L, ORB400L_v1.2.1_BVZRT
- **What happened**: after running `./installer util shell "echo 9 > /usrdata/mode.cfg"` and reboot the device no longer seems to communicate via adb this includes commands & installing or updating firmware
**Firmware install test w/output**:
`user@user:~/Documents/rayhunter/rayhunter-v0.5.0-linux-x64$ sudo ./installer orbic` _(same for test on v0.5.1)_
```
Forcing a switch into the debug mode to enable ADB
Device already in command mode. Doing nothing...
ADB enabled, waiting for reboot...
Failed to install rayhunter on the Orbic RC400L
Caused by:
0: Timeout waiting for Orbic to reconnect
1: deadline has elapsed
user@user:~/Documents/rayhunter/rayhunter-v0.5.0-linux-x64$
```
**Shell Access Test w/output**
`user@user:~/Documents/rayhunter/rayhunter-v0.5.0-linux-x64$ sudo ./installer util shell` _(same for test on v0.5.1)_
```
opening shell
Failed to open shell on Orbic RC400L
Caused by:
0: Timeout waiting for Orbic to reconnect
1: deadline has elapsed
user@user:~/Documents/rayhunter/rayhunter-v0.5.0-linux-x64$
---
Same result when trying the command to disable tethering.
All commands were working as i just upgraded from v0.5.0 to v0.5.1 with no issue and was able to gain shell access
in v0.5.1 until enabling tethering and more specifically after the reboot.
- **Expected behavior**: Probably obvious but i expected it to be able to access the shell to do normal things like
install/upgrade or change mode.
Contributor guide
Assessment
This issue has not been assessed yet.