Database Develop

Kaiser Splash Screen Repository [Pictures & Files]

Splash Screen (Boot) File Repository.
I Thought I would start a thread for the splash screens that people are using or those that people have designed for others.
Essentials for creating the splash screens are:
An art program to create the picture that you want, please make sure that your image is 240x320 pixels 24bit colour depth and save it as a .bmp
Follow the instructions in this post by pof (not exactly clear on the HTC rom tool section, just pick anything for the fields in the program and load the correct splash.nbh file by clicking the ... to the right of the splash1 field)
Here are a couple of pictures of some splash screens to get started with.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Put one of these files in the same directory as KaiserCustomRUUv1 and then run the program it will ask you questions make sure you answer yes to them all and then patch the phone. Once done it will automatically reboot your phone and show you the new splash screen.
Russ
Please make sure you edit your original post to add more pictures & files to save having lots of pages per person.

Is this for the first screen where it says 'smart mobility' or is for the animated HTC screen? If the latter, how do you make (which format) & upload an animated one?

I have no idea on the animated one but I am only guessing when I say that its the smart mobility one at the very beginning when you power on the phone on.
As for the animated one if it is the windows start-up then that is a 320x320 pixel 24 bit .png file called welcomehead.96.png on my T-Mobile UK phone so I would suggest starting there in your search for replacing the animated one (if its a .gif then you are ok).
Russ

Thanks mate!!
Awesome stuff
Here's my appreciation in the form of some Anime fan service shots
If I knock up any more I'll share them

There are also some animated ones in this thread.

my theme
great!
Post your splash

I like the easy way.
Just make your picture 240x320, save as welcomehead.96.png and copy to \windows\ on the Kaiser.
Bob's your Uncle.

I've always liked this one, it goes well with the Stock ROM's HTC logo when booting into Black. I believe that the welcomehead png's need to be 320 x320 to cover things when booting in landscape. These welcomehead splashes are so easy to just drop into the windows directory, no rom burning needed, getting the original file's read only attribute turned off is the only hurdle. I used resco file explorer to do it.

Due to the limitation of 4 images per post I guess we are going to have to make more posts per person.
Here are a couple of windows based ones I made. I actually have the carbon one on mine at the moment and it looks alot better on the device.
The animated gif does not work on my t-mobile even adding the registry key of hklm/software/htc/startupanimation/giffile and pointing it to the relevant named file so I guess thats only for those who have changed their roms (unless your on t-mobile rom and its working please correct me if i'm wrong)
Russ
at&t_deathstar.jpg created by RemE

A little contribution for the third splash screen...
Here is my work :
All in .png format, 240x320 pix, rename it welcomehead.96.png and paste it in the windows directory.
I've tried to keep the TyTN II'spirit ~smart'n'pro !
;-)

zachto said:
I like the easy way.
Just make your picture 240x320, save as welcomehead.96.png and copy to \windows\ on the Kaiser.
Bob's your Uncle.
Click to expand...
Click to collapse
I did as you sugested but it does not work, I created a new file put it in the windows directory, now i have two files there by the same name, I try to delete the original one but i get an error its a ROM file can not be deleted, and when I start my device the original still boots up instead of the new one, any sugestions to do it the easy way ?

My work....

continue...

arimus said:
I did as you sugested but it does not work, I created a new file put it in the windows directory, now i have two files there by the same name, I try to delete the original one but i get an error its a ROM file can not be deleted, and when I start my device the original still boots up instead of the new one, any sugestions to do it the easy way ?
Click to expand...
Click to collapse
You can't have two file with the same name so something must be different (unless the 2nd one has a (2). I found that I had to use resco file explorer to change the original welcomehead file's attributes and remove the "read-only" flag. Then I was able to copy over it with my own splash .png files.
Also the welcomehead files "should" be 320x320 to give you a correct image if booting in landscape but I never boot this way and I imagine others don't either.

Hey Deathace, do you have this screen in a plain version with no logos, just the swirl?

RemE: here you go.
Russ

Perfect Thanks!

Deathace said:
RemE: here you go.
Russ
Click to expand...
Click to collapse
did you make those? those are sweet

welcomehead.96 read only
I got Resco File Explorer, I went to the windows directory and changed welcomehead.96.png to read only, but it doesn't stick. It immediately reverts back to read only. So, I can't copy the new file in.

ChaoticPi said:
I got Resco File Explorer, I went to the windows directory and changed welcomehead.96.png to read only, but it doesn't stick. It immediately reverts back to read only. So, I can't copy the new file in.
Click to expand...
Click to collapse
copy the new file from your PC to the 'My Document' folder on the Tilt. Then on Tilt, copy (or move) the file from the "MY Docs" folder to the \windows directory. You get a prompt ot overwrite, say yes to that, then you will get a second warning about the file being replaced is a ROM file, say OK to this too....

[Ref Tutorial] Changing the boot animation screen on google builds

