J-Runner with Extras and PicoFlasher in 2026
The programmer people search in 2026 is not NAND-X first. It is a Raspberry Pi Pico running PicoFlasher, clipped to the Xbox 360 NAND (or Corona 4GB SPI/eMMC points), talking to J-Runner with Extras or J-Runner Pro. The Pico is cheap, fast, and easy to clone badly. Firmware forks matter: stock 16MB-oriented builds will mis-read a Corona 4GB. Community firmware (the names people actually Google: hax360, Kukri, 15432-style 4GB support) is part of the tool, not a flex.
What J-Runner with Extras is doing
It is the GUI around xeBuild, ECC creation, CPU key entry, KV injection, and writing XeLL. Dashboard targets in 2026 cluster on 17559 so Dashlaunch 3.21, Aurora, and Bad Update-era kernels match the rest of the scene. If you build 17511 folklore onto a box you intend to mix with modern plugins, you will debug ghosts.
Radio buttons still ruin evenings: JTAG, R-JTAG, Glitch, Glitch2, Glitch2m, Aud_Clamp on non-Xenon JTAG. I keep a sticky note on the monitor: board revision from the silkscreen, then method, then write. PicoFlasher is just the pipe.
xFlasher 360 and NAND-X
They still work. If your Pico enumerates as a serial brick, use them. Speed differences do not change dump hygiene. A slow good 4GB read beats a fast 16MB lie.
Bad Update users opening J-Runner
You might be here because XeUnshackle let Simple 360 NAND Flasher run. Congratulations: you now have the same responsibility as an RGH3 tech. Name the file, store the CPU key, do not upload nand.bin to a random Discord. If you later RGH3 that Trinity, this dump is your rollback. If you never solder, this dump is still the identity of a Winchester or E you might sell.