Many advanced users are faced with the need to change system information about their device. Most often, this is required to install applications that are not supported by a specific model, or to bypass carrier restrictions. Device ID (Model ID) is a line in the system file that tells Google Play servers and other services what kind of gadget you have in your hands.
The procedure for changing the model is not standard function in the settings menu. This is a deep modification of the system, affecting a file build.prop or using special kernel modules. Without understanding the principles of operation Android OS such actions can lead to unstable operation of the system or complete loss of warranty. However, with the right approach, this opens up access to hidden functions and exclusive content.
In this article we will analyze in detail safe ways to replace the model, the necessary tools and pitfalls that are silent about in official instructions. The knowledge gained will help you adapt the device to your unique tasks without fatal consequences for the firmware.
Why change the smartphone model at all
The main reason why users are looking for ways to change the Android phone model is access to content. The application store Google Play filters apps based on the hardware characteristics declared by the manufacturer. If your budget smartphone can technically handle a heavy game, but it is blocked for your model, changing the ID solves the problem.
Another scenario is related to functional limitations. Some functions, such as call recording or high quality video in instant messengers, are available only for certain brands like Samsung or Google Pixel. Substituting a model allows you to activate these features on third-party devices. System limitations Often they are of a software rather than hardware nature.
This is also necessary for enthusiasts involved in testing applications. Developers need to test the operation of their software on different configurations without buying dozens of physical devices. Emulating another model is a quick way to check compatibility.
⚠️ Attention: Changing the model may disrupt Google Pay (Mir Pay) services and banking applications as they check system integrity and compliance with security certificates.
Preparing the device for modifications
Before making changes to system files, you must ensure data security. Any intervention in build.prop carries the risk of “bricking” the device if the syntax is broken. Therefore, the first step should always be to create a full backup.
You will need to obtain advanced access rights. The model cannot be changed using standard methods, since the system partition is write-protected. You will need root access or an unlocked bootloader to install custom recovery. Without this, further actions are impossible.
Be sure to enable USB debugging in the developer menu. This will allow you to connect your smartphone to your computer to transfer files and use debugging tools like ADB. Also make sure that the battery charge is at least 60% so that the device does not turn off at a critical moment.
- 📱 Make a full backup of your data via TWRP or cloud services.
- 🔓 Unlock the Bootloader through the manufacturer's settings.
- 💻 Install ADB and Fastboot to your computer.
- 🔋 Charge your phone to at least 70% before starting work.
☑️ Ready for intervention
Method 1: Change through the build.prop file
This is a classic method that works on most versions of Android up to 11 inclusive. The file build.prop contains key variables that describe the device. We need to find the line responsible for the model and change its value.
To edit you will need a file manager with superuser rights, for example Root Explorer or MT Manager. Go to the directory /system and find the file build.prop. Open it as text and find the line ro.product.model.
Replace the value after the equal sign with the model of the device you want to emulate. For example, if you want to pretend Google Pixel 6, enter the appropriate model code. After saving the file, be sure to change the access rights (Permissions) to rw-r--r-- (644), otherwise the system will not boot.
ro.product.model=Pixel 6ro.product.brand=google
ro.product.manufacturer=Google
After making the changes, you must reboot the device. When loading, the system reads new parameters. If you make a mistake in syntax or permissions, your phone may get stuck on the logo. In this case, you will have to restore the file through recovery.
What to do if the phone does not boot?
If after editing build.prop the device goes into bootlap, boot into Recovery mode. Connect your phone to your PC and run the command via ADB: adb pull /system/build.prop (to save a copy of the error), then edit the file on your PC and upload it back: adb push build.prop /system/build.prop. Don't forget permissions 644.
Method 2: Using Magisk modules
For modern versions of Android, where the partition /system is read-only (Systemless Root), the method of directly editing the file will not work or will be reset during the update. This is where the root access manager Magisk and special modules come to the rescue.
The module MagiskHide Props Config is the gold standard for such a task. It allows you to change system properties (props) on the fly without affecting the physical partition of the system. It is safer and reversible. After installing the module through the Magisk menu, you need to run the configuration script.
Start a terminal (for example, Termux) and enter the command su to obtain superuser rights. Then enter the command props. A text menu will open where you need to select the item to edit device parameters. Follow the script prompts to replace the model, brand and manufacturer.
- 🛡️ The method does not violate the integrity of the system partition (Systemless).
- 🔄 It is easy to roll back changes through the Magisk menu.
- ⚙️ Allows you to change many parameters at the same time (serial number, assembly fingerprint).
- 📲 Works on Android 12, 13 and later, where direct writing is prohibited.
Use the Universal SafetyNet Fix module together with MagiskHide Props Config to hide the fact of receiving root access from banking applications after changing the model.
Table of popular model identifiers
For successful substitution, you need to know the exact name of the donor model. Below is a table with popular identifiers that are often used to unlock features or access beta versions of software.
| Brand | Device model | Identifier (Model) | Purpose of spoofing |
|---|---|---|---|
| Pixel 6 Pro | raven | Access to exclusive camera features | |
| Samsung | Galaxy S22 Ultra | SM-S908B | Activation of call recording and Samsung Pay |
| OnePlus | OnePlus 9 Pro | LE2123 | Unlocking 90 Hz in games |
| Xiaomi | Mi 11 Ultra | M2102K1G | Testing MIUI functions on other devices |
| Sony | Xperia 1 III | XQ-BC72 | Access to professional mode cameras |
Please note that simply changing the model line is sometimes not enough. Some applications check the combination of ro.product.brand and ro.product.manufacturer. Make sure that all three parameters correspond to the real donor device.
⚠️ Attention: Using other people's identifiers to override game licensing restrictions may result in the developer blocking your account. Use this knowledge responsibly.
Problems and possible risks
You should not think that the procedure will pass without a trace for the system. Security certificates may be compromised. Apps that use the Google SafetyNet or Play Integrity API will stop working. This is critical for the banking sector and payment systems.
Automatic system updates (OTA) may stop receiving or fail. The update server checks the device model with the firmware. If they do not match, the update will not install. You will have to flash the device manually via your computer.
In rare cases, unstable operation of the radio module may occur. If a device model with a different set of frequencies or regional features is replaced, problems may arise with network search or GPS operation. You can return everything back, but it will take time.
The safest way to change the model is to use Magisk modules, since they do not directly modify the system partition and allow you to easily roll back the changes.
Frequently asked questions (FAQ)
Is it possible to change the phone model without Is Root right?
No using standard means. However, some development applications allow you to emulate a different model within the sandbox of the application itself, but this will not change the model for the entire system and Google Play. For a global change, editing system files is required.
Will changing the model reset the warranty?
Editing a text file itself is not visually visible. But to add it, you will most likely have to unlock the bootloader or obtain root access. The unlocked bootloader flag (Knox on Samsung) is fixed forever and is grounds for denial of warranty service.
How to return the original model back?
If you used Magisk, simply remove the module in the application and reboot. If you edited build.prop manually, you need to restore the original file from a backup using Recovery mode or reflash the stock system image.
Does this affect the IMEI of the device?
No, the phone model and IMEI are different identifiers. Changing the model via build.prop does not affect IMEI. However, there are separate tools for changing IMEI, but their use is illegal in most countries and can lead to blocking of the device by the operator.
Why does Google Play still say "Device not supported"?
Perhaps the application requires not only a specific model, but also certain hardware features (for example, a ToF sensor, a specific version of OpenGL, or pixel density) that are not physically present in your device. In this case, changing the model will not help.