Magisk

https://topjohnwu.github.io/Magisk
Admin
Magisk is an open-source suite of tools for Android root management, systemless modifications, and...
Tokens:20,212
Snippets:218
Trust Score:8.3
Update:1 month ago
Show doc for...
Tokens:
Raw
### Custom .rc Script Example with ${MAGISKTMP}

Source: https://topjohnwu.github.io/Magisk/guides.html

An example of a custom `*.rc` script used with Magisk's overlay system. It demonstrates using `${MAGISKTMP}` to reference files placed in Magisk's temporary filesystem, such as kernel modules and custom scripts.

```shell
# Use ${MAGISKTMP} to refer to Magisk's tmpfs directory

on early-init
    setprop sys.example.foo bar
    insmod ${MAGISKTMP}/libfoo.ko
    start myservice

service myservice ${MAGISKTMP}/myscript.sh
    oneshot


```

--------------------------------

### Download NDK with Build Script

Source: https://topjohnwu.github.io/Magisk/build.html

Use the build script to download and install the necessary Android NDK.

```bash
./build.py ndk
```

--------------------------------

### Install Nightly Rust Toolchain and Components

Source: https://topjohnwu.github.io/Magisk/build.html

Install the Rust nightly toolchain and essential components like rust-src and clippy. This is primarily to satisfy IDE requirements, as the actual build will use the ONDK toolchain.

```bash
rustup toolchain install nightly
rustup +nightly component add rust-src clippy
```

--------------------------------

### Install Magisk on Emulator

Source: https://topjohnwu.github.io/Magisk/faq.html

Temporarily install Magisk on an Android emulator using this script command. The installation is not persistent across reboots. The emulator must have SELinux enabled.

```bash
./build.py emulator <path to Magisk APK>
```

--------------------------------

### Check Magisk Binary Version

Source: https://topjohnwu.github.io/Magisk/faq.html

Run this command in a terminal emulator to check the version and version code of the installed Magisk binaries, even if the Magisk app shows 'Installed = N/A'.

```bash
magisk -c
```

--------------------------------

### Print Message to Console in Magisk Installation

Source: https://topjohnwu.github.io/Magisk/guides.html

Use ui_print to display messages to the console during Magisk module installation. Avoid using 'echo' as it may not display correctly in custom recovery consoles.

```shell
ui_print <msg>

```

--------------------------------

### Run Post-FS-Data Boot Script

Source: https://topjohnwu.github.io/Magisk/guides.html

Scripts placed in /data/adb/post-fs-data.d are executed in post-fs-data mode. This stage is blocking and occurs before modules are mounted and Zygote starts. Use resetprop -n for setting properties to avoid deadlocking the boot process.

```shell
# Example for post-fs-data.sh in a module
# ... script logic ...

```

--------------------------------

### Abort Magisk Installation with Error Message

Source: https://topjohnwu.github.io/Magisk/guides.html

Use abort to display an error message and terminate the Magisk module installation. Avoid using 'exit' as it bypasses necessary cleanup steps.

```shell
abort <msg>

```

--------------------------------

### Clone Magisk Repository

Source: https://topjohnwu.github.io/Magisk/build.html

Clone the Magisk repository and its submodules to get the complete source code.

```bash
git clone --recurse-submodules https://github.com/topjohnwu/Magisk.git
```

--------------------------------

### Resetprop System Property Manipulation

Source: https://topjohnwu.github.io/Magisk/tools.html

The `resetprop` applet is an advanced utility for manipulating system properties. It can be used to get, set, delete, or load properties from files, with options for verbose output and direct manipulation.

```bash
Usage: resetprop [flags] [options...]

Options:
   -h, --help        show this message
   (no arguments)    print all properties
   NAME              get property
   NAME VALUE        set property entry NAME with VALUE
   --file FILE       load props from FILE
   --delete NAME     delete property

Flags:
   -v      print verbose output to stderr
   -n      set props without going through property_service
           (this flag only affects setprop)
   -p      read/write props from/to persistent storage
           (this flag only affects getprop and delprop)
```

--------------------------------

### Build All Magisk Components

Source: https://topjohnwu.github.io/Magisk/build.html

Run the build script to compile all components and create the final Magisk APK.

```bash
./build.py all
```

--------------------------------

### Build Native Binaries

Source: https://topjohnwu.github.io/Magisk/build.html

Build all native code components. This is a prerequisite for working on native code as it generates necessary code.

