Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[pbanj]

Give her time, she's just one person working on this project and she also has her own things.
If there's any CFW that should be giving you the itches, it should be RXtools.

those people have scratched their skin off

 

[hobbledehoy899]

those people have scratched their skin off

May @Roxas75's 3DS toolkit rest in peace.

 

[PetitMagique]

Give her time, she's just one person working on this project and she also has her own things.
If there's any CFW that should be giving you the itches, it should be RXtools.

Yeah these frequent releases have been like crack, now I neeedd my fix..NAAAAOOW!! Lol

 

[astronautlevel]

Yeah these frequent releases have been like crack, now I neeedd my fix..NAAAAOOW!! Lol

I promise you, the next release will not disappoint.

 

[The Catboy]

Yeah these frequent releases have been like crack, now I neeedd my fix..NAAAAOOW!! Lol

That's some pretty good marketing then. Give them regular updates, then cut them off for a few days to make them want it more!

 

[hobbledehoy899]

That's some pretty good marketing then. Give them regular updates, then cut them off for a few days to make them want it more!

lol New Coke

 

[Supster131]

I promise you, the next release will not disappoint.

>when you know what the next update will include

Cruel XD

 

[hobbledehoy899]

>when you know what the next update will include

You will be able to load an external loader.cxi from the SD-Card.

 

[Xenosaiga]

The next update will include airplane mode which will enable your device to float for several meters when thrown with sufficient force.

 

[Supster131]

The next update will include airplane mode which will enable your device to float for several meters when thrown with sufficient force.

Shhh! Don't leak that shit! It was supposed to be a surprise!

 

[Jiro2]

As an actual request, would it be possible to have the CFW automatically patch both the DS cart whitelist and whatever else it needs to patch, so people can run any DS flashcarts on it without having to manually install a whitelist or use a homebrew to run DS flashcarts? Or does it already do that?

Also, a question: could someone please explain to me the difference between the boot.3dsx and the other .3dsx? I understand that one is for menuhax, but what is it that the two do that is different, that requires using a special .3dsx for menuhax?

 

[Supster131]

As an actual request, would it be possible to have the CFW automatically patch both the DS cart whitelist and whatever else it needs to patch, so people can run any DS flashcarts on it without having to manually install a whitelist or use a homebrew to run DS flashcarts? Or does it already do that?

Kinda, with the patched TWL_FIRM, we don't really need the whitelist anymore.

The only exception being, of course, really old flashcarts that never worked on the 3DS, or hell, even the DSi if you're pushing it.
If your flashcart never worked on the 3DS, use this: https://gbatemp.net/threads/twl-slot-1-launcher-first-custom-dsiware-app.414501/
If your flashcart only worked on the DS (cards that would automatically boot into it), use this: https://gbatemp.net/threads/r4-stage2-twl-flashcart-launcher-and-perhaps-other-cards-soon™.416434/

 

[matpower]

As an actual request, would it be possible to have the CFW automatically patch both the DS cart whitelist and whatever else it needs to patch, so people can run any DS flashcarts on it without having to manually install a whitelist or use a homebrew to run DS flashcarts? Or does it already do that?

The TWL_FIRM patch already does that, it works even better than the whitelist. You just need the firmware_twl.bin file on your aurei folder.
Note that you still need a homebrew to run certain flashcards like the non-DSi/3DS flashcards(Acekard 2.1, Supercard DSOne, DSTT, the OG R4, etc.) or flashcards that worked on the DSi, but doesn't work on the 3DS.

 

[democracy]

>when you know what the next update will include

Cruel XD

Please tell me anything but DS Roms, I just bought an R4

 

[Supster131]

Please tell me anything but DS Roms, I just bought an R4

I wish
But no, that's not it.

 

[democracy]

The next update will include airplane mode which will enable your device to float for several meters when thrown with sufficient force.

That's a ludicrous image; 3DS fans sitting on a plane, airplane mode = getting smoked by a 3DS on a plane!

 

[democracy]

I wish
But no, that's not it.

Even more exciting, a new 3DS special ability!!

 

[Aurora Wright]

As some of you might already know, I was busy with a major AuReiNand overhaul. Now, I'll spoil the surprise for sure, but I learned that I need external testing to find bugs (there's always something that slips up). So, I'm publishing a beta.
http://www8.zippyshare.com/v/UioYD4Mt/file.html
There are a lot of changes:
- Gotten rid of the patched FIRMs, AuReiNand now finds and loads all the FIRMs from CTRNAND by default. If you are booting an emuNAND, the FIRMs will also be loaded from its CTRNAND. This also applies to AGB and TWL FIRM, and allows for a very fast boot with no firmware files on the SD card.
- 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 just for the default NAND.
- 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 "Updated SysNAND", and vice-versa.
- In order for AuReiNand to handle FIRM reboots, the .bin path needs to be hardcoded in the program. The default is /arm9loaderhax.bin (the AuReiNand.dat is also supported for 9.0 people). A PC tool was written to make changing the path easier.

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)

 

[pbanj]

As some of you might already know, I was busy with a major AuReiNand overhaul. Now, I'll spoil the surprise for sure, but I learned that I need external testing to find bugs (there's always something that slips up). So, I'm publishing a beta.
http://www8.zippyshare.com/v/UioYD4Mt/file.html
There are a lot of changes:
- Gotten rid of the patched FIRMs, AuReiNand now finds and loads all the FIRMs from CTRNAND by default. If you are booting an emuNAND, the FIRMs will also be loaded from its CTRNAND. This also applies to AGB and TWL FIRM, and allows for a very fast boot with no firmware files on the SD card.
- 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 just for the default NAND.
- 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 "Updated SysNAND", and vice-versa.
- In order for AuReiNand to handle FIRM reboots, the .bin path needs to be hardcoded in the program. The default is /arm9loaderhax.bin (the AuReiNand.dat is also supported for 9.0 people). A PC tool was written to make changing the path easier.

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)

holy fuck thats sick

 

[matpower]

As some of you might already know, I was busy with a major AuReiNand overhaul. Now, I'll spoil the surprise for sure, but I learned that I need external testing to find bugs (there's always something that slips up). So, I'm publishing a beta.
http://www8.zippyshare.com/v/UioYD4Mt/file.html
There are a lot of changes:
- Gotten rid of the patched FIRMs, AuReiNand now finds and loads all the FIRMs from CTRNAND by default. If you are booting an emuNAND, the FIRMs will also be loaded from its CTRNAND. This also applies to AGB and TWL FIRM, and allows for a very fast boot with no firmware files on the SD card.
- 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 just for the default NAND.
- 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 "Updated SysNAND", and vice-versa.
- In order for AuReiNand to handle FIRM reboots, the .bin path needs to be hardcoded in the program. The default is /arm9loaderhax.bin (the AuReiNand.dat is also supported for 9.0 people). A PC tool was written to make changing the path easier.

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)

Sadly, I don't have any crazy setup with different FIRMs, but I wonder how it handles AGB/TWL patching with pre-patched files, specially the AGB one. Gotta give it a try.