Hacking How safe is the downgraded 2.1.0 on an old 3DS?

[Searinox]

As the title says. I basically never really planned on forfeiting emuNAND because I like an extra layer of security as well as the possibility to screw up, or reverting things I don't like easily.

So after an A9LH + Luma install guide-style, I stuck to my 11.2 emuNAND and am keeping my 2.1.0 sysNAND. I'm happy with this because it unlocks some older style NDS flashcarts and because I don't plan on using the sysNAND in any way online. It's even unlinked.

But let's say someday I want to sell my console or were to want to update for whatever reason. I know that on a new 3DS it will install the o3DS firmware and brick, and I know that on 2DS firmwares older than 6.0 would have compatibility issues.

What about an old 3DS? The firmware was designed for it afterall. It seems to be working fine. Though I've not tried updating or resetting. Can I consider it as safe and as usable as a "legit" 2.1.0?

 

[Distrance]

If that day ever came you could flash your emuNAND onto your sysNAND as the guide instructs you to do anyways

FYI sticking to emuNAND for security is a bad argument, when there's literally no chance of a brick anyway. Lets say you fuck up something. Oh too bad. You just boot into Decrypt9 and restore your sysNAND .. Oh lookie it's fixed. emuNAND is nothing but a waste of space.

 

[Hayleia]

Lets say you fuck up something. Oh too bad. You just boot into Decrypt9...

Except if that "something" you fucked up touched a9lh in some way. It's probably hard to do that, especially not on purpose, but don't underestimate people who fuck up.

and restore your sysNAND ..

Rule number 4: people who fuck up don't have NAND backups.

 

[HyperT]

Except if that "something" you fucked up touched a9lh in some way. It's probably hard to do that, especially not on purpose, but don't underestimate people who fuck up.


Rule number 4: people who fuck up don't have NAND backups.

If you screw up a9lh an emunand isn't going to be of any use

 

[Hayleia]

If you screw up a9lh an emunand isn't going to be of any use

True, but it's even harder to fuck up a9lh from an emuNAND. Just an example, you only have to update a New 3DS from Gateway sysNAND to fuck up on sysNAND. And on emuNAND you're safe.
Then you may say "don't use Gateway, on sysNAND or emuNAND" (assuming the guy doesn't care about cheats). But don't go thinking noobs know why they use the setup they use.

 

[Searinox]

Good to know that I could flash the emuNAND back to sysNAND. I am still using a Gateway setup because I have one and it is simply easier for me to keep going with what I have. I have backups of both my current 11.2 emuNAND and the 2.1 sysNAND. But is the sysNAND I downgraded to as safe as a legit one?

 

[yusuo]

Personally I use emuNAND, if you got the space why not, its not harming anyone and its just an added precaution in the very unlikely event something bad does happens

 

[Deleted User]

Good to know that I could flash the emuNAND back to sysNAND. I am still using a Gateway setup because I have one and it is simply easier for me to keep going with what I have. I have backups of both my current 11.2 emuNAND and the 2.1 sysNAND. But is the sysNAND I downgraded to as safe as a legit one?

Basically when you downgrade to 2.1.0 you are only there for a short time to install a9lh through the webbrowser and extract the otp.Once that's done you can't brick if you have NAND backups and chainload acces to hourglass9.Even if you don't have a NAND backup you can still fix yourself with a 9.2 ctr transfer and decrypt9.

 

[Cuphat]

It's safe in that it won't harm your console, but I'd recommend not ever updating it directly. So long as you have your EmuNAND/other NAND backups, you should be safe as A9LH will be there to let you restore it if anything goes wrong.

I'd recommend restoring your EmuNAND or old SysNAND back to SysNAND and, if necessary, unlinking it again. DS flashcarts should still work fine with Luma on SysNAND, even on 11.2. You don't have to, though.

Just make sure you are using Hourglass9 (or Decrypt9 with the (keep A9LH) option) to restore your NANDs to make sure you don't overwrite A9LH.

 

[Searinox]

I've see ppl updating their 2.1 firmware through online or game carts and ending up with either unusable frankenfirms or bricks. Are those strictly a 2DS and new 3DS occurrence though? Same question about format system reset.

 

[HyperT]

True, but it's even harder to fuck up a9lh from an emuNAND. Just an example, you only have to update a New 3DS from Gateway sysNAND to fuck up on sysNAND. And on emuNAND you're safe.
Then you may say "don't use Gateway, on sysNAND or emuNAND" (assuming the guy doesn't care about cheats). But don't go thinking noobs know why they use the setup they use.

Gateway is obviously the exception to the rule - I was going to edit the original post with: unless there's a pc program to pull a valid nand backup from an emunand

 

[Hayleia]

Gateway is obviously the exception to the rule - I was going to edit the original post with: unless there's a pc program to pull a valid nand backup from an emunand

Yes there is https://gbatemp.net/threads/emunand-tool-release-and-support-thread.359239/
Not the only one, there is also emunand tool max or something. I used to use them and think they were an advantage to sysNAND (since I can directly put my backups in a dedicated folder on my PC instead of having them disorganized on my SD card) but that was before I got a New 3DS with the SD card behind two screws...

 

[HyperT]

I've see ppl updating their 2.1 firmware through online or game carts and ending up with either unusable frankenfirms or bricks. Are those strictly a 2DS and new 3DS occurrence though? Same question about format system reset.

2ds 2.1 format system has a bypass now.
Cart updates upto a point are fine - 2ds should be fine with any cart update [but ideally over 6.x]

 

[Ryccardo]

What about an old 3DS? The firmware was designed for it afterall. It seems to be working fine. Though I've not tried updating or resetting. Can I consider it as safe and as usable as a "legit" 2.1.0?

Yes

 

[dkabot]

O3DS is the safest A9LH case anyway.
If you were to, say, update without FIRM protections, you'll just be on the latest FW without A9LH.
Should you do the same on a N3DS, that's a guaranteed brick.

Between that and 2.1 being made for the O3DS (so no close -> brick bug) you're fine.
I do, however, question the point of EmuNAND, but that's your problem.