```bash
./build.py binary
```

--------------------------------

### su

Source: https://topjohnwu.github.io/Magisk/tools.html

The `su` applet provides the MagiskSU entry point, functioning as the traditional `su` command.

```APIDOC
## su

### Description
An applet of `magisk`, the MagiskSU entry point. This is the traditional `su` command.

### Usage
```
Usage: su [options] [-] [user [argument...]]
```

### Options
- `-c, --command COMMAND` : Pass COMMAND to the invoked shell.
- `-g, --group GROUP` : Specify the primary group.
- `-G, --supp-group GROUP` : Specify a supplementary group. The first specified supplementary group is also used as a primary group if the option `-g` is not specified.
- `-Z, --context CONTEXT` : Change SELinux context.
- `-t, --target PID` : PID to take mount namespace from.
- `-h, --help` : Display this help message and exit.
- `-, -l, --login` : Pretend the shell to be a login shell.
- `-m, -p, --preserve-environment` : Preserve the entire environment.
- `-s, --shell SHELL` : Use SHELL instead of the default `/system/bin/sh`.
- `-v, --version` : Display version number and exit.
- `-V` : Display version code and exit.
- `-mm, -M, --mount-master` : Force run in the global mount namespace.
```

--------------------------------

### Magisk CLI

Source: https://topjohnwu.github.io/Magisk/tools.html

The main Magisk binary acts as a utility tool with various helper functions and entry points for Magisk services.

```APIDOC
## Magisk CLI

### Description
The `magisk` binary serves as a versatile utility tool, providing access to numerous helper functions and acting as the entry point for various Magisk services.

### Usage
```
Usage: magisk [applet [arguments]...]
   or: magisk [options]...
```

### Options
- `-c` : Print current binary version.
- `-v` : Print running daemon version.
- `-V` : Print running daemon version code.
- `--list` : List all available applets.
- `--remove-modules [-n]` : Remove all modules. Reboot if `-n` is not provided.
- `--install-module ZIP` : Install a module from a ZIP file.

### Advanced Options (Internal APIs)
- `--daemon` : Manually start the Magisk daemon.
- `--stop` : Remove all Magisk changes and stop the daemon.
- `--[init trigger]` : Callback on init triggers. Valid triggers: `post-fs-data`, `service`, `boot-complete`, `zygote-restart`.
- `--unlock-blocks` : Set BLKROSET flag to OFF for all block devices.
- `--restorecon` : Restore SELinux context on Magisk files.
- `--clone-attr SRC DEST` : Clone permission, owner, and SELinux context from SRC to DEST.
- `--clone SRC DEST` : Clone SRC to DEST.
- `--sqlite SQL` : Execute SQL commands against the Magisk database.
- `--path` : Print the Magisk tmpfs mount path.
- `--denylist ARGS` : Denylist configuration command-line interface.
- `--preinit-device` : Resolve a device to store preinit files.

### Available Applets
- `su`
- `resetprop`

### Denylist Usage
```
Usage: magisk --denylist [action [arguments...] ]
```

#### Denylist Actions
- `status` : Return the enforcement status.
- `enable` : Enable denylist enforcement.
- `disable` : Disable denylist enforcement.
- `add PKG [PROC]` : Add a new target to the denylist.
- `rm PKG [PROC]` : Remove target(s) from the denylist.
- `ls` : Print the current denylist.
- `exec CMDs...` : Execute commands in an isolated mount namespace and perform all unmounts.
```

--------------------------------

### Remove Magisk Modules via ADB

Source: https://topjohnwu.github.io/Magisk/faq.html

Use this command in an ADB shell to remove all installed Magisk modules if your device is bootlooping. Ensure USB debugging is enabled.

```bash
magisk --remove-modules
```

--------------------------------

### MagiskSU (su) Command Usage

Source: https://topjohnwu.github.io/Magisk/tools.html

The `su` applet is the entry point for MagiskSU, providing root access. It supports various options for command execution, user switching, and environment preservation.

