Correct. You won't be able to boot to sysnand without the updated sysnand mode checked thoughso if i have nothing checked on the options, it still protects the sysnand if i'm using arm9loaderhax.bin right?
Correct. You won't be able to boot to sysnand without the updated sysnand mode checked thoughso if i have nothing checked on the options, it still protects the sysnand if i'm using arm9loaderhax.bin right?
i don't see any updated sysnand mode in 5.0. also i do have nothing checked and it boots to sysnand.Correct. You won't be able to boot to sysnand without the updated sysnand mode checked though
The keys are not used for this cfw they only need to be on the sd card if you want to used decrypt9Oh, I see. When I updated to A9LH on Plailect's guide there were only 3 slot0ckey.bin files and now there are 4. Maybe that's why I get that. I'll try adding the 4th one and seeing if it works correctly.
Oh, I see. When I updated to A9LH on Plailect's guide there were only 3 slot0ckey.bin files and now there are 4. Maybe that's why I get that. I'll try adding the 4th one and seeing if it works correctly.
Ok, so now that I added the 4th slot0xkey.bin file if I hold L+R it now says initialization: success! and press A to continue, however if I press start it boots up immediately to Decrypt9WIP menu.

Humanity will continue to find ways to be lazier by every passing day!Are you too lazy to open your web browser and use a FTP app or something?
O.o she must have changed the config again lol. I guess I should update lol. To the commitly site o/i don't see any updated sysnand mode in 5.0. also i do have nothing checked and it boots to sysnand.
The keys are not used for this cfw they only need to be on the sd card if you want to used decrypt9
AW already released 5.0 officially. the latest commit and the latest release are the same.O.o she must have changed the config again lol. I guess I should update lol. To the commitly site o/
i don't see any updated sysnand mode in 5.0. also i do have nothing checked and it boots to sysnand.
She changed the name of the setting to "Use SysNAND FIRM as default"O.o she must have changed the config again lol. I guess I should update lol. To the commitly site o/
Basically I have a server that checks for updates every 10 minutes, the source code is available for anyone who wants it.I don't think its about lazyness, but automation.
I actually think an "autoupdater" would be quiet easy, since @astronautlevel got an compiling automat, or am I wrong?
Humanity will continue to find ways to be lazier by every passing day!![]()
so this one is to protect the sysnand?She changed the name of the setting to "Use SysNAND FIRM as default"
It does exactly the same as it did before when it was named "Updated SysNAND mode"
Basically I have a server that checks for updates every 10 minutes, the source code is available for anyone who wants it.
huh, weird on the rename then...It does exactly the same as it did before when it was named "Updated SysNAND mode"
Shouldn't be too hard, but it would have to be a homebrew app or CIA because we don't have network function on arm9 yet.I'm not able to programm anything myself yet - was just thinking about this solution:
Grab the a9lh.bin from your Server and place it in the root of the SD
It actually makes more sense with this name, so it's not so weird. The name now reflects what it actually does.huh, weird on the rename then...
I was thinking someone could make an app that just checks the version of your arm9loaderhax.bin and if applicable, updates it. Choose between stable or nightly.Shouldn't be too hard, but it would have to be a homebrew app or CIA because we don't have network function on arm9 yet.
The problem is the need to change paths so it would have to support that alsoI don't think its about lazyness, but automation.
I actually think an "autoupdater" would be quiet easy, since @astronautlevel got an compiling automat, or am I wrong?
