Lets Not Go Down the Wrong Path - Keep Brickers Out of Homebrew

I was very vocal about this subject yesterday and my current view on it is that M33 have every right to defend their firmware from sites like ps3news, but I don't agree punishing users for going to that site, or even telling users that they can't go there.
M33, as good as their firmware is, are not the Homebrew Scene Police.
I don't say this to offend Team M33, but to let them know that they don't control the scene.
Compare this to releases by DA.
He took more shit that M33 ever has, and never retaliated like that.
Do the right thing, M33, and don't code this bricker into the next update.

Quote:

---

Originally Posted by dejkirkby

I was very vocal about this subject yesterday and my current view on it is that M33 have every right to defend their firmware from sites like ps3news, but I don't agree punishing users for going to that site, or even telling users that they can't go there.
M33, as good as their firmware is, are not the Homebrew Scene Police.
I don't say this to offend Team M33, but to let them know that they don't control the scene.
Compare this to releases by DA.
He took more shit that M33 ever has, and never retaliated like that.
Do the right thing, M33, and don't code this bricker into the next update.

---

Stop sugar coating the situation, what M33 did was wrong, we don't need a team of coders like them, all their respect imo is gone, we can do without them, they won't and can never replace mr dark alex. I will always stay with 3.40 OE-A, no need to get greedy because stuff like this happens, down with M33.

Quote:

---

Originally Posted by Nikolaos

Stop sugar coating the situation, what M33 did was wrong, we don't need a team of coders like them, all their respect imo is gone, we can do without them, they won't and can never replace mr dark alex. I will always stay with 3.40 OE-A, no need to get greedy because stuff like this happens, down with M33.

---

Woah, I aint sugar-coating anything!
Read my previous posts on this if you don't believe me!
But there are always two sides to a tale. I have read psot after post, on forum after forum on this and M33 while not being blameless, are only defending their property. I think they went about it the wrong way, but I'm not M33!

I have two psp's
as of yesterday, both were on 3.52 M33-2 running applecor.
neither had ANY differences in their flash other than those attributed to one psp being ta-079 and the other being ta-082.
PSP1: successfully upgraded
PSP2: with same memory stick used to upgrade PSP1 BRICKED.

nuff said. It can upgrade one psp, and then brick another on the same memory stick. there's something more broken than a mere CRC check.

i think u should only use the update once to avoid any problems. if u wanted to update the other psp u shouldve just transfered the update to your memory stick again. i updated my psp which was ta-082 and it updated successfully :)

Quote:

---

Originally Posted by xg917

i think u should only use the update once to avoid any problems. if u wanted to update the other psp u shouldve just transfered the update to your memory stick again. i updated my psp which was ta-082 and it updated successfully :)

---

I've continually updated both of my psp's using one memory stick in this fashion since dax's 3.02OE... Besides, I didn't write anything to the stick. The file should not have changed at all.

I have used the one stick with the update data to update my two PSP units. Both used the same one and had encountered no bricks from them....

Glad I stayed on OE. If this is true, thats pretty fvcked up, its gona take sometime for the HB community to build trust for its coders again.

Fanjita is right on how the bricking code works (the actual eboot is the key and if its changed, the code kicks in).

As for M33, I partly agree with why they did it and I partly disagree.

However, in the latest release M33-4, they fixed it by making it semi-brick instead of fully brick (included with the update is the ability to recover).

I updated my PSP twice using the same update file and I had no problem (need to downgrade to fix a problem with my photo menu freezing after deleting a picture).

Quote:

---

Originally Posted by zoson

PSP1: Upgraded to M33-3 NO PROBLEMS
PSP2: BRICKED by the very same file that upgraded PSP1.

The file was obtained HERE at dcemu. Both PSP's were running the EXACT(and I mean EXACT) configuration of software/homebrew.

Finally, I have _never_ visited the ps3 site that is so taboo here. Flat out, M33 screwed up. Big time. If the bricker did what it was supposed to do, fine. But it's not, it's hurting people who think they are safe from harm. Personally, I'll never touch another M33 piece of software again, I'm already back running 3.40OE on my surviving PSP. A $170 brick is more than enough reason for me to ignore their existence, and tell everyone their software is garbage that shouldn't be touched.

This is bullshit M33. Your firmware is great, but an intentional brick is stooping to a level lower than plaguarism.

Immitation is the highest form of flattery, M33. Learn the meaning of this saying.

---

Exactly what happened to me, One PSP upgraded fine, the other Bricked :mad: