1 Attachment(s)
Custom Firmware 3.52 M33-4 Update
Via M33 Forums comes a new version of the Custom Firmware for the PSP, Heres the details:
Spread this news
IMPORTANT: agree with LICENSE.TXT conditions before installing the program.
Changes in M33-4 (mainly bugfix)
- Fixed the bug that caused CRC error when writing to flash usb in the XMB. Now writing
is OK.
- Added the new speeds to vshmenu and core, because we forgot in recovery.
AS we didnn't want to release a new update without something new, we worked in making
3.10/3.11 to work with popsloader, and that's it, the new popsloader plugins supports them.
Instruction for 3.10 and 3.11 are same as 3.30: you need pops.prx, popsman.prx and pafmini.prx
with the correct names in popsloader directory. And remember that savedata of 3.10-3.30 are incompatible
with those of 3.40+. We'll research if a solution for this is possible.
Team M33
---------------------------------------------------------------------------------------------
As for yankee paranoids, a little word about the "brickers" issue.
We repeat it again: THERE IS NO MALICIOUS CODE inside M33.
Some of the files of this update are protected by encryption schemes to protect ourselves
from that page that annoys homebrew developers.
The keys for the decryption: the own update file.
So if the file is changed, the decrypted data is not the original one, and this causes the
wrong data to be written. There is no way you can call this malicious code as there is no explicit
code to brick nothing, it is the corruption of the update what actually causes the bad decrypted
data to be written.
Anyways in this update we check if decrypted data is wrong and in that case we write a recovery
warning the user what happened. It will activate usb, and it will allow you to execute a recovery
eboot.pbp... in a curious path ("ms0:/PSP/GAME/PS3NEWS_ARE_STEALERS_I_AM_NOT_GONNA_VISIT_THEM/EBOOT.PBP")
which is not at sight of an hex editor
If you visited ps3news and bricked in last release, then blame his administrator.
He is the one that modified the files and had them in the server for lots of hours
knowing the consequences.
Spread this news
We (DCEmu) warned users that some people were getting bricked because the had visted ps3new.com, and advisted you to clear you cach before upgrading, it turns out we were wrong and it was only users that had downloaded from ps3news.com that were getting brick (and know we know why).
We would like to apologise to M33 and our readers for that incorrect warning.
but as always: Update at your own risk, we are not responsible to what happens to your psp using this!
Download and Give Feedback Via Comments
