← Back to home
Installation Guide
Full setup checklist: from root preparation to your first reproducible QA scenario.
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
- Check whether your device brand requires an unlock code (Xiaomi, Motorola, etc.)
- Reboot to fastboot mode
- Run the unlock command for your device model
- Confirm unlock on the phone screen and complete initial setup again
Step 2 — Install Root (Magisk / KernelSU / APatch)
- Extract or obtain your stock boot image for the current firmware
- Patch boot image using your root solution (Magisk is the most common)
- Flash patched image via fastboot and reboot
- Open root manager app and verify root works correctly
Step 3 — Install LSPosed
- Enable Zygisk (for Magisk-based setups)
- Install LSPosed package compatible with your Android version
- Reboot and open LSPosed Manager
- Confirm LSPosed service status is active
Step 4 — Install and Configure Device Changer
- Install Device Changer APK from the official source
- Open LSPosed Manager and enable the module for Device Changer
- Set scope: select target apps where testing hooks should apply
- Grant root permissions when prompted
- Reboot the phone
Step 5 — First Launch and Verification
- Open Device Changer and enter your access code
- Set test values in Faker ID and enable required switches
- Apply changes and reopen target app
- Check System Info or app behavior to confirm simulation is active
Troubleshooting
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