I have no idea how to tell if i'm on a screen int or non screen int, I used the version from a few weeks backAre you on a screen-init or no-screen init fork of A9LH? Their really is no benefit to updating or reinstalling.
I have however flashed between forks and have done it just fine. Though I have decided to leave one of my o3DS systems on the no-screen init fork, just because I am to lazy to flashback a screen-init fork, and BootCTR9 already applies the screen-init patches for my payloads that need it. So meh.
Then you have a screen-init fork.I have no idea how to tell if i'm on a screen int or non screen int, I used the version from a few weeks back
To be honest, I don't really know, haven't gone over the changes that have been made. But basically from what I have read, it can now be installed directly from 2.1, you also have an easier time uninstalling A9LH if you are not on 11.0, and other stuff. You could always just go through the source code and figure out all the changes on your own and decide if it's worth updating. Just make sure you install it correctly.is there any thing to be gained by updating?
I followed Plailect's guide to install A9LH about 3 weeks ago. Should I go back to the Part 5 of the guide and follow Section II - Installing arm9loaderhax? I could not find any specific instructions to update A9LH.Just make sure you install it correctly.
It's a good thing I am lazy. Otherwise I might have tried updating.As of right now hold off, it seems like there are problems with d0k3's payloads with the new branch of a9lh.
The main advantage of upgrading is future compatibility.
Hold off on it for now.I followed Plailect's guide to install A9LH about 3 weeks ago. Should I go back to the Part 4 of the guide and follow Section II - Installing arm9loaderhax? I could not find any specific instructions to update A9LH.