-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Signature Spoofing
You need a ROM that supports signature spoofing. Some custom ROMs are patched to support signature spoofing out of the box, however most ROMs will require a patch or a Xposed module. Please ask your ROM developer if unsure.
The following ROMs have out-of-box support for signature spoofing.
- AospExtended: Must be enabled in Settings > Apps > Advanced (gear icon) > App Permissions > Spoof package signature
- ArrowOS: microG will ask for Signature Spoofing authorization
- CalyxOS: Bundled with microG
- CarbonROM: microG will ask for Signature Spoofing authorization
- crDroid: microG will ask for Signature Spoofing authorization
- /e/: Bundled with microG
- iodéOS: Bundled with microG
- LineageOS (from 2024/02/26)
- LineageOS for microG: Bundled with microG
- OmniROM 5: Must be enabled at the bottom of the developer settings first
- OmniROM 6/7: Must be enabled in Settings > Apps > Advanced (gear icon) > Additional permissions > Spoof signature
- MarshRom: Must be enabled in Settings > Apps > Advanced (gear icon) > Additional permissions > Spoof signature
Also there is another maintained list of custom ROMs that include the signature spoofing patch.
If you have the Xposed Framework installed, the following module will add support for signature spoofing: FakeGApps fork by whew-inc
As alternative, you can also patch your already-installed ROM using one of these methods:
- Using NanoDroid-patcher by Nanolx (up to Android 11), without any computer interaction and it will auto-patch every updated ROM;
- Using Tingle by ale5000;
- Using Haystack by Lanchon (Haystack can, optionally, add a simple UI to control spoofing, similar to the one offered by OmniROM 5).
NOTE: Most patchers require that the ROM to be patched is NOT odexed.
If you are a ROM developer or just do custom builds for whatever reason, you can download and include the patch from here or here.
Once you've downloaded the correct patch for your build version, change to the frameworks/base directory of your build tree and run patch -p1 -i "path/to/where/you/saved/the/patch", changing the path to the appropriate path of where you saved the patch file.
If it runs without error, your build will have Signature Spoofing enabled.
NOTE: The signature spoofing patches have not yet been updated with the latest changes, so it is not currently possible to fool the updated signature check code with these patches.
microG Services tests and diagnoses signature spoofing but, unfortunately, it cannot be installed on devices that have Google Play Services.
For testing on such devices you can use Signature Spoofing Checker instead.
NOTE 1: Unfortunately, many ROMs only enable signature spoofing for microG, which makes Signature Spoofing Checker almost useless.
NOTE 2: Signature Spoofing Checker has not been updated in a while, so it is not able to fully verify the updated signature spoofing patches.