How to uninstall Lucky Patcher on Android (and clean up what it leaves behind) in 2026

“How do I uninstall Lucky Patcher?” is one of the most-asked questions on the Lucky Patcher search results, and for good reason. Tapping the Settings uninstall button removes the client itself, but Lucky Patcher is not a regular app. It writes custom patches into other apps, sometimes installs a su daemon or a Magisk module, asks for device-admin rights to survive a botched patch, and leaves a folder of cached APKs in shared storage. Skipping any of those steps means the visible icon is gone but the device is still carrying the side effects.

This guide covers the full Lucky Patcher uninstall flow on Android, what the Settings flow actually cleans up, the patched apps you need to revisit, the root and Magisk artefacts most guides skip, and the verified Android stores worth installing afterwards. If you want the safety context for why people uninstall in the first place, is Lucky Patcher safe in 2026 covers the clone-APK problem in detail. If the install never finished correctly on Android 14 or 15, the Lucky Patcher Android compatibility guide explains what changed at the OS level.

The quick answer

• Uninstalling the Lucky Patcher client is a one-tap Settings flow on most devices. It removes the app, its cache, and its data partition.
• It does not revert apps you patched. Patched APKs keep running on their modified package or signature, and a few keep an entry in Lucky Patcher’s “modified apps” list even after the client is gone.
• It does not remove the /LuckyPatcher/ folder in shared storage. That folder holds backup APKs and dump files that can be 1 to 5 GB on a device that has been patching for a while.
• It does not revoke the “install unknown apps” permission you granted to the installer source. That permission stays until you remove it manually.
• It does not remove root, the su binary, or Magisk modules that Lucky Patcher uses to do its actual work. Those are separate components and need a separate cleanup.
• It does not scan the device for known malware samples. Most “Lucky Patcher malware” reports trace back to clone APKs, not the original, and a clone often arrives with a second hidden package that survives the visible uninstall.

If you are working through the list, the order below is the safe one. Skip the optional steps only if you are sure they do not apply.

Step 1: revoke device-admin access first

Lucky Patcher does not always ask for device-admin rights, but a number of clone builds do, and so does the official client if you used the “remove license verification” workflow on certain apps. Device admin is the trick that makes Settings show “this app is part of system settings” and grey out the Uninstall button.

1. Open Settings, then Security & privacy (or Security on older skins).
2. Find Device admin apps or Device administrators. The exact path varies: on Pixel it is Settings, Security & privacy, More security & privacy, Device admin apps. On Samsung One UI it is Settings, Security and privacy, Other security settings, Device admin apps.
3. Look for Lucky Patcher in the list, plus any unfamiliar entries. Tap each, then Deactivate.
4. Return to the previous screen and confirm Lucky Patcher is no longer ticked.

If you skip this and try to uninstall first, the Uninstall button is greyed out and Android shows a generic admin error. Revoking the rights now turns that button back on.

Step 2: uninstall the Lucky Patcher client

Once device admin is off, the uninstall itself is the standard Android flow.

1. Open Settings, then Apps (or Applications, depending on your device skin).
2. Scroll to Lucky Patcher in the list, or tap See all apps if the list is filtered.
3. Tap the entry, then Uninstall, then OK on the confirmation dialog.
4. Wait for the system to return to the apps list. The entry disappears when the package is gone.

If you cannot find Lucky Patcher in the list, two things may be true. Either the package name on disk is something other than com.chelpus.lackypatch (clone builds often ship under names like com.luckypatcher.android or com.lp.installer), or you already uninstalled it and the launcher icon is a leftover shortcut. Long-pressing the icon and tapping App info is the fastest way to confirm which package it points to.

If the uninstall still fails and the device shows a generic error, restart the phone and try once more. A persistent failure after a reboot points to a clone build with extra protection on, in which case the cleanest path is to put the device in Safe mode (hold the power button, then long-press Power off until the Safe-mode prompt appears) and uninstall from there. Safe mode disables every sideloaded app and lets you remove anything that is otherwise blocking itself.

Step 3: revisit every app you patched

This is the step most uninstall guides skip, and it is the one that matters most. Lucky Patcher does not just sit next to the apps it patched. It rewrites their APKs, swaps signing logic, or installs custom patches that survive the Lucky Patcher uninstall.

Open Lucky Patcher one last time before Step 2 if you can, tap the menu, and pick Toolbox, Backups. The list shows every app the client touched. Screenshot it. After you uninstall the client, that list is gone, and the apps are still on the device.

If you already removed the client, you can find patched apps by sorting installed apps by install date or last update:

1. In Settings, Apps, See all apps, tap the sort menu (a three-dot or filter icon in the top right).
2. Choose Sort by install date or Sort by last update.
3. Walk down the list and flag anything that lines up with when you used Lucky Patcher.

The signs that an app was patched are a signing certificate that does not match the original publisher (visible in App info, App details in store, or via an APK inspector), a version string ending in .modded, .lp, or .patched, an app that refuses to update through Play (because the signature no longer matches), and an app whose in-app purchase, ad-removal, or license behaviour is suspiciously generous.

For each one, the safe move is the same: uninstall the patched build, then reinstall the original from Play (or another verified store) so the app comes back on the developer’s release channel with the right signature. Your Play purchase history still recognizes the original; the patched copy was the problem, not the entitlement.

Pay particular attention to banking apps, payment wallets, and authenticator apps. If any of those went through a Lucky Patcher patch, treat them as compromised and reinstall the originals before logging back in.

Step 4: revoke “install unknown apps” for the installer source

When you installed Lucky Patcher the first time, Android asked you to grant the source (your browser, file manager, or another installer) permission to install unknown apps. That permission persists per source until you revoke it.

1. Open Settings, Apps, Special app access, Install unknown apps.
2. Find the source you used to install Lucky Patcher (commonly Chrome, Files by Google, Samsung Internet, or a file manager).
3. Toggle Allow from this source off.

This will not uninstall Lucky Patcher retroactively. It will stop the same source from silently re-installing a sideloaded APK that lands in your downloads folder. On Android 13 and later this also resets the Restricted Settings flag for that installer, which is the protection that blocks newly sideloaded apps from getting accessibility or notification access on first install.

Step 5: remove the LuckyPatcher folder and other residual files

Android 11 and later sandbox most app data inside /Android/data/, which the system clears when you uninstall the owning app. Lucky Patcher writes a lot of data outside that sandbox, in places the system uninstall does not touch.

The locations worth checking:

• /LuckyPatcher/ at the storage root. This is where backup APKs, dumped patches, and the offline catalog live. On a long-term install this folder is often the largest single source of “junk” storage on the device.
• /Download/ or /Download/LuckyPatcher/. Sideloaded APKs that Lucky Patcher fetched usually land here.
• /Android/data/com.chelpus.lackypatch/ (and any clone-build variant). Most of this gets cleared on uninstall, but a Restricted Settings reset can leave residue.
• /Android/obb/ subfolders matching apps you patched. These are large game data files; remove only the ones tied to apps you already uninstalled.

Open your file manager of choice (Files by Google, Samsung’s My Files, or any third-party file app you trust), navigate to Internal storage, and delete each of those folders if they exist. Empty the Recycle bin afterwards: Files by Google holds deleted items for 30 days, and some Samsung file manager builds keep their own bin.

Step 6: clean up root, su, and Magisk

This step only applies if you rooted the device to run Lucky Patcher’s actually useful features. If you stuck to the non-root mode the whole time, skip ahead to Step 7.

Lucky Patcher relies on a generic su binary for the patches that touch other apps’ data. Most Android 12 to 16 setups achieve that through Magisk, a popular systemless-root framework. Removing Lucky Patcher does not remove Magisk. If you want a clean, unrooted device back, here is the cleanup:

1. Open Magisk Manager (the Magisk app, not Lucky Patcher).
2. Tap the gear icon for Settings, scroll to the bottom, and tap Uninstall Magisk.
3. Pick Complete Uninstall. The framework restores the original boot image and the device reboots without root.

If you used a separate root manager (KingRoot, KingoRoot, SuperSU), open that app instead and use its own Unroot option. Be aware that some legacy root managers no longer cleanly unroot on Android 14 or 15; if the option is greyed out, the only reliable path back is to flash the stock firmware for your device.

Two follow-up checks worth doing after the unroot reboots the phone:

• Confirm Play Integrity passes again. Run a check with the free Play Integrity API Checker app from Play and look for MEETS_DEVICE_INTEGRITY plus MEETS_BASIC_INTEGRITY. If both pass, banking apps, Google Pay, Netflix downloads, and most online games are eligible to work again.
• Confirm Google Pay, your banking app, and any anti-cheat-protected game can be launched without an integrity error. If one of them still complains, the device profile may still be flagged from the original root. Clearing the data on that specific app, then re-launching, typically refreshes the integrity verdict.

Step 7: run Play Protect

This step matters because most malware reports tagged as “Lucky Patcher” trace back to clone APKs, not the original client, and a clone install often arrives with a second hidden package that is not removed when you uninstall the visible app.

1. Open the Play Store.
2. Tap your profile picture in the top right.
3. Tap Play Protect, then Scan.

Play Protect compares every installed package’s signature against Google’s known-bad list. If it flags anything, the safe move is to uninstall whatever it names, even if you do not remember installing it. It also re-flags any patched APKs that survived earlier steps, which is a useful second pass.

If you have a paid security app installed (Bitdefender, Malwarebytes, Kaspersky, ESET), run a full device scan afterwards. The two scanners use different signature lists, so they catch slightly different samples.

Step 8: optional, but worth it

If the Lucky Patcher install came from a clone domain you found through search, two extra cleanups make the next install safer:

