FMCB v1.7 Multi-Version Won't Boot

taimaishu · #1 10-10-2008, 11:43 AM

I borrowed a friends SCPH-30001 and used the CodeBreaker guide to install v1.7 on an official 8MB Sony MC. I used the multi-version install and everything goes off without a hitch, and Free MC Boot starts up just fine on that console. However, when I pull the memory card and put it in my SCPH-90001, it refuses to boot. I get no FMCB splash screen, and it goes straight to the normal PS2 menu as if it doesn't even know the FMCB card exists. I've tried this with 2 separate memory cards and the results are the same on both, SCPH-30001 boots FMCB, SCPH-90001 won't. I'm not sure if there's anything I should be looking for.

Note: The SCPH-90001 is the one that's been going out in the LEGO Batman bundle, maybe a new minor revision or something?

Thanks for any help.

iwasaperson · #2 10-10-2008, 04:13 PM

it looks like the new slim ps2s doesnt work with fmcb, and it just boots osdsys from the bios...
it works on the older slims though (7xxxxx)

TnA · #3 10-10-2008, 04:35 PM

@iwasaperson: Can you please post your PS2-Bios-Version (press TRIANGLE in main-menu)?

You can try a "normal install" and rename the osdmain.elf to the corresponding version + 0.1.

So if your shown version is 2.1, just rename your file to "osd220.elf".

taimaishu · #4 10-10-2008, 06:18 PM

The triangle menu lists:

Browser: 1.40
CD Player: 2.00
Playstation Driver: 2.00
DVD Player: 3.11U

Which should I be going off of?

TnA · #5 10-10-2008, 06:26 PM

Hm,...

osd150.elf is already listed, so that shouldn't be your problem.

Did you tried to install an older version of FMCB (e.g. 1.5, or 1.6)?

taimaishu · #6 10-10-2008, 07:06 PM

Just tried out and v1.5 and v1.6 and the same thing happens.

jimmikaelkael · #7 10-10-2008, 07:31 PM

Have you tried with mc inserted in slot 2 ?

taimaishu · #8 10-10-2008, 07:41 PM

Yep, doesn't seem to make a difference though.

jimmikaelkael · #9 10-10-2008, 07:50 PM

I guess like you have no way to boot homebrews, it will be difficult to have a bios dump ?

TnA · #10 10-10-2008, 07:54 PM

Your problems seems curious.

Btw.: You can try to run it as DVD-Update instead.
If it work as DVD-Update, your PS2-Version might search in another folder for the osd-update.

jimmikaelkael · #11 10-10-2008, 07:58 PM

Nice idea TnA, but does he now how and which file to rename, especially if he can't boo t homebrews...
FMCB had already working on 9000x.

TnA · #12 10-10-2008, 08:01 PM

Just an idea.
He can prepare the dvd-update on the other working PS2-Console.

With this, he still can start the bios-dumper on his slim-ps2 (only need a DVD-Video-Disc as "trigger").

@taimaishu: If you don't know how to prepare your FMCB-Files, to be recognized as DVD-Player-Upgrade, just post and I'll search the tutorial quickly.

Quote:

FMCB had already working on 9000x.

Yepp, but it is curious that it seems to not been recognized by the PS2 (no Logo at all on start-up).

Edit: Link to DVD-VTS-Xpl./How-To create an DVD-Update.

http://www.aoinamida.com/fmcbesr/esrdvdplayer.html

taimaishu · #13 10-10-2008, 08:39 PM

Alright, so via some trickery (a codebreaker save I found that will load SMS on the slim without needing the pelican.bin on the USB), I've managed to boot SMS, swap memory cards to boot uLaunchElf, and then run a PS2 BIOS dumper. The files I got were:

SCPH-90001_BIOS_VX_USA_230.BIN
SCPH-90001_BIOS_VX_USA_230.EROM
SCPH-90001_BIOS_VX_USA_230.NVM
SCPH-90001_BIOS_VX_USA_230.ROM1
SCPH-90001_BIOS_VX_USA_230.ROM2

I can send these files to either one of you if you'd like. Does the DVD-Player-Upgrade work as a fully alternate method of booting FMCB? If so, I guess that would work for the meantime. Let me know if you have any more thoughts / ideas or if you want me to grab any other information for you, thanks.

jimmikaelkael · #14 10-10-2008, 08:45 PM

Nice, you can send these at my PM box

taimaishu · #15 10-10-2008, 09:05 PM

Sent you the PM, in the meantime I've figured out how to auto-load uLE when I boot my CodeBreaker disc so I suppose that I can get by with that until we figure out this FMCB stuff.

jimmikaelkael · #16 10-10-2008, 09:07 PM

Yeah good, so try to re-install FMCB with normal install and see.
Your osdsys uses osdmain and osd240.elf

taimaishu · #17 10-10-2008, 09:12 PM

That was actually the first thing I tried after I was able to boot uLE but sadly it doesn't work. :\
Edit: Just saw your edit, I'll take a look at it, thanks.

jimmikaelkael · #18 10-10-2008, 09:21 PM

Quote:

Originally Posted by taimaishu

That was actually the first thing I tried after I was able to boot uLE but sadly it doesn't work. :\
Edit: Just saw your edit, I'll take a look at it, thanks.

I think i found your problem.
Your romver letter is J which induce installer in error I guess it creates a BIEXEC-SYSTEM folder ?

Try to rename the folder to BAEXEC-SYSTEM, or create it and copy osdmain.elf in it and it should work.

I would have bios dump from another bios v230 (one from another region) to see how can I fix the problem for 1.8 release, a non batman bundle will be ideal.

taimaishu · #19 10-10-2008, 09:32 PM

The installer doesn't error and the folder created is in fact BAEXEC-SYSTEM.

jimmikaelkael · #20 10-10-2008, 09:35 PM

Quote:

Originally Posted by taimaishu

The installer doesn't error and the folder created is in fact BAEXEC-SYSTEM.

Ok but I'm sure there's a problem with the letter...
What if you try to rename it to BIEXEC ?

EDIT:
I see something strange in your OSDSYS...
The osdsys was using LoadExecPs2("moduleload -x mc?:/BREXEC-SYSTEM/osdxxx.elf") to load osd update.
The function still here but not called from anywhere in the code.

I fear that sony have maybe disabled it.

taimaishu · #21 10-10-2008, 09:50 PM

LaunchELF wouldn't let me rename it so I copy/renamed it BIEXEC-SYSTEM, still nothing. Could it be getting signed incorrectly?