Hacking N3DS 10.3 downgraded to 9.2, EMUNAND9 dumping sysnand to NAND.bin failed.

[Ichigo1000]

The option says "Dump sysnand to file" instead of NAND.bin. In most tutorials, I see the option is "Dump sysnand to NAND.bin".

Upon trying to dump my sysnand, "Could not create nand.bin" and "Dumping sysnand failed" showed up.

If that info is necessary, at the bottom of Emunand9, it also says:

-EmuNAND: SD ready

-SD storage: unknown filesystem

It says SD card is ready, but it's an unknown file system. Is that normal?

I tried the following already:

• Reformat my microsd card (32GB) to FAT32 (Multiple times)
  
  
• Tried different allocation sizes
  
  
• used the gui format tool
  
  
• Updated to the latest homebrew starter kit and EMUNAND9 files

I also used this tutorial to set up EMUNAND9 if this is necessary. I didn't put anything else besides EMUNAND9 and HBL files though.

 

[Ronhero]

Try GW'S launcher

 

[DocKlokMan]

Do this:
1. Backup your files because we're about to format the SD card.
2. Run emuNAND9 from sysNAND
3. Choose SD Format Options
4. Format SD
5. without emuNAND
6. Confirm the format.

This will format your SD card into a filesystem emuNAND9 understands and will allow you to dump your NAND (older version only allowed NAND.bin, new versions let you choose a variety of names).

 

[Ichigo1000]

Do this:
1. Backup your files because we're about to format the SD card.
2. Run emuNAND9 from sysNAND
3. Choose SD Format Options
4. Format SD
5. without emuNAND
6. Confirm the format.

This will format your SD card into a filesystem emuNAND9 understands and will allow you to dump your NAND (older version only allowed NAND.bin, new versions let you choose a variety of names).

Wow why didn't I think of that... THANKS! It worked! Now it says SD is not ready for emunand though.

 

[DocKlokMan]

That just means there's no emuNAND partition. Once you have your NAND copied to your computer safely you can run the complete setup and copy your SD files back on again.

 

[Ichigo1000]

That just means there's no emuNAND partition. Once you have your NAND copied to your computer safely you can run the complete setup and copy your SD files back on again.

I get a black screen trying to load rxtools via homebrew launcher, and sometime I only get the top screen showing. It seems if i press random buttons the home screen restarts. and the settings say "RX-S" along with firmware. But when I exit and go to the settings again, it disappears. Most of the time it doesnt even work and get stuck on a black screen

If this info is necessary, I do not use menuhax, I used ninjhax.

 

[DocKlokMan]

I'm sorry, I'm a n3DS user at the time rxtools didn't work. I've since upgraded to AuReiNAND which works for both o3DS and n3DS and supports arm9loaderhax. As for the RX-S, I believe that means you're in emuNAND. Exiting the Settings screen reboots the 3DS, which puts you out of emuNAND and back into sysNAND, this is why the RX-S string is gone when you look the second time. Also, set up menuHax, it's a lot easier and I find it works better than ninjhax.

 

[tjhooker73]

Set up menuhax with ctrbootloader and rxtools. Then you should be able to hold R while booting rxtools to get into the rxtools menu

 

[Ichigo1000]

Set up menuhax with ctrbootloader and rxtools. Then you should be able to hold R while booting rxtools to get into the rxtools menu

wouldn't i still be getting the same problem if i cant boot correctly into rxtools via hombrew the first place?

 

[Ichigo1000]

I'm sorry, I'm a n3DS user at the time rxtools didn't work. I've since upgraded to AuReiNAND which works for both o3DS and n3DS and supports arm9loaderhax. As for the RX-S, I believe that means you're in emuNAND. Exiting the Settings screen reboots the 3DS, which puts you out of emuNAND and back into sysNAND, this is why the RX-S string is gone when you look the second time. Also, set up menuHax, it's a lot easier and I find it works better than ninjhax.

Is it risky to do, and how hard is it to do it? Is it possible for anyone at 9.2 firmware? I heard it fixes the 3d glitch, which I really want.

 

[DocKlokMan]

Is it risky to do, and how hard is it to do it? Is it possible for anyone at 9.2 firmware? I heard it fixes the 3d glitch, which I really want.

Are you asking about arm9loaderhax? It's harder to do on a n3DS than an old one. Wait another two-three days, new break throughs just happened and the n3DS firmware creation script is getting an update that has more safety checks built in. More guides are showing up so I'd say hold off for a bit. Once it's done though it's totally worth it.

 

[andrew weeks]

I sold my n3DS in order to get a XL , i tried to inject my old nand.bin and use Reinand, but only black screen apeears after the Reinand logo. Is it the same problem?

 

[Ichigo1000]

Are you asking about arm9loaderhax? It's harder to do on a n3DS than an old one. Wait another two-three days, new break throughs just happened and the n3DS firmware creation script is getting an update that has more safety checks built in. More guides are showing up so I'd say hold off for a bit. Once it's done though it's totally worth it.

Yes, can anyone with 9.2 firmware do this? I heard you need to downgrade to 2.x to do this.

 

[DocKlokMan]

Yes, can anyone with 9.2 firmware do this? I heard you need to downgrade to 2.x to do this.

If you have a 9.2 sysNAND and any emuNAND setup, you can do it. With a n3DS this is an extreme summary of steps, not to be followed as a guide:

