Related
I've read a couple boot animation threads so far, I have a bootanimation.zip file I want to try out. For whatever reason I cannot understand how I am supposed to get it on my phone. My eris is rooted but I'm not sure what next. Do I need adb? can I run these .bat files floating around here from my sd card? For some reason I can't wrap my head around this and it is frustrating, can anyone clarify what a rooted user needs to have/ what commands to run?
Thanks
The easiest way would be to download EStrongs File Manager from the Market. Put the boot animation on your SD card, then open EStrongs and move the zip into the /System/Media folder. Make sure you only have 1 boot animation in the there. Enjoy.
es0tericcha0s said:
The easiest way would be to download EStrongs File Manager from the Market. Put the boot animation on your SD card, then open EStrongs and move the zip into the /System/Media folder. Make sure you only have 1 boot animation in the there. Enjoy.
Click to expand...
Click to collapse
This does not work. It is not possible to copy from the sd card and put a file in my system folder
**edit, I see I needed to give estrong SU permissions. I got it to work just fine. Thank you.
Glad you got it to work, and you're welcome.
shatterpoints said:
This does not work. It is not possible to copy from the sd card and put a file in my system folder
**edit, I see I needed to give estrong SU permissions. I got it to work just fine. Thank you.
Click to expand...
Click to collapse
or u can use terminal emulator
su (enter)(to get root permisions)
cp /sdcard/(wherever your bootanimation.zip is) /data/local (enter)
reboot (enter)
shatterpoints said:
It is not possible to copy from the sd card and put a file in my system folder
Click to expand...
Click to collapse
You were so sure of yourself though! LOL
Bit of a noob to all this, so work with me please...... I'm trying to replace the Cyanogemod boot animation that came with CELB froyo 2.6 rom. I have a new bootanimation.zip copied to my SD card. I'm using ES File Explorer with SU permissions and it wouldn't let me copy new zip file to: /system/media. Says copy failed. If I try to delete the bootanimation.zip in /system/media, it says file can't be deleted.
So then I went to my terminal emulator and typed:
su (enter)
cp /sdcard/bootanimation.zip /data/local (enter)
reboot (enter)
And now I have not boot animation at all. It shows the bootscreen (3 skateboarding droids) then black screen, then lock screen
Where did I go wrong??
Update: removed bootanimation.zip and there was also a bootscreen.zip from /data/local. REbooted and cyanogemod boot screen came back.
I retried the terminal emulator and it worked!
junk74 said:
Bit of a noob to all this, so work with me please...... I'm trying to replace the Cyanogemod boot animation that came with CELB froyo 2.6 rom. I have a new bootanimation.zip copied to my SD card. I'm using ES File Explorer with SU permissions and it wouldn't let me copy new zip file to: /system/media. Says copy failed. If I try to delete the bootanimation.zip in /system/media, it says file can't be deleted.
So then I went to my terminal emulator and typed:
su (enter)
cp /sdcard/bootanimation.zip /data/local (enter)
reboot (enter)
And now I have not boot animation at all. It shows the bootscreen (3 skateboarding droids) then black screen, then lock screen
Where did I go wrong??
Update: removed bootanimation.zip and there was also a bootscreen.zip from /data/local. REbooted and cyanogemod boot screen came back.
I retried the terminal emulator and it worked!
Click to expand...
Click to collapse
Just an fyi Sometimes you need to re assign SU permissions to estrongs. Just uncheck and then check the mount syst directory as writeable and it will work. Its kinda like re shareing a folder in windows. Sometimes shares drop for no reason or just need to be re shared.
ps. I dont like using the terminal but thanks for the simple commands, I've seen way to many different ways to change the animation. The above cmd's are simple and easy.
Using Nook Color, CM7 nighly 107.
Got Netflix working a while back by modifying the build.prop file using ES File Explorer - no issues.
Tried again to make some mods and cannot save it anymore. ES reports "writable - NO"
Tried to "su chmod 666" it and it comes back with "File system read-only"
Is anybody else seeing this? What am I missing?
Thanks...
I encountered a similar situation during the build.prop edit while using ES File Explorer on my NC running CM7 on internal memory.
Possibly, the permissions in the program need to be changed to enable it to "write".
Here's what I did: Menu==>Settings==>Root options. "Check" Root Explorer and if my memory serves me correctly, click "Yes" to get past the "Experimental Feature", toggle the "Cyanogen Mod" (if you're using CM7) radio button, click OK and check the "Mount File System" box to make the system writable.
Now, it should be writable. Hope this helps.
dhyamato said:
... check the "Mount File System" box to make the system writable.
Click to expand...
Click to collapse
Thanks for the tip, that wasn't it
I remember setting those originally. I just checked again and "Root Explorer" and "Mount FIle System" are both checked.
mwilli20 said:
Using Nook Color, CM7 nighly 107.
Got Netflix working a while back by modifying the build.prop file using ES File Explorer - no issues.
Tried again to make some mods and cannot save it anymore. ES reports "writable - NO"
Tried to "su chmod 666" it and it comes back with "File system read-only"
Is anybody else seeing this? What am I missing?
Thanks...
Click to expand...
Click to collapse
In 106 SU wasn't working correctly until I reinstalled it. You can't modify build.prop without superuser rights. Check the thread about SU / Superuser missing in 106 (and I bet 107) for instructions. It worked for me.
DiDGR8 said:
Check the thread about SU / Superuser missing in 106 (and I bet 107) for instructions. It worked for me.
Click to expand...
Click to collapse
Interesting... the OP withdrew his post: (apparently it's back in 107)
http://forum.xda-developers.com/showthread.php?t=1131369
However when I checked it, the SU app was misbehaving, Force closing, refusing to respond to the menu command. So I reinstalled it. Now it's OK.
Unfortunately I still cannot edit the build.prop file.
I don't think it's a superuser problem because without SU access ES cannot even see the system folder!!! I can see it, and edit the file, just cannot save it.
You might try fixing permissions under recovery.
have you tried the app: nook netflix fixer?
I've changed it successfully on the past 6 consecutive nightlies using adbwireless pull/push. However since 106 I've hsd to reflash su. N108 hasn't given me the su issue. Is it fixed?
Same problem with the build.prop file: cannot save changes, or copy over it. Running in nightly 108 today. Tried both Root Explorer and ES File manager.
I think you need to change the build.prop file properties to be rw using chmod. Don't forget to mount system as rw before doing the chmod.
Sent from my Huawei Ascend using XDA App
foltz61 said:
I think you need to change the build.prop file properties to be rw using chmod.
Click to expand...
Click to collapse
Tried that (sudo chmod 666...), get the same message. "file system is read-only"
backup and restore fresh start....?
I'm not great at linux but I do it differently. Try chmod +rw /system/build.prop . Make sure you have system mounted as RW first. I'd also check superuser to make sure whatever terminal/file explorer you are using still has root privileges.
Sent from my Huawei-M860 using XDA App
foltz61 said:
Try chmod +rw /system/build.prop
Click to expand...
Click to collapse
666 is the same thing as +rw in this case...
It looks like the "fresh start" suggestion a couple of posts up is the best
All those numbers always confuse me . Sorry. Good luck.
Sent from my Huawei-M860 using XDA App
bike2002 said:
have you tried the app: nook netflix fixer?
Click to expand...
Click to collapse
Thanks! That did it!
Does anybody know why this app can modify the build.prop file while ES File Explorer cannot?
I had to mount the folder containing build.prop with rw access in order to use chmod. I think the latest version of the netflix fixer may do the same (see my post in that thread). In short, I used;
Code:
su
busybox mount -0 rw,remount /dev/block/mmcblk1p3 /system
in the terminal before using the chmod command in order to give myself rw permissions in the folder. I'm only two days old at this, so it beats me why root doesn't have normal rw permissions on the folder.
NCKevo said:
I had to mount the folder containing build.prop with rw access in order to use chmod...
Click to expand...
Click to collapse
Thanks for the tip. I ran the command successfully (by the way, small typo, I believe it's -o not -0) and was able to chmod and edit the file with vi.
That's where confusion began. I reboot and after the reboot I was able to modify the file without remounting the /system directory. The mount command does not surive a reboot does it?
Have you tried just pulling the build.prop
Code:
c:/<target_folder> adb pull /system/build.prop
then editing it with note pad then pushing it back and rebooting>
mwilli20 said:
That's where confusion began. I reboot and after the reboot I was able to modify the file without remounting the /system directory. The mount command does not surive a reboot does it?
Click to expand...
Click to collapse
That is confusing. What are the full (i.e. ls -l) permissions on the file now? (It's possible that it somehow ended up with o+w, but I don't understand how - vi isn't exactly known for changing permissions on-the-fly.)
Rodney
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
the first method worked great for me
thanks
Dassen said:
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
Click to expand...
Click to collapse
I tried both without success.. What explorer are you using? I tried with ES and got an error "the operation failed".. and I couldnt change permissions neither
thanks for any help
Are you rooted?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
blazeplacid said:
Are you rooted?
Click to expand...
Click to collapse
I supposed to. I rooted my device to install google play.. but I dont know if I continue been root.. I checked my permissions on system\app and I only have readable..
Could you explain me how to check if I am root, and if not, how to be root again to apply your process?
Thanks for your help
karacc said:
I supposed to. I rooted my device to install google play.. but I dont know if I continue been root.. I checked my permissions on system\app and I only have readable..
Could you explain me how to check if I am root, and if not, how to be root again to apply your process?
Thanks for your help
Click to expand...
Click to collapse
You go to the setting of ES,then at the bottom of setting menu, it has Root setting. Go there and checked all check boxes. If you can, that's mean your KF is rooted.
Sent from my KFTT using xda app-developers app
tried method 1 and it worked right away :good:
Worked
Method 1 worked for me.
Thanks.
Dassen said:
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
Click to expand...
Click to collapse
Worked for me, too. Was surprised about the beautiful wallpapers to see now everytime i turn the thingy on
Adding a Boot Animation
Thanks for this info. I used the 2nd method and it worked immediately. Are there Boot Animations for the KFHD? Or can Boot Animations from, say my LG ICS Spectrum work?
Dassen said:
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
Click to expand...
Click to collapse
Awesome, confirmed working on kindle fire 2 running 10.2.1
frieked said:
Awesome, confirmed working on kindle fire 2 running 10.2.1
Click to expand...
Click to collapse
Thanks a lot for this :highfive:
Confirmed works on KF 8.9, thanks OP! I renamed to dtcp_apk.ads
finally, those horrific ad screens are gone! thank you sir!
if you have adb available, you should be able to do this without a root explorer.
use one of the following codes:
adb shell
su
mount -o remount,rw /system
mv /system/app/dtcp_apk.apk /system/app/dtcp_apk.apk.bak
exit
exit
adb shell
su
mount -o remount,rw /system
chmod 000 /system/app/dtcp_apk.apk
exit
exit
adb shell
su
mount -o remount,rw /system
rm /system/app/dtcp_apk.apk
exit
exit
The first one will rename it. The second one will clear its permissions. The third one will remove it completely.
It should go without saying, but its not my fault if you screw something up, or if it is necessary to have this apk in your system, and you use the third method. I haven't tried it, but it should work. I do know what the commands do.
Didn't also work for me with es file explorer the first time i've tried it, although i've enabled all root options.
Rebooting the device helped me, but it's also important to make sure that you give the explorer the permission to change system data
Sent from my KFTT using XDA Premium HD app
Method 1 working
I tried it just out of curiosity and it worked right away. Using ES explorer, BTW.
Thanks!
Dassen said:
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
Click to expand...
Click to collapse
Thank you so much!!! Method 1 worked great. Also renamed the odex file to .odex.bat through root explorer. Note, in root explorer you will probably have to push the little 'Mount R/W" button once you get into system/app
Sweet. $15 saved.
Thanks for the quick 'how to'.
I have a T-Mobile HTC M7 converted to GPE, recently flashed to Lollipop from KK 4.4.4. I use Tasker and OpenRecoveryScript to automate Nandroid backups through TWRP, then use FolderSync to upload said backup to my server over WiFi. My method worked perfectly until I flashed to Lollipop.
Since flashing to Lollipop, whether through Tasker or manually, I get an error in FolderSync saying the Nandroid files can't be read or copied. If I use TWRP's file manager, I can view the Nandroid folders/files, but those same files are not viewable using ES File Explorer in Lollipop. When I navigate to TWRP\BACKUPS\{Serial Number} folder in ES File Explorer, the {Serial Number} folder (where the TWRP backups are) is listed as a 0k(zero) file that can't be read or copied. When I try to create a new folder (in the BACKUPS folder) using ES File Explorer I get an error saying the operation failed.
Just this morning I restored a Nandroid backup using TWRP, and now in ES File Explorer my entire SDcard folder is blank (not true, as all my apps still function), but in TWRP file manager the SDcard folder is fine. At first I thought the problem was with ES File Explorer, but I tried a few different file explorers with the same result (FX File Explorer tells me 'Access was Denied' when trying to view the sdcard folder. ) All file managers I've tried have root access.
I thought Lollipop fixed the sdcard problems from KK, but this is a whole new one for me. Is there an issue with Lollipop not being able to read files that are written through recovery/TWRP? Any help would be greatly appreciated.
In a terminal app type
Su
restorecon -FR /data/media/0
Ajxx16 said:
In a terminal app type
Su
restorecon -FR /data/media/0
Click to expand...
Click to collapse
Thanks for the help Ajxx16. Tried your suggestion and get: tmp-mksh: restorecon: not found
You have root correct?
Ajxx16 said:
You have root correct?
Click to expand...
Click to collapse
Yes. Rooted running SuperSu 2.37 and TWRP 2.8.1.0. I also tried applying the restorecon patch through TWRP's terminal. It seems like it did something, but again when I boot back into the system, sdcard folder listed as empty. I just flashed a Nandroid backup I had of 4.4.4 and no sdcard issue. I'm going to update back to 5.01 (slowly, monitoring each step) to see if I can troubleshoot when the issue starts again, if at all (which wouldn't bother me if it didn't, really).
So I updated from 4.4.4 and ran into the same issue. It turns out the ROM I was updating from somehow did not have restorecon in the system/bin folder. I was able to find a 5.01 GPE RUU, flashed that, applied restorecon fix, and issue is resolved. Thanks for the help Ajxx16!
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.