Sponsored Links

Sponsored Links

MultiMAN Cobra Manager (mmCM) v04.00.00, No Dongle Required


Sponsored Links
150w ago - Today MultiMAN Cobra Manager (mmCM) version 04.00.00 has been released, and those interested in updating multiMAN without the DRM-infected dongle can now do so as is it not required for non-Cobra multiMAN functionality on the PlayStation 3 console.

Download: multiMAN Cobra Manager (mmCM) v04.00.00 Update (20120112) / [Register or Login to view links] (184.72 MB) / [Register or Login to view links] (Mirror - 184.72 MB)

Previously multiMAN developer deank stated to the PlayStation 3 scene that he was not in bed with Cobra (aka Max Louarn), however, some PS3 developers such as [Register or Login to view links] appear to think otherwise, to quote via Twitter:

"Huge thanks to deank for leaving the scene and selling out to Cobra [/satire]"

Below is the multiMAN Cobra Manager (mmCM) v04.00.00 Full (20120113) changelog, as follows:

13 - 01 - 2012

  • Added support for jpg/png covers for BD/DVD ISO files in "Coverflow" mode
  • Added PIC1.PNG/SND0.AT3 (background image and music) support to lastGAME and "PSP Launcher" for PSP ISO files
  • Improved performance when extracting CSO to ISO and when creating ISO files from folders
  • SIXAXIS gyroscope affects screensaver mode (wave/tilt the controller to navigate the starfield)
  • Improved "Coverflow" display mode
  • Added preparations for experimental support for multi-disc PSX games in CUE+BIN or ISO format for up to 4 discs. ("Required Cobra USB/FW update will be announced when PSX multidisc support is available")
  • mmCM 04.00.00 will work without CobraUSB dongle connected (click [Register or Login to view links] for more information). New mmCM users will have to install mmCM 04.00.00 FULL version..

