UPDATE 04-02-2020
These tools have been superseded by the BG Toolset
** www.** ** www.ps3xploit.net > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com) > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com)/bgtoolset/











UPDATE (OCT. 11 2018) - With the release of OFW 4.83 portions of PS3Xploit have been patched, The team is looking at workarounds, STAY ON 4.82, DO NOT UPDATE TO 4.83 AT THIS TIME:
IMPORTANT UPDATE (MARCH-2019) v3.0.1 was released providing support for 4.84 HFW (a new hybrid firmware that restores PS3Xploit for 4.84 OFW user's (See Link to HFW)
dI will start this off with NO you can not jailbreak your PS3 SuperSlim Console's (seems to be a popular question), however that does not mean the Ps3Xploit Team, (bguerville, esc0rtd3w, habib & W), has not been hard at work, with this new release of Ps3Xploit v2.0.. In this release all the tools (IDPS Dumper, Flash Dumper & Flash Writer) have seen significant improvements and now performing the task such as installing a Custom Firmware on your 4.82 OFW PS3 (with flash writer) has been made even easier and very stable thanks to the team's new checks implemented and progression of the exploit. The Flash and IDPS dumper are also much improved. All the details are provided below please read all the spoiler and tabs before asking any questions.
-STLcardsWS​

PS3Xploit_Tools_v2.jpg


PS3Xploit 2.0 Tools Now LIVE!!

  • Included Tools
    • 4.XX IDPS DUMPER
    • 4.XX FLASH DUMPER (USB Edition)
    • 4.XX FLASH DUMPER (HDD Edition)
    • 4.82 NOR/NAND WRITER (USB Edition)
    • 4.82 NOR/NAND WRITER (HDD Edition)
    Ps3Xploit Tools Changelogs
    v2.0
    • Freeze issues - Fixed
    • Occasional bad dumps - Fixed
    • No beeps & shutdown. Replaced by a graceful ROP chain exit & return to browser. This gives the opportunity to the user to dump after patching & validate the dump with littlebalup's py checker. As long as the user does not shutdown/restart, it's still possible to recover from bad patching.
    • Support for usb port 0,1,6 + sd/cf/ms cards.
    • Multi firmware support on all dumpers (4.10+) & DEX support on 4.81.
    • HDD editions for all dumpers & flash writer where a picture file placeholder is used for read/write operations.
    • Javascript refactoring for performance & efficiency.
    • **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) will host the 2.0 update, no need for 3rd party sites.

    v1.0 (Thanksgiving 2017 Release)
    • Supports Direct OFW to CFW patching for All Phat and 2xxx Slim (minver 3.56 Dec 2010 and lower)
    • the NOR/NAND writer will just copy 3Mb of CoreOS data to both ros0 & ros1 in the flash memory.
    • There is only one version released for 4.82. The same hex patch file can be used on nor & nand.
    • It's as safe as possible, with a check for usb device & patch file making the exploit hang instead of corrupting flash if file is not found.
    • In case of corruption (extremely rare but could always happen), it's only a partial brick because no per console info ever gets erased so a hardware flasher could still be used if ever a recovery reboot was impossible



  • Frequency Asked Questions

    Will this jailbreak my SuperSlim?
    • NO,The Flasher Writer Tool is not Supported on the SuperSlim and a some very late Slim models, Howeever, PS3Xploit has a strong possiablity to eventually evolve into a HEN style exploit (that aspect will take some additional development.)

    Which PS3Xploits Tools are Compatible with my PS3 Console?



    • 9199-7853467153566ba1908c9b32aa331bb5.jpg.png
      Check this sticker on the back of your PS3 to view your PS3 Model.
      Flash Writer Model Compatibility (PHAT):
      • CECH-A01 (NAND)
      • B (NAND)
      • C (NAND)
      • E (NAND)
      • G (NAND)
      • H (NOR)
      • J (NOR)
      • K (NOR)
      • L (NOR)
      • M (NOR)
      • P (NOR)
      • Q (NOR)

      All DUMPER (FLASH/IDPS) & FLASH WRITER TOOLS are Supported for this model.


    • 9200-4361b3a6a7359ffe524f966d4eeca4bc.jpg.png
      Check this sticker on the back of your PS3 to view your PS3 Model.

      ***IMPORTANT***
      You must pay very close attention to your PS3 SLIM Models depending on when the PS3 SLIM was manufactured will determine if your console can install CFW (Flasher Writer Compatibility).

      For the 25XX series or even if your unsure about any of the models it is reccomnded you run the minverchk PUP >> (DOWNLOAD) & (How to use Minverchk) its a simply utility that show the factory installed firmware on your ps3 and for the CECH-25XX model if the utility shows 3.56 or lower you are compatible but if it shows 3.60 and higher that means your are NOT compatible to use the Flash Writer (CFW enabler for 4.82 CFW)

      • Flash Writer Model Compatibility (SLIM):
        • 20XX NOR
        • 21XX NOR
        • 25XX NOR (3.56 minver. and Lower)
      • NOT COMPATIBLE (SLIM):
        • 25XX NOR (3.60 and Higher)
        • 3XXX NOR


      All DUMPER (FLASH/IDPS) TOOLS are Supported for this model.



    • 9203-5ab5229a0530b0274c59419c8b4f8987.jpg
      Check this sticker on the back of your PS3 to view your PS3 Model.
      • FLASH WRITER NOT COMPATIBLE (SUPERSLIM):
        • 4XXXA EMMC
        • 4XXXB NOR
        • 4XXXC NOR
      All DUMPER (FLASH/IDPS) TOOLS are Supported for this model.


    Where can i find official info and details?
    • Official Website (Exploit Hosting / Info) @ ** http://www.**ps3xploit.com >Doma...no Longer owned by team** (ps3xploit.me =new)
    • Official Ps3Xploit Forum (Support/News/Info): @ http://www.psx-place.com/forums/PS3Xploit/
    Warning: Known Limitation
    • Due to the lack of proper checks after exiting the ROP chain, it is possible in some cases to obtain a success message despite an operation failure. For instance, if you choose a path where no device is plugged in, a dumper page will still display a success message despite the fact the dump save could not work. This limitation has already been addressed, the added operation checks will be part of an update to these PS3Xploit tools which will be released in the coming weeks, that update will be final, no more will come after it


  • FLASH Dumper's Help


    • PS3 4.xx NAND/NOR/EMMC FLASH DUMPER v2.0
      All PS3 models supported
      All 4.10+ CEX CFW/OFW supported
      4.81 DEX CFW/OFW supported


      IMPORTANT NOTES:
      • It's essential not to flood the browser memory with junk before running the exploit. The reason for this is that due to javascript core memory usage limitations we are scanning several times a small range of browser memory (a few Mb) to find some essential data in RAM, if the memory is flooded then the range to scan becomes much larger & the probabilities that our data is found in the smaller range decrease dramatically....
      • So in short, never use the browser or use a homepage you cancel before running the exploit!
      • It is recommended to set your homepage temporarily to the exploit page you wish to use to ensure there is no memory flooding messing with the exploit initialization stage.
      Steps:
      1. Open the browser & browse to the **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) website, go to the page of the exploit you need. Set the current page as browser homepage. Don't launch the exploit initialization. Close the browser.
      2. Open the browser. The exploit page will load automatically. Choose your dump path option.
      3. Press the exploit initialization button & wait until initialization succeeds. If it fails, follow the refresh/reload instructions on screen.
      4. Trigger the exploit by pressing the dump button.
      5. On success, validate your dump with the py checker tool.

    • PS3 4.xx NAND/NOR/EMMC FLASH DUMPER - HDD EDITION v2.0

      All PS3 models supported
      All 4.10+ CEX CFW/OFW supported
      4.81 DEX CFW/OFW supported


      IMPORTANT NOTES:
      • It's essential not to flood the browser memory with junk before running the exploit. The reason for this is that due to javascript core memory usage limitations we are scanning several times a small range of browser memory (a few Mb) to find some essential data in RAM, if the memory is flooded then the range to scan becomes much larger & the probabilities that our data is found in the smaller range decrease dramatically....
      • So in short, never use the browser or use a homepage you cancel before running the exploit!
      • It is recommended to set your homepage temporarily to the exploit page you wish to use to ensure there is no memory flooding messing with the exploit initialization stage.
      Steps:
      1. Open the browser & browse to the **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) website, go to the page of the exploit you need. Set the current page as browser homepage. Don't launch the exploit initialization. Close the browser.
      2. Open the browser. The exploit page will load automatically. Download the dump.jpg placeholder file to your PS3 System Storage using the provided link as instructed on screen.
      3. Press the exploit initialization button & wait until initialization succeeds. If it fails, follow the refresh/reload instructions on screen.
      4. Trigger the exploit by pressing the dump button.
      5. On success, retrieve the dump file from the PS3 XMB Photo section, rename it appropriately to dump.hex or whatever & validate your dump with the py checker tool.


    Usage Tips:
    • Try using a LAN connection or a solid WiFi connection during exploitation. A weak signal can cause problems.
    • If the exploit takes more than 5 minutes to work, reload page, browser, or restart console and try again.
    • ]If you are using a LAN connection and experience network issues, make sure all cables to router are in working order.




    • PS3 OFW 4.82 NAND/NOR FLASH WRITER v2.0
      ***** IMPORTANT DETAILS BELOW -- AVOIDING A BRICK *****
      WARNING: USE ONLY THE PROVIDED flash_482.hex AS IS. DON'T PATCH IT OR MODIFY IT OR YOU WILL BRICK *****
      • Verify flash_482.hex file on a flash drive and in the selected USB slot!
        • flash_482.hex MD5: d05be52f8d21700052fbd1fc0174acae
      • DO NOT USE ON CFW (Custom Firmware) (Only Supports OFW)
      • DO NOT USE ON PS3 Models 3xxx/4xxx (aka late Slim or Superslim models), you would brick those consoles.
      • ON SLIM 2xxx Consoles, always use MinVerChck PUP to ensure that the minimum installable firmware version is < 3.60, if ever the minimum version is >3.56, using the flash writer would partially brick your console!
      • USE ONLY ON 4.82 OFW

      IMPORTANT NOTES:
      • It's essential not to flood the browser memory with junk before running the exploit. The reason for this is that due to ps3 javascript core memory usage limitations we are scanning several times a small range of browser memory (a few Mb) to find some essential data in RAM, if the memory is flooded due to previous browsing then the range to scan becomes much larger & the probabilities that our data is found in the smaller range decrease dramatically..
      • So in short, never use the browser or use a homepage you cancel before running the exploit!
      • It is recommended to set your homepage temporarily to the exploit page you wish to use to ensure there is no memory flooding messing with the exploit initialization stage.

      Steps:
      For best results with flash writer, here are the recommended steps.
      1. Install OFW 4.82 twice on the console you wish to flash to avoid the potential corruption error during CFW installation.
      2. Open the browser & browse to the **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) website, go to the page of the exploit you need. Set the current page as browser homepage. Don't launch the exploit initialization. Close the browser.
      3. Open the browser. The exploit page will load automatically. Choose your path option.
      4. Press the exploit initialization button & wait until initialization succeeds. If it fails, follow the refresh/reload instructions on screen.
      5. Trigger the exploit by pressing the patch button.
      6. On success, load the **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) flash dumper, dump the flash memory & validate it with py checker tool. Do NOT restart the console if ever the validation tool gives you errors/warnings on both ros0 & ros1 or you risk to partially brick your console. Report your problem instead.
      7. When you are satisfied with the dump validation, restart your console & install a 4.82 CFW.


    • PS3 OFW 4.82 NAND/NOR FLASH WRITER - HDD EDITION v2.0
      ***** IMPORTANT DETAILS BELOW -- AVOIDING A BRICK *****
      WARNING: USE ONLY THE PROVIDED flash_482.jpg AS IS. DON'T PATCH IT OR MODIFY IT OR WILL BRICK *****
      • YOU
      • Download flash_482.jpg file to PS3 System Storage!
        • flash_482.jpg MD5: d05be52f8d21700052fbd1fc0174acae
      • DO NOT USE ON CFW (Custom Firmware) (Only Supports OFW)
      • DO NOT USE ON PS3 Models 3xxx/4xxx (aka SuperSlims / Late Slim models), you would brick those consoles.
      • ON SLIM 2xxx Consoles, always use MinVerChck PUP to ensure that the minimum installable firmware version is < 3.60, if ever the minimum version is >3.56, using the flash writer would partially brick your console!
      • USE ONLY ON 4.82 OFW

      IMPORTANT NOTES:
      • It's essential not to flood the browser memory with junk before running the exploit. The reason for this is that due to ps3 javascript core memory usage limitations we are scanning several times a small range of browser memory (a few Mb) to find some essential data in RAM, if the memory is flooded due to previous browsing then the range to scan becomes much larger & the probabilities that our data is found in the smaller range decrease dramatically..
      • So in short, never use the browser or use a homepage you cancel before running the exploit!
      • It is recommended to set your homepage temporarily to the exploit page you wish to use to ensure there is no memory flooding messing with the exploit initialization stage.
      Steps:
      For best results with flash writer, here are the recommended steps.
      1. Install OFW 4.82 twice on the console you wish to flash to avoid the potential corruption error during CFW installation.
      2. Open the browser & browse to the **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) website, go to the page of the exploit you need. Set the current page as browser homepage. Don't launch the exploit initialization. Close the browser.
      3. Open the browser. The exploit page will load automatically. Download the patch file flash_482.jpg to your PS3 System Storage using the provided link on screen.
      4. Press the exploit initialization button & wait until initialization succeeds. If it fails, follow the refresh/reload instructions on screen.
      5. Trigger the exploit by pressing the patch button.
      6. On success, load the **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) flash dumper, dump the flash memory & validate it with py checker tool. Do NOT restart the console if ever the validation tool gives you errors/warnings on both ros0 & ros1 or you risk to partially brick your console. Report your problem instead.
      7. When you are satisfied with the dump validation, restart your console & install a 4.82 CFW.

    Usage Tips:
    • Try using a LAN connection or a solid WiFi connection during exploitation. A weak signal can cause problems.
    • If the exploit takes more than 5 minutes to work, reload page, browser, or restart console and try again.
    • ]If you are using a LAN connection and experience network issues, make sure all cables to router are in working order.

  • PS3 4.xx IDPS DUMPER v2.0

    All PS3 models supported
    All 4.10+ CEX CFW/OFW supported
    4.81 DEX CFW/OFW supported

    IMPORTANT NOTES:
    • It's essential not to flood the browser memory with junk before running the exploit. The reason for this is that due to javascript core memory usage limitations we are scanning several times a small range of browser memory (a few Mb) to find some essential data in RAM, if the memory is flooded then the range to scan becomes much larger & the probabilities that our data is found in the smaller range decrease dramatically....
    • So in short, never use the browser or use a homepage you cancel before running the exploit!
    • It is recommended to set your homepage temporarily to the exploit page you wish to use to ensure there is no memory flooding messing with the exploit initialization stage.
    Steps:
    1. Open the browser & browse to the **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) website, go to the page of the exploit you need. Set the current page as browser homepage. Don't launch the exploit initialization. Close the browser.
    2. Open the browser. The exploit page will load automatically. Choose your dump path option.
    3. Press the exploit initialization button & wait until initialization succeeds. If it fails, follow the refresh/reload instructions on screen.
    4. Trigger the exploit by pressing the dump button.
    5. On success, check your idps dump with an hex editor.

