Related
Are they device specific or can I flash any from the evo/epic/etc threads?
Sometimes device specific, although some aosp ones can work on a few phones.
Is there a method for figuring out which are safe or can I grab any HTC animation and stay away from Samsung?
Is it even UNsafe to try others or will they simply not work?
thanks
Here is our stock boot animation on the Shift. It needs to be exactly the same as this (besides obvious changes to the content of the .png files).
The desc.txt file can be different, as those are the instructions of what image to show at what time during the animation.
All a bootanimation consists of is a collection of JPEG images and desc file, which tells the phone how to size the images, at what speed to show them, what is repeated, and how many times to do so. It is like a computer age flip book. Since most previous phones placed the animation in /system/media, which the shift does not, I would recommend not flashing animations not intended for this phone. Instead, take only the file bootanimation.zip from the flashable update, and either push it via adb, or copy and paste to /system/cutomize/resource/bootanimation.zip. The worst thing that will happen is that you get a bootloop, or the image is poorly formatted for this phone. If this happens, just use adb to push the original boot animation to /system/customize/resource/bootanimation.zip, and reboot, or do a nandroid restore. If the images are the wrong size, this is easily fixed by editing the size in the desc file. If you get bootloops play with the speed and repeat lines in the desc file. One last thing, if you open the bootanimation.zip to edit anything, you MUST rezip with absolutely no compression, or it will not work.
If anything in the above is not clear, please do not hesitate to ask for more information.
Hi everyone,
Today, I just found out about M10tools, which is required to change the m10 files within Rosie.apk and others such as Idlescreen_Base.apk. (for Sense 3.0)
I just wanted to change the image that is displayed when you receive an SMS - so instead of the Giant MMS symbol, I used another image.
So I decompiled the Idlescreen_Bake.apk, decoded the images, found the MMS image in textures, edited/replaced the image with one of my own.
(note, the original image is 250x250, and the image I uploaded is 250x270)
Then saved in another location.
When I check to see if it's replaced correctly, I opened up the new Idlescreen_Base.apk, and when I get to the png image, the image is messed up - kinda like when your analog TV would be messed up on certain channels and the image is repeatedly cut.
I was wondering if it had anything to do with my not editing the original image itself. I tried scaling my image down to 250x250, which didn't work either.
Any help would be greatly appreciated
Short Answer: its because you didn't edit the original image file
Long Answer: I have never edited mms icons but I have made my own lock rings by editing that same file. Open the apk in m10 tools then find the texture you want to edit and right click the image of it on the right side then choose show in explorer. Right click the highlighted file and open with your image editor. I use Photoshop. Then put your new image on top of the old one and delete the original. Now for lock rings you have to rotate your image 180° and mirror it across the y-axis. I don't know if you have to do this with mms notifications. Then do file save and select PNG as the format and do not change the name of the file. Then back in m10 tools go to save apk. Then push it to /system/app
Caution:::: I have today (1-18-2015) heard on the rumor mill that Motorola have used a new binary in the 5.0.2 update, this binary affects the boot animation. In effect it may only allow animations made in an mp4 format to work and causes a system crash if using the old, tried and tested format of frames of jpg's or png's. This of course fits in with Motorola's own animations which are mp4's. I can't vouch for the fact that it may be possible to overcome this by changing permissions but it seems that the new binary will have to be installed. In view of the fact that all my animations up to now are jpg's and png's I would strongly advise you don't install them on a 5.0.2 upgrade. I hope I'm being over cautious but I wouldn't want anyone to have to go through the number of re-sets that I have had to do over the past few days.
I've made a couple of animations for the 2014 moto g so over the next couple of days I'll post them to this thread in case anyone is interested. The usual disclaimer applies i.e. I am not responsible if installing these files causes your house to blow up, your cat to run away or your wife,partner or friend leave you for the next door neighbor.
This first one is CIA themed so I have made a similar bootlogo file in case anyone wants to go the whole way! The two files are easily identifiable by the names.
The "Logo" file is a flashable zip using any custom recovery (TWRP - CWM - Philz).
The animation zip has to be placed manually using any file manager you like.
First - go to ..... /system/media ..... and rename the bootanimation which is there to avoid it being overwritten. You can add the word "old" or "bak" or anything you like.
Second - copy the CIA-Anim.zip file to the folder ...../system/media ..... and then rename it bootanimation.zip
These files will work with KK and Lollipop O/S's and with all versions of moto g 2014 edition.
The PNG file shows you the Logo ..... The GIF file gives you an idea of the animation.
OK here is another one. Same as before all disclaimers apply i.e. house - cat - neighbor.
Logo file is "recovery flashable zip"
Anim file is put into ...../system/media ..... folder
JPG shows how Logo looks ..... GIF gives you an idea of the animation.
OK here is another one. Same as before all disclaimers apply i.e. house - cat - neighbor.
Logo file is "recovery flashable zip"
Anim file is put into ...../system/media ..... folder
JPG shows how Logo looks ..... GIF gives you an idea of the animation
Here's one for the Marvel Fans.
Usual disclaimer and guidance applies
Logo is flashable in recovery ..... Anim rename and place in /system/media
JPG shows Logo ..... GIF gives idea of Anim
OK as before same disclaimer and guidance apply
Logo file is flashable in recovery ..... Anim file placed in /system/media
At the moment I am holding off from posting any further anims. Before posting I always try out new anims on my own XT1064 to make certain they work and there is no possibility of bootlooping for other users. Since updating to 5.0.2 I have found problems installing new anims i.e. continuous bootlooping causing me several instances of having to factory reset and re-install the update. Until I can determine whether this is a fault on my phone or is caused by the 5.0.2 update I won't post any more. As a possible related issue, I have found that I can no longer make alterations to the "build.prop" file without causing a bootloop and crash.
If you unlock your bootloader, it will put an annoying warning message instead of the usual greeting screen when you first boot up.
If you want to restore to stock logo screen, go to Hashbang173's thread.
If you want to restore your custom greeting, follow the steps below:
1. Download the XT1575-logo-new-9-14-15.zip file from Hashbang173's thread and extract the logo.bin file.
2. Connect your phone to your computer. Then run this:
Code:
adb shell su -c “dd if=/dev/block/platform/f9824900.sdhci/by-name/clogo of=/sdcard/clogo.bmp”
3. Then you can use a file browser app, go to your sdcard, and email the clogo.bmp to yourself. This clogo.bmp is your original custom greeting screen. You can actually customize that file if you want a different picture.
4. Next, download the boot logo maker by caitsith2.
5. Run the logo maker and load the logo.bin from hashbang173 that you downloaded at the beginning.
6. Replace the logo-boot and logo-unlocked image with your clogo.bmp file.
7. Save the project in the boot logo maker. It will create a flashable zip file.
8. Extract the new logo.bin from that new zip, then flash it via fastboot (replace /path/to/logo.bin with the actual path to the new logo.bin you just extracted):
Code:
fastboot flash logo /path/to/logo.bin
I've uploaded a template logo.bmp file that you can edit and use for the moto maker to make your own custom greeting. If you want to make your own, skip step 2, and use the uploaded logo.bmp to edit as step 3. Dimensions for your custom image needs to be 1440x2560 pixels.
Credit
@Hashbang173 for creating the original logo restore.
@caitsith2 for the logo maker tool.
@vnphantom for figuring out how to retrieve your custom boot screen.
Thank you for this!
Mine is saying Not Found. Is there a way for me to just make my own with it saying whatever I want?
CJ-Wylde said:
Mine is saying Not Found. Is there a way for me to just make my own with it saying whatever I want?
Click to expand...
Click to collapse
Sure. Simply make an image to replace it. I'm assuming any file format would work, but the one pulled from the phone was a BMP file with dimensions 1440x2560 pixels.
I'll upload a template to the OP.
I keep getting Failed at barcodes Produced file is 96889 Bytes Too Large. Already tried lowering down the image resolution to make file smaller but still no success. Any tips?
Tabaqui said:
I keep getting Failed at barcodes Produced file is 96889 Bytes Too Large. Already tried lowering down the image resolution to make file smaller but still no success. Any tips?
Click to expand...
Click to collapse
I am using this tool to create custom logos. You can also fully customize the battery charger and bootloader images (like the android with his belly open).
For the logo file I'm saving them as 1400x2560 24bit .png files. (but in the tool you can see the resolution for the other types.
1) Open the logo.bin from this thread.
2)Replace whichever images you want
3) Save as zip
4) take the bin file from the zip and flash it with fastboot... fastboot flash logo mylogo.bin
http://forum.xda-developers.com/moto...ource-t2848667
To scare away the snoops...
https://imgur.com/Esu7I9s
ErikHellstrom said:
I am using this tool to create custom logos. You can also fully customize the battery charger and bootloader images (like the android with his belly open).
For the logo file I'm saving them as 1400x2560 24bit .png files. (but in the tool you can see the resolution for the other types.
1) Open the logo.bin from this thread.
2)Replace whichever images you want
3) Save as zip
4) take the bin file from the zip and flash it with fastboot... fastboot flash logo mylogo.bin
http://forum.xda-developers.com/moto...ource-t2848667
To scare away the snoops...
https://imgur.com/Esu7I9s
Click to expand...
Click to collapse
It finally worked by using jpeg and reducing the file to 85kb. Sadly the image looks kind of blurry on my phone
Tabaqui said:
It finally worked by using jpeg and reducing the file to 85kb. Sadly the image looks kind of blurry on my phone
Click to expand...
Click to collapse
Mine worked at 191K. I read that the reason the default logo screens are mostly one color is to reduce size. So going with a circle of detail in the middle of rectangle of one color can help.
ErikHellstrom said:
Mine worked at 191K. I read that the reason the default logo screens are mostly one color is to reduce size. So going with a circle of detail in the middle of rectangle of one color can help.
Click to expand...
Click to collapse
I guess that's why it was giving me issues, since I am not using a one color image. I just re-sized one of the icons in the picture and reduced the image to the same 85kb and it wont work again. Even by reducing it at 74kb. Ill attach the image in case you want to take a look at it
Tabaqui said:
I guess that's why it was giving me issues, since I am not using a one color image. I just re-sized one of the icons in the picture and reduced the image to the same 85kb and it wont work again. Even by reducing it at 74kb. Ill attach the image in case you want to take a look at it
Click to expand...
Click to collapse
you should be able to get it in at 1.5 mb
ErikHellstrom said:
you should be able to get it in at 1.5 mb
Click to expand...
Click to collapse
Already tried every format to save it in photoshop and still doesnt work . Ill try asking in the tool's thread to see if photoshop has something to do or what.
Tabaqui said:
Already tried every format to save it in photoshop and still doesnt work . Ill try asking in the tool's thread to see if photoshop has something to do or what.
Click to expand...
Click to collapse
Try this one. Unzip it, then flash in fastboot.
Stryder5 said:
Try this one. Unzip it, then flash in fastboot.
Click to expand...
Click to collapse
Thanks :good: it worked. Ill like to know though, how were you able to make the bootlogo maker accept the big image.??
Tabaqui said:
Thanks :good: it worked. Ill like to know though, how were you able to make the bootlogo maker accept the big image.??
Click to expand...
Click to collapse
Your dimensions were off. I simply stretched it out to the dimensions mentioned earlier. I've edited the OP to reflect dimensions for custom images.
When I pulled the logo, I saved the files as .png... and that's how I save my edits. .png is better at stretching/shrinking and not looking bad. My logo.bin file was 2.43/MB and had no problem..
Plus, I use paint.net to edit... it's free and you can do a lot of stuff with it.. .
Anyone willing to make a video of how to??
cerobles1 said:
Anyone willing to make a video of how to??
Click to expand...
Click to collapse
This is what I did... post #83 with link....
http://forum.xda-developers.com/moto-x-style/development/logo-remove-unlocked-bootloader-warning-t3201141/page9
Decided to recycle an image I've been using since the HTC Vision days. Feel free to use it, just remember that I had to upload it in .jpg format.
Finally decided to root my phone and this was one of the first things i had to do.
I'm a huge kindgom hearts fan and FF7 fan so i had to get cloud as my boot image, after some snooping this is what i came up with. Feel free to use
Tabaqui said:
I guess that's why it was giving me issues, since I am not using a one color image. I just re-sized one of the icons in the picture and reduced the image to the same 85kb and it wont work again. Even by reducing it at 74kb. Ill attach the image in case you want to take a look at it
Click to expand...
Click to collapse
I had the same thing happen when I stretched the image. I had to just leave the image centered. If you stretch it size of image increases and may be too big. I saved in .bmp, but png worked as well. Good luck.
---------- Post added at 09:18 PM ---------- Previous post was at 08:20 PM ----------
Tabaqui said:
Already tried every format to save it in photoshop and still doesnt work . Ill try asking in the tool's thread to see if photoshop has something to do or what.
Click to expand...
Click to collapse
Okily dokily. Here is how it worked for me using Photoshop.
Open a new image 1440 pixels X 2560 pixels, resolution 96px/in
Paste the image in, make changes etc. Make sure the image takes up all the room you want. You don't want to stretch it later.
Go to save as and choose jpeg.
Image options should pull up. Choose low quality. If it is over 100K use the slider to lower it even more. I'm not sure exectly where the cutoff is, but mine worked at 85.1k
WHY THIS TUTORIAL YOU MIGHT ASK? Making a boot animation for Android certainly isn't rocket science. Well, in most cases, I would certainly agree. I make animations for Android all the time without a hitch. The Honor 8, however, proved to be a special case for many reasons. First of all, it stores the bootanimation.zip in several places throughout the device, so determining which one needed to be replaced was the first obstacle. I soon discovered too that the device is also is extremely particular about the format of the images, the method of compression used on the images and the method of compression used in zipping the files. Since I don't own the device myself too, it took weeks of almost continuous tests with someone who had the device to actually determine what parameters needed to be in place for the animation to function properly.
-------
Btw, Here Are My Honor 8 Animations For Reference:
https://forum.xda-developers.com/showthread.php?p=70645944
-------
SO, BY REQUEST, HERE ARE THE STEPS FOR GETTING YOUR BOOT ANIMATION WORKING ON THE HONOR 8:
1) Set Up A Project Folder - First of all lets make a project folder(called "My Animation" or whatever). Open the folder and make two more folders inside it called "part0"(for the first part of the animation) & "part1"(for the second part). Then also create a blank ".txt" file called "desc.txt" and just copy this bit of text into it for now and save it:
1080 1920 20 p 1 0 part0 p 0 0 part1
2) Decide How You Want Your Animation To Work - For the first part of my animation I decided to have it simply fade in on mine. After fading I made an actual moving animation frame by frame that would just loop until the device boots up.
3) Make Sure Your Images Are The Correct Size - When creating the images for the Honor 8 you will need to make sure that they are 1080x1920 resolution, since that's the resolution of the display.
4) Naming The Images - When naming your images you'll want to make sure they appear in the proper sequence. To do this it helps to add numbers to each. You'll want to save the files for the first part of your animation into the "part0" folder, naming them something like "myanimation_001.png", then "myanimation_002.png", etc. Then, once you've finished the second part of the animation you'll want to save those files into the "part1" folder. Make sure that if you ended on say "myanimation_009" in "part0" that you continue where you left off at "myanimation_010" in "part1".
5) Make Sure Your Images Are PNG - Here's where things start to get trickier on the Honor 8. Even though the stock animation is in JPG, for some reason if you use anything other than PNG format, the most you will likely get when testing your animation is a bootloop or a flickering black screen. The Honor 8 seems to prefer PNGs.
6) Converting Your JPGs To PNGs(if needed) - If you're making your animation from scratch, say in Photoshop, then you can simply just save each frame of the animation as a PNG from the start, but if like me you already saved them to JPG or if you're extracting images from a video that come out JPG or you're porting another animation that's already JPG, then you will need to convert. You can load each image into a program like Photoshop and just do a "Save As" .PNG, as I mentioned, but you'll have to do them one by one. If you want to convert them all at once though with a batch conversion, then there is also a great free program called IrfanView for that here: http://www.irfanview.com/
7) Compressing Your PNGs(if needed) - PNGS will generally be larger files, perhaps even 10 times larger than JPG. If you don't compress them there's a chance that your animation will lag under the weight of those larger files if they're too big. Also, you don't really want people to have to download a 50-60MB boot animation file anyway. In my animation everything worked fine after I converted the images, but I had to try a few different programs to compress the images before the animation would actually show after the compression, as most programs seemed to be producing PNGs that the Honor 8 simply didn't like for whatever reason. You want to find a PNG compression program that says it's "Lossless" by the way. This means that the images won't really lose any quality in the process. (For reference, I actually ended up using a Chrome extension in the end called "iLoveIMG" on a whim that produced the proper PNGs and compressed them all by about 66%.)
8) Setting The Animation Parameters - Before you finish your animation you may want to edit the parameters we entered for it earlier in the "desc.txt" file to tell it where the images are and how fast you want your animation to play. If, like most animations, you just want the first part to play once and the second part to loop until the device boots, then you can probably just leave this file for now with the text we entered before. It will play at 20 frames per second as we have it now. Then later, after testing the animation, if you find it's playing too fast, then you might want to just edit the "20" in there to something less like "10" or if it runs too slow then you can try changing it to something higher like "30". Whichever way looks better.
Here's a brief explanation of what each part in the "desc.txt" means:
"1080 1920 20 p 1 0 part0 p 0 0 part1"
1080(width) 1920(height) 20(frames per second)
p(new part indicated) 1(times to play part) 0(seconds to pause before next part) part0(folder name)
p(new part indicated) 0(times to play-0 means infinite) 0(seconds to pause) part1(folder name)
9) Making Your "bootanimation.zip" File - In order for your animation to work, you're going to have to pack the "part0", "part1" & "desc.txt" files into a zip file called "bootanimation.zip". You must make sure that you select "No Compression" when packing the zip though or the animation will not work and will likely just show a black screen.
10) Testing Your Animation - First of all, before testing PLEASE BACKUP YOUR DEVICE in TWRP, if it doesn't work and gives you a bootloop, then you will need a backup to restore your device. The alternative to this is just having another "working" boot animation to flash in TWRP to be able to boot up the device again. As I said, there are many copies of the "bootanimation.zip", so it took some time to determine which one to replace. It turns out that it was actually the standard "/system/media/bootanimation.zip" one that needed to be changed. This might seem like a no brainer to anyone who is familiar with making animations for Android, but until the images and everything else were properly formatted the animation wouldn't show anyway, so there was no way really to determine if the issue was due to a particular animation file being replaced or something else. Again though, this was the only device I've seen that keeps a copy of the "bootanimation.zip" in so many folders, so that was still a bit confusing to be sure. Anyhow, just navigate to your animation file in a root browser and move it into the "/system/media/" folder to replace the current animation. Make sure before you ever reboot though that you've changed your "bootanimation.zip" files permissions to "rw-r--r--" after copying it over or you will get a bootloop. Optionally too, you can save your original "bootanimation.zip" to a folder somewhere on your sdcard if you want to save it as an additional backup or you can just install my animation linked at the top of this post if you get stuck and can't boot.
NOTE: If you're making animations for Honor 8 devices with Nougat installed, then it appears they actually moved the location of the boot animation to "/cust_spec/media/", so you will want to put the image there. It's not confirmed yet though whether this is true for all Honor 8 devices with Nougat, but it has been confirmed for some. The US variant of the FRD-L04, build B162, Marshmallow, also stores it's animations in "/cust_spec/media/" however, so it can be a bit tricky. If you make a file for that and "/system/media/" as well though, then you should be covered. You can always check the OP of my animations page too(linked above) to see if there are any more updates on this.
-------
So there it is to the best of my knowledge. I hope this helps any of you that want to customize your boot animation on the Honor 8 to hopefully be able to do it relatively stress free. As usual, if you like this post or if you found it useful in some way, then please feel free to click the "THANKS" button on this post or even a mention on your animation thread when you finally upload it might be cool too. [emoji14]
Thank guys! Good luck.
NOTE: You may have noticed that I packed my animations(linked above) into a flashable zip, so people don't have to do it manually. If you need any help with this down the road, then just let me know on this thread. Also, I may go back through this thread at another time and attempt to make it more concise if possible. Thanks!