Hacking emuNAND Brick when undoing Home Menu patch (Didn't backup)

[Deleted member 310901]

I was reinstalling the stock AGB, TWL, and home menu CIAs on a friend's emuNAND with FBI because AuReiNAND already patches them but it ended up with a bricked home menu. Didn't think to make a backup so it's pretty much dead. (I know, save the "you should've" comments.) So uh, long story short, how do I transfer the NNID and other NAND-tied stuff into a fresh emuNAND copy? I do remember that I formatted emuNAND exactly 5 times after the sysNAND backup so I can still backup save data from his games. Thanks.

Just want to say as a reference that I have my own 3DS with A9LH and I'm planning on installing it on his as well.

 

[frosty5689]

You can't transfer the NNID over, someone can correct me.

I think if you had another SD card handy, you can setup fresh EmuNAND on that one (using the same 3DS). Boot into sysupdater. Swap the sdcards and try to upgrade to the same firmware as the bricked EmuNAND (thereby fixing the mismatch system CIAs).

Disclaimer: I'm not sure if you can swap sdcard when sysupdater is open and also not sure if there is a chance of accidentally upgrading the SysNAND (theoretically since you booted to EmuNAND through CFW, it should be redirecting all read/write to EmuNAND)

IMO, it would be safer to just start from scratch.

 

[infinete]

If I am right, if you dump your CTRNAND.bin from the old nand and inject it into a working nand, you should keep everything..... I think.

 

[Supster131]

If I am right, if you dump your CTRNAND.bin from the old nand and inject it into a working nand, you should keep everything..... I think.

Er kinda.
This exact same thing happened to me a few weeks back (thanks to @daxtsu for helping me fix the problem!)

I did have some NAND backups, but they were old. I suggest you backup your current bricked emuNAND backup (as separate partitions though, not in its entirety). You also want to backup ticket.db and movable.sed (you can back all this up with Decrypt9WIP). Once you have all that backed up, make a new emuNAND. Once you're new emuNAND is all setup, go back into Decrypt9. You want to inject every partition into your new emuNAND with the exception of CTRNAND (since this is technically what's bricked), don't forget to inject ticket.db and movable.sed as well. Once you're done, your emuNAND should look like how it was before the brick (with the exception of the firmware, it'll most likely be on 9.2, feel free to update it).

This should work, this will however, delete your friends list and data within system titles (such as Miis and data in the Activity Log). I know there's a way to back that up and inject it into your new emuNAND with GodMode9, I don't remember where they are stored in CTRNAND.

 

[Deleted member 310901]

So, what partition is the NNID stored exactly?

 

[Supster131]

So, what partition is the NNID stored exactly?

I'm not sure, but you should be able to login just fine, since it's the same system.

 

[Deleted member 310901]

Oh, so I may misunderstood how NNID works. I thought it was a serial specific bin file stored in a NAND and cant be use on other NANDs if it wasn't unlinked manually through a system format.

Also, do I backup the FIRM partitions as well? I don't want to accidentally screw up something...whatever I can screw up. Just taking extra precautions.

 

[Halvorsen]

Juat take the emunand's nnidsave.bin using Decrypt9, fill all its data with FF blocks within a hex editor, then reinject it. It'll essentially unlink your NNID and you can sign in on your new nand.
If you're signed in to two different systems (nands count) anything that uses NNID services won't load, almost like a ban. It happened to me. Luckily, the same method can unban you.

 

[Supster131]

Oh, so I may misunderstood how NNID works. I thought it was a serial specific bin file stored in a NAND and cant be use on other NANDs if it wasn't unlinked manually through a system format.

Also, do I backup the FIRM partitions as well? I don't want to accidentally screw up something...whatever I can screw up. Just taking extra precautions.

It shouldn't really matter as this is an emuNAND and not a sysNAND on A9LH.