Custom Firmware 3.52 M33-4 Update

[jamotto]

I understand what M33 was trying to do, but they went to far. It would have been more than enough to prevent the eboot from running if it had been altered by exiting back to the xmb. Instead they allow the update to run as though nothing is wrong. They wrote up a "ban" list containing false information on what would take to brick your psp. Heck, they didn't even give a means to tell if the the eboot is bad or not via a checksum. I don't think ends justify the means.

[Gizmo356]

But before you flash you agree to take all responsibility so you can't really blame them.

[scarph]

if they really claimed it as their own it would say 3.52 ps3news-4 when you went to system info

it says 3.52 m33

remember that

[jamotto]

But before you flash you agree to take all responsibility so you can't really blame them.

The eula does not protect m33 from all responsibility. It only protects them from things outside their control. Things like hardware failure, acts of god etc. This however is different, they have full control here.

[mike_jmg]

so tha mothafukka owner of ps3news was the one responsable of all this shaitz

what are his modifications about??, puting a logo or something, what an ass

Now, that this is clarified I'll update and see what is this about

Just let me get this straight, dcemu hosted files = no bricking right

edit: forget it, just did and worked

[MicroNut]

Actually in a scenario like that Sony could be held responsible as they have been in the past, It is common practice to write your code or make your products to withstand tampering and modification.

In a small way I understand your point.
Update with an official firmware and the software bricks,
Good reason for a warrenty.
Good reason to download it from Sony.
Would you tell Sony you downloaded your update from a non-official site when asking for warrenty?

On the whole however the point is completly lost.
I am going to hold Sony responsible for Custom firmware?
Could I hold them responsible for a maliciously hex edited official update?
Not likely.

PS3news did what they did knowing the outcome.
They were warned in advance and did nothing to prevent it.
Instead they did it anyways.
And good people got hurt.

[urherenow]

Don't get me wrong, I like what M33 is doing, but I wish that they would have outlined it clearly in their readme or something, that getting the program from these specific sites could potentially brick your PSP, and then explain why.

1. ummnnn.... it WAS in the readme. PS3 news probably cut that part out of their package.

2. I still don't get this nonsense about ripping of other's work and playing it off as if it were thier own. GIVE ME 1 FRICKEN' EXAMPLE OF WHEN THAT SITE DID SUCH A THING? Most of your are simply talking out of your rear end because you don't know what you're talking about in the slightest.

3. The only thing they edited (or try to) was the bit in the program and the readme that simply BASHED thier site.


Having said that, I looks like I'll have to say this yet again. It is a site that is in it for the mony and therefore will post and host anything and everything related to PSP even if it was a ripoff or illegal (containing sony .prx files or whatever). They have always given credit where credit was due (or at least to whomever PROVIDED THE FILE TO THEM AND CLAIMED IT AS THIER OWN) INCLUDING PRAISING TEAM M33 FOR THIER NEW RELEASE!!!!!

Yes, caps intended because many of you are just jumping on the bandwagon and can't get it through your thick skulls exatly where the problem lies. M33 is Pissed because (Wildc*rd ???) Stole thier code and released thier own firmware and taking credit (or too much credit... neither here nor there for this conversation). PS3n*** hosted it and will continue to host it and future releases of it. They don't care. They will host anything as long as the entire staff isn't aware that a file will brick PSPs and then they will remove the file. This is the only sin I've seen the sight commit, although that's sin enough for most people.

I had about 6 or 7 other points to make but lost my train of thought.

anyways My final, unwavering word on the whole matter is this: Kudos for M33s progress and thank you so much for continuing development of custom firmware...

but PS3news AND M33... shame on you BOTH.

and PS if Wildc*rd was the wrong team to mention, please don't take it personal, I'm just trying to get a point across.

[armyStrong]

The eula does not protect m33 from all responsibility. It only protects them from things outside their control. Things like hardware failure, acts of god etc. This however is different, they have full control here.

I'm pretty sure they didn't have any control over an outside force tampering with their code...

I think a checksum would have been nice, but if it was never necessary in the past, you can't possibly expect m33 to have predicted that it would have been necessary for this release because some idiot screwed around with a hex editor.

It just seems like the lot of you need something to complain about. Nice work m33...I for one will continue to support your work!

[Chameleon]

It just seems like the lot of you need something to complain about. Nice work m33...I for one will continute to support your work!

Thank you

M33 is a great team and even if they killed someone I will still support them.. they fixed my brightness issue i was having :thumbup:

@ urherenow- im not the only one saying this sh*t maybe this thread will shead a little light on your false reality!!

[Spotfist]

Hey how come the zip file is said to be passworded but when I downloaded it, it's not? I just wana make sure no1 has been tinkering with the file.