XPOSED IMEI Changer Pro 1.3 MOD APK 1.3

Description

Xposed IMEI Changer Pro APK is a legacy Xposed module for rooted Android phones. When a chosen app requests the phone's IMEI from Android, the module can hand that app a substitute number instead. On a device you own, this lets you see how the app reacts to the original identifier versus the replacement. The modem and mobile network keep using the original identifier. The module cannot restore a missing IMEI.

The APK cannot run on its own. You need an active Xposed-compatible framework. In LSPosed, the app you want to test must also be enabled in the module's scope. Root access alone cannot load the module or add an app to its scope.

Different apps may show different numbers

In code, the module hooks two Android telephony methods: getDeviceId() and getImei(). A scoped app that calls either one can receive the module's answer rather than the real IMEI. Software that relies on Android ID, reads another identifier, reuses a value saved in its own data, or never calls those methods falls outside the module's reach.

LSPosed loads a module only into the apps placed in its scope. The dialer, Settings, and the target app are handled separately, so they do not have to display the same number. A changed value on one screen does not prove that every app receives it.

Random does not mean one number per session

Random mode produces a new numeric answer every time a hooked method is called. It does not select one random number and hold it until the next reboot. The same app may read one value at launch and another later, and the two will not necessarily match. Choose the fixed setting if the app expects its device number to stay the same.

Manual mode uses whatever number you enter each time a hooked call arrives. When you tap Apply, that number is saved, and a reboot prompt follows. After the phone restarts, the saved choice stays active. A later reboot will not bring back the original automatically. To return to the original, select it in the app and tap Apply.

The input box performs very little validation. It accepts up to 18 characters. A value with 14 or 16 digits triggers no warning, even though a standard IMEI has 15 digits. The check digit is not verified either. The app saves whatever you type, and you may only notice a problem once the target software rejects the number.

A dual-SIM phone does not get separate controls for each slot. Both slot-aware hooks share one setting. In fixed mode, SIM 1 and SIM 2 both receive the same replacement, so the module cannot store two numbers independently.

A successful install does not confirm Android compatibility

The code was written for an older Xposed and Android environment. It may install on Android 13, 14, 15, or 16, but that only shows the package manager accepted the APK. It does not show that the hooks attached correctly or that the target app still uses them. Android 10 and later also restrict which ordinary apps can read IMEI data.

Compatibility has to be judged app by app. A loaded module is not enough if the target app sits outside its scope or reads a different identifier. There is no reliable evidence that it works across all recent Android releases.

Check the result inside the app under test, not only in the dialer or Settings. Seeing the original IMEI means the read was not replaced. A blank result means the app received no IMEI, while Android ID is a separate identifier that this module does not change.