Hacking GATEWAY 4.1 PRIVATE BETA RELEASE

[Temptress Cerise]

Would it be worth trying to use the emunand backup with my original SD card to get a GW emunand backup with its matching .sha file?

I mean, if you really want that .sha file, go ahead. Hourglass9 though will protect your A9LH, and the .sha files weren't always around. It's just better to have them for peace of mind.

 

[codezer0]

Well... I was just thinking that presently, it's on 2.1.0. Not sure how I would be able to launch what I need to actually make that emunand backup.

 

[Temptress Cerise]

Well... I was just thinking that presently, it's on 2.1.0. Not sure how I would be able to launch what I need to actually make that emunand backup.

Sigh... just install A9LH.... continue with Section II and Section III. Once you are at Section IV, don't begin it... Instead hold Y on boot to launch EmuNAND9.... press select to safely eject your current SD Card... Insert your old SD Card with your GW EmuNAND, go to EmuNAND Manager Options -> Backup EmuNAND to file. Assuming you are using the latest EmuNAND9 release, your backup will have a .sha file as well. Once done, press select to safely eject that old SD Card. Back on your computer transfer that Emunand backup (.bin and .sha) to your other SD Card. Then continue with Section IV using that EmuNAND backup you just made.

I am assuming your GW EmuNAND is still on your old SD Card and that you used a new one for the A9LH process.

 

[Subtle Demise]

hay guiz gayway (lol) sux so bad dey dun stoled from da sceenzterz even do it wuz al fre n open surs

I can't blame them at all for attempting to stay relevant. If I even bothered with the 3DS anymore, I would still use gateway.

 

[codezer0]

Sigh... just install A9LH.... continue with Section II and Section III. Once you are at Section IV, don't begin it... Instead hold Y on boot to launch EmuNAND9.... press select to safely eject your current SD Card... Insert your old SD Card with your GW EmuNAND, go to EmuNAND Manager Options -> Backup EmuNAND to file. Assuming you are using the latest EmuNAND9 release, your backup will have a .sha file as well. Once done, press select to safely eject that old SD Card. Back on your computer transfer that Emunand backup (.bin and .sha) to your other SD Card. Then continue with Section IV using that EmuNAND backup you just made.

I am assuming your GW EmuNAND is still on your old SD Card and that you used a new one for the A9LH process.

Yes, exactly. Okay, that makes the most sense right now.

 

[codezer0]

Is there an appropriate solution to dealing with a 2.1.0 downgraded system just... always going black screen when starting up with the SD card inserted? Annoyingly, putting it back in and going through settings and stuff to return to the home menu causes it to freeze as well.

 

[Temptress Cerise]

Is there an appropriate solution to dealing with a 2.1.0 downgraded system just... always going black screen when starting up with the SD card inserted? Annoyingly, putting it back in and going through settings and stuff to return to the home menu causes it to freeze as well.

Boot without the SD Card inserted... then once in the home menu, insert it... then load up the web-browser and continue from there... you really shouldn't be on 2.1 for that long...

 

[codezer0]

well, right now it's not wanting to use that dukesrg url. it keeps insisting no access point is in range. Finished setting up the internet connection and it's still saying the same thing.

Not much sooner than I type that, it then loads arm11.bin... and powers off. Checking the SD card on my PC, I see that it left an otp.bin of 1kb. Granted I had to do the select on the glitched screen, but is an otp supposed to be that small? I'm just wondering if I should redo it...?

One more question, at least regarding Gateway. Currently the only version hosted on their site is 4.1b for the private beta, which I hear tell doesn't work with this A9 method. the launcher.dat that I'd been using though is from 3.7.1, which probably fhas far exceeded nintendo update expectations. Is it acceptable to stick with 3.7.1?

 

[Temptress Cerise]

well, right now it's not wanting to use that dukesrg url. it keeps insisting no access point is in range. Finished setting up the internet connection and it's still saying the same thing.

Not much sooner than I type that, it then loads arm11.bin... and powers off. Checking the SD card on my PC, I see that it left an otp.bin of 1kb. Granted I had to do the select on the glitched screen, but is an otp supposed to be that small? I'm just wondering if I should redo it...?

Your suppose to be seeing the SafeA9LHInstaller.... are you sure you copied the arm11.bin and arm9.bin from the SafeA9LHInstaller zip to the root of your SD card as instructed in Part 5, Section I, Step 6? Did you also do Steps 4 and 5?

 

[codezer0]

Your suppose to be seeing the SafeA9LHInstaller.... are you sure you copied the arm11.bin and arm9.bin from the SafeA9LHInstaller zip to the root of your SD card as instructed in Part 5, Section I, Step 6? Did you also do Steps 4 and 5?

I was up to section 2, and I got the glitched screen. the troubleshooting said to go ahead and press select anyway, and it powered off. At first tried turning it on again, but just had the solid black screen. But powering it off and putting said SD card back on the PC showed there was an OTP.bin in the a9lh folder. Simply, instead of rebooting, it powered off.

