faft: Speed up by moving the GBB flag setup to FAFTSequence

We now check/change GBB flags only on the first test of the test suite.
Moving all the required GBB flag change in FAFTSequence can save time for
duplicate check/change.

BUG=chromium-os:34392
TEST=run_remote_tests.sh --board daisy --remote dut DevScreenTimeout \
     RollbackFirmware/control$

Change-Id: I8417e5e1c79a8e7b18fadf54ec75c736dfcdcafd
Reviewed-on: https://gerrit.chromium.org/gerrit/35940
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
diff --git a/server/cros/faftsequence.py b/server/cros/faftsequence.py
index ec7e36c..9cb9559 100644
--- a/server/cros/faftsequence.py
+++ b/server/cros/faftsequence.py
@@ -184,7 +184,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_FORCE_DEV_BOOT_USB |
+                                 vboot.GBB_FLAG_DISABLE_FW_ROLLBACK_CHECK,
                                  vboot.GBB_FLAG_ENTER_TRIGGERS_TONORM)
         if self._install_image_path:
             self.install_test_image(self._install_image_path,