Changelog for non-Cobra users updating from multiMAN 02.09.02 to multiMAN/mmCM 04.00.00:

  • Added function "Create ISO from folder"
  • Support for *.0/.31, *.001/.032, *.66600/.66631 split file formats
  • Join split files in file manager (select and copy the first file to get the rest joined)
  • New display mode "XBDM" - XBOX Dash Clone
  • Added option "Detect Game Title in ISO Images" to allow using ISO filenames and *not* scan for game names in local database
  • Improved scanning for retro roms/iso and covers (populating the Retro column)
  • New THEME format (.thm). One theme - one file. Easy installation within multiMAN/mmCM without going to XMB to install theme pkg files.
  • mmTM - Easy to use PC application to create thm files from folders (separate download).
  • multiMAN/mmCM will try to read disc volume labels and display in VIDEO column (BD/DVD entry) and in other display modes.
  • Added indication (rotating refresh icon next to the column icon) when multiMAN/mmCM is loading/extracting title thumbnails (XMMB mode)
  • Added pop-up notifications when new versions of multiMAN/mmCM and Showtime are available for download
  • Added pop-up notification when running low on disc space (less than 1GB on internal HDD)
  • Added pop-up notification when multiMAN/mmCM successfully connects to nethost folders during startup (/net_host# in File Manager)
  • Added support for downloading themes in a background thread (pop-up messages will notify user when download starts and completes)
  • Added support for copying big (4+GB) files in File Manager to USB drives. multiMAN/mmCM will split source file when copying to USB.
  • Changed option "Link Video Library to Showtime" - it will only create links for XMB Video files, but will not start Showtime
  • Added shortcut (virtual folder) "XMB Video Files" when browsing HDD/USB drives in VIDEO column
  • Added "Showtime Font Preference" option to select 10 different fonts for SHOWTIME media player (GUI and Subtitles)
  • Added support to extract PSP CSO (compressed ISO) files in XMMB/XBDM display modes and File Manager (extracted image is saved in /dev_hdd0/PSPISO)
  • Added shortcut to ISO folder when browsing external USB devices (PSP connected with memory stick /ISO folder, containing CSO and ISO files)
  • Added music playback fade-out when leaving multiMAN/mmCM
  • Added download progress indication in XMMB/XBDM modes - Web column. An entry will show current download filename and percentage of completion.
  • Added TextViewer in File Manager (supported files colored in light blue). Supports viewing of ANSI/UTF plain text files.
  • TextViewer controls: L1/R1 - PageUp/PageDown, L2/R2 - zoom out/in (50%-250%), R3 - change font, UP/DOWN/LEFT/RIGHT - scroll/pan, L1/R1+SELECT - skip to start/end of file
  • Added support for browsing Video, Games, Favorites and Retro (ROMS/PS1/PS2/PSP) in "Coverflow" display mode. Change content mode with UP/DOWN.
  • Improved performance when extracting CSO to ISO and when creating ISO files from folders
  • SIXAXIS gyroscope affects screensaver mode (wave/tilt the controller to navigate the starfield)
  • Improved "Coverflow" display mode





Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!

Comments 1063 Comments - Go to Forum Thread »

• Please Register at PS3News.com or Login to make comments on Site News articles. Thanks!

PS3 News's Avatar
#613 - PS3 News - 60w ago
Today magneto states that the Cobra USB DRM dongle produced by Max Louarn and marketed by Gary Wayne Bowser (aka GaryOPA) is going open source now that they have their new ODE cash cow, just as they did with the True Blue DRM-infected dongle and countless other projects they profited on from the PS3 scene that should have been free and open-source to begin with.

Download: [Register or Login to view links]

Below are the details, to quote from the overview.txt document:

Compilers needed:

- The toolchain at bsc.es/computer-sciences/programming-models/linux-cell is needed.
Cobra is compiled with ppu-gcc version 4.1.1. It is unknown if other versions will work.

- Other toolchains are known not to work. Mainly, due to incompatibilities with cryptcode, and with the macros at lv2/include/patch.h,
as well as with some asm code. Porting cobra to other toolchain would be a matter of transalitng those files to the new toolchain.

- sdcc, to comopile the i8051 binaries. Version 2.8.0 is used. It is unknown if a different version will cause any problem.

- sony sdk, to compile netiso and cobralib. Any version is supossed to work.

- gcc: (linux, mingw32, cygwin, etc), to compile the pc tools. these tools usually assume a little endian system like x86/x86_64

Overview of directories.

+ cryptcode
----+ include: include files with macros to encrypt functions
----+ src: the source code to decrypt functions (ps3)
----+ tool: the tool to encrypt the functions (pc)

cryptcode is a tool to encrypt functions with the purpose of obfuscate things a bit.
Additionally, it has the "suicidal" feature, which makes a function code to be destroyed after returning,
which is intended to be used on initialization functions that are not further used.

+ debug
----+ include
----+ src

Debug files to printf over lan. It also has patches to redirect kernel printf and the ttyWrite syscall to the library.
Debug library also works in ps2 emulator mode.
The files here are intended for debug phase only, and they are not linked when DEBUG is not defined.

+ lv1
----+ include
----+ src

Files for hypercalls and lv1 related functionality.

+ lv2
----+ include
----+ src

The lv2 kernel cobra "sdk".
It contains the defintions of a bunch of lv2 kernel functions for all kind of functionality (io, memory, processes, threads, modules, synchronization, etc).
The file symbols.h has the addresses of the functions. Some symbols have only been resolved for 3.55.

+ lv2gen

Tool to merge stage0 and stage1 with lv2 kernel.
To compile stage1, original encrypted lv2_kernel.self of 3.55 must be placed in this directory.
This tool requires failoverflow tools to be installed and be on the path.

+ stage0_file

Stage 0 of cobra, merged along with stage1 inside lv2_kernel.self.
It just changes the protection of lv2 kernel memory and then jump to stage1 (0x7f0000).

+ stage1_file

Stage 1 of cobra, it loads and decrypts stage 1.5 from cobra.
The current code is a bit difficult to understand, but it is basically a very simple virtual machine
with 4 opcodes and some obfuscation, that receives the opcodes from cobra usb. Operations end in a xor with a table.
The small vm code does stage 1 integrity via the md5 functions of lv2 kernel, and it also checks that some functions of the kernel are untouched.
It is intended as a first barrier against attackers, more protections are in stage 1.5.

Because of its "exotic" way of working, any code change or compiler change will break the code, it was not intended to be modified.

+ stage1.5
---+ gen: pc tool to generate the modified i8051 rom.
It modifies the opcodes of the given i8051 program. In addition, each data of each opcode is also xored with different values.
Furthermore, the full ROM is xored again with keys that are residual data from stage 1.

----+ loader: the i8051 program, must be compiled with sdcc. It checks that lv2 kernel, stage0 and stage1 haven't been modified, it does some handshake with the device to
check cobra usb authenticity, and it decrypts stage2, which is inside stage 1.5. It also self-checks stage 1.5 against modification.

----+ vm: the vm that implements a simple i8051 emulator. The opcodes and obfuscation xor values are autogenerated by the gen tool in opcodes.c file.
Currently, generation of stage 1.5 requires to modify some vars in the Makefile, this was intended to be automatic in the future by the stage1.5_gen tool.

----+ stage1.5_gen: it generates the encrypted stage1.5 file, that can be directly flashed on the device.

Stage 1.5 protection mechanism includes some additional operations ("side effects") done in the md5 functions (vm) to complicate reverse engeneering,
emulation and debugging techniques such as hooks.

Most attackers would assume that it is just a md5 function after seeing some constants, and they would stop the reverse of the function.
This protects against both: emulation where the attacker blindly implemented the md5 function, and some hooks where the attacker would hook the function:
calling original function, returning to his code and giving the proper value of the md5 without realizing that the state of the vm (instrCount) has been
modified with the data passed.

+ stage1.5_lan

An unprotected implementation of stage1.5 that loads decrypted stage2 from lan. Useful for debugging: flash stage1.5_lan to the device and you can send
stage2.bin with graf chokolo "sendfile" tool upon ps3 boot.

+ stage2

Cobra core itself. It implements almost all functionality of cobra (except ps2 and network isos). Its functionality is made available to the gui program (manager)
via syscall8 with subopcodes. (see syscall8.h). Every pointer in these syscalls is reduced to 32 bits (get_secure_user_ptr function) for security purposes.

----+ storage_ext.c: it implements the disc emulation system, providing functions to mount/umount disc files, and to send insert/eject events to devices.
In 5.0, a "proxy system" was added, so that the actual read could happen in user mode via ports/queues.
This is currently only used for the network iso features, where the network code is done by an user mode sprx loaded at the vsh process by the gui program.

----+ modules_patch.c: it contains the patches to user modules. It also implements some syscalls, so that the gui program can load a sprx in the vsh process to have resident code.
This is currently used only for network iso, but it could be used in the future to implemented "plugin" features, like resident ftp or something.
Due to security concerns, all modules of the firmware are currently hashed, this is to avoid the gui program and the netiso sprx to be easily dumped,
although that wouldn't be critical anyways.

----+ psp.c: it implements the reading of psp isos. See modulespatch.c for patches. Currently 3.55 and 4.00 psp emulator are supported. The gui program is able to mount
an encrypted fat32 image with the sys_storage_ext_mount_encrypted_image (storage_ext.c)
This is currently used to hide the 4.00 ofw emulator (which is further encrypted with our own sprx encryption), which is located in the "lambda.db" file in the
psp launcher package. Other than that and having a way of starting the psp emulator, the psp launcher doesn't have any function, the rest of the content is
filled with random fake data and black png images.
Currently mode 1 = 3.55 emulator, mode 2 = 4.00 emulator. The gui program determines which emulator to use by either user selection of mode,
or by a fixed list if mode is auto. (see cobralib).

+ stage2_cipher

PC tool to cipher stage2.


+ ps2emu
---- + include
---- + src

The ps2emu cobra "sdk".
It contains the defintions of some ps2emu functions.
The functionality is quite limited compared to the lv2 one, but there are still functions for file access (internal hdd only), libc, etc

The symbols.h contains the addresses of the functions.
Either PS2HWEMU, PS2GXEMU or PS2SOFTEMU must be defined to select between the "almost full hardware" emulator (CECHA, CECHB),
the gx emulator (CECHC, CECHE) and the software emulator.

+ ps2emu_gen

Tool to merge ps2emu stage1 with a ps2emu. Original 3.55 ps2_emu.self, ps2_gxemu.self and ps2_softemu.self must be placed in this directory to compile ps2emu stage1.

+ ps2emu_stage1_file

Stage1 for ps2emu, which is merged with emulators .self. It loads an encrypted ps2emu stage 1.5 from internal hdd, that previously cobra core wrote to a temporary file.
Compile with "make -f Makefile.hwemu", "make -f Makefile.softemu" and "make -f Makefile.gxemu" to select each emulator.

For the encryption, modification date of the file is used the key as well as very minor obfuscation to hide file name, further protection is done in ps2emu stage 1.5.
A different key is used for each emulator.

+ ps2emu_stage1_file_debug

Same as above but without protection, intended for debuggin purposes. It loads directly a decrypted ps2emu stage 2 skipping stage 1.5.
PS2EMU_DEBUG must be set in cobra core (lv2 stage2).

+ ps2emu_stage1.5
----+ gen: pc tool to generate the rom of i8051 program with modified opcodes, encryption, etc. Pretty much like its lv2 counterpart, except that it takes two i8051 programs
as arguments.

----+ preloader: first i8051 program. It sets the keys of the second i8051 program using predictable rand function from sdcc, and reboots the virtual machine at the addresses
of the second program.
----+ loader: second and main i8051 program. Decrypts and loads stage2. Some protection to avoid modification of ps2emu as well as self-modification is done.
Some protection is done using unused part of the ps2 emu arguments that were set by lv2. See lv2 stage2.
----+ xtea: small ppc program with xtea algorithm. It is to be used by loader.
----+ xtea_cipher: pc progra, it encrypts the xtea binary with lightweight encryption that can be handled by virtual program, and converts it into an array suitable for sdcc.
----+ vm: the vm that emulates a modified i8051 machine. Pretty much like its lv2 counterpart, with some slight differences.
----+ stage1.5_cipher: it ciphers the ps2emu stage 1.5, making it ready to flash to cobra usb.

+ ps2emu_stage2

The core of the ps2emu code. It handles the disc emulation in the ps2 lpar.

----+ common: the part of the implementation that is common to the 3 emulators. Disc emulation itself is really here. Also, code to read non original ps2 dvd is here.
PS2 emulator tipically read most dvd sectors by using a 2064 bytes raw read using an unofficial/undocumented/propietary scsi command.
However, this command only works for original discs, and there doesn't seem to be any way to bypass this from the ps3 software side.
The workaround to make DVD+-R to work is implementing the 2064 command by reading 2048 bytes from disc and faking the rest of data,
just like it is done for isos anyways.

----+ hwemu: the part of the implementation that is specific of ps2_emu.self
----+ gxemu: the part of the implementation that is specific to ps2_gxemu.self
----+ softemu: the part of the implementation thati s specific to ps2_softemu.self. Very similar to the gxemu one.
----+ stage2_cipher: pc tool to cipher ps2emu stage2.

+ netiso: user sprx with the implementation of network isos. This sprx uses the sys_storage_ext_mount_discfile_proxy function to get the disc read requests from kernel.
This sprx is loaded by the gui program in the vsh process space. Because of the special way in which is loaded, the start and stop routines must follow some rules:
start routine can't use some functions and it must end with a thread exit using directly the lv2 syscall and not the library function.
Same goes the stop function, but additionally, the stop function must finalize the module by itself.

+ ps3netsrv: pc application with the server code for network isos.

+ sprx_cipher2: tool to encrypt self/sprx for cobra usage only. Keys for gui (manager), vsh plugins (netiso) and 4.00+ psp emulator are different.

+ encrypt_image: it encrypts a fat32 image. Used currently to hide 4.00 psp emulator.

+ cobralib

The library given to the gui programmer. It encapsulates the syscalls to make things a bit easier to understand. It also does some processing, like psp keys setting,
and discless jailberak game setting.
For example, discless games in jailbreak format are implemented like this: an empty dummy ps3 iso is created by cobralib and mounted. After that, the jailbreak
game is mounted with the standard path redirection method. This approach allows to have disc command emulation at the same time that the standard path redirection, allowing
a near 100% discless compatibility.

+ usb
----+ cobramakefirm5.0: tool to create a cba file. The 5.0 directory includes the files that were used to generate cobra 5.0 firmware.
To generate a new firmware, replace the content of that folder with new stages 1.5, leave mcu.bin and other files, and use "cobramakefirm 1 5.0 newfirm.cba"
----+ cobraflash: the flasher that is distributed to users.

+ cobrausbupdater: the ps3 version of cobraflash. Why are there idiots that try to reverse this when they have a pc version easier to reverse is unknown, but this application is unprotected because there is anything too useful for attackers there.

Finally, from deank: Without recompiling you can't port it to a different firmware. The latest cobrausb FW6.0 was for 4.30, so you'll need to change a lot of stuff to make it work on 4.50.

From CaptainCPS-X: So, yeah deank is right, we indeed need the source to be able to compile the CFW elements that need to be changed, payloads alone wont do the job.

vronz , payloads alone won't do the job. The article is not talking about USB dongle, or specific micro-controller source code and neither am I, if you research more you will notice it is talking about CFW modules and other needed tools.

So to give you an idea, lets say you get the magical payload, you will need to have the CFW with needed changes so it is able to interface with it, or else it will not work.

Lets say a Windows application to play mp3 and wav media, use functions from a Dynamic Library (DLL) but when compiled it didn't include a module to load mp3.

You load the application and try to play an mp3, what will happen? a message will pop-up about windows not being able to find the module required to play mp3, then to fix it you would have to recompile the Dynamic Library, this time including the new module to handle mp3s.

If you still believe we don't need any source code, then well, I tried to explain it . SeeYa!

Finally, from an0nym0us: You are mostly right, the majority of the code that they will be releasing is useless DRM protection they used to detect change, and brick the dongle. Much of which had been reversed already anyway. They probably are not selling many if any units anymore either, so that for sure was a factor. And of course it is to drive public sentiment of their profiteering in the ODE market.

But the "good for the scene" part has some truth to it. The patches used for bdemu for instance will be quite useful to replace the method that has been in use since 2010. Some of the other patches that remained unique to the Cobra USB will also be valuable to the scene.

At the end of the day though, for me personally, the choice to open-source now is a too little too late scenario. This company created its own reputation of being slimy snakes, and shedding skin now will not change that.

drphuz's Avatar
#612 - drphuz - 60w ago
So what does this do dump bluray keys and totally pwns the syskernel?

Also below is a Cobra ODE review from Senaxx as follows:

Note: I have received the Cobra ODE some time ago and it took me some time to review the unit and complete the review due some personal circumstances. This is not because of Playstation 3 Crunch (aka Gary Wayne Bowser alias GaryOPA) or Team Cobra (aka Max Louarn).

The Promise

Cobra ODE claims an easy install and it work on any Playstation 3 with any original firmware. My job to find out if the product works as good as advertised.

In the package

Team Cobra delivers all the cables to install the Cobra ODE in any type of Playstation 3. No matter if you have a PHAT (1k) SLIM (2k and 3k) or SUPER SLIM (4k). There is no need to find out what package you need for your model of Playstation 3. Just order the package and you are ready to go.

s3nint3!All the items you will receive in the package

You will receive:

1 x Main Cobra ODE board
6 x Ribbon cable (needed for different models of Playstation 3)
1 x QSB (needed for SATA Playstation 3’s)
3 x Power replacement cable
1 x USB Addon board
8 x Clips to attach the USB addon board to your Playstation 3
2 x USB connection cable
1 x USB extension cable
1 x USB Y cable




Installation

I have done the installation on a PHAT CECHG04 Playstation 3 and it was a fairly straight forward and easy install. One thing is to make sure you read up in the manual before you start. You have to make sure you have the right ribbon cables (!) for your model Playstation 3. I did some reading on the PS3 Crunch forums and a lot of users claiming their Cobra ODE didn't work was purely because they didn't use the right ribbon cables on their installation. After using the right ribbon cables this solved the issue for the people.

s3nint3!My PHAT Playstation 3 didn't require any soldering since it has a PATA Bluray connection interface. (This is up to the CECH Kxx Playstation 3 model / DIA-002). And as long your Playstation 3 doesn’t require soldering the installation can be done in a few minutes.

If you have a SATA model (CECH 25xx. CECH 3xxx and CECH 4xxx) you may want to brush up your soldering skills since you need to solder a small addon board (QSB) in the Playstation 3. You need to remove two tiny capacitors from the motherboard and solder the addon board (QSB) to catch the SATA signal. This can be pretty difficult for novice people who have no to little solder experience and need some help from a professional. But as soon the QSB is in place the rest of the install is pretty simple.

The only thing you will see installed on the outside of the Playstation 3 is the little addon board where you connect the external hard drive or USB Key.

Usage

The Cobra ODE supports two modes: Pass trough and emulation mode. You need the pass-through mode if you want to play an original disc in the Bluray drive and you choose for emulation if you want to boot an ISO from your external hard disk. Some earlier tests revealed that some external hard drives draw too much power from the Cobra ODE and because of that Team Cobra included an extra USB Y cable to add some extra power to the Cobra ODE.

By default Cobra ODE supports NTFS and FAT32 and because of this it should be fairly easy to put your “backup” ISO’s on the external hard drive and there is no need for extra software or tools. The Cobra ODE can only read games from an external hard drive since it has no access to the internal hard drive from the PS3. The only tool you need from Team Cobra is genPS3iso to generate a valid ISO from your PS3 folder structure.

s3nint3!These files need to be original and the Eboot.bin cannot be modified because you are booting on an OFW Playstation 3. DUPLEX had some games released with an added crack intro and supplied an extra original eboot. If you didn't replace the eboot before your ISO generation the game would not work. This is not the fault of the Cobra ODE but due security limitation from the Playstation 3 firmware.

The Cobra ODE requires to you to use a certain folder structure and two files supplied by Team Cobra. They supply a cobra.db file and a manager.iso. Furthermore you only need to copy over your generated ISO’s to the external hard drive and you are ready to go.

Homebrew support

The Cobra ODE also has the option to boot homebrew as long it is signed right and created in the right ISO format, and since we are used to multiMAN since the beginning I've contacted DeanK to get multiMAN working, since multiMAN is the most popular homebrew program together with Showtime.

After some testing from me, and a lot of development from DeanK we were able to make a version that is compatible with Cobra ODE (and other ODE’s). And if you really dislike the Cobra Manager made by Team Cobra you can replace the manager.iso with multiMAN renamed to manager.iso. By default after a cold boot you will be able to start multiman and mount the right ISO and start the game. Showtime is also already confirmed working on the Cobra ODE, more homebrew is getting ready.




But keep in mind since there is no peek and poke and you are bound by GameOS a lot of options are not available or need adjustments to make the homebrew work on OFW.

Updates

As far as I can tell Team Cobra is always committed to their products and like with their previous Cobra products they always kept updating and making it better. With the Cobra ODE out for only a few week they already released several updates and bug fixes. Latest update included a hassle free restart option so you don’t need to leave the couch anymore. I noticed they also keep an eye out on the community and fix the bugs fast in their Cobra ODE and their iso tool genPS3iso.

Improvements I can think of

Cobra ODE is working perfectly and installation is pretty much straight forward. One thing to make installation a bit better is find a way to keep the ribbons apart. They are described really well in the manual but a lot of people still mix them up. Maybe they can put a little sticker on it with a color, or just a sticker with a number. This would make it less confusing for really novice installers. One other thing I can think of is the power connector on the Cobra ODE board. It uses a top down press method. I read from some people that had some problems with this power connector (not all the way pressed down) and to me it looks a bit fragile (but that could just be me). So I would prefer a different more sturdy power connector on the ODE side.




Verdict

Cobra ODE works as advertised and they even improved their product with adding new features for free. Team Cobra has responded quickly with updates for the Cobra ODE for people that had some problems with getting their hard drive detected. So together with the straight forward installation and great compatibility I can recommend this for all people that have a Super Slim ps3 or don’t want or can’t downgrade their PS3’s.

PRO
+ Easy install on PATA models
+ Easy to maintain and add new games
+ Feels pretty stable and solid
+ Support for all PS3 models.
+ Homebrew support
+ Planned PS2 and PSX Iso support
+ Compatible with latest official firmware (4.50)

CON
- Can be expensive
- With little to no solder skills you need the help of a professional for installation on a SATA model
- Almost no difference in ribbon cables can be confusing

From asapreta: TIP: fix the ClipON on SuperSlims using HellermannTyton Cable Ties

The pictures talk for themselves:

s3nint3!s3nint3!

PS3 News's Avatar
#611 - PS3 News - 61w ago
Below is multiMAN 4.46.04 Base (for BD-R and ODE) and Showtime 04.03.536 CEX / DEX from deank with details as follows:

Download: [Register or Login to view links] (14.94 MB)

I found what was wrong... The first time mM is started it defaults to "options_default.ini" which is set for "BLES80608" and inside there are options for themes and covers. Now all should be fine. If you wish to keep the covers from the FULL .iso don't delete the game data and give this .iso a try. (Of course editing the .ini will also work, but it is easier to use the fixed iso)

Let me know how it goes. Themes and covers should now work, although covers will not download all-at-once but only one by one when it tries to display them and finds that they're missing.

Also there is small change in this version when activating a game. The prompt is changed to:

[Register or Login to view code]

This would allow the user to either soft-reset by using "Quit game" or use the manual "Eject-Reinsert" method by simply pressing [X] for OK.

Download: [Register or Login to view links] (27.06 MB)

  • Includes SHOWTIME for multiMAN. I tried another approach suggested by kakaroto to start Showtime. I have no idea if it works so let me know.
  • If it works it won't be needed to load a different ISO for showtime each time, but simply call it from mM.

The included version of showtime is 04.03.536.

Can we do another final test please:

Download: [Register or Login to view links] (27 MB)

Please delete GAME DATA for mM before you try this iso. It includes the latest showtime and it should not require any usb/sd/cf/ms storage attached.

1) Try to start showtime from mM (or try to start a video from the VIDEO column in mM)
2) Check if it plays
3) Change some of the showtime settings
4) Quit showtime - when you QUIT please do not use the "{PS}" button but the showtime interface (TRIANGLE -> Exit showtime)