Source Code & Downloads:
NOR/NAND/EMMC/IDPS 4.xx Dumpers v2.0 Update
NOR/NAND 4.82 Flash Writer v2.0 Update
flash_482.hex (already included in the Flash Writer 2.0 archive) MD5: d05be52f8d21700052fbd1fc0174acae
MinVerChck PUP


IMPORTANT UPDATE (MARCH-2019) v3.0.1 was released providing support for 4.84 HFW (a new hybrid firmware that restores PS3Xploit for 4.84 OFW user's (See Link to HFW)

Exploits now hosted @ **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new)
Official Support Forum: psx-place.com/forums/PS3Xploit/
 
Last edited:
Having a problem here with a CECHG01/NAND console, writer exploit INITIALIZES right away, PATCHING takes a few seconds to load then progresses to 10% then completes. the DUMPING of the NAND INITIALIZES fine again but DUMPING takes the full 15-25 mins and does not automatically reboot. Neither PyChecker or DumpStatistic will read the dump.hex. Rebug installs fine but am NOT able to install any other .pkg's other then the Rebug toolbox installer that is pre-loaded to the CFW. When booting Rebug toolbox system freezes. Any help would be appreciated, thanks.
A few seconds for patching & over 15mn for NAND dumping is about right on USB. Next time, you dump the nand, choose the hdd version, it's much faster.
Pyps3checker should work perfectly well unless you installed the wrong python version or the dump isn't good, no idea what problem you may have had. Dumpstatistic isn't part of our instructions, I haven't tested it with ps3xploit nand dumps & I don't know if it supports it.
Anyway none of this matters anymore now that you successfully installed Rebug CFW (despite our instructions that told you to wait until you had a validated dump, you took the risk to partially brick your console!).

Anyway, you are using a CFW now so your problems are no longer related with the ps3xploit tools.
Please post in an appropriate thread related to Rebug 4.8x or create your own thread.
 
Last edited:
A few seconds for patching & over 15mn for NAND dumping is about right on USB. Next time, you dump the nand, choose the hdd version, it's much faster.
Pyps3checker should work perfectly well unless you installed the wrong python version or the dump isn't good, no idea what problem you may have had. Dumpstatistic isn't part of our instructions, I haven't tested it with ps3xploit nand dumps & I don't know if it supports it.
Anyway none of this matters anymore now that you successfully installed Rebug CFW (despite our instructions that told you to wait until you had a validated dump, you took the risk to partially brick your console!).

Anyway, you are using a CFW now so your problems are no longer related with the ps3xploit tools.
Please post in an appropriate thread related to Rebug 4.8x or create your own thread.

Thanks bguerville, I had no doubts the exploit worked. Dumpstatistic worked great for 4.82 NOR systems. I think my Python install is a version behind the most recent so I will update and dump again from HDD. My other NAND consoles patched just fine and is the first time I've seen this happen to a CFW. I'll see what the Rebug pros have to say. Thanks again!
 
  • Multi firmware support on all dumpers (4.10+) & DEX support on 4.81.

Does this still apply? If i understand once Rebug 4.82.2 D/REX came out that we now have DEX with 4.82 also.
Please correct me if I am wrong.
I have a slim 2501a, manufacture date of August 2010 on OFW 4.81
I want to use this amazing ps3xploit v2 to then install Rebug 4.82.2 D/REX and use toolbox to toggle the lv2 to DEX
Do i start with D/REX or do i start with Rex and then update to D/REX?
I apologize if this has been answered already. I have read so many forum posts and haven't noticed this being discussed fully.
 
