So, Luma3DS is a "noob friendly" CFW.
As Apple (and more recently, Microsoft) products blatantly show, "noob friendly" often gets in the way of customization.
On the other hand, a high quality and very customizable CFW is now available thanks to chaoskagami, but its setup has historically been very inconvenient and, to a lesser extent, it still is compared to Luma. While most misconfigurations only result in very embarassing topics on gbatemp, "accidentally" deselecting kernel write protection (an optional feature on Corbenik) could also result in a9lh going horribly wrong. Luma also happens to be the only CFW that allows users to map .bin software directly to a button.
So, over this weekend I made Puma33DS.
If you didn't follow GBATemp in the last months and so you don't know what's up with the name (or this post didn't make you guess), yes, it's 99% based on today's current nightly of non-dev Luma3DS.
So what are the differences?
Region free is optional (which happens to be a workaround for the black icons that appear if you downgrade Home)
eShop/NZone anti-update, and Spotpass auto-update-download, patches are optional
SecureInfo patches are optional (= very easily switch between signed SecureInfo_A and un/signed SecureInfo_C)
Verbose ErrDisp patch from Luma-Dev (enhances "an error has occurred" while running in 3DS mode)
Select between Home and Test Menu if you have it installed (without the need for enabling UNITINFO or using Config/MenuSelector), thanks to
@ReisyukakuIt's only officially available in .bin format, and it's incompatible with Luma (the /luma/config.bin must be deleted when switching) because, well, there are more options...
Código fuente y descargaFuente