Hacking System 0x0 - 0x2FF

[democracy]

Why are you worried? With a9lh+aureinand, you can update sysnand all you want.

I suppose but I think the current implementation of firm block is a bit ambiguous, I mean what if it fails or I do something wrong on my end with implementing firm block. I still don't understand the warning about patched firmware with regards to using menuhax. It just seems to me that the firm block is ambiguous if it's in place or not. I also dug into firm.c in AuReiNand source and it references 9.2 fw, well I have fw 9.0 as system, so I'm not sure these safeguards are even in place for my system or not? If I had to ever upgrade sysnand anyways I would sooner dump sysnand ctrnad and upload to emunand, perform system update on emunand then reverse to be completely safe anyways.

 

[democracy]

When I setup my kids O3DS the eshop did not work in emunand. The current guides said to make a new emunand, re-link NNID and restore the old emunand.

Instead I updated sysnand to 10.6 linked the NNID and then restored the 9.2 sysnand. It was much faster.

The point is you do not have to worry about updating sysnand. As long as you have a 9.2 a9lh NAND backup you are fine. You can check the sysnand every couple of weeks if you want and if the kid updated it just restore it.

A9lh makes these systems pretty much kid proof. There is a better chance of them destroying the emunand with a cia installer than anything else.

I can't update sysnand because while I have two emumands on two separate mem cards each with different titles installed to both emumands both emunands stem from the same emunand. So if I do as you suggest, I got the gift bug on one of the memory cards and have to unwrap gifts on boot and also risk all titles being auto deleted if I visit data management.

 

[Just Passing By]

I suppose bit I think the current implementation of firm block is a bit ambiguous, I mean what if it fails or I do something wrong on my end with implementing firm block. I still don't understand the warning about patched firmware with regards to using menuhax. It just seems toe that the form block is ambiguous if it's in place or not. I also dug into firm.c in AuReiNand source and it references 9.2 fw, well I have fw 9.0 as system, so I'm not sure these safeguards are even in place for my system or not? If I had to ever upgrade sysnand anyways I would sooner dump sysnand ctrnad and upload to emunand, perform system update on emunand then reverse to be completely safe anyways.

You're right in saying that you don't know if firm block works properly, but no one has reported anything hinting at it failing. If you're so worried, stay on emunand and keep sysnand 9.2. That's what I do and it works fine. Why stress?

 

[YourHero]

Simply remove any wireless connections from the 3ds sysnand and run the recovery for a second then power off. Running recovery deletes any update data stored and not having a wifi connection prevents updates.

Problem solved.

 

[democracy]

That's what I'll do. For now I've compiled AuReiNand to make it emunand only but I also keep a untouched copy on sd in case I need those feature.

Maybe someone will figure out a way to brick fw updating & fw download for arm9 user who plan on sticking with emunand.

 

[roflpwnt]

What about cart updates though @YourHero

 

[Bu2d85]

I can't update sysnand because while I have two emumands on two separate mem cards each with different titles installed to both emumands both emunands stem from the same emunand. So if I do as you suggest, I got the gift bug on one of the memory cards and have to unwrap gifts on boot and also risk all titles being auto deleted if I visit data management.

Do you mean that they both stem from the same "sysnand"? Like you made an emunand and then cloned it to a different sd card?

If your emunands are on different sd cards and they are not linked to your sysnand there should be no issues. The gift wrap bug is caused by having linked nands. The same as the data management bug.

To me it sounds like one of your emunands is still linked to your sysnand. If there is nothing important on your sysnand use tinyformat to unlink it.

 

[YourHero]

What about cart updates though @YourHero

Why would you be using carts on sysnand when you have emunand? And lets be real..... who is buying physical copies? We aren't all using cfw for the sweet sweet custom themes. He has no reason to not update CFW currently. Everything works fine and can be run on the latest versions.

 

[democracy]

Why would you be using carts on sysnand when you have emunand? And lets be real..... who is buying physical copies? We aren't all using cfw for the sweet sweet custom themes. He has no reason to not update CFW currently. Everything works fine and can be run on the latest versions.

The idea is to make it kids proof, you would be surprised what damage kids can do and some people still use carts.

 

[Bu2d85]

That's what I'll do. For now I've compiled AuReiNand to make it emunand only but I also keep a untouched copy on sd in case I need those feature.

Maybe someone will figure out a way to brick fw updating & fw download for arm9 user who plan on sticking with emunand.

Why not just brick the sysnand completely? I'm being serious. If you really do not want to use it then there is no need to have it. As long as firm0 and firm1 are untouched you can brick the rest. If you ever needed it you could restore it with the a9lh version of decrypt 9.

 

[democracy]

Why not just brick the sysnand completely? I'm being serious. If you really do not want to use it then there is no need to have it. As long as firm0 and firm1 are untouched you can brick the rest. If you ever needed it you could restore it with the a9lh version of decrypt 9.

Never thought of that, lol. But that seems to be a much worse scenario to be in than than the one that I am in now; running a version of aureinand that does not allow sysnand booting.

 

[Just Passing By]

Never thought of that, lol. But that seems to be a much worse scenario to be in than than the one that I am in now; running a version of aureinand that does not allow sysnand booting.

It's not worth the time to brick sysnand and I think you're being a little paranoid (not trying to be mean). You're about 99%+ fine. There's no way you'd update sysnand to get rid of a9lh unless Nintendo does some voodoo with the updates. That's the only reason you'd lose it at this time from an update. And you sound fine now that you can't even boot sysnand from aureinand.

 

[democracy]

It's not worth the time to brick sysnand and I think you're being a little paranoid (not trying to be mean). You're about 99%+ fine. There's no way you'd update sysnand to get rid of a9lh unless Nintendo does some voodoo with the updates. That's the only reason you'd lose it at this time from an update. And you sound fine now that you can't even boot sysnand from aureinand.

I agree with you, I am not purposely going to brick sysnand.