Custom Firmware 3.52 M33-4 Update

[xg917]

if u lose 333 for some reason press home and set clock speed to default then press home to get out of the menu, then press home again to go back into the menu and set it to 333, it should be changed. it worked for me because i noticed my clock speed got slower somehow.

[Fanjita]

ab88

Yes they most certainly did praise m33 for the 3rd update. And all other m33 firmware updates. If they removed it now then whatever so YOU get YOUR facts straight. in fact up until now most CFWs I have I downloaded from there and every single readme up until now is unaltered (same as files from this site). Why this time? For the reason I already mentioned.

You realise, right, that they don't tend to add "this file has been edited by us to make us look better"? The edits tend to be relatively subtle and insidious, and of course they get away with it because most of their visitors are ignorant leeches that don't care anyway.

The one good thing to have come from all of this is a little user education. The only question is whether the cost was worth it.

[Cloudhunter]

Just because DAX and fanjita say somthing doesnt mean you have to agree with them. They are not God. We are all entitled to our own oppinions. So do not calll us misinformed or act like we are flaming noobs. If some of us have stronger morals than others so bit it. The truth is that m33 put somthing in their code that they knew would end up bricking psps. They may have given warning but they had to know it would end like this. they wanted this war and could accept a few casualties. In my mind this puts them in the wrong.

and frankly I dont believe in such blind faith.... even if they killed sombody? follow who you will, thats your choice, as i said i have more moral than most people. But to follow somebody knowing they killed someone, dont you see the flaw in that strategy?

Frankly, you need to STFU with this useless flaming.

The fact remains, that DAX and Fanjita are HIGHLY respected members of the scene. So, of course people are going to listen to them. They also agree that what M33 did was correct - aswell as 99% of people now that they have been presented with more evidence.

So, go suck a lemon.

Cloudy

[BelmontSlayer]

M33 put NO MALICIOUS CODE in their release. The "security measure" was placed by $ony. It corrupts an EBOOT if anything is changed in it. PS3News hex-edited the EBOOT and corrupted the update. That is what caused the bricks, not M33.

Get informed or just don't say anything.

[Cloudhunter]

I'm sorry, but I have to post this about the PS3n00bs drama.

"Attention All Visitors: Read In!" and "Update" - A Dramatic Reading by FreePlay

I just have to say "LOL"

Cloudy

[DPyro]

:rofl:

[Chameleon]

All ive got to say is WoW!!! :rofl::rofl::rofl:

[BelmontSlayer]

I just have to say "LOL"

+1

[FreePlay]

I just have to say "LOL"

*bows*

M33 put NO MALICIOUS CODE in their release. The "security measure" was placed by $ony. It corrupts an EBOOT if anything is changed in it. PS3News hex-edited the EBOOT and corrupted the update. That is what caused the bricks, not M33.

Get informed or just don't say anything.

Uh... actually, Sony has nothing to do with it.

The M33-3 update uses the EBOOT's checksum as its own decryption key. If the EBOOT is modified, the data decrypts improperly. It's M33's code that flashes the data, not Sony's.

but yes, irlolin.

[monkvash]

i think i brinked my psp using this cuz i didnt update 2 m33 3.52 i was on m33 3.51 =((((( now my psp wont turn on ,



*EDIT - i can get into recov menu just have 2 wait for battery 2 be 75% lol thank god for recov menu , god im stupid