olef files
CLI v3.0.2View Markdown
Generated from Olef 3.0.2. All commands · Capabilities and requirements
These entries describe available commands, not a sequence to run. Check prerequisites before changing app, device, or cloud state. Global options are listed in the command catalog.
olef files
Section titled “olef files”On-device file operations
olef files --helpOutput: json.
olef files ls
Section titled “olef files ls”List a directory on the device
olef files ls --helpOutput: json.
| Argument | Description |
|---|---|
--app <APP> |
Resolve the path inside this debuggable app’s private data directory |
--run-as |
Access the path through Android run-as instead of shared/server storage |
<remote> |
Required. Device path. An absolute path is that path on the device (shared storage through the Olef server, anything else through adb as the shell user); a relative path is inside Olef’s own app storage. With –run-as, a path inside the app’s data directory |
--json |
Accepted for compatibility; output is always JSON. |
olef files push
Section titled “olef files push”Push a local file to the device
olef files push --helpOutput: json.
| Argument | Description |
|---|---|
--app <APP> |
Resolve the destination inside this debuggable app’s private data directory |
--run-as |
Access the destination through Android run-as |
<local> |
Required. |
<remote> |
Required. Device path. An absolute path is that path on the device (shared storage through the Olef server, anything else through adb as the shell user); a relative path is inside Olef’s own app storage. With –run-as, a path inside the app’s data directory |
--mode <MODE> |
Require Unix permission bits after the push (octal, e.g. 644). Omit on shared/FUSE storage where Android controls the effective mode |
--json |
Accepted for compatibility; output is always JSON. |
olef files pull
Section titled “olef files pull”Pull a device file to the host
olef files pull --helpOutput: json.
| Argument | Description |
|---|---|
--app <APP> |
Resolve the source inside this debuggable app’s private data directory |
--run-as |
Access the source through Android run-as |
<remote> |
Required. Device path. An absolute path is that path on the device (shared storage through the Olef server, anything else through adb as the shell user); a relative path is inside Olef’s own app storage. With –run-as, a path inside the app’s data directory |
<local> |
Required. |
--json |
Accepted for compatibility; output is always JSON. |