Hacking [RELEASE] GATEWAY 4.0 BETA (Private Beta Program)

  • Thread starter Thread starter Traiver
  • Start date Start date
  • Views Views 109,824
  • Replies Replies 695
  • Likes Likes 12
I was asking the question why can gateway and a few select card makers load .3ds and cfw cant, not interested in bickering on which is better.
 
I was asking the question why can gateway and a few select card makers load .3ds and cfw cant, not interested in bickering on which is better.
I don't think it's because they can't, but because they have to be loaded with a flashcard (Sky3DS or Gateway) or another hardware I am not aware of. Most of CFW creator make them to be 100% free, so no external hardware. I would love to see the gateway menu booting on Luma, but it is not their priority. I also prefer .3ds, since installing .CIA takes much more time for me and I inject my own headers only on game that I'll use multiplayer (so not many of them, plus injecting takes literally 2 minutes). The advantage of .3DS is that I don't pirate my game (I don't want to start a debate on piracy please), so I do my own backup, which are .3DS by default. Converting them to .CIA and then installing them is WAY longer than injecting a header.
 
No that's only for access through the Homebrew Launcher (Menuhax, browserhax, etc.).
Actually, it's Time Machine, isn't it? My brain is fried at the moment (towards the end of a work day with a 21 hour day yesterday and <4 hours of sleep in-between), but I'm pretty sure that following GW's guide, Time Machine either loads via GW red card, or directly with browserhax/menuhax (not via HBL at all).

boots Luma by default, boots a shutdown payload when L is held down (so no one can get to sysNAND)
I hope you realize that you don't need to hold L while powering on. I bet you I can press L as soon as the screen changes, and get to the GW menu -> sysnand just as easy as any other console. Once it starts to load the GW payload, that's it. There's enough of a delay there...

I don't see why private headers in a cfw or on a flash card would make any difference whatsoever, it seems me that no one knows how to do it. I'm just wondering why it hasn't been done yet...
.3ds is a cart image. 3DS runs carts from the slot. No matter what, you have to run it from the slot (so you MUST have hardware that stores the image in the slot, that the 3DS system can read from and write to.
.cia is an installable archive. Think of it as a .zip file containing the contents (files) from the game, not an exact image of a cart.
 
Last edited by urherenow,
  • Like
Reactions: mijuu
I think a vast majority don't know what Beta's actually are, the risks involved, and the stability overall.

Also, it appears a lot will put their faith into GW who dont provide tech support than actually listening to users on temp, since following P's guide is a lot safer, if followed correctly and people are willing to help, which has already been mentioned in this thread.

I have seen a lot more jump the gun on gw's 4.0b without hard mods, yet the same ones freaked out wanting to avoid the current more superior a9lh install previously. I know which one I'd go for.
 
Last edited by retrofan_k,
I think a vast majority don't know what Beta's actually are, the risks involved, and the stability overall.

Also, it appears a lot will put their faith into GW who dont provide tech support than actually listening to users on temp, since following P's guide is a lot safer, if followed correctly and people are willing to help, which has already been mentioned in this thread.

I have seen a lot more jump the gun on gw's 4.0b without hard mods, yet the same ones freaked out wanting to avoid the current more superior a9lh install previously. I know which one I'd go for.
I am actually starting to get annoyed with those people. Sigh.

Anyways, I am thankful for the hardmod users who have gone ahead and done tests. Like @Kazuma77 for pointing out that Firm0/Firm1 protection is also not there on 3.7.1 Launcher.dat. :)
 
Last edited by Temptress Cerise,
  • Like
Reactions: retrofan_k
I am actually starting to get annoyed with those people. Sigh.

Anyways, I am thankful for the hardmod users who have gone ahead and done tests. Like @Kazuma77 for pointing out that Firm0/Firm1 protection is also not there on 3.7.1 Launcher.dat. :)

Has anyone stress tested the 4.0b dat with a9lh luma? I have stayed away from that at the moment for obvious reasons. Heard they fixed the 3d screen bug, which is good.
 
I think a vast majority don't know what Beta's actually are, the risks involved, and the stability overall.

Gateway calls almost every one of their releases a beta. If you take the "beta" seriously, you'd still be on Gateway 3.4. The only difference in the naming is that they're calling this one private instead of public.
 
