Database Users

[Q] Replacing build.prop?

hi!
in order to test something, i need to replace the build.prop in root/system with a modified one. but trying to delete this file with astro manager displays an error message, and just copying the modified build.prop over the old one doesn't work too (nothing happens).
so my question is: how do you replace such a file?
thanks in advance for your help

are you serious!?!?!?
If the build.prop is located on the Android folder IT HAS TO BE A SYSTEM FILE !!!
if you mod the system files you could break android or the system just won't let you do it, you will need R and W privileges to do that.
edit the system files from your PC or just boot up in to windows mobile.
use some common scene next time.
hope it helps!
Sent from my HTC HD2 using XDA App

Do you use a cyanogen build?

yes and there is already a cyanogen rom posted with the proper build.prop fixed, so you won't have to edit anything, just search for it.
Sent from my HTC HD2 using XDA App

mmmh actually cyanogen made things easy to replace a system file, just copy your file into sdcard/android/root/system and reboot.

thanks for your help / posts. but unfortunately they're not helpful.
yes, i am serious! and yes, of course it's a system file. i know as well that modification might brick android.
there are reasons for modifying this file. some people seem to be able to, e.g. for chaning screen point density or modify the data passthrough.
so, please tell me, how can i edit/modify a system file from pc or windows mobile when its within the data.img-file?
thanks for any tips / hints on this.

use root explorer

Sichroteph said:
mmmh actually cyanogen made things easy to replace a system file, just copy your file into sdcard/android/root/system and reboot.
Click to expand...
Click to collapse
Thank you VERY much for your help - I finally got it to work by listening your instructions. It is simply different if you have HD2 and plus CM mod. That figures why it was going back all the time to 180 instead of changing it - because it runs from sd card and that's where it needs to be replaced as well ...

Droid Explorer

Argh, I cant change DPI!

Hey peeps!
I just flashed to the latest CM9 nightly from RC2 and wiped cache and dalvik. I tried to change the DPI back to 213 as I did before: reading this guide and using Total Commander and editing the build.prop in the /system dirr which worked without any problems in RC2 but now TC or any other file manager cant save the file. I thought first that I didnt have root possibilites but all other apps that require root works and get roots. Whats your idea of this? I tried using ROM Toolbox but I couldnt figure out where to change the DPI there
EDIT: Uhm rather delete this one, Ill post it in the correct thread instead

Same experience with total commander. That's why I copied the build.prop in another folder, edited it and pasted it back into /system. Check the permissions.
ROM toolbox has two options, one with a slider (build prop tweaks) and the other is the editor. Look for ro.sf.lcd_density= 320 and change it there.

AAh thanx! finally away from the horror DPI 320, all mothers nightmare! =)
I bid you thank you kind sir!
AA1973 said:
Same experience with total commander. That's why I copied the build.prop in another folder, edited it and pasted it back into /system. Check the permissions.
ROM toolbox has two options, one with a slider (build prop tweaks) and the other is the editor. Look for ro.sf.lcd_density= 320 and change it there.
Click to expand...
Click to collapse

You can manualy change it with Root Explorer too. This is the only safe file explorer which doesn't kill you ROM if you change lcddestiny setting with it.

[Q] Problem With Package Installer

