Problem with 3.40oe winstaller

I just tried to use the winstaller for the 3.40oe custom firmware. When I ran it, everything was fine. I restarted to a blue screen with tons of writing in different languages saying "Setting Information is corrupted. Press the O button to repair and restore default settings. Did I just brick my friends PSP. It was a 3.40 out of the box and I used the 3.50 upgrade and then the downgrade to get it to 1.5. Please Help.

Ok, now weird thing is that after I hit the O button, I restarted it, and checked the system information and the firmware was 3.40oe-a. Is that what is supposed to happen?

[brentbizzle]

Not sure about going from Sony firmware to 3.40 custom, but in the past when I've gone from Sony to custom on mine and friend's PSP's that blue error screen shows up. In fact, if you look at all the older tutorials they show that as one of the steps.

It's fine that usually happens when you downgrade, and please next time edit your previous post and don't double post.

yup thats fine...every time you install a new firmware that screen will usually come up. All it is, is just something stating that your original settings have been corrupted and that you'll have to reinput them. (time, date, etc.)

Ok here is whats happening, I had just instll it and it doesn't run anything and I dont know where to put the game_plugin.prx, and neither the psx games, anyway anything I had put rum neither umd's or iso's, I got a ta-082. Any help please, will be appreciated.

[ace]

When you say game_plugin.prx are you trying to flash flash0? If so then toggle usb for flash0 in the recovery menu (turn psp off, turn it on while holding r trig) and go to VSH> Resources> and then paste it there. Make sure you have enough space too. Stick the psx eboot's in the GAME or GAME150 folder. Change the homebrew folder kernal to 1.50 via the recovery menu and selecting configuration. And I don't know where your last question is asking so you'll have to refraise it. If your asking how to run iso's then you jsut stick them in the ISO folder in the root of your mem stick and select game on the psp and it'll pop up there.

Ok here is whats happening, I had just instll it and it doesn't run anything and I dont know where to put the game_plugin.prx, and neither the psx games, anyway anything I had put rum neither umd's or iso's, I got a ta-082. Any help please, will be appreciated.

Woah, woah, woah... slow down a minute. What are you trying to achieve by installing the game_plugin.prx? If you just updated to 3.40 oe-a then you shouldnt need to modify your game_plugin.prx unless you have a customized opening_plugin.rco.

for psx games youll need to create a new folder, place the eboot and keys inside the folder you just created, then place that folder inside your game folder

for iso/cso just place them in your iso folder

Thanx Ace and Staxx, but I think I wasn't clear enough. let me refraise. U help me in the game part but the game_plugin.prx is a file that I download from the page, as it it was an update. But my real problem is that I have a PSP that I can't made it work with any of the special editions, neither M33 one. I had install M33 3.51, didn't work then upgrade to 3.52 M33, didn't work either, then made the 1.50 recovery and put the 3.40 0e and it didn't work either. When I say didn't work is that it doesn't run any games whether they are iso or cso or psx games neither umd ones. I install the 3.52 M33 in my PSP and it works like a charm. I don't know what to do with that other PSP to make it work. It's a ta-082( I think it's has that board cause of the numbers in the umd tray). Any help will be appreciated.

My guess would be that you had no-umd enabled on those other firmwares. You need to have it disabled and then throw a game or game demo into your umd tray for the games to work.

The only reason i see that its working on 3.52 M33 is because they fixed the no-umd compatability issue so it works a lot better with it enabled. Your probably still experiencing a problem playing umd games though correct? to fix this go into recovery and change no-umd to disabled then try running your umd game.