2.2 KiB

Raw Blame History

🛠️ Using ReVanced CLI

Learn how to ReVanced CLI.

⚡ Setup ADB

Ensure that ADB is working
```
adb shell exit
```
If you want to deploy the patched APK file on your device by mounting it on top of the original APK file, you will need root access. This is optional.
```
adb shell su -c exit
```
Get the name of your device
```
adb devices
```

🔨 Using ReVanced CLI

⚙️ Show all available options for ReVanced CLI
```
java -jar revanced-cli.jar -h
```

📃 List all available patches from supplied patch bundles

java -jar revanced-cli.jar
 -b revanced-patches.jar \
 -l

💉 Use ReVanced CLI to patch an APK file but deploy without root permissions

This will deploy the patched APK file on your device by installing it.
```
java -jar revanced-cli.jar \
 -a input.apk \
 -o patched-output.apk \
 -b revanced-patches.jar \
 -d device-name
```
👾 Use ReVanced CLI to patch an APK file but deploy with root permissions

This will deploy the patched APK file on your device by mounting it on top of the original APK file.
```
adb install input.apk
java -jar revanced-cli.jar \
 -a input.apk \
 -o patched-output.apk \
 -b revanced-patches.jar \
 -e vanced-microg-support \
 -d device-name \
 --mount
```
Note: Some patches from ReVanced Patches also require ReVanced Integrations. Supply them with the option -m. ReVanced Patcher will merge ReVanced Integrations automatically, depending on if the supplied patches require them.
⚙️ Supply options to patches using ReVanced CLI

Some patches provide options. Currently, ReVanced CLI will generate and consume an options.json file at the location that is specified in -o. If the option is not specified, the options file will be generated in the current working directory.

The options file contains all options from supplied patch bundles.

Note: The options.json file will be generated at the first time you use ReVanced CLI to patch an APK file for now. This will be changed in the future.