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...
Cosmic-R
stupid people will be stupid people, the instructions clearly said there could be a brick risk just like there is one in the cfw installation

people love to do a surprised pikachu face when the warning thats on big red bold letters happens then they complain

please dont be discouraged, tell them to F#$%& off and you keep doing what youre doing

they cant say they werent warned, is it unstable ?! probably, is there things to improve ?! sure, just like everything else.

but isnt pretty much any modded console (hardware or software) less stable than stock ? it just comes with the territory

maybe take a few days to cool off, people online love being toxic and point fingers at someone else instead of looking at a mirror
 
D
aomsin2526 said:
Yes, I will made a new thread about this later.

It seems since public release this mod get a lot of hate from many places.

Which is very demotivating. I'm not sure why I'm doing this anymore.

You can get your E3 setup ready first.
Click to expand...
Ignore them, those people are morons who completely ignored that you were quite clear this project was still in the beta/testing phase. They're also happily ignoring that CFW on any of these models would have been completely impossible without your work.
 
H
hello @aomsin2526 ,
I have insufficient privileges to reply under 'BadWDSD/qCFW + HW Flasher/NoBT' Thread, So I send it here to share my lesson learned,you can re-post this under your post.
I finally succeeded, and without using a hardware flasher. As mentioned before, although I successfully installed qCFW, it would black screen on every boot. Last night, I tried a new method provided by aomsin2526 : shorting the LITE pin to ground and copying the stage2.cex file to a USB drive. This time the screen showed a response, but it was garbled (artifacting).
After repeated attempts, I discovered I could enter Recovery Mode normally. Once in Recovery Mode, I chose 'System Update' and copied the 4.92 update file to the USB drive. After checking the update file, the PS3 rebooted into the pre-update interface; the buzzer beeped several times (I lost count, but it was a lot), and then the update started. This time, it succeeded without the F1F9 error.
I proceeded to install HEN, StageX, and qCFW under version 4.92. Everything went smoothly without any error prompts, but it still black-screened after rebooting. I kept trying and re-updating countless times... Finally, I decided to try a different hard drive. After swapping the HDD, shorting the LITE pin, and installing OFW, HEN, StageX, and qCFW, it still black-screened upon reboot, though there was some artifacting this time.
I continued to experiment, and by chance, I booted the console without the USB drive plugged in—and it entered the system! It booted into qCFW, and everything was working perfectly. I suddenly realized that I had left an overclock.txt file from another machine on the USB drive, which triggered an automatic overclock. This specific machine couldn't handle those high frequencies, which caused the black screen.
This is a Hard-learned lesson, and many thank to you @aomsin2526 !
 
A
Few days passed since first qCFW release, How it's going now? Please report.

The only reason I removed the files because of "bricking" reports. However, this only came from one specific group of people and never elsewhere.

I'm unable to replicate it too.

What I hear from people so far from many places is that once you get qCFW working, it is very smooth.

I don't count damaged console from failed soldering or disassembly. It is skill issue and not modchip fault.
 
Y
Agreed to the "moron's" thing, when u put yourself at risk you've got to assume consequences...

Some news about testing qCFW on my PS3's, so far so good :

3004B is working well 2504A is ok. Got another 2504A qCFW went unstable, manage to dump syscon errors: 1701-14FF then 3034, 4421, 4423...RSX is diying, when temperature go over 60° it shuts down, very lucky it goes trough to qCFW install.
I think many "haters" critizising aomsin are the one who got diying PS3/can't read instructions, blaming qCFW.

Got 2 superslim one NPX-001 with artifacts problems : gonna qCFW it , aomsin if she dies you'll be the only one responsible !! xD
Got an EEMC one too, if help needed to test things on it...

Besides that i encounter some bugs on the 2 one's working on qCFW:

some "PSN" pkgs are installing, launching but got a blackscreen then a reboot of the PS3, tested this pkg on My fat CFW one (exact same pkg installing from usb) and i can launch it and it works.
Am i doing something wrong ? don't think so : there is not so many ways to install a pkg on ps3.

Did someone already encounters these kind of behavior ?
 
M
aomsin2526 said:
Few days passed since first qCFW release, How it's going now? Please report.

The only reason I removed the files because of "bricking" reports. However, this only came from one specific group of people and never elsewhere.

I'm unable to replicate it too.

