Hacking Two 3DS NAND dumps, not labelled and mixed up. Way to differentiate them?

[Deleted member 333767]

Hello guise. I've got a bit of a conundrum at the moment.

Long story short, i have 2 3DS XL's, my silver/black one was on 4.5 (but was fully updated to play pokemanz) and my white one is currently on 4.4 and serves as my Gateway console.

I took a NAND dump prior to updating of the silver/black one when 2.0b1 was released (on 4.5) and i also have a dump of the white one (4.4) but silly me, i put them each in a new folder (to avoid name conflict) and didn't label them!!!

I want to get my black/silver one modified with NAND access but I need to differentiate the two dumps from one another otherwise the mod will be pointless. So is there a way to do this? Like MD5 checksum, or that NAND tool thing?

Any help would be much appreciated!!!

 

[bootmonster]

Write one to the 3ds, if it doesn't work write the other one?

 

[gamesquest1]

dump emunand from one of the console open it up in a hex editor, and check which one matches the start of the emu nand dump

 

[Deleted member 333767]

Write one to the 3ds, if it doesn't work write the other one?

I don't have NAND access on either consoles, unless you meant write them to the emuNAND partition of my 4.5 one. I suppose that would work.

dump emunand from one of the console open it up in a hex editor, and check which one matches the start of the emu nand dump

When you say 'the start' how much are we talking has to match? A line or two?

Thanks a lot to both of you

 

[XiTaU]

check the date created might help u unless u dont remember which one u dumped 1st.

 

[gamesquest1]

basically like the first 100 bytes should be the same if the nand dump is from the same console....but just checking like the first line or 2 would be enough

 

[GorTesK]

if both are still on 4.x, then what's the matter, you can just dump them again and this time label the folders ^^

 

[gamesquest1]

i think he means one is updated with a nand backup and one isnt.....and he wants to know which nand is which to get the other one downgraded.....truth is he could just get the port installed, backup his current nand then flash both and see which one works.....and seeing as there is 2 different nand sizes if they are different sizes you could get it installed check dump the current nand and check the file size to know which one is correct

 

[Deleted member 333767]

if both are still on 4.x, then what's the matter, you can just dump them again and this time label the folders ^^

One of them is fully updated but i want to get the NAND access mod on it so i have the option to revert back if something happens to my 4.4 console. I have a folder full of NAND dumps and i want to actually make sure i have the 4.5 backup of it before i shell out for a NAND mod

 

[GorTesK]

One of them is fully updated but i want to get the NAND access mod on it so i have the option to revert back if something happens to my 4.4 console. I have a folder full of NAND dumps and i want to actually make sure i have the 4.5 backup of it before i shell out for a NAND mod

oh silly me didn't read properly, sorry then

but can't you just make another NAND dump of the non-updated 3DS and compare it to your 2 other dumps? that is, ofc only you didn't change anything in it since the last dump, so the checksum will be the same as of the old one...
or you can test it by injecting it into your gateway 3DS emuNAND

 

[Deleted member 333767]

Hey gamesquest1 this is the comparison of my two NAND files, I'm so confused, are they from the same console? Where the two are highlighted is the first inconsistency between the two files.

 

[Deleted member 333767]

Sorry for double posting, but this is a screenshot of my 9.0 emuNAND i dumped 30 minutes ago.

Does this mean that they are all from the same 3DS? Starting to worry i didn't get a backup at all of my 4.5 3DS before i updated it.....

 

[gamesquest1]

they would seem to all be from the same 3ds if that's the first difference

 

[Deleted member 333767]

Yep, i thought so too.... Well there goes that idea of NAND access in that console then.... My 4.4 white one is still under nintendo warranty.

I might just try using emuNAND tool to write that unknown NAND to the white one, if it doesn't boot then I'm safe to assume it's the dump from my black one?

Thanks for taking the time to check out my screen dumps.