Hacking Is emuNAND irrelevant now?

[Daniel72]

I've never gotten into 3DS hacking until today.
I remember hearing a lot about emuNAND in the past, but I just followed 3ds.hacks.guide with little mention about emuNAND. The guide states that by following the guide I boot Luma3DS CFW SysNAND by default. Is it not a thing anymore?


A few more questions:
1. Is the GodMode9 like Priiloader in wii homebrew?
2. Is the FBI like a WAD installer in wii homebrew?

 

[KleinesSinchen]

I've never gotten into 3DS hacking until today.
I remember hearing a lot about emuNAND in the past, but I just followed 3ds.hacks.guide with little mention about emuNAND. The guide states that by following the guide I boot Luma3DS CFW SysNAND by default. Is it not a thing anymore?


A few more questions:
1. Is the GodMode9 like Priiloader in wii homebrew?
2. Is the FBI like a WAD installer in wii homebrew?

EmuNAND is not needed/helpful for the average user.

GodMode9 is a file manager (and much more!) that can be started instead of the normal operating system. It is not installed (normally – B9S is the actual modification on NAND) and does not intercept/modify the booting process like Priiloader does. Since B9S gives the user full system control milliseconds after power on and can load any .firm payload even if the complete normal OS is trashed, there is no need for another "brick protection" like Priiloader on Wii.

Yes, FBI can be somewhat compared to a WAD installer. Don't delete and NAND titles with FBI.


Good luck and have fun!

 

[Daniel72]

EmuNAND is not needed/helpful for the average user.

GodMode9 is a file manager (and much more!) that can be started instead of the normal operating system. It is not installed (normally – B9S is the actual modification on NAND) and does not intercept/modify the booting process like Priiloader does. Since B9S gives the user full system control milliseconds after power on and can load any .firm payload even if the complete normal OS is trashed, there is no need for another "brick protection" like Priiloader on Wii.

Yes, FBI can be somewhat compared to a WAD installer. Don't delete and NAND titles with FBI.


Good luck and have fun!

Oh wow, never knew the 3ds was super brick proof. That's super cool!

Thanks for the kind reply!

 

[Itsuki235]

Oh wow, never knew the 3ds was super brick proof. That's super cool!

Thanks for the kind reply!

It is only brick proof if you have a backup of your system. Stuff can still brick the main OS rendering the main osunbootable. Without a backup already created, it will be difficult to get it working again, even if you can boot into godmod9. Make sure to create one as the guide specifies.

 

[lone_wolf323]

It is only brick proof if you have a backup of your system. Stuff can still brick the main OS rendering the main osunbootable. Without a backup already created, it will be difficult to get it working again, even if you can boot into godmod9. Make sure to create one as the guide specifies.

Not needed of just your system backup. Thats what ctrtransfer is for aswell as ntrboothax. They will unbrick you even if you dont have a backup made.

 

[TurdPooCharger]

It is only brick proof if you have a backup of your system. Stuff can still brick the main OS rendering the main osunbootable. Without a backup already created, it will be difficult to get it working again, even if you can boot into godmod9. Make sure to create one as the guide specifies.

If there's a softbrick that CTRTransfer (Type D9) can't fix, I would like to know about it.

 

[Itsuki235]

Not needed of just your system backup. Thats what ctrtransfer is for aswell as ntrboothax. They will unbrick you even if you dont have a backup made.

If there's a softbrick that CTRTransfer (Type D9) can't fix, I would like to know about it.

Without a backup already created, it will be difficult to get it working again

I did not say it was impossible, just overly difficult. It is much simpler to just create a backup in the first place to not have to jump through hoops to get everything working again. GM9->backup/restore system ->done. There is no need to make it more restoring the system more complicated than that.

 

[TurdPooCharger]

I did not say it was impossible, just overly difficult. It is much simpler to just create a backup in the first place to not have to jump through hoops to get everything working again. GM9->backup/restore system ->done. There is no need to make it more restoring the system more complicated than that.

Restoring the SysNAND have the drawbacks of erasing your user settings, DSiWare games & saves, and possibly locking away the Nintendo 3DS folder if the movable.sed's encryption KeyY no longer matches.

I do not recommend this recovery method for * as an initial repair if one has important data they don't want to lose.

 

[Itsuki235]

The only important data on the console that is irreplaceable is save data, which can be exported to the SD card using Checkpoint and is restored after restoring the nand.

There is no reason to make restoring the system more complicated than it needs to be. Creating a full system backup is best practice for a reason.

 

[TurdPooCharger]

The only important data on the console that is irreplaceable is save data, which can be exported to the SD card using Checkpoint and is restored after restoring the nand.

There is no reason to make restoring the system more complicated than it needs to be. Creating a full system backup is best practice for a reason.

Except you can't export the save data with Checkpoint if the 3DS firmware is bricked. Bricked native firmware means no access to Checkpoint. If you can't decrypt and extract those saves by typical means, one has to resort to the CTRTransfer (Type D9) - Rebuild 3DS Database: (C) Manual - (1c) Backup Saves to do do.

If your 3DS system was involved in a System Transfer where it received the Nintendo 3DS folder from another (source) system, restoring the SysNAND made prior to the System Transfer will cause your (target) system to lose all those received games, dlcs, updates, and saves.

Hastily restoring the SysNAND can cause problems for data recovery if one does not consider what they loss in the process.

Edit - Also, lots of people don't* follow the good practice of periodically backing up their SysNAND. Or at all for that matter..

 

[Itsuki235]

Except you can't export the save data with Checkpoint if the 3DS firmware is bricked. Bricked native firmware means no access to Checkpoint.

Which is why you regularly backup your save data. Duh...

 

[TurdPooCharger]

Which is why you regularly backup your save data. Duh...

Late edit in my last post. That advice is like wearing a mask and socially distancing yourself while in public these days. Not everyone does it.

You get those who come here asking for help to unbrick their 3DS when they don't have a SysNAND image or get back their games & saves when they weren't backing up saves+extdata in the first place. What to do or tell them?

The easy answer to those unfortunate enough mess up would be, "Ah too bad. Get rekt! Should have make teh backupz u dum ehdeeuht! Better luck next time. lol."

I guess if you look around here GBAtemp, not-so-easy answers are given out more times than not.