Originally written by Monojit Dutta, updated by Dibyajyoti Kabi. First published June 26, 2017. Updated October 24, 2026.
Most of the build.prop tweaks that made the rounds in 2017 do nothing on a current Android phone. You can’t edit /system/build.prop directly anymore, and many of those old properties were removed years ago. The ones that still matter are better changed with Magisk’s resetprop, or through a normal setting.
This post used to list 15 tweaks you’d paste into build.prop with a root file manager. I’ll show you what build.prop is today, how to read it without root, how to change a property safely with Magisk, and which modern setting replaces each old tweak.
Key points
- build.prop is a text file of system properties. On current phones it sits on a read-only system partition.
- You can read every property without root using adb shell getprop.
- Editing the file by hand no longer works on phones that launched with Android 10 or later. Use Magisk resetprop or a Magisk module instead.
- Tweaks like DNS, density, navigation keys and animation speed now have proper settings.
- Changing ro.build properties can break Play Integrity, banking apps and Google Wallet.
What is build.prop on Android?
build.prop is a plain text file that holds system properties in a key=value format, like ro.product.model=SM-S938B. Android reads it at boot to learn the device model, Android version, build fingerprint and a set of default behaviors. Current phones also have separate prop files on the vendor, product and system_ext partitions.
You’ll find the main file at /system/build.prop. On newer phones, the same kind of file also lives at /vendor/build.prop, /product/etc/build.prop and /system_ext/etc/build.prop. Android merges all of them at boot.
That split is one reason old guides fall apart. A property you add to /system/build.prop can be overridden by a vendor file that loads later.
How do I read build.prop without root?
Connect your phone to a PC with USB debugging on and run adb shell getprop. It prints every property the system loaded, from all the prop files at once. Add a property name to see just one value. You don’t need root, and nothing on the phone changes.
- Turn on USB debugging. My guide on enabling Developer options and USB debugging shows how.
- Install ADB on your PC. My Minimal ADB and Fastboot guide covers it.
- Connect the phone and tap Allow on the USB debugging prompt.
- Run one of the commands below.
adb shell getprop
adb shell getprop ro.build.version.release
adb shell getprop ro.product.modelThe first one lists everything. The second shows your Android version, and the third shows your model number.
Why can’t I edit build.prop anymore?
Phones that launched with Android 10 or later use a system-as-root layout, and the system partition is mounted read-only and checked by verified boot. Most of them also use dynamic partitions with no spare room inside the system image. Even with root, writing to /system usually fails or stops the phone from booting.
Google’s system-as-root page says devices launching with Android 10 must use that layout. The dynamic partitions page explains how system, vendor and product now sit inside one super partition that gets resized only during updates.
So the old method of opening /system/build.prop in a root file manager, mounting it read-write and saving is gone. If you try it on a modern phone, the best case is that the change doesn’t stick. The worst case is a bootloop.
How do I change a build.prop value with Magisk?
Use resetprop, the property tool built into Magisk. Open a root shell, run resetprop with the property name and the new value, and the change applies right away without touching /system. A normal change resets on the next reboot, which makes it a safe way to test a tweak first.
You need an unlocked bootloader and Magisk installed. Make a Nandroid backup before you change anything.
- Connect the phone to your PC.
- Run adb shell.
- Run su and grant root in the Magisk prompt on the phone.
- Check the current value with getprop.
- Set the new value with resetprop.
- Test the change, then reboot to undo it if something feels off.
adb shell
su
getprop ro.sf.lcd_density
resetprop ro.sf.lcd_density 420Magisk’s tools documentation lists the other options. The -n flag sets a property without going through property_service, -d deletes a property, and -p writes a persist property to storage so it survives a reboot.
How do I make a build.prop tweak permanent?
Put it in a Magisk module. A module can include a system.prop file in the same key=value format as build.prop, and Magisk loads it with resetprop at every boot. Your /system partition stays untouched, and removing the module in the Magisk app undoes the tweak.
According to the Magisk developer guide, system.prop in a module’s folder is loaded as system properties by resetprop. For anything that needs to run later in boot, a module’s service.sh script is the recommended place.
A minimal system.prop looks like this.
ro.sf.lcd_density=420If a property change breaks something, boot into safe mode or remove the module from the Magisk app. My guide on flashing zips with TWRP helps if you’d rather install modules from recovery on a phone that still has TWRP.
Which old build.prop tweaks still work?
Very few, and most have a better replacement in Settings. DNS, screen density, navigation keys and animation speed all have built-in options now. Tweaks for scrolling, JPEG quality, call ring delay, Wi-Fi scan intervals and the old performance flags either do nothing on current Android or were removed.
Here’s how the classic 2017 list holds up.
| Old tweak | Works today? | What to use instead |
|---|---|---|
| net.dns1 and net.dns2 for faster DNS | No | Private DNS in Settings |
| ro.sf.lcd_density for a smaller UI | Sometimes | Display size in Settings, or adb shell wm density |
| qemu.hw.mainkeys to hide nav keys | No on most phones | Navigation mode in Settings |
| Scrolling speed props | No | High refresh rate in display settings |
| ro.media.enc.jpeg.quality | No | Your camera app’s quality settings |
| Animation speed props | Not needed | Developer options animation scales |
| debug.performance.tuning, stagefright and profiler props | No | No replacement needed |
| wifi.supplicant_scan_interval | No | No replacement needed |
| ro.telephony.call_ring.delay | No | No replacement needed |
| persist.sys.shutdown.mode=hibernate | No | No replacement needed |
What replaced the DNS tweak?
Private DNS. It sends every DNS lookup through an encrypted DNS-over-TLS server you pick, like dns.google or one.one.one.one. On a Pixel, go to Settings > Network & internet > Private DNS. On a Galaxy phone, go to Settings > Connections > More connection settings > Private DNS.
Google added it in Android 9, as the Android Developers blog post from 2018 explains. It does what the old net.dns1 tweak tried to do, and it works on both Wi-Fi and mobile data without root.
How do I change screen density without build.prop?
Use Display size in Settings first. On a Pixel, it’s under Settings > Display > Display size and text. On a Galaxy phone, go to Settings > Display > Screen zoom. For a custom value, run adb shell wm density with the number you want. No root needed.
adb shell wm density
adb shell wm density 420
adb shell wm density resetThe first line shows your current density. The second sets a new one, and the third puts it back to the default. A lower number makes everything smaller. Go in small steps, since a very low value can make some apps hard to use.
How do I speed up animations without build.prop?
Turn down the animation scales in Developer options. Go to Settings > System > Developer options on a Pixel, or Settings > Developer options on a Galaxy phone, and set Window animation scale, Transition animation scale and Animator duration scale to 0.5x. The phone feels quicker right away.
Google lists those options on its Developer options page. Setting them to Off removes animations entirely, but 0.5x keeps the visual cues and still feels snappy.
Can build.prop changes break apps?
Yes. Changing ro.build properties like the fingerprint, model or build type can make Play Integrity checks fail. That breaks Google Wallet, many banking apps and some games. Leave ro.build and ro.product values alone unless you know exactly why you’re changing them.
There’s another catch on Samsung phones. Samsung removed the OEM unlocking option in One UI 8, as 9to5Google reported, so most current Galaxy phones can’t be rooted at all. On those, settings and adb are your only options.
FAQ
Can I edit build.prop without root?
No. You can read it without root with adb shell getprop, but changing a property needs root. Without root, use the matching setting in Settings or an adb command like wm density, which covers most of what people used build.prop for.
Is it safe to edit build.prop?
Testing a change with Magisk resetprop is fairly safe, because a normal change goes away when you reboot. Editing /system/build.prop by hand on a modern phone isn’t safe, since it can stop the phone from booting. Make a Nandroid backup before any change.
Does a build.prop tweak survive an OTA update?
A tweak in a Magisk module usually comes back after you reinstall Magisk following the update. A direct edit to /system is wiped by every OTA, because the update writes a fresh system image. On most rooted phones, you can’t install an OTA normally anyway.
Where is build.prop located?
The main file is at /system/build.prop. Current phones also load prop files from /vendor/build.prop, /product/etc/build.prop and /system_ext/etc/build.prop. Run adb shell getprop to see the combined result from all of them.
Related guides
- How to make a Nandroid backup in TWRP
- How to install custom ROMs with TWRP
- How to flash zips on Android with TWRP
- How to change the boot animation on Android
- Download and install Minimal ADB and Fastboot
That’s it. Read your props with getprop, test changes with resetprop, and use the built-in settings for everything else.
Have a tweak you want to try? Leave a comment with your phone model (like SM-S938B or Pixel 9 Pro), your Android version and the property you want to change, and I’ll help you check whether it still works.
