HACK: a functional bin loader on track!

News via http://www.pspgen.com/hack-bin-loade...te-193026.html

If you're one of the new members of the community underground, do not worry we will resume here the main points of why exploits.
Since the arrival of new motherboards with waterproof kit SDC / XGen pandora, the only way to hack the laptop from Sony is ... using a fault. This is not new and every system has flaws. Today, the goal of PSP developers is to find one that will run unsigned code (as chickHEN of Davee) to patch the installed RAM and a subsequent custom firmware not permanent.
So the arrival of the PSP Go (and 6.20firmware) which opened hunting faults and unfortunately many dissemination fakes. However some info we challenge and we now have high hopes for the PSP hack inflashables (PSP2000 TA088v3, PSP3000 and PSP Go!, Especially in a higher firmware to 5.03 prevent the use of chickHEN).
Some time ago, a developer named Flyer said he found a flaw savedata in a game set name was not revealed to avoid seeing this flaw mouthful Flyer embarked on writing a bin loader!

little evidence of the fault
With the support and monitoring of several serious and experienced developers of the PSP scene as Wololo and n00b81 Flyer that has pursued his project and has set up a bin loader (e-loader) for this fault backup. What does this mean? It is possible to load bin files as if Sony had signed.
Could this be the beginning of a new hack? Probably yes, but as you know, once the game title and announced the exploit release, Sony would need 48 hours to fill all this. Besides it should also be a flaw Kernel in order to launch homebrew and iso.
But for now, seems determined Flyer has his job releaser. When? we do not know but you will be aware of this progress when we have something new.
However, an alternative to this seems to exist, actually Flyer said it had discovered another flaw backup but this time in a freely distributable demo. This would be less trouble for the release as a demo is available for everyone. Yet to be seen whether the bin loader could be made "compatible" with this new vulnerability.
Again Wait and See, but the path to a new hack seems to draw slowly. Avoid then update your firmware (especially if a new official firmware appeared).