Hacking (help)N3DS initializing by Emulator

[gnmmarechal]

Jesus... Menuhax isn't even that long ago and people are forgetting how it works?

OP, boot.3DSX is the file that usually boots your OS. It will boot whatever file is there when the system boots up. If you replace the file, for example, the emulator, it will boot the emulator instead.

Replacing your R4i card will have zero effect, and has nothing at all to do with booting the 3DS. Putting the original boot.3dsx will allow you to load your system.

Try removing the SD Card of your system. It will boot up to another version of your OS, a particularly unsafe version. For this reason, do NOT accept any update messages and try not to do much while in this alternative OS.

The microSD Card is located in the battery cover.

By the way, a game card is not an SD Card.

For future reference, you have Menuhax.

No, boot.3dsx is NOT the file that usually boots the OS. boot.3dsx is usually used for the HBL. If you're going to explain, in my opinion, it'd be better to explain everything using the actual terminology (like SysNAND, EmuNAND, HBL, etc.), as for him to start using it as well. That is just my opinion though.

My answer would be:

- sdmc:/boot.3dsx is the file launched by MenuHax. It usually is HBL (Homebrew Launcher), but it can also be a CFW launcher like Luma3DS' or ReiNAND's.

- The SD card inserted in the R4 will have 0 effect on the 3DS at boot time.

- The New3DS comes with a micro SD card. You can access it by unscrewing the backplate and removing the card, then plugging it to an adapter/card reader/whatever.

- If you boot without the SD; you will access the so called "SysNAND". What this means is that:
* Your system is booting from its internal storage. You shouldn't use SysNAND if you want to keep using EmuNAND, as updating SysNAND WILL update your system and it will make you unable to boot into EmuNAND (if you don't use ARM9LoaderHax, but that's not relevant to this explanation)

- If you use EmuNAND with MenuHax/MSET, you should definitely take at least a look to ARM9LoaderHax, and consider changing, as it isn't hard.



I probably wanted to say more, but I had to leave halfway through writing so I most likely forgot something.

 

[Halvorsen]

No, boot.3dsx is NOT the file that usually boots the OS. boot.3dsx is usually used for the HBL. If you're going to explain, in my opinion, it'd be better to explain everything using the actual terminology (like SysNAND, EmuNAND, HBL, etc.), as for him to start using it as well. That is just my opinion though.

My answer would be:

- sdmc:/boot.3dsx is the file launched by MenuHax. It usually is HBL (Homebrew Launcher), but it can also be a CFW launcher like Luma3DS' or ReiNAND's.

- The SD card inserted in the R4 will have 0 effect on the 3DS at boot time.

- The New3DS comes with a micro SD card. You can access it by unscrewing the backplate and removing the card, then plugging it to an adapter/card reader/whatever.

- If you boot without the SD; you will access the so called "SysNAND". What this means is that:
* Your system is booting from its internal storage. You shouldn't use SysNAND if you want to keep using EmuNAND, as updating SysNAND WILL update your system and it will make you unable to boot into EmuNAND (if you don't use ARM9LoaderHax, but that's not relevant to this explanation)

- If you use EmuNAND with MenuHax/MSET, you should definitely take at least a look to ARM9LoaderHax, and consider changing, as it isn't hard.



I probably wanted to say more, but I had to leave halfway through writing so I most likely forgot something.

I'm not going to explain the entire history of 3DS hacking, haha. I hit it in Layman's terms on purpose, while making it clear that you shouldn't update sysNAND and that Menuhax loads whatever is called boot.3dsx in the SD Card. From a casual perspective I already got confused by the explanation of sysNAND and emuNAND. "Does it matter if I update sysNAND? Does emuNAND really matter? Can't I just do these hacks from sysNAND?"

If he wanted to use the correct terms then he would research it himself, but his main goal in creating this thread was to be able to reboot into emuNAND. If one were to explain what everything was and meant, the original thread's purpose would be lost, and OP would probably not be able to find a solution. I mean, he bought the 3DS prehacked for a reason.

And technically, boot.3DSX does boot the OS he's talking about. Can't get into emuNAND from Menuhax without it.

 

[gnmmarechal]

I'm not going to explain the entire history of 3DS hacking, haha. I hit it in Layman's terms on purpose, while making it clear that you shouldn't update sysNAND and that Menuhax loads whatever is called boot.3dsx in the SD Card. From a casual perspective I already got confused by the explanation of sysNAND and emuNAND. "Does it matter if I update sysNAND? Does emuNAND really matter? Can't I just do these hacks from sysNAND?"

If he wanted to use the correct terms then he would research it himself, but his main goal in creating this thread was to be able to reboot into emuNAND. If one were to explain what everything was and meant, the original thread's purpose would be lost, and OP would probably not be able to find a solution. I mean, he bought the 3DS prehacked for a reason.

And technically, boot.3DSX does boot the OS he's talking about. Can't get into emuNAND from Menuhax without it.

Technically, with MenuHax, the firmware boots, then the Menuhax takes control and runs after that. Menuhax is much more than "run the OS".
Also, although you needn't explain everything, using the terms SysNAND and EmuNAND will help him understand (as everyone here uses that terminology)

Sent from my cave of despair where I collect souls

 

[Halvorsen]

Technically, with MenuHax, the firmware boots, then the Menuhax takes control and runs after that. Menuhax is much more than "run the OS".
Also, although you needn't explain everything, using the terms SysNAND and EmuNAND will help him understand (as everyone here uses that terminology)

Sent from my cave of despair where I collect souls

The OS OP is talking about is emuNAND, not sysNAND, so for all intents it doesn't load.

I understand where you're coming from as well.