Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[Localhorst86]

i cant get installed gba or twl games to work with this (no firmware.bin). what am i doing wrong? all i get is a black screen.

also, with the latest release it talks about a harcoded path to arm9loaderhax.bin. if i am using ctrbootmanager9 to launch my cfw, do i need to put aureinands arm9loaderhax.bin anywhere on the cart and patch the aureinand.dat file with the path changer tool?

 

[VIERcntHOLZ]

Shouldn't be too hard, but it would have to be a homebrew app or CIA because we don't have network function on arm9 yet.

Ah, damn - okay, start an cia on the home menu sucks too
I'm just speaking for the sake of automation

 

[pbanj]

so this one is to protect the sysnand?

help @Aurora Wright! please clarify!

I just checked, its the same its just renamed.

 

[reiyu]

It actually makes more sense with this name, so it's not so weird. The name now reflects what it actually does.

it makes it sound like you use the sysnand firm even though you're on emunand. which on the patch notes also state it.

The way AuReiNand works has changed. Now you can specify to autoboot SysNAND or not, and a NAND is no more tied to a FIRM (since 9.0 FIRM is autodetected). If you press nothing the default NAND is booted with its own FIRM, L boots the non-default NAND with its own FIRM, R boots EmuNAND with the SysNAND FIRM if you picked "Use SysNAND FIRM as default", and vice-versa.

If for some reason (like using NTR) you do not want to use the CTRNAND FIRM, you can place a firmware.bin in the aurei folder and it will be loaded in place of the default FIRM (so, the SysNAND FIRM if you picked "Use SysNAND FIRM as default", and vice-versa).

--------------------- MERGED ---------------------------

I just checked, its the same its just renamed.

the rename just confused me more than it should have helped...

 

[Deleted member 373223]

it makes it sound like you use the sysnand firm even though you're on emunand. which on the patch notes also state it.


--------------------- MERGED ---------------------------


the rename just confused me more than it should have helped...

in fact, that option doesn't protect the firm

 

[pbanj]

i cant get installed gba or twl games to work with this (no firmware.bin). what am i doing wrong? all i get is a black screen.

also, with the latest release it talks about a harcoded path to arm9loaderhax.bin. if i am using ctrbootmanager9 to launch my cfw, do i need to put aureinands arm9loaderhax.bin anywhere on the cart and patch the aureinand.dat file with the path changer tool?

You don't want to use the .dat with a9lh, just point the bootmanager to the .bin and remove the offset entry.
But you have to use the patch changer program to change the path inside the .bin for the games to work. Where do you keep the aireimand bin file and what is it named?

 

[reiyu]

in fact, that option doesn't protect the firm

huh what? then which option protects it?

 

[astronautlevel]

huh what? then which option protects it?

Force a9lh detection/just booting normally through the .bin

 

[Deleted member 373223]

huh what? then which option protects it?

if i am right, it is "Force A9LH detection"

--------------------- MERGED ---------------------------

a question, why should we want to make the 3ds think that he is a developer unit?

 

[astronautlevel]

if i am right, it is "Force A9LH detection"

--------------------- MERGED ---------------------------

a question, why should we want to make the 3ds think that he is a developer unit?

Mostly for more information on crashes.

 

[Deleted member 373223]

Mostly for more information on crashes.

other than that? ANY KIND of benefit?

 

[astronautlevel]

other than that? ANY KIND of benefit?

No, not really. Theoretically you could install dev apps, but there's really no benefit other than the additional information.

 

[reiyu]

if i am right, it is "Force A9LH detection"

"Force A9LH detection": If, for some reason, you want to use the non-A9LH version of the CFW (the .dat + .3dsx from HBL) after booting with the 9.0 FIRM on Arm9LoaderHax, you can force A9LH behavior with this setting. It's not needed otherwise.

no?

 

[astronautlevel]

"Force A9LH detection": If, for some reason, you want to use the non-A9LH version of the CFW (the .dat + .3dsx from HBL) after booting with the 9.0 FIRM on Arm9LoaderHax, you can force A9LH behavior with this setting. It's not needed otherwise.

no?

Yes, that's it. ARN autodetects booting with a9lh and as such will protect firm0/1 when you boot from it. Force A9LH detection forces this behavior if you boot from another means.

 

[Deleted member 373223]

"Force A9LH detection": If, for some reason, you want to use the non-A9LH version of the CFW (the .dat + .3dsx from HBL) after booting with the 9.0 FIRM on Arm9LoaderHax, you can force A9LH behavior with this setting. It's not needed otherwise.

no?

it SHOULD not be, but it is safer to use it, as it will block firm writing by system settings in WHATEVER CIRCUNSTANCE YOU ARE. (that's useful if for anykind of reason aureinand should not autodetect it)

 

[Localhorst86]

You don't want to use the .dat with a9lh, just point the bootmanager to the .bin and remove the offset entry.
But you have to use the patch changer program to change the path inside the .bin for the games to work. Where do you keep the aireimand bin file and what is it named?

ok, removed the dat, renamed the bin to aureinand.bin and put it into a9lh/aureinand.bin, used the path changing tool to point to that location, everything seems to work now, even agb and twl games.

 

[tloberif]

The.Legend.of.Zelda.Majoras.Mask.3D.EUR.3DS-CONTRAST == 0004000000125600.txt EUR ES
The.Legend.of.Zelda.Ocarina.of.Time.3D.USA.3DS-CONTRAST == 0004000000033500.txt EUR ES

Don´t work :T

 

[OctopusRift]

Basically I have a server that checks for updates every 10 minutes, the source code is available for anyone who wants it.

Please?

 

[reiyu]

Yes, that's it. ARN autodetects booting with a9lh and as such will protect firm0/1 when you boot from it. Force A9LH detection forces this behavior if you boot from another means.

so using "sysnand firm as default" isn't the one that protects contrary to what @pbanj is saying??

 

[leonmagnus99]

is updated sysnand file still needed in the aurei ?