Database Info

Boot logo

Does anyone know where the boot logo and animation is located

gentoo22 said:
Does anyone know where the boot logo and animation is located
Click to expand...
Click to collapse
not sure where but i did come across it many times.
Just instal Astro onto your device, and browse the root of the device and you will come across a BootAnimation.zip. Inside contains the png's for the animation.

the boot logo (non animated) is stored on splash1.
Here it is:
{
"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"
}
The animation is stored in /system/media/bootanimation.zip. Its a series of images in a zip file.
You can get it by using the command:
Code:
adb pull /system/media/bootanimation.zip C:/bootanimation.zip

system\media\bootanimation.zip
do a adb pull /system/media/bootanimation.zip xxx.zip and unzip.
You'll see the 2 sets of PNGs.

seraph1024 said:
system\media\bootanimation.zip
do a adb pull /system/media/bootanimation.zip xxx.zip and unzip.
You'll see the 2 sets of PNGs.
Click to expand...
Click to collapse
I always use / and have had no problems

melterx12 said:
I always use / and have had no problems
Click to expand...
Click to collapse
sorry about \ I mean to say /
adb pull system/media/bootanimation.zip bootanimation.zip
I just did that.

and how do i get the splash image

or how to flash a new one
i tried fastboot flash splash1 image...
created with a g1 tool for that but doesnt work

blablub334 said:
or how to flash a new one
i tried fastboot flash splash1 image...
created with a g1 tool for that but doesnt work
Click to expand...
Click to collapse
splash1 partition is locked for obvious reason.

seraph1024 said:
splash1 partition is locked for obvious reason.
Click to expand...
Click to collapse
What are the permissions for bootanimation.zip if they were left open to non root then this may-b a way to get root with unlocking the bootloader. This would be the same approach that was used to root the behold 2 where the "try3" file was renamed to play_logo . play_logo then was used to root and after root was opened it would make play_logo_real play which was the boot animation. I may be wrong but couldnt this be a possibility. Thanks.

how is it possible to unlock splash1 and safe the old picture
and then flash a new one

Made an extremely simple quick bacon boot-"animation". Just a static bacon image, but looks kinda cool...
http://karlerik.mine.nu:88/android/baconboot.zip
Might try to add some animation later...
|<

Help... Trying to flash the newest Tiamat kernal and Clockwork Mod

When I rooted, I used the one click method and worked like a charm. Now, I would like to learn how to flash the files via adb. I am a novice user of adb but have used it.
Right now, I am trying to flash the recovery.img file. Here is what I am getting:
{
"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"
}
I have the recovery.img file in my /platform-tools folder. When I go to devices, I see my xoom listed and I do screen shots all the time using the ddms.bat file.
Can anyone tell my why my xoom will not let me flash files? I tried this a few weeks ago with the first Tiamat SDCard enabled kernal and it said the same thing, it wouldn't let me flash the file.
Thanks!

Your not actually changing direcotry into the correct directory. so when you call the fastboot command it's looking in the current directory of "c:\Users\Marc" instead.
cd \Program Files(x86)\Android\android-skd\platformtools
adb reboot bootloader
fastboot flash recovory recovory.img

Did you open the command line from the same folder you have the file you want to use? If not, open the folder you have recovery.img and the other files you will be using are in and hold the shift key on the keyboard and right click on the mouse. Then left click on "open command window here". Then run your adb commands.
Sent from my Xoom using XDA Premium App

Thanks guys, Ill try again.

ghoticov said:
When I rooted, I used the one click method and worked like a charm. Now, I would like to learn how to flash the files via adb. I am a novice user of adb but have used it.
Right now, I am trying to flash the recovery.img file. Here is what I am getting:
I have the recovery.img file in my /platform-tools folder. When I go to devices, I see my xoom listed and I do screen shots all the time using the ddms.bat file.
Can anyone tell my why my xoom will not let me flash files? I tried this a few weeks ago with the first Tiamat SDCard enabled kernal and it said the same thing, it wouldn't let me flash the file.
Thanks!
Click to expand...
Click to collapse
*FACEPALM*

