Hacking The status of Gateway and A9LH
- Thread starter CreAtor135
- Start date
- Views 191,839
- Replies 1,476
- Likes 9
So what happens with users above 9.2 Sysnand? When we'll be able to downgrade man...?
Im tired about the A9HL stories when a lot of us are just asking GW to upload the final GW Time Machine for us, god damn!
Im tired about the A9HL stories when a lot of us are just asking GW to upload the final GW Time Machine for us, god damn!
So I'm still on the pre-a9lh 9.2/10.x sys/emu setup using the 3dsx to boot into emunand and have toyed with the idea of setting up al9h with Luma.
I pretty much only use my gateway card because it's the least amount of fuss/effort however I take it that the card does notnwork anymore unless you use their a9lh? Should I just stick with my setup and wait it out?
I pretty much only use my gateway card because it's the least amount of fuss/effort however I take it that the card does notnwork anymore unless you use their a9lh? Should I just stick with my setup and wait it out?
sorry but my mother language was italian,flags speak for me(but why don't you try to speak mine and will see what happens after?
)end of joke,in any case i think the message was clear enough to be understood for who want,A9LH+liomajor payloads for GW card gives a double kick in the .ss of gateway team,clear like the sun! Q: Can you provide a BIN file that is compatible with my existing A9LH (non-GW) setup?
A: We’re working on a solution for this.AHAHAHAAHHAAHHAAHAH
Last edited by AlucardjX,
Advice: now that beta is public opened for it, if GbaTemp users want to make a good contribution, any of you should open an oficial post. Like... Now.
Don't update through Gateway mode. Use Luma3DS to update sysNAND to 11.0.
Pretty sure @CreAtor135 will keep this thread updated. Don't really see any need for a new thread.
Also,
Damn, that sucks. Just tried the new 4.0b Launcher.dat, and it does give that nag screen. Back to 4.0a.
If you don't have a hardmod, I would wait for any kind hardmod users//members to test this, before trying it yourself.
Downloading the files from nus and installing it from a cia installer should also work in gateway mode if I'm right, because it should not start the to install the firm to its partitions, but I'm not completely sure atm.
I've updated the thread, now we wait for the results to come in.
Though I am quite happy with liomajor's workaround until Gateway releases a compatible arm9loaderhax.bin for current A9LH (non-GW) setups.
Edit: Oops, never mind. I see it now.
Last edited by Temptress Cerise,
You won't lose your existing setup. You CAN restore your EmuNAND_original.bin to SysNAND with Decrypt9's "keep A9LH" SysNAND restore option (In which case I would recommend restoring your SysNAND_original.bin to EmuNAND in case you still need 9.2 for something in the future, you can always delete EmuNAND later if you decide you don't need it). But no one's holding a gun to your head. You don't have to swap NANDs. It just makes it easier to have everything in the same place since DSiWare and GBA games only run from SysNAND (you can install them to EmuNAND, but they really just act like oversized links to the SysNAND copies). Still, you can leave your SysNAND and EmuNAND right where they are if you prefer. Just restore EmuNAND_original.bin to EmuNAND instead of restoring it to SysNAND using the "keep A9LH" option. You only need to follow the guide step for step to the point where you install A9LH. Most of the stuff after that is just suggestions.
It's already been done by liomajor. Check it out HERE, and custom hotkey files are HERE.
GW boots to SySNAND if it doesn't find an EmuNAND usually. The problem is, it often detects remnants of a deleted EmuNAND. In which case it will crash unless you manually select SysNAND mode from the menu. Using EmuNAND9 to do a no EmuNAND format sometimes fixes this. GW did say the new version still boots to SysNAND, just gives a warning.
GW may be working on a .bin payload to release eventually, but this is a perfectly safe alternative you can use while you wait.
mm, neat.. so if i waited it out for the Payload.
you think that it would be possible to boot it like we boot Luma with our current A9LH?
i thought their A9LH was specific to their hax , meaning having to re-do the A9LH process.
so we wont have to re-do it when they release a payload later on ?
D
Deleted User
Guest
Well, their A9LH payload does only run their launcher for now, but liomajor's solution puts their payload in an alterrnate location, which you can assign many different hotkeys to. So, it's almost like having it on your chain loader already.
"Q: Can you provide a BIN file that is compatible with my existing A9LH (non-GW) setup?
A: We’re working on a solution for this."
Straight from the horse's mouth. When that happens, you can just assign the .bin to a hotkey like anything else, then re-run Safe A9LH Installer with normal Stage1 and Stage2 payloads to remove the extra payloads and hotkeys added by liomajor's version.
let us -wait xD
best thing would be a compatible payload man, without us having to do squat.
just placing their payload inside the luma/payload folder and loading it off there.(have no idea if this is possible though, i am a N00B) hwahahah.
awesome man, thanks for the info.
edit: regarding the liomajor alternative , the SD card has got to be either samsung/toshiba?
Last edited by leonmagnus99,
Similar threads
-
-
-
-
-
-
-
-
-
-
-
@
Psionic Roshambo:
32GBs is the baseline for 4K video editing these days and lots of recommendations for 64GBs but for games 16,GBs is honestly plenty for a long time. -
-
-
-
-
-
-
-
-
-
@
Psionic Roshambo:
Some sort of police thing going on near me lol "Get out of the car with your hands up and walk backwards towards us" over a loud speaker thing
-
-
-
-
