Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[tiduscrying]

I will keep my eye on the beta. I use AuReiNand for "clean" GBA loading only so I have for the time being reverted to 4.2. I use ReiNand for emuNAND stuff as I am emuNAND user. Thank for your help.

I have a 9.2 sysNAND and 10.7 emuNAND setup like you and can confirm that GBA loading doesn't work on sysNAND using the latest 4.2 beta. It works just fine on my emuNAND though (I have GBA games installed to both since I don't want to merge to a sysNAND-only setup just yet...).

Edit: GBA loading on my sysNAND does work when I hold R on boot, which makes sense since it is loading from the firmware.bin on my SD.

 

[stl25]

I have a 9.2 sysNAND and 10.7 emuNAND setup like you and can confirm that GBA loading doesn't work on sysNAND using the latest 4.2 beta. It works just fine on my emuNAND though (I have GBA games installed to both since I don't want to merge to a sysNAND-only setup just yet...).

Edit: GBA loading on my sysNAND does work when I hold R on boot, which makes sense since it is loading from the firmware.bin on my SD.

So GBA loading is the same in the beta as it was in 4.2? You have firmware bin on your SD? Since I am using arm9select to use AuReiNand for GBA loading I will have to load AuReiNand as r.bin and keep firmware.bin on my SD.

Edit: GBA works just like @tiduscrying stated. Holding R while booting sysNAND will allow GBA games to work. I have an aurei folder with only a config.bin inside.

@Aurora Wright, when exiting a GBA game if the R button is not held the system reboots to sysNAND but you cannot start another GBA game without shut down and restart. Is it possible to flag the reboot to boot back into sysNAND as if the R button is being held without actually having to hold it? If the user forgets to hold R when exiting a GBA game they will be unable to launch another GBA game from sysNAND.

 

[democracy]

I have a 9.2 sysNAND and 10.7 emuNAND setup like you and can confirm that GBA loading doesn't work on sysNAND using the latest 4.2 beta. It works just fine on my emuNAND though (I have GBA games installed to both since I don't want to merge to a sysNAND-only setup just yet...).

Edit: GBA loading on my sysNAND does work when I hold R on boot, which makes sense since it is loading from the firmware.bin on my SD.

GBA loading working great here on latest beta but I don't have an emunand partition

 

[democracy]

@Aurora Wright posted this at the bottom of his beta release post.

