How to edit build.prop file on almost any android phone SAFELY? - Galaxy S II General

So guys...after surfing many websites..restoring my nandroid backup for almost 10 times i finally found a safe way to edit the build.prop file.. I don't exactly know if this happens on other android smartphones but whenever you try to edit the build.prop file via any editor on your phone or in my case even via adb i get bootloops...
So i tried remounting system and then unmounting it...i tried many file editors file explorers but every time what i got was a god damn phone stuck at the galaxy s2 logo
And also i would mention that I SEARCHED OVER XDA TOO!!.....the guys had great tools developed but they did not work in my case either.
So no more talkingss.....just how to do it...its rather very simple...you just need an app called Rom Toolbox...its free as well as paid too...download as per your requirement.. AND obviously YOU NEED ROOT.
Well open it(duh) and go into the performance tab and select the build.prop editor...well i will explain you what these values stand for...i am not going to explain each and every value but the ones you would require...leave the unlisted in the comments...
ro.build.date - Change your roms build date
ro.build.description - Your phone's description
ro.build.display.id - Change the build no.(dont use it on custom roms....respect the devs)
ro.build.product - Change your model number....
ro.build.version.release - change the android version(not really actually )
ro.product.brand - Phone's company (Samsung in my case)
ro.product.device - Change the device name
ro.product.model - change the model number
ro.sf.lcd_density - Change the lcd density(dont ask me what it is...google it)\
So guys dont change the values out of range like setting lcd density to 5000...or anything else...and also if anything happens to your phone I AM NOT RESPONSIBLE....
also this is my first thread so guys bear with me....i am a new semi pro java developer i would really like to contribute....

build.prop editing = Root Explorer, long press, open in text editor...

karendar said:
build.prop editing = Root Explorer, long press, open in text editor...
Click to expand...
Click to collapse
+1
Sent from my GT-I9100 using XDA

Or build.prop editor from the market.

Never had any trouble editing the LCD Density with root explorer :/

B3311 said:
Or build.prop editor from the market.
Click to expand...
Click to collapse
I second this.

I had bootloops....
I had bootloops dont you guys read.......!! I used root explorer...and text editor too
May be its the rom thats causing problems......

rohan999 said:
I had bootloops dont you guys read.......!! I used root explorer...and text editor too
May be its the rom thats causing problems......
Click to expand...
Click to collapse
Check for ownership and permissions before restarting. They are probably messed up and are causing bootloops. Or you made a typo somewhere and cause bootloops that way. Root Explorer always works fine for me.

No bootloops here either using root explorer or rom toolbox
Sent from my GT-I9100 using Tapatalk

rohan999 said:
I had bootloops dont you guys read.......!! I used root explorer...and text editor too
May be its the rom thats causing problems......
Click to expand...
Click to collapse
Maybe it's you bro
Sent from my GT-I9100 using xda premium

Please be dont be too hard on him. And i heard someone said it needs to be edited at two places sometimes, but i didnt read the threaded comments till the end. Its lost now. I guess thats that the thread starter means. On some roms, it caused bootloops. Is there any special thing to be taken care of cuz bootloop does happen on certain roms when u edit the build.prop on certain custom roms? On stock deodexed roms, no issues for me
Sent from my GT-I9100 using xda premium

