iso owners of a desr psx1 with a dead hard drive

My stuff is very old, but to list the files from the BIEXEC-SYSTEM directory, I do :
Code: 
fsclient -h %PSXIP% dir xfrom:BIEXEC-SYSTEM

To just get xosdmain.elf, I do :
Code: 
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/xosdmain.elf xosdmain_bak.elf

To get all the v1.xx launcher files, I do :
Code: 
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/INSTALL.ID INSTALL_bak.ID
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/osdmain.dat osdmain_bak.dat
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/osdmain.mod osdmain_bak.mod
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/xosdmain.elf xosdmain_bak.elf

To get all the possible v1.xx repartition token files, I do :
Code: 
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/contents.opt contents_bak.opt
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/delete_game_area.opt delete_game_area_bak.opt
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/make_game_area.opt make_game_area_bak.opt
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/repartition.opt repartition_bak.opt


So I believe that what you did to get :
[Contents of xfrom:/]

drwxrwxrwx 4 01-02-2000 31:56:26
drw-rw-rw- 0 10-11-2004 11:54:00
drwxrwxrwx 6 10-11-2004 11:54:41
drwxrwxrwx 2 01-02-2000 31:56:26

[4 Files - 12 Bytes]
is correct, and doing it for the BIEXEC-SYSTEM directory should work.
 
krHACKen said:
My stuff is very old, but to list the files from the BIEXEC-SYSTEM directory, I do :
Code: 
fsclient -h %PSXIP% dir xfrom:BIEXEC-SYSTEM

To just get xosdmain.elf, I do :
Code: 
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/xosdmain.elf xosdmain_bak.elf

To get all the v1.xx launcher files, I do :
Code: 
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/INSTALL.ID INSTALL_bak.ID
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/osdmain.dat osdmain_bak.dat
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/osdmain.mod osdmain_bak.mod
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/xosdmain.elf xosdmain_bak.elf

To get all the possible v1.xx repartition token files, I do :
Code: 
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/contents.opt contents_bak.opt
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/delete_game_area.opt delete_game_area_bak.opt
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/make_game_area.opt make_game_area_bak.opt
fsclient -h %PSXIP% copyfrom xfrom:BIEXEC-SYSTEM/repartition.opt repartition_bak.opt


So I believe that what you did to get :
[Contents of xfrom:/]

drwxrwxrwx 4 01-02-2000 31:56:26
drw-rw-rw- 0 10-11-2004 11:54:00
drwxrwxrwx 6 10-11-2004 11:54:41
drwxrwxrwx 2 01-02-2000 31:56:26

[4 Files - 12 Bytes]
is correct, and doing it for the BIEXEC-SYSTEM directory should work.
Click to expand...

Really, thank you very very very much
Indeed, that's the folder and the first for are the contents. Without your guide, I'd never get them, specially osdmain.dat and osdmain.mod. For some reason, dir wouldn't show the names of the directories. Comparing the dir results of my MC, the first two folder are . and .. , one folder is BIEXEC-SYSTEM, and the other one is folder A, a folder I created trying to test the build of wLaunchELF I made. So this problem clearly also translated to wLaunchELF XD
The A folder only shows two things, which should be . and ... The BIEXEC-SYSTEM had six files, . and .. and the files you mentioned.
The repartition tokens you said, didn't show up. Trying to copy contents.opt gave me error and, as I said, the where only 4 files beside . and ..
Code: 
 [Contents of xfrom:BIEXEC-SYSTEM]

  drwxrwxrwx  0 10-11-2004 11:54:01
  drwxrwxrwx  0 10-11-2004 11:54:00
  -rwxrwxrwx  423760 10-11-2004 11:54:02
  -rwxrwxrwx  2048 10-11-2004 11:54:04
  -rwxrwxrwx  6144000 10-11-2004 11:54:24
  -rwxrwxrwx  0 10-11-2004 11:54:41

 [6 Files - 6569808 Bytes]
The files sizes match the ones I downloaded.
So, checking offset 10dec didn't help, but searching for the root signatures got me something, I found a match at offset 000003A0, corresponding with v1.31.
Again, thank you very much

Btw, out of curiosity, what's osdmain.dat and osdmain.mod?
Viewing them, I saw each has the same 1024 bytes at the start and the end of the file. It's the copyright info and some bytes, and a lot of zeroes.
In the mod file, those bytes are just 4 bytes, and curiously, the same 4 bytes are in the dat file at the same position :o (Position 94hex, 148dec)
 
Last edited by a moderator:
.dat is the xosd ressource and upgrade history file.
.mod is the bootmode file, which is used for example to boot in install mode and upgrade the system software with the native system software updater, and to backup the current system software.