Does this still apply? If i understand once Rebug 4.82.2 D/REX came out that we now have DEX with 4.82 also.
Please correct me if I am wrong.
I have a slim 2501a, manufacture date of August 2010 on OFW 4.81
I want to use this amazing ps3xploit v2 to then install Rebug 4.82.2 D/REX and use toolbox to toggle the lv2 to DEX
Do i start with D/REX or do i start with Rex and then update to D/REX?
I apologize if this has been answered already. I have read so many forum posts and haven't noticed this being discussed fully.
just update to 4.82 OFW and follow instructions for NOR Writer, then yes, after backup (dump), writing, backup (for safety check). reboot and install Rebug 4.82.2 if you like

you can double-check your minimum downgrade version with minvercheck PUP (3.56 and lower compatible), but December 2010 and lower should all be fine
 
just update to 4.82 OFW and follow instructions for NOR Writer, then yes, after backup (dump), writing, backup (for safety check). reboot and install Rebug 4.82.2 if you like

you can double-check your minimum downgrade version with minvercheck PUP (3.56 and lower compatible), but December 2010 and lower should all be fine
Thank you very much for your quick response! I was being ultra careful and didn't want to lock the console in a CEX/CEX state. I will check with the minvercheck first to be 100%.
Thank you again for all of your efforts! You and the other Devs are Epic and at the end of the day I hope you feel appreciated! The community is better because if the many hours of work you guys put in!
 
