Device Environment Refresh Workflow

Device environment refresh clears app data or ROM state on a physical node — the hardware equivalent of returning a slot to a clean baseline. **When teams use it:** - QA labs rotating test matrices on the same hardware pool - Agencies handing devices between client projects - ROM paths that support factory reset without full re-cabling **Steps (typical):** 1. Export any logs or assets you need from the slot 2. Run factory reset or ROM refresh per your quoted stack 3. Re-authorize USB debugging or device trust if required 4. Re-bind network routes or proxy groups for the next workflow 5. Label the slot in batch-control software **Hardware notes:** Stable USB during refresh; adequate cooling if running parallel refreshes across groups. Network IP or proxy binding is buyer-managed — refresh the device layer first, then update routes in your proxy or router plan. **Caution:** We document hardware workflows only — platform terms of service are buyer compliance scope.