Then try again just to see if showtime settings are properly saved/reloaded.

Download: [Register or Login to view links] (27.06 MB) / [Register or Login to view links] (Mirror)

  • Supports ODDE MCU 1.0, 1.1, 1.2, 1.3 and later
  • Supports downloading game covers
  • Supports downloading themes
  • Includes Showtime for mM 04.03.536 by Andreas Oman (so no need for separate ISO and reset/eject/reload)
  • Changed exitspawn method (thanks to kakaroto for the suggestion) - that means that now RetroArch or other apps can be seamlessly integrated again with mM on OFW + ODDE

I just released showtime for the regular CFW mM online, too and also as standalone... Available in mM's webcolumn and from video->update showtime.

Download: [Register or Login to view links] (5.95 MB) / [Register or Login to view links] (6.01 MB)

p.s. Should I presume that you tested this last iso and all is ok?

Update: multiMAN 4.46.05 BASE with SHOWTIME4MM (for BD-R and ODE) is now available.

Download: [Register or Login to view links] (27 MB)

  • Added support for dumping PS3 game discs to ISO
  • Added support for mM online updates (in ISO format)
  • Removed a lot of stuff from "Settings" column, which do not apply to ODDE mode
  • Separate "what's new" and online updates

To test: Go to the GAME column, you will see a "PLAYSTATION3 GAME DISC" entry - press [TRIANGLE] and then "Create ISO". It will ask for destination (/dev_hdd0 or /dev_usb... or whatever you have connected). Let me know if it creates the ISO properly and if you can re-use it afterwards.

