3DS:Luma3DS forks: Difference between revisions

Line 5:

{{warning|text=There are some things that you should take note of when using Luma3DS forks:

* They may not always be kept up to date with upstream Luma3DS. This is particularly important with the jump between Luma3DS v10.3 and v11.0, where the configuration file format was changed and Luma3DS copies itself to internal memory.

* If you experience a bug with one of these forks, you must report it to the developer of that fork. The developers of Luma3DS are not responsible for any issues or bugs that may occur when using a fork unless the issue also occurs with upstream Luma3DS.}}

* If you experience a bug with one of these forks, you must report it to the developer of that fork. The developers of Luma3DS are not responsible for any issues or bugs that may occur when using a fork unless the issue also occurs with upstream Luma3DS.

* If you're getting assistance with an issue, you should specify if you are using a Luma3DS fork, as troubleshooting may differ.}}

== Installing a Luma3DS fork ==

Line 57:

Line 58:

** Lock system from use after specified time

|

|-

|[http://badda.de/lumamod/Luma3DS_v9.1-7-gbd15f_mod.7z Luma3DS PLG Loader (broken)]

|v9.1

|

* PLG plugin support without BootNTR

|Reportedly no longer works

on current firmware (11.14+)!

|-

|[https://gbatemp.net/attachments/9-1_stealth-zip.150796/ Luma3DS Stealth]

|v9.1

|

* Disable chainloader/config access from 3DS

* Store config and crash dumps on CTRNAND

* Effectively hides Luma3DS from SD

| Does not stop anyone from

just putting any other

<code>boot.firm</code> on root of SD.

|}