PS3 qCFW - Arrives to Slim (2500-3000) & SuperSlim (4000-NOR) PlayStation 3 Models

Major Updates
.
Original Article (Jan. 30): The evolution of PlayStation 3 (PS3) exploits rides high in 2026, In early-mid 2025 we seen developer and researcher @aomsin2526 (aka Chattrapat Sangmanee) show us a hardware exploit that provided some additional power to PS3HEN with the disclosure of the BadHTAB hardware exploit. The hardware exploit was soon replaced with another hardware exploit also from @aomsin2526 that we know as BadWDSD. While BadHTAB provided some additional functionality to PS3HEN like OverClocking & Linux Support. BadWDSD would proved to be the better foundation needed for what would become the next phase of the overall project.

Focusing now on the software side, the next phase from @aomsin2526 came in the form of a "qCFW" , this was a CFW that was built using Evilnat 4.92 PEX for the late Slim (2500) / SuperSlim (NOR) model PS3 Console's !!! While PS3HEN provided those once dubbed "nonCFW models" with many CFW like feature's, there were a number of abilities that were restricted to only CFW user's. Now with the release of BadWDSD with qCFW that gap has shrunk considerably to where 99% of CFW task can now be done on a qCFW installation. The process for installation of a qCFW is different then the traditional PUP installation of a Firmware, but you will still be running what is essentially a ("quasi") custom firmware running the cobra payload and based off Evilnat PEX CFW. Allowing for even DEX features on a SuperSlim (NOR) + Slim (2500).

PS3HEN developer @esc0rtd3w also had some work in this project as PS3HEN is essential in the installation/operation of qCFW/BadWDWD. You must be running v 3.4.1 Beta-test #4 or higher for support of the latest qCFW installation. Checkout this hardware/software modification that will supercharge thoseSlim 2500/3000 & Superslim (NOR) models. Take note of your SuperSlim model as the eMMc models are not supported.

