U got theme installed?
Did u restore to default setting b4 upgrade?
Any plugins enable in MS?
Wats ur last cfw?
1st PSP working then u musta made sum bad move on ur 2nd.
Printable View
I'm confused when I tried to update I took a while to read what it was saying before I pressed X to update. I then pushed it but I didn't see it say update successful, it reset and I thought it didn't update, so I ran it again and it said I already updated. If it did update it updated VERY fast like 1-3 seconds, I have a 4GB memory stick. I'm not a PS3News person or whatever that site is so no problems there. Anyway I checked my system settings and it says I'm at 3.52-3 and in the recovery menu I have the XMB device new features and stuff so everything looks fine. But it's wierd I can't get my XMB to run at 333mhz (I can tell using the PRXInfo plugin), it's set right in the recovery menu. And when I tried to access the recovery menu like 2 times it wouldn't pop up just the regular PSP start, so my PSP has been acting very wierd. Can anyone tell me how I can get back to 3.52-2 so I can try to update again?
ps- For PSX games what pops version should I use, I think I should choose "original from flash" but I'm not sure.
I'd recover back to 1.50 and reinstall M33 3.52 from there, then apply this patch. It's supposed to install in just a couple of seconds.
If a game you want to play doesn't work with the default POPS loader from flash (3.52), then try with another. If everything works fine, don't bother with the popsloader plugin.
That's the messed up thing, there was no difference between the configurations of the two PSP's. They were both running 3.52 M33-2, with the exact same theme. The only difference was the names of the psp's, and even that was just Zoson and Zoson2...
I guess one is a TA-079 and the other is a TA-082.
I've never had to get back to 1.5 from a CFW how do I do this, you don't have to baby me though I know a good amount of what I'm doing.
Get 3.02 OE-A. In it is a RECOVERY folder. Put the folder in ms0:/PSP/GAME with the update eboot you want to downgrade to, for example 1.50. Rename the update eboot to UPDATE.PBP. Then choose the option from the recovery menu to launch the recovery process and go back to 1.50. Now you can update back to 3.52 M33, and install this patch. :)
my point EXACTLY. team m33 are DIRECTLY responsible for brickage that occurs from now on.
this is the exact reason i chose not to update.
i feel for those of you who will brick because you dont realise what sites are banned. i wont be updating now i know for a fact that there will be some brickage, and even worse is you have to agree to it before hand. would you agree to have your left leg chopped off for the ability to play the latest firmware update? i wouldnt.
Almost any downgrader will work because what they do install a clean 1.50 from a cleared flash0. I prefer using the 3.03 downgrader, just don't follow the instructions that much. For example, put all the files you need on there, and instead of running GTA, just run the X.Y.Z Update from the XMB because your on a CFW, you have Homebrew enabled. Its not an issue of getting it to run, its just....running it. lol.
BTW: Bricking because of where a User went? WOW. Atleast we have Team Wildcard, their better anyway.
um.... my psp wont turn off... help
It only bricks if the eboot has been hex edited, if you download it from a site like ps3news. It does not check your browser history, nor your PSP browser history.
That is the only INTENTIONAL brick caused by this update.
And to answer some people's questions, yes WildC*rd will release a 3.52 firmware sometime.
Cloudy