i am trying to change the pixel density on my rooted cm7 nook color and make it stick across reboot i have tried a few apps altho they do change the density it resets to the default when i rebook i also tried to change it via root explorer but that just sent me into a boot loop forcing me to do a wipe
I use file expert to change build prop. I have to copy the file to SD card, edit it, and then overwrite the original file. You can mount system as rw within file expert.
Related
alright... I rooted my nook color, and I was wanting to change the screen specs to match the galaxy tab, but when I open my system > build.prop file in the root explorer, I can't change anything... any suggestions??
this is because the NookColor's stock LCD density is 169.333, which is pretty low (Galaxy Tab is 240). Unlike resolution, which is hardware-based, density is software-based and can be changed. If you search the market for LCD density, there are a couple apps that will do this--a free one that won't survive a hard reboot, and a paid one that (supposedly) will.
If you want to make it permanent for free, you can edit your build.prop file. Again, use Root Explorer to open system/build.prop (BACKUP FIRST!), find the following two lines:
ro.sf.lcd_density.xdpi=169.33333
ro.sf.lcd_density.ydpi=169.33333
If you wanted your density to be 250, you'd replace them with the following single line:
ro.sf.lcd_density=250
Save the edited file, and reboot.
Click to expand...
Click to collapse
Mount the /system partition as r/w first, there is a button on the top.
Forgot to mention that I tried that.. I restarted root explorer... no change
Sent from my HTC Glacier using XDA App
I just did it with mine no problems.
Sent from my LogicPD Zoom2 using Tapatalk
long press "build.prop" and select "open in text editor" from the popup menu.
Also 240 will be way to big. The menus wont fit. Im on 200 right now and some screens are off but not to bad.
sent from my Rooted Nook Color using Tapatalk
arda99 said:
long press "build.prop" and select "open in text editor" from the popup menu.
Click to expand...
Click to collapse
thanks... only time I'd used it was on my HTC Glacier (mytouch 4g), and I didn't have to do that... works like a champ
Can't get /system into r/w
I'm trying to change my build.prop file to change the display density on my NC.
I have an edited file waiting to be used.
I want to rename the original build.prop to something like build.old and copy the new file in next to it.
But Root Explorer won't change /system to r/w.
I can't rename the original file or paste the new file.
I can flip root "/" back and forth from r/o to r/w without problem.
But nothing happens when I touch or hold the button when in /system.
?????????
Did you figure this out? I am having the same issue modifying files for the hulu fix.
Hi All
I'm running the stock Jelly Bean (4.1.2) on my Note which is rooted.
I changed the LCD density by editing the build.prop after reading changing it to 213 would make it like the Nexus 7 interface. However, I'm now in a boot loop.
I have a copy of the original build.prop but I can't adb push it to my Note because I get a permissino denied error. If I try to adb root it tells me I can't do it on production builds and remount tells me the operation is not permitted.
Any chance this can be sorted without me having to flash the ROM again?
thanks in advance
EDIT: I originally flashed the ROM with Mobile Odin Pro and injected root. I don't really want to flash the ROM again as I'd lose root. I have the backup build.prop on my hard drive and also on the external CD card in my Note. Can I use adb shell / su / mount to copy it over?
I dont know about adb, there is cwm flashable zip thought in which you can put the buildprop you want to flash.
Best to use romtoolbox for changing dpi, that one is pretty safe. if you have two entries in buildprop chsnge both to desired density.
baz77 said:
I dont know about adb, there is cwm flashable zip thought in which you can put the buildprop you want to flash.
Best to use romtoolbox for changing dpi, that one is pretty safe. if you have two entries in buildprop chsnge both to desired density.
Click to expand...
Click to collapse
Thanks for the info, but I' have stock recovery so wouldn't be able to flash that, would I?
Is another option making my own update.zip and having my restored build.prop in there?
then you are probably right with adb. Not sure if it requires root.
I know of no other way myself, cant help you there, short of what you said reflashing entire rom
download PhilZ Touch 3.0 Recovery and AROMA Filemanager and place it on external SD
CWM touch Philz http://forum.xda-developers.com/showthread.php?t=1927097
Aroma File manager
http://forum.xda-developers.com/showthread.php?t=1646108
Use this PhilZ Touch 3.0 Recovery to be flashed from stock recovery then flash the Aroma file manager. now you will have a recovery file manager. now replace the build.prop with the backed up one, fix permissions and reboot.
Good luck
Thanks Nokia, I'll have to remember that one
Oh well. i had done the mistake of changing the build.prop using root explorer and the phone never booted up.. so ...
Hi there! I'm trying to modify my build.prop to set my DPI to 400, but i can't seem to make the change stick. I've searched for a solution for days, reset my phone a few times - the few solutions i found haven't actually worked. Here's some info:
Device: HTC One International(m7ul)
Recovery: CWM Recovery v6.0.3.2
ROM: HD Revolution Google Edition 4.1 (with all performance tweaks selected in AROMA installer, including build.prop tweaks)
Root: SuperSU
Solutions attempted:
-Setting RW before changing the file and setting it as RO afterwards, both through file manager and shell. File resets regardless.
-Modifying existing build.prop in ROM archive. Refused access.
-Creating a zip with the modified build.prop, installing it through CWM. CWM refused to install the file
-hamsteyrs Google Play DPI Fix tool. Required renaming of com.vendor1.apk to Phonesky.apk and running the tool instantly afterwards, as the application would rename itself back(in the end, i had to make it a flashable zip which created both a Phonesky.apk and a com.vendor, and outright broke my DPI in applications, ranging from different values at random)
I'm outright stumped by this, as nothing seems to be doing what i want it to.
I tried to change the boot animation, running M Preview 3, and despite the fact that the flash claims to have performed successfully, it did not. I'm trying to flash the Marvel boot from the Themes and Apps section, and I know the flashable file worked on 5.1.1. It didn't overwrite the bootanimation.zip in /system/media. At one point, I was able to manually move the file there myselfusing Root Explorer, but I did not realize that the /system partiton did not have enough space to hold the entire zip file, so it was a corrupted zip at that point, and now my boot animation is just "android" in gray lettering. I cleared up enough space to hold the entire zip file of the marvel boot, but now I cannot move the file there, ES File Explorer and Root Explorer simply say it failed to copy.
I just tried to use adb to push the zip file from my computer, but it fails because /system is a read-only file system. So, I tried to remount with a shell as read-write, after some initial issues with apparently /system/xbin/mount not working properly, it did remount as read-write when using /system/bin/mount. But, adb push still fails because /system is a read-only file system.
Code:
mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered 0 0
But, as you can see, it's mounted as read-write.
I, also, just tried to move the file as root in an adb shell, with no luck. A bootanimation.zip shows up in /system/media, but apparently it is corrupt because I cannot open it with root explorer, or in Windows when I pull it. When I try to move the boot animation that I want, the shell reports that there is not sufficient space, which is true now. The bootanimation.zip takes up 40MB of the 55MB of free space in the /system partition. Any time I try to delete the zip, it is automatically recreated before I have a chance to move anything in it's place, even when I do:
Code:
rm /system/media/bootanimation.zip | mv /storage/emulated/0/Download/marvelboot/system/media/bootanimation.zip /system/media/bootanimation.zip
So, what am I missing? Is it even possible to change the boot animation on Android M? Am I doing something wrong, or not doing something I need to?
why flash it? its a boot animation.. extract it from the zip, then pkace the bootanimation.zip into /system/media/ then just reboot. thats all it takes.
edit.. i didnt read ypur whole post and realuze that yoh have other issues.
Yeah, I wish it was just as easy as flashing or moving the zip file to /system/media/... Normally it is, but with Android M there seems to be a problem?
cappiez said:
Yeah, I wish it was just as easy as flashing or moving the zip file to /system/media/... Normally it is, but with Android M there seems to be a problem?
Click to expand...
Click to collapse
no, no problem here. do you have full root? i mean do you have the ability to edit anything in /system/?
Everything seems fine according to root checker. And, if I make small changes to my build.prop (Just editing build.id), the changes stick after a reboot. Soooo.. Yes?
cappiez said:
Everything seems fine according to root checker. And, if I make small changes to my build.prop (Just editing build.id), the changes stick after a reboot. Soooo.. Yes?
Click to expand...
Click to collapse
so you fo have full root. i use root explorer to put animations into /system/meda/, havent had any issues. does that animation work on a n6?
It worked on 5.1.1. Since I moved to the M Preview 3 builds, it appears to have stopped working.
cappiez said:
It worked on 5.1.1. Since I moved to the M Preview 3 builds, it appears to have stopped working.
Click to expand...
Click to collapse
nope. im on m preview 3, and it works fine here.
I've updated my device today to 6.0.1 and rooted, however I can't seem to change the boot animation (yes, I have searched for answers and tried quite a few fixes).
Root Explorer tells me I have renamed the old file and copied the new file, however once I leave the directory and go back the old file is still there.
I have used the file explorer in TWRP and managed to delete the stock boot animation, but get a FAILED message when I try to copy the new file.
I used the terminal in TWRP and tried to copy the file manually, and receive a "No space left on device" message.
I've also tried mounting the /system as rw in adb. I can delete the bootanimation.zip file from there, and df -h shows 3mb free. Shouldn't the system partition have more space available than that?
Am I missing something, or has something changed with the new android versions?
Google has filled the system partition up to the brim. Also you can't remount system as rw while Android is running.
But the direction is right, go to TWRP, mount system, delete the old bootanimation. If the new one is not that much bigger then you could just copy it there, set permissions to rw-r--r--. But if the new animation is significantly bigger, you'll have to delete some bloatware first.
Thanks for that. The odd thing is, when I run DF in the terminal, it shows I have 20mb free. The boot animation file I am trying to copy is 6mb.
I'll keep poking around. If it doesn't work, it doesn't. It's not hugely important