```bash
Usage: su [options] [-] [user [argument...]]

Options:
  -c, --command COMMAND         Pass COMMAND to the invoked shell
  -g, --group GROUP             Specify the primary group
  -G, --supp-group GROUP        Specify a supplementary group.
                                The first specified supplementary group is also used
                                as a primary group if the option -g is not specified.
  -Z, --context CONTEXT         Change SELinux context
  -t, --target PID              PID to take mount namespace from
  -h, --help                    Display this help message and exit
  -, -l, --login                Pretend the shell to be a login shell
  -m -p,
  --preserve-environment        Preserve the entire environment
  -s, --shell SHELL             Use SHELL instead of the default /system/bin/sh
  -v, --version                 Display version number and exit
  -V                            Display version code and exit
  -mm -M,
  --mount-master                Force run in the global mount namespace
```

--------------------------------

### Declare Folders to Replace in Magisk Module

Source: https://topjohnwu.github.io/Magisk/guides.html

Use the REPLACE variable to specify directories that should be replaced by the module. The module installer will create a .replace file in each specified directory.

```shell
REPLACE="
/system/app/YouTube
/system/app/Bloatware
"

```

--------------------------------

### Magisk Module Structure

Source: https://topjohnwu.github.io/Magisk/guides.html

Illustrates the directory structure for a Magisk module. Key files include module.prop for metadata, system for system modifications, zygisk for native libraries, and various scripts for execution at different boot stages.

```text
/data/adb/modules
├── . 
├── . 
|
├── $MODID                  <--- The folder is named with the ID of the module
│   │
│   │      *** Module Identity ***
│   │
│   ├── module.prop         <--- This file stores the metadata of the module
│   │
│   │      *** Main Contents ***
│   │
│   ├── system              <--- This folder will be mounted if skip_mount does not exist
│   │   ├── ...
│   │   ├── ...
│   │   └── ...
│   │
│   ├── zygisk              <--- This folder contains the module's Zygisk native libraries
│   │   ├── arm64-v8a.so
│   │   ├── armeabi-v7a.so
│   │   ├── riscv64.so
│   │   ├── x86.so
│   │   ├── x86_64.so
│   │   └── unloaded        <--- If exists, the native libraries are incompatible
│   │
│   │      *** Status Flags ***
│   │
│   ├── skip_mount          <--- If exists, Magisk will NOT mount your system folder
│   ├── disable             <--- If exists, the module will be disabled
│   ├── remove              <--- If exists, the module will be removed next reboot
│   │
│   │      *** Optional Files ***
│   │
│   ├── post-fs-data.sh     <--- This script will be executed in post-fs-data
│   ├── service.sh          <--- This script will be executed in late_start service
|   ├── uninstall.sh        <--- This script will be executed when Magisk removes your module
|   ├── action.sh           <--- This script will be executed when user click the action button in Magisk app
│   ├── system.prop         <--- Properties in this file will be loaded as system properties by resetprop
│   ├── sepolicy.rule       <--- Additional custom sepolicy rules
│   │
│   │      *** Auto Generated, DO NOT MANUALLY CREATE OR MODIFY ***
│   │
│   ├── vendor              <--- A symlink to $MODID/system/vendor
│   ├── product             <--- A symlink to $MODID/system/product
│   ├── system_ext          <--- A symlink to $MODID/system/system_ext
│   │
│   │      *** Any additional files / folders are allowed ***
│   │
│   ├── ...
│   └── ...
|
├── another_module
│   ├── .
│   └── .
├── .
├── .

```

--------------------------------

### Declare Files/Folders to Remove in Magisk Module

Source: https://topjohnwu.github.io/Magisk/guides.html

Use the REMOVE variable to specify files or folders to be removed by the module. The module installer will create dummy devices for each specified path.

```shell
REMOVE="
/system/app/YouTube
/system/fonts/Roboto.ttf
"

```

--------------------------------

### Magisk Overlay Directory Structure

Source: https://topjohnwu.github.io/Magisk/guides.html

Illustrates the placement of files within the `overlay.d` directory for Magisk's root overlay system. Custom `.rc` files, replacement resources, and additional binaries can be organized here.

```text
ramdisk
│
├── overlay.d
│   ├── sbin
│   │   ├── libfoo.ko      <--- These 2 files will be copied
│   │   └── myscript.sh    <--- into Magisk's tmpfs directory
│   ├── custom.rc          <--- This file will be injected into init.rc
│   ├── res
│   │   └── random.png     <--- This file will replace /res/random.png
│   └── new_file           <--- This file will be ignored because
│                               /new_file does not exist
├── res
│   └── random.png         <--- This file will be replaced by
│                               /overlay.d/res/random.png
├── ...
├── ...  /* The rest of initramfs files */
│

```

--------------------------------

### Create Rust Wrapper Directory