i-have-built-the-ultimate-ps3-super-slim-v0-6vggxy2we1ac1.jpg ps3_white_Superslim.jpg​
BadWDSD / qCFW Read Me PS3HEN- 3.4.1 qCFW Updates
  • Always view official link for latest updates: https://github.com/aomsin2526/BadWDSD
    .
    BadWDSD
    ​











    .​
    This is a hardware modchip for Sony PlayStation 3. By using Raspberry Pi Pico (RP2040), It is possible for non-CFW compatible models to boot qCFW.​

    Supported models
    • All CECH-2500
    • All CECH-3000
    • CECH-4x00 with NOR flash
    • 540772857-7066c760-a097-45ba-9697-6022c9cf1e07.png

    Models not Supported
    • CECH-4x00 with eMMC flash is NOT supported
    • 540773712-6592b99e-f80f-4319-a450-10a894aa5164.png

    Notice:
    1. One way to know if your console is eMMC or not is enter safe mode. If you see Change system storage option, It is eMMC.
    2. Other way is try to install Stagex. If it says Flash is not NOR then it is eMMC.

    qCFW Installation Update qCFW / Uninstall / .. OtherOS / Syscon NoBT & eMMc Support?

    • ​









      .What is qCFW?
      ​









      .You still can't install CFW PUP, so new variant of CFW must be made. This is called quasi-CFW.
      It is heavily based on Evilnat PEX CFW. And will support every feature except: Dumping eid_root_key and anything that needed it.​

      Note: Cobra must be active at all times or some feature will not work properly.

      qCFW quirks
      • For some unknown reason, When you turn on the console using wireless controller it won't sync. You must power cycle the controller for it to sync.

      Note on DEX mode
      • DEX mode is fully supported. But any kind of firmware installation or update is not possible while in this mode.
      • This means if you somehow need to reinstall the firmware such as corrupted HDD, you are stuck.
      • To recover, use BANKSEL pin on the modchip to go back to OFW.

    • Installation (Software)
      .
      FOR FIRST INSTALLATION, BACKUP FLASH FIRST!!!.

      IF SOMETHING GOES TOO WRONG AND YOU DON'T HAVE BACKUP, YOUR CONSOLE       MAY BE PERMANENTLY BRICKED
      ​
      1. Prepare the USB drive by DELETING old qcfw folder if existed, DO NOT OVERWRITE!! then download qCFW and extract it into your drive like this:
      1. Install PS3HEN 3.4.1 or later
      2. Plug your USB drive into RIGHTMOST USB port of your ps3
      3. On XMB, Enable HEN then use Network -> Hybrid Firmware Tools -> qCFW Options -> Install Stagex option. It must show Success
      4. If not already, Install the modchip by following Installation (Hardware) section
      5. After modchip installed and power plugged in, wait until LED of modchip becomes solid. If it doesn't solid after a while, check SC_RX/SC_TX wire
      6. Turn on the console. modchip LED should flash briefly with triple beep right after. This means exploit is successful. If your console keep turning off and on, check CMD/CLK wire and Stagex
      7. You should be on XMB now. now Enable HEN then use Install qCFW option
      8. If it tell you to reinstall firmware and try again, do it ONCE.
      9. Your screen will appear frozen. it is installing. This process take 10-20 minutes. If something goes wrong during this step, you should be still able to recover by entering safe mode and reinstall firmware normally
      10. Then it will reboot itself. you should be on qCFW and see Evilnat logo now.
      11. Congrats! qCFW installation is complete
      • From now on, modchip will be required to boot the console until you go back to OFW again
      • This can be done by reinstalling OFW/HFW firmware normally. Then after this you can disable or uninstall the modchip
      • If thing goes too bad to the point of not being able to enter safe mode at all, you can use BANKSEL pin instead.
      • If you flashed bad Stagex.bin or CoreOS.bin, see Recover from bad Stagex.bin or CoreOS.bin flash section.
      Installation (Hardware)
      .Currently, Raspberry Pi Pico (RP2040) and RP2040-Zero are supported.
      • Only install modchip after Stagex is installed to console flash from above section.Otherwise it won't boot,
        • if you already installed the modchip, You can use HOLD pin to temporary disable the modchip without unsoldering it.

      Since I don't have 2500 and 3000 model to test, it must be done by other people. If you know the solder location please tell me. Thanks.


      Pico
      RP2040-Zero
      3000
      4x00

      • To flash .uf2 file (it is included in qCFW zip), simply connect modchip USB port into your PC while pressing BOOTSEL button. Then new drive will appear, simply drag .uf2 file into it.
      • You should see LED blinking. Flash successful and ready to use. You can disconnect it from your PC.
      • Exclude power and ground, you only need to solder 4 wires that marked red (CMD, CLK, SC_RX, SC_TX). Other pin is optional.
      • It is possible to power the modchip using external power as long as it is active during ps3 standby

      Pin description
      SIGNAL PIN:
      CLK - XDR CLK signal
      CMD - XDR CMD signal
      SC_TX/SC_RX - Syscon UART signal
      DEBUG - Optional modchip UART signal, for debugging and accessing syscon (baud 576000, NOT 57600!)
      CONFIG PIN:
      Short to ground to activate
      HOLD - Disable the modchip without needing to remove power or unsolder
      LITE - TODO
      BANKSEL - Go back to OFW forcefully. It is equal to syscon command w 1224 00. Only use when absolutely needed. You can't turn on the console while this pin is shorted​

    • Update qCFW
      • You can't update qCFW while on qCFW. you must go back to OFW first.
      • Simply reinstall firmware normally, then use Install qCFW option with updated files on USB again. No need to do anything else
      • When updating files on USB, delete whole qcfw folder first. Don't overwrite or it may causes problem.


      Go back to OFW using PUP method (Recommended)
      • Always use this method when possible. Simply reinstall firmware as normal. No extra steps required.
      • If you want to uninstall the modchip, you can do so after this


      Go back to OFW using BANKSEL pin
      Avoid this unless absolutely needed.
      DO NOT GO STRAIGHT TO THIS PIN WITHOUT TRYING TO BOOT THE CONSOLE WITHOUT MODCHIP FIRST!, IF IT SHUT IFSELF OFF, THEN YOU CAN FOLLOW BELOW
      1. Unplug your console
      2. Short BANKSEL pin to ground
      3. Plug in your console, wait until modchip LED flashes very fast. Then it is successful. You can't turn on the console while this pin is shorted
      4. Unplug your console and unshort the pin. If necessary remove or use HOLD pin to disable the modchip
      5. Plug in your console again and turn it on, you will likely to get black screen. This is expected since dev_flash is still qCFW but you're on OFW now
      6. Enter safe mode and reinstall firmware normally to get full recovery

      Recover from bad Stagex.bin or CoreOS.bin flash
      • No worries, your console isn't really bricked.
      • FIRST, disable the modchip then try to boot the console if it boots then all is good.
      • If it shut itself off, Simply follow Go back to OFW using BANKSEL pin section above. But this time disable modchip before boot as well.

      Downgrading
      • After booting the console with modchip, It is possible to downgrade the firmware up to 4.80. It can't be done in XMB. You must use safe mode.

    • OtherOS
      It is different from CFW. Simply follow these steps.
      1. Download dtbImage.ps3.zfself and put it into root of your USB drive
      2. Plug your USB drive into RIGHTMOST USB port of your ps3
      3. On XMB, use Network -> Custom Firmware Tools -> OtherOS Tools -> Install OtherOS (qCFW) option. It should show Success
      4. Use Boot OtherOS (qCFW) option. It should enter petitboot right away

      Accessing Syscon
      You can't access syscon the old ways anymore. It must be done through modchip. Simply connect DEBUG pin of modchip into your UART adapter.


    • NoBT
      • TODO. It requires LITE pin and hardware flasher for first installation if you are already on update loop.

      eMMC Support?
      In very short summary, What modchip is doing is writing these code into ram at boot:
      Code: 
      stage_entry:
    // Jump to 0x2401F031000, aka 0x31000 on NOR flash where Stagex.bin is stored

    bl 4
    mflr %r3
    addi %r3, %r3, -4
    ld %r4, 24(%r3)
    mtctr %r4
    bctr

    .quad 0x2401F031000

      Do we have something like 0x2401F031000 on eMMC? If answer is yes, then eMMC can be supported (with more porting work).

  • Always view Official Link for latest updates:
    via esc0rtd3w > PS3HEN 3.4.1 has been released!

    If you have Auto Updates turned on, then HEN will automatically update the next time its enabled. If not, use whatever other method of your choosing to update. The ps3xploit.me site has been updated.

    CHANGELOG
    HEN Plugin Changes
    • Added detection of BadWDSD via LV1 peek check on hen enable (thanks aomsin2526)
    Payload Changes
    • Enabled LV1 peek and poke to support BadHTAB and BadWDSD exploits (thanks aomsin2526)
    • Added conditional timer for Retail and NPDRM self to reduce hanging when launching homebrew (thanks Joonie, aomsin2526)
    • Added support for 3k3y/Redump ISOs on-the-fly (thanks Joonie, Evilnat)
    Resource Changes
    • Added support for installing qCFW with xai (quasi-CFW for NOR 3000x and SS) (thanks aomsin2526)
    • Added BD Game Disc Fix (thanks LuanTeles)
    • Now using fork of Evilnats xai plugin as base to take advantage of updated features (thanks Evilnat)

  • qcfw-20260220-release​
    Based on Evilnat 4.92.2 PEX

    qCFW Changelog:
    • Stagex code improvements
    • Implement controller sync workaround. If you turn on the console using controller while on qCFW it will always power cycle once first (.uf2 must be updated)
    • Fix a loophole that can made BANKSEL useless under certain circumstance
    .uf2/Modchip Changelog:
    • Code improvements
    • Better self retry/power cycling
    • Handle controller sync workaround
    • Modchip now runs at stock clock speed (no longer overclocked)

    .uf2 update is optional but RECOMMENDED or controller sync workaround may not work properly.

​
Project Links
 
Last edited:
Click to expand...
D
pstreecco said:
It would be better to fix the BT module if possible, it might just be a 1v8 reg failure (easy replacement with a linear regulator).

If the module can't be fixed you need to follow the NoBT guide at https://www.psx-place.com/threads/badwdsd-qcfw-hw-flasher-nobt-thread.49625/
Click to expand...
I already followed the guide but I'm a little confused because I already installed the rasberry pi pico but I don't know what file I should have on my usb to install if the qcfw or qcfw lite since in the guide there is no file
 
A
I'm making new qcfw test that will allow you to dump HDD key. (not root key).
This key is what really used in encryption process. erk just being used to generate it.

This mean HDD decryption will be possible now.

I'm also planning to add Pico W support too. LED currently not working in that version.
But I don't have one to test so I need tester to try it.
 
pstreecco
aomsin2526 said:
I'm making new qcfw test that will allow you to dump HDD key. (not root key).
This key is what really used in encryption process. erk just being used to generate it.

This mean HDD decryption will be possible now.

I'm also planning to add Pico W support too. LED currently not working in that version.
But I don't have one to test so I need tester to try it.
Click to expand...

Do I need to connect directly to syscon to do w f03 1? I've tried doing it though the debug uart on modchip pin 5 but it doesn't seem to do anything, not even echo back the keystrokes.
I've tried with screen, minicom and ps3_diag_serial.py from the ps3syscon repo.
 
