Via Noobz
There's been a bit of a storm recently, with an awful lot of people's PSPs being bricked by a broken version of the latest M33 custom firmware, deliberately distributed by a certain disreputable piracy site. Here's my take on the whole situation, and maybe a ray of hope for those people who have bricked.
First off, let's talk about that ray of hope. We've been looking at the M33 code, and trying to understand exactly how these bricks have come about. The good news is that we think there may be a way to undo the bricking process in this case - in other words, we hope to be able to develop a way to fix those bricks in the near future. At this time, this is just for the M33 bricks. I can't predict exactly when this might be ready (it should be very soon), but maybe it will save some of you the hassle and expense of sending your PSP off to be repaired.
So what actually happened to cause these bricks? It's pretty simple, really. The M33-3 firmware installation process relied upon a delicate decryption algorithm. That algorithm was tied to the contents of the installer program, which had the side effect that if the installer was modified in any way, then the data being flashed to the PSP would be corrupt, and so a brick would result. Now that seems pretty dangerous - but they did at least put a warning in the README.TXT and LICENSE.TXT files, to warn people about it:
Not respecting the license will bring the PSP to BRICK, because the program will refuse to run.
You are however NOT allowed to modify the installer, the readme or this license, including the removal of one or more of them. Modification of installer covers all: icon, image, executable code, text, etc. These kind of modifications may end in the software refusing to work.
Unfortunately a site with a long history of taking homebrew releases, and modifying them to their own ends, got hold of this release, modified the credits and removed the warnings, then posted it on their site for download. So of course, people started to brick their PSPs. What's worse, is that even when the problem was identified, the site in question chose to try to cover it up by editing user comments, and did not take any action to fix the problem for at least 24 hours, leaving it up for download even when they knew about the damage it was causing.
Sadly that's just indicative of the attitude of that site to both its users, and to the authors whose work they rip off. They've been doing this for years - through the PS2 scene, then PSP, and now PS3. They've ripped off our releases, and attempted to claim that we're inciting piracy (which is ironic, if you're familiar with the content of their site). Any attempt to reason with them and get them to show some sort of respect and common decency has fallen on deaf and arrogant ears.
Now though, they seem to be starting to realise that they're not immune to the attentions of the homebrew community at large, and not untouchable. They've offered to correctly credit releases, both retrospectively and in the future. Time will tell whether an amicable agreement can be made, and whether it will be honoured, but we can only hope.
Personally, I have very mixed feelings about all this. On the one hand, lots of innocent bystanders have had their property damaged, just so that one bad apple can be brought back into line. I would never condone an action that would hurt someone else like this, without extreme personal provocation. We always strive to make sure that Noobz releases are as safe as possible, and can be trusted completely. But on the other hand, this is the first time ever that the offending site has paid any attention to anyone. If their antisocial behaviour has been curbed, then maybe it has been worth it. I guess sometimes you just have to fight fire with fire. I only hope that next time, innocent bystanders can avoid becoming collateral damage.
They only plan on having it work for those PSP bricked by the hex edited m33 flaser, but we are also hoping that it will extend farthe then that, to say PSPs that bricked due to a bad dxar
