my bad there, was thinking it tho..cech2004a being your console..
ok..right..u have 3 dumps there, the second in the backup folder is a bad dump, missing per console info(alot) and if no way of recovering a full dump with the per console data of your cech2004a there's no way of fixing it..only if there's missing other info or with the help from another(bad)dump but with more/other per console info intact, so u must be very lucky to have this scenario
it's clear now..i guess..u have 3 dumps there and used a dump from Pro.hack?
if that file is the same as i have here, check the MD5 =
MD5: 9d47f1c1f94384c388d8553ac9ec9d42...then u bricked it by using it as it's that one i posted previous from the wiki metldr/unhackable
btw did u reclip the e3clip between dump/restoring? cuse if the second one = bad cech2004a dump is your first one made, that's for sure a bad clip connection, the other 2(good) ones so to speak have everything intact but it's not from cech2004a and i think other per console info also, the metldr file is complete on all 3 dumps, the second being ur original cech2004a dump, first one made = bad?
if u then reclipped e3 and then instead flashed back the prohack dump with good e3clip connection this time, u may be screwed? as it's overwritten with other data, it must be? cuse those 2 dumps are complete = good e3 connection, very unlucky u are i think?
i may be totally wrong here, its a mess tho
could u do something, redump the bios and post it here
and for bytereversing...only if u work with Progskeet etc.. u'l need this option
for E3, after installing,dumping the bkpps3.bin, only for verifying/wiki/values it u must byte reverse it so it reads ifi like "what" in ur example
then if u sure it's correct u ALWAYS flash the original bkpps3.bin u made, not the swapped dumps, and if u use the manual E3 patches instead of "e3_downgrade.bin" it's the same thing, use the original bkpps3.bin u made with E3
restoring/flashing back a "byte reversed" e3 dump(fii/thaw) isn't gonna work, again use the original file