Homebrew Trouble with A9lH. Emunand backup is Toshiba, while the Sysnand is Samsung

[Derpncheez]

Is this normal or did I do something wrong? I've been following Plailect's guide and am working on step 4, but the Emunand backup is a Toshiba type at 943MB, while the Sysnand backup is a Samsung at 954MB. My system nand is Samsung, so is this not right? I don't want to risk bricking my console because a hardmod is out of the question at this point.

 

[KaduPSE]

I've never seen that actually causing a problem, but I could be missing something here

 

[pbanj]

Wouldn't using rednand for the emunand make it smaller than the actual nand? I know on the n3ds it brings the 1.8 one down to 1.2

 

[The Real Jdbye]

Wouldn't using rednand for the emunand make it smaller than the actual nand? I know on the n3ds it brings the 1.8 one down to 1.2

Yeah, this is probably the reason. From what I heard redNAND basically makes the partition only take up the space the 3DS is actually using, which presumably would be the size of the smallest NAND.

 

[pbanj]

Yeah, this is probably the reason. From what I heard redNAND basically makes the partition only take up the space the 3DS is actually using, which presumably would be the size of the smallest NAND.

Ya that's what I got from all I have read on the subject also.

 

[Derpncheez]

I've never seem that actually causing a problem, but I could be missing something here

I guess it doesn't matter because Emunand is not the actual Sysnand? I just want to be sure, honestly.

Wouldn't using rednand for the emunand make it smaller than the actual nand? I know on the n3ds it brings the 1.8 one down to 1.2

I'm not sure, but the Emunand is smaller and fits the filesize of a Toshiba type Nand. Both are the right sizes (According to the guide), but shouldn't they be the same type of brand name Nand?

 

[pbanj]

I guess it doesn't matter because Emunand is not the actual Sysnand? I just want to be sure, honestly.



I'm not sure, but the Emunand is smaller and fits the filesize of a Toshiba type Nand. Both are the right sizes (According to the guide), but shouldn't they be the same type of brand name Nand?

You followed the guide from the first part? If yes you are using rednand not emunand, while tthey are pretty much the same shit rednand uses the min amount of space. That's why you would have a size miss match .

 

[Derpncheez]

You followed the guide from the first part? If yes you are using rednand not emunand, while tthey are pretty much the same shit rednand uses the min amount of space. That's why you would have a size miss match .

Yeah, I started from the first part using Oothax as my entrypoint to HBL. So I'm guessing everything is good, just as long as the filesizes for the Nands are the right ones?

 

[dubbz82]

Yeah, this is probably the reason. From what I heard redNAND basically makes the partition only take up the space the 3DS is actually using, which presumably would be the size of the smallest NAND.

That's exactly it. The guide was switched to use rednand specifically because it can generate smaller files in some cases, thus speeding up all the reading/dumping of sysnand and emunand. It literally slices an hour or more off the time the process takes with the systems that have the larger nand.