Database Info

Extra Mod for Haykuro's H Users...

I was messing around with one of my update files on winrar and opened system/Media. There I found boot.gif and boot.mp3 which both play at start up with the htc logo and sound. So I decided to change both with my own. So I did then I signed the update zip and flashed. Worked like a charm, sorry if someone beat me to this if you guys already knew then ill just delete the thread.
How To:
1. You must have a copy of the build/rom you are using. You can use the last update.zip you've used to flash to your latest rom.
2. Open up the update zip file using winrar or whatever unzipping tool you use.
3. Once unzipped goto system/Media.
4. Here you will see two files boot.gif and boot.mp3 these are the files you are going to mod.
5. Editing boot.gif, find a replacement animated gif file you would like to use and rename to boot.gif and add it to the archive replacing the original. MUST BE A .GIF FILE ONLY!
6. Editing boot.mp3, you do the same procedure as step 5 but replace with a mp3 file. MUST BE AN MP3 FILE ONLY!
7. When finished put the update.zip you just edited place on the root of sd card and flashhhh!
8. HAVE FUN!
Alternative with adb without wipe thanks to: Andonnguyen
adb remount
adb shell
#cd /system
#cd /media
#rm boot.gif
#rm boot.mp3
#mv c:\locationoffile\boot.gif /system/media/boot.gif
#mv c:\locationoffile\boot.mp3 /system/media/boot.mp3
#reboot
{
"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"
}
​
Could not add the boot.mp3 but here it is the linux mandriva boot sound.
link to boot sound here:
http://www.zedge.net/ringtones/567398/mandriva-startup-ringtone/

Nice find! Too bad I just got everything set up the way I like it. I'll probably be flashing again on "Firmware Friday." I'll try this out then!
I've got about a million ideas for what I want my phone to do when I turn it on....

Yea its great, I currently have an android dancing gif instead of the htc and Pitbull I know you want me for the boot sound lol. I put it on just to test and now that I know it works, I will also be changing it to something sick on firmware Friday...

There is One big problem
How you sign your update ...
When I used auto sign to signed my mod ... I have a error in recovery mode

aluspl said:
There is One big problem
How you sign your update ...
When I used auto sign to signed my mod ... I have a error in recovery mode
Click to expand...
Click to collapse
Which auto signer are you using? I suggest using Stericson's also make sure your singing the whole update.zip

So this really does work?

i may try this for the next update as well, good find

Anyway you can make a how to or point me to the direction of this information?

Nikeem24 said:
So this really does work?
Click to expand...
Click to collapse
Yup, i've tested and it works.

