Hacking The status of Gateway and A9LH
- Thread starter CreAtor135
- Start date
- Views 191,499
- Replies 1,476
- Likes 9
Boot Manager Mega Configs updated again. Added Corbenik to the "CFWs" menu. Have fun. As always, the full version, with all needed files, is on the iso site in the "CFW Discussions" forum.
Well, there's something weird on my 3DS.
I'm already using Luma3DS + Arm9 and FW11.0 and I'm trying to boot my gateway 3ds payload direct on my sysnand using Luma payload folder and renaming the payload to x_gw.bin; however, I just get blackscreen after the dragon image.
I already formatted my SD (and removed the previous EmuNAND), tried both 3.7.1 and 4.0 launcher.dat versions and nothing.
But what makes me think is the fact that if I use the gateway arm9loaderhax.bin direct on the root of my SD card, it boots on sysnand and everything works as expected. But what's the problem with the payload and Luma channeler?
I'm already using Luma3DS + Arm9 and FW11.0 and I'm trying to boot my gateway 3ds payload direct on my sysnand using Luma payload folder and renaming the payload to x_gw.bin; however, I just get blackscreen after the dragon image.
I already formatted my SD (and removed the previous EmuNAND), tried both 3.7.1 and 4.0 launcher.dat versions and nothing.
But what makes me think is the fact that if I use the gateway arm9loaderhax.bin direct on the root of my SD card, it boots on sysnand and everything works as expected. But what's the problem with the payload and Luma channeler?
Sir, it worked like a charm! I still do not know why Luma channeller does not work, but it does not matter anymore.
Thank you very much for your help!
You're very welcome!
(Perhaps, Gateway does not want you to use Luma for launching their payload...)
Last edited by satelman,
Your problem was that you still had remnants of your emuNAND left on your SD that GW is detecting. The solution is to reformat with emuNAND9 with the Format SD (no emuNAND) option.
Really? Well, in that case I will try to format using EASEUS and Panasonic's SD Formatter combo and after that I will try Emunand9 again.
Thanks for the tip.
Those tools don't remove EmuNAND//RedNAND completely. If that's what you used to originally remove it, then there is you cause of your problem.Really? Well, in that case I will try to format using EASEUS and Panasonic's SD Formatter combo and after that I will try Emunand9 again.
Thanks for the tip.
Originally I did not used those tools. I just formatted using EmuNAND9. Alas, EmuNAND9 before formatting accused that there was a GW Emunand on my SD and after the formatting it says that Emunand is not ready (or something like that). I still got the black screen, though.
Excuse my ignorance, but what exactly is a "no-screen init fork"? I'm using LUMA3ds version 5.5 before trying to make gateway work. I saw you guys talking about it but I have no idea what is this for. What I can say (I did a quick search) is that when I boot my 3DS it shows the AuReinand splash screen (well, not anymore because I replaced the original arm9loaderhax by the arm9select's one), if this helps.
Edit: found the answer of no-screen init fork. I use a screen init fork one.
Last edited by kaiobj,
Made another update to my Boot Manager Mega Configs. This time to update Decrypt9, EmuNAND9, and GodMode9. Complete version coming to the iso site in a few minutes.
I've just completed A9LH installation following Plailect's guide and Luma is booting perfectly. I wanted to have Luma and Gateway share sysNAND but I'm getting a black screen when I try to boot into Gateway.
I've formatted my SD with Emunand9's no emuNAND option, I have launcher.dat (tried 3.7.1 and 4.0a) on the root of the SD and Gateway's a9lh payload in luma/payloads renamed to l_gw.bin so I can hold L to boot into Gateway. As I understand it Plailect's guide uses a screen init version of a9lh which Gateway requires. What am I missing?
edit: Got it working. just changed the hotkey, seems L isn't supported.
I've formatted my SD with Emunand9's no emuNAND option, I have launcher.dat (tried 3.7.1 and 4.0a) on the root of the SD and Gateway's a9lh payload in luma/payloads renamed to l_gw.bin so I can hold L to boot into Gateway. As I understand it Plailect's guide uses a screen init version of a9lh which Gateway requires. What am I missing?
edit: Got it working. just changed the hotkey, seems L isn't supported.
Last edited by Fgamer,
Something went wrong here on my end. I had a working threeStage A9LH setup but wanted to revert back to the standard config from this zip file using CBM9 as starting point. I therefore copied the payload stage 1 and stage 2 to my existing a9lh folder to overwrite the existing payloads and updated a9LH with the supplied safea9lh installer from the zip file. Now my O3ds doesn't boot anymore. Blue light stays on but screens stay black.
Am I screwed now? Hardmod needed (I must have a soldering iron somewhere from the old days)?
Edit: tried sanother working SD card, no success
Edit2: false alarm I think, put Luma back as default bin file (booting fine) but I think I was confused because this a9lh payload apparently doesn't do screen init.
Last edited by wiiuser2,
The Gateway "A9LH Fastboot" install instructions don't say to make a NAND backup.. but they are saying to restore it here.... does the Time Machine app create a NAND backup automatically? Or did Gateway forget to add "Do a NAND backup" to their instructions? Does the restore step let you choose a file or does it pick a file specifically named NAND.bin? And if so, should it be on uSD or bigSD? Thanks.
I included "no init" at one point, but thought I had reverted it to "screen init" because I was having issues with CBM9. I'll have a look at it. If it's the wrong files, I'll replace them.
EDIT: I'm not sure how, but it looks like I left the "no init" payloads in the archive by mistake. I'll correct it. That definitely explains why CBM9 wasn't working. The main version definitely doesn't like "no init" payloads. Sorry about that. I thought I had replaced those ages ago.
EDIT 2: It's fixed now. The original "screen init" files are now included as intended. I would advise anyone who's downloaded my Boot Manager Mega Configs before to re-download.
Made another update to my Boot Manager Mega Configs. This time to update Decrypt9, EmuNAND9, and GodMode9. Complete version coming to the iso site in a few minutes.
I'm not sure. I used their NAND dumper to dump NAND.bin before running the installer. I just assumed it would probably refuse to run if there wasn't one on the card. Much like the old downgrader. They probably just forgot to mention it. Backing up your NAND is just something you do automatically if you've been at this for a while. So it's understandable if they forgot to mention it explicitly. They'll probably correct it in the public release.
Last edited by Kazuma77,
Similar threads
