Hacking GATEWAY 4.1 PRIVATE BETA RELEASE

  • Thread starter Thread starter Swiftloke
  • Start date Start date
  • Views Views 39,307
  • Replies Replies 299
  • Likes Likes 5
It is actually faster using freeShop - don't forget about the time spent trawling through that iso site, putting up with millions of ads and malware, and often ending up with a bad link, or a link that requires you to sign up to something you don't want to, or a link that only downloads at 1kb/sec unless you pay money to register, or a link that puts you through multiple adf.ly links that make you wait, or a link that actually contains something different than advertised. Plus time spent copying over the file and troubleshooting when it won't work because of fragmentation or whatever. On freeShop, takes 2 seconds to find the game you want: open the app, type the name, click download, done.

So it's faster, only once you add the same excuses a lot of people do "that iso site, slow downloads, time taken to copy if you use a potato sd reader"

That iso site is not the sole souce on the internet for roms. I don't use it. Even with the time taken to copy across to sd card, freeshop is still slower for me due to Nintendo's servers never maxing my connection. Always get stuck at 3MB/s or so, while I can grab .3ds at nearly 3 times the speed (8.6MB/s).

Such an awful arguement anyway. .3ds are slower if X, Y and Z problem happens. Would it be fair for .3ds users to say freeshop is shit because of shitty wifi on the 3ds and slow Nintendo servers or would that suddenly be "not everyone has that issue".
 
Last edited by Armadillo,
  • Like
Reactions: Nightwish
I don't care that my console gets married with the GW as long the card don't fails, how many possibilities are of gw red card dead? Maybe the same of the 3ds sd reader? I haven't hear many cases of dead red card, blue card yes, on my ds I have an acekard 2I working for years to date and without problems.
 
Woo Gateway :P, still trying to figure out how to get you to work with luma.
Hey, I owe you one for mentioning the update on the 4.0 beta page :) that's what got me to write this. I've mentioned you in the OP.
February 2016, and it was with RxTools 2.7, which was supposedly the latest "safe" version I could get. Considering both RL friends and people on this very forum were recommending it, that's what I went with, and then nobody wanted to help with why nothing was working. So, I got fed up and scrubbed it from my SD card.
IwoJS3l.png
 
I can imagine it being super tedious, long and boring to do, but what's really needed here is a noob-friendly extensive, step-by-step A9LH install guide specific for GW users, which assumes user starts with 9.2 SYS and 10.x or 11.x EMU (should cover 90% of GW owners) and wants to keep all his shit.

Until then, all new GW beta threads will be the same:
"don't install GW A9LH version it sucks and makes red card mandatory"
"sure ok but the other install method (Plailect) is complex as hell, I don't know where the fuck I am"

If a dev or advanced user has some time and knows 100% what he's doing, a dedicated GW guide would be the best solution (i'm sadly not that dude).

But plailect's guide is perfectly fine to follow even when you are a gateway user on sys 9.2 und emu 11.0.
All you have to do is start following the guide from step 3 and you are good to go. I know this because thats excatly what I
have done. I was on Sys 9.2 Emu 11.0 with Gateway and now I'm on Luma 11.0 with my former Emunand as my Sysnand and can boot into
Gateway sysnand mode if I want to use my red card.

What I think the problem is that people have the misconception of GW Emunand ≠ CFW. But in reality, you have an image of
your orignal nand on your sd card and depending on which launcher you use, you end up with a different cfw. If you would to launch
a Gateway emunand the a luma launcher, you would end up with luna cfw. Boot up the gateway emunand and you have the gateway cfw.
 
Last edited by Essometer,
  • Like
Reactions: Lnkcld
Can i install the autoboot without red card in A9LHv2?

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

Can i install the autoboot without red card in A9LHv2?
LOL. It requires a red card for booting in GW mode... When i press "B", the "No red card found" reappears. I will try now with the card... (It can be only the first time?)

Finally, i ended testing. It requires the red card for everything, as always. Autobooting requires red card, if you wait and dont do the L+Select combo, you will be stuck in the "enter red card" screen, and if you want to do anything, you must put a red card or plug off the console. If you enter GW menu with the combo, GW mode wont work and classic mode says that you can try it without the card, as always in >8.x.
I didnt imagine ever Gateway lying, but this time, they did it.
 
Last edited by yacepi15,
I can imagine it being super tedious, long and boring to do, but what's really needed here is a noob-friendly extensive, step-by-step A9LH install guide specific for GW users, which assumes user starts with 9.2 SYS and 10.x or 11.x EMU (should cover 90% of GW owners) and wants to keep all his shit.

Until then, all new GW beta threads will be the same:
"don't install GW A9LH version it sucks and makes red card mandatory"
"sure ok but the other install method (Plailect) is complex as hell, I don't know where the fuck I am"

If a dev or advanced user has some time and knows 100% what he's doing, a dedicated GW guide would be the best solution (i'm sadly not that dude).