Source: https://topjohnwu.github.io/Magisk/build.html

Create a wrapper directory for cargo binaries. This is a workaround for rustup limitations and is used to configure IDEs for Rust development.

```bash
./build.py rustup ~/.cargo/wrapper
```

--------------------------------

### Repack Boot Image with magiskboot

Source: https://topjohnwu.github.io/Magisk/tools.html

Repacks boot image components from the current directory into a new boot image. Use '-n' to skip compression. The original boot image is required.

```bash
  repack [-n] <origbootimg> [outbootimg]
    Repack boot image components using files from the current directory
    to [outbootimg], or 'new-boot.img' if not specified. Current directory
    should only contain required files for [outbootimg], or incorrect
    [outbootimg] may be produced.
    <origbootimg> is the original boot image used to unpack the components.
    By default, each component will be automatically compressed using its
    corresponding format detected in <origbootimg>. If a component file
    in the current directory is already compressed, then no addition
    compression will be performed for that specific component.
    If '-n' is provided, all compression operations will be skipped.
    If env variable PATCHVBMETAFLAG is set to true, all disable flags in
    the boot image's vbmeta header will be set.
```

--------------------------------

### Get Magisk tmpfs Directory Path

Source: https://topjohnwu.github.io/Magisk/details.html

Use the `magisk --path` command to retrieve the current base directory Magisk is using for temporary files. This path is crucial for locating internal Magisk files and binaries.

```bash
# In order to get the current base folder Magisk is using,
# use the command `magisk --path`.
# Binaries like magisk, magiskinit, and all symlinks to
# applets are directly stored in this path. This means when
# this is /sbin, these binaries will be directly in PATH.
MAGISKTMP=$(magisk --path)

# Magisk internal stuffs
INTERNALDIR=$MAGISKTMP/.magisk

# /data/adb/modules will be bind mounted here.
# The original folder is not used due to nosuid mount flag.
$INTERNALDIR/modules

# The current Magisk installation config
$INTERNALDIR/config

# Partition mirrors
# Each directory in this path will be mounted with the
# partition of its directory name.
# e.g. system, system_ext, vendor, data ...
$INTERNALDIR/mirror

# Root directory patch files
# On system-as-root devices, / is not writable.
# All pre-init patched files are stored here and bind mounted.
$INTERNALDIR/rootdir

```

--------------------------------

### Run Late-Start Service Boot Script

Source: https://topjohnwu.github.io/Magisk/guides.html

Scripts placed in /data/adb/service.d are executed in late_start service mode. This stage is non-blocking and runs in parallel with the booting process. This is the recommended mode for most scripts.

```shell
# Example for service.sh in a module
# ... script logic ...

```

--------------------------------

### Unpack Boot Image with magiskboot

Source: https://topjohnwu.github.io/Magisk/tools.html

Unpacks a boot image into its individual components. Use '-n' to skip decompression and '-h' to dump the header.

```bash
Usage: ./magiskboot <action> [args...]

Supported actions:
  unpack [-n] [-h] <bootimg>
    Unpack <bootimg> to its individual components, each component to
    a file with its corresponding file name in the current directory.
    Supported components: kernel, kernel_dtb, ramdisk.cpio, second,
    dtb, extra, and recovery_dtbo.
    By default, each component will be automatically decompressed
    on-the-fly before writing to the output file.
    If '-n' is provided, all decompression operations will be skipped; 
    each component will remain untouched, dumped in its original format.
    If '-h' is provided, the boot image header information will be
    dumped to the file 'header', which can be used to modify header
    configurations during repacking.
    Return values:
    0:valid    1:error    2:chromeos
```

--------------------------------

### Enable BusyBox Standalone Mode

Source: https://topjohnwu.github.io/Magisk/guides.html

Demonstrates two methods to enable BusyBox's standalone mode for shell scripts. Method 1 uses an environment variable, which is preferred as it's inherited by child processes. Method 2 uses command-line options.

```bash
ASH_STANDALONE=1 /data/adb/magisk/busybox sh <script>
```

```bash
/data/adb/magisk/busybox sh -o standalone <script>
```

--------------------------------

### Verify Boot Image Signature with magiskboot

Source: https://topjohnwu.github.io/Magisk/tools.html

Checks if a boot image is signed with AVB 1.0. Optionally, a certificate can be provided for public key verification.

