Disable lost mode

Tool Name: airdroid_business_disable_lost_mode

Risk Level: 🟠 Medium Risk

Execution Mode: ⏳ Asynchronous

Category: Remote Commands

Quick Start (Copy & Use)

One-liner: Disable lost mode on a device — unlocks the screen and removes the lost mode message

What you need: DeviceId (device ID)

Success criteria: StatusCode = 200 and ErrorMessage is an empty string; returns Pid for tracking

What to do next: Use Get an Activity Log with the Pid to poll execution status

Minimal request example:

{
  "DeviceId": "fa6edcff65ab444e8b5e0eb08df4175d"
}

Minimal response example:

{
  "Pid": "1770854462319857000",
  "StatusCode": 200,
  "ErrorMessage": ""
}

Recipes (Common Recipes)

Recipe 1: Disable lost mode after device recovery

Scenario: The lost device has been recovered; restore normal usage

{
  "DeviceId": "fa6edcff65ab444e8b5e0eb08df4175d"
}

Recipe 2: Cancel accidental lost mode activation

Scenario: Lost mode was enabled by mistake; needs to be cancelled immediately

{
  "DeviceId": "abc123def456"
}

Recipe 3: Track disable status with Pid

Scenario: After disabling lost mode, confirm whether the operation succeeded

1. Call Disable Lost Mode to get the Pid
2. Use the Get an Activity Log tool to query status:

{
  "Pid": "1770854462319857000"
}

Polling logic:

• Progress = "Executing" → continue polling (interval 5 seconds)
• Progress = "Success" → disable succeeded
• Progress = "Failure" → check the FailReason field

1. Overview

1.1 Description

Disable lost mode on a device managed by AirDroid Business. The device screen will be unlocked, the lost mode message will be removed, and the device will return to its normal operating state.

1.2 When to Use

• Device recovery: The lost device has been recovered; restore normal usage
• Accidental activation recovery: Lost mode was enabled by mistake; needs cancellation
• Temporary lockdown ended: Temporary protection is over; restore device usage

1.3 Execution Mode & Response

This operation is asynchronous — after the command is sent, the device typically responds within seconds.

• Return value: Pid (activity log ID)
• Tracking method: Use the Get an Activity Log tool with the Pid to query execution status
• Prerequisite: The device must be online to receive the command
• Typical duration: Usually completes within 2-5 seconds

1.4 Prerequisites

1.5 Prerequisite Tools

1.6 Comparison with Similar Tools

2. Inputs

2.1 Parameter List

2.2 Parameter Details

`DeviceId`

Device unique identifier.

• Type: string
• Format: Non-empty string
• Source:
  1. Obtained via the Get All Devices tool; use the device_id field from the response
  2. Obtained via the Get a Device by Name tool for exact name lookup
• How to fill in a GI node:
  • Constant: Enter the device ID string directly, e.g. fa6edcff65ab444e8b5e0eb08df4175d
  • Upstream reference: Map from the Get All Devices node's Devices[0].device_id field
• Example:

  "fa6edcff65ab444e8b5e0eb08df4175d"

2.3 Parameter Combination Logic

• Only one required parameter: DeviceId
• Simple operation; no additional confirmation parameters needed

3. Outputs

3.1 Response Examples

Success response:

{
  "Pid": "1770854462319857000",
  "StatusCode": 200,
  "ErrorMessage": ""
}

Parameter error response:

{
  "Pid": "",
  "StatusCode": -1,
  "ErrorMessage": "device_id is required. Obtain via 'Get All Devices' or 'Get A Device By Name' tool."
}

Network error response:

{
  "Pid": "",
  "StatusCode": 500,
  "ErrorMessage": "Request timeout after 60 seconds."
}

3.2 Field Descriptions

3.3 Pid Tracking

Use the returned Pid with the Get an Activity Log tool to track execution status:

4. Examples

4.1 Basic Example: Disable lost mode

Request:

{
  "DeviceId": "fa6edcff65ab444e8b5e0eb08df4175d"
}

Response:

{
  "Pid": "789012",
  "StatusCode": 200,
  "ErrorMessage": ""
}

4.2 Advanced Example: Disable and confirm status

Step 1: Call disable lost mode

{
  "DeviceId": "fa6edcff65ab444e8b5e0eb08df4175d"
}

Step 2: Use the returned Pid to query the activity log

{
  "Pid": "789012"
}

Step 3: Use Get All Devices to confirm device status

{
  "DeviceIds": ["fa6edcff65ab444e8b5e0eb08df4175d"],
  "SelectedColumns": ["device_id", "device_name", "lost_mode_status"]
}

4.3 Error Example: Empty device ID

Request:

{
  "DeviceId": ""
}

Response:

{
  "Pid": "",
  "StatusCode": -1,
  "ErrorMessage": "device_id is required. Obtain via 'Get All Devices' or 'Get A Device By Name' tool."
}

5. Error Handling

5.1 AB Three-Layer Error Codes

Core principle: AB uses a three-layer error code strategy. The agent should decide how to handle based on StatusCode.

5.2 Common Errors

5.3 Agent Self-Healing Decision Table

6. Best Practices

6.1 Performance Tips

• Confirm device is online: Check device status before the operation
• Confirm device is in lost mode: Although calling on a non-lost-mode device also returns success, it is recommended to confirm first

6.2 Security Considerations

🟢 Low Risk: This operation only disables lost mode and restores the device to normal state.

Side effects:

• Screen is unlocked
• Lost mode message is removed
• Location tracking stops

Operation notes:

• Calling this on a device not in lost mode returns success with no side effects
• Confirm the device has been safely recovered before disabling lost mode

6.3 Idempotency

Idempotency: Naturally idempotent.

• Calling this on a device not in lost mode returns success with no side effects
• Multiple calls produce the same result; safe to retry

6.4 Async Operation Tracking

Use the returned Pid with Get an Activity Log to track execution status:

Polling recommendations:

• Interval: 5 seconds
• Max polling attempts: 6 (approx. 30 seconds)
• On timeout: Prompt the user to manually check device status

7. Related Tools

7.1 Prerequisite Tools

7.2 Follow-up Tools

7.3 Similar Tools Comparison

8. Tool Chains

8.1 Device Recovery Complete Flow

Scenario: Device has been recovered; restore normal usage

Tool chain:

Disable Lost Mode → Get an Activity Log → Get All Devices (confirm status)

Steps:

1. Call Disable Lost Mode to disable lost mode
2. Use Get an Activity Log with the Pid to confirm the operation succeeded
3. Call Get All Devices to confirm the device has exited lost mode

8.2 Lost Mode Full Lifecycle

Scenario: Complete flow from device loss to recovery

Tool chain:

Enable Lost Mode → (device recovered) → Disable Lost Mode

Steps:

1. When the device is lost, call Enable Lost Mode to activate lost mode
2. After recovery, call Disable Lost Mode to deactivate lost mode

8.3 Batch Recovery Pattern

Scenario: Batch disable lost mode on multiple devices

Tool chain:

Get All Devices (filter lost mode devices) → [Loop] Disable Lost Mode → Get an Activity Log

Steps:

1. Call Get All Devices with Keyword={"lost_mode_status":"In lost mode"} to get the list of devices in lost mode
2. Iterate through devices and call Disable Lost Mode for each
3. Collect all Pid values and use Get an Activity Log to batch-track status