Gateway calls almost every one of their releases a beta. If you take the "beta" seriously, you'd still be on Gateway 3.4. The only difference in the naming is that they're calling this one private instead of public.
Oh and this openly public Private Beta has the following disclaimer right on that page.
"DISCLAIMER: Files on this page should be treated with extreme care and only used by advanced users who have access to a way to restore their 3DS NAND. Users should have a valid/known good copy of their NAND before proceeding! Use at your own risk!"

I don't see the other normal beta releases having that. And also, some of us on here are GW users as well, but we are not telling everyone to go out and risk a brick when we know this "private beta" isn't even fully polished.

Yes, GW should take feedback from the advance users and from the users with hardmods, and they should use that feedback to improve their GW-A9LH installer, but by no means should we be pushing people to it. If you have to ask how to use that private beta, chances are you shouldn't even be using it.
 
  • Like
Reactions: Lumince
Actually, it's Time Machine, isn't it? My brain is fried at the moment (towards the end of a work day with a 21 hour day yesterday and <4 hours of sleep in-between), but I'm pretty sure that following GW's guide, Time Machine either loads via GW red card, or directly with browserhax/menuhax (not via HBL at all).
Oh you are probably right; I haven't actually looked into the recent releases so when I saw ".3dsx" I just assumed it was GW.3dsx but renamed.
 
.3ds is a cart image. 3DS runs carts from the slot. No matter what, you have to run it from the slot (so you MUST have hardware that stores the image in the slot, that the 3DS system can read from and write to.
.cia is an installable archive. Think of it as a .zip file containing the contents (files) from the game, not an exact image of a cart.

Aye now that's an answer that actually makes sense, so it's hardware dependent. Couldn't this hardware theoretically be emulated?
 
Aye now that's an answer that actually makes sense, so it's hardware dependent. Couldn't this hardware theoretically be emulated?
I think it would be THEORITICALLY possible, only not on the N3DS (let alone the O3DS). The 3DS do not have enough memory to allocate an entire 3DS emulated hardware on its kernel.
 
It's entirely possible to "emulate t by e slot 1 card the problem is the lack of memory available makes this task much more complicated... Though not impossible. Either way it's simply easier to convert to .cia and know it'll work on CFW...
 
Anyone find out how to fix that "fatal wifi error" thing...?
tbh theres probably like 3 people on here that are actually fully testing this thing. No one else will know because we all dont have hard mods. If you really want a9lh. You probably should go with the less risky Plailect guide :/ Everyone keeps saying this but people insist on using something that shouldnt be released to the public just yet. If you wish to brick keep trying to use the gateway method.
 
I just want to let everyone that's downloaded my Boot Manager Mega Configs in the past know that I've uncovered a problem. Somehow those "no init" A9LH payloads I thought I replaced worked their way back into the archive. Using them will break CBM9 (even the non-CBM9 configurations use it as an "extra stuff" menu, and even if you're using BootCTR9 it will still break that part of the setup). I've uploaded a corrected file that has the "screen init" payloads I thought I was including all along now. So, if you've downloaded them in the past. Please re-download them.
 
  • Like
Reactions: Subtle Demise
Another stupid noob here, have installed arm9loaderhax recently on my n3DS using Plailect's Guide and now trying to start Gateway's arm9loaderhax.bin as payload of Luma3DS and nothing work of course, just black screen, I use 4.0b Launcher.dat and x_GW.bin in payload folder.

Could someone please explain all these things with screen-init / noscreen-init and how to start Gateway's arm9loaderhax.bin as payload, don't want to use boot managers.
 
Another stupid noob here, have installed arm9loaderhax recently on my n3DS using Plailect's Guide and now trying to start Gateway's arm9loaderhax.bin as payload of Luma3DS and nothing work of course, just black screen, I use 4.0b Launcher.dat and x_GW.bin in payload folder.

Could someone please explain all these things with screen-init / noscreen-init and how to start Gateway's arm9loaderhax.bin as payload, don't want to use boot managers.
Try with the 3.7 launcher. If it still does not work, try with left_GW.bin
I don't really understand the screen-init thing, but if you followed Plailect guide, you should not have any problem.
 

Site & Scene News

Popular threads in this forum