But rxTools is not a CFWThere's rxtools too. KARL as well when they manage to release it.
It patches firm to allow sd redirection. So it is.But rxTools is not a CFW
It's just emuNAND and nothing more. It doesn't allow anything that normal firmware doesn't, it's just clean firmware, hence not CFW.It patches firm to allow sd redirection. So it is.
That's why you have to include firmware.bin.
emuNAND counts as a CFW if you ask me. Plus he has to do some stuff to modify MSET at runtime to show "-E" or whatever for emuNAND, Plus by that logic Pasta isn't a CFW either because it only changes 8 bytes and "only" disables sig checks.It's just emuNAND and nothing more. It doesn't allow anything that normal firmware doesn't, hence not CFW.
but NTR has debugger and pluginsNTR is debatable because it never touches ARM9 FIRM, but it messes with ARM11 FIRM.
emuNAND counts as a CFW if you ask me. Plus he has to do some stuff to modify MSET at runtime to show "-E" or whatever for emuNAND, Plus by that logic Pasta isn't a CFW either because it only changes 8 bytes and "only" disables sig checks.
thanksHere's a list:
Tell me if I'm missing something.
- Yellows8's CFW (Leaked by govanify)
- Palantine's CFW (Modified from yellows8's)
- PBT-CFW (Modified from palantine's)
- Dual-emuNAND CFW (Modified from palantine's)
- TRICK CFW (PBT + Dual-emuNAND + Palantine)
- rxMode
- NTR-CFW 1.0 (old 3ds)
- NTR-CFW 2.0 (new 3ds)
- Gateway
- MT-card (Was used for cartless emuNAND on 4.5 before rxMode came to life)
- Some more clones, not as widely used.
- Pasta
- Pasta MSET version
- Unreleased: KARL
- Unreleased: Govanify's CFW (He teased it on his site, so I guess it gets a place here)
- Unreleased: Some other private CFWs.
instead a plain list of cfw, i'd like to see a list of cfw with descriptions, and what they can do.
emuNAND is emuNAND. CFW is CFW. Things can be both, but not neccessarily.NTR is debatable because it never touches ARM9 FIRM, but it messes with ARM11 FIRM.
emuNAND counts as a CFW if you ask me. Plus he has to do some stuff to modify MSET at runtime to show "-E" or whatever for emuNAND, Plus by that logic Pasta isn't a CFW either because it only changes 8 bytes and "only" disables sig checks.
What is a Custom Firmware by your definition?emuNAND is emuNAND. CFW is CFW. Things can be both, but not neccessarily.
They are two separate, distinct things that really have nothing to do with eachother.
Honestly I think you're twisting terminology to fit your definition. "emuNAND enabled FW" just doesn't make any sense to me, emuNAND IS the FW.What is a Custom Firmware by your definition?
Anything that even if it is just a hack of the original firmware allows some different functionality, like e.g. allowing to run unsigned code or redirecting read/writes from NAND to SD?
PS: If you didn't notice you can't redirect with the normal firmware, so rxTool ALLOWS you to do something the original firmware CAN'T.
Something completely custom not based on the original firmware?
Something that let's you play pirated games?
As for me, I think the first one is the definition of CFW, so emuNAND enabled FW is a CFW.