Sorry to ask this, but i was wondering why built.prop restored to it's original state when rebooting phone? i was going to edit built.prop to make some tweak...
But after reboot, built.prop look like untouched...
Using rootexplorer edit, Flash tool.
same result
ROM:Fd experience 2.0.0 rev3
Single built.prop in /system only
CKKnot said:
Sorry to ask this, but i was wondering why built.prop restored to it's original state when rebooting phone? i was going to edit built.prop to make some tweak...
But after reboot, built.prop look like untouched...
Using rootexplorer edit, Flash tool.
same result
ROM:Fd experience 2.0.0 rev3
Single built.prop in /system only
Click to expand...
Click to collapse
That problem I have but I searched theat build and find in system/bin/build and editet that and other in /system I don't know how is on Fd experience but on gingerxperia is
You have to edit both files in system/build.prop and system/bin/build.prop to make changes permanent.
And I think this applies on all ROMs.
Yes, must change /system/built.prop and /system/bin/built.prop to make a changes permanent for my rom it's /system/built.prop and /system/bin/built thanks
Related
Is there any possibility of modding /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq without modding the kernel?
Just in case you don't know, cpuinfo_max_freq is the file that limits the maximum processor speed to 1000mhz.
cpuinfo_min_freq is the one that limits the minimum processor speed to 100mhz (i've no interest in modding that file).
I know i can acquire this with a custom kernel or by modding one myself, but i'd like to know if there's any way of doing this other than with a custom kernel.
Tried using root explorer and change permissions to write too apart from read and then modding, without success.
Tried changing permissions using root explorer and then using an init.d script
Tried a few more things, but so far none have worked.
Thanks
You did everything correct but one thing more open root explorer.
# Go to desire file (make sure you have it on rw)
# Now press and hold the file
# a menu will popup
# go to open in text editor and you can edit it
Enjoy
i have just tried it.. normally when i change any system file with text editor, i click on "save&exit" and it says it is saved and the original file is named as xxxxxxx.bak..
but this time there is no .bak file and the original file is not changing.. i write 1200000 but when i try to open it again it turns back into 1000000 ...
kkube said:
You did everything correct but one thing more open root explorer.
# Go to desire file (make sure you have it on rw)
# Now press and hold the file
# a menu will popup
# go to open in text editor and you can edit it
Enjoy
Click to expand...
Click to collapse
Tried that too. Root explorer says it's modded it but if you open it again, no change has been applied
Apparently, it's read only even after changing permissions.
or that file is modified by something else all the time.. obviously we have to change something else before that..
_delice_doluca_ said:
or that file is modified by something else all the time.. obviously we have to change something else before that..
Click to expand...
Click to collapse
The kernel. Just wanted to find out if there was another way, it'd be much simpler than modding a kernel. It seems there isn't
Just a trial idea, copy that file to as card, then edit it. See if it saved then, then rename old one as xxxx.bak and paste the edited file there.
I can't do it as I am on a custom kernal and i am able to change it as I said.
Check it out and tell if that's any help
Sent from my GT-I9000 using XDA Premium App
coldflid said:
Is there any possibility of modding /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq without modding the kernel?
Just in case you don't know, cpuinfo_max_freq is the file that limits the maximum processor speed to 1000mhz.
cpuinfo_min_freq is the one that limits the minimum processor speed to 100mhz (i've no interest in modding that file).
I know i can acquire this with a custom kernel or by modding one myself, but i'd like to know if there's any way of doing this other than with a custom kernel.
Tried using root explorer and change permissions to write too apart from read and then modding, without success.
Tried changing permissions using root explorer and then using an init.d script
Tried a few more things, but so far none have worked.
Thanks
Click to expand...
Click to collapse
Its impossible, i tried this command on terminal: echo 1800000 > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq it says permission denied (i was su)
Use Tegrak Overclock
Edit System Files
I have the same problem
think you have to edit the init.rc file
I have GingerDX installed on a stock kernel. My ro.product.manufacturer in build.prop says "Sh!tEricsson" and I wanted to change that, cause now I can't install Sony Ericsson Backup&Restore and can't restore a backup where all my contacts are saved.
Anyway, it looks like the changes I make do not save. I've followed all steps in tutorials - mounted /system as R/W in Root Explorer, changed permissions to 'write' for group and others before making changes (and changed back after saving). I press 'Save' or 'Save and Exit' and it's all fine. Then I change the /system back to R/O. I can reopen build.prop it in any other file editor and the change is still there, but SE B&R still says I don't have a Sony Ericsson product and after a reboot the ro.product.manufacturer line is reverted back to "Sh!tEricsson". I've tried Root Explorer, ES File Explorer, Prop Editor and BuildPropEditor, nothing works. Any ideas?
Check /system/bin. Some roms have a build.prop there that you also have to edit.
Sent from my rooted tomato using xda app
Yes there are 2 build.props..
One in /system and other in /system/bin.
you have to edit them both to change your build.prop successfully...
Thanks for a quick reply guys! I had no idea about the second file. Everything works now, cheers! :highfive:
make a flashable zip
Sent from my X8 using xda app-developers app
Build Prop is not saving
I tried apps to edit Build prop when ever I reboot the device all Build prop stays the same as before after edited
Hi,
I hope this is the write location for my post.
I have a HTC ONE rooted, android 4.3
I have a problem with my GPS: it doesn't lock any satellite. Reading on forum, I found that the problem may be the setting of gps.conf file in /system/etc.
In fact, checking it, I found that the NTP_SERVER set was for north.america, while I'm in Europe.
I would like to modify or replace it, but I'm experiencing some problem. Using Root Browser it seems to be able to modify it, but after rebooting the device it is exactly the same before the editing. I tried using other editors as ES File Explorer, but when I try to modify the file, it says "read only file system".
It makes me thing that also the other editor is not able to modify the file, since after reboot it is actually un-edited.
What do you think? how can I actually write in file system and actually modify gps.conf?
Thank you in advance
Let me add another detail: I tried to create a new empty file in the same folder with Root Browser. It seems to be able to create it, but after rebooting the device it desappears..so I guess I actually can't modify/write in the file system..
aerosmike said:
Hi,
I hope this is the write location for my post.
I have a HTC ONE rooted, android 4.3
I have a problem with my GPS: it doesn't lock any satellite. Reading on forum, I found that the problem may be the setting of gps.conf file in /system/etc.
In fact, checking it, I found that the NTP_SERVER set was for north.america, while I'm in Europe.
I would like to modify or replace it, but I'm experiencing some problem. Using Root Browser it seems to be able to modify it, but after rebooting the device it is exactly the same before the editing. I tried using other editors as ES File Explorer, but when I try to modify the file, it says "read only file system".
It makes me thing that also the other editor is not able to modify the file, since after reboot it is actually un-edited.
What do you think? how can I actually write in file system and actually modify gps.conf?
Thank you in advance
Let me add another detail: I tried to create a new empty file in the same folder with Root Browser. It seems to be able to create it, but after rebooting the device it desappears..so I guess I actually can't modify/write in the file system..
Click to expand...
Click to collapse
You need an unsecured kernel (/system writable) to write to /system partition of the htc one, not only root.. Otherwise, all changes will be reverted at reboot like you are experiencing.
Kernels for htc one here
And note that modifying/deleting files in /system will probably prevent you to install future ota unless you revert the change you have made. There is a md5 checksum of many files in /system before the ota installs. If the md5 cheksum doesn't match then the ota will not install. This might not apply to the .conf file you want to edit but just in case, make a backup of that file before. So if the next ota fail, you'll know why.
alray said:
You need an unsecured kernel (/system writable) to write to /system partition of the htc one, not only root.. Otherwise, all changes will be reverted at reboot like you are experiencing.
Kernels for htc one here
And note that modifying/deleting files in /system will probably prevent you to install future ota unless you revert the change you have made. There is a md5 checksum of many files in /system before the ota installs. If the md5 cheksum doesn't match then the ota will not install. This might not apply to the .conf file you want to edit but just in case, make a backup of that file before. So if the next ota fail, you'll know why.
Click to expand...
Click to collapse
Thank you very much
After flashing some roms my device changed from xt1063 to xt1068 and i think this is giving me the error when executing updater binary when flashing roms.How can i change it back to 1063?
You can use something like ES Explorer and go to device/system, touch build.prop and open it with ES Note Editor. Scroll down to the line ro.product.model and edit that line to read XT1063.
Sent from my GT-P5210 using Tapatalk
Tel864 said:
You can use something like ES Explorer and go to device/system, touch build.prop and open it with ES Note Editor. Scroll down to the line ro.product.model and edit that line to read XT1063.
Sent from my GT-P5210 using Tapatalk
Click to expand...
Click to collapse
cant find it, i can only find ro.product.name and brand
Flash a recovery for your device.
Or
Add the line in build.prop
or extract your ROM.zip edit update script (meta-inf/google/android/updater-script) and remove the device check lines, re zip and flash
fburgos said:
Flash a recovery for your device.
Or
Add the line in build.prop
or extract your ROM.zip edit update script (meta-inf/google/android/updater-script) and remove the device check lines, re zip and flash
Click to expand...
Click to collapse
didnt work :/
the model name is present on the build.prop file
it ROM must have that file, so if now your devices tink is any other name is just a name does not mean a thing, wen you try to flash other rom that rom will came with its on build.prop and will show the device name that is on that build.prop.
I dont see the problem you are mistaking things.:good:
but if you wanna to change try like other have told you... see pic you can set any name really will not change a ting.
how you can see my dont say XT****, wen i open app that show device model it show exactly what is on build.prop
Just Wipe ur /system/ directory and clean flash a new ROM (cm 12.1) , THis way ur build.prop is going to be wiped (as we are wiping /system ) and get recreated when u flash ur new ROM , Therby resoring the Original Build.prop
Hey Folks!
I'm working on my newest Project called "Fluence HD Patch".
Basicly it will just add the content from my Fluence HD ROM to any excisting/flashed ROM, but now the Problem...
The Content which i add always to my ROMs forces a Bootloop after flashing as Stand alone. Included in a ROM there is no Problem. Changed the Updater Script a lot of times, but no success yet...
Hope anyone can help me!? This **** brakes my Neck!
Thanks in advance!
Did you edit it with something other than Notepad++
Miustone said:
Hey Folks!
I'm working on my newest Project called "Fluence HD Patch".
Basicly it will just add the content from my Fluence HD ROM to any excisting/flashed ROM, but now the Problem...
The Content which i add always to my ROMs forces a Bootloop after flashing as Stand alone. Included in a ROM there is no Problem. Changed the Updater Script a lot of times, but no success yet...
Hope anyone can help me!? This **** brakes my Neck!
Thanks in advance!
Click to expand...
Click to collapse
If experiencing a bootloop, does restoring the original build.prop and setting 0644 permissions through TWRP's File Manager allow the device to fully boot? If yes, then it must be an entry or a permissions issue. My next step in that case would be to flash the Fluence Patch to force the bootloop, boot to TWRP, mount System, set permissions to 0644 for the patched build.prop, and reboot. If the bootloop persists then there is certainly something inside causing it. Is there a single entry added that you didn't incorporate in one of your previous roms?
Also, the only other changes from flashing the patch is a build.prop backup and a tweak.prop on /sdcard, right? The next step in this scenario I would do after experiencing that second bootloop after ensuring the patched build.prop had 0644 permissions would be deleting both of those files that were added to /sdcard through TWRP's File Manager, assuming I had made my own copy of the original build.prop on /sdcard before the very first flash of the patch. If that doesn't allow the device to boot then there is something in the patched build.prop.
Edit*
After reading your Fluence Patch thread it is clear you are talking about the Full Patch causing the bootloop issue and not the one in the thread at the moment. I'll take a look if you want to send me a copy. The META-INF folder and any script(s) used during installation might be enough but not positive. :good:
ronaldheld said:
Did you edit it with something other than Notepad++
Click to expand...
Click to collapse
Nope, I'm using only Notepad++ ? The Zip flashs also successful...
guitardedhero said:
If experiencing a bootloop, does restoring the original build.prop and setting 0644 permissions through TWRP's File Manager allow the device to fully boot? If yes, then it must be an entry or a permissions issue. My next step in that case would be to flash the Fluence Patch to force the bootloop, boot to TWRP, mount System, set permissions to 0644 for the patched build.prop, and reboot. If the bootloop persists then there is certainly something inside causing it. Is there a single entry added that you didn't incorporate in one of your previous roms?
Also, the only other changes from flashing the patch is a build.prop backup and a tweak.prop on /sdcard, right? The next step in this scenario I would do after experiencing that second bootloop after ensuring the patched build.prop had 0644 permissions would be deleting both of those files that were added to /sdcard through TWRP's File Manager, assuming I had made my own copy of the original build.prop on /sdcard before the very first flash of the patch. If that doesn't allow the device to boot then there is something in the patched build.prop.
Edit*
After reading your Fluence Patch thread it is clear you are talking about the Full Patch causing the bootloop issue and not the one in the thread at the moment. I'll take a look if you want to send me a copy. The META-INF folder and any script(s) used during installation might be enough but not positive. :good:
Click to expand...
Click to collapse
Thanks for the Reply Man! As you suggested right in Your edit, the build.prop is just fine for now... I will upload the patch content after waking up completely... Was a hard night ?
Your help is much appreciated! Thanks again! :angel: