OK, my systems are fine, But I lost all my files in a hard drive crash. I have made new band backups, but I can't figure out how to backup the essential files again.
Hacking Backup essential files again?
- Thread starter NicknameGoesHere
- Start date
- Views 8,472
- Replies 11
There is an option in Godmode to do that.
- Embed an essential backup right into a NAND dump: This is available in the A button menu for NAND dumps. Essential backups contain NAND header, movable.sed, LocalFriendCodeSeed_B, SecureInfo_A, NAND CID and OTP. If your local SysNAND does not contain an embedded backup, you will be asked to do one at startup.
Sorry how exactly do you back them up again? This is the only topic on google about this so-called "essential files backup".
I tried moving the files from /gm9/out (especially the "essential.exefs") to a different folder on the microSD, hoping GodMode9 will ask me again to back them up, but it never did.
The only other thing I could find is this post saying that:
What is "sysnand virtual"? I'm asking because I skipped to "Launch GodMode9 by holding (Start) during boot" (from this guide) while I was on the old 11.1.0 firmware, and now I'm worried that those might be the NAND headers from that old firmware and may cause a brick if I ever need to restore the 11.8.0 sysnand backup.
I tried moving the files from /gm9/out (especially the "essential.exefs") to a different folder on the microSD, hoping GodMode9 will ask me again to back them up, but it never did.
The only other thing I could find is this post saying that:
What is "sysnand virtual"? I'm asking because I skipped to "Launch GodMode9 by holding (Start) during boot" (from this guide) while I was on the old 11.1.0 firmware, and now I'm worried that those might be the NAND headers from that old firmware and may cause a brick if I ever need to restore the 11.8.0 sysnand backup.
Last edited by DSpider,
D
Deleted User
Guest
1: Boot Godmode9
2: Press the home button
3: Select Scripts...
4: Select GM9Megascript
5: Select Backup Options
6: Select either SysNAND Backup or EmuNAND Backup
7: Wait for the process to complete
8: Place the files created by the backup process to a safe directory located on your PC
I've been backing that file up even though I don't of its importance.
--------------------- MERGED ---------------------------
actually, these are all the files I've backed (have about 30 NAND backups). I took these from several of my folders so that I don't have to post multiple images:
do any of those files need to be rebacked up after installing a new firmware or game? I've been backing them all up every time I add something new.
The essential.exefs contains several console unique files that serves as a secondary mini backup in case the user was lazy and didn't do their due diligence backing up their SysNAND *.bin image like they were suppose to. Upon installing custom firmware and launching GodMode9 for the first time, GM9 will create and embed this archive onto the NAND.
- frndseed (LocalFriendCodeSeed_B) - Required for access to online play.
- hwlcal0 + hwcal1 (HWCAL0.DAt + HWCAL1.DAt) - Hardware calibrations for the top and bottom screens. Without these, the displays look like shit.
- movable (movable.sed) - Contains a copy of the LFCS_B. Required for access to Nintendo eShop. This has the 0x30 slot KeyY that controls the encryption + decryption of the Nintendo 3DS folder.
- nand_cid - I have no clue the importance of this. Perhaps it's for data recovery should one physical desoldering or remove the actual nand chip from the motherboard.
- nand_hdr (nand header) - Contains a 256 bytes NCSD signature in order for the SoC to validate the nand image. Also basically has the entire partition tables that makes up the rest of the 3DS firmware. In case you super softbricked your nand, like by force flashing a foreign SysNAND *.bin image, you'll need this header to rebuild from scratch.
- otp (one time protection, opt.bin) - Required to mount and decrypt the raw nand image dump for desktop program, ninfs.
- secinfo (SecureInfo_A / B) - Contains the 3DS serial number and region code. Read more about it here.
Last edited by TurdPooCharger,
damn, man. you're an encyclopedia. heh. 
--------------------- MERGED ---------------------------
@TurdPooCharger , I do have a question. which files should I backup if I install a new game or new firmware? the NAND, but tickets and titles.db? I've been backing up all of those files every time, which I think I'm just paranoid about.
--------------------- MERGED ---------------------------
@TurdPooCharger , I do have a question. which files should I backup if I install a new game or new firmware? the NAND, but tickets and titles.db? I've been backing up all of those files every time, which I think I'm just paranoid about.
damn, man. you're an encyclopedia. heh.
Dang, 30 NAND backups is kinda excess imo, lol. Keep the first backup that you've ever made when you first hacked the 3DS and the latest one that contains your most up to date setup.
If you ever softbrick the firmware and are afraid about losing your current user setup, try backing up the SysNAND and attempt 3DS firmware repairs with either CTRTransfer or CTRTransfer (Type D9). * These should retain as much of your setup before the brick, except for the firmware downgrade and maybe the need to reinstall DSiWare games (use the gm9 script's DSiWare CIAs & Saves).
- aeskeydb.bin - Replaceable or common to find publicly. Mostly used by devs or those who do game editing or modding stuff.
- boot9.bin - Replaceable or common to find. Needed if you use programs like 3dsconv, ninfs, or Simple CIA converter.
- boot11.bin - This is replaceable or common to find.
- certs.db - Console specific (semi-)unique. The nand images should already contain this.
- decTitleKeys.bin - No longer relevant since the death of freeShop and other homebrew Nintendo CDN downloaders.
- encTitleKeys.bin - No longer relevant since the death of freeShop and other homebrew Nintendo CDN downloaders.
- essential.exefs - Keep a copy of this alongside the [preferably] two (2) minimum SysNAND backups.
- HWCAL0.DAt - Already in the essential.exefs. Can delete.
- HWCAL1.DAt - Already in the essential.exefs. Can delete this.
- import.db - This is not important by itself. It keeps track of what installed titles require updates. Can delete this.
- keyY.bin - ?? Only you know what this key is tied to.
- LocalFriendCodeSeed_B - Unless this is a different copy from another 3DS system in case you ever get banned online, the essential.exefs has this already.
- movable.sed - blah blah, essential.exefs
- otp.bin - ditto
- SecureInfo_A - ditto
- seeddb.bin - Easily replaceable from here.
- ticket.db - This is very important if you legitimately purchased your titles from eShop. For actual bought games, it's better to retain the legit tickets by dumping and reinstalling them with FBI. For pirated games, use faketik. Keeping this depends on your specific situation.
- title.db - This is paired with the import.db and is tied to a particular title folder. It's not reusable from a softbrick. Can delete.
- tmp_i.db / tmp_t.db - These are the temporary import and title equivalent of the TWL (DSi mode). Can delete these.
Last edited by TurdPooCharger,
the keyY.bin was something I think I saw in one your posts, unless I'm mistaken. it's 910-91F in hex of a NAND dump. I thought it might be important considering those bytes have been the same for several firmware installs.
Ah, just checking. The 3DS has many other KeyY slots ranging from 0x01 to 3F. I didn't want to assume the specific one you had was the one from the movable.sed.
Add the 32-char <ID0> subfolder string to that file's name so you'll instantly know what that KeyY is linked to.
For those who run into the scenario where you kept a copy of the Nintendo 3DS folder and let a young relative or friend borrow your 3DS, let's suppose that person system reformatted it and changed the encryption key. There's a chance the original KeyY could be recoverable as explained here.
Similar threads
- No one is chatting at the moment.
-
@
Psionic Roshambo:
It's not the movies or games downloads that I would worry about, like breaking into networks, downloading encrypted things, spying on network traffic. I have seen so many "Top Secret" seals on files when I was a kid -
@
Psionic Roshambo:
I was obsessed with finding UFOs, a surprising amount of US files where stashed on computers in other countries, China back in the early 90s omg sooo much
-
@
BigOnYa:
Yea that crazy, I've never tried hack into anything, I just pirate, and my ISP have send me 3-4 letters, so had to VPN it -
@
Psionic Roshambo:
Ship to ship communication software for the Navy although without access to the encrypting chips it was mostly useless
-
@
Psionic Roshambo:
I bet now a 4090 could probably crack it? Hmmm maybe not even back then I'm pretty sure they where using like 1024 bit encryption
-
-
-
-
-
-
-
-
-
-
@
Psionic Roshambo:
I remember one time I downloaded like a 500MB ISO file on 56K and that literally took like 2 days
-
-
-
-
-
-
-
-
-
-
