• Official PS3 Toolset is now supporting 4.92 Firmware

    View Official Release Post for additional information HERE

PS3 [UPDATE 4] PS3 Toolset by bguerville: A powerful collection of tools fueled by new PS3 exploit

UPDATE FEB 2023 (The domain's of ** ** 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 and .com are no longer in poccession of the team, A new address will be posted in future release coverage.
Update (4) Now supporting 4.86 Fully & Issue fixed with NAND console's in rare situations
.You may recall a recent article revealing a few exclusive screenshots of bguerville's latest project, now the time has come to introduce the next evolution in PS3 Jailbreaking solutions. The PlayStation 3 Toolset by @bguerville is a new suite of tools, built upon a new PS3 exploitation framework & fueled by a new exploit discovered on the PS3 by the developer. The new exploit (and the toolset project as a whole) is compatible with all PS3 models running 4.82 - 4.86 OFW/HFW/CFW

While ps3xploit team member's @habib continued research and development of PS3HEN for nonCFW models with assistance from @esc0rtd3w, @bguerville meanwhile was working on his own research and developing other tools and exploits as you will see with this new PlayStation 3 Toolset, which thorough testing was conducted by @esc0rtd3w (whom we recently interviewed). All the team of talented devs have done some amazing work in the scene in recent years with all the PS3Xploit projects and that trend continues with this release.

The PS3 toolset is a project that @bguerville has been working on for some time,
the developer gave us a brief timeline of events since the Ps3Xploit Tools 2.0 framework (flash writer and dumper(s)) that led to this new release (see the timeline section).

Some tools in this project may offer limited features on non-CFW compatible consoles. For instance, the Flash Memory Manager includes the most functionality for CFW-compatible consoles, certain of its features are available on non-CFW models, others aren't. Features such as the dumping of flash memory (for backup purposes) and displaying of various console specific information in real-time such as the IDPS, Factory Installed Firmware version and automatic detection of your console's Custom Firmware (cfw) compatibility status are available on both CFW compatibles & non CFW compatibles console's.

Note that the PS3 Toolset does not feature PS3HEN, bguerville declared having his own plans for a HEN style solution.

The validation and safety checks have advanced greatly in this latest framework of bguerville's tools (since the release of the flashing tools in PS3Xploit v1.0 and v2.0), the toolset detects your console type and only allows the features that are compatible with your console to be used on your system, making it noob proof while also being very user friendly thanks to new automation and detection built in.

Let us now discover this release and how to use various functions of the toolset.

PS3-Toolset_bguerville.png

  • PS3 Toolset by bguerville
    PS3 Toolset by @bguerville.png 9797979.png

    "The PS3 Toolset is a repository project for tools built upon a new ps3 exploitation framework I have been working on for a while. More tools should be added to this repository with time.
    I hope you enjoy using them as much as I enjoy making them ;-)"

    Project Timeline:

    • End 2018, Sony patches one of the bugs the ps3xploit tools exploited to gain ROP execution. (4.83 OFW release)
    • Beginning 2019, I begin to look for a replacement exploit & the release of ps3xploit tools 3.0 is postponed.
    • Spring 2019, I rewrite most of the 3.0 framework to leverage the new capabilities gained with the new exploits.
    • Summer 2019, realizing the potential of the newly written 4.0 framework to create flexible & powerful tools, I decide to cancel the 3.0 release altogether & scrap the 3.0 framework.
    • Beginning 2020, I am releasing this "Toolset" project, as a repository for the tools created around my 4.0 framework that I deem release worthy, each tool being accessible in a toolset tab. This project is the fruit of many sleepless hours during many months, it showcases only part of the 4.0 framework capabilities though, there is still room for more surprises later... ;-)

    The initial release, contains a couple userland tools, a fully featured Flash Memory Manager & a Memory Editor (mostly for development & research purposes). A file explorer tool should be added to the repository soon, it will be the last userland tool I write for the foreseeable future
    General Information about the PS3 Toolset
    • Toolset supports all ps3 models & official firmware versions from 4.82 to 4.86 (cex & dex) *some ps3 models have exclusive features/tools (note: toolset tools will also work from CFW)
    • PS3 Toolset is executed from the PS3's Web-Browser by visiting the following URL (SSL): ** 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
    • PS3 Browser Requirements
      • JavaScript (Enabled from browser settings)
      • Cookies (Enabled from browser settings)
      • Flash Plugin (Enabled, but this one has a few caveats that may need explaining, the good news being that the toolset will detect the issue and let you know how to proceed (if there is an issue), see further explanations below)
        • If ever in the past, you agreed to load the Flash Player plugin when prompted and checked the checkbox "Do not show again", you should have no issue & will never even see the plugin popup.
        • If you never before checked the "Do not show again" checkbox, you will be greeted with a popup asking you to allow the Flash player plugin. If you agree to load the plugin, the PS3 toolset should continue to load. Note that if you take more than 15s to agree when prompted by the popup, you will get a PS3 Toolset warning about the plugin being disabled even if you finally agreed to load the plugin, just refresh the page when prompted.
        • If ever you got the Flash Player plugin popup in the past & selected NO and checked the checkbox "Do not show again", the Flash Player plugin will be permanently disabled, consequently the PS3 Toolset will not be able to load. Unfortunately there seems to be no official way to reset this setting in the browser. The PS3 toolset does have automatic detection of this issue and some instructions are given. Currently the easiest workaround is to create a new user profile on the XMB, when launching the toolset on the new profile, you will be greeted with the browser pop-up asking to allow the flash plugin. However it has been found that in some cases, a new user profile is not sufficient to reset the Flash Player plugin status. I hope that other devs & advanced users will look into this situation while I continue working on new tools, if nobody does, I might end up looking into the problem after the next tool release.
    • You are free to use the tools in this project at your own risk. Keep in mind that no official support is provided, if you experience any kind of problem & find yourself in need of help, I strongly recommend that you turn to the PS3Xploit sub-forum on psx-place.com for support & guidance..
    • It is highly recommended that you adjust the console's System Time settings properly to avoid any time related issues with the browser and/or the Flash Player plugin.
    • To avoid potential crashes, you should never attempt to close the browser while toolset operations are in progress, especially when the browser exit confirmation setting is turned off.
    • PS3 Toolset only loads tools & features compatible for your console, this means no accidental use of a feature not compatible with your system.
    • No local/offline version is planned & the source code will remain closed for the time being.

  • Requirements
    • PS3 Console (Any Model) running 4.82 - 4.86 (CEX/DEX) Firmware
    • Internet Connection to access Toolset from PS3's Internet Browser.
    • PS3 Browser Flash Player 9 Plugin enabled (View General Information section for additional info)
    • PS3 Browser Javascript enabled
    • PS3 Browser Cookies enabled

    Quick Overview of Toolset (v1.0.19) Capabilities:

    All Models
    • Display console's IDPS
    • Detects Console's CFW Compatibility + Factory Installed Firmware
    • Detects Internal Flash Type of console: NOR / NAND / eMMc ect...
    • Detects console & firmware information
    • Take's a Full dump (backup purposes) of Internal Flash
    • Memory Editor tool (R&D tool)
    Custom Firmware (CFW) compatible Models Only
    • Patching of OFW Flash (Flash Memory Patch) for Custom Firmware Installations.


  • Included Userland Tools (v1.x)
    1. The Memory Editor tool v1.1
    upload_2020-2-21_22-23-34.png

    • The tool maps up all the currently loaded sprx modules segments (text & data) & allows you to browse them as well as the 2 vsh segments and the browser memory container. Users can also edit the memory as they see fit in all writable memory segments. This is mostly a R&D tool.
    • - Notice - issues caused by RAM synchronisation. The memory editor is not a live debugger, it cannot pause lv2 or userland threads execution. Consequently, the RAM can be modified by the various threads executing in userland between the moment the memory editor tool takes a snapshot of a ram range to create the hex table to display on screen & the moment the table is actually displayed on screen.This means that on rare occasions the values displayed on screen might be different from those actually in RAM. This is especially true for specific memory areas such as the browser container memory.
      • There is no easy way to solve this issue, even the debugging deci3 syscalls available only in DEX would not help us much because while it would enable us to take properly synchronised snapshots of the RAM, displaying the data on screen would still require running js code in the browser, which would modify the RAM & lead to the same synchronisation problem we currently face without using the deci3 syscalls.
      • I implemented code to color out the detected table cells found to be unsynced with RAM so there is as little ambiguity as possible. The text of such detected table cells is set to 'undefined'.

    2. Flash Memory Manager v1.2 tool
    upload_2020-2-21_22-24-9.png

    • Compatible with all PS3 models (patching flash options exclusive to CFW compatible models)
    • FMM displays basic Flash Memory data in a tree.
    • Clicking on appropriate tree nodes reveals context menu entries to launch the tool's features.
    • Among other things, the manager can dump the Flash memory to file on any natively writable partition mounted on the console.
    • To patch (for cfw installation) a console using the no-fsm method, users must first load a patch file in memory. That file will be checked first & if found valid, the context menu entry to apply the patch will be enabled.
    There are 2 ways to acquire the correct patch file to flash.
    1. it can be downloaded to disk first then loaded into memory from file & finally applied to the system
    - or -
    2. it can be loaded via https directly to memory without using disk storage, the data is checked in RAM then if found valid, users can decide to apply it (from the unlocked menu, once file is validated by the toolset automatically).​
    • After applying a patch, the FMM automatically dumps the 2 ROS regions it just overwrote to double check that patching was properly done.
    • Progress dialogs keep the user informed of current operations & outcomes. User logs are provided in the various progress dialogs.

    3. Logs v1.0 Tool
    PS.png

    Technically the log section is also a tool of this Toolset. Its tab contains all the logs, warnings, errors & debug output of the toolset & its different tools.
    • Whenever something goes wrong, it's the first place to look & screenshots can be used to identify problems.
    • I also included a UDP broadcast similar to Cobra's. Users can use socat to listen on UDP to the Toolset broadcast. However for the moment, only some data gets broadcasted but not the entire contents of the log tab because of the performance impact. With the file explorer release, I plan implement a few changes to this feature as well, the UDP broadcast will be done in a separate thread & all logged data should be broadcasted to UDP.

  • colored.png
    Legend:
    • Displays firmware information
      • PS3 Firmware: (version)
      • VSH Mode: (Retail (CEX) or Debug (DEX))
      • Kernel Mode: (Retail (CEX) or Debug (DEX))
      • Custom Syscalls:
        • 1. detects 'Mamba' (if syscall 1022 exists)
        • 2. detects 'Cobra' (if 1022 does not exist but syscall 8 works)
        • 3. detects CFW (if 1022 & 8 are unavailable but syscall 6 works)
        • 4. Displays 'No' (if neither sc 1022, 8 & 6 are unavailable)
    • Flash Memory
      • the tree contains alot of information about any PS3 console and also provide option for taking a backup (dump) of internal flash
    • Quickly determines if your console is a NOR/NAND/eMMc type
      • Displaying of console info, also note previous tools user's had to select NOR/ NAND/ eMMc Tools (depending on model), now the toolset automatically checks and detects tools needed.
    • Displays your IDPS (option to hide onscreen)
      • Will display any Ps3 models IDPS
    • Displays Factory Installed Firmware
      • If your console < 3.60 that means you can install CFW
    • Displays Custom Firmware Installation Compatibility,
      • No longer have to check the sticker of your console and run minverpup and check min factory installed firmware, the toolset displays the compatibility of a Custom Firmware (CFW) Installation for your console.
    • ROS Bank 0/1
      • Display's hash checks of ROS 0 /1 (technically the hashes are not calculated from the entire ros ranges but from the range corresponding to a noFSM patch so that ROS hashes & patch file hashes can be compared.
    • Flash Memory Patch (CFW Compatible Console Only)
      • Patch Flash for CFW installations

    .
    Flash Dumper:
    - Notice - dumps should always be validated with PyPS3Checker to ensure a proper dump took place before using it for future backup purposes)

    Purpose of dumping the Flash?

    • Having a Clean backup of your system internal flash memory is a vital piece of information to have stored, its something that may never be used but can be extremely important in some instances where a brick occurs, having a clean backup can help restore your system along with a hardware flasher
    PS3 Toolset by @bguerville_2.png 33.png 6666.png


    Patch Flash (aka Flash Writer Tool) - CFW compatible console's only
    Purpose of patching flash?
    • Patching the Flash (ROS 0/1) allows for Custom Firmware Installations on applicable models
    PS3 Toolset by @bguerville_1.png
    2222.png
    3333.png
    4444.png
    55555.png
    666666.png
    7777.png
    8888.png
    9999.png
    Userland Memory Editor
    Purpose of using Userland Memory Editor?
    • The memory editor is a R&D tool. It's useful mostly for devs & hackers who can use it to peek/poke the RAM, either to verify certain results or to search for flaws.
    PS3 Toolset by @bguerville_4.png 888.png 101010.png
    Toolset detecting various PS3 models
    PS3 Toolset by @bguerville_3.png ps3-toolset-nor-4201b.png ps3-toolset-nand-phat-a01.png ps3-toolset-emmc-4201a.png
    Toolset Themes Options
    The toolset contains 4 Themes as shown below
    PS3 Toolset by @bguerville_5.png
    PS3 Toolset by @bguerville_10.png
    PS3 Toolset by @bguerville_6.png
    PS3 Toolset by @bguerville_7.png
    PS3 Toolset by @bguerville_8.png

  • Acknowledgements
    My warmest thanks to Jason, for his friendship & support of course, but in the context of this project, also for testing my work on a daily basis, not just before this release but all year round.


    The PS3 Toolset & its GUI were built in native js upon various open source js libraries including jQuery, jQueryUI, bigInteger, jstree, mCustomScrollbar, js-cookie, sjcl, switchButton & toastmessage as well as the Fork Awesome CSS icon library .
    Thanks to all the coders involved in the various projects.


    Thanks to all the psdevwiki contributors, scene hackers & developers who have brought us to this point.
    - @bguerville
    .
    Help and Donations
    You can show your appreciation for my (@bguerville) work & help fund future projects with a donation in BTC at either of the addresses below
    Thank you for your support.

    ** 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/assets/images/qr-legacy-P2PKH.png
    ** 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/assets/images/qr-native-segwit-BECH32.png
    ** 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/assets/images/qr-PayNyms.png
    Legacy P2PKH
    Segwit BECH32
    PayNyms

    The PS3Xploit team also needs your continued help to cover its growing web hosting costs.
    Please consider a donation to PS3Xploit via Paypal at https://www.paypal.me/ps3xploit

