Database Info

Skinning question

In framework-res.apk, what controls the color of the text for the status bar, such as notifications and the digitial clock? Are these controlled independently by seperate apks?
I'm considering diving in and attempting to skin my android but I want to know what I'm getting into.

I've tried replacing framework.apk that I built from source on a real device and emulator. Only bad things came of it. Had to reflash. Let me know if you have better luck.
I'm pretty sure it failed because a lot of the stuff in framework.apk is stubbed closed source stuff.

Koush,
Have you looked at this post by Living_Sword?
I suggest you enter the following commands using adb, because its faster and reliable than telnet or any other method. If you do not have adb setup, read here, if you do, then just enter adb shell in the console while the phone is connected.
In simple words, you have to re-sign the framework-res.apk with your own key. You should know that you will loose all your data while doing this mod. Here are the steps,
1. Re-sign and re-upload all the .apk files in /system/app with your own key or the test-keys. The command used for signing is included in the readme file alongwith the signing jar here.
2. Take a backup of /system/framework/framework-res.apk. Now, you would want to edit some stuff in framework-res.apk, for that the easiest method is to rename the apk file to .jar/.zip, put in your own files(with same name as original png) and rename it back to .apk. You have to re-sign this apk with the same key like you did in the first step.
3 . Upload the apk file to /system/framework. The phone will hang, and in few secs it will most likely go back to the android robot screen.
4. Take out the battery, then do a data reset by going into recovery mode and pressing ALT+L to see the log text and then ALT+W to wipe out /data. Obviously, you will loose all your apps and settings and will have to re-activate the phone.
5. After the wipe is complete, press HOME + BACK to reboot. The phone should reboot normally now.
I know its a pain to loose all the data and apps, but this is the easiest method until we figure out something more elegant, and its required to be done only once. Also, there is no need to keep the png file size same. And in future, you will be able to replace the framework-res.apk without any hassles.
Also, since each stock app's icon is in its own apk, once you re-sign every apk in /system/app, you can easily replace their icons with your own.
Source: http://www.modmygphone.com/forums/showthread.php?p=16871#post16871

Ok, so I have successfully replaced framework-res.apk with my own build which includes custom icons and things like that. However, I am running into two problems:
1: I keep running out of room in my system folder. Everytime I replace framework-res.apk I am losing space somehow, eventually I have to do the mod rc30 update all over again to get my memory back so I can push this file over, where is this space going? Whats eating it up? Oh, and it isn't the file size growing, this will happen if I pull a file and directly try to push it back onto the phone.
2: I still don't know how to change the default color of the text. I assume it is in one of these xml files but I'm not sure, and I haven't found it yet. Could it be in /res/color/?
If anyone could help me on these two issues I would be so appreciative.
This is what I've done so far, see the status bar and the icons?
Stericson

Stericson said:
Koush,
Have you looked at this post by Living_Sword?
I suggest you enter the following commands using adb, because its faster and reliable than telnet or any other method. If you do not have adb setup, read here, if you do, then just enter adb shell in the console while the phone is connected.
In simple words, you have to re-sign the framework-res.apk with your own key. You should know that you will loose all your data while doing this mod. Here are the steps,
1. Re-sign and re-upload all the .apk files in /system/app with your own key or the test-keys. The command used for signing is included in the readme file alongwith the signing jar here.
2. Take a backup of /system/framework/framework-res.apk. Now, you would want to edit some stuff in framework-res.apk, for that the easiest method is to rename the apk file to .jar/.zip, put in your own files(with same name as original png) and rename it back to .apk. You have to re-sign this apk with the same key like you did in the first step.
3 . Upload the apk file to /system/framework. The phone will hang, and in few secs it will most likely go back to the android robot screen.
4. Take out the battery, then do a data reset by going into recovery mode and pressing ALT+L to see the log text and then ALT+W to wipe out /data. Obviously, you will loose all your apps and settings and will have to re-activate the phone.
5. After the wipe is complete, press HOME + BACK to reboot. The phone should reboot normally now.
I know its a pain to loose all the data and apps, but this is the easiest method until we figure out something more elegant, and its required to be done only once. Also, there is no need to keep the png file size same. And in future, you will be able to replace the framework-res.apk without any hassles.
Also, since each stock app's icon is in its own apk, once you re-sign every apk in /system/app, you can easily replace their icons with your own.
Source: http://www.modmygphone.com/forums/showthread.php?p=16871#post16871
Click to expand...
Click to collapse
framework-res.apk is just the resources. framework.apk contains the actual code used by every application in the system. Attempting to replace THAT file the result of the android build process will fail.
I think we're talking about two different files.

