41w ago - Following up on the PS3 NOR Inspector v0.01 and his previous release, today PlayStation 3 homebrew developer BwE has made available a BwE NOR Validator Public HTML Edition v1.01 PS3 homebrew application followed by v1.02, v1.14 and newer revisions with details below.
From the included ReadMe file: This all in one validator/patcher will interpret the byte orientation, patch for 3.55 and will then output the results of 2200+ validations.
1) Run the comical keygen style loader
2) Click start (and maybe mute)
3) A console will appear asking you to select your dumps (if you have more than one in the folder)
4) Make your selection and or select if you watch to patch it (either in its current byte orientation or the opposite)
5) Wait patiently
6) Read the output
Areas Of Validation
First Region Header
Asecure_Loader/Metldr Corrupt Sequences
Asecure_Loader/Metldr Encrypted Statistics
Second Region Header
Second Region Block 0
Second Region Block 1
Lv0ldr/Bootldr Corrupt Sequences
File Digest Keys
Use at own risk! Valid dumps may be invalid - Invalid dumps may be valid. There are almost infinite variations of each dump! Have fun and good luck!
Report any bugs or issues to bwe AT betterwayelectronics.com or directly to BwE at irc.efnet.org #ps3downgrade
1.15 - 25/03/2013 : added 4.40 ofw information and optimised some code
1.14 - 19/03/2013 : improved validation of the flash-region table
1.13 - 18/03/2013 : better handling for metldr.2, more id detections and md5s, added byte reversal option for experimenting with E3.
1.12 - 16/03/2013 : md5 bug fix, changed id detections and general improvements
1.09 - 02/03/2013 : improved corruption checks for metldr/bootldr + more validations + old coreos bug fix (again) + changed some results
1.08 - 29/02/2013 : added timeout for version check + added 16bit corrupt sequence check + fixed long outputs + fixed metldr ident bug + changed some warning/danger results + changed 00/ff results
1.06 - 27/02/2013 : fixed bug when handling old coreos versions + fixed .self md5 list
1.05 - 25/02/2013 : added approx 220 more validations + changed statistic ranges + latest version check + fixes to metldr/bootldr
1.02 - 22/02/2013 : more md5's & authid checks + changed some results.
1.01 - 16/02/2013 : authid check bugfix
1.00 - 15/02/2013 : first public release
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
Can you please verify for us that your power cable connector is properly inserted into the connector. Usually the gold contacts have a hard time making the proper connection. Please let us know if you even get the stanby (red) light.
Hi, I flashed my ps3 back to original dump but I am getting no signal from hdd or usb what can I do I verified my dumps with ps3 flash tool and bwe nor validator 1.31 all was fine my ps3 model is cechk01.
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.
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.
Update: From sinsizer:
Added 4.46 patches
Some small changes
OFFSET: 0xF00896 --- VALUE: 0x20 --- 0x00 BLANK AREA