Hacking GATEWAY 3.2 ULTRA PUBLIC BETA

  • Thread starter Thread starter TheShadowRunner
  • Start date Start date
  • Views Views 213,801
  • Replies Replies 1,328
  • Likes Likes 24
what the the MSET thing do ?
and NVRAM ?
i only have OG 3DS i downgraded from 9.2 to 4.5
and other 3DS XL in 9.2
No, I don't, I did not mention I had one right?
So is anything possible with Cubic Ninja and a 4.5 3DS with this update?
You both have old3DSes so all you have to do is copy the new launcher.dat and you're good to launch it as you normally would.

All the other stuff is for new3DS users only.

I did that, it worked thanks!

But now i'm thinking, since we don't have emunand, we can't play online? Because i want to play monster hunter online, i have headers and those things, but i'll need to update the game, and to update the game we have to update the e-shop, so, no online?
You only need an SD card without emuNAND for the installation process, you can swap back to your emuNAND SD after you've installed the exploit. Don't forget to copy the new launcher.dat to your emuNAND SD card.
 
  • Like
Reactions: Margen67
Who knows? They actually were the first company (I use the term loosely) to have a new feature, multi-rom, I believe. Maybe they're working on something incredible? I know the odds are low, but they aren't zero.
yeah thats what i mean, it was never a 100% clone more a derivative work with a few odds and ends added into it, but gateway releasing an update doesnt mean MT will, which is what was asked, if it did they would of already released one, there has been about 5 GW updates since the last MT update afaik

EDIT, ok its been 8 GW fw's since the last MT release

funnily enough the DSTWO+ was announced around the same time as MT disappeared :rolleyes:
 
So you can downgrade to 4.5 system menu now on the new 3DS? Any chance we get this for the 2DS? I thought the reason they couldn't do it was because of the removal of the wifi switch. If I don't have to use the browser hack for my 2DS that would be preferable.
 
  • Like
Reactions: Random Joe
Apparently someone found a way to get the DS Profile exploit to stick after running DS games (page 4 of this thread). Nice.


Now if only Gateway would fix the "SuperStable" bug on the N3DS... You currently have to close flip the N3DS every time you launch a 3D game and then flip it open again. Not fun I imagine.

Perhaps my case is odd but the n3ds head tracking function remains after launching gateway without even having to close the lid.


Pay attention:

I think i found a way to fix this issue (3d head tracking being disabled after booting into gateway). You see, when i first launched gateway through the ds profile exploit on my n3ds the head tracking wasn´t functioning (just as it used to when i booted into gateway through cubic ninja), as you know, this is quickly fixed by putting the n3ds into sleep mode (closing and opening the lid). However, i launched the "Quick reboot" app (i installed it as a cia) and after doing that the head tracking remained to function the next time i launched into gateway (even after hard rebooting the n3ds)

Here is a link to the quick reboot thread, test and post your results

https://gbatemp.net/threads/homebrew-quick-reboot-cfw-gateway-ninjhax.379101/
 
I believe the XL's do have a slightly different DS mode, because they allow you to play with 1:1 pixel mapping by holding START or SELECT when entering DS mode.

This isn't different. The regular 3DS lets you do this too, although since the screen is smaller it's going to be harder to see.
 
Perhaps my case is odd but the n3ds head tracking function remains after launching gateway without even having to close the lid.


Pay attention:

I think i found a way to fix this issue (3d head tracking being disabled after booting into gateway). You see, when i first launched gateway through the ds profile exploit on my n3ds the head tracking wasn´t functioning (just as it used to when i booted into gateway through cubic ninja), as you know, this is quickly fixed by putting the n3ds into sleep mode (closing and opening the lid). However, i launched the "Quick reboot" app (i installed it as a cia) and after doing that the head tracking remained to function the next time i launched into gateway (even after hard rebooting the n3ds)

Here is a link to the quick reboot thread, test and post your results

https://gbatemp.net/threads/homebrew-quick-reboot-cfw-gateway-ninjhax.379101/
Did you install quick reboot to sys or emu??
 
Some people used 2 Msd to install the exploit ?
I don't get it.
Is there some advantage to using 2 different cards ?
For me it worked fine with only one.( Jap new 3DS)
 
Perhaps my case is odd but the n3ds head tracking function remains after launching gateway without even having to close the lid.


Pay attention:

I think i found a way to fix this issue (3d head tracking being disabled after booting into gateway). You see, when i first launched gateway through the ds profile exploit on my n3ds the head tracking wasn´t functioning (just as it used to when i booted into gateway through cubic ninja), as you know, this is quickly fixed by putting the n3ds into sleep mode (closing and opening the lid). However, i launched the "Quick reboot" app (i installed it as a cia) and after doing that the head tracking remained to function the next time i launched into gateway (even after hard rebooting the n3ds)

Here is a link to the quick reboot thread, test and post your results

https://gbatemp.net/threads/homebrew-quick-reboot-cfw-gateway-ninjhax.379101/

