I am trying to create a new file name "scaling_available_frequencies" in /sys/devices/system/cpu/cpu0/
I tried with
adb remount
adb push scaling_available_frequencies /sys/devices/system/cpu/cpu0/scaling_available_frequencies
not working say no such file
I tried too to create the file from root explorer and it sayse created but doesnt appear
What can I do?
I'm unsure, but i don't think you can create files there, as those objects there are not really files, but input/output ports for the specific devices.
To add another input/output port there called "scaling_available_frequencies" you will probably have to edit the kernel.
Someone correct me if i am wrong please.
/sys is not writable by anything but the kernel
The kernel publishes compile options and runtime values through /sys. It would be a security risk if anything else could modify /sys.
/sys is not persistant and is not really a filesystem in a traditional sense, but a read only database accessed by filesystem methods
If you don't see something you expect then look at you kernel compile options and what modules you may need to load
Different kernels support dfferent features and this is reflected in /sys.
Sent from my SMB-1002-3G using XDA Premium App
I want this..
http://forum.xda-developers.com/showthread.php?t=1010748&highlight=Bios+animation
Where is my boot animation located on my SD card?
Help appreciated!
It is under /system/media/bootanimation.zip
You won't find it on your SDcard. You'll need an app like Root Explorer to access the file system.
You could also use ADB to push the files there if you're familiar with ADB.
dont have that.. i replace the ones in Bamf_Extras.. but it didnt work
Are you familiar with ADB?
honestly, no. I one click rooted. what can I do?
can i push using clockwork recovery?
Runn3rLogic said:
honestly, no. I one click rooted. what can I do?
Click to expand...
Click to collapse
I believe there is a free alternative to Root Explorer in Super Manager. It contains File Explorer (Root). It may allow you to copy the bootanimation.zip and mp3 file into the directory. I also am unsure if it will let you set the correct permissions on the files once they are copied. It may be something you can try.
---------- Post added at 06:41 PM ---------- Previous post was at 06:32 PM ----------
I went ahead and installed Super Manager. It will allow you to do what you need. You'll find the permissions button on the bottom menu bar if you scroll to the right.
You dont need any apps to do it for you, the bootanimation is in system/customize/resource folder you name it the name as the one in the folder and copy over it. Most if not all the developers name it bootanimation.zip the default Verizon is named VZW_bootanimation.zip I have helped people add sound to their boot animations as well this can be edited in the system/customize/CID folder in the file default. Must be edited with notepad++ or wordpad++ its one of those look near the bottom of the file for boot animation. I have become quite good at doing this by breaking it and fixing it. Things like this need to be learned the hard way.
Sent from my Thunderbolt using XDA App
Grnlantern79 said:
You dont need any apps to do it for you, the bootanimation is in system/customize/resource folder you name it the name as the one in the folder and copy over it. Most if not all the developers name it bootanimation.zip the default Verizon is named VZW_bootanimation.zip I have helped people add sound to their boot animations as well this can be edited in the system/customize/CID folder in the file default. Must be edited with notepad++ or wordpad++ its one of those look near the bottom of the file for boot animation. I have become quite good at doing this by breaking it and fixing it. Things like this need to be learned the hard way.
Sent from my Thunderbolt using XDA App
Click to expand...
Click to collapse
The correct file path is for BAMF Forever 1.0.6 is system/media/bootanimation.zip
There is also an audio file that you can replace in the same location.
I edited my CID file so it where I want it to be. I am used to default setting. Also you can copy over audio but you still need to change desc file and CID so it starts with correct animation. Should I roll my eyes back? Plus I never even said anything about BAMF forever....
Sent from my Thunderbolt using XDA App
Grnlantern79 said:
I edited my CID file so it where I want it to be. I am used to default setting. Also you can copy over audio but you still need to change desc file and CID so it starts with correct animation. Should I roll my eyes back? Plus I never even said anything about BAMF forever....
Click to expand...
Click to collapse
I assumed you were attempting to address the original posters questions about changing his boot animation on BAMF Forever 1.0.6. I didn't understand that you were merely randomly posting about how you like to edit this and that. You can roll your eyes back now!
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-----
Hi all,
in the current rom I am using there is one file missing in sys / android_touch (s2w), but in an older version I have the file. Is there a way to copy this file? I have a file manager with root access and tried already, but I was not allowed to copy the file. Any ideas?
TIA
Sent from my HTC Sensation using xda app-developers app
blackfrank said:
Hi all,
in the current rom I am using there is one file missing in sys / android_touch (s2w), but in an older version I have the file. Is there a way to copy this file? I have a file manager with root access and tried already, but I was not allowed to copy the file. Any ideas?
TIA
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
s2w is known as sweep 2 wake it means when you swipe your finger from home to search button you screen will turn on
its related to kernel
IMO you cannot copy system files as they might be different if you want s2w flash a kernel wch supports it
Hi all,
I am working on aosp and have two questions about build.prop.
1) Normally, build.prop file is located to /system directory. I'd like to create custom build.prop file and save it to different directory. For example, I have tvconfig directory and want to create it in here. Could I read properties from /tvconfing/build.prop via SystemProperties?
2) Could I use different name for prop file except build.prop for example mycustom.prop
thanks in advance
batuhanavl said:
Hi all,
I am working on aosp and have two questions about build.prop.
1) Normally, build.prop file is located to /system directory. I'd like to create custom build.prop file and save it to different directory. For example, I have tvconfig directory and want to create it in here. Could I read properties from /tvconfing/build.prop via SystemProperties?
2) Could I use different name for prop file except build.prop for example mycustom.prop
thanks in advance
Click to expand...
Click to collapse
Not sure if it would work, but one idea to try is creating a symlink from the file you want, to the build.prop file. If it works, you could also rename the file. Just an idea? I use this technique for the hosts file myself. see the code in https://forum.xda-developers.com/an...osts-diamondjohn-host-builder-script-t3872728
The next choice would be a magisk module.
I need help with a Custom recovery for Fero Royale LTE
MICHAEL(SMHOS.ORG) said:
You can't really do that but you can make custom Changes or specs to the build.prop,like improve Speed or So, increased or reduced screen size fake android version etc
Click to expand...
Click to collapse
I understand that I can't move build.prop file to different directory except /system directory. Well! Can I do that create mycustom.prop file in different directory and read any property from it via SystemProperties?