How to Clone an APK by Changing Its Package Name
To clone an APK by changing its package name, the APK usually must be decompiled, the package identifier in the manifest and related code must be updated, then the app must be rebuilt and signed. A simple file rename does not work. This method is mainly useful for testing, open-source APKs, or older apps that do not check internal identifiers.
Steps
- Back up the original APK
Save the source APK before editing. Rebuilding changes the signature, so the original file stays useful for comparison.
- Decompile the APK
Use an APK editor such as APKTool or a similar reverse-engineering tool. This exposes the manifest, resources, and smali code.
- Change the package name
Edit the package name in
AndroidManifest.xmland update any hardcoded package references in smali, resources, and config files. If the app uses a namespace or application ID, change that value too. - Rebuild and sign the APK
Recompile the package, then sign it with a new keystore. Android will not install an unsigned or improperly signed APK.
- Install and test the clone
Install the rebuilt APK on the phone. If the clone installs as a separate app, the package name change worked. If the app crashes, more internal references still need editing.
| Option | Best For | Limitation |
|---|---|---|
| APKTool | Manual package editing | Requires code fixes and signing |
| App Cloner | Simple duplicate apps | Limited support for protected apps |
| Android Studio | Test builds and controlled APK changes | Not ideal for casual APK cloning |
Common Issues and Fixes
- Install fails with “App not installed” — The package name or signature still conflicts with an existing app — Change the package ID fully and sign with a new certificate.
- App opens then crashes — Hardcoded package references still point to the old name — Search the decompiled files for the original package string and replace it.
- Clone installs but shares data with the original — Backend account sync or device identifiers remain the same — Clear app data and use a separate account where possible.
- Google Play or security checks block launch — The app uses integrity or anti-tamper protection — Protected apps often cannot be cloned reliably.
- Update cannot be installed later — The new APK uses a different signing key — Treat the clone as a separate app build.
Quick Tips
🤔Note:
Samsung Secure Folder or Dual Messenger can duplicate some apps, but they do not truly change the APK package name.
💡Protip:
Changing the package name alone is not enough if the app stores the old ID inside code or configuration files.
- Banking, payment, and many social apps often fail after cloning because of anti-tamper checks.
- Keep the original version code logic consistent when testing repeated rebuilds.
Which app can I use to clone another app?
APKTool is a common choice for manual APK cloning because it allows package-name edits and rebuilds. App Cloner is easier for basic duplication, but protected apps may still fail.
Can a package name change install the same APK twice?
Yes. A changed package name lets Android treat the APK as a different app, so two copies can install side by side. Shared login data, server-side checks, or signature checks can still limit duplicate use.
