Tutorial Simple Guide to Downgrading your 3DS

Have you been able to successfully downgrade your 3DS/2DS?


  • Total voters
    1,055
Status
Not open for further replies.
They have the encryption keys.
then its not permanent like if you get a brick just send it into them make sure to take all the hack files of the sd though and say you dropped it while it was updating or some thing and it bricked will cost money but you get it unbricked
 
is there a way to fix a permabrick? i mean, i have some old 3DS parts over there, if i get a permabrick, then what part should i replace? CPU? which? just in case
 
then its not permanent like if you get a brick just send it into them make sure to take all the hack files of the sd though and say you dropped it while it was updating or some thing and it bricked will cost money but you get it unbricked
I don't think nintendo has done the repair centers since the snes days. And even if they did you would have to be under warranty.
 
I have o3ds in 9.4 and 9.5...
Someone told me that I have to update it to 10.3 first before I started downgrading to 9.2, is it true?
Or can I start downgrading right away?
 
is there a way to fix a permabrick? i mean, i have some old 3DS parts over there, if i get a permabrick, then what part should i replace? CPU? which? just in case
You would have to re-flash the NAND using a backup of your own NAND before the brick.
 
HEY EVERYONE, two guys got this working on the FIRST try, by just formatting the SD before using sysUpdater.

Everyone should try that out before keep trying and post if it managed to get the downgrade working
 
would you wait or lose an 100 to 200 dollar system why are people trying this

Mob mentality. Everyone heard about a great thing and they want it asap. Unfortunately, this great thing is unreleased code and not fully tested yet so people who don't know exactly what they are getting into are willfully risking their systems because they either don't understand the huge risks, or don't care. Some people have money and systems to spare, others assume they won't have any problems at all.

I'm also sure there are some that simply don't understand that a brick is unfixable by the common user.
 
Last edited by deishido,
  • Like
Reactions: WeedZ
Mob mentality. Everyone heard about a great thing and they want it asap. Unfortunately, this great thing is unreleased code and not fully tested yet so people who don't know exactly what they are getting into are willfully risking their systems because they either don't understand the huge risks, or don't care. Some people have money and systems to spare, others assume they won't have any problems at all.

I'm also sure there are some that simply don't understand that a brick is unfixable by the common user.

That thing of "this is unofficial" and "this is unreleased code" it's just bullshit
 
That thing of "this is unofficial" and "this is unreleased code" it's just bullshit
Why? Because Steveice10 compiled a quick update to try and salvage the disaster of all the lemmings walking off the brick cliff?

--------------------- MERGED ---------------------------

why can't we make nand back ups on newer flimwares to avoid this
You can with a hardmod
 
would you wait or lose an 100 to 200 dollar system why are people trying this
Impatient champs. Whatever
That thing of "this is unofficial" and "this is unreleased code" it's just bullshit
Why is it bullshit? Because kids on gbatemp can't wait another week before downgrading? Funny.
 
Why? Because Steveice10 compiled a quick update to try and salvage the disaster of all the lemmings walking off the brick cliff?

--------------------- MERGED ---------------------------


You can with a hardmod

Steveice10 has nothing to with sysUpdater.

Impatient champs. Whatever

Why is it bullshit? Because kids on gbatemp can't wait another week before downgrading? Funny.

Code is released and THERE IS NOT ANYTHING OFFICIAL.
 
That thing of "this is unofficial" and "this is unreleased code" it's just bullshit

But really it's not? Almost all bricks have been caused by user error, and most of the sysupdater caused bricks are on the n3ds, which was untested as of the most recent github push. This version of sysupdater was made for this downgrade using memchunkhax2's code, but it wasn't a full release. I'm pretty sure it's just testing ground for KernelTimeMachine's release coming up. Either way, this code wasn't optimised for downgrading yet and anyone running it at this point should understand the risks associated with running ANY code that affects system files. Yeah, steveice10 made a slightly more optimised edit that changed the order that things happened to make it safer (and also implemented memchuckhax2 I'm seeing) but its still a dangerous program for unskilled users to use.
 
Last edited by deishido,
If these new hax enable NAND downgrading from 10.3, could they not also allow a backup to be made of 10.3? That way downgrade permabricks could be recovered using a hardmod installed after the event.
Purhaps, but you'd still need to be hardmodded in order to restore.
Steveice10 has nothing to with sysUpdater.



Code is released and THERE IS NOT ANYTHING OFFICIAL.
Steveice10 incorporated sysupdater into the new memchunkhax2 in order to gain am:u

But since you know better then I do, link me the official release and the github that's not Steve's.
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum