MODDA.se
NyheterPlayStation 3PS3ModchipCFWqCFWBadWDSDRaspberry Pi PicoRP2040HårdvaraGaming

Modchip brings qCFW to PS3 Slim and Super Slim models that can't run regular CFW

12 juni 2026Source:Projektet på GitHub,Tråd på PSX-place

Update 13 October 2026: The original headline said "all models", which isn't accurate. BadWDSD supports PS3 Slim 25xx and 30xx and Super Slim 4xxx (eMMC models since September 2026). Fat and Slim 20xx/21xx models aren't on the list; they can run regular CFW. Read our guide qCFW on PS3: what it is, supported models and what you need.

A new hardware modchip, named BadWDSD, opens the door to running quasi-CFW (qCFW) on supported PS3 Slim 25xx and 30xx and Super Slim 4xxx models, which previously lacked Custom Firmware (CFW) support. The modchip utilizes a Raspberry Pi Pico (RP2040) to exploit a specific feature in the console's XDR memory, called WDSD (Write Data Serial Debug), to execute custom code early in the boot process.

Unlike traditional CFW, which cannot be installed directly, qCFW is a new variant heavily based on Evilnat PEX CFW. It offers virtually all CFW features, with the exception of dumping eid_root_key, but still enables functionalities such as HDD decryption without it. To ensure full functionality, Cobra must remain active at all times.

The developer describes the WDSD method not as a memory bug, but rather as an 'abused' feature. By sending data to the WDSD register during the early boot phase, custom code can be injected and executed when the console's processor starts. The method grants full access to the lv1 hypervisor. How reliably it works depends on the soldering and wiring: the developer says a proper install should succeed every time, but on Super Slim models with eMMC flash the strict timing means a 100% success rate isn't possible even with perfect wiring.

qCFW has some quirks, such as wireless controllers potentially needing to resync once at startup if the console is powered on with one. Updates to qCFW also require reverting to OFW (Official Firmware) first before installing the updated version.

The BadWDSD modchip does not replace previous exploits like BadHTAB but uses a completely different method to achieve custom code execution. Furthermore, it can be used to recover consoles stuck in FSM (Service Mode) or to update consoles with faulty Bluetooth/BD modules, as well as for downgrades. With proper installation, the console should be ready to XMB within approximately 30 seconds.