From the PS3 web browser you can access the toolset @: (SSL only)
** www.** ** www.ps3xploit.net > D... (NEW URL = http://ps3toolset.com)/bgtoolset

UPDATE (2) - Regarding 4.86 Support via @bguerville

PS3 Toolset is fully supporting 4.86

UPDATE (3) -A limited number of user's have been complaining of errors, the information often provided by user's is incomplete, which means tracking the issue is not easy based on the information provided, Developer bguerville is asking those user's who are experiencing issue to provide a dump of the flash to diagnose a possible issue and fix for the problem, here is a thread by fellow developer @esc0rtd3w setup here to acquire those dumps from affected user's:


Update (4) - Issues has been resolved and FMM has been updated to
v1.0.22. A fix for the handful of ppl with NAND consoles who are stuck unable to install another firmware at
** www.** ** www.ps3xploit.net > D...http://ps3toolset.com)/bgtoolset/fix_nand.php

Instructions here for NAND ISSUE:
https://www.psx-place.com/threads/bg-toolset-user-issues-and-dump-submissions.28868/
 
Last edited:
Hello! Thank you! Maybe I'm missing something... bgtoolset says my syscall is CFW now. But I don't have an option under games to install packages. I tried downloading and using system update via usb to flash CFW 4.87.2 Evilnat, but after a 100% the ps3 kinda flashes then says the latest version of firmware is already available. I know there are a million guides.. this is just so convaluted with 10k versions of ps3's and firmware and and and. Lol. Thanks again. I appreciate any and all help. You guys rock.
yes, as @baldjared said, use recovery.

I am curious what model you have though, because from my testing, NAND will not allow firmware install from USB, while on XMB, but NOR will. So i assume you have NOR since you were able to get to the point of firmware pup copying to /dev_hdd1/ and allowing a reboot.
 
Hello! Thank you! Maybe I'm missing something... bgtoolset says my syscall is CFW now. But I don't have an option under games to install packages. I tried downloading and using system update via usb to flash CFW 4.87.2 Evilnat, but after a 100% the ps3 kinda flashes then says the latest version of firmware is already available. I know there are a million guides.. this is just so convaluted with 10k versions of ps3's and firmware and and and. Lol. Thanks again. I appreciate any and all help. You guys rock.

I am pretty sure you did NOT actually install a CFW. You seem to have only patched your console to allow you to install a CFW.. as far as I can tell, that's what BgToolset does. You now need to install a CFW in order to get the ability to install packages and such and, indeed, Evilnat's CFW is one such thing. I also experienced the same error as you did when updating via usb from PS3'S GUI.. it worked when updating through Safe Mode, as @baldjared suggested. :) Let us know if it worked.

@esc0rtd3w If it matters, I have a NAND PS3 (CECHC04) and I was not able to install Evilnat's CFW from the XMB.. I had to do it from Safe Mode. THANK YOU for your work on the toolset!
 
[I hope this is the right place, pls lmk if I should post elsewhere]

I also have a warning, 008.04 trvk_prg1 Hash : WARNING!


I can't see the Hash on the Hashlist, is this a new one?

From what I know it's a Gamestop refurbed, no idea if Sony has touched it.

Many thx!

Interesting. I'll need more info. Can you run the extract2csv tool available at https://www.psx-place.com/threads/need-community-help-to-collect-data.20882/
and send me the generated CSV file?
Thanks
 
I am pretty sure you did NOT actually install a CFW. You seem to have only patched your console to allow you to install a CFW.. as far as I can tell, that's what BgToolset does. You now need to install a CFW in order to get the ability to install packages and such and, indeed, Evilnat's CFW is one such thing. I also experienced the same error as you did when updating via usb from PS3'S GUI.. it worked when updating through Safe Mode, as @baldjared suggested. :) Let us know if it worked.

@esc0rtd3w If it matters, I have a NAND PS3 (CECHC04) and I was not able to install Evilnat's CFW from the XMB.. I had to do it from Safe Mode. THANK YOU for your work on the toolset!


Thanks guys! You are right on all points. I hadn't installed CFW yet... I thought thats what the bgtoolset did. Lol. And you're also right I too couldn't get Evilnat's CFW to install via XMB, and had to do it in recovery mode. All is well now though! I've installed some packages, and I'm working on transferring games over. FTP via wireless is crazy slow since the PS3 is only 802.11G. I REALLY appreciate everyone's help. Thank you again!
 
Thanks guys! You are right on all points. I hadn't installed CFW yet... I thought thats what the bgtoolset did. Lol. And you're also right I too couldn't get Evilnat's CFW to install via XMB, and had to do it in recovery mode. All is well now though! I've installed some packages, and I'm working on transferring games over. FTP via wireless is crazy slow since the PS3 is only 802.11G. I REALLY appreciate everyone's help. Thank you again!
If I were you, I would not use FTP to transfer games.
It's slow, connections usually go down in the middle of game transfers & storing all your games on internal hdd might sound practical at first glance but it is not the most efficient setup you can choose.

I suggest you use an external USB HDD with 2 partitions instead, a big ntfs partition to store your games as iso files & a small fat32 partition for stuff like modded games or whatever else.
All backup managers nowadays support ntfs & iso is the recommended format for games backup.
 
Thanks guys! You are right on all points. I hadn't installed CFW yet... I thought thats what the bgtoolset did. Lol.
A ps3 CFW is packed into a 200Mb pup file, it's full of files to be distributed all over the place, some files are copied on hdd, others on Flash memory, there are also files for the syscon, BD drive, etc..
Did you really think the Flash memory manager could do the same job as a CFW PUP installation using only a 7Mb patch file? ;-)
The only thing that FMM does is overwrite the CoreOS files (hypervisor, kernel etc...) in flash memory with just enough modifications to allow CFW installation. When it comes to patching, we commonly refer to the CoreOS as no-fsm patch.
In theory, a minimally patched CoreOS would be enough as no-fsm patch (something like the CoreOS of a DB FW) but in practice, it's easier to use the CoreOS from an existing CFW.
On reboot after patching, the kernel is CFW, if you open the Toolset, you can see that custom syscalls are in place. However all the other system files are still OFW, to update them, a CFW pup must be installed.
 