marvinx's Avatar
#610 - marvinx - 61w ago
its nice to find all the info in one place. Great thread well done

Below is a Cobra ODE Troubleshooting Guide by magneto also:

In case you have problems getting the COBRA ODE to work, or if it is unstable, then read the following troubleshooting guide first before creating a new thread.

ODE CHECKLIST

  • Make sure you used the right cables, the length may not matter but pay attention to the same-side contacts and opposite-side contacts cables, where same-side contacts has the blue side on the same side of the cable, and opposite-side contacts have the blue side on opposite sides of the cable.
  • Make sure all the cables are connected with the blue side on the top.
  • Make sure you pushed the cables all the way through, and they are securely in place. The cable must not come from an angle that would tilt the cable out of its connector.
  • Make sure the power cable is connected in the right direction. The white cable can be plugged in both directions between the power supply and the PS3 motherboard, but only one direction will work. Refer to the pictures in the user manual for the way to install it properly.
  • Make sure the ODE board is isolated from the drive. The COBRA ODE bundle comes with a sticker with the COBRA ODE logo on it, that's a double-sided sticker and must be used to isolate the board to avoid shorts which can cause failure or instability.
  • Make sure the PATA/SATA and CECHL,2K/2k5,3k,4k switches on the ODE are set to the correct position.
  • Make sure the QSB is soldered correctly, that all 8 contacts are soldered properly and there are no shorts between them.
  • If using NTFS, make sure that NTFS partition is using a 4096 cluster size, and that all the files are correctly placed in the COBRA directory.
  • If using FAT32, make sure the FAT32 partition is the first partition on the drive.
  • Make sure you always "safely remove hardware" or eject in Windows before removing your HDD from your PC. Not doing that could cause the partition to be corrupted when you remove the HDD and may not work with the ODE until the partition is repaired.
  • If the HDD is using too much power, make sure you connect it properly with the USB Y cable provided for that purpose. Connect the USB Y cable to a USB wall charger or a PC nearby.

