i installed build prop editor and i saw the option change pixel density
i changed it to 360 and i rebooted the phone and when it rebooted i get force closes and i cant do anything on my phone now...
Any help???Any fix without loosing my apps? cuz i dont want to loose my apps... i have some important things in there...
@gabiabrudan7: you only may reduce dpi, lower 320! So try to restore the old build.prop: if there's a bak-file, you can rename it in TWRP's file manager - otherwise use ADB (if there's access from PC) to move build.prop to PC, change it with an editor, which stores in UNIX-format and move back.
rp158 said:
@gabiabrudan7: you only may reduce dpi, lower 320! So try to restore the old build.prop: if there's a bak-file, you can rename it in TWRP's file manager - otherwise use ADB (if there's access from PC) to move build.prop to PC, change it with an editor, which stores in UNIX-format and move back.
Click to expand...
Click to collapse
thanks for the reply but i already fixed it ... i flashed lollipop mirror and i have no problem now!
thanks anyway!
Related
i am on rooted stock ATT 2.2 firmware. I have busybox installed. Tried LCD density changer app from market but everytime i try to adjust the setting, the phone freezes and the only way to start back is by removing the battery. phone starts back up fine at 160 dpi again.
i have tried 180, 200, and 220 all with same results. any ideas what the problem is?
If you are using a rooted phone browser to build.prop, mount it R/W (root explorer e.g), and edit it.
You should be able to change it there manually.
In the /system/build.prop file, add this:
ro.sf.lcd_density=XXX (where XXX is the density number you want 160/240/etc)
Save, restart your phone and there you go.
MySeLfPT said:
If you are using a rooted phone browser to build.prop, mount it R/W (root explorer e.g), and edit it.
You should be able to change it there manually.
In the /system/build.prop file, add this:
ro.sf.lcd_density=XXX (where XXX is the density number you want 160/240/etc)
Save, restart your phone and there you go.
Click to expand...
Click to collapse
yeh, i saw that manual method but was afraid to try because i wasn't sure i'd be able to easily recover if there was a problem.
fortunately, i found a different app on the market "LCDDensity!" that works just fine. There is no preview and you have to reboot to make the change, but it does a fast reboot and it works flawlessly.
Thanks for the Help!
mongofrye said:
yeh, i saw that manual method but was afraid to try because i wasn't sure i'd be able to easily recover if there was a problem.
fortunately, i found a different app on the market "LCDDensity!" that works just fine. There is no preview and you have to reboot to make the change, but it does a fast reboot and it works flawlessly.
Thanks for the Help!
Click to expand...
Click to collapse
Tried it n it worked but after a full reboot, it reverts back to normal 160 density
MySeLfPT said:
If you are using a rooted phone browser to build.prop, mount it R/W (root explorer e.g), and edit it.
You should be able to change it there manually.
In the /system/build.prop file, add this:
ro.sf.lcd_density=XXX (where XXX is the density number you want 160/240/etc)
Save, restart your phone and there you go.
Click to expand...
Click to collapse
I cant seem to find this line in my build.prop
im using AWS 345 build rooted and Ive done this before with previous phone so im familiar with it but ive looked at least 5 times for that line but its nowhere to be found..
is there any other way???
ducehlmg said:
Tried it n it worked but after a full reboot, it reverts back to normal 160 density
I cant seem to find this line in my build.prop
im using AWS 345 build rooted and Ive done this before with previous phone so im familiar with it but ive looked at least 5 times for that line but its nowhere to be found..
is there any other way???
Click to expand...
Click to collapse
If the line doesn't exist, just add it. For some reason many of the stock Streak build.prop's don't have it in there. But, just add it and then you can tweak to your heart's content. That's what I did, and I'm on LCD=200 now.
mellojoe said:
If the line doesn't exist, just add it. For some reason many of the stock Streak build.prop's don't have it in there. But, just add it and then you can tweak to your heart's content. That's what I did, and I'm on LCD=200 now.
Click to expand...
Click to collapse
yea i figured that out but thanks for the tip... i set mine to 190 & i also grabbed ur wallpaper from the Screenshot thread.. so thanks for that too
MySeLfPT said:
If you are using a rooted phone browser to build.prop, mount it R/W (root explorer e.g), and edit it.
You should be able to change it there manually.
In the /system/build.prop file, add this:
ro.sf.lcd_density=XXX (where XXX is the density number you want 160/240/etc)
Save, restart your phone and there you go.
Click to expand...
Click to collapse
What did you use to edit the file?
mid_life_crisis said:
What did you use to edit the file?
Click to expand...
Click to collapse
Root Explorer. That's what I use. It is a paid app, but the best file explorer I've found. I'm a big fan.
mellojoe said:
If the line doesn't exist, just add it. For some reason many of the stock Streak build.prop's don't have it in there. But, just add it and then you can tweak to your heart's content. That's what I did, and I'm on LCD=200 now.
Click to expand...
Click to collapse
Worked for me. On 345 with density=180! Thanks mellojoe!
Try font changer if you don't want to meddle with build.prop.
I currently use a HTC HD Mini (Photon) running the SCREAM ROM by Ling Gan. It has a few bugs for most of which there is either a workaround or fix but there is the one problem which has remained unsolved: the default wallpaper on everything BUT the home and lockscreens cannot be changed. It is of a tree in a meadow under a blue sky and when rotated to landscape changes to some smiling chinese lady in the "settings" submenu. Doesn't hamper use much but it is quite annoying.
I have tried a number of solutions some of which resulted in my having to reflash and others did nothing. I post this here because I think it is a CM7 issue. The ROM developers have so far been unable to post a solution within the thread and I am aware that a fix for similar problems on CM9 ROMs exists using ADB to edit framework-res.apk. I felt it was time the problem was tackled by the wider XDA fam. Used google translate to look on the chinese site where the ROM is native to (mobile-kon) but found no help as well. Any help would be greatly appreciated.
i think ur problem lays in the framework-res.apk it contains the look of the rom and the transition effects
you can mod apk with the apkmanager tool for ur computer in the frameworkresapk you should find the images u want to change replace them witch a black picture or something like that
if never done this befoure exept from changing some transition effects and i had a couple of errors among this
the easier way seems to search for the rom on another page cus the images ure stating are not standart in the cm7
SOLVED!
jiffer1991 said:
i think ur problem lays in the framework-res.apk it contains the look of the rom and the transition effects
you can mod apk with the apkmanager tool for ur computer in the frameworkresapk you should find the images u want to change replace them witch a black picture or something like that
if never done this befoure exept from changing some transition effects and i had a couple of errors among this
the easier way seems to search for the rom on another page cus the images ure stating are not standart in the cm7
Click to expand...
Click to collapse
Many thanks!
I started off looking through the "res" folder in framwork-res.apk using Root Explorer to identify the images for the wallpaper. They were
Res/drawable-land-mdpi/screen-background-dark-transparent.png
And
Res/drawable-mdpi/screen-background-dark-transparent.png
I then created a copy of framework-res.apk on my SD card and copied it onto my pc. I created new wallpapers to replace the ones I just mentioned, one in portrait, the other in landscape. They were 320x480 and 480x320 respectively. Using 7zip on the pc, I placed them in the corresponding folders (/drawable-mdpi for protrait and /drawable-land-mdpi for landscape).
I copied framework-res.apk back to my sdcard and then fired up terminal emulator to run the following commands
su
sys -rw
busybox cp /sdcard/framework-res.apk /system/framework
sys -rw
You might get error messages from running apps after this but ignore them and reboot. The idea is to replace the framework-res.apk in system/framework with the one you just edited.
After the reboot, you should have your newly created wallpaper showing up in settings in both landscape and portrait modes.
Please hit "thanks" for both jiffer1991 and I if this was helpful. Big ups to jiffer1991for pushing me in the right direction.
Hi,
i did something wrong.
So my Phone didn´t run.
He show me the Bootsceen and the Animation.
But the he will run again and again and again.
Can i handle my Phone via USB so i can restore the framework.resp.apk on my System? Or i have to reinstall Android again?
I have no backup and i don´t want to erase my system settings.
Thanks
Felix
obstgarten said:
Hi,
i did something wrong.
So my Phone didn´t run.
He show me the Bootsceen and the Animation.
But the he will run again and again and again.
Can i handle my Phone via USB so i can restore the framework.resp.apk on my System? Or i have to reinstall Android again?
I have no backup and i don´t want to erase my system settings.
Thanks
Felix
Click to expand...
Click to collapse
hm u got stuck in a bootloop thats what i meant when i mentioned errors =)
you could make a zip with the old framework res apk or reflash the cm rom
if u dont whipe data/cash ure setting will be safed
read some tutorials how to mod the framework res apk
I have an .zip file on the sd card.
Can i copy it to the Android system somehow?
Felix
P.S. can i zip the framework and remove the ".zip" to ".apk"?
It is most likely that the zip file you have is the ROM image from which you flashed in the first place. Changing the extension to apk is NOT what you want to do. I suggest you create a backup in CWM of you present configuration and after reflashing, you can then do a partial restore of your user data. But its like Jiffer1991 said, read up on CWM, theres an exhaustive guide on xda somewhere.
Thanks,
i installed my modified cm rom without wipe caches data or something.
And now i have my old datas back, with the new Background.
I edited the build.prob file change lcd density to 720. now I can't access phone
If you know how to use adb, and have USB Debugging or a custom recovery set up, you might be able to pull the build.prop, edit it on your computer, push it back, change permissions, and reboot to resolve. You aren't able to access your apps or anything like that, I suppose?
es0tericcha0s said:
If you know how to use adb, and have USB Debugging or a custom recovery set up, you might be able to pull the build.prop, edit it on your computer, push it back, change permissions, and reboot to resolve. You aren't able to access your apps or anything like that, I suppose?
Click to expand...
Click to collapse
Am try to that, using DroidExplorer but after editng the build.prop the changes are not being saved. I thing usb debugging mode is disabled and I cant access anything in my phone. my device doesnt show in" fastboot devices"command when I use the ADB
fastboot devices only works in fastboot/bootloader mode and adb works when booted (with USB Debugging enabled) or via most custom recoveries. Did you install a custom recovery or just root? If just root, it might just be easier to return the device to stock and reroot.
3CPO_R2D2 said:
I edited the build.prob file change lcd density to 720. now I can't access phone
Click to expand...
Click to collapse
If you are running any custom rom..extract that zip...copy that build.prop to sd card...now using Root Explorer on your phone copy it and head on to /system...delete the build.prop and paste the new one..and Reboot.
P.S.:Remember to Mount R/W before pasting it.
theprakhar said:
If you are running any custom rom..extract that zip...copy that build.prop to sd card...now using Root Explorer on your phone copy it and head on to /system...delete the build.prop and paste the new one..and Reboot.
P.S.:Remember to Mount R/W before pasting it.
Click to expand...
Click to collapse
Don't think he can use his phone well enough to make that work. according to the way the pictures look, which is why I didn't suggest that one. All apps are going to be like that and it's not something you can scroll around in like you would if you zoomed in on the browser or something similar.
es0tericcha0s said:
Don't think he can use his phone well enough to make that work. according to the way the pictures look, which is why I didn't suggest that one. All apps are going to be like that and it's not something you can scroll around in like you would if you zoomed in on the browser or something similar.
Click to expand...
Click to collapse
Opz..my bad...i forgot that this is only his problem......yup...but still one other option left...he can install the zip of the rom which he is currently using WITHOUT formatting or wiping...just over-writing...It might work..
Hi guys, before I start I'll say that I have searched all over the internet and here on the forums and I couldn't find my particular issue. Well the thing is that I edited the line in my build.prop "ro.build.version.codename=REL" to "ro.build.version.codename=L" so I could get the material design on the Google Now Launcher pulled from a Android L build here's the thread I got that app: http://forum.xda-developers.com/android/apps-games/app-android-lollipop-apps-launcher-apps-t2912905
I did that and now my device will boot up normally then I will reboot by itself then show the boot animation then repeat the same process again and again until I force the phone to recovery or fastboot.
By the way my device is the LG Optimus G (E970) running GEE 3 ROM 1.2 and TRWP 2.6.3.0 and I have a backup of the original build.prop on my PC. I don't want to lose my data and apps since I forgot to make a backup (silly me).
I would like to know if there is a way to push the build.prop file on my PC to my phone so I could just replace it, or create a flashable zip.
Please help me, and thanks in advance.
Nevermind. I managed to push the original build.prop file to /system set the correct permissions and now my phone is working again.
Admin feel free to delete or close this thread.
question
AntonyOrtega said:
Nevermind. I managed to push the original build.prop file to /system set the correct permissions and now my phone is working again.
Admin feel free to delete or close this thread.
Click to expand...
Click to collapse
how were you able to do it when you couldnt get past booting.
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
deathsquad737 said:
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
Click to expand...
Click to collapse
You know there is already a flash for this and an apk.
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
deathsquad737 said:
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
Click to expand...
Click to collapse
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
tech_head said:
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
Click to expand...
Click to collapse
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
deathsquad737 said:
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
Click to expand...
Click to collapse
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
tech_head said:
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
Click to expand...
Click to collapse
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
deathsquad737 said:
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
Click to expand...
Click to collapse
I can always get you a copy of the file.
tech_head said:
I can always get you a copy of the file.
Click to expand...
Click to collapse
Yes please I pm you
A.L.B/E.B.B
Thank you but...
First of all, thanks for the post. Although I appreciate the helpful post, my phone is now stuck in boot loop . I hate to be the one to open up an old thread but I'm freaking out at the moment due to brick fever :crying: My current setup was a rooted LG G3 VS98512b. My goal was simple, I didn't want to do anything crazy, I just wanted to enable wifi tether now I'm afraid I've lost everything... Is there a way I can get back into the storage of my phone and delete the modified build.prop, remove the ".bak" from the original and be back to the good life? Any assistance is greatly appreciated, this seemed like such a simple modification that led to such a big headache.
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
trent999 said:
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
soundmasterx said:
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
Click to expand...
Click to collapse
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Digital_MD said:
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Click to expand...
Click to collapse
Again, thank you for the response. Do you recommend a specific method or tutorial for trying restore the original build.prop? I did search however, because this scenario is so specific I'm not sure there is an exact solution to my problem.
Again, just in case someone else can chime in, I followed the instructions on the first post of this thread (see first post for detailed info). I copied the original build.prop then changed the name of the original build.prop, edited the copy, moved it to the original directory and restarted the phone. Now my phone doesn't make it to the Verizon screen (I think it is stuck in boot loop), the screen stays black and the small led on the left corner flashes blue and green. If I can just get access to the storage I can replace the modified build.prop with the original that is still in the same directory just renamed. It seems like such an easy task but, I just don't know how to go about it I'm a somewhat of an old school tinker, I'm just now getting back into the swing of Android... Thanks in advance!!
Bump
Bump please
This is crazy... I changed 2 values in build.prop for tethering and my phone wont boot now... I didnt install a ROM, change DPI, or make any major changes WTF???
Do you have a custom recovery (twrp)?
Can you connect to your phone with adb?
If you have twrp, search the board for the startup hardware key sequence to reach twrp, else from adb do a reboot recovery.
In twrp, you can select to mount system, then go to advanced - file manager. You can delete the bad build.prop, rename the good one, then set the permissions on the good one. If your good copy of build.prop is on a PC, put it on a flash drive, and use twrp's file manager to get it into your phone.
If you have a saved copy of build.prop on your PC, you can also use adb's push command. (You may also want to look at the adb shell command. The sequence might be to open a shell, delete the bad build. prop, get the right build.prop into the right directory, then chmod the right build.prop so it has the proper permissions.)