Changing the model of an Android device through root access is a procedure that may be needed to bypass application restrictions, test software or disguise the device as another model. However, this process is fraught with serious risks: from loss of warranty to complete failure of the smartphone. Unlike standard settings, where the phone model is displayed only for information, editing system files requires a deep understanding of the operation Android and the consequences of such changes.
It is important to understand that changing the model in build.prop or through specialized utilities does not change your Samsung Galaxy A52 v Google Pixel 7 physically - only the identifiers that the system and applications โseeโ change. Some apps (for example, banking or secure games) can block work on โfakeโ devices, and updating the firmware after such manipulations will become impossible without returning the original parameters.
In this article we will look at legal ways to change the model, tools for editing system files, and also tell you how to minimize risks and return everything back if something goes wrong. If you are new to the world root access, we recommend that you first learn the basics of working with ADB, Magisk and backup NANDroid.
Why do users change the Android device model?
The main reasons for changing the smartphone model through root access usually associated with bypassing software restrictions or testing:
- ๐ฎ Access to games/applicationslimited by device model (for example, beta versions or regional releases).
- ๐ฑ Cheating verification systems (for example, for installing firmware intended for other devices of the same line).
- ๐ Compatibility testing Software or mods that do not officially support your model.
- ๐ก๏ธ Disguise from trackers or analytical systems (although this is weak protection).
- ๐ง Experiments with customization interface, where the device model affects the displayed settings.
However, there is a downside: many services (for example, Google Pay, Netflix or banking applications) block devices with changed system parameters due to the risk of fraud. In addition, some firmware may refuse to be installed if the model in build.prop does not match the real one.
โ ๏ธ Attention: Changing the device model can lead to loss of OTA updateserrors in the operation of the sensors or even a โbrickโ (breakage) of the smartphone if the new parameters conflict with the hardware. Always create NANDroid backup before editing system files.
Preparation: what needs to be done before changing the model?
Before you start editing system files, complete the required preparatory steps:
- Get root access (for example, through Magisk or SuperSU). Without root access, it is impossible to change the model.
- Create a backup copy the current state of the system. It is best to do
NANDroid backupvia TWRP or a similar recovery. - Check compatibility of the target model with your device. For example, you cannot replace Xiaomi Redmi Note 10 with Samsung Galaxy S22 โthis will lead to critical errors.
- Install a file manager with root access (for example, Root Explorer or FX File Explorer).
- Download the original firmware for your model in case of recovery.
Also make sure that the device has enough battery charge (at least 70%) and disable all protections that can block changes to system files (for example, Knox on Samsung or MIUI Optimization on Xiaomi).
Root access was obtained (Magisk/SuperSU)|NANDroid backup was created|Compatibility of the target model was checked|Root file manager was installed|Original firmware for recovery was downloaded-->
If you plan to change the model to bypass restrictions in games (for example, in PUBG Mobile or Genshin Impact), please note that many anti-cheats will detect such changes and block your account. In this case, it is better to use alternative methods, for example, emulators.
Method 1: Editing the build.prop file. manually
The main system file where information about the device model is stored is /system/build.prop. It can be edited manually through any text editor with root access. Here are step-by-step guide:
- Open a file manager with root access and go to the folder
/system/. - Find file
build.propand make a copy of it (just in case). - Open the original file in a text editor (for example, through QuickEdit or the built-in editor Root Explorer).
- Find lines starting with:
ro.product.model=ro.product.brand=
ro.product.name=
ro.product.device= - Change the values to the desired ones (for example, instead of
ro.product.model=RMX3363specifyro.product.model=SM-G991Bto disguise as Samsung Galaxy S21). - Save the changes and reboot the device.
After reboot, check the new model in the settings (Settings โ About phone โ Device model) or through command:
adb shell getprop ro.product.model
โ ๏ธ Attention: Some manufacturers (for example, Huawei or Oppo) use additional checks in the boot section (boot.img). editingbuild.propmay not work or cause a boot loop (bootloop).
What other parameters can be changed in build.prop?
In addition to the model, build.prop stores:
- ro.product.manufacturer (manufacturer)
- ro.build.version.release (Android version)
- ro.build.id (Build ID)
- ro.product.cpu.abi (processor architecture)
Changing these settings may affect application performance or compatibility, so only edit them if you are absolutely sure consequences.
Method 2: Using applications to change the model
If manual editing build.prop seems difficult, you can use specialized utilities Below are proven applications that automate the process:
| Application | Requires root? | Features | Link (source) |
|---|---|---|---|
| BuildProp Editor | Yes | Allows editing build.prop via a convenient interface, with the ability to rollback changes. |
XDA Developers |
| Root Essentials | Yes | Includes an editor build.prop, as well as tools for fine-tuning the system. |
Google Play |
| Magisk Module: Props Config | Yes (Magisk) | Module for Magisk, which changes the properties of the device without direct editing. (archive) build.prop. |
GitHub (Magisk) |
| Xposed Framework + module | Yes (Xposed) | Deprecated method, but some modules (eg. Xposed BuildProp Editor) are still working. | XDA (archive) |
The most secure option is Magisk Module: Props Config, since it does not make changes directly to the system partition, but uses a masking mechanism. You can install it via Magisk Manager:
- Open Magisk Manager and go to the section
Modules. - Click
+and select the downloaded module file Props Config. - Reboot the device.
- After reboot, open Terminal i enter:
suprops - Follow the on-screen instructions to select a new model.
The advantage of this method is that the changes are applied on the fly and do not affect the original build.propwhich makes rollback easier.
Manually editing build.prop|BuildProp type applications Editor|Magisk Module: Props Config|Another method-->
Checking results and possible problems
After changing the device model, you need to check whether the new parameters are applied correctly in several ways:
- ๐ฑ In the phone settings:
Settings โ About phone โ Device model. - ๐ Via
ADB:adb shell getprop ro.product.model - ๐ On device definition sites (for example, WhatIsMyDevice or DeviceInfo).
- ๐ฏ In applications that previously blocked your model (for example, games or beta versions of software).
If the model has not changed or the device behaves unstable, the following problems are possible:
| Problem | Possible reason | Solution |
|---|---|---|
| The model has not changed | The file build.prop was not saved or overwritten by the system |
Check the rights to the file (chmod 644 /system/build.prop) and repeat editing |
| The device does not turn on (bootloop) | Incompatible parameters in build.prop or error when saving |
Restore the backup via TWRP or flash the original firmware |
| Applications do not work | The target model is not supported by the software or is blocked by anti-cheat | Return the original model or use disguise modules (for example, MagiskHide) |
| OTA updates do not arrive | Update servers do not recognize device | Temporarily return the original model to install the update |
Critical error: If after changing the model the device stops booting and there is no backup, the only way out is to flash the firmware via Fastboot or ODIN (for Samsung). In some cases, you may need to flash the bootable one. section (boot.img), if the changes affected critical parameters.
How to return the original device model?
If after experiments you decide to return the original settings, do it in one of the following ways:
- Restoring from a backup:
- Boot into TWRP (or another custom recovery).
- Select
Restoreand specify the path to the savedNANDroid backup. - Confirm recovery and reboot the device.
- Manual editing
build.prop:- Open the file
/system/build.propand return the original values. - If the file is damaged, copy it from a backup or original firmware.
- Open the file
- Removing Magisk modules:
- Open Magisk Manager and remove the module Props Config.
- Reboot the device.
- Download stock firmware for your model from the official website of the manufacturer.
- Flash it via Fastboot, ODIN or SP Flash Tool (depending on the brand).
If you used Magisk Module: Props Config, just deactivate the module - the original parameters will be restored automatically after reboot.
โ ๏ธ Attention: After returning the original model, some applications (for example, banking) may require re-registration of the device or data reset. This is due to the fact that they are tied to unique identifiers that have changed.
Before returning the original model, take a screenshot of the current settings in build.prop or save the file separately. This will help you quickly restore the settings if you want to repeat the experiment later.
Risks and consequences of changing the Android model
Even if the procedure was successful, changing the device model can have long-term consequences:
- ๐ซ Loss of warranty: Any manipulation of system files will void the warranty manufacturer.
- ๐ Problems with updates: OTA updates may not install or lead to errors.
- ๐ก๏ธ Blocking services: Google Pay, Netflix, banking applications and protected games (for example, PUBG or Call of Duty Mobile) may deny access.
- ๐ง Unstable operation: Incompatible parameters can cause lags, overheating or random reboots.
- ๐ก Problems with the network: Some models have unique modem settings, and replacing them may lead to loss of connection.
Owners of devices with locked bootloader (for example, Samsung s) need to be especially careful data-i="233">or Knox or Xiaomi with Mi AccountOn such smartphones, changing system files can lead to activation of protection and complete blocking of the device.
If you changed the model to bypass regional restrictions (for example, to install firmware for another countries), please note that this may violate the certification of the device for local networks (for example, in the USA or in Russia). inappropriate application, consider alternatives: emulators, virtual machines or purchasing a supported device. FCC in the USA or Gossvyaznadzor in Russia).
Changing a device model is always a compromise between temporary benefits and long-term risks. If the goal is simply to install a non-optimal application, consider alternatives: emulators, virtual machines, or purchasing a supported device.
FAQ: Frequently asked questions about changing the Android model
Is it possible to change the model without root access?
No, without root access it is impossible to edit system files Some applications. They promise to โdeceiveโ the system without root, but they work only at the level of individual apps (for example, through Xposed for older versions of Android) and do not change the real model of the device.
Will Google Pay work after changing the model?
Rather everything, no. Google Pay checks the integrity of the system through SafetyNet, and any changes in build.prop or the presence of root access will lead to blocking of the service. To restore functionality, you need to roll back the changes and hide the root (for example, through MagiskHide).
Can I change the model on an iPhone? or iPad?
No, these instructions only apply to devices on Android. On iOS similar manipulations are impossible without hacking (jailbreak), and even in this case they are extremely limited due to the closed architecture Apple.
How to check whether the system recognizes a new model?
In addition to visual checking in the settings, use the commands:
adb shell getprop ro.product.model
adb shell getprop ro.product.brand
You can also install applications like DevCheck or AIDA64that show complete information about the device, including hidden ones parameters.
What to do if, after changing the model, the sensors stop working?
This means that the new model has different drivers or configurations for sensors (for example, a gyroscope or compass). Return the original parameters to build.prop or restore the backup. If the problem persists, you may need to flash the kernel (kernel) or modem software.