TROUBLESHOOTING GUIDE

Q: When I connect the power, the PS3's LED turns off
A: If on a SATA model, make sure you used the right side cables between the motherboard and the ODE and the ODE and the drive. Also make sure you connected the power cable in the right direction for the ODE. If an HDD is inserted, try using the USB Y Cable. Also make sure the ODE is properly isolated using the double sided sticker.

Q: PT works, but not EMU:
A: You used the wrong cable, for PATA, invert the two cables, for the QSB, use the opposite-side cable between the QSB and the ODE.

Q: EMU works, but not PT:
A: You are probably using the QSB and one of the pins on the QSB was not soldered correctly.

Q: When I insert the HDD, the PS3 shuts down:
A: The HDD uses too much power, use the USB Y Cable to provide it with additional power.

Q: I use the USB Y cable but the PS3 still shuts down when I insert the HDD:
A: Alternatively, you can connect a mini-usb cable to the mini-usb port on the clip-on PCB and use a wall charger to power the board.

Q: There is no disc icon when I boot the PS3:
A: Your cables are not connected correctly, or you used the wrong type or cable, or the QSB was not soldered properly.

Q: I get error 8001003E when I try to run a game :
A: You generated the iso with an old version of genps3iso tool. Download the latest version and regenerate your iso file.

Q: When I run the game, it shows error 80010007 or returns to the XMB directly:
A: You generated your iso using a modified rip. DUPLEX releases will modify the EBOOT.BIN which makes them invalid, there will usually be a EBOOT.BIN.ORIG file in the rip, simply replace the EBOOT.BIN with the original file and regenerate your iso.

TIPS AND TRICKS

  • You can setup your HDD with a 10MB partition as the first partition and the second partition as NTFS taking the remaining space of the HDD. You can use the FAT32 partition for MCU updates and the NTFS partition for games, this way you can use the same HDD and do the update and go back to your games in one shot.

To Be Continued

drphuz's Avatar
#609 - drphuz - 61w ago
No problem

Sponsored Links

Sponsored Links
Sponsored Links

Sponsored Links







Advertising - Affiliates - Contact Us - PS3 Downloads - Privacy Statement - Site Rules - Top - © 2014 PlayStation 3 News