So Plailects Guide says: "All variations of sysUpdater, not just sysDowngrader, have a very small chance of causing a “soft brick” once the downgrade is complete and the device reboots. This will cause the system to boot directly to the Nintendo error screen instructing users to power off the device. The reason for this is unknown, but can be prevented by performing a system format before downgrading. It seems to happen very often on systems with ambassador status or who have DSiWare installed. Once this error happens, it can only be fixed by using recovery mode (boot holding A + R + L + Up on the D-Pad) to update to the latest system version. As of the time this is written, the latest version (11.2.0) has completely blocked all software downgrading, and if someone encounters this error they will be locked out of any further downgrading unless they downgrade their NFIRM." So I have two (maybe noobish) questions, so the 1st one: I am gonna format the source 3ds so that I can create a new nnid and then do the dsiware stuff and I am also gonna normaly format the target 3ds to remove its nnid, so my first question is, can I safely format the source 3ds via system Settings without loosing A9LH or should I better use tinyformat? The 2nd one: So as quoted above, can I safely format the target system after the NFIRM Downgrade to prevent a soft brick? Cause I don´t see any way how formatting will restore the NFIRM so will this work? Better system Settings or Tinyformat? Btw this may sound like I am a noob, No I am not, I have A9LHed two Consoles so far (the first one when nothing was stable and safe) but this is the first DSiWare Downgrade so I won´t risk any sort of brick, well I wan´t to prevent it as much as possible.