How can I change my bootsplash image on Qtek2020i???
Desktop Application = nb image converter.
Purpose = use to convert ur .jpg file into a set of splash1.nb and splash2.nb files (the win mobile thingy uses this pic format at bootups).
Copy .nb files to your device /windows directory.
copy BootSplash_Changer.cab to device and run it. lastly please do a soft reset.
done....
thanks
mm... why two pictures? where second is shown? first appears when you turn on device... and second?...
thank's alot!
Ice_mephi said:
mm... why two pictures? where second is shown? first appears when you turn on device... and second?...
Click to expand...
Click to collapse
Some phones (not the Alpine as far as I know, though) have two splash images, and show splash1.nb and splash2.nb as they boot - if you look through the forums, some people detail how they've got pictures of their kids or family as the splash images.
The Alpine / 2020i just uses the one though, I believe. I remember creating two different images, but it just showed the first one until it reached Windows and the PIN entry screen.
I see... I used only Alpin so don't know what shows on other...
btw - can I save my current boot picture?
because if something goes wrong - i belive my guarantee would be canceled if they notice I made something with it...
I managed to obtain the original XDA2i splash image from the ROM, and I posted it up on this forum.
I saw it, but I live in Russia, and here is no O2...))
my alpine has picture of Moscow with some numbers at the bottom - some serial number I belive...
If you are very patient, you can strip out the original boot splash logo with a hex editor. It took me a while to get it just right, but it is possible.
Alternatively, if you have the original firmware on your PC or on the web anywhere if you send me a link to it I can try and strip it out.
I believe someone's also in the process of making a program to save the original boot splash, but it's not finished yet.
Excuse me... i downloaded the nb converter but when i run it it says a comdlg32.ocx is missing ?? how to make it run ?? THankzz
Google for the file, put it in the same directory as the .exe and it should work ok.
For those looking for the actual attachment I was talking about earlier, see this thread: http://forum.xda-developers.com/viewtopic.php?t=34359
you guys are a lifesaver
Dunno about the rest of us but I'm always glad to dispense nuggets of advice whenever I can.
So I've been playing around for a little while with the intention of creating my own custom ROM. I think I've got everything all figured out - however I'm having a problem that I think is related to the initflashfiles.dat file. Basically, after flashing my new OS ROM, my 8125 hangs at the splash screen with the version numbers on it. As a test, I redid my modified ROM, except I used the original initflashfiles.dat - this worked just fine. Tried it again by building the ROM with my modified initflashfiles.dat - same problem.
Here are the steps I'm going through.
1. Parse out the nk.nbf file using typhoonnbfdecode -x
2. prepare_imgfs 80040000-OS.nb -nosplit
3. viewimgfs imgfs_raw_data.bin
4. Modify contents of dump directory. Basically I've deleted files I don't need and added new ones.
5. Modifiy initflashfiles.dat (which I've attached). After modifying the file I open it in a hex editor and remove the first two bytes - making the first byte 3B (";"). I save it and mark it as read-only.
6. buildimgfs
7. make_imgfs 80040000-OS.nb -nosplit
8. Run nb2nbf_tornado.exe. I do run this correctly, using the correct memory address for the OS .nb file.
9. Put the new nk.nbf into an existing RUU self-extracting archive and run it.
It really seems like it's the initflashfiles.dat file - as I've successfully loaded this ROM with the original file (its really not the original, it's from a summiter ROM that I'm basing mine off).
Any thoughts?
I'm going to bump this once just in case people missed it originally.
I've messed around a bit more, and have pretty much isolated that this is my problem - but for the life of me I can't figure out what I'm doing wrong.
CameronJ said:
I'm going to bump this once just in case people missed it originally.
I've messed around a bit more, and have pretty much isolated that this is my problem - but for the life of me I can't figure out what I'm doing wrong.
Click to expand...
Click to collapse
Hi,
i see that the file you've attached isn't actually a .DAT file. It is a .dat.TXT that's the same that saying it's a TXT file!!!
If the file you're putting inside your ROM is this very same file (.dat.txt) then you've found your problem: you need a .DAT and NOT a .dat.txt file!!!
Try following this procedure on your PC (i suppose you're using XP or 2003 server):
- open a folder (whichever folder you like, it's not important)
- on the Tools menu click Folder Options.
- click the View tab.
- clear the Hide extensions for known file types check box.
- press OK
PS: Here is an illustrated guide on how to show file extensions
Now go to the place where your initflashfiles.dat is. If the file is named 'initflashfiles.dat.TXT' (like the file you uploaded in this forum) then:
- select the file
- press F2 (or right click and choose 'Rename')
- remove the tailing .txt from the name
Finally:
- let us know if it worked
Bye bye
risidoro said:
i see that the file you've attached isn't actually a .DAT file. It is a .dat.TXT that's the same that saying it's a TXT file!!!
Click to expand...
Click to collapse
:lol: Thanks for the reply.
I had to add the .txt extension otherwise the forum wouldn't let me upload the file (.dat files are not on the list of available file types for upload).
When I loaded the file I meant to put that explanation in there but forgot before I finished the post.
Hi. I don't know if you're still working on this, but I'd like to share with you my experience last night. I examined your initflashfiles.dat, and it is perfectly ok.
As I see in your initflashfiles.dat, there are a lot of folder customization like:
Directory("\Program Files\Task Manager"):-File("taskmanager.exe","\Windows\taskmanager.exe")
There is nothing wrong with this as we need the file to be in the right location. BTW, THIS FORMAT WORKED FOR ME. Just a thought, you might be editing the default.hv and user.hv (hives) to put in the registry keys of some applications?
My device (Himalaya) did not start out correctly and did not execute the initflashfiles.dat, BUT when I connected my Hima through active sync, you can actually explore the contents. SO, in this non-working state, I experimented in tracing the culprit, by restoring a couple of the original files I edited. I found out that it has something to do with the way I edited the hives.
Steps I made in experimenting:
1. I sync my Hima to my PC.
2. Copied the original default.hv to \windows directory
3. Hard Reset Hima, BUT answer NO to all three boot options
4. My Hima started normally and executed initflashfiles.dat to the detail.
Discovery from experiment:
1. The files were only copied to the directory were we wanted it, BUT the original file is still in the \windows directory. Therefore, we did not save storage memory.
2. We only benefitted from an already installed app built into the ROM.
Hope this gives you some insight.
I followed all the instructions on how to create but when I create the NBH file I cannot find it all my computer where I placed it...Then I search for it then I find it but the flash utility wont open the file and I can only see .nb files in the folder where I place everything.
Also what program should I use to resize my pictures to 400x640
And I've read many post on this so did get mad at me..... Because you wouldn't want to see me mad.... Hulk SMASH!!!!!!!!!!
Might as well delete this since nobody will give any pointers.....and I meant to put help and not [ref]
hopefully someone will respond cause I actually have the same problem...hahaha..put the file on my network --- somewhere --- and now can't recall where...haha
Sparkz914 said:
I followed all the instructions on how to create but when I create the NBH file I cannot find it all my computer where I placed it...Then I search for it then I find it but the flash utility wont open the file and I can only see .nb files in the folder where I place everything.
Click to expand...
Click to collapse
are you trying to change the bootsplash (1st screen) or the regular (2nd screen, non animated one)??? if your just trying to change the regular splash screen you dont need to convert to .nbh...just change the name to welcomehead.192.png...and put in windows...
Also what program should I use to resize my pictures to 400x640
Click to expand...
Click to collapse
i use gimp...great program and free!!
*hope this helps*
Thank you so very much JDM, but i'm trying to change the first screen when you first turn the phone on when it shows your rom and radio info....I've been able to make and find the .nbh files but I am lost on how to use PatchSplash so that the bottom portion of the screen isn't black....Any help would be Very Helpful from anyone, so much that I may let someone buy me dinner lol but no fooling around on the first date
jdmsleepr said:
are you trying to change the bootsplash (1st screen) or the regular (2nd screen, non animated one)??? if your just trying to change the regular splash screen you dont need to convert to .nbh...just change the name to welcomehead.192.png...and put in windows...
i use gimp...great program and free!!
*hope this helps*
Click to expand...
Click to collapse
I'm actually trying to do both. I simply lost the software required to do the first one.....
Here are the programs to do the first boot screen
JDM i got that program Gimp but when I try to scale the photo to 480x640 but it changes it to its own dimensions which is like 480x247....Any insight on how to make it the right size....Thanks in advance
Sparkz914 said:
Here are the programs to do the first boot screen
Click to expand...
Click to collapse
kewl thanks...
Ok JDM I found out how to size the picture but im still lost on how to use patchsplash, now when I flash the image to my phone its fuzzy and distorted making it unviewable(if thats even a word) and 10% of the screen on the bottom is black.....?
TechnoHippie said:
kewl thanks...
Click to expand...
Click to collapse
No problem man, and you'll also need this
Sparkz914 said:
Ok JDM I found out how to size the picture but im still lost on how to use patchsplash, now when I flash the image to my phone its fuzzy and distorted making it unviewable(if thats even a word) and 10% of the screen on the bottom is black.....?
Click to expand...
Click to collapse
ok i have figured out how to use the patchsplash program...if you want i can make the file for you and send it back...
JDM that would be cool man
and do you think you could give me a brief description on how to use patchsplash
Which ever one is easier for you to create...thanks in advance
and if possible can you PM me the final product or can i give you my email
Ok JDM i've sort of learned how to use Patchsplash but not fully...this is where the program is located on my computer
Users\Seymore Cake\Documents\Phone ****\Splash Screens\
What should I put following this or what steps should I do next
Sorry for being some what of a pain for all the questions I ask of you
once your in the folder where patchsplash.exe is...
type: patchsplash.exe R example.nb output.nb
i made the .nbh for ya and tested...good to go...
JDM your the man
Maybe this will help....
Code:
[b]Download the attached zip file.
Extract it to (wherever you like) then follow the instructions below.[/b]
==============================================================================
Step by Step instructions on how to create your custom splash screen
for the Diamond and Rafael windows mobile.
==============================================================================
Step 1: Create your image
-
Choose, find or create the image you would like to have as your splash screen.
Use your image editor (photoshop is my choice) to adjust your image.
The size of the picture needed for the splash is 640x480 72dpi.
Save it as (24 Bit) (bmp) in folder (2-bmp to rsb to bmp).
goto Step 2.
------------------------------------------------------------------------------
Step 2: Convert your image from *.bmp to *.rsb
-
Run rsbbmp.exe in folder (2-bmp to rsb to bmp).
Click on [Add Files] and choose your bmp.
Click on [Convert All]
Your image has now been cloned and converted to rsb format.
Move or copy your rsb file to folder (3-rsb to nb).
goto Step 3.
------------------------------------------------------------------------------
Step 3: Convert your image from *.rsb to *.nb
-
Run Splash-RSB Converter.exe in folder (3-rsb to nb)
Choose VGA (640x480) then press [Convert].
Choose your rsb and save it in folder (4-patchsplashv0.1) click on [Done]
goto Step 4.
------------------------------------------------------------------------------
Step 4: Patch your image file.
-
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Remember, patchsplash.exe is a command line tool. If you run the program by double
clicking on it a cmd window will open showing you examples of the command line you
will need to type to patch your *.nb that is all.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
First, open the folder (4-patchsplashv0.1) in Windows file explorer. Copy the
address found at the top of the explorer window.
example: D:\PDA\HTC\splash\4-patchsplashv0.1
On Windows, Start Menu->Run... Click on Run then paste the address you copied
from win explorer then type the rest of the line needed for patching.
My example:
D:\PDA\HTC\splash\4-patchsplashv0.1\patchsplash R YOURFILENAME.nb YOURFILENAME_P.nb
\patchsplash R YOURFILENAME.nb YOURFILENAME_P.nb -> Rafael
\patchsplash D YOURFILENAME.nb YOURFILENAME_P.nb -> Diamond
Press enter and you're done!
A cmd.exe window will pop up telling you the process is complete.
REMEMBER
The first part of my example "D:\PDA\HTC\splash\4-patchsplashv0.1\"
is what I copied from win explorer.
"I" then move the new "_P.nb" file to the folder (5-nb to nbh) so not to
confuse it with the unpatched file.
goto Step 5.
------------------------------------------------------------------------------
Step 5: Create the *.nbh for flashing
-
Run NBHutil.exe in the (5-nb to nbh) folder.
Note: (the NBHUtil.xml file has to be in the same folder as NBHUtil.exe).
On first tab 'Build NBH', in the 'Target Device' list, choose "Diamond" or "Rafael"
located ad the bottom of the list.
On the right side, you have the "NBH Items". Click on the [...] button for "Splash".
An "Open" window pops up. Locate and select the .nb file that you just created.
Press [Build NBH!]
Type a file name and save!
This will create a .nbh file in the location you chosen. ((5-nb to nbh) folder by default)
goto Step 6.
------------------------------------------------------------------------------
Step 6: Flash your NEW Splash Screen!!!
-
I personally like to create a new folder for my newly created .nbh files.
In each folder I have my (*.nbh) and a copy of (RaphaelCustomRUU.exe).
In this way I can quickly flash which ever splash screen I want without any extra effort.
Create a folder. Place your new .nbh and a copy of RaphaelCustomRUU.exe in the folder.
Run RaphaelCustomRUU.exe, follow the instructions and you will have a new splash screen!
Enjoy! ;)
HueMann
------------------------------------------------------------------------------
thanks HueMann very helpfull
cheers!
Here's a tutorial for those wanting to make their own (animated) bootscreen for the HTC Hero. Decided to write it after I'd seen a couple of posts from people asking about this, and some encouragement from yet another. I've tried to write this in greatest detail possible, so everyone can have a go at doing this.
Tools
It's really quite simple, if you have the proper tools for the job:
SignAPK.jar + testkey.pk8 + testkey.x509.pem
SignAPK.cmd (batch file written by me to facilitate signapk.jar use)
Graphics editor that can work with animated GIF files (Adobe Photoshop or Fireworks recommended)
a plain text editor capable of editing UNIX files (if you're unsure about this, use the free, and open source Notepad++. You can get the Installer.exe here.)
These aren't required, but make things easier:
Android SDK Tools installed (working adb.exe at the very least)
Hero's stock bootscreen to start from)
I have attached two stock Hero bootscreens (one with and one without the HTC startup sound), as well a zip file with the signapk files.
Setting up SignAPK
First, make sure you have Java installed. If not go to www.java.com to install it.
Second, I recommend to unzip the SignAPK_xda.zip file to C:\SignAPK.
Lastly, add the signapk folder to your PATH environment variable:
[*]Go to Control Panel, System
[*]Click on "Advanced" (or "Advanced System Settings")
[*]Click the button "Environment Variables..."
[*]Locate the PATH variable under "User Variables" (or "System variables" if you want to use SignAPK under other user accounts) and double-click it to edit
[*]In the "Variable Value" field, at the end of the line, type a semi-colon and the path to the signapk files ;C:\SignAPK
[*]You could also add the path to your java.exe file here if you have troubles with running signapk.​
A note on signapk.CMD
I wrote this batch file so it's possible to sign a zip file from a command line with the least amount of typing (saves time and less chance of a typo). It will check for java.exe and if it doesn't find it in your %PATH% it will let you know and try anyway. It will also prompt you to overwrite or not, if it finds the signed destination file already exists. Open in notepad to find out more.
Contents of bootscreen_stock.zip
You can delete the following three files, as they are created by the signing process:
META-INF\CERT.RSA
META-INF\CERT.SF
META-INF\MANIFEST.MF
This file contains the command to copy the files to the SYSTEM: volume on your device - you never need to edit this:
META-INF\com\google\android\update-script
This file tells Android how and which files to display - open in Notepad++:
system\media\bootscreen\boot_animation.xml
Then we have the actual bootscreen files:
system\media\bootscreen\boot1.gif - shown first, and plays only once
system\media\bootscreen\boot2.gif - shown after first ends, and loops forever (i.e. until end of boot sequence)
system\media\bootscreen\boot_bg.gif - optional file, this file is used as background during entire boot sequence if the 2 aforementioned files are smaller than Hero's screen
system\media\bootscreen\boot.mp3 - optional sound file, played once during boot
boot_animation.xml file contents
Code:
<?xml version="1.0" encoding="utf-8"?>
<!--
* Copyright (C) 2008 HTC Inc.
*
-->
[COLOR="Red"]<!-- For new bootup animation
<BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot.gif"
audio="/system/media/bootscreen/boot.mp3"
image2="/system/media/bootscreen/boot2.gif" (optional)
image3="/system/media/bootscreen/boot3.gif" (optional)
screenX="100" (optional)
screenY="130" (optional)
image_bg = "/system/media/bootscreen/boot_bg.gif" (optional)
useAudio="1" // 1: true ; 0:false (optional)
/>
</BootConfiguration>
-->
[/COLOR]
[COLOR="Green"]<!-- For cropped version -->
<BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot.gif"
image2="/system/media/bootscreen/boot2.gif"
image3="/system/media/bootscreen/boot2.gif"
loopimage="/system/media/bootscreen/boot2.gif"
image_bg="/system/media/bootscreen/boot_bg.gif"
audio="/system/media/bootscreen/boot.mp3"
screenX="10"
screenY="180"
useAudio="1"
/>
</BootConfiguration>
[/COLOR]
[COLOR="Red"]<!-- For full screen version -->
<!--BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot.gif"
audio="/system/media/bootscreen/boot.mp3"
useAudio="1"
/>
</BootConfiguration-->[/COLOR]
This is the file included with the stock bootscreen. This file actually contains 3(!) configurations, however the first and third (red-colored) have been commented out. In short, edit the middle (green-colored) "BootConfiguration" section.
Delete the line that begins with image3= as you won't need it.
If you do not wish to include a startup sound, delete lines starting with:
audio=
useaudio=
Alternatively, simply set useAudio=0
If you boot1.gif and boot2.gif files are both 320x480 pixels, delete lines starting with:
image_bg=
screenX=
screenY=
Alternatively, simply set screenX=0 and screenY=0
If you delete the audio= and image_bg= lines, you can ofcourse delete the files audio.mp3 and image_bg.gif to keep the update.zip as small as possible.
ScreenX and ScreenY are coordinates in pixels, that tell Android where to place the GIF files on the screen. Top-left of the screen would be ScreenX=0 and ScreenY=0; bottom-right would be ScreenX=320 and ScreenY=480. This means that if you make a GIF file that is 200 px wide and 180px high and you wish to center this on the screen, you'd use ScreenX=60 and ScreenY=150 (i.e. ScreenX=320-200=120/2=60 and ScreenY=480-180=300/2=150). If your GIF files are exactly 320x480 pixels, you can set ScreenX and ScreenY both to 0, or leave those two lines out entirely.
Creating a GIF animation from scratch
(boot1.gif and boot2.gif)
Using Adobe Photoshop CS4 (cannot speak for older versions, I think you'd need the now discontinued Adobe ImageReady instead):
Create a layer for each frame of your animation (yes, I didn't say creating an animation from scratch wouldn't be a lot of work)
Click Window -> Animation to show the Animation panel
Click the panel menu (top right icon in panel) and choose "Make Frames from Layers"
If the frames are loaded in reverse from what you intended, choose "Reverse Frames" from the Animation panel menu
From the panel menu, choose "Optimize Animation" and UNtick both "Bounding Box" and "Redundant Pixel Removal"
Finally, go to File -> Save for Web & Devices, UNtick "Transparency" and play with some of the options to reduce file size.
To (re-)open an animated GIF file in Photoshop CS4, go to File -> Import -> Video Frames to Layers and type in the file name box *.gif then hit the Enter key so you can see GIF files, browse to it, select and click Load.
Using Adobe Fireworks CS4:
Make sure the "States" panel is visible, via Window -> States
Create a new "State" for each frame of your animation
To set frame delays, or basically set how long each frame will be shown for, in 100ths of a second, select one or more states and right-click, choose "Properties"
Make sure you do not use transparency (this gave me problems)
To save, go to File -> Save As, set "Save as Type" to "Animated GIF (*.gif)" and "click Options"
Do check "Dither" for better looking gradients and transitions
Play with the options on the first tab to reduce file size
On the "Animation" tab, UNcheck "Crop each state" (don't do this and get some crazy glitchy results in your bootscreen)
Creating a GIF animation by converting a G1 bootscreen animation to Hero format
(boot1.gif and boot2.gif)
You can also import a bunch of PNG files as layers (and subsequently frames) from, for example, a G1 bootscreen.
The fastest way in my experience is simply using Fireworks' File -> Open dialog, make sure all files are in one directory, select them all, do check the "Open as Animation" checkbox and click "Open". This will open each file into its own state in one big file. Then use instructions above to set frame delays and proceed to save as animated GIF.
You can also do it in Photoshop, but this method is very slow, via File -> Scripts -> Load Files into Stack (UNtick "Create Smart Object after loading layers"). Then follow the steps above to create an animated GIF file.
Compiling your bootscreen
If you have the files you want, it's time to zip them and then sign the zip file.
Make a folder "mybootscreen" and unzip the stock bootscreen into that, so it looks like this:
META-INF\CERT.RSA
META-INF\CERT.SF
META-INF\MANIFEST.MF
META-INF\com\google\android\update-script
system\media\bootscreen\boot_animation.xml
system\media\bootscreen\boot1.gif
system\media\bootscreen\boot2.gif
system\media\bootscreen\boot_bg.gif
system\media\bootscreen\boot.mp3
Delete those first 3 files, edit the XML file as needed and replace the GIF files with your own (see my explanations above).
Use for example 7-zip to select the 2 folders META-INF and system and click "Add" (to create new archive)
Make sure you set "Archive Format" to ZIP
Open a Command Prompt window (click Start, Run, type cmd and click OK, or if you have Vista or Windows 7, click Start, type cmd and hit Enter key)
Use this command to go to the directory with your zip file: CD /D C:\path\to\your\file
Type signapk mybootscreen.zip and hit Enter key
Barring any typo's you should now have a file named mybootscreen_signed.zip. You can copy that to the root of your SDCARD and flash it via your recovery image, or use DroidExplorer's flash function.
If this tutorial was of any use to you, or you have ideas to make it better, please reply and let me know. Thanks for reading!
EDIT (2010-04-11): updated SignApk_xda_v20100411.zip. Fixed a couple of forgotten quotes in signapk.cmd that made signing files with spaces in their filenames impossible. New zipfile attached.
wooooo THANKS!
THANKS A LOT! I have made the animated gifs and the sound, but I was insure how to sign and create the signed zip. I'll be trying this ASAP when Ive finished work. Ill keep you posted....
Thanks again m8.
Great guide, I have made my own bootscreen for the Villain rom, but for some reason, when i flash it to my hero, on boot, it plays less than a second of it, ad then messes up completely and displays random static like on an old tv, and then just a black screen for the remainder of the boot time
Help!! my gifs are not that big, i made sure of that (only slightly more than the stock) and i made them in photoshop CS4 with the animations panel, and followed your instructions to the letter.
Gifs are bellow, please help, as i would really like to release these, as i think they are really nice.
Boot1
{
"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"
}
Boot2
Hey, very nice work! Try the zip I've attached. I think it came out great.
It boils down to a few small problems. Here are some steps I took to correct them:
Imported your files into PS as I described in the tutorial using "Video frames to Layers"
Edit -> Convert to Profile -> sRGB IEC61966-2.1 (UNcheck "Flatten Image")
For just boot1.gif in Animation Panel, bottom left, set looping to "Once"
For just boot1.gif via Image -> Image Size... -> Width:320px, Height:480px, Resolution:72dpi, Check Resample Image and set to "Bicubic"
File -> Save for Web & Devices, with these settings: Selective, Diffusion, UNcheck transparency, UNcheck interlaced, Colors:64 (as this is a grayscale animation, it looks fine), Dither:100%, Matte:none, Web snap:0%, Lossy:0, Metadata:none.
The end result is bigger files, but they work. The XML was fine.
Great! thanks a lot for your help, and your original guide, I might do a few more boot screens now as it looks really good (in my opinion)
mattyyey said:
THANKS A LOT! I have made the animated gifs and the sound, but I was insure how to sign and create the signed zip. I'll be trying this ASAP when Ive finished work. Ill keep you posted....
Thanks again m8.
Click to expand...
Click to collapse
How'd it come out? Would love to see your results!
Really interessant, this is exactly what I was looking for! Thanks for this How-To!
For the signing process I haven't use your "signapk.cmd" (since I'm a linux user)But I have a question: testkey.x509.pem & testkey.pk8 you provied are only to sign app for the Hero? or is it a standard Android singning process? I mean... where are those key from?
For now i've just "resign" the stockbootscreen for "educational purpose", soon I'll try to create something, I hope
EDIT: Okay I was able to resign the original one correctly since I was able to flash it, BUT my bootscreen is still this nexus one animated. So maybe I don't understand wich bootscreen we actually modifing. I know this is not the really first one (this one is fine: spend one day to find that we need a custom SPL to change my ex horrible T-mobile first bootscreen to a Hero one) So why can't I remove the nexus one coming with aHero ROM?
EDIT2: using
Code:
./adb pull /system/media/bootscreen/boot.gif ./Desktop
I get the right image... that mean the files are correctly flashed on my ROM but nothing change so that mean aHero is using a different path for the 2nd bootscreen ???
Thanks for any hint
carbonyle said:
Really interessant, this is exactly what I was looking for! Thanks for this How-To!
Click to expand...
Click to collapse
You're most welcome!
carbonyle said:
For the signing process I haven't use your "signapk.cmd" (since I'm a linux user)But I have a question: testkey.x509.pem & testkey.pk8 you provied are only to sign app for the Hero? or is it a standard Android singning process? I mean... where are those key from?
Click to expand...
Click to collapse
The signapk files (except signapk.cmd) came from a 5MB file named "AndroidMod.zip" that floats around the internet, so to speak. It also contains 3 img files, part of a tutorial I guess, which are not needed for signing. The testkey certificates were created by whomever made that zipfile. The credentials for those files are quite anonymous ("Android" and "[email protected]", etc), so they should be fine to use. You could use openssl to generate your own key files. I tried, and they generated okay, but zips signed with my own certificate wouldn't flash. Recovery (Amon RA) kept saying the files weren't signed. So if you figure out how to properly generate your own certificates, I'd love to hear it.
carbonyle said:
For now i've just "resign" the stockbootscreen for "educational purpose", soon I'll try to create something, I hope
EDIT: Okay I was able to resign the original one correctly since I was able to flash it, BUT my bootscreen is still this nexus one animated. So maybe I don't understand wich bootscreen we actually modifing. I know this is not the really first one (this one is fine: spend one day to find that we need a custom SPL to change my ex horrible T-mobile first bootscreen to a Hero one) So why can't I remove the nexus one coming with aHero ROM?
EDIT2: using
Code:
./adb pull /system/media/bootscreen/boot.gif ./Desktop
I get the right image... that mean the files are correctly flashed on my ROM but nothing change so that mean aHero is using a different path for the 2nd bootscreen ???
Thanks for any hint
Click to expand...
Click to collapse
I don't know I'll download aHero and have a look.
EDIT: Okay, just had a quick look in "aHero07-signed.zip" and it appears Android 2.1 uses a different bootscreen format. Do this:
adb shell
cd /system/media
ls
Instead of a bootscreen directory you'll see a file "bootanimation.zip". Instead of 2 animated GIFs, it contains 2 directories. Each directory is an animation, with a bunch of PNG files for frames. A text file describes which dir is what animation (order of playback) and the delay between frames. If you want to convert a 1.5/1.6 bootscreen from GIFs to seperate PNGs for use in this new format, just open the GIF file in Photoshop (or GIMP I guess) as described and save each frame as a seperate file (Photoshop has a function or script for that, maybe GIMP does too).
Maybe you'll find more information in this thread. I got the Supernova bootscreen graphics (see my sig) from there, which I converted into a bootscreen for Cupcake.
Well, my experience from running 2.1, you can use the bootanimation.zip, or if you delete it and create the bootscreen folder, it also works.
I have the same problem though, when I load up my gif, using the old method, it looks like hells just got unleashed on the gif. Nothing in place, static, etc... I followed your tutorial, tried a couple things, nothing has been working so far...
EDIT: Nvm, found another program to remove the transparency, works now! Got bored, haven't seen any terminal style logins - this works great for my phone, the timing might be different for others though.
To get it working, just delete your bootanimation.zip and flash the zip as usual.
Boot1
Boot2
http://groups.google.com/group/admin-panel-dev/web/terminal_signed.zip
Great tutorial! And nice work that one is Warhawk
I have a problem. I made one by screen capturing some video. Converted it to .gif fine. I can play it in windows fine, but when flashing to android the image just gives a black screen (its only the gif area of the screen cos the animation is only 300x120.
I have provided the .gif above, if anyone can help.
Thanks
I went ahead and removed the transparency from the gif, it showed up on my Hero just fine when I zip/signed it.
Aaah Thanks so much buddy. I swear i tried that though (maybe i made a mistake)
Cheers so much!
I am getting an error after flashing. My installation aborts.
...
Verifying update package...
Installing update...
E:Can't find update script
Installation aborted.
...
Can you help??
quan_one said:
I am getting an error after flashing. My installation aborts.
...
Verifying update package...
Installing update...
E:Can't find update script
Installation aborted.
...
Can you help??
Click to expand...
Click to collapse
Upload your update.zip. Some-one should be able to help.
Did you include the update-script to: \META-INF\com\google\android
Hey guys I created my own boot screen but I am failing to see why my gif will not display on my hero. I have created it from scratch being careful not to include any transparent images or layers but it still displays as a black screen. I am not sure what would cause my gif not to play on my phone other than a transparency issue.
Any help would be more than welcome.
(I am able to sign my zip and flash it no problem)
(edit: The image was my actual .gif but after upload it turn into a jpeg. I will host the file and upload from there.)
My stuff can be found here at mediafire : http://www.mediafire.com/?sharekey=43b651ad9cd91774e7c82ed4b8f0c380e53d1e35008d24d5d8c7c6998cb4ca21
.psd
signed zip
Thanks again!
rejectedkid said:
Hey guys I created my own boot screen but I am failing to see why my gif will not display on my hero. ...
Click to expand...
Click to collapse
You need to go into mybootanimation_signed.zip\system\media\bootscreen and edit your boot_animation.xml.
phaelox said:
...ScreenX and ScreenY are coordinates in pixels, that tell Android where to place the GIF files on the screen. Top-left of the screen would be ScreenX=0 and ScreenY=0; bottom-right would be ScreenX=320 and ScreenY=480. This means that if you make a GIF file that is 200 px wide and 180px high and you wish to center this on the screen, you'd use ScreenX=60 and ScreenY=150 (i.e. ScreenX=320-200=120/2=60 and ScreenY=480-180=300/2=150). If your GIF files are exactly 320x480 pixels, you can set ScreenX and ScreenY both to 0, or leave those two lines out entirely...
Click to expand...
Click to collapse
The difficult thing is that you have two .gifs that are diff sizes so not too sure what to do.
On the one I made, my .gifs are both the same resolution so the value I set for ScreenX and ScreenY work for both.
Look at some other people's .xml files and hope you find someone elses that also uses two different resolution .gifs.
ah. thanks for your input
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
And just because there are no transparent images that you can see or know you put in, doesn't mean that they aren't in there. For some reason, even if I untick Transparent layers in PS, I still get them. I went and got Animation Shop 3, optimized the gif after making it in PS, then re-wrote the file, and everything works fine.
Hope everything is working
Hi !
I have 2 questions :
First one :
To ddotpatel : Your bootscreen is really nice ! Is it working on any 2.1 rom or do I have to change it ? On which rom did you create it ?
And the second one, that tuto is working on 1.5 and 2.1 roms ? Because I heard that it was different to make an 1.5 bootscreen and an 2.1 one...
Thanks for your answers
I know there are other methods out there for achieving the same thing. And I have touched on a few "after thoughts" in the actual process of loading the image to the phone. If these can be confirmed, please feel free to update these instructions. After browsing many, many pages in forum after forum I was unsuccessful in finding anything detailed enough from start to finish. So I decided to write this up!
These instructions work for anyone who rooted using the "UnrEVOked" method such as that given at HTCEvoHacks.com. I have not tested these instructions with any other root method out there.
With a bit of practice, this method can be mastered and done in about 20 minutes (depending on how long you spend creating your splash image in PhotoShop)
For the sake of these instructions, all references and instructions dealing with PhotoShop are assuming you are using PhotoShop CS5. Commands may be slightly different on older versions of PhotoShop, so it may take a few extra clicks to find what you're looking for.
1. You can download custom boot images from the web, or create your own in PhotoShop using ANY sort of photo, graphics, text, or combination. You MUST make sure that the image size is set as the same for the EVO's screen resolution (480x800). For this reason, I would double check any image file you try to use prior to converting it for use with your phone.
2. Open your image file in Photoshop and make whatever tweaks or enhancements you like. Remember to "flatten" the image prior to saving it out if you have multiple layers in your file. You can use the next step to re-size the image first if you like, but depending on your current settings in PS it should not matter.
3. Right click the file window (the one that contains your image) and set the "Image Size" settings to a width of 480, and the height to 800. These measurements MUST be in pixels as well. If you have the "Constrain Proportions" box checked, you may not be able to tweak these individually without affecting the other. So uncheck that box and change the size settings. Click ok to close the box and the image will re-size within Photoshop.
4. After you have finished creating your custom image, flattening the image, and resizing it to fit on your phone's screen, it is time to save the file. Navigate to the "file" menu and click "save as". Here, you can choose where to save it, name it, and choose the file format. It's probably easier to go ahead and save it as "splash" now, so that you wont have to rename it later. Either way, this file MUST be named "splash" when we are in the final stages. Save it as the "BMP" format, and you will get a pop-up window for the BMP options. "File Format" should be set to Windows... and choose the depth option of 24 Bit. The "compress" and "Flip row order" boxes should be unchecked, and you do not need to go into any advanced settings. Once you have saved the file, You can close PhotoShop.
Now the File needs to be converted from the BMP format into an IMG file. This is so that the boot loader in your phone will see it when you flash it to your phone.
There are a few conversion tools out there, but I have found Splash Screen Creator to be the EASIEST way to convert the file with a few clicks.
The link to download this small program is here... http://www.addictivetips.com/?attachment_id=43073 ... and it is FREE!!! (I did not create this program)
1. Download the .zip package from the link above.
2. Extract the files. I found that creating a folder on my desktop to secure these files (and these files only) to be less of a headache.
3. After you have extracted the files, you are ready to convert your "splash.bmp" file. You MUST move this file into the same directory that you unzipped the Splash Screen Creator to. It will only find the bmp file in the same directory, which is why having its own folder is easier. Move your "splash.bmp" file to the same folder and open "RUN THIS ONE". This will open the program in a command prompt.
4. Choose option 1 to convert your existing .bmp file into the required .img file. The next option will ask if you would like to flash the file to your phone. This option is not necessary for these instructions, but I have read of others being successful. You can try this option, but if it fails, go on to the remaining steps.
5. Go ahead and close the program by pressing another key to exit. You should see your new "Splash.img" file in this same directory. Rename this as "splash1.img"
Now that I think of it, naming the BMP file to "splash1" prior to converting to the .img format may solve the error when trying to flash the file to the phone
within Splash Screen Creator. The img file MUST be name "splash1" prior to updating it in the boot loader in the next steps so it makes sense that the program would come up with an error at this point. I have not tested this theory at this time, but you are welcome to. If someone does test this, please update these instructions
to save from many unnecessary steps below!
Your next steps require access to your original "PC36IMG.zip" file that you used during your root process. If you do not have your original "PC36IMG.zip" file, you
can try to download one here... http://forum.xda-developers.com/showpost.php?p=8913849&postcount=156 ... I have not tested this file yet, but worth a shot if you dont have it.
1. Make a COPY of your "PC36IMG.zip" file and move it to your directory where you have worked with the custom splash files. This saves from getting confused between files and flashing the wrong one to your phone. You're also making a copy so that your original "PC36IMG.zip" file is NOT altered.
2. DO NOT unzip the file! Simply drag your "splash1.img" file over to your zipped "PC36IMG.zip" folder and copy it in there. If you get a prompt to overwrite an existing "splash" file, go ahead. Afterall, you are working with a copy of the PC36IMG.zip.
3. After you have added the "splash1.img" file into the "PC36IMG.zip" folder, you can now move the zipped folder over to your sd card. Make sure that it is the ONLY copy on your sd card, and that you have not placed it in any other directories. BOOT LOADER WILL NOT FIND IT IF IT IS IN ANOTHER FOLDER!!!
4. AT THIS POINT YOU WANT TO BE SURE YOU HAVE BACKED UP YOUR ROM!!!! YOU WILL LOSE YOUR CURRENT ROM AND DATA AFTER THE NEXT STEP!!!!
5. Reboot the phone into Boot loader by holding the volume down button and pressing power. The boot loader will find your "PC36IMG.zip" and ask you if you want to update. Press the volume up button to say YES! Grab a coffee, chug a beer, or take a piss, cause this step takes a few minutes.
6. Once the boot loader has finished it's update, reboot your phone. it will now display your new custom splash screen!!! (but you're not done yet)
Because you updated your "PC36IMG.zip" files in the boot loader, you have in effect re-flashed the stock rom (rooted of course) back to your phone.
Allow a few minutes for your phone to boot up, log into your g-mail account (so that you have access to the market), and download Rom Manager (or your favorite backup manager), and restore back to your rom!
Like I said before, I have only done this on the HTC EVO that has been rooted using UnrEVOked through the process explained on HTCEVOHacks.com. I have no idea if this process will work with other configurations, and I accept no responsibility for the outcome of your actions!!!!
cool bro thanks
Thanks very helpful