Device Changer Installation Guide: Android Testing Environment Setup

Before You Start

• Create a full backup (internal files + apps + photos)
• Charge the phone to at least 70%
• Install ADB/Fastboot on your PC and verify USB cable quality
• Enable Developer options, USB debugging, and OEM unlock

Important: Bootloader unlock usually wipes all data and can affect warranty status.

Step 1 — Unlock Bootloader

1. Check whether your device brand requires an unlock code (Xiaomi, Motorola, etc.)
2. Reboot to fastboot mode
3. Run the unlock command for your device model
4. Confirm unlock on the phone screen and complete initial setup again

Step 2 — Install Root (Magisk / KernelSU / APatch)

1. Extract or obtain your stock boot image for the current firmware
2. Patch boot image using your root solution (Magisk is the most common)
3. Flash patched image via fastboot and reboot
4. Open root manager app and verify root works correctly

Step 3 — Install LSPosed

1. Enable Zygisk (for Magisk-based setups)
2. Install LSPosed package compatible with your Android version
3. Reboot and open LSPosed Manager
4. Confirm LSPosed service status is active

For scope rules, reboot requirements, and validation, see the LSPosed Module Guide.

Step 4 — Install and Configure Device Changer

1. Install Device Changer APK from the official source
2. Open LSPosed Manager and enable the module for Device Changer
3. Set scope: select target apps where testing hooks should apply
4. Grant root permissions when prompted
5. Reboot the phone

Next, wire this setup into repeatable runs using Android testing workflows (smoke, regression, and release sign-off).

Step 5 — First Launch and Verification

1. Open Device Changer and enter your access code
2. Set test values in Faker ID and enable required switches
3. Apply changes and reopen target app
4. Check System Info or app behavior to confirm simulation is active

When you move into structured QA passes, follow Android QA testing checklists so results stay comparable across builds.

Troubleshooting

If identifiers or profiles still look wrong after reboot, confirm what the target app reads against your saved profile using device simulation documentation and System Info.

Module does not work

• Recheck scope in LSPosed (selected target apps)
• Verify module is enabled and LSPosed is active
• Restart device after any scope/module changes

No root access inside app

• Grant root prompt in manager app
• Disable battery optimization for root manager and Device Changer
• Update root solution and reboot

App still sees old identifiers

• Force stop target app and clear app cache
• Apply values again and reboot if required
• Use a different profile from Device Profiles

Related pages

Android testing · Device simulation · FAQ guide