Installing Devmenu

I've been looking around and learning a lot in a short amount of time. Here is what I've got.

New Instructions

You'll need a Gateway and BigBlueMenu. You can find BigBlueMenu via Google. Search for BigBlueMenu.3DS-BigBlueBox and you should find it pretty easily. Inside there are a few files.

The two we need are:

BigBlueMenu.3ds
BigBlueMenu.cia

Put BigBlueMenu.3ds onto the MicroSD card in the Gateway. Put BigBlueMenu.cia onto the SD card that goes into the 3DS.

Go to emunand. Never modify your sysnand unless you have a hardware flasher handy. (This may change when CFW comes about)

Run BigBlueMenu.3ds via Gateway and install BigBlueMenu.cia.

You can now install cia files when ever you want to.

Older Instructions

To install Devmenu, you'll need Devmenu. I can't provide that on this forum. I can however tell you which ones and about where to find them and how to use them.

First off, you'll need a Gateway card. You need to have it setup and be using emunand. This is for your safety.

You'll need two copies of Devmenu. One comes from the 3DS Dev Kit (DevMenu.csu). The other comes from GovanifY's 3DS_CFW (DevMenu_2x.cia).

Code:
MD5's
DevMenu.csu    - e65629fbe2ae8a419cf8624df78e78b2
DevMenu_2x.cia - 16dad9b20243446d3987d4dd26dfb93e

Put DevMenu.csu onto the MicroSD card that goes into the Gateway card. Rename it to DevMenu.3ds.

Put DevMenu_2x.cia onto the SD card that goes into the system.

Run DevMenu from the Gateway as a 3DS game. Go to the center tab and install DevMenu_2x.cia.

When you exit, you'll now have a DevMenu on the grid. Use that from now on to install cia files.
 

Shnilj

New Member
Newbie
Joined
Dec 12, 2014
Messages
1
Trophies
0
Age
35
Location
Brugge, Belgium
XP
41
Country
Belgium
For some reason this isn't working for me. I put the .3ds on my red card en the .cia on my SD. I then boot into gateway mode (emunand) and I do see the 'Title Manager', but it does not load... Am I doing something wrong? I am running emunand 9.2.0-20.
 

ChengCheng

Member
Newcomer
Joined
Jul 6, 2015
Messages
6
Trophies
0
Age
35
XP
63
Country
Switzerland
I've been looking around and learning a lot in a short amount of time. Here is what I've got.

New Instructions

You'll need a Gateway and BigBlueMenu. You can find BigBlueMenu via Google. Search for BigBlueMenu.3DS-BigBlueBox and you should find it pretty easily. Inside there are a few files.

The two we need are:

BigBlueMenu.3ds
BigBlueMenu.cia

Put BigBlueMenu.3ds onto the MicroSD card in the Gateway. Put BigBlueMenu.cia onto the SD card that goes into the 3DS.

Go to emunand. Never modify your sysnand unless you have a hardware flasher handy. (This may change when CFW comes about)

Run BigBlueMenu.3ds via Gateway and install BigBlueMenu.cia.

You can now install cia files when ever you want to.

Older Instructions

To install Devmenu, you'll need Devmenu. I can't provide that on this forum. I can however tell you which ones and about where to find them and how to use them.

First off, you'll need a Gateway card. You need to have it setup and be using emunand. This is for your safety.

You'll need two copies of Devmenu. One comes from the 3DS Dev Kit (DevMenu.csu). The other comes from GovanifY's 3DS_CFW (DevMenu_2x.cia).

Code:
MD5's
DevMenu.csu    - e65629fbe2ae8a419cf8624df78e78b2
DevMenu_2x.cia - 16dad9b20243446d3987d4dd26dfb93e

Put DevMenu.csu onto the MicroSD card that goes into the Gateway card. Rename it to DevMenu.3ds.

Put DevMenu_2x.cia onto the SD card that goes into the system.

Run DevMenu from the Gateway as a 3DS game. Go to the center tab and install DevMenu_2x.cia.

When you exit, you'll now have a DevMenu on the grid. Use that from now on to install cia files.
I donot know the difference between emunand and sysnand
 

Kayot

Well-Known Member
OP
Member
Joined
Jan 24, 2010
Messages
362
Trophies
0
Website
sites.google.com
XP
490
Country
United States
Emunand is NAND that is on the SD card, sysnand is the NAND that exists on the system itself. You can mess up emunand and be ok by just formatting the SD card (or deleting certain files). You toast Sysnand and you lose the 3DS unless you have both a hardware flasher installed and a backup of your nand to flash to the nand.

A better example would be overlayfs. Emunand is overlayed on top of the sysnand. If sysnand is marked as readonly then it is safe and all changes happen only to the emunand. If you eject the SD card then all the titles installed in emunand disappear. The os files on the SD card just sit there until / is remounted to the sd and restarted, which locks the sysnand to readonly and only the SD card is written to. This is also why the emunand can be updated. The changes are only made to the SD card since the sysnand is ro.

The reason toasting your sysnand bricks the system is because without sysnand, you can't remap the / to the sd card. In effect, you use the sysnand as a bootloader for emunand.

At least that's what it looks like to me.

I'm not really up on hardware stuff because the people who know how to do it don't bother teaching and usually just point at something akin to advanced unified field exponential inverse collapse quantum dynamic nuclear helios particle fusion and say, "See if you read it, it makes sense."
 
Last edited by Kayot,
  • Like
Reactions: ChengCheng

ChengCheng

Member
Newcomer
Joined
Jul 6, 2015
Messages
6
Trophies
0
Age
35
XP
63
Country
Switzerland
Emunand is NAND that is on the SD card, sysnand is the NAND that exists on the system itself. You can mess up emunand and be ok by just formatting the SD card (or deleting certain files). You toast Sysnand and you lose the 3DS unless you have both a hardware flasher installed and a backup of your nand to flash to the nand.

A better example would be overlayfs. Emunand is overlayed on top of the sysnand. If sysnand is marked as readonly then it is safe and all changes happen only to the emunand. If you eject the SD card then all the titles installed in emunand disappear. The os files on the SD card just sit there until / is remounted to the sd and restarted, which locks the sysnand to readonly and only the SD card is written to. This is also why the emunand can be updated. The changes are only made to the SD card since the sysnand is ro.

The reason toasting your sysnand bricks the system is because without sysnand, you can't remap the / to the sd card. In effect, you use the sysnand as a bootloader for emunand.

At least that's what it looks like to me.

I'm not really up on hardware stuff because the people who know how to do it don't bother teaching and usually just point at something akin to advanced unified field exponential inverse collapse quantum dynamic nuclear helios particle fusion and say, "See if you read it, it makes sense."
thank u, I am new a lot to learn
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    K3Nv2 @ K3Nv2: butt