|
M33 3.52-1 very unstable
|
|
|
sliexx
Junior Member
|
31. July 2007 @ 03:32 |
Link to this message
|
Is there a way to safely revert to 3.51-7 ? I'm sick and tired of all the errors i get while playing ISOs on 3.52-1.
Loads of 800XXXXX errors. Will start to log all of them. So far i've got at least 6-7 different error numbers while tryig to run isos.
And i dont do homebrew. Only isos and psx (psx stuff works fine btw).
Games freeze mid loading, read light flashes, but no loading happens and sometimes i cant get back to XMB without pulling the battery. Card is fine, i've checked. Considering its fake (4gb "sony") i've taken all the tests neccesary to ensure its working - filling it to the last bit of capacity several times and then reading it back. It works properly.
All this crap started to happen after i went from 3.51 to 3.52. Motherboard is TA-082.
I have tried running games with UMD, without umd (M33 and np9660). Same stuff happens.
At one point none of PSP native games were running. Past PSP logo just black screen and i have to pull batery to reset. I have turned all 3 Advanced Config toggles off, then somehow PSP isos were starting, but loads of errors and read problems, hangs, crashes...
Any help here ?
I use LUMINES as umd replacement for UMD mode.
Some errors i got while trying to run psp ISOs or CSOs:
80010002
80020148
8002014c
80020321
PS2 slim plugged into 42" sharp fullHD telly; AMD 3500+, 7900GTO, 2gb ram, 700gb hdd (combined)
|
|
Advertisement
|
|
|
|
|
mrmcman
Suspended permanently
|
31. July 2007 @ 06:05 |
Link to this message
|
hmmm never seen those before. try going to 3.52 M33-2.
also, try enabling (yes, enabling) no umd mode (M33 driver or sony NP9600)
(+[__]%) put this psp in ur siggy. just do it.
PSP Firmware: constantly changing, currently GoldenEye.
|
|
sliexx
Junior Member
|
31. July 2007 @ 06:21 |
Link to this message
|
|
Hell no, i've semibricked while trying to go 3.52-2... Had to winstall 1.50 recovery and then back to 3.51-6 > 3.51-7. but as soon as i went 3.52 sh!t hit the fan...
Unless you can walk me thru with update... maybe i did something wrong...
PS2 slim plugged into 42" sharp fullHD telly; AMD 3500+, 7900GTO, 2gb ram, 700gb hdd (combined)
|
|
modster
Senior Member
|
31. July 2007 @ 06:45 |
Link to this message
|
|
Planning to update to 3.52 M33-2.
But got some questions about it:
in the readme english version I noticed this:
"With this release we also a plugin to load pops from 3.40, 3.51, and 3.52"
My question is => What the heck is pops?
Can someone explain to me what pops are? Sorry for being a stupid but I don't know what pops is/are.....
Thanks
|
|
mrmcman
Suspended permanently
|
31. July 2007 @ 07:11 |
Link to this message
|
@sliexx: its the same installation as 3.51 M33. u gotta run the update maker to create the update psar and flasher. just follow the same instructions u followed for 3.51 M33, but sub 3.52 for 3.51.
@modster: im not entirely sure what pops are. i think theres popstation ps1, that may or may not be related.
(+[__]%) put this psp in ur siggy. just do it.
PSP Firmware: constantly changing, currently GoldenEye.
|
|
bu22ard
Senior Member
|
31. July 2007 @ 07:33 |
Link to this message
|
|
@modster pops is the playstation one emulator built in to the FW, it allows you to play ps1 games. you do NOT need to do anything special to get it to work, the complictaed instructions are for those that want to run pops from previous (below 3.52) FW. only a few games need this i believe.
1.52>2.0>1.5>3.40 OE-A>3.71 M33-4
3.60>4.01 M33-2
|
|
modster
Senior Member
|
31. July 2007 @ 09:42 |
Link to this message
|
|
thanks guy,
so all I have to do is update to 3.52 M33-2 and that's all?
Also, when I unzipped the M33-2 file, I got a file "EBOOT.PBP", do I need to rename this to 352-2.pbp? or can I just run as EBOOT.PBP for the update?
Thanks
This message has been edited since posting. Last time this message was edited on 31. July 2007 @ 09:44
|
|
mrmcman
Suspended permanently
|
31. July 2007 @ 10:10 |
Link to this message
|
|
just unzip it to the folder right before the eboot and put it in game150, then run it. its just a little update, it only takes 2 seconds
(+[__]%) put this psp in ur siggy. just do it.
PSP Firmware: constantly changing, currently GoldenEye.
|
|
bu22ard
Senior Member
|
31. July 2007 @ 13:01 |
Link to this message
|
|
spot on, so you should have something like this
ms0:/PSP/GAME150/M33-2/EBOOT.PBP
make sure the EBOOT is in a folder inside game150 though or you get an error
1.52>2.0>1.5>3.40 OE-A>3.71 M33-4
3.60>4.01 M33-2
|
|
modster
Senior Member
|
31. July 2007 @ 13:09 |
Link to this message
|
|
cool thanks guys!
|
AfterDawn Addict
|
31. July 2007 @ 14:16 |
Link to this message
|
|
3.52 M33 IS KICK A$$ LOL. I like it more than 3.51. I dunt know waht you're talking about man. i get no game errors and my psx eboots work, and the only thing that doesnt work is 3.03 oe-c themes, it freezes. will 3.40 oe-a themes work on it, or can i conver them?
|
|
mrmcman
Suspended permanently
|
31. July 2007 @ 14:23 |
Link to this message
|
|
3.03 oec converted and 3.40 oe themes both work, as long as u leave the system_plugin_fg.rco is left out.
(+[__]%) put this psp in ur siggy. just do it.
PSP Firmware: constantly changing, currently GoldenEye.
|
AfterDawn Addict
|
31. July 2007 @ 14:25 |
Link to this message
|
|
alrighy, what does that do though? is that the wave :S
|
|
mrmcman
Suspended permanently
|
31. July 2007 @ 14:35 |
Link to this message
|
|
battery icon. so its nothing big.
(+[__]%) put this psp in ur siggy. just do it.
PSP Firmware: constantly changing, currently GoldenEye.
|
AfterDawn Addict
|
31. July 2007 @ 14:37 |
Link to this message
|
|
alright thanks man, ur right tho, nothing big. have u got 3.52 M33 yet?
|
|
mrmcman
Suspended permanently
|
31. July 2007 @ 15:11 |
Link to this message
|
|
no 3.52 M33-2 get with the times lol :P
3.52 M33-3 in 3....2....1...
(+[__]%) put this psp in ur siggy. just do it.
PSP Firmware: constantly changing, currently GoldenEye.
|
AfterDawn Addict
|
31. July 2007 @ 15:21 |
Link to this message
|
|
haha lol ditto.
|
|
Advertisement
|
|
|
Member
|
31. July 2007 @ 18:37 |
Link to this message
|
I think I know what your problem is. You could solve it in one or two ways. You could go to the flash1 folder and delete a file called config.se(this clears the recovery mode settings). If you do that and that doesn't, your iso might have a long name. Just rename the game to something short and you should be able to run your iso's. I had the same problem and this seemed to fix everything.
|
