Hacking GATEWAY 4.1 PRIVATE BETA RELEASE

[Aroth]

Funny enough, I just tried that, and then it's saying that an error has occurred, and only gives me the option to press START to exit back out.

Double check that the files are present on the card (assuming you already made an emunand on that sd card). Otherwise it might just be the usually finicky browserhax. That is one of the least reliable entrypoints, which is why we have you set up menuhax as soon as you get into the homebrew launcher menu.

 

[codezer0]

Now if I could just get browserhax to load in the first place... geezus. Got to the part of using tinyformat and it's telling me to launch browserhax to reinstall menuhax. So hopefully it should work better this time... with feeling!

Meanwhile, as I type this, managed to get to the point where it wants me to load up Luma and update the RedNAND. But at my first attempt, it gave an error and forced a reboot. At least, this allowed me to verify that menuHax was working this time, and I was able to re-launch into it.

**UPDATE**

Up to the part to reinject FBI. I made sure that the resulting file copied successfully. However, Decrypt9 currently is not allowing me to actually select it. It seems to only see hs.app...

 

[SonicCloud]

Well I guess I was wrong ... but seriously fuck it, why would you care? If anyone has to write them to tell them that they are "stealing" free work and selling it, it has to be the devs behind those hacks.
Why do people act like the scene sherifs whenever GW pushes an update?? Don't you have Pokemon GO to play or something?

I don't because phone is too shit :c


Honestly i understand that GW has maked lots of bricks...But why bash them everytime someone mentions "Gateway?"

If you would be a dev of the Gateway flashcards. You would obviously feel bad, as everyone is taking to the trash your work...
I don't know, atleast for me i would feel bad ....

I don't have a GW Flashcard since i started hacking my 3DS since this year, but still, it is wrong to bash someone work even if you we're using it before... smh

 

[Aroth]

Now if I could just get browserhax to load in the first place... geezus. Got to the part of using tinyformat and it's telling me to launch browserhax to reinstall menuhax. So hopefully it should work better this time... with feeling!

Meanwhile, as I type this, managed to get to the point where it wants me to load up Luma and update the RedNAND. But at my first attempt, it gave an error and forced a reboot. At least, this allowed me to verify that menuHax was working this time, and I was able to re-launch into it.

**UPDATE**

Up to the part to reinject FBI. I made sure that the resulting file copied successfully. However, Decrypt9 currently is not allowing me to actually select it. It seems to only see hs.app...

out of curiousity, is there a decrypt9 folder on the root of your sd card?

If so delete it because if decrypt9wip sees that folder it automatically directs its path to look there only.

 

[codezer0]

out of curiousity, is there a decrypt9 folder on the root of your sd card?

If so delete it because if decrypt9wip sees that folder it automatically directs its path to look there only.

Pretty sure I did that. Even so, a full power cycle and restarting into menuHax and it was finally working again. Now getting to the part regarding OTP...

Spoiler: Pretty much me right now

 

[Aroth]

Pretty sure I did that. Even so, a full power cycle and restarting into menuHax and it was finally working again. Now getting to the part regarding OTP...

Spoiler: Pretty much me right now

Believe it or not, if you have made it to the OTP stage, you are pretty much past the part where you are most likely to encounter random glitches and errors. All stages of the downgrade, otp dump and a9lh install are pretty well safe guarded and double or triple checked during the process. Just make sure you are downgrading your emunand, not sysnand, so that IF something goes sideways while running PlaiSysUpdater you can restore the backup that I am sure you made when the guide told you to. Most of the few issues and errors that can occur at that stage are well documented in the FAQs and Troubleshooting sections of the guide. For the stage where it flashes the downgraded emunand to sysnand, all steps involve a file integrity check BEFORE it continues, and the LAST thing it will do is attempt to flash the 2.1 dump to sysnand (which is actually the step that is least likely to screw up as long as all other steps went smoothly, and its impossible for the program you are using to get there unless everything else checks out.

I wish you luck in the rest of the endeavor as I am going to be hitting the sack soon and will be out of town tomorrow. If you get stuck or have any issues feel free to PM me or ask here, just know I probably won't be able to respond until around 7 or 8pm CDT (it is currently 12:12am CDT, for reference).

 

[CrispyYoshi]

Going off the context of the posts in the thread, maybe it was a typo and he meant to say "non-XL N3DS"? Either way it sounds like the reason its recommended not to update your a9lh sysnand with gateway (lack of FIRM protection) is the very reason we CAN update with sysupdater inside Gateway Mode now. I imagine the only reason for the warning in the A9LH threads is because the lack of protection would result in a potentially broken firm because of A9LH. In the case of someone on 8.1J, that wouldn't be an issue at all. Thanks for the info.

Indeed, I was referring to a "non-XL N3DS," and it's a bit unfortunate given I happened to make a typo on such an important post. In any case...

Yes, I can confirm that updating the system via System Settings in Gateway via A9LH will result in a brick using 4.0b and it will also uninstall A9LH. Thankfully my system also happens to be hardmodded, so I easily got out of the situation via hardmod NAND restore. I can't confirm (or more accurately, haven't tried) to update it through other versions of GW's Launcher.dat. It's completely safe to update via Luma and use Gateway via A9LH on the updated-through-Luma-NAND.

 