```bash
  verify <bootimg> [x509.pem]
    Check whether the boot image is signed with AVB 1.0 signature.
    Optionally provide a certificate to verify whether the image is
    signed by the public key certificate.
    Return value:
    0:valid    1:error
```

--------------------------------

### Magisk Module Properties (module.prop)

Source: https://topjohnwu.github.io/Magisk/guides.html

Defines the strict format for the `module.prop` file, which contains essential metadata for a Magisk module. It specifies required fields like id, name, version, versionCode, author, and description, along with an optional updateJson URL. Adherence to UNIX (LF) line breaks is crucial.

```text
id=<string>
name=<string>
version=<string>
versionCode=<int>
author=<string>
description=<string>
updateJson=<url> (optional)

```

--------------------------------

### Set File Permissions in Magisk Module

Source: https://topjohnwu.github.io/Magisk/guides.html

Use set_perm to set ownership, permissions, and SELinux context for a file. If context is omitted, it defaults to "u:object_r:system_file:s0".

```shell
set_perm <target> <owner> <group> <permission> [context]

```

--------------------------------

### Magiskpolicy Usage and Policy Statements

Source: https://topjohnwu.github.io/Magisk/tools.html

This section outlines the command-line usage for magiskpolicy, including available options for loading, saving, and applying SELinux policies. It also details the syntax for various policy statements like 'allow', 'deny', 'auditallow', 'dontaudit', and 'permissive'.

```bash
Usage: ./magiskpolicy [--options...] [policy statements...]

Options:
   --help            show help message for policy statements
   --load FILE       load monolithic sepolicy from FILE
   --load-split      load from precompiled sepolicy or compile
                     split cil policies
   --compile-split   compile split cil policies
   --save FILE       dump monolithic sepolicy to FILE
   --live            immediately load sepolicy into the kernel
   --magisk          apply built-in Magisk sepolicy rules
   --apply FILE      apply rules from FILE, read and parsed
                     line by line as policy statements
                     (multiple --apply are allowed)

If neither --load, --load-split, nor --compile-split is specified,
it will load from current live policies (/sys/fs/selinux/policy)

One policy statement should be treated as one parameter;
this means each policy statement should be enclosed in quotes.
Multiple policy statements can be provided in a single command.

Statements has a format of "<rule_name> [args...]”.
Arguments labeled with (^) can accept one or more entries. Multiple
entries consist of a space separated list enclosed in braces ({})
Arguments labeled with (*) are the same as (^), but additionally
support the match-all operator (*).

Example: "allow { s1 s2 } { t1 t2 } class *"
Will be expanded to:

allow s1 t1 class { all-permissions-of-class }
allow s1 t2 class { all-permissions-of-class }
allow s2 t1 class { all-permissions-of-class }
allow s2 t2 class { all-permissions-of-class }

Supported policy statements:

"allow *source_type *target_type *class *perm_set"
"deny *source_type *target_type *class *perm_set"
"auditallow *source_type *target_type *class *perm_set"
"dontaudit *source_type *target_type *class *perm_set"

"allowxperm *source_type *target_type *class operation xperm_set"
"auditallowxperm *source_type *target_type *class operation xperm_set"
"dontauditxperm *source_type *target_type *class operation xperm_set"
- The only supported operation is 'ioctl'
- xperm_set format is either 'low-high', 'value', or '*'.
  '*' will be treated as '0x0000-0xFFFF'.
  All values should be written in hexadecimal.

"permissive ^type"
"enforce ^type"

"typeattribute ^type ^attribute"

"type type_name ^(attribute)"
- Argument 'attribute' is optional, default to 'domain'

"attribute attribute_name"

"type_transition source_type target_type class default_type (object_name)"
- Argument 'object_name' is optional

"type_change source_type target_type class default_type"
"type_member source_type target_type class default_type"

"genfscon fs_name partial_path fs_context"

```

--------------------------------

### Magisk Utility Tool Usage

Source: https://topjohnwu.github.io/Magisk/tools.html

The `magisk` command serves as a versatile utility tool with various helper functions and entry points for Magisk services. Use it to manage modules, start/stop services, or access advanced internal APIs.

