QUOTE(cory1492 @ May 29 2008, 09:22 AM)
![View Post](http://forums.xboxscene.org/public/style_images/master/snapback.png)
Basically what I get out of it too, is if you wanted to go from orig.bin directly to orig_hexd.bin one could "restore" it to that? Just wanted to know
which quirks of the whole thing was buggering the sense it should have made to me - thanks for the explanation. Thanks for "guinea-pigging" it and showing the rest of us too
![smile.gif](style_emoticons/default/smile.gif)
I've got good programmers, but that definitely doesn't add up to a good epoxy remover.
No, I wouldn't risk it, using restore would have the same/opposite problem. Flashing the hex'd sector first would mean the checksum would be wrong..... You just need to accept that changing any sectors with out the Master Checksum set will very likely lead to a bricked drive stuck in recovery mode.... Some sectors are not included in the checksum calculation, I don't have a list, but for instance the sector the Key is in doesn't appear to be included, as flashing the key does flash the checksum
If you just want a "stock" 79 that you can flash... just follow my steps from start to finish...
a. Dump the orig.bin
b. Smart hack (patch) it with the Passkey in place
c. Dump the modded
d. Hexedit it and flash (patch) it.
e. Remove passkey and test, should dump like a 78
f. Hexedit the Orig.bin
g. Open the orig.bin AND VALIDATE the checksum AND accept the changes
h. to be double sure close toolbox and open the hexd_orig again and VALIDATE checksum, it should return OK!
i. Flash this file (restore)
I have done this and I confirm it does work for me, at least!