Posts: 516
Threads: 19
Joined: Apr 2009
Reputation:
6
Location: Romania
All i can tell you is this: When i dumped my USA console's bios with the modchip on instead of getting my USA v2.30 bios that i use to this day it gave me a HK v2.00 bios.
Disable any modchips if you can while dumping bios is what advice i can give.
Posts: 21.718
Threads: 401
Joined: Sep 2013
Reputation:
476
Location: 私の夢の中
I guess if the console is chipped it's possible the BIOS dumper isn't dumping the true BIOS but part of what the chip is emulating to do it's thing? I wonder.
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
Posts: 21.718
Threads: 401
Joined: Sep 2013
Reputation:
476
Location: 私の夢の中
That's what I figured. Maybe the OP console is chipped and he doesn't even know?
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
Posts: 19
Threads: 5
Joined: Aug 2015
Reputation:
0
How do I safely disable the chip and then safely re-enable it?
Posts: 21.718
Threads: 401
Joined: Sep 2013
Reputation:
476
Location: 私の夢の中
Depends on what chip you have.
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
Posts: 113
Threads: 10
Joined: May 2012
Reputation:
4
10-18-2016, 12:41 AM
(This post was last modified: 10-18-2016, 12:42 AM by ShadedTear.)
I honestly don't think he does. I myself don't and as shown in the linked thread my file names all came out with the same _VX_ and are also read by PCSX2 as being Japan BIOS despite being taken from an unmodded console.
I think the issue might stem from whatever _VX_ means.
The BIOS I dumped from my original black slim (RIP) Did not have _VX_ in it's filenames and was recognized as US. But since I don't have my old black one anymore and just have my 77001 I can't confirm the filenames anymore.
Posts: 8.030
Threads: 278
Joined: Feb 2009
Reputation:
345
I personally don't have any problems with FMCB or the dumper and my PS2 have modchip(soldered myself)and pcsx2 also recognize it correctly
The dumper that dump the bios as p2b also worked fine.
Posts: 113
Threads: 10
Joined: May 2012
Reputation:
4
Okay, so if we've figured that out. We have 3 known cases where the Dumper has created _VX_ Files that read as JP BIOS's in PCSX2 despite being from varying locations and model numbers.
What I think is happening is since the Dumper can't figure out the version completely it's going into some type of compatibility mode and just marking the files as NTSC-J Regardless of the source so they can be read instead of just failing outright as that would be a major issue for versions higher than a certain point.
I don't think the BIOS are weird or corrupt as maybe they just have new code that the dumper doesn't recognize.
I also wonder if it's specific to which "Dumper" we used. I know there's one version I couldn't use because I didn't have it connected to a LAN and it didn't wanna just dump to my flash drive. IIRC The 1.0 is the one that dumps direct to it's launch location (In my case, flash drive) and 2.0 needed the LAN connection. But it's been a long time and I may be mistaken.