Hacking Different size Sys and Emunand from same console?

  • Thread starter Thread starter Cosmic_Link
  • Start date Start date
  • Views Views 2,010
  • Replies Replies 13

Cosmic_Link

Well-Known Member
Member
Joined
Jun 9, 2010
Messages
113
Reaction score
100
Trophies
0
Age
37
XP
1,706
Country
United Kingdom
Hi all,

Was just following Plailect's guide for installing A9LH on a N3DSXL.

I have just backed up the Sysnand and Emunand, as stated in step 4, and it both Nands are different sizes. Have made a second backup of each, with the same result.

Both sizes match up to the sizes stated on this page for N3DS: https://github.com/Plailect/Guide/wiki/NAND-Size

Here is a screen cap of the 2 nands.

14j3inr.jpg


Sysnand boots fine, emunand boots fine. Sysnand is 9.2, emunand is 11.0.

Is this normal? :S I don't expect it is. If somebody could advise before I continue, that would be great.

Thanks in advance for any help.
 
So it's fine for me to continue then?

I've not used "Rednand" before, only "emunand" this and it was a while ago when I installed A9LH on my own console and I never used this guide to install it, so I just wanted to be sure since this console doesn't have a hardmod.

Thanks for your help. :D
 
Thanks. That was what I expected.

Will try to just make a new emunand instead with matching sizes before I continue. ^_^
 
It is a perfectly fine backup, I wouldn't waste the space on having matching sizes. The extra space is just zeroes anyway.

In a pinch it can be flashed to sysNAND with no problems even though it's smaller.
 
  • Like
Reactions: Cosmic_Link
Ok cool. Thanks for your help. I'll carry on as I was then, since I have followed all other steps to a tee. ^_^
 
It is a perfectly fine backup, I wouldn't waste the space on having matching sizes. The extra space is just zeroes anyway.

In a pinch it can be flashed to sysNAND with no problems even though it's smaller.
is there any evidence that this is actually safe to do? Last time i checked, brick protection doesnt protect from something that isnt the correct size...
 
is there any evidence that this is actually safe to do? Last time i checked, brick protection doesnt protect from something that isnt the correct size...

Knowledge of how it works and since that is probably not enough for you I did at one time see dok3 say it and I'm sure you would trust him.
 
This happened to me most of the time, Emunand and Sysnand backups are not the same size(But they are valid since I check it on Plailects guide if it's the right nand dump) and I don't have problems at all.
 
The thing is that the way RedNAND works it will always have the smallest possible NAND-size for both N3DS and O3DS.
Because there is the possibility to get 2 different NAND-sizes on each console, you will appear to get different Sys and RedNAND sizes if your normal SysNAND uses the bigger value.
 
Just a quick update about this. I continued with the process and all is working fine with no issues.

Thanks for everybody's responses. ^_^
 

Site & Scene News

Popular threads in this forum