[Q] Is it possible to flash stock build.prop ?? - Moto G Q&A, Help & Troubleshooting

Sorry for my bad english.
I got a soft brick in my Moto G by changing this line in build.prop
ro.sf.lcd_density=320
for this line
ro.sf.lcd_density=260
My question is if is possible to flash the stock build.prop in /system folder?? Because I didn't make a backup of any picture and I wouldn't like to lose everything.
If it is possible. Would you bring me the .zip file?
By the way, I have this rom in my phone "US_retail_XT1032_KXB20.9-1.8-1.4_CFC.xml"

Easy:
1) get stock build.prop
2) adb push c:\build.prop /system
3) Reboot
alternatively to 1) you can
a) adb pull /system/build.prop c:\
b) edit build prop with editor
c) adb push c:\build.prop /system
(had the same problem with density=1320)

MrKra said:
Easy:
1) get stock build.prop
2) adb push c:\build.prop /system
3) Reboot
alternatively to 1) you can
a) adb pull /system/build.prop c:\
b) edit build prop with editor
c) adb push c:\build.prop /system
(had the same problem with density=1320)
Click to expand...
Click to collapse
Where do get the stock build prop from for xt1032 4.4.2?

Hello What if I don't have adb commands to use as i didn't have developer options enabled after factory reset

Related

[Q] How to modify build.prop on emulator?

I want to change the build.prop file on my emulator.
I searched the forum, found the instructions, and followed them. However, it still doesn't work.
Here are the steps I have done:
From command line:
emulator –avd <device> –partition-size 128
adb pull /system/build.prop
edit build.prop
adb mount
adb push build.prop /system/build.prop
adb shell rm /system/app/SdkSetup.apk
Close emulator, delete the files: userdata-qemu.img, userdata.img, cache.img
from avd\<device> directory
start emulator:
emulator –avd <device>
adb pull /system/build.prop
I see the original build.prop file, not the modified one.
I can also see SdkSetup.apk in system/app,
so the the emulator is reverted back to its original stage.
Am I missing something?
Please help.
Your emulator is running from the stock system.img file, you need to either copy it to the avd directory and specify it as the one to load (which should allow you to change it) or find one that is already modified. I had difficulty with the emulator when I was working on rooting and installing the marketplace but as soon as you get a system.img file you should be good to go.
It works! Thanks a lot
unable to edit build.prop
I have same problem as you have i.e even after push the build.file change are not reflected in file when i pull the file next time. please suggest
study_android said:
I have same problem as you have i.e even after push the build.file change are not reflected in file when i pull the file next time. please suggest
Click to expand...
Click to collapse
salex01 said:
I want to change the build.prop file on my emulator.
I see the original build.prop file, not the modified one.
so the the emulator is reverted back to its original stage.
Click to expand...
Click to collapse
I have the same problem
salex01 said:
It works! Thanks a lot
Click to expand...
Click to collapse
Please, how to settle the problem
Making Persistent Changes to an Android Emulator (http://blog.thecobraden.com/2012/06/making-persistent-changes-to-android.html)

[Q] HELP - Changed LCD Density and EVERYTHING is so tiny.

Ok so I was going through this post
http://forum.xda-developers.com/showthread.php?t=1193245
and I used to own the HTC EVO 4G, and I liked the lower LCD Density, so now I own the HTC Sensation 4G, and I wanted to do the same. I downloaded the LCDDensity app from the market, to find out that it doesn't work at all, so I followed the steps from this post and I thought I changed the density to 200, and in reality judging from the way everything looks, the editing of the file didnt register the last 0, so looks like the LCD Density is set to 20... is there any way I can edit that file or gain a new one, because I can not read anything on the phone as EVERYTHING is super small.
Hello:
In a command prompt:
- adb pull /system/build.prop
- edit the file in Windows (put ro.sf.lcd_density=240)
- save the file
- adb push build.prop /system/
- adb reboot
You should then be ok
Or restore your nandroid you made before doing the changes
anthrax132 said:
Hello:
In a command prompt:
- adb pull /system/build.prop
- edit the file in Windows (put ro.sf.lcd_density=240)
- save the file
- adb push build.prop /system/
- adb reboot
You should then be ok
Click to expand...
Click to collapse
+1
I'm the one who started the post he is referring to. I should have put this information in there for accidents.
Do you have a screen shot?
maybe you first need to remount /system with write access:
adb shell mount -o remount rw /system
anthrax132 said:
Hello:
In a command prompt:
- adb pull /system/build.prop
- edit the file in Windows (put ro.sf.lcd_density=240)
- save the file
- adb shell mount -o remount rw /system
- adb push build.prop /system/
- adb reboot
You should then be ok
Click to expand...
Click to collapse

Replaced wrong build.prop and local.prop

I've been stupid enough and replaced my modified build and local.prop files on B310 ROM with the ones I've backed up from my B121SP06 ROM and after I've rebooted the phone it just stays on "Honor, powered by android" logo. Is there some way I can't replace those files with the originals before the intervention ( I have them on my SD card)? I can boot into recovery or in bootloader, also I can flash CWM recovery.
doctorat said:
I've been stupid enough and replaced my modified build and local.prop files on B310 ROM with the ones I've backed up from my B121SP06 ROM and after I've rebooted the phone it just stays on "Honor, powered by android" logo. Is there some way I can't replace those files with the originals before the intervention ( I have them on my SD card)? I can boot into recovery or in bootloader, also I can flash CWM recovery.
Click to expand...
Click to collapse
I had also problems with these two files.
Install cwm on your phone and start your phone in cwm-mode to use adb
in cwm you have to mount system, data and cust
open a command line and use adb as following:
"adb remount"
"adb pull /system/build.prop" --> this will download the build.prop-file to your local folder, where your adb-file is located. At this point you can also download another file like your mentioned backup of the build.prop. for the local.prop-file you have to use: "adb pull /data/cust/prop/local.prop"
When you are ready with changes on the two files or you just want to upload the right ones to your phone back use this command:
"adb push build.prop /system/build.prop" and/or "adb push local.prop /data/cust/prop/local.prop" --> it will copy the file build.prop or local.prop from the local folder, where your adb-file is located to the phone.
After uploading the files to your phone you have to fix permissions:
"adb shell chmod 644 /system/build.prop" and/or "adb shell chmod 644 /data/cust/prop/local.prop"
reboot your phone via cwm.
This is how it worked for me. I hope it will help you too. :fingers-crossed:
By the way, I'm actually looking for a stock local.prop-file for the L04 (from the firmware B109SP1 or B114) or the L12 (from the firmware B118 or B607). Do you have one of these?
Thanks for the reply but I've already succeeded flashing B313. I've been trying with "adb pull" command but it was saying "no device found " or something similar.
My phone is H60-L02 so i don't have the files you're looking for.

[HELP] [ADB] Is adb rooted by default?

I have seen many tutorials which guide to press su directly in cmd (Command Prompt) after entering the command, does it mean that the shell is in root mode but only through the pc? So, is it possible to edit the build prop by copying the default one from /system and overriding the build prop after editing it from notepad? @iXaidyiu
Theoretically yes (except your title), but you need to be in recovery mode (TWRP) and mount /system -RW in order to perform such action.
Ref.:http://www.theandroidsoul.com/edit-build-prop-without-root-using-adb-in-twrp-recovery/
ok, thanks

Samsung health error

Guys I need some help !!
I have official firmware in my phone S7 edge ( Android 7.0 G935F ) but once i tried to root it and it was stuck in boot logo so i went to a store for a suppose unroot ,but know e cant use Samsung health app because gives me an error. I already searched this error and just have to change the tima value to 0 in build.prop
My real question is can I edit build.prop to fix this error without root or do i have to root my device again to fix this error ??
Please help
thanksssss, waiting 4 answers
Your phone KNOX is ticked 0X1 that's why not working, you must root your phone and edit built prob, edit line TIMA=0 and will work
so i have to root it again ?? i have some problems (fear) doing it again because i don't know how to do it right
Or othe way to make it work. But need to be Root. Delete v5 restar install v4. Loging abd update. Done
I would recommend you the recovery mode if you don't want root the phone again. You have full access to system files in recovery mode, but only if it is mounted.*
Many stock recoveries don't have option to mount system partition or don't have adb access for commands. You might want a custom recovery for this. And no, you don't need root for custom recovery. So now all you need to do is, boot into recovery (custom preferred), mount system and then using adb, pull the build.prop file:
adb pull /system/build.prop <path to save file>
Now edit the file you just extracted and save it*
Push it back to your phone via adb
adb push <path to your file> /system/build.prop
You're not done yet. You need to set permissions too. So open she'll via terminal
adb shell
Now from shell, set the right permissions
chmod 644 /system/build.prop
And you're done
Reboot your phone and see the changes

Categories

Resources