Oh yep, definetly we are...I thought you were talking about that but I figured you would clarify if you were indeed. Thanks.

so you guys are making progress on some themes... GOOD ****..

jzajzz said:
so you guys are making progress on some themes... GOOD ****..
Click to expand...
Click to collapse
Agreed. Once this process is mastered, and some polished themes, or a tool to make your own (or something) comes out, our G1's will look even sweeter.

jzajzz said:
so you guys are making progress on some themes... GOOD ****..
Click to expand...
Click to collapse
Well, I was making progress, but now my phone is bricked. Don't know how it happened. Was doing the same thing I've done over 20 30 times, suddenly started giving me problems, reflashe JF update and voila! bricked phone. So now I'm getting a new one sent to me and hoping that it comes pre-rc30. Sucks too because I am pretty sure I found out where the text color is set. Thats why I'm trying to get this to work under the emulator, but I can't get it to work. The dang emulator won't reboot or shutdown. So I can't see the changed made.

It sounds like it's too late to help now. But how was the phone bricked? Did it go into an infinite reboot cycle? Stay on the G1 screen?
Also, I assume you hadn't loaded the dev bootloader? That could have easily saved your phone from brickage

JesusFreke said:
It sounds like it's too late to help now. But how was the phone bricked? Did it go into an infinite reboot cycle? Stay on the G1 screen?
Also, I assume you hadn't loaded the dev bootloader? That could have easily saved your phone from brickage
Click to expand...
Click to collapse
My phone does have the dev bootloader on it. However, now it just stays on the boot splash screen and I can't do the update because it says the /dev file is gone! Can I reflash all of that and save my phone?
Btw, I actually think the entire folder /system is gone, because I can't abd with root, and when I did it in the update screen my system folder wasn't showing. So, I have no idea how this happened.
Is it possible to push that entire folder back on there and then recover or something?

Yes, you can reflash the recovery partition using the fastboot protocol, which the dev bootloader supports. There isn't a windows binary for it yet, but if you have a linux or mac handy, turn on the phone into bootloader mode, then plug in the USB cable. "Serial0" should change to "FASTBOOT". now you can use the fastboot binary on your computer to flash anything on the phone. You might try re-flashing the recovery image that's in my modified update. If that doesn't work, maybe try flashing the radio too.
If you have the dev bootloader, I'm almost positive your phone can be saved. Give me at IM if you want to talk about it.

I *think* the fastboot binary is in the sdk for linux/mac. I could be wrong though. There are copies of both floating around though, just ask if you need one.

I managed to repack framework-res.apk and resign all other packages without wiping. The problem is with the signatures in /data/system/packages.xml - they no longer match after resigning. The solution is to simply delete all <sigs> sections (and the <certs> within), and the PackageManager will automatically regenerate them as they are launched. I just now successfully booted, so can't say this is thoroughly tested, but I'll report back here if any problems crop up.

donniesmit said:
I managed to repack framework-res.apk and resign all other packages without wiping. The problem is with the signatures in /data/system/packages.xml - they no longer match after resigning. The solution is to simply delete all <sigs> sections (and the <certs> within), and the PackageManager will automatically regenerate them as they are launched. I just now successfully booted, so can't say this is thoroughly tested, but I'll report back here if any problems crop up.
Click to expand...
Click to collapse
A good check after doing something like this is to take a look at the call log, and actually receieve a call (call yourself from your home phone, or whatever). Both of these like to error out when messing around with resigning.

[Guide]Changing Kindle Wallpapers! [Obsolete]

