KELFBinder [obsolete]

PS2 KELFBinder [obsolete] DEPRECATED

Hello, I tried to install this, now my freemcboot auto boots to opl and I cannot do anything else. Exit to browser still boots opl, cannot use rescue.elf etc..any ideas?
 
Run FMCBInstaller, or wLE then FMCBInstaller, from the APPS menu of OPL.
What have you done exactly, you installed OPL as OSDSYS update ?
 
Run FMCBInstaller, or wLE then FMCBInstaller, from the APPS menu of OPL.
What have you done exactly, you installed OPL as OSDSYS update ?

So i was reading the guide "updating dvd player" by Berion and it said this: "The other alternative is the KELFBinder application, with which the entire operation can be performed on the console side ". So I started looking at Kelfbinder (now I assume I still had to do additional steps), ran the dvdplayer.elf and then the system.elf which is what caused this problem I think.
 
Can't edit post, but even using the fmbc installer from opl apps will just load opl (i use hdd).
 
This application taking kbit and kc fields from properly signed XLF (in this case SYSTEM.XLF) to another XLF (in this case DVDPLAYER.XLF) signed for different Memory Card. Allowing user to use this "another XLF" as bootable (because MG sign is per card, not proper sign results in ignoring by OSD Update).

And that's all what this application doing. You can do this by hex editor like in my tutorial, and it will be the same. I don't see any connection to Your issue. To make that what You described, You need to edit FREEMCB.CNF, put OPL executable in autoboot or under hot button while Your joypad constantly pressing this specific set button. Or in FMCB 1.8b and older, embedding OPL.
 
This application taking kbit and kc fields from properly signed XLF (in this case SYSTEM.XLF) to another XLF (in this case DVDPLAYER.XLF) signed for different Memory Card. Allowing user to use this "another XLF" as bootable (because MG sign is per card, not proper sign results in ignoring by OSD Update).

And that's all what this application doing. You can do this by hex editor like in my tutorial, and it will be the same. I don't see any connection to Your issue. To make that what You described, You need to edit FREEMCB.CNF, put OPL executable in autoboot or under hot button while Your joypad constantly pressing this specific set button. Or in FMCB 1.8b and older, embedding OPL.

Doesn't matter what I put in the config, it will always boot OPL, even if I run FMBCinstaller from within OPL it still kicks back to OPL. I am able to run WLaunch from OPL but if run any ELF file it just loads OPL (i have a hdd).
It happened after I installed Kelfbinder-system.elf
 
Last edited:
I don't know what have You done exactly. For sure Your problem isn't connected to KELFBinder in any way. I told You what are possibilities of such FMCB behavior. If You want change it, place uLE on USB as "mass:/RESCUE.ELF" (it will run on FMCB start) or default "mass:/FREEMCB.CNF" from FMCB installer which will be used instead one on Memory Card.
 
For sure? So it's just coincidental that after I ran Kelfbinder-system.elf this problem occurred...And I already mentioned what I did exactly, including the rescue.elf etc. My OPL ELF is located on the USB and even without it it still boots.
 
For sure. You did something else after that and You don't know, or don't remember. :P

That's discussion is pointless. The best would be if You just make memory card image (run uLE from OPL apps if You can and by uLE run MCA from USB), compress it by 7z, rar or whatever and attach here or upload to mediafire or mega. I will look inside and tell You Your sins. ;]
 
Look at Berion acting like some ps2 god, hilarious. I did exactly what I said I did.
Let me quote something of you: "On top of that; did You used DVD Player update? It could introduce some unexpected behaviours at least on OSDSYS side. "
 
Look at Berion acting like some ps2 god, hilarious.
I don't know from where this conclusion came from...

I did exactly what I said I did.
Something more You did and You are not aware of that. That's the case here I believe.

Let me quote something of you: "On top of that; did You used DVD Player update? It could introduce some unexpected behaviours at least on OSDSYS side."
Let me say something to You: applications aren't self aware and don't thinking, especially abstracting thinking. This program, literally read some bytes and replace some bytes in chosen by author files from specific locations. What You suggesting is doing that plus looking for OPL which can by anywhere on any device under any name and replace by it all OSD Update paths - which is ridiculous. It looks like You've put in "mass:/__KELFBinder/SYSTEM.XLF" the OPL if what You said is even valid. And that's the reason why krHACKen asked about it.

That's why I said You should make memory card image and attach it, so we could see how Yours mc looks like really - that's because You cannot say what exactly and everything You did... But You know what? I lost interesting in this now. So good luck.
 
Is there any significant difference between the installation process of this version and the v2?
I know v2 has a new user interface, but I am curious about the installation process itself.
What's different between this and FMCB's installer?
 
Is there any significant difference between the installation process of this version and the v2?
I know v2 has a new user interface, but I am curious about the installation process itself.
What's different between this and FMCB's installer?
KELFBinder 2 was coded from scratch while this was based on FreeMcBoot installer.

Enecryption process is the same, the diff is that KELFBinder 2 will do the full encryption each time you order it to install, instead of trying to clone the encryption of an already installed update like FMCBInst does.
 
  • Like
Reactions: TnA

Similar threads

Back
Top