[Aroth]

Indeed, I was referring to a "non-XL N3DS," and it's a bit unfortunate given I happened to make a typo on such an important post. In any case...

Yes, I can confirm that updating the system via System Settings in Gateway via A9LH will result in a brick using 4.0b and it will also uninstall A9LH. Thankfully my system also happens to be hardmodded, so I easily got out of the situation via hardmod NAND restore. I can't confirm (or more accurately, haven't tried) to update it through other versions of GW's Launcher.dat. It's completely safe to update via Luma and use Gateway via A9LH on the updated-through-Luma-NAND.

Good to know, and thanks for the clarification and testing.

I would venture that attempting to update an A9LH sysnand with Gateway on any version would result in a brick, since I suspect the FIRM protection they used in 3.x and the one used by A9LHv2 are different implementations. From what I understand, the old Gateway FIRM protection was a byproduct of the way they redirect reads from FIRM. This prevented system updates from writing to FIRM0/FIRM1 and thus would not install the updated native_firm. Since we can safely update the entire firmware with Luma and A9LH but without overwriting/lose A9LH, and it still updates native_firm, I would guess that the FIRM protection used by A9LHv2 simply protects the portion of FIRM0/FIRM1 where the exploit is installed.

 

[codezer0]

Okay, I got to the point where my O3DS XL is successfully downgraded to 2.1.0.

Now, it's telling me to go ahead and copy the emunand_original backups that I previously made as following this guide. Would this be where I'd mod things up by instead bringing in the emuNAND that I've been using (and all updated and everything) from my GW 3DS setup? Or should I hold off on that until after the A9 is set up and running?

 

[Aroth]

Okay, I got to the point where my O3DS XL is successfully downgraded to 2.1.0.

Now, it's telling me to go ahead and copy the emunand_original backups that I previously made as following this guide. Would this be where I'd mod things up by instead bringing in the emuNAND that I've been using (and all updated and everything) from my GW 3DS setup? Or should I hold off on that until after the A9 is set up and running?

Can you link me to the exact section and step number you last completed?

 

[Hayleia]

Okay, I got to the point where my O3DS XL is successfully downgraded to 2.1.0.

Now, it's telling me to go ahead and copy the emunand_original backups that I previously made as following this guide. Would this be where I'd mod things up by instead bringing in the emuNAND that I've been using (and all updated and everything) from my GW 3DS setup? Or should I hold off on that until after the A9 is set up and running?

If by "copy" you mean "copy to the SD card", then do it now or later, it doesn't matter. The thing that matters is the moment when it tells you to restore the backups you previously copied since that's when you want to restore them to the right place. And what you want is logical: emuNAND to emuNAND, sysNAND to sysNAND (instead of emuNAND to sysNAND and remove emuNAND).

 

[codezer0]

Can you link me to the exact section and step number you last completed?

Section 1, step 15, specifically. I was looking at the final step, where it wants me to bring emuNAND_original from Part IV of the guide.

Keep in mind, my ultimate goal is to continue using my existing GW emuNAND,in large part because that's where everything that matters (to me) is installed. I already have that emuNAND file backed up. It just doesn't have the .sha file that was created for the others in this. Would that be a problem?

 

[Aroth]

If by "copy" you mean "copy to the SD card", then do it now or later, it doesn't matter. The thing that matters is the moment when it tells you to restore the backups you previously copied since that's when you want to restore them to the right place. And what you want is logical: emuNAND to emuNAND, sysNAND to sysNAND (instead of emuNAND to sysNAND and remove emuNAND).

Actually since he is working with a second SD card for the installation, he would need to restore the sysnand_original.bin to sysnand, AFTER installing runing SafeA9LHInstaller, and then copy the relevant Luma3DS and gateway files to his old sd card.

Section 1, step 15, specifically. I was looking at the final step, where it wants me to bring emuNAND_original from Part IV of the guide.

Keep in mind, my ultimate goal is to continue using my existing GW emuNAND,in large part because that's where everything that matters (to me) is installed. I already have that emuNAND file backed up. It just doesn't have the .sha file that was created for the others in this. Would that be a problem?

Ok go ahead and follow what I posted here. That post will direct you on what to do differently in the next few steps. The main difference for YOU specifically is you don't need to worry about restoring any emunand backups since you are working with a second SD card for the installation. So just copy sysnand_original.bin to the SD card you are working with and when prompted by Plailect's guide, restore that one WITH HOURGLASS9. I literally CANNOT stress enough that you do the restoration with hourglass9 and NOT decrypt9. Decrypt9 will overwrite the entire NAND chip, including the A9LH exploit. Hourglass9 leaves the A9LH data intact.