What I hear from people so far from many places is that once you get qCFW working, it is very smooth.

I don't count damaged console from failed soldering or disassembly. It is skill issue and not modchip fault.
Click to expand...
well my cech 3001a works amazing
 
A
Yoplay said:
Agreed to the "moron's" thing, when u put yourself at risk you've got to assume consequences...

Some news about testing qCFW on my PS3's, so far so good :

3004B is working well 2504A is ok. Got another 2504A qCFW went unstable, manage to dump syscon errors: 1701-14FF then 3034, 4421, 4423...RSX is diying, when temperature go over 60° it shuts down, very lucky it goes trough to qCFW install.
I think many "haters" critizising aomsin are the one who got diying PS3/can't read instructions, blaming qCFW.

Got 2 superslim one NPX-001 with artifacts problems : gonna qCFW it , aomsin if she dies you'll be the only one responsible !! xD
Got an EEMC one too, if help needed to test things on it...

Besides that i encounter some bugs on the 2 one's working on qCFW:

some "PSN" pkgs are installing, launching but got a blackscreen then a reboot of the PS3, tested this pkg on My fat CFW one (exact same pkg installing from usb) and i can launch it and it works.
Am i doing something wrong ? don't think so : there is not so many ways to install a pkg on ps3.

Did someone already encounters these kind of behavior ?
Click to expand...

Please give me that "PSN" pkg to test.
Are you sure that HDD isn't dying?
 
Y
aomsin2526 said:
Please give me that "PSN" pkg to test.
Are you sure that HDD isn't dying?
Click to expand...
Pretty sure , on 2504 it's a HDD but on 3004 it's a brand New 1Tb SSD ....and it works on ps3 fat cfw.

But not exact same behavior on 2504 fatal crash with reboot, on 3004 (SSD one) black screen...have to "hard reset" console.

But both are rebooting without problems.

Don't know how to send u the pkg...it's a big one (4Go).

Tell me ( got it with pkgi)
 
A
I successfully installed the rp2040 zero on the 4000 SS. But there's one odd thing.
When I turn on the console, it beeps three times, then reboots itself, then beeps three more times, and the console turns on and functions normally.
 
A
ave_187 said:
I successfully installed the rp2040 zero on the 4000 SS. But there's one odd thing.
When I turn on the console, it beeps three times, then reboots itself, then beeps three more times, and the console turns on and functions normally.
Click to expand...

What qcfw version you use? The latest test one (20260214) have new controller sync workaround implemented. If you turn on the console using controller it will always reboot once first. But controller sync will work.
 
D
aomsin2526 said:
Few days passed, it seems there is no "critical bug" after all.

If no problem found again I will do proper release in few days.

It will be same file as qcfw-20260214-test
Click to expand...

I have a question I am new installing rasberry pi pico to ps3 and I know what points to connect but my ps3 slim cech 3011a has bluetooth wifi module problem and I know that first I have to flash the rasberry and then install but then I have to install the normal 4.92 update with a usb and so it would pass the bluetooth block or I have to do something else
 
A
A
Dexfox4 said:
I already saw the post but I'm bad at programming and at the same time if I damage my console I don't have a backup because the hard drive I had is no longer useful and I bought another 120gb and I don't know how to make a backup of my console Any tips to avoid damaging my console without backup
Click to expand...

Better repair bt module first

Previously only option is to repair, today you have modchip as second option.

If you can't do modchip, then repair is only way.
 
A
@aomsin2526 I know it is not the best time to ask about this but I thought mine is NOR flash before I got surprized when I knew it is EMMC, Anyway, is there any hope that qCFW ( or somethig alike ) will be working on the EMMC flash models ? even if it's in the distant future. Big thanks for what you are doing for us
 
D
aomsin2526 said:
Better repair bt module first

Previously only option is to repair, today you have modchip as second option.

If you can't do modchip, then repair is only way.
Click to expand...

IIf you're right but the modchip is more accessible to me and that's why I'm looking for a tutorial or something like that to revive my ps3 slim and install the modchip and that everything goes well on the first try without blocking the conslIf you're right but the modchip is more accessible to me and that's why I'm looking for a tutorial or something like that to revive my ps3 slim and install the modchip and that everything goes well on the first try without blocking the console
 
You must log in or register to reply here.

Similar threads

Featured content

Trending content

Latest posts

Back
Top