summaryrefslogtreecommitdiff
path: root/recovery.wipe.common
diff options
context:
space:
mode:
authorTianjie Xu <xunchang@google.com>2016-06-29 17:24:51 -0700
committerTianjie Xu <xunchang@google.com>2016-06-30 10:47:11 -0700
commitcdaeb15bf693f9c449c479252d543013d2a720e0 (patch)
tree2e45001afea6bd83f02512ac59bed3191477ca28 /recovery.wipe.common
parent90c635d927091e272c2a8650aa427fcbad40b87b (diff)
Reorder the wipe_ab partition list
Currently boot_a and boot_b are erased first when wiping a device with "--wipe_ab" option. As a result, a force reboot during the wiping process may end up with an unbootable device that has its userdata unwiped. Move the boot partition down the list so that the device could start over the wiping process after the force reboot. Change-Id: I14c767de79fc1a40cf984f828bacf56cfbac3e5a Test: Boot a sailfish into recovery with "--wipe_ab"; force reboot during erasing animation; and the erasing starts over. Bug: 29833989
Diffstat (limited to 'recovery.wipe.common')
-rw-r--r--recovery.wipe.common6
1 files changed, 4 insertions, 2 deletions
diff --git a/recovery.wipe.common b/recovery.wipe.common
index b27572bc..f6347130 100644
--- a/recovery.wipe.common
+++ b/recovery.wipe.common
@@ -1,8 +1,10 @@
# All the partitions to be bricked (in order) under recovery.
-/dev/block/bootdevice/by-name/boot_a
-/dev/block/bootdevice/by-name/boot_b
/dev/block/bootdevice/by-name/system_a
/dev/block/bootdevice/by-name/system_b
/dev/block/bootdevice/by-name/vendor_a
/dev/block/bootdevice/by-name/vendor_b
/dev/block/bootdevice/by-name/userdata
+# Wipe the boot partitions last so that all partitions will be wiped
+# correctly even if the wiping process gets interrupted by a force boot.
+/dev/block/bootdevice/by-name/boot_a
+/dev/block/bootdevice/by-name/boot_b