faft: Change the pad of VBLOCK to 0
The packing utility during build uses 0 as the pad of VBLOCK. Making FAFT
the same pad saves unnecessary restoring of firmware.
BUG=chrome-os-partner:16678
TEST=run RollbackFirmware and RONormalBoot, see the resulted VBLOCK as before
Change-Id: I1e9d58495560951242ec54bb0e6333ac5771d1d8
Reviewed-on: https://gerrit.chromium.org/gerrit/39831
Reviewed-by: Vic Yang <victoryang@chromium.org>
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
diff --git a/client/cros/saft/flashrom_handler.py b/client/cros/saft/flashrom_handler.py
index f140157..0b64065 100644
--- a/client/cros/saft/flashrom_handler.py
+++ b/client/cros/saft/flashrom_handler.py
@@ -553,7 +553,7 @@
# Pad the new signature.
new_sig = open(sig_name, 'a')
- pad = ('%c' % 0xff) * (sig_size - os.path.getsize(sig_name))
+ pad = ('%c' % 0) * (sig_size - os.path.getsize(sig_name))
new_sig.write(pad)
new_sig.close()