If the hardware for blowing fuses exist on the system but there's no software for such task, all it takes is upload the necessary software to blow a fuse. Connecting on the network would allow for that. :shrug:
Sounds fishy to me. What was the game everyone was playing when this happened? Same game? Same source?
No ones story matches up. Impossible to pinpoint atm. What strikes my interests is keep in mind any content leaked contains a console ID from the downloader.
CB can still be blacklisted. And that's something they could use to ruin a unit and still be able to repair it if it was ruined by mistake.
r6t3 must be disabled on all non whitelist kits asap. They might scramble nand as well as part of the logic bomb but backup should be possible. If they get the cpu you will need to replace cpu with matching nand. I might have confirmation tomorrow. This serves as a warning, don't play around in the dog's yard and not expect to be bit.
So how would you go about backing up your nand from a devkit then? Sounds like it's worth doing regardless...
a few things to help find the cause: i never ran games/code on the kit, it was used for downloading ONLY i never leaked anything i did not have anyone on my friends list backup from good nand backup via LPT give exactly the same result error code is 0022