BwE NOR Patcher v1.0 PS3 Homebrew Application is Now Available

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.

Download: http://www.mirrorcreator.com/files/IIXLTHHA/BwE_NOR_Validator.rar_links / http://www.mirrorcreator.com/files/1XPQ5ILS/BwE_NOR_Validator_v1.02.rar_links / http://www.mirrorcreator.com/files/0DZOG4IM/BwE_NOR_Validator.rar_links / http://www.mirrorcreator.com/files/T0NNLQLK/BwE_NOR_Validator.rar_links / http://www.betterwayelectronics.com/files/BwE_NOR_Validator.rar (Mirror)

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.

How-to use

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

• Statistics
• First Region Header
• Flash Format
• Flash Region
• Asecure_Loader/Metldr
• Asecure_Loader/Metldr Corrupt Sequences
• Asecure_Loader/Metldr Encrypted Statistics
• EID
• EID0
• EID2
• EID3
• EID5
• IDPS
• CISD
• CISD0
• CISD1
• CISD2
• CCSD
• CCSD0
• CVTRM/VTRM0
• VTRM 1
• TRVK_PRG0
• TRVK_PRG1
• TRVK_PKG0
• TRVK_PKG1
• ROS0
• ROS1
• ROS0/1 AuthID's/MD5's
• Revoke/CoreOS MD5's
• Second Region Header
• Second Region Block 0
• Second Region Block 1
• CELL_EXTNOR_AREA
• Lv0ldr/Bootldr
• Lv0ldr/Bootldr Corrupt Sequences
• Lv0ldr/Bootldr Statistics
• Minimum Version
• File Digest Keys
• PerConsole Nonce
• Corrupt Sequences
• Repetition
• Authenticiation IDs

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

Changelog:

• 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.11 - 08/03/2013 : improved patching structure, added 3 musketeers patch (3.56 patching), code optimisation
• 1.10 - 04/03/2013 : added 25+ validations + changed results & outputs + bugfix
• 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




More PlayStation 3 News...

You can use getconsoleID too, and if you changed the console ID can you generate a PSID with that?

the PSID can't be found in any NOR/NAND dump, only in the "dumped" LV1/LV2 dumps from the console. there you have the PSID, so it needs PSIDPatch either way... and the 2xConsoleID/IDPS in ur dump is at offset:

NAND offset 80870 - 16 bytes ( search again the IDPS and the second one appears..) NOR offset offset 2F070 - 16 bytes (search again the IDPS ...)

maybe this helps:

PSID starts at 0x800000000044A18C in 3.41, 0x800000000045218C in 3.55. It is 16 bytes long. Two identicle Console ID's exist in memory: one which is 32 bytes at 0x80000000003C2EF0 and another which is 16 bytes at 0x8000000000452174. PSN seems to use the second one, but PSIDPatch patches both

I am not sure...

Can I get the Console ID from a NAND dump? The conosle I have this dump from is dead but not sure where to find the Console ID from this NAND dump.

I got the Console ID, now where to find the PSID?