Currently up to section IV where I have Hourglass9 loaded. Right now, I am having it do its backup of the emunand from my GW SD card. And from what I'm reading here and on Aroth's post earlier, I should probably also transfer the sysnand backup to the SD card that I'd been using so far for this A9 stuff.

 

[Temptress Cerise]

I was up to section 2, and I got the glitched screen. the troubleshooting said to go ahead and press select anyway, and it powered off. At first tried turning it on again, but just had the solid black screen. But powering it off and putting said SD card back on the PC showed there was an OTP.bin in the a9lh folder.

Then you are done, black screen is because no CFW can boot 2.1. Go ahead and continue with the rest of the guide.

And the otp.bin is suppose to be 256 bytes. (Right-click it to get the size in bytes, otherwise it'll be reported by Windows as a 1KB file.)

 

[codezer0]

Then you are done, black screen is because no CFW can boot 2.1. Go ahead and continue with the rest of the guide.

And the otp.bin is suppose to be 256 bytes. (Right-click it to get the size in bytes, otherwise it'll be reported by Windows as a 1KB file.)

Okay, perfect. I just checked the otp.bin in the details and see that it is indeed 256 bytes. Mirrored it to my Google drive as well. And awkawrd to see it take up 16KB on the flash drive I currently have it (locally) mirrored to.

Okay, two more questions.

It's my understanding I can skip Section V, as I am not (yet) wanting to delete the emuNAND, and still want the ability to boot from it; seeing that it's also where all my legit stuff is on. Section VI assumes to use EmuNAND9 to backup the A9'd sysNAND. Could I use HourGlass9 instead, since I already have it up and running?

Second. For the GW launcher.dat file... I presently have the 3.7.1 launcher.dat in the root of my GW SD card. The other post I linked to suggested using 4.0b because of issues with 4.1b. However, going on Gateway 3DS's site, it currently only shows links for 4.1b. Is it known if it's safe to use 4.1b from the Private Beta page, or may I still use 3.7.1 launcher?

 

[codezer0]

Okay. Update on my end.

While I had Hourglass9 running to have it restore the A9'd sysNAND, I then used it to backup my GW EmuNAND from my GW SD card. Then copied this over to the other SD card I was using, and used the same utility to A9 and restore this to the emuNAND on both cards. Following Aroth's post, I disabled the autoboot sysnand, and updated sysNAND options. Now, it seems that when I don't press anything, it uses Luma to autoboot the emunand. I just finished copying the files I need so I could just press up to (in theory) boot GW mode on the EmuNAND (by pressing up), as well as copied over the files from the SD I was using for the A9 install process to the GW SD card.

But, how would I boot sysNAND (with Luma) ? I believe there were a few more things it wanted me to install. **EDIT** Okay, L+Select seems to give me sysNAND, but I'm presuming with Luma. And weirdly, it doesn't have FBI installed?

Well, noticing now, it seems it auto-boots Luma, but despite having the files where they should be, it's not launching GW mode at all, neither on emuNAND nor SysNAND. Though I currently still just have the 3.7.1 launcher.dat in the root of the GW SD; I'd since migrated to using that again. What should I do?

**EDIT 2**

Just to be sure this was all worth it, while it autoboots luma in emuNAND, tried to run one of my ambassador GBA titles. And it immediately goes to black screen "an error has occurred", and forcing a hard reboot.

So, not only can't run GW3DS mode at all (which I was afraid of), but I can't even run the GBA and DSiWare stuff that I even bothered to do all this for.

 

[Aroth]

Okay. Update on my end.

While I had Hourglass9 running to have it restore the A9'd sysNAND, I then used it to backup my GW EmuNAND from my GW SD card. Then copied this over to the other SD card I was using, and used the same utility to A9 and restore this to the emuNAND on both cards. Following Aroth's post, I disabled the autoboot sysnand, and updated sysNAND options. Now, it seems that when I don't press anything, it uses Luma to autoboot the emunand. I just finished copying the files I need so I could just press up to (in theory) boot GW mode on the EmuNAND (by pressing up), as well as copied over the files from the SD I was using for the A9 install process to the GW SD card.

But, how would I boot sysNAND (with Luma) ? I believe there were a few more things it wanted me to install. **EDIT** Okay, L+Select seems to give me sysNAND, but I'm presuming with Luma. And weirdly, it doesn't have FBI installed?

Well, noticing now, it seems it auto-boots Luma, but despite having the files where they should be, it's not launching GW mode at all, neither on emuNAND nor SysNAND. Though I currently still just have the 3.7.1 launcher.dat in the root of the GW SD; I'd since migrated to using that again. What should I do?

Sorry for the lack of replies, I JUST got home. You should probably have the 4.0b launcher.dat file, though from what I understand the 3.7.1 version should work as well.

Did you put the gateway.bin and <button>_v2gw.bin files in sd:\luma\payloads? Are you holding the button you used in the name for <button>_v2gw.bin during boot?

 

[codezer0]

Sorry for the lack of replies, I JUST got home. You should probably have the 4.0b launcher.dat file, though from what I understand the 3.7.1 version should work as well.

Did you put the gateway.bin and <button>_v2gw.bin files in sd:\luma\payloads? Are you holding the button you used in the name for <button>_v2gw.bin during boot?

Well, trying to get it now, I can't. The only version offered is 4.1b from the Private beta page, and the official 3.7.1 release. Holding down the button regardless just gets a solid black screen, so I can't even see if it's loading emuNAND nor sysNAND. I don't get to see the GW menu, or anything.

Heck, even now, I can't seem to determine or make it go between emu or sysNAND.

So I currently can't get it to let me launch Gateway mode at all for the games currently on my red card, it won't launch any gba or DSi ware, either.

 

[Aroth]

Well, trying to get it now, I can't. The only version offered is 4.1b from the Private beta page, and the official 3.7.1 release. Holding down the button regardless just gets a solid black screen, so I can't even see if it's loading emuNAND nor sysNAND. I don't get to see the GW menu, or anything.

Heck, even now, I can't seem to determine or make it go between emu or sysNAND.

So I currently can't get it to let me launch Gateway mode at all for the games currently on my red card, it won't launch any gba or DSi ware, either.

Gimme a few to pm you. PM'd you some info.

Stupid gateway didn't update their arm9loaderhax.bin file to work with the new 4.1b files.

If you are having trouble finding that arm9loaderhax.bin file (which you need to rename to gateway.bin and place it inthe /luma/payloads/ folder, go to their "Private Beta" page and search for "a5043db33e45aaa4423ab87e25e93f88"

 

[codezer0]

Gimme a few to pm you. PM'd you some info.

Stupid gateway didn't update their arm9loaderhax.bin file to work with the new 4.1b files.

If you are having trouble finding that arm9loaderhax.bin file (which you need to rename to gateway.bin and place it inthe /luma/payloads/ folder, go to their "Private Beta" page and search for "a5043db33e45aaa4423ab87e25e93f88"

Appreciate the effort. Tried what you sent me, but it made no difference. I still get the same result. Attempting to use the pad_key for loading GW mode just gives me a black screen.

And Luma for all its promises of covering what I was missing with the GW3DS (and the entire reason I even bothered to consider CFW AT ALL), won't load any GBA nor DSiWare.

If anything, I feel like I wasted two days for nothing.

 

[Aroth]

Appreciate the effort. Tried what you sent me, but it made no difference. I still get the same result. Attempting to use the pad_key for loading GW mode just gives me a black screen.

And Luma for all its promises of covering what I was missing with the GW3DS (and the entire reason I even bothered to consider CFW AT ALL), won't load any GBA nor DSiWare.

If anything, I feel like I wasted two days for nothing.

The GBA/DSiWare not loading is because you are launching them from emunand. Afaik even Luma would require that they be installed to both emunand and sysnand in order to launch them from emunand.

When you open a GBA game it soft reboots the console into AGB_FIRM (and DS/DSi/DSiWare games soft reboot into TWL_FIRM). This reboot resets your system's read/write calls back to sysnand and its data folders, at which point if the game is not also installed on sysnand it errors out because it cannot find them. The reason this is a non-issue for most Luma3DS users is because we use an updated sysnand and no emunand, so the games are exactly where the system expects them to be after the reboot into AGB/TWL_FIRM.

 

[codezer0]

Okay, what the hell?

I tried re-downloading the same a9 file from Gateway-3ds's site. same hash, same link. renamed and verified things before putting it in the 3DS again. And now it works?! Was literally just dealing with Steam this morning deciding it didn't want to launch anymore to the point I even tried reinstalling the whole program and it also not wanting to work, and then just not even an hour later, it started working again.

Okay, so GW is working again... one exasperated me later.

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

Even so, was also trying to see if/how freeshop is better than CIAngel. My immediate problem with CIAngel is that it flat out doesn't list even half of what's available in the real eshop. But if I run freeshop, it just tells me it needs some enctitlekeys file, but I couldn't find where or how to make it.

... I think I should head to bed, before I break something irreparably.

 

[Aroth]

Okay, what the hell?

I tried re-downloading the same a9 file from Gateway-3ds's site. same hash, same link. renamed and verified things before putting it in the 3DS again. And now it works?! Was literally just dealing with Steam this morning deciding it didn't want to launch anymore to the point I even tried reinstalling the whole program and it also not wanting to work, and then just not even an hour later, it started working again.

Okay, so GW is working again... one exasperated me later.

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

Even so, was also trying to see if/how freeshop is better than CIAngel. My immediate problem with CIAngel is that it flat out doesn't list even half of what's available in the real eshop. But if I run freeshop, it just tells me it needs some enctitlekeys file, but I couldn't find where or how to make it.

... I think I should head to bed, before I break something irreparably.

For CIAngel you have to search for the titles, afaik it wont show you a list. Make sure you have selected "create cia" and the proper region. For the enctitlekeys file, google "3DS Title Key" and it SHOULD be the first link. Cannot directly link it in the forums due to rules and such. My experience has been that freeShop is better for finding games, but for DLC you have to use CIAngel.