Shizuku is a useful Android tool that allows supported applications to access certain system-level APIs without requiring root access. It is commonly used by power-user apps for advanced settings, automation, file management, and other features that normally need ADB or elevated permissions.
The usual wireless debugging method requires Android’s Developer Options to remain enabled. This can be inconvenient for users who prefer to keep Developer Options turned off after finishing their setup.
Fortunately, there is a workaround using SystemUI Tuner. The method allows the required ADB-related setting to remain active while the main Developer Options screen is disabled. However, it is important to understand that this does not completely remove Android’s ADB requirements. You need Developer Options and Wireless Debugging during the initial setup.
Once everything is configured, SystemUI Tuner can be used to maintain the required setting, allowing Shizuku to continue working with Developer Options switched off.
What You Need Before Starting
Before following the steps, make sure you have:
- An Android phone that supports Wireless Debugging.
- Android 11 or newer for the standard Shizuku wireless debugging method.
- Shizuku installed.
- SystemUI Tuner installed.
- A Wi-Fi connection.
- Access to a computer with ADB, or another method capable of running the required ADB command.
- Developer Options available for the initial configuration.
Android places Wireless Debugging inside Developer Options. Google also notes that turning off the main Developer Options switch disables most of the options contained within it.
Also Read: 100 Shizuku Apps and Mods Every Android User Should Know
How This Method Works
Normally, the process looks like this:
Developer Options → Wireless Debugging → ADB → Shizuku
The problem is that turning off Developer Options normally turns off the debugging functionality that Shizuku needs.
SystemUI Tuner provides access to several hidden Android settings and includes controls related to ADB. Its Developer section can expose settings such as Enable ADB and Wireless ADB, while its Persistent Options feature can help keep selected settings applied.
The workaround therefore changes the practical setup to:
Initial Developer Options setup → SystemUI Tuner → ADB setting → Shizuku
This is why the method should not be described as a way to completely run Shizuku without ever using Developer Options. Instead, it lets you disable the visible Developer Options switch after the required configuration has been completed.
Step 1: Install Shizuku
First, install Shizuku on your Android phone.
Open Shizuku and check the available startup methods. On a non-rooted phone, the Wireless Debugging method is normally used on supported Android versions.
Do not turn off Developer Options at this stage.
Step 2: Enable Developer Options
If Developer Options is not already enabled, open your phone’s Settings and locate Build Number.
The location differs between manufacturers. On many phones, it can be found under:
Settings → About Phone → Build Number
Tap Build Number seven times until Android confirms that developer mode has been enabled. Google documents this same general process, although the exact location can vary by manufacturer.
Return to Settings and open Developer Options.
Step 3: Enable Wireless Debugging
Inside Developer Options, find Wireless Debugging and turn it on.
On newer Android versions, Google lists Wireless Debugging under Developer Options. The exact menu location can vary depending on the Android version and phone manufacturer.
Now open Shizuku and complete the Wireless Debugging pairing process.
You will normally need to use the Pairing option in Shizuku, open the Wireless Debugging pairing screen, and enter the pairing code shown by Android.
Once pairing is complete, start Shizuku.
Wait until Shizuku reports that its service is running.
Step 4: Install SystemUI Tuner
Next, install SystemUI Tuner by Zachary Wander.
SystemUI Tuner exposes a number of Android settings that are normally hidden or difficult to access. The developer also warns that its functionality depends on what individual Android manufacturers allow, so some features may behave differently on Samsung, Xiaomi, OnePlus, Oppo, and other devices.
Open SystemUI Tuner after installing it and complete its initial setup.
Step 5: Grant SystemUI Tuner the Required Permission
SystemUI Tuner needs access to protected Android settings for this method.
Connect your phone to a computer with ADB configured, then open Command Prompt or Terminal and run:
adb shell pm grant com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGSThis grants SystemUI Tuner the WRITE_SECURE_SETTINGS permission required for accessing certain protected settings.
If ADB is working correctly, the command should complete without showing an error.
This is an important step because simply installing SystemUI Tuner does not automatically give it permission to modify protected Android settings.
Step 6: Configure SystemUI Tuner
Open SystemUI Tuner and complete any setup prompts that appear.
Depending on your Android version and manufacturer, the available menus may look slightly different.
Look for the Developer section inside SystemUI Tuner.
You should find options related to ADB, including settings such as:
- Enable ADB
- Enable Wireless ADB
Enable the required ADB options.
The exact appearance can vary between Android builds because SystemUI Tuner works with Android’s underlying settings system, while manufacturers can modify or remove individual settings.
Step 7: Enable the ADB Setting Permanently
After enabling the ADB-related option, return to the main SystemUI Tuner settings and open Persistent Options.
Look for Enable ADB and enable it.
The purpose of Persistent Options is to keep the selected setting applied instead of treating it as a temporary change.
For this particular workaround, the important part is making sure the ADB setting remains available after you disable the main Developer Options switch.
Step 8: Check Shizuku
Now open Shizuku again.
Make sure:
- Your phone is connected to Wi-Fi.
- Wireless Debugging was successfully paired.
- SystemUI Tuner has the required permission.
- ADB is enabled through SystemUI Tuner.
- Shizuku can communicate with the wireless debugging service.
If everything is configured correctly, start Shizuku through the Wireless Debugging method.
The Shizuku status should change to Running.
At this point, open an application that supports Shizuku and check whether it can obtain Shizuku access.
Also Read: 20 Shizuku Tricks Most Android Users Don’t Know
Step 9: Turn Off Developer Options
This is the main part of the workaround.
Once Shizuku is running and SystemUI Tuner has been configured, open your normal Android Settings.
Go to Developer Options and turn off the main Developer Options switch.
Do not uninstall SystemUI Tuner or remove the permission you granted earlier.
The idea is that SystemUI Tuner continues controlling the required ADB-related setting even though the Developer Options interface itself is disabled.
If Shizuku remains active, you can now use supported Shizuku applications without leaving the main Developer Options switch enabled.
Does Shizuku Really Work Without Developer Options?
Yes, but there is an important distinction.
You are not bypassing Android’s ADB security completely.
The initial configuration still requires Developer Options and Wireless Debugging. SystemUI Tuner is being used afterward to maintain the underlying setting needed by the wireless ADB/Shizuku setup.
Therefore, it is more accurate to say that this method allows you to use Shizuku while the visible Developer Options switch is turned off, rather than saying that Shizuku never needs Developer Options.
This distinction is particularly important when troubleshooting the setup.
What Happens After Restarting the Phone?
A reboot can change the situation.
Shizuku’s wireless debugging startup process generally needs to be performed again after a reboot. SystemUI Tuner may help restore the relevant ADB setting, but it does not guarantee that Shizuku will automatically start on every Android device. Device manufacturers can also apply their own restrictions or reset certain settings.
After restarting your phone, try this:
- Connect to Wi-Fi.
- Open SystemUI Tuner.
- Check that the ADB-related setting is still enabled.
- Open Shizuku.
- Start Shizuku using the available Wireless Debugging option.
- Check that Shizuku shows Running.
If it does not start, you may need to temporarily enable Developer Options again and repeat the wireless debugging process.
Important Notes for Samsung, Xiaomi, OnePlus and Other Phones
This workaround may not behave identically on every Android phone.
Manufacturers often modify Android’s debugging and security systems. Some devices may require additional security-related options before ADB or Wireless Debugging can operate correctly.
For example, community reports indicate that certain Xiaomi, Oppo, and OnePlus devices can require additional manufacturer-specific settings.
Therefore, if the method works on one Android phone but fails on another, that does not necessarily mean the Shizuku setup itself is incorrect.
How to Undo the Setup
If you no longer want SystemUI Tuner to control the protected setting, you can revoke its permission through ADB:
adb shell pm revoke com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGSYou can then remove SystemUI Tuner if you no longer need it.
Before uninstalling the app, it is also a good idea to undo any settings you changed manually. SystemUI Tuner’s developer notes that changing or removing the app does not necessarily mean every modified Android setting will automatically return to its previous state.
Troubleshooting
Shizuku is not starting
First check whether Wireless Debugging is actually active and whether the phone is connected to Wi-Fi.
Then open SystemUI Tuner and verify that the ADB-related option is enabled.
If necessary, temporarily enable Developer Options and confirm that Wireless Debugging is working normally.
SystemUI Tuner cannot access the required settings
Check that the following command was executed successfully:
adb shell pm grant com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGSIf the command returns an error, check your ADB connection and make sure the correct device is detected.
Shizuku stops working after a reboot
This can be expected with the wireless debugging startup method.
Open SystemUI Tuner first, check the ADB configuration, and then try starting Shizuku again.
If it still fails, temporarily turn Developer Options back on and repeat the Wireless Debugging pairing/startup process.
The options are missing in SystemUI Tuner
SystemUI Tuner cannot override every manufacturer modification to Android. Some hidden settings may be unavailable or behave differently depending on the device and Android version.
Banking or payment apps still detect Developer Options
This method does not guarantee that every application will interpret the device in exactly the same way.
Some apps may check other debugging, security, root, bootloader, or device-integrity signals instead of simply checking whether the Developer Options screen is visible.
Final Thoughts
SystemUI Tuner provides a practical workaround for Android users who want to keep using Shizuku without leaving the main Developer Options switch enabled.
The setup requires some initial work: Developer Options and Wireless Debugging must first be enabled, Shizuku needs to be paired, and SystemUI Tuner needs the appropriate protected permission. After that, SystemUI Tuner can be configured to maintain the relevant ADB setting while Developer Options is switched off.
Keep in mind that Android manufacturers handle debugging features differently, so the procedure may not work exactly the same way on every phone. A reboot can also require additional Shizuku startup steps.
Most importantly, this is not a root method and not a complete removal of Android’s ADB security requirements. It is simply a way to keep the necessary ADB configuration available while hiding the active Developer Options state from the normal Settings interface.
Disclaimer: Settings and steps may vary by Android version and phone brand. Use ADB and SystemUI Tuner carefully, as some changes may affect system settings.
Note: Product details, pricing, and availability may change over time. While we try to keep information accurate, please verify details from the official website before purchasing. Some content may be assisted by AI tools like ChatGPT, and some articles may contain affiliate links that may earn us a small commission at no extra cost to you. Reviews, opinions, and feature highlights are based on official specifications and publicly available information at the time of writing.
Explore our
News Section
for daily updates and the latest tech news.Join our
WhatsApp Channel
for instant updates.
