Home | History | Annotate | Download | only in releasetools

Lines Matching refs:downgrade

25   --downgrade
28 "ota-downgrade=yes" will be set in the package metadata file. A data wipe
49 to an older one (based on timestamp comparison), by setting the downgrade
50 flag in the package metadata. This differs from --downgrade flag, as we
52 NOT an actual downgrade case, but two builds happen to be cut in a reverse
55 C -> B. Specifying --downgrade may not help since that would enforce a
59 now we consolidate the two cases (i.e. an actual downgrade, or a downgrade
60 based on timestamp) with the same "ota-downgrade=yes" flag, with the
210 OPTIONS.downgrade = False
884 # Assertions (e.g. downgrade check, device properties check).
1072 if OPTIONS.downgrade:
1075 "--downgrade or --override_timestamp specified but no downgrade "
1077 metadata["ota-downgrade"] = "yes"
1081 "Downgrade detected based on timestamp check: pre: %s, post: %s. "
1082 "Need to specify --override_timestamp OR --downgrade to allow "
1091 downgrade / data wipe based on the global options.
1135 # Use the actual post-timestamp, even for a downgrade case.
1138 # Detect downgrades and set up downgrade flags accordingly.
1824 # For downgrade OTAs, we prefer to use the update-binary in the source
1826 if OPTIONS.downgrade:
2033 if OPTIONS.downgrade:
2113 elif o == "--downgrade":
2114 OPTIONS.downgrade = True
2117 OPTIONS.downgrade = True
2178 "downgrade",
2208 if OPTIONS.downgrade: