Currently the wiping (and reset) is done by wipe-in-place, calling clobber-state.
However, clobber-state may have many extra unexpected dependency and changes randomly.
Currently, clobber-state does these:
- ensure root account (we don't need)
- redirect logs (we don't need)
- preserve files (we need but this can be done in other ways)
- detect system config (mainly for NAND and rotational devices, but since no projects are going NAND/rotational maybe we can skip this)
- wipe stateful by dd (we can do this)
- create new file system (we have to clone this)
- mount and restore CRX cache (need to do this)
- tag developer mode flags (probably need)
- remove VPD keys (we can do this in factory)
Maybe we should just do the clobbering (since what we need is slightly different from what clobber-state usually needs) inside factory script, that may include:
- Stop using display_boot_message and other functions that needs fonts & graphics
- Invoke frecon only one time and use its OSC (Escape code) to display images if needed, or do pure text UI
- Also change cutoff scripts to take advantage of the frecon / text UI.
Comment 1 by hungte@chromium.org
, Jul 12 2017