didnt work for me
 
I had the same problem and I used another micro sd and it worked, check below :

1) Copy the mset cia for your region to the INTERNAL microSD of your N3DS.
2) Get a spare microSD and format it.
3) Copy launcher.dat to the root of both the new microSD and the one you're using in your N3DS.
4) Copy DevMenu.3ds to the NEW microSD. Make sure it's DevMenu and not BigBlueMenu. If it says Title Manager it won't work!
5) Insert the new microSD into your N3DS internal card slot.
6) Boot your N3DS, wait for it to create the necessary files on your microSD.
7) Start the gateway launcher by using Zelda or Cubic Ninja.
8) Select "Install NVRam" and let it finish.
9) Insert your Gateway (without any microSD!) into your N3DS, boot Gateway mode.
10) Once in sysNAND, remove the new microSD from your N3DS and replace it with the microSD you use for emuNAND.
11) Insert the new microSD into your Gateway card and put it in your N3DS.
12) Press select and mount DevMenu and start it.
13) Import the mset CIA for your region.
14) Reboot
15) Profit!

This is from a member of this forum, can't remember his name sorry


so, you have to use a COMPLETE NEW internal microSD right? Can I put back my old internal microSD to the 3ds? because all my savegames are there.

EDIT:

yes, it works this way

Step 10 its emuNAND.
 
I used the option backup system nand and created the nand.bin file, and installed the nvram succesfully, now after I boot into gateway mode on my new 3ds LL, on next step for devmenu,

when I try to import the mset jap.cia, it says:

Import failed. File:
mset_jap.cia
This cia is invalid.
0xD8E08027


I dont understand what went wrong.
 
I used the option backup system nand and created the nand.bin file, and installed the nvram succesfully, now after I boot into gateway mode on my new 3ds LL, on next step for devmenu,

when I try to import the mset jap.cia, it says:

Import failed. File:
mset_jap.cia
This cia is invalid.
0xD8E08027


I dont understand what went wrong.
Use "DevMenu.3ds" blueboxmanager won't work
 
Use "DevMenu.3ds" blueboxmanager won't work


I tried to find this devmenu on google but every tutorial they change the names like they are all the same title manager (the one on my home screen on emunand) / blueboxmanager / devmenu.

For example, here: https://gbatemp.net/threads/tutorial-installing-devmenu.375241/

Devmenu I could find this one in .3ds, not .cia to install it first. I tried to run the .3ds file from game selector but I get black screen.

Could you PM me with both .cia and .3ds files please of devmenu finally?
 
I tried to find this devmenu on google but every tutorial they change the names like they are all the same title manager (the one on my home screen on emunand) / blueboxmanager / devmenu.

For example, here: https://gbatemp.net/threads/tutorial-installing-devmenu.375241/

Devmenu I could find this one in .3ds, not .cia to install it first. I tried to run the .3ds file from game selector but I get black screen.

Could you PM me with both .cia and .3ds files please of devmenu finally?
Search for SDK.DevKit.Tools.3DSWare.3DS.INTERNAL-BigBlueBox.rar on google, extract DevMenu.csu from it, rename it to DevMenu.3ds and you're good, DevMenu.cia from this archive will NOT install on retails console, only Developper's ones.
 
  • Like
Reactions: Margen67
Search for SDK.DevKit.Tools.3DSWare.3DS.INTERNAL-BigBlueBox.rar on google, extract DevMenu.csu from it, rename it to DevMenu.3ds and you're good, DevMenu.cia from this archive will NOT install on retails console, only Developper's ones.


As I said, I already have a devmenu.3ds on gateway microsd, when I try to run it, I get black screen on my new 3ds LL.

Anyway, I downloaded this dev kit and the latest version is 6.2 renamed it to .3ds

Again, black screen.

I dont know what else to do to make this GW 3.2 working and get rid of my sky3ds.
 
As I said, I already have a devmenu.3ds on gateway microsd, when I try to run it, I get black screen on my new 3ds LL.

Anyway, I downloaded this dev kit and the latest version is 6.2 renamed it to .3ds

Again, black screen.

I dont know what else to do to make this GW 3.2 working and get rid of my sky3ds.
It do NOT work with DevMenu 6.2, you need the old version from SDK2.x
 
As I said, I already have a devmenu.3ds on gateway microsd, when I try to run it, I get black screen on my new 3ds LL.

Anyway, I downloaded this dev kit and the latest version is 6.2 renamed it to .3ds

Again, black screen.

I dont know what else to do to make this GW 3.2 working and get rid of my sky3ds.

It do NOT work with DevMenu 6.2, you need the old version from SDK2.x

Right!
It needs to be 2.3.4...
Also, if it still does not work, Tilde88 said he had the same problem and "fixed" it by using a different MicroSD. He said this could have been because of file fragmentation and I add that what he said: it could have been because of SD failing as well.

Good luck!
 

Site & Scene News

Popular threads in this forum