Regardless on what I believe about the whole piracy issue. I'll still support this project. I may not agree with it's direction, but at this point I'd rather have this then nothing.
I made my views known, but I won't constantly repeat them or argue over them in this thread. I would suggest others do the same. We don't need 20 more pages on the whole piracy debate.
Red avatar, a logo, perhaps for a football club? Waaaaay ahead of you.Everyone should do themselve a favour, and add williamcesar2 to their ignore list.
I do disagree, but really it's just semantics at this point.just the point i was making was that imo for something to truly be a cfw it should work from boot up rather than needing to be started via additional exploits ........I'm sure people would disagree, but that's just my opinion
oh don't get me wrong im not saying i wouldn't class the emunand/rednand options as a form of CFW, obviously they are, but the ultimate goal of nearly all cfw's i would imagine would be to get it loaded up on bootup, obviously where that's not possible i wouldn't be disregarding the work of creating "loaded into" CFW's, i was just pointing out that for any cfw most of the time the ultimate goal would be a permanent solution rather than having to boot up the system, then boot into the cfw after its already booted upRed avatar, a logo, perhaps for a football club? Waaaaay ahead of you.
I do disagree, but really it's just semantics at this point.
My personal opinion is that modified system software, whether it be the actual NAND or an SD mounted red(irected)NAND is "Custom Firmware".
Everyone refers to the the PSP as the ideal model for a CFW. But when I got into the PSP scene (PSP 3000), I had to load up a corrupted image, that triggered an overflow, that then allowed me to boot into the CFW. Nobody squabbled over whether or not it was a "true" CFW because it didn't boot directly upon startup.
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.
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.
lol wtf?
I mean, EVERY CFW bar none had rom loading capabilities. After that CFW implied to some people to some degree that <your> system is yours now and <you> make the rules.
The custom in CFW implied you get a non-restricted system that you could customize how <you> chose.
Really? Like the only CFW that was what you described was PRO CFW (since it was open-source), and that didn't come out until basically EOL.
Really loving the progress that you guys are making! Best of luck to you!OK, so I've been working at getting firmlaunch hax all weekend, and while I haven't had success in taking over ARM9 as of yet, I did manage to get my 3DS to do a soft reboot from ARM11 kernel. Which means a regionthree-style region unlock might be possible if I can alter the FIRM launch flags before the launch occurs in order to boot the cartridge slot from firmlaunch.
EDIT:
Seems like assemby code to me
Literally nothing. Looks like ARM9 fopen/fread/ etc and a function that reads code.bin into ram.