more reading here.  http://forums.qj.net/f-psp-general-7/t-brickedand-it-isn't-even-mine-117238.html#post1722840

and her is my first post.

Quote:So i had my boss's son's psp in my hands today. Updated from 3.40oe to 3.55m33.
No problem
Installed SchmilKeNBerrieS for him...no problem
Rebooted, copied over the mp4s of the dvd video wee converted...no problem
Went and ran the m33 update 2 and it hung at the PSP splash screen...then turned off. (Ive done this MANY MANY times over the past week with no problems on mine and a few guys at work)

Now its permabricked. Turns on with a green light...nothing else...and it doesn't even turn it self off after a while.

The only thing i can think is that the m33 update 2 that i used had been touched by the patchSFO program a few days ago while I was figuring out why psfiler wouldnt work for someone using my theme.  

GRRRRRRR

So an hour of messing with it with no luck of making it better and I finally got the guts to tell him that its bricked...he looked at me funny and i showed him what it did and he didn't say anything else. Just packed up his laptop and went home.  

This is a bad day for me.  

But mine still works LOL NAHAHANAHANAHANNANA

There's my story....and I'm trying to figure out what exactly caused this.

So, I'm asking you fine fellas, does anyone have a UP chip installed and would like to do some testing and figure out what part of this spoon went wrong??

Thinking more about it, the last thing i added to schmilkenberries is the common_gui.prx from here and I don't remember if i have run the m33 update2 since then.  But basically i want to know if my m33 update file is busted from patchsfo...if something in my vshmain.prx which causes some homebrew not to work, caused the m33 update 2 not to work, or if its common_gui.prx related...

I have no idea...the update program didnt even get passed the psp splash screen ( i don't have a modified gameboot) it just splashed and showed PSP then sat for 3 seconds and shut off.  :(



If someone has a UP I'll sendspace all the files.

Thanks....this totally sucks...I need an unbricker in the USA if anyone knows one...

(This post was last modified: 08/08/2007 04:24 PM by SchmilK.)

is your boss going to be pissed that you bricked his kids psp

Have no idea.  Some random guesses:

• The updater replaced certain PRXs making your customized ones incompatible or something, or the customized PRXs stuffed the updater up
  
• Possibly PatchSFO, but I'm doubting that swapping an SFO would cause the executable section to suddenly act differently

Oddly, if it hangs at the splash screen, the program shouldn't even be executing, which would suggest an issue with the SFO, however if nothing is being executed then really you can't brick.

I'm with you there zinga...

So thinking about it while driving home and reading the thread on qj in traffic LOL, maybe there is something to do with the idstorage key because i never ran the key cleaner on his previously...and didn't even think about it today until driving home.

I don't know...I found a guy in California that will do it for $40 with free shipping.  Can't realy beat that i guess.

Thanks for your thoughts...I've been fixing computer problems for 16 years and it just realy baffles me as to what happened.

(This post was last modified: 08/08/2007 06:15 PM by SchmilK.)

exactly right. the only way to be sure is post the file and see if someone with the modchip can run it and see what happens. my gut instinct is that it was read/writing one of the core firmware files when it shut off thereby corrupting it. as these guys say - it does not and can not run the updater till the screen fades. this never happened so it has to be to do with the crash itself. i assume you did the obvious and took out umds and memory sticks, and also tried getting into recovery? did you drop the psp? i assume you tried removing the battery just in case the psp was in hibernate mode and not shut down. anyway things to try - i hope its something simple for ya to fix. worst case is that the psp itself is dead and that means new mobo.

a small thought - if the sfo was the cause wee may have another new exploit to work with :) i know sfo corrution has been done to death but you never know.

(This post was last modified: 08/08/2007 06:30 PM by Anger.)

ALRIGHT....partially solved...no blame should be put on patchsfo, nor any modified/recompressed prx files.  it HAS to be idstorage/ta082/ta086 related.  I (out of boredom and frustration) just ran the exact same m33 update 2 eboot after intalling the exact same theme files and it worked fine on my ta079!  

SO...it HAS to be idstorage or something else with the motherboard......

(This post was last modified: 08/08/2007 07:47 PM by SchmilK.)

^^ lol i wouldnt be surprised if that's the issue, i downgraded a psp once and it rebooted with the screen off, all i did was push the brightness button, its definetly worth a try :P