The normal one's the one you get from the data_input_v3.zip.I don't know what the normal one is but if you want to boot Luma you'll use Luma's bin and if you want to boot CTR9 you'll use CTR9's bin.
I mean if you want to open your front door, you don't use you car keys...
Yeah, I know that if you don't follow the guide yet the letter you'll probably brick, but Luma3DS's a9lh.bin is different than the data_input_v3.zip's a9lh.bin.Oh my...
You should follow the guide to the letter and not trying to outsmart it because you obviously don't understand what you are doing.
In data_input_v3.zip you'll find the necessary files to install the payload for A9LH with SafeA9LHinstaller.
This will then allow the console to load a file named arm9loaderhax.bin on boot. This bin can be a CFW like Luma3DS or a bootlaoder like CTR9 or a software like Hourglass9.
When installing A9LH you MUST NOT alter or modify the file in data_input_v3.zip, follow the guide to the letter or you might brick.
But from where can I get hartmannaf's a9lh fork to use instead of AuroraWright's one?There is no a9lh.bin in data_input_v3.zip. It contains firm files and the secret_sector.bin These are files necessary to install the payloads. They have nothing to do with Luma3DS.
Oh for f*** sake I had to search to understand what you meant...But from where can I get hartmannaf's a9lh fork to use instead of AuroraWright's one?