I am having a problem with the package installer on my Nexus 7. (Wi-Fi, 32 GB) I think I may have done something to it accidentally while browsing through the system files. I did click to install the installer itself out of curiosity, though, but I don't know if that could have any adverse effects on anything. I cannot install any apps, whether they're from the Play Store or an APK through a file explorer. I get error 406 when I try to download anything from the Play Store. (Except when I tried to update ES File Explorer. That worked fine... Every other app that I've tried will not update/ download.) When I try to install an APK, I get a message like, "There is no program to open this file." I had just rooted my Nexus after having it for nearly a year with the Motochopper root exploit, so the bootloader is still locked. I could still install apps, though, until after my first reboot. Could anybody identify the problem? Any help would be greatly appreciated!

you might have removed packageinstaller.apk thats in the system. you can fix it by getting the correct packageinstaller.apk from the interent and move it to the correct /system/app path and apply CORRECT permissions for it

Billchen0014 said:
you might have removed packageinstaller.apk thats in the system. you can fix it by getting the correct packageinstaller.apk from the interent and move it to the correct /system/app path and apply CORRECT permissions for it
Click to expand...
Click to collapse
It's still there. I think installing it with itself out of curiosity is what messed it up. It now shows up in the installed apps menu in Settings.

TheZeldaLova said:
It's still there. I think installing it with itself out of curiosity is what messed it up. It now shows up in the installed apps menu in Settings.
Click to expand...
Click to collapse
Change its permissions to the same as the other apps in the same folder should fix it

Billchen0014 said:
Change its permissions to the same as the other apps in the same folder should fix it
Click to expand...
Click to collapse
It doesn't seem that I am able to change permissions. I'm just going to back everything up and either flash a stock rom or another good rom. Thank you very much for your help anyways.

Same problem..
What do you mean about "changing permissions"? If you mean to change the file properties to -rw-r-r- then that didn't worked for me .. pls help!

Need help with build.prop edit

I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?

in_dmand said:
I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
Click to expand...
Click to collapse
I can do that above with RE, very strange problem you have.
Try a build.prop editor, i used this in the link. It sets correct permissions after editing and so on. Use the pencil icon in the bottom right to edit.
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

Hi,
Same thing for me with Root Explorer, instead I use build.prop Editor
EDIT: not fast enough :laugh:

qsec said:
I can do that above with RE, very strange problem you have.
Try a build.prop editor, i used this in the link. It sets correct permissions after editing and so on. Use the pencil icon in the bottom right to edit.
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Click to expand...
Click to collapse
I got it and tried exactly like you said, and while it does pull it up and my keyboard pulls up and I can feel the haptic feedback, no letters will be inserted in deleted...? Really weird.

Maybe it's related to my root access? TB is showing I'm rooted, but check out my superuser app when I try to update an install new binaries...

Get rid of Superuser and try SuperSu instead. Sometimes the old Superuser has issues on ROMs since ICS.

EniGmA1987 said:
Get rid of Superuser and try SuperSu instead. Sometimes the old Superuser has issues on ROMs since ICS.
Click to expand...
Click to collapse
Downloaded and installed... Removed the old one. Still not letting me edit... Looks an feels like it is but won't enter any characters. At least RE isn't giving me the "too large" error anymore

in_dmand said:
I got it and tried exactly like you said, and while it does pull it up and my keyboard pulls up and I can feel the haptic feedback, no letters will be inserted in deleted...? Really weird.
Click to expand...
Click to collapse
i had the same issue, couldn't figure out why. try replacing a commented line with the code to disable the nav bar

How do I know if it's just a commented line and not necessary to the program?

in_dmand said:
I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
Click to expand...
Click to collapse
i had the same issue any help?

If you are in stock android 4.4.2 dont do it
You will stuck on bootloop
If you still wand to do let copy your build.prop to pc and edit with notebat++ or some program and recopy overwrite to your phone
Sent from my LG-D802 using xda app-developers app

maxkanick said:
If you are in stock android 4.4.2 dont do it
You will stuck on bootloop
If you still wand to do let copy your build.prop to pc and edit with notebat++ or some program and recopy overwrite to your phone
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
You are right, I have tried to edit it on pc and stuck on a bootloop.

Use build.prop editor app from playstore
_____________________________________Read more write less and be smart

[Q] Sound/Headphone Mod Issue

Hi all! Thanks for any and all help!
Quick info: Stock ROM 4.4.2 via OTA (LS980ZVC), Rooted, Nova Launcher and Xposed Framework. I've tried flashing other ROMs and it just didn't work so I went back to stock.
I'm not too impressed with the speaker and headphone volume on my phone. I didn't buy the phone for the sound, though, so that's a good thing. However, an improvement would be nice!
I've tried both the sound mods below:
http://forum.xda-developers.com/showthread.php?t=2482750 - Root Explorer would not allow me to copy the file from my SD card to the proper location saying "copy failed!" each and every time.
http://forum.xda-developers.com/showthread.php?t=2542398 - I flashed this and it soft bricked my phone. I got bootlooped because of it. Is there any particular reason, other than I just don't know how to flash right? (all kidding aside!)
Is there an easy way to get one of these two to work, or am I just stuck with the sound I have?
Again, thanks for any and all help, folks!
(I posted this in the Sprint G2 help thinking it was the general G2 help.. whoops... sorry for cross posting)

If it rooted, RE should work.
Make sure you check and change permission if needed.

votinh said:
If it rooted, RE should work.
Make sure you check and change permission if needed.
Click to expand...
Click to collapse
RE works and I can navigate to the correct folder, as well as copy/paste the old file from /system/etc/snd_soc_msm to my SD card. Moving the file from the SD card, or copy and pasting, results in "Operation failed!" and no change. Permissions are good as far as I can see?

Try Root Browser instead.
https://play.google.com/store/apps/...owser&pcampaignid=APPU_yCRZU_eiLunEyQGkuoHYCg

cheetahcat79 said:
Try Root Browser instead.
https://play.google.com/store/apps/...owser&pcampaignid=APPU_yCRZU_eiLunEyQGkuoHYCg
Click to expand...
Click to collapse
Same issue, "operation failed."

Try changing permissions on the system folder?

cheetahcat79 said:
Try changing permissions on the system folder?
Click to expand...
Click to collapse
do the reroot and tell me if it made any difference..

cheetahcat79 said:
Try changing permissions on the system folder?
Click to expand...
Click to collapse
I've checked everything on the system folder for permissions. No dice.
buenarc said:
do the reroot and tell me if it made any difference..
Click to expand...
Click to collapse
Same as above, no dice.

Just as a heads up, I downloaded Viper4Android FX and XHiFi, and that worked the treat to get the sound muuuuuuch more clear and tolerable from Pandora. Night and day difference, no doubt... although Pandora's bitrate isn't high, it's 100x more tolerable now.