I've updated my device today to 6.0.1 and rooted, however I can't seem to change the boot animation (yes, I have searched for answers and tried quite a few fixes).
Root Explorer tells me I have renamed the old file and copied the new file, however once I leave the directory and go back the old file is still there.
I have used the file explorer in TWRP and managed to delete the stock boot animation, but get a FAILED message when I try to copy the new file.
I used the terminal in TWRP and tried to copy the file manually, and receive a "No space left on device" message.
I've also tried mounting the /system as rw in adb. I can delete the bootanimation.zip file from there, and df -h shows 3mb free. Shouldn't the system partition have more space available than that?
Am I missing something, or has something changed with the new android versions?
Google has filled the system partition up to the brim. Also you can't remount system as rw while Android is running.
But the direction is right, go to TWRP, mount system, delete the old bootanimation. If the new one is not that much bigger then you could just copy it there, set permissions to rw-r--r--. But if the new animation is significantly bigger, you'll have to delete some bloatware first.
Thanks for that. The odd thing is, when I run DF in the terminal, it shows I have 20mb free. The boot animation file I am trying to copy is 6mb.
I'll keep poking around. If it doesn't work, it doesn't. It's not hugely important
Related
Thank you in advance, this is a great community.
I am running cognition 3.04 and making my first attempt at transparent widgets. However, I am uncertain if I am properly set up to access and reinstall apk files. I can find them on my phone using the file explorer in Andriod Mate. However, it appears that when I plug my phone into the usb or use any other file exploring software, the base directory is /mnt/sdcard/ . I feel that I am missing a critical component of this process, as I do not have ready access to the files I need to alter and eventually replace.
Thank you again,
Dez
Dezdemona said:
Thank you in advance, this is a great community.
I am running cognition 3.04 and making my first attempt at transparent widgets. However, I am uncertain if I am properly set up to access and reinstall apk files. I can find them on my phone using the file explorer in Andriod Mate. However, it appears that when I plug my phone into the usb or use any other file exploring software, the base directory is /mnt/sdcard/ . I feel that I am missing a critical component of this process, as I do not have ready access to the files I need to alter and eventually replace.
Thank you again,
Dez
Click to expand...
Click to collapse
You would need to copy them from ur /system/app folder to some folder on ur sdcard to see them on computer.
Below is the file system layout.
/ (root)
/system
/system/app
/...
/...
/...
/sdcard
/sdcard/...
/sdcard/...
/sdcard/...
/sdcard/external_sd
/sdcard/external_sd/...
/sdcard/external_sd/...
/sdcard/external_sd/...
When u connect to computer, it mounts only the internal and external sd cards. It does not mount the system areas like system, data, etc.
So I just picked up the 7 inch Kindle Fire HD from a buddy of mine and wanted to root the thing right away I tried to do it through command line but when I try to edit anything in the /data/local or the /data folder in general I am met with errors saying no such file, not a directory, permission denied. So I decided to take a look at the actual folder on the kindle with a file explorer and there is nothing in the data folder, it is completely empty. There is no local folder and therefore no tmp folder, what I want to know is there any way for me to get those folders back? I know if I was rooted I could just recreate those, so I tried to use the QemuRoot tool to get rooted but I am unable to boot into fastboot. I don't know if it is due to those folders missing. I tried to boot into fast boot with the adb reboot-bootloader command and it just rebooted the kindle. It's more than likely I did something wrong there. I am quite confused and any help would be appreciated.
I Downloaded a WinRAR file onto my S5 for my computer. It is in my downloads folder on the internal storage of my S5. I have deleted everything out of the folder itself but cannot delete the folder. It annoys me. When I try to delete it I get this dialog box:
"Error deleting folder" Cannot delete WinRAR 5.21 Final(x86-x64) Pre-Activated 100(weird Chinese symbol) an install: The storage is write protected.
Remove the write protection and try again.
I am not stupid...I've tried everything I could think of and cannot remove the write protection or anything. For some reason I think it may be because of the weird Chinese symbol that is after the "Pre-Activated 100"
I cannot rename it, modify it or anything. It is the only file I am having a problem with. Can anybody help me with my OCD?
Is your phone rooted? If yes, you can either use adb or just a terminal emulator app, and delete the cr.p of that file!
Edit: the command you're looking for:
su
cd /mnt/sdcard
rm -r Download
That will remove the Download folder along with all its content. (this is irreversible)
I tried to change the boot animation, running M Preview 3, and despite the fact that the flash claims to have performed successfully, it did not. I'm trying to flash the Marvel boot from the Themes and Apps section, and I know the flashable file worked on 5.1.1. It didn't overwrite the bootanimation.zip in /system/media. At one point, I was able to manually move the file there myselfusing Root Explorer, but I did not realize that the /system partiton did not have enough space to hold the entire zip file, so it was a corrupted zip at that point, and now my boot animation is just "android" in gray lettering. I cleared up enough space to hold the entire zip file of the marvel boot, but now I cannot move the file there, ES File Explorer and Root Explorer simply say it failed to copy.
I just tried to use adb to push the zip file from my computer, but it fails because /system is a read-only file system. So, I tried to remount with a shell as read-write, after some initial issues with apparently /system/xbin/mount not working properly, it did remount as read-write when using /system/bin/mount. But, adb push still fails because /system is a read-only file system.
Code:
mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered 0 0
But, as you can see, it's mounted as read-write.
I, also, just tried to move the file as root in an adb shell, with no luck. A bootanimation.zip shows up in /system/media, but apparently it is corrupt because I cannot open it with root explorer, or in Windows when I pull it. When I try to move the boot animation that I want, the shell reports that there is not sufficient space, which is true now. The bootanimation.zip takes up 40MB of the 55MB of free space in the /system partition. Any time I try to delete the zip, it is automatically recreated before I have a chance to move anything in it's place, even when I do:
Code:
rm /system/media/bootanimation.zip | mv /storage/emulated/0/Download/marvelboot/system/media/bootanimation.zip /system/media/bootanimation.zip
So, what am I missing? Is it even possible to change the boot animation on Android M? Am I doing something wrong, or not doing something I need to?
why flash it? its a boot animation.. extract it from the zip, then pkace the bootanimation.zip into /system/media/ then just reboot. thats all it takes.
edit.. i didnt read ypur whole post and realuze that yoh have other issues.
Yeah, I wish it was just as easy as flashing or moving the zip file to /system/media/... Normally it is, but with Android M there seems to be a problem?
cappiez said:
Yeah, I wish it was just as easy as flashing or moving the zip file to /system/media/... Normally it is, but with Android M there seems to be a problem?
Click to expand...
Click to collapse
no, no problem here. do you have full root? i mean do you have the ability to edit anything in /system/?
Everything seems fine according to root checker. And, if I make small changes to my build.prop (Just editing build.id), the changes stick after a reboot. Soooo.. Yes?
cappiez said:
Everything seems fine according to root checker. And, if I make small changes to my build.prop (Just editing build.id), the changes stick after a reboot. Soooo.. Yes?
Click to expand...
Click to collapse
so you fo have full root. i use root explorer to put animations into /system/meda/, havent had any issues. does that animation work on a n6?
It worked on 5.1.1. Since I moved to the M Preview 3 builds, it appears to have stopped working.
cappiez said:
It worked on 5.1.1. Since I moved to the M Preview 3 builds, it appears to have stopped working.
Click to expand...
Click to collapse
nope. im on m preview 3, and it works fine here.
hi again
I have small problem that I find quite annoying
Xperia SP on android 4.3 (....1.207 rom)
device is rooted with towelroot + SuperSU,
no matter which file manager with root capability I use and go into SYSTEM folder
and either create new folder and delete it, or copy something from SD to system Audio folder
things get broken...
Folder cannot be deleted even if its newly created, and has nothing init
nothing cannot be copied in Audio folder, as everything gets erased by ... system ?
and my annoyance goes to, if its rooted OS, and I as user have "full access"
why are these things happening ?
is there something I need to learn of how android deals with stuff specially ?
As far as i can remember, i haven't faced this issue in my past (was ages since i last used stock ROM). But i can safely say it might be related to your actual file manager. Can you list me the file managers you used?
I would also recommend trying to use Solid Explorer Classic for the sake of testing, and also Fx File manager.
Basically, when you want to do a change in the system directory, the system partition must be remounted as read-write because the folder resides on a different partition. Android by default mounts system partition as read-only on boot. A file manager is responsible to remount the system partition to read-write before performing an operation on the system partition, and i believe this is where the problem occurs - if the files aren't being copied.
If you can copy the folders but unable to delete, this is most likely a permission issue, and the file manager was probably isn't properly using its root rights.
Please respond with your test with Fx or Solid Explorer classic. You may also try Solid Explorer 2.0 if you wish. NOTE: Please enable Full Logging in SuperSU settings. I'd like to see what is going on (you can too).
Also it is worth to know that although root gives you ultimate rights to modify or alter the OS, there are always technical problems which are caused by various reasons. Plus, there are even barriers of which root power can't even do. For an ultra simple comparison, you can't use root to somewhat modify an app's source code live. But of course, root gives much more freedom to do things compared to no root.
ah yes, you were right, it did depend on file manager after all
tho for unknown reasons 5 of 6 all needed supersu acceess and had root capability, but nothing to operate
I finally found (blue) root explorer, and this one can do it all, sorry for opening this thread
I jumped bit late with whole android thing