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 selected app requests the phone's IMEI from Android, the module can hand that app a replacement number instead. On a device you own or manage, you can compare how an app behaves with the original identifier versus the replacement. The modem and mobile network keep using the original identifier. This module cannot fix 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 added to the module's scope. Root access alone cannot load the module or assign an app to its scope.

Different apps may report different numbers

In code, the module hooks two Android telephony methods: getDeviceId() and getImei(). A scoped app that calls either method can receive the module's response in place of the original IMEI. Software that relies on Android ID, reads a different identifier, reuses a value saved in its own data, or never calls those methods is outside the module's reach.

LSPosed loads a module only into apps placed within 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 generates a fresh numeric response each time one of the hooked methods is called. It does not choose a single random number and hold it until the next reboot. The same app may read one value at launch and a different one later, and the two will not necessarily match. Use the fixed setting when an app expects its device number to remain unchanged.

Manual mode uses the number you enter each time a hooked call arrives. Tap Apply, and that number is saved. A reboot prompt follows. After the phone restarts, the saved choice stays active. A later reboot will not restore the original on its own. To go back to the original number, select it in the app and tap Apply.

The input box performs very little validation. It accepts up to 18 characters. An entry with 14 or 16 digits triggers no warning, even though a standard IMEI contains 15. The check digit is not verified either. The app saves whatever you typed, and you may not notice the mistake until the target software rejects the number.

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

A successful install does not confirm Android compatibility

The code targets 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 says nothing about whether the hooks attached correctly or whether 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 when the target app sits outside its scope or reads a different identifier. There is no reliable evidence of universal compatibility across recent Android releases.

Check the result inside the app under test, not only in the dialer or Settings. The original IMEI means the read was not replaced. A blank result means the app has no IMEI to report, while Android ID remains a separate identifier that this module does not touch.