Hacking GW addon for Luma + GW

  • Thread starter Thread starter Billy Acuña
  • Start date Start date
  • Views Views 2,997
  • Replies Replies 10
  • Likes Likes 2

Billy Acuña

Well-Known Member
Member
Joined
Oct 10, 2015
Messages
3,130
Reaction score
2,164
Trophies
2
Age
33
XP
3,901
Country
Mexico
Hello.

I made a boot setup to boot Luma + GW for no-screeninit users.

Basically I made this because I don't like BootCtr9 as boot manager because it makes a annoying flash on the screen when it boots, not like arm9select or Luma's chainloader (which is based on arm9select), sadly none of both has build-in screeninit code, but BootCtr9 does.

So what I made to avoid that awful flash and avoid the Luma's path setter, I put Luma's payload as my main arm9 payload (arm9loaderhax.bin), load BootCtr9 from Luma's chainloader with D-Pad Left, BootCtr9 looks for GW's payload from somewhere and GW's payload looks for launcher.dat from the root.

This is nothing mayor and none of this is my work but hope this setup might useful to someone :)

You need the arm9loaderhax.bin payload from Luma and launcher.dat from GW (I recommend 4.0a because it doesn't have the annoying sysnand nag) in the root, is highly recommend to use Quick Reboot to easily swith between Luma to GW and viceversa.

DON'T UPDATE ON SYSNAND GW MODE, update your sysnand on Luma always.

Link: https://mega.nz/#!yhYCUZbQ!sq4o5mfL84HMnxpZC1n4zDiJ8TWunNzO3QRQlMhm2e0
 
Last edited by Billy Acuña,
Good job!

Only thing, I recommend that you remove the Launcher.dat ASAP, because it contains copyrighted stuff and the mods here will likely remove it when they see it.
 
Good job!

Only thing, I recommend that you remove the Launcher.dat ASAP, because it contains copyrighted stuff and the mods here will likely remove it when they see it.
Ohh, don't knew that GW uses copyrighted stuff, or his code is alreally copyrighted since is freeware. Let me fix that.
 
Hey ! I just discovered this post, as i just updated my a9lh sysnand with GW :/ (Yeah, I know, I screwed up). Now, it seems like I don't have a9lh anymore (can't load any arm9loaderhax.bin). Do you know if there's any solution (but hardmod) ?
Thank you !
 
Hey ! I just discovered this post, as i just updated my a9lh sysnand with GW :/ (Yeah, I know, I screwed up). Now, it seems like I don't have a9lh anymore (can't load any arm9loaderhax.bin). Do you know if there's any solution (but hardmod) ?
Thank you !
If you are now on 11.0.0-33 and you updated while on GW mode, you are now on the latest OFW. You will need a hardmod. At this current moment there is no other solution. Sorry.
 
If you are now on 11.0.0-33 and you updated while on GW mode, you are now on the latest OFW. You will need a hardmod. At this current moment there is no other solution. Sorry.
Well, at least now, i'm know what i have to do ! I'll try to find someone to do it for me. Thank you very much ! I hope GW will communicate a bit about that, so that people don't get stuck too :/
 
Well, at least now, i'm know what i have to do ! I'll try to find someone to do it for me. Thank you very much ! I hope GW will communicate a bit about that, so that people don't get stuck too :/
4.0b warns you when you try to boot into sysNAND. They also have this disclaimer on their openly public Private Beta Program:
"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!"

As far as they're concerned, it's not their fault.
 
4.0b warns you when you try to boot into sysNAND. They also have this disclaimer on their openly public Private Beta Program:
"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!"

As far as they're concerned, it's not their fault.
Yeah, i know, I don't wanna blame them, I know it's my fault. I just thought they could have warned people not to upgrade a9lh sysnand with GW CFW (while it is possible with Luma).
 
Yeah, i know, I don't wanna blame them, I know it's my fault. I just thought they could have warned people not to upgrade a9lh sysnand with GW CFW (while it is possible with Luma).
They do... and did... If the nag wasn't enough, they also explain it in their changelog.

GATEWAY 4.0 BETA CHANGELOG (20160601)
  • Time Machine compatibility and stability fixes
  • GATEWAY Menu compatibility and stability fixes
  • Rename ‘Nintendo 3DS’ folder to 3DS_BAK (N3DS)
  • Add warning/nag screen when A9LH user tries to boot into sysNAND (to prevent accidentical sysNAND updates)
  • [Time Machine won’t allow 9.x to 2.x downgrade on O3DS (Must upgrade to 10.x first, then go down to 2.x)

Then there are the multiple people on here who keep telling others not to update in GW mode, even with the 3.7.1 Launcher.dat.
 
They do... and did... If the nag wasn't enough, they also explain it in their changelog.

GATEWAY 4.0 BETA CHANGELOG (20160601)
  • Time Machine compatibility and stability fixes
  • GATEWAY Menu compatibility and stability fixes
  • Rename ‘Nintendo 3DS’ folder to 3DS_BAK (N3DS)
  • Add warning/nag screen when A9LH user tries to boot into sysNAND (to prevent accidentical sysNAND updates)
  • [Time Machine won’t allow 9.x to 2.x downgrade on O3DS (Must upgrade to 10.x first, then go down to 2.x)

Then there are the multiple people on here who keep telling others not to update in GW mode, even with the 3.7.1 Launcher.dat.
Hmm, my bad. :bow:
 

Site & Scene News

Popular threads in this forum