-
Notifications
You must be signed in to change notification settings - Fork 354
Open
Labels
bugSomething isn't workingSomething isn't workinginstallerIssues related to the installerIssues related to the installer
Description
Prerequisites
- I have read CONTRIBUTING.md
Rayhunter Version
v0.10.1
Device
Orbic RC400L
Installer OS
Linux
Describe the Issue
What happened
Trying to install Rayhunter 0.10.1 on an Orbic RC400L hotspot from Ubuntu, both the orbic (network) and orbic-usb installers fail in different ways.
Host OS: Ubuntu (Linux 6.17.0-14-generic x86_64)
Rayhunter version: v0.10.1 (linux-x64 release zip)
Device: Orbic Speed RC400L
Software Version (from web UI): ORB400L_V1.2.8_BVZRT
Hardware Version: V1.1
I followed the “Installing from release” docs and got as far as running the installers.
installer orbic (network installer) failure
Command:
sudo ./installer orbic --admin-ip 192.168.1.1 --admin-username admin --admin-password 'MY\_REAL\_ADMIN\_PASSWORD'
Logging in and starting telnet...
Failed to install rayhunter on the Orbic RC400L
Caused by:
0: failed to start telnet
1: error sending request
2: client error (SendRequest)
3: connection closed before message completed
Bus 001 Device 004: ID 05c6:f626 Qualcomm, Inc. MDM9207-MTP _SN:B475A275
sudo ./installer orbic-usb
WARNING: The orbic USB installer is not recommended for most usecases. Consider using ./installer orbic instead, unless you want ADB access for other purposes.
Forcing a switch into the debug mode to enable ADB
ADB enabled, waiting for reboot... it's alive!
Waiting for atfwd\_daemon to startup... done
Installing rootshell...
Failed to install rayhunter on the Orbic RC400L (USB installer)
Caused by:
Received unexpected response: AT+SYSCMD=mv /tmp/rootshell /bin/rootshell
adb kill-server
sudo ./installer orbic-usb
WARNING: The orbic USB installer is not recommended for most usecases. Consider using ./installer orbic instead, unless you want ADB access for other purposes.
Forcing a switch into the debug mode to enable ADB
Device already in command mode. Doing nothing...
ADB enabled, waiting for reboot... it's alive!
Waiting for atfwd\_daemon to startup... done
Installing rootshell...
Failed to install rayhunter on the Orbic RC400L (USB installer)
Caused by:
Received unexpected response: AT+SYSCMD=mv /tmp/rootshell /bin/rootshell
Android Debug Bridge version 1.0.41
Version 34.0.4-debian
Installed as /usr/lib/android-sdk/platform-tools/adb
Running on Linux 6.17.0-14-generic (x86\_64)
What I’m asking
Is firmware version ORB400L_V1.2.8_BVZRT currently supported?
Are the telnet login failure and the AT+SYSCMD=mv /tmp/rootshell /bin/rootshell response expected on newer Orbic firmware?
Is there a known workaround, or should this device/firmware be considered unsupported for now?
Happy to run additional diagnostic commands if that helps, as long as they’re reasonably safe and don’t risk bricking the hotspot.Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workinginstallerIssues related to the installerIssues related to the installer