I'M OUTDATED YO.
I gave Benjyp senior my awesome Kindle as an awesome Christmas present to my awesome dad from his awesome son so I will not be updating this guide any further!
As of now there is speculation that this guide DOES NOT WORK but I know there are many better alternatives to be found elsewhere!​
I'm just gonna get right down to it.
If you don't feel comfortable doing this, please don't!
blauciel said:
Good! One other thing, doing this caused my Kindle to lose all remembrance of all things signed in. I had to sign in to google and in to amazon again, including registering the Kindle again. Twice... :/
Click to expand...
Click to collapse
Here's what I did:
1. Locate your framework-res.apk file found at /system/framework/framework-res.apk
2. Copy onto your computer (I used root explorer to copy it to the "sdcard" and then jut plugged the Kindle in)
3. Download APK Mukti Tool
4. Place your framework-res.apk in the "place-apk-here-for-modding" folder
5. Run Script.bat
6. Press any key to continue
7. Set current project (25) (hint, choose framework-res.apk)
8. Extract apk (1)
9. Go to projects\framework-res.apk\res\drawable-mdpi and observe all of the JPEG image named "wallpaper_xx_xxxx"
10. Replace these files with either one image of your choosing or any other you may want
NOTE: I did not try removing or adding any images, only replacing, if you do let us know what happen!
11. Once you are done editing, go back to APK Multi Tool and "Zip apk" (3)
12. Select "System apk (retains signature)" (1)
13. Next, Zipalign apk (5)
14. Go back to the "place-apk-here-for-modding" folder and copy "unsignedframework-res.apk" elsewhere
15. Rename "unsignedframework-res.apk" to "framework-res.apk"
16. Copy this file back to /system/framework/, I copied the file to the sdcard via usb and used root explorer to copy into the folder (must mount r/w), but if you are more comfortable with ADB than I, just push it!
NOTE: I got a force close error around this point but nothing terrible happened! (I think!)
17. Change the permissions to rw-r--r--
18. Reboot!
19. Enjoy your new wallpapers!
*You are probably going to experience errors with commands not being recognized with the APK Multi Tool, you must add locations to the windows PATH (just google your error )*
Sorry for the exessive length, I was trying to be thorough!
*Edit*
This is helpful:
blauciel said:
Thank you very much! I got this to work with one slight hiccup and workaround:
Step 13 gave me an error "(Option 24)" and the unsignedframework-res.apk file disappeared. The workaround was to add:
step 12.5: Set current project (25) - Hint: select unsignedframework-res.apk
Then step 13 worked, no error, and the file did not disappear.
On what happened with the images I selected:
I left the very first image intact: wallpaper_01_2422 just in case it didn't like my images. I then replaced all the other images with other images of mine of the exact same filename. wallpaper_02_1953.jpg, wallpaper_03_6474.jpg and so on. I did add one new image, because their wallpaper_05_????.jpg is not there, I put my own in it's place. That image does not show. Apparently there is a filename index somewhere that specifies what images to show. Also, all the images are 840x1024, while the screen size is 600x1024. I'm not sure why the difference, as the images DO get cropped. Also, I accidentally forgot to resize one of my images and it was much larger than the display, so I only saw the center 600x1024. Lastly, my image image file sizes were about 20% of what they already had. So the original framework-res.apk file is 29.8Mb, while mine came out to ~12Mb
Bottom Line lessons learned:
1. There are 21 images, and without further changes, only 21 allowed.
2. The naming convention is "wallpaper_##_9999.jpg" where the ## is 01-04, 06-22. They skipped 05 for some reason. The 9999 is a number they designated, no apparent reason or pattern.
3. You must use the same filenames.
4. Your image can be any dimension, the image is centered and cropped for display.
5. If you want your entire image to show, crop them to 600x1024.
6. File size is unimportant.
7. Each time you turn off the screen, and it locks, the software picks the next image down the line. No shuffle or changing of the order. See the filename list below.
Full filename list:
wallpaper_01_2422.jpg
wallpaper_02_1953.jpg
wallpaper_03_6474.jpg
wallpaper_04_5588.jpg
wallpaper_06_6043.jpg
wallpaper_07_5751.jpg
wallpaper_08_1905.jpg
wallpaper_09_2283.jpg
wallpaper_10_5683.jpg
wallpaper_11_5335.jpg
wallpaper_12_5866.jpg
wallpaper_13_3664.jpg
wallpaper_14_6752.jpg
wallpaper_15_2429.jpg
wallpaper_16_5737.jpg
wallpaper_17_6712.jpg
wallpaper_18_3613.jpg
wallpaper_19_5507.jpg
wallpaper_20_6562.jpg
wallpaper_21_3622.jpg
wallpaper_22_6413.jpg
Click to expand...
Click to collapse

Nice work! It would be even better if someone created an app that did just that. However I'm pretty sure the custom rom devs are going to include that in their roms too.. again, good work because this will help speed up the process!

webmastertroi said:
Nice work! It would be even better if someone created an app that did just that. However I'm pretty sure the custom rom devs are going to include that in their roms too.. again, good work because this will help speed up the process!
Click to expand...
Click to collapse
kind of surprised we don't have any custom roms yet.

