- Following up on the previous
updates from BwE
, today PlayStation 3 homebrew developer sinsizer
has made available PS3 NOR / NAND Statistic Beta for those interested in validating and checking their PS3 NOR / NAND dumps.
(Mirror) / PS3_NOR-NAND_Statistic.rar
/ dumpstatistic.7z (Win XP)
(Requires .NET Framework 4.0
To quote: Features:
- NOR/NAND statistics
- NOR/NAND patching
- NOR/NAND byte swapping
- NOR/NAND infos
- NOR/NAND validation
- NOR/NAND extraction
- DATECODE check
This tool works different than other validators. Instead of outputting a full log, it will output an error.log, if validate is checked. But see for yourself.
Always patching 3.55 is recommended to see if the patched statistic is right/green. ckp_management_ID values have to be equel as well as per_console_nonce (should be stated in error.log if not). There is one easy rule! If the error.log contains an entry, your dump is definitly broken!
Ros section is excluded from validation. Why? It's easy to repair, the hole section gets patched anyway and it leads to the rule above.
For NAND all known sections gets checked. But a big part is not or only rarely documented. So the hole part after cvtrm, cell_ext_os_area, OtherOS and unreferenced area at the end won't be checked. It's very important that you have look at the statistics and the “corrupt block count” of flowrebuilder when interleaving.
It's always recommended to check dumps manually with an hexeditor, and using other tools for validation, to be as save as possible! As long as it is not possible to decrypt the full dump, it's impossible to validate it to 100%. Keep in mind this is only beta.
: From sinsizer
- Added 4.46 patches
- Some small changes
OFFSET: 0xF00896 --- VALUE: 0x20 --- 0x00 BLANK AREA <--this is not normal, but it doesn't brick your console.
OFFSET: 0xF20020 --- VALUE: 0x000002000000004000000000 --- CELL_EXTNOR_AREA <--- you can find this check in line 1522, add this value or delete the check.
: Changelog: minor changes to the GUI (allows adding new patches to the patch folder). Thx to 3absiso and ChazLJ for testing.
How to extract the patch file for future CFW's (extracting/decrypting coreOS)
Tools Download: cos_extract.rar
- Extract CORE_OS_PACKAGE.pkg with pupview.exe from the firmware.pup.
- Unpack/decrypt the CORE_OS_PACKAGE.pkg with fwpkg.exe
- Copy the new file to the patch folder.
You have to use "ros" somewhere in the name. Otherwise it doesn't get recognized as patch.
: From sinsizer
: The tool patches now ros and rvk if a corresponding rvk patch is placed in the patch folder. If no rvk patch is found, it will only patch ros.
Naming convention for patch files:
In the example you can see that it will patch ros and rvk for nor. For nand it will patch only ros, because the revoke patch has another name. All patch files have to begin with the red names.
The tool will be released without patch files from now on. You can download the patchfiles here: ps3coredump.eu5.org
PS3 Coredump - All Files are in readable format! (000000000FACE0FF00000000DEADBEEF) or (IFI)
All tools, which use these files, should automatically detect the input format and swap the byteorder, if needed.
In future updates a small downloader will be integrated, as well as some other features regarding c2d and keyextraction from eid.
PS3 NOR/NAND Statistic Download: dumpstatistic_low_res.7z
on the Win XP port (linked above): What I did was download the latest one then I decompiled it and fixed a few minor decompilation errors and re-compiled it with .net 4.0 as target instead of .net 4.5. I tested to make sure it runs in Windows XP on one of my virtual machines, however... I didn't check that all checks etc. are ok, but they should be.