Block reference / App Management

Backup

Copy one app, or every app you installed, from the phone to a folder on this computer.

Only inWarpX Phone

Backup copies an app off the run's phone into a folder on this computer: its APKs, its files in shared storage and, on a rooted phone, its private data — where its accounts and settings live. With The whole phone it does that for every app you installed. Restore puts a backup back, on the same phone or another.

Backup copies Shopee — its APKs, its files and, on a rooted phone, the signed-in account — to a folder on this computer.
The Backup block's settings, filled in as in the example below.

Settings

Back up

One app backs up the app named in Package. The whole phone — every installed app backs up every app you installed, each in its own folder; apps that came with the phone are left out.

ExampleOne app
Packagewhen Back up is One app

The app, by its package name, such as com.shopee.vn. As you type, the field suggests the apps on the phone picked in the editor's toolbar, the apps phone farms run most (typing zalo finds com.zing.zalo) and the packages the workflow already names; tick System apps in the list to include built-in ones. What you type is kept as typed, so a reference such as {{loopData.package}} works too.

Examplecom.shopee.vn
Folder on this computer

Where the backup goes. Empty, it goes to Downloads/phone-backups/<phone's serial>/<date>_<time>. A path that does not start at a drive is read under Downloads.

Example
Save the backup's folder to a variable

Also stores the backup's folder in a workflow variable, ready for a Restore block.

ExampleChecked
Variable namewhen Save the backup's folder to a variable is on

The variable to write. Later blocks read it as {{variables.shopeeBackup}}.

ExampleshopeeBackup
Delay (ms)

A pause after the block finishes, before the next block starts. Write one number such as 1000, or a range such as 1000,3000 to pick a random pause in that range on each run.

Example0

Every block also has the shared block settings — a description, Disable block and what to do on an error. Fields that take text accept data from earlier blocks.

What it hands on

Hands on the backup's folder as {{prevBlockData}}, and to the variable when ticked. Inside it, each app has a folder named by its package, holding apk (the base APK and any splits), external.tgz (its shared-storage files, when it has any), data.tgz (its private data, rooted phones only) and meta.json. Leaves by its single output.

Example: Back up a signed-in Shopee account

  1. Start
  2. Stop app
  3. Backup
Where Backup sits in the example workflow.
  1. Sign in to Shopee on a rooted phone, by hand or with the workflow's own blocks.
  2. Add a Stop app block for com.shopee.vn, so the app is not writing while it is copied.
  3. Add a Backup block, leave Back up on One app and pick Shopee in Package.
  4. Leave Folder on this computer empty, tick Save the backup's folder to a variable and name it shopeeBackup.
  5. Run the workflow; the backup lands under Downloads/phone-backups/, and the log shows its folder.

Good to know

  • An app's private data is copied only on a rooted phone (Magisk or a su the phone has). Without root the backup holds the app and its shared-storage files, and a restored app comes back installed but signed out.
  • Caches are left out; the app makes them again.
  • Photos, downloads and other files in the phone's own storage are not part of a backup; copy them with Transfer file.
  • With One app, an app that is not on the phone fails with APP_NOT_INSTALLED. With The whole phone, an app that fails is skipped and the rest are backed up; the folder also gets a device.json naming the phone's model and Android version.
  • One file of a backup may weigh at most 1.5 GB.
  • A workflow that was not edited on this computer (from the Appstore, a file or the assistant) asks you to allow this block before its first run, in a window that lists what it will do. Blocks you set up in the editor are approved as you edit them, so your own workflows never ask; changing the block's settings asks again. A backup copies apps off the phone, on a rooted phone with the accounts signed in to them, so it asks too.
  • There is no Device field: the block acts on the run's phone — the one picked in the editor's toolbar, or each phone ticked for Run automation in the Control Center or named in an API run.

See also

  • Restore — Put a backup made by Backup back on a phone.
  • Clear app data — Wipe everything an app stored on the phone, which signs it out.
  • Transfer file — Copy a file from this computer to the phone, or from the phone to this computer.