downgrading is very safe, as long you don't power off while downgrading. And even if you powered it off, you can still use safe mode to update to newest firmware via internet.
Just do it right, download the right packages and you are good to go
I've downgraded a dozen of (n)3ds and it always worked.
remove nag: no, it's not important
format sd: no! why? for later, do a backup of your sdcard when formating emunand (formating process of emunand repartitioning the sd card)
format 3ds: No! why? it's recommended to unlink your nands after emunand formating, but pls, use the homebrew tinyformat for that! tinyformat doesn't deletes sd files and doesn't log off off your nnid, only updates KeyY for data encryption
remove nag: no, it's not important
format sd: no! why? for later, do a backup of your sdcard when formating emunand (formating process of emunand repartitioning the sd card)
format 3ds: No! why? it's recommended to unlink your nands after emunand formating, but pls, use the homebrew tinyformat for that! tinyformat doesn't deletes sd files and doesn't log off off your nnid, only updates KeyY for data encryption
So i'll just downgrade it as it is?
edit: to go into a little more detail this is a main reason for softbricks and partial downgrades the system sees the nag update files and skips the corresponding cia(s) from the downgrade update pack leaving you with a incomplete and sometimes unloadable (soft bricked) frainkin-firmware this is why even with the correct update pack many people fail to downgrade (softbrick) and end up needing to updateAlright, I'll help clear some stuff about downgrading up. Downgrading is fairly safe, what most users miss (and doesn't seem to be in any guides) is clearing the update nag BEFORE attempting the downgrade, the update actually puts the new titles in NAND but doesn't actually install them and they need to be cleared to properly downgrade...
Bullshit, downgraded a o3ds from 10.3 to 9.2 with the update nag, downgrade was successfullyedit: to go into a little more detail this is a main reason for softbricks and partial downgrades the system sees the nag update files and skips the corresponding cia(s) from the downgrade update pack leaving you with a incomplete and sometimes unloadable (soft bricked) frainkin-firmware this is why even with the correct update pack many people fail to downgrade (softbrick) and end up needing to update
tell that to the about 300 members who softbricked or the ones who had an practical downgradeBullshit, downgraded a o3ds from 10.3 to 9.2 with the update nag, downgrade was successfully
oh i forgot we all have the same exact files/firmware on our 3ds systems and there was no 100+ page thread where people speculated about where/if anywhere they went wrong oh yeah sysupdater and nasa load on the first time every time and not to mention the gogateway website . . . oh and that number that the system settings shows you is bullshit as well so your correct no one is/gets lucky . . . im not going to argue with you further believe im wrong if you like "have a nice day"There is no real luck and randomness in computer, there is a reason why it worked... More than once, I remember
tbf its like you said *speculation*oh i forgot we all have the same exact files/firmware on our 3ds systems and there was no 100+ page thread where people speculated about where/if anywhere they went wrong oh yeah sysupdater and nasa load on the first time every time and not to mention the gogateway website . . . oh and that number that the system settings shows you is bullshit as well so your correct no one is/gets lucky . . . im not going to argue with you further believe im wrong if you like "have a nice day"
this does not explain why during attempts i and others have made at downgrading why sysupdater does not always load (you can say its due to unfinished code but then that would say that well . . . luck is indeed a factor) or why it does not always install every cia in the update pack (again you can say its due to unfinished code but then that would say that well . . . . luck is indeed a factor) or why there is a such thing as a partial downgrade in the first place (admittedly also it could be that sysupdater installs the cia over the uninstalled titles from the update nag) so correct speculation as i am no dev in the least but i have been helping people with cfw installs scene September (and i take hardcore notes)also sounds like BS that update nag affects the downgrade process, as sysupdater directly installs cias regardless its literally a command to do that only the update nag isnt even accessed via the cia manager so it should have 0 faults in the causing of softbricks.
where do you think the update nag is stored on the say it with me . . . "on the nand" where does sysupdater write to you guessed it . . . "the nand" how is extra fw files getting in the way impossible type bsas sysupdater directly installs cias regardless its literally a command to do that only the update nag isnt even accessed via the cia manager so it should have 0 faults in the causing of softbricks.
true most of them were new accounts but i have been using guides in gbatemp for years before i made an account a post count is not an iq level so to say that none of them knew what they were doing sounds more presumptuous then the update nag getting in the way "dont you think"Also notice a sudden 100+ page thread of NEW MEMBERS that all suddenly appeared when downgrade became available and the influx we are still getting now.
Cause not knowing what your doing until after your fail isnt a common occurrence atm
and yes a lot of people fuck themselves i dont deny that but even in saying 90% of failed downgrades are negligence there would still be 10% of people. . . competent people fail stillFor example look another failed downgrade
http://gbatemp.net/threads/problem-after-downgrade-o3ds-9-5-0-23-to-4-5-0-10.413115/
honestly the failed downgrades are 90% to negligence and everyone just bum rushing it the first week.
right but the question remains and may in fact have to do with my pointMeaning any pause or freeze would result in softbrick.