Simple 360 NAND Flasher versus PicoFlasher
Two dump paths now sit in the same Discord questions. PicoFlasher (or xFlasher 360 / NAND-X) is a programmer clipped to SPI or Corona 4GB eMMC, driven by J-Runner with Extras. Simple 360 NAND Flasher is an on-console app that can read/write flash after you already have unsigned code — classically RGH/JTAG with the right patches, and in 2026 often after Bad Update 1.3 plus XeUnshackle’s HV access (Syscall0-style backdoors are why this app gets mentioned in XeUnshackle notes at all).
When the software dumper is enough
If XeUnshackle is up on dashboard 17559 and you want a copy of retail NAND before you ever buy a Pico, the on-console flasher is how Winchester and E owners enter dump culture. That file still contains kv.bin. It still wants a CPU key stored beside it. It is still not something you upload to a public channel. Congratulations: you are a NAND person. Read dump hygiene.
Software dumps are a poor choice when the console does not boot far enough to run XEX, when 4GB Corona mapping is wrong, or when you need to write XeLL Reloaded to the first 50 blocks because the glitch never reached a dash. That is hardware programmer territory. I do not debug a no-XeLL Trinity with Simple 360 NAND Flasher. There is nothing simple about a box that cannot run the app.
When PicoFlasher is the adult
RGH3 installs, bricks, Glitch2/Glitch2m writes, virtual eFuses, and 4GB eMMC that lied to a USB tool. J-Runner with Extras remains the GUI around xeBuild. A Raspberry Pi Pico is cheap; firmware forks that speak Corona 4GB are not optional trivia. See the PicoFlasher note.
Writing is scarier than reading
Reading NAND with either tool is a backup. Writing NAND with either tool is how you meet God. On-console writers plus a Bad Update session plus “install Dashlaunch to flash” is how FreeMyXe users brick retail images. I treat write mode as RGH3-only unless you know exactly which image you built. Winchester owners: keep a read, do not get clever with xeBuild Glitch2 images meant for Trinity.
winchester_badupdate_read.bin, not nand.bin. Future-you will try to flash it onto a Corona at 1 a.m. otherwise.Identity work after a dump is still pairing CPU key and vault, not “run the flasher again.” Software and hardware dumpers are pipes. They do not unshare a KeyVault.