When you are done and ready to set up Gateway, make sure that the SD card you have your games and emunand on has all of the files/folders shown in the screenshot on Plailect's guide, plus the Launcher.dat file from the 4.0b release from Gateway. The "luma" folder should have the same files as the screenshots in this post.

Spoiler: Folder screenshots

The "down_v2gw.bin" is a renamed copy of the "arm9loaderhax.bin" file from the link in the short tutorial post I linked above, and "gateway.bin" is a renamed copy of the "arm9loaderhax.bin" file from Gateway's beta releases page. All other files are ones that Plailect's guide had you download and install.

--------------------- MERGED ---------------------------

Btw, the steps in Plailect's guide involving DspDump and NTR might optional for you. I would skip them unless you plan to use things like RetroArch (a homebrew emulator that needs the dumped dsp files) or you plan to use the NTR cfw stuff.

If you plan to use a lot of homebrew or experiment with a lot of them, I would go ahead and dump the DSP files, but make sure you do it after you are back on your normal SD card so that the files are where they need to be.

As for NTR, the only real use for it anymore that I know of is screenshots, streaming and potentially the cheat plugins (though when using Gateway, why bother with NTR's cheat system).

 

[GerbilSoft]

What's upsetting already, is that this process has already corrupted the archive of pictures I had from my Digital camera. While it's true I had most of them mirrored up on Facebook, losing 700+ 14MP photos really sucks.

You might be able to recover some of them using PhotoRec.

 

[codezer0]

Actually since he is working with a second SD card for the installation, he would need to restore the sysnand_original.bin to sysnand, AFTER installing runing SafeA9LHInstaller, and then copy the relevant Luma3DS and gateway files to his old sd card.




Ok go ahead and follow what I posted here. That post will direct you on what to do differently in the next few steps. The main difference for YOU specifically is you don't need to worry about restoring any emunand backups since you are working with a second SD card for the installation. So just copy sysnand_original.bin to the SD card you are working with and when prompted by Plailect's guide, restore that one WITH HOURGLASS9. I literally CANNOT stress enough that you do the restoration with hourglass9 and NOT decrypt9. Decrypt9 will overwrite the entire NAND chip, including the A9LH exploit. Hourglass9 leaves the A9LH data intact.

When you are done and ready to set up Gateway, make sure that the SD card you have your games and emunand on has all of the files/folders shown in the screenshot on Plailect's guide, plus the Launcher.dat file from the 4.0b release from Gateway. The "luma" folder should have the same files as the screenshots in this post.

Spoiler: Folder screenshots

The "down_v2gw.bin" is a renamed copy of the "arm9loaderhax.bin" file from the link in the short tutorial post I linked above, and "gateway.bin" is a renamed copy of the "arm9loaderhax.bin" file from Gateway's beta releases page. All other files are ones that Plailect's guide had you download and install.

--------------------- MERGED ---------------------------

Btw, the steps in Plailect's guide involving DspDump and NTR might optional for you. I would skip them unless you plan to use things like RetroArch (a homebrew emulator that needs the dumped dsp files) or you plan to use the NTR cfw stuff.

If you plan to use a lot of homebrew or experiment with a lot of them, I would go ahead and dump the DSP files, but make sure you do it after you are back on your normal SD card so that the files are where they need to be.

As for NTR, the only real use for it anymore that I know of is screenshots, streaming and potentially the cheat plugins (though when using Gateway, why bother with NTR's cheat system).

So... just to be sure. For Step 16, the immediate next step, which asks for emunand_original.bin/sha, do I use the freshly created .bin/sha? Do I try to use my Gateway Emunand? Would it care if I had the GW emunand without a .sha? That's where I'm currently confused.

 

[codezer0]

Anyone?

 

[Temptress Cerise]

Anyone?

If you don't have a .sha it just won't be able to fully verify it's a good NAND backup. The .sha feature was introduced in all of d0k3's tools as an extra layer of security. Previous versions of the guide and tools didn't have this, so it's not absolutely necessary.

 

[codezer0]

If you don't have a .sha it just won't be able to fully verify it's a good NAND backup. The .sha feature was introduced in all of d0k3's tools as an extra layer of security. Previous versions of the guide and tools didn't have this, so it's not absolutely necessary.

But, again, which one do I use? the one generated for this whole install process? Or the emuNAND.bin from my GW with all my legit profile and installs and stuff?

 

[Temptress Cerise]

But, again, which one do I use? the one generated for this whole install process? Or the emuNAND.bin from my GW with all my legit profile and installs and stuff?

On an A9LH setup with SysNAND only, you want to restore the one that is going to be your main...

 

[codezer0]

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?