A
pstreecco said:
Do I need to connect directly to syscon to do w f03 1? I've tried doing it though the debug uart on modchip pin 5 but it doesn't seem to do anything, not even echo back the keystrokes.
I've tried with screen, minicom and ps3_diag_serial.py from the ps3syscon repo.
Click to expand...

Do you set baud correctly? it is 576000 (NOT 57600)
You should see modchip log and access syscon this way

You also use normal uart program, not syscon script
 
pstreecco
aomsin2526 said:
Do you set baud correctly? it is 576000 (NOT 57600)
You should see modchip log and access syscon this way

You also use normal uart program, not syscon script
Click to expand...

I could see the output just fine, but nothing I type seems to do anything.
After further testing I can initialize the serial port with GNU screen and then echo to it the whole line (echo "w f03 1" >> /dev/ttyUSB1 while also cat-ing it in another terminal) then it works, but if I type one character at a time through screen/minicom it doesn't, I suspect there could be some issue with line buffering on the modchip.

I managed to get the disk keys and will try populating the dev_flash partition tomorrow, are all the files I need in the qcfw zip or do I need to get some from somewhere else (working console/hfw pup)?
 
A
pstreecco said:
I could see the output just fine, but nothing I type seems to do anything.
After further testing I can initialize the serial port with GNU screen and then echo to it the whole line (echo "w f03 1" >> /dev/ttyUSB1 while also cat-ing it in another terminal) then it works, but if I type one character at a time through screen/minicom it doesn't, I suspect there could be some issue with line buffering on the modchip.

I managed to get the disk keys and will try populating the dev_flash partition tomorrow, are all the files I need in the qcfw zip or do I need to get some from somewhere else (working console/hfw pup)?
Click to expand...

You must end the line with \n

Edit: I guess I will improve it a little.

Whole dev_flash is included in qcfw zip
 
Last edited:
Galooko
A few years ago I got this Super Slim unit with Update loop because someone messed up while installing an ODE to it. The entire line is ripped out of the board to the Southbridge chip… I could recover it with BadWDSD but it has an EMMC Chip so for now it must sit and wait until this is figured out.
IMG_5764.jpeg
IMG_5765.jpeg
 
A
Galooko said:
A few years ago I got this Super Slim unit with Update loop because someone messed up while installing an ODE to it. The entire line is ripped out of the board to the Southbridge chip… I could recover it with BadWDSD but it has an EMMC Chip so for now it must sit and wait until this is figured out.View attachment 47404 View attachment 47405
Click to expand...

NoBD is a bit annoying, you can bypass update loop now for sure but you will likely have issues later on.

