Root Cannot move file to system folder

[valorian]

I downloaded a new boot animation. I'm trying to move it to /system/customize/resourses but es file explorer and Astros say file cannot be moved. I was able to move the original file out. Now I can't even move the original back. In ES I made sure the root explorer and mount file system boxes are checked.

Any ideas what I am doing wrong?

 

[bberryhill0]

Try changing the properties of the folder. Check the write permissions.

 

[valorian]

I've been trying that. ES is still saying "file cannot be moved". Even when I try to move the original file back.

 

[bberryhill0]

Hmmm... You have to make /system writable. I don't know how that's done.

* It's in settings in ES.

 

[valorian]

Hmmm... You have to make /system writable. I don't know how that's done.

* It's in settings in ES.

Yeah, I have that box checked. I still cannot move the file.

 

[bberryhill0]

Oh yeah, you said that. I went through and changed the permissions on each directory in the path and got a file to copy into resource.

 

[valorian]

I don't get it. I have all the permissions checked but I still cannot move a file into, only out of this location.

 

[bberryhill0]

ES is still saying "file cannot be moved". Even when I try to move the original file back.

Grasping at straws here: Did you try copy instead of move?

 

[valorian]

Grasping at straws here: Did you try copy instead of move?

Yeah, I tried that.

It's as if I can move or copy anything onto the SD card but nothing can be moved or copied from it.

 

[bberryhill0]

This is going to bug me until we figure it out. The properties of the resource directory looks like this?

 

[valorian]

This is going to bug me until we figure it out. The properties of the resource directory looks like this?

Yes they do.

Thanks you for trying to help. Frustration took over last night and I restored a backup from a couple weeks ago. After restoring the backup I am now able to change the boot animation.

 

[valorian]

Well I know what caused me to have this issue but I do not know the details why.

I was running the Mikrunny Odex ROM with the Red theme. I wanted to give the Coredroid theme a try so I installed the theme and this issue started. After many hours of trying to fix this I restored my backup from a couple weeks ago that has the red theme and all is good again. To reduplicate the issue I reinstalled the Coredroid theme and the issue returned.

Could the Coredroid theme by deodex only? It doesn't state so in the OP.

 

[bberryhill0]

That's weird. How could a theme break the file system? Odd. At least I was challenged to learn more about the file system. Thanks!

* You should post a question in the CoreDroid theme thread.

 

[valorian]

* You should post a question in the CoreDroid theme thread.

Yeah, good suggestion. I'll do that later today.

 

[gg48gg]

I had this issue and solved it my mounting /system as writeable.

In ES File Explorer
Menu->settings->Root Settings
check all of the following:
Root Explorer
Up to Root
Mount File System (as writeable)