Hello!
Not intented as a spam, but i need some help.
I cannot edit Mod Version. whenever i edit it and reboot, all my changes are deleted.
I cannot change anything in my build.prop
I used Root Explorer, Liberty toolbox, did changed the name of the ROM using kitchen and also replaced my build.prop before signing it.... but nothing helped.
anyone can please help?
Related
I'm working on an MIUI Rom and I want to edit the framework-res.apk; I decompiled the apk using apktool and then I rebuilt after changing the default lockscreen and default wallpaper; I then signed the apk using the autosigner from Stericson and it signed successfully; after repacking the rom and installing I successfully installed my signed rom, but afterwards my bootloader just went into a loop; my only thought of what could be wrong is when I changed the framework-res.apk; does anyone know if you have to do anything more then rebuild and sign? Sorry for the nub question, but I've been trying to get it to work to no avail and I don't really know what else to do at this point, but ask someone else for their input. Thanks.
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.
Hi, first time poster here. I can usually find what I need, but I'm stumped here.
I'm running a rooted Galaxy S4 on ATT with the i337ucuamf3 build.
I've successfully installed viper4android, but it only works on and off, with Google Music.
I'm pretty sure the fix for this is to change the build.prop lines: Ipa.decode, tunnel.decode and Ipa.use-stagefright.
I've tried everything that I can think of, but I no matter how I make the changes, they will not save. I've tried mounting System R/W in Rom Toolbox, and booting into System R/W. I've made the changes with Rom Toolbox Pro and ES File Manager. Nothing works.
Can anybody tell me if I just can't make these changes to build.prop because of the build I'm running?
Please, any help would be appreciated. When viper does work, it's incredible!
Thanks.
synesthesiac said:
Hi, first time poster here. I can usually find what I need, but I'm stumped here.
I'm running a rooted Galaxy S4 on ATT with the i337ucuamf3 build.
I've successfully installed viper4android, but it only works on and off, with Google Music.
I'm pretty sure the fix for this is to change the build.prop lines: Ipa.decode, tunnel.decode and Ipa.use-stagefright.
I've tried everything that I can think of, but I no matter how I make the changes, they will not save. I've tried mounting System R/W in Rom Toolbox, and booting into System R/W. I've made the changes with Rom Toolbox Pro and ES File Manager. Nothing works.
Can anybody tell me if I just can't make these changes to build.prop because of the build I'm running?
Please, any help would be appreciated. When viper does work, it's incredible!
Thanks.
Click to expand...
Click to collapse
Hello,
I was trying to edit the build prop file using the ES Explorer, but the same happened to me, I could edit the file by downloading the "build prop editor" from play store.
Edit the file by pressing the button in shape of a pencil and later press the save button. If you only search for the line you want to edit in the main screen of the app you will be able to modify the line but the changes are not saved.
Thanks/rate
synesthesiac said:
Hi, first time poster here. I can usually find what I need, but I'm stumped here.
I'm running a rooted Galaxy S4 on ATT with the i337ucuamf3 build.
I've successfully installed viper4android, but it only works on and off, with Google Music.
I'm pretty sure the fix for this is to change the build.prop lines: Ipa.decode, tunnel.decode and Ipa.use-stagefright.
I've tried everything that I can think of, but I no matter how I make the changes, they will not save. I've tried mounting System R/W in Rom Toolbox, and booting into System R/W. I've made the changes with Rom Toolbox Pro and ES File Manager. Nothing works.
Can anybody tell me if I just can't make these changes to build.prop because of the build I'm running?
Please, any help would be appreciated. When viper does work, it's incredible!
Thanks.
Click to expand...
Click to collapse
Never mind.
ES File doesn't always save, you'll just have to try a different app. Root explorer should work or fx file manager.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Hey Guys,
I have an S7 Edge and was always able to change the DPI via any common method.
For some weeks it´s somehow not possible. I tried while on various ROMs.
I tried via editing Build.prop, Android Terminal App, DPI Changing Apps and via Terminal on Mac and Windows.
It just doesnt work....
I noticed that being on BobCat ROM it works.... But with no other ROM. I tried them all on XDA.
Does anybody have an idea why and/or how to fix this?
I appreciate every reply.
You need to have root acces and use a file manager (I use Solid Explorer), open build.prop with the Solid Explorer built in editor (SE Text editor) and find and change the following line:
ro.sf.lcd_density=560
(560 is the best value that you can apply, anything bellow that dpi messes up the touchwiz apps).
Save the file and presto!!!
I hope this can help.
Best regards!!!
Not working. Build.prop shows the new value but no visual change is seen
Did you restart your device?
Hello dudes.Please help me.Just today my camera doesn't work anymore.No one of my 4 camera apps,just black screen!Any idea?i reflashed squid and also coffee kernel but nothing!!!
Peace to all
Bytheway yesterday i edited my build.prop with some 3g and scrolling tweaks.and now i read that this conflicts with camera.i restored the backedup build.prop through builf.prop editor app,but the same result..
permissions was changed,so I had to change them again.thanks
Peace to all
kos25k said:
Bytheway yesterday i edited my build.prop with some 3g and scrolling tweaks.and now i read that this conflicts with camera.i restored the backedup build.prop through builf.prop editor app,but the same result..
permissions was changed,so I had to change them again.thanks
Peace to all
Click to expand...
Click to collapse
What ROM are you using? Either way, you'll probably need to re-flash the ROM. The same thing happened to me before. I edited the build.prop and it caused my camera to force close. Had to re-flash the ROM because restoring the build prop didn't work for me either.
Stock rom.after a lot of search and one step from reflashing the rom...i realized that the restored build.prop permissions from rw-r-r changed by it's own to rw!so i just set them back to default permissions and all is ok now!i wonder also if my camera f.close was causing also from this.(i mean with just editing the build.prop,not the restored one)i made the restore process with root explorer finally.before this i edited b.p with the b.p app from playstore.
Peace to all