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.
Hi! I want to know how can i change the phone info, in the system settings.
I want to change them for my own rom, so i want to include, for example, a different build date, build number, kernel version, etc..
Help!?
You have to edit build.prop located in /system. You can edit it on the phone itself with a root file explorer or copy it to a computer, edit in a text editor and copy it back to the phone (don't forget to set permissions to the way they were before copying). Once you open build.prop you'll easily find the lines you want to change.
Sent from my Desire HD using xda premium
Hi guys and gals. after many attempts, i have working cricket mms on my evo 3d
So... you root and research a good custom rom for you. You flash it, all goes well, it looks cool, feels nice you are on top of the world... (like I was) then you find your mms does not work...
here you go
1. make sure you have es file explorer downloaded
2. open your es file explorer
3. go to settings and select Root settings
4. check all the boxes and grant for superuser
now you are looking at the files on your sd card
5. click the "slash" icon on the top left
now you are looking at the whole phone
6. scroll down and select "system"
7. scroll down and select " build.prop"
it will ask you which program to use. I used the es note editor
NOTE you will be changing the build properties of you rom from sprint values to Cricket values
BE CAREFUL NOT TO CHANGE ANYTHING ELSE!!!
9. scroll down slowly you will see ro.build.fingerprint=Sprint
delete Sprint and change it to cricket
10. scroll down about 1/2 of the way down and you will see additional build properties
you will be looking for 4 lines
gsm.sim.operator.alpha=(change to Cricket)
gsm.sim.operator.numeric=(change to 310016)
gsm.operator.alpha=(change to Cricket)
gsm.operator.numeric(change to 310016)
and about 3/4 fof the way down
ro.cdma.home.operator.alpha=(change to Cricket)
ro.cdma.home.operator.numeric=(change to 310016)
back out and SAVE
REBOOT TWICE!!!!!!!!
11. now go into you es file explorer again this time to system
12. select etc
13. scroll down to a file called apns-conf.xml
delete it!
download this one and edit it with your phone number with notepad+ on your computer
edit the second one, not the value 45
https://www.dropbox.com/s/mqixefjs829t7jg/apns-conf.xml
put the file on your sd card and copy it to your system/etc folder
REBOOT TWICE!!!
16. using the voice dialer say "open apn"
17. delete the one you see
18. select reset to default
now you should see 2 apns and a little circle beside both
click the circle beside "cricket"
REBOOT TWICE AND WAIT FOR THE SYSTEM TO CATCH UP
download this mms.apk (this is not mine.. i found it for the evo 4g somewhere)
https://www.dropbox.com/s/iq42wk65ifolv8u/Mms.apk
using es file explorer, delete your old mms.apk under system/apps
remember, you have to mount es as root rw every time you reboot
roboot and move the new mms.apk to the system/apps and install
next reboot
go back into es file and (set root rw again)move to the new mms.apk.
long press it and chose permissions.
set your permissions like the screenshot in at the bottom
this has been proven on my evo3d
NOTE. if you are a flashaholic, you will store the mms.apk and the apns-config.xml on your sd card so you can do this with every flash
if this helped you, press the thanks button please!!!
I use cricket and I have never changed the build.prop to get mms working. I change the apn and if it is a jellybean rom the mms.apk.
do you know how to fix mms on htc evo 3d with virgin mobile?
jlmancuso said:
I use cricket and I have never changed the build.prop to get mms working. I change the apn and if it is a jellybean rom the mms.apk.
Click to expand...
Click to collapse
i tried to leave the sprint settings and got it to work (sometimes) it always works for me this way
bosshoss14 said:
do you know how to fix mms on htc evo 3d with virgin mobile?
Click to expand...
Click to collapse
nope... sorry. I only have cricket. but if you search for the apn settings for virgin and put them in, it may work
jaredl45600 said:
nope... sorry. I only have cricket. but if you search for the apn settings for virgin and put them in, it may work
Click to expand...
Click to collapse
Ok thanks :good::good:
Ok so for anyone wondering how to fix mms on virgin mobile/ sprint/ boost follow these instructions provided in this thread http://forum.xda-developers.com/showthread.php?t=1794956
jaredl45600 said:
Hi guys and gals. after many attempts, i have working cricket mms on my evo 3d
So... you root and research a good custom rom for you. You flash it, all goes well, it looks cool, feels nice you are on top of the world... (like I was) then you find your mms does not work...
here you go
1. make sure you have es file explorer downloaded
2. open your es file explorer
3. go to settings and select Root settings
4. check all the boxes and grant for superuser
now you are looking at the files on your sd card
5. click the "slash" icon on the top left
now you are looking at the whole phone
6. scroll down and select "system"
7. scroll down and select " build.prop"
it will ask you which program to use. I used the es note editor
NOTE you will be changing the build properties of you rom from sprint values to Cricket values
BE CAREFUL NOT TO CHANGE ANYTHING ELSE!!!
9. scroll down slowly you will see ro.build.fingerprint=Sprint
delete Sprint and change it to cricket
10. scroll down about 1/2 of the way down and you will see additional build properties
you will be looking for 4 lines
gsm.sim.operator.alpha=(change to Cricket)
gsm.sim.operator.numeric=(change to 310016)
gsm.operator.alpha=(change to Cricket)
gsm.operator.numeric(change to 310016)
and about 3/4 fof the way down
ro.cdma.home.operator.alpha=(change to Cricket)
ro.cdma.home.operator.numeric=(change to 310016)
back out and SAVE
REBOOT TWICE!!!!!!!!
11. now go into you es file explorer again this time to system
12. select etc
13. scroll down to a file called apns-conf.xml
delete it!
download this one and edit it with your phone number with notepad+ on your computer
edit the second one, not the value 45
https://www.dropbox.com/s/mqixefjs829t7jg/apns-conf.xml
put the file on your sd card and copy it to your system/etc folder
REBOOT TWICE!!!
16. using the voice dialer say "open apn"
17. delete the one you see
18. select reset to default
now you should see 2 apns and a little circle beside both
click the circle beside "cricket"
REBOOT TWICE AND WAIT FOR THE SYSTEM TO CATCH UP
download this mms.apk (this is not mine.. i found it for the evo 4g somewhere)
https://www.dropbox.com/s/iq42wk65ifolv8u/Mms.apk
using es file explorer, delete your old mms.apk under system/apps
remember, you have to mount es as root rw every time you reboot
roboot and move the new mms.apk to the system/apps and install
next reboot
go back into es file and (set root rw again)move to the new mms.apk.
long press it and chose permissions.
set your permissions like the screenshot in at the bottom
this has been proven on my evo3d
NOTE. if you are a flashaholic, you will store the mms.apk and the apns-config.xml on your sd card so you can do this with every flash
if this helped you, press the thanks button please!!!
Click to expand...
Click to collapse
why the hell hasn't more people been to directed to this thread with unbeatable mms problems with cricket just changing apn settings DOES NOT WORK for alot of cricket users.
Edit: guess i shoulda seen that it was done on a evo3d as it didn't work for my evo 4g i shoulda known when two lines were missing from the build prop. as soon as i got to the voice dialer with the apns there were no apns listed and hitting reset to default brough nothing. back to the battery sucking no blue tooth everything cricket rom. Ive tried litterally hundreds of roms and mustve edited apns 1000 times and still cant get mms to work except for one rom.
The mms.apk was found on a evo 4g site somewhere. Maybe there is something else. Or maybe it was a 4g LTE. I don't remember now, but I know it will not work on stock versions of sprint ROMs. I tried.....
Sent from my PG86100 using xda premium
Guys,
I can't post in the official thread here:
http://forum.xda-developers.com/lg-g3/development/guide-headphone-speaker-volume-booster-t2819821
But I just wanted to confirm that if you root your device and follow the directions here, I've got confirmed working on the Sprint LS990 variant of this phone. The thread mentions nothing of this on Sprint or the LS990 but I can confirm that it is indeed working.
You'll need to:
1. Have root with SuperSU installed
2. Install Root Browser and 920 Text Editor (Available in market for free)
3. Navigate to system/etc and then mixer_paths.xml
4. Change file permissions to rw-r-r
5. Save to your downloads folder just in case you trash your phone or something
6. Navigate to markers mentioned in thread link above. The LS990 variant will have aforementioned markers listed approximately 15 lines later in the code. Edit them to your liking.
7. Save, reboot, pray not to get caught in limbo.
8. Enjoy having better sound than everyone else with a phone.
Just an FYI anyone attempting this: If you do not edit the permissions correctly when overwriting the file the phone will not boot. It will get stuck at the yellow sprint screen and you will have to preform a reset.
Root browser did not allow me to change permissions correctly and when going quickly I did not notice it when overwriting.
However, second attempt after recovery it worked great.
Thanks for the info TROPhouse
So i havnt edited yet but permissions look right here. Will they change after I edit and save. And then change them back right. I don't wanna get stuck since we have no custom recovery yet.
Did it. It was way worth sweatin through the reboot process. Haha.
Has anyone thats using Viper used this mod?
Sent from my LGLS990 using Tapatalk
sinisin said:
Has anyone thats using Viper used this mod?
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
I'm using viper. Works perfect. After installing I moved the app from data/app to system/app. Heard people were having it being stopped after using it for awhile and this was there fix for that.
Kept having permission issue and was kind of nerve wrecking with no recovery.... However, phone sounds awesome now!
stagejuan said:
Kept having permission issue and was kind of nerve wrecking with no recovery.... However, phone sounds awesome now!
Click to expand...
Click to collapse
What settings did you end up with. I used 68 or 69 on all mine and it's pretty good. Not sure if I want it louder or quieter but it's definitely way better than stock was.
delete
Mahapederdon said:
What settings did you end up with. I used 68 or 69 on all mine and it's pretty good. Not sure if I want it louder or quieter but it's definitely way better than stock was.
Click to expand...
Click to collapse
I did 69 which seems perfect to be honest... I mainly hear music at the gym and usually use soundcloud... at 69, I don't even get close to full volume on the phone now. Its perfect
it seems like there are another few steps in this process that aren't being mentioned, like how to save the mixer_paths file because following the instructions and updating the lines I want to update then trying to save with 920 text editor ends with the message that it's a read only system file.
Anyone care to fill in the blanks as to how you get the update to stick?
thanks!
Super loud
Thanks! Great volume!:victory:
dk2463 said:
it seems like there are another few steps in this process that aren't being mentioned, like how to save the mixer_paths file because following the instructions and updating the lines I want to update then trying to save with 920 text editor ends with the message that it's a read only system file.
Anyone care to fill in the blanks as to how you get the update to stick?
thanks!
Click to expand...
Click to collapse
Don't know if this is too late to help, but...
I don't use 920, but my guess is there's an option somewhere (probably in settings for the app) to switch the file system to read - write mode, instead of read-only. I use the FX app, and that's what I had to do with it. Be sure to set it back to read-only when you're done.
dk2463 said:
it seems like there are another few steps in this process that aren't being mentioned, like how to save the mixer_paths file because following the instructions and updating the lines I want to update then trying to save with 920 text editor ends with the message that it's a read only system file.
Anyone care to fill in the blanks as to how you get the update to stick?
thanks!
Click to expand...
Click to collapse
SUCCESS!
So you need to download an app that will mount your system, I used an app called mount/system. You launch it then select Mount r/w. Once you do that you have the needed access to edit the files as listed. I used this guide as well and had success....hope this helps others!
copy the original mixer_paths to your memory by ES file
edit it by notepad++ on windows and put it again in your memory
copy it from internal to your /system
highlight it and set permissions rw r r
move it from /system to /system/etc/
reboot and enjoy
Has anyone tryied playing with bluetooth volume i cant find where to change it any sugestions?
Nice, I haven't had any issues with my phone being too quiet, but I also came from a Verizon G2. Those were noticeably horrible for volume levels, so the G3 is a welcome change.
In regards to all the questions about which app to use for which function:
You could use Root Explorer, or any other file explorer that has root capabilities (ES File Explorer, Total Commander). You do NOT need to use a specific app set and if your file explorer can't mount/unmount the system partition with root permissions, try a new one because that one sucks.
You also should not be downloading three separate apps to accomplish this. It's kind of overkill to have a file explorer, a text editor, and a system partition mounter when any decent file explorer has all three of those built in. I think ROM Toolbox even has all those capabilities in the free version.
RandomPooka said:
Nice, I haven't had any issues with my phone being too quiet, but I also came from a Verizon G2. Those were noticeably horrible for volume levels, so the G3 is a welcome change.
In regards to all the questions about which app to use for which function:
You could use Root Explorer, or any other file explorer that has root capabilities (ES File Explorer, Total Commander). You do NOT need to use a specific app set and if your file explorer can't mount/unmount the system partition with root permissions, try a new one because that one sucks.
You also should not be downloading three separate apps to accomplish this. It's kind of overkill to have a file explorer, a text editor, and a system partition mounter when any decent file explorer has all three of those built in. I think ROM Toolbox even has all those capabilities in the free version.
Click to expand...
Click to collapse
Agreed but I downloaded ES File Explorer and several others and I was unable to find the ability to mount as r/w. If the option is in those apps, it's very much hidden so an app to mount your file system then an editor was what I needed and it worked.
dk2463 said:
Agreed but I downloaded ES File Explorer and several others and I was unable to find the ability to mount as r/w. If the option is in those apps, it's very much hidden so an app to mount your file system then an editor was what I needed and it worked.
Click to expand...
Click to collapse
ES's current interface does hide a lot, and is in almost every way inferior to the original interface. But the option is there. It's also in FX (File Explorer) which is my root editor of choice.
the pursuit of sound quality! bullet for my valentine cant be heard on stock!!!!!!!
tried this. guess i messed up. stuck on spark screen. sat and read through the pages here. gotta fix my phone when i get home tonight.
what did you change you volume levels to?
So can those who have successfully made the edits share what volume levels you changed and what are the new numbers? I've made the change to mine and even with my $100 earphones there's distortion at what I feel is a low level. I'm thinking maybe there's a balance among these that I need to achieve?
thanks!
dk2463
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.)