Aftercare · 12 min read · updated August 2026
First boot after a Corona RGH3: a conservative checklist
The glitch working once on the bench is a good start. It is not a finished console. I run the same dull sequence every time so I do not discover a KV, HDMI, or launch.ini problem after the clips are back in a Trinity Slim. Bad Update users can steal the identity and HDD parts of this list; they can skip the solder-stability part.
Power, picture, then software
Cold boot from the wall, not a soft restart. Confirm glitch time is stable across three cycles. If it hunts past ten seconds on RGH3, I do not “set it and forget it.” Timing, POST, and a cold joint are cheaper to fix now than after a customer has the unit for a week. Compare that to Bad Update 1.3 on a Winchester: failure is a USB retry, not a reflow.
HDMI sparkles on Corona are a separate repair. Do not hide them with analog AV. If the picture is dirty, fix the encoder path or be honest that the board is tired. Wi-Fi modules on Corona still die; Ethernet is a valid ship configuration.
Dashlaunch 3.21 before Live, Aurora before themes
I load a known Dashlaunch 3.21 config aimed at kernel 17559 (or whatever xeBuild actually wrote), disable Live-unfriendly folklore, and confirm the default dash path. Homebrew launchers can wait. If Freestyle Dash or Aurora is going on the HDD, I still boot retail NXE once to make sure the NAND side is sane. FATXplorer on the PC is for the drive; it is not a substitute for a NAND dump sitting next to the CPU key text file.
XeXMenu still earns a folder as a recovery hammer. It is not a daily UI. Aurora is. FSD is nostalgia. Neighborhood plus xbdm.xex is for people who want FTP without a third-party file manager on the 360. None of that loads if Dashlaunch is missing or if you installed launch.xex to flash on a FreeMyXe session.
Identity last — and not only for banned boxes
Only after the board is stable do I care about kv.bin as a change. I always care about it as a backup. If the original vault is banned, replacing it is a software job, not a glitch job. Pair the CPU key, verify the vault is not already circulating, then test. The click-by-click of that swap is in this Xbox 360 KV change walkthrough — I still do not reprint it on the hardware checklist.
If you are offline-only, you still should not clone this dump onto a second Jasper. Shared identities are how waves look like “stealth died” for twenty people at once. If you play Live, stealth plugins (the names rotate: proto-style servers, xbGuard, Cipher, Nfinite in checker lore) sit in launch.ini after identity is unique. A Corona that boots Aurora and still cannot sign in is almost never “the RGH3 diode.”
When the checklist is green, I reseat the RF board, check wireless, label the HDD with the CPU key nickname (not the key itself on a sticker on the shell), and only then close. That is the whole job. Everything else is people wanting 360 modding to be more mystical than board ID plus dump hygiene.