I want to use this amazing ps3xploit v2 to then install Rebug 4.82.2 D/REX and use toolbox to toggle the lv2 to DEX
Do i start with D/REX or do i start with Rex and then update to D/REX?

REX and D-REX are exactly the same CFW. You would need to install REX as your PS3 is CEX and has never been converted to DEX. Its not as simple as just switching the LV2 Kernel to DEX, you cannot use the DEX Kernel if your PS3 is on CEX, only DEX can switch between the 2.

You need to use the REBUG Tool box to dump your EID Root Key (ERK) and then convert your PS3 to DEX by re-writing the console Target ID in the flash to DEX changing it from EID5 (CEX) to EID0 (DEX).

And to be honest there's no point in then installing D-REX. You get exactly the same as REX.

D-REX is mainly for DECH PS3's ( Proper DEBUG units ) as they will not use a CEX CFW PUP file as soon as you jail break it. They need a DEX. D-REX is set to be installed as DEX on default for these consoles. You can then mess about and converting them.
 
REX and D-REX are exactly the same CFW. You would need to install REX as your PS3 is CEX and has never been converted to DEX. Its not as simple as just switching the LV2 Kernel to DEX, you cannot use the DEX Kernel if your PS3 is on CEX, only DEX can switch between the 2.

You need to use the REBUG Tool box to dump your EID Root Key (ERK) and then convert your PS3 to DEX by re-writing the console Target ID in the flash to DEX changing it from EID5 (CEX) to EID0 (DEX).

