So silly me tried to replace the lock screen clock font, and apparently the phone didn't like the font I picked, because it is now boot looping
I have the original font file backed up. But I can't get it back on the phone.
I can boot into custom recovery, but when I plug the phone in, adb cannot see it. I have used adb sheel on this PC many times before just fine, but now when I boot to custom recovery and plugthe phone in, nothing happens, and adb devices shows nothing
I need to push this file over, but can't do it without adb seeing the device. Any ideas? Am I totally screwed? Is it possible to get an update.zip that will copy the correct Clockopia.ttf to /system/fonts? I have no experience writing Edify scripts, could someone write an edify script that replaces Clockopia.ttf in system/fonts with the default one?
I'll have to PM you a link to the flashable.zip that I use (I don't have enough posts to put the link in here). After you download it unzip it and place your font into /system/fonts. Rezip and make sure under compression method you select Stored. move this new zip to your sdcard, boot into recovery and "install zip from sdcard"->"choose zip from sdcard" find your zip, flash it and reboot and you should be good to go.
~SkiZophr3nic~
Thanks, one quetions, why is the manifest.mf referencing three fonts?
Name: system/fonts/DroidSans-Bold.ttf
SHA1-Digest: eNby4Fea150Moa0YW6Cm9GxRldk=
Name: system/fonts/DroidSans.ttf
SHA1-Digest: eNby4Fea150Moa0YW6Cm9GxRldk=
Name: system/fonts/Clockopia.ttf
SHA1-Digest: eNby4Fea150Moa0YW6Cm9GxRldk=
Shoot that was the wrong one, my bad. I thought I uploaded a different one. Do you know how to change it or do you want me to fix it and re-up later on tonight?
lol sorry about that.
~SkiZophr3nic~
I got the same thing from someone else, but thanks for the tip that led me in that direction!
Related
Is there anyway to change the second boot screen?
http://forum.xda-developers.com/showpost.php?p=3133153&postcount=91
prolly not talking about splash2, but the Android animation and logo after splash1 & splash2. But i could be wrong.
Theres a folder in framework-res.apk/assets/images that seems to contain the images used in the second boot screen. I haven't had a chance to play with it to see if anything happened. I guess I'll try now and get back to you in 10 minutes. =]
ok so far, I was able to change the second boot screen image without using fastboot, and just modifying the android_320x480.png itself in framework-res/assets/images, but the animation goes out of whack when trying to replace boot_robot.png and boot_robot_glow.png with other images. I'm going to keep at it to see if i can get anywhere.
Hi, i edited the boot_robot_glow.png in PS and it shows up fine when booting
EDIT: I've edited the android_320x480.png but when it boots it shows the original then flicks to the modified one
EDIT: needed to replace boot_robot.png in res/drawable aswell!
Attached images aren'y quite aligned, moves about when booting :S
EDIT: Everything's aligned now
ximonx said:
Hi, i edited the boot_robot_glow.png in PS and it shows up fine when booting
EDIT: I've edited the android_320x480.png but when it boots it shows the original then flicks to the modified one
EDIT: needed to replace boot_robot.png in res/drawable aswell!
Attached images aren'y quite aligned, moves about when booting :S
EDIT: Everything's aligned now
Click to expand...
Click to collapse
would you mind telling us how to replace the files?
adb pull /system/framework/framework-res.apk to your computer,
rename it to framework-res.apk.zip
open framework-res.apk.zip
copy all 3 files into /assets/images
copy boot_robot.png into /res/drawable (in assets/images aswell)
(Uploaded my new boot_robot_glow to use with above files)
ximonx said:
adb pull /system/framework/framework-res.apk to your computer,
rename it to framework-res.apk.zip
open framework-res.apk.zip
copy all 3 files into /assets/images
copy boot_robot.png into /res/drawable (in assets/images aswell)
(Uploaded my new boot_robot_glow to use with above files)
Click to expand...
Click to collapse
Cool... Thanks guys!
Used your images and created a burning Droid for the boot up image.
Adapted the code slightly to run the commands on the phone itself then copied the zip file off the SD card through usb.
Thanks
any pitfalls?
does the image have to be a certain size before 'push' ing it back to the phone?
I like your design so Ill start there, thanks for sharing the work, people have been speculation on how to change this and you did it.
bhang
I'd play it safe and keep everything the size it is, although if you have the dev BL then go for it. It will probably start from the same location on the screen but extend further across and down
This will surround the that icon better than the round glow i made this just now. Looks better just change the hue and make it red if you like.
I can confirm that this work fine on RC30 and ADP1 (there is no reason why it shouldn't but I bet someone will ask...).
So i went ahead and tried to modify the images that make up the animation, got it all repackaged, and pushed it onto the phone. I rebooted and my animation came up like a charm, looking pretty cool, but it got stuck there and the animation kept running. I tried rebooting it several times and then restored it using a backup which fixed it. I am still trying to figure out what i did wrong. Could someone take a look?
Can I modify an existing one by simply dropping in updated bootscreen files, rosie.apk, etc.. and signing the existing rom zip?
Any good guides on how to do one if not, and/or how to use Flipz kitchen tool to create a rom?
Ceger
I am pretty sure if you sign the file and you modify it after that you will have to resign it. At least thats how it goes for other things that are similar that I deal with.
Kcarpenter said:
I am pretty sure if you sign the file and you modify it after that you will have to resign it. At least thats how it goes for other things that are similar that I deal with.
Click to expand...
Click to collapse
I understand that, just wondering if I can add new files and they will move or does some master script need to be updated to know to move the files. In other words, is it done by directory or by file?
For example, if I add some apps to /data/app in the zip will they be there on the phone when I install the ROM zip, etc.. More specifically, I have added an alternate boot sequence. The rom does not have a boot1.gif. If I add the new sequence with XML, will the boot1.gif be installed as well or do I need to update something that directs the install of the ROM to move that file or is it automatic as the folder is moved over?
Ceger
Ceger said:
I understand that, just wondering if I can add new files and they will move or does some master script need to be updated to know to move the files. In other words, is it done by directory or by file?
For example, if I add some apps to /data/app in the zip will they be there on the phone when I install the ROM zip, etc.. More specifically, I have added an alternate boot sequence. The rom does not have a boot1.gif. If I add the new sequence with XML, will the boot1.gif be installed as well or do I need to update something that directs the install of the ROM to move that file or is it automatic as the folder is moved over?
Ceger
Click to expand...
Click to collapse
I have found that the easiest thing to do is just put the files that you want to use to replace the old ones into a signed zip and then flash just those files I have tried altering a rom file with no success
wtphoto said:
I have found that the easiest thing to do is just put the files that you want to use to replace the old ones into a signed zip and then flash just those files I have tried altering a rom file with no success
Click to expand...
Click to collapse
Oh well, was trying to have a one step zip. I guess I can make at least have a 2 step process which is better than 4-5.
Thanks,
Ceger
Yes you can modify just about anything in the rom and flash your zip as long as it is signed and the update script is correct. I always make all my changes to a rom before flashing it so i do not have to flash several different things etc.
The update script is located in RomName\META-INF\com\google\android\
Lets look at a very simple update script to show you what i mean.
In this update script it is to write something to /system
example:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progress 0.1 10
We see here that whatever is in the system folder within the signed zip will be written to the phone
in this case i am writing /system/app/mobiledefense.apk
That will be the only file written to the phone and will be written to /system/app
The update script is not specific to every file so you can have 1 thing in the system folder or 100 and it will write everything in there.
One thing that many people mess up on is not using a update-script file when they sign a .zip file. The recovery has to know what to flash or it will not flash anything.
So the answer is yes you can change many things and then flash the signed update.zip file.
Not everything can be done this way but most things will work.
But for example changing the boot sceen can be done even if the file names are different as long as the folder structure stays the same and the .XML file is the correct one for the boot screen. I opened the .zip of a rom deleted everything out of the boot screen folder and dropped in all the files from the nexus one hero hybrid boot screen re signed the zip and everything flashed perfect. I changed many other things as well in the .zip like rosie.apk, sound files, lockscreen files, busybox files, added apps to /system/app and just resigned the zip and everything flashed the way i wanted it to and works perfect.
The way to correctly zip a file is to extract the zip modify what you want then select everything inside the zip right after you open the folder and the highlight everything select add to archive and then zip it up now sign that .zip
so say you extract the ROM and it is named Rom123 now you will have a folder named Rom123 open that folder and select everything file or folder in there and then hit add to archive that will make another zip right there called Rom123.zip pull that zip out to the desktop and sign that zip file and thats it.
I Know that is confusing as it is late as hell and i am tired but wanted to answer this real quick.
zippy-man said:
Yes you can modify just about anything in the rom and flash your zip as long as it is signed and the update script is correct. I always make all my changes to a rom before flashing it so i do not have to flash several different things etc.
The update script is located in RomName\META-INF\com\google\android\
Lets look at a very simple update script to show you what i mean.
In this update script it is to write something to /system
example:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progress 0.1 10
We see here that whatever is in the system folder within the signed zip will be written to the phone
in this case i am writing /system/app/mobiledefense.apk
That will be the only file written to the phone and will be written to /system/app
The update script is not specific to every file so you can have 1 thing in the system folder or 100 and it will write everything in there.
One thing that many people mess up on is not using a update-script file when they sign a .zip file. The recovery has to know what to flash or it will not flash anything.
So the answer is yes you can change many things and then flash the signed update.zip file.
Not everything can be done this way but most things will work.
But for example changing the boot sceen can be done even if the file names are different as long as the folder structure stays the same and the .XML file is the correct one for the boot screen. I opened the .zip of a rom deleted everything out of the boot screen folder and dropped in all the files from the nexus one hero hybrid boot screen re signed the zip and everything flashed perfect. I changed many other things as well in the .zip like rosie.apk, sound files, lockscreen files, busybox files, added apps to /system/app and just resigned the zip and everything flashed the way i wanted it to and works perfect.
The way to correctly zip a file is to extract the zip modify what you want then select everything inside the zip right after you open the folder and the highlight everything select add to archive and then zip it up now sign that .zip
so say you extract the ROM and it is named Rom123 now you will have a folder named Rom123 open that folder and select everything file or folder in there and then hit add to archive that will make another zip right there called Rom123.zip pull that zip out to the desktop and sign that zip file and thats it.
I Know that is confusing as it is late as hell and i am tired but wanted to answer this real quick.
Click to expand...
Click to collapse
Perfect, just what I was looking for.
Thank you, just made my day!
Ceger
It's not much, but I thought everyone should be able to theme their Framework
Requirements: WinZip(or any other zipping program), Android SDK, testsign, some graphics editor...
NOTE: This will work with theme apk's as well !!!
So what you need to start with is your framework files:
framework-res.apk, com.htc.resources.apk ... both are located in SYSTEM:framework/
These files are just renamed zip files, so rename them back to .zip and extract them (you can also edit them inside WINRAR or something, but it is more comfortable if you extract them)
In these, images are usually saved in res/drawable-mdpi or such, but you have to think here, allways modify all files from one resource
Now locate the images you want to edit but I only know how to edit .png files (.9.png files are for a different howto, probably not by me as I've never really mastered it)
Pick those you want to edit, and edit them (I'm not gonna tell you how here, I usually use photoshop to do that )
Once you have edited those images, it is recomended to optimize those png's (Firstly to make them smaller, but more importantly, most of the times the png's from Windows graphics editor didn't work for me...)
To optimize png's you can use:
OptiPNG: DOWNLOAD This one is drag'n'drop batch conversion capable...
Pngcrush: DOWNLOAD Command line utility, but it has more settings
...or something else, but I find these two the best
Once you have these optimized, copy and re-write them to folders you took them from to edit...
Now you need to zip these back, for framework files I was told it is usual to zip them as "store", but correct me someone if I'm wrong.
After you have zipped those, they will have to be re-signed. To do this, use testsign from code.google.com
Then run this in cmd line (or create a .bat file as I did, it's much easier):
Code:
java -classpath testsign.jar testsign [COLOR="DarkRed"]file.zip[/COLOR] [COLOR="DarkRed"]file-signed.zip[/COLOR]
Now that you have signed it, it is recomended to zipalign it:
(zipalign.exe is located in /tools in your SDK)
Run this in cmd line:
Code:
zipalign 4 [COLOR="DarkRed"]infile.zip[/COLOR] [COLOR="DarkRed"]outfile.zip[/COLOR]
(4 is alignment in bytes)
Now that you have aligned the .zip, rename it to the original name and then you just need to push it back to your phone:
Code:
adb shell mount /system
adb push [COLOR="DarkRed"]com.htc.resources.apk[/COLOR] /system/framework/[COLOR="DarkRed"]com.htc.resources.apk[/COLOR]
or
adb push [COLOR="DarkRed"]framework-res.apk[/COLOR] /system/framework/[COLOR="DarkRed"]framework-res.apk[/COLOR]
And you're done
I hope this helps someone! Enjoy!
note: This way you should be able to modify any apk I think
Very good.
Good initiative, thank you.
Lets hope that others will follow your example and contribute in this community,we need it.
Sent from my HTC Desire S using XDA Premium App
One question... can i change the framework if i'm s-on? And if yes how? flash it through recovery or how?
LE: Thx for the info. I found out how to edit themes... i will create a cool one to upload here. I could edit the framework.....but i am s-on so no use for that.
Unfortunately, when you're unrooted, you can't push files to your system...
But this will work for those Theme apk's too... so grab a theme you like and you can edit it as easily as you would your framework It has a limited potential, but it's something for you S-ON users
Hmm, I skipped the push part and copied the file back over the one in the phone. Now my phone is stuck in a continuous loop on the "quietly brilliant" screen.
Any help? Where do I get a stock rom to flash?
rogbese said:
Hmm, I skipped the push part and copied the file back over the one in the phone. Now my phone is stuck in a continuous loop on the "quietly brilliant" screen.
Any help? Where do I get a stock rom to flash?
Click to expand...
Click to collapse
Just enter recovery & factory reset,wipe, then wipe dev cache, then reflash your rom that you were using before the bootloop.
You can even swap icons in the framework of your rom then just flash (if you try to swap framework.apks or dialer.apks using a file manager you will delete or swap the file but this will cause loads or errors & force closes & then result in your bootloop!) Then just swap via a computer within the zip file then just flash in recovery as normal & if done right you wont get bootloops
Hey, I'd like to know how to change the bootanimation in Kyrillo's ROM as ive already tried BootAni and some other apps and even tried manually changing the Bootanimation in "data" and "system/media"...didnt work.... it'd be great if i could get some help and if possible in a step by step manner...
1. Find a suitable replacement in bootanimation.zip format.
2.check to make sure this isnt an update zip. (do this by exploring the file, it should consist of only files names "part0" and "desc.txt" and maybe "part1")
3.If it is a update zip, unzip it and extract the bootanimationzip inside it.
4. place this onto sd card
5. use root explorer or similar to move the file to system/media, making sure it is named "bootanimation.zip" it should say something like "file exists, replace it?". say yes.
6. now long press the new file and open up permissions in the menu. set these as rw-r--r--
7. reboot phone and enjoy!
bear in mind that kyrillos 10.4 is based on open fimg, so you may have white patched in the boot animation, just like the one preloaded onto it.
In 10.4, Kyrillos has fixed the white patches in SOME bootanimation, like the stock one.
ak700 said:
In 10.4, Kyrillos has fixed the white patches in SOME bootanimation, like the stock one.
Click to expand...
Click to collapse
I did ..
On an extra note:
If you want to avoid having white flashes in your bootanimations on any rom with openFIMG you should look for one with less than 75 frames in the part1 folder. Any frames past that turn white...
Tried didnt work!!....
Ava.tar said:
1. Find a suitable replacement in bootanimation.zip format.
2.check to make sure this isnt an update zip. (do this by exploring the file, it should consist of only files names "part0" and "desc.txt" and maybe "part1")
3.If it is a update zip, unzip it and extract the bootanimationzip inside it.
4. place this onto sd card
5. use root explorer or similar to move the file to system/media, making sure it is named "bootanimation.zip" it should say something like "file exists, replace it?". say yes.
6. now long press the new file and open up permissions in the menu. set these as rw-r--r--
7. reboot phone and enjoy!
bear in mind that kyrillos 10.4 is based on open fimg, so you may have white patched in the boot animation, just like the one preloaded onto it.
Click to expand...
Click to collapse
i tried it .... didnt work .... idk why.... just to change the bootanimation i bymistake flashed a motorola Xoom bootanimation please help...plzplzplzplz.... im stuck here with nothing but "A)" out of the whole bootanimation plz help im tired of trying to change my bootanimation!!!!!
I finally figured out what was stopping a custom boot animation from being installed onto the HD 10 running stock FireOS. This guide will show you how to replace the boot animation, to just about anything you want. For reference, we are using my favorite Android boot animation from Marshmallow, but there is Lollipop boot animation as well. You need to be rooted in order to complete this guide.
****THIS MAY NOT WORK FOR YOUR TABLET. RESULTS CAN VARY. YOU ARE PERFORMING THIS GUIDE AT YOUR OWN RISK. WORST CASE SCENERIO: NO BOOT ANIMATION (MUST REFLASH YOUR CURRENT VERSION OF FIRE OS TO RESTORE IT)****
1. Download the Marshmallow boot animation zip from this thread (1080p is perfect) to your internal storage. Using a root explorer, open the zip file and tap system then media and extract 'bootanimation.zip' to your internal storage.
2. Download 'bootanimation.zip' at the end of this post and extract the 'bootanimation' file to your desktop PC or the internal storage of your tablet. (THIS IS NOT A FLASHABLE ZIP FILE)
3. Again, using a root explorer, navigate to /system/bin and make a copy the 'bootanimation' file and back it up to a folder in your storage. Now copy the 'bootanimation' file you downloaded in step 2 and paste it in /system/bin, overwriting the existing one. Make sure to set the permissions of the file to rwxr-xr-x
4. Using a root explorer again, go back to your internal storage and copy the 'bootanimation.zip' you extracted earlier in step 1. Then navigate to /system/media and paste 'bootanimation.zip'. Set the permissions to rw-r--r--
5. Reboot and watch your animation. See video: https://www.youtube.com/watch?v=3lmNGAn_YIY
HOW?
The answer was in /system/bin. Amazon modified the 'bootanimation' file in /system/bin so only their boot animation is the one used. If you had only placed the zip in /system/media, the animation would animate for a few seconds, freeze and just before the end of booting, would start to animate again. I tried portrait and landscape. I tried different resolutions. I tried different animations and every one of the animations would freeze. I opened up the ROM for the Fire 7 (Fire Nexus ROM by @ggow) and copied the 'bootanimation' file from /system/bin over to the stock FireOS ROM on the HD 10, and set the proper permissions. Problem solved!
Updates:
January 11, 2019: The bootanimation-STOCK.zip attached below, contains the stock FireOS bootanimation. Simply delete the bootanimation.zip in /system/media (if there is one). Extract/unzip the bootanimation-STOCK.zip into internal storage and copy/paste the bootanimation file to /system/bin, overwriting the one there.
Awesome post, as always, Mr. DragonFire1024
Heads up. If you simply overwrite the file in /system/bin with the bootanimation file (not the zip) and reboot, you get a surprise. I don't want to ruin it With that said, if someone could extend that animation a little...
Wonder if we can use the Oreo Boot animation I'm using for my Moto G4??
Touchpad64gb said:
Wonder if we can use the Oreo Boot animation I'm using for my Moto G4??
Click to expand...
Click to collapse
Should be able to copy the .zip from /system/media to the same folder on the HD 10. The worst that can happen is it won't work (but won't break anything. You may get a black screen until the booting finishes) or the graphics will be too small.
Edit: still need to overwrite the bootanimation file in system/bin no matter what animation you want to use. It just needs to be done once
DragonFire1024 said:
Should be able to copy the .zip from /system/media to the same folder on the HD 10. The worst that can happen is it won't work (but won't break anything. You may get a black screen until the booting finishes) or the graphics will be too small.
Edit: still need to overwrite the bootanimation file in system/bin no matter what animation you want to use. It just needs to be done once
Click to expand...
Click to collapse
Alright, I'll give it a try...Thanks for the Reply.
DragonFire1024
I was just curious if you plan to do any more YouTube videos as proof of concepts to coincide with your very helpful posts
dondraper23 said:
DragonFire1024
I was just curious if you plan to do any more YouTube videos as proof of concepts to coincide with your very helpful posts
Click to expand...
Click to collapse
Depends what I find or do and if it should have a video. I'm always working on something ?
DragonFire1024 said:
Depends what I find or do and if it should have a video. I'm always working on something
Click to expand...
Click to collapse
I know you are and I always look forward to what you post next!
I Just wanted to report back and let you guys know that the Custom Oreo Boot Animation works Perfectly for FireHD10. I used the 1440p Resolution file from here https://www.yourtechnocrat.com/download-android-o-oreo-bootanimation-on-any-android/
Touchpad64gb said:
I Just wanted to report back and let you guys know that the Custom Oreo Boot Animation works Perfectly for FireHD10. I used the 1440p Resolution file from here https://www.yourtechnocrat.com/download-android-o-oreo-bootanimation-on-any-android/
Click to expand...
Click to collapse
I just tested that out. Thanks for the info! Works great.
I cannot, regardless of what I do, get this to work.
I have followed the instructions - exactly - multiple times now.
I have tried numerous bootanimation.zip, including the one linked to in OP.
Files are in the proper locations, file permissions are set as specified.
It doesn't matter if I have the zip in /system/media or not, I get a black screen until UI loads.
Power on --> amazon logo --> black screen --> UI, no matter what I seem to do.
Any help would be greatly appreciated. This is driving me nuts, I just don't understand what I'm missing or doing wrong.
help
Yeah, I followed all the directions and still cant get it to work nor can I get the original boot animation to work.
Delon88 said:
Yeah, I followed all the directions and still cant get it to work nor can I get the original boot animation to work.
Click to expand...
Click to collapse
I can't either. I tried after reading your comment.
No zip in /media, restored bootanimation in /bin to the original, still just a black screen during boot.
So this broke the bootanimation altogether.
Edit: I will add that my stock OS was 5.6.0.1. I suspect something has changed from previous versions, what was your stock version? What was OP's?
smam1338 said:
I can't either. I tried after reading your comment.
No zip in /media, restored bootanimation in /bin to the original, still just a black screen during boot.
So this broke the bootanimation altogether.
Edit: I will add that my stock OS was 5.6.0.1. I suspect something has changed from previous versions, what was your stock version? What was OP's?
Click to expand...
Click to collapse
You have to place the bootanimation.zip in /system/media after overwriting the file in /system/bin. Unzip the animation in the link in OP. There will be another zip inside it. that's the zip you use.
DragonFire1024 said:
You have to place the bootanimation.zip in /system/media after overwriting the file in /system/bin. Unzip the animation in the link in OP. There will be another zip inside it. that's the zip you use.
Click to expand...
Click to collapse
Yeah I follow, and I did so several times. I can't even revert to having the stock "fire" boot animation.
Following the guide effectively broke my boot animation altogether. Again, I cannot even go back to having the original boot animation. Same thing the guy who replied after me reported as well.
smam1338 said:
Yeah I follow, and I did so several times. I can't even revert to having the stock "fire" boot animation.
Following the guide effectively broke my boot animation altogether. Again, I cannot even go back to having the original boot animation. Same thing the guy who replied after me reported as well.
Click to expand...
Click to collapse
Make sure the permissions are set correctly. .bin file: rwxr-xr-x and the .zip: rw-r--r--
DragonFire1024 said:
Make sure the permissions are set correctly. .bin file: rwxr-xr-x and the .zip: rw-r--r--
Click to expand...
Click to collapse
Yes, I have, numerous times. As I have said.
I'm going to flash my system.img backup and see if that restores the stock boot animation, because nothing else has.
Edit: dd-ing my system.img of my post-root supersu backup restored my boot animation to stock.
Final Edit/Update:
Confirming that this does indeed work. I'm not sure what exactly I did the first time, but it completely botched the boot animation.
dd'd system.img (I had other compelling reasons to anyway), followed the instructions again, exactly as they are written.
I didn't even extract the zip on PC and then push, I did it all in ES.
The first time I did this I think I had some sort of permission issues (had to delete bootanimation and then paste the replacement, couldn't overwrite), and I suspect that combined with a little user error ruined boot animation. Anyway, thank you for the guide @DragonFire1024. This is a little thing, but completely worth it, imo.
smam1338 said:
Yes, I have, numerous times. As I have said.
I'm going to flash my system.img backup and see if that restores the stock boot animation, because nothing else has.
Edit: dd-ing my system.img of my post-root supersu backup restored my boot animation to stock.
Final Edit/Update:
Confirming that this does indeed work. I'm not sure what exactly I did the first time, but it completely botched the boot animation.
dd'd system.img (I had other compelling reasons to anyway), followed the instructions again, exactly as they are written.
I didn't even extract the zip on PC and then push, I did it all in ES.
The first time I did this I think I had some sort of permission issues (had to delete bootanimation and then paste the replacement, couldn't overwrite), and I suspect that combined with a little user error ruined boot animation. Anyway, thank you for the guide @DragonFire1024. This is a little thing, but completely worth it, imo.
Click to expand...
Click to collapse
Very strange but glad it worked. You can now have just about any boot animation you can find. Simply replace the zip in /system/media, give permissions, reboot. Just make sure to have the right resolution ?
DragonFire1024 said:
Very strange but glad it worked. You can now have just about any boot animation you can find. Simply replace the zip in /system/media, give permissions, reboot. Just make sure to have the right resolution
Click to expand...
Click to collapse
I still have no idea where I messed it up. It seems like ES wasn't actually in Root Explorer, it showed the permissions as being set, but they definitely weren't.
Was weird that I could delete then paste bootanimation in /bin but not overwrite.
Of course, right after I got this working I used a boot animation that wasn't the right resolution.
I thought 1440p would just look better, not give me a bootloop
I've spent way too much time on merely changing the boot animation. :laugh: