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...
A
MannyMania said:
Hey @pstreecco Thanks for the help. It was a short on the SC_RX and SC_TX. I cleaned that up and now when I Plug in the power to the console the Pico blue light flashes once and stays on. When the console is powered on you hear the PS3 beep, and the blue light flashes three times and goes back to steady on. There is no video and a few seconds later the console reboots. It then keeps repeating that cycle. If I disconnect the Pico the console powers on fine and goes to the XMB.

Did that short possibly damage something or am I missing something else?
Click to expand...

Check if stagex is installed and CMD/CLK is soldered correctly.
 
M
pstreecco said:
If it does the triple beep it means the modchip worked and the console is executing stagex, check the modchip's debug log and/or the southbridge log to see if you can find the reason for the reboot.
Click to expand...

I'm only getting one beep, not the three beeps.

aomsin2526 said:
Check if stagex is installed and CMD/CLK is soldered correctly.
Click to expand...

Thanks for the info :encouragement: I did some continuity tests on the CMD/CLK lines and they're good. The fail was at the connector I used for the CMD/CLK line to the Pico. ARGHHH!!! I Rechecked everything and now it finally powers up with the three beeps.
IMG_5796.jpeg

Now to continue with the next steps!!

Thanks All for the Help.

A huge thank you the Devs that make this stuff happen!!! :applause:

Thanks all for the help it's done!! I know someone with a 3D printer so I was able to do a nice install using the vertical stand hole as a mount. If you don't keep the wires to the Pico separated it also causes the console to beep once and keep rebooting.

Here's how it looks.
IMG_5802.jpeg IMG_5803.jpeg IMG_5826.jpeg IMG_5833.jpeg IMG_5834.jpeg

I anyone is interested I can share the stl files.

IMG_5828.jpeg IMG_5829.jpeg
IMG_5800.jpeg IMG_5799.jpeg

Cheers!!
 
Last edited by a moderator:
S
MannyMania said:
A huge thank you the Devs that make this stuff happen!!! :applause:

Thanks all for the help it's done!! I know someone with a 3D printer so I was able to do a nice install using the vertical stand hole as a mount. If you don't keep the wires to the Pico separated it also causes the console to beep once and keep rebooting.

Here's how it looks.
View attachment 47423 View attachment 47424 View attachment 47425 View attachment 47421 View attachment 47422

I anyone is interested I can share the stl files.

View attachment 47426 View attachment 47429
View attachment 47431 View attachment 47430

Cheers!!
Click to expand...

can you share the stl files sir?
 
ajthenoob
4301C here. I think I got it soldered right (SC_TX to SC_TX in image, not sure if I should reverse) and measured resistance for CMD and CLK - Pico powers on and solid light, flashes quick when powered on, but PS3 keeps bootlooping (green to red, single beep). Every boot the Pico will flash 3 times and then become solid. I can get into regular XMB by powering on super quickly after plugging it in. Any idea why this may be?

Also using latest HEN 3.4.3 (Latest_HEN_Installer_3.4.3_test2_signed-492C.pkg) and latest QFW (qcfw-20260228-release)
 
Last edited:
A
ajthenoob said:
4301C here. I think I got it soldered right (SC_TX to SC_TX in image, not sure if I should reverse) and measured resistance for CMD and CLK - Pico powers on and solid light, flashes quick when powered on, but PS3 keeps bootlooping (green to red, single beep). Every boot the Pico will flash 3 times and then become solid. I can get into regular XMB by powering on super quickly after plugging it in. Any idea why this may be?

Also using latest HEN 3.4.3 (Latest_HEN_Installer_3.4.3_test2_signed-492C.pkg) and latest QFW (qcfw-20260228-release)
Click to expand...

Did you install stagex yet?

Bootloop will caused by bad or no stagex installed. Or CMD/CLK wire is bad.
Check if CMD/CLK is soldered to correct pico pin.

Since your console still work without modchip, CMD/CLK resistor isn't damaged. But wire may be wrong.
 
ajthenoob
Thank you for responding! Stagex shows success. I then power down, unplug and replug waiting for the solid light. I double checked my CMD/CLK. If the wires are somewhat long (around 2ft) maybe that could be the issue? I also route them all out together. Even though my resistances are 55Ohm on both, maybe i will try shortening the wires.
 
A
ajthenoob said:
Thank you for responding! Stagex shows success. I then power down, unplug and replug waiting for the solid light. I double checked my CMD/CLK. If the wires are somewhat long (around 2ft) maybe that could be the issue? I also route them all out together. Even though my resistances are 55Ohm on both, maybe i will try shortening the wires.
Click to expand...

That's very long. It will surely cause a problem. Shorten all wire as much as you can.

Ground is the most important one
 
ajthenoob
Lesson learned! Shortening and re-routing away from motherboard and other wires worked. Thanks so much for your help. The default HEN in xploit also works fine with latest QFW release.

Edit: I can also confirm that BANKSEL works. I just had an issue where I was in-game (GT6) and it black-screened when quitting. I then couldn't enter back into CFW (it would boot after multiple attempts, and freeze at the "Please Wait" screen). Was able to reinstall HFW from recovery.
 
Last edited:
A
ajthenoob said:
Lesson learned! Shortening and re-routing away from motherboard and other wires worked. Thanks so much for your help. The default HEN in xploit also works fine with latest QFW release.

Edit: I can also confirm that BANKSEL works. I just had an issue where I was in-game (GT6) and it black-screened when quitting. I then couldn't enter back into CFW (it would boot after multiple attempts, and freeze at the "Please Wait" screen). Was able to reinstall HFW from recovery.
Click to expand...

This often happen when filesystem is corrupted. Check file system first. If still happening then you must format it.
 
ajthenoob
Thank you so much for all your help! I did the following wiring and finally my GND was stable for multiple boots.
The 43XX is an absolute tank. I got it up to ~1000~ *900 on the GPU and temps are under 65 the whole time. What a mod - never thought it would be possible for any sort of CFW in the super slims.
 

Attachments

  • Screenshot_20260312_210006.png
    Screenshot_20260312_210006.png
    1.3 MB · Views: 89
Last edited:
CatMachete
ajthenoob said:
Thank you so much for all your help! I did the following wiring and finally my GND was stable for multiple boots.
The 43XX is an absolute tank. I got it up to 1000 on the GPU and temps are under 65 the whole time. What a mod - never thought it would be possible for any sort of CFW in the super slims.
Click to expand...
What voltage are you using? I'm at 1.2v on a 42xx and it's crashing at 800 :(

edit: I did some further testing. My final settings are 800/700 at .95v. Going over 1v doesn't seem to help with stability, and the memory artifacts instantly at 750

I did find a clean way to route the wires, but it had to put some holes in the case.
QwDodd2.jpeg
 
Last edited:
Z
Hello! Need help.
Setup used:
PS3 4308C (4.92.1 HFW)
RP2040 16Mb (YD-RP2040) BadWDSD_SW_x32_20250529.uf2 (RP2040 with other firmwares does not connect to the syscon at all.)
qCFW qcfw-20260220-release-2 (qcfw-20260228-release)
The RP2040 connects to the syscon almost instantly, 3 beeps are heard on startup, video output works, qCFW loads.
I can restart it as many times as I want using Soft Reboot, or turn it off using the standard menu option. The PS3 will boot.
As soon as a Full Reboot or a shutdown via the standard menu option + unplugging the power cord is performed, I get this:
The RP2040 connects to the syscon, 3 beeps are heard on startup, but there is no video output (black screen), and it's impossible to enter Recovery Mode.
There is only one solution - formatting the HDD. The whole procedure can be repeated any number of times.
I have swapped the HDD for another one, and also swapped it for an SSD. The result is the same.
 
M
CatMachete said:
What voltage are you using? I'm at 1.2v on a 42xx and it's crashing at 800 :(

edit: I did some further testing. My final settings are 800/700 at .95v. Going over 1v doesn't seem to help with stability, and the memory artifacts instantly at 750

I did find a clean way to route the wires, but it had to put some holes in the case.
QwDodd2.jpeg
Click to expand...

I passed the wires by the network adapter. I forgot to take a picture. Here's how I ran them. I used wire wrap as it's very small.

IMG_5791.jpeg IMG_5795.jpeg
 
SyrianClippy
pstreecco said:
Because you'd want to write to eMMC from the modchip or use it as a trigger of sorts? Yea

Looking at the wiki eMMC boards have some kind of NOR-eMMC adapter chip, could they actually be treated like a NOR board? Or at least read like a NOR (memory mapped through southbridge) if the panasonic chip doesn't support writing.

It would be somewhat riskier because you can't just pull the HDD and wipe it, but if recovering is needed a 3DS-like hardware flasher setup (sd card adapter) is much simpler than what is needed on NOR.
Click to expand...
I believe the main reason is still the unknown MMIO interface on those, without a way to decrypt a eMMC dump knowing that is near impossible
 
ajthenoob
CatMachete said:
What voltage are you using? I'm at 1.2v on a 42xx and it's crashing at 800 :(

edit: I did some further testing. My final settings are 800/700 at .95v. Going over 1v doesn't seem to help with stability, and the memory artifacts instantly at 750

I did find a clean way to route the wires, but it had to put some holes in the case.
QwDodd2.jpeg
Click to expand...
Correction - I can only get 900/725 stable. That frequency actually did not apply for some reason. Looking into overvolting but first I need to figure out syscon, my putty terminal is not working.
 
M
Hey @aomsin2526. There is a small bug with the 4.92 CFW where the PS1 and PS2 options for screen smoothing and stretching are not being saved. It also effects the choice of Analog vs Digital controller as well. I noticed it in the qCFW first and then tested on a Fat PS3 to confirm it. I'm hoping that if/when a 4.93 CFW gets released that it will be fixed. Would you reconsider making a new qCFW if those problems do get fixed in the next CFW release?

Cheers!!
 
You must log in or register to reply here.

Similar threads

Featured content

Trending content

Latest posts

Back
Top