because cfw just means custom firmware, it is used to describe a whole lot more than just rom loaders, ....i can understand "why" people jump to that assumption, but it doesn't make the assumption correctAfter psp and ps3 CFW's why wouldn't they?
because cfw just means custom firmware, it is used to describe a whole lot more than just rom loaders, ....i can understand "why" people jump to that assumption, but it doesn't make the assumption correctAfter psp and ps3 CFW's why wouldn't they?
Nothing to do with the PSP. I was active in the PSP homebrew community from very early on, and custom firmware was simply custom firmware, because it was custom firmware. Not sure where this 'cfw = rom loader' business has come from. Just a bunch of dumb, new kids? I dunno.After psp and ps3 CFW's why wouldn't they?
Nothing to do with the PSP. I was active in the PSP homebrew community from very early on, and custom firmware was simply custom firmware, because it was custom firmware. Not sure where this 'cfw = rom loader' business has come from. Just a bunch of dumb, new kids? I dunno.
yeah, a cfw could just be a version of the fw re:d to change a colour of a certain button for example.
The moment this comes out, someone is going to modify it slightly and release "YAKARL3DS".
The 50ish unreleased homebrew apps I made can attest to that.
Sweet new leaked details: our custom firm literally only changes all instances of 'A Button' to 'C Button'. Sorry to disappoint anyone expecting more.
Cool, so we can support N3DS without using Cubic Ninja. Gateway doesn't matter any more.You mean the moment this comes out, Gateway 3DS will release their New 3DS support. scumbags.
Cool, so we can support N3DS without using Cubic Ninja. Gateway doesn't matter any more.
i would say the closest we have got to a true CFW would be cearps whitelist blocker as that is installed to the system and works at bootup to achieve its goal, granted all it does is disables the NDS whitelist....but i think the fact that once its installed its done, and its actually installed to sysnand imo is more true to the definition of a cfw....then again there isnt too much "custom" to it, its more just a feature blocker, rather than an additional/alternative feature
Once again, this isn't a place for discussion of the morals of piracy. It's true that people need to stop being entitled, though. If you want to make what we made, there's more than enough information out there for you to do that. If you can't, just sit tight and you'll get something eventually.
well technically it is modified to use a much higher revision number as you cant actually install a older title over a newer one, and really it could install anything at all not just the older whitelist, all it does is breaks the whitelist rather than replaces it, as the TMD is modified the signature is broken so it just fails to load effectively making no white-list be loaded at all.....as i said i know its not actually a cfw, but IMO its closer in some respects than cfw "rebooters"That's because there's nothing custom about it. All that does is install an old version of the whitelist title. It's signed by nintendo and everything, thus why it sticks around after reboot. It's like mixing and matching titles on the Wii.