Hacking Let's say my GW card breaks or I lose it...

[Kibido]

Am I fucked?

More precisely, would I be fucked if I installed the SOON to be released GW-a9lh and then broke or lost my card? No way of switching to a cfw or regular a9lh then? I have to admit, taking that red card in and out (since it sucks battery) is starting to become annoying after 3 years.

 

[Temptress Cerise]

Yes. You would be so f*cked until you got a new one. Even though I own two, I would not dare install GW-A9LH. I would not even wish GW-A9LH on my enemies. I feel like GW-A9LH is resevered for the deepest, darkest parts of hell.

Just get Standard A9LH, and use BootCTR9 to boot GW's a9lh.bin. Or install a compatible v2 A9LH fork. Or install the older v1 A9LH fork.

Or stick with your current setup.

 

[Ra1d]

Suggestion, do not install yet, if when they release the "public" version it's still going to lock your console unless you own a GW card without a way of unlocking it, the screw that, I also own GW card and this would be stupid if they didn't introduce a way to reverse the process in cases where you break/lose your card.

 

[Epicbeardman]

Also, don't forget that if something happens to your GW, you're left with a bunch of encrypted save files that you can't do shit with without getting another GW (or borrowing someone elses to decrypt them, should you happen to know someone who has one). This is one of the things that really bothered me and pushed me to switch from GW to A9LH+Luma3DS. Thanks to this guide by @MattKimura, the process of decrypting all of my GW save files was really straightforward.

By the way, this has nothing to do with GW-A9LH specifically, but is just a problem with GW in general.

 

[Temarile]

Once you've installed GW-A9LH your 3ds is married to the red card. So just install regular and then chain load the GW A9LH.bin to still load GW.

 

[Shadowfied]

Yes. You would be so f*cked until you got a new one. Even though I own two, I would not dare install GW-A9LH. I would not even wish GW-A9LH on my enemies. I feel like GW-A9LH is resevered for the deepest, darkest parts of hell.

Just get Standard A9LH, and use BootCTR9 to boot GW's a9lh.bin. Or install a compatible v2 A9LH fork. Or install the older v1 A9LH fork.

Or stick with your current setup.

I had no idea it was this bad. Not that I'd ever install Gateways A9LH when there's a proper detailed guide that doesn't require a GW cart. Why are they intentionally doing this shit? Like..why not just refer people to Plailects guide (they're obviously not ashamed to rely on others, as they often refer to, and use the HB Launcher etc) and then provide a payload for booting Gateway mode? Wouldn't that be better for both their consumers and themselves?

 

[Hayleia]

Yes. You would be so f*cked until you got a new one. Even though I own two, I would not dare install GW-A9LH. I would not even wish GW-A9LH on my enemies. I feel like GW-A9LH is resevered for the deepest, darkest parts of hell.

Just get Standard A9LH, and use BootCTR9 to boot GW's a9lh.bin. Or install a compatible v2 A9LH fork. Or install the older v1 A9LH fork.

Or stick with your current setup.

Do you have a link to a "compatible v2 A9LH fork"? Because I wouldn't want to be kicked out of Gateway (though I never use my red card...) but I wouldn't want to miss stuff that doesn't work with v1 (though there is no such thing at the moment).

 

[Shadowfied]

Do you have a link to a "compatible v2 A9LH fork"? Because I wouldn't want to be kicked out of Gateway (though I never use my red card...) but I wouldn't want to miss stuff that doesn't work with v1 (though there is no such thing at the moment).

There is actually one thing that doesn't work A9LH v2....Gateways' payload.

 

[Hayleia]

I had no idea it was this bad. Not that I'd ever install Gateways A9LH when there's a proper detailed guide that doesn't require a GW cart. Why are they intentionally doing this shit? Like..why not just refer people to Plailects guide (they're obviously not ashamed to rely on others, as they often refer to, and use the HB Launcher etc) and then provide a payload for booting Gateway mode? Wouldn't that be better for both their consumers and themselves?

They want to be relevant again. So instead of giving us an arm9loaderhax.bin months ago, they wasted time doing betas of downgraders and a9lh installers then declared "hey, look at what we've done and created and invented, amazing Gateway FAST BOOT, aren't we awesome", and THEN ONLY they give us the arm9loaderhax.bin saying "aka a9lh", so that people who get information from their website and read stuff in that order think that Gateway is the creator of a9lh, and that their stuff is probably safer (so that you "marry your 3DS with GW" instead of installing safer and more open options).

