Thank you.for arm9 binaries that need the screen to start. This does not include things like decrypt9, bootanim9 and other. But bootloaders do.
yesThe only things I use with A9LH are Luma3DS, Decrypt9, and EmuNAND9. Could I reinstall A9LH with no screeninit and have everything work the same? (My sysNAND is still on 9.2.)
What installer should I use? The one in Plailect's guide is for 2.1. I assume that won't work on 9.2.
https://github.com/Plailect/Guide/wiki/Updating-arm9loaderhax do this first and then use the binary from https://github.com/AuroraWright/arm9loaderhax/releasesWhat installer should I use? The one in Plailect's guide is for 2.1. I assume that won't work on 9.2.
I used this last night, works perfectlyWhat installer should I use? The one in Plailect's guide is for 2.1. I assume that won't work on 9.2.
why would you use an emunandI used this last night, works perfectly
https://github.com/Plailect/Guide/wiki/Updating-arm9loaderhax
My sysnand is also on 9.2 although I have a 11.0 emunand, I'm guessing you're the same
Because some people like their systems to look stock//vanilla. Screen-init has a short flash before powering on. No-screen-init does not and looks more vanilla//stock like.Question: if you have 100% compatibility with screeninit, and not 100% compatibility with noscreeninit, then why use noscreeninit?
no flash at the beginning, and bootloaders are unnecessaryQuestion: if you have 100% compatibility with screeninit, and not 100% compatibility with noscreeninit, then why use noscreeninit?
Cause if for whatever reason my system fucks up, I don't lose £200, its just a reflash to get it all up and running again.why would you use an emunand
For you maybe. However, there are people who don't like Luma3DS' chainloader. It also fails to initialize GW's a9lh.bin (yes, yes, f*k GW) - But apart from that, Luma3DS' chainloader isn't for everybody. BootCTR9 gives me a lot more control over what I can do with my buttons, I can even add a damn splash to each option. Oh and then their is people who like CtrBootManager9, and it's GUI interface for selecting their payloads, as opposed to how Luma3DS' chainloader and BootCTR9 do it. Then there is people who like arm9select and arm9loaderhay. Again, it may be unnecessary for you, but not others.no flash at the beginning, and bootloaders are unnecessary
you can restore a sysnand bricked with arm9loaderhax with out hardmod emunand is uselessCause if for whatever reason my system fucks up, I don't lose £200, its just a reflash to get it all up and running again.
I have an emunand and still have 10gb left on my 128gb card so it's not that big a deal to me
And yet I'm still going to use it. There's no immediate need to get rid of it and I've got all the games I want so space isn't an issueyou can restore a sysnand bricked with arm9loaderhax with out hardmod emunand is useless
you can use gif while booting with screeninitQuestion: if you have 100% compatibility with screeninit, and not 100% compatibility with noscreeninit, then why use noscreeninit?
I personally love ctrbootmanager9's interface, it reminds me of grubFor you maybe. However, there are people who don't like Luma3DS' chainloader. It also fails to initialize GW's a9lh.bin (yes, yes, f*k GW) - But apart from that, Luma3DS' chainloader isn't for everybody. BootCTR9 gives me a lot more control over what I can do with my buttons, I can even add a damn splash to each option. Oh and then their is people who like CtrBootManager9, and it's GUI interface for selecting their payloads, as opposed to how Luma3DS' chainloader and BootCTR9 do it. Then there is people who like arm9select and arm9loaderhay. Again, it may be unnecessary for you, but not others.
I dont telling you to get rid of, just that emunand is no longer usefullAnd yet I'm still going to use it. There's no immediate need to get rid of it and I've got all the games I want so space isn't an issue