PS2 How to properly combine HDD-OSD and FreeHdBoot 1.966

El_isra

El_isra

Developer
I've tried a lot of different combinations to achieve this.
But nothing works.
FreeHdBoot Boots showing the logo (allowing me to use launch Keys) but then it boots into the HDD-OSD with the non-hacked OSDSYS.

I'm using:
HDD-OSD from a image made by vash32 (recovered from a youtube tutorial)
FreeMcBoot 1.966 installer from https://sites.google.com/view/ysai187/home/projects/fmcbfhdb

uLaunchELF 4.43a 41e4ebe to format HDD


What I'm doing wrong??
 
El_isra said:
HDD-OSD from a image made by vash32 (recovered from a youtube tutorial)
Click to expand...
FHDB isn't compatible with that, because of the way the hosdsys KELF was packed.

You can format the HDD with wLE, use SUDC4 to install the HDD-OSD from the 1.10U installer, then install FHDB.
Code: 
https://pastebin.com/raw/dzi44h6d


Or if you really want to use that HDD image (which I do not recommend), replace the hosdsys.elf file in __system/osd100/ by the one from SUDC4.
Code: 
https://pastebin.com/raw/ZAGdAtPf

Or format the HDD with wLE, install FHDB, throw the above HDD-OSD files in __system/osd100/. But the filesystem checker program is missing from the archive.
 
krHACKen said:
FHDB isn't compatible with that, because of the way the hosdsys KELF was packed.

You can format the HDD with wLE, use SUDC4 to install the HDD-OSD from the 1.10U installer, then install FHDB.
Code: 
https://pastebin.com/raw/dzi44h6d


Or if you really want to use that HDD image (which I do not recommend), replace the hosdsys.elf file in __system/osd100/ by the one from SUDC4.
Code: 
https://pastebin.com/raw/ZAGdAtPf

Or format the HDD with wLE, install FHDB, throw the above HDD-OSD files in __system/osd100/. But the filesystem checker program is missing from the archive.
Click to expand...
Thanks!
how can I launch SUDC4 (or recover HDD-OSD from it) ??
my console laser and the disk tray mechanism arent working

i almost forgot to ask.... SUDC4 contains a 48bit HDD-OSD?? or a 28 bit one?

####edit
forget about launching SUDC4
I already extracted all HDDOSD1.* files with https://www.psx-place.com/resources/paker-utility.886/
I supose that i must copy the files into the corresponding partitions, but... what i must do with *.XLF files?
 
Last edited:
  • Like
Reactions: TnA
Berion said:
Everything about it You can find in below mega tutorial. Including installing HDD OSD without working optical drive :P and of course installing latest FHDB+HDD OSD v1.10 recognition:
https://www.psx-place.com/threads/apa-patitionology.30912/

BTW: SUDC4 have patched HDD OSD so it supporting LBA48 and none-Sony HDD.
Click to expand...
great!

ill leave this batch file here...
it will rename every file in the given directory from upercase to lowercase to install in into the HDD and OSDSYS_J.XLF to hosdsys.elf
 

Attachments

If You rename files to lowercase, it will hang on boot. ;) All (except "hosdsys.elf") must be upper case. Which is strange because HDD Utility Disc normally installing files with lower case filename. I also don't like mess like that so I change everything to lc and took me a while why FHDB start to freezing.
 
Berion said:
If You rename files to lowercase, it will hang on boot. ;) All (except "hosdsys.elf") must be upper case. Which is strange because HDD Utility Disc normally installing files with lower case.
Click to expand...
Yeah I discovered that on my own... Quite weird since all HDD-OSD files that I've fount use lowercase files, copying the as uppercase caused them to hang on Boot, and if they managed to launch every text had the name of it's variable instead of text.
But anyways I'll leave it here if someone wants 2 give it a try
 
  • Like
Reactions: TnA
Berion said:
If You rename files to lowercase, it will hang on boot. ;) All (except "hosdsys.elf") must be upper case. Which is strange because HDD Utility Disc normally installing files with lower case filename. I also don't like mess like that so I change everything to lc and took me a while why FHDB start to freezing.
Click to expand...
Thanks for reminding me about that PDF, I forgot it had a explanation on how to extract hddosd from sudc4
 
Sure thing, a very nice batch anyway, maybe someone with better knowledge explain from where this case sensitive comes from. Maybe it will be useful in future. ^^

