I've been searching for hours and haven't been able to find a clear answer, so I'm turning to the community.
I had a clean unpatched switch running 10.1.0. As part of my hacking project I bought a RCMLoader Model One B dongle. This loader has the ability to inject multiple different payloads, and comes preloaded with SXOS, Renix, and Hekate.
My intention was to boot into Hekate to immediately do a NAND backup before I touched anything else. So, I inserted the jig, went into RCM, and plugged in the dongle, thinking I would be able to toggle the dongle to boot into Hekate before the payload injected. To my surprise, the dongle immediately injected the SX OS payload. Since I didn't have any SX OS files on my SD Card, all I got was the missing "boot.dat?" screen. I turned off the switch, toggled the dongle to inject the Hekate payload, booted into Hekate, and did a NAND dump.
My question is - did simply injecting the SX OS payload and getting the "boot.dat" screen dirty my NAND before I was able to back it up? Is my NAND backup dirty?
Any help would be appreciated.
I had a clean unpatched switch running 10.1.0. As part of my hacking project I bought a RCMLoader Model One B dongle. This loader has the ability to inject multiple different payloads, and comes preloaded with SXOS, Renix, and Hekate.
My intention was to boot into Hekate to immediately do a NAND backup before I touched anything else. So, I inserted the jig, went into RCM, and plugged in the dongle, thinking I would be able to toggle the dongle to boot into Hekate before the payload injected. To my surprise, the dongle immediately injected the SX OS payload. Since I didn't have any SX OS files on my SD Card, all I got was the missing "boot.dat?" screen. I turned off the switch, toggled the dongle to inject the Hekate payload, booted into Hekate, and did a NAND dump.
My question is - did simply injecting the SX OS payload and getting the "boot.dat" screen dirty my NAND before I was able to back it up? Is my NAND backup dirty?
Any help would be appreciated.