There is actually one thing that doesn't work A9LH v2....Gateways' payload.

Yes, I know that. That's why I'm still on v1. But from what @Temptress Cerise said, it sounds like there is an a9lh v2 fork (not the "official" one) that works with it.

 

[Temptress Cerise]

Once you've installed GW-A9LH your 3ds is married to the red card. So just install regular and then chain load the GW A9LH.bin to still load GW.

Do you have a link to a "compatible v2 A9LH fork"? Because I wouldn't want to be kicked out of Gateway (though I never use my red card...) but I wouldn't want to miss stuff that doesn't work with v1 (though there is no such thing at the moment).

There is actually one thing that doesn't work A9LH v2....Gateways' payload.

They want to be relevant again. So instead of giving us an arm9loaderhax.bin months ago, they wasted time doing betas of downgraders and a9lh installers then declared "hey, look at what we've done and created and invented, amazing Gateway FAST BOOT, aren't we awesome", and THEN ONLY they give us the arm9loaderhax.bin saying "aka a9lh", so that people who get information from their website and read stuff in that order think that Gateway is the creator of a9lh, and that their stuff is probably safer (so that you "marry your 3DS with GW" instead of installing safer and more open options).


Yes, I know that. That's why I'm still on v1. But from what @Temptress Cerise said, it sounds like there is an a9lh v2 fork (not the "official" one) that works with it.

