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.
Hello i have the stock 2.3.4 gingerbread installed and tried the crt lock animation tutorial but not working. Does it only with the coderomv1 working because that file isnt avail for download or is there any other way to get that cool animation. i installed the coderomv1_default.zip but nothing has changed i think because i not installed the coderom himself.
Hope to help me out i want that crt lock animation it is really cool.
neophyte1983 said:
Hello i have the stock 2.3.4 gingerbread installed and tried the crt lock animation tutorial but not working. Does it only with the coderomv1 working because that file isnt avail for download or is there any other way to get that cool animation. i installed the coderomv1_default.zip but nothing has changed i think because i not installed the coderom himself.
Hope to help me out i want that crt lock animation it is really cool.
Click to expand...
Click to collapse
This will not work by default in stock.You have to change one binary value in bools.xml in framework-res.apk and then edit build.prop.Follow this tutorial and then edit build.prop.
forum.xda-developers.com/showthread.php?t=1138800
skynet28 said:
This will not work by default in stock.You have to change one binary value in bools.xml in framework-res.apk and then edit build.prop.Follow this tutorial and then edit build.prop.
forum.xda-developers.com/showthread.php?t=1138800
Click to expand...
Click to collapse
I made all steps but not working on 2.3.4 but i saw something is it normal that when i paste with root explorer the build.prop file to the system folder it shows the old on with old date etc. i have the clue that maybe it doesn´t copy it in the folder??? Dunno but it is always the same date there. My phone is rooted.
neophyte1983 said:
I made all steps but not working on 2.3.4 but i saw something is it normal that when i paste with root explorer the build.prop file to the system folder it shows the old on with old date etc. i have the clue that maybe it doesn´t copy it in the folder??? Dunno but it is always the same date there. My phone is rooted.
Click to expand...
Click to collapse
Did you use apktool to edit the values,put resources.arsc in the original and then copied modified framework-res.apk into the /system/framework/framework-res.apk ? Was it copied there? If not check that root explorer is mounted in read/write mode.Same for build.prop.I think you didn't copy it.
skynet28 said:
Did you use apktool to edit the values,put resources.arsc in the original and then copied modified framework-res.apk into the /system/framework/framework-res.apk ? Was it copied there? If not check that root explorer is mounted in read/write mode.Same for build.prop.
Click to expand...
Click to collapse
No i downloaded the finished apk from the thread the crt.zip and in the zip is the apk also i tried it with apk tool but windows 7 tell me something with "java" i have java on pc but it not working.
Can you maybe upload the apk file and the prop file so i just copy it inside the phone.
I am new in that materia.
neophyte1983 said:
No i downloaded the finished apk from the thread the crt.zip and in the zip is the apk also i tried it with apk tool but windows 7 tell me something with "java" i have java on pc but it not working.
Can you maybe upload the apk file and the prop file so i just copy it inside the phone.
I am new in that materia.
Click to expand...
Click to collapse
No..never use apk from another phone model.
skynet28 said:
No..never use apk from another phone model...I will upload tomorrow.
Click to expand...
Click to collapse
Thank you that will help me a lot i want that crt animation but not want to install theme or coderom that will help me thank you.
skynet28 said:
This will not work by default in stock.You have to change one binary value in bools.xml in framework-res.apk and then edit build.prop.Follow this tutorial and then edit build.prop.
forum.xda-developers.com/showthread.php?t=1138800
Click to expand...
Click to collapse
I made all steps wisely result is a bootloop with white screen
I am sick of it!!
I tried all stuff but that **** animation will not work.
I think it only works if the coderomv1 is flashed with the stock rom there is no way to get that animation working i tried all with the framework-res.apk no success with a theme no success i give up now no crt animation for me because i don´t know what can i do only flashing the coderomv1 but that i wouldn´t do because i not want the coderomv1.
neophyte1983 said:
I am sick of it!!
I tried all stuff but that **** animation will not work.
I think it only works if the coderomv1 is flashed with the stock rom there is no way to get that animation working i tried all with the framework-res.apk no success with a theme no success i give up now no crt animation for me because i don´t know what can i do only flashing the coderomv1 but that i wouldn´t do because i not want the coderomv1.
Click to expand...
Click to collapse
You had to set permisssions after copying framework-res.apk -rw -r -r.same with build.prop
With CRT animation enabled,you will lose your samsung boot screen in stock kph....I have managed to enable boot screen animation only through cf-root kernel.I don't have coderom but crt is enabled through this method and have brought custom boot animation through cf-root kernel.
Hi everyone, i used to tommytomatoes linux software to work on framwork and com.htc.resource files and all seemed to go fine with tommy's tools. no errors.
i pushed them to my phone and then installed them using adb.
i restart the phone and end up in a bootloop.
all i did was edit the colors.xml file to change the color and nothing else, no images, not a thing.
is there a way to figure out what is wrong with the 2 apk's i edited?
Thanks for any and all assistance, xml editing is killing me.
what ROM is it from? odex or not?
i used the apk's from king cobras rom.
I can't quite remember (and it could be different on a GSM ROM but I doubt it) but I think if you edit xml you need to remove the arsc or dex from the apk before you recompile.
you can ask here - lots of great help there, including tommyt
http://forum.xda-developers.com/showthread.php?t=1320891
hackit said:
Hi everyone, i used to tommytomatoes linux software to work on framwork and com.htc.resource files and all seemed to go fine with tommy's tools. no errors.
i pushed them to my phone and then installed them using adb.
i restart the phone and end up in a bootloop.
all i did was edit the colors.xml file to change the color and nothing else, no images, not a thing.
is there a way to figure out what is wrong with the 2 apk's i edited?
Thanks for any and all assistance, xml editing is killing me.
Click to expand...
Click to collapse
If any .xml's are edited, before you recompile the .apk, you should remove the resources.arsc file. Then, compile.
^^^ that thanks, I couldn't remember lol.
pinky059 said:
If any .xml's are edited, before you recompile the .apk, you should remove the resources.arsc file. Then, compile.
Click to expand...
Click to collapse
il Duce said:
^^^ that thanks, I couldn't remember lol.
Click to expand...
Click to collapse
where is the resource.arc file i have looked in the decompiled apk and i dont see it, but i see it in one that i havent decompiled?
ok i keep getting stuck bootlooping.
I have removed the resources.arsc file and lef tit in and either way it's the same, all i'm editing is the colors.xml and nothing else.
If i post my colors.xml and the apk can you maybe try it and see if you can do it?
Thanks to anyone willing to take the time to do this.
Kev
dased14 said:
where is the resource.arc file i have looked in the decompiled apk and i dont see it, but i see it in one that i havent decompiled?
Click to expand...
Click to collapse
it build when you compile - then delete from "keep" or whatever before you "finish" (in apkmanager anyway)
hackit said:
ok i keep getting stuck bootlooping.
I have removed the resources.arsc file and lef tit in and either way it's the same, all i'm editing is the colors.xml and nothing else.
If i post my colors.xml and the apk can you maybe try it and see if you can do it?
Thanks to anyone willing to take the time to do this.
Kev
Click to expand...
Click to collapse
post your exact edits, and you MUST remove arsc when edited xml, and your apk here with what you're trying to do >>
http://forum.xda-developers.com/showthread.php?t=1320891
Hello guys
I need your help, i'm working on a mod and a friend said me to modify the file: settings.db located in data/data/com.android.providers.settings/databases/settings.db
I only have to change "1" to "0" in the "secure" tab
for this I used Sql Lite browser for windows 7.
So i did it and saved the database, and then with root explorer replaced with the original settings.db but ....
I entered in a boot loop, why ?
I know for sure the "0" is a secure value, because used in a stock old rom
Why bootloop so? Have I to changed permissions to file?
Can please help me to do it without a new bootloop?
Thanks
hello
please i need to know if to change the permissions like that of original file prevent me to enter in a boot loop.
Noone have never edited settings.db file and replaced it?
If i am in wrong section, please, move the thread in the correct one.
I've done it before to modify wifi timeout. Here's the instructions I used:
http://forum.xda-developers.com/showthread.php?t=774507
polobunny said:
I've done it before to modify wifi timeout. Here's the instructions I used:
http://forum.xda-developers.com/showthread.php?t=774507
Click to expand...
Click to collapse
Did you change file permissions?
maRRRco89 said:
hello
please i need to know if to change the permissions like that of original file prevent me to enter in a boot loop.
Noone have never edited settings.db file and replaced it?
If i am in wrong section, please, move the thread in the correct one.
Click to expand...
Click to collapse
I bet you replaced the settings.db file with the edited version using ADB? If so you likely stamped the file with shell as the owner... This might have been the problem if the original file had different permissions / owner.
polobunny said:
I've done it before to modify wifi timeout. Here's the instructions I used:
http://forum.xda-developers.com/showthread.php?t=774507
Click to expand...
Click to collapse
THX
I have to crack the password for 9650108725
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.)