FAFT: Support new GBB flags

The new GBB flag GBB_FLAG_FORCE_DEV_BOOT_FASTBOOT_FULL_CAP is new added.
It is default ON and FAFT should disable it at the beginning.

BUG=chromium:527484
TEST=Ran a FAFT test.

Change-Id: I12ab5ce61bf01e7045a46dc26da0c4c18fffa5a0
Reviewed-on: https://chromium-review.googlesource.com/295896
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Shelley Chen <shchen@chromium.org>
diff --git a/server/cros/faft/firmware_test.py b/server/cros/faft/firmware_test.py
index f10363c..399a199 100644
--- a/server/cros/faft/firmware_test.py
+++ b/server/cros/faft/firmware_test.py
@@ -737,7 +737,8 @@
         self.clear_set_gbb_flags(vboot.GBB_FLAG_DEV_SCREEN_SHORT_DELAY |
                                  vboot.GBB_FLAG_FORCE_DEV_SWITCH_ON |
                                  vboot.GBB_FLAG_FORCE_DEV_BOOT_USB |
-                                 vboot.GBB_FLAG_DISABLE_FW_ROLLBACK_CHECK,
+                                 vboot.GBB_FLAG_DISABLE_FW_ROLLBACK_CHECK |
+                                 vboot.GBB_FLAG_FORCE_DEV_BOOT_FASTBOOT_FULL_CAP,
                                  vboot.GBB_FLAG_ENTER_TRIGGERS_TONORM |
                                  vboot.GBB_FLAG_FAFT_KEY_OVERIDE)
         self.mark_setup_done('gbb_flags')