Separate names with a comma.
Discussion in '3DS - Flashcards & Custom Firmwares' started by Jil.10, Jan 6, 2016.
Hi, is now safe downgrade a N3DS? If it isn, what is the problem?
No. Risk of hard brick.
Wait for KTM to be released.
Use the search button. There are literally dozens of threads about this.
The most recent builds of sysUpdater have become much more stable and are relatively safe but that means there is still a nonzero chance of a hard brick.
JustPingo himself explains that it won't change anything.
The steps are the same.
If you use the last sysUpdater and you check your files (checksum), everything should be ok.
There is still a risk of brick because you are modifying system files but the risk will be the same with KTM...
That's not what the guy that made the downgrading tutorial thread said in the OP.
The new sysUpdater has a far less chance of bricking your system. You may encounter a soft-brick, but that's easily fixed. It'll be the same thing with KTM, just verify your files and follow the steps exactly as written. It isn't hard, and it's nowhere near as dangerous as it was when first released.
Not really that safe, my N3DS got bricked from trying to downgrade. Had to send it to Nintendo as well even though they charge like 85$ lol. But oh well, I learned my lesson. Just make sure you can access your Nand via hardmod.
Is a so-called "hard brick" possible on a N3DS due to bad luck?
That won't ever change tho.
OP, downgrading probably won't get any safer, if you know what you're doing go for it.
Now a days it's user error. Like downloading the wrong firmware..
There's a version out which installs native_firm last.. I think that's how it should have been from the start, but it drastically reduces any chance of a hard brick.
Memchunkhax2 is very unstable on new 3ds (much worse than old 3ds in my tests).
A lot of that has to do with Steveice not having a new3ds (I think).
No hard brick since the new release of SysUpdater.
The problem with the first build is that it deletes all the CIA and it installs the part useful for the "Safe_firm" (recovery to upgrade to the last firm in case the downgrade fails) at the end. The problem is that if you've got a problem, you can't update to 10.3, you're screwed.
Now with the latest build, the safe_firm is installed first. Then sysupdater deletes a CIA and replace it, one after the other. (It doesn't delete everything and then install everything, it's CIA per CIA)
At the moment, except if the native_firm install fails (I don't think that it happened with the latest builds), I don't think you can hard-brick the 3DS. You can soft-brick, but you just have to boot into the recovery menu to update to 10.3 and retry.
It's not entirely safe but the risk is quite small atm.
I did a downgrade, 9.9E to 9.2E, no problem, not even at the reboot.
The most difficult part is to boot memchunkhax2 because usually it fails to get the permissions. Once sysupdater got those permissions, no problem.
Oh, I thought doing this on an N3DS could risk you getting hard bricked. Anyway, it doesn't bother me. I have an O3DS and the process worked fine.
Warning: Spoilers inside!
O3DS MASTER RACE!