You seem to forget that companies are out there to make money, and purposely putting tools for piracy into the hands of the users is... not the way to make money.
but they do it
http://www.youtube.com/watch?v=WJIuYgIvKsc
You seem to forget that companies are out there to make money, and purposely putting tools for piracy into the hands of the users is... not the way to make money.
Yes it is possible that TB got access to original disc debug fselfs, but that is almost as likely as me having access to debug executables of mario kart 7, Super mario 3D land and New Super Bros 2 and playing backups of them right now, on a dev 3ds. Unless they have connections with an employee for each of the companies which developed each of the games they've managed to patch, they don't have access original debug fselfs.Source:Myself/Knowledge of PS3/looking at TB eboots. There are many speculated methods on obtaining decrypted eboots, which mostly surrounds dumping the RAM, in some form (and having the keys, but having the keys is unlikely). Nothing confirmed of course. But they are re-encrypted versions of the original disc eboots, I haven't checked Duplex's 'anti-drmed' TB eboots, but they should be the same size as the disc original eboot. When they say debug eboot, they mean an eboot flagged as debug in the SCE header. Again TB obtain decrypted eboots (to which they apply DRM to) from a source other than debug fselfs(that is unless they get debug copies of every game they've patched again unlikely). What you see when you look at a TB eboot, is simply the result of their DRM process. The fself flag among other things in the SCE Header, is simply a way for the DRM distinguish between regular eboots and TB eboots(after all, all a SCE header does(for selfs) is tell the PS3 what the eboot is). Especially since fselfs are treated differently by the PS3 simply for been an fself(it has to be modified to accept them). And of course the encryption of TB eboots is part of the DRM.
EDIT: If you don't believe me, here's a quote from the dev wiki regarding the 'fself nature' of TB eboots:
I get what you're saying, true FSLEFs aren't encrypted. But that doesn't mean that the decrypted EBOOTs TB have access to aren't the debug EBOOTs (i.e. FSELFs). As I see it, it is perfectly possible they have access to the FSELFs (debug EBOOTs) of the games they release "patches" for, and they apply their DRM to those (including the encryption with their own keys) so they only work with the dongle. I see no other way for them to obtain decrypted EBOOTs for newer games unless they had all the newer keys, in which case they could release far more fixed games than they do. They could possibly also create some sort of software to allow users to fix games themselves (without giving the keys away; that part could be tricky, but they've managed to protect their EBOOTs this far, they could probably have a decent attempt at protecting the keys also). AFAIK, the only way to get unencrypted EBOOTs is debug EBOOTs (FSELFs), so that must be their "starting point" for each fix, right?
EDIT: The quote from the dev wiki you posted is found under this header:
I wouldn't put too much faith in that quote...old talk
(seems obsolete and incorrect in many ways)
My god. Read the thread. NO HOMEBREW CHANNEL. This is like the first tiny baby step of hacking the console. Read the stickies.it is true 3ds firmware has been decrypted and now you can make homebrew channel like the wii or not
and thanks
So some of us talked to him and he said this. No luck guys.[19:12] firmware isn't really decrypted
Well if it's decrypted, then you can take a peek into the lowest level of code next up from the bootloader.So what can a decrypted firmware do?
add1- (couldn't read the whole topic)
I would be hey with a home brew channel like the wii.
My god. Read the thread. NO HOMEBREW CHANNEL. This is like the first tiny baby step of hacking the console. Read the stickies.it is true 3ds firmware has been decrypted and now you can make homebrew channel like the wii or not
and thanks
Interesting, I wonder tho if this is just gotten from a hex editor or somthing?Well there is now a page on 3DBrew regarding the format of firmware files http://3dbrew.org/wiki/FIRM
https://github.com/3dshax/ctr was just updated an hour ago. Someone let me know if these updates from me are a waste of time. I don't know what they mean, I'm merely relaying them for anyone else who might care. The previous update was 5 days ago.
No. no there isn't. As mentioned by me way earlier, this is like a tiny little baby step.Something big is brewing i cant wait.