Don't do what I did, and delete a bunch of the wallpapers without replacing them. Should have replaced them all with one image. Stuck at bootlogo. Not sure what to do from here, but in all fairness, I knew it could happen.
Edit: Any advice, despite the fact that I did not follow the instructions that were made to be clear as day, would be appreciated. If nothing else, Ill send it back tomorrow.

xodlike said:
Don't do what I did, and delete a bunch of the wallpapers without replacing them. Should have replaced them all with one image. Stuck at bootlogo. Not sure what to do from here, but in all fairness, I knew it could happen.
Edit: Any advice, despite the fact that I did not follow the instructions that were made to be clear as day, would be appreciated. If nothing else, Ill send it back tomorrow.
Click to expand...
Click to collapse
Unbrick: http://forum.xda-developers.com/showthread.php?p=19552626
Sent from my SPH-D710 using xda premium

xodlike said:
Don't do what I did, and delete a bunch of the wallpapers without replacing them. Should have replaced them all with one image. Stuck at bootlogo. Not sure what to do from here, but in all fairness, I knew it could happen.
Edit: Any advice, despite the fact that I did not follow the instructions that were made to be clear as day, would be appreciated. If nothing else, Ill send it back tomorrow.
Click to expand...
Click to collapse
Oh no, that sucks! If you can get ADB running you can push a different framework-res.apk to the device, but I don't know how to do that. Does the Kindle have some sort of recovery mode??

Benjyp said:
Oh no, that sucks! If you can get ADB running you can push a different framework-res.apk to the device, but I don't know how to do that. Does the Kindle have some sort of recovery mode??
Click to expand...
Click to collapse
Fastboot
Sent from my SPH-D710 using xda premium

pyrostic said:
Fastboot
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I found this:
http://forum.xda-developers.com/showthread.php?p=19552898
Hope it helps!

Thank you very much! I got this to work with one slight hiccup and workaround:
Step 13 gave me an error "(Option 24)" and the unsignedframework-res.apk file disappeared. The workaround was to add:
step 12.5: Set current project (25) - Hint: select unsignedframework-res.apk
Then step 13 worked, no error, and the file did not disappear.
On what happened with the images I selected:
I left the very first image intact: wallpaper_01_2422 just in case it didn't like my images. I then replaced all the other images with other images of mine of the exact same filename. wallpaper_02_1953.jpg, wallpaper_03_6474.jpg and so on. I did add one new image, because their wallpaper_05_????.jpg is not there, I put my own in it's place. That image does not show. Apparently there is a filename index somewhere that specifies what images to show. Also, all the images are 840x1024, while the screen size is 600x1024. I'm not sure why the difference, as the images DO get cropped. Also, I accidentally forgot to resize one of my images and it was much larger than the display, so I only saw the center 600x1024. Lastly, my image image file sizes were about 20% of what they already had. So the original framework-res.apk file is 29.8Mb, while mine came out to ~12Mb
Bottom Line lessons learned:
1. There are 21 images, and without further changes, only 21 allowed.
2. The naming convention is "wallpaper_##_9999.jpg" where the ## is 01-04, 06-22. They skipped 05 for some reason. The 9999 is a number they designated, no apparent reason or pattern.
3. You must use the same filenames.
4. Your image can be any dimension, the image is centered and cropped for display.
5. If you want your entire image to show, crop them to 600x1024.
6. File size is unimportant.
7. Each time you turn off the screen, and it locks, the software picks the next image down the line. No shuffle or changing of the order. See the filename list below.
Full filename list:
wallpaper_01_2422.jpg
wallpaper_02_1953.jpg
wallpaper_03_6474.jpg
wallpaper_04_5588.jpg
wallpaper_06_6043.jpg
wallpaper_07_5751.jpg
wallpaper_08_1905.jpg
wallpaper_09_2283.jpg
wallpaper_10_5683.jpg
wallpaper_11_5335.jpg
wallpaper_12_5866.jpg
wallpaper_13_3664.jpg
wallpaper_14_6752.jpg
wallpaper_15_2429.jpg
wallpaper_16_5737.jpg
wallpaper_17_6712.jpg
wallpaper_18_3613.jpg
wallpaper_19_5507.jpg
wallpaper_20_6562.jpg
wallpaper_21_3622.jpg
wallpaper_22_6413.jpg

