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

  • Thread starter Thread starter Traiver
  • Start date Start date
  • Views Views 109,840
  • Replies Replies 695
  • Likes Likes 12
so guys i have a9lh with luma and im on latest sysnand with no emunand............
if i use gateway card, all i have to do is copy the a9lh.bin by GW?
 
so guys i have a9lh with luma and im on latest sysnand with no emunand............
if i use gateway card, all i have to do is copy the a9lh.bin by GW?
Yes, but if you're using a no-screen-init branch of a9lh it won't work with luma (dont worry about this if you followed plailect's guide in the past month or so.)
 
I think some people have said that you can use bootctr9 if you're not using the screen_init version.

I use Three Stage 2 as my A9LH and this boots Gateway A9LH fine.
 
so guys i have a9lh with luma and im on latest sysnand with no emunand............
if i use gateway card, all i have to do is copy the a9lh.bin by GW?

Pretty much. Some people have trouble getting it to work with Luma. You can always try another boot manager if it happens to you. I've uploaded all boot managers pre-configured to run everything if you're interested (Luma included).

I think some people have said that you can use bootctr9 if you're not using the screen_init version.

I use Three Stage 2 as my A9LH and this boots Gateway A9LH fine.

Yeah, BootCTR9 will run GW with no init. For some reason it brroke my CBM9 "leftovers" menu though (just not practical to hotkey everything after all). So I went back to the old screen init. Just seems to be the most compatible. I'm sure Three Stage 2 would work fine too, but I don't need a third boot manager atm (chaining CBM9 for the stuff I don't use every day works fine).
 
Last edited by Kazuma77,
thanks ill give it a try.

Almost forgot to mention, there's a more complete upload on that iso site if you're a member. It's in the "CFW Discussions" forum. Has all the CFW folders, with everything (including the optional firmware.bin files). Complete drag and drop setup, copy it over and everything is ready to run (you still have to perform initial configuration of Luma and Cakes though -- I don't try to guess what people want enabled).
 
Last edited by Kazuma77,
Yes, but if you're using a no-screen-init branch of a9lh it won't work with luma (dont worry about this if you followed plailect's guide in the past month or so.)

I have a no screen init payload. Can you point me to the most up to date payloads? Just install with SafeA9LHInstaller?
 
I recommend Three Stage 2. With this, you can boot an alternative payload (such as GW) just by holding X+Y.

https://gbatemp.net/threads/release-three-stage-2.429303/
No, this is a bad idea now that GW has released an arm9loaderhax.bin.

I have a no screen init payload. Can you point me to the most up to date payloads? Just install with SafeA9LHInstaller?
Use these payloads with safea9lhinstaller: https://mega.nz/#!nRYlDTCQ!xsQJoY1VvZnhHVK68IZH1gVVCTt6EJdIRjD7J323gYE
 
  • Like
Reactions: Lush
No, this is a bad idea now that GW has released an arm9loaderhax.bin.

Why? The latest version of Three Stage 2 has ditched support for launcher.dat in favour of three different arm9loaderhax.bin, puirely because of Gateway's arm9loaderhax.bin release.
 
Why? The latest version of Three Stage 2 has ditched support for launcher.dat in favour of three different arm9loaderhax.bin, puirely because of Gateway's arm9loaderhax.bin release.
this is something I feel a boot manager (like BootCTR9) should be doing, instead of a payload in NAND booting several different payloads, creating an unusual setup.
 
  • Like
Reactions: astronautlevel
No, this is a bad idea now that GW has released an arm9loaderhax.bin.


Use these payloads with safea9lhinstaller: https://mega.nz/#!nRYlDTCQ!xsQJoY1VvZnhHVK68IZH1gVVCTt6EJdIRjD7J323gYE

Thank you for your quick reply and all your contributions here. You are a tremendous help to the community. I currently use Luma/A9LH on my O3DS, 2DS, and N3DS. I can just flash these new payloads to each unit and then add r_gw.bin to the Luma payload folder to boot into gateway when desired? I still want to use Luma as my default...
 
Thank you for your quick reply and all your contributions here. You are a tremendous help to the community. I currently use Luma/A9LH on my O3DS, 2DS, and N3DS. I can just flash these new payloads to each unit and then add r_gw.bin to the Luma payload folder to boot into gateway when desired? I still want to use Luma as my default...
Yes, that should work :)

Use safea9lhinstaller from a9lh to flash the payload_stage1 and payload_stage2 that I provided in that link.

Also, thanks for your kind words, it means a lot :wub:
 
  • Like
Reactions: Lush
How do I configure my wifi?

I had configure it in sysnand but when I boot it, it still ask me to configure my wifi.
 
Already done that but it still give me "fatal error: please configure wifi before downgrade".
Oh, this is GW's time machine? It's... really buggy about that to say the least. I remember @ihaveamac was testing with it and couldn't get past that error, not sure if that changed.

You'd probably be better off using PlaiSysUpdater to downgrade, it's better tested and probably safer. What are you downgrading to?
 
  • Like
Reactions: samiam144
Oh, this is GW's time machine? It's... really buggy about that to say the least. I remember @ihaveamac was testing with it and couldn't get past that error, not sure if that changed.

You'd probably be better off using PlaiSysUpdater to downgrade, it's better tested and probably safer. What are you downgrading to?
I follow the fist page guide. Is there any other guide that safer?
 
is there anyway to use other names with the bin files instead of y.bin i could use say luma_y.bin.

Arm9 works fine for me but I am having trouble reading which is bloody which as theres so many of them.

I think the payload has to be y.bin, but I will try an edit to see if it works. I keep my payloads straight by making a txt file in my payloads folder listing which payload is which (y.bin = Luma3DS) for quick reference.


Edit: I edited arm9select for my setup and it works. My setup is CFW.bin = default (ReiNand), GW_l.bin, Luma3DS_r.bin, Decrypt9WIP_select.bin and Uncart_start.bin.


If you would like me to edit for you just provide the payload names you desire with the button you would like it assigned to. Hope this helps.
 
Last edited by Deleted member 117573,
Emailed GW concerning launcher.dat size and menu options:

Capture.PNG


Just seems that 8 MB for the launcher.dat and NVRAM install, Downgrade console and A9LH installer are not needed after your 3DS/2DS is setup to your desired entrypoint.
 

Site & Scene News

Popular threads in this forum