Ok, so I know a lot of you are looking for a simple process to get the animation screen changed on non-hero/htc builds. Well, we can do it.
First, animated gif images dont work for google builds as of yet (at least that I've heard of), so scrap that idea right now.
The google boot animation is a combination of two images:
android-logo-mask.png
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and
android-logo-shine.png
(images taken from Dude's 1.3RC1)
Now, the way this works is as so:
android-logo-shine is the color in the background. it scrolls across repeatedly, and that white stripe on there makes it look like it's got a light glimmer on it. android-logo-mask is the actual image. When it's all put together, it looks something like this (imagine the background color scrolling across as your phone is loading)
now, I've played with this some and my current logo is 256x265. The logo cant really be any wider than 256 pixels or it will crop off the edges of the screen. The shine has to match the image in height, but the width is fine at 512.
there are multiple methods for doing this. first is the old-school method for people who like to do things the old fashioned way.
So heres what you do: (VIDEO TUTORIAL HERE: http://www.youtube.com/watch?v=QMrn3n_ayHI)
1.)take your favorite rom and favorite unzip program (i use winrar). open the rom up and navigate as follows:
system--->framework
2.)you will see a file called framework-res.apk. open this file (again, winrar works good for this).
3.)open the assets folder, then open the images folder.
4.)you will see the two png files i mentioned above. extract them both to your desktop, but DO NOT CLOSE THE FILE BROWSER (unless you want to navigate to that folder all over again).
5.)now comes the fun part: editing your images. this is where it gets a little more complex:
-on the mask, any area you want the scrolling color to show up must be TRANSPARENT. You can put just about any text or image on there that you want, but the scrolling color from the shine image will not show through without the transparency.
-the shine image can be any colors you want, so feel free to play around with some schemes until you come up with something you like.
6.)after you're done and you've saved both images the way you want, put them back in the same folder you took them out of (framework-res.apk\assets\images)
7.)once you've put them back in, you have to resign the whole update. this is a very easy process that is laid out for you in this thread that stericson put together.
8.)throw the newly signed update.zip on your sd card, boot into recovery mode, flash, and reboot. you'll be happy with the result.
Just to give you guys a little taste, heres what my FIRST design looked like:
(just use your imagination to picture the red/white background scrolling across the android and lettering)
A couple things to point out for you artists: the "shorty's android" and the android outline are the only transparent parts, so they will show the scrolling color. The "1.5 customized" and android eyes are solid colors, so they dont scroll/change/nothing.
Now, at this point in time, I havent found any way of adding music like the htc/hero builds can do. If anyone figures that out, let me know and I can add it to this tutorial, with credit to you, of course.
Enjoy your spiffy new boot animations guys, and please post some screens here so we can all admire your work.
New addition guys: for those having trouble with the directions, I made a video tutorial to help out! Check it out here:
http://www.youtube.com/watch?v=QMrn3n_ayHI
Next, and probably the easiest method of doing this is to use METAMORPH! If you dont know what metamorph is, well, you're behind the times and need to check out this thread:
http://forum.xda-developers.com/showthread.php?t=591329
If you are familiar with using metamorph to at least install themes on your device, then you're set.
So how do you do it using metamorph? Simple.
First, you're going to create a brand new folder and title it "bootanimation" or whatever you choose.
Now, inside that folder, you're going to have several files in order for this to work right.
1. The folder stack where the boot animation will go (explained below)
2. the .thm OR .xml file depending on which version of metamorph you have. If you're not sure: free version uses .thm files. Pro/Donate version uses xml.
Now, creating these things is SIMPLE. The folder stack is going to be the same every time for boot animations. In your folder that you have already created and should be staring lovingly at, create a new folder called "framework-res". THIS FOLDER NAME MUST BE EXACT, as must all the ones that follow. open the folder you just made and create a new one inside it called "assets". Open the assets folder and create a new folder inside it called "images". I know it seems tedious, but thats the LAST folder you have to create, I promise. The last step here is to open the images folder and place inside it your android-logo-mask.png and android-logo-shine.png files. after you've done that, move back out to the original folder and get ready to create your .thm or .xml file.
Now, .thm files for bootanimations are simple. open notepad and put in the following:
any
any
framework-res.apk
/system/framework/
Then save the file (NOT AS A .TXT FILE) as bootanimation.thm
Now, when saving the file as indicated above, the name of the .thm file MUST be the same as the name of the folder you originally created. So if your folder, and thus your final zip file, is named purplebuttmonkey, then your .thm file must be named purplebuttmonkey.thm. Simple enough?
Now, creating the xml files is a bit more complex for the average user and certainly a bit much to put into text, so I'll simply defer you to the master, Stericson himself, in a nifty video he made to educate you how to do it:
http://www.youtube.com/watch?v=Mq4AuHKzNFo
So fast forwarding:
Once you've created your folder stack, your .thm file or .xml file and are ready to move on, all thats left to do is to create your zip file! Guess what, these dont have to be signed either! Hooray! So open your favorite zip program (again, I recommend winrar) and create a zip file out of the original folder you made. After that, put it on your phone, load up metamorph and go to town!
Also, metamorph is nice because it eliminates having to re-sign everything every time you want a new animation. All you have to do is replace the two png files in the folder stack you made, re-zip it and morph it once its on your phone.
NEW:
Hitchhiker's Guide To the Galaxy Boot Animation: http://www.4shared.com/file/XWXh6pT6/HHGBoot.html
YOU MUST HAVE METAMORPH. For right now (4/25), only the pro version will work. Stericson is updating the free version to XML on the 30th. After that, this will work for everyone!
NEW ADDITION: Burlyskink made an excellent html applet for testing out your designs so you no longer have to flash an update in order to see what the finished product looks like! You can find this little gem here. Many thanks to Burlyskink for this!

