Hacking Updated to a9lhv2, decrypt9 doesn't start anymore...

[Halvorsen]

Right, but under "v1" of A9LH, it did because you had to use AW's no-screen-init fork to use all functionality (screen brightness) in the Luma options menu. For the new version, AW released both a screen-init and a no-screen-init version. Is it logical to assume that the v2 no-screen-init version works the same in all cases where the v1 no-screen-init worked (EmuNAND9, Decrypt9WIP, etc.) or are the payloads assuming under v2 screen init has already been done?

Edit: oh wait a minute, the confusion is apparently about running these tools "standalone" as their own arm9loaderhax.bin, instead of being chainloaded through Luma. So to rephrase the question: is the no-screen-init version still the preferred way IF you ONLY chainload through Luma?

Not really. The only benefit of it is changing the backlight intensity rather than the set light in screeninit. It personally would introduce problems loading other arm9loaderhax.bins, so I don't recommend it. I like options :/

 

[SirByte]

Not really. The only benefit of it is changing the backlight intensity rather than the set light in screeninit. It personally would introduce problems loading other arm9loaderhax.bins, so I don't recommend it. I like options :/

Thanks, so screen-init it is, you can always side-grade (*cough*) to the no-screen-init version later.

 

[liomajor]

ppl don't get that it's currently no need to update a9lh if it's already installed.

It's ages ago that ' new = better ' was true, nowadays updates are overrated.

No one should fiddle with a9lh installation after its up and running,
or mix different stage releases without hardwaremod and backup.