And to be honest there's no point in then installing D-REX. You get exactly the same as REX.

D-REX is mainly for DECH PS3's ( Proper DEBUG units ) as they will not use a CEX CFW PUP file as soon as you jail break it. They need a DEX. D-REX is set to be installed as DEX on default for these consoles. You can then mess about and converting them.
Thank you for the clarification! I am new to this community and i appreciate you guys explaining these details and helping all of us out all of the time. Thank you for your efforts!
 
Last edited:
Does this still apply? If i understand once Rebug 4.82.2 D/REX came out that we now have DEX with 4.82 also.
Please correct me if I am wrong.
I have a slim 2501a, manufacture date of August 2010 on OFW 4.81
I want to use this amazing ps3xploit v2 to then install Rebug 4.82.2 D/REX and use toolbox to toggle the lv2 to DEX
Do i start with D/REX or do i start with Rex and then update to D/REX?
I apologize if this has been answered already. I have read so many forum posts and haven't noticed this being discussed fully.

I should also mention that you need to dump your IDPS (EID5) and PSID before you switch to DEX and use something like CCAPI to set it to spoof to these on boot of your PS3 as you will not be able to access PSN using the DEX (EID0) IDPS. REBUG has a built in safety to prevent you from doing this. As getting the right ones once on DEX can be a bit of a mission and faff on.
 
I should also mention that you need to dump your IDPS (EID5) and PSID before you switch to DEX and use something like CCAPI to set it to spoof to these on boot of your PS3 as you will not be able to access PSN using the DEX (EID0) IDPS. REBUG has a built in safety to prevent you from doing this. As getting the right ones once on DEX can be a bit of a mission and faff on.
Thank you, I didn't mean to take the thread on a tangent, but i am looking forward to using the Ps3xploit. Thank you again.
 
To jailbreak your slim console on 4.82, you should use the steps I detailed in the post below. Don't omit anything, every detail is important, even if it doesn't seem like it to you.
https://www.psx-place.com/index.php?posts/108103
Thank you for the easy and detailed tutorial. I was able to successfully use ps3xploit! I then installed Rebug 4.8.2 Rex and used the Rebug Toolbox to switch from CEX/CEX to DEX/DEX.
Thank you Devs again for these amazing tips and tricks. You people Rock!
 
Hello im a newbie here and im confused on how to jailbreak my ps3
Model:CECH2100A
Firmware: 4.81 version
Is this possible?
And where do i start? TIA
 
Hi I'm new but I'm on 4.80 OFW but I'm wanting to use the Han exploit helpfully until 3k model is added to this list, but I'm struggling to find where 4.81 OFW is? I've found a 4.81 update but I'm unsure if it's untouched, I've also a dump of my ps3 from the ps3exploit web site if that's any use to anyone
 
Hi I'm new but I'm on 4.80 OFW but I'm wanting to use the Han exploit helpfully until 3k model is added to this list, but I'm struggling to find where 4.81 OFW is? I've found a 4.81 update but I'm unsure if it's untouched, I've also a dump of my ps3 from the ps3exploit web site if that's any use to anyone

Curious why do you think you need 4.81?
 
Hi I'm new but I'm on 4.80 OFW but I'm wanting to use the Han exploit helpfully until 3k model is added to this list, but I'm struggling to find where 4.81 OFW is? I've found a 4.81 update but I'm unsure if it's untouched, I've also a dump of my ps3 from the ps3exploit web site if that's any use to anyone

4.82 OFW is the firmware to be on for these tools, and also the v3.0 tools to install HAN. The correct update PUP file can be found here:

https://www.psdevwiki.com/ps3/4.82_CEX
 
I read in another post there was extra options for 4.81 and more to come, so I don't want to move to far forward, if Han works on 4.81 and 4.82. So really I'm in hope that my 3k ps3 will be added to one of the exploit list, thanks for a quick reply
 
Instaloval jsem všechno v pořádku, dobrou práci pro všechny.
Chci nahradit pevný disk, bude to problém.
Angličtina není můj jazyk jen kompilátor google.
Díky za odpověď.
 
Instaloval jsem všechno v pořádku, dobrou práci pro všechny.
Chci nahradit pevný disk, bude to problém.
Angličtina není můj jazyk jen kompilátor google.
Díky za odpověď.
Please edit your post to include an English translation of your post. Google Translate is perfectly acceptable. Thank you. :)
 

Similar threads

Back
Top