### Enable adb access on Wingtech Source: https://efforg.github.io/rayhunter/wingtech-ct2mhs01.html Use the installer utility to start adb, then open an adb shell. ```bash ./installer util wingtech-start-adb --admin-password 12345678 adb shell ``` -------------------------------- ### Run the Rayhunter installer Source: https://efforg.github.io/rayhunter/print.html Commands to initiate the installer for Orbic or Kajeet/Smartspot devices, including optional arguments for custom credentials and the USB-based installation method. ```bash # For Orbic: ./installer orbic --admin-password 'mypassword' # For Kajeet/Smartspot: ./installer orbic --admin-password '$m@rt$p0tc0nf!g' # Note: the arguments --admin-username 'myusername' and --admin-ip 'mydeviceip' # may be required if different from the default. # Or install over USB if you want ADB and a root shell (not recommended for most users) ./installer orbic-usb ``` -------------------------------- ### Check Rayhunter installer help Source: https://efforg.github.io/rayhunter/installing-from-release.html Use these commands to view help for the installer and its utility subcommand. Useful for finding installation commands for other supported devices. ```bash ./installer --help ./installer util --help ``` -------------------------------- ### Enable telnet access on Wingtech Source: https://efforg.github.io/rayhunter/wingtech-ct2mhs01.html Use the installer utility to start telnet, then connect via telnet to 192.168.1.1. ```bash ./installer util wingtech-start-telnet --admin-password 12345678 telnet 192.168.1.1 ``` -------------------------------- ### Build and install Rayhunter Source: https://efforg.github.io/rayhunter/installing-from-source.html Builds everything and installs to a device. Replace 'orbic' with your device type. ```bash ./scripts/build-dev.sh ./scripts/install-dev.sh orbic # replace 'orbic' with your device type ``` -------------------------------- ### Run Moxee installer Source: https://efforg.github.io/rayhunter/print.html Executes the installer for the Moxee device. Provide custom admin credentials or IP address if they differ from the defaults. ```bash __ ./installer moxee --admin-password 'mypassword' # Note: the arguments --admin-username 'myusername' and --admin-ip 'mydeviceip' # may be required if different from the default. ``` -------------------------------- ### Rayhunter installer progress messages Source: https://efforg.github.io/rayhunter/wingtech-ct2mhs01.html Expected output during installation, showing the installer stuck at 'Testing rayhunter ...'. ```text Starting telnet ... ok Connecting via telnet to 192.168.1.1 ... ok Sending file /data/rayhunter/config.toml ... ok Sending file /data/rayhunter/rayhunter-daemon ... ok Sending file /etc/init.d/rayhunter_daemon ... ok Rebooting device and waiting 30 seconds for it to start up. Testing rayhunter ... ``` -------------------------------- ### Run UZ801 Installer Source: https://efforg.github.io/rayhunter/uz801.html Execute the installer script while the device is fully booted and connected to the computer. Use the --admin-ip argument if the device IP is not the default 192.168.100.1. ```bash ./installer uz801 ``` -------------------------------- ### Resource busy error output Source: https://efforg.github.io/rayhunter/print.html Example error message when ModemManager prevents the installer from claiming the AT interface. ```text Failed to start adb on the PinePhone's modem Caused by: 0: detach_and_claim_interface({USB_INTERFACE_NUMBER}) failed 1: Resource busy (os error 16) ``` -------------------------------- ### Run Rayhunter installer for Moxee Source: https://efforg.github.io/rayhunter/moxee.html Installs Rayhunter on the Moxee Hotspot. The password is the device admin password; if the username, password, or IP address differ from defaults, provide them via --admin-username and --admin-ip. The installer is similar to the Orbic installer but with better defaults for more recording space. ```bash ./installer moxee --admin-password 'mypassword' # Note: the arguments --admin-username 'myusername' and --admin-ip 'mydeviceip' # may be required if different from the default. ``` -------------------------------- ### Install Rayhunter on Wingtech Source: https://efforg.github.io/rayhunter/wingtech-ct2mhs01.html Run the installer with the admin password. Replace '12345678' with your own password. ```bash ./installer wingtech --admin-password 12345678 # replace with your own password ``` -------------------------------- ### Run Rayhunter installer for TP-Link Source: https://efforg.github.io/rayhunter/tplink-m7350.html Execute the installer script specifically for the TP-Link M7350 device. ```bash ./installer tplink ``` -------------------------------- ### Rayhunter install commands for Orbic and Kajeet Source: https://efforg.github.io/rayhunter/orbic.html Run the installer with the appropriate admin password. The password is the one used for the device admin menu; on Verizon Orbic it is the WiFi password, and on Kajeet/Smartspot it is '$m@rt$p0tc0nf!g'. Provide custom admin username or IP if changed from defaults. USB installation is for advanced users who want ADB and a root shell. ```bash #!/bin/bash # For Orbic: ./installer orbic --admin-password 'mypassword' # For Kajeet/Smartspot: ./installer orbic --admin-password '$m@rt$p0tc0nf!g' # Note: the arguments --admin-username 'myusername' and --admin-ip 'mydeviceip' # may be required if different from the default. # Or install over USB if you want ADB and a root shell (not recommended for most users) ./installer orbic-usb ``` -------------------------------- ### Install Rayhunter on PinePhone Source: https://efforg.github.io/rayhunter/pinephone.html Run the installer on the PinePhone itself. This must be executed on the device, not remotely. ```bash ./installer pinephone ``` -------------------------------- ### Open shell on Moxee after installation Source: https://efforg.github.io/rayhunter/moxee.html After running the installer, there is no root shell and ADB is not enabled. Use this command to access a shell on the device. ```bash ./installer util orbic-shell ``` -------------------------------- ### Run Rayhunter installer for Orbic and TP-Link devices Source: https://efforg.github.io/rayhunter/installing-from-release.html Run the installer with the appropriate device argument. For Orbic, provide the admin password (and optionally username/IP if changed). For TP-Link, no password is needed. On Windows, run in PowerShell, not CMD. ```bash # For Orbic: ./installer orbic --admin-password 'mypassword' # Important notes: # - the arguments --admin-username 'myusername' and --admin-ip 'mydeviceip' # may be required if different from the default. # - on Windows this command should be run in PowerShell and not the Command # Prompt (CMD) where characters like quotes are treated differently. # For TP-Link: ./installer tplink ``` -------------------------------- ### WebDAV configuration in config.toml Source: https://efforg.github.io/rayhunter/configuration.html Example configuration block for enabling WebDAV uploads in the Rayhunter config.toml file. ```toml [webdav] url = "https://dav.example.com/rayhunter/" username = "user" password = "pass" upload_timeout_secs = 300 poll_interval_secs = 3600 min_age_secs = 86400 delete_on_upload = false ``` -------------------------------- ### rayhunter-check usage examples Source: https://efforg.github.io/rayhunter/reanalyzing.html Examples of using rayhunter-check to analyze QMDL and PCAP files, check all files in a directory, and run in debug mode. The --path option is required and can point to a file or directory. ```bash rayhunter-check -p ~/Downloads/myfile.qmdl ``` ```bash rayhunter-check -p ~/Downloads/myfile.pcap ``` ```bash rayhunter-check -p ~/Downloads #Check all files in downloads ``` ```bash rayhunter-check -d -p ~/Downloads/myfile.qmdl #run in debug mode ``` -------------------------------- ### Obtain root shell on TP-Link Source: https://efforg.github.io/rayhunter/tplink-m7350.html Use the installer utility to gain root shell access to the device. ```bash ./installer util tplink-shell ``` -------------------------------- ### Enable adb on PinePhone modem Source: https://efforg.github.io/rayhunter/pinephone.html Enable adb access to the modem. This command starts adb and then opens a shell. ```bash ./installer util pinephone-start-adb adb shell ``` -------------------------------- ### Run orbic-shell utility after install Source: https://efforg.github.io/rayhunter/orbic.html Use this command after the installer to access a shell without enabling ADB or root. This is the recommended way to get a shell on the device. ```bash ./installer util orbic-shell ``` -------------------------------- ### Run rayhunter-daemon in debug mode on PC Source: https://efforg.github.io/rayhunter/installing-from-source.html Sets up a local qmdl store and config.toml with debug_mode=true, then runs the daemon. Skips DIAG, display, key input, battery worker, and WiFi client; recording endpoints won't work, but frontend and read-only APIs do. ```bash mkdir -p ./qmdl && printf 'entries = []\n' > ./qmdl/manifest.toml cat > config.toml <<'EOF' qmdl_store_path = "./qmdl" port = 8080 debug_mode = true EOF cargo run -p rayhunter-daemon --bin rayhunter-daemon -- ./config.toml ``` -------------------------------- ### Typical Rayhunter filesystem layout Source: https://efforg.github.io/rayhunter/porting.html Shows the conventional directory structure for Rayhunter installation. The daemon binary, config file, and qmdl directory are placed under /data/rayhunter/. If a different path is used, update the qmdl_store_path setting in config.toml. ```text _ /data/rayhunter/rayhunter-daemon /data/rayhunter/config.toml /data/rayhunter/qmdl/ ``` -------------------------------- ### Rayhunter installation failure error Source: https://efforg.github.io/rayhunter/wingtech-ct2mhs01.html Error message shown when the installer fails to connect to the device. Ensure your computer is connected to the hotspot's WiFi network. ```text Testing rayhunter ... Failed to install rayhunter on the Wingtech CT2MHS01 Caused by: 0: error sending request for url (http://192.168.1.1:8080/index.html) 1: client error (Connect) 2: tcp connect error: Network is unreachable (os error 101) 3: Network is unreachable (os error 101) ``` -------------------------------- ### Run frontend dev server Source: https://efforg.github.io/rayhunter/installing-from-source.html Runs the SvelteKit frontend separately on your PC while the Rust parts run on the target device. Assumes rayhunter-daemon is listening on localhost:8080. Use API_TARGET to specify a custom backend IP:port. ```bash cd daemon/web # Assumes rayhunter-daemon is listening on localhost:8080 npm run dev # Use a custom target IP:port where the backend runs API_TARGET=http://192.168.1.1:8080 npm run dev ```