Related
Hi,
I'm pretty sure this problem could be common to all rooted devices, so I'm posting it in the general Q&A.
Basically, I would like to experiment with some build.prop tweaks I found around other XDA topics. I'm sure all of you know about the general tweaking of the said file, so I won't get into too much detail about it.
However, the changes just don't stick. They reset to default every time I reboot, as if the build.prop file never changed. So, how do I make them stick?
Phone details:
Phone: Xperia X8
ROM: FroyoPro v2.5
Kernel: Stock (can't unlock the bootloader, unfortunately)
Are you saving before exiting?
XperienceD said:
Are you saving before exiting?
Click to expand...
Click to collapse
Of course! I even double-check if the changes were still there by opening the modified build.prop after the work is done. For the changes I used Root Browser Lite with the Text Editor pre-installed inside. This method does work well, as I used it to modify hw_config parameters related to governors a couple of weeks back.
I've read somewhere that sometimes changes aren't possible if the kernel is stock. Could that be the case here?
If not, are there any other methods I could use to modify build.prop?
xWhiskey said:
Of course! I even double-check if the changes were still there by opening the modified build.prop after the work is done. For the changes I used Root Browser Lite with the Text Editor pre-installed inside. This method does work well, as I used it to modify hw_config parameters related to governors a couple of weeks back.
I've read somewhere that sometimes changes aren't possible if the kernel is stock. Could that be the case here?
If not, are there any other methods I could use to modify build.prop?
Click to expand...
Click to collapse
A quick google caused me to find this thread and I too am having the same problem. I'm currently trying to edit my build.prop to unlock games which say they are incompatible. I'm using ES File Explorer and the built in text editor to edit and save the .prop file, I check if the changes have saved before rebooting my phone but when I turn it back on it has reverted back to stock.
sircrisp said:
A quick google caused me to find this thread and I too am having the same problem. I'm currently trying to edit my build.prop to unlock games which say they are incompatible. I'm using ES File Explorer and the built in text editor to edit and save the .prop file, I check if the changes have saved before rebooting my phone but when I turn it back on it has reverted back to stock.
Click to expand...
Click to collapse
Check if your ROM has a dual build.prop file. If one exists in system/bin, you ought to edit that one for the change to stick. This solved the issue for me, and might solve it for you.
If it isn't there, try using search, and if you find another one somewhere else then try editing that one. A simple matter, but apparently easily missed
xWhiskey said:
Check if your ROM has a dual build.prop file. If one exists in system/bin, you ought to edit that one for the change to stick. This solved the issue for me, and might solve it for you.
If it isn't there, try using search, and if you find another one somewhere else then try editing that one. A simple matter, but apparently easily missed
Click to expand...
Click to collapse
I'm here to wake this thread up, because I'm having this same issue and I can't seem to find any duplicate build.prop file...
Anyone having a good suggestion for me please give it, all assistance is welcome.
Android version 4.4.4
Galaxy Note Edge
Sent from my SM-N915P using Tapatalk 2
me too have the same problem , please some dev or expert help with these problem
You install root explorer and mount as r/w and copy the build.prop into your sd card (the unmoded one) and connect your phone to your pc and turn on usb copy file transfer or something like that. In your pc go into your sd and open your copied build.prop with notepad and mod it as you like. After that go into your root explorer and replace it with your original build.prop. Try on not bricking your phone bcz i bricked mine like that when i put a lot mods on it haha, make a cwm backup or if you know how to unbrick it in every case Hope i helped
Be sure its mounted as r/w otherwise you will not be able to do anything to system files.
Use the original root explorer or Andro Zip is recommeded by me
Sent from my GT-S5830i using XDA Free mobile app
Are you setting the file permissions correctly as rw-r--r-- ??
[/COLOR]
flexton said:
You install root explorer and mount as r/w and copy the build.prop into your sd card (the unmoded one) and connect your phone to your pc and turn on usb copy file transfer or something like that. In your pc go into your sd and open your copied build.prop with notepad and mod it as you like. After that go into your root explorer and replace it with your original build.prop. Try on not bricking your phone bcz i bricked mine like that when i put a lot mods on it haha, make a cwm backup or if you know how to unbrick it in every case Hope i helped
Be sure its mounted as r/w otherwise you will not be able to do anything to system files.
Use the original root explorer or Andro Zip is recommeded by me
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
samsungrockz said:
Are you setting the file permissions correctly as rw-r--r-- ??
Click to expand...
Click to collapse
thank u for answering but sorry guys to say this , it's not the way of editing it , or the permission , when i make changes they are saved correctly and the device apply the changes in the start of the first boot after these changes are made , but during the boot (after applying the changes) the device restore the stock build.prop , so when the device finishes boot up the changes are applyed but the build.prop (i cheked it) is back to stock , this mean another boot & the changes are gone , :crying: :crying: no matter how many times or changes u do they are applyed only for the first boot after they are made
Maybe it has some stock security feed, try to go to custom roms i dont now what else can you do
Sent from my GT-S5830i using XDA Free mobile app
flexton said:
Maybe it has some stock security feed, try to go to custom roms i dont now what else can you do
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
it my first ported rom -porting by replacing files ,not expert work- and i'm having this problem
Kico.MMK said:
it my first ported rom -porting by replacing files ,not expert work- and i'm having this problem
Click to expand...
Click to collapse
Try finding your device on xda and look for a custom rom that someone more expirienced than you if it doesnt work i dont know what will
Sent from my GT-S5830i using XDA Free mobile app
flexton said:
Try finding your device on xda and look for a custom rom that someone more expirienced than you if it doesnt work i dont know what will
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
thanks for the advice , actually i did that but you know there is always something to be fixed :silly:
I have the same issue with my Vodafone Smart Ultra 6. I have root and system has read write access according to ES File Explorer. But any app that has root privileges, writes just fine without errors. However, if I close the app and load it again, or reboot, any changes are lost. So if I remove a system app using a root uninstaller it will say the app has been uninstalled. But it's still there. Drives me insane.
Exactly the same on the Smart Ultra 6.
Was hard enough to get it rooted but seems any changes to the system partition/file system just don't stick. Short of putting a custom rom on it I'm stuck for ideas.
I'd love to know what causes this behaviour.
Any updates here? I just started running into this after updating to the 7.1.1 January factory image on my 5x. The weird thing is when i reboot in TWRP it all looks fine but when I look at my system directory from Android the boot-from-recovery.p is still there and my build.prop changes aren't...push TWRP again, boot to recovery read build.prop and it's my edited version. wtf?
I have found a solution which works in my case.
Edit build prop using any root explorer and save it.
Now once again edit the file with different root explorer app like amaze or es explorer with some comment line like
#comment
and save it.
Now it should prevent the build prop from resetting after a reboot.
I have the same problem: after reboot all the changes are gone....
ashd63 said:
I have found a solution which works in my case.
Edit build prop using any root explorer and save it.
Now once again edit the file with different root explorer app like amaze or es explorer with some comment line like
#comment
and save it.
Now it should prevent the build prop from resetting after a reboot.
Click to expand...
Click to collapse
It's not working for me ☹
---------- Post added at 09:43 AM ---------- Previous post was at 09:30 AM ----------
Is it normal that my build.prop has the permissions -rw------ ?
This could be the problem.
ullie4404 said:
I have the same problem: after reboot all the changes are gone....
It's not working for me ☹
---------- Post added at 09:43 AM ---------- Previous post was at 09:30 AM ----------
Is it normal that my build.prop has the permissions -rw------ ?
This could be the problem.
Click to expand...
Click to collapse
Did you ever find the solution to this? I'm having the same problem..all changes reset with every reboot and the file's permission is like -rw-----
Well I've read a good number of articles online about setting your own ringtone on the Apollo - none of which work on this G3 Modded phone for some reason?
I cannot write a new folder called media on the internal SD card - it will not let me.
I can write a new folder called media on the ext_SD card but it will only allow me to put one folder inside....
No matter what I try, the phone will only look at reading the media folder in the system for the default ringtones...
So, does anybody have any idea how to choose your own ringtone and notification?
gtd2000 said:
Well I've read a good number of articles online about setting your own ringtone on the Apollo - none of which work on this G3 Modded phone for some reason?
I cannot write a new folder called media on the internal SD card - it will not let me.
I can write a new folder called media on the ext_SD card but it will only allow me to put one folder inside....
No matter what I try, the phone will only look at reading the media folder in the system for the default ringtones...
So, does anybody have any idea how to choose your own ringtone and notification?
Click to expand...
Click to collapse
If you have root you can push your ringtones to system/media/audio/rintones (or system/media/audio/notifications for notifications).
zygis10 said:
If you have root you can push your ringtones to system/media/audio/rintones (or system/media/audio/notifications for notifications).
Click to expand...
Click to collapse
I have root access but for whatever reason cannot copy/move any files to system/media/audio/ringtones etc..?
Any ideas?
Perhaps I don't understand "push"..?
gtd2000 said:
I have root access but for whatever reason cannot copy/move any files to system/media/audio/ringtones etc..?
Any ideas?
Perhaps I don't understand "push"..?
Click to expand...
Click to collapse
When I use Astro - I copy or move the file but then once I choose paste I get an error : "Could not write file"
gtd2000 said:
When I use Astro - I copy or move the file but then once I choose paste I get an error : "Could not write file"
Click to expand...
Click to collapse
Try using root explorer, at the top right corner there will be mount R/W button just press it when you will be in system/media/audio/rintones and you should be able to copy. The same with notifications.
zygis10 said:
Try using root explorer, at the top right corner there will be mount R/W button just press it when you will be in system/media/audio/rintones and you should be able to copy. The same with notifications.
Click to expand...
Click to collapse
Well I managed to get Root Browser installed onto the phone - then although I could transfer the files finally, the system wouldn't see them as .mp3 files.
Converted them online to .ogg and the system still couldn't see them...when selecting ringtone etc.
Rebooted phone as a last effort and all is now well :silly:
I'm not so sure why this is so difficult really - it was all very simple on the previous non-Smart phone from ZTE :cyclops:
Thanks for the help
You're welcome
First, you need ROOT access to do this. It will fix the security force-close and enable the uninstall of apps.
1 - Download FIXV2 here - http://d-h.st/gMh
2 - Extract the file to your desktop and copy the files inside "FIRMWARE\IMAGE" folder to your phone.
3 - Download root explorer from play store and move those files to the firmware\image directory located on your phone.
4 - Long press each file and set permition to RW-R-R (0644) (You do this by selecting OWNER to read and write, GROUP to read and OTHERS to read.
5 - Reboot and try accessing settings.
Thanks to ferreinf for the link and how to do it, I just tried to do this as much newbie proof as possible.
have seen this problem in numerous ROM threads(haven't myself run into this), thanks for the heads up :thumbs up:
Sent from my Transformer Prime TF201 using Tapatalk
scorthyn said:
First, you need ROOT access to do this. It will fix the security force-close and enable the uninstall of apps.
1 - Download FIXV2 here - http://d-h.st/gMh
2 - Extract the file to your desktop and copy the files inside "FIRMWARE\IMAGE" folder to your phone.
3 - Download root explorer from play store and move those files to the firmware\image directory located on your phone.
4 - Long press each file and set permition to RW-R-R (0644) (You do this by selecting OWNER to read and write, GROUP to read and OTHERS to read.
5 - Reboot and try accessing settings.
Thanks to ferreinf for the link and how to do it, I just tried to do this as much newbie proof as possible.
Click to expand...
Click to collapse
Hi
Does this help to uninstall system apps as wel instead of deleting apk from system/app folder
Thanks.
smohanv said:
Hi
Does this help to uninstall system apps as wel instead of deleting apk from system/app folder
Thanks.
Click to expand...
Click to collapse
No, it has nothing to do with what you want and there's absolutely no point in doing what wanna do either. You can not reclaim the free space to yourself and that would yet prevent you from installing OTA updates. The best way around this is to unable the system apps you don't wanna run.
Doublepranks said:
No, it has nothing to do with what you want and there's absolutely no point in doing what wanna do either. You can not reclaim the free space to yourself and that would yet prevent you from installing OTA updates. The best way around this is to unable the system apps you don't wanna run.
Click to expand...
Click to collapse
Your description about this patch is confusing...
Read your description,
First, you need ROOT access to do this. It will fix the security force-close and enable the uninstall of apps.
scorthyn said:
First, you need ROOT access to do this. It will fix the security force-close and enable the uninstall of apps.
1 - Download FIXV2 here - http://d-h.st/gMh
2 - Extract the file to your desktop and copy the files inside "FIRMWARE\IMAGE" folder to your phone.
3 - Download root explorer from play store and move those files to the firmware\image directory located on your phone.
4 - Long press each file and set permition to RW-R-R (0644) (You do this by selecting OWNER to read and write, GROUP to read and OTHERS to read.
5 - Reboot and try accessing settings.
Thanks to ferreinf for the link and how to do it, I just tried to do this as much newbie proof as possible.
Click to expand...
Click to collapse
firmware\image directory located on your phone.
Where is this directory on the phone? it does not exist, are we to just push the whole dir w/files to the phone? I agree, need alittle more info here please....
Good work if it does what it says....:good:
TheAxman said:
firmware\image directory located on your phone.
Where is this directory on the phone? it does not exist, are we to just push the whole dir w/files to the phone? I agree, need alittle more info here please....
Good work if it does what it says....:good:
Click to expand...
Click to collapse
Worked for me to get the nexus g+ rom working fully... used root browsed in ROM Toolbox to copy the files to the relevant folder off root, and set all the permissions to rwx.
New VZW HTC one m8. Attempting to get write access to external SD card. Installed weak sauce, then SU, ran the SDFix app.
Everything went well, verified with root check, but still no write access. Inspected the platform.XML file, looked fine, rebooted phone, checked file again, still had the correct entry. Gave up for now, but today I looked at the platform.XML file and it shows an edit date of 4/1/2014. No text at all, file is empty.
Should I try to recreate the file? Everything appears to work as before, but I'm a bit concerned. Anyone have a copy of the file they can post?
Thanks, Paul
Pauls57 said:
New VZW HTC one m8. Attempting to get write access to external SD card. Installed weak sauce, then SU, ran the SDFix app.
Everything went well, verified with root check, but still no write access. Inspected the platform.XML file, looked fine, rebooted phone, checked file again, still had the correct entry. Gave up for now, but today I looked at the platform.XML file and it shows an edit date of 4/1/2014. No text at all, file is empty.
Should I try to recreate the file? Everything appears to work as before, but I'm a bit concerned. Anyone have a copy of the file they can post?
Thanks, Paul
Click to expand...
Click to collapse
Same problem.
Can somebody post the platform.xml file please?
My platform.xml
I uploaded this a little while back, it's my platform.xml. This is from when I was running SkyFall 1.1 or 1.2 (I can't remember exactly ) this particular file also includes the fixes for external sd card write. I don't know if the ROM or version make a damn difference, just including the info for disclosure's sake.
Link: https://www.dropbox.com/s/nmz9tiyjljbeypi/platform.xml
Oddly, I found the original file and copied to the phone, when I did this the phone spontaneously rebooted and all was well. Apparently, unless you have root and the insecure kernel, this happens as part of the new kitkat write protections. If you want to write to the ext sd card, first root, then install an insecure kernel, then make your edit. Restart, and then it works.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Hello,
I have a metronome app which uses .wav files which are stored in a subdirectory of /data/data/[app name]. Android 6.0.1, Oneplus 3.
Now I wanted to modify these wav files with Wavelab and put them back into place (via ES File Explorer in root mode).
That worked, BUT the owner of the files is now "root", and the app won't play the files anymore.
How can I either reset the file owner or prevent the ownership from changing??
Does no one answer because this problem isn't solvable?
Or is it because my question unmasks me as noobish??
Why not copy the wav files to sdcard then modify it?
Sent by a Cool Guy using XDA-Developers mobile app
Hahaha, you obviously don't understand what my problem is (although I think I described it clearly). It's no problem to copy the files elsewhere and modify them; it's when I copy them back into the original directory via root explorer that the file owner gets changed to "root" which makes them inaccessible to the metronome app.
hasenbein1966 said:
Hahaha, you obviously don't understand what my problem is (although I think I described it clearly). It's no problem to copy the files elsewhere and modify them; it's when I copy them back into the original directory via root explorer that the file owner gets changed to "root" which makes them inaccessible to the metronome app.
Click to expand...
Click to collapse
i think you can't do anything about it since its in "/data"
What about manually changing the owner back to the correct value after copying?
No, that isn't possible. Only owner selectable is "root".
hasenbein1966 said:
No, that isn't possible. Only owner selectable is "root".
Click to expand...
Click to collapse
Then the limit is in your file manager or root app, just change them
Sent from my Samsung GT-S5830i using XDA Labs