Updating 3 52 m33
Thanks, I actually ended up deviating from the above slightly.
Here's what I did for anyone else facing the same issue.
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.
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. So if the file is changed, the decrypted data is not the original one, and this causes the wrong data to be written.
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.
Changes in M33-4 (mainly bugfix) – Fixed the bug that caused CRC error when writing to flash usb in the XMB. – Added the new speeds to vshmenu and core, because we forgot in recovery.
I tried to do it directly but of course it wouldn't work, so I tried to update to 3.52 M33-2 (the next logical step). I'm using an 8gb card now, you think that may be causing a problem?
I've done this a few times with older updates but never had a problem.
Then run Hellcat's Recovery Flasher to update.
Note the second source link details precautions you may want to take the most pertinent is making sure your battery is fully charged when updating.
Yeah, I just did all that and the same thing happened, it just froze up.