Seemed our chinese E3 friends took the news of many bricks (even unrecoverable with their brickguide by soldering a Tristate to SBE wire) with E3 seriously and released a dump checker tool:.....................
E3 Nor dump checker V1.0 released. It help you check if the backup bios is corret or wrong. We suggest user check the backup bios first before downgrade, it will lower the risk of brick !
That seemed a bit too optimistic, even when it doesn’t claim 100% validity, so I decided to test that program to a bricktest!
Inserted where several known faults in specific regions, that would be invalid for any flash (e.g. resulting in a RLOD or YLOD brick – even unrecoverable because also perconsolespecific data was overwritten!).
The results where posted on the wiki by me :
Quick bulletproof test
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.
If you like to give this checker a try, be adviced, it crashed about 50 times when I was testing (about every 2 checks) – not sure if it was my PC only.
