How to Disable App Signature Verification on Android
In this guide, we will show you the steps to disable the app signature verification on your Android device. While in most cases, the built-in Play Store might be sufficient enough to check most of the prerequisites, in some instances, you might want to make some changes to the APK before installing it. For instance, if you want to sideload an older version of an app, then doing so via the generic method might give out the INSTALL_FAILED_VERSION_DOWNGRADE error.

Likewise, if you are installing a modified APK file, then you could be greeted with the ignore invalid digest error. And you might not even be able to allow overlay apps to be installed with inconsistent signatures. But using a nifty workaround, you could now easily bypass all these issues by disabling the app signature verification on your Android device. And in this guide, we will show you how to do just that. Follow along.
- Disable App Signature Verification on Android Without Root
- Disable App Signature Verification on Android Via Root Using LSPosed Framework [Recommended] Using Lucky Patcher
Disable App Signature Verification on Android Without Root

Well, I tried quite a few non-rooted methods, namely:
- Removed the existing app via Canta and then tried to install my app.
- Removed the existing app via the adb shell command and then tried to install my app.
- Used the InstallWithOption app by disabling Verification, and then tried to install my app [NOTE: The Disable Verification feature of InstallWithOptions will not disable license verification checks; it will only disable package verification.
Unfortunately, all of them failed. I was trying to install a system app [Google Photos], so maybe that might be a reason. If you are dealing with a user app, then you can first try the aforementioned methods and see if they work out for you or not. If they don’t, then you’ll have no choice but to use the rooted methods given below.
Disable App Signature Verification on Android Via Root

There exist two methods of getting this job done: via LSPosed and Lucky Patcher. The former is a much [much] safer way of getting the job done, but the latter comes with a higher success rate. Still, first try the LSPosed method and if that doesn’t work out, then try the LSPosed method. So with that in mind, let’ss get started.
Using LSPosed Framework [Recommended]
- Root your device using Magisk , KernelSU , or APatch .
- Then, install the LSPosed Framework on your device.
- Download and install the Core Patch app on your device.
- Now open LSPosed > go to Modules > enable Core Patch.
- Then check the System Framework and restart the device.
- You can now install the problematic app without any issue.
Using Lucky Patcher
Lucky Patcher is generally not considered a safe app. Proceed ahead with caution and at your own risk.
- Download & install Lucky Patcher on your Android device.
- Then, launch it and tap on Grant in the SuperUser request.
- Now go to Toolbox > “Patch to Android” > Disable APK signature verification
- Finally, hit Apply and check out the result.
- Install Xposed/LSPatch without Root on Locked Bootloader [Video]
- Install Xposed Framework/LSPosed on Android 13 [Video]
- How to Pass the SafetyNet test after installing Xposed or EdXposed
- How to Pass SafetyNet on Rooted Pixel Experience ROM [Video]
(Cancel Reply)
Δ