jase33 said:
Did you open the command line from the same folder you have the file you want to use? If not, open the folder you have recovery.img and the other files you will be using are in and hold the shift key on the keyboard and right click on the mouse. Then left click on "open command window here". Then run your adb commands.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Does this work using Vista? I do not see the option to "open command window here".

Duh, nevermind... I figured it all out. I was putting a \ after platform-tools so it wasn't actually opening the folder where the recovery.img file was. Told you I was a novice. But I am getting it!

This is why one-clicks are the root of evil. If you would have done it manually from the start, you would have already known what to do here . Also since you posted this in development, i'm looking forward to the release, although i'm unsure what you are releasing at this point...

Ok people... Let's be mature here and not flame other users. This is supposed to be a community, not a war zone. If something is posted in the wrong section, or there's a post that breaks forum rules, drop me a pm or report the post. Thanks!
And this belongs in q and a... Since this is a question. Thread moved.
Please follow forum rules and post in the correct section.

damn, I must have missed some good flaming post! Lol

dont feel too bad
hehe I was doing the same thing for a 1/2 hour before I realized that the recovery.img wasn't even in the same folder...got that sorted out tho..

[SOLVED] Soft-Brick BOOT.IMG Recovery with CM10 and All-In-One Toolkit [NOOB-FRIENDLY

Right, I'm sure there is similar here, but I had loads of difficulty finding it, so I thought I'd create my own version.
I'm a complete noob at this, so I'll make it easier on you, and put it as plainly as possible. EVERY step is listed as if you're in the same [or similar] situation.
I only recently tried to get CM10 onto my phone, and on first try, I soft-bricked it. I unlocked the Bootloader, Rooted, Installed TWRP and a version of CWM when it didn't work, and CM10 seemed to work fine, but upon booting for the first time, and leaving it for about 15 minutes, I realised something went wrong. Tried going back to the most recent RUU [the EU OTA version], and that didn't work [after relocking the bootloader, yes]. Started freaking out a small bit, as it stopped letting me mount the storage in Recovery, even though ADB could still see the phone.
Asked a friend to help, and we found this over on the One X sub-forum.
BEING AWARE THIS IS RELATIVE TO hasoon2000's All-In-One Toolkit
[nice work btw! Might wanna look into this btw - it may be a small bug with your software. No offense ]
Turned out it was the boot.img that installed incorrectly, so making sure the .zip MD5 is correct is first step.
If that's not the issue, the 2nd step is to just open the .zip and take the boot.img out of the root of the container, and pushing that to the phone using ADB [the one that come's with the AIO is perfect]. If you're not sure how to get into ADB, and get it to stay open, here's what you do:
1. Copy the directory of "adb.exe" within your AIO's "data" folder [for example, mine is D:\Administrator.Sheol\HTC\All-In-One\Data\]
Click to expand...
Click to collapse
2. Open Command Prompt [in Vista onwards, type "cmd" into the Start menu Search Bar, in XP, open the "run" dialog in type cmd. Alternatively, find it in Start > Accessories, in all recent versions of Windows]
Click to expand...
Click to collapse
3. Type the following into Command Prompt:
cd D:\Administrator.Sheol\HTC\All-In-One\Data\
{
"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"
}
Remembering your directory WILL be different, so adjust accordingly!
Click to expand...
Click to collapse
4. It'll list all ADB's command's. Don't worry, it's meant to. If you want to, skim through them to familiarise yourself with it. At this point you may want to maximise the window, to fill the screen height [makes every thing much easier]
Click to expand...
Click to collapse
5. Follow this thread to the tee > [Tutorial] How to flash a new boot.img via Fastboot
Click to expand...
Click to collapse
Doing exactly this, worked a charm, and now I have a flawless CM10 HTC One S! After the GApps install of course [which can be done in your Recovery after downloading it/pushing it to your phone, by using the "Install from .zip" option]

Cannot find 'recovery.img'