If you follow the guide, and use Aurora Wright's v2 A9LH fork, you'll need to use BootCTR9 to be able to use GW's A9LH.bin. Using Luma3DS' chainloader, you will just hang at a black screen. (Doesn't matter if you use screen-init or non-screen-init)

If you don't want to use BootCTR9, then you'll need to uninstall v2 A9LH, and install the older v1 A9LH.

Another alternative is to use a compatible v2 A9LH fork, as explained by liomajor in the following post.
Link: https://gbatemp.net/threads/safea9lhinstaller.419577/page-29#post-6432075

But you'll have to compile it yourself.

 

[Shadowfied]

If you follow the guide, and use Aurora Wright's v2 A9LH fork, you'll need to use BootCTR9 to be able to use GW's A9LH.bin. Using Luma3DS' chainloader, you will just hang at a black screen. (Doesn't matter if you use screen-init or non-screen-init)

If you don't want to use BootCTR9, then you'll need to uninstall v2 A9LH, and install the older v1 A9LH.

Another alternative is to use a compatible v2 A9LH fork, as explained by liomajor in the following post.
Link: https://gbatemp.net/threads/safea9lhinstaller.419577/page-29#post-6432075

But you'll have to compile it yourself.

What is special about BootCTR9 that Luma nor CtrBootManager9 doesn't do?

 

[Hayleia]

Another alternative is to use a compatible v2 A9LH fork, as explained by liomajor in the following post.
Link: https://gbatemp.net/threads/safea9lhinstaller.419577/page-29#post-6432075

But you'll have to compile it yourself.

Ah. I don't mind compiling it but I'm pretty sure I'll fail at finding the right files (like "the FIRM0 from 8.1"). I guess I'll just stay on v1.

 

[Catastrophic]

Dumb question, but why do people even use Gateway at all anymore? CFW makes it nearly obsolete.

 

[Hayleia]

Dumb question, but why do people even use Gateway at all anymore? CFW makes it nearly obsolete.

Mostly cheats I'd say (and saying "use NTR" is like saying "use Wine" when people say "this thing doesn't work on Linux"). Which shouldn't really convince anyone to buy a Gateway nowadays, but those who already bought one some time ago would probably like it better if they were still able to use it instead of switching completely to free CFWs.

(Also lol, why do people think a9lh is a CFW and GW isn't?)

 

[Temptress Cerise]

What is special about BootCTR9 that Luma nor CtrBootManager9 doesn't do?

Probably how it handles and initializes payloads that need initialization. I don't really know tbh. You could look into their respective source codes and see for yourself. The unofficial v7/v8/v9 of CTRBootManager9, should work. I think someone tested it with that, but I don't remember or have a link handy for that on where I read that, so I might be wrong.
Link: https://github.com/OperationNT414C/CtrBootManager/releases

Ah. I don't mind compiling it but I'm pretty sure I'll fail at finding the right files (like "the FIRM0 from 8.1"). I guess I'll just stay on v1.

That should be the new firm0.bin found in the new data_input_v2.zip found in Plailect's guide. It should have the following hashes:
SHA256: 6e4d14ad5150a59a875962b7090a3c744f724bbd973933f211c93522c8bb1c7d
SHA1: 40ff8ee94946232512d1d30ad266954828547cea
MD5: f0f8e46d11b388f19a31f3fad5c47e1b

However, maybe someone more experience on it, can chime in on it. Or you could ask over there to confirm if it's correct.

Dumb question, but why do people even use Gateway at all anymore? CFW makes it nearly obsolete.

Nearly. I use mine for ROM hacks and for the Cheat Menu. And please don't mention NTR, I don't like it's cheat-plugin whatever. Maybe had NTR been open source, it would have leaped and left Gateway's in the dust. But whatever.

 

[Shadowfied]

Probably how it handles and initializes payloads that need initialization. I don't really know tbh. You could look into their respective source codes and see for yourself. The unofficial v7/v8/v9 of CTRBootManager9, should work. I think someone tested it with that, but I don't remember or have a link handy for that on where I read that, so I might be wrong.
Link: https://github.com/OperationNT414C/CtrBootManager/releases


That should be the new firm0.bin found in the new data_input_v2.zip found in Plailect's guide. It should have the following hashes:
SHA256: 6e4d14ad5150a59a875962b7090a3c744f724bbd973933f211c93522c8bb1c7d
SHA1: 40ff8ee94946232512d1d30ad266954828547cea
MD5: f0f8e46d11b388f19a31f3fad5c47e1b

However, maybe someone more experience on it, can chime in on it. Or you could ask over there to confirm if it's correct.


Nearly. I use mine for ROM hacks and for the Cheat Menu. And please don't mention NTR, I don't like it's cheat-plugin whatever. Maybe had NTR been open source, it would have leaped and left Gateway's in the dust. But whatever.

Is it possible to use the GW Cheat menu on digital games now? I thought they said they were looking into that.

 

[Favna]

fix: don't use gatewait to begin with

 

[CreAtor135]

I'm not 100% certain but couldn't you just restore a pre-A9LH NAND through the GW menu?

 

[Temarile]

If you follow the guide, and use Aurora Wright's v2 A9LH fork, you'll need to use BootCTR9 to be able to use GW's A9LH.bin. Using Luma3DS' chainloader, you will just hang at a black screen. (Doesn't matter if you use screen-init or non-screen-init)

If you don't want to use BootCTR9, then you'll need to uninstall v2 A9LH, and install the older v1 A9LH.

Another alternative is to use a compatible v2 A9LH fork, as explained by liomajor in the following post.
Link: https://gbatemp.net/threads/safea9lhinstaller.419577/page-29#post-6432075

But you'll have to compile it yourself.

Oh sorry I didn't know that! I learned something new today I use v1 A9LH hence I can use chain loading to load GW

 

[Favna]

If you follow the guide, and use Aurora Wright's v2 A9LH fork, you'll need to use BootCTR9 to be able to use GW's A9LH.bin. Using Luma3DS' chainloader, you will just hang at a black screen. (Doesn't matter if you use screen-init or non-screen-init)

If you don't want to use BootCTR9, then you'll need to uninstall v2 A9LH, and install the older v1 A9LH.

Another alternative is to use a compatible v2 A9LH fork, as explained by liomajor in the following post.
Link: https://gbatemp.net/threads/safea9lhinstaller.419577/page-29#post-6432075

But you'll have to compile it yourself.

Oh sorry I didn't know that! I learned something new today I use v1 A9LH hence I can use chain loading to load GW

I have 0 knowledge of how (crappy) GateWay works and all that so if I'm wrong here then sorry but anyway, v2 a9lh can also be downloaded through aurora wright's repo or just check plailects guide on upgrading a9lh for the full package. Do mind that this guide assumes CFW from SD users, not GateWay users. https://github.com/Plailect/Guide/wiki/Updating-arm9loaderhax