As an alternative method (for those who don't want to wipe), modify the boot.gif and boot.mp3 then place them somewhere on your hard drive. Next type the following commands in ADB while your G1 is connected via USB to your computer:
adb remount
adb shell
#cd /system
#cd /media
#rm boot.gif
#rm boot.mp3
#cp c:\locationoffile\boot.gif /system/media/boot.gif
#cp c:\locationoffile\boot.mp3 /system/media/boot.mp3
#reboot
Click to expand...
Click to collapse
STERICSON (or anyone familiar with editing the xml files on android), please read below:
In the H builds of 1.5, there is also an xml file called boot_animation.xml in /system/media, the contents are as follows:
<?xml version="1.0" encoding="utf-8"?>
<!--
* Copyright (C) 2008 HTC Inc.
*
-->
<!--
<BootConfiguration>
<BootAnimation
image="/system/media/boot.gif"
audio="/system/media/boot.mp3"
image2="/system/media/boot2.gif" (optional)
image3="/system/media/boot3.gif" (optional)
screenX="100" (optional)
screenY="130" (optional)
image_bg = "/system/media/boot_bg.gif" (optional)
useAudio="0" // 1: true ; 0:false (optional)
/>
</BootConfiguration>
-->
<!-- Demonstrates configuration for application -->
<!-- Remove background
<BootConfiguration>
<BootAnimation
image="/system/media/boot.gif"
image_bg="/system/media/boot_bg.gif"
audio="/system/media/boot.mp3"
screenX="100"
screenY="130"
useAudio="1"
/>
</BootConfiguration>
-->
<BootConfiguration>
<BootAnimation
image="/system/media/boot.gif"
audio="/system/media/boot.mp3"
useAudio="1"
/>
</BootConfiguration>
Click to expand...
Click to collapse
It looks as if we can manage to load multiple animated gif's during the boot process after splash1 and splash2 images. Could you please look into this, and offer any input as how to modify the xml to allow this?

Ok it seems as if the boot gif when changed gets disorted now for some reason, will look into it.

andonnguyen said:
STERICSON (or anyone familiar with editing the xml files on android), please read below:
In the H builds of 1.5, there is also an xml file called boot_animation.xml in /system/media, the contents are as follows:
Click to expand...
Click to collapse
Well the first 2 BootConfiguration tags have been commented out. To comment in xml you type <!-- before your comment and --> after your comment.
Try removing the comment code on the first BootConfiguration and adding comments to the last one. also make sure to remove the (optional), then upload the images using your adb method and see if it works.
Below i cleaned the code up a bit. So you can copy that into your xml.
Also I changed the useAudio to 1 which means yes.
Code:
<BootConfiguration>
<BootAnimation
image="/system/media/boot.gif"
audio="/system/media/boot.mp3"
image2="/system/media/boot2.gif"
image3="/system/media/boot3.gif"
screenX="100"
screenY="130"
image_bg = "/system/media/boot_bg.gif"
useAudio="1"
/>
</BootConfiguration>
This is the last BootConfiguration in the xml. The middle one is just a demonstration. I wouldn't delete it though, Android might be expecting a certain file size.
Below is the current active BootConfig which i added the comment tag around.
Code:
<!--
<BootConfiguration>
<BootAnimation
image="/system/media/boot.gif"
audio="/system/media/boot.mp3"
useAudio="1"
/>
</BootConfiguration>
-->

So is there anywhere, where there are already made boot screens that i can just get the file and replace it

Jrbourque said:
So is there anywhere, where there are already made boot screens that i can just get the file and replace it
Click to expand...
Click to collapse
Yes search google for any gif files and just replace, same for the boot sound. I know have a cool setup ill upload now.

diaztradeinc said:
Yes search google for any gif files and just replace, same for the boot sound. I know have a cool setup ill upload now.
Click to expand...
Click to collapse
does it have to be a certain size?

Jrbourque said:
does it have to be a certain size?
Click to expand...
Click to collapse
I'm thinking the gif might have to be a certain size because my recent boot gif is distorted when animating. Check first page for boot gif and boot.mp3

adb remount
adb shell
#cd /system
#cd /media
#rm boot.gif
#rm boot.mp3
#mv c:\locationoffile\boot.gif /system/media/boot.gif
#mv c:\locationoffile\boot.mp3 /system/media/boot.mp3
#reboot
Click to expand...
Click to collapse
^^Not working for me; i keep getting the error msg "failed on 'C:\boot.gif' - No such file or directory"
And yes, my boot.gif file is saved in the C:\ directory.
Perhaps it needs to be saved on the sdcard to work? i'll try it and report back.
Edit: SUCCESS. I placed my modified boot.gif and boot.mp3 files on the sdcard, then used the following commands:
adb remount
adb shell
#cd /system
#cd /media
#rm boot.gif
#rm boot.mp3
#cp /sdcard/files/boot.gif /system/media/boot.gif
#cp /sdcard/files/boot.mp3 /system/media/boot.mp3
#reboot
Click to expand...
Click to collapse
And now my man John Stewart (the black Green Lantern... not the Comedy Central host) greets me to the tune of Kanye West's "WE MAJOR".

diaztradeinc said:
I'm thinking the gif might have to be a certain size because my recent boot gif is distorted when animating. Check first page for boot gif and boot.mp3
Click to expand...
Click to collapse
So you're having the same problem I am then? I analyzed the CRAP out of the original boot.gif, and compared it to a customer animated gif I attempted to completely customize my bootup w/ to no avail. I even modified the original boot.gif trying to place text and extra graphics on the existing frames, saved, and the modified version of the boot.gif glitched out too.
So as a test (since I'd only been trying to run modified/created animated gifs after about 3-4 hours of analyzing trying to figure out the difference) I replaced the boot.gif w/ a regular animated gif.
The boot automatically centers the gif (in this case it's not the 320x480 scale of the original boot.gif)... but it's still distoreted. Here are some pictures as an example
this gif -
doesn't animate at all. appears to show 3 different frames all glitched out and looks like this -
Any light anyone can shed on this would be greatly appreciated =( I'd absolutely love to customize my OWN animated gif for my boot image.

what size is it suppose to be?

Transformer Sound Effect
You wouldn't believe how hard it is to find the Transformer sound effect from the 2007 Movie. I finally gave up and used this one here. I kept the stock HTC.gif (H build) because it's timed right with the sound. Just thought I'd post in case anyone else had the same idea. If anyone finds a clean morph fx file, pm me.

LED debugging in Hero (6-22-09)

WOW OK SO I FINALLY GOT LED's WORKING IN HERO!!!
This means they can be manipulated via Terminal but not the Android OS. That will be the next step.
*IMPORTANT 4:50pm CST*
-Correction, you should be copying/symlinking sensors.msm7k.so to sensors.trout.so and not sensors.hero.so to sensors.trout.so. Please see updated instructions below.
If you already copied sensors.hero.so to sensors.trout.so then do the following to fix it. Following the previous instructions could affect auto rotate
Code:
rm /system/lib/hw/sensors.trout.so
ln -s /system/lib/hw/sensors.msm7k /system/lib/hw/sensors.trout.so
*Update 4:44pm CST*
-Changed copy commands to symlink so we save space on /system. Thanks for the tip chunga
*Update 6:01pm CST*
-If you're getting an issue where auto-rotate is no longer working it's most likely you fudged on the symlinking sensors.msm7k.so over to sensors.trout.so.
*Update 9:37pm CST*
-Forgot to add that you need to have /system remounted as read/write. I have added the command below
*Update 8:00pm CST*
The following command does not persist across reboots, therefore it will need to be placed in /init.rc or in /system/init.rc if you have a modded rom that allows for it. Just so everyone is clear, you can NOT edit /init.rc directly. To do that you'll need to unpack boot.img, edit init.rc, then repack boot.img and fastboot flash it to your device. My advice is to download a modded ROM that gets released with this fix.
Code:
echo "1" > /sys/devices/platform/i2c-adapter/i2c-0/0-0062/blink
It was a pretty trick fix to figure out. Here is a revised post with the complete terminal commands. ROM devs you could place these chmod commands in /init.rc to get it working. Please give credit where credit is due if you use my fixes.
Code:
[B]TERMINAL COMMANDS[/B]
mount -o rw,remount /dev/block/mtdblock3 /system
ln -s /system/lib/hw/lights.msm7k.so /system/lib/hw/lights.trout.so
ln -s /system/lib/hw/copybit.msm7k.so /system/lib/hw/copybit.trout.so
ln -s /system/lib/hw/sensors.msm7k.so /system/lib/hw/sensors.trout.so
echo "1" > /sys/devices/platform/i2c-adapter/i2c-0/0-0062/blink
chmod 666 /sys/devices/platform/i2c-adapter/i2c-0/0-0062/leds/blue/brightness
chmod 666 /sys/devices/platform/i2c-adapter/i2c-0/0-0062/leds/red/brightness
chmod 666 /sys/devices/platform/i2c-adapter/i2c-0/0-0062/leds/green/brightness
What's left to fix?
1) Currently the system is only giving the LED's a brightness of 1 so the light that comes on is dim. We need to find where it's getting this default value and up it to 100.
Want to manually change the colors?
You can edit the "brightness" value under leds/[blue/red/green] . The acceptable values are from 0 - 100. If you mix them up you can make any color you want
Exampe to change colors manually:
Code:
echo "50" > /sys/devices/platform/i2c-adapter/i2c-0/0-0062/leds/blue/brightness
echo "50" > /sys/devices/platform/i2c-adapter/i2c-0/0-0062/leds/red/brightness
This would make a purplish color.

okay so does it change colors when its charging after its cut on.

I believe the hero has dual LEDs. It says something about it in logcat...Let me see if i can find it.

jaygajay said:
I believe the hero has dual LEDs. It says something about it in logcat...Let me see if i can find it.
Click to expand...
Click to collapse
Yes it does in fact have dual LED's. So the trick now that LED's work is to get it working just like it was in cupcake. I'll keep working at it you can be sure of that

wizern23 said:
okay so does it change colors when its charging after its cut on.
Click to expand...
Click to collapse
I haven't seen it change colors as my phone is fully charged so the green LED comes on. Since we don't have bluetooth I can't check for the blue LED working. Anyone have chompsms installed? I know you can pick which LED color you want. Anyone wanna test that it's all working?

Terminal codes?
Hello! Thanks for the great fix!! But is there anyway you can post the entire terminal emu code? Kinda new on the copying and replacing of files. Thanks so much !

Try missed call, you can easily sample the different colors

phungshum said:
Hello! Thanks for the great fix!! But is there anyway you can post the entire terminal emu code? Kinda new on the copying and replacing of files. Thanks so much !
Click to expand...
Click to collapse
I updated the main post so others can easily find it

phungshum said:
Hello! Thanks for the great fix!! But is there anyway you can post the entire terminal emu code? Kinda new on the copying and replacing of files. Thanks so much !
Click to expand...
Click to collapse
this is actually editing the init.rc script... what do i open that in to edit it? and after edit can i just remount my system as writable and change the file names in my sys/lib/hw folder to the explained file names?

Zarboz said:
this is actually editing the init.rc script... what do i open that in to edit it? and after edit can i just remount my system as writable and change the file names in my sys/lib/hw folder to the explained file names?
Click to expand...
Click to collapse
You can type those commands from the terminal. If ROM devs want to make it so installing their ROM automatically does this, they would do it in init.rc.
You and I can do this from the terminal. It should hold those changes across a reboot. Hmmmm, lemme reboot and make sure otherwise it would require unpacking/repacking the boot.img and making the changes to init.rc in there. You can not edit init.rc directly. You have to extract boot.img (you can get this from the ROM you installed). Do a search for unpacking/repacking boot.img

great news

Good job shafty.

tried it, works, restarted my phone by itself after the echo though. Little confuse about the chmod stuff so not gonna try that yet. Oh did it in adb too, thanks.
EDIT: seemed to break my 'g-sensor', so no auto-rotate.

this is going into 1.65 Thanks shafty023 for the work!

running jacman hero and his lights.msm7k.so is already renamed do i need to worry about this and after the chmod lines after the /brightness/ can i enter a modifier to change the ammount of light given out?

just to clarify the terminal commands,
using JACMAN 1.64, files are already renamed.

Zarboz said:
running jacman hero and his lights.msm7k.so is already renamed do i need to worry about this and after the chmod lines after the /brightness/ can i enter a modifier to change the ammount of light given out?
Click to expand...
Click to collapse
Ya that's because he got it from justanothercrowd who got it from me. I was sending him most of my fixes directly since I'm using his ROM. Only seemed fair.
So you can ignore the line pertaining to lights.msm7k.
Yes you can feel free to change the value in brightness to whatever you want. I actually think the max is somewhere around 256. You can mix brightness values and that will allow you to change the colors manually. But unfortunately when you plug an a/c adapter it turns on the green led at a brightness value of only 1

so for example at the endo f my chmod 666 .... /brightness/100 ?? or would it be /brightness100

cool! thanks for the fix!

did nothing for me? wonder what i did wrong

[HOW-TO] ROM-HACKING: init.rc ext2-auto-mount / ROM Signing / ROM Kitchen

AS MENTIONED IN THE INTRODUCTION TEXT THIS HAS ONLY BEEN TESTED ON AMON RA ROM 1.6.2 BUT SHOULD REALLY WORK ON ANY ROM THAT HAS NO EXT2 AUTO-MOUNT. AND YEAH THIS WHOLE PROCESS HAS BEEN DONE ON A 32a BOARD. FOR THOSE THAT TRY THIS ON OTHER ROMS LET ME KNOW HOW IT GOES.
I've searched and shuffled through the entire forum and made inquiries to ROM authors without much light being shed on this issue. I doubt I am the only one who has been looking for a way of doing this so I decided to do a small HOW-TO. Here I will explain step by step as to how you can implement a script to be part of your ROM that will auto mount an ext2 partition on boot up if such partition is present. I have included all the tools I've used in order to pull this off, and as the title suggests this has only been done on Amon Ra's latest 1.6.2 ROM. In order to follow these instructions you are expected to allready have set up an adb enviroment on your linux box and for the signing process to work you must have sun-java present, the gnu java wont work. And of course a microSD card with an ext2 partition
1. Download install.sh to your home directory
Code:
wget http://www.grindhouse.no/androidtools/install.sh
chmod a+x install.sh
2. Now execute the install.sh script which will create a directory to work in and download a tool and script package and unpack it.
Code:
./install.sh
When the install.sh script is done you need to move the mkbootimg preferebly to your tools directory of your SDK.
Code:
mv toolstomove/mkbootimg <path/to/sdk/tools/mkbootimg>
3. Unpack the RA1.6.2 ROM into a directory in your home dir. In this HOW-TO we will use directory name "ra1.6.2" as an example through out the entire process.
4. Copy the boot.img from ra1.6.2 to the ROM-cooker dir
Code:
cp $HOME/ra1.6.2/boot.img $HOME/ROM-cooker/boot.img
cd $HOME/ROM-cooker
5. Use unpack.pl to extract the ramdisk from the boot image. I've modified the script a little so it automates the entire process and decompresses the ramdisk to a directory
Code:
./unpack boot.img
6. Now you can either replace the init.rc file here with the one I've included in this package or you can add these lines by yourself. In wich case do the following
Code:
cd boot.img-ramdisk
pico init.rc
Press CTRL+w and then CTRL+t and input 27. hit enter. This will take you to line 27 of init.rc so you can add a line right before the init process remounts the rootfs in read-only mode. Add following line:
Code:
mkdir /sdext2 0771 system system
Now scroll down to the end of the init.rc file and add the following:
Code:
service mountsdext2 /system/bin/mountsd
user root
group root
oneshot
7. You have now edited (or replaced) your init.rc file and prepared it to execute a script on boot that will detect an ext2 partition and boot it if there is one to be found. Now you have to make the mountsd script a part of the ROM. Do the following:
Code:
cd $HOME/ROM-cooker
mv toolstomove/mountsd $HOME/ra1.6.2/system/bin/mountsd
rm -rf toolstomove
8. Now that the init.rc file is sorted out and mountsd has been placed in /system/bin of the ROM so it is time to re-pack the boot.img:
Code:
cd $HOME/ROM-cooker
./repack boot.img-kernel boot.img-ramdisk boot.img
rm $HOME/ra1.6.2/boot.img
mv boot.img $HOME/ra1.6.2/boot.img
9. Your ROM now has a new boot image with an updated init.rc and the /system/bin dir has the script needed to auto-mount the microsd ext2. Now you must re-zip the ROM and sign it. Do the following:
Code:
cd $HOME/ra1.6.2
zip -r update.zip *
mv update.zip $HOME/ROM-cooker/update.zip
cd $HOME/ROM-cooker
./sign.pl update.zip
10. The ROM is now signed and you now have a file called update-signed.zip. Connect the phone to your computer and execute thus:
Code:
./push update-signed.zip
11. Now you are ready to flash the modified ROM which will auto-mount an ext2 partition on your microSD. There is no need to wipe before flashing. If you have no prior experience with ROM flashing or whatever just backup your current install. If you're using OpenHOME or anything similar, nothing will be changed or damaged but if you're using MontAlbert's themes with the ROM you will have to flash them again after flashing this modified ROM.
Code:
adb reboot recovery
12. Flash from choose zip and of course choose update-signed.zip. Reboot. After the system boots up again you can now check whats what with either one of the commands:
Code:
[email protected]:~$ adb shell mount | grep sdext2
/dev/block/mmcblk0p2 on /sdext2 type ext2 (rw,noatime,nodiratime,errors=continue)
[email protected]:~/boot$ adb shell busybox df -h | grep sdext2
/dev/block/mmcblk0p2 893.7M 13.0K 846.0M 0% /sdext2
13. Voila! Your RA 1.6.2 ROM now detects and mounts your microSD ext2 partition on boot. Woohoo?
I hope the HOW-TO was easy reading and that you have succeeded in hacking up your ROM. I know that certain ROMs have this as a built-in function but Amon Ra's does not. But since alot of people including myself use his ROM because of the high speed and stability I thought I should contribute to his project and add a cool (and missed?) function to it.
Mind you that you can use the ROM-cooker set to further adjust and hack up the ROM as you see fit. Happy learning!

Very nice!
Now the question many people will ask : why would you automount ext2 if you don't use apps2sd ?

I personally have ubuntu on my ext2 And besides this approach can be used for a number of things, people who have had the need, or wanted to experiment with init.rc doing things on boot, the mountsd script can easily be altered to do what ever needed.
For me its been a learning curve finding these things out, so by sharing it I may spare some people breaking their backs over this whole init.rc thing. people may want to modify init.rc for whatever reason, so I'm sure people wont have a problem finding a way of putting this to use, and its a subject that isnt all that covered on the forum .. and hey .. at least they get a rom kitchen out of the whole shabang

Very interesting! Thank you.
I used your unpack-program to unpack a recovery-image. It seems to work fine. What I am trying to do is change the state the recovery-image returns the phone to. Would it be possible to just replace your mountsd-script with, for example, a script that installs apps? Or is there a better way to do what Im trying to achieve?
Cheers,
edit: I noticed that on the emulator it is sufficient to just place an apk-file in "data/app" to get it installed. Could it be possible that this is all I need a script to do? :O or could I hurt my poor phone by doing so you think?

sandis84 said:
edit: I noticed that on the emulator it is sufficient to just place an apk-file in "data/app" to get it installed. Could it be possible that this is all I need a script to do? :O or could I hurt my poor phone by doing so you think?
Click to expand...
Click to collapse
That's indeed all you need to do.

Hi!
So I tried to create a signed update.zip, but it failed. It didnt create a "update-script"-file, so my device refused to install it. I wrote my own "update-script"-file, but then it complained "no digest" for the file. How do I solve this?

post the contents of your script people might see whats up

so is this all on linux?
also where are the script files for your tutorial
thanks for the time to put together

sitimber said:
so is this all on linux?
also where are the script files for your tutorial
thanks for the time to put together
Click to expand...
Click to collapse
Says where its at in the first line : )
Code:
wget http://www.grindhouse.no/androidtools/install.sh
But now that I checked, I have to apologize, I see I have a missed payment with my hosting, I'll fix that within the day. Also sorry I havent been answering the few questions here I've been afk cause of surgery.

sitimber said:
post the contents of your script people might see whats up
Click to expand...
Click to collapse
well, I looked in another "update-script" file and found this:
assert compatible_with("0.2") == "true"
assert getprop("ro.product.device") == "dream" || getprop("ro.build.product") == "dream"
show_progress 0.5 0
write_radio_image PACKAGE:radio.img
show_progress 0.5 10
Click to expand...
Click to collapse
So I figured that nothing was essential other then the line "write_radio_image PACKAGE:radio.img". Also ofcourse I made sure it contained the name of my image-file instead of "radio.img". This gave me the "no digest" message, so now I feel unsure on how to create a working update.zip.
edit:
SOLVED! How silly of me. When you sign the update, a hash of each file is put in manifest.mf. Since I added the update-script after signing the file, ofcourse the digest(hash) was missing. Now everything works alot better and I can proceed... until I get stuck again
Cheers,
edit2:
Just to get a better understanding, what exactly does each line do here? Or where can I read about this?
Code:
service mountsdext2 /system/bin/mountsd
user root
group root
oneshot
edit3:
Ok, so I have experimentet, but I still dont manage to solve those last steps. I tried to edit init.rc and just add "mkdir /testdir 0000 system system" where the other directories were created. I then repacked it, zipped it, signed it, put it on my sdcard, started up a custom recovery, installed the update and rebooted. Everything seems to work fine. But when I start adb and check around, I dont see the "testdir"-directory. Also when I check in init.rc my line is gone. Do you guys have an idea of where I went wrong?

sitimber said:
so is this all on linux?
also where are the script files for your tutorial
thanks for the time to put together
Click to expand...
Click to collapse
it doesnot necesarily have to be linux ...you can also do it in windows using cygwin and dsxda's android rom kitchen

[TUT] Change the leo splash screen (first screen after boot)

You just run in dos mode the nbimg 1.1 tool of pof from here
http://forum.xda-developers.com/showthread.php?t=405118
and you put the following parameters:
nbimg -p 18400 -w 480 -h 800 -F nameofphoto.bmp -T 0x601 -S 64 -D PB8110000
Flash the nbh file that is created ( i attach a sample in zip file ready for flashing) and you done it.You only flash the boot image, i mean the one that has the number of radio and rom at the bottom, and nothing else, radio and rom remain unchanged.Follow exactly the commands (capitals or not capital letters).
There is another image that appears just before the image that has the number of rom and radio.This can be changed if you replace the 601 with 600 in the parameters described above (tip goes to Chri55tof in post 2).
So you just need 2 bmp photos 480x800 24bit and the pof nbimg1.1 tool with the parameters i described above, piece of cake.
If you dont like it returm to the stock splash attached below.
Enjoy

Downloaded the file (from link you provided), made a 24bit .bmp file I wanted to use ... followed the command line, flashed to my HD2 and it works !!
Great job !
K.
EDIT :
By the way, flashing .nbh file done that way will replace 2nd splash screen. How to replace first screen ? (the one with white background and green htc trademark) ???
EDIT2 :
Just found it !
0x600 is changing 1st splash screen
0x601 is changing second (not like you stated in topic of this thread !)

What you mean ?
The second screen is the animation which is an animated gif file.
-T is the header type.
I attach the kind of settings:
Mandatory arguments:
-F <filename> Filename to convert.
If the extension is BMP it will be converted to NB.
If the extension is NB it will be converted to BMP.
Optional arguments:
-w <width> Image width in pixels. If not specified will be autodetected.
-h <height> Image height in pixels. If not specified will be autodetected.
-t <pattern> Manually specify the padding pattern (usually 0 or 255).
-p <size> Manually specify the padding size.
-n Do not add HTC splash signature to NB file.
-s Output smartphone format.
NBH arguments: (only when converting from BMP to NBH)
-D <model_id> Generate NBH with specified Model ID (mandatory)
-S <chunksize> NBH SignMaxChunkSize (64 or 1024)
-T <type> NBH header type, this is typically 0x600 or 0x601Example to convert a NB to BMP:

I mean `the very first screen`
This is the one with white BG and green `htc` trademark (the one before `reds` coming out)
0x600 is responsible to change this
0x600 next splash screen

Hi,
Q: So the second one is the animated one?? I'm talking about that one with 'quietly brilliant' ? It comes with the sound - how to change this sound?

pepesz said:
Hi,
Q: So the second one is the animated one?? I'm talking about that one with 'quietly brilliant' ? It comes with the sound - how to change this sound?
Click to expand...
Click to collapse
The sound is the HTC-QuietlyBrilliantBoot.wav in windows folder and the original animated gif (LEO_animated.gif) also in windows folder is attached
Read here
http://forum.xda-developers.com/showthread.php?t=625911

Thanks a lot

0x600 changes Carrier Bitmap (1)
0x601 changes Welcomehead (2)
Animation (3)

chri55tof said:
0x600 changes Carrier Bitmap (1)
0x601 changes Welcomehead (2)
Animation (3)
Click to expand...
Click to collapse
You dont have to do the procedure for changing the welcomehead,bmp because you just replace directly in windows file or cook the bmp file.
The 1st screen with the red letters at the bottom with radio and rom numbers needs to be flashed as is the only way to replace it.

My little contribution ^^
Enjoy !

NIKOSXRI said:
You just run in dos mode the nbimg 1.1 tool of pof from here
http://forum.xda-developers.com/showthread.php?t=405118
and you put the following parameters:
nbimg -p 18400 -w 480 -h 800 -F nameofphoto.bmp -T 0x601 -S 64 -D PB8110000
Flash the nbh file that is created ( i attach a sample in zip file ready for flashing) and you done it.You only flash the boot image, i mean the one that has the number of radio and rom at the bottom, and nothing else, radio and rom remain unchanged.Follow exactly the commands (capitals or not capital letters).
So you just need a bmp photo 480x800 24bit and the pof nbimg1.1 tool with the parameters i described above, piece of cake.
If you dont like it returm to the stock splash attached below.
Enjoy
Click to expand...
Click to collapse
Once I enter the command lines, it says "could not open "picture name".bmp? Am I missing something?

daleandla said:
Once I enter the command lines, it says "could not open "picture name".bmp? Am I missing something?
Click to expand...
Click to collapse
Check again and follow the command line exactly

My Contribution
NIKOSXRI said:
Check again and follow the command line exactly
Click to expand...
Click to collapse
Boom baby. Got it. Here's my contribution...

How do change from second splash screen. (Not the first screen or bios animation)

technomania34 said:
How do change from second splash screen. (Not the first screen or bios animation)
Click to expand...
Click to collapse
You change the welcomehead.png in Operator Pkg, 480x800 24 bits per pixel.
I attach a sample picture which you may use.

is there anyone that has the original 2nd splash bmp file or as a nbh file?
Found it

NIKOSXRI said:
You change the welcomehead.png in Operator Pkg, 480x800 24 bits per pixel.
I attach a sample picture which you may use.
Click to expand...
Click to collapse
Thanks mate

why isn't this or a link to this thread (or similar) in the sticky/wiki at the top?

A word of warning. when you create and flash a splashscreen using the 0x601 memory location, it is not removed when you flash a stock rom. (Tested with several stock roms)
Stock splashscreens are flashed to the 0x600 memory location, and shows for 14 seconds. 7 Seconds when teh phone boots, and 7 seconds when the RGD info shows.
When you have a second splash in place, it shows the first splash for 7 seconds, then the second splash when the RGD info shows for 7 seconds.
The implications of this are that if you need to send back your phone, and you flash a stock rom, your custom second splash will still show.
To remove it (well, make it look like it was gone) I had to make a duplicate of the stock splash and flash it to the 0x601 location, so that it looks like one long splash. (As i found out when i had to return mine to o2.)
More reading

[1st boot & 2nd splash ]
4 HD2 Leo :: choose your BMP shot for it
HERE

Overlays to modify framework-res.apk configuration

Hi all:
I am new to xda-developers but a very experienced software designer.
In attempting to enable Google Voice calling on my new Nexus 7, I followed some threads here that
showed how to enable config_voice_capable in framework-res.apk via decompiling and rebuilding. It occurred to me that there
might be a more direct method for resource changes and I discovered, also
in here a post at http://forum.xda-developers.com/showthread.php?t=1842302&nocache=1,
indicating the built-in overlay feature in android, for modifying resources at runtime.
I thought this looked promising and tried it out. I just wanted to confirm that it works well. I was unable to post in that
thread because I am new here, but I thought it would be worthwhile documenting what I did, for the benefit of
others.
I tested this method to enable 2 booleans in framework-res.apk but I believe it will work with any resources.
The booleans I enabled for testing were "config_voice_capable" and "config_enableLockScreenRotation".
All that is required on a rooted device is the following:
1. On your development machine (with aapt and other platform-tools installed).
switch to any directory of your choice for development purposes and
under it create a res/ directory for the resources you wish to change. Under this directory
I created a values directory in which I created a config.xml file that appears
as follows:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<bool name="config_voice_capable">true</bool>
<bool name="config_enableLockScreenRotation">true</bool>
</resources>
Notice that this file specifies only the 2 config values I wish changed. You can
add any other resources you want modified.
At the same level as the res/ directory create a manifest files AndroidManifest.xml
as follows:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.android.frameworkres.overlay">
</manifest>
2. Now using aapt build a package for the overlay as follows:
>aapt package -S res/ -M AndroidManifest.xml -f -v -F framework-res-overlay.apk
This will create the overlay package framework-res-overlay.apk, using resources in the res/
directory and the specified manifest file.
3. Now simply transfer the framework-res-overlay.apk to your device (I use a wifi ftp connection)
and save it on your sdcard (I use /sdcard/data).
Now on your Nexus or other device:
1. First check on your device for a directory /vendor/overlay.
2. If one is not present (it won't be by default) go into a terminal emulator on your device
and execute:
>su
>mount -o remount rw /system
>mkdir /vendor/overlay
3. Now copy the overlay package into that directory:
>cp /sdcard/data/framework-res-overlay.apk /vendor/overlay
That's it.
Simply power down your device then power up again and the new resources you specified
will replace the built-in defaults.
I hope that helps. And thanks to the original poster who discovered this feature.
It is in the source code tree, and is a much cleaner method for altering framework
resources at runtime than the procedure others have been using of decompiling, editing and
re-building, imo.
Good luck.

1. Awesome first post!
2. What are you gonna do for your second post? I bet it's all downhill from here LOL
Anyway, wow... this is very cool indeed

lol wait wait... could this potentially solve the clusterf*?! that is recompiling Motorola blur frameworks??
as it stands: you either choose gimped AOSP/CM ROMs with no webtop or hdmi.. or obnoxiously difficult to theme / mod blur framework that must be recompiled and signed very carefully..
plzs?

I try to follor your instruction but failed.
To make it works:
1. make xml folder under res
2. move config.xml to res\xml
3. move AndroidManifest.xml to a parent directory of res
So, file structure shold be:
Code:
AndroidManifest.xml
\_res
\_xml
\_config.xml
run your aapt command you will get framework-res-overlay.apk
But nothing happen after put it in /vendor/overlay... still finding a solution for this.
Thank you.

Can you detail:
2. Now using aapt build a package for the overlay as follows:
>aapt package -S res/ -M AndroidManifest.xml -f -v -F framework-res-overlay.apk
When I run this I get an error stating res/ is not found

Doing It Wrong!!
jrmora said:
Can you detail:
2. Now using aapt build a package for the overlay as follows:
>aapt package -S res/ -M AndroidManifest.xml -f -v -F framework-res-overlay.apk
When I run this I get an error stating res/ is not found
Click to expand...
Click to collapse
Congratulations!!! as your prize you get to read the documentation!! LOL Seriously you only use the -o switch and that is all.. It's all laid out in the original thread and further more in the Readme file in the Android Source Tree

still doin it wrong
thanks for the reply. Read the docs, still not clear. Can you specify how to use the -o switch please
trevd said:
Congratulations!!! as your prize you get to read the documentation!! LOL Seriously you only use the -o switch and that is all.. It's all laid out in the original thread and further more in the Readme file in the Android Source Tree
Click to expand...
Click to collapse

jrmora said:
thanks for the reply. Read the docs, still not clear. Can you specify how to use the -o switch please
Click to expand...
Click to collapse
Just wanted to note that in the newest version of aapt, there is no longer a -o switch.
The -S switch, followed by a directory path, specifies where to find the resources.
Use aapt -h to get help on aapt and a description of its options. Just follow the instructions I originally
documented and it all works out.

barrykr said:
Just wanted to note that in the newest version of aapt, there is no longer a -o switch.
The -S switch, followed by a directory path, specifies where to find the resources.
Use aapt -h to get help on aapt and a description of its options. Just follow the instructions I originally
documented and it all works out.
Click to expand...
Click to collapse
Hi barrykr
Thanks for heads up. To be honest I've only compiled this from within the android source source tree. So I use the android makefile.
Sent from my Nexus 7 using xda premium

great bro
barrykr said:
Hi all:
I am new to xda-developers but a very experienced software designer.
In attempting to enable Google Voice calling on my new Nexus 7, I followed some threads here that
showed how to enable config_voice_capable in framework-res.apk via decompiling and rebuilding. It occurred to me that there
might be a more direct method for resource changes and I discovered, also
in here a post at http://forum.xda-developers.com/showthread.php?t=1842302&nocache=1,
indicating the built-in overlay feature in android, for modifying resources at runtime.
I thought this looked promising and tried it out. I just wanted to confirm that it works well. I was unable to post in that
thread because I am new here, but I thought it would be worthwhile documenting what I did, for the benefit of
others.
I tested this method to enable 2 booleans in framework-res.apk but I believe it will work with any resources.
The booleans I enabled for testing were "config_voice_capable" and "config_enableLockScreenRotation".
All that is required on a rooted device is the following:
1. On your development machine (with aapt and other platform-tools installed).
switch to any directory of your choice for development purposes and
under it create a res/ directory for the resources you wish to change. Under this directory
I created a values directory in which I created a config.xml file that appears
as follows:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<bool name="config_voice_capable">true</bool>
<bool name="config_enableLockScreenRotation">true</bool>
</resources>
Notice that this file specifies only the 2 config values I wish changed. You can
add any other resources you want modified.
At the same level as the res/ directory create a manifest files AndroidManifest.xml
as follows:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.android.frameworkres.overlay">
</manifest>
2. Now using aapt build a package for the overlay as follows:
>aapt package -S res/ -M AndroidManifest.xml -f -v -F framework-res-overlay.apk
This will create the overlay package framework-res-overlay.apk, using resources in the res/
directory and the specified manifest file.
3. Now simply transfer the framework-res-overlay.apk to your device (I use a wifi ftp connection)
and save it on your sdcard (I use /sdcard/data).
Now on your Nexus or other device:
1. First check on your device for a directory /vendor/overlay.
2. If one is not present (it won't be by default) go into a terminal emulator on your device
and execute:
>su
>mount -o remount rw /system
>mkdir /vendor/overlay
3. Now copy the overlay package into that directory:
>cp /sdcard/data/framework-res-overlay.apk /vendor/overlay
That's it.
Simply power down your device then power up again and the new resources you specified
will replace the built-in defaults.
I hope that helps. And thanks to the original poster who discovered this feature.
It is in the source code tree, and is a much cleaner method for altering framework
resources at runtime than the procedure others have been using of decompiling, editing and
re-building, imo.
Good luck.
Click to expand...
Click to collapse
is't possible to use overlay to add/ change a value in build.prop file ?