I am trying to install a custom boot animation.
It says to put default.xml in system/customize/CID
I tried to do this with a root explorer but it said copy failed and I cant delete the default xml that is already there. Is it because it is being used? How would I do it with the phone off?
I dont understand how.
You could just flash one. Use bootscoot2, there's a thread in development.
jedinegotiator said:
I am trying to install a custom boot animation.
It says to put default.xml in system/customize/CID
I tried to do this with a root explorer but it said copy failed and I cant delete the default xml that is already there. Is it because it is being used? How would I do it with the phone off?
I dont understand how.
Click to expand...
Click to collapse
generally, the system is normally mounted in read only at boot. before making any changes to the system partition you'll need to mount the system in read/write mode. there is an app in the market by a senior xda moderator which helps with mounting the system as read/write called remount.
if, for some reason, you aren't able to modify the file because it is in use, then putting the phone in recovery mode, will be the next best way to access the /system partition with read/write access and not have any of the /system files be in use.
loading update.zip files where people have packaged up modifications in recovery mode, generally work well because recovery mode runs as root and there is the guarantee the recovery mode does not rely on and does not use any /system files.
hope that helps!
Related
I have installed the Deodexed 407 Rom, and installed Streakmod Recovery and also installed superuser.zip, so in theory, from what I have read my streak should now be rooted.
But when I try and edit a file, the build.prop file in /system with Astro File Manager I alter some of the settings and save it, but when I reopen the file the changes had not been saved. I have tried seeing if I can change the permissions on the file, but without success.
I would be grateful if someone could assist me in where I am going wrong, hopefully it is something simple or a wrong setting that I am not quite doing correct.
spanner44 said:
I have installed the Deodexed 407 Rom, and installed Streakmod Recovery and also installed superuser.zip, so in theory, from what I have read my streak should now be rooted.
But when I try and edit a file, the build.prop file in /system with Astro File Manager I alter some of the settings and save it, but when I reopen the file the changes had not been saved. I have tried seeing if I can change the permissions on the file, but without success.
I would be grateful if someone could assist me in where I am going wrong, hopefully it is something simple or a wrong setting that I am not quite doing correct.
Click to expand...
Click to collapse
You have to mount the system as ReadWrite and there was no need for a new thread. You should've posted in the rooting thread
Sorry, for not putting it in the rooting thread, but didn't want to clog a general rooting thread with a specific problem.
I have solved this now thanks, but not with Astro File manager as I still cannot seem to change the permissions with that app, but used advanced tools app instead.
Thanks again anyway.
Yes i had same problem trying do root operations with file expert. I used root file explorer instead. Weird thing being that even with rooting permissions ticked file explorer failed.
For most root-enabled browsers, just enabling root permissions won't give you write access. You'll need to find a second option to mount the /system directory as read/write. That's normally somewhere in the Settings menu or on the directory's long-press menu.
ChicoKiri said:
For most root-enabled browsers, just enabling root permissions won't give you write access. You'll need to find a second option to mount the /system directory as read/write. That's normally somewhere in the Settings menu or on the directory's long-press menu.
Click to expand...
Click to collapse
It's mainly dependant on the kernel, all custom kernels automatically mount system as RW and all stock kernels mount it as RO
At least root explorer tells you that it's read only if you attempt to modify it without remounting, I havnt used ASTRO in a long time so I cant comment on that
Root explorer better for me
Sent from my PC36100 using xda premium
Hey there?
I've got a question which I can't seem to find anywhere else and YES I have searched this forum and google. However, I may miss it.
Anyway, I've mapped my android phone as a network drive using Samba and changed the smb.conf file to show the System Root directory as well. However, system root is default set as R/O so to mange files USING my computer I need to change the permission to R/W using a file manager (such as root explorer). This is annoying, as I have to keep doing this in order to write to certail directories.
What I wish to do is create a massive guide on all of this to help out the community, however I need one little bit of information.
I would like the / directory (root) to be mounted as R/W as default so that I can quickly edit files on my PC without having to constantly change it to R/O.
If this has been answered before, I do apologize.
Thanks in advance.
Regards,
xxSHABSxx
EDIT:
To make things a bit clearer.
I want something that will automatically mount my phone's root dir into rw upon boot, without custom apps/having to manually mount as rw everytime it reboots. And yes I understand there are apps that do this.
Yes, the root file system is read-only, but it's also volatile. It's restored from the initramfs in the boot image each time you reboot the phone, so only mounting it writeable, doesn't do you very much anyway.
In /init.rc you find a line:
Code:
mount rootfs rootfs / ro remount
This remounts your root read-only. Remove this, and it'll stay writeable. But again, all edits to the root file system are volatile. To change this, you must flash a new boot.img
An easier way would be a root-app remounting it writable again after boot.
kuisma said:
Yes, the root file system is read-only, but it's also volatile. It's restored from the initramfs in the boot image each time you reboot the phone, so only mounting it writeable, doesn't do you very much anyway.
In /init.rc you find a line:
Code:
mount rootfs rootfs / ro remount
This remounts your root read-only. Remove this, and it's stay writeable. But again, all edits to the root file system are volatile. To change this, you must flash a new boot.img
An easier way would be a root-app remounting it writable again after boot.
Click to expand...
Click to collapse
Ahh I figured as much, since Google didn't offer any solutions to me. And flashing is way much more effort than simply having an app that does it for you.
Anyway thanks for the reply!
xxshabsxx said:
Ahh I figured as much, since Google didn't offer any solutions to me. And flashing is way much more effort than simply having an app that does it for you.
Click to expand...
Click to collapse
Or do like I did, move the root to a real ext3 non-volatile file system instead.
Hi all.
I'm trying to copy some files to the system partition after enabling write on read-only partitions and remounting it and everything is success, but when I restart the phone, files get deleted and partition back to original. I tried ES file explore and Total Commander.
Galaxy S2, cMIUI 2.10 JB
Hmm.. seems like a hard question!
Elancore said:
Hi all.
I'm trying to copy some files to the system partition after enabling write on read-only partitions and remounting it and everything is success, but when I restart the phone, files get deleted and partition back to original. I tried ES file explore and Total Commander.
Galaxy S2, cMIUI 2.10 JB
Click to expand...
Click to collapse
Elancore said:
Hmm.. seems like a hard question!
Click to expand...
Click to collapse
Hey,
no not a hard question but a bit confusing
So the copy to system works without probs?
Do u have root-enabled on it?
U can try Solid explorer once, too, to be sure.
CHEERS
I enabled root explorer and I mounted the file system to be writable, yes I have a rooted phone.
I can copy to system root folders anything (media files), the files stay there until I reboot the phone then they disappear, they get deleted maybe? how to disable that?
Thanks
Elancore said:
I enabled root explorer and I mounted the file system to be writable, yes I have a rooted phone.
I can copy to system root folders anything (media files), the files stay there until I reboot the phone then they disappear, they get deleted maybe? how to disable that?
Thanks
Click to expand...
Click to collapse
That listen like u have to save changes?!
Pls try the Solid explorer (for me the best explorer ever)
Copy files and have a look for root-acces request (should be asked for Solid, if it's new)
The copy/replace the file.
CHEERS
Thanks Hannibal for reply, I got no luck on doing it, they still get removed after reboot. Is there a way to flash these files that I want to copy to system as an update.zip?
Elancore said:
Thanks Hannibal for reply, I got no luck on doing it, they still get removed after reboot. Is there a way to flash these files that I want to copy to system as an update.zip?
Click to expand...
Click to collapse
Sure there's a way, but I can't help u with it, sorry.
With new Titanium Backup u can create flashable .zips but for sure only from isntalled apps.
Maybe u have a look at google. I remind for a tool which u just say what u wanna flash an it creates the flashable .zip.
Much success....
CHEERS
Edit: Sorry but couldn't answer u yesterday.
XDA had a prob for a while
Unhappy [Q] Problems with deleting files and replacing sounds
HI all! New use here.
I superuser'd my phone, routed my phone, installed CM11 and all is well. It was my understanding that with apps like RootBrowser and or SuperManager i could browse to files change permissions and delete and remove them or replace them.
I am unable to change my lock sound or boot animation.
Ive granted the permissions to the apps and am operating the root browsers in Root mode. (sorry if my terminology is wrong but im new to this) When i try to replace the files in system/media or system/media/audio/ui they simply dont work, "operation failed". I am able to change the permissions on the replacement files going into these directories to match those im overwriting but its still fails.
Ive even successfully deleted the default lock sound but when i paste the new one into the folder it fails and says stuff like "out of space" or "no room" and then when i shut app and go back in the original file is back!
Can anyone help with this as my lovely rooted phone is being very difficult.
Your partition is mounted as read-only, that`s why you get "operation failed".
Mount it as read / write and should be ok.
ngl_ro said:
Your partition is mounted as read-only, that`s why you get "operation failed".
Mount it as read / write and should be ok.
Click to expand...
Click to collapse
Thank you. I now know what to do but not how to do it? Are you able to help or link me to a post on how to do that?
Many thanks
ngl_ro said:
Your partition is mounted as read-only, that`s why you get "operation failed".
Mount it as read / write and should be ok.
Click to expand...
Click to collapse
When i use the app SuperManager to browse the file system to "system" folder it asks me "If you want to modify the file in teh system, you have to mount the system image first. Please choose access mode: System IMage: R/O"
then
"Do nothing Read only R/W" so i chose R/W but that does not fix the problem?
My errors i get are "not enough free space" well there is plenty of that!
So confused....
Any thoughts
Just ignore the "not enough free space".
Cant help you with RootBrowser or SuperManager because I never used them. I use ES File Explorer, and mounting partitions with it always solved my problems with not being able to delete / modify system files / apps.
Hi all,
I am trying to edit a file on /system (/system/etc/init/hw/init.rc), to allow my powered off phone to be turned on when plugged into a power source.
I have successfully gained root, however, /system is unable to be mounted as read/write. I have attempted this many ways such as re-mounting /system via FX File Explorer and root explorer or trying to remount via terminal, but I receive the error that /system can not be mounted as Read/Write.
I attempted to edit the file via TWRP file editor, and was able to successfully save, but the file reverts itself when the phone is booted. Strangely , the "HW" directory when booted into android has several *.rc files, however when viewing the directory in TWRP the only file seen is the init.rc, which differs in content than the booted version. This makes me think boot.img is writing these files each time the phone boots.
I have edited this file successfully on the 6T, which allows you to mount /system in R/W mode.
Any advice on how to edit the file, or another workaround to allow the phone to bootup when plugged into a power source?
Thanks!
Turn off secureboot
kwell24 said:
Turn off secureboot
Click to expand...
Click to collapse
Great suggestion, according to Fastboot screen Secure Boot is enabled. I googled around how to disable but the only oneplus specific suggestion was in the security settings, and this option is not listed in the Nord 200. Other suggestions also did not seem to work. Do you know how to turn off Secure Boot?
[TOOL][WIN,LIN,AND,DARW] Super image tools | extract or make partitions RW in super partition
Disclaimer: Super image tools was made for testing and educational purposes, ME is not responsible for what you do on/with your device using our tools, you must agree that you using our tools on your own risk, I am not responsible for anything...
forum.xda-developers.com
Or manually, either way I don't recommend messing with the system. Better trying to achieve it with Magisk systemless-ly
I finally figured out how to edit init.rc to allow automatic powering on when connected to a charger.
Converted T-Mobile phone to stock rom via https://forum.xda-developers.com/t/...thout-msm-tool-credit-to-summersofar.4339037/
Unpack the sys.img from the stock rom using CRB tool https://forum.xda-developers.com/t/tool-windows-kitchen-crb-v3-0-0-beta8b.3947779/
Edit init.rc according to https://forums.oneplus.com/threads/how-to-boot-oneplus-one-when-charger-connected.1170454/
Repack system.img using CRB tool
flash system.img back onto phone
Now my powered off phone will boot up when plugged into a power source! Steps 1 and 2 can probably be reversed so you just flash the edited system.img to the phone.