Assuming you want to keep a 9.2 sysnand and an updated emunand to use with gateway, the following are the only real changes beyond what Plailect has you do:

  1. Follow his guide up to Part 5, Section I, Step 16. When asked to copy emunand_original.bin and emunand_original.bin.sha to your SD card, you should also copy sysnand_original.bin and sysnand_original.bin.sha as well.
  2. Continue the guide until Part 5, Section III, Step 2. When turning on settings for Luma3DS, leave "Autoboot SysNAND" and "Updated SysNAND" turned off.
  3. In Part 5, Section IV, Step 4, when asked to confirm and restore from "emunand_original.bin", do not do so. Instead confirm and restore from "sysnand_original.bin". This will give you your 9.2 sysnand back while leaving A9LH intact.**
  4. Next go to "EmuNAND Backup/Restore..." and select "EmuNAND Restore". Confirm and restore from "emunand_original.bin". This will restore your original emunand with all its games/saves/etc that you made a backup of at the start of the guide.**
  5. Skip Step V entirely as you do not want to remove rednand/emunand from your system.
  6. Complete Step VI as it is having you make a backup of the A9LH enabled sysnand for future recovery if needed.
** It is imperative that you ONLY use hourglass9 (and not decrypt9) to restore sysnand at this step. If you use decrypt9 YOU WILL LOSE A9LH.

At this point you have a system with a 9.2 sysnand with A9LH, and an updated emunand for use with Gateway. To access Gateway you would need to do the following:

  1. Download the 4.0b files from the gateway website (do not download 4.1b at this time as I am unaware if they work with the prexisting arm9loaderhax.bin file from Gateway). Place "launcher.dat on the root of your sd card (as always).
  2. Download the arm9loaderhax.bin.zip file from Gateway's website and extract the arm9loadhax.bin file, rename it to gateway.bin and place it in "sd:\luma\payloads\".
  3. Go here and download "v2gw.zip".
  4. Extract the arm9loadhax.bin file and rename it to "<button>_v2gw.bin", where <button> is the key you wish to use for loading Gateway according to the list here.
  5. Place the renamed file in "sd:\luma\payloads".

Now when you boot the console it will load Luma3DS on the emunand partition if you do not press any buttons, and if you press the button(s) you set up for Gateway it will load Gateway on the emunand partition.

If someone with more experience sees any issues or mistakes (beyond the fact that using a 9.2 sysnand and updated emunand is a depreciated system configuration), please feel free to correct me.

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

Just a heads up for those who still want to know, the launcher.dat file from 4.1b does NOT work with the existing arm9loadhax.bin file provided by gateway last month. Just tried loading it and got a blackscreen. Restoring the launcher.dat from 4.0b restored access to Gateway Mode.

That said the only real change in the launcher.dat that should affect existing users (those not needing to mess with the "time machine" crap) is the new "Menu Lockout" feature that requires holding "L+Select" to access the GW Menu.
 
Last edited by Aroth,
I like the kangaroo reference. If that's the main risk with A9LH, most everyone in the world is safe, except unlucky australians. :lol:
Haha yep, wrote that without thinking. You guys probably have deer and moose though (do they also hide in bushes by the side of the road and then spring out in front of vehicles at the precise moment that it's too late to brake?)
 
Haha yep, wrote that without thinking. You guys probably have deer and moose though (do they also hide in bushes by the side of the road and then spring out in front of vehicles at the precise moment that it's too late to brake?)
Yes, hitting a moose can cause a serious accident. The government even built fences alongside the road in a national park to prevent that from happening.
 
if there was a way to have luma a9lh and use my gateway card without emunand id be all set. Just waitin on a sky to hack my n3ds 8.1J
 
if there was a way to have luma a9lh and use my gateway card without emunand id be all set. Just waitin on a sky to hack my n3ds 8.1J

There is.... just follow the Plailect guide 100%, then go to https://gbatemp.net/threads/tutorial-using-luma3ds-with-gateway-on-v2-a9lh.431691/ and follow the directions in that tutorial. You will have an updated sysnand (11.0) with a9lh and all of the games and saves that were on your emunand, recovery tools (decrypt9, hourglass9) and the ability to load GW mode on said sysnand to use the red cart.

Only thing is do NOT download the 4.1 files. Just the 4.0b files because the 4.1 launcher.dat will not load using the existing arm9loadhax.bin file we have for gateway.
 
  • Like
Reactions: Quantumcat
What is all this waiting for? Just to make a9lh work with Gateway's flashcard basically? Or is there something else that GW offers? I don't get it.
 
id rather wait on that one...

Just saw you had an 8.1J system. That would be a bit of a problem lol. Pretty sure that was the devil firmware that caused all the problems originally when we first started messing with the N3DS

Wait on what?


Suspect he is concerned about hacking a system on 8.1J. Wasn't that the firmware that was causing all the problems last year cuz no entrypoint worked right with it?
 

Site & Scene News

Popular threads in this forum