contents.opt is to copy default configuration files and folders to the DVR area partitions.
delete_game_area.opt is to delete the game area so the DVR area is mapped right after the system partitions.
make_game_area.opt is to create the game area, PS2-style.
repartition.opt triggers the repartition.
Some of the faulty PSX1 units I've serviced were stuck in a repart boot loop lol.

The PSX2 xosdmain does all the above things with bootflag.txt settings.
 
krHACKen said:
.dat is the xosd ressource and upgrade history file.
.mod is the bootmode file, which is used for example to boot in install mode and upgrade the system software with the native system software updater, and to backup the current system software.

contents.opt is to copy default configuration files and folders to the DVR area partitions.
delete_game_area.opt is to delete the game area so the DVR area is mapped right after the system partitions.
make_game_area.opt is to create the game area, PS2-style.
repartition.opt triggers the repartition.
Some of the faulty PSX1 units I've serviced were stuck in a repart boot loop lol.

The PSX2 xosdmain does all the above things with bootflag.txt settings.
Click to expand...

The updater restarts the system sometimes right?
Those other 4 files seem to be part of the update/restore process.
Would it be harmful to load FMCB between those restarts to try and dump the other 4 files? ;o
As far as I know, FMCB exploits the MC update system right?. The update disc doesn't use that, does it? (Well, it has xfrom XDD)

Just saying, I found my PS2 slim has a modbo 4, but I think I prefer waiting for mechapwn. I think I prefer risking the mechacon over the mobo XDD. Anyway, the exploit should be safer for someone whose fine skills are nonexistent :p
And, btw, how mechapwn is supposed to allow the load of backups, and how do you enable that? ;0 (speaking for a PS2 at least)
 
Jose64141 said:
The updater restarts the system sometimes right?
Click to expand...
The updater restarts the system after the job is done, if there's no Shutdown instruction in the script.
The update disc restarts the system after the files were copied to the HDD and the boot mode was changed for install mode.
Jose64141 said:
Those other 4 files seem to be part of the update/restore process.
Click to expand...
The opt files ? Actually they're written to the flash when you choose to repartition the system from the system settings options. Also, repartition causes the __common partition to be purged if my memory serves me right.
The reason I've made update scripts with .opt file copy is because some people may have drives with corrupted DVR area. Same with registry and gmm databases.
Jose64141 said:
Would it be harmful to load FMCB between those restarts to try and dump the other 4 files? ;o
Click to expand...
Harmless, can be done if the system doesn't reboot with the SkipMc argument (I cannot remember). Else with the bootloader and BOOT.ELF. But for what purpose ?
Jose64141 said:
As far as I know, FMCB exploits the MC update system right?. The update disc doesn't use that, does it? (Well, it has xfrom XDD)
Click to expand...
The update disc doesn't care about the MC as far as I know. Doesn't read from it, doesn't install anything to it.

Jose64141 said:
Just saying, I found my PS2 slim has a modbo 4, but I think I prefer waiting for mechapwn. I think I prefer risking the mechacon over the mobo XDD. Anyway, the exploit should be safer for someone whose fine skills are nonexistent :p
Click to expand...
MechaPwn was working on the PSX1 and PSX2, in beta stage. "Planned" to be implemented, no ETA https://github.com/MechaResearch/MechaPwn/issues/13
 
Berion said:
It's described in readme file. ;)
https://github.com/MechaResearch/MechaPwn
Click to expand...
It would be the Force Unlock mode? ;o
Cause it says that it allows booting from an original disc from other regions so I'm not sure about that, and it targets the Force unlock to homebrew so I wasn't sure about that either 0.0

krHACKen said:
Harmless, can be done if the system doesn't reboot with the SkipMc argument (I cannot remember). Else with the bootloader and BOOT.ELF. But for what purpose ?
Click to expand...
I assumed the opt files were part of the update process, but know you've made clear they aren't XD
Thank you for all the info c;
 
You have asked about how it works, so I paste link to readme. ;] In short: it converts console's ODD to debug one which have less restrictions than retail's. You can still go back to original data if You have a backup. On DESRs probably this will works in similar way. You don't need to use Force Unlock, it brakes by design reading other discs (DVD-Video (ESR Discs and FDVDB Discs are also DVD-Video) and PSX because it set drive to recognizing every disc as PS2 Disc).
 
I just found out bout disc patcher XDD
I think that's the bit I missed ;p
Berion said:
You have asked about how it works, so I paste link to readme. ;] In short: it converts console's ODD to debug one which have less restrictions than retail's. You can still go back to original data if You have a backup. On DESRs probably this will works in similar way. You don't need to use Force Unlock, it brakes by design reading other discs (DVD-Video (ESR Discs and FDVDB Discs are also DVD-Video) and PSX because it set drive to recognizing every disc as PS2 Disc).
Click to expand...
Thanks btw XD
 
