PS2 Updating DVD-Player

DTP stands for Dummy Test Program

it will reset IOP, do some basic stuff to allow printing on screen.

then it paints screen of red, prints a basic presentation and all argumments passed to program. then halts eternally

the .ELF is a common ELF
the .KELF is already encrypted with the DNASLOAD header. ready to bind into card
 

Attachments

Berion said:
Tutorial in both languages: Polish and English (and in case something would be hard to understand, look at few posts below where is translation attached by Aldostools made via Google instead to DeepL).

Changes from last time are few syntax colouring plus with additional warnings.
Click to expand...
@Berion
what about updating the guide using KELFBinder :eagerness:
 
That's good idea, but first I must dealt with all stuff which I still didn't finished. And there is plenty off. ^^

PS: I was thinking string for osd info is taking from executable. My bad. Thanks for clarification.
 
El_isra said:
DTP stands for Dummy Test Program

it will reset IOP, do some basic stuff to allow printing on screen.

then it paints screen of red, prints a basic presentation and all argumments passed to program. then halts eternally

the .ELF is a common ELF
the .KELF is already encrypted with the DNASLOAD header. ready to bind into card
Click to expand...

Thank you so much man, I will get back to you either tomorrow or Thursday with my findings :cheerful:
 
Pleased to announce that I have solved the problem.
Thank you everyone for your advice, particularly @El_isra for your help and for coding the dummy test program, I would've been completely lost without you. No doubt this will be a great resource for anyone else wanting to troubleshoot :cheerful:

I ran the DTP and was still returned to browser, so encryption problem I guess. I wondered if maybe my memory card was bust so I decided to dig around for a different one. I installed freemcboot, took osdmain.elf, and decided to retrace the exact same process I used in the first place to make sure the problem wasn't with KelfTwinSigner. surprisingly it worked perfectly.

I thought this was unexpected so I checked the file from the other mc again, in the output on my cmd, I noticed the kbit and kc were similar but not identical. So I guess I found the issue, my original memory card must be a bootleg or something, there's nothing visually that would indicate that but I got it from ebay so there you go. :beaten::crushed:

I highly highly recommend @El_isra 's Kelfbinder, It is an incredibly well made program. Once I got my head around what I was doing, I could see how it is a much easier and faster process than using KelfTwinSigner. Hopefully someone is able to make a tutorial soon, so that it can be even more accessible to the community. :applause:

Thank you so much guys :victorious:
 
I thought this was unexpected so I checked the file from the other mc again, in the output on my cmd, I noticed the kbit and kc were similar but not identical.
Click to expand...
kbit and kc always will be different for different cards.
 
Berion said:
kbit and kc always will be different for different cards.
Click to expand...

I meant that the kbit and kc were different from each other with just the first card in the output from kelftwinsigner.

In contrast, when I tried with my second card the kbit and kc showed identical to one another :encouragement:
 
  • Like
Reactions: TnA
lemonhead said:
I meant that the kbit and kc were different from each other with just the first card in the output from kelftwinsigner.

In contrast, when I tried with my second card the kbit and kc showed identical to one another :encouragement:
Click to expand...
IIRC KC is always the same and kbit depends on the KELF type.

Of course, both kbit and KC change after binding
 
lemonhead said:
I meant that the kbit and kc were different from each other with just the first card in the output from kelftwinsigner.

In contrast, when I tried with my second card the kbit and kc showed identical to one another :encouragement:
Click to expand...

Source file must contains valid sign for target memory card. That's why source file is eg. FMCB took from it because it must have it. Target file is file in which sign be cloned to make it "bootable", in this case hacked DVD-Player.

Normally, each Magic Gate PS2 Memory Card is unique, so sign be unique too. That's the reason why FMCB installing itself instead just copying some files in some places. They generating valid signing for itself.
 
What he means is, that the same card produced different values on different starts it seems.
 
Thanks for the tutorials, worked perfectly.

Small nibble: aldostool's version is missing the hyperlinks in it. Had to open the OG and his version to get the files.
 
cha0shacker said:
Thanks for the tutorials, worked perfectly.

Small nibble: aldostool's version is missing the hyperlinks in it. Had to open the OG and his version to get the files.
Click to expand...
You're welcome. ^^

Because it is how Google processing PDFs. You loosing links, fonts and formatting. In future I will update tutorial to make it based on KELF Binder, and it will be also in English (actually all my new tutorials will be dual language). But that's far future from now.
 
Hey! Sorry, I'm a complete noob when it comes to PS2 modding. I have an scph-30004 PS2 (with dvd version 1.20E) and was wondering if I could use this to update to a version that was supported by freedvdboot.
 
I understood Your earlier message that You don't have hacked PS2 yet. FMCB is a hack You can use, so yes, it is ok. Just follow the tutorial or read readme to KELFBinder and use it instead.
 
You must log in or register to reply here.

Similar threads

Back
Top