Codebreaker patched to load HDL

[dlanor]

Originally Posted by xbox1513

i dont think i have a __boot dir on my ps2 hdd. I have the official ps2 hdd from $sony, and browser 2.0 and hd loader, but i cant locate __boot on ulaunchelf.

You don't really need that partition, if you can accept launching HDLoader from another media than HDD. The patched CodeBreaker elf will look for the HDLoader elf in several different locations and using two different names, as follows:

hdd0:/__boot/CB_launch.elf
mass:/BOOT/CB_launch.elf
mc0:/BOOT/CB_launch.elf
hdd0:/__boot/boot.elf
mass:/BOOT/BOOT.ELF
mc0:/BOOT/BOOT.ELF
mc0:/B?DATA-SYSTEM/BOOT.ELF
mc1:/BOOT/BOOT.ELF
mc1:/B?DATA-SYSTEM/BOOT.ELF
"?" means region code.

So you can use a memory card or a USB mass storage device to hold HDLoader and leave the HDD partition setup unchanged.

Best regards: dlanor

[foureight84]

what if i rename the elf file in the patcher? say to HDLoader.elf? the weird thing is that when i run it, no matter what name and direct i put for the hdloader, it won't work. the dvd rom drive opens and the screen goes black.

[foureight84]

ah i got it working. anyway, i have another question. after i load the cheats and load metal gear solid 3 in hd loader, the screen stays blank. has anyone been having this problem with any other games? i'm using hdl .8c with the gtavs and gowII patch

[dask8da]

Hi, I'm using CBv10 patched for HDL and everything works fine. I want to upgrade CBv10 with day1 files. I have the .cbc-files on the root of my usb-stick, but I can't see any files. I also tried the upgrade.bin. Why I can't see aything on my usb-stick?

[Maverick]

Can someone please help me with codebreaker 9.3? I have it directed to hdloader and it works when I first run it. I can download cheats from day1 but when I save them and it makes a cheat file on the memory card hdloader won't load once I choose start game. It's just a black screen. Am I doing something wrong? Is there another version I can use or is there a way to fix this?

EDIT: Nvm, deleting extra game codes worked.

[ytifle]

I am using CodeBreaker 10 elf (MD5 6E4D4C2723D0F83120CD06D2D0A6C8ED {3,51 MB (3.688.628 bytes)} ), patched with ffgriever tool for CB10 ( cbv10hdlmod patcher.rar ), without options, with MCBOOT (1.5 normal)

At first when i tried to launch it without patching, it booted in black screen.

After patching, it works... (funny though)

The MD5 for the patched is: 683EF391D10249A398551021E6EA62AC [3,62 MB (3.798.592 bytes)]

HDL 0.8 full

Thanks for this useful software ^^

[TehSkull]

I'm having some issues with patching 9.2. I start with a checksum of F279F8412CAFE80F326BB945D7DC480F, but after unpacking I get 6A971720F6C47B65E3B07D24CA41F8B7. Am I doing anything wrong? I haven't tried using that file just yet so I'll do that right now.

[guxtabo]

Can you help me to know where can I get it. From where? I could get 9.2 and 93 work with esr, I dont know how to look for it.

Thanks.

Originally Posted by ytifle

I am using CodeBreaker 10 elf (MD5 6E4D4C2723D0F83120CD06D2D0A6C8ED {3,51 MB (3.688.628 bytes)} ), patched with ffgriever tool for CB10 ( cbv10hdlmod patcher.rar ), without options, with MCBOOT (1.5 normal)

At first when i tried to launch it without patching, it booted in black screen.

After patching, it works... (funny though)

The MD5 for the patched is: 683EF391D10249A398551021E6EA62AC [3,62 MB (3.798.592 bytes)]

HDL 0.8 full

Thanks for this useful software ^^

[Bootlegninja]

Please search google for it as linking is against the rules here since it is copyrighted material.

[eug1080]

is it possible for this to access toxicOS?

[TheOnts]

Hey everyone noob here. I was trying to find ffgrievers CB patcher in these forums but am unable to locate it. Can somebody please help me? Thanks a million

[Bootlegninja]

try the first post of this thread.

[TheOnts]

Thanks Bootlegninja, perhaps next time I should open my eyes a bit more hahaha. Again thanks a bunch!

[dask]

have patch for CODE BREAKER 8.0/8.1?

[Bootlegninja]

Nope. As far a I know, ffgriever never created such a patch for anything older than 9.2

