Making Custom DevHook EBOOTs for your ISO's - PSP3D.com - Sony PlayStation Portable News, Homebrew, Hacks, Reviews, Videos, Mods, Forums

bboy_sonik · #1 (**permalink**) 09-03-2006, 09:21 AM

GUIDE - Making custom EBOOT loaders for each of your DevHook'd games

Well, if you want to have each DevHook'd game on your PC have it's own little EBOOT file with its own graphics and such, here is the guide. This is especially useful if you have several games that need different DevHook settings, as each game has its own INI file which is saved with each eboot

Needed-
- PBP Unpacker (free download)
- A HEX editor (I use Ultra-Edit, one of the best text/hesx editors, but XVI32 is a great free HEX editor)
- A 'baseline' devhook package - basically a working DevHook 2.71 installation on your PSP.

Guide

1. Have the game working fully with the standard devhook launcher. We need this to grab the working INI file. (NOTE - You can skip this part and do it last. It may be less confusing, especially if you do not understand this step at all. You will be reminded of what to do at the end if you skip this step.)
2. Create a stand-alone folder structure like the following (in a new path, on your PC). This structure is based on my working Breath Of Fire 3 ISO.

MS0

\

- dh

\

dh_bof3.ini (Example filename. This is a copy of the original devhook INI file, must be exactly 7+3 characters!)

- ISO

\

[Watever the ISO is that is specified in the INI file]. Is this case, it is "Breath Of Fire 3.ISO"

- PSP

\

-GAME

\

__SCE__DH_BOF3

%__SCE__DH_BOF3

Both as renamed from the DevHook folders. We'll assume you kept the correct EBOOT.PBP's from the DevHook folders.

NOTE - By "exactly 7+3", i mean that the file must be 7 CHARACTERS EXACTLY, THEN A DOT, THEN THE 3 LETTER INI EXTENSION.

3. Edit the EBOOT.PBP in the '%' folder (eg, %__SCE__DH_BOF3) with PBP Unpacker. Open PARAM.SFO. Change the title to anything you wish, then add an icon and wallapaper image from the ISO of the UMD. This would usually be ICON0.PNG and PIC1.PNG. ICON0.PNG is the EBOOT icon graphic, and PIC1.PNG is the picture that the entire wallpaper will change to when selected. This is the standard behavior of PSP UMD games, do not worry if the numbers are not the same - you just need an ICONx.PNG and a PICx.PNG to add your graphics, but add them into the EBOOT as ICON0 and PIC1 (NOT PIC0).

4. Save the EBOOT.PBP. It is all good to go now, except for the individual INI. You need to HEX EDIT the EBOOT.PBP to change the INI file used. We will edit the PBP in the OPOSING folder referenced to the last step, that is, the one NOT in the % folder. This one should be 178kb (if running DevHook v0.44.5 Mod, which is the best IMO). Do an ASCII search for ".INI", and change the reference from devhook.ini to whatever the working INI was renamed to. Now you see why we have to retain the exact filename length of the INI file!

Now you can save these files into your archive, copy to the PSP, and play away!

NOTE - If you skipped step 1, when you launch DevHook you will have to specify your ISO (corresponding to the graphics you made for that EBOOT) and change your DevHook settings. The DevHook settings (and the ISO) will be saved for that EBOOT only!

Any questions, comments or problems? Especially if i didn't explain it good enough? Well, sorry. Post away.

Cheers,
SoniK

Robkellas · #2 (**permalink**) 09-03-2006, 09:42 AM

Does this maen load iso's straight from an eboot. if so, then Your AWESOME

bboy_sonik · #3 (**permalink**) 09-04-2006, 11:42 AM

Ummm no, not exactly. It's an EBOOT, that loads DevHook - but it is a custom DevHook which....

-Has its own INI file, as opposed to devhook.ini. This is so, for instance, it will auto-load your ISO for the particular game, have a custom game graphic for the particular EBOOT, and keep settings you set in DevHook for that game;
-Has it's own EBOOT file to have its own graphics, and entry in iRShell / XMB / etc.

So in essence, yes, it will load an ISO straight from an EBOOT. But it is merely the simplest way to have multiple DevHook installations on your PSP so each EBOOT has it's own graphics, ISO (which auto-loads) and DevHook settings.

Also, the devhook folder with the fw dump in it is common - ie, each EBOOT and INI file you make for seperate DevHook launchers will use the same firmware (in the normal devhook folders). So the only thing which needs to be cloned and edited from Devhook is the EBOOT and the INI file, edited accordingly for your particular game.

Does that answer your question? It does invisibly basically. But it's based on Devhook.

I hope that makes sense to you and anyone else. It's a very handy guide i think, i like to have seperate EBOOT's for each ISO i have, so i can just select the ISO in my App List in iRShell or Games-MemoryStick in XMB

the1nonly1 · #4 (**permalink**) 09-04-2006, 11:53 AM

so say i have 2 isos on my PSP and instead of loading up devhook each time i can click on the eboot for that game and it will load devhook with the settings for that game and autoload? and i could have 2 eboots both for seperate isos

monkeyboy1916 · #5 (**permalink**) 09-04-2006, 12:30 PM

WOW, took me a minute to get what you were saying, but GREAT totally forgot about the ini's

bboy_sonik · #6 (**permalink**) 09-05-2006, 12:32 AM

Quote:

Originally Posted by the1nonly1

so say i have 2 isos on my PSP and instead of loading up devhook each time i can click on the eboot for that game and it will load devhook with the settings for that game and autoload? and i could have 2 eboots both for seperate isos

Yes. All the settings you specify in DevHook for a certain EBOOT will only be saved for that EBOOT - that's what the HexEdit on the EBOOT.PBP file is for. Here are some screenshots of how it turns out, when the guide os followed...

...Games in the XMB, each going into DevHook with their own settings and ISO

...the folder on ms0:/dh/. Notice the two different INI files (this is where the ISO file settings are, as well as the other DevHook settings). On my PSP, i have the firmware files in 271 - these are shared by each EBOOT you make (so no need to waste space - the only thing that is unique per game is the EBOOT and the INI File)

...the GAME folder under PSP.

Hope you guys give this guide a go. It aint too hard. Any questions, just ask. I can easily edit the first post if there is any part that isn't explained well enough.

It may be easier to skip the "have a working DevHook setup" part, i'll edit the first post to note that.

Cheers.

bboy_sonik · #7 (**permalink**) 09-24-2006, 11:37 AM

Thread is now dead. I am currently making software that does all this for you.

I'm surprised at the small amount of feedback i've had with this, either people don't care or they don't understand what this does :P

Anyway, stay true PSP3D members

Phant0m_Ph3wl · #8 (**permalink**) 09-24-2006, 11:53 AM

This is awesome

good luck with your software

bboy_sonik · #9 (**permalink**) 09-28-2006, 03:26 AM

Check out the post here guys for more information (http://psp3d.com/general-psp-discuss...our-isos.html).

I'm no longer subscribed to this thread so don't reply. I wish we could close our own created threads when we want, and not just GM's...