bunnylock locks bands, RATs and cells on Android phones. It works through root or Shizuku and picks the right way to talk to your phone's modem.

Modems are weird, and vendors rarely implement the same controls in the same way. Something working on one phone does not guarantee that it will work on every phone with the same chipset or Android version.

Home	Bands	Cell lock	Tools

Caution

bunnylock changes low-level modem settings, and some of them stay after a reboot. A wrong lock can leave you without service, emergency calls included. Use it at your own risk. The author isn't responsible for any damage it causes, such as lost service, lost data or a phone that stops working properly. It comes without any warranty. See the license.

Unlock all on the Home screen tries to undo bunnylock's locks, even without service, but the modem doesn't always go along with it. Before you experiment, find out how else your phone can get back to normal, such as a network settings reset or its engineering menu.

Features

Depending on your phone, bunnylock can:

• lock 2G, 3G, 4G and 5G bands
• force a RAT, such as 4G only or 5G only
• lock 4G and 5G cells by EARFCN, ARFCN or PCI
• choose 5G SA, NSA or both
• lock to one mobile network
• turn VoLTE, Wi-Fi calling and carrier aggregation on or off
• restart the radio or reboot the modem
• open the built-in band menu on supported Samsung phones

See Tested devices for what has been tried on real phones.

Supported phones

bunnylock tries root first, then Shizuku. Shizuku started through ADB can do less, though some MediaTek and Unisoc phones can still lock bands with it.

It picks a backend for your chipset, and you can change it in Settings:

• Qualcomm: QMI
• MediaTek: AT commands
• Pixel (Tensor): the modem's NV settings
• Unisoc: AT commands
• Anything else: Android's radio HAL

If something doesn't work, copy the diagnostics from Tools and include them in your report.

Building

You need the Android SDK, the NDK version set in gradle/libs.versions.toml and CMake 3.22.1. Gradle runs on Java 25 and compiles with Temurin 17, and it downloads either one if it's missing, so the first build needs a network connection.

./gradlew assembleRelease

The APK ends up in app/build/outputs/apk/release/. It's signed with your debug key unless you add a keystore.properties in the project root with storeFile, storePassword, keyAlias, keyPassword and, optionally, a lineageFile from apksigner rotate.

Translating

The strings live in app/src/main/res/values and modem/src/main/res/values. To add a language:

1. In both app/src/main/res and modem/src/main/res, make a values-<code> folder, for example values-de, values-pt-rBR or values-b+sr+Latn, and copy only the strings_*.xml files from values into it.
2. Translate every string and delete the ones marked translatable="false". Set settings_language_name to the language's own name, like Deutsch.

The build finds the new folders by itself and adds the language to the app's picker and to Android's per-app language settings. It fails if a language has strings in only one of the two modules.