# Beginner Guide This guide covers the safe, practical path from a fresh install to a working live-console session. ## 1. Know the Minimum Requirements On the PC side: - Windows - no extra runtime if you are using the published `win-x64` release package - .NET 10 only if you are building or running XeCLI from source - Network access to the console On the console side: - XBDM enabled - JRPC2 if you want RPC, temps, CPU key, notifications, or Title ID reads - FTP service if you want FTP-backed save, content, or file workflows Direct plugin downloads from the XeCLI repo: - [Download `xbdm.xex`](https://github.com/SaveEditors/xecli/raw/main/xbdm.xex) - [Download `XDRPC.xex`](https://github.com/SaveEditors/xecli/raw/main/XDRPC.xex) - [Download `JRPC2.xex`](https://github.com/SaveEditors/xecli/raw/main/JRPC2.xex) Use these if you want the exact plugin files bundled with XeCLI instead of sourcing them separately. ## 2. Run the Installer If you are using the published Windows installer, launch the setup executable: ```powershell .\XeCLI-1.0.8-setup-win-x64.exe ``` The published release is self-contained. You do not need to install .NET separately for the normal installer or portable `win-x64` release paths. The installer walks through: - install scope: current user or all users - install directory selection - PATH registration for new terminals After setup finishes, XeCLI silently scans for consoles. If one console is detected, it can ask whether to connect immediately. If multiple consoles are detected, it lists them and asks you to choose one. When you confirm, XeCLI runs `rgh status` on the selected console. After installation completes, open a new terminal and use: ```powershell rgh --help rgh status rgh language ``` If you prefer the portable zip instead of the installer, extract it and run `rgh.exe` directly from that folder. ## 3. Discover or Set a Target Manually If you skipped the post-install connection prompt, use the manual discovery path: ```powershell rgh start ``` Direct targeting: ```powershell rgh target --set ``` If you use FTP features, set that target too: ```powershell rgh ftp target --set --user --pass ``` Read [FTP-and-File-Transfer.md](FTP-and-File-Transfer.md) if you want the full FTP command set and the guidance on when to use FTP instead of `rgh fs`. ## 4. Confirm the Console Is Reachable ```powershell rgh ping rgh status rgh status --quick ``` If you accepted the installer’s connect prompt, XeCLI already ran `rgh status` for the selected console. Use these commands any time you want to recheck reachability or switch back to a manual verification flow. ## 5. Resolve the Active Title ```powershell rgh title rgh title --json ``` `rgh title` with no arguments resolves the active title from the connected console. If the bundled database only knows the base system Title ID, XeCLI can still show a better path-based title name such as `Aurora`. ## 6. Inspect Live State Modules: ```powershell rgh modules list rgh modules info --name Aurora.xex ``` Memory: ```powershell rgh mem hexdump --addr 0x30000000 --size 0x40 rgh mem peek --addr 0x30000000 --type u32 ``` Screenshot: ```powershell rgh screenshot --out .\screen.bmp ``` ## 7. Use FTP-Backed Workflows Browse files: ```powershell rgh ftp list --path /Hdd1/ ``` List saves for a title: ```powershell rgh save list --titleid FFFE07D1 --device Hdd1 ``` List installed content: ```powershell rgh content list --device Hdd1 --show-types ``` List DashLaunch plugins: ```powershell rgh plugin list ``` Read [FTP-and-File-Transfer.md](FTP-and-File-Transfer.md) for the broader file and storage workflow. ## 8. Install or Stage Homebrew XeCLI can either stage the common public dashboards and tools to a USB drive or folder, or install them directly onto a detected console drive. ```powershell rgh homebrew install aurora --usb E: rgh homebrew install all --usb E: --auto-confirm rgh homebrew install aurora --device Hdd1 --ini-mode merge rgh homebrew install xm360 --usb E: rgh homebrew install timefixer --usb E: rgh homebrew install simple360 --usb E: rgh homebrew install xelllaunch --usb E: ``` USB or folder staging: - downloads the selected public package archives - extracts them into clean folders on the USB or staging path - copies the bundled `xbdm.xex`, `JRPC2.xex`, and `XDRPC.xex` files into `Plugins\` - generates `launch.ini` when Aurora is present - prompts before staging or installing unless `--auto-confirm` is supplied - supports Aurora, DashLaunch, XeXMenu, Freestyle Dash, XM360, TimeFixer, Simple 360 NAND Flasher, and XellLaunch If no removable USB drive is visible, use a normal folder path instead: ```powershell rgh homebrew install all --usb A:\UsbStage --auto-confirm ``` Direct console install: - detects only `Hdd1`, `Usb0`, `Usb1`, and `Usb2` from the live console over FTP - asks which detected drive you want to install to - asks whether XeCLI should generate a new `launch.ini`, merge plugin entries into the existing file, or leave it unchanged - uploads the selected dashboards/tools and bundled plugins directly onto the selected console drive Read [Homebrew-and-USB.md](Homebrew-and-USB.md) for the full package workflow. ### Original Xbox compatibility If you want original Xbox backwards compatibility on a modded console, use the dedicated `ogxbox` workflow instead of the normal homebrew installer: ```powershell rgh ogxbox list rgh ogxbox install hacked --usb E: rgh ogxbox install hud --include-fixer ``` Use `hacked` as the default choice for the widest compatibility on an exploited console. Use `hud` only if you specifically want the 360 guide available inside original Xbox titles and can accept the extra performance cost. Use `retail` when you want the stock Microsoft emulator behavior. Read [Original-Xbox-Compatibility.md](Original-Xbox-Compatibility.md) for the XeFu set differences and `HddX:\Compatibility` workflow. ## 9. Launch and Notify Launch a XEX: ```powershell rgh launch Hdd1:\Aurora\Aurora.xex --titleid FFFE07D1 ``` Send a notification: ```powershell rgh notify "XeCLI connected" 14 ``` ## 10. Check Session and Hardware State Signed-in user: ```powershell rgh signin state ``` Ring light: ```powershell rgh led set --preset quadrant1 rgh led state ``` If you want the hardware/session details explained in depth, read [Hardware-and-System.md](Hardware-and-System.md). ## 11. Avoid the Common Mistakes Do not start with dangerous commands until the basic path is stable. Start with: - `status` - `title` - `modules list` - `ftp list` - `screenshot` - `signin state` - `homebrew install all --usb E: --auto-confirm` - `ogxbox install hacked --include-fixer --usb E:` - `led set --preset quadrant1` Delay these until you know the target is stable: - `mem poke` - `mem search --freeze` - `modules unload --force` - `modules load --system` - `fan set` - deletion commands ## 12. Know Where to Go Next - [Commands Reference](Commands.md) for full command coverage - [Homebrew and USB](Homebrew-and-USB.md) for USB/folder staging and direct console installs - [Original Xbox Compatibility](Original-Xbox-Compatibility.md) for XeFu pack installs and HddX setup - [Hardware and System Controls](Hardware-and-System.md) for sign-in, LED, fan, and SMC behavior - [XNotify](XNotify.md) for icon IDs and notification usage - [Advanced Guide](Advanced-Guide.md) for reverse-engineering and automation workflows - [Troubleshooting](Troubleshooting.md) when the console or plugin stack does not behave as expected