I have a bit of an interesting N3ds on my hands, and in order to downgrade it properly i think i need some confirmation on a couple of details involved. Lets start with why this case is slightly special, and not commonly discussed. This N3ds used to be hacked with MenuHAX with an unlinked emuNAND (The emuNAND being the formatted one). I say used to, as i upgraded my sysNAND to 11.0 by accident. Menuhax users take note, it can happen to the best of us. In any case, this has a number of implications, chief among them that i have a backup of the 9.2 SysNAND that was originally made with Decrypt9. It also means i have 3 downgrade paths, and I'm wondering which would be ideal. First, i could restore my 9.2 nand backup via dgTools. This would probably be the easiest and possibly safest option. However, i don't know how reliable it is or if it's even a valid option in this case. Does anyone have any experience with it? The other two options involve using SysUpdater to downgrade as per usual. But my concern is that if it softbricks, I'd be back on 11.2. Which leads me to question two. Would dsiwarehax still be installed and usable in this case? If so, there's no real risk in going down this path as I'd have infinite retries. The third option would be to format using Tinyformat beforehand in order to nullify the softbrick risk. However, given that it has an unlinked emuNAND, I'd need to format it twice, right? similar to the 2.10 downgrade. As it had something to do with a unique identifier being randomized to the same number. I've forgotten the exact reason, and it's been kind of difficult to dig it back up. Does anyone have any insights regarding this?