blauciel said:
Thank you very much! I got this to work with one slight hiccup and workaround:
Step 13 gave me an error "(Option 24)" and the unsignedframework-res.apk file disappeared. The workaround was to add:
step 12.5: Set current project (25) - Hint: select unsignedframework-res.apk
Then step 13 worked, no error, and the file did not disappear.
On what happened with the images I selected:
I left the very first image intact: wallpaper_01_2422 just in case it didn't like my images. I then replaced all the other images with other images of mine of the exact same filename. wallpaper_02_1953.jpg, wallpaper_03_6474.jpg and so on. I did add one new image, because their wallpaper_05_????.jpg is not there, I put my own in it's place. That image does not show. Apparently there is a filename index somewhere that specifies what images to show. Also, all the images are 840x1024, while the screen size is 600x1024. I'm not sure why the difference, as the images DO get cropped. Also, I accidentally forgot to resize one of my images and it was much larger than the display, so I only saw the center 600x1024. Lastly, my image image file sizes were about 20% of what they already had. So the original framework-res.apk file is 29.8Mb, while mine came out to ~12Mb
Bottom Line lessons learned:
1. There are 21 images, and without further changes, only 21 allowed.
2. The naming convention is "wallpaper_##_9999.jpg" where the ## is 01-04, 06-22. They skipped 05 for some reason. The 9999 is a number they designated, no apparent reason or pattern.
3. You must use the same filenames.
4. Your image can be any dimension, the image is centered and cropped for display.
5. If you want your entire image to show, crop them to 600x1024.
6. File size is unimportant.
7. Each time you turn off the screen, and it locks, the software picks the next image down the line. No shuffle or changing of the order. See the filename list below.
Full filename list:
wallpaper_01_2422.jpg
wallpaper_02_1953.jpg
wallpaper_03_6474.jpg
wallpaper_04_5588.jpg
wallpaper_06_6043.jpg
wallpaper_07_5751.jpg
wallpaper_08_1905.jpg
wallpaper_09_2283.jpg
wallpaper_10_5683.jpg
wallpaper_11_5335.jpg
wallpaper_12_5866.jpg
wallpaper_13_3664.jpg
wallpaper_14_6752.jpg
wallpaper_15_2429.jpg
wallpaper_16_5737.jpg
wallpaper_17_6712.jpg
wallpaper_18_3613.jpg
wallpaper_19_5507.jpg
wallpaper_20_6562.jpg
wallpaper_21_3622.jpg
wallpaper_22_6413.jpg
Click to expand...
Click to collapse
Thanks! That was very helpful! I was concerned about the substantial change in the overall size of the .apk but I didn't even think about the image sizes being the cause.

Good! One other thing, doing this caused my Kindle to lose all remembrance of all things signed in. I had to sign in to google and in to amazon again, including registering the Kindle again. Twice... :/
//Tapatalk.KindleFire//
---------- Post added at 08:12 PM ---------- Previous post was at 07:45 PM ----------
Sorry for the double post, but I noticed after a text search through the unpacked framework-res.apk that each of the wallpapers is listed in this form:
Name: res/drawable-mdpi/wallpaper_14_6752.jpg
SHA1-Digest: w4mPNGSdoaKDPQW9Jf6HI7Jpegk=
Google reveals that SHA1-Digest is similar to an MD5 code that basically verifies the contents of the file. It would seem that simply changing or editing these entries would limit or add more wallpapers.

So are you saying that we have to have 21 wallpapers no matter what or it will not work? Guess if we want just one wallpaper then we have to put the same one on named the different ways?
Sent from my EVO with Tapatalk

You can put 21 copies of the same image though I gather you can delete all but one and replace that one with one you like. I just replaced all of them with cropped/resized images from my own photography collection (and one of the erupting volcano in Iceland).
//Tapatalk.EVO3D//

So I tried to replace all the wallpapers with just a single wallpaper..it didn't work. It put my device into a bootloop that I couldn't get out of. I had to use parts of the Unbrick thread to get my device to boot again after pushing my original framework-res.apk back to the device.
Trying a few other options now. Anyone know how to sign the apk after putting just a single wallpaper in it? I think the signature is what caused it to get all screwed up.
-Eric
So I got it working by replacing all the wallpapers with a single image but named the same way as the other 21 wallpapers. I still had to go back and get temp root again through adb and set the permissions from adb because as soon as I copied the apk to the folder the device reset on me and started boot looping. It is working fine now but still would be nice to replace with just a single image to reduce the size of the apk, or better yet once we can just do it on the device like all the other devices.

This IS a rather silly implementation that we have to work around.
//Tapatalk.KindleFire//

Someone posted a different solution in the General forum that I have not yet attempted. Had to do with changing the permissions on a package somewhere as I recall.