To use the path changer program, just drag the .bin on top and type the filename. (suppose it's in randomloader/arn.bin, type just that).
I'd like to have feedback on "complicated" setups (NANDs with different FIRMs, and things like that)

I'm a bit confused what this feature does, I think it let you specify where other payloads like decrypt9 can load from? Also firmware bin?

 

[tiduscrying]

So GBA loading is the same in the beta as it was in 4.2? You have firmware bin on your SD? Since I am using arm9select to use AuReiNand for GBA loading I will have to load AuReiNand as r.bin and keep firmware.bin on my SD.

For me, GBA loading works in the 4.2 beta, but only on my emuNAND (10.7) or on my sysNAND with a non-default firmware.bin file loaded holding R on boot (I'm using the 10.2 firmware.bin so I can also load NTR). In the normal 4.2 that was released a week ago, GBA games loaded fine from my sysNAND, without holding anything or using a different firm.

 

[Supster131]

I'm a bit confused what this feature does, I think it let you specify where other payloads like decrypt9 can load from? Also firmware bin?

It's made if you use ARN with a boot manager, I think.

 

[matpower]

I'm a bit confused what this feature does, I think it let you specify where other payloads like decrypt9 can load from? Also firmware bin?

That's wrong, according to what I have read, it's supposed to change where the reboot patch should look.
By default, when it loads the AGB_FIRM/TWL_FIRM from NAND in the newest beta, it searches for the "arm9loaderhax.bin"(which is AuReiNAND) to make the reboot patch work, if you are using a different boot manager(BootAnim9, CTRBootManager9, etc), it'll attempt to load the reboot patch from that, and it'll fail. With that program, you can redirect it to the proper file(AuReiNAND's arm9loaderhax.bin) if it's renamed or in a different location.

 

[stl25]

I'm a bit confused what this feature does, I think it let you specify where other payloads like decrypt9 can load from? Also firmware bin?

I believe it is for when AuReiNand reboots. Like for example you are playing from emuNAND and you

For me, GBA loading works in the 4.2 beta, but only on my emuNAND (10.7) or on my sysNAND with a non-default firmware.bin file loaded holding R on boot (I'm using the 10.2 firmware.bin so I can also load NTR). In the normal 4.2 that was released a week ago, GBA games loaded fine from my sysNAND, without holding anything or using a different firm.

For me in 4.2 I could only launch GBA by holding R to load firmware.bin from SD. If I held L to load sysNAND with firmware90.bin from SD, GBA games will not boot. Same in this beta only firmware.bin is not required in aurei folder anymore.

@tiduscrying, play a GBA game on AuReiNand, then exit without holding any buttons. When the 3DS reboots into sysNAND try to launch another GBA game and let me know if it runs or gives you the an error has occurred message. Thanks in advance.

 

[tiduscrying]

I believe it is for when AuReiNand reboots. Like for example you are playing from emuNAND and you



For me in 4.2 I could only launch GBA by holding R to load firmware.bin from SD. If I held L to load sysNAND with firmware90.bin from SD, GBA games will not boot. Same in this beta only firmware.bin is not required in aurei folder anymore.

@tiduscrying, play a GBA game on AuReiNand, then exit without holding any buttons. When the 3DS reboots into sysNAND try to launch another GBA game and let me know if it runs or gives you the an error has occurred message. Thanks in advance.

Alright, here's my report.

• Booted into emuNAND (ARN 4.2Beta, 10.7)
• Launched a GBA VC game (mother 3)
• Pressed home and was booted into sysNAND (9.2)
  • No buttons held
• Launched a different GBA VC game (river city ransom ex)
• Game booted just fine from there
• Went back to the home menu, was brought back into sysNAND
  • No buttons held
• Launched mother 3 again, launched just fine.

EDIT: exited mother 3 and returned to sysNAND. I checked the NAND info from system settings and it says "SysA 9.2.0-20U)" which is what it also says when I boot into sysNAND while holding R (and therefore loading the alternative firmware.bin).

 

[GBHAKC75]

Damn ! This new feature looks just awesome, but I still need NTR so I can't really use it
Hope NTR gets updated someday for 10.4 FIRM (but I highly doubt it...).

 

[stl25]

Thanks @tiduscrying, something must be wrong with my reboot patch. I play a game from sysNAND and exit from GBA game back to sysNAND with no buttons held, the next GBA game I try to run gives me the an error occurred message.

do you have patched AGB_FIRM installed to sysNAND and emuNAND or do you have stock AGB_FIRM and use the patching from within AuReiNand? Thanks for your quick reply.

 

[tiduscrying]

Thanks @tiduscrying, something must be wrong with my reboot patch. I play a game from sysNAND and exit from GBA game back to sysNAND with no buttons held, the next GBA game I try to run gives me the an error occurred message.

do you have patched AGB_FIRM installed to sysNAND and emuNAND or do you have stock AGB_FIRM and use the patching from within AuReiNand? Thanks for your quick reply.

No problem! I used to have the patched AGB_FIRM installed to both my sysNAND and emuNAND, but I restored it to the stock versions once AuRei started supporting AGB/TWL patching.

 

[stl25]

Something definitely wrong with my reboot patch then. Thanks @tiduscrying for all your help.


Edit: Installed GBA to emuNAND and sysNAND. Now everything runs fine as it did for @tiduscrying.


@Aurora Wright, what is different about running GBA from only sysNAND vice emuNAND and sysNAND? When GBA was only installed to sysNAND when a GBA game was exited, upon return to sysNAND another GBA title cannot be launched. However from launching GBA from emuNAND, when exiting GBA game, upon return to sysNAND another GBA title CAN be launched just fine.

 

[democracy]

That's wrong, according to what I have read, it's supposed to change where the reboot patch should look.
By default, when it loads the AGB_FIRM/TWL_FIRM from NAND in the newest beta, it searches for the "arm9loaderhax.bin"(which is AuReiNAND) to make the reboot patch work, if you are using a different boot manager(BootAnim9, CTRBootManager9, etc), it'll attempt to load the reboot patch from that, and it'll fail. With that program, you can redirect it to the proper file(AuReiNAND's arm9loaderhax.bin) if it's renamed or in a different location.

Oh that's clever!

 

[DjoeN]

I think i posted this before,
I don't play GBA games anymore from emunand, since i have unlinked nands i wanted to avoid installing GBA cia's twice (emunand and sysnand) to get them working in emunand.

I just install them in sysnand 9.2 with firmware 10.2 (NTR)(hold R to boot firmware.bin sysnand).
whenever i feel like playing GBA games i boot into sysnand (Hold R), this way only instlling them once is enough (takes up a little less space to)
Also, i really don't mind to reboot my system into sysnand and hold R, to play GBA games!

[EDIT]

Nevermind, was using an old thing

 

[Februarysn0w]

oh my god. latest commit looks we can load firm from ctrnand directly. this is what i want to know few days ago.

LOVE THIS AWESOME UPDATE. THANK YOU.

 

[Sir BLaDE]

oh my god. latest commit looks we can load firm from ctrnand directly. this is what i want to know few days ago.

LOVE THIS AWESOME UPDATE. THANK YOU.

Well, I suposse if the native_firm changes in newer updates, there is no need of more firmware.bin right? (Except for NTR)

 

[Februarysn0w]

Well, I suposse if the native_firm changes in newer updates, there is no need of more firmware.bin right? (Except for NTR)

YES! I think so.

 

[GBHAKC75]

Well, I suposse if the native_firm changes in newer updates, there is no need of more firmware.bin right? (Except for NTR)

Right
That said, if changes are too big, it could break AuReiNand patches (and then you'll have to wait for an update).

 

[About7fish]

I apologize for what I'm sure is a dumb question, but when the setup says to use the firmware from the n3ds folder, does this imply that I can't update my emunand via system update as I can with rxtools? I followed an incredibly simplified guide for hacking my launch 3DS and I'm finding that this is coming back to haunt me now that I'm trying to understand what exactly I'm doing.