You buy a phone with 128GB or 256GB of storage, and somehow it's still full. The app drawer has three browsers you never installed, two app stores competing for attention, and a folder of games you'd never download yourself. After a month the phone stutters, the battery drains faster than the review promised, and your notification shade fills up with offers from apps you didn't know existed.
That's bloatware. For years, getting rid of it meant rooting your phone, risking your warranty, or sitting at a computer with a USB cable and a stack of ADB commands.
I've debloated a POCO F9 Pro, a Redmi Note 17 Pro Max, and an HONOR Pad 9 without any of those things. No PC, no cable, no root, no unlocked bootloader. Just two free, open-source apps installed directly on the device. This guide walks through the same process.
Why bother debloating?
Manufacturers don't ship phones clean. Many pre-installed apps exist to earn the vendor money, through promotions, subscriptions, or data collection. The result is a phone that works against you from day one:
- Storage goes to apps you can't delete. System apps live in the read-only firmware partition, so a normal "uninstall" only hides them. They still take up space with their updates and data.
- Background processes eat RAM and battery. Duplicate services, like a second app store or a second cloud drive, wake each other up and sync in the background.
- Ads show up in system apps. On some Chinese-brand skins, the file manager, security app, or settings menu carries ad slots.
- Telemetry leaves the device. Usage data goes back to the vendor, and sometimes to third-party analytics SDKs built into the ROM.
Debloating helps with all four. The modern method doesn't touch the parts of Android that made this risky before. Your bootloader stays locked, the system partition is untouched, OTA updates keep arriving, and every removal can be reversed.
How the no-root approach works
Android has a command, pm uninstall --user 0, that removes an app for the current user only. The original APK stays on the system partition. Your user profile just stops seeing it. Because nothing on the protected partition is modified, this isn't rooting or a system mod. Restore the package and the app comes back as it was.
The catch is that running that command requires ADB-level privileges, which normal apps don't have. Traditionally you got those privileges by connecting to a computer.
Two apps remove the computer from the equation:
- Shizuku starts a privileged ADB-level service on the phone itself, using Android's Wireless Debugging feature (Android 11 and newer). Other apps can then borrow that privilege through a formal API.
- Canta talks to Shizuku, lists your installed packages with safety ratings from the community-maintained Universal Debloat List, and issues the uninstall commands for you.
No terminal, no cable, no PC. You pair once with a six-digit code, then tap to remove.
What you need before starting
- An Android phone running Android 11 or newer. Canta itself supports Android 9+, but the no-computer Shizuku start method requires 11+.
- The phone on Wi-Fi. Wireless Debugging only works on a local network.
- About 15 minutes of uninterrupted time.
- A rough idea of which apps you actually use. Install replacements first, such as a different browser, launcher, or keyboard, before removing the stock ones.
- Your photos and files backed up. It's standard advice, and it's cheap insurance.
Step 1: Install Shizuku and Canta
Shizuku is available on Google Play and GitHub.
Canta is best installed from F-Droid, where the package name is io.github.samolego.canta. The current release is 3.2.2, from March 2026, and it requires Android 9 or newer. F-Droid handles updates for you, which sideloaded APKs don't. Canta also has a Google Play listing if you prefer that.
If your phone runs Android 16, you need a forked build of Shizuku instead of the standard one. The Canta developer points to github.com/thedjchi/Shizuku for that case. Check your Android version in Settings before you install.
Install both, but don't open Canta yet. It can't do anything until Shizuku is running.
Step 2: Start Shizuku via Wireless Debugging
This is the only part that feels technical. It's really just pairing two screens.
- Enable Developer options. Go to Settings → About phone and tap Build number seven times. On POCO, Redmi, and Xiaomi phones, tap OS version (or MIUI version on older skins) instead. Enter your lock screen PIN when asked.
- Turn on the debugging toggles. Open Settings → System → Developer options (or Additional settings → Developer options on Chinese-brand skins). Turn on USB debugging, then open Wireless debugging and switch it on.
- Start pairing in Shizuku. Open Shizuku, tap Pairing under "Start via Wireless debugging," and allow notifications when prompted. Pairing completes through a notification, so Shizuku needs that permission.
- Generate the code. Back in Wireless debugging, tap Pair device with pairing code. Android shows a six-digit code. Leave that dialog open.
- Enter the code. Pull down the notification shade, expand the Shizuku notification, tap Enter pairing code, and type the six digits before they expire. You should see a "Pairing successful" message.
- Start the service. Return to Shizuku and tap Start. Once it's running, Shizuku shows a status confirming it's active.
Pairing only happens once. After a reboot, reopen Shizuku and tap Start again. Wireless Debugging has to stay on for that.
If pairing stalls on a Xiaomi, POCO, or Redmi phone, go to the system notification settings and change the notification style to "Android" instead of the default, then try again. Shizuku's troubleshooting page also lists a Legacy pairing option in its settings. If the search screen keeps spinning, toggle Wireless Debugging off and on and retry.
Step 3: Debloat with Canta
Open Canta. On first launch it asks for Shizuku access, so approve it. The app loads every installed package, system apps included, and tags each one with a badge from the Universal Debloat List, a community-maintained database.
The badges are the reason to use Canta instead of typing commands blind:
| Badge | Meaning | What to do |
|---|---|---|
| Recommended (green) | Safe to remove, such as ads, analytics, and duplicate stores | Remove, after reading the description |
| Advanced | Breaks minor or obscure functionality, or is easily replaced | Consider disabling it first |
| Expert | Breaks widely used or important functionality | Read the description carefully |
| Unsafe (red) | Can break core OS functions and may cause a bootloop | Leave it alone |
The Universal Debloat List FAQ recommends that for anything above Recommended, you disable a package before you uninstall it, because uninstalling those is more likely to cause stability problems. Canta's trash button uninstalls, so for Advanced and Expert packages, consider whether disabling is enough.
A workflow that works:
- Tap a package and read its description and recommendation.
- Confirm you don't use the feature. If you do, install the replacement first.
- Tap the trash icon and confirm.
- Test the phone. Make a call, take a photo, connect Bluetooth, and open your banking app.
- Only then move to the next package.
Remove things one or two at a time. Batch-selecting thirty green badges in one sitting is how people end up debugging a broken phone instead of enjoying a clean one.
Note: In my case I remove the Mi Store, Honor App Store to avoid conflict with Google Play Store, I also removed default Google Chrome Browser, Mi Browser and I use only Brave Browser, Please make sure you understand what you're doing here. Do not remove all green items says 'Recommended' or safe to remove.
Brand notes: Xiaomi, POCO, Redmi, and HONOR
The core process is the same on every brand. Only the menu names and a few quirks change.
On POCO and Redmi (HyperOS):
- Developer options unlock by tapping OS version, not Build number.
- HyperOS ships with a lot of extras, including App vault, App finder, the GetApps store, Mi Browser, and analytics packages.
- In my testing, App vault and App finder caused a launcher glitch when removed while still enabled, and the glitch survived a reboot. Turn them off in your launcher's Home screen settings first, then remove them.
- Some HyperOS builds on Android 14 and newer block disabling certain system apps. If Canta reports an error on a package, don't force it. Check the package's description and move on.
- Most Xiaomi, Google, and third-party packages with green or yellow badges are safe to go through. Leave red badges alone.
On HONOR (MagicOS):
- If an app you want to remove doesn't appear in Canta, try the normal home screen uninstall. Canta handles system packages, and that's where it's most useful.
- The usual targets are duplicate OEM services, such as HONOR Lens (Google Lens covers this), HONOR Share (Quick Share exists), and the duplicate App Market.
- Some vendor apps reinstall themselves after an OS update. If one returns, remove it again or accept it as harmless.
Undo: restoring anything you removed
Nothing in this method is permanent. Canta keeps a record of the packages you removed, and it can detect them again after you reinstall the app.
To bring something back, open Canta and go to the tab with the crossed-out trash icon, which lists removed apps. Select the one you want and tap the restore option. Canta needs Shizuku access for this, so make sure Shizuku is running first. Restoring works because the original package was never deleted from the system partition.
The real risk is removing something the OS needs at boot. Then you may get stuck in a bootloop, which a factory reset fixes but which also wipes your data. Stay out of the red badges and you won't get close to that.
After you finish
- Turn off Developer options and Wireless debugging when you're done. They're debugging tools, so keep them on only while you need them.
- Restart the phone and check that calls, camera, Bluetooth, payments, and notifications still work.
- Remove Shizuku and Canta. Canta remembers what you removed either way. If you uninstall Shizuku, you'll have to pair again the next time you want to debloat.
- Recheck after major updates. New HyperOS and MagicOS versions can bring old bloat back. A few minutes in Canta usually puts things back in line.
Quick FAQ
Do I need root? No. Shizuku runs an ADB-level service, which is a separate privilege tier from root. Your bootloader stays locked.
Does it void my warranty? This method doesn't unlock the bootloader or modify the system partition. Warranty terms are set by the manufacturer, though, so check them if you're unsure.
Will OTA updates still work? Yes. Packages removed for your user can come back after major OS updates, which is another reason to recheck.
Can I remove Google Play Services or the launcher? Don't. Both are in red-badge territory. Removing the launcher in particular is a good way to end up with a bootloop.
What about Android 10 and older? The no-PC Wireless Debugging method starts at Android 11. Older phones can still run Canta, but Shizuku needs a one-time computer connection to start.
Should I use the Play Store or F-Droid version of Canta? Either works. F-Droid is the one I'd pick, since it updates automatically.
The takeaway
Debloating used to be an enthusiast ritual: unlock the bootloader, flash a custom recovery, and hope. Then it became a computer chore: install platform tools, plug in a cable, and paste commands you half understood.
Now it's a phone-native process. Shizuku borrows the privileges Android already exposes through Wireless Debugging. Canta turns those privileges into a color-coded checklist, and the Universal Debloat List tells you what's safe before you tap anything. No root, no PC, no cable, and every removal can be undone.
Your phone shipped with someone else's deals built in. Taking them back takes about fifteen minutes.
Sources: Shizuku user manual (shizuku.rikka.app) and the thedjchi/Shizuku wiki, Canta GitHub repository and release notes (samolego/Canta), Canta Play Store listing, Universal Debloater Alliance FAQ (UAD-ng).
Note: If you need a video guide please search at youtube 'How to debloat your Android'