Last edited:
A ps3 CFW is packed into a 200Mb pup file, it's full of files to be distributed all over the place, some files are copied on hdd, others on Flash memory, there are also files for the syscon, BD drive, etc..
Did you really think the Flash memory manager could do the same job as a CFW PUP installation using only a 7Mb patch file? ;-)
The only thing that FMM does is overwrite the CoreOS files (hypervisor, kernel etc...) in flash memory with just enough modifications to allow CFW installation. When it comes to patching, we commonly refer to the CoreOS as no-fsm patch.
In theory, a minimally patched CoreOS would be enough as no-fsm patch (something like the CoreOS of a DB FW) but in practice, it's easier to use the CoreOS from an existing CFW.
On reboot after patching, the kernel is CFW, if you open the Toolset, you can see that custom syscalls are in place. However all the other system files are still OFW, to update them, a CFW pup must be installed.
Hi..i have a ps3 slim with error code 8002f2f0 when start system..i dump the NOR file with TNM5000 and check the dump file but the dump is ok but error code persist and system cant update..can i upload the dump file and can you check and fix it??

PyPS3checker v0.10.x. Check log.
Checked file : C:\Users\Amin\Desktop\PyPS3tools-master\PyPS3checker-standalone-package_2020-01-05_182610\0.bin
******* Getting flash type *******
Flash type : NOR
Reversed : YES
******* Getting SKU identification datas *******
idps = 0x09
metldr0 = 0xE890
metldr1 = 0x0E85
metldrkey = 0xBC78B8F02879A81184A0DA74
bootldr0 = 0x2F13
bootldr1 = 0x2F13
bootldrsize = 0x2F170
Matching SKU : OK
CECH-20xxx (DYN-001)
Minimum version 2.70
******* Getting SDK versions *******
ROS0 : 355.000
ROS1 : 355.000
******* Checking first_region_header *******
001.01 First Region Header 0x00 Filled Area 0 : OK
001.02 First Region Header Magic : OK
001.03 First Region Header 0x00 Filled Area 1 : OK
******* Checking flash_format *******
002.01 Flash Format String : OK
002.02 Flash Format Version : OK
002.03 Flash Format 0xFF Filled Area : OK
******* Checking flash_region_table *******
003.01 Flash Region Table Header : OK
003.02 asecure_loader Offset - Length : OK
003.03 asecure_loader Name : OK
003.04 eEID Offset - Length : OK
003.05 eEID Name : OK
003.06 cISD Offset - Length : OK
003.07 cISD Name : OK
003.08 cCSD Offset - Length : OK
003.09 cCSD Name : OK
003.10 trvk_prg0 Offset - Length : OK
003.11 trvk_prg0 Name : OK
003.12 trvk_prg1 Offset - Length : OK
003.13 trvk_prg1 Name : OK
003.14 trvk_pkg0 Offset - Length : OK
003.15 trvk_pkg0 Name : OK
003.16 trvk_pkg1 Offset - Length : OK
003.17 trvk_pkg1 Name : OK
003.18 ros0 Offset - Length : OK
003.19 ros0 Name : OK
003.20 ros1 Offset - Length : OK
003.21 ros1 Name : OK
003.22 cvtrm Offset - Length : OK
003.23 cvtrm Name : OK
003.24 Flash Region Table 0x00 Filled Area : OK
******* Checking asure_loader_region *******
004.01 asecure_loader Header : OK
004.02 metldr Offset : OK
004.03 metldr Length : OK
004.04 metldr Name : OK
004.05 metldr RevKey : OK
004.06 metldr Binary Size : OK
004.07 metldr Statistics : OK
004.08 asecure_loader 0x00 Filled Area : OK
******* Checking eEID_region *******
005.01 eEID Header : OK
005.02 EID0 Offset - Length : OK
005.03 EID1 Offset - Length : OK
005.04 EID2 Offset - Length : OK
005.05 EID3 Offset - Length : OK
005.06 EID4 Offset - Length : OK
005.07 EID5 Offset - Length : OK
005.08 EID0 IDPS0 : OK
005.09 EID0 IDPS1 : OK
005.10 EID0 Static : OK
005.11 EID2 BlockSize/Padding : OK
005.12 EID3 Static0 : OK
005.13 EID3 Static1 : OK
005.14 EID3 Static2 : OK
005.15 EID5 IDPS0 : OK
005.16 EID5 IDPS1 : OK
005.17 EID5 Static : OK
005.18 eEID Region 0xFF Filled Area : OK
005.19 eEID Statistics0 : OK
005.20 eEID Statistics1 : OK
******* Checking cISD_region *******
006.01 cISD Header : OK
006.02 cISD0 Offset - Length : OK
006.03 cISD1 Offset - Length : OK
006.04 cISD2 Offset - Length : OK
006.05 cISD0 0xFF Filled Area : OK
006.06 cISD1 IDLog Header : OK
006.07 cISD1 Semistatic 1 : OK
006.08 cISD1 Semistatic 2 : OK
006.09 cISD1 0xFF Filled Area 0 : OK
006.10 cISD1 Static : OK
006.11 cISD1 Semistatic 3 : OK
006.12 cISD1 0xFF Filled Area 1 : OK
006.13 cISD1 Statistics : OK
006.14 cISD2 : OK
006.15 cISD 0xFF Filled Area : OK
******* Checking cCSD_region *******
007.01 cCSD Header : OK
007.02 cCSD Entry Table : OK
007.03 cCSD 0xFF Filled Area : OK
******* Checking Revokation_region *******
008.01 trvk_prg0 SCE : OK
008.02 trvk_prg0 Hash : OK
Size = 0x2E0
MD5 = 78629D24BD721488F3A1E846938F87DF
Version = 3.55 (from PUP)
008.02 trvk_prg0 0xFF filled area : OK
008.03 trvk_prg1 SCE : OK
008.04 trvk_prg1 Hash : OK
Size = 0x2E0
MD5 = 78629D24BD721488F3A1E846938F87DF
Version = 3.55 (from PUP)
008.04 trvk_prg1 0xFF filled area : OK
008.05 trvk_pkg0 SCE : OK
008.06 trvk_pkg0 0xFF filled area : OK
008.07 trvk_pkg1 SCE : OK
008.08 trvk_pkg1 0xFF filled area : OK
******* Checking CoreOS_region *******
009.01 ROS0 Header : OK
009.02 ROS0 Hash : OK
Size = 0x6FFFE0
MD5 = F162E0D72EBA0F46B7FB36E6AAB63958
Version = 3.55 CEX Patched
009.03 ROS0 unused 0xFF Filled Area : OK
009.04 ROS1 Header : OK
009.05 ROS1 Hash : OK
Size = 0x6FFFE0
MD5 = F162E0D72EBA0F46B7FB36E6AAB63958
Version = 3.55 CEX Patched
009.06 ROS1 unused 0xFF Filled Area : OK
******* Checking cvtrm_region *******
010.01 Pre cvtrm 0xFF Filled Area : OK
010.02 cvtrm0 Header : OK
010.03 cvtrm0 0xFF Filled Area : OK
010.04 vtrm0 Magic : OK
010.05 vtrm0 Reserved Entries : OK
010.07 cvtrm1 Header : OK
010.08 cvtrm1 0xFF Filled Area : OK
010.09 vtrm1 Magic : OK
010.10 vtrm1 Reserved Entries : OK
******* Checking Second_Region_Header *******
011.01 Second Region Header 0x00 Filled Area 0 : OK
011.02 Second Region Header Magic : OK
011.03 Second Region Header Count : OK
011.04 Second Region Header 0x00 Filled Area 1 : OK
011.05 Second Region Unknown Block 0 : OK
011.06 Second Region Header 0x00 Filled Area 2 : OK
011.07 Second Region Unknown Block 1 : OK
011.08 Second Region Header 0x00 Filled Area 3 : OK
******* Checking Unreferenced_Area *******
012.01 unreferenced area 0xFF Filled : OK
******* Checking CELL_EXTNOR_AREA_Region *******
013.01 CELL_EXTNOR_AREA Header : OK
013.02 CELL_EXTNOR_AREA 0x00 Filled Area 0 : OK
013.03 CELL_EXTNOR_AREA 0x00 Filled Area 1 : OK
013.04 CELL_EXTNOR_AREA 0x00 Filled Area 2 : OK
013.05 CELL_EXTNOR_AREA 0x00 Filled Area 3 : OK
013.06 CELL_EXTNOR_AREA 0xFF Filled Area 0 : OK
013.07 CELL_EXTNOR_AREA 0x00 Filled Area 5 : OK
013.08 CELL_EXTNOR_AREA 0x00 Filled Area 6 : OK
013.09 CELL_EXTNOR_AREA 0xFF Filled Area 1 : OK
******* Checking bootldr_region *******
014.01 bootldr0 : OK
014.02 bootldr1 : OK
014.03 bootldr Rev key : OK
014.04 bootldr Statistics : OK
014.05 bootldr 0xFF Filled Area : OK
******* Checking datamatches *******
bootldr size : OK
per console nonce : OK
CELL_EXTNOR_AREA Hash1 : OK
CELL_EXTNOR_AREA Hash2 : OK
metldr size : OK
vtrm0 : OK
vtrm1 : OK
******* Checking repetitions *******
Header Magic0 Repetitions : OK
asecure_loader Repetitions : OK
eEID Repetitions : OK
cISD Repetitions : OK
cCSD Repetitions : OK
trvk_prg0 Repetitions : OK
trvk_prg1 Repetitions : OK
trvk_pkg0 Repetitions : OK
trvk_pkg1 Repetitions : OK
ros0 Repetitions : OK
ros1 Repetitions : OK
cvtrm Repetitions : OK
******* Additional information *******
HDD : Hitachi HTS545025B9SA00 090804PBY208QSHNS68A
MAC address : 00:24:8D:5D:22:CD
CID : 0x00020194FE59
eCID : 01C520025C1E270E1109F04200000000
board_id (part of console S/N) : 27453973
kiban_id (board barcode) : 3HG12752231B
******* Checks completed *******
Total number of checks = 155
Number of dangers = 0
Number of warnings = 0
All checks done in 10.96 seconds.
----------------------------------------------------------------------------
| IMPORTANT NOTICE ! |
| Checks of late CECH-25xxx, CECH-3xxxx and CECH-4xxxx consoles dumps still |
| under development and may return false results. If you feel it's the case, |
| please post your *.checklog.txt in a new issue on my github repository: |
| https://github.com/littlebalup/PyPS3tools/issues |
| Thanks! It will help me a lot to improve that tool ;) |
 