Many thanks to noonski and mikey for helping get this out of the dogpile. Show your mods some love guys!

Finally!!!
Nice work bro!
I'm am that guy who goes through much trouble w/ a lot of these upgrades mods and graphic tweaks do to the fact that im a visual learner not so much the literal. Do to minimal knowledge on the graphic's aspect, i need a first hand basis tutorial like this one to successfully complete these mods!! \
ThankS a million and Hope to start seeing many more VIDEO TUTORIALS like this around, touching on different area's of graphic designing/software modding for the G1..
Thanks again to all dev's/themers(HEAVY HITTERS!): Manup456("headcrack"), Moonsspoon, Stericson, DudeofLife, koush, Tehseano, Haykuro, Cyanogen, Twisted, Jwange, Diaztradenic, Doubleokneegro, Jborque, MarcusMaximus04, LucidRem, JAC, And of course last but definitely not least The Godfather, The man/The Myth JESUSFREKE!!! and for anyone that i did not mention you know who you are thanks a million!!

I've added these two png's to my update.zip\framework\framework-res.apk\assets\images\
I've been able to reboot with them in the apk now, but it's just a black/blank screen. Does anyone see any reason why they wouldn't be able to be merged into the apk?
I've gotten a log but at the moment, I'm not seeing anything very telling....

you did sign the file and reflash the update, correct? cause I just downloaded your two png files, loaded, signed, flashed and it works just fine for me.

heya,
i have tried to edit JFv1.51 CRB43-us but when i go into the folder i dont not see a .apk file i see .cramsf is there a way i can do it on these themes???

OP,
Mind sharing your red/white background?
EDIT: Just tried this. Edited my own files, repacked into framework-res.apk under assets & images. Resigned the update & all I got was a black screen. Does the framework-re.apk have to be pulled out of the update & edited, then resigned? Or can it just be edited from within the update.zip itself? I am using 7zip if that helps
EDIT2: Just tried pulling the framework-res.apk to edit the images but it didn't work. I placed the original images back in & that worked. I don't get it. The files are the same dimensions. But my images were bigger than the original as far as bytes go. I don't know if that has anything to do with it. I don't know how to get them any smaller. I tried pnggauntlet but it didn't seem to work. O well I'll stick with the stock stuff but continue playing with it till I get it

Beast84 said:
OP,
Mind sharing your red/white background?
EDIT: Just tried this. Edited my own files, repacked into framework-res.apk under assets & images. Resigned the update & all I got was a black screen. Does the framework-re.apk have to be pulled out of the update & edited, then resigned? Or can it just be edited from within the update.zip itself? I am using 7zip if that helps
EDIT2: Just tried pulling the framework-res.apk to edit the images but it didn't work. I placed the original images back in & that worked. I don't get it. The files are the same dimensions. But my images were bigger than the original as far as bytes go. I don't know if that has anything to do with it. I don't know how to get them any smaller. I tried pnggauntlet but it didn't seem to work. O well I'll stick with the stock stuff but continue playing with it till I get it
Click to expand...
Click to collapse
I dont have the original red/white because i'm using a much different background now. the easiest thing i can recommend would be to open the original shine image with photoshop, go image>adjustments>hue/saturation and drag the hue slider until you achieve the desired color. Oh yeah, and edit the image height to match your mask image.
As far as the other two problems, you can do it from directly within the zip. watch the video tutorial at the bottom of the OP, shows you exactly how to do it step by step.

Thanks for the tutorial Kusotare,just thought I would add that I use 320 x 480 images like Dude/Manup did in his 1.1 and 1.2 builds and they dont cut off the sides at all.Both of my themes use 320 x 480 boot animations if anyone wants to grab one as a template feel free they are in my signature.

kusotare said:
you did sign the file and reflash the update, correct? cause I just downloaded your two png files, loaded, signed, flashed and it works just fine for me.
Click to expand...
Click to collapse
Yep, I can include the two pngs to my update.zip/resign/flash, and then I just get a black screen now instead...tried fixing permissions/chmod'ing the file as well....still just getting a blank screen after rebooting.

kusotare said:
I dont have the original red/white because i'm using a much different background now. the easiest thing i can recommend would be to open the original shine image with photoshop, go image>adjustments>hue/saturation and drag the hue slider until you achieve the desired color. Oh yeah, and edit the image height to match your mask image.
As far as the other two problems, you can do it from directly within the zip. watch the video tutorial at the bottom of the OP, shows you exactly how to do it step by step.
Click to expand...
Click to collapse
I did it exactly how it was done in the video & still I get a black screen. The phone boots up fine but no animation

Beast84 said:
I did it exactly how it was done in the video & still I get a black screen. The phone boots up fine but no animation
Click to expand...
Click to collapse
Try doing it through winrar. I've had problems with 7zip in the past, which is why I use winrar to do it.

i did this through 7zip. you can modify a whole update (for example, you love a theme but hate the vanity boot screens authors sometimes force upon you) by bringing up the context menu (right click) on the update.zip, then 7-zip>open, after that, navigate to system/framework, and at framework-res.apk just right click again and select "Open inside", and then navigate to assets, pull the two files to your desktop, edit them however you want (or if you already have your own just skip pulling them out), and then just pull the files back to the window and close, it's going to ask you if you want to save, just say yes or ok, and that's it, the update is all good to go (no need to re-sign or anything, i can confirm it works that way)

I've used WinRAR and 7z, no dice.

