f0bes / biosdrain Goto Github PK

View Code? Open in Web Editor NEW

108.0 8.0 18.0 243 KB

PS2 BIOS dumper

License: MIT License

Makefile 2.30% C 97.70%

biosdrain's Introduction

biosdrain

Instructions

Download the latest version of biosdrain under the GitHub releases page.

- For PS2LINK / PS2CLIENT users

Execute biosdrain on the EE. For example: ps2client execee host:biosdrain.elf

biosdrain should automatically detect a host filesystem, and dump the files directly to your computer.

- For USB users (using uLaunchELF)

Put the biosdrain.elf file onto a FAT32 (or exFAT!) formatted USB drive.

In uLaunchELF, navigate to mass: and execute the biosdrain.elf file you just transferred.

biosdrain should automatically detect a USB drive, and dump the files to the root of the USB drive.

In the case that biosdrain does not detect a USB drive, try creating a smaller 1GB partition and leaving the rest unformatted.

Using the BIOS with PCSX2

Simply copy the files (if you've used a USB drive) back to your computer, and keep them somewhere safe so you don't have to do this process again.

I politely ask that you do not share your BIOS files!

If the path to your bios was D:\ps2bios\dump you'd see one of the below.

Uninteresting info

Currently detects and dumps

ROM0
ROM1 *size fixed at 4096kb
ROM2
NVM
MEC

Notes

This software has been based off of the work from PS2Ident licensed under AFL license-3.0 . The Sysman and Romdrv module source have been taken from there as well.

Check out https://fobes.dev for some interesting PS2 programming blogs. You can support me on KoFi here.

biosdrain's People

Contributors

Stargazers

Watchers

Forkers

mrlinkwii redpanda4552 sariohara mrtada142 23xbackk kyles1984 semisemet umemeio reet457 missgmoya brunohelmer francastanho lexynotfound adrian9991 knight-ryu12 israpps twhite96 jmorlock02

biosdrain's Issues

SCPH-90001: "This file isn't an ELF."

Hello there, trying to launch biosdrain.elf (latest version) using the latest version of OpenTuna, a fork of the PS2 Fortuna Project. I am unable to run the program, as I get a strange error. Attached is the error. You can see what version of LaunchELF I am using. Obviously I am running this program directly off USB.

SCPH-77004: Unable to dump bios to USB or host

Doesn't detect USB and running through PS2Link tries to dump to host but doesn't transfer anything.

PS2Client output:
loadelf: fname host:biosdrain.elf secname all
Input ELF format filename = host:biosdrain.elf
1 00100000 001fe688 ................................
Loaded, host:biosdrain.elf
start address 0x100b70
gp address 00000000
framebuffer at 00000000
zbuffer at 00046000
open name rom0:ROMVER flag 1 data 41378
open fd = 2
biosdrain - revision v2.1.3
mkdir name host:/tmp
mkdir wrong mode, using fallback value 493
rmdir name host:/tmp
loadmodule: fname rom0:ADDDRV args 0 arg
loadmodule: id 31, ret 1
loadmodule: fname rom0:ADDROM2 args 0 arg
loadmodule: id -203, ret 1
SYSMAN: Initializing ROM support.
SYSMAN: EROM filesystem driver not found.
SYSMAN: Initializing i.Link support.
SYSMAN: Initializing DEV9 support.
SYSMAN: Initializing USB support.
SYSMAN: Initializing SPU2 support.
SYSMAN: IOP peripherals initialized successfully.
SYSMAN ID is 32 (res 0)
Dumping to HOST

Successful dump on a crusty SCPH-50001

This PS2 was on its last legs, broken fan header, the fan being hooked up via USB around the chassis to one of the USB ports, leaving the case half way open, a damaged on button cable, so the color is yellow when it's off, and the disc drive died.

I heard there was a new BIOS dumper, so I went and plugged it in. It went pretty well, and I got 6 files, put them in PCSX2 and got everything just how it was on my PS2. Even the model number and PS1 Driver version were right there in PCSX2.
It also kept my "Full" screen setting, which for some reason I had on my PS2 for years, not that it really changes anything outside of the BIOS.

Great, efficient dumper!
I plan on getting a new PS2 one of these days, and I'll be dumping those BIOS too. Have a nice day!

PS2 Not locating the file.

My problem is exactly what the title says. I'm using FreeUSBBoot to launch the exploit, but when I go to the mass section of it, nothing at all shows up. I've tested with two different drives (A USB 3.0 and USB 2.0 both formatted to fat32,) and always get the same result. Is there a certain slot it's supposed to be plugged into? And if not, are there any other reasons this could be happening? Thank you!

biosdrain 2.0.0 doesn't even load up on SCPH-70004 and SCPH-75004

Just tried biosdrain v2.0.0 with multiple USB on Sony PS2 SCPH-70004 and SCPH-75004 (both PAL) using uLaunchELF 4.43a.

Got a black screen without nothing else when launching it

Got to use v1.0.0 to dump bios correctly

SCPH-7003: Can't find USB or Host

Hi, when use FreeDVDBoot and launch biosdrain from a USB drive (mass) from uLE the biosdrain utility loads up but then fails with the message:

USB not found, and HOST is not available, not continuing

I've tried the v2 release marked as "latest" and v1 and I get the same results.

PS2 Slim Info:
Console: SCPH-7003
Browser: 1.4.0
CD Player: 2.00
PlayStation Driver: 1.11
DVD Player: 3.10E
The console seems in decent shape and plays games ok

SCPH 39001: Failed to open 0 file

Trying to dump a PS2 SCPH 39001 model, with biosdrain version 2.2.0 and I get the error message failed to open 0 file, with nothing saved to the USB drive afterwards. Any help would be greatly appreciated.

SCPH-50001 taking forever to dump

I have legit waited for an hour for it to dump. Takes a few seconds to load the text at first but then it gets stuck pretty much indefinitely. I put the elf at the root of the usb drive and loaded it with uloader. I have tried both a 8gb fat32 and a 4gb fat16 drive and both lead to the same outcome. One of my USBs lights up when a read/write operation occurs and it has been off for quite a while. As far as I know, my system is in complete working condition with no issues whatsoever.

README ROM1 dump size update

Hello, I have used the latest version (v2.1.0) to dump the BIOS. Based on current README, under section Uninteresting info, I was expecting a file size of 512 kB for ROM1 so I was surprised when I got 4096 kB file, thinking that the process had somehow failed in my model (SCPH-77004).

Then I noticed in commit 49406d0 that the dump file size has indeed changed hence the process was successful. Please update the relevant information as it is misleading.