Hacking GATEWAY 4.1 PRIVATE BETA RELEASE

[Quantumcat]

Still not sure how to get around the GBA/DSiWare problem, yet.

Did you install them to sysNAND too like you were told in the reply immediately preceding yours?

it flat out doesn't list even half of what's available in the real eshop

People have to buy it and contribute the titlekey. This is mentioned hundreds of times in the CIAngel & freeShop release threads as well as noob paradise.

it needs some enctitlekeys file

You can get this to download onto your console using enctitlekeysupdater. This is also mentioned hundreds of times in the freeShop release thread.

I'm beginning to think your Google skills leave a lot to be desired (I really feel for @Temptress Cerise who was getting detectably frustrated, yet managing to stay completely polite)

 

[Hayleia]

Still not sure how to get around the GBA/DSiWare problem, yet.

The answer to this was given just above your post.
The solutions are either to install your GBA games to both sysNAND and emuNAND or to stop using emuNAND.

edit: ninja'd

 

[yacepi15]

Im 100% sure that the "special feature" is sysnand updating. And im saying this as a Gateway card owner.

 

[DragonSky]

This is a private beta after all so it is not safe to use yet I think.

 

[yacepi15]

Its possible to use the "menu lockout" with the standard A9LH, non-gateturd one?
Thanks.

 

[Hayleia]

Its possible to use the "menu lockout" with the standard A9LH, non-gateturd one?
Thanks.

Yes, I have it. It's just a part of their Launcher.dat, not at all something in their a9lh implementation.

 

[Nightwish]

Okay, what the hell?

Yeah, I can now clearly see now how spending hours hoping that someone can explain the very fool proof guide instead of just using what already works is much, much better.

 

[codezer0]

Did you install them to sysNAND too like you were told in the reply immediately preceding yours?

People have to buy it and contribute the titlekey. This is mentioned hundreds of times in the CIAngel & freeShop release threads as well as noob paradise.

You can get this to download onto your console using enctitlekeysupdater. This is also mentioned hundreds of times in the freeShop release thread.

I'm beginning to think your Google skills leave a lot to be desired (I really feel for @Temptress Cerise who was getting detectably frustrated, yet managing to stay completely polite)

Up until now, I lacked the means to be able to install any .cia's or anything of the sort on sysNAND. So, no. I hadn't done that yet.

Never heard of enctitlekeysupdater, and didn't see it listed in the OP of the freeshop thread, nor when I went to go download it, either.

It's not the first time that Google has flat out not given me relevant information when I did search for it. That's why I am asking quesitons. And considering the crap I went through yesterday with one snafu after another, both with the 3DS and with Steam on my PC, I thought I was losing my damn mind. But that gives neither you nor anyone else an excuse to be terse and disrespectful about it.

The simple matter was that it flat out wasn't working until literally the 11th hour when I was finally too mentally exhausted to fiddle with it anymore and ready to head to bed. What makes it more infuriating to me is that I was using the exact same links I was directed to from the beginning, and yet somehow redownloading and retrying for the umpteenth time ended up finally working on this CFW path, when the original DS Profile 'sploit with the Gateway card worked the first time, and worked every time thereafter for the better part of the three years that I've had the thing.

 

[Hayleia]

What makes it more infuriating to me is that I was using the exact same links I was directed to from the beginning, and yet somehow redownloading and retrying for the umpteenth time ended up finally working on this CFW path, when the original DS Profile 'sploit with the Gateway card worked the first time, and worked every time thereafter for the better part of the three years that I've had the thing.

Well of course the DS exploits worked better. It had requirements you met, such as "you must be on 4.X and have a DS cart, in all other cases you can gfy". Same, if the a9lh guide told you "you must be on 2.1.0, have a 9.2 backup and an internet connection, in all other cases you can gfy", it would have been as easy as the DS exploit.

edit
Haha ! I wanted to add "and If you want to follow Gateway's direction to install their a9lh, I challenge you to do so", and add a link to a thread where someone had problems as an example but was too lazy to search for one. I guess I didn't have to look too far actually, this one is in the recent posts on the forum home http://gbatemp.net/threads/tried-the-gateway-3ds-4-1-a9lh-firmware-semi-bricked-my-o3ds-xl.436940/

 

[Aroth]

So after further testing, the 4.1b launcher.dat file DOES work with the pre-existing arm9loaderhax.bin file.

Turns out to be user error as a result of using the same microSD card for both the bluecard and the redcart. The updated launcher.dat file takes major offense to the presence of the file "_DSMENU.DAT" being on the microSD card inside the redcart during boot, resulting in a blackscreen after the GW logo.

 

[Quantumcat]

Up until now, I lacked the means to be able to install any .cia's or anything of the sort on sysNAND. So, no. I hadn't done that yet.

You managed to install stuff to emuNAND, right? So therefore you can do the same thing to install to sysNAND. Where was the problem there? In fact, since your sysNAND is 9.2 you could even use FBI.3dsx. You could have made your life a million times easier by going with the recommended setup of sysNAND only. This means you can just follow the guide as written and not need to work anything out for yourself.

Never heard of enctitlekeysupdater, and didn't see it listed in the OP of the freeshop thread, nor when I went to go download it, either.

http://lmgtfy.com/?q=how+to+get+enctitlekeys+freeshop

 

[codezer0]