• Clear your browser’s autofill and saved credentials for the clone site. A clone often serves a fake “verify your install” page that asks for an email and a fake CAPTCHA. If you typed anything, treat the credential as compromised and rotate the password on the real service.
• Sign out of any account where you reused the same password. This is the same advice that applies after any sideload from an unknown source, and it is the cheapest insurance against the worst-case outcome.

You do not need to factory reset the phone. A reset is the right move only if Play Protect flags something it cannot remove, or if the device starts behaving abnormally after the uninstall (battery drain, unexpected ads, redirected DNS, banking-app integrity refusing to clear after the Magisk unroot).

If you still want what Lucky Patcher did, install one of these instead

A clean uninstall is half the work. The other half is replacing the job Lucky Patcher was doing without going back to the same supply chain. Most of what people use Lucky Patcher for can be done by no-root tools from verified stores.

Aptoide for non-Play apps with developer signatures

Aptoide is an independent Android app store that hosts apps Google Play will not list (legitimate apps blocked by Play policy, region-locked apps, older versions for rollback) alongside the bulk of mainstream Play apps in parallel. Every app page shows the developer signature, a full version history, and a malware-scan badge so you can audit what you are about to install. If you used Lucky Patcher to get apps that were not on Play, Aptoide is the closest functional replacement with proper chain of custody on the APK and no root required.

Download:

Aurora Store for anonymous Play access

Aurora Store is a community-maintained client that pulls APKs directly from the Google Play catalog without requiring a Google account or the Play Store app. If your reason for using Lucky Patcher was avoiding Play telemetry or fetching geo-locked apps rather than patching paid features, Aurora Store solves both problems without changing the underlying APK source or needing root.

Download:

AdGuard for Android for no-root system-wide ad blocking

AdGuard for Android is an ad blocker that runs in local-VPN mode and filters traffic for every app on the device, no root required. If you reached for Lucky Patcher to strip ads from a particular app, AdGuard achieves the same result for the entire phone without needing to repackage anything. It blocks ads inside browsers, free games, and most apps that use programmatic ad SDKs, and it keeps working through app updates because nothing on the app side has been touched.

Download:

NewPipe for ad-free video and audio on YouTube

NewPipe is an open-source YouTube frontend that runs without Google Play Services and never plays ads, because it never loads the Google ad stack in the first place. If you used Lucky Patcher to strip the ads out of YouTube or to enable background play, NewPipe gives you both for free, on an open-source codebase that you can install from F-Droid without sideloading anything from a clone domain.

Download:

For the full head-to-head replacements list, see our Lucky Patcher alternatives roundup. If the question is whether Lucky Patcher’s headline tasks can be done on a stock unrooted phone in 2026, Lucky Patcher without root covers that in detail.

Frequently asked questions

Does uninstalling Lucky Patcher restore the apps I patched?

No. Lucky Patcher’s patches rewrite the target APK or its data, and removing the client does not roll those changes back. To restore a patched app to its original state, uninstall the patched build and reinstall the original from Google Play or another verified store so the developer’s signed APK is back on the device.

Will a factory reset fully remove Lucky Patcher?

A factory reset removes every app and every file in shared storage, including Lucky Patcher and its /LuckyPatcher/ folder. It will not, on its own, remove root or Magisk if those were installed: those persist through a factory reset because they live in the boot partition, not the user data partition. To return to a fully stock device, unroot through Magisk Manager before the factory reset.

Why does the Lucky Patcher icon still show after I uninstalled?

Two common causes. The icon may be a launcher shortcut that points to a removed app and just needs to be long-pressed and removed manually. Or the package on disk has a different name than com.chelpus.lackypatch (typical for a clone build), and the real installed app is still on the phone under a different name. Long-press the icon and tap App info to confirm which package is behind it.

Should I unroot before or after uninstalling Lucky Patcher?

Uninstall the client first, then unroot. The order matters because unrooting first removes the su binary that Lucky Patcher relies on, which can leave some patched apps in a half-broken state that is harder to fix. Removing the client, then fixing the patched apps, then unrooting is the cleanest sequence.

Is it safe to delete the LuckyPatcher folder in internal storage?

Yes, after the client itself is uninstalled. The folder usually holds backup APKs and dump files that nothing else on the phone references. Make sure you did not save any unrelated APKs there before deleting; the folder is shared storage and other apps can drop files into it.

Can I reinstall Lucky Patcher later without going through the same risk?

The original Lucky Patcher client is signed by ChelpuS and lives on the publisher’s own domain. If you reinstall, take the install URL from the publisher’s site rather than a search-result link, and verify the package name (com.chelpus.lackypatch) before tapping install. Most of the malware reports tagged as “Lucky Patcher” in 2026 trace back to clone domains, not the publisher’s own client.

Does Play Protect always catch Lucky Patcher?

Play Protect typically flags Lucky Patcher and most clone builds as harmful because Google’s classifier treats apps whose primary purpose is patching other apps as PHA (potentially harmful application). The flag is not a definitive malware verdict, but it is a reliable signal that the install came from outside Play and that the device should re-scan after any related uninstall to catch hidden helpers.