This method does work with 6.2. I tried it with another APK tool and bricked my Kindle. I think the problem is the other one doesn't "sign" the apk. Putting the right framework-res.apk back in place fixed it.

I had trouble with the GUI interface and changing out the framework.apk out. I played around with adb and I figured out how to due it via command prompt:
You have to root again so that "adb remount" works
Locate android-sdk/platform-tools
Move the new "framework.apk" a new folder to C:\framework
Insert commands without " "
"adb kill-server"
"adb devices" (isn't necessary but I like to make sure that my device is connected)
"adb remount" (changes system files to rewrite)
"adb push /framework/framework-res.apk /system/framework/framework-res.apk"
Then restart Kindle Fire and it'll work! I don't know if this will work for others, but it worked for me after hours of playing around

It works great ! thanks for this guide, instead of making all different wallpaper, I made it all the same wallpaper but of course with different name each. Now my kindle shows 1 image only haha I guess I have to settle with this lol

easier mod
easier mod without bricking your device:
http://droidpirate.com/2011/11/20/amazon-kindle-fire-how-to-change-wallpapers/

[Q] Custom Boot Animation (Black Screening)

Hey everyone, it's my first time creating a custom boot animation and I've run into some trouble. After placing my animation on my device whenever it should play I just get a black screen. With any other animation, like one from the internet, it works fine. I've tried changing the resolution of the frames and the settings in desc.txt to my phone's native resolution (540x960), but to no avail. I've included the .zip file for it in my post. Can anyone tell me what I've done wrong?
EDIT: My phone is not rooted, by the way.

Try this...fixed and it works for me now

Thanks! That seem to have fixed it, but there is a white flash whenever part2 loops, and a few black flashes/glitches in between parts. Is there any way to fix this?
Also, what exactly did you do to it?

No, seriously, how did you do that? D:

Answer maybe
Im still pretty new to this too but I had an issue with this the first time I repacked an animation. (the Paint one, cuz i wasnt on HTC)
When I rezipped it the sanim.zip refused to work. After looking at every other boot animation file I had, and learning a lot, i think, i noticed the zip files were all set to store and not compress the files. so when you zip a file, however you do it, set it to "no compression" or "store" on the compression settings. otherwise, i think what happens is your phone has to decompress every image and by the time it would be done with that youve booted.
I used 7zip to do it and it was pretty straightforward.

customizing boot anamation problem

ive searched and where i found plenty people wit custom boot anamation problem, none were exactly mine. Im trying to edit the s2 boot anamation. I opened the zip and put each frame into paint and made my changes. The anamation has 2 parts. Part0 and part1. I only edited part1. When i put it all back together and install it will only play part0. It wont continue on to part1 as usual. Whats the deal?

I've got it. 3 F***ing hours investigating and finally got it. I'm posting this here for anyone that may run into the same situation. Maybe save someone some trouble. Wish I could hit my own thanks button...lol
All the files in the boot anamations are uncompressed. Even though they are .zip file they still arnt commpressed. Whenever I edited the frames and replaced them back into the bootanamation.zip they would be compressed by 19% or so. I assumed the phone cant read a compressed file on start-up. Everything's working perfect now. Finally have my own "TRUE" custom boot anamation. Just create your zip file with "no compression" Your welcome

Boot Animation Creation Help Required

I am not sure why I can't figure out how to make this work, so I am pleading for assistance. I am trying to take the standard Nexus boot animation and make it work for the Moto X. I've already done all the work to the files (cropped them down to our screen size, and removed the ones that were unnecessary). I have included a link to the files I put together, if someone would be so kind as to create the boot animation from them I would really appreciate it!
Edit: Got it to work! Thanks for the help nate! Instead of the files I have now put in place the boot animation and the CLogo I paired together. If you didn't know any better you would think your phone's a Nexus.
https://drive.google.com/folderview?id=0BwiMelVh_Za-WVRsTUdxbUZXUkU&usp=sharing
Thanks!

I have put a compressed folder in the download link called "files.zip" to make it easier to download all the images. Thanks again to anyone willing to help.

I don't feel like making you one... but here is one that I've made a while back that's the same.
Here you go. Tell me how that works.
Edit: Don't flash this. You need to manually place it in /system/media/ and set the permissions correctly.

I managed to finally make my own version work. I used the desc.txt from the file you uploaded, modded it slightly to match the resolution of the images I had cropped and it worked! No idea why my desc.txt was screwed up before. I paired it with a "Google" clogo on boot, and it's seamless. I'll be posting my results to share here after work today.