1. Backup your SD card
2. Load Decrypt9 from sysNAND
3. Backup sysNAND and emuNAND to BIN files, also dump your two XOR keys (~7GB of data)
4. Use Tiny Formatter to format emuNAND (should be newest version 10.6 if not already) and set it up new
5. Use Decrypt9 from sysNAND to inject FBI into Health and Safety
6. Backup your emuNAND again as emuNAND_formatted.bin
7. Boot emuNAND, make sure Wi-Fi is on, use FBI to install sysUpdater.cia and then run sysUpdater to downgrade to 2.1
8. Load Decrypt9 from sysNAND and backup emuNAND AGAIN as emuNAND_bricked.bin
9. Install Python on your PC, run python script to patch emuNAND_bricked.bin to work on the n3DS.
10. Use Decrypt9 from sysNAND to restore the patched emuNAND_bricked.bin
11. Delete the extData folders from the SD card located inside Nintendo 3DS folder (all of them).
12. Boot n3DS and hope you didn't brick it.
13. Use exploit to dump OTP.bin and copy it to your PC
14. Use another exploit to load Decrypt9 and then restore your NAND and emuNAND backup from step 3.
15. Once done, erase all files on memory card and restore them with the backup from step 1.

That's a really condensed form of how to get the OTP key and does not include how to use that OTP key to get arm9loaderhax installed. This is just to show you what the skeleton of steps looks like. Took me about 2.5 hours.

 

[Ichigo1000]

If you have a 9.2 sysNAND and any emuNAND setup, you can do it. With a n3DS this is an extreme summary of steps, not to be followed as a guide:

1. Backup your SD card
2. Load Decrypt9 from sysNAND
3. Backup sysNAND and emuNAND to BIN files, also dump your two XOR keys (~7GB of data)
4. Use Tiny Formatter to format emuNAND (should be newest version 10.6 if not already) and set it up new
5. Use Decrypt9 from sysNAND to inject FBI into Health and Safety
6. Backup your emuNAND again as emuNAND_formatted.bin
7. Boot emuNAND, make sure Wi-Fi is on, use FBI to install sysUpdater.cia and then run sysUpdater to downgrade to 2.1
8. Load Decrypt9 from sysNAND and backup emuNAND AGAIN as emuNAND_bricked.bin
9. Install Python on your PC, run python script to patch emuNAND_bricked.bin to work on the n3DS.
10. Use Decrypt9 from sysNAND to restore the patched emuNAND_bricked.bin
11. Delete the extData folders from the SD card located inside Nintendo 3DS folder (all of them).
12. Boot n3DS and hope you didn't brick it.
13. Use exploit to dump OTP.bin and copy it to your PC
14. Use another exploit to load Decrypt9 and then restore your NAND and emuNAND backup from step 3.
15. Once done, erase all files on memory card and restore them with the backup from step 1.

That's a really condensed form of how to get the OTP key and does not include how to use that OTP key to get arm9loaderhax installed. This is just to show you what the skeleton of steps looks like. Took me about 2.5 hours.

Is it possible to do without losing game data etc? I'm thinking of doing this in the future, as it becomes more safe and developed.

 

[Gcentrex]

Is it possible to do without losing game data etc? I'm thinking of doing this in the future, as it becomes more safe and developed.

If you follow the tutorial for dumping OTP then you will backup your games & saves

Once you have dumped OTP and restore your sysNAND backup and SD card backup you will have everything as if you didn't do anything

 

[Ichigo1000]

If you have a 9.2 sysNAND and any emuNAND setup, you can do it. With a n3DS this is an extreme summary of steps, not to be followed as a guide:

1. Backup your SD card
2. Load Decrypt9 from sysNAND
3. Backup sysNAND and emuNAND to BIN files, also dump your two XOR keys (~7GB of data)
4. Use Tiny Formatter to format emuNAND (should be newest version 10.6 if not already) and set it up new
5. Use Decrypt9 from sysNAND to inject FBI into Health and Safety
6. Backup your emuNAND again as emuNAND_formatted.bin
7. Boot emuNAND, make sure Wi-Fi is on, use FBI to install sysUpdater.cia and then run sysUpdater to downgrade to 2.1
8. Load Decrypt9 from sysNAND and backup emuNAND AGAIN as emuNAND_bricked.bin
9. Install Python on your PC, run python script to patch emuNAND_bricked.bin to work on the n3DS.
10. Use Decrypt9 from sysNAND to restore the patched emuNAND_bricked.bin
11. Delete the extData folders from the SD card located inside Nintendo 3DS folder (all of them).
12. Boot n3DS and hope you didn't brick it.
13. Use exploit to dump OTP.bin and copy it to your PC
14. Use another exploit to load Decrypt9 and then restore your NAND and emuNAND backup from step 3.
15. Once done, erase all files on memory card and restore them with the backup from step 1.

That's a really condensed form of how to get the OTP key and does not include how to use that OTP key to get arm9loaderhax installed. This is just to show you what the skeleton of steps looks like. Took me about 2.5 hours.

I think rxtools is fixed, but i sometimes have to try multiple times for it to work. When trying to install fbi cia, it says install failed. What's wrong?

I think it might be because i did not rebuild my database, which I'm going to try now. But how do I get back my games later?

 

[DocKlokMan]

I think rxtools is fixed, but i sometimes have to try multiple times for it to work. When trying to install fbi cia, it says install failed. What's wrong?

Dude, I don't know, I've never used rxTools. If you're trying to install CIA files onto your emuNAND by anything other than an already installed CIA, you can't. Take a peek here on how to use Decrypt9 / rxTools in sysNAND to dump, alter, and inject your Heath & Safety app with FBI into emuNAND so that you can install CIA files.

 

[Ichigo1000]

Dude, I don't know, I've never used rxTools. If you're trying to install CIA files onto your emuNAND by anything other than an already installed CIA, you can't. Take a peek here on how to use Decrypt9 / rxTools in sysNAND to dump, alter, and inject your Heath & Safety app with FBI into emuNAND so that you can install CIA files.

Tried to install it on sysnand SD destination in the FBI homebrew app as shown in the tutorial. Also tried to rebuild database, which also did not work.