Premetto che i famosi osdxxx.elf servono, ma a noi servono solo quelli della cartella BEEXEC-SYSTEM e sulla nostra MC ne va solamente uno: in base al nostro modello di PS2. La sua dimensione reale si potrebbe verificare dal nostro file di configurazione di sistema (il mio di soli 5 Kbyte)
Ma non ho capito cosa ci serve adesso: i famosi "OSDxxx.ELF" e l' "OSDMAIN.ELF" o il "memento.bin"???
Perchè senza il Firmware memento non facciamo partire niente, personalemnte credo che: prima bisogna riuscire a copiare il FW memento e poi trovare gliOSD giusti per lapropria versione di PS2
PS: Su google ho trovato un archivio in merito... posso postare l'eventuale contenuto??? (vari osd e il FW memento)
Aggiornamento
Per capire quale "osd" usare bisogna seguire questa procedura:
- Dump del BIOS della PlayStation2
- Eseguire l'unpack con RomDir (se lo avete postatelo)
- Decomprimere l'osdsys con PS2Unpack (it should get around 3x as big after unpack)
- Cercare al suo interno le stringhe ".elf" e guardare i riferimenti all'osdmain.elf e all'osdxxx.elf (xxx stà per il numero del file che vi serve)
Da fonti non ufficiali ho acquisito l'informazione che il FW memento decriptato occupa circa 1.2 MegaByte
Aggiornamento 2:
Su un forum ho trovato questo post che mi è sembrato degno dinotifica da parte nostra...
Citazione:
I'm reading this thread since nearly it started since I'm very interested in the homebrew of the PS2 [I'm coming from the GP32, GP2x and Dreamcast scenes with lots of emulators and great homebrew software] and the VAST project. As it seems that there wasn't going to be a VAST version, I ordered myself a Memor32 and I'm very happy with this thing (together with my HDD...).
I just wanna put somethings together for myself and other not so familiar with the PS2 platform and this thread: The PS2 has an update feature which is used by the DVD player (coming with the official remote) and by the browser (coming together with the HDD connector). This feature tries to load a file from the memory card in slot 1 (name OSDMAIN.ELF and OSDXXX.ELF corresponding to the version of the PS2). The files seemed to be encrypted using Sonys own MagicGate encryption. Unfortunately there seems to be very poor information about this format, nearly zero. The encryption key seems to be made partially with the ID of the memory-card, so there is only one key per MC.
Now there are three ways to boot an ELF file by the PS2 using a MC: Having many manipulated MC with only one ID-number, resulting in only one set of encrypted OSDXXX.ELF files. This is used by the Mementoteam and answers the question "Why doesn't work the Memento firmware on my MC?!".
Or fooling the PS2 that the files are already unencrypted by the MagicGate chip on the MC and giving the PS2 normal ELFs to boot, like the Memory Plus by Datel (called "GateCrusher"?).
Or the last and best method, approached by the VAST project: Hacking the MagicGate encryption and making a program which encrypts the ELF files especially for each MC-ID number and putting that file onto the MC, so it can boot everything you want.
I hope, I got everything right, please say when I got something wrong. I see now three ways to continue: Getting the Mementoteam up to add the last promised (and already shown!) features, but they seemed to be faded away. Or hacking the firmware ourselfs and making it opensource. Or doing it the hard way and trying to crack the MagicGate encryption and making the VAST idea come true. And this, making SONY VERY angry...
|