Um, I didn't have cubic ninja? Or ocarina of time? I was still on 4.4 until I followed this stuff to a9 this thing? Did you so quickly forget? There wasn't a means to install any 3ds files when I had first got the gateway. And since it had worked so well for so long, I hadn't even been keeping up on any of the other developments. The fact that my 3ds was working as (mostly)desired meant I had no motivation to find alternatives. "Don't fix what isn't broke," remember?

Giving me attitude is exactly part of the problem I have with the scene now. It's like all of the extreme opinions on Ghostbusters 2016. Everyone's so wrapped up in one extreme or another, they can't even conceive of having something to agree on, or letting someone form their own opinion. And since so many bitter people here are so convinced that their homebrew path is so superior, well... Be ready if shit goes wrong. Like it was for me nearly every step of the way when I was trying to follow your fool lauded Bible for this A9 stuff.

So far, the only thing that is an obvious tell for me as an improvement with A9, is that emuNAND boots up a crap ton faster than before. That's one thing I currently can't take away from A9 compared to the old way. But disrespecting me and treating me like an idiot won't earn you any favors.

 

[Quantumcat]

But ... you said GBA games didn't work ... therefore you installed them in some way ...

 

[codezer0]

But ... you said GBA games didn't work ... therefore you installed them in some way ...

They were form my original, non-XL 3DS. The one that I originally earned my Ambassador credentials on.

Let me see if I can explain this properly.

I first had just a bone-standard 3DS, albeit with one of the NyKo extended batteries. Not long after that, I earned the ambassador privileges, and the associated games.

When I found out about the Gateway 3DS, and the required firmware, my O3DS was already past the firmware window. At the time, my only option, was to buy another 3DS system in a vulnerable range. I lucked out and found an O3DS XL, whose sysNAND was on 4.4.

Ordered the GW 3DS almost the same day. At the time, the GW launcher was being controversial for the brick code going on. Whether by consequence or miracle, because the e-seller of the flash carts was being so slow about getting it out to me, to the point one of the fellow GBATemp mods had to go and contact them on my behalf because they flat out weren't responding to any of my own email inquiries, it arrived just in time for the newer version of said launcher to be released and available.

So, I got the GW 3DS, used the kit with my XL, and within its emuNAND, I did the system transfer from my O3DS, to my (then-new) 3DS XL. So everything I had legitimately from then, was now on the GW emuNAND.

I never had to do a .cia for GBA or DSiWare, because I had them legit long before CFW was even a twinkle in smea's eye, let alone there being a title/package manager to allow me to install anything on either NAND.

Yes, I was disappointed that GBA and DSiWare didn't work, but there was no such thing as CFW then. And I only bothered to start looking into it when people were bragging about how CFW allowed them to actually launch those without a problem.

The rest, is proverbial history.

I hope that cleared it up. Because presently, I don't know how to word it any clearer than that.

 

[Quantumcat]

Well, it didn't really clear it up, since I'm not sure how you would know it didn't work in order to ask how to make it work if you had never tried running it in the first place.

But anyway, good luck.

 

[Aroth]

Well, it didn't really clear it up, since I'm not sure how you would know it didn't work in order to ask how to make it work if you had never tried running it in the first place.

But anyway, good luck.

Sounds to me like he installed the Ambassador GBA games directly from the store (which he can do as an Ambassador) and then when he tried to launch them they would have gave a fatal error and forced a reboot of the system.

 

[codezer0]

Sounds to me like he installed the Ambassador GBA games directly from the store (which he can do as an Ambassador) and then when he tried to launch them they would have gave a fatal error and forced a reboot of the system.

That's pretty much it. And for a long time, I more or less accepted that I wasn't going to be able to use either the GBA VC or the DSiWare on my 3DS. And that sadly, I didn't have a way to use either on my DSi XL, short of maybe the Supercard DStwo...

It's only recently, on this forum no less, that people were soon bragging how the CFW path could let me play these games again.

 

[Aroth]

As I tried to explain earlier in the thread, this happens/happened because of the way the system handles compatibility with DS/DSi/DSiWare and GBA games. For all things DS(i), it reboots the system into TWL_FIRM, for all things GBA it reboots into AGB_FIRM. This reboot wipes the patched redirects that made it read data from the emunand partition instead of the NAND chip. So basically the following happens:

You boot gateway and load emunand.
System is patched to direct all NAND requests (read and write) to the emunand partition.
SD card request PATH is set to "sd:\Nintendo 3DS\<id0c>\<id1d>\" and its contents are decrypted using the key(s) stored in the emunand.
You launch a GBA game.
The system sends command to reboot into AGB_FIRM and load data from the proper "%PATH%\title\<id>\" folder.
System reboots and clears all patches, PATH is reset to "sd:\Nintendo 3DS\<id0a>\<id1b>\"
AGB_FIRM is loaded and attempts to load data from "%PATH%\title\<id>\".
System fails to find the folder in question and thus encounters a fatal error, forcing a reboot.

This is avoided by installing to both emunand and sysnand, so that the data is found after the soft-reboot. Alternatively if you leave the NANDs linked they will read from the same "\<id0>\<id1>\" folder.

 

[tony_2018]

I'm disappointed. The fact that they're sticking with acting like they invented A9LH is ridiculous. I'm going to write an E-Mail to them, and maybe they'll even respond, being that I'm the one who posted the info here.

Sure.

 

[codezer0]

Well, a hearty thanks to user @Aroth for helping me out, and for being patient enough with me. Was pretty much able to get everything sorted out.

So now, mine's all A9'd with Luma and GW 4.0b, with the sysNAND all current and everything.

A9 master race? How about A9 CFW+GW Divinity?