Unless you downgrade your sysnand before removing a9lh.You'll have no way of getting to a9lh without hardmod downgrading afterwards.
Unless you downgrade your sysnand before removing a9lh.You'll have no way of getting to a9lh without hardmod downgrading afterwards.
Yes but sending it for repair means they'll update you to 11.0Unless you downgrade your sysnand before removing a9lh.
NintendoUnless you downgrade your sysnand before removing a9lh.
Yes but sending it for repair means they'll update you to 11.0![]()
Oh yeah, you're right. I usually don't get my console repaired my Nintendo though.Nintendousuallyupdates the system, and sometimes they just send a refurb that's similar and already updated.
I wouldn't know. I don't have a hardmod (which is why ShadowNAND has a safety net and the installer has no uninstall button), so I never triedThanks to all of you, I'm fully aware of the consequences and hope I'll never have to remove A9LH. And AFAIK SafeA9LHInstaller won't let you uninstall A9LH if you're on 11.0 or greater.
That's correct, you'll need a clean non-A9LH sysNAND backup, and flash it back with Decrypt9, without keeping A9LH. Or downgrade your current SysNAND, and then uninstall.Thanks to all of you, I'm fully aware of the consequences and hope I'll never have to remove A9LH. And AFAIK SafeA9LHInstaller won't let you uninstall A9LH if you're on 11.0 or greater.
You should test this, and see what they do. Hopefully they don't give you an ass-whooping of Stability.Wait, has anyone tried asking Nintendo to not update their console? xD
Latest two commits have no-screeninit unless you press DPAD_LEFT (for payloads that don't init the screen).Thanks a lot again, installed ShadowNAND on both of my 3DSes in the meantime.Can't wait for the full CFW and a non-screeninit version (if that's possible at all).
xD And I wonder if they'll refuse or brick an a9lh console?You should test this, and see what they do. Hopefully they don't give you an ass-whooping of Stability.
I still have no idea of what your intention with ShadowNAND is. Is it a port of SaltFW to function entirely without depending on the SD? Because in that case it's definitely not complete.I've said, time and time again, ShadowNAND is not complete yet. This is just A9LH on steroids.
Maybe I should pull a @Wolfvak and make it private like he did because people don't know how to read.
I still have no idea of what your intention with ShadowNAND is. Is it a port of SaltFW to function entirely without depending on the SD? Because in that case it's definitely not complete.
On the other hand, if your project was to bring altstage2 and bigger stage2's, then it's pretty much finished (there's one thing I'd add, which is CTRNAND payload loading, or maybe a selector menu to choose your payload on bootup)
It's not really private, it's more about the fact that it was incomplete. I put up the source only because I thought it'd be cool for people to actually see some progress on it, but users insisted on installing and as such I took it down. It's still actively being worked on, and N3DS is fully supported, but at least one user (@Ryccardo) has been experiencing a fatal issue, so until it's sorted out (and properly tested) I'll put it up again, this time with a release. Maybe I'll even suggest using it with ShadowNAND, because the "official" A9LH doesn't support altstage2 or stage2s bigger than 0x20 sectors (0x4000 bytes) in size.Honestly, this is why I haven't installed this. It provides some direct benefits but at the same time, it's more an alternative A9LH implementation and not a CFW.
Side note: You made KGB private? Why? It was cool shit. Noobs will be noobs, but it's their own fault if they don't read the instructions/documentation. Not your fault if they brick.
All current CFWs rely on an SD card being present. Placing a CFW in CTRNAND is quite useless, since you can just put it in your SD card and it'll be the same.I'm not sure if this is essentially what ShadowNAND/KBG is already (forgive me if it is), but what about a stage2 cfw which just boots a arm9 payload which you can just copy to the nand using godmode9. This will allow more variety and choice, so people can choose their cfw.
It's not really private, it's more about the fact that it was incomplete. I put up the source only because I thought it'd be cool for people to actually see some progress on it, but users insisted on installing and as such I took it down. It's still actively being worked on, and N3DS is fully supported, but at least one user (@Ryccardo) has been experiencing a fatal issue, so until it's sorted out (and properly tested) I'll put it up again, this time with a release. Maybe I'll even suggest using it with ShadowNAND, because the "official" A9LH doesn't support altstage2 or stage2s bigger than 0x20 sectors (0x4000 bytes) in size.
My intention is to provide a small setup which users can rely on in case of getting shrekt by a dead SD or a bad stage2 update or something. I'd also like to wait until a new A9LH version comes out, in case it brings more changes (and possibly breakage).
If you have any unsigned titles installed to NAND, removing A9LH can permabrick your 3DS (you may still be able to enter safe mode but that's pretty much it) as they will fail signature checks.That's correct, you'll need a clean non-A9LH sysNAND backup, and flash it back with Decrypt9, without keeping A9LH. Or downgrade your current SysNAND, and then uninstall.
Ah, okay, I see. While I love to watch and use what amazing things others create, I am not very experienced in this stuff, so I don't know my factsAll current CFWs rely on an SD card being present. Placing a CFW in CTRNNAD is quite useless, since you can just put it in your SD card and it'll be the same.