Such as black screen during game launch.

qCFW didn't apply nobd lv1 patches yet
 
A
Bonjour @aomsin2526 & @Galooko :

I have a Foxconn KTE-001 card. On the card, I can't make out the CMD and SCK/CLK points. The card doesn't look like the one pictured by @Galooko, especially the CMD and SCK/CLK points. The other points are identical to the photos. Could you please guide me so I can start installing the dongle? Thank you in advance for everything you do.

Je possède une carte KTE-001 de Foxconn. Sur la carte, je ne distingue pas les points CMD et SCK/CLK. La carte ne ressemble pas à celle fournie en photo par @Galooko notamment les points CMD et SCK/CLK. Les autres sont identiques aux photos. Pouvez-vous me guider pour que je commence l'implantation du "dongle" s'il vous plait ? Merci par avance pour tout ce que vous faites.
 
A
Algol said:
Bonjour @aomsin2526 & @Galooko :

I have a Foxconn KTE-001 card. On the card, I can't make out the CMD and SCK/CLK points. The card doesn't look like the one pictured by @Galooko, especially the CMD and SCK/CLK points. The other points are identical to the photos. Could you please guide me so I can start installing the dongle? Thank you in advance for everything you do.

Je possède une carte KTE-001 de Foxconn. Sur la carte, je ne distingue pas les points CMD et SCK/CLK. La carte ne ressemble pas à celle fournie en photo par @Galooko notamment les points CMD et SCK/CLK. Les autres sont identiques aux photos. Pouvez-vous me guider pour que je commence l'implantation du "dongle" s'il vous plait ? Merci par avance pour tout ce que vous faites.
Click to expand...

Show board pics
 
A
These are the ones provided by @Galooko in discussion #173. The image in the bottom right corner doesn't match the back of my KTE-001. Could you please provide an image with the correct locations of the CMD and SCK/CLK points? Many thanks in advance.

Ce sont celles fournies par @Galooko dans la discussion #173. C'est l'image en bas à droite qui ne correspond pas à la face arrière de ma KTE-001. Pouvez-vous me donner une image avec la bonne localisation des points CMD et SCK/CLK. Mille merci par avance.
 
pstreecco
I have succesfully populated dev_flash using PS3HDH (though hex-editing the key by copying the syscon logs was a bit annoying), now my slim boots to XMB with evilnat logo and all (haven't tried running anything else though, I didn't have the cooler screwed in).

The odd part is that it still doesn't let me install updates in safe mode, same 8002f2f0 error as before.

Edit: Checking the southbridge log shows that the console throws the error just after entering safe mode, but it's only displayed after selecting system update. The output looks like so:

Code: 
lv2(2): Available physical SPUs: 6/7
lv2(2): mounting the flash file system : OK
lv2(2):
lv2(2): ###
lv2(2): ### Safe mode
lv2(2): ###
lv2(2):
lv2(2): creating the recover process (for safe mode) : OK
lv2(2): is factory mode ret[f]
lv2(2): ErrorPage[6] Code[-2147290384]

Could it be an RTC issue? I noticed the console always asks for date and time after powering it on, despite having just swapped the RTC battery for a new one.
 
Last edited:
A
@aomsin2526 : A quick question. Is it possible to make the LED on the RP2040-ZERO work instead of soldering an additional diode to the circuit?

In French :
une petite question. Est-il possible de faire fonctionner la LED présente sur le RP2040-ZERO au lieu de souder une diode supplémentaire sur le circuit ?
 
pstreecco
Algol said:
@aomsin2526 : A quick question. Is it possible to make the LED on the RP2040-ZERO work instead of soldering an additional diode to the circuit?

In French :
une petite question. Est-il possible de faire fonctionner la LED présente sur le RP2040-ZERO au lieu de souder une diode supplémentaire sur le circuit ?
Click to expand...

You need to flash the RP2040-Zero specific firmware, not the Pi Pico one
 
You must log in or register to reply here.

Similar threads

Featured content

Trending content

Latest posts

Back
Top