Releases: LumaTeam/Luma3DS
Releases · LumaTeam/Luma3DS
Release list
v3.7.3
- A lot of code clean-up. Filesize went down by ~3 KB, and there can possibly be slight speed improvements.
v3.7.2
Previous release broke .dat booting from a 9.0 NAND if A9LH was installed.
v3.7.1
- Added forcing of boot options on A9LH: always prevents losing AGB_FIRM saves by booting to sysNAND, forces the last used options on a MCU reboot (can be overridden with A).
v3.7
- Added a flag to skip decrypting and patching FIRM and use the already patched ones, for a slightly faster boot and to avoid writing 1 MB to SD on each boot.
Warning!:
You MUST remove the patched firmwares in the rei folder after switching from a non-A9LH usage to A9LH. You have been warned!
Original idea and patch by @FIX94.
v3.6.1
- Fixed reboot patch on New 3DS (178 MB cias now work!)
v3.6
- Full support for a future screen-init-enabled A9LH payload.
- A whole new reboot patch (thanks to a skilled reverser for this). It works on New 3DS (for as of yet unused large RAM modes), doesn't break GBA and DS games (no more choosing to press A or not on Old 3DS), gets disabled automatically with 9.0 FIRM to make exploits work.
- Because of the new reboot patch, now N and O3DS share the same "rei" folder.
- Fixed N3DS "3D bug", thanks to TiniVi and Cakes for this).
- Code clean-up.
v3.5.3
New button combos:
Regular mode: nothing boots EmuNAND with 9.6-10.4 FIRM, L boots SysNAND with 9.0 FIRM, R boots SysNAND with 9.6-10.4 FIRM
Updated SysNAND mode: nothing boots SysNAND with 9.6-10.4 FIRM, L boots EmuNAND with 9.0 FIRM, R boots EmuNAND with 9.6-10.4 FIRM.
v3.5.2
Hopefully fixed booting emuNAND with 9.0 FIRM.
v3.5.1
- Re-added reboot patch on A9LH
- O3DS and N3DS now share the same emuNAND patch
- Shorter patching patterns
- patched_firmware does not keep garbage from larger loaded FIRMs
- Flags can be empty files
v3.5
- Fixed A9LH boot detection
- Added a new "updated syaNAND" mode, which is enabled by the "/rei/updatedsysnand" flag. In this mode, sysNAND is booted by default using the 9.6-10.4 FIRM, L boots emuNAND with 9.0 FIRM (for arm9 exploits and such) and L+R boots emuNAND with the 9.6-10.4 FIRM.
- When sysNAND is booted on a A9LH setup, a patch (courtesy of delebile) is applied that makes updates skip writing to FIRM0 and FIRM1. This way, sysNAND can be updated without losing A9LH.