- Joined
- May 13, 2013
- Messages
- 402
- Trophies
- 0
- Age
- 30
- Location
- East Brunswick, New Jersey
- XP
- 438
- Country
I just got back into using my 3DS and made the jump from gateway to Luma, but want to know more about what's going on.
There's actually a cfw that removes the need of an amiibo at allI just got back into using my 3DS and made the jump from gateway to Luma, but want to know more about what's going on.
what do you mean?There's actually a cfw that removes the need of an amiibo at all
This isn't a custom firmware...
I'm gonna be that one asshole and say since it patches a firmware module it actually is a custom firmware.This isn't a custom firmware...
That's a patch, not a custom firmware. In actual terms, Luma (and all the other "custom firmwares") isn't a custom firmware. It's a loader with sets of memory patches. I guess at the time of conception, it was more simple for the layman to refer to these loaders as "custom firmware" and it just stuck.I'm gonna be that one asshole and say since it patches a firmware module it actually is a custom firmware.
it replaces a firmware module, custom firmware.That's a patch, not a custom firmware. In actual terms, Luma (and all the other "custom firmwares") isn't a custom firmware. It's a loader with sets of memory patches. I guess at the time of conception, it was more simple for the layman to refer to these loaders as "custom firmware" and it just stuck.
Semantics aside, NoAmii still wouldn't be considered a custom firmware as far as 3DS terminology goes because it's just a system module that replaces the native NFC module in memory, which requires a custom firmware to even make use of.
Through memory patching...If it permanently replaced it on the NAND it'd be closer to being called a custom firmware, but even then it'd just be a firmware customization. "Custom firmware" is firmware that replaces the entire stock firmware, which nothing in the 3DS scene does.it replaces a firmware module, custom firmware.
the firmware module is still replaced, no? therefore it is a custom firmware, albeit temporary.Through memory patching...If it permanently replaced it on the NAND it'd be closer to being called a custom firmware, but even then it'd just be a firmware customization. "Custom firmware" is firmware that replaces the entire stock firmware, which nothing in the 3DS scene does.
No, that's a fallacy. Think of something like Action Replay or GameShark. It's the exact same concept. "Custom firmware" denotes that the entire stock firmware is entirely replaced, and in this case it's not.the firmware module is still replaced, no? therefore it is a custom firmware, albeit temporary.
When using this the firmware isn't the same as before, if it's not the original then it's the custom firmware, the entire thing doesn't need to be replaced for it to be different.No, that's a fallacy. Think of something like Action Replay or GameShark. It's the exact same concept. "Custom firmware" denotes that the entire stock firmware is entirely replaced, and in this case it's not.
There seems to be some confusion here. Firmware customizations aren't the same as custom firmware. The "custom" implies that the firmware itself was developed from the ground up in order to be a replacement for the factory firmware of a device. Android ROMs are custom firmware, for example. When it comes to the 3DS we're just throwing memory patches at the factory firmware. Think of Luma and all the others as add-ons for the stock firmware. They enhance the firmware, but they don't actually replace it. However, now that sighax is available to everyone, writing a true custom firmware complete with custom home menu (think of an XMB or Xbox Dashboard style menu) is totally possible now. This makes me rather nostalgic for the PSP days when people actually did this. It's a shame nobody has put forth the initiative with the 3DS yet.When using this the firmware isn't the same as before, if it's not the original then it's the custom firmware, the entire thing doesn't need to be replaced for it to be different.
I don't know what kind of argument this is, a customization to a firmware of any kind means it is a custom firmware, unless my definition of the word custom is wrong.Firmware customizations aren't the same as custom firmware
Alright so, for whatever reason I'm not conveying this properly enough. Again, a "custom firmware" is a homebrew firmware that replaces the entire firmware of a device. I used Android ROMs as an example because I honestly can't think of a better one. Actually, I take that back. Check out Rockbox. That is a true custom firmware. It totally replaces the factory OS of whatever device it is installed on. Customizing the stock firmware isn't the same as installing a custom firmware. Just because you patch the UX style DLLs on Windows and install a custom visual style doesn't mean it's not Windows anymore, right?I don't know what kind of argument this is, a customization to a firmware of any kind means it is a custom firmware, unless my definition of the word custom is wrong.
I completely understand where you're coming from, and what you're saying logically seems more correct. It technically is a custom firmware, since it's not the original and meant to replace the original, also made by the community, it's custom.Alright so, for whatever reason I'm not conveying this properly enough. Again, a "custom firmware" is a homebrew firmware that replaces the entire firmware of a device. I used Android ROMs as an example because I honestly can't think of a better one. Actually, I take that back. Check out Rockbox. That is a true custom firmware. It totally replaces the factory OS of whatever device it is installed on. Customizing the stock firmware isn't the same as installing a custom firmware. Just because you patch the UX style DLLs on Windows and install a custom visual style doesn't mean it's not Windows anymore, right?
Then a firmware with that patch is a custom firmware but it itself isntWhen using this the firmware isn't the same as before, if it's not the original then it's the custom firmware, the entire thing doesn't need to be replaced for it to be different.
Lol
"I made my own, custom lego build out of this lego pack by adding shit on top of it and changing a bit here and there" is technically correct to say. Custom means (afaik) that it was "costumized", or modified to your liking, and not built from ground up. A custom 3ds cover can be a cover bought from some place and which afterward was painted and stuff to your liking, not built from ground up (you didnt 3d print the thing) so adding patches makes a firmware - custom, but the patches themselves arent a firmware, let alone a custom firmware, and the given thing is a patch/module and not an entire firmware, so talking about what a cfw is or isnt even related hereThere seems to be some confusion here. Firmware customizations aren't the same as custom firmware. The "custom" implies that the firmware itself was developed from the ground up in order to be a replacement for the factory firmware of a device. Android ROMs are custom firmware, for example. When it comes to the 3DS we're just throwing memory patches at the factory firmware. Think of Luma and all the others as add-ons for the stock firmware. They enhance the firmware, but they don't actually replace it. However, now that sighax is available to everyone, writing a true custom firmware complete with custom home menu (think of an XMB or Xbox Dashboard style menu) is totally possible now. This makes me rather nostalgic for the PSP days when people actually did this. It's a shame nobody has put forth the initiative with the 3DS yet.