I originally posted this over on the forum for the T-Mobile specific version, but there's no reason it wouldn't work on other Note 3's as long as it is rooted and has CWM or TWRP. It is possible to get this to work without a custom recovery (aka w/o flashing) by doing it manually...The phone will still have to be rooted and you will need a file manager capable of root browsing, I prefer ES File Explorer but any would work.
If you would like to reset your boot animation and undo the changes this zip made simply flash the tmo_kk_androidl_bootanim_n900t_reset.zip. It will restore the backups it created and remove the files it installed. I would like to know if you're able to get it work on Note 3's other than the SM-N900T I have.
Enjoy!
EDIT I updated the zip files to the latest version that do not have the error issues. Thanks to @Dan-SRi for pointing out the problem!
- Open the zip file and extract /system/bin/bootanimation and /system/media/bootanimation.zip.
- Put bootanimation into /system/bin/ and bootanimation.zip into /system/media.
- CHMOD /system/bin/bootanimation to 0755 (-rwxr-xr-x).
- Reboot and enjoy!
I whipped up a CWM/TWRP flashable ZIP to enable the Android L boot animation. Flash tmo_kk_androidl_bootanim_n900t.zip if you want to leave your current boot sounds, and flash tmo_kk_androidl_bootanim_n900t_nosound.zip if you want the script to rename the PowerOn.ogg and PowerOff.ogg.
This script will backup the original /system/bin/bootanimation so you can easily revert the changes.
I tested this on my N900T running EffortLess ROM Rev 6 (NF1) w/ Aurora Kernel, though I'm fairly sure it would work on other ROMs/variations.
Enjoy!
If you would like to reset your boot animation and undo the changes this zip made simply flash the tmo_kk_androidl_bootanim_n900t_reset.zip. It will restore the backups it created and remove the files it installed. I would like to know if you're able to get it work on Note 3's other than the SM-N900T I have.
Enjoy!
EDIT I updated the zip files to the latest version that do not have the error issues. Thanks to @Dan-SRi for pointing out the problem!
Attachments
Last edited: