Hacking [Q] Load Gateway menu without CN and still keep DS functionality

  • Thread starter Thread starter NEO117
  • Start date Start date
  • Views Views 1,647
  • Replies Replies 5

NEO117

Well-Known Member
Member
Joined
Mar 5, 2008
Messages
316
Reaction score
77
Trophies
1
XP
543
Country
Venezuela
I got my Gateway3DS yesterday, did everything that needed to be done and I setup my emunand. Then I installed the mset exploit so I could boot into the gateway menu without CN, however I also want to be able to use my bluecard without losing said exploit. I know this isn't possible atm but what alternatives do I have. I was thinking of the following...

1. Install CN as a .cia and use that without having to swap the cart.
2. Some way to boot to GW menu from the Blue card (very doubtful...).
3. Install Dev Menu as .cia and just reinstall mset from sysnand.

Any ideas?
 
I got my Gateway3DS yesterday, did everything that needed to be done and I setup my emunand. Then I installed the mset exploit so I could boot into the gateway menu without CN, however I also want to be able to use my bluecard without losing said exploit. I know this isn't possible atm but what alternatives do I have. I was thinking of the following...

1. Install CN as a .cia and use that without having to swap the cart.
2. Some way to boot to GW menu from the Blue card (very doubtful...).
3. Install Dev Menu as .cia and just reinstall mset from sysnand.

Any ideas?
The issue is that when you first start the system, sysNand is in charge. When sysNand is in charge, it checks for signatures and only allows valid items to run. This means you wouldn't be able to use a .cia version of CN or run DevMenu in sysNand. Without Nintendo's private keys to sign software, we can't yet create software that will run on a freshly started sysNand. (Installing mset.cia is done by running DevMenu in sysNand with Gateway Mode enabled, which is a patch that disables signature checks, among other things.)

As far as losing the exploit, the only thing lost is the NVRAM Profile, which can be reinstalled using GW_INSTALLER.nds on the blue card, so your idea #2 is the closest to your best option. After you're done playing games with your blue card, just run GW_INSTALLER.nds, and then you're back in business. mset.cia does not have to be installed again.
 
The issue is that when you first start the system, sysNand is in charge. When sysNand is in charge, it checks for signatures and only allows valid items to run. This means you wouldn't be able to use a .cia version of CN or run DevMenu in sysNand. Without Nintendo's private keys to sign software, we can't yet create software that will run on a freshly started sysNand. (Installing mset.cia is done by running DevMenu in sysNand with Gateway Mode enabled, which is a patch that disables signature checks, among other things.)

As far as losing the exploit, the only thing lost is the NVRAM Profile, which can be reinstalled using GW_INSTALLER.nds on the blue card, so your idea #2 is the closest to your best option. After you're done playing games with your blue card, just run GW_INSTALLER.nds, and then you're back in business. mset.cia does not have to be installed again.

Thank you. :)
 
I got my Gateway3DS yesterday, did everything that needed to be done and I setup my emunand. Then I installed the mset exploit so I could boot into the gateway menu without CN, however I also want to be able to use my bluecard without losing said exploit. I know this isn't possible atm but what alternatives do I have. I was thinking of the following...

1. Install CN as a .cia and use that without having to swap the cart.
2. Some way to boot to GW menu from the Blue card (very doubtful...).
3. Install Dev Menu as .cia and just reinstall mset from sysnand.

Any ideas?


^^ Do this, you'll be able to run your NDS games w/o losing the ability to boot into gateway from profile.
 

Site & Scene News

Popular threads in this forum