-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
Both, by design.
- Repository and product name:
XeCLI - Installed command:
rgh
No, not for the published win-x64 release zip.
The release package is self-contained. Source builds still require the .NET 10 SDK/runtime.
Run:
.\XeCLI-1.0.8-setup-win-x64.exeThat is the normal Windows install path.
The installer can choose the install scope, ask for the install directory, register rgh for new terminals, set the initial UI language, and then offer to connect to a detected console.
After installation, open a new terminal and use:
rgh --help
rgh languageIt can.
During install, XeCLI asks whether you want rgh available in new terminals. You can accept or skip that step.
Yes.
Use the dedicated homebrew branch:
rgh homebrew install aurora --usb E:
rgh homebrew install all --usb E: --auto-confirm
rgh homebrew install aurora --device Hdd1 --ini-mode mergeSupported package IDs are:
auroradashlaunchxexmenufsdxm360timefixersimple360xelllaunchall
With --usb, XeCLI stages the packages onto a USB drive or folder. Without --usb, XeCLI connects to the console, detects only Hdd1, Usb0, Usb1, and Usb2, installs to the selected drive, and asks whether it should generate a new launch.ini, merge plugin entries into the existing one, or leave launch.ini alone. XeCLI asks before staging or installing unless you use --auto-confirm or run the command non-interactively.
By default, temporary extraction now happens on the target drive instead of %LOCALAPPDATA%, which avoids the common "not enough space on disk" failure when staging larger packages.
Read Homebrew and USB for the full package workflow.
No. The bundled Title ID database ships with the repository and with the published release.
Yes. That is a supported use case. Read the bundled CSV/TXT files directly or use rgh title --json.
Use these pages in order:
Beginner GuideCommands ReferenceXNotifyCLI Help OutputTroubleshooting
That prompt only appears when XeCLI actually detects a console after install.
If it does not appear:
- the console may not be reachable yet
- discovery may not have found a target fast enough
- or you may have used a scripted install path
Manual fallback:
rgh start
rgh statusYes. The source tree and release package ship the common console-side .xex files XeCLI expects, including xbdm.xex, XDRPC.xex, and JRPC2.xex.
Those files are provided so users can deploy the exact plugin versions XeCLI was built and tested against.
Because the command is designed to resolve the active title by default when no Title ID is supplied.
Use a numeric logo ID or a saved preset.
Examples:
rgh notify "XeCLI connected" 14
rgh notify --message "Patch applied" --logo 16
rgh notify-icons add --name success --logo 14
rgh notify --message "Transfer complete" --icon successFor the full icon list and usage notes, read XNotify.
Use:
rgh signin stateThat command isolates the active session state, gamertag, XUID, and slot without forcing you to scan the full status output.
Yes.
Examples:
rgh led set --preset quadrant1
rgh led set --preset all-green
rgh led stateled state shows the last XeCLI-applied ring-light state.
XeCLI exposes manual fan command dispatch and a cached fan show view.
Examples:
rgh fan set --speed 55 --channel both
rgh fan showRead Hardware and System Controls for the operational details.
Because those fields were intentionally skipped. The current release distinguishes skipped from unknown so the operator can tell the difference between a deliberate fast path and a failed probe.
Because many retail, JTAG, and plugin-backed XBDM targets do not expose usable thread-name pointers.
XeCLI now resolves the thread start routine address, maps it back to a loaded image when possible, and shows Image, Start Addr., and End Addr. in the thread table. End Addr. is the containing image end boundary, not a reconstructed function end.
Yes. Some live module loads do not complete as a clean hot-load on every console or plugin stack. Use --reboot-expected and verify with rgh modules pending.
Not universally. That is why modules unload requires --force.
Yes. Prefer commands with --json when building scripts or companion tools.
Start with:
rgh status --jsonrgh title --jsonrgh modules list --jsonrgh profiles --jsonrgh scan --jsonrgh ghidra verify --json
Yes. Add entries to:
%APPDATA%\XeCLI\titleids.local.csv
No. Reverse-engineering tooling is optional.
- Ghidra is only required for the
ghidraandxex decompileworkflows. - IDA Pro is only required for the
idaandxex ida-decompileworkflows. - XeCLI does not bundle either tool.
- Ghidra is documented in the CLI as
(Free). - IDA support is pinned to
IDA Pro 9.1.250226withidaxex 0.42b.
No single tool replaces every scene workflow perfectly. The goal of XeCLI is to cover the high-value terminal-first workflows cleanly enough that you do not need to bounce between small one-off utilities for status, dumps, memory work, saves, content, notifications, screenshots, and scripted automation.
Use the Ko-fi link in the README or the support button in the published wiki:
XeCLI documentation for the rgh command. For release downloads, use the latest release.