Block reference / App Management
Restore
Put a backup made by Backup back on a phone.
Only in
WarpX Phone
Restore takes a folder made by Backup and puts it on the run's phone: each app is installed from its APKs, its shared-storage files go back, and on a rooted phone its private data replaces what the app holds there. Point it at one app's folder, or at a whole backup to restore every app in it. The phone need not be the one the backup came from.
Settings
- Backup folder
The folder to restore: one app's folder (it holds
meta.json), or a backup's folder with an app folder inside for each app. A path that does not start at a drive is read under Downloads, for examplephone-backups/R5CT119ZF7D/2026-10-12_16-05.Example{{variables.shopeeBackup}}- Delay (ms)
A pause after the block finishes, before the next block starts. Write one number such as
1000, or a range such as1000,3000to 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 one entry per app as {{prevBlockData}}: its package, whether it was installed, and what became of its external files and private data — restored, none, skipped: needs root, or the reason it failed. An app that could not be restored at all is listed with its folder and error. Leaves by its single output.
Example: Move a signed-in Shopee account to another phone
- Start
- Restore
- Start app
- Back the account up on the first phone with a Backup block that saves its folder to
shopeeBackup. - Pick the second phone, also rooted, in the editor's toolbar, or run the next part from the Control Center on it.
- Add a Restore block with Backup folder set to the backup's folder, for example
{{variables.shopeeBackup}}or the path the first run logged. - Add a Start app block for
com.shopee.vn; it opens signed in to the same account.
Good to know
- Private data goes back only on a rooted phone, and replaces the app's own. Without root that part reads
skipped: needs rootand the app is installed signed out. - The app is force-stopped while its files are put back, and its private data is handed to the app as installed on this phone.
- Android does not install an older version over a newer one, so an app the phone has in a newer version than the backup's fails to restore and is listed with the reason.
- The block fails only when no app came back. When some did, check
{{prevBlockData}}or the log for the ones that did not. - 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.
- 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
- Backup — Copy one app, or every app you installed, from the phone to a folder on this computer.
- Install app — Install an app from an .apk on this computer, from the APK library, or from Google Play.
- Start app — Open an app by its package, installing it first if the phone has not got it.