```bash
Usage: magisk [applet [arguments]...]
   or: magisk [options]...

Options:
   -c                        print current binary version
   -v                        print running daemon version
   -V                        print running daemon version code
   --list                    list all available applets
   --remove-modules [-n]     remove all modules, reboot if -n is not provided
   --install-module ZIP      install a module zip file

Advanced Options (Internal APIs):
   --daemon                  manually start magisk daemon
   --stop                    remove all magisk changes and stop daemon
   --[init trigger]          callback on init triggers. Valid triggers:
                             post-fs-data, service, boot-complete, zygote-restart
   --unlock-blocks           set BLKROSET flag to OFF for all block devices
   --restorecon              restore selinux context on Magisk files
   --clone-attr SRC DEST     clone permission, owner, and selinux context
   --clone SRC DEST          clone SRC to DEST
   --sqlite SQL              exec SQL commands to Magisk database
   --path                    print Magisk tmpfs mount path
   --denylist ARGS           denylist config CLI
   --preinit-device          resolve a device to store preinit files

Available applets:
    su, resetprop
```

```bash
Usage: magisk --denylist [action [arguments...] ]
Actions:
   status          Return the enforcement status
   enable          Enable denylist enforcement
   disable         Disable denylist enforcement
   add PKG [PROC]  Add a new target to the denylist
   rm PKG [PROC]   Remove target(s) from the denylist
   ls              Print the current denylist
   exec CMDs...    Execute commands in isolated mount
                   namespace and do all unmounts
```

--------------------------------

### Magisk Paths in /data/adb

Source: https://topjohnwu.github.io/Magisk/details.html

This section details the various subdirectories within `/data/adb` used by Magisk for storing scripts, modules, databases, and binaries. The `/data/adb` directory is chosen for its security and ubiquity.

```bash
SECURE_DIR=/data/adb

# Folder storing general post-fs-data scripts
$SECURE_DIR/post-fs-data.d

# Folder storing general late_start service scripts
$SECURE_DIR/service.d

# Magisk modules
$SECURE_DIR/modules

# Magisk modules that are pending for upgrade
# Module files are not safe to be modified when mounted
# Modules installed through the Magisk app will be stored here
# and will be merged into $SECURE_DIR/modules in the next reboot
$SECURE_DIR/modules_update

# Database storing settings and root permissions
MAGISKDB=$SECURE_DIR/magisk.db

# All magisk related binaries, including busybox,
# scripts, and magisk binaries. Used in supporting
# module installation, addon.d, the Magisk app etc.
DATABIN=$SECURE_DIR/magisk

```

--------------------------------

### Extract Partition from Payload with magiskboot

Source: https://topjohnwu.github.io/Magisk/tools.html

Extracts a specified partition from a payload.bin file to an output file. If no partition is specified, it attempts to extract 'init_boot' or 'boot'.

```bash
  extract <payload.bin> [partition] [outfile]
    Extract [partition] from <payload.bin> to [outfile].
    If [outfile] is not specified, then output to '[partition].img'.
    If [partition] is not specified, then attempt to extract either
    'init_boot' or 'boot'. Which partition was chosen can be determined
    by whichever 'init_boot.img' or 'boot.img' exists.
    <payload.bin> can be '-' to be STDIN.
```

--------------------------------

### Cpio Operations with magiskboot

Source: https://topjohnwu.github.io/Magisk/tools.html

Performs various operations on a cpio archive in-place, including exists, rm, mkdir, ln, mv, add, extract, test, patch, backup, and restore.

```bash
  cpio <incpio> [commands...]
    Do cpio commands to <incpio> (modifications are done in-place)
    Each command is a single argument, add quotes for each command.
    Supported commands:
      exists ENTRY
        Return 0 if ENTRY exists, else return 1
      rm [-r] ENTRY
        Remove ENTRY, specify [-r] to remove recursively
      mkdir MODE ENTRY
        Create directory ENTRY in permissions MODE
      ln TARGET ENTRY
        Create a symlink to TARGET with the name ENTRY
      mv SOURCE DEST
        Move SOURCE to DEST
      add MODE ENTRY INFILE
        Add INFILE as ENTRY in permissions MODE; replaces ENTRY if exists
      extract [ENTRY OUT]
        Extract ENTRY to OUT, or extract all entries to current directory
      test
        Test the cpio's status
        Return value is 0 or bitwise or-ed of following values:
        0x1:Magisk    0x2:unsupported
      patch
        Apply ramdisk patches
        Configure with env variables: KEEPVERITY KEEPFORCEENCRYPT
      backup ORIG
        Create ramdisk backups from ORIG
      restore
        Restore ramdisk from ramdisk backup stored within incpio
```
Tokens:
Raw