E3 Nor dump checker: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (Text replacement - "!important!important" to "!important") |
||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== E3 Nor dump checker == | == E3 Nor dump checker == | ||
{| border="1" cellspacing="0" cellpadding="5" border="#999" class="wikitable" style="border:1px solid #999; border-collapse: collapse;" | {| border="1" cellspacing="0" cellpadding="5" border="#999" class="wikitable" style="border:1px solid #999; border-collapse: collapse;" | ||
|- | |- | ||
! style="background-color:red;" | <span style="background-color:lightred; color:white; font-size:200%; ">Warning</span> | ! style="background-color:red!important;" | <span style="background-color:lightred; color:white; font-size:200%; ">Warning</span> | ||
|- | |- | ||
| <span style="white; color:red!important; font-size:150%; text-align:center; ">This tool is known and proven to give false positives on bad dumps that lead to permabricks. | |||
Use this method: [[Validating flash dumps]] to make sure the dumps are in crisp condition. | Use this method: [[Validating flash dumps]] to make sure the dumps are in crisp condition. | ||
| Line 47: | Line 46: | ||
Conclusion : '''USELESS''', brickdumps will still show as 'valid'. <br /> | Conclusion : '''USELESS''', brickdumps will still show as 'valid'. <br /> | ||
'''[[Recommendation: use]]<span style="white; color:red;"> [http:// | '''[[Recommendation: use]]<span style="white; color:red!important;"> [https://web.archive.org/web/*/http://ps3devwiki.com/files/flash/Tools/Flowrebuilder/ Flowrebuilder] instead and common sense like mentioned on [[Hardware_flashing#Generic_Warning|Hardware flashing]] page.''' | ||
==== Added 22 nov 2011 ==== | ==== Added 22 nov 2011 ==== | ||
| Line 53: | Line 52: | ||
We suggest user verify those bios with E3 Nor dump checker, to assure the backup bios is no erro.'' | We suggest user verify those bios with E3 Nor dump checker, to assure the backup bios is no erro.'' | ||
'''[[Conclusion:]]<span style="white; color:red;"> Anyone with a flasher (should) know that you can dump it 1 to 1000's times the same bad. Comparing CRC/MD5/SHA1 is not any secure way to validate flash (as mentioned on [[Hardware_flashing#Generic_Warning|Hardware flashing]]). Letting the dumper do it x times, only gives endusers/customers a false sense of reassurance, always a bad idea.''' | '''[[Conclusion:]]<span style="white; color:red!important;"> Anyone with a flasher (should) know that you can dump it 1 to 1000's times the same bad. Comparing CRC/MD5/SHA1 is not any secure way to validate flash (as mentioned on [[Hardware_flashing#Generic_Warning|Hardware flashing]]). Letting the dumper do it x times, only gives endusers/customers a false sense of reassurance, always a bad idea.''' | ||
{{Hardware Flashers}}<noinclude>[[Category:Main]]</noinclude> | |||
Latest revision as of 05:19, 1 July 2023
E3 Nor dump checker[edit | edit source]
| Warning |
|---|
| This tool is known and proven to give false positives on bad dumps that lead to permabricks.
Use this method: Validating flash dumps to make sure the dumps are in crisp condition. You cannot recover from bad flash without proper dumps (e.g. bricking the console beyond repair). |
E3 Nor Dump Checker V1.0.exe (521.7 KB)
Article: http://www.ps3hax.net/2011/11/released-e3-nor-dump-checker-v1-0-released-tested/
Quick bulletproof test[edit | edit source]
does not test:
- bootldr (corrupted binary not detected)
- metldr (corrupted binary not detected)
- bootldr size (both under- and oversize not detected)
- metldr size (both under- and oversize not detected)
- cISD (didn't catch brick-byte error)
- cCSD (didn't catch brick-byte error)
- trvk_prg0 (didn't catch brick-byte error)
- trvk_prg1 (didn't catch brick-byte error)
- trvk_pkg0 (didn't catch brick-byte error)
- trvk_pkg1 (didn't catch brick-byte error)
- eEID (didn't catch brick-byte error)
- cvtrm (didn't catch brick-byte error)
- CELL_EXTNOR_AREA (didn't catch brick-byte error)
partly test:
- ROS0 (but didn't catch brick-byte error)
- ROS1 (but didn't catch brick-byte error)
does test:
- headerprefix ("00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00")
- header ("00 00 00 00 AC 0F FF E0 00 00 00 00 AD DE EF BE")
- header ("FI.I")
- headersuffix "(FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF")
- filetable ("saceru_eoldare.." etc.)
Conclusion : USELESS, brickdumps will still show as 'valid'.
Recommendation: use Flowrebuilder instead and common sense like mentioned on Hardware flashing page.
Added 22 nov 2011[edit | edit source]
New E3 flasher update released, it will backup bios 3 times automatically. We suggest user verify those bios with E3 Nor dump checker, to assure the backup bios is no erro.
Conclusion: Anyone with a flasher (should) know that you can dump it 1 to 1000's times the same bad. Comparing CRC/MD5/SHA1 is not any secure way to validate flash (as mentioned on Hardware flashing). Letting the dumper do it x times, only gives endusers/customers a false sense of reassurance, always a bad idea.
| ||||||||||||||||||||||||||||||||||||||
