Download arm9loaderhax.bin from the downloads section of the Gateway website. Rename it to down_GW.bin and put it in luma/payloads. Also put launcher.dat from 3.7.1 on the root of your SD. Now you can hold down on boot up to launch Gateway.So I am almost across the finish line and I got to ask, how do I use my gateway after this and I will be in luma3ds auto so I don't need to worry about the RO module patch required for the CRO related hacks for pokemon games right.
does that matter in A9LH? or make more safe?Screen init is recommended and flashes your screen on boot, noscreen init does not display a screen flash, for those that are obsessed with their system being as stock as possible when hacked.
ThanksDownload arm9loaderhax.bin from the downloads section of the Gateway website. Rename it to down_GW.bin and put it in luma/payloads. Also put launcher.dat from 3.7.1 on the root of your SD. Now you can hold down on boot up to launch Gateway.
It didn't work so far I will try again.Download arm9loaderhax.bin from the downloads section of the Gateway website. Rename it to down_GW.bin and put it in luma/payloads. Also put launcher.dat from 3.7.1 on the root of your SD. Now you can hold down on boot up to launch Gateway.
From /r/3dshacks, about screen-init:does that matter in A9LH? or make more safe?
aha,i think i used the screen init files,because i can see the screen light up for brief second and goes off then boot luma3DS (but now i put anim9 the boot animation prevents me from knowing which version i have)From /r/3dshacks, about screen-init:
"It is a function of the system which turns the backlight on. Older versions of A9LH didn't have it, but now that it does, we can use Arm9 payloads at boot without adding separate screen init segments to each program."
Basically, it allows you to run payloads without each payload having code to turn the screen on.