Validating flash dumps
Why so important?
Whenever you want to mess with flash (NAND or NOR), you have to make sure you are getting 100% correct, valid, verified dumps.
So what can we use to prevent that, and make sure our dumps are as proper as we can check?
Flowrebuilder
Links to versions
http://www.ps3devwiki.com/files/flash/Tools/Flowrebuilder/
4.2.3.0 changelog ----------------- added support to manage NAND preloader dumps message user about the type of dump message the user if bootloader are missing auto-recognize if dump is normal or byte swapped and automanage them
- FlowRebuilder v.4.2.3.0.exe (367 KB) // mirror mirror2
- FlowRebuilder v.4.2.2.0.exe (389 KB) // mirror mirror 2 mirrors
- FlowRebuilder v.4.2.1.2.exe (313.50 KB) // mirror
- FlowRebuilder v.4.2.1.1.exe (473.57 KB) // mirror
- FlowRebuilder v.4.2.0.1.exe (474.01 KB) // mirror
- FlowRebuilder v.4.1.3.2.exe (459.95 KB) // mirror
- FlowRebuilder v.4.1.0.0.exe (454.85 KB) // mirror (don't use, for historic reasons listed)
Flowrebuilder options
- (NAND only) UNSCRAMBLE then interleave two NAND flashes into one unified dump - (4.1.0.0 and higher) : Makes a unified dump.bin from 2 seperate NAND flash dumps.
- In the second step it also extract the content of the unified dump. Make sure it extracts correctly (it will give no warning if it fails!) and all the needed files are there.
- (NAND only) RE-SCRAMBLE a modified dump then de-interleave it into two new flashes - (4.1.0.0 and higher) : Splits the unified dump.bin into 2 new seperate NAND flash dumps.
- Byte reverse and EXTRACT a NOR dump file - (4.1.0.0 and higher) : First byte reverse the single dump.bin then extract NOR content.
- EXTRACT a Byte reversed NOR dump or an interleaved and unscrambled NAND dump - (4.1.0.0 and higher) : Extract the single dump.bin.
- Byte reverse and PATCH a NOR dump - (4.2.1.1 and higher).
- PATCH a Byte reversed NOR dump or an interleaved and unscrambled NAND dump - (4.2.1.1 and higher).
- Byte reverse a dump - (4.2.1.1 and higher).
Note:
- when getting errors with autopatcher, use Winskeet to patch the unified dump and then Flowrebuilder to Rescramble it. -> Fixed in FlowRebuilder v.4.2.1.2
- Flowrebuilder 4.2.2.0 error in Wine : http://pastie.org/private/nxf7tutolf9jjojskxw
Extracted flash content files
(make sure they are all there, flowrebuilder will not give warning when it fails!):
- bootloader_0
- bootloader_1 (NAND only)
- cCSD
- cISD
- creserved_0 (NAND only)
- cvtrm
- eEID
- trvk_pkg
- trvk_prg
- \asecure_loader\metldr
- \ros\[two seperate folders named to FW version]\CoreOS files (19 up to 25 files, depending the FW version)
Notes:
- if it only extracted bootloader_0 + bootloader_1, check that both NANDs are dumped correct (known error with flashers that has bug with second NAND channel to read), and that high/low where selected correct.
- Do not use spaces in the folderpath, or Flowrebuilder will not extract the files.
- Bug workaround: delete previous extraction attempts to prevent Flowrebuilder to always error. -> bugreport -> Fixed in FlowRebuilder v.4.2.2.0
From unified to seperate low/high NAND files
If for some reason you lose the original seperate low/high NAND files and only have the unified, you need donor files to regenerate them.
extract and in Flowrebuilder select the option "RE-SCRAMBLE a modified dump then de-interleave it into two new flashes"
- Select the NAND backup "Flash 0" (TOP) file : here drop the 1bkp.bin
- Select the NAND backup "Flash 1" (BOTTOM) file : here drop the 2bkp.bin
- Select the Input NAND interleaved Modified file : here drop your unified flash .bin file
and click Execute Operation
This will result in making 2 new deinterleaved files you could use for reflashing (it is recommended to alway use your own deinterleaved sourcedumps, this method is only mentioned as last resort for people that lost their backups).
BwE NOR Validator
Created/Started by BwE on the 14th November 2012 (Because I was too lazy to constantly check everything).
Greetz/Credit: EussNL, Judges, No0bZiLLa, Rogero, Rebug, deank, 3absiso, AFP, SCE & PS3 Dev Wiki (+ Its Contributers).
This all in one validator/patcher will interpret the byte orientation, patch for either 3.55 or 4.40 and will then output the results of 2800+ validations via HTML.
Output Example
How?
1 - Place your .bin/s in the same folder as the validator.
2 - Run the validator and press Start.
3 - A console will appear asking you to select your dump (if you have more than one in the folder).
4 - Make your selection and/or select if you want to patch it (either in its current byte orientation or the opposite).
5 - Wait patiently.
6 - Press Enter at the end to launch the output.
Explanation
After selecting your dump and choosing which patch you want it will begin to process the validation. Once it is finished it will give you a brief count of the results, after this you simply press enter to exit.
The program will then open a html output illustrating everything that has been validated. Scroll through or use the menu at the top and read each section.
If a validation says 'warning' or 'danger' investigate it yourself manually using a hex editor, or contact somebody knowledgeable. Only corruption messages will show you the exact offset to look at, everything else won't so this is where you have to read/learn about it on the ps3devwiki.
Some validations will tell you that you need to patch it (e.g. TRVK_PRG0 / TRVK_PRG1 / TRVK_PKG0 / TRVK_PKG1 / ROS0 / ROS1 errors or warnings), if this is the case then do so (don't forget to rename the patched dump e.g. bkpps3.bin_patched to bkpps3.bin_patched.bin) and re-validate the patched dump (you can move the original unpatched dump to make sure it is checking the patched one).
If your dump has any 'danger' messages in the per console sections (find them in the menu) then there is a good chance its completely ruined and unfixable. Also, if your dump has a large amount of 'danger' messages then there is a serious issue - bad wiring can be discovered if you have any repetition in the dump.
Areas Of Validation
* Statistics * First Region Header * Flash Format * Flash Region * Asecure_Loader/Metldr * Asecure_Loader/Metldr Corrupt Sequences * Asecure_Loader/Metldr Encrypted Statistics/Entropy * EID * EID0 * EID1 * EID2 * EID3 * EID4 * EID5 * IDPS * CISD * CISD0 * CISD1 * CISD2 * CCSD * CCSD0 * TRVK_PRG0 * TRVK_PRG1 * TRVK_PKG0 * TRVK_PKG1 * ROS0 * ROS1 * ROS0/1 AuthID's/MD5's * Revoke/CoreOS MD5's * CVTRM/VTRM0 * VTRM 1 * Second Region Header * Second Region Block 0 * Second Region Block 1 * CELL_EXTNOR_AREA * Lv0ldr/Bootldr * Lv0ldr/Bootldr Corrupt Sequences * Lv0ldr/Bootldr Statistics/Entropy * Minimum Version * File Digest Keys * PerConsole Nonce * Corrupt Sequences * Repetition * Authentication IDs
Download
Application MD5: 28F0CD55255FE60E3F6D8AF90698440C
Changelog
- 1.31 - 27/05/2013 : added eid4 + fixed bug in entropy (note: possibly final version, unless adding firmware revisions/new consoles)
- 1.30 - 21/05/2013 : completely rewritten eid, cisd, ccsd + added more validations to it, upgraded other minor validations. all due to upcoming nand validator
- 1.28 - 15/05/2013 : completely rewritten cvtrm validation + added more validations to it, upgraded/perfected entropy
- 1.25 - 13/05/2013 : added entropy check for metldr/bootldr
- 1.24 - 06/05/2013 : added more information to suit newly discovered ps3 data, improved validation, added a tip for bad md5's, removed version forcing
- 1.23 - 29/04/2013 : improved validation, added 4.41 ofw information
- 1.22 - 16/04/2013 : added 115 more validations + changed statistic range for bootldr + other small boring changes
- 1.21 - 11/04/2013 : patch3 error fix.
- 1.20 - 10/04/2013 : added new console data, removed 3.56 patch (replaced with 4.40), added protection against using old validator, changed corruption check (again!), added quick info for console.
- 1.19 - 09/04/2013 : changed metldr statistic range, minver check (to suit refurbished ps3s), corruption changes
- 1.18 - 08/04/2013 : upgraded cisd/cell_ext_nor_area/metldr validations to suit unique metldr.2 revision, changed corruption output (again).
- 1.17 - 08/04/2013 : changed repetition check, changed corruption output, bugfix
- 1.16 - 02/04/2013 : added rogero's 4.40 patch, changed options, added 25+ md5's, changed stats range and id check
- 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
Warning
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!
Notes
Report any bugs or issues to [email protected] or directly to BwE @ irc.efnet.org #ps3downgrade or irc.ps3sanctuary.com #ps3hax
Give credit if you are using this for other people!
Made in Australia!
LT 4 AM <3
Gallery
BwE NAND Validator
Created/Started by BwE on the 3rd March 2013 (Because I was pressured to).
Greetz/Credit: EussNL, Judges, No0bZiLLa, Rogero, Rebug, deank, 3absiso, AFP, SCE & PS3 Dev Wiki (+ Its Contributers).
This all in one validator/patcher will patch for 3.55 and will output the results of 2799+ validations via HTML.
Output Example
How?
1 - Place your .bin/s in the same folder as the validator.
2 - Run the validator and press Start.
3 - A console will appear asking you to select your dump (if you have more than one in the folder).
4 - Make your selection and or select if you watch to patch it.
5 - Wait patiently.
6 - Press Enter at the end to launch the output.
Explanation
After selecting your dump and choosing which patch you want it will begin to process the validation. Once it is finished it will give you a brief count of the results, after this you simply press enter to exit.
The program will then open a html output illustrating everything that has been validated. Scroll through or use the menu at the top and read each section.
If a validation says 'warning' or 'danger' investigate it yourself manually using a hex editor, or contact somebody knowledgeable. Only corruption messages will show you the exact offset to look at, everything else won't so this is where you have to read/learn about it on the ps3devwiki.
Some validations will tell you that you need to patch it (e.g. ROS0 / ROS1 errors or warnings), if this is the case then do so (don't forget to rename the patched dump) and re-validate the patched dump (you can move the original unpatched dump to make sure it is checking the patched one).
If your dump has any 'danger' messages in the per console sections (find them in the menu) then there is a good chance its completely ruined and unfixable. Also, if your dump has a large amount of 'danger' messages then there is a serious issue - bad wiring can be discovered if you have any repetition in the dump.
Areas Of Validation
* Lv0ldr/Bootldr * Lv0ldr/Bootldr Corrupt Sequences * Lv0ldr/Bootldr Statistics/Entropy * First Region Header * Flash Format * Flash Region * Asecure_Loader/Metldr * Asecure_Loader/Metldr Corrupt Sequences * Asecure_Loader/Metldr Encrypted Statistics/Entropy * EID * EID0 * EID1 * EID2 * EID3 * EID4 * EID5 * IDPS * CISD * CISD0 * CISD1 * CISD2 * CCSD * CCSD0 * TRVK_PRG0 * TRVK_PRG1 * TRVK_PKG0 * TRVK_PKG1 * ROS0 * ROS1 * ROS0/1 AuthID's/MD5's * CoreOS MD5's * CVTRM/VTRM0 * VTRM 1 * CELL_EXT_OS_AREA * OtherOS * Lv0ldr/Bootldr * Lv0ldr/Bootldr Corrupt Sequences * Lv0ldr/Bootldr Statistics/Entropy * Minimum Version * File Digest Keys * PerConsole Nonce * Corrupt Sequences * Repetition * Authenticiation IDs
Download
Application MD5: F874983FABA32EA520A4A06057A3691C
Changelog
- 1.02 - 09/06/2013 : bugfix for patcher (did not fix enough) + added some more MD5's (CFW)
- 1.01 - 28/05/2013 : bugfix for patcher (mistake from using old nor code)
- 1.00 - 27/05/2013 : first proper/public release (because I am lazy there will be no loader!)
Bugreport
1.01:
- Minver is not detected correct (on rare version) - it gives a warning, even when metldr/lv0ldr revision is correct and console was downgraded fine.
Warning
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!
Notes
As this is the first release, give extra care to each alert and use at your own risk! This program will only as good as the NOR validator after tedious updates ;)
Report any bugs or issues to [email protected] or directly to BwE @ irc.efnet.org #ps3downgrade or irc.ps3sanctuary.com #ps3hax
Give credit if you are using this for other people!
Made in Australia!
LT 4 AM <3
Nor Inspector
Another Tool for validating your NOR Dump is "Nor Inspector".
It will display most common information about your dump and the console.
How-to use
1) start
2) drag'n'drop your dump into the app
3) on errors check out status-tab
Features
Other Features:
* Drag'n'drop CoreOS / Revokation Package to replace * Hex-Region Viewer * Byte reverse dumps supported * Error Logging in Status-Tab (OK/ERR) "The Tab is green, the dump is clean!" ...
Download
Nor Inspector 0.0.1 (Requires .NET Framework 2.0)
Notes/Warning
If you do not validate your flash, and for some reason(s) the dump is invalid/bad, and you are rewriting to flash, you have no way of restoring the console hence making a perma-brick (unrecoverable brick).
Gallery
NorInspector - tab : General Information
NorInspector - tab : More Information
NorInspector - tab : Region Viewer
NorInspector - tab : Status
PS3 NOR/NAND Statistic (Beta)
Features
- NOR/NAND statistics
- NOR/NAND patching
- NOR/NAND byte swapping
- NOR/NAND infos
- NOR/NAND validation
- NOR/NAND extraction
- DATECODE check
How-to use
This tool works different than other validators. Instead of outputing 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 equal 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 definetly 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. :)
http://www.ps3hax.net/showthread.php?t=55019
Download
Notes/Warning
If you do not validate your flash, and for some reason(s) the dump is invalid/bad, and you are rewriting to flash, you have no way of restoring the console hence making a perma-brick (unrecoverable brick).
Gallery
PS3 NOR-NAND Statistic (Beta)
.jpg)
Known bad guides (with obvious faults in them that lead to permanent bricks)
E3 FLASHER INSTALLATION and DOWNGRADE TUTORIAL (Khalkedon)
- http://www.youtube.com/watch?v=WHNw2E4tU6c&t Do not use
What is wrong / could be better ?
- cutting knife VS plastic to remove the bolt protectors
- cellophane 3M tape in hot environment
- ribbon flat cable not at 90 degrees position
- no fixating of clip (coin/foam filler to keep the clip more pressed)
- no tristate wire soldered
- not checking clip connection, before closing console
- no repasting of RSX and CellBE
- not using torc moment screwdriver, but electric drill
- uneven pressure when mounting frontboard
- greasy fingerprints all over the motherboard (bonus fingerprint: under cellophane tape)
- dual sata adaptor is used (not recommended, as ps3 host does not support SATA Port Multiplier)
- E3 is ´wobbly´ because no cardboard filler was used to prevent movement (bracket design error)
- not using the 'Samsung' multiconsole update for E3 and no proper SHA1 identification of the correctness of file
- using 001000 for dumping, not using flashfun, thus risking busy flashbus on a multithreaded system
- not validate content of dumps, only size
- doing a restore (will permabrick console if clipped bad)
- when unpluging the power cord at 19:09, insuficient time to dischargue capacitors of power supply (a real reset needs more time)
- using e3_downgrader.bin (nicknamed e3_bricker for obvious reasons) instead of prepatching
- misnaming ¨2nd usb port¨ -> it's usb00000 because we count from right to left in ps3 (rightmost, closest to BD)
- no proper identification of lv2diag.self (there exist many!) and PS3UPDAT.PUP to be used (SHA1)
- after FSM reinstall, no boot to XMB to check it booting proper with FSM active
- not setting proper time, corrupting node database unneeded
- fix permission errors (archaic, not needed)
biggest error : not reading the (E3) downgrade guide on wiki
challenge: can you name another error?
Progskeets official downgrade guides
- http://www.progskeet.com/downloads/NOR_eng.pdf
- Only checks statistics, no validation at all
- http://www.progskeet.com/downloads/NAND_eng.pdf
- Checks statistics, Extracts dump but does not check its content, no validation.
- The use of Flowrebuilder, to make a unified dump from 2 NAND dumps is a bit strangely placed in the guide
Word of Warning
When using validators and bricking your console as result, there are only 2 people to blame :
- the one making the validator (for not properly validating, warning users and telling what is wrong and/or how it could be solved);
- the enduser for flying blind and getting lazy/dumb with it.