Hi..I have Android L installed on my N5 and want to root it..so I have been following THIS guide, to install custom recovery and then I plan on rooting it using THIS thread..
While following the first guide to install TWRP..I am getting the following error
{
"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"
}
Can anyone please help me with this error..I tried the TAB to search for the recovery.img..but it did not work
if I hit Tab after 'fastboot flash' then I am not getting first 'recovery' option.
Not sure if this will help..here are the contents of the slimmed down android sdk I downloaded from first guide:

rockstar283 said:
Hi..I have Android L installed on my N5 and want to root it..so I have been following THIS guide, to install custom recovery and then I plan on rooting it using THIS thread..
While following the first guide to install TWRP..I am getting the following error
Can anyone please help me with this error..I tried the TAB to search for the recovery.img..but it did not work
if I hit Tab after 'fastboot flash' then I am not getting first 'recovery' option.
Not sure if this will help..here are the contents of the slimmed down android sdk I downloaded from first guide:
Click to expand...
Click to collapse
Navigate to your platform tools folder in command prompt. The path you have specified in the screenshot is not where your recovery.img is located... so keep typing ''cd.. enter'' until you're back at C:\ in the window, then type cd android-sdk-windows and hit enter, then cd platform-tools, and it should be able to find the recovery image.

GTI6speed said:
Navigate to your platform tools folder in command prompt. The path you have specified in the screenshot is not where your recovery.img is located... so keep typing ''cd.. enter'' until you're back at C:\ in the window, then type cd android-sdk-windows and hit enter, then cd platform-tools, and it should be able to find the recovery image.
Click to expand...
Click to collapse
was having the same problem and this actually fixed it, thank you sir

All, please have a read of my "adb and fastboot. What is it?" thread. It can be reached via the sticky roll up link in my signature.
You shouldn't need to put recover where you put it. My thread explains how to use it properly.
Sent from my Nexus 5 using Tapatalk

GTI6speed said:
Navigate to your platform tools folder in command prompt. The path you have specified in the screenshot is not where your recovery.img is located... so keep typing ''cd.. enter'' until you're back at C:\ in the window, then type cd android-sdk-windows and hit enter, then cd platform-tools, and it should be able to find the recovery image.
Click to expand...
Click to collapse
Thanks a lot mate..that did the trick..DUMB mistake

[Recovery] TWRP 3.1.1-0 for Elephone S3

{
"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"
}
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Download:
See " Attached Files"
Install:
Download zip file from above
Unzip the file
Download and install SP Flash Tools
Run SP Flash Tools and load scatter (Use the 'Modded' scatter if you want to install this recovery on a enlarged system partition.)
Press first the 'Download' button, before you connect the device with your pc
Reboot device
Remarks:
It is not possible to boot into recovery by holding some specific keys. You need to use ADB with the command: "adb reboot recovery".
Source code:
TWRP: https://github.com/omnirom/android_bootable_recovery/
Device Tree: https://github.com/Waterboy1602/Android_Device_Tree_Elephone_S3

Hey,
I installed this and the screen becomes irresponsive when I open TWRP. Any ideas?

skytig3r said:
Hey,
I installed this and the screen becomes irresponsive when I open TWRP. Any ideas?
Click to expand...
Click to collapse
I have no idea why it doens't work by you. Could you maybe give me a last_ksmg after you booted into the recovery?

waterboy1602 said:
I have no idea why it doens't work by you. Could you maybe give me a last_ksmg after you booted into the recovery?
Click to expand...
Click to collapse
Hey! Thanks for answering. I don't have it right now but on the weekend I'll be back and post it here.

skytig3r said:
Hey! Thanks for answering. I don't have it right now but on the weekend I'll be back and post it here.
Click to expand...
Click to collapse
I'm sorry for my late answer, but I fixed the problem. Now should your touch work

waterboy1602 said:
I'm sorry for my late answer, but I fixed the problem. Now should your touch work
Click to expand...
Click to collapse
hey! sry, it isn't my phone and I haven't been working on it lately, but now that you say it I'll try again thanks!