Threw this together to test.

Thanks for that, kusotare!
I used an adb-based approach:
1.) I pulled the framework-res.apk from /system/framework via adb
2.) then I put my modified PNGs (attached) into it
3.) I wanted to adb push framework-res.apk back onto /system/framework, but there was no space left on device.
4.) so I created a symlink (ln -s /system/sd/framework-res.apk /system/framework/framework-res.apk) to my Apps2SD partition.
5.) awesomely, it worked on the first try.
Edit: There is some kind of error with the scrolling background, it's maybe too big. Also, the blue doesn't look as good on the G1 screen as on my laptop. Firmware Information: JF 1.51 EU, 62.505.20.17U_2.22.19.26I, 2.6.27-00392-g8312baf [email protected] #1 CRB43
Edit: Okay, apparently, using Apps2SD for this is not a good idea. It can get you looped. However, it's easy to use adb to get out of it again by removing the symlink and repushing the original framework-res.apk . There is an even better solution for everyone with the current Google Maps from the Market - just erase the default /system/app/Maps.apk which is ignored anyway (according to adb logcat).
I swapped the splash out 5+ times now, and the phone boots up reliably. There is a very small possibilty of problems while using the phone, going to bed now and exploring that tomorrow. (It's 4:11)

Autarkis said:
Thanks for that, kusotare!
I used an adb-based approach:
1.) I pulled the framework-res.apk from /system/framework via adb
2.) then I put my modified PNGs (attached) into it
3.) I wanted to adb push framework-res.apk back onto /system/framework, but there was no space left on device.
4.) so I created a symlink (ln -s /system/sd/framework-res.apk /system/framework/framework-res.apk) to my Apps2SD partition.
5.) awesomely, it worked on the first try.
Edit: There is some kind of error with the scrolling background, it's maybe too big. Also, the blue doesn't look as good on the G1 screen as on my laptop. Firmware Information: JF 1.51 EU, 62.505.20.17U_2.22.19.26I, 2.6.27-00392-g8312baf [email protected] #1 CRB43
Edit: Okay, apparently, using Apps2SD for this is not a good idea. It can get you looped. However, it's easy to use adb to get out of it again by removing the symlink and repushing the original framework-res.apk . There is an even better solution for everyone with the current Google Maps from the Market - just erase the default /system/app/Maps.apk which is ignored anyway (according to adb logcat).
I swapped the splash out 5+ times now, and the phone boots up reliably. There is a very small possibilty of problems while using the phone, going to bed now and exploring that tomorrow. (It's 4:11)
Click to expand...
Click to collapse
Yeah, I tried the ADB version when I first started, thinking "you know, pushing the framework-res would certainly be much easier than manually repacking and resigning the whole update". Then I ran into the same problems you did and decided that the method I eventually settled on and posted here was going to be much easier for most people than trying to solve the million adb-how-to questions that would eventually come up. Glad you got the adb method working well though.

Thanks for confirming that, kusotare!
In anticipation of the adb-who-what questions you mentioned, let me state it for all to see:
First: All adb questions are answered in the forum. Use search, or Google. I heard they have this nifty search engine. I don't know where it'll get them eventually, but for the moment you can find pretty much everything using Google.
Second: I don't support adb - I love it!

Custom
I was bored and decided to make an electric version. I'll fool around with it with some newer ideas later.
As usual... open framework-res.apk, drop+replace in assets/images, sign.

I'm beginning to think that it's something that Paint Dot Net does, because I can use the png's in the first image and they work perfectly, as soon as I edit the mask or the shine not changing the name or size by too much it craps out on me (it updates, but just goes to a black screen for the animation)...
Anyone doing this with pdn, or are you guys all using GIMP/Adobe?
Paint Dot Net users: do not save with 32 bit, do not allow it to choose for you or it won't work for you. Much aggravation dispelled now...

Honeycomb Boot Animation

This is Honeycomb Official Boot Animation
Instructions (rooted users):
1. Download the bootanimation.zip file to your SD card
2. Open Root Explorer and copy the file to /data/local
3. Rename file to bootanimation.zip (if the name is NOT already bootanimation.zip)
4. Reboot your device and enjoy your new boot animation
I attach 2 files. First one is original Xoom's boot animation and second one is edited resolution in to g tab
Note - Screen may be blank if bootanimation.zip doesn't work but the device SHOULD still boot up properly
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to "deepowder2012" for this video

ndgayan said:
This is Honeycomb Official Boot Animation
Click to expand...
Click to collapse
How would one go about installing this? Flash the zip in CMR?

sumdumdude said:
How would one go about installing this? Flash the zip in CMR?
Click to expand...
Click to collapse
Some instructions are different depending on the device you want to install it on but these instructions seem to work well for me on most of the phones and stuff I've used. There are other instructions and other ways of doing this so if you don't have Root Explorer installed check around.
This is just a copy of the instructions I use...I don't remember where I found them...
Instructions (rooted users):
1. Download the bootanimation.zip file to your SD card
2. Open Root Explorer and copy the file to /data/local
3. Rename file to bootanimation.zip (if the name is NOT already bootanimation.zip)
4. Reboot your device and enjoy your new boot animation
Note - Screen may be blank if bootanimation.zip doesn't work but the device SHOULD still boot up properly

Is this the same animation shown at CES? The glowing honeycomb wipe?

Beck221 said:
Some instructions are different depending on the device you want to install it on but these instructions seem to work well for me on most of the phones and stuff I've used. There are other instructions and other ways of doing this so if you don't have Root Explorer installed check around.
This is just a copy of the instructions I use...I don't remember where I found them...
Instructions (rooted users):
1. Download the bootanimation.zip file to your SD card
2. Open Root Explorer and copy the file to /data/local
3. Rename file to bootanimation.zip (if the name is NOT already bootanimation.zip)
4. Reboot your device and enjoy your new boot animation
Note - Screen may be blank if bootanimation.zip doesn't work but the device SHOULD still boot up properly
Click to expand...
Click to collapse
Awesome. Can anyone confirm this works on the G-Tab Vegan/TNT Lite ROMs?

rrgreentree said:
Awesome. Can anyone confirm this works on the G-Tab Vegan/TNT Lite ROMs?
Click to expand...
Click to collapse
It's a standard bootanimation - it should work on any Android device.
However, it's set to use a high screen resolution - you might want to open the zip and update the settings to be used for a 1024x600 screen.

roebeet said:
It's a standard bootanimation - it should work on any Android device.
However, it's set to use a high screen resolution - you might want to open the zip and update the settings to be used for a 1024x600 screen.
Click to expand...
Click to collapse
Looks fantastic on my GTab; changes the resolution per Roebeet!

roebeet said:
It's a standard bootanimation - it should work on any Android device.
However, it's set to use a high screen resolution - you might want to open the zip and update the settings to be used for a 1024x600 screen.
Click to expand...
Click to collapse
How does one go about doing that? Is it the "desc.txt" file that we'd change?

jpmi23 said:
How does one go about doing that? Is it the "desc.txt" file that we'd change?
Click to expand...
Click to collapse
Yes.... change the resolution settings in that file... save it and when you reboot the animation looks soooooooooo much better!

Video: http://bit.ly/frXeeZ

GTablet said:
Yes.... change the resolution settings in that file... save it and when you reboot the animation looks soooooooooo much better!
Click to expand...
Click to collapse
I changed desc.txt from:
1408 880 24
p 0 0 part0
to:
1024 600 24
p 0 0 part0
...then dropped the file bootanimation.zip into /logodata using rootexplorer (renamed the original file first) and changed the permissions to match the original file.
On boot, it shows the first of the honeycomb images, but then stays on that - no animation. Am I missing something in the desc.txt file?
Thanks...

That's strange. The only thing I changed was 1408 to 1024, and 880 to 600. You saw my video. Not sure what that's about.
Also, I added the bootanimation.zip to the /logodata, /system/media, and /data/local. Maybe that has something to do with it? I only did that because adding it to /logodata alone didn't do anything.

jpmi23 said:
That's strange. The only thing I changed was 1408 to 1024, and 880 to 600. You saw my video. Not sure what that's about.
Also, I added the bootanimation.zip to the /logodata, /system/media, and /data/local. Maybe that has something to do with it? I only did that because adding it to /logodata alone didn't do anything.
Click to expand...
Click to collapse
I have had to put any new boot animation into both /media and /logodata to get them to work. Any chance someone can link a resolution edited bootanimation.zip? I wont be anywhere near my PC to edit the file for a few days.
Oh and thanks for the video jpmi23, very cool.

Thanks for the suggestion but no dice - I copied the bootanimation.zip file to the other two directories & still no animation. Not sure what's up with that. I'm running TNTLite FWIW, don't see how that would affect it. Oh well... I'll futz with it some more in my spare time...

Mantara said:
I have had to put any new boot animation into both /media and /logodata to get them to work. Any chance someone can link a resolution edited bootanimation.zip? I wont be anywhere near my PC to edit the file for a few days.
Oh and thanks for the video jpmi23, very cool.
Click to expand...
Click to collapse
http://dl.dropbox.com/u/19671888/bootanimation.zip
No problem.

Wow - got it working, thanks... I copied the file down from your dropbox link - the desc.txt file looked the same.
I copied it into /logodata, still just one frame, no animation. I copied it into /system/media, and /data/local and overwrote the file I had originally copied there...
- and bingo! animation!
Not sure why it wasn't doing it from the get-go, but I'll take it!
Thanks again!

Good deal. Glad it worked for ya.
(I'll leave the file up for a few hours in case anyone else needs it.)

Is it just me, or does this animation look kinda stale?

Got it to work. Looks great. Thanks

I rebooted while docked to my 42". Itsanice.
http://www.youtube.com/watch?v=ZmGBfqn-01g&feature=youtube_gdata_player
Sent from my HTC Hero CDMA using Tapatalk

[Q] Change galaxy tab 8.9 boot animation?

Anyone know how to change the animation to support bootanimation.zip ?
(Samsung galaxy tab 8.9 _motley kernel. KJ5 Honeycomb 3.2)
No luck on my end yet.
But here's what ive tried:
I connected my tab via ADB
Renamed bootsamsung.qmg to bootsamsung.qmg.bak
Renamed bootsamsungloop.qmg to bootsamsunglook.qmg.bak
Copy custom bootanimation.zip to /system/media/bootanimation.zip
copy custom bootanimation.zip to /data/media/bootanimation.zip
Type: bootanimation
It plays on my screen.
CTRL+C to quit.
I issue a reboot command and my 8.9 tab and I see Samsung logo, hear Samsung sound, but I do not see my custom start up. So samsung boot animation is down. But the custom animation is not up.
Can someone point me out to what I may be missing? I see some 8.9 roms support bootanimation.zip Here: http://forum.xda-developers.com/showthread.php?t=1321142&highlight=bootanimation+zip
....but I wanted to try it my self without flashing a new rom.
Any insight welcome.

I've answered this question here: http://forum.xda-developers.com/showpost.php?p=20977703&postcount=14
The correct way would of course be to change init.rc in the initrd but that's a bit complicated so a quick hack would be just to overwrite /system/bin/samsungani with /system/bin/bootanimation

kallt_kaffe said:
I've answered this question here: http://forum.xda-developers.com/showpost.php?p=20977703&postcount=14
The correct way would of course be to change init.rc in the initrd but that's a bit complicated so a quick hack would be just to overwrite /system/bin/samsungani with /system/bin/bootanimation
Click to expand...
Click to collapse
Thanks for the reply on the other thread, but I thought it would be better to bring this question outside of the rom discussion thread. Don't want to contaminate their discussion of the rom with something somewhat less important.
Anyhow, I tried the above in this specific order:
1. Using root explorer app, rename the 'samsungani' file to located in /system/bin
Done: samsungani.bak
2. Rename the file 'bootanimation' (also located in /system/bin) to 'samsungani'
Done.
3. Now put the bootanimation.zip of your choice in /system/media folder
Done.
However, after i reboot, now i'm stuck at the boot animation staying on screen even after the system has booted up. The animation goes on... If i tap my screen, I can launch apps and such, i just cant see behind the animation. If i rotate my tab, My main screen becomes visible at the bottom but portion of my screen is still occupied by the boot animation. Wierd! lol.
Looks like i have to adb and rename / fix stuff back.
Ever have this happen to you?
fun fun.
TESTING
Landscape:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Portrait:

0okami said:
Thanks for the reply on the other thread, but I thought it would be better to bring this question outside of the rom discussion thread. Don't want to contaminate their discussion of the rom with something somewhat less important.
Anyhow, I tried the above in this specific order:
1. Using root explorer app, rename the 'samsungani' file to located in /system/bin
Done: samsungani.bak
2. Rename the file 'bootanimation' (also located in /system/bin) to 'samsungani'
Done.
3. Now put the bootanimation.zip of your choice in /system/media folder
Done.
However, after i reboot, now i'm stuck at the boot animation staying on screen even after the system has booted up. The animation goes on... If i tap my screen, I can launch apps and such, i just cant see behind the animation. If i rotate my tab, My main screen becomes visible at the bottom but portion of my screen is still occupied by the boot animation. Wierd! lol.
Looks like i have to adb and rename / fix stuff back.
Ever have this happen to you?
fun fun.
Click to expand...
Click to collapse
(For 7300/7310 reference, if you have a different device then please ignore)
Actually, to change or remove the bootanimation, you don't have to touch anything at /system/bin (you might break something and might have to ODIN later on). The only files that matter are:
1_Power_on.ogg (the bootanimation sound) located at /system/etc
bootsamsung.qmg and bootsamsungloop.qmg both located at /system/media
Those are the 3 files you would have to delete or replace. No zip files in there. You actually have to unzip that file in your computer, not put it in the device. Check the mentioned contents, replace in the device and reboot.

nirogu325 said:
(For 7300/7310 reference, if you have a different device then please ignore)
Actually, to change or remove the bootanimation, you don't have to touch anything at /system/bin (you might break something and might have to ODIN later on). The only files that matter are:
1_Power_on.ogg (the bootanimation sound) located at /system/etc
bootsamsung.qmg and bootsamsungloop.qmg both located at /system/media
Those are the 3 files you would have to delete or replace. No zip files in there. You actually have to unzip that file in your computer, not put it in the device. Check the mentioned contents, replace in the device and reboot.
Click to expand...
Click to collapse
bootsamsung.qmg and bootsamsungloop.qmg have already been renamed to
bootsamsung.qmg.bak and bootsamsungloop.qmg.bak
After doing that, even with bootanimation.zip in place, it was just giving me a black screen until the launcher came up.

Seems the bootanim service needs to be stopped when boot is complete. This is not needed in Gingerbread asfaik.
In the Overcome ROM this has been added to the init.rc to take care of stopping the bootanimation:
Code:
on property:dev.sfbootcomplete=1
stop bootanim
Adding this means you have to unpack boot.img and the initrd, do the changes and then assemble it all again. This is a bit more complicated and nothing I recommend without doing the proper research on the subject first.

0okami said:
bootsamsung.qmg and bootsamsungloop.qmg have already been renamed to
bootsamsung.qmg.bak and bootsamsungloop.qmg.bak
After doing that, even with bootanimation.zip in place, it was just giving me a black screen until the launcher came up.
Click to expand...
Click to collapse
Hmm, actually you do have a very valid question. The dev didn't mention a How-to related to the Bootanimation.zip support. Have you checked at the Galaxy Tab 10.1 Themes and Apps forum for a clue?

progress...
I found these instructions and it got the boot animation loading and going away, but the sound that gets played with animation stopped working. (fixable since i backup everything)
Found here:
http://forum.xda-developers.com/showthread.php?t=1142838
My post in that thread:
http://forum.xda-developers.com/showpost.php?p=21010818&postcount=31
Basically the steps in Root Explorer:
wesbalmer said:
ROOT EXPLORER METHOD, thanks Berner:
Code:
Basically the steps in Root Explorer:
1. Copy bootanimation.zip to /sdcard (USB mount, dropbox, whatever).
2. Select /system/bin/playsound
(note - you'll need to set /system/bin as R/W here)
3. Rename to playsoundBACKUP
4. Select /system/bin/bootanimation
5. Copy/paste - new file will be named bootanimation - Copy
6. Rename bootanimation - Copy to playsound
7. Select bootanimation.zip whereever its located on .sdcard
(note - you may need to set /system/media as R/W here)
8. Move to /system/media/
Click to expand...
Click to collapse

ignore this post. double post.

[Q] No service on international ROMS for the T-MOBILE S6

So this awesome developer is working hard at making a fix for the no service issue on the Galaxy S6 for T-Mobile when flashing a G920F ROM
THIS IS OUR 2ND TRY AT THIS AND IT MAY NOT WORK THE LINK WILL BE UPDATED AS HE UPDATES IT UNTIL
HE MAKES HIS OWN THREAD FOR IT WHEN IT IS FINISHED
https://drive.google.com/file/d/0BwXTGcX6nnPEM21lYVpnZENlbXM/view
I checked to see if it worked on my S6 and I just get com.android.dialer has stopped.
THE ORIGINAL QUESTION WAS FLASHING INTERNATIONAL ROMS ON THE T-MOBILE S6 AND WE ARE STILL HAVING ISSUES WITH TEST2
I just thought I would update this thread to let everyone know our progress in solving this issue.
The developer who made this fix is gaganmohal!

I take it you don't care if you end up bricking? If thats the case you probably dont care if you trip knox. If that is so, you could just root and twrp then make a rom out of the tar ball. If you don't know how to do that I could help. I'm not completely up on how knox works yet but you should beable to make your own tar ball with the international system.img with with the tmobile boot. The two phones hardware should be close enough that the kernels difference shouldn't matter. Twrp zip or repackaging the tar ball are much better options than blindly flashing the wrong firmware.

ThePagel said:
I take it you don't care if you end up bricking? If thats the case you probably dont care if you trip knox. If that is so, you could just root and twrp then make a rom out of the tar ball. If you don't know how to do that I could help. I'm not completely up on how knox works yet but you should beable to make your own tar ball with the international system.img with with the tmobile boot. The two phones hardware should be close enough that the kernels difference shouldn't matter. Twrp zip or repackaging the tar ball are much better options than blindly flashing the wrong firmware.
Click to expand...
Click to collapse
OK I would like help on repackaging the tar ball and no I don't care about tripping KNOX as I already have and I don't even have a warranty on this and I plan on paying this phone off

ethanscooter said:
OK I would like help on repackaging the tar ball and no I don't care about tripping KNOX as I already have and I don't even have a warranty on this and I plan on paying this phone off
Click to expand...
Click to collapse
Here is the problem, my last samsung phone was the s3 and we didnt see knox intil the end of its 2 year run. I'm going to have to look into the s5 and see what can be left out of the tar ball just in case knox needs this or that to match up. Im not getting this phone until the first so I just wanted you to be completely aware I dont have this phone yet and am behind the times with knox. Honestly it probably wont work because if it would we would have seen a pre rooted tarball by now. Ill let you know what I come up with.

ThePagel said:
Here is the problem, my last samsung phone was the s3 and we didnt see knox intil the end of its 2 year run. I'm going to have to look into the s5 and see what can be left out of the tar ball just in case knox needs this or that to match up. Im not getting this phone until the first so I just wanted you to be completely aware I dont have this phone yet and am behind the times with knox. Honestly it probably wont work because if it would we would have seen a pre rooted tarball by now. Ill let you know what I come up with.
Click to expand...
Click to collapse
Thanks by the way you know knox can be disabled in supersu right tripping knox means it shows you voided your warranty in download mode but knox isn't like a locked bootloader...

ethanscooter said:
Thanks by the way you know knox can be disabled in supersu right tripping knox means it shows you voided your warranty in download mode but knox isn't like a locked bootloader. ..
Click to expand...
Click to collapse
Right, right I was on a locked s3 and I pinned the two together for some reason. I did know that :good:

ThePagel said:
Right, right I was on a locked s3 and I pinned the two together for some reason. I did know that :good:
Click to expand...
Click to collapse
So now that we can get started can you please help me with the process I already have the G920t tar downloaded

ethanscooter said:
So now that we can get started can you please help me with the process I already have the G920t tar downloaded
Click to expand...
Click to collapse
Gimme a couple hours just got off work.

ThePagel said:
Gimme a couple hours just got off work.
Click to expand...
Click to collapse
Ok

So I didn't even think to ask if you have access to linux. Probably a way to do it in windows but I don't do this kind of stuff in windows.

I can use cygwin linux terminal emulator

ThePagel said:
So I didn't even think to ask if you have access to linux. Probably a way to do it in windows but I don't do this kind of stuff in windows.
Click to expand...
Click to collapse
I can use cygwin terminal (linux terminal emulator) people have done it before.

Okay this is by no means a step by step since I have never used cygwin and have no clue how commands and directory layout might differ.
Commands needed and some examples if I feel is necessary
Spaces or the lack of spaces is very important
Make a new directory: mkdir
Move files/folders: mv
View directory contents: dir
Extract tar: tar xvf originalFirmwarename.tar.md5
Create tar: tar -cvf firmwaremixname.tar system.img boot.img modem.img (they might be .bin and thats fine)
Add md5: md5sum -t firmwaremixname.tar >> firmwaremixname.tar
Rename: mv firmwaremixname.tar firmwaremixname.tar.md5
Make 3 folders:
T-mobile
International
Mix
Move the the international and T-Mobile firmware to their folders
Cd to and extract the tar for both files
Move only the system from the international folder to the mix folder
Move the boot, modem and recovery from the T-mobile folder to the mix folder
Cd to the mix folder and create the tar
Add the md5 then rename it to whateveryouwant.tar.md5
Flash in odin or jodin
If it boots up great the systems are close enough that kernel difference doesn't matter. If it doesn't boot try a factory reset and if its still not working the kernel difference is whats killing it. The boot from the international version could potentially work but its not worth the possible brick.
If you add anything from international other than the system you will probably brick so don't do it.
If you get stuck just google it, Ill probably take a long time to get back to you. But if google doesn't help ill answer asap.

ThePagel said:
Okay this is by no means a step by step since I have never used cygwin and have no clue how commands and directory layout might differ.
Commands needed and some examples if I feel is necessary
Spaces or the lack of spaces is very important
Make a new directory: mkdir
Move files/folders: mv
View directory contents: dir
Extract tar: tar xvf originalFirmwarename.tar.md5
Create tar: tar -cvf firmwaremixname.tar system.img boot.img modem.img (they might be .bin and thats fine)
Add md5: md5sum -t firmwaremixname.tar >> firmwaremixname.tar
Rename: mv firmwaremixname.tar firmwaremixname.tar.md5
Make 3 folders:
T-mobile
International
Mix
Move the the international and T-Mobile firmware to their folders
Cd to and extract the tar for both files
Move only the system from the international folder to the mix folder
Move the boot, modem and recovery from the T-mobile folder to the mix folder
Cd to the mix folder and create the tar
Add the md5 then rename it to whateveryouwant.tar.md5
Flash in odin or jodin
If it boots up great the systems are close enough that kernel difference doesn't matter. If it doesn't boot try a factory reset and if its still not working the kernel difference is whats killing it. The boot from the international version could potentially work but its not worth the possible brick.
If you add anything from international other than the system you will probably brick so don't do it.
If you get stuck just google it, Ill probably take a long time to get back to you. But if google doesn't help ill answer asap.
Click to expand...
Click to collapse
Thanks but I decided to just flash an international rom which is working great... but I have no service can you please help me fix that I am trying to flash a G920F rom

ethanscooter said:
Thanks but I decided to just flash an international rom which is working great... but I have no service can you please help me fix that I am trying to flash a G920F rom
Click to expand...
Click to collapse
Whats inside the zip?

ThePagel said:
Whats inside the zip?
Click to expand...
Click to collapse
META-INF, system, tmp, boot.img
The rom download is here https://www.androidfilehost.com/?fid=95916177934555476
Thread for the rom is here: http://forum.xda-developers.com/gal...-xtrestolite-pure-edition-1-0-beta-1-t3082467

ethanscooter said:
META-INF, system, tmp, boot.img
The rom download is here https://www.androidfilehost.com/?fid=95916177934555476
Thread for the rom is here: http://forum.xda-developers.com/gal...-xtrestolite-pure-edition-1-0-beta-1-t3082467
Click to expand...
Click to collapse
Unless there is a modem.img or .bin in the tmp folder all you should need to do is make a apn for t-mobile or whatever your carrier is. You might have to change network mode after making the apn.

ThePagel said:
Unless there is a modem.img or .bin in the tmp folder all you should need to do is make a apn for t-mobile or whatever your carrier is. You might have to change network mode after making the apn.
Click to expand...
Click to collapse
I made an APN for T-Mobile and I still get the forbidden sign where I should see bars but the weird thing is data works and texting works but for calling, I can make calls but no one can hear me and I can't hear them and once again I have that forbidden sign (circle with line going through it)
Picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ethanscooter said:
I made an APN for T-Mobile and I still get the forbidden sign where I should see bars but the weird thing is data works and texting works but for calling, I can make calls but no one can hear me and I can't hear them and once again I have that forbidden sign (circle with line going through it)
Picture:
Click to expand...
Click to collapse
Well the good news is we can make it work. The bad news is your going to need to get your hands a little dirty. I cant think of the folder off hand but you need to move a bunch of .so files from the stock T-Mobile rom into the international rom then reflash. That should get everything up and running for you, should.
*edit*
I think its in system/lib
Do some searching and you should beable to find the exact files you need to transfer, otherwise I can give you a list later.

ThePagel said:
Well the good news is we can make it work. The bad news is your going to need to get your hands a little dirty. I cant think of the folder off hand but you need to move a bunch of .so files from the stock T-Mobile rom into the international rom then reflash. That should get everything up and running for you, should.
*edit*
I think its in system/lib
Do some searching and you should beable to find the exact files you need to transfer, otherwise I can give you a list later.
Click to expand...
Click to collapse
Thanks I tried looking for what files I need online but I couldn't find the names of them
Can I have that list
And yes I found lots of .so files in /system/lib
BTW I am rooted (you probably figured that by now)