How to patch TITLE.DB to autorun HDLoader as BOOT.ELF

OK, so this is the third time I have to start a new thread on this because my other ones were closed without my problem being solved. I also contacted a mod about this but got no reply so far, so here goes round three:

I want to have HDLoader autorun/autoboot directly from memory card. I don't want anything on it besides HDLoader and not boot from the HD, either.

Apparently, HDLoader won't boot up automatically if renamed to BOOT.ELF - that's a pitty. So far, the most effective way of fixing this seems to be patching the TITLE.DB file. I downloaded a patched TITLE.DB, but it does not contain any game IDs, so I doubt it'll even work with my setup. I'm using a PAL PS2 with FF8 as a trigger for the exploit.

Can someone tell me how to patch my own TITLE.DB to auto-execute HDLoader as BOOT.ELF without losing my game ID list?

Thanks a lot in advance!

I'm sorry if this is in the wrong forum (the first iteration of this was moved from HDD Discussion to Memory Card Hacking and the second was moved from there to HDD Discussion), being the third thread in a row with essentially the same question. Please, don't close this thread yet again before this problem is solved. Thanks.

Thats not what the file TITLE.DB is for.

Quote:

---

Originally Posted by ss256

Thats not what the file TITLE.DB is for.

---

That's actually the first thing that came to my mind as well. But can someone explain this to me?

Quote:

---

That's actually the first thing that came to my mind as well. But can someone explain this to me?

---

Well, I can't explain why it works, but my line of reasoning was this, "I wonder if it would work if I don't reset the IOP." Anyway, cut off your original TITLE.DB at offset 65808, and append to it everything in the patched TITLE.DB from offset 65808 to the end.

I just tested the patched TITLE.DB, and it works fine.

I used titleman.exe to add my own PSX id, named HDL as BOOT.ELF, put the two files on my memcard, and voila! It worked perfectly.

Quote:

---

Originally Posted by crazyc

Well, I can't explain why it works, but my line of reasoning was this, "I wonder if it would work if I don't reset the IOP." Anyway, cut off your original TITLE.DB at offset 65808, and append to it everything in the patched TITLE.DB from offset 65808 to the end.

---

Thanks for the info. I'll try that. Anyways, would I have to change 'mc0:/BRDATA-SYSTEM/BOOT.ELF' to 'mc0:/BEDATA-SYSTEM/BOOT.ELF' on my PAL system? I guess so ...

That's fine if there's a way, I guess. Ran into the same issue since my chip self-destructed and I needed the exploit as a temporary fix.

I was about to say, what's the big deal with using LaunchElf... it's only about 115K. You can make hdloader the default app and then set the timeout to zero so it loads right away. You barely see LaunchElf flash on the screen for just a split second. Plus if space is an issue, you should patch your hdloader with a simpler BMP for splash/menu. I have my ELF file down to just 311K.

How do you set the timeout to zero please?

Quote:

---

Originally Posted by adam31

How do you set the timeout to zero please?

---

Configure LaunchELF. Hit SELECT to enter configuration screen.


I tried everything suggested so far, but I still can't get HDLoader to boot as BOOT.ELF.

Maybe someone can help me in patching my TITLE.DB file:

Quote:

---

Originally Posted by DrGast

Configure LaunchELF. Hit SELECT to enter configuration screen.


I tried everything suggested so far, but I still can't get HDLoader to boot as BOOT.ELF.

---

from what ive gathered its impossible to boot hdl as boo.elf . it IS however possible to boot it directly if you rename it to HDA.ELF then add this BOOT.ELF in there. it is just not possible to boot it as BOOT.ELF alone but requires a redirect elf of some sort. its not that your title.db is wrong, its the method thats wrong.
heres the BOOT.ELF you need: