Dashlaunch 3.21 live flags: a conservative 2026 checklist
Dashlaunch is still the adult in the room on a persistent RGH3 or JTAG 360. Version 3.21 is the build people pair with kernel 17559. It loads plugins, sets live-related flags, default dash paths (Aurora, FSD, NXE), and fan targets. On Bad Update, XeUnshackle loads a launch.xex from the USB session. That is not permission to use Dashlaunch’s “install to flash” on a retail NAND. FreeMyXe users get bricked that way. Read it twice.
What I actually enable
A current stealth plugin if I am going Live, xbdm.xex if I want Neighborhood/FTP, a sane auto-off, and nothing that dumps debug strings into a session I care about. I leave trainers and screenshot hooks off until sign-in succeeds once. If you cannot sign in with a short ini, adding a cover downloader will not help.
What I leave off on purpose
2012 syscall piles. Region folklore copied from Phat JTAG guides onto Corona RGH3. Anything not rebuilt for 17559. People copy ini files from 2018 Trinity guides onto XeUnshackle USBs and then write essays about stealth being dead.
Order of operations
Stable glitch or a working Bad Update session. Known-good KV. Minimal Dashlaunch. Then stealth. Then a single sign-in. Then games. If you reverse that list you will spend a weekend debugging step four while staring at step one.
I do not publish my ini. If the order says “fix identity” and you have never done that swap, this KV swap walkthrough is the bookmark I use so XeLL and Flash360 do not get mashed into one 1 a.m. experiment. That bookmark is for Live players and for anyone injecting a vault into xeBuild after a dump — including people who still swear they will never sign in.