Android Device Deprovisioning and Handover
Deprovisioning removes a device from management and, where the chosen method says so, removes company data. It is the opposite of first-time provisioning. Deleting a console record is not the same event as a completed wipe.
Diperbarui
Four methods, four different results
Google’s Wipe and deprovision a device page, last updated 2025-06-25 UTC and read for this guide on 2026-10-09, names four methods. This page does not add a fifth. It also does not claim that every AOSP build implements the Android Management API. The parent program context is managed and controlled Android devices. First-time setup stays on Android device provisioning methods.
| Method | What the cited page says | What it does not prove |
|---|---|---|
| WIPE | Factory-resets a company-owned device, or deletes the work profile on a personally owned device. The device record is deleted after the device confirms completion. | A command that has not been acknowledged is not a completed wipe. The page says the command can be tracked and cancelled until the device acknowledges it or it expires. |
| RELINQUISH_OWNERSHIP | Converts a company-owned, personally enabled device to personally owned. Deletes the work profile and the device record. Personal-profile data and apps are preserved, and PersonalUsagePolicies set by the EMM are removed. | This is not a factory reset, and it is not a promise that every controlled state keeps personal data. It applies to the company-owned, personally enabled case the page describes. |
| enterprises.devices.delete | Deletes the device record immediately and sends a wipe instruction. If the device stays offline for more than 30 days, the wipe instruction will not reach it and company data can remain. | Deleting the record does not guarantee that data is gone. The cited page recommends this method when data must be removed from Google servers on a deadline, not as a guaranteed device wipe. |
| enterprises.delete | For EMM-managed enterprises, deletes the enterprise record and the associated device records, with the same effect as delete on the devices in that enterprise. | This is an enterprise-level action. It is not a per-device handover record, and it does not by itself prove each handset completed a wipe. |
A deleted record is not a wiped device
After a WIPE command is confirmed, the cited page says the device record is deleted, later list calls omit it, and further calls with that device ID return 404. The device is no longer manageable and must be provisioned again to be managed. That sequence is confirmation after the device reports completion. enterprises.devices.delete removes the record first and only then sends a wipe instruction. An offline device can miss that instruction. Do not write “the EMM row is gone, so the data is gone.”
Handover evidence to keep
A handover packet names the method, the ownership state you believe the device is in, who may issue the command, and what you will accept as done. The cited page says wipeParams can describe how Factory Reset Protection data, external storage, and eSIMs are treated, and can carry a localized wipeReason for personally owned devices. This guide does not describe an account-lock bypass, and it does not treat a parameter name as permission to clear someone else’s account. Spare-parts and end-of-life planning stay on lifecycle management. They are not a substitute for this evidence.
- Ownership state you are assuming: company-owned, personally owned, or company-owned and personally enabled.
- Method you intend to use, copied from the four names above.
- Whether the device is expected to be online long enough to acknowledge a command.
- Who issues the command, and who records the result.
- What “done” means for this handset: confirmed wipe, work-profile removal with personal data kept, or a server-side delete with the wipe still unconfirmed.
What to send us
Send a redacted brief. We reply within 1 business day.
| Item | Why we need it | Example format |
|---|---|---|
| Ownership state | The method depends on it. A personally owned device and a company-owned device are not the same command. | Company-owned, or personally owned work profile. No user name. |
| Intended method | We need the method you want checked, not a request to invent one. | WIPE, RELINQUISH_OWNERSHIP, enterprises.devices.delete, or enterprises.delete. |
| Online expectation | An offline device can miss a wipe instruction after the record is deleted. | Expected online within the return window, or may stay offline. No serial list in the first note. |
| Done condition | Handover is accepted against a condition, not against a deleted row alone. | Device confirms WIPE, or work profile removed and personal data kept, or server delete only and wipe still open. |
| Command owner | Someone has to be allowed to issue the command and keep the record. | EMM admin role name. Do not send tokens, QR payloads, or account passwords. |
Send the brief
Use the project brief. We reply within 1 business day. The photos on this page are general device-handling scenes already published for provisioning validation and lifecycle. They are not photographs of a wipe, a customer return, or a test result.
Pertanyaan Umum
Does deleting the device in the EMM mean the data is gone?
No. On the cited Android Management API page, enterprises.devices.delete removes the record immediately and sends a wipe instruction. If the device stays offline for more than 30 days, that instruction does not arrive and company data can remain.
Does WIPE always factory-reset the handset?
No. The cited page says WIPE factory-resets company-owned devices and deletes the work profile on personally owned devices. The device record is deleted after the device confirms completion.
Will RELINQUISH_OWNERSHIP keep personal data?
The cited page says this command is for converting a company-owned, personally enabled device to personally owned. It deletes the work profile and preserves data and apps in the personal profile. It does not say that every controlled state keeps personal data.
Can this page clear Factory Reset Protection or an account lock?
No. The cited page says wipeParams can specify how Factory Reset Protection data is treated. That is not a bypass, and this guide does not provide one.
Ceritakan alur kerja dan aturan Anda.
Kami mengubah persyaratan menjadi perangkat yang siap diterapkan.