[roll] Roll fuchsia [recovery] Don't fall back to wiping Fxfs

Previously, if the request to wipe the data volume from fshost failed,
we would fall back to manually erasing the Fxfs partition by overwriting
the superblocks.  This was sensible when Fxfs just stored mutable data,
but now Fxfs also stores blobs, so this will brick the device.

Remove the fallback logic.  This required plumbing the fxfs_blob setting
from the build into the factory_reset component, so that we would know
whether the fshost failure should be bubbled up (if fxblob is enabled)
or to continue by trying to wipe zxcrypt (if disabled).

Note that this removes the fallback logic for the Fxfs-but-not-fxblob
case too.  I didn't think it was worth also supporting that case, but if
we felt that it was important enough, we could keep it.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/975104
Original-Revision: b040af26e2a44b133ae480ead1f6c57683069937
GitOrigin-RevId: 61374969b6321a054a5891239566dd1e144ffc66
Change-Id: Icfddc96918b178417b018e6ce536cd843b96ce88
1 file changed
tree: 7f3462e11b769123ef5b3ce55ebad6370c3fb40f
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.