82w ago - Although PlayStation 3 developers have already commented on DRM-infected dongles, following in the shadows of JB-King and JB2USB today we have a third PS3 JailBreak 2 (JB2) True Blue (TB) dongle clone dubbed PB2 entering the market.
To quote from the official site (linked above): PB2 (PS3Break2) is the latest product from PS3Break Team who ever made a tremendous splash in the PS3 scene.
PB2 can break your own PS3 console and enjoy the latest and most popular PS3 games which require 3.6+ or 3.7+ PS3 firmware. The PS3Break team are focused on enhancing the user experience of our customers, play games with it easily!
Their official site (linked above) appears to be a simple template design similar to the others, while the DRM dongle is currently being peddled for $19.99 with the JB2USB PS3 JailBreak 2 (True Blue) clone details below, as follows:
JB2USB PS3 Features:
Booting of games designed for PS3 system software v3.6 and above
Runs your existing games and new v3.6+ games from HDD in conjunction with standard backup managers
Does not require the power/eject trick
Custom v3.55 Dongle firmware behaves like OFW when JB2USB is not inserted
Manufactured from highest grade components and Actel based
98w ago - As a follow-up on our previous article with the spirit of Operation: Mongoose in mind, we are continuing to examine both the Cobra and True Blue PS3 DRM-infected dongles and TB EBOOT files, and welcome any help with this project from other PlayStation 3 developers in the scene!
First let me tell you the following explanation is not a theory or any rumors, it's actually how the USB dongles work to allow different things.
We heard many rumors / theories about the process of the Cobra / True Blue but I didn't see anyone give any big answer about that (I'm not saying I would give you the big answer but the explanation how it works and how to make this possible)
Cobra / True Blue Part 1
Both dongle use syscall / payload (after a big investigation, both dongle also follow the work of graf_chokolo and the functionality of the dongle can be ported into a CFW (not a good idea from some devs I guess)
Cobra / True Blue use a lv1_wrapper (syscall implementation) that can allow to use subroutine function into kernel mode call....
98w ago - Below is a work-in-progress (WIP) of PS3 3.60+ games booting on PlayStation 3 Custom Firmware (CFW) 3.55 and 3.41 without a dongle for those interested in experimenting further with it.
What you need ?
1- PS3 3.55 CFW Rebug or 3.55/3.41 with Debug
2- Debug Dev_Flash (Also allow to have the debug options on retail)
3- Backup of your own CFW DEV_Flash (make a dev_flash path on your USB Device)
4- A File Manager
5- EBOOT.BIN of your games (also from Paradox)
What you need to know
Rebug normal in Debug mode 2
You need to put your PS3 in boot mode -> debugger mode (and not system software mode)
We're gonna use the debugger mode to debug the self execution we don't need to have NPDRM, anyway the debugger don't know how to Debug the Self NPDRM
Release mode -> Development mode
All the content type configuration -> Development mode
Dongle uses modified sprx/modules/lib related to the Debug files to be loaded when you boot the PS3 on CFW.
Almost all the EBOOT Paradox don't have NPDRM -> it's a simple self (fake sign header) renamed to EBOOT.BIN (like i was explaining many times) -> call function to the debugger -> sprx/modules loader.
100w 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.