BTW: Can I name it as something more informative, like i.e "PAK Upper to Lower Case" or something like that? I have in mind PS2 AIO update (which one day I'll finally release it ;p).


I have in plans also paid for professional translation into English in future for few tutorials but for now is in Polish. Still there is PSBBN installation and translation which I want to write about it.
 
Berion said:
Sure thing, a very nice batch anyway, maybe someone with better knowledge explain from where this case sensitive comes from. Maybe it will be useful in future. ^^

BTW: Can I name it as something more informative, like i.e "PAK Upper to Lower Case" or something like that? I have in mind PS2 AIO update (which one day I'll finally release it ;p).


I have in plans also paid for professional translation into English in future for few tutorials but for now is in Polish. Still there is PSBBN installation and translation which I want to write about it.
Click to expand...
Do as you want!
 
Sorry for the thread necromancy, but I was using this thread to help me with my own issues, and I ran into some trouble.

I'm new to this, and I'm trying to set up FreeHDBoot. I've got OPL working all right with my PS2 games (haven't tried PS1 yet), but now I'm trying to get HDD-OSD working. At first I used a disk image that I got from a YouTube tutorial: I think it was the same one OP used. But I saw this thread while trying to get it to work, and thought I should do it the right way.

So I wiped the drive and built up my HDD from scratch, according to the "APA Partitionology" PDF mentioned above. But I can't seem to get HDD-OSD running at all: FreeHDBoot does run, but it only goes to the original OSD. I think I may be using SUDC4 incorrectly, but if that's the case, then I'm not sure what to do with it.

Here are the exact steps I'm taking:

1) Format the HDD.
2) Install FreeHDBoot 1.966 using the installer.
3) Install OPL, GSM, MCA, and SMS.
4) Use CDMage to extract the PAK file from the SUDC4 image.
5) Use PakerUtility to extract the necessary files from the PAK. These get copied onto a USB drive.
6) Put the USB drive into the PS2.
7) Copy mass:/extracted/SYSCONF/* to hdd0:/__sysconf
8) Copy mass:/extracted/SYSTEM/* to hdd0:__system
9) Rename hdd0:/__system_/OSD/OSDSYS_A.XLF to hosdsys.elf.
10) Restart the PS2.

I expect HDD-OSD to start, but instead the normal OSD starts. Version numbers are what I'd expect for an un-updated PS2.

Since OP seems to have gotten things working, I think I must be misunderstanding something from the PDF, but I'm not sure which part. Does anything from my procedure stick out as incorrect?
 
  • Like
Reactions: TnA
In my case it is "hdd0:/__system/osd/hosdsys.elf" (because FHDB was drop there so I was thinking it is universal osd update path for all models). Is not?

You also named folder "OSD" instead of "osd". Maybe that's the problem. Or maybe different osd update paths for different models?
 
Berion said:
In my case it is "hdd0:/__system/osd/hosdsys.elf" (because FHDB was drop there so I was thinking it is universal osd update path for all models). Is not?

You also named folder "OSD" instead of "osd". Maybe that's the problem. Or maybe different osd update paths for different models?
Click to expand...
I'm starting to wonder. I'm on an SCPH-39001, and krHACKen's fix (osd100 and fsck100) seems to work for me.
 
It's the same path for all models.

The homebrew MBR program that comes with FHDB supports the same integrity checks as the Sony MBR program, and boots one of the following KELF targets:
  1. pfs0:/osd/osdmain.elf (Unofficial target, for FHDB)
  2. pfs0:/osd/hosdsys.elf
  3. pfs0:/osd100/hosdsys.elf
If the HDD has been deemed to have filesystem corruption, FSCK in one of these locations will be launched, in this order:
  1. pfs0:/fsck/fsck.elf (Unofficial target, for FHDB)
  2. pfs0:/fsck/fsck.elf
  3. pfs0:/fsck100/fsck.elf
 
Black screen can come from:
  • not compatible modchip with FHDB
  • not compatible HDD OSD hacks with FHDB
  • lowercase named resources of HDD OSD (hacked version from SUDC4 expecting uppercase)
 
krHACKen said:
FHDB isn't compatible with that, because of the way the hosdsys KELF was packed.

You can format the HDD with wLE, use SUDC4 to install the HDD-OSD from the 1.10U installer, then install FHDB.
Code: 
https://pastebin.com/raw/dzi44h6d


Or if you really want to use that HDD image (which I do not recommend), replace the hosdsys.elf file in __system/osd100/ by the one from SUDC4.
Code: 
https://pastebin.com/raw/ZAGdAtPf

Or format the HDD with wLE, install FHDB, throw the above HDD-OSD files in __system/osd100/. But the filesystem checker program is missing from the archive.
Click to expand...

i followed the procedure here and from @Berion tutorial pdf but when i boot to hdd fhdb logo appears then bsod
if i renamed hosdsys.elf to osd100.elf fhdb boots instead of hddosd
my console is fat scph-39001 with hdd WD black 80GB

Berion said:
Black screen can come from:
  • not compatible modchip with FHDB
  • not compatible HDD OSD hacks with FHDB
  • lowercase named resources of HDD OSD (hacked version from SUDC4 expecting uppercase)
Click to expand...
1- no modchip installed
2- maybe .
3- all uppercase except for hosdsys.elf and fsck.elf (folder names are osd100 and fsck100)
 
Last edited by a moderator:
  • Like
Reactions: TnA
Everytime I install a new MBR payload to sector 8192 it stops working throwing up a Magicgate decryption error in pcsx2, be it

HDDOSD
FHDB
PS2BBL
OSDMenu

the kelf is regionfree but the only one that works is that premade polyviewer image one with J in the header instead of W, how can I make the MBR elf decrypted & regionfree & reinsert it to sector 8192?

I tried your installer an it says the kelf is 570 sectors so the kelf payload is supposed to be 570x512=291840bytes without the header? this needs to be updated with every hosdmenu payload release alongside the installer because of the new sizes?
I think the only kelfs pcsx2 can load are the dnasload ones because of the hdd?

https://github.com/pcm720/OSDMenu/releases/download/v1.0.0-rc1/hosdmenu-mbr-installer-v1.0.0-rc1.zip
 
Last edited:
You must log in or register to reply here.

Similar threads

Back
Top