Davewatts said:
im working on a write up on how i fixed my desr 5000 with a scph 20401 and restored dvr functions.

So im looking for people that have a 5000 or 7000 with a dead hard drive access to sony hard drive and the ability to install a modbo on it (atleast until mechpwn supports it) and a memory card setup for freemcboot.

im also capable of doing the process if you happen to be in central Florida.

let me know if you have any questions or have the setup.
Click to expand...

Just registered to see if you still need help with this. I'm in the Central Florida area and I have a working DESR-7000 along with a SCPH-20401 HDD. While I do have a Modbo 4.0 lying around, I'm not able to install it myself. I do have the official 1.31 update disc if that would suffice.
 
Wow, central Florida, you are really close by lol. I'm in Bartow. As long as you laser is in good condition to read the original disk you should be good to go. You will need a freemcboot memory card and I have the files needed to copy over. Send me a message and Ill get you some links and walk your through what I did.
 
Hello All!

Sorry to aks here but it seems like the best place to do so.

I recently picked up a DESR5000 which seems to have a dead HDD.

I was looking to buy a SCPH-20401 for when Mechpwn finally supports it.

I've found one which the seller seems to have formatted... Is this an issue? I'm guessing not as I think from what I read online, it's just needed due to the Firmware on the drive motherboard itself and not for any data actually on the drive?

Thanks in advance!

Sent from my SM-G998B using Tapatalk
 
Davewatts said:
It shouldnt be an issue. I formatted mine in the process of figuring this out and it still works.
Click to expand...
Great! Thank you [emoji4]

And is it still the case that we can't swap to this type of PS2 HDD from a failed original HDD without either a mod chip or Mechpwn? Sorry I'm new to the PSX and there's a lot of info out there without it being apparent what's accurate and relevant still.

Sent from my SM-G998B using Tapatalk

@Davewatts

Just another question if you don't mind me asking. Which "style" SCPH-20401 do you have? I ask as there seems to be 2 styles. Both have Sony on them, but 1 of them at least shows as Maxtor branded to HDD tools...

I'm guessing it won't matter as the Firmware on them should be the same.
 
Last edited by a moderator:
If You have original PSX Update Disc with fw equal (?) or newer, then You do not need any hack to partition it.
Problem here are two security layers, which aren't defeated yet:
  • HDDs whitelisting
  • HDD encryption
If we know exactly how it works, first could be bypassed by custom HDD firmware which rather never happen (because this demand different hack for different HDD) or by special controller put between console and HDD which will faking response from HDD side. Second can be defeated if we find exploit to read key and reverse used algorithm for encryption (so You would be able prepare it on PC). Currently none of both solutions exist - but both are possible.

Good news is, we can run any code via FMCB or modchip (in future in addition after MechaPwn hack). Bad news is this console is rare, prices are very high and not many fully functional units left in the second/third hand market.
 
Last edited:
There are only 2 methods as of right now really if it still turns on and reads something.:
  1. You "refresh"/recover all sectors with something like HDD Regenerator, or MHDD, or etc. You make an image of it, LLF the HDD and write the image to back to it.
  2. You wait for a NAND-Based hack, which allows for every storage device (which is compatible) to be used.
Edit: Regarding "1.". I saw it was formatted. Try to 'Scan & Repair' via WinHIIP or the special HDL Dump version.

If you have an original update-disc, you can install everything again. Not sure if backups work...
 
Last edited:
TnA said:
There are only 2 methods as of right now really if it still turns on and reads something.:
  1. You "refresh"/recover all sectors with something like HDD Regenerator, or MHDD, or etc. You make an image of it, LLF the HDD and write the image to back to it.
  2. You wait for a NAND-Based hack, which allows for every storage device (which is compatible) to be used.
Edit: Regarding "1.". I saw it was formatted. Try to 'Scan & Repair' via WinHIIP or the special HDL Dump version.

If you have an original update-disc, you can install everything again. Not sure if backups work...
Click to expand...
Thanks! So mine powers on, I've got it booting from FreeMcboot etc. The HDD clicks however and leaves me hanging at a white screen upon boot if I allow it to try and boot from the HDD.

So feels like a mechanical issue there...

I do have 2 x 40GB SCPH-20401 HDDs coming from Japan but atm I have no official boot discs... So I don't think I'll be able to recover an OS onto then?

Sent from my SM-G998B using Tapatalk
 
You must log in or register to reply here.

Similar threads

Back
Top