Hi all actually i'm running DFT NAND ROM and i'm just wondering how can i modify the system files as they are read only (for istance i'd like to edit build.prop or gps.conf).
Sorry for the noob question
Thanks all
NO GPS
I'm not able to get GPS to Work no matter what Nand Rom I Use, I edited my GPS.conf with the us.pool.ntp.org still not locking on SATs
thesniffer said:
Hi all actually i'm running DFT NAND ROM and i'm just wondering how can i modify the system files as they are read only (for istance i'd like to edit build.prop or gps.conf).
Sorry for the noob question
Thanks all
Click to expand...
Click to collapse
You need to get root explorer. Google it for the apk. Then set your permissions to read/write in the app. Then you can easily modify those files.
Ok - other question, is there a way to modify or replace the file
/proc/calibration
I can replace the same file in two other locations (/system/etc and /etc) but not the one mentioned above. I tried with root explorer and adb - no success.
If not, i'll live with the generic mac-address
EDIT: i also tried a modified batch from mdj (I updated my kernel today with this one).
I was curious if anyone else had either tried or thought to edit some of the build prop settings. I'm at work now and probably wont get the opportunity till tomorrow but i was going to try the settings from this thread.
http://forum.xda-developers.com/showthread.php?t=1246748&
Thoughts?
nemoshotyany said:
I was curious if anyone else had either tried or thought to edit some of the build prop settings. I'm at work now and probably wont get the opportunity till tomorrow but i was going to try the settings from this thread.
http://forum.xda-developers.com/showthread.php?t=1246748&
Thoughts?
Click to expand...
Click to collapse
I just tried the following and my phone is super fast now. I can't believe the difference
For those wanting some tweaks:
The following mod adds the following:
GPU 2D acceleration
lower wifi scanning intervals (to save battery)
enable home to cache to memory to improve touchwiz experience
remove delay after ending calls
jpeg quality to 100%
reduce dialing out delay.
Copy to the bottom of your own build.prop using root explorer (there are no line redundancies)
Code:
#tweaks
debug.sf.hw=1
ro.HOME_APP_ADJ=1
wifi.supplicant_scan_interval=180
ro.media.enc.jpeg.quality=100
ro.telephony.call_ring.delay=0
ro.lge.proximity.delay=25
mot.proximity.delay=25
I tried editing this in rootexplorer. I can save it, but after a reboot it reverts back to the original build.prop. Does anyone know what's going on?
I have UBKK2 stock with chainfire root.
hp79 said:
I tried editing this in rootexplorer. I can save it, but after a reboot it reverts back to the original build.prop. Does anyone know what's going on?
I have UBKK2 stock with chainfire root.
Click to expand...
Click to collapse
before editing change your system folder to R/W !
friedje said:
before editing change your system folder to R/W !
Click to expand...
Click to collapse
I already did that. I know there is a button to change from readonly to readwrite. Otherwise, how would I have edited the file in the first place?
Again, I finished the edit, confirmed it's been saved. But after a reboot, the changes are gone and it has a November date for the file. I thought maybe it has to do something with the cf-root.
Any other thoughts?
hp79 said:
I already did that. I know there is a button to change from readonly to readwrite. Otherwise, how would I have edited the file in the first place?
Again, I finished the edit, confirmed it's been saved. But after a reboot, the changes are gone and it has a November date for the file. I thought maybe it has to do something with the cf-root.
Any other thoughts?
Click to expand...
Click to collapse
Did you remember to change it back to read only afterwards?
hp79 said:
Again, I finished the edit, confirmed it's been saved. But after a reboot, the changes are gone and it has a November date for the file. I thought maybe it has to do something with the cf-root.
Click to expand...
Click to collapse
Have you assigned correct file permissions after editing? Most of the files change their permissions in the editing process, and are not recognized by the system after reboot.
Hi. Maybe I can download 4.0.2.A.0.69 but I need to change default.prop.
I edit it and put 4.0.2.A.0.69 but when I restart the phone it´s restored automaticly to 4.0.2.A.0.62 . So can anybody help me?
No problem with the edit of build.prop.
Thanks!
Can I ask why you are wanting to change it to .69? To change you need to change to lines.
ro.build.id:
ro.build.display.id:
So long as you have changed those two lines that should explain.
Regards
Blackwatch
Sent from my Nexus S using xda premium
jlmcr87 said:
Hi. Maybe I can download 4.0.2.A.0.69 but I need to change default.prop.
I edit it and put 4.0.2.A.0.69 but when I restart the phone it´s restored automaticly to 4.0.2.A.0.62 . So can anybody help me?
No problem with the edit of build.prop.
Thanks!
Click to expand...
Click to collapse
default.prop is within the ramdisk and is not permanently editable. To change it permanently, you need to split the ramdisk out of the boot.img. Then you can amend it and remake the boot image.
I do this regularly to make the kernel insecure (so ADB can be used later for easy ROM amends).
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
I just installed my Hero's stock rom.. Android 1.5 with the first version of sense..
I did this with the sole purpose of seeing how it actually ran back then, compared to all the custom roms thats out there.. And i actually think it runs damn well! Its very snappy and it does have the functionality i need.. But most of the apps i use does not support Android 1.5 anymore which is a problem for me..
Is there any way you can "fake" that the android version you are running is maybe 2.1 ? So that i can download the apps i need, or would that not work? I remember that when i had a Tattoo i could fake the resolution of the display, so that more apps would show, and it worked fine actually.
You can try Change model!
If i remember correctly I've a solution:
You need root privileges (and I think you've =)) and a file manager as ES File Explorer.
In ES go to Setting -> Root Option -> Explore as Root and Mount File Sistem
In system folder find and open file build.prop, make a backup and edit the original
Setting, for example:
ro.product model=Nexus S
ro.product manufacturer= Samsung
Save and now you can install all apps...
I don't think it's that simple. Try this:
Reference: http://developer.android.com/guide/appendix/api-levels.html
Tool: http://code.google.com/p/android-apktool/
1 - Put the apk you want to change in the apktool folder and open cmdline.
2 - Run: apktool decode name.apk
3 - Use notepad to edit the AndroidManifest.xml and change the value for 'minSdkVersion':
<uses-sdk android:minSdkVersion="3" /> (3 or whatever version of Android you want your app to be compatible with.)
4 - Build a new apk. eg. apktool b C:\apktool\name name2.apk
Even if the apk installs; some or all features of the app may not work. Also, you will probably need to change the 'AndroidManifest' of any new version or update.
The other option is to find older versions of the app.