Editing Validating flash dumps
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
<div style="float:right">[[File:Dumpchecker.png|200px|thumb|left|Dumpchecker]]</div> | [[Category:Hardware]][[Category:Software]]<div style="float:right">[[File:Dumpchecker.png|200px|thumb|left|Dumpchecker]]</div> | ||
= Why so important? = | = 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.''' | Whenever you want to mess with flash (NAND or NOR), you have to '''make sure you are getting 100% correct, valid, verified dumps.''' | ||
{{warning|content=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 <span style="color:red | {{warning|content=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 <span style="background-color:white; color:red;">no way of restoring</span> the console hence making a perma-brick (unrecoverable brick). | ||
}} | }} | ||
So what can we use to prevent that, and make sure our dumps are as proper as we can check? | So what can we use to prevent that, and make sure our dumps are as proper as we can check? | ||
= Flowrebuilder = | = Flowrebuilder = | ||
| Line 178: | Line 12: | ||
== Links to versions == | == Links to versions == | ||
http://www. | http://www.ps3devwiki.com/files/flash/Tools/Flowrebuilder/ | ||
4.2.3.0 changelog | |||
----------------- | |||
added support to manage NAND preloader dumps | added support to manage NAND preloader dumps | ||
message user about the type of dump | message user about the type of dump | ||
| Line 206: | Line 21: | ||
auto-recognize if dump is normal or byte swapped and automanage them | auto-recognize if dump is normal or byte swapped and automanage them | ||
* [http://www. | * [http://www.ps3devwiki.com/files/flash/Tools/Flowrebuilder/FlowRebuilder%20v.4.2.3.0.exe FlowRebuilder v.4.2.3.0.exe (367 KB)] // [http://www.mirrorcreator.com/files/1HWLWYIY/FlowRebuilder_v.4.2.3.0.exe_links mirror] [http://www.mirrorcreator.com/files/1NYWARZT/FlowRebuilder_v.4.2.3.0.exe_links mirror2] | ||
* [http://www. | * [http://www.ps3devwiki.com/files/flash/Tools/Flowrebuilder/FlowRebuilder%20v.4.2.2.0.exe FlowRebuilder v.4.2.2.0.exe (389 KB)] // [http://www.mirrorcreator.com/files/7G5JLEK9/FlowRebuilder_v.4.2.2.0.exe_links mirror] [http://www.multiupload.nl/0ND4D0QW9Q mirror 2] [http://www.mirrorcreator.com/files/TJKTQQWB/FlowRebuilder_v.4.2.2.0.exe_links mirrors] | ||
* [http://www. | * [http://www.ps3devwiki.com/files/flash/Tools/Flowrebuilder/FlowRebuilder%20v.4.2.1.2.exe FlowRebuilder v.4.2.1.2.exe (313.50 KB)] // [http://www.mirrorcreator.com/files/08SGK09K/FlowRebuilder_v.4.2.1.2.exe_links mirror] | ||
* [http://www. | * [http://www.ps3devwiki.com/files/flash/Tools/Flowrebuilder/FlowRebuilder%20v.4.2.1.1.exe FlowRebuilder v.4.2.1.1.exe (473.57 KB)] // [http://www.mirrorcreator.com/files/GUUUKNWE/FlowRebuilder_v.4.2.1.1.exe_links mirror] | ||
* [http://www. | * [http://www.ps3devwiki.com/files/flash/Tools/Flowrebuilder/FlowRebuilder%20v.4.2.0.1.exe FlowRebuilder v.4.2.0.1.exe (474.01 KB)] // [http://www.mirrorcreator.com/files/C4U1C3OO/FlowRebuilder_v.4.2.0.1.exe_links mirror] | ||
* [http://www. | * [http://www.ps3devwiki.com/files/flash/Tools/Flowrebuilder/FlowRebuilder+v.4.1.3.2.exe FlowRebuilder v.4.1.3.2.exe (459.95 KB)] // [http://www.mirrorcreator.com/files/1UEPOIHX/FlowRebuilder_v.4.1.3.2.exe_links mirror] | ||
* [http://www. | * [http://www.ps3devwiki.com/files/flash/Tools/Flowrebuilder/FlowRebuilder%20v.4.1.0.0.exe FlowRebuilder v.4.1.0.0.exe (454.85 KB)] // [http://www.mirrorcreator.com/files/EC2ZFONW/FlowRebuilder_v.4.1.0.0.exe_links mirror] (don't use, for historic reasons listed) | ||
==Flowrebuilder options== | ==Flowrebuilder options== | ||
| Line 233: | Line 47: | ||
<div style="float:right">[[File:Nand-extract-noerror.png|200px|thumb|left|Flowrebuilder extraction no error]]<br />[[File:Nand-extract-error2.png|200px|thumb|left|Flowrebuilder extraction error]]</div> | <div style="float:right">[[File:Nand-extract-noerror.png|200px|thumb|left|Flowrebuilder extraction no error]]<br />[[File:Nand-extract-error2.png|200px|thumb|left|Flowrebuilder extraction error]]</div> | ||
<span style="color:red | <span style="background-color:white; color:red;">(make sure they are all there, flowrebuilder will not give warning when it fails!)</span>: | ||
* bootloader_0 | * bootloader_0 | ||
* bootloader_1 (NAND only) | * bootloader_1 (NAND only) | ||
| Line 255: | Line 69: | ||
== From unified to seperate low/high NAND files == | == 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 <abbr title="unscrambled then interleaved 2 NAND to unified dump">unified</abbr>, you need donor files to regenerate them. | If for some reason you lose the original seperate low/high NAND files and only have the <abbr title="unscrambled then interleaved 2 NAND to unified dump">unified</abbr>, you need donor files to regenerate them. | ||
* [ | * [http://www.ps3devwiki.com/files/flash/dumps/NAND0-1.rar NAND0-1.rar] [http://www.mirrorcreator.com/files/LTVIJEAK/NAND0-1.rar_links mirror] | ||
extract and in Flowrebuilder select the option "RE-SCRAMBLE a modified dump then de-interleave it into two new flashes" | 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 0" (TOP) file : here drop the 1bkp.bin | ||
| Line 275: | Line 89: | ||
=== How? === | === How? === | ||
1 - Place your .bin/s in the same folder as the validator.<br> | 1 - Place your .bin/s in the same folder as the validator.<br> | ||
2 - Run the validator | 2 - Run the validator and press Start.<br> | ||
3 - A console will appear asking you to select your dump (if you have more than one in the folder).<br> | 3 - A console will appear asking you to select your dump (if you have more than one in the folder).<br> | ||
4 - Make your selection and/or select if you want to patch it (either in its current byte orientation or the opposite).<br> | 4 - Make your selection and/or select if you want to patch it (either in its current byte orientation or the opposite).<br> | ||
| Line 286: | Line 100: | ||
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. | 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 | 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 | 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. | 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 === | === 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 === | === Download === | ||
BwE NOR Validator v1.31 | [http://betterwayelectronics.com/files/BwE_NOR_Validator.rar BwE NOR Validator v1.31] | ||
Application MD5: 28F0CD55255FE60E3F6D8AF90698440C<br> | |||
==== Changelog ==== | ==== Changelog ==== | ||
* 1.31 - 27/05/2013 : added eid4 + fixed bug in entropy (note: possibly final version, unless adding firmware revisions/new consoles) | * 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.30 - 21/05/2013 : completely rewritten eid, cisd, ccsd + added more validations to it, upgraded other minor validations. all due to upcoming nand validator | ||
| Line 381: | Line 191: | ||
There are almost infinite variations of each dump! Have fun and good luck! <br> | There are almost infinite variations of each dump! Have fun and good luck! <br> | ||
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 <span style="color:red | 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 <span style="background-color:white; color:red;">no way of restoring</span> the console hence making a perma-brick (unrecoverable brick).}}<br /><br /><br /><br /><br /><br /> | ||
| Line 403: | Line 213: | ||
File:Screenshot.jpg | File:Screenshot.jpg | ||
File:Sshot-147.jpg | File:Sshot-147.jpg | ||
</gallery> | </gallery> | ||
| Line 429: | Line 237: | ||
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. | 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 | 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). | 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). | ||
| Line 436: | Line 244: | ||
=== Areas Of Validation === | === 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 === | === Download === | ||
[http://betterwayelectronics.com/files/BwE_NAND_Validator.rar BwE NAND Validator v1.02] | |||
Application MD5: F874983FABA32EA520A4A06057A3691C<br> | Application MD5: F874983FABA32EA520A4A06057A3691C<br> | ||
| Line 499: | Line 304: | ||
=== Warning === | === Warning === | ||
{{warning|content=Using this program is [[NOT]] a 100% way of validating your dumps (because ''nothing'' is), but it is a good way of quickly seeing if it is worth checking further. This program will NOT | {{warning|content=Using this program is [[NOT]] a 100% way of validating your dumps (because ''nothing'' is), but it is a good way of quickly seeing if it is worth checking further. This program will NOT work with NAND and will not check anything other than what is stated. ALWAYS CHECK MANUALLY! | ||
Use at own risk! Valid dumps may be invalid - Invalid dumps may be valid. <br> | Use at own risk! Valid dumps may be invalid - Invalid dumps may be valid. <br> | ||
There are almost infinite variations of each dump! Have fun and good luck! <br> | There are almost infinite variations of each dump! Have fun and good luck! <br> | ||
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 <span style="color:red | 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 <span style="background-color:white; color:red;">no way of restoring</span> the console hence making a perma-brick (unrecoverable brick).}}<br /><br /><br /><br /><br /><br /> | ||
=== Notes === | === Notes === | ||
| Line 542: | Line 348: | ||
=== Notes/Warning === | === Notes/Warning === | ||
{{warning|content=Using this program is [[NOT]] a 100% way of validating your dumps (because ''nothing'' is), but it is a good way of quickly seeing if it is worth checking further. This program will NOT work with NAND and will not check anything other than what is stated. ALWAYS CHECK MANUALLY!<br /><br /> | {{warning|content=Using this program is [[NOT]] a 100% way of validating your dumps (because ''nothing'' is), but it is a good way of quickly seeing if it is worth checking further. This program will NOT work with NAND and will not check anything other than what is stated. ALWAYS CHECK MANUALLY!<br /><br /> | ||
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 <span style="color:red | 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 <span style="background-color:white; color:red;">no way of restoring</span> the console hence making a perma-brick (unrecoverable brick). | ||
}} | }} | ||
| Line 554: | Line 360: | ||
= PS3 NOR/NAND Statistic = | = PS3 NOR/NAND Statistic (Beta) = | ||
=== Features === | === Features === | ||
| Line 573: | Line 379: | ||
ckp_management_ID values have to be equal as well as per_console_nonce. (should be stated in error.log if not) | 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 | 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 | 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 | 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 | 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%. | As long as it is not possible to decrypt the full dump, it`s impossible to validate it to 100%. | ||
| Line 587: | Line 393: | ||
=== Download === | === Download === | ||
* http://rghost.net/45369360 | * http://rghost.net/45369360 | ||
* http://temp-share.com/show/FHKdyGTU6 | * http://temp-share.com/show/FHKdyGTU6 | ||
=== Notes/Warning === | === Notes/Warning === | ||
{{warning|content=Using this program is [[NOT]] a 100% way of validating your dumps (because ''nothing'' is), but it is a good way of quickly seeing if it is worth checking further. This program will not check anything other than what is stated. ALWAYS CHECK MANUALLY!<br><br /><br /> | {{warning|content=Using this program is [[NOT]] a 100% way of validating your dumps (because ''nothing'' is), but it is a good way of quickly seeing if it is worth checking further. This program will not check anything other than what is stated. ALWAYS CHECK MANUALLY!<br><br /><br /> | ||
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 <span style="color:red | 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 <span style="background-color:white; color:red;">no way of restoring</span> the console hence making a perma-brick (unrecoverable brick). | ||
}} | }} | ||
| Line 599: | Line 405: | ||
<gallery> | <gallery> | ||
File:PS3 NOR-NAND Statistic (Beta).jpg|PS3 NOR-NAND Statistic (Beta) | File:PS3 NOR-NAND Statistic (Beta).jpg|PS3 NOR-NAND Statistic (Beta) | ||
</gallery> | </gallery> | ||
| Line 668: | Line 455: | ||
* the one making the validator (for not properly validating, warning users and telling ''what'' is wrong and/or ''how'' it could be solved); | * 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. | * the enduser for flying blind and getting lazy/dumb with it. | ||