@amiani

There is no apparent issue with your Flash Memory.. Which doesn't necessarily mean that there is no issue for sure.

There could be a stack of reasons for your problem.

1. The internal hdd could be failing, it's not uncommon.
2. There could be a problem with your usb device, a USB hub or corruption with the PUP file itself.
3. There could be a "spoofed idps" issue
4. Another hardware based issue.
Etc..

At least, now you know that the console is on 3.55 & you can use 3.55 OFW for your PUP installation attempts. If installing 3.55 OFW fails, then there is a problem.

@littlebalup @baileyscream
What do you think?

And littlebalup, what is "3.55 CEX patched" exactly? 3.55 requires patching?
If it is in the hash list I assume it's a classic user case so obviously I am missing something.. Lol
 
Last edited:
@amiani

There is no apparent issue with your Flash Memory.. Which doesn't necessarily mean that there is no issue for sure.

There could be a stack of reasons for your problem.

1. The internal hdd could be failing, it's not uncommon.
2. There could be a problem with your usb device, a USB hub or corruption with the PUP file itself.
3. There could be a "spoofed idps" issue
4. Another hardware based issue.
Etc..

At least, now you know that the console is on 3.55 & you can use 3.55 OFW for your PUP installation attempts. If installing 3.55 OFW fails, then there is a problem.

@littlebalup @baileyscream
What do you think?
What CFW is "3.55 CEX patched" exactly?
Thank you so much @bguerville..i tried 3.55 OFW and CFW but error code appeared after hit the system update..i have a flash disk and when turn on the system the flash disk LED blinking about 2 sec..so i think the flash drive and usb port is healthy..so i tried with another healthy HDD but same reason..
 
@aminiani
"The system carnt update"
What happens when you try and what are you trying to update with?

Firmware revision and where you got it from

Usb stick

Any usb hubs

Anything plugged into the USB ports

How the update is on the usb stick (file system)

Can you try the min firmware check pup file.
@bguerville do you have a link to this before I go searching [emoji848]
 
@aminiani
"The system carnt update"
What happens when you try and what are you trying to update with?

Firmware revision and where you got it from

Usb stick

Any usb hubs

Anything plugged into the USB ports

How the update is on the usb stick (file system)

Can you try the min firmware check pup file.
@bguerville do you have a link to this before I go searching [emoji848]
i bought this console with this error..when i tried to update the console with latest version of OFW or CFW or HFW that error code 8002f2f0 appeared..
nothing pluged to usb port..i just connect FAT32 flash drive which so many console updated with this flash drive and its healthy..
 

Featured content

Trending content

Back
Top