J-Runner with Extras in 2026: still the NAND desk app
Forum threads age. The job does not. J-Runner with Extras remains the Windows front-end most techs use to talk to a Raspberry Pi Pico, load xeBuild targets (often dashboard 17559), and stitch a rebuild. This is not a stealth tool and not Aurora.
What you still use it for
Reading/writing NAND via PicoFlasher, entering a CPU key, choosing Glitch2 / Glitch2m style outputs for RGH3 paths, and exporting or injecting identity files. Hardware pairing notes: J-Runner + PicoFlasher · RGH context: Pico + RGH3.
CPU key field vs KeyVault slot
Operators still paste the CPU key and assume “pairing” fixed Live. The key unlocks the image. The KeyVault (kv.bin) is the Live identity. You can build a perfect xeBuild output with a burned vault. If the dump’s original serial is shared or banned, replace it with a checked unshared KV — do not hunt for a magic J-Runner checkbox.
Checked stock for that swap: unshared.shop. Walkthrough: KV change guide. Identity map: what kv.bin is.
Corona 4GB caution
4GB Corona is not a 16MB file with hope. Use the SPI / 4GB-aware path your Pico build supports. Wrong size writes are how “J-Runner bricked my Slim” posts are born.