[TLTD]

I have a codebreaker 9.3 version that looks for a boot.elf (hdloader) but it must be in a \boot\ directory on the mem card. It was supposed to be able to search the HDD partitions and never worked, sometimes I had a weird red screen of death. So I got a version of hdloader and renamed it boot.elf, put it in a \boot\ directory and copied onto mc w/uLaunchElf.

Some of the black screens are too many codes. I thought that it was game specific too, but that wouldn't make sense as it uses the same method and it's booting the same thing (hdloader) after. Some games, like Tony Hawk PG I could do one code and be fine. I realized it had a cheat menu though so that was even better.

It is nice to have a cheat prog loading games off the hard drive without being rebuilt, let me tell you.

[dlanor]

Originally Posted by TLTD

I have a codebreaker 9.3 version that looks for a boot.elf (hdloader) but it must be in a \boot\ directory on the mem card.

No, that is incorrect. It will look for "BOOT.ELF" in the folder "/BOOT/". Remember that on the PS2 character case is always significant for file names, so if even one letter uses the wrong case the elf file will not load. As for the patched CB 9.3, I use it myself, so I know that it also looks for the elf in several other places using two different file names.

It was supposed to be able to search the HDD partitions and never worked,

It works just fine here, but it was never intended to 'search' several partitions like you imply. It only looks for the elf, using either of two names, in the partition named "__boot".

sometimes I had a weird red screen of death.

IMO that is another issue entirely, not in any way connected to the patch.

So I got a version of hdloader and renamed it boot.elf, put it in a \boot\ directory and copied onto mc w/uLaunchElf.

Again, that can't possibly work, due to incorrect casing. It is also a bad choice for other reasons, as many homebrew programs expect to be able to restart your main browser (usually uLE) as "mc0:/BOOT/BOOT.ELF", which is why ffgriever also made his patch able to use another filename, with higher priority.

The filenames which the patched CodeBreaker looks for are "CB_launch.elf" and "BOOT.ELF", and it will look for both of these files in three different locations, and will check for "BOOT.ELF" in a fourth location as well, as follows:

"hdd0:/__boot/CB_launch.elf"
"mass:/BOOT/CB_launch.elf"
"mc0:/BOOT/CB_launch.elf"
"hdd0:/__boot/boot.elf"
"mass:/BOOT/BOOT.ELF"
"mc0:/BOOT/BOOT.ELF"
"mc0:/BxDATA-SYSTEM/BOOT.ELF"

Note that the "BxDATA" substring will be adapted for your console region, so for my european PAL console it is "BEDATA", though it will be "BADATA" for a US console.

Storing HDLoader in any of those four paths, renamed as indicated above, will cause the patched CodeBreaker to launch it when 'told' to launch game. I recommend using the name "CB_launch.elf", to avoid conflicts with how other homebrews use "BOOT.ELF". The launch path I use myself is "hdd0:/__boot/CB_launch.elf", and I usually launch the CodeBreaker elf from the HDD as well (stored as "hdd0:/+ELFS/CodeBreaker/CB93 hdlmod11.ELF").

Btw: I guess I should update to v1.2 of the patch, but I just haven't gotten around to it, as v1.1 works perfectly for me.

It is nice to have a cheat prog loading games off the hard drive without being rebuilt, let me tell you.

It certainly is, and I'm glad we can at least agree on that.

Best regards: dlanor

[AcidJeff]

dlanor, allow me to make a little correction for the paths searched: for the hdd0: the correct path is "hdd0:/__boot/boot.elf" with boot.elf all in lowercase. I use this path this way myself in my configuration and it's also described in the readme of the patch from ffgriever.

[dlanor]

Originally Posted by AcidJeff

dlanor, allow me to make a little correction for the paths searched: for the hdd0: the correct path is "hdd0:/__boot/boot.elf" with boot.elf all in lowercase. I use this path this way myself in my configuration and it's also described in the readme of the patch from ffgriever.

Ooops! You are of course correct, as it is intended to be the same path and name as used for modchip Dev2 booting. I just got a little sloppy with my copy-pasting...

I've now corrected that entry in my post above, to avoid misleading anyone.

Best regards: dlanor

[kevstah2004]

I was wondering if you could patch it load a ripped PS1DRV.ELF from BIOS then use PS1 RAW codes to cheat on original ps1 discs would it work? is it strictly a PS2 mode program or does it just alter scratch ram? worth a try.