The OP is definitely onto something, because it happened to me.
Specifically, I was trying to edit the DPI setting. Out of the stock ROM, the lcd_density setting was present twice in the file (kind of strange, but oh well - normally it shouldn't cause problems). Edited from 240 to 200 without typos, I'm not allowed to do that due to my line of work , reboot, bam! boot loop.
Replaced the build.prop from backup, edited with "build.prop Editor" from Market - no problems. Really don't see what was the difference, except the duplicated key which was gone after editing with build.prop Editor (probably it does some sort of unique key checking). Oh well, not serious enough to investigate further.

VAXXi said:
The OP is definitely onto something, because it happened to me.
Specifically, I was trying to edit the DPI setting. Out of the stock ROM, the lcd_density setting was present twice in the file (kind of strange, but oh well - normally it shouldn't cause problems). Edited from 240 to 200 without typos, I'm not allowed to do that due to my line of work , reboot, bam! boot loop.
Replaced the build.prop from backup, edited with "build.prop Editor" from Market - no problems. Really don't see what was the difference, except the duplicated key which was gone after editing with build.prop Editor (probably it does some sort of unique key checking). Oh well, not serious enough to investigate further.
Click to expand...
Click to collapse
How did u replace it with ur backup? I normally restore back my nandroid. Is there a much simpler way such as putting it in an update zip or something? Mind to share?
Sent from my GT-I9100 using xda premium

kyleforge said:
Maybe it's you bro
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
bpivk said:
Check for ownership and permissions before restarting. They are probably messed up and are causing bootloops. Or you made a typo somewhere and cause bootloops that way. Root Explorer always works fine for me.
Click to expand...
Click to collapse
override182 said:
Please be dont be too hard on him. And i heard someone said it needs to be edited at two places sometimes, but i didnt read the threaded comments till the end. Its lost now. I guess thats that the thread starter means. On some roms, it caused bootloops. Is there any special thing to be taken care of cuz bootloop does happen on certain roms when u edit the build.prop on certain custom roms? On stock deodexed roms, no issues for me
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
thank you really mate....you are not like the others who just need a reason to insult.....well this is my first thread...so its noobish....but i am a programmer (java) so i will be bringing some good roms later..

override182 said:
How did u replace it with ur backup?
Click to expand...
Click to collapse
I made a copy of /system/build.prop before editing it, of course. After rebooting and getting the bootloop, it's just replacing this file from the backup copy.

I've been using build.prop editor from Nathan Campos, 0 issues so far.

VAXXi said:
I made a copy of /system/build.prop before editing it, of course. After rebooting and getting the bootloop, it's just replacing this file from the backup copy.
Click to expand...
Click to collapse
Im still not clear on this. How did u managed to replace when u cant boot the device and edit it back again to the working build.prop. Did u push back via adb or some update.zip?
Sent from my GT-I9100 using xda premium

The device boots just fine, it just doesn't complete the booting process and remains at the spinning S with blue particles. You can use ADB during that time.

VAXXi said:
The device boots just fine, it just doesn't complete the booting process and remains at the spinning S with blue particles. You can use ADB during that time.
Click to expand...
Click to collapse
Noted. Thx
Sent from my GT-I9100 using xda premium

rohan999 said:
thank you really mate....you are not like the others who just need a reason to insult.....well this is my first thread...so its noobish....but i am a programmer (java) so i will be bringing some good roms later..
Click to expand...
Click to collapse
Most of us didn't insult. Don't jump the gun. Just giving the other side of the coin. Root explorer editing works fine, as others have stated it's possibly a messed up rom giving weird permissions to build.prop. chmod 644 build.prop usually solves the issue though.
I can't speak for everyone, but I wasn't hard on you... Noobs are noobs and I'm fine with that. Most info is readily available on the forums though... Just not necessarily on this forum. XDA is bigger than the sgs2 forums and other communities have very interesting ideas and threads!
***edit*** yeah, after re-reading, noone was harsh in any way. So... yeah!
Sent from my GT-I9100

Related

[HELP] get verizon/protected apps on sprint based roms like aloysius v12?

the title says it all how can i get those types of apps working on roms based on other phones? i have aloysius v12 but i want to use the verizon apps that come in the market but they are not there. is there i fix or patch so i can use skype or something like that?? i installed an APK i backed up but when i install it it says this app is not available for this phone. can someone please help?
Can you pull ur build.prop and attach it to a post here?
TopazAaron said:
Can you pull ur build.prop and attach it to a post here?
Click to expand...
Click to collapse
where and how do i do that?
Working on a fix right now. Gimme a little bit and I'll have it up.
Doesn't jcase's market fix help this kind of problem?
Sent from my FroyoEris using XDA App
snyluc13 said:
Doesn't jcase's market fix help this kind of problem?
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
I ran into this problem too running the Sprint based Fresh rom. While Jcase's Market Fix will fix the problem with missing protected apps, it wont fix the missing Verizon apps.
To do that, I used Root Explorer on my phone and opened the "build.prop" file located in the System folder. Open the file in the included text editor and scroll down to until you see this line:
"ro.cdma.home.operator.numeric"
The correct value for the line should be "310012". Sprint roms will have the value as "310120".
Save the changes and exit. After reboot, check your Market. The right-most tab on the main page will read "Verizon" now instead of "Downloads".
Or flash this handy zip from recovery.
FunkyFender said:
Or flash this handy zip from recovery.
Click to expand...
Click to collapse
thanks ...works great
FunkyFender said:
Or flash this handy zip from recovery.
Click to expand...
Click to collapse
Lol. Where were you when I needed you earlier?
PPCGeek01 said:
Lol. Where were you when I needed you earlier?
Click to expand...
Click to collapse
At work unfortunately. These back-to-back shifts are killing me.
FunkyFender said:
Working on a fix right now. Gimme a little bit and I'll have it up.
Click to expand...
Click to collapse
thanks i really want to use those apps
edit: thanks for the fix, works like a charm
Anyone else having issues with the my Verizon app? Everytime I go into it it states phone number can not be verified
FunkyFender said:
Or flash this handy zip from recovery.
Click to expand...
Click to collapse
I know this is probably elementary, but is there a step by step post anywhere for flashing a zip file?
I just rooted last night and put the first custom ROM on my phone. This is uncharted territory for me. Everything is great so far except for these missing apps.
I tried the root explorer method, but it would only let me read the text, not edit.
EDIT: Ignore this post. GREAT SUCCESS!! Too easy.
PPCGeek01 said:
I ran into this problem too running the Sprint based Fresh rom. While Jcase's Market Fix will fix the problem with missing protected apps, it wont fix the missing Verizon apps.
To do that, I used Root Explorer on my phone and opened the "build.prop" file located in the System folder. Open the file in the included text editor and scroll down to until you see this line:
"ro.cdma.home.operator.numeric"
The correct value for the line should be "310012". Sprint roms will have the value as "310120".
Save the changes and exit. After reboot, check your Market. The right-most tab on the main page will read "Verizon" now instead of "Downloads".
Click to expand...
Click to collapse
Thank you.
I was doing it the hard way - download the app in a HTC/VZW Rom, copy them to SD, restore the Sprint ROM (Aloysius V12) and install.
Looking at them now in the Market.
bftb0
THANKS. This worked great for me.

Screen after 2.3.4 Update

Hey Guys, I updated and rooted my phone to 2.3.4 HK...
Anyways, I remember seeing a post about an app that lets you enable the whole screen.
It appears that I have some dead space on the main home screen and I can not place any widgets in it (Its in the bottom)...
Any way I can fix that ? I cant remember the app name for the life of me.
thank you,
Alex
Hey, just use root explorer or shell in order to edit the build.prop in your system folder (or just use CWM and mount your /system folder to your computer). in the build.prop, there is a section that describes the ppi and for some reason, it's set as default to 240. Change it to 275 and it should fix all screen issues.
thanks for your response!! I checked thru Root Explorer, and only found
dpi... not PPI.. is that what you meant? Cause I see that listed as 240.
Also, do I need to reset after the edit?
Thanks a lot!!
The stock launcher seems to be messed up, get a different launcher.
Sent from my MB860 using XDA App
Some people have complained about the resulting effects of changing the build.prop file with this fix. Better to just use a different launcher than stock as was said.
LCD density for root I believe it is the 270 setting you need to select.
Sent from my MB860 using XDA App

dpi ? whats the deal?

can someone take the time to school a noob on DPI? I change the dpi n my ro.build and I see no difference... pretty sure I am misunderstanding some part of it.
From my understanding you change the build.prop... save and exit the text editor (must be rooted) and restart the device... I've been using that method on my galaxy nexus and now nexus 7 and it works perfect... think of lowing the dpi as in tricking the OS into thinking you have a bigger screen than you actually have... thus making everything smaller and also triggering tablet mode
No I've been there and done this too. If you open and save the file... then open it back up, the changes are reverted. Yea I was rooted and was using root explorer. Once I flashed a custom rom, I could change it no problem. Maybe something with stock rom or something else not allowing the file to change, even though the folder is R/W and all that.
The file keeps reverting back after you save it.
Sent from my Nexus 7 using xda premium
player911 said:
No I've been there and done this too. If you open and save the file... then open it back up, the changes are reverted. Yea I was rooted and was using root explorer. Once I flashed a custom rom, I could change it no problem. Maybe something with stock rom or something else not allowing the file to change, even though the folder is R/W and all that.
The file keeps reverting back after you save it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
It should work if the folder is R/W and you save and exit. Maybe you should try es Flie Explorer?
I was rushed while posting that and I believe I was completely unclear. I did edit the you Build.prop, I am on a custom rom sgt7 and the dpi and build.prop and DPI was 213 I think maybe 216, I changed it to 180 and I saw no difference at all. this is possibly because there are other modifications to the Rom that aren't dpi dependent or something.

Need help with build.prop edit

I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
in_dmand said:
I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
Click to expand...
Click to collapse
I can do that above with RE, very strange problem you have.
Try a build.prop editor, i used this in the link. It sets correct permissions after editing and so on. Use the pencil icon in the bottom right to edit.
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Hi,
Same thing for me with Root Explorer, instead I use build.prop Editor
EDIT: not fast enough :laugh:
qsec said:
I can do that above with RE, very strange problem you have.
Try a build.prop editor, i used this in the link. It sets correct permissions after editing and so on. Use the pencil icon in the bottom right to edit.
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Click to expand...
Click to collapse
I got it and tried exactly like you said, and while it does pull it up and my keyboard pulls up and I can feel the haptic feedback, no letters will be inserted in deleted...? Really weird.
Maybe it's related to my root access? TB is showing I'm rooted, but check out my superuser app when I try to update an install new binaries...
Get rid of Superuser and try SuperSu instead. Sometimes the old Superuser has issues on ROMs since ICS.
EniGmA1987 said:
Get rid of Superuser and try SuperSu instead. Sometimes the old Superuser has issues on ROMs since ICS.
Click to expand...
Click to collapse
Downloaded and installed... Removed the old one. Still not letting me edit... Looks an feels like it is but won't enter any characters. At least RE isn't giving me the "too large" error anymore
in_dmand said:
I got it and tried exactly like you said, and while it does pull it up and my keyboard pulls up and I can feel the haptic feedback, no letters will be inserted in deleted...? Really weird.
Click to expand...
Click to collapse
i had the same issue, couldn't figure out why. try replacing a commented line with the code to disable the nav bar
How do I know if it's just a commented line and not necessary to the program?
in_dmand said:
I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
Click to expand...
Click to collapse
i had the same issue any help?
If you are in stock android 4.4.2 dont do it
You will stuck on bootloop
If you still wand to do let copy your build.prop to pc and edit with notebat++ or some program and recopy overwrite to your phone
Sent from my LG-D802 using xda app-developers app
maxkanick said:
If you are in stock android 4.4.2 dont do it
You will stuck on bootloop
If you still wand to do let copy your build.prop to pc and edit with notebat++ or some program and recopy overwrite to your phone
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
You are right, I have tried to edit it on pc and stuck on a bootloop.
Use build.prop editor app from playstore
_____________________________________Read more write less and be smart

"I'm rooted, so what's next?", 3 cool tweaks you can do with a rooted G4

rirozizo said:
For all the people that are blaming this method for their bootloops, i can tell you one thing: you didn't follow this method correctly.
USING ROOT EXPLORER WILL RESULT IN A TRUNCATED BUILD.PROP FILE!
I clearly said "I'm using ES File Explorer for that" and that is for a reason. I prefer root explorer for anything that it can do because it's just so much faster. But ES file explorer can edit a text file no matter what size it is, root explorer will just cut it off at the bottom resulting in a bootloop.
Thank you for understanding.
Click to expand...
Click to collapse
Here's a video I made showing off 3 awesome tweaks found here on this device's forum. XDA made our beloved G4 a LOT better with "just" root.
If the above embedded video doesn't work for some reason, here's the youtube link: https://www.youtube.com/watch?v=Z4X2FF3BwjA
Have fun watching!
Thanks for the video! Pretty sweet to have 60 fps now on this amazing camera. Other two I already knew and did change the dual window one. The DPI was something that never bothered me.
thanks
Great video. One thing to mention is you can click the '1/2' square button next to the X on the recents screen to pick your dual window apps also
You can change the DPI without root via an adb command.
Is there any way to make nandroid style full backups without custom recovery? It would be nice to have that before trying tweaks.
Modified build.prop to true for multi window and got a bootloop.
mrnovanova said:
Modified build.prop to true for multi window and got a bootloop.
Click to expand...
Click to collapse
That's weird, didnt occur to me
wadamean said:
That's weird, didnt occur to me
Click to expand...
Click to collapse
We probably don't have the same variant. I have the H812 and editing build.prop causes bootloops for me.
changing the DPI always results in bootloop for me. I'm with an international H815.
Use an app that is designed to edit the build.prop. It's a large file. Standard text editors will likely truncate the file, resulting in boot loops.
Sent from my LG-H811 using Tapatalk
Make sure you are using a good editor. Some editors alter the integrity of the file and save it funky.
I used the non root method for dpi but you can use DPI changers in the play store. I like Tex_Droider.
Thanks to you I'm now stuck at t-mobile boot logo after editing split window to true. Tried restarting and factory erasing with holding down volume and power key but after rest I'm stuck at logo again.
eulin87 said:
Thanks to you I'm now stuck at t-mobile boot logo after editing split window to true. Tried restarting and factory erasing with holding down volume and power key but after rest I'm stuck at logo again.
Click to expand...
Click to collapse
Same thing happened to me. Just flash the root file again in download mode an you should be fine. For the record you can't be mad at the op. He didn't put a gun to your head.
Root file will do nothing because it won't replace the build. Prop. I had to restore using KDZ. And he did use a gun. You weren't there
Sent from my LG-H811 using XDA Free mobile app
mrnovanova said:
We probably don't have the same variant. I have the H812 and editing build.prop causes bootloops for me.
Click to expand...
Click to collapse
I have the Wind h812. Made a couple of changes in the build.prop and everything works fine.
---------- Post added at 12:34 AM ---------- Previous post was at 12:32 AM ----------
1080p 60fps works great. Thanks!
always remember to check the build prop permissions (make sure it's rw r r)
eulin87 said:
Root file will do nothing because it won't replace the build. Prop. I had to restore using KDZ. And he did use a gun. You weren't there
Sent from my LG-H811 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know which root method you uses but since low effort root consists in flashing the whole modified image of the rom it's pretty much the same as using KDZ but a whole lot faster. Like I said it did work for me.
---------- Post added at 06:36 AM ---------- Previous post was at 06:35 AM ----------
GetPatriotized said:
I have the Wind h812. Made a couple of changes in the build.prop and everything works fine.
Click to expand...
Click to collapse
For real? Which file manager did you use. I used root explorer. Should I try with ES?
partylikeaninjastar said:
Use an app that is designed to edit the build.prop. It's a large file. Standard text editors will likely truncate the file, resulting in boot loops.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
You are absolutely right. Used ES instead of root explorer and it worked.
For all the people that are blaming this method for their bootloops, i can tell you one thing: you didn't follow this method correctly.
USING ROOT EXPLORER WILL RESULT IN A TRUNCATED BUILD.PROP FILE!
I clearly said "I'm using ES File Explorer for that" and that is for a reason. I prefer root explorer for anything that it can do because it's just so much faster. But ES file explorer can edit a text file no matter what size it is, root explorer will just cut it off at the bottom resulting in a bootloop.
Thank you for understanding.
@eulin87 that's a dangerous statement there, please don't joke about it because XDA Staff might take that seriously and message me and all that. Thank you for understanding the situation guide makers are being put in
Have fun rooting!
Sent from my LG-H815 using Tapatalk

Categories

Resources