Homebrew Official [Download] Decrypt9 - Open Source Decryption Tools (WIP)

  • Thread starter Thread starter d0k3
  • Start date Start date
  • Views Views 935,203
  • Replies Replies 4,476
  • Likes Likes 71
Okay, that's not a valid NAND backup. No idea what it is. One last thing that you can try:
  • Dump a valid EmuNAND backup using EmuNAND9
  • Maker a backup of your corrupt one
  • Overwrite the first (exactly!) 512 (=0x200) bytes of your corrupt one with the first 512 bytes from the valid one
  • Now try to inject that (altered corrupt) one into the EmuNAND.
It will most likely not work, but if your NAND backup is not completely broken it may work. If that does not work, taht NAND backup is not an option. Don't inject it to SysNAND.
 
Okay, that's not a valid NAND backup. No idea what it is. One last thing that you can try:
  • Dump a valid EmuNAND backup using EmuNAND9
  • Maker a backup of your corrupt one
  • Overwrite the first (exactly!) 512 (=0x200) bytes of your corrupt one with the first 512 bytes from the valid one
  • Now try to inject that (altered corrupt) one into the EmuNAND.
It will most likely not work, but if your NAND backup is not completely broken it may work. If that does not work, taht NAND backup is not an option. Don't inject it to SysNAND.
So I am basically screwed?
 
Try it, then you can tell. If it's about your legitimate titles that you purchased, I suggest you call the Nintendo Hotline. But don't tell them how you lost them - think about some story.
What could they do though? I'll just link my NNID on sysNAND and see if I can redownload them on emuNAND.
 
What could they do though? I'll just link my NNID on sysNAND and see if I can redownload them on emuNAND.
Yup, try that and let me know if it worked. Nintendo migth have other ideas, too, but I'm pretty sure it will involve a system update.
 
Yup, try that and let me know if it worked. Nintendo migth have other ideas, too, but I'm pretty sure it will involve a system update.
Actually, right now I am trying that merge "corrupted" backup with a new one, I hope that works. :)
 
BTW, you should unify the nomenclature among EmuNAND9 and Decrypt9. One of them dumps to emuNAND.bin, and the other to EmuNAND.bin.

Tho i haven't actually tried whether the file detection is case sensitive
 
BTW, you should unify the nomenclature among EmuNAND9 and Decrypt9. One of them dumps to emuNAND.bin, and the other to EmuNAND.bin.

Tho i haven't actually tried whether the file detection is case sensitive
It is not. But you're right, this should be changed. Maybe I'll also add the file selection prompt to EmuNAND9.

BTW, there's a new release on GitHub. This mainly fixes the NAND restore feature that I broke on the last release (it simply wouldn't work in that one, without doing anything). Other than that, the readme now contains information about all the new functionality.
 
Last edited by d0k3,

Site & Scene News

Popular threads in this forum